ANSI SCTE 95 pdf free download
ANSI SCTE 95 pdf free download.HMS Inside Plant HMTS Theory of Operation.
2.1 HMTS Scope The HMTS is designed to support only those devices that use the HMS MAC to exchange data between the device (transponder) and the termination system. The HMS MAC may be implemented on any type of port defined by the HMTS standard. 2.2 HMTS SNMP Support: v1, v2c, or v3 The three SNMP versions that are used most frequently are SNMPv1, SNMPv2c and SNMPv3. While SNMPv1 and SNMPv2c support community strings, SNMPv3 does not but it has an extensive security model. Although the HMTS MIB is written in the SMIv2 syntax, an HMTS is not required to support SNMPv2c operations and SNMPv2c notifications. An HMTS can use SNMPv1 or SNMPv3 as well, or any combination of SNMPv1, SNMPv2c and SNMPv3. An HMTS e.g. could only support SNMPv1 operations and deliver SNMPv1 traps. Next to the HMTS SNMP agent itself, there are also the SNMPv1 agents in the transponders. An HMTS can support translation of the SNMPv1 transponder traffic to SNMPv2c or SNMPv3. Notes: ● If the HMTS agent supports SNMPv1, then the agent should support RFC1213-MIB (RFC 1213, a.k.a. MIB-II) instead of SNMPv2-MIB (RFC 3418, only applies to SNMPv2 and SNMPv3). ● If the HMTS is a proxy, and it supports SNMPv2c or SNMPv3, then the snmpTargetParamsMPModel column in the SNMP-TARGET-MIB controls whether transponder traps should be sent unmodified using SNMPvI, or whether these traps should be translated into SNMPv2c or SNMPv3. ● If the HMTS is of the proxy type and if the HMTS supports SNMPv3, the addressing information stored in the community string for SNMPv1 or SNMPv2, must now be stored in the context field of an SNMPv3 PDU. If the SNMP-PROXY-MIB is implemented on an HMTS, it should be kept consistent with the information in the device table. See also RFC 2273 for more information.● When the HMTS agent supports SNMPv3, then three additional MIBs should be supported: the SNMP- VIEW-BASED-ACM-MIB (RFC 2265), the SNMP-USER-BASED-SM-MIB (RFC 2574) and the SNMP-COMMUNITY-MIB. The SNMP-COMMUNITY-MIB is defined in RFC 2576, titled Coexistence between Version I, Version 2, and Version 3 of the Internet-standard Network Management Framework. Examples of possible HMTS implementations are: The HMTS agent supports SNMPv1, and all communication to transponders happens in SNMPvI. The HMTS is a proxy, its agent supports SNMPv2c, and translates all transponder communication between SNMPv1 and SNMPv2c. The HMTS is a gateway, its agent supports SNMPv2c, and all communication to transponders happens in SNMPv1. The HMTS is a gateway, its agent supports SNMPv3, and transponder communication happens in SNMPvl. The HMTS is a gateway, its agent supports SNMPv3, and translates all transponder operations between SNMPv1 and SNMPv3. The HMTS is a proxy, its agent supports SNMPv3, and translates all transponder operations between SNMPv1 and SNMPv3. 3 HMTS Internal Clock Synchronization with External Systems The HMTS must periodically set the time of day in all HMS transponders. This is done to ensure that SNMP traps are generated with the correct timestamp. For this to be of use, the HMTS will support setting of it’s own internal clock through an SNMP MIB and will optionally support time syne through use of a network timeserver.ANSI SCTE 95 pdf download.
