[nsp] Catalyst6509 GE interface hang without any indication

[Sukumar Subburayan]

Joe,

Sorry, there was a typo in the bug-id I mentioned.

It should be CSCeb39694 and *not* CSCed37694.

sukumar


>
> >a) When the box hangs does the sup2 hang or is it just 15/1?
>
> With the first box suffered from interface hang, only ge-1/1  hang ( I
> showed its info. in previous message), with the second on the whole
> system hang.
> and,

Your entire box hanging problem is related to a software caveat (please
refer  CSCed37694). If you had a console to the box you probably would
have seen some characters (like continuous "." or "R") printed.

This caveat affects releases 7.6(1) thro 7.6(4) and only for Sup2. Since
you are  running, 7.6(1), I think, this is the bug you are running into.

Customers with Sup2 running 7.6.x code are encouraged to consider
upgrading to 7.6(7).

sukumar

>
> 6509C-msfc-hz>sh scp status
> Rx 10691273,  Tx 7072654,  Sap 13
> Id     Channel name    current/peak/retry/total  time(queue/process)
> -- ------------------- ------------------------  -------------------
> 0  SCP async: TCAM MGR  0/ 20/  0/  162         13412/13412/   4
> 1  SCP async: Fake MCA  0/  0/  0/    0            0/   0/   0
> 3  SCP async: RUN_CONF  0/ 33/  0/   59          176/ 172/ 172
> 5  SCP async: HA SRM S  0/  2/  0/    7            0/   4/   0
> 6  SCP async: HA SRM M  0/  1/  0/    6            0/   0/   0
> 7  SCP Unsolicit:0      0/  3/  0/1233574            0/   0/ 396
> 8  SCP async: Draco-NM  0/  1/  0/    2            0/ 424/   0
> 9  SCP async: NMP       0/  0/  0/    0            0/   0/   0
> 10 SCP async: constall  0/  0/  0/    0            0/   0/   0
> 11 SCP async: [cfg] l3  0/ 16/  0/   19         1348/ 408/   8
> 12 SCP async: [mls] l3  0/  2/  0/10248            8/ 472/  20
>
> but, show inband, sh scp failcnt  seems not work. how could I check
> interface asicreg?
>
>
> >4) To note a few things from your email below - 15/1: Is there any
> correlation between Gig to M160 not sending/receiving traffic and 15/1
> >freezing? OR is 15/1 freezing the only cause of traffic not being
> forwarded. I guess I am saying the MSFC is problem and not the gig
port
> >between the 6500 and the m160. Is this valid?
>
> the problem went away when We restart ge-1/1. Other part seems good
when
> I noticed no traffic on the ge link.
>
> >5) Assuming that scp is not the problem I would set up a span and
> capture traffic up until the msfc fails.  Then see if you can see what
> >might be causing it (I have done this many times - Let me know if you
> need some ideas).
>
> Maybe I have to do this, but the traffic on that switch is about
> 800Mbps. Too heavy to my PC.
>
>
> Thank you very much !
>
> Joe
>
> _______________________________________________
> 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/
>