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

[Robert A. Hayden]

Ok, have you ever have one of those days?

It seems I'm completely wrong.

When I discovered yesterday that I wasn't getting link logging, I swear I
entered the "logging event link-status default" command and tried it
again.  Heck my RCS systems show the change was written to memory.  
Somehow I must have missed something.

In any case, I logged back into one of my routers and executed the command
again and did a test:

r-chem-s353-2-node(config)#int te1/1
r-chem-s353-2-node(config-if)#shut
r-chem-s353-2-node(config-if)#
Sep 14 15:47:11: %LINK-5-CHANGED: Interface TenGigabitEthernet1/1, changed 
state to administratively down
Sep 14 15:47:11: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet1/1, changed state to down
Sep 14 15:47:11: %SPANTREE-SP-6-PORT_STATE: Port Te1/1 instance 1512 
moving from forwarding to disabled

r-chem-s353-2-node(config-if)#no shut
r-chem-s353-2-node(config-if)#
Sep 14 15:47:24: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1, changed 
state to up
Sep 14 15:47:27: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
TenGigabitEthernet1/1, changed state to up
Sep 14 15:47:27: %SPANTREE-SP-6-PORT_STATE: Port Te1/1 instance 1512 
moving from disabled to blocking
Sep 14 15:47:28: %DTP-SP-5-TRUNKPORTON: Port Te1/1 has become dot1q 
trunk
Sep 14 15:47:28: %LINK-3-UPDOWN: Interface Vlan1512, changed state to 
up
Sep 14 15:47:28: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
Vlan1512, changed state to up
Sep 14 15:47:28: %SPANTREE-SP-6-PORT_STATE: Port Te1/1 instance 1512
moving from blocking to forwarding
Sep 14 15:48:08: %OSPF-5-ADJCHG: Process 10, Nbr 146.151.160.11 on 
Vlan1512 from LOADING to FULL, Loading Done

*sigh*

So, the gist of it is that with 12.2.(18)SXD it appears, as long as you 
tell it to, you will indeed get link status log messages and that I jumped 
the gun in my rant after seeing the TAC case response and the release note 
caveat.

My apologies and my thanks to everyone that contacted me to either collect 
information or to politely call me a dumbass (because obviously I am on 
this one).

That said, perhaps to save a little face, why the heck isn't this on by 
default?

Ok.  Is it Friday yet?

- Robert


On Tue, 14 Sep 2004, Robert A. Hayden wrote:

> Per the notes, the command is apparently not supported on the sup720.  My
> tests indicated also that the command had no effect.
> 
> On Tue, 14 Sep 2004, Jay Ford wrote:
> > 
> > It seems that the interface command "logging event link-status" is required
> > to enable link up/down logging.  That should be enabled by default in my
> > opinion, but at least it seems to be there.