"no snmp trap link-status" this command is accepted but a syslog msgs seen

Unanswered Question
Sep 2nd, 2009
User Badges:

CAT 6500 running IOS version:


Partial config:


interface GigabitEthernet2/23

bandwidth 1000000

ip address 10.x.x.x

no ip redirects

no ip unreachables

no ip proxy-arp

ip authentication mode eigrp 45 md5

ip authentication key-chain eigrp 45 xxxxx

ip summary-address eigrp 45 10.x.x.x. 5

ip summary-address eigrp 45 10.y.y.y 5

load-interval 30

delay 1

udld port aggressive

no snmp trap link-status

Note that logging event link-status is disabled by default so "no logging event link-status" command is not displayed in this configuration.

The config would normally have a line that reads logging event link-status to enable link status events being logged.

Also note that snmp link status events are disabled to be thorough but I believe the error is being generated by syslog as indicated below, in this instance when we bounced Gi2/23 interface.

Sep 3 08:31:39 bnz-80boul-l10-cs-01.bnz.tcnz.sytecnms.net [local7.notice]: 513: Sep 3 08:32:34.165: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface GigabitEthernet2/23, changed state to down

Sep 3 08:31:39 bnz-80boul-l10-cs-01.bnz.tcnz.sytecnms.net [local7.notice]: 514: .Sep 3 08:32:34.173: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 45: Neighbor (GigabitEthernet2/23) is down: interface down

Sep 3 08:31:40 bnz-80boul-l10-cs-01.bnz.tcnz.sytecnms.net [local7.err]: 515: Sep 3 08:32:34.173: %LINK-SP-3-UPDOWN: Interface GigabitEthernet2/23, changed state to down

Sep 3 08:34:19 bnz-80boul-l10-cs-01.bnz.tcnz.sytecnms.net [local7.err]: 516: Sep 3 08:35:14.553: %LINK-SP-3-UPDOWN: Interface GigabitEthernet2/23, changed state to up

Sep 3 08:34:20 bnz-80boul-l10-cs-01.bnz.tcnz.sytecnms.net [local7.notice]: 517: .Sep 3 08:35:14.575: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 45: Neighbor (GigabitEthernet2/23) is up: new adjacency

Sep 3 08:34:20 bnz-80boul-l10-cs-01.bnz.tcnz.sytecnms.net [local7.notice]: 518: Sep 3 08:35:14.557: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface GigabitEthernet2/23, changed state to up

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
astanislaus Wed, 09/02/2009 - 16:41
User Badges:

So why are syslog messages generated for Gi2/23 in spite of saying no snmp trap link-status under this interface.

More of the config:


logging trap notifications

logging source-interface Loopback0

logging 172.x.x.x

!snmp-server community RO 98

snmp-server trap-source Loopback0

snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart


This Discussion