AlphaNet DSM Series - Alpha Technologies Services Inc · Section 3.1). The DOCSIS Configuration File should be saved in the TFTP Root Directory of the Trivial File Transfer Protocol

Technical ManualModel XP-DSM

Effective: June 2007

Alpha Technologies

AlphaNet™ DSM SeriesDOCSIS® Status Monitor

PowerAlpha Technologies ®

AlphaNet DSM SeriesDOCSIS Status Monitor

Technical Manual

745-814-B0-001, Rev. A

Effective Date: June, 2007Copyright© 2007

Alpha Technologies, Inc.

Contacting Alpha Technologies: www.alpha.comor

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-33647 AM to 5 PM, Pacific Time or 24/7 emergency support

To report errors in this document, send email to:[email protected]


member of The GroupTM

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.

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

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:

NOTE:

NOTE:

3

mailto://[email protected]

4 745-814-B0-001, Rev. A

Table of Contents

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

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

2.0 System Overview ........................................................................................................... 92.1 System Diagram .................................................................................................. 92.2 Single IP Mode vs. Dual IP Mode Overview ...................................................... 102.3 Network Connectivity Overview ......................................................................... 112.4 System Configuration and Installation Overview ............................................... 112.5 XP-DSM Start-up and Reboot Routine .............................................................. 12

3.0 Network Configuration and Option Settings ................................................................. 143.1 Provisioning the DHCP Server with the MAC Addresses .................................. 143.2 The DOCSIS Configuration File ........................................................................ 15

3.2.1 Setting Modem Community Strings in the DOCSIS Configuration File .. 153.2.2 Example DOCSIS Configuration File ..................................................... 16

3.3 Setting Communication Options ........................................................................ 173.4 The DSM Setup File .......................................................................................... 18

3.4.1 Building the DSM Setup File .................................................................. 183.4.2 Example of an atidoc01.cfg DSM Setup File .......................................... 193.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 ..................................................................................................... 245.1 Upgrading XP-DSM Modem Firmware .............................................................. 24

5.1.1 Identifying the Modem and Obtaining Firmware Files ............................ 245.1.2 Modem Firmware Upgrade SNMP Parameters ...................................... 245.1.3 Upgrading Modem Firmware Manually by Setting SNMP Parameters .. 255.1.4 Upgrading Modem Firmware in the DOCSIS Configuration File ............ 25

5.2 Upgrading XP-DSM Transponder Firmware ...................................................... 265.2.1 Remotely Upgrading XP-DSM Firmware................................................ 275.2.2 Upgrading XP-DSM Firmware Using a DSM Setup File ........................ 27

6.0 Data Management ........................................................................................................ 296.1 The SCTE-HMS MIB ......................................................................................... 306.2 The Alpha MIB ................................................................................................... 32

5745-814-B0-001, Rev. A

6.3 SCTE-HMS MIB Alarms .................................................................................... 346.3.1 SCTE-HMS Configurable Alarms ........................................................... 346.3.2 Distributing Alarm Settings ..................................................................... 396.3.3 SNMP Traps ........................................................................................... 416.3.4 General Power Supply Alarms ............................................................... 43

7.0 Hardware Installation .................................................................................................... 447.1 Verifying Power Supply Device Address ........................................................... 447.2 Hardware Installation Procedure ....................................................................... 457.3 XP-DSM Connections ....................................................................................... 47

7.3.1 Front Panel Diagram ............................................................................. 477.3.2 Connecting the RF Drop ........................................................................ 477.3.3 Front Panel Connections ........................................................................ 48

8.0 Battery Sense Wire Kit Connections ............................................................................ 498.1 36V Single and Dual Strings ............................................................................. 498.2 48V Single and Dual Strings ............................................................................. 50

9.0 Start-up and Verification ............................................................................................... 519.1 Initial Startup ..................................................................................................... 519.2 LEDs and System Status .................................................................................. 519.3 Verifying Successful Hardware Installation ....................................................... 539.4 Verifying Communications via the Headend ...................................................... 53

10.0 MIB Parameter Definitions and Settings ..................................................................... 5410.1 Alpha MIB Parameter Definitions and Settings ................................................. 5410.2 Modem Firmware Upgrade Parameter Definitions and Settings ....................... 57

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

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

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

6 745-814-B0-001, Rev. A

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

TablesTable 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

7745-814-B0-001, Rev. A

Safety NotesReview 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.

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

ATTENTION:

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

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

CAUTION!

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

WARNING!

8 745-814-B0-001, Rev. A

1.0 IntroductionThe 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

Fig. 1-1, AlphaNet XP-DSM

Cable Modem

Transponder

9745-814-B0-001, Rev. A

2.0 System Overview2.1 System Diagram

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.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.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).The XP-DSM transmits data via its cable modem directly over the Coax or Hybrid fiber-coax network.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:

161 = SNMP 162 = SNMP Traps 69 = TFTP 80 = HTTPThe 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). 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.The Time of Day (TOD) Server provides the cable modem with the current date and time.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).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).

1

2

3

45

6

8

7

910

OUTPUT 2

OUTPUT 1ALRI

BatteryInput

TempProbe

BatteryBreaker

OUTPUT 1B

N+1 N+1

ALMRDYCOMLNK

RF REG DSTMPR

CTRL

COM

ETH

CD

ABLOCAL

2 XP-DSM1 Power Supply

3 Local Computer

4 Coax/HFC Network 5 CMTS 6 TCP/IP Network

11 Web Browser

10MIB Browser

7 DHCP Server 8 TFTP Server 9 TOD Server

11

10 745-814-B0-001, Rev. A

2.0 System Overview, continued

2.2 Single IP Mode vs. Dual IP Mode Overview

One CM IP address only accessible on the private (LAN) network with access to both CM and transponder data.

MIB Tables

TransponderCable ModemXP-DSM

CPE IP address, transponder data only; accessible on the public (CPE) network.

MIB Tables

Transponder (CPE)Cable Modem

XP-DSM

CM IP address, CM and transponder data; accessible on the private (LAN) network.

Fig. 2-1, Single IP Mode

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 ModeIn Single IP Mode all data from both the cable modem and power supply are accessed and managed through the modem’s IP address on the secure private modem network. The transponder is not accessible from the public (Customer Premises Equipment) network. Consequently, the Network Management System (NMS) that monitors the power supplies must have access to the same private modem network.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 ModeIn Dual IP Mode the transponder acts like a CPE device to the cable modem, and registers a second IP address on the public CPE network. This allows the power supply data to be accessed and managed from anywhere within the public (CPE) network.Dual IP Mode Considerations:

• The transponder is accessible on the public (CPE) network. This makes data management more versatile.

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

Fig. 2-2, Dual IP Mode

11745-814-B0-001, Rev. A

2.3 Network Connectivity OverviewThe 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 SystemConfigurationandInstallationOverviewNOTE: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.

12 745-814-B0-001, Rev. A

e

2

1AI

tteryIn t

ttery

1B

N+1 N+1


2.5 XP-DSM Start-up and Reboot Routine

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

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 THCP Server, which sets modem options (see Section 3.2).

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

Time

Cable Modem

DSM Transponder

DHCP Server Web Browser

MIB Browser

Network Management System

CMTS

Network Devices

TOD Server

TFTP Server

Local Laptop

1 2 3 4 5 6

6c

6b

6a

7

TCP

/IP N

etw

ork

HFC

Net

wor

k

1

2

3

4

5

13745-814-B0-001, Rev. A

Monitoring and Managing Transponder and Power Supply Parameters. 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.

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

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

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


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

6

6a

6b

6c

7

14 745-814-B0-001, Rev. A

3.0 NetworkConfigurationandOptionSettings

3.1 Provisioning the DHCP Server with the MAC AddressesIn 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.

Fig. 3-1, Location of MAC Addresses

CPE MAC Address

RF MAC AddressCPE MAC Address

RF MAC Address

15745-814-B0-001, Rev. A

3.0 NetworkConfiguration,continued

3.2 TheDOCSISConfigurationFileA 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 HitronTo build a DOCSIS Configuration File use a DOCSIS TLV editor program.See the example Configuration File on the next page.

• 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 SettingModemCommunityStringsintheDOCSISConfigurationFile

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

NOTE:

MIB Parameter Object ID Description ValuedocsDevNmAccessStatus.2 1.3.6.1.2.1.69.1.2.1.7 4docsDevNmAccessIp.2 1.3.6.1.2.1.69.1.2.1.2 The IP address (or subnet) of the

network management statione.g. 10.20.30.0

docsDevNmAccessIpMask.2 1.3.6.1.2.1.69.1.2.1.3 The IP subnet mask of the network management stations

e.g. 255.255.255.0

docsDevNmAccessCommunity.2 1.3.6.1.2.1.69.1.2.1.4 The community string matched to this IP/Mask entry

alphanumeric string

docsDevNmAccessControl.2 1.3.6.1.2.1.69.1.2.1.5 The level of access granted 1= none2= read only3= read/write

Table 3-1, Modem Community String Parameters

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

NOTE:

16 745-814-B0-001, Rev. A

3.2.2 ExampleDOCSISConfigurationFile


3.2 TheDOCSISConfigurationFile,continued

Fig. 3-2, Example DOCSIS Configuration File

Sets Read-Write Community string. Set the IP addresses and community strings to fit your system.

Sets Read-Only Community string. Set the IP addresses and community strings to fit your system.

Specifies location of DSM Setup File atidoc01.cfg

SNMP MIB Object (11) [Len=21]:docsDevNmAccessStatus.1/4SNMP MIB Object (11) [Len=21]:docsDevNmAccesslp.1/10.56.21.0SNMP MIB Object (11) [Len=21]:docsDevNmAccesslpMask.1/255.255.255.0SNMP 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/4SNMP MIB Object (11) [Len=21]:docsDevNmAccesslp.2/10.56.21.0SNMP MIB Object (11) [Len=21]:docsDevNmAccesslpMask.2/255.255.255.0SNMP MIB Object (11) [Len=25]:docsDevNmAccessCommunity.2/"RO STRING"SNMP MIB Object (11) [Len=21]:docsDevNmAccessControl.2/2

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

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

Manufacturer Code Verification Certificate (32) [Len=254]: 30 82 03 1A 30 82...Manufacturer Code Verification Certificate (32) [Len=254]: 04 0A 13 11 41 4D...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....

Example File

Sets firmware download parameters.

Sets Code Verification Certificate (CVC)

17745-814-B0-001, Rev. A


3.3 Setting Communication OptionsThe 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.

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.

NOTE:

See Section 10.0 for complete parameter definitions.

Table 3-2, Transponder Communications Parameters

NOTE:

SNMP Parameter Local Port Parameter Type Description ValueAtiMgmtSnmpCommGetOID: 1.3.6.1.4.1.926.1.3.1.4.1

[Text] SNMP GET Alphanumeric String

Read Community String AlphaGet (default)

AtiMgmtSnmpCommSetOID: 1.3.6.1.4.1.926.1.3.1.4.2

[Text] SNMP SET Alphanumeric String

Read/Write Community String AlphaSet (default)

atiCibDiscTable 1.3.6.1.4.1.926.1.2.1.1

[Discretes] BLOCK CM Integer Block access to power supply data through modem

0 = Disabled (Default)

1 = Enabled


[Discretes] BLOCK CPE Integer Access Mode (Single/Dual IP) 0 = Dual IP

1 = Single IP (Default)


[Discretes] TRAP ON NORMAL Integer Send SNMP trap when alarmed condition returns to normal state

0 = Disabled (default)

1 = Enabled


[Discretes] HTTP SERVER Integer Display CIB Tables on Web page

0 = Disabled

1 = Enabled (default)


[Discretes] HTTP TEXT Integer Display TEXT table on Web page

0 = Disabled (default)

1 = Enabled

atiCibTextTable 1.3.6.1.4.1.926.1.2.1.4

[Text] IP ADDR STATIC IP address Static IP Address Assignment 0.0.0.0 (Default)


[Text] IP NETMASK STATIC IP address Static IP NETMASK 0.0.0.0 (Default)


[Text] IP GATEWAY STATIC IP address Static IP Gateway 0.0.0.0 (Default)

atiMgmtSnmpTrapTable 1.3.6.1.4.1.926.1.3.1.1

[Text] SNMP TRAP TARGET IP address SNMP Destination Trap Address 0.0.0.0 (Default)

atiMgmtSnmpAccessTable 1.3.6.1.4.1.926.1.3.1.2

[Text] SNMP ACCESS LIST IP address “(Dual IP Only) Restricted DSM SNMP Access”

0.0.0.0 (Default)

atiCibCountTable 1.3.6.1.4.1.926.1.2.1.3

[Counters] RECONFIG TIMER Integer Download interval for DSM Setup File atidoc01.cfg (Hours)

24 (Default)

atiCibCountTable 1.3.6.1.4.1.926.1.2.1.3

[Counters] SNMP COM TIMEOUT

Integer Time DSM will wait before reset if SNMP traffic not detected (Hours)

24 (Default)

AtiMgmtSysHttpAccessOID: 1.3.6.1.4.1.926.1.3.2.2.1

[Discretes] HTTP SERVER Integer HTTP Web Server SNMP Local Port

1 = Disable 1 = Enable

2 = Enable 0 = Disable

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

18 745-814-B0-001, Rev. A


3.4 The DSM Setup FileThe 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).

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.

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.

http://www.alpha.com/us/92_254_305_912/Broadband-Power/Status-Monitoring/DSM-2c-EMBEDDED-DOCSIS-HMS.aspx

19745-814-B0-001, Rev. A


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 ValuesParameter Type Description Value

atiMgmtSysDownloadCfgCheckProgressOID: 1.3.6.1.4.1.926.1.3.2.1.12.0

Integer Required file marker entry 3

atiMgntSnmpTrapAddress1OID: 1.3.6.1.4.1.926.1.3.1.1.

IP address Optional SNMP trap destination address 10.80.0.2

atiMgntSnmpTrapAddress2OID: 1.3.6.1.4.1.926.1.3.1.1.

IP address Optional SNMP trap destination address 70.45.94.130

atiCibDiscValue.sys.1.6OID: 1.3.6.1.4.1.926.1.2.1.1.1.5.14.1.6

Integer Sets XP-DSM into Dual IP Mode 1 = single IP (default)

0 = dual IP

atiMgmtSnmpSnmpv1AccessOID: 1.3.6.1.4.1.926.1.3.1.3.1.0

Integer Required to allow remote SNMPv1 access to power supply data

1 = disable

2 = enable (default)

atiMgmtSnmpSnmpv2AccessOID: 1.3.6.1.4.1.926.1.3.1.3.2.0

Integer Required to allow remote SNMPv2 access to power supply data

1 = disable


atiMgmtSysHttpAccessOID:1.3.6.1.4.1.926.1.3.2.2.1.0

Integer Enables embedded HTTP Web server to allow XP-DSM data to be visible from Internet Web browser.

1 = disable


Firmware DownloadatiMgmtSysDownloadTftpAddressOID: 1.3.6.1.4.1.926.1.3.2.1.1.0

IP address Address of modem’s TFTP server 10.20.13.3

atiMgmtSysDownloadFile1OID: 1.3.6.1.4.1.926.1.3.2.1.4.0

Filename Firmware filename esm1100_.phy

atiMgmtSysDownloadCtrlOID: 1.3.6.1.4.1.926.1.3.2.1.2.0

Integer “Trigger” file initiates firmware upgrade 1


Table 3-3, Example DSM Setup File Parameters and Values

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

Example DSM Setup File

20 745-814-B0-001, Rev. A


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 ValueAtiMgmtSnmpCommGetOID: 1.3.6.1.4.1.926.1.3.1.4.1

Alphanumeric String

Read Community String

[desired value]

AtiMgmtSnmpCommSetOID: 1.3.6.1.4.1.926.1.3.1.4.2

Alphanumeric String

Read/Write Community String

[desired value]

Table 3-4, Transponder Community String Parameters

21745-814-B0-001, Rev. A


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 TableThe 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:

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.

SNMP Parameter Local Port Parameter Description Type ValueatiMgmtSnmpAccessTable 1.3.6.1.4.1.926.1.3.1.2

[Text] SNMP ACCESS LIST Restricted DSM SNMP Access”

IP address 0.0.0.0 (Default)

NOTE:

The XP-DSM transponder variables will still be accessible through the private modem management network using the community strings without requiring additional security.

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.

Method 2: Security Using the Data Access Key

SNMP Parameter Local Port Parameter Description Type ValueatiMgmtSnmpAlphaSetAccess1.3.6.1.4.1.926.1.3.1.3.3.0

[Discretes] ALPHA SNMP SETS Set to Access Key Read/WriteOctet String

Set to match the value of atiMgmtSnmpAlphaSetKey

atiMgmtSnmpAlphaSetKey1.3.6.1.4.1.926.1.3.1.3.4.0

[Text] ALPHA SNMP SETS Data Access Key Read/WriteOctet String

CIBSET (default)

ALPHA SNMP SETS1.3.6.1.4.1.926.1.2.1.1.1.5

[Discretes] ALPHA SNMP SETS OID of Dicrete Table Value

Read/WriteInteger

0 = Disabled

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.

22 745-814-B0-001, Rev. A

4.0 Using the Local PortThe 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).

NOTE:Entries in the TEXT Table are transponder parameters and do not have subsystems.Example: To Update Read/Write Community String to “ReadString” Enter Command: >tex 45 ReadString

Procedure:1. Launch the terminal emulation software.

2. Hit ENTER to display the menu of CIB tables.3. Enter >[first three letters of table] and ENTER

to display the contents of a table.

Subsystem DefinitionsBSS Battery SystemXM2 Power Supply SystemSYS Transponder SystemECM Generator System

SYS-1 06 SNMPv1 1 ENABLED YES

Subsystem

Parameter IndexParameter Value Enumerated Value

Modifiable?

Power Supply

Entry Explanation

SELECT FROM : ANALOGS CONFIG COUNTERS DISCRETES TEXT >disDISCRETESDEV-A IX NAME VALUE ENM/UNIT SET----------------------------------------------BSS-1 00 GENERAL STATUS 0 OK NO----------------------------------------------XM2-1 00 GENERAL STATUS 0 OK NOXM2-1 01 SELF TEST FAIL 0 OK NOXM2-1 02 LOW BATT VOLTS 0 OK NOXM2-1 03 HIGH BATT VOLTS 0 OK NOXM2-1 04 NO BATTERIES 0 OK NOXM2-1 05 BATT TEMP PROBE 0 OK NOXM2-1 06 LINE ISOLATION 0 OK NOXM2-1 07 OUTPUT FAILURE 0 OK NOXM2-1 08 OUTPUT OVERLOAD 0 OK NOXM2-1 09 OUTPUT 1 TRIPPED 0 OK NOXM2-1 10 OUTPUT 2 TRIPPED 0 OK NOXM2-1 11 CHARGER FAILURE 0 OK NOXM2-1 12 INPUT FAILURE 0 OK NOXM2-1 13 INV DISCONNECTED 0 OK NOXM2-1 14 INVERTER TEMP 0 OK NOXM2-1 15 TAP SWITCH 0 NO NOXM2-1 16 PIM OPTION 0 NO NOXM2-1 17 N+1 VALID 0 NO NOXM2-1 18 SELF TEST 0 OFF YESXM2-1 19 TEST INHIBIT 0 YESXM2-1 20 ACCEPT/FLOAT 0 FLOAT YESXM2-1 21 INVERTER ENABLE 1 ON NOXM2-1 22 CHARGER ENABLE 1 ON NOXM2-1 23 RESET OUT 1 1 YESXM2-1 24 RESET OUT 2 0 NO YESXM2-1 25 N+1 IN USE 0 NO NOXM2-1 26 SET DEFAULTS 0 NO YESXM2-1 27 FACTORY TEST 0 OFF NOXM2-1 28 TAP FUSE FAIL 0 OK NOXM2-1 29 CONFIG ERROR 0 OK NOXM2-1 30 N+1 FAULT 0 OK NOXM2-1 31 BB-CMM/CMT OPT 0 NO YES----------------------------------------------SYS-1 00 AUTO CONFIG 0 ENABLED YESSYS-1 01 TAMPER ALARM 0 OK NOSYS-1 02 TAMPER ALM WHEN 0 CLOSED YESSYS-1 03 MGMT MSG TARGET 0 CPE NOSYS-1 04 BLOCK CM 0 NO YESSYS-1 05 BLOCK CPE 0 NO YESSYS-1 06 SNMPv1 1 ENABLED YESSYS-1 07 SNMPv2 1 ENABLED YESSYS-1 08 ALPHA SNMP SETS 1 ENABLED YESSYS-1 09 TRAP ON NORMAL 0 DISABLED YESSYS-1 10 HTTP SERVER 1 ENABLED YESSYS-1 11 HTTP TEXT 0 DISABLED YESSYS-1 12 PING REQUEST 0 YESSYS-1 13 GET NEW IMAGE 0 YESSYS-1 14 COM BUS DAT SIZE 0 9 BIT YESSYS-1 15 DEVICE RESET 0 RUNNING YESSYS-1 16 DEBUG MESSAGES 0 ENABLED YESSYS-1 17 PI CURRENT MODE 0 ENABLED YES----------------------------------------------

Discrete Table

Baud 19200Data Bits 8Parity NoneStop Bits 1Flow Control None

Serial Communication SettingsOUTPUT 2

OUTPUT 1ALRI

BatteryInput

TempProbe

BatteryBreaker

OUTPUT 1B

N+1 N+1

ALMRDYCOMLNK

RF REG DSTMPR

CTRL

COM

ETH

CD

ABLOCAL

Power Supply

Result:

SYS-1 06 SNMPv1 0 DISABLED YES

Hit ENTER

>dis sys 1 6 0

Subsystem

Parameter Index

Value

Table

Example CommandTo disable SNMPv1, enter the command:

4. To set a parameter value, enter: >[table] [subsystem] [power supply] [Index] [Value] ENTER.

23745-814-B0-001, Rev. A

4.0 Using the Local Port, continued

Variables are added and moved between firmware versions; therefore, the index values may change from the examples. Obtain the index value from the current displayed table prior to updating any values.

>ana

ANALOGSDEV-A IX NAME VALUE ENM/UNIT SET----------------------------------------------BSS-1 00 BATT 1A 0.00 VDC NOBSS-1 01 BATT 2A 0.00 VDC NOBSS-1 02 BATT 3A 0.00 VDC NOBSS-1 03 BATT 4A 0.00 VDC NOBSS-1 04 BATT 1B OR 5A 0.00 VDC NOBSS-1 05 BATT 2B OR 6A 0.00 VDC NOBSS-1 06 BATT 3B OR 7A 0.00 VDC NOBSS-1 07 BATT 4B OR 8A 0.00 VDC NO----------------------------------------------XM2-1 00 INPUT VOLTAGE 118.80 Vac NOXM2-1 01 INPUT FREQ 60.00 Hz NOXM2-1 02 OUTPUT VOLTAGE 64.00 Vac NOXM2-1 03 OUTPUT 1 CURR 0.00 A NOXM2-1 04 OUTPUT 2 CURR 0.00 A NOXM2-1 05 PERCENT LOAD 0.00 % NOXM2-1 06 OUTPUT VA 0.00 VA NOXM2-1 07 OUTPUT WATTS 0.00 W NOXM2-1 08 BATT VOLTAGE 40.40 Vdc NOXM2-1 09 CHARGER CURR 1.20 A NOXM2-1 10 BATTERY TEMP 27.50 oC NOXM2-1 11 FREQ RANGE 3.00 Hz YESXM2-1 12 FLOAT V/C 2.25 YESXM2-1 13 ACCEPT V/C 2.35 YESXM2-1 14 TEMP COMP 3.00 mV YESXM2-1 15 PEAK CURR 1 10.00 A YESXM2-1 16 PEAK CURR 2 10.00 A YESXM2-1 17 CHGR CURR LIMIT 25.50 A NOXM2-1 18 EOD VOLTAGE V/C 1.75 YES----------------------------------------------SYS-1 00 INPUT CURRENT 2.30 A NO----------------------------------------------

Analogs Table

>cou

COUNTERSDEV-A IX NAME VALUE ENM/UNIT SET----------------------------------------------BSS-1 00 NUMBER OF BATTS 0 YESBSS-1 01 NUMBER OF STRNGS 0 YES----------------------------------------------XM2-1 00 TEST INTERVAL 30 DAY YESXM2-1 01 TEST COUNTDOWN 30 DAY YESXM2-1 02 TEST DURATION 10 MIN YESXM2-1 03 STANDBY TIME 163 MIN YESXM2-1 04 STANDBY EVENTS 164 YESXM2-1 05 RETRY DELAY 60 SEC YESXM2-1 06 RETRY LIMIT 20 YESXM2-1 07 OVER CURR TOL 3 SEC YESXM2-1 08 BATT CAPACITY 100 AH YESXM2-1 09 RESERVED 0 BMP NOXM2-1 10 DEVICE ADDRESS 1 YESXM2-1 11 TOTAL RUN TIME 496 DAY NO----------------------------------------------SYS-1 00 PING CYCLE TIME 10 MIN YESSYS-1 01 POLL CYCLE TIME 10 SEC YESSYS-1 02 POLL RETRIES 5 YESSYS-1 03 ENGINE BOOTS HI 0 YESSYS-1 04 ENGINE BOOTS LO 5 YESSYS-1 05 TRAP SEND COUNT 0 YESSYS-1 06 SNMP COM TIMEOUT 24 HR YESSYS-1 07 RECONFIG TIMER 24 HR YES----------------------------------------------

Counters Table

NOTE:

>tex

TEXT ---------------------------------------------- 0 [ro] DHCP STATE : DISCOVER SENT 1 [ro] DHCP TIMER : 0 2 [ro] DHCP SERV : 0.0.0.0 3 [ro] DHCP SERV 54 : 0.0.0.0 4 [ro] DOWN STAT : 5 [rw] DOWN NAME 1 : 6 [rw] DOWN NAME 2 : 7 [rw] DOWN IP : 0.0.0.0 8 [rw] DOWN CFG : 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 12 [ro] NTP TIME UTC : 01/01/70 00:00:00 13 [ro] ENET ADDR : 00.90.EA.A0.1E.5F 14 [ro] IP ADDR IN USE : 0.0.0.0 15 [ro] NETMASK IN USE : 0.0.0.0 16 [ro] GATEWAY IN USE : 0.0.0.0 17 [rw] IP ADDR STATIC : 0.0.0.0 18 [rw] NETMASK STATIC : 0.0.0.0 19 [rw] GATEWAY STATIC : 0.0.0.0 20 [rw] SNMP TRAP TARGET : 0.0.0.0 21 [rw] SNMP TRAP TARGET : 0.0.0.0 22 [rw] SNMP TRAP TARGET : 0.0.0.0 23 [rw] SNMP TRAP TARGET : 0.0.0.0 24 [rw] SNMP ACCESS LIST : 0.0.0.0 25 [rw] SNMP ACCESS LIST : 0.0.0.0 26 [rw] SNMP ACCESS LIST : 0.0.0.0 27 [rw] SNMP ACCESS LIST : 0.0.0.0 28 [ro] sysDescr : ATI P01V1.08.0 29 [rw] sysName : 30 [rw] sysContact : 31 [rw] sysLocation : 32 [rw] comLogicalID : 33 [ro] CHECK CODE : 146.51.132.199 34 [rw] PING IP : 0.0.0.0 35 [rw] ATICONFIG IP : 0.0.0.0 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 : AlphaSet 46 [rw] SNMP TRAP : public 47 [rw] ALPHA SNMP SETS : CIBSET---------------------------------------------

Text Table

Note: no subsystem

24 745-814-B0-001, Rev. A

5.0 Upgrading Firmware5.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.

Modem Firmware Upgrade SNMP ParametersParameter Type ValuedocsDevSoftwareOID: 1.3.6.1.2.1.69.1.3docsDevSwServerOID: 1.3.6.1.2.1.69.1.3.1.0

IP address Set to the IP address of the TFTP server from which the firmware will be downloaded.

docDevSwFilenameOID: 1.3.6.1.2.1.69.1.3.2.0.4.2.0

Octet String Set to the filename of the firmware file downloaded from the Alpha website. Example: [“firmwareImage.bin”]

docsDevSwAdminStatusOID: 1.3.6.1.2.1.69.1.3.3.0.4.3.0

Integer 1 = Initiate upgrade2 = Upgrade on next reboot3 = Ignore update

docsDevSwOperStatusOID: 1.3.6.1.2.1.69.1.3.4.0

Read Only, Integer

1 = A TFTP download is in progress.2 = Last upgrade was performed at reboot3 = Last upgrade was initiated by setting docsDevSwAdminStatus to “1”4 = Firmware upgrade failed5 = Other

docsDevSwCurrentVersOID: 1.3.6.1.2.1.69.1.3.5.0

Read Only, Octet String

The current version of firmware in-stalled in the modem

5.1.2 Modem Firmware Upgrade SNMP Parameters

Table 5-1, Modem Firmware Upgrade SNMP Parameters

http://www.faqs.org/rfcs/rfc2669.html


25745-814-B0-001, Rev. A

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.

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.0 Upgrading Firmware, continued

5.1 Upgrading XP-DSM Modem Firmware, continued

5.1.4 UpgradingModemFirmwareintheDOCSISConfigurationFile

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

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.

Parameter ValuedocsDevSwServer Address of TFTP serverdocDevSwFilename Firmware filenamedocsDevSwAdminStatus 2Manufaacturer CVC The CVC file for you modem version

Parameter ValuedocsDevSwServer Address of TFTP serverdocDevSwFilename Firmware filenamedocsDevSwAdminStatus 1


26 745-814-B0-001, Rev. A


5.2 Upgrading XP-DSM Transponder FirmwareThere 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 ParametersParameter Local Port

ParameterType Value

atiMgntSysDownloadOID: 1.3.6.1.4.1.926.1.3.2.1atiMgmtSysDownloadTftpAddressOID: 1.3.6.1.4.1.926.1.3.2.1.1

[Text] DOWN IP

IP address The IP address of the modem’s TFTP server from which the firmware will be downloaded.

atiMgmtSysDownloadCtrl OID: 1.3.6.1.4.1.926.1.3.2.1.2

[Discrete] GET NEW IMAGE

Integer 1 = Initiate Download of firmware file2 = Initiate Download of two firmware files (ver-sion 1.05.0)3 = Idle

atiMgmtSysDownloadStatusOID: 1.3.6.1.4.1.926.1.3.2.1.3

[Text] DOWN STAT

Read Only Integer

1 = Idle5 = Transferring6 = Testing8 = Error

atiMgmtSysDownloadFile11.3.6.1.4.1.926.1.3.2.1.4

[Text] DOWN NAME 1

Octet String Set to the filename of the firmware file downloaded from the Alpha Website.

atiMgmtSysDownloadProgressOID: 1.3.6.1.4.1.926.1.3.2.1.6

Integer Byte count of firmware download process.

atiMgmtSysDownloadSysDescrOID: 1.3.6.1.4.1.926.1.3.2.1.7

Octet String Firmware version. Alpha will provide this value with released firmware.

atiMgmtSysDownloadSysObjectIDOID: 1.3.6.1.4.1.926.1.3.2.1.8

OID 1.3.6.1.4.1.926.1.99.1.1.1 (OID embedded in transponder to ensure firmware compatibility.)

atiMgmtSysDownloadCfgCheckProgressOID: 1.3.6.1.4.1.926.1.3.2.1.12

Integer 3 (file maker, only used with DSM Setup File.)

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.



27745-814-B0-001, Rev. A


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:

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

Parameter Local Port Parameter ValueatiMgmtSysDownloadTftpAddress [Text] DOWN IP Address of TFTP serveratiMgmtSysDownloadFile1 [Text] DOWN NAME 1 Firmware filename, e.g. “esm1100_.phy”atiMgmtSysDownloadCtrl [Discretes] GET NEW

IMAGE1 (initiate download of one firmware file)

5.2.2 Upgrading XP-DSM Firmware Using a DSM Setup File

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.

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.


28 745-814-B0-001, Rev. A


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:

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.

Parameter Local Port Parameter ValueatiMgmtSysDownloadReCfgTime [Counters] RECONFIG TIMER 0 (disable automatic upgrade)atiMgmtSysDownloadTftpAddress [Text] DOWN IP Address of TFTP serveratiMgmtSysDownloadFile1 [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

29745-814-B0-001, Rev. A

6.0 Data Management

SCTE-HMS MIBs Alpha MIB

Power Supply Data

XP-DSM

Network Management System (NMS) or MIB Browser: SNMP

Web Browser: http

Local Computer: RS485

OUTPUT 2

OUTPUT 1ALRI

BatteryInput

TempProbe

BatteryBreaker

OUTPUT 1B

N+1 N+1

ALMRDYCOMLNK

RF REG DSTMPR

CTRL

COM

ETH

CD

ABLOCAL

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.

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.

30 745-814-B0-001, Rev. A

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

6.1 The SCTE-HMS MIBThe 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.

6.0 Data Management, continued

http://www.scte.org

31745-814-B0-001, Rev. A

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


6.1 The SCTE-HMS MIB, continued

Table 6-1, SCTE-HMS MIB Hierarchy

32 745-814-B0-001, Rev. A


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 TablesAll 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 ManagementAdvanced 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 IDsThe Alpha Technologies IDs branch is used by internal DSM processes to identify the model of the transponder for firmware upgrades and other functions.

http://www.mg-soft.com/


33745-814-B0-001, Rev. A

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)

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)

Con

tent

s

XM2 Major Alarms

Advanced Settings

DSM Settings

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)

Con

tent

s

Voltages

Currents

Frequency

Temperatures: power supply, batteries, generator

atiCibCountTable (1.3.6.1.4.1.926.1.2.1.3) (Counters Table)

Con

tent

s Power Supply Self-Test

Communications Settings

Configuration Settings

atiCibTextTable (1.3.6.1.4.1.926.1.2.1.4) (Text Table)

Con

tent

s

DSM Communications Settings

IP Addresses

DHCP Server

DSM Firmware Version

Set Static IP address

DSM Configuration File

atiManagement (1.3.6.1.4.1.926.1.3)atiMgntSnmp (1.3.6.1.4.1.926.1.3.1.0)

Con

tent

s

SNMP Trap Tables

Dual IP Security

SNMP Access Enable

Community Strings

atiMgntSys (1.3.6.1.4.1.926.1.3.2)

Con

tent

s Firmware Download

Web Server Enable

SNTP Server Location

alphaTechIncIDs (1.3.6.1.4.1.926.1.99)

Con

tent

s

Internal DSM processes to identify the transponder model for firmware upgrades and other functions.

Alpha Technologies IDs

Alpha CIB Tables

Alpha Management


6.2 The Alpha MIB, continued

Table 6-2, Alpha MIB Hierarchy

34 745-814-B0-001, Rev. A


6.3 SCTE-HMS MIB AlarmsThe 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-HMSConfigurableAlarms

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 DefinitionLOLO alarm threshold for extreme low conditionLO alarm threshold for low conditionHI alarm threshold for high conditionHIHI 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.

35745-814-B0-001, Rev. A


6.3 SCTE-HMS MIB Alarms, continued

6.3.1 SCTE-HMSConfigurableAlarms,continued

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.

Binary to Hex Conversions for Alarm SettingsUnused HiHi Hi Lo LoLo Hex Enabled Alarms

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 0 0 0 0 0 0 0 00 No Alarms0 0 0 0 0 0 0 1 01 LoLo0 0 0 0 0 0 1 0 02 Lo0 0 0 0 0 0 1 1 03 Lo, LoLo0 0 0 0 0 1 0 0 04 Hi0 0 0 0 0 1 0 1 05 Hi, LoLo0 0 0 0 0 1 1 0 06 Hi, Lo0 0 0 0 0 1 1 1 07 Hi, Lo, LoLo0 0 0 0 1 0 0 0 08 HiHI0 0 0 0 1 0 0 1 09 HiHi, LoLo0 0 0 0 1 0 1 0 0A HiHi, Lo0 0 0 0 1 0 1 1 0B HiHi, Lo, LoLo0 0 0 0 1 1 0 0 0C HiHi, Hi0 0 0 0 1 1 0 1 0D HiHi, Hi, LoLo0 0 0 0 1 1 1 0 0E HiHi, Hi, Lo0 0 0 0 1 1 1 1 0F HiHi, Hi, Lo, LoLo

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

psTemerature

36 745-814-B0-001, Rev. A




Table 6-4, Analog Alarms and Common Settings

Analog Alarms and Common Settings

Analog Alarms Description AlarmEnable LOLO LO HI HIHI Deadband

psTotalStringVoltage 36V Scaled representation of the full battery string in 1/100 Volts units

0x0F 3120 3140 4510 4530 .1V

48V 0x0F 4160 4185 6015 6040 .1V

psBatteryVoltage Battery Voltage of 12V battery, scaled 1/100 V

0x0F 970 1000 1530 1550 .1V

psInputVoltage 120V Scaled representation of the input line voltage in 1/100 Volts units

0x0F Varies by site. The XM2 will switch to standby at Nominal +15% -20%

220V 0x0F

psOutputVoltage 48V Scaled representation of the power supply output voltage in 1/100 Volts units.

0x0F 4300 4550 5050 5300 1V

60V 0x0F 5650 6000 6600 7000 1V

90V 0x0F 7830 8265 9135 9570 1V

psPowerOut Representation of power supply output power in 1W

0x00 Monitor Output Current Instead

psStringChargeCurrent Battery string charge current, scaled at 1/100 Amp

0x0C Disable Disable 1200 1250 0.2A

psStringFloat Battery string float charge current, scaled at 1/100 Amp


psStringDischargeCurrent Battery string discharge current, scaled at 1/100 Amp

0x00 Not Supported by XM2/GMX

psOutputCurrent 15A Scaled representation of power supply RMS current in 1/100 Amp units


22A 0x0C Disable Disable 2530 2750 0.2A

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

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

37745-814-B0-001, Rev. A

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.

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.

Values of 2 and 5 generate

minor alarms.




38 745-814-B0-001, Rev. A




DiscreteAlarmDefinitionsandCommonSettingsDiscrete Alarms Discrete Alarm

ValueDefinition Example

SettingspsInverterStatus 1 Inverter is off DisablepsInverterStatus 2 AC Input line loss EnableMinorpsInverterStatus 3 Inverter is in a local test cycle DisablepsInverterStatus 4 Remote inverter test has been

initiatedDisable

psInverterStatus 5 The last Inverter test failed. EnableMinorpsMajorAlarm 1 No alarm DisablepsMajorAlarm 2 Service has been dropped or a

service interruption is imminent. This is a general alarm; the cause of which can be determined by looking in the Discretes Table.

EnableMajor

psMinorAlarm 1 No alarm DisablepsMinorAlarm 2 A non-service effecting condition has

occurred and should be monitoredEnableMinor

psTamper 1 Indicates status of enclosure door tamper sensor: closed (door is open).

EnableMinor

psTamper 2 Indicates status of enclosure door tamper sensor: open (door is closed).

Disable

psInputVoltagePresence 1 Digital value indicating that line voltage is lost, based on measurement of input voltage.

EnableMinor

psInputVoltagePresence 2 Indicates that line voltage is present and within tolerance, based on measurement of input voltage.

Disable

transponderInterfaceBusIdent 1 Remote device will respond to commands from master transponder.

Disable

transponderInterfaceBusIdent 2 Local device is under local control and will not respond to commands from master transponder.

EnableMinor

transponderInterfaceBusIdent 3 Device is not responding. EnableMajor

Table 6-5, Discrete Alarm Definitions and Common Settings

39745-814-B0-001, Rev. A



6.3.2 Distributing Alarm SettingsAlarm 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: Createan.s19imagefileofthemasterXP-DSM’salarmsettings.

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.

40 745-814-B0-001, Rev. A



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.

STEP3: Distributethe.s19filetootherXP-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 ParametersParameter Local Port

ParameterType Value

atiMgntSysDownloadOID: 1.3.6.1.4.1.926.1.3.2.1atiMgmtSysDownloadTftpAddressOID: 1.3.6.1.4.1.926.1.3.2.1.1

[Text] DOWN IP

IP address The IP address of the modem’s TFTP server on which HMScfg.s19 is stored.

atiMgmtSysDownloadCtrl OID: 1.3.6.1.4.1.926.1.3.2.1.2

[Discrete] GET NEW IMAGE

Integer 1 = Initiate download of .s19 file.

atiMgmtSysDownloadFile11.3.6.1.4.1.926.1.3.2.1.4

[Text] DOWN NAME 1

Octet String Set to HMScfg.s19.

Parameter Local Port Parameter

Type Value

atiMgmtSysDownloadProgressOID: 1.3.6.1.4.1.926.1.3.2.1.6

Integer Byte count of file download process.

atiMgmtSysDownloadStatusOID: 1.3.6.1.4.1.926.1.3.2.1.3

[Text] DOWN STAT

Read Only Integer

1 = Idle5 = Transferring6 = Testing8 = Error

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

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

41745-814-B0-001, Rev. A



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

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 Trap Translated by MG-Soft

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) Specifictraptype:1 Timestamp: 2358751 Objectidentifier1: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

Objectidentifier2: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.” Objectidentifier3: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

Objectidentifier4: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 Objectidentifier5:1.3.6.1.4.1.5591.1.1.2.1.2(SNMPv2-SMI::enterprises.5591.1..1.2.1.2) Value: INTEGER: 7

Example Raw Trap

Fig. 6-1, Example SNMP Alarm Trap

Example Alarm TrapThe 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.

42 745-814-B0-001, Rev. A



6.3.2 SNMP Alarm Traps, continued

Trap on NormalThe 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 TrapIn 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 TrapA 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.

Varbind ExplanationBinding #1commonPhysAddressOID: 1.3.6.1.4.1.5591.1.3.2.7.0

MAC Address of the transponder

Binding #2commonLogicalID OID: 1.3.6.1.4.1.5591.1.3.1.1.0

Optional user-configurable parameter that is often used to provide a unique logical name, or even the physical address of where the transponder is installed.

Binding #3alarmLogInformationOID: 1.3.6.1.4.1.5591.1.2.3.1.2.1

This varbind was designed by the SCTE-HMS committee with the intention of being used by sophisticated trap interpreters. The information is “coded” within the octet strings: Octet 1-4: POSIX Time of alarm occurrence (Most 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 #4Alarmed Parameter OID/ValueOID: 1.3.6.1.4.1.5591.1.4.2.1.27.1

This field provides the varbind of the parameter that is alarming along with the value of that parameter. This is the same information encoded in varbind #3 Octets 7 through z. In the example above the value would be:OID: 1.3.6.1.4.1.5591.1.4.2.1.27.1.0 (psTamper)Value: 2 (Open)

Binding #5Alarm Location/TypeOID: 1.3.6.1.4.1.5591.1.1.2.1.2

This is the information from varbind #3 Octet 5 above. The alarm location will always be the SCTE-HMS currentAlarmAlarmState, and the type will be determined based on how the alarm was 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

43745-814-B0-001, Rev. A

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.

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 AlarmspsMinor

Problem DefinitionLine 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 DefinitionOutput 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



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

44 745-814-B0-001, Rev. A

7.0 Hardware InstallationBefore 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.

Verify Device Address

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.

WARNING!

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

CAUTION!

7.1 Verifying Power Supply Device AddressBefore 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.

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.

45745-814-B0-001, Rev. A

Disconnect

Captive Screws

7.0 Hardware Installation, continued

7.2 Hardware Installation Procedure

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.

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

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

46 745-814-B0-001, Rev. A


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.

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

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

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

Insert Long Side Into Inverter Module

Inverter Module

Fig. 7-2, The 18-pin Jumper

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

47745-814-B0-001, Rev. A


7.3 XP-DSM Connections

7.3.1 Front Panel Diagram

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

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

CAUTION!

RF Cable to Headend

Grounded Surge Protector(See Caution Above)

Batterynput

TempProbe

BatteryBreaker

STAT

ALMRDYCOMLNK

DSREG

RF

DCTMPR

O

O

XP-DSM

Fig. 7-5, Connecting the RF Drop

7.3.2 Connecting the RF Drop

Fig. 7-4, Front Panel

XP-DSM Front Panel

Reset Button

Status LEDsRF Connection Cable Modem Status LEDs

Tamper Switch ConnectionAlphaBus Communication Port

Battery String Connection (A/B)

Local Port ConnectionRF MAC Address

CPE MAC Address

48 745-814-B0-001, Rev. A

Fig. 7-6, System Interconnection Diagram

7.3.3 Front Panel Connections

Connections

Connections with more than one power supply


7.3 XP-DSM Connections, continued

To Battery Sense Wire HarnessCommunications Port

Communications Port

COM

SYS

COM

SYS

STAT

ALMRDYCOMLNK

DSREG

RF

TMPR

COM

LOCAL

XM2 XM2“Master”

XM2

Generator (ECM)

ECM to SCM Interface (Alpha P/N 704-709-20)

Battery String Connector

System Port

Communications Port

System Port

XP-DSM Front Panel Connections

49745-814-B0-001, Rev. A

8.0 Battery Sense Wire Kit Connections8.1 36V Single and Dual Strings

POS POS POS

Back of Plug

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

1

2

3

4

5

6

7

8

Vba

tt 3A

[C] 3

6VPi

n 4

3A

POS

NEG

2A

POS

NEG

1A

POS

NEG

A/B

[C/D

] NE

GPi

n 1

Vba

tt 2A

[C] 2

4VPi

n 3

Vba

tt 1A

[C] 1

2VPi

n 2

To Power Supply

Fig. 8-2, 36V System, Dual StringAlpha P/N: 874-842-20 (6')Alpha P/N: 874-842-28 (9')

3B

NEG

2B

NEG

1B

NEG

1

2

3

4

5

6

7

8

Back of Plug

3A

POS

NEG

2A

POS

NEG

1A

POS

NEG

A/B

[C/D

] NE

GPi

n 1

Vba

tt 3A

[C] 3

6VPi

n 4

Vba

tt 2A

[C] 2

4VPi

n 3

Vba

tt 1A

[C] 1

2VPi

n 2

Vba

tt 3B

[D] 3

6VPi

n 7

Vba

tt 2B

[D] 2

4VPi

n 6

Vba

tt 1B

[D] 1

2VPi

n 5

To Power Supply

BlackRed

Red Black

50 745-814-B0-001, Rev. A

8.0 Battery Sense Wire Kit Connections, continued

8.2 48V Single and Dual Strings

Fig. 8-3, 48V System, Single StringAlpha P/N: 875-841-21 (6')Alpha P/N: 875-841-25 (9')

3A

POS

NEG

2A

POS

NEG

1A

POS

NEG

4A

POS

NEG

A/B

[C/D

] NE

GPi

n 1

Vba

tt 3A

[C] 3

6VPi

n 4

Vba

tt 2A

[C] 2

4VPi

n 3

Vba

tt 1A

[C] 1

2VPi

n 2

Vba

tt 4A

[C/D

] 48V

Pin

8

To Power Supply

Fig.8-4, 48V System, Dual StringAlpha P/N: 874-841-20 (6')Alpha P/N: 874-841-24 (9')

1

2

3

4

5

6

7

8

Back of Plug

1

2

3

4

5

6

7

8

Back of Plug

To Power Supply

4A

POS

NEG

3A

POS

NEG

2A

POS

NEG

4B

POS

NEG

3B

POS

NEG

2B

POS

NEG

1A

POS

NEG

1B

POS

NEG

Vba

tt 1A

[C] 1

2VPi

n 2

Vba

tt 2A

[C] 2

4VPi

n 3

Vba

tt 3A

[C] 3

6VPi

n 4

A/B

[C/D

] NE

GPi

n 1

Vba

tt A

/B [C

/D] 4

8VPi

n 8

Vba

tt 3B

[D] 3

6V

Pin

7

Vba

tt 2B

[D] 2

4VPi

n 6

Vba

tt 1B

[D] 1

2VPi

n 5

Red

Black

Black

Red

51745-814-B0-001, Rev. A

9.0 Start-upandVerification9.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.

9.2 LEDs and System StatusThe 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 AlarmThe 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 MemoryDuring normal operation, the RDY LED blinks steadily, indicating a heartbeat pulse from the processor.

COM – Alpha Bus, or Local port ReceiveThe 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 StatusFor single IP applications the LNK LED blinks. For dual IP applications, the LNK LED is on solid, and indicates network health.

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.

52 745-814-B0-001, Rev. A

9.0 Start-upandVerification,continued

9.2 LEDs and System Status, continued

ReadyAlarm

CommunicationLink

Downstream

Registration

LED Behavior Indication

ALMOFF No alarms reported Blinking ON more than OFF Major Alarm presentBlinking OFF more than ON Minor Alarm present

RDY

Steady Blinking Normal OperationQuick Burst Write to non-volitile memorySteady ON Processor hung. Reset or

replace.OFF Processor not operating.

Replace card

COM Blinking Receiving Data via the Alpha Bus or Com Port

LNK Not used with default application.

REGBlinking Attempting to register ON Registration verified

DS

Model H OFFAquiring downstream signal

Model A Blinking

ON Downstream communication established

Fig. 9-1, LED Indications

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

53745-814-B0-001, Rev. A

9.0 Start-upandVerification,continued

9.3 Verifying Successful Hardware InstallationTo confirm successful hardware installation before leaving the installation site, verify successful network connectivity and correct hardware interconnection.To Verify Network Connectivity:The DS and REG LEDs on the front of the XP-DSM should be ON solid. This indicates successful registration with the headend.Using the Local Port, verify the following in the TEXT table (see Section 4.0 for Local Port instructions).

• For single IP applications, verify the CM IP field is populated with the cable modem’s IP address, and the CM/RF ENET field is populated with the RF MAC Address.

• For dual IP applications, also verify the IP ADDR IN USE field is populated with the CPE IP address and the ENET ADDR field is populated with the CPE MAC Address.

To Verify Correct Hardware Interconnection:To test hardware interconnection using the Local Port, verify valid values for Output Voltage and Output Current in the ANALOGS table.

9.4 Verifying Communications via the HeadendUsing 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.

>tex

TEXT ---------------------------------------------- 0 [ro] DHCP STATE : DISCOVER SENT 1 [ro] DHCP TIMER : 0 2 [ro] DHCP SERV : 0.0.0.0 3 [ro] DHCP SERV 54 : 0.0.0.0 4 [ro] DOWN STAT : 5 [rw] DOWN NAME 1 : 6 [rw] DOWN NAME 2 : 7 [rw] DOWN IP : 0.0.0.0 8 [rw] DOWN CFG : 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 12 [ro] NTP TIME UTC : 01/01/70 00:00:00 13 [ro] ENET ADDR : 00.90.EA.A0.1E.5F 14 [ro] IP ADDR IN USE : 65.66.67.68 15 [ro] NETMASK IN USE : 0.0.0.0 16 [ro] GATEWAY IN USE : 0.0.0.0 17 [rw] IP ADDR STATIC : 0.0.0.0 18 [rw] NETMASK STATIC : 0.0.0.0 19 [rw] GATEWAY STATIC : 0.0.0.0 20 [rw] SNMP TRAP TARGET : 0.0.0.0 21 [rw] SNMP TRAP TARGET : 0.0.0.0 22 [rw] SNMP TRAP TARGET : 0.0.0.0 23 [rw] SNMP TRAP TARGET : 0.0.0.0 24 [rw] SNMP ACCESS LIST : 0.0.0.0 25 [rw] SNMP ACCESS LIST : 0.0.0.0 26 [rw] SNMP ACCESS LIST : 0.0.0.0 27 [rw] SNMP ACCESS LIST : 0.0.0.0 28 [ro] sysDescr : ATI P01V1.08.0 29 [rw] sysName : 30 [rw] sysContact : 31 [rw] sysLocation : 32 [rw] comLogicalID : 33 [ro] CHECK CODE : 146.51.132.199 34 [rw] PING IP : 0.0.0.0 35 [rw] ATICONFIG IP : 0.0.0.0 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 : 10.20.30.40 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 : AlphaSet 46 [rw] SNMP TRAP : public 47 [rw] ALPHA SNMP SETS : CIBSET---------------------------------------------

54 745-814-B0-001, Rev. A

10.0MIBParameterDefinitionsandSettings10.1 AlphaMIBParameterDefinitionsandSettings

Alpha MIB ParametersParameter Local Port/

CIB VariableDescription Access

TypeValue

atiMgntSnmp 1.3.6.1.4.1.926.1.3.1.0SNMP TRAP ADDRESSESatiMgmtSnmpTrapTable1.3.6.1.4.1.926.1.3.1.1atiMgmtSnmpTrapAddress.11.3.6.1.4.1.926.1.3.1.1.1.2.1

[Text] SNMP TRAP TARGET

SNMP Trap Address (1) Read/WriteIP address

0.0.0.0 (default)

atiMgmtSnmpTrapAddress.21.3.6.1.4.1.926.1.3.1.1.1.2.2



0.0.0.0




0.0.0.0




0.0.0.0

SECURE SNMP ACCESS ADDRESSatiMgmtSnmpAccessTable1.3.6.1.4.1.926.1.3.1.2atiMgmtSnmpAccessAddress.11.3.6.1.4.1.926.1.3.1.2.1.2.1

[Text] SNMP ACCESS LIST

Secure IP address Read/WriteIP address

0.0.0.0 (default)

atiMgmtSnmpAccessAddress.21.3.6.1.4.1.926.1.3.1.2.1.2.2


Read/WriteIP address

0.0.0.0




0.0.0.0




0.0.0.0

SNMP ACCESS ENABLEatiMgntSnmpAccess1.3.6.1.4.1.926.1.3.1.3.0atiMgmtSnmpSnmpv1Access1.3.6.1.4.1.926.1.3.1.3.1.0

[Discretes] SNMPv1 SNMPv1 Access to Power Supply Data

Read/WriteInteger

SNMP Local Port



atiMgmtSnmpSnmpv2Access1.3.6.1.4.1.926.1.3.1.3.2.0

[Discretes] SNMPv2 SNMPv2 Access to Power Supply Data

Read/WriteInteger

SNMP Local Port



CPE SECURITY KEY (Dual IP)atiMgmtSnmpAlphaSetAccess1.3.6.1.4.1.926.1.3.1.3.3.0

[Discretes] ALPHA SNMP SETS

Set to Access Key CIBSET

Read/WriteOctet String

Set to match atiMgmtSnmpAlphaSetAccess

atiMgmtSnmpAlphaSetKey1.3.6.1.4.1.926.1.3.1.3.4.0

[Text] ALPHA SNMP SETS

Data Access Key (Dual IP)


CIBSET (default)

ALPHA SNMP SETS1.3.6.1.4.1.926.1.2.1.1.1.5

[Discretes] ALPHA SNMP SETS

OID of Dicrete Table Value

Read/WriteIntegeter read/write

0 = Disabled

1 = Enabled

COMMUNITY STRINGSatiMgntSnmpCommunities1.3.6.1.4.1.926.1.3.1.4.0atiMgmtSnmpCommGet1.3.6.1.4.1.926.1.3.1.4.1.0

[Text] SNMP GET Default ‘Read’ Community String


AlphaGet (default)

atiMgmtSnmpCommSet1.3.6.1.4.1.926.1.3.1.4.2.0

[Text] SNMP SET Default ‘Read/Write’ Community String


AlphaSet (default)

55745-814-B0-001, Rev. A



TypeValue

atiMgntSys1.3.6.1.4.1.926.1.3.2.0SOFTWARE DOWNLOADatiMgmtSysDownload1.3.6.1.4.1.926.1.3.2.1.0atiMgmtSysDownloadTftpAddress1.3.6.1.4.1.926.1.3.2.1.1.0

[Text] DOWN IP TFTP Server Address Read/WriteIP address

0.0.0.0 (default)

atiMgmtSysDownloadCtrl1.3.6.1.4.1.926.1.3.2.1.2.0

[Discretes] GET NEW IMAGE

DSM Firmware Download “Trigger”

Read/WriteInteger

0 = Idle (default)

1 = Download File1 (From v1.08 and higher)

2 = Download File2 then File1 (From v1.05 only)

atiMgmtSysDownloadStatus1.3.6.1.4.1.926.1.3.2.1.3.0

[Text] DOWN STAT DSM Firmware download Status

Read OnlyInteger

1=Idle (default)

2=Ready

3=Request

4=Requested

5=Transferring

6=Testing

7=DataDone

8=Error

9=Closing

atiMgmtSysDownloadFile11.3.6.1.4.1.926.1.3.2.1.4.0

[Text] DOWN NAME 1 DSM Firmware Filename Read/WriteOctet String

“DSM firmware filename (v1.08 and higher) “”Loadcode.s19* (v1.05)”

atiMgmtSysDownloadFile21.3.6.1.4.1.926.1.3.2.1.5.0

[Text] DOWN NAME 2 Reserved Read/WriteOctet String

DSM firmware filename* (v1.05 only)

atiMgmtSysDownloadProgress1.3.6.1.4.1.926.1.3.2.1.6.0

Download Progress in Bytes

Read OnlyInteger

0:0..100000

atiMgmtSysDownloadSysDescr1.3.6.1.4.1.926.1.3.2.1.7.0

DSM Firmware description used for upgrades


e.g. “ATI P01V01.12.0 “

atiMgmtSysDownloadSysObjectId1.3.6.1.4.1.926.1.3.2.1.8.0

DSM Hardware Identifier used for upgrades

Read/WriteObject Identifier

1.3.6.1.4.1.926.1.99.1.1.1.0

atiMgmtSysDownloadConfigName1.3.6.1.4.1.926.1.3.2.1.9.0

[Text] DOWN CFG DSM Setup File Filename Read/WriteOctet String

atidoc01.cfg

atiMgmtSysDownloadConfigAddress1.3.6.1.4.1.926.1.3.2.1.10.0

[Text] DOWN CFG IP DSM Setup File TFTP loaction


0.0.0.0 (default)

atiMgmtSysDownloadCm1.3.6.1.4.1.926.1.3.2.1.11.0

Force DSM Download from modem’s docsDevSwServerIp (Dual IP)

Read/WriteInteger

1=Auto (default)

2=ForceCM

atiMgmtSysDownloadCfgCheckProgress1.3.6.1.4.1.926.1.3.2.1.12.0

DSM Setup File Marker Read OnlyInteger

3

10.0 MIBParameterDefinitionsandSettings,continued

10.1 AlphaMIBParameterDefinitionsandSettings,continued

56 745-814-B0-001, Rev. A



TypeValue

atiMgmtSysDownloadReCfgTime1.3.6.1.4.1.926.1.3.2.1.13.0

[Counters] RECONFIG TIMER

Hours between download of setup file

Read/WriteInteger

24 (Default)

WEB SERVER ENABLEatiMgmtSysAccess1.3.6.1.4.1.926.1.3.2.2.0atiMgmtSysHttpAccess1.3.6.1.4.1.926.1.3.2.2.1.0

[Discretes] HTTP SERVER

Access to DSM via Web browser

Read/WriteInteger

SNMP Local Port

1=Disable 1= Enable (Default)

2=Enable (Default)

0= Disable

atiMgmtSysHttpTextAccess1.3.6.1.4.1.926.1.3.2.2.2.0

[Discretes] HTTP TEXT Access to DSM Text Table via Web

Read/WriteInteger

SNMP Local Port

1=Disable (Default)

1= Enable

2=Enable 0= Disable (Default)

SIMPLE NETWORK TIMER PROTOCOLatiMgmtSysServers1.3.6.1.4.1.926.1.3.2.3.0

atiMgmtSysServSntp1.3.6.1.4.1.926.1.3.2.3.1.0

[Text] NTP SERV IP address of SNMP Server (Optional)


0.0.0.0 (Default)

alphaTechIncIDs1.3.6.1.4.1.926.1.99.0atiHMSIDs1.3.6.1.4.1.926.1.99.1.0

atiHMS-ETH-DIGI-011.3.6.1.4.1.926.1.99.1.1.0

Read OnlyObject Identifier

atiHMS-ETH-DIGI-01r11.3.6.1.4.1.926.1.99.1.1.1

DSM Version 1 Read OnlyObject Identifier


10.1 AlphaMIBParameterDefinitionsandSettings,continued

57745-814-B0-001, Rev. A

Modem Firmware Upgrade (Not in Alpha MIB)Parameter Description Access

TypeValue

docsDevSoftware1.3.6.1.2.1.69.1.3.0docsDevSwServer1.3.6.1.2.1.69.1.3.1.0

IP address of modem firmware server


0.0.0.0 (Default)

docDevSwFilename1.3.6.1.2.1.69.1.3.2.0

Filename of modem firmware image (Alpha Provided)


“firmware Image.bin” (Example)

docsDevSwAdminStatus1.3.6.1.2.1.69.1.3.3.0

Firmware upgrade trigger

Read/WriteInteger

1=Initiate Upgrade

2=Upgrade on Next Reboot

3=Ignore Upgrade

docsDevSwOperStatus1.3.6.1.2.1.69.1.3.4.0

Monitor firmware upgrade

Read Only 1=InProgress: Indicates a TFTP 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


10.2 ModemFirmwareUpgradeParameterDefinitionsandSettings

58 745-814-B0-001, Rev. A

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.

Wherearethefirmwareversionsdisplayed?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.1DSM (HMS) Firmware: The firmware for the DSM code can be found through any of the following locations:

59745-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 ConfigurationFile?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.

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

60 745-814-B0-001, Rev. A

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.

61745-814-B0-001, Rev. A

12.0SpecificationsXP-DSMDOCSISStatusMonitorSpecifications

InterfacePower Supplies Supported XM2, XM2VP, GMXRF Connection F-connector, female, 75 ohm LED Indicators Alarm, Ready, Comm, Link, DS, REGXM2 Data and Power Interface 18-pin DIL header, proprietaryTamper 2 pin headerBattery Input A/B 8 pin, female connector, string A and B, 36V or 48V voltage monitoring. Configurable to monitor up

to 6 x 6V batteriesMulti-Device Communications RJ-12 offset, RS-485 multidrop, communication for three XM2s and an AlphaGenLocal 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 parametersElectrical/Mechanical/EnvironmentalOperating Temperature -40ºC to +65ºCStorage Temperature -40ºC to +85ºCHumidity 10-90% non-condensingEmissions EN50022 Class A1, FCC Part 15 Class A1, one Installed in XM2 power supplySurge IEEE C62.41-1991, cat B3, 6KVWarranty 2 yearsNetwork CommunicationsNetwork Protocols IP, UDP, TCP, DHCP, TFTPSNMP v1, v2cEmbedded 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 ParametersMajor Alarm Logical (OR) of: test fail, battery fail, line isolation alarm, output overload, inverter over

temperature, N+1 active, fuse failMinor Alarm Logical (OR) of: temperature probe error, AC line loss, N+1 errorInput Line Voltage 90-270Vac 50/60Hz measured valueOutput Voltage 60/90Vac measured valueOutput Current 1 0-25A measured valueOutput Current 2,3,4 0-25A measured value (if optional power supply ports installed)Output Power Calculated, reported in AC WattsUPS Status AC line, standby, test in-process, test alarmEnclosure Door open/closedBattery Voltage “6V or 12V batteries, up to 8 batteries, individual battery voltages measured +/- 100mv resolution,

+/- 50mv accuracy”Battery Temperature measured, reported in degrees CelsiusRemote Test Control start/stop XM2 self test cycleGenerator Monitored Parameters

Status Off, Running, AlarmAlarm 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 failGas Hazard Indicates combustible fumes above acceptable levels (LEL)Water Intrusion Generator compartment floodedPad Shear Generator has been dislocatedEnclosure Door Open or ClosedIgnition Battery Voltage Measured value for 12V generator battery. Reported to +/- 100mv resolutionEnclosure Temperature Measured temperature inside generator compartmentLow Fuel Indicates fuel level insufficient to sustain engineRemote Test Control Start/Stop generator self test cycleModem 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 dBmVChannel 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

62 745-814-B0-001, Rev. A

AcronymDefinitionsANSI: American National Standards InstituteCM: Cable ModemCMTS: Cable Modem Termination SystemCPE: Customer Premise EquipmentDHCP: Dynamic Host Configuration Protocol DOCSIS: Data Over Cable Service Interface SpecificationEMS: Element Management SystemHMS: Hybrid Management SublayerIT: Information TechnologyMAC: Media Access ControlMIB: Management Information BaseNMS: Network Management SystemQoS: Quality of ServiceRTS: Remote Temperature SensorSCTE: Society of Cable Telecommunications EngineersSI: Serial InterfaceSNMP: Simple Network Management ProtocolTFTP: Trivial File Transfer Protocol TOD: Time of DayUDP: User Datagram ProtocolVoIP: Voice over Internet Protocol

13.0 Glossary

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


Alpha Technologies3767 Alpha WayBellingham, WA 98226USATel: +1 360 647 2360Fax: +1 360 671 4936Web: www.alpha.com

Alpha Technologies Ltd.4084 McConnell CourtBurnaby, BC, V5A 3N7CANADATel: +1 604 430 1476Fax: +1 604 430 8908

Alpha TechnologiesEurope Ltd.Twyford HouseThorleyBishop's StortfordHertfordshire CM22 7PAUNITED KINGDOMTel: +44 0 1279 501110Fax: +44 0 1279 659870

Alpha Technologies GmbHHansastrasse 8D 91126 SchwabachGERMANYTel: +49 9122 79889 0Fax: +49 9122 79889 21

Alphatec, LtdP.O. Box 56468Limassol, CyprusCYPRUSTel: +357 25 375675Fax: +357 25 359595

AlphaTEK oooKhokhlovskiy Pereulok 16Stroenie 1, Office 403109028 MoscowRUSSIATel: +7 495 916 1854Fax: +7 495 916 1349

Alphatec Baltics S. Konarskio G. 482009 VilniusLITHUANIATel: +370 5 213 8822Fax: +370 5 213 7799

Alpha Technologies9, Impasse Sans Souci92140 Clamart FranceFRANCETel: +33 141 900 707Fax: +33 141 909 312

Documents

AlphaNet DSM Series - Alpha Technologies Services Inc · Section 3.1). The DOCSIS Configuration File should be saved in the TFTP Root Directory of the Trivial File Transfer Protocol