Home/Catalog/OPTIX-SONET-ALM-MIB

OPTIX-SONET-ALM-MIB

AI MIB Summary

The OPTIX-SONET-ALM-MIB monitors optical transport network alarms and performance degradation events on Huawei OptiX SONET/SDH transmission equipment. It provides real-time visibility into critical SONET-specific fault indicators, including signal loss, frame alignment errors, and bit error rate thresholds.

Description.
Main OID:
optixSonetAlarm.1.3.6.1.4.1.2011.2.25.3.20.10
47
Objects
Active
Status
5
Dependencies

Imported Objects

Objects

47 total
Object Name
optixSonetAlarmDescription.
MODULE-IDENTITY
.1.3.6.1.4.1.2011.2.25.3.20.10
almData
OBJECT IDENTIFIER
.1.3.6.1.4.1.2011.2.25.3.20.10.10
almDataTableAlarm data table
SEQUENCE OF AlmDataEntry
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10
almDataEntryAlarm data table
AlmDataEntry
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1
almDataMOD2Signal mode.ro
MOD2Type (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.1
almDataSlotSlot number. This will indicate what is the slot of the object which raised this alarm. If not relevant to the alarm, will be zero.ro
Unsigned32
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.2
almDataPortPort Number. This will indicate what is the Port of the object which raised this alarm. If not relevant to the alarm, will be zero.ro
Unsigned32
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.3
almDataPathPath number. This will indicate what is the Path of the object which raised this alarm. If not relevant to the alarm, will be zero.ro
Unsigned32
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.4
almDataVTVT path number. This will indicate what is the VT path of the object which raised this alarm. If not relevant to the alarm, will be zero.ro
Unsigned32
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.5
almDataNtfcnCdeThe notification code of the retrieved alarm. Only CR|MJ|MN will be represented here.ro
AlmDataNtfcnCdeType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.6
almDataNameAlarm name.ro
AlarmEventType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.7
almDataSrvEffThe effect on service caused by the alarm condition. Only NSA(Nonservice-effecting)|SA(Service-effecting) will be represented here.ro
AlmDataSrvEffType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.8
almDataLocationAlarm location. Only NEND(Near end)|FEND(Far end)|ALL will be represented here.ro
LocationType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.9
almDataDirectionAlarm direction. Only RCV(Receive direction)|TRMT(Transmit direction)|ALL will be represented here.ro
DirectionType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.10
almDataDateTimeAlarm date and time.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.11
almDataDescText message.ro
OCTET STRING
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.12
almDataAiddetSupplementary equipment identification.ro
Unsigned32
.1.3.6.1.4.1.2011.2.25.3.20.10.10.10.1.13
condDataTableMOD2 condition table.
SEQUENCE OF CondDataEntry
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20
condDataEntryMOD2 condition table.
CondDataEntry
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1
condDataMOD2Signal mode.ro
MOD2Type (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.1
condDataSlotSlot number. This will indicate what is the slot of the object which raised this alarm. If not relevant to the alarm, will be zero.ro
Unsigned32
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.2
condDataPortPort number. This will indicate what is the Port of the object which raised this alarm. If not relevant to the alarm, will be zero.ro
Unsigned32
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.3
condDataPathPath number.ro
Unsigned32
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.4
condDataVTVT path number. This will indicate what is the VT path of the object which raised this alarm. If not relevant to the alarm, will be zero.ro
Unsigned32
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.5
condDataNameCondition name.ro
AlarmEventType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.6
condDataLocationAlarm location. Only NEND(Near end)|FEND(Far end)|ALL will be represented here.ro
LocationType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.7
condDataDirectionAlarm direction. Only RCV(Receive direction)|TRMT(Transmit direction)|ALL will be represented here.ro
DirectionType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.8
condDataNtfcnCdeThe notification code of the retrieved alarm. Only NA|NR will be represented here.ro
AlmDataNtfcnCdeType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.9
condDataSrvEffThe effect on service caused by the alarm condition. Only NSA(Nonservice-effecting)|SA(Service-effecting) will be represented here.ro
AlmDataSrvEffType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.10
condDataDateTimeDate and time when the triggering event occurred.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.11
condDataDescText message.ro
OCTET STRING
.1.3.6.1.4.1.2011.2.25.3.20.10.10.20.1.12
almEnvDataTableenvironment alarm table
SEQUENCE OF AlmEnvDataEntry
.1.3.6.1.4.1.2011.2.25.3.20.10.10.30
almEnvDataEntryenvironment alarm table
AlmEnvDataEntry
.1.3.6.1.4.1.2011.2.25.3.20.10.10.30.1
almEnvDataAidAID of the input switch for environment monitoring.ro
Unsigned32
.1.3.6.1.4.1.2011.2.25.3.20.10.10.30.1.1
almEnvDataNtfcnCdeThe notification code of the retrieved alarm. Only CR|MJ|MN|NA will be represented here.ro
AlmDataNtfcnCdeType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.30.1.2
almEnvDataNameCondition type.ro
AlarmEventType (OPTIX-SONET-TC-MIB)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.30.1.3
almEnvDataDateTimeDate and time when the triggering event occurred.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.2011.2.25.3.20.10.10.30.1.4
almEnvDataCondDescText message.ro
OCTET STRING
.1.3.6.1.4.1.2011.2.25.3.20.10.10.30.1.5
almSummary
OBJECT IDENTIFIER
.1.3.6.1.4.1.2011.2.25.3.20.10.11
almSummaryCriticalCritical alarm count.ro
INTEGER
.1.3.6.1.4.1.2011.2.25.3.20.10.11.10
almSummaryMajorMajor alarm count.ro
INTEGER
.1.3.6.1.4.1.2011.2.25.3.20.10.11.20
almSummaryMinorMinor alarm count.ro
INTEGER
.1.3.6.1.4.1.2011.2.25.3.20.10.11.30
optixSonetAlarmConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.2011.2.25.3.20.10.20
optixSonetAlarmGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.2011.2.25.3.20.10.20.1
optixSonetAlarmObjectGroupEnter the description of the created OBJECT-GROUP.
Unknown
.1.3.6.1.4.1.2011.2.25.3.20.10.20.1.1
optixSonetAlarmCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.2011.2.25.3.20.10.20.2
optixSonetAlarmBasicComplianceEnter the description of the created MODULE-COMPLIANCE.
Unknown
.1.3.6.1.4.1.2011.2.25.3.20.10.20.2.1

More MIBs from Huawei

Browse all HuaweiMIBs →
HUAWEI-MIB

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.

3074 objects→
HUAWEI-SERVER-IBMC-MIB

Standard SNMP MIB module defining data structures for HUAWEI-SERVER-IBMC-MIB.

2171 objects→
HUAWEI-XPON-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.

1553 objects→
H3C-ENTITY-VENDORTYPE-OID-MIB

SNMP MIB module

1462 objects→
HUAWEI-WLAN-CONFIGURATION-MIB

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.

1280 objects→
HUAWEI-XQoS-MIB

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.

1134 objects→