NN46220-701 - 01.01 - TRBL - CFM Y1731

Nortel Metro Ethernet Routing Switch 8600
Troubleshooting
NN46220-701 (323745-A Rev 01)

.
Document status: Standard
Document version: 01.01
Document date: 3 August 2007
Copyright © 2007, Nortel Networks

All Rights Reserved.
Sourced in Canada and the United States of America
This document is protected by copyright laws and international treaties. All information, copyrights and any other
intellectual property rights contained in this document are the property of Nortel Networks. Except as expressly
authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein and
this document shall not be published, copied, produced or reproduced, modified, translated, compiled, distributed,
displayed or transmitted, in whole or part, in any form or media.
The information in this document is subject to change without notice. The statements, configurations, technical
data, and recommendations in this document are believed to be accurate and reliable, but are presented without
express or implied warranty. Users must take full responsibility for their applications of any products specified in this
document. The information in this document is proprietary to Nortel Networks Inc.
The software described in this document is furnished under a license agreement and may be used only in accordance
with the terms of that license. The software license agreement is included in this document.
Restricted rights legend

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer
software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth
in the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.
Nortel Networks Inc. 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 Customer’s 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 MERCHANTABILITY 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, CUSTOMER’S 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 forgoing 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
Customer’s 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.
5
Contents
New in this release 9
Features 9
Other changes 9
Introduction 11
Acronyms 11
Troubleshooting fundamentals 15
Transparent Domain Continuity 16
Connectivity Fault Management 16
Y.1731 Performance Monitoring 17
Digital Diagnostic Monitoring 17
Port mirroring 17
Remote mirroring 18
Ping snoop 19
Packet capture tool 19
System log (syslog) 20
General diagnostic tools 20
Troubleshooting planning 21
Proper installation and routine maintenance 21
Network configuration 21
Site network map 22
Logical connections 22
Device configuration information 22
Other important data about your network 22
Normal behavior on your network 22
Initial troubleshooting 25
Using the Knowledge and Solution Engine 25
Gathering information 26
Displaying configuration information using the show config command 27
Displaying system status using the show tech command 28
Using log files 28
Viewing the software version 28
Providing a network topology diagram 29

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
6 Contents
Changes to your system or network 29
Hardware troubleshooting 31
Troubleshooting the Metro Ethernet Routing Switch 8600 hardware 31
LED indications of problems 31
Apparent module failure 33
Failure to get a login prompt from the console port 34
Cable connection problems 34
Using Digital Diagnostic Monitoring 35
Viewing DDI information using Device Manager 36
Viewing DDI information using the CLI 40
Troubleshooting a nonworking link 45
Software troubleshooting 47
Using Transparent Domain Continuity 47
Using Transparent Domain Continuity with Device Manager 48
Using Transparent Domain Continuity with the CLI 57
Using Connectivity Fault Management 75
Configuring CFM using Device Manager 75
Configuring CFM using the CLI 93
Using Y.1731 Performance Monitoring 113
Configuring PM using Device Manager 114
Configuring PM using the CLI 123
Using port mirroring 134
Configuring port mirroring using Device Manager 135
Configuring port mirroring using the CLI 143
Using remote port mirroring 152
Configuring ports for remote mirroring using Device Manager 153
Configuring ports for remote mirroring using the CLI 155
Troubleshooting IS-IS 159
CLI debug commands 159
Other troubleshooting issues 162
Troubleshooting using a network manager 163

Troubleshooting with Device Manager 163
Downloading software 165

Downloading MERS 8600 software 165
Downloading ESU 1800 software 165
Downloading ESU 1850 software 166
Troubleshooting tools 167

Trapping errors using Device Manager 167
Log files using the CLI 168
Configuring log files 169
Displaying log information 171

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Contents 7
Displaying level information 173

Using syslog 174
Using the system log with Device Manager 174
Using the system log with the CLI 179
Monitoring ports 188
Monitoring how often a port goes down 188
Showing port statistics 189
Monitoring port statistics 191
Clearing statistics 194
Running a trace test 199
Running a trace route test using Device Manager 199
Viewing trace route results using Device Manager 201
Viewing the trace route probe history using Device Manager 203
Tracing the route to a remote host using the CLI 204
Configuring an automatic trace using the CLI 205
Using ping snoop 208
Configuring ping snoop 209
Running a ping test 211
Viewing the ping probe history 214
Viewing a ping result 215
Performing a loopback test 216
Prerequisites 216
Testing the switch fabric and address resolution table 217
Testing the switch fabric 217
Viewing address resolution statistics 219
Displaying the address resolution table using the CLI 222
Checking the MIB status 223
Viewing topology status information 224
Viewing the MIB topology table 225
Using rapid ping 226
Navigation 226
Configuring rapid ping using Device Manager 227
Enabling responses to pings in the data path using Device Manager 229
Testing traffic using rapid ping in the CLI 230
Configuring the ESU for a customer rapid ping request 241
Example of enabling the ESU for a rapid ping response 242
Example of configuring the default gateway 243
Understanding alarms, logs, traps, and system messages 245

Supported RFCs 247
Contacting technical support 249
Gathering critical information 249
Getting Help from the Nortel Web site 250

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
8 Contents
Getting help over the phone from a Nortel Solutions Center 250
Getting help from a specialist by using an Express Routing Code 251
Getting help through a Nortel distributor or reseller 251
Troubleshooting configuration examples 253

Configuring port mirroring on an R module using the CLI 253
Creating an ACT 253
Creating ACL 1 254
Adding ACEs to ACL 1 254
Enabling port mirroring 255
Configuring port mirroring on an R module using Device Manager 255
Creating an ACT 255
Creating an ACL 257
Adding ACEs to the ACL 258
Configuring remote port mirroring on a legacy module using the CLI 262
Configuring ping snoop on R modules 265
Configuring ping snoop using the CLI 265
Configuring ping snoop using Device Manager 266
Diagnostics reference 269

Special terminal characters reference 269
Edit mode commands reference 270
Port numbering and MAC address assignment reference 272
Port numbering 272
Interface indexes 273
MAC address assignment 274
Trap error messages reference 275
Proprietary traps 275
Standard traps 292
Tap and OctaPID assignment reference 298

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
9
New in this release

The following sections detail what’s new in Nortel Metro Ethernet Routing
Switch 8600 Troubleshooting (NN46220-701) for Release 4.2.
Features
The following features are new for Release 4.2:
• Y.1731 Performance Monitoring functionality is added for PBT and
client-level service instances. See "Using Y.1731 Performance
Monitoring" (page 113).
• Port mirroring functionality at the endpoint level (service level) has
been extended to R modules on Local TLS and ESU Ring/SA ports.
The packets are mirrored before encapsulation at ingress and after
decapsulation at egress. See "Configuring port mirroring using Device
Manager" (page 135) and "Configuring port mirroring using the CLI"
(page 143).
• You can now get a count of the total MAC addresses and IP addresses
learnt against Customer IP VLANs on an ESM port or R-module lane.
See "Displaying the MAC and IP count " (page 140) and "Displaying the
MAC and IP count" (page 151).
• The ESU responds to ESU or customer-generated rapid ping requests
(in the data path), received through an ESU or other customer device
on the Metro ERS 8600. Additionally, the ESU can initiate rapid pings
outside the IP subnet. For more information, see "Using rapid ping"
(page 226).
Other changes
Nortel Metro Ethernet Routing Switch 8600 Troubleshooting (NN46220-701)
is a new document for Metro Ethernet Routing Switch 8600 Release 4.2.
Some of the content in this document originally appeared in the following
sources:
• Nortel Metro Ethernet Routing Switch 8600 Diagnostics (NN46220-700);
this document is now obsolete
• Nortel Metro Ethernet Routing Switch 8600 Configuration — UNI and
Endpoints for non-PBT VPN (NN46220-506)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
10 New in this release
• Nortel Metro Ethernet Routing Switch 8600 Configuration — Provider

Backbone Transport (NN46220-504)
• Nortel Fundamentals — Digital Diagnostic Monitoring (NN46220-102);
this document is now obsolete
• Nortel Metro Ethernet Services Unit 1850 Configuration — Ethernet
Layer 2 Switch Mode using the Command Line Interface (NN46211-501)
• Nortel Metro Ethernet Services Unit 1850 Configuration — Layer 2
Switch Mode Using Device Manager (NN46211-503)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
11
Introduction
The Nortel Metro Ethernet Routing Switch 8600 (MERS 8600) is a flexible
and multifunctional switch that supports a diverse range of network
architectures and protocols. This guide provides procedural information to
help you troubleshoot and isolate problems in your MERS 8600 network
Navigation
• "Troubleshooting fundamentals" (page 15)
• "Troubleshooting planning" (page 21)
• "Initial troubleshooting" (page 25)
• "Hardware troubleshooting" (page 31)
• "Software troubleshooting" (page 47)
• "Troubleshooting using a network manager" (page 163)
• "Downloading software" (page 165)
• "Troubleshooting tools" (page 167)
• "Understanding alarms, logs, traps, and system messages" (page 245)
• "Supported RFCs" (page 247)
• "Contacting technical support" (page 249)
• "Troubleshooting configuration examples" (page 253)
• "Diagnostics reference" (page 269)
Acronyms
This guide uses the following acronyms:
ACL Access Control List

ARP Address Resolution Protocol
ATM Asynchronous Transfer Mode
BPDU Bridge Protocol Data Unit
BootP Bootstrap Protocol

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
12 Introduction
CCM Continuity Check Message

CFM Connectivity Fault Management
CoS Class of Service
CLI Command Line Interface
DA Destination Address
DDI Digital Diagnostic Interface
DDM Digital Diagnostic Monitoring
DMM Delay Measurement Message
DMR Delay Measurement Reply
DS Differentiated Services
ELAN Emulated Local Area Network
CPU Central Processing Unit
CRC Cyclic Redundancy Check
DDI Digital Diagnostic Monitoring
FD Frame Delay
FDB Forwarding Database
FDV Frame Delay Variation
FLR Frame Loss Ratio
GbE, GE Gigabit Ethernet
ICMP Internet Control Message Protocol
IDS Intrusion Detection System
IP Internet Protocol
IPS Intrusion Prevention System
I/O Input/Output
IST Inter Switch Trunk
LBM Loopback Message
LBR Loopback Reply
LMM Loss Measurement Message
LMR Loss Measurement Reply
MA Maintenance Association
MAC Media Access Control
MD Maintenance Domain
MEP Maintenance Endpoint
MIB Management Information Base
MIP Maintenance Intermediate Point

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Acronyms 13
MLT MultiLink Trunking

NNI Network-to-Network Interface
OSPF Open Shortest Path First
PBT Provider Backbone Transport
PCAP Packet Capture Tool
PM Performance Monitoring
RMS remote mirroring source
SA source address
RMEP Remote Maintenance Endpoint
RMT Remote Mirroring Termination
RMON Remote Monitoring
RTT Round-Trip-Time
SFP Small Form-factor Pluggable
SMLT Split MultiLink Trunking
SNMP Simple Network Management Protocol
STG Spanning Tree Group
TCN Transmission Control Notification
TD Transparent Domain
TDC Transparent Domain Continuity
UDP User Datagram Protocol
UNI User-to-Network Interface
VACM View-Based Access Control Model
VLAN Virtual Local Area Networks

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
14 Introduction

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
15
Troubleshooting fundamentals
This section provides conceptual information about the methods and
tools that you can use to troubleshoot and isolate problems in your Metro
Ethernet Routing Switch 8600 (MERS 8600) network.
The types of problems that typically occur with networks involve connectivity
and performance. The MERS 8600 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 MERS 8600 supports a wide range of diagnostic tools

that you can use to monitor and analyze traffic; monitor laser operating
characteristics; capture and analyze data packets; trace data flows; view
statistics; and manage event messages.
Certain protocols and tools are tailored for troubleshooting specific MERS
8600 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 MERS 8600.
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.
The following provides a summary of the different troubleshooting tools

and their application.
Navigation
• "Transparent Domain Continuity" (page 16)
• "Connectivity Fault Management" (page 16)
• "Digital Diagnostic Monitoring" (page 17)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
16 Troubleshooting fundamentals
• "Port mirroring" (page 17)

• "Ping snoop" (page 19)
• "Packet capture tool" (page 19)
• "System log (syslog)" (page 20)
• "General diagnostic tools" (page 20)
Transparent Domain Continuity

Transparent Domain Continuity (TDC) is a connectivity and fault detection
mechanism that provides end-to-end data packet path validation per
transparent domain (TD) in service provider (SP) networks. TDC supports
Optical Ethernet Layer 2 (OEL2), which is the precursor to Nortel’s proposed
802.1ah standard.
You can use TDC to test the data flow from the Metro Ethernet Routing
Switch 8600 through the SP network to another Metro Ethernet Routing
Switch 8600, to a UNI on an OM1000 ESM, or to a UNI or NNI interface
on the Optical Metro 3500 multiservices platform with the Optical Packet
Edge System.
For conceptual information about TDC, see Nortel Metro Ethernet Routing
Switch 8600 Fundamentals (NN46220-100).
Connectivity Fault Management

Connectivity Fault Management (CFM) (IEEE standard 802.1ag) is a
connectivity and fault detection mechanism that ensures the delivery
of services by verifying the path and isolating faults to the destination.
CFM accomplishes this by sending the following three message types to
endpoints within the domain:
• Continuity Check Message (CCM)
• Loopback Message (LBM)
• Linktrace Message (LTM)
CFM supports both Provider Backbone Bridging (PBB), which complies with
the 802.1ah standard, and Provider Backbone Transport (PBT).
Provider Backbone Transport (PBT) sends CCM packets to endpoints within

the maintenance domain (MD) to detect, verify, and isolate connectivity
failures.
Loopback messages test the connection between maintenance points (MP).

You can also use Loopback messages to diagnose faults in the network
and to measure performance.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Port mirroring 17
Linktrace messages isolate faults by tracing the hop-by-hop path to the

destination maintenance endpoints (MEP) or maintenance intermediate
points (MIP). All the MPs along the path to the destination intercept the
linktrace messages and send a reply. This enables you to isolate failures to
smaller segments of the network.
For conceptual information about CFM, see Nortel Metro Ethernet Routing
Switch 8600 Fundamentals (NN46220-100).
Y.1731 Performance Monitoring

Y.1731 is the ITU-T standard that measures Performance Monitoring (PM),
which can assist you with service level agreements (SLA) assurance and
capacity planning. This standard complements the CFM functionality
defined by IEEE 802.1ag. The MERS 8600 Y.1731 PM functionality
supports PBT and client-level service instances.
You can use PM to measure the following point-to-point connection metrics:

frame loss ratio, frame delay, and frame delay variation.
Digital Diagnostic Monitoring

Digital Diagnostic Monitoring (DDM) enables you to monitor laser operating
characteristics such as temperature, voltage, current, and power. This
feature works at any time during active laser operation without affecting
data traffic. There are two optical transceivers that support DDM: Small
Form-factor Pluggable (SFP) tranceivers and 10 Gigabit SFPs (XFP).
An interface that supports DDM is called a Digital Diagnostic Interface (DDI).

These devices provide real-time monitoring of individual DDI SFPs and
XFPs on a variety of Nortel products. The DDM software provides warnings
or alarms when the temperature, voltage, laser bias current, transmitter
power or receiver power fall outside of vendor-specified thresholds during
initialization.
Use DDM for monitoring your Small Form-factor Pluggable (SFP) tranceivers
and 10 Gigabit SFPs (XFP).
For information about DDM, SFPs and XFPs, see Nortel Metro Ethernet
Routing Switch 8600 Installation — SFP and XFP Transceivers and GBICs
(NN46225-301).
Port mirroring
The MERS 8600 has a port mirroring feature that you can use to monitor
and analyze network traffic flowing on a port. The MERS 8600 supports
both ingress (incoming traffic) and egress (outgoing traffic) port mirroring.
When using port mirroring, you specify a destination port to see mirrored
traffic and specify the source ports from which traffic is mirrored. Any

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
packet ingressing or egressing a specified port is forwarded normally, and

a copy of the packet is sent out to the mirroring or destination port to be
observed using a network analyzer. When this feature is active, all packets
received on the specified source ports are copied to the port specified as
the destination. The mirroring operation is nonintrusive.
In addition, you can use the Virtual Local Area Network (VLAN) forwarding
database feature to monitor traffic for Media Access Control (MAC)
addresses where traffic with a given source or destination MAC address
is copied to the mirror port.
Remote mirroring
The remote mirroring feature steers mirrored traffic through a switch cloud
to a network analysis probe located on a remote switch. With this feature,
you can monitor many ports from different switches using one network
probe device. This is achieved by encapsulating mirrored packets in a
remote mirroring encapsulation wrapper. The encapsulated frame is bridged
though the network by a separate port-based VLAN to the remote mirroring
termination (RMT) port. At the termination port, the encapsulation header is
removed before sending the packet out of the port.
The remote mirroring feature uses a specific VLAN if remote mirroring is

enabled on the port mirroring destination port. The VLAN ID is set in the
monitor tag field of the remote mirrored packet. With this feature, the user
can segregate the remote mirrored traffic to a single VLAN in the entire
network.
"Remote mirroring" (page 19) shows remote mirroring operations in a

network. Although the ERS 8600 is shown, the MERS 8600 operates in
an identical manner.
Port mirroring and remote port mirroring are features that can negatively
impact normal traffic. Mirrored traffic is always handled with lower priority
(ingress, egress, or in the switch fabric). Use these features only for
troubleshooting, debugging, or for some security purposes like packet
sniffing, intrusion detection system (IDS), or intrusion prevention system
(IPS).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Packet capture tool 19
Remote mirroring
Ping snoop
You can use the ping snoop feature to troubleshoot MultiLink Trunking (MLT)
and Split MultiLink Trunking (SMLT) networks. Ping snoop 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.
ATTENTION
There is no mechanism to prevent line rate ICMP traffic from going to the CPU as
a result of enabling ping snoop.
Packet capture tool

The Packet Capture Tool (PCAP) is a data packet capture tool that captures
ingress and egress packets on selected I/O ports. With this feature, you can
capture, save, and download one or more traffic flows through the MERS
8600. The captured packets can then be analyzed offline for troubleshooting
purposes. This feature is based on the mirroring capabilities of the I/O ports.
All captured packets are stored in the secondary CPU, used as the PCAP
engine. The primary CPU maintains its protocol handling and is not affected
by any PCAP capture activity.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
ATTENTION
PCAP is not supported on R modules.
For more information about PCAP, see Using the Packet Capture (PCAP)
Tool (315023-E).
System log (syslog)

On any UNIX-based management platform, you can use the system log
(syslog) messaging feature to manage event messages. The MERS 8600
syslog software communicates with a server software component named
syslogd on your management workstation.
The UNIX daemon syslogd is a software component that receives and

locally logs, displays, prints, and forwards messages that originate from
sources internal and external to the workstation. For example, syslogd
on a UNIX workstation concurrently handles messages received from
applications running on the workstation, as well as messages received from
a MERS 8600 running in a network accessible to the workstation.
General diagnostic tools

The Metro Ethernet Routing Switch 8600 has diagnostic features available
with Device Manager (DM) and the Command Line Interpreter (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
NN46220-701 01.01 Standard
4.2 3 August 2007
.
21
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:
• that your system is properly installed and routinely maintained
• your network’s configuration
• your network’s normal behavior
Navigation
• "Proper installation and routine maintenance" (page 21)
• "Network configuration" (page 21)
• "Normal behavior on your network" (page 22)
Proper installation and routine maintenance

See Nortel Metro Ethernet Routing Switch 8600 Installation — Chassis
Installation and Maintenance (NN46220-305) for detailed installation
information. This document also outlines the routine tasks required for
operating the Metro Ethernet Routing Switch 8600.
Network configuration
To keep track of your network’s 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 22)
• "Logical connections" (page 22)
• "Device configuration information" (page 22)
• "Other important data about your network" (page 22)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
22 Troubleshooting planning
Site network map

A site network map Identifies where each device is physically located 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

You should maintain online and paper copies of your device configuration
information. Ensure that all online data is stored with your site’s 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 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. The
inventory allows you 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 when 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
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Normal behavior on your network 23
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. This normal data can then be used 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 device’s response time
and when you are troubleshooting you can use these baseline response
times to help you troubleshoot.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
24 Troubleshooting planning

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
25
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 you system. It is a good practice to
gather critical information prior to contacting Technical Support.
Navigation
• "Using the Knowledge and Solution Engine" (page 25)
• "Gathering information" (page 26)
Using the Knowledge and Solution Engine

The Knowledge and Solution Engine allows you 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.
• Software: Includes software patches and software releases.
• Solutions: Includes troubleshooting solutions written by the Nortel
Technical Support team.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
26 Initial troubleshooting
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
1 Go to the Nortel Web site: www.nortel.com

2 Log in using user name and password.
3 Select SUPPORT & TRAINING.
4 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.
5 Enter your problem statement or question in the text box.
Ensure that you leave spaces between the words in the statement
or question.
6 From the ALL TYPES drop-down list, select the document type you
would like to search against.
The default is ALL TYPES, which searches on all available
documents (bulletins, documentation, services requests, software,
and solutions).
7 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—
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

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
• output from the show tech command

• output from the show port stats show-all and show port
error show-all commands
• log files
• software version
• topology of the network
• a list of any changes made prior to the issue (such has software,
hardware, upgrades)
Navigation
• "Displaying configuration information using the show config command"
(page 27)
• "Displaying system status using the show tech command" (page 28)
• "Using log files" (page 28)
• "Viewing the software version" (page 28)
• "Providing a network topology diagram" (page 29)
• "Changes to your system or network" (page 29)
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
1 To display information about the configuration of the switch

information, enter the following command:
show config
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—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
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
1 To display information about the status of the system and switch

information, enter the following command:
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.
For more information about configuring and displaying log files, see "Log
files using the CLI" (page 168).
Viewing the software version

The show sys sw commands displays the software version that is running
on all cards.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 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 that shows
the nodes and connections. This visual depiction of your network is very
helpful to Technical Support when they are assessing your problem.
Changes to your system or network

When troubleshooting a problem you should 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.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
31
Hardware troubleshooting
Use the tasks in this section to troubleshoot problems related to the Metro
Ethernet Routing Switch 8600 (MERS 8600) hardware components.
Navigation
• "Troubleshooting the Metro Ethernet Routing Switch 8600 hardware"
(page 31)
• "Using Digital Diagnostic Monitoring" (page 35)
Troubleshooting the Metro Ethernet Routing Switch 8600 hardware

The following sections provide troubleshooting information for some of the
more common problems that you may encounter with the Metro Ethernet
Routing Switch 8600.
Navigation
• "LED indications of problems" (page 31)
• "Apparent module failure" (page 33)
• "Failure to get a login prompt from the Console port" (page 34)
• "Cable connection problems" (page 34)
LED indications of problems

"LED problem indicators" (page 31) lists possible problems indicated by the
LEDs on the switch modules and suggests corrective action.
LED problem indicators

Symptom Probable cause Corrective action
Green AC power supply The switch is not receiving Verify that each AC power cord is
LEDs are off. AC power or the power fastened securely at both ends and
supply has failed. that power is available at each AC
power outlet. Plug in a device such

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
32 Hardware Troubleshooting

as a lamp to ensure that the power
outlet is operational. Verify that each
power supply is turned on.
The Link/Activity LED for The switch is experiencing Verify that the cable connections to
a connected port is off a port connection problem, the link partner are correct. Verify
or does not blink (and or the switch’s link partner port configuration parameters for both
you believe that traffic is is not auto-negotiating ends of the connection. Move the
present). properly. cable to another port to see whether
the problem occurs on the new port.
The Link/Activity LED There may be a high traffic Verify port configuration parameters
blinks continuously. load or possible packet for both ends of the connection.
broadcast storm.
The Online LED is steady Software incompatibility Use the show log command to
amber for longer than 3 exists, or the module check the system log for indications
minutes. cannot communicate with of communication problems. Use the
the master module over the boot command to download a new
backplane. software image.
The Master LED on a The module has detected Replace the module; make sure that
module in slot 1 or slot 2 is a system clock generation it is in the correct slot.
amber. failure on its own circuitry.
This LED has significance only for the
module in slot 1 or slot 2 that provides
the clock function for the switch.
The Fault LED is blinking A chassis failure has been From the console management
amber. detected. station, use the show log command
to check the system log for information
about hardware failures.
Check the fan tray in the Ethernet

Routing Switch 8000 Series chassis
to make sure both fans are running.
Check the switch power supplies; one

may have stopped functioning.
The module may have failed to read

the MAC address from the chassis
backplane. If this is the case, arrange
to replace the chassis.
The Fault LED is steady The module failed its Replace the module.
amber. power-on self-test. A
diagnostic or hardware
failure has been detected.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Troubleshooting the Metro Ethernet Routing Switch 8600 hardware 33

No LEDs are lit. A hardware failure has Turn the switch power off and then
been detected. turn it on again.
The statistics and LEDs on Unknown Reset the hardware.
the front panel freeze.
LED on a port blinks green The port is administratively Enable the port if traffic needs to run
at a steady rate. disabled. over it.
Apparent module failure

If a module failure occurs, check for possible backplane connection
problems. Make sure that the module is correctly seated in the backplane
connector and that the retaining screws are securely tightened.
If a module fails during module initialization and the replacement module is

the same module type, in rare cases the new module may not initialize.
To work around this issue, follow the steps in either work around 1 or 2.
Module failure work around 1
Step Action
1 Remove the faulty module.
2 Insert a module type that is different from the module type removed
in Step 1 and wait for this replacement module to initialize.
3 Remove the module inserted in Step 2.
4 Insert a new module model in the same slot as the faulty module
resided. This new module model must be identical to the module
model removed in Step 1.
—End—
Module failure work around 2
Step Action
1 Remove the faulty module.

2 Insert a new module.
3 Reboot the chassis.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
If the module still fails to operate, contact the Nortel Technical Solutions
Center for assistance.
Failure to get a login prompt from the console port

If you connect a terminal to the Console port of the 8691omSF, or
8692omSF CPU module and you fail to get a login prompt, the port may
have an incorrect DCE/DTE setting. Try moving the DCE/DTE switch from
its current setting to the other position ("DCE/DTE switch" (page 34)).
DCE/DTE switch
Cable connection problems

Port connection problems can usually be traced to a poor cable connection
or to an improper connection of the port cables at either end of the link. To
remedy such problems, make sure that the cable connections are secure
and that the cables are connected to the correct ports at both ends of the
link.
10BASE-T cables
Cabling for 10BASE-T networks can consist of two-pair Category 3, 4, or
5 unshielded twisted pair (UTP) wiring. However, to prepare for future
upgrades to Fast Ethernet, Nortel strongly recommends that you use all
Category 5 cable in your network.
Ethernet 10BASE-T network installations use cables consisting of two pairs

of twisted pair wires—one pair to send data and one to receive data. These
wires must connect to another 10BASE-T station that has the sending pair
attached to its receiving pair and vice versa. If the two nodes are wired
alike, they both attempt to send data out on the same RJ-45 pins. In such
a case, a straight-through cable would not work. However, a crossover
cable would operate normally.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The 8648TXE, 8648TXM, and 8632TXE modules are designed to have

Ethernet network interface cards (NICs) connect directly to their RJ-45 ports
using straight-through cables. The NIC port types are MDI. However, if a
8648TXE, 8648TXM, or 8632TXE module must connect to a hub or another
switch that follows usual conventions, a crossover cable is required because
the port types are MDI-X. You only need crossover cables when connecting
cables to devices that have the same port type.
100BASE-T and 1000BASE-T cables

The 100 Mb/s ports and 1 Gb/s ports are designed to operate using
Category 5 UTP cabling only. Category 5 UTP cable is a two-pair cable
certified to handle up to 100 Mb/s bandwidth. To minimize crosstalk noise,
maintain the twist ratio of the cable up to the point of termination; untwist at
any termination should not exceed 0.5 in. (1.27 cm).
GBIC cables
Cables for the GBICs vary depending on the specific GBIC type. For
information about the cable requirements for GBICs, see Nortel Metro
Ethernet Routing Switch 8600 Installation — SFP and XFP Transceivers
and GBICs (NN46225-301).
For information about troubleshooting SFP, XFP, and GBIC components,

see "Using Digital Diagnostic Monitoring" (page 35).
Using Digital Diagnostic Monitoring

This section shows you how to use Digital Diagnostic Monitoring (DDM) on
individual Digital Diagnostic Interface (DDI) SFPs and XFPs to perform
real-time monitoring of laser operating characteristics, such as temperature,
voltage, current, and power.
You can use DDM at any time during active laser operation without affecting
data traffic. The DDM software provides warnings or alarms when the
temperature, voltage, laser bias current, transmitter power or receiver
power fall outside of vendor-specified thresholds during initialization. For
logging purposes, DDM warning and alarm messages are mapped into the
WARNING and FATAL message categories.
Navigation
• "Viewing DDI information using Device Manager" (page 36)
• "Viewing DDI information using the CLI" (page 40)
• "Troubleshooting a nonworking link" (page 45)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Viewing DDI information using Device Manager

View DDI information (such as module information, temperature, and
voltages) to monitor the SFPs and XFPs on the 30-port 1 GE 8630 module
and the 3-port 10 GE 8683 R modules.
Procedure steps
Step Action
1 In the Device view, double left-click a port, or select a port and select
Edit > Port.
The Interface tab appears.
Port dialog box, Interface tab

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
2 Select the DDI/SFP tab.

The DDI/SFP tab appears (see "Port dialog box, DDI/SFP tab" (page
37)).
Port dialog box, DDI/SFP tab
For information about the DDI fields, see the following table.
3 Click Refresh to update the statistics.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Variable definitions
Variable Value
DdmStatus Indicates if DDM is enabled.
Calibration Indicates if the calibration is internal or external.
PowerMeasure Indicates Rx power measurement as average or OMA.
ConnectorType Indicates the type of SFP or XFP connector.
VendorName Indicates the name of the SFP or XFP manufacturer.
VendorPartNumber Indicates the Nortel PEC for the SFP or XFP
VendorRevNumber Indicates the manufacturer revision level for the SFP or XFP.
VendorSN Indicates the manufacturer serial number for the SFP or XFP.
VendorDateCode Indicates the manufacturer date code for the SFP or XFP.
CLEI Indicates the Telcordia register assignment Nortel CLEI code.
SupportsDDM Indicates if the SFP or XFP supports DDM.
Aux1Monitoring Indicates if auxiliary monitoring is implemented for the XFP.
Aux2Monitoring Indicates if auxiliary monitoring is implemented for the XFP.
Wavelength Indicates the wavelength in nm of the SFP or XFP.
Temperature Indicates the current temperature in degrees Celsius of the SFP
or XFP.
TemperatureHighAlarmThresh Indicates the high alarm threshold in degrees Celsius.
old
TemperatureLowAlarmThresh Indicates the low alarm threshold in degrees Celsius.
old
TemperatureHighWarningThr Indicates the high warning threshold in degrees Celsius.
eshold
TemperatureLowWarningThre Indicates the high warning threshold in degrees Celsius.
shold
TemperatureStatus Indicates if any temperature thresholds were exceeded.
Voltage Indicates the current voltage in volts.
VoltageHighAlarmThreshold Indicates the high alarm threshold in volts.
VoltageLowAlarmThreshold Indicates the low alarm threshold in volts.
VoltageHighWarningThreshold Indicates the high warning threshold in volts.
VoltageLowWarningThreshold Indicates the high warning threshold in volts.
VoltageStatus Indicates if any voltage thresholds were exceeded.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
Bias Indicates the laser bias current in mA.
BiasHighAlarmThreshold Indicates the bias current high alarm threshold in mA.
BiasLowAlarmThreshold Indicates the bias current low alarm threshold in mA.
BiasHighWarningThreshold Indicates the bias current high warning threshold in mA.
BiasLowWarningThreshold Indicates the bias current high warning threshold in mA.
BiasStatus Indicates if any bias thresholds were exceeded.
TxPower Indicates the current Tx power in mW.
TxPowerHighAlarmThreshold Indicates the high alarm threshold in mW for the Tx power.
TxPowerLowAlarmThreshold Indicates the low alarm threshold in mW for the Tx power.
TxPowerHighWarningThresh Indicates the high warning threshold in mW for the Tx power.
old
TxPowerLowWarningThresho Indicates the high warning threshold in mW for the Tx power.
ld
TxPowerStatus Indicates if any Tx power thresholds were exceeded.
RxPower Indicates the current Rx power in mW.
RxPowerHighAlarmThreshold Indicates the high alarm threshold in mW for the Rx power.
RxPowerLowAlarmThreshold Indicates the low alarm threshold in mW for the Rx power.
RxPowerHighWarningThresh Indicates the high warning threshold in mW for the Rx power.
old
RxPowerLowWarningThresho Indicates the high warning threshold in mW for the Rx power.
ld
RxPowerStatus Indicates if any Rx power thresholds were exceeded.
Aux1 Indicates the current auxiliary 1 reading.
Aux1HighAlarmThreshold Indicates the high alarm threshold auxiliary 1 reading.
Aux1LowAlarmThreshold Indicates the low alarm threshold auxiliary 1 reading.
Aux1HighWarningThreshold Indicates the high warning threshold auxiliary 1 reading.
Aux1LowWarningThreshold Indicates the high warning threshold auxiliary 1 reading.
Aux1Status Indicates if any auxiliary 1 thresholds were exceeded.
Aux2 Indicates the current auxiliary 2 reading.
Aux2rHighAlarmThreshold Indicates the high alarm threshold auxiliary 2 reading.
Aux2LowAlarmThreshold Indicates the low alarm threshold auxiliary 2 reading.
Aux2HighWarningThreshold Indicates the high warning threshold auxiliary 2 reading.
Aux2LowWarningThreshold Indicates the high warning threshold auxiliary 2 reading.
Aux2rStatus Indicates if any auxiliary 2 thresholds were exceeded.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Viewing DDI information using the CLI

The following sections describe the CLI commands that you use to view DDI
module information, temperature, and voltages:
Navigation
• "Viewing DDI module information" (page 40)
• "Viewing DDI temperature information" (page 42)
• "Viewing DDI voltage information" (page 43)
Viewing DDI module information

Use the following procedure to view basic SFP and XFP manufacturing
information and characteristics.
Procedure steps
Step Action
1 To view basic SFP and XFP manufacturing information and

characteristics, enter the following command:
show sys pluggable-optical-module info [<ports>]
[detail]
This command displays information for both DDI and non-DDI SFPs
and XFPs.
—End—
Variable Value
[detail] Specify to display all details.
<ports> A port or a range of ports in the format
of slot/port. If you do not specify any
port, the complete detailed output is
displayed for each port.
The command show sys pluggable-optical-module info displays

the following sample information:
System:5# show sys pluggable-optical-module info

========================================================================
Pluggable Optical Module Information
========================================================================
PORT DDM

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
NUM Type ENABLED VENDOR NAME PART NUMBER

-----------------------------------------------------------------------
xx/xx xxxxxxxx xxxxxxx xxxxxxxxxxxxxx xxxxxxxxxxxxx
10/1 GbicBx True IBM IBM42S12SNY
11/2 10GbOther False JDS UNIPHASE JGBR12SY02315
"show sys pluggable-optical-module info output description" (page 41)

describes the output of the show sys pluggable-optical-module
info command.
show sys pluggable-optical-module info output description

Parameter Description
PORT NUM Indicates the port number on the module.
Type Indicates the type of device.
DDM ENABLED Indicates if DDM is enabled.
VENDOR NAME Indicates the manufacturer’s name.
PART NUMBER Indicates the manufacturer’s part number.
The command show sys pluggable-optical-module info 4/1

detail displays the following sample information:
System:5/show/sys/pluggable-optical-modules# info 4/1 detail

===================================================================
Port: 4/1
Type: GbicBx
DDM Enabled : True
Nortel PEC : AA1419048 CLEI : IPUIAHCWAA
Vendor : Agilent Vendor PN : HFBR-5710LPQ
Vendor REV : 123jump Vendor SN : 134213423
Vendor Date : 05/01/2005 Vendor Lot : xx
Wavelength : 850 nm
Digital Diagnostic Interface Supported
DDM Status : Ok
Calibration : External
RX Power Measurement : Average
Auxiliary 1 Monitoring : +5V Supply Voltage (V)
Auxiliary 2 Monitoring : +1.8V Supply Current (V)
------------------------------------------------------------------------
LOW_ALARM LOW_WARN ACTUAL HIGH_WARN HIGH_ALARM THRESHOLD
THRESHOLD THRESHOLD VALUE THRESHOLD THRESHOLD STATUS
------------------------------------------------------------------------

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Temp(C) xxxxxxxx xxxxxxxx xxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

Voltage(V) xxxxxxxx xxxxxxxx xxxxxx xxxxxxxx xxxxxxxx Low Warn
Bias(mA) xxxxxxxx xxxxxxxx xxxxxx xxxxxxxx xxxxxxxx High Warn
TxPower(dBm) xxxxxxx xxxxxxxx xxxxxx xxxxxxxx xxxxxxxx Low Alarm
RxPower(dBm) xxxxxxx xxxxxxxx xxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Aux 1 xxxxxxx xxxxxxx xxxxxx xxxxxxxx xxxxxxxx Normal
Aux 2 xxxxxxx xxxxxxx xxxxxx xxxxxxxx xxxxxxxx Normal
========================================================================
Viewing DDI temperature information

Use the following procedure to view SFP and XFP temperatures.
Procedure steps
Step Action
1 To view SFP and XFP temperatures, enter the following command:

show sys pluggable-optical-module temperature [<ports>]
and XFPs.
—End—
Variable Value
<ports> Specify a port or a range of ports
in the format of slot/port. If you do
not specify any ports, the complete
detailed output is displayed for each
port.
The command show sys pluggable-optical-module

temperature displays the following sample information:
System:5# show sys pluggable-optical-module temperature

========================================================================
Pluggable Optical Module Temperature(C)
========================================================================
PORT LOW_ALARM LOW_WARN ACTUAL HIGH_WARN HIGH_ALARM THRESHOLD
NUM THRESHOLD THRESHOLD VALUE THRESHOLD THRESHOLD STATUS
------------------------------------------------------------------------
10/30 xxxxxxxxx xxxxxxxxx xxxxxxxx xxxxxxxxx xxxxxxxxx Normal
10/15 -40.1234 -25.2343 -15.2342 100.0234 125.0000 High Alarm

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The following table describes the output of the show sys

pluggable-optical-module temperature command.
show sys pluggable-optical-module temperature output description

LOW_ALARM Indicates the low temperature alarm threshold.
THRESHOLD
LOW_WARN Indicates the low temperature warning threshold.
THRESHOLD
ACTUAL VALUE Indicates the actual temperature.
HIGH_WARN Indicates the high temperature warning threshold.
THRESHOLD
HIGH_ALARM Indicates the high temperature alarm threshold.
THRESHOLD
THRESHOLD Indicates the threshold status (normal, low or high
STATUS warning, low or high alarm).
Viewing DDI voltage information

Use the following procedure to view SFP and XFP voltages.
Procedure steps
Step Action
1 To view SFP and XFP voltages, enter the following command:

show sys pluggable-optical-module voltage [<ports>]
and XFPs.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
<ports> Specify a port or a range of ports
in the format of slot/port. If you do
not specify any ports, the complete
detailed output is displayed for each
port.
The command show sys pluggable-optical-module voltage

displays the following sample information:
System:5# show sys pluggable-optical-module voltage

========================================================================
Pluggable Optical Module Voltage(V)
=======================================================================
PORT LOW_ALARM LOW_WARN ACTUAL HIGH_WARN HIGH_ALARM THRESHOLD
NUM THRESHOLD THRESHOLD VALUE THRESHOLD THRESHOLD STATUS
------------------------------------------------------------------------
10/30 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx Normal
10/15 1.5342 1.0133 3.2500 3.3500 3.6000 High Alarm
The following table describes the output of the show sys

pluggable-optical-module voltage command.
show sys pluggable-optical-module voltage output description

LOW_ALARM Indicates the low voltage alarm threshold.
THRESHOLD
LOW_WARN Indicates the low voltage warning threshold.
THRESHOLD
ACTUAL VALUE Indicates the actual voltage.
HIGH_WARN Indicates the high voltage warning threshold
THRESHOLD
HIGH_ALARM Indicates the high voltage alarm threshold.
THRESHOLD
THRESHOLD STATUS Indicates the threshold status (normal, low or high
warning, low or high alarm).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Troubleshooting a nonworking link

You can use the laser transmit (Tx) and receive (Rx) optical power values to
help you debug a nonworking link.
Use the following procedure if a link is not working at all.
Procedure steps
Step Action
1 Check the Tx power at both ends of the link. Outputs should be

comparable for similar devices. Large differences could mean you
have mismatched optics (SX versus LX).
2 Check the Rx power at both ends of the link and compare to Tx

power.
Rx power should be similar at both ends. If not, then low values can
indicate a broken connection or dirty interface on the transmitter.
Values too high can indicate a mismatch in SFPs resulting in one Tx
port saturating its receiver.
If the Rx power is zero and the link worked at one time, it is likely
that the transmitter at the far end has shut off.
—End—
Use the following procedure if a link is intermittent.
Procedure steps
Step Action
1 Check that one SFP is not over-driving its receiver. Receive

energy at both receivers should be approximately the same and
both transmitter outputs should be approximately the same. This
indicates similar device types. Additionally, when using long haul
devices, the Rx energy must be significantly less than the Tx energy,
otherwise the transmitter is over-driving the receiver. To correct the
problem, install an attenuator in the path.
2 If Rx energy is unusually low, check that the right type of fiber is
being used for the device (multimode versus single mode fiber) and
that the transmitters are clean.
3 As a debug step, loop back Tx to Rx locally (use an attenuator with

XD, ZX, or EX SFPs) and read the SFP parameters.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The Tx and Rx power should be similar and close to the range of

the transmitter. Values too low indicate a bad optics interface, bad
fiber, or a bad transmitter.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
47
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 Metro Ethernet Routing Switch 8600 (MERS 8600).
Navigation
• "Using Transparent Domain Continuity" (page 47)
• "Using Connectivity Fault Management" (page 75)
• "Using Y.1731 Performance Monitoring" (page 113)
• "Using port mirroring" (page 134)
• "Using remote port mirroring" (page 152)
• "Troubleshooting IS-IS" (page 159)
Using Transparent Domain Continuity

This section describes how to test Transparent LAN Services (TLS) with
Transparent Domain Continuity (TDC), including multicast and unicast
packets and round trip time. You can run the tests using any port that is
configured for Optical Ethernet Layer 2.
TDC provides end-to-end data packet path validation for each transparent
domain (TD) in the SP networks. Using TDC, you can test the data flow
from the Metro Ethernet Routing Switch 8600 through the SP network to
another Metro Ethernet Routing Switch 8600, or to a UNI on ESU, or to
a UNI on an OM1000 ESM module, or to OME6500, or to a UNI or NNI
interface on the Optical Metro 3500 multiservices platform with the Optical
Packet Edge System.
TDC end-to-end connectivity testing includes:
• Path learning validation (multicast test)
• Path validation (unicast test)
• Data path round-trip delay

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
48 Software troubleshooting
When you run a TDC test, consider the number of history entries and how
often you run the test or you will run out of memory. Nortel recommends
that you multiply the number of test case entries (history) times how often
you want to run the test (period). The total should not exceed 250 000.
For example, if you have 500 entries. You can run the test 500 times for a
total of 250 000.
The Metro Ethernet Routing Switch 8600 TDC test configuration parameters
include:
• Test name
• Test duration (one-time or periodic)
• SNMP-based configuration and traps
• Round-trip time
• Storage of test configurations in nonvolatile memory
• Test history
You can use Device Manager or the Command Line Interpreter (CLI) to
configure and run a TDC test.
Navigation
• "Using Transparent Domain Continuity with Device Manager" (page 48)
• "Using Transparent Domain Continuity with the CLI" (page 57)
Using Transparent Domain Continuity with Device Manager

Transparent Domain Continuity (TDC) using Device Manager.
Navigation
• "Configuring a new TDC test" (page 48)
• "Running a currently configured TDC test" (page 52)
• "Displaying test history" (page 52)
Configuring a new TDC test

Configure your system for TDC testing over an OEL2 port. Use the following
procedure to configure a new TDC test.
When you configure a new TDC test, the current configuration is overwritten;
all other existing configurations remain unchanged. In addition, all existing
result history for the specified test is cleared when an existing test
configuration is overwritten. You cannot configure a new test if the test
is currently running.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 From the Device Manager menu bar, choose VPN > TD Continuity.
The TDC dialog box appears with the TD Continuity tab displayed.
2 In the TDC dialog box, TD Continuity tab, click Insert.
The TDC, Insert TD Continuity dialog box appears. See "TDC, Insert
TD Continuity dialog box" (page 49).
3 Click any field to edit the data and then click Insert.
TDC, Insert TD Continuity dialog box
For information about the TD Continuity dialog box fields, see

"Variable definitions" (page 50).
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
TestId Sets the number of the TDC test you want to create.
• Enter an integer value in the range 1 and 9999.
Name Sets a unique name for the TDC test.
• Enter an alphanumeric string (in the range 1 and 63
alphanumeric characters).
TDI Specifies the unique number that identifies a specific TD.
• Enter an integer value in the range 1 and 16 777 215.
SrcUni Sets the source UNI ID (in IP address notation) for the TDC
test.
DstUni Sets the destination UNI ID for the TDC test.
DstPortNum Sets the destination port for the TDC test. Use this
destination port parameter only if the destination terminates
on an OM3500 or OME6500 NNI. This destination port
parameter is not valid for remote ESM or R module UNI
ports.
• Enter integer values in the form of slot/port. The valid
port range is 1-1 to 14-8. If a user enters an invalid
range, the system brings it back to the closest valid port
number.
MulticastCnt Specifies the number of multicast packets to send for this
test.
• Enter an integer value in the range 0 and 100 packets.
UnicastCnt Specifies the number of unicast packets to send for this test.
• Enter an integer value in the range 0 and 100 packets.
Set the value to 0 if the test is going to optical equipment.
HistoryCnt Sets the number of history entries you want to allocate for
this test.
• Enter an integer value in the range 1 and 9 999 entries.
The total number of all history entries across all tests on

a single switch is 900.
When you run a TDC test, consider the number of history
entries and how often you run the test or you will run out of
memory. Nortel recommends that you multiply the number
of test case entries (history) times how often you want to run

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
the test (period). The total should not exceed 250 000. For
example, if you have 500 entries. You can run the test 500
times for a total of 250 000.
PeriodicRate Specifies the time-interval, in minutes, when you want the
periodic TDC test to run.
• Enter an integer value in the range 1 and 1 440 minutes.
1 440 minutes equals 24 hours (one day).

PeriodicCount Specifies the number of times you want the periodic TDC
test to run.
If you enter 0, the periodic TDC test runs constantly.
PktPriority Specifies a priority value to use, instead of the priority of
the source port.
• Enter an integer value in the range 0 and 7.
The default value is the priority of the source port.

PktTimeout Sets the timeout period (in seconds) for the TDC test. The
default value is 10 seconds.
• Enter an integer value in the range 1 and 120 seconds.
You must specify an integer value; otherwise the default

value (10 seconds) is used.
TimeTrace Sets the round trip time option:
• none
• time
RttThreshold Specifies the round trip time threshold parameter.
• Enter an integer value in the range 0 and 10 000 ms.
Setting this value to 0 (zero) disables the rtt threshold

parameter.
Qtag Assigns the q-tag to endpoints defined as many-to-one.
Action Allows you to specify the TDC test action:
• none—disables the specified TestID from running.
• start—runs the specified TestID.
• startPeriodic—allows you to run the specified TestID in
periodic mode.
• abort—stops the TDC test you are currently running.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
• abortPeriodic—stops the TDC test you are periodically

running.
Running a currently configured TDC test

Test Transparent LAN Services (TLS) using a currently configured TDC test.
When you select and run an existing (previously configured) test, only
the current displayed configuration is overwritten; all other existing
configurations remain unchanged. In addition, all existing result history
for the specified test is cleared when an existing test configuration is
overwritten.
Procedure steps
Step Action
See "TDC dialog box, TD Continuity tab" (page 52).
TDC dialog box, TD Continuity tab
2 Select the currently configured test you want to run and then click
start in the Action field. See "TDC dialog box, TD Continuity tab"
(page 52).
Use the pull-down menu to choose other menu options.
For information about the TD Continuity History field descriptions,
see "Variable definitions" (page 50).
3 Click Apply to change the configuration.
—End—
Displaying test history

Display the TDC test history for a specific test.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
See "TDC dialog box, TD Continuity tab" (page 52).
2 In the TDC dialog, TD Continuity tab, select the test id for which
you want to display test history.
3 Click History.
The TD Continuity History dialog box appears with the History tab
displayed. See "TD Continuity History dialog box, History tab" (page
53).
TD Continuity History dialog box, History tab
For information, see "Variable definitions" (page 54).

4 Click Refresh to update the display data.
ATTENTION
The fields in this screen display register bitmask codes that indicate test
history results.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
5 Click Error Codes to view the bitmask code description online (or
refer to "Error bitmask code descriptions" (page 55)).
—End—
Variable Value
TestId Indicates the unique test id for this entry.
Name Indicates the name of the TDC test configured.
Id Indicates the number of times the test was run.
PktsSent Indicates the number of test packets transmitted.
PktsReceived Indicates the number of test packets received.
RttBroadcastMin Indicates minimum round-trip-time (RTT), in
microseconds, required by a broadcast test packet for
all executions of this test.
RttBroadcastMax Indicates maximum round-trip-time (RTT), in
RttBroadcastAvg Indicates average round-trip-time (RTT), in
RttUnicastMin Indicates minimum round-trip-time (RTT), in
microseconds, required by a unicast test packet for
RttUnicastMax Indicates maximum round-trip-time (RTT), in
RttUnicastAvg Indicates average round-trip-time (RTT), in
RttAvg Indicates average round-trip-time (RTT), in
microseconds, required by a unicast and broadcast
test packet for all executions of this test.
HopCountMin Indicates the minimum number of hops a test packet
took.
HopCountMax Indicates the maximum number of hops a test packet
took.
HopCountAvg Indicates the average number of hops a test packet
took.
TestDateandTime Indicates the date and time of the test.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
TimeStamp Indicates the timestamp.
Result Indicates the number of results saved for a given TDC
test.
ErrorMask Indicates the error mask associated with the TDC
test. Each bit in the mask represents a specific error.
The errors from the least significant bit to the highest
significant bit are summarized and represented in this
mask. See "Error bitmask code descriptions" (page 55)
for the descriptions.
In Release 4.1 and later, the TDC history results warning or error messages
now display. Bitmask error codes no longer display in DM.
Error bitmask code descriptions

Error code number Description
1 TD nonexistent on destination port
2 TD disabled on destination port
3 TD not assigned to destination port
4 TD filtered on destination NNI port
5 Destination port is NNI
6 Destination port is craft
7 Destination FDB test failed
8 Destination administrative state down
9 Destination operational state down
10 Destination port connectivity mismatch error
11 Destination port type mismatch
12 Destination port mode mismatch error
13 Destination MIB query failed
14 Destination system error
15 Invalid destination port
16 Destination port is CPU
17 Destination port mode mismatch warning
18 Destination port connectivity mismatch warning
19 Default priority used on destination
20 IP not assigned on destination oel2 port

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

21 Static entry exists on destination port
22 Destination FDB table full warning
23 to 32 Not Applicable
Not used
33 TD nonexistent on source port
34 TD not assigned to source port
35 Source FDB test failed
36 Source administrative state down
37 Source operational state down
38 Source system error
39 No response (timeout)
40 Could not get trace information
41 Could not get time information
42 Source MIB query failed
43 TD disabled on source port
44 Invalid source port
45 All ports down on the source node
46 Unknown error
47 Source FDB test failed
48 Static entry exists on source port
No FDB entry for destination MAC, unicast
49
aborted
50 RTT threshold exceeded
51 Test FAIL due to bad packet TD CONT version
52 Test FAIL due to bad packet TDI
53 Test FAIL due to bad packet Dest MAC (match)
54 Test FAIL due to bad packet Dest IP (match)
Test FAIL due to bad packet Src MAC (must
55
be unicast)
56 Test FAIL due to bad packet Src IP (match)
57 Test FAIL due to tagged/untagged mismatch
58 Test FAIL due to bad packet VID (match)
59 Test FAIL due to T/M Bit Mismatch
Test FAIL due to APPL TYPE mismatch in
60
packet

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

Test FAIL due to DST PORT mismatch in
61
packet
62 Test FAIL due to other field mismatch in packet
63 Test was aborted by user
Warning, dst TDI manytoone case, qtag
64
mismatch
Using Transparent Domain Continuity with the CLI

Transparent Domain Continuity (TDC) using the CLI.
Navigation
• "Running a currently configured TDC test" (page 57)
• "Displaying test history" (page 58)
• "Configuring a new TDC test" (page 62)
• "Example: TD continuity test" (page 73)
Running a currently configured TDC test

When you run an existing (previously configured) test, only the current
displayed configuration is overwritten; all other existing configurations
remain unchanged. In addition, all existing result history for the specified
test is cleared when an existing test configuration is overwritten.
Use the following procedure to run a currently configured TDC test using
the CLI.
Procedure steps
Step Action
1 To run a currently configured TDC test using the CLI, enter the
following command:
config tdcont test <tdc id> run [ periodic ]
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
periodic An optional parameter that allows you
to run the test in periodic mode. If
you specify periodic, then you must
have configured the TDC test with the
period parameter value.
tdc id Specifies the test id number, in the
range of 1 and 9 999.
Displaying test history

Use the following procedure to display the test results and history using
the CLI.
Procedure steps
Step Action
1 To show TDC test results, enter the following command:

show tdcont test results [ <TdcId|TdcName> ]
[history <value> ][detail]
The following graphic shows sample output for this command.
See "show tdcont test results output description" (page 59)for a

description of the output of the show tdcont test results
command.
—End—
Variable Value
detail Displays additional results in a
two-level display. This command will
indicate the reasons for failure.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
history <value> Optional parameter that allows you

to specify an integer value, between
1 and 65 535, that represents a
unique history information for the TD
Connectivity tests.
TdcId|TdcName Optional parameters that indicate the
unique TDC test ID for this entry (an
integer value between 1 and 9 999) or
a unique TDC name.
The following table describes the output of the show tdcont test
results command.
show tdcont test results output description

TEST ID Indicates the unique test id for this entry.
PKTS TX Indicates the number of test packets transmitted.
PKTS RX Indicates the number of test packets received.
BCAST-RTT Indicates the broadcast test packet round-trip-time (RTT) status.
• LST—The round-trip-time of the last broadcast test in
microseconds.
• AVG—The average round-trip-time for a broadcast test packet in
microseconds for all executions of this test.
• MAX—The maximum round-trip-time, in microseconds, required
by a broadcast test packet for all executions of this test.
• MIN—The minimum round-trip-time, in microseconds, required by
a broadcast test packet over for all executions of this test.
UAST-RTT Indicates the unicast test packet round-trip-time (RTT) status.
• LST—The round-trip-time, in microseconds, of the last unicast
test.
• AVG—The average round-trip-time, in microseconds, for a
unicast test packet for all executions of this test.
• MAX—The maximum round-trip-time, in microseconds, required
by a unicast test packet for all executions of this test.
• MIN—The minimum round-trip-time, in microseconds, required by
a unicast test packet for all executions of this test.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
ERROR MASK Indicates the error mask associated with the TDC test. Each bit in the
mask represents a specific error. The errors from the least significant
bit to the highest significant bit are summarized and represented in
this mask.
This field returns the error status in Hexadecimal format (see
"Hexadecimal Result Mask:" (page 60)).
Status Indicates the current status of the specified TDC test.
Hexadecimal Result Mask:

This section describes the Result Mask format, which is used in the TDC
results display. The Error Mask is 64-bits wide and is in Hexadecimal format.
Procedure steps
Step Action
1 To display the Result Mask, enter the following command:

show tdcont test results [ <TdcId>|<TdcName> ]
[history <value> ]
—End—
Example for Result Mask:

As shown in the "Result Mask Status description" (page 61), bit 63 is the
most significant bit. For example, if a multicast + unicast test passes +
overall tests passed (multicast passed and unicast passed), the Result
Mask is: E0000000
If a timeout occurs during the unicast portion of a multicast + unicast test,
the Result Mask is: 40080000
The "Result Mask Status description" (page 61) is divided into two sections:
• First 32-bit mask of test results
The first 32-bit mask shows the overall test results.
• Second 32-bit mask of test results

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The second 32-bit mask shows informational errors returned from the
destination device.
Result Mask Status description

Result Mask (Hexidecimal
Description
results)
First 32-bit mask of test results

0x80000000 Overall Test PASS
0x40000000 Multicast Test PASS
0x20000000 Unicast Test PASS
0x10000000 Other undefined failure occurred
0x08000000 Source Port Administration State is Down
0x04000000 Source Port Operational State (Link) is Down
0x02000000 FDB Check on Remote Destination Failed
0x01000000 Error, Can’t Send Packet, all uplink ports down
0x00800000 Dest Port Administration State is Down
0x00400000 Dest Port Operational State (Link) is Down
0x00200000 FDB Check on Remote Destination Failed
0x00080000 Test FAIL due to Packet Timeout
0x00040000 Test FAIL due to bad packet TD CONT Version
0x00020000 Test FAIL due to bad packet TDI
0x00010000 Test FAIL due to bad packet Dst MAC (match)
0x00008000 Test FAIL due to bad packet Dst IP (match)
0x00004000 Test FAIL due to bad packet Src MAC (must be unicast)
0x00002000 Test FAIL due to bad packet Src IP (match)
0x00001000 Test FAIL due to tagged/untagged mismatch
0x00000800 Test FAIL due to bad packet VID (match)
0x00000400 Test FAIL due to T/M Bit Mismatch
0x00000200 Test FAIL due to APPL TYPE mismatch in packet
0x00000100 Test FAIL due to DST PORT mismatch in packet
0x00000001 t Test FAIL due to other field mismatch in packet
0x00000080 Test was aborted by user
0x00000040 Round-trip time threshold exceeded
Second 32-bit mask of test results

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Result Mask (Hexidecimal

Description
results)
0x80000000 Error, TDI does not exist on destination port
0x40000000 Error, TDI is not mapped on destination port
0x20000000 Warning, destination port is a NNI Port
0x10000000 Warning, destination port is a craft port
0x08000000 Error, source and destination port type mismatch
0x04000000 Error, source and destination port mode mismatch
0x02000000 Error, system error on destination port
0x01000000 Error, destination MIB access failed
0x00800000 Error, TDI is not enabled on the destination port
0x00400000 Error, TDI is filtered on the destination port
0x00200000 Error, src/dst port connectivity mismatch (spoke-ptpt, spoke,
ptpt-spoke)
0x00100000 Error, destination port number is invalid
0x00080000 Warning, destination port is a CPU port
0x00040000 Warning, source and destination port mode mismatch
(oel2/l2)
0x00020000 Warning, src/dst port connectivity mismatch (hub->ptpt,
ptpt->hub)
0x00010000 Warning, default priority used on destination mapped port
0x00008000 Error, no IP on the destination oel2 port
0x00004000 Error, static entry for src/dst port’s MAC exists on the dst port
0x00002000 Error, static entry for src/dst port’s MAC exists on the src port
0x00001000 Warning, dst TDI manytoone case, qtag mismatch
Configuring a new TDC test

Use the following procedure to configure your system for TDC testing over
an OEL2 port.
Procedure steps
Step Action
1 To configure your system for TDC testing over an OEL2 port, enter
config tdcont test <tdc id> create
This command allows you to enter the number of the TDC you want
to create for continuity testing.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
<tdc id> Specifies the test id number in the
Displaying the current configuration information

Use the following procedure to display the current configuration information
for the specified configuration.
Procedure steps
Step Action
1 To display the current configuration information, enter the following

command. The <tdc id> specifies the test id number in the range
of 1 and 9 999.
config tdcont test <tdc id> info
—End—
Setting a unique name for the TDC test

Use the following procedure to set the name for the TDC test.
Procedure steps
Step Action
1 To set a unique name for a TDC test, enter the following command.
config tdcont test <tdc id> name <name>
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
<name> An alphanumeric string (between 1
and 63 alphanumeric characters) that
uniquely identifies the TDC
Setting TDI for a specific TDC test

Use the following procedure to set a unique TDI for the TDC test.
Procedure steps
Step Action
1 To set a unique number that defines the TDI for which this TDC will
run, enter the following command.
config tdcont test <tdc id> tdi <1..16777215>
—End—
Variable Value
<1..16777215> The TDI on which the TDC test runs.
An integer value between 1 and 16
777 214.
Deleting a TDC test

Use the following procedure to delete a TDC test.
Procedure steps
Step Action
1 To delete a TDC test, enter the following command. The <tdc id>
specifies the test id number in the range of 1 and 9 999.
config tdcont test <tdc id> delete
This command allows you to enter the number or name of the TD
you want to delete from the continuity testing.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Stopping the current test

Use the following procedure to stop the TDC testing you are currently
running.
Procedure steps
Step Action
1 To stop the TDC testing you are currently running, enter the following
command:
config tdcont test <tdc id> abort [periodic]
—End—
Variable Value
[periodic] An optional value that you can enter,
which aborts only the TDC testing you
are periodically running.
range of 1 and 9 999
Setting the destination port for the TDC test

Use the following procedure to set the destination port for the TDC test.
Prerequisites
• Use the destination port parameter only if the destination terminates on
an OM3500 or OME6500 product.
• The destination port parameter is not valid for remote ESM or R module
UNI ports.
Procedure steps
Step Action
1 To set the destination port for the TDC test, enter the following
command:
config tdcont test <tdc id> des-port <port>

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
<port> Indicates the slot/port number (1/1 to
1/4). The valid port range for OM is
1-1 to 14-8.
If you enter an invalid range, the
system brings it back to the closest
valid port number.
Setting the source UNI ID for the TDC test

Use the following procedure to set the source UNI ID (IP address) for the
TDC test.
Procedure steps
Step Action
1 To set the source UNI ID for the TDC test, enter the following
command:
config tdcont test <tdc id> src-uni <ipaddr>
—End—
Variable Value
<ipaddr> The IP address of the source UNI.
Setting the destination UNI ID for the TDC test

Use the following procedure to set the destination UNI ID (IP address) for
the TDC test.
Procedure steps

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Step Action
1 To set the destination UNI ID for the TDC test, enter the following
command:
config tdcont test <tdc id> des-uni <ipaddr>
—End—
Variable Value
<ipaddr> The IP address of the destination UNI.
Allocating history entries

Use the following procedure to enter the number of history entries you want
to allocate for TDC test.
The total number of all history entries across all tests on a single switch is
900.
Prerequisites
• When you run a TDC test, consider the number of history entries
and how often you run the test or you will run out of memory. Nortel
recommends that you multiply the number of test case entries (history)
times how often you want to run the test (period). The total should not
exceed 250 000. For example, if you have 500 entries. You can run the
test 500 times for a total of 250 000.
Procedure steps
Step Action
1 To set the number of history entries you want to allocate for TDC
test, enter the following command:
config tdcont test <tdc id> history <1..9999>
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
<1..9999> 1..9999 indicates that you must enter
an integer value between 1 and 9 999
entries. The default is 1.
Setting SNMP trap control

Use the following procedure to set SNMP trap control for the TDC test.
Procedure steps
Step Action
1 To set SNMP trap control for the TDC test, enter the following
command:
config tdcont test <tdc id> trap <TRUE|FALSE>
—End—
Variable Value
tdcont <tdc id> Specifies the test id number in the
trap <TRUE|FALSE> Enter TRUE to set SNMP trap control.
Enter FALSE to turn off SNMP trap
control. The default if FALSE.
Setting the number of multicast packets

Use the following procedure to set the number of multicast packets to send
for the TDC test.
Procedure steps
Step Action
1 To set the number of multicast packets to send for the TDC test,
enter the following command:
config tdcont test <tdc id> multicast <0..100>
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
<0..100> Specifies the number of multicast
packets to send for this test. 0..100
indicates that you must enter an
integer value between 0 and 100
Setting the number of unicast packets

Use the following procedure to set the number of unicast packets to send
for the TDC test.
Procedure steps
Step Action
1 To set the number of unicast packets to send for the TDC test, enter
config tdcont test <tdc id> unicast <0..100>
—End—
Variable Value
<0..100> Specifies the number of unicast
packets to send for this test. 0..100
indicates that you must enter an
integer value between 0 and 100
If the destination port is set for 1/1 to
1/4, the unicast is set to 0.
Setting the time interval for the periodic TDC test

Use the following procedure to set the time interval (in minutes) when you
want the periodic TDC test to run.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 To set the time interval (in minutes) when you want the periodic TDC
test to run, enter the following command:
config tdcont test <tdc id> period <1..1440>
—End—
Variable Value
<0..1440> 1..1440 indicates that you must enter
an integer value between 1 and 1 440
minutes (equals 24 hours or one day).
The default is 1 minute.
Setting the number of times a periodic TDC test runs

Use the following procedure to set the number of times you want the
periodic TDC test to run.
Procedure steps
Step Action
1 To set the number of times you want the periodic TDC test to run,
config tdcont test <tdc id> period-count <1..1440>
—End—
Variable Value
<0..1440> 1..1440 indicates the number of times
the TDC test will run. The default is
0 (indefinitely). If you enter 0, the
periodic TDC test runs constantly.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Setting the priority value of the TDC test

Use the following procedure to set the priority value to use (instead of the
priority of the source port) for the TDC test.
Procedure steps
Step Action
1 To set a priority value to use, instead of the priority of the source port
for the TDC test, enter the following command:
config tdcont test <tdc id> priority <0..7>
—End—
Variable Value
<0..7> An integer value between 0 and 7.
The default is the priority of the source
port.
Setting the q-tag for the TDC test

Use the following procedure to set the q-tag for many-to-one endpoints
for the TDC test.
Prerequisites
• Do not use this option for one-to-one endpoints.
Procedure steps
Step Action
1 To set the q-tag for many-to-one endpoints, enter the following

command:
config tdcont test <tdc id> qtag <0..4096>
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
<0..4096> An integer value between 0 and 4
096. The default is 0. Do not use this
option for one-to-one endpoints.
Setting the TDC test time and trace mode

Use the following procedure to set the TDC test time and trace mode.
Procedure steps
Step Action
1 To set the TDC test time and trace mode, enter the following
command:
config tdcont test <tdc id> rtt-mode <none|time>
—End—
Variable Value
<none|time> none indicates that the test does not
calculate the round trip time (RTT)
and the number of hops. The default
is none.
time is the TD test time.
Setting the round trip time threshold parameter

Use the following procedure to set the round trip time threshold parameter.
Procedure steps
Step Action
1 To set the round trip time threshold parameter, enter the following
command:
config tdcont test <tdc id> rtt-threshold
<0..10000>

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
<0..10000> 0..10000 indicates the rtt threshold
value between 0 and 10 000
milliseconds.
Setting this value to 0 (zero) disables
the rtt threshold parameter.
Setting the timeout period for the TDC test

Use the following procedure to set the timeout period for the TDC test.
Procedure steps
Step Action
1 To set the timeout period for the TDC test, enter the following
command:
config tdcont test <tdc id> timeout <1..120>
—End—
Variable Value
<1..120> Enter an integer value between 1 and
120 seconds.
The default is 10 seconds.
Example: TD continuity test

This example shows you how to configure and run a TDC test using the CLI.
Configuring a TDC test on the Metro Ethernet Routing Switch 8600

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
You must create the UNI, TDI and endpoint first and then use TDC to test
them before adding traffic. The following example tests the existing OEL2
service.
Step Action
1 Create the TDC test, using the following command:

config tdcont test 8000 create
2 Configure the source-uni using the following command:
config tdcont test 8000 src-uni 1.3.2.9
3 Configure the dest-uni using the following command:

config tdcont test 8000 des-uni 1.3.2.12
4 Configure the TDI, using the following command:

config tdcont test 8000 tdi 600
5 Run the test using the following command:
config tdcont test 8000 run
6 See the result of the test with info option, using the following
command:
config tdcont test 8000 info
Sub-Context:
Current Context:
name: TEST-8000
tdi: 600
src-uni: 1.3.2.9
des-uni: 1.3.2.12
des-port:
trap: N
multicast: 1
unicast: 1
history: 1
period: 1(min)
period-count: 0(indefinitely)
priority: 1

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
timeout: 10(sec)
rtt-mode: none
rtt-threshold: 0
qtag: 0
action: null
result: Pass
—End—
Using Connectivity Fault Management

This section describes how you configure and use Connectivity Fault
Management (CFM) to verify connectivity, detect and isolate faults, and
ensure the delivery of services in your Provider Backbone Bridge (PBB) and
Provider Backbone Transport (PBT) trunks and service instances.
Navigation
• "Configuring CFM using Device Manager" (page 75)
• "Configuring CFM using the CLI" (page 93)
Configuring CFM using Device Manager

This section describes how to configure and use Connectivity Fault
Management (CFM) for PBB and PBT trunks and service instances using
Device Manager.
Navigation
• "Creating a maintenance domain" (page 76)
• "Creating a maintenance association" (page 77)
• "Creating a maintenance endpoint" (page 78)
• "Displaying MEP statistics" (page 80)
• "Creating a remote maintenance endpoint" (page 82)
• "Displaying RMEP statistics" (page 83)
• "Creating a maintenance intermediate point" (page 85)
• "Displaying MIP statistics" (page 87)
• "Displaying CFM port statistics" (page 88)
• "Monitoring CFM loopback messages" (page 89)
• "Monitoring CFM linktrace messages" (page 91)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Creating a maintenance domain

Create a maintenance domain (MD) to define a part of the network
for connectivity fault management (CFM). With CFM, you can verify
connectivity, detect and isolate faults, and ensure the delivery of services.
One MD may contain several maintenance associations and maintenance
endpoints. (The following sections describe how to configure these
features.) You can configure an MD for different levels within the metro
network: Trunk Group and Service Instance.
Prerequisites
• You must set the bootconfig flag to discard unknown MAC
destinations with the command config bootconfig flags
unknown-destmac-discard true; and then reboot the MERS 8600.
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > CFM >
Maintenance Domain.
The Maintenance Domain dialog box opens and shows the existing
domains. See the following figure.
Maintenance Domain dialog box
2 Click Insert.
The Maintenance Domain, Insert dialog box opens (see the following
figure).
Maintenance Domain, Insert dialog box
3 Enter a Name for this MD.
4 Assign a Level to this MD.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
5 Click Insert.
—End—
Variable Value
Index Assigns a unique index number to this
maintenance domain. Device Manager assigns
this automatically, which you can overwrite.
Name Assigns a name to this maintenance domain.
Level Separates MDs from each other so you can
provide different functions to different areas in
the network. The 802.1ag draft recommends the
following assignments:
• level 5–7 to customer equipment
• level 3–4 to service provider equipment
• level 0–2 to operator equipment
EventTrapEnable Enables or disables the sending of 802.1ag and
Y.1731 event traps for this maintenance domain.
PmEnable Enables or disables performance monitoring for
this maintenance domain.
Creating a maintenance association

Create a maintenance association (MA) to link a service instance (trunk,
VLAN, or VPN) to an MD. You also use this feature to set the continuity
check message (CCM) interval.
Prerequisites
• Create a maintenance domain.
Procedure steps
Step Action
Maintenance Domain.
The Maintenance Domain dialog box opens.
2 Select an MD.
This activates its Maintenance Association button.
3 Click Maintenance Association.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The Maintenance Association dialog box opens.
4 Click Insert.
The Maintenance Association, Insert dialog box opens (see the
following figure).
Maintenance Association, Insert dialog box
5 Enter a AssociationName for this MA.

6 Customize your MA by changing the default settings. For information,
see the following table.
7 Click Insert.
—End—
Creating a maintenance endpoint

Create a maintenance endpoint (MEP) to link an endpoint to an MA. MEPs
originate CFM messages and respond to CFM messages sent by other
MEPs. You also use this feature to set the CFM message values.
Prerequisites
• Create a maintenance association.
Procedure steps

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Step Action
Maintenance Domain.
2 Select an MD to activate its Maintenance Association button.
3 Click the Maintenance Association button.
4 Select an MA to activate its Maintenance Endpoint button.

5 Click the MaintenanceEndpoint button.
The Maintenance Endpoint dialog box opens (see the following
figure).
Maintenance Endpoint dialog box
6 Click Insert.
The Maintenance Endpoint, Insert dialog box opens (see the
following figure).
Maintenance Endpoint, Insert dialog box
7 Enable the MEP.
8 Customize your MEP by changing the default settings. For

information, see the following table.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
Id Assigns a unique ID number to this
maintenance endpoint. Device Manager
assigns this automatically, which you can
overwrite.
AdminState Administratively enables or disables the
maintenance association. The default is
disable.
CcmPriority Sets the priority level for transmitting continuity
check messages. The range is from 0 to 7,
and the default is 7.
CcmTxEnable Enables or disables sending continuity check
messages from this MA. It is enabled by
default.
Displaying MEP statistics

Display MEP statistics to monitor your system.
To reset the statistics counters, use the ClearStats button. Clicking this
button causes the columns to reset to zero and automatically begin to
recalculate statistical data. The ClearStats button does not affect the
AbsoluteValue column. To reset absolute values, use the resetCounters
function (Edit > Chassis > System).
Prerequisites
• Create a maintenance endpoint.
Procedure steps
Step Action
Maintenance Domain.


Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
5 Click the Maintenance Endpoint button.
6 Select a MEP.
7 Click the Statistics tab.

The Maintenance Endpoint statistics dialog box opens (see the
following figure).
Maintenance Endpoint statistics
For a description of the column names, see "Procedure job aid:

Maintenance Endpoint statistics description" (page 81).
—End—
Procedure job aid: Maintenance Endpoint statistics description
Heading Description
TxCnt Shows the total number of CFM messages
transmitted from the trunk or ESM port.
RxCnt Shows the total number of CFM messages
received by the trunk or ESM port.
Defect The highest priority defect present since the
last MEP fault reset:
• none—no faults
• DefRDICCM—RDI bit set in received CCM
packet
• DefMACstatus—the MAC associated with
the transmitting MEP is reporting an error
status
• DefRemoteCCM—not receiving CCMs
from a MEP in the configured list
• DefErrorCCM—received an invalid CCM
• DefXconCCM—received a CCM that could
be from some other MA

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Creating a remote maintenance endpoint

Create a remote maintenance endpoint to link the MAC address of the
remote endpoint to an MA.
Prerequisites
Procedure steps
Step Action
Maintenance Domain.

4 Select an MA to activate its Remote Maintenance Endpoint button.

5 Click RemoteMaintenanceEndpoint.
The Remote Maintenance Endpoint dialog box opens (see the
following figure).
Remote Maintenance EndPoint dialog box
ATTENTION
If you see all zeros for the MAC addresses, disable the AutoDetect
feature. For more information, see "Creating a maintenance association"
(page 77).
6 Click Insert.
The Remote Maintenance Endpoint, Insert dialog box opens (see
the following figure).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Remote Maintenance EndPoint, Insert dialog box
Enter the MAC address of the remote MEP (RMEP). When

configuring an RMEP, specify the primary port for the RING MAC
address for the RMEP.
• If the remote MEP is an MLT, use the MAC assigned to that MLT.
• If the remote MEP is a PBT, use the PBT MAC address specified
for the chassis.
7 Click Insert.
For more information, see the following table.
—End—
Displaying RMEP statistics

Display RMEP statistics to monitor your system.
Prerequisites
• Create an remote maintenance endpoint.
Procedure steps
Step Action
Maintenance Domain.

4 Select an MA to activate its RemoteMaintenanceEndPoint button.

5 Click the RemoteMaintenanceEndPoint button.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
6 Select a remote MEP.

The Remote Maintenance Endpoint statistics dialog box opens (see
Remote MEP Statistics dialog box
For a description of the column names, see "Procedure job aid:

Remote MEP Statistics description" (page 84).
—End—
Procedure job aid: Remote MEP Statistics description
Heading Description
LearnType
Shows how the remote MEP was learned.
• Config indicates the RMEP was
manually created.
• Auto indicates the RMEP was
automatically detected.
ATTENTION
You cannot automatically detect RMEPs.
You have to manually add and remove
MAC addresses for the trunk VLAN.
When you configure a trunk, PBT no

longer automatically adds or removes the
MAC address for the trunk VLAN to the
forwarding database entry. This eliminates
the possibility of the MAC address getting
inadvertently removed when the last trunk
to this VLAN is removed.
RemoteMacAddr Shows the MAC address of the remote MEP.

RxCnt Shows the total number of CFM messages
received by the remote MEP (RMEP).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Heading Description
SeqErrCnt Shows the total number of CFM messages
received by the RMEP that are out of
sequence.
OperState Shows the current state of the remote RMEP.
Creating a maintenance intermediate point

Create a maintenance intermediate point (MIP) to reduce the distance
between MEPs. Because MIPs passively receive CFM messages, process
the messages received, and respond back to the originating MEP, you can
use MIPs to isolate connection failures to smaller segments of the network.
MIPs are always associated with MEPs. Configuring a MEP with a MIP is
optional. A MEP does not need to exist on the port where a MIP will be
configured. You must have a MEP to initiate a message. However, even if a
MEP does not exist on a node, the MIP can be created to respond to a MEP
in an other node which sends its traffic across this newly defined MIP.
Prerequisites
Procedure steps
Step Action
Maintenance Domain.
2 Select an MD to activate its Maintenance Intermediate Point button.
3 Click the Maintenance Intermediate Point button.

The Maintenance Intermediate Point dialog box opens (see the
following figure).
4 Click Insert.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The Maintenance Intermediate Point, Insert dialog box opens (see

5 Assign a unique index number to this maintenance intermediate

point.
6 Click Insert.
7 To complete the MIP configuration, associate the MIP with a VLAN.
8 Select the CFM MIP tab.
9 Click Insert.
The VLAN, Insert CFM MIP dialog box appears.
10 Enter the VlanId and Port or MLT.

MLT cannot be used when the MIP is associated with PBT.
11 Click Insert.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Displaying MIP statistics

Display MIP statistics to monitor your system, which includes loopback and
linktrace messages.
Prerequisites
• Create a maintenance intermediate point.
Procedure steps
Step Action
Maintenance Domain.
2 Select an MD to activate its Maintenance Intermediate Point button.
3 Click the Maintenance Intermediate Point button.

4 Select a MIP.

The Maintenance Intermediate Point statistics dialog box opens (see
MIP Statistics dialog box
For a description of the column names, see "Procedure job aid: MIP
statistics description" (page 87).
—End—
Procedure job aid: MIP statistics description
Heading Description
LoopbackReceived Shows the total number of CFM loopback
messages received.
LoopbackReplied Shows the total number of CFM loopback reply
messages sent.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Heading Description
LinktraceReceived Shows the total number of CFM linktrace
messages received.
LinktraceReplied Shows the total number of CFM linktrace reply
messages sent.
Displaying CFM port statistics

Display the CFM transmit and receive port statistics.
Procedure steps
Step Action
1 From the Device Manager menu, choose VPN > CFM > Port Stats.
The CfmPortStats dialog box opens showing the Tx and Rx count for
all ports using CFM (see the following figure).
CfmPortStats dialog box
2 To clear the statistics, close the CfmPortStats dialog box and then
choose VPN > CFM > Port Stats and click the ClearStats button.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Monitoring CFM loopback messages

Monitor connectivity fault management (CFM) loopback messages to test
the connection between Maintenance Points (MP). You can also use this
feature to diagnose faults in the network as well as to measure performance.
The CFM solution uses both linktrace and loopback messages to isolate
the exact point of failure. When a port fails, the MAC addresses are flushed
from the forwarding database (FDB) of the VLANs associated with that port.
When this happens, the linktrace message (LTM) sent to the remote MEP
isolates the area of failure because the destination MERS 8600 does not
respond to the LTM. When you send LBMs to the ports on the unresponsive
MERS 8600, you can discover exactly which port failed.
Loopback messages are unicast messages that you can address to either a
MEP or MIP, but only a MEP can initiate a loopback message. The receiving
Maintenance Point (MP) responds with a loopback reply. This mechanism
provides fault verification for the MD.
Prerequisites
Procedure steps
Step Action
Maintenance Domain.

The Maintenance Endpoint dialog box opens.
5 Select an MEP to activate its Loopback button.
6 Click the Loopback button.

The Loopback dialog box opens (see the following figure).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Loopback dialog box
—End—
Variable Value
Specifies the MAC address of the
DestMacAddress
destination MEP.
Specifies the ID of the destination
DestMepId
MEP.
Indicates whether the destination is
DestIsMepId
the MEP ID: true or false.
Messages Specifies the burst count number,
which determines how many LBM
messages to send to the remote MEP.
The default burst count is 1, and the
maximum count is 10000.
DataTlv Sets the size of the LBM. The
maximum size is 512 (in bytes). The
default size is the size of the LBM
PDU.
Vlan Priority Sets the priority level for transmitting
continuity check messages. The
range is from 0 to 7, and the default
is 7.
Status Shows the status of the loopback
command:
• ready indicates that the MEPs are
ready for you to initiate a loopback
message.
• not ready indicates that the MEPs
are not configured so you cannot
initiate a loopback messaged.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
• transmit initiates a loopback

message.
Monitoring CFM linktrace messages

Fault isolation is achieved through the use of Linktrace Messages (LTM).
LTM is intercepted by all the MPs on the way to the destination MP (LTM
can be addressed to either MEP or MIP).
Monitor CFM linktrace messages to trace the hop-by-hop path to the
destination MEP or MIP. All the MPs along the path to the destination
intercept the linktrace messages and send a reply. This enables you to
isolate failures to smaller segments of the network.
from the forwarding database (FDB) of the VLANs associated with that
port. When this happens, the linktrace message sent to the remote MEP
respond to the linktrace message. When you send LBMs to the ports on the
unresponsive MERS 8600, you can discover exactly which port failed.
Prerequisites
Procedure steps
Step Action
Maintenance Domain.

5 Select an MEP to activate its LinkTrace button.

6 Click the LinkTrace button.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The LinkTrace dialog box opens (see the following figure).

LinkTrace dialog box
—End—
Variable Value
Sets the priority level for transmitting
Vlan Priority
is 7.
Specifies the MAC address of the
DestMacAddress
destination MEP.
Specifies the ID of the destination
DestMepId
MEP.
Indicates whether the destination is
DestIsMepId
the MEP ID: true or false.
Ttl Specifies the time-to-live (TTL) value
for the linktrace message. Each MP
on the way to the destination does the
following:
• decrements the TTL field in the
linktrace frame
• sends a linktrace reply message
to the originating MEP
• forwards the original linktrace
message to the destination
The linktrace message is forwarded

until it reaches its destination or the
TTL value is decremented to 0. The
default TTL is 64.
Status Shows the status of the linktrace
command:

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
• ready indicates that the MEPs are

ready for you to initiate a linktrace
message.
• not ready indicates that the MEPs
are not configured so you cannot
initiate a linktrace messaged.
• transmit initiates a linktrace
message.
Configuring CFM using the CLI

This section describes how to configure and use Connectivity Fault
Management (CFM) for Provider Backbone Bridge (PBB) and Provider
Backbone Transport (PBT) trunks and service instances using the CLI.
Navigation
• "Configuring CFM ethernet type" (page 93)
• "Creating a maintenance domain" (page 94)
• "Creating a maintenance association" (page 95)
• "Creating a maintenance endpoint" (page 98)
• "Displaying MEP statistics" (page 102)
• "Creating a remote maintenance endpoint" (page 104)
• "Displaying RMEP statistics" (page 105)
• "Configuring loopback messages" (page 107)
• "Configuring linktrace messages" (page 110)
• "Creating a maintenance intermediate point" (page 111)
• "Displaying MIP statistics" (page 112)
Configuring CFM ethernet type

Use this procedure to run at a different connectivity fault management
(CFM) ethernet type than the default of 0x88e6. The ethernet type is used
in the continuity check message (CCM) header to identify the packet as
a CCM packet.
Procedure steps
Step Action
1 Configure the CFM ethernet type with the following command.

config cfm ethertype <value>

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
ethertype <value> Specify the ethernet type as something
other than the default (0x88e6). The
range is 0x1..0xffff.
Creating a maintenance domain

Create a maintenance domain (MD) to define a part of the network for
connectivity fault management (CFM).
One MD may contain several maintenance associations and maintenance

endpoints. You can configure an MD for different levels within the metro
network: Trunk Group and Service Instance.
Prerequisites
• You must set the bootconfig flag to discard unknown MAC
destinations with the command config bootconfig flags
unknown-destmac-discard true; and then reboot the MERS 8600.
Procedure steps
Step Action
1 Create an MD with the following command. Specify a string of 1 to

22 characters for <md-name> that uniquely names the MD.
config cfm md <md-name> create [index <value>]
You can override the CLI and specify an index number for the
maintenance domain.
2 Customize your MD by changing the default settings of preconfigured

parameters. For information, see the following variable definitions
table.
3 Verify your configuration.

show cfm md info
The following shows output for the show cfm md info command.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
event-trap <enable|disable> Enables or disables the sending of
802.1ag and Y.1731 event traps for
this MD.
maint-level <level> Specify the maintenance level for this
MD.
pm <enable|disable> Enables or disables performance
monitoring for this MD. For information
about performance monitoring,
see "Using Y.1731 Performance
Creating a maintenance association

Create a maintenance association (MA) to link a service instance (trunk,
VLAN, or VPN) to an MD. You also use this feature to set the continuity
check message (CCM) interval.
Prerequisites
Procedure steps
Step Action
1 Create an MA with the following command. Specify a string of 1 to

22 characters for <ma-name> that uniquely names the MA.
config cfm md <md-name> ma <ma-name> create [index
<value>]

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
You can override the CLI and specify an index number for the
maintenance association.
2 Customize your MA by changing the default settings of preconfigured

table.
—End—
Variable Value
auto-detect <enable|disable>
Enables or disables the MA from
automatically detecting remote
MEPs. The default is disable.
ATTENTION
You cannot automatically detect
remote MEPs. You have to
manually add and remove MAC
addresses for the trunk VLAN.
When you configure a trunk, PBT
no longer automatically adds or
removes the MAC address for
the trunk VLAN to the forwarding
database entry. This eliminates
the possibility of the MAC
address getting inadvertently
removed when the last trunk to
this VLAN is removed.
ccm-interval <integer> Sets the time interval (in milliseconds)

for how often continuity check
messages (CCM) are sent between
endpoints within a domain. The
options are: 10, 100, 1000, 10 000,
60 000, and 600 000. The default is
10 000.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
ccm-rdi <enable|disable> Enables or disables the Remote
Defect Indication (RDI) on the
underlying MEP CCMs associated
with this MA.
RDI is a CCM mechanism that
is used to detect one way failure
scenarios. RDI ensures that the
CCMs transmitted by the MEP are
being received by the remote MEPs.
When an RDI is received by the
local MEP, PBT receives a link down
message, which triggers a PBT
failover.
RDI is enabled by default.
ccm-type <multicast|unicast> Controls if the CCM is sent as

multicast or unicast on underlying
MEPs associated with this MA.
event-trap <enable|disable> Enables or disables the sending of
802.1ag and Y.1731 event traps for
this MA.
[index <value>] Specify a index number for this
maintenance association.
pm <enable|disable> Enables or disables performance
monitoring for this MA. For information
about performance monitoring,
see "Using Y.1731 Performance
remove-auto-discovered-rmep Removes the specified remote MEP.
<rmep-id>
Example of configuring a maintenance association

This example configures an MA called matr1901.
Step Action
1 Name the MA matr1901 and assign the index value of 1.

config cfm md TRUNKDOMAIN ma matr1901 create index 1
2 Change the CCM interval to 1000.

config cfm md TRUNKDOMAIN ma matr1901 ccm-interval 1000

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

show cfm ma info
The following shows the current configuration information for the
show cfm ma info command.
—End—
Creating a maintenance endpoint

Create a maintenance endpoint (MEP) to link an endpoint to an MA. MEPs
originate CFM messages and respond to CFM messages sent by other
MEPs. You also use this feature to set the CFM message values.
Prerequisites
Procedure steps

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Step Action
1 Create a MEP with the following command. Specify an integer

between 1 and 8191 for <mep-id> that uniquely identifies the MEP.
config cfm md <md-name> ma <ma-name> mep <mep-id>
create
2 Enable the MEP.

config cfm md <md-name> ma <ma-name> mep <mep-id> state
enable
3 Customize your MEP by changing the default settings of

preconfigured parameters. For information, see the following
variable definitions table.
—End—
Variable Value
ccm-priority <integer> Sets the priority level for transmitting
is 7.
ccm-tx <enable|disable> Enables or disables sending continuity
check messages from this MEP. The
default is enable.
lbm <1..8191|00.00.00.00 Configures the loopback messages
.00.00> [-c <value>] [-d sent from this MEP.
<value>][-f <value>] [-i
• -c <value> specifies the burst
<value>] [-m <value>] [-p
count number, which determines
<value>] [-t <value>]
how many LBM messages to send
to the remote MEP. The default
burst count is 1, and the maximum
count is 10000.
• -d <value> sets the size of the
LBM. The maximum size is 400
(in bytes). The default size is the
size of the LBM PDU.
• -f < value> sets the fill test pattern
in the LBM PDU to one of the
following options (0–3). The
default value is 3.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
— 0 — Null signal (all zeros)

without cyclical redundancy
checking (CRC)-32
— 1 — Null signal with CRC-32
— 2 — Pseudo-random bit
sequence (PRBS) without
CRC-32
— 3 — PRBS with CRC-32
• -i <value> is the interval between

LBM frames with a range of (0,
10…1000) msecs with a default
value of 0 msecs. The value of
0 msecs indicates to send the
frames as fast as possible.
• -m <value> sets the mode for
the transmit loopback service:
RoundTripTime or throughput
mode of operation. LBM frames
are sent out in RoundTripTime;
LBM frames are sent out one at
a time and the transmit time is
recorded locally.
— 1 — This is the throughput
mode, which transmits LBM
frames at the configured
transmit interval rate for the
burst count number (the -c
option). This is the default.
— 2 — This is the
RoundTripTime mode, which
transmits LBM frames one
at a time and records the
transmit time locally.
• -p <value> sets the priority level

for transmitting continuity check
messages. The range is from 0 to
7, and the default is 7.
• -t <value> sets the interval to wait
for an LBM timeout. The range
is 1..10, (in seconds), the default
value is 3.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
ltm <1..8191|00.00.00.00 Configures the linktrace messages
.00.00> [-t <value>] [-p sent from this MEP.
<value>]
• 1..8191 is the remote MEP ID to
which LTM is sent.
• 00.00.00.00.00.00 is the remote
MEP or MIP MAC to which the
LTM is sent.
• -t <value> specifies the time-to-live
(TTL) value for the linktrace
message. Each MP on the way
to the destination decrements
the TTL field in the linktrace
frame. The linktrace message
is forwarded until it reaches its
destination or the TTL value is
decremented to 0. The default
TTL is 64.
• -p <value> sets the priority level
for transmitting continuity check
messages. The range is from 0 to
7, and the default is 7.
remove-auto-discovered-rmep Removes the specified remote MEP.
<rmep-id>
state <enable|disable> Administratively enables or disables
the maintenance endpoint. The
default is disable.
Example of configuring a maintenance endpoint

This example configures a MEP with an ID of 10.
Step Action
1 Assign the MEP ID to 10.

config cfm md TRUNKDOMAIN ma matr1901 mep 10 create
2 Enable the MEP.

config cfm md TRUNKDOMAIN ma matr1901 mep 10 state
enable
3 Change the CCM priority to 0.

config cfm md TRUNKDOMAIN ma matr1901 ccm-priority 0

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
show cfm mep info

The following shows the current configuration information for the
show cfm mep info command.
—End—
Displaying MEP statistics

Display MEP statistics to monitor your system.
Prerequisites
Procedure steps
Step Action
1 Display MEP statistics.

show cfm mep stats [md <value>] [ma <value>][mep-id
<value>][defect][no-defect]
2 Refer to the following figure for sample output for the show cfm
mep stats command. For a description of the column names, see
the job aid following this procedure.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
3 Clear statistics shown in the Maintenance Endpoint CCM stats table

with the following command:
clear cfm mep stats [ma <value>] [ma <value>] [mep-id
<value>]
This command clears the statistical values for any or all of
the following: maintenance domain, maintenance association,
maintenance endpoint.
4 Show a summary of all the MEPs.
show cfm mep summary
The following shows sample output for this command.
—End—
Procedure job aid: show cfm mep stats output description
Heading Description
DOMAIN_NAME Shows the name of the maintenance domain
that these statistics are derived from.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Heading Description
ASSOCIATION_NAME Shows the name of the maintenance
association that these statistics are derived
from.
MEP_ID Shows the number of the maintenance
endpoint that these statistics are derived from.
TX_COUNT The total number of CCM messages
transmitted from the trunk or ESM port.
RX_COUNT The total number of CCM messages received
by the trunk or ESM port.
DEFECT The highest priority defect present since the
last MEP fault reset:
• none—no faults
• DefRDICCM—RDI bit set in received CCM
packet
• DefMACstatus—the MAC associated with
the transmitting MEP is reporting an error
status
• DefRemoteCCM—not receiving CCMs
from aMEP in the configured list
• DefErrorCCM—received an invalid CCM
• DefXconCCM—received a CCM that could
be from some other MA
Creating a remote maintenance endpoint

Create a remote maintenance endpoint (RMEP) to link the MAC address
of the remote endpoint to an MA.
Prerequisites
Procedure steps
Step Action
1 Create an RMEP with the following command:

config cfm md <md-name> ma <ma-name> rmep <rmep-id>
create

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
2 Specify the endpoint on another MERS 8600.

config cfm md <md-name> ma <ma-name> rmep <rmep-id>
remote-mac <mac-address>

show cfm rmep info
ATTENTION
If you see all zeros for the MAC addresses, disable the auto-detect feature.
For more information, see "Creating a maintenance association" (page
95). To see all MAC addresses detected, enter show cfm rmep all.
—End—
Variable Value
<md-name> Specify a string of 1 to 22 characters that
identifies the MD.
<ma-name> Specify a string of 1 to 22 characters that
identifies the MA.
<rmep-id> Specify a string of 1 to 8191 characters
that uniquely identifies the RMEP.
remote-mac <mac-address> Specifies the MAC address of the remote
endpoint on another MERS 8600.
Displaying RMEP statistics

Display RMEP statistics to monitor your system.
Prerequisites

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

Procedure steps
Step Action
1 Display RMEP statistics.

show cfm rmep stats [md <value>] [ma <value>][rmep-id
<value>][up][down]
This command shows the statistical values for any or all of the
following: maintenance domain, maintenance association, and
remote maintenance endpoint.
rmep stats command. For a description of the column names,
see the job aid following this procedure.
3 Clear statistics shown in the Remote Maintenance Endpoint Stats

table with the following command:
clear cfm rmep stats [md <value>] [ma <value>][mep-id
<value>] [rmep-id <value>]
This command clears the statistical values for any or all of the
following: maintenance domain, maintenance association, and
remote maintenance endpoint.
4 Show a summary of all the RMEPs.
show cfm rmep summary

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Procedure job aid: show cfm rmep stats output description
Heading Description
DOMAIN_NAME Shows the name of the maintenance domain
ASSOCIATION_NAME Shows the name of the maintenance
association that these statistics are derived
from.
MEP_ID Shows the number of the maintenance
endpoint (MEP) that these statistics are
derived from.
RMEP_ID Show the number of the remote maintenance
endpoint that the state and RDI comes from.
STATE Shows the current state of the RMEP.
RX_COUNT The total number of CFM messages received
by the MEP.
SEQ_ERR The total number of CFM messages missing
on the MEP.
RDI Set to true when RMEP is sending Remote
Defect Indication (RDI), otherwise false.
Configuring loopback messages

Configure connectivity fault management (CFM) loopback messages to test
the connection between Maintenance Points (MP). You can also use this
feature to diagnose faults in the network as well as to measure performance.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Loopback messages are unicast messages that you can address to either
a MEP or a MIP, but only a MEP can initiate a loopback message. The
receiving Maintenance Point (MP) responds with a loopback reply. This
mechanism provides fault verification for the MD.
Prerequisites
Procedure steps
Step Action
1 Navigate to the MEP that you want to originate the LBM.

config cfm md <md-name> ma <ma-name> mep <mep-id>
2 Use the first command to configure an LBM when the destination

is a MEP. Use the second command when the destination is a MIP.
Specify a unique ID or MAC address that identifies the remote MP.
lbm <remote-mep-id|remote-mep-mac>
lbm <remote-mip-mac>
3 Customize the LBM by changing the default settings of preconfigured

table.
—End—
Variable Value
-c <value> Sets the burst count number, which
determines how many LBM messages to
send to the remote MEP. The default burst
count is 1, and the maximum count is 200.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
-d <value> Sets the size of the LBM. The maximum
size is 400 (in bytes). The default size is
the size of the LBM PDU.
-f <value> Sets the fill test pattern in the LBM PDU to
one of the following options (0–3):
• 0 — Null signal (all zeros) without
cyclical redundancy checking -32
(CRC-32)
• 1 — Null signal with CRC-32
• 2 — Pseudo-random bit sequence
(PRBS) without CRC-32
• 3 — PRBS with CRC-32
The default value is 3.

-i <value> The interval between LBM frames with
a range of (0, 10…1000) msecs with a
default value of 0 msecs. The value of 0
msecs indicates to send the frames as fast
as possible.
-m <value> Sets the mode for the transmit loopback
service: RoundTripTime or throughput
mode of operation. LBM frames are sent
out in RoundTripTime; LBM frames are
sent out one at a time and the transmit
time will be recorded locally.
• 1 — This is the throughput mode,
which transmits LBM frames at the
configured transmit interval rate for the
burst count number (the -c option).
• 2 — This is the RoundTripTime mode,
which transmits LBM frames one at
a time and records the transmit time
locally.
The default is 1.
-p <value> Sets the priority level for transmitting
continuity check messages. The range is
from 0 to 7, and the default is 7.
-t <value> Sets the interval to wait for an LBM
timeout. The range is 1..10, (in seconds),
the default value is 3.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Configuring linktrace messages

Configure CFM linktrace messages (LTM) to isolate faults in the network.
LTMs trace the hop-by-hop path to the destination MEP or MIP. All the
MPs along the path to the destination intercept the linktrace messages
and send a reply. This enables you to isolate failures to smaller segments
of the network.
Prerequisites
Procedure steps
Step Action
1 Navigate to the MEP that you want to originate the LTM.

config md <md-name> ma <ma-name> mep <mep-id>
2 Configure an LTM. Specify a unique ID or MAC address that

identifies the remote MP.
ltm <remote-mep-id|remote-mep-mac>
3 Customize the LTM by changing the default settings of preconfigured

table.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
-p <value> Sets the priority level for transmitting
continuity check messages. The range is
from 0 to 7, and the default is 7.
-t <value> Specifies the time-to-live (TTL) value
(1..64) for the linktrace message. Each
MP on the way to the destination does the
following:
• decrements the TTL field in the
linktrace frame
• sends a linktrace reply message to the
originating MEP
• forwards the original linktrace
message to the destination
The linktrace message is forwarded until it

reaches its destination or the TTL value is
decremented to 0. The default TTL is 64.
Creating a maintenance intermediate point

Create a maintenance intermediate point (MIP) to reduce the distance
between MEPs. Because MIPs passively receive CFM messages, process
the messages received, and respond back to the originating MEP, you can
use MIPs to isolate connection failures to smaller segments of the network.
MIPs are always associated with MEPs. Configuring a MEP with a MIP
is optional.
Prerequisites
Procedure steps
Step Action
1 Create a MIP.
config cfm md <md-name> mip <mip-id> create

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Specify the names of the MD for <md-name> and the MIP ID for
<mip-id>.

show cfm mip info
The following shows output for this command.
—End—
Displaying MIP statistics

Display MIP statistics to monitor your system, which includes the loopback
and linktrace messages.
Prerequisites
• Create a maintenance intermediate point.
Procedure steps
Step Action
1 Display MIP statistics.

show cfm mip stats
mip stats command. For a description of the column names, see
the job aid following this procedure.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
3 Clear statistics shown in the Maintenance Intermediate Point Stats

table with the following command.
clear cfm mip stats [md <value>] [mip <value>]
This command clears the MIP loopback and linktrace statistical
values.
—End—
Procedure job aid: show cfm mip stats output description
Heading Description
Domain Name Shows the name of the maintenance domain
Domain Index Shows the index number of the domain.
Mip Id Shows the MIP ID number.
Loopback Received Shows the total number of CFM loopback
messages received.
Loopback Replied Shows the total number of CFM loopback reply
messages sent.
Linktrace Received Shows the total number of CFM linktrace
messages received.
Linktrace Replied Shows the total number of CFM linktrace reply
messages sent.
Using Y.1731 Performance Monitoring

Use the Y.1731 Performance Monitoring (PM) to assist you with SLA
assurance and capacity planning. You can use Y.1731 PM to measure the
following point-to-point connection metrics:
• Frame Loss Ratio (FLR) — This measurement defines a ratio that is
expressed as a percentage of the number of service frames not delivered
divided by the total number of service frames during time interval.
• Frame Delay (FD) — This measurement specifies the round-trip delay
for a frame. The elapsed time starts when the source node transmits the
first bit of the frame and ends when the same source node receives the
last bit of the loop backed frame.
• Frame Delay Variation (FDV) — This measurement records the
variations in the frame delay between a pair of service frames, where
the service frames belong to the same CoS instance on a point-to-point
Ethernet connection.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The MERS 8600 Y.1731 PM functionality supports PBT and client-level

service instances. You enable PM between MEP and remote MEP pairs by
adding PM configuration under MEPs and specifying the remote MEP id.
For example, if a given MEP has four remote MEPs, you can configure PM
between the MEP and each of the four remote MEPs.
The remote MEP can be configured or autolearned. Therefore, no check
will be done at configuration time to validate the remote MEP. Instead, the
protocol maintains an operational state and if the remote MEP is not yet
learned, the state will be set to an error condition. The protocol will use the
learning of an remote MEP as a trigger to start PM on the pair, if PM is
configured.
You can create profiles for frame loss and frame delay, including frame
delay variation. You can add and remove a profile to or from multiple PM
pairs. Each PM pair can have up to eight profiles of each type, frame loss
and frame delay, to allow for monitoring at each of the CoS levels. You
cannot have two profiles of the same type assigned to a PM pair with the
same CoS level.
Each profile contains the following parameters:
• Performance targets
• Set and clear alarm thresholds
• Threshold state
• CoS level
Navigation
• "Configuring PM using Device Manager" (page 114)
• "Configuring PM using the CLI" (page 123)
Configuring PM using Device Manager

This section describes how you configure and use performance monitoring
for the Metro Ethernet Routing Switch 8600 using Device Manager.
Navigation
• "Creating a performance monitoring pair" (page 115)
• "Creating a frame delay profile" (page 117)
• "Displaying frame delay statistics" (page 119)
• "Removing a frame delay profile" (page 120)
• "Creating a frame loss ratio profile" (page 120)
• "Displaying frame loss ratio statistics" (page 122)
• "Removing a frame loss ratio profile" (page 123)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Creating a performance monitoring pair

You can configure any number of performance monitoring (PM) pairs.
Prerequisites
Procedure steps
Step Action
Maintenance Domain.

5 Click MaintenanceEndpoint.
6 Select a Maintenance Endpoint that you want to monitor.
The PM button is activated.
7 Click PM.
The PM dialog box opens showing the PM pairs that are currently
configured. (see the following figure).
PM dialog box
8 Click Insert.
The PM Insert dialog box opens (see the following figure).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
PM Insert dialog box
9 Specify the remote MEP identifier in RmepId that you want to

monitor with this MEP.
10 Customize your performance monitoring pair configuration by filling

in the other fields. For information, see the following table.
11 Click Insert.
—End—
Variable Value
MdIndex The MD that you selected for this PM pair.
MaIndex The MA that you selected for this PM pair.
MepId The MEP that you selected for this PM pair.
RmepId Specify the remote MEP identifier that you
want to monitor with this MEP.
HistoryInterval The history summary interval in minutes.
The default setting is 15 minutes.
SampleRate The frame loss and frame delay sample rate
in seconds. Specify a value between 1 to
3600. Default setting is 10.
A consistency check is done to ensure that
the sample rate is at least four times faster
than the PM history period.
Be aware that for each PM pair that is
defined, a CFM packet will be sent for
each profile that has been added to it. For
example, if 50 PM pairs are configured and
enabled for PBT trunks and each PM pair
has four frame loss and four frame delay

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
profiles with a sample rate of one second,

the number of CFM packets sent will be 400
hundred packets per second.
State Enable or disable the performance monitoring
state.
FdList Add a frame delay profile to this PM pair.
Click the list button to view the available
frame delay profiles.
You can modify a profile after it has been
added to a PM pair, but the changes do
not take affect until one of the following
conditions occurs:
• The PM state is disabled and then
enabled.
• The profile is removed and then added
to the PM pair.
• The system is rebooted.
FlrList Add a frame loss ratio profile to this PM pair.
Click the list button to view the available
frame loss ratio profiles.
You can modify a profile after it has been
added to a PM pair, but the changes do
not take affect until one of the following
conditions occurs:
enabled.
• The profile is removed and then added
to the PM pair.
Creating a frame delay profile

Create a frame delay profile.
Frame delay DMM packets are sent at the sample rate; a frame delay is
calculated for each frame delay response (DMR) packet that is received.
The minimum sample, maximum sample, and average for the PM period will
be maintained for both frame delay and frame delay variation.
The frame delay ratio and frame delay variation ratio are compared against
the set and clear alarm percentages to determine if a trap is sent to raise or
clear a frame delay alarm.
Procedure steps

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Step Action
1 From the Device Manager, choose VPN > CFM > FD > Profile.
The Frame Delay Profile dialog box opens.
2 Click Insert.
The Frame Delay Profile, Insert dialog box appears (see the following
figure).
Frame Delay Profile, Insert dialog box
3 Type a name for your frame delay profile in ProfileName.
4 Customize your frame delay profile by changing the settings of the

profile parameters. For information, see the following table.
5 Click Insert.
—End—
Variable Value
Index Assigns a unique ID number to this frame
delay profile. Device Manager assigns this
automatically, which you can overwrite.
ProfileName The name for the frame delay profile. Specify a
string from 1 to 22 characters.
Priority The CoS priority for messaging. Specify a value
from 0 to 7. The default is 7.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
PerformanceTarget The frame delay performance objective in

milliseconds. Specify a value from 1 to 10 000.
AlarmThresholdPercent The frame delay set alarm threshold (percent).
Specify a value from 0 to 99 in 1 percent
increments.
AlarmThresholdSubPercent The frame delay set alarm threshold
(sub-percent). Specify a value from 0 to 99 in
1/100 percent increments.
ClearThresholdPercent The frame delay clear alarm threshold (percent).
Specify a value from 0 to 99 in 1 percent
increments.
ClearThresholdSubPercent The frame delay clear alarm threshold
(sub-percent). Specify a value from 0 to 99 in
FdvPerformanceTarget The frame delay variation performance objective
in milliseconds. Specify a value from 1 to
10 000.
FdvAlarmThresholdPercent The frame delay variation set alarm threshold
(percent). Specify a value from 0 to 99 in 1
percent increments.
FdvAlarmThresholdSubPer The frame delay variation set alarm threshold
cent (sub-percent). Specify a value from 0 to 99 in
FdvClearThresholdPercent The frame delay variation clear alarm threshold
percent increments.
FdvClearThresholdSubPerc The frame delay variation clear alarm threshold
ent (sub-percent). Specify a value from 0 to 99 in
ThresholdState Enable or disable the threshold state.
Displaying frame delay statistics

Display frame delay statistics to monitor the performance of your system.
Prerequisites
• You must have a performance monitoring pair with PM enabled and a
frame delay profile.
Procedure steps
Step Action
1 To view a brief summary of the frame delay statistics for performance

monitoring pairs, choose VPN > CFM > FD > Stats: Info from the
Device Manager menu.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The FdInfoStats dialog box opens showing a brief summary of the

frame delay statistics for each performance monitoring pair.
2 To view a detailed summary of the frame delay statistics for

performance monitoring pairs, choose VPN > CFM > FD > Stats:
Current from the Device Manager menu.
The FdCurrentStats dialog box opens showing a detailed summary
of the frame delay statistics for each performance monitoring pair.
3 To view the history of the frame delay statistics for performance

monitoring pairs, choose VPN > CFM > FD > Stats: History from
the Device Manager menu.
The FdHistoryStats dialog box opens showing the history of the
frame delay statistics for each performance monitoring pair.
—End—
Removing a frame delay profile

Remove a frame delay profile.
Prerequisites
• You must have created the frame delay profile.
Procedure steps
Step Action
1 From the Device Manager, choose VPN > CFM > FD > Profile.
2 Select the frame delay profile that you want to remove.
3 Click Delete.
The frame delay profile is removed.
4 Click Close.
—End—
Creating a frame loss ratio profile

Create a frame loss ratio profile.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The frame loss ratio is calculated for both the far end and near end. Frame
loss LMM packets are sent at the sample rate; the percentage frame loss
ratio is calculated for each frame loss response (LMR) packet that is
received and for the PM interval period.
The frame loss statistics collected for each PM period include the following
information:
• Tx frame count
• Far end Rx frame count
• Far end Tx frame count
• Rx frame count
• Frames lost
• Frame loss ratio
The frame loss percentage is compared against the set and clear alarm
percentages to determine if a trap is sent to raise or clear a frame loss alarm.
Procedure steps
Step Action
1 From the Device Manager, choose VPN > CFM > FLR > Profile.
The Frame Loss Ratio Profile dialog box opens.
2 Click Insert.
The Frame Loss Ratio Profile, Insert dialog box appears (see the
following figure).
Frame Loss Ratio Profile, Insert dialog box
3 Type a name for your frame loss ratio profile in ProfileName.
4 Customize your frame loss ratio profile by changing the settings of

the profile parameters. For information, see the following table.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
5 Click Insert.
—End—
Variable Value
Index Assigns a unique ID number to this frame
loss ratio profile. Device Manager assigns
this automatically, which you can overwrite.
ProfileName The name for the frame loss ratio profile.
Specify a string from 1 to 22 characters.
Priority The CoS priority for messaging. Specify a
value from 0 to 7.
AlarmThresholdPercent The frame loss ratio set alarm threshold
percent increments.
AlarmThresholdSubPercent The frame loss ratio set alarm threshold
(sub-percent). Specify a value from 0 to 99
in 1/100 percent increments.
ClearThresholdPercent The frame loss ratio clear alarm threshold
percent increments.
ClearThresholdSubPercent The frame loss ratio clear alarm threshold
(sub-percent). Specify a value from 0 to 99
in 1/100 percent increments.
ThresholdState Enable or disable the threshold state.
Displaying frame loss ratio statistics

Display frame loss ratio statistics to monitor the performance of your system.
Prerequisites
• You must have a performance monitoring pair with PM enabled and
a frame loss ratio profile.
Procedure steps
Step Action
1 To view a brief summary of the frame loss ratio statistics for

performance monitoring pairs, choose VPN > CFM > FLR > Stats:
Info from the Device Manager menu.
The FlrInfoStats dialog box opens showing a brief summary of the
frame loss ratio statistics for each performance monitoring pair.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
2 To view a detailed summary of the frame loss ratio statistics for

performance monitoring pairs, choose VPN > CFM > FLR > Stats:
Current from the Device Manager menu.
The FlrCurrentStats dialog box opens showing a detailed summary
of the frame loss ratio statistics for each performance monitoring pair.
3 To view the history of the frame loss ratio statistics for performance
monitoring pairs, choose VPN > CFM > FLR > Stats: History from
the Device Manager menu.
The FlrHistoryStats dialog box opens showing the history of the
frame loss ratio statistics for each performance monitoring pair.
—End—
Removing a frame loss ratio profile

Remove a frame loss ratio profile.
Prerequisites
• You must have created the frame loss ratio profile.
Procedure steps
Step Action
1 From the Device Manager, choose VPN > CFM > FLR > Profile.
2 Select the frame loss ratio profile that you want to remove.
3 Click Delete.
The frame loss ratio profile is removed.
4 Click Close.
—End—
Configuring PM using the CLI

This section describes how you configure and use performance monitoring
for the Metro Ethernet Routing Switch 8600 using the CLI.
Navigation
• "Creating a performance monitoring pair" (page 124)
• "Removing a performance monitoring pair" (page 126)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
• "Creating a frame delay profile" (page 126)

• "Displaying frame delay statistics" (page 128)
• "Removing a frame delay profile" (page 130)
• "Creating a frame loss ratio profile" (page 130)
• "Displaying frame loss ratio statistics" (page 131)
• "Removing a frame loss profile" (page 134)
Creating a performance monitoring pair

You can configure any number of performance monitoring (PM) pairs.
Prerequisites
Procedure steps
Step Action
1 Create a MEP and a remote MEP pair for performance monitoring

with the following command:
config cfm md <md-name> ma <ma-name> mep <mep-id> pm
<rmep-id> create
Specify the MD name for <md-name>; the MA name for <ma-name>;
the MEP identifier for <mep-id>; and the remote MEP identifier for
<rmep-id>.
2 Customize your PM configuration by changing the default settings
of preconfigured parameters. For information, see the following
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
add-fd-profile <fd-profile- Add a frame delay profile.
name> You can modify a profile after it has
been added to a PM pair, but the
changes do not take affect until one of
the following conditions occurs:
enabled.
• The profile is removed and then
added to the PM pair.
add-flr-profile <flr-profile Add a frame loss ratio profile.
-name> You can modify a profile after it has
been added to a PM pair, but the
changes do not take affect until one of
the following conditions occurs:
enabled.
• The profile is removed and then
added to the PM pair.
history-interval <value> The performance monitoring summary
interval in minutes. Specify a value
from 5 to 1440.
state <enable|disable> Enable or disable the performance
monitoring state.
sample-rate <value> The frame loss and frame delay
sample rate in seconds. Specify a
value between 1 to 3600. Default
setting is 30.
A consistency check is done to ensure
that the sample rate is at least four
times faster than the PM history
period.
Be aware that for each PM pair that
is defined, a CFM packet will be sent
for each profile that has been added
to it. For example, if 50 PM pairs are
configured and enabled for PBT trunks
and each PM pair has four frame loss
and four frame delay profiles with

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
a sample rate of one second, the
number of CFM packets sent will be
400 hundred packets per second.
Removing a performance monitoring pair

Remove a performance monitoring (PM) pair.
Prerequisites
• You must have created a performance monitoring pair.
Procedure steps
Step Action
1 To delete the PM pair, enter the following command:

config md <md-name> ma <ma-name> mep <mep-id> pm
<rmep-id> delete
Specify the MD name for <md-name>; the MA name for <ma-name>;
the MEP identifier for <mep-id>; and the remote MEP identifier for
<rmep-id>.
—End—
Creating a frame delay profile

Create a frame delay profile.
Frame delay DMM packets are sent at the sample rate; a frame delay is
calculated for each frame delay response (DMR) packet that is received.
The minimum sample, maximum sample, and average for the PM period will
be maintained for both frame delay and frame delay variation.
The frame delay ratio and frame delay variation ratio are compared against
the set and clear alarm percentages to determine if a trap is sent to raise or
clear a frame delay alarm.
Procedure Steps

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Step Action
1 Create a frame delay profile. Specify a string of 1 to 22 characters

for <fd-name> that uniquely names the profile.
config cfm fd-profile <fd-name> create
2 Customize your frame delay profile by changing the settings of

the profile parameters. For information, see the following variable
definitions table.
3 View your frame delay profile settings.

config cfm fd-profile <fd-name> info
—End—
Variable Value
alarm-threshold-percent The frame delay set alarm threshold
<value> (percent). Specify a value from 0 to
99 in 1 percent increments.
alarm-threshold-sub-percent The frame delay set alarm threshold
<value> (sub-percent). Specify a value from 0
to 99 in 1/100 percent increments.
clear-threshold-percent The frame delay clear alarm threshold
clear-threshold-sub-percent The frame delay clear alarm threshold
fdv-alarm-threshold-percent The frame delay variation set alarm
<value> threshold (percent). Specify a value
from 0 to 99 in 1 percent increments.
fdv-alarm-threshold-sub-perc The frame delay variation set alarm
ent <value> threshold (sub-percent). Specify a
value from 0 to 99 in 1/100 percent
increments.
fdv-clear-threshold-percent The frame delay variation clear alarm
<value> threshold (percent). Specify a value
from 0 to 99 in 1 percent increments.
fdv-clear-threshold-sub-perc The frame delay variation clear alarm
ent <value> threshold (sub-percent). Specify a
value from 0 to 99 in 1/100 percent
increments.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
fdv-performance-target The frame delay variation
<value> performance objective in milliseconds.
Specify a value from 1 to 10 000.
priority <value> The CoS priority for messaging.
Specify a value from 0 to 7.
threshold-state <enable|dis Enable or disable the threshold state.
able>
Displaying frame delay statistics

Display frame delay statistics to monitor the performance of your system.
Prerequisites
• You must have a performance monitoring pair with PM enabled and a
frame delay profile.
Procedure steps
Step Action
1 To display the current frame delay statistics for a performance

monitoring pair, enter the following command:
show cfm pm fd current <mdName.maName.mepId.rmepId>
The following figure shows sample output of the show cfm pm fd
current command. For a description of the column names, see the
job aid following this procedure.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
To reset the statistics, simply disable/enable PM at any level.
2 To display the history frame delay statistics for a performance

show cfm pm fd history <mdName.maName.mepId.rmepId>
The following figure shows sample output of the show cfm pm fd
history command. For a description of the column names, see the
—End—
Procedure job aid: show frame delay statistics output description
show frame delay statistics output description

Heading Description
DOMAIN_NAME The name of the maintenance domain
ASSOCIATION_NAME The name of the maintenance
association that these statistics are
derived from.
MEP The maintenance endpoint that these
statistics are derived from.
RMEP The remote maintenance endpoint
FD PRIORITY The frame delay message priority on
CoS: 0 to 7.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
PM_OPER_STATE Show the PM operational state: up,

down, or fail.
PM_HIST_STATUS The PM history status: Complete or
Incomplete.
Removing a frame delay profile

Use the following procedure to remove a frame delay profile.
Prerequisites
• You must have created the frame delay profile.
Procedure steps
Step Action
1 To delete a frame delay profile, enter the following command.

Specify the name of the frame delay profile for <fd-name>.
config cfm fd-profile <fd-name> delete
—End—
Creating a frame loss ratio profile

Use the following procedure to create a frame loss ratio profile.
The frame loss ratio is calculated for both the far end and near end. Frame
loss LMM packets are sent at the sample rate; the percentage frame loss
ratio is calculated for each frame loss response (LMR) packet that is
received and for the PM interval period.
The frame loss statistics collected for each PM period include the following
information:
• Tx frame count
• Far end Rx frame count
• Far end Tx frame count
• Rx frame count
• Frames lost
• Frame loss ratio
The frame loss percentage is compared against the set and clear alarm
percentages to determine if a trap is sent to raise or clear a frame loss alarm.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure Steps
Step Action
1 Create a frame loss ratio profile. Specify a string of 1 to 22

characters for <fd-name> that uniquely names the profile.
config cfm flr-profile <flr-name> create
2 Customize your frame loss ratio profile by changing the settings of

the profile parameters. For information, see the following variable
definitions table.
3 View your frame loss profile settings.
config cfm flr-profile <flr-name> info
—End—
Variable Value
alarm-threshold-percent The frame loss set alarm threshold
alarm-threshold-sub-percent The frame loss set alarm threshold
clear-threshold-percent The frame loss clear alarm threshold
clear-threshold-sub-percent The frame loss clear alarm threshold
priority <value> The CoS priority for frame loss
messaging. Specify a value from 0 to
7.
threshold-state <enable|dis Enable or disable the threshold state.
able>
Displaying frame loss ratio statistics

Display frame loss ratio statistics to monitor the performance of your system.
Prerequisites

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
• You must have a performance monitoring pair with PM enabled and

a frame loss ratio profile.
Procedure steps
Step Action
1 To display the current frame loss ratio statistics for a performance

show cfm pm flr current <mdName.maName.mepId.rmepId>
The following figure shows sample output of the show cfm pm flr
current command. For a description of the column names, see the
2 To display the history frame loss ratio statistics for a performance

show cfm pm flr history <mdName.maName.mepId.rmepId>
The following figure shows sample output of the show cfm pm flr
history command. For a description of the column names, see the

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Procedure job aid: show frame loss ratio statistics output

description
show frame loss ratio statistics output description

Heading Description
DOMAIN_NAME The name of the maintenance domain
ASSOCIATION_NAME The name of the maintenance
association that these statistics are
derived from.
MEP The maintenance endpoint that these
statistics are derived from.
RMEP The remote maintenance endpoint
FD PRIORITY The frame loss ratio message priority
on CoS: 0 to 7.
PM_OPER_STATE Show the PM operational state: up,
down, or fail.
PM_HIST_STATUS The PM history status: Complete or
Incomplete.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Removing a frame loss profile

Use the following procedure to remove a frame loss profile.
Prerequisites
• You must have created the frame loss profile.
Procedure steps
Step Action
1 To delete a frame loss profile, enter the following command. Specify

the name of the frame loss profile for <flr-name>.
config cfm flr-profile <flr-name> delete
—End—
Using port mirroring

Use the port mirroring feature to monitor and analyze network traffic flowing
on a port. The MERS 8600 supports both ingress (incoming traffic) and
egress (outgoing traffic) port mirroring.
You can 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. 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

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
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.
You can use Device Manager or the Command Line Interface (CLI) to
configure port mirroring.
For examples of how to configure port mirroring on an R module, see

"Troubleshooting configuration examples" (page 253).
Navigation
• "Configuring port mirroring using Device Manager" (page 135)
• "Configuring port mirroring using the CLI" (page 143)
Configuring port mirroring using Device Manager

Use the procedures in this section to configure port mirroring using Device
Manager.
Navigation
• "Configuring ports for mirroring at the port level" (page 135)
• "Configuring ports for mirroring at the endpoint level" (page 138)
• "Displaying the MAC and IP count " (page 140)
• "Editing existing port mirroring values" (page 141)
Configuring ports for mirroring at the port level

Configure mirroring ports at the port level to troubleshoot the system using
port mirroring.
Prerequisites
• Ingress mirroring is supported on all modules; however, egress mirroring
is supported only on some E, M, and R modules. Refer to the Release
Notes for a list of supported E, M, and R modules.
• ESM ports support port mirroring at the endpoint level and legacy ports.
• R module-based local TLS and ESU ring/SA ports support port mirroring
at the endpoint level, providing ingress and egress mirroring. At ingress,
port mirroring takes place before the OEL2 and PBB packets are
encapsulated. At egress, port mirroring takes place after decapsulation.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
• A maximum of 383 port mirroring entries can be enabled except on

R modules. On R modules, you can create one enabled entry for each
lane on a module. Therefore, you can create up to 3 entries on a 3
lane module, and up to 24 entries on an 8 module chassis. For more
information about R modules, see Nortel Metro Ethernet Routing Switch
8600 Installation — Modules (NN46220-306).
• When mirroring ingress traffic, only packets with valid cyclic redundancy
checks (CRC) are mirrored.
• The mirroring configuration in the ACL (rxFilter) takes precedence
over the mode of the diag mirror-by-port. Suppose that port 4/1 is
configured with a ACL rxFilter and mirroring is enabled in ACE. Also,
if you configure a diag mirror-by-port with the mirrored-port as 4/1,
then the mode as rxFilter works fine. However, if the mode of the diag
mirror-by-port is changed to txFilter or tx, the port continues to mirror rx
traffic. Nortel does not recommend enabling both an ACL mirror and an
endpoint/port mirror at the same time.
Procedure steps
Step Action
1 From the Device Manager menu bar, choose Edit > Diagnostics
> General.
The Diagnostics dialog box appears.
2 Click the Port Mirrors tab.
The Port Mirrors tab appears.
Diagnostics dialog box, Port Mirrors tab
3 Click Insert.
The Diagnostics, Insert Port Mirrors dialog box opens.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Diagnostics, Insert Port Mirrors dialog box
4 Select a mirrored (source) port. In the MirroredPort box click the

ellipsis button.
The DiagMirrorByPortMirroredPort dialog box appears [see
"DiagMirrorByPortMirroredPort dialog box" (page 137)].
DiagMirrorByPortMirroredPort dialog box
5 Select a source port.
6 Click Ok.
7 Select a destination port. In the MirroringPort box, click the ellipsis
button.
The DiagMirrorByPortMirroringPort dialog box appears.
8 Select a destination port.
9 Click Ok.
10 From the Mode options, select the appropriate mode value to specify
the traffic direction of the mirrored packet.
11 To enable this instance of mirroring, select the Enable check box.
12 Click Insert.
For information about the port mirroring fields, see the following table.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
Id Specifies an assigned identifier for the configured port
mirroring instance.
MirroredPort Specifies a port to be mirrored (source port).
MirroringPort Specifies a destination port (the port to which the
mirrored packets are forwarded).
Mode Specifies the traffic direction of the packet being
mirrored—rx, tx, both, rxFilter, txFilter, or bothFilter.
The default configuration is rx.
Note that if you use the rxFilter option with an
R module, you must use an ACL filter option. For
more information about the ACL filter, see Nortel Metro
Ethernet Routing Switch 8600 Configuration — QoS
and Traffic Management (NN46220-508).
If you have legacy modules installed in the MERS 8600
and set the mirroring mode to rxFilter, you must use
the IP traffic filter option of port mirroring.
Enable Enables or disables this port mirroring instance. The
default value is Enable.
MirrorVlanId Specify a VLAN to mirror.
Configuring ports for mirroring at the endpoint level

Configure an ISID or TDI endpoint for mirroring to troubleshoot the system.
Prerequisites
is supported only on E, M, and R modules. Refer to the Release Notes
for a list of supported E, M, and R modules.
• A maximum of 383 port mirroring entries can be enabled except on R
modules. On R modules, you can create one enabled entry for each

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

• When EPVN broadcast optimization is enabled, service level mirroring
is not supported for broadcast packets.
Procedure steps
Step Action
1 To configure an I-SID endpoint for port mirroring, from the Device

Manager menu bar, choose VPN > I-SID.
The ISID dialog box appears.
2 To configure a TDI endpoint for port mirroring, from the Device
Manager menu bar, choose VPN > TDI.
The TDI dialog box appears.
3 Select the Advanced Endpoint tab.

The Advanced Endpoint dialog box appears.
4 Move the scroll bar to the right until you can view the
IngressMirrorState and EgressMirrorState columns.
5 To enable ingress port mirroring, double-click the entry under
IngressMirrorState for the endpoint that you want to enable ingress
port mirroring on and select enable in the drop-down list.
6 To enable egress port mirroring, double-click the entry under

EgressMirrorState for the endpoint that you want to enable egress
port mirroring on and select enable in the drop-down list.
7 Click Apply.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Displaying the MAC and IP count

View the number of MAC and IP addresses learned on an ESM port and R
module to understand how resources are being used and if number of MAC
addresses are approaching the C-MAC limit per R module.
Procedure steps
Step Action
1 From the Device Manager menu bar, choose Edit > Chassis.
The Chassis dialog box appears.
2 Select the Record Count tab.

The MAC and IP record count statistics appear.
See "Procedure job aid: MAC and IP record count information"

(page 140) for a description of the information shown.
—End—
Procedure job aid: MAC and IP record count information
Heading Description
Port Identifies the port.
Ingress The number of ingress MAC
addresses learned on an ESM port or
R module lane.
Egress The number of egress MAC addresses
learned on an ESM port or R module
lane.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Ip The number of IP addresses learned

against Customer-IP-VLANs on an
ESM port or R module lane.
RecRemaining The number of MAC table records that
are unused.
RecTotal The total number of MAC table records
that are available.
Editing existing port mirroring values

This section describes how to edit existing port mirroring values. This
section includes the following topics:
• "Sorting entries" (page 141)
• "Displaying configured port mirroring entries" (page 141)
• "Editing existing mirrored or mirroring ports" (page 141)
• "Editing the Mode field values" (page 142)
• "Editing the Enable field values" (page 142)
Sorting entries
You can click 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 mirroring entries

Display the configured port mirroring entries.
Procedure steps
Step Action
> General.
2 Click the Port Mirrors tab.

For information about the port mirrors fields, see "Variable
definitions" (page 138).
—End—
Editing existing mirrored or mirroring ports

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Edit an existing mirrored or mirroring port.
Procedure steps
Step Action
> General.
2 In the Port Mirrors dialog box, double-click a port entry you want to
modify in the MirroredPort or MirroringPort column heading.
3 Click the port you want as a replacement.
4 Click Ok.
5 Click Apply.
—End—
Editing the Mode field values

Modify the Mode field of an existing entry.
Procedure steps
Step Action
> General.
2 Click the entry.
The Mode list displays the following options: Rx, Tx, Both, Rx Filter,
Tx Filter, or Both Filter.
3 Click the option you want.

The Apply button becomes active.
4 Click Apply.
—End—
Editing the Enable field values

Edit the Enable field to enable or disable the port mirroring feature.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 Click the entry.

The enable list displays the following options: true or false.
2 Click the option you want.
The Apply button becomes active.
3 Click Apply.
—End—
Configuring port mirroring using the CLI

Use the procedures in this section to configure and display port mirroring.
Navigation
• "Creating a mirroring port at the port level" (page 143)
• "Creating a mirroring port at the endpoint level" (page 147)
• "Displaying mirror port information at the port level" (page 149)
• "Displaying mirror port information at the endpoint level" (page 150)
• "Displaying the MAC and IP count" (page 151)
Creating a mirroring port at the port level

Create a mirroring port at the port level to troubleshoot the system using
port mirroring.
Prerequisites

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

Procedure steps
Step Action
1 Create a mirroring port entry.

config diag mirror-by-port <id> create in-port
<value> out-port <value> [mode <value>] [enable
{true|false}] [sp-encap <value>] [granularity <value>]
[remote-mirror-vlan-id <value>]
See the table following this procedure for the variable definitions
and options for this command.
See "Procedure job aid: Configuring mirror-by-port example" (page
146) for an example of this command.
2 Display the mirroring configuration of the port.

config diag mirror-by-port <id> info
—End—
Variable Value
enable {true|false} Enables or disables a mirroring port already
created in the mirror-by-port table.
<id> The mirror-by-port entry ID (1 to 383). You
can configure 1 mirroring port and up to 10
mirrored ports.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
in-port <value> The mirrored port. The mirrored port can
be an ESM, R module, or legacy port.
mirrored-port <port> Specifies the mirrored port. An option on
config diag mirror-by-port
<id>.
mirroring-port <port> Specifies the mirroring port. An option on
config diag mirror-by-port <id>
For information about mirroring ports, see
"Procedure job aid: About mirroring ports"
(page 146).
mode {tx|rx|both| Sets the mirroring mode. The default is rx.
rxFilter|txFilter|
bothFilter}
• tx mirrors transmit packets.
• rx mirrors receive packets.
• both mirrors both transmit and receive
packets.
• txFilter mirrors and filters transmit
packets.
• rxFilter mirrors and filters receive
packets.
• bothFilter mirrors and filters both
transmit and receive packets.
Note that mode must be set to both if

granularity is set to service-level.
Note that if you have an R module installed
in the Ethernet Routing Switch 8600 and
set the mirroring mode to rxFilter, you must
use an ACL filter option to mirror the port.
For more information about the ACL filter,
see Nortel Metro Ethernet Routing Switch
8600 Configuration — QoS and Traffic
Management (NN46220-508).
Note that if you have legacy modules
installed in the MERS 8600 and set the
mirroring mode to rxFilter, you must use
the IP traffic filter option of port mirroring.
out-port <value> The mirroring port. The mirroring port is
limited to R modules and legacy cards.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
sp-encap [true|false] Set mirroring to be done with or without
service provider encapsulation.
When you configure mirroring at the port
level for an R module, set sp-encap to false
(default), since mirroring of encapsulated
packets is not supported.
granularity Set the level, physical port or service,
{physical-port-level| that mirroring is to be done. Specify
service-level} physical-port-level or service-level. Valid
for both ESM and R module ports.
If service-level is specified, mode must be
set to both.
remote-mirror-vlan-id Sets the remote mirror VLAN ID. This is the
<value> VLAN on which remote mirrored traffic will
be sent to RMT. The ID of the VLAN in the
range of 0 to 4094.
Procedure job aid: Configuring mirror-by-port example
This configuration example uses the config diag mirror-by-port

command to mirror a port. See "config diag mirror-by-port sample output"
(page 146) for a summary of the results using the info command.
MERS-8610:5# config diag mirror-by-port 3 create in-port

10/1 out-port 10/2
config diag mirror-by-port sample output
Procedure job aid: About mirroring ports
The number of mirroring ports (also called destination ports) that you can
configure depends on the type and quantity of modules you have in your
system configuration.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The module’s switch fabric determines the number of mirrored (source)

ports that can be supported by a single mirroring (destination) port, based
on the OctaPID ID assignment for that module. For example, a 48-port
10/100TX module is assigned 6 OctaPID IDs, and each OctaPID ID
supports up to eight ports (6 x 8 = 48 ports). You can assign one destination
port per OctaPID ID.
When you configure destination ports, the CLI interface automatically

assigns the actual OctaPID ID assignment according to the switch fabric in
specific MERS 8600 modules. The assignment of the OctaPID ID by the
interface follows a fixed set of configuration rules based on the module type.
Source ports that are members of the same OctaPID ID can be mirrored
only to the same destination port. If you try to assign source ports that are
members of the same OctaPID ID to different destination ports, the CLI
prompts you with an error message. For more information about how the
OctaPID ID is used for assigning destination ports, see "Tap and OctaPID
assignment reference" (page 298).
Creating a mirroring port at the endpoint level

Create a mirroring port for a Service Instance Identifier (I-SID) or
Transparent Domain Identifier (TDI) endpoint to troubleshoot the system
using port mirroring.
Prerequisites

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

• When EPVN broadcast optimization is enabled, service level mirroring
is not supported for broadcast packets.
Procedure steps
Step Action
1 To create a mirroring port entry on an I-SID, enter the following

command:
config i-sid <i-sid> end-point <endpoint port>
ingress-mirror {enable|disable} egress-mirror
{enable|disable}
See the following table for the variable definitions for this command.
2 To create a mirroring port entry on a TDI, enter the following

command:
config tdi <tdi> end-point <uni-id> ingress-mirror
{enable|disable} egress-mirror {enable|disable}
See the following table for the variable definitions for this command.
—End—
Variable Value
egress-mirror {enable|disa Enable or disable the egress mirroring
ble} port feature for this endpoint.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
<endpoint port> Identify the endpoint port that you want

to configure for port mirroring. Specify
one of the following:
• port <port>—specify the port
number in the format slot/port.
• mlt <mid>—specify the multilink
trunking number for <mid>.
• standalone <slot/port-m
od-port>—The slot/port
represents the R-module port to
which the stand-alone ESU is
connected, mod is the module ID,
and port of the stand-alone ESU
that the endpoint is attached to.
• ring <ring-mod-port>—specif
y the ESU ring number, ESU module
identifier, and port number in the
format <ring-mod-port>.
Only applicable to I-SID endpoints.

ingress-mirror {enable|di Enable or disable the ingress mirroring
sable} port feature for this endpoint.
<i-sid> Specify the identifier for the I-SID that
you are configuring.
<tdi> Specify the identifier for the TDI that you
are configuring.
<uni-id> Specify the identifier for the UNI
endpoint (in IP notation).
Only applicable to TDI endpoint.
Displaying mirror port information at the port level

Display the mirror state of a port on the switch.
Procedure steps
Step Action
1 To display the mirror state of a port, enter the command:

show diag mirror-by-port
The following shows sample output from this command.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Show diag mirror-by-port command sample output
—End—
Displaying mirror port information at the endpoint level

Display the mirror state of an endpoint on the switch.
Procedure steps
Step Action
1 To display the mirror state of an I-SID endpoint, use the following

command:
show i-sid endpoint
The following shows sample output from this command.
2 To display the mirror state of an TDI endpoint, use the following

command:
show tdi endpoint
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Displaying the MAC and IP count

View the number of MAC and IP addresses learned on an ESM port and R
module to understand how resources are being used and if number of MAC
addresses are approaching the C-MAC limit per R module.
Procedure steps
Step Action
1 To view the number of MAC and IP addresses learned, enter the

command:
show record-count port {<port>[,<port>,...]}
See the following table for the variable definitions and other options
to this command.
"Procedure job aid: show record-count example" (page 151) shows
sample output for this command.
—End—
Variable Value
all Displays the MAC and IP addresses
learned for all ESM and R modules in
the chassis.
<port> The port or list of port numbers in the
format slot/port.
Procedure job aid: show record-count example

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Using remote port mirroring

Use remote mirroring to steer mirrored traffic through a switch cloud to a
network analysis probe located on a remote switch. With this feature, a
network administrator can monitor many ports from different switches using
one network probe device.
Remote mirroring is done by encapsulating mirrored packets in a remote

mirroring encapsulation wrapper. The encapsulated frame is bridged
though the network by a separate port-based VLAN to the remote mirroring
termination (RMT) port. At the termination port, the encapsulation header is
removed before sending the packet out of the port.
The remote mirroring feature uses a specific VLAN if remote mirroring is

enabled on the port mirroring destination port. The VLAN ID is set in the
Monitor Tag field of the remote mirrored packet. With this feature, the user
can segregate the remote mirrored traffic to a single VLAN in the entire
network.
Remote mirrored traffic is always treated in the lowest priority queue.

However, Nortel recommends that you enable remote mirroring only
for troubleshooting purposes because this feature degrades switch
performance.
You can use Device Manager or the Command Line Interface (CLI) to
configure remote port mirroring.
For examples of how to configure port mirroring on an R module, see

"Troubleshooting configuration examples" (page 253).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Navigation
• "Configuring ports for remote mirroring using Device Manager" (page
153)
• "Configuring ports for remote mirroring using the CLI" (page 155)
Configuring ports for remote mirroring using Device Manager

Configure ports for remote mirroring to troubleshoot your system.
Prerequisites
• You must be a read-write-access (RWA) user to configure remote
mirroring.
• The remote mirroring source port must be a port mirroring destination
port because only mirrored packets are remote mirrored. The switch
does not check if the port is a port mirroring destination port and sends
no error messages if the port is not.
• A remote mirroring destination port must be part of at least one
port-based VLAN.
• A maximum of 16 remote mirroring termination ports can be configured
in a switch.
• Only one port of an OctaPIDA can have a remote mirroring (termination
or source) port enabled.
• On R modules, only one port per egress lane can be mirrored.
Procedure steps
Step Action
1 From the device view, select a port.
2 From the Device Manager menu bar, choose Edit > Port.
3 Click the Remote Mirroring tab.
The Remote Mirroring tab appears (Port dialog box, Remote
Mirroring tab).
Port dialog box, Remote Mirroring tab
4 Click Insert.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The Port, Insert Remote Mirroring dialog box appears (Port, Insert
Remote Mirroring dialog box).
Port, Insert Remote Mirroring dialog box
5 Select the Enable check box.
6 From the Mode options, select source or termination.

7 In SrcMac, type the source MAC address.
8 In DstMac, type the destination MAC address.

9 Beside the VlanIdList, click the ellipsis button and select a VLAN
from the list.
10 Click Insert.
For information about the fields, see "Variable definitions" (page
154).
—End—
Variable Value
Enable Enables or disables the feature on the port. When you
enable or disable remote mirroring, a trap is sent to the
trap receiver, and an SNMP log message is generated
stating that remote mirroring is enabled or disabled.
When remote mirroring termination (RMT) is enabled,
the switch does the following:
• A forwarding database FDB static entry for the
dstmac is added. This sends all the packets that
are coming with remote mirroring dstmac to the
RMT port.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
• Periodically (once every 10 seconds) transmits

broadcast Layer 2 packets to the VLANs so that all
nodes in the network can learn the dstmac
Note that when you remove an I/O card from a slot, the
RMS and the RMT on all ports in the slot are disabled.
This action generates an SNMP log message and a
trap. When you reinsert the card, the RMS and RMT
are reenabled, but you must reenable remote mirroring.
Mode Specifies whether the port is a RMT (termination mode)
or remote mirroring source (RMS) (source mode).
SrcMac Used to set the source MAC address for the remote
mirroring encapsulation. The packet is sent out of the
RMS with the source MAC address derived from this.
The source MAC address of the encapsulated frame
contains the first 45 bits of this MAC address. The
three least significant bits are derived from the port
number of the RMS port. The MAC address of the port
is used as the default value.
DstMac Used to set the destination MAC address for the remote
mirroring encapsulation. The remote mirrored packet
is sent to this MAC address. The user-configured
dstmac is used only for the RMS. For the RMT, one of
the unused MAC addresses from the switch Port MAC
address range is used. To get the same dstmac for
the RMT across reboot, this MAC address is saved
in the configuration file and the dstmac of RMT is
accepted from the user only when the configuration
file is restored.
VlanIdList Used only for RMT. The user must specify to which
VLAN the remote mirror destination MAC address
belongs. This VLAN must be a port-based VLAN.
When the RMT port is removed from the last VLAN in
the list, RMT is disabled from the port.
Configuring ports for remote mirroring using the CLI

Use the procedures in this section to configure and display remote port
mirroring.
Navigation
• "Creating a remote mirroring port" (page 156)
• "Displaying remote mirrored port information" (page 158)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Creating a remote mirroring port

Create a remote mirroring entry to troubleshoot the system using remote
mirroring. You must create and enable an entry before setting any remote
mirroring parameters on the port.
Prerequisites
• You must be a RWA user to configure remote mirroring.
• The remote mirroring source port must be a port mirroring destination
port because only mirrored packets are remote mirrored. The switch
does not check if the port is a port mirroring destination port and sends
no error messages if the port is not.
• A remote mirroring destination port must be part of at least one
port-based VLAN.
• A maximum of 16 remote mirroring termination ports can be configured
in a switch.
• Only one port of an OctaPIDA can have a remote mirroring (termination
or source) port enabled.
• On R modules, only one port per egress lane can be mirrored.
Procedure steps
Step Action
1 Create a remote mirroring port entry.

config ethernet <slot/port> remote-mirroring create
[enable {true|false}] [mode <source|termination>]
[srcmac <mac>] [dstmac <mac>] [ether-type <ether-type>]
See the following table for the variable definitions and other options
for this command.
2 Display the remote mirroring configuration of the port.

config ethernet <slot/port> remote-mirroring info
The following figure shows the sample output for this command.
config ethernet remote-mirroring info command
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
enable {true|false} Enables or disables remote mirroring on
the port. When you enable or disable
remote mirroring, a trap is sent to the trap
receiver, and an SNMP log message is
generated stating that remote mirroring is
enabled or disabled.
When Remote Mirroring Termination
(RMT) is enabled, the switch does the
following:
• A Forwarding Database (FDB) static
entry for the dstmac is added. This
sends all the packets that are coming
with remote mirroring dstmac to the
RMT port.
• Periodically (once every 10 seconds)
transmits broadcast layer 2 packets in
the added VLAN so that all nodes in
the network can learn the dstmac.
You can modify the remote mirroring

parameters only when remote mirroring
is disabled.
mode {source|termination} Specifies whether the port is an RMT
(mode is termination) or a Remote
Mirroring Source (RMS) (mode is source).
srcmac <mac> Sets the source MAC address for the
remote mirroring encapsulation in the
format 0x00:0x00:0x00:0x00:0x00:0x00.
The packet is sent out of RMS with the
source MAC derived from this. The source
MAC address of the encapsulated frame
contains the first 45 bits of this MAC
address. The three least significant bits
are derived from the port number of the
RMS port.
The MAC address of the port is used as
the default value.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
dstmac <mac> Sets the destination MAC address for
the remote mirroring encapsulation in the
format 0x00:0x00:0x00:0x00:0x00:0x00.
The remote mirrored packet is sent to this
MAC address. User configured dstmac is
used only for RMS.
For RMT, one of the unused MAC
addresses from the switch port MAC
address range is used. To get the same
dstmac for RMT across reboot, this MAC
address is saved in the configuration file
and, only when the configuration file is
restored, the dstmac of RMT is accepted
from the user.
ether-type <ether-type> The ether-type of the remote mirrored
packet. The default value is 0x8103.
add-vlan-id <vlan-id> Used only for RMT. The user must
remove-vlan-id <vlan-id> specify to which VLAN the remote mirror
destination MAC address belongs. This
must be a port-based VLAN. When the
RMT port is removed from the last VLAN
in the list, RMT is disabled from the port.
Displaying remote mirrored port information

To display the remote mirroring information of the port, use the following
command:
show port info remote-mirroring [ <port-num> ] [mode

<value> ] [dstmac <value> ] [srcmac <value> ] [vlan-id
<value> ]
"show port info remote mirroring command" (page 158) shows sample
output for the show port info remote mirroring command.
show port info remote mirroring command

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Troubleshooting IS-IS
As an administrator of a network, you must have a basic knowledge and
understanding of networking best practices. You need to create a complete
diagram of your network before you begin to troubleshoot IS-IS. This
network map will give you a better understanding of the network topology
and traffic flow, and will help you understand how routing hardware is used.
This is important because for an IS-IS network you must define each Metro
Ethernet Routing Switch 8600 router as either Level 1/2 or Level 1. You
must also define the interfaces of each of these routers as Level 1 or Level
2-only. If authentication is in use, you must understand that there are three
levels of authentication:
• Area (Level 1)
• Domain (Level 2)
• interface Hello authentication
To troubleshoot the router, ensure that:

• IP access to the router is configured.
• Console access to the router is configured.
• The latest version of the software is installed. See Metro Ethernet
Routing Switch 8600 Upgrades (NN46220-402).
CLI debug commands

The following CLI commands are used mostly in debugging an IS-IS
network issue in case an IS-IS adjacency does initialize:
• "Global level commands" (page 159)
• "Interface level commands:" (page 161)
• "Authentication CLI commands (global and interface level):" (page 161)
Global level commands

See "IS-IS global level debug commands" (page 159) and "IS-IS statistical
CLI commands" (page 160) for global level commands.
IS-IS global level debug commands

Command Description
show ip isis info or These two commands show the same
config ip isis info information. They show the general configured
status of IS-IS on the Metro Ethernet Routing
Switch 8600 router.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Command Description
show ip isis These two commands display the configured
manual-area or config manual area for the router. Be sure that
ip isis manual-area adjacent routers are configured to be in the
info same area.
show ip interface Displays all configured interfaces.
show ip isis interface Displays which interfaces are configured with
IS-IS and the state of those interfaces.
show ip isis Displays any adjacencies that have formed
adjacencies with the local router, what interface the
adjacency is coming through, and the system
ID of the adjacent router.
IS-IS statistical CLI commands

Command Description
show ip isis Displays the IS-IS routing level of each
int-ckt-level interface (Ethernet or VLAN) and displays the
<portlist> system ID of the designated router (DIS) in the
area.
show ip isis Displays the IS-IS routing level of each
int-counters interface (Ethernet or VLAN) and other
<portlist> network changes that have occurred.
show ip isis Displays packet counts of Level 1 traffic flow.
int-l1-cntl-pkts
<portlist>
show ip isis Displays packet counts of Level 2 traffic flow.
int-l2-cntl-pkts
show ip isis stats Displays useful IS-IS network statistics.
show ip interface command output
Clearing IS-IS specific statistical data

To clear all error counters and packet counters, use the following command:

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
clear ip isis stats [ error-counters ][ packet-counters ]

The counters display 0 when you use the following show commands:
• show ip isis int-counters
• show ip isis int-l1-cntl-pkts
• show ip isis stats
To clear error counters, use the following command:

clear ip isis stats [ error-counters ]
• show ip isis int-counters
• show ip isis stats
To clear packet counters, use the following command:

clear ip isis stats [ packet-counters ]
Interface level commands:

To see the configuration of the interface, use the following commands:
config ethernet <slot#/port#> ip isis info

config ip isis interface <IP Address> info
Authentication CLI commands (global and interface level):

To see configuration information for the global or interface level, use the
following commands
Command Description
show ip isis info These two commands show the same information.
or config ip isis These commands display the authentication
info settings for the global level.
config ethernet This command displays the authentication settings
<slot/port> ip for the interface level.
isis info

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Command Description
config vlan <vlan This command displays the authentication settings
id> ip isis info for the interface level.
show ip isis int-a This command displays all interface level (Ethernet
uth <portlist> or VLAN) authentication configured on the Metro
Ethernet Routing Switch 8600 for IS-IS.
ATTENTION
If overload is set to true, the Metro Ethernet Routing Switch 6000 ignores the
setting in the SPF calculation when it is received.
Other troubleshooting issues

Sometimes, adjacencies do not come up after the interface reconfiguration.
This section describes why this may occur.
When the device initially boots, all the ports are in default VLAN (1) if not
already assigned to a particular VLAN.
When a port is assigned to a specific VLAN, that port is taken out of the
default VLAN (1). If the configured port is removed from the assigned VLAN,
(for example, VLAN [3]), then the port is automatically put into VLAN (0).
The port does not go back to the default VLAN (1).
VLAN (0) is not a functioning VLAN; it is a pool holding ports that are not in
any VLAN. The ports in VLAN (0) do not forward any customer traffic.
To enable IS-IS, the administrator must specifically put a port into the
desired VLAN. If a router Ethernet port needs to be reconfigured for IS-IS,
the administrator must put the port, which is in VLAN (0), back into the
default VLAN (1) manually.
Use the CLI command show vlan info ports to see which VLAN the
port belongs to.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
163
Troubleshooting using a network

manager
Navigation
• "Troubleshooting with Device Manager" (page 163)
Troubleshooting with Device Manager

Device Manager is a graphical user interface (GUI) used to configure and
manage switches in the Optical Ethernet Switching Solutions portfolio.
This includes the Metro Ethernet Routing Switch 8600, the Metro Ethernet
Services Unit (ESU) 1800, and the Metro Ethernet Services Unit (ESU)
1850. You install Device Manager on a management station in the network.
For more information on Device Manager, see Fundamentals - Using Device

Manager (NN46225-300).
ATTENTION
For Solaris and HP-UX, certain Operating System (OS) patches are required for
Java Device Manager (JDM) and Java Runtime Environment (JRE) to function
properly. Consult Sun Microsystems or Hewlett-Packard to install the appropriate
OS patches before launching JDM.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
164 Troubleshooting using a network manager

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
165
Downloading software
To download software from the Nortel Web site, see the following site for
download content:
http://www.nortel.com/downloadingcontent
Navigation
• "Downloading MERS 8600 software" (page 165)
• "Downloading ESU 1800 software" (page 165)
• "Downloading ESU 1850 software" (page 166)
Downloading MERS 8600 software

Use the following procedure to download MERS 8600 software.
Procedure steps
Step Action
1 Follow the instructions at http://www.nortel.com/downloadingcontent

to download the following file to your local terminal:
• Product Category: Routers & Routing Switches > Ethernet
Routing Switches
• Product Name: Metro Ethernet Routing Switch 8600
• Content type: Software
• Title: Metro Ethernet Routing Switch 8600 v4.2
—End—
Downloading ESU 1800 software

Use the following procedure to download ESU 1800 software.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
166 Downloading software
Procedure steps
Step Action

• Product Category: Optical Networks > Optical Ethernet
• Product Name: Metro Ethernet Services Unit 1800
• Title: Metro Ethernet Services (ESU) Unit 1800 v3.4
—End—
Downloading ESU 1850 software

Use the following procedure to download ESU software.
Procedure steps
Step Action

• Product Category: Optical Networks > Optical Ethernet
• Product Name: Metro Ethernet Services Unit 1850
• Title: Metro Ethernet Services (ESU) Unit 1850 v3.4
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
167
Troubleshooting tools
This section describes the tools that are part of the Metro Ethernet Routing
Switch 8600 that you can use to troubleshoot operational and configuration
issues.
Navigation
• "Trapping errors" (page 167)
• "Log files" (page 168)
• "Using syslog" (page 174)
• "Monitoring ports" (page 188)
• "Running a trace test" (page 199)
• "Using ping snoop" (page 208)
• "Running a ping test" (page 211)
• "Performing a loopback test" (page 216)
• "Testing the switch fabric and address resolution table" (page 217)
• "Checking the MIB status" (page 223)
Trapping errors using Device Manager

Trap all errors that are detected and have them sent to a log that you can
view in Device Manager.
Procedure steps
Step Action
> General.
2 Click the Error tab.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
168 Troubleshooting tools
The Error tab appears (see "Diagnostics dialog box, Error tab" (page
168)).
Diagnostics dialog box, Error tab
For information about the Error tab fields, see the following table.
3 Select the AuthenticationTraps check box.
—End—
Variable Value
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
Log files using the CLI

Configure and display the log files for the switch using the CLI.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Navigation
• "Configuring log files" (page 169)
• Displaying log information
• "Displaying level information" (page 173)
Configuring log files

Configure the log files for the switch.
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 entries
are stored in memory.
Use the following procedure to configure for the logging for the switch.
Procedure steps
Step Action
1 To configure for the logging for the switch, enter the following
command:
config log
—End—
Displaying the current log settings

Use the following procedure to display the current log settings.
Procedure steps
Step Action
1 To display the current log settings, enter the following command:

config log info
—End—
Clearing the log file

Use the following procedure to clear the log file.
Procedure steps
Step Action
1 To clear the log file, enter the following command:

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
config log clear
—End—
Setting the logging level

Use the following procedure to show and set the logging level.
Procedure steps
Step Action
1 To display the current log settings, enter the following command:

config log level [<level>]
—End—
Variable Value
[<level>] The logging level is one of the following
values:
• 0 = Information; all messages are
recorded.
• 1 = Warning; only warning and more
serious messages are recorded.
• 2 = Error; only error and more serious
messages are recorded.
• 3 = Manufacturing; this parameter is not
available for customer use.
• 4 = Fatal; only fatal messages are
recorded.
Setting the log display on screen

Use the following procedure to set the log display on the screen to on or off.
Procedure steps
Step Action
1 To turn on the log display on the screen, enter the following

command:
config log screen on

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
2 To turn off the log display on the screen, enter the following
command:
config log screen off
—End—
Adding a string to a log file

Use the following procedure to write the log file with a designation string.
Procedure steps
Step Action
1 To write the log file with a designation string, enter the following
command:
config log write <str>
—End—
Variable Value
<str> The string or command that you
append to the log file.
If the string contains spaces, you must
enclose the string in quotation marks.
Logging to a PCMCIA
Use the following procedure to enable or disable logging to a PCMCIA
Procedure steps
Step Action
1 To enable logging to a PCMCIA, enter the following command:

config log logToPCMCIA
—End—
Displaying log information

Use the following procedure to display log information for the switch.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 To display log information for the switch, enter the following

command:
show log file [tail]
Issuing the show log file tail command shows only the log
messages reported after the system starts. Issuing this command
avoids system problems when displaying a large (larger than 10
MB) /pcmcia/syslog.txt file.
—End—
Variable Value
[tail] Displays the log file in reverse order,
with the most recent information first.
Configuration example: Showing log file tail

This example uses the preceding command to write a log file, where the
tail option is entered to display the most recent information first.
If the MERS 8600 has a real-time clock, the log file shows real time.
"Show log file tail command" (page 173) shows a summary of the results
of this command.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Show log file tail command
Displaying level information

The show log level command displays the level of information being
entered in the log. 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.
Use the following procedure to display the level information.
Procedure steps
Step Action
1 To display the level information, enter the following command:

show log level
"Show log level command sample output" (page 173) shows sample
output of this command.
Show log level command sample output

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Using syslog
Use the system log (syslog) messaging feature to manage event messages.
Navigation
• Using the system log with Device Manager
• Using the system log with the CLI
Using the system log with Device Manager

Use the system log feature to send messages to syslog hosts.
Navigation
• "Enabling the system log globally" (page 174)
• "Receiving system log messages" (page 175)
• "Changing the severity level mapping" (page 176)
Enabling the system log globally

Enable the system log feature to send messages to up to 10 syslog hosts.
By default, five hosts are supported.
Procedure steps
Step Action
1 From the Device Manager menu bar, choose Edit > Diagnostics >
System Log and click the System Log tab.
The System Log tab appears.
Diagnostics, System Log tab

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Using syslog 175
3 Click Apply.
For information about the System Log tab fields, see the following
—End—
Variable Value
Enable Used to enable or 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 MERS 8600 to
manage switch event messages on any UNIX-based management
platform. The MERS 8600 syslog software supports this functionality by
communicating with a counterpart software component named syslog on
your management workstation.
The UNIX daemon syslogd is a software component that receives and
locally logs, displays, prints, and forwards messages that originate from
sources internal and external to the workstation. For example, syslogd
on a UNIX workstation concurrently handles messages received from
applications running on the workstation, as well as messages received from
MERS 8600 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 MERS 8600
• examines the severity code in each message
• uses the severity code to determine appropriate system handling for
each message
• dispatches each message (based on the severity code) to any or all of
the following destinations:
— workstation display
— local log file

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
— designated printer
— one or more remote hosts
Internally, the MERS 8600 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
For information about mapping severity levels, see "Default severity levels
and system log severity levels" (page 176).
Default severity levels and system log severity levels

UNIX system System log Internal MERS 8600
error codes severity level severity level
0 Emergency Fatal
1 Alert -
2 Critical -
3 Error Error
4 Warning Warning
5 Notice -
6 Info Info
7 Debug -
Changing the severity level mapping

Change the severity level mapping of your system log messages.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Using syslog 177
Procedure steps
Step Action
System Log and click the System Log Table tab.
The System Log Table tab appears.
Diagnostics, System Log Table tab
2 Double-click the severity field and change as required.

Use the Severity list and the "Default severity levels and system log
severity levels table" (page 176).
3 Click Ok.
—End—
Inserting a system log table member

Insert a syslog host and configure its messaging features.
Procedure steps
Step Action
System Log.
2 Click the System Log Table tab.

The System Log Table tab appears.
3 In the System Log Table tab, click Insert.
The Diagnostics, Insert System Log Table dialog box appears (see
"Diagnostics, Insert System Log Table dialog box" (page 178)).
4 Configure the fields as required.
5 Click Insert.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Diagnostics, Insert System Log Table dialog box
For information about the Insert System Log Table fields, see the
following variable definitions table.
—End—
Variable Value
Id ID for the syslog host being created.
IpAddr IP address of the syslog host.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Using syslog 179
Variable Value
UdpPort The UDP port to use to send messages to the syslog
host (514 to 530).
Enable Enables or disables sending messages to the syslog
host.
HostFacility The syslog host facility used to identify messages
(LOCAL0 to LOCAL7)
Severity The MERS 8600 message severity for which syslog
messages will be sent.
MapInfoSeverity The fields that map MERS 8600 severity levels to
syslog severity.
MapWarningSeverity The fields that map MERS 8600 warning severity levels
to syslog severity.
MapErrorSeverity The fields that map MERS 8600 error severity levels to
syslog severity.
MapFatalSeverity The fields that map MERS 8600 fatal severity levels to
syslog severity.
Using the system log with the CLI

Use the syslog facility to send messages to syslog hosts.
Navigation
• "Configuring the syslog facility" (page 180)
• "Displaying the current syslog settings" (page 180)
• "Configuring a host location for the syslog host" (page 180)
• "Creating or deleting a syslog host" (page 181)
• "Enabling or disabling a syslog host" (page 181)
• "Specifying the UNIX facility for the syslog host" (page 182)
• "Specifying the message severity levels" (page 182)
• "Enabling or disabling the sending of system messages" (page 184)
• "Enabling or disabling the sending of system messages" (page 184)
• "Specifying the maximum number of syslog hosts" (page 185)
• "Configuration example 1: Configuring the syslog facility" (page 185)
• "Configuration example 2: Configuring the syslog facility" (page 186)
• "Displaying information about syslog features" (page 187)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Configuring the syslog facility

The syslog facility in UNIX operating systems logs messages and assigns
each message a severity level based on importance.
Procedure steps
Step Action
1 To configure the syslog facility, enter the following command

config sys syslog host <id>
—End—
Variable Value
<id> A value from 1 to 10.
Displaying the current syslog settings

Use the following procedure to display the current syslog settings for the
specified host.
Procedure steps
Step Action
1 To display the current syslog settings for the specified host, enter
config sys syslog host <id> info
The system log information for the specified host appears. This
command results in the same output as the show sys syslog
host <id> info command.
—End—
Variable Value
Configuring a host location for the syslog host

Use the following procedure to configure a host location for the syslog host.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Using syslog 181
Procedure steps
Step Action
1 To configure a host location for the syslog host, enter the following
command:
config sys syslog host <id> address <ipaddr>
—End—
Variable Value
address <ipaddr> ipaddr is the IP address of the UNIX
system syslog host.
Creating or deleting a syslog host

Use the following procedure to create or to delete a syslog host.
Procedure steps
Step Action
1 To create a syslog host, enter the following command:

config sys syslog host <id> create
2 To delete a syslog host, enter the following command:

config sys syslog host <id> delete
—End—
Variable Value
Enabling or disabling a syslog host

Use the following procedure to enable or to disable a syslog host.
Procedure steps

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Step Action
1 To enable a syslog host, enter the following command:

config sys syslog host <id> enable
2 To disable a syslog host, enter the following command:

config sys syslog host <id> disable
—End—
Variable Value
Specifying the UNIX facility for the syslog host

Use the following procedure to specify the UNIX facility used in messages to
the syslog host.
Procedure steps
Step Action
1 To specify the UNIX facility used in messages to the syslog host,

config sys syslog host <id> facility <facility>
—End—
Variable Value
facility <facility> facility is the UNIX system syslog
host facility (LOCAL0 to LOCAL7).
Specifying the message severity levels

Use the following procedure to specify the syslog severity level to use
for the Metro Ethernet Routing Switch messages. The following types of
messages are available:
• Information messages
• Warning messages

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Using syslog 183
• Error messages
• Fatal messages
Procedure steps
Step Action
1 To specify the severity levels for which syslog messages are sent for
the specified modules, enter the following command:
config sys syslog host <id> severity <info|warning|e
rror|fatal>
2 To specify the syslog severity level to use for information messages,

config sys syslog host <id> mapinfo <level>
3 To specify the syslog severity level to use for warning messages,

config sys syslog host <id> mapwarning <level>
4 To specify the syslog severity level to use for error messages, enter
config sys syslog host <id> maperror <level>
5 To specify the syslog severity level to use for fatal messages, enter
config sys syslog host <id> mapfatal <level>
—End—
Variable Value
maperror <level> level is emergency, alert, critical,
error, warning, notice, info, or debug.
mapfatal <level> level is emergency, alert, critical,
mapinfo <level> level is emergency, alert, critical,
mapwarning <level> level is emergency, alert, critical,

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Enabling the sending of system messages

Use the following procedure to enable the sending of syslog messages
on the switch.
Procedure steps
Step Action
1 To enable sending of syslog messages on the switch, enter the

following command:
config sys syslog host <id> state enable
—End—
Variable Value
state <enable|disable> Enables or disables sending syslog
messages on the switch.
Specifying the UDP port number

Use the following procedure to specify the User Datagram Protocol (UDP)
port number on which to send syslog message to the syslog host.
Procedure steps
Step Action
1 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>
—End—
Variable Value
udp-port <port> port is the UNIX system syslog host
port number. The range is 514 to 530.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Using syslog 185
Specifying the maximum number of syslog hosts

Use the following procedure to specify the maximum number of supported
syslog hosts.
Procedure steps
Step Action
1 To specify the maximum number of supported syslog hosts, enter

config sys syslog host <id> max-hosts <maxhost>
—End—
Variable Value
max-hosts <maxhost> maxhost is the maximum number of
enabled hosts allowed. The range is
1 to 10.
Configuration example 1: Configuring the syslog facility

This configuration example uses the preceding commands to:
• Create a host.
• Specify a facility to log on syslog host.
• Specify a syslog severity to use for Metro Ethernet Routing Switch
warning messages.
• Specify a syslog severity to use for MERS 8600 fatal messages.
• Enable the sending of syslog messages.
• Display system log information for the specified host.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Config sys syslog command sample output
Configuration example 2: Configuring the syslog facility

This configuration example uses the preceding command to:
• Configure a host location for the syslog host.
• Create a syslog host.
• Specify the UNIX facility used in messages to the syslog host.
• Enable the sending of syslog messages.
• Display system log information for the specified host.
MERS-8606:5# config sys syslog host 1
MERS-8606:5/config/sys/syslog/host/1# create address

10.143.163.200
MERS-8606:5/config/sys/syslog/host/1# facility local6
MERS-8606:5/config/sys/syslog/host/1# host enable
MERS-8606:5/config/sys/syslog/host/1# info
Sub-Context:
Current Context:
address : 10.143.163.200
create : 1
delete : N/A
facility : local6
host : enable
mapinfo : info
mapwarning : warning
maperror : error
mapfatal : emergency
severity : info|warning|error|fatal
udp-port : 514
MERS-8606:5/config/sys/syslog/host/1#

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Using syslog 187
Displaying information about syslog features

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

switch, enter the following command:
show sys syslog
2 To display general information about the system log, enter the

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

following command:
show sys syslog host <id> info
—End—
Configuration example: Displaying syslog information
This configuration example uses the preceding commands to display

general information about the system log, and to display information about
a specified host.
Show sys syslog general-info command sample output

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Monitoring ports
Monitor the links on a port and view port statistics.
Navigation
• "Monitoring how often a port goes down" (page 188)
• "Showing port statistics" (page 189)
• "Monitoring port statistics" (page 191)
• "Clearing statistics" (page 194)
Monitoring how often a port goes down

Monitor the number of times a link goes up or down rapidly (that is, flaps) on
a port. This action can be detrimental to network stability because it can
trigger spanning tree and routing table recalculation. If the number exceeds
a given boundary during a specified interval, the port is forced out of service.
Procedure steps
Step Action
> General.
2 Click the Link Flap tab.
The Link Flap tab appears.
Diagnostics, Link Flap tab
For information about the Link Flap fields, see the following variable
definitions table.
3 Select SendTrap.
4 Click Apply.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
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.
The default is 10.
Interval Specifies the interval (in minutes). The default is 60.
Showing port statistics

You can display port statistics using the CLI. This section includes the
following port statistic commands:
• "Showing port routing statistics" (page 189)
• "Showing port DHCP relay statistics" (page 190)
• "Showing port RMON statistics" (page 190)
• "Showing port STG statistics" (page 191)
Showing port routing statistics

Use the following procedure to display routing statistics about ports on the
switch.
Procedure steps
Step Action
1 To display routing statistics about ports on the switch, enter the

following command:
show port stats routing
"Show port stats routing command sample output" (page 190) shows
sample output from this command.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Show port stats routing command sample output
—End—
Showing port DHCP relay statistics

Use the following procedure to display Dynamic Host Configuration Protocol
(DHCP) relay statistics about ports on the switch.
Procedure steps
Step Action
1 To display Dynamic Host Configuration Protocol (DHCP) relay

statistics about ports on the switch, enter the following command:
show port stats dhcp-relay
—End—
Showing port RMON statistics

Use the following procedure to display Remote Monitoring (RMON) statistics
about ports on the switch.
Procedure steps
Step Action
1 To display Remote Monitoring (RMON) statistics about ports on the

show port stats rmon
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Showing port STG statistics

Use the following procedure to display Spanning Tree Group (STG) statistics
about ports on the switch.
Procedure steps
Step Action
1 To display Spanning Tree Group (STG) statistics about ports on the

show port stats stg
"Show port stats stg command sample output" (page 191) shows
sample output for this command.
Show port stats stg command sample output
—End—
Monitoring port statistics

The monitor commands are self-updating show commands. Use the
following procedure to set the monitor duration and interval,
Procedure steps
Step Action
1 To display the current level parameter settings and next level

directories, enter the following command:
config cli monitor info
2 To set the monitor time duration, enter the following command:

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
config cli monitor info duration <integer>
3 To clear the display, type Ctrl/L.
4 To set the monitor time interval, enter the following command:

config cli monitor info interval <integer>
5 To clear the display, type Ctrl/L.
—End—
Variable Value
duration <integer> <integer> is an integer value with a
range of 1 to 1800 seconds.
interval <integer> <integer> is an integer value with a
range of 1 to 600 seconds.
Configuration example: Monitoring port statistics

This configuration example uses the config cli monitor command to
display the port statistics every 10 seconds for a duration of 300 seconds.
MERS-8606:5# config cli monitor duration 300 interval 10
"Monitor commands" (page 192) lists the monitor commands for ports
and MultiLink Trunking (MLT).
Monitor commands
monitor commands
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 stats bridging [<ports>] [from <value>]
monitor ports stats rmon [<ports>] [from <value>]
monitor ports stats stp [<ports>] [from <value>]

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
monitor commands
monitor ports stats interface extended [<ports>] [from
<value>]
monitor ports stats interface main [<ports>] [from <value>]
monitor ports stats interface utilization [<ports>] [from
<value>]
"Routing monitor commands" (page 193) lists the monitor commands

for routing functions.
Routing monitor commands

routing monitor commands
monitor ports error ospf [<ports>] [from <value>]
monitor ports stats dhcp-relay [<ports>] [from <value>]
monitor ports stats ospf extended [<ports>] [from <value>]
monitor ports stats ospf main [<ports>] [from <value>]
monitor ports stats routing [<ports>] [from <value>]
monitor ports stats vrrp extended [<ports>] [from <value>]
monitor ports stats vrrp main [<ports>] [from <value>]
monitor ports stats pos [<ports>] [from <value>]
monitor ports stats wis main [<ports>] [from <value>]
Configuration example: Monitoring error collisions

This configuration example uses the preceding commands to monitor error
collisions and to set the monitor port statistics.
MERS-8606:5 monitor ports error collision 1/1-1/15

MERS-8606:5/config/cli/monitor# monitor port stats
interface utilization
To stop monitoring collision statistics, you can enter CTRL C, q, or press

ESC.
"Config cli monitor ports error collision command sample output" (page 194)
shows the results of this command.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Config cli monitor ports error collision command sample output
Clearing statistics
To clear statistics from counters, flush entries from a table, or end a Telnet
session use the clear command.
Clearing ATM statistics

Use the following procedure to clear Asynchronous Transfer Mode (ATM)
statistics.
Procedure steps
Step Action
1 To clear ATM Embedded Local Area Network (ELAN) statistics, enter

clear atm elan-stats <ports> <vlan id>
2 To clear ATM F5 statistics, enter the following command:

clear atm f5-stats [<ports>]
3 To clear ATM port statistics, enter the following command:

clear atm port-stats [<ports>]
—End—
Variable Value
ports Specifies the ports for which you are
entering the command in the form
portlist {slot/port[-slot/port][, ..]}.
vlan id The vlan id is a value from 1 to
4095.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Clearing entries from the ARP table

Use the following procedure to clear Address Resolution Protocol (ARP)
entries from the ARP table.
Procedure steps
Step Action
1 To clear ARP port entries from the ARP table, enter the following
command:
clear ip arp ports <port>
2 To clear ARP VLAN entries from the ARP table, enter the following
command:
clear ip arp vlan <vid>
—End—
Variable Value
vlan <vid> The vlan <vid> is the VLAN ID.
Clearing statistics for access control entities

Use the following procedure to clear statistics for access control entities.
Procedure steps
Step Action
1 To clear traffic statistics for all the access control entries or for the
specified entry, enter the following command:
clear filter acl statistics default [<acl-id>]
2 To clear port statistics for all the access control entries or for the
specified entry, enter the following command:
clear filter acl statistics port [<acl-id>]
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
<acl-id> <acl-id> is a value from 1 to 4096.
Clearing route entities

Use the following procedure to clear route entities.
Procedure steps
Step Action
1 To clear route entries associated with a specified port, enter the

following command:
clear ip route ports <port>
2 To clear route entries associated with a VLAN, enter the following

command:
clear ip route vlan <vid>
—End—
Variable Value
<vid> The <vid> is the VLAN ID. The valid
values are 0 to 255.
Clearing IP VRRP statistics

Use the following procedure to clear Internet Protocol (IP) Virtual Router
Redundancy Protocol (VRRP) statistics.
Procedure steps
Step Action
1 To clear IP VRRP statistics for the specified ports and virtual router,
clear ip vrrp ports <ports> vrid <value>
2 To clear IP VRRP statistics for the specified VLAN and virtual router,

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
clear ip vrrp vlan <vid> vrid <value>
—End—
Variable Value
<value> The <value> specifies the virtual
router. The valid values are 0 to 255.
<vid> The <vid> is the VLAN ID. The valid
values are 1 to 4095.
Clearing MLT IST statistics

Use the following procedure to clear MultiLink Trunking (MLT) Inter Switch
Trunk (IST) statistics.
Procedure steps
Step Action
1 To clear MLT IST statistics, enter the following command:

clear mlt ist stats
—End—
Clearing port statistics from the switch counters

Use the following procedure to clear port statistics from the switch counters.
Procedure steps
Step Action
1 To clear port statistics from the switch counters, enter the following
command:
clear ports stats [<ports>]
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
Ending the Telnet session

Use the following procedure to end the specified Telnet session.
Procedure steps
Step Action
1 To end the specified Telnet session, enter the following command:

clear telnet <session id>
—End—
Variable Value
<session id> <session id> is a number between
0 and 7.
Configuration example: Clearing statistics

This configuration example uses the preceding command to:
• clear ATM ELAN statistics
• clear ATM F5 statistics
• clear ATM port statistics
• clear ARP port entries from the ARP table
After configuring the parameters, use the info command to show a

summary of the results.
MERS-8606:5# clear atm elan-stats 4/1 1

MERS-8606:5# clear atm f5-stats 4/1
MERS-8606:5#
clear atm port-stats 4/1
MERS-8606:5#
clear ip arp ports 4/3

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
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
• "Running a trace route test using Device Manager" (page 199)
• "Viewing trace route results using Device Manager" (page 201)
• "Viewing the trace route probe history using Device Manager" (page 203)
• "Tracing the route to a remote host using the CLI" (page 204)
• "Configuring an automatic trace using the CLI" (page 205)
Running a trace route test using Device Manager

Create and run trace route test entries and log the cumulative test result
as well as the test results for each probe. You can specify the frequency
of test reruns and specify the following parameters: Target Address, Data
Size, Probe Count, Time-Out period, and Data Pattern.
Procedure steps
Step Action
Ping/Trace Route.
2 Click the Trace Route Control tab.
The Trace Route Control tab appears.
Trace Route Control tab
3 In the Trace Route Control tab, click Insert and create an entry.
4 In the Trace Route Control tab, click the entry.

The Trace Route Result, Trace Route History, Start, and Stop
buttons are activated.
For information about the Trace Route Control fields, see the
following table.
5 Click Start.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
OwnerIndex Provides access control by a security administrator
using the View-Based Access Control Model (VACM)
for tables in which multiple users may need to
independently create or modify entries.
TestName Specifies the name of the Trace Route test.
TargetAddressType Specifies the type of host address to be used on the
Trace Route request at the remote host.
TargetAddress Specifies the host address used on the Trace Route
request at the remote host.
ByPassRouteTable Using this field you can optionally enable bypassing of
the route table.
DataSize Specifies the size of the data portion of a Trace Route
request in octets.
TimeOut Specifies the timeout value, in seconds, for a Trace
Route request.
ProbesPerHop Specifies the number of times to reissue a Trace Route
request with the same time-to-live (TTL) value.
Port Specifies the UDP port to which you need to send the
Trace Route request.
MaxTtl Specifies the maximum time-to-live value.
DSField Specifies the value to store in the Differentiated
Services (DS) field in the IP packet used to encapsulate
the Trace Route probe.
SourceAddressType Specifies the type of the source address,
TraceRouteCtlSourceAddress, to be used at a remote
host when you perform a trace route operation.
SourceAddress Uses the specified IP address (which must be given as
an IP number, not a hostname) as the source address
in outgoing probe packets.
IfIndex Directs the Trace Route probes to be transmitted over
the specified interface
MiscOptions Enables an application to specify implementation-depe
ndent options.
MaxFailures Indicates the maximum number of consecutive
timeouts allowed before terminating a remote Trace
Route request.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
DontFragment Enables setting of the don’t fragment flag (DF) in the IP
header for a probe.
InitialTtl Specifies the initial TTL value to use.
Frequency Specifies the number of seconds to wait before
repeating a trace route test as defined by the value of
the various objects in the corresponding row.
StorageType Specifies the storage type for this conceptual row.
AdminStatus Specifies the desired state that a TraceRouteCtlEntry
should be in. The options are:
• Enabled—Attempt to activate the test as defined

by this TraceRouteCtlEntry.
• Disabled—Deactivate the test as defined by this
TraceRouteCtlEntry.
MaxRows Specifies the maximum number of entries allowed in
the TraceRouteProbeHistoryTable.
TrapGeneration Determines when to generate a notification for this
entry. The options are:
• PathChange—Generate a TraceRoutePathChange
notification when the current path varies from a
previously determined path.
• TestFailure—Generate a TraceRouteTestFailed
notification when the full path to a target can’t be
determined.
• TestCompletion—Generate a TraceRouteTestCo
mpleted notification when the path to a target has
been determined.
Descr Describes the remote trace route test.
CreateHopsEntries Keeps the current path for a trace route test in the
TraceRouteHopsTable on a per hop basis when the
value of this object is true.
Type Reports or selects the implementation method to be
used for performing a trace route operation.
Viewing trace route results using Device Manager

View the results of the trace route.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
Ping/Trace Route.
3 Click a field.
The Trace Route Result button is enabled
4 Click the Trace Route Result button.

Trace Route Result dialog box
For information about the Trace Route Result fields, see the following
—End—
Variable definition
Variable Value
Ownerindex Specifies the index of the owner.
Testname Specifies the name of the test.
Operstatus Specifies the operational status of
the test. The default is disabled.
CurHopCount Specifies the current count of
hops.
CurProbeCount Specifies the current count of
probes.
IpTgtAddressType Specifies the IP target address
type
IpTgtAddr Specifies the IP target address.
TestAttempts Specifies the number of test
attempts.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
TestSuccesses Specifies the number of
successful test attempts.
LastGoodPath Specifies the date and time when
the last response is received for
a probe.
Viewing the trace route probe history using Device Manager

View the history of the trace route probe to see the probe information for
the hops in the routing path.
Procedure steps
Step Action
Ping/Trace Route.
3 In the Trace Route Control tab, click a field.

The trace Route Probe History button is enabled.
4 Click the Route Probe History button.

The Trace Route Probe History dialog box appears.
Trace Route Probe History

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
For information about the Trace Route Probe History fields, see the
variable definitions table that follows this procedure.
—End—
Variable Value
Ownerindex Identifies the Trace Route entry to
which a probe result belongs.
TestName The test name.
Index The Index.
HopIndex Indicates for which hop in a traceroute
path the probe results are intended.
ProbeIndex The index of a probe for a particular
hop in a traceroute path.
HAddrType The IP address type of the hop to
which this probe belongs.
Haddr The IP address of the hop to which
this probe belongs.
Response The cumulative results at any time.
Status The status of the probe.
LastRC When a new entry is added in the
ProbeHistoryTable, the old entry is
purged if the total number of entries
exceeds the specified maximum
number of entries in the Control Table
Entry
Time The response time of the probe.
Tracing the route to a remote host using the CLI

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

traceroute <ipaddr> [<datasize>] [-m <value>] [-p
<value>] [-q <value>] [-w <value>] [-v]
"Traceroute command sample output" (page 205) shows output from
the traceroute command.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Traceroute command sample output
—End—
Variable Value
ipaddr Specifies the IP address of the remote
host.
datasize The size of the probe packet (1 to 1464).
-m <value> Specifies the maximum time-to-live (TTL)
value (1 to 255).
-p <value> Specifies the base UDP port number (0
to 65 535).
-q <value> Specifies the number of probes per TTL
(1 to 255).
-w <value> Specifies the wait time per probe (1 to
255).
-v Specifies the verbose mode (showing all).
Configuring an automatic trace using the CLI

Use the following procedures to configure the switch to automatically do a
trace in the event that the CPU utilization reaches a predefined value.
Prerequisites
• The enabling or disabling of auto-trace is not saved to the configuration
file. When the MERS 8600 reboots, the auto-trace functionality is
disabled.
Enabling and displaying information about the automatic trace

feature
Use the following procedure to enable the automatic trace feature
Procedure steps
Step Action
1 To enable the automatic trace feature, enter the following command:

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
trace auto-enable
2 To display information about the trace, enter the following command:

trace auto-enable info
"Trace auto-enable info command sample output" (page 206) shows
sample output for the trace auto-enable info command.
Trace auto-enable info command sample output
—End—
Enabling auto-trace
Use the following procedure to enable auto-trace. When you enable
auto-trace, central processing unit (CPU) utilization increase by up to 30
percent.
Procedure steps
Step Action
1 To enable the automatic trace feature, enter the following command:

trace auto-enable auto-trace enable
2 To disable the automatic trace feature, enter the following command:

trace auto-enable auto-trace disable
Auto-trace is disabled by default.
—End—
Adding a module
Use the following procedure to add a module to be traced or removed a
module from automatic tracing.
Procedure steps

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Step Action
1 To add a module to be traced by the trace auto-enable feature, enter

trace auto-enable add-module <modid> <level>
2 To remove a module from automatic tracing, enter the following

command:
trace auto-enable remove-module <modid>
—End—
Variable Value
level level identifies the level of detail
you want in the trace. For example,
0 = Disabled, 1 = Very Terse. For
a complete list of module IDs, enter
trace auto-enable add-module
?.
modid modid identifies the module that
you want to add or remove. For
example, 3 = Port Manager, 20 =
Topology Discovery. For a complete
list of module IDs, enter trace
auto-enable add-module ?.
Enabling auto-trace based on CPU utilization percentage

Use the following procedure to specify when auto-trace is enabled based on
CPU utilization percentage.
Procedure steps
Step Action
1 To specify the CPU utilization percentage above which auto-trace is

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

disabled, enter the following command:
trace auto-enable low-percentage <percent>
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
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
Triggering a trace based on CPU monitoring time

Use the following procedure to specify the time to monitor CPU utilization
before triggering a trace.
Procedure steps
Step Action
1 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>
2 To specify the time (in seconds) to monitor CPU utilization before

disabling a trace, enter the following command:
trace auto-enable low-track-duration <seconds>
—End—
Variable Value
seconds seconds is a value from 3 to 10. The
default is 5.
Using ping snoop

Use the ping snoop feature to troubleshoot MultiLink Trunking (MLT) and
Split MultiLink Trunking (SMLT) networks.
Ping snoop displays the route that IP traffic takes over an MLT or SMLT path.
Ping snoop works by using a filter that copies Internet Control Message
Protocol (ICMP) messages to the CPU. 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

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Using ping snoop 209
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 shown on the management console.
Ping snoop uses one of the available global filters (0-7). If eight global filters
are configured on a port prior to enabling ping snoop, ping snoop cannot
be enabled for a port. You must remove at least one of the global filters
to enable ping snoop.
Ping snoop configurations are not saved to the configuration file and are
deleted when resetting the switch. In addition, your ping snoop configuration
is erased if you log off and then log on under a different security level
If you have an R module installed in the MERS 8600 and configure

ping snoop, you must use an ACL filter option. See "Troubleshooting
configuration examples" (page 253) for an example of how to configure
ping snoop on an R module. For information about ACL filters, see Nortel
Metro Ethernet Routing Switch 8600 Configuration — QoS and Traffic
Management (NN46220-508).
Navigation
• "Configuring ping snoop" (page 209)
Configuring ping snoop

Configure and enable ping snoop to trace the route that IP traffic takes
over an MLT or SMLT path.
Procedure steps
Step Action
1 To start configuring ping snoop, enter the following command:

config diag ping-snoop
2 To create a ping snoop filter you must enter two arguments, the
source IP address and the destination IP address. To create the
filter, enter the following command:
config diag ping-snoop create src-ip <value> dst-ip
<value>
3 To enable ping snoop to trace the route that IP traffic takes over an
MLT or SMLT path, enter the following command:
config diag ping-snoop enable true
4 To add ports to the ping snoop filter (after the filter is created), enter

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
config diag ping-snoop add-port <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.
5 To display information about the ping snoop filter and the ports on
which it is applied, enter the following command:
config diag ping-snoop info
6 To remove the ping snoop filter on a particular port, enter the

following command:
config diag ping-snoop remove-port <ports>
7 To remove the ping snoop filter from any ports that were added and
also delete the filter, enter the following command:
config diag ping-snoop delete
—End—
Variable Value
add-ports <ports> ports specifies the port or range
of ports in the format slot/port
[-slot/port][,...] when you apply the
ping snoop filter
dst-ip <value> dst-ip value is 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.
enable <true|false> Enables or disables the ping snoop
filter.
remove-ports <ports> portsis the port or range of ports to
remove from a ping snoop filter.
src-ip <value> src-ip value is 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.
Configuration example: Configuring ping snoop

This configuration example shows how to create and enable a ping snoop
filter, and add ports to it.
System:5# config diag ping-snoop

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
MERS-8606:5/config/diag/ping-snoop# create src-ip

default dst-ip default
MERS-8606:5/config/diag/ping-snoop# enable true
MERS-8606:5/config/diag/ping-snoop# add-ports 1/1
Running a ping test

Create and run ping test entries, and log the cumulative test results as well
as the test results of each probe. You can specify the frequency of test
reruns and specify the following parameters: Target Address, Data Size,
Probe Count, Time-Out period, and Data Pattern.
Procedure steps
Step Action
Ping/Trace Route and click the Ping Control tab.
The Ping Control dialog box appears.
Ping Control tab
2 In the Ping Control tab, click Insert.

The Insert Ping Control tab appears.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Insert Ping Control tab
For more information, see the following variable definitions table.
3 In the OwnerIndex box, type the owner index.

4 In the TestName box, type the name of the test.
5 In the TargetAddress box, type the host address.

6 From the AdminStatus options, choose enabled or disabled.
7 In the remainder of the option boxes, type the desired values and
click Insert.
8 Select an entry in the Ping Control table.
The Ping Result, Ping Probe History, and Start buttons are activated.
9 To run a Ping test, click Start. Click Stop to stop the Ping test.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
OwnerIndex Provides access control by a security administrator
using the View-Based Access Control Model
(VACM) for tables in which multiple users may
need to independently create or modify entries.
This is a string of up to 32 characters.
TestName Specifies the name of the Ping test.
TargetAddressType Specifies the type of host address to be used at a
remote host to perform a ping operation.
TargetAddress Specifies the host address to be used at a remote
host to perform a ping operation.
DataSize Specifies the size of the data portion to be
transmitted in a ping operation in octets.
TimeOut Specifies the timeout value, in seconds, for a
remote ping operation.
ProbeCount Specifies the number of times to perform a ping
operation at a remote host.
AdminStatus Specifies the state of the ping control entry should
be in. Options are:
• Enabled—Activate the test as defined by this

ping control entry.
• Disabled —Deactivate the test as defined by
this ping control entry.
DataFill Determines how to fill the data portion of a probe
packet
Frequency Specifies the number of seconds to wait before
repeating a ping test as defined by the values of
the various objects in the corresponding row.
MaxRows Specifies the maximum number of entries allowed
in the PingProbeHistory table.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
TrapGeneration Specifies the value of this object determines when
to generate a notification for this entry. The options
are:
• ProbeFailure—Generates a PingProbeFailed
notification subject to the value of
pingCtlTrapProbeFailureFilter. The object
pingCtlTrapProbeFailureFilter can be used to
specify the number of successive probe failures
that are required before a pingProbeFailed
notification can be generated.
• TestFailure—Generates a PingTestFailed
notification. In this instance the object
pingCtlTrapTestFailureFilter can be used to
determine the number of probe failures that
signal when a test fails.
• TestCompletion—Generates a
PingTestCompleted notification.
TrapProbeFailureFilter Specifies the number of successive probe failures
that are required before a pingProbeFailed
notification can be generated.
TrapTestFailureFilter Determines the number of probe failures that
signal when a test fails.
Descr Describes the remote ping test.
SourceAddress Specifies the IP address (which must be given in
numeric form, not as a hostname) as the source
address in outgoing probe packets.
ByPassRouteTable Enables optionally the bypassing of the route table.
Viewing the ping probe history

View the history of a ping probe.
Procedure steps
Step Action
Ping/Trace Route and click the Ping Control tab.
The Ping Control dialog box appears.
2 In the Ping Control dialog box, click any field.

The Ping Probe History button is activated.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
3 Click the Ping Probe History button.

The Ping Probe History dialog box appears ("Ping Probe History
dialog box" (page 215)).
Ping Probe History dialog box
For more information, see the following variable definitions table.
—End—
Variable Value
Ownerindex The owner index
Testname The name given to the test.
Index The index number.
Response The number of responses.
Status At what status the response stands.
LastRC The last time recorded.
Time The time taken to respond.
Viewing a ping result

View the result of a ping.
Procedure steps
Step Action
and click the Ping tab.
The Ping dialog box appears.
2 In the Ping dialog box, click any field.

The Ping Result button is activated.
3 Click the Ping Result button.
The Ping Result dialog box appears ("Ping Result" (page 216)).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Ping Result
For information about the Ping Result fields, see the following
—End—
Variable Value
OwnerIndex The index of the owner.
TestName The test name.
OperStatus The operational status of the test. The default is
disabled.
IpTargetAddressType The IP address type of the target.
IpTargetAddress The IP address of the target.
MinRtt The minimum ping round-trip-time (RTT) received.
A value of 0 for this object means that no RTT is
received.
MaxRtt The maximum ping RTT received. A value of 0 for
this object means that no RTT is received.
AverageRtt The current average ping RTT.
ProbeResponses The number of responses for probes.
SentProbes The number of probes that are sent.
RttSumofSquares The sum of squares of all probes received.
LastGoodProbe The date and time when the last response is
received for a probe.
Performing a loopback test

Perform a loopback test.
Prerequisites
• Test mode must be enabled to perform a loopback test; otherwise you
receive an error message.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 To perform a loopback test, enter the following command:

test loopback <ports> [<int|ext>]
—End—
Variable Value
int|ext int|ext is a string length between 1
and 1536.
ports ports specifies the ports for which
you are entering the command in the
form port list {slot/port[-slot/port][, ...]}.
The following warning message appears when you perform a loopback test
using the test loopback command.
CPU utilization will dramatically increase with this

diagnostic.
This could affect the performance of box.
Do you really want to loopback (y/n) ?
Testing the switch fabric and address resolution table

Test the switch fabric and check the address resolution (AR) table for
consistency.
Navigation
• "Testing the switch fabric" (page 217)
• "Viewing address resolution statistics" (page 219)
• "Displaying address resolution table using the CLI" (page 222)
Testing the switch fabric

Use the Test tab in Device Manager to test the switch fabric and check the
address resolution (AR) table for consistency.
The fabric test causes the central processing unit (CPU) to generate traffic
and send it through the switch fabric. Given the forwarding rate of the MERS
8600, the CPU does not generate much traffic, but it performs a simple test
of the switch fabric memory.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The AR table test performs a consistency check on address resolution table

entries.
Procedure steps
Step Action
> General.
The Diagnostics dialog box opens with the Test tab displayed
("Diagnostics dialog box, Test tab" (page 218)).
Diagnostics dialog box, Test tab
The following test options are available:

• Test the AR Test.
• Test the switch fabric (Fabric).
• Stop a test in progress.
2 Click AR Test or Fabric, as required.

For information about the Test tab fields, see the following variable
definitions table.
—End—
Variable Value
Result The result of the most recently run (or current) test:
• none
• success
• inProgress
• notSupported

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
• unAbleToRun
• aborted
• failed
Code More specific information about the test result (for example, an
error code after a failed test):
• none
• NoReceive (timeout on a send)
• BadSeq (packets received out of sequence)
• BadLen (packet length mismatch)
• BadData (packet data mismatch)
PassCount The number of iterations of the test case that completed
successfully.
FailCount The number of iterations of the test case that failed.
Viewing address resolution statistics

View the address resolution (AR) statistics for the internal state of the AR
translation table. These statistics are debugging aids. You should use them
only when consulting with Nortel support personnel.
Procedure steps
Step Action
> General.
2 Click the AR Stats tab.
The AR Stats tab appears.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Diagnostics, AR Stats tab
The statistic of most interest is the NoSpace counter, which indicates

the number of entries the AR table could not add because of lack of
space.
For information about the AR Stats tab fields, see the following

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
—End—
Variable Value
TblSize The size of the AR translation table.
Free The number of free entries that are available in
the AR translation table.
NoSpace The number of entries that were not added to the
AR translation table because of lack of space.
Added The number of entries added to the AR translation
table.
Deleted The number of entries deleted from the AR
translation table.
MacAdded The number of MAC entries added to the AR
translation table.
MacDeleted The number of MAC entries deleted from the AR
translation table.
MacMoved The number of MAC entries moved in the AR
translation table.
IpAdded The number of IP entries added to the AR
translation table.
IpDeleted The number of IP entries deleted from the AR
translation table.
McastTblSize The size of the Multicast AR translation table.
FreeMcastGroups The number of free multicast groups available in
the AR table.
IpMcastAdded The number of IP multicast entries added to the
AR table.
IpMcastDeleted The number of IP multicast entries deleted from
the AR table.
VlanByPortAdded The number of VLAN by Port entries added to
the AR table.
VlanByPortDeleted The number of VLAN by Port entries deleted from
the AR table.
VlanByProtocolAdded The number of VLAN by Protocol Type entries
added to the AR table.
VlanByProtocolDeleted The number of VLAN by Protocol Type entries
deleted from the AR table.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
VlanByIpSubnetAdded The number of VLAN by IP Subnet entries added
to the AR table.
VlanByIpSubnetDeleted The number of VLAN by IP Subnet entries deleted
from the AR table.
IpSubnetsAdded The number of IP Subnet entries added to the AR
table.
IpSubnetsDeleted The number of IP Subnet entries deleted from
the AR table.
RsvpsAdded The number of Resource Reservation Setup
Protocol (RSVP) entries added to the AR table.
RsvpsDeleted The number of RSVP entries deleted from the AR
table.
Displaying the address resolution table using the CLI

Display the contents of the RaptARU attached to OctaPID in an address
resolution table.
Procedure steps
Step Action
1 To display the contents of the RaptARU attached to OctaPID in an

address resolution table, enter the following command:
dump ar <opid> <vlan|ip_subnet|mac_vlan|mac|arp|ip|ipx|
ipmc|ip_filter|protocol|sys_rec|all> <verbosity>
"Dump ar command sample output" (page 223) uses the preceding
commands to specify an octaPID and specify a record type in the
AR table.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Dump ar command sample output
—End—
Variable Value
opid Specifies the octaPID assignment,
from 1 to 64.
For more information, see Configuring
Network Management (314723-E).
vlan|ip_subnet|mac_vlan|mac Specifies a record type in the address
|arp|ip|ipx|ipmc|ip_filter| resolution (AR) table.
protocol|sys_rec|all
verbosity Specifies the verbosity level, from 0
to 3. Higher numbers specify more
verbosity.
Checking the MIB status

View the MIB topology status and table information.
Navigation
• "Viewing topology status information" (page 224)
• "Viewing the MIB topology table" (page 225)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Viewing topology status information

Use the Topology tab to view Nortel management information base (MIB)
topology status information.
Procedure steps
Step Action
Topology and click the Topology tab.
The Topology dialog box appears (see "Topology tab" (page 224)).
Topology tab
For information about the Topology tab fields, see the following
2 Click Refresh.
—End—
Variable Value
IpAddr The IP address of the device.
Status Indicates if 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.
NmmMaxNum The maximum number of entries in the NMM topology
table.
NmmCurNum The current number of entries in the NMM topology
table.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Viewing the MIB topology table

View the Nortel management information base (MIB) topology table
information.
Procedure steps
Step Action
and click the Topology Table tab.
The Topology Table tab appears (see "Topology Table tab" (page
225)).
Topology Table tab
For information about the Topology Table tab fields, see the following
—End—
Variable Value
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.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
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:
• topChanged—Topology information has recently

changed.
• heartbeat—Topology information is unchanged.
• new—The sending agent is in a new state.
Using rapid ping

The Metro Ethernet Service Units tests traffic data issues such as
connectivity, latency, and packet loss using rapid ping.
Configure rapid ping to troubleshoot traffic issues between customer devices
and the Metro Ethernet Service Unit. Rapid ping is based on the Metro
Ethernet Service Unit’s standard ICMP ping protocol. Rapid ping is used to:
• check connectivity on the network
• measure the traffic loss rate
• check latency between the ESU and a local or remote network device
• respond to pings in the datapath, from devices connected to the Metro
Ethernet 8600
You initially configure the:

• source IP address on the network
• destination IP address on the network
• type of test (for stand-alone and ring modes only)
• mode
• customer’s remote or local device VLAN identification
• customer port (port on the customer device)
Navigation
• "Configuring rapid ping using Device Manager" (page 227)
• "Enabling responses to pings in the data path using Device Manager"
(page 229)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
• "Testing traffic using rapid ping in the CLI" (page 230)

• "Configuring the ESU for a customer rapid ping request" (page 241)
• "Example of enabling the ESU for a rapid ping response" (page 242)
• "Example of configuring the default gateway" (page 243)
Configuring rapid ping using Device Manager

To initiate pings to customer devices outside the subnet, you must also
configure rapid ping gateway information on the ESU connected to the
customer device located within the subnet:
• DefaultGatewayIpAddr
• DefaultGatewayIpNetMask
• DefaultGatewayState
Procedure steps
Step Action
1 From the Device Manager menu bar, select Rapid Ping > Ping.
The RapidPing dialog box appears.
RapidPing dialog box
2 Click each field to change the value.
3 Click Refresh to refresh the statistics.
—End—
Variable Value
SrcIpAddr The configured source (or sending) IP address of the
test.
DestIpAddr The IP address of the destination (receiving) customer
router.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
Mode The ESU mode: RTT or throughput
• RTT indicates that only one IP rapid ping packet is
sent, at a time, during the test session.
• throughput indicates that IP rapid ping packets
are sent out in the specified transmission interval
during the test session.
The only difference in test results is that round trip time

(RTT) information (minimum, maximum, and average)
does not display in throughput mode. The default
value is RTT.
For rapid ping results, the displayed RTT values
are round down to the nearest ten millisecond. For
example, if the maximum or minimum RTT is less than
10ms, then the value t is displayed as 0ms.
Custvid The customer’s VLAN identification information in the
range of 1 to 4094 or 4096. In ring or stand-alone
mode, Custvid = 4094 indicates an untagged test
packet. In Layer 2 switch mode, Custvid = 4096
indicates an untagged test packet.
Pbit The configured pbit value for the tagged test packet.
This value applies to management traffic. Tagged test
packet values are 1 to 4094 in ring and stand-alone
mode. The pbit value range is 0 to 7; the default value
is 0.
CustPort The ESU port connected to the customer router that
forwards and receives test packets.
PktSize The Ethernet test packet size on the ESU. The range
is 64 to 1522 for tagged packets and 64 to 1518 for
untagged packets. The default is 1522.
PktCnt The number of test packets to be sent. The range is 1
to 10000. The default is 1.
PktInterval The time interval between test packets measured in
milliseconds (ms). The range is 10 to 1000 ms in 10
ms increments. The default is 1000 ms.
TimeoutInterval The maximum interval between the transmission and
reception of the test frame. After the expiration of
this interval time, the test packet is considered to
have failed. The range is 1 to 10 seconds (s) in 1 s
increments. The default is 3 s.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
Action The action of the test. Options include:
• ready
• run—conducts the test
• delete—deletes the test
• stop—stops the test
Status The status of the test. Options include:
• running—the test is running
• finished—the test is complete
MinRTT The minimum round trip time (RTT), in milliseconds,
for the test packet.
example, if the minimum RTT is less than 10ms, then
the value t is displayed as 0ms.
MaxRTT The maximum round trip time (RTT), in milliseconds,
example, if the maximum RTT is less than 10ms, then
the value t is displayed as 0ms.
AverageRTT The average round trip time (RTT), in milliseconds,
LossPercent The packet loss percentage.
PktTx The number of test packets transmitted.
PktRx The number of test packets received.
PercentComplete The percentage of complete packets received.
DefaultGatewayIpAd The rapid ping session uses the DefaultGatewayIPAddr
dr as the destination IP or dest-ip-addr. This is the IP
address of the customer device within the subnet.
DefaultGatewayIpNe The destination network mask for the rapid ping
tMask session.
DefaultGatewayState Enables or disables the rapid ping gateway feature
on this ESU device.
Enabling responses to pings in the data path using Device Manager

Enable responses to pings in the data path to allow the ESU to perform
service layer and end-to-end tests from one ESU through the service
provider network to a second ESU switch.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 From the Device Manager menu bar, select Rapid Ping > Response
to open the Rapid Ping Response dialog box.
2 Click the entry in the State column you want to modify to open the
list.
3 Select Enabled.
4 Click Apply.
—End—
Rapid ping response dialog
Field Description
State Enable or disable responses to rapid
ping on this ESU device.
SrcIpAddr The IP address that the ESU device
responding to the ping assumes.
SrcIpAddrNetMask The net mask for the device
responding to the ping.
CustVid The ID for the customer VLAN where
pings are received.
CustPort The customer port associated with
pings.
Testing traffic using rapid ping in the CLI

The ESU identifies the customer device that is being pinged through the
ESU. You cannot configure the ESU ring (or stand-alone) port as the
customer port. The following table provides possible combinations for the
ESU in Layer 2 or Q-in-Q modes, local or remote rapid ping test types, and
sequence of events between the ESU and device ports.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The following table provides possible combinations for the ESU , local or
remote rapid ping test types, and sequence of events between the ESU
and device ports.
Use the following procedures to test traffic using rapid ping.
Prerequisites
• The config rapid-ping and config rapid-ping-response
command sets are two different functions. You cannot use both
command sets at the same time.
Setting the source IP address

Use the following procedure to set the source IP address for the test.
Procedure steps
Step Action
1 To set the source IP address for the rapid ping test, enter the
following command:
config rapid-ping src-ip-addr <ipaddr>
—End—
Variable Value
src-ip-addr <ipaddr> The IP address of the source (sending)
device, designated in a.b.c.d. format.
If the src-ip-addr of the source
device is outside the IP subnet, you
must add the default gateway.
Setting the destination IP address

Use the following procedure to set the destination IP address for the test.
Procedure steps
Step Action
1 To set the destination IP address, enter the following command:

config rapid-ping dest-ip-addr <ipaddr>
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
dest-ip-addr <ipaddr> The IP address of the destination
(receiving) device in the test;
designated in a.b.c.d format.
If the <ipaddr> of the destination
device is outside the IP subnet, you
must add the default-gateway.
Setting the mode

Use the following procedure to set the rapid ping mode.
Procedure steps
Step Action
1 To set the rapid ping mode, enter the following command:

config rapid-ping mode <rtt|throughput>
—End—
Variable Value
mode <rtt|throughput> The rapid ping mode.
<rtt|throughput> indicates two
mode choices; is the current rapid
ping mode; one of two choices. The
default value is rtt (round trip time).
rtt (Round Trip Time) means only
one IP rapid ping packet is sent at a
time during the test session. If, after a
specified timeout interval is reached
and no response is received, the
packet is considered lost and another
ping packet is sent.
throughput means IP rapid ping
packets are sent in a specified
transmission packet interval during
the test session.
The only difference in test results
is that RTT information (minimum,
maximum, and average) does not
display in throughput mode.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
For rapid ping results, the displayed

RTT values are round down to the
nearest ten millisecond. For example,
if the maximum or minimum RTT is
less than 10ms, then the value t is
displayed as 0ms.
Configuring the Ethernet Services Unit port

Use the following procedure to configure the Ethernet Services Unit port
used in connecting to the customer device port.
Procedure steps
Step Action
1 To configure the Ethernet Services Unit port which is used

in connecting to the customer device port, enter the following
command:
config rapid-ping cust-port <port>
—End—
Variable Value
cust-port <port> The Ethernet Services Unit port
connected to the customer router that
forwards and receives test packets in
a rapid ping test.
The Ethernet Services Unit identifies
the network (customer) router port
that is pinged through the Ethernet
Services Unit. The Ethernet Services
Unit ring or stand-alone port is not
configured as the customer port.
Configuring the customer VLAN ID

Use the following procedures to configure the customer VLAN Id for the
rapid ping test.
Procedure steps

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Step Action
1 To configure the customer VLAN ID for the rapid ping test, enter
config rapid-ping cust-vid <vid>
—End—
Variable Value
<cvid> The customer’s VLAN identification
information.
The customer VLAN ID is an integer
set in the range from 1 to 4094 or
4096; vid 4096 in Layer 2 mode is an
untagged test packet. (For Q-in-Q
mode, if cust-vid is 4096, the test
packet is not considered.)
Configuring the VLAN ID when the ESU responds to ping

requests
Use the following procedure to configure the VLAN ID when the ESU
responds to ping requests from a local or remote device.
Procedure steps
Step Action
1 To configure the VLAN ID when the ESU responds to ping requests

from a local or remote device, enter the following command:
config rapid-ping-response cust-vid <vid>
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
cust-vid <vid> cust-vid is the customer’s VLAN
identification information.
The VLAN ID <vid> is an integer set
in the range from 1 to 4094 or 4096;
cust-vid 4096 in Layer 2 mode is an
untagged test packet.
Directly configuring the Ethernet Services Unit access port to

the customer device port
Use the following procedure to directly configure the ESU access port to the
customer device port.
Procedure steps
Step Action
1 To directly configure the ESU access port to the customer device

port, enter the following command:
config rapid-ping cust-port <port>
—End—
Variable Value
cust-port cust-port is the ESU port connected
to the customer router that forwards
and receives test packets. The ESU
identifies the network (customer)
router port that is being pinged. You
cannot configure the ESU ring or
stand-alone port as the customer
port. All test packets are forwarded
and received over the customer port
connection.
<port> <port> is an integer that identifies
the ESU port.
Configuring the ESU port to respond to customer ping requests

Use the following procedure to configure the ESU port. The port is used to
connect to the customer device port after the ESU is enabled to respond
to customer ping requests.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 To configure the ESU port to respond to customer ping requests,

config rapid-ping-response cust-port <port>
—End—
Variable Value
cust-port The ESU port used to connect to the
customer device. All test packets
are forwarded and received over this
connection.
<port> <port> is an integer that identifies
the ESU port.
Configuring network management frames

Use the following procedure to configure network management frames with
a pbit marking value.
Procedure steps
Step Action
1 To configure network management frames with a pbit marking value,

config rapid-ping pbit <value 0-7>
—End—
Variable Value
pbit <value 0-7> The configured pbit value for the
tagged test packet.
Tagged test packet values are vid !=
4094 in ring and stand-alone and vid
!= 4096 in Layer 2 mode.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Variable Value
The value range is 0 to 7; the default

value is 0.
Configuring the Ethernet packet size for the test

Use the following procedure to configure the Ethernet packet size for the
test.
Procedure steps
Step Action
1 To configure the Ethernet packet size for the test, enter the following
command:
config rapid-ping pkt-size <value 64 - 1522>
—End—
Configuring the number of Ethernet test packets

Use the following procedure to configure the number of Ethernet test
packets.
Procedure steps
Step Action
1 To configure the number of Ethernet test packets, enter the following

command:
config rapid-ping pkt-cnt <value 1 - 10000>
—End—
Variable Value
pkt-cnt The configurable number of test
packets.
<value 1-10000> <value 1-10000> is the range of
values; the default value is 1.
Configuring the time interval between test packets

Use the following procedure to configure the time interval between test
packets.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 To configure the time interval between test packets, enter the

following command:
config rapid-ping pkt-interval <value 10 - 1000>
—End—
Variable Value
pkt-interval The time interval between test packets
sent.
<value 10-1000> 10-1000 is the range of values
measured in milliseconds (ms); the
default is 1000.
Configuring the time interval between test packets

Use the following procedure to configure the time interval between test
packets.
Procedure steps
Step Action
1 To configure the time interval between test packets, enter the

following command:
config rapid-ping pkt-interval <10 - 1000>
—End—
Variable Value
<10-1000> 10-1000 is the range of values
measured in milliseconds (ms); the
default is 1000.
pkt-interval The time interval between test packets
sent.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Configuring the timeout interval of the test packets

Use the following procedure to configure the timeout interval of the test
packets.
Procedure steps
Step Action
1 To configure the timeout interval of the test packets, enter the

following command:
config rapid-ping timeout-interval <value 1 - 10>
—End—
Variable Value
timeout-interval <value The time interval, measured in
1-10> seconds, before rapid ping times out.
1-10 is the range of values; the
default is 3 seconds.
Running the configured rapid ping test

Use the following procedure to run the configured rapid ping test.
As the test runs, the ESU displays the progress of the test with the
percentage of completion with a period (.) displaying periodically during
the test.
In the default running mode, the ESU displays the exclamation mark ! for
every failed test frame received.
Procedure steps
Step Action
1 To run the configured rapid ping test, enter the following command:
config rapid-ping run
2 To stop a running rapid ping test, press Ctrl+c.

The test immediately stops and the abort command displays on
the screen.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Deleting a previously configured test

Use the following procedure to delete a previously configured test.
Procedure steps
Step Action
1 To delete a previously configured test, enter the following command:

config rapid-ping delete
—End—
Examples
Example of setting up a local type rapid ping test
The following commands provide an example of setting up values for a
rapid ping test in a local environment:
config rapid-ping src-ip-addr 10.1.1.1
config rapid-ping dest-ip-addr 10.1.1.10
config rapid-ping type local
config rapid-ping mode default
config rapid-ping cust-vid 1
config rapid-ping pbit 5
config rapid-ping cust-port 5
config rapid-ping pkt-size 1522
config rapid-ping pkt-cnt 10000
config rapid-ping timeout-interval 3
Example of enabling the ESU to respond to a rapid ping request

In the following example, an ESU (ESU 2) receives rapid-ping packets
from the uplink port on ESU 1. The ESU matches the configured
customer-port and configured source IP address/IP-2, to the destination
IP address in the rapid-ping packet. ESU 2 responds to ESU 1. It is not
necessary for ESU 1 to check the customer-port for C1 status before
sending a response.
config rapid-ping-response enable
config rapid-ping-response source-ip-addr IP/8
config rapid-ping-response cust-vid 4094
config rapid-ping-response cust-port 5
config rapid-ping-response type remote

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Example of an ESU responding to a ping in the data path

In the following example, two ESUs within a network assist the remote
customer, a service provider, in performing service layer, end-to-end
tests within the provider’s network. In the test, an ESU responds to the
provider-initiated rapid pings in the data path, through a second ESU.
config rapid-ping-response source-ip-addr 129.32.1.1/24
• Set the source IP address that the ESU uses in responding to
the ping. The ESU that receives, and responds to, the rapid ping
request, will assume this address. Also, 24 is the net mask.
• Set the customer VLAN identifier. In Layer 2, 4096 is the untagged
teat packet.
• Set the ESU’s (customer facing) port.
• Set the rapid ping test type to remote, since this is a customer device.
Configuring the ESU for a customer rapid ping request

Use the following command to enable or disable the ESU port used in
connecting to the customer device port after the customer’s rapid ping
request.
The ESU identifies the customer device that is being pinged through the
ESU. You cannot configure the ESU ring (or stand-alone) port as the
customer port.
Procedure steps
Step Action
1 To enable the ESU port used in connecting to the customer device

port after the customer’s rapid ping request, enter the following
command:
2 To disable the ESU port used in connecting to the customer device

port after the customer’s rapid ping request, enter the following
command:
config rapid-ping-response disable
3 If you want to configure the customers VLAN ID when the ESU

responds to ping requests from a local or remote device, enter the
following command:

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
config rapid-ping-response cust-vid <vid>
4 You can configure an ESU port to respond to customer ping

requests, then connect to the customer device port after the ESU is
enabled. Enter the following command:
config rapid-ping-response cust-port <port>
—End—
Variable Value
cust-port The ESU port used to connect to the
customer device. All test packets
are forwarded and received over this
connection.
<port> An integer that identifies the ESU port.
<vid> The customer’s VLAN identification
information.
Example of enabling the ESU for a rapid ping response

When a customer sends a rapid ping request to an ESU, the ESU responds
if the response function is enabled. An example of enabling the ESU to
respond to the customer’s rapid ping request follows.
config rapid-ping-response source-ip-addr IP/8
In this example:
• enable enables the ESU in order to respond to the request.
• source-ip-addr is the customer’s IP address, from which the rapid
ping request originated.
• IP/8 is the IP submask.
• 4096 is the customer’s EVPN VLAN id; an untagged packet.
• cust-port 5 is the customer’s current port on which the rapid ping
originated.
• remote is the test type; the rapid ping request originating from the
remote customer site.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Example of configuring the default gateway

You can specify a default gateway on your primary ESU from a second ESU
within the network. The customer’s Router 2 (described in the previous
example above) is configured in the same subnet. When Router-2 sends a
rapid-ping request packet through the ESU-2, the destination IP address
is checked to confirm that the originating rapid-ping feature is within the
subnet configured.
• If so, the packet is transmitted to the ESU.
• If the destination IP address configured is not within the subnet, the ESU
sends an ARP for the MAC address of the default gateway router 2.
config rapid-ping default-gateway-ip-addr 10.1.1.254(R2-ip)/8

config rapid-ping default-gateway enable
config rapid-ping cust-port 5
config rapid-ping cust-vid 4094
config rapid-ping des-ip-addr 20.1.1.1
config rapid-ping src-ip-addr 10.1.1.4
config rapid-ping mode rtt
config rapid-ping pkt-cnt 100
config rapid-ping pkt-interval 10
config rapid-ping pkt-size 100
config rapid-ping type local
In this example:
• 20.1.1.1 is the IP Address for the customer device outside the subnet.
• 10.1.1.254 is the IP address for the customer device inside the subnet.
• 8 is the netmask.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
245
Understanding alarms, logs, traps, and

system messages
The System Messaging Platform (SMP) creates a scheme for the display
and access of system messages. For more information, see the Ethernet
Routing Switch 8600 Release 4.1 System Messaging Platform Reference
Guide (315015-E).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
246 Understanding alarms, logs, traps, and system messages

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
247
Supported RFCs
The list of supported Request for Comments (RFCs) are outlined in the
following documents:
• For the Nortel Metro Ethernet Routing Switch 8600, see Release Notes
— Software Release 4.2 (NN46220-403).
• For the Nortel Metro Ethernet Services Unit 1850, see Release Notes
— Software Release 3.4.0.0 (NN46211-400).
• For the Nortel Metro Ethernet Services Unit 1800, see Release Notes
— Software Release 3.4.0.0 (NN46210-400).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
248 Supported RFCs

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
249
Contacting technical support

Use the following sections to contact Nortel for technical support.
Navigation
• "Gathering critical information" (page 249)
• "Getting Help from the Nortel Web site" (page 250)
• "Getting help over the phone from a Nortel Solutions Center" (page 250)
• "Getting help from a specialist by using an Express Routing Code"
(page 251)
• "Getting help through a Nortel distributor or reseller" (page 251)
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 the critical information that should be gathered before
contacting Nortel Technical Support.
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 search the solutions database? Were any related solutions
found? Is there currently a workaround for this issue?

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
250 Contacting technical support
• 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.
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:
http://www.nortel.com/support
This site provides quick access to software, documentation, bulletins, and
tools to address issues with Nortel products. More specifically, the site
enables you to:
• 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
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Getting help through a Nortel distributor or reseller 251
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
NN46220-701 01.01 Standard
4.2 3 August 2007
.
252 Contacting technical support

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
253
Troubleshooting configuration
examples
This section provides examples of port mirroring and ping snoop
configuration tasks, including the CLI commands and Device Manager
procedures you use to create the configuration.
This section describes the following topics:
• Configuring port mirroring on an R module using the CLI
• Configuring port mirroring on an R module using Device Manager
• Configuring remote port mirroring on a legacy module using the CLI
• Configuring ping snoop on R modules
Configuring port mirroring on an R module using the CLI

This configuration example shows how to create an access control table
(ACT) and associated access control list (ACL) and access control entries
(ACE), and configure port mirroring on an R module. Specifically, this
example accomplishes the following:
• uses port 3/48 as the monitoring port
• sets up an ACL so that only Transmission Control Protocol (TCP) traffic
with a range from port 20 to 500 and Internet Control Message Protocol
(ICMP) frames are mirrored to the monitoring port
The following sections provide step-by-step example procedures that show

how to configure port mirroring on the MERS 8600.
Creating an ACT
Create a new access control table to filter on ICMP frames and TCP dst-port
Procedure steps
Step Action
1 Create a new access control table with ID = 2

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
254 Troubleshooting configuration examples
MERS-8610:5# config filter act 2 create
2 Select IP attributes of source IP and IP protocol type

MERS-8610:5# config filter act 2 ip ipProtoType
3 Select Protocol Attributes of TCP source port, TCP destination port,
and user datagram protocol (UDP) destination port
MERS-8610:5# config filter act 2 protocol
tcpDstPort
4 Enable ACT 2
MERS-8610:5# config filter act 2 apply
—End—
Creating ACL 1
Use the following procedure to create ACL 1.
Procedure steps
Step Action
1 Create ACL 1 with type of inPort:

MERS-8610:5# config filter acl 1 create inPort act
2
—End—
Adding ACEs to ACL 1

Use the following procedures to add ACEs to ACL 1.
Procedure steps
Step Action
1 Add ACE 1 with action of permit to mirror ICMP traffic:

MERS-8610:5# config filter acl 1 ace 1 create name
icmp
MERS-8610:5# config filter acl 1 ace 1 action
permit
MERS-8610:5# config filter acl 1 ace 1 debug
mirror enable

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
MERS-8610:5# config filter acl 1 ace 1 ip

ip-protocol-type eq icmp
MERS-8610:5# config filter acl 1 ace 1 enable
2 Add ACE 2 with action of permit to mirror TCP traffic with a

destination port range from 20 to 500
MERS-8610:5# config filter acl 1 ace 2 create name
tcp_range
MERS-8610:5# config filter acl 1 ace 2 action
permit
MERS-8610:5# config filter acl 1 ace 2 debug
mirror enable
MERS-8610:5# config filter acl 1 ace 2 ip
ip-protocol-type eq tcp
MERS-8610:5# config filter acl 1 ace 2 protocol
tcp-dst-port eq 20-500
MERS-8610:5# config filter acl 1 ace 2 enable
—End—
Enabling port mirroring

The following enables port mirroring:
MERS-8610:5# config diag mirror-by-port 1 create in-port

3/25 out-port 3/48 mode bothFilter enable true
Configuring port mirroring on an R module using Device Manager

This configuration example shows how to create an access control table
(ACT) and associated access control list (ACL) and access control entries
(ACE), and configure port mirroring on an R module.
• uses port 3/48 as the monitoring port
• sets up an ACL so that only Transmission Control Protocol (TCP) traffic
with a range from port 20 to 500 and Internet Control Message Protocol
(ICMP) frames are mirrored to the monitoring port
The following sections provide step-by-step procedures that show how to

configure port mirroring on the MERS 8600. In this example:
Creating an ACT
Use the following procedure to create a new access control table to filter
on ICMP frames and TCP dst-port.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Procedure steps
Step Action
1 From the Device Manager menu bar, choose Security > Data Path
> Advanced Filters (ACE/ACLs).
The following message appears: "Note: Filter configuration of R
modules only."
2 Click Ok.
The ACL dialog box appears with the ACT tab visible.
3 Click Insert.
See the following figure.
ACL, Insert ACT
4 In the ActId box, type 2.
5 In the Name box, type ACT-2.

6 From the IpAttrs box, select ipProtoType.
7 From the ProtocolAttrs options, select tcpDstPort.

8 Click Insert.
9 In the ACT tab of the ACL dialog box, double-click the Apply column
entry for ACT-2, and select True.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
10 On the ACL dialog box—ACT tab, click Apply.
—End—
Creating an ACL
Use the following procedure to create an ACL.
Procedure steps
Step Action
1 In the ACL dialog box, click the ACL tab.

The ACL tab appears.
2 Click Insert.
The ACL, Insert ACL dialog box appears (ACL, Insert ACL dialog
box).
ACL, Insert ACL dialog box
3 In the AclId box, type 1.

4 In the ActId box, type ACT-2.
5 From the Type options, select inPort.
6 In the Name box, if the name ACL-1 does not appear, type it.
7 Click Insert.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Adding ACEs to the ACL

Use the following procedure to add ACEs to the ACL.
Procedure steps
Step Action
Configure ACE 1
1 In the ACL dialog box—ACL tab, click AclId 1.

The ACE button is activated.
2 Click ACE.
The ACE, ACL1 dialog box appears with the ACE Common tab
visible.
3 Click Insert.
The ACE, ACL1, Insert ACE Common dialog box opens (Insert ACE
Common).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Insert ACE Common
4 In the AceId box, type 1.
5 In the Name box, type the name icmp.
6 From the Mode options, select permit.

7 From the Flags options, select mirror.
8 Click Insert.
9 In the ACE, ACL1 dialog box—ACE Common tab, select Ace Id 1.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The IP tab is activated.
10 Click IP.
11 Click Insert.
The Insert Protocol dialog box appears.
12 From the Oper options, select eq.

13 In the List box, type icmp.
14 Click Insert.
—End—
Procedure steps
Step Action
Configure ACE 2
1 In the ACE, ACL1 dialog box—ACE Common tab, click Insert.

The ACE, ACL1, Insert ACE Common dialog box opens.
2 in the AceId box, type 2.
3 In the Name box, type tcp_range.

4 From the Mode options, select permit.
5 From the Flags options, select mirror.

6 Click Insert.
AceId 2 appears in the ACE, ACL1 dialog box—ACE Common tab.
7 In the ACE, ACL 1 dialog box—ACE Common tab, click Insert.

The ACE, ACL 1, Insert ACE Common tab appears.
8 Click AceId 2.
The IP button is activated.
9 Click IP.
10 Click Insert.
12 In the List box, type tcp.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
13 Click Insert.
—End—
Procedure steps
Step Action
Add TCP port range
1 In the ACE, ACL 1 dialog box—ACE Common tab, click AceId 2.
2 Click the Proto tab.

3 Click Insert.

5 In the Port box, type 20-500.
6 Click Insert.
—End—
Procedure steps
Step Action
Enable ACEs and port mirroring
1 In the ACE, ACL 1 dialog box—ACE Common tab, double-click the

AdminState for AceId 1.
2 Click enable.
3 In the ACE, ACL 1 dialog box—ACE Common tab, double-click the

AdminState for AceId 2.
4 Click enable.
5 From the Device Manager menu bar, choose Edit > Diagnostics.
The Diagnostics dialog box appears with the Test tab visible.
6 Click Port Mirrors.

The Port Mirrors tab appears.
7 Click Insert.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The Diagnostics, Insert Port Mirrors dialog box appears (Diagnostics,

Insert Port Mirrors dialog box).
Diagnostics, Insert Port Mirrors dialog box
8 In the Id box, type 1.
9 In the MirroredPort box, type 3/25.

10 In the MirroringPort box, type 3/48.
11 From the Mode options, select bothFilter.

13 Click Insert.
—End—
Configuring remote port mirroring on a legacy module using the CLI

This configuration example shows how to create a separate port-based
VLAN on all switches with legacy modules to channel remote mirrored traffic
(Remote port mirror configuration example).

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Configuring remote port mirroring on a legacy module using the CLI 263
Remote port mirror configuration example
The following sections provide step-by-step procedures that show how to

configure port mirroring on a legacy module on switch S1, S2, and S3:
Configuring S3
Use the following procedure to configure port mirroring on switch S3.
Procedure steps
Step Action
1 Create a separate port-based VLAN to channel the remote mirroring

traffic in the network. In this example, use VLAN 10:
MERS-8610_3:5# config vlan 10 create byport 1
2 Add the RMT ports and the port through which remote mirrored
packets enter the switch for VLAN 10:
MERS-8610_3:5# config vlan 10 ports add 1/15,2/8
3 Add the VLAN to the RMT Ethernet port, in this example port 1/15:
MERS-8610:5# config ethernet 1/15 remote-mirroring
create
MERS-8610_3:5# config ethernet 1/15 remote-
mirroring add-vlan-id 10
mirroring mode termination

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

mirroring enable true
4 Get the destination MAC address of the RMT port. This is required
to configure RMS in the other switches:
mirroring info
—End—
Configuring S1
Procedure steps
Step Action
1 Create a separate port-based VLAN to channel the remote mirroring

traffic in the network. In this example, use VLAN 10:
2 Add the PMD port to VLAN 10:

MERS-8610_1:5# config vlan 10 ports add 1/1
3 Create port mirroring with RMS as the destination port and add
VLAN 10. The source port is the port from which packets must be
remotely mirrored:
MERS-8610_1:5# config diag mirror-by-port 1 create
in-port 1/15 out-port 1/1 mode rx enable true
remote-mirror-vlan-id 10
4 Add the destination MAC for remote mirroring to the RMS port.
This is the destination MAC address of the RMT port from switch
MERS8600-3:
MERS-8610_1:5# config ethernet 1/1 remote-mirroring
create
MERS-8610_1:5# config ethernet 1/1 remote-mirroring
dstmac 00:e0:7b:82:9d:9c
5 Enable RMS:
MERS-8610:5# config ethernet 1/1 remote-mirroring
enable true
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Configuring S2
Procedure steps
Step Action
1 Create VLAN 10
2 Add ports to VLAN 10

MERS-8610_2:5# config vlan 10 ports add 1/1,2/8
—End—
Configuring ping snoop on R modules

To configure ping snoop on R modules, you must use an ACL filter. You
can create the ACL filter as follows:
• Locate the already partially-defined ACT-ACL available pair.
The ACT and ACL names are "IP ping snoop" and the ids are 4096.
• Add the appropriate ports as members in the ACL and enable them.
• Create an ACE with actions "permit" and "copytoprimarycp".
• Create a relevant source or destination or both IP.
• Enable the ACT.
You can use your own ACT, ACL, and ACE instead, but you are duplicating
the ACT, ACL, and ACE that the system predefines.
Configuring ping snoop using the CLI

This example shows the commands you use to set up the system defined
ACL filter using the CLI:
MERS-8610:5/config/filter/acl/4096# port add 7/1,7/2

MERS-8610:5/config/filter/acl/4096# enable
MERS-8610:5/config/filter/acl/4096# ace 2 create
MERS-8610:5/config/filter/acl/4096# ace 2 action permit
MERS-8610:5/config/filter/acl/4096# ace 2 debug
copytoprimarycp enable
MERS-8610:5/config/filter/acl/4096# ace 2 ip dst-ip eq
1.1.1.2

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
You can set the source IP address or the destination IP address, or both.
Enable the ACE. You can use the info and port info commands to
verify your configuration.
MERS-8610:5/config/filter/acl/4096# ace 2 enable

MERS-8610:6/config/filter/acl/4096# info
MERS-8610:6/config/filter/acl/4096# port info
Configuring ping snoop using Device Manager

This example shows you how to set up the system-defined ACL filter using
Device Manager.
Use the following procedure to configure the ACL and the ACE.
Procedure steps
Step Action
Configure the ACL and ACE
1 From the Device Manager menu bar, choose Security > Data Path
> Advanced Filters (ACE/ACLs).
The following message appears: Note: Filter configuration of R
modules only.
2 Click Ok.
3 Click the ACL tab.

The ACL tab appears with the IP ping-Snoop ACT visible.
4 In the IP Ping-Snoop ACL row, double click the PortList.
The PortList dialog box appears.
5 Click the desired ports and then click Ok.
6 On the ACL, ACL tab, click Apply.
7 Click the ACE tab.

The ACE, ACL 4096 dialog box appears with the ACE Common
tab visible.
8 Click Insert.
The ACE, ACL 4096, Insert ACE Common dialog box appears.
9 In the AceId box, type 1.
10 In the Name box, type the name of the ACE.

11 From the Mode options, select Permit.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
12 From the Flags options, select copyToPrimaryCp.
13 Click Insert.
—End—
Use the following procedure to configure IP addresses and to enable ACE.
Procedure steps
Step Action
Configure IP addresses and enable ACE
1 Click ACE 1.
The IP button is activated.
2 Click IP.
The ACE, ACL 4096, ACE1 dialog box appears with the Source
Address tab visible.
3 Click Insert.
The IP, ACL 4096, Insert Source Address dialog box appears.
4 From the Oper options, select eq
5 In the List box, type 10.10.1.0
6 Click Insert.
7 In the ACE, ACL 4096, ACE1 dialog box, click the Destination
Address tab.
8 Click Insert.
The IP, ACL 4096, ACE1—Insert Destination Address dialog box
appears.
9 From the Oper options, select eq
10 In the List box, type 10.10.10.0.
11 Click Insert.
12 In the ACE, ACL 4096—ACE, double-click the AdminState box,

select enable, and click Apply.
13 In the ACL dialog box, double-click the State box for the IP
Ping-Snoop ACL, and select enable.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
14 Click Apply.
—End—

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
269
Diagnostics reference
This section contains reference material you can use when you perform
diagnostics on the Metro Ethernet Routing Switch 8600.
Navigation
• Special terminal characters reference
• Edit mode commands reference
• Port numbering and MAC address assignment reference
• Trap error messages reference
• Tap and OctaPID assignment reference
Special terminal characters reference

Special terminal characters lists the special terminal characters.
Special terminal characters

Key Combination Command
^H Backspace.
^D Logout of the CLI.
^C Abort line entry.
^P Previous history command.
^N Next history command.
^S Output suspend.
^Q Output resume.
Î Command completion.
^B Move the cursor back one character.
^F Move the cursor forward one character.
Â Move the cursor to the beginning of the line.
Ê Move the cursor to the end of the line.
ESC B Move the cursor back one word.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
270 Diagnostics reference
Key Combination Command

ESC F Move the cursor forward one word.
DEL Erase the character at the cursor.
^K Erase all characters from the cursor to the end of the
line.
^X Erase all characters before the cursor to beginning of
line.
Û Erase or clear the entire line.
^W Erase the word to the left of the cursor.
ESC D Erase from the cursor to the end of the word.
^L Redisplay the line.
^R Redisplay the line.
^T Transpose the character to the left of the cursor with
the character at the cursor.
ESC L Change the character at the cursor to lowercase.
ESC U Change the character at the 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
Commands available in edit mode. The ESC key switches the shell to edit
mode. The RETURN key always moves to the next line.
Commands available in edit mode is a summary of the commands available

in edit mode.
When you enter the editor, you are in edit mode.
Commands available in edit mode

Key Combination Description
:q End the editing mode without saving the changes
made to a file.
:w Quit and save the file.
ZZ Quit and save the file.
Movement and Search Commands
^L Redraw the screen.
^F Display the next screen.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Edit mode commands reference 271

^B Display the previous screen.
^D Display the next 1/2 screen.
Û Display the previous 1/2 screen.
<n>G Go to the command number n.
G Go to the last command line.
/<s> Search for the string s forward in file.
?<s> Search for the string s backward in file.
n Repeat the last search.
N Repeat the last search in the opposite direction.
<n>k Get the nth previous line in the 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 1
<n>w Move n words forward.
<n>W Move n blank-separated words forward.
<n>e Move to the end of the nth next word.
<n>E Move to the 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 the cursor to the first non-blank character in line.
$ Go to the end of the line.
0 Go to the beginning of the line.
Insert commands (input is expected until an ESC is typed)
a Append.
A Append at the end of the line.
c SPACE Change character.
cl Change character.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

cw Change word.
cc Change entire line.
c$ Change everything from the cursor to the end of the
line.
C Same as "c$."
S Same as "cc."
i Insert.
I Insert at the beginning of the line.
R Type over characters.
o Open a line below current line.
O 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.
Port numbering and MAC address assignment reference

This section includes information about the following topics:
• Port numbering
• Interface indexes
• MAC address assignment
Port numbering
A port number includes the slot location of the module in the chassis, as
well as the port’s position in the I/O module. In the 8600 switches, slots are
numbered from top to bottom. 8010 chassis slots shows slot numbering
for an 8010 chassis.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Port numbering and MAC address assignment reference 273
8010 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
8648TX module, ports in the top row are assigned sequential odd numbers,
and ports in the bottom row are assigned sequential even numbers (Port
numbers on high-density modules).
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 (VLAN), and Multi-Link Trunks.
The interface index of a port is computed using the following formula:
inIndex = (64 x slot number) + (port number – 1)
where
• slot number is a value between 1 and 10, inclusive.

• port number is a value between 1 and 48, inclusive.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
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 MGID
where
MGID is the multicast group ID number.
Because the default VLAN always has an MGID value of 1, its interface
index is always 2049.
The interface index of a Multi-Link Trunk (MLT) is computed using the

following formula:
ifIndex = 4096 + MLT ID number
The interface index for tunnels was introduced in Release 4.1. The range is
4352-4451.
The interface index for a tunnel is computed using the following formula:
ifIndex = 4352 + Tunnel ID number
MAC address assignment

Understanding how Media Access Control (MAC) addresses are assigned
is important when you define static Address Resolution Protocol (ARP)
entries for IP addresses in the switch and when you use a network analyzer
to decode network traffic.
Each MERS 8600 module is assigned a base of 1024 MAC addresses.
Within the switch, these MAC addresses are assigned as follows:
• 512 addresses for ports in the switch (physical MAC addresses)
• 500 addresses for VLANs in the switch (virtual MAC addresses)
• 8 addresses for central processing unit (CPU) interfaces
• 4 addresses for use by other 8600 modules
A MAC address has the format shown in Parts of a MAC address.

Parts of a MAC address

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
The MAC address is divided into the following parts:

• bits 47–24: IEEE OUI (for example, 00-80-2d)
• bits 23–10: Chassis ID
• bit 9: Type of MAC address in the switch:
— 0 = Port address (physical MAC address)
— 1 = VLAN address (virtual MAC address)
• bits 8–0: Unique port or VLAN address
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 Bridge Protocol Data Units (BPDU) sent by
the switch
• frames to or from an isolated routing port 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 or the CPU module have the following last
bytes:
• management port in slot 5: 0xf4
• CPU port (an internal port) in slot 5: 0xf5
• management port in slot 6: 0xf6
• CPU port in slot 6: 0xf7
• virtual management IP address: 0xf8
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 Internet Protocol (IP) address is the virtual MAC address
assigned to the VLAN.
Trap error messages reference

Proprietary traps
OID 1.3.6.1.4.1.2272.1.21.0.1
Notification type rcnCardDown

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Objects rcCardIndex, rcCardAdminStatus, rcCardOperStatus

Status current
Description A rcCardDown trap signifies that the Simple Network
Management Protocol version 2 (SNMPv2) entity,
acting in an agent role, has detected that the
rcCardOperStatus object for one of its cards is about to
transition into the down state.
OID 1.3.6.1.4.1.2272.1.21.0.2
Notification type rcnCardUp
Objects rcCardIndex, rcCardAdminStatus, rcCardOperStatus
current
Status current
Description A rcCardUp trap signifies that the SNMPv2 entity,
acting in an agent role, has detected that the
transition into the up state.
OID 1.3.6.1.4.1.2272.1.21.0.3
Notification type rcnErrorNotification
Objects rcErrorLevel, rcErrorCode, rcErrorText
Status current
Description A rcErrorNotification trap signifies that the SNMPv2
entity, acting in an agent role, has detected that an
error condition has occurred.
OID 1.3.6.1.4.1.2272.1.21.0.4
Notification type rcnStpNewRoot
Objects rcStgId
Status current
Description A rcStpNewRoot trap signifies that the SNMPv2 entity,
acting in an agent role, has detected the Spanning
Tree Protocol (STP), and has declared the device to
be the new root of the spanning tree.
OID 1.3.6.1.4.1.2272.1.21.0.5
Notification type rcnStpTopologyChange
Objects rcStgId, rcPortIndex

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description A rcStpTopologyChange trap signifies that the
SNMPv2 entity, acting in an agent role, has detected
that the Spanning Tree Protocol has gone due to a
topology change event.
OID 1.3.6.1.4.1.2272.1.21.0.6
Notification type rcnChasPowerSupplyDown
Objects rcChasPowerSupplyId, rcChasPowerSupplyOperSta
tus
Status current
Description A rcChasPowerSupplyDown trap signifies that the
rcChasPowerSupplyOperStatus object for one of its
power supply units is about to transition into the down
state.
OID 1.3.6.1.4.1.2272.1.21.0.7
Notification type rcnChasFanDown
Objects rcChasFanId, rcChasFanOperStatus
Status current
Description A rcChasFanDown trap signifies that the SNMPv2
entity, acting in an agent role, has detected that the
rcChasFanOperStatus object for one of its power
supply units is about to transition into the down state.
OID 1.3.6.1.4.1.2272.1.21.0.8
Notification type rcnLinkOscillation
Objects rcPortIndex
Status current
Description A rcLinkOscillation trap signifies that the SNMPv2
entity, acting in an agent role, has transitions on the
specified port.
OID 1.3.6.1.4.1.2272.1.21.0.9
Notification type rcnMacViolation
Objects rcErrorText, rcPortIndex

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description A rcMacViolation trap signifies that the SNMPv2 entity,
acting in an agent role, has received a Protocol Data
Unit (PDU) with an invalid source Medium Access
Control (MAC) address.
OID 1.3.6.1.4.1.2272.1.21.0.10
Notification type rcnSonetTrap
Objects rcPortIndex, rcPosSonetTrapType, rcPosSonetTrapI
ndication
Status current
Description A rcSonetTrap trap signifies that the SNMPv2 entity,
acting in an agent role, has detected a change of status
on a Sonet port.
OID 1.3.6.1.4.1.2272.1.21.0.11
Notification type rcn2kCardDown
Objects rc2kCardIndex, rc2kCardFrontAdminStatus,
rc2kCardFrontOperStatus
Status current
Description A rc2kCardDown trap signifies that the SNMPv2
transition into the down state.
OID 1.3.6.1.4.1.2272.1.21.0.12
Notification type rcn2kCardUp
Objects rc2kCardIndex, rc2kCardFrontAdminStatus,
rc2kCardFrontOperStatus
Status current
Description A rc2kCardUp trap signifies that the SNMPv2
entity,acting in an agent role, has detected that the
transition into the up state.
OID 1.3.6.1.4.1.2272.1.21.0.13
Notification type rcn2kTemperature
Objects rc2kChassisTemperature

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description A rc2kTemperature trap signifies that the
SNMPv2entity, acting in an agent role, has detected
the chassis is overheating.
OID 1.3.6.1.4.1.2272.1.21.0.14
Notification type rcnChasPowerSupplyUp
Objects rcChasPowerSupplyId, rcChasPowerSupplyOperSta
tus
Status current
Description A rcChasPowerSupplyUp trap signifies that the
that the rcChasPowerSupplyOperStatus object for one
of its power supply units is about to transition into the
up state.
OID 1.3.6.1.4.1.2272.1.21.0.15
Notification type rcn2kAtmPvcLinkStateChange
Objects rc2kAtmPvcIfIndex, rc2kAtmPvcVpi, rc2kAtmPvcVci,
rc2kAtmPvcOamVcStatus
Status current
Description A rc2kAtmPvcLinkStateChange trap signifies that the
that the rc2kAtmPvcOamVcStatus object for one of the
PVCs is about to transition into a different state, either
from up to down, or from down to up.
OID 1.3.6.1.4.1.2272.1.21.0.16
Notification type rcnStpTCN
Objects rcStgId, rcPortIndex, rcStgBridgeAddress
Status current
Description A rcStpTCN trap signifies that the SNMPv2 entity,
acting in an agent role, has detected the Spanning Tree
Protocol has gone due to a topology change event.
OID 1.3.6.1.4.1.2272.1.21.0.17
Notification type rcnSmltIstLinkUp
Objects

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description A rcSmltIstLinkUp trap signifies that the Split Multi-Link
Trunk (SMLT) link is from down to up.
OID 1.3.6.1.4.1.2272.1.21.0.18
Notification type rcnSmltIstLinkDown
Objects
Status current
Description A rcSmltIstLinkDown trap signifies that the SMLT link
is from up to down.
OID 1.3.6.1.4.1.2272.1.21.0.19
Notification type rcnSmltLinkUp
Objects rcMltSmltId
Status current
Description A rcnSmltLinkUp trap signifies that the SMLT link is up.
OID 1.3.6.1.4.1.2272.1.21.0.20
Notification type rcnSmltLinkDown
Objects rcMltSmltId
Status current
Description A rcnSmltLinkDown trap signifies that the SMLT link
is down.
OID 1.3.6.1.4.1.2272.1.21.0.21
Notification type rcnChasFanUp
Objects rcnChasFanUp
Status current
Description A rcChasFanUp trap signifies that the SNMPv2
rcChasFanOperStatus object for one of its power
supply units is about to transition into the up state.
OID 1.3.6.1.4.1.2272.1.21.0.22
Notification type rcnPasswordChange
Objects rc2kCardIndex, rcChasEmModeError

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description A rcPasswordChange trap signifies that the SNMPv2
entity, acting in an agent role, has detected that one of
the cli passwords has changed.
OID 1.3.6.1.4.1.2272.1.21.0.23
Notification type rcnEmError
Objects rc2kCardIndex, rcChasEmModeError
Status current
Description A rcEmError trap signifies that the SNMPv2 entity,
acting in an agent role, has detected an Em error.
OID 1.3.6.1.4.1.2272.1.21.0.25
Notification type rcnPcmciaCardRemoved
Objects
Status current
Description A rcPcmciaRemoved trap signifies that the SNMPv2
entity, acting in an agent role, has detected that
the Personal Computer Memory Card International
Association (PCMCIA) or (PC) card is being removed.
OID 1.3.6.1.4.1.2272.1.21.0.26
Notification type rcnSmartCpldTimerFired
Objects rc2kCardIndex
Status current
Description A rcSmartCpldTimerFired trap signifies that the CPLD
timer fired.
OID 1.3.6.1.4.1.2272.1.21.0.27
Object type rcnCardCpldNotUpDate
Status current
Description A rcCardCpldNotUpDate trap signifies that the cpld is
not up to date.
OID 1.3.6.1.4.1.2272.1.21.0.28
Notification type rcnIgapLogFileFull
Objects

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description A rcIgapLogFileFull trap signifies that the Igap
accounting time-out log file has reached the maximum
size.
OID 1.3.6.1.4.1.2272.1.21.0.29
Notification type rcnCpLimitShutDown
Objects rcPortIndex, ifAdminStatus, ifOperStatus,
rcPortCpLimitShutDown
Status current
Description A rcCpLimitShutDown trap signifies that the CP limit for
the port is shutting down.
OID 1.3.6.1.4.1.2272.1.21.0.30
Notification type rcnSshServerEnabled
Objects
Status current
Description A rcSshServerEnabled trap signifies that the Secure
Shell (SSH) server is enabled.
OID 1.3.6.1.4.1.2272.1.21.0.31
Notification type rcnSshServerDisabled
Objects rcSshGlobalPort
Status current
Description A rcSshServerDisabled trap signifies that the SSH
server is disabled.
OID 1.3.6.1.4.1.2272.1.21.0.32
Notification type rcnSshSessionLogin
Objects rcSshGlobalHostIpAddr
Status current
Description A rcSshSessionLogin trap signifies that there is an
SSH session login.
OID 1.3.6.1.4.1.2272.1.21.0.33
Notification type rcnSshSessionLogout
Objects rcSshGlobalHostIpAddr

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description A rcSshSessionLogout trap signifies that there is an
SSH session logout
OID 1.3.6.1.4.1.2272.1.21.0.34
Notification type rcnSshUnauthorizedAccess
Objects rcnSshUnauthorizedAccess
Status current
Description A rcSshUnauthorizedAccess trap signifies that an
unauthorized access has occurred.
OID 1.3.6.1.4.1.2272.1.21.0.35
Notification type rcnHaCpuState
Objects rc2kCardIndex, rcL2RedundancyHaCpuState
Status current
Description A rcHaCpuState trap signifies the state of the High
Availability (HA)-CPU.
OID 1.3.6.1.4.1.2272.1.21.0.36
Notification type rcnInsufficientMemory
Status current
Description A rcInsufficientMemory trap indicates insufficient
memory on the CPU blade for proper operation. The
recommended memory is 256 MB, available through
the Nortel upgrade kit.
OID 1.3.6.1.4.1.2272.1.21.0.37
Notification type rcnSaveConfigAction
Objects rcSysActionL1
Status current
Description A rcSaveConfigAction trap indicates that the switch
run-time or boot configuration is being saved.
OID 1.3.6.1.4.1.2272.1.21.0.38
Notification type rcnLoopDetectOnPort
Objects rcVlanId, rcPortIndex

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description A rcLoopDetectOnPort trap indicates that a loop has
been detected on a port. The VLAN on that port will
be disabled.
OID 1.3.6.1.4.1.2272.1.21.0.39
Notification type rcnbgpEstablished
Objects rcIpBgpPeerIpAddress, rcIpBgpPeerLastError,
rcIpBgpPeerState
Status current
Description The rcnbgpEstablished event is generated when the
Border Gateway Protocol (BGP) Full Screen Mode
(FSM) enters the ESTABLISHED state.
OID 1.3.6.1.4.1.2272.1.21.0.40
Notification type rcnbgpBackwardTransition
Objects rcIpBgpPeerIpAddress, rcIpBgpPeerLastError,
rcIpBgpPeerState
Status current
Description The rcnbgpBackwardTransition Event is generated
when the BGP FSM moves from a higher numbered
state to a lower numbered state.
OID 1.3.6.1.4.1.2272.1.21.0.41
Notification type rcnAggLinkUp

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Objects rcMltId
Status current
Description A rcAggLinkUp trap is generated when the operational
state of the aggregator changes from down to up.
OID 1.3.6.1.4.1.2272.1.21.0.42
Notification type rcnAggLinkDown
OID rcMltId
Status current
Description A rcAggLinkDown trap is generated when the
operational state of the aggregator changes from up
to down.
OID 1.3.6.1.4.1.2272.1.21.0.43
Notification type rcnIgmpNewGroupMember
Objects rcIgmpGroupIfIndex, rcIgmpGroupIpAddress,
rcIgmpGroupInPort, rcIgmpGroupMembers
Status current
Description An IgmpNewGroupMember trap signifies that a new
member has come on an interface.
OID 1.3.6.1.4.1.2272.1.21.0.44
Notification type rcnIgmpLossGroupMember
Objects rcIgmpGroupMembers,rcIgmpGroupIpAddress,
rcIgmpGroupInPort,rcIgmpGroupIfIndex

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description An IgmpLossGroupMember trap signifies that a group
member has been lost on an interface.
OID 1.3.6.1.4.1.2272.1.21.0.45
Notification type rcnIgmpNewQuerier
OID igmpInterfaceIfIndex,igmpInterfaceQuerier
Status current
Description An igmpNewQuerier trap signifies that a new querier
has come up on an interface.
OID 1.3.6.1.4.1.2272.1.21.0.46
Notification type rcnIgmpQuerierChange
Objects igmpInterfaceIfIndex, rcIgmpInterfaceExtnNewQuer
ier,igmpInterfaceQuerier
Status current
Description An rcIgmpQuerierChange trap signifies that the querier
has changed.
OID 1.3.6.1.4.1.2272.1.21.0.47
Notification type rcnDvmrpIfStateChange
Objects dvmrpInterfaceIfIndex, dvmrpInterfaceOperState
Status current
Description A rcDvmrpIfStateChange trap signifies that there
has been a change in the state of a Distance Vector
Multicast Routing Protocol (DVMRP) interface.
OID 1.3.6.1.4.1.2272.1.21.0.48
Notification type rcnDvmrpNewNbrChange
Objects dvmrpNeighborIfIndex, dvmrpNeighborAddress
Status current
Description A rcDvmrpNewNbrChange trap signifies that a new
neighbor has come up on a DVMRP interface.
OID 1.3.6.1.4.1.2272.1.21.0.49
Notification type rcnDvmrpNbrLossChange
Objects dvmrpNeighborIfIndex, dvmrpNeighborAddress

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description A rcDvmrpNbrLossChange trap signifies that a new
neighbor has gone down on a DVMRP interface.
OID 1.3.6.1.4.1.2272.1.21.0.59
Notification type rcnFdbProtectViolation
Objects rcPortIndex, rcVlanId
Status current
Description The rcFdbProtectViolation trap signifies that the has
violated the user-configured limit for total number of
Forwarding Database (FDB) entries learned on that
port.
OID 1.3.6.1.4.1.2272.1.21.0.60
Notification type rcnLogMsgControl
Objects rcSysMsgLogFrequency, rcSysMsgLogText
Status current
Description A rcMsgControl trap signifies whether the number of
repetitions of the particular log message has exceeded
the particular frequency/count.
OID 1.3.6.1.4.1.2272.1.21.0.61
Notification type rcnSaveConfigFile
Objects rcSysActionL1, rcSysConfigFileName
Status current
Description A rcSaveConfig trap signifies that either the runtime
configuration or the boot configuration has been saved
on the switch.
OID 1.3.6.1.4.1.2272.1.21.0.62
Notification type rcnDNSRequestResponse
Objects rcSysDnsServerListIpAddr, rcSysDnsRequestType
Status current
Description A rcDnsRequestResponse trap signifies that the
switch sent a query to the DNS server or it received a
successful response from the DNS server.
OID 1.3.6.1.4.1.2272.1.21.0.63
Notification type rcnDNSRequestResponse

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Objects ipNetToMediaNetAddress,ipNetToMediaPhysAddress
Status current
Description A rcDuplicateIpAddress trap signifies that a duplicate
IP address is detected on the subnet.
OID 1.3.6.1.4.1.2272.1.21.0.64
Notification type rcnLoopDetectPortDown
Objects rcPortIndex,ifAdminStatus,ifOperStatus
Status current
Description A rcLoopDetectPortDown trap signifies that a loop has
been detected on a port, and the port is going to shut
down.
OID 1.3.6.1.4.1.2272.1.21.0.67
Notification type rcnLoopDetectMacDiscard
Objects rcPortIndex, rcSysMacFlapLimitTime, rcSysMacFlapLi
mitCount
Status current
Description A rcLoopDetectMacDiscard trap signifies that a loop
has been detected on a port, and the MAC address will
be discarded on all ports in that VLAN.
OID 1.3.6.1.4.1.2272.1.21.0.68
Notification type rcnAutoRecoverPort
Objects rcPortIndex
Status current
Description A rcnAutoRecoverPort trap signifies that autorecover
has reenabled a port disabled by link flap or cp limit.
OID 1.3.6.1.4.1.2272.1.21.0.69
Notification type rcnAutoRecoverLoopDetectedPort
Objects rcVlanNewLoopDetectedAction
Status current
Description A rcnAutoRecoverPort trap signifies that autorecover
has cleared the action taken on a port by loop detect.
OID 1.3.6.1.4.1.2272.1.21.0.70
Notification type rcnExtCpLimitShutDown

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Objects rcPortIndex, ifAdminStatus

Status current
Description A rcnExtCpLimitShutDown trap signifies that the port is
shut down due to the extended CP limit.
OID 1.3.6.1.4.1.2272.1.21.0.71
Notification type rcnExtCpLimitSopCongestion
Objects rcSysExtCplimitSysOctapidCongested, rcSysExtCpl
imitPortsMonitored
Status current
Description A rcnExtCpLimitSopCongestion signifies whether the
system OctaPID polling finds that the system OctaPID
is congested. rcSysExtCplimitSysOctapidCongested
signifies whether the system OctaPID is congested.
rcSysExtCplimitPortsMonitored signifies whether ports
are selected for monitoring the ingress traffic utilization.
OID 1.3.6.1.4.1.2272.1.21.0.80
Notification type rcnVlacpPortDown
Objects rcPortIndex
Objects current
Description A rcnVlacpPortDown trap signifies that the Virtual Link
Aggregate Control Protocol (VLACP) is down on the
port specified.
OID 1.3.6.1.4.1.2272.1.21.0.81
Notification type rcnVlacpPortUp
Objects rcPortIndex
Status current
Description A rcnVlacpPortUp trap signifies that the VLACP is up
on the port specified.
OID 1.3.6.1.4.1.2272.1.21.0.82
Notification type rcnExtCpLimitShutDownNormal
Objects

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description An rcnExtCpLimitShutDownNormal trap signifies that
ports are shut down due to extended CP-Limit in
Normal mode.
OID 1.3.6.1.4.1.2272.1.21.0.83
Notification type rcnEapMacIntrusion
Objects rcSysIpAddr, rcRadiusPaePortNumber,
rcRadiusEapLastAuthMac, rcRadiusEapLastRejMac
Status current
Description A rcnEapMacIntrusion trap signifies that an Extensible
Authentication Protocol (EAP) MAC intrusion has
occurred on this port.
OID 1.3.6.1.4.1.2272.1.21.0.84
Notification type rcnInterCpuCommStatus
Objects rc2kCardIndex, rcCardOperStatus
Status Current
Description A rcnInterCpuCommStatus trap signifies the current
communication status between primary and secondary
CPU.
OID 1.3.6.1.4.1.2272.1.50.2.1
Object type rcWisSonetTrapType
Syntax Integer
sectionAlarm 1

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
lineAlarm 2
pathAlarm 3
Max-access read-only
Status current
Description Used to indicate a particular type of 10GE Sonet trap.
OID 1.3.6.1.4.1.2272.1.50.2.2
Object type rcWisSonetTrapIndication
Syntax Integer
noDefect 1
sectionLossOfSignal 2
sectionLossOfFrame 3
lineAlarmIndication 4
lineRemoteDefectIndication 5
pathLossOfPointer 6
pathAlarmIndication 7
pathRemoteDefectIndication 8
pathUnequipped 9
pathSignalLabelMismatch 10
pathTraceMismatch 11
Max-access read-only
Status current
Description Used to indicate an indication for a 10GE Sonet trap.
OID 1.3.6.1.4.1.2272.1.64.1.0.1
Notification type rcnSlppPortDownEvent
Objects rcSlppPortSlppEnable, rcSlppVlanSlppEnable,
rcSlppIncomingVlanId, rcSlppSrcMacAddress
Status current
Description A port down event that has occurred due to Simple
Loop Protection Protocol (SLPP). The user is notified
of the expected Vlan ID along with the Vlan ID and
source MAC address of the packet coming in on the
port identified. The first two objects can be used to look
up instance information for port ID and VLAN ID.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Standard traps
OID 1.3.6.1.6.3.1.1.5.1
Notification type coldStart
Objects
Status current
Description A coldStart trap signifies that the SNMPv2 entity,
acting in an agent role, is reinitializing itself and that its
configuration may have been altered.
OID 1.3.6.1.6.3.1.1.5.2
Notification type warmStart
Objects
Status current
Description A warmStart trap signifies that the SNMPv2 entity,
acting in an agent role, is reinitializing itself such that
its configuration is unaltered.
OID 1.3.6.1.6.3.1.1.5.3
Trap type linkUp
Enterprise snmp
Variables ifIndex
Description A linkUp trap signifies that the sending protocol entity
recognizes a failure in one of the communication links
represented in the agent’s configuration.
OID 1.3.6.1.6.3.1.1.5.4
Trap type linkUp
Enterprise snmp
Variables ifIndex
Description A linkUp trap signifies that the sending protocol
entity recognizes that one of the communication links
represented in the agent’s configuration has come up.
OID 1.3.6.1.6.3.1.1.5.5
Notification type authenticationFailure
Objects

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description An authenticationFailure trap signifies that the SNMPv2
entity, acting in an agent role, has received a protocol
message that is not properly authenticated. While all
implementations of the SNMPv2 must be capable of
generating this trap, the snmpV2EnableAuthenTraps
object indicates whether this trap is generated.
OID 1.3.6.1.2.1.14.16.2.1
Notification type ospfVirtIfStateChange
Objects ospfRouterId (the originator of the trap),
ospfVirtIfAreaId, ospfVirtIfAreaId, ospfVirtIfNeighbor,
ospfVirtIfState (the new state)
Status current
Description An ospfIfStateChange trap signifies that there is a
change in the state of an Open Shortest Path First
(OSPF) virtual interface.This trap is generated when
the interface state regresses (for example, goes from
Point-to-Point to Down) or progresses to a terminal
state (that is, Point-to-Point).
OID 1.3.6.1.2.1.14.16.2.2
Notification type ospfNbrStateChange
Objects ospfRouterId (the originator of the trap), ospfNbrIpAddr,
ospfNbrAddressLessIndex, ospfNbrRtrId, ospfNbrState
(the new state)
Status current
Description An ospfNbrStateChange trap signifies that there is a
change in the state of a nonvirtual OSPF neighbor.
This trap is generated when the neighbor state
regresses (for example, goes from Attempt or Full to
1-Way or Down) or progresses to a terminal state (for
example, 2-Way or Full). When a neighbor transitions
from or to Full on non-broadcast, multi-access, and
broadcast networks, the trap is generated by the
designated router. A designated router transitioning to
Down is noted by ospfIfStateChange.
OID 1.3.6.1.2.1.14.16.2.3
Notification type ospfVirtNbrStateChange
ospfVirtNbrArea, ospfVirtNbrRtrId, ospfVirtNbrState
(the new state)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description An ospfIfStateChange trap signifies that there has been
a change in the state of an OSPF virtual neighbor. This
trap is generated when the neighbor state regresses
(for example, goes from Attempt or Full to 1-Way or
Down) or progresses to a terminal state (for example,
Full).
OID 1.3.6.1.2.1.14.16.2.4
Notification type ospfIfConfigError
ospfIfIpAddress, ospfAddressLessIf,ospfPacketSrc
(the source IP address), ospfConfigErrorType (type
of error, ospfPacketType)
Status current
Description An ospfIfConfigError trap signifies that a packet has
been received on a nonvirtual interface from a router
whose configuration parameters conflict with this
router configuration parameters. Note that the event
optionMismatch causes a trap only if it prevents an
adjacency from forming.
OID 1.3.6.1.2.1.14.16.2.5
Notification type ospfVirtIfConfigError
Objects ospfRouterId (the originator of the trap), ospfVirtIfAre
aId, ospfVirtIfNeighbor, ospfConfigErrorType (type of
error), ospfPacketType
Status current
Description An ospfConfigError trap signifies that a packet has
been received on a virtual interface from a router
whose configuration parameters conflict with this
router configuration parameters. Note that the event
optionMismatch causes a trap only if it prevents an
adjacency from forming.
OID 1.3.6.1.2.1.14.16.2.6
Notification type ospfIfAuthFailure
ospfIfIpAddress, ospfAddressLessIf, ospfPacketSrc
(the source IP address), ospfConfigErrorType
(authTypeMismatch or authFailure, ospfPacketType)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description An ospfIfAuthFailure trap signifies that a packet
has been received on a nonvirtual interface from a
router whose authentication key or authentication
type conflicts with this router authentication key or
authentication type.
OID 1.3.6.1.2.1.14.16.2.7
Notification type ospfVirtIfAuthFailure
Objects ospfRouterIdt (the originator of the trap),
ospfVirtIfAreaId, ospfVirtIfAreaId, ospfVirtIfNeighbor,
ospfConfigErrorType (authTypeMismatch or
authFailure, ospfPacketType)
Status current
Description An ospfVirtIfAuthFailure trap signifies that a packet has
been received on a virtual interface from a router whose
authentication key or authentication type conflicts with
this router authentication key or authentication type.
OID 1.3.6.1.2.1.14.16.2.16
Notification type ospfIfStateChange
ospfIfIpAddress, ospfAddressLessIf, ospfIfState (the
new state)
Status current
Description An ospfIfStateChange trap signifies that there has
been a change in the state of a nonvirtual OSPF
interface. This trap is generated when the interface
state regresses (for example, goes from DR to Down)
or progresses to a terminal state (that is, Point-to-Point,
DR Other, DR, or Backup).
OID 1.3.6.1.2.1.80.0.1
Notification type pingProbeFailed
Objects pingCtlTargetAddressType, pingCtlTargetAddress,
pingResultsOperStatus, pingResultsIpTargetAddressT
ype, pingResultsIpTargetAddress, pingResultsMinRtt,
pingResultsMaxRtt, pingResultsAverageRtt,
pingResultsProbeResponses, pingResultsSentProbes,
pingResultsRttSumOfSquares, pingResultsLastGood
Probe

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Status current
Description A rcnAggLinkUp trap is generated when a probe
failure is detected when the corresponding
pingCtlTrapGeneration object is set to probeFailure(0)
subject to the value of pingCtlTrapProbeFailureFilter.
The object pingCtlTrapProbeFailureFilter can be used
to specify the number of successive probe failures that
are required before this notification is generated.
OID 1.3.6.1.2.1.80.0.2
Notification type pingTestFailed
Probe
Status current
Description A pingTestFailed trap is generated when a ping test
is determined to have failed when the corresponding
pingCtlTrapGeneration object is set to testFailure(1).
In this instance, pingCtlTrapTestFailureFilter specifies
the number of probes that must fail in a test to consider
the test as failed.
OID 1.3.6.1.2.1.80.0.3
Notification type pingTestCompleted
Probe
Status current
Description A pingTestCompleted is generated at the
completion of a ping test when the corresponding
pingCtlTrapGeneration object is set to
testCompletion(4).
OID 1.3.6.1.2.1.81.0.1
Notification type traceRoutePathChange

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Objects traceRouteCtlTargetAddressType, traceRouteCtl

TargetAddress, traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr
Status current
Description The path to a target has changed.
OID 1.3.6.1.2.1.81.0.2
Notification type traceRouteTestFailed
Status current
Description Could not determine the path to a target.
OID 1.3.6.1.2.1.81.0.3
Notification type traceRouteTestCompleted
Status current
Description The path to a target has been determined.
OID 1.3.6.1.2.1.16.0.1
Trap type risingAlarm
Enterprise rmon
Variables alarmIndex, alarmVariable, alarmSampleType,alarmV
alue, alarmRisingThreshold
Description The SNMP trap that is generated when an alarm entry
crosses its falling threshold and generates an event
that is configured for sending SNMP traps.
OID 1.3.6.1.2.1.16.0.2
Trap type fallingAlarm
Enterprise rmon
Variables alarmIndex, alarmVariable, alarmSampleType,alarmV
alue, alarmFallingThreshold
Description The SNMP trap that is generated when an alarm entry
crosses its falling threshold and generates an event
that is configured for sending SNMP traps.

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Tap and OctaPID assignment reference

The switch fabric in the Metro Ethernet Routing Switch 8600 modules has
nine switching taps, one for each of the eight I/O slots (1 to 4 and 7 to 10)
and one for the CPU slots (5 and 6). Taps 0-7 map to the eight I/O slots
and can support up to eight OctaPIDs. Each OctaPID can support up to
eight ports.
In the MERS 8600, a physical port number is 10 bits long and has the
following format:
bits 9–6: Tap number (0–15)
bits 5–3: OctaPID number (0–7)
bits 2-0: MAC port number (0-7)
The tap number bits and the OctaPID number bits combined (bits 9–3) are
usually referred to as the OctaPID ID.
Available module types and OctapPID ID assignments lists the module

types that are currently available, along with the associated OctaPID ID
assignments for each module.
Available module types and OctapPID ID assignments

OctaPID ID
Module type Port type
assignment
8608GBE and 8608GBM 1000BASE-SX (GBIC) 8608GBE,
modules 8608GBM, 8608G
TE/8608GTM, and
8608SXE modules
1000BASE-LX (GBIC)
1000BASE-ZX (GBIC)
1000BASE-XD (GBIC)
1000BASE-TX (GBIC)
8608GTE and 8608GTM 1000BASE-T 8608GBE,
modules 8608GBM, 8608G
TE/8608GTM, and
8608SXE modules

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
OctaPID ID
Module type Port type
assignment
8608SXE module 1000BASE-SX 8608GBE,
8608GBM, 8608G
TE/8608GTM, and
8608SXE modules
8616SXE module 1000BASE-SX 8616SXE module
8624FXE module 100BASE-FX 8624FXE module
8632TXE and 8632TXM 10BASE-T/100BASE-TX 8632TXE and
modules 8632TXM modules
1000BASE-SX (GBIC)
1000BASE-LX (GBIC)
1000BASE-ZX (GBIC)
1000BASE-XD (GBIC)
1000BASE- TX (GBIC)
8648TXE and 8648TXM 10/100 Mb/s 8648TXE and
modules 8648TXM modules
8672ATME and OC-3c MDA 8672ATME and
8672ATMM modules 8672ATMM
modules
OC-12c MDA
DS3
8681XLR module 10GBASE-LR 8681XLR module
8681XLW module 10GBASE-LW 8681XLW module
8683POSM module OC-3c MDA 8683POSM module
OC-12c MDA
8608GBE, 8608GBM, 8608GTE/8608GTM, and 8608SXE modules

describes the OctaPID ID and port assignments for the 8608GBE, Metro
Ethernet Routing Switch 8608GBM, 8608GTE, 8608GTM, and 8608SXE
modules.
8608GBE, 8608GBM, 8608GTE/8608GTM, and 8608SXE modules

OctaPID ID assignment Port assignment
OctaPID ID: 0 Port 1

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

8616SXE module describes the OctaPID ID and port assignments for the
8616SXE module.
8616SXE module
OctaPID ID: 0 Ports 1 and 2
8624FXE module describes the OctaPID ID and port assignments for the
8624FXE module.
8624FXE module
OctaPID ID: 0 Ports 1 through 8
8632TXE and 8632TXM modules describes the OctaPID ID and port

assignments for the 8632TXE and 8632TXM modules.
8632TXE and 8632TXM modules

- -
- -

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.

OctaPID ID: 6 Port 33 (GBIC port)
OctaPID ID: 7 Port 34 (GBIC port)
8648TXE and 8648TXM modules describes the OctaPID ID and port

assignments for the 8648TXE and 8648TXM modules.
8648TXE and 8648TXM modules

- -
- -
OctaPID ID: 6 Port 33 through 40
OctaPID ID: 7 Port 41 through 48
8672ATME and 8672ATMM modules describes the OctaPID ID and port

assignments for the 8672ATME and 8672ATMM modules.
8672ATME and 8672ATMM modules

OctaPID ID: 0 • Ports 1 through 4 (with OC-3c
MDA)
• Port 1 (with OC-12c MDA)
• Ports 1 through 2 (with DS-3
MDA)
OctaPID ID: 1 • Ports 5 through 8 (with OC-3c
MDA)
• Ports 5 through 6 (with DS-3
MDA)
OctaPID ID: 2 Not used

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
8681XLR module describes the OctaPID ID and port assignments for the
8681XLR module.
8681XLR module
OctaPID ID: 1
OctaPID ID: 2
OctaPID ID: 3
OctaPID ID: 4
OctaPID ID: 5
OctaPID ID: 6
OctaPID ID: 7
8681XLW module describes the OctaPID ID and port assignments for the
8681XLW module.
8681XLW module
OctaPID ID: 1
OctaPID ID: 2
OctaPID ID: 3
OctaPID ID: 4
OctaPID ID: 5
OctaPID ID: 6
OctaPID ID: 7
8683POSM module describes the OctaPID ID and port assignments for the
8683POSM module.
8683POSM module
OctaPID ID: 0 • Ports 1 and 2 (with OC-3c MDA)

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.


Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
304
Index
A port mirroring 143
acronyms 11 Continuity Check Message
address resolution table, displaying 222 CFM message type 16
Address Resolution, see AR 219 crossover cable 34
AR
statistics table 219 D
testing 217 DDI 40, 42, 43
viewing statistics 219 debugging 159
AR Stats tab 219 DHCP 190
ARP table, clearing specified entries 195 diagnostics
automatic trace, configuring using the address resolution table test 218
CLI 205 error trapping 167
port mirroring 135
C DTE/DCE switch
cable changing setting of 34
Category 5 35 dump ar command 222
crossover 34
straight-through 34 E
troubleshooting 34 edit mode commands 270
CCM enabling PBT 80
MA parameters in CLI 96 encapsulation method 80
MEP parameters in CLI 99 error trapping 167
MEP parameters in Device Error Traps tab 167
Manager 80
CFM
configuring using Device
H
Hexidecimal Results Mask
Manager 75
Displaying in CLI 60
configuring using the CLI 93
definition 16
CFM port statistics 88 I
clear commands 194 interface index 273
CLI IP, entries in AR table 221
displaying address resolution
records 222

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Index 305
L mirroring
MAC address 134
LEDs
port 17
power supplies 32
mirroring mode, setting 145
problem indications 31
mirroring-port command 145
Linktrace Message
monitor commands 191, 192
CFM message type 16
Multi-Link Trunk interface index 274
linktrace messages 110
multicast AR table 221
log files 169
mux mode 80
login prompt, failure to display 34
Loopback Message
CFM message type 16
N
loopback messages 107 network management
port mirroring 17
M NMM (network management MIB) 224
MAC
entries in AR table 221
P
mirroring addresses 134 PBT, enabling 80
monitoring MAC table 134 physical MAC address 275
MAC address assignment 274 ping probe history
maintenance association viewing of 211
configuring with CLI 95 ping result 215
configuring with Device Manager 76 ping snoop
maintenance domain configuring on R modules
configuring with CLI 94 using Device Manager 266
maintenance endpoint using the CLI 265
configuring with CLI 98 overview of 209
configuring with Device Manager 77 ping test
creating 78 running of
statistics 80, 102, 105 using Device Manager 211
maintenance intermediate endpoint port mirroring 135
creating 85 assigning destination ports 147
statistics 87 configuration on R modules
maintenance intermediate point using the CLI 253
configuring with CLI 111 configuration on R-module
maintenance intermediate point using Device Manager 255
statistics 112 description 17
Manufacturing information displaying entries 141
viewing Metro Ethernet Routing editing existing values 141
Switch 8600 using the CLI 40 editing ports 141
viewing Metro Ethernet Routing egress 17
Switch using DM 36 ingress 17
messages MAC addresses 18
loopback test warning 217 OctaPID ID and port
MIBs assignments 298
checking status 224 OctaPID ID assignment 146
mirrored-port command 145 sorting entries 141

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
306 Index
source port members 147 UNIX messages 20

port mirroring commands 143 syslog commands, show 187
port numbering 273 Syslog severity levels 176
ports syslogd daemon 174
interface index 274 system log 32
monitoring how often down 188 enabling 174
numbering 272 receiving messages 174
System Log Table tab 174,
R
rapid ping 227 T
access port to customer port 235 table, flushing 194
description of 226 TD Continuity
ping responses 229 Configuring a test 48
Rapid ping, testing traffic with 230 Configuring a test using the CLI 62
remote maintenance endpoint Configuring a test with DM 48
configuring with CLI 104 Displaying test in DM 52
creating 82 Running a current test in DM 52
statistics 83 Running a current test using the
remote mirroring CLI 57
configuration of TD continuity test example using the
using Device Manager 153 CLI 73
using the CLI 155 TD continuity
configuration on legacy module Displaying test history using the
using the CLI 262 CLI 58
RMON 190 TDC 16, 47
RSVP, entries in AR table 222 TDI
configuring with Device Manager 80
S Telnet sessions
severity codes 175 ending 194
severity levels Temperature
mapping 176 viewing Metro Ethernet Routing
MERS 8600 176, 176 Switch 8600 using the CLI 42
syslog 176 viewing Metro Ethernet Routing
system log 176, 176 Switch using DM 36
show log commands terminal characters, special 269
level 173 Test tab
show sys commands Topology Table tab 225
syslog general-info 187 trace route
slot numbering 273 probe history 203
software incompatibility 32 result 201
statistics trace route test
CFM port 88 running of
STG 191 using Device Manager 199
straight-through cable 34 traceroute command 204
syslog 180, 187 trap error messages 275
syslogd daemon 20 troubleshooting 204

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Index 307
cables 34 U
Connectivity Fault Management 75
UNIX Syslog facility 180
error trapping 167
UNIX, managing messages 174
failure to get login prompt 34
IS-IS 159
LED indications 31 V
MAC address counting 134 virtual MAC address 275
MAC address mirroring 134 VLAN
module failure 33 entries in AR table 221
performance monitoring 113 VLAN (0) 162
port connections problems 34 VLAN interface index 274
port mirroring 135 Voltages
Transparent Domain Continuity 47 viewing Metro Ethernet Routing
Troubleshooting tools Switch 8600 using the CLI 43
TD Continuity viewing Metro Ethernet Routing
overview 16 Switch using DM 36

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
308 Index

Troubleshooting
NN46220-701 01.01 Standard
4.2 3 August 2007
.
Troubleshooting
Copyright © 2007 , Nortel Networks
All Rights Reserved.
Publication: NN46220-701
Document status: Standard
Document version: 01.01
Document date: 3 August 2007
To provide feedback or report a problem in this document, go to www.nortel.com/documentfeedback.
Sourced in Canada and the United States of America
This document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual
property rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel
Networks, the holder is granted no rights to use the information contained herein and this document shall not be published, copied,
produced or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or media.
The information in this document is subject to change without notice. The statements, configurations, technical data, and
recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty.
Users must take full responsibility for their applications of any products specified in this document. The information in this document
is proprietary to Nortel Networks Inc.
The software described in this document is furnished under a license agreement and may be used only in accordance with the
terms of that license. The software license agreement is included in this document.
Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
All other trademarks are the property of their respective owners.

NN46220-701 - 01.01 - TRBL - CFM Y1731

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NN46220-701 - 01.01 - TRBL - CFM Y1731

Uploaded by

Copyright:

Available Formats

Nortel Metro Ethernet Routing Switch 8600

NN46220-701 (323745-A Rev 01)

Copyright © 2007, Nortel Networks

Sourced in Canada and the United States of America

Restricted rights legend

Nortel Networks Inc. software license agreement

Nortel Metro Ethernet Routing Switch 8600

Changes to your system or network 29

Troubleshooting using a network manager 163

Downloading software 165

Troubleshooting tools 167

Nortel Metro Ethernet Routing Switch 8600

Displaying level information 173

Understanding alarms, logs, traps, and system messages 245

Nortel Metro Ethernet Routing Switch 8600

Troubleshooting configuration examples 253

Diagnostics reference 269

Nortel Metro Ethernet Routing Switch 8600

New in this release

Nortel Metro Ethernet Routing Switch 8600

• Nortel Metro Ethernet Routing Switch 8600 Configuration — Provider

Nortel Metro Ethernet Routing Switch 8600

ACL Access Control List

Nortel Metro Ethernet Routing Switch 8600

CCM Continuity Check Message

Nortel Metro Ethernet Routing Switch 8600

MLT MultiLink Trunking

Nortel Metro Ethernet Routing Switch 8600

Nortel Metro Ethernet Routing Switch 8600

In addition, the MERS 8600 supports a wide range of diagnostic tools

When connectivity problems occur and the source of the problem is

The following provides a summary of the different troubleshooting tools

Nortel Metro Ethernet Routing Switch 8600

• "Port mirroring" (page 17)

Transparent Domain Continuity

Connectivity Fault Management

Provider Backbone Transport (PBT) sends CCM packets to endpoints within

Loopback messages test the connection between maintenance points (MP).

Nortel Metro Ethernet Routing Switch 8600

Linktrace messages isolate faults by tracing the hop-by-hop path to the

Y.1731 Performance Monitoring

You can use PM to measure the following point-to-point connection metrics:

Digital Diagnostic Monitoring

An interface that supports DDM is called a Digital Diagnostic Interface (DDI).

Nortel Metro Ethernet Routing Switch 8600

packet ingressing or egressing a specified port is forwarded normally, and

The remote mirroring feature uses a specific VLAN if remote mirroring is

"Remote mirroring" (page 19) shows remote mirroring operations in a

Nortel Metro Ethernet Routing Switch 8600

Packet capture tool

Nortel Metro Ethernet Routing Switch 8600

System log (syslog)

The UNIX daemon syslogd is a software component that receives and

General diagnostic tools

Nortel Metro Ethernet Routing Switch 8600

Proper installation and routine maintenance

Nortel Metro Ethernet Routing Switch 8600

Site network map

Device configuration information

Other important data about your network

Normal behavior on your network

Nortel Metro Ethernet Routing Switch 8600