cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
404
Views
10
Helpful
7
Replies

WS-X6348 reload

ybuecking
Level 1
Level 1

In the last months I had problems with the

Modul type WS-X6348.

I had at least 3 moduls in different Switches 6509, which all had experienced a couple of reloads in the last months. The show log counters is up to let´s say 21, and this is not a "counter" Problem.

In one case I also changed the modul, but there was another reload last weekend.

The software version is 6-3-5.

Does anybody know what could probably have caused the reload, or has the same problems ?

Show test and other "helpful" commands don´t show up with any problems.

There are no aligment or runts detected.

Any helpful hints are welcome.

best regards

yves

7 Replies 7

cminch
Level 1
Level 1

Hi,

I am not sure if the command still exsists but perhaps a 'sh health 1' might give you an insight. Look for High VDP misses. How is the power usage? You might want to see if there is a power change during the times of reload.

hi

"show health" is unfortunately not supported.

What do you mean by high VDP misses ?

I checked the "show enviroment all ", and it seems the power status is correct.

I dont think there is a power change, because only one specific module is affected.

Its always module 7.

Maybe there ´s a problem with the backplane ?

Is it possible that traffic , especially over a trunk connection causes a relaod ?

best regards

Yves

Hi,

Would have been interesting if the command did work. The command was a hidden command and showed a lot of the internal processes. VDP Misses a value you can see if certain problems on your SUPs and Line Cards. You could move the card to a different slot and see if it migrates. If it doesn't I would swap the chassis. It is possible the the traffic over a trunk will cause a reload. But this is more with 2900's and 4000's. Here again be looking at the VDP Misses you can sometimes see Astro Errors, which can effect the rest of the network. I'll do some snooping around what other command might help see what going on.

Regards,

Corey

Corey, that info applies to cat4k family switches only. The 6500 is based on a different architecture.

Yves,

Are there any log messages associated with the reset? 'sh logg buff'

There are a few reasons why a linecard might reset. Ensure all linecards (including the supervisors) are seated tightly and secured with the thumbscrews. If you could, please post any logging buffer messages associated with the reset.

Hi,

here are the latest buf messages:

I guess the next step would be to change the chassis, but somehow I REALLY would like to fix it without changing the fully loaded chassis, seems to be a lot of work.

Last but not least. Yes , the linecard is firmly seated, screws are tight.

best regards

yves

2003 Sep 12 19:55:03 MEZ +02:00 %SPANTREE-6-PORTFWD: Port 7/34 state in VLAN 473

changed to forwarding

2003 Sep 14 18:27:28 MEZ +02:00 %SNMP-5-ENTITYTRAP:Entity Mib last change time -

1563281550 ticks

2003 Sep 14 18:27:28 MEZ +02:00 %SNMP-5-MODULETRAP:Module 7 [Down] Trap

2003 Sep 14 18:27:46 MEZ +02:00 %SNMP-5-ENTITYTRAP:Entity Mib last change time -

1563279798 ticks

2003 Sep 14 18:28:10 MEZ +02:00 %SNMP-5-MODULETRAP:Module 7 [Up] Trap

2003 Sep 14 18:28:11 MEZ +02:00 %SYS-5-MOD_OK:Module 7 is online

2003 Sep 14 18:28:11 MEZ +02:00 %SYS-3-MOD_PORTINTFINSYNC:Port Interface in sync

for Module 7

2003 Sep 14 18:28:11 MEZ +02

-----------------------------------

Exceptions: 0

Loaded NMP version: 6.3(9)

Software version: bootflash:cat6000-sup.6-3-9.bin

Reload same NMP version count: 1

EOBC Exceptions/Hang: 0

Heap Memory Log:

Corrupted Block = none

------------------------------

Module 7 Log:

Reset Count: 21

Reset History: Sun Sep 14 2003, 18:27:46

Thu Sep 4 2003, 06:48:26

Wed Sep 3 2003, 14:55:36

Tue Sep 2 2003, 20:28:47

------------------------------------

I just found a bug:

CSCeb35612

Well, that doesn´t look good to me !!!

It does appear you are experiencing CSCeb35612. The fix is in the following CatOS releases and later:

6.4(6)

7.6(3)

8.1(2)

8.2(1)