Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: nsp: extreme

alpine, harware-fault, recovery

 

 

nsp extreme RSS feed   Index | Next | Previous | View Threaded


marcin at leon

Sep 11, 2007, 3:54 AM

Post #1 of 4 (1792 views)
Permalink
alpine, harware-fault, recovery

hello,

I have a problem with Alpine3808 switch (EW7.6).
It sais, that there is a hardware fault and that the system didn't fully
start because of that.
*** HARDWARE FAILURE HAS BEEN DETECTED IN THE SYSTEM ***

the problem is, that show diagnostics sais nothing about the problem
(problem detected after diagnostics test).
However, there was an information in log, that slot 6 port 3 MAC chip
failed.
ok, I've removed this module, I've even removed all the modules.

Nothing happend, I have still limited access to commands.

clear log is not physically clearing the log, because after reboot the log
is back as it was before "clear log".

Whatever - how to handle this problem ?
I need to run diagnostics again, but how ? How to enable full access to
commands ?

Regards,
Marcin

(THE LOG FILE BELOW)

09/11/2007 13:31:19.10 <Info:USER> admin logged in through console
09/11/2007 13:31:15.40 <Info:SYST> Memory successfully allocated for
compression
09/11/2007 13:31:11.40 <Crit:SYST> System has not been initialized
09/11/2007 13:31:11.40 <Crit:SYST> System has recorded diag failures
09/11/2007 13:31:11.17 <Info:KERN> NV:Booted up with Standard
Configuration Mode
09/11/2007 13:31:11.17 <Erro:KERN> NV:Config database is empty; using
default configuration
09/11/2007 13:31:11.17 <Info:KERN> NV:Using primary config database from
FLASH
09/11/2007 13:31:10.00 <Info:KERN> System startup Version 7.6.4.4 [ssh]
[wlan] by Release_Master on 04/27/07 10:23:04
09/11/2007 13:26:50.40 <Crit:SYST> System has not been initialized
09/11/2007 13:26:50.40 <Crit:SYST> System has recorded diag failures
09/11/2007 13:26:50.17 <Erro:KERN> NV:Config database is empty; using
default configuration
09/11/2007 13:24:36.40 <Crit:SYST> System has not been initialized
09/11/2007 13:24:36.40 <Crit:SYST> System has recorded diag failures
09/11/2007 13:23:18.82 <Crit:SYST> System has not been initialized
09/11/2007 13:23:18.82 <Crit:SYST> System has recorded diag failures
09/11/2007 13:20:05.82 <Crit:SYST> System has not been initialized
09/11/2007 13:20:05.82 <Crit:SYST> System has recorded diag failures
09/11/2007 13:15:11.29 <Warn:USER> Login failed for user root through
console
09/11/2007 13:14:53.40 <Crit:SYST> System has not been initialized
09/11/2007 13:14:53.40 <Crit:SYST> System has recorded diag failures
09/11/2007 13:12:27.82 <Crit:SYST> System has not been initialized
09/11/2007 13:12:27.82 <Crit:SYST> System has recorded diag failures
09/11/2007 13:10:23.82 <Crit:SYST> System has not been initialized
09/11/2007 13:10:23.82 <Crit:SYST> System has recorded diag failures
09/11/2007 13:05:37.82 <Crit:SYST> System has not been initialized
09/11/2007 13:05:37.82 <Crit:SYST> System has recorded diag failures
09/11/2007 12:54:52.82 <Crit:SYST> System has not been initialized
09/11/2007 12:54:52.82 <Crit:SYST> System has recorded diag failures
09/11/2007 12:48:04.75 <Erro:SYST> Card 4 type=35 does not match the
configured card type (32).
09/11/2007 12:48:04.65 <Erro:SYST> Card 3 type=35 does not match the
configured card type (32).
09/11/2007 12:48:04.55 <Erro:SYST> Card 2 type=33 does not match the
configured card type (35).
09/11/2007 12:47:58.22 <Warn:USER> Login failed for user admin through
console
09/04/2007 17:09:26.09 <Erro:SYST> cardSM_NONOPERATIONAL(6): Invalid
event(9).
09/04/2007 17:09:25.94 <Erro:PORT> init TOS Tx look-up table failed on
slot 6 port 7!
09/04/2007 17:09:25.94 <Erro:PORT> sync content of LUT table index 8 error
on slot 6 port 7
09/04/2007 17:09:25.94 <Crit:SYST> Set card 6 to NON_OPERATIONAL due to
Hardware failure
09/04/2007 17:09:25.93 <Crit:SYST> Sys-health-check [ACTION] (hardware
failure) (CARD_HWFAIL_VLAN_LKUP_REG_TIMEOUT) slot 6
09/04/2007 17:09:25.93 <Crit:PORT> MAC Chip of slot 6 port 3 is not ready
09/04/2007 09:42:29.74 <Erro:SYST> Card 4 type=33 does not match the
configured card type (32).
09/04/2007 09:42:29.64 <Erro:SYST> Card 3 type=33 does not match the
configured card type (32).
09/04/2007 09:42:29.54 <Erro:SYST> Card 2 type=33 does not match the
configured card type (35).
09/04/2007 09:36:38.74 <Erro:SYST> Card 4 type=33 does not match the
configured card type (32).
09/04/2007 09:36:38.64 <Erro:SYST> Card 3 type=33 does not match the
configured card type (32).
09/04/2007 09:36:38.54 <Erro:SYST> Card 2 type=33 does not match the
configured card type (35).
09/04/2007 09:35:51.40 <Crit:SYST> System rebooted
09/04/2007 09:30:48.52 <Warn:USER> Login failed for user admin through
console
09/04/2007 09:30:47.68 <Erro:SYST> Card 4 type=33 does not match the
configured card type (32).
09/04/2007 09:30:47.58 <Erro:SYST> Card 3 type=33 does not match the
configured card type (32).
09/04/2007 09:30:47.48 <Erro:SYST> Card 2 type=33 does not match the
configured card type (35).
Displayed 49 messages from memory-buffer.


Phil.Bartlett at comtek

Sep 11, 2007, 4:35 AM

Post #2 of 4 (1663 views)
Permalink
alpine, harware-fault, recovery [In reply to]

Marcin,

Try the following set of commands to see if it will restore full access
to the commands. If not it might require a higher leverl of software to
be installed or the eeprom reloaded with software (which we can do)

Clear log Static
Clear log diag-status
Clear log diag-status remap
Clear log mes mem
clear log mes nv


Rgds


Phil Bartlett
Comtek Network Systems (UK) Ltd
+44 845 450 1626
http://www.comtek.co.uk


-----Original Message-----
From: extreme-nsp-bounces [at] puck
[mailto:extreme-nsp-bounces at puck.nether.net] On Behalf Of Marcin Kuczera
Sent: 11 September 2007 12:55
To: extreme-nsp at puck.nether.net
Subject: [e-nsp] alpine, harware-fault, recovery

hello,

I have a problem with Alpine3808 switch (EW7.6).
It sais, that there is a hardware fault and that the system didn't fully
start because of that.
*** HARDWARE FAILURE HAS BEEN DETECTED IN THE SYSTEM ***

the problem is, that show diagnostics sais nothing about the problem
(problem detected after diagnostics test).
However, there was an information in log, that slot 6 port 3 MAC chip
failed.
ok, I've removed this module, I've even removed all the modules.

Nothing happend, I have still limited access to commands.

clear log is not physically clearing the log, because after reboot the
log is back as it was before "clear log".

Whatever - how to handle this problem ?
I need to run diagnostics again, but how ? How to enable full access to
commands ?

Regards,
Marcin

(THE LOG FILE BELOW)

09/11/2007 13:31:19.10 <Info:USER> admin logged in through console
09/11/2007 13:31:15.40 <Info:SYST> Memory successfully allocated for
compression
09/11/2007 13:31:11.40 <Crit:SYST> System has not been initialized
09/11/2007 13:31:11.40 <Crit:SYST> System has recorded diag failures
09/11/2007 13:31:11.17 <Info:KERN> NV:Booted up with Standard
Configuration Mode
09/11/2007 13:31:11.17 <Erro:KERN> NV:Config database is empty; using
default configuration
09/11/2007 13:31:11.17 <Info:KERN> NV:Using primary config database from
FLASH
09/11/2007 13:31:10.00 <Info:KERN> System startup Version 7.6.4.4 [ssh]
[wlan] by Release_Master on 04/27/07 10:23:04
09/11/2007 13:26:50.40 <Crit:SYST> System has not been initialized
09/11/2007 13:26:50.40 <Crit:SYST> System has recorded diag failures
09/11/2007 13:26:50.17 <Erro:KERN> NV:Config database is empty; using
default configuration
09/11/2007 13:24:36.40 <Crit:SYST> System has not been initialized
09/11/2007 13:24:36.40 <Crit:SYST> System has recorded diag failures
09/11/2007 13:23:18.82 <Crit:SYST> System has not been initialized
09/11/2007 13:23:18.82 <Crit:SYST> System has recorded diag failures
09/11/2007 13:20:05.82 <Crit:SYST> System has not been initialized
09/11/2007 13:20:05.82 <Crit:SYST> System has recorded diag failures
09/11/2007 13:15:11.29 <Warn:USER> Login failed for user root through
console
09/11/2007 13:14:53.40 <Crit:SYST> System has not been initialized
09/11/2007 13:14:53.40 <Crit:SYST> System has recorded diag failures
09/11/2007 13:12:27.82 <Crit:SYST> System has not been initialized
09/11/2007 13:12:27.82 <Crit:SYST> System has recorded diag failures
09/11/2007 13:10:23.82 <Crit:SYST> System has not been initialized
09/11/2007 13:10:23.82 <Crit:SYST> System has recorded diag failures
09/11/2007 13:05:37.82 <Crit:SYST> System has not been initialized
09/11/2007 13:05:37.82 <Crit:SYST> System has recorded diag failures
09/11/2007 12:54:52.82 <Crit:SYST> System has not been initialized
09/11/2007 12:54:52.82 <Crit:SYST> System has recorded diag failures
09/11/2007 12:48:04.75 <Erro:SYST> Card 4 type=35 does not match the
configured card type (32).
09/11/2007 12:48:04.65 <Erro:SYST> Card 3 type=35 does not match the
configured card type (32).
09/11/2007 12:48:04.55 <Erro:SYST> Card 2 type=33 does not match the
configured card type (35).
09/11/2007 12:47:58.22 <Warn:USER> Login failed for user admin through
console
09/04/2007 17:09:26.09 <Erro:SYST> cardSM_NONOPERATIONAL(6): Invalid
event(9).
09/04/2007 17:09:25.94 <Erro:PORT> init TOS Tx look-up table failed on
slot 6 port 7!
09/04/2007 17:09:25.94 <Erro:PORT> sync content of LUT table index 8
error on slot 6 port 7
09/04/2007 17:09:25.94 <Crit:SYST> Set card 6 to NON_OPERATIONAL due to
Hardware failure
09/04/2007 17:09:25.93 <Crit:SYST> Sys-health-check [ACTION] (hardware
failure) (CARD_HWFAIL_VLAN_LKUP_REG_TIMEOUT) slot 6
09/04/2007 17:09:25.93 <Crit:PORT> MAC Chip of slot 6 port 3 is not
ready
09/04/2007 09:42:29.74 <Erro:SYST> Card 4 type=33 does not match the
configured card type (32).
09/04/2007 09:42:29.64 <Erro:SYST> Card 3 type=33 does not match the
configured card type (32).
09/04/2007 09:42:29.54 <Erro:SYST> Card 2 type=33 does not match the
configured card type (35).
09/04/2007 09:36:38.74 <Erro:SYST> Card 4 type=33 does not match the
configured card type (32).
09/04/2007 09:36:38.64 <Erro:SYST> Card 3 type=33 does not match the
configured card type (32).
09/04/2007 09:36:38.54 <Erro:SYST> Card 2 type=33 does not match the
configured card type (35).
09/04/2007 09:35:51.40 <Crit:SYST> System rebooted
09/04/2007 09:30:48.52 <Warn:USER> Login failed for user admin through
console
09/04/2007 09:30:47.68 <Erro:SYST> Card 4 type=33 does not match the
configured card type (32).
09/04/2007 09:30:47.58 <Erro:SYST> Card 3 type=33 does not match the
configured card type (32).
09/04/2007 09:30:47.48 <Erro:SYST> Card 2 type=33 does not match the
configured card type (35).
Displayed 49 messages from memory-buffer.


_______________________________________________
extreme-nsp mailing list
extreme-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp


Stephane.Grosjean at telindus

Sep 11, 2007, 8:14 AM

Post #3 of 4 (1671 views)
Permalink
alpine, harware-fault, recovery [In reply to]

Hi,


I second Phil answer, I often was able to regain full access after issuing both "clear log static" and "clear log diag".


Stephane.
----------------------

>Marcin,
>
>Try the following set of commands to see if it will restore full access
>to the commands. If not it might require a higher leverl of software to
>be installed or the eeprom reloaded with software (which we can do)
>
>Clear log Static
>Clear log diag-status
>Clear log diag-status remap
>Clear log mes mem
>clear log mes nv


marcin at leon

Sep 12, 2007, 2:29 AM

Post #4 of 4 (1686 views)
Permalink
alpine, harware-fault, recovery [In reply to]

well,

It seems that the switch/module behaves very strange.

The module is GM-4Ti, in slot #6 sometimes it doesn't pass diagnostics.
However, located in slot #4, it works fine.

Other GM-4Ti located in slot #6 works fine, no problems with diagnostics.

Any idea about what could be the reason of such problems ?
Connector ? to a backplane ?

Regards,
Marcin

nsp extreme RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.