ANSI SCTE 94-2:2017 pdf download.HMS Common Inside Plant-Management Information Base(MIB)-SCTE-HMS-HE-RF-SWITCH-MIB.
This document provides MIB definitions for HMS RF switch equipment present in the headend (or indoor) and is supported by a SNMP agent.
2. COPYRIGHT
The MIB definition found in this document may be incorporated directly in products without further permission from the copyright owner, SCTE.
3. NORMATIVE REFERENCE
IETF RFC 1907 SNMPv2-MIB
IETF RFC 2578 SNMPv2-SMI
IETF RFC 2579 SNMPv2-TC
IETF RFC 2580 SNMPv2-CONF
IETF RFC 2737 ENTITY-MIB
SCTE 36 SCTE-ROOT
SCTE 37 SCTE-HMS-ROOTS
SCTE 38-11 SC1E-HMS-HEADENDIDENT-MIB
SCTE 83-4 SCTE-HMS-HE-RF-MIB
SCTE 38-1 SCTE-HMS-HE-PROPERTY-MIB
SCTE 84-1 SCTE-HMS-HE-COMMON-MIB
4. INFORMATIVE REFERENCE None
5. 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.
6. REQUIREMENTS
This section defines the mandatory syntax of the SCTE-HMS-HE-RF-SWITCH-MIB. It follows the IETF Simple Network Management Protocol (SNMP) for defining managed objects.
The syntax is given below.
This MIB module is for representing RF switch equipment present in the headend (or indoor) and is supported by a SNMP agent.
This MIB is limited in its scope and intended to describe an A-B (2 input and 1 output) or a crossbar RF switch. Up to 2 RF inputs and 2 outputs are supported. Any devices with more than 2 RF inputs or outputs shall be covered by another M1B.
This MIB does not intend to dictate all of the nuances involved in changing control settings (automatic or manual mode, changing switch controls in each possible mode combination). The most common desired behaviors arc noted but specific switch operation and behavior are left to the RF switch vendors.
Not all control enumerations must be supported. This is noted in the variables that have optional enumerations.
Refer to the associated notes for information on what SNMP responses should be returned for unsupported enumerations.”
— Every RF switch is modeled by the tables presented
— in this MIB module. These tables extend the eniPhysicalTable
— according to RFC 2737. The extension index entPhysicallndex uniquely
— identifies the RF switch.
— Every RF switch is also modeled by the following tables:
— entPhysicalEntry – I row; (defined in document: RFC2737)
— heCommonEntry – 1 row. (defined in document: HMS Ill)
— Every RF switch module will have its alarms modeled by the table:
— propertyEntry – x rows; (defined in document: HMSO26)
— (where x is the nos. of alarmable analog properties supported
— by the RF switch)
discretePropcrtyEntry – y rows; (defined in document: HMSO26) (where y is the nos. of alarmable digital properties supported by
— the RF switch)
— Every RF switch module will have a list of currently active
— alarms modeled by the table:
— currentAlarmEntry – z rows; (defined in document: HMSO26)
— (where z is the nos. of current active alarms in the RF
— switch)
— Thus. an A-B RF switch (2 RF inputs and one RF output)
— will be represented by one row in eniPhysicalTable, one row in
— heCommonTable, one row in hcRFSwiichUnitTable, two rows in
— hcRFSwitchlnputTablc and one row in heRFSwitchOutputTable.
— Additionally, a crossbar RF switch (2 inputs and 2 outputs).ANSI SCTE 94-2 pdf download.