Cisco Prime Nerk 43 User Guide

							  
8-19
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 Port Status and Properties and Checking Port Utilization
The following table lists the subinterface properties that are not self-explanatory. The subinterface 
configuration determines which properties are displayed. Double-click any properties that are hyperlinks 
to view additional properties.
Viewing the Services That Are Configured on a Port
A physical port’s configuration details can include services that are provisioned on the port. Information 
that is displayed includes: 
Physical layer information.
Layer 2 information, such as ATM and Ethernet. 
Subinterfaces used by a VRF.
For more information on the services, check the logical inventory. See Viewing the Logical Properties 
of a Device (Traffic, Routing, Information, Tunnels, Data Link Aggregations, Processes), page 8-21.
Checking a Port’s Utilization
Prime Network provides a tool that displays a port’s current Rx/Tx Rate and historical rate information. 
These graphs are for physical ports only. Port utilization graphs are not available for ATM, E1/T1, or 
ATM IMA interfaces that are included in an IMA group. Whether you can run these commands depends 
on your permissions. See Vision Client Permissions, page B-1. 
Step 1Open the inventory window and select the required port in physical inventory. 
Step 2In the Ethernet CSMA/CD section, click Port Utilization Graph. You may have to scroll down the 
properties area to display this tool.
The following information is displayed in the Port Statistics dialog box:Field Description
VLAN Type Type of VLAN, such as Bridge or IEEE 802.1Q. 
Operational State Operational state of the subinterface.
VLAN ID VLAN identifier.
Inner VLAN CE-VLAN identifier.
IP Interface IP interface, hyperlinked to the VRF properties in the inventory window.
VRF Name Name of the VRF.
Is MPLS Whether this is an MPLS interface: True or False.
VC Virtual connection (VC) configured on the interface, hyperlinked to the VC 
Table window. (For more information about VC properties, see Vi ew i n g  
ATM Virtual Connection Cross-Connects, page 26-6.)
Tunnel Edge Hyperlinked entry to the specific tunnel edge in logical inventory. 
Binding Hyperlinked entry to the specific bridge or pseudowire in logical inventory. 
Rx Rate Reception rate (percentage)
Rx Rate History Graphical representation of reception rate history
Tx Rate Transmission rate (percentage)
Tx Rate History Graphical representation of transmission rate history 
						

							  
8-20
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 Port Status and Properties and Checking Port Utilization
Step 3Click   to close the Port Statistics dialog box.
Disabling a Port’s Alarms
By default, alarms are enabled on all ports. If you expect a port to go down, you can disable alarms on 
the port so that no alarms are generated or displayed in the ticket and events pane. To disable alarms on 
ports: 
Step 1Open the inventory window for the required device. 
Step 2To disable alarms on individual ports, right-click the port and choose Disable Sending Alarms. The 
Sending Alarms field displays the value false, indicating that the alarm for the required port has been 
disabled, and the content pane displays the Enable Sending Alarms button.
Step 3To disable alarms on one or more ports at the same time:
a.In the inventory window, click the Ports tab.
b.In the Ports table, select the required ports. You can select multiple ports by using the Ctrl and Shift 
keys. 
c.Right-click one of the selected ports, and choose Disable Sending Alarms. In response, the Sending 
Alarms field displays the value false for the selected ports. 
To enable alarms, use the previous procedure but choose Enable Sending Alarms.
Viewing the Pluggable Optics of Break-Out Mode Capable ports in Physical 
Inventory
An external physical port could be broken down in to multiple sub ports if it supports the break out 
functionality. For example, a 100 Giga port can be broken into ten 10-giga ports. In this case, each and 
every port must be modeled. However, a single pluggable optic must be maintained for each of these 
ports. 
In Prime Network, the ports and the pluggable optics for a NCS6008 device are modeled separately. The 
pluggable optic as well as the port must be shown separately and at the same level for this device. 
To view the pluggable optic details for a NCS device:
Step 1Right-click the NCS device and choose the Inventory option.
Step 2In the Inventory menu, expand the Physical Inventory node.
Step 3Choose Chassis>Slot>port. In the content pane, view the Associated Pluggable field under the 
Ethernet CSMA/CD section.The pluggable transceiver links to the associated slot.
NoteYou can view the Associated Pluggable field only when the pluggable transceiver is available in MIB. 
						

							  
8-21
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 the Logical Properties of a Device (Traffic, Routing, Information, Tunnels, Data Link Aggregations,
Step 4
Step 5
view the pluggable port in the Associated Pluggable field under the Ethernet CSMA/CD section.
Viewing the Logical Properties of a Device (Traffic, Routing, 
Information, Tunnels, Data Link Aggregations, Processes)
The logical inventory lists configuration data, forwarding, and service-related components that affect 
traffic handling in the element. Figure 8-15 shows an example of the Forwarding Component Containers 
for a Cisco 7604 router. All of the items listed in the tab are configured on the device. If something is 
not displayed, that means it has not been configured on the device.
Figure 8-15 Logical Inventory—Forwarding Components for Cisco 7604 Router
These topics describe the information you can obtain when you click the various Logical Inventory tabs.
Viewing a Device’s Traffic Descriptors, page 8-22.
Viewing a Device’s Forwarding Components, Device and VRF Routing Tables, and IP Interfaces, 
page 8-22.
Viewing a Device’s Tunneling Containers, page 8-23. 
						

							  
8-22
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 the Logical Properties of a Device (Traffic, Routing, Information, Tunnels, Data Link Aggregations, Processes)
Viewing a Device’s Data Link Aggregation Containers, page 8-23.
Viewing Management Processes that Are Running on a Device, page 8-23.
Viewing a Device’s Operating System Details (and K9 Security), page 8-25. 
Viewing a Device’s Traffic Descriptors
Traffic descriptors can include access lists, ATM and Frame Relay traffic profiles, OAM, forwarding 
tables, and so forth. To find out which traffic descriptors are configured on a device:
Step 1In the Inventory window, choose Logical Inventory.
Step 2Click the Traffic Descriptors tab. It lists the traffic descriptors that are configured on the NE—for 
example, ATM and Frame Relay traffic profiles or OAM.
Step 3Click a traffic descriptor container in the logical inventory for information on that container. For 
example, if you choose Logical Inventory > OAM, you can view the OAM local port and its admin 
status.
Viewing a Device’s Forwarding Components, Device and VRF Routing Tables, 
and IP Interfaces
To find out which forwarding components are configured on a device:
Step 1In the Inventory window, choose Logical Inventory.
Step 2Click the Forwarding Components Container tab. It lists the forwarding components that are configured 
on the NE—for example, bridges, routing entities, local switching, VRFs, and so forth.
Step 3Click a forwarding component container in the logical inventory for information on that container. For 
example, if you choose Logical Inventory > Routing Entities > Routing Entity, you can view all 
interface types configured on the devices, such as Ethernet, GigabitEthernet, loopback, VLAN, and so 
forth. 
Click the IP Interfaces tab to see the IPaddress, associated entity, and so forth
Click the IPv4 (or IPv6) Routing Table tab to see the destination, hops, and so forth
You can also use the following commands to view a device’s routing table and the routing table of a 
selected VRF. The devices that support these commands are listed in the Addendum: Additional VNE 
Support for Cisco Prime Network 4.3. Whether you can run these commands depends on your 
permissions. See Vision Client Permissions, page B-1.
Command Navigation Description
Show> IP Route Logical Inventory> Routing Entities> 
Routing Entity> CommandsDisplays the device routing 
table. 
						

							  
8-23
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 the Logical Properties of a Device (Traffic, Routing, Information, Tunnels, Data Link Aggregations,
Viewing a Device’s Tunneling Containers
Tunneling containers can include GRE tunnels, pseudowires, traffic engineering tunnels, and so forth. 
Step 1In the Inventory window, choose Logical Inventory.
Step 2Click the Tunneling Containers tab. It lists the tunneling containers that are configured on the NE—for 
example, GRE, pseudowire, traffic engineering tunnels, and so forth.
Step 3Click a tunneling container in the logical inventory for information on that container. For example, if 
you choose Logical Inventory > Traffic Engineering Tunnels, you can view the TE tunnel name, 
admin and operational status, outgoing label, lockdown status, and so forth. 
Viewing a Device’s Data Link Aggregation Containers
Use this procedure to view data link aggregation containers such as Ethernet Link Aggregations. ICL 
and transport are the two types of ethernet link bundles where ICL link type represents the ethernet link 
bundle between Cisco ASR 9000 device and satellite chassis or between two satellite chassis. Transport 
link type represents the ethernet link bundle between two Cisco ASR 9000 devices.
Step 1In the Inventory window, choose Logical Inventory.
Step 2Choose Logical Inventory > Ethernet Link Aggregation to view the aggregation type, bandwidth, 
aggregation control protocol, load balance type (Source and Destination MAC, Source IP, or Destination 
IP), link type, and so forth. 
Viewing Management Processes that Are Running on a Device
Use this procedure to find out which management processes are running on a devices. These processes 
can include BFD, CFM, CDP, clock, E-LMI, ICCP redundancy, IP SLA responder, LLDP, REP, STP, 
VTP, and so forth.
Step 1In the Inventory window, choose Logical Inventory.
Step 2Click the Processes tab. It lists the management processes that are configured on the NE—for example, 
BFD, LLDP, clock, E-LMI, and so forth.Show> VRF IP route Logical Inventory> VRFs> VRF> 
CommandsDisplays the routing table of a 
selected VRF.
Show> IP> 
Interface BriefNE> CommandsLists all IP interfaces on the 
device. Command Navigation Description 
						

							  
8-24
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 Technologies and Services Configured on a Device
Step 3Click a process container in the logical inventory for information on that container. For example, if you 
choose Logical Inventory > Bidirectional Forwarding Detection, you can view the source and 
destination IP, the protocols, state, and so forth for a BFD session. 
Viewing Technologies and Services Configured on a Device
The inventory window provides detailed information on the different services and technologies 
configured on a devices. The Vision client may also provide configuration commands that are specific 
to those technologies and services. See these topics for information on to drill down into a device’s 
inventory to get this information.
To get information about this technology/service on a device: See:
Carrier Ethernet—CDP, LLDP, STP, REP, HSRP, access gateways, 
Ethernet Link Aggregation groups, mLACP, provider backbone, EFPs, 
EVC services, ethernet flow domains VLANs, unassociated bridges, 
ethernet flow point cross-connects, VPLS and H-VPLS, Pseudowires, 
Ethernet services, IP SLA, IS-IS, OSPFManaging Carrier Ethernet 
Configurations, page 18-1
Carrier Grade NAT—CGNs, VRFs, address poolsMonitoring Carrier Grade 
NAT Configurations, 
page 20-1
DWDM—OTU and ODU alarms, FEC info, counter information, 
performance statisticsManaging DWDM 
Networks, page 16-1
CFM, E-LMI, L-OAMManaging Ethernet 
Networks Using Operations, 
Administration, and 
Maintenance Tools, 
page 19-1
Y.1731 IPSLA—Performance management statistics and probesManaging IP Service Level 
Agreement (IP SLA) 
Configurations, page 22-1
MPLS services—MPLS over IPv6 (6VPE0, MPLS-TP tunnels, VPNs, 
VRFs, IP interfaces, MPLS-TE, RSVP, BGP, VRRP, Bundle EthernetManaging MPLS Networks, 
page 17-1
IP and MPLS Multicast nodes and protocols, address family (IPv6) 
profiles, multicast label switching, multicast routing entitiesMonitoring IP and MPLS 
Multicast Configurations, 
page 23-1
MToP services—SAToP and CESoPSN pseudowire, virtual connections, 
IMA groups, TDM, channelization, MLPPP and MLPPP links, MPLS 
pseudowire over GRE, network clock, CEM and virtual CEM, SONET, 
APSManaging Mobile Transport 
Over Pseudowire (MToP) 
Networks, page 26-1
SBCs—DBEs, SBEs, performance statisticsManaging Session Border 
Controllers (SBCs), 
page 24-1
AAA—AAA groups, dynamic authorization profiles, RADIUS and 
diameter global configurations, charging configurationsMonitoring AAA 
Configurations, page 15-1
IP pool monitoring and configurationManaging IP Address Pools, 
page 14-1 
						

							  
8-25
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 a Device’s Operating System Details (and K9 Security)
Viewing a Device’s Operating System Details (and K9 Security)
All devices will display the software version running on the device when you open the NE inventory 
window and select the NE at the very top of the navigation area (see Figure 8-2 on page 8-3 for an 
example). Depending on the operating system and device type, you can drill down into more operating 
system details using one of these methods. 
If you need to change the software image on an NE, use the procedures described in Managing Device 
Software Images, page 9-3.
NoteNot all devices will display the same fields; it depends on the device type, operating system, and device 
configuration.
Open the logical inventory and click the Operating System tab. For groups of devices (such as Nexus 
data center aggregations), choose Logical Inventory > Nexus management node> Operating System.  BNG—Policy containers and QoS profiles, BBA groups, subscriber 
access points, DHCP, dynamic configuration and PPP templatesMonitoring BNG 
Configurations, page 25-1
Mobile technologies—GPRS/UMTS networks (GGSN, GTPU, APNs, 
GTPP, eGTP, SGSN); LTE networks (SAE-GW, P-GW, S-GW, QCI-QoS 
mapping, LAC, HSGW, home agent, foreign agent, ePDG, PDSN, 
LMA); operator polices, APN remaps and profiles; active charging 
servicesManaging Mobile 
Networks, page 27-1
Data centers—Virtual port channels, Cisco FabricPath, virtualized 
resources (hypervisors and compute servers, virtual machines, data 
stores, clusters, resource pools)Managing Data Center 
Networks, page 28-1
Cable technologies—Cable ports and interfaces, upstream and 
downstream configurations, QAM, DEPI, L2TP, MAC domains, 
narrowband channelsMonitoring Cable 
Technologies, page 29-1
ADSL2+ and VDSL2—XDSL traffic descriptors, DSL bonding groups, 
supported transport models, one-to-one and TLS access profilesMonitoring ADSL2+ and 
VDSL2 Technologies, 
page 30-1 To get information about this technology/service on a device: See:
Field Description
Is K9Sec If the operating system K9 security feature is enabled (true) or disabled 
(false)
Family Cisco family, based on the device platform
SDR Mac Addr (Cisco IOS XR only) Secure Domain Router (SDR) MAC address
Software Version Operating system software version
Boot Software System image information
ROM Version Bootstrap software version 
						

							  
8-26
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
  Updating the Inventory (Poll Now)
For some Cisco IOS-XR devices, more information will be displayed in the Operating System tab, or by 
choosing Logical Inventory > Modular OS.
Updating the Inventory (Poll Now)
Prime Network polls devices according to settings that configured when the device is added to Prime 
Network. By default, Prime Network uses its reduced polling mechanism (also called event-based 
polling) and polls the device when a configuration change syslog is received. In other words, updates are 
driven by incoming events. Only the affected areas of the NE are polled, and the modeling information 
is immediately updated. 
For example, if you see in the device inventory properties that an NE is in the Currently Unsynchronized 
investigation state and you suspect an event was dropped, you should perform a manual poll of the 
device. Or, if you make a manual device configuration change and want to update the Prime Network 
model, poll the NE that you reconfigured.
Be sure you perform the poll from the right point in the inventory. Follow the below points:
If one container is populated or dependent on another table (parent table), update the parent table. 
For example, the GRE tunnels container and the ARP entities container are generated from the 
IP Interface table. When the IP Interface table is polled, the IP address will be populated and the 
GRE tunnel and ARP entity properties will be updated accordingly. 
Perform the poll from the most efficient location in the NE. For example, do not poll the entire 
device if you only made a small change.
When you are ready to perform the poll, select a device in a map, or an NE in a device’s physical or 
logical inventory, and click Poll Now.
Changing the NE Host Name
This procedure changes the system name of the network device. After you poll the device, the hostname 
is updated in the Vision client. Because the NE’s information is saved by Prime Network using an ID 
that cannot be modified, all of the NE’s information (such as its ticket history) remains associated with  Field Description
Boot Software System image information
SDR Name SDR name
SDR Id SDR identifier
ROM Version Bootstrap software version
RAM Size Size (kilobytes) of device processor RAM
OS Packages Table
Package Info Package information in the format device:package-version, such as 
disk0:hfr-admin-3.9.3.14
Package Description Description of the package, such as FPD (Field Programmable 
Device) Package
Composite Name Name of composite package with date and time, such as:
Tues Feb 8 20:37:07.966 UTC
disk0:comp-hfr-mini-3.9.3.14  
						

							  
8-27
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
  Changing the SNMP Configuration and Managing SNMP Traps
the NE. Whether you can run this command depends on your permissions. See Permissions for Vision 
Client NE-Related Operations, page B-4. You can verify whether a device supports this command by 
checking the information in the Addendum: Additional VNE Support for Cisco Prime Network 4.3.
Step 1Right-click an NE and choose Commands > Configuration > System >Remove host name.
Step 2Click Execute Now to remove the device’s current host name. The device’s hostName value is set to null, 
and the name is deleted from Prime Network object.
Step 3Right-click the NE and choose Commands > Configuration > System >Add host name.
Step 4Enter the new host name and click Execute Now.
Step 5Right-click the NE and choose Poll Now to update the NE information in the Prime Network inventory.
Changing the SNMP Configuration and Managing SNMP Traps
These commands change these SNMP properties on the real device. If you change the device SNMP 
configuration, you must also change the settings on the VNE (the model of the device that is maintained 
by Prime Network). Otherwise, Prime Network will not be able to properly communicate with and 
model the device. Whether you can run these commands depends on your permissions. See Appendix B, 
“Permissions Required to Perform Tasks Using the Prime Network Clients”. You can verify whether a 
device supports these commands by checking the information in the Addendum: Additional VNE Support 
for Cisco Prime Network 4.3.2.
Step 1Right-click a device in the map, or choose the (top-level) device name in the inventory window.
Step 2Use the following commands to change the device configuration. When you launch the command, click 
Preview to see the actual commands that will be sent to the device.
Step 3To change the SNMP configuration on the device VNE:
a.Right-click the NE and choose Properties.
b.Click VNE Details.
c.In the VNE properties window, click the SNMP tab and change the settings so they are consistent 
with the changes you made in the previous step. To do the following: Right-click device and choose:
Change the SNMP configuration 
(community settings, read-write 
access control, view-based 
access control, group settings, 
and so forth)Commands > Configuration > System > SNMP> Add SNMP 
Configuration
Commands > Configuration > System > SNMP > Update SNMP 
Configuration
1
Commands > Configuration > System > SNMP> Remove 
SNMP Configuration
1. The “Update SNMP configuration” command is not applicable for Cisco UBR10K and RFGW10 cards.
Enable, disable, and remove traps 
by choosing them from a 
drop-down listCommands > Configuration > System > SNMP> Add Traps
Commands > Configuration > System > SNMP> Enable Traps
Commands > Configuration > System > SNMP> Remove Traps 
						

							  
8-28
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
  Changing Device Port Properties and Disabling Ports
d.Click OK.
Step 4Right-click the NE and choose VNE Tools > Stop VNE.
Step 5When the device icon turns red, right-click the NE and choose VNE Tools > Start VNE and 
Prime Network will poll the device.
NoteWhen VNE is configured to use SNMPv2 or SNMPv3 for discovery, ensure that the device must be 
enabled with SNMPv1 also.
Changing Device Port Properties and Disabling Ports
The following commands change the port properties of the real device. Whether you can run these 
commands depends on your permissions. See Appendix B, “Permissions Required to Perform Tasks 
Using the Prime Network Clients”. You can verify whether a device supports these commands by 
checking the information in the Addendum: Additional VNE Support for Cisco Prime Network 4.3.2.
Step 1Locate the port in the physical inventory.
Step 2Change the port configuration using the commands in the following table. When you launch the 
command, click Preview to see the actual commands that will be sent to the device.
To make the following change on a port:Right-click port in Physical Inventory and 
choose:
Change port status: Disable (Shutdown) or enable (No 
Shutdown) 
For example, shutting down a port prevents a known 
fault from continuing to generate eventsCommands > Configuration > System > 
Change Port Status
Configure the descriptive information that is displayed 
in Prime Network clients when the port is selected such 
as customer information or business case details)
(You can also label ports using business tags; see 
Labelling NEs to Associate Them with Customers 
(Business Tags), page 4-9)Commands > Configuration > 
System >Add Port Description
Commands > Configuration > System > 
Remove Port Description
Commands > Configuration > System > 
Update Port Description
Change port characteristics such as bindings, contexts, 
link aggregations, and so forthCommands > Configuration > System > 
Modify Port
Assign a port to a VLAN assignment (enter a VLAN 
between 1-4094); or deassign a port from a VLAN. 
When assigned, the port can communicate only with or 
through other devices in that VLAN. When deassigned, 
you can move a port to a new VLAN.
Other VLAN actions are described in Wo r k i n g  w i t h  
VLANs, page 18-62.Logical Inventory> Routing Entities>
Routing Entity> interface> 
Commands> Configuration> Assign 
Port to Vlan
Logical Inventory> Routing Entities>
Routing Entity> interface> 
Commands> Configuration> DeAssign 
Port To Vlan