No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Alarm Handling

S9300, S9300E, and S9300X V200R010C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
BASETRAP_1. hwEntityBecomeMaster

BASETRAP_1. hwEntityBecomeMaster


BASETRAP/4/ENTITYBECOMEMASTER: OID [oid] Physical entity changed to the master state. (Index=[INTEGER], Severity=[INTEGER], ProbableCause=[INTEGER], EventType=[INTEGER], ContainedIn=[INTEGER], PhysicalName="[OCTET]", RelativeResource="[OCTET]", ReasonDescr="[OCTET]")

This alarm is generated when the entity is switched from standby state to active state.


Alarm ID Alarm Severity Alarm Type Warning processingErrorAlarm(4)


Name Meaning
[oid] Indicates the ID of the MIB object.
Index Indicates the index of the entity.
Severity Indicates the severity level of the alarm.
ProbableCause Indicates the possible causes of the alarm. The codes of the possible causes are as follows:

612: IANAITUPROBABLECAUSE_OUTOFSERVICE indicates that the MPU is abnormal and cannot provide services.

EventType Indicates the alarm type:
  • communicationsAlarm (2)
  • qualityOfServiceAlarm (3)
  • processingErrorAlarm (4)
  • equipmentAlarm (5)
  • environmentalAlarm (6)

This alarm is an alarm of the processingErrorAlarm type, that is, the alarm on processing errors.

ContainedIn Indicates the parent index of the entity.
PhysicalName Indicates the physical name of the entity.
RelativeResource Indicates the name of a component that is associated with the alarm.
ReasonDescription Indicates the description of causes of the alarm.

Impact on the System


Possible Causes

Cause 1

The operator performs active/standby switchover manually.

Cause 2

Exceptions occur on the original active MPU.


  1. When the alarm is generated, the active MPU is reset. After about three minutes, run the display device command in the user view to locate the causes of the active/standby switchover according to the slot ID of the MPU in the alarm.

    • If the standby MPU can be registered successfully after the switchover, the switchover is performed through command lines and no action is required.
    • If the standby MPU fails to be registered, switchover may be caused by the active MPU error or abnormal resetting. Go to Step 2.

  2. Replace the active MPU.
  3. Check whether the errors are rectified.

    If the following conditions are met, it indicates that the fault is rectified:

    • The alarm is not displayed on the NMS.
    • After you run the display trapbuffer command, this alarm is not displayed.
    • After you run the terminal monitor and terminal trapping commands, this alarm is not displayed.
    • Three or four minutes later after the switchover, run the display device command to check whether the standby MPU is registered successfully.
      • If so, the alarm handling ends.
      • If not, collect alarm information and configuration information, and then contact technical support personnel.

Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 191071

Downloads: 44

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next