Cisco Prime Nerk 43 User Guide

							  
7-37
Cisco Prime Network 4.3.2 User Guide
Chapter 7      Viewing Devices, Links, and Services in Maps
  Changing the Vision Client Default Behavior
Changing the Vision Client Default Behavior
All users can change their Vision client defaults. The defaults apply only to the client machines—that 
is, the machine from which you launch the Vision client. You can change:
What is displayed when you start the Vision client
Audio alerts and sounds
NE text (font sizes, whether you can label NEs with business tags)
Ticket severity information that is displayed with an NE icon
Age of tickets that are displayed in the Vision client
To change these settings, see Changing Vision Client Default Settings (Sound, Display, Events Age), 
page 4-15. 
						

							  
7-38
Cisco Prime Network 4.3.2 User Guide
Chapter 7      Viewing Devices, Links, and Services in Maps
  Changing the Vision Client Default Behavior 
						

							CH A P T E R
  
8-1
Cisco Prime Network 4.3.2 User Guide
8
Drilling Down into an NE’s Physical and Logical 
Inventories and Changing Basic NE Properties
The following topics describe how to view a device’s physical and logical inventory using the Vision 
client:
Drilling Down into the Properties of a Network Element, page 8-2
Viewing Single- and Multi-Chassis Devices, Clusters, Satellites and Their Redundancy Settings, 
page 8-4
Viewing Cards, Fans, and Power Supplies and Their Redundancy Settings, page 8-13
Viewing Port Status and Properties and Checking Port Utilization, page 8-14
Viewing the Logical Properties of a Device (Traffic, Routing, Information, Tunnels, Data Link 
Aggregations, Processes), page 8-21
Viewing a Device’s Operating System Details (and K9 Security), page 8-25
Updating the Inventory (Poll Now), page 8-26
Changing the NE Host Name, page 8-26
Changing the SNMP Configuration and Managing SNMP Traps, page 8-27
Changing Device Port Properties and Disabling Ports, page 8-28
Changing Device Interface Properties and Disabling Interfaces, page 8-29
Changing Server Settings for DNS, NTP, RADIUS, and TACACs, page 8-30
Suppressing Service Alarms on Virtual Interfaces, page 8-31 
						

							  
8-2
Cisco Prime Network 4.3.2 User Guide
Chapter 8      Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties
  Drilling Down into the Properties of a Network Element
Drilling Down into the Properties of a Network Element
From a map, double-click an NE to open its inventory window. Figure 8-1 provides an example.
Figure 8-1 Inventory Window 
1Physical and logical inventory—Physical Inventory includes the device components such as chassis, satellite, cards, and 
subslots. Configuration and status information is continuously updated. Logical inventory includes access lists, ATM 
traffic profiles, routing entities, and other logical entities. 
2Poll Now button—Initiates a poll of the selected NE.
3VNE Details button (VNEs are internal components, one VNE per device)—Provides information about whether the 
VNE is operating correctly, what polling values are set, and so forth.
4VNE Status button—Lists the protocols the device is using (it can also provide troubleshooting information).
5Property tabs (General properties and Ports properties in this example)—The Ports tab provides a quick list of all device 
ports. The tabs displayed depend on what is selected. General tab can also display context-sensitive tabs and buttons.
6Properties area—Provides inventory details. For a closer view of the Properties panel, see Figure 8-2 on page 8-3. The 
NE icon may also display:
Colors indicating a ticket and the ticket severity. See Severity Icons and Colors for Events, Tickets, and NEs, 
page A-14 for an explanation of the colors.
Badges that represent technologies such as a Protected LSP or an STP root. See Network Element 
Technology-Related Badges, page A-23 for a list of badges.
7Vision client status bar.
320084
8
12634
7
9
10
5 
						

							  
8-3
Cisco Prime Network 4.3.2 User Guide
Chapter 8      Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties
  Drilling Down into the Properties of a Network Element
Figure 8-2 shows the basic properties window for an NE. To display the basic properties, open the 
inventory window and select the NE at the very top of the navigation area.
Figure 8-2 NE Basic Properties Window
The following table provides information about the fields that are not self-explanatory.
Figure 8-3 provides an example of the device view pane for a Cisco device. The circled slot in the device 
view pane corresponds to the circled slot in the physical inventory navigation pane.  8Ticket and events pane—Displays tickets associated with the selected NE (from the last 6 hours) and associated Network 
and Provisioning events. See Ways You Can View Tickets and Events, page 11-1.
9Device view—Generic representation of the chassis, slots, modules, subslots and ports. All occupied slots are rendered in 
the device view pane. Problems are indicated with colors. See Figure 8-3 on page 8-4.
10Device view tools for zooming and best fit.
Field Description
Communication 
StateAbility of the Prime Network device model to reach the network element and 
other components in Prime Network. 
Investigation State Level of network element discovery that has been performed or is being 
performed by the Prime Network device model. 
Up Since Date and time the element was last reset.
Sending Alarms Whether or not the element is configured for sending alarms (True or False) 
						

							  
8-4
Cisco Prime Network 4.3.2 User Guide
Chapter 8      Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties
  Viewing Single- and Multi-Chassis Devices, Clusters, Satellites and Their Redundancy Settings
Figure 8-3 Device View Pane
TipYou can display or hide the ticket and events pane by clicking the arrows displayed below the device 
view panel.
Viewing Single- and Multi-Chassis Devices, Clusters, Satellites 
and Their Redundancy Settings
To get an NE’s chassis details, choose Physical Inventory > Chassis. Prime Network displays the 
chassis serial number and description, along with the equipment in each slot.
Icon NE
Chassis
Cluster
Satellite
Shelf 
						

							  
8-5
Cisco Prime Network 4.3.2 User Guide
Chapter 8      Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties
  Viewing Single- and Multi-Chassis Devices, Clusters, Satellites and Their Redundancy Settings
If any items in the chassis inventory are black, it means the item was physically removed. You can verify 
this by checking the item status which should display Out. The other properties of the removed item 
reflect the most recent value that was updated from the device.
Viewing Multi-Chassis Devices
Multi-chassis devices, such Cisco ASR9000 and Cisco UCS devices, are grouped into aggregations and 
displayed as a single entity with a plus sign as shown in Figure 8-4. 
Figure 8-4 Multichassis Devices in Map View
The physical ethernet links used for connecting the multi chassis devices are ICL (Inter Chassis Link) 
and IRL (Inter Rack Link). For more information on when each of these links are used, see Vi ew i n g  
Cluster Inter-Rack Links (IRLs), page 8-6 and Viewing Satellites and Satellite Inter-Chassis Links 
(ICLs), page 8-7. 
Viewing Redundant (Primary and Secondary) Devices
In the Failover Configuration, two ASA devices are connected to each other. When the primary device 
becomes unavailable due to failure or down time, then the secondary device takes over the function of 
the primary device. The ASA device supports the following two failover configurations:
Active/Active Failover—Also called the group failover, this type of configuration is available only 
in multiple context mode. In this configuration, both the ASA devices are active and pass traffic. 
This lets you configure load balancing on your network. When one of the devices becomes 
unavailable, then its functions are taken over by the other device. 
As mentioned earlier, this configuration has multiple contexts. The security contexts are divided into 
two failover groups. In other words, each device will have two failover groups. 
NoteBy default, the admin context and any unassigned security contexts are members of failover 
group 1.
These groups can be in Active, Standby or a combination of Active and Standby modes. If Group 1 
of the first ASA device is Active, then Group 1 of the second device must be in Standby mode. If 
Group 1 of the first ASA device (which is active) becomes unavailable, then Group 1 of the second 
device (which is in Standby mode) will become active. The same process applies for Group 2 
contexts in both the devices. 
						

							  
8-6
Cisco Prime Network 4.3.2 User Guide
Chapter 8      Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties
  Viewing Single- and Multi-Chassis Devices, Clusters, Satellites and Their Redundancy Settings
Active/Standby Failover—This type of configuration is available either on single or multiple context 
mode. In this configuration, only one of the units is active while the other one is in standby mode. 
When the active unit becomes unavailable, then the standby unit becomes active.
When there is a failover, and the secondary device takes over, syslogs are generated. You can view the 
syslog information in the “Latest Events” tab. 
Figure 8-5 depicts the ASA failover scenario, along with the events that are generated after the failover:
Figure 8-5 ASA Failover topology with generated events
NoteThese syslogs help Prime Network to identify the devices that are in active and standby mode. When an 
active device goes into standby mode, and the other device becomes active, Prime Network changes the 
IP address of these devices. For example, if the primary devices goes into standby mode, the secondary 
device will take over the IP address of the primary device and starts functioning immediately.
Viewing Cluster Inter-Rack Links (IRLs)
Inter-Rack Links (IRLs) represent connectivity between the cluster chassis as shown in Figure 8-6.  
						

							  
8-7
Cisco Prime Network 4.3.2 User Guide
Chapter 8      Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties
  Viewing Single- and Multi-Chassis Devices, Clusters, Satellites and Their Redundancy Settings
Figure 8-6 Multiple Chassis in a Cluster
To view the cluster IRLs:
Step 1Double-click the cluster device to open the Inventory window. 
Step 2In the device’s Logical Inventory, choose Cluster IRL. A list of cluster IRLs is displayed showing the 
following information:
A End Point—Device or site that is the source of the link, hyperlinked to the inventory of the device 
or site.
Z End Point—Device or site that is the destination of the link, hyperlinked to the relevant entry in 
the inventory.
Viewing Satellites and Satellite Inter-Chassis Links (ICLs)
The Cisco ASR 9000 Series Router Satellite Network Virtualization (nV) service or the Satellite 
Switching System enables you to configure a topology in which one or more satellite switches 
complement one or more Cisco ASR 9000 Series routers, to collectively realize a single virtual switching 
system. In this system, the satellite switches act under the management control of the routers. The 
complete configuration and management of the satellite chassis and features are performed through the 
control plane and management plane of the Cisco ASR 9000 Series Router, which is referred to as the 
host.
The Satellite nV system supports the dual-homed network architecture, based on which two hosts are 
connected to a satellite through the Satellite Discovery And Control (SDAC) Protocol. Both these 
dual-homed hosts act in the active/standby mode for the satellite. The standby host takes control of the 
satellite only when the active host is down. The two hosts can leverage the Inter-chassis Communication 
Protocol (ICCP) infrastructure to provide redundant Layer 2 and Layer 3 services for Satellite Ethernet 
interfaces. The network traffic is switched through the active host. In case of connection loss to the active 
host due failure such as cut cable and host or client connection interface failure, the standby host 
becomes the active host and the active host becomes the new standby host. The hosts communicate with 
each other using ORBIT/ICCP protocols.
The advanced satellite nV system network topologies can be realized based on one of these architecture:
Hub and Spoke.
Ring with Dual Home.
Ring with Layer 2 Fabric.
Linear and Cascade. 
						

							  
8-8
Cisco Prime Network 4.3.2 User Guide
Chapter 8      Drilling Down into an NE’s Physical and Logical Inventories and Changing Basic NE Properties
  Viewing Single- and Multi-Chassis Devices, Clusters, Satellites and Their Redundancy Settings
Figure 8-7 shows an example of a satellite ring topology.
Figure 8-7 Satellite Ring Topology
Figure 8-8 shows an example of a hub and spoke topology.
Figure 8-8 Hub and Spoke Topology
10.104.120.199
10.104.120.198 (3M+)
10.142.41.79 (4...
10.142.42.35 (4...
364095
Chassis 888: AS...
Chassis 102: AS...
Chassis 999: AS...
Chassis 600: AS... Chassis 601: A9...
Chassis 103: AS... Chassis 101: AS...
Chassis 0: ASR...Chassis 0: ASR...
Chassis 101: AS...
Chassis 103: AS... Chassis 102: AS...
!
!
ASR9k-199(1m)
ASR9K
364097
Chassis 888: AS... Chassis 102: AS...
Chassis 999: AS...Chassis 103: AS...
Chassis 101: AS...Chassis 0: ASR...
Chassis 103: AS... Chassis 102: AS...
Chassis 0: ASR...
Chassis 101: AS...