All MIBs › ASKEY-ENTITY-ALARM-MIB
Organization: Askey Computer Corp.
Last Updated: 2004-11-22
Category: Alarm and Event Management, DSL and Broadband, Vendor: Askey
Description:
Defines entity-level alarm notifications and fault conditions on Askey broadband equipment.
Imported Objects
From ASKEY-DSLAM-MIB
| AskeyVendorTypeEnum | |
| ipDslam | OBJECT-IDENTITY |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| AutonomousType | |
| DisplayString | |
| TEXTUAL-CONVENTION | |
| TruthValue |
What Is ASKEY-ENTITY-ALARM-MIB?
ASKEY-ENTITY-ALARM-MIB is a vendor-specific SNMP module from Askey Computer Corp, a manufacturer of broadband customer-premises equipment such as ONTs, ONUs, and residential/SMB gateways, extending the standard ENTITY-MIB with alarm-management capabilities. It exposes alarm definition data (type, name, description, severity, filtering, and suppression relationships) alongside an active alarm table that ties each raised alarm to a specific physical entity on the device. This makes it squarely a fault/status-monitoring MIB: it tracks hardware health events—active alarms against line cards, ports, power, or other physical components—by reporting alarm severity, whether an alarm is filtered, and whether it is currently suppressed by another correlated alarm, and tracing a specific ASKEY-ENTITY-ALARM-MIB OID from aeAlarmTable back to its aeAlarmDefinitionTable entry is typically the first step in interpreting a raised alarm. It builds directly on the IETF ENTITY-MIB's physical entity indexing to associate each alarm with a specific hardware component. It is typically deployed on Askey-branded broadband access devices (ONTs/ONUs, residential gateways) to feed alarm state into an upstream NMS via SNMP traps and polling.
IPNetwork Monitor allows you to monitor SNMP objects defined in ASKEY-ENTITY-ALARM-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
- active alarm list per physical entity
- alarm severity level
- alarm type/definition and description
- alarm filtering status
- alarm suppression relationships
Supported Devices
- Askey RTV7906VW — XGSPON tri-band Wi-Fi 7 fiber home gateway for ISP CPE deployments
- Askey RTL0310 — 5G NR CPE fixed wireless access gateway (Qualcomm Snapdragon X55/Dragonwing NPro 6)
Monitoring Examples
An NMS would poll aeAlarmTable/aeAlarmEntry and key on aeAlarmPhysicalIndex to see which active alarms are raised against a specific physical component, cross-referencing aeAlarmDefinitionTable (aeAlarmDefSeverity, aeAlarmDefDescr) to interpret severity and meaning. A rising count of critical-severity entries tied to a power or optical-related physical index would indicate a hardware fault requiring dispatch. The aeAlarmDefSuppressedby field lets an operator recognize when a lower-priority alarm is being masked by a correlated root-cause alarm, avoiding alert flooding.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| askeyEntityAlarmMIB | 1.3.6.1.4.1.3646.1300.2.12 | The MIB module presents all managed objects extended to ENTITY-MIB, including alarm definition, alarm ,monitoring and entity status. | ||
| askeyEntityAlarmMIBObjects | 1.3.6.1.4.1.3646.1300.2.12.1 | |||
| aeAlarmDefinition | 1.3.6.1.4.1.3646.1300.2.12.1.2 | |||
| aeAlarmDefinitionTable | 1.3.6.1.4.1.3646.1300.2.12.1.2.1 | not-accessible | This table contains alarm definition. Each row defines a single alarm per vendor type, NOT an alarm list. | |
| aeAlarmDefinitionEntry | 1.3.6.1.4.1.3646.1300.2.12.1.2.1.1 | not-accessible | Information about an alarm definition to help an NMS find the meaning of an alarm, and object (aeAlarmFiltered) to help an NMS stop monitoring a type of alarm. | |
| ASK aeAlarmDefVendorTypeEnum | 1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.1 | AskeyVendorTypeEnum | not-accessible | A reference of the vendor-specific hardware type of the physical entity. |
| ASK aeAlarmDefType | 1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.2 | AskeyAlarmBit | read-only | The type of this alarm. It represents the position of bit in the AskeyAlarmList. |
| ASK aeAlarmDefName | 1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.3 | AskeyAlarmName | read-only | The abbreviation of an alarm type, e.g. LOS, LOF, AIS. |
| STR aeAlarmDefDescr | 1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.4 | DisplayString | read-only | A textual description of an alarm type. This object should contain the description and trouble-shooting of a alarm. |
| ASK aeAlarmDefSeverity | 1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.5 | AskeyAlarmSeverity | read-write | The severity of an alarm type. |
| T/F aeAlarmDefFiltered | 1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.6 | TruthValue | read-write | To determine whether enable this alarm trap. |
| ASK aeAlarmDefSuppressedby | 1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.7 | AskeyAlarmList | read-write | To determine which alarms make this alarm suppressed. |
| aeAlarmMonitoring | 1.3.6.1.4.1.3646.1300.2.12.1.3 | |||
| aeAlarmTable | 1.3.6.1.4.1.3646.1300.2.12.1.3.1 | not-accessible | This table contains one row per physical entity. Information in this table are derived from AskeyAlarmList and aeAlarmDefinitionTable. | |
| aeAlarmEntry | 1.3.6.1.4.1.3646.1300.2.12.1.3.1.1 | not-accessible | The status of an physical entity about active alarm includes highest-level alarm severity and service affection. | |
| U32 aeAlarmPhysicalIndex | 1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.1 | Unsigned32 | read-only | Physical entity index, encoded by shelf/slot/port, 2 decimal digits each field. |
| ASK aeAlarmPlannedVendorTypeEnum | 1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.2 | AskeyVendorTypeEnum | read-only | An enumeration of the planned vendor-specific hardware type of the physical entity. |
| ASK aeAlarmOnlineVendorTypeEnum | 1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.3 | AskeyVendorTypeEnum | read-only | An enumeration of the online vendor-specific hardware type of the physical entity. |
| ASK aeAlarmList | 1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.4 | AskeyAlarmList | read-only | Defines the active alarms on physical entity. Alarm information is represented by AskeyAlarmList, A manager can use bitwise integer operation to retrieve what type of alarms are asserted. All the alarm types are defined in aeAlarmDefinitionTable. A bit value of '0' implies no such type of alarm and in contrast a bit value of '1' implies there is an such type of alarm asserted. All unused bits (or no alarm) are filled by 0. |
| U32 aeAlarmLastChange | 1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.5 | Unsigned32 | read-only | The system time of the alarm vector is changed. |
| ASK aeAlarmSeverity | 1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.6 | AskeyAlarmSeverity | read-only | The highest level of alarm severity of a physical entity. |
| aeAlarmHistory | 1.3.6.1.4.1.3646.1300.2.12.1.4 | |||
| INT aeHistoryAlarmTableSize | 1.3.6.1.4.1.3646.1300.2.12.1.4.1 | INTEGER | read-only | The size of the aeHistoryAlarmTable in rows. A value of 0 means no alarm logged in this table. |
| aeHistoryAlarmTable | 1.3.6.1.4.1.3646.1300.2.12.1.4.2 | not-accessible | This table contains all active alarms currently exist in the overall system. There is one row per active alarm of physical entity. When a manager misses those traps originated by a agent, it can also retrieve those events from this table. | |
| aeHistoryAlarmEntry | 1.3.6.1.4.1.3646.1300.2.12.1.4.2.1 | not-accessible | The history of alarms recently ever existed in the system but removed. | |
| INT aeHistoryAlarmIndex | 1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.1 | INTEGER | not-accessible | The index of this entry.The value of index will wrap back to 1 while it reaching 2^31-1. So a manager must notice this condition by checking aeHistoryAlarmTime. |
| U32 aeHistoryAlarmPhysicalIndex | 1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.2 | Unsigned32 | read-only | The index of physical entity for this alarm. |
| ASK aeHistoryAlarmPlannedVendorTypeEnum | 1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.3 | AskeyVendorTypeEnum | read-only | An enumeration of the planned vendor-specific hardware type of the physical entity. |
| ASK aeHistoryAlarmOnlineVendorTypeEnum | 1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.4 | AskeyVendorTypeEnum | read-only | An enumeration of the online vendor-specific hardware type of the physical entity. |
| ASK aeHistoryAlarmType | 1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.5 | AskeyAlarmBit | read-only | The type of this alarm. |
| U32 aeHistoryAlarmTime | 1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.6 | Unsigned32 | read-only | The value of sysUpTime at the time this alarm asserted. |
| ASK aeHistoryAlarmAction | 1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.7 | AskeyAlarmAction | read-only | The action of this alarm. |
| aeRelayInTable | 1.3.6.1.4.1.3646.1300.2.12.1.5 | not-accessible | This table contains one row per relay in entity. Administrator use this table to management the normal/abnormal status of relay-in alarm ports. | |
| aeRelayInEntry | 1.3.6.1.4.1.3646.1300.2.12.1.5.1 | not-accessible | The configuration and status of an physical entity about alarm relay-in ports. | |
| U32 aeRelayInPhysicalIndex | 1.3.6.1.4.1.3646.1300.2.12.1.5.1.1 | Unsigned32 | read-only | Physical entity index, encoded by shelf/slot/port, 2 decimal digits each field. |
| STR aeRelayInName | 1.3.6.1.4.1.3646.1300.2.12.1.5.1.2 | DisplayString | read-write | User defined name for this relay-in port. |
| INT aeRelayInNormalStatus | 1.3.6.1.4.1.3646.1300.2.12.1.5.1.3 | INTEGER | read-write | User defined status for this relay-in port. |
| INT aeRelayInCurrentStatus | 1.3.6.1.4.1.3646.1300.2.12.1.5.1.4 | INTEGER | read-only | Current status for this relay-in port. |
| askeyEntityAlarmMIBTraps | 1.3.6.1.4.1.3646.1300.2.12.2 | |||
| askeyEntityMIBTrapPrefix | 1.3.6.1.4.1.3646.1300.2.12.2.0 | |||
| NTF askeyEntityAlarmTrap | 1.3.6.1.4.1.3646.1300.2.12.2.0.1 | An askeyEntityAlarmClear trap is sent when a entity clears an alarm. It can be utilized by an NMS to trigger alarm definition table maintenance polls. An NMS should periodically check the items of aeHistoryAlarmTable to detect any missed askeyEntityAlarmClear trap events, e.g. due to throttling or transmission loss. | ||
| askeyEntityAlarmConformance | 1.3.6.1.4.1.3646.1300.2.12.3 | |||
| askeyEntityAlarmCompliances | 1.3.6.1.4.1.3646.1300.2.12.3.1 | |||
| askeyEntityAlarmCompliance | 1.3.6.1.4.1.3646.1300.2.12.3.1.1 | The compliance statement for SNMP entities which implement the Askey EntityAlarm MIB. | ||
| askeyEntityAlarmGroups | 1.3.6.1.4.1.3646.1300.2.12.3.2 | |||
| askeyEntityAlarmDefinitionGroup | 1.3.6.1.4.1.3646.1300.2.12.3.2.2 | The collection of objects which are used to represent definition of alarms, for which a single agent provides management information. | ||
| askeyEntityAlarmMonitoringGroup | 1.3.6.1.4.1.3646.1300.2.12.3.2.3 | The collection of objects which are used to represent monitoring of alarm status, for which a single agent provides management information. | ||
| askeyEntityAlarmNotificationsGroup | 1.3.6.1.4.1.3646.1300.2.12.3.2.4 | The collection of notifications used to indicate Entity MIB data consistency and general status information. |
RFC description
Extends ENTITY-MIB with vendor-private alarm monitoring, entity status, and alarm relay-in port configuration objects for Askey networking devices.
Start monitoring Askey RTV7906VW/RTL0310 fiber/5G CPE gateways 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.