DEVM/1/hwEntityInvalid_active: Physical entity failed. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=[67971], BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=A communication failure occurred on the fan module.)
In VS mode, this log is supported only by the admin VS.
| Parameter Name | Parameter Meaning |
|---|---|
|
BaseTrapSeverity |
To describe the level of trap. |
|
ProbableCause |
To describe the probable cause of trap. |
|
BaseTrapEventType |
To describe the type of trap. |
|
EntityPhysicalIndex |
The index of the physical entity. |
|
EntContainedIn |
The value of entPhysicalIndex for the physical entity. |
|
EntPhysicalName |
The textual name of the physical entity. |
|
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. |
1. Run the reset slot command to reset the faulty fan module. Then, check whether the alarm is cleared. If the alarm persists after the fan module is registered, replace the faulty fan module. If the alarm is cleared after the fan module is reset and can be registered, a software error occurs.
2. Upgrade system software .Download the system software with the version later than the source version to the CF card of the active and standby main control boards. Run the startup system-software command to specify the system software to be loaded for the next startup. Then, restart the router.
3. Run the display device command and check whether the faulty board can be successfully registered.
4. Collect trap, log, and configuration information, and contact technical support.
5. End.