The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The ATM OAM Support of F5 Continuity Check feature provides the ability to detect connectivity failures at the ATM layer by introducing Operation, Administration, and Maintenance (OAM) support for F5 segment and end-to-end Continuity Check (CC) cells. This feature also enables network administrators to detect connectivity failures on each PVC. Simple Network Management Protocol (SNMP) notifications are generated when CC cells indicate virtual circuit (VC) connectivity failure and notify the administrator that continuity for a particular permanent virtual circuits (PVCs) has been lost while the PVC is still operationally up.
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 Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Extended ATM PVC and ATM OAM F5 CC traps cannot be used at the same time as the legacy ATM PVC trap. The legacy ATM PVC trap must be disabled by using the no snmp-server enable traps atm pvc command before extended ATM PVC traps and ATM OAM F5 CC traps can be configured. If the extended ATM PVC traps or ATM OAM F5 CC traps are enabled, you must disable them by using the no snmp-server enable traps atm pvc extension command before you can enable the legacy ATM PVC trap.
Cisco digital subscriber line access multiplexers (DSLAMs) and ATM switches (such as the Cisco LS1010) do not forward F5 OAM segment CC cells.
The ATM OAM Support for F5 Continuity Check feature is supported on ATM PVCs only.
The ATM OAM Support for F5 Continuity Check feature introduces Operation, Administration, and Maintenance (OAM) support for the use of F5 segment and end-to-end Continuity Check (CC) cells to detect connectivity failures at the ATM layer. This feature also introduces new Simple Network Management Protocol (SNMP) notifications that are generated when CC cells indicate virtual circuit (VC) connectivity failure.
ATM OAM F5 CC cells provide an in-service tool optimized to detect connectivity problems at the VC level of the ATM layer. CC cells are sent between a router designated as the source location and a router designated as the sink location. The local router can be configured as the source, as the sink, or as both the source and the sink.
The ATM OAM Support for F5 Continuity Check feature enables network administrators to detect connectivity failures on a per-PVC basis. The feature also provides support for SNMP notifications that notify the administrator that continuity for a particular PVC has been lost while the PVC is still operationally up.
The ATM OAM Support for F5 Continuity Check feature introduces three new SNMP notifications that indicate CC segment, CC end-to-end, and alarm indication signal/remote defect indication (AIS/RDI) failures to the Network Management System (NMS). The notifications include information such as the number of OAM failures that occurred and time stamps showing when the first and last failures occurred during the notification interval for permanent virtual circuits (PVCs). In addition to notifications, MIB tables are maintained to provide information about the failures on PVCs.
Perform the following steps to configure ATM OAM F5 CC support on an ATM PVC.
Perform the following steps to disable ATM OAM F5 CC support on an ATM PVC and to configure the PVC to deny OAM F5 CC activation requests.
Perform the following steps to configure a PVC to send ATM OAM F5 CC deactivation requests when the PVC is already down.
Perform the following steps to enable the MIB and send SNMP notifications that support ATM OAM F5 CC management.
To verify the configuration and operation of ATM OAM F5 CC management, perform the following steps:
Step 1 | Use the show running-config command to verify configuration. The following is sample output for the show running-config command: Example:
Router# show running-config interface atm0
Building configuration...
Current configuration :152 bytes
!
interface ATM0
no ip address
shutdown
no atm ilmi-keepalive
pvc 1/40
oam-pvc manage cc segment direction both
!
dsl operating-mode auto
end |
Step 2 | Use the show atm pvccommand to verify that ATM OAM F5 CC management is enabled and to display the activation and deactivation retry counts and retry frequency values. This command also displays the CC state of the PVC. The following is sample output for the show atm pvc command: Example:
Router# show atm pvc 1/40
ATM0:VCD:1, VPI:1, VCI:40
UBR, PeakRate:0
AAL5-LLC/SNAP, etype:0x0, Flags:0xC20, VCmode:0x0
OAM frequency:0 second(s), OAM retry frequency:1 second(s)
OAM up retry count:3, OAM down retry count:5
OAM END CC Activate retry count:3, OAM END CC Deactivate retry count:3
OAM END CC retry frequency:30 second(s),
OAM SEGMENT CC Activate retry count:3, OAM SEGMENT CC Deactivate retry count:3
OAM SEGMENT CC retry frequency:30 second(s),
OAM Loopback status:OAM Disabled
OAM VC state:Not Managed
ILMI VC state:Not Managed
OAM END CC status:OAM CC Ready
OAM END CC VC state:Verified
OAM SEGMENT CC status:OAM CC Active
OAM SEGMENT CC VC state:Verified
InARP frequency:15 minutes(s)
InPkts:0, OutPkts:0, InBytes:0, OutBytes:0
InPRoc:0, OutPRoc:0, Broadcasts:0
InFast:0, OutFast:0, InAS:0, OutAS:0
Giants:0
OAM cells received:20
F5 InEndloop:0, F5 InSegloop:0,
F5 InEndcc:0, F5 InSegcc:20, F5 InAIS:0, F5 InRDI:0
F4 InEndloop:0, F4 InSegloop:0, F4 InAIS:0, F4 InRDI:0
OAM cells sent:20
F5 OutEndloop:0, F5 OutSegloop:0,
F5 OutEndcc:0, F5 OutSegcc:20, F5 OutRDI:0
F4 OutEndloop:0, F4 OutSegloop:0, F4 OutRDI:0
OAM cell drops:1
Status:UP |
The following example shows how to configure ATM OAM CC support over the segment and configure the router to function as the source. The frequency at which CC activation and deactivation requests will be sent over the segment is also configured.
interface atm 0 ip address 10.0.0.3 255.255.255.0 pvc 0/40 oam-pvc manage cc segment direction source oam retry cc segment 10 10 30
The following example shows how to disable ATM OAM F5 CC support and configure the VC to deny CC activation requests:
interface atm 0 ip address 10.0.0.3 255.255.255.0 pvc 0/40 oam-pvc manage cc segment deny
The following example shows how to send a CC deactivation request across the segment when PVC 0/40 goes down:
interface atm 0 ip address 10.0.0.3 255.255.255.0 pvc 0/40 no oam-pvc manage cc segment deactivate-down-vc
In the following example, the ATM OAM F5 CC notifications and an extended ATM PVC notification are enabled. If CC cells detect connectivity failures on PVC 0/40, host 172.16.61.90 will receive the SNMP notifications.
! Configure SNMP support on your router: snmp-server community public snmp-server host 172.16.61.90 public ! ! Enable SNMP notifications: snmp-server enable traps atm pvc extension mibversion 2 snmp-server enable traps atm pvc extension oam failure aisrdi snmp-server enable traps atm pvc extension oam failure endcc snmp-server enable traps atm pvc extension oam failure segmentcc snmp-server enable traps atm pvc extension oam failure loopback snmp-server enable traps atm pvc extension up
The following sections provide references related to the ATM OAM Support for F5 Continuity Check feature.
Related Topic |
Document Title |
---|---|
Configuring ATM |
"Configuring ATM" |
ATM commands |
Cisco IOS Asynchronous Transfer Mode Command Reference |
Configuring SNMP support |
"Configuring SNMP Support" |
SNMP commands |
Cisco IOS Network Management Command Reference |
Standard |
Title |
---|---|
No new or modified standards are supported by this feature. |
-- |
MIB |
MIBs Link |
---|---|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFC |
Title |
---|---|
No new or modified RFCs are supported by this feature. |
-- |
Description |
Link |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS Asynchronous Transfer Mode Command Reference. For information about all Cisco IOS commands, use the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or the Cisco IOS Master Command List, All Releases, at http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html.
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 | Feature Information for ATM OAM Support for F5 Continuity Check |
Feature Name |
Releases |
Feature Information |
---|---|---|
ATM OAM Support for F5 Continuity Check |
12.2(13)T |
The ATM OAM Support for F5 Continuity Check feature introduces three new SNMP notifications that indicate failures to the network management system (NMS). This feature was introduced in 12.2(13)T that supported Cisco 827 and 1700 series. The following commands were introduced or modified: debug atm oam cc, oam-pvc manage cc, oam-pvc manage cc deny, oam retry cc, snmp-server enable traps atm pvc extension, snmp-server enable traps atm pvc extension mibversion. |
AIS --alarm indication signal. In a T1 transmission, an all-ones signal transmitted in lieu of the normal signal to maintain transmission continuity and to indicate to the receiving terminal that there is a transmission fault that is located either at or upstream from the transmitting terminal.
MIB --Management Information Base. Database of network management information that is used and maintained by a network management protocol such as SNMP. The value of a MIB object can be changed or retrieved using SNMP commands, usually through a network management system (NMS).
NMS --network management system. An application or suite of applications designed to monitor networks using SNMP.
OAM --Operation, Administration, and Maintenance. OAM cells provide a virtual-circuit-level loopback in which a router responds to the cells, demonstrating that the circuit is up and the router is operational.
PVC --permanent virtual circuit. Virtual circuit that is permanently established. In ATM terminology, PVC also stands for permanent virtual connection.
RDI --remote defect indication. In ATM, when the physical layer detects loss of signal or cell synchronization, RDI cells are used to report a virtual path connection/virtual channel connection (VPC/VCC) failure. RDI cells are sent upstream by a VPC/VCC endpoint to notify the source VPC/VCC endpoint of the downstream failure.
SNMP --Simple Network Management Protocol. An application-layer protocol that provides a message format for communication between SNMP managers and agents and is used almost exclusively in TCP/IP networks. SNMP provides a means to monitor and control network devices and to manage configurations, statistics collection, performance, and security.
SNMP trap --Message from an SNMP agent alerting the SNMP manager to a condition on the network.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)
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.