|
Table Of Contents
Prerequisites for the ATM OAM Ping Feature
Restrictions for the ATM OAM Ping Feature
Information About the ATM OAM Ping Feature
Benefits of the ATM OAM Ping Feature
How to Use the ATM OAM Ping Feature
Testing Network Connectivity Using ATM Interface Ping in the Normal Mode
Testing Network Connectivity Using ATM Interface Ping in the Interactive Mode
Configuration Examples for the ATM OAM Ping Feature
Verifying the Connectivity of a Specific PVC: Example
Testing Network Connectivity Using ATM Interface Ping in the Normal Mode: Example
Testing Network Connectivity Using ATM Interface Ping in the Interactive Mode: Example
Feature Information for the ATM OAM Ping Feature
ATM OAM Ping
First Published: December 15, 2001Last Updated: November 20, 2009The ATM OAM Ping feature sends an ATM Operation, Administration, and Maintenance (OAM) packet to confirm the connectivity of a specific permanent virtual circuit (PVC). The status of the PVC is displayed when a response to the OAM packet is received. The ATM OAM Ping feature allows the network administrator to verify PVC integrity and facilitates ATM network troubleshooting.
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 the ATM OAM Ping Feature" 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 Ping Feature
•Restrictions for the ATM OAM Ping Feature
•Information About the ATM OAM Ping Feature
•How to Use the ATM OAM Ping Feature
•Configuration Examples for the ATM OAM Ping Feature
•Feature Information for the ATM OAM Ping Feature
Prerequisites for the ATM OAM Ping Feature
A PVC corresponding to the virtual path identifier (VPI) and virtual channel identifier (VCI) values entered with the ping command should already exist. (For Cisco 827 series routers, the virtual circuit need not exist.)
For information about how to configure ATM PVCs, see the section "Configuring PVCs" in the chapter "Configuring ATM" in the Cisco IOS Asynchronous Transfer Mode Configuration Guide.
Restrictions for the ATM OAM Ping Feature
The ATM OAM Ping feature does not support pings based on the following:
•Network service access point (NSAP) addresses
•Multiple-hop loopbacks
•Loopback location identification
Information About the ATM OAM Ping Feature
To use the ATM OAM Ping feature, you must understand the following concepts:
•Benefits of the ATM OAM Ping Feature
•How to Use the ATM OAM Ping Feature
Benefits of the ATM OAM Ping Feature
The ATM OAM Ping feature modifies the ping command, which can be used to send an OAM packet to verify PVC connectivity. The status of the PVC is displayed when a response to the OAM packet is received. This is a common method for testing the accessibility of devices.
The ping atm interface atm command provides two ATM OAM ping options:
•End loopback—Verifies end-to-end PVC integrity.
•Segment loopback—Verifies PVC integrity to the immediate neighboring ATM device.
The ping atm interface atm command is used to determine the following:
•Whether a remote host is active or inactive.
•The round-trip delay in communicating with the host.
•Packet loss.
The simpler ping command provides an interactive mode for testing ATM network connectivity. The ping command first sends an OAM command loopback cell to the destination and then waits for an OAM response loopback cell. The ping is successful only when the following criteria are met:
•The OAM command loopback cell reaches the destination.
•The destination is able to send an OAM loopback response cell back to the source within a predetermined time called a timeout. The default value of the timeout is 2 seconds on Cisco routers.
How to Use the ATM OAM Ping Feature
The following sections describe tasks that use ping commands to test network connectivity in an ATM network:
•Testing Network Connectivity Using ATM Interface Ping in the Normal Mode (optional)
•Testing Network Connectivity Using ATM Interface Ping in the Interactive Mode (optional)
•Aborting a Ping Session (optional)
Testing Network Connectivity Using ATM Interface Ping in the Normal Mode
This section describes how to test the network connectivity by using the ping atm interface atm command in normal mode; that is, by entering all values for the ping test on the command line.
SUMMARY STEPS
1. enable
2. ping atm interface atm interface-number vpi-value [vci-value [end-loopback | seg-loopback] [repeat [timeout]]]
DETAILED STEPS
Testing Network Connectivity Using ATM Interface Ping in the Interactive Mode
This section describes how to test network connectivity by using the ping command; that is, by providing values for the ping test by typing the value after the prompts displayed and pressing the Enter key. Press the Enter key without supplying a value to use the default.
SUMMARY STEPS
1. enable
2. ping
DETAILED STEP
Aborting a Ping Session
To terminate a ping session, type the escape sequence Ctrl-Shift-6.
Configuration Examples for the ATM OAM Ping Feature
This section provides the following configuration examples:
•Verifying the Connectivity of a Specific PVC: Example
•Testing Network Connectivity Using ATM Interface Ping in the Normal Mode: Example
•Testing Network Connectivity Using ATM Interface Ping in the Interactive Mode: Example
Verifying the Connectivity of a Specific PVC: Example
The following example verifies the connectivity of a specific PVC by sending an ATM OAM packet and confirms the connectivity when it is successful:
Router# show atm pvc 0/500
VC 0/500 doesn't exist on interface ATM1/0 - cannot displayATM1/1.1: VCD: 2, VPI: 0, VCI: 500UBR, PeakRate: N/A (UBR VC)AAL5-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 END CC Activate retry count: 3, OAM END CC Deactivate retry count: 3OAM END CC retry frequency: 30 second(s),OAM SEGMENT CC Activate retry count: 3, OAM SEGMENT CC Deactivate retry count: 3OAM SEGMENT CC retry frequency: 30 second(s),OAM Loopback status: OAM ReceivedOAM VC state: VerifiedILMI VC state: Not ManagedOAM END CC status: OAM CC ReadyOAM END CC VC state: VerifiedOAM SEGMENT CC status: OAM CC ReadyOAM SEGMENT CC VC state: VerifiedVC is managed by OAM.InARP frequency: 15 minutes(s)InPkts: 289035, OutPkts: 217088, InBytes: 21165546, OutBytes: 17367793InPRoc: 289039, OutPRoc: 289274InFast: 0, OutFast: 0, InAS: 1, OutAS: 2Out CLP=1 Pkts: 0OAM cells received: 119900F5 InEndloop: 119809, F5 InSegloop: 0,F5 InEndcc: 0, F5 InSegcc: 0, F5 InAIS: 92, F5 InRDI: 0OAM cells sent: 119902F5 OutEndloop: 119810, F5 OutSegloop: 0,F5 OutEndcc: 0, F5 OutSegcc: 0, F5 OutAIS: 0, F5 OutRDI: 92OAM cell drops: 0Status: UPTesting Network Connectivity Using ATM Interface Ping in the Normal Mode: Example
The following is sample output for the ping atm interface atm command in normal mode:
Router# ping atm interface atm1/1.1 0 500Type escape sequence to abort.Sending 5, 53-byte end-to-end OAM echoes, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 4/16/52 msRouter# ping atm interface atm1/1.1 0 500 seg-loopbackType escape sequence to abort.Sending 5, 53-byte segment OAM echoes, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 msRouter# ping atm interface atm1/1.1 0 500 end-loopback 100 25Type escape sequence to abort.Sending 100, 53-byte end-to-end OAM echoes, timeout is 25 seconds:!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Success rate is 100 percent (100/100), round-trip min/avg/max = 4/13/180 msRouter# ping atm interface atm1/1.1 0 500 seg-loopback 50 20Type escape sequence to abort.Sending 50, 53-byte segment OAM echoes, timeout is 20 seconds:!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Success rate is 100 percent (50/50), round-trip min/avg/max = 1/1/4 msRouter# show atm pvc 0/500VC 0/500 doesn't exist on interface ATM1/0 - cannot displayATM1/1.1: VCD: 2, VPI: 0, VCI: 500UBR, PeakRate: N/A (UBR VC)AAL5-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 END CC Activate retry count: 3, OAM END CC Deactivate retry count: 3OAM END CC retry frequency: 30 second(s),OAM SEGMENT CC Activate retry count: 3, OAM SEGMENT CC Deactivate retry count: 3OAM SEGMENT CC retry frequency: 30 second(s),OAM Loopback status: OAM ReceivedOAM VC state: VerifiedILMI VC state: Not ManagedOAM END CC status: OAM CC ReadyOAM END CC VC state: VerifiedOAM SEGMENT CC status: OAM CC ReadyOAM SEGMENT CC VC state: VerifiedVC is managed by OAM.InARP frequency: 15 minutes(s)InPkts: 290975, OutPkts: 219031, InBytes: 21306632, OutBytes: 17509085InPRoc: 290979, OutPRoc: 291219InFast: 0, OutFast: 0, InAS: 1, OutAS: 2Out CLP=1 Pkts: 0OAM cells received: 120881F5 InEndloop: 120734, F5 InSegloop: 55,F5 InEndcc: 0, F5 InSegcc: 0, F5 InAIS: 92, F5 InRDI: 0OAM cells sent: 120882F5 OutEndloop: 120735, F5 OutSegloop: 55,F5 OutEndcc: 0, F5 OutSegcc: 0, F5 OutAIS: 0, F5 OutRDI: 92OAM cell drops: 0Status: UPTesting Network Connectivity Using ATM Interface Ping in the Interactive Mode: Example
The following is sample output for the ping command in the interactive mode:
Router# pingProtocol [ip]: atmATM Interface: atm1/1.1VPI value [0]: 0VCI value [1]: 500Loopback - End(0), Segment(1) [0]:Repeat Count [5]:Timeout [2]:Type escape sequence to abort.Sending 5, 53-byte end-to-end OAM echoes, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 4/9/12 msAdditional References
The following sections provide references related to the ATM OAM Ping feature.
Related Documents
Related Topic Document TitleConfiguring PVCs and mapping a protocol address to a PVC while configuring ATM
Configuring PVCs section of Cisco IOS Configuring ATM Feature Guide
Configuring ATM
ATM commands, complete command syntax, command mode, command history, defaults, usage guidelines, and examples
Configuring ATM OAM traffic reduction
ATM OAM Traffic Reduction feature module
Configuring PVCs with or without OAM
Using OAM for PVC Management sample configuration
Detecting failures when using OAM cells and PVC management
Troubleshooting PVC Failures When Using OAM Cells and PVC Management technical note
Cisco IOS commands
Standards
MIBs
MIB 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 the ATM OAM Ping Feature
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://www.cisco.com/go/cfn. 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 and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental
© 2001-2009 Cisco Systems, Inc. All rights reserved.