AlphaNet DSM Series DOCSIS Status Monitor

Transcription

1 AlphaNet DSM Series DOCSIS Status Monitor Technical Manual Model XP-DSM Effective: June 2007 Alpha Technologies

2 Power Alpha Technologies

3 AlphaNet DSM Series DOCSIS Status Monitor Technical Manual B0-001, Rev. A Effective Date: June, 2007 Copyright 2007 Alpha Technologies, Inc. member of The Group TM NOTE: Alpha denies responsibility for any damage or injury involving its enclosures, power supplies, generators, batteries or other hardware, manufactured by Alpha or members of the Alpha Group, when used for an unintended purpose, installed or operated in an unapproved manner, or improperly maintained. NOTE: Photographs and drawings in this manual are for illustrative purposes only and might not exactly match your installation. NOTE: Review this manual before proceeding. If there are questions regarding the safe installation or operation of this product, please contact Alpha Technologies or your nearest Alpha representative. Contacting Alpha Technologies: or For general product information and customer service (7 AM to 5 PM, Pacific Time), call For complete technical support, call AM to 5 PM, Pacific Time or 24/7 emergency support To report errors in this document, send to:techpubs@alpha.com 3

4 Table of Contents Safety Notes Introduction System Overview System Diagram Single IP Mode vs. Dual IP Mode Overview Network Connectivity Overview System Configuration and Installation Overview XP-DSM Start-up and Reboot Routine Network Configuration and Option Settings Provisioning the DHCP Server with the MAC Addresses The DOCSIS Configuration File Setting Modem Community Strings in the DOCSIS Configuration File Example DOCSIS Configuration File Setting Communication Options The DSM Setup File Building the DSM Setup File Example of an atidoc01.cfg DSM Setup File Setting Transponder Community Strings with the DSM Setup File Security in Dual IP Mode Using the Local Port Upgrading Firmware Upgrading XP-DSM Modem Firmware Identifying the Modem and Obtaining Firmware Files Modem Firmware Upgrade SNMP Parameters Upgrading Modem Firmware Manually by Setting SNMP Parameters Upgrading Modem Firmware in the DOCSIS Configuration File Upgrading XP-DSM Transponder Firmware Remotely Upgrading XP-DSM Firmware Upgrading XP-DSM Firmware Using a DSM Setup File Data Management The SCTE-HMS MIB The Alpha MIB B0-001, Rev. A

5 6.3 SCTE-HMS MIB Alarms SCTE-HMS Configurable Alarms Distributing Alarm Settings SNMP Traps General Power Supply Alarms Hardware Installation Verifying Power Supply Device Address Hardware Installation Procedure XP-DSM Connections Front Panel Diagram Connecting the RF Drop Front Panel Connections Battery Sense Wire Kit Connections V Single and Dual Strings V Single and Dual Strings Start-up and Verification Initial Startup LEDs and System Status Verifying Successful Hardware Installation Verifying Communications via the Headend MIB Parameter Definitions and Settings Alpha MIB Parameter Definitions and Settings Modem Firmware Upgrade Parameter Definitions and Settings Frequently Asked Questions Specifications Glossary B0-001, Rev. A 5

6 Figures Fig. 1-1, AlphaNet XP-DSM...8 Fig. 2-1, Single IP Mode...10 Fig. 2-2, Dual IP Mode...10 Fig. 3-1, Location of MAC Addresses...14 Fig. 3-2, Example DOCSIS Configuration File...16 Fig. 6-1, Example SNMP Alarm Trap...41 Fig. 7-1, Removing the Inverter Module from the Power Supply...45 Fig. 7-2, The 18-pin Jumper...46 Fig. 7-3, Connecting the Transponder to the Inverter Module...46 Fig. 7-4, Front Panel...47 Fig. 7-5, Connecting the RF Drop...47 Fig. 7-6, System Interconnection Diagram...48 Fig. 8-1, 36V System, Single String...49 Fig. 8-2, 36V System, Dual String...49 Fig. 8-3, 48V System, Single String...50 Fig.8-4, 48V System, Dual String...50 Fig. 9-1, LED Indications...52 Tables Table 3-1, Modem Community String Parameters...15 Table 3-2, Transponder Communications Parameters...17 Table 3-3, Example DSM Setup File Parameters and Values...19 Table 3-4, Transponder Community String Parameters...20 Table 5-1, Modem Firmware Upgrade SNMP Parameters...24 Table 5-2, Transponder Firmware Upgrade SNMP Parameters...26 Table 6-1, SCTE-HMS MIB Hierarchy...31 Table 6-2, Alpha MIB Hierarchy...33 Table 6-3, Binary to Hex Conversions for Alarm Settings...35 Table 6-4, Analog Alarms and Common Settings...36 Table 6-5, Discrete Alarm Definitions and Common Settings...38 Table 6-6, SNMP Alarm Trap Varbinds and Explanations...42 Table 6-7, XM2 Major and Minor Alarms B0-001, Rev. A

7 Safety Notes Review the drawings and illustrations contained in this manual before proceeding. If there are any questions regarding the safe installation or operation of the system, contact Alpha Technologies or the nearest Alpha representative. Save this document for future reference. To reduce the risk of injury or death, and to ensure the continued safe operation of this product, the following symbols have been placed throughout this manual. Where these symbols appear, use extra care and attention. ATTENTION: The use of ATTENTION indicates specific regulatory/code requirements that may affect the placement of equipment and /or installation procedures. NOTE: A NOTE provides additional information to help complete a specific task or procedure. CAUTION! The use of CAUTION indicates safety information intended to PREVENT DAMAGE to material or equipment. WARNING! WARNING presents safety information to PREVENT INJURY OR DEATH to the technician or user B0-001, Rev. A 7

8 1.0 Introduction The AlphaNet DSM Series Embedded DOCSIS Transponder (XP-DSM) allows monitoring of Alpha XM2 and GMX power supplies through existing cable network infrastructure. Advanced networking services provide quick reporting and access to critical powering information. The XP-DSM utilizes Simple Network Management Protocol (SNMP) and standard Management Information Bases (MIBs) to provide network status monitoring and diagnostics. A Web interface enables authorized personnel direct access to advanced diagnostics using a common Web browser. No custom software is required. Primary Features: 10/100 Mbps auto-negotiating standard interface Supports SNMPv1, v2c Extensive power supply diagnostic MIBs Embedded Web server for direct diagnostics Directly monitors up to two 36V or 48V battery strings Environmentally hardened DOCSIS cable modem and transponder Supports both Single IP and Dual IP applications Single XP-DSM supports communications and system control for up to three XM2 power supplies and an AlphaGen backup generator system Automatic firmware upgrades Configuration cloning Local port provides technician access to extensive power supply diagnostics Cable Modem Transponder Fig. 1-1, AlphaNet XP-DSM B0-001, Rev. A

9 N+1 N+1 OUTPUT 1B LRI OUTPUT 2 OUTPUT 1A Battery Breaker Battery Input Temp Probe ALM RDY COM LNK RF REG DS TMPR CTRL C O M E T H A B L O CA L C D 2.0 System Overview 2.1 System Diagram 10 MIB Browser 1 Power Supply 2 XP-DSM 4 Coax/HFC Network 5 CMTS 6 TCP/IP Network 3 Local Computer 7 DHCP Server 8 TFTP Server 9 TOD Server 11 Web Browser 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 ) (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 = HTTP The Dynamic Host Configuration (DHCP) server needs to be provisioned with the XP-DSM s cable modem RF MAC Address: the MAC Address needs to be assigned a DOCSIS Configuration File (see Section 3.1). 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) B0-001, Rev. A 9

10 2.0 System Overview, continued 2.2 Single IP Mode vs. Dual IP Mode Overview The XP-DSM can operate in either Single (default) or Dual IP Mode. To switch the transponder from Single to Dual IP Mode the Block CPE function must be disabled in the Discrete Menu of the Alpha MIB (see Section 6.2). Single IP Mode In Single IP Mode all data from both the cable 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: One CM IP address only accessible on the private (LAN) network with access to both CM and transponder data. Cable Modem XP-DSM Transponder MIB Tables Fig. 2-1, Single IP Mode Communication with the transponder is limited to the private LAN network, and is very secure. Where the IP address pool is limited, there is no need to issue the transponder a CPE IP address. Access to the transponder is limited to the private LAN network making data management less versatile, especially for field personnel. Dual IP Mode In Dual IP Mode the transponder acts like a CPE device to the cable modem, and registers a second IP address on the public CPE network. 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. CM IP address, CM and transponder data; accessible on the private (LAN) network. Cable Modem CPE IP address, transponder data only; accessible on the public (CPE) network. XP-DSM Transponder (CPE) MIB Tables 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. Fig. 2-2, Dual IP Mode 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 B0-001, Rev. A

11 2.0 System Overview, continued 2.3 Network Connectivity Overview The XP-DSM cable modem must be recognized by the CMTS as a valid device to be assigned an IP address from the DHCP server, locate the TFTP and TOD servers, and communicate with the SNMP management server (trap receiver) (see Section 2.5). CMTS and system vendors use different security methods to insure network integrity, but common considerations are: MAC filtering may have to be modified to allow RF MAC registration of addresses starting with 00.05:CA and 00:03:08. For SNMP access, UDP ports 161 & 162 must not be blocked. For TFTP access, port 69 must not be blocked. For HTTP access, port 80 must not be blocked. For Web access with firmware version , allow traffic on port 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. NOTE: 2.4 System Configuration and Installation Overview 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 B0-001, Rev. A 11

12 N+1 N+1 1B I 2 1A ttery ttery In t e 2.0 System Overview, continued 2.5 XP-DSM Start-up and Reboot Routine TFTP Server Network Management System TCP/IP Network TOD Server DHCP Server 6a 6b 6c MIB Browser Web Browser Network Devices CMTS HFC Network Cable Modem DSM Transponder 7 Local Laptop Time The above diagram, read left to right, indicates the order of operations as the transponder comes online. There are certain conditions that must exist for each step to occur, resulting in successful data monitoring and management. The numbers below correspond to the numbered arrows above 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) B0-001, Rev. A

13 2.0 System Overview, continued 2.5 XP-DSM Start-up and Reboot Routine, continued 6 7 Monitoring and Managing Transponder and Power Supply Parameters. 6a 6b 6c 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 ) (Section 4.0) B0-001, Rev. A 13

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

15 3.0 Network Configuration, continued NOTE: 3.2 The DOCSIS Configuration File A cable modem s DOCSIS Configuration File is a type-length-value (TLV) file that contains important operational parameters as defined by the DOCSIS standards. It provides certain settings for the cable modem. In addition to standard entries, settings in the DOCSIS Configuration File should include the modem s community strings and firmware upgrade parameters. Place the configuration file in the TFTP root directory. Due to different firmware and manufacturers Code Verification Certificate (CVC) files, separate DOCSIS Configuration Files are required for the two cable modem versions used with the XP-DSM in order to upgrade modem firmware: If your network includes both versions, you will need to create two Configuration Files. The cable modem version is indicated by the Organizationally Unique Identifier (OUI) of the cable modem s RF MAC Address (see Section 5.1): 00:03:08 AM 00:05:CA Hitron To build a DOCSIS Configuration File use a DOCSIS TLV editor program. See the example Configuration File on the next page. 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 Setting Modem Community Strings in the DOCSIS Configuration File Set the modem community strings with the DOCSIS Configuration File by including in it the following SNMP parameters: MIB Parameter Object ID Description Value docsdevnmaccessstatus docsdevnmaccessip The IP address (or subnet) of the network management station docsdevnmaccessipmask The IP subnet mask of the network management stations docsdevnmaccesscommunity The community string matched to this IP/Mask entry e.g docsdevnmaccesscontrol The level of access granted 1= none Table 3-1, Modem Community String Parameters e.g alphanumeric string 2= read only 3= read/write NOTE: In Single IP Mode the community strings set in the DOCSIS Configuration File override any community strings set in the Alpha MIB for the transponder (Section 3.3). In Dual IP Mode or if the modem is left unsecured, the XP-DSM transponder reverts to default community strings. Change these strings through the Alpha MIB (Section 6.2), either manually using a MIB browser or automatically using a DSM Setup File (Section 3.4) B0-001, Rev. A 15

16 3.0 Network Configuration, continued 3.2 The DOCSIS Configuration File, continued Example DOCSIS Configuration File Example 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. Sets firmware download parameters. Specifies location of DSM Setup File atidoc01.cfg Sets Code Verification Certificate (CVC) SNMP MIB Object (11) [Len=21]:docsDevNmAccessStatus.1/4 SNMP MIB Object (11) [Len=21]:docsDevNmAccesslp.1/ SNMP MIB Object (11) [Len=21]:docsDevNmAccesslpMask.1/ SNMP MIB Object (11) [Len=25]:docsDevNmAccessCommunity.1/"RW STRING" SNMP MIB Object (11) [Len=21]:docsDevNmAccessControl.1/3 SNMP MIB Object (11) [Len=21]:docsDevNmAccessStatus.2/4 SNMP MIB Object (11) [Len=21]:docsDevNmAccesslp.2/ SNMP MIB Object (11) [Len=21]:docsDevNmAccesslpMask.2/ SNMP 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.bin SNMP MIB Object (11) [Len=20]:docsDevSwAdminStatus.0/2 Software Upgrade TFTP Server (21) [Len=4]: Manufacturer Code Verification Certificate (32) [Len=254]: A Manufacturer Code Verification Certificate (32) [Len=254]: 04 0A D... Manufacturer Code Verification Certificate (32) [Len=254]: 04 0C 30 0A Manufacturer Code Verification Certificate (32) [Len=36]: 11 A3 41 A6 A7 D9... Fig. 3-2, Example DOCSIS Configuration File B0-001, Rev. A

17 3.0 Network Configuration, continued 3.3 Setting Communication Options The XP-DSM ships with the following default communication option settings: Access Mode Single IP Network registration DHCP HTTP Web Server Enabled Read Community String AlphaGet Read/Write Community String AlphaSet Communications Settings may be changed through the Alpha MIB remotely using a SNMP MIB browser, automatically using a DSM Setup File (see Section 3.4), or by connecting directly to the front of the XP-DSM using a PC or laptop and the local port (see Section 4.0). See Section 6.2 for an explanation of the Alpha MIB. NOTE: Before setting options, verify UDP ports 161 and 162, and TCP ports 80 and 69 are not blocked. SNMP Parameter Local Port Parameter Type Description Value AtiMgmtSnmpCommGet OID: AtiMgmtSnmpCommSet OID: aticibdisctable [Text] SNMP GET [Text] SNMP SET Alphanumeric String Alphanumeric String Read Community String Read/Write Community String [Discretes] BLOCK CM Integer Block access to power supply data through modem AlphaGet (default) AlphaSet (default) 0 = Disabled (Default) 1 = Enabled aticibdisctable aticibdisctable [Discretes] BLOCK CPE Integer Access Mode (Single/Dual IP) 0 = Dual IP [Discretes] TRAP ON NORMAL Integer Send SNMP trap when alarmed condition returns to normal state 1 = Single IP (Default) 0 = Disabled (default) 1 = Enabled aticibdisctable aticibdisctable aticibtexttable aticibtexttable aticibtexttable atimgmtsnmptraptable atimgmtsnmpaccesstable aticibcounttable aticibcounttable AtiMgmtSysHttpAccess OID: See Section 10.0 for complete parameter definitions. NOTE: [Discretes] HTTP SERVER Integer Display CIB Tables on Web page [Discretes] HTTP TEXT Integer Display TEXT table on Web page Table 3-2, Transponder Communications Parameters 0 = Disabled 1 = Enabled (default) 0 = Disabled (default) 1 = Enabled [Text] IP ADDR STATIC IP address Static IP Address Assignment (Default) [Text] IP NETMASK STATIC IP address Static IP NETMASK (Default) [Text] IP GATEWAY STATIC IP address Static IP Gateway (Default) [Text] SNMP TRAP TARGET IP address SNMP Destination Trap Address (Default) [Text] SNMP ACCESS LIST IP address (Dual IP Only) Restricted DSM SNMP Access [Counters] RECONFIG TIMER Integer Download interval for DSM Setup File atidoc01.cfg (Hours) [Counters] SNMP COM TIMEOUT Integer Time DSM will wait before reset if SNMP traffic not detected (Hours) (Default) 24 (Default) 24 (Default) [Discretes] HTTP SERVER Integer HTTP Web Server SNMP Local Port 1 = Disable 1 = Enable 2 = Enable 0 = Disable 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 B0-001, Rev. A 17

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

19 3.0 Network Configuration, continued 3.4 The DSM Setup File, continued Example of an atidoc01.cfg DSM Setup File Below is an example DSM Setup File with the following settings: Example DSM Setup File Parameters and Values Parameter Type Description Value atimgmtsysdownloadcfgcheckprogress OID: atimgntsnmptrapaddress1 OID: atimgntsnmptrapaddress2 OID: aticibdiscvalue.sys.1.6 OID: Integer Required file marker entry 3 IP address Optional SNMP trap destination address IP address Optional SNMP trap destination address Integer Sets XP-DSM into Dual IP Mode 1 = single IP (default) 0 = dual IP atimgmtsnmpsnmpv1access OID: Integer Required to allow remote SNMPv1 access to power supply data 1 = disable 2 = enable (default) atimgmtsnmpsnmpv2access OID: Integer Required to allow remote SNMPv2 access to power supply data 1 = disable 2 = enable (default) atimgmtsyshttpaccess OID: atimgmtsysdownloadtftpaddress OID: atimgmtsysdownloadfile1 OID: Integer Enables embedded HTTP Web server to allow XP-DSM data to be visible from Internet Web browser. Firmware Download 1 = disable 2 = enable (default) IP address Address of modem s TFTP server Filename Firmware filename esm1100_.phy atimgmtsysdownloadctrl OID: See Section 10.0 for complete parameter definitions. Integer Trigger file initiates firmware upgrade 1 Table 3-3, Example DSM Setup File Parameters and Values Example DSM Setup File File: atidoc01.cfg Network Access Control (3) [Len - 1]: 1 SNMP MIB Object (11) [Len = 23]: atimgmtsysdownloadcfgcheckprogress.0 / 3 SNMP MIB Object (11) [Len = 24]: atimgntsnmptrapaddress1 / SNMP MIB Object (11) [Len = 24]: atimgntsnmptrapaddress2 / 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 / SNMP MIB Object (11) [Len = 31]: atimgmtsysdownloadfile1.0 / esm1100_.phy SNMP MIB Object (11) [Len = 23]: atimgmtsysdownloadctrl.0 / B0-001, Rev. A 19

20 3.0 Network Configuration, continued 3.4 The DSM Setup File, continued Setting Transponder Community Strings with the DSM Setup File The default transponder read-only community string is AlphaGet. The default read-write community string is AlphaSet. These community strings are overridden by modem community strings set in the DOCSIS Configuration File. If the modem is left unsecured or if operating in Dual IP Mode, the XP-DSM needs to have its community strings set in the Alpha MIB. This can be done with the DSM Setup File by including the following parameters: Parameter Type Description Value AtiMgmtSnmpCommGet OID: AtiMgmtSnmpCommSet OID: Alphanumeric String Alphanumeric String Read Community String Read/Write Community String Table 3-4, Transponder Community String Parameters [desired value] [desired value] B0-001, Rev. A

21 3.0 Network Configuration, continued NOTE: 3.5 Security in Dual IP Mode In Dual IP Mode additional SNMP security is required because data is exposed on the CPE network, which is more vulnerable to packet sniffing and community string deciphering than on the secure cable modem network. For an explanation of Dual IP Mode, see Section 2.2. For an explanation of the Alpha MIB, see Section 6.2. There are two methods of providing SNMP Security in Dual-IP Mode: the Secure Access List, and the Key-Match. Method 1: Security Using the Secure Access Table The Secure Access List method limits remote SNMP access to four IP addresses. Only those IP addresses listed in the SNMP Access Table are able to read or write to the Alpha MIB parameters from the public (CPE) network. Set the IP addresses through the following Alpha MIB parameter: SNMP Parameter Local Port Parameter Description Type Value atimgmtsnmpaccesstable [Text] SNMP ACCESS LIST Restricted DSM SNMP Access IP address (Default) 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. If the entries in the SNMP Access Table are set remotely using SNMP through the cable modem s IP address, then the SNMP community strings will have to be used. However, if they are set remotely through the public (CPE) IP address the data access key, explained below, must be used to gain access. The XP-DSM transponder variables will still be accessible through the private modem management network using the community strings without requiring additional security. Method 2: Security Using the Data Access Key SNMP Parameter Local Port Parameter Description Type Value atimgmtsnmpalphasetaccess atimgmtsnmpalphasetkey ALPHA SNMP SETS [Discretes] ALPHA SNMP SETS Set to Access Key Read/Write Octet String [Text] ALPHA SNMP SETS Data Access Key Read/Write Octet String [Discretes] ALPHA SNMP SETS OID of Dicrete Table Value Read/Write Integer Set to match the value of atimgmtsnmpalphasetkey CIBSET (default) 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 B0-001, Rev. A 21

22 N+1 N+1 OUTPUT 1B LRI OUTPUT 2 OUTPUT 1A Battery Breaker Battery Input Temp Probe ALM RDY COM LNK RF REG DS TMPR CTRL C O M E T H A B L O CA L C D 4.0 Using the Local Port The local port allows a technician to monitor and set XP-DSM parameter values directly using a personal computer and a Local Port Adapter Cable (Alpha Alpha P/N ). Terminal emulation software is necessary (HyperTerminal is recommended). Procedure: 1. Launch the terminal emulation software. Serial Communication Settings Baud Data Bits 8 Parity None Stop Bits 1 Flow Control None Discrete Table 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. SYS-1 06 SNMPv1 1 ENABLED YES Subsystem Parameter Index Power Supply BSS XM2 SYS ECM Entry Explanation Parameter Value Enumerated Value Subsystem Definitions Battery System Power Supply System Transponder System Generator System Modifiable? 4. To set a parameter value, enter: >[table] [subsystem] [power supply] [Index] [Value] ENTER. Hit ENTER Result: Example Command To disable SNMPv1, enter the command: >dis sys Table Subsystem Power Supply Parameter Index Value SYS-1 06 SNMPv1 0 DISABLED YES 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 SELECT FROM : ANALOGS CONFIG COUNTERS DISCRETES TEXT >dis DISCRETES DEV-A IX NAME VALUE ENM/UNIT SET BSS-1 00 GENERAL STATUS 0 OK NO XM GENERAL STATUS 0 OK NO XM SELF TEST FAIL 0 OK NO XM LOW BATT VOLTS 0 OK NO XM HIGH BATT VOLTS 0 OK NO XM NO BATTERIES 0 OK NO XM BATT TEMP PROBE 0 OK NO XM LINE ISOLATION 0 OK NO XM OUTPUT FAILURE 0 OK NO XM OUTPUT OVERLOAD 0 OK NO XM OUTPUT 1 TRIPPED 0 OK NO XM OUTPUT 2 TRIPPED 0 OK NO XM CHARGER FAILURE 0 OK NO XM INPUT FAILURE 0 OK NO XM INV DISCONNECTED 0 OK NO XM INVERTER TEMP 0 OK NO XM TAP SWITCH 0 NO NO XM PIM OPTION 0 NO NO XM N+1 VALID 0 NO NO XM SELF TEST 0 OFF YES XM TEST INHIBIT 0 YES XM ACCEPT/FLOAT 0 FLOAT YES XM INVERTER ENABLE 1 ON NO XM CHARGER ENABLE 1 ON NO XM RESET OUT 1 1 YES XM RESET OUT 2 0 NO YES XM N+1 IN USE 0 NO NO XM SET DEFAULTS 0 NO YES XM FACTORY TEST 0 OFF NO XM TAP FUSE FAIL 0 OK NO XM CONFIG ERROR 0 OK NO XM N+1 FAULT 0 OK NO XM BB-CMM/CMT OPT 0 NO YES SYS-1 00 AUTO CONFIG 0 ENABLED YES SYS-1 01 TAMPER ALARM 0 OK NO SYS-1 02 TAMPER ALM WHEN 0 CLOSED YES SYS-1 03 MGMT MSG TARGET 0 CPE NO SYS-1 04 BLOCK CM 0 NO YES SYS-1 05 BLOCK CPE 0 NO YES SYS-1 06 SNMPv1 1 ENABLED YES SYS-1 07 SNMPv2 1 ENABLED YES SYS-1 08 ALPHA SNMP SETS 1 ENABLED YES SYS-1 09 TRAP ON NORMAL 0 DISABLED YES SYS-1 10 HTTP SERVER 1 ENABLED YES SYS-1 11 HTTP TEXT 0 DISABLED YES SYS-1 12 PING REQUEST 0 YES SYS-1 13 GET NEW IMAGE 0 YES SYS-1 14 COM BUS DAT SIZE 0 9 BIT YES SYS-1 15 DEVICE RESET 0 RUNNING YES SYS-1 16 DEBUG MESSAGES 0 ENABLED YES SYS-1 17 PI CURRENT MODE 0 ENABLED YES B0-001, Rev. A

23 4.0 Using the Local Port, continued >tex TEXT [ro] DHCP STATE : DISCOVER SENT 1 [ro] DHCP TIMER : 0 2 [ro] DHCP SERV : [ro] DHCP SERV 54 : [ro] DOWN STAT : 5 [rw] DOWN NAME 1 : 6 [rw] DOWN NAME 2 : 7 [rw] DOWN IP : [rw] DOWN CFG : 9 [rw] DOWN CFG IP : [rw] NTP SERV : [ro] NTP DHCP : [ro] NTP TIME UTC : 01/01/70 00:00:00 13 [ro] ENET ADDR : EA.A0.1E.5F 14 [ro] IP ADDR IN USE : [ro] NETMASK IN USE : [ro] GATEWAY IN USE : [rw] IP ADDR STATIC : [rw] NETMASK STATIC : [rw] GATEWAY STATIC : [rw] SNMP TRAP TARGET : [rw] SNMP TRAP TARGET : [rw] SNMP TRAP TARGET : [rw] SNMP TRAP TARGET : [rw] SNMP ACCESS LIST : [rw] SNMP ACCESS LIST : [rw] SNMP ACCESS LIST : [rw] SNMP ACCESS LIST : [ro] sysdescr : ATI P01V [rw] sysname : 30 [rw] syscontact : 31 [rw] syslocation : 32 [rw] comlogicalid : 33 [ro] CHECK CODE : [rw] PING IP : [rw] ATICONFIG IP : [rw] ATICONFIG NAME : 37 [ro] TIME UP : 0 00:00:29 38 [ro] CM/RF ENET : B.9A.EA 39 [ro] CM IP : [ro] CM SUBNET : [ro] CM GATEWAY : [ro] CM TOD : [ro] CM TFTP : [rw] SNMP GET : AlphaGet 45 [rw] SNMP SET : AlphaSet 46 [rw] SNMP TRAP : public 47 [rw] ALPHA SNMP SETS : CIBSET NOTE: Note: no subsystem Text Table 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 Analogs Table ANALOGS DEV-A IX NAME VALUE ENM/UNIT SET BSS-1 00 BATT 1A 0.00 VDC NO BSS-1 01 BATT 2A 0.00 VDC NO BSS-1 02 BATT 3A 0.00 VDC NO BSS-1 03 BATT 4A 0.00 VDC NO BSS-1 04 BATT 1B OR 5A 0.00 VDC NO BSS-1 05 BATT 2B OR 6A 0.00 VDC NO BSS-1 06 BATT 3B OR 7A 0.00 VDC NO BSS-1 07 BATT 4B OR 8A 0.00 VDC NO XM INPUT VOLTAGE Vac NO XM INPUT FREQ Hz NO XM OUTPUT VOLTAGE Vac NO XM OUTPUT 1 CURR 0.00 A NO XM OUTPUT 2 CURR 0.00 A NO XM PERCENT LOAD 0.00 % NO XM OUTPUT VA 0.00 VA NO XM OUTPUT WATTS 0.00 W NO XM BATT VOLTAGE Vdc NO XM CHARGER CURR 1.20 A NO XM BATTERY TEMP oc NO XM FREQ RANGE 3.00 Hz YES XM FLOAT V/C 2.25 YES XM ACCEPT V/C 2.35 YES XM TEMP COMP 3.00 mv YES XM PEAK CURR A YES XM PEAK CURR A YES XM CHGR CURR LIMIT A NO XM EOD VOLTAGE V/C 1.75 YES SYS-1 00 INPUT CURRENT 2.30 A NO >cou Counters Table COUNTERS DEV-A IX NAME VALUE ENM/UNIT SET BSS-1 00 NUMBER OF BATTS 0 YES BSS-1 01 NUMBER OF STRNGS 0 YES XM TEST INTERVAL 30 DAY YES XM TEST COUNTDOWN 30 DAY YES XM TEST DURATION 10 MIN YES XM STANDBY TIME 163 MIN YES XM STANDBY EVENTS 164 YES XM RETRY DELAY 60 SEC YES XM RETRY LIMIT 20 YES XM OVER CURR TOL 3 SEC YES XM BATT CAPACITY 100 AH YES XM RESERVED 0 BMP NO XM DEVICE ADDRESS 1 YES XM TOTAL RUN TIME 496 DAY NO SYS-1 00 PING CYCLE TIME 10 MIN YES SYS-1 01 POLL CYCLE TIME 10 SEC YES SYS-1 02 POLL RETRIES 5 YES SYS-1 03 ENGINE BOOTS HI 0 YES SYS-1 04 ENGINE BOOTS LO 5 YES SYS-1 05 TRAP SEND COUNT 0 YES SYS-1 06 SNMP COM TIMEOUT 24 HR YES SYS-1 07 RECONFIG TIMER 24 HR YES B0-001, Rev. A 23

24 5.0 Upgrading Firmware 5.1 Upgrading XP-DSM Modem Firmware The firmware in the XP-DSM s modem is upgraded using standard DOCSIS methods as defined in RFC2669 (available at 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 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: 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 Parameters Modem Firmware Upgrade SNMP Parameters Parameter Type Value docsdevsoftware OID: docsdevswserver OID: docdevswfilename OID: docsdevswadminstatus OID: docsdevswoperstatus OID: docsdevswcurrentvers OID: IP address Octet String Integer Read Only, Integer Read Only, Octet String Set to the IP address of the TFTP server from which the firmware will be downloaded. Set to the filename of the firmware file downloaded from the Alpha website. Example: [ firmwareimage.bin ] 1 = Initiate upgrade 2 = Upgrade on next reboot 3 = Ignore update 1 = A TFTP download is in progress. 2 = Last upgrade was performed at reboot 3 = Last upgrade was initiated by setting docsdevswadminstatus to 1 4 = Firmware upgrade failed 5 = Other The current version of firmware installed in the modem Table 5-1, Modem Firmware Upgrade SNMP Parameters B0-001, Rev. A

25 5.0 Upgrading Firmware, continued 5.1 Upgrading XP-DSM Modem Firmware, continued 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 Parameter Value docsdevswserver Address of TFTP server docdevswfilename Firmware filename docsdevswadminstatus 1 The firmware upgrade will begin immediately. Monitor the upgrade with the docsdevswoperstatus MIB parameter, and verify it with the docsdevswcurrentvers MIB parameter (see table above). Once the firmware has been upgraded, the modem will automatically reset to the new version Upgrading Modem Firmware in the DOCSIS Configuration File Modem Firmware can be automatically updated in the DOCSIS Configuration File by including in it the following docsdevsoftware SNMP parameters and the manufacturer s Code Verification Certificate (CVC). Parameter Value docsdevswserver Address of TFTP server docdevswfilename Firmware filename docsdevswadminstatus 2 Manufaacturer CVC The CVC file for you modem version The firmware will be upgraded on the next reboot. Monitor the upgrade with the TFTP server log of with the docsdevswoperstatus MIB parameter, and verify it with the docsdevswcurrentvers MIB parameter (see table above). Once the firmware has been upgraded, the modem will automatically reset to the new version B0-001, Rev. A 25

26 5.0 Upgrading Firmware, continued 5.2 Upgrading XP-DSM Transponder Firmware There are three methods to upgrade XP-DSM firmware: manually setting SNMP parameters remotely in a MIB browser, setting them through the local port (see Section 4.0), and automatically in the DSM Setup File (to build a Setup File, see Section 3.4). Once the firmware download process has been initiated the XP-DSM will download the DSM firmware from the specified TFTP server. The XP-DSM remains fully functional during the upgrading process and will automatically reset when the upgrade is finished. The most recent firmware version files are available at Monitoring>DSM>XP-DSM Tech. Support. Parameter atimgntsysdownload OID: atimgmtsysdownloadtftpaddress OID: atimgmtsysdownloadctrl OID: atimgmtsysdownloadstatus OID: atimgmtsysdownloadfile atimgmtsysdownloadprogress OID: atimgmtsysdownloadsysdescr OID: atimgmtsysdownloadsysobjectid OID: atimgmtsysdownloadcfgcheckprogress OID: See Section 10.0 for complete parameter definitions. XP-DSM Firmware Upgrade Parameters Local Port Type Parameter [Text] DOWN IP [Discrete] GET NEW IMAGE [Text] DOWN STAT [Text] DOWN NAME 1 IP address Integer Read Only Integer Octet String Integer Octet String OID Integer Table 5-2, Transponder Firmware Upgrade SNMP Parameters Value The IP address of the modem s TFTP server from which the firmware will be downloaded. 1 = Initiate Download of firmware file 2 = Initiate Download of two firmware files (version ) 3 = Idle 1 = Idle 5 = Transferring 6 = Testing 8 = Error Set to the filename of the firmware file downloaded from the Alpha Website. Byte count of firmware download process. Firmware version. Alpha will provide this value with released firmware (OID embedded in transponder to ensure firmware compatibility.) 3 (file maker, only used with DSM Setup File.) 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 or newer. For an application to upgrade from earlier firmware versions, go to Monitoring>DSM>XP-DSM Tech. Support B0-001, Rev. A

27 5.0 Upgrading Firmware, continued 5.2 Upgrading XP-DSM Transponder Firmware, continued Remotely Upgrading XP-DSM Firmware This section explains how to upgrade the XP-DSM firmware from version to a more recent version by manually setting SNMP parameters. Firmware can also be upgraded automatically (see Section 5.2.2). Procedure: 1. Download the most recent firmware version from the Alpha Website and load it on the TFTP server. 2. Using a MIB browser or the local port, set the following Alpha MIB parameter values: Parameter Local Port Parameter Value atimgmtsysdownloadtftpaddress [Text] DOWN IP Address of TFTP server atimgmtsysdownloadfile1 [Text] DOWN NAME 1 Firmware filename, e.g. esm1100_.phy atimgmtsysdownloadctrl [Discretes] GET NEW IMAGE 1 (initiate download of one firmware file) 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: ) Upgrading XP-DSM Firmware Using a DSM Setup File NOTE: The procedure in this section applies to firmware version or newer. For an application to upgrade from earlier firmware versions, go to Monitoring>DSM>XP-DSM Downloads. This section explains how to upgrade the XP-DSM firmware from version 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 B0-001, Rev. A 27

28 5.0 Upgrading Firmware, continued 5.2 Upgrading XP-DSM Transponder Firmware, continued Upgrading XP-DSM Firmware Using a DSM Setup File, continued 3. Include in the atidoc01.cfg Setup File the following Alpha MIB parameters and values: Parameter Local Port Parameter Value atimgmtsysdownloadrecfgtime [Counters] RECONFIG TIMER 0 (disable automatic upgrade) atimgmtsysdownloadtftpaddress [Text] DOWN IP Address of TFTP server atimgmtsysdownloadfile1 [Text] DOWN NAME 1 Firmware filename, e.g. esm1100_.phy atimgmtsysdownloadctrl [Discretes] GET NEW IMAGE 1 (initiate download of one firmware file) atimgmtsysdownloadsysdescr NA Provided with firmware release notes, e.g. ATIP01V1.12.0_ atimgmtsysdownloadsysobjectid NA OID embedded in transponder to ensure firmware compatibility, provided with release notes 4. Load the atidoc01.cfg setup file onto the TFTP server. 5. Within 24 hours all XP-DSMs on the network will begin downloading the new firmware B0-001, Rev. A

29 N+1 N+1 OUTPUT 1B LRI OUTPUT 2 OUTPUT 1A Battery Breaker Battery Input Temp Probe ALM RDY COM LNK RF REG DS TMPR CTRL C O M E T H A B L O CA L C D 6.0 Data Management The XP-DSM remotely reports power supply data and alarms using the Simple Network Management Protocol (SNMP) over the DOCSIS (Data Over Cable Service Interface Specification) communication specification. The XP-DSM typically reports into a centralized Network Management System (NMS) through a standard collection of data access points referred to as the SCTE-HMS Management Information Bases (MIBs). The NMS polls the XP-DSM for power supply data with the option of having the XP-DSM send SNMP traps in the event that an alarm condition is met. In addition to the SCTE-HMS MIBs, the XP-DSM also supports the Alpha proprietary SNMP MIB (the Alpha MIB), which allows direct access to the power supply as well as the ability to change transponder settings. Power supply and transponder settings can also be viewed and set with a local PC via the local port on the front of the XP-DSM (see Section 4.0). Transponder and power supply data can also be monitored with an Internet Web browser. Network Management System (NMS) or MIB Browser: SNMP Web Browser: http XP-DSM SCTE-HMS MIBs Alpha MIB Local Computer: RS485 Power Supply Data 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 Distributing Alarm Settings: Section SNMP Traps: Section General Power Supply Alarms: Section B0-001, Rev. A 29

30 6.0 Data Management, continued 6.1 The SCTE-HMS MIB The SCTE-HMS MIB can be monitored with a SNMP compatible Network Management System (NMS) or with a MIB browser. The following MIB files are required for the MIB browser to collect data from the transponder. These files can be found on the Society of Cable Telecommunications (SCTE) Web site: There are dependencies between MIB files, so they should be compiled in the following order. ANSI/SCTE (formerly HMS 028), SCTE-ROOT Management Information Base (MIB) Definitions ANSI/SCTE (formerly HMS 072), Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-ROOTS Management Information Base (MIB) Definition ANSI/SCTE (formerly HMS 024), Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-COMMON-MIB Management Information Base (MIB) Definition ANSI/SCTE (formerly HMS 026), Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-PROPERTY-MIB Management Information Base (MIB) Definition ANSI/SCTE Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-ALARMS-MIB Management Information Base (MIB) Definition ANSI/SCTE (formerly HMS 027), Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-PS-MIB Management Information Base (MIB) Definition ANSI/SCTE (formerly HMS 033) Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-GEN-MIB Management Information Base (MIB) Definition B0-001, Rev. A

31 6.0 Data Management, continued 6.1 The SCTE-HMS MIB, continued scteroot ( ) sctehmstree ( ) propertyident ( ) propertytable ( ) Alarm thresholds for analog measurements currentalarmtable ( ) Real-time view of items in alarm states as defined in the propertytable and discretepropertytable. discretepropertytable ( ) SNMP alarm definitions for discrete parameters alarmsident ( ) A historic log of transponder alarms and traps sent commonident ( ) commonadmingroup ( ) Logical name Firmware version Transponder reset SNMP trap community string psident ( ) psdevicetable Input voltage Output voltage Battery string voltage Inverter status Major alarm Tamper Remote self-test psstringtable ( ) Battery charging currents psbatterytable ( ) Individual battery voltages psoutputtable ( ) Output Current pstemperaturesensortable ( ) Battery temperature genident ( ) Generator monitoring transponderinterfacebusident ( ) Monitoring of externally connected devices e.g. multiple power supplies daisy-chained to a single XP-DSM Table 6-1, SCTE-HMS MIB Hierarchy B0-001, Rev. A 31

32 6.0 Data Management, continued 6.2 The Alpha MIB Measurements and settings for the power supply, generator, batteries, and XP-DSM are accessed using Simple Network Management Protocol (SNMP) through the Alpha Management Information Base (MIB). The Alpha MIB is defined through the SNMP MIB file ATI-TABLES-MGMT-MIB.mib, which can be obtained from the com>broadband>status Monitoring>DSM>XP-DSM Tech. Support page. Many MIB browsers such as MG-Soft ( 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 , and is organized into three branches: Alpha CIB Tables All of the power supply, generator, battery, and most of the XP-DSM data and settings are located in the CIB Tables. These tables are sorted into four categories: Analogs, Counters, Discretes, and Text. Analogs: voltages, currents, frequency, temperatures. Counters: XM2 self-test schedule, communications and configuration settings. Discretes: XM2 major alarms, single/dual IP, tamper polarity, SNMP communications, SNMP traps, Web server. Text: XP-DSM communications settings, IP addresses, DHCP server, XP-DSM firmware version, static/dynamic IP address, DSM Setup File. Alpha Management Advanced DSM settings are located in the Alpha Management branch and are split between SNMP and system-related settings. SNMP Management: SNMP trap tables, Dual IP security, SNMP access, and community strings. System Management: firmware download, Web server, SNTP Server location, enclosure environmental controller. Alpha Technologies IDs The Alpha Technologies IDs branch is used by internal DSM processes to identify the model of the transponder for firmware upgrades and other functions B0-001, Rev. A

33 6.0 Data Management, continued 6.2 The Alpha MIB, continued The Alpha MIB hierarchy (see Section 10.0 for a list and definitions of all Alpha MIB parameters). enterprises ( ) Alpha CIB Tables alphatechinc ( ) atitables ( ) aticibtables ( ) aticibdisctable ( ) (Discrete Table) XM2 Major Alarms Advanced Settings DSM Settings Contents Single/Dual IP (Block CPE) Tamper Polarity SNMP Communications Enable SNMP Trap on Normal Condition Web Server Enable aticibanatable ( ) (Analog Table) Alpha Management Alpha Technologies IDs Contents Voltages Currents Frequency Temperatures: power supply, batteries, generator aticibcounttable ( ) (Counters Table) Contents Power Supply Self-Test Communications Settings Configuration Settings aticibtexttable ( ) (Text Table) DSM Communications Settings Contents IP Addresses DHCP Server DSM Firmware Version Set Static IP address DSM Configuration File atimanagement ( ) atimgntsnmp ( ) SNMP Trap Tables Contents Dual IP Security SNMP Access Enable Community Strings atimgntsys ( ) Contents Firmware Download Web Server Enable SNTP Server Location alphatechincids ( ) Contents Internal DSM processes to identify the transponder model for firmware upgrades and other functions B0-001, Rev. A Table 6-2, Alpha MIB Hierarchy 33

34 6.0 Data Management, continued 6.3 SCTE-HMS MIB Alarms The HMS discrete and analog alarms provide the capability to monitor and alarm various power supply and environmental conditions and measurements. The alarms in the MIB tables can be defined and set to provide a custom monitoring system SCTE-HMS Configurable Alarms The SCTE-HMS MIB tables can be configured to send SNMP traps to a network management system in response to certain power supply conditions. The tables used to define these alarms are the propertytable and the discretepropertytable, which are both located in the propertyident MIB at OID 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 LOLO LO HI HIHI Definition alarm threshold for extreme low condition alarm threshold for low condition alarm threshold for high condition 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 binary, or 04 Hex. To set alarms for all threshold levels, enable Bits 0 through 3 by setting them to 1 represented by binary , 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 See Table B0-001, Rev. A

35 6.0 Data Management, continued 6.3 SCTE-HMS MIB Alarms, continued SCTE-HMS Configurable Alarms, continued Binary to Hex Conversions for Alarm Settings Unused HiHi Hi Lo LoLo Hex Enabled Alarms Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit No Alarms LoLo Lo Lo, LoLo Hi Hi, LoLo Hi, Lo Hi, Lo, LoLo HiHI HiHi, LoLo A HiHi, Lo B HiHi, Lo, LoLo C HiHi, Hi D HiHi, Hi, LoLo E HiHi, Hi, Lo F HiHi, Hi, Lo, LoLo Table 6-3, Binary to Hex Conversions for Alarm Settings Example: The alarms for pstemperature below are set so that the normal temperature range is from 30 C to 45 C. If the temperature rises above 45 C, a cashi alarm will be sent to the alarmtable. Anything over 50 C is considered a critical condition and will generate a cashihi alarm. If the temperature falls below the normal level of 30 degrees, and caslo will be generated, and if it continues to drop below 0, a caslolo will be generated. The temperature must rise above the LOLO limit plus the deadband value of 3 C before the caslolo alarm will change to a caslo. The alarmenable field is set to 0F Hex to monitor and alarm for all conditions. pstemerature B0-001, Rev. A 35

36 6.0 Data Management, continued 6.3 SCTE-HMS MIB Alarms, continued SCTE-HMS Configurable Alarms, continued Analog Alarms Analog Alarms and Common Settings Description Alarm Enable Table 6-4, Analog Alarms and Common Settings LOLO LO HI HIHI Deadband pstotalstringvoltage 36V Scaled representation of the full 0x0F V 48V battery string in 1/100 Volts units 0x0F V psbatteryvoltage Battery Voltage of 12V battery, scaled 1/100 V psinputvoltage 120V Scaled representation of the 220V input line voltage in 1/100 Volts units 0x0F V 0x0F 0x0F Varies by site. The XM2 will switch to standby at Nominal +15% -20% psoutputvoltage 48V Scaled representation of the 0x0F V 60V power supply output voltage in 1/100 Volts units. 0x0F V 90V 0x0F V pspowerout psstringchargecurrent psstringfloat psstringdischargecurrent The following table displays the various analog alarms with common settings. Representation of power supply output power in 1W Battery string charge current, scaled at 1/100 Amp Battery string float charge current, scaled at 1/100 Amp Battery string discharge current, scaled at 1/100 Amp 0x00 Monitor Output Current Instead 0x0C Disable Disable A 0x0C Disable Disable A 0x00 Not Supported by XM2/GMX psoutputcurrent 15A Scaled representation of power 0x0C Disable Disable A 22A supply RMS current in 1/100 Amp units 0x0C Disable Disable A pstemperature -40 to +80 degrees C 0x0F Varies by site B0-001, Rev. A

37 6.0 Data Management, continued 6.3 SCTE-HMS MIB Alarms, continued SCTE-HMS Configurable Alarms, continued discretepropertytable: Discrete Alarms This table holds the alarmable discrete objects that are passed from the power supply to the transponder. The SCTE-HMS-PS-MIB file defines all supported objects in this table, including the different states and dependencies of each object. An object must both be in this file and be supported by the power supply and transponder before it will show up in the discretepropertytable. Through this table, how an object is alarmed when it transitions to the different states is defined. Discrete alarms settings are programmable using three values: enable major, enable minor, and disable. The discrete alarms represent the value of the alarm as defined by the network, and are distinct from the power supply alarms. For example, the discrete alarm for a psmajoralarm (power supply major alarm, see Section 6.3.2) may be set as enable minor (network alarm setting). In this case, a power supply major alarm is reported to the network as a minor alarm. If an object transitions into a state set at enableminor or enablemajor, an alarm instance is created in the currentalarmtable. This alarm is labeled caasdiscreteminor or caasdiscretemajor. If an object is set to disable, no alarm is generated. To set system discrete alarms, select edit mode as defined by your MIB browser. Select the alarm in the discretealarmenable column and change the value to the desired setting. Example: In the example below, psinverterstatus is set to generate discreteminor alarms if it enters a state of 2 or 5, which are AC line loss and Test Fail respectively. If the inverter enters states 1, 3, or 4, no alarm is generated. See the table on the next page for alarm definitions. Values of 2 and 5 generate minor alarms. NOTE: discreteminor and discretemajor are completely different from psmajor and psminor, which are defined by the power supply (see Section 6.3.2). In the Discrete Table, psmajor or psminor can actually be disabled so that they would not generate an entry in the currentalarmtable B0-001, Rev. A 37

38 6.0 Data Management, continued 6.3 SCTE-HMS MIB Alarms, continued SCTE-HMS Configurable Alarms, continued Discrete Alarms Discrete Alarm Definitions and Common Settings Discrete Alarm Value Definition Example Settings psinverterstatus 1 Inverter is off Disable psinverterstatus 2 AC Input line loss EnableMinor psinverterstatus 3 Inverter is in a local test cycle Disable psinverterstatus 4 Remote inverter test has been initiated Disable psinverterstatus 5 The last Inverter test failed. EnableMinor psmajoralarm 1 No alarm Disable psmajoralarm 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 Disable psminoralarm 2 A non-service effecting condition has occurred and should be monitored pstamper 1 Indicates status of enclosure door tamper sensor: closed (door is open). pstamper 2 Indicates status of enclosure door tamper sensor: open (door is closed). psinputvoltagepresence 1 Digital value indicating that line voltage is lost, based on measurement of input voltage. psinputvoltagepresence 2 Indicates that line voltage is present and within tolerance, based on measurement of input voltage. transponderinterfacebusident 1 Remote device will respond to commands from master transponder. transponderinterfacebusident 2 Local device is under local control and will not respond to commands from master transponder. EnableMinor EnableMinor Disable EnableMinor Disable Disable EnableMinor transponderinterfacebusident 3 Device is not responding. EnableMajor Table 6-5, Discrete Alarm Definitions and Common Settings B0-001, Rev. A

39 6.0 Data Management, continued 6.3 SCTE-HMS MIB Alarms, continued Distributing Alarm Settings Alarm settings can be distributed automatically from one XP-DSM to another. They can also be distributed to all the XP-DSMs on a network by using a DSM Setup File. The procedure is a follows: STEP 1: Make the desired SCTE-HMS alarm settings on a master XP-DSM, according to the methods described in the sections above. STEP 2: Create an.s19 image file of the master XP-DSM s alarm settings. To create an.s19 image file of the master XP-DSM s alarm settings, you must first obtain its SCTE-HMS configuration. This can be done in two ways. Method A: Method B: If the Web server is enabled (default), enter the master XP-DSM s IP address followed by /?X=con (e.g. into a Web browser. Connect a local computer to the master XP-DSM using the local port adapter (Alpha P/N ). 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 S B8 at the beginning of the file. c. Add the line S FB 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 B0-001, Rev. A 39

40 6.0 Data Management, continued 6.3 SCTE-HMS MIB Alarms, continued Distributing Alarm Settings, continued The.s19 file should now look like the following: Save the file as HMScfg.s19 and move it to a TFTP server on the network that is accessible by the XP-DSMs that you want to update. STEP 3: Distribute the.s19 file to other XP-DSMs. The.s19 file is distributed to other XP-DSMs by setting the following Alpha MIB parameters to the indicated values. This can be done to an individual XP-DSM using the local port (see Section 4.0) or a MIB browser, or to multiple XP-DSMs by using a DSM Setup File (see Section 3.4): XP-DSM Alarm Settings Distribution Parameters Parameter Local Port Parameter Type Value atimgntsysdownload OID: atimgmtsysdownloadtftpaddress OID: atimgmtsysdownloadctrl OID: atimgmtsysdownloadfile Parameter atimgmtsysdownloadprogress OID: atimgmtsysdownloadstatus OID: [Text] DOWN IP [Discrete] GET NEW IMAGE [Text] DOWN NAME 1 Local Port Parameter IP address Integer Octet String Type The IP address of the modem s TFTP server on which HMScfg.s19 is stored. 1 = Initiate download of.s19 file. Set to HMScfg.s19. The status of the alarm settings download can be monitored with the following parameters: [Text] DOWN STAT Integer Read Only Integer Value Byte count of file download process. 1 = Idle 5 = Transferring 6 = Testing 8 = Error Verify the XP-DSMs property tables have been updated using an SNMP manager B0-001, Rev. A

41 6.0 Data Management, continued 6.3 SCTE-HMS MIB Alarms, continued 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 Example Alarm Trap The example below is a pstamper alarm trap indicating a discreteminor alarm: tamper is open. The first example is a trap with varbinds and values as translated through a MG-Soft MIB browser. The second example is a raw trap. See the table of varbind definitions on the next page. Example Trap Translated by MG-Soft Bindings (5) Binding #1: commonphysaddress.0 *** (octets) EA.A0.01.4E (hex) Binding #2: commonlogicalid.0 *** (octets) (123 Example Ave.) Binding #3: alarmloginformation.1 *** (octets) D.2B AB B (hex) Binding #4: pstamper.1 *** (int32) open (2) Binding #5: currentalarmalarmstate *** (int32) caasdiscreteminor(7) Example Raw Trap Frame 441 (230 bytes ib wire, 230 bytes captured) Ethernet II, Src: (00:05:ca:29:b4:89), Dst: 3com_0d:1d:d4 (00:10:5a:0dL1d:d4) Internet Protocol, Src Port: (62481), Dst Port: snmptrap (162) Simple Network Management Protocol Version: 1 (0) Community: PUBLIC PDU type: TRAP-V1 (4) Enterprise: (SNMPv2-SMI::enterprises ) Agent address: ( ) Trap type: ENTERPRISE SPECIFIC (6) Specific trap type: 1 Timestamp: Object identifier 1: (SNMPv2-SMI::enterprises ) Value: Hex-STRING: EA A0 0B 82 Object identifier 2: (SNMPv2-SMI::enterprises ) Value STRING: 123 Example Ave. Object identifier 3: (SNMPv2-SMI::enterprises ) Value: Hex-STRING: D 2B AB B Object identifier 4: (SNMPv2-SMI::enterprises ) Value: INTEGER: 2 Object identifier 5: (SNMPv2-SMI::enterprises ) Value: INTEGER: 7 Fig. 6-1, Example SNMP Alarm Trap B0-001, Rev. A 41

42 6.0 Data Management, continued 6.3 SCTE-HMS MIB Alarms, continued Varbind Binding #1 commonphysaddress OID: Binding #2 commonlogicalid OID: Binding #3 alarmloginformation OID: Binding #4 Alarmed Parameter OID/Value OID: Binding #5 Alarm Location/Type OID: SNMP Alarm Traps, continued MAC Address of the transponder Trap on Normal The XP-DSM has the capability of sending a return to normal trap once an alarmed condition returns to a normal state. This feature is disabled by default, but can be enabled by setting the TRAP ON NORMAL parameter in the aticibdiscretetable to a value of 1. The contents of this trap message will be identical to the SNMP Alarm traps, but the value of the Alarm Type defined in the 5th varbind will be 1 (NOMINAL). Warm Start Trap In addition to the SNMP alarm traps, the XP-DSM will also send a warm-start trap when it is initialized. Some SNMP monitoring software requires this trap for autoidentification of the transponder. The format of this trap will be similar to the alarm trap, but the only information sent will be: commontrapcommunitystring, OID commonphyaddress, OID, commonlogicalid, OID Cold Start Trap Explanation 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. 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. 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: (pstamper) Value: 2 (Open) This is the information from varbind #3 Octet 5 above. The alarm location will always be the SCTE-HMS currentalarmalarmstate, and the type will be determined based on how the alarm was configured in the SCTE-HMS PropertyIdent MIB tables. OID (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 A cold-start trap will be generated by the XP-DSM anytime it initializes with a new firmware version. This trap should only appear after the first time the XP-DSM has been reset during a firmware upgrade B0-001, Rev. A

43 6.0 Data Management, continued 6.3 SCTE-HMS MIB Alarms, continued General Power Supply Alarms General power supply alarms are passed directly from the power supply to the transponder without specific definition and are classified in the HMS MIB table as psminoralarm and psmajoralarm. There are a number of problems that can generate these alarms, and the exact nature of the situation is not specified. Minor and Major alarms are defined by the SCTE standards committee as follows: psmajor Service has been dropped or a service interruption is imminent. Indicates that an immediate truck roll is appropriate. Several psmajor alarms are latching, meaning that the alarm won t clear until the problem is fixed and after either a successful completion of a self-test or a complete power cycle of the power supply. NOTE: The cause of a psmajor alarm can be determined by checking the Discretes table in the Alpha MIB. The cause will have the value of ALARM. psminor A non-service effecting condition has occurred and should be monitored. The following table lists the psmajor and psminor alarm definitions for the XM2 power supply. psminor XM2 Major and Minor Alarms Problem Line Loss from Inverter Status Battery Temperature Probe Definition Loss of AC line as determined by power supply inverter. 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 Output Failure (non-latching) General Failure (latching) Test Fail (latching) Battery Fail (non-latching) Line Isolation (latching) Output Overload (non-latching) Charger Failure (non-latching) Inverter Fail (latching) Configuration Failure Overtemp Definition AC output failure, open or short detected by power supply. Indicates a latched failure of an automated, local or remote inverter test, or some other major malfunction within the power supply. Battery voltage drops below 1.85V/cell or inverter fail during self test. Battery voltage drops below 1.75V/cell while in standby mode; battery exceeds 2.5V/cell; Batteries not detected. Line isolation circuitry has failed. Indicates XM2 is overloaded. Power supply will shut down and restart periodically. Charger has failed or was shut down due to problem such as battery over-temp. XM2 has detected a failure in inverter operation. XM2 has detected that it is improperly configured. 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 B0-001, Rev. A 43

44 7.0 Hardware Installation Before installing the hardware, provision the DHCP server with the cable modem s RF MAC Address (see Section 3.1). If operating in Dual IP Mode, provision it with the CPE MAC Address as well. This allows the installation to be verified while the technician is on-site, eliminating the need for a second visit if there are problems with the installation. WARNING! To reduce the risk of electric shock, completely remove the inverter module from the power supply prior to installation. For field installation, use a service power supply to avoid losing power to the load. CAUTION! The XP-DSM is static sensitive. An ESD wrist strap should be worn when installing the transponder. 7.1 Verifying Power Supply Device Address Before removing the Inverter Module (IM), verify the power supply device address is correct. The power supply device address must not be set to zero, and no two power supplies monitored by a single XP-DSM can have the same address. Power supplies must have 1, 2, or 3 as an address. To verify the power supply s address do the following: 1. Press the Enter key on the inverter module twice to access the SETUP Menu. 2. Press the Down key until DEVICE ADDRESS is displayed. 3. If the address is correct (in the range of 1 to 3), skip to Step To change the address, press the Enter key to enter the Edit mode. Verify Device Address 5. Press the Up or Down keys until the desired address (1, 2, or 3) is displayed. Remember, each power supply monitored by a single transponder must have a unique address. 6. Press the Enter key to load the new address. 7. Press the Enter key again to accept the new data. 8. Press ESC three times to return to the OPERATION NORMAL screen B0-001, Rev. A

45 7.0 Hardware Installation, continued 7.2 Hardware Installation Procedure NOTE: With the battery breaker in the OFF position, the power supply will not go into inverter mode. 1. Switch OFF the power supply s battery breaker. 2. Unplug all inverter module connections (e.g. battery cable, remote temperature sensor). 3. Loosen the inverter module thumbscrews and slide the inverter module out just enough to disconnect the ribbon cable. Disconnect the ribbon cable. 4. Slide the inverter module out of the power supply. 5. If the inverter module is equipped with a communication module, remove it by loosening the two Phillips captive screws. Disconnect Captive Screws Fig. 7-1, Removing the Inverter Module from the Power Supply B0-001, Rev. A 45

46 7.0 Hardware Installation, continued 7.2 Hardware Installation Procedure, continued 6. Locate the 18-pin jumper and insert the long side of the jumper firmly into the side of the inverter module. Inverter Module Fig. 7-2, The 18-pin Jumper Insert Long Side Into 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). 8. Line up the 18-pin jumper with the XP-DSM connector and connect the unit to the inverter module. Fig. 7-3, Connecting the Transponder to the Inverter Module 9. Secure the XP-DSM to the inverter module by tightening the two captive screws. 10. Reinstall the inverter module and reconnect the ribbon cable. Make front panel connections (tamper, RTS, battery sense, etc.) B0-001, Rev. A

47 O O 7.0 Hardware Installation, continued 7.3 XP-DSM Connections Front Panel Diagram XP-DSM Front Panel Reset Button CPE MAC Address Status LEDs Cable Modem Status LEDs RF Connection Tamper Switch Connection AlphaBus Communication Port Battery String Connection (A/B) Local Port Connection RF MAC Address CAUTION! Fig. 7-4, Front Panel Connecting the RF Drop Install a grounded surge suppressor (Alpha P/N or equivalent). Connect the RF drop according to the diagram below. The RF drop must have a properly installed ground block in the power supply enclosure. Recommended downstream RF level is 0 dbmv. Connect any other front panel connections at this time (e.g. battery strings, tamper switch). STAT ALM RDY COM LNK XP-DSM RF DS REG DC TMPR Battery Breaker Battery nput Temp Probe Grounded Surge Protector (See Caution Above) RF Cable to Headend Fig. 7-5, Connecting the RF Drop B0-001, Rev. A 47

48 7.0 Hardware Installation, continued 7.3 XP-DSM Connections, continued Front Panel Connections XP-DSM Front Panel Connections ECM to SCM Interface (Alpha P/N ) XM2 XM2 Master XM2 System Port STAT Communications Port S Y S C O M System Port Communications Port S Y S C O M ALM RDY COM LNK RF REG DS TMPR Generator (ECM) Communications Port Battery String Connector C O M LOCAL To Battery Sense Wire Harness Connections Connections with more than one power supply Fig. 7-6, System Interconnection Diagram B0-001, Rev. A

49 8.0 Battery Sense Wire Kit Connections V Single and Dual Strings To Power Supply Red Black Fig. 8-1, 36V System, Single String Alpha P/N: (6') Alpha P/N: (9') NEG 3A NEG 2A NEG 1A POS POS POS A/B [C/D] NEG Pin 1 Vbatt 3A [C] 36V Pin 4 Vbatt 2A [C] 24V Pin 3 Vbatt 1A [C] 12V Pin Back of Plug To Power Supply Red Black Fig. 8-2, 36V System, Dual String Alpha P/N: (6') Alpha P/N: (9') NEG NEG NEG 3A 2A 1A POS POS POS A/B [C/D] NEG Pin 1 Vbatt 3A [C] 36V Pin 4 Vbatt 2A [C] 24V Pin 3 Vbatt 1A [C] 12V Pin Back of Plug Vbatt 3B [D] 36V Pin 7 Vbatt 2B [D] 24V Pin 6 Vbatt 1B [D] 12V Pin 5 NEG NEG NEG 3B 2B 1B POS POS POS B0-001, Rev. A 49

50 8.0 Battery Sense Wire Kit Connections, continued V Single and Dual Strings To Power Supply Red Black Fig. 8-3, 48V System, Single String Alpha P/N: (6') Alpha P/N: (9') NEG NEG NEG NEG 4A 3A 2A 1A POS POS POS POS A/B [C/D] NEG Pin 1 Vbatt 4A [C/D] 48V Pin 8 Vbatt 3A [C] 36V Pin 4 Vbatt 2A [C] 24V Pin 3 Vbatt 1A [C] 12V Pin Back of Plug To Power Supply Red Black Fig.8-4, 48V System, Dual String Alpha P/N: (6') Alpha P/N: (9') NEG 4A NEG 3A NEG 2A NEG 1A POS POS POS POS A/B [C/D] NEG Pin 1 Vbatt 3A [C] 36V Pin 4 Vbatt 2A [C] 24V Pin 3 Vbatt 1A [C] 12V Pin Back of Plug Vbatt A/B [C/D] 48V Pin 8 NEG Vbatt 3B [D] 36V Pin 7 NEG Vbatt 2B [D] 24V Pin 6 NEG Vbatt 1B [D] 12V Pin 5 NEG 4B 3B 2B 1B POS POS POS POS B0-001, Rev. A

51 9.0 Start-up and Verification 9.1 Initial Startup 1. Plug the power supply into the AC outlet and turn on the battery breaker. 2. The XP-DSM LEDs blink three times and the RDY light begins blinking on and off. 3. Verify no alarms are active. 4. Verify the DS and REG LEDs are on solid (this verifies successful network registration). 5. Verify LNK LED is blinking if in Single IP Mode and on solid if in Dual IP Mode. NOTE: A solid registration LED indicates registration with the CMTS. Use this indicator to confirm the communication with the headend. It might take several minutes for communication to be established. 9.2 LEDs and System Status The XP-DSM has six LEDs that indicate system status. During system startup, the LEDs blink momentarily. The Status LEDs indicate alarms, status of the XP-DSM, and communications and activity with the network. A description of each LED follows. ALM HMS Major and Minor Alarm The ALM LED is the only red LED. It provides a visual alert for power supply discrete major and minor alarms, as defined in the discrete property tables of the SCTE HMS MIB. Refer to Section 6.3 for information on configuring the XP-DSM for active monitoring and alarming. If an event triggers an HMS alarm, the ALM LED blinks according to the alarm type until the alarm has been resolved. If there are multiple active alarms, including one or more major alarms with one or more minor alarms, the major alarm will take precedent in terms of the LED indication. RDY Micro-controller Status and Write to Non-volatile Memory During normal operation, the RDY LED blinks steadily, indicating a heartbeat pulse from the processor. COM Alpha Bus, or Local port Receive The COM LED indicates any RS-232 and RS-485 traffic being received by the XP-DSM through the Com port or Local port. When using the Local port, the light blinks for every character typed, as the transistor-to-transistor logic (TTL) accepts each character. This LED will also blink with one to three blinks approximately every 10 seconds, which indicates communication exists between the XP-DSM card and other connected devices, such as a generator or additional XM2. LNK Network Communication Status For single IP applications the LNK LED blinks. For dual IP applications, the LNK LED is on solid, and indicates network health B0-001, Rev. A 51

52 9.0 Start-up and Verification, continued 9.2 LEDs and System Status, continued DS Downstream Communication This LED indicates the state of the CM s attempt to gain a downstream signal. The process may take several seconds, depending on how long it takes the CM to locate carrier signal and lock into a channel. The LED is on solid when the downstream channel is locked. REG CM Registration Once a downstream channel is negotiated between the CM and CMTS, the modem attempts to register with the DHCP server and obtain the configuration file. This LED flashes while the process takes place. Once the registration is complete, the LED will remain on. This is the best indication that the XP-DSM is connected to the headend. Alarm Ready Communication Link Registration Downstream LED Behavior Indication ALM RDY COM LNK REG DS OFF Blinking ON more than OFF Blinking OFF more than ON Steady Blinking Quick Burst Steady ON OFF Blinking Not used with default application. No alarms reported Major Alarm present Minor Alarm present Normal Operation Write to non-volitile memory Processor hung. Reset or replace. Processor not operating. Replace card Receiving Data via the Alpha Bus or Com Port Blinking Attempting to register ON Model H Model A ON OFF Blinking Registration verified Aquiring downstream signal Downstream communication established Fig. 9-1, LED Indications B0-001, Rev. A