-
Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3
-
Introduction
-
CFR Commands: absolute -- clock timezone
-
CFR Commands: clock update-calendar -- escape-character
-
CFR Commands: exception core-file -- ip ftp passive
-
CFR Commands: ip ftp password -- lsr-path
-
CFR Commands: memory sanity -- periodic
-
CFR Commands: ping -- service sequence numbers
-
CFR Commands: service slave-log -- show
tee -
CFR Commands: show context -- show ip http server
-
CFR Commands: show kron schedule -- show rtr enhanced-history
-
12.3 CF CR Commands: show rtr distributions-statistics -- snmp-server enable informs
-
CFR Commands: snmp-server enable traps -- statistics-distribution-interval
-
CFR Commands: stopbits -- ttl ip
-
CFR Commands: type dhcp - xsm vdm
-
CFR Appendix: ASCII Character Set and Hex Values
-
Table Of Contents
snmp-server enable traps aaa_server
snmp-server enable traps atm pvc extension mibversion
snmp-server enable traps atm pvc extension
snmp-server enable traps atm pvc
snmp-server enable traps atm subif
snmp-server enable traps calltracker
snmp-server enable traps director
snmp-server enable traps envmon
snmp-server enable traps frame-relay
snmp-server enable traps frame-relay subif
snmp-server enable traps mpls ldp
snmp-server enable traps mpls traffic-eng
snmp-server enable traps mpls vpn
snmp-server enable traps pppoe
snmp-server enable traps repeater
snmp-server enable traps syslog
snmp-server enable traps voice poor-qov
snmp-server manager session-timeout
snmp-server trap-authentication
statistics-distribution-interval
snmp-server enable traps
To enable all Simple Network Management Protocol (SNMP) notifications (traps or informs) available on your system, use the snmp-server enable traps command in global configuration mode. To disable all available SNMP notifications, use the no form of this command.
snmp-server enable traps [notification-type]
no snmp-server enable traps [notification-type]
Syntax Description
Defaults
This command is disabled by default. Most notification types are disabled. However, some notification types cannot be controlled with this command.
If you enter this command with no notification-type keyword extenstions, the default is to enable (or diable, if the no form is used) all notification types controlled by this command.
Command Modes
Global configuration
Command History
10.3
This command was introduced.
12.0(2)T
The rsvp keyword was added.
12.0(3)T
The hsrp keyword was added.
Usage Guidelines
For additional notification types, see the Related Commands table for this command.
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. To specify whether the notifications should be sent as traps or informs, use the snmp-server host [traps | informs] command.
If you do not enter an snmp-server enable traps command, no notifications controlled by this command are sent. In order to configure the router to send these SNMP notifications, you must enter at least one snmp-server enable traps command. If you enter the command with no keywords, all notification types are enabled. If you enter the command with a keyword, only the notification type related to that keyword is enabled. In order to enable multiple types of notifications, you must issue a separate snmp-server enable traps command for each notification type and notification option.
The snmp-server enable traps 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.
Examples
The following example enables the router to send all traps to the host specified by the name myhost.cisco.com, using the community string defined as public:
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com publicThe following example enables the router to send Frame Relay and environmental monitor traps to the host myhost.cisco.com using the community string public:
Router(config)# snmp-server enable traps frame-relayRouter(config)# snmp-server enable traps envmon temperatureRouter(config)# snmp-server host myhost.cisco.com publicThe following example will not send traps to any host. The BGP traps are enabled for all hosts, but the only traps enabled to be sent to a host are ISDN traps (which are not enabled in this example).
Router(config)# snmp-server enable traps bgpRouter(config)# snmp-server host bob public isdnThe following example enables the router to send all inform requests to the host at the address myhost.cisco.com, using the community string defined as public:
Router(config)# snmp-server enable trapsRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicThe following example sends HSRP MIB traps to the host myhost.cisco.com using the community string public.
Router(config)# snmp-server enable traps hsrpRouter(config)# snmp-server host myhost.cisco.com traps version 2c public hsrpRelated Commands
snmp-server enable traps aaa_server
To enable authentication, authorization, and accounting (AAA) server state-change Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps aaa_server command in global configuration mode. To disable AAA server state-change SNMP notifications, use the no form of this command.
snmp-server enable traps aaa_server
no snmp-server enable traps aaa_server
Syntax Description
This command has no arguments or keywords.
Defaults
SNMP notifications are disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.
This command controls (enables or disables) AAA Server state change (casServerStateChange) notifications. ServerStateChange notifications, when enabled, will be sent when the server moves from an "up" to "dead" state or when a server moves from a "dead" to "up" state.
The Cisco AAA Server State is defined by the casState object in the Cisco AAA Server MIB. The possible values are as follows:
•
up(1)—Server is responding to requests.
•
A server is marked "dead" if it does not respond after maximum retransmissions. A server is marked "up" again either after a waiting period or if some response is received from it. The initial value of casState is "up(1)" at system startup. This will only transition to "dead(2)" if an attempt to communicate fails.
For a complete description of this notification and additional MIB functions, see the CISCO-AAA-SERVER-MIB.my file, available on Cisco.com at http://www.cisco.com/public/mibs/v2/.
The snmp-server enable traps aaa_sever 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. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example enables the router to send AAA server up/down informs to the host at the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps aaa_serverRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicRelated Commands
snmp-server enable traps atm pvc extension mibversion
To specify the MIB that supports extended ATM permanent virtual circuit (PVC) Simple Network Management Protocol (SNMP) notifications or the MIB that supports SNMP notifications for ATM Operation, Administration, and Maintenance (OAM) F5 continuity check (CC) management, ATM OAM F5 AIS/RDI management, and F5 loopback failure management, use the snmp-server enable traps atm pvc extension mibversion command in global configuration mode. To remove the MIB specification, use the no form of this command.
snmp-server enable traps atm pvc extension mibversion {1 | 2}
no snmp-server enable traps atm pvc extension mibversion {1 | 2}
Syntax Description
Defaults
MIB version: 1
Command Modes
Global configuration
Command History
Usage Guidelines
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 mibversion 1 command or the no snmp-server enable traps atm pvc extension mibversion 2 command to reenable this MIB if it was previously disabled with the snmp-server enable traps atm pvc extension mibversion 2 command.
Use the snmp-server enable traps atm pvc extension mibversion 2 command 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/.
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.
Examples
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 endRelated Commands
snmp-server enable traps atm pvc extension
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 extension command in global configuration mode. To disable these SNMP notifications, use the no form 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
Defaults
SNMP notifications are disabled.
The interval between successive traps is 30 seconds.Command Modes
Global configuration
Command History
Usage Guidelines
For PVCs that are not part of a range, extended ATM PVC traps include virtual path identifier/virtual channel indentifier (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 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 the following differences:
•
•
•
Note
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 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/.
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 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.
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 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 1.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 1.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 1.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 1.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
snmp-server enable traps atm pvc
To enable the sending of ATM permanent virtual circuit (PVC) Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps atm pvc command in global configuration mode. To disable ATM PVC-specific SNMP notifications, use the no form of this command.
snmp-server enable traps atm pvc [interval seconds] [fail-interval seconds]
no snmp-server enable traps atm pvc [interval seconds] [fail-interval seconds]
Syntax Description
Defaults
SNMP notifications are disabled by default.
The default interval is 30.
The default fail-interval is 0.
Command Modes
Global configuration
Command History
12.0(1)T
This command was introduced for those platforms that support ATM PVC Management.
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types. ATM notifications are defined in the CISCO-IETF-ATM2-PVCTRAP-MIB.my file, available from the Cisco FTP site at ftp://www.cisco.com/public/mibs/v2/.
ATM PVC failure notification are sent when a PVC on an ATM interface fails or leaves the UP operational state. Only one trap is generated per hardware interface, within the specified interval defined by the interval keyword (stored as the atmIntfPvcNotificationInterval in the MIB). If other PVCs on the same interface go DOWN during this interval, traps are generated and held until the fail-interval has elapsed. Once the interval has elapsed, the traps are sent if the PVCs are still DOWN.
No notifications are generated when a PVC returns to the UP state after having been in the DOWN state. If you need to detect the recovery of PVCs, you must use the SNMP management application to regularly poll your router.
The snmp-server enable traps atm pvc 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.
Examples
The following example shows the enabling of ATM PVC traps on a router, so that if PVC 0/1 goes down, host 172.16.61.90 will receive the notifications:
!For ATM PVC Trap Support to work on your router, you must first have SNMP support and!an IP routing protocol configured 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 ATM PVC Trap Support and OAM management:Router(config)# snmp-server enable traps atm pvc interval 40 fail-interval 10Router(config)# interface atm 1/0.1Router(config-if)# pvc 0/1Router(config-if-atm-vc)# oam-pvc manageRelated Commands
snmp-server enable traps atm subif
To enable the sending of ATM subinterface Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps atm subif command in global configuration mode. To disable ATM subinterface-specific SNMP notifications, use the no form of this command.
snmp-server enable traps atm subif [interval seconds [count number-of-traps] | [count number-of-traps]
no snmp-server enable traps atm subif [interval seconds [count number-of-traps] | [count number-of-traps]
Syntax Description
Defaults
ATM subinterface SNMP notifications are disabled by default.
Interval: 10 seconds
Count: 10 trapsCommand Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests for the specified notification types.
ATM subinterface traps are sent to the network management system (NMS) whenever a subinterface enters or leaves the down state.
The count and interval parameters can be configured to limit the number of traps sent and the frequency at which they are sent in order to prevent trap storms. Configuring an interval of 0 seconds causes all ATM subinterface traps to be sent.
You can disable ATM subinterface traps by using the no snmp-server enable traps atm subif command. When traps are disabled, you can use the SNMP management application to poll your router for subinterface status information.
The snmp-server enable traps atm subif 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.
The snmp-server trap link ietf command must be configured in order to use the snmp-server enable traps atm subif command. The snmp-server trap link ietf command is used to configure your router to use the RFC 2233 IETF standards-based implementation of linkUp/linkDown traps. The default Cisco object definitions do not generate linkUp/linkDown traps correctly for subinterfaces.
Examples
The following example shows how to enable ATM subinterface traps on a router. If an ATM subinterface on this router changes state, host 172.16.61.90 will receive the notifications:
!For ATM subinterface trap to work on your router, you must first have SNMP support and!an IP routing protocol configured on your router:Router(config)# snmp-server community public roRouter(config)# snmp-server host 172.16.61.90 publicRouter(config)# snmp-server trap link ietfRouter(config)# snmp-server enable traps snmpRouter(config)# ip routingRouter(config)# router igrp 109Router(config-router)# network 172.16.0.0!Enable ATM subinterface trap support:Router(config)# snmp-server enable traps atm subif interval 60 count 5Related Commands
snmp-server enable traps bgp
To enable Border Gateway Protocol (BGP) state-change Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps bgp command in global configuration mode. To disable BGP state-change SNMP notifications, use the no form of this command.
snmp-server enable traps bgp
no snmp-server enable traps bgp
Syntax Description
This command has no arguments or keywords.
Defaults
SNMP notifications are disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.
This command controls (enables or disables) BGP server state change notifications, as defined in the BGP4-MIB (enterprise 1.3.6.1.2.1.15.7). The notifications types are:
•
•
The BGP notifications are defined in the BGP-4 MIB as follows:
For a complete description of these notifications and additional MIB functions, see the BGP4-MIB.my file, available through the Cisco FTP site at ftp://www.cisco.com/public/mibs/v2/.
Note
The snmp-server enable traps bgp 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. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example enables the router to send BGP state change informs to the host at the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps bgpRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicRelated Commands
snmp-server host
Specifies the recipient of an SNMP notification operation.
snmp-server trap-source
Specifies the interface that an SNMP trap should originate from.
snmp-server enable traps calltracker
To enable Call Tracker CallSetup and Call Terminate Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps calltracker command in global configuration mode. To disable Call Tracker SNMP notifications, use the no form of this command.
snmp-server enable traps calltracker
no snmp-server enable traps calltracker
Syntax Description
This command has no arguments or keywords.
Defaults
SNMP notifications are disabled by default.
Command Modes
Global configuration
Command History
12.1(3)T
This command was introduced for the Cisco AS5300 and Cisco AS580 access servers.
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.
This command controls (enables or disables) Call Tracker CallSetup and CallTerminate notifications. CallSetup notifications are generated at the start of each call, when an entry is created in the active table (cctActiveTable), and CallTerminate notifications are generated at the end of each call, when an entry is created in the history table (cctHistoryTable).
For a complete description of these notifications and additional MIB functions, refer to the CISCO-CALL-TRACKER-MIB.my file, available on Cisco.com at http://www.cisco.com/public/mibs/v2/.
The snmp-server enable traps calltracker command is used in conjunction with the snmp-server host global configuration command. Use the snmp-server host command to specify which host or hosts receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example enables the router to send call-start and call-stop informs to the host at the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps calltrackerRouter(config)# snmp-server host myhost.cisco.com informs version 2c public calltrackerRelated Commands
snmp-server enable traps director
To enable DistributedDirector Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps director command in global configuration mode. To disable DistributedDirector SNMP notifications, use the no form of this command.
snmp-server enable traps director [server-up | server-down]
no snmp-server enable traps director [server-up | server-down]
Syntax Description
Defaults
SNMP notifications are disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.
This command controls (enables or disables) DistributedDirector status notifications for systems. If none of the optional keywords is specified, all available environmental notifications are enabled.
Examples
In the following example, both ciscoDistDirEventServerUp and ciscoDistDirEventServerDown notifications are enabled:
Router(config)# snmp-server enable traps directorRouter# show running-configip host myhost 172.2.2.10 172.2.2.20 172.2.2.30...ip director host myhostip dns primary myhost soa myhost myhost@comip director host myhost priority boomerang 1no ip director drp synchronizedsnmp-server enable traps director server-up server-downRelated Commands
snmp-server enable traps dlsw
To enable the sending of Data Link Switch (DLSw) circuit and peer connection Simple Network Management Protocol (SNMP) notifications (traps and informs), use the snmp-server enable traps dlsw command in global configuration mode. To disable DLSw notifications, use the no form of this command.
snmp-server enable traps dlsw [circuit | tconn]
no snmp-server enable traps dlsw [circuit | tconn]
Syntax Description
Defaults
SNMP notifications are disabled by default.
If the optional keywords are not used, all DLSw notification types are enabled (or disabled, if the no form is used).
Command Modes
Global configuration
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests. Use this command in conjunction with the snmp-server host command.
This command controls (enables or disables) SNMP notifications for Data Link Switch (DLSw) circuit and connection activity. DLSw objects are defined in the Cisco DLSw MIB module (CISCO-DLSW-MIB.my) and the DLSw+ (Cisco Specific Features) MIB module (CISCO-DLSW-EXT-MIB.my), available through Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
Examples
In the following example the device is configured to send DLSw circuit state change informs to the host at the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps dlsw circuitRouter(config)# snmp-server host myhost.cisco.com informs version 2c publicRelated Commands
snmp-server host
Specifies the recipient of an SNMP notification operation.
snmp-server trap-source
Specifies the interface that an SNMP trap should originate from.
snmp-server enable traps envmon
To enable environmental monitor Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps envmon command in global configuration mode. To disable environmental monitor SNMP notifications, use the no form of this command.
snmp-server enable traps envmon [shutdown] [voltage] [temperature] [fan] [supply]
no snmp-server enable traps envmon [shutdown] [voltage] [temperature] [fan] [supply]
Syntax Description
Defaults
SNMP notifications are disabled by default.
Command Modes
Global configuration
Command History
10.3
This command was introduced.
11.3(6)AA
Support for this command was introduced for the Cisco AS5300 access server.
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform requests.
This command controls (enables or disables) Environmental Monitor (EnvMon) status notifications for supported systems. Cisco enterprise EnvMon notifications are triggered when an environmental threshold is exceeded. If none of the optional keywords are specified, all available environmental notifications are enabled.
For a complete description of these notifications and additional MIB functions, see the CISCO-ENVMON-MIB.my and CISCO-ACCESS-ENVMON-MIB.my files, available on Cisco.com at http://www.cisco.com/public/mibs/v2/.
Status of the Environmental Monitor can be viewed using the show environment command.
The snmp-server enable traps envmon 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. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example enables a Cisco 12000 GSR to send environmental failure informs to the host at the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps envmonRouter(config)# snmp-server host myhost.cisco.com informs version 2c public envmonRelated Commands
snmp-server enable traps frame-relay
To enable Frame Relay Data Link Connection Identifier (DLCI) and subinterface Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps frame-relay command in global configuration mode. To disable Frame Relay DLCI and subinterface SNMP notifications, use the no form of this command.
snmp-server enable traps frame-relay
no snmp-server enable traps frame-relay
