DEVM/1/hwChassisFail_active

Procedure

• Cause 131328: The dustproof of the cabinet not cleaned.

  1. Clean the air filter of the cabinet in time.

  2. Run the reset dustproof run-time command to check whether the running time of the air filter reaches the cleaning cycle.

  3. If the alarm persists, collect alarm, log, and configuration information, and contact technical support engineers.

  4. The procedure ends.

• Cause 131330: MPU in the chassis is not full.

  1. Install an additional main board in the chassis. Then, check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 3.
  • If the alarm persists, go to Step 2.

  2. Collect trap, log, and configuration information, and contact technical support.

  3. End.

• Cause 131333: The fan or power dismatch.

  1. Replace the fan module. Then, check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 3.
  • If the alarm persists, go to Step 2.

  2. Collect trap, log, and configuration information, and contact technical support.

  3. End.

• Cause 131340: Power type mismatch.

  Collect trap, log, and configuration information, and contact technical support.

• Cause 131343: The power supply would be abnormal because excessive fan boards were installed.

  1. Check the slot where the fan board resides. If the fan board is in position, remove the fan board from the slot and check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 3.
  • If the alarm persists, go to Step 2.

  2. Collect trap, log, and configuration information, and contact technical support.

  3. End.

• Cause 131344: The switch 1 on the power panel is off.

  1. Check whether switch 1 on the power panel is closed.

  • If switch 1 is not closed, go to Step 2.
  • If switch 1 is closed, go to Step 3.

  2. Close switch 1 and check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 3.

  3. Collect trap, log, and configuration information, and contact technical support.

  4. End.

• Cause 131345: CMUs were not fully configured.

  1. Check whether CMUs are fully configured.

  • If not, go to Step 2.
  • If so, go to Step 3.

  2. Install CMUs based on configuration requirements, then check whether the alarm persists.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 3.

  3. Collect trap, log, and configuration information, and contact technical support.

  4. End.

• Cause 131346: The switch 2 on the power panel is off.

  1. Check whether switch 2 on the power panel is closed.

  • If switch 2 is not closed, go to Step 2.
  • If switch 2 is closed, go to Step 3.

  2. Close switch 2 and check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 3.

  3. Collect trap, log, and configuration information, and contact technical support.

  4. End.

• Cause 131347: The number of pm on two plane is different.

  1. Check whether the number of PMs on the two planes are consistent.

  • If yes, go to Step 3.
  • If no, go to Step 2.

  2. Install the same number of PMs on the two planes.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 3.

  3. Collect trap, log, and configuration information, and contact technical support.

  4. End.

• Cause 131348: Device power is insufficient.

  1. Check whether enough power modules are installed as required.

  • If yes, go to Step 3.
  • If no, go to Step 2.

  2. Install enough power modules as required.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 3.

  3. Collect trap, log, and configuration information, and contact technical support.

  4. End.

• Cause 131349: The dustproof gate is not closed.

  1. Check whether the dust filter door is closed as required.

  • If yes, go to Step 3.
  • If no, go to Step 2.

  2. Close the dust filter door.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 3.

  3. Collect trap, log, and configuration information, and contact technical support.

  4. End.

• Cause 131350: The power supply would be abnormal because power limit was configured insufficiently.

  1. Confirm with the customer whether the specified power consumption limit can be reached.

  • If yes, go to Step 2.
  • If no, go to Step 3.

  2. Increase the power consumption to make it reach the specified upper limit. Then, check whether the alarm can be cleared.

  • If the alarm is cleared, go to Step 5.
  • If the alarm persists, go to Step 3.

  3. Insert more PMs and make them work. Then, check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 5.
  • If the alarm persists, go to Step 4.

  4. Collect trap, log, and configuration information, and contact technical support.

  5. End.

• Cause 131351: Power backplane cable is not stable

  1. Run the slave switchover command to switchover ,and wait for a period of time,check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 3.
  • If the alarm persists, go to Step 2.

  2. Contact technical support and check whether the power supply unit backplane cable is securely inserted.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 3.

  3. Collect trap, log, and configuration information, and contact technical support.

  4. End.

• Cause 131352: Fan backplane cable of LPU area is not stable

  1. Remove and then insert the faulty fan located in the LPU area.When the fan is registered, check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 2.

  2. Contact technical support personnel. and check whether the LPU area cable for the fan backplane is securely inserted.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 3.

  3. Collect trap, log, and configuration information, and contact technical support.

  4. End.

• Cause 131353: Fan backplane cable of SFU area is not stable

  If this alarm occurs, the fans in the SFU area cannot work properly.

  1. Remove and then insert the faulty fan located in the SFU area.When the fan is registered, check whether the alarm is cleared.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 2.

  2. Contact technical support personnel. and check whether the SFU area cable for the fan backplane is securely inserted.

  • If the alarm is cleared, go to Step 4.
  • If the alarm persists, go to Step 3.

  3. Collect trap, log, and configuration information, and contact technical support.

  4. End.

• Cause 131354: SFU is failed,the number of the registered SFU is less than default number in chassis.

  1. In the system view, run the display least sfuboard command to check the minimum number of configurations on the SFU.

  2. If the number of registered SFUs on the device is less than the minimum number of SFUs, insert the missing SFUs.

  3. Collect trap, log, and configuration information, and contact technical support.

  4. End.

• Cause 131355: The backplane ID of chassis failed to be checked.

  1. If an installed board has no services on it, check whether the board is properly installed, if pins have bent, and if the board connectors become faulty.

  2. If the board is not securely installed, install it securely.

  3. If the pins on the backplane have bent, do not install a new board into the improper slot, go to Step 6.

  4. If only the board connectors are found to be faulty, replace the board.

  5. If services on the board are normal, go to Step 6.

  6. Collect trap, log, and configuration information, and contact technical support.

  7. End.

• Cause 131357: After you configure the time in which a non-security software package can still be used, an alarm is reported every hour in this time, informing you of the remaining time. After the time expires, no non-security software package can be used.

  This trap message is informational only, and no action is required.

• Cause 131359: IPUs with different forwarding capabilities were inserted on the device.

  1. Replace the existing standby main control board with the one having the same rate as the active main control board. After the new standby main control board is registered, check whether the alarm is cleared.

  • If yes, go to Step 3.
  • If no, go to Step 2.

  2. Collect trap, log, and configuration information, and contact technical support.

  3. End.

• Cause 131361: CXPs with different forwarding capabilities were inserted on the device.

  1. Replace the existing standby main control board with the one having the same rate as the active main control board. After the new standby main control board is registered, check whether the alarm is cleared.

  • If yes, go to Step 3.
  • If no, go to Step 2.

  2. Collect trap, log, and configuration information, and contact technical support.

  3. End.