Downloads |
Table Of Contents
ATM OAM Support for F5 Continuity Check
SNMP Support for ATM OAM F5 Continuity Checking
Configuring ATM OAM F5 CC Support
Configuring Denial of ATM OAM F5 CC Activation Requests
Configuring ATM OAM F5 CC Deactivation Requests to Be Sent upon PVC Failure
Configuring SNMP Notification Support for ATM OAM F5 CC Management
Verifying ATM OAM Support for F5 CC Management
Monitoring and Maintaining ATM OAM F5 CC Management
ATM OAM F5 CC Support on a PVC Configuration Example
Denial of ATM OAM F5 CC Activation Requests Configuration Example
Deactivation of ATM OAM F5 CC upon PVC Failure Example
Support for ATM OAM F5 CC SNMP Notifications Configuration Example
snmp-server enable traps atm pvc extension
ATM OAM Support for F5 Continuity Check
First Published: 12.2(105)TLast Updated: February 28, 2006The 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
History for the ATM OAM Support for F5 Continuity Check Feature
12.2(105)T
This feature was introduced.
12.2(28)SB
This feature was integrated into Cisco IOS Release 12.2(28)SB.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Monitoring and Maintaining ATM OAM F5 CC Management
Feature Overview
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.
This feature implements two types of OAM cells: CC cells for fault management and CC cells for activation and deactivation. Fault management cells detect connectivity failures. Activation and deactivation cells initiate the activation or deactivation of continuity checking.
SNMP Support for ATM OAM F5 Continuity Checking
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.
For a complete description of the extended ATM PVC MIB, including the supported notifications and tables, see the MIB file called CISCO-ATM-PVCTRAP-EXTN-MIB.my, available through Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Benefits
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.
Restrictions
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.
Prerequisites
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.
Configuration Tasks
See the following sections for configuration tasks for the ATM OAM Support for F5 Continuity Check feature. Each task in the list is identified as either required or optional.
•
•
•
•
•
Configuring ATM OAM F5 CC Support
To configure ATM OAM F5 CC support on an ATM PVC, use the following commands beginning in global configuration mode:
Configuring Denial of ATM OAM F5 CC Activation Requests
To disable ATM OAM F5 CC support on an ATM PVC and to configure the PVC to deny OAM F5 CC activation requests, use the following commands beginning in global configuration mode:
Configuring ATM OAM F5 CC Deactivation Requests to Be Sent upon PVC Failure
To configure a PVC to send ATM OAM F5 CC deactivation requests when the PVC is already down, use the following commands beginning in global configuration mode:
Configuring SNMP Notification Support for ATM OAM F5 CC Management
To enable the MIB and the sending of SNMP notifications that support ATM OAM F5 CC management, use the following commands beginning in global configuration mode:
Verifying ATM OAM Support for F5 CC Management
To verify the configuration and operation of ATM OAM F5 CC management, perform the following steps:
Step 1
Router# show running-config interface atm0Building configuration...Current configuration :152 bytes!interface ATM0no ip addressshutdownno atm ilmi-keepalivepvc 1/40oam-pvc manage cc segment direction both!dsl operating-mode autoendStep 2
The following is sample output for the show atm pvc command:
Router# show atm pvc 1/40ATM0:VCD:1, VPI:1, VCI:40UBR, PeakRate:0AAL5-LLC/SNAP, etype:0x0, Flags:0xC20, VCmode:0x0OAM frequency:0 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 DisabledOAM VC state:Not ManagedILMI VC state:Not ManagedOAM END CC status:OAM CC ReadyOAM END CC VC state:VerifiedOAM SEGMENT CC status:OAM CC ActiveOAM SEGMENT CC VC state:VerifiedInARP frequency:15 minutes(s)InPkts:0, OutPkts:0, InBytes:0, OutBytes:0InPRoc:0, OutPRoc:0, Broadcasts:0InFast:0, OutFast:0, InAS:0, OutAS:0Giants:0OAM cells received:20F5 InEndloop:0, F5 InSegloop:0,F5 InEndcc:0, F5 InSegcc:20, F5 InAIS:0, F5 InRDI:0F4 InEndloop:0, F4 InSegloop:0, F4 InAIS:0, F4 InRDI:0OAM cells sent:20F5 OutEndloop:0, F5 OutSegloop:0,F5 OutEndcc:0, F5 OutSegcc:20, F5 OutRDI:0F4 OutEndloop:0, F4 OutSegloop:0, F4 OutRDI:0OAM cell drops:1Status:UP
Monitoring and Maintaining ATM OAM F5 CC Management
To monitor and maintain ATM OAM F5 continuity checking, use the following command in privileged EXEC mode:
Configuration Examples
This section provides the following configuration examples:
•
•
•
•
ATM OAM F5 CC Support on a PVC Configuration Example
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 0ip address 10.0.0.3 255.255.255.0pvc 0/40oam-pvc manage cc segment direction sourceoam retry cc segment 10 10 30Denial of ATM OAM F5 CC Activation Requests Configuration Example
The following example shows how to disable ATM OAM F5 CC support and configure the VC to deny CC activation requests:
interface atm 0ip address 10.0.0.3 255.255.255.0pvc 0/40oam-pvc manage cc segment denyDeactivation of ATM OAM F5 CC upon PVC Failure Example
The following example shows how to send a CC deactivation request across the segment when PVC 0/40 goes down:
interface atm 0ip address 10.0.0.3 255.255.255.0pvc 0/40no oam-pvc manage cc segment deactivate-down-vcSupport for ATM OAM F5 CC SNMP Notifications Configuration Example
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 publicsnmp-server host 172.16.61.90 public!! Enable SNMP notifications:snmp-server enable traps atm pvc extension mibversion 2snmp-server enable traps atm pvc extension oam failure aisrdisnmp-server enable traps atm pvc extension oam failure endCCsnmp-server enable traps atm pvc extension oam failure segmentCCsnmp-server enable traps atm pvc extension oam failure loopbacksnmp-server enable traps atm pvc extension upAdditional References
The following sections provide references related to ATM OAM Support for F5 Continuity Check.
Related Documents
ATM configuration tasks
The "Configuring ATM" chapter in the Cisco IOS Wide-Area Networking Configuration Guide, Release 12.2
WAN Commands
The "ATM Commands" chapter in the Cisco IOS Wide-Area Networking Command Reference, Release 12.2
SNMP support configuration tasks
The "Configuring SNMP Support" chapter in the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2
System management commands
The "SNMP Commands" chapter in the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2
Standards
MIBs
None
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
Command Reference
This section documents modified commands.
•
debug atm oam cc
To display ATM operation, administration, and maintenance (OAM) F5 continuity check (CC) management activity, use the debug atm oam cc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug atm oam cc [interface atm number]
no debug atm oam cc [interface atm number]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following sample output for the debug atm oam cc command records activity beginning with the entry of the oam-pvc manage cc command and ending with the entry of the no oam-pvc manage cc command. The ATM 0 interface is specified, and the "both" segment direction is specified. The output shows an activation request sent and confirmed, a series of CC cells sent by the routers on each end of the segment, and a deactivation request and confirmation.
Router# debug atm oam cc interface atm 0Generic ATM:ATM OAM CC cells debugging is onRouter#00:15:05: CC ACTIVATE MSG (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAMType:8 OAM Func:1 Direction:3 CTag:500:15:05: CC ACTIVATE CONFIRM MSG (ATM0) O:VCD#1 VC 1/40 OAM CellType:4 OAM Type:8 OAM Func:1 Direction:3 CTag:500:15:06: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:100:15:07: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:08: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:09: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:10: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:11: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:12: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:13: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:14: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:15: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:16: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:17: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:18: CC CELL (ATM0) O:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:19: CC CELL (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAM Type:1 OAM Func:400:15:19: CC DEACTIVATE MSG (ATM0) I:VCD#1 VC 1/40 OAM Cell Type:4 OAMType:8 OAM Func:1 Direction:3 CTag:600:15:19: CC DEACTIVATE CONFIRM MSG (ATM0) O:VCD#1 VC 1/40 OAM CellType:4 OAM Type:8 OAM Func:1 Direction:3 CTag:6Table 1 describes the significant fields shown in the display.
Related Commands
oam-pvc manage cc
Configures ATM OAM F5 CC management.
show atm pvc
Displays all ATM PVCs and traffic information.
oam-pvc manage cc
To configure ATM Operation, Administration, and Maintenance (OAM) F5 continuity check (CC) management, use the oam-pvc manage cc command in ATM virtual circuit configuration mode. To disable OAM F5 continuity checking, use the no form of this command.
oam-pvc manage cc {end | segment} [direction {both | sink | source}] [keep-vc-up [end aisrdi failure | seg aisrdi failure]]
no oam-pvc manage cc {end | segment} [deactivate-down-vc] [direction {both | sink | source}] [keep-vc-up [end aisrdi failure | seg aisrdi failure]]
Syntax Description
Command Default
The default direction is sink.
Command Modes
ATM virtual circuit configuration
Command History
12.2(105)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
ATM OAM F5 continuity checking enables OAM to support the use of F5 segment and end-to-end CC cells to detect connectivity failures.
It is not necessary to enter a CC configuration on the router at the other end of a segment. The router on which CC management has been configured sends a CC activation request to the router at the other end of the segment, directing it to act as either a source or a sink.
Use the oam-pvc manage cc deny command to configure a permanent virtual circuit (PVC) to respond to activation requests from a peer device with "activation denied" messages. The oam-pvc manage cc deny command prevents ATM OAM F5 CC management from being activated on the PVC.
Use the no oam-pvc manage cc command to send a deactivation request to the peer device. The no oam-pvc manage cc command will disable ATM OAM F5 CC management on the PVC until the PVC receives an activation request. When the PVC receives an activation request, ATM OAM F5 CC management will be reenabled.
The no oam-pvc manage cc {end | segment} deactivate-down-vc command does not disable ATM OAM F5 CC support. This command causes OAM F5 CC deactivation messages to be sent over the VC when the VC goes down.
To enable the SNMP notifications that support ATM OAM F5 continuity checking, use the snmp-server enable traps atm pvc extension command.
Examples
ATM OAM F5 CC Support on a PVC Configuration Example
The following example shows how to configure ATM OAM F5 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 0ip address 10.0.0.3 255.255.255.0pvc 0/40oam-pvc manage cc segment direction sourceoam retry cc segment 10 10 30Deactivation of ATM OAM F5 CC upon VC Failure Example
The following example shows how to configure OAM to send a CC deactivation request across the segment when PVC 0/1 goes down:
interface atm 0ip address 10.0.0.3 255.255.255.0pvc 0/40no oam-pvc manage cc segment deactivate-down-vcRelated Commands
oam-pvc manage cc deny
To disable ATM Operation, Administration, and Maintenance (OAM) F5 continuity check (CC) support and configure a permanent virtual circuit (PVC) to deny CC activation requests, use the oam-pvc manage cc deny command in ATM virtual circuit configuration mode. To reenable OAM F5 CC support and allow CC activation requests, use the no form of this command.
oam-pvc manage cc {end | segment} deny
no oam-pvc manage cc {end | segment} deny
Syntax Description
Command Default
If the peer device sends the activation message, F5 CC management will be enabled on the PVC.
Command Modes
ATM virtual circuit configuration
Command History
12.2(105)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Usage Guidelines
Use the oam-pvc manage cc deny command to configure a permanent virtual circuit (PVC) to respond to activation requests from a peer device with "activation denied" messages. The oam-pvc manage cc deny command prevents ATM OAM F5 CC management from being activated on the PVC.
Use the no oam-pvc manage cc command to send a deactivation request to the peer device. The no oam-pvc manage cc command will disable ATM OAM F5 CC management on the PVC until the PVC receives an activation request. When the PVC receives an activation request, ATM OAM F5 CC management will be reenabled.
Examples
The following example shows how to disable ATM OAM F5 CC support and configure the VC to deny CC activation requests:
interface atm 0ip address 10.0.0.3 255.255.255.0pvc 0/40oam-pvc manage cc segment denyRelated Commands
oam retry cc
To set the frequency at which ATM Operation, Administration, and Maintenance (OAM) F5 continuity check (CC) activation and deactivation requests are sent to a device at the other end of a segment or permanent virtual circuit (PVC), use the oam retry cc command in ATM virtual circuit configuration mode. To remove the retry settings, use the no form of this command.
oam retry cc {end | segment} [activation-count [deactivation-count [retry-frequency]]]
no oam retry cc {end | segment} [activation-count [deactivation-count [retry-frequency]]]
Syntax Description
Command Default
Activation count is 3
Deactivation count is 3
Retry frequency: 30 secondsCommand Modes
ATM virtual circuit configuration
Command History
12.2(105)T
This command was introduced.
12.2(28)SB
This command was integrated into Cisco IOS Release 12.2(28)SB.
Examples
The following example shows how to configure ATM OAM F5 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 0ip address 10.0.0.3 255.255.255.0pvc 0/40oam-pvc manage cc segment direction sourceoam retry cc segment 10 10 30Related Commands
oam-pvc manage cc deny
Configures ATM OAM F5 CC management.
oam-pvc manage cc deny
Disables ATM OAM F5 CC support and configures the PVC to deny CC activation requests.
snmp-server enable traps atm pvc extension
To enable the extended ATM permanent virtual circuit (PVC) Simple Network Management Protocol (SNMP) notifications and to specify the MIB to be used to support the notifications, use the snmp-server enable traps atm pvc extension command in global configuration mode. To disable the SNMP notifications or remove the MIB specification, use the no form of this command.
snmp-server enable traps atm pvc extension {up | down | mibversion {1 | 2 } | oam failure [aisrdi | endCC | loopback | segmentCC]}
no snmp-server enable traps atm pvc extension {up | down | mibversion {1 | 2 } | oam failure [aisrdi | endCC | loopback | segmentCC]}
Syntax Description
Command Default
MIB version 1 is the default version.
SNMP notifications are disabled.
The interval between successive traps is 30 seconds.Command Modes
Global configuration
Command History
Usage Guidelines
This section contains the following information:
•
SNMP Notifications
The snmp-server enable traps atm pvc extension command is used in conjunction with the snmp-server host command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. In order to send notifications, you must configure at least one snmp-server host command.
SNMP notifications can be sent as traps or inform requests. The snmp-server enable traps atm pvc extension command enables both traps and inform requests for the specified notification types.
Extended ATM PVC Notifications
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 can be configured.
The extended ATM PVC failure trap (which is enabled by the snmp-server enable traps atm pvc extension down command) is the same trap as the legacy ATM PVC failure trap (which is enabled by the snmp-server enable traps atm pvc command), but with the following differences:
•
•
•
ATM PVC traps are generated at the end of the notification interval. It is possible to generate all three types of ATM PVC traps (the ATM PVC failure trap, ATM PVC up trap, and ATM PVC OAM failure trap) at the end of the same notification interval; however, only one type of trap will be generated for each PVC.
OAM Managment
OAM management must be enabled on the PVC before you can use ATM PVC traps. To generate F5 loopback failure traps, enable OAM management using the oam-pvc manage command. To generate segment F5 CC failure traps, enable segment OAM CC management by using the oam-pvc manage cc segment command. To generate end-to-end F5 CC failure traps, enable end-to-end OAM CC management by using the oam-pvc manage cc end command. To generate OAM F5 AIS/RDI failure traps, enable any of the three types of OAM management listed above.
OAM management and support for OAM F5 continuity checking must be enabled on the PVC by using the oam-pvc manage cc command before you can use the ATM OAM continuity check SNMP notifications. For PVCs that are not part of a range, extended ATM PVC traps include virtual path identifier/virtual channel identifier (VPI/ VCI) information, the number of state transitions a PVC goes through in an interval, and the timestamp for the start and end of the transitions. For PVCs that are part of a range, extended ATM PVC traps include the first and last VPI/VCI of the range and the timestamp for the first failure and the last failure within the same range.
MIB Versions
MIB version 1 specifies the MIB that supports legacy extended ATM PVC traps and is defined in the file CISCO-IETF-ATM2-PVCTRAP-MIB-EXTN.my. MIB version 1 is implemented by default. Use the snmp-server enable traps atm pvc extension command with the mibversion 1 keyword or the no snmp-server enable traps atm pvc extension command with the mibversion 2 keyword to re-enable this MIB if it was previously disabled with the snmp-server enable traps atm pvc extension command employed with the mibversion 2 keyword.
Use the snmp-server enable traps atm pvc extension command with the mibversion 2 keyword to specify the MIB that supports ATM OAM F5 CC and ATM OAM AID/RDI failure notifications. This MIB is defined in the file CISCO-ATM-PVCTRAP-EXTN-MIB.my.
To enable the SNMP notifications that support ATM OAM F5 continuity checking, use the snmp-server enable traps atm pvc extension command in global configuration mode. These SNMP notifications are defined in the file CISCO-ATM-PVCTRAP-EXTN-MIB.my, available from the Cisco FTP site at ftp://www.cisco.com/public/mibs/v2/.
The extended ATM PVC notifications for MIB version 1 are defined in the CISCO-IETF-ATM2-PVCTRAP-MIB.my file.The extended ATM PVC notifications for MIB version 2 are defined in the CISCO-ATM-PVCTRAP-EXTN-MIB.my file. Both of these MIB files are available from the Cisco FTP site at ftp://www.cisco.com/public/mibs/v2/.
Note
PVC State Changes
When the ATM OAM F5 loopback, AIS/RDI, or CC failure trap is enabled, the PVC remains in the UP state when an OAM loopback, AIS/RDI, or CC failure is detected, so that the flow of data will still be possible. If one of these traps is not enabled, the PVC will be placed in the DOWN state when an OAM loopback, AIS/RDI, or CC failure is detected.
Examples
MIB Specification For SNMP Notifications Example
In the following example, the MIB that supports the SNMP notifications for ATM OAM continuity checking is implemented, and the ATM OAM continuity checking notifications are enabled. Support for end-to-end OAM F5 continuity checking is enabled on PVC 0/1:
Router(config)# snmp-server enable traps atm pvc extension mibversion 2Router(config)# snmp-server enable traps atm pvc extension oam failure aisrdiRouter(config)# snmp-server enable traps atm pvc extension oam failure endccRouter(config)# snmp-server enable traps atm pvc extension oam failure segmentccRouter(config)# snmp-server enable traps atm pvc extension oam failure loopbackRouter(config)# snmp-server enable traps atm pvc extension upRouter(config)# interface atm 0Router(config-if)# pvc 0/40Router(config-if-atm-vc)# oam-pvc manage cc endExtended ATM PVC Notifications Example
The following example shows all three of the extended ATM PVC traps enabled on a router. If PVC 0/1 leaves the UP state, leaves the DOWN state, or has an OAM loopback failure, host 172.16.61.90 will receive the SNMP notifications:
! Configure SNMP support and an IP routing protocol on your router:Router(config)# snmp-server community public roRouter(config)# snmp-server host 172.16.61.90 publicRouter(config)# ip routingRouter(config)# router igrp 109Router(config-router)# network 172.16.0.0!! Enable extended ATM PVC trap support and OAM management:Router(config)# snmp-server enable traps atm pvc extension downRouter(config)# snmp-server enable traps atm pvc extension upRouter(config)# snmp-server enable traps atm pvc extension oam failure loopbackRouter(config)# interface atm 1/0.1Router(config-if)# pvc 0/1Router(config-if-atm-vc)# oam-pvc manageExtended ATM PVC Failure Trap Output: Example
The following example shows output for extended ATM PVC failure trap for PVCs 1/100, 1/102, and 1/103. Note that only one trap is generated for all the PVCs associated with the same interface or subinterface (in contrast to the legacy ATM PVC failure trap, which generates a separate trap for each PVC). The VPI/VCI information and timing information are located in the objects associated with the trap.
00:23:56:SNMP:Queuing packet to 10.1.1.100:23:56:SNMP:V2 Trap, reqid 2, errstat 0, erridx 0sysUpTime.0 = 143636snmpTrapOID.0 = atmIntfPvcFailuresTrapifEntry.1.19 = 19atmIntfPvcFailures.2 = 7atmIntfCurrentlyFailingPVcls.2 = 3atmPVclLowerRangeValue.19.1.2 = 102atmPVclHigherRangeValue.19.1.2 = 103atmPVclRangeStatusChangeStart.19.1.2 = 140643atmPVclRangeStatusChangeEnd.19.1.2 = 140698atmPVclStatusTransition.19.1.100 = 1atmPVclStatusChangeStart.19.1.100 = 140636atmPVclStatusChangeEnd.19.1.100 = 14063600:23:56:SNMP:Packet sent via UDP to 10.1.1.1Extended ATM PVC Up Trap Output: Example
The following example shows output for the extended ATM PVC up trap for PVCs 1/100, 1/102, and 1/103:
00:31:29:SNMP:Queuing packet to 10.1.1.100:31:29:SNMP:V2 Trap, reqid 2, errstat 0, erridx 0sysUpTime.0 = 188990snmpTrapOID.0 = atmIntfPvcUpTrapifEntry.1.19 = 19atmIntfCurrentlyDownToUpPVcls.2 = 3atmPVclLowerRangeValue.19.1.2 = 102atmPVclHigherRangeValue.19.1.2 = 103atmPVclRangeStatusChangeStart.19.1.2 = 186005atmPVclRangeStatusChangeEnd.19.1.2 = 186053atmPVclStatusTransition.19.1.100 = 1atmPVclStatusChangeStart.19.1.100 = 185990atmPVclStatusChangeEnd.19.1.100 = 18599000:31:30:SNMP:Packet sent via UDP to 10.1.1.1ATM OAM F5 CC Notifications Example
In the following example, the ATM OAM CC notifications and an extended ATM PVC notification are enabled. If connectivity failures are detected on PVC 0/1, host 172.16.61.90 will receive the SNMP notifications:
! Configure SNMP support and an IP routing protocol on your router:Router(config)# snmp-server community public roRouter(config)# snmp-server host 172.16.61.90 publicRouter(config)# ip routingRouter(config)# router igrp 109Router(config-router)# network 172.16.0.0!! Enable extended ATM PVC trap support and OAM management:Router(config)# snmp-server enable traps atm pvc extension mibversion 2Router(config)# snmp-server enable traps atm pvc extension oam failure aisrdiRouter(config)# snmp-server enable traps atm pvc extension oam failure endccRouter(config)# snmp-server enable traps atm pvc extension oam failure segmentccRouter(config)# snmp-server enable traps atm pvc extension oam failure loopbackRouter(config)# snmp-server enable traps atm pvc extension upRouter(config)# interface atm 0Router(config-if)# pvc 0/1Router(config-if-atm-vc)# oam-pvc manage cc endRelated Commands
Glossary
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.
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, 2005-2006 Cisco Systems, Inc. All rights reserved.
