Alpha XM3-HP Technical Manual

AlphaNet™ IDH4 Series DOCSIS® Status Monitor for the XM3-HP CableUPS

Technical Manual

Effective: November 2013

®

Alpha Technologies

Power

®

AlphaNet™ IDH4 Series

DOCSIS® Status Monitor for XM3-HP CableUPS®

Technical Manual

746-257-B5-001, Rev. A1

Effective Date: November 2013

Copyright© 2013

Alpha Technologies, Inc.

member of The Group

NOTE:

Alpha denies responsibility for any damage or injury involving its enclosures, power supplies, generators,
batteries or other hardware, manufactured by Alpha or members of the Alpha Group, when used for an
unintended purpose, installed or operated in an unapproved manner, or improperly maintained.

NOTE:

Photographs and drawings in this manual are for illustrative purposes only and might not exactly match your
installation.

NOTE:

Review this manual before proceeding. If there are questions regarding the safe installation or operation of
this product, please contact Alpha Technologies or your nearest Alpha representative.

TM

Contacting Alpha Technologies: www.alpha.com

or

For general product information and customer service (7 AM to 5 PM, Pacic Time), call

To report errors in this document, send email to:[e-mail]

746-257-B5-001, Rev. A1 (11/2013)

1-800-863-3930

For complete technical support, call

1-800-863-3364

7 AM to 5 PM, Pacic Time or 24/7 emergency support

3

Contents

Safety Notes .....................................................................................................................................7

1.0 Introduction ....................................................................................................................................8

2.0 Overview ...................................................................................................................................10

2.1 System Diagram ........................................................................................................10

2.2 Network Connectivity .................................................................................................11

2.3 System Conguration and Installation .......................................................................11

2.4 IDH4 Series Start Up and Reboot Routine ................................................................12

3.0 Network Conguration .................................................................................................................13

3.1 Provisioning the DHCP Server with the MAC Addresses ..........................................13

3.2 The DOCSIS Conguration File .................................................................................14

3.2.1 Setting Modem Community Strings .....................................................................14

3.2.2 Setting SNMP Trap Destination Addresses..........................................................15

3.2.3 Sample DOCSIS Conguration File Entries .........................................................16

3.2.4 Proprietary Conguration File idhdoc04.cfg .........................................................17

3.2.5 Changing Default idhdoc04.cfg Download Settings .............................................17

3.3 Setting Communication Options ................................................................................18

4.0 Web Interface ..............................................................................................................................19

4.1 Local Web Server Access ..........................................................................................19

4.2 Remote Web Server Access ......................................................................................22

4.3 Navigating the Web Page ..........................................................................................23

4.3.1 Web Interface Security Levels .............................................................................24

4.4 Verifying Communication Parameters ........................................................................25

4.5 Verifying Power Supply and Battery Parameters .......................................................26

4.6 Remote Self Tests via the Web Page ........................................................................26

4.7 Viewing HMS Alarm Status via the Web Page ...........................................................27

4.8 Setting the I/O Controller via the Web Page ..............................................................28

4.9 Viewing and Conguring Power Supply Settings via the Web Page .........................29

4.10 Viewing and Conguring Generator Settings via the Web Page ...............................31

4.11 Viewing AlphaApps Information via the Web Page ....................................................32

4.12 Battery Management ..................................................................................................33

4.13 Viewing Power Supply Event and Conguration Logs ...............................................35

4.14 Battery Event Log ......................................................................................................39

4.15 Viewing the Modem Event Log via the Web Page .....................................................40

4.16 RF Constellation Page ...............................................................................................41

4.17 Constellation Data Interpretation ...............................................................................42

4.18 Microreections ..........................................................................................................43

5.0 Upgrading Firmware ....................................................................................................................44

5.1 Upgrading IDH4 Series Modem Firmware .................................................................44

5.1.1 Identifying the Modem and Obtaining Firmware Files ..........................................44

5.1.2 Modem Firmware Upgrade SNMP Parameters ...................................................44

5.1.3 Upgrading Manually by Setting SNMP Parameters .............................................45

5.1.4 Upgrading via the DOCSIS Conguration File .....................................................45

6.0 Data Management .......................................................................................................................46

6.1 SCTE-HMS MIBs ......................................................................................................46

6.2 SCTE-HMS MIB Alarms .............................................................................................47

6.2.1 SCTE-HMS Congurable Alarms .........................................................................47

6.2.2 SNMP Traps .........................................................................................................50

4

746-257-B5-001, Rev. A1 (11/2013)

Contents, continued

6.2.3 General Power Supply Alarms .............................................................................52

6.2.4 Battery Alarms ......................................................................................................54

6.3 The Alpha MIBs ..........................................................................................................55

6.3.1 The Alpha MIB Structure ......................................................................................57

7.0 Installation ...................................................................................................................................58

7.1 Verifying Power Supply Device Address ...................................................................58

7.2 Installation / Replacement Procedure in XM3-HP Power Supplies ............................59

7.3 IDH4X LEDs and Connections ...................................................................................61

7.4 IDH4 LEDs and Connections .....................................................................................62

7.5 IDH4L LEDs and Connections ...................................................................................63

7.6 Connecting the RF Drop ............................................................................................64

7.7 Front Panel Connections ...........................................................................................64

7.8 Environmental Connections .......................................................................................65

7.8.1 Connecting the Battery Heater Mat Controller .....................................................65

7.9 Environmental Control MIBs .....................................................................................66

7.10 Conguring the Battery Heater Mat Controller ...........................................................68

8.0 Battery Sense Wire Kits...............................................................................................................69

8.1 36V Single and Dual Strings ......................................................................................69

9.0 Start Up and Verication ..............................................................................................................70

9.1 Initial Start Up and Local Verication .........................................................................70

9.2 Verifying Correct Hardware Interconnection ..............................................................72

9.3 System Status Indicators and Reset Button ..............................................................73

9.3.1 Detailed LED Descriptions ...................................................................................73

9.3.2 Resetting the Transponder ...................................................................................75

9.4 Verifying Communications via the Headend ..............................................................75

10.0 MIB Parameters.........................................................................................................................76

10.1 Denitions and Settings .............................................................................................76

11.0 Specications .............................................................................................................................83

12.0 Glossary ...................................................................................................................................85

13.0 Dual IP Mode .............................................................................................................................86

13.1 Overview ....................................................................................................................86

13.2 Web Comparison, Single IP Mode/Dual IP Mode ......................................................87

13.3 Conguring Dual IP Mode ..........................................................................................88

13.3.1 idhdoc04.cfg in Dual IP Mode ..............................................................................89

13.3.2 Changing Default idhdoc04.cfg Download Settings in Dual IP Mode ..................89

13.3.3 Specifying idhdoc04.cfg Filename and Location via DHCP Tags ........................90

13.4 Dual IP SNMP Community Strings ............................................................................91

13.5 Security in Dual IP Mode ...........................................................................................91

13.6 Copyright Information .................................................................................................92

746-257-B5-001, Rev. A1 (11/2013)

5

Figures

Fig. 1-1, AlphaNet IDH4X ...................................................................................................................... 8

Fig. 1-2, AlphaNet IDH4 ......................................................................................................................... 8

Fig. 1-3, AlphaNet IDH4L ....................................................................................................................... 8

Fig. 1-4, Side View, AlphaNet IDH4 Series ............................................................................................ 9

Fig. 2-1, Representative System Arrangement .................................................................................... 10

Fig. 2-2, Order of Operations ............................................................................................................... 12

Fig. 3-1, Locations of MAC Address Labels ........................................................................................ 13

Fig. 3-2, Sample DOCSIS Conguration File ...................................................................................... 16

Fig. 4-1, IDH4 Series Web Page ......................................................................................................... 19

Fig. 4-2, Local Area Connection Properties Screen ............................................................................ 20

Fig. 4-3, Internet Protocol (TCP/IP) Properties Screen ....................................................................... 20

Fig. 4-4, Local Area Connection Properties Screen, Windows 7 ......................................................... 21

Fig. 4-5, Internet Protocol (TCP/IP) Properties Screen, Windows 7 .................................................... 21

Fig. 4-6, Web Server Home Page ....................................................................................................... 22

Fig. 4-7, IDH4 Series Site Map ............................................................................................................ 23

Fig. 4-8, IDH4 Series Transponder Security Levels ............................................................................ 24

Fig. 4-9, Communications Parameters ................................................................................................ 25

Fig. 4-10, Advanced Communications Parameters ............................................................................. 25

Fig. 4-11, Power Supply and Battery Parameters ............................................................................... 26

Fig. 4-12, Location of Start Button for Self Test ................................................................................... 26

Fig. 4-13, HMS Alarm Conguration .................................................................................................... 27

Fig. 4-14, Advanced I/O Controller Status Screen ............................................................................... 28

Fig. 4-15, Advanced Power Supply Settings Screen ........................................................................... 29

Fig. 4-16, Advanced Generator Status Screen .................................................................................... 31

Fig. 4-17, AlphaApps and Utility Status Parameters ............................................................................ 32

Fig. 4-18, Battery Mangement ............................................................................................................. 33

Fig. 4-19, Battery Model Selection ...................................................................................................... 34

Fig. 4-20, System Log Overview ......................................................................................................... 35

Fig. 4-21, Power Supply Event Log ..................................................................................................... 37

Fig. 4-22, Power Supply Conguration Log ......................................................................................... 38

Fig. 4-23, Battery Event Log ................................................................................................................ 39

Fig. 4-24, Modem Event Log Screen ................................................................................................... 40

Fig. 4-25, RF Constellation Page ........................................................................................................ 41

Fig. 4-26, Microreections ................................................................................................................... 43

Fig. 6-1, Sample Raw SNMP Alarm Trap ............................................................................................ 50

Fig. 6-2, Sample Translated SNMP Alarm Trap ................................................................................... 50

Fig. 6-3, IDH4 Series Alarms on General Web Page .......................................................................... 54

Fig. 7-1, Captive Screw Locations ...................................................................................................... 59

Fig. 7-2, The 18-pin Connector ............................................................................................................ 60

Fig. 7-3, Connecting the Transponder to the Inverter Module ............................................................. 60

Fig. 7-4, IDH4X LEDs and Connectors ................................................................................................ 61

Fig. 7-5, IDH4 LEDs and Connectors .................................................................................................. 62

Fig. 7-6, IDH4L LEDs and Connections .............................................................................................. 63

Fig. 7-7, Connecting the RF Drop ........................................................................................................ 64

Fig. 7-8, System Interconnection Diagram .......................................................................................... 64

Fig. 8-1, 36V System, Single String ..................................................................................................... 69

Fig. 8-2, 36V System, Dual String ....................................................................................................... 69

Fig. 9-1, XM3-HP Smart Display Screens ........................................................................................... 70

Fig. 9-2, General Tab Screen .............................................................................................................. 71

Fig. 9-3, Power Supply Section - General Page ................................................................................. 72

Fig. 9-4, LED Functionality and Indications ......................................................................................... 73

Fig. 9-5, IDH4 Series Web Page, RF Power Level Indicators ............................................................. 75

Fig. 13-1, Simplied Block Diagram, Single IP Mode .......................................................................... 86

Fig. 13-2, Simplied Block Diagram, Dual IP Mode ............................................................................. 86

Fig. 13-3, Web Page, Single IP IDH4 Series ....................................................................................... 87

Fig. 13-4, Web Page, Dual IP IDH4 Series ......................................................................................... 87

Fig. 13-5, Dual IP Conguration Settings on Communications Page of IDH4 Web Server ................. 88

Fig. 13-6, Dual IP Parameters on the General Page of IDH4 Web Server .......................................... 88

6

746-257-B5-001, Rev. A1 (11/2013)

Tables

Table 1-1, IDH4 Series Transponder Model Variation ........................................................................... 8

Table 2-1, LEDs and Indications .......................................................................................................... 12

Table 3-1, Modem Community String Parameters ............................................................................... 14

Table 3-2, Trap Destination Addresses ................................................................................................ 15

Table 3-3, Changing Default idhdoc04.cfg Download Settings............................................................ 17

Table 3-4, Transponder Communications Parameters ........................................................................ 18

Table 4-1, Time Offset Values and Location Reference (offset +/- GMT) ............................................ 36

Table 4-2, Constellation Impairments .................................................................................................. 42

Table 5-1, Modem Firmware Upgrade SNMP Parameters .................................................................. 44

Table 5-2, Setting SNMP MIB Parameters .......................................................................................... 45

Table 5-3, Setting docsDevSoftware SNMP Parameters .................................................................... 45

Table 6-1, SCTE-HMS MIB Files ......................................................................................................... 46

Table 6-2, Binary to Hex Conversions for Alarm Settings .................................................................... 47

Table 6-3, Recommended Settings for IDH4 Series Analog Alarms ................................................... 48

Table 6-4, Recommended Settings for Discrete Alarms ...................................................................... 49

Table 6-5, SNMP Alarm Trap VarBinds and Explanations ................................................................... 51

Table 6-6, Power Alarms: Classications, Causes and Corrections .................................................... 52

Table 6-7, Battery Alarms: Classications, Causes and Corrections ................................................... 54

Table 6-8, Alpha MIB Hierarchy ........................................................................................................... 56

Table 6-9, Alpha MIB Structure ............................................................................................................ 57

Table 7-1, Environmental Control MIBs ............................................................................................... 66

Table 7-2, OID Values for Battery Heater Mat Controller ..................................................................... 68

Table 7-3, SNMP MIB Points for Battery Heater Mat Controller .......................................................... 68

Table 9-1, SCTE-HMS Property Table ................................................................................................. 74

Table 9-2, Rx/Tx Power LED Color Ranges ........................................................................................ 74

Table 13-1, Single IP Mode versus Dual IP Mode ............................................................................... 86

Table 13-2, Enabling Dual IP Mode ..................................................................................................... 88

Table 13-3, idhdoc04.cfg Download Settings ...................................................................................... 89

Table 13-4, Community Strings ........................................................................................................... 91

Table 13-5, Data Access Key Parameters ........................................................................................... 91

Table 13-6, Secure Access Table Parameters ..................................................................................... 92

Safety Notes

Review the drawings and illustrations contained in this manual before proceeding. If there are any questions regarding
the safe installation or operation of the system, contact Alpha Technologies or the nearest Alpha representative. Save this
document for future reference.

To reduce the risk of injury or death and to ensure the continued safe operation of this product, the following symbols have
been placed throughout this manual. Where these symbols appear, use extra care and attention.

WARNING!

WARNING presents safety information to PREVENT INJURY or DEATH to the technician or user.

CAUTION!

CAUTION indicates safety information intended to PREVENT DAMAGE to material or equipment.

NOTE:

A NOTE provides additional information to help complete a specic task or procedure.

ATTENTION:

The use of ATTENTION indicates specic regulatory/code requirements that may affect the placement of equipment

and /or installation procedures.

746-257-B5-001, Rev. A1 (11/2013)

7

1.0 Introduction

The AlphaNet IDH4 Series Embedded DOCSIS Transponder allows monitoring of Alpha power supplies through
existing cable network infrastructure. Advanced networking services provide quick reporting and access to
critical powering information. This manual focuses on the IDH4 Series transponders complementing the XM3-HP
CableUPS.

The IDH4 Series utilizes Simple Network Management Protocol (SNMP) and Management Information Bases
(MIBs) to provide network status monitoring and diagnostics. A Web interface enables authorized personnel
direct access to advanced diagnostics using a common Web browser. No custom software is required. This
manual addresses the three models of the IDH4 Series. The table below compares the differences between the
transponder models when installed in an XM3-HP power supply.

Model IDH4X IDH4 IDH4L

Part Number 746-257-20 746-257-21 746-257-22

Capacity 4 power supplies (plus generator) 1 power supply 1 power supply

1 & 2 Battery Strings Yes Yes Yes with SAG option

3 & 4 Battery Strings Yes No Yes with SAG option

Tamper Switch Yes Yes Yes

Environmental Control Yes No Yes

COM Port (AlphaBus) Yes No No

Ethernet Port Yes Yes Yes

Table 1-1, IDH4 Series Transponder Model Variation

Fig. 1-1, AlphaNet IDH4X Fig. 1-2, AlphaNet IDH4 Fig. 1-3, AlphaNet IDH4L

Primary Features:

• 10/100 Mbps auto-negotiating standard Ethernet interface

• Supports SNMPv1, v2c

• Extensive power supply diagnostic MIBs

• Embedded Web server for direct diagnostics

• Environmentally hardened DOCSIS cable modem and transponder

• Local Ethernet port provides technician on-site access to extensive power supply diagnostics*

• Angled RF connector reduces cable bend radius

• Diagnostic LEDs

* Ethernet port also permits the connecting of external CPE devices

8

746-257-B5-001, Rev. A1 (11/2013)

1.0 Introduction, continued

Environmental IO Connector
(IDH4X and IDH4L only)

Tamper Connector

Ethernet Port for Local Diagnostics

Intelligent CableUPS Interface
(located on other side of the board)

RF Connector

COM Port (IDH4X only)

Battery Monitoring Connection A/B
(IDH4 and IDH4X only)

Battery Monitoring Connection C/D
(IDH4X only)

Fig. 1-4, Side View, AlphaNet IDH4 Series

746-257-B5-001, Rev. A1 (11/2013)

9

2.0 Overview

2.1 System Diagram

Power Supply

1

SNMP-based Network Management System

10

IDH4

2

Series

Coax/HFC Network

5

Local Computer

4

CMTS

6

TCP/IP Network

12

External Generator

3

DHCP Server

7

TFTP Server TOD Server

8

9

Web Browser

11

Fig. 2-1, Representative System Arrangement

All power supply data is stored in the power supply inverter module's class information base (CIB) tables in the power supply.

1

This data is accessible directly via the power supply’s smart display (see the power supply’s technical manual for details).
The CIB tables are the source of the transponder’s data.

The IDH4 Series contains both SCTE-HMS Management Information Base (MIBs) and the proprietary Alpha MIB tables. The

2

SCTE-HMS MIBs are industry standard MIB tables that store power supply, battery and generator data from the CIB tables
(See Section 7.0, Data Management). The Alpha MIB contains all the data of the SCTE-HMS MIBs, additional power supply

settings and values, and IDH4 Series conguration values.

An external generator or additional power supplies may be connected through the COM (AlphaBus, available only on the

3

IDH4X) port permitting monitoring locally through the Ethernet connector or remotely via the Web page or SNMP-based
Network Management System.

Power supply and transponder parameters can be monitored and set locally using a personal computer and a standard

4

Ethernet cable.

The IDH4 Series transmits data via its cable modem directly over the Coax or Hybrid Fiber Coax network.

5

The Cable Modem Termination System (CMTS) is the bridge between the cable network and the TCP/IP network. The IDH4

6

Series’ cable modem communicates directly with the CMTS.

The Dynamic Host Control Protocol (DHCP) server needs to be provisioned with the IDH4’s cable modem CM MAC address

7

and the MAC address needs to be assigned a DOCSIS Conguration File.

10

The DOCSIS Conguration File and rmware les should be available in the Root Directory of the Trivial File Transfer

8

Protocol (TFTP) Server.

The Time of Day (TOD) Server provides the cable modem with the current date and time via the SNTP protocol.

9

A Network Management System (NMS) or MIB Browser allows remote monitoring of parameter values and changing of

10

settings in SNMP MIB tables. SCTE-HMS and Alpha MIBs must be installed in the browser. Alarms and traps can be set and
monitored.

The power supply and generator data may be accessed remotely through the transponder's Web page by placing its IP
address into a standard Internet Web browser.

11

The following ports of the Transmission Control Protocol/Internet Protocol network must be opened: 161=SNMP, 162=SNMP,
Traps, 69=TFTP, 80=HTTP.

12

746-257-B5-001, Rev. A1 (11/2013)

2.0 Overview, continued

2.2 Network Connectivity

The IDH4 Series cable modem must be recognized by the CMTS as a valid device to be assigned an IP
address from the DHCP server, to locate the TFTP and TOD servers, and to communicate with the SNMP
management server (trap receiver).

Data from both the cable modem and power supply are accessed and managed through the modem’s
IP address on the secure private modem network. The transponder is not accessible from the public
Customer Premises Equipment (CPE) network. Consequently, the Network Management System (NMS)
that monitors the power supplies must have access to the same private modem network.

CMTS and system vendors use different security methods to insure network integrity, but common
considerations are:

• Network MAC ltering may have to be modied to allow the cable modem OUI of 00:26:97
for North America.

• For SNMP access, UDP ports 161 and 162 must not be blocked.

• For TFTP access, port 69 must not be blocked.

• For HTTP access, port 80 must not be blocked.

• For SNTP access, port 37 must not be blocked.

• Firewalls must allow TFTP, DHCP, SNMP and TOD communication to the cable modem.

• If the address of the TFTP or TOD server is different than the DHCP server, the response from the

DHCP server must contain the TFTP and TOD addresses.

2.3 System Conguration and Installation

NOTE:

Before installation, read all of the System Overview Sections.

IDH4 Series installation and setup is comprised of three basic steps:

1. Conguring the Network: Provisioning the DHCP Server with the transponder’s MAC address and
assigning it a DOCSIS Conguration File.

2. Setting Options: The IDH4 Series is designed for out of the box, "plug and play" operation, but
non-default settings such as SNMP trap destination addresses may be required for the Network
Management System (NMS). SNMP trap addresses can be set automatically via the DOCSIS

Conguration File per RFC 4639, while IDH4 Series proprietary options may be set through type-11

TLV entries. The SCTE-HMS and Alpha MIBs may need to be compiled into a MIB browser before it
can be used to monitor or set transponder and power supply parameters.

3. Field Installation of the IDH4 Series into the power supply, connecting the battery sense wire
harnesses and verifying operation.

These steps can be performed independently of one another. However, conguring the network prior
to eld installation will allow the installation to be veried while personnel are still on-site. Performing
eld installation before network conguration and before the installation can be veried, might result in
additional eld service calls to correct mistakes.

Carefully read the following section in order to understand the dependencies within the system before

performing system conguration or hardware installation.

746-257-B5-001, Rev. A1 (11/2013)

11

2.0 Overview, continued

2.4 IDH4 Series Start Up and Reboot Routine

TFTP Server

TOD Server

DHCP Server

TCP/IP NetworkHFC Network

5

4

3

Switches

Routers

Firewalls

Network Management System

MIB Browser

Web Browser

CMTS

2

6

IDH4 Series

1

Power Supply

7

Local Laptop

Fig. 2-2, Order of Operations

The above diagram, read left to right, indicates the order of operations as the transponder comes online.
There are certain conditions that must exist for each step to occur, resulting in successful data monitoring and
management. The numbers below correspond to the numbered arrows above.

LEDs and Indications

Ref #

1

2

3 5

to

6

7

Communications

State

Transponder Initializing/
Searching for
Downstream DOCSIS
channel

DOCSIS Channel locked

- Completing upstream
and network registration

Online - Registration
Complete

IDH4 Series fully
functional

Laptop Connected to
local Ethernet port

ALM/RDY Downstream (DS) Registration (REG)

ON (Green) Flashing OFF OFF OFF OFF

ON (Green) ON Flashing ON (Green) OFF OFF

Flashing

(Green)

Flashing

(Green)

Flashing

(Green)

ON ON ON (Green) OFF and ON OFF

ON ON ON (Green)

ON ON ON (Green) Bursts

Rx/Tx

Power

Communications (COM) Ethernet (ETH)

Bursts when communicating to

multiple power supplies (IDH4X

OFF

LNK - ON

ACT - Bursts

12

Refer to Ref #6 in the above table for normal LED behavior when the IDH4 is fully functional.

• Blue Rx/Tx Power LED indicates Rx/Tx Power at a warning level. Make the necessary RF level adjustments.

• Red Rx/Tx Power LED indicates Rx/Tx Power at an alert level. Make the necessary RF level adjustments.

Table 2-1, LEDs and Indications

746-257-B5-001, Rev. A1 (11/2013)

3.0 Network Conguration

3.1 Provisioning the DHCP Server with the MAC Addresses

On the DHCP server, assign the cable modem’s CM MAC address with a DOCSIS Conguration File to

set modem communication options. (See Section 3.2, The DOCSIS Conguration File for instructions

on how to create a DOCSIS Conguration File).

The CM and CPE MAC addresses are located in two places on the IDH4 Series and on the packing slip,
see below. The CM MAC address may be labeled as the RF MAC address on some IDH4 Series units.

Identier label

746-257-B5-001, Rev. A1 (11/2013)

Cable Modem
and CPE MAC
Address Label

Fig. 3-1, Locations of MAC Address Labels

13

3.0 Network Conguration, continued

3.2 The DOCSIS Conguration File

A cable modem’s DOCSIS Conguration File is a type-length-value (TLV) le that contains important
operational parameters as dened by the DOCSIS standards. It provides certain settings for the cable
modem. In addition to standard entries, settings in the DOCSIS Conguration File should include the
modem’s community strings and if an upgrade is necessary, rmware upgrade parameters. Place the
conguration le in the TFTP root directory.

To build a DOCSIS Conguration File use a DOCSIS TLV editor program.

See Section 3.2.3, Sample DOCSIS Conguration File Entries.

NOTE:

The modem community strings should be set in the DOCSIS Conguration File. Failure to set
community strings will result in a less secure system. For automatically updating modem rmware
with the DOCSIS Conguration File, see Section 5.1, Upgrading IDH4 Series Modem Firmware.

3.2.1 Setting Modem Community Strings

Set the modem community strings with the DOCSIS Conguration File by including the following

SNMP parameters:

MIB Parameter Object ID Description Value

docsDevNmAccessIp 1.3.6.1.2.1.69.1.2.1.2.x The IP address (or subnet) of the

network management station

docsDevNmAccessIpMask 1.3.6.1.2.1.69.1.2.1.3.x The IP subnet mask of the network

management stations

docsDevNmAccessCommunity 1.3.6.1.2.1.69.1.2.1.4.x The community string matched to this

IP address net mask entry

docsDevNmAccessControl 1.3.6.1.2.1.69.1.2.1.5.x The level of access granted 1= none

docsDevNmAccessInterfaces 1.3.6.1.2.1.69.1.2.1.6.x Species the set of interfaces from

which requests from this NMS will be
accepted

docsDevNmAccessStatus 1.3.6.1.2.1.69.1.2.1.7.x Controls and reects the status of rows

in this table

Note: "X" denotes the index of the SNMP entry

e.g. 10.20.30.0

e.g. 255.255.255.0

alphanumeric string

2= read only
3= read/write

0x40 : Cable interface (typical)
0x80 : Ethernet interface
0xC0 or 0x00 : Both interfaces

4

Table 3-1, Modem Community String Parameters

14

746-257-B5-001, Rev. A1 (11/2013)

3.0 Network Conguration, continued

3.2 The DOCSIS Conguration File, continued

3.2.2 Setting SNMP Trap Destination Addresses

Set the SNMP Trap Destination Addresses via the DOCSIS Conguration File by including the

following SNMP parameters:

MIB Parameter Object ID Description Value

docsDevNmAccessIP 1.3.6.1.2.1.69.1.2.1.2.x IP address of trap destination, e.g. NMS

docsDevNmAccessIpMask 1.3.6.1.2.1.69.1.2.1.3.x Must be set to 255.255.255.255 per RFC

docsDevNmAccessCommunity 1.3.6.1.2.1.69.1.2.1.4.x Community string used by NMS to query

docsDevNmAccessControl 1.3.6.1.2.1.69.1.2.1.5.x Level of SNMP access to IDH4 Series

docsDevNmAccessInterfaces 1.3.6.1.2.1.69.1.2.1.6.x Species the set of interfaces from which

docsDevNmAccessStatus 1.3.6.1.2.1.69.1.2.1.7.x Controls and reects the status of rows

Note: "X" denotes the index of the SNMP entry

server

4639

transponder

from IP address specied in

docsDevNmAccessIpMask

requests from this NMS will be accepted

in this table

e.g. 10.20.30.40

255.255.255.255

alphanumeric string

4= Read/Only plus Trap
5= Read/Write plus Trap
6= Trap only, no SNMP access

0x40 : Cable interface (typical)
0x80 : Ethernet interface
0xC0 or 0x00 : Both interfaces

4

Table 3-2, Trap Destination Addresses

NOTE:

As an alternative to the docsDevNmAccessTable, SNMP Trap Destination Addresses may be set
through the IDH4 proprietary MIB atiMgmtSnmpTrapTable (OID: 1.3.6.1.4.1.926.1.3.1.1) using

a SNMP MIB Browser or as an entry in the Proprietary Conguration File (see Section 3.2.4,

Proprietary Conguration File 'idhdoc04.cfg').

746-257-B5-001, Rev. A1 (11/2013)

15

3.0 Network Conguration, continued

3.2 The DOCSIS Conguration File, continued

3.2.3 Sample DOCSIS Conguration File Entries

SNMP MIB Object (11) [Len=21]:docsDevNmAccessStatus.1/4
SNMP MIB Object (11) [Len=21]:docsDevNmAccesslp.1/10.56.21.0

A

B

SNMP MIB Object (11) [Len=21]:docsDevNmAccesslpMask.1/255.255.255.0
SNMP MIB Object (11) [Len=25]:docsDevNmAccessCommunity.1/"RW STRING"
SNMP MIB Object (11) [Len=25]:docsDevNmAccessInterfaces.1/"@"
SNMP MIB Object (11) [Len=21]:docsDevNmAccessControl.1/3

SNMP MIB Object (11) [Len=21]:docsDevNmAccessStatus.2/4
SNMP MIB Object (11) [Len=21]:docsDevNmAccesslp.2/10.20.30.40
SNMP MIB Object (11) [Len=21]:docsDevNmAccesslpMask.2/255.255.255.255
SNMP MIB Object (11) [Len=25]:docsDevNmAccessCommunity.2/"RW Trap string"
SNMP MIB Object (11) [Len=25]:docsDevNmAccessInterfaces.2/"@"
SNMP MIB Object (11) [Len=21]:docsDevNmAccessControl.2/5

C

D

E

Legend:

A

B

C

Software Upgrade Filename(9) [Len=24]:"ModemFirmwareFile.bin"
SNMP MIB Object (11) [Len=20]:docsDevSwAdminStatus.0/2

Software Upgrade TFTP Server (21) [Len=4]:10.56.48.15

Manufacturer Code Verication Certicate (32) [Len=254]: 30 82 03 1A 30 82...
Manufacturer Code Verication Certicate (32) [Len=254]: 04 0A 13 11 41 4D...
Manufacturer Code Verication Certicate (32) [Len=254]: 04 0C 30 0A 06 01...

Manufacturer Code Verication Certicate (32) [Len=36]: 11 A3 41 A6 A7 D9....

Fig. 3-2, Sample DOCSIS Conguration File

Sets Read-Write community string. Set the IP address, netmask and community string to t your system.

Sets the IP address of where the SNMP traps will be sent. This is typically set to match the IP address of the Network
Management's System Server.

Sets rmware download parameters.

16

Species the IP Address of the TFTP server used for upgrading rmware.

D

Sets Code Verication Certicate (CVC) for rmware upgrade security per the DOCSIS specication.

E

NOTE:

DOCSIS conguration les vary from system to system. Take into consideration your company's policies,
and test the le on a local system prior to widescale deployment.

746-257-B5-001, Rev. A1 (11/2013)

3.0 Network Conguration, continued

3.2 The DOCSIS Conguration File, continued

3.2.4 Proprietary Conguration File ‘idhdoc04.cfg’

The IDH4 Series will attempt to download a TLV-formatted le ‘idhdoc04.cfg’ from the modem’s

provisioning TFTP server at start up and every 24 hours thereafter. The idhdoc04.cfg proprietary

conguration le is optional and provides an alternative method to the modem’s DOCSIS conguration
le for deploying Alpha proprietary SNMP MIB parameters to eld-installed IDH4 Series transponders.

The idhdoc04.cfg le should be used if the following conditions are true:

1. Non-default settings, such as SNMP Trap Destination Addresses need to be distributed to all
IDH4 Series transponders.

2. The operator does not desire to place Alpha-proprietary parameters into the modem’s DOCSIS

conguration le.

NOTE:

The recommended method for setting the SNMP trap address(es) is through the modem DOCSIS

conguration le (see Section 3.2, The DOCSIS Conguration File). Alpha-proprietary parameters may
also be set through the modem’s DOCSIS conguration le, eliminating the need for the idhdoc04.cfg
proprietary conguration le.

To build the idhdoc04.cfg le, enter the desired SNMP OIDs and values from the Alpha MIB into a TLV
le as TLV type-11 entries using a TLV editor (see sample entries below). The IDH4 Series proprietary
conguration Setup le must be named “idhdoc04.cfg” and placed in the root directory of the TFTP
server. IDH4 settings are updated according to values dened in this le at start up and after every 24

hours of operation.

Sample idhdoc04.cfg Entries:
Network Access Control (3) [Len = 1]: 1

SNMP MIB Object (11) [Len = 24]: atiMgmtSnmpTrapAddress.1 / 10.20.30.40
SNMP MIB Object (11) [Len = 24]: atiMgmtSnmpTrapAddress.2 / 10.20.30.50
SNMP MIB Object (11) [Len = 23]: atiMgmtSysTamperPolarity.0 / 1

3.2.5 Changing Default idhdoc04.cfg Download Settings

By default the IDH4 Series will download the idhdoc04.cfg le from the provisioning TFTP server

every 24 hours. However, these settings may be adjusted per the tables below by placing the

respective SNMP varbinds into the modem’s DOCSIS conguration le.

Parameter Type Description Value

atiMgmtSysDownloadCongName

1.3.6.1.4.1.926.1.3.2.1.9.0

atiMgmtSysDownloadReCfgTime

1.3.6.1.4.1.926.1.3.2.1.13.0

Search

Order

Parameter Type Description Value

atiMgmtSysDownloadCongAddress

1

OID 1.3.6.1.4.1.926.1.3.2.1.10.0

docsDevServerCongTftpAddress

2

1.3.6.1.2.1.69.1.4.11.0

docsDevSwServerAddress

3

1.3.6.1.2.1.69.1.3.7.0

4 Software Upgrade Server IP Address

Alphanumeric String

Integer

IP Address

IP Address

IP Address

Overrides default
location

Default location (No
change necessary)

Set via DOCSIS

conguration le

Set via DOCSIS

conguration le

Name of proprietary

conguration le

Download interval for
idhdoc04.cfg (hours)

"idhdoc04.cfg"
(Default)

24 (Default)

0.0.0.0 (Default)

CM's TFTP
Server Address

Congurable

Congurable

746-257-B5-001, Rev. A1 (11/2013)

Table 3-3, Changing Default idhdoc04.cfg Download Settings

17

3.0 Network Conguration, continued

3.3 Setting Communication Options

Communications Settings may be changed through the Alpha MIB remotely using an SNMP MIB browser
or automatically by placing the SNMP parameters into the DOCSIS cong le.
See Section 6.0, Data Management for an explanation of the Alpha MIB.

NOTE:

Before setting options, verify UDP ports 37, 69, 161, 162 and TCP port 80 are not blocked.

SNMP Parameter Type Description Value

atiMgmtSnmpTrapOnNormal
OID: 1.3.6.1.4.1.926.1.3.1.5.1.0

atiMgmtSysDownloadReCfgTime
OID: 1.3.6.1.4.1.926.1.3.2.1.13.0

atiMgmtSysSnmpTimeout
OID: 1.3.6.1.4.1.926.1.3.1.5.3.0

atiMgmtSysHttpAccess
OID: 1.3.6.1.4.1.926.1.3.2.2.4.1.0

See Section 10.0, MIB Parameters for complete parameter denitions.

Integer Send SNMP trap when alarmed

Integer Download interval for IDH4 Series-

Integer Time IDH4 Series will wait before

Integer

condition returns to normal state

specic items in idhdoc04.cfg cong
le (hours)

reset if SNMP trafc is not detected

(minutes)

HTTP Web Server

1 = Disabled
2 = Enabled (Default)

24 (Default, in hours)

1440 (Default, in minutes)
Note: If set to zero, watchdog will be
disabled.

1 = Disabled
2 = Enabled (default)

Table 3-4, Transponder Communications Parameters

NOTE:

The IDH4 Series will inherit the cable modem community string settings provided by the DOCSIS

Conguration File.

18

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface

Overview

The IDH4 Series power supply transponder provides an embedded Web server interface to allow operations
personnel the ability to connect locally or remotely via TCP/IP over Ethernet with a laptop/computer to verify the

status of common data points and to congure various operating parameters.

4.1 Local Web Server Access

The IDH4 Series transponder’s Ethernet port (comparable to the Craft port on some transponder models)
will typically be used as a local connection point allowing the user to connect directly to the IDH4 Series

Web server interface to verify/congure common communication parameters and view power supply

status and battery values. The Ethernet port on the IDH4 Series is a fully functional standard Ethernet
port, capable of providing all the functionality of any standard Ethernet connection.

To access the IDH4 Series transponder Web server locally utilizing a Web browser, follow the procedure
outlined below:

1. Connect a standard Ethernet cable (CAT5) between the IDH4 Series transponder Ethernet port (ETH)
and a laptop or computer’s network interface port.

2. Launch a Web browser.

3. Enter the transponder's default IP address (192.168.100.1) into the Web browser’s address eld.

4. The transponder’s Web server home page will appear (Fig. 4-1). Note: For the IDH4 Series,

this may take up to 45 seconds when the transponder is initially powered up with no RF
connection.

5. Click on the Language menu to select a desired language for the text information on the Web page.
The language choices are English (default), Spanish, Portuguese, French and German.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-1, IDH4 Series Web Page

(data values shown for illustration purposes only)

19

4.0 Web Interface, continued

4.1 Local Web Server Access, continued

NOTE:

If you are unable to view the home page of the IDH4 Series using IP address 192.168.100.1, the network

conguration on the computer that is being used to connect to the IDH4 Series transponder may require a
temporary static IP address to be congured.

Use the following procedure to congure a static IP

address on a laptop or computer:

1. Click the Start button (lower left button on most
Windows® computers).

2. When the window pops up, click Control Panel
(usually about half the way down the second
column).

3. Click Network Connections.

4. Right-Click Local Area Connection.

5. Click the Properties button.

6. You will see a dialog box much like Fig. 4-2; scroll
down to the entry Internet Protocol (TCP/IP) and
then click on the Properties button.

7. The Internet Protocol (TCP/IP) Properties
dialog box will open (Fig. 4-3). Select Use
the following IP address. Enter the values
as shown (i.e. IP address 192.168.100.2
and Subnet mask 255.255.255.0). Record
the existing IP address and Subnet mask
in order to later return the computer to its
original state.

8. Click on the OK button and try to connect
to the IDH4 Series transponder once again
using 192.168.100.1 in your Web browser.

9. To restore network settings, repeat Steps 1
through 6.

Fig. 4-2, Local Area Connection

Properties Screen

20

Fig. 4-3, Internet Protocol (TCP/IP)

Properties Screen

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.1 Local Web Server Access, continued

Use the following procedure to congure a static IP

address on a laptop or computer with the Windows 7
operating system:

1. Click the Start button (lower left button on most
Windows® computers).

2. When the window pops up, click Control Panel
(usually about half the way down the second
column).

3. Click Network and Sharing Center.

4. Click Local Area Connection.

5. Click the Properties button.

6. You will see a dialog box much like Fig. 4-4; click

Internet Protocol (TCP/IPv4) and then click the
Properties button.

7. The Internet Protocol (TCP/IP) Properties
dialog box will open (Fig. 4-5). Select "Use
the following IP address". Enter the values
as shown (i.e. IP address 192.168.100.2
and Subnet mask 255.255.255.0). Record
the existing IP address and Subnet mask
in order to later return the computer to its
original state.

8. Click the OK button and try to connect to the
DSM3 Series transponder once again using

192.168.100.1 in the Web browser.

9. To restore network settings, repeat Steps 1
through 6.

Fig. 4-4, Local Area Connection

Properties Screen, Windows 7

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-5, Internet Protocol (TCP/IP)

Properties Screen, Windows 7

21

4.0 Web Interface, continued

4.2 Remote Web Server Access

To remotely access the IDH4 Series transponder Web server utilizing a Web browser, follow the
procedure outlined below:

NOTE:

For Web server (HTTP) access, port 80 must not be blocked.

1. Connect the laptop or computer’s network interface port to the company’s Ethernet network.

2. Open a Web browser.

3. Enter the IDH4 Series' designated IP address (e.g., 192.168.1.124) into the Web browser’s address

eld.

4. The IDH4 Series transponder’s Web server home page will appear (Fig. 4-4).

5. Click on the Language drop-down menu located on the top right of the page to select a desired
language for the text information on the Web page. The language choices are English (default),
Spanish, Portuguese, French and German

22

Fig. 4-6, Web Server Home Page

(data values shown for illustration purposes only)

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.3 Navigating the Web Page

Once the Web page has been successfully accessed, the operator is able to select a link on the header

bar and the page specic to the topic will open enabling real-time data to be observed.

See Fig. 4-7 for IDH4 Series navigation bar items.

TM

AlphaNet

DOCSIS Status Monitor

General Conguration

General HMS Alarms Advanced Settings Print

General Advanced Conguration APPS History Language Print

Commonly used
parameters for
quick diagnostics
of Power Supply,
Communications,
Batteries and
Generator.

Communications: Comprehensive
communications diagnostic parameters

Power Supply: Comprehensive Power

Supply conguration and congurable

parameters

Generator: Comprehensive Generator

conguration and diagnostic parameters

IO - Environment: Status and conguration

of tamper polarity and external I/O devices

HMS Alarms: Status of SCTE-HMS active
alarms, alarm history and alarm threshold
settings

The Web page content
will be displayed in the
selected language.

System Logs (requires AlphaApp card): Log

overview page provides snapshot of rst 5 entries

from each of the system logs.

Power Supply Events (requires AlphaApp card):

Records daily power supply system events.

Power Supply Conguration (requires

AlphaApp card): Records power supply system

conguration events, many of which are set during

the initial installation.

Battery Events (requires AlphaApp card):

Records battery conductance measurements and
manufacturing dates.

Cable Modem Log: Web page representation of
the DOCSIS modem event log.

(Requires AlphaApp card)

Overview: Provides AlphaApp card
version and status, plus Utility power
health information.

Battery Management: Congure

technician ID, battery conductance
measurements, battery model and
battery manufacturing dates for
runtime and battery life calculations.

Sends the contents
of the selected
Web page to the
computer’s default
printer.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-7, IDH4 Series Site Map

23

4.0 Web Interface, continued

4.3 Navigating the Web Page, continued

4.3.1 Web Interface Security Levels

Within the IDH4 Series transponder are two levels of function-specic security. General operation­related functions are set at Level 1 and conguration-related functions are set at Level 2.
Default User Name and Security Passwords are shown in the gure below.

IDH4 Series Web Page Security

OID Function Value

1.3.6.1.4.1.4413.2.2.2.1.1.3.3.0 Level 1 User Name Alpha

1.3.6.1.4.1.4413.2.2.2.1.1.3.4.0 Level 1 Security Password AlphaGet

1.3.6.1.4.1.4413.2.2.2.1.1.3.1.0 Level 2 User Name Alpha

1.3.6.1.4.1.4413.2.2.2.1.1.3.2.0 Level 2 Security Password AlphaSet

Web Page Function Security Level

General

Advanced Communications

Advanced Power Supply Congure/Save 2

Advanced Generator

Modem Log [Event Log] Reset Log 1

Advanced I/O

Apps Overview Congure/Save 2

Battery Management Congure/Save 2

System Name, System Contact, System Location,
Common Logical ID

Power Supply Self Test 1

Generator Self Test 1

Reset Transponder 1

Provisioning Mode - Single IP or Dual IP 2

Congure Static IP Address 2

Congure Proprietary Trap Addresses 2

Power Supply Self Test 1

Reset Output 1/2 2

Generator Self Test 1

Reset Latched Alarms 1

Tamper Switch Polarity 1

Enclosure Heater/Cooler Installed 1

1

24

Fig. 4-8, IDH4 Series Transponder Security Levels

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.4 Verifying Communication Parameters

Click the General menu of the web page to display common communication settings and values. Click
the Advanced Communication menu to view additional communication parameters.

Fig. 4-9, Communication Parameters

(data values shown for illustration purposes only)

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-10, Advanced Communication Parameters

(data values shown for illustration purposes only)

25

4.0 Web Interface, continued

4.5 Verifying Power Supply and Battery Parameters

The General tab of the Web page also displays the common power supply and battery parameter values.
Important parameters such as current alarm status, inverter status and tamper status can be quickly

veried on this page. Additional power supply parameters can be viewed and edited on the Power Supply
page located in the Advanced Conguration menu.

Fig. 4-11, Power Supply and Battery Parameters

(data values shown for illustration purposes only)

4.6 Remote Self Tests via the Web Page

Remote Self Tests on power supplies may be started and stopped via the IDH4 Series Web page. This
requires a Level 1 login. Refer to Section 4.3.1, Web Interface Security Levels for User Name and
Security Password.

To launch a remote Self Test, click on the Start Test button.

To stop a remote Self Test before the predened test duration, click on the Stop Test button.

26

Fig. 4-12, Location of Start Button for Self Test

(data values shown for illustration purposes only)

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.7 Viewing HMS Alarm Status via the Web Page

HMS alarm levels and currently reported states may be viewed by clicking on the HMS Alarms link on the

Advanced Conguration menu. An example is shown below. Parameter values cannot be edited on this

Web page. An SNMP MIB browser or status monitoring software may be used for such edits.

Refer to Table 6-3, Recommended Settings for IDH4 Series Analog Alarms for information regarding the scaling applied to the
indicated values.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-13, HMS Alarm Conguration

(data values shown for illustration purposes only)

27

4.0 Web Interface, continued

4.8 Setting the I/O Controller via the Web Page

Settings for the Tamper Switch and I/O Controller may be made by accessing the the I/O - Environment

page from the Advanced Conguration drop down list. The Tamper Switch polarity may be changed

by clicking on the preferred Tamper Switch polarity button. The I/O Controller section provides a user
interface to select the type of device that will be connected and monitored via the ENV connector of the
transponder. An example of such a device would be the battery heater mat controller.

Fig. 4-14, Advanced I/O Controller Status Screen

(data values shown for illustration purposes only)

28

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.9 Viewing and Conguring Power Supply Settings via the Web Page

Connected power supply parameters may be viewed by clicking on the Advanced Conguration heading,

and selecting Power Supplies from the drop down list. The power supply parameters with a box or a drop

down menu around the value can be edited for specic congurations. Power supply Self Tests may

be remotely started by clicking on the Start Test button. When prompted, refer to Section 4.3.1, Web
Interface Security Levels for the applicable User Name and Password.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-15, Advanced Power Supply Settings Screen

(data values shown for illustration purposes only)

29

4.0 Web Interface, continued

4.9 Viewing and Conguring Power Supply Settings via the Web Page, continued

30

Fig. 4-15, Advanced Power Supply Settings Screen, continued

(data values shown for illustration purposes only)

When the Battery Model is set to Other, the battery charging parameters such as charger voltages,
battery capacity, and temperature compensation can be customized, otherwise default values are
populated for the Alpha supported batteries. For systems wtih more than one power supply, the master
unit will override the charger parameter settings.

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.10 Viewing and Conguring Generator Settings via the Web Page

When a generator is connected to an IDH4X, the generator page listed in the Advanced Conguration

menu will populate a list of the various parameters and alarm statuses. Generator Self Tests may be
remotely started by clicking on the Start Test button. When prompted, refer to Section 4.3.1, Web
Interface Security Levels for User Name and Security Password.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-16, Advanced Generator Status Screen

(data values shown for illustration purposes only)

31

4.0 Web Interface, continued

4.11 Viewing AlphaApps Information via the Web Page

The status of the optional AlphaApp Card may be viewed by navigating to the AlphaApps selection on
the Apps menu of the IDH4 Series Web page. Status and rmware version are typical parameters listed
for this installed component of the power supply. A Congure/Save button is available for manually
setting the Application Clock. Refer to Section 4.3.1, Web Interface Security Levels for User Name and
Password.

The Utility section of the Web page displays current AC Line Status and Utility Performance Current
Status. The utility event monitor tracks typical power events such as outages, sags, surges, and
frequency in a tabular format for ease of viewing.

32

Fig. 4-17, AlphaApps and Utility Status Parameters

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.12 Battery Management

Technician ID, battery conductance measurements, battery model and battery manufacturing dates can
be manually entered via the Web page interface. Navigate to the Battery Management selection on the

Apps menu Web page to access the battery management details. A Congure/Save button is available
for the congurable settings on this page. Click the Congure button to enable the conguration/editing

mode, then click the Save button to save all the edits. Refer to Section 4.3.1, Web Interface Security
Levels for User Name and Password.

Fig. 4-18, Battery Management

746-257-B5-001, Rev. A1 (11/2013)

33

4.0 Web Interface, continued

4.12 Battery Management, continued

Click the drop down menu to view a selection of common battery models. If the installed battery model is
not listed for your particular conguration, then select Other for the model type.

Fig. 4-19, Battery Model Selection

34

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.13 Viewing Power Supply Event and Conguration Logs

Navigate to the History menu for viewing the power supply event and conguration logs. The System
Logs provide a snapshot of the ve most recent entries of the power supply event log and the power

supply conguration log. For a more comprehensive list, click on the link or select from the History menu
for the desired log le.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-20, System Log Overview

35

4.0 Web Interface, continued

4.13 Viewing Power Supply Event and Conguration Logs, continued

A Time Offset selection is available on each log table for selection of your current time offset from
Greenwich Mean Time (GMT). Select the time offset that best matches your location to enable the local
time in the log tables. Refer to Table 4-1 for a list of time zone offsets and relative locations.

GMT Offset Location Reference

+12 Auckland

+11 Magadan

+10 Sydney

+9.5 Adelaide

+9 Seoul

+8 Hong Kong

+7 Bangkok

+6.5 Yangon

+6 Astana

+5.5 Sri Lanka

+5 Islamabad

+4.5 Kabul

+4 Abu Dhabi

+3.5 Tehran

+3 Moscow

+2 Jerusalem

+1 Berlin

GMT

-1 Azores

-2 Mid-Atlantic

-3 Buenos Aires

-3.5 Newfoundland

-4 Santiago

-4.5 Caracas

-5 Eastern Time

-6 Central Time

-7 Mountain Time

-8 Pacic Time

-9 Alaska

-10 Hawaii

-11 Midway Is

-12 Eniwetok

London

36

Table 4-1, Time Offset Values and Location Reference (offset +/- GMT)

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.13 Viewing Power Supply Event and Conguration Logs, continued

The Power Supply event log contains events that occur in the normal course of daily power supply
operation such as IP address changes, inverter health, alarms, power outages, etc. The event log data
may be downloaded by clicking on the Save button or printed by clicking on the Print button.

NOTE:

The AlphaApps card stores up to 768 event log entries that can be reviewed in the CSV le. The Power

Supply Event Log Web page displays up to 512 event log entries. The event log entries are displayed
in groups of 50. Navigate to particular events by selecting one of the numbered entry links listed at the
bottom of the page.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-21, Power Supply Event Log

37

4.0 Web Interface, continued

4.13 Viewing Power Supply Event and Conguration Logs, continued

The Power Supply Conguration Log contains events that occur infrequently or only once such as

transponder conguration (rmware version), CM MAC address, Inverter Module serial number, etc. The
conguration log data may be downloaded by clicking on the Save button. The Conguration Log stores

up to 255 entries.

38

Fig. 4-22, Power Supply Conguration Log

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.14 Battery Event Log

The Battery Event Log can be accessed by navigating to the History menu. The Battery Event Log
contains the battery conductance measurements and battery manufacturing dates. The Battery Event Log
data may be downloaded by clicking on the Save button located at the top right of the page. The Battery
Event Log stores up to 1024 entries.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-23, Battery Event Log

39

4.0 Web Interface, continued

4.15 Viewing the Modem Event Log via the Web Page

The transponder's event log may be viewed using a Web browser. From the General ("home") page,
click on the History link, and select Cable Modem Log from the drop down list. The Cable Modem
Log displays the contents of the docsDevEventTable in an easy to read format. The log may be reset
by clicking on the RESET LOG button or the logged data may be downloaded by clicking on the Save
button, or be printed by clicking on the Print button.

Fig. 4-24, Modem Event Log Screen

(data values shown for illustration purposes only)

40

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.16 RF Constellation Page

Select the Tools menu to access the Constellation page. Click the Constellation menu item to view the
Constellation display for the DOCSIS channel. The page will automatically refresh until the updates
remaining counter reaches 0. Clicking the Run button restarts the automatic refresh, and clicking the Stop
button stops it.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-25, RF Constellation Page

41

4.0 Web Interface, continued

4.16 RF Constellation Page, continued

Controls:

• Run — Start the sampling of data by pushing the Run button. The unit will acquire 100 samples then

stop.

• Stop — Use the Stop button to end the sampling.

Downstream Data:

• Frequency — is the downstream frequency given in Hz.

• Power — is the downstream power given in dBmV.

• SNR / (RxMER) — this is the downstream signal quality. Modulation Error Ratio (SNR).

• EVM —Error Vector Magnitude calculated from MER.

• CER Interval — Codeword Error Rate (CER) refresh rate.

• Pre FEC CER — Codeword error rate (CER) BEFORE forward error correction is applied.

• Post FEC CER — Codeword error rate (CER) AFTER forward error correction is applied.

• Updates Remaining — this is the number of sample updates remaining for this session.

4.17 Constellation Data Interpretation

The usefulness of the QAM Constellation comes in the ability to recognize common shapes and

congurations within the map. Refer to the following table for examples.

Shape Focus Impairment Description

Individual cells
and entire QAM
constellation

Individual cells

Individual cells

Individual cells Gaussian Noise

Entire QAM
constellation

Entire QAM
constellation

Entire QAM
constellation

Normal

Low CNR and/or
Low MER

Coherent
Interference

Phase Noise QAM constellation consists of smeared, concentric, circular patterns.

Gain Compression

I-Q Imbalance in
the Modulator

Dots are centered in the individual QAM quadrants. The QAM
constellation has a uniform square shape.

Individual cells of QAM constellation contain a fuzzy and diffused pattern.

Individual cells of QAM constellation contain diffused hollow circles or
“doughnuts”. This indicates an interfering carrier and shows the effect of
not allowing the carrier to ever reach the proper point in the target range.

Individual cells contain a complete and fairly uniform smear up to all
decision boundaries, and is usually caused by improper system setup, too

many ampliers in a cascade, damaged/overheated hardware, and/or low

power.

QAM constellation looks uniformly square but the outside corners appear
to be “smashed” toward center of grid (compression in the RF plant).

Overall appearance of QAM constellation is rectangular rather than the
desired square shape (square inequality).

42

Entire QAM
constellation

Quadrature
Distortion

Overall appearance of QAM constellation has a twisted or skewed
parallelogram shape.

Table 4-2, Constellation Impairments

746-257-B5-001, Rev. A1 (11/2013)

4.0 Web Interface, continued

4.18 Microreections

Select the "Tools" menu to access the Microreections page. The CMTS Adaptive equalization must
be enabled for the active upstream channel for this page to display valid data. The Microreections

page provides information about impairments on the line and the approximate distance(s) of those
impairment(s). Placing the mouse pointer over each bar provides details about that particular reading.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 4-26, Microreections

43

5.0 Upgrading Firmware

5.1 Upgrading IDH4 Series Modem Firmware

The rmware is upgraded using standard DOCSIS methods as dened in RFC4639.

There are two ways to upgrade the modem’s rmware: By directly setting the appropriate MIB parameters

in the docsDevSoftware branch, or by including the appropriate SNMP parameters and values in the

modem’s DOCSIS Conguration File, stored on the TFTP server's root directory.

Both methods are explained below.

5.1.1 Identifying the Modem and Obtaining Firmware Files

The cable modem rmware in the IDH4 Series requires its own rmware and manufacturer's
Code Verication Certicate (CVC le).

Contact Alpha Technologies to obtain the latest rmware and manufacturer's CVC les.

5.1.2 Modem Firmware Upgrade SNMP Parameters

Parameter Type Value

docsDevSoftware
OID: 1.3.6.1.2.1.69.1.3

docsDevSwServer
OID: 1.3.6.1.2.1.69.1.3.1.0

docDevSwFilename
OID: 1.3.6.1.2.1.69.1.3.2.0

docsDevSwAdminStatus
OID: 1.3.6.1.2.1.69.1.3.3.0

docsDevSwOperStatus
OID: 1.3.6.1.2.1.69.1.3.4.0

docsDevSwCurrentVers
OID: 1.3.6.1.2.1.69.1.3.5.0

docsDevSwServerAddressType

1.3.6.1.2.1.69.1.3.6.0

docsDevSwServerAddress
OID: 1.3.6.1.2.1.69.1.3.7.0

Modem Firmware Upgrade SNMP Parameters

Object Heading None

IP Address, Read-write The IP address of the TFTP server from which the rmware will be

Octet String, Read-write Set to the lename of the rmware le. Example: [“rmwareImage.bin”]

Integer, Read-write 1 = Initiate upgrade (manual method)

Integer,
Read Only

Octet String,
Read Only

Integer, Read-write The type of address (IPv4, IPv6) of server used for upgrades

IP Address, Read-write The IP address of the server from which the rmware will be

downloaded

2 = Upgrade on next reboot (Cong File Method)
3 = Ignore update

1 = TFTP download is in progress
2 = Last upgrade was performed at reboot
3 = Last upgrade was initiated by setting docsDevSwAdminStatus to “1”
4 = Firmware upgrade failed
5 = Other

The current version of rmware installed in the modem

downloaded. A set of this object to an IPv4 address will result in also setting
the value of docsDevSwServer to that address. If this object is set to an
IPv6 address, docsDevSwServer is set to 0.0.0.0. If docsDevSwServer is
set, this object is also set to that value.

44

docsDevSwServerTransportProtocol

1.3.6.1.2.1.69.1.3.8.0

Table 5-1, Modem Firmware Upgrade SNMP Parameters

0:unknown
1:ipv4
2:ipv6
3:ipv4z
4:ipv6z
16:dns

Integer, Read Only The Transport protocol to be used for software upgrades:

1 = TFTP
2 = HTTP

746-257-B5-001, Rev. A1 (11/2013)

5.0 Upgrading Firmware, continued

5.1.3 Upgrading Manually by Setting SNMP Parameters

1. Acquire the rmware and CVC les for your IDH4 Series from Alpha Technologies.

2. Import the CVC into the modem’s DOCSIS Conguration File (to create a Conguration File,

see Section 3.2, The DOCSIS Conguration File).

3. Set the following MIB parameters using an SNMP MIB browser. For additional information
regarding the SNMP MIB parameters, refer to the table in Section 5.1.2, Modem Firmware

Upgrade SNMP Parameters.

Parameter Value

docsDevSwServer
OID: 1.3.6.1.2.1.69.1.3.1.0

docDevSwFilename
OID: 1.3.6.1.2.1.69.1.3.2.0

docsDevSwAdminStatus
OID: 1.3.6.1.2.1.69.1.3.3.0

Table 5-2, Setting SNMP MIB Parameters

IP Address of theTFTP server

Firmware lename

1

The rmware upgrade will begin immediately. Monitor the upgrade status with the
docsDevSwOperStatus MIB parameter, and verify the rmware version with the
docsDevSwCurrentVers MIB parameter (refer to Table 5-1). Once the rmware has been

upgraded, the modem will automatically run the new version.

5.1.4 Upgrading via the DOCSIS Conguration File

IDH4 Series rmware can be automatically upgraded using the DOCSIS Conguration File

by adding the following docsDevSoftware SNMP parameters and the manufacturer’s Code

Verication Certicate (CVC).

Parameter Value

docsDevSwServer
OID: 1.3.6.1.2.1.69.1.3.1.0

docsDevSwFilename
OID: 1.3.6.1.2.1.69.1.3.2.0

docsDevSwAdminStatus
OID: 1.3.6.1.2.1.69.1.3.3.0

Manufacturer CVC
TLV:32

IP Address of TFTP server

Firmware lename

2

The CVC le for the IDH4 Series (embed in the conguration le).

The rmware will be upgraded on the next reboot. Monitor the upgrade status with
the docsDevSwOperStatus MIB parameter, and verify the rmware version with the
docsDevSwCurrentVers MIB parameter (refer to Table 5-1). Once the rmware has been

upgraded, the modem will automatically run the new version.

746-257-B5-001, Rev. A1 (11/2013)

Table 5-3, Setting docsDevSoftware SNMP Parameters

45

6.0 Data Management

6.1 SCTE-HMS MIBs

The IDH4 Series remotely reports power supply data and alarms using the Simple Network Management

Protocol (SNMP) over the DOCSIS (Data Over Cable Service Interface Specication) communications

standard. The IDH4 Series typically reports into a centralized Network Management System (NMS)
through a standard collection of data access points referred to as the SCTE-HMS Management
Information Bases (MIBs). The NMS polls the IDH4 Series for power supply data with the option of having
the IDH4 Series send SNMP traps in the event that an alarm condition occurs. In addition to the SCTE­HMS MIBs, the IDH4 Series also supports the Alpha proprietary SNMP MIBs, which allows direct access
to the power supply as well as the ability to change transponder settings.

The following MIB (Management Information Base) les are required for the NMS or SNMP Manager to
collect data from the transponders. These les can be found on the Society of Cable Telecommunications
Engineers (SCTE) Web site www.scte.org. There are dependencies between MIB les so they should be

compiled in the order listed below:

Reference Number Description

ANSI/SCTE 36 2002R2007

(formerly HMS 028)

ANSI/SCTE 37 2010

(formerly HMS 072),

ANSI/SCTE 38-1 2009

(formerly HMS 026)

ANSI/SCTE 38-2 2005

(formerly HMS 023)

ANSI/SCTE 38-3 2008

(formerly HMS 024)

ANSI/SCTE 38-4 2006

(formerly HMS 027)

ANSI/SCTE 38-6 2006

(formerly HMS 033)

ANSI/SCTE 38-7 2008

(formerly HMS 050)

SCTE-ROOT Management Information Base (MIB) Denitions

Hybrid Fiber/Coax Outside Plant Status Monitoring

SCTE-HMS-ROOTS Management Information Base (MIB) Denition

Hybrid Fiber/Coax Outside Plant Status Monitoring

SCTE-HMS-PROPERTY-MIB Management Information Base (MIB) Denition

Hybrid Fiber/Coax Outside Plant Status Monitoring

SCTE-HMS-ALARMS-MIB Management Information Base (MIB) Denition

Hybrid Fiber/Coax Outside Plant Status Monitoring

SCTE-HMS-COMMON-MIB Management Information Base (MIB) Denition

Hybrid Fiber/Coax Outside Plant Status Monitoring

SCTE-HMS-PS-MIB Management Information Base (MIB) Denition

Hybrid Fiber/Coax Outside Plant Status Monitoring

SCTE-HMS-GEN-MIB Management Information Base (MIB) Denition

Hybrid Fiber/Coax Outside Plant Status Monitoring

SCTE-HMS-Transponder-Interface-Bus (TIB)-MIB Management Information Base (MIB) Denition

46

Table 6-1, SCTE-HMS MIB Files

746-257-B5-001, Rev. A1 (11/2013)

6.0 Data Management, continued

6.2 SCTE-HMS MIB Alarms

6.2.1 SCTE-HMS Congurable Alarms

The HMS discrete and analog alarms provide the capability to monitor and alarm various
power supply and environmental conditions and measurements. The alarms in the SCTE-

HMS propertyTable and the discretePropertyTable can be dened and set to provide a custom

monitoring system.

The following section provides an example and detailed information on how to set values and
enable or disable alarms in the MIB tables. For ease of reference they are in this sequence:

• An example of how to set a temperature alarm

• A table to help convert the desired reported alarm states to hexadecimal for setting the MIB

• Commonly monitored parameters and recommended values

Example:

The alarms for psTemperature below are set so that the normal temperature range is from
30°C to 45°C. If the temperature rises above 45°C, a casHI alarm will be sent to the alarmTable.
Anything over 50°C is considered a critical condition and will generate a casHIHI alarm. If the
temperature falls below the normal level of 30°C, casLO will be generated and if it continues to
drop below 0, a casLOLO will be generated. The temperature must rise above the LOLO limit plus
the deadband value of 3°C before the casLOLO alarm will change to a casLO. The alarmEnable

eld is set to 0F Hex to monitor and alarm for all conditions.

psTemperature

0F (hex)

Binary to Hex Conversions for Alarm Settings

Unused HiHi Hi Lo LoLo Hex Enabled Alarms

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

0 0 0 0 0 0 0 0 00 No Alarms
0 0 0 0 0 0 0 1 01 LoLo

0 0 0 0 0 0 1 0 02 Lo

0 0 0 0 0 0 1 1 03 Lo, LoLo

0 0 0 0 0 1 0 0 04 Hi

0 0 0 0 0 1 0 1 05 Hi, LoLo

0 0 0 0 0 1 1 0 06 Hi, Lo

0 0 0 0 0 1 1 1 07 Hi, Lo, LoLo

0 0 0 0 1 0 0 0 08 HiHi

0 0 0 0 1 0 0 1 09 HiHi, LoLo

0 0 0 0 1 0 1 0 0A HiHi, Lo

0 0 0 0 1 0 1 1 0B HiHi, Lo, LoLo

0 0 0 0 1 1 0 0 0C HiHi, Hi

0 0 0 0 1 1 0 1 0D HiHi, Hi, LoLo

0 0 0 0 1 1 1 0 0E HiHi, Hi, Lo

0 0 0 0 1 1 1 1 0F HiHi, Hi, Lo, LoLo

746-257-B5-001, Rev. A1 (11/2013)

Table 6-2, Binary to Hex Conversions for Alarm Settings

47

6.0 Data Management, continued

6.2.1 SCTE-HMS Congurable Alarms, continued

The following table displays the various analog alarms with common settings for the IDH4 Series
Transponder.

Analog Alarms and Common Settings

Analog Alarms Description

psTotalStringVoltage

psBatteryVoltage

psInputVoltage

psOutputVoltage

psPowerOut

psStringChargeCurrent

psStringFloat

psOutputCurrent

psTemperature -40 to +80 degrees C 0x0F Varies by site

Alarms for Optional Generator

GenVBatIgnition

genEnclosureTemperature

36V Scaled representation of the full

120V Scaled representation of the input

220V 0x0F

60V Scaled representation of the

90V 0x0F 7800 8200 9150 9300 200

15A 0x0C Disable Disable 1650 1720 20

18A 0x0C Disable Disable 1980 2060 20

22A 0x0C Disable Disable 2420 2530 40

24A 0x0C Disable Disable 2640 2750 40

battery string in 1/100 Volts units

Battery Voltage of individual
batteries, scaled 1/100 Volts units

line voltage in 1/100 Volts units

power supply output voltage in
1/100 Volts units

Representation of power supply
output power in 1W units

Battery string charge current,
scaled in 1/100 Amp units

Battery string oat charge current,

scaled in 1/100 Amp units

Scaled representation of the
generator's ignition battery in
1/100 Volts

Temperature inside generator's
enclosure in degrees C

Alarm

Enable

0x0F 3300 3500 4520 4570 50

0x0F 1050 1150 1530 1550 20

0x0F Varies by site. The XM3-HP will switch to standby

0x0F 5650 6000 6600 7000 200

0x00 It is recommended that psOutputCurrent be used

0x0C Disable Disable 1200 1250 20

0x0C Disable Disable 1200 1250 20

0x0F 1150 1200 1500 1550 20

0x09 -40 0 0 55 5

LOLO LO HI HIHI Deadband

at nominal +15% -20%

for output alarms.

48

Table 6-3, Recommended Settings for IDH4 Series Analog Alarms

746-257-B5-001, Rev. A1 (11/2013)

6.0 Data Management, continued

6.2.1 SCTE-HMS Congurable Alarms, continued

Discrete Alarms Description Setting

psInverterStatus (1) Inverter OFF Disable

psInverterStatus (2) Inverter running due to loss of AC Line voltage discreteMinor

psInverterStatus (3) Self Test initiated locally Disable

psInverterStatus (4) Self Test initiated remotely Disable

psInverterStatus (5) Last Self Test failed discreteMajor

psMajorAlarm (1) No Alarm Disable

psMajorAlarm (2) Alarm discreteMajor

psMinorAlarm (1) No Alarm Disable

psMinorAlarm (2) Alarm discreteMinor

psTamper (1) Closed Disable

psTamper (2) Open discreteMajor

psInputVoltagePresence (1) AC Line Voltage Lost Disable

psInputVoltagePresence (2) AC Line Voltage Present Disable

tibControlMode (1) Device will respond to commands Disable

tibControlMode (2) Device is under local control Disable

tibControlMode (3) Remote device is not responding discreteMajor

Discrete Alarms for Optional Generator

genGeneratorStatus (1) Generator Off Disable

genGeneratorStatus (2) Generator Running (Test) discreteMinor

genGeneratorStatus (3) Generator Running discreteMajor

genGeneratorStatus (4) Generator Fail discreteMajor

genGasHazard (1) No Alarm Disable

genGasHazard (2) The concentration of hydrocarbon fuel in the generator enclosure has exceeded safe

limits. Generator operation is suspended. The alarm is cleared when the sensor reports
safe conditions, and the alarm is reset via the resetLatchedAlarms(3) command found in
the genEquipmentControl MIB point..

genWaterIntrusion (1) No Alarm Disable

genWaterIntrusion (2) Water level within the generator or fuel enclosure has exceeded safe limits for generator

operation. Generator operation is suspended while this alarm is active. The alarm resets
when the water returns to a safe level.

genPadShear (1) No Alarm Disable

genPadShear (2) Indicates that the generator or fuel enclosure has shifted from its mounting position.

Generator operation is suspended. The alarm resets when the unit is returned to its
original position.

genEnclosureDoor (1) No Alarm Disable

genEnclosureDoor (2) Generator and/or auxiliary fuel enclosure door is open discreteMajor

genCharger (1) No Alarm Disable

genCharger (2) Ignition battery charger is not operating correctly discreteMajor

genFuel (1) No Alarm Disable

genFuel (2) Indicates the engine's fuel supply is insufcient for extended operation. Alarm resets

when fuel is replenished.

genOil (1) No Alarm Disable

genOil (2) Indicates the engine's oil is inadequate for safe operation. Alarm resets when the

condition returns to normal.

genMinorAlarm (1) No Alarm Disable

genMinorAlarm (2) The generator is indicating a minor alarm. The generator requires attention, but does not

require an immediate visit to the site.

genMajorAlarm (1) No Alarm Disable

genMajorAlarm (2) The generator is indicating a major alarm. The generator requires immediate attention. discreteMajor

discreteMajor

discreteMajor

discreteMajor

discreteMajor

discreteMajor

discreteMinor

746-257-B5-001, Rev. A1 (11/2013)

Table 6-4, Recommended Settings for Discrete Alarms

49

6.0 Data Management, continued

6.2.2 SNMP Traps

Use of SNMP Traps allow the network manager to set conditions (alarms) under which the device (or

devices) autonomously report to the headend the existence of the pre-congured event. The type of event

determines the level of action to be taken.

1. Verify the IP address of the trap destination server(s) has been congured.

If the trap destination server requires conguration, refer to Section 3.2.2, Setting SNMP Trap

Destination Addresses for instructions.

2. Alarms must be congured. SNMP alarm traps sent by the transponder are formatted according
to the SCTE-HMS-ALARM-MIB specication with the following information included:

SNMP Trap community string:

commonTrapCommunityString, OID 1.3.6.1.4.1.5591.1.3.1.11.0

Default value is "public"

Example Alarm Trap

The example below is a psTamper alarm trap indicating a discreteMinor alarm: Tamper is open.
Data from the raw trap will appear as shown below. Refer to Table 6-5 for denitions of the
varbinds.

Frame 441 (230 bytes ib wire, 230 bytes captured)
Ethernet II, Src: 192.168.1.77 (00:90:EA:A0:01:4E), Dst: 3com_0d:1d:d4 (00:10:5a:0dL1d:d4)
Internet Protocol, Src Port: 62481 (62481), Dst Port: snmptrap (162)
Simple Network Management Protocol
Version: 1 (0)
Community: PUBLIC
PDU type: TRAP-V1 (4)
Enterprise: 1.3.6.1.4.1.5591.1 (SNMPv2-SMI::enterprises.5591.1)
Agent address: 0.0.0.0 (0.0.0.0)
Trap type: ENTERPRISE SPECIFIC (6)

Specic trap type: 1

Timestamp: 2358751

Object identier 1: 1.3.6.1.4.1.5591.1.3.2.7.0 (SNMPv2-SMI::enterprises.5591.1.3.2.7.0)

Value: Hex-STRING: 00 90 EA A0 0B 82

Object identier 2: 1.3.6.1.4.1.5591.1.3.1.1.0 (SNMPv2-SMI::enterprises.5591.1.3.2.1.0)

Value STRING: “123 Example Ave.”

Object identier 3: 1.3.6.1.4.1.5591.1.2.3.1.2.1 (SNMPv2-SMI::enterprises.5591.1.2.3.1.2.1)

Value: Hex-STRING: 00 00 00 76 07 10 06 0D 2B 06 01 04 01 AB 57 01 04 02 01 1B 01 02 01 02

Object identier 4: 1.3.6.1.4.1.5591.1.4.2.1.27.1 (SNMPv2-SMI::enterprises.5591.1.3.2.1.0)

Value: INTEGER: 2

Object identier 5: 1.3.6.1.4.1.5591.1.1.2.1.2 (SNMPv2-SMI::enterprises.5591.1..1.2.1.2)

Value: INTEGER: 7

Fig. 6-1, Sample Raw SNMP Alarm Trap

When viewed through a third-party trap receiver, the translated varbinds and data values will be
displayed in a format similar to the sample below:

50

Bindings (5)
Binding #1: commonPhysAddress.0 *** (octets) 00:90.EA.A0.01.4E (hex)
Binding #2: commonLogicalID.0 *** (octets) (123 Example Ave.)
Binding #3: alarmLogInformation.1 *** (octets) 00.00.00.76.07.10.06.0D.2B.06.01.04.01.AB.57.01.04.02.01.1B.01.02.01.02 (hex)
Binding #4: psTamper.1 *** (int32) open (2)
Binding #5: currentAlarmAlarmState *** (int32) caasDiscreteMinor(7)

Fig. 6-2, Sample Translated SNMP Alarm Trap

746-257-B5-001, Rev. A1 (11/2013)

6.0 Data Management, continued

6.2.2 SNMP Alarm Traps, continued

Varbind Explanation

Binding #1
commonPhysAddress
OID: 1.3.6.1.4.1.5591.1.3.2.7.0

Binding #2
commonLogicalID
OID: 1.3.6.1.4.1.5591.1.3.1.1.0

Binding #3
alarmLogInformation
OID: 1.3.6.1.4.1.5591.1.2.3.1.2.1

Binding #4
Alarmed Parameter OID/Value
OID:

1.3.6.1.4.1.5591.1.4.2.1.27.1

Binding #5
Alarm Location/Type
OID: 1.3.6.1.4.1.5591.1.1.2.1.2

MAC address of the transponder

Optional user-congurable parameter that is often used to provide a unique logical name, or even

the physical address of where the transponder is installed.

This varbind was designed by the SCTE-HMS committee with the intention of being used by

sophisticated trap interpreters. The information is “coded” within the octet strings:
Octet 1-4: POSIX Time of alarm occurrence (most signicant byte rst)

Octet 5: Alarm Type (See description below)
Octet 6: Contents of commonNeStatus immediately after alarm occurred

Octet 7-m: Alarm Object Identier (BER encoded)

Octet n-z: Alarm value (BER encoded)
Most trap interpreters cannot decode this message, which is why varbinds 4 and 5 were added that
provide the same information in a more useable format.

This eld provides the varbind of the parameter that is alarming along with the value of that

parameter. This is the same information encoded in varbind #3 Octets 7 through Z.
In the example above the value would be:
OID: 1.3.6.1.4.1.5591.1.4.2.1.27.1.0 (psTamper)
Value: 2 (Open)

This is the information from varbind #3 Octet 5 above. The alarm location will always be the
SCTE-HMS currentAlarmAlarmState and the type will be determined based on how the alarm was

congured in the SCTE-HMS PropertyIdent MIB tables.

OID 1.3.6.1.4.1.5591.1.1.2.1.2.0 (currentAlarmAlarmState)

Type: 1-7 based on SCTE denitions:

1 NOMINAL
2 HIHI
3 HI
4 LO
5 LOLO
6 Discrete Major
7 Discrete Minor

The Type will be determined by how the alarm is congured in the SCTE-HMS PropertyIdent MIB,
whether it is a Discrete or Analog alarm and the level of alarm dened for that state.

Table 6-5, SNMP Alarm Trap Varbinds and Explanations

Trap on Normal

The IDH4 Series has the capability of sending a “return to normal” trap once an alarmed condition

returns to a normal state. This feature is enabled by default, but can be disabled by setting the
"TRAP ON NORMAL" parameter in the the MIB point atiMgmtSnmpTrapOnNormal to a value of "2".
The contents of this trap message will be identical to the SNMP Alarm traps, but the value of the

Alarm "Type" dened in the 5th varbind will be "1" (NOMINAL).

SCTE-HMS Warm-Start Trap

In addition to the SNMP alarm traps, the IDH4 Series will also send an SCTE-HMS warm-start trap

when it is initialized. Some SNMP monitoring software requires this trap for auto-identication of the

transponder. The format of this trap will be similar to the alarm trap, but the only information sent
will be:

commonTrapCommunityString, OID 1.3.6.1.4.1.5591.1.3.1.11.0

commonPhyAddress, OID, 1.3.6.1.4.1.5591.1.3.2.7

commonLogicalID, OID 1.3.6.1.4.1.5591.1.3.1.1.0

SCTE-HMS Cold-Start Trap

An SNMP-HMS cold-start trap will be generated by the IDH4 Series anytime it initializes with a

new rmware version. In addition, a cold-start trap is sent whenever the IDH4 conguration has

changed. If any parameter in the HMS PROPERTY table has changed since the last reset, a
cold-start trap will be sent upon the next reset.

746-257-B5-001, Rev. A1 (11/2013)

51

6.0 Data Management, continued

6.2.3 General Power Supply Alarms

The Intelligent CableUPS detects a wide array of alarms and displays the type of active alarm in the
Smart Display screen and the severity of alarm (e.g., Major/Minor) by means of the Inverter Module LEDs.

General power supply alarms are passed directly from the power supply to the transponder without

specic denition and are classied in the HMS MIB table as psMinorAlarm and psMajorAlarm. There

are a number of problems that can generate these alarms and the exact nature of the situation is not

specied. Minor and Major alarms are dened by the SCTE standards committee as follows:

psMajor

“Service has been dropped or a service interruption is imminent. Indicates that an immediate truck roll is
appropriate.” Several psMajor alarms are latching, meaning that the alarm won’t clear until the problem is
xed and after a successful completion of a Self Test. A Self Test is the preferred method of verifying the

resolution of the alarm condition as cycling the power has the potential of masking the problem and not
indicating the actual state of the system.

psMinor

“A non-service affecting condition has occurred and should be monitored.”

The following table lists the psMajor and psMinor alarm denitions for the XM3-HP power supply.

Active Alarm Alarm type Alarm Category Probable Cause of Alarm Corrective action

SELF TEST FAIL Major PWR

LINE ISOLATION RELAY Major PWR

OUTPUT FAIL Major PWR

OUTPUT OVERLOAD Major PWR The output is overloaded or shorted.

OUTPUT 1 TRIPPED Major PWR

OUTPUT 2 TRIPPED

CHARGER FAILURE Major PWR

INVERTER TEMP Major PWR

CONFIG ERROR Major PWR

Major PWR Output 2 AlphaDOC hardware protection

Output voltage failed or batteries less than

1.85V/C during Self Test.

Line isolation has failed and Inverter
operations are suspended.

The AC output has failed due to a bad Inverter
or transformer.

Output 1 AlphaDOC hardware protection
mode is engaged and overloaded.

mode is engaged and overloaded.

Charger has failed to shut down; possible
battery over temperature condition exists.

Inverter heat sink has exceeded set
temperature. (Stand-by operations suspended
until temperature drops to a safe level.)

The power supply is improperly congured

and operation is suspended until error is
corrected.

1. Check Batteries

2. Check Inverter

1. Replace Power Supply as soon as possble

1. Check Conguration

2. Replace Inverter

3. Replace Power Supply

1. Remove Short Circuit

2. Reduce Output Load

3. Replace Power Supply

1. Reduce Output Load

2. Check AlphaDOC setting

1. Reduce Output Load

2. Check AlphaDOC Setting

1. Re-seat Inverter

2. Perform Self Test

3. Replace Inverter

1. Check Ventilation

2. Replace Inverter

1. Check Inverter Module

52

INPUT FAIL Minor PWR Utility AC input has failed.

INPUT CURRENT LIMIT Major PWR

AC Input current exceeds threshold setting.

Table 6-6, Power Alarms: Classications, Causes and Corrections

1. Check AC Input

2. Restore AC Input

3. Connect Generator

1. Reduce Output Load

2. Check Input Current Limit Setting

746-257-B5-001, Rev. A1 (11/2013)

6.0 Data Management, continued

6.2.3 General Power Supply Alarms, continued

Active Alarm Alarm type Alarm Category Probable Cause of Alarm Corrective action Standby Disabled

INPUT OVER CURR /
INPUT CURRENT LIMIT

Minor PWR AC Input current exceeds threshold setting.

1. Reduce Output Load

2. Check Input Current Limit Setting

NO

SURGE MOV FAIL Minor PWR

ALPHADOC OPTION Minor PWR I2C has failed between XM3-HP and DOC.

INVERTER ENABLE Minor PWR System controller has disabled the Inver ter. 1. Check inverter YES

CHARGER ENABLE Minor PWR System controller has disabled the charger. 1. Check charger NO

APP OPTION Minor PWR I2C has failed between XM3 -HP and APP.

INV EEPROM ERROR Minor PWR

HW COMPATIBILITY Minor PWR

PDB EEPROM ERROR Minor PWR

The MOV board surge protection has failed and needs
to be replaced.

There has been an error reading the EEProm on the
inverter board.

There is a hardware incompatiblity between the Main
micro board and the inverter board.

There has been an error reading the EEProm on the
PDB.

1. Replace MOV board NO

1. Check ribbon cable

2. Replace DOC

1. Check ribbon cable

2. Replace APP

1. Replace inverter NO

1. Check Micro Board

2. Check Inverter Brd

1. Replace power supply NO

NO

NO

NO

Table 6-6, Power Alarms: Classications, Causes and Corrections, continued

746-257-B5-001, Rev. A1 (11/2013)

53

6.0 Data Management, continued

6.2.4 Battery Alarms

The Intelligent CableUPS detects a wide array of battery alarms and displays the type of active alarm in
the Smart Display screen and the severity of alarm (e.g., Major/Minor) by means of the Inverter Module
LEDs.

Active Alarm Alarm type Alarm Category Probable Cause of Alarm Corrective action Standby Disabled

NO BATTERIES Major BATT

LOW BATT VOLTS Major BATT Battery voltages below 1.833V/cell

HIGH BATT VOLTS Major BATT Battery voltages above 4.5V over target charger voltage

BATTERY EOD Major BAT T Batter ies dropped below the low voltage shutdown level 1. Low Battery Disconnect YES

BATTERY FAIL Major B ATT Charge current > 5.0A for 7 days while in oat mode

BATT TEMP PROBE Minor BATT Precision Temperature Sensor (PTS) failed or is not installed.

REFRESH/BATT REFRESH ALARM Minor BATT Battery Temperature Exceeded 60°C

SAG OPTION Minor B ATT I2C has failed between XM3-HP and SAG

SAG DELTA MEAN Minor BAT T Battery voltage is either too high or low from mean

SAG RELAY STUCK Minor BAT T Relay has stuck or 36V or 0V wire is no longer connected

STR X MISWIRED Minor B ATT Battery wires are not connected properly

SAG NOT CALIBRAT Minor BATT Calibration data is not or is no longer available 1. Replace SAG NO

X BAL STAGE Minor B ATT

SAG NO HARNESS Minor BATT Battery wires are not connected properly

Detected the absence of batteries (alarm inactive when
battery capacity or number of battery strings is set to 0).

Stage 0 and 1 are normal. Stage 2 shows that the batteries
are not of similar capacity. Stage 3- 5 trigger check battery
alarm to show that there is a major capacity imbalance

1. Check Batt Breaker

2. Check Connections

3. Check Battery Fuse

1. Check AC Input

2. Restore AC Input

3. Connect Generator

1. Check Batteries

2. Replace Inverter

1. Check Batteries

2. Replace Batteries

1. Check Connection

2. Replace Sensor

1. Check Charger Settings

2. Check Batteries

3. Check Battery Temperature

1. Check Ribbon Cable

2. Replace SAG

1. Check Batteries

2. Replace Batteries

1. Check SAG Bat

2. Check SAG Wires Unit

3. Replace SAG

1. Check SAG Wires Bat

2. Check SAG Wires Unit

3. Replace SAG Wires

1. Check Batteries

2. Replace Batteries

1. Check SAG Wires Bat

2. Check SAG Wires Unit

3. Replace SAG Wires

YES

NO

NO

NO

NO

NO

NO

NO

NO

NO

NO

NO

54

Table 6-7, Battery Alarms: Classications, Causes and Corrections

NOTE:

The cause of a psMajor or psMinor alarm can be determined by checking the Discretes table in the Alpha MIB

or by viewing the Web page. The cause will have the value of “ALARM.”

NOTE:

When in alarm, the IDH4 General and Advanced Power Supply Web pages will display the cause of active
power supply alarms next to the parameters Major Alarm and Minor Alarm.

Fig. 6-3, IDH4 Series Alarms on General Web Page

746-257-B5-001, Rev. A1 (11/2013)

6.0 Data Management, continued

6.3 The Alpha MIBs

Accompanying the release of the IDH4 Series are new MIB les. These are backward-compatible with

the existing Alpha Technologies DOCSIS transponders. These MIBs are available by contacting Alpha
Technical Support or from the Alpha website. A complete listing is shown below:

ATI-BB-SYS-APPS-MIB.my

ATI-BB-SYS-LOGS-MIB.my

ATI-BB-SYS-VIEW-MIB.my

ATI-MANAGEMENT-MIB.my

ATI-MGMT-SNMP-MIB.my

ATI-MGMT-SYS-ACCESS-MIB.my

ATI-MGMT-SYS-DOWNLOAD-MIB.my

ATI-MGMT-SYS-GENRL-CTRL-MIB.my

ATI-MGMT-SYS-GENRL-INFO-MIB.my

ATI-MGMT-SYS-IO-MIB.my

ATI-MGMT-SYS-MIB.my

ATI-MGMT-SYS-NV-DEFAULTS.my

ATI-MGMT-SYS-PHONEHOME-MIB.my

ATI-MGMT-SYS-SERVERS-MIB.my

ATI-MGMT-SYS-TEMP-MGR-MIB.my

ATI-MPSPS-MIB.my

ATI-PKT-CABLE-UPS-MIB.my

ATI-PRODUCT-PLATFORMS-MIB.my

ATI-ROOT-MIB.my

ATI-TABLES-MIB.my

ATL-ROOT-MIB.my

MIB browsers such as MG-Soft (www.mg-soft.com) require these MIBs to be compiled into the browser
for the branches and parameters to be ordered and displayed properly. Refer to your MIB browser’s

documentation for instructions on compiling MIB les.

The following MIB les may be required (see http://www.simpleWeb.org) to be compiled into the MIB
browser prior to the Alpha MIB les:

RFC-1212

RFC-1215

RFC1155-SMI

SNMPv2-MIB

SNMPv2-TC

Additionally, there are four MIBs from Broadcom that are necessary to support the new features of the
IDH4 Series. They are:

BRCM-CABLEDATA-MGMT.my

BRCM-CABLEDATA-SMI.my

BRCM-HTTP-MGMT.my

BRCM-TELNET-MGMT.my

746-257-B5-001, Rev. A1 (11/2013)

55

6.0 Data Management, continued

6.3 The Alpha MIBs, continued

The Alpha MIB is dened within the enterprises branch of the MIB tree starting at 1.3.6.1.4.1.926 and is

organized as shown in the overview below:

MIB Tree

ccit

iso (1)

org (1.3)

dod (1.3.6)

internet (1.3.6.1)

directory (1.3.6.1.1)

mgmt (1.3.6.1.2)

experimental (1.3.6.1.3)

private (1.3.6.1.4)

enterprises (1.3.6.1.4.1)

atl(1.3.6.1.4.1.926)

alphaTechInc(1.3.6.1.4.1.926.1)

atiLegacyReserved01(1.3.6.1.4.1.926.1.1)

atiTables (1.3.6.1.4.1.926.1.2)

atiManagement (1.3.6.1.4.1.926.1.3)

atiMgntSnmp (1.3.6.1.4.1.926.1.3.1)

atimgntSnmpTrapTable(1.3.6.1.4.1.926.1.3.1.1)

atimgntSnmpAccessTable(1.3.6.1.4.1.926.1.3.1.2)

atimgntSnmpAccess(1.3.6.1.4.1.926.1.3.1.3)

atimgntSnmpCommunities(1.3.6.1.4.1.926.1.3.1.4)

atimgntSnmpControls(1.3.6.1.4.1.926.1.3.1.5)

atiMgntSys (1.3.6.1.4.1.926.1.3.2)

atiMgmtSysDownload (1.3.6.1.4.1.926.1.3.2.1)

atiMgmtSysAccess (1.3.6.1.4.1.926.1.3.2.2)

atiMgmtSysServers (1.3.6.1.4.1.926.1.3.2.3)

atiMgmtSysTempMgr (1.3.6.1.4.1.926.1.3.2.4)

atiMgmtSysPhoneHome (1.3.6.1.4.1.926.1.3.2.5)

atiMgmtSysGnrlControls (1.3.6.1.4.1.926.1.3.2.6)

atiMgmtSysGnrlInfo (1.3.6.1.4.1.926.1.3.2.7)

atiMgmtSysIO (1.3.6.1.4.1.926.1.3.2.8)

atiMgmtSysNvDefaults (1.3.6.1.4.1.926.1.3.2.9)

atiProductPlatforms (1.3.6.1.4.1.926.1.4)

atiBroadbandUPS (1.3.6.1.4.1.926.1.4.1)

atiBBSysView (1.3.6.1.4.1.926.1.4.1.1)

atiBBSysLogs (1.3.6.1.4.1.926.1.4.1.2)

atiBBSysApps (1.3.6.1.4.1.926.1.4.1.3)

56

Table 6-8, Alpha MIB Hierarchy

746-257-B5-001, Rev. A1 (11/2013)

6.0 Data Management, continued

6.3 The Alpha MIBs, continued

6.3.1 The Alpha MIB Structure

Measurements and settings for the power supply, generator, batteries and transponder are
accessed using Simple Network Management Protocol (SNMP) through the Alpha Management

Information Base (MIB) les.

The Alpha MIB is dened within the enterprise branch of the MIB tree starting at 1.3.6.1.4.1.926

and is organized into the following branches:

Alpha CIB Tables – atiTables (1.3.6.1.4.1.926.1.2.1)

Power supply, generator, battery and transponder data and settings are located in the CIB Tables branch (atiCibTables). The tables are sorted into the
following categories:

1. Discretes - XM3-HP major alarms & installed XM3-HP options.

2. Analogs - Voltages, currents, frequencies, temperatures.

3. Counters - Batteries per string, number of strings, XM3-HP Self Test schedule, device address, total run time and conguration settings.

4. Version - Device version information.

Alpha Management – atiManagement (1.3.6.1.4.1.926.1.3)

Advanced transponder settings are located in the Alpha management branch (atiManagement) and the settings are split between SNMP and system­related settings.

1. SNMP Management – atiMgntSnmp (1.3.6.1.4.1.926.1.3.1)
SNMP Trap tables, SNMP access, Community Strings and SNMP Trap controls.

1.1 SNMP Trap Table - Table of SNMP trap addresses.

1.2 SNMP Access Table – Table of SNMP access addresses.

1.3 SNMP Access – Device accessibility via SNMPv1 & SNMPv2 (Dual-IP only).

1.4 CPE Mode – Enable/disable Dual IP and Static IP settings.

1.5 Community Strings – Get, set and trap community strings (Dual-IP only).

1.6 SNMP Trap controls – Trap on normal, send count, SNMP timeout.

2. System Management – atiMgmtSys (1.3.6.1.4.1.926.1.3.2)
Download, Web server, SNTP server IP addresses, enclosure environmental controller, general controls (tamper polarity).

2.1 Download – Transponder Proprietary Conguration File settings.

2.2 System Access – Enable/disable Web Page

2.3 System Servers – Simple Network Time Protocol server (SNTP) IP address.

2.4 Temperature Manager – Battery heater mat or cooler settings.

2.5 Phone Home – IP address and timer settings.

2.6 General Controls – Tamper switch polarity and internal bus data size.

2.7 General Info – Base conguration of the device. i.e. IDH4x, IDH4 Series, IDH4L.

2.8 System IO – Conguration and status of Environmental Controller

2.9 Non-volatile Memory Defaults – Factory and custom defaults.

Alpha Product Platforms – atiProductPlatforms (1.3.6.1.4.1.926.1.4)

System power supply parameters are located the Alpha Product Platforms branch (atiProductPlatforms).

1. Broadband UPS

System View – Self Test, alarms, scalars, and counters reported by the host device.

1.1 Selects – Start/stop and control of the System Control Manager.

1.2 Alarms – Status of major and minor alarm, Self Test, temperature probe and input power.

1.3 Scalars – Power supply input voltage, frequency and current. Battery voltage and temperature. Charger settings.

1.4 Counters – Self Test and inverter counters.

2. System Logs – atiProductPlatforms (1.3.6.1.4.1.926.1.4.1.2)

2.1 Events Table

2.2 Cong Table

2.3 Perform Table

3. System Apps – atiProductPlatforms (1.3.6.1.4.1.926.1.4.1.3)

3.1 Power Supply Health

3.2 Battery Status

3.3 Utility Quality

Refer to Section 10.0 MIB Parameters for further details regarding the Alpha MIBs.

746-257-B5-001, Rev. A1 (11/2013)

Table 6-9, Alpha MIB Structure

57

7.0 Installation

7.1 Verifying Power Supply Device Address

Before installing the hardware, provision the DHCP server with the cable modem’s CM MAC address.

This allows the installation to be veried while the technician is on-site, eliminating the need for a second

visit if there are problems with the installation.

WARNING!

To reduce the risk of electric shock, completely remove the Inverter Module from the power

supply prior to installation. For eld installation, use a service power supply to avoid losing

power to the load.

CAUTION!

The IDH4 Series is static sensitive. An ESD wrist strap should be worn when installing the
transponder.

Before removing the Inverter Module, verify the power supply device address is correct.

The power supply device address must not be set to zero and no two power supplies monitored by
a single IDH4 Series can have the same address. The power supply must have a unique address to

communicate with a system controller. The system controller uses the address as an identier to query
the power supply for information. Each power supply on the same communications bus must be identied

with a value between 1 and 5. To verify the power supply’s address do the following:

EDIT USING ↑ ↓ <ENTR>

DEVICE ADDRESS

1

ESC

Smart Display Screen

1. Press the PWR key on the Inverter Module twice to access the PWR CNFG Menu.

2. Press the Down or Up key until DEVICE ADDRESS is displayed.

3. If the address is correct (in the range of 1 to 5), skip to Step 7.

4. To change the address, press the Enter key to enter the Edit mode.

5. Press the Up or Down keys until the desired address (1 to 5) is displayed. Remember, each power
supply monitored by a single transponder must have a unique address; this may require accessing
the menu systems of the additional power supplies and adjusting as applicable.

6. Press the Enter key to load the new address.

7. Press ESC two times to return to the OPERATION NORMAL screen.

58

746-257-B5-001, Rev. A1 (11/2013)

7.0 Installation, continued

7.2 Installation / Replacement Procedure in XM3-HP Power Supplies

If the XM3-HP CableUPS has been shipped without a IDH4 Series module, or the existing module
requires removal and replacement, do so via the the following procedure:

1. Switch OFF the Inverter Module battery breaker.

NOTE:

With the battery breaker in the OFF position, the power supply will not go into inverter mode.

2. Unplug all Inverter Module connections (e.g. battery cable, remote temperature sensor).

3. Loosen the two Inverter Module thumbscrews.

4. Slide the Inverter Module out of the power supply.

5. If the Inverter Module is equipped with a communication module, remove it by loosening the two
Phillips captive screws.

Captive Screws

Fig. 7-1, Captive Screw Locations

746-257-B5-001, Rev. A1 (11/2013)

59

7.0 Installation, continued

7.2 Module Installation Procedure in XM3-HP Power Supplies, continued

Fig. 7-2, The 18-pin Connector

6. Line up the 18-pin mating connectors on the IDH4 Series and the XM3-HP Inverter Module. Gently
push the IDH4 Series into the Inverter Module until the 18 pin mating connector is properly seated.

Fig. 7-3, Connecting the Transponder to the Inverter Module

7. Fasten the IDH4 Series to the Inverter Module by tightening the two captive screws. It is
recommended that the screws be tightened alternately, a few turns at a time so the transponder
aligns in parallel to the Inverter Module.

60

8. Reinstall the Inverter Module and tighten the two thumbscrews. Make front panel connections
(tamper, temperature sensor, battery sense, RF etc.).

9. If not yet done, record the cable modem MAC address from the front of the unit and report it to the
network manager for network provisioning.

746-257-B5-001, Rev. A1 (11/2013)

7.0 Installation, continued

7.3 IDH4X LEDs and Connections

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

Item LED or Connector Status Behavior Indication

N/A OFF No power or malfunctioning IDH4 Series

GRN

ALM/RDY: Alarm

1

and Ready

RED

REG: Upstream

2

ranging and
registration lock

DS: Downstream

3

RF Carrier detection
and lock

ACT: CPE Activity

4

status

LNK: CPE Link

5

status

RF Rx/Tx Power

6

Level Indicator

COM: AlphaBus

7

communications

8 BAT A/B GRN ON/OFF ON (steady) if battery string(s) connected correctly

9 BAT A/B Connector

10 BAT C/D GRN ON/OFF ON (steady) if battery string(s) connected correctly

11 BAT C/D Connector

12 RST: Reset buttton

13 ENV: Environmental Control connector

14 TPR: Tamper Switch connector

15 ETH: Ethernet connection

16 RF Connection

17 COM: AlphaBus Communications connector

18 CM, CPE MAC Address label

GRN

GRN

GRN

GRN

TRI

GRN

ON Reset of the IDH4 Series is in process

Steady Blinking Normal operation

Blinking more
OFF than ON

Blinking more
ON than OFF

OFF No power, upstream frequency undetermined

OFF / ON

ON CMTS registration completed

OFF No power / downstream carrier

OFF / ON Power on, downstream carrier frequency searching

ON Downstream carrier lock

OFF No Ethernet communications activity

OFF/ON

OFF No Ethernet link

ON Link on Ethernet Craft port

OFF No RF detected

Blue

Green Rx/Tx RF Power level within tolerance

Red

OFF No AlphaBus Communications

OFF/ON

Minor Alarm

Major Alarm

Power on, downstream locked, upstream
frequency ranging, DHCP request in progress

Momentary ashes during CPE communications

via the Ethernet Craft port

Rx/Tx Power at a warning level as set within the
SCTE-HMS Property Table

Rx/Tx Power at an alert level as set within the
SCTE-HMS Property Table

Momentary ashes - AlphaBus Port

communications active

746-257-B5-001, Rev. A1 (11/2013)

Fig. 7-4, IDH4X LEDs and Connectors

61

7.0 Installation, continued

7.4 IDH4 LEDs and Connections

1

9

2

3

10

4

5

11

6

12

7

8

Item LED or Connector Status Behavior Indication

N/A OFF No power or malfunctioning transponder

GRN

ALM/RDY: Alarm and

1

Ready

RED

REG: Upstream

2

ranging and
registration lock

DS: Downstream RF

3

Carrier detection and
lock

ACT: CPE Activity

4

status

5 LNK: CPE Link status GRN

RF Rx/Tx Power Level

6

Indicator

7 BAT A/B GRN ON/OFF ON (steady) if battery string(s) connected correctly.

8 BAT A/B Connector

9 RST: Reset buttton

10 TPR: Tamper Switch connector

11 ETH: Ethernet connection

12 RF Connection

13 CM, CPE MAC Address label

GRN

GRN

GRN

TRI

ON Transponder reset in process

Steady Blinking Normal operation

Blinking more
OFF than ON

Blinking more
ON than OFF

OFF No power, upstream frequency undetermined

BLINKING

ON CMTS registration completed

OFF No power / downstream carrier

BLINKING Power on, downstream carrier frequency searching

ON Downstream carrier lock

OFF No Ethernet communications activity

BLINKING

OFF No link

ON Link on Ethernet Craft port

OFF No RF detected

Blue

Green Rx/Tx RF Power level within tolerance

Red

Minor Alarm

Major Alarm

Power on, downstream locked, upstream
frequency ranging, DHCP request pending

Momentary ashes during CPE communications

via the Ethernet Craft port

Rx/Tx Power at a warning level as set within the
SCTE-HMS Property Table

Rx/Tx Power at an alert level as set within the
SCTE-HMS Property Table

62

13

Fig. 7-5, IDH4 LEDs and Connectors

746-257-B5-001, Rev. A1 (11/2013)

7.0 Installation, continued

7.5 IDH4L LEDs and Connections

1

7

2

8

3

9

4

10

5

6

11

Item LED or Connector Status Behavior Indication

N/A OFF No power or malfunctioning transponder

GRN

ALM/RDY: Alarm and

1

Ready

RED

REG: Upstream

2

ranging and
registration lock

DS: Downstream RF

3

Carrier detection and
lock.

ACT: CPE Activity

4

status

5 LNK: CPE Link status GRN

RF Rx/Tx Power Level

6

Indicator

7 RST: Reset buttton

8 ENV: Environmental Control connector

9 TPR: Tamper Switch connector

10 ETH: Ethernet connection

11 RF Connection

12 CM, CPE MAC Address label

GRN

GRN

GRN

TRI

ON Transponder reset in process

Steady Blinking Normal operation

Blinking more
OFF than ON

Blinking more
ON than OFF

OFF No power, upstream frequency undetermined

BLINKING

ON CMTS registration completed

OFF No power / downstream carrier

BLINKING Power on, downstream carrier frequency searching

ON Downstream carrier lock

OFF No Ethernet communications activity

BLINKING

OFF No link

ON Link on Ethernet Craft port

OFF No RF detected

Blue

Green Rx/Tx RF Power level within tolerance

Red

Minor Alarm

Major Alarm

Power on, downstream locked, upstream
frequency ranging, DHCP request pending

Momentary ashes during CPE communications

via the Ethernet Craft port

Rx/Tx Power at a warning level as set within the
SCTE-HMS Property Table

Rx/Tx Power at an alert level as set within the
SCTE-HMS Property Table

746-257-B5-001, Rev. A1 (11/2013)

Note: The IDH4L requires the XM3 Smart AlphaGuard (SAG) option for individual battery voltage
measurements.

12

Fig. 7-6, IDH4L LEDs and Connectors

63

7.0 Installation, continued

7.6 Connecting the RF Drop

CAUTION!

Install a grounded surge suppressor (Alpha P/N 162-028-10 or equivalent) to protect
equipment from overvoltage.

Connect the RF drop according to the diagram below. The RF drop must have a properly installed ground
block in the power supply enclosure. Recommended downstream RF level is 0 dBmV. Connect any other
front panel connections at this time (e.g. battery strings, tamper switch).

Grounded Surge Protector

(See Caution Above)

RF Cable

to Headend

7.7 Front Panel Connections

Linked CableUPS

Serial Interface Cards

B

S
Y
S

C
O
M

A

A

Fig. 7-7, Connecting the RF Drop

IDH4 Series in

Primary XM3-HP

-21 for 9', -22 for 18', -23 for 35')

B

S
Y
S

C
O
M

Environmental connection

Ethernet connection

RF connection

A

C

AlphaBus Cable

(Alpha P/N 875-190-20 for 6',

ECM to SCM Interface

(Alpha P/N 704-709-20)

Generator (ECM)

Battery Sense Wire Harness

Refer to Section 8.0 Battery Sense Wire
Kits for part numbers and wiring options.

64

Comm Port

A

B

System Port

C

Battery Sense Connections

Connections

Connections with more
than one power supply

Fig. 7-8, System Interconnection Diagram

746-257-B5-001, Rev. A1 (11/2013)

7.0 Installation, continued

7.8 Environmental Connections

The IDH4X and IDH4L have the capability to monitor and control enclosure environmental heating and
cooling. Typically this is used for battery mat heaters in cold environments, however the functionality may
be implemented to control enclosure fans or air conditioners. The following section will outline the details

of the controls available and will include an example of a typical battery heater mat conguration and

explanation of the settings.

7.8.1 Connecting the Battery Heater Mat Controller

Power to the heater mat is provided via a customer-supplied controller plugged into the power
outlet inside the enclosure. A cable (Alpha p/n 875-627-22) connects the controller to the ENV
(Environmental) connector on the IDH4X and IDH4L. The connection procedure is shown below.

1. Connect the 4-pin connector from the
controller cable (Alpha p/n 875-627-22) into the
base of the Heater Mat Controller.

2. Plug the controller into the power outlet.

3. Plug the Heater Mat into the controller.

4. Plug the 6-pin connector into the ENV

connector.

Once the connection has been made, Environmental Control Management can be

congured through the following tables. The Environmental Control MIB section begins at

atiMgmtSysTempMgr (1.3.6.1.4.1.926.1.3.2.4).

Status of the Environmental Control is also available on the transponder’s Web page.

746-257-B5-001, Rev. A1 (11/2013)

65

7.0 Installation, continued

7.9 Environmental Control MIBs

atiMgmtSysTempCtrl (1.3.6.1.4.1.926.1.3.2.4.1)

Value list Description

off(1) Temperature device is off. This setting is non-volatile, if the variable is in this state upon reset (or power-up) this value will be

onTimer(2) Temperature device is turned on for a predened time. Before a SET to this state is issued, atiMgmtSysTempTimer is to be SET

onTemp(3) Temperature device is controlled by the battery temperature probe. Before a SET to this state, atiMgmtSysTempTemperature

onTimerTemp(4) Temperature device will be controlled by both the temperature and timer values. When set to this state, the temperature device will

on(5) Temperature device is on. This value can be used when the temperature device has a thermostat of its own. However it is recom-

atiMgmtSysTempStatus (1.3.6.1.4.1.926.1.3.2.4.2)

Value list Description

contactOpen(1) The value of this variable reects the state of the feedback signal from the temperature device. Since not all temperature devices

contactClosed(2)

retained. This is the DEFAULT factory value for this variable.

with the number of minutes the heater or cooler is to be on. When the timer has expired, this variable will automatically be set to 1.

and atiMgmtSysTempHysteresis must be set to the desired temperature values. Once placed into this state, this variable will not
change until another SET to this OID is received. Temperature control is based on the battery temperature probe. If there appears
to be no battery temperature probe, the output to the temperature device will be inactive.

be controlled as if this variable is in state 3, but only for the time dened by atiMgmtSysTempTimer. Once the timer has counted

down to zero, the value of this variable will be returned to 1. This value is volatile, after reset, the state of this variable will be 1 if it
was in this state before the reset.

mended, as a safety precaution, that state 3 is used with the battery temp probe being used as a backup in case the device ther­mostat gets stuck in the "on" state (provided the transponder is connected to the temperature device’s power control). This state
/ mode could also be used if the temperature control line was used for something other than a temperature control. This value is
non-volatile and will remain in this state after a reset.

have a feedback signal, or the operation of the feedback signal may vary from device to device, the meaning of this signal is

implementation specic.

atiMgmtSysTempMode (1.3.6.1.4.1.926.1.3.2.4.3)

Value list Description

heater(1) Mode of Operation. The temperature device may be a heater (such as a battery mat) or a cooler (such as an enclosure fan). When

cooler(2)

this device is acting as a thermostat, this variable denes the active state. If this variable is set to "heater", the temperature device
will be active only when the temperature is below the dened level. If this variable is set to "cooler", the temperature device will be
activated when the temperature is above the dened level. The DEFAULT factory setting for this variable is heater(1). This variable

is non-volatile and its value will be retained when the device is reset.

atiMgmtSysTempActiveState (1.3.6.1.4.1.926.1.3.2.4.4)

Value list Description

closed(1) This variable denes how this device creates the active state. When this variable is set to "closed(1)" the active state will be rep-

open(2)

resented by the drive pin being shorted to ground and high impedance will represent the inactive state. When this variable is set
to "open(2)" the active state will be represented by the drive pin being high impedance in the active state and shorted to ground in
the inactive state. The DEFAULT factory state for this variable will be 1. This variable is non-volatile and the value will be retained
when the device is reset.

Table 7-1, Environmental Control MIBs

66

746-257-B5-001, Rev. A1 (11/2013)

7.0 Installation, continued

7.9 Environmental Control MIBs, continued

atiMgmtSysTempTemperature (1.3.6.1.4.1.926.1.3.2.4.5)

Size list Description

1...70 Thermostatic temperature setpoint in degrees centigrade. When this device is set to control the temperature device based on

atiMgmtSysTempHysteresis (1.3.6.1.4.1.926.1.3.2.4.6)

Size list Description

1...10 When the device is controlling the temperature device thermostatically, this value is used to keep the temperature device from

atiMgmtSysTempTimer (1.3.6.1.4.1.926.1.3.2.4.7)

Size list Description

0...1440 When the temperature device is controlled using the timer, this is the number of minutes the temperature device will be active.

temperature, this variable (along with the hysteresis variable) will be used to determine when the temperature device is to be
turned on and off. This value is compared to the value from the battery temperature sensor. The DEFAULT factory state for this
variable will be 0 (once changed, it may not be put back to zero, providing an indication that the value has been adjusted). This
variable is non-volatile and the value will be retained when the device is reset.

going on and off too often. If the temperature device is a heater, the device will be turned on when the temperature reaches the
setpoint but will not be turned off until the detected temperature overshoots the set point by this amount. When the temperature
device is a cooler, the device will be turned on when the temperature reaches the set point, but will not turn off until the detected
temperature undershoots the set point by this amount. The DEFAULT factory state for this variable is 1. This variable is non­volatile and the value will be retained when the device is reset.

The DEFAULT factory state for this variable is 30. This variable is non-volatile and the value will be retained when the device is
reset.

atiMgmtSysTempCountdown (1.3.6.1.4.1.926.1.3.2.4.8)

Size list Description

0...1440 When the temperature device is controlled using the timer, this is a countdown that will indicate how many minutes before

the device will become inactive. The value of this counter is undened when the device is not active in a timer mode. Anytime

atiMgmtSysTempCtrl is SET to a value that indicates timer mode, the value of atiMgmtSysTempTimer will be copied into this
variable. If, while this variable is counting down, atiMgmtSysTempCtrl is again SET to a value that represents a timer mode,
the value of atiMgmtSysTempTimer will again be copied into this variable and the count will start over again. The temperature
device will change to inactive when this count drops to zero. At zero the counter will stop.

atiMgmtSysTempStatusInvert (1.3.6.1.4.1.926.1.3.2.4.9)

Value list Description

noInvert(1) The default value of this variable is noInvert(1), which provides a contact closure when the temperature device is on. When

invert(2)

this parameter is set to invert(2), the returned value for the contact status (atiMgmtSysTempStatus) will be inverted (contact
closed will be reported as open, contact open will be reported as closed). This accommodates the differences in which the
manufacturers of the relay block have implemented the open versus closed status contacts. This variable is non-volatile and the
value will be retained when the device is reset.

Table 7-1, Environmental Control MIBs, continued

746-257-B5-001, Rev. A1 (11/2013)

67

7.0 Installation, continued

7.10 Conguring the Battery Heater Mat Controller

In this example, values are written to their respective OIDs to set temperatures, control mode and status
reporting:

Set these OIDs to the specied value Functionality

atiMgmtSysTempTemperature (1.3.6.1.4.1.926.1.3.2.4.5) to 5 Heater turns on at 5°C

atiMgmtSysTempHysteresis (1.3.6.1.4.1.926.1.3.2.4.6) to 3 3°C of permitted controller overshoot (in this case, would turn off at 8°C)

atiMgmtSysTempCtrl (1.3.6.1.4.1.926.1.3.2.4.1) to 3 Battery temperature sensor used to control heater setpoint

atiMgmtSysTempMode (1.3.6.1.4.1.926.1.3.2.4.3) to 1 Places controller in heater mode

atiMgmtSysTempActiveState (1.3.6.1.4.1.926.1.3.2.4.4) to 1 Drive pin to the temperature device will go low when heater is on

atiMgmtSysTempStatusInvert (1.3.6.1.4.1.926.1.3.2.4.9) to 1 Sets the polarity of the feedback signal from the temperature device

Table 7-2, OID Values for Battery Heater Mat Controller

During operation, the following MIB points will report the current temperature and whether the heater is on
or off.

SNMP MIB Point Data

atiMgmtSysTempStatus (1.3.6.1.4.1.926.1.3.2.4.2) Temperature device ON or OFF

atiBBSysViewBatteryTemperature (1.3.6.1.4.1.926.1.4.1.1.3.5) Battery temperature (in degrees C)

Table 7-3, SNMP MIB Points for Battery Heater Mat Controller

68

746-257-B5-001, Rev. A1 (11/2013)

8.0 Battery Sense Wire Kits

8.1 36V Single and Dual Strings

Transponder Battery Sense Wire Kits are required for individual battery voltage monitoring when the XM3­HP SAG option is NOT installed. For XM3-HP power supplies with the SAG option, it is recommended to

use the specic SAG wire kits for the SAG adapter kits to accommodate any existing transponder Battery

Sense Wire Kits. Otherwise, a SAG "No Harness" alarm will be generated if the Battery Sense Wire Kits
are connected to the transponder battery connections (A/B or C/D) instead of the SAG connector.

To Power Supply

Red

Black

1

5

2

6

3

7

8

4

Back of Plug

A/B [C/D] NEG

To Power Supply

Red

Black

Pin 1

NEG

NEG

3A

POS

Vbatt 3A [C] 36V

Pin 4

NEG

NEG

2A

POS

Vbatt 2A [C] 24V

Pin 3

NEG

1A

Fig. 8-1, 36V System, Single String

POS

Sense Wire Kits:

Alpha P/N: 874-842-21 (6')
Alpha P/N: 874-842-27 (9')

Pin 2

Vbatt 1A [C] 12V

NEG

1

5

2

6

3

7

8

4

Back of Plug

746-257-B5-001, Rev. A1 (11/2013)

Pin 1

A/B [C/D] NEG

Pin 7

Vbatt 3B [D] 36V

3A

POS

Pin 4

Vbatt 3A [C] 36V

NEG

3B

POS POS POS

2A

POS

Pin 3

Vbatt 2A [C] 24V

Pin 6

Vbatt 2B [D] 24V

NEG

2B

Pin 5

Vbatt 1B [D] 12V

1A

POS

Vbatt 1A [C] 12V

NEG

1B

Pin 2

Fig. 8-2, 36V System, Dual String

Sense Wire Kits:

Alpha P/N: 874-842-20 (6')
Alpha P/N: 874-842-28 (9')

69

9.0 Start Up and Verication

9.1 Initial Start Up and Local Verication

To conrm successful hardware installation before leaving the installation site, verify network connectivity and

correct hardware interconnection.

To Verify Network Connectivity:

The DS and REG LEDs on the front of the IDH4 Series should be ON solid green. This indicates successful
registration with the headend. In addition, the RF LED should also be ON solid green indicating proper RF
power levels and the ALM/RDY LED should be blinking green for normal operation.

With the IDH4 Series used in conjunction with the XM3-HP power supply, network connectivity can be veried

via the COMM menu on the XM3-HP Smart Display. The following provides a list of parameters available on
the XM3-HP Smart Display populated with sample values. Important communication parameters such as the
cable modem IP address, upstream and downstream power levels can be viewed on the COMM - GENERAL

menu selection to conrm network connectivity. If no RF power is detected at the RF connector, a COMM -

FAULT menu will populate in the COMM menu.

COMM - GENERAL

COMM - EXTENDED

COMM - DIAGNOSITCS

ENTER ESC ESC

COMM - FAULT

RF POWER LEVEL FAULT

SEE GENERAL MENU

ESC

COMM - GENERAL

CM MAC ADDRESS

COMM GENERAL

CM MAC ADDRESS

CM IP ADDRESS

CPE MAC ADDRESS*

CPE IP ADDRESS*

CM RECEIVE POWER

CM TRANSMIT POWER

DOWNSTREAM SNR

00:90:EA:A0:04:99

00:90:EA:A0:04:99

192.196.203.101

00:90:EA:A0:05:01

192.168.200.100

Fig. 9-1, XM3-HP Smart Display Screens

ESC

-12.9dBmV

34.5dBmV

33.8dB

COMM - EXTENDED

IDH4 MODEL/CONFIG

IDH4X CW - 8B

COMM - EXTENDED

IDH4 MODEL/CONFIG

DSM3X CW-8B

IDH4 FIRMWARE VERSION

4.4.9.0_03.02_NA

SYSTEM NAME

ABC123 CABLE

SYSTEM CONTACT

SYSTEM LOCATION

123 BAKERVIEW

COMMON LOGICAL ID

12345-3767 ALPHAWAY

DOCSIS CONFIG FILE

ALPHA_IDH4.CM

IDH4 SERIAL NUMBER

SYSTEM DEVICES 3/7**

IPU-1 SAG-1 DOC-1

SYSTEM DEVICES 6/7**

XM3-1 APP-1 BTQ-1

SYSTEM DEVICES 7/7**

CABLEWARE SERVER IP*

192.168.200.151

ESC

JOHN DOE

A00499

UTL-1

COMM - DIAGNOSTICS

CABLE MODEM STATUS

Operational

COMM - DIAGNOSTICS

CABLE MODEM STATUS

SYSTEM UPTIME

DOWNSTREAM FREQUENCY

DOWN MODULATION TYPE

UPSTREAM FREQUENCY

T3 TIMEOUTS

T4 TIMEOUTS

CODEWORD ERROR RATIO

MICROREFLECTIONS

CM RESETS

CM LOST SYNCS

LAST SN MP QUERY

*NOTE: Some menu items may not appear depending on
the options installed.

**NOTE: System Device menu items are internal Alpha
diagnostic codes. The System Devices menu items will
populate based on the option cards (SAG, APP, DOC)
installed and the number of external devices added to a
power system such a s multiple XM3s and/or AlphaGen.

3 DAYS 05H:16M:59S

ESC

OPERATIONAL

300.000 MHZ

256 QAM

15.000 MHZ

80360

51

8.20%

-5 DBC

10

5

Date/Time

70

746-257-B5-001, Rev. A1 (11/2013)

9.0 Start Up and Verication, continued

9.1 Initial Start Up and Local Verication, continued

Connect a computer’s network port to the transponder’s Ethernet port using a standard network cable.
Launch an Internet browser and enter 192.168.100.1 into the address. The transponder will return the

Web page shown below. Click on “General” to display the key communications parameters including
upstream and downstream power levels and the cable modem’s IP address, which conrms connectivity.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 9-2, General Tab Screen

71

9.0 Start Up and Verication, continued

9.2 Verifying Correct Hardware Interconnection

The BAT A/B and BAT C/D LED indicators on the front panel of the IDH4 Series unit should illuminate
solid green once the battery wiring harnesses are correctly installed. A system with multiple battery strings

must use String A as the rst string, B as the second, C as the third and D as the fourth.

NOTE:

The IDH4X model provides both BAT A/B and BAT C/D LED indicators and battery harness connectors (supports
a maximum of 4 battery strings). The IDH4 model provides only the BAT A/B LED indicator and battery harness
connector (supports a maximum 2 battery strings).

From the Power Supplies and Batteries section of "General" tab of the IDH4 Series Web page, the

following screen will be visible and the parameters shown will be available for viewing and verication.

To test hardware interconnection using the Ethernet port, verify valid values for Output Voltage, Output
Current and individual battery voltages.

72

Fig. 9-3, Power Supply Section - General Page

746-257-B5-001, Rev. A1 (11/2013)

9.0 Start Up and Verication, continued

9.3 System Status Indicators and Reset Button

The IDH4 Series indicates status with light emitting diodes (LEDs). During system start up, the LEDs

will rst blink momentarily then indicate the current status of a variety of parameters on the IDH4

Series transponder. The LEDs indicate alarms, RF power level status, battery string connectivity and
communications activity with the network. A description of each LED follows.

LED Status Behavior Indication

N/A OFF No power or malfunctioning IDH4 Series

ALM/RDY: Alarm and Ready

REG: Upstream ranging and
registration lock.

DS: Downstream RF Carrier
detection and lock.

ACT: CPE Activity status GRN

LNK: CPE Link status GRN

RF Rx/Tx Power Level
Indicator

COM: AlphaBus
Communications

BATT A/B GRN ON/OFF ON (steady) if battery string(s) connected correctly

BATT C/D GRN ON/OFF ON (steady) if battery string(s) connected correctly

GRN

RED

GRN

GRN

TRI

GRN

ON Reset of the IDH4 Series is in process

Steady Blinking Normal operation

Blinking more OFF than ON Minor Alarm SCTE-HMS congured

Blinking more ON than OFF Major Alarm SCTE-HMS congured

OFF No power, upstream frequency undetermined

OFF / ON

ON CMTS registration completed

OFF No power / downstream carrier

OFF / ON Power on, downstream carrier frequency searching

ON Downstream carrier lock

OFF No Ethernet communications activity

OFF/ON

OFF No Ethernet link

ON Link on Ethernet Craft port

OFF No RF detected

Blue

Green Rx/Tx RF Power level within tolerance

Red

OFF No AlphaBus Communications

OFF/ON

Power on, downstream locked, upstream frequency
ranging, DHCP request in progress

Momentary ash while CPE communications

ongoing via the Ethernet Craft port

Rx/Tx Power at a warning level as set within the
SCTE-HMS Property Table

Rx/Tx Power at an alert level as set within the
SCTE-HMS Property Table

Momentary ashes - AlphaBus Port Communications

active

ALM/RDY

REG

DS

ACT

LNK

RF

COM

BATT A/B

BATT C/D

9.3.1 Detailed LED Descriptions

After power is applied or a reset occurs, all LEDs will ash in certain patterns indicating the cable

modem chipset is starting or restarting. Once it is ready, it will begin the DOCSIS requirement of
searching for the downstream frequency lock and the LEDs will follow the detailed descriptions
below.

ALM/RDY - Alarm/Ready

The LED blinks GREEN during normal operation. The frequency of ashing by this LED provides
a visual alert for power supply discrete major and minor alarms if congured in the property and

discrete property tables of the SCTE-HMS MIB. If an event triggers an HMS alarm, the ALM/
RDY LED blinks RED according to the alarm type until the alarm has been resolved. For minor

alarms, the frequency of ashing will be more OFF than ON, and for major alarms the frequency
of ashing will be more ON than OFF. If both minor and major alarms activate, the ALM/RDY

LED displays a major alarm signal. Refer to Section 6.3, The Alpha MIBs for information on

conguring the IDH4 Series for active monitoring and alarming.

746-257-B5-001, Rev. A1 (11/2013)

Fig. 9-4, LED Functionality and Indications

73

9.0 Start Up and Verication, continued

9.3.1 Detailed LED Descriptions, continued

REG - CM Registration

This LED blinks while the modem registers with the DHCP and obtains the conguration le after

downstream channel CM/CMTS negotiation. Once the registration is complete, the LED will display solid
GREEN. This indicates that the IDH4 Series is communicating with the CMTS in the headend.

DS - Downstream Communication

The LED ashes while searching for the downstream DOCSIS channel and is on solid when the

downstream channel is locked. This LED indicates CM downstream signal status. This process may
take several seconds, depending on how long it takes the CM to locate a carrier signal and lock onto a
channel.

ACT - CPE Activity

The CPE activity LED ashes to indicate that data is being transmitted or received between the IDH4

Series and a network device.

LNK - Network Communication Status

The Ethernet link LED remains ON when there is an active connection on the Ethernet port (e.g., a
computer is connected for local diagnostics).

Rx/Tx Power

The Rx/Tx PWR LED tricolor LED provides the quick verication of the modem transmit (Tx) and receive

(Rx) RF power levels. The Rx/Tx PWR LED is GREEN when both the cable modem Tx and cable

modem Rx RF power levels are within the range as specied in Table 9-1, SCTE-HMS Property Table.
It is BLUE when Rx and/or Tx levels are within the “warning” range as specied by the SCTE-HMS
PropertyTable. The LED is RED when Rx and/or Tx levels are outside the range as specied by the

SCTE-HMS PropertyTable.

Parameter alarm Enable HiHi Hi Lo LoLo Deadband

Rx

Tx

docsIfDownChannelPower

(OID:1.3.6.1.2.1.10.127.1.1.1.1.6)

docsIfCmStatusTxPower

(OID:1.3.6.1.2.1.10.127.1.2.2.1.3)

00

(0F*)

00

(0C*)

150 100 -100 -150 15

550 500 00 00 15

*Values in ( ) denote behavior of the Rx/TX LED if alarmEnable bits are set to ‘00’.

Table 9-1, SCTE-HMS Property Table

By default, alarmEnable is set to 00 (disabled) to prevent unwanted SNMP traps but the LED behavior will
function as if the alarmEnable were set to the values in the SCTE-HMS Property Table. If the alarmEnable
bits are set to anything other than 00 the LEDs will then follow the behavior of the desired enable bit
setting.

The SCTE-HMS Property Table values translate into the following Rx/Tx Power LED color ranges:

74

LED Color Rx Range (dBmV) Tx Range (dBmV)

Green +10 to -10 0 to +50

Blue +15 to +10 and -10 to -15 +50 to +55

Red >+15 and <-15 >+55

Table 9-2, Rx/Tx Power LED Color Ranges

In addition to the above SCTE-HMS PropertyTable entries, the Tx and Rx levels displayed on the IDH4
Series Web page will each provide colored indicator bars that correlate to the RF LED and SCTE-HMS
PropertyTable thresholds.

746-257-B5-001, Rev. A1 (11/2013)

9.0 Start Up and Verication, continued

9.3.1 Detailed LED Descriptions, continued

Rx/Tx Power, continued

The current RF level status for both the Rx and Tx will be displayed on the colored scale

highlighted in black, providing verication of modem RF power levels. Refer to the gure below

for an example of the RF power level indicator bars on the Web page.

Fig. 9-5, IDH4 Series Web Page, RF Power Level Indicators

Conguring the Rx/Tx Power LED - Custom Settings

If desired, the RF Power Level ranges for the Rx/Tx PWR LED may be customized via
SNMP by adjusting the HiHi, Hi, Lo, LoLo values for the docsIfDownChannelPower and
docsIfCmStatusTxPower in the SCTE-HMS Property Table (OID:1.3.6.1.4.1.5591.1.1.1). Be

careful not to exceed the RF Input Power and Output Power range specications of the IDH4

Series transponder.

COM - AlphaBus Communications

The COM LED indicates any data trafc being received by the IDH4 Series through the COM

(AlphaBus) port. This LED will also blink one to three times approximately every 10 seconds,
which indicates communication exists between the IDH4 Series and other connected devices,
such as a generator or additional XM3.

BAT A/B - Battery Strings A & B

The LED indicator remains ON solid when the battery string wiring harness is correctly connected
to the batteries and the Bat A/B connector on the IDH4 and IDH4X Series.

BAT C/D - Battery Strings C & D

The LED indicator remains ON solid when the battery string wiring harness is correctly connected
to the batteries and the Bat C/D connector on the IDH4X.

9.3.2 Resetting the Transponder

Should the need arise to reset the transponder locally, such as in the case of adding additional
power supplies, a generator, or carrying out maintenance activities, do the following:

Press and hold the reset button (RST) for approximately three (3) seconds. Release the button.
The transponder will perform its power up sequence. A pen or similar tool may be required to
depress the small reset button.

9.4 Verifying Communications via the Headend

Using SNMP, check connectivity by verifying power supply data by doing the following:

• With a MIB browser check power supply data in the psIdent MIB branch (1.3.6.1.4.1.5591.1) of the

SCTE-HMS tree.

• With network management software, verify the IDH4 Series has been identied and is reporting data

correctly.

746-257-B5-001, Rev. A1 (11/2013)

75

10.0 Alpha MIB Parameters

10.1 Denitions and Settings

The following tables display commonly-congured Alpha MIB parameters and provide specic information

with regard to functionality, options, OIDs, types and variables.

NOTE:

The Alpha MIB Denitions and Settings are subject to change without notice and should only be used

for advanced diagnostics. The SCTE-HMS MIBs listed in Section 6.0 Data Management should be
implemented for status monitoring & control.

Parameter OID Description Access Type Value

atiMgntSnmp 1.3.6.1.4.1.926.1.3.1 Object

SNMP TRAP ADDRESSES

atiMgmtSnmpTrapTable 1.3.6.1.4.1.926.1.3.1.1 Object

atiMgmtSnmpTrapAddress.1 1.3.6.1.4.1.926.1.3.1.1.1.2.1 SNMP Trap Address (1) Read/Write IP Address 0.0.0.0 (default)

atiMgmtSnmpTrapAddress.2 1.3.6.1.4.1.926.1.3.1.1.1.2.2 SNMP Trap Address (2) Read/Write IP Address 0.0.0.0

atiMgmtSnmpTrapAddress.3 1.3.6.1.4.1.926.1.3.1.1.1.2.3 SNMP Trap Address (3) Read/Write IP Address 0.0.0.0

atiMgmtSnmpTrapAddress.4 1.3.6.1.4.1.926.1.3.1.1.1.2.4 SNMP Trap Address (4) Read/Write IP Address 0.0.0.0

SECURE SNMP ACCESS ADDRESS

atiMgmtSnmpAccessTable 1.3.6.1.4.1.926.1.3.1.2 Object

atiMgmtSnmpAccessAddress.1 1.3.6.1.4.1.926.1.3.1.2.1.2.1 Secure IP Address (1) Read/Write IP Address 0.0.0.0 (default)

atiMgmtSnmpAccessAddress.2 1.3.6.1.4.1.926.1.3.1.2.1.2.2 Secure IP Address (2) Read/Write IP Address 0.0.0.0

atiMgmtSnmpAccessAddress.3 1.3.6.1.4.1.926.1.3.1.2.1.2.3 Secure IP Address (3) Read/Write IP Address 0.0.0.0

atiMgmtSnmpAccessAddress.4 1.3.6.1.4.1.926.1.3.1.2.1.2.4 Secure IP Address (4) Read/Write IP Address 0.0.0.0

SNMP ACCESS ENABLE

atiMgntSnmpAccess 1.3.6.1.4.1.926.1.3.1.3.0 Object

atiMgmtSnmpSnmpv1Access 1.3.6.1.4.1.926.1.3.1.3.1.0 SNMPv1 Access to Power

atiMgmtSnmpSnmpv2Access 1.3.6.1.4.1.926.1.3.1.3.2.0 SNMPv2c Access to Power

CPE & SECURITY KEY (Dual IP)

atiMgmtSnmpAlphaSetAccess 1.3.6.1.4.1.926.1.3.1.3.3.0 "Set to Data Access Key

atiMgmtSnmpAlphaSetKey 1.3.6.1.4.1.926.1.3.1.3.4.0 Data Access Key (Dual IP) Read/Write Octet String CIBSET (default)

atiMgmtSnmpCPESetEnabled 1.3.6.1.4.1.926.1.3.1.3.5.0 Corresponds to whether

atiMgmtSnmpSnmpCPEAccess 1.3.6.1.4.1.926.1.3.1.3.6.0 Enables the CPE interface -

CPE SETTINGS (Dual IP)

atiMgmtSysMonitoringCpeStaticMode 1.3.6.1.4.1.926.1.3.2.2.5.2.1.0 Method by which the CPE

atiMgmtSysMonitoringCpeStaticAddress 1.3.6.1.4.1.926.1.3.2.2.5.2.2.0 When the address source is

atiMgmtSysMonitoringCpeStaticMask 1.3.6.1.4.1.926.1.3.2.2.5.2.3.0 When the address source is

atiMgmtSysMonitoringCpeStaticGateway 1.3.6.1.4.1.926.1.3.2.2.5.2.4.0 When the address source is

Supply Data

Supply Data

CIBSET (default)"

or not the action taken on
atiMgmtSnmpAlphaSetKey
was successful. Once
enabled, writing 1(false)
to this variable will disable
CPE sets.

Dual IP mode

acquires its IP address

static, this is the IP address the
CPE will be assigned.

static, this is the mask the
device will use to determine if
other devices are on the local
area network (LAN).

static, this is the IP address of
the gateway the device will use
for accessing devices not on the
local area network (LAN).

Identier

Identiers

Identiers

Identiers

Read/Write Integer 1 = Disable

Read/Write Integer 1 = Disable

Read/Write Octet String Set to match the value

Read/Write Integer 1=Disabled (False)

Read/Write Integer 1=Disabled (Single IP)

Read/Write Integer 1=DHCP

Read/Write IP Address 0.0.0.0 (default)

Read/Write IP Address 0.0.0.0 (default)

Read/Write IP Address 0.0.0.0 (default)

2 = Enable (Default)

2 = Enable (Default)

of the Data Access Key
atiMgmtSnmpAlphaSetKey)

2=Enabled (True)

2=Enabled (Dual IP)

2=Static

76

746-257-B5-001, Rev. A1 (11/2013)

10.0 Alpha MIB Parameters, continued

10.1 Denitions and Settings, continued

Parameter OID Description Access Type Value

COMMUNITY STRINGS

atiMgmtSnmpCommunities 1.3.6.1.4.1.926.1.3.1.4.0 Object Identier

atiMgmtSnmpCommGet 1.3.6.1.4.1.926.1.3.1.4.1.0 Default "Read" Community String Read/Write Octet String AlphaGet (default)

atiMgmtSnmpCommSet 1.3.6.1.4.1.926.1.3.1.4.2.0 Default "Read/Write" Community String Read/Write Octet String AlphaSet (default)

SNMP TRAP

atiMgmtSnmpControls 1.3.6.1.4.1.926.1.3.1.5 Object Identier

atiMgmtSnmpTrapOnNormal 1.3.6.1.4.1.926.1.3.1.5.1.0 Traps sent when an item in an alarm

atiMgmtSnmpSendCount 1.3.6.1.4.1.926.1.3.1.5.2.0 Number of times a trap is to be sent/

atiMgmtSysSnmpTimeout 1.3.6.1.4.1.926.1.3.1.5.3.0 The number of minutes allowed to pass

SOFTWARE DOWNLOAD

atiMgmtSys 1.3.6.1.4.1.926.1.3.2.0 Object Identier

atiMgmtSysDownload 1.3.6.1.4.1.926.1.3.2.1.0 Object Identier

atiMgmtSysDownloadTftpAddress 1.3.6.1.4.1.926.1.3.2.1.1.0 DSM Firmware TFTP Server Address Read/Write IP Address 0.0.0.0 (default)

atiMgmtSysDownloadCtrl 1.3.6.1.4.1.926.1.3.2.1.2.0 DSM Firmware Download "Trigger" Read/Write Integer 1=readOneNext(1)

atiMgmtSysDownloadStatus 1.3.6.1.4.1.926.1.3.2.1.3.0 DSM Firmware download Status Read Only Integer 1=Idle (default)

atiMgmtSysDownloadFile1 1.3.6.1.4.1.926.1.3.2.1.4.0 DSM Firmware Filename Read/Write Octet String DSM rmware lename

atiMgmtSysDownloadFile2 1.3.6.1.4.1.926.1.3.2.1.5.0 Reserved Read/Write Octet String

atiMgmtSysDownloadProgress 1.3.6.1.4.1.926.1.3.2.1.6.0 Download Progress in Bytes Read Only Integer 0:0..100000

atiMgmtSysDownloadSysDescr 1.3.6.1.4.1.926.1.3.2.1.7.0 DSM Firmware description used for

atiMgmtSysDownloadSysObjectId 1.3.6.1.4.1.926.1.3.2.1.8.0 DSM Hardware Identier used for

atiMgmtSysDownloadCongName 1.3.6.1.4.1.926.1.3.2.1.9.0 DSM Setup File Filename Read/Write Octet String idhdoc04.cfg

atiMgmtSysDownloadCongAddress 1.3.6.1.4.1.926.1.3.2.1.10.0 DSM Setup File TFTP location Read/Write IP Address 0.0.0.0 (default)

atiMgmtSysDownloadCm 1.3.6.1.4.1.926.1.3.2.1.11.0 Force DSM Download from modem's

WEB SERVER ENABLE

atiMgmtSysHttpPrams 1.3.6.1.4.1.926.1.3.2.2.4 Object Identier

atiMgmtSysHttpEnabled 1.3.6.1.4.1.926.1.3.2.2.4.1.0 Access to IDH4 via Web Browser Read/Write Integer 1=Disable

SIMPLE NETWORK TIME PROTOCOL

atiMgmtSysServers 1.3.6.1.4.1.926.1.3.2.3.0 Object Identier

atiMgmtSysServSntp 1.3.6.1.4.1.926.1.3.2.3.1.0 IP Address of SNTP Server (Optional) Read/Write IP Address 0.0.0.0 (default)

state returns to normal

repeated

without SNMP communications. On the
lapse of this many minutes the device
will reset. Setting this value to zero will
prevent timeout resets.

upgrades

upgrades

docsDevSwServerIp (Dual IP)

Read/Write Integer 1 = Disable

2 = Enable (default)

Read/Write Integer 1 to 9

1 (default)

Read/Write Integer 0 to 65,000 (in minutes)

1440 (default)

2=readTwoNext(2)
3=idle(3)
4=abort(4)
5=psReprogram(5)

2=Ready
3=Request
4=Requested
5=Transferring
6=Testing
7=Data Done
8=Error
9=Closing

Read/Write Octet String i.e. "ATI P01V01.12.0 " (legacy

Read/Write Object Identier 1.3.6.1.4.1.926.1.99.1.1.1.0

Read/Write Integer "1=Auto (default)

DSMs)

2=ForceCM"

2=Enable (default)

746-257-B5-001, Rev. A1 (11/2013)

77

10.0 Alpha MIB Parameters, continued

10.1 Denitions and Settings, continued

Parameter OID Description Access Type Value

ENVIRONMENTAL MANAGER

atiMgmtSysTempMgr 1.3.6.1.4.1.926.1.3.2.4.0 Object Identier

atiMgmtSysTempCtrl 1.3.6.1.4.1.926.1.3.2.4.1.0 Environmental Control Read/Write Integer 1=off (default)

atiMgmtSysTempStatus 1.3.6.1.4.1.926.1.3.2.4.2.0 Environmental Control Feedback State Read Only Integer 1=Contact Open (default)

atiMgmtSysTempMode 1.3.6.1.4.1.926.1.3.2.4.3.0 Environmental Mode (Heat/Cool) Read/Write Integer 1=Heater (default)

atiMgmtSysTempActiveState 1.3.6.1.4.1.926.1.3.2.4.4.0 Environmental Control Contact State

atiMgmtSysTempTemperature 1.3.6.1.4.1.926.1.3.2.4.5.0 Environment Temperature Read/Write Integer 1...70ºC

atiMgmtSysTempHysteresis 1.3.6.1.4.1.926.1.3.2.4.6.0 Environmental Temperature Hysteresis Read/Write Integer 1...10ºC

atiMgmtSysTempTimer 1.3.6.1.4.1.926.1.3.2.4.7.0 Environmental Default Timer Read/Write Integer 0...1440 (30 minute default, 15

atiMgmtSysTempCountdown 1.3.6.1.4.1.926.1.3.2.4.8.0 Environmental Timer Time Remaining Read Only Integer 0...1440 (in minutes)

atiMgmtSysTempStatusInvert 1.3.6.1.4.1.926.1.3.2.4.9.0 State Inverted to match the type of

GENERAL CONTROLS

atiMgmtSysTamperPolarity 1.3.6.1.4.1.926.1.3.2.6.1.0 Determines when tamper is active Read/Write Integer 1=Alarm On Open (default)

atiMgmtSysAlphaBusSize 1.3.6.1.4.1.926.1.3.2.6.2.0 Internal microprocessor

atiMgmtSysBatteryCalMode 1.3.6.1.4.1.926.1.3.2.6.3.0 This parameter determines which of the

atiMgmtSysAlphaBusSpeed 1.3.6.1.4.1.926.1.3.2.6.4.0 Select the speed at which the AlphaBus

atiMgmtSysGnrlInfoCongs 1.3.6.1.4.1.926.1.3.2.7.1 Object Identier

atiMgmtSysGnrlInfoCongsMain 1.3.6.1.4.1.926.1.3.2.7.1.1.0 An ASCII string programmed into the

(Open/Closed)

relay operation on the heater mat
controller

communications bus size. Alpha XM3
series power supplies use 9 bit. Alpha
GMX and VMX series supplies use 8 bit

calibration tables to use in cases where
the battery negative is tied to ground or

when it oats.

will communicate

main board non-volatile memory

Read/Write Integer 1=Closed (default)

Read/Write Integer 1=No invert (default)

Read/Write Integer 1=9 Bit (default)

Read/Write Integer 1=Float

Read/Write Integer 1=baud9600

Read Only Octet String Product number, conguration

2=OnTimer
3=OnTemp
4=onTimerTemp
5=on

2=Contact Closed

2=Cooler

2=Open

minute increments)

2=Invert

2=Alarm On Close

2=8 Bit

2=Negative

2=baud57600

number serial number, etc.

78

atiMgmtSysGnrlInfoCongsDaughter 1.3.6.1.4.1.926.1.3.2.7.1.2.0 An ASCII string programmed into the

atiMgmtSysGnrlInfoCongsBase 1.3.6.1.4.1.926.1.3.2.7.1.3.0 An ASCII string describing the base

ENVIRONMENTAL CONTROL CONNECTOR

atiMgmtSysIO 1.3.6.1.4.1.926.1.3.2.8 Object Identier

atiMgmtSysIOSelect 1.3.6.1.4.1.926.1.3.2.8.1.0 Designates what function the ENV IO

atiMgmtSysIOGenState 1.3.6.1.4.1.926.1.3.2.8.3.0 Current state of the generator when

C/D battery circuitry (IDH4X only)

conguration of the device

pins are being used for.

the portable generator sense lines are
being used

Read Only Octet String Product number, conguration

Read Only Octet String i.e. IDH4, IDH4X

Read/Write Integer 1=notInstalled(1)

Read only Integer 1=notInstalled

746-257-B5-001, Rev. A1 (11/2013)

number serial number, etc.

2=lapOnly(2)
3=heaterControlOnly(3)
4=generatorOnly(4)
5=heaterControlAndLap(6)
6=generatorAndLap(6)
96=auxIO_1(96)
97=auxIO_2(97)
98=auxIO_3(98)
99=auxIO_4(99)

2=genOff
3=genRunning
4=genNotDetected
5=error

10.0 Alpha MIB Parameters, continued

10.1 Denitions and Settings, continued

Parameter OID Description Access Type Value

ENVIRONMENTAL CONTROL CONNECTOR, continued

atiMgmtSysIOSysIOPinCtrl 1.3.6.1.4.1.926.1.3.2.8.20.0 Control of Output Pin Read/Write Integer 1=contactOpen

atiMgmtSysIOSysIOPinIn4 1.3.6.1.4.1.926.1.3.2.8.21.0 Status of Input Pin 4 Read Only Integer 1=contactOpen

atiMgmtSysIOSysIOPinIn5 1.3.6.1.4.1.926.1.3.2.8.22.0 Status of Input Pin 5 Read Only Integer 1=contactOpen

atiMgmtSysIOSysIOPinIn6 1.3.6.1.4.1.926.1.3.2.8.23.0 Status of Input Pin 6 Read Only Integer 1=contactOpen

PLATFORMS

atiProductPlatforms 1.3.6.1.4.1.926.1.4 Object Identier

atiBroadbandUPS 1.3.6.1.4.1.926.1.4.1 Object Identier

atiBBSysView 1.3.6.1.4.1.926.1.4.1.1 Object Identier

atiBBSysViewSelects 1.3.6.1.4.1.926.1.4.1.1.1 Object Identier

atiBBSysViewSelfTestControl 1.3.6.1.4.1.926.1.4.1.1.1.1.0 Starts/Stops a system Self Test Read/Write Integer 1=Stop

atiBBSysViewSelfTestInhibit 1.3.6.1.4.1.926.1.4.1.1.1.2.0 System Self Test is prevented. On reset, the IDH4

atiBBSysViewSystemControlMgr 1.3.6.1.4.1.926.1.4.1.1.1.3.0 If the System Control Manager is running, the Small

atiBBSysViewFactoryDefaults 1.3.6.1.4.1.926.1.4.1.1.1.4.0 Will set all parameters back to the factory default

SYSTEM ALARMS

atiBBSysViewAlarms 1.3.6.1.4.1.926.1.4.1.1.2 Object Identier

atiBBSysViewMajorAlarm 1.3.6.1.4.1.926.1.4.1.1.2.1.0 Indicates if any of the items monitored are in a major

atiBBSysViewMinorAlarm 1.3.6.1.4.1.926.1.4.1.1.2.2.0 Indicates if any of the items monitored are in a minor

atiBBSysViewSelfTestResult 1.3.6.1.4.1.926.1.4.1.1.2.3.0 If any of the items being monitored indicate that Self

atiBBSysViewTempProbeStatus 1.3.6.1.4.1.926.1.4.1.1.2.4.0 If any of the devices being monitored indicate a

atiBBSysViewInputStatus 1.3.6.1.4.1.926.1.4.1.1.2.5.0 If ALL the items being monitored indicate no AC, this

SCALARS

atiBBSysViewScalars 1.3.6.1.4.1.926.1.4.1.1.3 Object Identier

atiBBSysViewInputVoltage 1.3.6.1.4.1.926.1.4.1.1.3.1.0 Power supply input voltage Read Only Integer

atiBBSysViewInputFrequency 1.3.6.1.4.1.926.1.4.1.1.3.2.0 Power supply input line frequency Read Only Integer

atiBBSysViewInputCurrent 1.3.6.1.4.1.926.1.4.1.1.3.3.0 Power supply input current Read Only Integer

atiBBSysViewBatteryVoltage 1.3.6.1.4.1.926.1.4.1.1.3.4.0 Battery voltage Read Only Integer

atiBBSysViewBatteryTemperature 1.3.6.1.4.1.926.1.4.1.1.3.5.0 Battery temperature (Degrees C) Read Only Integer

atiBBSysViewChargerCurrent 1.3.6.1.4.1.926.1.4.1.1.3.6.0 Sum of charging current from all power supplies Read Only Integer

atiBBSysViewChargerVoltsFloat 1.3.6.1.4.1.926.1.4.1.1.3.7.0 Battery charger oat voltage Read/Write Integer

atiBBSysViewChargerVoltsEqualize 1.3.6.1.4.1.926.1.4.1.1.3.8.0 Battery charger equalization voltage Read/Write Integer

atiBBSysViewChargerVoltsTemperatureComp 1.3.6.1.4.1.926.1.4.1.1.3.9.0 Battery charger temperature compensation

atiBBSysViewBatteryCapacity 1.3.6.1.4.1.926.1.4.1.1.3.10.0 Battery string capacity (Amp hours) Read/Write Integer

DETECT 6V BATTS

atiCibDiscTable 1.3.6.1.4.1.926.1.2.1.1.1.5.

14.0.11

gets this value from the master XM3 (in a system
with more than one power supply).

System Controller/Administrator (SSC or SSA)
is running and there is coordination between the
power supplies for charging, testing, etc. The value
of this item is stored in non-volatile memory.

value

alarm state

alarm state

Test failed, this item indicates a failure.

temp probe failure or absence, this item will alarm.

item will alarm.

(0 to 5mV/Cell/°C)

Controls the ability to detect and report 6 Volt
batteries

2=contactClosed

2=contactClosed

2=contactClosed

2=contactClosed

2=Start

Read/Write Integer 1=Normal (default)

Read/Write Integer 1=Running

Read/Write Integer 1=Normal

Read Only Integer 1=OK

Read Only Integer 1=OK

Read Only Integer 1=OK

Read Only Integer 1=OK

Read Only Integer 1=OK

Read/Write Integer

Read/Write Integer 0 = default

2=Inhibited

2=Disabled

2=Reset

2=Alarm

2=Alarm

2=Fail

2=Missing

2=No AC Present

1 = Detect 6 Volt
Batteries

746-257-B5-001, Rev. A1 (11/2013)

79

10.0 Alpha MIB Parameters, continued

10.1 Denitions and Settings, continued

Parameter OID Description Access Type Value

SYSTEM COUNTERS

atiBBSysViewCounters 1.3.6.1.4.1.926.1.4.1.1.4 Object Identier

atiBBSysViewSelfTestInterval 1.3.6.1.4.1.926.1.4.1.1.4.1.0 Power supply Self Test interval Read/Write Integer

atiBBSysViewSelfTestCountdown 1.3.6.1.4.1.926.1.4.1.1.4.2.0 Power supply Self Test countdown Read/Write Integer

atiBBSysViewSelfTestDuration 1.3.6.1.4.1.926.1.4.1.1.4.3.0 Power supply Self Test duration Read/Write Integer

atiBBSysViewInverterRuntime 1.3.6.1.4.1.926.1.4.1.1.4.4.0 Power supply inverter runtime Read Only Integer

atiBBSysViewStandbyEvents 1.3.6.1.4.1.926.1.4.1.1.4.5.0 Power supply standby events Read Only Integer

atiBBSysViewRuntimeRemaining 1.3.6.1.4.1.926.1.4.1.1.4.6.0 Power supply runtime remaining Read Only Integer

atiBBSysViewTimeInStandby 1.3.6.1.4.1.926.1.4.1.1.4.7.0 Power supply time in standby Read Only Integer

atiBBSysViewTimeSinceLastStandby 1.3.6.1.4.1.926.1.4.1.1.4.8.0 Power supply time since last standby Read Only Integer

SYSTEM LOGS

atiBBSysLogs 1.3.6.1.4.1.926.1.4.1.2 Object Identier

atiBBSysLogsEventsTable 1.3.6.1.4.1.926.1.4.1.2.1 Table of logged events Read Only

atiBBSysLogsCongTable 1.3.6.1.4.1.926.1.4.1.2.2 Table of logged conguration items Read Only

atiBBSysLogsPerformTable 1.3.6.1.4.1.926.1.4.1.2.3 Table of logged performance information Read Only

atiBBSysLogsBatteryTable 1.3.6.1.4.1.926.1.4.1.2.4 Table of logged battery information Read Only

SYSTEM APPLICATIONS

atiBBSysApps 1.3.6.1.4.1.926.1.4.1.3 Object Identier

atiBBSysAppsPsHealth 1.3.6.1.4.1.926.1.4.1.3.1 Object Identier

atiBBSysAppsPsHealthPsCount 1.3.6.1.4.1.926.1.4.1.3.1.1.0

atiBBSysAppsPsHealthTable 1.3.6.1.4.1.926.1.4.1.3.1.2 Table - row for each power supply

atiBBSysAppsBattStatus 1.3.6.1.4.1.926.1.4.1.3.2 Object Identier

atiBBSysAppsBattTable 1.3.6.1.4.1.926.1.4.1.3.2.1 Table - row for each battery Read Only Integer

atiBBSysAppsBattStringNum 1.3.6.1.4.1.926.1.4.1.3.2.1.1.1 String that this battery is a member of Read Only Integer 1 to 4

atiBBSysAppsBattBatteryNum 1.3.6.1.4.1.926.1.4.1.3.2.1.1.2 Battery number in string Read Only Integer 1 to 4

atiBBSysAppsBattMfgDate 1.3.6.1.4.1.926.1.4.1.3.2.1.1.3 Manufacture Date, typically stamped onto battery Read/Write Octet String Date

atiBBSysAppsBattAge 1.3.6.1.4.1.926.1.4.1.3.2.1.1.4

atiBBSysAppsBattMhos 1.3.6.1.4.1.926.1.4.1.3.2.1.1.5 Measured Battery MHOs Read/Write Integer

atiBBSysAppsBattBalancing 1.3.6.1.4.1.926.1.4.1.3.2.1.1.6 Status of attempt to balance the battery Read Only Integer

atiBBSysAppsBattStringCount 1.3.6.1.4.1.926.1.4.1.3.2.2.0

atiBBSysAppsBattPerStringCount 1.3.6.1.4.1.926.1.4.1.3.2.3.0

atiBBSysAppsBattConductanceMeasurementDate 1.3.6.1.4.1.926.1.4.1.3.2.4.0 Date of last conductance measurement Read Only Octet String Date and Time

atiBBSysAppsBattStandbyTimeRemaining 1.3.6.1.4.1.926.1.4.1.3.2.5.0

Indicates the number of power supplies that support
health analysis

Age of battery in months based on Manufacture
Date

Indicates the number of Battery strings that support
Health Analysis

Indicates the number of Batteries that support
Health Analysis

Remaining runtime if batteries are currently
discharging or available runtime for next discharge

Read Only Integer

Read Only Integer

Read Only Integer

Read Only Integer

Read Only Integer

1=balanced
2=inProgess
3=failed

1=overThreeHr
2=twoToThreeHr
3=oneToTwoHr
4=lessThanOneHr
5=calculating
6=notAvailable

80

746-257-B5-001, Rev. A1 (11/2013)

10.0 Alpha MIB Parameters, continued

10.1 Denitions and Settings, continued

Parameter OID Description Access Type Value

SYSTEM APPLICATIONS

atiBBSysAppsBattLifeRemaining 1.3.6.1.4.1.926.1.4.1.3.2.6.0 Remaining time before batteries need to be replaced Read Only Integer

1=overFiveYr

2=threeToFiveYr

3=twoToThreeYr

4=lessThanTwoYr

5=pmRecomnded

6=notAvailable

atiBBSysAppsUtilQualSupported 1.3.6.1.4.1.926.1.4.1.3.3.1.0 Indicates if Utility Quality Analysis is supported Read Only Integer

atiBBSysAppsUtilQualStartDate 1.3.6.1.4.1.926.1.4.1.3.3.2.0 Date upon which Utility Analysis started Read Only Octet String Date

atiBBSysAppsUtilQualStatus 1.3.6.1.4.1.926.1.4.1.3.3.3.0 Indicates the current line status Read Only Integer

atiBBSysAppsUtilQualSag 1.3.6.1.4.1.926.1.4.1.3.3.4 Object Identier

atiBBSysAppsUtilQualSagCurDuration 1.3.6.1.4.1.926.1.4.1.3.3.4.1.0 Time duration of current Sag event Read Only Time Ticks

atiBBSysAppsUtilQualSag24HourCount 1.3.6.1.4.1.926.1.4.1.3.3.4.2.0 Number of Sag events in the last 24 hours Read Only Integer

atiBBSysAppsUtilQualSag24HourAvgDuration 1.3.6.1.4.1.926.1.4.1.3.3.4.3.0

atiBBSysAppsUtilQualSag24HourMinDuration 1.3.6.1.4.1.926.1.4.1.3.3.4.4.0

atiBBSysAppsUtilQualSag24HourMaxDuration 1.3.6.1.4.1.926.1.4.1.3.3.4.5.0

atiBBSysAppsUtilQualSagLifetimeCount 1.3.6.1.4.1.926.1.4.1.3.3.4.6.0 Number of Sag events since device initialized Read Only Integer

Average Duration of Sag events occurring in the
last 24 hours

Minimum Duration of Sag events occurring in the
last 24 hours

Maximum Duration of Sag events occurring in the
last 24 hours

Read Only Time Ticks

Read Only Time Ticks

Read Only Time Ticks

1=unsupported

2=supported

1=ok

2=outage

3=sag

4=surge

5=frequency

6=unknown

atiBBSysAppsUtilQualSagLifetimeDurationSum 1.3.6.1.4.1.926.1.4.1.3.3.4.7.0

atiBBSysAppsUtilQualSagLifetimeMaxDuration 1.3.6.1.4.1.926.1.4.1.3.3.4.8.0 Time of longest Sag since device initialized Read Only Time Ticks

atiBBSysAppsUtilQualSurge 1.3.6.1.4.1.926.1.4.1.3.3.5 Object Identier

atiBBSysAppsUtilQualSurgeCurDuration 1.3.6.1.4.1.926.1.4.1.3.3.5.1.0 Time duration of current Surge event Read Only Time Ticks

atiBBSysAppsUtilQualSurge24HourCount 1.3.6.1.4.1.926.1.4.1.3.3.5.2.0 Number of Surge events in the last 24 hours Read Only Integer

atiBBSysAppsUtilQualSurge24HourAvgDuration 1.3.6.1.4.1.926.1.4.1.3.3.5.3.0

atiBBSysAppsUtilQualSurge24HourMinDuration 1.3.6.1.4.1.926.1.4.1.3.3.5.4.0

atiBBSysAppsUtilQualSurge24HourMaxDuration 1.3.6.1.4.1.926.1.4.1.3.3.5.5.0

atiBBSysAppsUtilQualSurgeLifetimeCount 1.3.6.1.4.1.926.1.4.1.3.3.5.6.0 Number of Surge events since device initialized Read Only Integer

atiBBSysAppsUtilQualSurgeLifetimeDurationSum 1.3.6.1.4.1.926.1.4.1.3.3.5.7.0

atiBBSysAppsUtilQualSurgeLifetimeMaxDuration 1.3.6.1.4.1.926.1.4.1.3.3.5.8.0 Time of longest Surge since device initialized Read Only Time Ticks

746-257-B5-001, Rev. A1 (11/2013)

Total accumulated time in Sag since device
initialized

Average Duration of Surge events occurring in the
last 24 hours

Minimum Duration of Surge events occurring in the
last 24 hours

Maximum Duration of Surge events occurring in the
last 24 hours

Total accumulated time in Surge since device
initialized

Read Only Time Ticks

Read Only Time Ticks

Read Only Time Ticks

Read Only Time Ticks

Read Only Time Ticks

81

10.0 Alpha MIB Parameters, continued

10.1 Denitions and Settings, continued

Parameter OID Description Access Type Value

SYSTEM APPLICATIONS

atiBBSysAppsUtilQualOutage 1.3.6.1.4.1.926.1.4.1.3.3.6 Object Identier

atiBBSysAppsUtilQualOutageCurDuration 1.3.6.1.4.1.926.1.4.1.3.3.6.1.0 Time duration of current Outage event Read Only Time Ticks

atiBBSysAppsUtilQualOutage24HourCount 1.3.6.1.4.1.926.1.4.1.3.3.6.2.0 Number of Outage events in the last 24 hours Read Only Integer

atiBBSysAppsUtilQualOutage24HourAvgDuration 1.3.6.1.4.1.926.1.4.1.3.3.6.3.0

atiBBSysAppsUtilQualOutage24HourMinDuration 1.3.6.1.4.1.926.1.4.1.3.3.6.4.0

atiBBSysAppsUtilQualOutage24HourMaxDuration 1.3.6.1.4.1.926.1.4.1.3.3.6.5.0

atiBBSysAppsUtilQualOutageLifetimeCount 1.3.6.1.4.1.926.1.4.1.3.3.6.6.0 Number of Outage events since device initialized Read Only Integer

atiBBSysAppsUtilQualOutageLifetimeDurationSum 1.3.6.1.4.1.926.1.4.1.3.3.6.7.0

atiBBSysAppsUtilQualOutageLifetimeMaxDuration 1.3.6.1.4.1.926.1.4.1.3.3.6.8.0 Time of longest Outage since device initialized Read Only Time Ticks

atiBBSysAppsUtilQualFreq 1.3.6.1.4.1.926.1.4.1.3.3.7 Object Identier

atiBBSysAppsUtilQualFreqCurDuration 1.3.6.1.4.1.926.1.4.1.3.3.7.1.0 Time duration of current frequency deviation event Read Only Time Ticks

atiBBSysAppsUtilQualFreq24HourCount 1.3.6.1.4.1.926.1.4.1.3.3.7.2.0

atiBBSysAppsUtilQualFreq24HourAvgDuration 1.3.6.1.4.1.926.1.4.1.3.3.7.3.0

atiBBSysAppsUtilQualFreq24HourMinDuration 1.3.6.1.4.1.926.1.4.1.3.3.7.4.0

atiBBSysAppsUtilQualFreq24HourMaxDuration 1.3.6.1.4.1.926.1.4.1.3.3.7.5.0

atiBBSysAppsUtilQualFreqLifetimeCount 1.3.6.1.4.1.926.1.4.1.3.3.7.6.0

atiBBSysAppsUtilQualFreqLifetimeDurationSum 1.3.6.1.4.1.926.1.4.1.3.3.7.7.0

atiBBSysAppsUtilQualFreqLifetimeMaxDuration 1.3.6.1.4.1.926.1.4.1.3.3.7.8.0

Average Duration of Outage events occurring in the
last 24 hours

Minimum Duration of Outage events occurring in the
last 24 hours

Maximum Duration of Outage events occurring in
the last 24 hours

Total accumulated time in Outage since device
initialized

Number of frequency deviation events in the last
24 hours

Average Duration of frequency deviation events
occurring in the last 24 hours

Minimum Duration of frequency deviation events
occurring in the last 24 hours

Maximum Duration of frequency deviation events
occurring in the last 24 hours

Number of frequency deviation events since device
initialized

Total accumulated time in frequency deviation since
device initalized

Time of longest frequency deviation since device
initialized

Read Only Time Ticks

Read Only Time Ticks

Read Only Time Ticks

Read Only Time Ticks

Read Only Integer

Read Only Time Ticks

Read Only Time Ticks

Read Only Time Ticks

Read Only Integer

Read Only Time Ticks

Read Only Time Ticks

82

Broadcom MIBS:

Parameter OID Description Access Type Value

HTTP Management MIB

httpMgmt 1.3.6.1.4.1.4413.2.2.2.1.1.3 Object Identier

httpAdminId 1.3.6.1.4.1.4413.2.2.2.1.1.3.1.0 Controls and reects the user name for admin level HTTP privileges Read/Write Octet String Alpha (default)

httpAdminPassword 1.3.6.1.4.1.4413.2.2.2.1.1.3.2.0 Controls and reects the password for admin level HTTP privileges Read/Write Octet String AlphaSet (default)

httpUserId 1.3.6.1.4.1.4413.2.2.2.1.1.3.3.0 Controls and reects the user name for user level HTTP privileges Read/Write Octet String Alpha (default)

httpUserPassword 1.3.6.1.4.1.4413.2.2.2.1.1.3.4.0 Controls and reects the password for user level HTTP privileges Read/Write Octet String AlphaGet (default)

746-257-B5-001, Rev. A1 (11/2013)

11.0 Specications

Battery Monitoring

Power System Management

Management Protocol

Advanced Diagnostics

Intelligent Power Supply Interface

Battery State of Health
(requires AlphaApps option)

Utility Status & Events
(requires AlphaApps option)

History Log Reports

Hardware

RF Cable Interface

Local Interface RJ-45, Ethernet, 10/100Mbps

LED Indicators

I/O Control

(IDH4X and IDH4LOnly)

1

IDH4X IDH4 IDH4L

Up to four strings of 36 or 48V

batteries (6V batts congurable up to

two strings)

Up to ve power supplies and an

AlphaGen generator are managed
from a single IDH4X including
coordinated battery charging, system
test and aggregated alarms

Standard ANSI/SCTE-HMS MIBs support basic power supply monitoring. Advanced diagnostics with
battery and power module analytics available via secure SNMP

Power supply user interface displays advanced diagnostics including: DOCSIS modem upstream and

downstream RF levels, IP address assigned by network DHCP server, MAC address and rmware

versions, individual battery voltages to verify correct wire harness installation

Power supply internal analytic diagnostics report when batteries should be serviced.

• Battery String Runtime Remaining

• Battery Life Remaining

AC Line Status:

• Utility Performance Status (outages, sags, surges, frequency)

• Utility Events (24-hour and lifetime number of events)

• Power Supply Event Log (events of daily power supply operation)

• Power Supply Conguration Log (events that occur infrequently)

• Battery Event Log (battery conductance measurements and battery manufactured dates)

F-connector, female, 75 Ohm, connector angle better accommodates coax bend radius when installed in
some enclosures

Alarm/Ready, Upstream registration, Downstream lock, AlphaBus activity, RF level, Ethernet Link, CPE trafc,

Battery Sense harness correctly connected

6-pin Molex: Digital input, Digital output, 5V, Common

Up to two strings of 36 or 48V

batteries (6V batts congurable

up to two strings)

N/A N/A

Smart AlphaGuard (SAG)
option required for individual
battery monitoring.

AlphaBus RJ-11 offset tab: Multiple-power supply and AlphaGen communications

Battery Monitoring

Tamper NO or NC, software congurable, reads enclosure door magnetic switch

8-pin Molex battery string A/B and
8-pin Molex battery string C/D.

8-pin Molex battery string A/B

Environment

Operating Temperature -40 to 65°C / -40 to 149°F

Storage Temperature -40 to 85°C / -40 to 185°F

Humidity 10 to 90% non-condensing

FCC Part 15 Class A

Regulatory Compliance

1

Advanced diagnostics are available through Alpha Certied network monitoring systems

EN 50083-2:2006 EMC requirements for CATV equipment
EN 62040-2:2006 Uninterruptable power supply EMC requirements, Category C2

Surge: IEEE 587, Category B3
RoHS: Directive 2002/95/EC

Network Communications

DOCSIS (RF) Port Protocols IPv4, IPv6, UDP, TCP, DHCP, TFTP, SNMPv1,SNMPv2c, HTTP, SNTP

Ethernet Port

Local Mode: HTTP Web interface for local on-site diagnostics
CPE Mode: DOCSIS Cable modem Ethernet CPE functionality

10-pin Molex battery string
A/B and C/D (requires SAG
option)

MIBs

746-257-B5-001, Rev. A1 (11/2013)

Power supply (ANSI/SCTE 38-4)
Other SCTE-HMS MIBs as dened by the SCTE for power supply and generator status monitoring
Alpha proprietary advanced UPS diagnostics

83

11.0 Specications, continued

Power Supply Monitored Parameters

Major Alarm

Minor Alarm Aggregate alarm consisting of: Temperature probe error, AC line loss

Input Voltage Reported from power supply V(in) measurement

Output Voltage Reported from power supply V(out) measurement

IDH4X IDH4 IDH4L

Aggregate alarm consisting of: Test fail, battery fail, line isolation alarm, output overload, inverter,
over-temperature

Output Current

Output Power Calculated, reported in AC Watts

UPS Status AC Line, Standby, Test in progress, Test alarm

Enclosure Door Open or Closed

Battery Voltage

Battery Temperature Reported from power supply battery Remote Temperature Sensor (RTS)

Remote Test Control Start/Stop power supply test cycle

0 to 25A standard on port 1
Port 2 requires power suppy DOC option

Individual battery voltage, up to
four strings of 3 or 4 batteries
(maximum 16 batteries),
±100mV per battery.

Individual battery voltage,
up to two strings of 3 or
4 batteries (maximum 8
batteries), ±100mV per
battery.

Individual battery voltage, up to
four strings of 3 or 4 batteries
(maximum 16 batteries),
±100mV per battery. (with SAG option)

Generator Monitored Parameters (IDH4X Only)

Status Generator Off, Running, Alarm

Generator Alarm

Gas Hazard OK, Alarm

Water Intrusion OK, Alarm

Pad Shear OK, Alarm

Enclosure Door Open, Alarm

Ignition Battery Voltage ±100mV

Enclosure Temperature ±2°C

Low Fuel OK, Alarm

Remote Test Control Start / Stop generator test cycle

Aggregate alarm consisting of: Low oil pressure, engine over-temp, engine over-speed, crank limit,
over voltage, low fuel, water intrusion, pad shear, gas hazard, test fail

Cable Modem

Compliance DOCSIS 1.1 and 2.0

Transmit Frequency Range 5 to 42 MHz

Receive Center Frequency Range 91 to 857 MHz

TDMA:
+8 to +54 dBmV (32QAM, 64QAM)

Output Power Range

+8 to +55 dBmV (8QAM, 16QAM)
+8 to +58 dBmV (QPSK)
S-CDMA:
+8 to +53 dBmV (All modulations of S-CDMA)

84

Input Signal Range -15 to +15 dBmV

Channel Bandwidth 6 MHz

Additional Equipment

874-842-21 XP-BSC-3-6 Wire Kit, Battery Sense, 1x36V, 6'

874-842-20 XP-BSC-6-6 Wire Kit, Battery Sense, 2x36V, 6'

874-841-21 XP-BSC-4-6 Wire Kit, Battery Sense, 1x48V, 6'

Surge Protector

(Alpha p/n 162-028-10)

Female/Female connector conguration, “F” type connector with integral ground block. Required for

all installations

746-257-B5-001, Rev. A1 (11/2013)

12.0 Glossary

Acronym Denitions

ANSI: American National Standards Institute

BER: Basic Encoding Rules

CM: Cable Modem

CMTS: Cable Modem Termination System

CPE: Customer Premises Equipment

DHCP: Dynamic Host Conguration Protocol

DOCSIS: Data Over Cable Service Interface Specication

EMS: Element Management System

HMS: Hybrid Management Sublayer

IT: Information Technology

MAC: Media Access Control

MIB: Management Information Base

NMS: Network Management System

QoS: Quality of Service

RTS: Remote Temperature Sensor

SCTE: Society of Cable Telecommunications Engineers

SI: Serial Interface

SNMP: Simple Network Management Protocol

SNTP: Simple Network Time Protocol

TFTP: Trivial File Transfer Protocol

TOD: Time of Day

UDP: User Datagram Protocol

VoIP: Voice over Internet Protocol

746-257-B5-001, Rev. A1 (11/2013)

85

13.0 Dual IP Mode (Addendum)

13.1 Overview

The IDH4 Series can operate in either Single (default) or Dual IP mode. In Single IP mode, data from both
the cable modem and power supply are accessed and managed through the modem’s IP address on the
secure private modem network. In Dual IP mode, the transponder acts like a CPE device to the cable
modem and registers a second IP address on the public CPE network.

The following table lists some of the common characteristics of the IDH4 Single IP and Dual IP

congurations:

Single IP Dual IP

Network All data from both the cable modem and power

supply are accessed and managed through
the modem’s IP address on the secure private
modem network.

Data Access The Network Management System requires

access to the same private modem network.

Security Communication with the transponder is limited

to the private LAN network, and is very secure.

IP Addresses Where the IP address pool is limited, there is

no need to issue the transponder a CPE IP
address. Only one (1) IP Address is required for
the cable modem of the IDH4.

Data Management Access to the transponder is limited to the

private LAN network making data management

less versatile, especially for eld personnel.

Table 13-1, Single IP Mode versus Dual IP Mode

The transponder acts like a CPE device to the cable
modem and registers a second IP address on the public
CPE network.

Dual IP mode allows the power supply data to be
accessed and managed from anywhere within the
public (CPE) network.

Since the transponder is a CPE on the public network,
access may be less secure.

The CPE requires its own IP address, which may be
in short supply. A total of two (2) IP addresses are
required, one for the cable modem and one for the
transponder.

The transponder is accessible on the public (CPE)
network. This makes data management more versatile

for eld personnel.

86

One CM IP address only accessible on the private (LAN)
network with access to both CM and transponder data.

IDH4

Cable Modem Transponder

MIB Tables

Fig. 13-1, Simplied Block Diagram

Single IP Mode

One CM IP address, CM and transponder data;
accessible on the private (LAN) network.

IDH4

Cable Modem Transponder (CPE)

MIB Tables

One CPE IP address, transponder data only;
accessible on the public (CPE) network.

Fig 13-2, Simplied Block Diagram

Dual IP Mode

746-257-B5-001, Rev. A1 (11/2013)

13.0 Dual IP Mode (Addendum), continued

13.2 Web Comparison, Single IP Mode/Dual IP Mode

To easily determine the conguration of the transponder when viewing it on its web page, check the

Conguration Line as well as the entries for the CM and CPE addresses. A single IP transponder will
display a CM MAC address only, while a Dual IP transponder will also indicate a CPE address.

Indicates 1 IP address:

"Single IP" Status Monitor

(partial page only; data values shown for illustration purposes only)

Indicates 2 IP addresses:

"Dual IP" Status Monitor

Displays CM MAC address only

Fig. 13-3, Single IP IDH4 Series Web Page

Displays CM and CPE addresses only

746-257-B5-001, Rev. A1 (11/2013)

Fig. 13-4, Dual IP IDH4 Series Web Page

(partial page only; data values shown for illustration purposes only)

87

13.0 Dual IP Mode (Addendum), continued

13.3 Conguring Dual IP Mode

To switch the IDH4 Series transponder from Single to Dual IP mode the atiMgmtSnmpSnmpCPEAccess
parameter of the Alpha MIB will need to be enabled. The Dual IP enable setting can be set through

the DOCSIS Conguration le, the IDH4 Setup File (idhdoc04.cfg), the Provisioning Mode via the

Communications Web page or remotely using SNMP by setting the following Alpha MIB:

MIB Parameter Object ID Description Value

atiMgmtSnmpSnmpCPEAccess 1.3.6.1.4.1.926.1.3.1.3.6.0 Enables/Disables the

Table 13-2, Enabling Dual IP mode

The CPE Transponder IP can be assigned its IP, Subnet Mask and Gateway Addresses via a DHCP
server.

CPE Interface

1=Disabled (Single IP)
2=Enabled (Dual IP)

88

Fig. 13-5, Dual IP Conguration Settings on the Communications Page of IDH4 Web Server

Fig. 13-6, Dual IP Parameters on the General Page of IDH4 Web Server

746-257-B5-001, Rev. A1 (11/2013)

13.0 Dual IP Mode (Addendum), continued

13.3 Conguring Dual IP Mode, continued

13.3.1 idhdoc04.cfg in Dual IP Mode

NOTE:

Refer Section 3.2.4, Proprietary Conguration File idhdoc04.cfg for details on using the

idhdoc04.cfg le to propagate custom settings to eld-deployed IDH4 Series transponders.

In Dual IP mode, the IDH4 Series will rst attempt to download the proprietary conguration le

idhdoc04.cfg through the CPE’s interface from a TFTP server on the CPE network. In many
networks, the TFTP server is blocked or disabled, so the IDH4 Series also has provisions to

download this le through the Cable Modem interface from the modem’s provisioning server if
necessary. The lename and TFTP server location may also be specied through special tags in

the DHCP Offer, refer to Section 13.3.3, Specifying idhdoc04.cfg Download Settings in Dual
IP Mode for details. Similiar to Single IP mode, any IDH4 Series proprietary SNMP MIB setting

may be placed in the modem’s DOCSIS conguration le which would eliminate the need for

idhdoc04.cfg.

13.3.2 Changing Default idhdoc04.cfg Download Settings in Dual IP Mode

Table 13-3 explains the download options available for the idhdoc04.cfg le in Dual IP mode. The
‘Download Interface’ indicates the network from which the IDH4 series will attempt to download

idhdoc04.cfg, either the CPE network or the more secure cable modem management network.

Parameter Comments Value

atiMgmtSysDownloadCongAddress

OID 1.3.6.1.4.1.926.1.3.2.1.10.0

DHCP Server IP Server or Relay Agent Address

DHCP Option 54 Server IP Server or Relay Agent Address

DHCP Tags See Section 13.3.3 As Set 4 CPE

docsDevServerCongTftpAddress

1.3.6.1.2.1.69.1.4.11.0

docsDevSwServerAddress

1.3.6.1.2.1.69.1.3.7.0

Software Upgrade Server Set via DOCSIS conguration le As Set 7 CM

Overrides Default Location 0.0.0.0

(Default)

As Set 2 CPE
from DHCP lease (No Change
Necessary)

As Set 3 CPE
from DHCP lease

Automatically set in modem CM's TFTP

Server Address

Set via DOCSIS conguration le As Set 6 CM

Search

Order

Table 13-3, idhdoc04.cfg Download Settings

Download

Interface

1 CPE

5 CM

746-257-B5-001, Rev. A1 (11/2013)

89

13.0 Dual IP Mode (Addendum), continued

13.3 Conguring Dual IP Mode, continued

13.3.3 Specifying idhdoc04.cfg name and location via DHCP Tags

In the User-dened area of the DHCP Tags, above option 192, the TRANSPONDER will look for

the following value:

Tag: [Insert Unique Tag Name, e.g. ‘ati-tag’]
Value: aticong

In the Tag value immediately following will be the value for the TFTP server to use:

Tag: [Insert Unique Tag Name, e.g. ‘ati-ip’]

Value: IP address of TFTP server (i.e. 192.168.1.51)

Immediately following will be the value for the cong lename:

Tag: [Insert Unique Tag Name, e.g. ‘ati-name’]
Value: =idhdoc04.cfg (an equal sign needs to be in front of the lename for the DHCP server

to recognize this as a valid entry)

90

746-257-B5-001, Rev. A1 (11/2013)

13.0 Dual IP Mode (Addendum), continued

13.4 Dual IP SNMP Community Strings

The transponder community strings used for the CPE Transponder in Dual IP mode can be congured

by the operator. The default transponder read-only community string is AlphaGet. The default read-write

community string is AlphaSet. These settings can be congured with the DOCSIS Conguration File, the

IDH4 Setup File (aitdoc03.cfg) or remotely using SNMP by including the parameters below:

NOTE:

These community strings are only applicable for CPE access in Dual IP mode. CM access in both Single

IP and Dual IP modes use standard DOCSIS community strings set through the modem conguration le's

docsDevNmAccessTable. See Section 3.2.1, Setting Modem Community Strings.

MIB Parameter Object ID Description Value

atiMgmtSnmpCommGet 1.3.6.1.4.1.926.1.3.1.4.1.0 Read Community String AlphaGet (default)

atiMgmtSnmpCommSet 1.3.6.1.4.1.926.1.3.1.4.2.0 Read/Write Community String AlphaSet (default)

Table 13-4, Community Strings

13.5 Security in Dual IP Mode

[desired value]

[desired value]

In Dual IP mode, additional SNMP security to the IDH4 Series proprietary MIBs is required since the
transponder and power supply data is exposed on the CPE network, which may be more vulnerable to

packet snifng and community string deciphering than on the secure cable modem network.

There are two methods of providing SNMP Security in Dual IP mode: the Data Access Key (default), and
the Secure Access List.

Method 1: Dual IP Security Using the Data Access Key

In Dual IP mode atiMgmtSnmpAlphaSetAccess is the only SNMP parameter within the Alpha
proprietary MIB with SNMP write access on the CPE network by default. When this parameter is
set to the value of the parameter atiMgmtSnmpAlphaSetKey, the data access key, SNMP read/write
access is granted to all parameters in the Alpha MIB tree with read/write attributes. When this access
is granted, the value of atiMgmtSnmpCPESetEnabled is automatically changed to "2" (enabled). After

the operator is nished setting the SNMP variables, SNMP write access can be disabled by setting the

atiMgmtSnmpCPESetEnabled to "1" or by setting atiMgmtSnmpAlphaSetAccess to any value other than
the data access key or by performing a reset to the IDH4 Series.

The data access key parameters can be changed from the default values through the DOCSIS

Conguration File, the IDH4 Series Setup File (idhdoc04.cfg) or remotely using SNMP by including the

following Alpha MIB parameters:

MIB Parameter Object ID Description Value

atiMgmtSnmpAlphaSetAccess 1.3.6.1.4.1.926.1.3.1.3.3.0 Set to Access Key Set to match the value of

atiMgmtSnmpAlphaSetKey

atiMgmtSnmpAlphaSetKey 1.3.6.1.4.1.926.1.3.1.3.4.0 Data Access Key (Dual IP) CIBSET (default)

atiMgmtSnmpCPESetEnabled 1.3.6.1.4.1.926.1.3.1.3.5.0 Corresponds to whether

746-257-B5-001, Rev. A1 (11/2013)

or not the action taken on
atiMgmtSnmpAlphaSetKey
was successful. Once
enabled, writing 1 to this
variable will disable CPE
sets.

Table 13-5, Data Access Key Parameters

1 = Disabled (False)

2 = Enabled (True)

91

13.0 Dual IP Mode (Addendum), continued

13.5 Security in Dual IP Mode, continued

Method 2: Dual IP Security Using the Secure Access List

The IDH4 provides an alternative method of providing additional SNMP security in Dual IP by limiting access
to the transponder’s CPE address. The Secure Access List method limits remote SNMP access to four IP
addresses. Only the IP addresses listed in the SNMP Access Table are able to read or write to the Alpha MIB
parameters from the public (CPE) network. This method overrides the default "Data Access Key" method.

The IP address entries in the SNMP Access Table can be set through the DOCSIS Conguration File, the IDH4

Setup File (idhdoc04.cfg) or remotely using SNMP by including the following Alpha MIB parameters:

MIB Parameter Object ID Description Value

atiMgmtSnmpAccessTable 1.3.6.1.4.1.926.1.3.1.2 Table of SNMP

atiMgmtSnmpAccessAddress.1 1.3.6.1.4.1.926.1.3.1.2.1.2.1 SNMP access IP Address #1 0.0.0.0 (Default)

atiMgmtSnmpAccessAddress.2 1.3.6.1.4.1.926.1.3.1.2.1.2.2 SNMP access IP Address #2 0.0.0.0 (Default)

atiMgmtSnmpAccessAddress.3 1.3.6.1.4.1.926.1.3.1.2.1.2.3 SNMP access IP Address #3 0.0.0.0 (Default)

atiMgmtSnmpAccessAddress.4 1.3.6.1.4.1.926.1.3.1.2.1.2.4 SNMP access IP Address #4 0.0.0.0 (Default)

Table 13-6, Secure Access Table Parameters

Access Addresses

Object identier

13.6 Copyright Information

Copyright © 2010-2012, Teng-Yong Ng. All rights reserved.

Redistribution and use in source and binary forms, with or without modication, are permitted provided

that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

92

746-257-B5-001, Rev. A1 (11/2013)

this page intentionally blank

Alpha Technologies Inc.

3767 Alpha Way
Bellingham, WA 98226
United States
Tel: [phone]
Fax: [phone]

Alpha Technologies Ltd.

7700 Riverfront Gate
Burnaby, BC V5J 5M4
Canada
Tel: [phone]
Fax: [phone]
Toll Free: [phone]

Alpha Technologies Europe Ltd.

Twyford House Thorley
Bishop’s Stortford
Hertfordshire, CM22 7PA
United Kingdom
Tel: [phone]
Fax: [phone]

Alpha Technologies GmbH

Hansastrasse 8
D-91126 Schwabach,
Germany
Tel: [phone]
Fax: [phone]

Alphatec Ltd.

339 St. Andrews St.
Suite 101 Andrea Chambers
3307 Limassol
Cyprus
Tel: [phone]
Fax: [phone]

Alpha TEK ooo

Khokhlovskiy Pereulok 16

Stroenie 1, Ofce 403

109028 Moscow
Russia
Tel: [phone]
Fax: [phone]

Alpha Technologies

Suite 1903, Tower 1,
Hong Kong City
33 Canton Road, Kowloon
Hong Kong, China
Tel: [phone]
Fax: [phone]

Alphatec Baltic

S. Konarskio Street 49-201
Vilnius, LT-03123
Lithuania
Tel: [phone]
Fax: [phone]

Visit us at www.alpha.com

Due to continuing product development, Alpha Technologies reserves the right to change specications without notice.
Copyright © 2013 Alpha Technologies. All Rights Reserved. Alpha® is a registered trademark of Alpha Technologies.

746-257-B5-001 Rev. A1 (11/2013)