CiscoPrimeNetwork 38 UserGuide PDF
CiscoPrimeNetwork 38 UserGuide PDF
8 User Guide
Published: November 14, 2011
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display
output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in
illustrative content is unintentional and coincidental.
Preface xvii
Audience xvii
Conventions xx
CHAPTER 2 Working with the Cisco Prime Network Vision Client 2-1
User Roles Required for Working with Prime Network Vision Maps 4-2
User Roles Required to Work with Business Tags and Business Elements 6-1
User Roles Required to Work with Tickets in Prime Network Vision 9-1
Roles and Working with Tickets in Prime Network Vision 9-2
Default Permission/Security Levels for Working with Tickets in Prime Network Vision 9-2
CHAPTER 15 Viewing Ethernet Operations, Administration, and Maintenance Tool Properties 15-1
Icons A-1
Network Element Icons A-2
Business Element Icons A-4
Logical Inventory Icons A-6
Physical Inventory Icons A-8
Links A-8
Link Icons A-8
Link Colors A-9
Link Characteristics A-10
Buttons A-12
Prime Network Vision Buttons A-12
Table Buttons A-15
Link Filtering Buttons A-15
Prime Network Events Buttons A-16
Ticket Properties Buttons A-16
Report Manager Buttons A-17
Badges A-17
VNE Communication State Badges A-18
VNE Investigation State Badges A-18
Network Element Technology-Related Badges A-20
Alarm and Ticket Badges A-20
INDEX
This document describes Cisco Prime Network (Prime Network) 3.8. Prime Network serves as an
extensible integration platform for network and service management. At its core is a virtual network
mediation model that is rich, open, and vendor-neutral, and supports the management of diverse
multiservice and multivendor networks. Additionally, Prime Network provides the following mature
NMS functionality:
• Network topology discovery and visualization.
• Element management, providing near real-time inventory.
• Fault management, event correlation, root cause analysis and troubleshooting.
• Network service support.
This preface contains the following sections:
• Audience, page xvii
• Document Organization, page xviii
• Conventions, page xx
• Related Documentation, page xxi
• Obtaining Documentation and Submitting a Service Request, page xxi
Audience
The intended audience for this documentation includes:
• Network viewers who monitor the network and perform basic (nonprivileged) system functions.
• Network operators who perform day-to-day operations such as creating business tags and maps, and
managing alarms.
• Network configurators who activate services and configure network elements.
• System administrators who manage and configure users, network elements, the Prime Network
system, and overall security.
• System managers or administrators who periodically review and manage the events list using
Cisco Prime Network Events (Prime Network Events).
• Networking engineers who are interested in understanding how the Prime Network Events fault and
root cause analysis mechanism works. These engineers should have networking knowledge at Cisco
Certified Network Associate (CCNA) level, and should have received Cisco Prime Network Vision
(Prime Network Vision) basic and administrative training.
Document Organization
This guide contains the following sections:
Conventions
This document uses the following conventions:
Table 1 Conventions
Convention Description
string A string is a nonquoted set of characters. For example, when setting an SNMP
community string to public, do not use quotation marks around the string, or the
string will include the quotation marks.
^ or Ctrl ^ or Ctrl represents the Control key. For example, the key combination ^D or
Ctrl-D means hold down the Control key while you press the D key. Alphabetic
character keys are indicated in capital letters but are not case sensitive.
<> Angle brackets show nonprinting characters, such as passwords.
! An exclamation point at the beginning of a line indicates a comment line.
[] Square brackets show optional elements.
{} Braces group alternative, mutually exclusive elements that are part of a required
choice.
| A vertical bar, also known as a pipe, separates alternative, mutually exclusive
elements of a choice.
boldface font Button names, commands, keywords, and menu items.
boldface screen Courier bold shows an example of text that you must enter.
font
italic font Variables for which you supply values.
italic screen font Variables you enter.
screen font Courier plain shows an example of information displayed on the screen.
Option > Network Choosing a menu item.
Preferences
Related Documentation
Note We sometimes update the documentation after original publication. Therefore, you should also review
the documentation on Cisco.com for any updates.
Cisco Prime Network (Prime Network) provides a suite of GUI tools that offer an intuitive interface for
managing the network and services, and for performing required system administration activities. The
Prime Network client application suite comprises Prime Network Vision, Prime Network Events, and
Prime Network Administration.
The following topics provide an introduction to Prime Network terminology and client applications:
• Basic Prime Network Terminology, page 1-1
• Prime Network Security: Permissions, Roles, and Scopes, page 1-3
• Prime Network Vision, page 1-4
• Prime Network Events, page 1-7
Note For information about the Prime Network Administration application, see the Cisco Prime Network 3.8
Administrator Guide.
Term Description
aggregation A user-defined collection of network elements. For example, an aggregation can
contain devices, links, VPNs, and other aggregations.
alarm Sequence of event notifications that share the same source, cause, or fault. For
example, if a single port goes up and then down, these two events in a related
sequence may result in a single alarm. An alarm is stateful and is opened when a
fault is first detected. Event notifications may be added to the alarm, and it is
archived when it is fixed.
Term Description
association A relationship between the following types of network elements:
• A logical (protocol-oriented) network element and a physical network
element
• A logical network element and another logical network element
• An existing association and anything else
An example for a VPN would be an association between the physical IP interface
and Virtual Routing and Forwarding (VRF) table, which is the associated routing
table. An association is not considered a topological link.
business element Construction or organization of certain network elements and their properties
into a logical entity, to provide the ability to track them in a way that makes sense
from a business perspective.
A virtual private network (VPN) is a business element, which represents a set of
interconnected sites that form a single network over a public network. Prime
Network organizes the business elements in a way that creates a containment
hierarchy that reflects the VPN structure.
business tag A string that is meaningful to the business, and that can be used to label a
component of a network element for use in Prime Network screens and reports.
There are three types of business tags: subscriber, provider, and label. Business
tags are stored in the Prime Network gateway database.
event In the context of network management, a discrete activity that occurred at a
specific point in time.
link A physical or logical connection between:
• Two devices in the network
• A device and an aggregation
• Two aggregations
logical link An association between two network elements (based on a chain of physical links
between the elements); for example, a tunnel.
managed element A network element that is managed by Prime Network; for example, a device,
cloud, or Internet Control Message Protocol (ICMP) VNE.
network element Any physical component or device in the network that can be managed through
an IP address.
physical link A link between physical network objects; for example, a connection between two
physical ports.
provider The party providing a service.
subscriber The party receiving a service.
Term Description
ticket Object that represents an attention-worthy root alarm whose type is marked in the
registry as “ticketable.” A ticket has the same type as the root alarm it represents,
and it has a status, which represents the entire correlation tree. A ticket can be
acknowledged by the user.
Both Prime Network Vision and Cisco Prime Network Events display tickets and
allow you to navigate down to view the consequent alarm hierarchy.
From an operator’s point of view, a fault is always represented by a complete
ticket. Operations such as Acknowledge or Remove are applied to the whole
ticket.
virtual cloud or Network, or part of a network, that is not managed by Prime Network. An
unmanaged unmanaged network is often represented in network diagrams by a cloud symbol
network or image.
VLAN Virtual local-area network (LAN). Group of devices on one or more LANs that
are configured (using management software) so that they can communicate as if
they were attached to the same wire, when in fact they are located on a number
of different LAN segments. Because VLANs are based on logical instead of
physical connections, they are extremely flexible.
VPN Virtual Private Network. Enables IP traffic to travel securely over a public
TCP/IP network by encrypting all traffic from one network to another. A VPN
uses tunneling to encrypt all information at the IP level.
Permission
The user’s ability to perform certain tasks. There are two types of permissions: GUI-related and
element-related.
• GUI-related—Applies only to the activities that are related to GUI functionality, and not the
activities related to network elements. For example, a user with the default permission Viewer can
view maps and the element list. For more information, see the Cisco Prime Network 3.8
Administrator Guide.
• Element-related—Enables the administrator to group a collection of managed elements (in Prime
Network Administration) to allow the user to view and manage the elements based on the user’s role
or permission. After the user is allocated a scope (group of elements) and a role, the user can then
perform various activities on the allocated elements, such as viewing maps or generating reports on
the elements using Report Manager. For more information, see the Cisco Prime Network 3.8
Administrator Guide.
Roles
Prime Network implements a security engine that combines a role-based security mechanism that is
applied on scopes of network elements granted per user. The system supports:
• User account creation
• Network element scope definition
• A set of five predefined roles for security and access control that allow different system functions.
The roles, listed from the lowest security level to the highest security level, are:
– Viewer—Have read-only access to the network and to nonprivileged system functions.
– Operator—Configure business tags and perform most day-to-day operations.
– Operator Plus—Fully control alarm life cycle and create maps.
– Configurator—Activate services and configure the network.
– Administrator—Manage the system configuration and security.
Note Viewer is the lowest security level, and Administrator is the highest. A user with a higher security level
can perform all the Prime Network functions assigned to a user with a lower security level.
Each user is assigned a permission level for an operational scope, which enables the user to perform
certain tasks. Every user has a private username and password. A user can log in from any workstation
with their own set of permissions and operational scope. When a user does not have the required
permission level to perform a function, the appropriate menu option or button is disabled.
The administrator is responsible for defining the types of activities that the user can view and perform
using Prime Network Administration. For more information about user security and defining operational
scopes, see the Cisco Prime Network 3.8 Administrator Guide.
A user’s role (their default permissions) applies only to the activities that are related to GUI
functionality, not the activities related to network elements (which are controlled by scopes). Default
permissions control Prime Network functions.
Scopes
A scope is a named collection of managed network elements that have been grouped together to allow a
user to view or manage the network elements, based on their access role. Grouping can be based on
geographical location, network element type (such as DSLAM, router, or software), network element
category (such as access or core), or any other division according to the network administrator’s
requirements.
For example, using Prime Network Vision, a user who has been assigned a scope can view or manage
the network elements within this scope, according to the role assigned to the user for that scope. The
user cannot view any information regarding network elements that are outside their scope, including
basic properties, inventory, and alarms.
Prime Network Vision supports the creation of multiple network maps to represent specific network
views. Views can cover specific network segments, customer networks, or any other mix of network
elements desired. Once the maps have been created, they are available for all connecting clients (with
support for fine-grained access privileges).
Prime Network Vision enables you to:
• View network inventory and multiple-layer connectivity.
• Troubleshoot, monitor, and manage network elements.
• Model and view network maps, maintaining up-to-date topological information on connections,
traffic, and routes.
Prime Network Vision maps based on Prime Network’s representation of VNEs provide a graphic
display of active faults and alarms, and serve as an easy access point for activation of services. Prime
Network provides rich functionality for displaying and managing network maps by providing:
• Multiple concurrent maps per user.
• Easily customizable hierarchy of nested submaps, aggregations, and business tags with easy
navigation up and down the hierarchy.
• Dual views of the network in a hierarchical tree, as well as in topological maps, including all
network connections.
• Network elements and links using color cues and graphic symbols to indicate status and alarms.
• Mouse point-and-click drill-down from every element (either from the tree or map), providing
detailed internal physical and logical inventory information.
For details on using Prime Network Vision when working with specific technologies, see the following
topics:
• Carrier Ethernet services—Chapter 12, “Monitoring Carrier Ethernet Services”
• Carrier Grade NAT properties—Chapter 13, “Monitoring Carrier Grade NAT Properties”
• Dense wavelength division multiplexing (DWDM) services—Chapter 14, “Monitoring DWDM
Properties”
• Ethernet Operations, Administration, and Maintenance (E-OAM) tool properties—Chapter 15,
“Viewing Ethernet Operations, Administration, and Maintenance Tool Properties”
• IPv6 and 6VPE technologies—Chapter 16, “IPv6 and IPv6 VPN over MPLS”
• Multiprotocol Label Switching (MPLS) services—Chapter 17, “Monitoring MPLS Services”
• Mobile Transport over Packet services—Chapter 18, “Monitoring MToP Services”
• Session Border Controller properties—Chapter 19, “Viewing SBC Properties”
Prime Network Vision is also the launch point for:
• Cisco PathTracer
• Prime Network Soft Properties Manager
• Prime Network Command Builder
• Prime Network Report Manager
• Prime Network Change and Configuration Management
• Prime Network Activation
Cisco PathTracer
Cisco PathTracer enables you to perform end-to-end route tracing with pertinent performance
information displayed simultaneously for the multiple networking layers. Upon receiving a path's
starting point and end point, Cisco PathTracer visually traces the route through the network. For more
information about Cisco PathTracer, see Chapter 11, “Using Cisco PathTracer to Diagnose Problems.”
You can also retrieve reports using BQL. For more information, see the Cisco Prime Network 3.8
Integration Developer Guide.
You can configure Prime Network Events to display the following information:
• Number of events per page.
• Number of events to be exported to a file.
• Previous dated events (in weeks).
• Filter options.
• The information that appears in Prime Network Events tabs, such as the Audit tab.
System managers or administrators periodically review and manage the events list using Prime Network
Events. In addition, when an event occurs in the Prime Network system, the details become available in
Prime Network Events.
All administrator activities in Prime Network Administration are logged and available in Prime Network
Events. For more information on Prime Network Administration, see the Cisco Prime Network 3.8
Administrator Guide.
The following topics describe the user access roles required to use Cisco Prime Network Vision (Prime
Network Vision), the Prime Network Vision working environment, and how to access the Prime Network
Vision tools and commands:
• User Roles Required to Work with Prime Network Vision, page 2-1
• Launching Prime Network Vision, page 2-2
• Prime Network Vision Window, page 2-4
• Prime Network Vision Status Indicators, page 2-26
• Prime Network Vision Toolbar, page 2-32
• Prime Network Vision Menu Bar, page 2-35
• Prime Network Vision Right-Click Menus, page 2-40
• Changing a User Password in Prime Network Vision, page 2-51
• Selecting Prime Network Vision Options, page 2-51
• Working with Prime Network Tables, page 2-53
Table 2-1 Default Permission/Security Level Required for Prime Network Vision Functions
Note If you do not log into Prime Network Administration, Prime Network Vision, or Prime Network Events
during a specified period of time (the default is one month) from the standalone application, your
account is automatically locked. The default period can be changed per user in Prime Network
Administration. The period of time is measured from the time you last logged out of any of the Prime
Network client applications. For more information about changing the default period and unlocking an
account, see the Cisco Prime Network 3.8 Administrator Guide.
For more information about using Prime Network Vision with the Prime Central suite of products, see:
• Cisco Prime Central 1.0 User Guide
• Prime Network Vision Right-Click Menus, page 2-40
Step 1 Choose Start > Programs > Cisco Prime Network > gateway hostname/IP address > Cisco Prime
Network Vision.
Note The hostname/IP address corresponds to the gateway on which Prime Network was configured.
After logging into Prime Network Vision and launching the application, you can customize the Prime
Network Vision settings. For example, you can:
• Load the content pane with information when starting Prime Network Vision.
• Display network elements in the Prime Network Vision content pane and navigation pane.
• Configure audio responses when different alarms are triggered.
• Specify the length of time that events should be displayed in the inventory window.
For more information on customizing Prime Network Vision startup and display options, see Selecting
Prime Network Vision Options, page 2-51.
The Prime Network Vision window can display either inventory tabs or maps. For more information, see
the following topics:
• Prime Network Vision Inventory Tabs, page 2-5
• Prime Network Vision Maps, page 2-7
Tip The ticket pane can be displayed or hidden by clicking the arrows below the navigation pane (see Callout
7 in Figure 2-1).
The status bar at the bottom of the window provides information about the current connection status for
the view. The status bar also displays information about the command that was sent while the application
waits for an answer.
The memory utilization bar in the status bar displays the amount of memory used by the client. By
default, if memory utilization exceeds 60%, it is colored yellow, and if it exceeds 80%, it is colored red.
Dragging the borders of the Prime Network Vision window adjusts the size of each pane. The navigation
pane and content pane are correlated; this means that selecting an option in the navigation pane affects
the information displayed in the content pane.
• Ethernet Flow Domains—Lists all Ethernet flow domains, including the domain name, the
system-defined domain name, and a brief description for each domain. For more information about
Ethernet flow domains, see Viewing and Renaming Ethernet Flow Domains, page 12-39.
• VTP Domains—Lists all VTP domains. For more information about VTP domains, see Viewing
VLAN Trunk Group Properties, page 12-65.
The inventory tabs display the network inventory icon and name. If a tab is selected, it also displays an
X for closing the tab. To close a tab that is not selected, place your cursor over that tab and click the X
once it appears.
Function Description
Filter Click Filter in the table toolbar and specify filter criteria.
For more information, see Filtering Table Contents, page 2-57.
Scroll If the number of entries exceeds the current viewing area, use your mouse
scroll wheel to move up and down through the table.
Search This option is available only for the Network Elements tab.
To search for specific elements:
1. Click Search.
2. In the drop-down list, select the category to search.
3. In the search field, enter the string to search for.
4. Click Go.
Sort To sort:
• By a single column, click the column heading. Click the heading again
to sort in the reverse order.
• Using multiple sort criteria, click Sort Table Values in the toolbar and
select the required criteria.
For more information, see Sorting a Table, page 2-55.
Opening Maps
You can open an existing map in any of the following ways:
• In the menu bar, choose File > Open Map.
• In the toolbar, click Open Map.
• In the Network Elements tab, right-click the required element and choose Open Relevant Maps.
• In either the navigation pane or content pane, right-click the required element and choose Open
Relevant Maps.
The Open Map dialog box is displayed (see Figure 2-3).
Depending on the method you use to open this dialog box, the Open Map dialog box lists either all maps
or only those maps that contain the selected network element.
A check mark in the Opened column indicates that the map is already open.
Select the required maps and click OK.
Map tabs display the root node icon and name.
In addition, the icon color reflects the highest severity ticket that is not cleared in the map, and an alarm
icon indicates the severity of the highest severity ticket that is not acknowledged. If a tab is selected, it
also displays an X for closing the tab. To close a tab that is not selected, place your cursor over that tab
and click the X once it appears.
For more information about maps, see Working with Prime Network Vision Maps, page 4-1.
Navigation Pane
The navigation pane displays a tree-and-branch representation of the network elements and aggregations
defined for the loaded map.
The highest level in the navigation tree displays root node icon with the map name. When the map name
is changed, the Prime Network Vision window is updated, and the new map name is displayed at the top
of the navigation tree and in the window title bar.
The lowest level of the navigation tree displays a single network element or service, such as a port,
Ethernet flow point, or bridge.
The navigation pane can include up to two icons for each element. These icons can include alarm icons,
communication or investigation state icons, and badges, as shown in Figure 2-4. Alarm icons are always
displayed next to the element icon.
For information about the status of network objects, see Prime Network Vision Status Indicators,
page 2-26.
Map View
Click Show Map View on the toolbar to display the map view in the Prime Network Vision window.
In the map view, Prime Network Vision displays:
• Aggregations
• Managed network elements
– Each network element is displayed as an icon, the color of which reflects severity, as described
in Alarm Indicators, page 2-17.
– Depending on the size of the icon, additional information can be displayed. For more
information, see Information Available in Element Icons, page 3-3.
• Ethernet flow point cross-connects
• Ethernet services
• MPLS-TP tunnels
• Pseudowires
• VLANs
• VPLS instances
• VPNs
• Links
– Service and business links are represented as well as physical and topological links.
– Unidirectional links include arrowheads that indicate the direction of the flow, while
bidirectional links do not have arrowheads.
• Relationships between network elements, aggregations, and networks
The map view enables you to view network objects down to the device level. An example of the map
view is displayed in Figure 2-1.
You can move network elements manually on the map by dragging the required icon. You can also click
Layout Map in the toolbar or use your mouse to change the way the elements are displayed on the map.
For more information about working with maps, see Chapter 4, “Working with Prime Network Vision
Maps.”
Element Icons
Normal
• Displays the element as an icon with the element name below
the icon.
• Alarm severities are indicated by badge, element icon
outline, and link colors.
ATM switch
Cloud
Ethernet switch
ICMP device
WiFi element
Note When Prime Network Vision detects a network element for which it does not have enough information
available, Prime Network Vision displays as a ghost element on the map. When this occurs, you cannot
view the ghost element properties or communicate with it. When the information for the ghost element
becomes available, Prime Network Vision replaces its icon with the relevant element icon, and updates
the related element and communication information.
Ethernet service
Network VLAN
Subnet
Switching entity
TP tunnel endpoint
VPLS forward
VPLS instance
VPN
Links
Prime Network Vision maps contain graphical links that can represent multiple physical, topological,
service, and business links.
The maximum number of graphical links that can be displayed is specified in the registry. If the number
of graphical links exceeds the specified limit, a warning message with a Refresh button is displayed, and
the map is surrounded by a red border. The presence of a red border around a map indicates that some
links exist that are not displayed in the map.
Note Changes to the registry should only be carried out with the support of Cisco. For details, contact
your Cisco account representative.
Links in maps have tooltips that provide you with information regarding the link endpoints and the
number of links represented by the selected link in the map. Click the link tooltip to view additional
information about the link in a link quick view window. Click Properties in the link quick view window
to open the link properties window. For more information about viewing link properties, see Viewing
Link Properties in Prime Network Vision Maps, page 5-4.
Note If you apply a link filter to the map, the link tooltip displays only the relevant links.
Alarm Indicators
Table 2-6 shows the colors that are used to display the severity (or propagated severity) of a network
element in the navigation, content, and ticket panes.
Orange Major
Yellow Minor
The same coloring conventions apply to the link severities displayed in the map view, links view, and
link quick view.
Note The color of a selected link can be customized. The default color is blue.
When you select an aggregation in the navigation tree, you can view the elements that belong to that
aggregation in the map pane by either double-clicking its icon or clicking the plus sign in the upper right
corner of its icon.
For more information about how the status of a network element is displayed in a map, see Prime
Network Vision Status Indicators, page 2-26.
Right-Click Functions
Many functions can be performed by using the right-click menu in the map view, including launching
external applications or tools. Some of these functions are also available in the navigation pane, links
view, and ticket pane.
The specific options that are available in the right-click menu depend on whether you select a network
element, click in the map background, select an aggregation, or select a ticket in the ticket pane. For
details on the specific right-click options that are available for each scenario, see Prime Network Vision
Right-Click Menus, page 2-40.
List View
Click Show List View in the toolbar to display the Prime Network Vision list view. The list view displays
the tabs described in Table 2-7, depending on the items included in the current map and the item selected
in the navigation tree.
Tab Description
Aggregations Aggregations in the current map.
Connection TP Connection termination points (TPs) in the current map.
EFP Cross-Connect EFP cross-connects in the current map.
Ethernet Flow Points EFPs in the current map.
Ethernet Services Ethernet services in the current map.
EVCs EVCs in the current map.
Network Elements Network elements in the current map that are in the user’s scope.
Network Pseudowire Network pseudowires in the current map.
Tab Description
Network TP Tunnel Network Traffic Profile (TP) tunnels in the current map.
Pseudowires Pseudowires in the current map.
Pseudowire Edge Pseudowire endpoints in the current map.
PW Switching Entity Pseudowire switching entities in the current map.
Restricted Elements Network elements in the current map that are not in the user’s scope.
Sites Sites for the selected VLAN. Site properties include site name, description,
location, and IP interface.
Switching Entities Switching entities in the current map.
Virtual Routers Virtual routers on the selected VLAN. Virtual router properties include the
virtual router name and description.
VLANs VLANs in the current map. VLAN properties include VLAN name,
identifier, description, and Ethernet flow points.
VPLS Forward VPLS forwards in the current map.
VPLS Instance VPLS instances in the current map.
VPNs VPNs in the current map. VPN properties include VPN name and description
Table 2-8 describes the network element properties displayed in the Network Elements tab. (Locked
network elements display only managed element information and the locked element icon.) To ensure
that you are viewing the latest information, either perform a new search or click the Refresh button.
Tip Click the red triangle in a cell to expand the cell and view all the information it contains. You can also
use a tooltip to view all the information.
Table 2-9 identifies the buttons that are displayed in the list view toolbar.
Show All Rows Displays all table rows that meet the current
filtering criteria.
Show Only Selected Displays only the rows that you select.
Rows
For more information, see Viewing Selected
Rows, page 2-58.
See Working with Prime Network Tables, page 2-53 for more information about filtering, finding details
about a network element in Prime Network Vision tables, and keyboard shortcuts available for accessing
table functionality.
Table 2-10 describes some of the functions that are available from the right-click menu in the list view.
You must select an item for the right-click menu to appear. Not all options are available for all selections.
Tip Click a column heading in a table to sort the information by that property.
Links View
Click Show Links View in the toolbar to display the links view in the Prime Network Vision window.
Maps can contain many graphical links, each of which can represent multiple physical, topological,
service, and business links. This can make it difficult for you to view the links you are interested in. In
addition, if the number of graphical links exceeds the number that can be displayed in a map, not all links
are displayed. By using the links view, you can view all links in the map, as well as search for a specific
link and view the status of a link.
Note You can view and filter the links according to type by using the Link Filter dialog box. For more
information, see Filtering Links in a Map, page 4-38.
Any links that are added or removed from the map are automatically added or removed from the links
view, provided they have not been filtered out.
The links view is selection sensitive; that is, the links displayed in the links view depend on the context
selected in the navigation pane or map. For example, if an aggregation is selected, the links in the
selected aggregation are displayed in the links view.
Figure 2-5 shows a links view.
Note An external link has a blue cell background in the table, and you can open the inventory window by
clicking the hyperlink. For more information about external links, see Viewing Link Properties in the
Links View, page 5-8.
Table 2-11 describes the information that is displayed in the links view.
Note Clicking a column heading in the links view sorts the information by that header value.
The links view toolbar includes the tools described in Table 2-9 and the link filtering buttons described
in Table 2-12.
Deep Links Displays the links for the current aggregation where both endpoints are
within the currently selected context.
For more information about filtering and sorting links in the links view, see Viewing Link Properties in
the Links View, page 5-8.
For information about the right-click options available in the links view, see Links View Right-Click
Menu, page 2-49.
Ticket Pane
When Prime Network Vision detects faulty behavior in the network, the VNEs and their internal device
components initiate an internal, end-to-end message flow, resulting in the full understanding and
containment of the fault across all relevant network elements and network layers.
The ticket pane enables you to view and manage tickets as well as identify elements or links that are
affected by a ticket. All the tickets that are reported by Prime Network are stored in the Prime Network
gateway database.
The ticket pane is displayed beneath the navigation and content panes in the Prime Network Vision
window. You can view or hide the ticket pane by clicking the arrows displayed below the navigation
pane.
A ticket represents the complete hierarchy of correlated alarms representing a single specific fault
scenario. A ticket points to the root cause alarm that is the top-most alarm in the correlation hierarchy.
Examples of alarms are Link Down, Device Unreachable, or Module Out. Some event types are capable
of creating tickets. When an event is generated, it is correlated to an existing event, which is correlated
to a ticket. If there is no existing ticket, a new ticket is created.
Note For information on managing tickets, see Chapter 9, “Working with Tickets in Cisco Prime Network
Vision.”
Prime Network identifies the relationship between a root cause alarm and its consequent alarms. It
automatically correlates the consequent alarms as children of the root alarm. The ticket pane displays
the ticket (the root cause alarm), the aggregated severity of the ticket, and the severity of the root cause
alarm. In addition, the ticket pane displays the time at which the original event was detected, the ticket
creation time, and a description of the event that caused the ticket creation.
The Ticket Properties window enables you to view all correlated alarms.
Note The root cause alarm severity is the top-most severity of its contained alarms.
Table 2-13 describes the functions that are available from the ticket pane.
The ticket details in the ticket pane change automatically as new information arrives. For example, Port
Down is updated to Port Up.
By default, the tickets in the ticket pane are sorted according to the last modification time. For
information about tickets, see Chapter 9, “Working with Tickets in Cisco Prime Network Vision.”
The Find field enables you to search for information in the ticket pane table according to the selected
column. For more information about the buttons displayed in Prime Network Vision tables and table
functionality, see Working with Prime Network Tables, page 2-53.
The Location bar below the table displays:
• The location of the selected rows in the table; for example, Line 3.
• The number of selected rows and the total number of rows in the table; for example, 2/16 Selected.
For more information about network element status indicators, see Prime Network Vision Status
Indicators, page 2-26.
Severity
Severity indicates the operational health of the element. An element has only one severity value at any
given time, and this value is displayed using a severity color. For more information about the colors used
to display the severity (or propagated severity) of network elements and links, see Alarm Indicators,
page 2-17.
Propagation
Severity is propagated upward in the network hierarchy, displaying the top-most severity of the network
element’s children and thereby ensuring that every single problem in the network is propagated and
visible.
The same severity propagation rules that are used for network elements apply to links. A link is a child
object of an aggregation only if it is fully contained in the aggregation; that is, the network elements on
both sides of the link are part of the aggregation, as shown in Figure 2-6 and Figure 2-7.
1 2
180111
Figure 2-6 shows critical link 1 between two network elements in an aggregation. This critical link
affects the severity of aggregation 2. That is, the aggregation is critical because it contains a link with a
critical severity. Link severity affects the context.
2
180112
Figure 2-7 shows critical link 1 that forms part of a link aggregation. This affects the severity of link 2
because it contains a link with a critical severity.
When new tickets are accumulated, a label is displayed in the navigation pane and map, based on the
following formula:
n s [+]
where:
Symbol Description
n The number of tickets with the highest severity in the new ticket count.
s The highest severity level in the new tickets:
• C = Critical
• M = Major
• m = Minor
• W = Warning
• N = Normal (cleared alarm)
• i = Informational
+ Additional, less severe tickets (optional) exist.
For example:
• An object with three critical new alarms, two major alarms, and one warning alarm is labeled 3C+.
• An object with five minor new alarms is labeled 5m.
An icon represents unacknowledged tickets, and the icon color is that of the most severe,
unacknowledged ticket. For more information about severity colors and icons, see Alarm Indicators,
page 2-17.
If all relevant tickets are acknowledged, no bell is displayed.
A managed VNE icon consists of a managed element icon and one or two overlay icons, or badges:
• The managed element icon displays a symbol of the element, and the color of the symbol indicates
the highest severity ticket that is not cleared for the element.
An element icon is colored green if either of the following is true:
– No ticket of any severity exists for the element.
– All tickets that exist for the element have the severity Cleared or Informational.
For more information about network element icons, see Element Icons, page 2-11. For more
information about severity colors, see Alarm Indicators, page 2-17.
• An alarm badge is displayed on top of a managed element icon, and the color of the alarm badge
indicates the severity of the highest severity ticket that is not acknowledged for the element. If all
tickets are acknowledged, no alarm icon appears.
Figure 2-8 shows an example of an element with the following ticket and alarm severities:
– The highest severity ticket that is not cleared for the element is Major, as indicated by the orange
color applied to the element icon.
– The highest severity alarm that is not acknowledged for the element is Cleared or OK, as
indicated by the green alarm badge.
• A VNE management state badge is displayed on top of the managed element icon to indicate the
management state of the VNE in the navigation tree and map. For example, a router that is partially
reachable by Prime Network Vision is displayed as illustrated in Figure 2-9.
2
310517
Table 2-15 and Table 2-16 describe network element communication and investigation states and shows
the related badge for each state.
More than one management state can occur at the same time. For example, a single overlay icon can be
displayed, reflecting the device status based on the following priorities: Unsupported > Discovering >
VNE/Agent Unreachable > Device Unreachable > Partially Discovered > Operational.
For more information about each of these states and how to troubleshoot any issues, see the Cisco Prime
Network 3.8 Administrator Guide.
Tickets
Cisco Prime Network Vision displays an icon with a ticket to indicate the severity of the top-most alarm
on the ticket. The icons are the same as those used with network elements (see Table 2-6) and are
displayed in Cisco Prime Network Vision as follows:
Note The functionality that a user can access in Prime Network Vision depends on the user role and the
security level of the scopes assigned to the user. For more information, see User Roles Required for
Working with Prime Network Vision Maps, page 4-2.
Table 2-17 identifies the toolbar buttons and describes the functions that are available in the Prime
Network Vision toolbar.
Open Map Opens a map saved in the database using the Open dialog box.
Add to Map Adds an element to the map or to the subnetwork selected in the
navigation pane and displayed in the content pane.
Save Map Saves the current map (the background and the location of devices)
Appearance to the database.
Show List View Displays the list view in the Prime Network Vision content pane (the
button toggles when selected or deselected).
Show Links View Displays the links view in the Prime Network Vision content pane
(the button toggles when selected or deselected).
Overlay Tools
Choose Overlay Chooses and displays an overlay of a specific type on top of the
Type elements displayed in the content pane in a map view.
Available overlay options are:
• Ethernet Service
• MPLS-TP Tunnel
• Network Clock
• Pseudowire
• VLAN
• VPLS
• VPN
• None—Removes the existing overlays.
Show Overlay / Displays or hides a previously defined overlay on top of the
Hide Overlay elements displayed in the map view.
Note Overlays do not reflect changes that occur in the selected
service. As a result, the information in an overlay can
become stale.
Refresh Overlay Refreshes the overlay that was last selected.
Viewing Tools
Go to Parent Moves up one level in the navigation pane and content pane so you
can view different information.
Link Filter Opens the Link Filter dialog box, enabling you to display or hide
different types of links in the map and links views.
If a link filter is applied to the map, the Link Filter Applied button
is displayed instead.
Link Filter Applied Indicates a link filter is currently applied to the map and opens the
Link Filter dialog box so you can remove or modify the existing link
filter.
If no link filter is applied to the map, the Link Filter button is
displayed instead.
Find Business Tag Opens the Find Business Tag dialog box, enabling you to find and
delete a business tag according to name, key, or type.
Search Tools
Find Previous Finds the previous instance of the search string entered in the Find
in Map dialog box.
Find Opens the Find in Map dialog box, enabling you to find an element
in the map by its name or IP address.
Find Next Finds the next instance of the search string entered in the Find in
Map dialog box.
Zoom Selection Activates the zoom selection mode, which enables you to zoom in
Mode on a section of the map by clicking and dragging the required area.
Pan Mode Activates the pan mode, which enables you to view different areas
of the map by clicking and dragging the map.
Application-Specific Tools
Open Activation Displayed if Prime Network Activation is installed with Prime
Network.
Opens the Activation dialog box.
For more information, see the Cisco Prime Network 3.8 Activation
User Guide.
Activation History Displayed if Prime Network Activation is installed with Prime
Network.
Opens the Activation History dialog box.
For more information, see the Cisco Prime Network 3.8 Activation
User Guide.
Note The functionality that a user can access in Prime Network Vision depends on the user role and the
security level of the scopes assigned to the user. For more information, see User Roles Required for
Working with Prime Network Vision Maps, page 4-2.
Note The menus are context-sensitive and the options vary depending on your selection in the application.
File Menu
Table 2-18 describes the options that are available in the Prime Network Vision File menu. For more
information, see Chapter 4, “Working with Prime Network Vision Maps.”
Edit Menu
Table 2-19 identifies the options available in the Prime Network Vision Edit menu. For more
information, see Chapter 4, “Working with Prime Network Vision Maps.”
View Menu
Table 2-20 identifies the options available in the Prime Network Vision View menu. For more
information, see Using the Overview Window, page 4-19.
Node Menu
Table 2-21 describes the Node menu options.
Note Most of the functionality available in this menu is available only when an element icon or an aggregation
is selected in the navigation pane or a map.
Tools Menu
Table 2-22 describes the Tools menu options.
Activation Menu
The Activation menu is displayed if the Prime Network Activation application is installed with Prime
Network.
See the Cisco Prime Network 3.8 Activation User Guide for more information about any of the options
in this menu.
Table 2-23 describes the Activation menu options.
Network Inventory
Menu Option Description
Network Elements Displays a list of the available network elements in the Network Elements tab.
For more information, see Prime Network Vision Inventory Tabs, page 2-5.
Ethernet Flow Displays a list of the current Ethernet flow domains in the Ethernet Flow
Domains Domains tab. For more information, see Viewing and Renaming Ethernet Flow
Domains, page 12-39
VTP Domains Displays a list of the current of the VLAN Trunk Protocol (VTP) domains in the
VTP Domains tab. For more information, see Viewing VLAN Trunk Group
Properties, page 12-65.
Reports Menu
Table 2-25 describes the Reports menu options.
For more information about Report Manager and reports, see Chapter 10, “Working with Reports.”
Window Menu
The Prime Network Vision Window menu lists all maps open in the Prime Network Vision content pane,
enabling you to move between the maps. The menu also lists any network element inventory tabs that
are open.
Help Menu
Table 2-26 describes the Help menu options.
See the following topics for the default options available in Prime Network Vision right-click menus:
• Map Right-Click Menu, page 2-41
• Element Right-Click Menu, page 2-41
• Aggregation Right-Click Menu, page 2-45
• Link Right-Click Menu, page 2-46
• List View Right-Click Menu, page 2-46
• Links View Right-Click Menu, page 2-49
• Ticket Right-Click Menu, page 2-50
Option Description
Go to Parent Moves up one level in the navigation pane and content pane to enable you to view
different information.
Go to Root Moves to the root level in the navigation pane and content pane to enable you to
view different information.
Set Map Displays a background image for the map in the content pane. For more
Background information, see Applying a Background Image, page 4-17.
Note The element right-click menu is context-sensitive and the options vary depending on your selection in
the application. Also, some options might not be available if multiple elements are selected.
Table 2-28 describes the options available in the element right-click menu.
Option Description
Add Associated VLAN Opens the Add Associated VLAN dialog box so that you can add an
associated VLAN to the selected VLAN. For more information, see Adding
an Associated VLAN, page 12-52.
Aggregate Groups the selected devices into an aggregation in the Prime Network Vision
content pane, and enables you to define a name for the new aggregation. For
more information, see Chapter 4, “Working with Prime Network Vision
Maps.”
Note You cannot aggregate service entities that exist within services. For
example, you cannot aggregate VRFs that exist in a VLAN.
Attach / Detach / Edit Allows you to perform the following actions:
Business Tag • Attach a business tag to the selected network element.
• Detach a business tag from a network element.
• Edit a business tag for a network element.
Note The Detach and Edit options are displayed only when a business tag
is attached to a network element.
For more information, see Chapter 6, “Working with Business Tags and
Business Elements.”
Commands Enables you to launch any of the commands that are included with Prime
Network Vision.
For more information on the available commands and how to implement
them, see the “Using the Prime Network Basic Operation Commands”
chapter in the Cisco Prime Network 3.8 Reference Guide.
Config Mgmnt This option is available only if Prime Network Change and Configuration
Management is installed.
Displays the Configuration Management page for the selected device in
Prime Network Change and Configuration Management.
For more information, see the Cisco Prime Network 3.8 Change and
Configuration Management User and Administration Guide.
Delete Deletes the selected item from the map.
Disaggregate Ungroups the devices in the selected aggregation in the navigation and map
panes. For more information, see Chapter 4, “Working with Prime Network
Vision Maps.”
Note This option is available only when an aggregation is selected in the
navigation pane or map.
Edit Move the selected virtual router to the location you specify.
Filter Tickets Displays only those tickets that have the selected VNE as the root cause.
This option is available only for VNEs that have not been deleted by Prime
Network Administration.
Hide Connected Hides the devices for sites with one or more connected devices.
Devices
Option Description
Image Mgmnt This option is available only if Prime Network Change and Configuration
Management is installed.
Displays the Image Management page for the selected device in Prime
Network Change and Configuration Management.
For more information, see the Cisco Prime Network 3.8 Change and
Configuration Management User and Administration Guide.
Inventory Displays a window enabling you to view the physical and logical inventory.
For physical inventory, you can view all the components of the device, such
as the modules, ports, and its IP address or configured VLANs. In addition,
you can view the status of each component. For logical inventory, you can
view all the profiles and VC tables of the device. For more information, see
Chapter 3, “Viewing Network Element Properties.”
Launch external Starts an external application or tool that has been configured for access via
applications the right-click menu. For more information, see the Cisco Prime Network 3.8
Customization User Guide.
Management Contains the following submenu options:
• Command Builder—Defines commands and scripts using the Prime
Network Command Builder tool (Configurator security level required).
• Soft Properties Management—Extends VNEs by adding SNMP MIB or
Telnet/SHH/TL-1 properties to the device’s collected information model
using the Prime Network Soft Properties Manager (Administrator
security level required).
For more information about Command Builder and Soft Properties Manager,
see the Cisco Prime Network 3.8 Customization User Guide.
Modify Displays the Modify dialog box so that you can change the selected item’s
name, description, or icon.
Open Relevant Maps Displays the Open Map dialog box so that you can view and open maps that
contain the selected element.
PathTracer Launches a path trace from the selected item.
Poll Now Polls the selected element.
Properties Displays the properties of the selected item, such as the IP address and
system name. In addition, you can open the VNE Properties dialog box and
manage VNE properties. For more information, see Chapter 3, “Viewing
Network Element Properties.”
Remove from Map Removes the selected device and all its children from the map (navigation
pane and content pane). The device that has been removed is still maintained
in the network.
Rename Renames the selected item.
Resize Enables you to resize an object on the map by percentage or size.
Run Report Enables you to run standard or user-defined events, inventory, and network
service reports on demand.
Option Description
Save as New Map Creates a new map and places the selected aggregation as the root, while
leaving the original map intact.
Script names Launches available activation and configuration scripts, including those you
create using Command Builder (can be launched against multiple network
elements). For more information, see the Cisco Prime Network 3.8
Customization User Guide.
Show as Aggregation / Displays the selected aggregation as a single entity or as a collection of
Thumbnail items.
The options toggle, depending on whether the aggregation is in a thumbnail
or aggregated view.
Show CE Device Displays devices for sites or LCPs with one or more hidden, connected
devices.
Tools The Tools option contains the following choices:
• CPU Usage—Displays memory and CPU usage information for a device
or network element.
• Ping—Pings the device from the client station.
• Telnet—Communicates with the device using the Telnet window from
the client station.
Note If you are using a Windows 7 system and want to use the Prime
Network Telnet option, you need to set up Telnet on the Windows 7
system as follows:
Option Description
Topology The Topology option enables you to add:
• A static link between two devices.
• A static topology between a device and an unmanaged network.
• A tunnel to a VPN.
When working with static links, the following submenu options enable you
to define the A Side and Z Side of the link:
• Mark as A Side
• Mark as Z Side
When working with VPNs in VPN Service View, the Add Tunnel submenu
option allows you define and configure tunnels.
VNE Tools Contains the following submenu options:
• Poll Now—Updates the VNE information.
• Stop VNE—Stops the VNE.
• Start VNE—Starts the VNE.
For more information, see Chapter 3, “Viewing Network Element
Properties.”
Option Description
Aggregate Groups the selected aggregations into an aggregation in the Prime Network
Vision content pane, and enables you to define a name for the new aggregation.
For more information, see Chapter 4, “Working with Prime Network Vision
Maps.”
Disaggregate Ungroups the selected aggregation in the navigation pane and map in the Prime
Network Vision window. All the aggregations in the selected node move up one
level, and the original aggregation is removed. For more information, see
Chapter 4, “Working with Prime Network Vision Maps.”
Rename Renames the selected aggregation.
Resize Defines the size of selected aggregations in a map according to one of four sizes
or according to a percentage of the current size.
Remove from Map Removes the selected aggregation and all its children from the navigation pane
and the map.
Save as New Map Creates a new map and places the selected aggregation as the root, while leaving
the original map intact.
Option Description
Run Report Enables you to run standard or user-defined events, inventory, and network
service reports.
Show as Displays the aggregation as a single entity or as a collection of items.
Aggregation /
The options toggle, depending on whether the aggregation is in a thumbnail or
Thumbnail
aggregated view.
Delete Deletes the selected item.
This option is available when the item is marked with the reconciliation icon.
Option Description
Properties Displays the properties of the selected link.
Table 2-31 List View Right-Click Menu Options - Network Elements Tab
Option Description
Inventory Displays a window enabling you to view the physical and logical inventory.
For physical inventory, you can view all the components of the device, such
as the modules, ports, and its IP address or configured VLANs. In addition,
you can view the status of each component. For logical inventory, you can
view all the profiles and VC tables of the device. For more information, see
Chapter 3, “Viewing Network Element Properties.”
Attach / Detach / Allows you to perform the following actions:
Edit Business Tag
• Attach a business tag to the selected element.
• Remove a business tag from the selected element.
• Edit an existing business tag for the selected element.
Note The Detach and Edit options are available only when a business tag
is attached to a link.
For more information, see Chapter 6, “Working with Business Tags and
Business Elements.”
Config Mgmnt Displays the Configuration Management page for the selected device in
Prime Network Change and Configuration Management.
For more information, see the Cisco Prime Network 3.8 Change and
Configuration Management User and Administration Guide.
Image Mgmnt Displays the Image Management page for the selected device in Prime
Network Change and Configuration Management.
For more information, see the Cisco Prime Network 3.8 Change and
Configuration Management User and Administration Guide.
Run Report Enables you to run standard or user-defined events, inventory, and network
service reports.
Show Only Displays only the rows that you select.
Selected Rows
For more information, see Viewing Selected Rows, page 2-58.
Show All Rows Displays all table rows that meet the current filtering criteria.
Table 2-31 List View Right-Click Menu Options - Network Elements Tab (continued)
Option Description
Tools Contains the following submenu options:
• CPU Usage—Displays memory and CPU usage information for a device
or network element.
• Ping—Pings the device from the client station.
• Telnet—Communicates with the device using the Telnet window from
the client station.
Note If you are using a Windows 7 system and want to use the Prime
Network Telnet option, you need to set up Telnet on the Windows 7
system as follows:
Table 2-31 List View Right-Click Menu Options - Network Elements Tab (continued)
Option Description
Management Contains the following submenu options:
• Command Builder—Defines commands and scripts using the Prime
Network Command Builder tool (Configurator security level required).
• Soft Properties Management—Extends VNEs by adding SNMP MIB or
Telnet/SHH/TL-1 properties to the device’s collected information model
using the Prime Network Soft Properties Manager (Administrator
security level required).
For more information about Command Builder and Soft Properties Manager,
see the Cisco Prime Network 3.8 Customization User Guide.
VNE Tools Contains the following submenu options:
• Poll Now—Updates the VNE information.
• Stop VNE—Stops the VNE.
• Start VNE—Starts the VNE.
For more information, see Chapter 3, “Viewing Network Element
Properties.”
Option Description
Attach Business Attaches a business tag to the selected link. For more information, see Chapter 6,
Tag “Working with Business Tags and Business Elements.”
Detach/Edit Detaches or edits a business tag from the selected link. For more information, see
Business Tag Chapter 6, “Working with Business Tags and Business Elements.”
The Detach and Edit options are available only when a business tag is attached
to a link.
Select Link in Map Highlights the selected link in the content pane.
Show Only Displays only the rows that you select.
Selected Rows
For more information, see Viewing Selected Rows, page 2-58.
Show All Rows Displays all table rows that meet the current filtering criteria.
Properties Displays the properties of the selected link.
Option Description
Acknowledge Acknowledges that the ticket is being handled; the ticket is displayed as true in
the ticket pane. Acknowledging an alarm removes the alarm icon from the device
icon. Multiple tickets can be acknowledged at the same time.
Clear Approves the reported faulty ticket and clears the faulty networking entity from
Prime Network. The ticket is displayed as Clear in the ticket pane.
Note When a Card Out or Link Down alarm occurs, the relevant information is
displayed in the inventory and maintained in the VNE.
Remove Removes the ticket and all its active subtickets from the ticket pane (this option
is only available after the ticket has been cleared). The deleted tickets can be
viewed using Cisco Prime Network Events. Multiple tickets can be removed at
the same time.
Note When a ticket is removed, the information is no longer displayed in the
inventory and is removed from the VNE.
Clear and Remove Approves the reported faulty ticket and clears the faulty networking entity from
Prime Network. In addition, the ticket and all its active subtickets are removed
from the ticket pane.
Find Affected Finds any elements affected by the selected ticket:
Elements
• If only one element is affected, it is selected in the Prime Network navigation
pane and content area.
• If multiple elements are affected, they are displayed in the Affected
Elements window.
Show Only Displays only the rows that you select.
Selected Rows
For more information, see Viewing Selected Rows, page 2-58.
Show All Rows Displays all table rows that meet the current filtering criteria.
Properties Displays the Ticket Properties dialog box, enabling you to view ticket
information, including impact analysis details of the affected parties and
correlated alarms. See Viewing Ticket Properties, page 9-10.
Step 1 Choose Tools > Change User Password. The Change User Password dialog box is displayed.
Note If Prime Network uses an LDAP server for authentication, the Change User Password option is
dimmed. Contact your administrator to change your password on the LDAP server.
Step 3 Click the Display tab. Set the display options using the information in Table 2-34.
Field Description
Preferences
Map Labels Font Size In the drop-down list, choose the preferred font size for labels on maps.
Font sizes are 26, 28, 30, 32, and 34, with a default of 30.
Severity
Show Severity Text Check the check box to view severity labels in the navigation pane and
(e.g. [3M+] maps, using the formula described in New Ticket Propagation,
page 2-27.
Uncheck the check box to hide severity labels.
Show Acknowledged Check the check box to view the number of both acknowledged and
unacknowledged alarms in the network element display name.
Uncheck the check box to view only the number of unacknowledged
alarms in the network element display name.
For example, assume that device NE1 has two alarms with the severity
M. One of these two alarms is acknowledged, and the other is not. If
you check the Show Acknowledged check box, the display name will
be NE1 [2M]. If you uncheck the Show Acknowledged check box, the
display name will be NE1 [1M].
Show Propagated Check the check box to view propagated alarms on the specific entity.
Uncheck the check box to view only the alarms on the specific entity.
Display Name
Display Name Select the preferred setting for network element names:
• Do not use Business Tag—Displays the original network element
name only.
• Add Business Tag to name—Displays the original network element
name and the name of the business tag.
• Replace name with Business Tag—Replaces the network element
name with the business tag name. When a subscriber is attached to
a port, the subscriber name is also added.
Step 4 Click the Audio tab and select your preferences for audio notifications using the information in
Table 2-35.
Field Description
Enable Audio Response for Alarm Select the preferred setting for audio notifications:
• To indicate that a sound is to be issued when an alarm is
triggered, check the check box.
• To prevent a sound from being issued when an alarm is
triggered, uncheck the check box.
If you uncheck the check box, continue with Step 6.
Critical Specify the .wav file to use for critical alarms.
Major Specify the .wav file to use for major alarms.
Minor Specify the .wav file to use for minor alarms.
Loop Sound on Critical Alarm Specify whether or not the critical alarm sound should sound
continuously when a critical alarm is triggered:
• To play the critical alarm sound continuously when a
critical alarm is triggered, check the check box.
• To play the critical alarm sound only once when a critical
alarm is triggered, uncheck the check box.
Step 5 Click the Events tab and, in the Events History Size in Hours field, enter the length of time in hours that
Cisco Prime Network Vision should use when determining the events to display in the Network Events
and Provisioning Events tab in the inventory window (see Ticket and Events Pane, page 3-18). If you
enter a value of 0 (zero), only active events are displayed in the Network Events tab in inventory. The
default value of six hours can be changed in Prime Network Administration.
Step 6 Click Apply to apply your selections.
Step 7 Click OK.
To view all text in a table cell, you can do either of the following:
• Click the red triangle in the cell to automatically expand the cell to the size of the cell’s contents.
• Hover your mouse cursor over the cell.
Show All Rows Displays all table rows that meet the current filtering
criteria.
Show Only Selected Displays only the rows that you select.
Rows
For more information, see Viewing Selected Rows,
page 2-58.
Step 1 In the Find field on the toolbar, enter the search criterion for the entity that you want to find and press
Enter.
Step 2 Press F3 to continue searching the table or press Ctrl + F to return to the Find field.
Sorting a Table
Prime Network Vision enables you to sort a table in the following ways:
• According to a column, by clicking the required column heading.
• In ascending or descending order, by clicking a column heading.
• By clicking Sort Table Values in the toolbar and specifying sort criteria.
A triangle next in the column heading indicates the sort order:
Step 1 In the table toolbar, click Sort Table Values. The Sort dialog box is displayed.
Step 2 In the Sort Operation field, specify the frequency of the sort operation:
• Only Once—Sorts the information in the table only once according to the specified criteria. When
this option is selected, newly added rows will always be listed at the bottom of the table, regardless
of their sort criteria value. Also, if an existing row's value changes, the row will remain where it is.
• Continuously/Repeatedly—Sorts the information in the table continuously according to the
specified criteria.
If you select this option, the icon is displayed next to the selected column heading.
Step 3 In the Sort By field, specify the first sort criterion:
a. In the first drop-down list, choose the column to use for the first sort criterion.
b. In the second drop-down list, choose Ascending or Descending to indicate the sort order.
Note If you load a table with many entries, (for example, thousands of entries), it can take a while for the
complete table to load. The filtering options in the table toolbar are unavailable until the table has
completely loaded.
The following changes in the GUI indicate that a filter has been applied:
• The Filter button is slightly shaded.
• The Clear Filter button is active.
• The filter details are displayed:
– In the status line below the table.
– When you hover the mouse cursor over the Filter button.
To define a filter:
Step 1 In the toolbar above the table, click Filter. The Filter dialog box is displayed as shown in Figure 2-11.
Step 2 In the Match drop-down list, choose the rule for including items that meet the specified criteria:
• All—All of the following criteria are to be met.
• Any—Any of the following criteria are to be met.
Step 3 For each criterion, specify the following information:
a. In the first drop-down list, choose the primary match category. The drop-down list contains all
columns in the current table.
b. In the second drop-down list, choose the rule to use for this criterion. The options are:
– Contains
– Does not contain
– Equals
– Does not equal
– Greater than
– Less than
c. The third field either lists the available values or allows you to enter text:
– If a drop-down list is displayed, choose the required entry.
– If an entry field is displayed, enter a string or regular expression for the criterion.
Any entry that is not a regular expression is treated as a string.
Tip You can use the “Greater than” or “Less than” rule with a string for filtering. For example, if you
want to include all interfaces above Ethernet0/0/3, you can select Greater than and enter the
string Ethernet0/0/3 to view interfaces Ethernet0/0/4, Ethernet0/0/5, and so on.
If no rows are selected, the value for the line defaults to 0, such as:
Line 0 (Size 6)
Step 1 Select the appropriate line or lines in the table using standard Windows mouse or keystroke operations.
Step 2 Click Show Only Selected Rows.
The table displays the selected rows, and the Show All Rows option becomes active.
Step 3 Click Show All Rows to view all rows in the table.
The following topics describe the user access roles required to use Cisco Prime Network Vision (Prime
Network Vision) and how to view network element physical and logical properties in any mapped
network:
• User Roles Required to Work with Prime Network Vision, page 3-2
• Information Available in Element Icons, page 3-3
• Viewing the Properties of a Network Element, page 3-5
• Viewing and Modifying VNE Properties, page 3-9
• Viewing VNE Communication Status, page 3-11
• Updating VNE Information, page 3-12
• Opening the Inventory Window, page 3-12
Note The inventory window also enables you to view all the tickets that are collected on the
selected element in the ticket and events pane. For more information, see Ticket and Events
Pane, page 3-18.
Note Prime Network Vision maintains continuous, real-time discovery of all the physical and logical entities
of the network inventory and the relationships among them. The Prime Network Vision distributed
system inventory automatically reflects every addition, deletion, and modification that occurs in the
network.
Table 3-1 Default Permission/Security Level Required for Prime Network Vision Functions - Element Not in User’s
Scope
Table 3-2 Default Permission/Security Level Required for Prime Network Vision Functions - Element in User’s Scope
Icon Size
Element Type Tiny (Dot) Normal Large Huge
Aggregation Color representing Name Name in card title Name in card title
the associated
alarm severity
Bridge Color representing Name • Name in card title and body • Name in card title and body
the associated • Number of Ethernet flow • Number of Ethernet flow
alarm severity points points
EFP cross-connect Color representing Name Name in card title Name in card title
the associated
alarm severity
Ethernet flow Color representing Name • Name in card title • Name in card title
point the associated
• Type, such as Trunk, Access, • Type, such as Trunk, Access,
alarm severity
Dot1Q Tunnel, and so on Dot1Q Tunnel, and so on
• Match criteria • Match criteria
Ethernet service Color representing Name • Name in card title • Name in card title
the associated
• Number of edge EFPs • Number of edge EFPs
alarm severity
Icon Size
Element Type Tiny (Dot) Normal Large Huge
EVC Color representing Name • Name in card title • Name in card title
the associated
• Number of instances of • Number of instances of
alarm severity
domains (VPLS, EoMPLS, domains (VPLS, EoMPLS,
bridge, or cross-connect) with bridge, or cross-connect) with
a maximum of three lines a maximum of four lines
LSP Endpoint Color representing Name • Name in card title • Name in card title
(Working or the associated
• Bandwidth • Bandwidth
Protected) alarm severity
• Attach Business Tag button
• Properties button
LSP Midpoint Color Name • Name in card title • Name in card title
• Forward bandwidth • Forward bandwidth
• Reverse bandwidth • Reverse bandwidth
• Reverse in and out labels • Reverse in and out labels
• Attach Business Tag button
• Inventory button
• Properties button
MPLS-TP Tunnel Color representing Name Name in card title and body • Name in card title and body
the associated
• Attach Business Tag button
alarm severity
• Properties button
MPLS-TP Tunnel Color representing Name • Name in card title and body • Name in card title and body
Endpoint the associated
• Tunnel identifier • Tunnel identifier
alarm severity
• Attach Business Tag button
• Inventory button
• Properties button
Network element Color representing Name • Name in card title • Name in card title
the associated
• Element model • Element model
alarm severity
• IP address • IP address
• Software version • Software version
• Inventory button
• Filter Tickets button
• Attach Business Tag button
Pseudowire Color representing Name Name in card title and body • Name in card title and body
the associated
• Attach Business Tag button
alarm severity
• Properties button
Icon Size
Element Type Tiny (Dot) Normal Large Huge
Pseudowire edge Color representing Name • Name in card title • Name in card title
the associated
• Local IP address • Local IP address
alarm severity
• Peer IP address • Peer IP address
• Attach Business Tag button
• Inventory button
• Properties button
VLAN Color representing Name Name in card title and body • Name in card title
the associated
• Name in card body
alarm severity
• Number of switching entities
• Number of edge EFPs
VPLS Color representing Name • Name in card title • Name in card title
the associated • Number of access EFPs • Number of access EFPs
alarm severity
• Number of access pseudowires • Number of access pseudowires
• Number of VPLS forwards • Number of VPLS forwards
VPLS Forward Color representing Name • Name in card title • Name in card title
the associated
• VPN identifier • VPN identifier
alarm severity
• Number of core pseudowires • Number of core pseudowires
VPN Color representing Name Name in card title and body • Name in card title and body
the associated
• Attach Business Tag button
alarm severity
• Properties button
Step 1 To view general information about a network element, do either of the following:
• Zoom in to view the required information:
1. Position your mouse cursor on or near the required element.
2. Use the mouse scroll wheel to zoom in or out.
Table 3-4 describes the information displayed in both the Properties and inventory windows.
Field Description
General Tab
Element icon Icon representing the element in Prime Network Vision and
displaying the current color associated with the element operational
health. For more information on severity colors, see Prime Network
Vision Status Indicators, page 2-26.
The icon might include a badge that indicates an alarm or another
item of interest associated with the element. For more information
about badges, see Network Element Badges, page 3-8.
Element Name Name assigned to the element for ease of identification.
Communication State Ability of the VNE to reach the network element, according to the
health of the element. For more information about communication
states, see the Cisco Prime Network 3.8 Administrator Guide.
Investigation State Level of network element discovery that has been performed or is
being performed by the VNE. For more information about
investigation states, see the Cisco Prime Network 3.8 Administrator
Guide.
Vendor Vendor name, as defined in the device MIB.
Product Product name of the element, as defined in the device MIB; for
example, Router.
Device Series Product series that the device belongs to, such as Cisco 7600 Series
Routers.
Element Type Element model, such as Cisco 7606.
1
Serial Number Serial number of the element.
1
CPU Usage Percentage of CPU currently in use by the element.
1
Memory Usage Amount of memory currently in use by the element.
IP Address IP address used for managing the element.
System Name Name of the device, as defined in the device MIB.
Up Since Date and time the element was last reset.
Contact Email address of the person responsible for the element.
Location Physical location of the element, as defined in the device MIB.
1
DRAM Usage Percentage of available DRAM currently in use by the element.
1
Flash Device Size Amount of flash memory available on the element.
1
NVRAM Size Amount of NVRAM available on the element.
Software Version Software version running on the element.
Software Description Description of the system taken from the element.
1
Processor DRAM Amount of DRAM currently in use by the element’s processor.
1
Sending Alarms Whether or not the element is configured for sending alarms: True
or False.
Field Description
Buttons
VNE Details Opens the Properties dialog box, where you can edit the VNE’s
properties, perform maintenance, configure polling rates, and
identify IP addresses for which SNMP syslog and trap events are to
be generated.
For more information, see:
• Viewing and Modifying VNE Properties, page 3-9
• Cisco Prime Network 3.8 Administrator Guide
VNE Status Opens the Communication Details window, which displays the
status of the device protocols and whether the device is sending
traps and syslogs. For more information, see Viewing VNE
Communication Status, page 3-11.
1. Displayed only in the inventory window.
Multiple links One or more links is represented by the Viewing REP Information in
visual link and at least one of the links VLAN Domain Views and
contains a badge. VLAN Overlays,
page 12-60
Step 1 Select the required element in Prime Network Vision and open the inventory window or Properties
window in one of the following ways:
• If the element icon is at the largest size, click the Inventory icon.
• Select an element in the map view or list view, and choose Node > Inventory.
• Right-click a device in the navigation pane, map view, or list view, and choose Properties.
• Select an element in the map view or list view, and choose Node > Properties.
Step 2 Click VNE.
Figure 3-2 shows an example of the VNE Properties window.
If the VNE for the element has been stopped, a message is displayed at the top of the inventory window
letting you know that the VNE was stopped. The message includes a Refresh button so that you can
refresh the information if the VNE has restarted. If the VNE is still down when you click Refresh, a
VNE Unreachable message is displayed and the inventory window is closed. For more information about
starting VNEs, stopping VNEs, adding new VNEs to a network, or modifying the status of a VNE, see
the Cisco Prime Network 3.8 Administrator Guide.
Step 3 Click the required tab to view or modify the desired information. For more information about these
options and configuring a VNE, see the Cisco Prime Network 3.8 Administrator Guide.
Step 4 If you change any of the settings, click Apply and then OK.
If you do not change any of the settings, click OK or Cancel.
Table 3-6 Tasks Available from Inventory and Related Topics (continued)
The inventory window also allows you to view technology-specific information. For more information
on viewing technology-specific information in logical inventory or physical inventory, see:
• Chapter 12, “Monitoring Carrier Ethernet Services”
• Chapter 13, “Monitoring Carrier Grade NAT Properties”
• Chapter 14, “Monitoring DWDM Properties”
• Chapter 15, “Viewing Ethernet Operations, Administration, and Maintenance Tool Properties”
• Chapter 16, “IPv6 and IPv6 VPN over MPLS”
• Chapter 17, “Monitoring MPLS Services”
• Chapter 18, “Monitoring MToP Services”
• Chapter 19, “Viewing SBC Properties”
To open the inventory window, do one of the following:
• If the element icon is at the largest size, click the Inventory icon.
• Double-click an item in the navigation pane or map.
• Right-click an element in the navigation pane or map and choose Inventory.
Figure 3-4 shows an example of an inventory window.
The inventory window displays the physical and logical inventory for the selected item. For more
information about the options in the inventory window, see:
• Navigation Pane, page 3-15
• Device View Pane, page 3-16
• Device View Pane Toolbar, page 3-17
• Ticket and Events Pane, page 3-18
• Content Pane, page 3-16
• Working with Ports, page 3-22
• Updating VNE Information, page 3-12
• Viewing the Properties of a Network Element, page 3-5
• Viewing VNE Communication Status, page 3-11
All areas displayed in the inventory window are correlated; this means that selecting an option in one
area affects the information displayed in the other areas.
The information displayed in the inventory window varies according to the item selected in the
navigation pane.
To view logical inventory information, expand the Logical Inventory branch. For more information about
logical inventory information, see Viewing the Logical Properties of a Network Element, page 3-28.
To view physical inventory information, expand the Physical Inventory branch. For more information
about physical inventory information, see Viewing the Physical Properties of a Device, page 3-19.
Click Poll Now to update the display with the current VNE information.
Click the top right corner to close the inventory window.
Navigation Pane
The navigation pane in the inventory window displays a tree-and-branch representation of the selected
device and its modules. The navigation pane contains two main branches:
• Logical Inventory—Includes logical items related to the selected element, such as access lists, ATM
traffic profiles, and routing entities.
• Physical Inventory—Includes the various device components, such as chassis, cards, subslots, and
so on.
When you select an item in the navigation pane, the information displayed in the content pane is updated.
You can expand and collapse the branches in the navigation pane to display and hide information as
needed.
The window heading and the highest level in the navigation pane display the name of the VNE given to
the element as defined in Cisco Prime Network Administration. The element icon and status are
displayed at the top of the navigation and content panes.
The color of the element icon reflects the element operational status. For more information about
indicators of operational health and status, see:
• Prime Network Vision Status Indicators, page 2-26
• VNE Management State, page 2-28
Status Indicators
A status indicator icon appears next to the element icon for any unacknowledged tickets associated with
the element. In addition, status indicator icons are displayed next to the specific logical or physical
inventory branches that are associated with the ticket.
If you click a branch in the navigation pane that contains a status icon, the associated tickets and events
are displayed in the tickets and events pane at the bottom of the inventory window.
The navigation pane can also display a communication or investigation state icon next to the element
icon in the navigation and content panes.
For more information about communication and investigation state icons, see VNE Management State,
page 2-28.
Content Pane
The content pane contains two tabs:
• General—Contains physical or logical information specific to the item you select in the navigation
pane or device view panel; for example, information about pseudowires or the chassis.
The General tab can also display context-sensitive tabs and buttons; the buttons displayed depend
on your selection in the navigation pane or device view panel. For example, if an ATM port is
selected, the Show VC Table, Show Cross-Connect, or Show Encapsulation button might be
displayed.
• Ports—Lists all ports on the device with their current alarm status, location, and other properties,
and enables you to change their status by using a right-click menu. For more information, see
Working with Ports, page 3-22.
The content pane can also display context-sensitive tabs and buttons; the buttons displayed depend on
your selection in the navigation pane or device view panel. For example, if an ATM port is selected, the
Show VC Table, Show Cross-Connect, or Show Encapsulation button might be displayed.
In addition, you can view the properties of a row in a table by double-clicking the row or by
right-clicking the row and choosing Properties.
For information about tables that appear in the content pane, see Working with Prime Network Tables,
page 2-53.
Icon Description
Displays an enhanced view of the components within the device in
a browse box as you move over the device view panel with the
selection tool.
Fits the entire view of the element in the device view panel.
Field Description
Severity Icon indicating the severity of the alarm on the event
Event ID Event identifier, assigned sequentially.
Time Date and time when the event occurred and was logged and
recorded.
Description Description of the event.
Location Entity that triggered the event.
Detection Type Method by which the event was detected, such as Service or Syslog.
Alarm ID Identifier of the alarm associated with the event.
Ticket ID Identifier of the ticket associated with the event.
Causing Event ID Identifier of the causing event.
Duplication Count For network events, the duplication count is calculated by the VNE
and pertains only to flapping events. The duplication count
represents the number of noncleared events aggregated by the
flapping event.
Reduction Count For network events, the reduction count is calculated by the VNE
and pertains only to flapping events. The reduction count represents
the number of events that are aggregated by the flapping event.
Archived Whether the event is archived: True or False.
• Provisioning Events—Available to users with the Configurator role or higher for the selected
element. This tab displays provisioning events with their source in the selected element and with a
timestamp that falls within the specified events history size (see Selecting Prime Network Vision
Options, page 2-51).
If Prime Network Activation is installed, all activations that occur are included in this tab.
Table 8-4 on page 8-5 describes the information that is available in the Provisioning Events tab.
Note Provisioning events that are caused by workflows (AVM 66) are not displayed in this table
even if the element is affected by the workflow.
When displaying network and provisioning events, Prime Network Vision monitors the history size value
defined in the Events tab of the Options dialog box (Tools > Options > Events). The default value is six
hours and can be changed in Prime Network Administration. In addition, Prime Network Vision limits
the maximum number of network and provisioning events that are sent from the server to client to 15,000
each. If the number of network or provisioning events exceeds the limit specified in the Options Events
tab or the 15,000 maximum limit, Prime Network Vision purges the oldest events from table. The
purging mechanism runs once per minute.
Tip You can display or hide the ticket and events pane by clicking the arrows displayed below the device
view panel.
Icon Device
Chassis
Shelf
Card/Subcard
Port/Logical Port
Pluggable Transceiver
Unmanaged Port
Physical inventory is continuously updated for both status and configuration. The addition of a new card,
the removal of a card, or any change to the device is reflected by the VNE and updated instantly.
If you physically remove an item that Prime Network Vision is managing, the following changes occur
in physical inventory, depending on the item removed:
• Removing an item other than a pluggable transceiver results in the following changes:
– The color of the icon in physical inventory changes to black.
– The item’s status changes to Out.
The other properties of the removed item reflect the most recent value that was updated from the
device with the following exceptions:
– Cards—If the card was participating in a card redundancy configuration, the redundancy state
changes to None.
– Port—The operational status of the port changes to Down.
• Removing a pluggable transceiver results in the following changes:
– The color of the pluggable transceiver icon changes to gray.
– The pluggable transceiver status changes to Disabled.
– In the Pluggable Transceiver panel:
— The properties are no longer displayed.
— The connector type changes to Unknown.
— The pluggable port state changes to Out.
Fans and power supplies are displayed in physical inventory if they are field replacable units (FRUs).
The manner in which the fans are displayed depends on whether the fans can be separated or not:
• If the fans under the fan trays are inseparable, only the fan trays are represented.
• If the fans under the fan trays can be separated, they are shown as separate items in physical
inventory.
The window displayed for all the devices is similar in appearance. However, the individual sections that
are displayed depends on the selected item. For example, when a port that supports pluggable
transceivers is selected, the Pluggable Transceiver section is displayed. This section provides
information such as the port connector’s type and serial number, as well as an indication whether a
transceiver is currently plugged in.
Figure 3-6 shows an example of a selection in physical inventory and the available buttons.
1 Poll Now button Poll the VNE and update the information as needed.
For more information, see Updating VNE Information,
page 3-12.
2 Show VC Table button Displays virtual circuit (VC) information for the selected
port.
For more information, see Viewing ATM VPI and VCI
Properties, page 18-10.
3 Show Cross Connect button Displays cross-connect information for incoming and
outgoing ports.
For more information, see Viewing ATM Virtual
Connection Cross-Connects, page 18-6.
4 Show Encapsulation button Displays encapsulation information for incoming and
outgoing traffic for the selected item.
For more information, see Viewing Encapsulation
Information, page 18-11.
5 Disable Sending Alarms button Enables you to manage the alarms on a port.
For more information, see Working with Ports, page 3-22.
6 Port Utilization Graph button Displays the selected port traffic statistics: Rx/Tx Rate and
Rx/Tx Rate History.
For more information, see Generating the Port Utilization
Graph, page 3-27.
— Show DLCI Table button Displays data-link connection identifier (DCLI)
(not displayed) information for the selected port.
The buttons that are displayed in the physical inventory content pane depend on the selected port.
For information about configuring topology from a port, see Adding Static Links, page 5-15.
For a detailed description of device properties, see Viewing the Properties of a Network Element,
page 3-5.
Table 3-9 describes the information that is displayed in the Ports tab.
Field Description
Location Location of the port in the device, using the format
slot.module/port, such as 1.GigabitEthernet1/14.
Type Port type, such as RJ45 or Pluggable.
Sending Alarms Whether or not the port is configured for sending alarms: True or
False.
Pluggable Transceiver For the Pluggable port type, indicates that the port can hold a
pluggable transceiver.
Port Alias Name used in the device CLI or EMS for the port.
Managed Whether or not the port is managed: True or False.
Status Port status, such as OK, Major, or Disabled.
The subinterface is a logical interface defined in the device; all of its parameters can be part of its
configuration. Table 3-10 describes the information that can be displayed in the Subinterfaces table. Not
all fields appear in all Subinterfaces tables.
Field Description
Address IP address defined in the subinterface.
Mask Subnet mask.
VLAN Type Type of VLAN, such as Bridge or IEEE 802.1Q.
Double-click the entry to view the Port IP VLAN Properties window
containing:
• VLAN type
• VLAN identifier
• Operational status
• A brief description of the VLAN
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 Viewing ATM Virtual
Connection Cross-Connects, page 18-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.
Disabling Alarms
By default, alarms are enabled on all ports. When the alarms are disabled on a port, no alarms are
generated for the port and they are not displayed in the ticket and events pane.
To disable alarms on ports:
Enabling Alarms
You can enable the alarms on a port at any time.
To enable alarms:
In response:
• The Sending Alarms field displays the value true, indicating that the alarm for the required port has
been enabled.
• The content pane displays the Disable Sending Alarms button.
Step 3 To enable 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 Enable Sending Alarms. In response, the Sending
Alarms field displays the value true for the selected ports.
Step 1 Open the inventory window and select the required port in physical inventory.
Step 2 In the Ethernet CSMA/CD section, click Port Utilization Graph.
The following information is displayed in the Port Statistics dialog box:
• Rx Rate—The reception rate as a percentage.
• Rx Rate History—The reception rate history is displayed as a graph.
• Tx Rate—The transmission rate as a percentage.
• Tx Rate History—The transmission rate history is displayed as a graph.
Note For more information about opening the inventory window, see Opening the Inventory Window,
page 3-12.
Bridge
Cross-VRF
Encapsulation
Logical inventory
Note Prime Network Vision does not display the tabs in Table 3-13 for devices that support multiple contexts.
Instead, when you select Logical Inventory for a device that contains multiple contexts, Prime Network
Vision displays a Contexts table that lists the contexts configured on the device.
Tab Description
Data Link Aggregation Lists the data link aggregations configured on the selected entity,
Containers such as Ethernet link aggregations.
Encapsulation Aggregation Lists the encapsulation aggregations configured on the selected
Containers entity.
Forwarding Component Lists the context profiles for which logical inventory information
Containers can be displayed, such as routing entities and bridges.
Operating System Provides information about the operating system on the selected
entity.
Physical Layer Aggregation Lists aggregations configured at the physical layer for the selected
Containers entity, such as IMA groups.
Processes Lists the processes running on the selected entity, such as Clock or
CDP.
Tab Description
Traffic Descriptors Lists the profiles for which logical inventory information can be
displayed, such as Frame Relay traffic profiles and Address
Resolution Protocol (ARP) entities.
Tunnel Containers Lists the types of tunnels that are configured on the selected entity,
such as pseudowires or GRE tunnels.
Field Description
Boot Software Cisco IOS system image information.
Is K9Sec Whether or not the K9 security feature is enabled on the operating
system: True or False
ROM Version Cisco IOS bootstrap software version, such as 12.2(33r)SRC3.
OS Version Cisco IOS software version, such as 12.2(33)SRE, Release
Software (fc1).
Table 3-15 describes the information that is displayed in the Operating System tab.
Field Description
Is K9Sec Whether or not the K9 security feature is enabled on the operating
system: True or False
Family Cisco family, based on the device platform, such as CRS_IOS or
C12K_IOS_XR.
SDR Mac Addr Secure Domain Router (SDR) MAC address.
This field applies to Cisco IOS XR devices only.
Software Version Cisco IOS software version, such as 12.2(33)SRC3, Release Software
(fc2).
Boot Software Cisco IOS system image information.
ROM Version Cisco IOS bootstrap software version, such as 12.2(17r)SX3.
Step 3 For a Cisco IOS XR device, view information about the operating system in one of the following ways:
• In the inventory window, choose Logical Inventory > Modular OS.
Figure 3-11 shows an example of the information that is displayed for Cisco IOS XR devices.
Table 3-16 describes the information that is displayed for Cisco IOS XR system.
Field Description
Is K9Sec Whether or not the K9 security feature is enabled on the operating
system: True or False
Cw Family Cisco family, based on the device platform, such as CRS_IOS_XR
or C12K_IOS_XR.
SDR Mac Addr Secure Domain Router (SDR) MAC address.
OS Version Cisco IOS XR software version, such as 3.8.0[00].
Boot Software Cisco IOS XR system image information.
SDR Name SDR name.
SDR Id SDR identifier.
ROM Version Cisco IOS XR bootstrap software version, such as 1.51.
RAM Size Size, in kilobytes, of the device processor RAM.
Field Description
OS Packages Table
Package Info Information on the individual package and its 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 Composite package name of the package with the date and time,
such as:
Tues Feb 8 20:37:07.966 UTC
disk0:comp-hfr-mini-3.9.3.14
Table 3-17 describes the information that is displayed for modular operating systems in the
Operating System tab.
Field Description
Is K9Sec Whether or not the K9 security feature is enabled on the operating
system: True or False
Family Cisco family, based on the device platform, such as CRS_IOS_XR or
C12K_IOS_XR.
Software Version Cisco IOS XR software version, such as 4.0.0[Default].
SDR Mac Addr Secure Domain Router (SDR) MAC address.
Boot Software Cisco IOS XR system image information.
SDR ID SDR identifier.
SDR Name SDR name.
ROM Version Cisco IOS XR bootstrap software version, such as 1.54.
The topological map is the main tool used by Cisco Prime Network Vision (Prime Network Vision) to
display the links and relationships between the network elements and aggregations. The following topics
describe how to work with the topological maps displayed in the content pane of the Prime Network
Vision window:
• User Roles Required for Working with Prime Network Vision Maps, page 4-2
• Using Chinese Characters, page 4-5
• Opening and Closing Maps, page 4-5
• Creating a New Map, page 4-8
• Working with Elements in a Map, page 4-9
• Managing Maps, page 4-16
• Finding Items in a Map, page 4-26
• Working with Aggregations, page 4-28
• Working with Overlays, page 4-33
• Filtering Links in a Map, page 4-38
• Opening the CPU Usage Graph, page 4-40
• Communicating with Devices Using Ping and Telnet, page 4-41
You can also perform the following functions from the map and list views if they are configured for your
client:
• Launch external applications or tools, such as an SSH client.
• Launch available activation and configuration scripts, including those you create using Command
Builder. These scripts can be launched against multiple network elements at the same time.
For more information on these functions, see the Cisco Prime Network 3.8 Customization User Guide.
Table 4-1 Default Permission/Security Level Required for Working with Prime Network Vision
Maps - Element Not in User’s Scope
Table 4-1 Default Permission/Security Level Required for Working with Prime Network Vision
Maps - Element Not in User’s Scope (continued)
Table 4-2 Default Permission/Security Level Required for Working with Prime Network Vision
Maps - Element in User’s Scope
Table 4-2 Default Permission/Security Level Required for Working with Prime Network Vision
Maps - Element in User’s Scope (continued)
Note This list is not available to first-time users or users who closed their maps before closing the application.
To open a map that you viewed previously but did not close when you last logged out:
Step 1 Launch Prime Network Vision as described in Launching Prime Network Vision, page 2-2. The Prime
Network Vision window opens, and the Last Open Maps dialog box is displayed.
Step 2 Check the check boxes for the maps you want to open, and uncheck the check boxes for the maps you
do not want to open.
Step 3 Click OK.
Step 1 Display the Open Map dialog box by doing one of the following:
• Click Open Map in the main toolbar.
• Choose File > Open.
The Open Map dialog box lists the existing maps, and indicates which maps are currently open in your
view.
The Find field enables you to search for a map containing the string that you enter. For more information,
see Finding Text in a Table, page 2-55.
You can use the tools described in Table 4-3 to manage maps in the Open Map dialog box.
Delete Map Deletes the selected map from the Open Map dialog box, the Prime
Network Vision window, and the database. If a map that is opened
is deleted, the map closes. For more information, see Deleting a
Map from the Prime Network Vision Database, page 4-25.
Rename Map Renames the selected map in the Open Map dialog box and Prime
Network Vision window. For more information, see Renaming a
Map, page 4-20.
Sort Table Values Sorts the information displayed in the table. For more information,
see Sorting a Table, page 2-55.
Filter Defines a filter for the information displayed in the table. For more
information, see Filtering Table Contents, page 2-57.
Note When a filter is applied, the Clear Filter button is activated.
Clear Filter Clears the existing filter.
Show All Rows Displays all table rows that meet the current filtering criteria.
Show Only Selected Displays only the rows that you select.
Rows
For more information, see Viewing Selected Rows, page 2-58.
Step 2 Select the maps you want to open using one of the following methods. You can select multiple maps by
pressing Ctrl while you select individual maps.
• Select the maps in which you are interested, and then click Open.
• Right-click the required maps and choose Open.
• Double-click the required maps.
Note By default, you can view and work on a maximum of five maps at any given time (per client
instance) in the Prime Network Vision window. To change this default setting, contact your
Cisco account representative. To create a new map or select a new map, close the required
number of maps.
Closing a Map
When you close a map, Prime Network Vision saves basic map information whether or not you manually
save the map. This default information includes device and link additions, device and link removals,
aggregations, and disaggregations. However, you must use the Save Map option if you want to retain the
following information in the database:
• The location of the devices on the map
• Thumbnails
• The size of the devices
To close a map:
Step 1 (Optional) To save more than the default map information, use one of the following methods:
• Click Save Map Appearance in the main toolbar.
• Choose File > Save Map from the main menu.
Step 2 Do one of the following:
• Choose File > Close.
• Click in the upper right corner of the content pane.
If changes have been made to the map, an information message is displayed.
Step 3 Click Yes. The map is saved and closed. An empty Prime Network Vision window is displayed, or the
map that was last opened is displayed.
Note You cannot specify the same name for two or more maps.
For information on removing elements from a map, see Removing Elements from a Map, page 4-15.
Note Based on the security level and access permissions assigned, this option might not be available to all
users.
You can add the following types of elements to maps, as shown in Figure 4-1:
• EFP cross-connects
• Ethernet services
• MPLS-TP tunnels
• Network elements
• Pseudowires
• Unassociated bridges
• VLANs
• VPLS instances
• Existing or new VPNs
If you choose to add a new VPN, the Create VPN dialog box is displayed. For information on creating
a VPN, see Creating a VPN, page 17-22
In all other instances, the Add element to map dialog box is displayed, as shown in Figure 4-2.
Note If the element you want to add is outside of your scope, it is not displayed if you enter a search
string. Choose Show All to view all available elements, both in and out of your scope.
b. Enter a search string to narrow the display to a range of elements or to a specific element.
c. Click Go.
For example, if you add a network element, choose IP Address, and enter 254, the network elements
with IP addresses containing the string 254 are displayed. If you choose Vendor and enter Cisco,
only Cisco network elements are displayed.
As recommended, use the Search option to specify search criteria and thereby limit the number
of elements displayed.
The number of elements that can be displayed in the Add element dialog box is configured in
the registry.
Note Changes to the registry should only be carried out with the support of Cisco. For details,
contact your Cisco account representative.
The available elements are displayed in the Add element dialog box in table format. The dialog box also
displays the date and time at which the list was generated. To update the list, click Refresh.
If a network element is not included in your scope, it is displayed with the locked device icon.
For information about sorting and filtering the table contents, see Working with Prime Network Tables,
page 2-53.
Step 3 In the Add element dialog box, select the elements that you want to add. You can select and add multiple
elements by pressing Ctrl while selecting individual network elements or by pressing Ctrl + Shift to
select a group of elements.
Step 4 Click OK.
If you select more than 25 business elements (such as VLANs or VPLS instances) to add, a message is
displayed, stating that the action can take a while to complete and asking if you want to continue. Click
OK to continue or Cancel to change your selection.
The elements are displayed in the navigation pane and content area. In addition, any associated tickets
are displayed in the ticket pane.
The network element information is saved with the map in the Prime Network Vision database.
Note The Resize option is enabled only when element icons are selected. Links cannot be resized.
For more information about the information that is displayed in the element icons, see Information
Available in Element Icons, page 3-3.
Using Zoom
Prime Network Vision enables you zoom in or out of maps so that you can use the viewing level that
meets your needs. Zooming differs from resizing in that zooming does not change the size of the icon
itself.
You can zoom in or out on a map by using either of the following methods:
• Position your mouse cursor in the map pane and use your mouse scroll wheel, as follows:
– Roll the wheel forward to zoom in on the map.
– Roll the wheel backward to zoom out on the map.
• Click Zoom Selection Mode in the and zoom in and out, as follows:
– To zoom in, press and hold the mouse button while selecting the area that you want to view in
greater detail. Prime Network Vision zooms in on the selected area and centers it in the map
pane.
– To zoom out, click Normal Selection Mode in the and do either of the following:
- Position your mouse cursor in the map pane and use the mouse scroll wheel to zoom out.
- Click Fit in Window to view the entire map in the map pane.
Note Based on the security level and access permissions assigned, this option might not be available to all
users.
Step 1 In the navigation pane or map, select the element or aggregation that you want to delete.
Step 2 Right-click to display the right-click menu and choose Remove from Map. The selected element or
aggregation is removed from the map.
The element is removed from the map in the database, but is still managed by Prime Network Vision and
can be added again.
Managing Maps
The following topics describe how to manage maps in Prime Network Vision:
• Selecting Map Viewing Options, page 4-16
• Defining a Map Layout, page 4-17
• Applying a Background Image, page 4-17
• Using the Overview Window, page 4-19
• Renaming a Map, page 4-20
• Saving Maps, page 4-20
• Previewing and Printing a Map, page 4-23
• Deleting a Map from the Prime Network Vision Database, page 4-25
Zoom Selection Mode Activates the zoom selection mode, which enables you to select an
area in the map pane to enlarge by clicking and dragging the zoom
mode cursor.
Pan Mode Activates the pan mode, which enables you to move around in the
map pane by clicking and dragging the pan mode cursor.
Note Changes to the registry should only be carried out with the support of Cisco. For details, contact
your Cisco account representative.
By default, Prime Network Vision uses the circular layout for maps. If you click Layout Map in the main
toolbar, Prime Network Vision displays the map according to the option last selected.
Step 1 Navigate to the required map in Prime Network Vision. The map can reside at the top level or in a
subordinate window.
Step 2 Right-click the map background and choose Set Map Background.
The Manage Map Background dialog box is displayed, as shown in Figure 4-3.
Field Description
Select Image Applies the selected image to the current map background:
1. Choose Select Image.
2. Click Browse.
3. In the Open dialog box, select the desired image and click OK.
The name of the selected image is displayed in the Manage Map
Background dialog box.
4. Click OK. The selected image is displayed as the map
background.
Use Image From Upper Level Indicates whether the selected subordinate map should use the same
image as the parent map or a different image:
• To use the same image that is used by the parent map, choose
Use Image from Upper Level. The name of the image used by
the parent map is displayed by default.
• To use a different image than that used by the parent map,
choose Select Image and complete the steps described for that
option.
Remove Image Removes the current image from the map background.
To remove an image from the current map, click Remove Image.
Renaming a Map
Prime Network Vision enables you to rename a map that is displayed in the Prime Network Vision
window. The name change affects all users of the map and the new name is displayed in the Prime
Network Vision window of all users.
To rename a map:
Saving Maps
Prime Network Vision provides three options for saving maps:
• To save more map information than Prime Network Vision saves by default, see Saving a Map with
Information, page 4-20.
• To save a copy of a map so that you can use it as a template for another map, see Saving a Map as a
New Map, page 4-21.
• To save a map as an image, see Saving a Map as an Image, page 4-21.
Step 1 Make sure that the map that you want to save is displayed in the Prime Network Vision content pane.
Step 2 Select the required map, elements, or aggregations in the navigation tree or the map.
Step 3 Right-click in the navigation pane or one of the selected items in the map pane, and choose Save as New
Map.
Step 4 In the Create Map dialog box, enter a new name for the map.
Step 5 Click OK. The new map is created.
For information about opening the new map, see Opening a Map from the Open Map Dialog Box,
page 4-6.
Attribute Description
Image Specify the image type and filename:
• Type—In the drop-down list, select one of the following file types:
– GIF Image (*.gif)
– JPEG Image (*.jpg)
– PDF Document (*.pdf)
– Portable Network Graphics (*.png)
– Scalable Vector Graphics (*.svg)
• File Name—Browse to the required location and enter a filename for the
image.
Image Content Check the appropriate check box for the content to be included in the image:
• Visible Window Only—Saves the currently selected map as an image,
even if the content area displays the list view or the links view.
The option is enabled only if Current Zoom Level is selected for the Size
attribute.
• Selected Objects Only—Saves the selected network objects as an image.
This option is enabled only if network objects are selected in the content
pane.
Image Quality Select the required image quality level:
• High
• Medium
• Low
Size Specify the required zoom level for the image:
• Current Zoom Level—Saves the image at the currently selected zoom
level. Selecting this option enables the Visible Window Only check box.
• Actual Size—Saves the image at the actual size.
• Fit in Canvas—Saves the image so that it fits in the canvas.
• Custom—Saves the image at an enlarged or reduced size. Selecting this
option enables the Width and Height options, so that you can enter the
required size in pixels.
Step 4 Click OK. The map is saved as an image in the directory you specified.
Using Prime Network Vision, you can preview a map before printing it.
To preview a map:
Step 1 In Prime Network Vision, display the map that you want to print.
Step 2 From the main menu, choose File > Print Preview. The Print Preview window is displayed with the
active map.
The following buttons are displayed in the Print Preview window:
Print Opens the Print dialog box so you can print the displayed network or map
to the required printer.
Fit Displays the entire network or map in the Print Preview window.
Step 3 Click Print. The required map is printed to the selected printer.
Prime Network Vision enables you to define the print setup of a map before it is printed.
To define the print setup:
Step 1 From the main menu, choose File > Print Preview to open the Print Preview dialog box.
Step 2 Click Print Setup. The Print Setup dialog box is displayed.
Step 3 Define the print setup, using the information in Table 4-8.
Option Description
Print Selection
Print Entire Drawing Prints the currently displayed map, including aggregations.
Print Current Window Prints the currently displayed map, excluding aggregations.
Print Current Selection Prints the area selected in the currently displayed map.
Scale By
Pages Prints the currently displayed map according to the numbers
specified in the Page Columns and Page Rows fields.
Actual Size Prints the currently displayed map at the actual size.
Zoom Level Prints the currently displayed map according to the selected zoom
level.
Caption
Print Caption Adds the specified caption to the printed map.
Font Specifies the font to use for the caption.
Caption Prints the text entered in this field as the caption.
Position Defines the position of the caption in the printed map.
Option Description
Multipage Printing
Print Page Numbers Prints the map with page numbers.
Print Crop Marks Prints the map with crop marks.
Other
Print Border Prints a border around the printed map.
Color Displays the Choose Color dialog box so you can select the border
color.
Print Background Prints the background of the currently displayed map.
Page Setup
Page Setup Offers standard printer options, such as printing in portrait or
landscape mode and setting margin widths.
Step 4 Click OK to save your settings, or Default to restore the default settings.
The Print Preview dialog box is refreshed with the current settings.
Step 5 If you are satisfied with your settings, click Print. Otherwise, click Print Setup and revise your settings.
Step 1 Open the Open Map dialog box in one of the following ways:
• Click Open Map in the main toolbar.
• Choose File > Open from the File menu.
Step 2 In the Open Map dialog box, complete the following steps:
a. Select the map you want to delete.
b. In the toolbar, click Delete Map. A confirmation message is displayed.
c. Click Yes. The selected map is deleted from the Open Map dialog box, the Prime Network Vision
window, and the database. If the map is open when you click Yes, a message is displayed, stating
that the map will be closed.
d. Click OK to acknowledge that the map can be closed.
e. Click Cancel to close the Open Map dialog box.
Note You can enter a partial name (case insensitive) or IP address. For example, entering XY finds
elements or services with names containing the string xy, such as Axy, Xy, xY, or xyZ.
The Search all map levels check box enables you to search for an element, name, or IP address at all
levels of the map. When disabled, this option searches for the element or service, but excludes
aggregations from the search. This option is disabled by default.
Step 3 Check or uncheck the Search all map levels check box, as required.
Step 4 Click OK. An element or service matching the search criteria is selected in the map.
Step 5 Continue searching using the following methods:
• To view the next element or service that matches the search criteria, click Find Next in the or press
F3.
• To view the previous element or service that matches the search criteria, click Find Previous in the
or press Shift + F3.
Step 1 In the Links view, right-click the required link and choose Select Link in Map.
The link is highlighted in the map pane.
Step 2 If two or more lines represent the same link (such as a VRF link), the Select Link Context dialog box is
displayed. Select the required link context from the drop-down list and click OK. The link is highlighted
in the map pane.
Step 3 Click in the map background to remove the highlight from the selected link.
For more information about links in Prime Network Vision, see Chapter 5, “Working with Links.”
Step 1 In the ticket pane, right-click the required ticket and choose Find Affected Elements. Depending on the
number of affected elements, the information is displayed in one of the following ways:
• If only one element is affected, the affected element is selected in the navigation pane and the
content area.
• If a link is affected, the affected link is selected in the links view.
• If two or more elements are affected, the affected elements are displayed in the Affected Elements
window as shown in Figure 4-7.
Step 2 In the Affected Elements window, select the required element, then click OK. The selected element is
selected in the Prime Network Vision map or links view.
Step 3 Click in the navigation pane or the map pane to remove the highlight from the selected device or link.
Note You cannot aggregate service entities that exist within a service. For example, you cannot aggregate
VRFs that exist within a VLAN.
For more information on working with aggregations, see the following topics:
• Grouping Network Elements into Aggregations, page 4-29
• Adding Elements to an Existing Aggregation, page 4-30
• Viewing an Aggregation Thumbnail, page 4-30
• Ungrouping Aggregations, page 4-33
• Renaming Aggregations, page 4-32
Step 1 Select the network elements using one of the following methods:
• Select a single item in the map pane or navigation tree.
• Select multiple items in the map pane or navigation tree while pressing Ctrl.
Step 2 Aggregate the network elements using one of the following methods:
• In the menu bar, choose Node > Aggregate.
• Right-click the navigation pane and choose Aggregate.
• In the map pane, right-click one of the selected items and choose Aggregate.
Step 3 In the Aggregation dialog box, enter a unique name for the aggregation and click OK. The aggregation
is displayed in the navigation pane and the map pane. Aggregations are displayed as a single entity with
the Aggregation icon and a plus sign, as in the following examples:
The aggregation icon changes color according to the alarm severity. For more information about severity
colors, see Alarm Indicators, page 2-17.
When a thumbnail is opened, neighboring nodes are moved aside by default to allow room for the
thumbnail to expand. Similarly, when a thumbnail is closed, the neighboring nodes usually return to their
original locations. This behavior of the neighboring nodes when a thumbnail is opened and closed is
configured in the registry, and can be disabled, if required.
Note Changes to the registry should only be carried out with the support of Cisco. For details,
contact your Cisco account representative.
A dashed gray border around an icon indicates that the element resides within a thumbnail and not at the
current map level.
Table 4-9 describes the options available when working with aggregation thumbnails.
Renaming Aggregations
You can rename aggregations that are displayed in Prime Network Vision. The name change affects all
users of the map, and the new name is displayed in the Prime Network Vision window of all users.
To rename an aggregation:
Step 1 Select the aggregation that you want to rename in the navigation tree or the map.
Step 2 Right-click the aggregation icon and choose Rename.
Step 3 In the Rename Node dialog box, enter a new name for the aggregation and click OK. The selected
aggregation is renamed in the navigation tree, map pane, and database.
Ungrouping Aggregations
Aggregations can be ungrouped. If the aggregation that you ungroup contains nested aggregations, the
nested aggregations move up one level, and the original aggregation is removed.
If an element in the aggregation that you ungroup also exists at the parent level, the element is
represented only once after the aggregation is ungrouped. As a result, no elements are represented twice
at the same level.
To ungroup an aggregation:
For more information about resizing aggregation icons, see Resizing Map Elements, page 4-14.
Applying an Overlay
To apply an overlay:
Step 1 In Prime Network Vision, choose the map in which you want to apply an overlay.
Step 2 From the toolbar, choose Choose Overlay Type > overlay-type where overlay-type is one of the
following options:
With the exception of the None option, a dialog box is displayed that allows you to select the specific
overlay to apply.
Figure 4-9 shows an example of the Select Pseudowire Overlay dialog box.
Each overlay type allows you to search for specific overlays. Table 4-10 identifies the search fields
available for each overlay type.
Note The overlay is a snapshot taken at a specific point in time and does not reflect changes that occur in the
service. As a result, the information in an overlay can become stale. To update the overlay, click Refresh
Overlay in the toolbar.
Removing an Overlay
To remove an overlay, choose Choose Overlay Type > None. The overlay is removed from the map.
Step 1 Open the Create Map dialog box using one of the following methods:
• Click New Map in the main toolbar.
• Choose File > New Map from the main menu.
The Create Map dialog box is displayed. For more information, see Creating a New Map, page 4-8.
Step 2 Click Advanced. The Link Filter dialog box is displayed.
The Link Filter dialog box displays a list of all the types of links that you can filter in the map view and
links view.
Note By default all link types are selected in the Link Filter dialog box. That is, all links are displayed
in the map view and links view.
Step 3 Select the required option from the Group drop-down list:
• All—All the links are displayed in the map view and links view.
• Custom—Only the links defined for the customized filter are displayed in the map view and links
view.
• Data Link—The data link layer class of links (ATM and Frame Relay) is displayed in the map view
and links view.
• None—None of the links are displayed in the map view and links view.
• Physical—Only the physical links are displayed in the map view and links view.
• VPN—Only VPN-related links (GRE, Pseudowire, VPN, and VPN IPv6) are displayed in the map
view and links view.
Note You can customize the Group drop-down list options by selecting an option and adding or
removing the required link types. The next time the Link Filter dialog box is opened, the Custom
option is displayed with the specified link types.
Step 4 Check the check boxes for the links that you want to display in the map view and links view. Uncheck
the check boxes for the links you do not want to display in the map view and links view.
Step 5 Click Apply to apply the defined link filter settings and continue with more selections.
Step 1 Right-click a network element in the navigation tree and choose Tools > CPU Usage.
The CPU Usage dialog box displays the following information:
• CPU Usage—The CPU usage rate as a percentage.
• CPU Usage History—The CPU usage rate history is graphically displayed.
• Memory Usage—The memory usage rate as a percentage.
• Memory Usage History—The memory usage rate history is graphically displayed.
Step 2 If desired, click Save to CSV File to export the displayed data. For more information, see Exporting
Tables to a File, page 2-59.
Step 3 Click the upper right corner to close the CPU Usage dialog box.
Pinging a Device
Prime Network Vision enables you to ping a device to verify that the device is responding.
The ping is performed from the client to the device, and not from the Prime Network Vision unit hosting
the VNE to the device.
To ping a device, right-click a device in the navigation tree or map, and choose Tools > Ping.
The results are displayed in a new window.
Telneting a Device
Prime Network Vision enables you to communicate with a device using the Telnet window.
The Telnet session is performed from the client to the device, and not from the Prime Network Vision
unit hosting the VNE to the device.
Note If you are using a Windows 7 system, you must enable the Windows Telnet Client before you can use
the Prime Network Telnet option.
- For Windows 7 32-bit systems, enable the Windows Telnet Client to use the Prime Network Telnet
option.
- For Windows 7 64-bit systems, a solution is available on the Cisco Developer Network at
http://developer.cisco.com/web/ana/forums/-/message_boards/message/2780108.
To telnet a device:
Step 1 Right-click a device in the navigation tree or map, and choose Tools > Telnet. A terminal window opens.
Step 2 Log in and use the Telnet window as needed.
The following topics describe how to view information about static and dynamic links using the
Cisco Prime Network Vision (Prime Network Vision) user interface:
• User Roles Required to Work with Links, page 5-1
• Understanding Dynamic and Static Links, page 5-3
• Link Discovery and Flickering Ethernet Topology Links, page 5-3
• Viewing Link Properties, page 5-4
• Viewing Link Impact Analysis, page 5-13
• Adding Static Links, page 5-15
• Filtering Links Using the Collection Method, page 5-18
• Selecting a Link, page 5-18
Table 5-1 Default Permission/Security Level Required for Working with Links - Element Not in
User’s Scope
Table 5-2 Default Permission/Security Level Required for Working with Links - Element in
User’s Scope
Note Changes to the registry should only be carried out with the support of Cisco. For details, contact your
Cisco account representative.
Prime Network Vision provides information about links in the following ways:
• Through the physical characteristics of the link in a map, tooltips, and link quick views—See
Viewing Link Properties in Prime Network Vision Maps, page 5-4.
• In the Links view—See Viewing Link Properties in the Links View, page 5-8.
• In the link properties window—See Viewing Link Properties in the Link Properties Window,
page 5-10.
Link Color
Red Critical alarm is on the link.
Orange Major alarm is on the link.
Yellow Minor alarm is on the link.
Note The color of a selected link is customizable. The default color is blue. For more information on link
colors, see Map View, page 2-10.
Step 1 Hover your mouse cursor over the required link in a map. A link tooltip is displayed as shown in
Figure 5-1.
1 Number of links represented by the single link in the map. In this example, 29 links.
2 Link endpoints.
3 List of all links represented by the link in the map with the following information, as appropriate:
• Type of link, such as Physical, MPLS, or Tunnel. For a complete list of the types of links and
their abbreviations, see Link Icons, page A-8.
• Link detail, such as the interface used on each endpoint, service name, or type of service.
• Link alarm status, indicated by the link color.
4 Hyperlink to the link properties window.
The Properties button is available for physical, topographical, and service links, but is not
available for business links (dashed links).
For more information, see Viewing Link Properties in the Link Properties Window, page 5-10.
Step 3 To view more link properties, click Properties in the link quick view.
For more information about the link properties window, see Viewing Link Properties in the Link
Properties Window, page 5-10.
Note A link external to the network has a blue cell background in the table.
Any links that are added or removed from the map are automatically added or removed from the links
view, provided they have not been filtered out.
Table 5-4 describes the information that is displayed in the links view.
Field Description
Context Name of the map or aggregation containing the link. The links view
can include multiple contexts.
This field can be empty for either of the following reasons:
• One side of the link is not included in the map.
• The link is filtered out of all contexts.
Severity Severity bell icon, colored according to the severity of the alarm on
the link and indicating the impact of the alarm on the network. For
more information, see Prime Network Vision Status Indicators,
page 2-26.
A End Point Device or site that is the source of the link, as a hyperlink to the
inventory of the device or site.
Bidirectional Whether the link is bidirectional or unidirectional: True
(bidirectional) or False (unidirectional).
Z End Point Device or site that is the destination of the link, hyperlinked to the
relevant entry in inventory.
Link Type Type of link, such as Physical Layer, VPN, MLPPP, or MPLS.
By default, the links displayed in the links view are sorted according to link type and the deep collection
method.
The buttons in Table 5-5 are displayed at the top of the links view and enable you to filter the links
according to the collection method.
Note If you load a map with many links (for example, thousands of links), it can take a while for the complete
list of links to load. The filtering options in the table are unavailable until the table has completely
loaded.
External Links with one side of the link in the selected map or aggregation and the other
Links side of the link outside the currently selected map or aggregation.
Flat Links Links currently visible in the map pane for the selected map or aggregation,
excluding any thumbnails.
Deep Links for the selected aggregation and any nested aggregations, with both
Links endpoints within the currently selected map or aggregation.
For more information about filtering links using the collection method, see Filtering Links Using the
Collection Method, page 5-18.
Note If multiple links exist between the elements or aggregations, the link properties window displays
information for all the links.
See the following topics for more information about each of the panes in the link properties window:
• Link List Pane, page 5-11
• Properties Pane, page 5-11
• Ticket and Events Pane, page 3-18
The information displayed in the link properties window changes according to the ports or subports
selected in the link list pane.
Properties Pane
The properties pane enables you to view the following, depending on your selection in the link list pane:
• Properties of a selected link, including port properties information.
• Hyperlinks to relevant entries in logical or physical inventory.
• Status.
The properties pane displays the link type, port alias, and port location, all of which uniquely identify
the port. The port location information is also displayed as a hyperlink to the inventory window.
The properties pane also displays the parameters for each end of the link, aligned under the relevant link
identifier. Any discrepancies between the link’s ports are displayed in red.
The following fields are displayed in the Connection Information area for physical links:
• Type—Type of connector, such as fiber optic.
• Status—Status of the link, such as OK.
• Port Alias—Name used in the device CLI or EMS for the selected port.
• Managed—Whether or not the link is managed: True or False.
When displaying network events, Prime Network Vision monitors the history size value defined in the
Events tab of the Options dialog box (Tools > Options > Events). The default value is six hours and can
be changed in Prime Network Administration. In addition, Prime Network Vision limits the maximum
number of network and provisioning events that are sent from the server to client to 15,000 each. If the
number of network or provisioning events exceeds the limit specified in the Options Events tab or the
15,000 maximum limit, Prime Network Vision purges the oldest events from table. The purging
mechanism runs once per minute.
Tip You can display or hide the ticket and events pane by clicking the arrows displayed below the device
view panel.
Step 1 Select a map or aggregation in the navigation pane, and click Show Links View in the main toolbar. The
links view is displayed in the content pane.
Step 2 In the table toolbar, click Link Filter. The Link Filter dialog box is displayed. For information about the
Link Filter dialog box, see Filtering Links in a Map, page 4-38.
Step 3 In the Filter dialog box:
a. In the Match drop-down list, choose All.
b. In the field drop-down list, choose Link Type.
c. In the operand drop-down list, choose Equals.
d. In the matching criteria drop-down list, choose Physical Layer.
e. Click OK.
Only physical links are displayed in the links view.
Step 4 In the links view, right-click the required link and choose Properties. The Topological Link Properties
window is displayed.
Step 5 Click Calculate Affected. The total number of potentially affected parties is displayed in the Affected
Parties area.
Step 6 Click Show Affected. The Affected Parties window is displayed as shown in Figure 5-6.
Step 7 To view the potentially affected destinations if a link were go to down, click an entry in the Source table.
The potentially affected destinations are displayed in the Destination table.
Step 8 To view source or destination properties in inventory, click the required hyperlinked entry.
Note The Affected Parties window occasionally displays entries that start with the word Misconfigured.
Entries that start with Misconfigured indicate that the flow has stopped unexpectedly between the source
and destination points. An unexpected termination point can be a routing entity, bridge, or VC switching
entity. The significant aspects of Misconfigured entries are:
- Because the link does not terminate as expected, the link is not actually impacted.
- An error might exist in the configuration or status of the termination points.
We recommend that you check the configuration and status of the affected termination points.
To create a static link, select a device or port and define it as the A side. Then define a second device or
port as the Z side. Prime Network Vision validates the new link after the two ports are selected.
Validation checks the consistency of the port types (for example, RJ45 on both sides), and Layer 2
technology type (for example, ATM OC-3 on both sides).
You can also create static links between Ethernet Link Aggregation Groups (LAGs) by choosing a LAG
and the desired port channel for the A or Z side as described in the following procedure.
When you add a new link, the color of the link reflects its current state. For example, if the operation
status of a port is down, the link is colored red. You can add links from either the Prime Network Vision
window’s navigation and a map (method 1), or from the inventory window navigation pane (method 2).
In addition, you can add a new link using Cisco Prime Network Administration. For more information,
see the Cisco Prime Network 3.8 Administrator Guide.
Step 1 Right-click the required A Side device in the navigation pane or in a map, and choose Topology > Mark
as A Side.
Step 2 Right-click the required Z Side device or LAG in the navigation pane or properties pane to display the
right-click menu and choose Topology > Mark as Z Side. The Create Static Link window is displayed
as shown in Figure 5-7, so that you can select the ports to connect.
Step 3 Select the required port on both the A Side device and the Z Side device.
Step 4 Click Create to validate the connection and create the new link.
A success message is displayed.
A warning message is displayed if any of the following apply:
• A validation check fails.
• The operation status of one port is Up and the other port is Down.
• The selected ports are not of the same type.
• The Layer 2 technology type is not the same.
• One of the ports is part of another link.
Step 1 Open the inventory window for the required A Side device.
Step 2 In the navigation pane, navigate to the required port or LAG.
Step 3 Right-click the required port or LAG and choose Topology > Mark as A Side.
Step 4 Repeat Step 1 and Step 2 for the Z Side port or LAG.
Step 5 Right-click the required port or LAG and choose Topology > Mark as Z Side. A confirmation message
is displayed.
Step 6 Click Yes.
The ports are connected, and a link is created between the selected ports.
A warning message is displayed if any of the following conditions exist:
• One of the validation checks fails.
• The operation status of one port is Up and the other port is Down.
• The ports selected are not of the same type.
• The Layer 2 technology type is not the same.
• One of the ports is part of another link.
For information about removing a static link, see the Cisco Prime Network 3.8 Administrator Guide.
Note • The deep collection method is applied by default in the links view.
• The filter applies only to the links view; it has no effect elsewhere in Prime Network Vision.
Step 1 Click Show Links View in the Prime Network Vision main toolbar.
Step 2 Select a map or aggregation in the navigation pane or links view.
Step 3 In the links view toolbar, click one of the following buttons in the toolbar:
• All Links
• External Links
• Flat Links
• Deep Links
The links are displayed in the links view according to the selected collection method.
Selecting a Link
Prime Network Vision enables you to select a link listed in the links view and highlight the link in the
map in the content pane.
To select and highlight a link in a map:
Step 1 In the Links view, right-click the required link and choose Select Link in Map. The link is displayed in
blue in the map.
Step 2 If two or more links are the same (for example, two VRF links), but they are in different contexts or
aggregations, the Select Link Context dialog box is displayed. Select the required context from the
drop-down list, then click OK. The link is displayed in blue in the map.
Step 3 To remove the blue highlight from the selected link, click the map background.
A business tag is a string that is meaningful to the business, and which can be used to label a component
of a network element for use in Prime Network screens and reports.
A business element is a construction or organization of certain network elements and their properties
into a logical entity, to provide the ability to track them in a way that makes sense from a business
perspective. Examples of business elements include Layer 2 VPNs, Layer 3 VPNs, and virtual routers.
The following topics describe how to manage and view Cisco Prime Network Vision business tags and
business elements:
• User Roles Required to Work with Business Tags and Business Elements, page 6-1
• Using Chinese Characters, page 6-3
• Attaching and Detaching Business Tags, page 6-3
• Searching for Business Tags and Viewing Their Properties, page 6-5
• Renaming a Business Element, page 6-8
• Deleting a Business Element, page 6-8
The following tables identify the tasks that you can perform:
• Table 6-1 identifies the tasks that you can perform if a selected element is not in one of your
assigned scopes.
• Table 6-2 identifies the tasks that you can perform if a selected element is in one of your assigned
scopes.
By default, users with the Administrator role have access to all managed elements. To change the
Administrator user scope, see the topic on device scopes in the Cisco Prime Network 3.8 Administrator
Guide.
Table 6-1 Default Permission/Security Level Required for Working with Business Tags and
Business Elements - Element Not in User’s Scope
Table 6-2 Default Permission/Security Level Required for Working with Business Tags and
Business Elements - Element in User’s Scope
Note If you select Label, the name of the network object changes to display the business tag name
if the Replace name with Business Tag option is selected in the Options dialog box (Tools >
Options). For more information about display options, see Selecting Prime Network Vision
Options, page 2-51.
You can search and edit business tag information attached to a network object using tools available from
the appropriate Business Tag dialog box.
A business tag that has been attached to a network object can also be detached. You can detach one more
more business tags at a time.
To detach a business tag:
Step 1 In the Cisco Prime Network Vision window, navigate to the network object that contains the business tag
you want to remove. You can also search for the business tag as described in Searching for Business Tags
and Viewing Their Properties, page 6-5.
Step 2 Right-click the network object and choose Detach Business Tag.
The business tag is detached from the network object and is no longer displayed.
Step 1 Open the Find Business Tag dialog box in one of the following ways:
• Click Find Business Tag in the main toolbar.
• Choose Edit > Find Business Tag from the main menu.
Figure 6-2 shows an example of the Find Business Tag dialog box.
Table 6-3 describes the fields in the Find Business Tag dialog box.
Find Business Tag Finds the business tag according to a name, key, or type entered in
the Find Business Tag dialog box.
Clear Search Clears the search information entered in fields in the Find Business
Tag dialog box.
Edit Business Tag Opens the Edit Business Tag dialog box so you can edit the selected
business tag.
Detach Business Removes the selected business tag from the element.
Tag
Help Displays online help for Cisco Prime Network Vision and
Cisco Prime Network Events.
Input Fields
Unique Key Enter the key you are searching for.
Name Enter a full or partial entry of the name you are searching for.
The search function is case-insensitive, so entering the string
biz tag in the Name field results in business tags with names
containing Biz Tag, Biz tag, and biz tag.
Type From the drop-down list, select the type of business tag you are
searching for: Label, Subscriber, Provider Connection, or All
Types.
Note Enter a full or partial entry of the note for the business tag you are
searching for.
Results Table
Key Business tag key matching the search criteria.
Name Business tag names matching the search criteria.
Type Business tag type matching the search criteria.
Entity Entity to which the business tag is attached, hyperlinked to entity
properties.
Step 2 Enter the search criteria using the information for the Input Fields in Table 6-3, keeping in mind that the
search function is case-sensitive.
Step 3 Click Find. The search results are displayed in the Results Table at the bottom of the Find Business Tag
dialog box, as shown in Figure 6-2.
Step 4 View additional details as required:
• To view the business tag’s properties, double-click the business tag in the search results table.
• To go to the business tag’s location, click the hyperlink provided in the search results table.
Step 1 In the Cisco Prime Network Vision navigation pane or a map, right-click the business element and
choose Rename.
Step 2 In the Rename Node dialog box, enter a new name.
Step 3 Click OK.
The changed business element name appears in the Cisco Prime Network Vision navigation pane and
map.
Caution Deleting business elements affects all users who have the business elements loaded in their service view
map.
Table 6-4 lists the requirements that must be met before you can delete a business element.
Step 1 Verify that the business element meets all requirements specified in Table 6-4. You cannot delete the
element if all requirements are not met.
Step 2 In the Cisco Prime Network Vision navigation pane or a map, right-click the business element, and
choose Delete.
Step 3 In the confirmation message, click Yes to delete the currently selected element, or click Yes to All to
delete multiple selected elements.
The selected business element is deleted from the business configuration of all users.
These topics describe the Cisco Prime Network Events (Prime Network Events) application and the
options you can use to view system events and tickets that are generated within the Prime Network
system:
• User Roles Required to Work with Prime Network Events, page 7-1
• Launching Prime Network Events, page 7-2
• Prime Network Events Window, page 7-3
• Prime Network Events Right-Click Options, page 7-9
• Selecting Prime Network Events Viewing Options, page 7-10
Only users with the Administrator role can log into Prime Network Events (see Table 7-1).
Table 7-1 Default Permission/Security Level Required for Prime Network Events
Note If you do not log into Prime Network Administration, Prime Network Vision, or Prime Network Events
during a specified period of time (the default is one month) from the standalone application, your
account is automatically locked. The default period can be changed per user in Prime Network
Administration. The period of time is measured from the time you last logged out of any of the Prime
Network client applications. For more information about changing the default period and unlocking an
account, see the Cisco Prime Network 3.8 Administrator Guide.
The following conditions apply when working with Prime Network Events:
• Prime Network Events shows events only from the fault database and not from the event archive.
Use Report Manager to view events from the event archive. For more information, see Chapter 10,
“Working with Reports.”
• Only users with the Administrator role can log into Prime Network Events.
The following topics describe how to launch Prime Network Events:
• Launching Prime Network Events from Prime Central, page 7-3
• Launching Prime Network Events as a Standalone Application, page 7-3
Step 1 Choose Start > Programs > Cisco Prime Network > gateway hostname/IP address >Cisco Prime
Network Events.
Note The hostname/IP address corresponds to the gateway on which Prime Network was configured.
Prime Network Events displays events for the last two days by default. To modify the default number of
days for which events are displayed, see Selecting Prime Network Events Viewing Options, page 7-10.
Increasing the number of days can affect how long it takes for the events to be displayed.
You can display the events table with or without the properties pane, and select the specific type of
information to display, such as provisioning events or SNMPv3 traps. For details on the information that
is displayed in each tab, see Viewing Events and Tickets in Cisco Prime Network Events, page 8-2.
You can also use the Prime Network Events window and menu options to:
• Filter results so that events meeting your criteria are displayed. See Filtering Events, page 8-22.
• View selected event properties in a separate window. See Viewing Event Properties, page 8-14.
Orange Major
Yellow Minor
Tab Description
Audit Events related to commands running in the Prime Network gateway.
Provisioning Events related to configuration and provisioning activities,
including activations from Prime Network Activation.
Security Events related to client login and user activity when managing the
system and the environment.
Service Events related to the alarms that are generated by the Prime
Network system.
Syslog Events related to the predefined set of syslogs received from the
devices by the VNEs, which are used to generate the syslog events.
System Events related to the everyday working of the internal system and
its components. These events may be related to Prime Network and
Prime Network gateway resources, representing the system log.
Ticket Tickets that were opened in Prime Network.
V1 Trap SNMPv1 traps that are generated by a network element and
received by Prime Network; Prime Network uses these traps to
generate the trap events.
V2 Trap SNMPv2 traps that are generated by a network element and
received by Prime Network; Prime Network uses these traps to
generate the trap events.
V3 Trap SNMPv3 traps that are generated by a network element and
received by Prime Network; Prime Network uses these traps to
generate the trap events.
All A flat list of all events and tickets, sorted by time.
Displayed when you choose File > Open All Tab.
3.6.x Type Five tabs where Type represents one of the following:
• Ticket
• Service
• Syslog
• V1 Trap
• V2-V3 Trap
These tabs are:
• Available only if Prime Network was upgraded from
Cisco ANA 3.6.x to the current Prime Network version.
• Displayed when you choose File > Open 3.6.x Tabs.
Button Function
Displays the previous page of events in the Prime Network Events window.
Displays the next page of events in the Prime Network Events window.
Refreshes the events displayed in the log by querying the database. If a filter is active, the
refresh is done according to the filter. The log returns to the beginning of the list,
displaying the events in ascending or descending order depending on the order of the
current list. Descending order means that the last event is displayed first. For more
information, see Refreshing Cisco Prime Network Events Information, page 8-21.
Displays the Filter Events dialog box, which enables you to define a filter for the events
displayed in the Prime Network Events log. For more information, see Filtering Events,
page 8-22.
Clears the existing filter.
Displays the Find Events dialog box so that you can view events matching specific
criteria. When finished selecting your criteria, click OK. The Prime Network Events
window updates and displays the matching events. Note the following:
• You can select multiple criteria here, as needed.
• The Find Events dialog box returns every matching event in the database unless you
specify a specific timeframe. This differs from the Filter Events dialog box, which
returns events from the past 2 days (by default).
For a description of the items in the Find Events dialog box, see Table 8-23 on page 8-24.
Toggles automatic refresh of event data on and off. You define the refresh-time period (in
seconds) in the Prime Network Events Options dialog box. The default is 60 seconds. If a
filter is active, the refresh is done according to the filter. For more information, see
Selecting Prime Network Events Viewing Options, page 7-10.
Displays the properties of the selected event or ticket in the Properties pane.
Option Description
Save last filter Saves the filter criteria defined per event type in the Filter Events dialog box. The
filter criteria are available the next time you log into Prime Network Events.
Note Events are not filtered automatically when you next log into Prime
Network Events unless the Open Events with saved filter option is also
selected.
Open Events with When enabled, applies the previously defined filter to the events as soon as you
saved filter log into Prime Network Events. The events are continuously filtered according
to the defined settings, even after you close the application.
Show n events Specifies the number of events to be displayed per page.
per page
Export n events Sets the maximum number of events to be exported to a file.
in total
Option Description
Run auto refresh Automatically refreshes the Prime Network Events display after the specified
every n secs number of seconds.
Note This option uses rapid refresh from the database, which can affect the
performance of other vital database options.
Display events for Displays past events from the specified number of days. Values range from 1 to
the last n days 14 days, with a default of 2 days.
If you increase the number of days, it can take longer for the events to be
displayed.
The following topics describe how to use Cisco Prime Network Events (Prime Network Events) to track
faults:
• User Roles Required to Work with Prime Network Events, page 8-1
• Viewing Events and Tickets in Cisco Prime Network Events, page 8-2
• Viewing 3.6.x Tabs, page 8-12
• Working with Cisco Prime Network Events, page 8-14
Table 8-1 Default Permission/Security Level Required for Cisco Prime Network Events
Note Cisco Prime Network Events shows events only from the fault database and not from the event
archive. Use Report Manager to view events from the event archive. For more information, see
Chapter 10, “Working with Reports.”
The Ticket tab displays the tickets that have been generated for correlated events.
Events and tickets are sorted by date, with the latest item displayed first and the oldest item displayed
last.
Note Prime Network stores events in the database in Greenwich Mean Time (GMT) format. The
Prime Network client converts events to the time zone that is configured on the client
workstation. The times displayed in the Cisco Prime Network Events GUI reflect the time
according to the client workstation.
By using the Cisco Prime Network Events Options dialog box, you can define a filter to be used or the
number of items to be displayed in the list. Each tab displays the specified number of entries per page
as defined in the Cisco Prime Network Events Options dialog box.
For more information, see Selecting Prime Network Events Viewing Options, page 7-10.
Because the lists of events and tickets can be lengthy, you can use the left and right arrows on the
navigation to move through the records. You can also use the submenus that are available from
View > Go To in the main menu.
All Tab
The All tab displays information about all events. Additional information specific to the event category
can be viewed in the Event Properties window or individual category tabs.
When you launch Cisco Prime Network Events, the All tab is not displayed. You can view this tab by
choosing File > Open All Tab.
Note When you open the All tab, it might take some time to retrieve information from the Prime Network
database for all category events.
You can disable the All tab by following the instructions provided in the Cisco Prime Network 3.8
Installation Guide.
Table 8-2 describes the information that is displayed in the All tab.
Column Description
Severity Icon indicating the severity of the alarm on the event (the color and type
of alarm are displayed in the Properties window Severity field). See
Event Status Indicators, page 7-5.
Event ID Event identifier, assigned sequentially.
Time Date and time when the event occurred and was logged and recorded.
Description Description of the event.
Location Entity that triggered the event.
Event Type Type of event: Audit, Provisioning, Security, Service, Syslog, System,
V1 Trap, V2 Trap, or V3 Trap.
Audit Tab
The Audit tab displays all events generated for each command or request in Prime Network; for example,
opening Cisco Prime Network Events displays the Get command as shown in Figure 8-1.
Table 8-3 describes the information that is displayed in the Audit tab.
Column Description
Severity Icon indicating the severity of the alarm on the event (the color and type
of alarm are displayed in the Properties window Severity field). See
Event Status Indicators, page 7-5.
Event ID Identifier of the event, assign sequentially.
Time Date and time when the event happened and was logged and recorded.
Description Aggregation of portions of the same fields in the Audit Command fields.
Command Name Audit-specific command name, prefaced by, for example, Get, Update,
or Find.
Command Signature Actual command run by Prime Network, such as
GetEventViewerProperties.
Command Parameters Command parameters issued with the command identified in the
Command Name column.
Originating IP IP address of the client that issued the command
User Name Name of the user who initiated the command.
The audit service enables you to audit all the commands executed in the system; for example, the Get
command can be audited. The Audit tab then displays this information.
Provisioning Tab
Events displayed in the Provisioning tab are events triggered during the configuration of a device. Prime
Network sends an event explaining the configuration operation, such as configuring the cross-connect
table in a device. The Provisioning tab displays detailed information specific to this event category. It
contains events from Prime Network Command Builder, Prime Network Activation, and Prime Network
Workflow Editor1.
Additional information specific to this event category can be viewed in the Event Properties window.
If a provisioning event is the result of an activation script, the provisioning event can include an
extremely long description. This description is displayed in the Event Properties window in the Details
field. If the description exceeds the size of the Details field, Prime Network truncates the description in
the database and Details field, and displays the following line to indicate that the description has been
truncated:
=====CONTENT TRUNCATED BY CISCO PRIME NETWORK=====
Table 8-4 describes the information that is displayed in the Provisioning tab.
Column Description
Severity Icon indicating the severity of the alarm on the event (the color and type
of alarm are displayed in the Properties window Severity field). See
Event Status Indicators, page 7-5.
Event ID Identifier of the event, assigned sequentially.
Time Date and time when the event happened and was logged and recorded.
Description Description of the event, such as “Script Show has failed.”
Location Entity that triggered the event.
Username Name of the user who performed the provisioning operations.
Status Status, such as Success or Fail.
Security Tab
The Security tab displays detailed information specific to this event category. Security events are related
to client login and user activity when managing the system and the environment. Additional information
specific to this event category can be viewed in the Event Properties window.
Table 8-5 describes the information that is displayed in the Security tab.
Column Description
Severity Icon indicating the severity of the alarm on the event (the color and type
of alarm are displayed in the Properties window Severity field). See
Event Status Indicators, page 7-5.
Event ID Identifier of the event, assigned sequentially.
Time Date and time when the event happened and was logged and recorded.
Column Description
Description Description of the event, such as “Invalid password. Couldn’t
authenticate user root.”
Location Entity that triggered the event.
Username Name of the user who triggered the event.
Originating IP IP address of the client where the event was triggered.
For more information about the system security events displayed in this tab, see the Cisco Prime
Network 3.8 Reference Guide.
System Tab
The System tab displays all the system events related to the everyday working of the internal system and
its components. These events can be related to Prime Network and Prime Network gateway resources,
representing the system log. Additional information specific to this event category can be viewed in the
Event Properties window.
Table 8-6 describes the information that is displayed in the System tab.
Column Description
Severity Icon indicating the severity of the alarm on the event (the color and type
of alarm are displayed in the Properties window Severity field). See
Event Status Indicators, page 7-5.
Event ID Identifier of the event, assigned sequentially.
Time Date and time when the event happened and was logged and recorded.
Description Description of the event, such as “AVM 77 is shutting down. Unit =
11.22.33.444.”
Location Entity that triggered the event.
For more information about the system error and event messages displayed in this tab, see the
Cisco Prime Network 3.8 Reference Guide.
Service Tab
The Service tab displays all the events generated by Prime Network, such as Link Down. Service events
are related to the alarms that are generated by the Prime Network system. Additional information
specific to this event category can be viewed in the Event Properties window.
Table 8-7 describes the information that is displayed in the Service tab.
Column Description
Severity Icon indicating the severity of the alarm on the event (the color and type
of alarm are displayed in the Properties window Severity field). See
Event Status Indicators, page 7-5.
Event ID Calculated correlation identifier.
Time Date and time when the event happened and was logged and recorded.
Description Description of the event, such as “Port down due to oper.”
Location Hyperlink to the entity that triggered the event.
Alarm ID Hyperlinked identifier of the alarm associated with the event. Click the
link to view the Ticket Properties window.
Ticket ID Hyperlinked identifier of the ticket associated with the event. Click the
link to view the Ticket Properties window.
Causing Event ID Identifier of the causing event.
Duplication Count For network events, the duplication count is calculated by the VNE and
pertains only to flapping events. The duplication count represents the
number of noncleared events aggregated by the flapping event.
Reduction Count For network events, the reduction count is calculated by the VNE and
pertains only to flapping events. The reduction count represents the
number of events that are aggregated by the flapping event.
For more information about the service alarms that are displayed in this tab, see the Cisco Prime Network
3.8 Reference Guide.
Syslog Tab
The Syslog tab displays all the syslog events. These events are related to the predefined set of syslogs
received from the devices by the VNEs, which are used to generate the syslog events. Additional
information specific to this event category can be viewed in the Event Properties window.
Table 8-8 describes the information that is displayed in the Syslog tab.
Column Description
Severity Icon indicating the severity of the alarm on the event (the color and type
of alarm are displayed in the Properties window Severity field). See
Event Status Indicators, page 7-5.
Event ID Calculated correlation identifier.
Time Date and time when the event happened and was logged and recorded.
Description Description of the event, such as “Device configuration changed.”
Location Hyperlink to the entity that triggered the event.
Alarm ID Identifier of the alarm associated with the event.
Ticket ID Identifier of the ticket associated with the event.
Causing Event ID Identifier of the causing event.
Duplication Count For network events, the duplication count is calculated by the VNE and
pertains only to flapping events. The duplication count represents the
number of noncleared events aggregated by the flapping event.
Reduction Count For network events, the reduction count is calculated by the VNE and
pertains only to flapping events. The reduction count represents the
number of events that are aggregated by the flapping event.
Ticket Tab
The Ticket tab displays detailed information specific to tickets. A ticket contains a single root alarm (the
root cause alarm can be of any alarm type, such as syslog or service), and all its subsequent correlated
alarms. Additional information specific to tickets can be viewed in the Ticket Properties window.
A Tickets capacity overflow, red threshold reached system alarm is generated when the maximum
number of tickets is exceeded. The alarm severity is defined as critical.
Table 8-9 describes the information that is displayed in the Ticket tab.
Column Description
Severity Icon indicating the severity of the alarm on the ticket (the color and type
of alarm are displayed in the Ticket Properties window Severity field).
See Event Status Indicators, page 7-5.
Ticket ID Sequentially assigned identifier of the ticket, hyperlinked to the Ticket
Properties window.
Last Modification Time Date and time (per the database) that the ticket was last updated.
Updates can result from either manual or automatic operations.
Root Event Time Date and time that the event that created the root cause alarm of the
ticket was detected.
Description Description of the event, such as “Layer 2 tunnel down.”
Location Hyperlink to the entity that triggered the event.
Acknowledged Whether the ticket is acknowledged or has been modified: Yes, No, or
Modified.
Creation Time Date and time that the ticket was created.
Event Count Number of events associated with the ticket.
Affected Devices Count Number of devices affected by the ticket (the sources of the alarm and
their subsequent alarms).
Duplication Count For tickets, the duplication count is the sum of the duplication counts of
all events that are associated with the root alarm.
Reduction Count Ticket reduction count is the sum of reduction counts of all the events
that are associated to the ticket. The History tab in the Ticket Properties
window displays one reduction count for each event listed. For more
information, see Chapter 9, “Working with Tickets in Cisco Prime
Network Vision.”
Alarm Count Total number of alarms associated with the ticket, including the root
alarm.
For information about viewing ticket properties, see Viewing Ticket Properties, page 8-19.
V1 Trap Tab
This event is triggered when the network element sends a trap message to Prime Network because of a
network event, such as Link Down. The V1 Trap tab displays detailed information specific to this
category. Additional information specific to each event category can be viewed in the Event Properties
window.
Table 8-10 describes the information that is displayed in the V1 Trap tab.
Column Description
Severity Icon indicating the severity of the alarm on the event (the color and type
of alarm are displayed in the Properties window Severity field). See
Event Status Indicators, page 7-5.
Event ID Calculated correlation identifier.
Time Date and time when the event happened and was logged and recorded.
Description Description of the event, such as “Enterprise generic trap.”
Location Hyperlink to the entity that triggered the trap.
Alarm ID Identifier of the alarm associated with the event, hyperlinked to the
Alarm Properties window.
Ticket ID Hyperlinked sequential identifier of the ticket. Click the link to view the
Ticket Properties window.
Causing Event ID Identifier of the causing event, hyperlinked to the Network Event
Properties window.
Duplication Count For network events, the duplication count is calculated by the VNE and
pertains only to flapping events. The duplication count represents the
number of noncleared events aggregated by the flapping event.
Reduction Count For network events, the reduction count is calculated by the VNE and
pertains only to flapping events. The reduction count represents the
number of events that are aggregated by the flapping event.
For more information about the Cisco IOS and Cisco IOX traps displayed in one of these tabs, see the
Cisco Prime Network 3.8 Reference Guide.
V2 Trap Tab
This event is triggered when the network element sends a trap message to Prime Network because of a
network event. The V2 Trap tab displays detailed information specific to this category. Additional
information specific to each event category can be viewed in the Event Properties window.
Table 8-11 describes the information that is displayed in the V2 Trap tab.
Column Description
Severity Icon indicating the severity of the alarm on the event (the color and type
of alarm are displayed in the Properties window Severity field). See
Event Status Indicators, page 7-5.
Event ID Calculated correlation identifier.
Time Date and time when the event happened and was logged and recorded.
Description Description of the event, such as “SNMP authentication failure.”
Location Hyperlink to the entity that triggered the trap.
Alarm ID Identifier of the alarm associated with the event, hyperlinked to the
Alarm Properties window.
Ticket ID Sequential identifier of the ticket, hyperlinked to the Ticket Properties
window.
Causing Event ID Identifier of the causing event, hyperlinked to the Network Event
Properties window.
Duplication Count For network events, the duplication count is calculated by the VNE and
pertains only to flapping events. The duplication count represents the
number of noncleared events aggregated by the flapping event.
Reduction Count For network events, the reduction count is calculated by the VNE and
pertains only to flapping events. The reduction count represents the
number of events that are aggregated by the flapping event.
Trap Type OID Trap object identifier.
Translated Enterprise Translation of the OID using the MIB. For example, an enterprise OID
of .1.3.6.1.2.1.88.2 is displayed in this column as
.iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.dismanEventMIB
NotificationPrefix.
Enterprise Enterprise OID for the trap, representing the company or organization
that is associated with the trap.
For more information about the Cisco IOS and Cisco IOX traps displayed in this tab, see the Cisco Prime
Network 3.8 Reference Guide.
V3 Trap Tab
This event is triggered when the network element sends a trap message to Prime Network because of a
network event. The V3 Trap tab displays detailed information specific to this category. Additional
information specific to each event category can be viewed in the Event Properties window.
Table 8-12 describes the information that is displayed in the V3 Trap tab.
Column Description
Severity Icon indicating the severity of the alarm on the event (the color and type
of alarm are displayed in the Properties window Severity field). See
Event Status Indicators, page 7-5.
Event ID Calculated correlation identifier.
Time Date and time when the event happened and was logged and recorded.
Description Description of the event, such as “Enterprise generic trap.”
Location Hyperlink to the entity that triggered the trap.
Alarm ID Identifier of the alarm associated with the event, hyperlinked to the
Alarm Properties window.
Ticket ID Sequential identifier of the ticket, hyperlinked to the Ticket Properties
window.
Causing Event ID Identifier of the causing event, hyperlinked to the Network Event
Properties window.
Duplication Count For network events, the duplication count is calculated by the VNE and
pertains only to flapping events. The duplication count represents the
number of noncleared events aggregated by the flapping event.
Reduction Count For network events, the reduction count is calculated by the VNE and
pertains only to flapping events. The reduction count represents the
number of events that are aggregated by the flapping event.
Trap Type OID Trap object identifier.
Translated Enterprise Translation of the OID using the MIB. For example, an enterprise OID
of .1.3.6.1.2.1.88.2 is displayed in this column as
.iso.org.dod.internet.mgmt.mib-2.dismanEventMIB.dismanEventMIB
NotificationPrefix.
Enterprise Enterprise OID for the trap, representing the company or organization
that is associated with the trap.
For more information about the Cisco IOS and Cisco IOX traps displayed in this tab, see the Cisco Prime
Network 3.8 Reference Guide.
Table 8-13 describes the information that is displayed in each of the 3.6.x tabs.
Field Description
3.6.x Ticket Tab
Severity Icon of a bell, colored according to the severity of the alarm on the
ticket. For more information, see Event Status Indicators, page 7-5.
Ticket ID Sequentially assigned identifier of the ticket.
Short Description Description of the event.
Location Hyperlink to the entity that triggered the event.
Last Modification Time Date and time (per the database) that the ticket was last updated.
Updates can result from either manual or automatic operations.
Time Date and time recorded when the first event happened.
Acknowledged Status of the ticket: Acknowledged, Not Acknowledged, or
Modified.
Affected Devices Count Number of devices affected by the ticket (the sources of the alarm
and their subsequent alarms).
Correlation Count Number of correlated alarms included in the ticket.
Reduction Count Ticket reduction count is the sum of reduction counts of all the
events that are associated to the ticket. The History tab in the Ticket
Properties window displays one reduction count for each event
listed. For more information, see Chapter 9, “Working with Tickets
in Cisco Prime Network Vision.”
Duplication Count For tickets, the duplication count is the sum of the duplication
counts of all events that are associated with the root alarm.
3.6.x Service Tab
Severity Icon of a bell, colored according to the severity of the alarm. For
more information, see Event Status Indicators, page 7-5.
Alarm ID Sequentially assigned identifier of the alarm.
Short Description Description of the event.
Location Hyperlink to the entity that triggered the event.
Time Date and time recorded when the first event happened.
3.6.x Syslog Tab
Severity Icon of a bell, colored according to the severity of the alarm. For
more information, see Event Status Indicators, page 7-5.
Alarm ID Sequentially assigned identifier of the alarm.
Short Description Description of the event.
Location Hyperlink to the entity that triggered the event.
Time Date and time recorded when the first event happened.
Field Description
3.6.x V1 Trap Tab
Severity Icon of a bell, colored according to the severity of the alarm. For
more information, see Event Status Indicators, page 7-5.
Alarm ID Sequentially assigned identifier of the alarm.
Short Description Description of the event.
Location Hyperlink to the entity that triggered the event.
Time Date and time recorded when the first event happened.
Suppress Display Whether or not the display of the alarm is suppressed.
3.6.x V2-V3 Trap Tab
Severity Icon of a bell, colored according to the severity of the alarm. For
more information, see Event Status Indicators, page 7-5.
Alarm ID Sequentially assigned identifier of the alarm.
Short Description Description of the event.
Location Hyperlink to the entity that triggered the event.
Time Date and time recorded when the first event happened.
Suppress Display Whether or not the display of the alarm is suppressed.
Tip Clicking Detailed Pane on the displays the properties of the selected ticket or event in the Properties
pane.
Step 1 Select the required tab for the specific event type and the event in the Cisco Prime Network Events
window.
Step 2 Do one of the following:
• Double-click the event in the events list.
• Click Detailed Pane in the toolbar.
• Choose View > Properties from the main menu.
• Right-click the event and choose Properties.
The event properties are displayed for the selected event, either in the lower portion of the Cisco Prime
Network Events window or in a separate window as shown in Figure 8-2. The Details tab is displayed
by default.
Table 8-14 describes the information that is displayed in the Details tab in the Event Properties window.
Field Description
Event ID Unique identifier for the selected event.
Severity Severity of the event, indicated by color and text label.
Description Description of the event.
Time Date and time when the event happened and was logged and
recorded.
Location Entity that triggered the event, hyperlinked to its entry in inventory.
Type Type of event, such as Security or Service.
Ticket ID This field is displayed only for network events.
Sequential identifier of the ticket, hyperlinked to the Ticket
Properties window.
Alarm ID This field is displayed only for network events.
Alarm identifier, hyperlinked to the Ticket Properties window.
Causing Event This field is displayed only for network events.
The identifier of the causing event.
Details Detailed description of the event.
Field Description
Duplication Count For network events, the duplication count is calculated by the VNE
and pertains only to flapping events. The duplication count
represents the number of noncleared events aggregated by the
flapping event.
Reduction Count For network events, the reduction count is calculated by the VNE
and pertains only to flapping events. The reduction count represents
the number of events that are aggregated by the flapping event.
Affected Devices The number of devices affected by the ticket.
Alarm Count The total number of alarms associated with the ticket, including the
root alarm.
Field Description
User Name Name of user who initiated the command.
Result Command result, if available.
Originating IP IP address of the client that issued the command.
Command Signature Actual command run by Prime Network, such as
GetEventViewerProperties.
Command Parameters Parameters applied to the command.
Field Description
User Name Name of the user who performed the provisioning operation.
Status Status of the operation: Success or Fail.
Field Description
User Name Name of the user who triggered the event.
Client Type Client that triggered the event: Cisco Prime Network Vision,
Cisco Prime Network Administration, Cisco Prime Network
Events, or Unknown.
Originating IP IP address of the client where the event was triggered.
Field Description
Version SNMP version: version-1, version-2c, or version-3.
Community String Community that the device sends in the Protocol Data Unit (PDU).
Error Status Error status: No Error, Too Big, No Such Name, Bad Value, Read Only,
and Gen Err.
Values Table
Translated OID String representation of the OID. For example, 1.3.6 is translated into
iso.org.dod where:
• 1 represents iso.
• 3 represents org.
• 6 represents dod.
Translated Value String representation of the OID value. For example, 1.3 is translated to
iso(1).org.10, or a specific value, such as “down” or “4 days, 20 hours,
32 minutes, 11 seconds.”
OID OID that is not translated. It is a dot notation representation of the OID,
such as 1.3.6.1.4.1.9.
Value Value that is not translated.
The properties of a selected ticket can be viewed in the Ticket Properties window. For a detailed
description of the Ticket tab properties, see Viewing Ticket Properties, page 8-19.
Step 1 In the Ticket tab in the Cisco Prime Network Events window, select the required ticket.
Step 2 Do one of the following:
• Double-click the ticket.
• Click Detailed Pane in the toolbar.
• Choose View > Properties from the main menu.
• Right-click the ticket and choose Properties.
The properties are displayed for the selected ticket, either in the lower portion of the Cisco Prime
Network Events window or in a separate window as shown in Figure 8-3.
Table 8-20 describes the information that is displayed in the Details tab in the Ticket Properties window.
Field Description
Buttons
Acknowledge Acknowledges that the ticket is being handled. The status of the
ticket is displayed as true in the ticket pane and in the Ticket
Properties dialog box. For more information, see Acknowledged
Ticket, page 9-6.
If a ticket is acknowledged, and events are correlated to it after
correlation, the ticket is considered to have not been acknowledged.
This button is enabled only if the ticket is not acknowledged.
Clear Requests the Prime Network system to remove the faulty network
element from the Prime Network networking inventory. In addition,
it sets the ticket to Cleared severity or status and automatically
changes the acknowledged status of the ticket to Yes. For more
information, see Cleared Ticket, page 9-6.
This button is enabled only if the severity of the alarm is higher than
Cleared or Normal.
Details Tab
Ticket ID Sequentially assigned identifier of the ticket.
Severity Severity of the ticket, indicated by color and text label.
Description Description of the ticket.
Last Modification Time Date and time (per the database) that the ticket was last updated.
Updates can result from either manual or automatic operations.
Location Hyperlink to the entity that triggered the event.
Note If the entity that triggered the event is outside your scope, a
message is displayed that states you do not have permission
to access the selected item.
Open Alarms Number of open alarms out of all alarms, such as 3/4.
Root Event Time Date and time that the event that created the root cause alarm of the
ticket was detected.
Acknowledged Whether or not the ticket has been acknowledged: Yes or No.
Creation Time Date and time when the ticket was created.
Details Detailed description of the ticket.
Tab Description
History Contains the history of the ticket, including all the events.
For more information, see History Tab, page 9-13.
Affected Parties The services (affected pairs) that are potentially affected (potential impact
analysis) by the ticket.
For more information, see Affected Parties Tab, page 9-14.
Correlation Displays all alarms that are correlated to the selected ticket.
For more information, see Correlation Tab, page 9-17.
Advanced The number of affected devices, correlations, duplications, and reductions for the
selected ticket. In addition, it provides any other additional information available
about the ticket.
For more information, see Advanced Tab, page 9-18.
Notes Enables you to add and save notes for the selected ticket.
The Notes tab is not available for tickets that have been archived.
For more information, see Notes Tab, page 9-18.
Auto Refresh Automatically refreshes the events list. The Auto Refresh icon toggles to
indicate whether auto refresh is on or off. This icon indicates auto refresh
is on.
Filtering Events
The Filter Events dialog box allows you to filter events according to a number of criteria including
severity, identifier, time stamp, description, location, and category-specific information.
You may also use the filter to search for information in the database.
The Filter icon toggles to indicate that a filter has been applied.
The following settings in the Cisco Prime Network Events Options dialog box also affect your filters:
• If you check the Keep Last Filter check box, the currently defined filter settings are saved in the
registry and are displayed the next time you log in, but are not applied.
• If you check the Open Using Filter check box, the events are continuously filtered according to the
defined settings, even when you log out of and back into the application.
For more information, see Selecting Prime Network Events Viewing Options, page 7-10.
See the following topics for more information about filtering events:
• Defining Filters, page 8-23
• Removing Filters, page 8-24
For information about filtering tickets, see Filtering Tickets by Criteria, page 9-7.
Defining Filters
To define a filter:
Step 2 Specify the filter criteria by using the following steps and the information in Table 8-23:
a. Check the check box for each criterion to use for filtering.
b. As needed, choose the operator for the filter, such as Contains or Does Not Contain.
c. Supply the specific information to apply to the filter, such as the time, a string, or one or more IP
addresses.
Field Description
Severity Severities to be included in the filter.
General
Event ID Event identifier to apply to the filter.
Description String to include or exclude.
Location Network elements to include.
This field is not displayed for Audit events.
Time Beginning and ending dates and times to apply to the filter.
Network Events Advanced Options
Alarm ID Alarm identifier to apply to the filter.
Causing Event ID Identifier of the causing event to apply to the filter.
Ticket ID Ticket identifier to apply to the filter.
Duplication Count Duplication count value to use for filtering.
Reduction Count Reduction count value to use for filtering.
Archived Archive status to use for filtering: True or False.
System Events Advanced Options
Command Name String in the command name to use for filtering.
Command Signature String in the command signature to use for filtering.
Command Parameters String in a command parameter to use for filtering.
Originating IP Originating IP address to include or exclude from filtering.
Status Status to use for filtering: Configuring, Fail, Success, or Unknown.
User Name String in the username to use for filtering.
Step 3 Click OK to save your filter settings and apply the filter. The filtered entries are displayed in the list
according to the defined criteria.
Removing Filters
To remove a filter:
The following topics describe viewing tickets in Cisco Prime Network Vision (Prime Network Vision),
how to manage tickets that represent fault scenarios of selected devices or network elements, and fault
impact analysis:
• User Roles Required to Work with Tickets in Prime Network Vision, page 9-1
• Viewing Tickets in Prime Network Vision, page 9-4
• Viewing Ticket Properties, page 9-10
• Managing Tickets, page 9-19
• Impact Analysis in Prime Network, page 9-21
Table 9-1 Default Permission/Security Level Required for Working with Tickets in Prime
Network Vision - Source of Selected Ticket Not in User’s Scope
Table 9-2 Default Permission/Security Level Required for Working with Tickets in Prime
Network Vision - Source of Selected Ticket in User’s Scope
The ticket pane enables you to view and manage tickets as well as find the elements affected by a ticket.
All tickets that are reported by Prime Network Vision are stored in the Prime Network gateway database.
The ticket pane is displayed beneath the navigation and content panes in the Prime Network Vision
window. You can view or hide the ticket pane by clicking the arrows displayed below the navigation
pane.
Note Prime Network stores events in the database in Greenwich Mean Time (GMT) format. The Prime
Network client converts events to the time zone that is configured on the client workstation. The times
displayed in the Prime Network Vision GUI reflect the time according to the client workstation.
For more information about the information available in the ticket pane, see Table 2-14 on page 2-25.
The ticket pane enables you to perform the following tasks:
Generated Ticket
Table 9-3 shows an example of the appearance of the ticket pane when a ticket is generated.
Cleared Ticket
Table 9-4 shows an example of the appearance of the ticket pane when a ticket is cleared.
A ticket that has been cleared can be removed from the ticket pane.
When a ticket is cleared, its definition automatically changes to acknowledged in the ticket pane and its
definition in the Acknowledged column is Acknowledged.
Acknowledged Ticket
Table 9-5 shows an example of the appearance of the ticket pane when a ticket is acknowledged. When
a ticket is acknowledged it can then be cleared and the severity changes to Normal.
Note When a ticket with an Information severity is acknowledged, the ticket is automatically removed from
the Prime Network gateway and from the ticket pane.
Generated Up Ticket
The cause of the alarm is fixed; therefore an Up ticket is automatically generated with a Normal severity.
Table 9-6 shows an example of the appearance of the ticket pane when an Up ticket is generated.
Step 1 Click Ticket Filter in the ticket pane toolbar. The Ticket Filter dialog box is displayed (Figure 9-2).
Step 2 Specify the filter criteria by using the following steps and the information in Table 9-7:
a. Check the check box for each criterion to use for filtering.
b. As needed, choose the operator for the filter, such as Contains or Does Not Contain.
c. Supply the specific information to apply to the filter, such as the time, a string, or one or more IP
addresses.
Field Description
Severity Severity to be included in the filter.
General
Ticket ID Ticket identifier to be included or excluded when filtering.
Description String in the ticket description to include or exclude.
Location Network elements to include.
Root Event Time Beginning and ending dates and times of the range for the root event time to
apply to the filter.
Last Modification Time Beginning and ending dates and times of the range for the ticket last
modification time to apply to the filter.
Creation Time Beginning and ending dates and times of the range for the ticket creation
time to apply to the filter.
Advanced
Acknowledged Ticket acknowledgement status to include in the filter: Acknowledged, Not
Acknowledged, or Modified.
Event Count Event count value to use for filtering.
Affected Devices Count Number of affected devices to use for filtering.
Duplication Count Duplication count value to use for filtering.
Reduction Count Reduction count value to use for filtering.
Alarm Count Alarm count value to use for filtering.
Archived Archive status to use for filtering: True or False.
Step 3 Click OK. The tickets are displayed in the ticket pane according to the defined criteria.
Note The Ticket Filter button in the ticket pane toggles to indicate that a filter has been applied.
Step 1 Click Ticket Filter in the ticket pane toolbar. The Ticket Filter dialog box is displayed.
Step 2 Click Clear. The selected options in the Ticket Filter dialog box are cleared.
Step 3 Click OK. All the tickets are displayed in the ticket pane.
The information displayed in the Ticket Properties window corresponds with the information displayed
in the Prime Network Vision ticket pane or the Prime Network Vision window. The ID number displayed
in the header corresponds to the ID number of the ticket selected in the ticket pane.
Icon Description
Acknowledges that the ticket is being handled. The status of the ticket is displayed
as true in the ticket pane and in the Ticket Properties dialog box. For more
information, see Acknowledged Ticket, page 9-6.
If a ticket was acknowledged, and some events were correlated to it afterward,
then the ticket is considered to have not been acknowledged.
This button is enabled only if the ticket is not acknowledged.
Requests the relevant Prime Network system to remove the faulty network
element from the Prime Network networking inventory. In addition, it sets the
ticket to Cleared severity or status (the icon is displayed in green) and
automatically changes the acknowledged status of the ticket to true. For more
information, see Cleared Ticket, page 9-6.
This button is enabled only if the severity of the alarm is higher than Cleared or
Normal.
Saves the notes for the selected ticket.
This button is enabled only when text is entered in the Notes field of the Notes tab.
Details Tab
Table 9-9 describes the information that is displayed in the Details tab about the compiled alarm.
Field Description
Ticket ID Ticket identifier.
Severity Severity propagated from all the correlated alarms.
Description Description of the ticket.
Last Modification Time Date and time (per the database) that the ticket was last updated.
Updates can result from either manual or automatic operations.
Location Entity that triggered the root-cause alarm, as a hyperlink that opens the
relevant location.
Note If the entity that triggered the alarm is outside your scope, a
message is displayed that states you do not have permission to
access the selected item.
Open Alarms Number of correlated alarms for the ticket that are open, such as 3/4. In
this example, four indicates the total number of correlated alarms for the
ticket, and three indicates the number of alarms that have not been
cleared. Therefore, one alarm has been cleared.
Root Event Time Date and time that the event that created the root cause alarm of the
ticket was detected.
Acknowledged Whether the alarm has been acknowledged: Yes or No.
Creation Time Date and time the ticket was created.
Details Detailed description of the alarm.
History Tab
The History tab enables you to display the history of the ticket, including all the events. Figure 9-4 shows
the History tab.
Table 9-10 describes the information that is displayed in the History tab.
Field Description
Severity Severity bell icon, colored according to the severity of the alarm.
Event ID Event identifier of the specific alarm.
Time Date and time the event was received by the Event Collector.
Description Description of the event.
Location Entity that triggered the alarm, as a hyperlink that opens the relevant
location.
Note If the entity that triggered the alarm is outside your scope, a
message is displayed that states you do not have permission to
access the selected item.
Alarm ID Alarm identifier.
Ticket ID Ticket identifier.
This field appears in the History tab only in Prime Network Events.
Causing Event ID Identifier of the causing event for the ticket.
Duplication Count For network events, the duplication count is calculated by the VNE and
pertains only to flapping events. The duplication count represents the
number of noncleared events aggregated by the flapping event.
Reduction Count For network events, the reduction count is calculated by the VNE and
pertains only to flapping events. The reduction count represents the
number of events that are aggregated by the flapping event.
Detail panel Long description of the selected event.
The Affected Parties tab contains two tables: Source and Destination. Table 9-11 describes the
information that is displayed in the Affected Properties tab.
Field Description
Source Table
Location Hyperlinked entry to the port with the affected parties.
Key Unique value taken from the affected element’s business tag key, if it
exists.
Name Subinterface (site) name or business tag name of the affected element,
if it exists.
Type Business tag type.
IP Address If the affected element is an IP interface, the IP address of the
subinterface site.
Field Description
Affected Status (Agg) Status for the affected pair (destination). The same source can be part of
multiple pairs, and therefore each pair can have a different affected
status. The highest affected status reflects the highest among these. The
affected status can be one of the following:
• Potential
• Real
• Recovered
• N/A—From the links view, this indicates Not Applicable.
Destination Table
Location Hyperlinked entry to the port with the affected parties.
Key Unique value taken from the affected element’s business tag key, if it
exists.
Name Subinterface name or business tag name of the affected element, if it
exists.
Type Business tag type.
IP Address If the affected element is an IP interface, the IP address of the
subinterface site.
Affected Status Status of the affected pair as calculated by the client according to the
rules defined in Status Values for Affected Parties, page 9-22.
Alarm Clear State For each pair, an indication of the clear state of the alarm:
• Cleared—All related alarms for this pair have been cleared.
• Not Cleared—One or more alarms for this pair have not been
cleared.
When an affected side is selected in the Source table, the Destination table lists all endpoints with
services that have been affected between them and the entry selected in the Source table.
Note The Affected Parties dialog box occasionally displays entries that start with the word Misconfigured.
Entries that start with Misconfigured indicate that the flow has stopped unexpectedly between the source
and destination points. An unexpected termination point can be a routing entity, bridge, or VC switching
entity. The significant aspects of Misconfigured entries are:
- Because the link does not terminate as expected, the link is not actually impacted.
- An error might exist in the configuration or status of the termination points. We recommend that you
check the configuration and status of the affected termination points.
Correlation Tab
The Correlation tab displays all the alarms that are correlated to the selected ticket.
Table 9-12 describes the information that is displayed in the Correlation tab.
Field Description
Alarm Correlation Alarms correlated with the ticket. Expand or collapse the branch to
display or hide information as needed.
The severity displayed is the severity of the root alarm.
Short Description Description of the alarm.
Location Hyperlinked entry that opens an window displaying the selected node
along with the affected parties.
Note If the entity that triggered the alarm is outside your scope, a
message is displayed that states you do not have permission to
access the selected item.
Field Description
Acknowledged Whether or not the root alarm has been acknowledged: Yes or No.
Affected Devices Count Number of devices affected by the alarm.
Last Event Time Date and time the alarm was last modified.
Detail panel Long description of the selected entry.
Advanced Tab
The Advanced tab displays the following values for the selected ticket:
• Duplication Count:
– For network events, the duplication count is calculated by the VNE and pertains only to flapping
events. The duplication count represents the number of noncleared events aggregated by the
flapping event.
– For tickets, the duplication count is the sum of the duplication counts of all events that are
associated with the root alarm.
• Reduction Count:
– For network events, the reduction count is calculated by the VNE and pertains only to flapping
events. The reduction count represents the number of events that are aggregated by the flapping
event.
– For tickets, reduction count is the sum of reduction counts of all the events that are associated
to the ticket. The History tab in the Ticket Properties window displays one reduction count for
each event listed.
• Affected Devices—The number of devices affected by the ticket.
• Alarm Count—The total number of alarms associated with the ticket, including the root alarm.
Notes Tab
The Notes tab enables you to add and save notes for the selected ticket. To add text, enter text in the
Notes field and click Save Notes. The new text is added to any previously existing text.
The following restrictions apply to the Notes tab:
• You can add notes for a ticket only if both of the following conditions are true:
– The default permission for your account is OperatorPlus or higher.
– The security level for the device scope is OperatorPlus or higher for the device that holds the
root alarm for that ticket.
• The Notes tab is not available for archived tickets.
• The Save Notes button is enabled only when text is entered in the Notes field.
• The text cannot be edited or removed once you have saved the notes.
Managing Tickets
The following topics describe how to manage tickets:
• Finding Affected Elements, page 9-19
• Acknowledging a Ticket, page 9-19
• Clearing a Ticket, page 9-20
• Removing a Ticket, page 9-20
• Clearing and Removing Tickets, page 9-21
You can acknowledge, clear, remove, or clear and remove a ticket only if both of the following conditions
are true:
• The default permission for your account is OperatorPlus or higher.
• The security level for the device scope is OperatorPlus or higher for the device that holds the root
alarm for that ticket.
Prime Network automatically clears and removes (archives) tickets with more than 150 associated
events, and generates a system notification event regarding the actions taken. For more information
about this feature, see the Cisco Prime Network 3.8 Administrator Guide.
Acknowledging a Ticket
When an alarm occurs, a warning or ticket is displayed in the ticket pane. Prime Network Vision enables
you to handle the status of a ticket by acknowledging it. This acknowledges the fault.
The change is reported to the Prime Network gateway and all open Prime Network applications. You can
acknowledge multiple tickets at the same time.
An acknowledged ticket returns to a status of Not Acknowledged when a new event is correlated to it.
Clearing a Ticket
When an alarm occurs, a warning or ticket is displayed in the ticket pane. Prime Network Vision enables
you to handle the reported ticket by verifying the report of what is faulty and clearing the faulty network
element. The change is reported to the Prime Network gateway and all open Prime Network applications.
This operation cannot be reversed.
You can clear multiple tickets at the same time.
Note Before using Clear and Remove (which might also be available when you right-click a ticket), be sure
you understand the results of removing a ticket. Like clearing a ticket, removing a ticket cannot be
reversed. See Removing a Ticket, page 9-20.
Removing a Ticket
When an alarm occurs, a warning or ticket is displayed in the ticket pane. Prime Network Vision enables
you to completely remove the ticket and all of its active alarms and business tags. The change is reported
to the Prime Network gateway and all instances of Prime Network that are open. In addition, several
tickets can be removed at the same time. After a ticket is cleared or an Up alarm occurs, the ticket can
be removed.
You can remove multiple tickets at the same time.
Note This operation cannot be reversed. A ticket that has been removed can be viewed only by using Prime
Network Events.
Removing a ticket within seven minutes of its creation results in the following behavior:
• New alarms that might be related to the ticket, and should therefore be correlated to it, are not
correlated to the original ticket because the ticket has been removed from Prime Network Vision.
• Flagging events that are ticketable open new tickets. These new tickets might be delayed and might
not be visible in Prime Network Vision for up to seven minutes after the event was created.
• Flagging events that are not ticketable are archived.
• Clearing events are archived.
Note Only tickets with a severity of Cleared, Normal, or Information can be removed.
To remove one or more tickets, select the required tickets in the ticket pane, and then right-click and
choose Remove.
For more information, see Ticket Status in the Ticket Pane, page 9-5.
In addition, an uncleared ticket (which has a severity higher than Cleared or Normal) can be cleared and
removed by right-clicking in the ticket pane and choosing Clear and Remove. For more information
about the Ticket right-click menu, see Ticket Right-Click Menu, page 2-50.
Note This applies only to specific alarms. Not every alarm initiates automatic impact analysis.
• Proactive impact analysis—Prime Network provides what-if scenarios for determining the possible
effect of network failures. This enables on-demand calculation of affected service resources for
every link in the network, thus enabling an immediate service availability check and analysis for
potential impact and identification of critical network links. Upon execution of the what-if scenario,
Prime Network initiates an end-to-end flow that determines all the potentially affected edges.
Note Each fault that has been identified as potentially service affecting triggers an impact analysis calculation,
even if the fault recurs in the network.
Note There is no clear state for the affected services when the alarm is cleared.
Card out
|
----- Link A down
| |
| ------BGP neighbor loss
|
180110
Prime Network identifies the affected parties for each type of alarm and accumulates the following
information:
• The affected parties reported on all the events in the alarm event sequence, including flapping
alarms.
• The affected parties reported on the alarms that are correlated to it.
The gathered information includes the accumulation of the affected report of all the events in its own
correlation tree.
For example, in Figure 9-7:
• BGP neighbor loss includes the affected parties of all events in its own event sequence.
• Link A Down includes the affected parties of its own event sequence and the accumulated
information of the BGP Neighbor Loss event.
Cisco Prime Network (Prime Network) provides a Report Manager that enables you to generate, view,
and export reports of the information managed by Prime Network. You can save the generated reports in
any of the following formats: PDF, CSV, HTML, XLS, and XML.
In addition to a variety of standard reports for events and inventory, you can define reports as required
for your environment. The following topics discuss the Report Manager and reports in more detail:
• User Roles Required to Manage Reports, page 10-1
• Using the Report Manager, page 10-4
• Report Categories, page 10-11
• Generating Reports, page 10-21
• Managing Reports, page 10-37
• Defining Report Types, page 10-44
• Working with Report Folders, page 10-44
The following tables identify the tasks that you can perform:
• Table 10-1 identifies whether you can generate a report if a selected element is not in one of your
assigned scopes.
• Table 10-2 identifies whether you can generate a report if a selected element is in one of your
assigned scopes.
• Table 10-3 identifies the tasks you can perform on the reports that you generate.
• Table 10-4 identifies the tasks you can perform on the reports that someone else generates.
• Table 10-5 identifies the tasks you can perform on report folders.
By default, users with the Administrator role have access to all managed elements. To change the
Administrator user scope, see the topic on device scopes in the Cisco Prime Network 3.8 Administrator
Guide.
Table 10-1 Default Permission/Security Level Required for Generating Reports - Element Not in User’s Scope
Table 10-2 Default Permission/Security Level Required for Generating Reports - Element in User’s Scope
Table 10-3 Default Permission/Security Level Required for Working with Reports You Generate
Table 10-4 Default Permission/Security Level Required for Working with Reports Another User Generates
Table 10-5 Default Permission/Security Level Required for Working with Report Folders
Note Not all reports include pie charts. In addition, reports that normally include a pie chart do not
display a pie chart if the chart exceeds 25 slices.
Menu Options
Table 10-6 describes the menu options available in the Report Manager window.
Option Description
File Menu
Exit Exits the Report Manager window.
Tools Menu
Change User Password Enables you to change the password used when logging into the
Prime Network client application suite. The change takes effect the
next time you log into the application.
Note The administrator can also change a user password in Prime
Network Administration.
Help Menu
Cisco Prime Network Report Opens the online help for Prime Network Vision and Prime
Manager Help Network Events.
Cisco.com Unavailable.
About Cisco Report Manager Displays application information about Prime Network Vision and
Prime Network Events.
Define Report of Enables you to define a report of this type that is suited specifically
This Type to your environment.
Navigation Tree
The navigation pane displays a tree-and-branch representation of report folders and types of reports. The
highest level in the tree displays report folders. The following standard report folders are provided in
Report Manager:
• Events Reports
• Inventory Reports
• Network Service Reports
Each folder contains the types of reports that are provided with Prime Network and any user-defined
reports. For more information on the standard report types, see Table 10-12.
When you select an item in the tree, the content pane displays the generated reports as follows:
• If you select a folder, the content pane lists all reports that have been generated using any of the
report types in that folder.
• If you select a report type, the content pane lists all reports that have been generated of that report
type.
Content Pane
The content pane lists all reports generated for the folder or report type selected in the navigation tree.
You can double-click a report to view the report in HTML format.
Figure 10-3 shows an example of the content pane.
Table 10-8 describes the information displayed in the content pane for each report.
Attribute Description
Name Name of the report.
Double-click the report to view the report in HTML format.
Description Brief description of the report.
Creation Time Date and time when the report was generated.
Type Report type.
State State of the report: Running, Done, Canceled, or Failed.
For more information about the Failed state, see Generating
Reports, page 10-21.
Created By User who created the report.
Running Time Amount of time it takes for the report to be complete.
Size Report size.
Attribute Description
Public Availability of the report to other users:
• True—The report is available to all users.
• False—The report is available to only the user who generated
the report and the administrator.
Data Source Source of the information for the report: Fault Database, Event
Archive, or Network Elements.
Note Reports are purged from Prime Network after 90 days by default. This setting can be modified by
changing the setting in Prime Network Administration. For more information, see the Cisco Prime
Network 3.8 Administrator Guide.
Right-Click Options
Right-click options are available for:
• Navigation Pane Folders, page 10-9
• Navigation Pane Reports, page 10-10
• Content Pane Reports, page 10-10
Table 10-9 describes the options available when you right-click a folder in the navigation pane.
Option Description
New Folder Creates a new folder.
Delete Deletes a user-defined folder.
Rename Renames a user-defined folder.
Move Moves a user-defined folder.
Properties Displays the Folder Properties window which lists the folder contents. For
more information on the Reports Category Properties window, see Viewing
Folder and Report Type Properties, page 10-47.
Table 10-10 describes the options available when you right-click a report in the navigation pane.
Option Description
Run Displays the Run Report dialog box so you can run a report of this type
specifically for your environment and adds the generated report to the table
in the content pane.
Define Report of This This option is available only for Cisco-supplied report types.
Type
Displays the Define Report dialog box so you can create a report of this type
specifically for your environment, and adds the newly defined report to the
navigation tree.
Delete Deletes a user-defined report.
Move Moves a user-defined report.
Properties For a standard report type, displays the Reports Type Properties window
which includes a brief description of the report and enables you to generate
the report. For more information on the Reports Type Properties window,
see Viewing Report Properties, page 10-42.
For a user-defined report, displays the Edit report dialog box so that you can
modify the currently defined settings and generate the report.
Table 10-11 describes the options available when you right-click a report in the content pane.
Option Description
View As Displays the report in the selected format:
• HTML
• PDF
• CSV
• XLS
• XML
The default option, HTML, is displayed in bold font. For more
information on viewing reports, see Viewing and Saving Reports,
page 10-38.
Rename Renames the selected report.
Table 10-11 Report Manager Content Pane Report Right-Click Options (continued)
Option Description
Share or Unshare Shares the selected reports or limits them to your viewing only. The
option toggles between Share and Unshare, as appropriate for the
selected reports.
By default, the Share and Unshare options are available only to users
with administrator access. These options are available to other users
only if an administrator has enabled sharing in Prime Network
Administration. For more information, see the Cisco Prime Network 3.8
Administrator Guide.
Delete Report Deletes the selected reports.
Cancel This option is displayed only while the selected report is being
generated or queued.
Cancels the report that is being generated or is queued.
Show Only Selected Displays only the rows that you select.
Rows
Show All Rows Displays all table rows that meet the current filtering criteria.
Properties Displays the Reports Type Properties window, which includes a brief
description of the report and enables you to edit its name and
description.
Report Categories
Prime Network Vision provides reports related to:
• Events—See Events Reports, page 10-11.
• Inventory—See Inventory Reports, page 10-18.
• Network services—See Network Service Reports, page 10-19.
Events Reports
Prime Network Vision provides the following standard event report types:
• General report types, as described in Table 10-12.
• Detailed network event reports, as described in Table 10-13.
• Detailed non-network event reports, as described in Table 10-14.
Inventory Reports
Table 10-15 describes the standard inventory report types provided by Prime Network Vision and the
data source.
Generating Reports
You can generate reports in any of the following ways:
• Generating Reports from Report Manager, page 10-22
• Generating Reports from the Reports Menu, page 10-36
• Generating Reports from Prime Network Vision, page 10-37
You can generate reports only for devices that are within your scope.
Note Report Manager generates reports up to 150 MB in size. If you generate a report that exceeds this limit:
• Report Manager window displays Failed in the State column.
• An error message is entered in the log stating that the report failed because the resulting output is
too large.
To run the report successfully, enter more specific report criteria or limit the time period covered by the
report.
Note You can generate reports only for devices that are within your scope.
Step 1 In Prime Network Vision, Prime Network Events, or Prime Network Administration, choose Reports >
Report Manager.
Step 2 In the Report Manager window, choose Events Reports > report-type.
For information on the reports available for events, see Table 10-12.
Step 4 In the Run Report dialog box, specify the report settings as follows:
• For standard events reports, use the information in Table 10-17.
• For detailed network reports, use the information in Table 10-18.
• For detailed non-network reports, use the information in Table 10-19.
Option Description
Report Settings
Report Name Enter a unique name for the report, from 1 to 150 characters in length.
Report names cannot include the following characters: ;?<>/:\"#*|.
Description Enter a brief description of the report.
Report Security This field is displayed only if report sharing is enabled in Prime Network
Administration.
Indicate the level of security for the report by clicking the appropriate
option:
• Private—The report can be viewed and used only by the report creator
and the administrator.
• Public—The report can be viewed and used by all other users, regardless
of whether the devices are listed in the report are in the user’s scope.
Note You can share reports with others only if sharing is enabled in Prime
Network Administration. For more information, see the Cisco Prime
Network 3.8 Administrator Guide.
Display n This field does not appear for all reports.
Enter the number of items to be displayed in the generated report.
Data Source This field does not appear for all reports.
Select the source of information to use for the report: Fault Database or
Event Archive.
Include pie charts in This field does not appear for all reports.
report output
Check the check box to view pie charts in the report with the standard
numerical output.
Date Selection
Last Specify the length of time before the current date and time, and the unit of
measure: seconds, minutes, hours, days, weeks, or months.
From Date Specify the date range for the report:
To Date 1. Click From Date.
2. In the From date field, enter the start date for the time period, or click
the drop-down arrow to select the start date from a calendar.
3. Enter a time for the start date, using the format HH MM SS.
4. In the To Date field, enter the end date for the time period, or click the
drop-down arrow to select the end date from a calendar.
5. Enter a time for the end date, using the format HH MM SS.
Table 10-17 Events Report - Run Report Dialog Box Fields (continued)
Option Description
Device Selection
Select Devices Note
• You can add only those devices that are within your scope.
• A user with the Administrator role can select unmanaged devices (by IP
address) for reports that run on the Event Archive.
Select devices to include in the report:
1. Click Select Devices.
2. Click Add.
3. In the Add Network Element dialog box, select devices using either of
the following methods:
– To select devices that meet specific criteria, click Search and enter
the required criteria.
– To select from all network elements, click Show All.
4. In the list of displayed elements, select the network elements that you
want to include in the report. You can select multiple network elements
at a time.
5. Click OK.
All Devices This field does not appear for all reports.
Click All Devices to include all devices in your scope in the report.
Syslog Trend (by Severity) Report—Additional Report Specifications
Intervals In the Grouped by drop-down list, choose the unit of time to use for tracking
the trend: Seconds, Minutes, Hours, or Days.
Severity Check the check boxes of the syslog message severities to be included in the
report: All, Critical, Major, Minor, Warning, Cleared, Information, and
Indeterminate.
Syslog Messages Specify the syslog messages to be included in the report:
• To include selected syslog messages in the report, in the list of syslog
messages on the left, select the required syslog messages, and then click
Add Selected to move them to the list of syslog messages on the right.
• To include all syslog messages in the report, click Add All.
To find syslog messages that match a string, enter the string in the Find field.
The list of syslog messages is automatically updated to include only those
messages that contain the string you enter.
Click the Sort Order button to sort the syslog messages in alphabetic or
reverse alphabetic order.
Table 10-18 Detailed Network Events Reports - Run Report Dialog Box Fields
Option Description
Report Settings
Report Name Enter a unique name for the report, from 1 to 150 characters in length.
Report names cannot include the following characters: ;?<>/:\"#*|.
Description Enter a brief description of the report.
Report Security This field is displayed only if report sharing is enabled in Prime Network
Administration.
Indicate the level of security for the report by clicking the appropriate
option:
• Private—The report can be viewed and used only by the report creator
and the administrator.
• Public—The report can be viewed and used by all other users, regardless
of whether the devices are listed in the report are in the user’s scope.
Note You can share reports with others only if sharing is enabled in Prime
Network Administration. For more information, see the Cisco Prime
Network 3.8 Administrator Guide.
Data Source This field does not appear for all reports.
Select the source of information to use for the report: Fault Database or
Event Archive.
Date Selection
Last Specify the length of time before the current date and time, and the unit of
measure: seconds, minutes, hours, days, weeks, or months.
From Date Specify the date range for the report:
To Date 1. Click From Date.
2. In the From date field, enter the start date for the time period, or click
the drop-down arrow to select the start date from a calendar.
3. Enter a time for the start date, using the format HH MM SS.
4. In the To Date field, enter the end date for the time period, or click the
drop-down arrow to select the end date from a calendar.
5. Enter a time for the end date, using the format HH MM SS.
Table 10-18 Detailed Network Events Reports - Run Report Dialog Box Fields (continued)
Option Description
Device Selection
Select Devices Note
• You can add only those devices that are within your scope.
• A user with the Administrator role can select unmanaged devices (by IP
address) for reports that run on the Event Archive.
• The Detailed Event Count (by device) report accepts a maximum of
1000 devices.
Select devices to include in the report:
1. Click Select Devices.
2. Click Add.
3. In the Add Network Element dialog box, select devices using either of
the following methods:
– To select devices that meet specific criteria, click Search and enter
the required criteria.
– To select from all network elements, click Show All.
4. In the list of displayed elements, select the network elements that you
want to include in the report. You can select multiple network elements
at a time.
5. Click OK.
All Devices This field does not appear for all reports.
Click All Devices to include all devices in your scope in the report.
Severity
Severity This field does not appear for all reports.
Check the check boxes of the syslog message severities to be included in the
report: All, Critical, Major, Minor, Warning, Cleared, Information, and
Indeterminate.
Detailed Service Events Report—Additional Report Specifications
Description Contains Enter the string that the service event must contain to be included in the
report.
Detailed Syslogs Report—Additional Report Specifications
Syslogs Description This field is displayed if you choose Fault DB for the data source.
In the Description Contains field, enter the string that the syslog must
contain to be included in the report.
Syslogs Raw Data This field is displayed if you choose Event Archive for the data source.
In the Raw Data Contains field, enter the string that the syslog raw data must
contain to be included in the report.
Table 10-18 Detailed Network Events Reports - Run Report Dialog Box Fields (continued)
Option Description
Detailed Traps Report—Additional Report Specifications
Traps Detailed In the Description Contains field, enter the string that the trap must contain
Description to be included in the report.
Long Description This option is enabled if you choose Fault DB for the data source.
1. Check the Show Long Description check box to include the long
description in the report.
2. In the Long Description Contains field, enter the string that the long
description must contain to be included in the report.
SNMP Version Specify the SNMP versions to include in the report: All, 1, 2, or 3.
Generic This option is enabled if you choose Event Archive for the data source.
Specify the generic traps to include in the report:
1. Select the generic traps to include in the report:
– All—Include all generic traps
– 0—coldStart
– 1—warmStart
– 2—linkDown
– 3—linkUp
– 4—authenticationFailure
– 5—egpNeighborLoss
– 6—enterpriseSpecific
2. If you select generic type 6, enter the OIDs (comma separated) in the
Vendor Specific field.
The Vendor Specific field accepts a maximum of 125 digits.
Table 10-19 Detailed Non-Network Events Reports - Run Report Dialog Box Fields
Option Description
Report Settings
Report Name Enter a unique name for the report, from 1 to 150 characters in length.
Report names cannot include the following characters: ;?<>/:\"#*|.
Description Enter a brief description of the report.
Report Security This field is displayed only if report sharing is enabled in Prime Network
Administration.
Indicate the level of security for the report by clicking the appropriate
option:
• Private—The report can be viewed and used only by the report creator
and the administrator.
• Public—The report can be viewed and used by all other users, regardless
of whether the devices are listed in the report are in the user’s scope.
Note You can share reports with others only if sharing is enabled in Prime
Network Administration. For more information, see the Cisco Prime
Network 3.8 Administrator Guide.
Date Selection
Last Specify the length of time before the current date and time, and the unit of
measure: seconds, minutes, hours, days, weeks, or months.
From Date Specify the date range for the report:
To Date 1. Click From Date.
2. In the From date field, enter the start date for the time period, or click
the drop-down arrow to select the start date from a calendar.
3. Enter a time for the start date, using the format HH MM SS.
4. In the To Date field, enter the end date for the time period, or click the
drop-down arrow to select the end date from a calendar.
5. Enter a time for the end date, using the format HH MM SS.
Severity
Severity Check the check boxes of the syslog message severities to be included in the
report: All, Critical, Major, Minor, Warning, Cleared, Information, and
Indeterminate.
Detailed Audit Events Report—Additional Report Specifications
Description Contains Enter the string that the event must contain to be included in the report.
Command Name Enter the string that the command name must contain to be included in the
Contains report.
Originator IP Contains Enter the string that the originating IP address must contain to be included
in the report.
User Name Contains Enter the string that the user name must contain to be included in the report.
Table 10-19 Detailed Non-Network Events Reports - Run Report Dialog Box Fields (continued)
Option Description
Detailed Provisioning Events Report—Additional Report Specifications
Description Contains Enter the string that the trap must contain to be included in the report.
User Name Contains Enter the string that the user name must contain to be included in the report.
Status Choose the statuses to be included in the report: All, Unknown, Configuring,
Success, and Fail.
Detailed Security Events Report—Additional Report Specifications
Description Contains Enter the string that the event must contain to be included in the report.
Originator IP Contains Enter the string that the originating IP address must contain to be included
in the report.
User Name Contains Enter the string that the user name must contain to be included in the report.
Detailed System Events Report—Additional Report Specifications
Description Contains Enter the string that the event must contain to be included in the report.
Step 1 In Prime Network Vision, Prime Network Events, or Prime Network Administration, choose Reports >
Report Manager.
Step 2 In the Report Manager window, choose Inventory Reports > report-type.
For information on the standard reports available for inventory, see Table 10-15.
Step 3 Generate the report in either of the following ways:
• Click Run in the toolbar.
• Right-click the report type, then choose Run.
The Run Report dialog box is displayed as shown in Figure 10-5.
Step 4 Enter the required information in the Run Report dialog box as described in Table 10-20.
Field Description
Report Settings
Report Name Enter a unique name for the report, from 1 to 150 characters in length.
Report names cannot include the following characters: ;?<>/:\"#*|.
Description Enter a brief description of the report.
Report Security This field is displayed only if report sharing is enabled in Prime Network
Administration.
Indicate the level of security for the report by clicking the appropriate
option:
• Private—The report can be viewed and used only by the report creator
and the administrator.
• Public—The report can be viewed and used by all other users, regardless
of whether the devices are listed in the report are in the user’s scope.
Note You can share reports with others only if sharing is enabled in Prime
Network Administration. For more information, see the Cisco Prime
Network 3.8 Administrator Guide.
Table 10-20 Inventory Report - Run Report Dialog Box Fields (continued)
Field Description
Device Selection
Select Devices Note You can add only those devices that are within your scope.
Step 1 In Prime Network Vision, Prime Network Events, or Prime Network Administration, choose Reports >
Report Manager.
Step 2 In the Report Manager window, choose Network Service Reports > report-type.
For information on the standard reports available for network services, see Table 10-16.
Step 4 Enter the required information the Run Report dialog box as described in Table 10-21.
Table 10-21 Network Service Report - Run Report Dialog Box Fields
Field Description
Report Settings
Report Name Enter a unique name for the report, from 1 to 150 characters in length.
Report names cannot include the following characters: ;?<>/:\"#*|.
Description Enter a brief description of the report.
Report Security This field is displayed only if report sharing is enabled in Prime
Network Administration.
Indicate the level of security for the report by clicking the appropriate
option:
• Private—The report can be viewed and used only by the report
creator and the administrator.
• Public—The report can be viewed and used by all other users,
regardless of whether the devices are listed in the report are in the
user’s scope.
Note You can share reports with others only if sharing is enabled in
Prime Network Administration. For more information, see the
Cisco Prime Network 3.8 Administrator Guide.
Ethernet Service Reports—Report Contents
Define Filter Check the Define Filter check box to enter criteria that must be matched
for inclusion in the report.
You can specify match criteria in any or all of the following fields.
Ethernet Service Name Enter a string that must appear in the Ethernet service name for the
Contains Ethernet service to be included in the report.
EVC Name Contains Enter a string that must appear in the EVC name for the EVC to be
included in the report.
Ethernet Service Business Enter a string that must appear in the Ethernet service business tag for
Tag Contains the Ethernet service to be included in the report.
EVC Business Tag Contains Enter a string that must appear in the EVC business tag for the EVC to
be included in the report.
Maps Specify the maps to include in the report:
• To include specific maps in the report, in the list of maps on the left,
select the required maps, and then click Add Selected to move them
to the list of maps on the right.
• To include all maps in the report, click Add All.
To find maps that match a string, enter the string in the Find field. The
list of maps is automatically updated to include only those maps that
contain the string you enter.
Click the Sort Order button to sort the maps alphabetically or in reverse
alphabetic order.
Table 10-21 Network Service Report - Run Report Dialog Box Fields (continued)
Field Description
Network Pseudowire Reports—Report Contents
Define Filter Check the Define Filter check box to enter criteria that must be matched
for inclusion in the report.
You can specify match criteria in any or all of the following fields.
Network Pseudowire Name Enter a string that must appear in the network pseudowire name for the
Contains pseudowire to be included in the report.
Network Pseudowire Type In the drop-down list, choose the type of network pseudowire to be
included in the report.
Network Pseudowire Enter a string that must appear in the network pseudowire business tag
Business Tag Contains for the pseudowire to be included in the report.
Maps Specify the maps to include in the report:
• To include specific maps in the report, in the list of maps on the left,
select the required maps, and then click Add Selected to move them
to the list of maps on the right.
• To include all maps in the report, click Add All.
To find maps that match a string, enter the string in the Find field. The
list of maps is automatically updated to include only those maps that
contain the string you enter.
Click the Sort Order button to sort the maps alphabetically or in reverse
alphabetic order.
VPLS Reports—Report Contents
Define Filter Check the Define Filter check box to enter criteria that must be matched
for inclusion in the report.
You can specify match criteria in any or all of the following fields.
VPLS Name Contains Enter a string that must appear in the VPLS name for the VPLS or
H-VPLS to be included in the report.
VPLS Business Tag Enter a string that must appear in the VPLS business tag for the VPLS
Contains or H-VPLS to be included in the report.
Maps Specify the maps to be included in the report:
• To include specific maps in the report, in the list of maps on the left,
select the required maps, and then click Add Selected to move them
to the list of maps on the right.
• To include all maps in the report, click Add All.
To find maps that match a string, enter the string in the Find field. The
list of maps is automatically updated to include only those maps that
contain the string you enter.
Click the Sort Order button to sort the maps alphabetically or in reverse
alphabetic order.
Note You can generate reports only for devices that are within your scope.
Step 1 Choose Reports > Run Report > folder > report-type where:
• folder is the required folder.
• report-type is the required type of report.
Step 2 In the Run Report dialog box, enter the required information. For more information on the options in the
Run Report dialog box, see Generating Reports, page 10-21.
Step 3 Click OK.
Step 4 In the Running Report dialog box, select the required viewing options:
a. Check the Open Report Manager to monitor status check box to open the Report Manager
window so that you can view the report generation process. Uncheck the check box to proceed
without opening the Report Manager window.
b. Check the View report immediately upon completion check box to view the report as soon as it is
generated. If you enable this option, the report is displayed in HTML format as soon as it is
complete. Uncheck the check box to view the report at a later time by using Report Manager.
Step 5 Click OK.
Depending on your selections in Step 4, the Report Manager window is displayed, the report is
displayed, or the report is available for viewing at a later time.
Note You can generate reports only for devices that are within your scope.
Step 1 In Prime Network Vision, select the required devices in the map or list view.
Step 2 In the navigation tree or content pane, right-click the selected devices, then choose Run Report >
folder > report-type.
Step 3 In the Run Report dialog box, enter the required information as described in Generating Reports,
page 10-21.
The devices that you select in the navigation pane or content pane are automatically included in the
report.
Step 4 Click OK.
Step 5 In the Running Report dialog box, specify the desired viewing options:
a. Check the Open Report Manager to monitor status check box to open the Report Manager
window so that you can view the report generation process. Uncheck the check box to proceed
without opening the Report Manager window.
b. Check the View report immediately upon completion check box to view the report as soon as it is
generated. If you enable this option, the report is displayed in HTML format as soon as it is
complete. Uncheck the check box to view the report at a later time by using Report Manager.
Depending on your selections in Step 5, the Report Manager window is displayed, the report is
displayed, or the report is available for viewing at a later time.
Managing Reports
Prime Network provides the following options for working with reports:
• Managing the Maximum Number of Concurrent Reports, page 10-38
• Viewing and Saving Reports, page 10-38
• Renaming Reports, page 10-40
• Sharing Reports, page 10-41
• Moving Reports Between Folders, page 10-41
• Deleting Reports, page 10-42
• Viewing Report Properties, page 10-42
Note Changes to the registry should only be carried out with the support of Cisco. For details, contact your
Cisco account representative.
To change the maximum number of concurrent reports, use the runRegTool command (located in
ANAHOME/Main) as follows:
./runRegTool.sh -gs 127.0.0.1 set 0.0.0.0
site/reports/reports-setting/reports-running-settings/maxRunningReports value
Note Reports are purged from Prime Network after 90 days by default. This setting can be modified by
changing the setting in Prime Network Administration. For more information, see the Cisco Prime
Network 3.8 Administrator Guide.
Step 3 In the content pane, right-click the report, then choose View As > format where format is one of the
following:
• HTML—Displays the report in a browser window. Clicking a column heading in the report sorts the
report by that value; clicking the column heading again sorts the data in the reverse order. HTML is
the default format.
• PDF—Displays a PDF version of the report.
• CSV—Creates a CSV version of the report that you can either save to a specific location or view
using another application. The CSV version contains only the report data; it does not contain the
header information, layout, or formatting information that is available in other formats.
• XLS—Creates an XLS version of the report that you can either save to a specific location or view
using another application, such as Microsoft Excel.
• XML—Creates an XML version of the report that you can either save to a specific location or view
using an XML editor or viewer.
Figure 10-7 is an example of the Most Common Daily Events report in HTML format. The data is sorted
by the Count column, in descending order.
Renaming Reports
You can rename:
• Any report type that you defined.
• Any generated report that you have access to.
You cannot rename any of the Prime Network standard report types.
Note When you rename a report type, the new name applies to only those reports that you run after changing
the name; it does not change the names of reports that were run prior to changing the name.
To rename a report:
Sharing Reports
Prime Network enables you to share reports that you generate with other users, or limit access to a report
to only you and the administrator.
Note You can share reports with others only if sharing is enabled in Prime Network Administration. For more
information, see the Cisco Prime Network 3.8 Administrator Guide.
Sharing a Report
Note You cannot move a standard report type from one folder to another.
Deleting Reports
You can delete reports to which you have access.
To delete a report:
Step 3 In the content pane, right-click the selected report, then choose Properties.
The Report Properties dialog box is displayed, as shown in Figure 10-8.
The Report Properties dialog box contains the following information about the report:
• Name
• Description
• Type
• Source of the information
• Date and time it was created
• User who created it
• Size
• State
• Access
Creating Folders
Prime Network enables you to create additional report folders in Report Manager.
To create a report folder:
Moving Folders
Prime Network enables you to move folders that you have created in Report Manager. You cannot move
the Events Reports, Inventory Reports, or Network Service Reports folder.
To move a report folder:
Renaming Folders
Prime Network enables you to rename folders that you have created in Report Manager. You cannot:
• Rename a folder that resides at the highest level in the hierarchy, such as the Events Reports,
Inventory Reports, or Network Service Reports folder.
• Use the same name for different folders that reside at the same level in the hierarchy.
To rename a report folder:
Deleting Folders
You can delete folders that you have created in Report Manager if they are empty. You cannot delete the
following folders:
• Events Reports
• Detailed Network Events
• Detailed Non-Network Events
• Inventory Reports
• Network Service Reports
• User-created folders that contain other folders or report types
To delete a report folder:
Table 10-22 describes the information that is displayed in each tab, depending on the folder’s contents.
Field Description
Report Folders Tab
Name Name of the folder included in the selected folder.
Report Types Tab
Name Name of the report type included in the selected folder.
Description Description of the report type included in the selected folder.
Defined Reports Tab
Name Name of the user-defined report in the selected folder.
Description Description of the user-defined report in the selected folder.
Type Report type on which the user-defined report is based.
Public Status of public access to the report: True or False.
Step 1 In the navigation pane, right-click the required report type, then choose Properties.
The information that is displayed depends on whether the report type is one that you defined or one
provided by Prime Network:
• Prime Network-provided report type—The Report Type Properties window is displayed with the
report name and description. Click Run to generate the report.
• User-defined report type—The Edit dialog box is displayed with all settings specified for the report
type. You can modify the settings or leave them as they are.
Step 2 Click Close or the upper right corner to close the window.
Cisco PathTracer enables you to view a network path between two network objects. The following topics
describe Cisco PathTracer and how to use it:
• User Roles Required to Work with Cisco PathTracer, page 11-1
• Cisco PathTracer Overview, page 11-2
• Launching Path Traces, page 11-3
• Viewing Path Traces in Cisco PathTracer, page 11-14
• Viewing Path Trace Details, page 11-21
• Saving and Opening Cisco PathTracer Map Files, page 11-26
• Saving Cisco PathTracer Counter Values, page 11-27
• Rerunning a Path and Comparing Results, page 11-28
• Viewing Q-in-Q Path Information, page 11-28
• Viewing L2TP Path Information, page 11-29
• Using Cisco PathTracer in MPLS Networks, page 11-30
By default, users with the Administrator role have access to all managed elements. To change the
Administrator user scope, see the topic on device scopes in the Cisco Prime Network 3.8 Administrator
Guide.
Table 11-1 Default Permission/Security Level Required for Working with Cisco PathTracer -
Element Not in User’s Scope
Table 11-2 Default Permission/Security Level Required for Working with Cisco PathTracer -
Element in User’s Scope
In MPLS and Carrier Ethernet environments, Cisco PathTracer can trace paths across:
• Carrier Supporting Carrier (CSC) configurations—A path trace along a CSC flow follows the path
from the customer CE through the customer carrier VPN, across the customer backbone carrier
VPN, back to the customer carrier VPN, and to the destination CE.
• VLANs—A path trace across VLANs follows the path based on the forwarding table, which means
that the trace follows ports in the Forwarding STP state.
• Q-in-Q—A path trace across Q-in-Q creates a single path trace (if the MAC address is learned) or a
multiple-path (multipath) trace if the MAC address is not in the forwarding table. If the VLAN
bridge has not learned a given MAC address, the bridge floods the Ethernet frame to the confines of
a given VLAN or switching entity and across those ports that allow the given VLAN identifier. A
MAC/VLAN path trace can be conducted from a customer edge (CE) VLAN interface across a
service provider (SP) VLAN; that is, across Q-in-Q configurations with the CE-VLAN identifier as
the inner VLAN identifier and Cisco PathTracer detecting the outer SP-VLAN identifier that
encapsulates the CE-VLAN.
• Pseudowires (also known as EoMPLS)—A MAC/VLAN path trace can be conducted from a VLAN
interface across a VLAN attachment to a pseudowire.
• VLAN-VPLS-VLAN configurations—A multiple-point MAC/VLAN path trace can be conducted
on CE-VLANs across a service provider VPLS transport from a VLAN interface that attaches to the
VPLS.
In addition, Cisco PathTracer can trace a path:
• If the destination MAC address is not reachable—If Cisco PathTracer cannot complete a
MAC/VLAN path trace to a specified destination MAC address across an MPLS core, VPLS, or
H-VPLS, then Cisco PathTracer displays the portion of the path that Cisco PathTracer can trace
toward the destination MAC address.
• That contains a simulated Ethernet frame—Cisco PathTracer can trace a simulated Ethernet frame
from a VLAN port, across a VLAN (VLAN-based flow domain fragment), VPLS (VPLS-based flow
domain fragment), and VLAN, for an end-to-end MAC address trace.
Prime Network derives the various paths on the network from its up-to-date knowledge of the network.
After a user selects a source and destination, Cisco PathTracer finds and retrieves the path of a specified
service, and displays the path in the Cisco PathTracer window. The retrieved information contains
network elements in the path, including all properties at Layer 1, Layer 2, and Layer 3, plus alarm
information, counters, and more, all of which is available via Cisco PathTracer.
To view a specific path, you must specify an initial point and a destination, such as an IP or MAC
address. If you specify VC or DLCI information, which ends in a router, Cisco PathTracer finds the next
hop according to the destination IP address. If you do not specify a destination IP or MAC address,
Cisco PathTracer uses the default gateway in the router. Any business tags that are associated with the
physical or logical entities are also displayed.
Note A path can also be launched if a business tag attached to an endpoint that can be used as the starting
point.
Element Location
Affected Parties • Inventory window
• Ticket Properties window (Affected Parties tab)
Bridge Inventory window
Business tag The path can be found using a business tag, which is attached to the
VPI/VCI, or using an IP interface by entering its key. The path can
then be opened from the Find Business Tag dialog box.
Ethernet flow point • Map view or navigation pane
• Inventory window
IP interface • Inventory window
• Affected entry
Layer 2 MPLS tunnel Inventory window
MPLS-TE tunnel Inventory window
MPLS-TP tunnel endpoint • Map view or navigation pane
• Inventory window
Port Inventory window
Element Location
Pseudowire endpoint • Map view or navigation pane
• Inventory window
Site Map view
Switching entity Map view
Virtual connection Inventory window:
• Cross Connect window
• VC Table window
VLAN • Navigation pane
• Map view
Step 1 In a Cisco Prime Network Vision map, start the path trace in one of the following ways:
• For a VLAN:
a. In the navigation pane or map pane, select the required network VLAN.
b. Double-click the VLAN to view the VLAN entities.
c. Right-click the required item and choose PathTracer > From Here to Destination or
PathTracer > Start Here.
• For a VPN:
a. In the navigation pane or map pane, select the required network VPN.
b. Double-click the VPN to view the VPN entities.
c. Right-click the site and choose PathTracer > From Here to Destination or PathTracer > Start
Here.
• For an Ethernet flow point:
a. Choose Network Inventory > Ethernet Flow Domains.
b. In the Ethernet Flow Domain List Properties window, double-click the required domain.
c. In the Ethernet Flow Domain Properties window, right-click the required element and choose
PathTracer > From Here to Destination or PathTracer > Start Here.
Field Description
Destination IP Select this option to specify an IP address as the destination. Enter
either an IPv4 or IPv6 address.
Destination MAC Select this option to specify a MAC address as the destination. Enter
the MAC address.
VLAN ID Enter the required VLAN identifier. You must enter an IP address or
a MAC address to use this option.
Inner VLAN ID Enter the required inner VLAN identifier.
Stop trace after Check this check box to limit the number of hops that
Cisco PathTracer makes in its attempt to reach the destination.
Enter the maximum number of hops that you want to allow in the
hops field.
b. Click OK.
Step 3 If you choose Start Here, navigate to the destination interface, port, or bridge, right-click it, and choose
End Here.
The Cisco PathTracer window is displayed showing the path or paths that were found.
Step 4 To view additional details regarding the path traces, select one or more paths in the paths pane.
Note If you select an IP interface as the launch point, the right-click menu displays IPv4 and IPv6
options. These options are enabled or dimmed, depending on whether the IP interface has an
IPv4 IP address, an IPv6 address, or both IPv4 and IPv6 addresses. For an example, see
Figure 11-3.
• PathTracer > Start Here—If you choose this option, continue with Step 3 in From the Map View,
page 11-5.
A network VLAN is required for you to start a path trace using an Ethernet flow point.
To launch a path trace from an Ethernet flow point:
Step 1 In the Cisco Prime Network Vision navigation pane or map pane, expand the required network VLAN.
Step 2 In the VLAN, right-click the required Ethernet flow point and choose PathTracer > From Here to
Destination. The Path Information dialog box is displayed as shown in Figure 11-2.
Using an IP Interface
Both IPv4 and IPv6 addresses are supported as valid path trace sources and destinations as illustrated in
the following procedure.
To launch a path trace from an IP interface:
Step 1 In logical inventory, right-click the required IP interface (Logical Inventory > Routing Entities >
Routing Entity > ip-interface).
The right-click menu displays IPv4 and IPv6 options. These options are enabled or dimmed, depending
on whether the IP interface has an IPv4 address, an IPv6 address, or both IPv4 and IPv6 addresses. See
Figure 11-3.
Figure 11-4 IP Interface Path Trace Launch Point - Path Information Dialog Box
You can launch path traces from VLAN bridges. Additionally, MAC addresses in the VLAN bridge
forwarding table can be path trace destinations.
To launch a path trace from a VLAN bridge:
Step 1 In logical inventory, right-click the required bridge (Logical Inventory > Bridges > bridge) and choose
one of the following options as shown in Figure 11-5:
• PathTracer > From Here to Destination
• PathTracer > Start Here
Step 2 If you choose From Here to Destination in Step 1, the Path Information dialog box is displayed.
Specify the required destination using the information in Table 11-4.
Step 3 If you choose Start Here, navigate to the destination, right-click it, and choose End Here. Destination
options include:
• IP interface—Logical Inventory > Routing Entities > Routing Entity > IP-interface
• Bridge—Logical Inventory > Bridges > bridge
• MAC address—Logical Inventory > Bridges > bridge > Bridge Table > MAC-address
• Ethernet port—Physical Inventory > chassis > slot > port
When a destination is selected, the system extracts the relevant IP address from this point and uses it as
the destination.
The Cisco PathTracer window is displayed with the resulting path trace.
Step 1 In physical inventory, right-click the required port (Physical Inventory > Chassis > slot > subslot >
port) and choose one of the following options as shown in Figure 11-6:
• PathTracer > From Here to Destination
• PathTracer > Start Here
Step 2 Depending on your choice in Step 1, specify the required destination information or select the path trace
endpoint.
The Cisco PathTracer window appears, displaying the resulting path trace.
Using a Pseudowire
Step 1 In the navigation pane or map pane, expand the required network pseudowire.
Step 2 Right-click the required pseudowire endpoint and choose PathTracer > From Here to Destination.
The Path Information dialog box is displayed as shown in Figure 11-7.
Step 1 In the navigation pane or map pane, expand the required MPLS-TP tunnel.
Step 2 Right-click the required MPLS-TP tunnel endpoint and choose PathTracer > From Here to
Destination.
The Path Information dialog box is displayed as shown in Figure 11-8.
The Cisco PathTracer window contains the following components and options:
• Menus, page 11-16
• Toolbar, page 11-17
• Trace Tabs, page 11-18
• Paths Pane, page 11-18
• Path Trace Pane, page 11-18
• Right-Click Menu Options, page 11-19
Menus
Table 11-5 describes the options available in the Cisco PathTracer menus.
Option Description
File Menu
Run Again Offers the following options for running Cisco PathTracer again for the same
source and destination:
• Change Hop Count—Enables you to enter a new hop count.
• Repeat Last Trace—Runs the previous trace with the same settings.
• Run Full Path Trace—Runs the previous trace without a hop count limit.
Save Opens the Save dialog box so that you can save the current path trace to your
local system in XML format.
Close Closes the Cisco PathTracer window.
Edit Menu
Select All Selects all paths in the selected path trace pane.
View Menu
Layout Specifies how the elements are arranged in the path trace pane: circular,
hierarchical, orthogonal, or symmetric.
Overview Opens a window displaying an overview of the path trace.
Zoom In Zooms in on the current path trace.
Zoom Out Zooms out on the current path trace.
Fit in Window Fits the entire path trace in the path trace pane.
Normal Select Activates the normal selection mode.
Pan Activates the pan mode, which enables you to move around in the path trace by
clicking and dragging.
Zoom Selection Enables you to zoom in on a specific area in the path trace.
Toolbar
Table 11-6 describes the options available in the Cisco PathTracer toolbar.
Button Function
Displays the previous path in the path trace pane.
Opens the Cisco PathTracer details window. A map is displayed for the selected path,
including network element details, links, and property information. For more information,
see Viewing Path Trace Details, page 11-21.
Saves the current multiple-path trace to an XML file on your local system. For more
information, see Saving and Opening Cisco PathTracer Map Files, page 11-26.
Offers the following options for running Cisco PathTracer again for the same source and
destination:
• Change Hop Count—Enables you to enter a new hop count.
• Repeat Last Trace—Runs the previous trace with the same settings.
• Run Full Path Trace—Runs the previous trace without a hop count limit.
The new path trace map is displayed in the path trace pane.
A new tab with the up-to-date (or refreshed) path map is created for each run, with each tab
representing a run and the tab label indicating the snapshot time.
Opens a window displaying a high level view of the path trace currently displayed in the
path trace pane.
Specifies how the elements are arranged in the path trace pane: circular, hierarchical,
orthogonal, or symmetric.
Activates the normal selection mode. The button toggles when selected or deselected.
Activates the zoom selection mode, which enables you to select a specific area in the path
to zoom in on by clicking and dragging. The button toggles when selected or deselected.
Activates the pan mode, which enables you to move around in the path trace by clicking and
dragging. The button toggles when selected or deselected.
Trace Tabs
The discovered path trace is initially displayed in the path trace pane with a tab that displays the date
and time when Prime Network started the path tracing process (snapshot time).
If you load a saved path from a file or run the displayed path trace again, the opened or refreshed path
is displayed in a new tab with a refreshed path map for each run or file. When using a saved path from
a file, the source and destination must be the same as the current display for it to appear in the same path
trace window. Each tab represents a run or file, and its header displays the snapshot time.
Paths Pane
The paths pane lists all the paths discovered in the current path trace. A new path is created for each
source and destination pair. The paths are identified by number, such as 1, 2, and 3.
If you launch a path trace with a specific hop count, the paths pane displays First n Hops where n is the
number of hops specified.
Selecting a path in the paths pane highlights the selected path in the path trace pane. The paths that are
not selected are dimmed in the map.
To view a different path, do either of the following:
• Choose a different path in the paths pane.
• Click Select Previous Path or Select Next Path in the toolbar.
To remove a path selection, click Clear Path Selection in the toolbar.
Option Description
Inventory Opens the inventory window for the selected element.
Aggregate Groups the selected devices into an aggregation.
Disaggregate Ungroups the devices in the selected aggregation.
Note This option is available only when an aggregation is selected.
Poll Now Polls the selected element.
Attach Business Tag Attaches a business tag to the selected network element
Config Mgmnt This option is available only if Prime Network Change and Configuration
Management is installed.
Displays the Configuration Management page for the selected device in
Prime Network Change and Configuration Management.
Image Mgmnt This option is available only if Prime Network Change and Configuration
Management is installed.
Displays the Configuration Management page for the selected device in
Prime Network Change and Configuration Management.
Resize Enables you to resize an object on the map by percentage or size.
Open Relevant Maps Displays the Open Map dialog box so that you can view and open maps that
contain the selected element.
Run Report Enables you to run standard or user-defined events, inventory, and network
service reports on demand.
Show Callouts/ Displays or hides callouts associated with the selected element.
Hide Callouts
Option Description
Tools Contains the following choices:
• CPU Usage—Displays memory and CPU usage information for a device
or network element.
• Ping—Pings the device from the client station.
• Telnet—Communicates with the device using the Telnet window from
the client station.
Note If you use a Windows 7 system, you must enable the Windows Telnet
Client before you can use the Prime Network Vision Telnet option.
Menus
Table 11-8 describes the Cisco PathTracer details window menu options.
Option Description
File Menu
Close Closes the Cisco PathTracer window.
View Menu
Show All Displays all the information in the tabs.
Hide All Hides all the information in the tabs.
Tools Menu
Export to File Exports the currently displayed data to a CSV file.
Start Saving to File Starts exporting the counter values of the path displayed in the
Cisco PathTracer window to a CSV file.
Stop Saving to File Stops exporting the counter values of the path displayed in the
Cisco PathTracer window to a CSV file.
Help Menu
Help Contents Opens the online help for Cisco Prime Network Vision and
Cisco Prime Network Events.
Help About Displays the Cisco Prime Network Vision version and any
additionally installed applications.
Start Saving to File Starts exporting the counter values of the path displayed in the
Cisco PathTracer window to a CSV file.
Stop Saving to File Stops exporting the counter values of the path displayed in the
Cisco PathTracer window to a CSV file.
Table 11-10 describes the right-click menu options that are available for elements in the path trace pane.
Option Description
Inventory Opens the inventory window for the selected element.
Attach Business Tag Attaches a business tag to the selected network element
Poll Now Polls the selected element.
Config Mgmnt This option is available only if Prime Network Change and
Configuration Management is installed.
Displays the Configuration Management page for the selected
device in Prime Network Change and Configuration Management.
Image Mgmnt This option is available only if Prime Network Change and
Configuration Management is installed.
Displays the Configuration Management page for the selected
device in Prime Network Change and Configuration Management.
Run Report Enables you to run standard or user-defined events, inventory, and
network service reports on demand.
Tools Contains the following choices:
• CPU Usage—Displays memory and CPU usage information for
a device or network element.
• Ping—Pings the device from the client station.
• Telnet—Communicates with the device using the Telnet
window from the client station.
Note If you use a Windows 7 system, you must enable the
Windows Telnet Client before you can use the Prime
Network Vision Telnet option.
Option Description
Launch external Starts an external application or tool that has been configured for
applications access via the right-click menu. For more information, see the
Cisco Prime Network 3.8 Customization User Guide.
Properties Displays the properties of the selected item, such as the IP address
and system name.
Commands Launches available activation and configuration scripts, including
those you create using Command Builder. For more information,
see the Cisco Prime Network 3.8 Customization User Guide.
Management Contains the following submenu options:
• Command Builder—Defines commands and scripts using the
Prime Network Command Builder tool (Configurator security
level required).
• Soft Properties Management—Extends VNEs by adding SNMP
MIB or Telnet/SHH/TL-1 properties to the device's collected
information model using the Prime Network Soft Properties
Manager (Administrator security level required).
VNE Tools Contains the following submenu options:
• Poll Now—Updates the VNE information.
• Stop VNE—Stops the VNE.
• Start VNE—Starts the VNE.
Details Pane
Selecting a device or link in the path trace pane automatically highlights the related parameters in the
details pane.
The details pane, with its Layer and Business tabs, displays the supported parameters of the selected
element in a table, with the ingress and egress ports along the top and the parameters on the left.
Any inconsistencies between the two connected ports are colored to emphasize a discrepancy, such as
different admin statuses.
Step 1 Open the Cisco PathTracer window as described in Launching Path Traces, page 11-3.
Step 2 Click Save MultiPath in the toolbar.
Step 3 In the Save dialog box, navigate to the directory where you want to save the file and enter a name for
the map file.
Step 4 Click Save. The map file is saved in the selected directory.
Step 1 In Cisco Prime Network Vision, choose File > Load MultiPath from the main menu. The Open dialog
box is displayed.
Step 2 Navigate to the directory of the saved file and select the file.
Step 3 Click Open. The previously saved map is displayed in the Cisco PathTracer window.
Note This topic applies to the Cisco PathTracer details window only.
To save Cisco PathTracer counter values that are generated over a period of time:
Step 1 Open the Cisco PathTracer details window as described in Viewing Path Trace Details, page 11-21.
Step 2 Click Start Saving to File in the toolbar.
Step 3 In the Export Table to File dialog box, navigate to the directory where you want to save the
Cisco PathTracer counter values.
Step 4 In the File name field, enter a name for the file in which to save the counter values.
Step 5 Click Save. Cisco PathTracer starts saving the counter values to the specified file.
Step 6 To stop exporting counter values to the file, click Stop Saving to File in the toolbar.
Cisco PathTracer stops exporting the counter values to the file.
Step 1 Load the required map file as described in Saving and Opening Cisco PathTracer Map Files, page 11-26.
The Cisco PathTracer window is displayed with the previously saved map file.
Step 2 Click Run Again in the toolbar.
The path trace runs automatically using the same source and destination as the loaded map file, and a
new tab is displayed in the Cisco PathTracer window with the updated map. The tab displays the date
and time when the path was rerun.
Step 3 Compare the previous map to the updated one by switching between the tabs in the Cisco PathTracer
window.
Note • If you load a Cisco PathTracer map file that does not contain the same source and destination
information as the map that is currently displayed in the window, the map is automatically opened
in a new Cisco PathTracer window.
• If you load a Cisco PathTracer map file that contains the same source and destination information
as a map that is currently displayed in the window, the map is loaded in a new tab in the same
window.
Field Description
Encapsulation Type Encapsulation type, such as Point-to-Point Protocol over ATM (PPPoA).
Binding Information Name of the subscriber.
Binding Status Binding status: bound or unbound.
Tunnel Session Count Number of current sessions.
Tunnel Remote ID Remote tunnel identifier.
Tunnel ID Local tunnel identifier.
Tunnel Name Name of the subscriber and the tunnel identifier.
Session ID Session identifier.
Traffic > Number of traffic packets passing through the L2TP tunnel.
L2TPSessionCounters
Traffic < Number of traffic packets passing through the L2TP tunnel.
L2TPSessionCounters
Field Description
Tunnel Ctl Errors Number of control errors.
Tunnel State Tunnel state: unknown, idle, connecting, established, or disconnecting.
Session Type Session type: unknown, LAC, or LNS.
Peer Name Peer name.
Tunnel Remote IP Remote IP address of the tunnel.
Last Error Code Value of the last error code that caused the tunnel disconnection.
Session State Session state: unknown, idle, connecting, established, or disconnecting.
Remote Session ID Remote session identifier.
Note An LSP can be traced and displayed by Cisco PathTracer as part of an end-to-end tracing of a service;
for example, when viewing a path between one CE device and another. Cisco PathTracer traces the path
that goes over circuits or VLANs in the access networks. It also traces the LSPs between the VRFs going
through all intermediate devices such as CE devices, aggregation switches, PE routers, and core routers.
To view a specific path, you must specify an initial starting point, such as an IP interface; specifying a
destination IP address is optional. If the traced path (for example, a VC or VLAN) ends in a router,
Cisco PathTracer finds the next hop according to the destination IP address. If you select an endpoint,
Cisco PathTracer extracts the relevant IP address from this point and uses it as the destination.
The following topics provide more information on using Cisco PathTracer in MPLS networks:
• Cisco PathTracer MPLS Start and Endpoints, page 11-31
• Using Cisco PathTracer for CSC Configurations, page 11-32
• Using Cisco PathTracer for Layer 3 VPNs, page 11-33
• Using Cisco PathTracer for Layer 2 VPNs, page 11-33
• Using Cisco PathTracer for MPLS TE Tunnels, page 11-34
If you choose the Start Here option, Table 11-13 lists the endpoints that can be selected as path
destinations.
The Cisco PathTracer window is displayed. From this window you can open the Cisco PathTracer details
window with the VPN information displayed in the Layer 2 and Layer 3 tabs.
Note If multiple paths are selected in the paths pane, or if nothing is selected in the paths pane, all available
paths are opened automatically, and each is displayed in a separate Cisco PathTracer window.
Table 11-14 describes the Layer 2 properties that can be displayed in the Layer 2 tab specifically for
VPNs.
Field Description
Top Label Details of the outer MPLS label.
Label Stack Details of the inner MPLS label.
MAC Address MAC address.
Tunnel ID Tunnel identifier. The identifier and the router IP address of the two
tunnel edges identify the pseudowire tunnel.
Tunnel Type Tunnel type:
• 0—Unknown
• 1—PWE3
• 2—TE
Tunnel Status Operational state of the tunnel: Up or Down.
Tunnel Local VC Label MPLS label that is used by the router to identify or access the tunnel. It
is inserted in the MPLS label stack by the local router.
Tunnel Peer VC Label MPLS label that is used by the router to identify or access the tunnel. It
is inserted in the MPLS label stack by the peer router.
Tunnel Local Router IP IP address of the tunnel edge, which is used as the MPLS router
identifier.
Tunnel Peer Router IP IP address of the peer tunnel edge, which is used as the MPLS router
identifier.
Distribution Protocol Protocol used by MPLS to build the tunnel, such as LDP or TDP.
Type
Peer OID Tunnel identifier and device name.
Note Cisco PathTracer does not display or trace EXP bits for Layer 3 VPNs that use PBTS.
Layer 2 and Layer 3 path trace information is displayed in the Cisco PathTracer details window when a
path is traced over MPLS TE tunnels. To view Layer 2 path information, choose the Layer 2 tab and then
View > Show All. The path information is displayed in the active tab.
Table 11-15 describes the Layer 2 properties that can be displayed in the Layer 2 tab specifically for
MPLS TE tunnels.
Field Description
MPLS TE Properties MPLS TE data set in an MPLS interface, primarily bandwidth allocation
levels and signaling protocol.
Tunnel Oper Status Operational status of the tunnel: Up or Down.
If this value is Up, the Tunnel Admin Status must also be Up. See Tunnel
Admin Status properties for additional information.
Tunnel Bandwidth Kbps Configured bandwidth (in Kb/s) for the tunnel.
Tunnel Description Description of the tunnel.
Tunnel Name Interface name.
Tunnel Admin Status Administrative status of the tunnel (Up or Down) with the following
caveats:
• If the Tunnel Oper Status value is Up, the Tunnel Admin Status
value must also be Up.
• If the Tunnel Admin Status value is Down, the Tunnel Oper Status
value must also be Down.
Tunnel Lockdown Whether or not the tunnel can be rerouted:
• Enabled—The tunnel cannot be rerouted.
• Disabled—The tunnel can be rerouted.
Tunnel LSP ID LSP identifier.
Tunnel Auto Route Whether or not destinations behind the tunnel are routed through the
tunnel: Enabled or disabled.
Tunnel Hold Priority Tunnel priority after path setup.
Tunnel Setup Priority Tunnel priority upon path setup.
Tunnel Path Option Tunnel path option:
• Dynamic—The tunnel is routed along the ordinary routing
decisions after taking into account the tunnel constraints such as
attributes, priority, and bandwidth.
• Explicit—The route is explicitly mapped with the included and
excluded links.
Tunnel Out Label TE tunnel MPLS label distinguishing the LSP selection in the adjacent
device.
Tunnel Affinity Tunnel’s preferential bits for specific links.
Table 11-15 Cisco PathTracer Layer 2 Properties for MPLS TE Tunnels (continued)
Field Description
Tunnel Destination Address IP address of the device in which the tunnel ends.
Tunnel Peak Rate Kbps Peak flow specification (in Kb/s) for this tunnel.
Tunnel Out Interface Interface through which the tunnel exits the device.
Tunnel Burst Kbps Burst flow specification (in Kb/s) for this tunnel.
Tunnel Average Rate Kbps Tunnel average rate in Kb/s.
Tunnel Affinity Mask Tunnel affinity bits that should be compared to the link attribute bits.
The following topics describe how you can use Cisco Prime Network Vision (Prime Network Vision) to
monitor Carrier Ethernet services:
• User Roles Required to Work with Carrier Ethernet Services, page 12-2
• Viewing CDP Properties, page 12-6
• Viewing Link Layer Discovery Protocol Properties, page 12-8
• Viewing Spanning Tree Properties, page 12-10
• Viewing Resilient Ethernet Protocol Properties, page 12-14
• Viewing Access Gateway Properties, page 12-18
• Working with Ethernet Link Aggregation Groups, page 12-21
• Viewing mLACP Properties, page 12-27
• Viewing Provider Backbone Bridge Properties, page 12-30
• Viewing EFP Properties, page 12-31
• Understanding EFP Severity and Ticket Badges, page 12-36
• Viewing EVC Service Properties, page 12-37
• Viewing and Renaming Ethernet Flow Domains, page 12-39
• Working with VLANs and VLAN Overlays, page 12-42
• Understanding Unassociated Bridges, page 12-70
• Working with Ethernet Flow Point Cross-Connects, page 12-72
• Working with VPLS and H-VPLS Instances, page 12-75
• Working with Pseudowires, page 12-88
• Working with Ethernet Services, page 12-101
• Viewing IP SLA Responder Service Properties, page 12-108
• Viewing IS-IS Properties, page 12-110
• Viewing OSPF Properties, page 12-113
Table 12-1 Default Permission/Security Level Required for Working with Carrier Ethernet
Services - Element Not in User’s Scope
Table 12-1 Default Permission/Security Level Required for Working with Carrier Ethernet
Services - Element Not in User’s Scope (continued)
Table 12-1 Default Permission/Security Level Required for Working with Carrier Ethernet
Services - Element Not in User’s Scope (continued)
Table 12-2 Default Permission/Security Level Required for Working with Carrier Ethernet
Services - Element in User’s Scope
Table 12-2 Default Permission/Security Level Required for Working with Carrier Ethernet
Services - Element in User’s Scope (continued)
Table 12-2 Default Permission/Security Level Required for Working with Carrier Ethernet
Services - Element in User’s Scope (continued)
In Logical Inventory
Step 1 In Prime Network Vision, double-click the device whose CDP properties you want to view.
Step 2 In the inventory window, click Logical Inventory > Cisco Discovery Protocol.
The CDP properties are displayed in logical inventory as shown in Figure 12-1.
Table 12-3 describes the CDP instance properties that are displayed.
Field Description
Process Process name; in this case, Cisco Discovery Protocol
Process Status Process status: Running or Disabled.
CDP Holdtime Specifies the amount of time a receiving device should hold the
information sent by a device before discarding it.
CDP Message Interval Interval between CDP advertisement transmissions.
CDP Local Device ID Local device identifier.
CDP Version CDP version: 1 or 2.
CDP Neighbors Table
Local Port Local port name.
Local Port ID Local port identifier.
Remote Device ID Remote device identifier.
Remote Port ID Remote port identifier.
Remote IP Address Remote IP address.
In Physical Inventory
Step 1 In Prime Network Vision, double-click the device with the Layer 2 port with the CDP information you
want to view.
Step 2 In the inventory window, select the required port under Physical Inventory.
The CDP information is displayed in the Discovery Protocols area in the Prime Network Vision content
pane:
• Discovery Protocol Type—CDP
• Info—Up or Down
In Logical Inventory
Step 1 In Prime Network Vision, double-click the device with the LLDP information you want to view.
Step 2 In the inventory window, choose Logical Inventory > Link Layer Discovery Protocol.
The LLDP properties are displayed in logical inventory as shown in Figure 12-2.
Table 12-4 describes the properties that are displayed for LLDP.
Field Description
Process Process; in this case, Link Layer Discovery Protocol
Process Status Process status: Running or Disabled.
LLDP Hold Time LLDP advertised hold time in seconds.
LLDP Reinitialization LLDP interface reinitialization delay in seconds
Delay
LLDP Advertisements LLDP advertisements interval in seconds.
Interval
Local System Name Local system name.
Local Chassis ID Local chassis identifier.
Field Description
LLDP Neighbors Table
Local Port Local port.
Local Port ID Local port identifier.
Local Port Name Local port name.
Remote System Name Remote system name.
Remote Chassis ID Remote chassis identifier.
Remote Port ID Remote port identifier.
Remote Port Name Remote port name.
Remote Management IP Remote management IP address.
In Physical Inventory
Step 1 In Prime Network Vision, double-click the device with the Layer 2 port with LLDP information you want
to view.
Step 2 In the inventory window, select the required port under Physical Inventory.
The LLDP information is displayed in the Discovery Protocols area in the Prime Network Vision content
pane:
• Discovery Protocol Type—LLDP
• Info—Tx (Enabled or Disabled), Rx (Enabled or Disabled).
Step 1 In Prime Network Vision, double-click the element whose STP properties you want to view.
Step 2 In the inventory window, choose Logical Inventory > Spanning Tree Protocol.
Step 3 STP properties are displayed in logical inventory as shown in Figure 12-3.
Table 12-5 describes the properties that are displayed for STP.
Field Description
Process Process; in this case, Spanning Tree Protocol.
Process Status Process status: Running or Disabled.
Bridge Hello Time Hello message keepalive interval (in seconds) when the port is the root.
Hello Time Current hello time (in seconds).
Bridge Forward Delay When the port is the root and in listening or learning state, amount of
time to wait (in seconds) before proceeding to the forwarding state.
Forward Delay Current bridge forward delay (in seconds).
Bridge Max Age When the port is the root, maximum age of learned Spanning Tree
Protocol port information (in seconds).
Max Age Current maximum age (in seconds).
STP Protocol STP version: MST, RSTP, PVSTP, MSTP, or RPVST.
UplinkFast PVSTP Uplink Fast function status: Up or Down.
BackboneFast PVSTP BackboneFast function status: Up or Down.
Field Description
STP Instance Info Table
STP Instance ID STP instance name.
VLAN IDs VLAN identifiers.
Bridge Priority Bridge priority.
STP Root Port Hyperlinked entry to the STP port in logical or physical inventory.
Root Cost Root cost value for this bridge.
Designated Root MAC address of the designated root.
Bridge ID Bridge identifier (MAC address).
Bridge Hello Time Hello message keepalive interval (in seconds) when the port is the root.
Hello Time Current hello time (in seconds).
Bridge Forward Delay When the port is the root and in the listening or learning state, amount
of time to wait (in seconds) before proceeding to the forwarding state.
Forward Delay Current bridge forward delay (in seconds).
Bridge Max Age When the port is the root, maximum age of learned Spanning Tree
Protocol port information (in seconds).
Max Age Current maximum age (in seconds).
Field Description
STP Instance ID STP instance identifier.
VLAN ID VLAN identifier.
Bridge Priority Bridge priority.
Bridge ID Bridge identifier (MAC address).
Root Cost Root cost value for this bridge.
Designated Root MAC address of the designated root.
Bridge Hello Time Hello message keepalive interval (in seconds) when the port is the root.
Hello Time Current hello time (in seconds).
Bridge Forward Delay When the port is the root and in listening or learning state, amount of
time to wait (in seconds) before proceeding to the forwarding state.
Forward Delay Current bridge forward delay (in seconds).
Bridge Max Age When the port is the root, the maximum age of learned Spanning Tree
Protocol port information (in seconds).
Field Description
Max Age Current maximum age (in seconds).
STP Protocol Specification Specific STP protocol type or variant used for this instance, such as
Rapid PvSTP.
Is Root Whether or not the port is the root: True or False.
Ports Info Table
STP Port Hyperlinked entry to the STP port in physical inventory.
Port State STP port state: Disabled, Blocking, Listening, Learning, or Forwarding,
Port Role Port role: Unknown, Backup, Alternative, Designated, Root, or
Boundary.
Port Priority Default 802.1p priority assigned to untagged packets arriving at the port.
Port Path Cost Port path cost, which represents the media speed for this port.
Point To Point Port Whether or not the port is linked to a point-to-point link: True or False.
Edge Port Whether or not the port is an edge port; that is, whether it is connected
to a nonbridging device: True or False.
MST Port Hello Time This field is displayed in the Ports Info Table only for MST.
In seconds, the interval between hello BPDUs sent by root switch
configuration messages. The range is 1 to 10 seconds.
Port Identifier STP port identifier.
Portfast Whether or not STP PortFast is enabled on the port: Up or Down.
Designated Port Identifier Designated STP port identifier.
Designated Bridge STP designated bridge.
BPDU Filter BPDU Filter status: Up or Down.
BPDU Guard BPDU Guard status: Up or Down.
Step 5 To view MSTP properties, choose the required MSTP entry in logical inventory under Spanning Tree
Protocol.
Table 12-7 describes the information that is displayed for MSTP.
Field Description
MST Force Version Force version used: MST, PVSTP, RSTP, STP, or Unknown.
MST Cfg ID Rev Level Revision level used by the selected device and negotiated with other
devices.
MST Cfg ID Name MSTP instance name.
MST Max Instances Maximum number of MSTP instances.
MST Cfg ID Fmt Sel Configuration format used by this device and negotiated with other
devices.
MST External Root Cost External root cost of the MSTP instance.
The following topics describe how to view STP properties related to:
• VLAN domain views and overlays—See Viewing STP Information in VLAN Domain Views and
VLAN Overlays, page 12-63.
• VLAN service link properties—See Viewing STP Properties for VLAN Service Links, page 12-64.
Step 1 In Prime Network Vision, double-click the device configured for REP.
Step 2 In the inventory window, choose Logical Inventory > Resilient Ethernet Protocol.
Figure 12-4 shows an example of REP in logical inventory.
Field Description
Process Process name; in this case, Resilient Ethernet Protocol.
Process Status State of the REP process, such as Running or Down.
Administrative VLAN Administrative VLAN used by REP to transmit its hardware flooding
layer messages. Values range from 1 to 4094.
Notification Enabled Whether or not notification is enabled: True or False.
REP Version Version of REP being used.
REP Segments Table
Segment ID Segment identifier.
Segment Complete Whether the segment is complete; that is, that no port in the segment is
in a failed state: True or False.
Step 3 To view REP segment properties, double-click the required entry in the REP Segments table.
Figure 12-5 shows an example of REP segment properties in logical inventory.
Table 12-9 describes the information that is displayed for REP segments.
Field Description
Segment ID Segment identifier.
Segment Complete Whether the segment is complete; that is, that no port in the segment is
in a failed state: True or False.
Segment Ports Table
Port Hyperlinked entry to the port in physical inventory.
Port State Current operational link state of the REP port: None, Init Down, No
Neighbor, One Way, Two Way, Flapping, Wait, or Unknown.
Port Type Port type: Primary Edge, Secondary Edge, or Intermediate.
Port Role Role or state of the REP port depending on its link status and whether it
is forwarding or blocking traffic: Failed, Alternate, or Open.
Remote Device Name Name of the neighbor device that this port is connected to on this
segment. This value can be null.
Remote Port Name Name of the neighbor port on the neighbor bridge that this port is
connected to on this segment. This value can be null.
Blocked VLANs VLANs that are blocked on this port.
Configured Load List of VLANs configured to be blocked at this port for REP VLAN load
Balancing Blocked balancing.
VLANs
Preemptive Timer Amount of time, in seconds, that REP waits before triggering
preemption after the segment is complete. The entry can range from 0 to
300, or be Disabled.
The value Disabled indicates that no time delay is configured, and that
the preemption occurs manually.
This property applies only to REP primary edge ports.
LSL Ageout Timer Using the Link Status Layer (LSL) age-out timer, the amount of time, in
milliseconds, that the REP interface remains up without receiving a
hello from a neighbor.
Remote Device MAC MAC address of the neighbor bridge that this port is connected to on this
segment. This value can be null.
The following topics describe how to view REP properties related to VLANs:
• VLAN domain views and overlays—See Viewing REP Information in VLAN Domain Views and
VLAN Overlays, page 12-60.
• VLAN service link properties—See Viewing REP Properties for VLAN Service Links, page 12-61.
Table 12-10 describes the information that is displayed for an access gateway.
Field Description
Group Name Access gateway group name.
Group Type Group type: MSTAG or REPAG.
Interface Properties
Interface Hyperlink to the interface in physical inventory on which access
gateway is configured.
Config Name Name of the MSTP region.
The default value is the MAC address of the switch, formatted as a
text string using the hexadecimal representation specified in IEEE
Standard 802.
Max Age In seconds, the maximum age for the bridge.
Values range from 6 to 40 seconds.
Provider Bridge Whether the current instance of the protocol is in 802.1ad mode:
True or False.
Bridge Address Bridge identifier for the interface.
Port Identifier Port identifier for the interface.
External Cost External path cost on the current port.
Values range from 1 to 200000000.
Config Revision Number of the configuration revision.
Hello Time Current hello time (in seconds)
Port Active Whether or not the port is active: True or False.
BPDUs Sent Number of BPDUs sent.
Reversion Control Enabled Whether reversion control is enabled: True or False.
Table 12-11 describes the information that is displayed for an access gateway instance.
Field Description
Interface Key Hyperlink to the interface in physical inventory on which access
gateway is configured.
Config Name Name of the MSTP region.
The default value is the MAC address of the switch, formatted as a
text string using the hexadecimal representation specified in IEEE
Standard 802.
Config Revision Number of the configuration revision.
Max Age In seconds, the maximum age for the bridge.
Values range from 6 to 40 seconds.
Provider Bridge Whether the current instance of the protocol is in 802.1ad mode:
True or False.
Bridge Address Bridge identifier for the current switch.
BPDUs Sent Number of BPDUs sent.
Field Description
Port Identifier Port identifier for the interface.
Reversion Control Enabled Whether reversion control is enabled: True or False.
External Cost External path cost on the current port.
Values range from 1 to 200000000.
Hello Time Current hello time (in seconds)
Port Active Whether or not the port is active: True or False.
Instances Table
Instance ID Access gateway instance identifier.
VLAN IDs VLAN identifiers.
Cost Path cost for this instance.
Bridge Priority Priority associated with current bridge.
Root Bridge Priority Priority associated with the root bridge.
Root Bridge Address Address of the root bridge.
Port Priority Priority of the interface for this instance.
Topology Changes Number of times the topology has changed for this instance.
Access GW External Cost External root cost of this instance.
Note Cisco CRS devices must be configured to receive SNMP traps in order to view Ethernet LAG properties.
For more information on required SNMP settings, see the Cisco Prime Network 3.8 Administrator
Guide.
Step 1 In Prime Network Vision, double-click the device with the link aggregation group you want to view.
Step 2 In the inventory window, choose Logical Inventory > Ethernet Link Aggregation.
The link aggregation properties are displayed as shown in Figure 12-8.
Table 12-12 describes the aggregation group properties that are displayed in the Data Link Aggregations
table.
Field Description
ID Aggregation identifier. Double-click the entry to view the properties for
that aggregation.
Type Aggregation group type: Ethernet Channel or IEEE 8023 AD LAG.
Group Number Aggregation group number.
Field Description
Bandwidth Aggregation bandwidth.
Aggregation Control Aggregation control protocol: Manual, Link Aggregation Control
Protocol Protocol (LACP), or Port Aggregation Protocol (PagP).
Status Aggregation status: Up or Down.
MAC Address Aggregation MAC address.
Step 3 To view properties for a specific aggregation, double-click the group identifier.
The information that is displayed depends on the type of aggregation:
• For Ethernet Channel aggregations, see Table 12-13.
• For IEEE 802.3 AD aggregations, see Table 12-14.
Field Description
Group Number Aggregation group number.
Bandwidth Aggregation bandwidth in b/s.
Control Protocol Aggregation control protocol: Manual, Link Aggregation Control Protocol (LACP), or Port
Aggregation Protocol (PagP).
MAC Address Aggregation MAC address.
Administrative State Aggregation administrative status: Up or Down.
Operational State Aggregation operational status: Up or Down.
Adjacent Adjacent group, hyperlinked to the group in logical inventory.
mLACP Properties mLACP properties are displayed if the aggregation group is associated with an ICCP redundancy
group.
ICCP Redundancy ICCP redundancy group associated with this aggregation group, hyperlinked to the relevant entry
Group in logical inventory.
mLACP Role Role of the LAG in the redundancy group: Active or Standby.
mLACP Operational MAC address used in a dual-homed environment that is selected by ICCP from one of the
System MAC configured system MAC addresses for one of the points of attachment (PoAs).
mLACP Operational Priority used in a dual-homed environment that is selected by ICCP from the configured system
System Priority priority on one of the PoAs.
mLACP Failover Configured mLACP failover mode: Revertive or Nonrevertive.
Option
mLACP Max Bundle Maximum number of links allowed per bundle.
Field Description
Aggregated Ports Table
ID Aggregated port identifier, hyperlinked to the interface in physical inventory.
Type Aggregation type, such as Layer 2 VLAN.
Mode VLAN mode, such as Trunk.
Native VLAN ID VLAN identifier (VID) associated with this VLAN. The range of VLANs is 1 to 4067.
VLAN Encapsulation Type of encapsulation configured on the VLAN, such as IEEE 802.1Q.
Type
Allowed VLANs List of VLANs allowed on this interface.
VLAN Encapsulation VLAN administration encapsulation type, such as IEEE 802.1Q.
Admin Type
Subinterfaces Table
Address IP address of the subinterface.
Mask Subnet mask applied to the IP address.
VLAN Type Type of VLAN, such as Bridge or IEEE 802.1Q.
Operational State Operational state of the subinterface: Up or Down.
VLAN ID VLAN identifier.
Inner VLAN CE-VLAN identifier.
IP Interface IP interface configured as part of the subinterface, hyperlinked to the routing entity or VRF in
logical inventory.
VRF Name VRF associated with the subinterface.
Is MPLS Whether the subinterface is enabled for MPLS: True or False.
This column is displayed when at least one interface is MPLS-enabled.
Tunnel Edge Whether this is a tunnel edge: True or False.
VC Virtual circuit identifier, hyperlinked to the VC Table when the subinterface is configured for
ATM VC.
Binding Hyperlinked entry to the specific bridge in logical inventory.
EFPs Table
EFP ID EFP identifier.
Operational State EFP operational state: Up or Down.
VLAN VLAN associated with this EFP.
Inner VLAN CE-VLAN identifier.
Translated VLAN Translated, or mapped, VLAN identifier.
Translated Inner VLAN Translated, or mapped, inner VLAN identifier.
Binding Hyperlinked entry to the specific bridge in logical inventory.
Description Description for the EFP.
Field Description
Group Number Aggregation group number.
Bandwidth Aggregation bandwidth.
Control Protocol Aggregation control protocol: Manual, Link Aggregation Control
Protocol (LACP), or Port Aggregation Protocol (PagP).
MAC Address Aggregation MAC address.
Administrative State Aggregation administrative status: Up or Down.
Operational State Aggregation operational status: Up or Down.
Dot3ad Agg Partner System Priority Priority of the partner system.
Dot3ad Agg MAC Address Aggregation MAC address.
Dot3ad Agg Actor Admin Key Actor administrative key.
Dot3ad Agg Actor System Priority Actor system priority.
Dot3ad Agg Partner Oper Key Partner operational key.
Dot3ad Agg Actor Oper Key Actor operational key.
Dot3ad Agg Collector Max Delay Maximum delay (in microseconds) for either delivering or discarding a
received frame by the frame collector.
Dot3ad Agg Actor System ID Actor system identifier, in the form of a MAC address.
Dot3ad Agg Partner System ID Partner system identifier, in the form of a MAC address.
mLACP Properties mLACP properties are displayed if the aggregation group is associated
with an ICCP redundancy group.
ICCP Redundancy Group ICCP redundancy group associated with this aggregation group,
hyperlinked to the relevant entry in logical inventory.
mLACP Role Role of the LAG in the redundancy group: Active or Standby.
mLACP Operational System MAC MAC address used in a dual-homed environment that is selected by
ICCP from one of the configured system MAC addresses for one of the
points of attachment (PoAs).
mLACP Operational System Priority Priority used in a dual-homed environment that is selected by ICCP
from the configured system priority on one of the PoAs.
mLACP Failover Option Configured mLACP failover mode: Revertive or Nonrevertive.
mLACP Max Bundle Maximum number of links allowed per bundle.
Aggregated Ports Table
ID Port identifier, hyperlinked to the interface in physical inventory.
Type Type of VLAN, such as Layer 2 VLAN.
Discovery Protocols Discovery protocols used on this port.
Field Description
Subinterfaces Table
Address IP address of the subinterface.
Mask Subnet mask applied to the IP address.
VLAN Type Type of VLAN, such as Bridge or IEEE 802.1Q.
Operational State Operational state of the subinterface: Up or Down.
VLAN ID VLAN identifier.
Inner VLAN CE-VLAN identifier.
IP Interface IP interface configured as part of the subinterface, hyperlinked to the
routing entity or VRF in logical inventory.
VRF Name VRF associated with the subinterface.
VC Virtual circuit identifier, hyperlinked to the VC Table when the
subinterface is configured for ATM VC.
Binding Hyperlinked entry to the specific bridge in logical inventory.
EFPs Table
EFP ID EFP identifier.
Operational State EFP operational state: Up or Down.
VLAN VLAN associated with this EFP.
Inner VLAN CE-VLAN identifier.
Translated VLAN Translated, or mapped, VLAN identifier.
Translated Inner VLAN Translated, or mapped, inner VLAN identifier.
Binding Hyperlinked entry to the specific bridge in logical inventory.
Description Description for the EFP.
LACP Port Entries
Aggregated Port Port on which the aggregation is configured, hyperlinked to the entry in
physical inventory.
Dot3ad Agg Port Partner Admin Port Priority Administrative port priority for the partner.
Dot3ad Agg Port Partner Admin Key Administrative key for the partner port.
Dot3ad Agg Port Partner Oper Port Priority Priority assigned to the aggregation port by the partner.
Dot3ad Agg Port Actor Oper State Local operational state for the port.
Dot3ad Agg Port Actor Admin State Local administrative state as transmitted by the local system in LACP
data units (LACPDUs).
Dot3ad Agg Port Selected Agg ID Selected identifier for the aggregation port.
Dot3ad Agg Port Partner Oper Key Operational key for the partner port.
Dot3ad Agg Port Partner Admin State Partner administrative state.
Dot3ad Agg Port Actor Port Priority Priority assigned to the local aggregation port.
Dot3ad Agg Port Partner Oper State Partner administrative state as transmitted by the partner in the most
recently transmitted LAPCDU.
Dot3ad Agg Port Attached Agg ID Identifier of the aggregator that the port is attached to.
Field Description
Dot3ad Agg Port Actor Admin Key Administrative key for the local port.
Dot3ad Agg Port Actor Port Number assigned to the local aggregation port.
Dot3ad Agg Port Partner Oper Port Number assigned to the aggregation port by the partner.
Dot3ad Agg Port Actor Oper Key Operational for the local port.
Dot3ad Agg Port Partner Admin Port Administrative value of the port for the partner.
Step 1 In Prime Network Vision, double-click the element configured for mLACP.
Step 2 In the inventory window, choose Logical Inventory > ICCP Redundancy.
In response, Prime Network Vision lists the Inter-Chassis Communication Protocol (ICCP) redundancy
groups configured on the device as shown in Figure 12-9.
Table 12-15 describes the information displayed in the ICCP Redundancy Groups table.
Field Description
Group Number ICCP group identifier.
Peer Monitoring Option Method used to monitor the peer: BFD or IP Reachability
Monitoring.
Member IP Address IP address of the neighbor PoA device.
Member Device Name Name of the neighbor PoA device.
mLACP Node ID Identifier used by this member of the mLACP redundancy group.
mLACP Configured System System MAC address of the redundancy group advertised to other
MAC members of the mLACP redundancy group and used for arbitration.
mLACP Configured System System priority advertised to other mLACP members of the
Priority redundancy group.
Step 3 To view additional information about an ICCP redundancy group, do either of the following:
• In the logical inventory window navigation pane, choose Logical Inventory ICCP Redundancy >
ICCP-group.
• In the logical inventory content pane, right-click the required group in the ICCP Redundancy Groups
table and choose Properties.
The ICCP Redundancy Group Properties window is displayed with the Backbone Interfaces and Data
Link Aggregations tabs as shown in Figure 12-10.
Table 12-16 describes the information available in the ICCP Redundancy Group Properties window.
Field Description
Group Number ICCP group identifier.
Peer Monitoring Option Method used to monitor the peer: BFD or IP Reachability
Monitoring.
Member IP Address IP address of the neighbor PoA device.
Member device name Name of the neighbor PoA device.
mLACP Node ID Identifier used by this member of the mLACP redundancy group.
mLACP Configured System System MAC address of the redundancy group advertised to other
MAC members of the mLACP redundancy group and used for arbitration.
mLACP Configured System System priority advertised to other mLACP members of the
Priority redundancy group.
Backbone Interfaces Tab
ID Backbone interface defined for the redundancy group, hyperlinked
to the relevant entry in logical inventory.
Status Status of the backbone interface: Up, Down, or Unknown.
Data Link Aggregations Tab
ID Link aggregation group associated with the redundancy group,
hyperlinked to the relevant entry in logical inventory.
Type Aggregation group type: Ethernet Channel or IEEE 8023 AD LAG.
Group Number Aggregation group number.
Bandwidth Aggregation bandwidth.
Aggregation Control Aggregation control protocol: Manual, LACP, or PAgP.
Protocol
Status Aggregation status: Up or Down.
MAC Address Aggregation MAC address.
Step 4 To view additional mLACP properties, double-click the entry for the required link aggregation group in
the Data Link Aggregations tab.
mLACP information is displayed in the Link Aggregation Group Properties window, as described in the
following tables:
• Table 12-13—LAG Ethernet Channel Properties
• Table 12-14—LAG IEEE 802.3 AD Properties
Step 1 In Prime Network Vision, double-click the element configured for PBB.
Step 2 In the inventory window, choose Logical Inventory > BridgeILans > PBB-bridge.
Figure 12-11 shows an example of PBB properties in logical inventory.
Field Description
Name Identifier of the bridge as follows:
• For Cisco 7600 devices, the identifier of the MAC tunnel
created.
• For Cisco ASR 9000-series devices, the identifier is a
combination of the bridge group and the bridge domain on the
B-Bridge component.
IB Bridge Mapping Table
ISID 24-bit entry representing the Backbone service instance.
I-Bridge XID of the I-Bridge component, hyperlinked to the relevant bridge
in logical inventory.
B-Bridge XID of the B-Bridge component, hyperlinked to the relevant bridge
in logical inventory.
Step 1 In the Prime Network Vision map view, select the required EFP in the navigation pane or in the map pane
and then do either of the following:
• Right-click the EFP and choose Properties.
• Choose Node > Properties.
Figure 12-12 shows an example of the EFP Properties window.
Table 12-18 describes the information displayed in the EFP Properties window.
Field Description
EFP ID Identifier for the EFP.
VLAN Match Criteria Match criteria configured on the EFP for forwarding decisions.
Split Horizon Group Split horizon group to which the EFP is associated.
If no split horizon group is defined, the value is null.
If only one split horizon group exists and it is enabled for the EFP, the
value is the default group 0.
Operational State Operational status of the EFP: Up or Down.
Administrative State Administrative status of the EFP: Up or Down.
Binding Hyperlinked entry to the relevant item in logical inventory, such as
a pseudowire or bridge.
Rewrite Definition Rewrite command configured on the EFP: pop, push, or translate.
Step 2 Click the hyperlink entry in the Binding field to view the related properties in logical inventory.
In this example, clicking the hyperlink displays the relevant bridge in logical inventory, as shown in
Figure 12-13.
Table 12-19 describes the information displayed for an EFP associated with a bridge.
Field Description
Name VLAN bridge name.
Type VLAN bridge type.
MAC Address VLAN bridge MAC address.
VLAN ID VLAN bridge VLAN identifier.
STP Instance STP instance information, hyperlinked to the STP entry in logical
inventory.
VSI VSI information, hyperlinked to the VSI entry in logical inventory.
Field Description
EFPs Table
EFP ID EFP identifier.
Operational State EFP operational state: Up or Down.
VLAN VLAN associated with this EFP.
Inner VLAN CE-VLAN identifier.
Translated VLAN Translated, or mapped, VLAN identifier.
Translated Inner VLAN Translated, or mapped, inner VLAN identifier.
Binding Hyperlinked entry to the specific interface and EFP entry in physical
inventory.
Description Description for the EFP.
Step 3 To view EFP properties in physical inventory, navigate to the required interface in one of the following
ways:
• In the bridge entry in logical inventory, click the hyperlinked entry in the Binding field.
• Use the procedure described in Viewing and Renaming Ethernet Flow Domains, page 12-39 to
navigate to the individual interface.
• In physical inventory, navigate to and then select the required interface.
The EFPs tab is displayed in the content pane next to the Subinterfaces tab as shown in Figure 12-14.
Field Description
EFP ID EFP identifier.
Operational State EFP operational state.
VLAN VLAN identifier.
Inner VLAN CE-VLAN identifier.
Translated VLAN Translated VLAN identifier.
Translated Inner VLAN Translated CE-VLAN identifier.
Binding Hyperlinked entry to the specific bridge or pseudowire in logical
inventory.
Description Configured description for the EFP.
Figure 12-15 EFP Severity and Ticket Badges Based on Underlying Service Instance
• If the Ethernet flow point element represents a VLAN interface for a regular switch port, the severity
and ticket badges are based on the corresponding port, as shown in Figure 12-16.
Figure 12-16 EFP Severity and Ticket Badges Based on Corresponding Port
Field Description
Storm Control and Monitoring Properties Area
Storm Control Status of storm control on the port: Enabled or Disabled.
Port Monitoring Status Status of port monitoring:
• Enabled—The switch sends keepalive messages on user network
interfaces (UNIs) and enhanced network interfaces (ENIs) and does
not send keep alive messages on network node interfaces (NNIs).
• Disabled—The switch does not send keepalive messages.
Port Monitoring Interval Keepalive interval in seconds. The default value is ten seconds.
Storm Control Level Representing a percentage of the total available bandwidth of the port,
the threshold at which additional traffic of the specified type is
suppressed until the incoming traffic falls below the threshold.
Storm Control Type Type of storm the port is configured for protection from: Broadcast,
Multicast, or Unicast.
Field Description
Security Properties Areas
Port Security Status of security on the port: Enabled or Disabled.
MAC Address Limit Maximum number of MAC addresses allowed on the interface.
Aging Type Type of aging used for automatically learned addresses on a secure port:
• Absolute—Times out the MAC address after the specified age-time
has been exceeded, regardless of the traffic pattern. This is the
default for any secured port, and the age-time value is set to 0.
• Inactivity—Times out the MAC address only after the specified
age-time of inactivity from the corresponding host has been
exceeded.
Aging Time Length of time, in minutes, that a MAC address can remain on the port
security table.
Violation Mode Action that occurs when a new device connects to a port or when a new
device connects to a port after the maximum number of devices are
connected:
• Protect—Drops packets with unknown source addresses until a
sufficient number of secure MAC addresses are removed to drop
below the maximum value
• Restrict—Drops packets with unknown source addresses until a
sufficient number of secure MAC addresses are removed to drop
below the maximum value and causes the Security Violation
counter to increment.
• Shutdown—Puts the interface into the error-disabled state
immediately and sends an SNMP trap notification.
Step 1 In Prime Network Vision, choose Network Inventory > Ethernet Flow Domains.
The Ethernet Flow Domain List window is displayed with the domain name, the system-defined domain
name, and a brief description for each Ethernet flow domain as shown in Figure 12-18.
Table 12-22 describes the information displayed in the Ethernet Flow Domain Properties window.
Note Not all fields are available in all tables. The table contents depend on the domain type, such as
FastEthernet.
Field Description
Domain Name Name of the selected domain.
System Defined Name Domain name as identified by the most dominant device and its lowest
port name lexicographically.
Elements Table
ID Interface identifier, hyperlinked to the interface in physical inventory.
Type Aggregation group type: Ethernet Channel (EtherChannel), or IEEE
8023 AD LAG (IEEE 802.3 link aggregation group).
Discovery Protocols Discovery protocols used on the interface.
Is ELMI Enabled Whether or not Ethernet LMI is enabled on the interface: True or False.
Step 4 To navigate to the individual interface or link aggregation group, click an interface identifier or group.
The interface or link aggregation group properties are displayed in the inventory window.
Table 12-23 describes the icons that Prime Network Vision uses to represent VLAN elements.
VLANs
Prime Network Vision discovers and allows you to display maps with a network-level view of VLANs.
In Prime Network, a VLAN entity consists of one or more switching entities and the corresponding EFP
elements.
A network VLAN represents the virtual LAN. The network VLAN holds its contained switching entities
and can be associated to a customer. The network VLAN also holds the Ethernet flow points that are part
of the network VLAN but not part of any switching entity. For example, a port that tags ingress flows
after which the flow moves to a different VLAN.
Switching Entities
A switching entity represents a device-level Layer 2 forwarding entity (such as a VLAN or bridge
domain) that participates in a network VLAN. A switching entity is associated to a network VLAN
according to its relationship to the same Ethernet Flow Domain (EFD) and the VLAN identifier.
If you right-click a switching entity in Prime Network Vision and then choose Inventory, the inventory
window is displayed with the corresponding bridge selected in Logical Inventory.
A switching entity typically contains EFP elements.
An Ethernet flow point (EFP) can represent a port that is configured for participation in a specific
VLAN.
If you right-click an EFP in Prime Network Vision and then choose Inventory, the inventory window is
displayed with the corresponding port selected in Physical Inventory.
EFPs that are located in a switching entity represent Ethernet ports that are configured as switch ports
(in either Access, Trunk, or Dot1Q tunnel mode).
Figure 12-20 shows an example of EFPs configured as switch ports in Prime Network Vision.
EFPs that are located directly inside a VLAN represent one of the following:
• Termination point EFPs—Ethernet ports that are at the edge of a Layer 2 domain flow, such as a
VLAN, on which traffic enters a Layer 3 domain or a different Layer 2 domain, such as EoMPLS.
These ports are found on such devices as the Cisco 7600 series, Cisco GSR, and Cisco ASR 9000
series devices.
These EFPs are typically connected to a switching entity inside the VLAN by a VLAN link, as
shown in Figure 12-21.
• Edge EFPs—A subset of EFPs that exist inside a switching entity but that are not connected to other
EFPs and that represent edge EFPs in the context of the VLAN.
In Prime Network Vision, edge EFPs are displayed directly under the VLAN at the same level as
their switching entities and are connected to their corresponding switching entities by a dotted link,
as shown in Figure 12-22.
An edge EFP can be displayed both inside and outside of its switching entity, as shown in
Figure 12-23, which contains two examples:
– In VLAN 1710@c7-sw8, EFP GigabitEthernet1/1/1@c7-sw8 (blue outline) is not connected to
any other EFP by a VLAN link, as opposed to EFP GigabitEthernet1/0/1@c7-sw8.
– Similarly, in VLAN 1710@c7-sw9, EFP FastEthernet1/0/1@c7-sw9 (red outline) is not
connected to any other EFP by a VLAN link, as opposed to EFP GigabitEthernet1/0/1@c7-sw9.
– Both EFPs (GigabitEthernet1/1/1@c7-sw8 and FastEthernet1/0/1@c7-sw9) are displayed
inside and outside of their switching entities.
Figure 12-23 Edge EFPs Displayed Inside and Outside of Switching Entities
You can delete EFPs and switching entities that have a reconciliation icon by right-clicking them and
choosing Delete. After all switching entities and EFPs are deleted from a network VLAN, the empty
network VLAN is automatically deleted from Prime Network Vision after a few minutes.
Note Adding VLANs affects other users if they are working with the same map.
Step 1 In Prime Network Vision, display the map to which you want to add the VLANs.
Step 2 Choose File > Add to Map > VLAN. The Add VLAN to map dialog box is displayed as shown in
Figure 12-24.
After you add a VLAN to a map, you can use Prime Network Vision to view its switching entities and
Ethernet flow points. For more information, see:
• Viewing and Renaming Ethernet Flow Domains, page 12-39
• Viewing EFP Properties, page 12-31
You can view additional information about REP and STP in logical inventory, VLAN domain views, and
VLAN overlays.
For REP, see:
• Viewing Resilient Ethernet Protocol Properties, page 12-14
• Viewing REP Information in VLAN Domain Views and VLAN Overlays, page 12-60
• Viewing REP Properties for VLAN Service Links, page 12-61
For STP, see:
• Viewing Spanning Tree Properties, page 12-10
• Viewing STP Information in VLAN Domain Views and VLAN Overlays, page 12-63
• Viewing STP Properties for VLAN Service Links, page 12-64
Step 1 In Prime Network Vision, double-click the device with VLAN mappings configured.
Step 2 In the inventory window, choose Physical Inventory > Chassis > slot > port.
Step 3 Click VLAN Mappings next to the Subinterfaces tab in the lower portion of the content pane.
The VLAN Mappings tab is displayed as shown in Figure 12-26.
Table 12-24 describes the information that is displayed in the VLAN Mappings table.
Field Description
Direction Whether the VLAN mapping is defined in the incoming or outgoing
direction: In or Out.
VLAN Customer-side VLAN identifier.
Inner VLAN Used for two-to-one mappings, the customer-side inner VLAN
identifier.
Translated VLAN Translated, or mapped, service-provider side VLAN identifier.
Translated Inner VLAN Translated, or mapped, service-provider side inner VLAN identifier.
Action Action taken if the VLAN traffic meets the specified mapping: Translate
or Drop.
Step 1 In Prime Network Vision, select the required VLAN in the map view.
Step 2 Right-click the VLAN and choose Add Associated VLAN.
The Add Associated VLAN table is displayed as shown in Figure 12-27.
In this example, the selected network VLAN has one associated VLAN: VLAN-1742.
Table 12-26 describes the information displayed in the Add Associated VLAN table.
Field Description
Name Name of the VLAN.
ID VLAN identifier.
EFD Name Name of the Ethernet flow domain.
EFD System Name Name that Prime Network assigns to the EFD.
System Name Name that Prime Network assigns to the VLAN.
Description Brief description of the VLAN.
Step 3 Select the required VLAN in the Add Associated VLAN table, then click OK.
The associated network VLAN is added to the map in Prime Network Vision.
Viewing Associated Network VLAN Service Links and VLAN Mapping Properties
After you add an associated network VLAN, you can:
• View the associated network VLAN service links in Prime Network Vision in the thumbnail view.
• View VLAN mapping properties in the Link Properties window.
To view associated network VLAN service links and VLAN mapping properties:
If VLAN tag manipulation is configured on the link, the VLAN Mapping Properties area in the Link
Properties window displays the relevant information. For example, in Figure 12-29, the VLAN Mapping
Properties area shows that a one-to-one VLAN mapping for VLAN tag 1709 to VLAN tag 709 is
configured on GigabitEthernet1/1/1 on c7-sw8 on the egress direction.
For additional information about viewing network VLAN service link properties, see:
• Viewing REP Properties for VLAN Service Links, page 12-61
• Viewing STP Properties for VLAN Service Links, page 12-64
1 The Ethernet topological link between port GigabitEthernet1/1/2 on VNE c7-sw10 and
GigabitEthernet1/1/2 on VNE c7-sw8.
2 The VLAN link between GigabitEthernet1/1/2@c7-sw10 EFP and GigabitEthernet1/1/2@c7-sw8
EFP.
3 Another view of the VLAN link (link 2), shown as a link between GigabitEthernet1/1/2@c7-sw10
EFP and GigabitEthernet1/1/2@c7-sw8 EFP.
4 Another view of the VLAN link (link 2), shown as a link between GigabitEthernet1/1/2@c7-sw10
EFP and GigabitEthernet1/1/2@c7-sw8 EFP.
The key point is that a link between a VNE and EFP, switching entity, or network VLAN does not
represent an association between the VNE and the logical element. Such a link is simply another view
of the VLAN link.
If the thumbnail view is closed, instead of a link between the VNE and EFP, you will see a link between
the VNE and the switching entity or network VLAN.
Step 1 Display the network map for which you want to create an overlay in Prime Network Vision.
Step 2 In the toolbar, choose Choose Overlay Type > VLAN.
Step 3 In the Select VLAN Overlay dialog box, do either of the following:
• Choose a search category, enter a search string, then click Go to narrow the selection to a set of
overlays or a specific overlay.
The search condition is “contains.” Search strings are case-insensitive. For example, if you choose
the Name category and enter “net,” Prime Network Vision displays overlays that have “net” in their
names. The string “net” can be at the beginning, middle, or end of the name, such as Ethernet.
• Choose Show All to view all overlays.
Step 4 Select an overlay, then click OK.
The network elements and physical links used by the selected VLAN overlay are highlighted in the
network map. All other network elements and links are dimmed. The VLAN name is displayed in the
title of the window. See Figure 12-32.
Note The overlay is a snapshot taken at a specific point in time. As a result, the information in the overlay
might become stale. To update the overlay, click Refresh the Last Selected Overlay in the toolbar.
Note The Overlay icon toggles between Show Overlay and Hide Overlay. When selected, the VLAN overlay
is displayed and the Hide Overlay tool is active. When deselected, the VLAN overlay is hidden and the
Show Overlay tool is active.
Table 12-27 REP Icons and Badges in VLAN Domain Views and Overlays
Table 12-27 REP Icons and Badges in VLAN Domain Views and Overlays (continued)
Blocking badge—Indicates
a REP alternate port.
Figure 12-33 VLAN Service Link Properties Window with REP Information
Table 12-28 describes the information that is displayed for REP for each end of the link.
Field Description
Segment ID REP segment identifier.
Port Type Port type: Primary Edge, Secondary Edge, or Intermediate.
Port Role Role or state of the REP port depending on its link status and
whether it is forwarding or blocking traffic: Failed, Alternate, or
Open.
Port Status Operational link state of the REP port: None, Init Down, No
Neighbor, One Way, Two Way, Flapping, Wait, or Unknown.
To view additional STP information in a VLAN overlay, right-click an STP link and choose Show
Callouts. The following STP port information is displayed as shown in Figure 12-34:
• Port name
• Port role
• Port state
Table 12-30 describes the information that is displayed for STP for the VLAN service link.
Field Description
Port State STP port state: Disabled, Blocking, Listening, Learning, or
Forwarding,
Port Role STP port role: Unknown, Backup, Alternative, Designated, Root, or
Boundary.
Step 1 In Prime Network Vision, choose Network Inventory > VTP Domains.
Step 2 Double-click the VTP domain you want to view.
The VTP Domain Properties window is displayed as shown in Figure 12-36.
Table 12-31 describes the information that is displayed in the VTP Domain Properties window.
Field Description
Managed Element Managed element name, hyperlinked to VTP in logical inventory.
Operating Mode VTP operating mode:
• Server—Allows VLAN creation, modification, and deletion, and
specification of other configuration parameters for the entire VTP
domain. Server is the default mode.
• Client—Same behavior as VTP server, except VLANs cannot be
created, changed, or deleted.
• Transparent—The device does not participate in the VTP. The
device does not advertise its VLAN configuration and does not
synchronize its VLAN configuration based on received
advertisements.
However, the device forwards received VTP advertisements out of
their trunk ports in VTP Version 2.
• Off—The device does not participate in VTP and does not forward
VTP advertisements.
Process Status Status of the VTP process: Running or Disabled.
Authentication Enabled Whether or not VTP authentication is enabled: True or False.
Authentication ensures authentication and integrity of switch-to-switch
VTP messages. VTP Version 3 introduces an additional mechanism to
authenticate the primary VTP server as the only device allowed to
change the VLAN configuration on a network-wide basis.
Configuration Revision 32-bit number that indicates the level of revision for a VTP packet.
Each VTP device tracks the VTP configuration revision number that is
assigned to it. Most VTP packets contain the VTP configuration revision
number of the sender.
Version VTP version: 1, 2, or 3.
Step 3 To view the VTP properties at the device, double-click the VTP domain.
Table 12-32 describes the VTP information that is displayed in the inventory window content pane.
Field Description
Operating Mode VTP operating mode: Server, Client, Transparent, or Off.
Domain Name VTP domain name.
Version VTP version: 1, 2, or 3.
Pruning Whether or not VTP pruning is enabled: True or False.
VTP pruning increases available bandwidth by restricting flooded
traffic to those trunk links that the traffic must use to access the
appropriate network devices.
Field Description
Configuration Revision 32-bit number that indicates the level of revision for a VTP packet.
Authentication Whether or not VTP authentication is enabled: True or False.
Step 4 When finished, press Ctrl + F4 to close each VTP properties window.
Step 1 In Prime Network Vision, double-click the device containing the VLAN bridges you want to view.
Step 2 In the inventory window, choose Logical Inventory > Bridges > bridge.
VLAN bridge properties are displayed as shown in Figure 12-37.
Table 12-33 describes the information that is displayed. Depending on the bridge configuration, any of
the tabs might be displayed for the selected bridge.
Field Description
Name VLAN bridge name.
Type VLAN bridge type.
MAC Address VLAN bridge MAC address.
VLAN ID VLAN bridge VLAN identifier.
STP Instance STP instance information, hyperlinked to the STP entry in logical
inventory.
Bridge Table Tab
MAC Address Bridge MAC address.
Port Port associated with the bridge, hyperlinked to the interface in physical
inventory.
Interfaces Tab
ID VLAN interface identifier, hyperlinked to the interface in physical
inventory.
Type VLAN interface type, such as Layer 2 VLAN.
Mode VLAN interface configuration mode:
• Unknown—The interface is not VLAN aware.
• Access—Puts the interface into permanent nontrunking mode and
negotiates to convert the link into a nontrunk link. The interface
becomes nontrunking.
• Dynamic Auto—The interface can convert the link to a trunk link. The
interface becomes a trunk if the neighbor interface is set to Trunk or
Dynamic Desirable mode.
• Dynamic Desirable—The interface actively attempts to convert the
link to a trunk link. The interface becomes a trunk if the neighboring
interface is set to Trunk, Dynamic Desirable, or Dynamic Auto mode.
Dynamic Desirable is the default mode for all Ethernet interfaces.
• Trunk—Puts the interface into permanent trunking mode and
negotiates to convert the link into a trunk link. The interface becomes
a trunk interface even if the neighbor interface is not a trunk interface.
• Dot1Q Tunnel—Configures the interface as a tunnel (nontrunking)
port to be connected in an asymmetric link with an 802.1Q trunk port.
802.1Q tunneling is used to maintain customer VLAN integrity across
a service provider network.
Native VLAN ID VLAN Identifier (VID) associated with this VLAN. The range of the
VLAN ID is 1 to 4067.
VLAN Encapsulation Type of encapsulation configured on the VLAN, such as IEEE 802.1Q.
Type
Field Description
Allowed VLANs List of the VLANs allowed on this VLAN interface.
VLAN Encapsulation VLAN administration encapsulation type, such as IEEE 802.1Q.
Admin Type
EFPs Tab
EFP ID EFP identifier.
Operational State EFP operational state.
VLAN VLAN identifier.
Inner VLAN CE-VLAN identifier.
Translated VLAN Translated VLAN identifier.
Translated Inner VLAN Translated CE-VLAN identifier.
Binding Port Hyperlinked entry to the port in physical inventory.
Description Brief description of the EFP.
Pseudowires Tab
ID Pseudowire identifier, hyperlinked to the VLAN entry in Bridges in logical
inventory.
Peer Identifier of the pseudowire peer, hyperlinked to the entry in the
Pseudowire Tunnel Edges table in logical inventory.
Tunnel ID Tunnel identifier.
Tunnel Status Status of the tunnel: Up or Down.
Peer Router IP IP address of the peer router for this pseudowire.
Sub Interfaces Tab
BER VLAN bit error rate.
Interface Name Interface on which the VLAN is configured.
VLAN Type Type of VLAN, such as Bridge or IEEE 802.1Q.
Operational State Subinterface operational state.
VLAN ID VLAN identifier.
Inner VLAN CE-VLAN identifier.
Step 3 When finished, press Ctrl + F4 to close each VLAN Bridge properties window.
Step 3 In the Add Unassigned Bridge to domain dialog box, select the required bridge and click OK.
The map is refreshed and displays the newly added bridge as shown in Figure 12-39.
Step 1 In Prime Network Vision, select the map to which you wish to add the cross-connect.
Step 2 Open the Add EFP Cross-Connect dialog box in one of the following ways:
• Choose File Add to Map > Cross Connect.
• In the toolbar, click Add to Map and choose Cross Connect.
Step 3 In the Add EFP Cross Connect to domain dialog box, select the required EFP cross-connect and click
OK.
The map is refreshed and displays the newly added EFP cross-connect.
Table 12-34 describes the information displayed for the EFP cross-connects in the Local Switching
Table.
Field Description
Key Entry key for the cross-connect group.
Entry Status Status of the cross-connect: Down, Unresolved, or Up.
Segment 1 Identifier of the first cross-connect segment, hyperlinked to the
relevant entry in physical inventory.
Segment 1 Port Name Identifier of the first cross-connect segment port.
Segment 1 Status Status of the first cross-connect segment, such as Admin Up, Admin
Down, Oper Down, or Up.
Segment 2 Identifier of the second cross-connect segment, hyperlinked to the
relevant entry in physical inventory.
Segment 2 Port Name Identifier of the second cross-connect segment port.
Segment 2 Status Status of the second cross-connect segment, such as Admin Up,
Admin Down, Oper Down, or Up.
Note If an element is not included in your scope, it is displayed with the locked device icon.
For information about sorting and filtering the table contents, see Working with Prime Network Tables,
page 2-53.
Step 4 In the Add VPLS Instance dialog box, select the instances that you want to add. You can select and add
multiple instances by pressing Ctrl while selecting individual instances or by pressing Ctrl +Shift to
select a group of instances.
Step 5 Click OK.
The VPLS instance is displayed in the navigation pane and in the content area. In addition, any
associated tickets are displayed in the ticket pane. See Figure 12-41.
The VPLS instance information is saved with the map in the Prime Network database.
Step 1 In Prime Network Vision, choose the map in which you want to apply an overlay.
Step 2 From the toolbar, choose Choose Overlay Type > VPLS.
Figure 12-42 shows an example of the Select VPLS Instance Overlay for map dialog box.
Step 5 To hide and view the overlay, click Hide Overlay/Show Overlay in the toolbar. The button toggles
depending on whether the overlay is currently displayed or hidden.
Step 6 To remove the overlay, choose Choose Overlay Type > None.
To view unidirectional or bidirectional pseudowire traffic links when a VPLS overlay is applied to a map:
Step 1 Right-click the required link in the overlay, and choose Show Callouts. The link must be visible (not
dimmed) in the map.
Link information is displayed as shown in Figure 12-44.
The callout window displays the following information for each link represented by the selected link:
• Link details and direction.
• Details of the sites using the link and the interlinks.
Step 2 To view the pseudowire link details, double-click the yellow callout window.
The details about the link are displayed in the Link Details window as shown in Figure 12-45.
1 Link details and direction. In this example, the link is from p1 to p2.
3 Link details and direction. In this example, the link is from p2 to p1.
2 and 4 Details of the pseudowire tunnel traversing this link.
Table 12-35 describes the information that is displayed for VPLS instance properties.
The tabs that appear in the window depend on the VPLS instance and its configuration.
Field Description
System Name Name that Prime Network Vision assigns to the VPLS instance.
Name User-defined name of the VPLS instance.
When the VPLS instance is created, the system name and this name
are the same. If you change the name of the VPLS instance
(right-click, then choose Rename), the changed name appears in
this field whereas the system name retains the original name.
VPN ID VPN identifier used in an MPLS network to distinguish between
different VPLS traffic.
VPLS Forwards Tab
Name User-defined name of the VPLS forward.
System Name Name that Prime Network Vision assigns to the VPLS forward.
Bridge Bridge that the VSI is configured to use, hyperlinked to the bridge
table in logical inventory.
VSI VSI hyperlinked to the relevant entry in logical inventory.
VPN ID VPN identifier for the VSI.
Field Description
Access Pseudowires Tab
Name Pseudowire name.
Port VSI on which the pseudowire is configured, hyperlinked to the
entry in logical inventory.
Local Router IP Local router IP address on which the pseudowire is configured.
Tunnel ID Virtual circuit identifier of the pseudowire.
PTP Tunnel Hyperlinked entry to the pseudowire properties in logical inventory.
Peer Router IP Peer router IP address on which the pseudowire is configured.
Peer OID Hyperlinked entry to the pseudowire properties of the peer.
Pseudowire Type Type of pseudowire, such as Ethernet, Ethernet Tagged, CESoPSN
Basic, PPP, or SAToP.
Pseudowire Edge Binding Pseudowire endpoint association:
Type
• 0—Unknown
• 1—Connection termination point
• 2—Ethernet flow point
• 3—Switching entity
• 4—Pseudowire switching entity
• 5—VPLS forward
Access Flow Points Tab
Name Access flow point name. Double-click to view port connector
properties.
Port Interface configured as a flow point, hyperlinked to the interface in
physical inventory.
If you right-click the VPLS forward and choose Inventory, the inventory window is displayed. If you
right-click the VPLS forward and choose Properties, the VSI Properties window is displayed. The
information displayed is the same for both options.
VSI properties are displayed as shown in Figure 12-48.
Table 12-36 describes the information that is displayed for the selected VSI.
Field Description
VSI Name VSI name.
VPN ID VPN identifier used in an MPLS network to distinguish between different
VPLS traffic.
VSI Mode VSI mode: Point-to-Point (default) or Multipoint.
Discovery Mode VSI discovery mode: Manual, BGP, LDP, RADIUS, DNS, MSS/OSS, or
Unknown.
Operational State VSI operational status: Up or Down.
Administrative State VSI administrative status: Up or Down.
Local Bridge Local bridge, hyperlinked to the bridge in logical inventory.
Pseudowires Table
Pseudowire ID Pseudowire identifier, hyperlinked to the Tunnel Edges table under
Pseudowires in logical inventory.
Autodiscovery Whether the pseudowire was automatically discovered: True or False.
Split Horizon SSH pseudowire policy that indicates whether or not packets are forwarded
to the MPLS core: True or False.
Pseudowire Peer IP IP address of the pseudowire peer.
Pseudowire VC ID Pseudowire virtual circuit identifier.
Figure 12-50 shows an example of the Tunnel Properties window that is displayed.
Table 12-37 describes the information that is displayed for pseudowire endpoint properties.
Field Description
Port VSI on which the pseudowire is configured, hyperlinked to the VSI
in logical inventory.
Peer Hyperlinked entry to the pseudowire endpoint peer pseudowires in
logical inventory.
Peer VC Label MPLS label that is used by this router to identify or access the tunnel.
It is inserted into the MPLS label stack by the peer router.
Tunnel Status Operational state of the tunnel: Up or Down.
Local VC Label MPLS label that is used to identify or access the tunnel. It is inserted
into the MPLS label stack by the local router.
Local Router IP IP address of this tunnel edge, which is used as the MPLS router
identifier.
Tunnel ID Identifier that, along with the router IP addresses of the two pseudowire
endpoints, identifies the PWE3 tunnel.
Peer Router IP IP address of the peer tunnel edge, which is used as the MPLS router
identifier.
Local MTU Size, in bytes, of the MTU on the local interface.
Remote MTU Size, in bytes, of the MTU on the remote interface.
Signaling Protocol Protocol used by MPLS to build the tunnel, such as LDP or TDP.
Pseudowire Type Type of pseudowire, such as Ethernet, Ethernet Tagged, CESoPSN
Basic, PPP, or SAToP.
Figure 12-52 shows an example of the information displayed for the interface in physical inventory.
The information displayed in this window is the same as that displayed when the interface is selected in
physical inventory.
The following information is displayed, depending on the interface and its configuration:
• Location and interface details.
• Technology-related information, such as Ethernet CSMA/CD or ATM IMA properties.
• VLAN configuration details.
• List of the configured subinterfaces on the port. For more information on the Subinterfaces table,
see Viewing a Port Configuration, page 3-24.
• List of the configured EFPs on the port. For more information on the EFPs table, see Viewing EFP
Properties, page 12-31.
• List of VLAN mappings configured on the port. For more information about the VLAN Mappings
table, see Viewing VLAN Mappings, page 12-50.
Note If an element is not included in your scope, it is displayed with the locked device icon.
For information about sorting and filtering the table contents, see Working with Prime Network Tables,
page 2-53.
Step 4 In the Add Pseudowire dialog box, select the pseudowires that you want to add. You can select and add
multiple pseudowires by pressing Ctrl while selecting individual pseudowires or by pressing
Ctrl +Shift to select a group of pseudowires.
Step 6 Click the pseudowire in the navigation pane or double-click the pseudowire in the map pane to view the
pseudowire components, such as pseudowire endpoints, pseudowire switching entities, and terminating
interfaces.
Figure 12-55 shows an example of an expanded pseudowire in Prime Network Vision.
The pseudowire information is saved with the map in the Prime Network database.
Table 12-38 describes the information presented in the Pseudowire Properties window.
Field Description
Name Name of the pseudowire.
Multisegment Pseudowire Whether or not the pseudowire is multisegment: True or False.
System Name Internal or system-generated name of the pseudowire.
Pseudowire Type Type of pseudowire, such as Ethernet, Ethernet Tagged, CESoPSN
Basic, PPP, or SAToP.
Step 4 To view the properties of a pseudowire endpoint associated with a pseudowire, right-click the required
pseudowire endpoint, and then choose Properties.
The Tunnel Properties window containing the pseudowire endpoint properties is displayed as shown in
Figure 12-50 and described in Table 12-37.
Step 5 To view the properties of a pseudowire switching entity associated with the pseudowire, select the
switching entity, and then choose Node > Inventory.
The Local Switching table is displayed as shown in Figure 12-40.
Table 12-34 describes the information displayed in the Local Switching table.
Step 6 To view the properties of the pseudowire endpoint that terminates on the subinterface, right-click the
required interface, and then choose Properties.
Note The selected port must be an Ethernet subinterface for the Contained Current CTPs table to be
displayed.
Table 12-39 describes the information displayed in the Contained Current CTPs table.
Field Description
Local Interface The name of the subinterface or port, hyperlinked to the interface in
physical inventory.
ID The tunnel identifier, hyperlinked to Pseudowires Tunnel Edges
table in logical inventory.
Peer The peer tunnel identifier, hyperlinked to the peer pseudowire
tunnel in logical inventory.
Tunnel ID The identifier that, along with the router IP addresses of the two
tunnel edges, identifies the tunnel.
Tunnel Status The operational state of the tunnel: Up or Down.
Local Router IP The IP address of this tunnel edge, which is used as the router
identifier.
Peer Router IP The IP address of the peer tunnel edge, which is used as the router
identifier.
Pseudowire Type Type of pseudowire, such as Ethernet, Ethernet Tagged, CESoPSN
Basic, PPP, or SAToP.
Local MTU The size, in bytes, of the MTU on the local interface.
Remote MTU The size, in bytes, of the MTU on the remote interface.
Local VC Label The MPLS label that is used by this router to identify or access the
tunnel. It is inserted in the MPLS label stack by the local router.
Peer VC Label The MPLS label that is used by this router to identify or access the
tunnel. It is inserted in the MPLS label stack by the peer router.
Signaling Protocol The protocol used to build the tunnel, such as LDP or TDP.
Preferred Path Tunnel The path to be used for pseudowire traffic.
Step 7 To view the properties of an Ethernet flow point associated with the pseudowire, right-click the EFP and
then choose Properties.
See Viewing EFP Properties, page 12-31 for the information that is displayed for EFPs.
Pinging a Pseudowire
Prime Network Vision enables you to ping a peer router to ensure that the pseudowire tunnel is available.
To ping a pseudowire peer router:
Step 1 In the require map, double-click the required device configured for pseudowire.
Step 2 In the inventory window, choose Logical Inventory > Pseudowires.
Step 3 In the Tunnel Edges table, select the interface with the peer edge that you want to ping, and make sure
that the tunnel status is up.
Step 4 Right-click the interface and choose Commands > Configure > Ping Pseudowire as shown in
Figure 12-57.
The Ping Pseudowire dialog box is displayed with the General tab as shown in Figure 12-58.
Step 1 In the require map, double-click the required device configured for pseudowire.
Step 2 In the inventory window, choose Logical Inventory > Pseudowire.
Step 3 In the Tunnel Edges table, right-click the required interface and choose Commands > Show > Display
Pseudowire.
Step 4 In the Display Pseudowire dialog box, do either of the following:
• To view the command before running it, click Preview.
• To run the command, click Execute.
When you click Execute, the results are displayed in the dialog box as shown in Figure 12-60.
Step 1 To determine if a pseudowire is configured for redundancy service, expand the required pseudowire in
the navigation or map pane.
If the pseudowire is configured for redundancy service, the redundancy service badge appears in the
navigation and map panes as shown in Figure 12-61.
Step 2 To view additional details, in the map, double-click the element with the redundancy service badge.
The PTP Layer 2 MPLS Tunnel Properties window is displayed as shown in Figure 12-62 and shows that
the selected pseudowire has a Secondary role in a redundancy service.
Figure 12-62 Layer 2 MPLS Tunnel Properties for Pseudowire Redundancy Service
Step 3 In the PTP Layer 2 MPLS Tunnel Properties window, click the VC ID hyperlink.
The Tunnel Edges table in logical inventory is displayed, with the local interface selected in the table.
(See Figure 12-63.)
The entries indicate that the selected tunnel edge has a Secondary role in the first VC and a Primary role
in the second VC.
For more information about the Pseudowires Tunnel Edges table, see Table 17-24 on page 17-49.
Step 1 In Prime Network Vision, choose the map in which you want to apply an overlay.
Step 2 From the toolbar, choose Choose Overlay Type > Pseudowire.
Figure 12-64 shows an example of the Select Pseudowire Overlay for map dialog box.
Step 5 To hide and view the overlay, click Hide Overlay/Show Overlay in the toolbar. The button toggles
depending on whether the overlay is currently displayed or hidden.
Step 6 To remove the overlay, choose Choose Overlay Type > None.
The available elements that meet the specified search criteria are displayed in the Add Ethernet Service
dialog box in table format. The dialog box also displays the date and time at which the list was generated.
To update the list, click Refresh.
Note If an element is not included in your scope, it is displayed with the locked device icon.
For information about sorting and filtering the table contents, see Working with Prime Network Tables,
page 2-53.
Step 4 In the Add Ethernet Service dialog box, select the elements that you want to add. You can select and add
multiple elements by pressing Ctrl while selecting individual elements or by pressing Ctrl +Shift to
select a group of elements.
Step 5 Click OK.
The Ethernet service is displayed in the navigation pane and in the content area. In addition, any
associated tickets are displayed in the ticket pane. See Figure 12-66.
The Ethernet service information is saved with the map in the Prime Network database.
Step 1 In Prime Network Vision, choose the map in which you want to apply an overlay.
Step 2 From the toolbar, choose Choose Overlay Type > Ethernet Service.
Figure 12-67 shows an example of the Select Ethernet Service Overlay for map dialog box.
Step 5 To hide and view the overlay, click Hide Overlay/Show Overlay in the toolbar. The button toggles
depending on whether the overlay is currently displayed or hidden.
Step 6 To remove the overlay, choose Choose Overlay Type > None.
Step 1 In Prime Network Vision, select the map containing the required Ethernet service.
Step 2 In the navigation or map pane, right-click the Ethernet service and choose Properties.
Figure 12-69 shows an example of an Ethernet Service Properties window with the EVC Terminating
table. Depending on the types of service in the EVC, tabs might be displayed. For example, if the EVC
contains two network VLANs and a VPLS, tabs are displayed for the following:
• EVC Terminating table
• Network VLANs
• VPLS
Table 12-40 describes the information that is displayed for an Ethernet service.
Field Description
Name Ethernet service name.
System Name Name that Prime Network Vision assigns to the Ethernet service.
EVC Name of the EVC associated with the Ethernet service, hyperlinked
to the EVC Properties window.
EVC Terminating Table
Name EVC name, represented by the interface name, EFP, and the EFP
name.
Network Element Hyperlinked entry to the specific interface and EFP in physical
inventory.
Port Hyperlinked entry to the specific interface in physical inventory.
Step 3 To view the EVC Properties window, click the hyperlink in the EVC field.
Figure 12-70 shows an example of the EVC Properties window.
Table 12-41 describes the information that is displayed in the EVC Properties window. The tabs that are
displayed depend on the services included in the EVC. For example, if the EVC contains two network
VLANs and a VPLS, tabs are displayed for the following:
• EVC Terminating table
• Network VLANs
• VPLS
Field Description
System Name Name of the system on which the EVC is configured.
Name EVC name.
Cross-Connects Table
Name Cross-connect name.
Segment 1 Identifier of the first cross-connect endpoint.
Segment 2 Identifier of the second cross-connect endpoint.
System Name Cross-connect system name.
Field Description
Network VLANs Tab
Name VLAN name.
ID VLAN identifier.
EFD Name Name of the Ethernet flow domain.
EFD System Name Name that Prime Network Vision assigns to the EFD.
System Name VLAN system name.
Description Brief description of the VLAN.
Network Pseudowires Tab
Name Pseudowire name.
System Name System on which the pseudowire is configured.
Description Brief description of the pseudowire.
Pseudowire Type Type of pseudowire.
Is Multisegment Pseudowire Whether or not the pseudowire is multisegment: True or False.
VPLS Instances Tab
Name VPLS instance name.
System Defined Name Name that Prime Network Vision assigns to the VPLS instance.
VPN ID Identifier of associated VPN.
Step 1 In Prime Network Vision, double-click the device configured for IP SLA Responder service.
Step 2 In the inventory window, choose Logical Inventory > IP SLA Responder.
IP SLA Responder properties are displayed as shown in Figure 12-71.
Table 12-42 describes the properties displayed for IP SLA Responder service.
Field Description
IP SLA Responder Status Status of the IP SLA Responder: Up or Down.
IP SLA TWAMP Responder Status of the IP SLA TWAMP responder: Up or Down.
Status
UDP Echo Tab
IP Address Destination IP address used for the UDP echo operation.
Port Number Destination port number used for the UDP echo operation.
TCP Connect Tab
IP Address Destination IP address used for the TCP connect operation.
Port Number Destination port number used for the TCP connect operation.
Step 1 In Prime Network Vision, double-click the device configured for IS-IS.
Step 2 In the inventory window, choose Logical Inventory > IS-IS > System.
Figure 12-72 shows an example of the IS-IS window with the Process table in logical inventory.
Table 12-43 describes the information that is displayed in this window and the Processes table.
Field Description
Version Version of IS-IS that is implemented.
Processes Table
Process ID Identifier for the IS-IS process.
System ID Identifier for this Intermediate System.
IS Type Level at which the Intermediate System is running: Level 1, Level
2, or Level 1-2.
Manual Area Address Address assigned to the area.
Step 3 To view IS-IS process information, choose Logical Inventory > IS-IS > Process nnn.
Figure 12-73 shows an example of the information that is displayed for the IS-IS process.
Table 12-44 describes the information that is displayed for the selected IS-IS process.
Field Description
Process Unique identifier for the IS-IS process.
System ID Identifier for this Intermediate System.
IS Type Level at which the Intermediate System process is running: Level 1,
Level 2, or Level 1-2.
Manual Area Address Address assigned to the area.
Metrics Tab
IS Type Level at which the Intermediate System is running: Level 1, Level
2, or Level 1-2.
Metric Style Metric style used: Narrow, Transient, or Wide.
Metric Value Metric value assigned to the link. This value is used to calculate the
path cost via the links to destinations. This value is available for
Level 1 or Level 2 routing only.
If the metric style is Wide, the value can range from 1 to 16777214.
If the metric style is Narrow, the value can range from 1 to 63.
The default value for active IS-IS interfaces is 10, and the default
value for inactive IS-IS interfaces is 0.
Address Family IP address type used: IPv4 or IPv6.
Interfaces Tab
Interface Name Interface name.
Neighbors Tab
System ID Identifier for the neighbor system.
Interface Neighbor interface name.
IP Address Neighbor IP address.
Type IS type for the neighbor: Level 1, Level 2, or Level 1-2.
SNPA Subnetwork point of attachment (SNPA) for the neighbor.
Hold Time Holding time, in seconds, for this adjacency. The value is based on
received IS-to-IS Hello (IIH) PDUs and the elapsed time since
receipt.
State Administrative status of the neighbor system: Up or Down.
Address Family IP address type used by the neighbor: IPv4 or IPv6.
Step 1 In Prime Network Vision, double-click the device configured for OSPF.
Step 2 To view OSPF processes, choose Logical Inventory > OSPF Processes > OSPF Process (vn) ID where
vn represents the OSPF version and ID is the OSPF process identifier.
For example, in Figure 12-74, the entry in the navigation tree is OSPF Process (v2) 10.
Table 12-45 describes the information that is displayed for OSPF processes.
Field Description
OSPF Process Details
Process ID Unique process identifier.
Router ID Router IP address.
OSPF Version OSPF version: v1, v2, or v3.
SPF Timers
Schedule Delay Number of milliseconds to wait after a change before calculating the shortest path first (SPF).
Min Hold Time Minimum number of milliseconds to wait between two consecutive SPF calculations.
Max Wait Time Maximum number of milliseconds to wait between two consecutive SPF calculations.
OSPF Neighbors Table
Neighbor ID OSPF neighbor IP address.
Area OSPF area identifier.
Interface Address IP address of the interface on the neighbor configured for OSPF.
State State of the communication with the neighbor: Down, Attempt, Init, 2-Way, Exstart, Exchange,
Loading, and Full.
OSPF Interface Hyperlinked entry to the OSPF Interface Properties window.
The OSPF Interfaces window displays the same information as the OSPF Interfaces Table below.
OSPF Interfaces Table
IP Interface OSPF interface, hyperlinked to the relevant entry in the routing entity IP Interfaces table in logical
inventory.
For more information about the IP Interfaces table, see Table 17-11.
Internet Address OSPF interface IP address.
Area ID OSPF area identifier.
Priority Eight-bit unsigned integer that specifies the priority of the interface. Values range from 0 to 255. Of
two routers, the one with the higher priority takes precedence.
Cost Specified cost of sending a packet on the interface, expressed as a metric. Values range from 1 to
65535.
Status State of the interface: Up or Down.
State OSPF state: BDR, DR, DR-Other, Waiting, Point-to-Point, or Point-to-Multipoint.
Network Type Type of OSPF network: Broadcast, Nonbroadcast Multiple Access (NBMA), Point-to-Multipoint,
Point-to-Point, or Loopback.
DR Address Designated router IP address.
BDR Address Backup designated router IP address.
Note IPv4 Network Address Translation (NAT44) is not supported for devices running Cisco IOS XR
software version 4.0.
The following topics describe using Prime Network Vision to view Carrier Grade NAT properties:
• User Roles Required to View Carrier Grade NAT Properties, page 13-1
• Viewing Carrier Grade NAT Properties in Logical Inventory, page 13-2
• Viewing Carrier Grade NAT Properties in Physical Inventory, page 13-5
By default, users with the Administrator role have access to all managed elements. To change the
Administrator user scope, see the topic on device scopes in the Cisco Prime Network 3.8 Administrator
Guide.
Table 13-1 Default Permission/Security Level Required for Viewing Carrier Grade NAT Properties
- Element Not in User’s Scope
Table 13-2 Default Permission/Security Level Required for Viewing Carrier Grade NAT Properties
- Element in User’s Scope
Step 1 In Prime Network Vision, double-click the Cisco CRS device configured for Carrier Grade NAT.
Step 2 In the inventory window, click Logical Inventory > Carrier Grade NAT.
The Carrier Grade NAT properties are displayed in logical inventory as shown in Figure 13-1.
Table 13-3 describes the Carrier Grade NAT properties that are displayed.
Field Description
CGN Name Name of the Carrier Grade NAT service.
Preferred Location Tab
Preferred Location Hyperlinked entry to the card in physical inventory.
Preferred Location (alias) Location of module in clear text.
Location Type Configured type of location: Active or Standby.
Redundancy Status Redundancy state: Online or Offline.
If the field is empty, it means the data was not collected from the
device.
Service Infra Interface Hyperlinked entry to the routing entity in logical inventory.
For more information about routing entities in logical inventory, see
Viewing Routing Entities, page 17-32.
Field Description
Address Pools Tab
Inside VRF Hyperlinked entry to the inside VRF in logical inventory.
For more information about VRF properties in logical inventory,
see Viewing VRF Properties, page 17-28.
Address Family Type of IP address in this pool: IPv4 or IPv6.
Outside VRF Hyperlinked entry to the outside VRF in logical inventory.
For more information about VRF properties in logical inventory,
see Viewing VRF Properties, page 17-28.
Address Pool Range of IP addresses that can be used for the service instance. If
an end address is not specified, the entire range of 255 addresses is
used for the address pool.
Associated Interfaces Tab
Interface Hyperlinked entry to the associated entry in logical inventory:
• For SVI service interfaces, hyperlinked entry to the routing
entity in logical inventory.
• For SVI service applications, hyperlinked entry to the VRF
entity in logical inventory.
Service Types Tab
Service Type Name Name of the Carrier Grade NAT service.
Service Type Type of Carrier Grade NAT service: 6RD, XLAT, or NAT44.
Statistics Tab
Statistics Name Name of the statistic.
For statistic names and descriptions, see Table 13-4.
Statistics Value Value of the statistic.
Step 1 In Prime Network Vision, double-click the Cisco CRS device configured for Carrier Grade NAT.
Step 2 To view Carrier Grade NAT properties configured on a specific interface, click Physical Inventory >
chassis > shelf > slot > card > interface. See Table 3-10 for a description of the information displayed
in the Subinterfaces table.
Step 3 To view Carrier Grade NAT properties configured on a Cisco CRS-CGSE-PLIM card, click Physical
Inventory > chassis > shelf > slot > PLIM-card.
Figure 13-2 shows an example of Carrier Grade NAT properties in physical inventory.
The field CGN Service is displayed, and the entry is hyperlinked to the associated Carrier Grade NAT
service in logical inventory.
The following topics describe how you can view and monitor IP over dense wavelength division
multiplexing (DWDM) properties configured on network elements by using Cisco Prime Network
Vision (Prime Network Vision):
• User Roles Required to View DWDM Properties, page 14-1
• Viewing DWDM in Physical Inventory, page 14-2
• Viewing G.709 Properties, page 14-4
• Viewing Performance Monitoring Configuration, page 14-10
Table 14-1 Default Permission/Security Level Required for Viewing DWDM Properties - Element
Not in User’s Scope
Table 14-2 Default Permission/Security Level Required for Viewing DWDM Properties - Element
in User’s Scope
Step 1 In a Prime Network Vision map, double-click the device on which DWDM is configured.
Step 2 In the inventory window, choose Physical Inventory > Chassis and navigate to the interface configured
for DWDM. DWDM details are displayed in the DWDM area in the content pane as shown in
Figure 14-1.
Field Description
Location Physical interface using the format rack/slot/module/port where:
• rack is the chassis number of the rack.
• slot is the physical slot number of the line card.
• module is the module number. A physical layer interface module
(PLIM) is always 0. Shared port adapters (SPAs) are referenced by
their subslot number.
• port is the physical port number of the interface.
Controller Status Status of the controller: Up or Down.
Loopback Whether or not the DWDM controller is configured for loopback mode.
Frequency Frequency of the channel in terahertz.
Port Type The port type. In this case, DWDM.
MSA ITU Channel Multi Source Agreement (MSA) ITU channel number.
Rx Power Actual optical power at the receiving port.
Tx Power Value of the transmit power level.
Field Description
Rx LOS Threshold Number of optical channel transport unit (OTU) loss of signal (LOS)
alarms. If the receive optical power is less than or equal to this defined
threshold, the optical LOS alarm is raised.
Wavelength Wavelength corresponding to the channel number in nanometers.
Wavelength Band Indicates the wavelength band: C-band or L-band.
Optics Type Indicates the optics type: GE or DWDM.
G709 Properties
G709 Status Whether the G.709 wrapper is enabled or disabled: Up or Down.
OTU Detected Alarms OTU overhead alarms.
ODU Detected Alarms Optical channel data unit (ODU) alarms.
OTU Detected Alerts OTU alerts.
ODU Detected Alerts ODU alerts.
FEC Info Indicates the:
• FEC mode of the controller: Disabled, Enhanced, Standard, or
Unknown.
• FEC mode on the remote device: Disabled, Enhanced, Standard, or
Unknown.
• Number of sync word mismatches found during the tracking phase.
G709 Details Click to view G709 properties. For more information, see Viewing
G.709 Properties, page 14-4.
PM 15-min Settings Click to view 15-minute performance monitoring properties. For more
information, see Viewing Performance Monitoring Configuration,
page 14-10.
PM 24-hour Settings Click to view 24-hour performance monitoring properties. For more
information, see Viewing Performance Monitoring Configuration,
page 14-10.
Step 1 In Prime Network Vision, double-click the device on which DWDM is configured.
Step 2 In the inventory window, choose Physical Inventory > Chassis and navigate to the interface configured
for DWDM.
Step 3 In the content pane, click G709 Details.
The G709 Info Properties window is displayed as shown in Figure 14-2 for all Cisco devices except the
Cisco 7600 series devices.
Figure 14-3 shows the tabs that are displayed in the G709 Info Properties window for Cisco 7600 series
devices. For Cisco 7600 series devices:
• The ODU Alert Counters tab is displayed.
• The ODU TTI and OTU TTI tabs are not displayed.
Figure 14-3 DWDM G709 Properties Window for Cisco 7600 Series Devices
Table 14-4 describes the fields that are displayed above the tabs in the G709 Info Properties window.
Field Description
Location Physical interface using the format rack/slot/module/port where:
• rack is the chassis number of the rack.
• slot is the physical slot number of the line card.
• module is the module number. A physical layer interface module
(PLIM) is always 0. Shared port adapters (SPAs) are referenced by
their subslot number.
• port is the physical port number of the interface.
OTU Alarms
OTU Alarm Reporting The types of alarms enabled for reporting:
Enabled for
• AIS—Alarm indication signal (AIS) alarms.
• BDI—Backward defect indication (BDI) alarms.
• BEI—Backward error indication (BEI) alarms.
• BIP—Bit interleaved parity (BIP) alarms.
• FECMISMATCH—FEC mismatch alarms.
• IAE—Incoming alignment error (IAE) alarms.
• LOF—Loss of frame (LOF) alarms.
• LOM—Loss of multiple frames (LOM) alarms.
• LOS—Loss of signal (LOS) alarms.
• TIM—Type identifier mismatch (TIM) alarms.
OTU Asserted Alarms OTU alarms indicated to be reported by the user.
OTU Detected Alarms OTU alarms detected by the hardware.
ODU Alarms
ODU Alarm Reporting The types of ODU alarms enabled for reporting:
Enabled for
• AIS—Incoming SONET AIS error status.
• BDI—Path termination BDI error status.
• BEI—Backward error indication (BEI) error status.
• BIP—Bit interleaved parity (BIP) error status.
• LCK—Upstream connection locked (LCK) error status.
• OCI—Open connection indication (OCI) error status.
• PTIM—Payload TIM error status.
• TIM—Data stream TIM error status.
ODU Asserted Alarms ODU alarms indicated to be reported by the user.
ODU Detected Alarms ODU alarms detected by the hardware.
Field Description
OTU Alerts
OTU Alert Reporting The types of alerts enabled for reporting:
Enabled for • SD-BER—Section Monitoring (SM) bit error rate (BER) is in
excess of the signal degradation (SD) BER threshold.
• SF-BER—SM BER is in excess of the signal failure (SF) BER
threshold.
• PM-TCA—Performance monitoring (PM) threshold crossing alert
(TCA).
• SM-TCA—SM threshold crossing alert.
OTU Asserted Alerts OTU alerts indicated to be reported by the user.
OTU Detected Alerts OTU alerts detected by the hardware.
ODU Alerts
ODU Alert Reporting The types of ODU alerts enabled for reporting:
Enabled for
• SD-BER—SM BER is in excess of the SD BER threshold.
• SF-BER—SM BER is in excess of the SF BER threshold.
• PM-TCA—PM threshold crossing alert.
• SM-TCA—SM threshold crossing alert.
ODU Asserted Alerts ODU alerts indicated to be reported by the user.
ODU Detected Alerts ODU alerts detected by the hardware.
Other
FEC Info FEC properties:
• FEC mode for the controller—Disable, Enhanced, Standard, or
Unknown.
• Remote FEC mode—FEC mode on the remote device: Disabled,
Enhanced, Standard, or Unknown.
• FEC mismatch counter—Number of sync word mismatches found
during the tracking phase.
Status G.709 wrapper administrative status: Up or Down.
The G709 Info Properties window contains the following tabs, depending on the selected network
element:
• OTU Alarm Counters Tab, page 14-9
• OTU Alert Counters Tab, page 14-9
• ODU Alarm Counters Tab, page 14-9
• OTU TTI Tab, page 14-9
• ODU TTI Tab, page 14-9
• ODU Alert Counters Tab, page 14-10
Step 4 To view additional G.709 properties, click the required tab. Table 14-5 describes the information
displayed in each tab.
Field Description
OTU Alarm Counters Tab
Type Type of OTU alarm, such as BDI or BEI.
Counter Number of alarms reported for each alarm type.
OTU Alert Counters Tab
Type Type of OTU alert, such as SD-BER or SF-BER.
Threshold Threshold set for the type of alert.
Counter Number of alerts reported for each alert type. A value of -1 indicates that
no value has been set up.
ODU Alarm Counters Tab
Type Type of ODU alarm, such as AIS or BDI.
Counter Number of alarms reported for each alarm type.
OTU TTI Tab
This tab is not displayed for Cisco 7600 series devices.
Type Type of OTU Trail Trace Identifier (TTI) configured:
• Expected
• Received
• Sent
String Type For each TTI type, the type of string:
• ASCII
• Hexadecimal
TTI String For each TTI type, the specific TTI string configured.
ODU TTI Tab
This tab is not displayed for Cisco 7600 series devices.
Type Type of ODU TTI configured:
• Expected
• Received
• Sent
String Type For each TTI type, the type of string:
• ASCII
• Hexadecimal
TTI String For each TTI type, the specific TTI string configured.
Field Description
ODU Alert Counters Tab
This tab is displayed only for Cisco 7600 series devices.
Type Type of OTU alert, such as SD-BER or SF-BER.
Threshold Threshold set for the type of alert.
Counter Number of alerts reported for each alert type. A value of -1 indicates that
no value has been set up.
Step 5 To close the G709 Info Properties window, click the upper right corner.
Step 1 In Prime Network Vision, double-click the device on which DWDM is configured.
Step 2 In the inventory window, choose Physical Inventory > Chassis and navigate to the interface configured
for DWDM.
Step 3 In the content pane, select the performance monitoring configuration settings you want to view:
• To view the performance monitoring 15-minute configuration settings, click PM 15-min Settings.
• To view the performance monitoring 24-hour configuration settings, click PM 24-hour Settings.
The Client DWDM PM Settings Properties window is displayed as shown in Figure 14-4.
Table 14-6 describes the information displayed above the tabs in the Client DWDM PM Settings
Properties window and in each of the tabs.
Field Description
Interval Type The performance monitoring interval, either 15 minutes or 24 hours.
Location Physical interface using the format rack/slot/module/port where:
• rack is the chassis number of the rack.
• slot is the physical slot number of the line card.
• module is the module number. A physical layer interface module (PLIM) is always 0. Shared
port adapters (SPAs) are referenced by their subslot number.
• port is the physical port number of the interface.
FEC PM Settings Tab
Type FEC performance monitoring parameter being tracked:
• EC-BITS—The number of bit errors corrected (EC-BITS) in the DWDM trunk line during the
performance monitoring time interval.
• UC-WORDS—The number of uncorrectable words (UC-WORDS) detected in the DWDM
trunk line during the performance monitoring time interval.
Threshold Threshold for the performance monitoring parameter.
TCA Whether TCA generation for the specified parameter on the DWDM controller is enabled or
disabled.
Optics PM Settings Tab
Type Optics performance monitoring parameter being tracked:
• LBC—Laser bias current.
• OPR—Optical power on the unidirectional port.
• OPT—Transmit optical power in dBm.
Max Threshold Maximum threshold configured for the parameter.
Max TCA If enabled, indicates a TCA is generated if the value of the parameter exceeds the maximum
threshold during the performance monitoring period. If disabled, TCAs are not generated if the
maximum threshold is exceeded.
Min Threshold Minimum threshold configured for the parameter.
Min TCA If enabled, indicates a TCA is generated if the value of the parameter drops below the minimum
threshold during the performance monitoring period. If disabled, TCAs are not generated if the
value drops below the minimum threshold.
Table 14-6 Client DWDM PM Settings Properties Window and Tabs (continued)
Field Description
OTN PM Settings Tab
Type OTN performance monitoring parameter being tracked:
• bbe-pm-fe—Far-end path monitoring background block errors (BBE-PM). Indicates the
number of background block errors recorded in the optical transport network (OTN) path
during the performance monitoring time interval.
• bbe-pm-ne—Near-end path monitoring background block errors (BBE-PM).
• bbe-sm-fe—Far-end section monitoring background block errors (BBE-SM). Indicates the
number of background block errors recorded in the OTN section during the performance
monitoring time interval.
• bbe-sm-ne—Near-end section monitoring background block errors (BBE-SM).
• bber-pm-fe—Far-end path monitoring background block errors ratio (BBER-PM). Indicates
the background block errors ratio recorded in the OTN path during the performance
monitoring time interval.
• bber-pm-ne—Near-end path monitoring background block errors ratio (BBER-PM).
• bber-sm-fe—Far-end section monitoring background block errors ratio (BBER-SM).
Indicates the background block errors ratio recorded in the OTN section during the
performance monitoring time interval.
• bber-sm-ne—Near-end section monitoring background block errors ratio (BBER-SM)
• es-pm-fe—Far-end path monitoring errored seconds (ES-PM). Indicates the errored seconds
recorded in the OTN path during the performance monitoring time interval.
• es-pm-ne—Near-end path monitoring errored seconds (ES-PM).
• es-sm-fe—Far-end section monitoring errored seconds (ES-SM). Indicates the errored
seconds recorded in the OTN section during the performance monitoring time interval.
• es-sm-ne—Near-end section monitoring errored seconds (ES-SM).
• esr-pm-fe—Far-end path monitoring errored seconds ratio (ESR-PM). Indicates the errored
seconds ratio recorded in the OTN path during the performance monitoring time interval.
• esr-pm-ne—Near-end path monitoring errored seconds ratio (ESR-PM).
• esr-sm-fe—Far-end section monitoring errored seconds ratio (ESR-SM). Indicates the errored
seconds ratio recorded in the OTN section during the performance monitoring time interval.
• esr-sm-ne—Near-end section monitoring errored seconds ratio (ESR-SM).
• fc-pm-fe—Far-end path monitoring failure counts (FC-PM). Indicates the failure counts
recorded in the OTN path during the performance monitoring time interval.
• fc-pm-ne—Near-end path monitoring failure counts (FC-PM).
• fc-sm-fe—Far-end section monitoring failure counts (FC-SM). Indicates the failure counts
recorded in the OTN section during the performance monitoring time interval.
• fc-sm-ne—Near-end section monitoring failure counts (FC-SM).
Table 14-6 Client DWDM PM Settings Properties Window and Tabs (continued)
Field Description
Type (cont.) • ses-pm-fe—Far-end path monitoring severely errored seconds (SES-PM). Indicates the
severely errored seconds recorded in the OTN path during the performance monitoring time
interval.
• ses-pm-ne—Far-end path monitoring severely errored seconds (SES-PM).
• ses-sm-fe—Far-end section monitoring severely errored seconds (SES-SM). Indicates the
severely errored seconds recorded in the OTN section during the performance monitoring time
interval.
• ses-sm-ne—Near-end section monitoring severely errored seconds (SES-SM).
• sesr-pm-fe—Far-end path monitoring severely errored seconds ratio (SESR-PM). Indicates
the severely errored seconds ratio recorded in the OTN path during the performance
monitoring time interval.
• sesr-pm-ne—Near-end path monitoring severely errored seconds ratio (SESR-PM).
• sesr-sm-fe—Far-end section monitoring severely errored seconds ratio (SESR-SM). Indicates
the severely errored seconds ratio recorded in the OTN section during the performance
monitoring time interval.
• sesr-sm-ne—Near-end section monitoring severely errored seconds ratio (SESR-SM).
• uas-pm-fe—Far-end path monitoring unavailable seconds (UAS-PM). Indicates the
unavailable seconds recorded in the OTN path during the performance monitoring time
interval.
• uas-pm-ne—Near-end path monitoring unavailable seconds (UAS-PM).
• uas-sm-fe—Far-end section monitoring unavailable seconds (UAS-SM). Indicates the
unavailable seconds recorded in the OTN section during the performance monitoring time
interval.
• uas-sm-ne—Near-end section monitoring unavailable seconds (UAS-SM).
Threshold Threshold configured for the parameter.
TCA If enabled, indicates a TCA is generated if the value of the parameter crosses the threshold during
the performance monitoring period. If disabled, TCAs are not generated if the value crosses the
threshold.
The following topics describe how you can use Cisco Prime Network Vision (Prime Network Vision) to
monitor Ethernet operations, administration, and maintenance (OAM) tools:
• User Roles Required to View Ethernet OAM Tool Properties, page 15-1
• Ethernet OAM Overview, page 15-2
• Viewing Connectivity Fault Management Properties, page 15-3
• Viewing Ethernet LMI Properties, page 15-9
• Viewing Link OAM Properties, page 15-13
Table 15-1 Default Permission/Security Level Required for Viewing Ethernet OAM Tool
Properties - Element Not in User’s Scope
Table 15-2 Default Permission/Security Level Required for Viewing Ethernet OAM Tool
Properties - Element in User’s Scope
Note Prime Network Vision does not display information for CFM maintenance endpoints or maintenance
intermediate points for Cisco Viking devices if errors exist in their configurations. An error in the
configuration is indicated by an exclamation point (!) in the CLI output.
For example, if you enter the command show ethernet cfm local maintenance-points , a
configuration error is indicated as follows:
Step 1 In Prime Network Vision, double-click the required device for CFM.
Step 2 In the inventory window, choose Logical Inventory > CFM.
Figure 15-1 shows an example of CFM in logical inventory.
Field Description
Cache Size CFM traceroute cache size in number of lines.
Hold Time Configured hold time (in minutes) that is used to indicate to the receiver
the validity of traceroute and loopback messages transmitted by the
device. The default value is 2.5 times the transmit interval.
Maximum Cache Size Maximum CFM traceroute cache size in number of lines.
CFM Version CFM version, such as IEEE D8.1.
Maintenance Domains Table
Name Domain name.
Level Unique level the domain is managed on. Values range from 0 to 7.
ID Optional domain identifier.
Step 3 Click the Maintenance Intermediate Points tab to view MIP information. See Figure 15-2.
Table 15-4 describes the information that is displayed in the Maintenance Intermediate Points table.
Field Description
Interface Interface configured as a MIP, hyperlinked to its entry in physical
inventory.
MAC Address MAC address of the interface.
Inner VLANs Inner VLAN identifiers.
VLANs VLANs associated with the interface.
Auto Created Whether or not the MIP was automatically created: True or False.
Level Unique level the domain is managed on. Values range from 0 to 7.
Step 4 To view the details of a specific maintenance domain, do one of the following:
• Choose Logical Inventory > CFM > domain.
• Double-click the required entry in the Maintenance Domains table.
Figure 15-3 shows an example of the information displayed for the maintenance domain.
Table 15-5 describes the information that is displayed for CFM maintenance domains.
Field Description
Maintenance Domain Name Name of the domain.
Level Level at which the domain is managed: 0-7.
ID Optional maintenance domain identifier.
Maintenance Associations Table
Name Name of the maintenance association.
Association Type Maintenance association type.
Direction Direction of the maintenance association: Up or Down.
Continuity Check Whether or not the continuity check is enabled: True or False.
Continuity Check Interval Interval (in seconds) for checking continuity.
Associated Entity Bridge, port, or pseudowire that the maintenance association uses
for CFM. Click the hyperlinked entry to view the item in inventory.
Cross Check Whether or not cross checking is enabled: True or False.
Maximum MEPs Maximum number of maintenance endpoints (MEPs) that can be
configured on the maintenance association.
Inner VLAN Inner VLAN identifier.
Step 5 To view the properties for a maintenance association’s endpoints, do one of the following:
• Choose Logical Inventory > CFM > domain > association.
• In the Maintenance Associations table, double-click the required association.
Figure 15-4 shows the information displayed for the maintenance association endpoints.
Table 15-6 describes the information that is displayed for CFM maintenance associations and MIPs.
Field Description
Maintenance Association Name Name of the maintenance association.
Association Type Maintenance association type, such as Bridge Domain.
Direction Direction of the maintenance association: Up or Down.
Continuity Check Whether or not the continuity check is enabled: True or False.
Continuity Check Interval Interval (in seconds) for checking continuity.
Cross Check Whether or not cross checking is enabled: True or False.
Associated Entity Bridge that the maintenance association uses for CFM. Click the
hyperlinked entry to view the bridge in logical inventory.
Maximum MEPs Maximum number of MEPs that can be configured on the
maintenance association.
Inner VLANs Inner VLAN identifiers.
Field Description
Maintenance End Points Table
ID Local identifier for the MEP.
MAC Address MAC address that identifies the MEP.
Interface Interface on which the MEP is configured, hyperlinked to the
respective EFP, VSI or interface in inventory.
Continuity Check Status CFM continuity check status: MEP Active, MEP Inactive, MEP
Enabled, MEP Disabled, or Unknown.
Direction Direction of traffic on which the MEP is defined: Up, Down, or
Unknown.
Step 6 Click the Remote Maintenance End Points tab to view the information displayed for remote MEPs.
See Figure 15-5.
Field Description
MEP ID Remote MEP identifier.
Level Level at which the remote MEP is managed: 0-7.
Status Status of the remote MEP, such as MEP Active.
MAC Address MAC address of the remote MEP.
Local MEP ID Numeric identifier assigned to the local MEP. Values range from 1 to
8191.
Note If the remote MEP is in Up mode, the remote MEP is not
associated to the local MEP. As a result, the Local MEP ID
column is empty.
Step 1 In Prime Network Vision, double-click the device configured for Ethernet LMI.
Step 2 In the inventory window, choose Logical Inventory > Ethernet LMI.
Figure 15-6 shows an example of Ethernet LMI properties in logical inventory.
Field Description
Globally Enabled Whether or not Ethernet LMI is enabled globally: True or False.
Mode Ethernet LMI mode: CE or PE.
Device EVCs Tab
EVC Name Name of the EVC.
EVC Type Type of EVC: Point-to-point or Multipoint.
EVC Status EVC status: Active, Inactive, Not Defined, or Partially Active.
Maintenance Association Hyperlinked entry to the maintenance association in CFM in logical
inventory. For more information about maintenance associations, see
Table 15-6.
Active Remote UNI Count Number of active remote UNIs.
Configured Remote UNI Number of configured remote UNIs.
Count
Field Description
ELMI Interfaces Tab
Interface Name Hyperlinked entry to the interface in physical inventory. For more
information, see Step 4 in this procedure.
T391 Frequency at which the customer equipment sends status inquiries. The
range is 5-30 seconds, with a default of 10 seconds.
T392 Frequency at which the metro Ethernet network verifies that status
enquiries have been received. The range is 5-30 seconds, with a default
of 15 seconds. A value of 0 (zero) indicates the timer is disabled.
N391 Frequency at which the customer equipment polls the status of the UNI
and all EVCs. The range is 1-65000 seconds, with a default of 360
seconds.
N393 Error count for the metro Ethernet network. The range is 1-10, with a
default of 4.
Step 3 To view device EVC properties, double-click an EVC name in the Device EVCs tab.
The Device EVC Properties window is displayed as shown in Figure 15-7.
Table 15-9 describes the information displayed in the Device EVC Properties window.
Field Description
EVC Name Name of the EVC.
EVC Type Type of EVC: Point-to-point or Multipoint.
EVC Status EVC status: Active, Inactive, Not Defined, or Partially Active.
Maintenance Association Hyperlinked entry to the maintenance association in CFM in logical
inventory. For more information about maintenance associations, see
Table 15-6.
Active Remote UNI Count Number of active remote UNIs.
Configured Remote UNI Number of configured remote UNIs.
Count
UNI Interfaces Table
UNI Id UNI identifier.
UNI Status Status of the UNI: Up or Down.
LMI Link Status Status of the LMI link: Up or Down.
Interface Name Interface on which UNI is configured.
Is UNI Local Whether or not UNI is local: True or False.
Local Interface Hyperlinked entry to the interface in physical inventory.
VLAN List Name of the VLAN associated with the UNI interface.
Step 4 To view properties for an Ethernet LMI interface in physical interface, click the required interface name
in the ELMI Interfaces table.
Table 15-10 describes the information displayed in the UNI Properties area in physical inventory.
Field Description
Service Multiplexing Enabled Whether or not the interface is configured for UNI
multiplexing: True or False.
Bundling Enabled Whether or not the interface is configured for UNI bundling:
True or False.
UNI Id UNI identifier.
Bundling Type Type of bundling applied: All-to-One or None.
This field appears only when a bundling type is set.
Step 1 In Prime Network Vision, double-click the device configured for Link OAM.
Step 2 In the inventory window, choose Logical Inventory > OAM.
Field Description
Table Types Type of table. In this case, it is OAM.
OAM Table
Local Port Name of the OAM-supported interface, hyperlinked to the location
in physical inventory.
Local Port ID Local port identifier, such as FastEthernet1/0/9.
Admin Status Administrative status of the interface.
Port Status Status of the port.
Remote MAC Address Remote client MAC address.
Step 3 To view detailed information about an entry in the table, double-click the required entry.
The Link OAM Data Properties window is displayed as shown in Figure 15-9.
Table 15-12 describes the information that is displayed in the Link OAM Data Properties window.
Field Description
Local Interface
Local Port Name of the OAM-supported interface, hyperlinked to the location
in physical inventory.
Local Port ID Local port identifier.
Admin Status Administrative status of the interface: Up or Down.
Port Status Status of the port, such as Operational.
PDU Max Rate (Frames/sec) Maximum transmission rate measured by the number of OAM
PDUs per second; for example, 10 packets per second.
PDU Min Rate Minimum transmission rated measured by the number of seconds
(Seconds/frame) required for one OAM PDU; for example, 1 packet per 2 seconds.
Link Timeout Number of seconds of inactivity on a link before the link is dropped.
High Threshold Action Action that occurs when the high threshold for an error is exceeded.
Link Fault Action Action that occurs when the signal is lost.
Field Description
Dying Gasp Action Action that occurs when an unrecoverable condition is encountered.
Critical Event Action Action that occurs when an unspecified vendor-specific critical
event occurs.
Mode Mode of the interface: Active or Passive.
Unidirection Status of unidirectional Ethernet on the local interface: Supported
or Not supported.
Link Monitor Status of link monitoring on the local interface: Supported or Not
supported.
Remote Loopback Status of remote loopback on the local interface: Supported or Not
supported.
Loopback Status Status of loopback on the local interface: Supported or No
loopback.
Remote Client
MAC Address MAC address for the remote client.
Vendor Vendor of the remote client.
Mode Mode of the remote client: Active or Passive.
Unidirection Status of unidirectional Ethernet on the remote client interface:
Supported or Not supported.
Link Monitor Status of link monitoring on the remote client interface: Supported
or Not supported.
Remote Loopback Status of loopback on the remote client interface: Supported or Not
supported.
Step 4 To view Link OAM status in physical inventory, choose Physical Inventory > chassis > slot > interface.
The Link OAM administrative status is displayed as shown in Figure 15-10.
Table 16-1 Default Permission/Security Level Required for Viewing IPv6 Properties - Element Not
in User’s Scope
Table 16-2 Default Permission/Security Level Required for Viewing IPv6 Properties - Element in
User’s Scope
The IP addresses that appear depend on whether the interface has only IPv4 addresses, only IPv6
addresses, or both IPv4 and IPv6 addresses, as shown in Table 16-4.
Table 16-4 IP Addresses Displayed in the Interface Table and Properties Window
Note Interfaces or subinterfaces that do not have IP addresses are not discovered and therefore are not shown
in Prime Network Vision.
Figure 16-1 shows a port inventory view of a port with IPv4 and IPv6 addresses. In this example, one
IPv4 address and multiple IPv6 addresses are provisioned on the interface.
• The primary IPv4 address appears in the interface table and properties window. If secondary IPv4
addresses were provisioned on the interface, they would appear in the properties window.
• IPv6 addresses provisioned on the interface appear in the properties window and Sub Interfaces tab.
Figure 16-2 shows a port with only IPv6 addresses provisioned. In this example, the lowest IPv6 address
is shown in the subinterface table, and all IPv6 addresses are shown in the interface properties window.
The following topics describe how to view and manage aspects of Multiprotocol Label Switching
(MPLS) services using Cisco Prime Network Vision (Prime Network Vision), including the MPLS
service view, business configuration, and maps. The topics also describe the device inventory specific
to MPLS VPNs, including routing entities, label switched entities (LSEs), BGP neighbors,
Multiprotocol BGP (MP-BGP), VRF instances, pseudowires, and TE tunnels. Topics include:
• User Roles Required to Work with MPLS Networks, page 17-1
• Working with MPLS-TP Tunnels, page 17-4
• Viewing VPNs, page 17-19
• Managing VPNs, page 17-22
• Working with VPN Overlays, page 17-25
• Monitoring MPLS Services, page 17-27
Table 17-1 Default Permission/Security Level Required for Working with MPLS Networks -
Element Not in User’s Scope
Table 17-2 Default Permission/Security Level Required for Working with MPLS Networks -
Element in User’s Scope
Step 1 In Prime Network Vision, display the map to which you want to add the MPLS-TP tunnel.
Step 2 Do either of the following:
• From the File menu, choose Add to Map > MPLS-TP Tunnel.
• In the main toolbar, click Add to Map, then choose Add to Map > MPLS-TP Tunnel.
The Add MPLS-TP Tunnel dialog box is displayed.
Step 3 Do either of the following:
• Choose a search category, enter a search string, then click Go to narrow search results to a range of
MPLS-TP tunnels or a specific MPLS-TP tunnel. Search categories include:
– Description
– Name
– System Name
• Choose Show All to display all the MPLS-TP tunnels.
Step 4 Select the MPLS-TP tunnel that you want to add to the map.
Step 5 Click OK.
The MPLS-TP tunnel is added to the map and to the navigation pane.
In Figure 17-1:
• The devices are on the left side of the map, and the MPLS-TP tunnel is displayed in a thumbnail on
the right.
• The devices are connected to each other and to the MPLS-TP tunnel via tunnels.
• Physical links connect the devices to the Working and Protected LSPs.
• A redundancy service badge is displayed next to the Protected LSP in the navigation and map panes.
• In the thumbnail:
– The tunnel endpoints are connected to each other via a tunnel.
– A physical link connects the Working and Protected LSPs.
– Business links connect the Working and Protected LSPs to each endpoint.
If an LSP is configured for redundancy service, a redundancy service badge is applied to the secondary
(backup) LSP in the navigation and map panes in the navigation and map panes.
For more information about LSP redundancy service, see Viewing LSP Endpoint Redundancy Service
Properties, page 17-14.
Step 1 Right-click the required device in Prime Network Vision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > MPLS-TP > MPLS-TP Global.
The routing information is displayed as shown in Figure 17-3.
Table 17-3 describes the information that is available for MPLS-TP tunnels. The information that is
displayed depends on the configuration.
Field Description
Global ID Globally unique Attachment Interface Identifier (AII) for MPLS-TP derived
from the Autonomous System Number (ASN) of the system hosting the PEs.
Router ID MPLS-TP source node identifier for this element in the form of an IPv4
address.
Protection Mode Whether the transmitting endpoint is in revertive or nonrevertive mode:
• Revertive—If the protection mode is revertive and a failed path is
restored, the traffic automatically returns, or reverts, to the original path.
• Nonrevertive—If the protection mode is nonrevertive and a failed path
is restored, the traffic does not return to the original path. That is, the
traffic does not revert to the original path.
Redundancy Mode Level of redundancy for the MPLS-TP tunnel: 1:1, 1+1, or 1:N.
Field Description
MPLS-TP Tunnel Endpoints Tab
ID Tunnel endpoint identifier as a Tunnel-tp interface on the selected network
element.
Tunnel ID Unique tunnel identifier.
Admin Status Administrative status of the tunnel: Up or Down.
Oper Status Operational status of the tunnel: Up or Down.
Bandwidth (kbps) Configured bandwidth (in Kb/s) for the tunnel.
Description Tunnel description.
TP Enabled Links Tab
Link ID Identifier assigned to the MPLS-TP interface.
Interface Hyperlink to the interface in physical inventory.
Next Hop IP address of the next hop in the path.
LSP End Points Tab
LSP ID LSP identifier, derived from both endpoint identifiers and using the format
src-node-ID::src-tunnel-number::dest-node-ID::dest-tunnel-number where:
• src-node-ID represents the identifier of the node originating the signal
exchange.
• src-tunnel-number represents source tunnel identifier.
• dest-node-ID represents the identifier of the target node.
• dest-tunnel-number represents the destination tunnel identifier.
LSP Type Indicates whether the LSP is active (Working) or backup (Protect).
In Label Incoming label identifier.
Out Label Outgoing label identifier.
Out Interface Outgoing interface hyperlinked to the relevant entry in physical inventory.
Bandwidth (kbps) Bandwidth specification in Kb/s.
Role (Oper Status) Role of the LSP endpoint (Active or Standby) with the operational status (UP
or DOWN).
Field Description
LSP Mid Points Tab
LSP ID LSP identifier, derived from both endpoint identifiers and using the format
src-node-ID::src-tunnel-number::dest-node-ID::dest-tunnel-number where:
• src-node-ID represents the identifier of the node originating the signal
exchange.
• src-tunnel-number represents source tunnel identifier.
• dest-node-ID represents the identifier of the target node.
• dest-tunnel-number represents the destination tunnel identifier.
LSP Type Indicates whether the LSP is active (Working) or backup (Protect).
Forward In Label Incoming label identifier in the forward direction (source to destination).
Forward Out Label Label selected by the next hop device in the forward direction.
Reverse In Label Incoming label identifier in the reverse direction (destination to source).
Reverse Out Label Label selected by the next hop device in the reverse direction.
Forward Out Interface Outgoing interface in the forward direction, hyperlinked to its entry in
physical inventory.
Forward Bandwidth Bandwidth specification in Kb/s for the forward direction.
(kbps)
Reverse Out Link ID Link identifier assigned to the outgoing interface in the reverse direction.
Reverse Out Interface Outgoing interface in the reverse direction, hyperlinked to its entry in
physical inventory.
Reverse Bandwidth Bandwidth specification in Kb/s for the reverse direction.
Internal ID Identifier associated with the parent entity of the link. Using an internal
identifier ensures that individual LSP links do not participate in multiple
network LSPs.
Step 3 To view additional MPLS-TP tunnel endpoint properties, double-click the required entry in the
MPLS-TP Tunnel Endpoints table.
The MPLS-TP Tunnel Properties window is displayed as shown in Figure 17-4.
Table 17-4 describes the information available in the top portion of the MPLS-TP Tunnel Properties
window. For information about the tabs that are displayed, see Table 17-3.
Field Description
Tunnel ID Unique tunnel identifier.
Peer Tunnel ID Unique identifier of peer tunnel.
Bandwidth (kbps) Configured bandwidth (in Kb/s) for the tunnel.
Admin Status Administrative status of the tunnel: Up or Down.
Oper Status Operational status of the tunnel: Up or Down.
Local Info MPLS-TP source node identifier for this element in the form of an
IPv4 address.
Peer Info MPLS-TP peer node identifier in the form of an IPv4 address.
Global ID Globally unique Attachment Interface Identifier (AII) for MPLS-TP
derived from the Autonomous System Number (ASN) of the system
hosting the PEs.
Peer Global ID Globally unique AII for the peer.
Working LSP Number Number assigned to the working LSP. By default, the working LSP
number is 0 and the protected LSP number is 1.
Field Description
Protect LSP Number Number assigned to the protected LSP. By default, the working LSP
number is 0 and the protected LSP number is 1.
BFD Template BFD template associated with this MPLS-TP tunnel.
Working LSP BFD State Configured state of the working LSP BFD template: Up or Down.
Protect LSP BFD State Configured state of the protected LSP BFD template: Up or Down.
Working LSP Fault OAM Indicates that a fault has been detected on the working LSP.
Protect LSP Fault OAM Indicates that a fault has been detected on the protected LSP.
Tunnel Name Tunnel name.
Adjacent Hyperlink to the adjacent endpoint in logical inventory.
Step 1 In the map view, right-click the required link and choose Properties.
Step 2 In the link properties window, choose the required Ethernet link.
The link properties window refreshes and displays the Labels button as shown in Figure 17-5.
Step 4 To identify a specific path, click an outgoing label in the Source table. The corresponding in label is
selected in the Destination table.
Step 1 To determine if an LSP endpoint on an MPLS-TP tunnel is configured for redundancy service, expand
the required MPLS-TP tunnel in the navigation or map pane.
If the LSP endpoint is configured for redundancy service, the redundancy service badge is displayed in
the navigation and map panes as shown in Figure 17-7.
Step 2 To view properties for the LSP endpoint, navigate to and right-click the required endpoint in the map or
navigation pane, and choose Properties.
The LSP endpoint properties window is displayed as shown in Figure 17-8.
Table 17-5 describes the information displayed in the LSP Endpoint Properties window.
Field Description
LSP Type Indicates whether the LSP is active (Working) or backup (Protected).
LSP ID LSP identifier, derived from both endpoint identifiers and using the format
src-node-ID::src-tunnel-number::dest-node-ID::dest-tunnel-number where:
• src-node-ID represents the identifier of the node originating the signal
exchange.
• src-tunnel-number represents source tunnel identifier.
• dest-node-ID represents the identifier of the target node.
• dest-tunnel-number represents the destination tunnel identifier.
In Label Incoming label identifier.
Out Label Outgoing label identifier.
Bandwidth (kbps) Bandwidth specification in Kb/s.
Out Link ID Link identifier assigned to the outgoing interface.
Out Interface Outgoing interface hyperlinked to the relevant entry in physical inventory.
Role (Oper Status) Role of the LSP endpoint (Active or Standby) with the operational status (UP
or DOWN)
Step 3 To view LSP endpoint redundancy status in inventory, double-click the element on which the MPLS-TP
tunnel is configured.
Step 4 Choose Logical Inventory > MPLS-TP > MPLS-TP Global > LSP End Points.
Step 5 The LSP End Points tab contains the following information related to LSP redundancy service (see
Figure 17-9):
• Whether the LSP endpoint is Working or Protected.
• The LSP endpoint role, either Active or Standby.
• The operational status of the LSP endpoint, either Up or Down.
Step 1 In Prime Network Vision, display the network map on which you want to apply an overlay.
Step 2 From the main toolbar, click Choose Overlay Type and choose MPLS-TP tunnel.
The Select MPLS-TP tunnel Overlay dialog box is displayed.
Note An overlay is a snapshot taken at a specific point in time and does not reflect changes that occur in the
service. As a result, the information in an overlay can become stale. To update the overlay, click Refresh
Overlay in the main toolbar.
Viewing VPNs
Figure 17-11 shows a VPN displayed in the Prime Network Vision map view. In this example, the VPN
is selected in the navigation pane, so the VPN details, such as virtual routers and IP interfaces, are not
shown in the map view.
Figure 17-12 shows a VPN with details, including virtual routers and sites, in the Prime Network Vision
map view.
Figure 17-12 VPN in Prime Network Vision Map View with VRFs and Sites
1 Virtual routers
2 Sites
The Prime Network Vision navigation pane displays the VPN business elements in a tree-and-branch
representation. Each business element is represented by an icon in a color that reflects the highest alarm
severity. The icon might also have a management state badge or alarm. For more information about icon
severity colors and badges, see Prime Network Vision Status Indicators, page 2-26.
Table 17-6 shows the VPN icons in the Prime Network Vision map view.
Icon Description
Root (map name) or aggregation
VPN
Virtual router
Site
The highest level of the navigation pane displays the root or map name. The branches display the VPN
and aggregated business elements as well as their names. The Layer 3 VPN sub-branch displays the
virtual routers and sites contained in the VPN along with the names of the business elements. In addition,
CE devices can be displayed in the Layer 2 and Layer 3 VPN sub-branches. If you select an aggregated
business element in the navigation pane, the map view displays the business elements contained within
the aggregated business element.
The Prime Network Vision map view displays the VPN business elements and aggregated business
elements loaded in the map view, along with the names of the business elements. In addition, the map
view displays the VPN topology (between the virtual routers in the VPNs) and the topology and
associations between other business elements. After you select the root in the navigation pane, the map
view displays all the VPNs.
Prime Network Vision presents tickets related to the map in the ticket area, which allows you to view
and manage the VPN tickets.
Managing VPNs
The following topics describe:
• Creating a VPN, page 17-22
• Adding a VPN to a Map, page 17-23
• Removing a VPN from a Map, page 17-24
• Moving a Virtual Router Between VPNs, page 17-24
Creating a VPN
You can change business configurations by manually creating VPNs. The VPNs that are manually
created do not contain virtual routers and sites.
To create a VPN:
Step 1 In the Prime Network Vision navigation pane, select the map root.
Step 2 From the File menu, choose Add to Map > VPN > New.
Step 3 In the Create VPN dialog box, enter the following:
• Name—A unique name for the new VPN.
• Icon—To use a custom icon for the VPN, click the button next to the Icon field and navigate to the
icon file.
Note If a path is not specified to an icon, the default VPN icon is used (for more information about
icons, see Table 17-6 on page 17-21).
For more information about loading the newly created VPN in the service view map, see Adding a VPN
to a Map, page 17-23.
Note Adding a VPN affects other users if they are working with the same map.
Step 1 In Prime Network Vision, display the map to which you want to add the VPN.
Step 2 Do either of the following:
• From the File menu, choose Add to Map > VPN > Existing.
• In the main toolbar, click Add to Map, then choose Add to Map > VPN > Existing.
The Add VPN dialog box is displayed.
Step 3 Do either of the following:
• Choose a search category, enter a search string, then click Go to narrow search results to a range of
VPNs or a specific VPN. Search categories include:
– Description
– Name
The search condition is “contains.” Search strings are case-insensitive. For example, if you choose
the Name category and enter “net,” Prime Network Vision displays VPNs that have “net” in their
names whether at the beginning of the name, the middle, or the end.
• Choose Show All to display all the VPNs.
Step 4 Select the VPN that you want to add to the map.
Note If the routing information changes after an overlay is applied, the changes do not appear in the current
overlay. Click Refresh Overlay to update the routing information.
Step 1 In the Prime Network Vision navigation pane or map, right-click the virtual router and choose Edit >
Move selected.
Step 2 Right-click the required VPN in the navigation pane or map to where you want to move the virtual router
and choose Edit > Move here.
Caution Moving a virtual router from one VPN to another affects all users who have the virtual router loaded in
their service view map.
The virtual router and its sites are displayed under the selected VPN in the navigation pane and in the
map.
Step 1 In Prime Network Vision, display the network map on which you want to apply an overlay.
Step 2 From the main toolbar, click Choose Overlay Type and choose VPN.
The Select VPN Overlay dialog box is displayed.
Step 3 Do one of the following:
• Choose a search category, enter a search string, then click Go to narrow the search results to a range
of VPNs or a specific VPN. Search categories include:
– Description
– Name
The search condition is “contains.” Search strings are case-insensitive. For example, if you choose
the Name category and enter “net,” Prime Network Vision displays VPNs that have “net” in their
names whether net appears at the beginning of the name, the middle, or at the end: for example,
Ethernet.
• Choose Show All to display all the VPNs.
Step 4 Select the VPN overlay that you want to apply to the map.
The PE routers, MPLS routers, and physical links used by the selected VPN are highlighted in the
network map. The VPN name is displayed in the title of the window.
Note An overlay is a snapshot taken at a specific point in time and does not reflect changes that occur in the
service. As a result, the information in an overlay can become stale. To update the overlay, click Refresh
Overlay in the main toolbar.
Note The Show Overlay button is a toggle. When clicked, the overlay is displayed. When clicked
again, the overlay is hidden.
• To remove the VPN overlay, choose Show Overlay Type > None.
Note The link must be displayed in the VPN overlay and not dimmed for you to display the link callouts.
1 Link details and direction. In this example, 3 Details of sites using the link and interlinks.
the link is from P-North to PE-West. In this example, the site PE-West is linked to
all sites on PE-South.
2 Details of the sites using the link and 4 Link details and the direction. In this
interlinks. In this example, the site PE-88 is example, the link is from PE-West to P-North.
linked to site PE-West.
Step 1 In the Prime Network Vision window, display the map view with the VPN overlay.
Step 2 Right-click the required link in the map view and choose Show Callouts.
Step 3 To hide the callouts, right-click the link in the map view that is displaying the callouts and choose Hide
Callouts.
Step 1 In the Prime Network Vision navigation pane or map view, do either of the following:
• If the VPN icon is of the largest size, click the Properties button.
• Right-click the VPN and choose Properties.
The VPN Properties window displays the following information:
• Name—Name of the VPN.
• ID—Unique identifier assigned to the VPN.
Step 2 Click Close to close the VPN Properties dialog box.
Field Description
Name Name of the site, such as FastEthernet4/1.252.
State Interface state, either Up or Down.
IP Address IP address of the interface.
Mask Network mask.
Interface Description Description applied to the interface.
Associated Entity Element and interface associated with the site, hyperlinked to its
entry in physical inventory.
Addresses Table
Subnet IP address and subnet mask.
Note If the site is an IPv6 VPN over MPLS with IPv6 addresses
provisioned, the IPv6 addresses are displayed. For more
information, see Viewing IPv6 Information, page 16-3.
Type Address type, such as Primary, Secondary, or IPv6 Unicast.
The VRF Properties window contains the VRF routing table for the device. The table is a collection of
routes that are available or reachable to all the destinations or networks in the VRF. The forwarding table
also contains MPLS encapsulation information.
Table 17-9 describes the information displayed in the VRF Properties window.
Note The VRF Properties window only displays properties and attributes that are provisioned in the
VRF. You might not see all the fields and tabs described in Table 17-9.
Field Description
Route Distinguisher Route distinguisher configured in the VRF.
Name VRF name.
Description Description of the VRF.
IPv4 Tab
Export Route Targets IPv4 export route targets contained by the VRF.
Import Route Targets IPv4 import route targets contained by the VRF.
Route Maps Route maps for the VRF.
IPv6 Tab
Export Route Targets IPv6 export route targets contained by the VRF.
Import Route Targets IPv6 import route targets contained by the VRF.
Route Maps Route maps for the VRF.
Routing Tables
Destination Destination of the specific network.
Prefix Length Length of the network prefix in bits.
Next Hop Next routing hop.
Outgoing Interface Name of the outgoing interface; displayed if the Routing Protocol type is
local.
Type Route type: Direct (local), Indirect, or Static.
Routing Protocol Routing protocol used to communicate with the other sites and VRFs: BGP
or local.
BGP Next Hop Border Gateway Protocol (BGP) next hop. This is the PE address from
which to continue to get to a specific address. This field is empty when the
routing entry goes to the CE.
Bottom In Label Innermost label that is expected when MPLS traffic is received.
Bottom Out Label Innermost label sent with MPLS traffic.
Outer Label Outermost or top label in the stack used for MPLS traffic.
Field Description
Sites Tab
Name Site name.
IP Address IP address of the interface.
Mask Subnet mask.
State State of the subinterface: Up or Down.
Associated Entity Element and interface associated with the site, hyperlinked to its entry in
physical inventory.
Description Interface description.
Input Access List Access list applied to the inbound traffic.
Output Access List Access list applied to the outbound traffic.
Rate Limits If a rate limit is configured on an IP interface, the limit is shown as an IP
interface property. This option is checked when a rate limit is defined on
the IP interface, meaning the access list is a rate limit access list. IP
interface traffic is measured and includes the average rate, normal burst
size, excess burst size, conform action, and exceed action.
Note Double-clicking a row displays the properties of the IP interface.
When a rate limit is configured on the IP interface, the Rate Limits
tab is displayed. For more information about rate limits, see
Viewing Rate Limit Information, page 17-36.
Note The Input Access, Output Access, and Rate Limits parameters
apply only to Cisco IOS devices.
IP Sec Map Name IP Security (IPsec) map name.
Site Name Name of the business element to which the interface is attached.
Field Description
Name VRF name.
Route Distinguisher Route distinguisher configured in the VRF.
VRF V6 Table IPv6 route distinguisher if IPv6 is configured.
Step 1 Right-click the required device in Prime Network Vision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > Routing Entities > Routing Entity.
The routing information is displayed as shown in Figure 17-15.
Table 17-11 describes the information that is displayed in the Routing Entity table.
Field Description
Name Name of the routing entity.
IP Interfaces Tab
Name Site name.
IP Address IP address of the interface.
Mask Network mask.
State State of the subinterface: Up or Down.
Associated Entity Interface associated with the routing entity, hyperlinked to its location in
physical inventory.
Description Description of the interface.
Input Access List If an input access list is assigned to an IP interface, the list is shown as an IP
interface property, and a hyperlink highlights the related access list in the
Access List table. When an access list is assigned to the inbound traffic on an
IP interface, the actions assigned to the packet are performed.
VRRP Group If a VRRP group is configured on an IP interface, the information is shown
as an IP interface property. This option is checked when a rate limit is defined
on the IP interface.
Note Double-clicking a row displays the properties of the IP interface.
When a VRRP group is configured on an IP interface, the VRRP
Groups tab is displayed in the IP Interface Properties window. For
more information, see Viewing VRRP Information, page 17-37.
Output Access List If an output access list is assigned to an IP interface, the list is shown as an
IP interface property, and a hyperlink highlights the related access list in the
Access List table. When an access list is assigned to the outbound traffic on
an IP interface, the actions assigned to the packet are performed.
Rate Limits If a rate limit is configured on an IP interface, the limit is shown as an IP
interface property. This option is checked when a rate limit is defined on the
IP interface, meaning the access list is a rate limit access list. IP interface
traffic is measured and includes the average rate, normal burst size, excess
burst size, conform action, and exceed action.
Note Double-clicking a row displays the properties of the IP interface.
When a rate limit is configured on the IP interface, the Rate Limits
tab is displayed. For more information, see Viewing Rate Limit
Information, page 17-36.
Note The Input Access, Output Access, and Rate Limits parameters apply
only to Cisco IOS devices.
IP Sec Map Name IP Security (IPsec) crypto map name.
Site Name Name of the business element to which the interface is attached.
Field Description
IPv4 and IPv6 Routing Table Tabs
Destination Destination of the specific network.
Outgoing If Name Name of the outgoing interface; displayed if the Routing Protocol type is
local.
Type Routing type: Direct, Indirect, Static, Other, Invalid, or Unknown.
Next Hop IP address from which to continue to get to a specific address. This field is
empty when the routing entry goes to a PE router.
Prefix Length Length of the network prefix in bits.
Route Protocol Type Routing protocol used to communicate with other routers.
Step 1 Right-click the required device in Prime Network Vision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > Routing Entities > Routing Entity >
ARP.
Table 17-12 describes the information that is displayed in the ARP table.
Field Description
MAC Interface MAC address.
Interface Interface name.
IP Address Interface IP address.
State Interface state:
• Dynamic—The entry was learned by the device according to
network traffic.
• Static—The entry was learned by a local interface or from a user
configuring a static route.
• Other—The entry was learned by another method not explicitly
defined.
• Invalid—In SNMP, this type is used to remove an ARP entry from
the table.
Step 1 Right-click the required device in Prime Network Vision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > Routing Entities > Routing Entity >
ARP Entity.
Step 3 Click the NDP Table tab.
Figure 17-16 shows an example of the NDP Table tab.
Field Description
MAC Interface MAC address.
Interface Interface name.
IP Address Interface IPv6 address.
Type Entry type:
• ICMP (Incomplete)—Address resolution is being performed on the
entry. A neighbor solicitation (NS) message has been sent to the
solicited-node multicast address of the target, but the corresponding
neighbor advertisement (NA) message has not yet been received.
• REACH (Reachable)—Positive confirmation was received via an
NA that the forward path to the neighbor was functioning properly.
While in REACH state, the device takes no special action as packets
are sent.
• STALE—Too much time has elapsed since the last positive
confirmation was received that the forward path was functioning
properly. While in STALE state, the device takes no action until a
packet is sent.
• DELAY—Too much time has elapsed since the last positive
confirmation was received that the forward path was functioning
properly. If no reachability confirmation is received within a
specified amount of time, the device sends an NS message and
changes the state to PROBE.
• PROBE—A reachability confirmation is actively sought by
resending neighbor solicitation messages until a reachability
confirmation is received.
• ????—The state is unknown.
Step 1 Right-click the required element in Prime Network Vision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > Routing Entities > Routing Entity.
Step 3 In the IP Interfaces tab, double-click the required interface to view the IP interface properties. If a rate
limit is configured on the IP interface, the Rate Limits tab is displayed.
Note Rate limit information is relevant only for Cisco IOS devices.
Table 17-14 describes the information that is displayed in the Rate Limits tab of the IP Interface
Properties dialog box.
Field Description
Type Rate limit direction, either Input or Output.
Max Burst Excess burst size in bytes.
Normal Burst Normal burst size in bytes.
Bit Per Second Average rate in bits per second.
Conform Action Action that can be performed on the packet if it conforms to the specified
rate limit (rule), for example, continue, drop, change a bit, or transmit.
Exceed Action Action that can be performed on the packet if it exceeds the specified rate
limit (rule), for example, continue, drop, change a bit, or transmit.
Access List Hyperlink that highlights the related access list in the Access List table.
Field Description
Group Number Number of the VRRP group associated with the interface.
Priority Value that determines the role each VRRP router plays and what
happens if the master virtual router fails.
Values are 1 through 254, with lower numbers having priority over
higher numbers.
Master IP Address IP address of the VRRP group, taken from the physical Ethernet
address of the master virtual router.
Admin State Administrative status of the VRRP group: Up or Down.
Operation State State of the VRRP group: Master or Backup.
Preempt Mode Whether or not the router is to take over as the master virtual router
for a VRRP group if it has a higher priority than the current master
virtual router: Enabled or Disabled.
Virtual IP Address IP address of the virtual router.
Virtual MAC Address MAC address of the virtual router.
Advertisement Interval Amount of time (in seconds) between successive advertisements by
the master virtual router.
Table 17-16 describes the information that is displayed for label switched entities.
Field Description
Local LDP ID Local Label Distribution Protocol (LDP) identifier.
LDP Process State State of the LDP process, such as Running, Down, or Unknown.
MPLS Interfaces
ID Identifier for MPLS interface, as a combination of IP address and
interface name.
Distribution Protocol Type Distribution protocol used: Null, LDP, TDP (Tag Distribution
Protocol), RSVP, or TDP and LDP.
MPLS TE Properties Whether or not traffic engineering (TE) properties are configured
on the interface:
• Checked—MPLS TE properties are configured on the interface.
• Unchecked—MPLS TE properties are not configured on the
interface.
Discovery Protocols Discovery protocols used on the interface.
Label Switching Table
Incoming Label Incoming MPLS label identifier.
Action Type of switching action: Null, Pop, Swap, Aggregate, Untagged,
or Act. If an action is defined as Pop, an outgoing label is not
required. If an action is defined as Untagged, an outgoing label is
not present.
Outgoing Label Outgoing label.
Out Interface Name of the outgoing interface, displayed as a hyperlink to the port
subinterface in physical inventory.
IP Destination Destination IP address.
Destination Mask Subnet mask of the destination.
Next Hop IP address of the next hop in the path. The IP address is used for
resolving the MAC address of the next MPLS interface that you
want to reach.
VRF Table
Incoming Label Incoming VRF label identifier.
Action Type of switching action: Null, Pop, Swap, Aggregate, Untagged,
or Act.
VRF VRF name, hyperlinked to its location in logical inventory.
IP Destination Destination IP address.
Destination Mask Subnet mask of the destination.
Next Hop IP address of the next hop in the path. The IP address is used for
resolving the MAC address of the next MPLS interface that you
want to reach.
Out Interface Name of the outgoing interface, displayed as a hyperlink to the port
subinterface in physical inventory.
Field Description
Traffic Engineering LSPs
LSP Name Label switched path (LSP) name.
LSP Type Segment type: Head, Midpoint, or Tail.
Source Address Source IP address.
Destination Address Destination IP address.
In Label Incoming label, if not a head segment.
In Interface Incoming interface, if not a head segment.
Out Interface Outgoing interface, if not a tail segment.
Out Label Outgoing label, if not a tail segment.
Average Bandwidth (Kbps) Current bandwidth (in Kb/s) used to automatically allocate the
tunnel’s bandwidth.
LSP ID LSP identifier.
Burst (Kbps) Tunnel bandwidth burst rate, in Kb/s.
Peak (Kbps) Tunnel bandwidth peak rate, in Kb/s.
FRR TE Tunnel Fast Reroute (FRR) TE tunnel name, hyperlinked to the routing
entity in logical inventory.
FRR TE Tunnel State State of the FRR TE tunnel:
• Active—A failure exists in the primary tunnel and the backup
is in use.
• Not Configured—The primary tunnel has no designated backup
tunnel.
• Ready—The primary tunnel is in working condition.
MPLS Label Range
MPLS Label Type Type of MPLS label: Dynamic or Static.
Minimum Label Value Lowest acceptable MPLS label in the range.
Maximum Label Value Highest acceptable MPLS label in the range.
Field Description
LDP Neighbors
LDP ID Identifier of the LDP peer.
Transport IP Address IP address advertised by the peer in the hello message or the hello
source address.
Session State Current state of the session: Transient, Initialized, Open Rec, Open
Sent, or Operational.
Protocol Type Protocol used by the peer to establish the session: LDP, TDP, or
Unknown.
Label Distribution Method Method of label distribution: Downstream, Downstream On
Demand, Downstream Unsolicited, or Unknown.
Session Keepalive Interval Length of time (in milliseconds) between keepalive messages.
Session Hold Time The amount of time (in milliseconds) that an LDP session can be
maintained with an LDP peer, without receiving LDP traffic or an
LDP keepalive message from the peer.
Discovery Sources Whether the peer has one or more discovery sources:
• Checked—Has one or more discovery sources.
• Unchecked—Has no discovery sources.
Note To see the discovery sources in the LDP Neighbor
Properties window, double-click the row of the peer in the
table.
Step 3 Double-click an entry in any of the tables to view additional properties for that entry.
Table 17-17 Additional Properties Available from Label Switching in Logical Inventory
Note If there are multiple MP-BGP links between two devices, Prime Network displays each link in the content
pane map view.
Step 1 Right-click the required device in Prime Network Vision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > MPBGPs > MPBGP.
Table 17-18 describes the information that is displayed for MP-BGP.
Field Description
Local AS Identifier of the autonomous system (AS) to which the router
belongs.
BGP Identifier BGP identifier, represented as an IP address.
Cross VRFs Tab
VRF Name Name of the VRF.
Cross VRF Routing Entries Group of cross VRFs that share a single destination.
BGP Neighbors Tab
Peer AS Identifier of the AS to which the remote peer belongs.
Peer State State of the remote peer: Active, Connect, Established, Open
Confirm, Open Sent, or Null.
Peer Address Remote peer IP address.
AFI Address family identifier: IPv4, IPv6, L2VPN, VPNv4, or VPNv6.
AF Peer State Address family peer state: Established or Idle.
Peer BGP ID Identifier of the remote peer, represented as an IP address.
Local BGP ID Local peer IP address.
VRF Name Remote peer VRF name.
BGP Neighbor Type Neighbor type: Null, Client, or Non Client.
Hold Time (secs) Established hold time in seconds.
Keepalive (secs) Established keepalive time in seconds.
BGP Neighbor Entry BGP neighbor IP address.
Field Description
Tunnel Name 6rd tunnel name.
IPv6 Prefix IPv6 prefix used to translate the IPv4 address to an IPv6 address.
Source Address Tunnel IPv4 source IP address.
Tunnel SubMode Tunnel type:
• 6rd—Static IPv6 interface.
• 6to4—IPv6 address with the prefix embedding the tunnel
source IPv4 address.
• Auto-tunnel—IPv4-compatible IPv6 tunnel.
• ISATAP—Overlay tunnel using an Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) address.
Prefix Length IPv4 prefix length used to derive the delegated IPv6 prefix.
Suffix Length IPv4 suffix length used to derive the delegated IPv6 prefix.
MTU Maximum transmission unit (MTU) configured on the 6rd IPv4
tunnel.
Field Description
Process Process name, such as Bidirectional Forwarding Detection.
Process State Process state, such as Running.
BFD Sessions Table
Source IP Source IP address of the session.
Destination IP Destination IP address of the session.
State Session state, such as Up or Down.
Interface Interface used for BFD communications, hyperlinked to the routing
entity in logical inventory.
Registered Protocols Routing protocol being monitored for communication failures, such as
BGP or OSPF.
Field Description
Process Process name: Bidirectional Forwarding Detection.
Process State Process state, such as Running.
MPLS-TP BFD Sessions Table
Interface Interface used for BFD communications, hyperlinked to the routing
entity in logical inventory.
LSP Type Type of LSP: Working or Protected.
State Session state: Up or Down.
Registered Protocols Routing protocol being monitored for communication failures:
MPLS-TP.
Interface Name
Step 3 To view additional properties, double-click the required entry in the Sessions table.
Table 17-22 describes the information that is displayed in the Session Properties window.
Field Description
Source IP Source IP address of the session.
Destination IP Destination IP address of the session.
State Session state: Up or Down.
Interface Hyperlink to the routing entity in logical inventory.
Registered Protocols Routing protocol being monitored for communication failures.
Protocols Table
Protocol Protocol used for this session.
Interval Length of time (in milliseconds) to wait between packets that are
sent to the neighbor.
Multiplier Number of times a packet is missed before the neighbor is declared
down.
Step 1 Right-click the required device in Prime Network Vision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > MPBGPs > MPBGP.
Step 3 Click the Cross VRFs tab.
Step 4 Double-click the required entry in the list of cross-VRFs.
The Cross VRF Properties window is displayed, containing the information described in Table 17-23.
Field Description
Name Cross-VRF name.
Cross VRF Routing Entries Table
Destination IP address of the destination network.
Prefix Length of the network prefix in bits.
Next Hop IP address of the next hop in the path.
Out Going VRF Outgoing VRF identifier, hyperlinked to its entry in logical inventory.
Out Tag Outgoing virtual router tag, such as 50 or no tag.
In Tag Incoming virtual router tag, such as 97 or no tag.
Step 1 Right-click the required device in Prime Network Vision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > Pseudowires.
The Tunnel Edges table is displayed and contains the information described in Table 17-24.
Field Description
Local Interface Name of the subinterface or port.
Strings, such as Aggregation Group, EFP, VLAN, and VSI, are included in the interface name, and
the entry is hyperlinked to the relevant entry in logical or physical inventory:
• Aggregation groups are linked to Ethernet Link Aggregation in logical inventory.
• ATM interfaces are linked to the port in physical inventory and the ATM interface.
• ATM VCs are linked to the port in physical inventory and the Port IP Properties table.
• CEM groups are linked to the port in physical inventory and the CEM Group table.
• EFPs are linked to the port in physical inventory and the EFPs table.
• IMA groups are linked to IMA Groups in logical inventory.
• Local switching entities are linked to Local Switching Entity in logical inventory.
• VLANs are linked to Bridges in logical inventory.
• VSIs are linked to the VSI entry in logical inventory.
VC ID Tunnel identifier, hyperlinked to the PTP Layer 2 MPLS Tunnel Properties window.
Peer Details of the selected peer, hyperlinked to the peer pseudowire tunnel in logical inventory.
Status Operational state of the tunnel: Up or Down.
Pseudowire Role If the pseudowire is in a redundancy configuration, indicates whether its role is as the primary or
secondary pseudowire in the configuration.
If the pseudowire is not configured for redundancy, this field is blank.
Preferred Path Path to be used for MPLS pseudowire traffic.
Tunnel
Local Router IP IP address of this tunnel edge, which is used as the MPLS router identifier.
Peer Router IP IP address of the peer tunnel edge, which is used as the MPLS router identifier.
Pseudowire Type Type of pseudowire, such as Ethernet, Ethernet Tagged, CESoPSN Basic, PPP, or SAToP.
Local MTU Size, in bytes, of the MTU on the local interface.
Remote MTU Size, in bytes, of the MTU on the remote interface.
Local VC Label MPLS label that is used by this router to identify or access the tunnel. It is inserted into the MPLS
label stack by the local router.
Peer VC Label MPLS label that is used by this router to identify or access the tunnel. It is inserted into the MPLS
label stack by the peer router.
Signaling Protocol Protocol used by MPLS to build the tunnel, for example, LDP or TDP.
Step 1 Right-click the required device in Prime Network Vision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > Traffic Engineering Tunnels.
Table 17-25 describes the information that is displayed in the Tunnel Edges table.
Field Description
Name Name of the TE tunnel; for Cisco devices it is the interface name.
Tunnel Type Whether the tunnel is Point-to-Point or Point-to-Multipoint.
Tunnel Destination IP address of the device in which the tunnel ends.
Administrative Status Administrative state of the tunnel: Up or Down.
Operational Status Operational state of the tunnel: Up or Down.
Outgoing Label TE tunnel’s MPLS label distinguishing the LSP selection in the next device.
Description Description of the tunnel.
Outgoing Interface Interface through which the tunnel exits the device.
Bandwidth (KBps) Bandwidth specification for this tunnel in Kb/s.
Setup Priority Tunnel priority upon path setup.
Hold Priority Tunnel priority after path setup.
Affinity Tunnel preferential bits for specific links.
Affinity Mask Tunnel affinity bits that should be compared to the link attribute bits.
Auto Route Whether or not destinations behind the tunnel are routed through the tunnel:
Enabled or disabled.
Lockdown Whether or not the tunnel can be rerouted:
• Enabled—The tunnel cannot be rerouted.
• Disabled—The tunnel can be rerouted.
Path Option Tunnel path option:
• Dynamic—The tunnel is routed along the ordinary routing decisions after
taking into account the tunnel constraints such as attributes, priority, and
bandwidth.
• Explicit—The route is explicitly mapped with the included and excluded
links.
Average Rate (Kbps) Average bandwidth for this tunnel (in Kb/s).
Field Description
Burst (Kbps) Burst flow specification (in Kb/s) for this tunnel.
Peak Rate (Kbps) Peak flow specification (in Kb/s) for this tunnel.
LSP ID LSP identifier.
Policy Class Value of Policy Based Tunnel Selection (PBTS) configured. Values range
from 1-7.
FRR TE Fast Reroute (FRR) status: Enabled or Disabled.
Type
The Traffic Engineering LSPs tab in the LSEs branch in logical inventory displays TE tunnel LSP
information.
For details about the information displayed for TE tunnel LSPs, see Traffic Engineering LSPs,
page 17-41.
The following topics describe Mobile Transport over Packet (MToP) services and the properties
available in Cisco Prime Network Vision (Prime Network Vision):
• User Roles Required to Work with MToP, page 18-1
• Viewing SAToP Pseudowire Type in Logical Inventory, page 18-2
• Viewing CESoPSN Pseudowire Type in Logical Inventory, page 18-3
• Viewing Virtual Connection Properties, page 18-5
• Viewing IMA Group Properties, page 18-13
• Viewing TDM Properties, page 18-16
• Viewing Channelization Properties, page 18-17
• Viewing MLPPP Properties, page 18-26
• Viewing MLPPP Link Properties, page 18-29
• Viewing MPLS Pseudowire over GRE Properties, page 18-32
• Network Clock Service Overview, page 18-35
• Viewing CEM and Virtual CEM Properties, page 18-51
By default, users with the Administrator role have access to all managed elements. To change the
Administrator user scope, see the topic on device scopes in the Cisco Prime Network 3.8 Administrator
Guide.
Table 18-1 Default Permission/Security Level Required for Viewing MToP Properties - Element
Not in User’s Scope
Table 18-2 Default Permission/Security Level Required for Viewing MToP Properties - Element in
User’s Scope
Step 1 In Prime Network Vision, right-click the device on which SAToP is configured, then choose Inventory.
Step 2 In the inventory window, choose Logical Inventory > Pseudowires.
Step 3 In the Tunnel Edges table, select the required entry and scroll horizontally until you see the Pseudowire
Type column. See Figure 18-1.
Note You can also view this information by right-clicking the entry in the table and choosing
Properties.
Step 4 To view the physical inventory for the port, click the hypertext port link.
To view TDM properties for Circuit Emulation (CEM) groups in Prime Network Vision:
Step 1 In Prime Network Vision, right-click the device on which CESoPSN is configured, then choose
Inventory.
Step 2 In the inventory window, choose Logical Inventory > Pseudowires.
Step 3 In the Tunnel Edges table, select the required entry and scroll horizontally until you see the Pseudowire
Type column. See Figure 18-2.
Note You can also view this information by right-clicking the entry in the table and choosing
Properties.
Step 4 To view the physical inventory for the port, click the hypertext port link.
Step 1 In Prime Network Vision, right-click the required device, then choose Inventory.
Step 2 Open the VC Cross Connect table in either of the following ways:
• In the inventory window, choose Logical Inventory > VC Switching Entities > VC Switching
Entity. The Cross-Connect Table is displayed in the content pane as shown in Figure 18-4.
• In the inventory window:
a. Choose Physical Inventory > Chassis > Slot > Subslot > Port.
b. Click the Show Cross Connect button.
The VC Cross Connections window is displayed and contains the same information as the
Cross-Connect Table in logical inventory.
Step 3 Select an entry and scroll horizontally until you see the required information.
Table 18-3 identifies the properties that are displayed for ATM VC cross-connects.
Field Description
In Port Incoming port for the cross-connect.
In VC Incoming virtual connection for the cross-connect.
You can view additional details about the virtual connection in the following
ways:
• Click the hyperlinked entry to view the VC table.
• Right-click the entry, then choose Properties to view information about the
incoming and outgoing VCIs, VPI, service category, and traffic descriptors.
Out Port Outgoing port for the cross-connect.
Out VC Outgoing virtual connection for the cross-connect.
You can view additional details about the virtual connection in the following
ways:
• Click the hyperlinked entry to view the VC table.
• Right-click the entry, then choose Properties to view information about the
incoming and outgoing VCIs, VPI, service category, and traffic descriptors.
In VC Ingress ATM traffic parameters and service categories for the incoming traffic on the
Traffic Descriptor incoming VC cross-connect.
For information on VC traffic descriptors, see Table 18-4.
In VC Egress ATM traffic parameters and service categories for the outgoing traffic on the
Traffic Descriptor incoming VC cross-connect.
For information on VC traffic descriptors, see Table 18-4.
Out VC Egress ATM traffic parameters and service categories for the outgoing traffic on the
Traffic Descriptor outgoing VC cross-connect.
For information on VC traffic descriptors, see Table 18-4.
Out VC Ingress ATM traffic parameters and service categories for the incoming traffic on the
Traffic Descriptor outgoing VC cross-connect.
For information on VC traffic descriptors, see Table 18-4.
Value Description
ABR Available bit rate (ABR) supports nonreal-time applications that tolerate
high cell delay, and can adapt cell rates according to changing network
resource availability to prevent cell loss.
CBR Constant bit rate (CBR) supports real-time applications that request a static
amount of bandwidth that is continuously available for the duration of the
connection.
CDVT Cell Delay Variation Tolerance (CDVT) specifies an acceptable deviation in
cell times for a PVC that is transmitting above the PCR. For a given cell
interarrival time expected by the ATM switch, CDVT allows for some
variance in the transmission rate.
CLP Cell loss priority (CLP) indicates the likelihood of a cell being dropped to
ease network congestion.
MBS Maximum Burst Size (MBS) specifies the number of cells that the edge
device can transmit up to the PCR for a limited period of time without
penalty for violation of the traffic contract.
MCR Minimum Cell Rate (MCR) specifies the cell rate (cells per second) at which
the edge device is always allowed to transmit.
PCR Peak Cell Rate (PCR) specifies the cell rate (cells per second) that the edge
device cannot exceed.
PDR CLP0+1: 1536 Packet delivery ratio (PDR) for all cells (both CLP1 and CLP0 cells) on the
circuit.
SCR Sustainable Cell Rate (SCR) specifies the upper boundary for the average
rate at which the edge device can transmit cells without loss.
UBR Unspecified Bit Rate (UBR) supports nonreal-time applications that tolerate
both high cell delay and cell loss on the network.
UBR+ Unspecified bit rate plus (UBR+) supports nonreal-time applications that
tolerate both high cell delay and cell loss on the network, but request a
minimum guaranteed cell rate.
nrt-VBR Nonreal-time variable bit rate (nrt-VBR) supports nonreal-time applications
with bursty transmission characteristics that tolerate high cell delay, but
require low cell loss.
rt-VBR rt-VBR—Real-time variable bit rate (rt-VBR) supports real-time
applications that have bursty transmission characteristics.
Field Description
VPI Virtual Path Identifier for the selected port.
VCI Virtual Channel Identifier for the selected port.
Admin Status Administrative state of the connection: Up, Down, or Unknown.
Oper Status Operational state of the connection: Up, Down, or Unknown.
Ingress Traffic Descriptor Traffic parameters and service categories for the incoming traffic.
For information on VC traffic descriptors, see Table 18-4.
Egress Traffic Descriptor Traffic parameters and service categories for the outgoing traffic.
For information on VC traffic descriptors, see Table 18-4.
Shaping Profile Traffic shape profile used for the virtual connection.
Type ATM traffic descriptor type for the virtual connection.
Interface Name Interface name, such as ATM1/1/16.
Step 1 In Prime Network Vision, double-click the element configured for virtual connection encapsulation.
Step 2 In the inventory window, choose Physical Inventory > Chassis > Slot > Subslot > Port.
Step 3 Click the Show Encapsulation button.
The VC Encapsulation window is displayed as shown in Figure 18-6.
Field Description
VC Virtual connection identifier, such as VC:7/4.
Type Type of encapsulation, such as Point-to-Point Protocol (PPP) over
ATM (PPPoA) or ATM adaption layer Type 5 (AAL5).
Binding Information Information tied to the virtual connection, such as a user name.
Binding Status Binding state: Bound or Unbound.
VC Egress Traffic Descriptor Traffic parameters and service categories for the outgoing traffic.
For information on VC traffic descriptors, see Table 18-4.
VC Ingress Traffic Descriptor Traffic parameters and service categories for the incoming traffic.
For information on VC traffic descriptors, see Table 18-4.
Discovery Protocols Discovery protocol used for the VC.
Table 18-7 describes the information displayed for the IMA group.
Field Description
Active Bandwidth Active bandwidth of the IMA group.
Admin Status Administrative status of the IMA group.
Clock Mode Clock mode the IMA group is using:
• Common—Common transmit clocking (CTC).
• Independent—Independent transmit clocking (ITC).
Configured Bandwidth Total bandwidth of the IMA group, which is the sum of all
individual links in the group.
Field Description
Description IMA group interface name.
Frame Length Length of the IMA group transmit frames, in the number of cells:
32, 64, 128, or 256.
A small frame length causes more overhead but loses less data if a
problem occurs. We recommend a frame length of 128 cells.
Group Number IMA group number.
Group State IMA group status, in the order of usual appearance:
• Startup—The near end is waiting to receive indication that the
far end is in Startup. The IMA group moves to the Startup-Ack
state when it can communicate with the far end and has
recorded IMA identifier, group symmetry, and other IMA group
parameters.
• Startup ACK—Both sides of the link are enabled.
• Config Aborted—The far end has unacceptable configuration
parameters, such as an unsupported IMA frame size, an
incompatible group symmetry, or an unsupported IMA version.
• Insufficient Links—The near end has accepted the far end
group parameters, but the far end does not have sufficient links
to move into the Operational state.
• Operational—The group is not inhibited and has sufficient
links in both directions. The IMA interface can receive ATM
layer cells and pass them from the IMA sublayer to the ATM
layer.
• Blocked—The group is blocked, even though sufficient links
are active in both directions.
IMA Version IMA version configured, either 1.0 or 1.1.
Minimum Number of Rx Links Minimum number of Rx links needed for the IMA group to be
operational.
Minimum Number of Tx Links Minimum number of Tx links needed for the IMA group to be
operational.
Number of Active Links Number of DS1 (E1 or T1) links that are active in the group.
Number of Configured Links Number of DS1 (E1 or T1) links that are configured in the IMA
group.
Field Description
Oper Status Operational state of the IMA group interface:
• Dormant—The interface is dormant.
• Down—The interface is down.
• Not Present—An interface component is missing.
• Testing—The interface is in test mode.
• Unknown—The interface has an unknown operational status.
• Up—The interface is up.
Port Type Type of port, such as ATM IMA.
Table 18-8 describes the information displayed in the IMA Members table.
Column Description
Admin Status Administrative status of the IMA member.
Channelization Channelization that occurs through the path, such as
STS1-> VTG-> VT15.
Information is displayed in this field only if the T1 or E1 path was
channelized. If the line was not channelized, this field is not displayed.
For example, if the IMA group is configured on a T1 or E1 card, this
field is not displayed.
Clocking Source of the clocking mechanism: Internal or Line.
Description Type of channelization, such as Synchronous Transport Signal 1
(STS-1) or Synchronous Transport Module level 1 (STM-1).
Oper Status Operational state of the IMA member:
Physical Port Hyperlinked entry to the port in physical inventory.
Port Type Type of port, such as E1 or T1.
Step 3 In the IMA Members table, click a hyperlinked port entry to view the port properties in physical
inventory. See Figure 18-8.
The information that is displayed for the port in physical inventory depends on the type of connection,
such as SONET or ATM.
MToP encapsulates TDM streams for delivery over packet-switching networks (PSNs) using the
following methods:
• SAToP—A method for encapsulating TDM bit-streams (T1, E1, T3, or E3) as pseudowires over
PSNs.
• CESoPSN—A method for encapsulating structured (NxDS0) TDM signals as pseudowires over
PSNs.
For T1 or E1 entries, the TDM properties presented in Table 18-9 are displayed in physical inventory in
addition to the existing T1 or E1 properties.
Table 18-9 TDM-Specific Properties for DS1 (T1 or E1) in Physical Interfaces
Field Description
International Bit Whether or not the international bit is used by the controller:
• 0—The international bit is not used.
• 1—The international bit is used.
This property applies only to E1.
National Bits Whether or not the national reserve bits (sa4, sa5, sa6, sa7, and sa8) are used
by the controller:
• 0—The national reserve bits are not used.
• 1—The national reserve bits are used.
This property applies only to E1.
Line Code Line encoding method for the DS1 link:
• For E1, the options are Alternate Mark Inversion (AMI) and
high-density bipolar of order 3 (HDB3).
• For T1, the options are AMI and bipolar with 8 zero substitution (B8ZS).
Cable Length For T1 ports in short-haul mode, the length of the cable in feet.
Step 1 In Prime Network Vision, right-click the required device, then choose Inventory.
Step 2 Choose Physical Inventory > Chassis > slot > subslot > SONET/SDH-interface. The properties for
SONET/SDH and OC-3 are displayed in the content pane. See Figure 18-9.
Table 18-11 describes the information that is displayed for SONET/SDH and OC3 in the content pane.
Field Description
SONET/SDH High Order Path (HOP) Area
Description SONET/SDH path description including the interface and high order
path. Double-click an entry to view additional details about the path.
Channelization Type of channelization, such as STS-1 or STM-1.
Admin Status Administrative status of the HOP.
Oper Status Operational status of the HOP.
OC3 Area
Admin Status Administrative status of the OC-3 line.
Oper Status Operational status of the OC-3 line.
Port Type Type of port.
Last Changed Date and time of the last status change of the line.
Scrambling Any scrambling that has been applied to the SONET payload.
Maximum Speed Maximum bandwidth for the line.
Loopback Loopback setting configured on the line.
Port Description Description of the port defined by the user.
Clocking Clocking configured on the line.
Specific Type Specific type of line; in this case, OC3.
Internal Port Whether or not the line includes an internal port: True or False.
Ss Ctps Table Size Size of the SONET/SDH Connection Termination Point (CTP) table.
Step 3 To view additional information about a channelized path, double-click the required entry in the
Description column. The SONET/SDH High Order Path Properties window is displayed as shown in
Figure 18-10.
Table 18-12 describes the information displayed in SONET/SDH High Order Path Properties window.
Field Description
Description SONET/SDH path description including the interface and high order
path. Double-click an entry to view additional details about the path.
Channelization Type of channelization, such as Synchronous Transport Signal 1
(STS-1) or Synchronous Transport Module level 1 (STM-1).
Admin Status Administrative status of the HOP.
Oper Status Operational status of the HOP.
Port Type Type of port.
Last Changed Date and time of the last status change of the path.
Maximum Speed Maximum bandwidth for the line.
MTU MTU for the path.
Applique Type Sub-STS-1 facility applied to this path. In this example, the facility
applied is Virtual Tributary 1.5 (VT1.5).
Sending Alarms Whether or not the path is sending alarms: True or False.
Field Description
Low Order Path Tab
Description Description of the low order path down to the T1 level, including the
channel types (such as STS-1, VTG, or VT) and channel allocated.
Physical Port Hyperlinked entry to the port in physical inventory.
Channelization Channelization that occurs through the path, such as
STS1-> VTG-> VT15.
Admin Status Administrative status of the path.
Oper Status Operational status of the path.
Clocking Source of the clocking mechanism: Internal or Line.
Supported Alarms Tab
Name Supported alarm.
Enable Whether the alarm is enabled or disabled.
Step 1 In Prime Network Vision, right-click the required device, then choose Inventory.
Step 2 Choose Physical Inventory > Chassis > slot > subslot > T3-interface.
Figure 18-11 shows DS1 channelization properties for T3 in physical inventory.
Table 18-13 describes the information that is displayed for Channelized DS1 and DS3 in the content
pane.
Field Description
Channelized DS1 Table
Description Path description including the physical interface and the channel
number. Double-click an entry to view additional details about the path.
Physical Port Physical port for the channelized line.
Channelization Type of channelization, such as channelized T3 (CT3) to T1.
Admin Status Administrative status of the channelized line.
Oper Status Operational status of the channelized line.
VDC For devices with multiple virtual contexts, the context associated with
the channelized line.
Clocking Clocking configured on the line: Internal or Line.
Field Description
DS3 Area
Admin Status Administrative status of the DS3 line.
Oper Status Operational status of the DS3 line.
Port Type Type of port.
Last Changed Date and time of the last status change of the line.
Maximum Speed Maximum bandwidth for the line.
Port Description Description of the port configured on the interface.
Recovered Clocking ID Recovered clock identifier, if known.
Scrambling Any scrambling that has been applied to the SONET payload.
Framing Type of framing applied to the line.
Loopback Loopback setting configured on the line.
Clocking Clocking configured on the line: Internal or Line.
Alarm State Alarm state of the DS3 line:
• Clear—The alarm state is clear.
• AIS—Alarm Indication Signal (AIS).
• LOS—Loss of signal (LOS) alarm.
• AIS_LOS—AIS loss of signal alarm.
• LOF—Loss of frame (LOF) alarm.
• AIS_LOF—AIS loss of frame alarm.
• LOS_LOF—Loss of signal and loss of frame alarm.
• AIS_LOS_LOF—AIS loss of signal and loss of frame alarm.
• Unknown—Unknown alarm.
Internal Port Whether or not the line includes an internal port: True or False.
Line Code Line coding applied to the line.
Step 3 To view additional information about a DS1channelized path, double-click the required entry in the
Channelized DS1 table. Figure 18-12 shows the information that is displayed in the Channelized DS1
PDH Properties window.
Table 18-14 describes the information that is displayed in the Channelized DS1 PDH Properties window.
Field Description
Location Area
Description Path description including the physical interface and the channel
number.
Channelization Type of channelization used on the line, such as CT3-> T1.
Admin Status Administrative status of the channelized line.
Oper Status Operational status of the channelized line.
Field Description
Alarm State Alarm state of the DS1 line:
• Clear—The alarm state is clear.
• AIS—Alarm Indication Signal (AIS).
• LOS—Loss of signal (LOS) alarm.
• AIS_LOS—AIS loss of signal alarm.
• LOF—Loss of frame (LOF) alarm.
• AIS_LOF—AIS loss of frame alarm.
• LOS_LOF—Loss of signal and loss of frame alarm.
• AIS_LOS_LOF—AIS loss of signal and loss of frame alarm.
• Unknown—Unknown alarm.
Sending Alarms Whether or not the line is sending alarms: True or False.
Maximum Speed Maximum bandwidth for the line.
Framing Type of framing applied to the line.
Line Code Line coding applied to the line.
Loopback Loopback setting configured on the line.
Clocking Clocking configured on the line: Internal or Line.
Recovered Clock ID Recovered clock identifier, if known.
Group Table
This table appears only if a DS0 bundle is configured on a channelized DS1 line. The properties
that are displayed pertain to the DS0 bundle.
Group Name of the DS0 bundle.
Time Slots Range of timeslots (DS0 channels) allotted to the group.
Oper Status Operational status of the group.
Encapsulation Type of encapsulation used, such as High-Level Data Link Control
(HDLC).
Admin Status Administrative status of the group.
ID DS0 bundle identifier.
Step 1 In Prime Network Vision, right-click the required device, then choose Inventory.
Step 2 In the inventory window, choose Logical Inventory > MLPPP. See Figure 18-13.
Field Description
Type Type of properties; in this case, MLPPP.
MLPPP Bundle Table
MLPPP MLPPP bundle name, hyperlinked to the MLPPP Properties window.
Name MLPPP interface name.
Group MLPPP group to which the bundle belongs.
Active Link Number of active interfaces participating in MLPPP.
Admin Status Administrative status of the MLPPP bundle: Up or Down.
Operational Status Administrative status of the MLPPP bundle: Up or Down.
LCP Status Link Control Protocol (LCP) status of the MLPPP bundle: Closed,
Open, Started, or Unknown.
Step 3 To view properties for individual MLPPP bundles, double-click the hyperlinked entry in the MLPPP
Bundle table.
The MLPPP Properties window is displayed as shown in Figure 18-14.
Table 18-16 describes the information that is displayed in the MLPPP Properties window.
Field Description
MLPPP MLPPP bundle name, hyperlinked to MLPPP in logical inventory.
Name MLPPP interface name.
Group Group to which the MLPPP bundle belongs.
Active Link Number of active interfaces participating in MLPPP.
Admin Status Administrative status of the MLPPP bundle: Up or Down.
Operational Status Operational status of the MLPPP bundle: Up or Down.
LCP Status Link Control Protocol (LCP) status of the MLPPP bundle: Closed,
Open, Started, or Unknown.
Minimum Configured Minimum number of configured links for an MLPPP bundle.
Link
Maximum Configured Maximum number of configured links for an MLPPP bundle.
Link
Bandwidth Bandwidth allocated to the MLPPP bundle.
MTU Size of the Maximum Transmission Unit (MTU), from 1 to 2147483647
bytes.
Keepalive Status of the keepalive function: Set, Not Set, or Unknown.
Keepalive Time If keepalive is enabled, the amount of time, in seconds, to wait before
sending a keepalive message.
Interleave Enabled Whether or not interleaving of small fragments is enabled.
Fragment Disable Whether fragmentation is enabled or disabled: True or False.
Fragment Delay Maximum size, in units of time, for packet fragments on an MLPPP
bundle. Values range from 1 to 999.
Fragment Maximum Maximum number of MLPPP bundle fragments.
Keepalive Retry Number of times that the device sends keepalive packets without
response before closing the MLPPP bundle protocol. Values range from
2 to 254.
Load Threshold Minimum load threshold for the MLPPP bundle. If the traffic load falls
below the threshold, the link is removed.
Field Description
MLPPP Members Table
ID MLPPP bundle member identifier, hyperlinked to the interface in
physical inventory.
Type No value is displayed in this field.
Binding Information Binding information to which the interface is associated. The value is
null.
Binding Status No value is displayed in this field.
Discovery Protocols Discovery protocol used on the interface.
Step 4 To view the interface properties in physical inventory, double-click the required entry in the ID column.
Step 1 In the Prime Network Vision map view, select a link connected to two MLPPP devices and open the link
quick view window as shown in Figure 18-15.
Table 18-17 describes the information that is displayed for the MLPPP link.
Field Description
General Properties
Link Type Link protocol. In this case, MLPPP.
Type Type of link: Dynamic or Static.
Bi Directional Whether the link is bidirectional: True or False.
MLPPP Properties Properties are displayed for both ends of the MLPPP link.
MLPPP Interface configured for MLPPP, hyperlinked to the entry in physical
inventory.
Group MLPPP group to which the interface belongs.
Active Link Number of active interfaces participating in the MLPPP link for each device.
Admin Status Administrative status of the interface: Up or Down.
Operational Status Operational status of the interface: Up or Down.
LCP Status LCP status of the MLPPP interface: Closed, Open, Started, or Unknown.
Step 1 In Prime Network Vision, right-click the required device, then choose Inventory.
Step 2 In the inventory window, choose Logical Inventory > Pseudowires. The Tunnel Edges table is
displayed in the content pane as shown in Figure 18-17.
Step 3 Select the required entry and scroll horizontally until you see the required information.
Table 18-18 describes the information included in the Tunnel Edges table specifically for MPLS
pseudowire tunnels over GRE.
Field Description
Pseudowire Type Type of pseudowire relevant to MToP:
• ATM AAL5 SDU—ATM with ATM Adaptation Layer 5
(AAL5) service data units.
• ATM n-to-one VCC—ATM with n-to-one virtual channel
connection (VCC).
• ATM n-to-one VPC—ATM with n-to-one virtual path
connection (VPC).
• CESoPSN Basic—CESoPSN basic services with CAS.
• SAToP E1—SAToP on an E1 interface.
Local MTU Size, in bytes, of the MTU on the local interface.
Remote MTU Size, in bytes, of the MTU on the remote interface.
Preferred Path Tunnel Path to be used for MPLS pseudowire traffic.
Click the hyperlinked entry to view the tunnel details in logical
inventory.
Step 4 To view GRE Tunnel properties, choose Logical Inventory > GRE Tunnels.
Figure 18-18 shows the Tunnel Edges table that is displayed for GRE tunnels.
Table 18-19 describes the information that is displayed for GRE tunnels in logical inventory.
Field Description
Name Tunnel name.
IP Address Tunnel IP address.
Source IP address local to the device.
Destination IP address of the remote router.
State State of the tunnel: Up or Down.
Keepalive Time If keepalive is enabled, the amount of time, in seconds, to wait before
sending a keepalive message.
Type Tunnel type.
Keepalive Status of the keepalive function: Set, Not Set, or Unknown.
Keepalive Retry Number times that the device continues to send keepalive packets
without response before bringing the tunnel interface protocol down.
Values range from 2 to 254, with a default of 3.
Note In Prime Network Vision, clock service refers to network clock service.
The following topics describe how to use Prime Network Vision to monitor clock service:
• Monitoring Clock Service, page 18-35
• Monitoring PTP Service, page 18-37
• Viewing Pseudowire Clock Recovery Properties, page 18-42
• Viewing SyncE Properties, page 18-46
• Applying a Network Clock Service Overlay, page 18-49
Step 1 In Prime Network Vision, right-click the required device, then choose Inventory.
Step 2 In the inventory window, choose Logical Inventory > Clock. Clock service information is displayed in
the content pane as shown in Figure 18-19.
Field Description
Clock Service Mode This field is not populated.
Network Clock Select Mode Action to take if the master device fails:
• Non-revert—Do not use the master device again after it
recovers from the failure.
• Revert—Use the master device again after it recovers and
functions correctly for a specified amount of time.
• Unknown—The network clock selection mode is unknown.
Service Status Status of the system service:
• Initializing—The service is starting up.
• Down—The service is down.
• Reset—The service has been reset.
• Running—The service is running.
• Other—A status other than those listed.
Active Clock Source Current active clock source used by the device.
Hold Timeout How long the device waits before reevaluating the network
clock entry. Values can be from 0-86400 seconds, Not Set, or
infinite.
Service Type Type of system service, such as Clock or Cisco Discovery
Protocol.
Use Stratum4 Quality of the clock source:
• True—Use Stratum 4, the lowest level of clocking quality.
• False—(Default) Use Stratum 3, a higher level of clocking
quality than Stratum 4.
Field Description
Clock Source Table This table is displayed only if there are active clock sources.
Clock Source Current active clock source used by the device.
Network Clock Priority Priority of the clock source with 1 being the highest priority.
Source Type Method by which clocking information is provided:
• BITS—Timing is supplied by a Building Integrated Timing
Supply (BITS) port clock.
• E1/T1—Clocking is provided via an E1 or T1 interface.
• Packet-Timing—Clocking is provided over a packet-based
network.
• Synchronous Ethernet—Clocking is provided by
Synchronous Ethernet.
• Others—Clocking is provided by a source other than the
above.
Valid Source Validity of the clock source:
• True—The clock source is valid and operational.
• False—The clock source is not valid or is not operational.
Step 1 In Prime Network Vision, right-click the required device, then choose Inventory.
Step 2 In the inventory window, choose Logical Inventory > Clock > PTP Service. The PTP service properties
are displayed in the content pane as shown in Figure 18-20.
Table 18-21 describes the properties that are displayed for PTP service.
Field Description
PTP Mode Mode of PTP operation:
• Boundary—Boundary clock mode.
• E2E Transparent—End-to-end transparent clock mode.
• Ordinary—Ordinary clock mode.
• P2P Transparent—Peer-to-peer transparent clock mode.
• Unknown—The clock mode is unknown.
Note Cisco MWR-2941 routers support Ordinary mode only.
PTP Clock ID Clock identifier derived from the device interface.
PTP Domain Number of the domain used for PTP traffic. A single network
can contain multiple separate domains.
Priority 1 First value checked for clock selection. The clock with the
lowest priority takes precedence.
Priority 2 If two or more clocks have the same value in the Priority 1 field,
the value in this field is used for clock selection.
Port State Clock state according to the PTP engine:
• Freerun—The slave clock is not locked to a master clock.
• Holdover—The slave device is locked to a master device,
but communication with the master is lost or the
timestamps in the PTP packet are incorrect.
• Acquiring—The slave device is receiving packets from a
master and is trying to acquire a clock.
• Freq locked—The slave device is locked to the master
device with respect to frequency, but is not aligned with
respect to phase.
• Phase aligned—The slave device is locked to the master
device with respect to both frequency and phase.
PTP Interface List Table
Interface Name Interface identifier.
PTP Version Version of PTP used. The default value is 2, indicating PTPv2.
Port Name Name of the PTP port clock.
Port Role PTP role of the clock: Master or Slave.
Field Description
PTP Slave Mode For an interface defined as a slave device, the mode used for
PTP clocking:
• Not Set—The slave mode is not used.
• Multicast—The interface uses multicast mode for PTP
clocking.
• Unicast—The interface uses unicast mode for PTP
clocking.
• Unicast with Negotiation—The interface uses unicast
mode with negotiation for PTP clocking.
Clock Source Addresses IP addresses of the clock source.
Delay Request Interval (log mean When the interface is in PTP master mode, the interval
value) specified to member devices for delay request messages. The
intervals use base 2 values, as follows:
• 4—1 packet every 16 seconds.
• 3—1 packet every 8 seconds.
• 2—1 packet every 4 seconds.
• 1—1 packet every 2 seconds.
• 0—1 packet every second.
• -1—1 packet every 1/2 second, or 2 packets per second.
• -2—1 packet every 1/4 second, or 4 packets per second.
• -3—1 packet every 1/8 second, or 8 packets per second.
• -4—1 packet every 1/16 seconds, or 16 packets per second.
• -5—1 packet every 1/32 seconds, or 32 packets per second.
• -6—1 packet every 1/64 seconds, or 64 packets per second.
Announce Interval (log mean value) Interval value for PTP announcement packets:
• 4—1 packet every 16 seconds.
• 3—1 packet every 8 seconds.
• 2—1 packet every 4 seconds.
• 1—1 packet every 2 seconds.
• 0—1 packet every second.
• -1—1 packet every 1/2 second, or 2 packets per second.
• -2—1 packet every 1/4 second, or 4 packets per second.
• -3—1 packet every 1/8 second, or 8 packets per second.
• -4—1 packet every 1/16 seconds, or 16 packets per second.
• -5—1 packet every 1/32 seconds, or 32 packets per second.
• -6—1 packet every 1/64 seconds, or 64 packets per second.
Field Description
Announce Timeout Number of PTP announcement intervals before the session
times out. Values are 2-10.
Sync Interval (log mean value) Interval for sending PTP synchronization messages:
• 4—1 packet every 16 seconds.
• 3—1 packet every 8 seconds.
• 2—1 packet every 4 seconds.
• 1—1 packet every 2 seconds.
• 0—1 packet every second.
• -1—1 packet every 1/2 second, or 2 packets per second.
• -2—1 packet every 1/4 second, or 4 packets per second.
• -3—1 packet every 1/8 second, or 8 packets per second.
• -4—1 packet every 1/16 seconds, or 16 packets per second.
• -5—1 packet every 1/32 seconds, or 32 packets per second.
• -6—1 packet every 1/64 seconds, or 64 packets per second.
Sync Limit (nanoseconds) Maximum clock offset value, in nanoseconds, before PTP
attempts to resynchronize.
Interface Physical interface identifier, hyperlinked to the routing
information for the interface.
PTP Master Mode For an interface defined as a master device, the mode used for
PTP clocking:
• Not Set—The master mode is not used.
• Multicast—The interface uses multicast mode for PTP
clocking.
• Unicast—The interface uses unicast mode for PTP
clocking. This mode allows a single destination.
• Unicast with Negotiation—The interface uses unicast
mode with negotiation for PTP clocking. This mode allows
up to 128 destinations.
Clock Destination Addresses IP addresses of the clock destinations. This field contains IP
addresses only when Master mode is enabled.
Domain Clocking domain.
Step 1 Choose Logical Inventory > Clock > Pseudowire Clock Recovery. Prime Network Vision displays the
Virtual CEM information by default. See Figure 18-21.
Step 2 To view more information about a virtual CEM, right-click the virtual CEM, then choose Properties.
The Virtual CEM Properties window is displayed.
The information that is displayed in the Virtual CEM Properties window depends on whether or not the
virtual CEM belongs to a group:
• If a CEM group is not configured on the virtual CEM, the Virtual CEM Properties window contains
only the CEM interface name.
• If a CEM group is configured on the virtual CEM, the Virtual CEM Properties window contains the
information described in Table 18-22.
Field Description
CEM Interface Name CEM interface name.
CEM Group Table
CEM Group Name of the virtual CEM group.
Framing Framing mode used for the CEM channel:
• Framed—Specifies the channels used for the controller, such as
Channels: (1-8), (10-14). The channels that are available
depend on the type of controller: T1, E1, T3, or E3.
• Unframed—Indicates that a single CEM channel is used for all
T1/E1 timeslots. SAToP uses the unframed mode.
Pseudowire Name of the pseudowire configured on the CEM interface,
hyperlinked to the pseudowire properties in logical inventory.
Oper Status Operational status of the CEM interface:
• Dormant—The interface is dormant.
• Down—The interface is down.
• Not Present—An interface component is missing.
• Testing—The interface is in test mode.
• Unknown—The interface has an unknown operational status.
• Up—The interface is up.
Admin Status Administrative status of the CEM interface:
• Down—The CEM interface is administratively down.
• Testing—The administrator is testing the CEM interface.
• Unknown—The administrative status is unknown.
• Up—The CEM interface is administratively up.
Step 3 To view additional CEM group properties, double-click the required CEM group.
Table 18-23 describes the information displayed in the CEM Group Properties window.
Field Description
Oper Status Operational status of the CEM interface:
• Dormant—The interface is dormant.
• Down—The interface is down.
• Not Present—An interface component is missing.
• Testing—The interface is in test mode.
• Unknown—The interface has an unknown operational status.
• Up—The interface is up.
Idle Pattern Eight-bit hexadecimal number that is transmitted on a T1 or E1 line
when missing packets are detected on the pseudowire (PW) circuit.
Type Type of CEM group. This is always DS0 Bundle.
Idle CAS Pattern When CAS is used, the 8-bit hexadecimal signal that is sent when
the CEM interface is identified as idle.
Bundle Location Associated card and slot for the virtual CEM, using the virtual CEM
port 24; for example virtual-cem/8/3/24:0.
Dejitter Size of the dejitter buffer in milliseconds (ms). The range is 4 to 500
ms with a default of 4 ms.
RTP Hdr Compression Whether RTP header compression is enabled or disabled.
RTP Enabled Whether RTP compression is enabled or disabled.
Admin Status Administrative status of the CEM interface:
• Down—The CEM interface is administratively down.
• Testing—The administrator is testing the CEM interface.
• Unknown—The administrative status is unknown.
• Up—The CEM interface is administratively up.
ID DS0 bundle CEM group identifier.
Payload Size Size of the payload for packets on the CEM interface. The range is
32 to 1312 bytes.
Step 4 To view recovered clock entries, click the Recovered Clock Entries tab. See Figure 18-22.
If no recovered clock entries exist, this tab is not displayed.
Table 18-24 describes the information displayed for pseudowire clock recovery.
Field Description
Recovered Clock Source Interface (slot/subslot) in which clock recovery occurred.
Click the hyperlinked entry to view its properties in physical
inventory.
Recovered Clock Mode Recovered clock mode:
• Adaptive—The devices do not have a common clock
source. The recovered clock is derived from packet arrival.
• Differential—The edge devices have a common clock
source, and the recovered clock is derived from timing
information in packets and the related difference from the
common clock.
• Synchronous—A GPS or BITS clock source externally
synchronizes both end devices. This method is extremely
accurate, but is rarely available for all network devices.
Field Description
Virtual CEM Tab
CEM Interface Name Virtual CEM interface associated with the clock.
Recovered Clock Entries Tab This tab appears if recovered entries exist.
Transfer Type • In-band—The clocking information is sent over the same
pseudowire as the bearer traffic.
• Out-of-band—The clocking information is sent over a
dedicated pseudowire between the sending and receiving
SPAs.
Clock ID Clock identifier, if known.
Clock Mode Clock mode of the recovered clock:
• Adaptive—The recovered clock was obtained using ACR.
• Primary—The recovered clock was obtained from a clock
with the highest priority.
• Secondary—The recovered clock was obtained from a
clock with a lower priority than the primary clock.
Clock Status Status of the clock:
• Acquiring—The clock is obtaining clocking information.
• Acquired—The clock has obtained the required clocking
information.
• Holdover—The current primary clock is invalid and a
holdover timer has started to check whether or not the clock
becomes valid within the specified holdover time.
CEM Group CEM group associated with the clock.
CEM Group ID Identifier of the CEM group associated with the clock.
CEM Interface Name Virtual CEM interface associated with the clock.
Frequency Offset Offset to the clock frequency, in Hz.
Field Description
Synchronous Mode Status of the automatic synchronization selection process: Enabled or
Disable.
Equipment Clock Ethernet Equipment Clock (EEC) options: EEC-Option I or
EEC-Option II.
Clock Mode Whether the clock is enabled or disabled for the Quality Level (QL)
function: QL-Enabled or QL-Disabled.
ESMC Ethernet Synchronization Message Channel (ESMC) status: Enabled or
Disabled.
SSM Option Synchronization Status Message (SSM) option being used:
• ITU-T Option I
• ITU-T Option II Generation 1
• ITU-T Option II Generation 2
Hold-off (global) Length of time (in milliseconds) to wait before issuing a protection
response to a failure event.
Wait-to-restore (global) Length of time (in seconds) to wait after a failure is fixed before the span
returns to its original state.
Revertive Whether the network clock is to use revertive mode: Yes or No.
Field Description
SyncE Interfaces Table
Interface Name Name of the Gigabit or 10 Gigabit interface associated with SyncE.
If SyncE is not associated with a Gigabit or 10 Gigabit interface, this
field contains Internal.
Interface Hyperlinked entry to the interface routing information in the Routing
Entity Controller window. For more information, see Viewing Routing
Entities, page 17-32.
This field does not apply for Internal interfaces.
Mode Whether the interface is enabled or disabled for the QL function:
QL-Enabled or QL-Disabled.
Timing Port Priority Value used for selecting a SyncE interface for clocking if more than one
interface is configured. Values are from 1 to 250, with 1 being the
highest priority.
QL Tx Actual Actual type of outgoing quality level information, depending on the
globally configured SSM option:
• ITU-T Option I—Available values are QL-PRC, QL-SSU-A,
QL-SSU-B, QL-SEC, and QL-DNU.
• ITU-T Option II Generation 1—Available values are QL-PRS,
QL-STU, QL-ST2, QL-SMC, QL-ST4, and QL-DUS.
• ITU-T Option II Generation 2—Available values are QL-PRS,
QL-STU, QL-ST2, QL-TNC, QL-ST3, QL-SMC, QL-ST4, and
QL-DUS.
QL Tx Configured Configured type of outgoing quality level information, depending on the
globally configured SSM option.
See QL Tx Actual for the available values.
QL Rx Actual Actual type of incoming quality level information, depending on the
globally configured SSM option.
See QL Tx Actual for the available values.
QL Rx Configured Configured type of incoming quality level information, depending on
the globally configured SSM option.
See QL Tx Actual for the available values.
Hold-Off Timer (msecs) Length of time (in milliseconds) to wait after a clock source goes down
before removing the source.
Wait-to-Restore (secs) Length of time (in seconds) to wait after a failure is fixed before the
interface returns to its original state.
Field Description
ESMC Tx Whether ESMC is enabled for outgoing QL information on the
interface: Enabled, Disabled, or NA (Not Available).
ESMC Rx Whether ESMC is enabled for incoming QL information on the
interface: Enabled, Disabled, or NA (Not Available).
SSM Tx Whether SSM is enabled for outgoing QL information on the interface:
Enabled, Disabled, or NA (Not Available).
SSM Rx Whether SSM is enabled for incoming QL information on the interface:
Enabled, Disabled, or NA (Not Available).
Step 1 In Prime Network Vision, display the network map on which you want to apply an overlay.
Step 2 From the main toolbar, click Choose Overlay Type and choose Network Clock.
The Select Network Clock Service Overlay dialog box is displayed.
Step 3 Do one of the following:
• Choose a search category, enter a search string, then click Go to narrow the search results to a range
of network clock services or a specific network clock service. Search categories include:
– Description
– Name
The search condition is “contains.” Search strings are case-insensitive. For example, if you choose
the Name category and enter “net,” Prime Network Vision displays network clock services that have
“net” in their names whether net appears at the beginning of the name, the middle, or at the end: for
example, Ethernet.
• Choose Show All to display all network clock services.
Step 4 Select the network clock service overlay that you want to apply to the map.
The elements and links used by the selected network clock are highlighted in the map, and the overlay
name is displayed in the title of the window. (See Figure 18-24.)
In addition, the elements configured for clocking service display a clock service icon as in the following
example:
Note An overlay is a snapshot taken at a specific point in time and does not reflect changes that occur in the
service. As a result, the information in an overlay can become stale. To update the overlay, click Refresh
Overlay in the main toolbar.
See Table 18-22 for a description of the properties displayed for CEM groups in the content pane.
Step 3 To view additional information, double-click the required group.
The CEM Group Properties window is displayed as shown in Figure 18-27.
See Table 17-24 on page 17-49 for the properties displayed in the Pseudowire table in the CEM Group
Properties window.
Step 1 In Prime Network Vision, right-click the required device, then choose Inventory.
Step 2 In the inventory window, choose Logical Inventory > Clock > Pseudowire Clock Recovery.
Step 3 In the Virtual CEM tab, right-click the CEM interface name and choose Properties. The CEM group
properties are displayed in a separate window (Figure 18-28). If a pseudowire is configured on the CEM
group for out-of-band clocking, the pseudowire VCID is also shown.
Step 4 To view additional CEM group properties, double-click the required CEM group.
Table 18-23 describes the information displayed in the CEM Group Properties window.
This topic identifies and describes the properties for Session Border Controllers (SBCs) that appear in
Cisco Prime Network Vision (Prime Network Vision)logical inventory.
An SBC can provide the following types of services:
• Protocol and media interworking
• Session routing
• Hosted Network Address Translation (NAT) and firewall traversal
• Security and AAA
• Intra- and inter-VPN interconnections and optimization
• Media transcoding with an external media server
SBC services are divided into the following components:
• Data Border Element (DBE)—Responsible for media-related functions.
• Signaling Border Element (SBE)—Responsible for call signaling-related functions.
Table 19-1 Default Permission/Security Level Required for Viewing SBC Properties - Element Not
in User’s Scope
Table 19-2 Default Permission/Security Level Required for Viewing SBC Properties - Element in
User’s Scope
Table 19-3 describes the general SBC properties displayed in logical inventory.
Field Description
Process Process name, such as Session Border Controller.
Process Status Status of the process, such as Running.
Application Version SBC version number.
Mode Mode in which the SBC is operating:
• Unified
• Distributed DBE
SBC Service Name Name of the service.
Field Description
Process Process name, such as DBE.
Process Status Status of the process, such as Running.
Name Name assigned to the DBE.
Type Type of DBE, either DBE or virtual DBE (vDBE).
DBE Location Id Unique identifier configured on each vDBE within a UM DBE.
Field Description
Address Range IP addresses defined for the pool.
Port Range Lower Lower end of the port range for the interface. If no range is specified, all possible
Voice over IP (VoIP) port numbers are valid.
Port Range Upper Upper end of the port range for the interface.
VRF Name VRF that the interface is assigned to.
Service Class Class of service (CoS) for each port range, such as fax, signaling, voice, or any.
Branch Description
H248 Controller H.248 controller used by the DBE.
The Media Gateway Configuration (MGC) table displays the following
information:
• Index—The number of the H.248 controller. The profile is used to
interoperate with the SBE.
• Remote IP—The remote IP address for the H.248 controller.
• Remote Port—The remote port for the H.248 controller.
• Transport—The transport for communications with the remote device.
H248 Interface The SBC H248 Control Interface table displays the following information:
• IP Address:
– In DM mode, the local IP address of the DBE used to connect to the
SBE.
– In UM mode, the local IP address used to connect to the media gateway.
• Port—The port for the H.248 controller interface.
• Transport—The transport the H.248 controller interface uses.
• Association—The relationship between the SBE and the media gateway.
Field Description
Process Name of the process, such as SBE.
Process Status Status of the process, such as Running or Idle.
Name Name assigned to this SBE.
Call Redirect Limit Maximum number of times a call is redirected before the call is
declared failed. The range is 0 to 100 with a default of 2.
On Hold Timeout Amount of time, in milliseconds, that the SBE waits after receiving
a media timeout notification from the DBE for an on-hold call
before tearing down the call.
Branch Description
AAA Interface The SBE AAA Interface table displays the following information:
• AAA Address—The local AAA interface address.
• Network ID—A unique identifier for the SBE.
Accounting The Accounting Radius Client table displays the following information:
• Name—The name of the accounting client.
• Client Type—The type of client, either Accounting or Authentication.
Branch Description
Authentication The Authentication Radius Client table displays the following information:
• Name—The name of the authentication client.
• Client Type—The type of client, either Accounting or Authentication.
Billing The SBE Billing table displays the following information related to billing:
• LDR Check Time—The time of day (local time) to run the long duration
record check.
• Local Billing Address—The local IP address for SBE billing. This IP
address can be different from the local AAA IP address and is the IP address
written in the bill records.
• Admin Status—The configuration status, available with the running-config
command.
• Operational Status—The running status, available from the CLI. This entry
indicates whether or not the billing interface is up. The status is derived from
the interworking of the SBC and the AAA server.
Branch Description
H248 Interface The SBC H248 Control Interface table displays the following information:
• IP Address:
– In DM mode, the IP address used to connect the DBE and the MGC.
– In UM mode, the IP address used to connect the SBC and the media
gateway.
• Port—The port for the H.248 controller interface.
• Transport—The transport the H.248 controller interface uses.
• Association—The relationship between the SBE and the media gateway.
Media Gateway The Media Gateway table displays the following information:
• IP Address—The IP address of the media gateway.
• Codec List—A comma-separated list of the codecs supported.
Branch Description
Blacklist The Blacklists table contains the following information:
• Name—The blacklist name.
• Type—The type of source that this blacklist applies to, such as critical or
normal.
CAC Policy A Call Admission Control (CAC) policy is used to define admission control.
The SBE CAC Policy Set table contains the following information:
• Policy Set Number—An identifying number the SBE has assigned to the
policy set.
• First Table—A CAC policy table.
• Status—Whether the policy is active or inactive. If the policy is active, the
SBC applies the defined rules to events.
• First CAC Scope—The scale that the CAC applies for, such as source
adjacency or destination adjacency. This is the first CAC table used for CAC
policy match.
• Description—A brief description of the policy set.
Call Policy A call policy set is used for number analysis and routing.
The SBE Call Policy Set table contains the following information:
• Policy Set Number—An identifying number the SBE has assigned to the
policy set.
• Status—Whether the policy is active or inactive. If the policy is active, the
SBC applies the defined rules to events.
• First Call Table—The first call table used for call policy match.
• Description—A brief description of the policy set.
Codec List The SBE Codec List table contains the following information:
• Name—The name of the codec list.
• Codecs—The codecs contained in each list.
Branch Description
Current The Current Blacklistings table contains the following information:
Blacklisting • Type—The type of source this blacklist applies to. Blacklists are used to
block certain VoIP services that meet specified conditions.
• Event Type—The type of event this blacklist applies to, such as
CORRUPT_MESSAGE.
• Is All Source Addresses—Whether the blacklist applies to all source IP
addresses:
– True—Ignore any IP address in the Source Address field.
– False—Use the IP address in the Source Address field.
• Source Address—The IP address that this blacklist applies to.
• Source Port Number—The port number that this blacklist applies to.
• Source Port Type—The type of port this blacklist applies to. All is a valid
entry.
• Time Remaining—The amount of time, in hours, minutes, or seconds, before
the blacklist is removed.
Hunting Trigger The hunting trigger enables the SBC to search for other routes or destination
adjacencies if an existing route fails.
The Global Hunting Trigger List table contains the following information:
• Hunting Mode—Indicates the protocol to use to search for routes, such as
Session Initiation Protocol (SIP).
• Hunting Triggers—The SIP responses, such as 468 or 503, that indicate the
SBC is to search for an alternate route or destination adjacency. SIP
responses are defined in RFC3261.
Branch Description
QoS Profile QoS profiles can be used by CAC policies and are used exclusively for marking
IP packets.
The QoS Profile table contains the following information:
• Name—The name of the QoS profile.
• Class of Service—The type of call this profile applies to, such as voice,
video, signaling, or fax.
• Marking Type—The type of marking to be applied to the IP packet. Options
include Passthrough, Differentiated Service Code Point (DSCP), and IP
Precedence/ToS.
• IP Precedence—If the marking type is IP Precedence, the specified
precedence, either 0 or 1.
• ToS—If the marking type is ToS, the ToS value.
• DSCP—If the marking type is DSCP, the DSCP value.
SDP The Session Description Protocol (SDP) content pane contains the following
tabs, each with their respective table:
• SBE SDP Policy Table:
– Instance Name—The name of the policy table.
– SBE SDP Match Table—The name of the SDP match table.
• SBE SDP Match Table:
– Instance Name—The name of the SDP match table.
– Match Strings—The match criteria.
– Table Type—The type of table, either Blacklist or Whitelist.
Branch Description
SIP Account The SBE Account table contains the following information:
• Name—The name of the account associated with the adjacencies.
• Adjacencies—The identified adjacencies.
SIP Adjacency An adjacency represents a signaling relationship with a remote call agent.
One adjacency is defined per external call agent. Each adjacency belongs
within an account. Each incoming call is matched to an adjacency, and each
outgoing call is routed out over a second adjacency.
The SBC SIP Adjacencies table contains the following information:
• Name—The adjacency name.
• Status—The status of the adjacency, either Attached or Detached.
• Signaling Address—The local IP address and port (optional) for
communications.
• Signaling Peer—The remote IP address and port (optional) for
communications.
• Description—A brief description of the adjacency.
SIP Adjacency Group The Adjacencies Groups table contains the following information:
• Name—The name of the SIP adjacency group.
• Adjacencies—The adjacencies that belong to the group.
SIP Profile The SBC can be configured with whitelist and blacklists profiles on SIP
messages. The following types of SIP profiles are available:
• Header profile—A profile based on SIP header information.
• Method profile—A profile based on SIP method strings.
• Option profile—A profile based on SIP option strings.
• Parameter profile—A profile based on SIP parameters.
SIP Profile > The SIP Header Profiles table contains the following information:
Header Profile
• Name—The name of the SIP header profile.
• Status—Whether or not the profile is in use.
• Profile Type—The type of profile:
– Whitelist—Accepts SIP requests that match the profile.
– Blacklist—Rejects SIP requests that match the profile.
• Description—A brief description of the profile.
Branch Description
SIP Profile > The SIP Method Profiles table contains the following information:
Method Profile • Name—The name of the SIP method profile.
• Status—Whether or not the profile is in use.
• Profile Type—The type of profile:
– Whitelist—Accepts SIP requests that match the profile.
– Blacklist—Rejects SIP requests that match the profile.
• Description—A brief description of the profile.
• Is Passthrough—Whether or not passthrough is enabled:
– True—Permits message bodies to be passed through for nonvital
methods that match this profile.
– False—Strips the message body out of any nonvital SIP messages
that match this profile.
SIP Profile > The SIP Option Profiles table contains the following information:
Option Profile
• Name—The name of the SIP option profile.
• Status—Whether or not the profile is in use.
• Profile Type—The type of profile:
– Whitelist—Accepts SIP requests that match the profile.
– Blacklist—Rejects SIP requests that match the profile.
• Description—A brief description of the profile.
• Options—The SIP option strings that define this profile, such as host
user-agent, refer redirect, or replaces.
Branch Description
SIP Profile > The SIP Parameter Profiles table contains the following information:
Parameter Profile • Name—The name of the SIP parameter profile.
• Status—Whether or not the profile is in use.
• Description—A brief description of the profile.
SIP Timer The SBE SIP Timer table contains the following information:
• TCP Connect Timeout—The time, in milliseconds, that the SBC waits
for a SIP TCP connection to a remote peer to complete before failing
that connection. The default is 1000 milliseconds.
• TCP Idle Timeout—The minimum time, in milliseconds, that a TCP
socket does not process any traffic before it closes the connection. The
default is 120000 milliseconds (2 minutes).
• TLS Idle Timeout—The minimum time, in milliseconds, that a
Transport Layer Security (TLS) socket does not process traffic before it
closes the connection.
• Invite Timeout—The time, in seconds, that the SBC waits for a final
response to an outbound SIP invite request. The default is 180 seconds.
If no response is received during that time, an internal request timeout
response is generated and returned to the caller.
• UDP First Retransmit Interval—The time, in milliseconds, that the SBC
waits for a UDP response or ACK before sending the first
retransmission of a signal. The default value is 500 milliseconds.
• UDP Max Retransmit Interval—The maximum time interval, in
milliseconds, for an SBC to retransmit a signal. The maximum
retransmission interval is 4000 milliseconds (4 seconds).
• UDP Response Linger Period—The time, in milliseconds, for which the
SBC retains negative UDP responses to invite requests. The default
value is 32000 milliseconds (32 seconds).
The following topics identify the buttons, icons, and badges used in Cisco Prime Network Vision (Prime
Network Vision) and Cisco Prime Network Events (Prime Network Events):
• Icons, page A-1
• Links, page A-8
• Severity Icons, page A-11
• Buttons, page A-12
• Badges, page A-17
Icons
The following topics describe the icons used in Prime Network Vision:
• Network Element Icons, page A-2
• Business Element Icons, page A-4
• Logical Inventory Icons, page A-6
• Physical Inventory Icons, page A-8
ATM switch
Cloud
ICMP device
PC
Printer
WiFi element
Business IP interface
EFP cross-connect
Ethernet service
Network LSP
Network pseudowire
Network TP tunnel
Protected LSP
Pseudowire edge
Site
Subnet
Switching entity
Virtual router
VPLS forward
VPLS instance
VPN
Working LSP
Cross-VRF
Encapsulation
Label switching
Logical inventory
Icon Device
Chassis
Shelf
Slot/Subslot
Port/Logical Port
Unmanaged Port
Links
The following sections describe link icons and characteristics:
• Link Icons, page A-8
• Link Colors, page A-9
• Link Characteristics, page A-10
Link Icons
Table A-5 identifies the available link types and their representation in Prime Network Vision.
Ethernet Pseudowire
IP VLAN
MPLS
Link Colors
Table A-6 Link Colors and Severity
Link Characteristics
Table A-7 Link Characteristics
Example Description
Solid Line vs. Dashed Line
Solid line—Physical, topological, or service link,
such as a link between two devices.
Link Widths
Normal—Contains links of the same group.
Available groups are:
• Business
• GRE
• MPLS-TP
• Pseudowire
• VLAN
• All others
Wide—Aggregated links that contain links of
different groups.
When viewing a map at a low zoom level,
aggregated links cannot be distinguished in the
GUI.
Tunnel—The center color represents the severity
of any alarms on the link.
Severity Icons
Table A-8 identifies the severity icons used in Prime Network Events and Prime Network Vision.
The icons and colors are used as follows:
• The icons are used to indicate the severity of alarms in Prime Network Events and tickets in the
Prime Network Vision ticket pane.
• The icons are used as badges in Prime Network Vision maps to indicate the highest severity alarm
that is not acknowledged for the associated network element.
• The colors are used with network elements in Prime Network Vision to indicate the severity of the
highest uncleared ticket on the element.
• The colors are used with links in Prime Network Vision to indicate the severity of the alarm on the
link. For more information, see Link Colors, page A-9.
Orange Major
Yellow Minor
Buttons
The following topics describe the buttons used in Prime Network Vision:
• Prime Network Vision Buttons, page A-12
• Table Buttons, page A-15
• Link Filtering Buttons, page A-15
• Prime Network Events Buttons, page A-16
• Ticket Properties Buttons, page A-16
• Report Manager Buttons, page A-17
Button Function
Map Options
Creates a new map in the database.
Opens a map saved in the database using the Open dialog box.
Adds a network element to the map or to the subnetwork selected in the navigation pane
and displayed in the content pane.
Saves the current map (the background and the location of devices) to the database.
Viewing Options
Displays the map view in the Prime Network Vision content pane (the button toggles when
selected or deselected).
Displays the list view in the Prime Network Vision content pane (the button toggles when
selected or deselected).
Displays the links view in the Prime Network Vision content pane (the button toggles
when selected or deselected).
Button Function
Overlay Tools
Chooses and displays an overlay of a specific type on top of the elements displayed in the
content pane in the map view.
When an overlay is selected, all the elements and links that are part of the overlay are
colored, and those that are not part of the overlay are dimmed.
Displays or hides a previously defined overlay of a specific type on top of the elements
displayed in the content pane in map view.
Navigation Tools
Moves up a level in the navigation pane and map pane to enable you to view different
information.
Opens the Link Filter dialog box, enabling you to display or hide different types of links
in the map and links views.
If a link filter is applied to the map, the Link Filter Applied button is displayed instead.
Indicates a link filter is currently applied to the map and opens the Link Filter dialog box
so you can remove or modify the existing link filter.
If no link filter is applied to the map, the Link Filter button is displayed instead.
Search Tools
Finds the previous instance of the search string entered in the Find in Map dialog box.
Opens the Find in Map dialog box, enabling you to find a device or aggregation in the map
by its name or IP address.
Finds the next instance of the search string entered in the Find in Map dialog box.
Opens the Find Business Tag dialog box, enabling you to find and detach a business tag
according to a name, key, or type.
Button Function
Map Zoom and Layout Tools
Defines the way in which the NES are arranged in the Prime Network Vision map view:
circular, hierarchical, orthogonal, or symmetric.
Activates the zoom selection mode, which enables you to select an area in the map pane to
zoom in on by clicking and dragging.
Activates the pan mode, which enables you to move around in the map pane by clicking
and dragging.
Opens the Print dialog box so you can print the displayed network or map to the required
printer.
Table Buttons
Table A-10 Table Buttons
Show All Rows Displays all table rows that meet the current filtering
criteria.
Show Only Selected Displays only the rows that you select.
Rows
Deep Links Displays the links for the current aggregation where both endpoints are
within the currently selected context.
Button Function
Displays the previous page of events in the Prime Network Events window.
Displays the next page of events in the Prime Network Events window.
Refreshes the events displayed in the log by querying the database. If a filter is active, the
refresh is done according to the filter. The log returns to the beginning of the list,
displaying the events in ascending or descending order depending on the order of the
current list. Descending order means that the last event is displayed first.
Displays the Prime Network Events Filter dialog box, which enables you to define a filter
for the events displayed in the Prime Network Events log.
Toggles automatic refresh of event data on and off. You define the refresh-time period (in
seconds) in the Prime Network Events Options dialog box. The default is 60 seconds. If
a filter is active, the refresh is done according to the filter.
Displays the properties of the selected event or ticket in the Properties pane.
Icon Description
Refreshes the information displayed in the Ticket Properties dialog box.
Acknowledges that the ticket is being handled. The status of the ticket is displayed
as true in the ticket pane and in the Ticket Properties dialog box.
If a ticket was acknowledged, and some events were correlated to it afterward, then
the ticket is considered to have not been acknowledged.
This button is enabled only if the ticket is not acknowledged.
Requests the relevant Prime Network system to remove the faulty network element
from the Prime Network Vision networking inventory. In addition, it sets the ticket
to Cleared severity or status (the icon is displayed in green) and automatically
changes the acknowledged status of the ticket to true.
This button is enabled only if the severity of the alarm is higher than Cleared or
Normal.
Saves the notes for the selected ticket.
This button is enabled only when text is entered in the Notes field of the Notes tab.
Badges
Badges are small icons that appear with other network elements, such as element icons or links.
The following topics describe the badges used by Prime Network Vision and Prime Network Events:
• VNE Communication State Badges, page A-18
• VNE Investigation State Badges, page A-18
• Network Element Technology-Related Badges, page A-20
Device Unreachable The connection between the VNE and the device id down because all of the protocols
are down (though the device might be sending traps or syslogs).
None Tracking Disabled The reachability detection process is not enabled for any of the protocols used by the
VNE. The VNE will not perform reachability tests nor will Prime Network generate
reachability-related events. In some cases this is desirable; for example, tracking for
Cloud VNEs should be disabled because Cloud VNEs represent unmanaged network
segments.
Icon Description
Access gateway
Blocking
Clock service
Multiple links
Reconciliation
REP primary
Redundancy service
STP root
Advanced tab
Numerics
events 8-17
3.6.x tabs, in Prime Network Events 8-12 tickets 9-18
6rd tunnels, viewing properties 17-44 affected elements, finding 9-19
6VPE Affected Elements window 4-28
and IPv6 16-1 affected parties 9-22
IPv6 VPN over MPLS 16-1 accumulating 9-7, 9-23
Affected Parties tab (tickets) 9-14
calculating 9-22
A
finding 9-19
access gateway affected severity, updating over time 9-24
badge 3-8, A-20 Agent Not Loaded, VNE communication state 2-30
viewing properties 12-18 Agent Unreachable, VNE communication state 2-30
accumulating affected parties aggregation, definition 1-1
in an alarm 9-23 aggregations
in the correlation tree 9-23 adding elements to 4-30
acknowledged tickets 9-6 aggregating network elements 4-28
acknowledging tickets 9-19 disaggregating 4-33
activation script, launching 2-44, 2-48, 4-1 renaming 4-32
adding using Chinese characters 4-5
associated VLANs 12-52 viewing thumbnails 4-30
EFP cross-connects 12-73 working with thumbnail views 4-32
Ethernet services 12-102 alarm count, definition 2-26
MPLS-TP tunnels 17-5 alarms
network elements 4-9 badges A-20
pseudowires 12-88 customizing 2-51
unassociated bridges 12-70 definition 1-1
VLANs 12-48 disabling on a port 3-26
VPLS instances 12-76 enabling on a port 3-26
VPNs severities 9-22
existing 17-23 All tab, in Prime Network Events 8-3
new 17-22 application, launching external 2-43, 2-48, 4-1
applying overlays
B
Ethernet service 12-104
MPLS-TP tunnels 17-17 background images for maps 4-17
network clock 18-49 badges
pseudowire 12-100 access gateway 3-8, A-20
VLAN 12-58 alarms 2-28, A-20
VPLS instance 12-77 blocking 3-8, A-20
VPN 17-25 clock service 3-8, A-20
ARP table 17-34 for elements and links 3-8
associated VLANs icons A-17
adding 12-52 lock 3-8, 17-6, A-20
tag manipulations 12-52 management states A-17
viewing multiple links 3-8, A-20
mapping properties 12-54 reconciliation 3-9, 6-8, 12-47, A-20
service links 12-54 redundancy service 3-9, A-20
working with 12-52 REP primary 3-9, A-20
association, definition 1-2 REP primary blocking 3-9, A-20
ATM cross-connects STP root 3-9, A-20
in logical and physical inventory 18-6 technology related A-20
overview 18-6 tickets A-20
properties 18-7 VNE communication states A-18
viewing 18-6 VNE investigation states A-18
audience, intended xvii VNE management states 2-28
audio options, customizing 2-51 BFD
Audit tab viewing BFD session properties 17-45
events 8-17 viewing MPLS-TP BFD session properties 17-47
in Prime Network Events 8-3 BGP, viewing inventory details 17-43
auto refresh, in Prime Network Events 8-21 Bidirectional Forwarding Detection. See BFD
blocked ports, using with Cisco PathTracer 11-4
blocking badge 3-8, A-20
borders for selected icons 4-14
bridges
understanding unassociated 12-70
viewing properties for VLANs 12-67
business configurations 6-8
business elements
definition 1-2
icons 2-15, A-4
roles required 6-1
defining report types 10-44 Devices with the Most Events report
deleting by severity 10-12
business elements 6-8 by type 10-12
maps 4-25 Devices with the Most Syslogs report 10-12
report folders 10-46 Devices with the Most Traps report 10-12
reports 10-42 Device Unreachable, VNE communication state 2-30
Dense Wavelength Division Multiplexing. See DWDM device view pane
destination, for Cisco PathTracer 11-11 in the Prime Network Vision inventory window 3-16
Detailed Audit Events report 10-17 toolbar 3-17
Detailed Provisioning Events report 10-17 disaggregating aggregations 4-33
Detailed Security Events report 10-17 Discovering, VNE investigation state 2-31
Detailed Service Events report 10-15 discovery
Detailed Syslogs report 10-16 based on Link OAM 15-13
Detailed System Events report 10-17 EFD 12-42
Detailed Tickets report 10-16 EVC multiplex services 12-102
Detailed Traps report 10-16 MPLS-TP tunnels 17-5
details pane, Cisco PathTracer 11-25 VLAN 12-42
Details tab document
events 8-16 audience xvii
tickets 8-20, 9-12 conventions xx
Device Partially Reachable, VNE communication organization xviii
state 2-30
related documentation xxi
devices
terminology 1-1
adding to maps 4-9
duplication count, definition 2-26
aggregations 4-28
DWDM
CPU usage, checking 4-40
roles required for viewing properties 14-1
finding in maps 4-26
viewing
icons 2-10, A-2
alert and alarm counters 14-9
in maps 4-28
G.709 properties 14-4
pinging 4-41
ODU alarm properties 14-7
removing from map 4-15
ODU alert properties 14-8
renaming aggregations 4-32
OTU alarm properties 14-7
resizing in maps 4-14
OTU alert properties 14-8
severity indicator 2-27
performance monitoring configuration 14-10
status indicators 2-26
properties 14-2
Telnet to a device 4-41
viewing
operating system information 3-33
properties 3-5
element icons, and information displayed 3-3 EVC multiplex services, discovery 12-102
elements, viewing operating system information 3-33 event history size, customizing 2-51
overlays overview
applying to ATM cross-connects 18-6
Ethernet services 12-104 CFM 15-3
maps 4-34 Cisco PathTracer 1-6, 11-1
MPLS-TP tunnels 17-17 EFP cross-connects 12-72
network clocks 18-49 EFPs 12-44
pseudowire 12-100 Ethernet LMI 15-9
VLANs 12-58 Ethernet OAM 15-2
VPLS instances 12-77 Link OAM 15-13
VPNs 17-25 MPLS-TP tunnels 17-4
displaying and hiding network clocking service 18-35
for VLANs 12-59 Prime Network Command Builder 1-6
for VPNs 17-26 Prime Network Events 1-7
in maps 4-37 Prime Network Soft Properties Manager 1-6
Ethernet service 12-104 Prime Network Vision 1-4
pseudowire 12-88, 12-100 Prime Network Vision inventory window 3-12
removing 4-37, 12-59 Prime Network Vision maps 2-7
viewing 4-37 PTP service 18-37
pseudowire tunnel links in VPLS 12-79 Report Manager 1-6
REP information 12-60 reports 10-1
STP information 12-63 SAToP 18-2
VLAN SBC 19-1
adding 12-58 switching entities 12-43
removing 12-59 TDM 18-16
viewing STP link information 12-63 unassociated bridges 12-70
working with 12-42 VLANs 12-43
VPLS overview window 4-19
callouts 12-80
instance 12-77
P
viewing pseudowire tunnel links 12-79
VPN 17-25 Partially Discovered, VNE investigation state 2-31
adding 17-25 parties, accumulating affected 9-7
callouts 17-26 password, changing 2-51
working with 4-26, 4-33 path pane, in Cisco PathTracer 11-18
REP events
icons and badges 12-60 Daily Average and Peak 10-12
viewing Devices with the Most Events by severity 10-12
for VLAN service link properties 12-61 Devices with the Most Events by type 10-12
in VLAN domain views 12-60 Devices with the Most Syslogs 10-12
in VLAN overlays 12-60 Devices with the Most Traps 10-12
report categories 10-11 Event Reduction Statistics 10-13
report folders Fault Database vs. Event Archive Statistics 10-13
creating 10-45 Mean Time to Repair 10-13
deleting 10-46 Most Common Daily Events 10-14
moving 10-45 Most Common Syslogs 10-14
renaming 10-46 Syslog Count by device 10-14
viewing properties 10-47 Syslog Count by type 10-14
working with 10-44 Syslog Trend by severity 10-14
Report Manager fail to generate 10-22
content pane 10-7 formats 10-38
events reports 10-11 generating 10-21
generating reports 10-22 events reports 10-22
inventory reports 10-18 inventory reports 10-30
menu options 10-6 network service reports 10-32
navigation tree 10-7 generating from
network service reports 10-19 Prime Network Vision 10-37
overview 1-6 Report Manager 10-22
report categories 10-11 Reports menu 10-36
right-click options 10-9 inventory
roles required 10-1 IOS-XR Software Package Summary 10-18
toolbar buttons 10-6, A-17 Software Version Summary by device 10-18
using 10-4 Software Version Summary by version 10-18
report properties, viewing 10-42 limiting access to 10-41
reports managing
and database load 10-22 maximum concurrent reports 10-38
canceled 10-22 options 10-37
creating folders 10-45 maximum number of concurrent reports 10-38
defining types 10-44 moving
deleting folders 10-45
folders 10-46 reports between folders 10-41
reports 10-42
finding toolbars
affected elements in map 4-27 Cisco PathTracer 11-17
affected elements using the ticket pane 9-19 Cisco PathTracer details window 11-23
generated 9-6 device view pane 3-17
icons 2-32 Prime Network Events 7-7
managing 9-19 Prime Network Vision 2-32, 2-54
propagating new 2-27 Prime Network Vision list view 2-20, 2-54
properties 9-10 Report Manager 10-6
removing 9-20 Ticket Properties window 9-11
removing filters 8-24 tooltips for links 5-6
right-click menu 2-50 Tracking Disabled, VNE communication state 2-30
roles required 9-1 Trap tab (events) 8-18
status 9-5
viewing
U
in Prime Network Events 8-2
in Prime Network Vision 9-4 unassociated bridges
properties 9-11 adding 12-70
working with in Prime Network Vision 9-1 overview 12-70
Tickets tab understanding
inventory window 3-18 EFP severity and ticket badges 12-36
link properties window 5-12 static and dynamic links 5-3
Prime Network Events 8-8 unassociated bridges 12-70
Time Division Multiplexing. See TDM or MToP TDM VLAN and EFD discovery 12-42
toolbar buttons ungrouping aggregations 4-33
Cisco PathTracer single-path window 11-17 unmanaged network, definition 1-3
for filtering links A-15 Unsupported, VNE investigation state 2-30
for tables 2-54, A-15 updating
Prime Network Vision list view A-15 affected severity 9-24
Report Manager 10-6, A-17 VNE information 3-12
Ticket Properties window 9-11 Up ticket 9-7
VPLS report
W
detailed 10-21
options 10-35 Working and Protected LSPs 17-5
summary 10-21 working with
VPNs associated VLANs 12-52
adding to maps 17-23 business elements 6-1
and virtual routers 17-24 business tags 6-1
creating 17-22 EFP cross-connects 12-72
definition 1-3 Ethernet services 12-101
managing 17-22 H-VPLS 12-75
moving virtual routers between 17-24 inventory tabs 2-7
overlays 17-25 links, user roles required 5-1
callouts 17-26 MPLS-TP tunnels 17-4
creating 17-25 overlays 4-33
displaying 17-26 Prime Network Events 8-14
hiding 17-26 pseudowire overlays 12-88
properties, viewing 17-27 pseudowires 12-88
removing from maps 17-24 tickets in Prime Network Vision 9-1
sites 17-28 VLAN overlays 12-42
viewing in maps 17-19 VLANs 12-42
virtual routers 17-28 VPLS 12-75
VRFs
cross-VRF routing entries 17-48
Z
tables
egress 17-31 zooming in and out of maps 4-15
ingress 17-31
viewing properties 17-28
with IPv4 and IPv6 addresses 16-6
VSI, viewing properties 12-83
VTP Domains inventory tab 2-6