ATM and Layer 3 Troubleshooting Guide, 12.0(13)W5(19)
Troubleshooting ATM Router Module Connections
Download this chapter
Troubleshooting ATM Router Module ConnectionsTroubleshooting ATM Router Module Connections
give_us_feedback

Table of Contents

Troubleshooting ATM Router Module Connections
 Overview of Integrated Layer 3-to-ATM Switching and Routing
 Hardware and Software Restrictions of the ATM Router Module
 Troubleshooting LANE Clients on ATM Router Module Connections
 Troubleshooting RFC 1483 on ATM Router Module Connections
 Troubleshooting RFC 1577 on ATM Router Module Connections
 Troubleshooting OAM on ATM Router Module Connections

Troubleshooting ATM Router Module Connections

This chapter provides troubleshooting information about connectivity and performance problems in the ATM router module (ARM) on the Catalyst 8540 CSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers, and the enhanced ATM router module for the Catalyst 8540 CSR. The ATM router module allows you to integrate Layer 3 switching with ATM switching on the same switch router.

Note   For complete descriptions of the commands mentioned in this chapter, refer to the
ATM Switch Router Command Reference . For hardware installation and cabling instructions, refer to the ATM and Layer 3 Port Adapter and Interface Module Installation Guide.
Note   The LightStream 1010 system software image does not include support for the ATM router module or Layer 3 features. You can download the Catalyst 8510 MSR image to a LightStream 1010 ATM switch router that has a multiservice ATM switch processor installed.

The chapter includes the following sections:

Overview of Integrated Layer 3-to-ATM Switching and Routing

This section describes the ATM router module that can be installed in Catalyst 8540 MSR and Catalyst 8540 CSR chassis that allows direct connections from the Layer 3 Ethernet network to the ATM backbone.

ATM Router Module Overview

The ATM router module allows you to integrate Layer 3 routing and ATM switching within a single chassis. When you install the ATM router module, you no longer need to choose either Layer 3 or ATM technology, as is frequently the case with enterprise, campus, and MAN applications.

The ATM router module can perform one or a combination of the functions described in Figure 13-1.


Figure 13-1   ATM Router Module Routing and Bridging Functions


The ATM router module receives Address Resolution Protocol (ARP) messages and route broadcasts from connected ATM peers, and sends the appropriate control information to the route processor. On the ATM side, the ATM router module connects to the switching fabric as would any other interface module.

On the Catalyst 8540 CSR, the ATM router module supports LANE clients (LECs), but not the LANE servers (LES, LECS, and BUS). It separates the control and data path so that all LANE control messages are handled by the route processor, and data messages are switched on the ATM router module port, as shown in Figure 13-8. (See the "Comparing Data Plane and Control Plane Traffic" section for a description of control and dataplane traffic.) The LEC is configured on the ATM router module interface, but control message traffic is sent to the route processor by the ATM router module. The ATM router module sends all ATM data traffic to the following VCs:

  • In a LANE environment, the ATM router module sends all ATM data traffic to the Data Direct VCs.
  • In an RFC 1483 environment, or multiprotocol encapsulation over ATM (MPOA), the ATM router module sends all ATM data traffic to the corresponding PVC.
  • In an RFC 1577 environment, the ATM router module sends all ATM data traffic to the corresponding SVC.
    • Note   The Catalyst 8540 CSR enhanced ATM router module does not support LANE clients.

The ATM router module has no external interfaces. All traffic is sent and received through internal interfaces to the switching fabric. The Catalyst 8540 CSR enhanced ATM router module has two internal ports. See the "Understanding Packet and Cell Flow" section for a description of how the ATM router module interfaces connect to the other interfaces.

Hardware and Software Restrictions of the ATM Router Module

This section describes hardware and software restrictions for the ATM router module that could cause you connection or configuration problems.

Hardware Restrictions

The following hardware restrictions apply to the Catalyst 8540 CSR, Catalyst 8510 MSR, and LightStream 1010 ATM router modules, and the Catalyst 8540 CSR enhanced ATM router modules:

  • You can install the ATM router module in any slot except a route processor slot and, in the case of the Catalyst 8540 CSR, a switch processor slot.
  • The ATM router module is only supported on LightStream 1010 ATM switches that have a multiservice ATM switch route processor with FC-PFQ and the Catalyst 8510 MSR system software image.
  • You can install up to two ATM router modules per chassis.
  • When you hot swap an ATM router module, wait one minute after removing the module before inserting a new module.
Note    The ATM router module is only supported on ATM switches that have a multiservice ATM switch processor installed.

ATM Router Module Software

This section describes software image requirements and restrictions that, if ignored could cause your ATM router module to malfunction.

Catalyst 8540 CSR Enhanced ATM Router Module Software Restrictions

The following software restrictions apply to the Catalyst 8540 CSR enhanced ATM router module:

  • LANE is not supported.
  • Use tag switching functionality with caution. Do not distribute routes learned through tag switching to Fast Ethernet (FE) or Gigabit Ethernet (GE), or vice versa. Otherwise, you might have unreachable route destinations.
  • The ATM router module does not initialize if it replaces an ATM port adapter or interface module when hierarchical VP tunnels are globally enabled. Reboot the switch to initialize the ATM router module.
  • ATM Director does not support any PVC commands.
  • Up to 2048 external VCs can be configured on each ATM router module interface.
  • Do not install an ATM router module in a slot pair with hierarchical VP tunnels configured. Slot pairs 0 and 1, 2 and 3, 9 and 10, and 11 and 12 use the same switching modules for scheduling. For example, do not install an ATM router module in slot 10 when hierarchical VP tunnels are configured on slot 9. For more information on hierarchical VP tunneling restrictions, refer to the "Configuring Virtual Connections" chapter in the ATM  Switch Router Software Configuration Guide.

The Catalyst 8540 CSR enhanced ATM router modules do not support the following features:

  • Point-to-point subinterfaces. Only point-to-multipoint subinterfaces are supported.
  • Tag-edged router functionality
  • Fast Simple Server Redundancy Protocol (SSRP)
  • Bridging for multiplexing device encapsulation
  • Protocol Independent Multicast (PIM) IP multipoint signalling
  • PIM nonbroadcast multiaccess (NBMA)
  • PIM over ATM multipoint signalling
  • Translation from IP quality of service (QoS) to ATM QoS
  • Resource Reservation Protocol (RSVP) to ATM SVC
  • Access lists for ATM to ATM routing
  • Half-bridge devices
  • Layer 2 ACLs
Catalyst 8540 CSR ATM Router Module Software Restrictions

The following software restrictions apply to the Catalyst 8540 CSR ATM router module:

  • Use tag switching functionality with caution. Do not distribute routes learned through tag switching to FE or GE, or vice versa. Otherwise, you might have unreachable route destinations.
  • The ATM router module does not initialize if it replaces an ATM port adapter or interface module when hierarchical VP tunnels are globally enabled. Reboot the switch to initialize the ATM router module.
  • ATM Director does not support any PVC commands.
  • On an ATM router module interface, only LANE clients or RFC 1483 can be configured.
    • Note   LANE clients or RFC 1483 can be configured on multiple ATM router module interface simultaneously.
  • RFC 1483 on the ATM router module supports only AAL5 SNAP encapsulation.
  • Up to 2048 external VCs can be configured on each ATM router module interface.
  • You can have a maximum of 64 LECs per chassis.
  • Do not install an ATM router module in a slot pair with hierarchical VP tunnels configured. Slot pairs 0 and 1, 2 and 3, 9 and 10, and 11 and 12 use the same switching modules for scheduling. For example, do not install an ATM router module in slot 10 when hierarchical VP tunnels are configured on slot 9. For more information on hierarchical VP tunneling restrictions, refer to the "Configuring Virtual Connections" chapter in the ATM  Switch Router Software Configuration Guide.
  • Token Ring LANE is not supported.

The Catalyst 8540 CSR ATM router modules do not support the following features:

  • Point-to-point subinterfaces. Only point-to-multipoint subinterfaces are supported.
  • Tag-edged router functionality
  • Fast Simple Server Redundancy Protocol (SSRP)
  • Bridging for multiplexing device encapsulation
  • PIM IP multipoint signalling
  • PIM NBMA
  • PIM over ATM multipoint signalling
  • Translation from IP QoS to ATM QoS
  • RSVP to ATM SVC
  • Access lists for ATM to ATM routing
  • Half-bridge devices
  • RFC 1483 MUX encapsulation
  • ACL support for IP, and standard ACL support for IPX
  • IP fragmentation support.
  • IP 6-path load balancing support.
Catalyst 8510 MSR and LightStream 1010 ATM Router Module Software Restrictions

The following software restrictions apply to the Catalyst 8510 MSR ATM router module:

  • Use tag switching functionality with caution. The switch router does not distribute routes learned through tag switching to FE or GE, or vice versa. If you use tag switching, you might have unreachable route destinations.
    • Note   This is a temporary restriction. A soon-to-be-released software update will remove this limitation.
  • The ATM router module does not initialize if it replaces an ATM port adapter or interface module when hierarchical VP tunnels are globally enabled. Reboot the switch to initialize the ATM router module.
  • ATM Director does not support any PVC commands.
  • RFC 1483 on the ATM router module supports only AAL5 SNAP encapsulation.
  • Up to 2048 external VCs can be configured on each ATM router module interface.
  • Do not install an ATM router module in a slot pair with hierarchical VP tunnels configured. Slot pair 0 and 1 and slot pair 3 and 4 use the same switching modules for scheduling. For example, do not install an ATM router module in slot 1 when hierarchical VP tunnels are configured on slot 0. For more information on hierarchical VP tunneling restrictions, refer to the "Configuring Virtual Connections" chapter in the ATM  Switch Router Software Configuration Guide.
  • RFC 1577 SVCs
  • LANE clients are not supported.
  • Only UBR PVCs are supported.

The Catalyst 8510 MSR and LightStream 1010 ATM router modules do not support the following features:

  • Point-to-point subinterfaces. Only point-to-multipoint subinterfaces are supported.
  • Tag-edged router functionality
  • SSRP
  • Bridging for multiplexing device encapsulation
  • Protocol Independent Multicast (PIM) IP multipoint signalling
  • PIM nonbroadcast multiaccess (NBMA)
  • PIM over ATM multipoint signalling
  • Translation from IP quality of service (QoS) to ATM QoS
  • Resource Reservation Protocol (RSVP) to ATM SVC
  • Access lists for ATM to ATM routing
  • Half-bridge devices
  • RFC 1483 MUX encapsulation
  • ACL support for IP, and standard ACL support for IPX
  • IP fragmentation support.
  • IP 6-path load balancing support.
    • Note   The ATM router module is only supported on ATM switches that have a multiservice ATM switch processor installed.

Understanding Packet and Cell Flow

This section describes packet flow through the ATM router module.

An ATM router module interface does not have any capabilities for ATM signalling. All ATM signalling is directed to the main route processor. The route processor is also responsible for setting up all ATM related VCs to enable the ATM router module to route any data traffic that it processes.

The ATM router module provides a packet-parsing, or look-up, engine that does not exist on the other ATM port adapter modules in the switch router. Data traffic coming from an ATM cloud targeted to hosts on the Ethernet side of the switch router are terminated on the ATM router module. The ATM router module processes the packets to identify the target port before the packets are sent to the Ethernet ports, ATM port, or route processor.

Note   All LANE control frames are sent to route processor.

When an ATM router module encounters a spanning tree packet or an ARP request, it passes it to the route processor. Unlike an Ethernet module, the packet may have LANE or RFC 1483 encapsulation, and the packet must be transferred to the respective protocol layer once it reaches the route processor. For this to happen, one data VC per protocol is created when the ATM router module is initialized. These VCs are enabled as long as the ATM router module is present in the system.

The ATM router module port needs no external interfaces, such as cables, to come up. Each ATM router module interface has a unique MAC Address which is allocated by the route processor. You can configure subinterfaces on the ATM router module interfaces where the LECS or RFC 1483 clients are configured. The ATM interface allows limited ATM functionality; the subinterfaces on the ATM router module interface support full ATM functionality.

Note   These subinterfaces are not created by default.

The ATM router module supports LANE clients (LECs), but not the LANE servers (LES, LECS, and BUS). It separates the control and data path so that all LANE control messages are handled by the route processor, and all data messages are switched on the ATM router module port, as shown in Figure 13-2. The LEC is configured on the ATM router module interface, but control message traffic is sent to the route processor by the ATM router module. The ATM router module then sends all ATM data traffic to the appropriate VCs.


Figure 13-2   ATM Router Module Traffic Flow (Catalyst 8540 CSR)


The design of ATM router module software is intended to separate the control and data paths so that all LANE control messages are handled by route processor, and all data is switched on the ATM router module port.

Note   The LightStream 1010 ATM switch allows configuration of LECs only on the controller port subinterface (for example, the route processor atm2/0/0.subinterface). Thus, all VCs for signalling are terminated on the route processor.

Figure 13-3 shows the functional architecture of a switch router with an ATM router module installed. Traffic can enter the switch through any one of the ATM, Fast EtherChannel, or Gigabit Ethernet interfaces. Then the traffic is either:

  • switched across the switch fabric to the route processor for initial route processing
  • switched across the switch fabric to the ATM router module to be returned to the switch fabric for routing through any one of the remaining interfaces
  • Layer 2 switched across the switch fabric to any one of the remaining interfaces

Figure 13-3   Packet Flow Through the ATM Router Module


Logically, the ATM router module appears and functions like a router connected with both Gigabit Ethernet and ATM interfaces to the switch router on one side and the Ethernet and ATM networks connected to the other side. See Figure 13-4.


Figure 13-4   Logical View of the ATM Router Module in the Switch Router


The ATM router modules for the switch routers have the following aggregate throughput:

  • 2.5 Gb/s throughput for the Catalyst 8540 MSR ATM router module with two internal ATM interfaces
  • 1.25 Gb/s throughput for the Catalyst 8510 MSR ATM router module with one internal ATM interface

Troubleshooting the ATM Router Module Hardware

The ATM router module for the Catalyst 8510 MSR is based on the single-port Gigabit Ethernet interface module. The ATM router module for the Catalyst 8540 CSR is based on the dual-port Gigabit Ethernet interface module. The ATM router module does not have the fiber transceivers in the faceplate. The Gigabit Ethernet processor interfaces are terminated on the board and only connect to the other interfaces on the ATM switch router through the backplane.

Note   You can access the ATM router module interfaces using the standard CLI show interface atm card/subcard/port command and other interface commands.

On the faceplate, there is only one Status LED. If that LED appears green, the ATM router module is functioning properly, red means the ATM router module has failed its internal diagnostic self-tests.

Follow these steps to troubleshoot the ATM router module hardware:

Step 1   Use the show hardware detail command to confirm the ATM router module FPGA version and CAM configuration.

Switch# show hardware detail
Switch named Switch, Date: 18:23:14 UTC Tue Dec 5 2000
Slot Ctrlr-Type Part No. Rev Ser No Mfg Date RMA No. Hw Vrs Tst EEP
---- ------------ ---------- -- -------- --------- -------- ------- --- ---
0/* Super Cam 73-2739-03 D0 03170TAL May 03 99 0 3.1
0/0 8T1 IMA PAM 73-3367-02 B2 03100061 Mar 15 99 00-00-00 2.0 0 0
0/1 8E1 IMA PAM 73-3378-02 B2 03120056 Mar 25 99 00-00-00 2.0 0 2
2/* ARM PAM 73-4208-01 05 03150016 Apr 18 99 1.0
3/* ETHERNET PAM 73-3754-06 B0 03282WBF Jul 13 99 0 5.1
9/* OC48c PAM 73-3745-02 12 03190UXC Jun 28 99 2.1
10/* OCM Board 73-4165-01 04 03230ZZ2 Jun 28 99 10.1
10/0 QUAD 622 Gen 73-2851-05 A0 03160RVS Jun 16 99 5.0
11/* OC48c PAM 73-3745-02 12 03100015 Jun 28 99 2.1
12/* OCM Board 73-4165-01 04 03190UJV Jun 28 99 10.1
12/0 QUAD 622 Gen 73-2851-05 A0 03160S9J Jun 16 99 0 5.0
.
(Information Deleted)
.
slot: 2/* Controller-Type : ARM PAM
Part Number: 73-4208-01 Revision: 05
Serial Number: SCA03150016 Mfg Date: Apr 18 99
RMA Number: H/W Version: 1.0
FPGA Version: 2.3
EPIF Version: 1704 CAM size: 64 KB
Ucode Version: 0.0 CAM Type: Dual
Port Phy Setup
          Port 0: DONE GBIC Vendor: No vendor info.
          Port 1: DONE GBIC Vendor: No vendor info.
slot: 3/*
.
(Information Deleted)
.

Step 2   Check the Ctrlr-Type field. Find the slot where the ATM router module (shown as "ARM PAM") is installed.

Step 3   Check the FPGA Version field. It should match the version listed in the
Hardware and Software Compatibility Matrix.

If it is not the correct version, update the FPGA image using the instructions in the "IOS Upgrade Procedures" section.

Step 4   Check the CAM size and type.

Note   The GBIC Vendor field indicates no vendor information. These Gigabit interfaces, included with the ATM router module, are terminated on the board and only connect to the backplane.



If you determine that the interface is configured incorrectly, refer to the "Configuring ATM Router Module Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Troubleshooting LANE Clients on ATM Router Module Connections

The troubleshooting process for LECs configured on the ATM router module is very similar to the troubleshooting process for ATM-to-ATM LANE connections described in "Troubleshooting LAN Emulation Switching Environments," except for the following:

  • All LANE VCs terminate on the ATM router module
  • All ATM signalling is processed by the route processor and the ATM router module redirects LANE control traffic to route processor
  • All Service Specific Connection Oriented Protocol (SSCOP) packets are forwarded directly to route processor

Figure 13-5 displays how the ATM router module installed in the Catalyst 8540 interacts with the other elements of the ATM network and allows connections to Ethernet networks.


Figure 13-5   ATM Router Module in the ATM Network


An ATM router module installed in the switch router allows the connection of Ethernet networks through the switch router to the ATM connections in the ATM cloud. The ATM router module has the following functions and limitations:

  • Supports LEC configuration on the ATM router module interfaces and subinterfaces
  • No LECS/LES/BUS configuration is allowed on the ATM router module
  • Up to 32 LECs are allowed per ATM router module
  • A maximum of two ATM router modules per chassis, allowing a maximum of 64 LECs
  • Default ATM address prefix same as the route processor port
  • All IP, IPX, and bridging commands are allowed on the ATM router module interfaces and subinterfaces
  • Shutdown and no shutdown commands are allowed on the ATM router module interfaces and subinterfaces
  • From the CLI, the ATM router module ATM interface is configured in the same manner as any other IOS switch router

Troubleshooting LECs Problems on the ATM Router Module Commands

To display the ATM router module and LECs configuration, use the following commands:

Command Purpose

show lane client

Displays the LEC configuration and status

show atm vc interface card/subcard/port.subinterface

Displays the ATM layer connection information about the virtual connection.

show epc if-entry

Displays interface entry information for the specific interface.

show ip cef ip-address

Displays Cisco Express Forwarding information.

show epc ip-address interface {fastethernet | gigabitethernet} slot/subslot/port ip-address

Displays the IP addresses of adjacent interfaces.

show atm vc traffic interface atm card/subcard/port VPI VCI

Displays information about the ATM virtual connection.

ping ip-address

Confirms the IP connection and increments the transmit and receive cell counters.

To troubleshoot LECs configured on the ATM router module, refer to "Troubleshooting LAN Emulation Switching Environments," and use normal LANE troubleshooting techniques.

Figure 13-6 is an example network of a switch router with an ATM router module configured with two LECs connecting an Ethernet network and an ATM network.


Figure 13-6   ATM Router Module LEC Example Network


This example network is used in the following troubleshooting steps.

Follow these steps to troubleshoot the ATM router module LECs configured in the example:

Step 1   Use the following commands to configure the LECs on ATM interfaces 10.0.0.0 and 10.0.0.1.

Switch# config term
Switch(config)# interface atm10/0/0.1 multipoint
Switch(config-if)# lane client ethernet elan1
Switch(config-if)# ip address 1.1.1.2 255.255.0.0
Switch(config-if)# exit
Switch(config)# interface atm10/0/1.1 multipoint
Switch(config-if)# lane client ethernet elan2
Switch(config-if)# ip address 2.2.2.2 255.255.0.0
Switch(config-if)# end
Switch#

Step 2   Use the show running-config command to confirm the LEC configuration of the ATM router module interfaces.

Switch# show running-config
Building configuration...
Current configuration:
!
.
(Information Deleted)
.
!
interface ATM10/0/0
no ip address
logging event subif-link-status
!
interface ATM10/0/0.1 multipoint
ip address 1.1.1.2 255.255.0.0
 lane client ethernet elan1
!
interface ATM10/0/1
no ip address
atm pvc 2 100 pd on inarp 10
!
interface ATM10/0/1.1 multipoint
ip address 2.2.2.2 255.255.0.0
 lane client ethernet elan2
!
.
(Information Deleted)
.

Step 3   Use the show lane client command to confirm the various LEC connections are up and the configuration is valid.

Switch# show lane client
LE Client ATM10/0/0.3 ELAN name: ELAN3 Admin: up State: operational
Client ID: 4 LEC up for 1 hour 52 minutes 56 seconds
.
(Information Deleted)
.

Step 4   Check the LEC field. It should be up.

Step 5   Use the show atm vc interface command to confirm the connections are up and the configuration is valid.

Switch# show atm vc interface atm 10/0/0.3
Interface VPI VCI Type X-Interface X-VPI X-VCI Encap Status
ATM10/0/0           0 35    PVC       ATM0                0      271  LSCNTL UP
ATM10/0/0          0 36    PVC       ATM0                0      272  LSDATA UP
.
(Information Deleted)
.
ATM10/0/0           0 743    SVC      ATM9/0/0            0       53  LANE UP
ATM10/0/0           0 744    SVC      ATM9/0/0            0       54  LANE UP
ATM10/0/0           0 745    SVC      ATM9/0/0            0       55  LANE UP
.
(Information Deleted)
.
ATM10/0/0           0 322    PVC      Gi3/0/1             0       67  LSDATA UP
ATM10/0/0           0 323    PVC      Gi3/0/1             0       68  LSDATA UP
ATM10/0/0           0 325    PVC      Gi3/0/1             0       70  LSDATA UP
ATM10/0/0           0 326    PVC      Gi3/0/1             0       71  LSDATA UP

Step 6   Check the Status field. It should appear up for all LECs ATM interfaces.

Step 7   Use the show epc if-entry interface command and test the CAM information between the egress Gigabit Ethernet interface from the entry ATM interface.

Switch# show epc if-entry interface atm 10/0/0 entry gigabitEthernet 3/0/1
IF Entry for GigabitEthernet3/0/1 on ATM10/0/0
Mac(hex) - 00:90:21:41:88:38
isMyInteface : False isSubInterface : False
      Status Up Broute VC - 322 Bcast VC - 0
Netmask: 24
FEC disabled
Trunking Disabled
State : Not-Applicable/Listening/Blocking
Bridge-Group disabled
       IP routing on bridging off
IPX routing off bridging off
Appletalk routing off
In Encapsulation:
ICMP Redirect enabled Unreachable enabled
IP Multicast disabled: ttl-threshold: 0

Check the following:

  • Broute VC field status is up.
  • Note the Broute VC number. In this example, the Broute VC is "322."
  • IP routing is on.

Step 8   Use the show epc if-entry interface command and test the CAM information in the opposite direction between the egress ATM interface from the entry Gigabit Ethernet interface.

Switch# show epc if-entry interface gigabitEtherenet3/0/1 entry atm 10/0/0.3
IF Entry for ATM10/0/0.3 on GigabitEthernet3/0/1
Mac(hex) - 00:90:21:41:88:17
isMyInteface : False isSubInterface : True
   Status Up Broute VC - 67 Bcast VC - 0
Netmask: 25
FEC disabled
Trunking Disabled
State : Not-Applicable/Listening/Blocking
Bridge-Group disabled
     IP routing on bridging off
IPX routing off bridging off
Appletalk routing off
In Encapsulation:
ICMP Redirect enabled Unreachable enabled
IP Multicast disabled: ttl-threshold: 0
LECID - 0, Multicast Send VC - 0

Check the following:

  • Broute VC field status is up.
  • Note the Broute VC number. In this example, the Broute VC is "67."
  • IP routing is on.

Step 9   Use the show ip cef command to verify that routes and attached devices appear in the table correctly and point to the correct next hop or outgoing interface.

Switch# show ip cef 128.250.0.1
128.250.0.1/32, version 90, connected, cached adjacency 128.250.0.1
0 packets, 0 bytes
via 128.250.0.1, ATM10/0/0.1, 0 dependencies
       next hop 128.250.0.1, ATM10/0/0.1, valid cached adjacency

Step 10   Use the show epc ip-address command with the IP address of the egress interface to display the status of the MAC address rewrite and the VCI number.

Switch# show epc ip-address interface atm 10/0/0 128.250.0.1
IPaddr: 128.250.0.1 MACaddr: 0000.0c07.ac01 Routed to VC(940)

Check the Routed to VC field (in this example, the VC is "940"). The value is used in the next step.

Step 11   Use the show atm vc traffic interface atm command with the VPI and VCI parameters to see the receive and transmit cell counts.

Switch# show atm vc traffic interface atm 10/0/0 0 940
Interface VPI VCI Type rx-cell-cnts tx-cell-cnts
ATM10/0/0 0 940 SVC 18 25

Step 12   Use the ping command to confirm the connection and increment the receive and transmit cell counts.

Switch# ping 128.250.0.1
Sending 5, 100-byte ICMP Echos to 128.250.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

Step 13   Again, use the show atm vc traffic interface atm command with the VPI and VCI parameters, to confirm that the receive and transmit cell counts are incrementing.

Switch# show atm vc traffic interface atm 10/0/0 0 940
Interface VPI VCI Type rx-cell-cnts tx-cell-cnts
ATM10/0/0 0 940 SVC 33 40



If you determine that the interface is configured incorrectly, refer to the "Configuring ATM Router Module Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

ATM Router Module IP Switching Overview

This section describes IP switching using the ATM router module.

Figure 13-7 shows a network with a switch router that has an ATM router module installed and connected to an Ethernet subnet on one side and two ATM ELAN networks on the other.


Figure 13-7   ATM Router Module IP Switching Example Network


The following are the routing, CEF, and adjacency tables created for the network configuration on the Catalyst 8540 with an ATM router module, shown in Figure 13-7.

Routing Table:
10.1.0.0 is directly connected, FastEth 1/0/0
20.1.0.0 is directly connected, ATM3/0/0.1
30.1.0.0 is directly connected, ATM4/0/0.1
CEF Table
10.1.0.0 attached FastEth 0/0/0
20.1.0.0 attached ATM 3/0/0.1
30.1.0.0 attached ATM 4/0/0.1
Adjacency Table:
FastEth   0/0/0 10.1.1.2 00ab.cdef.0001 Interface No.
ATM 3/0/0.1 20.1.1.2 00ab.cdef.0002 Data VC
ATM 4/0/0.1 30.1.1.2 00ab.cdef.0003 Data VC

Using this configuration, traffic entering the Catalyst 8540 through the Fast Ethernet interface 0/0/0 from Host A on network 10.1.0.0 propagates the CAM on the Ethernet interface with the following:

CAM Port FA 0/0/0
My-MAC=FE000
My-Subnet=10.1.0.0/16
Subnet    20.1.0.0/16
10.1.1.2=00ab.cdef.0001, S1.A,  FA0/0/0
20.1.1.5=LEC101,         S2.B,  ATM10/0/1
IF-MAP:
ATM10/0/1    Broute VC    92
                  Bcast VC      0

Using Broute VC 92, the Ethernet packet is switched across the backplane to the ATM router module at ATM interface 1/0/1, where it propagates the CAM on the ATM interface with the following:

CAM Port atm 10/0/1
My-MAC=LEC101
My-Subnet=S2
Subnet S1
10.1.1.2=00ab.cdef.0001, S1.A, Fa 0/0/0
20.1.1.5=MAC_B, VPI0, VCI188
(Data Direct VC)
IF-MAP:
       Fa 0/0/0    Broute VC     80
                 Bcast VC      0

Using VPI 10 and VCI 188, the ATM router module transfers the Ethernet packets across the backplane to ATM interface 9/0/3, for transmission out to the LANE cloud and subsequent delivery to the destination Host.

Troubleshooting IP switching with the ATM router module configured between the ATM and Ethernet interfaces is essentially the same as described in the "Troubleshooting IP Layer 3 Connections" section. However, you must confirm connections and adjacencies through the ATM router module.

IPX Switching Overview

This section describes IPX switching using the ATM router module.

Figure 13-8 shows a network with a switch router that has an ATM router module installed and connected to an Ethernet subnet on one side and two ATM ELAN networks on the other.


Figure 13-8   ATM Router Module IPX Switching Example Network


The following are the routing and node tables created for the network configuration on the Catalyst 8540 with an ATM router module shown in Figure 13-8.

Routing Table
Network 100, Primary network, FastEth 1/0/0
Network 200, Primary network, ATM 3/0/0.1
Node Table:
FastEth 1/0/0 100.00ab.cdef.0001 Interface no.
ATM      3/0/0.1 200.00ab.cdef.0002 Data VC

Troubleshooting IP switching with the ATM router module configured between the ATM and Ethernet interfaces is essentially the same as described in the "Troubleshooting IPX Layer 3 Routing" section. However, you must confirm connections and adjacencies through the ATM router module.

General ATM Router Module Troubleshooting

Use the following commands to troubleshoot general ATM router module connections:

Command Purpose

ping ip-address

Tests the network node reachability.

show epc ifmapping interface-map-number

Displays interface mapping to CAM interface number.

show epc ip-address interface atm card/subcard/port ip-address

Displays all adjacent IP addresses for the specified interface.

Use the following commands to troubleshoot the ATM router module LECs and the configuration:

Step 1   Use the ping command to confirm the LEC connection to the end station.

Switch# ping 128.250.20.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 128.250.20.1, timeout is 2 seconds:
3d09h: LEC ATM10/0/0.3: received SETUP
3d09h: LEC ATM10/0/0.3: callid 0x638CACB8
3d09h: LEC ATM10/0/0.3: called party 39.036F10070306000101000000.009021418817.03
3d09h: LEC ATM10/0/0.3: calling_party 39.036F100703060010073C1501.0010F66C841C.03
3d09h: LEC ATM10/0/0.3: sending CONNECT
3d09h: LEC ATM10/0/0.3: callid 0x638CACB8
3d09h: LEC ATM10/0/0.3: vcd 943
3d09h: LSSLEC:LANE-Cache_VC:if=45 vc=943 type=6
3d09h: LEC ATM10/0/0.3: received CONNECT_ACK.!!.!
Success rate is 60 percent (3/5), round-trip min/avg/max = 1/1/1 ms
3d09h: LSSLEC:ADJ:Host:128.250.20.1 MAC:0000.0c07.ac03 Valid:TRUE MyIP:FALSE if=8 vc=943 if_vc=45
3d09h: LSSLEC:ADJ:Host:128.250.20.1 MAC:0000.0c07.ac03 Valid:TRUE MyIP:FALSE if=8 vc=943 if_vc=45

Check the if_vc= field and make note of the interface VC number. In this case, the interface VC is "45."

Step 2   Use the show epc ifmapping command with the interface number to confirm the interface VC is mapped correctly to the ATM interface.

Switch# show epc ifmapping 45
ATM10/0/0.3 (IF number: 45)

The IF number field (in this example, "45") indicates the interface index number is mapping correctly.

Step 3   Use the show epc ip-address interface command with the IP address to confirm the VC number.

Switch# show epc ip-address interface atm 10/0/0 128.250.20.1
IPaddr: 128.250.20.1 MACaddr: 0000.0c07.ac03 Routed to VC(943)

The information in this display should match the information shown using the show adjacency command to display the MAC address rewrite.




If you determine that the interface is configured incorrectly, refer to the "Configuring ATM Router Module Interfaces" chapter in the ATM Switch Router Software Configuration Guide .

Troubleshooting RFC 1483 on ATM Router Module Connections

The primary use of RFC 1483, or multiprotocol encapsulation over ATM (MPOA), is to carry multiple Layer 3 and bridged frames over ATM. RFC 1483 traffic is routed through the ATM router module interface using static map lists. Static map lists provide an alternative to using the ATM Address Resolution Protocol (ARP) and ATM Inverse ARP (InARP) mechanisms.

Note   Traffic shaping and policing are not supported on the ATM router module interfaces. Use VP tunnels as an alternative for traffic shaping on ATM connections.

Troubleshooting RFC 1483 Problems on ATM Router Module Commands

To display the ATM router module and RFC 1483 configuration, use the following commands:

Command Purpose

show running-config

Shows the status of the configuration and physical interfaces.

show interfaces atm card/subcard/port

Shows the status of the physical interface.

show atm vc interface card/subcard/port.subinterface

Displays the ATM layer connection information about the virtual connection.

ping ip-address

Confirms the IP connection and increments the transmit and receive cell counters.

Figure 13-6 is an example network of a switch router with an ATM router module configured with two RFC 1483 interfaces connecting an Ethernet network and an ATM network.


Figure 13-9   ATM Router Module RFC 1483 Example Network


This example network is used in the following troubleshooting process.

To troubleshoot the ATM router module configured with RFC 1483 and with aggressive policing configured follow these processes:

  • Verify VC status between ATM router module interfaces and the route processor.
  • Display VC details between ATM router module interfaces and ATM interfaces
  • Display VC details between ATM router module interfaces and Ethernet interfaces
  • Verify policing or Usage Parameter Control (UPC) on switch and traffic shaping on routers
    • Policing UPC—Traffic is constantly monitored at the switch to ensure the contract is not violated. Non-conforming cells may be marked, dropped or passed
    • Traffic shaping—Typically done at edge devices to reduce burstiness. Decreases probability of cell loss at expense of occasional delay between ATM router module interfaces and Ethernet interfaces

Follow these steps to troubleshoot the ATM router module configured with RFC 1483 and very aggressive policing.

Step 1   Use the following commands to configure the aggressive policing, the ATM router module with RFC 1483, and the map list.

Switch(config)# atm connection-traffic-table-row index 110 ubr pcr 1
 Switch(config)# interfaces atm10/0/1.3 multipoint
Switch(config-if)# ip address 2.2.0.2 255.255.255.0
Switch(config-if)# map-group RFC1483_2
Switch(config-if)# atm pvc 2 109 pd on interface ATM0/0/0 0 109 upc drop
Switch(config-if)# exit
Switch(config)# int atm10/0/1.3 multipoint
Switch(config-if)# atm pvc 2 101 pd on interface ATM0/0/1 0 101
Switch(config-if)# bridge-group 10
Switch(config-if)# exit
Switch(config)# map-list RFC1483_2
Switch(config-map-list)# ip 2.2.0.1 atm-vc 109 broadcast
Switch(config-map-list)# end
Switch(config)# bridge 10 protocol ieee

Step 2   Use the show running-config command to confirm your configuration.

Switch# show running-config
Building configuration...
Current configuration:
.
(Information Deleted)
.
!
atm connection-traffic-table-row index 110 ubr pcr 1
.
(Information Deleted)
.
interface ATM10/0/1.3 multipoint
ip address 2.2.0.2 255.255.255.0
map-group RFC1483_2
atm pvc 2 109 pd on rx-cttr 110 tx-cttr 110 interface ATM0/0/0 0 109 upc drop
!
.
(Information Deleted)
.
map-list RFC1483_2
ip 2.2.0.1 atm-vc 109 broadcast
ip 11.1.10.1 atm-vc 110 broadcast

Step 3   Use the show interfaces atm command to confirm the configuration of the ingress ATM interface connected to the Cisco 7500 router.

Switch# show interfaces atm 0/0/0
ATM0/0/0 is up, line protocol up
Hardware is quad_oc12suni
   Internet address is 10.0.1.26/30
MTU 4470 bytes, sub MTU 4470, BW 622080 Kbit, DLY 0 usec,
      rely 255/255, load 1/255
Encapsulation ATM, loopback set, keepalive not supported
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 4000 bits/sec, 9 packets/sec
5 minute output rate 4000 bits/sec, 9 packets/sec
16300 packets input, 863900 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
        0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
16808 packets output, 890824 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out

Step 4   Confirm the interface and protocol are both up.

Step 5   Use the show interfaces atm command to confirm the configuration of the ATM router module interface.

Switch# show interfaces atm 10/0/1
ATM10/0/1 is up, line protocol is up
Hardware is ATM router module_port, address is 0090.2141.bc58 (bia 0090.2141.bc58)
SVC idle disconnect time: 300 seconds
MTU 1500 bytes, sub MTU 1500, BW 1000000 Kbit, DLY 10 usec,
     rely 255/255, load 1/255
Encapsulation ATM, loopback not set, keepalive not supported
Full-duplex, 1000Mb/s, 100BaseFX
ARP type: ARPA, ARP Timeout 00:15:00
Last input 00:02:13, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
23 packets input, 10352 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
        0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 watchdog, 0 multicast
23 packets output, 10352 bytes, 2 underruns
2 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out

Step 6   Confirm the ATM router module interface and protocol are both up.

Step 7   Use the show atm vc interfaces atm command with VPI 0 and VCI 109 to confirm the configuration of the ingress ATM interface connected to the Cisco 7500 router.

Switch# show atm vc interfaces atm 0/0/0 0 109
Interface: ATM0/0/0, Type: quad_oc12suni
VPI = 0 VCI = 109
Status: UP
Packet-discard-option: enabled
Usage-Parameter-Control (UPC): drop
Wrr weight: 2
Cross-connect-interface: ATM10/0/1, Type: arm_port
Cross-connect-VPI = 2
Cross-connect-VCI = 109
Threshold Group: 5, Cells queued: 0
Rx cells: 0, Tx cells: 0
Tx Clp0:0, Tx Clp1: 0
Rx Clp0:0, Rx Clp1: 0
Rx Upc Violations:0, Rx cell drops:0
Rx pkts:0, Rx pkt drops:0
Rx connection-traffic-table-index: 110
Rx service-category: UBR (Unspecified Bit Rate)

Step 8   Confirm the Status is up.

Step 9   Confirm that the Cross-connect-interface is the ATM router module internal interface.

Step 10   Again use the show atm vc interfaces atm command with VPI 0 and VCI 109 on the ingress ATM interface connected to the Cisco 7500 router, to confirm that the cell and packet numbers are incrementing.

Switch# show atm vc interfaces atm 0/0/0 0 109
Interface: ATM0/0/0, Type: quad_oc12suni
VPI = 0 VCI = 109
Status: UP
Packet-discard-option: enabled
Usage-Parameter-Control (UPC): drop
Wrr weight: 2
Cross-connect-interface: ATM10/0/1, Type: arm_port
Cross-connect-VPI = 2
Cross-connect-VCI = 109
Threshold Group: 5, Cells queued: 6
Rx cells: 15, Tx cells: 0
Tx Clp0:0, Tx Clp1: 0
Rx Clp0:15, Rx Clp1: 0
Rx Upc Violations:5, Rx cell drops:9
Rx pkts:0, Rx pkt drops:5
Rx connection-traffic-table-index: 110
Rx service-category: UBR (Unspecified Bit Rate)

Step 11   Check the Rx cells fields. The numbers should have incremented from the previous display.

Step 12   From the downstream Cisco 7500 router use the ping command, with the IP address of the ATM router module, to send five ICMP messages.

C7500# ping 2.2.0.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.0.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/3)

Step 13   Confirm that the Success rate is 0.

Step 14   From the downstream router, use the extended ping ip command, with the IP address of the ATM router module, to send five 64-byte ICMP messages.

C7500#ping ip
Target IP address: 2.2.0.2
Repeat count [5]:
Datagram size [100]: 64
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 64-byte ICMP Echos to 2.2.0.2, timeout is 2 seconds:
.!.!.
Success rate is 40 percent (2/5), round-trip min/avg/max = 1/1/1 ms
C7500#

Step 15   Check the Success rate field. Note that the success rate improved to 40 percent after you changed the ICMP datagram size to 64 bytes, from the default 100 bytes used in the previous ping command attempt.

Step 16   Again use the show atm vc interfaces atm command with VPI 0 and VCI 109 on the ingress ATM interface connected to the Cisco 7500 router.

Switch# show atm vc interface atm 0/0/0 0 109
Interface: ATM0/0/0, Type: quad_oc12suni
VPI = 0 VCI = 109
Status: UP
Threshold Group: 5, Cells queued: 0
Rx cells: 25, Tx cells: 4
Tx Clp0:4, Tx Clp1: 0
Rx Clp0:25, Rx Clp1: 0
Rx Upc Violations:9, Rx cell drops:14
Rx pkts:2, Rx pkt drops:8
Rx connection-traffic-table-index: 110

Step 17   Check the Rx cells field. Notice that the number is incrementing.

Step 18   Check the values in Rx Upc Violations, Rx cell drops, and Rx pkt drops fields. These values are also incrementing proving that the aggressive policing, configured with the atm connection-traffic-table-row index 110 ubr pcr 1 command setting the peak cell rate to 1, is working correctly.




If you determine that the ATM router module interface is configured incorrectly, refer to the "Configuring ATM Router Module Interfaces" chapter in the
ATM Switch Router Software Configuration Guide .

Troubleshooting RFC 1577 on ATM Router Module Connections

Classical IP over ATM is an IETF protocol that uses high speed ATM connections to provide better connections between IP members. The classic logical IP subnet (LIS) is implemented over an ATM switching network using an ATMARP server to replace the broadcast ARP service. IP over ATM is a Layer 3 switching service, where IP and ARP datagrams are encapsulated in AAL5 using IETF RFC1483 LLC/SNAP encapsulation as the default. RFC1577 provides for "best effort" service only. However, Resource Reservation Protocol (RSVP) over ATM enhances classical IP to support RSVP signalling, allowing differentiated QoS over an ATM network.

Troubleshooting RFC 1577 Problems on the ATM Router Module Commands

To display and troubleshoot the ATM router module and RFC 1577 configuration, use the following commands:

Command Purpose

show running-config

Shows the status of the configuration and physical interfaces.

show interfaces atm card/subcard/port

Shows the status of the physical interface.

show atm vc interface card/subcard/port.subinterface

Displays the ATM layer connection information about the virtual connection.

ping ip-address

Confirms the IP connection and increments the transmit and receive cell counters.

show atm map

Confirms the static connection to the ATM ARP server.

Figure 13-6 is an example network of a switch router with an ATM router module configured with two RFC 1577 connections between Ethernet networks and an ATM network.


Figure 13-10   ATM Router Module RFC 1577 Example Network


This example network is used in the following troubleshooting steps.

Follow these steps to troubleshoot the ATM router module, shown in Figure 13-10, configured with RFC 1577:

Step 1   Use the following commands to configure RFC 1577 for the example network shown in Figure 13-10.

Switch# config term
Switch(config)# interface atm 10/0/1.1 multipoint
Switch(config-if)# ip address 1.1.1.2 255.255.0.0
Switch(config-if)# atm arp-server nsap 47.009181000000009021418801.009021418801.00
Switch(config-if)# atm pvc 2 102 pd on inarp 5 interface ATM0/0/0 0 102
 Switch(config-if)# exit
Switch(config)# interface atm 10/0/1.3 multipoint
Switch(config-if)# ip address 3.3.0.2 255.255.0.0
Switch(config-if)# atm arp-server nsap 47.009181000000009021418801.0050BD9B2160.0A
Switch(config-if)# atm pvc 2 103 pd on inarp 5 interface ATM0/0/1 0 103
 Switch(config-if)# end
Switch#

Step 2   Use the show running-config command to confirm your configuration.

Switch# show running-config
Building configuration...
Current configuration:
!
!
interface ATM10/0/1.1 multipoint
ip address 172.20.52.41 255.255.255.224
atm arp-server nsap 47.00918100000000E04FACB401.00E04FACB401.00
atm pvc 2 102 pd on inarp 5 interface ATM0/0/0 0 102
!

The following process describes troubleshooting basic connectivity problems with RFC 1577 networks. In the example shown in Figure 13-10, the Cisco 7500 router connected to Ethernet 1.1.0.0 is acting as the ARP server.

Step 1   Using the show atm map command, confirm that both the switch router and the Cisco 7500 router connected to Ethernet 3.3.0.0 have connections to the ARP server. If they are connected, they can ask the ARP server for an IP-to-ATM address resolution.

Step 2   To test the switch router configuration, use the debug atm arp command on the switch router, to see whether it is sending out an ARP request to the ARP server router.

Step 3   From the Cisco 7500 router connected to Ethernet 1.1.0.0 (and acting as the ARP server), confirm it is receiving the ARP request and responding to it with a positive acknowledgment by using the debug atm arp command.

Step 4   On the ARP server, use the debug atm arp command to confirm it is receiving the ARP requests and responding with a positive acknowledgment.

When the IP-to-ATM address is resolved, the Cisco 7500 router connected to Ethernet 3.3.0.0 should be able to make a call to the ATM address of the switch router ATM router module. If the Cisco 7500 router still can not connect to the switch router ATM router module, the problem is probably the call setup. Refer to the "Troubleshooting RFC 1483 on ATM Router Module Connections" section.




If you determine that RFC 1577 on the interface is configured incorrectly, refer to the "Configuring IP over ATM" chapter in the ATM Switch Router Software Configuration Guide .

Troubleshooting OAM on ATM Router Module Connections

OAM performs fault management and performance management functions at the ATM management (M)-plane layer.

Note   Current OAM implementation supports only the fault management function, which includes connectivity verification and alarm surveillance.

The ATM switch router has full support for the following ATM OAM cell flows:

  • F4 flows—OAM information flows between network elements (NEs) used within virtual paths, to report an unavailable path or a virtual path (VP) that cannot be guaranteed.
  • F5 flows—OAM information flows between NEs used within virtual connections, to report degraded virtual channel (VC) performance such as late arriving cells, lost cells, and cell insertion problems.

Both F4 and F5 flows can be configured as either end-to-end loopback or segment-loopback and used with alarm indication signal (AIS) and remote defect indication (RDI) functions.

Troubleshooting OAM Problems on the ATM Router Module Commands

To display the ATM router module and OAM configuration, use the following commands:

Command Purpose

show atm traffic

Displays the ATM layer traffic information for all of the ATM interfaces.

show atm vc interface atm card/subcard/port.subinterface VPI VCI

Displays the ATM layer connection information about the virtual connection.

show atm vc traffic interface atm card/subcard/port VPI VCI

Displays information about the ATM virtual connection.

To configure OAM on the ATM router module, refer to the "Configuring Operation, Administration, and Maintenance" chapter in the ATM Switch Router Software Configuration Guide .

Figure 13-6 is an example network of a switch router with an ATM router module having OAM configured on the ATM router module and the connecting ATM interfaces.


Figure 13-11   ATM Router Module OAM Example Network


This example network is used in the following troubleshooting steps.

Follow these steps to configure and troubleshoot the ATM router module with OAM configured (see the example network shown in Figure 13-11):

Step 1   At switch router c8540-1, use the following commands to configure the ATM interface connected to switch router c8540-2, to perform OAM fault management.

c8540-1(config)# interface atm 0/0/0.5 point-to-point
c8540-1(config-subif)# atm pvc 2 105 int atm 0/0/0 0 105
c8540-1(config-subif)# atm oam interfaces atm 0/0/0 0 105 end-loopback
% OAM: Connection level end to end loopback is enabled
c8540-1(config-subif)#

In this example, the system message "% OAM: Connection level end to end loopback is enabled" appears, indicating the subinterface is correctly enabled.

Step 2   At switch router c8540-1, use the show running-config command to confirm configuration of the ATM interface connected to switch router c8540-2 and the ATM route module interface.

c8540-1# show running-config
Building configuration...
Current configuration:
!
.
(Information Deleted)
.
interface ATM0/0/0
no ip address
no ip route-cache distributed
no atm ilmi-keepalive
!
interface ATM0/0/0.5 point-to-point
ip address 11.1.5.2 255.255.255.252
pvc 0/105
oam-pvc manage 5
encapsulation aal5snap
!
.
(Information Deleted)
.
interface ATM10/0/1
no ip address
no ip directed-broadcast
logging event subif-link-status
arp timeout 900
!
interface ATM10/0/1.5 point-to-point
ip address 11.1.5.1 255.255.255.252
no ip directed-broadcast
atm pvc 2 105 pd on interface ATM0/0/0 0 105
atm oam interface ATM0/0/0 0 105 end-loopback
!

Step 3   At router c7576-1, use the show atm traffic command to confirm the F5 OAM cells are being received.

c7576-1# show atm traffic
.
(Information Deleted)
.
348 OAM cells received
F5 InEndloop: 348, []
586 OAM cells sent
F5 OutEndloop: 586, []

Step 4   At router c7576-1, use the show atm traffic command again, to confirm the F5 OAM cells are incrementing.

c7576-1# show atm traffic
.
(Information Deleted)
.
397 OAM cells received
F5 InEndloop: 397, []
635 OAM cells sent
F5 OutEndloop: 635, []

Step 5   At router c8540-1, use the show atm vc interfaces atm command with the VPI and VCI parameters to confirm the ATM router module subinterface status and configuration.

c8540-1# show atm vc interfaces atm 10/0/1.5 2 105
Interface: ATM10/0/1, Type: arm_port
VPI = 2 VCI = 105
Status: UP
Time-since-last-status-change: 00:34:41
Connection-type: PVC
.
(Information Deleted)
.
Cross-connect OAM-configuration: End-to-end-loopback-on
Cross-connect OAM-state: OAM-Up
OAM-Loopback-Tx-Interval: 5

Step 6   Check the Status field. It should be UP.

Step 7   Check the Time-since-last-status-change field. It should indicate the time since you enabled OAM on the subinterface.

Step 8   Check the Cross-connect OAM-configuration field. It should indicate End-to-end-loopback-on.

Step 9   Check the Cross-connect OAM-state field. It should indicate OAM-Up.

Step 10   To demonstrate an OAM failure, delete the PVC between switch router c8540-1 and switch router c8540-2 from the switch router c8540-2 end of the PVC.

c8540-2(config-if)# no atm pvc 0 105 int atm 1/0/1 0 105

Step 11   At router c7576-1, a system error message appears as in the following:

c7576-1#00:43:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/0/0.5, changed state to down

The system error message "%LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/0/0.5, changed state to down" indicates the subinterface ATM 0/0/0.5 has changed status to down because the PCV was disabled on switch router c8540-2.

Step 12   At router c7576-1, use the show atm traffic command to check the OAM cells received and sent.

c7576-1# show atm traffic
.
(Information Deleted)
.
442 OAM cells received
708 OAM cells sent

Step 13   At router c7576-1, use the show atm traffic command a second time, and check the number of OAM cells received and sent.

c7576-1# show atm traffic
.
(Information Deleted)
.
442 OAM cells received
734 OAM cells sent

Step 14   Check the number before the OAM cells received field. Since the number of OAM cells received has not incremented since the previous display, this confirms the connection is down and the OAM cells are sent but not received.

Step 15   At router c8540-1, use the show atm vc interfaces atm command with the VPI and VCI parameters to confirm the ATM router module subinterface OAM status and configuration.

c8540-1# show atm vc interfaces atm 10/0/1.5 2 105
Interface: ATM10/0/1, Type: arm_port
VPI = 2 VCI = 105
Status: UP
Time-since-last-status-change: 00:43:05
Cross-connect OAM-configuration: End-to-end-loopback-on
Cross-connect OAM-state: OAM-Up End-to-end-loopback-failed
OAM-Loopback-Tx-Interval: 5

Step 16   Check the Status field. It should be UP.

Step 17   Check the Time-since-last-status-change field. It should indicate the time since you enabled OAM on the subinterface.

Step 18   Check the Cross-connect OAM-configuration field. It should indicate End-to-end-loopback-on.

Step 19   Check the Cross-connect OAM-state field. It should indicate OAM-Up, but that the End-to-end-loopback-failed because the PCV was disabled on switch router c8540-2.

The effect of OAM failure on an interface or subinterface is as follows:

  • On the ATM router module the interface or subinterface status and VC remain UP, causing the following:
    • the VC remains in switch fabric
    • OAM loopback cells are still sent, but not received
    • The routing or bridging layer is informed to remove routes or MAC addresses learned over the affected VC
  • On the router, the subinterface status and VC status change to DOWN



If you determine that the OAM interface is configured incorrectly, refer to the "Configuring Operation, Administration, and Maintenance" chapter in the ATM Switch Router Software Configuration Guide .