ANSI SCTE 38-8:2017 pdf download.Hybrid Fiber/Coax Outside Plant Status Monitoring-SCTE-HMS-DOWNLOAD-MIB-Management Information Base (MI B) Definition.
This document is identical to SCTE 38-8 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.
This document contains the definitions used to maintain one or more loadahie firmware images on an HMS transponder.
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 1155
SCTE 37
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-DOWNLOAD-MIB. It follows the IETF Simple Network Management Protocol (SNMP) for defining the managed objects.
The syntax is given below.
The Download MIII is used to maintain one or more loadahie firmware images on an HMS transponder. The M also has support for downloading to sub-components managed by an IIMS transponder.
The firmware image for one vendor’s transponder is not expected to be interchangeable with another vendor’s transponder. Care must be used not to download the wrong image. The DEVICE-KEY and dlDownload Key are used to ensure that only the intended transponders are rnoIitied.
The firmware may be transferred using broadcast, multicast, or unicast addressing. When using broadcast or multicast addressing. then suitable delays must be placed between each transaction to allow the transponder time to process the request. The value for these delays may be read from the download distribution file.
Down load Devices:
The MIB is designed to support download to sub-components attached to the transponder. These additional devices may be located on the Transponder Interface Bus JIB) or on a vendor specific bus. The Transponder Interface Bus is defined by SCTE 25-3 (formerly HMSO22. )
Within this MIB, device number I specifies the transponder. Device numbers 2 to 256 are reserved for TIB devices. The download device numbers 2 to 256 correspond to TIB addresses I to 255 respectively. Download device numbers greater than 256 may be used for vendor specific non-Till devices managed by the transponder.
— * Not all transponders support TIB based devices.
— * The initial version of SC1’E 25-3 (formerly HMSO22) does not support firmware
— * download.
— * The firmware update for a transponder is to be distributed in
— * a single file. The file has a header which describes information
— * used to configure a download. The header information consists
— * of a se of keywords with parameters, defined within comment lines.
* Comment lines begin with a pair of back to back ‘-‘ characters.
The standard distribution file format for all vendors uses S-Records to define the transponder firmware. Using a common tile format permits standard dowiiload tools to be developed.ANSI SCTE 38-8 pdf download.