Effective: March 2016 · 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 fiber nodes through an existing

CMD-N Arris SG4000Technical Manual

Effective: March 2016

Safety NotesAlpha 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 specific regulatory/code requirements that may affect the placement of equip-ment and /or installation procedures.

ATTENTION:

NOTICE provides additional information to help complete a specific 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 flammability 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 SG4000Technical Manual050-0188, Rev. J

Effective Date: March 2016© 2016 by Alpha Technologies, Inc.

DisclaimerImages 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 InformationSales information and customer service in USA(7AM to 5PM, Pacific Time):

Complete technical support in USA(7AM to 5PM, Pacific Time or 24/7 emergency support):

Website:

866 944 1482

www.alpha.comwww.cheetahtech.com

412 923 3486

4 050-0188, Rev. J (03/2016)

Table of Contents1.0 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.1 CMD-N Transponder Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3 Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.0 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Connections Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112.3 CMD-N Transponder Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

3.0 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.1 Provisioning the Transponders in the Network . . . . . . . . . . . . . . . . . . . . . . . . 123.2 Your Network Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.4 Cable Modem Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.5 Installing the CMD-N Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

SG4000 Node Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15MBN100/200 Node Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18BTN100 Modular Optical Node Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.6 Transponder Configuration Using the sg4000NodeDiscoveryGroup MIB . . . . . . . . . . 253.7 Viewing and Overriding the BPIM Switch Setting . . . . . . . . . . . . . . . . . . . . . . 263.8 Checking the LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4.0 Provisioning the SNMP Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.1 MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.2 Acquiring the Transponders by the SNMP Manager . . . . . . . . . . . . . . . . . . . . . 29

5.0 Using the Craft Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.2 Web Page Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.3 Console Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

6.0 CMD-N Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346.2 Configuring the SYSNAME and SYSLOCATION OIDs. . . . . . . . . . . . . . . . . . . . 34

Configuration Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Choosing the Appropriate Device Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

6.3 Status Page for Software Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366.4 Status Page for Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 376.5 Status Page for the SNMP Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386.6 HMS Fiber Node Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396.7 HSIA Diagnostics Page: Ping Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Controlling the Ping Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Simultaneous Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

6.8 HSIA Diagnostics Page: Traceroute Command . . . . . . . . . . . . . . . . . . . . . . . 44Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Controlling the Traceroute Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Simultaneous Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5050-0188, Rev. J (03/2016)

6.9 RF Constellation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Downstream Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Interpreting QAM Constellation Data by Visual Inspection . . . . . . . . . . . . . . . . . . 47

6.10 MTA Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526.11 MTA DHCP Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526.12 MTA Quality of Service (QoS) Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536.13 MTA Provisioning Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536.14 MTA Event Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

7.0 Cable Pinout Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557.1 Ethernet Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

8.0 Upgrading the CMD-N Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Table of Contents, Continued

6 050-0188, Rev. J (03/2016)

FiguresFig. 1-1, CMD-N Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Fig. 2-1, CMD-N Transponder Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Fig. 3-1, Typical Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Fig. 3-2, Cable Modem Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Fig. 3-3, Fiber Node Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Fig. 3-4, Slot and Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Fig. 3-5, Mounting Screw Access Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Fig. 3-6, RF Cable Attached to RF Test Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Fig. 3-7, RF Cable Attached to SM Test Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Fig. 3-8, Fiber Node Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Fig. 3-9, Slot and Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Fig. 3-10, Mounting Screw Access Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Fig. 3-11, RF Cable Attached to Injection Point . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Fig. 3-12, RF Cable Attached to SM Test Point . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Fig. 3-13, Fiber Node Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Fig. 3-14, Slot and Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Fig. 3-15, Mounting Screw Access Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Fig. 3-16, RF Cable Attached to RF Test Points . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Fig. 3-17, RF Cable Attached to SM Test Point on the Return Configuration Board . . . . . . . . . 23Fig. 3-18, RF Cable Attached to SM Test Point on Receiver Optical Module . . . . . . . . . . . . 24Fig. 3-19, The CMD-N Transponder LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Fig. 5-1, Console Main Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Fig. 5-2, Console Prompt Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Fig. 5-3, Console HMS Prompt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Fig. 5-4, Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Fig. 6-1, Configuration Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Fig. 6-2, Status Page for Software Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Fig. 6-3, Status Page for Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . 37Fig. 6-4, Status Page for the SNMP Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Fig. 6-5, SG4000 Fiber Node Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Fig. 6-6, MBN200 Fiber Node Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Fig. 6-7, BTN100 Fiber Node Data Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Fig. 6-8, HSIA Diagnostics Page: Ping Command . . . . . . . . . . . . . . . . . . . . . . . . . . 41Fig. 6-9, Ping Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Fig. 6-10, HSIA Diagnostics Page: Traceroute Command . . . . . . . . . . . . . . . . . . . . . . 44Fig. 6-11, Traceroute Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Fig. 6-12, Constellation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Fig. 6-13, Sample QAM Constellation — Normal Centered Dots (Good Sound Quality) . . . . . . 48Fig. 6-14, Sample QAM Constellation — Fuzzy (Low CNR and/or Low MER) . . . . . . . . . . . 48Fig. 6-15, Sample QAM Constellation — “Doughnuts” (Coherent Interference) . . . . . . . . . . . 49Fig. 6-16, Sample QAM Constellation — Gaussian Noise . . . . . . . . . . . . . . . . . . . . . . 49Fig. 6-17, Sample QAM Constellation — Circular Smear (Phase Noise) . . . . . . . . . . . . . . 50Fig. 6-18, Sample QAM Constellation — Corners Squeezed to Center (Gain Compression) . . . . 50Fig. 6-19, Sample QAM Constellation — Rectangular vs. Square (I-Q Imbalance) . . . . . . . . . 51Fig. 6-20, Sample QAM Constellation — Twisted or Skewed (Quadrature Distortion). . . . . . . . 51Fig. 6-21, MTA Status Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Fig. 6-22, MTA DHCP Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Fig. 6-23, MTA Quality of Service (QoS) Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

7050-0188, Rev. J (03/2016)

TablesTable 1-1, CMD-N Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 2-1, Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Table 2-2, CMD-N Transponder Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Table 3-1, Network Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 3-2, Status Monitoring Slot Number Cross Reference. . . . . . . . . . . . . . . . . . . . . 21Table 3-3, LED Status Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Table 4-1, ANSI / SCTE Management Information Base (MIB) Files . . . . . . . . . . . . . . . . 28Table 4-2, Arris Management Information Base (MIB) Files . . . . . . . . . . . . . . . . . . . . . 28Table 5-1, OIDs for Usernames, Passwords, Telnet Access for Console Access . . . . . . . . . . 30Table 5-2, TelnetIpStackInterfaces OID Values and Descriptions . . . . . . . . . . . . . . . . . . 31Table 5-3, Telnet Access Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Table 5-4, Commands Available in the HMS Section of Console Mode . . . . . . . . . . . . . . . 33Table 6-1, OIDs for Port Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Table 6-2, OIDs for Usernames and Passwords for Web Interface Access . . . . . . . . . . . . . 34Table 6-3, Status Monitoring Slot Number Cross Reference. . . . . . . . . . . . . . . . . . . . . 41Table 6-4, Input Parameters for the Ping Command . . . . . . . . . . . . . . . . . . . . . . . . . 41Table 6-5, Control Buttons on the Ping Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Table 6-6, Input Parameters for the Traceroute Command . . . . . . . . . . . . . . . . . . . . . 44Table 6-7, Control Buttons on the Traceroute Screen . . . . . . . . . . . . . . . . . . . . . . . . 45Table 6-8, QAM Constellation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Table 7-1, Pin Number Configuration Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Figures, ContinuedFig. 6-24, MTA Provisioning Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Fig. 6-25, MTA Event Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

8 050-0188, Rev. J (03/2016)

1.0 Introduction1.1 CMD-N Transponder OverviewThe CMD-N transponder provides the ability to manage fiber nodes through an existing cable modem infrastructure. Contact an Alpha Technical Support Representative for a complete listing of supported fiber 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 configure 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 fiber 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 specifications, see Cable Laboratories specifications (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 Configuration Using the sg4000NodeDiscoveryGroup MIB”

NOTICE:

1.0 Introduction, continued

9050-0188, Rev. J (03/2016)

1.2 Parts ListTable 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 InformationFor 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 ListDescription Part Number Quantity

CMD-N Transponder 66900-0665 1

10 050-0188, Rev. J (03/2016)

2.0 Connections2.1 Connections OverviewThe 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 configuration 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 Specifications

Table 2-2, CMD-N Transponder Specifications

Connector SummaryConnector 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 CableThe Return (Upstream) RF cable is the physical connection to the “SM” injection point connector on the Return Configuration 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 SpecificationsParameter Specification

GeneralDOCSIS Version 2.0

HMS Monitoring Protocol SNMP v1DOCSIS Monitoring Protocol SNMP v1, v2, v3

RF Interface InternalRF Internal Padding 18dB Downstream and 15dB UpstreamEthernet Interface RJ45

Operating Temperature –40°C to +75°CHumidity 10% to 90% (non-condensing)EMI/EMC FCC Part 15 Class A, CE EN50022 Class A

RF Transmit/ReceiveTx Frequency Range 5 to 42 MHz

Tx Output Power +8 to +58 dBmVRx Frequency Range 88 MHz to 860 MHz

Rx Input Level –15 to +15 dBmVChannel Bandwidth 6 MHz to 8 MHz

Part NumbersTransponder 66900-0665

12 050-0188, Rev. J (03/2016)

3.0 InstallationCable 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 configuration data to the cable modem configuration file• Installing the transponder• Powering the transponder and checking the LEDs for status

3.1 Provisioning the Transponders in the NetworkBefore 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 Configuration Using the sg4000NodeDiscoveryGroup MIB”

NOTICE:

3.0 Installation, continued

13050-0188, Rev. J (03/2016)

3.2 Your Network InformationThe 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 fit 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 SecurityDifferent 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 filtering may have to be modified 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 WorksheetNetwork Item ValueCable Modem MAC Address

Cable Modem IP Address

TFTP Server IP Address

Provisioning Server IP AddressTime of Day Server

IP AddressDHCP Server IP

Address


14 050-0188, Rev. J (03/2016)

3.4 Cable Modem Configuration FileAlpha Technologies strongly recommends you ensure that the cable modem configuration file has been successfully modified and tested prior to deploying transponders into the system in quantity. The transponder manages SNMP filters 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 configuration file.

Additional OIDs may be added to further configure other options such as the transponder’s HTTP port, its username and password configuration 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 configuration file. Include only those OIDs that will provide the desired features and functionality.

Fig. 3-2, Cable Modem Configuration File

3.5 Installing the CMD-N TransponderThe following sections detail installation procedures for installing the CMD-N transponder into the following nodes:

• SG4000• MBN100/200• BTN100 modular optical node• VSN1000 node


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


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


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 Configuration 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


18 050-0188, Rev. J (03/2016)

MBN100/200 Node Installation





Interface Connector

Fiber Node Interface Connector

Slot


19050-0188, Rev. J (03/2016)



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


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


21050-0188, Rev. J (03/2016)

BTN100 Modular Optical Node Installation

Table 3-2, Status Monitoring Slot Number Cross Reference





The status monitoring index of the receivers and transmitters for the BTN100 match the silk screen slot labeling of the module locations in the node, not the actual module description. The following table displays the status monitoring indexing of the modules and the corresponding silk-screened slot number and module label within the node.

NOTICE:

Status Monitoring Slot Number Cross ReferenceStatus Monitoring Module Name Node Silk Screening Module Identification

Receiver 1 Slot 1 RX2 SecondaryReceiver 2 Slot 2 RX1 Primary

Transmitter 3 Slot 3 TX 2Transmitter 4 Slot 4 TX 1

Interface Connector

BTN100 Fiber Node Interface Connector and Slot


22 050-0188, Rev. J (03/2016)



4. Attach the Forward RF cable (the longer cable) to the appropriate BTN100 monitor point. Route the cable(s) appropriately within the node (see Fig. 3-16).

Fig. 3-16, RF Cable Attached to RF Test Points

Screw HoleScrew Hole


23050-0188, Rev. J (03/2016)

5. Determine the appropriate method for connecting the Return (upstream) RF cable:• Attach the Return (upstream) RF cable (the shorter cable) to the SM test point connector on the Return

Configuration board located to the left of the transmitter optical modules (see Fig. 3-17).

Fig. 3-17, RF Cable Attached to SM Test Point on the Return Configuration Board


24 050-0188, Rev. J (03/2016)

• Attach the Return (upstream) RF cable (the shorter cable) to the SM test point connector on the appropriate transmitter optical module (see Fig. 3-18).

Fig. 3-18, RF Cable Attached to SM Test Point on Receiver Optical Module


25050-0188, Rev. J (03/2016)

3.6 Transponder Configuration Using the sg4000NodeDiscoveryGroup MIBThe CMD-N transponder for the SG4000, MBN100/200, and BTN100 automatically detects the type of node it is installed into as long as there is an EPIM, VPIM, or BPIM in the node to report the node type. If there is no EPIM, VPIM, or BPIM, the transponder operates as if it were installed in an SG4000 node. The discovery code runs at startup, on reset, and every 5 minutes thereafter by default. This behavior can be controlled and overridden via SNMP using the SG4000NodeDiscoveryGroup MIB.

The SG4000NodeDiscoveryGroup OIDs allow the user to enable or disable the node type discovery. If the discovery is disabled, the user then has the ability to manually set the node type. These OIDs can also be used to view if the last discovery attempt was successful or if there was an error during discovery.

The three OIDs used to control discovery are:

• nodeTypeSettings (OID 1.3.6.1.4.1.1166.1.203.3.3.1) – Returns the current node type when read.. Valid values are mbn100(1) mbn200(2) and sg4000(3), and btn100(6). If nodeTypeDiscovery is disabled this OID can be written to with any of the valid values. This forces the transponder to operate in the specified mode. The default mode is SG4000.

• nodeTypeDiscovery (OID 1.3.6.1.4.1.1166.1.203.3.3.2) – Used to enable or disable whether the transponder automatically discovers the type of node it is installed in. Reading returns either enabled(1) or disabled(2). Setting the OID to enabled(1) enables automatic node type discovery. Setting it to disabled(2) disables automatic discovery.

• nodeTypeDiscoveryError (OID 1.3.6.1.4.1.1166.1.203.3.3.2) – Displays the status of the last node type discovery process. • If the nodeTypeDiscoveryError displays success(1), there were no known problems during the discovery

process. Success will be displayed if the nodeTypeDiscovery is set to disabled(2).• If the nodeTypeDiscoveryError displays nodeTypeError(2), there was a problem during the discovery process.

When this occurs the nodeTypeSetting will be set to the default value of sg4000(3).


26 050-0188, Rev. J (03/2016)

3.7 Viewing and Overriding the BPIM Switch SettingIf the Node or Amplifier has a BPIM installed, the A/B switch setting state, dip switch settings, and the module slot locations can be viewed via the web page and can be viewed and/or changed using the sg4000NodeTypeGroup branch of the sg4000ExtensionsMib.

The OIDs used to control these features are:

• nodeManualSwitchSettings – Displays the manual switch A/B switch settings.• switchStateStatic - When in this position, the last switch state will persist.• forcePathPrimary - Forces the AB switch to the optical receiver connected to primary. Any automatic switching

performed by the transponder is disabled.• forcePathSecondary - Forces the AB switch to the optical receiver connected to secondary. Any automatic

switching performed by the transponder is disabled.• Automatic - Automatic switching enabled. Both the primary and secondary are enabled.• nodeForwardConfigSettings – Reports/sets Node forward Configuration Settings. This reflect the switch S5

positions 1(msb) to 5(lsb). This object needs to be reported only if the detected node type is MBN100/MBN200/BTN100/BTN200. Refer to the appropriate MBN100/MBN200/BTN100 manual for current supported forward configuration. The nodeConfig object shall be enabled(1) each time before attempting to write to this table.

• nodeReturnConfigSettings – Reports/sets Node Return Configuration Settings. This reflect the switch S5 positions 6(msb)to 10(lsb). This object needs to be reported only if the detected node type is MBN100/MBN200/BTN100/BTN200. Refer to the appropriate MBN100/MBN200/BTN100 manual for current supported return configuration. The nodeConfig object shall be enabled(1) each time before attempting to write to this table.

• nodeReceiverLocation - Location of the receiver modules in the MBN and BTN nodes. Values of 0,1, and 2 are applicable for the MBN100/200 and values of 0,1,2,3, and 4 for the BTN100. The nodeConfig object shall be enabled(1) each time before attempting to write to this table.

• nodeTransmitterLocation - Location of the transmitter modules in the MBN and BTN nodes. Values of 0,1, and 2 are applicable for the MBN100/200 and values of 0,1,2,3, and 4 for the BTN100. The nodeConfigEnable object shall be enabled (1) each time before attempting to write to this table.

• nodeConfigEnable - A value of enable(1) needs to be written to this object in order for any MBN/BTN node configuration write access. This is a one time write operation and needs to be enabled for each config parameter write. The config parameters are nodeTransmitterLocation, nodeReceiverLocation, NodeForwardConfigSettings, and NodeReturnConfigSettings. Setting a value of configReset(3) shall cause the node to restore the factory default FWD and RTN configuration. Attempt to read this object shall return disable(2).


27050-0188, Rev. J (03/2016)

3.8 Checking the LEDsThe CMD-N transponder includes 6 green LEDs:

• Online • PWR• Elink • DS• Status • US

On initial power up, the LEDs will remain off for several seconds after which time the DS, US, and Online LEDs will blink, in unison, 6 times. After this sequence completes, the LEDs indicate the status. The Power, DS, US, Online, and Elink LEDS conform to the DOCSIS OSSI specification.

Fig. 3-19, The CMD-N Transponder LEDs

Table 3-3, LED Status Summary

LED Status SummaryLED Function State Meaning

PWR Power LED (Note: This LED is not tied directly to line power).

Off The transponder is switched off or is not functioning.On The transponder is on.

DS Indicates status of downstream scanning and synchronization.

Blinking The transponder is scanning for a downstream DOCSIS channel.

On The transponder has locked onto and synchronized with a downstream DOCSIS channel.

US Indicates status of upstream parameters and initial ranging.

Blinking The transponder is obtaining upstream parameters and is performing initial ranging.

On The transponder has completed a successful initial ranging sequence.

Online Indicates status of the completion of the IP initialization process and when the unit is operational.

Blinking The transponder is currently involved in the IP initialization process.

On The transponder has completed the IP initialization process.

ElinkIndicates status of the bridging of data to and from a CPE device connected to the transponder’s Ethernet port.

Off A CPE device is not connected to the transponder’s Ethernet port.

Blinking The transponder is bridging data to/from a CPE device.

StatusIndicates the absence or presence of data transference between the transponder’s two processors.

Off Data is not being transferred between the two processors.

Blinking Data is being transferred between the two processors.

28 050-0188, Rev. J (03/2016)

4.0 Provisioning the SNMP Manager4.1 MIB FilesThe following MIB (Management Information Base) files are required for the SNMP Manager to collect data from the transponder. The files in Table 4-1 can be found on the Society of Cable Telecommunications (SCTE) web site www.scte.org. The files in Table 4-2, as well as the list of additionally supported files on the following page, are provided by Alpha Technologies or Arris. There are dependencies between MIB files, so compile them in the order shown in the following tables.

Table 4-1, ANSI / SCTE Management Information Base (MIB) Files

Table 4-2, Arris Management Information Base (MIB) Files

ANSI / SCTE Management Information Base (MIB) FilesANSI / SCTE # Former HMS # Title

ANSI / SCTE 36 2002 HMS 028 SCTE-ROOT Management Information Base (MIB) Definitions

ANSI / SCTE 37 2003 HMS 072 Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-ROOTS Management Information Base (MIB) Definition

ANSI / SCTE 38-1 2002 HMS 026 Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-PROPERTY-MIB Management Information Base (MIB) Definition

ANSI / SCTE 38-2 2002 HMS 023 Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-ALARMS-MIB Management Information Base (MIB) Definition

ANSI / SCTE 38-3 2002 HMS 024 Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-COMMON-MIB Management Information Base (MIB) Definition

ANSI / SCTE 38-5 2002 HMS 025 Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-FIBERNODE-MIB Management Information Base (MIB) Definition

ANSI / SCTE 38-7 2002 HMS 050 Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-Transponder-Bus(TIB)-MIB Management Information Base (MIB) Definition

Arris Management Information Base (MIB) FilesProvider Title

Arris SG4-OSW MIBArris SG4-OA MIBArris SG4-HMS-EXTENSION-MIB

4.0 Provisioning the SNMP Manager, continued

29050-0188, Rev. J (03/2016)

Below is a list of additionally supported Management Information Base (MIB) Files:

• BRCM-BFC-MGMT-MIB• BRCM-CM-MGMT-MIB• BRCM-EMTA-MGMT-MIB• BRCM-HTTP-MGMT-MIB• BRCM-SNMP-MGMT-MIB• BRCM-SSH-MGMT-MIB• BRCM-TELNET-MGMT-MIB• BRIDGE-MIB• ENTITY-MIB• eSAFE-MIB• EtherLike-MIB• IF-MIB• IGMP-STD-MIB• IP-MIB• RFC1213-MIB• SLED-MIB• SNMPv2-MIB• TOLLGRADE-HTTP-MGMT-MIB• TOLLGRADE-LIGHTHOUSE-HMS-SG4000HMS-MIB (no longer supported)• UDP-MIB• USB-MIB

4.2 Acquiring the Transponders by the SNMP ManagerThe transponder must first complete its initialization/registration from the Cable Modem configuration file. The transponder will then send a warm start trap to the SNMP Manager (as specified in the cable modem configuration file). This trap provides the SNMP Manager with the MAC and IP addresses of the transponder and should, depending on the configuration of the manager software, initiate discovery and monitoring of the fiber node.

The Arris SG4-HMS-EXTENSION-MIB has replaced the functionality previously provided by the TOLLGRADE-LIGHTHOUSE-HMS-SG4000HMS-MIB which is no longer supported.

NOTICE:

30 050-0188, Rev. J (03/2016)

5.0 Using the Craft Port5.1 OverviewThe Craft port on the transponder will typically be used as a local connection point allowing the user to connect directly to the unit. However, the Craft port is a fully functional standard Ethernet port capable of providing all the functionality of any standard Ethernet connection.

When utilizing a local (direct) connection to the transponder, the technician has the option of either communicating with the transponder via a web browser interface or telnet console session. Both connection processes are discussed in the sections that follow. Please refer to the section titled “CMD-N Web Interface” for more detailed information on using the transponder’s web interface. It is also important to note that console access is intended for use by factory trained technicians and is not recommended for use by technicians in the field.

5.2 Web Page AccessTo access the transponder locally utilizing a Web browser, follow the procedure outlined below.

1. Connect a standard CAT5 Ethernet cable between the transponder and a laptop or similar device.2. Open a Web browser.3. Enter the 192.168.100.1 into the browser’s URL bar. Press Enter.4. Refer to the section titled “CMD-N Web Interface” for more detailed information.

5.3 Console Access

By default, access to the ETHERNET port is enabled and the CM interface is disabled. If the use of the CM interface is desired, the operator must first enable the interface by setting the telnetIpStackInterfaces OID to the appropriate value (refer to Table 5-1). In addition, the default username and password may be altered if desired.

Table 5-1 contains a list of the OIDs in the telnetMgmt MIB that are used to change the username or password for the interfaces, enable/disable the interfaces, and enable/disable telnet server access. Table 5-2 contains a list of the values for the telnetIpStackInterfaces OID along with the definition of each value. Table 5-3 provides a matrix describing the settings of the different access options. Change these values as deemed necessary.

Table 5-1, OIDs for Usernames, Passwords, Telnet Access for Console Access

Console access is intended for use by factory trained technicians and is not recommended for use by technicians in the field.

NOTICE:

Any local (direct) craft connection is subject to the DOCSIS cable modem configuration. And any method used for connection must be supported in the cable modem configuration file.

NOTICE:

OIDs for Usernames, Passwords, Telnet Access for Console AccessParameter OID Default

telnetIpStackInterfaces 1.3.6.1.4.1.4413.2.2.2.1.1.1.1.00x40 (hex)

(CM interface is disabled and the ETHERNET port interface is enabled)

telnetUserName 1.3.6.1.4.1.4413.2.2.2.1.1.1.2.0 cheetahtelnetPassword 1.3.6.1.4.1.4413.2.2.2.1.1.1.3.0 cheetah

telnetServerControl 1.3.6.1.4.1.4413.2.2.2.1.1.1.4.0 1 (enabled)

5.0 Using the Craft Port, continued

31050-0188, Rev. J (03/2016)

Table 5-2, TelnetIpStackInterfaces OID Values and Descriptions

Table 5-3, Telnet Access Matrix

To access the transponder locally utilizing the console via a telnet connection, follow the procedure outlined below.

1. Verify that software capable of supporting a standard telnet communications session is present and operational on the laptop or similar device being used to communicate with the transponder.

2. Connect a standard CAT5 Ethernet cable between the transponder and a laptop or similar device.3. Using your telnet client software and IP address 192.168.100.1, establish a telnet session to the transponder. The

following screen will appear.

TelnetIpStackInterfaces OID Values and DescriptionsValue in Hexadecimal Setting

0xC0 CM Interface enabled and Craft port Interface enabled.0x80 CM Interface enabled and Craft port Interface disabled.0x40 CM Interface disabled and Craft port Interface enabled.0x00 CM Interface disabled and Craft port Interface disabled.

Telnet Access MatrixtelnetServerControl OID

ValuetelnetIpStackInterfaces

OID Value (hex) Result

0 0x00 Telnet access is disabled and both interfaces are disabled.1 0x00 Telnet access is enabled and both interfaces are disabled.

1 0x40 Telnet access is enabled, the CM interface is disabled, and the Craft port interface is enabled.

1 0x80 Telnet access is enabled, the CM interface is enabled, and the Craft port interface is disabled.

1 0xC0 Telnet access is enabled, the CM interface is enabled, and the Craft port interface is enabled.

If the transponder is having difficult establishing communications, try changing the laptop’s IP address value to 192.168.100.2 and its subnet mask value to 255.255.255.0.

NOTICE:


32 050-0188, Rev. J (03/2016)

Fig. 5-1, Console Main Page

4. Press the Enter key. At the login prompt enter the appropriate UserName (the default is cheetah) and press the Enter key. Next, enter the appropriate PassWord (the default is cheetah) and press the Enter key. The following screen will appear.

Fig. 5-2, Console Prompt Page

Console mode supports a number of commands that are used for troubleshooting and debugging purposes. Providing a list and description all of the available commands would exceed the scope of this manual. Therefore, the commands described in this section will be those found in the hms directory. For additional information about the use of the console commands please contact an Alpha Technical Support representative at 1-866-944-1482.

On the following page, Table 5-4 provides a list the commands in the hms section available via console mode along with a brief description of each command.

NOTICE:


33050-0188, Rev. J (03/2016)

Table 5-4, Commands Available in the HMS Section of Console Mode

5. To switch to the hms section, type cd hms at the prompt and press Enter. The following screen appears:

Fig. 5-3, Console HMS Prompt

6. To display a listing of all of the available commands, type ? and press Enter.

Fig. 5-4, Console Commands

7. To display the proper syntax for a particular command, type the command followed by ? and press Enter.8. When the session is complete, type “exit” to terminate the telnet session, and then close the telnet dialog box.

Commands Available in the HMS Section of Console ModeCommand Description

devices Displays the modules that have been discovered in the Fiber Node.dumps Toggles the serial dump feature on and off.images Displays the firmware image information.rawio Displays the raw input and output values from the transponder’s two processors.smio Displays the status monitoring IO values.

spidump Toggles the spidump feature on and off. The spidump data consists of the communications information between the two processors.

spistats Displays the SPI statistics.status Displays the general transponder information (i.e., firmware version, IP addresses, etc.)/

34 050-0188, Rev. J (03/2016)

6.0 CMD-N Web Interface6.1 OverviewA web interface is available on the CMD-N transponder. The default port for HTTP traffic is port 80, but can be configured to use other ports via the Alpha Technologies httpMgmt MIB. HTTP port configuration is available for the cable modem interface (via the cable modem IP address) and the CPE interface (via the Craft connection). Setting the value to zero (0) will shutdown access to the HTTP server for the given interface. The specific OIDs and their default values are listed in the following table. The port must be open in order to use all of the features described here. The interface can be accessed by typing the cable modem IP address of the transponder into your web browser. The interface includes status data for the cable modem, the HMS transponder, and the High Speed Internet Access (HSIA) diagnostics.

Table 6-1, OIDs for Port Management

6.2 Configuring the SYSNAME and SYSLOCATION OIDsIt is also possible to configure the sysName (1.3.6.1.2.1.1.5.0) and sysLocation (1.3.6.1.2.1.1.6.0) OIDs from the web interface. This feature is password protected. There are both Admin and User usernames and passwords. Both usernames (Admin and User) have the authority to set sysName and sysLocation. The passwords can be changed via the Broadcom httpMgmt MIB. The specific OIDs and default values are shown below.

Table 6-2, OIDs for Usernames and Passwords for Web Interface Access

OIDs for Port ManagementParameter OID Default

httpCMMgmtPort 1.3.6.1.4.1.2082.5.5.1.1.1.0 80httpCPEMgmtPort 1.3.6.1.4.1.2082.5.5.1.1.2.0 80

httpCPU2MgmtPort* 1.3.6.1.4.1.2082.5.5.1.1.3.0 8008*This parameter is not applicable to this transponder

OIDs for Usernames and Passwords for Web Interface AccessParameter OID Default

httpAdminId 1.3.6.1.4.1.4413.2.2.2.1.1.3.1.0 adminhttpAdminPassword 1.3.6.1.4.1.4413.2.2.2.1.1.3.2.0 cheetah

httpUserId 1.3.6.1.4.1.4413.2.2.2.1.1.3.3.0 cheetahhttpUserPassword 1.3.6.1.4.1.4413.2.2.2.1.1.3.4.0 cheetah

None of the pages automatically refresh, so the user must manually refresh each page in order to view the most current data.

NOTICE:

6.0 CMD-N Web Interface, continued

35050-0188, Rev. J (03/2016)

Configuration Data Page

This page allows for setting sysName, and sysLocation. A login dialog will appear when the apply button is clicked. The Device Type and the value(s) in the Device field are determined based on several factors relevant to your specific application. Selecting the appropriate Device Type is discussed in the next section.

Fig. 6-1, Configuration Data Page

Choosing the Appropriate Device Type

Choosing the appropriate device type is necessary to ensure the device is properly controlled and monitored.

• Motorola Node• Motorola Node Dual IP


36 050-0188, Rev. J (03/2016)

6.3 Status Page for Software InformationSelect the Status tab to view details on the software running in the cable modem.

Fig. 6-2, Status Page for Software Information


37050-0188, Rev. J (03/2016)

6.4 Status Page for Connection InformationClick the Connection button to see detailed status information related to the current connection to the CMTS.

Fig. 6-3, Status Page for Connection Information

• The downstream RF connection has 18dB of internal padding which has an impact on the downstream power reading.

• The transponder output is limited to a maximum of 40dBmV at the transponder RF connector so as to not exceed the manufacturer’s specifications. This is accomplished through a 15 dB pad in the Upstream RF path within the transponder. It is possible for the transmit power reading on the web page to exceed 40dBmV by a significant margin if the transponder cannot reach the CMTS requested transmit level. This high reading on the web page has no adverse impact on operation of either the transponder or the node. As the CMTS requests the transponder to transmit at a level beyond its capacity, the web page display can show a slowly increasing power level up to the maximum DOCSIS level for that particular transmit mode and modulation type. Even though the level reading on the web page is high, the transponder output is still limited to 40dBmV. This condition can occur where the Upstream attenuation between the node and CMTS is significant. Under normal conditions, the web page display and actual RF output level are the same.

NOTICE:


38 050-0188, Rev. J (03/2016)

6.5 Status Page for the SNMP Event LogClick the Event Log button to view recent event log entries.

Fig. 6-4, Status Page for the SNMP Event Log

To clear the Event Log click the Clear Log button.


39050-0188, Rev. J (03/2016)

6.6 HMS Fiber Node Data PageSelect the HMS tab to view HMS fiber node data. The help button refers to a web page at the Alpha Technologies web site. Click on a link to view the parameters associated with that particular module or click the View All link to view all of the parameters at once.

The color of each module indicates the highest level of alarm present in that module at the time. Clicking on the module displays the parameter(s) responsible for the alarm(s). The following is a list of the module colors and their meanings:

• Dark Gray: The module is not present in the node.• Green: The module has no alarms.• Yellow: The module has at least one parameter in the minor alarm state.• Red: The module has at least one parameter in the major alarm state.

Fig. 6-5, SG4000 Fiber Node Data Page


40 050-0188, Rev. J (03/2016)

Fig. 6-6, MBN200 Fiber Node Data Page

Fig. 6-7, BTN100 Fiber Node Data Pages

The status monitoring index of the receivers and transmitters for the BTN100 match the silk screen slot labeling of the module locations in the node, not the actual module description. The following table displays the status monitoring indexing of the modules and the corresponding silk screened slot number and module label within the node.

NOTICE:


41050-0188, Rev. J (03/2016)

Table 6-3, Status Monitoring Slot Number Cross Reference

6.7 HSIA Diagnostics Page: Ping CommandSelect the HSIA tab to view high speed internet access diagnostics. The HSIA-Ping Web Interface is accessed from the Connection form that is first displayed when the transponder is accessed.

Fig. 6-8, HSIA Diagnostics Page: Ping Command

Input Parameters

Table 6-4, Input Parameters for the Ping Command

Status Monitoring Slot Number Cross ReferenceStatus Monitoring Module Name Node Silk Screening Module Identification

Receiver 1 Slot 1 RX2 SecondaryReceiver 2 Slot 2 RX1 Primary

Transmitter 3 Slot 3 TX 2Transmitter 4 Slot 4 TX 1

Input Parameters for the Ping CommandInput Parameter Description

Target IP Address or Name

Either a standard IPv4 dotted-quad address is entered,FQDN, or a host name. The address entered will be unconditionally given to the DNS resolver; a dotted-quad will be resolved the same value, and a name will be resolved to its IPv4 address. The final IPv4 address to be pinged is shown in parenthesis beside the host field.

Source of Ping A maximum of 2 choices, depending on the unit: Cable Modem and CPE.Number of Pings Range 1 to 100.Ping Size Range 64 to 1518. (64 is the standard)Timeout Range 1 to 60 seconds. (5 seconds is the standard)


42 050-0188, Rev. J (03/2016)

Controlling the Ping Test

The Ping Test is controlled by the following buttons.

Table 6-5, Control Buttons on the Ping Screen

Control Buttons on the Ping ScreenButton Description

Start Test

Starts the ping test. Each of the values provided in the input fields is evaluated for validity:

• If the hose name field is blank, the test will not proceed (the exception is leaving it, when a previous name had been entered. That name will be used).

• Range checking on the parameters. Any parameter out of range will be ignored, and the default value used.

Any issues with the parameters will be displayed at the top of the results box.

When the test is started, the web page will begin to automatically refresh. Also, a message will be displayed

Ping in use from <source>; pkings xxx; sizy yyy; timeout zzz seconds

indicating the parameters actually in use. This message is also in the text box.Abort Test Stops any ping test currently in progress.Clear Results Clears the results window.


43050-0188, Rev. J (03/2016)

Test Results

Below the test control buttons is a text area that displays the results of the ping test. Any issues with the parameters will be displayed at the top of the results box. During a test, the web page will automatically refresh to show the current results. This refresh stops once the test is completed.

The results area permits the user to select results and copy them for pasting into another program. This is accessed by standard web browser methods; either left-clicking in the box, and pressing CTRL-A (select all), or right-clicking in the box and clicking “Select all”, OR by simply using the mouse cursor, and selecting those lines of interest. Copy is done via standard commands used on the system in question (e.g., under Windows, use CTRL-C to copy). The figure below shows a typical set of Ping results.

Fig. 6-9, Ping Results

Simultaneous Access

Access by more than one user is possible; however, only a single test can be run at a time. When the “Ping in use” message is displayed (see the section titled “Controlling the Ping Test”), no other test can be started. Through the use of a temporary cookie, only the original user can abort an active test.


44 050-0188, Rev. J (03/2016)

6.8 HSIA Diagnostics Page: Traceroute CommandClick the Traceroute button to view the traceroute diagnostics page. The HSIA-Traceroute Web Interface is accessed from the Connection form that is first displayed when the transponder is accessed.

Fig. 6-10, HSIA Diagnostics Page: Traceroute Command

Input Parameters

Table 6-6, Input Parameters for the Traceroute Command

Input Parameters for the Traceroute CommandInput Parameter Description

Target IP Address or Name

Either a standard IPv4 dotted-quad address is entered, FQDN, or a host name. The address entered will be unconditionally given to the DNS resolver; a dotted-quad will be resolved the same value, and a name will be resolved to its IPv4 address. The final IPv4 address to be tracerouted is shown in parenthesis beside the host field.

Source of Traceroute A maximum of 2 choices, depending on the unit: Cable Modem and CPE.Max Hopes Range 1 to 255; default is 30. Also known as Max TTL (Maximum Time-to-Live).

Traceroute Size Range 0 to 1518. 0 is the standard size, resulting in packets of 40 bytes (inclusive of all overhead).

Port Port to use. Standard is 33434 as the initial port.


45050-0188, Rev. J (03/2016)

Controlling the Traceroute Test

The Traceroute Test is controlled by the following buttons.

Table 6-7, Control Buttons on the Traceroute Screen

Test Results

Below the test control buttons is a text area that displays the results of the Traceroute test. Any issues with the parameters will be displayed at the top of the results box. During a test, the web page will automatically refresh to show the current results. This refresh stops once the test is completed.

The results area permits the user to select results and copy them for pasting into another program. This is accessed by standard web browser methods; either left-clicking in the box, and pressing CTRL-A (select all), or right-clicking in the box and clicking “Select all”, OR by simply using the mouse cursor, and selecting those lines of interest. Copy is done via standard commands used on the system in question (e.g., under Windows, use CTRL-C to copy.)

The figure below shows a typical set of Traceroute results.

Fig. 6-11, Traceroute Results

Control Buttons on the Traceroute ScreenButton Description

Start Test

Starts the Traceroute test. Each of the values provided in the input fields is evaluated for validity:

• If the hose name field is blank, the test will not proceed (the exception is leaving it, when a previous name had been entered. That name will be used).

• Range checking on the parameters. Any parameter out of range will be ignored, and the default value used.

Any issues with the parameters will be displayed at the top of the results box.

When the test is started, the web page will begin to automatically refresh. Also, a message will be displayed

Traceroute in use from <source>; max TTL xxx; size yyy; port nnnn

indicating the parameters actually in use. This message is also in the text box.Abort Test Stops any traceroute test currently in progress.Clear Results Clears the results window.


46 050-0188, Rev. J (03/2016)

Simultaneous Access

Access by more than one user is possible; however, only a single test can be run at a time. When the “Traceroute in use” message is displayed (see the section titled “Controlling the Traceroute Test”), no other test can be started. Through the use of a temporary cookie, only the original user can abort an active test.

6.9 RF Constellation PageSelect the RF tab to access the Constellation page. The QAM constellation map is useful in diagnosing line problems that might otherwise go undiagnosed. This section provides useful information on how to interpret the information presented in the QAM map. The interface consists of a panel of variables and the constellation map itself. At the device level, the QAM functionality is only supported by Alpha Technologies products that are based on the ECMM technology.

Fig. 6-12, Constellation Page


47050-0188, Rev. J (03/2016)

Controls

• Run — Start the sampling of data by pushing the Run button. The unit will acquire 100 samples and than stop.• Stop — Use the Stop button to end the sampling.

Downstream Data

• Frequency — is the downstream frequency given in MHz.• Power — is the downstream DOCSIS communications channel power given in dBmV.• SNR / (RxMER) — this is the downstream signal quality. Modulation Error Ratio (SNR)• EVM — Error Vector Magnitude, calculated from MER.• CER Interval — Codeword Error Rate (CER) refresh rate in seconds.• Pre FEC CER — Codeword error rate (CER) BEFORE forward error correction is applied.• Post FEC CER — Codeword error rate (CER) AFTER forward error correction is applied.• Updates Remaining — this is the number of sample updates remaining for this session.

Interpreting QAM Constellation Data by Visual Inspection

The usefulness of the QAM constellation comes in the ability to recognize common shapes and configurations within the map. Examples of the data shown in the table below are illustrated in the figures that follow.

Table 6-8, QAM Constellation Data

QAM Constellation DataShape Focus Impairment Description

Individual cells and entire QAM constellation

Normal Dots are centered in the individual QAM quadrants. The QAM constellation has a uniform square shape.

Individual cells Low CNR and/or Low MER Individual cells of QAM constellation contain a fuzzy and diffused pattern.

Individual cells Coherent Interference

Individual cells of QAM constellation contain diffused hollow circles or “doughnuts”. This indicates an interfering carrier and shows the effect of not allowing the carrier to ever reach the proper point in the target range.

Individual cells Gaussian Noise

Individual cells contain a complete and fairly uniform smear up to all decision boundaries, and is usually caused by improper system setup, too many amplifiers in a cascade, damaged/overheated hardware, and/or low power.

Entire QAM Constellation Phase Noise QAM constellation consists of smeared, concentric, circular patterns.

Entire QAM Constellation

Gain Compression

QAM constellation looks uniformly square, but the outside corners appear to be “smashed” toward center of grid (compression in the RF plant).


I-Q Imbalance in the Modulator

Overall appearance of QAM constellation is rectangular rather than the desired square shape (square inequality).


Quadrature Distortion

Overall appearance of QAM constellation has a twisted or skewed parallelogram shape.


48 050-0188, Rev. J (03/2016)

Fig. 6-13, Sample QAM Constellation — Normal Centered Dots (Good Sound Quality)

Fig. 6-14, Sample QAM Constellation — Fuzzy (Low CNR and/or Low MER)


49050-0188, Rev. J (03/2016)

Fig. 6-15, Sample QAM Constellation — “Doughnuts” (Coherent Interference)

Fig. 6-16, Sample QAM Constellation — Gaussian Noise


50 050-0188, Rev. J (03/2016)

Fig. 6-17, Sample QAM Constellation — Circular Smear (Phase Noise)

Fig. 6-18, Sample QAM Constellation — Corners Squeezed to Center (Gain Compression)


51050-0188, Rev. J (03/2016)

Fig. 6-19, Sample QAM Constellation — Rectangular vs. Square (I-Q Imbalance)

Fig. 6-20, Sample QAM Constellation — Twisted or Skewed (Quadrature Distortion)


52 050-0188, Rev. J (03/2016)

6.10 MTA Status PageSelect the MTA tab to view the MTA status via the Status, DHCP, QoS, Provisioning, and Event Log buttons. The Status page provides information related to the initialization status of the MTA.

Fig. 6-21, MTA Status Page

6.11 MTA DHCP PageClick the DHCP button to view the Dynamic Host Communications Protocol (DHCP) information.

Fig. 6-22, MTA DHCP Page


53050-0188, Rev. J (03/2016)

6.12 MTA Quality of Service (QoS) PageClick the QoS button to view the Quality of Service (Qos) parameters.

Fig. 6-23, MTA Quality of Service (QoS) Page

6.13 MTA Provisioning PageClick the Provisoning button to view the MTA provisioning details.

Fig. 6-24, MTA Provisioning Page


54 050-0188, Rev. J (03/2016)

6.14 MTA Event Log PageClick the Event Log button to view the MTA Event Log information.

Fig. 6-25, MTA Event Log Page

55050-0188, Rev. J (03/2016)

7.0 Cable Pinout Details7.1 Ethernet CableThe following table is the pin number configuration chart for the Ethernet cable.

Table 7-1, Pin Number Configuration Chart

Pin Number Configuration ChartPin Name1 Transmit +2 Transmit -3 Receive +4 Unused5 Unused6 Receive -7 Unused8 Unused

56 050-0188, Rev. J (03/2016)

8.0 Upgrading the CMD-N FirmwareThe firmware in the CMD-N transponder can be upgraded in the same fashion as any other DOCSIS-compliant cable modem. Alpha only supports signed firmware downloads that require the appropriate manufacturer or co-signed CVC to be included in the cable modem configuration file. Consult with Alpha Technical Support for more information.

Alpha Technologies Alpha reserves the right to change specifications without notice.Alpha is a registered trademark of Alpha Technologies.

For more information visit www.alpha.com

© 2016 Alpha Technologies Inc. All Rights Reserved.

050-0188, Rev. J (03/2016)

Worldwide Corporate Offices

North AmericaTel: +1 360 647 2360Fax: +1 360 671 4936

EuropeTel: +49 9122 79889 0Fax: +49 9122 79889 21

Latin AmericaTel: +561 792.9651Fax: +561 792.7157

Asia PacificTel: +852 2736.8663Fax: +852 2199.7988

Documents

Effective: March 2016 · 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 fiber nodes through an existing