Cisco Prime Nerk 43 User Guide

							  
12-17
Cisco Prime Network 4.3.2 User Guide
Chapter 12      Viewing All Event Types in Prime Network
  Viewing Tickets
Viewing Tickets
The Events and Vision client display the same ticket information, and the same operations can be 
performed from both clients. However, if you want to view archived tickets, use the Events client filters. 
See Viewing Non-Network Events (Audit, Provisioning, System and Security Events), page 12-17. To 
view Resync service alarm ticket information, see the topic Viewing Resync Alarm Details in Prime 
Network, page 11-5
Refer to Managing Tickets with the Vision Client, page 11-1 for complete information on how to find 
and manage tickets.
Viewing Non-Network Events (Audit, Provisioning, System and 
Security Events)
Audit Events (Executed Commands)
Audit events provide information about configuration commands that are executed on the Prime Network 
gateway. This can include NE right-click commands, CCM and Compliance Audit operations, and so 
forth. For example, if a CCM user activated an IOS-XR image, the Events client would display an event 
Activation was executed by user on the device device for the image image.
The Provisioning tab provides the results of the command. You would find an associated Provisioning 
event that would list the results (Execution of script !NEIMActivateIOSXRPackage status) along with 
the exact commands sent to and received from the device.
Audit events also provide the following information, which you can also use as criteria for an Audit event 
filter:
When you double-click the event, Prime Network displays the commands that were sent from Prime 
Network to the device.
If you are looking for specific Audit events, use the Events filters. You can search for events based on 
the originating IP address, strings included (or not included) in the command name, signature, or 
parameters, and other common filter criteria (severity, description, and so forth). Once you create the 
filter, you can search for recent events or all events that are stored in the Oracle database. To create a 
filter, see Creating and Saving Filters for Tickets and Events, page 12-6. Field Description
Command Name Audit-specific command name, such as CCM_Config_Restore for a CCM 
restore operation
Command Signature Arguments used to create the command (often left blank).
Command Parameters Command parameters issued with the command, such as 
CONFIG-DEPLOY for the CCM restore operation
Originating IP IP address of the client that issued the command (127.0.0.1 is the gateway) 
						

							  
12-18
Cisco Prime Network 4.3.2 User Guide
Chapter 12      Viewing All Event Types in Prime Network
  Viewing Non-Network Events (Audit, Provisioning, System and Security Events)
Provisioning Events (Device Configuration Results)
Provisioning events display the results of device configuration operations. For example, if a Vision client 
user right-clicks an NE and chooses Commands  > Show > Users (Telnet sessions), the Provisioning 
tab creates a new event called Execution of script !Device_ShowUser_xr succeeded. The event 
includes the device the command was executed on and the status of the command (Configuring, Success, 
Fail). It also includes this information, which you can use as criteria for a Provisioning event filter:
Provisioning events display the results of operations performed by other Prime Network features such 
as Change and Configuration Management, Command Manager, and Transaction Manager. When you 
double-click the event, Prime Network displays the results returned from the device and the operation 
status.
If you are looking for specific Provisioning events, use the Events filters. You can search for events based 
on location (devices), the Prime or device username, the status (success, fail, configuring, unknown), and 
other common filter criteria (severity, description, and so forth). Once you create the filter, you can 
search for recent events or all events that are stored in the Oracle database. To create a filter, see Creating 
and Saving Filters for Tickets and Events, page 12-6.
Prime Network Security Events
Security events are related to user authentication, session management, and information about who is 
making system changes (disabling and enabling AVMs, adding new VNEs to the system, and so forth). 
An example is User user authenticated successfully. If you double-click the event, you can find out 
which client the user logged into.
If you are looking for specific Security events, use the Events filters. You can search for events based on 
a string that is included (or not included) in the username, the IP address where the event was triggered, 
and other common filter criteria (severity, description, and so forth). Once you create the filter, you can 
search for recent events or all events that are stored in the Oracle database. To create a filter, see Creating 
and Saving Filters for Tickets and Events, page 12-6.
For information on how to respond to specific Security events (including their probable cause), refer to 
Cisco Prime Network Supported System and Security Events. 
Prime Network System Events
System events represent the everyday working of Prime Network and its components. Examples are:
State or reachability changes in Prime Network components
Database events (ticket archiving, disk space, dropped events, synchronization issues)
Unit protection (standby unit) events Field Description
Prime Login 
UsernameUsername of the user that executed the command.
Device Login 
UsernameUsername that was used to access the device. It can be either of the following:
From VNE Login—Username specified when the device was added to Prime 
Network
username—username entered when the user ran the command and was prompted 
for their credentials.  
						

							  
12-19
Cisco Prime Network 4.3.2 User Guide
Chapter 12      Viewing All Event Types in Prime Network
  Viewing Standard Traps and Syslogs Not Recognized by Prime Network
Most System events occur on AVM 11 (the gateway). If an event occurs on device, a hyperlink to the 
device is provided in the event details. For information on how to respond to specific System events 
(including their probable cause), refer to Cisco Prime Network Supported System and Security Events. 
If you are looking for specific System events, use the Events filters. You can search for events based on 
a string that is included (or not included) in the description, specific devices, and other common filter 
criteria (severity, time, and so forth). Once you create the filter, you can search for recent events or all 
events that are stored in the Oracle database. To create a filter, see Creating and Saving Filters for Tickets 
and Events, page 12-6.
Viewing Standard Traps and Syslogs Not Recognized by 
Prime Network
Standard events are events that Prime Network could not match with any of the rules that define events 
of interest. Prime Network does a best effort at extracting information from these syslogs and traps, but 
does not process them for correlation. Standard events are saved to the database and can be viewed in 
the Standard tab. You can also create an event filter for Standard syslog and trap events using the same 
criteria for events displayed in the Syslogs tab and the V1 Trap, V2 Trap, and V3 Trap tabs. See Viewing 
Network Events (Service, Trap, and Syslog Events), page 12-13 for more information. 
Standard events also appear in the Vision client:
In the Latest Events tab in a map view (if enabled from the Administration client)
In the Network Events tab in a device inventory view
Changing How Often Event Information is Refreshed 
By default, the Events client displays event information from the last 2 hours (up to 50 records per table). 
Data is refreshed when you log into the Events client, and when you move between the Events tabs. To 
refresh the data in a table you are viewing, click Refresh Now. You can also enable the auto-refresh 
mechanism which will update the data every 60 seconds. The manual and auto refresh buttons are shown 
below.
The following table shows the default settings for data display and refresh, and how you can adjust them. Button Name Function
Refresh Now Manually refreshes the events list (same as choosing View > Refresh).
Auto Refresh Enables auto refresh of events tables (every 60 seconds). Filters remain intact.
NoteBy default, tabular data is not refreshed on an ongoing basis.
To control: Default Setting To change setting:
Updating data when you log into Events 
clientEnabled Switch to Find in Database mode (see 
Creating a New Filter and Saving It, 
page 12-7)
Updating events data whenever you move 
between Events tabs (“Find” mode)Enabled Choose Tools > Options 
						

							  
12-20
Cisco Prime Network 4.3.2 User Guide
Chapter 12      Viewing All Event Types in Prime Network
  Exporting Events Data
Exporting Events Data
When you export data, it is saved as a CSV file. Prime Network will export all of the data listed in the 
table, up to the number of records specified in the Events client Options dialog. You can check the setting 
by choosing Tools > Options from the main menu.
To export an Events table to a CSV file:
Step 1Choose File > Export.
Step 2Browse to the directory where you want to save the file and enter a name for the file.
Step 3Click Save. The displayed records are saved in a CSV file.
Changing the Events Client Defaults
Events client users can change their default settings. This includes:
Saving filters and using them by default when you open Events
How many records to display in the Events client
How many records can be exported at one time
How often data should be refreshed
The age of data to display
Enabling manual event retrieval (so that events are not retrieved immediately when you first log in 
or when you switch between tabs)
To change these settings, see Setting Up Your Events View, page 6-4. Updating the displayed data:
On an ongoing basis, and Disabled Click Au t o  Re fresh
At a specific interval 60 seconds Choose Tools > Options
How much data to display in the events 
tables (age and number of records per page)2hours
50 recordsChoose Tools > Options
NoteIncreasing the interval beyond 
2 hours can adversely affect 
the display performance. To control: Default Setting To change setting: 
						

							CH A P T E R
  
13-1
Cisco Prime Network 4.3.2 User Guide
13
Finding Available Network Paths Using 
PathTracer
Cisco PathTracer uses Prime Network’s inner logic to show available paths between two network 
elements. It creates a virtual path, without modifying any real network elements, and shows all devices 
and components the path flows through, including performance data. 
The following topics describe Cisco PathTracer and how to use it: 
Cisco PathTracer, page 13-1
Launching Path Tracer, page 13-2
Viewing Path Traces, page 13-12
Saving and Opening Cisco PathTracer Map Files, page 13-17
Saving Cisco PathTracer Counter Values, page 13-17
Rerunning a Path and Comparing Results, page 13-18
Viewing Q-in-Q Path Information, page 13-18
Viewing L2TP Path Information, page 13-19
Using Cisco PathTracer in MPLS Networks, page 13-20
Cisco PathTracer
Cisco PathTracer enables you to launch end-to-end route traces and view related performance 
information for Layer 1, Layer 2, and Layer 3 traffic. Upon receiving a paths start and endpoint, 
Cisco PathTracer visually traces the route through the network. For example, in an ATM network 
environment, Cisco PathTracer identifies all information regarding the connection of a subscriber to a 
provider, including all ATM PVCs, ATM switching tables, ATM class of service (CoS) definitions, 
IP-related information, and so on. 
You can also use Cisco PathTracer to: 
Trace paths using IPv4, IPv6, or both IPv4 and IPv6 addresses for the source and destination.
Trace a hypothetical Ethernet frame from a VLAN interface to a specified MAC address.
Trace a hypothetical Ethernet frame from an Ethernet interface to a specified MAC address within 
a specific VLAN identifier. 
						

							  
13-2
Cisco Prime Network 4.3.2 User Guide
Chapter 13      Finding Available Network Paths Using PathTracer
  Launching Path Tracer
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—CiscoPathTracer 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.
Launching Path Tracer 
Cisco PathTracer can be launched from a bridge, switching entity, Ethernet interface, Ethernet flow 
point, VLAN interface, ATM VC, DLCI, or IP interface entry point. Ethernet flow points can be starting 
points whether they are associated with an interface, bridge, or LAG. 
The virtual route is found according to the cross connect table of each ATM switch or Frame Relay 
device. The IP routing and path-finding process is enabled according to the VRF tables of each router, 
and the Ethernet-simulated path is found according to the various Layer 2 forwarding tables, such as 
bridges or VSIs. 
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.  
						

							  
13-3
Cisco Prime Network 4.3.2 User Guide
Chapter 13      Finding Available Network Paths Using PathTracer
  Launching Path Tracer
NoteA path can also be launched if a business tag attached to an endpoint that can be used as the starting 
point.
Path Traces and Blocked Ports
The following conditions apply for blocked ports: 
You can launch a path trace from a blocked port. This action is equivalent to launching a path trace 
from a bridge.
You can specify a blocked port as a destination. 
If Cisco PathTracer encounters a blocked port in its path to the destination, the path trace stops. Path 
traces do not traverse blocked ports. 
Table 13-1 identifies the available path trace launching points and their locations within the Vision 
client. Cisco PathTracer is available in each location as a right-click menu option. 
Supported Launch Points for Cisco PathTracer
Cisco PathTracer is launched by using right-click menu options. Table 13-1 identifies the launching 
points for the different types of elements. 
Ta b l e 1 3 - 1 C i s c o P a t h Tr a c e r  Right-Click Menu Options
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
Pseudowire endpoint
Map view or navigation pane
Inventory window
Site Map view
Switching entity Map view 
						

							  
13-4
Cisco Prime Network 4.3.2 User Guide
Chapter 13      Finding Available Network Paths Using PathTracer
  Launching Path Tracer
Starting a Path Trace
To start a path trace:
Step 1Start the path trace in one of the following ways:
NoteIf 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 address, an IPv6 address, or both IPv4 and IPv6 addresses. For an example, see 
Figure 13-3. Virtual connection Inventory window:
Cross Connect window
VC Table window
VLAN
Navigation pane
Map view
Table 13-1 Cisco PathTracer Right-Click Menu Options (continued)
Element Location
Launch Point Steps
VLAN (from 
map view)
1.Double-click a VLAN to view its entities. 
2.Right-click the required item and choose PathTracer > From Here to 
Destination or PathTracer > Start Here.
VPN (from 
map view)
1.Double-click the VPN to view its entities.
2.Right-click the site and choose PathTracer > From Here to Destination or 
PathTracer > Start Here.
Ethernet Flow 
Point (from 
map view)
1.Choose Network Inventory > Ethernet Flow Domains.
2.In the Ethernet Flow Domain List Properties window, double-click the required 
domain. 
3.In the Ethernet Flow Domain Properties window, right-click the required element 
and choose PathTracer > From Here to Destination or PathTracer > Start 
Here.
NE physical or 
logical 
inventory
1.Right-click one of the following:
–IP interface
–MPLS-TP tunnel endpoint
–Port
–Pseudowire endpoint
–VLAN bridge
2.Choose PathTracer > From Here to Destination or PathTracer > Start Here. 
						

							  
13-5
Cisco Prime Network 4.3.2 User Guide
Chapter 13      Finding Available Network Paths Using PathTracer
  Launching Path Tracer
Step 2If you choose PathTracer > From Here to Destination, complete the Path Information dialog box 
(Figure 13-1). 
Figure 13-1 Path Information Dialog Box 
a.
In the Path Information dialog box, enter the required information. The contents depend on your 
launch point.
b.Click OK. 
Step 3If 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 4To view additional details regarding the path traces, select one or more paths in the paths pane. 
Step 5In the toolbar, click Cisco PathTracer. 
If you select one or more paths in the paths pane, each selected path is displayed in its own window 
with the Layer 1, Layer 2, Layer 3, and Business Tag tabs.
If you select nothing in the Paths pane, each path found is displayed in its own window with the 
Layer 1, Layer 2, Layer 3, and Business Tag tabs.
For more information about the end-to-end path and networking layer details, see Saving and Opening 
Cisco PathTracer Map Files, page 13-17.
Field Description
Destination IP Specify an IPv4 or IPv6 address.
Destination MAC MAC address
VLAN ID Enter the VLAN identifier (For example, VLAN id 1-4094)
.
Inner VLAN ID Inner VLAN identifier
Stop trace after Check this check box to enter a maximum of hops that Cisco PathTracer makes 
in its attempt to reach the destination 
						

							  
13-6
Cisco Prime Network 4.3.2 User Guide
Chapter 13      Finding Available Network Paths Using PathTracer
  Launching Path Tracer
Examples of Launching Cisco PathTracer 
The following topics provide examples for launching Cisco PathTracer from different locations in the 
Vision client: 
Using an Ethernet Flow Point, page 13-6
Using an IP Interface, page 13-7
Using a VLAN Bridge, page 13-8
Using an Ethernet Port, page 13-9
Using a Pseudowire, page 13-10
Using an MPLS-TP Tunnel Endpoint, page 13-11
Using an Ethernet Flow Point
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 1In the Vision client navigation pane or map pane, expand the required network VLAN. 
Step 2In 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 13-2. 
Figure 13-2 Ethernet Flow Point Path Trace Launch Point