ANSI SCTE 84-1-2017 pdf free download.HMS Common Inside Plant Management Information Base (MIB) Part 1: SCTE-HMS-HE-COMMON-MIB
SCOPE
This document is identical to SCTE 84-1 2009 except for informative components which
may have been updated such as the title page, NOTICE text, headers and footers. No
normative changes have been made to this document.
The MIB module is for representing general information about optical equipment present
in the headend (or indoor) and is supported by an SNMP agent.
COPYRIGHT
The MIB definition found in this document may be incorporated directly in products
without further permission from the copyright owner, SCTE.
NORMATIVE REFERENCE
IETF RFC2578, Structure of Management Information Version 2 (SMIv2)
IETF RFC2579, Textual Conventions for SMIv2
IETF RFC2580, Conformance Statements for SMIv2
IETF RFC2737, Entity MIB (Version 2)
ANSI/SCTE 36 ,SCTE Root Management Information Block (MIB)
SCTE 38-11, Hybrid Management Sub-layer Management Information Base (MIB) Part
11: SCTE-HMS-HEADENDIDENT-MIB
IETF RFC2573, SNMP Applications
IETF RFC1907, Management Information Base for Version 2 of the Simple Network
Management Protocol (SNMPv2)
ANSI/SCTE 38-1, Hybrid Management Sublayer Management Information Blocks
(MIB) Part 1: Property MIB
INFORMATIVE REFERENCE
None TERMS AND DEFINITIONS
This document defines the following terms:
Management Information Base (MIB) – the specification of information in a manner
that allows standard access through a network management protocol.
REQUIREMENTS
This section defines the mandatory syntax of the SCTE-HMS-HE-COMMON-MIB. It
follows the IETF Simple Network Management Protocol (SNMP) for defining managed
objects.
The syntax is given below:
The detectionEnabled(2) value permits alarm detection to run. The detection process continues from the state the headend entity was in prior to detectionEnabled(2) being set. The detectionEnabledAndRegenerate(3) value clears all alarm information and permits alarm detection to run. All alarm properties, both discrete and analog, are restored to the nominal value before alarm detection runs. Any properties that are in an alarm state SHALL NOT produce a ‘return to normal’ alarm as part of the process. Setting this value clears the heCommonLogTable and the currentAlarmTable. The detectionEnabledAndRegenerate(3) value is transient, that is a SET request with a value detectionEnabledAndRegnerate(3) shall return the same value detectionEnabledAndRegnerate(3). Subsequent GET requests shall return a value detectionEnabled(2). The detectionDisabled(1) value shall affect the generation of heCommonAlarmEvent trap only. Traps added in the future are assumed to be unaffected by this object, unless stated in the description of that trap.
“The current number of entries in the heCommonLogTable. Before the very first wrap-around condition occurs for heCommonLogIndex, heCommonLogNumberOfEntries will return the total number of entries logged in heCommonLogTable, since the unit was powered up. After the first wrap-around condition has occured for for the value of the MIB variable heCommonLogIndex, heCommonLogNumberOfEntries will return the maximum number of rows the heCommonLogTable can hold.
“An index that uniquely identifies an entry in the log table. Indexes are assigned beginning with 1 and increased by one with each new log entry up to 65535. The next entry after 65535 is one. The agent may choose to delete the oldest instances of heCommonLogEntry as required because of lack of memory. It is an implementation-specific matter as to when this deletion may occur. Note – The wrap-around for the heCommonLogIndex variable MUST occur after 65535 regardless of the implementation specific size of the hlCommonLogTable.”
