Cisco BPX 8650, Руководство по установке и настройке

Страница: 496 / 606

28-8
Cisco BPX 8600 Series Installation and Configuration
Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005
Chapter 28 Troubleshooting
Troubleshooting the BPX Switch
Connection Testing
System software includes a Test Connection ( tstcon ) command for testing network connections. This
test is initiated by the network operator from the NMS console and can be performed at any time, but it
momentarily interrupts traffic on the connection during the test. Connection testing should be performed
only when an alarm has been reported from the connection or during off-hours.
Test Connection tests both directions of transmission from end to end and displays a pass or fail
indication for each connection tested. You can specify:
•
a single connection
• all connections
•
all connections of a particular type (voice, data, or Frame Relay)
•
a starting and ending connection number
In addition to testing the connection, the Test Connection routine will attempt to isolate and repair any
failure it detects. The controller card at the node where the Test Connection (
tstcon ) command is issued
instructs the service card to build packets containing special test frames. These packets are sent across
the network to the terminating node, which depacketizes them, repacketizes the frame, and sends them
back to the originating node where the returned frame is analyzed.
If the returned test pattern is incorrect, the system goes into an automatic fault isolation mode.
Controllers in the various nodes along the connection route communicate with each other over an
overhead message channel separate from the normal circuits.
The test pattern continues to be transmitted and analyzed at each node along the path as it is transmitted
and as it is received until the failed network element is identified. Redundant cards may be switched into
operation and routing tables in associated network trunk cards may be reprogrammed in an attempt to
correct the problem. If all else fails, the suspected path and/or network component is then reported to the
network manager (NMS).
External Device Window
External devices connected to network nodes, such as bridges, routers, or subrate multiplexers may be
accessed through the NMS Window command. This feature provides a direct command line interface to
external devices from the NMS console. Depending on the capability of the external device, it is often
possible to report status and alarms and to control or configure the device through an RS232 port
connection.
The following example illustrates a Window display of a router connected to the local node. In this
example, the window is used to initiate a ping of the router connection.
Example: NMS Window to a Local Router
Protocol [ip]:
Target IP address: 192.9.202.1
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Type escape sequence to abort. ^^