AlphaNet™ DSM Series

DOCSIS® Status Monitor

Technical Manual
Model XP-DSM

Effective: June 2007

Alpha Technologies
Power
Alpha Technologies
®
 AlphaNet DSM Series
DOCSIS Status Monitor
Technical Manual

745-814-B0-001, Rev. A

Effective Date: June, 2007

Copyright© 2007
Alpha Technologies, Inc.
member of The GroupTM

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.

Contacting Alpha Technologies: www.alpha.com

or
For general product information and customer service (7 AM to 5 PM, Pacific Time), call
1-800-863-3930
For complete technical support, call
1-800-863-3364
7 AM to 5 PM, Pacific Time or 24/7 emergency support

To report errors in this document, send email to:Techpubs@alpha.com

3
 Table of Contents

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

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

2.0 System Overview............................................................................................................ 9

2.1 System Diagram................................................................................................... 9
2.2 Single IP Mode vs. Dual IP Mode Overview....................................................... 10
2.3 Network Connectivity Overview.......................................................................... 11
2.4 System Configuration and Installation Overview................................................ 11
2.5 XP-DSM Start-up and Reboot Routine............................................................... 12

3.0 Network Configuration and Option Settings.................................................................. 14

3.1 Provisioning the DHCP Server with the MAC Addresses................................... 14
3.2 The DOCSIS Configuration File......................................................................... 15
3.2.1 Setting Modem Community Strings in the DOCSIS Configuration File... 15
3.2.2 Example DOCSIS Configuration File...................................................... 16
3.3 Setting Communication Options......................................................................... 17
3.4 The DSM Setup File........................................................................................... 18
3.4.1 Building the DSM Setup File................................................................... 18
3.4.2 Example of an atidoc01.cfg DSM Setup File........................................... 19
3.4.3 Setting Transponder Community Strings with the DSM Setup File......... 20
3.5 Security in Dual IP Mode . ................................................................................. 21

4.0 Using the Local Port...................................................................................................... 22

5.0 Upgrading Firmware...................................................................................................... 24

5.1 Upgrading XP-DSM Modem Firmware............................................................... 24
5.1.1 Identifying the Modem and Obtaining Firmware Files............................. 24
5.1.2 Modem Firmware Upgrade SNMP Parameters....................................... 24
5.1.3 Upgrading Modem Firmware Manually by Setting SNMP Parameters... 25
5.1.4 Upgrading Modem Firmware in the DOCSIS Configuration File............. 25
5.2 Upgrading XP-DSM Transponder Firmware....................................................... 26
5.2.1 Remotely Upgrading XP-DSM Firmware................................................ 27
5.2.2 Upgrading XP-DSM Firmware Using a DSM Setup File......................... 27
6.0 Data Management......................................................................................................... 29
6.1 The SCTE-HMS MIB.......................................................................................... 30
6.2 The Alpha MIB.................................................................................................... 32

 745-814-B0-001, Rev. A
 6.3 SCTE-HMS MIB Alarms..................................................................................... 34
6.3.1 SCTE-HMS Configurable Alarms............................................................ 34
6.3.2 Distributing Alarm Settings...................................................................... 39
6.3.3 SNMP Traps............................................................................................ 41
6.3.4 General Power Supply Alarms................................................................ 43
7.0 Hardware Installation..................................................................................................... 44
7.1 Verifying Power Supply Device Address............................................................ 44
7.2 Hardware Installation Procedure........................................................................ 45
7.3 XP-DSM Connections........................................................................................ 47
7.3.1 Front Panel Diagram .............................................................................. 47
7.3.2 Connecting the RF Drop......................................................................... 47
7.3.3 Front Panel Connections......................................................................... 48
8.0 Battery Sense Wire Kit Connections............................................................................. 49
8.1 36V Single and Dual Strings.............................................................................. 49
8.2 48V Single and Dual Strings.............................................................................. 50

9.0 Start-up and Verification................................................................................................ 51

9.1 Initial Startup...................................................................................................... 51
9.2 LEDs and System Status................................................................................... 51
9.3 Verifying Successful Hardware Installation........................................................ 53
9.4 Verifying Communications via the Headend....................................................... 53

10.0 MIB Parameter Definitions and Settings...................................................................... 54

10.1 Alpha MIB Parameter Definitions and Settings.................................................. 54
10.2 Modem Firmware Upgrade Parameter Definitions and Settings........................ 57

11.0 Frequently Asked Questions........................................................................................ 58

12.0 Specifications............................................................................................................... 61

13.0 Glossary....................................................................................................................... 62

745-814-B0-001, Rev. A 
 Figures
Fig. 1-1, AlphaNet XP-DSM......................................................................................................8
Fig. 2-1, Single IP Mode.........................................................................................................10
Fig. 2-2, Dual IP Mode............................................................................................................10
Fig. 3-1, Location of MAC Addresses.....................................................................................14
Fig. 3-2, Example DOCSIS Configuration File........................................................................16
Fig. 6-1, Example SNMP Alarm Trap......................................................................................41
Fig. 7-1, Removing the Inverter Module from the Power Supply ...........................................45
Fig. 7-2, The 18-pin Jumper...................................................................................................46
Fig. 7-3, Connecting the Transponder to the Inverter Module................................................46
Fig. 7-4, Front Panel...............................................................................................................47
Fig. 7-5, Connecting the RF Drop...........................................................................................47
Fig. 7-6, System Interconnection Diagram.............................................................................48
Fig. 8-1, 36V System, Single String........................................................................................49
Fig. 8-2, 36V System, Dual String..........................................................................................49
Fig. 8-3, 48V System, Single String........................................................................................50
Fig.8-4, 48V System, Dual String...........................................................................................50
Fig. 9-1, LED Indications........................................................................................................52

Tables
Table 3-1, Modem Community String Parameters..................................................................15
Table 3-2, Transponder Communications Parameters...........................................................17
Table 3-3, Example DSM Setup File Parameters and Values................................................19
Table 3-4, Transponder Community String Parameters.........................................................20
Table 5-1, Modem Firmware Upgrade SNMP Parameters.....................................................24
Table 5-2, Transponder Firmware Upgrade SNMP Parameters.............................................26
Table 6-1, SCTE-HMS MIB Hierarchy....................................................................................31
Table 6-2, Alpha MIB Hierarchy..............................................................................................33
Table 6-3, Binary to Hex Conversions for Alarm Settings.......................................................35
Table 6-4, Analog Alarms and Common Settings...................................................................36
Table 6-5, Discrete Alarm Definitions and Common Settings.................................................38
Table 6-6, SNMP Alarm Trap Varbinds and Explanations.......................................................42
Table 6-7, XM2 Major and Minor Alarms.................................................................................43

 745-814-B0-001, Rev. A
 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.

ATTENTION:
The use of ATTENTION indicates specific regulatory/code requirements that may affect the placement of
equipment and /or installation procedures.

NOTE:
A NOTE provides additional information to help complete a specific task or procedure.

CAUTION!

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

WARNING!

WARNING presents safety information to PREVENT INJURY OR DEATH to the technician

or user.

745-814-B0-001, Rev. A 
 1.0 Introduction
The AlphaNet DSM Series Embedded DOCSIS Transponder (XP-DSM) allows monitoring of Alpha
XM2 and GMX power supplies through existing cable network infrastructure. Advanced networking
services provide quick reporting and access to critical powering information.
The XP-DSM utilizes Simple Network Management Protocol (SNMP) and standard 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.

Primary Features:
• 10/100 Mbps auto-negotiating standard interface
• Supports SNMPv1, v2c
• Extensive power supply diagnostic MIBs
• Embedded Web server for direct diagnostics
• Directly monitors up to two 36V or 48V battery strings
• Environmentally hardened DOCSIS cable modem and transponder
• Supports both Single IP and Dual IP applications
• Single XP-DSM supports communications and system control for up to three XM2 power supplies
and an AlphaGen™ backup generator system
• Automatic firmware upgrades
• Configuration cloning
• Local port provides technician access to extensive power supply diagnostics

Cable Modem

Transponder

Fig. 1-1, AlphaNet XP-DSM

 745-814-B0-001, Rev. A
 2.0 System Overview
2.1 System Diagram
10 MIB Browser

1 Power Supply 2 XP-DSM

4 Coax/HFC Network 5 CMTS 6 TCP/IP Network
ALM
RDY
COM
LNK

RF
REG
DS
TMPR

CTRL

C
O
M
E
Battery T
H
Breaker
C
N+1 N+1 OUTPUT 2 D

Battery A
B
Input L
O
OUTPUT 1B LRI OUTPUT 1A C
A
L

Temp
Probe

3 Local Computer

7 DHCP Server 8 TFTP Server 9 TOD Server

11 Web Browser

1 All power supply, battery, and generator data are stored in the class information base (CIB) tables in
the power supply. These data are 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.
2 The XP-DSM is comprised of a cable modem and a transponder. The transponder contains both
SCTE-HMS management Information base (MIBs) and the propriety Alpha MIB tables. The SCTE-
HMS MIBs are industry standard MIB tables that store power supply, battery, and generator data from
the CIB tables (see Section 6.1). The Alpha MIB contains all the data of the SCTE-HMS MIBs plus
additional power supply settings and values, and transponder data.

3 Power supply and transponder parameters can be monitored and set locally using a personal
computer and a Local Port Adapter (Alpha P/N 745-826-21) (see Section 4.0).
4 The XP-DSM 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 XP-DSM’s cable modem communicates directly with the CMTS.
The following ports of the Transmission Control Protocol/Internet Protocol network must be opened:
6
161 = SNMP 162 = SNMP Traps 69 = TFTP 80 = HTTP
7 The Dynamic Host Configuration (DHCP) server needs to be provisioned with the XP-DSM’s cable
modem RF MAC Address: the MAC Address needs to be assigned a DOCSIS Configuration File (see
Section 3.1).
8 The DOCSIS Configuration File should be saved in the TFTP Root Directory of the Trivial File
Transfer Protocol (TFTP) Server. If used, a DSM Setup File should be placed in the same location. To
build DOCSIS Configuration or DSM Setup Files, see Section 3.0.

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

10 A Network Management System (NMS) or MIB Browser allows remote monitoring of parameter
values and changing of settings in MIB tables. SCTE-HMS and Alpha MIBs must be installed in the
browser (Section 6.0). Alarms and traps can be set and monitored (see Section 6.3).

11 In both Single and Dual IP Modes, power supply parameters can be monitored on an internal network
Web browser. In Dual IP Mode only, the transponder is given an IP address independent of the cable
modem and parameters can be monitored on the public network (see Section 2.2).

745-814-B0-001, Rev. A 
 2.0 System Overview, continued

2.2 Single IP Mode vs. Dual IP Mode Overview

The XP-DSM can operate in either Single (default) or Dual IP Mode. To switch the
transponder from Single to Dual IP Mode the “Block CPE” function must be disabled in the
Discrete Menu of the Alpha MIB (see Section 6.2).

Single IP Mode
In Single IP Mode all data from both the cable
One CM IP address only
modem and power supply are accessed and accessible on the private (LAN)
managed through the modem’s IP address network with access to both CM
and transponder data.
on the secure private modem network. The
transponder is not accessible from the public XP-DSM
(Customer Premises Equipment) network. Cable Modem Transponder
Consequently, the Network Management
MIB Tables
System (NMS) that monitors the power supplies
must have access to the same private modem
network. Fig. 2-1, Single IP Mode
Single IP Mode Considerations:
• Communication with the transponder is limited to the private LAN network, and is
very secure.
• Where the IP address pool is limited, there is no need to issue the transponder a
CPE IP address.
• Access to the transponder is limited to the private LAN network making data
management less versatile, especially for field personnel.

Dual IP Mode
CM IP address, CM and
In Dual IP Mode the transponder acts like transponder data; accessible on
the private (LAN) network.
a CPE device to the cable modem, and
registers a second IP address on the public
CPE network. This allows the power supply XP-DSM
data to be accessed and managed from Cable Modem Transponder (CPE)
anywhere within the public (CPE) network. MIB Tables

Dual IP Mode Considerations:

• The transponder is accessible on Fig. 2-2, Dual IP Mode
the public (CPE) network. This
CPE IP address, transponder
makes data management more data only; accessible on the
versatile. public (CPE) network.

• Because the transponder is a CPE on the public network, access is less secure.
• The CPE requires its own IP address, which may be in short supply.

NOTE:
The transponder settings determine whether the system operates in Dual or Single IP Mode. The cable
modem always interacts with the transponder both as a CPE and as an extension of its own IP address.

10 745-814-B0-001, Rev. A
 2.0 System Overview, continued

2.3 Network Connectivity Overview

The XP-DSM cable modem must be recognized by the CMTS as a valid device to be
assigned an IP address from the DHCP server, locate the TFTP and TOD servers, and
communicate with the SNMP management server (trap receiver) (see Section 2.5).
CMTS and system vendors use different security methods to insure network integrity, but
common considerations are:

• MAC filtering may have to be modified to allow RF MAC registration of addresses starting
with 00.05:CA and 00:03:08.

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

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

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

• For Web access with firmware version 1.05.0, allow traffic on port 61520.

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

• 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.4 System Configuration and Installation Overview

NOTE:
Before installation read all of the “System Overview” Sections.

XP-DSM installation and setup is comprised of three basic steps:

1. Configuring the Network: provisioning the DHCP Server with the transponder’s MAC
Address (Section 3.1) and assigning it a DOCSIS Configuration File (Section 3.2).
2. Setting Options: There are a number of ways transponder options can be set.
They can be set automatically before or after hardware installation via the DOCSIS
Configuration File or the DSM Setup File (see Sections 3.2 and 3.4), remotely after
installation of the hardware (Section 3.3), or locally by plugging a computer directly
into the transponder’s local port (Section 4.0). The SCTE-HMS and Alpha MIBs
need to be compiled into a MIB browser before it can be used to monitor or set
transponder and power supply parameters (Section 6.0).
3. Field Installation: a straight-forward procedure that consists of installing the XP-
DSM into the power supply (Section 7.0), installing the battery sense wire harnesses
(Section 8.0), and verifying operation (Section 9.0).
These steps can be performed independently of one another. However, configuring the
network prior to field installation will allow the installation to be verified while personnel are
still on-site (Section 9.0). Performing field installation before network configuration—before
the installation can be verified—might result in additional field service calls to correct
mistakes.
Carefully read the following section in order to understand the dependencies within the
system before performing system configuration or hardware installation.

745-814-B0-001, Rev. A 11
 2.0 System Overview, continued

2.5 XP-DSM Start-up and Reboot Routine

TFTP Server Network Management System

6a
TOD Server MIB Browser
TCP/IP Network

6b
DHCP Server Web Browser

6c

Network Devices

CMTS

1 2 3 4 5 6
HFC Network

Cable Modem

DSM Transponder

Local Laptop

Time

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.
1 When the XP-DSM is installed and powered-up, it finds the DOCSIS frequency being used by the
Cable Modem Termination System (CMTS), and establishes communication.
2 The CMTS communicates with the DHCP server to get an IP address for the XP-DSM’s cable
modem. The DHCP server must be provisioned with the XP-DSM’s cable modem RF MAC
address for it to recognize the modem as a valid device (Section 3.1). This means the cable
modem’s RF MAC address must be assigned a specific DOCSIS Configuration File, stored in the
TFTP root directory of the TFTP server (Section 3.2).

3 Once the modem is given an IP address, it is synchronized with the network through the Time of
Day (TOD) Server.
As the modem comes online, the XP-DSM downloads the DOCSIS Configuration file from the
4
THCP Server, which sets modem options (see Section 3.2).

5 The XP-DSM transponder’s options are set according to the DSM Setup File (if used). In Dual IP
Mode, the XP-DSM transponder is given its own IP address as a CPE to the modem (see Section
2.2).

ttery

N+1 N+1 2

ttery
In t
1B I 1A

12 745-814-B0-001, Rev. A
 2.0 System Overview, continued

2.5 XP-DSM Start-up and Reboot Routine, continued

6 Monitoring and Managing Transponder and Power Supply Parameters.

6a A network management system (NMS) is software used to monitor transponder and power
supply parameters on the network. The XP-DSM operates with an any NMS that supports
SCTE-HMS standards.
6b The MIB browser is a valuable networking tool that enables personnel to remotely manage
and configure an individual transponder through the SNMP-HMS and Alpha MIBs. The
SCTE-HMS and Alpha MIBs must be compiled in the MIB browser in order to access all the
power supply and transponder parameters. (see Sections 6.1 and 6.2).
6c A Web interface enables personnel direct, read-only access to transponder and power supply
parameters using a common Web browser. It may be used to verify installation (see Section
9.3). In the default Single IP Mode, only Web browsers inside the private network have
access. While in Dual IP Mode, power supply data can be monitored on the public network
(see Section 2.2).
7 Transponder and power supply parameters can be monitored and options set locally using a
laptop or PC with a Local Port Adapter (Alpha P/N 745-826-21) (Section 4.0).

745-814-B0-001, Rev. A 13
 3.0 Network Configuration and Option Settings

3.1 Provisioning the DHCP Server with the MAC Addresses

In the DHCP server, assign the cable modem’s RF MAC Address with a DOCSIS
Configuration File to set modem communication options (see Section 3.2 to create a DOCSIS
Configuration File).
If desired, the MAC Address can be assigned a DSM Setup File to set transponder options
(see Section 3.4). In Single IP Mode, if a DSM Setup File is not assigned, the transponder
runs on its default settings (see Section 3.3) and inherits community string settings from the
DOCSIS Configuration File.
If operating in Dual IP Mode, the DHCP server must also be provisioned with the
transponder’s CPE MAC Address, and extra security is needed (see Section 3.5)
The XP-DSM can be provisioned with static or dynamic IP addresses.
The RF and CPE MAC addresses are located in a number of places on the XP-DSM, and on
the packing slip, see below.

CPE MAC Address

RF MAC Address
CPE MAC Address

RF MAC Address

Fig. 3-1, Location of MAC Addresses

14 745-814-B0-001, Rev. A
 3.0 Network Configuration, continued

3.2 The DOCSIS Configuration File

A cable modem’s DOCSIS Configuration File is a type-length-value (TLV) file that contains
important operational parameters as defined by the DOCSIS standards. It provides certain
settings for the cable modem. In addition to standard entries, settings in the DOCSIS
Configuration File should include the modem’s community strings and firmware upgrade
parameters. Place the configuration file in the TFTP root directory.
Due to different firmware and manufacturers’ Code Verification Certificate (CVC) files,
separate DOCSIS Configuration Files are required for the two cable modem versions
used with the XP-DSM in order to upgrade modem firmware: If your network includes
both versions, you will need to create two Configuration Files. The cable modem version
is indicated by the Organizationally Unique Identifier (OUI) of the cable modem’s RF MAC
Address (see Section 5.1):
00:03:08 AM
00:05:CA Hitron
To build a DOCSIS Configuration File use a DOCSIS TLV editor program.
See the example Configuration File on the next page.
NOTE:
• The modem community strings should be set in the DOCSIS Configuration File. Failure to set community
strings will result in a less secure system (default community strings will be required).
• For automatically updating modem firmware with the DOCSIS Configuration File, see Section 5.1.

3.2.1 Setting Modem Community Strings in the DOCSIS Configuration File

Set the modem community strings with the DOCSIS Configuration File by including in it
the following SNMP parameters:

MIB Parameter Object ID Description Value

docsDevNmAccessStatus.2 1.3.6.1.2.1.69.1.2.1.7 4
docsDevNmAccessIp.2 1.3.6.1.2.1.69.1.2.1.2 The IP address (or subnet) of the e.g. 10.20.30.0
network management station
docsDevNmAccessIpMask.2 1.3.6.1.2.1.69.1.2.1.3 The IP subnet mask of the e.g. 255.255.255.0
network management stations
docsDevNmAccessCommunity.2 1.3.6.1.2.1.69.1.2.1.4 The community string matched to alphanumeric string
this IP/Mask entry
docsDevNmAccessControl.2 1.3.6.1.2.1.69.1.2.1.5 The level of access granted 1= none
2= read only
3= read/write
Table 3-1, Modem Community String Parameters

NOTE:
In Single IP Mode the community strings set in the DOCSIS Configuration File override any community strings
set in the Alpha MIB for the transponder (Section 3.3).

In Dual IP Mode or if the modem is left unsecured, the XP-DSM transponder reverts to default community
strings. Change these strings through the Alpha MIB (Section 6.2), either manually using a MIB browser or
automatically using a DSM Setup File (Section 3.4).

745-814-B0-001, Rev. A 15
 3.0 Network Configuration, continued

3.2 The DOCSIS Configuration File, continued

3.2.2 Example DOCSIS Configuration File

Example File

Sets Read-Write Community SNMP MIB Object (11) [Len=21]:docsDevNmAccessStatus.1/4

string. Set the IP addresses SNMP MIB Object (11) [Len=21]:docsDevNmAccesslp.1/10.56.21.0
and community strings to fit SNMP MIB Object (11) [Len=21]:docsDevNmAccesslpMask.1/255.255.255.0
your system. SNMP MIB Object (11) [Len=25]:docsDevNmAccessCommunity.1/"RW STRING"
SNMP MIB Object (11) [Len=21]:docsDevNmAccessControl.1/3

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

Sets Read-Only Community SNMP MIB Object (11) [Len=21]:docsDevNmAccesslp.2/10.56.21.0
string. Set the IP addresses SNMP MIB Object (11) [Len=21]:docsDevNmAccesslpMask.2/255.255.255.0
and community strings to fit SNMP MIB Object (11) [Len=25]:docsDevNmAccessCommunity.2/"RO STRING"
your system. SNMP MIB Object (11) [Len=21]:docsDevNmAccessControl.2/2

Sets firmware Software Upgrade Filename(9) [Len=24]:"ModemFirmwareFile.bin

download parameters. SNMP MIB Object (11) [Len=20]:docsDevSwAdminStatus.0/2
Specifies location of DSM
Software Upgrade TFTP Server (21) [Len=4]:10.56.48.15
Setup File atidoc01.cfg
Manufacturer Code Verification Certificate (32) [Len=254]: 30 82 03 1A 30 82...
Sets Code Verification Manufacturer Code Verification Certificate (32) [Len=254]: 04 0A 13 11 41 4D...
Certificate (CVC) Manufacturer Code Verification Certificate (32) [Len=254]: 04 0C 30 0A 06 01...
Manufacturer Code Verification Certificate (32) [Len=36]: 11 A3 41 A6 A7 D9....

Fig. 3-2, Example DOCSIS Configuration File

16 745-814-B0-001, Rev. A
 3.0 Network Configuration, continued

3.3 Setting Communication Options

The XP-DSM ships with the following default communication option settings:
• Access Mode – Single IP
• Network registration – DHCP
• HTTP Web Server – Enabled
• Read Community String – AlphaGet
• Read/Write Community String – AlphaSet
Communications Settings may be changed through the Alpha MIB remotely using a SNMP
MIB browser, automatically using a DSM Setup File (see Section 3.4), or by connecting
directly to the front of the XP-DSM using a PC or laptop and the local port (see Section 4.0).
See Section 6.2 for an explanation of the Alpha MIB.
NOTE:
Before setting options, verify UDP ports 161 and 162, and TCP ports 80 and 69 are not blocked.

SNMP Parameter Local Port Parameter Type Description Value

AtiMgmtSnmpCommGet [Text] SNMP GET Alphanumeric Read Community String AlphaGet (default)
OID: 1.3.6.1.4.1.926.1.3.1.4.1 String
AtiMgmtSnmpCommSet [Text] SNMP SET Alphanumeric Read/Write Community String AlphaSet (default)
OID: 1.3.6.1.4.1.926.1.3.1.4.2 String
atiCibDiscTable [Discretes] BLOCK CM Integer Block access to power supply 0 = Disabled (Default)
1.3.6.1.4.1.926.1.2.1.1 data through modem
1 = Enabled

atiCibDiscTable [Discretes] BLOCK CPE Integer Access Mode (Single/Dual IP) 0 = Dual IP
1.3.6.1.4.1.926.1.2.1.1
1 = Single IP (Default)
atiCibDiscTable [Discretes] TRAP ON NORMAL Integer Send SNMP trap when alarmed 0 = Disabled (default)
1.3.6.1.4.1.926.1.2.1.1 condition returns to normal state
1 = Enabled

atiCibDiscTable [Discretes] HTTP SERVER Integer Display CIB Tables on Web 0 = Disabled
1.3.6.1.4.1.926.1.2.1.1 page
1 = Enabled (default)
atiCibDiscTable [Discretes] HTTP TEXT Integer Display TEXT table on Web 0 = Disabled (default)
1.3.6.1.4.1.926.1.2.1.1 page
1 = Enabled
atiCibTextTable [Text] IP ADDR STATIC IP address Static IP Address Assignment 0.0.0.0 (Default)
1.3.6.1.4.1.926.1.2.1.4
atiCibTextTable [Text] IP NETMASK STATIC IP address Static IP NETMASK 0.0.0.0 (Default)
1.3.6.1.4.1.926.1.2.1.4
atiCibTextTable [Text] IP GATEWAY STATIC IP address Static IP Gateway 0.0.0.0 (Default)
1.3.6.1.4.1.926.1.2.1.4
atiMgmtSnmpTrapTable [Text] SNMP TRAP TARGET IP address SNMP Destination Trap Address 0.0.0.0 (Default)
1.3.6.1.4.1.926.1.3.1.1
atiMgmtSnmpAccessTable [Text] SNMP ACCESS LIST IP address “(Dual IP Only) 0.0.0.0 (Default)
1.3.6.1.4.1.926.1.3.1.2 Restricted DSM SNMP Access”
atiCibCountTable [Counters] RECONFIG TIMER Integer Download interval for DSM 24 (Default)
1.3.6.1.4.1.926.1.2.1.3 Setup File atidoc01.cfg (Hours)
atiCibCountTable [Counters] SNMP COM Integer Time DSM will wait before reset 24 (Default)
1.3.6.1.4.1.926.1.2.1.3 TIMEOUT if SNMP traffic not detected
(Hours)
AtiMgmtSysHttpAccess [Discretes] HTTP SERVER Integer HTTP Web Server SNMP Local Port
OID: 1.3.6.1.4.1.926.1.3.2.2.1
1 = Disable 1 = Enable
2 = Enable 0 = Disable
See Section 10.0 for complete parameter definitions.

Table 3-2, Transponder Communications Parameters

NOTE:
The XP-DSM will inherit the cable modem community string settings provided by the DOCSIS Configuration
File. If the cable modem is left unsecured, the XP-DSM uses the default community strings listed above.

745-814-B0-001, Rev. A 17
 3.0 Network Configuration, continued

3.4 The DSM Setup File

The DSM Setup File, atidoc01.cfg, is an optional type-length-value (TLV) formatted file
similar to the modem’s DOCSIS Configuration File that distributes custom Alpha MIB settings
to all XP-DSMs on a network. Unlike the DOCSIS Configuration File, the DSM Setup File
is made up only of type 11 entries, OIDs supported by the transponder through the Alpha
MIB. The XP-DSM is programmed to check for this file at startup and after every 24 hours of
operation (configurable) and update with the settings defined.
The IP address of the TFTP server where atidoc01.cfg is located must be defined in the
modem’s DOCSIS Configuration File using the parameter docsDevSwServer. This entry
should be defined as type 21 (Software Upgrade TFTP server) and not type 11 (misc. SNMP
entries).
If a DSM Setup File is not used, the transponder will retain its default settings (see Section
3.3) until they are changed manually with a MIB browser or a local computer connected to the
XP-DSM’s local port (see Sections 6.2, 4.0).
Some common parameters set in the DSM Setup File are:
• Switching to Dual IP Mode.
• Setting transponder community strings in Dual IP Mode, see Section 3.4.3.
• Upgrading transponder firmware, see Section 5.2.
• Disabling or enabling the transponder’s Web server.
• Enable ‘Trap on Normal’, see Section 6.3.
• Setting SNMP trap addresses, see Section 6.3.
• Setting power supply parameters (Alpha recommends contacting your Alpha
representative before changing power supply settings).
NOTE:
The procedure in this section applies to firmware version 1.08.0 or newer. For an application to upgrade from
earlier firmware versions, go to www.Alpha.com>Broadband>StatusMonitoring>DSM>XP-DSM Downloads.

3.4.1 Building the DSM Setup File

To build a DSM Setup File, enter SNMP parameters and values from the Alpha MIB
(see Section 6.2) inside a TLV file using a TLV editor.
The entry atiMgmtSysDownloadCfgCheckProgress with the value of 3 is the file
marker that the XP-DSM looks for to begin reading entries and must be the first entry
in the file.

The DSM Setup File must be named atidoc01.cfg and placed in the root directory of
the TFTP server.
XP-DSM settings are updated according to values defined in this file at startup and
after every 24 hours of operation.
See the example file on the next page.
NOTE:
Most TLV editors will display the parameter name instead of the Object ID if the SNMP MIB file ATI-TABLES-
MGMT-MIB.mib is copied into the installation directory of the TLV editor. This makes the file more readable.

18 745-814-B0-001, Rev. A
 3.0 Network Configuration, continued

3.4 The DSM Setup File, continued

3.4.2 Example of an atidoc01.cfg DSM Setup File

Below is an example DSM Setup File with the following settings:

Example DSM Setup File Parameters and Values

Parameter Type Description Value
atiMgmtSysDownloadCfgCheckProgress Integer Required file marker entry 3
OID: 1.3.6.1.4.1.926.1.3.2.1.12.0
atiMgntSnmpTrapAddress1 IP address Optional SNMP trap destination address 10.80.0.2
OID: 1.3.6.1.4.1.926.1.3.1.1.
atiMgntSnmpTrapAddress2 IP address Optional SNMP trap destination address 70.45.94.130
OID: 1.3.6.1.4.1.926.1.3.1.1.
atiCibDiscValue.sys.1.6 Integer Sets XP-DSM into Dual IP Mode 1 = single IP (default)
OID: 1.3.6.1.4.1.926.1.2.1.1.1.5.14.1.6
0 = dual IP
atiMgmtSnmpSnmpv1Access Integer Required to allow remote SNMPv1 access to 1 = disable
OID: 1.3.6.1.4.1.926.1.3.1.3.1.0 power supply data
2 = enable (default)
atiMgmtSnmpSnmpv2Access Integer Required to allow remote SNMPv2 access to 1 = disable
OID: 1.3.6.1.4.1.926.1.3.1.3.2.0 power supply data
2 = enable (default)
atiMgmtSysHttpAccess Integer Enables embedded HTTP Web server to allow 1 = disable
OID:1.3.6.1.4.1.926.1.3.2.2.1.0 XP-DSM data to be visible from Internet Web
browser. 2 = enable (default)

Firmware Download
atiMgmtSysDownloadTftpAddress IP address Address of modem’s TFTP server 10.20.13.3
OID: 1.3.6.1.4.1.926.1.3.2.1.1.0

atiMgmtSysDownloadFile1 Filename Firmware filename esm1100_.phy

OID: 1.3.6.1.4.1.926.1.3.2.1.4.0
atiMgmtSysDownloadCtrl Integer “Trigger” file initiates firmware upgrade 1
OID: 1.3.6.1.4.1.926.1.3.2.1.2.0
See Section 10.0 for complete parameter definitions.
Table 3-3, Example DSM Setup File Parameters and Values

Example DSM Setup File

File: atidoc01.cfg
Network Access Control (3) [Len - 1]: 1
SNMP MIB Object (11) [Len = 23]: atiMgmtSysDownloadCfgCheckProgress.0 / 3
SNMP MIB Object (11) [Len = 24]: atiMgntSnmpTrapAddress1 / 10.80.0.2
SNMP MIB Object (11) [Len = 24]: atiMgntSnmpTrapAddress2 / 70.45.94.130
SNMP MIB Object (11) [Len = 26]: atiCibDiscValue.sys.1.6 / 1
SNMP MIB Object (11) [Len = 23]: atiMgmtSnmpSnmpv1Access.0 / 2
SNMP MIB Object (11) [Len = 23]: atiMgmtSnmpSnmpv2Access 0 / 2
SNMP MIB Object (11) [Len = 23]: atiMgmtSysHttpAccess 0 / 2
SNMP MIB Object (11) [Len = 23]: atiMgmtSysDownloadTftpAddress.0 / 10.20.13.3
SNMP MIB Object (11) [Len = 31]: atiMgmtSysDownloadFile1.0 / “esm1100_.phy”
SNMP MIB Object (11) [Len = 23]: atiMgmtSysDownloadCtrl.0 / 1

745-814-B0-001, Rev. A 19
 3.0 Network Configuration, continued

3.4 The DSM Setup File, continued

3.4.3 Setting Transponder Community Strings with the DSM Setup File
The default transponder read-only community string is AlphaGet. The default read-write
community string is AlphaSet. These community strings are overridden by modem
community strings set in the DOCSIS Configuration File. If the modem is left unsecured
or if operating in Dual IP Mode, the XP-DSM needs to have its community strings
set in the Alpha MIB. This can be done with the DSM Setup File by including the
following parameters:

Parameter Type Description Value

AtiMgmtSnmpCommGet Alphanumeric Read Community [desired value]
OID: 1.3.6.1.4.1.926.1.3.1.4.1 String String
AtiMgmtSnmpCommSet Alphanumeric Read/Write [desired value]
OID: 1.3.6.1.4.1.926.1.3.1.4.2 String Community String

Table 3-4, Transponder Community String Parameters

20 745-814-B0-001, Rev. A
 3.0 Network Configuration, continued

3.5 Security in Dual IP Mode

In Dual IP Mode additional SNMP security is required because data is exposed on the CPE
network, which is more vulnerable to packet sniffing and community string deciphering than
on the secure cable modem network. For an explanation of Dual IP Mode, see Section 2.2.
For an explanation of the Alpha MIB, see Section 6.2.
There are two methods of providing SNMP Security in Dual-IP Mode: the Secure Access List,
and the Key-Match.
Method 1: Security Using the Secure Access Table
The Secure Access List method limits remote SNMP access to four IP addresses. Only those
IP addresses listed in the SNMP Access Table are able to read or write to the Alpha MIB
parameters from the public (CPE) network. Set the IP addresses through the following Alpha
MIB parameter:

SNMP Parameter Local Port Parameter Description Type Value

atiMgmtSnmpAccessTable [Text] SNMP ACCESS LIST Restricted DSM IP address 0.0.0.0 (Default)
1.3.6.1.4.1.926.1.3.1.2 SNMP Access”

The entries in the SNMP Access Table can be set through the local port (see Section 4.0), the
DSM Setup File (see Section 3.4), or remotely using SNMP.
NOTE:
If the entries in the SNMP Access Table are set remotely using SNMP through the cable modem’s IP address,
then the SNMP community strings will have to be used. However, if they are set remotely through the public
(CPE) IP address the data access key, explained below, must be used to gain access.
The XP-DSM transponder variables will still be accessible through the private modem
management network using the community strings without requiring additional security.

Method 2: Security Using the Data Access Key

SNMP Parameter Local Port Parameter Description Type Value

atiMgmtSnmpAlphaSetAccess [Discretes] ALPHA SNMP SETS Set to Access Key Read/Write Set to match the value of
1.3.6.1.4.1.926.1.3.1.3.3.0 Octet String atiMgmtSnmpAlphaSetKey
atiMgmtSnmpAlphaSetKey [Text] ALPHA SNMP SETS Data Access Key Read/Write CIBSET (default)
1.3.6.1.4.1.926.1.3.1.3.4.0 Octet String
ALPHA SNMP SETS [Discretes] ALPHA SNMP SETS OID of Dicrete Table Read/Write 0 = Disabled
1.3.6.1.4.1.926.1.2.1.1.1.5 Value Integer
1 = Enabled

If in Dual IP Mode and not using the Secure Access List Method (above),
atiMgmtSnmpAlphaSetAccess is the only SNMP parameter 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 write access is granted to all
parameters in the Alpha MIB tree. When this access is granted, the value of ALPHA SNMP
SETS in the discretes table automatically switches to ‘1’, enabled. After the operator is
finished setting SNMP variables, SNMP-write access can be disabled by either manually
setting this value to ‘0’ or by setting atiMgmtSnmpAlphaSetAccess to any value other than the
data access key.
The data access key can be set by changing the value of atiMgmtSnmpAlphaSetKey through
the local port, through SNMP using the modem’s IP address, or through the CPE IP address
once access has been granted and the value of ALPHA SNMP SETS in the discretes table is
‘1’, enabled.

745-814-B0-001, Rev. A 21
 4.0 Using the Local Port
The local port allows a technician to monitor and set XP-DSM parameter values directly using a
personal computer and a Local Port Adapter Cable (Alpha Alpha P/N 745-826-21). Terminal emulation
software is necessary (HyperTerminal is recommended).
Procedure:
1. Launch the terminal emulation software.
ALM
RDY
COM
LNK

RF
REG
DS
TMPR

CTRL

C
O
M
E
Battery T
H
Breaker
C
N+1 N+1 OUTPUT 2 D

Battery A

Serial Communication Settings

B
Input L
O
OUTPUT 1B LRI OUTPUT 1A C
A
L

Temp
Probe

Baud 19200
Data Bits 8
Parity None
Stop Bits 1
Flow Control None Discrete Table
2. Hit ENTER to display the menu of CIB tables. SELECT FROM : ANALOGS CONFIG COUNTERS DISCRETES
TEXT
3. Enter >[first three letters of table] and ENTER >dis
DISCRETES
to display the contents of a table. DEV-A IX NAME VALUE ENM/UNIT SET
----------------------------------------------
Entry Explanation BSS-1 00 GENERAL STATUS 0 OK NO
----------------------------------------------
XM2-1 00 GENERAL STATUS 0 OK NO
SYS-1 06 SNMPv1 1 ENABLED YES XM2-1 01 SELF TEST FAIL 0 OK NO
XM2-1 02 LOW BATT VOLTS 0 OK NO
Modifiable? XM2-1 03 HIGH BATT VOLTS 0 OK NO
XM2-1 04 NO BATTERIES 0 OK NO
Parameter Value Enumerated Value XM2-1 05 BATT TEMP PROBE 0 OK NO
Parameter Index XM2-1 06 LINE ISOLATION 0 OK NO
XM2-1 07 OUTPUT FAILURE 0 OK NO
Power Supply XM2-1 08 OUTPUT OVERLOAD 0 OK NO
XM2-1 09 OUTPUT 1 TRIPPED 0 OK NO
Subsystem XM2-1 10 OUTPUT 2 TRIPPED 0 OK NO
Subsystem Definitions XM2-1 11 CHARGER FAILURE 0 OK NO
XM2-1 12 INPUT FAILURE 0 OK NO
BSS Battery System XM2-1 13 INV DISCONNECTED 0 OK NO
XM2-1 14 INVERTER TEMP 0 OK NO
XM2 Power Supply System XM2-1 15 TAP SWITCH 0 NO NO
XM2-1 16 PIM OPTION 0 NO NO
SYS Transponder System XM2-1 17 N+1 VALID 0 NO NO
ECM Generator System XM2-1 18 SELF TEST 0 OFF YES
XM2-1 19 TEST INHIBIT 0 YES
XM2-1 20 ACCEPT/FLOAT 0 FLOAT YES
4. To set a parameter value, enter: >[table] XM2-1 21 INVERTER ENABLE 1 ON NO
[subsystem] [power supply] [Index] [Value] XM2-1 22 CHARGER ENABLE 1 ON NO
ENTER. XM2-1 23 RESET OUT 1 1 YES
XM2-1 24 RESET OUT 2 0 NO YES
Example Command XM2-1 25 N+1 IN USE
XM2-1 26 SET DEFAULTS
0
0
NO
NO
NO
YES
XM2-1 27 FACTORY TEST 0 OFF NO
To disable SNMPv1, enter the command: XM2-1 28 TAP FUSE FAIL 0 OK NO
XM2-1 29 CONFIG ERROR 0 OK NO
>dis sys 1 6 0 XM2-1 30 N+1 FAULT 0 OK NO
XM2-1 31 BB-CMM/CMT OPT 0 NO YES
Table ----------------------------------------------
Subsystem SYS-1 00 AUTO CONFIG 0 ENABLED YES
SYS-1 01 TAMPER ALARM 0 OK NO
Power Supply Value SYS-1 02 TAMPER ALM WHEN 0 CLOSED YES
SYS-1 03 MGMT MSG TARGET 0 CPE NO
Parameter Index SYS-1 04 BLOCK CM 0 NO YES
Hit ENTER SYS-1 05 BLOCK CPE 0 NO YES
SYS-1 06 SNMPv1 1 ENABLED YES
Result: SYS-1 07 SNMPv2 1 ENABLED YES
SYS-1 08 ALPHA SNMP SETS 1 ENABLED YES
SYS-1 06 SNMPv1 0 DISABLED YES SYS-1 09 TRAP ON NORMAL 0 DISABLED YES
SYS-1 10 HTTP SERVER 1 ENABLED YES
SYS-1 11 HTTP TEXT 0 DISABLED YES
NOTE: SYS-1 12 PING REQUEST 0 YES
Entries in the TEXT Table are transponder parameters SYS-1 13 GET NEW IMAGE 0 YES
and do not have subsystems. SYS-1 14 COM BUS DAT SIZE 0 9 BIT YES
SYS-1 15 DEVICE RESET 0 RUNNING YES
Example: To Update Read/Write Community String to
SYS-1 16 DEBUG MESSAGES 0 ENABLED YES
“ReadString” SYS-1 17 PI CURRENT MODE 0 ENABLED YES
Enter Command: >tex 45 ReadString ----------------------------------------------

22 745-814-B0-001, Rev. A
 4.0 Using the Local Port, continued

Text Table >ana

Analogs Table
>tex ANALOGS
TEXT DEV-A IX NAME VALUE ENM/UNIT SET
---------------------------------------------- ----------------------------------------------
0 [ro] DHCP STATE : DISCOVER SENT BSS-1 00 BATT 1A 0.00 VDC NO
1 [ro] DHCP TIMER : 0 BSS-1 01 BATT 2A 0.00 VDC NO
2 [ro] DHCP SERV : 0.0.0.0 BSS-1 02 BATT 3A 0.00 VDC NO
3 [ro] DHCP SERV 54 : 0.0.0.0
4 [ro] DOWN STAT : BSS-1 03 BATT 4A 0.00 VDC NO
5 [rw] DOWN NAME 1 : BSS-1 04 BATT 1B OR 5A 0.00 VDC NO
6 [rw] DOWN NAME 2 : BSS-1 05 BATT 2B OR 6A 0.00 VDC NO
7 [rw] DOWN IP : 0.0.0.0 BSS-1 06 BATT 3B OR 7A 0.00 VDC NO
8 [rw] DOWN CFG : BSS-1 07 BATT 4B OR 8A 0.00 VDC NO
9 [rw] DOWN CFG IP : 0.0.0.0
10 [rw] NTP SERV : 0.0.0.0 ----------------------------------------------
11 [ro] NTP DHCP : 0.0.0.0 XM2-1 00 INPUT VOLTAGE 118.80 Vac NO
12 [ro] NTP TIME UTC : 01/01/70 00:00:00 XM2-1 01 INPUT FREQ 60.00 Hz NO
13 [ro] ENET ADDR : 00.90.EA.A0.1E.5F XM2-1 02 OUTPUT VOLTAGE 64.00 Vac NO
14 [ro] IP ADDR IN USE : 0.0.0.0 XM2-1 03 OUTPUT 1 CURR 0.00 A NO
15 [ro] NETMASK IN USE : 0.0.0.0
16 [ro] GATEWAY IN USE : 0.0.0.0 XM2-1 04 OUTPUT 2 CURR 0.00 A NO
17 [rw] IP ADDR STATIC : 0.0.0.0 XM2-1 05 PERCENT LOAD 0.00 % NO
18 [rw] NETMASK STATIC : 0.0.0.0 XM2-1 06 OUTPUT VA 0.00 VA NO
19 [rw] GATEWAY STATIC : 0.0.0.0 XM2-1 07 OUTPUT WATTS 0.00 W NO
20 [rw] SNMP TRAP TARGET : 0.0.0.0 XM2-1 08 BATT VOLTAGE 40.40 Vdc NO
21 [rw] SNMP TRAP TARGET : 0.0.0.0
22 [rw] SNMP TRAP TARGET : 0.0.0.0 XM2-1 09 CHARGER CURR 1.20 A NO
23 [rw] SNMP TRAP TARGET : 0.0.0.0 XM2-1 10 BATTERY TEMP 27.50 oC NO
24 [rw] SNMP ACCESS LIST : 0.0.0.0 XM2-1 11 FREQ RANGE 3.00 Hz YES
25 [rw] SNMP ACCESS LIST : 0.0.0.0 XM2-1 12 FLOAT V/C 2.25 YES
26 [rw] SNMP ACCESS LIST : 0.0.0.0 XM2-1 13 ACCEPT V/C 2.35 YES
27 [rw] SNMP ACCESS LIST : 0.0.0.0
28 [ro] sysDescr : ATI P01V1.08.0 XM2-1 14 TEMP COMP 3.00 mV YES
29 [rw] sysName : XM2-1 15 PEAK CURR 1 10.00 A YES
30 [rw] sysContact : XM2-1 16 PEAK CURR 2 10.00 A YES
31 [rw] sysLocation : XM2-1 17 CHGR CURR LIMIT 25.50 A NO
32 [rw] comLogicalID : XM2-1 18 EOD VOLTAGE V/C 1.75 YES
33 [ro] CHECK CODE : 146.51.132.199
34 [rw] PING IP : 0.0.0.0 ----------------------------------------------
35 [rw] ATICONFIG IP : 0.0.0.0 SYS-1 00 INPUT CURRENT 2.30 A NO
36 [rw] ATICONFIG NAME : ----------------------------------------------
37 [ro] TIME UP : 0 00:00:29
38 [ro] CM/RF ENET : 00.03.08.0B.9A.EA
39 [ro] CM IP : 192.168.1.192
40 [ro] CM SUBNET : 255.255.255.0
41 [ro] CM GATEWAY : 192.168.1.1
42 [ro] CM TOD : 192.43.244.18
43 [ro] CM TFTP : 192.168.1.51
44 [rw] SNMP GET : AlphaGet
45 [rw] SNMP SET
46 [rw] SNMP TRAP
: AlphaSet
: public >cou
Counters Table
47 [rw] ALPHA SNMP SETS : CIBSET
---------------------------------------------
COUNTERS
Note: no subsystem DEV-A IX NAME VALUE ENM/UNIT SET
----------------------------------------------
BSS-1 00 NUMBER OF BATTS 0 YES
BSS-1 01 NUMBER OF STRNGS 0 YES
----------------------------------------------
XM2-1 00 TEST INTERVAL 30 DAY YES
XM2-1 01 TEST COUNTDOWN 30 DAY YES
XM2-1 02 TEST DURATION 10 MIN YES
NOTE: XM2-1 03 STANDBY TIME 163 MIN YES
XM2-1 04 STANDBY EVENTS 164 YES
Variables are added and moved between XM2-1 05 RETRY DELAY
XM2-1 06 RETRY LIMIT
60 SEC
20
YES
YES
firmware versions; therefore, the index values XM2-1 07 OVER CURR TOL 3 SEC YES
XM2-1 08 BATT CAPACITY 100 AH YES
may change from the examples. Obtain the XM2-1 09 RESERVED 0 BMP NO
index value from the current displayed table XM2-1 10 DEVICE ADDRESS 1 YES
XM2-1 11 TOTAL RUN TIME 496 DAY NO
prior to updating any values. ----------------------------------------------
SYS-1 00 PING CYCLE TIME 10 MIN YES
SYS-1 01 POLL CYCLE TIME 10 SEC YES
SYS-1 02 POLL RETRIES 5 YES
SYS-1 03 ENGINE BOOTS HI 0 YES
SYS-1 04 ENGINE BOOTS LO 5 YES
SYS-1 05 TRAP SEND COUNT 0 YES
SYS-1 06 SNMP COM TIMEOUT 24 HR YES
SYS-1 07 RECONFIG TIMER 24 HR YES
----------------------------------------------

745-814-B0-001, Rev. A 23
 5.0 Upgrading Firmware
5.1 Upgrading XP-DSM Modem Firmware
The firmware in the XP-DSM’s modem is upgraded using standard DOCSIS methods as
defined in RFC2669 (available at http://www.faqs.org/rfcs/rfc2669.html).
There are two ways to upgrade the modem’s firmware: 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 Configuration File, stored on the TFTP root
directory.
Both methods are explained below. To build a DOCSIS Configuration File, see Section 3.2.

5.1.1 Identifying the Modem and Obtaining Firmware Files

There are two versions of the cable modem in XP-DSMs, each of which requires its
own firmware and manufacturer’s Code Verification Certificate (CVC) files. These
versions can be differentiated by the first three hexadecimal pairs, known as the
Organizationally Unique Identifier (OUI), in their MAC Addresses:

00:03:08 AM
00:05:CA Hitron

The firmware and CVC files for each modem can be downloaded from the XP-DSM
website: www.Alpha.com>Broadband Cable>Status Monitoring>DSM>XP-DSM Tech.
Support. Take care to download the correct firmware and CVC files for your modem
version.

5.1.2 Modem Firmware Upgrade SNMP Parameters

Modem Firmware Upgrade SNMP Parameters

Parameter Type Value
docsDevSoftware
OID: 1.3.6.1.2.1.69.1.3
docsDevSwServer IP address Set to the IP address of the TFTP
OID: 1.3.6.1.2.1.69.1.3.1.0 server from which the firmware will be
downloaded.
docDevSwFilename Octet String Set to the filename of the firmware file
OID: 1.3.6.1.2.1.69.1.3.2.0.4.2.0 downloaded from the Alpha website.
Example: [“firmwareImage.bin”]
docsDevSwAdminStatus Integer 1 = Initiate upgrade
OID: 1.3.6.1.2.1.69.1.3.3.0.4.3.0 2 = Upgrade on next reboot
3 = Ignore update
docsDevSwOperStatus Read Only, 1 = A TFTP download is in progress.
OID: 1.3.6.1.2.1.69.1.3.4.0 Integer 2 = Last upgrade was performed at
reboot
3 = Last upgrade was initiated by
setting docsDevSwAdminStatus to “1”
4 = Firmware upgrade failed
5 = Other
docsDevSwCurrentVers Read Only, The current version of firmware in-
OID: 1.3.6.1.2.1.69.1.3.5.0 Octet String stalled in the modem
Table 5-1, Modem Firmware Upgrade SNMP Parameters

24 745-814-B0-001, Rev. A
 5.0 Upgrading Firmware, continued

5.1 Upgrading XP-DSM Modem Firmware, continued

5.1.3 Upgrading Modem Firmware Manually by Setting SNMP Parameters

1. Download the firmware and CVC files for your version modem from the Alpha
Website.

2. Import the CVC into the modem’s DOCSIS Configuration File (to create a
Configuration File, see Section 3.2).

3. Reset the modem.

4. Set the following MIB parameters using an SNMP MIB browser. Make reference
to the table in Section 5.1.2.
Parameter Value
docsDevSwServer Address of TFTP server
docDevSwFilename Firmware filename
docsDevSwAdminStatus 1
The firmware upgrade will begin immediately. Monitor the upgrade
with the docsDevSwOperStatus MIB parameter, and verify it with the
docsDevSwCurrentVers MIB parameter (see table above). Once the firmware has
been upgraded, the modem will automatically reset to the new version.

5.1.4 Upgrading Modem Firmware in the DOCSIS Configuration File

Modem Firmware can be automatically updated in the DOCSIS Configuration
File by including in it the following docsDevsoftware SNMP parameters and the
manufacturer’s Code Verification Certificate (CVC).

Parameter Value
docsDevSwServer Address of TFTP server
docDevSwFilename Firmware filename
docsDevSwAdminStatus 2
Manufaacturer CVC The CVC file for you modem version

The firmware will be upgraded on the next reboot. Monitor the upgrade with the TFTP
server log of with the docsDevSwOperStatus MIB parameter, and verify it with the
docsDevSwCurrentVers MIB parameter (see table above). Once the firmware has
been upgraded, the modem will automatically reset to the new version.

745-814-B0-001, Rev. A 25
 5.0 Upgrading Firmware, continued

5.2 Upgrading XP-DSM Transponder Firmware

There are three methods to upgrade XP-DSM firmware: manually setting SNMP parameters
remotely in a MIB browser, setting them through the local port (see Section 4.0), and
automatically in the DSM Setup File (to build a Setup File, see Section 3.4). Once the
firmware download process has been initiated the XP-DSM will download the DSM firmware
from the specified TFTP server. The XP-DSM remains fully functional during the upgrading
process and will automatically reset when the upgrade is finished.
The most recent firmware version files are available at www.Alpha.com>Broadband>Status
Monitoring>DSM>XP-DSM Tech. Support.

XP-DSM Firmware Upgrade Parameters

Parameter Local Port Type Value
atiMgntSysDownload Parameter
OID: 1.3.6.1.4.1.926.1.3.2.1
atiMgmtSysDownloadTftpAddress [Text] IP address The IP address of the modem’s TFTP server
OID: 1.3.6.1.4.1.926.1.3.2.1.1 DOWN IP from which the firmware will be downloaded.
atiMgmtSysDownloadCtrl [Discrete] GET Integer 1 = Initiate Download of firmware file
OID: 1.3.6.1.4.1.926.1.3.2.1.2 NEW IMAGE 2 = Initiate Download of two firmware files (ver-
sion 1.05.0)
3 = Idle
atiMgmtSysDownloadStatus [Text] Read Only 1 = Idle
OID: 1.3.6.1.4.1.926.1.3.2.1.3 DOWN STAT Integer 5 = Transferring
6 = Testing
8 = Error
atiMgmtSysDownloadFile1 [Text] Octet String Set to the filename of the firmware file
1.3.6.1.4.1.926.1.3.2.1.4 DOWN NAME 1 downloaded from the Alpha Website.
atiMgmtSysDownloadProgress Integer Byte count of firmware download process.
OID: 1.3.6.1.4.1.926.1.3.2.1.6
atiMgmtSysDownloadSysDescr Octet String Firmware version. Alpha will provide this value
OID: 1.3.6.1.4.1.926.1.3.2.1.7 with released firmware.
atiMgmtSysDownloadSysObjectID OID 1.3.6.1.4.1.926.1.99.1.1.1 (OID embedded in
OID: 1.3.6.1.4.1.926.1.3.2.1.8 transponder to ensure firmware compatibility.)
atiMgmtSysDownloadCfgCheckProgress Integer 3 (file maker, only used with DSM Setup File.)
OID: 1.3.6.1.4.1.926.1.3.2.1.12
See Section 10.0 for complete parameter definitions.

Table 5-2, Transponder Firmware Upgrade SNMP Parameters

NOTE:
By using a DSM Setup File, all the transponders on a network can be automatically upgraded in only one step
(see Section 3.4).
NOTE:
The procedures in this section presuppose firmware version 1.08.0 or newer. For an application to upgrade
from earlier firmware versions, go to www.Alpha.com>Broadband>Status Monitoring>DSM>XP-DSM Tech.
Support.

26 745-814-B0-001, Rev. A
 5.0 Upgrading Firmware, continued

5.2 Upgrading XP-DSM Transponder Firmware, continued

5.2.1 Remotely Upgrading XP-DSM Firmware

This section explains how to upgrade the XP-DSM firmware from version 1.08.0 to
a more recent version by manually setting SNMP parameters. Firmware can also be
upgraded automatically (see Section 5.2.2).

Procedure:

1. Download the most recent firmware version from the Alpha Website and load it
on the TFTP server.

2. Using a MIB browser or the local port, set the following Alpha MIB parameter
values:

Parameter Local Port Parameter Value

atiMgmtSysDownloadTftpAddress [Text] DOWN IP Address of TFTP server
atiMgmtSysDownloadFile1 [Text] DOWN NAME 1 Firmware filename, e.g. “esm1100_.phy”
atiMgmtSysDownloadCtrl [Discretes] GET NEW 1 (initiate download of one firmware file)
IMAGE

3. The firmware download process can be monitored with the TFTP server logs, or
with the following parameters:
atiMgmtSysDownloadStatus: Displays the status of the upgrade.
atiMgmtSysDownloadProgress: Displays bytes transferred.

The transponder will automatically reset after the download is complete (5-10
minutes).

4. The firmware upgrade can be verified by checking the firmware version in the
SCTE-HMS MIB parameter commonVenderInfo (OID: 1.3.6.1.4.1.5591.1.3.1.5.0).

5.2.2 Upgrading XP-DSM Firmware Using a DSM Setup File

NOTE:
The procedure in this section applies to firmware version 1.08.0 or newer. For an application to upgrade from
earlier firmware versions, go to www.Alpha.com>Broadband>Status Monitoring>DSM>XP-DSM Downloads.

This section explains how to upgrade the XP-DSM firmware from version 1.08.0
to a more recent version automatically using a DSM Setup File. The XP-DSM is
programmed to look for a DSM Setup File file named atidoc01.cfg at start-up and
after every 24 hours of operation. The XP-DSM will update its SNMP settings based
on the contents of this file. By building a DSM Setup File that includes specific
Alpha MIB parameters and values, all the XP-DSMs on a network can be upgraded
simultaneously. See Section 3.4 for a full explanation of the DSM Setup File.

Procedure:

1. Download the most recent firmware version from the Alpha Website and load it
on the TFTP server.

2. Create a Type-Length-Value Setup File named atidoc01.cfg, as described in

Section 3.4.

745-814-B0-001, Rev. A 27
 5.0 Upgrading Firmware, continued

5.2 Upgrading XP-DSM Transponder Firmware, continued

5.2.2 Upgrading XP-DSM Firmware Using a DSM Setup File, continued

3. Include in the atidoc01.cfg Setup File the following Alpha MIB parameters and
values:

Parameter Local Port Parameter Value

atiMgmtSysDownloadReCfgTime [Counters] RECONFIG TIMER 0 (disable automatic upgrade)
atiMgmtSysDownloadTftpAddress [Text] DOWN IP Address of TFTP server
atiMgmtSysDownloadFile1 [Text] DOWN NAME 1 Firmware filename, e.g. “esm1100_.phy”
atiMgmtSysDownloadCtrl [Discretes] GET NEW IMAGE 1 (initiate download of one firmware file)
atiMgmtSysDownloadSysDescr NA Provided with firmware release notes,
e.g. ”ATIP01V1.12.0_”
atiMgmtSysDownloadSysObjectID NA OID embedded in transponder to
ensure firmware compatibility, provided
with release notes

4. Load the atidoc01.cfg setup file onto the TFTP server.

5. Within 24 hours all XP-DSMs on the network will begin downloading the new
firmware.

28 745-814-B0-001, Rev. A
 6.0 Data Management

The XP-DSM remotely reports power supply data and alarms using the Simple Network Management
Protocol (SNMP) over the DOCSIS (Data Over Cable Service Interface Specification) communication
specification. The XP-DSM 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 XP-DSM for power supply data with the option of
having the XP-DSM send SNMP traps in the event that an alarm condition is met. In addition to the
SCTE-HMS MIBs, the XP-DSM also supports the Alpha proprietary SNMP MIB (the Alpha MIB),
which allows direct access to the power supply as well as the ability to change transponder settings.
Power supply and transponder settings can also be viewed and set with a local PC via the local
port on the front of the XP-DSM (see Section 4.0). Transponder and power supply data can also be
monitored with an Internet Web browser.

Web Browser: http

Network Management System (NMS)
or MIB Browser: SNMP

XP-DSM SCTE-HMS MIBs Alpha MIB

Local Computer: RS485

ALM
RDY
COM
LNK

Power Supply Data

RF
REG
DS
TMPR

CTRL

C
O
M
E
Battery T
H
Breaker
C
N+1 N+1 OUTPUT 2 D

Battery A
B
Input L
O
OUTPUT 1B LRI OUTPUT 1A C
A
L

Temp
Probe

This Data Management section contains the following subsections:

• The SCTE-HMS MIB: Section 6.1.
• The Alpha MIB: Section 6.2.
• SCTE-HMS Configurable Alarms: Section 6.3.1.
• Distributing Alarm Settings: Section 6.3.2.
• SNMP Traps: Section 6.3.3.
• General Power Supply Alarms: Section 6.3.4.

745-814-B0-001, Rev. A 29
 6.0 Data Management, continued

6.1 The SCTE-HMS MIB

The SCTE-HMS MIB can be monitored with a SNMP compatible Network Management
System (NMS) or with a MIB browser. The following MIB files are required for the MIB
browser to collect data from the transponder. These files can be found on the Society of
Cable Telecommunications (SCTE) Web site: www.scte.org. There are dependencies
between MIB files, so they should be compiled in the following order.

ANSI/SCTE 36 2002 (formerly HMS 028), SCTE-ROOT Management Information Base (MIB)
Definitions
ANSI/SCTE 37 2003 (formerly HMS 072), Hybrid Fiber/Coax Outside Plant Status Monitoring
SCTE-HMS-ROOTS Management Information Base (MIB) Definition
ANSI/SCTE 38-3 2002 (formerly HMS 024), Hybrid Fiber/Coax Outside Plant Status
Monitoring SCTE-HMS-COMMON-MIB Management Information Base (MIB) Definition
ANSI/SCTE 38-1 2004 (formerly HMS 026), Hybrid Fiber/Coax Outside Plant Status
Monitoring SCTE-HMS-PROPERTY-MIB Management Information Base (MIB) Definition
ANSI/SCTE 38-2 2005 Hybrid Fiber/Coax Outside Plant Status Monitoring
SCTE-HMS-ALARMS-MIB Management Information Base (MIB) Definition
ANSI/SCTE 38-4 2006 (formerly HMS 027), Hybrid Fiber/Coax Outside Plant Status
Monitoring SCTE-HMS-PS-MIB Management Information Base (MIB) Definition
ANSI/SCTE 38-6 2006 (formerly HMS 033) Hybrid Fiber/Coax Outside Plant Status
Monitoring SCTE-HMS-GEN-MIB Management Information Base (MIB) Definition

30 745-814-B0-001, Rev. A
 6.0 Data Management, continued

6.1 The SCTE-HMS MIB, continued

scteRoot (1.3.6.1.4.1.5591)
scteHmsTree (1.3.6.1.4.1.5591.1)
propertyIdent (1.3.6.1.4.1.5591.1.1)
propertyTable (1.3.6.1.4.1.5591.1.1.1)
Alarm thresholds for analog measurements
currentAlarmTable (1.3.6.1.4.1.5591.1.1.2)
Real-time view of items in alarm states as defined in
the propertyTable and discretePropertyTable.
discretePropertyTable (1.3.6.1.4.1.5591.1.1.3)
SNMP alarm definitions for discrete parameters
alarmsIdent (1.3.6.1.4.1.5591.1.2)
A historic log of transponder alarms and traps sent
commonIdent (1.3.6.1.4.1.5591.1.3)
commonAdminGroup (1.3.6.1.4.1.5591.1.3.1)
Logical name
Firmware version
Transponder reset
SNMP trap community string
psIdent (1.3.6.1.4.1.5591.1.4)
psDeviceTable
Input voltage
Output voltage
Battery string voltage
Inverter status
Major alarm
Tamper
Remote self-test
psStringTable (1.3.6.1.4.1.5591.1.4.3)
Battery charging currents
psBatteryTable (1.3.6.1.4.1.5591.1.4.4)
Individual battery voltages
psOutputTable (1.3.6.1.4.1.5591.1.4.5)
Output Current
psTemperatureSensorTable (1.3.6.1.4.1.5591.1.4.6)
Battery temperature
genIdent (1.3.6.1.4.1.5591.1.6)
Generator monitoring
transponderInterfaceBusIdent (1.3.6.1.4.1.5591.1.7)
Monitoring of externally connected devices e.g.
multiple power supplies daisy-chained to a single
XP-DSM

Table 6-1, SCTE-HMS MIB Hierarchy

745-814-B0-001, Rev. A 31
 6.0 Data Management, continued

6.2 The Alpha MIB

Measurements and settings for the power supply, generator, batteries, and XP-DSM
are accessed using Simple Network Management Protocol (SNMP) through the Alpha
Management Information Base (MIB). The Alpha MIB is defined through the SNMP
MIB file ATI-TABLES-MGMT-MIB.mib, which can be obtained from the www.Alpha.
com>Broadband>Status Monitoring>DSM>XP-DSM Tech. Support page. Many MIB browsers
such as MG-Soft (www.mg-soft.com) require this MIB to be compiled into the browser in order
for the branches and parameters to be ordered and displayed properly. Refer to your MIB
browser’s documentation for instructions on compiling MIB files.
The Alpha MIB is defined within the enterprise branch of the MIB tree starting at
1.3.6.1.4.1.926, and is organized into three branches:
Alpha CIB Tables
All of the power supply, generator, battery, and most of the XP-DSM data and settings are
located in the CIB Tables. These tables are sorted into four categories: Analogs, Counters,
Discretes, and Text.
Analogs: voltages, currents, frequency, temperatures.
Counters: XM2 self-test schedule, communications and configuration settings.
Discretes: XM2 major alarms, single/dual IP, tamper polarity, SNMP communications,
SNMP traps, Web server.
Text: XP-DSM communications settings, IP addresses, DHCP server, XP-DSM
firmware version, static/dynamic IP address, DSM Setup File.
Alpha Management
Advanced DSM settings are located in the Alpha Management branch and are split between
SNMP and system-related settings.
SNMP Management: SNMP trap tables, Dual IP security, SNMP access, and community
strings.
System Management: firmware download, Web server, SNTP Server location, enclosure
environmental controller.
Alpha Technologies IDs
The Alpha Technologies IDs branch is used by internal DSM processes to identify the model
of the transponder for firmware upgrades and other functions.

32 745-814-B0-001, Rev. A
 6.0 Data Management, continued

6.2 The Alpha MIB, continued

The Alpha MIB hierarchy (see Section 10.0 for a list and definitions of all Alpha MIB
parameters).
enterprises (1.3.6.1.4.1)
alphaTechInc (1.3.6.1.4.1.926.1)
Alpha CIB Tables atiTables (1.3.6.1.4.1.926.1.2)
atiCibTables (1.3.6.1.4.1.926.1.2.1)
atiCibDiscTable (1.3.6.1.4.1.926.1.2.1.1) (Discrete Table)
XM2 Major Alarms
Advanced Settings
DSM Settings

Contents
Single/Dual IP (Block CPE)
Tamper Polarity
SNMP Communications Enable
SNMP Trap on Normal Condition
Web Server Enable
atiCibAnaTable (1.3.6.1.4.1.926.1.2.1.2) (Analog Table)
Voltages
Contents

Currents
Frequency
Temperatures: power supply, batteries, generator
atiCibCountTable (1.3.6.1.4.1.926.1.2.1.3) (Counters Table)
Power Supply Self-Test
Contents

Communications Settings
Configuration Settings
atiCibTextTable (1.3.6.1.4.1.926.1.2.1.4) (Text Table)
DSM Communications Settings
IP Addresses
Contents

DHCP Server
DSM Firmware Version
Set Static IP address
DSM Configuration File
Alpha Management
atiManagement (1.3.6.1.4.1.926.1.3)
atiMgntSnmp (1.3.6.1.4.1.926.1.3.1.0)
SNMP Trap Tables
Contents

Dual IP Security
SNMP Access Enable
Community Strings
atiMgntSys (1.3.6.1.4.1.926.1.3.2)
Firmware Download
Contents

Web Server Enable

SNTP Server Location
Alpha Technologies IDs
alphaTechIncIDs (1.3.6.1.4.1.926.1.99)
Contents

Internal DSM processes to identify the transponder model

for firmware upgrades and other functions.

745-814-B0-001, Rev. A Table 6-2, Alpha MIB Hierarchy 33

 6.0 Data Management, continued

6.3 SCTE-HMS MIB 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 MIB tables
can be defined and set to provide a custom monitoring system.

6.3.1 SCTE-HMS Configurable Alarms

The SCTE-HMS MIB tables can be configured to send SNMP traps to a network
management system in response to certain power supply conditions. The tables
used to define these alarms are the propertyTable and the discretePropertyTable,
which are both located in the propertyIdent MIB at OID 1.3.6.1.4.1.5591.1.1. When
an alarm condition is detected in either of these tables, an entry is created in the
alarmTable, and an alarmEvent SNMP trap is sent by the transponder to the SNMP
trap address.

propertyTable: Analog Alarms

Each variable in this table corresponds to an analog value of the power supply. The
alarms are disabled by default, and may be enabled and configured to suit monitoring
preferences. Each entry in the propertyTable has four possible alarm threshold levels:

Threshold Level Definition

LOLO alarm threshold for extreme low condition
LO alarm threshold for low condition
HI alarm threshold for high condition
HIHI alarm threshold for extreme high condition

There is also a ‘Deadband’ setting used as a buffer to prevent alarm oscillation when
the analog value transitions from an alarm state to a non-alarm state. The value must
exceed the alarm threshold by the amount of the deadband value before the alarm
will clear.

An alarm for a parameter in the table is enabled by setting its ‘alarmEnable’ bit-mask.
By setting the bits, the user can define which threshold levels are enabled. A “1” in a
bit position indicates the threshold level is enabled. This bit mask is converted to Hex
within the table.

For example, to set an alarm for only HI level values of a parameter, then set Bit 2 to
“1”, represented by 00000100 binary, or 04 Hex. To set alarms for all threshold levels,
enable Bits 0 through 3 by setting them to “1” represented by binary 00001111, or 0F
Hex.

See the table and example on the next page.

NOTE:
• Some programs, such as MG-Soft, use a Hex notation where 0F, for example, is rendered 0x0F. There is
no difference in the binary meaning of this notation.

• Most of the values in the propertyTable are scaled 1/100. For example, 43V is rendered 4300. See Table
6-4.

34 745-814-B0-001, Rev. A
 6.0 Data Management, continued

6.3 SCTE-HMS MIB Alarms, continued

6.3.1 SCTE-HMS Configurable Alarms, continued

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
Table 6-3, Binary to Hex Conversions for Alarm Settings

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 degrees, and 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 field is set to 0F Hex to monitor and alarm for all conditions.

psTemerature

745-814-B0-001, Rev. A 35
 6.0 Data Management, continued

6.3 SCTE-HMS MIB Alarms, continued

6.3.1 SCTE-HMS Configurable Alarms, continued

The following table displays the various analog alarms with common settings.

Analog Alarms and Common Settings

Alarm
Analog Alarms Description LOLO LO HI HIHI Deadband
Enable
psTotalStringVoltage 36V Scaled representation of the full 0x0F 3120 3140 4510 4530 .1V
battery string in 1/100 Volts units
48V 0x0F 4160 4185 6015 6040 .1V
psBatteryVoltage Battery Voltage of 12V battery, 0x0F 970 1000 1530 1550 .1V
scaled 1/100 V
psInputVoltage 120V Scaled representation of the 0x0F Varies by site. The XM2 will switch to standby at
input line voltage in 1/100 Volts Nominal +15% -20%
220V units 0x0F

psOutputVoltage 48V Scaled representation of the 0x0F 4300 4550 5050 5300 1V
power supply output voltage in
60V 0x0F 5650 6000 6600 7000 1V
1/100 Volts units.
90V 0x0F 7830 8265 9135 9570 1V
psPowerOut Representation of power supply 0x00 Monitor Output Current Instead
output power in 1W
psStringChargeCurrent Battery string charge current, 0x0C Disable Disable 1200 1250 0.2A
scaled at 1/100 Amp
psStringFloat Battery string float charge 0x0C Disable Disable 1200 1250 0.2A
current, scaled at 1/100 Amp
psStringDischargeCurrent Battery string discharge current, 0x00 Not Supported by XM2/GMX
scaled at 1/100 Amp
psOutputCurrent 15A Scaled representation of power 0x0C Disable Disable 1725 1875 0.2A
supply RMS current in 1/100
22A 0x0C Disable Disable 2530 2750 0.2A
Amp units
psTemperature -40 to +80 degrees C 0x0F Varies by site

Table 6-4, Analog Alarms and Common Settings

36 745-814-B0-001, Rev. A
 6.0 Data Management, continued

6.3 SCTE-HMS MIB Alarms, continued

6.3.1 SCTE-HMS Configurable Alarms, continued

discretePropertyTable: Discrete Alarms

This table holds the alarmable discrete objects that are passed from the power
supply to the transponder. The SCTE-HMS-PS-MIB file defines all supported objects
in this table, including the different states and dependencies of each object. An object
must both be in this file and be supported by the power supply and transponder
before it will show up in the discretePropertyTable. Through this table, how an object
is alarmed when it transitions to the different states is defined.

Discrete alarms settings are programmable using three values: enable major, enable
minor, and disable. The discrete alarms represent the value of the alarm as defined
by the network, and are distinct from the power supply alarms. For example, the
discrete alarm for a psMajorAlarm (power supply major alarm, see Section 6.3.2)
may be set as “enable minor” (network alarm setting). In this case, a power supply
major alarm is reported to the network as a minor alarm. If an object transitions
into a state set at enableMinor or enableMajor, an alarm instance is created in the
currentAlarmTable. This alarm is labeled caasDiscreteMinor or caasDiscreteMajor.
If an object is set to disable, no alarm is generated. To set system discrete
alarms, select edit mode as defined by your MIB browser. Select the alarm in the
“discreteAlarmEnable” column and change the value to the desired setting.

Example:
In the example below, psInverterStatus is set to generate discreteMinor alarms if it
enters a state of “2” or “5,” which are “AC line loss” and “Test Fail” respectively. If the
inverter enters states “1,” “3,” or “4,” no alarm is generated. See the table on the next
page for alarm definitions.

Values of 2
and 5 generate
minor alarms.

NOTE:
discreteMinor and discreteMajor are completely different from psMajor and psMinor, which are defined by the
power supply (see Section 6.3.2). In the Discrete Table, psMajor or psMinor can actually be disabled so that
they would not generate an entry in the currentAlarmTable.

745-814-B0-001, Rev. A 37
 6.0 Data Management, continued

6.3 SCTE-HMS MIB Alarms, continued

6.3.1 SCTE-HMS Configurable Alarms, continued

Discrete Alarm Definitions and Common Settings

Discrete Alarms Discrete Alarm Definition Example
Value Settings
psInverterStatus 1 Inverter is off Disable
psInverterStatus 2 AC Input line loss EnableMinor
psInverterStatus 3 Inverter is in a local test cycle Disable
psInverterStatus 4 Remote inverter test has been Disable
initiated
psInverterStatus 5 The last Inverter test failed. EnableMinor
psMajorAlarm 1 No alarm Disable
psMajorAlarm 2 Service has been dropped or a EnableMajor
service interruption is imminent. This
is a general alarm; the cause of which
can be determined by looking in the
Discretes Table.
psMinorAlarm 1 No alarm Disable
psMinorAlarm 2 A non-service effecting condition has EnableMinor
occurred and should be monitored
psTamper 1 Indicates status of enclosure door EnableMinor
tamper sensor: closed (door is open).
psTamper 2 Indicates status of enclosure door Disable
tamper sensor: open (door is closed).
psInputVoltagePresence 1 Digital value indicating that EnableMinor
line voltage is lost, based on
measurement of input voltage.
psInputVoltagePresence 2 Indicates that line voltage is present Disable
and within tolerance, based on
measurement of input voltage.
transponderInterfaceBusIdent 1 Remote device will respond to Disable
commands from master transponder.
transponderInterfaceBusIdent 2 Local device is under local control and EnableMinor
will not respond to commands from
master transponder.
transponderInterfaceBusIdent 3 Device is not responding. EnableMajor

Table 6-5, Discrete Alarm Definitions and Common Settings

38 745-814-B0-001, Rev. A
 6.0 Data Management, continued

6.3 SCTE-HMS MIB Alarms, continued

6.3.2 Distributing Alarm Settings

Alarm settings can be distributed automatically from one XP-DSM to another. They
can also be distributed to all the XP-DSMs on a network by using a DSM Setup File.
The procedure is a follows:

STEP 1: Make the desired SCTE-HMS alarm settings on a master XP-DSM,

according to the methods described in the sections above.

STEP 2: Create an .s19 image file of the master XP-DSM’s alarm settings.

To create an .s19 image file of the master XP-DSM’s alarm settings, you must first
obtain its SCTE-HMS configuration. This can be done in two ways.

Method A: If the Web server is enabled (default), enter the master XP-DSM’s IP
address followed by “/?X=con” (e.g. http://192.168.1.4/?X=con) into a
Web browser.

Method B: Connect a local computer to the master XP-DSM using the local port
adapter (Alpha P/N 745-826-21). Enter the command >CONFIG at the
prompt.

In either case, the SCTE-HMS configuration should be displayed as follows:

Copy the data between the dashed lines and paste it into a plain text file (Microsoft
notepad or equivalent. Do not use Microsoft Word.). Execute the following steps to
convert this text to an .s19 image:

a. Replace “config ” with “S1” throughout the file. Remove any spaces between
‘S1’ and the remainder of the row.

b. Add the line “S004000043B8” at the beginning of the file.

c. Add the line “S804000000FB” at the end of the file.

d. Ensure there is one extra line entered at the end of the last line in the file. For
example, go to the end of the last row of data and press the <Enter> key once.

745-814-B0-001, Rev. A 39
 6.0 Data Management, continued

6.3 SCTE-HMS MIB Alarms, continued

6.3.2 Distributing Alarm Settings, continued
The .s19 file should now look like the following:

Save the file as “HMScfg.s19” and move it to a TFTP server on the network that is
accessible by the XP-DSMs that you want to update.

STEP 3: Distribute the .s19 file to other XP-DSMs.

The .s19 file is distributed to other XP-DSMs by setting the following Alpha MIB
parameters to the indicated values. This can be done to an individual XP-DSM using
the local port (see Section 4.0) or a MIB browser, or to multiple XP-DSMs by using a
DSM Setup File (see Section 3.4):

XP-DSM Alarm Settings Distribution Parameters

Parameter Local Port Type Value
atiMgntSysDownload Parameter
OID: 1.3.6.1.4.1.926.1.3.2.1
atiMgmtSysDownloadTftpAddress [Text] IP address The IP address of the modem’s TFTP server on
OID: 1.3.6.1.4.1.926.1.3.2.1.1 DOWN IP which HMScfg.s19 is stored.
atiMgmtSysDownloadCtrl [Discrete] GET Integer 1 = Initiate download of .s19 file.
OID: 1.3.6.1.4.1.926.1.3.2.1.2 NEW IMAGE
atiMgmtSysDownloadFile1 [Text] Octet String Set to HMScfg.s19.
1.3.6.1.4.1.926.1.3.2.1.4 DOWN NAME 1

The status of the alarm settings download can be monitored with the following
parameters:

Parameter Local Port Type Value

Parameter
atiMgmtSysDownloadProgress Integer Byte count of file download process.
OID: 1.3.6.1.4.1.926.1.3.2.1.6
atiMgmtSysDownloadStatus [Text] Read Only 1 = Idle
OID: 1.3.6.1.4.1.926.1.3.2.1.3 DOWN STAT Integer 5 = Transferring
6 = Testing
8 = Error

Verify the XP-DSMs’ property tables have been updated using an SNMP manager.

40 745-814-B0-001, Rev. A
 6.0 Data Management, continued

6.3 SCTE-HMS MIB Alarms, continued

6.3.3 SNMP Traps

SNMP alarm traps sent by the XP-DSM are formatted according to the SCTE-HMS-
ALARM-MIB specification with the following information included:
SNMP Trap community string:
commonTrapCommunityString, OID 1.3.6.1.4.1.5591.1.3.1.11.0

Example Alarm Trap

The example below is a psTamper alarm trap indicating a discreteMinor alarm:
tamper is open. The first example is a trap with varbinds and values as translated
through a MG-Soft MIB browser. The second example is a raw trap. See the table of
varbind definitions on the next page.

Example Trap Translated by MG-Soft

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)

Example Raw Trap

Frame 441 (230 bytes ib wire, 230 bytes captured)
Ethernet II, Src: 192.168.1.77 (00:05:ca:29:b4:89), 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)
Specific trap type: 1
Timestamp: 2358751
Object identifier 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 identifier 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 identifier 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 identifier 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 identifier 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, Example SNMP Alarm Trap

745-814-B0-001, Rev. A 41
 6.0 Data Management, continued

6.3 SCTE-HMS MIB Alarms, continued

6.3.2 SNMP Alarm Traps, continued

Varbind Explanation
Binding #1 MAC Address of the transponder
commonPhysAddress
OID: 1.3.6.1.4.1.5591.1.3.2.7.0
Binding #2 Optional user-configurable parameter that is often used to provide a unique logical name, or even
commonLogicalID the physical address of where the transponder is installed.
OID: 1.3.6.1.4.1.5591.1.3.1.1.0
Binding #3 This varbind was designed by the SCTE-HMS committee with the intention of being used by
alarmLogInformation sophisticated trap interpreters. The information is “coded” within the octet strings:
OID: 1.3.6.1.4.1.5591.1.2.3.1.2.1 Octet 1-4: POSIX Time of alarm occurrence (Most significant byte first)
Octet 5: Alarm Type (See description below)
Octet 6: Contents of commonNeStatus immediately after alarm occurred
Octet 7-m: Alarm Object Identifier (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.
Binding #4 This field provides the varbind of the parameter that is alarming along with the value of that
Alarmed Parameter OID/Value parameter. This is the same information encoded in varbind #3 Octets 7 through z.
OID: 1.3.6.1.4.1.5591.1.4.2.1. In the example above the value would be:
27.1 OID: 1.3.6.1.4.1.5591.1.4.2.1.27.1.0 (psTamper)
Value: 2 (Open)
Binding #5 This is the information from varbind #3 Octet 5 above. The alarm location will always be the
Alarm Location/Type SCTE-HMS currentAlarmAlarmState, and the type will be determined based on how the alarm was
OID: 1.3.6.1.4.1.5591.1.1.2.1.2 configured 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 definitions:
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 configured in the SCTE-HMS-PropertyIdent MIB,
whether it is a Discrete or Analog alarm, and the level of alarm defined for that state.

Table 6-6, SNMP Alarm Trap Varbinds and Explanations

Trap on Normal
The XP-DSM has the capability of sending a “return to normal” trap once an alarmed
condition returns to a normal state. This feature is disabled by default, but can be
enabled by setting the ‘TRAP ON NORMAL’ parameter in the atiCibDiscreteTable to
a value of ‘1’. The contents of this trap message will be identical to the SNMP Alarm
traps, but the value of the Alarm ‘Type’ defined in the 5th varbind will be ‘1’ (NOMINAL).
Warm Start Trap
In addition to the SNMP alarm traps, the XP-DSM will also send a warm-start trap
when it is initialized. Some SNMP monitoring software requires this trap for auto-
identification 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
Cold Start Trap
A cold-start trap will be generated by the XP-DSM anytime it initializes with a new
firmware version. This trap should only appear after the first time the XP-DSM has
been reset during a firmware upgrade.
42 745-814-B0-001, Rev. A
 6.0 Data Management, continued

6.3 SCTE-HMS MIB Alarms, continued

6.3.4 General Power Supply Alarms

General power supply alarms are passed directly from the power supply to the
transponder without specific definition and are classified 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 specified. Minor and Major
alarms are defined 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 fixed and after either a successful
completion of a self-test or a complete power cycle of the power supply.
NOTE:
The cause of a psMajor alarm can be determined by checking the Discretes table in the Alpha MIB. The
cause will have the value of “ALARM.”

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

The following table lists the psMajor and psMinor alarm definitions for the XM2 power
supply.

XM2 Major and Minor Alarms

psMinor

Problem Definition
Line Loss from Inverter Status Loss of AC line as determined by power supply inverter.
Battery Temperature Probe Indicates an XM-2 temperature probe has failed or is not connected.
N+1 Error N+1 circuit isn’t configured properly. Possibly detecting input voltage on redundant system or
other issue.
psMajor

Problem Definition
Output Failure (non-latching) AC output failure, open or short detected by power supply.
General Failure (latching) Indicates a latched failure of an automated, local or remote inverter test, or some other major
malfunction within the power supply.
Test Fail (latching) Battery voltage drops below 1.85V/cell or inverter fail during self test.
Battery Fail (non-latching) Battery voltage drops below 1.75V/cell while in standby mode; battery exceeds 2.5V/cell;
Batteries not detected.
Line Isolation (latching) Line isolation circuitry has failed.
Output Overload (non-latching) Indicates XM2 is overloaded. Power supply will shut down and restart periodically.
Charger Failure (non-latching) Charger has failed or was shut down due to problem such as battery over-temp.
Inverter Fail (latching) XM2 has detected a failure in inverter operation.
Configuration Failure XM2 has detected that it is improperly configured.
Overtemp Inverter heat sink over-temperature.
N+1 Active A power supply has failed and the N+1 system has been activated to provide backup power.
Fuse Fail Fuse failed on tap switch option board.

Table 6-7, XM2 Major and Minor Alarms

745-814-B0-001, Rev. A 43
 7.0 Hardware Installation
Before installing the hardware, provision the DHCP server with the cable modem’s RF MAC Address
(see Section 3.1). If operating in Dual IP Mode, provision it with the CPE MAC Address as well. This
allows the installation to be verified 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 field installation, use a service power supply to avoid losing
power to the load.

CAUTION!
The XP-DSM is static sensitive. An ESD wrist strap should be worn when installing the transponder.

7.1 Verifying Power Supply Device Address

Before removing the Inverter Module (IM), 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 XP-DSM can have the same address. Power supplies must have 1, 2,
or 3 as an address. To verify the power supply’s address do the following:

1. Press the Enter key on the inverter module twice to access the SETUP Menu.

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

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

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

5. Press the Up or Down keys until the desired address (1, 2, or

3) is displayed. Remember, each power supply monitored by a single transponder must
have a unique address.

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

7. Press the Enter key again to accept the new data.

8. Press ESC three times to return to the OPERATION NORMAL screen.

44 745-814-B0-001, Rev. A
 7.0 Hardware Installation, continued

7.2 Hardware Installation Procedure

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

1. Switch OFF the power supply’s battery breaker.

2. Unplug all inverter module connections (e.g. battery cable, remote temperature sensor).

3. Loosen the inverter module thumbscrews and slide the inverter module out just enough
to disconnect the ribbon cable. Disconnect the ribbon cable.

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.

Disconnect

Captive Screws

Fig. 7-1, Removing the Inverter Module from the Power Supply

745-814-B0-001, Rev. A 45
 7.0 Hardware Installation, continued

7.2 Hardware Installation Procedure, continued

6. Locate the 18-pin jumper and insert the long side of the jumper firmly into the
side of the inverter module.

Inverter Module

Insert Long Side Into Inverter Module

Fig. 7-2, The 18-pin Jumper

7. Unpack the XP-DSM. If not yet done, record the MAC addresses from the front
of the unit, and report it to the network manager for network provisioning (see
Section 3.1).

8. Line up the 18-pin jumper with the XP-DSM connector and connect the unit to the
inverter module.

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

9. Secure the XP-DSM to the inverter module by tightening the two captive screws.

10. Reinstall the inverter module and reconnect the ribbon cable. Make front panel
connections (tamper, RTS, battery sense, etc.).

46 745-814-B0-001, Rev. A
 7.0 Hardware Installation, continued

7.3 XP-DSM Connections

7.3.1 Front Panel Diagram

XP-DSM Front Panel

CPE MAC Address

Reset Button

Status LEDs
Cable Modem Status LEDs RF Connection

Tamper Switch Connection

AlphaBus Communication Port

Battery String Connection (A/B)

Local Port Connection
RF MAC Address

Fig. 7-4, Front Panel

7.3.2 Connecting the RF Drop

CAUTION!
Install a grounded surge suppressor (Alpha P/N 162-028-10 or equivalent).

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).

STAT

ALM
XP-DSM
RDY
COM
LNK

RF
DS
REG

DC
TMPR

Battery
Breaker

Battery
O
nput

Temp
Probe RF Cable
to Headend
Grounded Surge Protector
(See Caution Above)

Fig. 7-5, Connecting the RF Drop

745-814-B0-001, Rev. A 47
 7.0 Hardware Installation, continued

7.3 XP-DSM Connections, continued

7.3.3 Front Panel Connections

XP-DSM Front Panel Connections

ECM to SCM Interface

(Alpha P/N 704-709-20)

“Master”
XM2 XM2 XM2
System Port

STAT
S S
Y Y ALM
S S
RDY
COM
C C LNK
O
M
System Port O
M

Communications RF
REG
Communications Port Port DS

TMPR Generator (ECM)

C
O
M

Communications
Port

Battery String
To Battery Sense Wire Harness
LOCAL
Connector

Connections
Connections with more
than one power supply

Fig. 7-6, System Interconnection Diagram

48 745-814-B0-001, Rev. A
 8.0 Battery Sense Wire Kit Connections
8.1 36V Single and Dual Strings

To Power Supply
Red Black

NEG NEG NEG

Fig. 8-1, 36V System, Single String
Alpha P/N: 874-842-21 (6')
Alpha P/N: 874-842-27 (9') 3A 2A 1A

POS POS POS

Vbatt 3A [C] 36V

Vbatt 1A [C] 12V

Vbatt 2A [C] 24V
A/B [C/D] NEG
Pin 1

Pin 4

Pin 2
Pin 3
5 1

6 2

7 3

8 4

Back of Plug

To Power Supply

Red Black

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

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

3A 2A 1A

POS POS POS

Vbatt 2A [C] 24V
Vbatt 3A [C] 36V

Vbatt 1A [C] 12V

A/B [C/D] NEG
Pin 1

Pin 3
Pin 4

Pin 2

5 1

6 2

7 3
Vbatt 2B [D] 24V

Vbatt 1B [D] 12V

Vbatt 3B [D] 36V

8 4
Pin 6

Pin 5
Pin 7

Back of Plug

NEG NEG NEG

3B 2B 1B

POS POS POS

745-814-B0-001, Rev. A 49
 8.0 Battery Sense Wire Kit Connections, continued

8.2 48V Single and Dual Strings

To Power Supply

Red Black

Fig. 8-3, 48V System, Single String

Alpha P/N: 875-841-21 (6') NEG NEG NEG NEG
Alpha P/N: 875-841-25 (9')

4A 3A 2A 1A

POS POS POS POS

Vbatt 3A [C] 36V

Vbatt 1A [C] 12V

Vbatt 2A [C] 24V
A/B [C/D] NEG

Vbatt 4A [C/D] 48V

Pin 1

Pin 4

Pin 2
Pin 3
Pin 8

5 1

6 2

7 3

8 4
To Power Supply
Back of Plug

Red Black

Fig.8-4, 48V System, Dual String NEG NEG NEG NEG

Alpha P/N: 874-841-20 (6')
Alpha P/N: 874-841-24 (9')
4A 3A 2A 1A

POS POS POS POS

Vbatt 1A [C] 12V
Vbatt 3A [C] 36V

Vbatt 2A [C] 24V

A/B [C/D] NEG
Pin 1

Pin 2
Pin 4

Pin 3

5 1

6 2

7 3
Vbatt 3B [D] 36V

Vbatt 2B [D] 24V

Vbatt 1B [D] 12V

Vbatt A/B [C/D] 48V

8 4
Pin 7

Pin 6

Pin 5
Pin 8

Back of Plug

NEG NEG NEG NEG

4B 3B 2B 1B

POS POS POS POS

50 745-814-B0-001, Rev. A
 9.0 Start-up and Verification
9.1 Initial Startup
1. Plug the power supply into the AC outlet and turn on the battery breaker.

2. The XP-DSM LEDs blink three times and the RDY light begins blinking on and off.

3. Verify no alarms are active.

4. Verify the DS and REG LEDs are on solid (this verifies successful network registration).

5. Verify LNK LED is blinking if in Single IP Mode and on solid if in Dual IP Mode.

NOTE:
A solid registration LED indicates registration with the CMTS. Use this indicator to confirm the communication
with the headend. It might take several minutes for communication to be established.

9.2 LEDs and System Status

The XP-DSM has six LEDs that indicate system status. During system startup, the
LEDs blink momentarily. The Status LEDs indicate alarms, status of the XP-DSM, and
communications and activity with the network. A description of each LED follows.

ALM – HMS Major and Minor Alarm

The ALM LED is the only red LED. It provides a visual alert for power supply discrete major
and minor alarms, as defined in the discrete property tables of the SCTE HMS MIB. Refer to
Section 6.3 for information on configuring the XP-DSM for active monitoring and alarming.
If an event triggers an HMS alarm, the ALM LED blinks according to the alarm type until the
alarm has been resolved. If there are multiple active alarms, including one or more major
alarms with one or more minor alarms, the major alarm will take precedent in terms of the
LED indication.

RDY – Micro-controller Status and Write to Non-volatile Memory

During normal operation, the RDY LED blinks steadily, indicating a heartbeat pulse from the
processor.

COM – Alpha Bus, or Local port Receive

The COM LED indicates any RS-232 and RS-485 traffic being received by the XP-DSM
through the Com port or Local port. When using the Local port, the light blinks for every
character typed, as the transistor-to-transistor logic (TTL) accepts each character. This LED
will also blink with one to three blinks approximately every 10 seconds, which indicates
communication exists between the XP-DSM card and other connected devices, such as a
generator or additional XM2.

LNK – Network Communication Status

For single IP applications the LNK LED blinks. For dual IP applications, the LNK LED is on
solid, and indicates network health.

745-814-B0-001, Rev. A 51
 9.0 Start-up and Verification, continued

9.2 LEDs and System Status, continued

DS – Downstream Communication
This LED indicates the state of the CM’s attempt to gain a downstream signal. The process
may take several seconds, depending on how long it takes the CM to locate carrier signal and
lock into a channel. The LED is on solid when the downstream channel is locked.

REG – CM Registration
Once a downstream channel is negotiated between the CM and CMTS, the modem attempts
to register with the DHCP server and obtain the configuration file. This LED flashes while the
process takes place. Once the registration is complete, the LED will remain on. This is the
best indication that the XP-DSM is connected to the headend.

LED Behavior Indication

OFF No alarms reported
ALM Blinking ON more than OFF Major Alarm present
Blinking OFF more than ON Minor Alarm present
Steady Blinking Normal Operation
Alarm Quick Burst Write to non-volitile memory
Ready RDY Steady ON Processor hung. Reset or
replace.
Communication OFF Processor not operating.
Link Replace card
Receiving Data via the Alpha
COM Blinking
Registration Bus or Com Port
LNK Not used with default application.
Downstream Blinking Attempting to register
REG
ON Registration verified
Model H OFF
Aquiring downstream signal
Model A Blinking
DS
Downstream communication
ON
established

Fig. 9-1, LED Indications

52 745-814-B0-001, Rev. A
 9.0 Start-up and Verification, continued

9.3 Verifying Successful Hardware Installation

>tex
To confirm successful hardware installation before
TEXT
leaving the installation site, verify successful network ----------------------------------------------
0 [ro] DHCP STATE : DISCOVER SENT
connectivity and correct hardware interconnection. 1 [ro] DHCP TIMER : 0
2 [ro] DHCP SERV : 0.0.0.0
3 [ro] DHCP SERV 54 : 0.0.0.0
To Verify Network Connectivity: 4 [ro] DOWN STAT :
5 [rw] DOWN NAME 1 :
6 [rw] DOWN NAME 2 :
The DS and REG LEDs on the front of the XP- 7 [rw] DOWN IP : 0.0.0.0
8 [rw] DOWN CFG :
DSM should be ON solid. This indicates successful 9 [rw] DOWN CFG IP
10 [rw] NTP SERV
:
:
0.0.0.0
0.0.0.0
registration with the headend. 11 [ro] NTP DHCP
12 [ro] NTP TIME UTC
:
:
0.0.0.0
01/01/70 00:00:00
13 [ro] ENET ADDR : 00.90.EA.A0.1E.5F
Using the Local Port, verify the following in the TEXT 14 [ro] IP ADDR IN USE
15 [ro] NETMASK IN USE
:
:
65.66.67.68
0.0.0.0
table (see Section 4.0 for Local Port instructions). 16 [ro] GATEWAY IN USE
17 [rw] IP ADDR STATIC
:
:
0.0.0.0
0.0.0.0
18 [rw] NETMASK STATIC : 0.0.0.0
19 [rw] GATEWAY STATIC : 0.0.0.0
• For single IP applications, verify the CM IP field 20 [rw] SNMP TRAP TARGET :
21 [rw] SNMP TRAP TARGET :
0.0.0.0
0.0.0.0
is populated with the cable modem’s IP address, 22 [rw] SNMP TRAP TARGET :
23 [rw] SNMP TRAP TARGET :
0.0.0.0
0.0.0.0
and the CM/RF ENET field is populated with the 24 [rw] SNMP ACCESS LIST :
25 [rw] SNMP ACCESS LIST :
0.0.0.0
0.0.0.0
RF MAC Address. 26 [rw] SNMP ACCESS LIST :
27 [rw] SNMP ACCESS LIST :
0.0.0.0
0.0.0.0
28 [ro] sysDescr : ATI P01V1.08.0
29 [rw] sysName :
• For dual IP applications, also verify the IP ADDR 30 [rw] sysContact
31 [rw] sysLocation
:
:
IN USE field is populated with the CPE IP 32 [rw] comLogicalID
33 [ro] CHECK CODE
:
: 146.51.132.199
address and the ENET ADDR field is populated 34 [rw] PING IP
35 [rw] ATICONFIG IP
:
:
0.0.0.0
0.0.0.0
with the CPE MAC Address. 36 [rw] ATICONFIG NAME :
37 [ro] TIME UP : 0 00:00:29
38 [ro] CM/RF ENET : 00.03.08.0B.9A.EA
To Verify Correct Hardware Interconnection: 39 [ro] CM IP
40 [ro] CM SUBNET
:
:
10.20.30.40
255.255.255.0
41 [ro] CM GATEWAY : 192.168.1.1
To test hardware interconnection using the Local 42 [ro] CM TOD
43 [ro] CM TFTP
:
:
192.43.244.18
192.168.1.51
44 [rw] SNMP GET : AlphaGet
Port, verify valid values for Output Voltage and 45 [rw] SNMP SET : AlphaSet
46 [rw] SNMP TRAP : public
Output Current in the ANALOGS table. 47 [rw] ALPHA SNMP SETS : CIBSET
---------------------------------------------

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 XP-DSM has been identified and is
reporting data correctly.
• The XP-DSM can also be pinged.

745-814-B0-001, Rev. A 53
 10.0 MIB Parameter Definitions and Settings
10.1 Alpha MIB Parameter Definitions and Settings

Alpha MIB Parameters

Parameter Local Port/ Description Access Value
CIB Variable Type
atiMgntSnmp
1.3.6.1.4.1.926.1.3.1.0
SNMP TRAP ADDRESSES
atiMgmtSnmpTrapTable
1.3.6.1.4.1.926.1.3.1.1
atiMgmtSnmpTrapAddress.1 [Text] SNMP TRAP SNMP Trap Address (1) Read/Write 0.0.0.0 (default)
1.3.6.1.4.1.926.1.3.1.1.1.2.1 TARGET IP address
atiMgmtSnmpTrapAddress.2 [Text] SNMP TRAP SNMP Trap Address (2) Read/Write 0.0.0.0
1.3.6.1.4.1.926.1.3.1.1.1.2.2 TARGET IP address
atiMgmtSnmpTrapAddress.3 [Text] SNMP TRAP SNMP Trap Address (3) Read/Write 0.0.0.0
1.3.6.1.4.1.926.1.3.1.1.1.2.3 TARGET IP address
atiMgmtSnmpTrapAddress.4 [Text] SNMP TRAP SNMP Trap Address (4) Read/Write 0.0.0.0
1.3.6.1.4.1.926.1.3.1.1.1.2.4 TARGET IP address
SECURE SNMP ACCESS ADDRESS
atiMgmtSnmpAccessTable
1.3.6.1.4.1.926.1.3.1.2
atiMgmtSnmpAccessAddress.1 [Text] SNMP ACCESS Secure IP address Read/Write 0.0.0.0 (default)
1.3.6.1.4.1.926.1.3.1.2.1.2.1 LIST IP address
atiMgmtSnmpAccessAddress.2 [Text] SNMP ACCESS Read/Write 0.0.0.0
1.3.6.1.4.1.926.1.3.1.2.1.2.2 LIST IP address
atiMgmtSnmpAccessAddress.3 [Text] SNMP ACCESS Read/Write 0.0.0.0
1.3.6.1.4.1.926.1.3.1.2.1.2.3 LIST IP address
atiMgmtSnmpAccessAddress.4 [Text] SNMP ACCESS Read/Write 0.0.0.0
1.3.6.1.4.1.926.1.3.1.2.1.2.4 LIST IP address

SNMP ACCESS ENABLE

atiMgntSnmpAccess
1.3.6.1.4.1.926.1.3.1.3.0
atiMgmtSnmpSnmpv1Access [Discretes] SNMPv1 SNMPv1 Access to Power Read/Write SNMP Local Port
1.3.6.1.4.1.926.1.3.1.3.1.0 Supply Data Integer
1 = Disable 1 = Enable
2 = Enable 0 = Disable
atiMgmtSnmpSnmpv2Access [Discretes] SNMPv2 SNMPv2 Access to Power Read/Write SNMP Local Port
1.3.6.1.4.1.926.1.3.1.3.2.0 Supply Data Integer
1 = Disable 1 = Enable
2 = Enable 0 = Disable

CPE SECURITY KEY (Dual IP)

atiMgmtSnmpAlphaSetAccess [Discretes] ALPHA Set to Access Key Read/Write Set to match
1.3.6.1.4.1.926.1.3.1.3.3.0 SNMP SETS CIBSET Octet String atiMgmtSnmpAlphaSetAccess
atiMgmtSnmpAlphaSetKey [Text] ALPHA SNMP Data Access Key (Dual Read/Write CIBSET (default)
1.3.6.1.4.1.926.1.3.1.3.4.0 SETS IP) Octet String
ALPHA SNMP SETS [Discretes] ALPHA OID of Dicrete Table Read/Write 0 = Disabled
1.3.6.1.4.1.926.1.2.1.1.1.5 SNMP SETS Value Integeter read/
write 1 = Enabled

COMMUNITY STRINGS
atiMgntSnmpCommunities
1.3.6.1.4.1.926.1.3.1.4.0
atiMgmtSnmpCommGet [Text] SNMP GET Default ‘Read’ Community Read/Write AlphaGet (default)
1.3.6.1.4.1.926.1.3.1.4.1.0 String Octet String
atiMgmtSnmpCommSet [Text] SNMP SET Default ‘Read/Write’ Read/Write AlphaSet (default)
1.3.6.1.4.1.926.1.3.1.4.2.0 Community String Octet String

54 745-814-B0-001, Rev. A
 10.0 MIB Parameter Definitions and Settings, continued

10.1 Alpha MIB Parameter Definitions and Settings, continued

Alpha MIB Parameters

Parameter Local Port/ Description Access Value
CIB Variable Type
atiMgntSys
1.3.6.1.4.1.926.1.3.2.0
SOFTWARE DOWNLOAD
atiMgmtSysDownload
1.3.6.1.4.1.926.1.3.2.1.0
atiMgmtSysDownloadTftpAddress [Text] DOWN IP TFTP Server Address Read/Write 0.0.0.0 (default)
1.3.6.1.4.1.926.1.3.2.1.1.0 IP address
atiMgmtSysDownloadCtrl [Discretes] GET NEW DSM Firmware Download Read/Write 0 = Idle (default)
1.3.6.1.4.1.926.1.3.2.1.2.0 IMAGE “Trigger” Integer
1 = Download File1 (From v1.08
and higher)
2 = Download File2 then File1
(From v1.05 only)
atiMgmtSysDownloadStatus [Text] DOWN STAT DSM Firmware download Read Only 1=Idle (default)
1.3.6.1.4.1.926.1.3.2.1.3.0 Status Integer
2=Ready
3=Request
4=Requested
5=Transferring
6=Testing
7=DataDone
8=Error
9=Closing
atiMgmtSysDownloadFile1 [Text] DOWN NAME 1 DSM Firmware Filename Read/Write “DSM firmware filename (v1.08
1.3.6.1.4.1.926.1.3.2.1.4.0 Octet String and higher)
“”Loadcode.s19* (v1.05)”
atiMgmtSysDownloadFile2 [Text] DOWN NAME 2 Reserved Read/Write DSM firmware filename* (v1.05
1.3.6.1.4.1.926.1.3.2.1.5.0 Octet String only)
atiMgmtSysDownloadProgress Download Progress in Read Only 0:0..100000
1.3.6.1.4.1.926.1.3.2.1.6.0 Bytes Integer
atiMgmtSysDownloadSysDescr DSM Firmware Read/Write e.g. “ATI P01V01.12.0 “
1.3.6.1.4.1.926.1.3.2.1.7.0 description used for Octet String
upgrades
atiMgmtSysDownloadSysObjectId DSM Hardware Identifier Read/Write 1.3.6.1.4.1.926.1.99.1.1.1.0
1.3.6.1.4.1.926.1.3.2.1.8.0 used for upgrades Object Identifier
atiMgmtSysDownloadConfigName [Text] DOWN CFG DSM Setup File Filename Read/Write atidoc01.cfg
1.3.6.1.4.1.926.1.3.2.1.9.0 Octet String
atiMgmtSysDownloadConfigAddress [Text] DOWN CFG IP DSM Setup File TFTP Read/Write 0.0.0.0 (default)
1.3.6.1.4.1.926.1.3.2.1.10.0 loaction IP address
atiMgmtSysDownloadCm Force DSM Download Read/Write 1=Auto (default)
1.3.6.1.4.1.926.1.3.2.1.11.0 from modem’s Integer
2=ForceCM
docsDevSwServerIp
(Dual IP)
atiMgmtSysDownloadCfgCheckProgress DSM Setup File Marker Read Only 3
1.3.6.1.4.1.926.1.3.2.1.12.0 Integer

745-814-B0-001, Rev. A 55
 10.0 MIB Parameter Definitions and Settings, continued

10.1 Alpha MIB Parameter Definitions and Settings, continued

Alpha MIB Parameters

Parameter Local Port/ Description Access Value
CIB Variable Type
atiMgmtSysDownloadReCfgTime [Counters] RECONFIG Hours between download Read/Write 24 (Default)
1.3.6.1.4.1.926.1.3.2.1.13.0 TIMER of setup file Integer
WEB SERVER ENABLE
atiMgmtSysAccess
1.3.6.1.4.1.926.1.3.2.2.0
atiMgmtSysHttpAccess [Discretes] HTTP Access to DSM via Web Read/Write SNMP Local Port
1.3.6.1.4.1.926.1.3.2.2.1.0 SERVER browser Integer
1=Disable 1= Enable
(Default)
2=Enable 0= Disable
(Default)
atiMgmtSysHttpTextAccess [Discretes] HTTP TEXT Access to DSM Text Table Read/Write SNMP Local Port
1.3.6.1.4.1.926.1.3.2.2.2.0 via Web Integer
1=Disable 1= Enable
(Default)
2=Enable 0= Disable
(Default)
SIMPLE NETWORK TIMER PROTOCOL
atiMgmtSysServers
1.3.6.1.4.1.926.1.3.2.3.0
atiMgmtSysServSntp [Text] NTP SERV IP address of SNMP Read/Write 0.0.0.0 (Default)
1.3.6.1.4.1.926.1.3.2.3.1.0 Server (Optional) IP address

alphaTechIncIDs
1.3.6.1.4.1.926.1.99.0
atiHMSIDs
1.3.6.1.4.1.926.1.99.1.0
atiHMS-ETH-DIGI-01 Read Only
1.3.6.1.4.1.926.1.99.1.1.0 Object Identifier
atiHMS-ETH-DIGI-01r1 DSM Version 1 Read Only
1.3.6.1.4.1.926.1.99.1.1.1 Object Identifier

56 745-814-B0-001, Rev. A
 10.0 MIB Parameter Definitions and Settings, continued

10.2 Modem Firmware Upgrade Parameter Definitions and Settings

Modem Firmware Upgrade (Not in Alpha MIB)

Parameter Description Access Value
Type
docsDevSoftware
1.3.6.1.2.1.69.1.3.0
docsDevSwServer IP address of modem Read/Write 0.0.0.0 (Default)
1.3.6.1.2.1.69.1.3.1.0 firmware server IP address
docDevSwFilename Filename of modem Read/Write “firmware Image.bin” (Example)
1.3.6.1.2.1.69.1.3.2.0 firmware image (Alpha Octet String
Provided)
docsDevSwAdminStatus Firmware upgrade Read/Write 1=Initiate Upgrade
1.3.6.1.2.1.69.1.3.3.0 trigger Integer
2=Upgrade on Next Reboot
3=Ignore Upgrade
docsDevSwOperStatus Monitor firmware Read Only 1=InProgress: Indicates a TFTP
1.3.6.1.2.1.69.1.3.4.0 upgrade download is under way
2=CompleteFromProvisioning: The
last upgrade was performed at
bootup due to a firmware mismatch
3=CompleteFromMgt: Last
upgrade was inititated by setting
docsDevSwAdminStatus to ‘1’
4=Failed: Last firmware upgrade
failed
5=Other

745-814-B0-001, Rev. A 57
 11.0 Frequently Asked Questions
How is power supply data accessed from the XP-DSM?
The XP-DSM uses Simple Network Management Protocol (SNMP) to provide power supply data and
access to the transponder settings through the network. Management Information Base (MIB) files
must be compiled into the SNMP software to provide a map of the data and settings. See Section
6.0. The Society of Cable Television Engineers (SCTE) created a standard for monitoring power
supply data. They developed MIB files that provide standard locations for power supply and generator
data. These MIB files are available at the SCTE web site http://www.scte.org/home.cfm. Alpha has
also created a MIB file ATI-TABLES-MGMT-MIB.mib for managing the XP-DSM and for accessing
power supply data and settings that are not covered by the SCTE standards. The Alpha MIB can be
accessed through the Alpha website, or by calling technical support.

With which monitoring software packages is the XP-DSM compatible?

The XP-DSM is designed around the SCTE standards and should work with any SNMP management
software that can monitor the SNMP MIB variables defined within the standard.

Can XP-DSM settings and power supply data be accessed from the front of the power supply?
There is a local port on the front of the XP-DSM that allows a user to access power supply and
transponder data and settings using a laptop or PC. A special Local Port Adapter (Alpha P/N 745-826-
21) must be used to interface between the computer and XP-DSM. Free emulator software such as
HyperTerminal or Terminal is used for this local connection. See Section 4.0.

What is the difference between Single IP and Dual IP Modes?

By default, the XP-DSM operates in Single IP Mode, which means that the power supply data is
only available through the modem’s IP address. This allows the XP-DSM to be managed within the
secure modem network. The XP-DSM can be configured to operate in Dual IP Mode, where a second
IP address is assigned on the CPE (public) network. This allows power supply data and XP-DSM
settings to be available from any place on the public network. See Section 2.2.

Why are there two MAC Addresses on the XP-DSM?

There are two MAC Addresses on the XP-DSM, the RF MAC and the CPE MAC. The RF MAC
Address is associated with the cable modem and is the only MAC Address required for operation
in Single IP Mode (default). The CPE MAC Address is used for operation in Dual IP Mode when a
second IP address is provided for access to data on the public network. See Sections 2.2 and 3.1.

Does the XP-DSM’s modem need to be specially provisioned?

The XP-DSM’s RF MAC Address is the network address of its cable modem. The RF MAC Address
must be provisioned as a standard cable modem and must allow a CPE connection. See Sections 2.3
and 3.1.

Where are the firmware versions displayed?

There are two components of the XP-DSM assembly that require firmware, the cable modem and the
DSM transponder.
Cable Modem: The cable modem firmware information is located via SNMP through sysDescr at OID:
1.3.6.1.2.1.1.1
DSM (HMS) Firmware: The firmware for the DSM code can be found through any of the following
locations:

58 745-814-B0-001, Rev. A
 11.0 Frequently Asked Questions, continued

Local Port: At the command prompt type TEXT. The firmware version will be displayed next to the
SysDescr variable and will disaply as ‘ATI P01V1.10.0’ indicating firmware version 1.10.0.
SNMP: SCTE-HMS CommonVendorInfo: OID: 1.3.6.1.4.1.5591.1.3.1.5. See Section 5.0.
What is the purpose of the DOCSIS Configuration File?
A DOCSIS Configuration File is required for all DOCSIS cable modems and provides settings for the
cable modem. Settings in the DOCSIS file for the XP-DSM are optional and include setting SNMP
security (community strings) for the modem and for upgrading the firmware for the modem.
In Single IP Mode, if the community strings are not set in the DOCSIS Configuration File, only the
power supply SNMP MIB varbinds (enterprise.5591 and enterprise.926) will require community
strings AlphaGet (Read) and AlphaSet (Read/Write) default. However if the cable modem community
strings are set in the DOCSIS Configuration File they will override the DSM defaults. See Section 3.2.

Is there a way to set options on multiple XP-DSMs without visiting each site?
The DSM Setup File allows automated distribution of communications, power supply, and firmware
upgrade options to every XP-DSM on the network. See Section 3.4.

Can the XP-DSM be set to generate SNMP traps?

The XP-DSM supports the SNMP alarms defined in the SCTE-HMS Property MIB. See Section 6.3.

What if traps are not being received by the SNMP manager?

• Disable personal firewalls on computer receiving traps.
• Disable firewall clients in network interface properties, e.g. Check Point SecuRemote.
• Ensure DSM trap table is populated – atiMgmtSnmpTrapTable OID: 1.3.6.1.4.1.926.1.3.1.1.
• Ensure SCTE-HMS propertyTable and discretePropertyTables are configured to sent traps on
desired power supply conditions.
• Ensure port 162 is not blocked or filtered.

How is the cause of a psMajor Alarm determined?

With most transponders a site visit is required to look at the LCD on the XM2. With the XP-DSM,
however, the cause of a psMajor alarm can be determined by looking at the ‘DISCRETES’ table either
through the XP-DSM Web page or through SNMP MIB atiCibDiscTable. The XM2 parameter that
caused the alarm will have a value of ‘ALARM’. See Section 6.3.

How is firmware upgraded on the XP-DSM?

The XP-DSM uses TFTP to upgrade the power supply monitoring (HMS) firmware and is independent
of the modem firmware. The DSM Setup File can be used to automate the upgrade, or an Alpha-
provided software application can be installed and managed from any Windows or Sun Solaris server
on the XP-DSM’s network. See Section 5.2.

745-814-B0-001, Rev. A 59
 11.0 Frequently Asked Questions, continued

What if SNMP data can be accessed from the cable modem but power supply data is
unavailable in Single IP Mode?
Remotely verify that power supply data can be viewed through a Web browser. If you can connect to
the Web page but cannot see power supply data, the problem is most likely one of the following:
• The DEVICE ADDRESS on the power supply is set to ‘0’. The DEVICE Address must be set
to a non-zero value. See Section 7.1.
• The 2x9 pin connector on the DSM card was damaged during installation. The card needs to
be repaired or replaced. See Section 7.2.
If power supply data can be viewed via the ‘Analog’ link on the Web page, the issue is SNMP network
access related. Attempt the following:
• Ensure the XP-DSM’s cable modem has been provisioned to allow a CPE device on the
network. See Section 2.3 and 3.1.
• Check the DOCSIS Configuration File for community string settings. See Section 3.2.
When polling for power supply data, make sure to start the SNMP walk or SNMP get from inside the
SCTE-HMS or ATI enterprise tree (enterprise.5591 or enterprise.926).

Why is the battery temperature showing 80°C when it is actually lower?

Most likely there is not a Remote Temperature Sensor (RTS) installed. Temperature is used as part
of the XM2 charging algorithm, so if there is no temperature probe installed then the temperature
reading is set high to prevent over-charging of the batteries.

60 745-814-B0-001, Rev. A
 12.0 Specifications
XP-DSM DOCSIS Status Monitor Specifications
Interface
Power Supplies Supported XM2, XM2VP, GMX
RF Connection F-connector, female, 75 ohm
LED Indicators Alarm, Ready, Comm, Link, DS, REG
XM2 Data and Power Interface 18-pin DIL header, proprietary
Tamper 2 pin header
Battery Input A/B 8 pin, female connector, string A and B, 36V or 48V voltage monitoring. Configurable to monitor up
to 6 x 6V batteries
Multi-Device Communications RJ-12 offset, RS-485 multidrop, communication for three XM2s and an AlphaGen
Local Port RJ-12, RS-232, 19.2,N,8,1 Requires serial port adaptor for laptop connection. Access to power
supply MIB data and network parameters
Electrical/Mechanical/Environmental
Operating Temperature -40ºC to +65ºC
Storage Temperature -40ºC to +85ºC
Humidity 10-90% non-condensing
Emissions EN50022 Class A1, FCC Part 15 Class A1, one Installed in XM2 power supply
Surge IEEE C62.41-1991, cat B3, 6KV
Warranty 2 years
Network Communications
Network Protocols IP, UDP, TCP, DHCP, TFTP
SNMP v1, v2c
Embedded Web Interface “Read access MIB variables, Read-Write access networking parameters”
MIBs “Power Supply (ANSI/SCTE 38-4), Generator (ANSI/SCTE 38-6), Property (ANSI/SCTE 38-1),
Alpha Proprietary Advanced UPS Diagnostics”
Power Supply Monitored Parameters
Major Alarm Logical (OR) of: test fail, battery fail, line isolation alarm, output overload, inverter over
temperature, N+1 active, fuse fail
Minor Alarm Logical (OR) of: temperature probe error, AC line loss, N+1 error
Input Line Voltage 90-270Vac 50/60Hz measured value
Output Voltage 60/90Vac measured value
Output Current 1 0-25A measured value
Output Current 2,3,4 0-25A measured value (if optional power supply ports installed)
Output Power Calculated, reported in AC Watts
UPS Status AC line, standby, test in-process, test alarm
Enclosure Door open/closed
Battery Voltage “6V or 12V batteries, up to 8 batteries, individual battery voltages measured +/- 100mv resolution,
+/- 50mv accuracy”
Battery Temperature measured, reported in degrees Celsius
Remote Test Control start/stop XM2 self test cycle
Generator Monitored Parameters
Status Off, Running, Alarm
Alarm Logical (OR) of: low oil pressure, engine over temperature, engine over speed, crank limit, over
voltage, low fuel, water intrusion, pad shear, gas hazard, test fail
Gas Hazard Indicates combustible fumes above acceptable levels (LEL)
Water Intrusion Generator compartment flooded
Pad Shear Generator has been dislocated
Enclosure Door Open or Closed
Ignition Battery Voltage Measured value for 12V generator battery. Reported to +/- 100mv resolution
Enclosure Temperature Measured temperature inside generator compartment
Low Fuel Indicates fuel level insufficient to sustain engine
Remote Test Control Start/Stop generator self test cycle
Modem Parameters
Standards “DOCSIS 2.0
EuroDOCSIS 2.0”
Tx Frequency Range “5 to 42 MHz DOCSIS, 5 to 65 MHz EuroDOCSIS”
Output Power +8 to +58 dBmV
Channel Bandwidth “6 MHz DOCSIS, 8 MHz EuroDOCSIS”
Receive Center Frequency Range “91 to 857 MHz DOCSIS, 108 to 862 MHz EuroDOCSIS”
Input Level -15 to +15 dBmV

745-814-B0-001, Rev. A 61
 13.0 Glossary
Acronym Definitions
ANSI: American National Standards Institute
CM: Cable Modem
CMTS: Cable Modem Termination System
CPE: Customer Premise Equipment
DHCP: Dynamic Host Configuration Protocol
DOCSIS: Data Over Cable Service Interface Specification
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
TFTP: Trivial File Transfer Protocol
TOD: Time of Day
UDP: User Datagram Protocol
VoIP: Voice over Internet Protocol

62 745-814-B0-001, Rev. A
Power
Alpha Technologies ®

Alpha Technologies
3767 Alpha Way
Bellingham, WA 98226
USA
Tel: +1 360 647 2360
Fax: +1 360 671 4936
Web: www.alpha.com

Alpha Technologies Ltd.

4084 McConnell Court
Burnaby, BC, V5A 3N7
CANADA
Tel: +1 604 430 1476
Fax: +1 604 430 8908

Alpha Technologies
Europe Ltd.
Twyford House
Thorley
Bishop's Stortford
Hertfordshire
CM22 7PA
UNITED KINGDOM
Tel: +44 0 1279 501110
Fax: +44 0 1279 659870

Alpha Technologies GmbH

Hansastrasse 8
D 91126 Schwabach
GERMANY
Tel: +49 9122 79889 0
Fax: +49 9122 79889 21

Alphatec, Ltd
P.O. Box 56468
Limassol, Cyprus
CYPRUS
Tel: +357 25 375675
Fax: +357 25 359595

AlphaTEK ooo
Khokhlovskiy Pereulok 16
Stroenie 1, Office 403
109028 Moscow
RUSSIA
Tel: +7 495 916 1854
Fax: +7 495 916 1349

Alphatec Baltics
S. Konarskio G. 48
2009 Vilnius
LITHUANIA
Tel: +370 5 213 8822
Fax: +370 5 213 7799

Alpha Technologies
9, Impasse Sans Souci
92140 Clamart France
FRANCE
Tel: +33 141 900 707
Fax: +33 141 909 312

Due to continuing product improvements, Alpha reserves the right to change specifications without notice.
Copyright © 2007 Alpha Technologies, Inc. All rights reserved. Alpha is a registered trademark of Alpha Technologies. 745-814-B0-001, Rev. A