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

[Tim Stevenson]

You sure about that? It works fine on my lab box:

tstevens-6506#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
tstevens-6506(config)#int gig 1/13
tstevens-6506(config-if)#sh
tstevens-6506(config-if)#^Z
tstevens-6506#
Sep 14 13:40:10.876: %LINK-5-CHANGED: Interface GigabitEthernet1/13, 
changed state to administratively down
Sep 14 13:40:10.880: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet1/13, changed state to down
Sep 14 13:40:11.028: %SYS-5-CONFIG_I: Configured from console by console
tstevens-6506#sh logging | in LINE
Sep 14 13:40:10.880: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet1/13, changed state to down
tstevens-6506#

I see the message logged to my syslog server as well. Am running 18SXD, but 
I am not aware of any issue w/this in earlier releases either, nor am I 
aware of any reason this should be documented as unsupported on s720. What 
release are you running?

I will follow up with the tech pubs folks and let you know.

Tim


At 12:21 PM 9/14/2004, cisco-nsp-request at puck.nether.net mused:
>Date: Tue, 14 Sep 2004 14:00:34 -0500 (CDT)
>From: "Robert A. Hayden" <rhayden at geek.net>
>Subject: [c-nsp] Sup720 won't log link status changes? WTF?!
>To: cisco-nsp at puck.nether.net
>Message-ID: <Pine.LNX.4.44.0409141352110.11298-100000 at shell.geek.net>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>Ok, this is just a mid-afternoon rant, but I'm just stunned by this.
>
>Last week we began converting our campus backbone from Sup2/MSFC2s over to
>Sup720-3BXL cards.  A painful process since we're also moving from hybrid
>to IOS.
>
>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
>
>GARGH!
>
>Who was the marketing genius that decided people wouldn't want to know
>when ports went up or down?!??!  Is there _any_ logical reason for this
>that anyone can figure out?
>
>Ok, end of rant.  Time to enjoy the last nice days of the fall.
>
>Robert Hayden
>Senior Network Engineer
>University of Wisconsin Madison



Tim Stevenson, tstevens at cisco.com
Routing & Switching CCIE #5561
Technical Marketing Engineer, Catalyst 6500
Cisco Systems, http://www.cisco.com
IP Phone: 408-526-6759
********************************************************
The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.