[c-nsp] 7600 weirdness

[Tassos Chatzithomaoglou]

I don't know how often you got the snmp traps, but maybe there was some micro flapping happening and the logging process 
didn't catch it.
I have seen many down/up snmp traps at the same time (*), while there where only a few of logging events (and no drops 
due to rate-limit). Besides checking for any "logging rate-limit" configs, "sh int x/x" can probably give you more 
details about actual resets.

* There is a bug on dot1-tunnel ports, where the reset of them causes cdp to be disabled. Many times, although there 
were no logs about down/up, cdp was disabled under these ports...probably due to a very fast reset.

--
Tassos

Timothy Young wrote on 16/09/2009 19:07:
> Hello,
> 
> I have a pair of 7606s running single SUP 720 – 3BXLs with Version
> 12.2(18)SXF7 (IP Services)
> 
> What I saw last night is perplexing and mind you I’m not the greatest with
> these devices.
> 
> Sep 15 18:39:04: %LINK-3-UPDOWN: Interface GigabitEthernet4/41, changed
> state to up
> 
> Sep 15 18:39:04: %LINK-SP-3-UPDOWN: Interface GigabitEthernet4/41, changed
> state to up
> 
> Sep 15 18:39:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet4/41, changed state to up
> 
> Sep 15 18:39:07: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface
> GigabitEthernet4/41, changed state to up
> 
> Sep 15 18:39:08: %LINK-SP-3-UPDOWN: Interface GigabitEthernet1/2, changed
> state to up
> 
> Sep 15 19:00:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet4/41, changed state to down
> 
> Sep 15 19:00:10: %LINK-3-UPDOWN: Interface GigabitEthernet4/41, changed
> state to down
> 
> Sep 15 19:00:10: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface
> GigabitEthernet4/41, changed state to down
> 
> Sep 15 19:00:10: %LINK-SP-3-UPDOWN: Interface GigabitEthernet4/41, changed
> state to down
> 
> Sep 15 19:44:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> GigabitEthernet4/3, changed state to down
> 
> Sep 15 19:44:08: %LINEPROTO-SP-5-UPDOWN: Line protocol on Interface
> GigabitEthernet4/3, changed state to down
> 
> Sep 15 19:44:08: %LINK-3-UPDOWN: Interface GigabitEthernet4/3, changed state
> to down
> 
> 
> 
> So basically I have interfaces bouncing regularly – but there’s 45 minutes
> of time where nothing showed in my logs at all.
> 
> That is very uncommon, but what makes this perplexing is that the 7600 still
> sent traps to my Solarwinds box about multiple port up / downs during the
> 19:00:10 to 19:44:08 timeframe.  Nothing else on the box had issues, I had
> no network problems (my voice network would’ve flaked to high hell if I had
> any cpu / network  issues).
> 
> My CPU holds between 20-30% at any given time – with the occasional spike up
> near 80ish (and when I say spike – I literally mean momentarily –it doesn’t
> hold there at all).
> 
> The history for the CPU doesn’t show anything corresponding to that time
> frame and even spikes.
> 
> Memory looks fine on the box with tons free.
> 
> What I’m looking for is where I can start looking on the box – or ideas that
> may help me sort out why the box seems to have flipped and stopped reporting
> for a bit.
> 
> I’m familiar with the logging – but anything more and it gets fuzzy for me.
> 
> 
> 
> Thanks
> 
> 
> Tim
> _______________________________________________
> 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/
>