To enable the sending of extended ATM permanent virtual circuit (PVC) SNMP notifications and SNMP notifications for ATM Operation, Administration, and Maintenance (OAM) F5 continuity check (CC), ATM OAM F5 alarm indication signals/remote defect indications (AIS/RDI), and loopback failures, use the snmp-server enable traps atm pvc extensioncommand in global configuration mode. To disable these SNMP notifications, use the noform of this command.
snmp-server
enable
traps
atm
pvc
extension
{ up | down | oam
failure
[ aisrdi | endCC | loopback | segmentCC ] }
no
snmp-server
enable
traps
atm
pvc
extension
{ up | down | oam
failure
[ aisrdi | endCC | loopback | segmentCC ] }
Syntax Description
up |
Enables ATM PVC up traps. These notifications are generated when a PVC changes from the DOWN to the UP state. |
down |
Enables ATM PVC failure traps. These notifications are generated when a PVC changes from the UP to the DOWN state. |
oam failure |
Enables ATM PVC OAM failure traps. These notifications are generated when any type of OAM failure occurs on the PVC. |
aisrdi |
(Optional) Enables AIS/RDI OAM failure traps. These notifications are generated when AIS/RDI OAM failure occurs on the PVC. |
endCC |
(Optional) Enables end-to-end OAM CC failure traps. These notifications are generated when end-to-end CC failures occur on the PVC. |
loopback |
(Optional) Enables OAM failure loopback traps. These notifications are generated when OAM loopback failure occurs on the PVC. |
segmentCC |
(Optional) Enables segment OAM CC failure traps. These notifications are generated when segment CC failures occur on the PVC. |
Command Default
SNMP notifications are disabled. The interval between successive traps is 30 seconds.
Command Modes
Global configuration (config)
Command History
Release |
Modification |
12.2(4)T |
This command was introduced for those platforms that support ATM PVC management. |
12.2(13)T |
This command was modified to configure SNMP notification support for ATM OAM F5 CC and ATM OAM F5 AIS/RDI failures. |
12.2(28)SB |
This command was integrated into Cisco IOS Release 12.2(28)SB. |
Cisco IOS XE Release 2.3 |
This command was integrated into Cisco IOS XE Software Release 2.3 and implemented on the Cisco ASR 1000 series routers. |
12.2(33)SRE |
This command was integrated into Cisco IOS Release 12.2(33)SRE. |
Usage Guidelines
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.
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:
- The extended ATM PVC failure trap contains information in the form of VPI/VCI ranges.
- The extended ATM PVC failure trap contains timestamps for when PVCs go down.
- The legacy ATM PVC failure trap contains only one VPI/VCI per trap.
Note |
You must configure the snmp-server enable traps atm pvc extension mibversion 2command before you can enable the ATM OAM F5 AIS/RDI failure traps, the end-to-end ATM OAM F5 CC failure traps, the OAM failure loopback traps, and the segment ATM OAM F5 CC failure traps. This command enables the MIB that supports these traps.
|
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.
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. The interval between successive traps is 30 seconds.
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://ftp.cisco.com/pub/mibs/v2/ .
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.
The snmp-server enable traps atm pvc extensioncommand is used in conjunction with the snmp-server hostcommand. 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 hostcommand.
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
Extended ATM PVC Notifications
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 ro
Router(config)# snmp-server host 172.16.61.90 public
Router(config)# ip routing
Router(config)# router igrp 109
Router(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 down
Router(config)# snmp-server enable traps atm pvc extension up
Router(config)# snmp-server enable traps atm pvc extension oam failure loopback
Router(config)# interface atm 1/0.1
Router(config-if)# pvc 0/1
Router(config-if-atm-vc)# oam-pvc manage
Examples
Extended ATM PVC Failure Trap Output
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.1
00:23:56:SNMP:V2 Trap, reqid 2, errstat 0, erridx 0
sysUpTime.0 = 143636
snmpTrapOID.0 = atmIntfPvcFailuresTrap
ifEntry.1.19 = 19
atmIntfPvcFailures.2 = 7
atmIntfCurrentlyFailingPVcls.2 = 3
atmPVclLowerRangeValue.19.1.2 = 102
atmPVclHigherRangeValue.19.1.2 = 103
atmPVclRangeStatusChangeStart.19.1.2 = 140643
atmPVclRangeStatusChangeEnd.19.1.2 = 140698
atmPVclStatusTransition.19.1.100 = 1
atmPVclStatusChangeStart.19.1.100 = 140636
atmPVclStatusChangeEnd.19.1.100 = 140636
00:23:56:SNMP:Packet sent via UDP to 10.1.1.1
Examples
Extended ATM PVC Up Trap Output
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.1
00:31:29:SNMP:V2 Trap, reqid 2, errstat 0, erridx 0
sysUpTime.0 = 188990
snmpTrapOID.0 = atmIntfPvcUpTrap
ifEntry.1.19 = 19
atmIntfCurrentlyDownToUpPVcls.2 = 3
atmPVclLowerRangeValue.19.1.2 = 102
atmPVclHigherRangeValue.19.1.2 = 103
atmPVclRangeStatusChangeStart.19.1.2 = 186005
atmPVclRangeStatusChangeEnd.19.1.2 = 186053
atmPVclStatusTransition.19.1.100 = 1
atmPVclStatusChangeStart.19.1.100 = 185990
atmPVclStatusChangeEnd.19.1.100 = 185990
00:31:30:SNMP:Packet sent via UDP to 10.1.1.1
Examples
ATM OAM F5 CC Notifications
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 ro
Router(config)# snmp-server host 172.16.61.90 public
Router(config)# ip routing
Router(config)# router igrp 109
Router(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 2
Router(config)# snmp-server enable traps atm pvc extension oam failure aisrdi
Router(config)# snmp-server enable traps atm pvc extension oam failure endcc
Router(config)# snmp-server enable traps atm pvc extension oam failure segmentcc
Router(config)# snmp-server enable traps atm pvc extension oam failure loopback
Router(config)# snmp-server enable traps atm pvc extension up
Router(config)# interface atm 0
Router(config-if)# pvc 0/1
Router(config-if-atm-vc)# oam-pvc manage cc end
Related Commands
Command |
Description |
oam-pvc manage |
Enables end-to-end F5 OAM loopback cell generation and OAM management. |
oam-pvc manage cc |
Configures ATM OAM F5 CC management. |
show atm pvc |
Displays all ATM PVCs and traffic information. |
snmp-server enable traps |
Enables all available SNMP notifications on your system. |
snmp-server enable traps atm pvc |
Enables the sending of legacy ATM PVC failure traps. |
snmp-server enable traps atm pvc extension mibversion |
Specifies the MIB that supports extended ATM PVC SNMP notifications or the MIB that supports SNMP notifications for ATM OAM F5 CC, F5 AIS/RDI, and F5 loopback failures. |
snmp-server host |
Specifies the recipient of an SNMP notification operation. |
snmp-server trap-source |
Specifies the interface from which an SNMP trap should originate. |