The objects described here can be monitored with the IPHost Network Monitor.
You can start SNMP monitoring using free 30-day trial version of IPHost right now.
OID list for alarm status
- alarm Status
- alarmStatus 1.3.6.1.2.1.16.3.1.1.12 (defined in rfc1271)
The status of this alarm entry. - alarm Status
- alarmStatus 1.3.6.1.2.1.16.3.1.1.12 (defined in rfc1757)
The status of this alarm entry. - Compaq Me Alarm Status
- cpqMeAlarmStatus 1.3.6.1.4.1.232.10.2.2.2.1.11 (defined in CPQTHRSH)
The status of this alarm entry. Setting this object to the value invalid(4) has the effect of invalidating the corresponding entry. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries currently not in use. Proper interpretation of such entries requires examination of the relevant cpqMeAlarmStatus object. An existing instance of this object cannot be set to createRequest(2). This object may only be set to createRequest(2) when this instance is created. When this object is created, the agent may wish to create supplemental object instances to complete a conceptual row in this table. Immediately after completing the create operation, the agent must set this object to underCreation(3). Entries shall exist in the underCreation(3) state until the management station is finished configuring the entry and sets this object to valid(1) or aborts, setting this object to invalid(4). The agent will deny a request to modify an underCreation(3) entry to be that of createRequest(2) in order to lessen problems arising when multiple management stations may be trying to add an entry with the same index. If the agent determines that an entry has been in the underCreation(3) state for an abnormally long time, it may decide that the management station has crashed. If the agent makes this decision, it may set this object to invalid(4) to reclaim the entry. A prudent agent will understand that the management station may need to wait for human input and will allow for that possibility in its determination of this abnormally long period. If the agent has an entry which is valid(4) and it is unable to query the particular ASN.1 object specified, the agent should set the status to tempUnavailable(5). The agent should continue to query that ASN.1 object, and upon a successful query, the agent should set the status back to valid(4). - ADSL Line Alarm Configuration Profile Row Status
- adslLineAlarmConfProfileRowStatus 1.3.6.1.2.1.10.94.1.1.15.1.20 (defined in ADSL-LINE-MIB)
This object is used to create a new row or modify or delete an existing row in this table. A profile activated by setting this object to `active'. When `active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service, (by setting this object to `destroy' or `outOfService') it must be first unreferenced from all associated lines. If the implementator of this MIB has chosen not to implement `dynamic assignment' of profiles, this object's MIN-ACCESS is read-only and its value is always to be `active'. - ADSL2 L Alarm Configuration Template Row Status
- adsl2LAlarmConfTempRowStatus 1.3.6.1.2.1.10.238.1.5.3.1.1.7 (defined in ADSL2-LINE-MIB)
This object is used to create a new row or to modify or delete an existing row in this table. A template is activated by setting this object to 'active'. When 'active' is set, the system will validate the template. Before a template can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it must first be unreferenced from all associated lines. - ADSL2 Line Alarm Configuration Profile Row Status
- adsl2LineAlarmConfProfileRowStatus 1.3.6.1.2.1.10.238.1.5.3.2.1.14 (defined in ADSL2-LINE-MIB)
This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. When 'active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it must first be unreferenced from all associated templates. - ADSL2 Channel Alarm Configuration Profile Row Status
- adsl2ChAlarmConfProfileRowStatus 1.3.6.1.2.1.10.238.1.5.3.3.1.6 (defined in ADSL2-LINE-MIB)
This object is used to create a new row or to modify or delete an existing row in this table. A profile is activated by setting this object to 'active'. When 'active' is set, the system will validate the profile. Before a profile can be deleted or taken out of service (by setting this object to 'destroy' or 'notInService'), it must first be unreferenced from all associated templates. - Cisco 6400NSP Chassis Facility Alarm Status
- c64ChassisFacilityAlarmStatus 1.3.6.1.4.1.9.10.27.1.2.1.1 (defined in CISCO-6400-CHASSIS-MIB)
presence of critical/major/minor telco alarm: Bit 0, if set, indicates the presence of minor alarm Bit 1, if set, indicates the presence of major alarm Bit 2, if set, indicates the presence of critical alarm ::= { c64TelcoAlarmMgmt 1 } SYNTAX INTEGER { done(0), all(1), minor(2), major(3), critical(4) } MAX-ACCESS read-write STATUS current DESCRIPTION "This object is used to clear all, major or minor alarms indication and reset the alarm contacts. When the clear command is done the value of this object will be set to done(0). - Cisco 6400NSP Chassis Alarm ACO Status
- c64ChassisAlarmACOStatus 1.3.6.1.4.1.9.10.27.1.2.2.1.5 (defined in CISCO-6400-CHASSIS-MIB)
local alarm relay has been locally cut off for this particular alarm source. When this status is 'normal', the alarm in this entry has closed the local audible/visible alarm relay contacts. When this status is 'cutoff', the alarm in this entry initially closed the local relay contacts, but was suppressed by a local user pressing the external ACO button on the 6400 NSP.
