Table of Contents

Configuring Operation, Administration, and Maintenance

This chapter describes the Operation, Administration, and Maintenance (OAM) implementation on the ATM switch router.

Note   This chapter provides advanced configuration instructions for the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers. For complete descriptions of the commands mentioned in this chapter, refer to the ATM Switch Router Command Reference publication.

This chapter includes the following sections:

OAM Overview

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:

Both F4 and F5 flows can be configured as either end-to-end or segment-loopback and used with alarm indication signal (AIS) and remote defect indication (RDI) functions. An AIS is a signal transmitted downstream informing the destination that an upstream failure has been detected. An RDI signal indicates that a failure has occurred at the far end of an ATM network.

Note   Cells can be sent either on demand or periodically to verify link and connection integrity.

In addition to the standard OAM functions, the ATM switch router can also send OAM pings. OAM cells containing the ATM node addresses or IP addresses of intermediate switches allow network administrators to determine the integrity of a chosen connection at any intermediate point along the connection, allowing for network connection debugging and troubleshooting.

OAM software implements ATM Layer F4 and F5 OAM fault management functions. OAM performs standard loopback (end-to-end or segment) and fault detection and notification (AIS and RDI) for each connection. It also maintains a group of timers for the OAM functions. When there is an OAM state change such as loopback failure, OAM software notifies the connection management software. The network operator can enable or disable OAM operation for the following switch components:

If OAM operation is disabled, outgoing OAM cells (AIS, RDI and loopbacks) are not generated and AIS and RDI cells that arrive at connection endpoints are discarded.

To support various OAM operations, the ATM switch router hardware provides OAM cell routing functions on a per-connection basis for each direction and for different OAM cell spans (segment and end-to-end). The hardware OAM cell routing determines the destination of an OAM cell received from the link or the network and then determines whether OAM cells are processed by the switch software.

The hardware can perform the following functions on OAM cells:

An ATM connection consists of a group of network points that form the edges of each ATM switch or end system.

Each point can be one of the following:

The following sections describe the OAM tasks:

Configuring OAM Functions

This section describes OAM commands in EXEC, global, and interface configuration mode.

Configuring OAM for the Entire Switch (Catalyst 8540 MSR)

To enable OAM operations for the Catalyst 8540 MSR, use the global configuration command, as shown in the following table:

Note   The number of maximum OAM configured connections allowed ranges from 1 to 3200; the default is 3200.

Examples

The following example shows how to enable AIS and segment loopback for the entire switch:

The following example shows how to configure the ATM OAM connection maximum to 1600:

Configuring OAM for the Entire Switch (Catalyst 8510 MSR and LightStream 1010)

To enable OAM operations for the entire Catalyst 8510 MSR and LightStream 1010 ATM switch router, use the global configuration command, as shown in the following table:

Note   The number of maximum OAM configured connections allowed ranges from 1 to 3200; the default is 3200.

Examples

The following example shows how to enable AIS and segment loopback for the entire switch:

The following example shows how to configure the ATM OAM connection maximum to 1600:

Configuring the Interface-Level OAM

To enable OAM operations on an interface, perform the following steps, beginning in global configuration mode:

Examples

The following example shows how to enable OAM AIS and end-to-end loopback on interface 3/0/0:

The following example shows how to enable OAM AIS and end-to-end loopback on interface 3/0/0, VPI = 50, VCI = 100:

Note   You can use only VPI values to configure OAM operations on VP connections.

In interface configuration command mode, you can enable or disable OAM operations on existing connections on different interfaces by specifying interface atm card/subcard/port. The following example disables OAM AIS flows at interface 1/0/0 while in interface 3/0/0:

Checking the ATM Connection (Catalyst 8540 MSR)

To check ATM connection reachability and network connectivity on the Catalyst 8540 MSR, use the ping EXEC command, as shown in the following table:

You can ping a neighbor switch by selecting the segment loopback option. In privileged EXEC mode, you can select various other parameters such as repeat count and timeout values.

Examples

The following example shows the ping command used in normal mode to check a virtual channel connection (VCC) with a segment loopback flow:

The following example shows the ping command used in extended mode to check a VCC with end-to-end loopback flow:

Checking the ATM Connection (Catalyst 8510 MSR and LightStream 1010)

To check ATM connection reachability and network connectivity on the Catalyst 8510 MSR and LightStream 1010 ATM switch router, use the ping EXEC command, as shown in the following table:

You can use either an ATM address prefix or an IP address as a ping destination. You can ping a neighbor switch by selecting the segment loopback option. In privileged EXEC mode, you can select various other parameters such as repeat count and timeout values.

Examples

The following example shows the ping command used in normal mode to check a VCC with a segment loopback flow:

The following example shows the ping command used in extended mode to check a VCC with end-to-end loopback flow:

Note   If you do not enable the OAM segment loopback option, the ping command uses an OAM end-to-end loopback cell. If you do not provide a target address, the connection end point becomes the target.

Displaying the OAM Configuration

To display the OAM configuration, use the following EXEC command:

Example

The OAM configuration is displayed in the following example: