ASKEY-ENTITY-ALARM-MIB
The ASKEY-ENTITY-ALARM-MIB extends the standard ENTITY-MIB to define, monitor, and report hardware alarm states and entity status conditions for ASKEY networking devices. It provides specific managed objects for tracking critical system events, such as interface failures, power supply anomalies, and environmental thresholds, within ASKEY-managed infrastructure.
Imported Objects
Objects
48 total| Object Name |
|---|
askeyEntityAlarmMIBThe MIB module presents all managed objects extended to ENTITY-MIB, including alarm definition, alarm ,monitoring and entity status. MODULE-IDENTITY .1.3.6.1.4.1.3646.1300.2.12 |
askeyEntityAlarmMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.3646.1300.2.12.1 |
aeAlarmDefinition OBJECT IDENTIFIER .1.3.6.1.4.1.3646.1300.2.12.1.2 |
aeAlarmDefinitionTableThis table contains alarm definition. Each row defines a single alarm per vendor type, NOT an alarm list. SEQUENCE OF AeAlarmDefinitionEntry .1.3.6.1.4.1.3646.1300.2.12.1.2.1 |
aeAlarmDefinitionEntryInformation 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. AeAlarmDefinitionEntry .1.3.6.1.4.1.3646.1300.2.12.1.2.1.1 |
aeAlarmDefVendorTypeEnumA reference of the vendor-specific hardware type of the physical entity. AskeyVendorTypeEnum (ASKEY-DSLAM-MIB) .1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.1 |
aeAlarmDefTypeThe type of this alarm. It represents the position of bit in the AskeyAlarmList.ro AskeyAlarmBit .1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.2 |
aeAlarmDefNameThe abbreviation of an alarm type, e.g. LOS, LOF, AIS.ro AskeyAlarmName .1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.3 |
aeAlarmDefDescrA textual description of an alarm type. This object should contain the description and trouble-shooting of a alarm.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.4 |
aeAlarmDefSeverityThe severity of an alarm type.rw AskeyAlarmSeverity .1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.5 |
aeAlarmDefFilteredTo determine whether enable this alarm trap.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.6 |
aeAlarmDefSuppressedbyTo determine which alarms make this alarm suppressed.rw AskeyAlarmList .1.3.6.1.4.1.3646.1300.2.12.1.2.1.1.7 |
aeAlarmMonitoring OBJECT IDENTIFIER .1.3.6.1.4.1.3646.1300.2.12.1.3 |
aeAlarmTableThis table contains one row per physical entity. Information in this table are derived from AskeyAlarmList and aeAlarmDefinitionTable. SEQUENCE OF AeAlarmEntry .1.3.6.1.4.1.3646.1300.2.12.1.3.1 |
aeAlarmEntryThe status of an physical entity about active alarm includes highest-level alarm severity and service affection. AeAlarmEntry .1.3.6.1.4.1.3646.1300.2.12.1.3.1.1 |
aeAlarmPhysicalIndexPhysical entity index, encoded by shelf/slot/port, 2 decimal digits each field.ro Unsigned32 .1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.1 |
aeAlarmPlannedVendorTypeEnumAn enumeration of the planned vendor-specific hardware type of the physical entity.ro AskeyVendorTypeEnum (ASKEY-DSLAM-MIB) .1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.2 |
aeAlarmOnlineVendorTypeEnumAn enumeration of the online vendor-specific hardware type of the physical entity.ro AskeyVendorTypeEnum (ASKEY-DSLAM-MIB) .1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.3 |
aeAlarmListDefines 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.ro AskeyAlarmList .1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.4 |
aeAlarmLastChangeThe system time of the alarm vector is changed.ro Unsigned32 .1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.5 |
aeAlarmSeverityThe highest level of alarm severity of a physical entity.ro AskeyAlarmSeverity .1.3.6.1.4.1.3646.1300.2.12.1.3.1.1.6 |
aeAlarmHistory OBJECT IDENTIFIER .1.3.6.1.4.1.3646.1300.2.12.1.4 |
aeHistoryAlarmTableSizeThe size of the aeHistoryAlarmTable in rows. A value of 0 means no alarm logged in this table.ro INTEGER .1.3.6.1.4.1.3646.1300.2.12.1.4.1 |
aeHistoryAlarmTableThis 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. SEQUENCE OF AeHistoryAlarmEntry .1.3.6.1.4.1.3646.1300.2.12.1.4.2 |
aeHistoryAlarmEntryThe history of alarms recently ever existed in the system but removed. AeHistoryAlarmEntry .1.3.6.1.4.1.3646.1300.2.12.1.4.2.1 |
aeHistoryAlarmIndexThe 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. INTEGER .1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.1 |
aeHistoryAlarmPhysicalIndexThe index of physical entity for this alarm.ro Unsigned32 .1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.2 |
aeHistoryAlarmPlannedVendorTypeEnumAn enumeration of the planned vendor-specific hardware type of the physical entity.ro AskeyVendorTypeEnum (ASKEY-DSLAM-MIB) .1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.3 |
aeHistoryAlarmOnlineVendorTypeEnumAn enumeration of the online vendor-specific hardware type of the physical entity.ro AskeyVendorTypeEnum (ASKEY-DSLAM-MIB) .1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.4 |
aeHistoryAlarmTypeThe type of this alarm.ro AskeyAlarmBit .1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.5 |
aeHistoryAlarmTimeThe value of sysUpTime at the time this alarm asserted.ro Unsigned32 .1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.6 |
aeHistoryAlarmActionThe action of this alarm.ro AskeyAlarmAction .1.3.6.1.4.1.3646.1300.2.12.1.4.2.1.7 |
aeRelayInTableThis table contains one row per relay in entity. Administrator use this table to management the normal/abnormal status of relay-in alarm ports. SEQUENCE OF AeRelayInEntry .1.3.6.1.4.1.3646.1300.2.12.1.5 |
aeRelayInEntryThe configuration and status of an physical entity about alarm relay-in ports. AeRelayInEntry .1.3.6.1.4.1.3646.1300.2.12.1.5.1 |
aeRelayInPhysicalIndexPhysical entity index, encoded by shelf/slot/port, 2 decimal digits each field.ro Unsigned32 .1.3.6.1.4.1.3646.1300.2.12.1.5.1.1 |
aeRelayInNameUser defined name for this relay-in port.rw DisplayString .1.3.6.1.4.1.3646.1300.2.12.1.5.1.2 |
aeRelayInNormalStatusUser defined status for this relay-in port.rw Enumeration .1.3.6.1.4.1.3646.1300.2.12.1.5.1.3 |
aeRelayInCurrentStatusCurrent status for this relay-in port.ro Enumeration .1.3.6.1.4.1.3646.1300.2.12.1.5.1.4 |
askeyEntityAlarmMIBTraps OBJECT IDENTIFIER .1.3.6.1.4.1.3646.1300.2.12.2 |
askeyEntityMIBTrapPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.3646.1300.2.12.2.0 |
askeyEntityAlarmTrapAn 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. NOTIFICATION-TYPE .1.3.6.1.4.1.3646.1300.2.12.2.0.1 |
askeyEntityAlarmConformance OBJECT IDENTIFIER .1.3.6.1.4.1.3646.1300.2.12.3 |
askeyEntityAlarmCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.3646.1300.2.12.3.1 |
askeyEntityAlarmComplianceThe compliance statement for SNMP entities which implement the Askey EntityAlarm MIB. Unknown .1.3.6.1.4.1.3646.1300.2.12.3.1.1 |
askeyEntityAlarmGroups OBJECT IDENTIFIER .1.3.6.1.4.1.3646.1300.2.12.3.2 |
askeyEntityAlarmDefinitionGroupThe collection of objects which are used to represent definition of alarms, for which a single agent provides management information. Unknown .1.3.6.1.4.1.3646.1300.2.12.3.2.2 |
askeyEntityAlarmMonitoringGroupThe collection of objects which are used to represent monitoring of alarm status, for which a single agent provides management information. Unknown .1.3.6.1.4.1.3646.1300.2.12.3.2.3 |
askeyEntityAlarmNotificationsGroupThe collection of notifications used to indicate Entity MIB data consistency and general status information. Unknown .1.3.6.1.4.1.3646.1300.2.12.3.2.4 |
More MIBs from ASKEY
Browse all ASKEYMIBs →The ASKEY-SYSTEM-MIB provides SNMP management interfaces for ASKEY ADSL modems and routers, enabling the monitoring of DSL line parameters such as attenuation, signal-to-noise ratio, and interface status. It facilitates the collection of ADSL-specific performance counters and error statistics required for troubleshooting broadband connectivity issues on vendor hardware.
The ASKEY-ADSL-MIB module enables monitoring and management of ASKEY vendor ADSL modems and DSLAMs by exposing interface statistics, line status, and physical layer parameters via SNMP. It provides specific counters for DSL synchronization states, error rates, and data throughput to facilitate troubleshooting of broadband access links.
The ASKEY-HARDWARE-INFORMATION-MIB enables SNMP-based monitoring of ASKEY network equipment by exposing operational status and telemetry for network cards, line cards, and fan modules. This module facilitates hardware health assessment and fault detection through standardized access to component-level inventory and state data.
The ASKEY-MCAST-MIB module enables monitoring and configuration of multicast profile parameters on ASKEY network devices, specifically tracking session states, group membership data, and multicast forwarding statistics. This MIB facilitates the management of IP multicast services by exposing OID-based metrics for profile definitions and operational status within the device's multicast routing and switching infrastructure.
The ASKEY-DSLAM-VC-VLAN-MIB enables monitoring and configuration of Virtual Circuit (VC) to Virtual LAN (VLAN) mapping tables on ASKEY DSL Access Multiplexer (DSLAM) hardware via SNMP. It exposes managed objects for tracking the binding relationships between ATM/PPPoE virtual circuits and their corresponding Ethernet VLAN identifiers to ensure proper traffic segregation and service delivery.
The ASKEY-DSLAM-INTERNET-GROUP-MANAGEMENT-PROTOCOL-PROXY-MIB configures and monitors IGMP proxy states and multicast group membership tables on ASKEY DSLAM hardware. It exposes specific metrics for multicast session management, including active group counts, interface bindings, and proxy forwarding status to ensure efficient bandwidth utilization in IPTV and multicast service deployments.