8300

Nortel Ethernet Routing Switch 8300
Troubleshooting
NN46200-704
.
Downloaded from www.Manualslib.com manuals search engine
(323321-A Rev 01)
Document status: Standard

Document version: 01.01
Document date: 29 October 2007
Copyright 2007, Nortel Networks
All Rights Reserved.
Sourced in Canada and the United States of America
LEGAL NOTICE
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed
to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY
KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject
to change without notice.
Trademarks
*Nortel, the Nortel Networks logo and the Globemark are trademarks of Nortel Networks.
Adobe and Acrobat Reader are trademarks of Adobe Systems Incorporated.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation.
The asterisk after a name denotes a trademarked item.
Statement of conditions
In the interest of improving internal design, operational function, and/or reliability, Nortel Networks reserves the right
to make changes to the products described in this document without notice.
Nortel Networks does not assume any liability that may occur due to the use or application of the product(s) or
circuit layout(s) described herein.
Nortel Networks software license agreement

This Software License Agreement (License Agreement) is between you, the end-user (Customer) and Nortel
Networks Corporation and its subsidiaries and affiliates (Nortel Networks). PLEASE READ THE FOLLOWING
CAREFULLY. YOU MUST ACCEPT THESE LICENSE TERMS IN ORDER TO DOWNLOAD AND/OR USE THE
SOFTWARE. USE OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS LICENSE AGREEMENT.
If you do not accept these terms and conditions, return the Software, unused and in the original shipping container,
within 30 days of purchase to obtain a credit for the full purchase price.
Software is owned or licensed by Nortel Networks, its parent or one of its subsidiaries or affiliates, and is
copyrighted and licensed, not sold. Software consists of machine-readable instructions, its components, data,
audio-visual content (such as images, text, recordings or pictures) and related licensed materials including all whole
or partial copies. Nortel Networks grants you a license to use the Software only in the country where you acquired the
Software. You obtain no rights other than those granted to you under this License Agreement. You are responsible for
the selection of the Software and for the installation of, use of, and results obtained from the Software.
1.
Licensed Use of Software. Nortel Networks grants Customer a nonexclusive license to use a copy of the
Software on only one machine at any one time or to the extent of the activation or authorized usage level,
whichever is applicable. To the extent Software is furnished for use with designated hardware or Customer
furnished equipment (CFE), Customer is granted a nonexclusive license to use Software only on such
hardware or CFE, as applicable. Software contains trade secrets and Customer agrees to treat Software as
confidential information using the same care and discretion Customer uses with its own similar information that it
does not wish to disclose, publish or disseminate. Customer will ensure that anyone who uses the Software
does so only in compliance with the terms of this Agreement. Customer shall not a) use, copy, modify, transfer or
distribute the Software except as expressly authorized; b) reverse assemble, reverse compile, reverse engineer
or otherwise translate the Software; c) create derivative works or modifications unless expressly authorized; or d)
sublicense, rent or lease the Software. Licensors of intellectual property to Nortel Networks are beneficiaries of
this provision. Upon termination or breach of the license by Customer or in the event designated hardware or
CFE is no longer in use, Customer will promptly return the Software to Nortel Networks or certify its destruction.
Nortel Networks may audit by remote polling or other reasonable means to determine Customers Software
activation or usage levels. If suppliers of third party software included in Software require Nortel Networks to
include additional or different terms, Customer agrees to abide by such terms provided by Nortel Networks
with respect to such third party software.
2.
Warranty. Except as may be otherwise expressly agreed to in writing between Nortel Networks and Customer,
Software is provided AS IS without any warranties (conditions) of any kind. NORTEL NETWORKS DISCLAIMS
ALL WARRANTIES (CONDITIONS) FOR THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABLITITY AND FITNESS FOR A
PARTICULAR PURPOSE AND ANY WARRANTY OF NON-INFRINGEMENT. Nortel Networks is not obligated
to provide support of any kind for the Software. Some jurisdictions do not allow exclusion of implied warranties,
and, in such event, the above exclusions may not apply.
3.
Limitation of Remedies. IN NO EVENT SHALL NORTEL NETWORKS OR ITS AGENTS OR SUPPLIERS BE

LIABLE FOR ANY OF THE FOLLOWING: a) DAMAGES BASED ON ANY THIRD PARTY CLAIM; b) LOSS
OF, OR DAMAGE TO, CUSTOMERS RECORDS, FILES OR DATA; OR c) DIRECT, INDIRECT, SPECIAL,
INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS),
WHETHER IN CONTRACT, TORT OR OTHERWISE (INCLUDING NEGLIGENCE) ARISING OUT OF YOUR
USE OF THE SOFTWARE, EVEN IF NORTEL NETWORKS, ITS AGENTS OR SUPPLIERS HAVE BEEN
ADVISED OF THEIR POSSIBILITY. The foregoing limitations of remedies also apply to any developer and/or
supplier of the Software. Such developer and/or supplier is an intended beneficiary of this Section. Some
jurisdictions do not allow these limitations or exclusions and, in such event, they may not apply.
4.
General
a.
If Customer is the United States Government, the following paragraph shall apply: All Nortel Networks
Software available under this License Agreement is commercial computer software and commercial
computer software documentation and, in the event Software is licensed for or on behalf of the United States
Government, the respective rights to the software and software documentation are governed by Nortel
Networks standard commercial license in accordance with U.S. Federal Regulations at 48 C.F.R. Sections
12.212 (for non-DoD entities) and 48 C.F.R. 227.7202 (for DoD entities).
b.
Customer may terminate the license at any time. Nortel Networks may terminate the license if Customer
fails to comply with the terms and conditions of this license. In either event, upon termination, Customer
must either return the Software to Nortel Networks or certify its destruction.
c.
Customer is responsible for payment of any taxes, including personal property taxes, resulting from
Customers use of the Software. Customer agrees to comply with all applicable laws including all applicable
export and import laws and regulations.
d.
Neither party may bring an action, regardless of form, more than two years after the cause of the action
arose.
e.
The terms and conditions of this License Agreement form the complete and exclusive agreement between
Customer and Nortel Networks.
f.
This License Agreement is governed by the laws of the country in which Customer acquires the Software.
If the Software is acquired in the United States, then this License Agreement is governed by the laws of
the state of New York.
Contents
New in this release
Features 9
System core image dump 9
Other changes 9
Introduction
11
Troubleshooting planning
13
Proper installation and routine maintenance 13

Network configuration 13
Site network map 14
Logical connections 14
Device configuration information 14
Other important data about your network 14
Normal behavior on your network 14
Troubleshooting fundamentals
17
Port mirroring 18
Port statistics 20
Route tracing 20
Ping snoop 20
Log files 21
Loopback testing 21
System log (syslog) 21
Virtual Cable Tester 21
System core image dump 22
General diagnostic tools 22
Initial troubleshooting
NNCLI and CLI 23
About the NNCLI 23
Accessing the NNCLI (from the CLI) 25
Returning to the CLI (from the NNCLI) 26
Using the Knowledge and Solution Engine 26
Gathering information 28
Displaying configuration information using the show config command 28

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
23
6 Contents
Displaying system status using the show tech command 29
Using log files 29
Viewing the software version 30
Providing a network topology diagram 30
Documenting changes to your system or network 30
Assessing connectivity problems 30
Assessing CPU utilization problems 31
Using a trace to assess a CPU utilization problem 31
Using an auto-trace to assess a CPU utilization problem 32
Using system logging 33
Transferring a log file to a remote machine 34
Setting syslog file size 34
Setting host address for file transfer 35
Job aid: example of change syslog sizes 35
Hardware troubleshooting
37
Troubleshooting the Ethernet Routing Switch 8300 hardware 37

LED indication of problems 37
Troubleshooting when the CPU receives bad packets 38
Software troubleshooting
39
Troubleshooting PIM-SM issues in the CLI 39

Navigation 39
Troubleshooting for no bootstrap router 39
Troubleshooting for no rendezvous point 41
Troubleshooting for No (*,G) and (S,G) in the Mroute table 41
Troubleshooting for (*,G) setup, No (S,G) in the Mroute Table 43
Troubleshooting when traffic does not forward 43
Troubleshooting for traffic loss 43
Troubleshooting Split MultiLink Trunking issues 44
Navigation 44
Troubleshooting when the interswitch trunking goes down 44
Troubleshooting when the maximum supported SMLT ids is 31 through MLT
44
Downloading software
47
Downloading Ethernet Routing Switch 8300 software 47
Troubleshooting tools
Configuring port mirroring using Device Manager 49
Configuring port mirroring ports 50
Selecting ports for mirroring 51
Editing existing port mirroring values 52
Sorting entries 52
Displaying configured port mirrored entries 52
Editing existing mirrored or mirroring ports 54
Editing the Mode field values 54

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
49
Contents 7
Editing the Enable field values 55
Configuring and monitoring port mirroring using the NNCLI 55
Navigation 55
Deleting port mirroring on a port 55
Configuring port-mirroring entries 56
Displaying mirrored port information 57
Configuring and monitoring port mirroring using the CLI 58
Displaying port mirroring settings 59
Configuring mirror-by-port entries 59
Creating a new mirror-by-port table entry 59
Deleting mirror-by-port entries 60
Enabling a mirroring port 61
Configuring the mirrored port and mirroring port 61
Configuring the mirror-by-port mode 62
Displaying mirrored port information 62
Trapping errors using Device Manager 63
Displaying and configuring log files 64
Configuring and displaying log files using the NNCLI 64
Configuring and displaying log files using the CLI 71
Using syslog 81
Checking the MIB status using Device Manager 97
Checking the details of the MIB status 98
Using the Virtual Cable Tester 99
Using the Virtual Cable Tester with Device Manager 99
Testing ports using the Virtual Cable Tester in the NNCLI 106
Testing ports using the Virtual Cable Tester using the CLI 111
Monitoring ports 117
Monitoring how often a port goes down using Device Manager 117
Displaying port statistics using the NNCLI 118
Displaying port information using the CLI 122
Configuring the duration/interval of the monitor commands 128
Monitoring port statistics using the NNCLI 131
Monitoring port statistics using the CLI 134
Clearing statistics using the NNCLI 136
Clearing statistics using the CLI 137
Using ping snoop 138
Running a trace test 143
Tracing a route to a remote host using the NNCLI 143
Tracing a route to a remote host using the CLI 144
Configuring an automatic trace 145
Configuring an automatic trace using the CLI 146
Configuring an automatic trace using the NNCLI 149
Performing a loopback test 153

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
8 Contents
Performing a loopback test using the NNCLI 153
Performing a loopback test using the CLI 154
Configuring the system core image dump 155
System core image dump navigation 155
Configuring the system core image dump using the CLI 155
Configuring the system core image dump using the NNCLI 157
Understanding alarms, logs, traps, and system messages
161
Troubleshooting configuration examples
163
Configuring port mirroring using the NNCLI 163

Configuring port mirroring using the CLI 165
Supported RFCs
167
Contacting technical support
169
Gathering critical information 169

Getting Help from the Nortel Web site 170
Getting help over the phone from a Nortel Solutions Center 170
Getting help from a specialist by using an Express Routing Code 171
Getting help through a Nortel distributor or reseller 171
Diagnostics reference
173
Special terminal characters reference 173

Edit mode commands reference 174
Port numbering and MAC address assignment reference 176
Port numbering 176
Interface indexes 177
MAC address assignment 178
Text conventions 179
Index
182

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
New in this release

The following sections detail what is new in Nortel Ethernet Routing Switch
8300: Troubleshooting (NN46200-704) for Release 4.0.
"Features" (page 9)
"Other changes" (page 9)
Features
See the following section for information about a feature change:
System core image dump

In Release 4.0, the Nortel Ethernet Routing Switch 8300 supports the
system core image dump. The system core image dump preserves the core
image of RAM after the system experiences a fatal failure. This file can aid
in the determination of the root cause for the failure.
For conceptual information about the system core image dump, see "System
core image dump" (page 22). For information about the configuration of
system core image dump, see "Configuring the system core image dump "
(page 155).
Other changes
Nortel Ethernet Routing Switch 8300: Troubleshooting (NN46200-704) is a
new document for Ethernet Routing Switch 8300 Release 4.0. Content from
the following two sources has been added to this document. The following
two documents are obsolete for this release.
Ethernet Routing Switch 8300: Performance Management Diagnostic

Tools Using NNCLI and CLI (NN46200-700 / 317222-C)
Ethernet Routing Switch 8300: Performance Management Diagnostic

Tools Using Device Manager (NN46200-702 / 317359-E)

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
10 New in this release

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
11
Introduction
The Nortel Ethernet Routing Switch 8300 is a flexible and multifunctional
Layer 2/Layer 3 switch that supports diverse network architectures and
protocols. The Ethernet Routing Switch 8300 provides security and control
features such as Extensible Authentication Protocol over LAN (EAPoL),
Simple Network Management Protocol, Version 3 (SNMP3), and Secure
Shell (SSH). The Ethernet Routing Switch 8300 provides quality of service
(QoS) for a high number of attached devices and supports future network
requirements for QoS for critical applications, such as Voice over IP (VoIP).
This guide describes the diagnostic tools available for the Nortel Ethernet
Routing Switch 8300 including the Java Device Manager (Device Manager),
Nortel Networks Command Line Interface (NNCLI), and the Command Line
Interface (CLI).
Device Manager is a graphical user interface (GUI) used to configure

and manage the Ethernet Routing Switch 8300. You install it on a
management station in the network. For instructions on installing and
starting Device Manager on a Windows*, UNIX*, or Linux* platform,
refer to Nortel Ethernet Routing Switch 8300: Fundamentals Using
Device Manager (NN46200-303). The manual also describes some
common startup problems and how to troubleshoot them.
To learn the basic structure and operation of the NNCLI, refer to

Nortel Ethernet Routing Switch 8300: Command Reference NNCLI
(NN46200-306). This reference guide describes the function and syntax
of each NNCLI command.
To learn the basic structure and operation of the CLI, refer to

Nortel Ethernet Routing Switch 8300: Command Reference CLI
(NN46200-513). This reference guide describes the function and syntax
of each CLI command.
Prerequisites
This guide is intended for network administrators with the following
background:
basic knowledge of networks, Ethernet bridging, and IP routing
familiarity with networking concepts and terminology

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
12 Introduction
experience with windowing systems or GUIs
basic knowledge of network topologies
"Troubleshooting planning" (page 13)
"Troubleshooting fundamentals" (page 17)
"Initial troubleshooting" (page 23)
"Hardware troubleshooting" (page 37)
"Software troubleshooting" (page 39)
"Downloading software" (page 47)
"Troubleshooting tools" (page 49)
"Understanding alarms, logs, traps, and system messages" (page 161)
"Troubleshooting configuration examples" (page 163)
"Supported RFCs" (page 167)
"Contacting technical support" (page 169)
"Diagnostics reference" (page 173)
Navigation

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
13
Troubleshooting planning
You can better troubleshoot the problems on your network by planning for
these events in advance. To do this, you must know the following:
the proper installation and routine maintenance for your system
the configuration of your network
the normal behavior of your network
"Proper installation and routine maintenance" (page 13)
"Network configuration" (page 13)
"Normal behavior on your network" (page 14)
Navigation
Proper installation and routine maintenance

See Nortel Ethernet Routing Switch 8300 Installation Chassis Installation
and Maintenance (NN46200-304) for detailed installation information. This
document also outlines the routine tasks required for operating the Ethernet
Routing Switch 8300.
Network configuration
To keep track of your networks configuration, gather the information
described in the following sections. This information, when kept up-to-date,
is extremely helpful for locating information when you experience network
or device problems.
Navigation
"Site network map" (page 14)
"Logical connections" (page 14)
"Device configuration information" (page 14)
"Other important data about your network" (page 14)

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
14 Troubleshooting planning
Site network map

A site network map Identifies where each device is physically on your
site, which helps locate the users and applications that are affected by a
problem. You can use map to systematically search each part of your
network for problems.
Logical connections
With virtual LANs (VLANs), you must know how your devices are connected
logically as well as physically.
Device configuration information

Maintain online and paper copies of your device configuration information.
Ensure that all online data is stored with your sites regular data backup.
If your site does not have a backup system, copy the information onto a
backup disk (such as a CD or zip disk) and store the backup disk at an
offsite location.
Other important data about your network

For a complete picture of your network, have the following information
available:
All passwords - Store passwords in a safe place. It is a good practice

to keep records of you previous passwords in case you must restore a
device to a previous software version and need to use the old password
that was valid for that version.
Device inventory - It is a good practice to maintain a device inventory,

which list all devices and relevant information for your network. You can
use the inventory to easily see the device type, IP address, ports, MAC
addresses, and attached devices.
MAC address-to-port number list - If your hubs or switches are not

managed, you must keep a list of the MAC addresses that correlate to
the ports on your hubs and switches.
Change control - Maintain a change control system for all critical

systems. Permanently store change control records.
Contact details - It is a good practice to store the details of all support

contracts, support numbers, engineer details, and telephone and fax
numbers. Having this information available when troubleshooting can
save a lot to time.
Normal behavior on your network

When you are familiar with your network after it is fully operational, you can
be more effective at troubleshooting problems that arise. To understand the
normal behavior of you network, monitor your network over a long period of
time. During this time you can see a pattern in the traffic flow, such as which
devices are typically accessed or when peak usage times occur.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Normal behavior on your network
15
To identify problems, you can use a baseline analysis, which is an important

indicator of overall network health. A baseline serves as a useful reference
of network traffic during normal operation, which you can then compare
to captured network traffic while you troubleshoot network problems. A
baseline analysis speeds the process of isolating network problems. By
running tests on a healthy network, you compile normal data for your
network. You can then use this normal data to compare against the results
that you get when your network is experiencing trouble. For example, ping
each node to discover how long it typically takes to receive a response from
devices on your network. Capture and save each devices response time
and when you are troubleshooting you can use these baseline response
times to help you troubleshoot.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
16 Troubleshooting planning

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
17
Troubleshooting fundamentals
This section provides conceptual information about the methods and tools
that you can use to troubleshoot and isolate problems in your Ethernet
Routing Switch 8300 network.
The types of problems that typically occur with networks involve connectivity
and performance. The Ethernet Routing Switch 8300 supports a diverse
range of network architectures and protocols, some of which are used to
maintain and monitor connectivity and isolate connectivity faults.
In addition, the Ethernet Routing Switch 8300 supports a wide range of
diagnostic tools that you can use to monitor and analyze traffic, capture and
analyze data packets, trace data flows, view statistics, and manage event
messages.
Certain protocols and tools are tailored for troubleshooting specific Ethernet
Routing Switch 8300 network topologies. For instance, the Connectivity
Fault Management (CFM), the IEEE standard 802.1ag, is used to maintain
connectivity for Provider Backbone Transport (PBT) trunks and service
instances. Other tools are more general in their application and can be
used to diagnose and monitor ingress and egress traffic on the Ethernet
Routing Switch 8300.
When connectivity problems occur and the source of the problem is
unknown, it is usually best to follow the OSI network architecture layers.
Therefore, confirm that your physical environment, such as the cables and
module connections, is operating without any failures before moving up to
the network and application layers.
ATTENTION
Nortel recommends that you use debugging procedures only under Global
Product Support (GPS) team guidance. To contact the GPS team, call
1-8004NORTEL (1-800-466-7835).
The following provides a summary of the different troubleshooting tools

and their application.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
18 Troubleshooting fundamentals
Navigation
"Port mirroring" (page 18)
"Port statistics" (page 20)
"Route tracing" (page 20)
"Ping snoop" (page 20)
"Log files" (page 21)
"Loopback testing" (page 21)
"System log (syslog)" (page 21)
"Virtual Cable Tester" (page 21)
"System core image dump" (page 22)
"General diagnostic tools " (page 22)
Port mirroring
Ethernet Routing Switch 8300 switches have a port mirroring feature that
helps you to monitor and analyze network traffic. The port mirroring feature
supports both ingress (incoming traffic) and egress (outgoing traffic) port
mirroring. When you enable port mirroring , the ingress or egress packets of
the mirrored (source) port are forwarded normally and a copy of the packets
is sent out the mirrored port to the mirroring (destination) port. Although you
can configure Ethernet Routing Switch 8300 to monitor both ingress and
egress traffic, some restrictions apply:
You can configure up to 383 total entries in the port mirroring table for
mirroring, and you can have up to 383 entries active at any given time.
This total is the combination of the maximum number of entries in egress
port mirroring (8) and the number of entries in ingress port mirroring.
For ingress port mirroring, you can only configure one port as the
mirroring (destination) port. You can configure any number of ingress
ports as mirrored (source) ports. Therefore, all ingress mirrored traffic
is sent to the single mirroring (destination) port. Similarly, for egress
mirroring, you can only configure one port as the mirroring (destination)
port. You can configure a maximum of eight ports in egress. For ingress
and egress mirroring, you can configure the mirroring port as the same
port for both ingress and egress mirroring.
Egress port mirroring can be enabled separately, allowing you to monitor

packets as they leave specified ports. In addition, you can monitor traffic
for MAC addresses, where traffic with a given MAC source address (SA)
or MAC destination address (DA) is copied to the specified mirroring
port.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Port mirroring
19
To avoid seeing unintended traffic, remove mirroring (destination) ports

from all virtual local area networks (VLAN ) and spanning tree groups
(STG).
When mirroring ports where VLAN tagging is enabled, the VLAN tags
are not included in the packets received at the mirroring (destination)
port.
You can observe and analyze packet traffic at the mirroring port using a
network analyzera copy of the packet can be captured and analyzed.
Unlike other methods that are used to analyze packet traffic, the packet
traffic is uninterrupted and packets flow normally through the mirrored
port.
You can use the port mirroring feature to monitor and analyze network traffic
flowing on a port.
Use port mirroring to specify a destination port on which you want to see
mirrored traffic and specify the source ports from which traffic is mirrored.
You configure one mirroring port (destination port) for each mirrored port.
This port can reside on any fast packet inspection (FPI) unit. Any packet
entering or leaving a specified port is forwarded normally, and a copy of the
packet is sent out to the mirroring or destination port. When enabled, the
mirroring operation is non-intrusive; mirrored traffic is always treated in
the lowest priority queue.
You can observe and analyze packet traffic at the mirroring port using a
network analyzer. Unlike other methods that are used to analyze packet
traffic, the packet traffic is uninterrupted and packets flow normally through
the mirrored port.
You can also use the port mirroring feature to monitor traffic from Media
Access Control (MAC) addresses where traffic with a given MAC source
address (SA) or MAC destination address (DA) is copied to the mirror port.
You can enable this feature by setting the Device Manager Monitor field to
true for a MAC address in the Forwarding dialog box. Monitoring of MAC
address traffic must be within the context of a VLAN.
The port mirroring feature can be used to monitor the MAC table to show the
total count of MAC addresses and IP addresses that have been learned on
an ESM port or R module lane. You can view the number of MAC addresses
learned on each ESM port (ingress) or R module lane (ingress and egress).
Monitoring the MAC table helps you to understand how resources are
being used and how close you are to approaching the C-MAC limit per
R module lane.
Nortel recommends that you enable port mirroring only for diagnostic
purposes because this feature degrades switch performance.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
You can use Device Manager, the Nortel Command Line Interface (NNCLI),
or the Command Line Interface (CLI) to configure port mirroring.
Port statistics
The port statistics commands allow you to display information on received
and transmitted packets at the ports. The ingress and egress counts are
taken at the MAC layer. These counts are updated once every second.
Route tracing
The traceroute command records the route (the specific gateway
computers at each hop) through the internet between your computer and a
specified destination computer. It also calculates and displays the amount of
time each hop took. It is a handy tool both for understanding where problems
are in the Internet network and for getting a detailed sense of the internet.
Ping snoop
You can use the ping snoop feature to troubleshoot MultiLink Trunking (MLT)
and Split MultiLink Trunking (SMLT) networks. This feature displays the
route that IP traffic takes over an MLT or SMLT path. Ping snoop enables a
filter that copies Internet Control Message Protocol (ICMP) messages to the
CPU. The CPU then monitors the ICMP stream. The console displays the
port that is used for each IP traffic flow, from source to destination station.
There is no mechanism to prevent line rate ICMP traffic from going to the
CPU as a result of enabling ping snoop.
You create a ping snoop filter by specifying a source and destination IP
address. Then, you specify the ports on which you want to enable ping
snoop. Only one ping snoop filter is supported on a port. If an ICMP
request is received on any of the added ports, the source and destination IP
address and the port, on which the packet was received, are displayed on
the management console.
If you do not know the source and destination IP address, use 0.0.0.0/0.0.0.0
as a wild card. The wild card shows all of the ICMP flows though the port
or ports.
Ping snoop is limited by the maximum number of Access Control Groups
(ACGs) configured on the ports. The maximum is 1024 ACGs.
By design, ping snoop configurations are not saved to the configuration
file and are deleted by resetting the switch. In addition, your ping snoop
configuration is erased if you log off and then log on under a different
security level.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Virtual Cable Tester
21
Log files
Important events in the switch are logged into the log file with the timestamp,
status, and severity level (INFO, WARNING, ERROR, and FATAL). You can
use system log files to track old events which may have caused a problem.
Some of these event messages are displayed on the screen as they happen
and some of them are logged only to the file depending on how the logging
system is configured. Event message time stamp information can be used
to track the sequence of events occurring on various switches. The log file
on the PCMCIA is not saved when you reboot the system. The Ethernet
Routing Switch 8300 also logs events from the I/O modules.
Loopback testing
The Ethernet Routing Switch 8300 supports port-based internal loopback
testing. During an internal loopback test, packets are looped back at the
CPU. The CPU continues to send one packet at a time and wait for the
reply until you stop the test.
System log (syslog)

You can use the syslog messaging feature of the Ethernet Routing Switch
8300 to manage event messages. The Ethernet Routing Switch 8300
syslog software communicates with a server software component named
syslogd that resides on your management workstation.
The daemon syslogd is a software component that receives and locally
logs, displays, prints, or forwards messages that originate from sources that
are internal and external to the workstation. For example, syslogd software
concurrently handles messages received from applications running on the
workstation, as well as messages received from a Ethernet Routing Switch
8300 running in a network accessible to the workstation.
Virtual Cable Tester

The Virtual Cable Tester (VCT) technology integrates cable fault diagnostics
into physical layer (PHY) devices. You can use the technology to remotely
analyze the connected cable network, identify the error cause, and rapidly
isolate the source of the problem.
The VCT works with ports on the following modules:
8324GT
8348TX
8348TX-PWR
Note: The VCT does not work with optical ports nor with the
management port on the 8393SF module.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
The VCT technology uses time domain reflectometry (TDR) to diagnose the
attached cable plant. Similar to the principle of radar, TDR is the analysis
of a conductor by sending a pulsed signal into the conductor, and then
examining the reflection of that pulse. When the transmitted pulse reaches
the end of the cable, or a fault in the cable, part or all of the pulse energy is
reflected back to the source.
The VCT algorithm measures the time it takes for the signal to travel
down the cable, see the problem, and reflect back. This measured time is
converted to distance (0 to 255 meters). The polarity and magnitude of the
reflection, together with the distance, indicates the cable condition. For
example, +1 V indicates an open cable; -1 V indicates a short in the cable.
A VCT can tell you:
the length of a cable

Note: The cable length result can be within +1 or -1 meter of the
actual cable length.
whether or not the cable is correctly wired internally (pin-to-pin wire

mapping)
whether or not the cable contains a short circuit (wires touching each
other through damaged or missing insulation)
whether or not the cable contains a broken wire (an open)
whether or not the cable suffers from electrical cross talk (interference)
System core image dump

System core image dump preserves the core image of RAM after the
system experiences a fatal failure. This file can aid in the determination
of the root cause for the failure. You must first use the CLI to enable this
feature, and you must specify a file destination when you enable it. You
can write this file to the local flash memory, PCMCIA card, or a remote
TFTP server. If you write the file to the local flash or PCMCIA card, you do
not need to maintain network connectivity during the failure. However, the
administrator must ensure that there is adequate storage room on the flash.
After you determine that a failure has occurred and that a core dump is
recorded, retrieve the file and call 1-800-4NORTEL (1-800-466-7835).
General diagnostic tools

The Ethernet Routing Switch 8300 has diagnostic features available with
Device Manager (DM) and the Command Line Interface (CLI). You can
use these diagnostic tools to help you with troubleshooting operational
and configuration issues. You can perform such tasks as configuring and
displaying log files, viewing and monitoring port statistics, tracing a route,
running loopback and ping tests, testing the switch fabric, and viewing the
address resolution table.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
23
Initial troubleshooting
As part of your initial troubleshooting, Nortel recommends that you check
the Knowledge and Solution Engine on the Nortel Web site for known issues
and solutions related to the problem you are experiencing.
If you have to call Technical Support with your issue, the Technical Support
personnel will ask for information about your system. It is a good practice to
gather critical information prior to contacting Technical Support.
Navigation
"NNCLI and CLI" (page 23)
"Using the Knowledge and Solution Engine" (page 26)
"Gathering information" (page 28)
"Assessing connectivity problems" (page 30)
"Assessing CPU utilization problems" (page 31)
"Using system logging" (page 33)
NNCLI and CLI

About the NNCLI
This section describes the Nortel Networks Command Line Interface
(NNCLI) command modes you use to configure the Ethernet Routing Switch
8300 and the commands you use to access the NNCLI. You can access the
NNCLI using the following methods:
Telnet session
rlogin
local console port
NNCLI command modes

The NNCLI has four major command modes, listed in order of increasing
privileges:
User EXEC
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
24 Initial troubleshooting
Privileged EXEC
Global configuration
Interface configuration
Each mode provides a specific set of commands. The command set of

a higher-privilege mode is a superset of a lower-privilege mode. That
is, all lower-privilege mode commands are accessible when using a
higher-privilege mode.
The command modes are as follows:
User EXEC mode

This is the initial mode of access. By default, the User Access
Verification Password for this mode is empty, and password checking
is disabled. The password can be changed (and password checking
enabled) by the system administrator in Global configuration mode.
After the password is changed, it is activated immediately.
Privileged EXEC mode

You can access this mode from the User EXEC mode. When accessing
this mode, you are prompted to provide a login name and password.
The login name and password combination determines your access
level in the Privileged EXEC mode and other higher modes.
Global configuration mode

You can use this mode to make changes to the running configuration. If
you save the configuration, these settings survive reboots of the switch.
Interface configuration mode

You can use this mode to modify either a logical interface, such as a
VLAN, or a physical interface, such as a port/slot.
From either the Global configuration mode or the Interface configuration

mode, all the configuration parameters (both global and interface) can be
saved to a file. The default name for the configuration parameters file is
config.cfg. Alternative filenames can also be used.
Table 1 "NNCLI command modes" (page 25) lists the NNCLI command
modes, the prompts for each mode, the abbreviated name for each mode,
and how to enter and exit each mode.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
NNCLI and CLI 25

Table 1
NNCLI command modes
Command mode
Prompt
Mode
name
Command/mode
to enter or exit mode
User EXEC
Passport-8300:5>
exec
Default mode
when NNCLI is started
logout to exit
Privileged EXEC
Passport-8300:5#
privExec
enable to enter from

User EXEC mode
disable to exit to
User EXEC mode
Global
configuration
Passport-8300:5(conf
ig)#
config
configure to enter
from Privileged EXEC
mode
exit to exit to
Privileged EXEC mode
Interface
configuration
Passport-8300:5(confi
g-if)#
config-if
interface to
enter from Global
configuration mode
exit to exit to Global
configuration mode
Note: Prompts are expressed in this table using the format Passport-8300:5;
however, prompts returned from your switch typically reflect the specific chassis
you use. For example, if you use the 8310 chassis, the prompts use the format
Passport-8310:5. Prompts can be customized, also, using the NNCLI command
snmp-server name <prompt>. Refer to Nortel Ethernet Routing Switch 8300
Installation Read Me First for more information.
Accessing the NNCLI (from the CLI)

When you first power up the Ethernet Routing Switch 8300, the default
interface is the CLI. To switch from the CLI to the NNCLI, you must change
the NNCLI boot flag to true and save the boot configuration file using the
following commands:
Passport-8310:5# config boot flags nncli true
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Passport-8310:5# save boot

You must reboot the switch for this change to take effect. After you reboot
the switch, access the NNCLI using Telnet, rlogin, or the local console port.
You can log in to the switch using your password and the default privilege
password nortel.
Use the following commands to:
log in to the software using the default user name and password
access Global configuration mode

Login: xxxxx
Password: xxxxx
Passport-8310:5> enable
Password: nortel
Passport-8310:5# configure terminal
Passport-8310:5(config)#
Returning to the CLI (from the NNCLI)

Note: The config.cfg file for the CLI and the config.cfg file for the NNCLI
are not compatible. If you decide to change the CLI mode to NNCLI, or
the reverse, you must use the config.cfg file for the selected mode.
To switch from the NNCLI to the CLI, enter the following commands:
Passport-8310:5(config)# no boot flags nncli
Passport-8310:5(config)# exit
Passport-8310:5(config)# save boot
You must reboot the switch for this change to take effect.
Using the Knowledge and Solution Engine

You can use the Knowledge and Solution Engine to search an entire
database of Nortel technical documents, troubleshooting solutions,
software, and technical bulletins.
The document types available from the Knowledge and Solution Engine
include the following:
Bulletins: Includes a listing of technical bulletins.
Documentation: Includes all technical documentation written for Nortel

products (such as installation guides, administration guides, release
notes).
Service Requests: Includes technical support cases created within the

past year. The availability of service requests is based on your customer
entitlement.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using the Knowledge and Solution Engine
Software: Includes software patches and software releases.
Solutions: Includes troubleshooting solutions written by the Nortel

Technical Support team.
27
When searching through the Knowledge and Solution Engine, enter a

natural language query (that is, a query in the form of a statement or a
question).
Procedure steps
Step
Action
Go to the Nortel Web site: www.nortel.com
Log in using your user name and password.
Select SUPPORT & TRAINING.
Select ONLINE SELF-SERVICE, and then select Knowledge Base.

The Online Self-Service page appears and shows the Knowledge
and Solution Engine. For information on performing your search,
click the Search Tips link.
To view an interactive tutorial for the Knowledge and Solution
Engine, go to the Help & Contact section, click the Help Using This
Site link and then scroll to find the Knowledge Base tutorial.
Enter your problem statement or question in the text box.

Ensure that you leave spaces between the words in the statement
or question.
From the ALL TYPES drop-down list, select the document type you
want to search against.
The default is ALL TYPES, which searches on all available
documents (bulletins, documentation, services requests, software,
and solutions).
Click > (the arrow adjacent to the text box) or press Enter to start
your search.
The page reloads and provides the option to narrow your search by
product family.
End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Gathering information
Before contacting Nortel Technical Support, you must gather information
that can help the Technical Support personnel when troubleshooting. This
includes the following information:
output from the show config command
output from the show tech command
output from the following command

show port stats interface main
show port stats interface extended
show port error main
show port error extended
log files
software version
topology of the network
a list of any changes made prior to the issue (such as software,

hardware, upgrades)
Navigation
"Displaying configuration information using the show config command"

(page 28)
"Displaying system status using the show tech command" (page 29)
"Using log files" (page 29)
"Viewing the software version" (page 30)
"Providing a network topology diagram" (page 30)
"Documenting changes to your system or network" (page 30)
Displaying configuration information using the show config command

The show config command displays information about default and
current configuration of the switch. When troubleshooting a problem, use
this command to obtain useful information about the switch configuration.
Procedure steps
Step
Action
To display information about the configuration of the switch

information, enter the following command:
show config

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Gathering information 29
The information available from the show config command

includes general information about the switch type, software version,
and configuration. Each section of the configuration display pertains
to a different part of the switch.
End
Displaying system status using the show tech command

The show tech command displays technical information about system
status and information about the hardware, software, and operation of the
switch. When troubleshooting a problem, use this command to obtain useful
information about the system.
Procedure steps
Step
Action
To display information about the status of the system and switch

show tech
The information available from the show tech command includes

general information about the system (such as location), hardware
(chassis, power supplies, fans, and modules), system errors, boot
configuration, software versions, memory, port information (locking
status, configurations, names, interface status), VLANs and STGs
(numbers, port members), OSPF (area, interface, neighbors), VRRP,
IPv6, RIP, PIM, PGM, and log and trace files.
This command displays more information than the similar show sys
info command.
End
Using log files

Log files contain information about the system and events that have
occurred in the past. The log files can provide useful information when
troubleshooting.
When the config bootconfig flags logging true command
is saved in the configuration file, the log entries are written to the
/pcmcia/syslog.txt file. If the logging flag is not set to true, the log file entries
are stored in memory. The logs files can be copied from the PCMCIA card
and sent to the Technical Support team if they are requested.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
For more information about configuring and displaying log files, see
"Displaying and configuring log files" (page 64).
Viewing the software version

The show sys sw commands displays the software version that is running
on all cards.
Procedure steps
Step
Action
To display information about the software running on all cards, enter

the following command:
show sys sw
The information available from the show sys sw command

includes system software information.
End
Providing a network topology diagram

Every network is designed differently. It is a good troubleshooting practice
to have an accurate and detailed topology diagram of your network shows
the nodes and connections. This visual depiction of your network is very
helpful to Technical Support when they are assessing your problem.
Documenting changes to your system or network

When troubleshooting a problem, verify whether anything has been changed
recently. Ask the following questions:
Have you recently changed or upgraded your system, your network, or

a custom application? (For example, has any configuration or code
been changed?)
When were these changes made? Provide the date and time.
Who made these changes? Were the changes made by a partner or

customer? Provide the names of the individuals who made the changes.
What events can be identified prior to the trouble occurring? Such as an

upgrade, a LAN change, increased traffic, new hardware.
Assessing connectivity problems

When there are connectivity problems, use the source and destination IP
pairs to help troubleshoot. Look at five working source and destination IP
pairs and five IP pairs with connectivity issues.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Assessing CPU utilization problems
31
Prerequisites
Ensure that you have run the following commands:

show tech
show config
show port stats interface main
show port stats interface extended
show port error main
show port error extended
Use the following procedure to determine connectivity problems.
Procedure steps
Step
Action
Obtain five working source and destination IP pairs.
Obtain five source and destination IP pairs with connectivity issues.
To facilitate troubleshooting, compare the source and destination

IP pairs.
End
Assessing CPU utilization problems

If a CPU utilization issue is observed (generally, a sustained spike above
90%), then a trace of the CPU must be performed and captured. However,
in some instances the CPU can be fluctuating and accessing the switch to
perform a CPU trace is not an option. In this case, enable auto-trace to
automatically perform this function.
Navigation
"Using a trace to assess a CPU utilization problem" (page 31)
"Using a auto-trace to assess a CPU utilization problem" (page 32)
Using a trace to assess a CPU utilization problem

Use the following procedure to perform a CP trace.
Procedure steps
Step
Action
Clear any existing traces using the following command:

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
trace clear
Set the trace level using the following command:

trace level 9 3
Wait approximately 30 seconds.
Turn the trace off using the following command:

trace off
Access the information obtained by the trace using the following

command:
trace info
If you need to save the trace you can save the trace file to the
PCMCIA card using the following command:
save trace
The trace files is saved to the PCMCIA card with a filename of

systrace.txt.
End
Using an auto-trace to assess a CPU utilization problem

Auto-trace monitors CPU utilization so that when the configured utilization is
reached and sustained for the preconfigured amount of time, a CP trace is
performed and saved to the PCMCIA.
The default CPU utilization settings are:
High CPU utilization: 90%
High track duration: 5 seconds
Low CPU utilization: 75%
Low track durations: 5 seconds
Use the following procedure to configure the module and verbosity to trace
and then enable the feature.
Procedure steps
Step
Action
Configure the module and verbosity using the following command:

trace auto-trace add-module <module_id> <verbosity_lev
el>

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using system logging
33
For example:
trace auto-trace add-module 9 3
Enable the auto-trace feature using the following command:

trace auto-trace auto-trace enable
End
Variable definitions
Variable
Value
<module_id>
The ID of the module.

In the previous example, the module id
is 9.
<verbosity_level>
The verbosity level.

In the previous example, the verbosity
is set to 3.

By default, a system log (syslog) file is created when a PCMCIA card is
present in the switch. All log entries are saved to this file including encrypted
crash dump information.
The log file is named according to 8.3 format (xxxxxxxx.sss).
The first six characters of the log file name contains the last three bytes
of the chassis base MAC address.
The next two characters specify the slot number of CPU that generated
the logs.
The last three characters (sss) denote the sequence number of the log
file. The sequence number of the log file is incremented after every
successful auto-transfer of the file to the remote host.
After a reboot, the logs are stored in the log file name with the highest
sequence number present in the PCMCIA. If the log file does not exist,
then a new log file with the sequence number 000 is created and the logs
are stored.
Over time the syslog eventually grows to the capacity of the PCMCIA
card and thus stops logging. To prevent this, you can specify the minsize,
maxsize, and maxoccupypercentage for the syslog. By default they are
as follows:
minsize 100KB
maxsize 1024KB
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
maxoccupypercentage 90%
Transferring a log file to a remote machine

A host can be configured to send the files when they reach their maxsize.
You can configure up to 10 hosts and they are tried in the order configured.
After a file reaches its maxsize, the switch attempts to copy the syslog to
the server/host configured. If there are no hosts configured or the hosts
are unreachable the switch stops logging to the syslog and all new entries
are logged in DRAM.
If the current syslog log file is transferred to a remote host and the transfer is
verified as successful, the SMP log on the PCMCIA card is deleted. A new
log file is then started and the extension is incremented by 1.
If the settings are left at default (that is, the syslog reaches the default
maxsize of 1MB), then all logging to the syslog ceases. To ensure that
logging does not stop, you can do either of the following:
Change the maxsize to a larger value than the default and manually
maintain the syslog files on the switches. See "Setting syslog file size"
(page 34).
Create syslog hosts and transfer the syslog files to this host. See
"Setting host address for file transfer" (page 35).
Setting syslog file size

Use the following procedure to change to maxsize of the log file.
Procedure steps
Step
Action
To change to log file parameters, enter the following command:

config bootconfig logfile {minsize {64..500} {maxsize
{500..16384} {maxoccupyPercentage {10..90}
To prevent the syslog file from stopping logging, change the maxsize
to a larger value than the default value of 1024 KB.
End
Variable
Value
maxoccupyPercentage {10..90}
The maximum percentage that the

syslog can occupy. The default is 90%.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
Value
maxsize {500..16384}
The maximum size of the syslog file.

The default is 1024 KB.
minsize {64..500}
The minimum size of the syslog file.

The default is 100 KB.
35
Setting host address for file transfer

When the maxsize of the syslog is reached, the files are transferred to the
host server of choice. The file is then removed from PCMCIA and a new
one created with the sequence number increased by one.
Use the following procedure to create syslog hosts:
Procedure steps
Step
Action
To transfer the syslog file to a syslog host, enter the following

command:
config log transferFile 1 add-IP <Server IP address>
End
Job aid: example of change syslog sizes

The following command sets the minsize to 64 KB and the maxsize to 8MB.
config bootconfig logfile
64 8192 90
If no host server is specified (using the config log transferFile

command), then the capacity to store the log on PCMCIA has been
increased to 8MB from the default of 1MB. However, manual file
maintenance is required.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
37
Hardware troubleshooting
Use the tasks in this section to troubleshoot problems related to the Ethernet
Routing Switch 8300 hardware components.
Troubleshooting the Ethernet Routing Switch 8300 hardware

The following sections provide troubleshooting information for some of the
more common problems that you can encounter with the Ethernet Routing
Switch 8300.
"LED indication of problems" (page 37)
"Troubleshooting if the CPU receives bad packets" (page 38)
LED indication of problems

Table 2 "LED problem indicators" (page 37) lists the possible problems
indicated by the LEDs on the switch modules and suggests corrective action.
Table 2
LED problem indicators
Symptom
Probable cause
Corrective action
Green AC power supply

LEDs are off.
The switch is not receiving

AC power, or the power
supply has failed.
Verify that each AC power cord is

fastened securely at both ends and
that power is available at each AC
power outlet. Plug in a device such as
a lamp to ensure that the power outlet
is operational. Verify that each power
supply is turned on.
The Link/Activity LED for a

connected port is off or does
not blink (and you believe
that traffic is present).
The switch is experiencing a

port connection problem, or
the switch link partner is not
autonegotiating properly.
Verify that the cable connections to

the link partner are correct. Verify port
configuration parameters for both ends
of the connection. Move the cable
to another port to see whether the
problem occurs on the new port.
The Link/Activity LED blinks

continuously.
There is a high traffic load or

a packet broadcast storm.
Verify port configuration parameters

for both ends of the connection.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
38 Hardware troubleshooting
Symptom
Probable cause
Corrective action
The Online LED is steady

amber for longer than 3
minutes.
The module failed the

power-on self-test. A
diagnostic or hardware
failure is detected.
Replace the module.
The fan tray LED is steady

amber.
A fan tray is not present

in the specified slot, is not
turned on, or has failed.
A fan has failed or the
control/monitor circuit is
malfunctioning.
If a fan fails, replace the fan tray

as quickly as possible to maintain
high-availability operation. Failure to
replace the fan tray can cause the
chassis to overheat. You can replace
a fan tray in the 8306, 8310, 8006, or
8010 chassis with the power on or off.
Troubleshooting when the CPU receives bad packets

Heavy traffic together with high scaling numbers can cause the packet
processor to send packets with the wrong VLAN ID to the CPU. Use the
following procedure when this condition occurs.
Procedure steps
Step
Action
Ensure that the (S,G) entry number is not larger than 512.
End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
39
Software troubleshooting
Use the tasks in this section to troubleshoot connectivity, packet loss, and
performance issues that occur with specific features and functional layers of
the Ethernet Routing Switch 8300.
Navigation
"Troubleshooting PIM-SM issues in the CLI" (page 39)
"Troubleshooting Split MultiLink Trunking issues" (page 44)
Troubleshooting PIM-SM issues in the CLI

Use the tasks in this section to troubleshoot the following CLI issues that
occur with the PIM-SM feature on the Ethernet Routing Switch 8300:
Navigation
"Troubleshooting for no bootstrap router" (page 39)
"Troubleshooting for no rendezvous point" (page 41)
"Troubleshooting for No (*,G) and (S,G) in the Mroute table" (page 41)
"Troubleshooting for (*,G) setup, No (S,G) in the Mroute Table" (page 43)
"Troubleshooting if traffic does not forward" (page 43)
"Troubleshooting for traffic loss" (page 43)
Troubleshooting for no bootstrap router

Use the following procedure if the network does not designate a bootstrap
router (BSR).
Procedure steps
Step
Action
Ensure that at least one switch within the PIM domain is configured
as the candidate BSR.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
40 Software troubleshooting
To display information about the BSR for this PIM-SM domain, use
the following command: show ip pim bsr
"Show ip pim bsr command output" (page 40) shows sample output
for the show ip pim bsr command.
Show ip pim bsr command output
Check the route to the BSR.

End
Variable
Definition
Current BSR address
Specifies the IP address of the current BSR for

the local PIM-SM domain.
Current BSR Fragment Tag
Specifies a randomly generated number that

distinguishes fragments belonging to different
Bootstrap messages. Fragments belonging to
the same Bootstrap message carry the same
Fragment Tag.
Current BSR HashMask
Specifies the mask used in the hash function

to map a group to one of the C-RPs from the
RP-Set. With the hash-mask, a small number
of consecutive groups (for example, four) can
always hash to the same RP.
Current BSR priority
Specifies the priority of the current BSR. The

Candidate BSR (C-BSR) with the highest BSR
priority and address (referred to as the preferred
BSR) is elected as the BSR for the domain.
Pim Bootstrap Timer
When the Bootstrap Timer expires, the BSR

sends out Bootstrap messages.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Troubleshooting for no rendezvous point

Use the following procedure if the network does not designate an active
rendezvous point (RP).
Step
Action
To display the active RP, use the following command: show ip

pim active-rp
"Show ip pim active-rp command output" (page 41) shows sample
output for the show ip pim active-rp command.
Show ip pim active-rp command output
Check the route to the RP.

End
Variable
Definition
GRPADDR
Specifies the IP address of the multicast group.

Together with the group mask, the group address
identifies the prefix that the local router uses to
advertise as a C-RP.
RP-ADDR
Specifies the IP address of the C-RP. This

address must be one of the local PIM-SM
enabled interfaces.
RP-PRIORITY
Specifies the priority of the RP. C-RPs must send

C-RP advertising messages with the field set to
0, which is the highest priority.
Troubleshooting for No (*,G) and (S,G) in the Mroute table

The issue is often caused by the unicast route not being reachable. Use the
following procedure to check the route.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Procedure steps
Step
Action
To display the Mroute table, use the following command: show ip

pim mroute
"Show ip pim mroute command output" (page 42) shows sample
output for the show ip pim mroute command.
Show ip pim mroute command output
Check the route to the source and to the RP.

End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Troubleshooting for (*,G) setup, No (S,G) in the Mroute Table

This issue is often caused by the unicast route not being reachable. Use the
following procedure to check the route.
Procedure steps
Step
Action

pim mroute
Check the route to the source.

End
Troubleshooting when traffic does not forward

If the multicast traffic does not forward, use the following procedure:
Procedure steps
Step
Action

pim mroute
Check the outgoing port.

End
Troubleshooting for traffic loss

Use the following procedure if the multicast traffic loses packets.
Procedure steps
Step
Action

pim mroute
Check the number of (S,G) and IGMP entries .

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
End
Troubleshooting Split MultiLink Trunking issues

Use the tasks in this section to troubleshoot the following issues with Split
MultiLink Trunking (SMLT):
Navigation
"Troubleshooting if the interswitch trunking goes down" (page 44)
"Troubleshooting if the maximum supported SMLT ids is 31 through

MLT" (page 44)
Troubleshooting when the interswitch trunking goes down

If the interswitch trunking (IST) goes down, the network experiences an
unstable condition that can lead to loop, broadcast storm, and loss of
connectivity. Use the following procedure to minimize the single hardware
point-of-failure:
Procedure steps
Step
Action
Distribute IST links between modules by selecting member links that

are on different modules.
For more information about configuring IST, see Nortel Ethernet
Routing Switch 8300 Configuration VLANs, Spanning Tree, And
Static Link Aggregation using the NNCLI (NN46200-504), Nortel
Ethernet Routing Switch 8300 Configuration VLANs, Spanning
Tree, And Static Link Aggregation using the CLI (NN46200-509),
or Nortel Ethernet Routing Switch 8300 Configuration VLANs,
Spanning Tree, And Static Link Aggregation using Device Manager
(NN46200-510) .
End
Troubleshooting when the maximum supported SMLT ids is 31 through

MLT
Use the following procedure to increase the maximum SMLT ids to 512.
Step
Action
Use Single Link Trunk (SLT) by configuring SMLT on one port directly.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Troubleshooting Split MultiLink Trunking issues 45
For more information about configuring IST, see Nortel Ethernet

Routing Switch 8300 Configuration VLANs, Spanning Tree, And
Static Link Aggregation using the NNCLI (NN46200-504), Nortel
Ethernet Routing Switch 8300 Configuration VLANs, Spanning
Tree, And Static Link Aggregation using the CLI (NN46200-509),
or Nortel Ethernet Routing Switch 8300 Configuration VLANs,
Spanning Tree, And Static Link Aggregation using Device Manager
(NN46200-510) .
End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
47
Downloading software
To download software from the Nortel Web site, see the following site for
download content:
http://www.nortel.com/downloadingcontent
Navigation
"Downloading ERS 8300 software" (page 47)
Downloading Ethernet Routing Switch 8300 software

Use the following procedure to download Ethernet Routing Switch 8300
software.
Procedure steps
Step
Action
Follow the instructions to download the following file to your local

terminal:
Product Category: Routers & Routing Switches > Ethernet

Routing Switches
Product Name: Ethernet Routing Switch 8300
Content type: Software
Title: Ethernet Routing Switch 8300 v4.0

End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
48 Downloading software

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
49
Troubleshooting tools
This section describes the tools that are part of the Ethernet Routing Switch
8300 that you can use to troubleshoot operational and configuration issues.
Navigation
"Configuring port mirroring using the Device Manager" (page 49)
"Configuring and monitoring port mirroring using the NNCLI" (page 55)
"Configuring and monitoring port mirroring using the CLI" (page 58)
"Trapping errors using Device Manager" (page 63)
"Displaying and configuring log files" (page 64)
"Using syslog" (page 81)
"Checking the MIB status using Device Manager" (page 97)
"Using the Virtual Cable Tester" (page 99)
"Monitoring ports" (page 117)
"Running a trace test" (page 143)
"Performing a loopback test" (page 153)
Configuring port mirroring using Device Manager

Use port mirroring to specify a destination port on which you want to see
mirrored traffic and specify the source ports from which traffic is mirrored.
Navigation
"Configuring port mirroring ports" (page 50)
"Selecting ports for mirroring" (page 51)
"Editing existing port mirroring values" (page 52)
"Sorting entries" (page 52)
"Displaying configured port mirrored entries" (page 52)

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
50 Troubleshooting tools
"Editing existing mirrored or mirroring ports" (page 54)
"Editing the Mode field values" (page 54)
"Editing the Enable field values" (page 55)
Configuring port mirroring ports

Use the following procedure to configure ports for port mirroring.
Procedure steps
Step
Action
From the Device Manager menu bar, choose Edit, Diagnostics.

The Diagnostics dialog box appears with the Link Flap tab displayed.
Click the Port Mirrors tab.

The Port Mirrors tab appears. See "Diagnostics dialog box - Port
Mirrors tab" (page 50).
Diagnostics dialog box - Port Mirrors tab
Click Insert.
The Diagnostics, Insert Port Mirrors dialog box appears. See
"Diagnostics, Insert Port Mirrors dialog box" (page 50).
Diagnostics, Insert Port Mirrors dialog box
End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Table 3 "Diagnostics, Insert Port Mirrors dialog box fields" (page

51) describes the Diagnostics, Insert Port Mirrors dialog box fields.
Table 3
Diagnostics, Insert Port Mirrors dialog box fields
Field
Description
Id
An assigned identifier for the configured port mirroring

instance.
MirroredPort
Specifies a port to be mirrored (source port). You can

select ports from any module in your configuration by
clicking the ellipses button to the right of the field . See
"Diagnostics, Insert Port Mirrors dialog box" (page 50).
MirroringPort
Specifies a destination port (the port to which the

mirrored packets are forwarded). You can select ports
from any module in your configuration by clicking the
ellipses button to the right of the field. See "Selecting
ports for mirroring" (page 51).
Mode
Specifies the traffic direction of the packet being

mirroredRx, Tx, or both. The default configuration is
Rx.
Enable
Enables or disables this port mirroring instance. The

default value is Enable.
Selecting ports for mirroring

Use the following procedure to select ports for port mirroring.
Procedure steps
Step
Action
On the device view, select a mirrored (source) port:

a. Click the ellipses button in the MirroredPort field.
The DiagMirrorByPortMirroredPort dialog box appears. See
"DiagMirrorByPortMirroredPort dialog box" (page 51).
DiagMirrorByPortMirroredPort dialog box
b. Select a source port.

c. Click Ok.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
51
The Diagnostics, Insert Port Mirrors dialog box displays the new
entry in the MirroredPort field.
2
Select a destination port.

a. Click the ellipses button in the MirroringPort field.
The DiagMirrorByPortMirroringPort dialog box appears.
b. Select a destination port.
c. Click Ok.
The Diagnostics, Insert Port Mirrors dialog box displays the new
entry in the MirroringPort field.
In the Diagnostics, Insert Port Mirrors dialog box, select the

appropriate mode value (Tx, Rx, or both) to specify the traffic
direction of the mirrored packet. The default configuration is Rx.
Select the appropriate value (Enable or Disable) to enable or disable

this instance of mirroring. The default value is Enable.
Click Insert to accept your configuration choices.

End
Editing existing port mirroring values

This section describes how to edit existing port mirroring values. The
following topics are covered:
"Sorting entries" (page 52)
"Displaying configured port mirrored entries" (page 52)
"Editing existing mirrored or mirroring ports" (page 54)
"Editing the Mode field values" (page 54)
"Editing the Enable field values" (page 55)
Sorting entries
You can click on the column heading of any entry listed in the Port Mirrors
tab to sort the entries in ascending or descending numerical order, or you
can sort to group entry values.
Displaying configured port mirrored entries

Use the following procedure to display existing port mirroring entries.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
53
Procedure steps
Step
Action

Click the Port Mirrors tab.

The Port Mirrors tab appears with the configured port mirroring
entries displayed. See "Diagnostics dialog box - Port Mirrors tab"
(page 53).
Diagnostics dialog box - Port Mirrors tab
End
Table 4 "Port Mirrors tab fields" (page 53) describes the Port Mirrors tab
fields on the Diagnostics dialog box.
Table 4
Port Mirrors tab fields
Field
Description
Enable
Specifies the status of existing entriestrue (enabled)

or false (disabled).
Id
Read-only fielddisplays the assigned identifier for the

existing port mirroring instances.
MirroredPort
Displays existing port(s) from which packets are being

copied (also referred to as source ports).
MirroringPort
Displays the existing port that is performing the

mirroring, that is, the port to which the mirrored packets
are forwarded (also referred to as the destination port).
Mode
Specifies the traffic direction of the packets being

mirrored for each existing entryRx, Tx, or Both.
Enable
Specifies the status of existing entriestrue (enabled)

or false (disabled).

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Editing existing mirrored or mirroring ports

The Ethernet Routing Switch 8300 supports only one mirroring port. Use
the following procedure to modify an existing mirrored or mirroring port.
Procedure steps
Step
Action
From the Port Mirrors dialog box, double click on an entry you want
to modify in the MirroredPort or MirroringPort column heading.
The MirroringPort dialog box appears with the port you clicked to
modify shown selected. See "MirroringPort dialog box" (page 54).
MirroringPort dialog box
Click on the port you want as a replacement.
Click Ok.
The entry in the Port Mirrors tab is replaced with the new port.
End
Editing the Mode field values

Use the following procedure to modify an existing entry in the Mode field.
Procedure steps
Step
Action
Double click on the entry to display the pop up menu.

A pop up widow displays the following options: Rx, Tx, or Both.
Click on the option you want for replacement.

The Apply button becomes highlighted.
Click Apply to accept the option.

End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Editing the Enable field values

Use the following procedure to modify an existing entry in the Enable field.
Procedure steps
Step
Action
Double click the entry to display the pop up menu.

A pop up widow displays the following options: true or false.
Click on the option you want for replacement.

The Apply button is highlighted.
Click Apply to accept the option.

End
Configuring and monitoring port mirroring using the NNCLI

Set up port mirroring using the port-mirroring command in Global
configuration mode. For example, to monitor port 9/2 with output on port
9/3, use the following commands:
port-mirroring 1 both 9/2 9/3 enable
Prerequisites
If you are using a network sniffer, connect the sniffer to port 3.
To avoid seeing unintended traffic, remove the mirroring (destination)

port from all VLANs and spanning tree groups (STG).
You can configure one mirror port and up to 10 monitor ports.
Navigation
"Deleting port mirroring on a port" (page 55)
"Configuring port-mirroring entries" (page 56)
"Displaying mirrored port information" (page 57)
Deleting port mirroring on a port

Use the following procedure to disable mirroring on a port.
Procedure steps
Step
Action
To disable mirroring on a port, enter the following command :

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
port-mirroring <id> disable

End
Variable
Value
id
Port-mirroring entry ID (1 to 383).
Configuring port-mirroring entries

Use the following procedure to diagnose the system by monitoring/mirroring
a port. You must use the command in Global configuration mode.
Procedure steps
Step
Action
To diagnose the system by monitoring/mirroring a port, enter the

following command in Global configuration mode:
port-mirroring <id> <mode> <mirrored_port> <mirroring_p
ort> [enable|disable]
To create a new port mirroring table entry to mirror transmit packets,

enter the following command:
port-mirroring <id> tx <mirrored_port> <mirroring_port>
[enable|disable]
To create a new port mirroring table entry to mirror receive packets,

port-mirroring <id> rx <mirrored_port> <mirroring_port>
[enable|disable]
To create a new port mirroring table entry to mirror both transmit and
receive packets, enter the following command:
port-mirroring <id> both <mirrored_port> <mirroring_por
t> [enable|disable]
To change the port-mirroring mode, enter the following command:

port-mirroring <id> mode <mode> [monitor-port
<slot/port>] [mirror-port <slot/port>]
To set the mirrored port, enter the following command:

port-mirroring <id> [monitor-port <slot/port>]
[mirror-port <slot/port>]

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
To set the mirroring port, enter the following command:

port-mirroring <id> [mirror-port <slot/port>]
End
Variable
Value
id
The port-mirroring entry ID (1 to 383).
enable|disable
Enables or disables the specified port.
enable enables a mirroring port

already created in the mirror-by-port
table.
disable disables a mirroring port

table.
The default value is enable.
mirrored_port
The port number of the mirrored port.
mirroring_port
The port number of the mirroring port.
mode
The mode can be either tx, rx, or both.
tx mirrors transmit packets.
rx mirrors receive packets.
both mirrors both the transmit and

receive packets.
Displaying mirrored port information

Use the following procedure to display information about mirrored ports
on the switch.
Procedure steps
Step
Action
To display information about mirrored ports on the switch, enter the

following command:
show port-mirroring
"Show port-mirroring" (page 58) displays output from the show

port-mirroring command.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Show port-mirroring
End
Configuring and monitoring port mirroring using the CLI

Set up port mirroring using the config diag commands. For example, to
monitor port 9/2 with output on port 9/3, use the following commands:
config diag mirror-by-port 1 create in-port 9/2 out-port 9/3
config diag mirror-by-port 1 enable true
ATTENTION
Nortel recommends that you disable port mirroring when not in use to reduce
the load on the switch.
Prerequisites
If you are using a network sniffer, connect the sniffer to port 9/3.
To avoid seeing unintended traffic, remove the mirroring (destination)

port from all VLANs and spanning tree groups (STGs).
You can configure one mirror port and up to 10 monitor ports.
Navigation
"Displaying port mirroring settings" (page 59)
"Configuring mirror-by-port entries" (page 59)
"Creating a new mirror-by-port table entry" (page 59)
"Deleting mirror-by-port entries" (page 60)
"Enabling a mirroring port" (page 61)
"Configuring the mirrored port and mirroring port" (page 61)
"Configuring the mirror-by-port mode" (page 62)
"Displaying mirrored port information" (page 62)

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Displaying port mirroring settings

Use the following procedure to display information about the current port
mirroring settings.
Procedure steps
Step
Action
To display information about the current port mirroring settings, enter

config diag info
End
Configuring mirror-by-port entries

Use the following procedure to diagnose the system by monitoring/mirroring
a port.
Procedure steps
Step
Action
To diagnose the system by monitoring/mirroring a port, enter the

following command:
config diag mirror-by-port <id>
The mirror-by-port entry ID is a value of 1 to 383.

2
To display the current port mirroring settings, enter the following

command:
config diag mirror-by-port <id> info
End
Variable
Value
id
The mirror-by-port entry ID (1 to 383).
Creating a new mirror-by-port table entry

Use the following procedure to create a new mirror-by-port table entry.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Procedure steps
Step
Action
To create a new mirror-by-port table entry, enter the following

command:
config diag mirror-by-port <id> create in-port <value>
out-port <value> [mode <value>] [enable <value>]
End
Variable
Value
enable <value>
Enables the mirroring port. <value>

can be true or false. Enables (true)
or disables (false) a mirroring port
table.
This variable is optional.
id
The mirror-by-port entry ID (1 to 383).
in-port <value>
The mirrored port.
mode <value>
Sets the mirror mode. <value> can be

tx, rx, or both.
both mirrors both transmit and

receive packets.
This variable is optional.

out-port <value>
The mirroring port.
Deleting mirror-by-port entries

Use the following procedure to delete an entry from the mirror-by-port table.
Procedure steps
Step
Action
To delete an entry from the mirror-by-port table, enter the following

command:
config diag mirror-by-port <id> delete

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
End
Variable
Value
id
The mirror-by-port entry ID (1-383).
Enabling a mirroring port

Use the following procedure to enable an entry in the mirror-by-port table.
Procedure steps
Step
Action
To enable an entry from the mirror-by-port table, enter the following

command:
config diag mirror-by-port <id> enable true
To disable an entry from the mirror-by-port table, enter the following

command:
config diag mirror-by-port <id> enable false
End
Variable
Value
enable <true|false>
Enables (true) or disables (false) a

mirroring port already created in the
mirror-by-port table.
id
Configuring the mirrored port and mirroring port

Use the following procedure to configure the mirrored port and the mirroring
port.
Procedure steps
Step
Action
To configure the mirrored port, enter the following command:

config diag mirror-by-port <id> mirrored-port <port>
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
To configure the mirroring port, enter the following command:

config diag mirror-by-port <id> mirroring-port <port>
End
Variable
Value
id
port
The port number of the mirrored port or

the mirroring port.
Configuring the mirror-by-port mode

Use the following procedure to configure the mode of the mirror-by-port.
Procedure steps
Step
Action
To configure the mode, enter the following command:

config diag mirror-by-port <id> mode <tx | rx | both>
End
Variable
Value
id
mode <tx | rx | both>
Sets the mirroring mode.
both mirrors both transmit and

receive packets.
Displaying mirrored port information

Use the following procedure to display information about mirrored ports
on the switch.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Trapping errors using Device Manager
63
Procedure steps
Step
Action
To display information about mirrored ports on the switch, enter the

following command:
show diag mirror-by-port
End
Trapping errors using Device Manager

You can specify that errors generate an SNMP trap. All errors detected are
then sent to a log that you can view in Device Manager.
Use the following procedure to trap errors using Device Manager.
Procedure steps
Step
Action

Click the Error tab.

The Error tab appears. See "Diagnostics dialog box - Error tab"
(page 63).
Diagnostics dialog box - Error tab
End
Table 5 "Error tab fields" (page 64) describes the Error tab fields on the
Diagnostics dialog box.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Table 5
Error tab fields
Field
Description
AuthenticationTrap
When enabled, sends a trap upon receiving an error in

the system.
LastErrorCode
The last error reported in the system. This value is

intended to help customer support personnel isolate
system problems.
LastErrorSeverity
The last error reported in the system. The meanings

of this value are:
0= Informative Information
1= Warning Condition
2= Error Condition
3= Manufacturing Information
4= Fatal Condition
Displaying and configuring log files

Configure and display the log files for the switch using the NNCLI or the CLI.
Navigation
"Configuring and displaying log files using the NNCLI" (page 64)
"Configuring and displaying log files using the CLI" (page 71)
Configuring and displaying log files using the NNCLI

Use the logging command to configure and display the log files for the
switch. When file logging is enabled, the log entries are written to the log
file. The name of the log file is based on the chassis-based MAC address
and the CPU slot. If the logging flag is not set to true, the entries are stored
in memory.
Writing log files

Use the following procedure to write a log file.
Prerequisites
To write a log file you must be in Global Configuration mode.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
65
Procedure steps
Step
Action
To write to a log file in Global Configuration mode, enter the following

command:
logging
To specify the severity level of the events to be logged, enter the

following command:
logging level [<level>]
To specify the filtering action you want on matching logs; enter the
following command:
logging filter <str> <action> <position>
To set the log display on the screen to on or off, enter the following
command:
logging screen <true|false>
To enable logging to a PCMCIA; enter the following command:

logging logToPCMCIA
To transfer the syslog file to a remote FTP/TFTP server, enter the

following command:
logging transferFile <id> [add-IP <ipaddr>|filename
<filename>|remove-IP]
To write the log file with the designated string, enter the following
command:
logging write <str>
To clear the log file, enter the following command:

logging clear
End
Variable
Value
clear
Clears the log file.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
Value
filter <str>
<action> <position>
Specifies the filtering action you want on matching

logs.
str specifies the string that you want to match and
can be from 1 to 80 characters.
action is one of the following options:
drop - if the specified string matches, the log

should be dropped.
fileonly - if the specified string matches, the

log should be sent to a file.
screenonly - if the specified string matches,

the log should be sent to the screen.
both - if the specified string matches, the log

should be sent to both a file and to the screen.
position is the filter string insertion position. The

valid range is 1 to 50 characters.
level [<level>]
Specifies the severity level of the events to be

logged. level is one of these values:
0 = Information; all messages are recorded.
1 = Warning; only warning and more serious

messages are recorded.
2 = Error; only error and more serious

3 = Manufacturing; this parameter is not

available for customer use.
4 = Fatal; only fatal messages are recorded.
logToPCMCIA
Enable logging to PCMCIA. The default is enable

(true).
To stop logging to PCMCIA, enter no logging
logToPCMCIA.
screen <true|false>
Sets the log display on the screen to on or off.
true specifies that you want to display the log

on the screen.
false specifies that you do not want to display

the log to the screen. This is the default value.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
Value
transferFile
<id> [add-IP
<ipaddr>|filename
<filename>|remove-I
P]
Transfers the syslog file to a remote FTP/TFTP

server.
write <str>
67
id identifies the syslog file. The range is 1 to

10. You can configure up to 10 transfer files.
add-IP <ipaddr> adds a host with the

specified IP address.
filename filename is the name of the file at

the remote host.
remove-IP removes a host.
Writes the log file with the designated string.
str is the string or command that you append

to the log file. It can be from 1 to 432 characters.
If the string contains spaces, you must enclose
the string in quotation marks.
Job aid: Configuration example

This configuration example uses the preceding commands to write a log file,
set the logging level, and turn on the screen display.
Passport-8310:5(config)# logging write test
Passport-8310:5(config)# logging level 0
Passport-8310:5(config)# logging screen on
Screen logging is on
Displaying log information

Use the following procedure to display log information for the switch.
Prerequisites
To use the show logging file command, you must be in Privileged

EXEC, Global configuration, or Interface configuration mode.
Procedure steps
Step
Action
To specify the name of the log file that you want to display, enter
show logging file name-of-file <filename>

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
To specify the name of the file for which you want to save the log
show logging file save-to-file <filename>
To specify the CPU for which you want to display information, enter
show logging file CPU <CPU>
To specify the service for which you want to display information,

show logging file category <service>
To specify the severity level of the events that you want to display,
show logging file severity <level>
To display the log file in reverser order (most recent information first),
show logging file tail
End
Variable
Value
category <service>
Specifies the service for which you want to display

information. <service> is one of the following
options: SNMP, EAP, RADIUS, RMON, WEB, STG,
IGMP, HW, MLT, FILTER, QOS, SW, CPU, IP, VLAN,
or IPMC.
Use "|" to separate the options.
CPU <CPU>
Specifies the CPU for which you want to display

information.<CPU> is one of the following options:
CPU3, CPU4, or CPU5.
name-of-file
<filename>
Specifies the name of the log file that you want to

display. <filename> is the name of the file.
save-to-file
<filename>
Specifies the name of the file to which you want to

save the log information. <filename> is the name
of the file.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
69
Variable
Value
severity <level>
Specifies the severity level of the events that you

want to display. <level> is one of the following
options: INFO, ERROR, WARNING, or FATAL.
tail
Displays the log file in reverse order, with the most

recent information first.
Issuing the show logging file tail command
shows only the log messages reported after the
system comes up. This avoids system problems
when displaying a large (larger than 10 MB)
/pcmcia/syslog.txt file.

This configuration example uses the show logging file tail
command to write a log file. See Figure 1 "Show logging file tail command
output" (page 70) for sample output for this command.
If the Ethernet Routing Switch 8300 has a real-time clock, the log file shows
real time.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Figure 1
Show logging file tail command output
Displaying level information

Use the following procedure to display the level of information being entered
in the log.
Procedure steps
Step
Action
To display the level of information being entered in the log, enter

show logging config
"Show logging config command output" (page 70) shows sample

output for the show logging config command.
Show logging config command output

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
71
The level ranges from information (INFO), where all messages

are entered, to FATAL, where only fatal errors are recorded. The
manufacturing (MFG) level is for manufacturing purposes only and
not available for customer use.
End
Displaying filter
Use the following procedure to display the configured log filters.
Procedure steps
Step
Action
To display the configured log filters, use the following command:

show logging filter
"Show logging filter command output" (page 71) displays output from
the show logging filter command.
Show logging filter command output
End
Configuring and displaying log files using the CLI

The log commands allow you to configure and display the log files for the
switch. When file logging is enabled, the log entries are written to the log
file. The name of the log file is based on the chassis base MAC address
and the CPU slot. If the logging flag is not set to true, the entries are stored
in memory.
Writing log files

Use the following procedure to write a log file.
Procedure steps
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Step
Action
To write a log file, use the following command:

config log
To show and set the logging level, enter the following command:
config log level <level>
To set the log display on the screen to on or off, enter the following
command:
config log screen [<setting>]
To write the log file with the designated string, enter the following
command:
config log write <str>
To enable logging to the PCMCIA, enter the following command:

config log logtoPCMCIA
To display the current log settings, enter the following command:

config log info
To clear the log file, enter the following command:

config log clear
End
Variable
Value
level [<level>]
Shows and sets the logging level. <level> is one

of the following values:
0 = Information; all messages are recorded.
1 = Warning; only warning and more serious

2 = Error; only error and more serious

3 = Manufacturing; this parameter is not

available for customer use.
4 = Fatal; only fatal messages are recorded.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
Value
screen [<setting>]
Sets the log display on the screen to on or off.
write <str>
setting is off or on. The default is off.
Writes the log file with the designated string.
logToPCMCIA
73
str is the string or command that you append

to the log file. If the string contains spaces, you
must enclose the string in quotation marks.
Enables or disables logging to the PCMCIA. The

default is enable (true).

This configuration example uses the preceding commands to write a log file,
set the logging level, and turn on the screen display. The example also uses
the info command to display log information.
Passport-8310:5/config/log# write test

Passport-8310:5/config/log# level 0
Passport-8310:5/config/log# screen on
Screen logging is on
Passport-8310:5/config/log#info
Figure 2 "Config log info command output" (page 73) shows sample output
for the config log info command.
Figure 2
Config log info command output
Configuring log filters

The Ethernet Routing Switch 8300 provides the ability to suppress or
highlight log messages of interest through the use of log filters. Use the
following procedure to configure log filters.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Procedure steps
Step
Action
To display the configured log filters, enter the following command:

config log filter info
To specify the filtering action you want on matching logs, enter the
following command:
config log filter add <string> action <value> [pos
<value>]
To remove a filter entry, enter the following command:

config log filter delete [string <value>] [pos <value>]
End
Variable
Value
add <string>
action <value> [pos
<value>]
Specifies the filtering action you want on matching

logs.
add <string> specifies the string that you want to
match and can be from 1 to 80 characters.
action <value> specifies the filters function.
value is one of the following options:
drop - if the specified string matches, the log

should be dropped.
fileonly - if the specified string matches, the

log should be sent to a file.
screenonly - if the specified string matches,

the log should be sent to the screen.
both - if the specified string matches, the log

should be sent to both a file and to the screen.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
75
Value
pos <value> is an optional parameter that
specifies the numerical position to insert the new
string. value is a range from 1 to 50 characters.
delete [string
<value>] [pos
<value>]
Removes a filter entry. Optionally, you can specify

it by string or by position.
string <value> is the string the you want to
delete.
pos <value> specifies the numerical position of
the filter string to delete.

The following example shows how to configure a log filter with an ID of 5
and an action of drop, and display log filters:
Passport-8310:5# config log filter add 5 action drop
Passport-8310:5# config log filter info
Figure 3 "Config log filter info command output" (page 75) shows sample
output for the Config log filter info command.
Figure 3
Config log filter info command output
Transferring log files

Use the following procedure to transfer the syslog file.
Procedure steps

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Step
Action
To specify the remote FTP/TFTP server to which you want to transfer

the syslog file, enter the following command:
config log transferFile <id>
To add a host, enter the following command:

config log transferFile add-IP <ipaddr>
To specify the name of a file at the remote host, enter the following
command:
config log transferFile filename <str>
To display the remote IP address and file name of the remote host,
config log transferFile info
To remove a host, enter the following command:

config log transferFile remove-IP
End
Variable
Value
add-IP <ipaddr>
<ipaddr> is the IP address of the

host being added.
filename <str>
<str> is the name of the file at the

remote host.
<id>
Identifies the syslog file. The range

is 1 to 10. You can configure up to
10 transfer files.

The following example shows how to specify that you want the syslog file
to be transferred to a remote host with the IP address of 10.10.10.10, and
display the remote IP address that you specified and the default file name.
Passport-8310:5# config log transferFile 4
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
77
Passport-8310:5 config log transferFile 4# add-IP

10.10.10.10
Passport-8310:5 config log transferFile 4# info
Figure 4 "Config log transferFile 4 info command output" (page 77) shows
sample output for the config log transferFile 4 info command.
Figure 4
Config log transferFile 4 info command output
Displaying log information

To display log information for the switch, use the following command:
The show log file command uses the following options:
Procedure steps
Step
Action
To display log information for the switch, enter the following

command:
show log file
To specify the service for which you want to display information,

show log file category <value>
To specify the CPU for which you want to display information, enter
show log file CPU <value>
To specify the name of the log file for which you want to display
show log file name-of-file <value>
To specify the name of the file to which you want to save the log
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
show log file save-to-file <value>
To specify the severity level of the events that you want to display,
show log file severity <value>
To display the log file in reverse order; enter the following command:
show log file tail
End
Variable
Value
category <value>
Specifies the service for which you

want to display information.<value>
is one or more of the following options:
SNMP, EAP, RADIUS, RMON, WEB, STG,
IGMP, HW, MLT, FILTER, QOS, SW,
CPU, IP, VLAN, or IPMC.
CPU <value>
Specifies the CPU for which you want

to display information. <value> is
one or more of the following options:
CPU3, CPU4, or CPU5.
name-of-file <value>
Specifies the name of the log file that

you want to display. <value> is the
name of the file.
save-to-file <value>
Specifies the name of the file to which

you want to save the log information.
<value> is the name of the file.
You can specify just the filename,
or the entire path (for example,
/pcmcia/filename or /flash/filename.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
Value
severity <value>
Specifies the severity level of the

events that you want to display.
<value> is one or more of the
following options: INFO, ERROR,
WARNING, and FATAL.
tail
Displays the log file in reverse order,

with the most recent information first.
79
Issuing the show logging file

tail command shows only the log
messages reported after the system
comes up. This avoids system
problems when displaying a large
(larger than 10 MB) /pcmcia/syslog.txt
file.

This configuration example uses the preceding command to write a log file,
where the tail option was entered to display the most recent information
first.
Note: If the Ethernet Routing Switch 8300 has a real-time clock, the log
file shows real time.
Figure 5 "Show log tail file command output" (page 80) shows sample
output for this command.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Figure 5
Show log tail file command output
Displaying level information

Use the following procedure to display the level of information being entered
in the log.
Procedure steps
Step
Action
To display the level of information being entered in the log, enter

show log level
"Show log level command output" (page 80) shows sample output
for the show log level command.
Show log level command output
The level ranges from information (INFO), where all messages

are entered, to FATAL, where only fatal errors are recorded. The
manufacturing (MFG) level is for manufacturing purposes only and
not available for customer use.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using syslog 81
End
Using syslog
Use the system log (syslog) messaging feature to manage event messages.
Navigation
"Using the system log in Device Manager" (page 81)
"Using the system log in the NNCLI" (page 87)
"Using the system log in the CLI" (page 92)
Using the system log in Device Manager

Use the system log feature to send messages to syslog hosts.
Navigation
"Enabling the system log" (page 81)
"Receiving system log messages" (page 82)
"Changing the severity level mapping" (page 84)
Enabling the system log

You can enable the system log feature globally to send messages to up to
10 syslog hosts. By default, five hosts are supported.
Use the following procedure to enable the system log feature globally.
Procedure steps
Step
Action

Click the System Log tab.

The System Log tab appears. See "Diagnostics dialog box - System
Log Table tab" (page 84).

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Diagnostics dialog box - System Log tab
Set Enable to true.
Set MaxHosts (maximum number of hosts) to a value between 1

and 10.
End
Table 6 "System Log tab fields" (page 82) describes the System Log tab
fields on the Diagnostics dialog box.
Table 6
System Log tab fields
Field
Descriptions
Enable
Used to enable/disable the syslog feature. When enabled,

this feature sends a message to a server on a network that
is configured to receive and store diagnostic messages from
this device. The type of messages sent is user configurable.
MaxHost
The maximum number of remote hosts considered active

and able to receive messages from the syslog service.
OperState
The operational state of the syslog service.
Receiving system log messages

You can use the system log messaging feature of the Ethernet Routing
Switch 8300 to manage switch event messages on any management
platform. The Ethernet Routing Switch 8300 syslog software supports this
functionality by communicating with a counterpart software component
named syslog on your management workstation. The daemon syslogd is a
software component that receives and locally logs, displays, prints, and/or
forwards messages that originate from sources internal and external to the
workstation. For example, syslogd on a workstation concurrently handles

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using syslog 83
messages received from applications running on the workstation, as well

as messages received from Ethernet Routing Switch 8300 running in a
network accessible to the workstation.
At a remote UNIX management workstation, the system log messaging
feature does the following:
Receives system log messages from the Ethernet Routing Switch 8300
Examines the severity code in each message
Uses the severity code to determine appropriate system handling for

each message
Based on the severity code in each message, dispatches each message

to any or all of the following destinations:
Workstation display
Local log file
Designated printer
One or more remote hosts
Internally the Ethernet Routing Switch 8300 has four severity levels for log
messages:
Info
Warning
Error
Fatal
The system log feature supports eight different severity levels:
Debug
Info
Notice
Warning
Error
Critical
Alert
Emergency
Table 7 "Default severity levels and system log severity levels" (page
84) shows the default mapping of internal severity levels to syslog severity
levels.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Table 7
Default severity levels and system log severity levels
UNIX system
error codes
System log
severity level
Internal Ethernet Routing

Switch 8300 severity
level
Emergency
Fatal
Alert
Critical
Error
Error
Warning
Warning
Notice
Info
Info
Debug
Changing the severity level mapping

Use the following procedure to change the severity level mapping.
Procedure steps
Step
Action

Click the System Log Table tab.

The System Log Table tab appears. See "Diagnostics dialog box System Log Table tab" (page 84).
Diagnostics dialog box - System Log Table tab
For each severity type, use the MapWarningSeveritylist to change

the severity level.
End
Use the following procedure to insert a system log table member.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using syslog 85
Procedure steps
Step
Action

Click the System Log Table tab.

The System Log Table tab appears.
In the Diagnostics dialog box, click Insert.

The Diagnostics, Insert System Log Table dialog box appears. See
"Diagnostics, Insert System Log Table dialog box" (page 86).

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Diagnostics, Insert System Log Table dialog box
Select the appropriate items.
Click Insert.
End
Table 8 "Diagnostics, Insert System Log Table dialog box fields" (page
87) describes the System Log Table tab fields and Diagnostics, Insert
System Log Table dialog box.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using syslog 87
Table 8
Diagnostics, Insert System Log Table dialog box fields
Field
Description
Id
ID for the syslog host being created.
IpAddr
IP address of the syslog host.
UdpPort
The UDP port to use to send messages to the syslog

host (514 to 530). The default port is 514.
HostFacility
The syslog host facility used to identify messages

(LOCAL0 to LOCAL7). The default is LOCAL7.
Severity
The Ethernet Routing Switch 8300 message severity for

which syslog messages are sent.
MapInfoSeverity
Specifies the syslog severity level to use for Ethernet

Routing Switch 8300 Information messages. The default
is info.
MapWarningSeverity

Routing Switch 8300 Warning messages. The default is
warning.
MapErrorSeverity

Routing Switch 8300 Error messages. The default is
error.
MapFatalSeverity

Routing Switch 8300 Fatal messages. The default is
emergency.
Enable
Enables or disables sending messages to the syslog

host.
Using the system log in the NNCLI

Use the syslog facility to send messages to syslog hosts.
The syslog facility logs messages and assigns each message a severity
level based on importance.
Navigation
"Configuring the syslog facility" (page 87)
"Deleting the syslog host" (page 90)
"Displaying information about syslog features" (page 91)
Configuring the syslog facility

Use the following procedure to configure the syslog facility.
Prerequisites
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
To configure the syslog facility, you must be in Global Configuration

mode.
Procedure steps
Step
Action
To create a syslog host, enter the following command:

syslog host <id> create
To configure a host location for the syslog host; enter the following
command:
syslog host <id> address <ipaddr>
To specify the facility used in message to the syslog host, enter the
following command:
syslog host <id> facility <facility>
To specify the UDP port number on which to send syslog message

to the syslog host; enter the following command:
syslog host <id> udp-port <port>
To specify the maximum number of support syslog hosts; enter the

following command:
syslog max-hosts <maxhost>
To specify the syslog severity level to use for the Ethernet Routing
Switch 8300 information messages; enter the following command:
syslog host <id> mapinfo <level>
Switch 8300 error messages; enter the following command:
syslog host <id> maperror <level>
Switch 8300 fatal messages; enter the following command:
syslog host <id> mapfatal <level>
Switch 8300 warning messages; enter the following command:
syslog host <id> mapwarning <level>
10
To specify the severity levels for which syslog messages must be

sent for the specified modules; enter the following command:
syslog host <id> severity <info|warning|error|fatal>

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using syslog 89
11
To enable the sending of syslog message on the switch, enter the

following command:
syslog state enable
12
To enable the syslog host; enter the following command:

syslog host <id> enable
End
Variable
Value
address <ipaddr>
The IP address of the system syslog host.
facility <facility>
The system syslog host facility (LOCAL0 to LOCAL7).

The default is LOCAL7.
host <id>
The syslog host ID. The range is 1 to 10.
host <id> <enable|dis

able>
Enables or disables the syslog host. The default is

disable.
maperror <level>
The syslog severity to use for error messages.

level is {emergency|alert| critical|error|w
arning|notice|info|debug}. The default is error.
mapfatal <level>
The syslog severity to use for fatal messages.

level is {emergency|alert| critical|error
|warning|notice|info|debug}. The default is
emergency.
mapinfo <level>
The syslog severity level to use for information

messages.
arning|notice|info|debug}. The default is info.
mapwarning <level>
The syslog severity to use for warning messages.

warning.
max-hosts <maxhost>
The maximum number of enabled syslog hosts allowed

(1 to 10).
severity <info|warning|
error|fatal>
severity is the severity for which syslog messages

are sent. The valid options are info, warning, error, and
fatal.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
Value
state <enable|disable>
Enables or disables sending syslog messages on the

switch. The default is disable.
udp-port <port>
The UDP port number on which to send syslog

messages to the syslog host.
<port> is the system syslog host port number (514 to
530). The default is 514.

The following configuration example uses the preceding commands to
create a host, specify a host address, specify a facility to log on syslog host,
specify a syslog severity to use for Ethernet Routing Switch 8300 Warning
messages, specify a syslog severity to use for Ethernet Routing Switch
8300 Fatal messages, and enable the sending of syslog messages.
Passport-8310:5(config)#syslog
128.1.1.254
host 1 create
host 1 address
host 1 facility local0
host 1 mapwarning alert
host 1 mapfatal alert
state enable
Deleting the syslog host

Use the following procedure to remove the syslog host.
Prerequisites
To remove the syslog host, you must be in Global Configuration mode.
Procedure steps
Step
Action
To remove the syslog host; enter the following command:

no syslog host <id>
End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using syslog 91
Variable
Value
host <id>
Displaying information about syslog features

Use the following procedure to display information about the syslog features
enabled on the switch.
Procedure steps
Step
Action
To display information about the syslog features enabled on the

switch, enter the following command:
show syslog [host <id>]
If the host ID is entered, then system log information for the specified
host is displayed.
End
Variable
Value
host <id>
Job aid: Example

This example uses the show syslog command to display general
information about the system log and to display information about a
specified host.
Figure 6
Show syslog command output

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using the system log in the CLI

The syslog facility logs messages and assigns each message a severity
level based on importance.
Use the following procedure to configure the syslog facility.
Procedure steps
Step
Action
To create a syslog host, enter the following command:

config sys syslog host <id> create
To configure a host location for the syslog host; enter the following
command:
config sys syslog host <id> address <ipaddr>
To specify the facility used in message to the syslog host, enter the
following command:
config sys syslog host <id> facility <facility>
To specify the UDP port number on which to send syslog message

to the syslog host; enter the following command:
config sys syslog host <id> udp-port <port>
To specify the maximum number of support syslog hosts; enter the

following command:
config sys syslog max-hosts <maxhost>
Switch 8300 information messages; enter the following command:
config sys syslog host <id> mapinfo <level>
Switch 8300 error messages; enter the following command:
config sys syslog host <id> maperror <level>
Switch 8300 fatal messages; enter the following command:
config sys syslog host <id> mapfatal <level>
Switch 8300 warning messages; enter the following command:
config sys syslog host <id> mapwarning <level>
10
To specify the severity levels for which syslog messages must be

sent for the specified modules; enter the following command:
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
Using syslog 93
config sys syslog host <id> severity <info|warning|e

rror|fatal>
11
To enable the sending of syslog message on the switch, enter the

following command:
config sys syslog state enable
12
To enable the syslog host; enter the following command:

config sys syslog host <id> enable
13
To display the current syslog settings, enter the following command:

config sys syslog info
14
To display system log information for a specified host, enter the

following command:
config sys syslog host <id> info
End
Variable
Value
address <ipaddr>
The IP address of the system syslog host.
facility <facility>
The system syslog host facility (LOCAL0 to LOCAL7).

The default is LOCAL7.
host <id>
host <id> <enable|dis

able>
Enables or disables the syslog host. The default is

disable.
maperror <level>
The syslog severity to use for error messages.

level is {emergency|alert|critical|error|wa
rning|notice|info|debug}. The default is error.
mapfatal <level>
The syslog severity to use for fatal messages.

level is {emergency|alert|critical|error|
warning|notice|info|debug}. The default is
emergency.
mapinfo <level>
The syslog severity level to use for information

messages.
arning|notice|info|debug}. The default is info.
mapwarning <level>
The syslog severity to use for warning messages.

warning.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
Value
max-hosts <maxhost>
The maximum number of enabled syslog hosts allowed

(1 to 10).
severity <info|warning|
error|fatal>
severity is the severity for which syslog messages

are sent. The valid options are info, warning, error, and
fatal.
state <enable|disable>
Enables or disables sending syslog messages on the

switch. The default is disable.
udp-port <port>
The UDP port number on which to send syslog

messages to the syslog host.
<port> is the system syslog host port number (514 to
530). The default is 514.

This configuration example uses the previous commands to create a host,
specify an address for the host, specify a facility to log on syslog host,
specify a syslog severity to use for Ethernet Routing Switch 8300 Warning
messages, specify a syslog severity to use for Ethernet Routing Switch
8300 Fatal messages, and enable the sending of syslog messages. The
example also uses the info command to display system log information
for the specified host.
Passport-8310:5# config sys syslog
Passport-8310:5#host 1 create
Passport-8310:5# host 1 address
11.127.249.34
Passport-8310:5/config/sys/syslog#
local7
warning
emergency
host 1 facility
host 1 mapwarning
host 1 mapfatal
state enable
host 1 info
Figure 7 "Config sys syslog host 1 info command output" (page 95) shows
sample output for the config sys syslog host 1 info command.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using syslog 95
Figure 7
Config sys syslog host 1 info command output
Deleting the syslog host

Use the following procedure to delete a syslog host.
Procedure steps
Step
Action
To delete a syslog host; enter the following command:

config sys syslog host <id> delete
End
Variable
Value
host <id>
Displaying information about syslog features

Use the following procedure to display information about the syslog features
enabled on the switch.
Procedure steps
Step
Action
To display general information about the syslog features enabled on

the switch, enter the following command:
show sys syslog general-info
To display system log information for a specified host, enter the

following command:
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
show sys syslog host <id> info
This command results in the same output as the config sys

syslog host <id> info command.
End
Variable
Value
host <id>

This configuration example uses the preceding commands to display
general information about the system log, and to display information about
a specified host.
Figure 8 "Show sys syslog general-info command output" (page 96) shows
sample output for the show sys syslog general-info command.
Figure 8
Show sys syslog general-info command output
Figure 9 "Show sys syslog host 1 info command output" (page 97) shows
sample output for the show sys syslog host 1 info command.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Checking the MIB status using Device Manager
97
Figure 9
Show sys syslog host 1 info command output
Checking the MIB status using Device Manager

Use the Topology tab to view Nortel Management MIB (NMM) status
information.
Use the following procedure to view topology status information.
Procedure steps
Step
Action

Click the Topology tab.

The Topology tab appears. See "Diagnostics dialog box - Topology
tab" (page 97).
Diagnostics dialog box - Topology tab
End
Table 9 "Topology tab fields" (page 98) describes the Topology tab fields on
the Diagnostics dialog box.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Table 9
Topology tab fields
Field
Description
IpAddr
The IP address of the device.
Status
Whether Nortel topology is on or off for the device.
NmmLstChg
The value of sysUpTime the last time an entry in the network

management MIB (NMM) topology table was added, deleted,
or modified. If the table has not changed since the last cold or
warm start of the agent, then the value is zero.
NmmMaxNum
The maximum number of entries in the NMM topology table.
NmmCurNum
The current number of entries in the NMM topology table.
Checking the details of the MIB status

Use the Topology Table tab to view details of Nortel Management MIB
(NMM) status information.
Use the following procedure to view topology table information.
Procedure steps
Step
Action

Click the Topology Table tab.

The Topology Table tab appears. See "Diagnostics dialog box Topology Table tab" (page 98).
Diagnostics dialog box - Topology Table tab
End
Table 10 "Topology Table tab fields" (page 99) describes the Topology
Table tab fields.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Using the Virtual Cable Tester
99
Table 10
Topology Table tab fields
Field
Description
Slot
The slot number in the chassis in which the topology

message was received.
Port
The port on which the topology message was received.
IpAddr
The IP address of the sender of the topology message.
SegId
The segment identifier of the segment from which the remote

agent sent the topology message. This value is extracted
from the message.
MacAddr
The MAC address of the sender of the topology message.
ChassisType
The chassis type of the device that sent the topology

message.
BkplType
The backplane type of the device that sent the topology

message.
LocalSeg
Indicates if the sender of the topology message is on the

same Ethernet segment as the reporting agent.
CurState
The current state of the sender of the topology message.

The choices are:
topChangedTopology information has recently

changed.
heartbeatTopology information is unchanged.
newThe sending agent is in a new state.

Use the Virtual Cable Tester to test a single port or multiple ports.
Navigation
"Using the Virtual Cable Tester with the Device Manager" (page 99)
"Testing ports using the Virtual Cable Tester in the NNCLI" (page 106)
"Testing ports using the Virtual Cable Tester using the CLI" (page 111)
Using the Virtual Cable Tester with Device Manager

Use the following information to test a port or multiple ports using the Virtual
Cable Tester.
Navigation
"Testing a port using the Virtual Cable Tester using the Device Manager"
(page 100)

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
"Testing multiple ports using the Virtual Cable Tester using the Device
Manager" (page 103)
Testing a port with the Virtual Cable Tester using Device Manager
Use the following procedure to test a port using the Virtual Cable Tester
(VCT).
Procedure steps
Step
Action
In the Device Manager Main window, select the port.

The port is highlighted.
From the Device Manager menu bar, choose Edit, Port.

The Port dialog box appears with the Interface tab displayed.
Click the VCT tab.

The port VCT tab appears. See "Port VCT tab" (page 100).
Port VCT tab
To start VCT on this port, set StartTest to true.
Click Apply.
The VCT test warning box appears. See "VCT test warning box"
(page 101).

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
101
VCT test warning box
Click Yes to configure VCT for this port. Click No if you want to
discontinue the VCT test.
Click Refresh a few seconds after clicking Apply to view the test
results.
When the test is compete, StartTest is set to false and the TestDone
field is set to true. All other fields contain test result data.
Click Close.
End
Table 11 "VCT tab fields" (page 101) describes the VCT tab fields.
Table 11
VCT tab fields
Field
Description
Ifindex
The IFindex or port number of the particular port
StartTest
A read/write binary flag that is set to TRUE to start

the test. When this flag is set to TRUE, the switch
immediately sets it to FALSE and begins the VCT test.
TestDone
Indicates whether the VCT test is complete or not.

When a test is started by setting StartTest to TRUE,
this flag is immediately set to FALSE. This field is set
to TRUE when the test is complete.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Field
Description
NormalCableLength
The measured length of a cable that is OK and

plugged into a good port at the other end. Because
such a port has no reflection, the normal cable length
cannot be determined with great accuracy therefore,
the value of this field is an enumeration. The cable
length can be + or - 1 M. The meanings of this value
are:
Phy Type
cableLT50M(1) cable length = less than 50 meters
cable50M80M(2) cable length = between 50

meters and 80 meters
cable 80M110M(3) cable length = between 80

cable 110M140M(4)cable length = between 110

cable GT140M(5) cable length = greater than 140

meters
cableUnknown(6)
The type of the Phy, expressed as a speed. The

meanings of this value are:
phy100M(1) = 10/100 port
phy1000M(2) = 1 gigabit port
phyUnknown
Cable Status
Status of the cable as a whole. The status of a cable

is in a sense, a summation of the status of its pairs. If
all of the pairs are normal, then the cable is normal.
If the cable consists of zero or more normal pairs and
one or more open pairs, then the cable is considered
open. If the cable consists of shorted pairs and
normal pair, then the cable is considered shorted. Any
combination of open and shorted pairs is considered
FAILED.
PairnStatus
Indicates status of the twisted pair.

Where n is a number that specifies the cable pair.
Pairn ErrLength
The length of a twisted pair, as measured by Time

Domain Reflectometry (TDR).
n is a number that specifies the cable pair.
This measurement can only be done if the pair is
open or shorted. Therefore, this is an "Error" length.
If the pair is good and properly terminated there is
no reflection to measure.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
103
Testing multiple ports with the Virtual Cable Tester using Device
Manager
Use the following procedure to test multiple ports using the Virtual Cable
Tester.
Procedure steps
Step
Action

Click the VCT tab.

The VCT tab appears. See "Diagnostics dialog box - VCT tab" (page
103).
Diagnostics dialog box - VCT tab
Select the ports to test.
To start VCT on these ports, double click their StartTest fields and
set the field to true.
Click Apply.
The VCT test warning box appears. See "VCT test warning box"
(page 104).

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.

VCT test warning box
Click Yes to configure VCT for these ports. Click No if you want to
discontinue the VCT test.
Click Refresh a few seconds after clicking Apply to view the test
results.
When the test is compete, the StartTest field is set to false and the
TestDone field is set to true. All other fields contain test result data.
Click Close.
End
Table 12
VCT tab fields
Field
Description
Ifindex
The IFindex or port number of the particular port
StartTest
A read/write binary flag that is set to TRUE to start the test.

When this flag is set to TRUE, the switch immediately sets
it to FALSE and begins the VCT test.
TestDone
Indicates whether the VCT test is complete or not. When

a test is started by setting StartTest to TRUE, this flag is
immediately set to FALSE. This field is set to TRUE when
the test is complete.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
105
Field
Description
NormalCableLeng
th
The measured length of a cable that is OK and plugged into

a good port at the other end. Because such a port has no
reflection, the normal cable length cannot be determined
with great accuracy therefore, the value of this field is an
enumeration. The cable length can be + or - 1 M. The
Phy Type
cableLT50M(1) cable length = less than 50 meters
cable50M80M(2) cable length = between 50 meters

and 80 meters
cable 80M110M(3) cable length = between 80 meters

and 110 meters
cable 110M140M(4) cable length = between 110 meters

and 140 meters
cable GT140M(5) cable length = greater than 140

meters
cableUnknown(6)
The type of the Phy, expressed as a speed. The meanings

of this value are:
Cable Status
phy100M(1) = 10/100 port
phyUnknown
Status of the cable as a whole. The status of a cable is in

a sense, a summation of the status of its pairs. If all of the
pairs are normal, then the cable is normal.
If the cable consists of zero or more normal pairs and one
or more open pairs, then the cable is considered open. If
the cable consists of shorted pairs and normal pair, then the
cable is considered shorted. Any combination of open and
shorted pairs is considered FAILED.
PairnStatus
Indicates status of the twisted pair. Where n is a number

that specifies the different cable pairs.
Pairn ErrLength
The length of twisted pair number, as measured by Time

Where n is a number that specifies the different cable pairs.
This measurement can only be done if the pair is open or
shorted. Therefore, this is an "Error" length. If the pair
is good and properly terminated there is no reflection to
measure.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Testing ports using the Virtual Cable Tester in the NNCLI

Use the following procedure to test one or more ports using the Virtual
Cable Tester (VCT).
Prerequisites
To test ports using the Virtual Cable Tester (VCT), you must be in Global
configuration mode in the NNCLI.
Procedure steps
Step
Action
To test one or more ports using the Virtual Cable Tester (VCT), enter
the following command in Global configuration mode:
vct test <slot/port> [-slot/port][, ...]
When you enter the vct test command, the following warning
message appears:
Passport-8310:6(config)#vct test 1/2
WARNING: VCT test will impact the traffic flow.
Do you want to continue (y/n) ?
End
Variable
Value
<slot/port> [-slot/port][, ...]
Specifies the port or ports that you want

to test.
Viewing Virtual Cable Tester information

Use the following procedure to view VCT information.
Procedure steps
Step
Action
To view VCT information, enter the following command in Global

configuration mode:
show vct <slot/port> [-slot/port][, ...]
End
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
107
Variable
Value
<slot/port> [-slot/port][, ...]
Specifies the port or ports for which you

want to view VCT information.
Job aid: Example

Figure 10 "Show vct 1/2 command output" (page 107) shows sample output
for the show vct <slot/port> command.
Figure 10
Show vct 1/2 command output
Table 13
VCT tab fields
Field
Description
Port
The port number of the particular port
PhyType
The type of the Phy, expressed as a speed. The

phy100M(1) = 10/100 port
phyUnknown

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Field
Description
TestDone
Indicates whether the VCT test is complete or not.

When a test is started by setting StartTest to TRUE,
this flag is immediately set to FALSE. This field is set to
TRUE when the test is complete.
Cable Status
Status of the cable as a whole. The status of a cable is

in a sense, a summation of the status of its pairs. If all
of the pairs are normal, then the cable is normal.
If the cable consists of zero or more normal pairs and
one or more open pairs, then the cable is considered
open. If the cable consists of shorted pairs and
normal pair, then the cable is considered shorted. Any
combination of open and shorted pairs is considered
FAILED.
PairnStatus

Pairn ErrLength

Where n is a number that specifies the different cable
pairs.
This measurement can only be done if the pair is open
or shorted. Therefore, this is an "Error" length. If the pair
is good and properly terminated there is no reflection
to measure.
Job aid: VCT configuration example

You can test VCT on a port from either the Global configuration mode or
the Interface configuration mode. This configuration example uses the
commands described previously to perform the following tasks:
Configure VCT from Global Configuration mode. See "Example 1:

Configuring VCT from Global Configuration mode" (page 108).
Configure VCT from Interface Configuration mode. See "Example 2:

Configuring VCT from Interface Configuration Mode" (page 109).
Example 1: Configuring VCT from Global Configuration mode

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
109
To configure and enable VCT, use the following command:

Passport-8310:5# vct test 2/9
Figure 11 "vct test command output" (page 109) shows a VCT test
configured on port 2/9.
Figure 11
vct test command output
To display VCT information on slot 2, port 9, use the following command:

Passport-8310:5(config)# show vct 2/9
Figure 12 "Show vct command output" (page 109) shows sample output
for this command.
Figure 12
Show vct command output
Example 2: Configuring VCT from Interface Configuration Mode

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
To configure VCT from the interface configuration mode, use the following
command:
Passport-8310:5(config)# int fast 4/1
To configure and enable VCT, use the following command:
Passport-8310:5(config)# vct test
Figure 13 "VCT test command output" (page 110) shows a VCT test
Figure 13
VCT test command output
To display VCT information, use the following command:

Passport-8310:5# show vct 4/1
Figure 14 "Show vct command output" (page 111) shows sample output
for this command.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
111
Figure 14
Show vct command output
Testing ports using the Virtual Cable Tester using the CLI
You can test a single port or a range of ports using the Virtual Cable Tester
(VCT).
Navigation
"Testing a single port using VCT" (page 111)
"Testing a range of ports using VCT" (page 112)
Testing a single port using VCT

Use the following procedure to test a single port using the Virtual Cable
Tester.
Procedure steps
Step
Action
To test a single port using the Virtual Cable Tester (VCT), use the
following command:
config ethernet <slot/port> vct test
When you enter this option, a warning message appears, informing

you that the test will impact traffic flow and asking whether you want
to continue the test.
2
To display the VCT table, enter the following command:

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
config ethernet <slot/port> vct info
End
Variable
Value
<slot/port>
Specifies the slot/port you want to test.
Testing a range of ports using VCT

Use the following procedure to test a range of ports using the Virtual Cable
Tester.
Procedure steps
Step
Action
To test a range of specified ports using the Virtual Cable Tester

(VCT), enter the following command:
config ethernet <slot/port> vct test <ports>
When you enter this option, a warning message appears, informing

you that the test will impact traffic flow and asking whether you want
to continue the test.
2
To display the VCT table for the specified port or ports, enter the
following command:
config ethernet <slot/port> vct info <ports>
End
Variable
Value
<slot/port>
Specifies the slot/port you want to test.
<ports>
The command executes the VCT test

for the specified port or ports.
Example: Output for a single port

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
113
Figure 15 "Config ethernet 9/1 vct info command output" (page 113) shows
sample output for the config ethernet <slot|port> vct info
command.
Figure 15
Config ethernet 9/1 vct info command output
Table 14
VCT tab fields
Field
Description
Port
The port number of the particular port.
PhyType
The type of the Phy, expressed as a speed. The meanings

of this value are:
TestDone
phy100M(1) = 10/100 port
phyUnknown
Indicates whether the VCT test is complete or not. When

a test is started by setting StartTest to TRUE, this flag is
immediately set to FALSE. This field is set to TRUE when
the test is complete.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Field
Description
Cable Status
Status of the cable as a whole. The status of a cable is in

a sense, a summation of the status of its pairs. If all of the
pairs are normal, then the cable is normal.
If the cable consists of zero or more normal pairs and one or
more open pairs, then the cable is considered open. If the
cable consists of shorted pairs and normal pair, then the
cable is considered shorted. Any combination of open and
shorted pairs is considered FAILED.
PairnStatus

Pairn ErrLength

Where n is a number that specifies the different cable pairs.
This measurement can only be done if the pair is open or
shorted. Therefore, this is an "Error" length. If the pair
is good and properly terminated there is no reflection to
measure.
Example: Output for multiple ports

Figure 16 "Config diag vct info 8/1 command output" (page 114) shows
sample output for the config diag vct info <ports> command.
Figure 16
Config diag vct info 8/1 command output

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
115
See Table 14 "VCT tab fields" (page 113) for descriptions of the VCT tab
fields.
Job aid: VCT configuration example

You can test VCT on a port using either of these two commands:
config diagnostics vct (See "Example 1 Configuring VCT using

config diagnostics vct" (page 115).)
conf ethernet <port> vct (See "Example 2 Configuring VCT

from config ethernet <port#> vct" (page 115).)
Example 1: Configuring VCT using config diagnostics vct

To configure and enable VCT, use the following commands:
Passport-8310:5 config diag# vct
Passport-8310:5 config diag/VCT# test 2/9
Figure 17

Passport-8310:5/config# ether 2/9 vct info
Example 2: Configuring VCT from config ethernet <port#> vct
To configure and enable VCT, use the following commands:
Passport-8310:5/config# ether 4/1
Passport-8310:5/config/ethernet/4/1# vct
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Passport-8310:5/config/ethernet/4/1/VCT# test
Figure 18

Passport-8310:5/config/ethernet/4/1/VCT# info
Figure 19 "Config ethernet 4/1 VCT info command output" (page 116) shows
sample output for this command.
Figure 19
Config ethernet 4/1 VCT info command output

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
117
Monitoring ports
Navigation
"Monitoring how often a port goes down using Device Manager" (page
117)
"Displaying port statistics using the NNCLI" (page 118)
"Displaying port information using the CLI" (page 122)
"Configuring the duration/interval of the monitor commands using the

NNCLI" (page 128)

CLI" (page 129)
"Monitoring port statistics using the NNCLI" (page 131)
"Monitoring port statistics using the CLI" (page 134)
"Clearing statistics using the NNCLI" (page 136)
"Clearing statistics using the CLI" (page 137)
"Using ping snoop" (page 138)
Monitoring how often a port goes down using Device Manager

You can monitor the number of times a link is going up or down rapidly
(that is, flapping) on a port. If the number exceeds a given boundary during
a specified interval, the port is forced out of service. Use the following
procedure to monitor a port.
Procedure steps
Step
Action

See "Diagnostics dialog box - Link Flap tab" (page 117).
Diagnostics dialog box - Link Flap tab

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
End
Table 15 "Link Flap tab fields" (page 118) describes the Link Flap tab fields
on the Diagnostics dialog box.
Table 15
Link Flap tab fields
Field
Description
AutoPortDownEnable
Enables or disables the Link Flap Detect feature.
SendTrap
Specifies whether or not a trap should be sent if the

port is forced out of service.
Frequency
Specifies the number of times the port can go down

before AutodPortDown is triggered. The default is 10.
Interval
Specifies the interval (in seconds) that port change

frequency is evaluation. If multiple power down
events (specified by Frequency) occur in the interval
time, AutoPortDown is triggered. The default is 60.
Displaying port statistics using the NNCLI

Use this procedure to display port statistics.
Procedure steps
Step
Action
To display port statistics, enter the following command

from Privileged EXEC, Global configuration, or Interface
configuration mode:
show interfaces FastEthernet statistics {rmon|stg}
{slot/port[-slot/port][,...]}
End
Variable
Value
rmon
Displays RMON statistics for all ports,

or for specific ports. See "Showing
RMON port statistics" (page 120).

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
119
Variable
Value
slot/port[-slot/port][,...]
Selects one or more ports for which you

want to display statistics.
stg
Displays spanning tree statistics for

all ports, or for specific ports. See
"Showing STG port statistics" (page
119).
Showing STG port statistics

Use this procedure to display spanning tree statistics for one or more ports.
Procedure steps
Step
Action
To display spanning tree statistics for one or more ports, enter the
following command:
show interfaces FastEthernet statistics stg
End
Job aid: Showing STG port statistics

Figure 20 "Show interfaces FastEthernet statistics stg command output"
(page 120) shows the output from the show interfaces FastEthernet
statistics stg command.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.

Figure 20
Show interfaces FastEthernet statistics stg command output
Table 16 "Spanning tree port statistics" (page 120) describes the spanning
tree port statistics.
Table 16
Spanning tree port statistics
Field
Description
PORT NUM
The port number of the port for which this entry

contains Spanning Tree Protocol management
information.
IN_CONFIG BPDU
The number of Config BPDUs received.
IN_TCN BPDU
The number of Topology Change Notification

BPDUs received.
IN_BAD BPDU
The number of unknown or malformed BPDUs

received.
OUT_CONFIG BPDU
The number of Config BPDUs transmitted.
OUT_TCN BPDU
The number of Topology Change Notification

BPDUs transmitted.
Showing RMON port statistics

Use this procedure to display RMON statistics for one or more ports.
Procedure steps
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
121
Step
Action
To display RMON statistics for one or more ports, enter the following
command:
show interfaces FastEthernet statistics rmon
End
Job aid: Showing RMON port statistics

Figure 21 "Show interfaces FastEthernet statistics rmon command output"
(page 121) shows the output from the show interfaces FastEthernet
statistics rmon command:
Figure 21
Show interfaces FastEthernet statistics rmon command output
Table 17 "RMON port statistics" (page 121) describes the RMON port
statistics.
Table 17
RMON port statistics
Field
Description
PORT NUM
The port number of the port for which this entry contains
RMON management information.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Field
Description
OCTETS
The total number of octets of data (including those

in bad packets) received on the network (excluding
framing bits but including FCS octets). You can use this
object as a reasonable estimate of Ethernet utilization.
For greater precision, sample the etherStatsPkts and
etherStatsOctets objects before and after a common
interval.
PKTS
The total number of packets (including bad packets,

broadcast packets, and multicast packets) received
MULTICAST
The total number of good packets received that were

directed to the multicast address. Note that this number
does not include packets directed to the broadcast
address.
BROADCAST
The total number of good packets received that were

directed to the broadcast address. Note that this number
does not include multicast packets.
CRC ALIGN
The total number of packets received that had a length

(excluding framing bits but including FCS octets) of
between 64 and 1518 octets inclusive, but had either
a bad Frame Check Sequence (FCS) with an integral
number of octets (FCS Error) or a bad FCS with a
nonintegral number of octets (Alignment Error).
UNDERSIZE
The total number of packets received that were less

than 64 octets long (excluding framing bits but including
FCS octets) and were otherwise well formed.
OVERSIZE
The total number of packets received that were more

than 1518 octets long (excluding framing bits but
including FCS octets) and were otherwise well formed.
FRAGMENT
The total number of packets received that were less than

64 octets long (excluding framing bits but including FCS
octets) and had either a bad Frame Check Sequence
(FCS) with an integral number of octets (FCS Error) or a
bad FCS with a nonintegral number of octets (Alignment
Error). It is entirely normal for etherStatsFragments
to increment because it counts both runts (which are
normal occurrences due to collisions) and noise hits.
COLLISION
The best estimate of the total number of collisions on

this Ethernet segment.
Displaying port information using the CLI

You can use the Ethernet Routing Switch 8300 to display general port
information and statistics.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
123
Navigation
"Displaying port error statistics" (page 123)
"Displaying port statistics" (page 124)
"Displaying interface statistics" (page 125)
"Displaying port information" (page 126)
Displaying port error statistics

Use this following procedure to display port error statistics.
Procedure steps
Step
Action
To display port error statistics, enter the following command:

show ports error
"Show ports error show-all command output" (page 123) shows

sample output for the show ports error collision command.
Show ports error show-all command output
End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
Value
collision [<ports>]
Displays the number and type of Ethernet

collision errors for the specified port or all ports.
extended [<ports>]
Displays additional information about Ethernet

errors for the specified port or for all ports.
main [<ports>]
Displays basic information about the number

of different types of Ethernet errors for the
specified port or for all ports.
ospf [<ports>]
Displays extended information about OSPF

Displaying port statistics

Use the following procedure to display statistical information for one or
more ports.
Procedure steps
Step
Action
To display statistical information for one or more ports, enter the

following command:
show ports stats rmon|stag [<port>]
End
Variable
Value
rmon [<ports>]
Displays RMON statistics about ports on the switch.
stg [<ports>]
Displays spanning tree statistics about ports on the

switch.
Job aid: rmon and stg examples

Figure 22 "Show ports stats rmon command output" (page 125) shows
output from the show ports stats rmon command:

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
125
Figure 22
Show ports stats rmon command output
Figure 23 "Show ports stats stg command output" (page 125) shows output
from the show ports stats stg command:
Figure 23
Show ports stats stg command output
Displaying interface statistics

Use the following procedure to display interface statistics.
Procedure steps
Step
Action
To display interface statistics, use the following command:

show ports stats interface

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
End
Variable
Value
main [<ports>]
Displays basic interface information about the

extended [<ports>]
Displays additional port interface information

about the specified port or for all ports.
Displaying port information

Use the following procedure to display port information.
Procedure steps
Step
Action
To display port information, enter the following command:

show ports info all [<ports>] [by <value>]
End
Variable
Value
all [<ports>] [by

<value>]
Displays general information about the specified

port or for all ports.
by value displays group information by ID
number or be each feature {default|ID}.
config [<ports>]
Displays general configuration information

about the specified port or all ports.
filter [<ports>]
Displays filter information for the specified port

or all ports
interface [<ports>]
Displays information about the physical

interface for the specified port or all ports.
name [<ports>]
Displays general information, including the

name or names of the specified port or all ports.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
127
Variable
Value
qos [<ports>]
Displays QoS information for the specified port

or all ports.
route-discovery
[<ports>]
Displays IP ICMP route discovery information

for the specified port or all ports.
rate-limit [<ports>]
Displays packet rate limits for the specified port

or all ports.
tx-queue [<ports>]
Displays transmit queue information for the

specified port or all ports.
unknown-mac-discard
[<ports>]
Displays unknown-mac-discard information for

the specified port or all ports.
vlans [<ports>]
Displays VLAN information for the specified port

or all ports.
Job aid: show ports info all Figure 24 "Show ports info all command
output" (page 127) shows output from the show ports info all
command:
Figure 24
Show ports info all command output
Displaying EAPoL port information

For EAPoL information use the show ports info eapol command.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Displaying spanning tree port information

to display spanning tree port information.
Use the following procedure
Procedure steps
Step
Action
To display spanning tree port information, enter the following

command:
show ports info stg
End
Variable
Value
extended [<ports>]
Displays additional information about Ethernet

main [<ports>]
Displays basic information about the number

of different types of Ethernet errors for the
Configuring the duration/interval of the monitor commands

The monitor commands are self-updating show commands.
Navigation

NNCLI" (page 128)

CLI" (page 129)

using the NNCLI
Use the following procedure to configure the duration and interval of the
monitor commands.
Prerequisites
To use the monitor command, you must be in Global configuration

or Interface configuration mode.
Procedure steps

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
Step
Action
To configure the duration of the monitor command, enter the

following command:
129
monitor-stats duration <integer>
To configure the interval of the monitor command, enter the

following command:
monitor-stats interval <integer>
End
Variable
Value
duration <integer>
Sets the length of the monitor period.

To clear the display, type Ctrl/L.
<integer> is an integer value with a
range of 1 to 1800 seconds. The
default is 300 seconds
interval <integer>
Sets the frequency of the update

interval. To clear the display, type
Ctrl/L.
<integer> is an integer value with a
range of 1 to 600 seconds. The default
is 5 seconds.

This configuration example uses the preceding commands to set the sample
interval to 10 seconds and the sample duration to 500 seconds. These
settings cause the switch to take a sample every 10 seconds, continue
sampling for a duration of 500 seconds, and then return to the system
prompt.
Passport-8310:5(config)#monitor-stats
Passport-8310:5(config)#monitor-stats interval 10

using the CLI
Use the following procedure to set the monitor duration and interval.
Procedure steps

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Step
Action
To configure the duration of the monitor command, enter the

following command:
config cli monitor duration <integer>
To configure the interval of the monitor command, enter the

following command:
config cli monitor interval <integer>
End
Variable
Value
info
Displays current level parameter settings and next

level directories.
duration <integer>
Sets the monitor time duration. To clear the display,

type Ctrl/L.
interval <integer>
<integer> is an integer value with a range of 1

to 1800 seconds.
Sets the monitor time interval. To clear the display,

type Ctrl/L.
<integer> is an integer value with a range of

1 to 600 seconds

This configuration example uses the preceding commands to set the
monitor duration and set the monitor interval. The example also uses the
info command to display the current level parameter settings and next
level directories.
Passport-8310:5#
Passport-8310:5# config cli monitor
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
131
Passport-8310:5/config/cli/monitor# info
Figure 25 "Config cli monitor command output" (page 131) shows sample
output for the config cli monitor command.
Figure 25
Config cli monitor command output
Monitoring port statistics using the NNCLI

To monitor port statistics, use the following command from Privileged
EXEC mode:
monitor
Table 18 "Monitor commands" (page 131) shows the available options for
the monitor command.
Table 18
Monitor commands
monitor
monitor mlt error collision [<mlt_id>]
monitor mlt error main [<mlt_id>]
monitor mlt stats interface main [<mlt_id>]
monitor mlt stats interface utilization [<mlt_id>]
monitor ports error collision [from <slot/port>]
monitor ports error extended [from <slot/port>]

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
monitor
monitor ports error main [from <slot/port>]
monitor ports stats interface extended [from <slot/port>]
monitor ports stats interface main [from <slot/port>]
monitor ports stats interface utilization [from

<slot/port>]
monitor ports stats rmon [from <slot/port>]
monitor ports stats stp [from <slot/port>]
Job aid: Example

The following example uses the monitor ports error collision
command to monitor error collisions. Figure 26 "Monitor ports error collision
command output" (page 133) shows sample output for this command.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
133
Figure 26
Monitor ports error collision command output
The following example uses the monitor ports stats interface

utilization command to set the monitor port statistics. Figure 27
"Monitor ports stats interface utilization command output" (page 133) shows
Figure 27
Monitor ports stats interface utilization command output

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring port statistics using the CLI

To monitor port statistics, use the following command:
monitor
Table 19 "Monitor commands" (page 134) shows the available options for
the monitor command.
Table 19
Monitor commands
monitor
monitor mlt error collision [<mid>]
monitor mlt error main [<mid>]
monitor mlt stats interface main [<mid>]
monitor mlt stats interface utilization [<mid>]
monitor ports error collision [<ports>] [from <value>]
monitor ports error extended [<ports>] [from <value>]
monitor ports error main [<ports>] [from <value>]
monitor ports error ospf [<ports>] [from <value>]
monitor ports stats rmon [<ports>] [from <value>]
monitor ports stats interface extended [<ports>] [from

<value>]
monitor ports stats interface main [<ports>] [from <value>]

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
135
monitor
monitor ports stats interface utilization [<ports>] [from

<value>]
monitor ports stats stp [<ports>] [from <value>]
The monitor ports stats rmon [<ports>] [from <value>]

command is similar to the config rmon etherstats info command,
which is described in Configuration Network Management using NNCLI,
CLI, and Device Manager (NN46200-502).
Job aid: Example

This example uses the monitor ports error collision command to
monitor error collisions. Figure 28 "Monitor ports error collision command
output" (page 135) shows sample output for this command.
Figure 28
Monitor ports error collision command output

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Clearing statistics using the NNCLI

Use the following procedure to clear statistics from counters, flush entries
from a table, or end a Telnet session.
Prerequisites
The clear command can be executed from the Privileged EXEC, Global
configuration, or Interface configuration mode.
Procedure steps
Step
Action
To clear filters from switch counters, enter the following command:

clear filter statistics <filter_id>
To clear ARP VLAN entries from the ARP table , enter the following
command:
clear ip arp vlan <vid>
To clear route entries associated with the specified VLAN, enter

clear ip route vlan <vid>
To clear QoS statistics from the switch counters, enter the following
command:.
clear qos policy-stats <policy_id>
To clear port statistics from the switch counters, enter the following
command:
clear port-stats [<ports>]
To end a specified Telnet session, enter the following command:

clear telnet <session id>
End
Variable
Value
<filter_id>
The filter ID. The valid values are 1 to 512.
<policy_id>
The policy ID. The valid values are 1 to 128.
[<ports>]
Specifies the ports for which you are

entering the command in the form portlist
{slot/port[-slot/port][, ...]}.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
Monitoring ports
Variable
Value
<session id>
The session ID. The valid values are 0 to 7.
<vid>
vid is the VLAN ID. The valid values are 0 to

255.
137
Clearing statistics using the CLI

Use the following procedure to clear statistics from counters, flush entries
from a table, or end a Telnet session.
Procedure steps
Step
Action
To clear specified filter statistics, enter the following command:

clear filter statistics [<acl-id>] [ace-id>]
To clear ARP VLAN entries from the ARP table , enter the following
command:
clear ip arp vlan <vid>
To clear route entries associated with the specified VLAN, enter

clear ip route vlan <vid>
To clear specified QoS statistics, enter the following command:

clear qos policy-stats [<policy-id>]
To clear port statistics from the switch counters, enter the following
command:
clear ports stats [<ports>]
To end a specified Telnet session, enter the following command:

clear telnet <session id>
End
Variable
Value
[<ace-id>]
The ACE ID.
[<acl-id>]
The ACL ID.
<policy-id>
The policy ID.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
Value
[<ports>]

entering the command in the form portlist
{slot/port[-slot/port][, ...]}.
<session id>
The session ID. The valid values are 0 to 7.
<vid>
vid is the VLAN ID. The valid values are 0 to

255.
Using ping snoop

Use the following sections to configure ping snoop using the NNCLI or CLI.
Navigation
"Configuring ping snoop using the NNCLI" (page 138)
"Configuring ping snoop using the CLI" (page 140)
Configuring ping snoop using the NNCLI

Use the following procedures to configure and enable ping snoop with the
NNCLI.
Navigation
"Configuring and enabling ping snoop" (page 138)
"Disabling ping snoop with NNCLI" (page 139)
"Showing ports with ping snoop enabled" (page 140)
Configuring and enabling ping snoop

Use the following procedure to configure and enable ping snoop.
Prerequisites
You must be in EXEC mode to configure and enable ping snoop using
the NNCLI.
Procedure steps
Step
Action
To create the ping snoop filter you must set the SIP and DIP patterns.
Enter the following command:
diag ping-snoop src-ip <ip-mask> dst-ip <ip-mask>
To enable the ping snoop filter on specified ports after the filter has
been created, enter the following command:
diag ping-snoop ports <portlist>
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
Monitoring ports
139
To enable messages on the console, enter the following command:

diag ping-snoop enable
Messages are disabled by default when you create a ping snoop

filter. No messages are displayed on the console unless enabled.
End
Variable
Value
dst-ip <ip-mask>
The destination IP address. This address can

have one of the following formats: a.b.c.d/x,
a.b.c.d/x.x.x.x, or default (0.0.0.0/0.0.0.0).
ports <portlist>
Specifies the port or range of ports in the format

slot/port[-slot/port][,...] when you
apply the ping snoop filter.
src-ip <ip-mask>
The source IP address. This address can have

one of the following formats: a.b.c.d/x,
a.b.c.d/x.x.x.x, or default.
Disabling ping snoop with NNCLI

Use the following procedure to disable ping snoop.
Procedure steps
Step
Action
To disable ping snoop with the NNCLI in the EXEC mode, enter
no diag ping-snoop
To remove the ping snoop filter from the specified ports after the filter
has been disabled, enter the following command:
no diag ping-snoop ports <portlist>
To disable messages on the console, enter the following command:

no diag ping-snoop enable
Messages are disabled by default when you create a ping snoop

filter. No messages are displayed on the console unless enabled.
End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Variable
Value
ports <portlist>
Specifies the port or range of ports in

the format slot/port[-slot/port
][,...] when you disable the ping
snoop filter.
Showing ports with ping snoop enabled

Use the following procedure to see which ports have the ping snoop filter
enabled.
Procedure steps
Step
Action
To see which ports have the ping snoop filter enabled with the NNCLI
in the EXEC mode,enter the following command:
show diag ping-snoop
"Show diag ping-snoop command output" (page 140) shows a

summary of the results of this command.
Show diag ping-snoop command output
End
Configuring ping snoop using the CLI

Use the following sections to configure and enable ping snoop with the CLI.
Navigation
"Configuring and enabling ping snoop" (page 140)
"Displaying information about ping snoop" (page 141)
"Deleting the ping snoop filter" (page 142)
Configuring and enabling ping snoop

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Monitoring ports
141
Use the following procedure to configure and enable ping snoop using the
CLI.
Procedure steps
Step
Action
To creates the ping snoop filter you must provide two arguments
(the source IP address and the destination IP address). Enter the
following command:
config diag ping-snoop create src-ip <value> dst-ip
<value>
To enable the ping snoop filter, enter the following command:

config diag ping-snoop enable true
To add ports to the ping snoop filter after the filter has been created,
config diag ping-snoop add-ports <ports>
After adding a port, if an ICMP request is received on that port, the

source and destination IP address and the port on which the packet
was received are displayed on the management console.
End
Variable
Value
dst-ip <value>
The destination IP address. This address can

have one of the following formats: a.b.c.d/x,
a.b.c.d/x.x.x.x, or default (0.0.0.0/0.0.0.0).
enable <true|false>
Enables or disables the ping snoop filter.
<ports>
<ports> specifies the port or range of ports in

the format slot/port[-slot/port][,...]
when you apply the ping snoop filter.
src-ip <value>
The source IP address. This address can have

one of the following formats: a.b.c.d/x,
a.b.c.d/x.x.x.x, or default.
Displaying information about ping snoop

Use the following procedure to display information about the ping snoop
filter and to find out the ports on which the filter is applied.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Procedure steps
Step
Action
To display the ping snoop filter and the ports on which it is applied,
config diag ping-snoop info
End
Deleting the ping snoop filter

Use the following procedure to removed the ping snoop filter from all ports
or a specified port.
Procedure steps
Step
Action
To delete the ping snoop filter on a particular port, enter the following
command:
config diag ping-snoop remove-ports <ports>
To remove the ping snoop filter from any ports that were added and
delete the filter, enter the following command:
config diag ping-snoop delete
End
Variable
Value
<ports>
<ports> specifies the port or range of ports in

the format slot/port[-slot/port][,...]
when you apply the ping snoop filter.
Job aid: CLI configuration example of configuring ping snoop

This configuration example uses the previous commands and shows a
summary of the results using the info command.
Passport-8300:3/config/diag/ping-snoop# create src-ip
default
dst-ip default

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Running a trace test
143
Passport-8300:3/config/diag/ping-snoop# enable true

Passport-8300:3/config/diag/ping-snoop# add-ports 1/1
Figure 29 "Config diag ping-snoop info command output" (page 143) shows
a summary of the results of these commands.
Figure 29
Config diag ping-snoop info command output
Running a trace test

Run a trace to find all the routes to a remote host or to determine if the
remote network is not reachable.
Navigation
"Tracing a route to a remote host using the NNCLI" (page 143)
"Tracing a route to a remote host using the CLI" (page 144)
Tracing a route to a remote host using the NNCLI

Use the following procedure to trace a route to a remote host using the
NNCLI.
Prerequisites
The traceroute command must be entered in Privileged EXEC mode.
Procedure steps
Step
Action
To trace the route to a remote host, enter the following command in

Privileged EXEC mode:
traceroute <ipaddr> [<datasize>] [-m <value>] [-p
<value>] [-q <value>] [-w <value>] [-v]
This command is useful for troubleshooting because it shows all

the routes that are used or indicates that the remote network is not
reachable.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
"Traceroute command output" (page 144) shows output from the

traceroute command.
Traceroute command output
End
Variable
Value
datasize
The size of the probe packet (1 to

1464).
ipaddr
The IP address of the remote host.
-m <value>
The maximum time-to-live (TTL) value

(1 to 255).
-p <value>
The base UDP port number (0 to

65535).
-q <value>
The number of probes for each TTL

value (1 to 255)
-w <value>
The wait time for each probe (1 to 255).
-v
The verbose mode (showing all).
Tracing a route to a remote host using the CLI

Use the following procedure to trace a route to a remote host using the CLI.
Procedure steps
Step
Action
To trace the route to a remote host, enter the following command:

traceroute <ipaddr> [<datasize>] [-m <value>] [-p
<value>] [-q <value>] [-w <value>] [-v]

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Configuring an automatic trace
145
This command is valuable for troubleshooting because it shows all

the routes that are used or indicates that the remote network is not
reachable.
"Traceroute command output" (page 145) shows output from the
traceroute command.
Traceroute command output
End
Variable
Value
<datasize>
The size of the probe packet (1 to

1464).
<ipaddr>
The IP address of the remote host
-m <value>
The maximum time-to-live (TTL) value

(1 to 255).
-p <value>
The base UDP port number (0 to

65535).
-q <value>
The number of probes per TTL (1 to

255).
-w <value>
The wait time per probe (1 to 255).
-v
The verbose mode (showing all).

You can configure the switch to automatically enable a trace in the event
CPU utilization reaches a pre-defined value.
Navigation
"Configuring an automatic trace using the CLI" (page 146)
"Configuring an automatic trace using the NNCLI" (page 149)

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
Configuring an automatic trace using the CLI

Use the procedures in this section to configure an automatic trace using
the CLI.
ATTENTION
The enabling or disabling of auto-trace is not saved to the configuration file. When
a Ethernet Routing Switch 8300 re-boots, the auto-trace functionality is disabled.
Navigation
"Enabling an auto-trace" (page 146)
"Adding a module" (page 146)
"Removing a module" (page 147)
"Specifying the CPU utilization percentages" (page 148)
"Specifying the time to monitor CPU utilization" (page 148)
"Displaying information about the trace" (page 149)
Enabling an auto-trace
Use the following procedure to enable the trace auto-enable feature.
Procedure steps
Step
Action
To enable the trace auto-enable feature, enter the following

command:
trace auto-enable auto-trace enable
End
Variable
Value
auto-trace <enable|disable>
Enables or disables auto-trace. The

default value is disable.
Adding a module
Use the following procedure to add a module to be traced by the trace
auto-enable feature.
Procedure steps

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Step
Action
To add module to be traced, enter the following command.
147
trace auto-enable add-module <modid> <level>
End
Variable
Value
<level>
Identifies the level of detail you want in

the trace. For example, 0 = Disabled, 1
= Very Terse.
<modid>
Identifies the module that you want to

add. For example, 3 = Port Manager,
20 = Topology Discovery. For a list
of valid module IDs, enter trace
auto-enable add-module ?.
Removing a module
Use the following procedure to remove a module from automatic tracing.
Procedure steps
Step
Action
To remove a module that is being traced by the trace auto-enable

feature, enter the following command.
trace auto-enable remove-module <modid>
End
Variable
Value
<modid>
Identifies the module for which you want

to disable auto-trace. For example,
3 = Port Manager, 20 = Topology
Discovery. The valid range is 0 to 66.
For a list of valid module IDs, enter
trace auto-enable add-module
??.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Specifying the CPU utilization percentages

Use the following procedure to specify the CPU utilization percentage above
which tracing is enabled and the CPU utilization percentage below which
auto-trace is disabled.
Procedure steps
Step
Action
To specify the CPU utilization percentage above which auto trace

must be enabled, enter the following command.
trace auto-enable high-percentage <percent>
To specify the CPU utilization percentage below which auto-trace is

disabled, enter the following command:
trace auto-enable low-percentage <percent>
End
Variable
Value
high-percentage <percent>
percent is a value from 60 to 100.

The default is 90.
low-percentage <percent>
percent is a value from 50 to 90. The

default is 75.
Specifying the time to monitor CPU utilization

Use the following procedure to specify the time to monitor CPU utilization
before triggering or disabling a trace.
Procedure steps
Step
Action
To specify the time (in seconds) to monitor CPU utilization before

triggering a trace, enter the following command.
trace auto-enable high-track-duration <seconds>

disabling the trace, enter the following command:
trace auto-enable low-track-duration <seconds>
End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
149
Variable
Value
<seconds>
seconds is a value from 3 to 10. The

default is 5.
Displaying information about the trace

Use the following procedure to display trace auto-enable information.
Procedure steps
Step
Action
To enable the trace auto-enable feature, use the following command:

trace auto-enable info
"Trace auto-enable info command output" (page 149) shows sample

output for the trace auto-enable info command.
Trace auto-enable info command output
End
Configuring an automatic trace using the NNCLI

Use the procedures in this section to configure an automatic trace using
the NNCLI.
ATTENTION
The enabling or disabling of auto-trace is not saved to the configuration file. When
a Ethernet Routing Switch 8300 reboots, the auto-trace functionality is disabled.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Navigation
"Enabling an auto-trace" (page 150)
"Adding a module" (page 150)
"Removing a module" (page 151)
"Specifying the CPU utilization percentages" (page 151)
"Specifying the time to monitor CPU utilization" (page 152)
Enabling an auto-trace
Use the following procedure to enable the trace auto-enable feature.
Prerequisites
To enable the trace auto-enable feature, the trace auto-enable command

must be used in Privileged EXEC mode.
Procedure steps
Step
Action
To enable the trace auto-enable feature, enter the following

command:
trace auto-enable auto-trace enable
End
Variable
Value
auto-trace <enable|disable>
Enables or disables auto-trace. The

default value is disable.
Adding a module
Use the following procedure to add a module to be traced by the trace
auto-enable feature.
Procedure steps
Step
Action
To add module to be traced, enter the following command.

trace auto-enable add-module <modid> <level>
End
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
151
Variable
Value
<level>
Identifies the level of detail you want in

the trace. For example, 0 = Disabled, 1
= Very Terse. The valid range is 0 to 7.
<modid>
Identifies the module that you want to

add. For example, 3 = Port Manager,
20 = Topology Discovery. The valid
range is 0 to 66. For a list of valid
module IDs, enter trace level ?.
Removing a module
Use the following procedure to remove a module from automatic tracing.
Procedure steps
Step
Action
To remove a module that is being traced by the trace auto-enable

feature, enter the following command.
trace auto-enable remove-module <modid>
End
Variable
Value
<modid>
Identifies the module for which you want

to disable auto-trace. For example,
3 = Port Manager, 20 = Topology
Discovery. The valid range is 0 to 66.
For a list of valid module IDs, enter
trace level ?.
Specifying the CPU utilization percentages

Use the following procedure to specify the CPU utilization percentage above
which tracing is enable and the CPU utilization percentage below which
auto-trace should be disabled.
Procedure steps

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Step
Action
To specify the CPU utilization percentage above which auto trace

must be enabled, enter the following command.
trace auto-enable high-percentage <percent>
To specify the CPU utilization percentage below which auto-trace

should be disabled, enter the following command:
trace auto-enable low-percentage <percent>
End
Variable
Value
high-percentage <percent>
percent is a value from 60 to 100.

The default is 90.
low-percentage <percent>
percent is a value from 50 to 90. The

default is 75.
Specifying the time to monitor CPU utilization

Use the following procedure to specify the time to monitor CPU utilization
before triggering or disabling a trace.
Procedure steps
Step
Action

triggering a trace, enter the following command.
trace auto-enable high-track-duration <seconds>

disabling the trace, enter the following command:
trace auto-enable low-track-duration <seconds>
End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Performing a loopback test
153
Variable
Value
<seconds>
seconds is a value from 3 to 10. The

default is 5.
Performing a loopback test

Use the following sections to perform a loopback test.
Navigation
"Performing a loopback test using the NNCLI" (page 153)
"Performing a loopback test using the CLI" (page 154)
Performing a loopback test using the NNCLI

Use the following procedure to perform a loopback test.
Prerequisites
Before you perform a port loopback test, you must place the port in
loopback mode using the following command
interface FastEthernet <slot/port> test
The loopback command must be executed in Privileged EXEC mode.
Procedure steps
Step
Action
To perform a loopback test, enter the following command:

test loopback <slot/port>
"Test loopback warning message " (page 153) appears when you
perform a loopback test:
Test loopback warning message
To stop a currently running loopback test, enter the following

command:
test stop
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
End
Variable
Value
slot/port

entering the command in the form
portlist {slot/port[-slot/port][, ...]}
Performing a loopback test using the CLI

Use the following procedure to perform a loopback test.
Prerequisites
Before you perform a port loopback test, you must place the port in
loopback mode using the following command
config ethernet <slot/port> test
Procedure steps
Step
Action
To perform a port loopback test, enter the following command:

test loopback <ports>
"Test loopback warning message " (page 154) appears when you
perform a loopback test using the test loopback command.
Test loopback warning message
End

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Configuring the system core image dump
155
Variable
Value
ports

entering the command in the form
portlist {slot/port[-slot/port][, ...]}.

This section describes how to configure the system core image dump using
the CLI and the NNCLI.
System core image dump navigation
"Configuring the system core image dump using the CLI" (page 155)
"Enabling the system core image dump using the NNCLI" (page 157)
Configuring the system core image dump using the CLI

Use the following procedure to preserve a core image of RAM when the
system fails.
Prerequisites
The flash or the PCMCIA card must have enough free space to save a
core save compact file of more than 10 megabytes (MB).
The TFTP server must have write access for a core save normal file of
more than 100 MB .
Procedure steps
Step
Action
Configure the system core image dump by using the following

command:
config [diag] slot <slot#> core-save <enable|disable>
<file>
When a failure occurs, retrieve the file and call 1-800-4NORTEL

(1-800-466-7835).
End
Variable
Value
enable | disable
Enables or disables the system core image

dump. Disabled is the default.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
Variable
Value
file
Specifies the target location to save the core

image. You can save the image to the flash, the
PCMCIA card or a TFTP server.
slot#
Specifies the number of the slot occupied by the

8393 or 8394 card.
Job aid: System core image dump configuration example

You can configure the system core dump with the flash, the PCMCIA card,
or a TFTP server as the target.
Example 1: Configuring the system core image dump with the flash
as a target
Example 2: Configuring the system core image dump with the PCMCIA
card as a target
Example 3 : Configuring the system core image dump with a TFTP

server as a target location
as a target
To enable the system core image dump with the flash as a target location,
use the following command:
Passport-8310:5 config diag slot 5 core-save enable
/flash/cp5_core.zip
card as a target
To enable the system core image dump with the PCMCIA card as a target
location, use the following command:
/pcmcia/cp5_core.zip
To enable the system core image dump with a TFTP server (10.10.10.5)
as a target location, use the following command:
10.10.10.5:cp5_core.zip

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
157
Configuring the system core image dump using the NNCLI

Use the following procedure to preserve a core image of RAM when the
system fails.
Prerequisites
The flash or the PCMCIA card must have enough free space to save
a core save compact file of more than 10 MB.
The TFTP server must have write access for a core save normal file of
more than 100 MB.
Procedure steps
Step
Action
Enable the system core image dump by using the following

command in the Global configuration mode:
core-save <slotlist> [filename <WORD/1-127>]
Verify the configuration by using the following command in the

Privileged EXEC mode:
show core-save [<slotlist>]
When a failure occurs, retrieve the file and call 1-800-4NORTEL

(1-800-466-7835).
End
Variable
Value
filename <WORD/1-127>
Specifies the target location to save the core

image. You can save the image to the flash, the
PCMCIA card or a TFTP server.
slotlist
Specifies the number of the slots occupied by

the 8393 or 8394 cards.
Job aid: System core image dump configuration example

You can configure the system core dump with the flash, the PCMCIA card,
or a TFTP server as the target.
as a target
card as a target
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.

as a target
To enable the system core image dump with PCMCIA as a target location,
use the following command:
Passport-8310:5<config># core-save 5
/flash/cp5_core.zip
To show the system core image dump, use the following command:
Passport-8310:5<config># show core-save 5
The following figure shows the output for this example.
Figure 30
Example 1
card as a target
To enable the system core image dump with the PCMCIA card as a target
location, use the following command:
Passport-8310:5<config># core-save 5 /pcmcia/cp5_core.zip
Passport-8310:5<config># show core-save 5
The following figure shows the output for this example.
Figure 31
Example 2

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
159

To enable the system core image dump with a TFTP server (10.10.10.5)
as a target location, use the following command:
Passport-8310:5 core-save 5 10.10.10.5:cp5_core.zip
Passport-8310:5 show core-save 5
The following figure shows the output for this command.
Figure 32
Example 3

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
161
Understanding alarms, logs, traps, and

system messages
The System Messaging Platform (SMP) creates a scheme for the display
and access of system messages that enhances your access to system
information. For more information, see Nortel Ethernet Routing Switch
8300: Fault Management System Messaging Platform Reference
(NN46200-701).

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
162 Understanding alarms, logs, traps, and system messages

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
163
Troubleshooting configuration
examples
Navigation
"Configuring port mirroring using the NNCLI" (page 163)
"Configuring port mirroring using the CLI" (page 165)
Configuring port mirroring using the NNCLI

The following configuration examples use the commands described
previously to perform the following tasks:
Create an ingress port-mirror
Delete port-mirroring on a port
Change the mode of the port-mirror
Change the mirrored port
Disable port-mirroring on a port
Change the mirroring port
Display mirrored port information
Example 1
To set up ingress port mirroring and set the mode to receive, use the
following command:
Passport-8310:5(config)# port-mirroring 1 rx 2/1 6/4
enable
Example 2
To delete mirroring on a port, use the following command:
Passport-8310:5(config)# no port-mirroring 1

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
164 Troubleshooting configuration examples
Example 3
To change the port mirroring mode, use the following command:
Passport-8310:5(config)# port-mirroring 1 mode tx
Example 4
To change a mirrored port, use the following command:
Passport-8310:5(config)# port-mirroring 1 monitor-port
2/2
Example 5
To disable port mirroring on port 1, use the following command:
Passport-8310:5(config)# port-mirroring 1 disable
Example 6
To change a mirroring port, use the following command:
Passport-8310:5(config)# port-mirroring 1 mirror-port
6/7
Example 7
To display information about port-mirror configuration in a switch, use the
following command:
Passport-8310:5(config)# show port-mirroring
Figure 33 "Show port-mirroring command output" (page 164) shows sample
output for this command.
Figure 33
Show port-mirroring command output

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Configuring port mirroring using the CLI 165
Configuring port mirroring using the CLI

The following configuration examples use the commands described
previously to perform the following tasks:
Create an ingress port-mirror
Delete port-mirroring on a port
Change the mode of the port-mirror
Change the mirrored port
Disable port-mirroring on a port
Change the mirroring port
Display mirrored port information
Example 1
To set up ingress port mirroring and set the mode to receive, use the
following command:
Passport-8310:5/config/diag/mirror-by-port/1# create
in-port 1/1 out port 5/4 mode rx enable true
Example 2
To delete mirroring on a port, use the following command:
Passport-8310:5/config/diag/mirror-by-port/1# delete
Example 3
To change the port mirroring mode to mirror both transmit and receive
packets, use the following command:
Passport-8310:5/config/diag/mirror-by-port/1# mode both
Example 4
To change a mirrored port, use the following command:
Passport-8310:5/config/diag/mirror-by-port/1#
mirrored-port 1/3
Example 5
To disable port mirroring on port 1, use the following command:
Passport-8310:5/config/diag/mirror-by-port/1# enable
false

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
166 Troubleshooting configuration examples
Example 6
To change a mirroring port use the following command:
Passport-8310:5/config/diag/mirror-by-port/1#
mirroring-port 5/5
Example 7
To display information about mirrored ports on the switch, use the following
command:
Passport-8310:5 # show diag mirror-by-port
Figure 34 "Show diag mirror-by-port command output" (page 166) shows
Figure 34
Show diag mirror-by-port command output

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
167
Supported RFCs
The supported Request for Comments (RFCs) are outlined inNortel
Ethernet Routing Switch 8300: Release Notes - Software Release 4.0
(NN46200-401).

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
168 Supported RFCs

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
169
Contacting technical support

Navigation
"Gathering critical information" (page 169)
"Getting Help from the Nortel Web site" (page 170)
"Getting help over the phone from a Nortel Solutions Center" (page 170)
"Getting help from a specialist by using an Express Routing Code"

(page 171)
"Getting help through a Nortel distributor or reseller" (page 171)
Gathering critical information

Before contacting Nortel Technical Support, you must gather information
that can help the technical support personnel when troubleshooting. This
section identifies all of that critical information .
You must attempt to resolve your problem using this troubleshooting
guide. Contacting Nortel is a final step taken only when you have been
unable to resolve the issue using the information and steps provided in
this troubleshooting guide.
Gather the following information before contacting Nortel Tech Support.
Collecting this information helps Nortel analyze and address the reported
issue.
Detailed description of the problem
Date and time when the problem started
Frequency of the problem
Is this a new installation?
Have you searched the solutions database? Did you find any related
solutions? Is there currently a workaround for this issue?
Have you recently changed or upgraded your system, your network, or

a custom application? (For example, has any configuration or code
been changed?)

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
170 Contacting technical support
When were these changes made? Provide the date and time. Who
made these changes? Were the changes made by a partner or
customer? Provide the names of the individuals who made the changes.
Also provide Nortel Technical Support with the following information:
A copy of your configuration files
A copy of the .000 file from the PCMCIA
A detailed network topology diagram
Log files
Output of show tech command
Getting Help from the Nortel Web site

The best way to get technical support for Nortel products is from the Nortel
Technical Support Web site:
www.nortel.com/support
This site provides quick access to software, documentation, bulletins, and
tools to address issues with Nortel products. More specifically, at this site
you can:
download software, documentation, and product bulletins
search the Technical Support Web site and the Nortel Knowledge Base
for answers to technical issues
sign up for automatic notification of new software and documentation

for Nortel equipment
open and manage technical support cases
Getting help over the phone from a Nortel Solutions Center

If you do not find the information you require on the Nortel Technical Support
Web site, and have a Nortel support contract, you can also get help over the
phone from a Nortel Solutions Center.
In North America, call 1-800-4NORTEL (1-800-466-7835).
Outside North America, go to the following Web site to obtain the phone
number for your region:
www.nortel.com/callus

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Getting help through a Nortel distributor or reseller 171
Getting help from a specialist by using an Express Routing Code

To access some Nortel Technical Solutions Centers, you can use an Express
Routing Code (ERC) to quickly route your call to a specialist in your Nortel
product or service. To locate the ERC for your product or service, go to:
www.nortel.com/erc
Getting help through a Nortel distributor or reseller

If you purchased a service contract for your Nortel product from a distributor
or authorized reseller, contact the technical support staff for that distributor
or reseller.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
172 Contacting technical support

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
173
Diagnostics reference
This section contains reference material you can use when you perform
diagnostics on the Ethernet Routing Switch 8300.
Navigation
"Special terminal characters reference" (page 173)
"Edit mode commands reference" (page 174)
"Port numbering and MAC address assignment reference" (page 176)
"Text conventions" (page 179)
Special terminal characters reference

Table 20 "Special terminal characters" (page 173) lists the special terminal
characters.
Table 20
Special terminal characters
Key Combination
Command
^H
Backspace.
^D
Logout of cli.
^C
Abort line entry.
^P
Previous history command.
^N
Next history command.
^S
Output suspend.
^Q
Output resume.
Î
Command completion.
^B
Move cursor back one character.
^F
Move cursor forward one character.
Â
Move cursor to beginning of line.
Ê
Move cursor to end of line.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
174 Diagnostics reference
Key Combination
Command
ESC B
Move cursor back one word.
ESC F
Move cursor forward one word.
DEL
Erase character at cursor.
^K
Erase all characters from cursor to end of line.
^X
Erase all characters before the cursor to beginning of

line.
Û
Erase or clear entire line.
^W
Erase word to left of cursor.
ESC D
Erase from cursor to end of word.
^L
Redisplay line.
^R
Redisplay line.
^T
Transpose the character to left of cursor with character

at cursor.
ESC L
Change character at cursor to lowercase.
ESC U
Change character at cursor to uppercase.
Multiple command terminator.
"..."
Preserve white space in strings.
Edit mode commands reference

To edit a file, type ESC to enter edit mode and use the commands listed
in Table 21 "Commands available in edit mode" (page 174). The ESC key
switches the shell to edit mode. The RETURN key always moves to the
next line.
When you enter the editor, you are in edit mode.
Table 21 "Commands available in edit mode" (page 174) is a summary of
the commands available in edit mode.
Table 21
Commands available in edit mode
Key Combination
Description
:q
Ends the editing mode without saving the changes

made to a file.
:w
Quits and saves the file.
ZZ
Quits and saves the file.
Movement and Search Commands

^L
Redraw screen.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
Edit mode commands reference 175
Key Combination
Description
^F
Display next screen.
^B
Display previous screen.
^D
Display next 1/2 screen.
Û
Display previous 1/2 screen.
<n>G
Go to command number n.
Go to last command line.
/<s>
Search for string s forward in file.
?<s>
Search for string s backward in file.
Repeat last search.
Repeat last search in opposite direction.
<n>k
Get nth previous line in file.
<n>-
Same as "k."
<n>j
Get nth next line in file.
<n>+
Same as "j."
RETURN
Same as "j."
<n>h
Move left n characters.
^H
Same as "h."
<n>l
Move right n characters.
SPACE
Same as "l."
<n>w
Move n words forward.
<n>W
Move n blank-separated words forward.
<n>e
Move to end of the nth next word.
<n>E
Move to end of the nth next blank-separated word.
<n>b
Move back n words.
<n>B
Move back n blank-separated words.
f<c>
Find character c, searching forward.
F<c>
Find character c, searching backward.
Move cursor to first nonblank character in line.
Go to end of line.
Go to beginning of line.
Insert Commands (Input is expected until an ESC is typed)

a
Append.
Append at end of line.
c SPACE
Change character.
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
Key Combination
Description
cl
Change character.
cw
Change word.
cc
Change entire line.
c$
Change everything from the cursor to the end of the line.
Same as "c$."
Same as "cc."
Insert.
Insert at the beginning of the line.
Type over characters.
Open a line below current line.
Open a line above current line.
Editing Commands
<n>r<c>
Replace the following n characters with c.
<n>x
Delete n characters starting at the cursor.
<n>X
Delete n characters to the left of the cursor.
d SPACE
Delete character.
dl
Delete character.
Note: The default value for <n> is 1.
Port numbering and MAC address assignment reference

This section includes information about the following topics:
"Port numbering" (page 176)
"Interface indexes" (page 177)
"MAC address assignment" (page 178)
Port numbering
A port number includes the slot location of the module in the chassis, as
well as the ports position in the I/O module. In the Ethernet Routing Switch
8300, slots are numbered from top to bottom. Figure 35 "8310 chassis
slots" (page 177) shows slot numbering for an 8310 chassis.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Port numbering and MAC address assignment reference 177

Figure 35
8310 chassis slots
Ports are numbered generally from left to right beginning with 1 for the far
left port. On high-density modules with two rows of ports, such as the
8348TX module, ports in the top row are assigned sequential odd numbers,
and ports in the bottom row are assigned sequential even numbers. See
Figure 36 "Port numbers on high-density modules" (page 177).
Figure 36
Port numbers on high-density modules
Interface indexes
Interface indexes are used in Simple Network Management Protocol
(SNMP) to identify ports, Virtual Local Area Networks (VLANs), and
Multi-Link Trunks.
The interface index of a port is computed using the following formula:
ifIndex = (64 x slot number) + (port number 1)
where:
Slot number is a value between 1 and 10, inclusive.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
Port number is a value between 1 and 48, inclusive.
For example, the interface index of port 1/1 is 64, and the interface index
of port 10/48 is 687.
The interface index of a VLAN is computed using the following formula:
ifIndex = 2048 + VLAN ID
Because the default VLAN always has an ID of 1, the interface index is
always 2049.
The interface index of a Multi-Link Trunk (MLT) is computed using the
following formula:
ifIndex = 6144 + MLT_ID -1
MAC address assignment

Understanding how MAC addresses are assigned is important when you
define static ARP entries for IP addresses in the switch and when you use a
network analyzer to decode network traffic.
Each Ethernet Routing Switch 8300 module is assigned a base of 4096
MAC addresses. These MAC addresses can be used for VLANs, ports, or
both. A MAC address has the format shown in Figure 37 "Parts of a MAC
address" (page 178).
Figure 37
Parts of a MAC address
The MAC address is divided into the following parts:
Bits 4724: IEEE OUI (for example, 00-80-2d)
Bits 2312: Chassis ID
Bit 11-0: These last 12 bits represent the:

ifindex for a port MAC address (physical MAC address)
VLAN ID for a VLAN MAC address (virtual MAC address)
The ifindex and the VLAN ID can overlap.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Text conventions
179
Physical MAC addresses

Physical MAC addresses are addresses assigned to the physical interfaces
or ports visible on the device. The physical MAC addresses are used in
the following types of frames:
Spanning Tree Protocol BPDUs sent by the switch
Frames to or from an isolated routing ports physical interface
BPDUs are sent using the physical MAC address as the source because
identifying which physical port sent the BPDU is critical to how the Spanning
Tree Protocol works.
The ports on the switch fabric/CPU module have the following last 12 bits:
Management port in slot 5: 0x3f4
CPU port (an internal port) in slot 5: 0x3f5
Management port in slot 6: 0x3f6
CPU port (an internal port) in slot 6: 0x3f7
Virtual MAC addresses

Virtual MAC addresses are the addresses assigned to VLANs. A virtual
MAC address is assigned to a VLAN when it is created. The MAC address
for a VLAN IP address is the virtual MAC address assigned to the VLAN.
Text conventions
This guide uses the following text conventions:
angle brackets (< >)
Indicate that you choose the text to enter based on

the description inside the brackets. Do not type the
brackets when entering the command.
Example: If the command syntax is
ping <ip_address>, you enter ping
192.32.10.12
bold body text
Indicates objects such as window names, dialog

box names, and icons, as well as user interface
objects such as buttons, tabs, and menu items.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
bold Courier text
Indicates command names, options, and text that

you must enter.
Example: Use the dinfo command.
Example: Enter show ip {alerts|routes}.
braces ({})
Indicate required elements in syntax descriptions

where there is more than one option. You must
choose only one of the options. Do not type the
braces when entering the command.
show ip {alerts|routes}, you must enter
either show ip alerts or show ip routes,
but not both.
brackets ([ ])
Indicate optional elements in syntax descriptions.

Do not type the brackets when entering the
command.
show ip interfaces [-alerts], you can
enter either show ip interfaces or show ip
interfaces -alerts.
ellipsis points (. . . )
Indicate that you repeat the last element of the

command as needed.
ethernet/2/1 [<parameter> <value>]...,
you enter ethernet/2/1 and as many
parameter-value pairs as needed.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Text conventions
italic text
181
Indicates variables in command syntax descriptions.

Also indicates new terms and book titles. Where
a variable is two or more words, the words are
connected by an underscore.
show at <valid_route>,
valid_route is one variable and you substitute one
value for it.
plain Courier text
Indicates command syntax and system output, for

example, prompts and system messages.
Example: Set Trap Monitor Filters
separator ( > )
Shows menu paths.

Example: Protocols > IP identifies the IP command
on the Protocols menu.
vertical line ( | )
Separates choices for command keywords and

arguments. Enter only one of the choices. Do not
type
the vertical line when entering the command.
show ip {alerts|routes}, you enter either
show ip alerts or show ip routes, but not
both.

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
182
Index
A
access policies 59
accessing
NNCLI 25
automatic trace, configuring using the
CLI 146
automatic trace, configuring using the
NNCLI 149
C
clear commands 136, 137
CLI
returning to, from NNCLI 26
commands, NNCLI
modes 23
config cli monitor command 128
config cli montor command 129
config sys syslog commands 87, 92
conventions, text 179
D
diagnostics
error trapping 63
port mirroring 18
E
edit mode commands 174
error trapping 63
errors, collision 124
Ethernet collision errors 124
I
interface index 177
Knowledge and Solution Engine

using 26
L
LEDs
power supplies 37
log files, description 21
loopback testing, descripion 21
M
MAC address assignment 178
managing messages 82
messages
loopback test warning 153, 154
MIBs
checking status 97
checking status details 98
mirror-port, disabling 57
mirror-port, enabling 57
mirroring
port 18
mirroring mode, setting 62
mirroring port, enabling 60
module LEDs
problem indications 37
monitor commands 128, 128, 129, 131, 134
Multi-Link Trunk interface index 178
N
NMM (network management MIB) 97
NNCLI
accessing 25
Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007

.
Index 183
show log commands

level 70
show sys commands
syslog general-info 95
slot numbering 177
switching
to CLI 26
to NNCLI 25
syslog commands, show 91, 95
Syslog severity levels 83
system core image dump
configuring using the CLI 155
configuring using the NNCLI 157
description 22
system log
configuring host 84
description 21
enabling 81
receiving messages 82
System Log Table tab 82,
returning to CLI 26
switching from CLI 25
NNCLI commands
modes 23
P
physical MAC address 179
ping snoop 138
CLI 140
description 20
disable 139
enable 138
NNCLI 138
show ports 140
port mirroring 18
description 18
displaying entries 52
editing existing values 52
egress 18
ingress 18
MAC addresses 18
VLANs 19
port mirroring commands 55, 58
port numbering 177
port statistics, description 20
port-mirroring table entry 56
ports
interface index 178
numbering 176
R
Route tracing, description 20
S
severity codes 83
severity levels
Ethernet Routing Switch 83
mapping 84
Passport 84
syslog 83
system log 83, 84
show interfaces FastEthernet statistics
command 118
table, flushing 136, 137

Telnet sessions
ending 136, 137
terminal characters, special 173
text conventions 179
topology 97
Topology Table tab 98
traceroute command 143, 144
troubleshooting 143, 144
error trapping 63
module LED indications 37
PIM-SM issues in the CLI 39
port mirroring 18
V
VCT
description 21
testing a port using 100
testing multiple ports using 103
virtual MAC address 179
VLAN interface index 178

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
184 Index

Troubleshooting
NN46200-704 01.01 Standard
4.0 29 October 2007
.
Troubleshooting
All Rights Reserved.
Publication: NN46200-704
Document status: Standard
Document version: 01.01
Document date: 29 October 2007
Sourced in Canada and the United States of America
To provide feedback or report a problem in this document, go to www.nortel.com/documentfeedback.
LEGAL NOTICE
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing
NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR
IMPLIED. The information and/or products described in this document are subject to change without notice.
Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
IEEE is a trademark of the Institute of Electrical and Electronics Engineers, Inc.
All other trademarks are the property of their respective owners.

8300

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

8300

Diunggah oleh

Hak Cipta:

Format Tersedia

Nortel Ethernet Routing Switch 8300

Downloaded from www.Manualslib.com manuals search engine

(323321-A Rev 01)

Document status: Standard

Nortel Networks software license agreement

Downloaded from www.Manualslib.com manuals search engine

Limitation of Remedies. IN NO EVENT SHALL NORTEL NETWORKS OR ITS AGENTS OR SUPPLIERS BE

Downloaded from www.Manualslib.com manuals search engine

Downloaded from www.Manualslib.com manuals search engine

Proper installation and routine maintenance 13

Nortel Ethernet Routing Switch 8300

Downloaded from www.Manualslib.com manuals search engine

Troubleshooting the Ethernet Routing Switch 8300 hardware 37

Troubleshooting PIM-SM issues in the CLI 39

Downloading Ethernet Routing Switch 8300 software 47

Nortel Ethernet Routing Switch 8300

Downloaded from www.Manualslib.com manuals search engine

Nortel Ethernet Routing Switch 8300

Downloaded from www.Manualslib.com manuals search engine

Understanding alarms, logs, traps, and system messages

Troubleshooting configuration examples

Configuring port mirroring using the NNCLI 163

Contacting technical support

Gathering critical information 169

Special terminal characters reference 173

Nortel Ethernet Routing Switch 8300

Downloaded from www.Manualslib.com manuals search engine

New in this release

"Other changes" (page 9)

System core image dump

Ethernet Routing Switch 8300: Performance Management Diagnostic

Ethernet Routing Switch 8300: Performance Management Diagnostic

Nortel Ethernet Routing Switch 8300

Downloaded from www.Manualslib.com manuals search engine

10 New in this release

Nortel Ethernet Routing Switch 8300

Downloaded from www.Manualslib.com manuals search engine

Device Manager is a graphical user interface (GUI) used to configure

To learn the basic structure and operation of the NNCLI, refer to

To learn the basic structure and operation of the CLI, refer to

basic knowledge of networks, Ethernet bridging, and IP routing

familiarity with networking concepts and terminology

Copyright 2007, Nortel Networks

Downloaded from www.Manualslib.com manuals search engine

experience with windowing systems or GUIs

basic knowledge of network topologies

"Troubleshooting planning" (page 13)

"Troubleshooting fundamentals" (page 17)

"Initial troubleshooting" (page 23)

"Hardware troubleshooting" (page 37)

"Software troubleshooting" (page 39)

"Downloading software" (page 47)

"Troubleshooting tools" (page 49)

"Understanding alarms, logs, traps, and system messages" (page 161)

"Troubleshooting configuration examples" (page 163)

"Supported RFCs" (page 167)

"Contacting technical support" (page 169)

"Diagnostics reference" (page 173)

Nortel Ethernet Routing Switch 8300

Downloaded from www.Manualslib.com manuals search engine

the proper installation and routine maintenance for your system

the configuration of your network

the normal behavior of your network