HUAWEI-BASE-TRAP-MIB

MIB Reference — IPNetwork Monitor

All MIBsHUAWEI-BASE-TRAP-MIB

Organization: Huawei Technologies Co.,Ltd.

Last Updated: 2015-06-02

Category: Alarm and Event Management, Vendor: Huawei

Description:

Huawei base trap definitions MIB providing fundamental notification objects and trap variables common to all Huawei device platforms.

Imported Objects

From ENTITY-MIB

entPhysicalClassOBJECT-TYPE
entPhysicalContainedInOBJECT-TYPE
entPhysicalIndexOBJECT-TYPE
entPhysicalNameOBJECT-TYPE

From HUAWEI-FLASH-MAN-MIB

hwStorageNameOBJECT-TYPE
hwStorageSpaceOBJECT-TYPE
hwStorageSpaceFreeOBJECT-TYPE

From HUAWEI-MIB

hwDatacommOBJECT-IDENTITY

From IANA-ITU-ALARM-TC-MIB

IANAItuEventType
IANAItuProbableCause

From IF-MIB

ifDescrOBJECT-TYPE
ifIndexOBJECT-TYPE
ifNameOBJECT-TYPE

From ITU-ALARM-TC-MIB

ItuPerceivedSeverity

From RFC1213-MIB

ifAdminStatus
ifOperStatus

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString

What Is HUAWEI-BASE-TRAP-MIB?

HUAWEI-BASE-TRAP-MIB is a Huawei enterprise MIB that defines the fundamental, shared notification (trap) objects and variable bindings used as a common base across the wide range of Huawei DataCom device platforms (routers, switches, and related network equipment). Rather than exposing polled operational counters itself, it standardizes the structure of trap variables so that individual Huawei product/feature MIBs can raise consistent, well-formed SNMP notifications for faults and state changes. Its monitoring significance is therefore in fault/event reporting infrastructure: it underlies traps that report hardware issues (e.g., interface down, power/environmental faults) and software/process issues raised by other Huawei MIBs that import from this base. Because it is described as a base for DataCom, most Huawei-specific feature and hardware MIBs depend on it for common trap variable definitions rather than defining their own from scratch, so a HUAWEI-BASE-TRAP-MIB download from Huawei's support resources is typically required before compiling any dependent feature MIB. It is deployed across Huawei enterprise and carrier network devices as the foundational notification layer feeding an SNMP-based network management system.

IPNetwork Monitor allows you to monitor SNMP objects defined in HUAWEI-BASE-TRAP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

  • common trap/notification variable bindings

Supported Devices

  • Huawei CloudEngine S6730-H (2024) — enterprise/data-center LAN switch with hybrid-cloud support

Monitoring Examples

No sample objects were provided for this module, so specific object names cannot be cited here. In practice, a management station would not poll this MIB directly for values but would rely on other Huawei feature-specific MIBs to reference its base trap variable bindings when generating notifications, such as an interface-down or environmental-alarm trap. An operator troubleshooting a Huawei device would see this MIB's imported objects appear inside the varbind list of traps rather than as directly walkable status.

OIDs
OID symbolicOID numericTypeAccessDescription
hwBaseTrapMIB1.3.6.1.4.1.2011.5.25.129This is the base trap definition for DataCom.
hwBaseTrapObject1.3.6.1.4.1.2011.5.25.129.1
ITU hwBaseTrapSeverity1.3.6.1.4.1.2011.5.25.129.1.1ItuPerceivedSeverityaccessible-for-notifyTo describe the level of trap.
IAN hwBaseTrapProbableCause1.3.6.1.4.1.2011.5.25.129.1.2IANAItuProbableCauseaccessible-for-notifyTo describe the probable cause of trap.
IAN hwBaseTrapEventType1.3.6.1.4.1.2011.5.25.129.1.3IANAItuEventTypeaccessible-for-notifyTo describe the type of trap.
STR hwBaseTrapRelativeResource1.3.6.1.4.1.2011.5.25.129.1.4DisplayStringaccessible-for-notifyThis object may contain a key word to indicate the relative resource of an entity. Such as: hwEntityCommunicateError alarm may relate to a resource named 'IPC01'(A specified channel). So the trap may contain such a varbind in DisplayString style.
STR hwBaseTrapReasonDescr1.3.6.1.4.1.2011.5.25.129.1.5DisplayStringaccessible-for-notifyTo describe the reason of trap in DisplayString style.
hwBaseThresholdTable1.3.6.1.4.1.2011.5.25.129.1.6not-accessibleA table to config the threshold of each sensor.
hwBaseThresholdEntry1.3.6.1.4.1.2011.5.25.129.1.6.1not-accessibleThe entry of threshold table.
INT hwBaseThresholdType1.3.6.1.4.1.2011.5.25.129.1.6.1.1INTEGERnot-accessibleThe index to indicate the type of threshold for an entry.Such as temperature, humidity ,power supply......
I32 hwBaseThresholdIndex1.3.6.1.4.1.2011.5.25.129.1.6.1.2Integer32not-accessibleA subindex to identify each sensor on physical entity.
I32 hwBaseThresholdValue1.3.6.1.4.1.2011.5.25.129.1.6.1.3Integer32read-onlyThe current value that been measured.
INT hwBaseThresholdUnit1.3.6.1.4.1.2011.5.25.129.1.6.1.4INTEGERread-onlyThe unit for this threshold value. percentage(1) ---unit for humidity centigrade1(2) ---unit for temperature centigrade2(3) ---unit for hundredth of centigrade voltage1(4) ---unit for volt (V) voltage2(5) ---unit for thousandth of volt (mV) electric current: current1(6) ---unit for milliampere (mA) current2(7) ---unit for microampere (uA) power1(8) ---unit for dbm(decibels above one milliwatt in 600 ohms) power2(9) ---unit for hundredth of dbm(decibels above one milliwatt in 600 ohms)
I32 hwBaseThresholdLowCritical1.3.6.1.4.1.2011.5.25.129.1.6.1.5Integer32read-writeThe critical alarm threshold for falling alarm. It could be used for a more dangerous instance than hwBaseThresholdLowWarning. It should be equal to hwBaseThresholdLowWarning when don't support this threshold.
I32 hwBaseThresholdLowWarning1.3.6.1.4.1.2011.5.25.129.1.6.1.6Integer32read-writeThe normal warning threshold for falling alarm.
I32 hwBaseThresholdHighWarning1.3.6.1.4.1.2011.5.25.129.1.6.1.7Integer32read-writeThe normal warning threshold for rising alarm.
I32 hwBaseThresholdHighCritical1.3.6.1.4.1.2011.5.25.129.1.6.1.8Integer32read-writeThe critical alarm threshold for rising alarm. It could be used for a more dangerous instance than hwBaseThresholdHighWarning. It should be equal to hwBaseThresholdHighWarning when don't support this threshold.
hwBaseUsageTable1.3.6.1.4.1.2011.5.25.129.1.7not-accessibleA table to config the threshold for each storage device.
hwBaseUsageEntry1.3.6.1.4.1.2011.5.25.129.1.7.1not-accessibleThe entry for hwBaseUsageTable.
INT hwBaseUsageType1.3.6.1.4.1.2011.5.25.129.1.7.1.1INTEGERnot-accessibleThe index to indicate the type of threshold for an entry.Such as cpu,memory,flash and so on.
I32 hwBaseUsageIndex1.3.6.1.4.1.2011.5.25.129.1.7.1.2Integer32not-accessibleA subindex to identify each sensor on physical entity.
I32 hwBaseUsageValue1.3.6.1.4.1.2011.5.25.129.1.7.1.3Integer32read-onlyThe current value that been measured.
INT hwBaseUsageUnit1.3.6.1.4.1.2011.5.25.129.1.7.1.4INTEGERread-onlyThe unit for this threshold value. percentage(1) ---unit for cpu/men/disk/flash/cfCard
I32 hwBaseUsageThreshold1.3.6.1.4.1.2011.5.25.129.1.7.1.5Integer32read-writeThe threshold of usage for storage device.
INT hwFIBOverloadModule1.3.6.1.4.1.2011.5.25.129.1.8INTEGERaccessible-for-notifymodule is ipv4 or ipv6
INT hwBaseFlowDirectionType1.3.6.1.4.1.2011.5.25.129.1.9INTEGERaccessible-for-notifyThe direction of data flow is specified.
INT hwPowerDirection1.3.6.1.4.1.2011.5.25.129.1.10INTEGERaccessible-for-notifyThe direction of photoelectric power.
INT hwBaseTrapTrafficDir1.3.6.1.4.1.2011.5.25.129.1.11INTEGERaccessible-for-notifyThe traffic flows in or out of the port.
I32 hwEntityRatedPower1.3.6.1.4.1.2011.5.25.129.1.12Integer32accessible-for-notifyThe rated power of board.
I32 hwDevAvailablePower1.3.6.1.4.1.2011.5.25.129.1.13Integer32accessible-for-notifyAvailable power of the device.
I32 hwDeviceTotalPower1.3.6.1.4.1.2011.5.25.129.1.14Integer32accessible-for-notifyTotal power of the device.
I32 hwBaseTrapCurPortType1.3.6.1.4.1.2011.5.25.129.1.15Integer32accessible-for-notifyThe current type of port.
I32 hwBaseTrapLastPortType1.3.6.1.4.1.2011.5.25.129.1.16Integer32accessible-for-notifyThe last type of port.
OCT hwPortPhysicalDownReason1.3.6.1.4.1.2011.5.25.129.1.17OCTET STRINGaccessible-for-notifyAUAIS: The RX detects administrative(A) unit(U) alarm(A) indication(I) signal(S). B1TCA: The RX detects b1(B1) threshold(T) crossing(C) alarm(A). B2TCA: The RX detects b2(B2) threshold(T) crossing(C) alarm(A). B3TCA: The RX detects b3(B3) threshold(T) crossing(C) alarm(A). LAIS: The RX detects line(L) alarm(A) indication(I) signal(S). LCD: The RX detects loss(L) of code-group(C) delineation(D). LOF: The RX detects loss(L) of(O) frame(F). LOM: The RX detects loss(L) of(O) multiframe(M). LOP: The RX detects loss(L) of(O) pointer(M). LOS: The RX detects loss(L) of(O) signal(S). LRDI: The RX detects line(L) remote(R) defect(D) indication(I). LREI: The RX detects line(L) remote(R) error(D) indication(I). OOF: The RX detects out(O) of(O) frame(F). PAIS: The RX detects path(P) alarm(A) indication(I) signal(S). PPLM: The RX detects path(P) payload(P) label(L) mismatch(M). PRDI: The RX detects path(P) remote(R) defect(D) indication(I). PREI: The RX detects path(P) remote(R) error(E) indication(I). PUNEQ: The RX detects path(P) unequipped(UNEQ). RDOOL: The RX detects receive(R) data(D) out(O) of(O) lock(L). RROOL: The RX detects receive(R) reference(R) out(O) of(O) lock(L). SD: The RX detects signal(S) degrade(D). SF: The RX detects signal(S) fail(F). TROOL: The TX detects transmit(T) reference(R) out(O) of(O) lock(L). WLINK: The RX detects pcs link has failed (wis mode). TRANSCEIVER_OFFLINE: The transceiver is not in position. TRANSCEIVER_FAIL: A hardware failure occurs when accessing the transceiver. TRANSCEIVER_MISMATCH: The transceiver does not match the port-mode. TRANSCEIVER_UNKNOWN: The transceiver is unknown type. PMA_LOS: The PMA(physical medium attachment) detects loss of signal. PMA_UNLOCK: The PMA(physical medium attachment) detects receive data out of lock. PCS_HIGHBER: The PCS(physical coding sublayer) enter High-BER status. PCS_UNLOCK: The PCS(physical coding sublayer) detects receive data out of lock. LOCAL_FAULT: The RX detects Local Fault signal. REMOTE_FAULT: The RX detects Remote Fault signal. NEGOTIATION_FAIL: Auto-negotiation is not successful. SOFT_FORCE_DOWN: The interface was DOWN triggered by a protocol module or was administratively shut down.
hwBaseTraps1.3.6.1.4.1.2011.5.25.129.2
hwEntityTrap1.3.6.1.4.1.2011.5.25.129.2.1
NTF hwEntityRemove1.3.6.1.4.1.2011.5.25.129.2.1.1Entity has been removed.
NTF hwEntityInsert1.3.6.1.4.1.2011.5.25.129.2.1.2Entity has been inserted.
NTF hwEntityUnstable1.3.6.1.4.1.2011.5.25.129.2.1.3Entity has been inserted but position unstable.
NTF hwEntityUnstableResume1.3.6.1.4.1.2011.5.25.129.2.1.4Resume from entity position unstable situation.
NTF hwEntityReset1.3.6.1.4.1.2011.5.25.129.2.1.5Entity will be reseted.
NTF hwEntityResetDone1.3.6.1.4.1.2011.5.25.129.2.1.6Entity has been reseted and in good health now.
NTF hwEntityCommunicateError1.3.6.1.4.1.2011.5.25.129.2.1.7Communication error has been detected. Include all kinds of communication error between boards.
NTF hwEntityCommunicateResume1.3.6.1.4.1.2011.5.25.129.2.1.8Resume from communication error situation.
NTF hwEntityInvalid1.3.6.1.4.1.2011.5.25.129.2.1.9Entity is invalid for some reason.
NTF hwEntityResume1.3.6.1.4.1.2011.5.25.129.2.1.10Entity reusme from invalid situation.
NTF hwEntityLeaveMaster1.3.6.1.4.1.2011.5.25.129.2.1.11Redundant entity leave master role.
NTF hwEntityBecomeMaster1.3.6.1.4.1.2011.5.25.129.2.1.12Redundant entity become master role.
NTF hwEntityOffline1.3.6.1.4.1.2011.5.25.129.2.1.13Entity change to OFFLINE status.
NTF hwEntityOnline1.3.6.1.4.1.2011.5.25.129.2.1.14Entity change to ONLINE status.
NTF hwEntityCheckFail1.3.6.1.4.1.2011.5.25.129.2.1.15Failure of self-check occurs to the board
NTF hwEntityCheckResume1.3.6.1.4.1.2011.5.25.129.2.1.16The status is recovered from the failure of board self-check
NTF hwEntityRegFail1.3.6.1.4.1.2011.5.25.129.2.1.17Entity fail in registration.
NTF hwEntityRegSuccess1.3.6.1.4.1.2011.5.25.129.2.1.18Entity success in registration.
NTF hwEntityDyingGasp1.3.6.1.4.1.2011.5.25.129.2.1.19Dying gasp event is occurred.
hwEnvironmentTrap1.3.6.1.4.1.2011.5.25.129.2.2
NTF hwTempRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.2.1Temperature rise over HIGH threshold.
NTF hwTempRisingResume1.3.6.1.4.1.2011.5.25.129.2.2.2Temperature back to normal level.
NTF hwTempFallingAlarm1.3.6.1.4.1.2011.5.25.129.2.2.3Temperature fall below LOW threshold.
NTF hwTempFallingResume1.3.6.1.4.1.2011.5.25.129.2.2.4Temperature back to normal level.
NTF hwHumidityRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.2.5Humidity rise over HIGH threshold.
NTF hwHumidityRisingResume1.3.6.1.4.1.2011.5.25.129.2.2.6Humidity back to normal level.
NTF hwHumidityFallingAlarm1.3.6.1.4.1.2011.5.25.129.2.2.7Humidity fall below LOW threshold.
NTF hwHumidityFallingResume1.3.6.1.4.1.2011.5.25.129.2.2.8Humidity back to normal level.
NTF hwVoltRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.2.9Voltage of power rise over HIGH threshold.
NTF hwVoltRisingResume1.3.6.1.4.1.2011.5.25.129.2.2.10Voltage back to normal level.
NTF hwVoltFallingAlarm1.3.6.1.4.1.2011.5.25.129.2.2.11Voltage of power fall below LOW threshold.
NTF hwVoltFallingResume1.3.6.1.4.1.2011.5.25.129.2.2.12Voltage back to normal level.
NTF hwCurrentRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.2.13Current rise over HIGH threshold.
NTF hwCurrentRisingResume1.3.6.1.4.1.2011.5.25.129.2.2.14Current back to normal level.
NTF hwCurrentFallingAlarm1.3.6.1.4.1.2011.5.25.129.2.2.15Current fall below LOW threshold.
NTF hwCurrentFallingResume1.3.6.1.4.1.2011.5.25.129.2.2.16Current back to normal level.
NTF hwPowerRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.2.17Photoelectric power rise over HIGH threshold.
NTF hwPowerRisingResume1.3.6.1.4.1.2011.5.25.129.2.2.18Photoelectric power back to normal level.
NTF hwPowerFallingAlarm1.3.6.1.4.1.2011.5.25.129.2.2.19Photoelectric power fall below LOW threshold.
NTF hwPowerFallingResume1.3.6.1.4.1.2011.5.25.129.2.2.20Photoelectric power back to normal level.
NTF hwPowerInsufficiencyAlarm1.3.6.1.4.1.2011.5.25.129.2.2.21The available power of device is not enough for the board.
NTF hwPowerInsufficiencyResume1.3.6.1.4.1.2011.5.25.129.2.2.22The available power of device becomes sufficient for the board.
NTF hwAcuSoftwareUpgradeFailure1.3.6.1.4.1.2011.5.25.129.2.2.23ACU current startup system software and next startup system software are difference.
hwPowerTrap1.3.6.1.4.1.2011.5.25.129.2.3
NTF hwPowerOff1.3.6.1.4.1.2011.5.25.129.2.3.1One of the power is shutting down.
NTF hwPowerOn1.3.6.1.4.1.2011.5.25.129.2.3.2One of the power is starting up.
NTF hwPowerMixed1.3.6.1.4.1.2011.5.25.129.2.3.3The power is not of the same type!
NTF hwPowerMixedResume1.3.6.1.4.1.2011.5.25.129.2.3.4The power is changed to the same type!
hwCPUTrap1.3.6.1.4.1.2011.5.25.129.2.4
NTF hwCPUUtilizationRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.4.1CPU utilization exceed threshold.
NTF hwCPUUtilizationResume1.3.6.1.4.1.2011.5.25.129.2.4.2CPU utilization back to normal level.
hwPortTrap1.3.6.1.4.1.2011.5.25.129.2.5
NTF hwPortPhysicalDown1.3.6.1.4.1.2011.5.25.129.2.5.1One of the port physical connect down.
NTF hwPortPhysicalUp1.3.6.1.4.1.2011.5.25.129.2.5.2One of the port physical connect up.
NTF hwPortPhysicalNoTrafficAlarm1.3.6.1.4.1.2011.5.25.129.2.5.3One of the port has none traffic.
NTF hwPortPhysicalNoTrafficClear1.3.6.1.4.1.2011.5.25.129.2.5.4One of the port traffic resume.
NTF hwPortPhysicalTrafficRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.5.5One of the port traffic rise over threshold.
NTF hwPortPhysicalTrafficClear1.3.6.1.4.1.2011.5.25.129.2.5.6One of the port traffic resume to normal level.
NTF hwPortPhysicalCrcErrorRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.5.7One of the port CRC error rise over threshold.
NTF hwPortPhysicalCrcErrorClear1.3.6.1.4.1.2011.5.25.129.2.5.8One of the port CRC error resume to normal level.
NTF hwPortPhysicalEthBroadcastRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.5.9One of the Ethernet port broadcast rise over threshold.
NTF hwPortPhysicalEthBroadcastClear1.3.6.1.4.1.2011.5.25.129.2.5.10One of the Ethernet port broadcast resume to normal level.
NTF hwPortPhysicalEthHalfDuplexAlarm1.3.6.1.4.1.2011.5.25.129.2.5.11One of the Ethernet port works on the half-duplex mode.
NTF hwPortPhysicalEthFullDuplexClear1.3.6.1.4.1.2011.5.25.129.2.5.12One of the Ethernet port works on the full-duplex mode.
NTF hwPortPhysicalPortTypeChange1.3.6.1.4.1.2011.5.25.129.2.5.13One of the port type changed.
NTF hwPortPhysicalAutoNegotiateFail1.3.6.1.4.1.2011.5.25.129.2.5.14One of the port auto-negotiation failed.
NTF hwPortPhysicalAutoNegotiateResume1.3.6.1.4.1.2011.5.25.129.2.5.15One of the port auto-negotiation resumed.
hwStorageTrap1.3.6.1.4.1.2011.5.25.129.2.6
NTF hwStorageUtilizationRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.6.1Storage device utilization rise over threshold.
NTF hwStorageUtilizationResume1.3.6.1.4.1.2011.5.25.129.2.6.2Storage utilization resume to normal level.
NTF hwVsDiskFullAlarm1.3.6.1.4.1.2011.5.25.129.2.6.3The disk usage exceeded the overload threadhold.
NTF hwVsDiskResume1.3.6.1.4.1.2011.5.25.129.2.6.4The disk usage fall below the clear threashold.
hwClockTrap1.3.6.1.4.1.2011.5.25.129.2.7
hwFanTrap1.3.6.1.4.1.2011.5.25.129.2.8
hwFibTrap1.3.6.1.4.1.2011.5.25.129.2.9
NTF hwFIBOverloadSuspend1.3.6.1.4.1.2011.5.25.129.2.9.1The board is suspended for IPv4/IPv6 FIB capability overload.
NTF hwFIBOverloadSusResume1.3.6.1.4.1.2011.5.25.129.2.9.2The board is recovered for FIB capability overload suspend.
NTF hwFIBOverloadForward1.3.6.1.4.1.2011.5.25.129.2.9.3The board is forwarding for IPv4/IPv6 FIB capability overload.
NTF hwFIBOverloadFwResume1.3.6.1.4.1.2011.5.25.129.2.9.4The board is recovered for IPv4/IPv6 FIB capability overload forward.
NTF hwFESInconsistencyForMemoryLack1.3.6.1.4.1.2011.5.25.129.2.9.5Because the memory usage of the interface board exceeds the upper threshold, the FES cannot add new entries. As a result, the entries of the interface board is inconsistent with those of the main board.
NTF hwFESInconsistencyForMemoryLackResume1.3.6.1.4.1.2011.5.25.129.2.9.6The memory usage of the interface board reduces to the lower threshold, and the FES can add entries. The entries of the interface board is consistent with those of the main board.
hwPppTrap1.3.6.1.4.1.2011.5.25.129.2.10
NTF hwPppLoopbackDetect1.3.6.1.4.1.2011.5.25.129.2.10.1The interface Loopback is detected.
NTF hwPppLoopbackDetResume1.3.6.1.4.1.2011.5.25.129.2.10.2The interface is recovered from Loopback.
hwFlowControlTrap1.3.6.1.4.1.2011.5.25.129.2.11
NTF hwFlowCongestion1.3.6.1.4.1.2011.5.25.129.2.11.1The object is in congested state and some of the frames are dropped.
NTF hwFlowCongestionResume1.3.6.1.4.1.2011.5.25.129.2.11.2Alarms of the congested object are cleared.
hwDeviceAbnormalTrap1.3.6.1.4.1.2011.5.25.129.2.12
NTF hwDeviceAbnormalRisingAlarm1.3.6.1.4.1.2011.5.25.129.2.12.1Device abnormal or pulled out.
hwResExhaustBfdTrap1.3.6.1.4.1.2011.5.25.129.2.13
NTF hwResExhaustBfdAlarm1.3.6.1.4.1.2011.5.25.129.2.13.1Failed to allocate resources for BFD because hardware resources were exhausted.
NTF hwResExhaustBfdResume1.3.6.1.4.1.2011.5.25.129.2.13.2BFD recovered from alarms of hardware resources exhausting.
hwResExhaustOamTrap1.3.6.1.4.1.2011.5.25.129.2.14
NTF hwResExhaustOamAlarm1.3.6.1.4.1.2011.5.25.129.2.14.1Failed to allocate resources for OAM because hardware resources were exhausted. MPLS OAM is short for Operation Administration and Maintenance by MPLS. It is used for connectivity verification of MPLS LSP.
NTF hwResExhaustOamResume1.3.6.1.4.1.2011.5.25.129.2.14.2OAM recovered from alarms of hardware resources exhausting. MPLS OAM is short for Operation Administration and Maintenance by MPLS. It is used for connectivity verification of MPLS LSP.
hwHdlcTrap1.3.6.1.4.1.2011.5.25.129.2.15
NTF hwHdlcLoopbackDetect1.3.6.1.4.1.2011.5.25.129.2.15.1The interface Loopback is detected.
NTF hwHdlcLoopbackDetResume1.3.6.1.4.1.2011.5.25.129.2.15.2The interface is recovered from Loopback.
hwAutoFtpTrap1.3.6.1.4.1.2011.5.25.129.2.16
NTF hwAutoFtpFailAlarm1.3.6.1.4.1.2011.5.25.129.2.16.1This object indicates the software failure in the automatic upgrade system.
hwBaseOpticalTrap1.3.6.1.4.1.2011.5.25.129.2.17
NTF hwOpticalPowerAbnormal1.3.6.1.4.1.2011.5.25.129.2.17.1Optical rxpower or txpower is exceed threshold value.
NTF hwOpticalPowerResume1.3.6.1.4.1.2011.5.25.129.2.17.2Optical power resume.
hwBaseTrapConformance1.3.6.1.4.1.2011.5.25.129.3
hwBaseTrapCompliances1.3.6.1.4.1.2011.5.25.129.3.1
hwBaseTrapCompliance1.3.6.1.4.1.2011.5.25.129.3.1.1Compliance statement for agents that provide full support for hwBaseTrapMIB.
hwBaseTrapGroups1.3.6.1.4.1.2011.5.25.129.3.2
hwBaseObjectGroup1.3.6.1.4.1.2011.5.25.129.3.2.1Group for base trap objects.
hwBaseTrapGroup1.3.6.1.4.1.2011.5.25.129.3.2.2Group for all base traps.

RFC description

Huawei base trap and alarm definitions for network device notifications.

Start monitoring Huawei DataCom device (routers/switches, shared base trap definitions) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download HUAWEI-BASE-TRAP-MIB