How it Works
EnerSys
Loading...
Alpha AlphaNet DOCSIS DM3EX
Technical Manual
100 pgs5.56 Mb0
Table of contents
Loading...

EnerSys Alpha AlphaNet DOCSIS DM3X Series, Alpha AlphaNet DOCSIS DM3EX Technical Manual

AlphaNetTM DM3X Series DOCSIS® Status Monitor for XM2
Technical Manual
E󰀨ective: June 2019
Safety Notes
WARNING! GENERAL HAZARD
GENERAL HAZARD WARNING provides safety information to PREVENT INJURY OR DEATH to the techni­cian or user.
WARNING! ELECTRICAL HAZARD
ELECTRICAL HAZARD WARNING provides electrical safety information to PREVENT INJURY OR DEATH to the technician or user.
WARNING! FUMES HAZARD
FUMES HAZARD WARNING provides fumes safety information to PREVENT INJURY OR DEATH to the techni­cian or user.
WARNING! FIRE HAZARD
FIRE HAZARD WARNING provides ammability safety information to PREVENT INJURY OR DEATH to the techni­cian or user.
There may be multiple warnings associated with the call out. Example:
WARNING! ELECTRICAL & FIRE HAZARD
This WARNING provides safety information for both Electrical AND Fire Hazards
CAUTION!
CAUTION provides safety information intended to PREVENT DAMAGE to material or equipment.
NOTICE:
NOTICE provides additional information to help complete a specic task or procedure.
ATTENTION:
ATTENTION provides specic regulatory/code requirements that may a󰀨ect the placement of equipment and /or installation procedures.
The following sections contain important safety information that must be followed during the installation and maintenance of the equipment and batteries. Read all of the instructions before installing or operating the equipment, and save this manual for future reference.
AlphaNetTM DM3X Series DOCSIS
®
Status Monitor for XM2
Technical Manual 704-939-B10-001 Rev. A5
E󰀨ective Date: June 2019
©
2019 by Alpha Technologies Services, Inc.
Disclaimer
Images contained in this manual are for illustrative purposes only. These images may not match your installation.
Operator is cautioned to review the drawings and illustrations contained in this manual before proceeding. If there are questions regarding the safe operation of this powering system, please contact Alpha Technologies Services, Inc. or your nearest Alpha representative.
Alpha shall not be held liable for any damage or injury involving its enclosures, power supplies, generators, batteries or other hardware if used or operated in any manner or subject to any condition not consistent with its intended purpose or is installed or operated in an unapproved manner or improperly maintained.
Contact Information
Sales information and customer service in USA (7AM to 5PM, Pacic Time):
Complete technical support in USA (7AM to 5PM, Pacic Time or 24/7 emergency support):
Sales information and technical support in Canada:
Website:
1 800 322 5742
1 800 863 3364
1 888 462 7487
www.alpha.com
Table of Contents
1.0 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.0 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1 System Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Network Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 System Conguration and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4 DM3.0 Series Start Up and Reboot Routline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.0 Network Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1 Provisioning the DHCP Server with the MAC Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
3.2 Establishing IP Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3 The DOCSIS Conguration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3.1 Setting Modem Community Strings - docsDevNmAccess Method (IPv4 Only) . . . . . . . . . 15
3.3.2 Setting Modem Community Strings - Coexistence Method . . . . . . . . . . . . . . . . . . . 16
3.3.3 Setting SNMP Trap Destination Addresses - docsDevNmAccess Method. . . . . . . . . . . . 17
3.3.4 Setting SNMP Trap Destination Addresses - Coexistence Method . . . . . . . . . . . . . . . 18
3.3.5 Sample DOCSIS Conguration File Entries - devDocNmAccess . . . . . . . . . . . . . . . . 19
3.3.6 Sample DOCSIS Conguration File Entries - Coexistence . . . . . . . . . . . . . . . . . . . 20
3.3.7 Proprietary Conguration File ‘atidoc33.cfg’ . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.3.8 Changing Default atidoc33.cfg Download Settings. . . . . . . . . . . . . . . . . . . . . . . . 22
3.4 Setting Communication Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.0 Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.1 Local Web Server Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2 Remote Web Server Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.3 Navigating the Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.3.1 Web Interface Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.4 Verifying Communication Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.5 Verifying Power Supply and Battery Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.6 Remote Self-Tests via the Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.7 Viewing HMS Alarm Status via the Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.8 Setting the I/O Controller via the Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.9 Viewing and Conguring Power Supply Settings via the Web Page . . . . . . . . . . . . . . . . . . 34
4.10 Viewing and Conguring Generator Settings Via the Web Page . . . . . . . . . . . . . . . . . . . 37
4.11 Tools Menu - Constellation and Microreections . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.11.1 QAM Constellation Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.11.2 QAM Constellation Common Impairments . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.11.3 Microreections Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.12 Viewing the Modem Event Log via the Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.0 Upgrading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.1 Upgrading DM3X Modem Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.1.1 Identifying the Modem and Obtaining Firmware Files . . . . . . . . . . . . . . . . . . . . . . 48
5.1.2 Modem Firmware Upgrade SNMP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.1.3 Upgrading Manually by Setting SNMP Parameters . . . . . . . . . . . . . . . . . . . . . . . 49
5.1.4 Upgrading via the DOCSIS Conguration File . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.0 Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.1 SCTE-HMS MIBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6.2 SCTE-HMS MIB Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.2.1 SCTE-HMS Congurable Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.2.2 SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.2.3 General Power Supply Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.2.4 Battery Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4 704-939-B10-001 Rev. A5 (06/2019)
Table of Contents
7.0 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.1 Verifying Power Supply Device Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.2 Installation / Replacement Procedure in XM2 Power Supplies . . . . . . . . . . . . . . . . . . . . 66
7.3 DM3X LEDs and Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
7.4 Connecting the RF Drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.5 Front Panel Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
7.6 I/O Connections (TPR, ENV). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.6.1 Tamper (TPR) Switch Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
7.6.2 I/O Port Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
7.6.3 Conguring I/O Port Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
7.6.4 I/O Port: Generic Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
7.6.5 Connecting a Generic I/O Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
7.6.6 Conguring and Monitoring a Generic I/O Device . . . . . . . . . . . . . . . . . . . . . . . . 74
7.6.7 I/O Port: Heater Mat Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
7.6.8 Connecting the Battery Heater Mat Controller . . . . . . . . . . . . . . . . . . . . . . . . . . 76
7.6.9 Conguring the Battery Heater Mat Controller . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7.6.10 I/O Port: Emergency DC Generator (GEN) . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7.6.11 Conguring and Monitoring the DC Emergency Generator . . . . . . . . . . . . . . . . . . . 78
8.0 Battery Sense Wire Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
8.1 36V Single and Dual Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
9.0 Start Up and Verication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
9.1 Initial Start Up and Local Verication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
9.2 Verifying Correct Hardware Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
9.3 System Status Indicators and Reset Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
9.3.1 Detailed LED Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
9.3.2 Resetting the Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
9.4 Verifying Communications via the Headend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
9.5 Dual IP Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
9.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
9.5.2 Web Comparison, Single IP Mode/Dual IP Mode . . . . . . . . . . . . . . . . . . . . . . . . 90
9.5.3 Conguring Dual IP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
9.5.4 Dual IP SNMP Community Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
9.5.5 Security in Dual IP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
10.0 Specications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
11.0 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
11.1 Acronym Denitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5704-939-B10-001 Rev. A5 (06/2019)
Figures
Fig. 1-1, AlphaNet DM3X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Fig. 1-2, DM3X Transponder Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Fig. 2-1, Representative System Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Fig. 2-2, DM3X Transponder Start Up and Reboot Routline. . . . . . . . . . . . . . . . . . . . . . . . . . 12
Fig. 3-1, Locations of MAC Address Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Fig. 4-1, DM3X Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Fig. 4-2, Local Area Connection Properties Screen, Windows® 7 . . . . . . . . . . . . . . . . . . . . . . . 25
Fig. 4-6, Web Server Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Fig. 4-7, Navigation Bar Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Fig. 4-8, Communication Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Fig. 4-9, Advanced Communication Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Fig. 4-10, Power Supply and Battery Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Fig. 4-11, HMS Alarm Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Fig. 4-12, Advanced I/O Controller Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Fig. 4-13, Advanced Power Supply Settings Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Fig. 4-14, Advanced Generator Status Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Fig. 4-15, QAM Constellation Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Fig. 4-16, Normal - (Good Quality) and Individual Cell Characteristics . . . . . . . . . . . . . . . . . . . . 39
Fig. 4-17, Fuzzy (Low CNR and/or Low MER) and Individual Cell Characteristics . . . . . . . . . . . . . . 40
Fig. 4-18, Doughnuts (Coherent Interference) and Individual Cell Characteristics . . . . . . . . . . . . . . 40
Fig. 4-19, Gaussian Noise and Individual Cell Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . 41
Fig. 4-20, Rectangular vs. Square (I-Q Imbalance) and Entire Constellation Shape . . . . . . . . . . . . . 41
Fig. 4-21, Corners Squeezed to Center (Gain Compression) and Entire Constellation Shape . . . . . . . . 42
Fig. 4-22, Circular Smear (Phase Noise) and Entire Constellation Shape. . . . . . . . . . . . . . . . . . . 42
Fig. 4-23, Twisted or Skewed (Quadrature Distortion) and Entire Constellation Shape . . . . . . . . . . . . 43
Fig. 4-24, Microreections Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Fig. 4-25, Spectrum Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Fig. 4-26, Spectrum Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Fig. 4-27, Docsdev Event Log Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Fig. 7-1, Captive Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Fig. 7-2, Jumper Location and the 18-Pin Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Fig. 7-3, Connecting the Transponder to the Inverter Module . . . . . . . . . . . . . . . . . . . . . . . . . 67
Fig. 7-4, DM3X LEDs and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Fig. 7-5, Connecting the RF Drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Fig. 7-6, System Interconnection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Fig. 7-7, I/O (ENV) and Tamper Switch Interface (TPR) Connection Locations . . . . . . . . . . . . . . . . 71
Fig. 8-1, 36V System, Single String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Fig. 8-2, 36V System, Dual String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Fig. 8-3, 48V System, Single String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Fig. 8-4, 48V System, Dual String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Fig. 9-1, XM2 Smart Display Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Fig. 9-2, Communications Section - General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Fig. 9-3, Power Supply Section - General Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Fig. 9-4, LED Functionality and Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Fig. 9-5, Transponder Web Page, RF Power Level Indicators . . . . . . . . . . . . . . . . . . . . . . . . . 87
Fig. 9-6, Simplied Block Diagram Single IP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Fig. 9-7, Simplied Block Diagram Dual IP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Fig. 9-8, Single IP DM3X Transponder Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Fig. 9-9, Dual IP DM3X Transponder Web Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Fig. 9-10, Dual IP Conguration Settings for Web Server Communications Page. . . . . . . . . . . . . . . 92
Fig. 9-11, Dual IP Parameters for Web Server General Page . . . . . . . . . . . . . . . . . . . . . . . . . 92
6 704-939-B10-001 Rev. A5 (06/2019)
Tables
Table 1-1, DM3X Transponder Model Specications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Table 2-1, LEDs and Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 3-1, Modem Community String Parameters - docsDevNmAccess Method . . . . . . . . . . . . . . . 15
Table 3-2, Modem Community String Parameters - Coexistence Method . . . . . . . . . . . . . . . . . . . 16
Table 3-3, Trap Destination Addresses - docsDevNmAccess Method . . . . . . . . . . . . . . . . . . . . . 17
Table 3-4, Trap Destination Addresses - Coexistence Method. . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 3-5, Default atidoc33.cfg Download Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 3-6, Communications Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 4-1, DM3X Web Page Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 4-2, DM3X Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Table 4-3, Spectrum Tool Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 4-4, Spectrum Table Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Table 5-1, Modem Firmware Upgrade SNMP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 5-2, SNMP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 5-3, DOCSIS Congurations File Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 6-1, SCTE-HMS MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 6-2, Binary to Hex Conversions for Alarm Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Table 6-3, Recommended Settings for DM3X Analog Alarms . . . . . . . . . . . . . . . . . . . . . . . . . 53
Table 6-4, Recommended Settings for Discrete Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 6-5, DM3X Alarm Setting Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 6-6, Status of Alarm Setting Download Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 6-7, SNMP Alarm Trap Varbinds and Explanations . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Table 6-8, Power Alarms: Classications, Causes and Corrections . . . . . . . . . . . . . . . . . . . . . . 61
Table 6-8, Power Alarms: Classications, Causes and Corrections, Continued . . . . . . . . . . . . . . . . 62
Table 6-8, Power Alarms: Classications, Causes and Corrections, Continued . . . . . . . . . . . . . . . . 63
Table 6-9, Battery Alarms: Classications, Causes and Corrections. . . . . . . . . . . . . . . . . . . . . . 64
Table 7-1, Tamper (TPR) Switch Specications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Table 7-2, ENV Connector and Pin Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Table 7-3, I/O Port Specications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 7-4, I/O Port: Generic Device Specciations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Table 7-5, I/O Port: Heater Mat Control Specications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Table 7-6, Heater Mat OIDs and Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Table 7-7, Heater Mat MIB Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Table 7-8, Generator Monitoring Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Table 9-1, SCTE-HMS Property Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Table 9-2, Rx/Tx Power LED Color Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Table 9-3, Single IP Mode vs. Dual IP Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Table 9-4, Enabling Dual IP Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 9-5, CPE Communications Module IP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table 9-6, Available Download Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Table 9-7, Community Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 9-8, Data Access Key Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Table 9-9, Secure Access Table Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
7704-939-B10-001 Rev. A5 (06/2019)

1.0 Introduction

The AlphaNet DM3X Embedded DOCSIS and EuroDOCSIS Transponders allow monitoring of Alpha power supplies through existing cable network infrastructure. Advanced networking services provide quick reporting and access to critical powering information. This manual focuses on the DM3X Transponder complementing the XM2 CableUPS.
The DM3X Transponder utilizes Simple Network Management Protocol (SNMP) and Management Information Bases (MIBs) to provide network status monitoring and diagnostics. A Web interface enables authorized personnel direct access to advanced diagnostics using a common Web browser. No custom software is required. See Table 1-1 for model specications.
DM3X Transponder Model Specications
Features & Information DM3X DM3EX
Part Number 704-939-20 704-939-22
1 & 2 Battery Strings Yes Yes
3 & 4 Battery Strings Yes Yes
DOCSIS 3.0 Standard U.S. EURO
Gb-Ethernet, CPE and local access Yes Yes
Tamper Switch Interface Ye s Ye s
ENV I/O Monitoring and Control Yes Yes
COM Port (AlphaBus) (PSx5 & AlphaGen)
Battery Monitoring
Quality of Service (QoS) Yes Ye s
24V / 36V x 4 STR / 6 x 6V 24V / 36V x 4 STR / 6 x 6V
Yes Yes
Table 1-1, DM3X Transponder Model Specications

Fig. 1-1, AlphaNet DM3X

8 704-939-B10-001 Rev. A5 (06/2019)
1.0 Introduction, continued
Primary Features
• DOCSIS 3.0 “Full Band Capture” Hardware
• 10/100/1000 Mbps auto-negotiating standard Ethernet interface
• Local Ethernet port provides technician on-site access to extensive power supply diagnostics*
• Embedded Web server for direct diagnostics
• Supports SNMPv1, v2c, v3
• Extensive power supply diagnostic MIBs
• Environmentally hardened DOCSIS cable modem and transponder
• Angled RF connector reduces cable bend radius
• Diagnostic LED indicators for RF communications, Battery connections and Ethernet status
• North American DOCSIS or EuroDOCSIS available
*Ethernet port also permits the connecting of external CPE devices.
Captive Screw
Tamper Connector
Environmental IO Connector
Battery Monitoring Connections DM3(E)X only
Ethernet Port for Local Diagnostics or External CPE Device
RF Connector
COM Port DM3(E)X

Fig. 1-2, DM3X Transponder Components

Captive Screw
9704-939-B10-001 Rev. A5 (06/2019)

2.0 Overview

2.1 System Diagram

DM3X Transponder
2
1
Power Supply
5 6
Coax/HFC Network CMTS
10
SNMP-based Network Management System
12
TCP/IP Network
External Generator
3
Local Computer
4
DHCP Server
7 8 9
TFTP Server TOD Server
Web Browser
11

Fig. 2-1, Representative System Arrangement

• All power supply data is stored in the power supply Inverter Module’s class information base (CIB) tables in
1
the power supply. This data is accessible directly via the power supply’s LCD Display (see the power supply’s technical manual for details). The CIB tables are the source of the transponder’s data.
2
• The DM3X Transponder contains both SCTE-HMS Management Information Base (MIBs) and the proprietary 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.0, Data Management). The Alpha MIB contains all the data of the SCTE-HMS MIBs plus additional power supply settings and values as well as the transponder’s conguration values.
3
• A xed or stationary external generator or additional power supplies may be connected through the COM (AlphaBus) port permitting monitoring locally through the Ethernet connector or remotely via the Web page or SNMP-based Network Management System.
4
• Power supply and transponder parameters can be monitored and set locally using a personal computer and a standard Ethernet cable.
5
• The transponder transmits data via its cable modem directly over the Coax or Hybrid Fiber Coax network.
6
• The Cable Modem Termination System (CMTS) is the bridge between the cable network and the TCP/IP network. The transponder’s cable modem communicates over the HFC network to the CMTS.
7
• The Dynamic Host Control Protocol (DHCP) server needs to be provisioned with the transponder’s cable modem CM MAC address and the MAC address needs to be assigned a DOCSIS Conguration File.
8
• The DOCSIS Conguration File and rmware les should be available in the Root Directory of the Trivial File Transfer Protocol (TFTP) Server.
9
• The Time of Day (TOD) Server provides the cable modem with the current date and time.
10
• A Network Management System (NMS) or MIB Browser allows remote monitoring, control, and conguration of the transponder, power supply, and connected device parameters. Alarms and traps can be set and monitored.
11
• The power supply and generator data may be accessed remotely through the transponder’s Web page by placing its IP address into a standard Web browser.
12
• The following ports of the Transmission Control Protocol/Internet Protocol network must be opened: 161=SNMP, 162=SNMP, Traps, 69=TFTP, 80=HTTP, 37=TOD.
10 704-939-B10-001 Rev. A5 (06/2019)
2.0 Overview, continued

2.2 Network Connectivity

The transponder’s cable modem must be provisioned to be recognized by the CMTS as a valid device to be assigned an IP address from the DHCP server, to locate the TFTP and TOD servers and to communicate with the SNMP management server (trap receiver). The DM3X Transponder must be provisioned in the cable system to allow it to be recognized by the CMTS, receive an IP address, TOD, TFTP les and communicate with the SNMP management system.
In single IP congured devices, data from both the cable modem and power supply are accessed and managed through the modem’s IP address on the secure private modem network. The transponder is not accessible from the public Customer Premises Equipment (CPE) network. Consequently, the Network Management System (NMS) that monitors the power supplies must have access to the same private modem network.
CMTS and system vendors use di󰀨erent security methods to ensure network integrity, but common considerations are:
• Network MAC ltering may have to be modied to allow the cable modem OUI of 00:90:EA for North America, and 00:03:08 for European models.
• For SNMP access, UDP ports 161 and 162 must not be blocked.
• For TFTP access, port 69 must not be blocked.
• For HTTP access, port 80 must not be blocked.
• For TOD access, port 37 must not be blocked.
• Firewalls must allow TFTP, DHCP, SNMP and TOD communication to the cable modem.
• If the address of the TFTP or TOD server is di󰀨erent than the DHCP server, the response from the DHCP server must contain the TFTP and TOD addresses.
2.3 System Conguration and Installation
NOTICE:
Before installation, read all of Section 2.0, Overview.
DM3X Transponder installation and setup is comprised of three basic steps:
1. Configuring the Network: Provisioning the DHCP Server with the transponder’s MAC address and assigning it a DOCSIS Configuration File.
2. Setting Options: The DM3X Transponder is designed for out-of-the-box, “plug and play” operation, but non-default settings such as SNMP trap destination addresses may be required for the Network Management System (NMS). SNMP trap addresses can be set automatically via the DOCSIS Conguration File per RFC 4639 (IPv4), or through SNMPv3 Notication settings (IPv6), while proprietary options may be set through type-11 TLV entries.
3. Field Installation of the DM3X Transponder into the power supply, connecting the battery string wire harnesses, Tamper, Environmental Control (as applicable), RF drop cable and verifying operation.
These steps can be performed independently of one another. However, conguring the network prior to eld installation will allow the installation to be veried while personnel are still on-site. Performing eld installation before network conguration and before the installation can be veried, might result in additional eld service calls to correct mistakes.
Carefully read the following section in order to understand the dependencies within the system before performing system conguration or hardware installation.
11704-939-B10-001 Rev. A5 (06/2019)
2.0 Overview, continued

2.4 DM3.0 Series Start Up and Reboot Routline

TFTP Server
TOD Server
DHCP Server
TCP/IP NetworkHFC Network
5
4
3
Switches
Routers
Firewalls
CMTS
2
DM3X Transponder
1
Power Supply
Network Management System
6
7

Fig. 2-2, DM3X Transponder Start Up and Reboot Routline

MIB Browser
Web Browser
Local Laptop
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.
• Blue Rx/Tx Power LED indicates Rx/Tx Power at a warning level. Make the necessary RF level adjustments.
• Red Rx/Tx Power LED indicates Rx/Tx Power at an alert level. Make the necessary RF level adjustments.
LEDs and Indications
Ref
#
1
2
3 - 5 Online - registration complete
6
7 Laptop Connected (Local)
Communications State ALM/
Transponder Initializing / Searching for Downstream DOCSIS channel
Downstream channel acquired, service group determination and ranging initialization
DM3.0 Series Transponder fully functional
RDY
Flashing
(Green)
Flashing
(Green)
Flashing
(Green)
Flashing
(Green)
Flashing
(Green)
Downstream
(ds)
Flashing OFF OFF OFF OFF OFF
ON Flashing OFF OFF OFF OFF
ON ON
ON ON
ON ON
Upstream
(US)
Rx / Tx
Power
ON
(Green)
ON
(Green)
ON
(Green)
ONLINE
(OL)
ON OFF and ON OFF
ON
Bursts when
CPE device
communicating
Communications
(COM)
Bursts when
communicating to
multiple power
supplies
Bursts ON
Link
(LNK)
OFF

Table 2-1, LEDs and Indications

12 704-939-B10-001 Rev. A5 (06/2019)

3.0 Network Configuration

3.1 Provisioning the DHCP Server with the MAC Addresses

On the DHCP server, assign the cable modem’s CM MAC address with a DOCSIS Conguration File to set modem communication options. (See Section 3.3, The DOCSIS Conguration File for instructions on how to create a DOCSIS Conguration File).
The CM and CPE MAC addresses are located on the DM3X Transponder and on the packing slip, see below. The CM MAC address may be labeled as the RF MAC address on some DM3X units.
Identier label

Fig. 3-1, Locations of MAC Address Labels

13704-939-B10-001 Rev. A5 (06/2019)
3.0 Network Conguration, continued

3.2 Establishing IP Connectivity

The DM3X Transponder supports the CableLabs DOCSIS 3.0 IPv6 implementation. The main benet of IPv6 is its expanded addressing capability, increasing the address space from 32 to 128 bits, providing virtually unlimited number of networks and systems. The DM3X Transponder determines the IP provisioning mode via the CableLabs SNMP MIB parameter docsIf3CmMdCfgIpProvMode (SNMP OID: 1.3.6.1.4.1.4491.2.1.20.1.31.1.1). The DM3X will support the following congurable IP Provisioning Mode Override policies:
• Honor MDD: The cable modem of the DM3X unit will acquire an IPv6 or IPv4 address as directed by the MAC Domain Descriptor (MDD) message for provisioning and operation.
• IPv4 only: The cable modem of the DM3X unit will acquire a single IPv4 address for the CM management stack, overriding the TLVs in the MDD message.
• IPv6 only: The cable modem of the DM3X unit will acquire a single IPv6 address for the CM management stack, overriding the TLVs in the MDD message.
3.3 The DOCSIS Conguration File
A cable modem’s DOCSIS Conguration File is a type-length-value (TLV) le that contains important operational parameters as dened by the DOCSIS standards. It provides certain settings for the cable modem. In addition to standard entries, settings in the DOCSIS Conguration File should include the modem’s community strings and if an upgrade is necessary, rmware upgrade parameters. Place the Conguration File in the TFTP root directory.
The transponder’s cable modem interface can support both IPv4 and IPv6 addressing schemes. The required DOCSIS Conguration File operational parameters will di󰀨er depending on company policies, cable modem rmware versions and IP addressing schemes. The following DOCSIS Conguration File details listed in this manual are general guidelines. Please consult the published DOCSIS Specication resources (CableLabs) for additional DOCSIS Conguration File details and guidelines.
To build a DOCSIS Conguration File, use a DOCSIS TLV editor program. See the example Conguration Files in Sections 3.3.5 and 3.3.6.
NOTICE:
The modem community strings should be set in the DOCSIS Conguration File. Failure to set community strings will result in a less secure system. For automatically updating modem rmware with the DOCSIS Conguration File, see Section 5.1, Upgrading DM3X Modem Firmware.
14 704-939-B10-001 Rev. A5 (06/2019)
3.0 Network Conguration, continued

3.3.1 Setting Modem Community Strings - docsDevNmAccess Method (IPv4 Only)

Set the modem community strings with the DOCSIS Conguration File by including the following SNMP parameters.
Modem Community String Parameters docsDevNmAccess Method
MIB Parameter Object ID Description Value
docsDevNmAccessIp 1.3.6.1.2.1.69.1.2.1.2.x The IP address (or subnet) of
the NMS
docsDevNmAccessIpMask 1.3.6.1.2.1.69.1.2.1.3.x The IP subnet mask of the NMS e.g. 255.255.255.0
docsDevNmAccessCommunity 1.3.6.1.2.1.69.1.2.1.4.x The community string matched
to this IP address net mask entry
docsDevNmAccessControl 1.3.6.1.2.1.69.1.2.1.5.x The level of access granted 1-3
docsDevNmAccessInterfaces 1.3.6.1.2.1.69.1.2.1.6.x Species the set of interfaces
from which requests from this NMS will be accepted
docsDevNmAccessStatus 1.3.6.1.2.1.69.1.2.1.7.x Controls and reects the status
of rows in this table
e.g. 10.20.30.0
alphanumeric string
None, Read Only, Read / Write
0x40 : Cable interface (typical) 0x80 : Ethernet interface 0xC0 or 0x00 : Both interfaces
4
Note: X denotes the index of the SNMP entry

Table 3-1, Modem Community String Parameters - docsDevNmAccess Method

15704-939-B10-001 Rev. A5 (06/2019)
3.0 Network Conguration, continued

3.3.2 Setting Modem Community Strings - Coexistence Method

Set the modem community strings with the DOCSIS Conguration File for an IPv6 network by including the following SNMP parameters:
Modem Community String Parameters Coexistence Method
TLV
Type
53 SNMPv1v2c
53.1 SNMPv1v2c
53.2 SNMPv1v2c Transport
53.2.1 SNMPv1v2c Transport
53.2.2 SNMPv1v2c Transport
53.3 SNMPv1v2c Access
53.4 SNMPv1v2c Access
TLV Parameter Description Value
Coexistence Conguration
Community Name
Address Access
Address
Address Mask
View Type
View Name
This object species the SNMPv1v2c Coexistence Access Control conguration of the CM. This TLV creates entries in SNMPv3 tables as specied in [DOCSIS OSSIv3.0]
This sub-TLV species the Community Name (community string) used in SNMP requests to the CM.
This sub-TLV species the Transport Address and Transport Address Mask pair used by the CM to grant access to the SNMP entity querying the CM.
Species the Transport Address to use in conjunction with the Transport Address Mask used by the CM to grant access to the SNMP entity querying the CM. Length is 6 bytes for IPv4 and 18 bytes for IPv6. Two additional bytes are added to the IP address length for the port number.
Species the Transport Address Mask to use in conjunction with the Transport Address used by the CM to grant access to the SNMP entity querying the CM. Length is 6 bytes for IPv4 and 18 bytes for IPv6. Two additional bytes are added to the IP address length for the port number.
Species the type of access to grant to the community name of this TLV. If not specied, default read-only is used.
Species the name of the view that provides the access indicated in sub-TLV SNMPv1v2c Access View Type.
Composite
Text (e.g. AlphaRead)
Variable
Transport Address (e.g. 0.0.0.0/0 or 0:0:0:0:0:0:0:0/0)
Transport Address (e.g. 0.0.0.0/0 or 0:0:0:0:0:0:0:0/0)
1 = Read Only 2 = Read / Write
String (e.g. docsisManagerView)

Table 3-2, Modem Community String Parameters - Coexistence Method

16 704-939-B10-001 Rev. A5 (06/2019)
3.0 Network Conguration, continued

3.3.3 Setting SNMP Trap Destination Addresses - docsDevNmAccess Method

Set the SNMP Trap Destination Addresses via the DOCSIS Conguration File by including the following SNMP parameters.
Trap Destination Addresses docsDevNmAccess Method
MIB Parameter Object ID Description Value
docsDevNmAccessIP 1.3.6.1.2.1.69.1.2.1.2.x IP address of trap
destination, e.g. NMS server
docsDevNmAccessIpMask 1.3.6.1.2.1.69.1.2.1.3.x Must be set to
255.255.255.255 per RFC 4639
docsDevNmAccessCommunity 1.3.6.1.2.1.69.1.2.1.4.x Community string used by
NMS to query transponder
docsDevNmAccessControl 1.3.6.1.2.1.69.1.2.1.5.x Level of SNMP access to
DM3X Transponder from IP address specied in docsDevNmAccessIpMask
docsDevNmAccessInterfaces 1.3.6.1.2.1.69.1.2.1.6.x Species the set of
interfaces from which requests from this NMS will be accepted
docsDevNmAccessStatus 1.3.6.1.2.1.69.1.2.1.7.x Controls and reects the
status of rows in this table
e.g. 10.20.30.40
255.255.255.255
alphanumeric string
4=Read/Only plus Trap 5=Read/Write plus Trap 6=Trap only, no SNMP access
0x40 : Cable interface (typical) 0x80 : Ethernet interface 0xC0 or 0x00 : Both interfaces
4
Note: X denotes the index of the SNMP entry

Table 3-3, Trap Destination Addresses - docsDevNmAccess Method

17704-939-B10-001 Rev. A5 (06/2019)
3.0 Network Conguration, continued

3.3.4 Setting SNMP Trap Destination Addresses - Coexistence Method

Set the SNMP Trap Destination Addresses via the DOCSIS Conguration File by including the following SNMP parameters:
Trap Destination Addresses Coexistence Method
TLV
Type
38
38.1
38.2
38.3
38.4
38.5
38.6
TLV Parameter Description Value
This cong le element species an NMS
SNMPv3 Notication Receiver
SNMPv3 Notication Receiver IP Address
SNMPv3 Notication Receiver UDP Port Number
SNMPv3 Notication Receiver Trap Type
SNMPv3 Notication Receiver Timeout
SNMPv3 Notication Receiver Retries
SNMPv3 Notication Receiver Filtering Parameters
that will receive notications from the modem when it is in Coexistence mode. Up to 10 of these elements may be included in the conguration le.
This sub-TLV species the IP address of the notication receiver.
This sub-TLV species the UDP port number of the notication receiver. If this sub-TLV is not present, the default value of 162 should be used.
This sub-TLV species the type of trap to send.
This sub-TLV species the timeout value to use when sending an Inform message to the notication receiver.
This sub-TLV species the number of times to retry sending an Inform message if an acknowledgement is not received.
Object Identier of the snmpTrapOID value that identies the notications to be sent to the notication receiver. This notication and all below it will be sent.
Composite
0:0:0:0:0:0:0:0 (e.g.fc00:168:1:0:0:0:0:32)
0.0.0.0 (e.g. 10.11.0.1)
UDP port number (e.g. 162)
The trap type may take values: 1 = SNMP v1 trap in an SNMP v1 packet 2 = SNMP v2c trap in an SNMP v2c packet 3 = SNMP inform in an SNMP v2c packet 4 = SNMP v2c trap in an SNMP v3 packet 5 = SNMP inform in an SNMP v3 packet
Time in milliseconds (e.g. 15000)
Number of retries (e.g. 3)
Filter OID (e.g. 1.3.6)

Table 3-4, Trap Destination Addresses - Coexistence Method

NOTICE:
As an alternative to the docsDevNmAccessTable or SNMPv3 trap parameters, SNMP Trap Destination Addresses may be set through the DM3X proprietary MIB atiMgmtSnmpTrapTable (OID: 1.3.6.1.4.1.926.1.3.1.1) using a SNMP MIB Browser or as an entry in the Proprietary Conguration File ‘atidoc33.cfg’ in Section 3.3.6, Sample DOCSIS Conguration File Entries — Coexistence Method.
18 704-939-B10-001 Rev. A5 (06/2019)
3.0 Network Conguration, continued
3.3.5 Sample DOCSIS Conguration File Entries - devDocNmAccess
SNMP MIB Object (11) [Len=21]:docsDevNmAccessStatus.1/4 SNMP MIB Object (11) [Len=21]:docsDevNmAccesslp.1/10.56.21.0 SNMP MIB Object (11) [Len=21]:docsDevNmAccesslpMask.1/255.255.255.0
1
SNMP MIB Object (11) [Len=25]:docsDevNmAccessCommunity.1/”RW STRING” SNMP MIB Object (11) [Len=25]:docsDevNmAccessInterfaces.1/”@” SNMP MIB Object (11) [Len=21]:docsDevNmAccessControl.1/3
SNMP MIB Object (11) [Len=21]:docsDevNmAccessStatus.2/4 SNMP MIB Object (11) [Len=21]:docsDevNmAccesslp.2/10.20.30.40 SNMP MIB Object (11) [Len=21]:docsDevNmAccesslpMask.2/255.255.255.255
2
SNMP MIB Object (11) [Len=25]:docsDevNmAccessCommunity.2/”RW Trap string” SNMP MIB Object (11) [Len=25]:docsDevNmAccessInterfaces.2/”@” SNMP MIB Object (11) [Len=21]:docsDevNmAccessControl.2/5
Software Upgrade Filename(9) [Len=24]:”ModemFirmwareFile.bin”
3
SNMP MIB Object (11) [Len=20]:docsDevSwAdminStatus.0/2
4
Software Upgrade TFTP Server (21) [Len=4]:10.56.48.15
Manufacturer Code Verication Certicate (32) [Len=254]: 30 82 03 1A 30 82... Manufacturer Code Verication Certicate (32) [Len=254]: 04 0A 13 11 41 4D...
5
Manufacturer Code Verication Certicate (32) [Len=254]: 04 0C 30 0A 06 01...
Manufacturer Code Verication Certicate (32) [Len=36]: 11 A3 41 A6 A7 D9....
Legend
1
Sets Read-Write community string. Set the IP address, netmask and community string to t your system.
2
Sets the IP address of where the SNMP traps will be sent. This is typically set to match the IP address of the Network Managements System Server.
3
Sets rmware download parameters.
4
Species the IP address of the TFTP server used for upgrading rmware.
5
Sets Code Verication Certicate (CVC) for rmware upgrade security per the DOCSIS specication.
19704-939-B10-001 Rev. A5 (06/2019)
3.0 Network Conguration, continued
3.3.6 Sample DOCSIS Conguration File Entries - Coexistence
SNMPv1v2c Coexistence Conguration SNMPv1v2c Community Name:ReadWrite SNMPv1v2c Transport Address Access SNMPv1v2c Transport Address:0.0.0.0/0 SNMPv1v2c Transport Address Mask:0.0.0.0/0
1
SNMPv1v2c Transport Address Access SNMPv1v2c Transport Address:0:0:0:0:0:0:0:0/0 SNMPv1v2c Transport Address Mask:0:0:0:0:0:0:0:0/0 SNMPv1v2c Access View Type:read-write SNMPv1v2c Access View Name:docsisManagerView
Docsis V3 Notication Receiver UDP Port number of trap receiver:162 Type of trap:SNMP v1 trap in an SNMP v1 packet Timeout for sending inform:15000 Number of retries:3 Filtering Parameters:1.3.6 IPv6 Address of trap receiver:fc00:168:1:0:0:0:0:32
2
Docsis V3 Notication Receiver IP Address of trap receiver:192.168.1.51 UDP Port number of trap receiver:162 Type of trap:SNMP v1 trap in an SNMP v1 packet Timeout for sending inform:15000 Number of retries:3 Filtering Parameters:1.3.6
3
Software Upgrade Filename:ModemFirmwareFile.bin
4
Software Upgrade IPv6 TFTP Server:fc00:168:1:0:0:0:0:51
Manufacturer Code Verication Certicate:3082031B30820… Manufacturer Code Verication Certicate:040A1312414C5…
5
Manufacturer Code Verication Certicate:FF040C300A060… Manufacturer Code Verication Certicate:257939C848CE0…
Legend
1
Sets Read-Write community string. Set the IP address, netmask and community string to t your system.
2
Sets the IP address of where the SNMP traps will be sent. This is typically set to match the IP address of the Network Managements System Server.
3
Sets rmware download parameters.
4
Species the IP address of the TFTP server used for upgrading rmware.
5
Sets Code Verication Certicate (CVC) for rmware upgrade security per the DOCSIS specication.
NOTICE:
DOCSIS conguration les vary from system to system. Take into consideration your company’s policies and test the le on a local system prior to widescale deployment.
In previous versions of the DM product line, an additional conguration le (also known as a Setup File) could be used for distributing custom Alpha MIB settings to all DMs on a network. This is still the case, with the only di󰀨erence being the name of the le, which for the DM3.0 Series is atidoc33.cfg. It may be used if preferred but is not required.
20 704-939-B10-001 Rev. A5 (06/2019)
3.0 Network Conguration, continued
3.3.7 Proprietary Conguration File ‘atidoc33.cfg’
The DM3X Transponder will attempt to download a TLV-formatted le ‘atidoc33.cfg’ from the modem’s provisioning TFTP server at start up and every 24 hours thereafter. The atidoc33.cfg proprietary conguration le is optional and provides an alternative method to the modem’s DOCSIS conguration le for deploying Alpha proprietary SNMP MIB parameters to eld-installed DM3.0 Series Communications Modules.
The atidoc33.cfg le should be used if the following conditions are true:
1. Non-default settings, such as SNMP Trap Destination Addresses need to be distributed to all DM3X Transponders.
2. The operator does not desire to place Alpha-proprietary parameters into the modem’s DOCSIS conguration le.
NOTICE:
The recommended method for setting the SNMP trap address(es) is through the modem DOCSIS conguration le (See Section 3.3, The DOCSIS Conguration File). Alpha-proprietary parameters may also be set through the modem’s DOCSIS conguration le, eliminating the need for the atidoc33.cfg proprietary conguration le.
To build the atidoc33.cfg le, enter the desired SNMP OIDs and values from the Alpha MIB into a TLV le as TLV type-11 entries using a TLV editor (Refer to sample entries below). The DM3X proprietary conguration Setup le must be named “atidoc33.cfg” and placed in the root directory of the TFTP server. DM3X settings are updated according to values dened in this le at start up and after every 24 hours of operation. Sample atidoc33.cfg Entries:
• Network Access Control (3) [Len - 1]: 1
• SNMP MIB Object (11) [Len = 24]: atiMgmtSnmpTrapAddress.1 / 10.20.30.40
• SNMP MIB Object (11) [Len = 24]: atiMgmtSnmpTrapAddress.2 / 10.20.30.50
• SNMP MIB Object (11) [Len = 23]: atiMgmtSysTamperPolarity.0 / 1
21704-939-B10-001 Rev. A5 (06/2019)
3.0 Network Conguration, continued

3.3.8 Changing Default atidoc33.cfg Download Settings

By default, the DM3X Transponder will download the atidoc33.cfg le from the provisioning TFTP server every 24 hours. However, these settings may be adjusted per the tables below by placing the respective SNMP varbinds into the modem’s DOCSIS conguration le.
Default atidoc.cfg Download Settings
Parameter Type Description Value
atiMgmtSysDownloadCongName
1.3.6.1.4.1.926.1.3.2.1.9.0
atiMgmtSysDownloadReCfgTime
1.3.6.1.4.1.926.1.3.2.1.13.0
Search Order Parameter Type Description Value
Alphanumeric String
Integer
Name of proprietary conguration le
Download interval for atidoc33.cfg (hours)
“atidoc33.cfg” (Default)
24 (Default)
1
2
3
4 Software Upgrade Server IP Address
atiMgmtSysDownloadCongAddress OID 1.3.6.1.4.1.926.1.3.2.1.10.0
docsDevServerCongTftpAddress
1.3.6.1.2.1.69.1.4.11.0
docsDevSwServerAddress
1.3.6.1.2.1.69.1.3.7.0

Table 3-5, Default atidoc33.cfg Download Settings

IP Address
IP Address
IP Address
Overrides default location
Default location (no change necessary)
Set via DOCSIS conguration le
Set via DOCSIS conguration le
0.0.0.0 (Default)
CM’s TFTP Server Address
Congurable
Congurable
22 704-939-B10-001 Rev. A5 (06/2019)
3.0 Network Conguration, continued

3.4 Setting Communication Options

Communications Settings may be changed through the Alpha MIB remotely using an SNMP MIB browser or automatically by placing the SNMP parameters into the DOCSIS Conguration File.
NOTICE:
Before setting options, verify UDP ports 37, 69, 161, 162 and TCP port 80 are not blocked.
Communications Parameters
SNMP Parameter Type Description Value
atiMgmtSnmpTrapOnNormal OID: 1.3.6.1.4.1.926.1.3.1.5.1.0
atiMgmtSysDownloadReCfgTime OID: 1.3.6.1.4.1.926.1.3.2.1.13.0
atiMgmtSysSnmpTimeout OID: 1.3.6.1.4.1.926.1.3.1.5.3.0
atiMgmtSysHttpAccess OID: 1.3.6.1.4.1.926.1.3.2.2.4.1.0
Integer
Integer
Integer
Integer HTTP Web Server
Send SNMP trap when alarmed condition returns to normal state
Download interval for DM3X-specic items in atidoc33.cfg cong le (hours)
Time DM3X will wait before reset if SNMP tra󰀩c is not detected (minutes)
1 = Disabled 2 = Enabled (Default)
24 (Default)
240 (Default) Note: If set to zero, watchdog will be disabled.
1 = Disabled 2 = Enabled (default)

Table 3-6, Communications Parameters

NOTICE:
The DM3X Transponder will inherit the cable modem community string settings provided by the DOCSIS Conguration File.
23704-939-B10-001 Rev. A5 (06/2019)

4.0 Web Interface

Overview
The DM3X provides an embedded Web server interface to allow operations personnel the ability to connect locally or remotely via TCP/IP over Ethernet with a laptop/computer to verify the status of common data points and to congure various operating parameters. Unless otherwise stated, data values shown in the gures throughout this section are shown for illustration purposes only.

4.1 Local Web Server Access

The DM3X Ethernet port (comparable to the Craft port on some transponder models) will typically be used as a local connection point allowing the user to connect directly to the DM3X Web server interface to verify/congure common communication parameters and view power supply status and battery values. The Ethernet port on the DM3X is a fully functional standard Ethernet port, capable of providing all the functionality of any standard Ethernet connection.
To access the DM3X Web server locally utilizing a Web browser, use the following procedure:
NOTICE:
The following Web Browser settings should be ‘enabled’ for proper rendering/download of the web pages:
• Java Script
• Cookies
• ActiveX Controls
• Downloads
• Active Scripting
• Show Pictures These settings are typically enabled in the Web Browser by default.
1. Connect a standard Ethernet cable (CAT5) between the DM3X Ethernet port (ETH) and a laptop or computer’s network interface port.
2. Launch a Web browser.
3. Enter the transponder’s default IP address (192.168.100.1) or the DHCP assigned IP address into the Web browser’s address eld.
4. The transponder’s Web server home page will appear (Fig. 4-1). Note: This may take up to 45 seconds when the transponder is initially powered up with no RF connection. Click the Language menu to select a desired language for the text information on the Web page. The language choices are English (default), Spanish, Portuguese, French & German.

Fig. 4-1, DM3X Web Page

24 704-939-B10-001 Rev. A5 (06/2019)
4.0 Web Interface, continued
NOTICE:
If you are unable to view the home page of the DM3X Transponder using IP address 192.168.100.1, the network conguration on the computer that is being used to connect to the DM3X Transponder may require a temporary static IP address (192.168.100.2) to be congured.
Use the following procedure to congure a static IP address on a laptop or computer with the Windows® 7 operating system:
1. Click the Start button (lower left button on most Windows® computers).
2. When the window pops up, click Control Panel (usually about half the way down the second column).
3. Click Network Connections.
4. Right-Click Local Area Connection link to open menu box.
5. Click the bottom option Properties.
6. You will see a dialog box much like Fig. 4-2; select Internet Protocol (TCP/IP) and then click the Properties button.
1. The Internet Protocol (TCP/IP) Properties dialog box will open (Fig. 4-3). Select “Use the following IP address”. Enter the values as shown (i.e. IP address 192.168.100.2, or DHCP assigned IP address, and Subnet mask 255.255.255.0). Record the existing IP address and Subnet mask in order to later return the computer to its original state.
2. Click the OK button and try to connect to the DM3X once again using
192.168.100.1 in the Web browser.
3. To restore network settings, repeat Steps 1 through 6 but in step 7 click check box for “Obtain IP address automatically or, manually set back to the original settings recorded in Step 7.
Fig. 4-2, Local Area Connection
Properties Screen, Windows® 7
1. Fig. 4-3, Internet Protocol (TCP/IP) Properties Screen, Windows® 7
25704-939-B10-001 Rev. A5 (06/2019)
4.0 Web Interface, continued
Use the following procedure to congure a static IP address on a laptop or computer with the Windows® 8 operating system:
1. Click the Start button (lower left button on most Windows® computers).
2. When the window pops up, click Control Panel (usually about half the way down the second column).
3. Click Network and Sharing Center.
4. Click Local Area Connection.
5. Click the Properties button.
6. You will see a dialog box much like Fig. 4-4; click Internet Protocol (TCP/ IPv4) and then click the Properties button.
1. Fig. 4-4, Local Area Connection Properties Screen, Windows® 8
1. The Internet Protocol (TCP/IP) Properties dialog box will open (Fig. 4-5). Select “Use the following IP address”. Enter the values as shown (i.e. IP address 192.168.100.2 and Subnet mask 255.255.255.0). Record the existing IP address and Subnet mask in order to later return the computer to its original state.
2. Click the OK button and try to connect to the DM3X once again using
192.168.100.1 in the Web browser.
3. To restore network settings, repeat Steps 1 through 6 but in step 7 click check box for “Obtain IP address automatically or, manually set back to the original settings recorded in Step 7.
1. Fig. 4-5, Internet Protocol (TCP/IP) Properties Screen, Windows® 8
26 704-939-B10-001 Rev. A5 (06/2019)
4.0 Web Interface, continued

4.2 Remote Web Server Access

To remotely access the DM3X Web server utilizing a Web browser, use the following procedure:
NOTICE:
For Web server (HTTP) access, port 80 must not be blocked and the computer must have access to the private cable modem network
1. Connect the laptop or computer’s network interface port to the company’s Ethernet network.
2. Open a Web browser.
3. Enter the DM3X DHCP designated IP address (e.g., 192.168.1.124) into the Web browser’s address eld. Use square brackets when entering IPv6 IP addresses (e.g. [FC00:168:40::124]) into the Web browser’s address eld.
4. The DM3X Web server home page will appear (Fig. 4-6).
5. Click on the Language menu to select a desired language for the text information on the Web page. The language choices are English (default), Spanish, Portuguese, French and German.

Fig. 4-6, Web Server Home Page

27704-939-B10-001 Rev. A5 (06/2019)
4.0 Web Interface, continued

4.3 Navigating the Web Page

Once the Web page has been successfully accessed, the operator is able to select a link on the header bar and the page specic to the topic will open enabling real-time data to be observed.
See Fig. 4-7 for the navigation bar items.
TM
AlphaNet
DOCSIS Status Monitor
General Tools Apps History Language Print
Commonly used parameters for quick diagnostics of Power Supply, Communications, Batteries and Generator.
Communications: Comprehensive communications diagnostic parameters
Power Supply: Comprehensive Power
parameters
Generator: Comprehensive Generator
IO - Environment:
of Tamper polarity and external I/O devices
HMS Alarms: Status of SCTE-HMS active alarms, alarm history and alarm threshold settings.
Constellation: Provides a constellation view of the DOCSIS channel for troubleshooting impairments.
Provides details about impairments on the network and the approximate distance(s) of those impairment(s). Requires the Adaptive equalization feature to be enabled on the CMTS.
Spectrum: Displays and records the Full Band Capture data by directly sampling and digitizing the entire 1GHz downstream spectrum.
The Web page content will be displayed in the selected language
System Logs (requires AlphaApp card): Log
from each of the system logs.
Power Supply Events (requires AlphaApp card):
Records daily Power Supply system events.
AlphaApp card): Records power supply system
the initial installation.
Battery Events (requires AlphaApp card):
Records battery conductance measurements and manufacturing dates.
Cable Modem Log: Web page representation of the DOCSIS modem event log.
(Requires AlphaApp card)
Overview: Provides AlphaApp card version and status, plus Utility power health information.
Battery Management: technician ID, battery conductance measurements, battery model and battery manufacturing dates for runtime and battery life calculations.
Sends the contents of the selected Web page to the computer’s default printer.

Fig. 4-7, Navigation Bar Items

28 704-939-B10-001 Rev. A5 (06/2019)
4.0 Web Interface, continued

4.3.1 Web Interface Security Levels

The DM3X has two levels of function-specic security. General operations are Level 1. Conguration-related functions are Level 2. Refer to Table 4-1 for default User Name and Security Passwords.
DM3.0 Series Transponder Web Page Security
OID Function Value
1.3.6.1.4.1.4413.2.2.2.1.1.3.3.0 Level 1 User Name Alpha
1.3.6.1.4.1.4413.2.2.2.1.1.3.4.0 Level 1 Security Password AlphaGet
1.3.6.1.4.1.4413.2.2.2.1.1.3.1.0 Level 2 User Name Alpha
1.3.6.1.4.1.4413.2.2.2.1.1.3.2.0 Level 2 Security Password AlphaSet

Table 4-1, DM3X Web Page Security

DM3.0 Series Transponder Security Levels
Web Page Function Security Level
System Name, System Contact, System Location, Common Logical ID 1
General
Advanced Communications
Advanced Power Supply
Advanced Generator
Modem Log [Event Log] Reset Log 1
Advanced I/O
HMS Alarms Export Alarm Cloning File 2
Constellation Number of Samples 2
Power Supply Self-Test 1
Generator Self-Test 1
Reset Transponder 1
Provisioning Mode - Single IP or Dual IP 2
Congure Proprietary Trap Addresses 2
Power Supply Self-Test 1
Congure / Save 2
Reset Output 1 / 2 2
Generator Self-Test 1
Reset Latched Alarms 1
Tamper Switch Polarity 1
Enclosure Heater / Controller Installed 1

Table 4-2, DM3X Security Levels

29704-939-B10-001 Rev. A5 (06/2019)
4.0 Web Interface, continued

4.4 Verifying Communication Parameters

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

Fig. 4-8, Communication Parameters

Fig. 4-9, Advanced Communication Parameters

30 704-939-B10-001 Rev. A5 (06/2019)
Loading...
+ 70 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use