From: gladston@br.ibm.com
Date: Sat Aug 06 2005 - 23:32:40 GMT-3
Hi,
Testing this statement:
=====================
However, some notification types cannot be controlled with the snmp-server enable command. For example, some notification types are always enabled. Other notification types are enabled by a different command. For example, the linkUpDown notifications are controlled by the snmp trap link-status command. These notification types do not require an snmp-server enable command.
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094a05.shtml
=====================
revealed that it does not work that way. At least not on (C7200-JS-M), Version 12.2(15)T14.
Traps for link up/down are sent only if 'snmp-server enable traps' are entered.
Do you have a different experience?
The test consist of shut/no sht the interface fastethernet of CAT-2 connected to R11's fa0/0.
R11 should send a trap to R2.
Before enabling snmp-server enable trap:
Extended IP access list 140
10 permit udp any any eq snmptrap log-input (13 matches)
20 permit ip any any (15 matches)
Rack2R2#sh access-list
Extended IP access list 140
10 permit udp any any eq snmptrap log-input (13 matches)
20 permit ip any any (15 matches)
Rack2R2#sh access-list
Extended IP access list 140
10 permit udp any any eq snmptrap log-input (13 matches)
20 permit ip any any (15 matches)
After enabling snmp-server enable trap:
Extended IP access list 140
10 permit udp any any eq snmptrap log-input (14 matches)
20 permit ip any any (15 matches)
Rack2R2#sh access-list
Extended IP access list 140
10 permit udp any any eq snmptrap log-input (15 matches)
20 permit ip any any (15 matches)
Rack2R2#sh access-list
Extended IP access list 140
10 permit udp any any eq snmptrap log-input (17 matches)
20 permit ip any any (15 matches)
Config:
snmp-server host 148.5.2.1 Community
snmp-server enable trap
int fa 0/0
snmp trap link-status
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:18 GMT-3