[c-nsp] Sup720 won't log link status changes? WTF?!

[Ian Cox]

What version of code are you running?

The link up / down syslog messages are working on the 12.2(18)SXD release.


Sep 14 13:10:52.393 PDT: %LINK-5-CHANGED: Interface GigabitEthernet1/1, 
changed state to administratively down
Sep 14 13:10:52.397 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet1/1, changed state to down
Sep 14 13:10:54.969 PDT: %LINK-3-UPDOWN: Interface GigabitEthernet1/1, 
changed state to down
Sep 14 13:10:55.293 PDT: %LINK-3-UPDOWN: Interface GigabitEthernet1/1, 
changed state to up
Sep 14 13:10:55.297 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet1/1, changed state to up


ringebu#sh run int gig 1/1
Building configuration...

Current configuration : 164 bytes
!
interface GigabitEthernet1/1
  no ip address
  logging event link-status
  switchport
  switchport access vlan 2
  switchport mode access
  spanning-tree portfast
end

ringebu#sh ver | inc Version
IOS (tm) s72033_rp Software (s72033_rp-JK9O3SV-M), Version 12.2(18)SXD, 
RELEASE SOFTWARE (fc2)
ROM: System Bootstrap, Version 12.2(14r)S1, RELEASE SOFTWARE (fc1)
BOOTLDR: s72033_rp Software (s72033_rp-JK9O3SV-M), Version 12.2(18)SXD, 
RELEASE SOFTWARE (fc2)
X.25 software, Version 3.0.0.

ringebu# sh run int gig 1/2
Building configuration...

Current configuration : 78 bytes
!
interface GigabitEthernet1/2
  ip address 1.1.1.1 255.255.255.0
  logging event link-status
end


Sep 14 13:14:29.232 PDT: %LINK-3-UPDOWN: Interface GigabitEthernet1/2, 
changed state to up
Sep 14 13:14:29.236 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet1/2, changed state to up



Ian


At 03:34 PM 9/14/2004 -0400, Jared Mauch wrote:
>On Tue, Sep 14, 2004 at 09:26:08PM +0200, sthaug at nethelp.no wrote:
> > > Along the way I discover that the logs on the routers no longer show 
> when
> > > a port physically go up or down.  It will trap, but nothing actually
> > > occurs in the log files.  Of course, the "logging event link-status"
> > > command is still accepted, it just doesn't work.
> > >
> > > So, opening a case with TAC about this rather obvious shortcoming 
> results
> > > in the typic "it's supposed to be that way" response along with an
> > > invitation to submit a feature request.
> > >
> > > (Relevant release note buried so deep nobody could find it):
> > >     http://tinyurl.com/4a7kb
> >
> > Sounds like an excellent reason for *not* buying Sup720 - at least
> > until this if fixed. I agree, link status in the logs is important.
>
>         i'm talking to my support rep in the background on this..
>
>         i'm not 100% sure this is the case based on data he's passed
>back..
>
>         - jared
>
>--
>Jared Mauch  | pgp key available via finger from jared at puck.nether.net
>clue++;      | http://puck.nether.net/~jared/  My statements are only mine.
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/