Znyx Networks bh5700 Manuale Utente
sensor information. Examine the System Event Log (SEL) on the ShMM and determine if critical
sensor events have been logged for the switch in question.
sensor events have been logged for the switch in question.
If the switch has reported critical sensor data for temperature or voltage, the ShMM can prevent
it from booting. To determine if the critical sensor events persist, it may be necessary to alter the
rules enforced by the ShMM to allow the switch to receive back-end power and boot (see the
ShMM documentation for instruction).
it from booting. To determine if the critical sensor events persist, it may be necessary to alter the
rules enforced by the ShMM to allow the switch to receive back-end power and boot (see the
ShMM documentation for instruction).
If other FRUs, in addition to the failed switch, are reporting similar critical sensors, such as
temperature or voltage, this may indicate a chassis-related failure (such as fans or power supply).
temperature or voltage, this may indicate a chassis-related failure (such as fans or power supply).
Voltage: If the Ethernet Switch Blade continues to report voltage critical threshold error after
changing the rules in the ShMM to allow it to receive power, then return the switch for repair.
changing the rules in the ShMM to allow it to receive power, then return the switch for repair.
Temperature: If the Ethernet Switch Blade continues to report a temperature critical temperature
error after changing the rules, check the fans to make sure that there is sufficient airflow to the
switch. If airflow is sufficient, and the temperature threshold is still reported, then return the
switch for repair.
error after changing the rules, check the fans to make sure that there is sufficient airflow to the
switch. If airflow is sufficient, and the temperature threshold is still reported, then return the
switch for repair.
Analyzing Mstate information for the switch
The SEL will also contain Mstate information for the switch that can be useful in determining
conditions related to a failed boot. Knowing the state change transition history in the SEL can
help to narrow down activation problems with the switch. The states are defined as follows:
conditions related to a failed boot. Knowing the state change transition history in the SEL can
help to narrow down activation problems with the switch. The states are defined as follows:
M0 – No power and hot swap handle open
M1 – No communications. Wait in M1 until hot swap ejector is closed.
M2 – FRU announces its presence to the ShMM and awaits activation permission
M3 – Activation
M4 - Operational state; command issued to enable back-end power.
M5 – Deactivation request, such as hotswap ejector opened
M6 – Deactivation granted by ShMM
M7 – Unexpected loss of communication between FRU and ShMM
The information in the SEL will mostly reflect problems that can be related to the IPMC functions
of the switch. Other problems related to loading the switch software environment during boot
might require further analysis of the switch itself.
of the switch. Other problems related to loading the switch software environment during boot
might require further analysis of the switch itself.
Checking the ekey Status From the Shelf Manager
You can check the ekey status from the shelf manager with the
clia board <x>
command.
Shelf Manager commands:
Ethernet Switch Blade User's Guide
release 3.2.2j
page 153