SCTE-HMS-PROPERTY-MIB

        This MIB contains information that must be supported by all HMS
network elements, including but not limited to, transponders, 
line monitors, amplifiers, fiber nodes, and power supplies.
        
The Property MIB defines the 'properties' that may be associated with 
each parameter. This MIB is defined so that these 'properties' may be 
applied to any parameter, because the index to the MIB is the object 
identifier of the parameter.  The purpose of a 'property' is to provide 
a mechanism to manage alarm thresholds. It is not the responsibility of 
the transponder to check for violation of the above recommendations. 
The element manager is responsible for checking alarm limit values.
        
Entries in the property table are specifically for 'analog' parameters.  
The discrete property table is used to monitor other parameters.
        
Each property entry has four alarm threshold levels that may be established. 
These are:
        
LOLO                  Alarm threshold for the extreme low condition.
LO                    Alarm threshold for the low condition.
HI                    Alarm threshold for the high condition.
HIHI                  Alarm threshold for the extreme high condition.
        
In addition, there is a 'Deadband' setting which applies to all alarm thresholds.
After an alarm occurs, the parameter value must pass back over the alarm threshold 
by this amount for the alarm condition to be cleared. This Deadband is smaller than
the distance between any two alarm thresholds to avoid indeterminate states.
        
Alarm detection for each threshold is controlled by a specific bit in the alarmEnable 
variable for the entry.  Alarm detection is active when the corresponding bit in 
alarmEnable is enabled.
        
When an alarm condition is detected, in either the propertyTable or the discretePropertyTable,
an entry is created in the alarm log ( see HMS023Rx.MIB ) and an alarmEvent SNMP trap sent 
by the transponder/agent.
        
NOTE
Parameters which do not 'exist' must NOT have properties that are accessible.  For example, in
the HMS027 MIB (SCTE 38-4), the MIB object psOutputPowerSupport indicates whether or not the
power supply supports the psPowerOut object.  If the psPowerOut object is NOT supported, then
the properties normally associated with the psPowerOut object must not be accessible.
        
Some devices only require 16 bit integer or smaller and therefore only support 16 bit (or smaller)
values.  Values outside of the supported range will return a bad value error.
    
Source file
SCTE-HMS-PROPERTY-MIB
Last revised
Identity
propertyModuleIdentity
Base OID
1.3.6.1.4.1.5591.1.1.4
Imported Objects
SCTE-HMS-ROOTS propertyIdent
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page)
Net-SNMP examples using the scte MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'SCTE-HMS-PROPERTY-MIB' -M '/opt/observium/mibs/scte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'SCTE-HMS-PROPERTY-MIB::propertyModuleIdentity'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'SCTE-HMS-PROPERTY-MIB' -M '/opt/observium/mibs/scte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SCTE-HMS-PROPERTY-MIB::propertyModuleIdentity'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (25)
.1.3.6.1.4.1.5591.1.1.1
.1.3.6.1.4.1.5591.1.1.1.1
ObjectIdentifier
.1.3.6.1.4.1.5591.1.1.1.1.1
OctetString
.1.3.6.1.4.1.5591.1.1.1.1.2
Enumeration
.1.3.6.1.4.1.5591.1.1.1.1.3
.1.3.6.1.4.1.5591.1.1.1.1.4
.1.3.6.1.4.1.5591.1.1.1.1.5
.1.3.6.1.4.1.5591.1.1.1.1.6
.1.3.6.1.4.1.5591.1.1.1.1.7
.1.3.6.1.4.1.5591.1.1.1.1.9
.1.3.6.1.4.1.5591.1.1.2
.1.3.6.1.4.1.5591.1.1.2.1
ObjectIdentifier
.1.3.6.1.4.1.5591.1.1.2.1.1
Enumeration
.1.3.6.1.4.1.5591.1.1.2.1.2
.1.3.6.1.4.1.5591.1.1.2.1.3
.1.3.6.1.4.1.5591.1.1.3
.1.3.6.1.4.1.5591.1.1.3.1
ObjectIdentifier
.1.3.6.1.4.1.5591.1.1.3.1.1
Integer32
.1.3.6.1.4.1.5591.1.1.3.1.2
Enumeration
.1.3.6.1.4.1.5591.1.1.3.1.3
Enumeration
.1.3.6.1.4.1.5591.1.1.3.1.4
.1.3.6.1.4.1.5591.1.1.4
.1.3.6.1.4.1.5591.1.1.4.1
.1.3.6.1.4.1.5591.1.1.4.1.1
.1.3.6.1.4.1.5591.1.1.4.1.2
Dependencies (5) 3 direct · 2 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
  1. RFC1155-SMIrfc
  2. SCTE-ROOTscte
  3. SNMPv2-SMIrfc
  4. SCTE-HMS-ROOTSscte
  5. SNMPv2-CONFrfc
  6. SCTE-HMS-PROPERTY-MIBscteselected
Conformance Groups (3)
The analog alarms group defines objects which represent alarm information
for alarmable analog variables in an optical module.
.1.3.6.1.4.1.5591.1.1.4.1.2.1
The discrete alarms group defines objects which represent alarm information
for alarmable discrete variables in an optical module.
.1.3.6.1.4.1.5591.1.1.4.1.2.2
The current alarms group defines objects which represent a list of
active alarms present in an optical module.
.1.3.6.1.4.1.5591.1.1.4.1.2.3
Compliance Statements (1)

OID .1.3.6.1.4.1.5591.1.1.4.1.1.1
The compliance statement for HMS entities which
implement the SCTE HMS Property MIB.
Required groups