Hello,
Please find below the answer for your question
A Fan Fails to Be Registered Because Versions of MonitorBus on the Master and Slave MPUs of an NE40E are Incompatible
Context
NOTE:
This troubleshooting case comes from a live network and is for reference only. The device version involved is NE40E V600R001C00SPC800. When you troubleshoot similar problems, take into consideration your particular network conditions and device versions.
Fault Symptom
The status of a fan in an NE40E is displayed as Unregistered Abnormal, and the alarm information displays the slot of the fan as MonitorBUS node failed. The fan runs normally.
<HUAWEI> display deviceNE40E-X3's Device status:
Slot # Type Online Register Status Primary
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1 LPU Present Registered Normal NA
4 MPU Present NA Normal Master
5 MPU Present Registered Normal Slave
6 CLK Present Registered Normal Master
7 CLK Present Registered Normal Slave
8 PWR Present Registered Normal NA
9 PWR Present Registered Normal NA
10 FAN Present Unregistered Abnormal NA
<HUAWEI> display alarm all----------------------------------------------------------------------------
Index Level Date Time Info
1 Emergency 11-03-24 14:07:34 SlotID:10 is failed, MonitorBUS node failed
----------------------------------------------------------------------------
Fault Analysis
The display temperature command output shows that the temperature of each part of the device is normal. However, the slave MPU in slot 5 and the fan in slot 10 fail to display the temperature but display abnormal information.
SlotID1 :
Base-Board, Unit:C, Slot1
PCB I2C Addr Chl Status Minor Major Fatal Adj_speed Temp
TMin Tmax (C)
-----------------------------------------------------------------
LPUK 1 0 0 NORMAL 70 80 90 65 70 38
LPUK 1 1 0 NORMAL 76 85 95 65 75 44
LPUK 1 2 0 NORMAL 73 83 93 63 73 43
LPUK 1 4 0 NORMAL 70 80 90 60 70 43
LPUK 1 5 0 NORMAL 70 80 90 60 70 35
LPUK 1 6 0 NORMAL 70 80 90 60 70 41
LPUK 1 7 0 NORMAL 66 75 80 60 66 43
LPUK 2 76 2 NORMAL 90 96 102 80 90 56
EBGFB 3 73 0 NORMAL 75 85 91 60 70 19
EBGFB 3 74 0 NORMAL 80 90 96 65 75 27
EBGFB 4 73 0 NORMAL 75 85 91 60 70 20
EBGFB 4 74 0 NORMAL 80 90 96 65 75 26
SlotID4 :
Base-Board, Unit:C, Slot4
PCB I2C Addr Chl Status Minor Major Fatal Adj_speed Temp
TMin Tmax (C)
-----------------------------------------------------------------
MPUD 0 0 0 NORMAL 73 79 90 56 67 25
MPUD 0 1 0 NORMAL 73 79 90 56 67 20
MPUD 0 2 0 NORMAL 73 79 90 56 67 23SlotID5 : MonitorBUS not work.SlotID10 : MonitorBUS communicate fail.
However, the fan is running normally. After the backup fan replaces the fan, the problem still exists.
Based on the command output about the temperature, it is suspected that MonitorBUS of the slave MPU results in the registration failure of the fan. Pull out the slave MPU and run the display device command. The fan succeeds to be registered and runs normally. Therefore, the problem is caused by MonitorBUS of the slave MPU.
Procedure
Insert the slave MPU back and run the upgrade mpu 5 startup monitorbus force command. Upgrade MonitorBus of the slave MPU.
After the preceding operations are complete, the fan succeeds to be registered and the fault is rectified.
Summary
The fan mbusnode communicates with the main MonitorBus module of the MPU to control the fan module, and deliver the status of the fan module and the fault information. If MonitorBUS of the master MPU does not work and fails to communicate with the fan, the versions of MonitorBus on the master and slave MPUs are probably incompatible.
