Catalyst 6500 Series Software Configuration Guide, 8.7 - Checking Status and Connectivity [Cisco Catalyst 6500 Series Switches]

Table Of Contents

Checking Status and Connectivity

Checking the Module Status

Checking the Port Status

Displaying the Port MAC Address

Displaying the Duplicate MAC Entries in the CAM Table

Displaying Port Capabilities

Configuring the MAC Utilization Load Interval

Understanding How the MAC Utilization Load Interval Works

Setting the MAC Utilization Load Interval

Displaying MAC Utilization Statistics

Clearing MAC Utilization Counters

Checking the 10-Gigabit Ethernet Link Status

Checking the Cable Status Using TDR

Using Telnet

Using Secure Shell Encryption for Telnet Sessions

Monitoring User Sessions

Using Ping

Understanding How Ping Works

Executing Ping

Using Layer 2 Traceroute

Layer 2 Traceroute Usage Guidelines

Identifying a Layer 2 Path

Using IP Traceroute

Understanding How IP Traceroute Works

Executing IP Traceroute

Using System Warnings on Port Counters

Executing System Warnings on Port Counters

Backplane Traffic

Low Remaining Memory

Detected Memory Corruption

NVRAM Logs

Inband Errors

UDP Errors

Executing Hardware Level Warnings on Port Counters

Executing Spanning-Tree Warnings on Port Counters

Blocking to Listening Transitions

BPDU Skewing

SNMP

Configuring Packet-Buffer Error Handling

Configuring EtherChannel/Link Error Handling

Configuring IEEE 802.3ah Ethernet OAM

Understanding How OAM Works

Ethernet OAM Configuration Guidelines and Restrictions

Executing Ethernet OAM

Enabling or Disabling Ethernet OAM

Specifying the Ethernet OAM Port Mode

Denying or Permitting Ethernet OAM Remote Loopback Tests

Enabling or Disabling the Ethernet OAM Remote Loopback Test

Specifying the Number of Packets and the Packet Size for the Ethernet OAM Remote Loopback Test and Running the Test

Enabling or Disabling Ethernet OAM Link Monitoring

Specifying the Window Size for Link Events for Ethernet OAM Link Monitoring

Specifying the Low-Threshold Error Count and the Associated Action for Ethernet OAM Link Monitoring

Specifying the High-Threshold Error Count and the Associated Action for Ethernet OAM Link Monitoring

Specifying the Associated Action for OAM Critical Link Events

Clearing Ethernet OAM Statistics and the Ethernet OAM Configuration

Clearing User-Configured Parameters for OAM Link Monitoring

Clearing User-Configured Actions for OAM Critical Link Events

Displaying Ethernet OAM-Related Information

Displaying Ethernet OAM Neighbor Information

Displaying Ethernet OAM Remote Loopback Test Information

Displaying Ethernet OAM Statistics

Configuring Metro Ethernet Connectivity Fault Management

Understanding How Metro Ethernet Connectivity Fault Management Works

Connectivity Fault Management Protocols

Maintenance Domains

Maintenance Associations

Maintenance Points

CFM Configuration Guidelines and Restrictions

Scalability Data for Connectivity Fault Management and Alarm Indication Signal

Configuring Metro Ethernet CFM

Enabling or Disabling Metro Ethernet CFM

Configuring Metro Ethernet CFM Domains

Configuring a Metro Ethernet CFM Maintenance Association

Configuring CFM on a Port as a Maintenance Point

Configuring Continuity-Check Protocol Parameters

Configuring Ethernet CFM traceroute Protocol Parameters

Configuring a System CAM Entry

Displaying Metro Ethernet CFM Domains

Displaying CFM Maintenance Association Information

Displaying Metro Ethernet CFM Maintenance Point Information

Displaying the Metro Ethernet CFM Status

Displaying Metro Ethernet CFM Statistics

Displaying Metro Ethernet CFM Errors

Displaying the Metro Ethernet CFM traceroute Database

Clearing a Metro Ethernet CFM

Clearing a Metro Ethernet CFM Maintenance Association

Clearing a Metro Ethernet CFM Maintenance Point

Clearing the MAC Configuration for Maintenance End Points

Clearing the Ethernet CFM traceroute Database

Configuring the Alarm Indication Signal

Understanding How CFM Works with 802.3ah Link-OAM for AIS-RDI

Ethernet Alarm Indication Signal

Timer Spread Design Logic and Guidelines:

Ethernet Remote Defect Indication

ASI and RDI Configuration Guidelines and Restrictions

Configuring an Alarm Indication Signal

Enabling or Disabling a Metro Ethernet CFM Alarm Indication Signal

Configuring Continuity-Check Protocol AIS Parameters

Configuring the Metro Ethernet CFM Alarm Indication Signal Transmission Level

Configuring the Metro Ethernet CFM Alarm Indication Signal PDUs Transmission Count

Configuring a CFM AIS on an Individual Port

Displaying CFM AIS/RDI Errors

Configuring the Ethernet Local Management Interface

Understanding How ELMI Works

Ethernet Local Management Protocols

Configuring ELMI

Configuring ELMI on the Switch

Enabling or Disabling ELMI

Enabling or Disabling an EVC

Configuring ELMI on an Individual Port

Configuring a UNI ID on an Individual Port

Configuring UNI-TYPE on an Individual Port

Configuring an EVC on an Individual Port

Displaying an EVC

Displaying CE-VLAN/ EVC

Displaying ELMI Statistics and Configuration

Clearing an EVC

Clearing an EVC on an Individual Port Associated to a UNI

Clearing ELMI Statistics Counters

Clearing a UNI Configuration

Configuring MAC Address Move Counters

Understanding How MAC Address Move Counters Work

MAC Address Move Counter Configuration Guidelines and Restrictions

MAC Address Move Counter syslog Generation

Detecting MAC Address Moves

Exceeding the Maximum Limit for MAC Address Move Counters for a VLAN

Executing MAC Address Move Counters

Enabling or Disabling MAC Address Move Counters

Displaying MAC Address Move Counter Statistics

Clearing MAC Address Move Counter Statistics

Digital Optical Monitoring

Displaying Transceiver Information

Displaying General Port Transceiver Information

Displaying Detailed Transceiver Information

Displaying Transceiver Threshold Violations

Displaying Port Transceiver Information

Displaying Port Transceiver Configuration Information

Setting Transceiver Monitoring and Thresholds

Enabling or Disabling Transceiver Monitoring

Setting the Transceiver Monitoring Interval

Setting the Transceiver Temperature Threshold

Checking Status and Connectivity

This chapter describes how to check the status and connectivity on the Catalyst 6500 series switches.

Note For complete syntax and usage information for the commands that are used in this chapter, refer to the Catalyst 6500 Series Switch Command Reference publication.

This chapter consists of these sections:

•Checking the Module Status

•Checking the Port Status

•Displaying the Port MAC Address

•Displaying the Duplicate MAC Entries in the CAM Table

•Displaying Port Capabilities

•Configuring the MAC Utilization Load Interval

•Checking the 10-Gigabit Ethernet Link Status

•Checking the Cable Status Using TDR

•Using Telnet

•Using Secure Shell Encryption for Telnet Sessions

•Monitoring User Sessions

•Using Ping

•Using Layer 2 Traceroute

•Using IP Traceroute

•Using System Warnings on Port Counters

•Configuring Packet-Buffer Error Handling

•Configuring EtherChannel/Link Error Handling

•Configuring IEEE 802.3ah Ethernet OAM

•Configuring Metro Ethernet Connectivity Fault Management

•Configuring the Alarm Indication Signal

•Configuring the Ethernet Local Management Interface

•Configuring MAC Address Move Counters

Checking the Module Status

Catalyst 6500 series switches are multimodule systems. You can see what modules are installed and the MAC address ranges and version numbers for each module using the show module [mod] command. Specify a particular module number to see detailed information on that module.

To check the module status, perform this task in normal mode:

Task

Command

Check the module status.

show module [mod]

This example shows how to check the module status. The output shows that there is one supervisor engine and four additional modules that are installed in the chassis.
Console> (enable) show module
Mod Slot Ports Module-Type               Model               Status
--- ---- ----- ------------------------- ------------------- --------
1   1    2     1000BaseX Supervisor      WS-X6K-SUP1-2GE     ok
2   2    24    100BaseFX MM Ethernet     WS-X6224-100FX-MT   ok
3   3    8     1000BaseX Ethernet        WS-X6408-GBIC       ok
4   4    48    10/100BaseTX (Telco)      WS-X6248-TEL        ok
5   5    48    10/100BaseTX (RJ-45)      WS-X6248-RJ-45      ok
Mod Module-Name         Serial-Num
--- ------------------- -----------
1                       SAD03040546
2                       SAD03110020
3                       SAD03070194
4                       SAD03140787
5                       SAD03181291
Mod MAC-Address(es)                        Hw     Fw         Sw
--- -------------------------------------- ------ ---------- -----------------
1   00-50-f0-a8-26-b2 to 00-50-f0-a8-26-b3 1.4    5.1(1)     5.2(1)CSX
    00-50-f0-a8-26-b0 to 00-50-f0-a8-26-b1
    00-50-3e-8d-64-00 to 00-50-3e-8d-67-ff
2   00-50-54-6c-e9-a8 to 00-50-54-6c-e9-bf 1.3    4.2(0.24)V 5.2(1)CSX
3   00-50-54-6c-93-6c to 00-50-54-6c-93-73 1.4    4.2(0.24)V 5.2(1)CSX
4   00-50-54-bf-59-64 to 00-50-54-bf-59-93 0.103  4.2(0.24)V 5.2(1)CSX
5   00-50-f0-ac-30-54 to 00-50-f0-ac-30-83 1.0    4.2(0.24)V 5.2(1)CSX
Mod Sub-Type                Sub-Model           Sub-Serial  Sub-Hw
--- ----------------------- ------------------- ----------- ------
1   L2 Switching Engine I   WS-F6020            SAD03040312 1.0 
Console> (enable)
This example shows how to check the module status on a specific module:
Console> (enable) show module 4
Mod Slot Ports Module-Type               Model               Status
--- ---- ----- ------------------------- ------------------- --------
4   4    48    10/100BaseTX (Telco)      WS-X6248-TEL        ok
Mod Module-Name         Serial-Num
--- ------------------- -----------
4                       SAD03140787
Mod MAC-Address(es)                        Hw     Fw         Sw
--- -------------------------------------- ------ ---------- -----------------
4   00-50-54-bf-59-64 to 00-50-54-bf-59-93 0.103  4.2(0.24)V 5.2(1)CSX
Console> (enable)
Checking the Port Status

You can see summary or detailed information on the switch ports using the show port [mod[/port]] command. To see summary information on all of the ports on the switch, enter the show port command with no arguments. Specify a particular module number to see information on the ports on that module only. Enter both the module number and the port number to see detailed information about the specified port.

To apply configuration commands to a particular port, you must specify the appropriate logical module. For more information, see the "Checking the Module Status" section.

To check the port status, perform this task in normal mode:

Task

Command

Check the port status.

show port [mod[/port]]

This example shows how to see information on the ports on a specific module only:
Console> (enable) show port 1
Port  Name               Status     Vlan       Duplex Speed Type
----- ------------------ ---------- ---------- ------ ----- ------------
 1/1                     connected  1            full  1000 1000BaseSX
 1/2                     notconnect 1            full  1000 1000BaseSX
Port  Security Secure-Src-Addr   Last-Src-Addr     Shutdown Trap     IfIndex
----- -------- ----------------- ----------------- -------- -------- -------
 1/1  disabled                                     No       disabled 3
 1/2  disabled                                     No       disabled 4
Port     Broadcast-Limit Broadcast-Drop
-------- --------------- --------------------
 1/1                   -                    0
 1/2                   -                    0
Port   Send FlowControl    Receive FlowControl   RxPause    TxPause
       admin    oper       admin    oper
-----  -------- --------   -------- --------     ---------- ----------
 1/1   desired  off        off      off          0          0
 1/2   desired  off        off      off          0          0
Port  Status     Channel   Admin Ch    Neighbor                         Neighbor
                 Mode      Group Id    Device                              Port
----- ---------- --------- ----- ----- ----------------------------------- -----
 1/1  connected  auto      65    0
 1/2  notconnect auto      65    0
Port  Align-Err  FCS-Err    Xmit-Err   Rcv-Err    UnderSize
----- ---------- ---------- ---------- ---------- ---------
 1/1           0          0          0          0         0
 1/2           0          0          0          0         0
Port  Single-Col Multi-Coll Late-Coll  Excess-Col Carri-Sen Runts     Giants
----- ---------- ---------- ---------- ---------- --------- --------- ---------
 1/1           0          0          0          0         0         0         0
 1/2           0          0          0          0         0         0         0
Last-Time-Cleared
--------------------------
Tue Jun 8 1999, 10:01:35 
Console> (enable)
This example shows how to see information on an individual port:
Console> (enable) show port 1/1
Port  Name               Status     Vlan       Duplex Speed Type
----- ------------------ ---------- ---------- ------ ----- ------------
 1/1                     connected  1            full  1000 1000BaseSX
Port  Security Secure-Src-Addr   Last-Src-Addr     Shutdown Trap     IfIndex
----- -------- ----------------- ----------------- -------- -------- -------
 1/1  disabled                                     No       disabled 3
Port     Broadcast-Limit Broadcast-Drop
-------- --------------- --------------------
 1/1                   -                    0
Port   Send FlowControl    Receive FlowControl   RxPause    TxPause
       admin    oper       admin    oper
-----  -------- --------   -------- --------     ---------- ----------
 1/1   desired  off        off      off          0          0
Port  Status     Channel   Admin Ch    Neighbor                         Neighbor
                 Mode      Group Id    Device                              Port
----- ---------- --------- ----- ----- ----------------------------------- -----
 1/1  connected  auto      65    0
Port  Align-Err  FCS-Err    Xmit-Err   Rcv-Err    UnderSize
----- ---------- ---------- ---------- ---------- ---------
 1/1           0          0          0          0         0
Port  Single-Col Multi-Coll Late-Coll  Excess-Col Carri-Sen Runts     Giants
----- ---------- ---------- ---------- ---------- --------- --------- ---------
 1/1           0          0          0          0         0         0         0
Last-Time-Cleared
--------------------------
Tue Jun 8 1999, 10:01:35 
Console> (enable)
Displaying the Port MAC Address

In addition to displaying the MAC address range for a module using the show module command, you can display the MAC address of a specific port in the switch using the show port mac-address [mod[/port]] command.

To display the MAC address of a specific port, perform this task in normal mode:

Task

Command

Display the MAC address of a specific port.

show port mac-address [mod[/port]]

This example shows how to display the MAC address of a specific port:
Console> show port mac-address 4/1
Port  Mac address
----- ----------------------
 4/1  00-50-54-bf-59-64
This example shows how to display the MAC addresses of all ports on a module:
Console> show port mac-address 4
Port  Mac address
----- ----------------------
 4/1  00-50-54-bf-59-64
 4/2  00-50-54-bf-59-65
 4/3  00-50-54-bf-59-66
 4/4  00-50-54-bf-59-67
 4/47 00-50-54-bf-59-92
 4/48 00-50-54-bf-59-93
Displaying the Duplicate MAC Entries in the CAM Table

You can track multiple E-LAN VLANs and VLAN loops using the MAC duplication indicator (&) displayed next to the MAC entries that appear more than once in the CAM table.

To display the duplicate MAC entries in the CAM table, perform these tasks in enabled mode:

Task

Command

Display all duplicate MAC addresses in the CAM table.

show cam duplicate

Display only the dynamic MAC addresses with the duplicate indicator (&)

show cam dynamic [mod[/port]]

The show cam static | permanent commands also display MAC entries with the duplicate indicator (&).

This example shows how to display all duplicate MAC entries in the CAM table:
Console> (enable) show cam duplicate 
* = Static Entry. + = Permanent Entry. # = System Entry. R = Router Entry. X = Port 
Security Entry $ = Dot1x Security Entry M = Mac-Auth-Bypass Entry & = Duplicate MAC entry
                                                  Destination Ports or
   VLAN  Dest MAC/Route Des    [CoS]     Age      VCs / [Protocol Type]
   ----  ------------------    -----  ----------  ---------------------
42    00-d0-02-83-eb-89  &                     3/3
   142    00-d0-02-83-eb-89  &                     5/3
    42    d8-d9-02-83-ef-ff  &                     2/3
     3    d8-d9-02-83-ef-ff  &                     3/4
Total Matching CAM Entries Displayed = 2
========================================================================
Note If the show cam duplicate command delays the printing of duplicate entries, some of the entries might age out before the print operation is complete.

This example shows how to display only the dynamic MAC addresses with the duplicate indicator (&):
Console> (enable) show cam dynamic 
* = Static Entry. + = Permanent Entry. # = System Entry. R = Router Entry. X = Port 
Security Entry $ = Dot1x Security Entry M = Mac-Auth-Bypass Entry & = Duplicate MAC entry
                                               Destination Ports or
   VLAN  Dest MAC/Route Des    [CoS]     Age      VCs / [Protocol Type]
   ----  ------------------    -----  ----------  ---------------------
   142   00-d0-02-94-4f-ff                        5/4
   42    00-d0-02-83-eb-fc                        2/1
   142   00-d0-02-83-eb-ff  &                     5/3
   Total Matching CAM Entries Displayed = 3
========================================================================= 
Displaying Port Capabilities

You can display the capabilities of any port in a switch using the show port capabilities [[mod][/port]] command.

To display the capabilities of a specific port, perform this task in normal mode:

Task

Command

Display the capabilities of a specific port.

show port capabilities [mod[/port]]

This example shows how to display the port capabilities for switch ports:
Console> (enable) show port capabilities 1/1
Model                    WS-X6K-SUP1A-2GE
Port                     1/1
Type                     No Connector
Speed                    1000
Duplex                   full
Trunk encap type         802.1Q,ISL
Trunk mode               on,off,desirable,auto,nonegotiate
Channel                  yes
Broadcast suppression    percentage(0-100)
Flow control             receive-(off,on,desired),send-(off,on,desired)
Security                 yes
Membership               static,dynamic
Fast start               yes
QOS scheduling           rx-(1p1q4t),tx-(1p2q2t)
CoS rewrite              yes
ToS rewrite              DSCP
UDLD                     yes
Inline power             no
AuxiliaryVlan            no
SPAN                     source,destination
COPS port group          1/1-2 
Console> (enable)
Configuring the MAC Utilization Load Interval

These sections describe how to configure the MAC utilization load interval:

•Understanding How the MAC Utilization Load Interval Works

•Setting the MAC Utilization Load Interval

•Displaying MAC Utilization Statistics

•Clearing MAC Utilization Counters

Understanding How the MAC Utilization Load Interval Works

The show mac utilization command displays the packet rate, bit rate, and octet rate per port, per module, and per VLAN, based on the load interval. You can set the load interval to either 30 or 300 seconds. You can also clear the MAC utilization counters on a port, range of ports, or for all ports in a module.

Setting the MAC Utilization Load Interval

You can set the MAC utilization load interval to 30 or 300 seconds. The default is 300 seconds.

To set the MAC utilization load interval, perform this task in enabled mode:

Task

Command

Set the MAC utilization load interval.

set mac utilization load-interval seconds

This example shows how to set the MAC utilization load interval to 30 seconds:
Console> (enable) set mac utilization load-interval 30 
Load interval set to 30 seconds.
Displaying MAC Utilization Statistics

To display MAC utilization statistics, perform this task in enabled mode:

Task

Command

Display the MAC utilization statistics.

show mac utilization [vlan number]|[mod[/port]

This example shows how to display the MAC utilization statistics globally:
Console> (enable) show mac utilization 
30 seconds input/output port rates:
Port  Xmit-Packet-Rate     Xmit-Octet-Rate      Xmit-Bit-Rate
----- -------------------- -------------------- --------------------
 2/1                555351             71088003            568704024 
 2/2                555351             71088110            568704880 
 2/3                555350             71088002            568704016 
 2/14               555351             71088050            568704400 
 2/15               555350             71088001            568704008 
 2/16               555351             71088042            568704336 
 3/1                     0                   12                   96 
 3/2                     0                    0                    0 
 3/3                     0                    0                    0 
 3/43                    0                    7                   56 
 3/44                    0                    4                   32 
 3/45                    0                   46                  368 
 3/46                    0                   46                  368 
 3/47                    0                   40                  320 
 3/48                    0                   40                  320 
 4/1                     0                    0                    0 
 4/2                     0                   18                  144 
 4/3                     0                   18                  144 
 4/4                     0                   18                  144 
12/1                   369                23658               189264 
12/2                     0                   12                   96 
12/3                614539            921816483           7374531864 
12/4                     0                    0                    0 
13/1                 33960             50941147            407529176 
13/2                 33960             50941151            407529208 
13/3                 33960             50941190            407529520 
Port  Rcv-Packet-Rate      Rcv-Octet-Rate       Rcv-Bit-Rate
----- -------------------- -------------------- --------------------
 2/1                845671            108247607            865980856 
 2/2                555384             71090299            568722392 
 2/3                555384             71090397            568723176 
 2/4                555384             71090295            568722360 
 2/5                555384             71090401            568723208 
 2/6                555384             71090296            568722368 
 2/16               845671            108247597            865980776 
 3/1                     1                  129                 1032 
 3/2                     0                    0                    0 
 3/3                     0                    0                    0 
 3/4                     0                    0                    0 
 3/29                    0                   73                  584 
 3/43                    0                   73                  584 
 3/44                    0                   73                  584 
 3/45                    0                   14                  112 
 3/46                    0                    9                   72 
 3/47                    0                   12                   96 
 3/48                    0                   12                   96 
 4/1                     0                    0                    0 
 4/2                     0                   18                  144 
 4/3                     0                   18                  144 
 4/25                    0                   18                  144 
 4/26                    0                   18                  144 
 4/27                    0                   18                  144 
 4/28                    0                   18                  144 
 4/29                    0                   18                  144 
 8/1                     0                    0                    0 
 8/2                     0                    0                    0 
12/1                614201            921296589           7370372712 
12/2                614198            921301441           7370411528 
12/3                     0                   12                   96 
12/4                     0                    0                    0 
13/1                 82362            123544992            988359936 
13/21                33960             50941535            407532280 
13/22                33960             50940833            407526664 
13/23                33960             50941552            407532416 
Console> (enable)
This example shows how to display the MAC utilization statistics for a VLAN:
Console> (enable) show mac utilization vlan 100
300 seconds input/output port rates:
Port  Xmit-Packet-Rate     Xmit-Octet-Rate      Xmit-Bit-Rate
----- -------------------- -------------------- --------------------
13/1                 33925             50886135            407089080 
13/26                33924             50885801            407086408 
Port  Rcv-Packet-Rate      Rcv-Octet-Rate       Rcv-Bit-Rate
----- -------------------- -------------------- --------------------
13/1                 82278            123414184            987313472 
13/26                33927             50887092            407096736 
Console> (enable)
This example shows how to display MAC utilization statistics for a module:
Console> (enable) show mac utilization 12
30 seconds input/output port rates:
Port  Xmit-Packet-Rate     Xmit-Octet-Rate      Xmit-Bit-Rate
----- -------------------- -------------------- --------------------
12/1                396702            594010991           4752087928 
12/2                395978            593964837           4751718696 
12/3                412889            619338738           4954709904 
12/4                396693            418773370           3350186960 
Port  Rcv-Packet-Rate      Rcv-Octet-Rate       Rcv-Bit-Rate
----- -------------------- -------------------- --------------------
12/1                412891            619344814           4954758512 
12/2                412891            619340051           4954720408 
12/3                395978            593964450           4751715600 
12/4                405223            425521134           3404169072 
Console> (enable)
This example shows how to display MAC utilization statistics for a port:
Console> (enable) show mac utilization 12/1
30 seconds input/output port rates:
Port  Xmit-Packet-Rate     Xmit-Octet-Rate      Xmit-Bit-Rate
----- -------------------- -------------------- --------------------
12/1                405825            607683712           4861469696 
Port  Rcv-Packet-Rate      Rcv-Octet-Rate       Rcv-Bit-Rate
----- -------------------- -------------------- --------------------
12/1                408276            612401845           4899214760 
Console> (enable) 
Clearing MAC Utilization Counters

To clear the MAC utilization counters, perform this task in enabled mode:

Task

Command

Clear the MAC utilization counters.

clear mac utilization [mod/port]¹

¹There is no option for this command.

This example shows how to clear the MAC utilization counters for a port:
Console> (enable) clear mac utilization 1/1 
Mac utilization counters are cleared for the port 1/1. 
This example shows how to clear the MAC utilization counters for a module:
Console> (enable) clear mac utilization 1 
Module  1 mac utilization counters are cleared. 
This example shows how to clear the MAC utilization counters globally:
Console> (enable) clear mac utilization 
Mac utilization counters are cleared.
Checking the 10-Gigabit Ethernet Link Status

Cable diagnostics allow you to activate the pseudorandom binary sequence (PRBS) test on the 10-Gigabit Ethernet links.

Note The PRBS test is currently available on the 1-port 10GBASE-E serial 10-Gigabit Ethernet module (WS-X6502-10GE).

To run the PRBS test between two devices, you must start it on both ends of the cable. If the cable is looped back, a single end can generate the test sequence (on the Tx), verify the test sequence, and count the errors (at the Rx).

Before the PRBS test starts, the port is automatically put in the errdisable state. The errdisable timeout is disabled for the port so that the port is not automatically reenabled after the timeout interval ends. The errdisable timeout is automatically reenabled on the port after the PRBS test finishes.

When the PRBS test is running, the system does not allow you to enter the set port enable and set port disable commands.

The PRBS error counter measures the reliability of the cable. The error counter range is from 0-255. A value of 0 signifies a perfect link connection; a value of 255 signifies that the port is faulty, not connected, or that there is no communication through the link. If the counter does not remain at 0 for a predetermined length of time, the link is faulty. For example, for a baud error rate (BER) of 10^-12, the counter should remain at 0 for 100 seconds.

Each time that you access the PRBS counter by entering the show port prbs command, the PRBS error counter value is reset to 0, and the counter begins to accumulate errors again.

Note The PRBS counter is a "read and clear" register. The first reading in a sequence is usually unreliable and serves primarily to purge the counter; successive readings are accurate.

To start or stop the PRBS test, perform this task in privileged mode:

Task

Command

Step 1

Start or stop the PRBS test.

test cable-diagnostics prbs {start | stop} mod/port

Step 2

Display the PRBS test counter information.

show port prbs

This example shows how to start the PRBS test on port 1 on module 5:
Console> (enable) test cable-diagnostics prbs start 5/1 
PRBS cable-diagnostic test started on port 5/1. 
Console> (enable)
This example shows how to stop the PRBS test on port 1 on module 5:
Console> (enable) test cable-diagnostics prbs stop 5/1 
PRBS cable-diagnostic test stopped on port 5/1. 
Console> (enable)
This example shows the message that displays when the PRBS test is not supported on a module:
Console> (enable) test cable-diagnostics prbs start 6/1 
Feature not supported on module 6. 
Console> (enable) 
This example shows how to display the PRBS counter values and the ports that are running the PRBS test:
Console> (enable) show port prbs 
Port PRBS state Error Counters 
6/1 start 30 
7/1 stop - 
Console> (enable)

Checking the Cable Status Using TDR

You can check the status of the copper cables by using the time domain reflectometer (TDR). TDR is supported on the following modules: WS-X6148-GE-TX, WS-X6148V-GE-TX, WS-X6548-GE-TX, WS-X6548V-GE-TX, WS-X6548-GE-45AF, WS-X6748-GE-TX, WS-X6148A-GE-TX, WS-X6148-GE-45AF, WS-X6148A-GE-45AF, WS-X6148A-RJ-45, and WS-X6148A-45AF. The TDR detects a cable fault by sending a signal through the cable and reading the signal that is reflected back to it. All or part of the signal can be reflected back by any number of cable defects or by the end of the cable itself.

Note TDR can test cables up to a maximum length of 115 meters.

Use TDR to determine if the cabling is at fault if you cannot establish a link. This test is especially important when replacing an existing switch, upgrading to Gigabit Ethernet, or installing new cable plants.

To start or stop the TDR test, perform this task in privileged mode:

Task

Command

Step 1

Start or stop the TDR test.

test cable-diagnostics tdr {start | stop} mod/port

Step 2

Display the TDR test counter information.

show port tdr

This example shows how to start the TDR test on port 1 on module 2:
Console> (enable) test cable-diagnostics tdr start 2/1 
TDR test started on port 2/1. Use show port tdr <m/p> to see the results
Console> (enable) 
This example shows how to stop the TDR test on port 1 on module 2:
Console> (enable) test cable-diagnostics tdr stop 2/1 
tdr cable-diagnostic test stopped on port 2/1. 
Console> (enable) 
This example shows the message that displays when the TDR test is not supported on a module:
Console> (enable) test cable-diagnostics tdr start 2/1 
Feature not supported on module 2. 
Console> (enable) 
This example shows how to display the TDR test results for a port:
Console> (enable) show port tdr 2/1
TDR test last run on Mon, March 10 2003 at 1:35:00 pm
Port  Speed  Local pair  Pair length         Remote pair  Pair status
----- ------ ----------- ------------------- ------------ ------------
2/1   1000   Pair A      12  +/- 3 meters    Pair A       Terminated
             Pair B      12  +/- 3 meters    Pair B       Terminated
             Pair C      12  +/- 3 meters    Pair C       Terminated
Pair D 12 +/- 3 meters Pair D Terminated

Using Telnet

You can access the switch command-line interface (CLI) using Telnet. In addition, you can use Telnet from the switch to access the other devices in the network. Up to eight simultaneous Telnet sessions are possible.

To Telnet to another device on the network from the switch, perform this task in privileged mode:

Task

Command

Open a Telnet session with a remote host.

telnet host [port]

This example shows how to Telnet from the switch to a remote host:
Console> (enable) telnet labsparc
Trying 172.16.10.3...
Connected to labsparc.
Escape character is '^]'.
UNIX(r) System V Release 4.0 (labsparc)
login:
Using Secure Shell Encryption for Telnet Sessions

Note To use Secure Shell encryption commands, you must be running an encryption image. See Chapter 27, "Working with System Software Images" for the software image naming conventions that are used for the encryption images.

Note The Secure Shell encryption feature includes cryptographic software written by Eric Young (eay@cryptsoft.com).

Secure Shell encryption provides security for Telnet sessions and other remote connections to the switch. Secure Shell encryption is supported for remote logins to the switch only. Telnet sessions that are initiated from the switch cannot be encrypted. To use this feature, you must install the application on the client accessing the switch, and you must configure Secure Shell encryption on the switch.

The current implementation of Secure Shell encryption supports SSH version 1 and version 2. SSH version 1 supports DES and 3DES encryption methods, and SSH version 2 supports the 3DES and AES encryption methods. Secure shell encryption can be used with RADIUS and TACACS+ authentication. To configure authentication with Secure Shell encryption, enter the telnet keyword in the set authentication commands.

Note If you are using Kerberos to authenticate connections to the switch, you will not be able to use Secure Shell encryption.

Note Catalyst 6500 series software release 8.7(1) supports SSH keyboard interactive authentication methods such as S/KEY, one-time-pads, hardware tokens that print a number or string, and other legacy authentication methods with RADIUS and TACACS servers. For SSH keyboard interactive authentication to work, ensure that the Apply password change rule checkbox is checked on the Authentication Server Group Setup page on the RADIUS/TACACS server. The keyboard interactive authentication method works only with SSH V2 and the blank password mechanism is supported only with TACACS authentication.

To enable Secure Shell encryption on the switch, perform this task in privileged mode:

Task

Command

Step 1

Create the RSA host key.

set crypto key rsa nbits [force]

Step 2

Set the SSH version.

Note If you do not specify the v1 or the v2 keyword, SSH operates in compatibility mode.

set ssh mode {v1 | v2}

Step 3

Clear the SSH mode configuration.

clear ssh mode

Step 4

Display the SSH configuration information.

show ssh

This example shows how to create the RSA host key:
Console> (enable) set crypto key rsa 1024
Generating RSA keys.... [OK]
Console> (enable) set ssh mode v2
SSH protocol mode set to SSHv2 Only.
Console> (enable) show ssh
Session      Protocol       Cipher     State           PID     Userid       Host
-------      --------       ------     -----           ---     --------     ----- 
0            V2             3DES       SESSION_OPEN    146     dkoya        171.69.66.45
1            V1             3DES       SESSION_OPEN    147     -            dove.cisco.com
SSH server mode : V1 and V2
Console> (enable)
The nbits value specifies the RSA key size. The valid key size range is from 512-2048 bits. For SSH version 2, the minimum recommended key size is 768 bits. A key size with a larger number provides higher security but takes longer to generate.

You can enter the optional force keyword to regenerate the keys and suppress the warning prompt of overwriting existing keys.

Monitoring User Sessions

You can display the currently active user sessions on the switch using the show users command. The command output displays all the active console port and Telnet sessions on the switch.

To display the active user sessions on the switch, perform this task in privileged mode:

Task

Command

Display the currently active user sessions on the switch.

show users [noalias]

This example shows the output of the show users command when local authentication is enabled for console and Telnet sessions (the asterisk [*] indicates the current session):
Console> (enable) show users
  Session  User             Location
  -------- ---------------- -------------------------
  console  
  telnet                    sam-pc.bigcorp.com
* telnet                    jake-mac.bigcorp.com
Console> (enable) 
This example shows the output of the show users command when TACACS+ authentication is enabled for console and Telnet sessions:
Console> (enable) show users
  Session  User             Location
  -------- ---------------- -------------------------
  console  sam
  telnet   jake             jake-mac.bigcorp.com
  telnet   tim              tim-nt.bigcorp.com
* telnet   suzy             suzy-pc.bigcorp.com
Console> (enable)
This example shows how to display information about a user session using the noalias keyword to display the IP addresses of the connected hosts:
Console> (enable) show users noalias
  Session  User             Location
  -------- ---------------- -------------------------
  console  
  telnet                    10.10.10.12
* telnet                    10.10.20.46
Console> (enable)
To disconnect an active user session, perform this task in privileged mode:

Task

Command

Disconnect an active user session on the switch.

disconnect {console | ip_addr}

This example shows how to disconnect an active console port session and an active Telnet session:
Console> (enable) show users
  Session  User             Location
  -------- ---------------- -------------------------
  console  sam
  telnet   jake             jake-mac.bigcorp.com
  telnet   tim              tim-nt.bigcorp.com
* telnet   suzy             suzy-pc.bigcorp.com
Console> (enable) disconnect console
Console session disconnected.				
Console> (enable) disconnect tim-nt.bigcorp.com
Telnet session from tim-nt.bigcorp.com disconnected. (1)
Console> (enable) show users
  Session  User             Location
  -------- ---------------- -------------------------
  telnet   jake             jake-mac.bigcorp.com
* telnet   suzy             suzy-pc.bigcorp.com
Console> (enable)
Using Ping

These sections describe how to use IP ping:

•Understanding How Ping Works

•Executing Ping

Understanding How Ping Works

You can use IP ping to test connectivity to remote hosts. If you attempt to ping a host in a different IP subnetwork, you must define a static route to the network or configure a router to route between those subnets.

The ping command is configurable from normal EXEC mode and privileged EXEC mode. In normal EXEC mode, the ping command supports the -s parameter, which allows you to specify the packet size and packet count. In privileged EXEC mode, the ping command lets you specify the packet size, packet count, and the wait time.

Table 20-1 shows the default values that apply to the ping-s command.

Table 20-1 Ping Default Values

Description

Ping

Ping-s

Number of Packets

5

0=continuous ping

Packet Size

56

56

Wait Time

2

2

Source Address

Host IP Address

N/A

To stop a ping in progress, press Ctrl-C.

Ping returns one of the following responses:

•Normal response—The normal response (hostname is alive) occurs in 1 to 10 seconds depending on the network traffic.

•Destination does not respond—If the host does not respond, a no answer message is returned.

•Unknown host—If the host does not exist, an unknown host message is returned.

•Destination unreachable—If the default gateway cannot reach the specified network, a destination unreachable message is returned.

•Network or host unreachable—If there is no entry in the route table for the host or network, a network or host unreachable message is returned.

Executing Ping

To ping another device on the network from the switch, perform one of these tasks in normal or privileged mode:

Task

Command

Ping a remote host.

ping host

Ping a remote host using ping options.

ping -s host [packet_size] [packet_count]

This example shows how to ping a remote host from normal EXEC mode:
Console> ping labsparc
labsparc is alive
Console> ping 72.16.10.3
12.16.10.3 is alive
Console> 
This example shows how to ping a remote host using the ping -s option:
Console> ping -s 12.20.5.3 800 10
PING 12.20.2.3: 800 data bytes
808 bytes from 12.20.2.3: icmp_seq=0. time=2 ms
808 bytes from 12.20.2.3: icmp_seq=1. time=3 ms
808 bytes from 12.20.2.3: icmp_seq=2. time=2 ms
808 bytes from 12.20.2.3: icmp_seq=3. time=2 ms
808 bytes from 12.20.2.3: icmp_seq=4. time=2 ms
808 bytes from 12.20.2.3: icmp_seq=5. time=2 ms
808 bytes from 12.20.2.3: icmp_seq=6. time=2 ms
808 bytes from 12.20.2.3: icmp_seq=7. time=2 ms
808 bytes from 12.20.2.3: icmp_seq=8. time=2 ms
808 bytes from 12.20.2.3: icmp_seq=9. time=3 ms
----17.20.2.3 PING Statistics----
10 packets transmitted, 10 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 2/2/3
Console> 
This example shows how to enter a ping command in privileged mode specifying the number of packets, the packet size, and the timeout period:
Console> (enable) ping
Target IP Address []: 12.20.5.19
Number of Packets [5]: 10
Datagram Size [56]: 100
Timeout in seconds [2]: 10
Source IP Address [12.20.2.18]: 12.20.2.18
!!!!!!!!!!
----12.20.2.19 PING Statistics----
10 packets transmitted, 10 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 1/1/1
Console> (enable) 
Using Layer 2 Traceroute

The Layer 2 Traceroute utility allows you to identify the physical path that a packet will take when going from a source to a destination. The Layer 2 Traceroute utility determines the path by looking at the forwarding engine tables of the switches in the path.

Information is displayed about all Catalyst 6500 series switches that are in the path from the source to the destination.

These sections describe how to use Layer 2 Traceroute:

•Layer 2 Traceroute Usage Guidelines

•Identifying a Layer 2 Path

Layer 2 Traceroute Usage Guidelines

This section describes the guidelines for using the Layer 2 Traceroute utility:

•The Layer 2 Traceroute utility works for unicast traffic only.

•You must enable Cisco Discovery Protocol (CDP) on all of the Catalyst 5000 and 6500 series switches in the network. (See Chapter 31, "Configuring CDP" for information about enabling CDP.) If any devices in the path are transparent to CDP, l2trace will not be able to trace the Layer 2 path through those devices.

•You can use this utility from a switch that is not in the Layer 2 path between the source and the destination; however, all of the switches in the path, including the source and destination, must be reachable from the switch.

•All switches in the path must be reachable from each other.

•You can trace a Layer 2 path by specifying the source and destination IP addresses (or IP aliases) or the MAC addresses. If the source and destination belong to multiple VLANs and you specify MAC addresses, you can also specify a VLAN.

•The source and destination switches must belong in the same VLAN.

•The maximum number of hops that an l2trace query will try is 10; this includes the hops that are involved in source tracing.

•The Layer 2 Traceroute utility does not work with Token Ring VLANs, when multiple devices are attached to one port through hubs, or when multiple neighbors are on a port.

Identifying a Layer 2 Path

To identify a Layer 2 path, perform one of these tasks in privileged mode:

Task

Command

(Optional) Trace a Layer 2 path using MAC addresses.

l2trace {src-mac-addr} {dest-mac-addr} [vlan] [detail]

(Optional) Trace a Layer 2 path using IP addresses or IP aliases.

l2trace {src-ip-addr} {dest-ip-addr} [detail]

This example shows the source and destination MAC addresses specified, with no VLAN specified, and the detail option specified. For each Catalyst 5000 and 6500 series switch found in the path, the output shows the device type, device name, device IP address, in port name, in port speed, in port duplex mode, out port name, out port speed, and out port duplex mode.
Console> (enable) l2trace 00-01-22-33-44-55 10-22-33-44-55-66 detail
l2trace vlan number is 10. 
00-01-22-33-44-55 found in C5500 named wiring-1 on port 4/1 10Mb half duplex 
C5500:wiring-1:192.168.242.10:4/1 10Mb half duplex -> 5/2 100MB full duplex 
C5000:backup-wiring-1:192.168.242.20:1/1 100Mb full duplex -> 3/1 100MB full duplex 
C5000:backup-core-1:192.168.242.30:4/1 100 MB full duplex -> 1/1 100MB full duplex 
C6000:core-1:192.168.242.40:1/1 100MB full duplex -> 2/1 10MB half duplex. 
10-22-33-44-55-66 found in C6000 named core-1 on port 2/1 10MB half duplex. 
Using IP Traceroute

The IP Traceroute utility allows you to identify the path that packets take through the network at Layer 3 on a hop-by-hop basis. The command output displays all network layer (Layer 3) devices, such as the routers, that the traffic passes through on the way to the destination.

These sections describe how to use IP Traceroute:

•Understanding How IP Traceroute Works

•Executing IP Traceroute

Understanding How IP Traceroute Works

The traceroute command uses the Time To Live (TTL) field in the IP header to cause the routers and the servers to generate specific return messages. Traceroute starts by sending a User Datagram Protocol (UDP) datagram to the destination host with the TTL field set to 1. If a router finds a TTL value of 1 or 0, it drops the datagram and sends back an Internet Control Message Protocol (ICMP) time-exceeded message to the sender. The traceroute facility determines the address of the first hop by examining the source address field of the ICMP time-exceeded message.

To identify the next hop, traceroute sends a UDP packet with a TTL value of 2. The first router decrements the TTL field by 1 and sends the datagram to the next router. The second router sees a TTL value of 1, discards the datagram, and returns the time-exceeded message to the source. This process continues until the TTL is incremented to a value that is large enough for the datagram to reach the destination host (or until the maximum TTL is reached).

To determine when a datagram reaches its destination, traceroute sets the UDP destination port in the datagram to a very large value that the destination host is unlikely to be using. When a host receives a datagram with an unrecognized port number, it sends an ICMP port unreachable error to the source. This message indicates to the traceroute facility that it has reached the destination.

The switches can participate as the source or destination of the traceroute command but will not appear as a hop in the traceroute command output.

Executing IP Traceroute

To trace the path that the packets take through the network, perform this task in privileged mode:

Task

Command

Execute IP traceroute to trace the Layer 3 path that the packets take through the network.

traceroute [-n] [-w wait_time] [-i initial_ttl]
[-m max_ttl] [-p dest_port] [-q nqueries] [-t tos] host [data_size]

This example shows how to use the traceroute command:
Console> (enable) traceroute 10.1.1.100
traceroute to 10.1.1.100 (10.1.1.100), 30 hops max, 40 byte packets
 1 10.1.1.1 (10.1.1.1)  1 ms  2 ms  1 ms
 2 10.1.1.100 (10.1.1.100)  2 ms  2 ms  2 ms
Console> (enable)
This example shows how to perform a traceroute with six queries to each hop with packets of 1400 bytes each:
Console> (enable) traceroute -q 6 10.1.1.100 1400
traceroute to 10.1.1.100 (10.1.1.100), 30 hops max, 1440 byte packets
 1 10.1.1.1 (10.1.1.1)  2 ms  2 ms  2 ms  1 ms  2 ms  2 ms
 2 10.1.1.100 (10.1.1.100)  2 ms  4 ms  3 ms  3 ms  3 ms  3 ms
Console> (enable)
Using System Warnings on Port Counters

You can monitor and troubleshoot the Catalyst 6500 series switches by polling the selected error counters on the ports and logging the system error messages. The messages are logged for the system, hardware, and spanning-tree ports for these conditions:

•Backplane traffic levels that exceed configurable thresholds

•Low remaining memory

•Detected memory corruption

•NVRAM logs

•Inband errors

•User Datagram Protocol (UDP) and TCP errors

The hardware error information is logged to provide information for the debug port counters at 30-minute intervals. The messages are logged if the counter values increase.

Spanning-tree error information is provided for the following:

•Ports that go from the blocking to the forwarding state

•Bridge protocol data unit (BPDU) skewing that exceeds a fixed threshold

These sections describe how to use the system warning feature on the Catalyst 6500 series switches:

•Executing System Warnings on Port Counters

•Executing Hardware Level Warnings on Port Counters

•Executing Spanning-Tree Warnings on Port Counters

Executing System Warnings on Port Counters

These sections describe how to execute the system warnings on the port counters:

•Backplane Traffic

•Low Remaining Memory

•Detected Memory Corruption

•NVRAM Logs

•Inband Errors

•UDP Errors

Backplane Traffic

You can configure backplane threshold detection by using a high threshold as a percentage. When backplane traffic goes over the specified threshold, compared with the previous traffic poll, a syslog message is generated. However, if you specify a 100-percent threshold (the default), no syslog message is generated.

For switches with three switching buses, you can configure a threshold and syslog throttling (to control the syslog event polling and message generation) for each switching bus instead of configuring the average traffic of all three buses. The throttle interval is 5 minutes.

This example shows how to set a threshold:
Console> (enable) set traffic monitor help
Usage: set traffic monitor <threshold>
       (threshold = 0..100 in percentage)
Console> (enable) set traffic monitor 60
Traffic monitoring threshold set to 60%.
Console> (enable) show traffic
Threshold: 60%
Backplane-Traffic Peak Peak-Time
----------------- ---- -------------------------
  0%                0% Tue Apr 16 2002, 08:01:53
Fab Chan Input Output
-------- ----- ------
       0    0%     0%
       1    0%     0%
       2    0%     0%
       3    0%     0%
       4    0%     0%
       5    0%     0%
       6    0%     0%
       7    0%     0%
       8    0%     0%
       9    0%     0%
      10    0%     0%
      11    0%     0%
      12    0%     0%
      13    0%     0%
      14    0%     0%
      15    0%     0%
      16    0%     0%
      17    0%     0%
Console> (enable)
Some sample syslog messages are as follows:
2000 Jan 11 06:00:27 PST -07:00 %SYS-4-SYS_HITRFC: 62% traffic detected on switching bus 
(A)
2000 Feb 21 12:00:27 PST -07:00 %SYS-4-SYS_HITRFC: 65% traffic detected on switching bus
Low Remaining Memory

When memory allocation of clusters and buffers on the Catalyst 6500 series switch goes above a high watermark of 90 percent, the syslog messages are generated. These actions generate the syslog messages:

•When cluster allocation usage goes above a high watermark of 90 percent, the throttle interval is 1 hour.

•When mbufs allocation usage goes above a high watermark of 90 percent, the throttle interval is 1 hour.

•When malloc allocation usage goes above a high watermark of 90 percent, the throttle interval is 1 hour.

A sample syslog message is as follows:
1999 Sep 9 00:00:00 PDT -07:00 %SYS-3-SYS_MEMLOW: Memory cluster usage exceeded 90%
1999 Sep 9 00:00:00 PDT -07:00 %SYS-3-SYS_MEMLOW: Mbuf usage exceeded 90%
1999 Sep 9 00:00:00 PDT -07:00 %SYS-3-SYS_MEMLOW: Malloc usage exceeded 90%
Detected Memory Corruption

By default, memory corruption that is detected by the Memory Management Module (MMU) is enabled. This example shows how to enable memory corruption detection:
Console> (enable) set errordetection memory
Usage: set errordetection memory <enable|disable>
Console> (enable) set errordetection memory enable
Memory error detection enabled.
Console> (enable) show errordetection
Inband error detection:             disabled
Memory error detection:             enabled
Packet buffer error detection:      errdisable
Port counter error detection:       disabled
Port link-errors action:            port-failover
Port link-errors interval:          30 seconds
Port link-errors high rx-threshold: 1000 packets
Port link-errors low rx-threshold:  1000 packets
Port link-errors high tx-threshold: 1000 packets
Port link-errors low tx-threshold:  1000 packets
Port link-errors sampling:          3
Console> (enable)
A sample syslog message is as follows:
1999 Nov 23 16:32:21 PDT -07:00 %SYS-3-SYS_MEMERR: Out of range while freeing address 
0xabcdefab
NVRAM Logs

The syslog errors are generated for each configuration-related NVRAM log event. These events may indicate configuration or hardware errors or NVRAM configurations that are made without notification of users.The hardware errors NVRAM log is not syslogged. The NVRAM log time stamp is not included in the message.

A sample syslog message is as follows:
1999 Nov 23 16:37:21 PDT -07:00 %SYS-4-SYS_NVLOG: convert_post_SAC_CiscoMIB:Block 63 
converted from version 0 to 1
1999 Nov 23 16:37:25 PDT -07:00 %SYS-4-SYS_NVLOG: StartupConfig:Auto config started
Inband Errors

The inband syslog messages are generated when transmit or receive errors are detected. By default, the inband syslog messages are enabled. This example shows how to enable inband error detection:
Console> (enable) set errordetection inband
Usage: set errordetection inband <enable|disable>
Conosle> (enable) set errordetection inband enable
Inband errordetection enabled.
When the resource errors on the receive side reach a multiple of 500, this syslog error is generated:
2000 Jun 24 06:37:25 PDT -07:00 %SYS-3-INBAND_NORESOURCE: inband resource error warning 
(500)
2000 Jun 24 08:12:03 PDT -07:00 %SYS-3-INBAND_NORESOURCE: inband resource error warning 
(1000)
For each spurious interrupt, a message similar to the following is logged:
1999 Dec 25 18:22:08 PDT -07:00 %SYS-3-INBAND_SPRINTR: inband spurious interrupt occurred 
(2)
For each inband port transmit and receive failure, a message similar to the following is logged:

Note The number in parentheses indicates the number of times that the inband port is reset instead of the number of transmit or receive fails.
1999 Dec 25 18:22:08 PDT -07:00 %SYS-3-INBAND_TXRXFAIL: inband driver stuck/reset (2)
UDP Errors

When you enter the show netstat udp command, each socket overflow generates a message similar to the following:
1999 Oct 31 23:59:59 PDT -07:00 %IP-3-UDP_SOCKOVFL: UDP socket overflow
When you enter the show netstat udp/tcp command, each bad UDP/TCP checksum generates a message similar to the following:
1999 Oct 31 23:59:59 PDT -07:00 %IP-3-UDP_BADCKSUM: UDP bad checksum
1999 Oct 31 23:59:59 PDT -07:00 %IP-3-TCP_BADCKSUM: TCP bad checksum
Executing Hardware Level Warnings on Port Counters

You can poll selected error counters of each switch port every 30 minutes. If the count goes up between two subsequent polls on the same port, the incidence is logged. Background polling is enabled or disabled by the set errordetection portcounters command. By default, polling is enabled.

Enter the set errordetection portcounters command as follows:
Console> (enable) set errordetection portcounters
Usage: set errordetection portcounters <enable|disable>
Console> (enable) set errordetection portcounters disable
Port Counters error detection disabled.
A sample syslog message is as follows:
1999 Jan 11 08:02:59 PDT -07:00 %SYS-3-PORT_ERR: Port 3/4 swBusResultEvent (12)
1999 Jan 11 09:03:03 PDT -07:00 %SYS-3-PORT_ERR: Port 3/4 swBusResultEvent (223)
1999 Jan 11 09:03:03 PDT -07:00 %SYS-4-PORT_WARN: Port 3/4 dmaTxFull (7) dmaRetry (33) 
dmaLevel2Request(21)
Executing Spanning-Tree Warnings on Port Counters

These sections describe how to execute the spanning-tree warnings on the port counters:

•Blocking to Listening Transitions

•BPDU Skewing

•SNMP

Blocking to Listening Transitions

A syslog message is generated whenever a port goes from blocking to listening. The spanning-tree state changes have existing syslog messages.

A sample syslog messages is as follows:
1999 Jan 03 00:02:59 PDT -07:00 %SPANTREE-5-PORTLISTEN: Port 3/4 state in vlan 1 changed 
to listening
1999 Jan 03 00:02:59 PDT -07:00 %SPANTREE-5-TR_PORTLISTEN: Trcrf 101 in trbrf 102 state 
changed to listening
BPDU Skewing

A syslog message is generated when the interval between two consecutive BPDUs that are received on a port exceeds the hello time interval by 10 seconds. The throttle interval is one message per port, per minute for all VLAN numbers.

A sample syslog messages is as follows:
1999 Jan 01 00:01:19 PDT -07:00 %SPANTREE-3-BPDUSKEW: Port 2/1 vlan 1 BPDU skewed
1999 Jan 01 00:05:19 PDT -07:00 %SPANTREE-3-BPDUSKEW: Port 2/5 vlan 1 BPDU skewed
1999 Jan 01 00:05:23 PDT -07:00 %SPANTREE-3-BPDUSKEW: Port 2/5 vlan 3 BPDU skewed
SNMP

A matching SNMP trap generation for each of the syslog warnings using the existing clogMessageGenerated trap is sent every time that any syslog message is generated.

Configuring Packet-Buffer Error Handling

The set errordetection packet-buffer {errdisable | powercycle | supervisor {errdisable | shutdown}} command allows you to specify packet-buffer error handling as follows (the default is errdisable):

•errdisable—If you enter the errdisable keyword, the ports that experience the packet-buffer errors are put in the errdisable state.

•powercycle—If you enter the powercycle keyword, the modules supporting this option are power cycled when they encounter the packet-buffer errors. When you choose this option, a ROMMON upgrade is automatically performed on the module (if required), and the normal bootup sequence is bypassed to reduce the module downtime (this feature is also referred to as the rapid boot feature).

•supervisor—If you enter the supervisor errdisable keywords, the supervisor engine ports that experience the packet-buffer errors are put in the errdisable state. If you enter the supervisor shutdown keywords, the supervisor engine ports that experience the packet-buffer errors are shut down.

Caution Do not power cycle the module when the ROMMON image is downloading. Doing so might damage the module.

The rapid boot feature is available on the following modules:

•WS-X6248-RJ45

•WS-X6248-TEL

•WS-X6348-RJ45

•WS-X6348-RJ21

•WS-X6148-RJ45

•WS-X6148-RJ21

Note Enter the show errordetection command to display information about the error-detection configuration.

Configuring EtherChannel/Link Error Handling

This feature provides for an automatic failover of traffic from one port in an EtherChannel to another port in the same EtherChannel when one of the ports in the channel exceeds a configurable error threshold within the specified interval. The port failover only occurs if there is an operational port left in the EtherChannel. If the failed port is the last port in the EtherChannel, the port does not enter the "port failover" state and continues to pass traffic regardless of the type of errors being received. Single, nonchanneling ports do not go into the port failover state; these ports go into the errdisable state when the error threshold is exceeded within the specified interval.

Note The link errors that are monitored are based on three counters: Inerrors, RXCRC (CRCAlignErrors), and TXCRC. If the errdisable timer for the link is enabled (using the set errdisable-timeout enable command), the errdisabled port is automatically reenabled after the timeout interval expires (the timeout interval is specified using the set errdisable-timeout interval {interval} command). For more information on these commands, see the "Configuring a Timeout Period for Ports in errdisable State" section on page 4-12.

The set errordetection link-errors global command allows you to specify EtherChannel/link error handling as follows:

•set errordetection link-errors action {errordisable | port-failover}

If a port's error count reaches the configurable threshold's high value (within the specified sampling count period), the action taken is either errordisable or port-failover. If you select errordisable, the port goes into the errdisable state when the high threshold is reached. If you select port-failover, the port's channel status is considered and the port goes into the errdisable state if the port is in a channel and it is not the last operational port in the channel (the port also goes into the errdisable state if it is a single port). The default action setting is port-failover.

•set errordetection link-errors interval {timer-value}

The interval timer-value specified determines how often the port's error counters are read. The default timer value specified is 30 seconds, and the allowed range is from 30 to 1800 seconds.

Note If the EtherChannel/link error handling feature is not enabled, you can still set the interval. If the feature is enabled, when you specify an interval, the timer restarts with the new value.

•set errordetection link-errors {inerrors | rxcrc | txcrc} {[high value] | [low value]}

The rxcrc and txcrc values specified determine how many link errors are allowed during the specified interval by entering the interval timer-value command. If the low threshold is reached (within the sampling count period specified), a syslog message is displayed. If the high threshold is reached (within the sampling count period specified), in addition to displaying a syslog message, the port is either errdisabled or the port failover mechanism is triggered. The high threshold range is from 2 to 65535, and the low threshold range is from 1 to 65534. The inerrors values specified determines the inerrors threshold. The default threshold values are as follows:

–The high value for the inerrors threshold is 1001 packets.

–The low value for the inerrors threshold is 1000 packets.

–The high value for the rxcrc threshold is 1001 packets.

–The low value for the rxcrc threshold is 1000 packets.

–The high value for the txcrc threshold is 1001 packets.

–The low value for the rxcrc threshold is 1000 packets.

•set errordetection link-errors sampling {sampling_count}

To minimize accidentally putting a port into the errdisable state due to a one-time event that is not a true system error condition, you can specify a sampling_count. The sampling_count determines the number of times that a port must reach the high or low threshold value before the port is placed in the errdisable state. For example, if the port's high threshold value is 1000 and the sampling count is 3, the port is errdisabled only after it has reached the 1000 threshold 3 times. The default sampling count value is 3, and the allowed range is from 1 to 255.

Note Enter the show errordetection command to display information about the error-detection configuration.

Configuring IEEE 802.3ah Ethernet OAM

The Ethernet Operations, Administrations, and Maintenance (OAM) feature follows the specifications provided in the IEEE 802.3ah document. The major Ethernet OAM features covered by this protocol are link monitoring, remote failure indication, and a remote loopback test.

Note We do not support remote failure indication.

This section describes how to configure IEEE 802.3ah Ethernet OAM:

•Understanding How OAM Works

•Ethernet OAM Configuration Guidelines and Restrictions

•Executing Ethernet OAM

Understanding How OAM Works

In the Open Systems Interconnection (OSI) reference model, Ethernet OAM is an optional sublayer that is implemented in the data link layer between the logical link control (LLC) and MAC sublayers (see Figure 20-1).

Figure 20-1 Position of Ethernet OAM in the OSI Reference Model

Note OAM is a relatively slow protocol with low bandwidth requirements (the frame transmission rate is limited to a maximum of 10 frames per second), and it is not required for normal link operation. OAM frames, referred to as OAM protocol data units (OAMPDUs), use the slow protocol destination MAC address (0180.c200.0002), are intercepted by the MAC sublayer, and cannot propagate beyond a single hop within an Ethernet network.

You can implement OAM on any full-duplex point-to-point or emulated point-to-point Ethernet link. You configure OAM on a per-port basis and the OAM configuration is independent of any other configuration on the port. The port can be a trunk port, access port, or part of an EtherChannel. When you configure OAM on a port, that port's OAM functions are independent of the OAM functions that are configured on other ports.

Ethernet OAM Configuration Guidelines and Restrictions

Follow these configuration guidelines and restrictions when configuring Ethernet OAM:

•The OAM feature is only supported on physical, external Ethernet ports.

•The port that is running OAM must be in full-duplex mode.

•Remote failure indication is not supported.

•To support OAM remote loopback mode, the port needs to specifically be configured as follows:

–The trunk mode must be set to off.

–The channel mode must be set to off.

–The port cannot be a private VLAN port.

•MIB variable requests and responses are not supported.

Executing Ethernet OAM

These sections describe how to execute Ethernet OAM:

•Enabling or Disabling Ethernet OAM

•Specifying the Ethernet OAM Port Mode

•Denying or Permitting Ethernet OAM Remote Loopback Tests

•Enabling or Disabling the Ethernet OAM Remote Loopback Test

•Specifying the Number of Packets and the Packet Size for the Ethernet OAM Remote Loopback Test and Running the Test

•Enabling or Disabling Ethernet OAM Link Monitoring

•Specifying the Window Size for Link Events for Ethernet OAM Link Monitoring

•Specifying the Low-Threshold Error Count and the Associated Action for Ethernet OAM Link Monitoring

•Specifying the High-Threshold Error Count and the Associated Action for Ethernet OAM Link Monitoring

•Specifying the Associated Action for OAM Critical Link Events

•Clearing Ethernet OAM Statistics and the Ethernet OAM Configuration

•Clearing User-Configured Parameters for OAM Link Monitoring

•Clearing User-Configured Actions for OAM Critical Link Events

•Displaying Ethernet OAM-Related Information

•Displaying Ethernet OAM Neighbor Information

•Displaying Ethernet OAM Remote Loopback Test Information

•Displaying Ethernet OAM Statistics

Enabling or Disabling Ethernet OAM

You can use the commands in this section to enable or disable OAM on the specified ports. By default, OAM is disabled on all ports.

To enable or disable OAM on the specified ports, perform this task in privileged mode:

Task

Command

Enable or disable OAM on the specified ports.

set port ethernet-oam mod/port {disable | enable}

This example shows how to enable OAM on the specified port:
Console> (enable) set port ethernet-oam 3/1 enable 
Successfully enabled OAM on port(s) 3/1.
Console> (enable)
Specifying the Ethernet OAM Port Mode

You can use the commands in this section to specify the OAM port mode on the specified ports. Table 20-2 lists the OAM port functions that are allowed in the active and passive modes. By default, the OAM mode is active on all ports.

Table 20-2 Ethernet OAM Port Modes

Capability

Active

Passive

Initiates the OAM discovery process.

Yes

No

Reacts to the OAM discovery process initiation.

Yes

Yes

Required to send information OAMPDUs.

Yes

Yes

Permitted to send event notification OAMPDUs.

Yes

Yes

Permitted to send variable request OAMPDUs.

Yes

No

Permitted to send variable response OAMPDUs.

Yes¹

Yes

Permitted to send loopback control OAMPDUs.

Yes

No

Reacts to loopback control OAMPDUs.

Yes1

Yes

Permitted to send organization-specific OAMPDUs.

Yes

Yes

¹Requires the peer port to be in active mode.

To specify the OAM port mode on the specified ports, perform this task in privileged mode:

Task

Command

Specify the OAM port mode on the specified ports.

set port ethernet-oam mod/port mode {active | passive}

This example shows how to specify the OAM port mode to active on the specified port:
Console> (enable) set port ethernet-oam 3/1 mode active 
Successfully updated OAM mode to active on port(s) 3/1.
Console> (enable)
Denying or Permitting Ethernet OAM Remote Loopback Tests

You can use the commands in this section to deny or permit an OAM remote loopback request on the specified ports. The default is permit.

To deny or permit an OAM remote loopback request on the specified ports, perform this task in privileged mode:

Task

Command

Deny or permit an OAM remote loopback request on the specified ports.

set port ethernet-oam mod/port remote-loopback {deny | permit}

This example shows how to deny an OAM remote loopback request on the specified port:
Console> (enable) set port ethernet-oam 3/1 remote-loopback deny
Successfully updated OAM remote-loopback capability to deny on port(s) 3/1.
Console> (enable) 
Enabling or Disabling the Ethernet OAM Remote Loopback Test

You can use the commands in this section to enable or disable the OAM remote loopback test on the specified ports. The ports that you specify to run this test must be connected to a peer OAM device that is capable of entering into the OAM remote loopback mode.

Note The commands in this section are not saved in your configuration file or NVRAM.

Note During a remote loopback test operation, all packets including data packets are dropped at the port when remote loopback is enabled. This behavior results in many protocols (such as STP, EtherChannel protocols, and so on) resetting their state machines.

To enable or disable the OAM remote loopback test on the specified ports, perform this task in privileged mode:

Task

Command

Enable or disable the OAM remote loopback test on the specified ports.

set port ethernet-oam mod/port remote-loopback {disable | enable}

This example shows how to enable the OAM remote loopback test on the specified port:
Console> (enable) set port ethernet-oam 3/1 remote-loopback enable
Successfully initiated OAM remote-loopback on port(s) 1/1.
Port status set to inactive
Console> (enable)
Specifying the Number of Packets and the Packet Size for the Ethernet OAM Remote Loopback Test and Running the Test

You can use the commands in this section to specify the number of packets and the packet size for the OAM remote loopback test and run the test on the specified ports. This command can be used only on ports that have the OAM remote loopback test enabled. After entering this command, the remote loopback test is run and the test result summary is displayed after the test finishes. By default, 10,000 64-byte packets are sent. The number of packets allowed is 1 to 99999999 packets. The allowable packet size is from 64 to 1518 bytes.

Note The commands in this section are not saved in your configuration file or NVRAM.

To specify the number of packets and the packet size for the OAM remote loopback test and run the test on the specified ports, perform this task in privileged mode:

Task

Command

Specify the number of packets and the packet size for the OAM remote loopback test and run the test on the specified ports.

set port ethernet-oam mod/port remote-loopback test [no of packets [packet size]]

This example shows how to specify the number of packets for the OAM remote loopback test and run the test on the specified port:
Console> (enable) set port ethernet-oam 1/1 remote-loopback test 999999
Transmitting packets ...
OAM Remote Loopback Test 1/1: 999999 transmitted, 999999 received
Console> (enable)
Enabling or Disabling Ethernet OAM Link Monitoring

You can use the commands in this section to enable or disable OAM link monitoring on the specified ports. The default is enabled.

To enable or disable OAM link monitoring on the specified ports, perform this task in privileged mode:

Task

Command

Enable or disable OAM link monitoring on the specified ports.

set port ethernet-oam mod/port link-monitor {disable | enable}

This example shows how to enable OAM link monitoring on the specified port:
Console> (enable) set port ethernet-oam 3/1 link-monitor enable
Successfully enabled OAM link-monitor on port(s) 3/1.
Console> (enable)
Specifying the Window Size for Link Events for Ethernet OAM Link Monitoring

You can use the commands in this section to specify the OAM link monitoring window size for the corresponding link events. The defaults and ranges for the window sizes are as follows:

•symbol-period—The default is 625 million symbols. The range is from 1 to 1,000,000 in million-symbol increments.

•frame—The default is 30 seconds. The range is from 10 to 65535 in 100-millisecond increments (1 to 6553.5 seconds).

•frame-period—The default is 10 million frames. The range is from 200 to 2,000,000,000 frames.

To specify the OAM link monitoring window size for corresponding link events on the specified ports, perform this task in privileged mode:

Task

Command

Specify the OAM link monitoring window size for corresponding link events on the specified ports.

set port ethernet-oam mod/port link-monitor {symbol-period | frame | frame-period} window size

This example shows how to specify a link monitoring symbol-period window size of 10000:
Console> (enable) set port ethernet-oam 3/1 link-monitor symbol-period window 10000
Successfully updated OAM symbol-period window on port(s) 3/1.
Console> (enable) 
This example shows how to specify a link monitoring frame window size of 100:
Console> (enable) set port ethernet-oam 3/1 link-monitor frame window 100
Successfully updated OAM frame window on port(s) 3/1.
Console> (enable)
This example shows how to specify a link monitoring frame-period window size of 1000:
Console> (enable) set port ethernet-oam 3/1 link-monitor frame-period window 1000
Successfully updated OAM frame-period window on port(s) 3/1.
Console> (enable) 
Specifying the Low-Threshold Error Count and the Associated Action for Ethernet OAM Link Monitoring

You can use the commands in this section to specify the OAM link monitoring low-threshold error count and the associated action on the specified ports. The default low-threshold error count is one error. The default action is warning.

The low-threshold error count also serves as the monitoring threshold for OAM link monitoring. Once the specified low-threshold error count is met or exceeded, an OAM link event TLV is generated and sent as described in the IEEE 802.3ah document.

To specify the OAM link monitoring low-threshold error count and the associated action on the specified ports, perform this task in privileged mode:

Task

Command

Specify the OAM link monitoring low-threshold error count and the associated action on the specified ports.

set port ethernet-oam mod/port link-monitor {symbol-period | frame | frame-period} low-threshold count [action {none | warning}]

This example shows how to specify the OAM link monitoring low-threshold error count and the associated action on the specified port:
Console> (enable) set port ethernet-oam 3/1 link-monitor frame low-threshold 2 action none
Successfully updated OAM frame low threshold on port(s) 3/1.
Console> (enable) 
Specifying the High-Threshold Error Count and the Associated Action for Ethernet OAM Link Monitoring

You can use the commands in this section to specify the OAM link monitoring high-threshold error count and the associated action on the specified ports. The default high-threshold error count is 65535 errors. The default action is warning.

To specify the OAM link monitoring high-threshold error count and the associated action on the specified ports, perform this task in privileged mode:

Task

Command

Specify the OAM link monitoring high-threshold error count and the associated action on the specified ports.

set port ethernet-oam mod/port link-monitor {symbol-period | frame | frame-period} high-threshold count [action {errordisable | none | warning}]

This example shows how to specify the OAM link monitoring high-threshold error count and the associated action on the specified port:
Console> (enable) set port ethernet-oam 3/1 link-monitor frame high-threshold 100 action 
none
Successfully updated OAM frame-period high threshold on port(s) 3/1.
Console> (enable) 
Specifying the Associated Action for OAM Critical Link Events

You can use the commands in this section to specify the associated action for OAM critical link events (critical-event, dying-gasp, or link-fault) on the specified ports. The default is warning. If you specify the dying-gasp keyword, the errordisable option is not available.

The error-block action sets the port to blocking state when a remote link failure flag is received and continues to monitor the link status flag. The error-block action then automatically changes the port to forwarding state whenever the remote link becomes operational.

To specify the associated action for OAM critical link events on the specified ports, perform this task in privileged mode:

Task

Command

Specify the associated action for OAM critical link events on the specified ports.

set port ethernet-oam mod/port {critical-event | dying-gasp^¹ | link-fault} action {errordisable | none | warning | error-block}

¹Does not support errordisable and error-block.

This example shows how to specify the associated action for OAM critical link events on the specified port:
Console> (enable) set port ethernet-oam 3/1 link-fault action errdisable 
Successfully updated OAM link-fault action on port(s) 3/1.
Console> (enable) 
This example shows how to set the critical link event action to error-block for a port:
Console> (enable) set port ethernet-oam 3/2 critical-event action error-block 
Successfully updated OAM critical-event action on port(s) 3/2.
Clearing Ethernet OAM Statistics and the Ethernet OAM Configuration

To clear OAM statistics and OAM-related configurations on all ports or individual ports, perform this task in privileged mode:

Task

Command

Clear OAM statistics and OAM-related configurations on all ports or individual ports.

clear port ethernet-oam [mod/port] [statistics]

This example shows how to clear the OAM configuration on all ports:
Console> (enable) clear port ethernet-oam
Successfully cleared OAM config on port(s) 2/1-2,3/1-48,8/1-8.
Console> (enable)
This example shows how to clear the OAM configuration from a specific port:
Console> (enable) clear port ethernet-oam 3/1 
Successfully cleared OAM config on port(s) 3/1.
Console> (enable) 
This example shows how to clear OAM statistics from all ports:
Console> (enable) clear port ethernet-oam statistics
Successfully cleared OAM statistics on port(s) 2/1-2,3/1-48,8/1-8.
Console> (enable) 
This example shows how to clear OAM statistics from a specific port:
Console> (enable) clear port ethernet-oam 3/1 statistics
Successfully cleared OAM statistics on port(s) 3/1.
Console> (enable) 
Clearing User-Configured Parameters for OAM Link Monitoring

When you clear the high-threshold or low-threshold parameters, the associated action is also cleared.

To clear the user-configured parameters for OAM link monitoring on the specified ports, perform this task in privileged mode:

Task

Command

Clear the user-configured parameters for OAM link monitoring on the specified ports.

clear port ethernet-oam mod/port link-monitor {symbol-period | frame | frame-period} {high-threshold | low-threshold | window}

These examples show how to clear the user-configured parameters for OAM link monitoring on the specified port:
Console> (enable) clear port ethernet-oam 3/1 link-monitor frame high-threshold 
Successfully cleared OAM frame-period high-threshold on port(s) 3/1.
Console> (enable)
Console> (enable) clear port ethernet-oam 3/1 link-monitor frame-period window 
Successfully cleared OAM frame-period window on port(s) 3/1.
Console> (enable)
Clearing User-Configured Actions for OAM Critical Link Events

To clear the user-configured actions for OAM critical link events on the specified ports, perform this task in privileged mode:

Task

Command

Clear the user-configured actions for the OAM critical link events on the specified ports.

clear port ethernet-oam mod/port {critical-event | dying-gasp | link-fault} action

These examples show how to clear the user-configured actions for OAM critical link events on the specified port:
Console> (enable) clear port ethernet-oam 3/1 link-fault action 
Successfully cleared OAM link-fault action on port(s) 3/1.
Console> (enable) 
Console> (enable) clear port ethernet-oam 3/1 critical-event action 
Successfully cleared OAM critical-event action on port(s) 3/1.
Console> (enable)
Displaying Ethernet OAM-Related Information

To display the OAM configuration and status for all OAM ports or on the specified OAM ports, perform this task in normal mode:

Task

Command

Display the OAM configuration and status for all OAM ports or on the specified OAM ports.

show port ethernet-oam [mod | mod/port]

This example shows how to display the OAM configuration and status for the specified ports:
Console> (enable) show port ethernet-oam 1/1,3/5,4/6 
 
Port  State    Mode    Status       LinkMonitor ConfigRev MaxPdu 
----- -------- ------- ------------ ----------- --------- ------ 
1/1   enable   active  R-Loopback   enable      11        1518 
3/5   enable   passive Connecting   enable      38        1518 
4/6   disable  active  Operational  disable     0         1518 
Port  Remote   Link    UniDir  Variable 
      Loopback Event           retrieval
----- -------- ------- ------- ---------
1/1   Permit   enable  disable disable 
3/5   Permit   enable  enable  disable 
4/6   Deny     enable  disable disable 
Port  ErrSymbol Period  ErrSymbol Period    ErrSymbol Period
      Window              LowThreshold        HighThreshold 
      (millions)        Count     Action    Count     Action 
----- ----------------- --------- --------- --------- --------- 
1/1   625               1         None      10        Warning 
3/5   65535             1         Warning   1000      ErrDisable 
4/6   1                 1         None      1         ErrDisable 
Port   Errored Frame    Errored Frame       Errored Frame
       Window            LowThreshold       HighThreshold 
       (100 msec)       Count     Action    Count     Action 
----- ----------------- --------- --------- --------- --------- 
1/1   300               1         None      10        Warning 
3/5   65535             1         Warning   1000      ErrDisable 
4/6   1000              1         Warning   1         ErrDisable 
Port  ErrFrame Period   ErrFrame Period     ErrFrame Period
      Window             LowThreshold        HighThreshold 
                        Count     Action    Count     Action 
----- ----------------- --------- --------- --------- --------- 
1/1   10000             1         None      10        Warning 
3/5   1294967000        1         Warning   1000      ErrDisable 
4/6   200               1         Warning   1         ErrDisable
Port  LinkFaultAction   DyingGaspAction CriticalEventAction 
----- ----------------- --------------- ------------------- 
1/1   ErrDisable        Warning         Error-Block
3/5   None              Warning         None
4/6   ErrDisable        None            None
Console> (enable) 
Displaying Ethernet OAM Neighbor Information

You can use the commands in this section to display OAM neighbor information. The neighbor is the connected OAM peer.

To display OAM information for the specified neighbor or for all neighbors, perform this task in normal mode:

Task

Command

Display OAM information for the specified neighbor or for all neighbors.

show port ethernet-oam [mod | mod/port] neighbor

This example shows how to display OAM information for all neighbors:
Console> (enable) show port ethernet-oam neighbor 
Port  MAC Addr          OUI    VendorInfo Mode    ConfigRev MaxPDU 
----- ----------------- ------ ---------- ------- --------- ------ 
1/1   00-50-54-6c-b5-20 00000C 0000018C   passive 3         1518 
3/5   00-0b-fc-fb-4a-10 00000C 0000018D   active  7         1518 
Port  Remote   Link    UniDir  Variable 
      Loopback Event           retrieval 
----- -------- ------- ------- --------- 
1/1   permit   enable  disable disable 
3/5    deny      enable  enable   disable
Console> (enable)
Displaying Ethernet OAM Remote Loopback Test Information

You can use the commands in this section to display information about the OAM remote loopback test for the specified ports. The current-session keyword displays the statistics of the current OAM remote-loopback session. Specifying the detail keyword with the current-session keyword displays MAC statistics. The last-session keyword displays the statistics of the last OAM remote-loopback session. Specifying the detail keyword with the last-session keyword displays MAC statistics and statistics reported by the remote peer (if supported). After a port starts a new remote-loopback session, the last-session information becomes unavailable.

To display information about the OAM remote loopback test for the specified ports, perform this task in normal mode:

Task

Command

Display information about the OAM remote loopback test for the specified ports.

show port ethernet-oam [mod | mod/port] {remote-loopback} {current-session | last-session} [detail]

This example shows how to display information about the OAM remote loopback test for the current session:
Console> (enable) show port ethernet-oam 1/2 remote-loopback current-session
Port Loopback at OAM Rx     OAM Tx
---- ----------- ---------- ----------
1/2  Remote           33333      55555
Console> (enable) show port ethernet-oam 1/2 remote-loopback current-session detail
Port: 1/2 
Loopback: Remote OAM in loopback mode
Start: Mon Aug 1 2005, 07:30:59
End: Still running
Test statistics:
OAM Rx: 10000
OAM Tx: 10000
MAC Rx: 13415
MAC Tx: 13403
OAMPDU Rx: 3415
OAMPDU Tx: 3403
MAC Rx Drop: 0
Console> (enable)
This example shows how to display information about the OAM remote loopback test for the last session:
Console> (enable) show port ethernet-oam 1/2 remote-loopback last-session
Port Last Loopback at   OAM Rx     OAM Tx
---- ----------------   ---------- ----------
1/2  Remote                  33333      55555
Console> (enable) show port ethernet-oam 1/2 remote-loopback last-session detail
Port: 1/2 
Last Loopback: Remote OAM in loopback mode
Start: Mon Aug 1 2005, 07:30:59
End: Mon Aug 1 2005, 08:29:07
Test statistics:
OAM Rx: 10000
       OAM Tx: 10000
       MAC Rx: 13459
       MAC Tx: 13448
    OAMPDU Rx: 3459
    OAMPDU Tx: 3448
  MAC Rx Drop: 0
Test statistics reported by remote peer:
       OAM Rx: 10000
       OAM Tx: 10000
       MAC Rx: 13448
    OAMPDU Rx: 3448
  MAC Rx Drop: 0
Console> (enable)
Displaying Ethernet OAM Statistics

To display OAM statistics, perform this task in normal mode:

Task

Command

Display OAM statistics.

show port ethernet-oam [mod | mod/port] statistics

This example shows how to display OAM statistics for port 1/2:
Console> (enable) show port ethernet-oam 1/2 statistics 
Port  InfoPduRx  UniEventRx DupEventRx RLBCtrlRx  VarReqRx   VarResRx
----- ---------- ---------- ---------- ---------- ---------- ----------
1/2   2579       0          0          0          0          0
Port  InfoPduTx  UniEventTx DupEventTx RLBCtrlTx  VarReqTx   VarResTx
----- ---------- ---------- ---------- ---------- ---------- ----------
1/2   2571       0          0          1          0          0
Port  OrgSpecRx  UnknownRx  CiscoPduRx CiscoTLVRx
----- ---------- ---------- ---------- ----------
1/2   0          0          0          1
Port  OrgSpecTx  UnknownTx  CiscoPduTx CiscoTLVTx
----- ---------- ---------- ---------- ----------
1/2   0          0          0          0
Console> (enable)
Configuring Metro Ethernet Connectivity Fault Management

This section describes how to configure Metro Ethernet Connectivity Fault Management (CFM). CFM is part of the Metro Ethernet OAM feature.

These sections describe how to configure Metro Ethernet CFM:

•Understanding How Metro Ethernet Connectivity Fault Management Works

•Connectivity Fault Management Protocols

•Maintenance Domains

•Maintenance Associations

•Maintenance Points

•CFM Configuration Guidelines and Restrictions

•Configuring Metro Ethernet CFM

•Understanding How CFM Works with 802.3ah Link-OAM for AIS-RDI

•Ethernet Alarm Indication Signal

•Ethernet Remote Defect Indication

•ASI and RDI Configuration Guidelines and Restrictions

•Configuring an Alarm Indication Signal

Understanding How Metro Ethernet Connectivity Fault Management Works

Metro Ethernet connects multiple customer sites to form one virtual private network (VPN). A Metro Ethernet network consists of networks from multiple operators that are supported by one service provider. Networks provided and managed by multiple independent service providers have restricted access to each other's equipment. Because of the diversity in these multiple-operator networks, failures must be isolated quickly. As a Layer 2 network, Ethernet must be capable of reporting network faults at Layer 2. IEEE 802.3ah is a point-to-point and per physical wire OAM protocol; it is not a service-aware switch protocol. IEEE 802.1ag CFM is a service level OAM protocol that provides tools for detecting and isolating connectivity failures in the network.

Connectivity Fault Management Protocols

IEEE 802.1ag draft 8.0 Metro Ethernet CFM incorporates several OAM facilities that allow you to manage Metro Ethernet networks, including an Ethernet continuity check, an end-to-end Ethernet traceroute, a Link Trace Message (LTM), a Loopback Message (LBM), and a Loopback Reply (LBR). These Metro Ethernet CFM elements allow you to quickly identify problems in your network.

The following three protocols work together to help you debug Ethernet networks:

•Continuity Check—These heartbeat messages are issued periodically by the maintenance endpoints. They allow maintenance endpoints to detect a loss of service connectivity among themselves. They also allow maintenance endpoints to discover other maintenance endpoints within a domain and allow maintenance intermediate points to discover maintenance endpoints.

•Link Trace—These messages are transmitted by a maintenance endpoint by the request of the administrator to track the path (hop-by-hop) discovery to a destination maintenance endpoint. They allow the transmitting node to discover connectivity data about the path. Link trace messages are nonguaranteed datagram delivery packets that are transmitted similarly to User Datagram Protocol (UDP) traceroute messages.

•Loopback—These messages are transmitted by a maintenance endpoint by the request of the administrator to verify connectivity to a particular maintenance point. Loopback indicates whether the destination is reachable or not; it does not allow hop-by-hop discovery of the path. Loopback messages are similar to ICMP echoes (ping).

Maintenance Domains

Ethernet CFM, within any given service provider network, consists of hierarchical maintenance domains. A maintenance domain is an administrative domain for the purpose of managing and administering a network. A domain is assigned a unique maintenance level (among eight possible levels) by the administrator, which is useful for defining the hierarchical relationship of domains. Maintenance domains may nest or touch but cannot intersect. If the two domains nest, the outer domain must have a higher maintenance level that is contained within it. A maintenance domain is defined by determining which bridge ports are interior to the domain. See Figure 20-2 for an example of a maintenance domain.

Figure 20-2 Ethernet CFM Maintenance Domain

.

Often, three different organizations are involved in a Metro Ethernet service: customers, service providers, and operators. Customers purchase the Ethernet service from service providers. Service providers may use their own networks or the networks of other operators to provide connectivity for the requested service. Customers themselves may be service providers. For example, a customer may be an Internet service provider that sells Internet connectivity.

Nested maintenance domains allow the service provider to contract with one or more operators to provide the Ethernet service to a customer. In a nested domain, each operator has its own maintenance domain, the service provider defines its own domain that is a superset of the operators' domains, and the customer has its own end-to-end domain, which is a superset of the service provider's domain. In this scenario, the involved administering organizations communicate between the maintenance levels of the various nesting domains. For example, the service provider would assign the maintenance levels to the operators.

Maintenance Associations

A maintenance association identifies a service that can be uniquely identified within a maintenance domain. The CFM protocol runs within a particular maintenance association. An MA is a set of Maintenance End Points (MEPs), each configured with the same Maintenance Association ID (MAID) and a maintenance domain level established to verify the integrity of a single service instance. Multiple maintenance associations can exist within each maintenance domain.

Maintenance Points

Any port of a bridge is referred to as a maintenance point. A maintenance point may be classified as a maintenance endpoint, maintenance intermediate point, or transparent point for a maintenance level. Table 20-3 shows the maintenance point classifications.

Table 20-3 Maintenance Point Classifications

Functions

Maintenance Endpoint

Maintenance Intermediate Point

Transparent Point

Initiate CFM messages

Yes

No

No

Respond to loopback and link trace messages

Yes

Yes

No

Catalog continuity-check information received

Yes

Yes

No

Forward CFM messages

No

Yes

Yes

Maintenance endpoints reside at the edge of a maintenance domain, while maintenance intermediate points are internal to the domain. An intermediate point will forward CFM packets (unless it is a loopback or link trace destined for that intermediate point), while endpoints do not forward CFM packets because they must keep them within the domain. The only exception is when an endpoint is also acting as an intermediate point for a higher-level domain, in which case, it will forward the CFM packets as long as they are part of the higher-level domain.

Figure 20-3 shows an example where a service provider is using the networks of two operators to provide service. The service provider maintenance level is shown in blue. The maintenance levels for Operator A and Operator B are shown in orange and violet, respectively. Two special-case maintenance levels are the customer level (shown in green) and the physical layer level (shown in black). The customer level allows the customer to test connectivity (using connectivity checks) and isolate issues (using loopback and link trace). The physical layer level defines the narrowest possible maintenance domain, which is a single link domain.

The designation of maintenance points as maintenance endpoints or maintenance intermediate points for the Operator A (or the Operator B) level is relative to that level only. When these maintenance points are observed relative to the service provider level, maintenance endpoints at the Operator A level translate into either maintenance endpoints or maintenance intermediate points at the service provider level. Maintenance intermediate points at the Operator A level translate into transparent points at the service provider level. Also, the demarcation of maintenance points as maintenance endpoints or maintenance intermediate points within a domain is left to the discretion of the administrator, because these points indicate points of particular relevance for the management of the network.

Figure 20-3 shows an example of how the CFM messages are used across the domains. The customer could use a CFM loopback or link trace to isolate a fault between the maintenance point M, which is on the Customer Premises Equipment (CPE), and the intermediate point L, which is on the user-facing provider edge equipment (U-PE). The link between the CPE and U-PE is a single hop. The customer would know which link has the fault. However, if the fault is between the two intermediate points (the Ls), the customer will need to rely on the service provider to determine between which maintenance (M) or intermediate (L) points that the fault has occurred. The service provider may simply isolate the fault to a specific operator's network and will rely on the operator to isolate the fault to a specific link in its network.

Each different organization (customer, service provider, and operator) can isolate the fault within the organization's maintenance level, without the service provider having to share its network information to the customer, or the operator having to share its network information to the service provider

Figure 20-3 Maintenance Points and Maintenance Domains

CFM Configuration Guidelines and Restrictions

When configuring CFM, follow these guidelines:

•The CFM configuration is allowed only in text configuration mode.

•The Spanning Tree mode should be Multiple Spanning Tree (MST).

•When configuring MEP, follow these steps:

1. Configure the maintenance domain.

2. Configure the maintenance association.

3. Configure the MEPs.

•Configuring a maintenance domain and maintenance association is not mandatory when you configure an MIP.

•You should configure the EtherChannel before enabling CFM on member ports of the EtherChannel.

•Multiple maintenance associations cannot have the same VLAN within a particular domain.

•To avoid a misconfiguration error, use a unique MPID when configuring an MEP and when the customer shifts the local MEP from one port to another port (for the MEP that is down) or from one bridge brain switch to another bridge brain switch (for an MEP that is up).

•When configuring a maintenance association across two domains, a shared VLAN is allowed only if a maintenance association is configured at different levels.

•To optimize on the packet processing time, the sender ID Type-Length-Value (TLV) has been removed from the Continuity Check (CC) packet .The organisational specific TLV which contains the ELMI specific information for the remote MEPs gets populated only, when ELMI is enabled globally. However, all the standard defined TLVs are processed when the CC is being received from the network.

Note CFM domains, maintenance associations and maintenance points can be configured in binary mode or with any other Spanning Tree mode. CFM protocol will be functional only when it is globally enabled in the text configuration mode.

Scalability Data for Connectivity Fault Management and Alarm Indication Signal

•On a Catalyst 6500 series switch with Supervisor Engine 720 that runs software release 8.7(3), when CFM or CFM with MVRP are enabled together on dot1q trunk ports with a 10 second CC interval, the switch supports the following:

–The CCM traffic up to 2000 services or VLANs.

–The Customer Edge (CE) switch supports 2000 customer level MIPs, and 2000 higher-level flood traffic (traffic coming at the level higher than the maximum Maintenance level configured on the switch).

–The Provider Edge (PE) switch up to 200 upward MEPs.

Caution An increase in number of MIPs, provider level MEPs or higher level flood traffic will increase the CPU utilization, and might degrade performance of the system.

•On a Catalyst 6500 series switch with Supervisor Engine 720 that runs software release 8.7(3), when CFM or CFM with MVRP enabled together on the EtherChannel ports (4 ports in a bundle) and with a 10 seconds CC interval, the switch supports the following:

–The CCM traffic up to 1000 services or VLANs.

–1000 customer level MIPs and 1000 higher-level flood traffic (traffic coming at the level higher than the maximum Maintenance level configured on the switch).

–200 Provider Level Up MEPs.

Caution An increase in the number of ports to the EtherChannel or increase in the number of MIPs on a bundled port, will increase the CPU utilization. This may result in CC lifetime expiry for the remote MEPs, and trigger false indication of fault in the network.

•On a Catalyst 6500 series switch with Supervisor Engine 720 that runs software release 8.7(3), when CFM-AIS or CFM-AIS and MVRP are enabled together on dot1q trunk/EtherChannel ports with 10 second CC interval the switch supports the following:

–In the event of link failure, the switch supports CCM traffic for up to 2000 services in the normal state.

–The switch supports 2000 customer level MIPs and 2000 higher-level flood traffic (traffic coming at the level higher than the maximum Maintenance level configured.

–Up to 200 Provider level Up MEPs.

Note In the event of link failure, a CPU spike occurs at every one minute time interval because of the AIS timer spread logic.

Caution An increase in the number of MIPs, provider level MEPs or higher level flood traffic will increase the CPU utilization and may degrade system performance.

Note On a Catalyst 6500 series switch that runs software release 8.7(3), when an AIS detects the link fault condition occurs the configured number of AIS PDUs will be sent (default 5) at 1 second transmission interval for each of the affected VLAN on the failed trunk. Then the AIS transmission period is changed to 1 minute automatically in the software (timer spread logic). This will increase the CPU utilization at every 1 minute until the fault condition is cleared, which is an expected behavior.

Configuring Metro Ethernet CFM

Note For complete syntax and usage information for the commands that are used in this section, refer to the Catalyst 6500 Series Switch Command Reference Software Release 8.x publication.

This section describes how to configure Metro Ethernet CFM:

•Enabling or Disabling Metro Ethernet CFM

•Configuring Metro Ethernet CFM Domains

•Configuring a Metro Ethernet CFM Maintenance Association

•Configuring CFM on a Port as a Maintenance Point

•Configuring Continuity-Check Protocol Parameters

•Configuring Ethernet CFM traceroute Protocol Parameters

•Configuring a System CAM Entry

•Displaying Metro Ethernet CFM Domains

•Displaying CFM Maintenance Association Information

•Displaying Metro Ethernet CFM Maintenance Point Information

•Displaying the Metro Ethernet CFM Status

•Displaying Metro Ethernet CFM Statistics

•Displaying Metro Ethernet CFM Errors

•Displaying the Metro Ethernet CFM traceroute Database

•Clearing a Metro Ethernet CFM

•Clearing a Metro Ethernet CFM Maintenance Association

•Clearing a Metro Ethernet CFM Maintenance Point

•Clearing the MAC Configuration for Maintenance End Points

•Clearing the Ethernet CFM traceroute Database

Enabling or Disabling Metro Ethernet CFM

To enable or disable Metro Ethernet CFM globally on a switch, perform this task in privileged mode:

Task

Command

Enable or disable Metro Ethernet CFM globally on a switch.

set ethernet-cfm {disable | enable}

This example shows how to enable Metro Ethernet CFM globally on a switch:
Console> (enable) set ethernet-cfm enable
Ethernet CFM enabled.
Console> (enable)
Configuring Metro Ethernet CFM Domains

To create a maintenance domain and configure the maintenance level, perform this task in privileged mode:

Task

Command

Configure a Metro Ethernet CFM domain.

set ethernet-cfm domain domain name level level

This example shows how to configure a maintenance domain with domain name customerxy Domain and at level 6:
Console> (enable) set ethernet-cfm domain customerXYDomain level 6
Created a Domain customerXYDomain at level 6.
Console> (enable)
Configuring a Metro Ethernet CFM Maintenance Association

To configure a maintenance association within the maintenance domain, perform this task in privileged mode:

Task

Command

Configure a Metro Ethernet CFM maintenance association within the maintenance domain.

set ethernet-cfm maintenance-association ma-name-fmt fmt name | value domain domain-name vlan vlan_id [direction up | down]

This example shows how to configure a maintenance association in a domain with a VLAN ID:
Console> (enable) set ethernet-cfm maintenance-association ma-name-fmt text customerXMA 
domain customerXYDomain vlan 1 direction up
Maintenance Association created successfully for vlan 1 in domain customerXYDomain 
Console> (enable) 
Configuring CFM on a Port as a Maintenance Point

To enable or disable CFM on a port and to configure a port as a Maintenance End Point (MEP) and Maintenance Intermediate Point (MIP) for a specific maintenance level and VLAN, perform this task in privileged mode:

Task

Command

Step 1

Configure Ethernet CFM on a specific module and port or set the port to transparent mode.

set port ethernet-cfm mod/port {enable | disable | transparent}

Step 2

Configure a port as an MEP and configure an MPID for a specific maintenance level.

set port ethernet-cfm mod/port mep mpid mpid domain domain-name vlan vlan-id

Step 3

Configure an MIP for a specific domain or a specific maintenance level.

set port ethernet-cfm mod/port mip level level vlan vlan-id

This example shows how to initialize an MEP at module 1, port 1, for VLAN 10:
Console> (enable) set port ethernet-cfm 1/1 mep mpid 1 domain XYZ vlan 10
MEP is configured for port  1/1 with MPID 1 in domain XYZ for vlan10.
Console> (enable)
This example shows how to initialize an MIP at module 1, port 1 at MIP level 5:
Console> (enable) set port ethernet-cfm 1/1 mip level 5 vlan 10
MIP is configured for port  1/1 at level 5 for vlan(s)10.
Console> (enable)
Configuring Continuity-Check Protocol Parameters

To configure continuity-check message attributes for a specific level of the local Maintenance End Points (MEPs), perform this task in privileged mode:

Task

Command

Configure continuity-check message attributes for a specific level of MEPs.

set ethernet-cfm continuity-check level level vlan vlans interval interval-value [loss-threshold threshold]

This example shows how to configure continuity-check message attributes for level 5, VLAN ID 11 at an interval of 1 minute and a loss threshold of three messages:
Console> (enable) set ethernet-cfm continuity-check level 5 vlan 11 interval 2
loss-threshold 3
CC Attributes set for level(s)5
Console> (enable)
This example shows how to enable the continuity-check protocol for a particular maintenance association or VLAN at a specific level:
Console> (enable) set ethernet-cfm continuity-check level 4 vlan 100
Succesfully enabled CC for level 4 for vlan(s) 100.
Console> (enable)
Configuring Ethernet CFM traceroute Protocol Parameters

To enable or disable caching of Ethernet Connectivity Fault Management (CFM) data entered using traceroute messages, perform this task in priviliged mode:

Task

Command

Step 1

Enable or disable caching of Ethernet CFM data.

set ethernet-cfm traceroute-database [enable | disable]

Step 2

Set the size of the traceroute database. The size varies from 1 to 4095 entries.

set ethernet-cfm traceroute-database size size

Step 3

Configure the time for retaining the entry in the traceroute database. This time varies from 1 to 2880 minutes.

set ethernet-cfm traceroute-database hold-time hold_time

This example shows how to enable the caching of the Ethernet CFM data:
Console> (enable) set ethernet-cfm traceroute-database enable
Ethernet TRDB Cache enabled
Console> (enable)
This example shows how to set the hold time to 300 in the traceroute database:
Console> (enable) set ethernet-cfm traceroute-database hold-time 300
Ethernet TRDB hold-time is set to 300 minutes
Console> (enable)
This example shows how to set the size of the traceroute database to 300:
Console> (enable) set ethernet-cfm traceroute-database size 300
Ethernet TRDB size is set to 300.
Console> (enable)
Configuring a System CAM Entry

To configure a system CAM entry for a specified module, port number, and a specific VLAN or VLANs, perform this task in priviledged mode:

Task

Command

Configure a system CAM entry for a specified module, port number, and VLAN.

set ethernet-cfm port-mac-enable mNo/pNo vlan vlans

This example shows how to configure a system CAM entry for module 6, port 2, and VLAN 10:
Console>(enable) set ethernet-cfm port-mac-enable 6/2 vlan 10
CAM table updated with entries for port(s) 6/2 vlan(s) 10
Console>(enable)
Note For LTMs/LBMs to be successful with DOWN MEPs, you should configure the system CAM entry for that VLAN on the DOWN MEP port.

Displaying Metro Ethernet CFM Domains

To display all the configured CFM domains, perform this task in privileged mode:

Task

Command

Display the domains configured for a switch.

show ethernet-cfm domain [domain_name] detail

This example shows how to display information on all the domains on the switch:
Console> (enable)
Console> (enable) show ethernet-cfm domain 
----------------------------------------------------
Domain Name                Index   Level   Services 
-----------------------------------------------------
dom3                           1     3     2000    
dom6                           2     6     0       
dom7                           3     7     0
Console> (enable)
This example shows how to display information on only the sjlabf1 domain:
Console> (enable) show ethernet-cfm domain customerXYZ detail 
* - indicates vlan does not exist
$ - indicates vlan is suspended
Domain ID : 2
Domain Name : customerXYZ
Level : 4
Total Services : 1
Services : 
Vlan Direction CC-Enable shortMAName
100 Up Y CUST-MA-10
Console> (enable)
Displaying CFM Maintenance Association Information

To display all the maintenance association information, perform this task in privileged mode:

Task

Command

Display all the maintenance association information.

show ethernet-cfm maintenance-association
Console> (enable) show ethernet-cfm maintenance-association 
Maintenance Association Details : 
* - indicates vlan does not exist
$ - indicates vlan is suspended
------------------------------------------------------------------------------------------
Vlan  Dir  Domain                Lvl MA      MA-Name     CC-    Loss  CC-    AIS   
           Name                     Format              Intv   Thres Enable state 
------------------------------------------------------------------------------------------
2000  up   dom3                   3 text    vlan2000    10 sec   3   TRUE   TRUE 
2001  up   dom3                   3 text    vlan2001    10 sec   3   TRUE   TRUE 
2002  up   dom3                   3 text    vlan2002    10 sec   3   TRUE   TRUE 
2003  up   dom3                   3 text    vlan2003    10 sec   3   TRUE   TRUE 
2004  up   dom3                   3 text    vlan2004    10 sec   3   TRUE   TRUE 
2005  up   dom3                   3 text    vlan2005    10 sec   3   TRUE   TRUE 
2006  up   dom3                   3 text    vlan2006    10 sec   3   TRUE   TRUE 
2007  up   dom3                   3 text    vlan2007    10 sec   3   TRUE   TRUE 
2008  up   dom3                   3 text    vlan2008    10 sec   3   TRUE   TRUE 
2009  up   dom3                   3 text    vlan2009    10 sec   3   TRUE   TRUE 
2010  up   dom3                   3 text    vlan2010    10 sec   3   TRUE   TRUE
Console> (enable)
Displaying Metro Ethernet CFM Maintenance Point Information

To display all the local or remote maintenance points, perform this task in privileged mode:

Task

Command

Display all local or remote maintenance points.

show ethernet-cfm maintenance-point {local | remote}

This example shows how to display local MEPs/MIPs configured on the switch:
Console> (enable) show ethernet-cfm maintenance-point local
* - indicates vlan does not exist
$ - indicates vlan is suspended
@ - indicates vlan is not allowed on this port
LOCAL MEPS:
-------------------------------------------------
Port MPID Dir    Level Domain CC   Vlan MA-name
                        Name stat
--------------------------------------------------
3/20 200 DOWN  4      xyz     1      10     MA-10
Total Local MEP's = 1 
LOCAL MIPS:
----------------------
Port Level Vlans
----------------------
3/20   5    10
Total Local MIP's = 1
Console> (enable)
This example shows how to display remote maintenance points:
Console> (enable) show ethernet-cfm maintenance-point remote
* - indicates port is a channel port
-----------------------------------------------------
MPID Port Vlan Level Mac-Addr Domain Name MA Name RDI
-----------------------------------------------------
200 3/14 10 4 00-30-19-c0-a0-a5 cust-1     MA-10   n
200 3/14 20 4 00-30-19-c0-a0-a5 cust-1     MA-20   n
200 3/14 30 4 00-30-19-c0-a0-a5 cust-1     MA-30   n
200 3/14 40 4 00-30-19-c0-a0-a5 cust-1     MA-40   n
200 3/14 50 4 00-30-19-c0-a0-a5 cust-1     MA-50   n
Console>
Displaying the Metro Ethernet CFM Status

To display the global CFM and AIS status, the maximum configured maintenance level, and CFM MAC addresses, perform this task in privileged mode:

Task

Command

Display the global CFM and AIS status and the maximum configured maintenance level.

show ethernet-cfm status

This example shows how to display the CFM and AIS status:
Console> (enable) show ethernet-cfm status
Ethernet CFM is enabled on this switch.
Max configured level is 4.
Bridge Brain Mac Address is 00-13-5f-1f-67-3b.
CFM CC Multicast Address is 01-80-c2-00-00-30.
CFM LTM Multicast Address is 01-80-c2-00-00-38.
CFM AIS is enabled.
CFM AIS Default Transmission Interval is 1 sec.
CFM AIS configured level is 8.
CFM AIS PDUs to be transmitted at 1 sec Interval is 8.
Console> (enable) 
Displaying Metro Ethernet CFM Statistics

To display the CFM packet statistics, such as the Continuity Check Messages (CCMs) sent, CCMs received with out-of-order transaction IDs, Loopback Replies (LBRs), or Linktrace Replies (LTRs), perform this task in privileged mode:

Task

Command

Display continuity check packet statistics.

show ethernet-cfm statistics [mpid mpid]

This example shows how to display the CFM statistics:
SW8> (enable) 
SW8> (enable) 
SW8> (enable) show ethernet-cfm statistics 
* - indicates vlan does not exist
$ - indicates vlan is suspended
@ - indicates vlan is not allowed on this port
--------------------------------------------------------------------------------
MPID  Port   Vlan   CCM    CCM Seq  LTR        LBR   LBR     LBR     LBR
                    Sent   Error    unexpected sent  seq-err recvd   bad-msdu
--------------------------------------------------------------------------------
2001  3/1    2000   1407   20       0          5     0       0       0    
2002  3/1    2001   1407   21       0          0     0       0       0    
2003  3/1    2002   1407   15       0          0     0       0       0    
2004  3/1    2003   1407   36       0          0     0       0       0    
2005  3/1    2004   1406   32       0          0     0       0       0    
2006  3/1    2005   1406   33       0          0     0       0       0    
2007  3/1    2006   1406   23       0          0     0       0       0    
2008  3/1    2007   1406   36       0          0     0       0       0    
2009  3/1    2008   1406   18       0          0     0       0       0    
2010  3/1    2009   1405   34       0          0     0       0       0    
2011  3/1    2010   1407   22       0          0     0       0       0    
2012  3/1    2011   1406   36       0          0     0       0       0    
2013  3/1    2012   1407   20       0          0     0       0       0    
2014  3/1    2013   1405   33       0          0     0       0       0    
Console> (enable)
Displaying Metro Ethernet CFM Errors

To display the CFM continuity check and AIS error conditions logged since the last reload, perform this task in privileged mode:

Task

Command

Displays CFM and AIS error condition.

show ethernet-cfm errors {domain domain-name}

This example shows how to display Ethernet CFM errors:
Console> (enable) show ethernet-cfm errors
------------------------------------------------------------------------------------------
Lvl Vlan MPID Remote-MAC        Reason           MA-Name              Domain-Name  
-----------------------------------------------------------------------------------------
6   2816 8190 00-0b-45-a8-c4-3b AIS-Error        vlan2816             dom6                 
6   2816 817  00-11-bc-99-af-fb Lifetime-Expiry  vlan2816             dom6                 
6   2560 8190 00-0b-45-a8-c4-3b AIS-Error        vlan2560             dom6                 
6   2560 561  00-11-bc-99-af-fb Lifetime-Expiry  vlan2560             dom6                 
6   2304 8190 00-0b-45-a8-c4-3b AIS-Error        vlan2304             dom6                 
6   2304 305  00-11-bc-99-af-fb Lifetime-Expiry  vlan2304             dom6                 
6   2048 8190 00-0b-45-a8-c4-3b AIS-Error        vlan2048             dom6                 
6   2048 49   00-11-bc-99-af-fb Lifetime-Expiry  vlan2048             dom6                 
6   3328 1329 00-11-bc-99-af-fb Lifetime-Expiry  vlan3328             dom6                 
6   3072 1073 00-11-bc-99-af-fb Lifetime-Expiry  vlan3072             dom6                 
6   3840 1841 00-11-bc-99-af-fb Lifetime-Expiry  vlan3840             dom6                 
6   3584 1585 00-11-bc-99-af-fb Lifetime-Expiry  vlan3584             dom6                 
6   2817 8190 00-0b-45-a8-c4-3b AIS-Error        vlan2817             dom6                 
6   2817 818  00-11-bc-99-af-fb Lifetime-Expiry  vlan2817             dom6
Console> (enable)
Displaying the Metro Ethernet CFM traceroute Database

To display the contents of the traceroute database, perform this task in priviledged mode:

Task

Command

Display the contents of the traceroute database.

show ethernet-cfm traceroute-database [status | size | hold time]

This example shows how to display the contents of the traceroute database:
Console> (enable) show ethernet-cfm traceroute-database
Traceroute to 00-50-3e-78-fb-fb on Domain dom3, Level 3,
Vlan 2000 issued at Wed Aug 12 2009, 03:12:17
B = Intermediary Bridge
! = Target Destination
* = Per hop Timeout
--------------------------------------------------------------------------------
                             MAC          Ingress      Ingr Action  Relay Action
  Hops   Host             Forwarded       Egress       Egr Action   Prev Hop
--------------------------------------------------------------------------------
B  1  y69              00-12-da-66-76-3b     4/13        IngOK         RlyMPDB
                             Forwarded                         00-0f-f8-8d-cb-fb
B  2  y72              00-0f-f8-8a-d0-7b                               RlyMPDB
                             Forwarded        3/5        EgrOK 00-12-da-66-76-3b
!  3  y90              00-50-3e-78-fb-fb                                RlyHit
                         Not Forwarded                         00-0f-f8-8a-d0-7b
Clearing a Metro Ethernet CFM

To clear CFM parameters, perform one of these tasks in privileged mode:

Task

Command

Clear a Metro Ethernet CFM domain.

clear ethernet-cfm domain domain_name level level.

Clear a Metro Ethernet CFM CC information.

clear ethernet-cfm continuity-check level level vlan vlan.

This example shows how to clear an Ethernet CFM CC level on a VLAN:
Console> (enable) clear ethernet-cfm continuity-check level 3 vlan 1
cc attributes are cleared for level(s) 3
Console> (enable)
This example shows how to clear an Ethernet CFM domain:
Console> (enable) clear ethernet-cfm domain test level 1
Domain test is cleared from level 1.
Console> (enable)
Clearing a Metro Ethernet CFM Maintenance Association

To clear the maintenance association configured within the maintenance domain, perform one of these tasks in priviledged mode:

Task

Command

Clear the CFM configured within a maintenance domain.

clear ethernet-cfm maintenance-association domain domain-name

Clear the maintenance association name used to construct the Maintenance Association ID (MAID) to be used in CFM frames.

clear ethernet-cfm maintenance-association ma-name-fmt ma_fmt ma-name domain domain-name

This example shows how to clear the maintenance association, customerXYA in customerXYADomain:
Console> (enable) clear ethernet-cfm maintenance-association ma-name-fmt text customerXYA
domain customerXYADomain
Maintenance Association customerXYA cleared from domain customerXYADomain.
Console> (enable)
Clearing a Metro Ethernet CFM Maintenance Point

To clear the Maintenance End Points (MEPs) or Maintenance Intermediate Points (MIPs) for a specific port, perform one of these tasks in priviledged mode:

Task

Command

Clear the CFM configured on a specific module/port.

clear port ethernet-cfm mod/port

Clear the MEP configuration at a maintenance level and clear the specified VLAN on a specific port.

Note MEP level values range from 0 to 7.

Note VLAN values range from 1 to 4094.

clear port ethernet-cfm mod/port mep [domain domain-name | vlan vlan]

Clear the MIP configuration.

clear port ethernet-cfm mod/port mip [level level vlan vlans]

This example shows how to clear the MEP configuration for module 2, port 1 for a particular domain customerxyz and VLAN 10:
Console> (enable) clear port ethernet-cfm 2/1 mep domain customerxyz vlan 10.
MEP config on Port 2/1 is cleared.
Console> (enable)
This example shows how to clear the MIP configuration for module 2, port 1:
Console> (enable) clear port ethernet-cfm 2/1 mip
MIP config on Port 6/1 is cleared.
Console> (enable)
Clearing the MAC Configuration for Maintenance End Points

To clear the port MAC configuration for Maintenance End Points (MEPs) that are down in a particular module and port number of a VLAN, perform one of these tasks in priviledged mode:

Task

Command

Clear the MAC configuration.

clear ethernet-cfm port-mac-enable

Clear the MAC configuration for MEPs in a specific module and port number of a VLAN.

clear ethernet-cfm port-mac-enable mNo/pNo vlan vlans

This example shows how to clear the port MAC configuration for MEPs that are down in module 3, port 14, and VLAN ID 10:
Console> (enable) clear ethernet-cfm port-mac-enable 3/14 vlan 10
Successfully deleted entries for port(s) 3/14 vlan(s) 10.
Console> (enable)
Clearing the Ethernet CFM traceroute Database

To clear the contents of the traceroute database, perform one of these tasks in privileged mode:

Task

Command

Clear the CFM traceroute database information.

clear ethernet-cfm traceroute-database

Clear the hold time and the size of the traceroute database.

clear ethernet-cfm traceroute-database {hold-time | size}

This example shows how to clear the contents of the traceroute database:
Console> (enable) clear ethernet-cfm traceroute-database
Traceroute database entries cleared.
Console> (enable)
This example shows how to clear the hold time of the traceroute database:
Console> (enable) clear ethernet-cfm traceroute-database hold-time
Ethernet TRDB Hold time is cleared and set to default.
Console> (enable)
This example shows how to clear the size of the traceroute database:
Console> (enable) clear ethernet-cfm traceroute-database size
Ethernet TRDB Size cleared and set to default.
Console> (enable)
Configuring the Alarm Indication Signal

This section describes how to configure the Alarm Indication Signal (AIS) and the Remote Defect Indication (RDI), which are fault management functions of the Connectivity Fault Management (CFM) protocol. The CFM module works with 802.3ah Link-OAM to support these new extensions.

Note AIS-RDI requires Catalyst 6500 series switch software release 8.7(3) or later.

These sections describe how to configure the AIS:

•Understanding How CFM Works with 802.3ah Link-OAM for AIS-RDI

•Ethernet Alarm Indication Signal

•Ethernet Remote Defect Indication

•ASI and RDI Configuration Guidelines and Restrictions

•Configuring an Alarm Indication Signal

•Ethernet Remote Defect Indication

Understanding How CFM Works with 802.3ah Link-OAM for AIS-RDI

The Ethernet Alarm Indication function (ETH-AIS) and the Ethernet Remote Defect Indication (ETH-RDI) are new functional extensions to Metro Ethernet Connectivity Fault Management (CFM). The ETH-AIS is a standard defined by ITU Y.1731 and the ETH-RDI is part of IEEE 802.1ag. AIS-RDI works together to help reduce the management complexity of large SPAN networks and multiple constituent networks that belong to separate organizations.

Ethernet Alarm Indication Signal

ETH-AIS is an important component of Ethernet-OAM. ETH-AIS is used to suppress alarms after defect conditions are detected at the server (sub) layer.

Note The server (sub) layer is the virtual MEP layer. The IEEE 802.3ah OAM can detect a fault condition.

AIS can differentiate between the faults at the customer level and at the provider level. The AIS serves the following purposes:

1. Notifies the faults from the lower to the upper maintenance domain levels by potentially allowing longer continuity check intervals to be used in the upper levels.

2. Suppresses the multiple redundant alarms by notifying the upper level that the fault detected originates from a lower level.

3. Enables the customer to monitor service availability.

The main functions of the AIS module is as follows:

•To generate the AIS protocol data units (PDUs) upon a signal fault condition that has occurred due to an AIS defect condition.

•To receive to process AIS PDUs, and to maintain an expiry timer.

•To inform the continuity check module about the remote MEP connectivity path failure. The CCM module then generates the Continuity Check Messages (CCMs) with an RDI flag set in the periodic CCMs until the error condition is cleared.

•To signal the configuration management application to suppress alarms.

The CFM works with 802.3ah Finite State Machine (FSM) and has two states:

•SEND_ANY—The 802.3ah OAM link is up and operational. In this state, AIS PDUs are not transmitted.

•AIS—The 802.3ah OAM link has detected traffic that results in a fault condition. The AIS module remains in a sticky state until the OAM link explicitly sends an operational trigger to clear the sticky state. CFM periodically sends AIS PDUs until the defect condition is cleared.

The Server MEP sends the AIS frames with the ETH-AIS information that can be enabled or disabled on a MEP (or on a Server MEP). These frames are issued at the client's maintenance level by a MEP that includes a Server MEP when a defect condition is detected. The defect conditions may include the following:

•The signal fail conditions when an Ethernet Continuity Check (ETH-CC) is enabled.

•The AIS condition when an Ethernet Continuity Check (ETH-CC) is disabled.

Note A Server MEP represents both the server layer termination function and Server/Ethernet adaptation function. In the Cisco IOS software, the Link OAM and Interface/Line Protocol state act as Server MEPs.

Timer Spread Design Logic and Guidelines:

•The AIS transmission interval has been hard coded to 1 second and it can be changed to1 minute dynamically, after the configured number of AIS PDUs are transmitted (default 5).

•The AIS timer logic is designed such that depending upon the global AIS PDU transmission count configured on the switch, you can determine the number of AIS PDUs which will be sent at 1 second interval periodically, when the link failure is detected by the server MEP. The default AIS packet count is set to 5.

•When the defect condition is cleared, the Server MEP sends another set of AIS PDUs (global AIS PDU tx_count configured on the switch) with 1 second interval. So, that the subsequent remote MEPs comes out of the AIS defect condition faster.

•Both the Server MEP and the Local MEP follows the same timer logic to transmit the AIS further in the network.

Ethernet Remote Defect Indication

A MEP uses an ETH-RDI to communicate to its peer MEPs that a defect condition has occurred. A MEP uses an ETH-RDI only when an Ethernet Continuity-Check transmission is enabled.

A MEP that is in a defect condition transmits frames with the ETH-RDI information. When a MEP receives frames with ETH-RDI information, it determines that its peer MEP has encountered a defect condition. However, in a multipoint Ethernet connection, when a MEP receives frames with ETH-RDI information, it cannot determine which peer MEP has a fault condition.

The Ethernet Remote Defect Indication has two management applications:

1. Single-ended fault management—The receiving MEP detects an RDI, which indicates that some of its remote MEPs have failed. When an RDI is not present, it indicates the absence of defects in all the MEPs in a network. This RDI mechanism helps the administrator in the fault management activity on a per service basis.

2. Contribution to far-end performance monitoring—An ETH-RDI indicates that there was a defect condition in the far end of a network. This information is used as an input to the performance monitoring process.

ASI and RDI Configuration Guidelines and Restrictions

When configuring ASI and RDI, follow these configuration guidelines and restrictions:

•You must enable CFM and AIS globally on a switch.

•You must enable CFM on the port before you enable AIS.

•You must enable the Link-OAM on the Server MEP port so that the Link OAM-CFM can function.

•If you explicitly disable CFM globally but the AIS remains enabled, the AIS configuration displays in the configuration. However, the AIS is not functional.

•All the AIS attributes (level, interval, enable/disable, alarm suppression) relate to the MA. The MEP inherits these attributes from the MA. You must create an MA so that you can set any of the AIS parameters.

•You must create a MA for all the VLANs to configure the AIS paramenters for a MA. The AIS configuration is provided for the Server MEP and all of the CFM entities for the local MEPs.

•The software does not support SNMP trap generation to indicate the receipt or transmission of the AIS. A syslog message will be generated to notify the event to the administrator. Because Y.1731 does not define a MIB, this would require either a new MIB, or an extension to that defined by 802.1ag.

•CFM will not generate an SNMP trap for the Server MEP AIS defect condition. Only the syslog messages will be generated to notify the administrator.

•When the CC lifetime expiry occurs for the remote MEP because of a fault in the network, and if the local MEP is already in an AIS condition with alarm-suppression enabled (the default is enable), the trap will be suppressed for that remote MEP. You must explicitly disable alarm suppression for the lifetime expiry trap to be generated.

•For EtherChannel and Server MEP configurations, the AIS is suppressed until the last port of the EtherChannel goes down. The AIS will be generated only when the last port of the EtherChannel leaves the aggregation port. When one of the channel port becomes operational, the AIS condition is cleared.

Configuring an Alarm Indication Signal

This section describes how to configure the Alarm Indication Signal:

•Enabling or Disabling a Metro Ethernet CFM Alarm Indication Signal

•Configuring Continuity-Check Protocol AIS Parameters

•Configuring the Metro Ethernet CFM Alarm Indication Signal Transmission Level

•Configuring the Metro Ethernet CFM Alarm Indication Signal PDUs Transmission Count

•Configuring a CFM AIS on an Individual Port

•Displaying CFM AIS/RDI Errors

Note For complete syntax and usage information for the commands that are used in this section, refer to the Catalyst 6500 Series Switch Command Reference Software Release 8.x publication.

Enabling or Disabling a Metro Ethernet CFM Alarm Indication Signal

To enable or disable a CFM AIS globally on a switch, perform this task in privileged mode:

Task

Command

Enable or disable a CFM AIS globally on a switch.

set ethernet-cfm ais {disable | enable}

This example shows how to enable a CFM AIS globally on a switch:
Console> (enable) set ethernet-cfm ais disable
Link-Status AIS feature is already disabled on the switch.
Console> (enable)

Configuring Continuity-Check Protocol AIS Parameters

To configure the AIS attributes for all MEPs that belong to a specific MA or service, perform this task in privileged mode:

Task

Command

Step 1

Enable or disable AIS generation to specify the AIS level and VLAN for all MEPs of an MA.

set ethernet-cfm continuity-check level levels vlan vlans ais {enable | disable}

Step 2

Set the maintenance level of all MEPs of an MA. Valid values are from 0 to 7.

set ethernet-cfm continuity-check level levels vlan vlans ais level level

Step 3

Enable or disable alarm suppression for all MEPs of an MA.

set ethernet-cfm continuity-check level levels vlan vlans ais alarm-suppress {enable | disable}

This example shows how to enable AIS generation for level 0 and VLAN ID 1000:
Console> (enable) set ethernet-cfm continuity-check level 0 vlan 1000 ais enable
CC Attributes set for level(s) 0.
Console> (enable)
This example shows how to disable AIS generation for level 0 and VLAN ID 1000:
Console> (enable) set ethernet-cfm continuity-check level 0 vlan 1000 ais disable 
CC Attributes set for level(s) 0.
Console> (enable)
This example shows how to enable alarm suppression for level 0 and VLAN ID 1000:
Console> (enable) set ethernet-cfm continuity-check level 0 vlan 1000 ais alarm-suppress 
enable 
CC Attributes set for level(s) 0.
Console> (enable)
This example shows how to configure the AIS level for the MEPs:
Console> (enable) set ethernet-cfm continuity-check level 5 vlan 5 ais level 6
CC Attributes set for vlan(s) 5 on level 5.
Console> (enable)

Configuring the Metro Ethernet CFM Alarm Indication Signal Transmission Level

To configure the CFM AIS transmission level globally on a switch, which will be inherited by all the server MEPs to transmit AIS PDUs when a fault is detected, perform this task in privileged mode:

Task

Command

Configure the CFM AIS transmission level globally on a switch.

set ethernet-cfm ais level {level | default}

This example shows how to configure the CFM AIS level globally on a switch:
Console> (enable) set ethernet-cfm ais level 4
Link-Status AIS transmission level configured to 4 on the switch.
Console> (enable)

Configuring the Metro Ethernet CFM Alarm Indication Signal PDUs Transmission Count

To configure the CFM Alarm Indication Signal PDUs transmission count on a switch, perform this task in privileged mode:

Task

Command

Configure AIS PDU transmission count globally on a switch. Valid values are from 3 to10. The default is 5.

set ethernet-cfm ais tx-count count

This example shows how to configure AIS PDUs transmission count globally on a switch:
Console> (enable) set ethernet-cfm ais tx-count 10
AIS PDU transmission count set to 10 on the switch.
Console> (enable)
Configuring a CFM AIS on an Individual Port

To enable or disable AIS on a port, and to configure an AIS parameter of the port, perform this task in privileged mode:

Task

Command

Enable or disable AIS on a port to specify the AIS server MEP configuration and the AIS generation on a switch port.

set port ethernet-cfm mod/port ais {enable | disable}

This example shows how to enable a CFM AIS on a port:
Console > (enable) set port ethernet-cfm 2/2 ais enable
Server MEP AIS generation is enabled on the port 2/2.
Console > (enable)
Displaying CFM AIS/RDI Errors

To display the CFM and AIS/RDI error conditions logged since the last reload, perform this task in privileged mode:

Task

Command

Step 1

Display the CFM error conditions for maintenance points that have a specific maintenance level.

show ethernet-cfm errors [level level]

Step 1

Display the CFM error conditions for maintenance points and to specify the name of the device domain.

show ethernet-cfm errors [domain domain_name]

This example shows how to display AIS and RDI errors for the local maintenance points:
Console> (enable) show ethernet-cfm errors
------------------------------------------------------------------------------------------
Lvl Vlan MPID Remote-MAC        Reason           MA-Name              Domain-Name  
------------------------------------------------------------------------------------------
0   2010 8190 00-14-f2-31-c1-08 AIS-Errror       vlan2010             dom0 
6 2000 8190 00-0b-45-a9-2c-fb RDI-Error vlan2000 dom6

Configuring the Ethernet Local Management Interface

These sections describe how to configure the Ethernet Local Managagement Interface (ELMI):

•Understanding How ELMI Works

•Ethernet Local Management Protocols

•Configuring ELMI

Understanding How ELMI Works

ELMI is an Ethernet layer operation, administration, and management (OAM) protocol. It provides information that enables autoconfiguration of Customer Edge (CE) devices and provides the status of Ethernet virtual connections (EVCs) for Metro Ethernet Networks (MENs). ELMI notifies a CE device of the operating state of an EVC when an EVC is added or deleted to the interfaces. ELMI also communicates the attributes of an EVC and a user-network interface (UNI) to a CE device.

Ethernet Local Management Protocols

The ELMI protocols are as follows:

•Ethernet Virtual Connections (EVC)—An EVC can be a port level point-to-point or multipoint-to-multipoint Layer 2 circuit. The CE device can use the EVC status to find an alternative path to the service provider network, or in some cases, fall back to a backup path over Ethernet or another alternative service such as Frame Relay or Asynchronous Transfer Mode (ATM).

•Ethernet Local Management Interface (ELMI)—ELMI is an Ethernet layer OAM protocol between a Customer Edge (CE) device and the Provider Edge (PE) in a MEN. It provides information that enables service providers to autoconfigure CE devices with service parameters and parameter changes from a user provider edge (UPE) device.

In a MEN, the EVC status is determined by the OAM protocol. In the Catalyst operating system, ELMI relies on CFM to provide an end-to-end status of the EVC across CFM domains (PE device) in MEN and updates the CE device through ELMI.

Note The Catalyst operating system supports ELMI only in the PE mode.

•User Network Interface (UNI)—UNI is the physical demarcation point between the service provider and the customer. Its attributes, which are similar to the UNI identifier and UNI type, are defined on the PE port that connects to the CE device. The ELMI protocol runs on the UNI interface.

ELMI does the following:

•Notifies the CE when an EVC is added.

•Notifies the CE when an EVC is deleted.

•Notifies the CE of the availability of a configured EVC (Active, Not Active, or Partially Active).

•Communicates UNI and EVC attributes to the CE.

Configuring ELMI

Figure 20-4 shows an example of ELMI that is configured in a multipoint EVC network.

Figure 20-4

ELMI Configured in a Multipoint EVC Network

These guidelines apply to Figure 20-4:

•PE1, PE2, and PE3 are PE switches in the MEN.

Note•PE1 is a WS-C6509 chassis switch with a WS-SUP720-3BXL as the supervisor engine that runs Catalyst software release 8.7(2).

•PE2 is a WS-C6509 chassis switch with a WS-SUP32-10GE-3B supervisor engine that runs Catalyst software release 8.7(2).

•PE3 is a WS-C6513 chassis switch with a WS-SUP720-3BXL supervisor engine that runs Catalyst software release 8.7(2).

•PE1, PE2, and PE3 switches have VLANs 10 and 250 (switch VLANs) configured as CFM VLANs.

•The ELMI protocol runs between the PE1 switch and CE1-Cisco Internet Switch and Router (ISR) 3845.

•The remote MEPs Continuity Check Database (CCDB) cataloging occurs on all 3 PE switches for VLANs 10 and 250.

•All connected ports are 802.1Q trunk ports that carry the above VLANs.

•Before you can enable and have a working ELMI between PE1-Supervisor Engine 720 WS-C6509 and CE1-ISR 3845, CFM MEPs that are up must exist on edge switch PE1 (port 4/4). Figure 20-4 the CFM MEP that is up also exists on edge switches PE2 and PE3 on ports 11/38 and 4/5, respectively. In the figure, the configuration steps are required so that the PE switch for the ELMI protocol can be enabled and the ELMI frames can be exchanged between the PE1 switch and CE1-ISR3845.

Note You must enable ELMI on the switch globally.

•Enable ELMI on the PE1 port 4/4 that connects to the CE device.

•Multipoint EVCs (EVC 250 and EVC 10 that have a Uni-count of 3 for UNI-A, UNI-B, and UNI-C) are configured on a PE switch that is mapped to VLANs 10 and 250 on which CFM inward MEPs exist. The EVCs are also mapped to CE VLANs 10 and 250.

•The UNI ID and UNI type is configured on the PE edge. Port 4/4 connects to the ISR CE switch. Port 4/4 is a dot1q trunk port and the UNI service bundling type configured on the port is multiplex. The EVCs are mapped onto the PE port 4/4 that connects to the CE1 ISR3845.

•The ELMI frames between PE1 and CE1- ISR3845 are exchanged once you enable ELMI on the CE1-ISR3845 and the ELMI protocol is up between PE1 and CE1-ISR3845.

•The ELMI protocol carries the following information in ELMI frames from the PE to the CE using the ELMI status messages:

–Notification to the CE about the status of an EVC.

–Communication of UNI and EVC attributes to the CE.

Configuring ELMI on the Switch

This section describes how to configure ELMI:

•Enabling or Disabling ELMI

•Enabling or Disabling an EVC

•Configuring ELMI on an Individual Port

•Configuring a UNI ID on an Individual Port

•Configuring UNI-TYPE on an Individual Port

•Configuring an EVC on an Individual Port

•Displaying an EVC

•Displaying CE-VLAN/ EVC

•Displaying ELMI Statistics and Configuration

•Clearing an EVC

•Clearing an EVC on an Individual Port Associated to a UNI

•Clearing ELMI Statistics Counters

•Clearing a UNI Configuration

Note For complete syntax and usage information for the commands that are used in this section, refer to the Catalyst 6500 Series Switch Command Reference Software Release 8.x publication.

Enabling or Disabling ELMI

To enable or disable the ELMI globally on a switch, perform this task in privileged mode:

Task

Command

Enable or disable ELMI globally on a switch.

set ethernet-lmi {enable | disable}

This example shows how to enable ELMI globally on a switch:
Console> (enable) set ethernet-lmi enable
Ethernet-LMI is enabled.
Console> (enable)
Enabling or Disabling an EVC

To create an Ethernet Virtual Connection (EVC) in global configuration mode and configure various parameters associated with the EVC on a switch, perform this task in privileged mode:

.

Task

Command

Enable EVC globally and configure various parameters, such as the EVC identifier and specify the number of endpoints (UNIs), a multipoint service (uni-count of 3), the CFM maintenance domain name, the MA-name format, the maintenance association, and associated CE-VLAN.

set ethernet-evc evc-id uni-count count [multipoint] domain name ma-name-fmt fmt ma-name ce-vlan any | vlan

Note By default, an EVC with uni-count 2 is a point-to-point EVC.

These examples show how to configure various EVC parameters:
Console>(enable) set ethernet-evc EVC1 uni-count 2
UNI count for EVC1 is configured as 2.
Console> (enable) set ethernet-evc EVC1 domain ELMI ma-name-fmt text CFM1
Successfully create EVC EVC1 and CFM service name CFM1.
Console>(enable) set ethernet-evc EVC1 ce-vlan 10
CE-Vlan 10 is successfully mapped to EVC1.
Console > (enable)
Configuring ELMI on an Individual Port

To enable or disable ELMI processing on the port, perform one of these tasks in privileged mode:

Task

Command

Enable or disable ELMI on a switch port.

set port ethernet-lmi {mod/port} {enable | disable}

Specify the timer value and polling timer to transmit the status query.

Note t391 is part of the CE configuration; the Catalyst operating system supports only PE mode.

Note The polling timer range is from 5 to 30 seconds.

set port ethernet-lmi {mod/port} t391 {value | default | disable}

Specify the polling verification timer to verify the status query that is sent by the CE device and to which the PE responds with status messages.

Note t392 should be greater than t391.

Note The polling verification timer range is from 5 to 30 seconds.

set port ethernet-lmi {mod/port} t392 {value | default | disable}

Specify the polling counter that gives a full status of the User to Network Interface (UNI) and all the EVC polling counts.

Note n391 applies only to the CE.

Note The EVC polling counts range is from 1 to 65000.

set port ethernet-lmi {mod/port} n391 {value | default}

Specify the event counterthat gives a count of monitored events.

Note n393 applies to the CE and PE.

Note The event counter range is from 1 to 10.

set port ethernet-lmi {mod/port} n393 {value | default}

These examples show how to set the ELMI port:
Console>(enable) set port ethernet-lmi 3/1 enable
Ethernet LMI is enabled on port 3/1.
Console>(enable) set port ethernet-lmi 3/1 t392 30
Ethernet LMI polling verification timer is set to 30 seconds for port 3/1.
Console>(enable)
Configuring a UNI ID on an Individual Port

To set the UNI ID for a particular port, perform this task in privileged mode:

Task

Command

Configure a UNI ID on a specific module and port.

set port ethernet-uni {mod/port} id {uni-id}

This example shows how to set the Ethernet UNI ID as CUST_A_PORT1 for module 3, port 1:
Console> (enable) set port ethernet-uni 3/1 id CUST_A_PORT1
UNI id CUST_A_PORT1 is configured on port 3/1
Console> (enable)
Configuring UNI-TYPE on an Individual Port

To configure the UNI-TYPE for a particular port, perform this task in privileged mode:

Task

Command

Configure a UNI-TYPE for a specific module and port.

set port ethernet-uni {mod/port} type {all-to-one | multiplex}

This example shows how to to set the UNI TYPE as all-to-one for module 5 and port 1:
Console> (enable) set port ethernet-uni 5/1 type all-to-one 
Uni type on port 5/1 successfully set to all-to-one.
This example shows how to to set the UNI TYPE as multiplex for module 5 and port 1:
Console> (enable) set port ethernet-uni 5/1 type multiplex 
Uni type on port 5/1 successfully set to multiplex.
Configuring an EVC on an Individual Port

To associate an EVC to a port and the corresponding CE-VLANs, perform this task in privileged mode:

Task

Command

Enable or disable an EVC on a particular module and port and associate the EVC identifier.

set port ethernet-evc mod/port [evc_id]

This example shows how to set the Ethernet EVC ID as EVC1 for module 7, port 1:
Console> (enable) set port ethernet-evc 7/1 EVC1
EVC1 is associated to port 7/1.
Console> (enable

Displaying an EVC

To display the EVCs configured on a device, perform this task in privileged mode:

Task

Command

Display EVCs configured on a device.

show ethernet-evc {[detail] | evc_id [detail]}

These examples show how to display EVCs configured on the device:
Console> (enable) show ethernet-evc
St EVC Id CE-Vlan
--- ---------- -------------------------------
A EVC1 10
A EVC2 20
Key: St=Status, A=Active, P=Partially Active, I=Inactive, ?=ELMI Link Down
Console> (enable) show ethernet-evc detail
EVC Id: EVC1
EVC Type: P-P
EVC Status: Active
EVC Uni Count: 2
Number of Remote UNIs up: 1
Number of Local UNIs up: 1
CFM Service Maintenance Domain: ELMI
CFM Service Maintenance Name: CFM1
EVC CE-Vlan Mapping: 10
Ports associated to this EVC: 7/1
Remote UNI Details:
UNI Id UNI Status Port
-------------- ------------ -----------
SANFRANCISCO Up 4/47
EVC Id: EVC2
EVC Type: P-P
EVC Status: Inactive
EVC Uni Count: 2
Number of Remote UNIs up: 0
Number of Local UNIs up: 1
CFM Service Maintenance Domain: SJC
CFM Service Maintenance Name: CFM2
EVC CE-Vlan Mapping: 20
Ports associated to this EVC: 7/1
Displaying CE-VLAN/ EVC

To display the CE-VLAN/EVC mapping configured for the port, perform this task in privileged mode:

Task

Command

Display the CE-VLAN/EVC mapping.

show port ethernet-evc mod/port {[detail] | evc-id [detail]}

These examples show how to display the CE-VLAN/EVC mapping configured for module 7, port 1:
Console>(enable) show port ethernet-evc 7/1
UNI Id: PE-CUSTA-PORT1
St EVC Id CE-Vlan
------ -------------- ----------
?A EVC1 10
?A EVC2 20
Key: St=Status, A=Active, P=Partially Active, I=Inactive, ?=ELMI Link Down
Console> (enable) show port ethernet-evc 7/1 EVC1 detail
Port: 7/1
EVC Id: EVC1
Time since Last Full Report: Never
Ether LMI Link Status: Down
UNI Id: SANJOSE
UNI Status: Up
CE-VLAN/EVC Map Type: multiplex
CE-VLAN: 10
EVC Status: Inactive
EVC Type: Point-to-Point
Remote UNI Count: Configured = 1, Active = 0
Displaying ELMI Statistics and Configuration

To display ELMI statistics and ELMI parameters, perform one of these tasks in privileged mode:

Task

Command

Display ELMI statistics.

show port ethernet-lmi mod/port statistics

Display the ELMI configuration.

show port ethernet-lmi mod/port config

This example shows how to display the ELMI statistics and configuration for module 7, port 1:
Console> (enable) show port ethernet-lmi 7/1 statistics
E-LMI statistics for port 7/1
Ethernet LMI Link Status: Up
UNI Status: Up
UNI Id: PE1-CustA-Port1
Reliability Errors:
Status Enq Timeouts 0 Invalid Sequence Number 0
Protocol Errors:
Invalid Protocol Version 0 Invalid EVC Reference Id 0
Invalid Message Type 0 Out of sequence IE 0
Duplicated IE 0 Mandatory IE missing 0
Invalid Mandatory IE 0 Invalid non-mandatory IE 0
Unrecognized IE 0 Unexpected IE 0
Last Full Status Enq Rcvd 00:00:10 Last Full Status Sent 00:00:10
Last Status Check Enq Rcvd 00:00:00 Last Status Check Sent 00:00:00
Last clearing of counters never
Console> (enable) show port ethernet-lmi 7/1 config
E-LMI parameters for port 7/1
Port Ethernet LMI: Enabled
Operational Status: Disabled
Mode: PE
T391: NA
T392: 15
N391: NA
N393: 4
Console <enable>
Clearing an EVC

To clear an EVC configured in the switch, perform this task in privileged mode:

Task

Command

Clear an EVC configured in the switch.

clear ethernet-evc [evc_id]

This example shows how to clear EVC1:
Console> (enable) clear ethernet-evc EVC1
EVC1 is successfully cleared.
Console> (enable)
Clearing an EVC on an Individual Port Associated to a UNI

To clear any EVCs associated to the UNI or a specified EVC, perform this task in privileged mode:

Task

Command

Clear an EVC configured in the switch port.

clear port ethernet-lmi mod/portstatistics

This example shows how to clear EVCs associated with module 7, port 1:
Console> (enable) clear port ethernet-evc 7/1
EVCs associated with port 7/1 are cleared.
Console> (enable)
Clearing ELMI Statistics Counters

To clear ELMI statistics counters for all ports or a specified port, perform this task in priviledged mode:

Task

Command

Clear ELMI statistics counters.

clear port ethernet-evc mod/port [evc_id]

This example shows how to clear ELMI statistics associated with module 7, port 1:
Console> (enable) clear port ethernet-lmi 7/1 statistics
Ethernet LMI statistics cleared on port 7/1.
Console> (enable)
Clearing a UNI Configuration

To clear the UNI configuration on the port, perform this task in priviledged mode:

Task

Command

Clear a UNI configuration on the port.

clear port ethernet-evc mod/port [id | type]

This example shows how to clear the UNI configuration on module 7, port 1:
Console> (enable) clear port ethernet-uni 7/1
UNI configuration is cleared for port 7/1.
Console> (enable)
Configuring MAC Address Move Counters

These sections describe the MAC address move counters:

•Understanding How MAC Address Move Counters Work

•MAC Address Move Counter Configuration Guidelines and Restrictions

•MAC Address Move Counter syslog Generation

•Executing MAC Address Move Counters

Understanding How MAC Address Move Counters Work

The MAC address move counters feature provides a counter that increments each time that an existing MAC address moves from a given port to another port in the same VLAN. If you see the same MAC address on another port, this situation can indicate a problem in the network (such as a spanning-tree loop, HSRP flapping, or a server link flapping). However, this situation does not always indicate a problem. The following events can result in the same MAC address that is seen on another port but are considered normal behavior and are not indications of a problem:

•A laptop PC is moved throughout a VLAN domain as the laptop PC is moved from port to port.

•A laptop PC with multiple connections to the VLAN is moved through a physical port or wireless connection.

•A server with dual NICs is moved in two separate VLANs.

Before the MAC address move counters feature was introduced, the existing MAC move notification feature generated syslogs for each MAC address move. The two main drawbacks to the existing feature were as follows:

•When there are a large number of MAC moves, the number of generated syslogs can be overwhelming.

•The feature does not provide a convenient means of displaying the MAC addresses that have moved for future examination.

MAC Address Move Counter Configuration Guidelines and Restrictions

When configuring MAC address move counters, follow these configuration guidelines and restrictions :

•Layer 2 AISCs learn any new MAC addresses and associate them with a port. Only dynamic CAM entries are learned.

•MAC address moves are defined when MAC addresses move from a given port to another port in the same VLAN.

•The counter increments each time that an existing MAC address moves from a given port to another port in the same VLAN.

•For private VLANs, MAC address moves are defined as MAC addresses that move from a given port to another port in different secondary VLANs but in the same primary VLAN.

•The MAC address move counters feature coexists with the existing MAC address move feature when you enter the set cam notification move {enable | disable} command.

•The feature allows you to store a maximum of 1000 MAC address move counter tuples per VLAN. When the maximum limit of 1000 tuples is exceeded, new moves that occur in that VLAN are not recorded.

•For proper syslog generation, you need to set the logging level for the EARL facility to 4 or higher by entering the set logging level earl severity command.

MAC Address Move Counter syslog Generation

The MAC address move counters generate the syslogs that are described in these sections:

•Detecting MAC Address Moves

•Exceeding the Maximum Limit for MAC Address Move Counters for a VLAN

Detecting MAC Address Moves

Table 20-4 describes the scenarios that cause the "%EARL-4-MAC_MOVE_COUNTER:Mac move(s) detected" syslog to be generated.

Table 20-4 MAC Address Move Counter Syslog Generation

Scenario

Are MAC Address Move Counter Syslogs Generated?

MAC address move counters have been enabled for the first time and one or more MAC address moves occurred since the feature was enabled.

Yes

MAC address move counters have been disabled and then enabled, and one or more MAC address moves occurred since the feature was enabled.

Yes

MAC address move counter entries have been cleared for all VLANs by entering the clear cam notification move counters all command, and one or more MAC address moves occurred after the entries were cleared.

Yes

MAC address move counter entries have been cleared for a specified VLAN by entering the clear cam notification move counters vlan command, and one or more MAC address moves occurred after entries were cleared.

No

MAC address move counters have been disabled and MAC address moves are occurring.

No

Exceeding the Maximum Limit for MAC Address Move Counters for a VLAN

The following syslog is generated when the maximum limit of 1000 MAC address move counter tuples per VLAN is exceeded: "%EARL-4-MAC_MOVE_COUNTER_COUNT_EXCEEDED: Maximum limit for MAC move counters exceeded for Vlan vlan."

Executing MAC Address Move Counters

These sections describe how to execute MAC address move counters:

•Enabling or Disabling MAC Address Move Counters

•Displaying MAC Address Move Counter Statistics

•Clearing MAC Address Move Counter Statistics

Enabling or Disabling MAC Address Move Counters

To enable or disable MAC address move counters, perform this task in privileged mode:

Task

Command

Enable or disable MAC address move counters.

set cam notification move counters {disable | enable}

This example shows how to enable MAC address move counters:
Console> (enable) set cam notification move counters enable
MAC move counters are enabled
Please change the logging level for the Earl facility, as the current logging
level is set to 2 and Mac Move Counters requires a logging level of at least 4.
Console> (enable)
This example shows that the logging level for the EARL facility needs to be set to 4 or higher as follows:
Console> (enable) set logging level earl 4
System logging facility <earl> for this session set to severity 4(warnings)
Console> (enable)
This example shows how to disable MAC address move counters:
Console> (enable) set cam notification move counters disable
MAC move counters are disabled
Console> (enable)
Displaying MAC Address Move Counter Statistics

To display MAC address move counter statistics, perform this task in normal mode:

Task

Command

Display MAC address move counter statistics.

show cam notification move counters [vlan]

This example shows how to display MAC address move counter statistics for all VLANs:
Console> (enable) show cam notification move counters
-----------------------------------------------------------------------------------
Vlan    Mac Address         From Mod/Port           To Mod/Port           Count
---- ----------------- ----------------------- ----------------------- ------------
  1  00-01-02-04-04-01                     2/3                     3/1           10
 200 00-01-05-03-02-01                     5/3                     5/1           20
Console> (enable)
This example shows how to display MAC address move counter statistics for the specified VLAN:
Console> (enable) show cam notification move counters 1
-----------------------------------------------------------------------------------
Vlan    Mac Address         From Mod/Port           To Mod/Port           Count
---- ----------------- ----------------------- ----------------------- ------------
   1 00-01-02-04-04-01                     2/3                     3/1           15
Console> (enable)
This example shows how to display MAC address move counter statistics where the To Mod/Port field is part of an EtherChannel:
Console> (enable) show cam notification move counters 
-----------------------------------------------------------------------------------
Vlan    Mac Address         From Mod/Port           To Mod/Port           Count
---- ----------------- ----------------------- ----------------------- ------------
   1 00-01-02-07-08-01                     3/1         2/1,2/3,2/5,2/7           10
Console> (enable)
This example shows how to display MAC address move counter statistics where the From Mod/Port field is part of an EtherChannel:
Console> (enable) show cam notification move counters 
-----------------------------------------------------------------------------------
Vlan    Mac Address         From Mod/Port           To Mod/Port           Count
---- ----------------- ----------------------- ----------------------- ------------
   1 0-01-02-07-03-0A          2/1,2/3,2/5,2/7                     3/1           20
Console> (enable)
This example shows how to display MAC address move counter statistics where the To Mod/Port field and the From Mod/Port field are part of an EtherChannel:
Console> (enable) show cam notification move counters 
-----------------------------------------------------------------------------------
Vlan    Mac Address         From Mod/Port           To Mod/Port           Count
---- ----------------- ----------------------- ----------------------- ------------
   1 00-01-02-06-08-01         3/1,3/3,3/5,3/7         2/1,2/3,2/5,2/7           15
Console> (enable)
Clearing MAC Address Move Counter Statistics

To clear MAC address move counter statistics, perform this task in privileged mode:

Task

Command

Clear MAC address move counter statistics.

clear cam notification move counters {all | vlan}

This example shows how to clear MAC address move counter statistics for all VLANs:
Console> (enable) clear cam notification move counters all
This will clear the mac move counters for all Vlans.
Do you want to continue (y/n) [n]? y
MAC move counters for all Vlans cleared
Console> (enable)
This example shows how to clear MAC address move counter statistics for the specified VLAN:
Console> (enable) clear cam notification move counters 1
This will clear the mac move counters for Vlan 1.
Do you want to continue (y/n) [n]? y
MAC move counters for Vlan 1 cleared
Console> (enable)
Digital Optical Monitoring

The Diagnostic Optical Monitoring (DOM) feature provides real-time access for optical transceivers to operating parameters such as temperature, voltage, laser bias current, and receive/transmit optical power.

Note Xenpak transceivers do not support the voltage parameter. For Xenpak transceivers, voltage will be displayed as "n/a."

To display the default values provided for the transceivers, use the show transceivers threshold-table command. You can overwrite the threshold values by using per-port set commands.

Note Bias current is a parameter that is unique to each transceiver, and it cannot be changed by using the per-port set commands.

Displaying Transceiver Information

The following sections describe how to display transceiver information:

•Displaying General Port Transceiver Information

•Displaying Detailed Transceiver Information

•Displaying Transceiver Threshold Violations

•Displaying Port Transceiver Information

•Displaying Port Transceiver Configuration Information

Displaying General Port Transceiver Information

To display general port transceiver information, perform this task in enabled mode:

Task

Command

Display general port transceiver information.

show port transceiver

This example shows how to display general port transceiver information:
Console> show port transceiver
Transceiver monitoring is disabled for all ports.
Monitor interval is set to 10 minutes.
If device is externally calibrated, only calibrated values are printed.
++ : high alarm, +  : high warning, -  : low warning, -- : low alarm.
NA or N/A: not applicable, Tx: transmit, Rx: receive.
mA: milliamperes, dBm: decibels (milliwatts).
                                                             Optical   Optical
         Temperature  Voltage  Current   Tx Power  Rx Power
Port   (Celsius)        (Volts)   (mA)      (dBm)       (dBm)
-----   --------------   ---------   --------    ------------  -----------
 3/1     34.6             0.00        29.3         -1.7           -2.1   
 3/2     32.9             0.00        30.5         -1.8           -2.3 
Displaying Detailed Transceiver Information

To display detailed transceiver information, perform this task in enabled mode:

Task

Command

Display detailed transceiver information.

show port transceiver detail

This example shows how to display detailed transceiver information:
Console> show port transceiver detail
Transceiver monitoring is disabled for all ports.
Monitor interval is set to 10 minutes.
mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable.
## : high alarm, #  : high warning, @  : low warning, @@ : low alarm.
A2D readouts (if they differ), are reported in parentheses.
The threshold values are calibrated.
                                   High Alarm  High Warn  Low Warn   Low Alarm
         Temperature      Threshold     Threshold   Threshold    Threshold
Port   (Celsius)           (Celsius)       (Celsius)     (Celsius)     (Celsius)
-----   -----------------  --------------  -------------  --------------  ---------
 3/1    34.5                  70.0              70.0            0.0               0.0
 3/2    32.9                  70.0              70.0            0.0               0.0
                                  High Alarm  High Warn  Low Warn   Low Alarm
         Voltage             Threshold     Threshold   Threshold    Threshold
Port   (Volts)             (Volts)          (Volts)        (Volts)         (Volts)
-----  ---------------    ---------------  -------------  -------------   ---------------
 3/1   0.00                  5.24              5.24            5.24             5.24
 3/2   0.00                  5.24              5.24            5.24             5.24
                                  High Alarm  High Warn  Low Warn   Low Alarm
         Current             Threshold     Threshold   Threshold    Threshold
Port   (milliamperes)  (mA)           (mA)           (mA)           (mA)
-----  -----------------  --------------  --------------  -------------  --------------
 3/1    29.3                 2.5               2.5                2.5              2.5
 3/2    30.4                 2.5               2.5                2.5              2.5
         Optical              High Alarm  High Warn  Low Warn   Low Alarm
         Transmit Power Threshold    Threshold    Threshold    Threshold
Port   (dBm)               (dBm)          (dBm)          (dBm)          (dBm)
-----  -------------------  -------------  --------------  -------------  --------------
 3/1    -1.7                   1.0               0.0                -7.2             -8.2
 3/2    -1.8                   1.0               0.0                -7.2             -8.2
         Optical              High Alarm  High Warn  Low Warn   Low Alarm
         Receive Power  Threshold     Threshold   Threshold    Threshold
Port  (dBm)                (dBm)           (dBm)         (dBm)          (dBm)
-----  -----------------   --------------  --------------  -------------  --------------
 3/1    -2.1                  1.0               0.0                 -14.1          -16.4
 3/2    -2.3                  1.0               0.0                 -14.1          -16.4
Displaying Transceiver Threshold Violations

To display transceiver threshold violations, perform this task in enabled mode:

Task

Command

Display transceiver threshold violations.

show port transceiver slot number threshold-violations

This example shows how to display transceiver threshold violations:
Console> show port transceiver 3 threshold-violations
Transceiver monitoring is enabled for all ports.
Monitor interval is set to 5 minutes.
Rx: Receive, Tx: Transmit.
DDDD: days, HH: hours, MM: minutes, SS: seconds
Time since Last Known
         Time in slot     Threshold Violation        Type(s) of Last Known
Port  (DDDD:HH:MM:SS)     (DDDD:HH:MM:SS)           Threshold Violation(s)
-----  --------------------------  -----------------------------  ------------
 3/1   0000:06:39:07             0000:00:03:57                 Tx bias high alarm
                                                                                      5.8 
mA >   0.5 mA
 3/2   0000:06:39:07             0000:00:03:56                 Tx bias high alarm
                                                                                      6.0 
mA >   0.5 mA
Displaying Port Transceiver Information

To display port transceiver information, perform this task in enabled mode:

Task

Command

Display port transceiver information.

show port transceiver mod/port

This example shows how to display port transceiver information:
Console> show port transceiver 2/1
sh port transceiver 5/1   
Transceiver monitoring is enabled.
Monitor interval is set to 1 minute
ITU Channel not available (1550 nm)
## : high alarm, #  : high warning, @  : low warning, @@ : low alarm.
NA or N/A: not applicable, Tx: transmit, Rx: receive.
mA: milliamperes, dBm: decibels (milliwatts).
                                             Optical       Optical
       Temperature  Voltage    Current       Tx Power      Rx Power
Port   (Celsius)    (Volts)    (mA)          (dBm)         (dBm)
-----  -----------  ---------  ------------  ------------  ------------
 5/1          29.2        N/A         102.5           0.9  @@     -31.0
Displaying Port Transceiver Configuration Information

To display port transceiver configuration information, perform this task in enabled mode:

Task

Command

Display port transceiver configuration information.

show port transceiver mod/port config

This example shows how to display port transceiver configuration information:
Console> show port transceiver 3/1 config
Transceiver monitoring is disabled.
Monitor interval is set to 1 minute.
                                 Transmit Power (dBm)
          High Alarm        High Warn           Low Warn           Low Alarm
          Threshold           Threshold            Threshold            Threshold
Port   Value   Severity  Value   Severity  Value   Severity  Value   Severity
-----    -------  ----------   -------  ----------   -------   ----------  -------   -----
 3/1    default   critical   default   critical   default    critical  default   critical
                                 Receiver Power (dBm)
          High Alarm         High Warn          Low Warn           Low Alarm
          Threshold           Threshold            Threshold            Threshold
Port   Value   Severity  Value   Severity  Value   Severity  Value   Severity
-----    -------  ----------   -------   ----------  -------   ----------   -------  -----
 3/1   default    critical   default   critical   default    critical  default   critical
                                 Temperature (Celsius)
          High Alarm         High Warn          Low Warn           Low Alarm
          Threshold           Threshold            Threshold            Threshold
Port   Value   Severity  Value   Severity  Value   Severity  Value   Severity
-----    -------  ----------   -------   ----------  -------   ----------  -------  ------
 3/1    default   critical   default    critical  default   critical  default    critical
                                 Voltage (volts)
          High Alarm         High Warn          Low Warn           Low Alarm
          Threshold           Threshold            Threshold            Threshold
Port   Value   Severity  Value   Severity  Value   Severity  Value   Severity
-----    -------  ----------   -------   ----------  -------   ----------  -------   -----
 3/1   default    critical  default    critical  default    critical  default    critical
Setting Transceiver Monitoring and Thresholds

The following sections describe how to set transceiver monitoring parameters and thresholds:

•Enabling or Disabling Transceiver Monitoring

•Setting the Transceiver Monitoring Interval

•Setting the Transceiver Temperature Threshold

Enabling or Disabling Transceiver Monitoring

To enable or disable transceiver monitoring, perform this task in enabled mode:

Task

Command

Enable transceiver monitoring.

set transceiver-monitoring [enable | disable]

This example shows how to enable transceiver monitoring:
Console> (enable) set transceiver-monitoring enable
Transceiver monitoring is successfully enabled
This example shows how to disable transceiver monitoring:
Console> (enable) set transceiver-monitoring disable
Transceiver monitoring is successfully disabled