DEVM/1/hwEntityReset_active: Physical entity reset. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=[BaseTrapProbableCause], BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntPhysicalContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=[ReasonDescription])
In VS mode, this log is supported only by the admin VS.
| Parameter Name | Parameter Meaning |
|---|---|
|
BaseTrapSeverity |
Indicates the physical index. |
|
BaseTrapProbableCause |
Possible reason. |
|
BaseTrapEventType |
Indicates the possible cause of the trap. |
|
EntityPhysicalIndex |
Indicates the trap type. |
|
EntPhysicalContainedIn |
Indicates the parent index. |
|
EntPhysicalName |
Indicates the name of the entity such as a chassis. |
|
RelativeResource |
This object may contain a key word to indicate the relative resource of an entity. |
|
ReasonDescription |
To describe the reason of trap in DisplayString style. |
Cause 1: A fault may occur on the ECM channel.
Cause 2: The CPU usage on the master MPU is too high.
Cause 1: A fault may occur on the ECM channel.
Cause 2: The CPU usage on the master MPU is too high.
Cause 1: A fault may occur on the ECM channel.
Cause 2: The CPU usage on the master MPU is too high.
Cause 1: A board reset command was run.
Cause 2: Software faults occurred.
Cause 1: A fault may occur on the ECM channel.
Cause 2: The CPU usage on the master MPU is too high.
1. The slave MPU can restore automatically. Check whether the reset MPU works normally.
2. Replace an MPU. After the registration, check whether the trap is recovered.
3. Collect the trap information, log information, and configuration of the router, and contact technical support personnel.
4. End.
1. Collect the trap information, log information, and configuration of the router, and contact technical support personnel.
2. End.
Cause 1: A fault may occur on the ECM channel.
Cause 2: The CPU usage on the master MPU is too high.
1. The SFU can be reset automatically. After the reset, run the display device command to check whether the SFU works normally.
2. Replace the SFU and then check whether the fault is rectified.
3. Collect the trap information, log information, and configuration of the router, and contact technical support personnel.
4. End.
Cause 1: A fault may occur on the ECM channel.
Cause 2: The CPU usage on the master MPU is too high.
1. The interface board can be reset automatically. After the reset, run the display device command to check whether the interface board works normally.
2. Replace the interface board and then check whether the fault is rectified.
3. Collect the trap information, log information, and configuration of the router, and contact technical support personnel.
4. End.
Cause 1: A board reset command was run.
Cause 2: Software faults occurred.
1.Check whether the board registers after a reset.
2. Replace the board and then check whether the alarm is cleared after the board registers.
3. Collect trap, log, and configuration information, and contact technical support personnel.
4. End.
1. The boards in the chassis will register automatically. Check if the board can work normally after registering automatically.
2. Pull out the unregistered boards and replace them with new boards. Then, check whether the trap is recovered.
3. Collect trap information, log information, and configuration information, and then contact technical support personnel.
4. End.