Status in source: unspecified.
Technical details
{
"smi_kind": "TRAP-TYPE",
"definition": [
"hmsAlarmEvent",
"TRAP-TYPE",
"ENTERPRISE",
"scteHmsTree",
"VARIABLES",
"{",
"commonPhysAddress",
",",
"commonLogicalID",
",",
"alarmLogInformation",
"}",
"DESCRIPTION",
"\"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.\"",
"::=",
"1"
],
"syntax_tree": [
[
"objectIdentifier",
[
"scteHmsTree"
]
],
[
"VarTypes",
[
"commonPhysAddress",
"commonLogicalID",
"alarmLogInformation"
]
],
[
"DESCRIPTION",
"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."
],
null
]
}