OPTIX-SDH-ALM-MIB
The OPTIX-SDH-ALM-MIB monitors alarm states and fault conditions on Huawei Optix Synchronous Digital Hierarchy (SDH) transmission equipment, tracking specific SDH layer defects such as LOS, LOF, and AIS to facilitate rapid network fault isolation.
Imported Objects
Objects
47 total| Object Name |
|---|
optixAlarmThis module MIB describes the Optix Alarm. MODULE-IDENTITY .1.3.6.1.4.1.2011.2.25.3.10.30 |
almAttribute OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.25.3.10.30.10 |
almAutoReportTableAlarm auotmatic report status table. SEQUENCE OF AlmAutoReportEntry .1.3.6.1.4.1.2011.2.25.3.10.30.10.10 |
almAutoReportEntryAlarm auotmatic report status entry. AlmAutoReportEntry .1.3.6.1.4.1.2011.2.25.3.10.30.10.10.1 |
almAutoRepBidCard IDro Gauge32 .1.3.6.1.4.1.2011.2.25.3.10.30.10.10.1.1 |
almAutoRepEidAlarm IDro SdhAlarmEventType (OPTIX-SDH-TC-MIB) .1.3.6.1.4.1.2011.2.25.3.10.30.10.10.1.2 |
almAutoRepAlarm auotmatic report status.rw Enumeration .1.3.6.1.4.1.2011.2.25.3.10.30.10.10.1.3 |
almSeverityTableAlarm severity table. SEQUENCE OF AlmSeverityEntry .1.3.6.1.4.1.2011.2.25.3.10.30.10.20 |
almSeverityEntryAlarm severity table. AlmSeverityEntry .1.3.6.1.4.1.2011.2.25.3.10.30.10.20.1 |
almSeverityBidCard IDro Gauge32 .1.3.6.1.4.1.2011.2.25.3.10.30.10.20.1.1 |
almSeverityEidAlarm IDro SdhAlarmEventType (OPTIX-SDH-TC-MIB) .1.3.6.1.4.1.2011.2.25.3.10.30.10.20.1.2 |
almSeverityAlarm severity.rw Enumeration .1.3.6.1.4.1.2011.2.25.3.10.30.10.20.1.3 |
almMonStateTableAlarm monitor status table. SEQUENCE OF AlmMonStateEntry .1.3.6.1.4.1.2011.2.25.3.10.30.10.30 |
almMonStateEntryAlarm monitor status entry. AlmMonStateEntry .1.3.6.1.4.1.2011.2.25.3.10.30.10.30.1 |
almMonStateBidCard IDro Gauge32 .1.3.6.1.4.1.2011.2.25.3.10.30.10.30.1.1 |
almMonStateEidAlarm IDro SdhAlarmEventType (OPTIX-SDH-TC-MIB) .1.3.6.1.4.1.2011.2.25.3.10.30.10.30.1.2 |
almMonStatePortOptical port No.ro Gauge32 .1.3.6.1.4.1.2011.2.25.3.10.30.10.30.1.3 |
almMonStatePathPath No.ro Gauge32 .1.3.6.1.4.1.2011.2.25.3.10.30.10.30.1.4 |
almMonStateAlarm monitor status.rw Enumeration .1.3.6.1.4.1.2011.2.25.3.10.30.10.30.1.5 |
almData OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.25.3.10.30.20 |
almCurAlarmDataTableCurrent alarm table. SEQUENCE OF AlmCurAlarmDataEntry .1.3.6.1.4.1.2011.2.25.3.10.30.20.10 |
almCurAlarmDataEntryCurrent alarm table. AlmCurAlarmDataEntry .1.3.6.1.4.1.2011.2.25.3.10.30.20.10.1 |
almCurAlarmDataNIDNumber ID.ro Gauge32 .1.3.6.1.4.1.2011.2.25.3.10.30.20.10.1.1 |
almCurAlarmDataBidCard ID.ro Gauge32 .1.3.6.1.4.1.2011.2.25.3.10.30.20.10.1.2 |
almCurAlarmDataEidAlarm event ID.ro SdhAlarmEventType (OPTIX-SDH-TC-MIB) .1.3.6.1.4.1.2011.2.25.3.10.30.20.10.1.3 |
almCurAlarmDataSeverityAlarm severity.ro Enumeration .1.3.6.1.4.1.2011.2.25.3.10.30.20.10.1.4 |
almCurAlarmDataStateAlarm state.ro Enumeration .1.3.6.1.4.1.2011.2.25.3.10.30.20.10.1.5 |
almCurAlarmDataStartTimeDate and time when alarm declared,has following format: field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minute 0..59 6 7 second 0..60 (use 60 for leap-second) 7 8 deci-second 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.2011.2.25.3.10.30.20.10.1.6 |
almCurAlarmDataEndTimeDate and time when alarm cleared,has following format: field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.2011.2.25.3.10.30.20.10.1.7 |
almCurAlarmDataParaAdditional parameters,include optical port No,path No,etc.ro OCTET STRING .1.3.6.1.4.1.2011.2.25.3.10.30.20.10.1.8 |
almCurAlarmDataTableStatusIndicate whether this row has been deleted.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.2.25.3.10.30.20.10.1.9 |
almHisAlarmDataTableHistoric alarm table. SEQUENCE OF AlmHisAlarmDataEntry .1.3.6.1.4.1.2011.2.25.3.10.30.20.20 |
almHisAlarmDataEntryHistoric alarm Entry. AlmHisAlarmDataEntry .1.3.6.1.4.1.2011.2.25.3.10.30.20.20.1 |
almHisAlarmDataNIDNumber ID.ro Gauge32 .1.3.6.1.4.1.2011.2.25.3.10.30.20.20.1.1 |
almHisAlarmDataBidCard ID.ro Gauge32 .1.3.6.1.4.1.2011.2.25.3.10.30.20.20.1.2 |
almHisAlarmDataEidAlarm event ID.ro SdhAlarmEventType (OPTIX-SDH-TC-MIB) .1.3.6.1.4.1.2011.2.25.3.10.30.20.20.1.3 |
almHisAlarmDataSeverityAlarm severity.ro Enumeration .1.3.6.1.4.1.2011.2.25.3.10.30.20.20.1.4 |
almHisAlarmDataStateAlarm state.ro Enumeration .1.3.6.1.4.1.2011.2.25.3.10.30.20.20.1.5 |
almHisAlarmDataStartTimeDate and time when alarm declared,has following format: field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.2011.2.25.3.10.30.20.20.1.6 |
almHisAlarmDataEndTimeDate and time when alarm cleared,has following format: field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC 0..11ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.2011.2.25.3.10.30.20.20.1.7 |
almHisAlarmDataParaAdditional parameters,include optical port No,path No,etc.ro OCTET STRING .1.3.6.1.4.1.2011.2.25.3.10.30.20.20.1.8 |
almHisAlarmDataTableStatusIndicate whether this row has been deleted.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.2.25.3.10.30.20.20.1.9 |
optixAlarmConformance OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.25.3.10.30.50 |
optixAlarmGroups OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.25.3.10.30.50.1 |
currentObjectGroupEnter the description of the created OBJECT-GROUP. Unknown .1.3.6.1.4.1.2011.2.25.3.10.30.50.1.1 |
optixAlarmCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.2011.2.25.3.10.30.50.2 |
optixAlarmbasicComplianceEnter the description of the created MODULE-COMPLIANCE. Unknown .1.3.6.1.4.1.2011.2.25.3.10.30.50.2.1 |
More MIBs from Huawei
Browse all HuaweiMIBs →The HUAWEI-MIB module provides a unified namespace for monitoring and managing generic system resources, interface statistics, and hardware telemetry across Huawei network devices. It serves as the foundational OID repository for retrieving standard operational data, including CPU utilization, memory usage, interface counters, and device status, required for comprehensive network management via SNMP.
Standard SNMP MIB module defining data structures for HUAWEI-SERVER-IBMC-MIB.
The HUAWEI-XPON-MIB module enables Network Management Systems to monitor and configure GPON and EPON optical line terminals and optical network units, specifically tracking PON port status, optical power levels, bandwidth allocation, and subscriber session states.
SNMP MIB module
The HUAWEI-WLAN-CONFIGURATION-MIB facilitates the configuration and monitoring of Huawei Wireless LAN access point parameters, specifically managing AP port link profiles and broadcast suppression settings. This module enables administrators to enforce traffic control policies and optimize wireless network performance by adjusting switch profile associations and limiting broadcast traffic on specific ports.
The HUAWEI-XQoS-MIB enables configuration and real-time monitoring of Class Based QoS parameters on Huawei network devices, specifically tracking traffic classification rules, queue states, and policy enforcement metrics. This module facilitates granular control over bandwidth allocation and packet prioritization by exposing objects for policy definitions, interface queue depths, and dropped packet counters associated with QoS classes.