Table Of Contents
Prerequisites for the ATM OAM Traffic Reduction Feature
Restrictions for the ATM OAM Traffic Reduction Feature
Information About the ATM OAM Traffic Reduction Feature
How to Configure the ATM OAM Traffic Reduction Feature
Configuring ATM OAM Traffic Reduction on an ATM Interface
Configuring ATM OAM Traffic Reduction on a VC Class
Verifying ATM OAM Traffic Reduction
Configuration Examples for ATM OAM Traffic Reduction
ATM OAM Traffic Reduction on an ATM Interface: Example
ATM OAM Traffic Reduction on a VC Class: Example
Verifying ATM OAM Traffic Reduction: Example
Feature Information for ATM OAM Traffic Reduction
ATM OAM Traffic Reduction
First Published: October 28, 2002Last Updated: October 4, 2009The ATM OAM Traffic Reduction feature is a mechanism for reducing overhead when loopback cells are being used for fault detection in bidirectional virtual circuits (VCs) over ATM.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for ATM OAM Traffic Reduction" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•Prerequisites for the ATM OAM Traffic Reduction Feature
•Restrictions for the ATM OAM Traffic Reduction Feature
•Information About the ATM OAM Traffic Reduction Feature
•How to Configure the ATM OAM Traffic Reduction Feature
•Configuration Examples for ATM OAM Traffic Reduction
Prerequisites for the ATM OAM Traffic Reduction Feature
The Operation, Administration, and Maintenance (OAM) loopback cells described in this document are defined in International Telecommunication Union (ITU) specification I.610 SERIES I: INTEGRATED SERVICES DIGITAL NETWORK, Maintenance principles, and understanding this specification is requisite to understanding the ATM OAM Traffic Reduction feature.
Restrictions for the ATM OAM Traffic Reduction Feature
•This feature supports only Permanent Virtual Circuits (PVCs) for F5 END_TO_END OAM loopback cells. This feature is not applicable for F4 OAM cells, AIS/RDI cells, or F5 SEGMENT OAM loopback cells.
•This feature breaks OAM loopback functionality when there is a unidirectional breakage and when retry frequency is configured to be the same as the F5 OAM loopback frequency.
Information About the ATM OAM Traffic Reduction Feature
To configure ATM OAM traffic reduction, you need to understand the following concept:
OAM Traffic Flow
The OAM management portion of a PVC sends OAM loopback cells at periodic intervals. When OAM management is enabled at both ends of the PVC, the cells are transmitted and looped back at both ends. This transmission is redundant, because the OAM cells travel through the same physical circuit twice.
In Figure 1, assume PVCs are configured between router R1 and router R2, and that OAM management is enabled on both ends of the PVC. Router R1, upon receiving OAM command cells from router R2, can stop its own OAM command cell transmission and can manage the link on the basis of incoming OAM command cells. Router R1 can reinitiate OAM command cell transmission upon discovering the absence of command cells from router R2.
Figure 1 ATM OAM Traffic Flow
When router R1 detects the first OAM command cell from router R2, time-stamp T1 is noted. When the next OAM command cell is detected, time-stamp T2 is noted. The interval T1 minus T2 provides the OAM the loopback frequency of router R2. The average value of this interval is taken by measuring it a random number of times. (The interval needs to be taken a random number of times to avoid a race condition that might happen when routers R1 and R2 implement this algorithm and the frequency is the same.)
At the end of the random time period, router R1 stops sending OAM command cells and starts the OAM traffic monitoring timer. This timer in router R1 checks for a change in interval frequency in router R2. If there is a change, the traffic monitoring timer is stopped and the VC goes into Retry mode and checks whether the link is still up. In Retry mode, OAM command loopback cells are transmitted at an interval of one per second for 3 seconds. If router R1 does not receive a response to the command cell, the link is changed to the Down state.
Note If ATM OAM traffic reduction is enabled on routers R1 and R2, then because of the random nature of the traffic reduction algorithm, either router can initiate OAM command cells and the other router will have to listen to the incoming OAM command cells.
If this feature is enabled on only one router (R1, for example), then the frequency of that router must be greater than or equal to the interval frequency set in the other router (R2) in order for router R1 to stop sending OAM command cells.
The ATM OAM Traffic Reduction feature is enabled by the oam-pvc command. When the optimum keyword is enabled, and when a change in the interval frequency of router R2 is detected, the VC initiates an OAM command cell from router R1 and does not go into Retry mode immediately. If no response is obtained, the VC goes into Retry mode and follows the OAM Retry procedure.
How to Configure the ATM OAM Traffic Reduction Feature
This section contains the following procedures.
•Configuring ATM OAM Traffic Reduction on an ATM Interface (optional)
•Configuring ATM OAM Traffic Reduction on a VC Class (optional)
•Verifying ATM OAM Traffic Reduction (optional)
Configuring ATM OAM Traffic Reduction on an ATM Interface
To configure ATM OAM traffic reduction on an ATM interface, use the following commands.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface atm interface-number
4. pvc interface-number
5. oam-pvc [frequency | manage [frequency [auto-detect [optimum] | keep-vc-up [seg aisrdi failure]] | auto-detect [optimum] | keep-vc-up [seg aisrdi failure] | loop-detection]]]
6. exit
DETAILED STEPS
Configuring ATM OAM Traffic Reduction on a VC Class
To configure ATM OAM traffic reduction on a VC class, use the following commands.
SUMMARY STEPS
1. enable
2. configure terminal
3. vc-class atm vc-class-name
4. oam-pvc [frequency | manage [frequency [auto-detect [optimum] | loop-detection]]]
5. exit
6. interface atm interface-number
7. class-int vc-class-name
8. pvc vpi/vci
9. exit
DETAILED STEPS
Verifying ATM OAM Traffic Reduction
To verify that the ATM OAM Traffic Reduction feature is working, perform the following steps.
SUMMARY STEPS
1. enable
2. show atm oam auto-detect [atm interface-number]
3. show atm pvc [interface atm type number[vpi/vci | vci | name] vpi/vci | vci | name]
DETAILED STEPS
Configuration Examples for ATM OAM Traffic Reduction
This section provides the following configuration examples to match the identified configuration tasks in the previous section:
•ATM OAM Traffic Reduction on an ATM Interface: Example
•ATM OAM Traffic Reduction on a VC Class: Example
•Verifying ATM OAM Traffic Reduction: Example
ATM OAM Traffic Reduction on an ATM Interface: Example
The following example enables ATM OAM traffic reduction on an ATM interface:
interface atm 1/0pvc 0/100oam-pvc manage auto-detect optimumATM OAM Traffic Reduction on a VC Class: Example
The following example enables ATM OAM traffic reduction using a VC class:
vc-class atmoam-pvc manage 10 auto-detect optimuminterface atm 1/0class-int testpvc 0/100pvc 0/200Verifying ATM OAM Traffic Reduction: Example
In the following examples, the output is displayed for each command in the task.
Sample Output for the show atm oam auto-detect Command
The following is sample output from the show atm oam auto-detect command:
Router# show atm oam auto-detect atm 2/0ATM OAM Auto Detect statistics on ATM2/0Number of VCs in Auto Detection:ATM OAM AUTO DETECT INIT : 0ATM OAM SENDING MONITORING : 0ATM OAM MONITORING : 0Number of VCs in OAM Loopback:DownRetry : 0UpRetry : 0Verified : 0Not Verified : 0Sample Output for the show atm pvc Command
The following is sample output from the show atm pvc command with ATM OAM traffic reduction enabled:
Router# show atm pvc 0/100ATM1/0: VCD: 1, VPI: 0, VCI: 100UBR, PeakRate: 149760AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0OAM frequency: 10 second(s), OAM retry frequency: 1 second(s)OAM up retry count: 3, OAM down retry count: 5OAM Loopback status: OAM ReceivedOAM VC state: VerifiedOAM Auto Detect state: ATM OAM AUTO DETECT INITOAM PEER frequency: 0 second(s)Last OAM Command Cell was received at 00:02:09ILMI VC state: Not ManagedAdditional References
The following sections provide references related to the ATM OAM Traffic Reduction feature.
Related Documents
Related Topic Document TitleConfiguring VC management
"Configuring ATM" chapter in the Cisco IOS Asynchronous Transfer Mode Configuration Guide
VC management commands
Standards
Standards TitleITU-I Specification
I.610 SERIES I: INTEGRATED SERVICES DIGITAL NETWORK, Maintenance principles
MIBs
MIBs MIBs LinkNone
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for ATM OAM Traffic Reduction
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2002-2009 Cisco Systems, Inc. All rights reserved.