All MIBs › SCTE-HMS-PROPERTY-MIB › currentAlarmOID
currentAlarmOID
Module: SCTE-HMS-PROPERTY-MIB
OID (symbolic): SCTE-HMS-PROPERTY-MIB::currentAlarmOID
OID (numeric): 1.3.6.1.4.1.5591.1.1.2.1.1
Node type: OBJECT-TYPE
Type: OBJECT IDENTIFIER
Access: read-only
Description: This is the OID of the alarmed object whose current value makes an alarm active.
In the case of the alarmed analog object, the value of this object is equal to the value of the index parameterOID of the propertyTable.
In the case of the alarmed discrete object, the value of this object is equal to the value of the index discreteParameterOID of the discretePropertyTable.
Please note that in the case of the alarmed discrete object, the value of this object is not equal to the identity part of the OID of the instances in the corresponding row of the discretePropertyTable.
Example 1. Object commonInternalTemperature (HMS024).
If object commonInternalTemperature has a major alarm for a HIHI threshold value of 100 degrees Celsius defined in the propertyTable, and this alarm occurs then:
(1) 'currentAlarmOID.12.commonInternalTemperature.0' instance will have the value 'commonInternalTemperature.0';
(2) 'currentAlarmAlarmState.12.commonInternalTemperature.0' instance will have the value caasHIHI(2);
(3) 'currentAlarmAlarmValue.12.commonInternalTemperature.0' instance will have the value 100.
Notice the presence of 12 in the OIDs of the instances above. Number 12 is the length of the 'commonInternalTemperature.0' OID, which is '1.3.6.1.4.1.5591.1.3.1.13.0'.
Example 2. Object fnOpticalReceiverABSwitchState (HMS025).
If object 'fnOpticalReceiverABSwitchState.1', which is the first instance of A/B switch in a fiber node, has a major alarm for a value pathB(2) defined in the discretePropertyTable, and this alarm occurs then:
(1) 'currentAlarmOID.13.fnOpticalReceiverABSwitchState.1' instance will have the value 'fnOpticalReceiverABSwitchState.1';
(2) 'currentAlarmAlarmState.13.fnOpticalReceiverABSwitchState.1' instance will have the value caasDiscreteMajor(6);
(3) 'currentAlarmAlarmValue.13.fnOpticalReceiverABSwitchState.1' instance will have the value pathB(2).
Notice the presence of 13 in the OIDs of the instances above. Number 13 is the length of the 'fnOpticalReceiverABSwitchState.1' OID, which is '1.3.6.1.4.1.5591.1.5.13.1.4.1'.
Example 3. Object heCommonTemperature (HMS111).
If object 'commonInternalTemperature.1' has a major alarm for a HIHI threshold value of 60 degrees Celsius defined in the propertyTable, and this alarm occurs then:
(1) 'currentAlarmOID.18.heCommonTemperature.1' instance will have the value 'heCommonTemperature.1';
(2) 'currentAlarmAlarmState.18.heCommonTemperature.1' instance will have the value caasHIHI(2);
(3) 'currentAlarmAlarmValue.18.heCommonTemperature.1' instance will have the value 600.
Notice the presence of 18 in the OIDs of the instances above. Number 18 is the length of the 'heCommonTemperature.1' OID, which is '1.3.6.1.4.1.5591.1.11.2.1.1.1.1.1.1.2.1'.
Example 4. Object heOpTxLaserOutputStatus (HMS112).
If object 'heOpTxLaserOutputStatus.1.2', which is the second laser instance in the first instance of the headend optical transmitter, has a major alarm for a value off(1) defined in the discretePropertyTable, and this alarm occurs then:
(1) 'currentAlarmOID.18.heOpTxLaserOutputStatus.1.2' instance will have the value 'heOpTxLaserOutputStatus.1.2';
(2) 'currentAlarmAlarmState.18.heOpTxLaserOutputStatus.1.2' instance will have the value caasDiscreteMajor(6);
(3) 'currentAlarmAlarmValue.18.heOpTxLaserOutputStatus.1.2' instance will have the value off(1).
Notice the presence of 18 in the OIDs of the instances above. Number 18 is the length of the 'heOpTxLaserOutputStatus.2' OID, which is '1.3.6.1.4.1.5591.1.11.1.1.1.1.3.1.8.1.2'.
What is currentAlarmOID?
This read-only OBJECT IDENTIFIER, the first index of currentAlarmTable, identifies which monitored object currently has an active alarm, matching parameterOID for analog properties or discreteParameterOID for discrete ones. Because currentAlarmTable only lists properties presently in an alarm state, a manager can use GET-NEXT iteration starting from currentAlarmTable to quickly retrieve just the active alarms instead of scanning the entire propertyTable. For example, if commonInternalTemperature.0 has an active HIHI alarm, the currentAlarmOID.12.commonInternalTemperature.0 instance returns the value commonInternalTemperature.0, with the leading 12 being the encoded length of that object's OID.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.5591.1.1.2.1.1 snmpwalk -v2c -c public <target> SCTE-HMS-PROPERTY-MIB::currentAlarmOID
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.5591.1.1.2.1.1.1 snmpget -v2c -c public <target> SCTE-HMS-PROPERTY-MIB::currentAlarmOID.1
Start monitoring cable/broadband HFC network element, transponder/line monitor/RF amplifier/fiber node/power supply (alarm-threshold property mechanism) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SCTE-HMS-PROPERTY-MIB::currentAlarmOID OID value, configure state conditions and alerts, and monitor any cable/broadband HFC network element, transponder/line monitor/RF amplifier/fiber node/power supply (alarm-threshold property mechanism) from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.5591 | scteRoot | SCTE-ROOT |
| 1.3.6.1.4.1.5591.1 | scteHmsTree | SCTE-ROOT |
| 1.3.6.1.4.1.5591.1.1 | propertyIdent | SCTE-HMS-ROOTS |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.5591.1.1.2 | currentAlarmTable | SCTE-HMS-PROPERTY-MIB |
| 1.3.6.1.4.1.5591.1.1.2.1 | currentAlarmEntry | SCTE-HMS-PROPERTY-MIB |
| 1.3.6.1.4.1.5591.1.1.2.1.1 | currentAlarmOID | SCTE-HMS-PROPERTY-MIB |