How to check the reset causes of an interface card


Run the display reset-reason command to check the reset cause of the interface card installed in a slot, determining whether the interface card reset proactively or passively.
If the following message is displayed: Reason: A link fault fails to be rectified (which indicates a link fault), the interface card reset proactively. Otherwise, the interface card reset passively.

Other related questions:
How can I check the reason that a board is reset
Run the display reset-reason command to check whether a board is reset actively or passively.
  • If the message "Reason: A link fault fails to be rectified." is displayed, the board is actively reset.
  • If the preceding message is not displayed, the board is passively reset.

How to check the card reset cause on CE series switches
To check the reason of a card reset, run the display device board reset slot-id command. The following is an example:
<HUAWEI> system-view
[~HUAWEI] diagnose
[~HUAWEI-diagnose] display device board reset 1

If fan card of metro1000 support hot reset .
Fan card of metr 1000 support to hot reset

How to check the 4E1 interface card of the Huawei ViewPoint 9000 series endpoint
How to check the 4E1 interface card: 4E1 site loopback test method: A line loopback test is being performed. Both endpoints and MCUs support loopback upon power outage. 1. Line loopback: Connect to the loopback connector or line. Connect to another endpoint or MCU in power-off state. After the loopback, view the indicator status of the endpoint. In normal conditions, the yellow indicator of the loopback port is on and the green indicator is off. 2. Call loopback: 4E1 does not support call loopback. It is recommended the test be performed in simple scenarios, for example, point-to-point calls between endpoints. After lines are connected, view the endpoint status. In normal conditions, the green and yellow indicators are on. The line is in properly connected state. The local and remote frame synchronization is normal. 4E1 calls can be properly placed. There are a maximum of four lines. Connection status: After software synchronization, the connection status is normal. Otherwise, the connection status is abnormal. Type: The system automatically detects the board type after being started. The CRC bit error rate and bit error count are periodically calculated during 4E1 line status detection. Local and remote frame synchronization: The GL.IMXSS records the local and remote synchronization status after the line sequence is bound.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top