SCTE-HMS-ALARMS-MIB
- Source file
SCTE-HMS-ALARMS-MIB- Last revised
- Not declared
Imported Objects
| RFC-1212 | OBJECT-TYPE (no object page) |
| RFC-1215 | TRAP-TYPE (no object page) |
| RFC1213-MIB | DisplayString |
| SCTE-HMS-COMMON-MIB | commonLogicalID commonPhysAddress |
| SCTE-HMS-ROOTS | alarmsIdent |
| SCTE-ROOT | scteHmsTree |
Objects (7)
Showing 7 of 7 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
|
|
.1.3.6.1.4.1.5591.1.2.1 |
|
|
|
.1.3.6.1.4.1.5591.1.2.2 |
|
|
|
.1.3.6.1.4.1.5591.1.2.3 |
|
|
|
.1.3.6.1.4.1.5591.1.2.3.1 |
|
|
|
Integer32
|
.1.3.6.1.4.1.5591.1.2.3.1.1 |
|
|
OctetString
|
.1.3.6.1.4.1.5591.1.2.3.1.2 |
|
|
.1.3.6.1.4.1.5591.1.2.4 |
Dependencies (10) 6 direct · 4 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- RFC-1212rfc
- RFC-1215rfc
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- IANAifType-MIBrfc
- RFC1155-SMIrfc
- RFC1213-MIBrfc
- SCTE-ROOTscte
- SCTE-HMS-ROOTSscte
- SCTE-HMS-COMMON-MIBscte
- SCTE-HMS-ALARMS-MIBscteselected
Notifications / Traps (1)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.5591.1.0.1 |
The SNMP trap that is generated when an alarm event is found. At the
option of the transponder, the alarmText variable may be reported as a fourth varbind, for those instances where an additional text field is indicated by the object, as noted in the alarmText object description. Also, at the option of the transponder, additional specific varbinds MAY be added to clearly define the event that caused the trap to be sent. In the case where the event is defined in the propertyTable, the additional varbinds (when present) MUST BE the parameterOID object & value and the currentAlarmState object & value (see HMS026) from the table entry for which the trap was generated. In the case where the event is defined in the discretePropertyTable, the additional varbinds (when present) MUST BE the discreteParameterOID object & value and the discreteAlarmState object & value from the table entry for which the trap was generated. The non-optional parameters of the trap (commonPhysAddress, commonLogicalID, alarmLogInformation) MUST still be filled in properly, regardless of whether additional parameters are appended. It is highly recommended that transponders not requiring specific HMS software at the headend include these varbinds in order to assist networks that do not implement HMS-specific SNMP management software. Additionally, though indicated as an option for the transponder, it is recommended that transponders using HMS specified RF transmission (specifically, SCTE 25-1 aka HMS005) SHOULD NOT append these additional parameters, due to the limited bandwidth available in the return path. |