Alpha CMD-N Arris SG4000 Technical Manual

Type
Technical Manual
CMD-N Arris SG4000
Technical Manual
Effective: March 2016
Safety Notes
Alpha considers customer safety and satisfaction its most important priority. To reduce the risk of
injury or death and to ensure continual safe operation of this product, certain information is presented
differently in this manual. Alpha tries to adhere to ANSI Z535 and encourages special attention and
care to information presented in the following manner:
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.
There may be multiple warnings associated with the call out. Example:
ATTENTION provides specic regulatory/code requirements that may affect the placement of equip-
ment and /or installation procedures.
ATTENTION:
NOTICE provides additional information to help complete a specic task or procedure.
NOTICE:
ELECTRICAL HAZARD WARNING provides electrical safety information to PREVENT
INJURY OR DEATH to the technician or user.
WARNING! ELECTRICAL HAZARD
FUMES HAZARD WARNING provides fumes safety information to PREVENT INJURY OR
DEATH to the technician or user.
WARNING! FUMES HAZARD
FIRE HAZARD WARNING provides ammability safety information to PREVENT INJURY OR
DEATH to the technician or user.
WARNING! FIRE HAZARD
This WARNING provides safety information for both Electrical AND Fire Hazards
WARNING! ELECTRICAL & FIRE HAZARD
CAUTION provides safety information intended to PREVENT DAMAGE to material or
equipment.
CAUTION!
GENERAL HAZARD WARNING provides safety information to PREVENT INJURY OR
DEATH to the technician or user.
WARNING! GENERAL HAZARD
3050-0188, Rev. J (03/2016)
CMD-N Arris SG4000
Technical Manual
050-0188, Rev. J
Effective Date: March 2016
©
2016 by Alpha Technologies, 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 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):
Website:
866 944 1482
www.alpha.com
www.cheetahtech.com
412 923 3486
4 050-0188, Rev. J (03/2016)
Table of Contents
1.0 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1 CMD-N Transponder Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3 Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.0 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1 Connections Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.3 CMD-N Transponder Specications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
3.0 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.1 Provisioning the Transponders in the Network . . . . . . . . . . . . . . . . . . . . . . . . 12
3.2 Your Network Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.4 Cable Modem Conguration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.5 Installing the CMD-N Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
SG4000 Node Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
MBN100/200 Node Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
BTN100 Modular Optical Node Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.6 Transponder Conguration Using the sg4000NodeDiscoveryGroup MIB . . . . . . . . . . 25
3.7 Viewing and Overriding the BPIM Switch Setting . . . . . . . . . . . . . . . . . . . . . . 26
3.8 Checking the LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.0 Provisioning the SNMP Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.1 MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2 Acquiring the Transponders by the SNMP Manager . . . . . . . . . . . . . . . . . . . . . 29
5.0 Using the Craft Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.2 Web Page Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.3 Console Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.0 CMD-N Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.2 Conguring the SYSNAME and SYSLOCATION OIDs. . . . . . . . . . . . . . . . . . . . 34
Conguration Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Choosing the Appropriate Device Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.3 Status Page for Software Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.4 Status Page for Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.5 Status Page for the SNMP Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.6 HMS Fiber Node Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.7 HSIA Diagnostics Page: Ping Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Controlling the Ping Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Simultaneous Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.8 HSIA Diagnostics Page: Traceroute Command . . . . . . . . . . . . . . . . . . . . . . . 44
Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Controlling the Traceroute Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Simultaneous Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5050-0188, Rev. J (03/2016)
6.9 RF Constellation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Downstream Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Interpreting QAM Constellation Data by Visual Inspection . . . . . . . . . . . . . . . . . . 47
6.10 MTA Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.11 MTA DHCP Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.12 MTA Quality of Service (QoS) Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.13 MTA Provisioning Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.14 MTA Event Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.0 Cable Pinout Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.1 Ethernet Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.0 Upgrading the CMD-N Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table of Contents, Continued
6 050-0188, Rev. J (03/2016)
Figures
Fig. 1-1, CMD-N Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Fig. 2-1, CMD-N Transponder Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Fig. 3-1, Typical Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Fig. 3-2, Cable Modem Conguration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Fig. 3-3, Fiber Node Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Fig. 3-4, Slot and Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Fig. 3-5, Mounting Screw Access Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Fig. 3-6, RF Cable Attached to RF Test Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Fig. 3-7, RF Cable Attached to SM Test Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Fig. 3-8, Fiber Node Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Fig. 3-9, Slot and Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Fig. 3-10, Mounting Screw Access Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Fig. 3-11, RF Cable Attached to Injection Point . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Fig. 3-12, RF Cable Attached to SM Test Point . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Fig. 3-13, Fiber Node Interface Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Fig. 3-14, Slot and Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Fig. 3-15, Mounting Screw Access Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Fig. 3-16, RF Cable Attached to RF Test Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Fig. 3-17, RF Cable Attached to SM Test Point on the Return Conguration Board . . . . . . . . . 23
Fig. 3-18, RF Cable Attached to SM Test Point on Receiver Optical Module . . . . . . . . . . . . 24
Fig. 3-19, The CMD-N Transponder LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Fig. 5-1, Console Main Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Fig. 5-2, Console Prompt Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Fig. 5-3, Console HMS Prompt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Fig. 5-4, Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Fig. 6-1, Conguration Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Fig. 6-2, Status Page for Software Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Fig. 6-3, Status Page for Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Fig. 6-4, Status Page for the SNMP Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Fig. 6-5, SG4000 Fiber Node Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Fig. 6-6, MBN200 Fiber Node Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Fig. 6-7, BTN100 Fiber Node Data Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Fig. 6-8, HSIA Diagnostics Page: Ping Command . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Fig. 6-9, Ping Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Fig. 6-10, HSIA Diagnostics Page: Traceroute Command . . . . . . . . . . . . . . . . . . . . . . 44
Fig. 6-11, Traceroute Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Fig. 6-12, Constellation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Fig. 6-13, Sample QAM Constellation — Normal Centered Dots (Good Sound Quality) . . . . . . 48
Fig. 6-14, Sample QAM Constellation — Fuzzy (Low CNR and/or Low MER) . . . . . . . . . . . 48
Fig. 6-15, Sample QAM Constellation — “Doughnuts” (Coherent Interference) . . . . . . . . . . . 49
Fig. 6-16, Sample QAM Constellation — Gaussian Noise . . . . . . . . . . . . . . . . . . . . . . 49
Fig. 6-17, Sample QAM Constellation — Circular Smear (Phase Noise) . . . . . . . . . . . . . . 50
Fig. 6-18, Sample QAM Constellation — Corners Squeezed to Center (Gain Compression) . . . . 50
Fig. 6-19, Sample QAM Constellation — Rectangular vs. Square (I-Q Imbalance) . . . . . . . . . 51
Fig. 6-20, Sample QAM Constellation — Twisted or Skewed (Quadrature Distortion). . . . . . . . 51
Fig. 6-21, MTA Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Fig. 6-22, MTA DHCP Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Fig. 6-23, MTA Quality of Service (QoS) Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7050-0188, Rev. J (03/2016)
Tables
Table 1-1, CMD-N Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 2-1, Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Table 2-2, CMD-N Transponder Specications . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Table 3-1, Network Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 3-2, Status Monitoring Slot Number Cross Reference. . . . . . . . . . . . . . . . . . . . . 21
Table 3-3, LED Status Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 4-1, ANSI / SCTE Management Information Base (MIB) Files . . . . . . . . . . . . . . . . 28
Table 4-2, Arris Management Information Base (MIB) Files . . . . . . . . . . . . . . . . . . . . . 28
Table 5-1, OIDs for Usernames, Passwords, Telnet Access for Console Access . . . . . . . . . . 30
Table 5-2, TelnetIpStackInterfaces OID Values and Descriptions . . . . . . . . . . . . . . . . . . 31
Table 5-3, Telnet Access Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 5-4, Commands Available in the HMS Section of Console Mode . . . . . . . . . . . . . . . 33
Table 6-1, OIDs for Port Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 6-2, OIDs for Usernames and Passwords for Web Interface Access . . . . . . . . . . . . . 34
Table 6-3, Status Monitoring Slot Number Cross Reference. . . . . . . . . . . . . . . . . . . . . 41
Table 6-4, Input Parameters for the Ping Command . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 6-5, Control Buttons on the Ping Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 6-6, Input Parameters for the Traceroute Command . . . . . . . . . . . . . . . . . . . . . 44
Table 6-7, Control Buttons on the Traceroute Screen . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 6-8, QAM Constellation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Table 7-1, Pin Number Conguration Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figures, Continued
Fig. 6-24, MTA Provisioning Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Fig. 6-25, MTA Event Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8 050-0188, Rev. J (03/2016)
1.0 Introduction
1.1 CMD-N Transponder Overview
The CMD-N transponder provides the ability to manage ber nodes through an existing cable modem infrastructure.
Contact an Alpha Technical Support Representative for a complete listing of supported ber nodes.
The transponder transmits data to a management system over the network’s existing DOCSIS infrastructure, using
standard SNMP (Simple Network Management Protocol). Status monitoring information is compatible with ANSI/SCTE
HMS standards.
This CMD-N transponder can be installed in either an SG4000, MBN100/200 node, or a BTN100 node. The transponder
will query the EPIM or VPIM module in the Node to determine the node type and will congure itself appropriately. If there
is no EPIM or VPIM for the transponder to query, it will default to operating in SG4000 mode.
Fig. 1-1, CMD-N Transponder
The CMD-N transponder:
Uses ANSI/SCTE HMS standards
Measures analog or receives digital SCTE/HMS data from ber nodes
Can be network managed through an existing DOCSIS infrastructure
To the cable network infrastructure, the CMD-N transponder appears as a DOCSIS 2.0 cable modem. The transponder
is assigned an IP address like any other DOCSIS device on the DOCSIS network. The assigned IP address is used to
access the HMS status monitoring data via SNMP and the HMS MIBs.
For complete DOCSIS specications, see Cable Laboratories specications (Cable Labs Public DOCSIS SPECS) at
www.cablelabs.com.
Node type discovery can be controlled or overriden via SNMP. For more information, see the section titled
“Transponder Conguration Using the sg4000NodeDiscoveryGroup MIB”
NOTICE:
1.0 Introduction, continued
9050-0188, Rev. J (03/2016)
1.2 Parts List
Table 1-1 lists the transponder and any other items that are available as an option. For damage or discrepancies, please
contact an Alpha Technical Support representative.
Table 1-1, CMD-N Parts List
1.3 Contact Information
For technical issues related to Motorola or Arris nodes, customers should call Arris Technical Support at:
Domestic — 1-866-36-ARRIS (1-866-362-7747)
International — +1-678-473-2907
CMD-N Parts List
Description Part Number Quantity
CMD-N Transponder 66900-0665 1
10 050-0188, Rev. J (03/2016)
2.0 Connections
2.1 Connections Overview
The CMD-N transponder includes six status LEDs, the Craft* port (which is a standard RJ-45 Ethernet connector), an
optical tamper sensor, RF communication cables, and a node interface connector. The transponder receives its power and
performs communications all via the node interface connector. The locations of these items are shown in Figure 2.
* The Craft port provides local access to the transponder. However, it is important to note that the Craft port is a fully
functional standard Ethernet port capable of providing all the functionality of any standard Ethernet connection. DOCSIS
conguration can affect the the Craft port’s addressing and network connection.
Fig. 2-1, CMD-N Transponder Connections
Tamper Sensor
Craft Port
LEDs
Label with
Transponder
Serial Number
2.0 Connections, continued
11050-0188, Rev. J (03/2016)
2.2 Connector Summary
Table 2-1, Connector Summary
2.3 CMD-N Transponder Specications
Table 2-2, CMD-N Transponder Specications
Connector Summary
Connector Description
DS RF Cable
The Forward (Downstream) RF cable is the physical connection to the forward RF -20dB test point of
an SG4000-RF module or the -20dB Status Monitor Output injection point of the MBN100/200.
US RF Cable
The Return (Upstream) RF cable is the physical connection to the “SM” injection point connector on
the Return Conguration Board of an SG4000 or the Transmitter Status Monitor injection point of the
MBN100/200.
Craft
The Craft port provides a local connection to the transponder. The Craft port is a fully functional
standard Ethernet port capable of providing all the functionality of any standard Ethernet connection.
Node Interface The Node Interface is the physical connection point at which the transponder attaches to the node.
Tamper Sensor The Tamper Sensor provides an indication of physical tampering (opening of the node enclosure).
LED Indicators
The CMD-N transponder includes six green LEDs that indicate transponder status: PWR, DS, US,
Online, Elink, and Status.
CMD-N Transponder Specications
Parameter Specication
General
DOCSIS Version 2.0
HMS Monitoring Protocol SNMP v1
DOCSIS Monitoring Protocol SNMP v1, v2, v3
RF Interface Internal
RF Internal Padding 18dB Downstream and 15dB Upstream
Ethernet Interface RJ45
Operating Temperature
–40°C to +75°C
Humidity 10% to 90% (non-condensing)
EMI/EMC FCC Part 15 Class A, CE EN50022 Class A
RF Transmit/Receive
Tx Frequency Range 5 to 42 MHz
Tx Output Power +8 to +58 dBmV
Rx Frequency Range 88 MHz to 860 MHz
Rx Input Level –15 to +15 dBmV
Channel Bandwidth 6 MHz to 8 MHz
Part Numbers
Transponder 66900-0665
12 050-0188, Rev. J (03/2016)
3.0 Installation
Cable modem infrastructures are likely to have unique characteristics, therefore Alpha Technologies strongly recommends
completely installing one transponder and making it operational before deploying the entire system throughout your
network.
Installing the transponders for operation consists of the following steps:
Provisioning the transponders in the network
Adding conguration data to the cable modem conguration le
Installing the transponder
Powering the transponder and checking the LEDs for status
3.1 Provisioning the Transponders in the Network
Before installing CMD-N transponders, the transponder must be provisioned in the network in order for the network to
recognize, discover, and communicate with the transponders when they are powered up. The following graphic shows a
typical network.
Fig. 3-1, Typical Network
The transponders must be received into the inventory like other cable modems to allow their MAC addresses to be
provisioned into the billing system.
NOTICE:
Node type discovery can be controlled or overriden via SNMP. For more information, see the section titled
“Transponder Conguration Using the sg4000NodeDiscoveryGroup MIB”
NOTICE:
3.0 Installation, continued
13050-0188, Rev. J (03/2016)
3.2 Your Network Information
The following worksheet will assist in gathering the network information needed throughout the deployment process.
Table 3-1, Network Worksheet
The deployment of an Alpha DOCSIS-based transponder is similar to provisioning a standard subscriber cable modem
and MTA with certain exceptions owing to the transponder being a test device. For instance, care must be used when
provisioning, such that it is not invoiced in the billing system or mistakenly blocked. Cable operators will want to adapt
the deployment strategy to t their unique operational landscape. The introduction of a new device type in the DOCSIS
network touches several OSS systems and disciplines whose participation is necessary for a successful and timely
deployment.
3.3 Security
Different security methods are used to ensure network integrity. Some common issues are:
A subscriber account (where the transponder is the subscriber) may be required for each transponder
The transponder’s MAC address may have to be pre-loaded into the CMTS
MAC ltering may have to be modied to allow MAC addresses starting with 00:26:97:xx:xx:xx to be registered
For SNMP access, UDP ports 161 and 162 must not be blocked
Firewalls must allow communications between the cable modem and the various servers.
An entry must be added to the DOCSDevNMAccess table to ensure SNMP communications and traps are sent to
the monitoring server from each transponder.
Network Worksheet
Network Item Value
Cable Modem
MAC Address
Cable Modem IP
Address
TFTP Server IP
Address
Provisioning
Server IP Address
Time of Day Server
IP Address
DHCP Server IP
Address
3.0 Installation, continued
14 050-0188, Rev. J (03/2016)
3.4 Cable Modem Conguration File
Alpha Technologies strongly recommends you ensure that the cable modem conguration le has been successfully
modied and tested prior to deploying transponders into the system in quantity. The transponder manages SNMP lters
and trap destinations via the docsDevNmAccessTable.
To ensure the proper management of SNMP access, such as limiting access to certain SNMP managers or allowing
the transponder to send SNMP/HMS traps, the docsDevNmAccessTable must be populated via the cable modem
conguration le.
Additional OIDs may be added to further congure other options such as the transponder’s HTTP port, its username and
password conguration information (see section titled “CMD-N Web Interface”), or its support for telnet server access (see
section titled “Console Access”).
The following is a sample cable modem conguration le. Include only those OIDs that will provide the desired features
and functionality.
Fig. 3-2, Cable Modem Conguration File
3.5 Installing the CMD-N Transponder
The following sections detail installation procedures for installing the CMD-N transponder into the following nodes:
SG4000
MBN100/200
BTN100 modular optical node
VSN1000 node
3.0 Installation, continued
15050-0188, Rev. J (03/2016)
SG4000 Node Installation
1. Remove the transponder from the shipping package. Record the transponder’s MAC address, associated node
number and location information to be entered into the provisioning and monitoring systems.
2. Position the transponder so that the interface connector shown in Fig. 3-3 aligns with the node’s interface
connector shown in Fig. 3-4.
Fig. 3-3, Fiber Node Interface Connector
Fig. 3-4, Slot and Interface Connector
Interface Connector
Fiber Node Interface Connector
Slot
3.0 Installation, continued
16 050-0188, Rev. J (03/2016)
3. Firmly push the transponder down onto the node’s motherboard until the transponder seats into position. Use the
screws provided with the transponder to secure the transponder to the motherboard. The locations of the screw
access holes are shown in Fig. 3-5.
Fig. 3-5, Mounting Screw Access Locations
4. Attach the Forward RF cable (the longer cable) to the appropriate SG4 RF module -20dB test point. Route the
cable(s) appropriately within the node (see Fig. 3-6).
Fig. 3-6, RF Cable Attached to RF Test Points
Screw Holes
Screw Holes
Forward RF Connector to RF Test Point
3.0 Installation, continued
17050-0188, Rev. J (03/2016)
5. Attach the Return (upstream) RF cable (the shorter cable) to the “SM” test point connector on the Return
Conguration board located directly above the receiver optical module in slot 3 or slot 7 (see Fig. 3-7).
Fig. 3-7, RF Cable Attached to SM Test Point
SM Test Point Connector
3.0 Installation, continued
18 050-0188, Rev. J (03/2016)
MBN100/200 Node Installation
1. Remove the transponder from the shipping package. Record the transponder’s MAC address, associated node
number and location information to be entered into the provisioning and monitoring systems.
2. Position the transponder so that the interface connector shown in Fig. 3-8 aligns with the node’s interface
connector shown in Fig. 3-9.
Fig. 3-8, Fiber Node Interface Connector
Fig. 3-9, Slot and Interface Connector
Interface Connector
Fiber Node Interface Connector
Slot
3.0 Installation, continued
19050-0188, Rev. J (03/2016)
3. Firmly push the transponder down onto the node’s motherboard until the transponder seats into position. Use the
screws provided with the transponder to secure the transponder to the motherboard. The locations of the screw
access holes are shown in Fig. 3-10.
Fig. 3-10, Mounting Screw Access Locations
4. Attach the Forward RF cable (the longer cable) to the -20dB Status Monitor Output injection point. Route the
cable(s) appropriately within the node (see Fig. 3-11).
Fig. 3-11, RF Cable Attached to Injection Point
Screw Holes
Screw Holes
Forward RF Connector
to Status Monitor Output
3.0 Installation, continued
20 050-0188, Rev. J (03/2016)
5. Attach the Return (upstream) RF cable (the shorter cable) to the appropriate Transmitter Status Monitor injection
point (see Fig. 3-12).
Fig. 3-12, RF Cable Attached to SM Test Point
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58

Alpha CMD-N Arris SG4000 Technical Manual

Type
Technical Manual

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI