Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Blue

IOS bug? Cisco linkDown traps with locIfReason: up

Lately I've noticed a number of instances where Cisco devices sent linkDown traps with "locIfReason: up". Is there any known bug for this kind of behavior?

For example: A cat6k sent:

1184761877 7 Wed Jul 18 08:31:17 2007 rtr1 - Cisco Agent Interface Down (linkDown Trap) on interface: GigabitEthernet2/43 locIfReason: up;4 .1.3.6.1.6.3.1.1.5.3.1.3.6.1.4.1.9.1.283 0

A 2600 sent:

1182869108 7 Tue Jun 26 10:45:08 2007 access1 - Cisco Agent Interface Down (linkDown Trap) on interface: FastEthernet0/0 locIfReason: up;4 .1.3.6.1.6.3.1.1.5.3.1.3.6.1.4.1.9.1.469 0

A normal Cisco linkUp trap looks like this (with the correct OID fragment ...5.4.1...):

1182866869 7 Tue Jun 26 10:07:49 2007 rtr2 - Cisco Agent Interface Up (linkUp Trap) on interface: GigabitEthernet3/23 locIfReason: up;1 .1.3.6.1.6.3.1.1.5.4.1.3.6.1.4.1.9.1.283 0

3 REPLIES
Cisco Employee

Re: IOS bug? Cisco linkDown traps with locIfReason: up

This is most likely related to CSCeb46140 which covers a lot of linkUp/Down trap problems of this nature (you're probably seeing symptoms described in CSCed09166, but that bug was duped to the first one). Check to see if you're running one of the affected versions of code.

Blue

Re: IOS bug? Cisco linkDown traps with locIfReason: up

The bug seems limited to IETF traps. The devices I checked all have the straight non-IETF [Cisco] SNMP traps configured. The 2600 is running an affected version. The cat6k's are running 12.1.x that's not on the affected list at all, though CSCeb46140 does have 12.1(22)EA06 among "First Fixed-in Version".

Alternatively, is it plausible these traps are legitimate in a scenario when someone unplugs the cable from an ethernet int without configuring "admin down" first? I see some of these trap source ints are in the following state immediately after the traps:

GigabitEthernet2/43 is up, line protocol is down (notconnect)

And there's this sequence of traps from a single int last night:

1184816683 7 Wed Jul 18 23:44:43 2007 rtr3 - Cisco Agent Interface Down (linkDown Trap) on interface: FastEthernet9/7 locIfReason:up;4 .1.3.6.1.6.3.1.1.5.3.1.3.6.1.4.1.9.1.283 0

1184816683 7 Wed Jul 18 23:44:43 2007 rtr3 - Cisco Agent Interface Up (linkUp Trap) on interface: FastEthernet9/7 locIfReason:up;1 .1.3.6.1.6.3.1.1.5.4.1.3.6.1.4.1.9.1.283 0

1184816892 7 Wed Jul 18 23:48:12 2007 rtr3 - Cisco Agent Interface Up (linkUp Trap) on interface: FastEthernet9/7 locIfReason:up;1 .1.3.6.1.6.3.1.1.5.4.1.3.6.1.4.1.9.1.283 0

Cisco Employee

Re: IOS bug? Cisco linkDown traps with locIfReason: up

There are a lot of bugs duped to the one I mentioned, and I still think it is a good candidate. The problem was reported for certain Cat6K code. Which code are you running?

The locIfReason should reflect the procotol status, so a linkDown trap with a locIfReason of up is not right.

739
Views
5
Helpful
3
Replies