Table Of Contents
Cisco WAN Manager Fault Management Tools
Understanding Fault Management Functions for Network Topology
Navigating with Network Browser
Network Browser Menus and Toolbar
Managing Node and Trunk Filters
Filtering Routing Nodes and Feeder Nodes
Filtering Routing Trunks and Feeder Trunks
Verifying CUG Security Privileges
Displaying a CUG Session for a Node
Displaying a CUG Session for All Nodes in a Network
Displaying a CUG Session for All Managed CWM Nodes
Managing Fault Management with CiscoView
Launching the Real-Time Monitor in CiscoView
Understanding the LED Color Display
Understanding Fault Management Functions for Connection Manager
Testing AutoRoute Connections (PVCs)
Testing PNNI Connections (SPVCs)
Assigning the Category for an Event
Configuring Events and Categories
Navigating with Event Configuration
Performing Additional Actions on Events
Monitoring Network Faults
This chapter describes the tools used to identify network faults, isolate the cause of the fault, and correct the fault if possible. Fault management enables the network administrator to avoid catastrophic conditions through alarms and early warnings. The primary basis for fault management is provided by real-time messages that are generated by network elements when a change in status occurs.
Contents of this chapter include:
•
Cisco WAN Manager Fault Management Tools
•
•
•
•
Cisco WAN Manager Fault Management Tools
This section describes the fault management tools for Cisco WAN Manager (CWM).
Table 5-1 describes the applications that are used for fault management tools.
Table 5-1 Fault Management Tools
Network Topology
Discovers and displays AutoRoute and PNNI topology and indicates the operational status of nodes and trunks with multicolor icons and lines. In addition, HP OpenView topology manager can discover layer three connectivity.
For more information, see the "Understanding Fault Management Functions for Network Topology" section.
Network Browser
Provides a hierarchical view of the network structure, which is principally intended to facilitate inventory management of network resources. Network Browser provides a color-coded visual indication of the status of every network component.
For more information, see the "Managing with Network Browser" section.
Device Management with CiscoView
Provides a graphical view of equipment status for the operational and alarm status of each card, port, line, or trunk that is represented with a predefined color. CiscoView can also generate real-time displays of element performance and utilization using system counters repeatedly polled with SNMP, and facilitates the monitoring of activity and error rates of individual ports, lines, and trunks.
For more information, see the "Managing Fault Management with CiscoView" section.
Connection Manager
Includes diagnostic capabilities that allow individual connections to include AutoRoute, PVC, XPVC, and PNNI SPVC. The connections are verified for integrity and round-trip delay. Connection Manager also includes a call-tracing function for PNNI SPVCs.
For more information, see the "Understanding Fault Management Functions for Connection Manager" section.
Event Browser
Receives, stores, and sorts SNMP traps and alarms sent by a network node. Every network event generates a trap or alarm that is recorded by CWM and accessible through the Event Browser.
Note
For more information, see the "Managing with Event Browser" section.
Understanding Fault Management Functions for Network Topology
CWM automatically discovers network elements and displays a topology map of nodes interconnected by trunks and real-time status. Integrated, AutoRoute, Standalone, and PNNI topologies are discovered. Cisco SES PNNI controllers are visible in the topology as feeder shelves.
Multicolor displays are updated in real-time in response to events occurring in the network. Icons representing network nodes change color to reflect the status of the node, which allows rapid recognition of network faults as they occur. The network topology is configured to produce an audible alarm signal at the CWM station in the event of a major alarm in the network. To facilitate network management and enhance fault recognition, network topology allows control over the visual presentation of the map, and selective display of network elements based on grouping and other filtering mechanisms.
Table 5-2 describes the colors that are used to display alarm situations detected by the Network Topology.
Managing with Network Browser
The Network Browser application provides a hierarchical representation of network elements, which include networks, nodes, cards, lines and ports, displayed in tree format in the left panel of the Network Browser's main window. Associated information about a selected network element is displayed in table format in the right panel of the Network Browser window.
Each network element managed by CWM has its own attributes and fits into the network's physical or logical hierarchy. In Release 12 of CWM, the Network Browser presents the network elements that are discovered, managed, and controlled in a hierarchical view for all networks populated in the tables by CWM processes.
The Network Browser displays the network elements in a hierarchical format based on either a physical or logical relationship among the various network elements. Networks are displayed at the root level of the component tree, nodes, and trunks are displayed beneath the networks in a parent/child relationship.
The Network Browser also displays informational messages in a multiline text display; other types of messages can be displayed in response to user actions.
The following tasks are used with the network browser:
•
•
•
•
Launching the Network Browser
To launch the Network Browser application, choose Apps > Network Browser or click the
Network Browser icon from the toolbar.After launching Network Browser for the first time, you see a root node called Browser in the left panel of the window, and discovered networks in the right panel of the window in table format.
You can further extend the tabular display down to the node, card, line, or port level by repeatedly expanding the hierarchical table display.
Figure 5-1 shows the Network Browser main window.
Figure 5-1 Network Browser Main Window
Note
Navigating with Network Browser
The following sections describe the navigation of network browser:
•
Network Browser Main Window
The Network Browser main window (see Figure 5-1) includes five options (see Table 5-3).
Table 5-3 Network Browser Main Window Options
Menu bar
For a definition, see Table 5-4.
Toolbar
For a definition, see Table 5-5.
Browser
Retrieves network level information for all networks that you defined when installing CWM. You can further extend the tabular display down to the node, card, trunk, and line level table by repeatedly expanding the hierarchical table display.
The following browser functions are:
•
The NW IP flag is not applicable to PNNI nodes.
•
•
•
•
•
•
•
•
Networks
Displays the selected network element.
Tabs
Displays the following tabs for the applicable browser option.
Routing Nodes
Status
Includes node number, node name, alarm, management, synchronization, and SNMP-Get Failures.
Version
Displays additional information about the selected node that includes the node number, node name, LAN IP address, and network IP address.
All
Displays all routing node categories.
Card Level
Type
Includes the following card type information:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
This is the default tab.
Revision
Displays information about the card slot and card name, front card hardware revision, front card firmware revision, back card hardware revision, back card firmware revision, second back card hardware revision, and second back card firmware revision.
Redundancy Info
Displays information about the card slot and card name, primary card type and slot, primary card status, secondary card type and slot, secondary card status, and covered slot and redundancy type.
All
Displays all card categories.
Line Level
Configuration
Includes line number, admin state, interface, trunk, virtual trunk, and APS flag.
Note
This is the default tab.
Status
Displays additional information about the selected line including line number, interface, and alarm status.
Misc
Displays additional information about the selected line including line number, interface, and miscellaneous comments.
All
Displays all line categories.
Port Level
Properties
Displays information about the slot.port, administrative state, port speed, and whether the port is XLMI enabled.
This is the default tab.
RscPrtn
Displays information about the selected port that includes the slot.port, part ID, Ctlr type, egress and ingress guaranteed and maximum bandwidths, minimum and maximum vpi and vci, minimum and maximum connections and channels, and ingress and egress percent bandwidth.
Status
Displays information about the selected port that includes slot.port and port status.
Misc
Displays information about the selected port that includes slot.port and miscellaneous status.
All
Displays all port categories.
Feeder Nodes
Status
Displays information about the node number, node name, alarm status, SNMP-Get Failure status, and synchronization status.
This is the default tab.
Version
Displays information about the node number, node name, node type, revision, and protocol.
Address
Displays information about the node number, node name, LAN IP address, and NW IP address.
All
Displays all feeder node categories.
Feeder Trunks
Status
Displays information about the node.slot.port [vtrk.id] information, alarm status, and PNNI link status.
This is the default tab.
General
Displays information about the selected feeder trunk that includes the interface type, line load, statistical reserve, and protocol information.
Line
Displays information about the selected feeder trunk that includes both the local and remote physical line numbers.
All
Displays all feeder trunk categories.
Access Nodes
Status
Displays information about the node number, node name, alarm status, management status, and synchronization status.
This is the default tab.
Version
Displays information about the selected access node that includes the node number, node name, node type, revision, and protocol.
Address
Displays information about the selected access node that includes the node number, node name, LAN IP address, and NW IP address.
All
Displays all access node categories.
Routing Trunks
Status
Displays information about the node.slot.port [vtrk.id] information, alarm status, and PNNI link status.
This is the default tab.
General
Displays information about the selected routing trunk that includes interface type, line load, statistical reserve, and protocol information.
Line
Displays information about the selected routing trunk that includes local and remote physical line numbers.
All
Displays all routing trunk categories.
1 APS = automatic protection switching
Network Browser Menus and Toolbar
The menu bar provides available menu options for the network browser application.
The options and functions are listed in Table 5-4.
Table 5-4 Network Browser Menu Bar
Exit
Exits the network browser.
Show Node
Displays the Node View window to enter the node name.
Set Fonts
Sets the fonts to be displayed.
Set Colors
Sets the colors to be displayed.
Refresh All
Refreshes the current display.
Show All CUG1 s
Displays the Closed User Group window (see Figure 5-20).
Routing Node
Filters the routing node. Displays the Node Filter window.
Routing Trunk
Filters the routing trunk. Displays the Trunk Filter window.
Feeder Node
Filters the feeder node. Displays the Node Filter window.
Feeder Trunk
Filters the feeder trunk. Displays the Trunk Filter window.
CiscoView
Launches CiscoView. For configuration information, see "Managing Devices." For fault management information, see the "Managing Fault Management with CiscoView" section.
Detects and displays hardware failures at the card, interface, port, line, and trunk level. CiscoView supports fault management by displaying port activity and port error rates, which can signal an impending port failure.
Running Bert
Displays the Monitored BERT2 window.
Bert Test
Displays the BERT test.
About
Provides information about the network browser.
Icon
Describes the help icons that are used in the network browser.
The following icons are
•
•
•
•
•
•
1 CUG = closed user group
2 BERT = bit error rate test
The toolbar contains buttons that are used frequently (see Table 5-5). Move the pointer over a button to display the feature.
Table 5-5 Network Browser Toolbar Buttons
Show Node
For a definition, see Table 5-4.
Filter Routing Nodes
Displays the Node Filter window to filter the applicable node.
Filter Routing Trunks
Displays the Trunk Filter window to filter the applicable trunk.
Filter Feeder Nodes
Displays the Node Filter window to filter the applicable feeder node.
Filter Feeder Trunks
Displays the Trunk Filter window to filter the applicable feeder trunk.
Help
For a Help definition, see Table 5-4.
Displaying Nodes
To display a node, complete the following procedure:
Step 1
The Node View window (see Figure 5-2) is displayed.
Figure 5-2 Node View Window
Step 2
Click OK.
The node name is highlighted and the corresponding details appear in the network browser main window (see Figure 5-3).
Figure 5-3 Routing Node Level Table
.
Displaying Cards and Lines
From the Browser, the card level table (see Figure 5-4) is one level below the node level, and is accessed by expanding one of the routing nodes. At the same level as the card level are displays for the feeder, access nodes, and feeder trunks. For tab definitions, see Table 5-3.
Note
Figure 5-4 Card Level Table
For information about supported cards and platforms, see Table 4-2 of "Managing Connections."
By selecting and expanding a card, you can display a line level table.
Displaying Trunks
The routing trunks level provides an information table (see Figure 5-5) for all ports on a routing node that are configured as physical or virtual trunks. For tab definitions, see Table 5-3.
In a large network with many trunks, you can use filtering to limit the display to trunks or a particular type, or to trunks with the same alarm status. For more information about filtering trunks, see the "Filtering Routing Trunks and Feeder Trunks" section.
Figure 5-5 Routing Trunks Level
Displaying XLMI Links
XLMI is a Cisco proprietary extension of the Local Management Interface (LMI) Protocol used to exchange IP addresses, and to detect the connections associated with a XPVC segment. For more information on XPVC, see "Managing Connections," "Managing XPVC Connections" section.
XLMI is a special kind of trunk designed to link AutoRoute (AR) nodes and PNNI nodes.
ILMI status and operation status are queried for each link. If both ILMI status and operation status are up, the link is considered valid for persistent topology.
To display XLMI links, select the applicable XLMI node from the Browser.
Figure 5-6 shows XLMI links that are used in conjunction with the CWM Network Browser.
Figure 5-6 XLMI Links
Managing Node and Trunk Filters
This section describes how to manage node and trunk filters.
The following tasks are
•
•
Table 5-6 lists the information for the node table.
Table 5-7 lists the information for the trunk table.
Note
Filtering Routing Nodes and Feeder Nodes
This section describes how to filter routing nodes and feeder nodes.
Node filtering is defined for any node element in the network, for example, routing nodes and routing trunks, individual card types, or node names beginning with a certain prefix. You can set up filters for all nodes or specify one of the following types:
•
•
•
Node filtering is also defined for all node types with AutoRoute (AR), TAG, PNNI, ILMI, and Standalone, or with all protocols.
To filter routing nodes or feeder nodes, complete the following procedure:
Step 1
Figure 5-7 shows a selected feeder node in the left panel of the window, and its corresponding information displayed in the right panel of the window.
For definitions of the node table, see Table 5-6.
Figure 5-7 Node Filtering
The Node Filter window is displayed (see Figure 5-8).
Figure 5-8 Node Filter - Protocol
Step 2
•
•
•
•
•
Click OK.
Step 3
Figure 5-9 Node Filter - Type
Step 4
Click OK.
Figure 5-10 Node Filter - Synchronized
Click OK.
Filtering Routing Trunks and Feeder Trunks
To filter routing trunks or feeder trunks, complete the following procedure:
Step 1
Figure 5-11 shows a selected feeder trunk in the left panel of the window, and its corresponding information displayed in the right panel of the window.
For definitions of the trunk table, see Table 5-7.
Figure 5-11 Trunk Filtering
The Trunk Filter window is displayed (see Figure 5-12).
Figure 5-12 Trunk Filter - Alarm
Step 2
Click OK.
Step 3
•
•
•
•
•
Click OK.
Figure 5-13 Trunk Filter - Type
Managing Bit Error Rate Tests
This section describes the configuration and operation of the Bit Error Rate Test (BERT).
The following contents include:
BERT Overview
BERT verifies the integrity of a network element by measuring error statistics that result from sending known bit patterns, analyzing a remote interface, and analyzing the pattern that is returned. BERT is used on DS3, DS1, and DS0/DS0 bundle interfaces.
BERT generates a known data sequence into a transmission device, and examines the received sequence at the same device or a remote device for errors. Tests run on a full T1/E1 line or run on a fractional T1/E1, for example, single DS0 or a group of DS0s. BERT tests the quality of links by directly comparing a pseudo-random or repetitive test pattern with an identical, local generated test pattern.
Note
The following functions are used for BERT:
•
•
•
•
•
•
•
Configuring BERT
You can set up BERT options on the looped back connection and use the available test patterns displayed in the BERT Control window (see Figure 5-14 or Figure 5-15). Before you configure the BERT options from the BERT Control window, ensure a line or port is selected from a BERT-supported service module.
To configure a BERT session, complete the following procedure:
Step 1
Step 2
The AXIS Diagnostics MIB Control window (Cisco MGX 8850 (PXM1) is displayed (see Figure 5-14).
Figure 5-14 AXIS Diagnostics MIB Control Window
The Cisco-BERT-MIB- Control window (Cisco MGX8850 (PXM1E) is displayed (see Figure 5-15).
Figure 5-15 Cisco BERT MIB Control Window
Step 3
Table 5-8 describes the BERT options for Cisco MGX 8850 (PXM1).
Table 5-9 describes the BERT options for Cisco MGX 8850 (PXM1E and PXM45).
Step 4
The status shows that BERT is running. Once BERT is started, BERT can be restarted with the modified options.
Stopping BERT
While the BERT session is running, you can stop the session from the BERT Control window (see Figure 5-14 or Figure 5-15) that is applicable to your selected line or port. From the BERT Control window, click Stop to stop the session.
Modifying BERT
To modify a BERT, complete the following procedure:
Step 1
Step 2
Depending upon the selected line or port, the BERT control window is displayed (see Figure 5-14 or Figure 5-15).
Step 3
Displaying BERT
You can view the status of all initiated bit error rate test (BERT) sessions at once.
To display BERT status, complete the following procedure:
Step 1
Step 2
The Monitored BERTs window (see Figure 5-16) is displayed.
Figure 5-16 Monitored BERTs Window
Table 5-10 describes the parameters for the BERT statistics.
Step 3
Click Refresh.
Step 4
Managing Closed User Groups
This section describes the configuration and operation of the closed user group (CUG).
The following contents include:
•
•
•
•
CUG Overview
The PNNI CUG allows network users to form a closed community within a PNNI network. A network user can be associated with one, multiple, or no CUGs. Members of a specific CUG can communicate typically among themselves, but not in general with network users outside of the CUG. Specific network users can have additional restrictions preventing them from originating calls to, or receiving calls from, network users of the same CUG. In addition, a network user is further restricted in originating calls to, or receiving calls from, network users outside of any CUG membership is defined for the network user.
The user within a CUG is actually a UNI ATM end station address (AESA) or an ATM address prefix, and this address or address prefix is assigned to more than one interface on a switch. When an ATM address is assigned to more than one CUG, the CPE that uses that address must specify the CUG for a connection or accept default selection of the preferential CUG.
CUG membership is evaluated only when setting up SVC connections. CUG membership is not evaluated for SPVC or SPVP calls because these connections are already subject to careful configuration by the network administrators.
CUG membership is supported as follows:
•
•
•
•
Note
Verifying CUG Security Privileges
Before you launch a CUG session, security privileges are verified before launching network browser. If you do not have right permissions, all CUG menus are disabled.
If the core processes are not running, network browser is not able to check the user security profile and disables all CUG menus.
If the core processes are running, network browser checks if you have the right to view and configure CUGs. If not, network browser displays another Network Browser-Security Check window.
Exiting a CUG Session
To exit a CUG session, choose File > Exit to close the Closed User Group window and return to the network browser.
CUG Configuration
This section describes the procedures that relate to CUG configuration.
The following procedures include:
Creating CUG
A CUG is established by assigning the same 24 B interlock code to two or more prefixes or AESAs on a PNNI network. All prefixes and addresses that share the same interlock code are considered part of the same CUG and can establish connections amongst themselves, unless these connections are blocked by configuration options.
To select a CUG, the CPE is configured with a CUG index, which is a number that you assign when you assign a prefix or address to a CUG. When a CPE requests a specific CUG during call setup, this is called an explicit CUG request.
To create a CUG or assign a new user to a CUG, complete the following procedure:
Step 1
Step 2
The Add Closed User Group (CUG) window (see Figure 5-17) is displayed.
Figure 5-17 Add Closed User Group Window
For parameter definitions, see Table 5-11.
Step 3
Step 4
One option is to use the ATM address of a network node for the first 20 B and provide a unique 4 B suffix.
Step 5
•
•
•
Step 6
If not successful and the entry is not saved, the following error messages appear:
•
•
•
•
•
•
Modifying CUG
When you are assigned to a CUG, the default configuration initiates the outgoing connections to other CUG members and receives incoming connections from other CUG members. You can disable incoming or outgoing connections to other group members for a specific CUG, or remove restrictions and enable communications with other CUG members.
You can also enable or disable communications between a user and users outside of a CUG.
To modify a CUG assignment, complete the following procedure:
Step 1
Step 2
Figure 5-18 Modify Closed User Group Window
For parameter definitions, see Table 5-11.
Step 3
•
•
•
For outgoing access option definitions, see Table 5-11.
The Outgoing Access option changes the outgoing access configuration to not allow outgoing calls, enable outgoing calls when an outgoing call specifically requests outside access, or permanently enable going connections as if they were CUG membership connections.
Step 4
•
•
For incoming access option definitions, see Table 5-11.
The Incoming Access option changes the incoming access configuration to allow or not allow incoming calls from outside the CUG membership.
Step 5
If the Pref box is checked, you cannot change the Calls Barred to outgoing. If the Pref box is unchecked, all outgoing calls are barred.
Note
Step 6
•
•
•
For calls barred option definitions, see Table 5-11.
Step 7
Deleting a CUG Assignment
A CUG assignment is made when you choose Edit > Add CUG from the Closed User Group window.
Note
To delete a single CUG assignment, complete the following procedure:
Step 1
Step 2
Figure 5-19 CUG Delete Window
Step 3
If the CUG assignment is deleted as a preferential entry, the following message appears:
Can not delete preferential CUG. Use Modify to change the preferential CUG from this entryStep 4
Displaying a CUG Session for a Node
To display a CUG session for a node, right-click on a node and choose Show CUG. The Closed User Group window (see Figure 5-20) is displayed.
Figure 5-20 Closed User Group Window
Each column header in the Closed User Group window can be chosen to sort the data in alphabetical, ascending, or descending order. Table 5-11 lists the parameter definitions.
Table 5-11 Closed User Group
Network
Specifies a network name.
Node
Specifies a node name.
AESA
Specifies the AESA at the UNI interface. For ATM addresses or prefix information, see the "CUG Overview" section.
length
Specifies the length of the ATM address. The range is 0-160.
plan
Specifies the addressing plan for the specified AESA. The address format for the plan is either one NSAP or E.164.
OA
Specifies the following options for outgoing access:
•
•
•
IA
Specifies the following options for incoming access:
•
•
pref
Specifies the CUG index as the preferential index. A CUG entry is not preferential if the entry is provisioned with outgoing calls barred. When the first CUG is added to an interface address, no preferential CUG is assumed.
CUG Index
Specifies the unique ATM address. The range is 1-65535.
CUG Code
Specifies the 24 B CUG lock code. The first 20 B from the administrative AESA, which owns the CUG interlock code followed by the 4 B identifier. The 24 B code is unique across multiple CUG entries associated with the specified ATM address.
Calls Barred
Specifies that incoming or outgoing calls are not allowed. If the outgoing calls are barred, the CUG entry cannot become the preferential entry.
The default is none.
Displaying a CUG Session for All Nodes in a Network
To a CUG session for all nodes in a network, right-click a network and choose Show CUG. The Closed User Group window (see Figure 5-20) is displayed. For parameter definitions, see Table 5-11.
Displaying a CUG Session for All Managed CWM Nodes
To display a CUG session for all managed CWM nodes, complete the following procedure:
Step 1
Step 2
The Closed User Group window (see Figure 5-20) is displayed. For parameter definitions, see Table 5-11.
Managing Fault Management with CiscoView
This section describes how CiscoView is used as a fault management tool.
By periodically polling each network element through SNMP, CiscoView detects and displays hardware failures at the card, interface, port, line, and trunk level. For example, you can observe in quasi-real time that a port failure has occurred, because the color changes on the graphical display. The real-time monitor in CiscoView supports fault management by displaying port activity and port error rates, which can signal an impending port failure.
Note
The following tasks are
•
•
Launching the Real-Time Monitor in CiscoView
To launch the real-time monitor in CiscoView, complete the following procedure:
Step 1
Step 2
Press Return.
Monitoring SONET Lines
To monitor SONET lines on the AXSM card, complete the following procedure:
Step 1
Step 2
Step 3
•
•
•
Step 4
Note
Step 5
Figure 5-21 displays the SONET Section Counters (AXSM Card) Monitor window.
Figure 5-21 Sonet Section Counters (AXSM Card) Monitor Dialog
The SONET Section Counter parameters are described in Table 5-12.
.
Table 5-12 Sonet Section Counters Parameters
Errored Seconds
Displays the number of ES1 encountered by a SONET/SDH Section in the last 24 hours.
Severely Errored Seconds
Displays the number of SESs2 encountered by a SONET/SDH Section in the last 24 hours.
SE Framing Seconds
Displays the number of SEFSs3 encountered by a SONET/SDH Section in the last 24 hours.
Coding Violations
Displays the number of CVs4 encountered by a SONET/SDH Section in the last 24 hours.
1 ES = errored seconds
2 SES = severely errored seconds
3 SEFS = severely errored framing seconds
4 CV = coding violations
Step 6
Figure 5-22 displays the SONET Line Counters window.
For parameter definitions, see Table 5-13.
Figure 5-22 Sonet Line Counters Window
Step 7
Figure 5-23 displays the SONET Path Counters window.
Figure 5-23 Sonet Path Counters Window
The SONET Line and Path Counter parameters are described in Table 5-13.
Table 5-13 SONET Line and Path Counter Parameters
errored seconds
Displays the number of ES1 encountered by a SONET/SDH Section in the last 24 hours.
severely errored seconds
Displays the number of SESs2 encountered by a SONET/SDH Section in the last 24 hours.
coding violations
Displays the number of CVs3 encountered by a SONET/SDH Section in the last 24 hours.
unavailable seconds
Displays the number of UAS4 encountered by a SONET/SDH Section in the last 24 hours.
1 ES = errored seconds
2 SES = severely errored seconds
3 CV = coding violations
4 UAS = unavailable seconds
Monitoring DS3 Counters
To monitor DS3 counters, complete the following procedure:
Step 1
Step 2
Figure 5-24 displays the DS3 Counters window.
Figure 5-24 DS3 Counters (AXSM Card) Refresh Rate (sec) Dialog
The DS3 counter parameters are described in Table 5-14.
Table 5-14 DS3 Counters Refresh Rate Dialog Parameters
LOS Count
Displays the number of LOS1 errors encountered by a DS3 in the last 24 hours.
OOF Count
Displays the number of OOF2 errors encountered by a DS3 in the last 24 hours.
RAI Count
Displays the number of RAI3 errors encountered by a DS3 in the last 24 hours.
CCV Count
Displays the number of CCV4 errors encountered by a DS3 in the last 24 hours.
FEC Count
Displays the number of FEC5 errors encountered by a DS3 in the last 24 hours.
1 LOS = loss of signal
2 OOF = out-of-frame
3 RAI = remote alarm indicator
4 CCV = C-bit coding violations
5 FEC = forward explicit congestion
Step 3
Note
Understanding the LED Color Display
The ports, connectors, and LEDs are color-coded to display their status for each device. Table 5-15 describes the commonly used colors and their meaning.
Table 5-15 LED Colors for CiscoView
gray
Dormant/OK
orange
Down
red
Major Alarm/failure
yellow
Minor alarm
purple
Self-test
green
Up/OK
Understanding Fault Management Functions for Connection Manager
In addition to connection provisioning, Connection Manager assists with diagnostics. The key functions are the ability to test status, delay and integrity of AutoRoute (AR) PVC, XPVC, and PNNI SPVC connections. You need to have CLI access to individual routing switches and feeder nodes to verify each connection segment individually.
The following key functions are
•
•
You can temporarily disable a SPVC segment from Connection Manager by choosing Diagnostic > Connection Down. The operation is reversed by choosing Diagnostic > Connection Up.
You can also enable a point-to-multipoint (P2MP) SPVC connection at the master endpoint, which is used to diagnose the party, slave endpoints. For more information, see the "Testing PNNI Connections (SPVCs)" section.
•
Testing Connections
You can test the integrity of any existing connection that is nondisruptive to user traffic. The operation is similar to the tstcon command. For more information on the tstcon command, refer to the Cisco WAN Switching Command Reference, Release 9.3.30.
The following test connections are described:
•
•
Testing AutoRoute Connections (PVCs)
To test an AR PVC connection as an example, complete the following procedure:
Step 1
Step 2
Note
A successful test connection message indicates that the connection succeeded.
The integrity of a connection is tested by sending a single collection of supervisory cells to the remote end of the network and back. The operation is similar to the tstdelay command. For more information on the tstdelay command, refer to the Cisco WAN Switching Command Reference, Release 9.3.30.
To test an AR PVC connection test delay as an example, complete the following procedure:
Step 1
Step 2
The terminal displays a pass or fail message and the round trip time in ms.
Figure 5-25 shows that a test delay activity is in progress.
Figure 5-25 Test Delay in Progress
Figure 5-26 shows that the test delay activity is successful.
Figure 5-26 Test Delay Successful
Testing PNNI Connections (SPVCs)
This section describes how to enable and disable a P2MP SPVC connection for ATM-ATM.
To enable a P2MP SPVC connection, complete the following procedure:
Step 1
Step 2
Figure 5-27 displays the party diagnostics menu options. The example shows Up Party is selected.
Figure 5-27 Point-to-Multipoint SPVC/Party Configuration: Up Party
A successful up party message appears.
To disable a P2MP SPVC connection, complete the following procedure:
Step 1
Step 2
A successful down party message appears.
The oper status field indicates that the party is down.
Understanding P2MP Color Status
Table 5-16 describes the party color status.
Testing XPVC Connections
This section describes how to test specific XPVC connections.
The following tasks are
Testing Connection Segments
By testing the integrity of connection segments, a single collection of supervisory cells is sent in the egress direction between the card and service equipment (CPE). The OAM loopback cells pass through the XPVC segment linking the AR-PNNI networks. If the test connection is executed on an XPVC segment, only the local AR node information is displayed.
Note
To test connection segments for XPVC, complete the following procedure:
Step 1
(see Figure 4-1).Step 2
(see Figure 4-1).Step 3
The Test Connection Segment Configuration window (see Figure 5-28) appears.
Figure 5-28 Test Connection Segment Configuration Window
Step 4
The default value is the local end.
Step 5
The following values are
•
•
•
•
•
The default value is 1.
Step 6
The default value is disable.
Note
Step 7
The default value is I.610 Format.
Note
Step 8
When the test successfully starts, the system displays a test in-progress message (see Figure 5-29).
Figure 5-29 Test Connection Segment in Progress
Click Cancel to cancel testing.
Upon completion of the test, the relevant test results are displayed.
Testing Ping OAM
To initiate a test ping OAM for an XPVC connection, complete the following procedure:
Step 1
Step 2
Step 3
The Test Ping OAM Configuration window (see Figure 5-30) appears.
Figure 5-30 Test Ping OAM Configuration Window
Step 4
The default value is the local end.
Step 5
The following values are
•
•
•
•
•
The default value is 1.
Step 6
The default value is disable.
Note
Step 7
When the test successfully starts, the system displays a test in-progress message (see Figure 5-31).
Figure 5-31 Test Ping OAM in Progress
Click Cancel to cancel testing.
Upon completion of the test, the relevant test results are displayed.
Managing with Event Browser
The Event Browser is a component of the HP OpenView Network Node Manager application that is integrated with CWM. It includes a database that stores and provides a search capability for SNMP traps and proprietary alarms transmitted by network nodes.
The Event Browser works with hierarchical traps and alarms. Hierarchical alarms use measures to suppress the number of alarms generated. For example, if a port fails, the PVCs contained within that port cannot generate traps. This type of alarm suppression is helpful if the port contains many PVCs since only one trap is needed to indicate failure.
Trap filtering is used by upstream SNMP managers to register received traps on certain groups of resources, for example, APS or node connectivity traps instead of receiving all traps.
Network resources, which can either be a trunk or card that are inserted, modified, or removed, are monitored through configuration or modification traps.
The Event Browser window displays a listing of all events and alarms in the events database.
The following tasks are used with Event Browser:
•
•
Launching Event Browser
To launch Event Browser, complete the following procedure:
Step 1
Step 2
The Event Categories window is displayed (see Figure 5-32) that categorizes the events for the Event Log along with the HP OpenView Root window.
As a diagnostic tool, the Event Category window identifies the type and magnitude of events using a color-coded square in front of the process group.
Figure 5-32 Event Categories Window
Step 3
Navigating with Event Browser
This section describes the navigation of the event browser.
Event Browser Menu Bar
The menu bar provides available menu options for the event browser application. Table 5-17 provides a complete list of options.
Table 5-17 Event Browser Menu Bar
Save
Displays a submenu with the following options:
•
•
•
•
•
Save Browser State
Saves the current set of undeleted events to a file so the next time a restore operation is performed, the same set of events (plus any new events) are loaded.
Restore Browser State
Reloads the set of events saved when you last chose the Save Browser State option; or by either a map change or an exit of xnmevents (assuming the session was not read-only).
The Event Browser displays the saved set of events that includes any events you may have deleted in the interim plus any new events that have occurred. The operation is useful when you accidently deleted an event, or you performed a Reload Event Log operation, and you want to restore the state of your Event Browser.
Reload Event Log
Displays a submenu with the following options:
•
•
Close
Closes the All Events Browser window.
Highlight Source on Map Menu
Highlights the source of selected events in the Network Topology window.
Acknowledge
Displays a submenu with the following options:
•
•
•
UnAcknowledge
Displays a submenu with the following options:
•
•
•
Delete
Displays a submenu with the following options:
•
•
•
•
Configure Event
Manages event details such as add, edit, and other operations from the Event Configuration window (see Figure 5-39).
Assign Category
Changes the category where the selected events belonged from the Assign Category from All Events window (see Figure 5-36).
Assign Severity
Assigns one of the severity levels to the selected events. For a list of the severity levels, see the severity parameter of Table 5-18.
Additional Actions
Displays the Additional Actions window (see Figure 5-37). Transmits selected events into user-written shell commands through standard input.
Describe Event
Provides a detailed explanation of the current, selected event.
Set Filters
Sets the filter conditions that determine which events are listed in the All Events Browser window.
Clear Filters
Restores the filter conditions to the applicable default values.
Using the Event Browser
To use the Event Browser, you check the applicable event category from the Event Categories window (see Figure 5-32) to display the All Events Browser window (see Figure 5-33).
The All Events Browser window displays all the events that belong to the selected category.
Figure 5-33 Events Browser Window
Table 5-18 describes the parameters for the All Events Browser window.
Setting Event Filters
To set an event filter, complete the following procedure:
Step 1
(see Figure 5-33).Figure 5-34 displays the Set Filters for All Events window.
Note
Figure 5-34 Set Filters Window
Step 2
Step 3
•
•
•
•
•
•
Step 4
Step 5
Step 6
a.
a.
Step 7
Step 8
Saving an Event File
To save an event file, complete the following procedure:
Step 1
Step 2
The Save Selected in All Events window (see Figure 5-35) is displayed.
Note
Figure 5-35 Save... Window
Step 3
Step 4
Step 5
Assigning the Category for an Event
To assign the category for an event, complete the following procedure:
Step 1
(see Figure 5-36).Figure 5-36 Assign Category Window
Step 2
Step 3
Transmitting Selected Events
To transmit selected events into user-written shell commands, complete the following procedure:
Step 1
Figure 5-37 displays the Additional Actions on All Events window.
Note
Figure 5-37 Additional Actions Window
Step 2
•
•
•
•
•
Step 3
Step 4
Figure 5-38 Describe Event Window
Step 5
Step 6
a.
b.
Configuring Events and Categories
The following tasks are used to configure events and categories:
•
•
To configure an event, choose Actions > Configure Event from the All Events Browser window. The Event Configuration window (see Figure 5-39) is displayed.
Figure 5-39 Event Configuration Window
Navigating with Event Configuration
This section describes the navigation of the event configuration.
Event Configuration Menu Bar
The menu bar provides available menu options for the event configuration. Table 5-19 provides a complete list of options.
Table 5-19 Event Configuration Menu Bar
Save
Saves any changes that you made using the Event Configuration window. The option is disabled when you have not made any changes.
Close
Closes the Event Configuration window.
Note
Add
Displays a submenu with the following options:
•
•
Delete
Displays a submenu with the following options:
•
•
Modify Event
Displays the Modify Event window. All the data fields are filled for the selected event.
Copy Event
Copies the selected event that you assigned as the unique, event name.
Describe Event
Displays information about the event selected in the Event Configuration window.
Configure
Displays a submenu with the following options:
•
•
Sort
Displays a submenu with the following options:
•
•
Event Identifiers
Displays a submenu with the following options:
•
•
1 SNMP = Simple Network Management Protocol
Defining Events
Internally, event descriptions are generated as a result of trap information, which transpires between the network management system and the network agents. These traps are controlled by the SNMP processes.
An SNMP agent is software capable of answering valid queries from an SNMP station, for example, a CWM workstation, about information defined in the Management Information Base (MIB). A network device, which provides information about the MIB to CWM, has an SNMP agent.
CWM and the SNMP agents exchange messages over the network's Transport Layer protocol. SNMP conducts five valid types of messaging as described in Table 5-20.
The CWM SNMP traps are enhanced by a robust trap mechanism (RTM) to ensure detection and retrieval of missed traps. With RTM, CWM can maintain sequential tracking of traps from specific agents. CWM detects missed traps based on sequence numbers, and uploads the missing number from the agent using SNMP Get-Requests.
Connections between Cisco MGX PXM1-based products (Cisco 8230, Cisco 8250, and Cisco 8850) always show the Cisco BPX node. For internal connections, Cisco MGX 8220 nodes show the Cisco BPX node; however, Cisco MGX PXM1-based products (Cisco 8230, Cisco 8250, and Cisco 8850) do not.
The following example shows a connection between two Cisco MGX nodes from the trapd.log:
BPX1.MGX1.slot.port.vpi.vci - BPX2.MGX2.slot.port.vpi.vciThe following example shows a connection between two Cisco BPX nodes from the trapd.log:
BPX1..slot.port.vpi.vci - BPX2..slot.port.vpi.vciThe following example shows an internal connection for the Cisco MGX 8220 node from the trapd.log:
BPX1.MGX1.slot.port.vpi.vci - BPX1.MGX1.slot.port.vpi.vciThe following example shows an internal connection for the Cisco MGX 8850 (PXM1) node from the trapd.log:
MGX1..slot.port.vpi.vci - MGX1..slot.port.vpi.vciHP OpenView expects to receive SNMP traps only on port 162. Therefore, the RTM front-end registers with the agent on a different preconfigured port to receive traps.
Note
The Cisco MGX 8220 node reports the aggregate shelf alarm status, which is evident at the LED on the node that is affected by a specific new trap.
You need to configure the operations support system (OSS) to increase the packet size length. For example, pkt_size option for getone and setany binaries are supplied by SNMP Research.
HP OpenView snmpset and snmpget binaries default configurations do not allow set or get utilities of protocol data units (PDUs) with more than 7 to 10 KB. The default response buffer size for HPOV snmpset and snmpget binaries is around 8 KB. Due to this limitation, the set and get operation fails. The situation mostly occurs when the number of network elements in a preferred route configuration is more than 10 to 12.
To overcome the problem, the set and get utility are configured to have a response buffer size more than 15 KB. This is achieved in SNMP Research setany and getone by specifying the pkt_size command line option with the required maximum response buffer size.
Note
Creating a New Event
To create a new event, complete the following procedure:
Step 1
Figure 5-40 displays the Event Configurator/Add Event window.
Figure 5-40 Add Event Window
Step 2
Step 3
Step 4
Step 5
Step 6
Note
Step 7
Modifying an Event
To modify an event, complete the following procedure:
Step 1
Step 2
Deleting an Event
To delete an event, complete the following procedure:
Step 1
Step 2
Step 3
Displaying an Event
To display information about an event, complete the following procedure:
Step 1
See Figure 5-38 for the Describe Event window.
Step 2
Adding Categories
To add an event category, complete the following procedure:
Step 1
Figure 5-41 displays the Event Configuration: Event Categories window.
Figure 5-41 Event Configuration: Event Categories Window
Step 2
Step 3
Step 4
Deleting Categories
To delete an event category, complete the following procedure:
Step 1
See Figure 5-41 for the Event Configuration: Event Categories window.
Step 2
Step 3
Performing Additional Actions on Events
To manually perform additional actions on events, complete the following procedure:
Step 1
Figure 5-42 displays the Event Configuration /Additional Actions for Operator window.
Note
Figure 5-42 Event Configuration / Additional Actions for Operator Window
Step 2
Step 3
Step 4
a.
b.
