Effective: May 2016 - Alpha Technologies Broadbandbroadband.alpha.com/.../cmd_n_cisco_gs_7000/018345B0.pdf · Safety Notes Alpha considers customer safety and satisfaction its most

CMD-N GS7000Technical Manual

Effective: May 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 installa-tion 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

3018-345-B0-001, Rev. A (05/2016)

CMD-N GS7000Technical Manual018-345-B0-001 Rev. A

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

DisclaimerImages contained in this manual are for illustrative purposes only. These images may not match every 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, contact Alpha Technologies or the 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.com

412 923 3486

4 018-345-B0-001, Rev. A (05/2016)

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

1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.4 Technical Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2.0 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112.2 Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3 CMD-N Transponder Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13RF Transmit/Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.0 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.1 Provisioning the Transponders in the Network . . . . . . . . . . . . . . . . . . . . . . . . 143.2 Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.4 Cable Modem Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.5 Installing the CMD-N Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

GS7000 Node Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 GHz GS7000 Non-Redundant Node Installation . . . . . . . . . . . . . . . . . . . . . . 22GS7000 Optical Hub Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.6 Configuring the Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31SA-HMS-FIBERNODEGS7000-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.7 Module Firmware Download Using the CHEETAH-MGMT-UPDATE-MIB . . . . . . . . . . 333.8 Checking the LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.0 Provisioning the SNMP Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.1 MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.2 Acquiring the Transponders by the SNMP Manager . . . . . . . . . . . . . . . . . . . . . 39

5.0 Using the Craft Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.2 Web Page Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.3 Console Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5018-345-B0-001, Rev. A (05/2016)

6.0 CMD-N Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456.2 Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466.3 Web Page Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46System Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Hardware Diagram Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48HFC Node Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49System Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51DOCSIS Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Alarms Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Modem Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Constellation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

6.4 Configuring the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61General Node Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Node Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Other Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

6.5 Configuring the Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657.0 Cable Pinout Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

7.1 Ethernet Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678.0 Upgrading the CMD-N Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Table of Contents

6 018-345-B0-001, Rev. A (05/2016)

FiguresFig. 1-1, The CMD-N Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Fig. 2-1, CMD-N Transponder Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Fig. 2-2, CMD-N Transponder Upstream Pad Location . . . . . . . . . . . . . . . . . . . . . . . 12Fig. 3-1, A Typical Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Fig. 3-2, Cable Modem Configuration File Example . . . . . . . . . . . . . . . . . . . . . . . . . 16Fig. 3-3, Upstream Pad Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Fig. 3-4, Fiber Node Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Fig. 3-5, Fiber Node Transponder Slot and Interface Connector . . . . . . . . . . . . . . . . . . 18Fig. 3-6, Transponder Mounting Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . . 19Fig. 3-7, Transponder RF1 Cable Attachment Points . . . . . . . . . . . . . . . . . . . . . . . . 20Fig. 3-8, Transponder RF2 Cable Attachment Points . . . . . . . . . . . . . . . . . . . . . . . . 21Fig. 3-9, Completed Transponder Installation in the Node . . . . . . . . . . . . . . . . . . . . . . 21Fig. 3-10, Transponder with Return Path Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Fig. 3-11, Pad Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Fig. 3-12, Pad Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Fig. 3-13, Fiber Node Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Fig. 3-14, Fiber Node Transponder Slot and Interface Connector . . . . . . . . . . . . . . . . . . 24Fig. 3-15, Transponder Mounting Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . 25Fig. 3-16, Return Path Cable Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Fig. 3-17, RF1 to Optical Receiver 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Fig. 3-18, RF2 to Optical Receiver 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Fig. 3-19, Completed Transponder Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Fig. 3-20, Upstream Pad Socket with Proper 0 dB Pad Installed . . . . . . . . . . . . . . . . . . 29Fig. 3-21, Optical Hub Interface Connector on CMD-N . . . . . . . . . . . . . . . . . . . . . . . 30Fig. 3-22, Optical Hub Transponder Slot and Interface Connector . . . . . . . . . . . . . . . . . 30Fig. 3-23, Transponder Mounting Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . 31Fig. 3-24, Update Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Fig. 3-25, The CMD-N Transponder LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Fig. 5-1, Console Main Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Fig. 5-2, Console Prompt Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Fig. 5-3, Console Device Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Fig. 5-4, Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Fig. 6-1, GS7000 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Fig. 6-2, Log in via GS7000 Home Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Fig. 6-3, GS7000 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Fig. 6-4, System Link, Navigation Pane, GS7000 Home Page . . . . . . . . . . . . . . . . . . . 47Fig. 6-5, Hardware Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Fig. 6-6, HFC Node Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Fig. 6-7, Alarm Settings Popup Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Fig. 6-8, System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Fig. 6-9, DOCSIS Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Fig. 6-10, Limit Properties, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Fig. 6-11, Discrete Properties, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Fig. 6-12, Modem Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Fig. 6-13, Constellation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

7018-345-B0-001, Rev. A (05/2016)

TablesTable 1-1, CMD-N Package Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 1-2, Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 1-3, Technical Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . 10Table 2-1, Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Table 3-1, Network Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Table 3-2, SA-HMS-FIBERNODEGS7000-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table 3-3, LED Status Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Table 4-1, Management Information Base (MIB) Files . . . . . . . . . . . . . . . . . . . . . . . . 37Table 4-2, Management Information Base (MIB) Files . . . . . . . . . . . . . . . . . . . . . . . . 37Table 4-3, Additional Supported Management Information Base (MIB) Files . . . . . . . . . . . . 38Table 4-4, High-resolution optical power in ATI-DEV-HFC-NODES-MIB. . . . . . . . . . . . . . . 38Table 5-1, OIDs for Usernames, Passwords, Telnet Access for Console Access . . . . . . . . . . 41Table 5-2, TelnetIpStackInterfaces OID Values and Descriptions . . . . . . . . . . . . . . . . . . 42Table 5-3, Telnet Access Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Table 5-4, Commands Available in the Device Section of Console Mode . . . . . . . . . . . . . . 43Table 6-1, Alarm Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Table 6-2, Downstream Table Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Table 6-3, QAM Constellation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Table 6-4, Node Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Table 6-5, OIDs for Port Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Table 6-6, OIDs for Usernames and Passwords for Web Interface Access . . . . . . . . . . . . . 65Table 6-7, ATI-MGMT-SYS-HTTP-LOGINS-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Table 7-1, Pin Number Configuration Chart for the Ethernet Cable . . . . . . . . . . . . . . . . . 67

Fig. 6-14, Normal Centered Dots (Good Sound Quality). . . . . . . . . . . . . . . . . . . . . . . 58Fig. 6-15, Fuzzy (Low CNR and/or Low MER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Fig. 6-16, Circular Smear (Phase Noise). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Fig. 6-17, Corners Squeezed to Center (Gain Compression) . . . . . . . . . . . . . . . . . . . . 59Fig. 6-18, Rectangular vs. Square (I-Q Imbalance) . . . . . . . . . . . . . . . . . . . . . . . . . 60Fig. 6-19, Twisted or Skewed (Quadrature Distortion) . . . . . . . . . . . . . . . . . . . . . . . . 60Fig. 6-20, GS7000 Hardware Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Fig. 6-21, Configuring Module Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Fig. 6-22, System Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Figures

8 018-345-B0-001, Rev. A (05/2016)

1.0 Introduction1.1 OverviewThe CMD-N transponder provides the ability to manage fiber nodes and optical hubs through an existing cable modem infrastructure. Contact an Alpha Technologies 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.

Fig. 1-1, The CMD-N Transponder

The CMD-N transponder:

• Uses ANSI/SCTE HMS standards• Measures analog values and digital states or receives digital SCTE/HMS data from fiber nodes• Can be network managed through the existing CMTS. • Allows remote control and configuration of the node. • Can provide a remote upgrade of node module firmware.

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.

1.0 Introduction, continued

9018-345-B0-001, Rev. A (05/2016)

CMD-N Package Parts ListDescription Part Number Qty

CMD-N Cisco GS7000, 1.2GHz 018-345-20 1CMD-N Cisco GS7000, 1GHz 66900-0722 1Optional GS7000 RF Cable Kit (required for 1GHz nodes with cable modem downstream frequencies above 140MHz; not required for optical hubs)

66905-0340 1

Optional non-redundant upstream cable (required for 1Ghz nodes with segmented upstream paths) 66900-1205 1

0 dB pad N/A 110 dB pad N/A 1

Revision History - P/N 050-0201Version Date Description of Changes and New Features

A 6 / 2009 Initial Release of DocumentB 1 / 2010 Formatting and Graphic UpdatesC 9 / 2010 Added Support for Cisco’s Optical HubD 3 / 2015 Formatting, Section 3.7 MIB Update, Other Minor Section Changes

1.2 Parts ListTable 1-1 lists the transponder and any other items that may be available as options. For damage or discrepancies, please contact an Alpha Technologies representative.

Table 1-1, CMD-N Package Parts List

1.3 Revision HistoryThis section contains revision tracking information such as document version, release date, and descriptions of changes and new features.

Revision History - 018-345-B0Version Date Description of Changes and New Features

A 05/2016 Initial Release of Document under new part number, updating of transponder and node models and firmware revision.

Table 1-2, Revision History

1.0 Introduction, continued

10 018-345-B0-001, Rev. A (05/2016)

1.4 Technical Support Contact InformationFor technical issues, Cisco customers should call the following Cisco Technical Support and Customer Service Numbers.

Technical Support Contact InformationRegion Centers Telephone and Fax Numbers

North America Atlanta, Georgia

Technical Support Customer Service

Toll-Free: 1-800-722-2009Toll-Free: 1-800-722-2009Local: 678-277-1120 (Press 3 at the prompt)

Local: 678-277-1120Fax: 770-236-5477Email: [email protected]

Europe, Middle East, Africa Belgium

Technical Support Customer ServiceTelephone #1: 32-56-445-197 Telephone: 32-56-445-444Telephone #2: 32-56-445-155 Fax: 32-56-445-051Fax: 32-56-445-061 Email: [email protected]

Japan JapanTelephone #1: 81-3-5908-2153Telephone #2: +81-3-5908-2154Fax: 81-3-5908-2155

Korea KoreaTelphone: 82-2-3429-8800Fax: 82-2-3452-9748Email: [email protected]

China (mainland) ChinaTelephone: 82-2-3429-8800Fax: 82-2-3452-9748Email: [email protected]

All other Asia Pacific countries & Australia Hong Kong

Telephone: 852-2588-4746Fax: 852-2588-3139Email: [email protected]

Brazil Brazil

Telephone: 11-55-08-9999Fax: 11-55-08-9998Email #1: [email protected] #2: [email protected]

Mexico, Central America, Carribean Mexico

Technical Support Customer ServiceTelephone: 52-351512599 Telephone: 52-55-50-81-8425

Fax: 52-3515152599Fax: 52-55-52-61-0893Email: [email protected]

All other Latin America countries Argentina

Technical Support Customer ServiceTelephone: 54-23-20-403340 ext: 109

Telephone: 770236-5662Fax: 770-236-5888

Fax: 54-23-20-403340 ext: 103 Email: [email protected]

Table 1-3, Technical Support Contact Information

11018-345-B0-001, Rev. A (05/2016)

2.0 Connections2.1 OverviewThe CMD-N transponder includes six status LEDs, the Craft port (which is a standard RJ-45 Ethernet connector), an optical tamper sensor, and a node interface connector. The transponder receives its power and performs communications all via the node interface connector. The transponder also has a pad socket to attenuate the upstream signal from the transponder. This is so the transponder can be configured for different implementations. If the transponder is to be used in a GS7000 node then the 10 dB pad must be used. If the transponder is to be used in a GS7000 Optical Hub then the 0 dB pad must be used. The locations of these components are shown in Fig. 2-1 and Fig. 2-2.

Fig. 2-1, CMD-N Transponder Connections

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

NOTICE:

Interface Connector

Tamper Sensor

Craft Port

LEDs

Downstream RF Cable Connectors

Label with Transponder Serial Number

2.0 Connections, continued

12 018-345-B0-001, Rev. A (05/2016)

Fig. 2-2, CMD-N Transponder Upstream Pad Location

Upstream Pad Socket with

Pad Installed

Connector SummaryConnector Description

DS RF1 CABLE* The Forward (Downstream) RF1 cable is the physical connection to the forward RF -20dB test point of optical receiver 1 (OPTRX1).

DS RF2 CABLE* The Forward (Downstream) RF2 cable is the physical connection to the forward RF -20dB test point of optical receiver 2 (OPTRX2).

CRAFT

The Craft port provides a local, physical connection to the transponder. This connection can be used for onsite configuration of the node, modules and transponder. In addition, the Craft port is a fully functional standard Ethernet port capable of providing all the functionality of any standard Ethernet connection.

INTERFACE CONNECTOR

The Interface Connector is the physical connection point at which the transponder attaches to the node or optical hub. The interface connector provides the transponder power, internal communications and a possible upstream RF connection.

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:• PWR• DS• US• Online• Elink• StatThese indicate transponder status. For details on the LEDs and their indications, see the section titled “Checking the LEDs” presented in this manual.

Upstream Pad SocketThe Pad Socket is to attenuate the upstream signal from the transponder. If the transponder is to be used in a GS7000 node then the 10 dB pad must be used. If the transponder is to be used in a GS7000 Optical Hub then the 0 dB pad must be used.

* Not required for optical hubs or 1.2GHz nodes.

If a pad with a value less than 10 dB is used and the transponder is used in a GS7000, there is a risk the output power of the transponder may be too high for the node transmitter.

NOTICE:

The Interace Connector is fragile and must be handled carefully to avoid damage

CAUTION!

Table 2-1, Connector Summary

2.2 Connector Summary

2.0 Connections, continued

13018-345-B0-001, Rev. A (05/2016)

2.3 CMD-N Transponder Specifications

General

DOCSIS: Version 2.0HMS Monitoring Protocol: SNMP v1DOCSIS Monitoring Protocol: SNMP v1, v2, v3RF Interface: InternalRF Internal Padding: Configurable JXP pad for 15 dB UpstreamEthernet Interface: RJ45Operating Temperature: –40°C to +75°CHumidity: 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 MHzTx Output Power: +8 to +58 dBmVRx Frequency Range: 88 MHz to 860 MHzRx Input Level: –15 to +15 dBmVChannel Bandwidth: 6 and 8 MHz

14 018-345-B0-001, Rev. A (05/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 the network.

Installing the transponders and making them operational consists of the following steps, which are explained in detail in this chapter.

• 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 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, A Typical Network

Some provisioning systems require that the transponder’s MAC address be added to the CMTS prior to installing the transponder to achieve full functionality.

NOTICE:

HFC

HFC

Tap

Power Supply

Fiber Node

CMD-N Transponder

Web Client

Softswitch

Cable Modem.cfg TFTP Server

Provisioning Server

Time of Day Server

CheetahXD / SNMP Manager

Fault and Performance Management

OSS Integration

IP Network

Alpha DOCSIS Cable Modem Firmware Image Upgrade

CMTS

RF

3.0 Installation, continued

15018-345-B0-001, Rev. A (05/2016)

3.2 Network InformationRecord the values of the network items below to facilitate the deployment process.

Network WorksheetNetwork Item Value

Cable Modem MAC AddressCable Modem IP AddressTFTP Server IP Address

Provisioning Server IP AddressTime of Day Server IP Address

DHCP Server IP Address

Table 3-1, Network Worksheet

3.3 SecurityDifferent security methods are used to ensure network integrity. Some common issues are:

• 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:90:EA:xx:xx:xx, 00:26:97:xx:xx:xx,

and 00:10:3F:xx:xx:xx to be registered• For SNMP access, UDP ports 161 and 162 must not be blocked.• Remote transponder Web page access requires TCP port 80 to be opened.• Firewalls must allow communication between the cable modem and the various servers.

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 (please refer to “6.0 CMD-N Web Interface”), or its support for telnet server access (please refer to “5.3 Console Access”).


16 018-345-B0-001, Rev. A (05/2016)

The following is a sample cable modem configuration file. Include only those OIDs that will provide the desired features and functionality.

The configuration file entries shown above starting with “docsDevNmAccess” all end with a “.1”. The “.1” is a row index indicating row 1 in the docsDevNmAccess table. Additional rows can be added to this table by adding additional sets of docsDevNmAccess entries with different row indexes. A given row index may only be used once.

NOTICE:

Fig. 3-2, Cable Modem Configuration File Example


17018-345-B0-001, Rev. A (05/2016)

3.5 Installing the CMD-N TransponderThe following sections provide information for installing the CMD-N transponder in the following devices:

• GS7000 Node• 1GHz GS7000 Non-redundant Node• GS7000 Optical Hub

Refer to the appropriate section for installing the CMD-N transponder into the appropriate node hardware.

GS7000 Node Installation

If a pad with a value less than 10 dB is used and the transponder is used in a GS7000 Node, there is a risk that the output power of the transponder may be too high for the node transmitter.

NOTICE:

Fig. 3-3, Upstream Pad Replacement

If the transponder is configured as “non redundant” and being installed in a 1GHz node, refer to the next section, “1 GHz GS7000 Non-Redundant Node Installation.”

NOTICE:

Remove the transponder from the shipping package.Ensure the correct pad for the desired application is installed in the pad socket. For GS7000 Node installations, verify the use of the 10 dB pad in the transponder pad socket. If any other size pad is in place (e.g., a zero (0) dB pad), replace it with the 10 dB pad as shown below.


18 018-345-B0-001, Rev. A (05/2016)

Position the transponder so that the interface connector shown in Fig. 3-4 aligns with the node’s interface connector shown in Fig. 3-5.

Interface Connector

Fiber Node Interface Connector

Fig. 3-4, Fiber Node Interface Connector

Fig. 3-5, Fiber Node Transponder Slot and Interface Connector


19018-345-B0-001, Rev. A (05/2016)

Firmly push the transponder down onto the node’s mother board until transponder seats into position. Use the screws provided with the transponder to secure the transponder to the motherboard. The screw locations are shown in Fig. 3-6.

Transponder Screw Locations

The Interface connector is a complex high density connector; appropriate care must be exercised when installing the transponder to assure proper alignment between the connectors so that the pins are not damaged.

CAUTION!

Fig. 3-6, Transponder Mounting Screw Locations


20 018-345-B0-001, Rev. A (05/2016)

For installation in a 1GHz node, attach the Forward RF1 cable to the Optical Receiver 1 -20 dB test point. Route the cable(s) appropriately within the node. Refer to Fig. 3-7.

The cable must be inserted into the Optical Receiver 1 -20dB test point to ensure correct functionality. This is because the transponder DS RF port that is used corresponds with which receiver is active, RCVR 1 or RCVR 2. If RCVR 1 is the active receiver then the transponder DS RF 1 port is used. If RCVR 2 is the active receiver then the transponder DS RF 2 port is used.

NOTICE:

Node RCVR 1 Connection

Transponder RF1 Connection

Fig. 3-7, Transponder RF1 Cable Attachment Points

If the transponder is installed into a 1.2GHz GS7000 node, the Forward RF1 and RF2 cables do not need to be installed. The Forward signal will be received by the transponder through the interface connector on the OIB board.

NOTICE:


21018-345-B0-001, Rev. A (05/2016)

For installation in a 1GHz node, attach the Forward RF2 cable to the appropriate Optical Receiver 2 -20 dB test point. Route the cable(s) appropriately within the node. Refer to Fig. 3-8.

The cable must be inserted into the Optical Receiver 2 -20 dB test point to ensure correct functionality. This is because the transponder DS RF port that is used corresponds with which receiver is active, RCVR 1 or RCVR 2. If RCVR 1 is the active receiver then the transponder DS RF 1 port is used. If RCVR 2 is the active receiver then the transponder DS RF 2 port is used.

NOTICE:

Node RCVR 2 Connection

Transponder RF2 Connection

Fig. 3-9, Completed Transponder Installation in the Node

Fig. 3-8, Transponder RF2 Cable Attachment Points


22 018-345-B0-001, Rev. A (05/2016)

1 GHz GS7000 Non-Redundant Node InstallationRemove the non-redundant transponder from its shipping package.

Fig. 3-11, Pad Removal

Remove the pad in the “XMTR 1” socket in the node.

Fig. 3-10, Transponder with Return Path Cable


23018-345-B0-001, Rev. A (05/2016)

Verify an appropriate pad value is installed within the end of the return path cable. This would typically be the same value as the longer pad removed in the previous step.

Fig. 3-12, Pad Installation


24 018-345-B0-001, Rev. A (05/2016)

Interface Connector

Fiber Node Interface Connector


Fig. 3-13, Fiber Node Interface Connector

Fig. 3-14, Fiber Node Transponder Slot and Interface Connector


25018-345-B0-001, Rev. A (05/2016)

Firmly push the transponder down onto the node’s mother board until transponder seats into position. Use the screws provided with the transponder to secure the transponder to the motherboard. The screw locations are shown in Fig. 3-15.

Transponder Screw Locations

The Interface connector is a complex high density connector; appropriate care must be exercised when installing the transponder to assure proper alignment between the connectors so that the pins are not damaged.

CAUTION!



26 018-345-B0-001, Rev. A (05/2016)

Install the end of the return path cable into the XMTR 1 pad socket.

Fig. 3-16, Return Path Cable Installed


27018-345-B0-001, Rev. A (05/2016)

The cable must be inserted into the Optical Reciever 1 -20 dB test point to ensure correct functionality. This is because the transponder DS RF port that is used corresponds with which receiver is active, RCVR 1 or RCVR 2. If RCVR 1 is active then the transponder DS RF 1 port is used. If RCVR 2 is the active receiver then the transponder DS RF 2 port is used.

NOTICE:

Fig. 3-17, RF1 to Optical Receiver 1

Attach the Forward RF1 cable to the Optical Reciever 1 -20 dB test point. Route the cable(s) appropriately within the node. Refer to Fig. 3-17.

If the node configuration is for Downstream redundancy, attach the Forward RF2 cable to the appropriate Optical Receiver 2 -20 dB test point. Route the cable(s) appropriately within the node. Refer to Fig. 3-18.

The cable must be inserted into the Optical Receiver 2 -20 dB test point to ensure correct functionality. This is because the transponder DS RF port that is used corresponds with which receiver is active, RCVR 1 or RCVR 2. If RCVR 1 is the active receiver then the transponder DS RF 1 port is used. If RCVR 2 is the active receiver then the transponder DS RF 2 port is used.

NOTICE:


28 018-345-B0-001, Rev. A (05/2016)

Fig. 3-18, RF2 to Optical Receiver 2

Fig. 3-19, Completed Transponder Installation


29018-345-B0-001, Rev. A (05/2016)

GS7000 Optical Hub Installation

Remove the transponder from the shipping package.Ensure the correct pad for the desired application is installed in the pad socket. For GS7000 Optical Hub installations, verify the use of the 0 dB pad in the transponder pad socket. If any other size pad is in place (e.g., a 10 dB pad), replace it with the 0 dB pad as illustrated.

Fig. 3-20, Upstream Pad Socket with Proper 0 dB Pad Installed


30 018-345-B0-001, Rev. A (05/2016)


Interface Connector

Optical Hub Interface

Connector

Fig. 3-22, Optical Hub Transponder Slot and Interface Connector

Fig. 3-21, Optical Hub Interface Connector on CMD-N


31018-345-B0-001, Rev. A (05/2016)

Firmly push the transponder down onto the hub’s mother board until transponder seats into position. Use the screws provided with the transponder to secure the transponder to the mother board. The screw locations are shown in Fig. 3-23.

Transponder Screw Location

Transponder Screw Location

3.6 Configuring the TransponderThe transponder acts as the Cisco GS7000 controller. The node and module configuration of the transponder is required for the node and modules to operate properly. Before the transponder can monitor the node it will need to be set up for how the node is configured. This is typically accomplished through the CMD-N Web Interface, described later in this manual.

For details of how to configure the transponder using the Web page, refer to “6.4 Configuring the Node.”



32 018-345-B0-001, Rev. A (05/2016)

SA-HMS-FIBERNODEGS7000-MIB

If the node or optical hub is already online, some of the transponder configuration can also be performed using SNMP, as described in the following table.

SA-HMS-FIBERNODEGS7000-MIBComponent Description

saFnForwardConfig(OID 1.3.6.1.4.1.1429.1.6.5.2.5)

Sets the forward configuration of the node.

• oneX/twoXFwdSeg(1) - Forward RF signal for all ports comes from one or two optical receivers.

• fourXFwdSeg(2) - Forward RF signal for each port comes from separate optical receivers.

• threeXRx1-2-4FwdSeg(3) - Forward RF signal for each port comes from one of three separate optical receivers. The three receivers are Rx1, 2 and 4; Rx3 is not powered on.

• threeXRx1-3-4FwdSeg(4) - Forward RF signal for each port comes from one of three separate optical receivers. The three receivers are Rx1, 3 and 4; Rx2 is not powered on.

saFnPowerSupplySlot(OID 1.3.6.1.4.1.1429.1.6.5.2.9.1.2)

Configures the power supply slots to indicate whether a power supply is installed or not installed. Set the installed power supplies to Mount and the power supply, if any, that is not installed to Unmount.

saFnRestoreTime(OID 1.3.6.1.4.1.1429.1.6.5.2.8)

Sets the time in seconds the A/B switch setting will be restored after power has been restored to the primary receiver. The default is 9 and the range is 0-255.

saFnOpticalReceiverSlot(OID 1.3.6.1.4.1.1429.1.6.5.2.4.1.2)

Configures the receiver slots to indicate if a receiver is installed or not installed. Set the active slots to Mount and the slots, if any, that do not have an installed receiver to Unmount.

saFnOpticalReceiverLoPwrLimit(OID 1.3.6.1.4.1.1429.1.6.5.2.4.1.4)

Sets the minimum threshold level for the input signal to the A/B switch in mW. The default is 0.10 mW and the range is 0.06-2.40 mW.

If the LoLo Alarm Limit is set for hfcnOpticalReceiverOpticalPower, it also sets the saFnOpticalReceiverLoPwrLimit. Similarly, setting the saFnOpticalRecieverLoPwrLimit also sets hfcnOpticalReceiverOpticalPower.

Notice: In firmware 5.0, hfcnOpticalReceiverOpticalPower (OID 1.3.6.1.4.1.5591.1.5.5.1.2) replaces fnOpticalReceiverPower as the link to saFNOpticalReceiverLoPwrLimit (OID 1.3.6.1.4.1.1429.1.6.5.2.4.1.4).

saFnOpticalReceiverHiPwrLimit(OID 1.3.6.1.4.1.1429.1.6.5.2.4.1.3)

Sets the maximum threshold level for input signal to the A/B switch in mW. The default is 1.60 mW and the range is 0.06-2.40 mW.

If the HiHi Alarm Limit is set for hfcnOpticalReceiverOpticalPower, it also sets the saFnOpticalReceiverHiPwrLimit. Similarly, setting the saFnOpticalReceiverHiPwrLimit also sets the hfcnOpticalReceiverOpticalPower.

Notice: In firmware 5.0, hfcnOpticalReceiverOpticalPower (OID 1.3.6.1.4.1.5591.1.5.5.1.2) replaces fnOpticalReceiverPower as the link to saFnOpticalReceiverHiPwrLimit (OID 1.3.6.1.4.1.1429.1.6.5.2.4.1.3).

saFnReturnLaserSlot(OID 1.3.6.1.4.1.1429.1.6.5.2.2.1.2)

Configures the transmitter slots to indicate if a transmitter is installed or not installed. Set the active slots to Mount and the slots, if any, that do not have an installed transmitter to Unmount.

Table 3-2, SA-HMS-FIBERNODEGS7000-MIB


33018-345-B0-001, Rev. A (05/2016)

3.7 Module Firmware Download Using the CHEETAH-MGMT-UPDATE-MIB

With firmware version 5.0 and greater, the CMD-N transponder for the GS7000 has the ability to download firmware to Optical Amps, Optical Switches, and the Transponder by using the CHEETAH-MGMT-UPDATE-MIB (OID 1.3.6.1.4.1.33872.2.4).

A provisioning style download or management style download can be utilized to upgrade the module’s firmware.

A provisioning style download must be configured in order for the transponder to use the module download information supplied by the provisioning server during boot up or reboot. In the CM config file, set the TFTP server address via updateServerAddressType and updateServerAddress along with the updateProvisioningFilename. UpdateProvisioningFileName OIDs are: 1.3.6.1.4.1.33872.2.4.10.1.4.6.1 for Optical Amplifier and 1.3.6.1.4.1.33872.2.4.10.1.4.6.2 for Optical Switch or 1.3.6.1.4.1.33872.2.4.10.1.4.1.1 for the transponder.

• updateProvisioningGroup (OID 1.3.6.1.4.1.33872.2.4.10.1.1) - A numeric identifier for a distinct group of index values for provisioning update entries.

• updateProvisioningIndex (OID 1.3.6.1.4.1.33872.2.4.10.1.2) - A numeric identifier for a single provisioning update entry, unique within the provisioning group.

• updateProvisioningDescription (OID 1.3.6.1.4.1.33872.2.4.10.1.3) - A text description of this provisioning update entry (as identified by the group and index values).

• updateProvisioningFilename (OID 1.3.6.1.4.1.33872.2.4.10.1.4) - The name of the file to retrieve from the TFTP server for the update. If this is set to the empty string, there is no automatic provisioning for this update entry.

• updateProvisioningStatus (OID 1.3.6.1.4.1.33872.2.4.10.1.5) - This reflects the operational status of this particular provisioning update entry (See Fig. 3-14). • nothingToDo - No filename was provided, the item is up-to-date or it is not needed.• updatePending - An update is needed, but not yet started.• updateInProgress - An update is occurring now.• updateFailed - The last attempt to perform this update was unsuccessful.

• updateProvisioningVersion (OID 1.3.6.1.4.1.33872.2.4.10.1.6) - This is the current version installed for this update entry. If the version is not known, or if the version is not consistent between multiple objects of this update type, an empty string may be returned.

While downloading firmware to the Optical Amps and Optical Switches there will be no communications between the transponder and any Optical Amps or Optical Switches in the Hub or Node throughout the entire firmware download process, although they will continue to function correctly. The transponder will still be able to monitor the Optical Transmitters and Receivers.

NOTICE:

Fig. 3-24, Update Example

A write to this object of updatePending(2) forces the transponder to consider an update as necessary. This is intended as a manual override for the special case where the transponder has previously completed a successful update, and does not recognize the need for another update. Writing any other value to this object will fail.

NOTICE:


34 018-345-B0-001, Rev. A (05/2016)

To start a management initiated download, set the updateServerAddress, and updateFilename to the correct values. Then set the updateControl to either startDownload(1) or forceDownload(2).

The following OIDs are used for the Module Download Feature:

• updateServerAddress (OID 1.3.6.1.4.1.33872.2.4.3) - The IP address of the TFTP server where the module firmware file is located. If the TFTP server is unknown and the OID is read, the returned value will be 0.0.0.0.

• updateModuleType (OID 1.3.6.1.4.1.33872.2.4.1) - The type of download to be executed. The updateProvisioningGroup OID (1.3.6.1.4.1.33872.2.4.10.1.1) followed by the module type from the updateProvisioningDescription must be entered. 1.3.6.1.4.1.33872.2.4.10.1.1.6.1 for Optical Amplifier and 1.3.6.1.4.1.33872.2.4.10.1.1.6.2 for Optical Switch or 1.3.6.1.4.1.33872.2.4.10.1.1.1.1 for Transponder.

• updateServerAddressType (OID 1.3.6.1.4.1.33872.2.4.2) - The type of address of the TFTP server used for the update.

• updateFilename (OID 1.3.6.1.4.1.33872.2.4.4) - The file name of the image to be loaded into the device. • updateControl (OID 1.3.6.1.4.1.33872.2.4.5) - Begins the download to the module(s).

• startDownload(1) - Begins the download to the modules with version checking enabled. If a module is running the same version of firmware that is being downloaded, it will not receive the firmware download. While in the process of downloading in this fashion the downloadAdminStatus will report startDownload if read.

• forceDownload(2) - Begins the download to the modules regardless of the current version of firmware running or any other factors that may cause a download not to be performed. While in the process of downloading in this fashion the updateControl will report forceDownload if read.

• startPush(3) - This command is utilized in conjunction with a standalone tool.• inactive(4) - No update operation underway.

• updateStatus (OID 1.3.6.1.4.1.33872.2.4.6) - Reflects the operational status of the firmware download. The following are the possible states:• unknown(0) - No information about any previous update operation. • downloading(1) - Transferring data from the TFTP server to the transponder.• programming(2) - Programming of the module in progress.• completePush(3) - Complete from a ‘push’ update.• completeDownload(4) - startDownload or forceDownload completed successfully.• completeWithExceptions(5) - Indicates the firmware download has completed but one or more modules failed

to download the firmware successfully.• failedTftp(6) - Transfer of the file failed.• failedInvalid(7) - Firmware file was invalid.• failedTimeout(8) - Device did not respond when firmware download attempted.• failedOther(9) - An unknown error occurred when attempting the firmware download.

• updateStatusMessage (OID 1.3.6.1.4.1.33872.2.4.7) - A text message providing the latest download status information.

The Management Upgrade can also be performed through CheetahXD 5.3 (or later).NOTICE:


35018-345-B0-001, Rev. A (05/2016)

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

• Online• Pwr• DS• US• Elink• Stat

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 Pwr, DS, US, Online, and Elink LEDS conform to the DOCSIS OSSI specification.

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


36 018-345-B0-001, Rev. A (05/2016)

Table 3-3, LED Status Summary

LED Status SummaryLED Function State Meaning

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

DSDownstream LED: Indicates status with respect to downstream scanning and synchronization

Blinking The transponder is scanning for a downstream DOCSIS channel.

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

USUpstream LED: Indicates status with respect to acquisition 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.

OnlineOnline LED: Indicates status with respect to 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 and is operational.

ElinkCPE Link LED: Indicates status with respect to 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.

StatStatus LED: Indicates the presence or absence 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.

37018-345-B0-001, Rev. A (05/2016)

4.0 Provisioning the SNMP Manager

4.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 and Table 4-3 are provided by Alpha Technologies or Cisco. There are dependencies between MIB files, so compile them in the order shown in the following tables.

Management Information Base (MIB) FilesANSI / SCTE # 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 (MID) 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 050Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-Transponder-Interface-Bus(TIB)-MIB Management Information Base (MIB) Definition

ANSI / SCTE 85-3 HMS 118 SCTE-HMS-HE-OPTICAL-AMPLIFIER-MIBANSI / SCTE 85-4 HMS 119 SCTE-HMS-HE-OPTICAL-SWITCH-MIB

Management Information Base (MIB) FilesProvider Title

Alpha Technologies ATI-DEV-HFC-NODES-MIBAlpha Technologies ATI-MGMT-SYS-HTTP-LOGINS-MIBAlpha Technologies CHEETAH-MGMT-UPDATE-MIBAlpha Technologies CHEETAH-MGMT-ACCESS-MIBAlpha Technologies Lighthouse HMS Extensions MIB

Cisco SA-HMS-FIBERNODEGS7000-MIB

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

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

4.0 Provisioning the SNMP Manager, continued

38 018-345-B0-001, Rev. A (05/2016)

Additional Supported Management Information Base (MIB) Files

TitleBRCM-BFC-MGMT-MIBBRCM-CM-MGMT-MIB

BRCM-EMTA-MGMT-MIBBRCM-HTTP-MGMT-MIBBRCM-SNMP-MGMT-MIBBRCM-SSH-MGMT-MIB

BRCM-TELNET-MGMT-MIBBRIDGE-MIB

DISMAN-PING-MIBDOCS-BPI2-MIB

DOCS-CABLE-DEVICE-DRAFT-MIBDOCS-CABLE-DEVICE-MIB

DOCS-CABLE-DEVICE-TRAP-MIBDOCS-IF-MIB

DOCS-QOS-MIBDOCS-TEST-MIB

ENTITY-MIBeSAFE-MIB

EtherLike-MIBIF-MIB

IGMP-STD-MIBIP-MIB

RFC1213-MIBSLED-MIB

SNMPv2-MIBTOLLGRADE-HTTP-MGMT-MIB

UDP-MIBUSB-MIB

Table 4-3, Additional Supported Management Information Base (MIB) Files

ATI-DEV-HFC-NODES-MIBComponent Description

hfcnReturnLaserOpticalPower(OID 1.3.6.1.4.1.926.1.5.4.3.1.11)

This optional object represents the optical power on the return laser, expressed in units of 1 microWatt. This object has an entry in the limit properties table.

hfcnOpticalReceiverOpticalPower(OID 1.3.6.1.4.1.926.1.5.4.4.1.5)

This optional object represents the received optical power, expressed in units of 1 microWatt. This object has an entry in the limit properties table.

Table 4-4, High-resolution optical power in ATI-DEV-HFC-NODES-MIB

4.0 Provisioning the SNMP Manager, continued

39018-345-B0-001, Rev. A (05/2016)

In 5.0 and later, hfcnReturnLaserOpticalPower (OID 1.3.6.1.4.1.926.1.5.4.3.1.11) and hfcnOpticalReceiverOpticalPower (OID 1.3.6.1.4.1.926.1.5.4.4.1.5) have a higher resolution (.001 milliWatts) than the fnReturnLaserOpticalPower and fnOpticalReceiverPower. These new components are located in ATI-DEV-HFC-NODES-MIB. The fnReturnLaserOpticalPower and fnOpticalReceiverPower components are still supported, but have a lower resolution.

NOTICE:

When upgrading the transponder to firmware version 5.0, two new objects (hfcnReturnLaserOpticalPower and hfcnOpticalReceiverOpticalPower) will be discovered. If CheetahXD is used, the alarm limits associated with these new objects will need to be configured and downloaded to each transponder.

NOTICE:

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 or cold 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 of the transponder, node, node modules, and monitoring of the fiber node.

40 018-345-B0-001, Rev. A (05/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 of 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 “6.0 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 the Web browser.3. Enter the address value 192.168.100.1 into the browser’s address field. Press enter or the appropriate button to

commence communications with the transponder.4. The transponder’s home page will appear.

The cable modem configuration may enable functions like DHCP through the Ethernet interface requiring the technicians to create a static IP on the connecting terminal in the 192.168.100.0/24 range.

NOTICE:

5.0 Using the Craft Port, continued

41018-345-B0-001, Rev. A (05/2016)

5.3 Console Access

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.

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

NOTICE:

By default, telnet 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-2). In addition, the default username and password may be altered if desired.

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 AlphatelnetPassword 1.3.6.1.4.1.4413.2.2.2.1.1.1.3.0 AlphaSet

telnetServerControl 1.3.6.1.4.1.4413.2.2.2.1.1.1.4.0 1 (enabled)

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


42 018-345-B0-001, Rev. A (05/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. Be certain that telnet access to the server has been enabled by making the appropriate MIB changes. Refer to the information presented earlier in this section for details on enabling telnet access to the server.

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

3. Connect a standard CAT5 Ethernet cable between the transponder and a laptop or similar device.4. Via 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 Setting0xC0 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 Value telnetIpStackInterfaces OID Value 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.

The cable modem configuration may enable functions like DHCP through the Ethernet interface requiring the technicians to create a static IP on the connecting terminal in the 192.168.100.0/24 range.

NOTICE:

Fig. 5-1, Console Main Page


43018-345-B0-001, Rev. A (05/2016)

5. Press the Enter key. At the login prompt enter the appropriate user name (the default is Alpha) and press the Enter key. Next, enter the appropriate password (the default is AlphaSet) and press the Enter key. (If a different user name and password have been previously configured by the user, those settings must be used. Additionally, an older transponder that has been updated may still default to “cheetah” for user name and password configuration.) The following screen will appear.

Commands Available in the Device Section of Console ModeCommand Descriptionabswitch Sets an optical receiver A/B switch behavior

masteratten Masteratten is not supported for the GS7000portatten Sets reverse attenuation for a port

show Displays information about the devices managed by this systemstatus Displays status information for sub-devices

Fig. 5-3, Console Device Folder

To switch to the device section, type “cd device” at the prompt and press Enter. The following screen appears.

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

Console mode supports a number of commands that are used for troubleshooting and debugging purposes. Providing a list and description of 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 device directory. For additional information about the use of the console commands, please contact Alpha Technical Support at 1-866-944-1482.

Table 5-4 provides a list of the commands in the device section available via console mode along with a brief description of each command.

Fig. 5-2, Console Prompt Page


44 018-345-B0-001, Rev. A (05/2016)

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

Fig. 5-4, Console Commands

To display the proper syntax for a particular command, type the command followed by “?” and press Enter.

When the session is complete, type “exit” to terminate the telnet session, and then close the telnet dialog box.

45018-345-B0-001, Rev. A (05/2016)

6.0 CMD-N Web Interface6.1 OverviewThe CMD-N transponder offers a Web interface, for easy viewing and optional modification of many important details of the fiber node and transponder through a standard Web browser. This Web access may be performed locally, using the craft port and the standard local IP address of 192.168.100.1, or through the cable modem interface, using the assigned cable modem IP address.

By default, Web access to the transponder is fully supported. To change the configuration of this access, refer to “6.5 Configuring the Web Access.”

Fig. 6-1, GS7000 Home Page

6.0 CMD-N Web Interface, continued

46 018-345-B0-001, Rev. A (05/2016)

6.2 Logging InInitially, all of the Web pages on the transponder are read-only: information can be read, but not edited. Changes usually come from the Element Management System (EMS) rather than from the Web interface, but if the unit is configured to allow changes to be made via the Web interface, the user can log in to make changes.

1. Select the Log In link located near the top right corner of the Web page. (If this link is not shown, the transponder is not configured to allow changes to be made from the Web interface.)

2. When prompted, enter user name (the default is Alpha) and password (the default is AlphaGet).

In cases where a manual log out is not performed, the transponder will automatically log the user out after a certain, configurable interval, to prevent the EMS from being blocked indefinitely.

NOTICE:

Fig. 6-2, Log in via GS7000 Home Page

After logging in, some elements on some Web pages become editable. Upon completion select the Log Out link near the upper right corner to return control to the EMS and return the Web interface to read-only operation.

6.3 Web Page Summaries

Home PageThe Home page displays when the GS7000 Web page is loaded. This page displays summaries for the Alarm, Hardware, System, and Communications pages. Follow the link below each summary to view the corresponding page for further detail.

Fig. 6-3, GS7000 Home Page

While logged in, the EMS is not able to make changes. NOTICE:


47018-345-B0-001, Rev. A (05/2016)

System PagesSelecting the System link in the navigation pane enables the user to access five areas:

• Hardware Diagram Page - View and edit the Node by its hardware modules.• HFC Node Page - View details about the Node and its related modules.• System Data Page - View and edit system data for the transponder.• DOCSIS Page - View details about the cable modem communications link.• Alarms Page - View the current alarms, and view and edit alarm settings.

Fig. 6-4, System Link, Navigation Pane, GS7000 Home Page


48 018-345-B0-001, Rev. A (05/2016)

Hardware Diagram PageOpen the Hardware Diagram page by selecting System -> Hardware Diagram on the main menu.

The GS7000 Hardware Diagram page displays the Node Type, Node Hardware Type, Forward Configuration, Forward Redundancy, Restore Time, and Line Voltage data fields. An interactive diagram is also displayed (see Fig. 6-5).

The node diagram represents each installed module with a colored box to indicate the status of that module. Selecting a module opens a separate window with details about that specific module.

By logging in on this page, you can make configuration changes to the node and the types of modules installed. This is detailed in “6.4 Configuring the Node.”

Fig. 6-5, Hardware Diagram

Alarm DescriptionsColor MeaningGreen No AlarmsYellow Minor AlarmRed Major AlarmGray Not Configured

Table 6-1, Alarm Descriptions


49018-345-B0-001, Rev. A (05/2016)

HFC Node PageOpen the HFC Node page by selecting System -> HFC Node on the main menu. The HFC Node page displays all the details of the fiber node and its various modules, organized by category. This is similar to the information in the pop-ups on the Hardware Diagram page, but presented all in a single view.

Fig. 6-6, HFC Node Data


50 018-345-B0-001, Rev. A (05/2016)

Many of the features on the HFC Node page are editable or selectable when logged in. Before leaving a page, click the Save Changes button at the bottom of the page to apply and save new settings.

Other items in this display are “alarmable,” meaning they can (and may already) be set to announce alarms to an Element Management System (EMS) under certain conditions. These alarmable items are indicated with a bell icon to the right of the information. The bell icon will be either solid to indicate that an alarm is enabled, or an outline to indicate that the item is configurable to generate alarms, but the alarms for this item are presently disabled. The operator can select the bell icon to display, or if logged in, modify the alarm settings for that item.

Configure Alarm Settings

Use the following instructions to configure an alarm setting:

1. If not already logged in, select the Log In link near the upper right corner of the page, enter the user name and password and then click the Log In button.

2. Select the bell icon next to the item to be configured; a pop-up window (sample shown below) will appear displaying the current alarm settings.

3. For a numeric property, enter the desired threshold values, and set the checkbox next to each threshold for which you want to enable an alarm.

4. For a discrete property, for each possible state listed, select what alarm level you wish to use (no alarm, minor alarm, major alarm).

5. As necessary, select the Save Changes or Cancel Changes button within the popup. Alternatively, simply closing the popup window will prevent the changes from being applied.

Fig. 6-7, Alarm Settings Popup Window

Any changes to parameters in the field that are deemed necessary should be recorded and conveyed to the EMS operations group for application to this devices profile, otherwise the next download from the EMS can overwrite the field set values.

NOTICE:


51018-345-B0-001, Rev. A (05/2016)

Fig. 6-8, System Data

System Data Page

Open the System Data page by selecting System -> System Data on the main menu. The System Data page displays a variety of status and configuration information about the transponder (this is separate from information about the node).

By logging in on this page, configuration changes can be made to the transponder, including but not limited to, the system name, system location, system contact and logical ID, each of which is reported in SNMP.

The RF Adjust Downstream and RF Adjust Upstream values are added to the corresponding measured RF signal levels before reporting the adjusted values to a CMTS system. These “Virtual pad” values allow the readings to better align with expected values from cable modems. When adjustment values are set, the DOCSIS communications page shows both the reported and actual values.


52 018-345-B0-001, Rev. A (05/2016)

DOCSIS Page

Open the DOCSIS page by selecting System -> DOCSIS on the main menu. The DOCSIS page displays detailed information about the DOCSIS modem including a quick communications summary, downstream and upstream data, and network communications data.

Three data points on this page can also be enabled with alarm settings. These data points are Downstream Power and SNR (RxMER) in the Downstream section and Upstream Power in the Upstream section. Alarm-related settings for these features are set by selecting the bell icon to the right of the respective line.

Fig. 6-9, DOCSIS Data


NOTICE:


53018-345-B0-001, Rev. A (05/2016)

Alarms Page

Open the Alarms page by selecting System -> Alarms on the main menu.

The Alarms page consists of three main sections:

• Alarms - Any items currently in alarm, first listed as a summary and then by category.• Limit Properties - Configuration of alarms generated by exceeding numeric limits.• Discrete Properties - Configuration of alarms generated by entering a specific discrete status.

The Alarms section presents a quick list of every current alarm, not just the first few shown on the Home page. The alarm details, including the current value, are then listed by category.

The Limit Properties section shows all the SNMP objects in this transponder that can generate an alarm based on numeric limits.

Fig. 6-10, Limit Properties, Alarms


54 018-345-B0-001, Rev. A (05/2016)

Each type of alarm setting is displayed with its current state, current value, and five settings: Major High, Minor High, Minor Low, Major Low, and Dead Band.

The checkboxes next to each setting indicate whether the setting generates an alarm or not. Checked boxes generate an alarm. Unchecked boxes do not generate an alarm.

Alarms are triggered once the configured major/minor low value or the minor/major high values are exceeded.

The Dead Band setting helps to prevent alarm oscillation by initiating a major and/or minor band buffer that prohibits the triggering of repeated alarms (once the upper or lower limits are reached). This buffer stalls additional alarms until the Dead Band setting is reached (the level moves this amount in the opposite direction of the alarm) and the alarm is reset.

If logged into the Web page, the Limit Properties page can be edited. To set specific alarm setting, enter the desired amount in the appropriated text box, select the checkbox next to the text box, and then click Save Changes.

The Discrete Properties section shows all the SNMP objects in this transponder that can generate an alarm when the object enters a specific discrete status.

Each of the alarm settings on this page display their current setting in the State column (“Nominal” for no alarms, “Major Discrete” for major alarms, and “Minor Discrete” for minor alarms), and can be set to Major Alarm, Minor Alarm, or No Alarm in the Enable column. To change an alarm setting, select the desired alarm setting from the Enable drop down menu, then click Save Changes.

Fig. 6-11, Discrete Properties, Alarms


55018-345-B0-001, Rev. A (05/2016)

Modem Log Page

Open the Modem Log page by selecting History -> Modem Log on the main menu. The Modem Log page records the system events including the time, alarm count, priority, event description, and the ID of the alarm.

Fig. 6-12, Modem Log Page


NOTICE:


56 018-345-B0-001, Rev. A (05/2016)

Constellation PageOpen the Constellation page by selecting Tools -> Constellation. The Constellation page displays a visual representation of the accuracy of the received digital signal, which allows a user to quickly identify a variety of common signal impairments.

The downstream test will begin as soon as the page is loaded. The progress bar is above the Constellation image. Click Stop to abort the test.

The Downstream table, located to the right of the constellation map, displays specific information related to the Constellation map. Descriptions for each specification are shown below.

Downstream Table InformationSpecification DescriptionFrequency The downstream frequency given in MHz

Power The downstream power given in dBmV

SNR (RxMER)The downstream signal quality.

Signal Noise Ratio (SNR)/Modulation Error Rate (MER)EVM Error Vector Magnitude (EVM) calculated from MER

CER Interval The intervals of each CER check.Codeword Error Rate (CER) refresh rate.

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.

Fig. 6-13, Constellation Page

Table 6-2, Downstream Table Information


57018-345-B0-001, Rev. A (05/2016)

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. The following table summarizes the shapes commonly visible in the RF Constellation page. Examples of these shapes are illustrated in the figures below.

Table 6-3, 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 are 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.


58 018-345-B0-001, Rev. A (05/2016)

Fig. 6-14, Normal Centered Dots (Good Sound Quality)

Fig. 6-15, Fuzzy (Low CNR and/or Low MER)


59018-345-B0-001, Rev. A (05/2016)

Fig. 6-16, Circular Smear (Phase Noise)

Fig. 6-17, Corners Squeezed to Center (Gain Compression)


60 018-345-B0-001, Rev. A (05/2016)

Fig. 6-18, Rectangular vs. Square (I-Q Imbalance)

Fig. 6-19, Twisted or Skewed (Quadrature Distortion)


61018-345-B0-001, Rev. A (05/2016)

6.4 Configuring the NodeFor proper operation, the GS7000 must be configured to match the node in which it is installed. Configuration is done at the time of the initial installation of the GS7000, or whenever the node is reconfigured. The technician has the option of connecting to the GS7000 via an ethernet cable in the local craft port or remotely via the CMTS connection.

The majority of the configuration is accomplished on the on the Hardware Diagram page. Once the Craft Port Web connection has been established, configure the node as follows:

1. Navigate to the main Web page by entering the IP address of the transponder into the Web browser’s URL bar.2. Log In.3. On the main menu, click System -> Hardware Diagram. This opens the GS7000 Hardware Diagram page as

shown below.

Fig. 6-20, GS7000 Hardware Diagram

Configuration table


62 018-345-B0-001, Rev. A (05/2016)

Table 6-4, Node Configuration Options

Node Configuration OptionsComponent Description

Node Type

Sets the GS7000 device type:• GS7000 Optical Node• GS7000 Optical Hub Node• GS7000 Optical Hub

Node Hardware Type Indicates the detected node hardware type, as indicated by the OIB board. This is not available on the older, 1GHz transponders.

Forward Configuration

The forward configuration of the node:• 1X / 2X - Forward RF signal for all ports comes from one or two optical receivers• 4X - Forward RF signal for each port comes from separate optical receivers.• 3X:1,2,4 - Forward RF signal for each port comes from one of three separate optical

receivers. The three receivers are Rx1, 2 and 4; Rx3 is not powered on.• 3X: 1,3,4 - Forward RF signal for each port comes from one of three separate optical

receivers. The three receivers are Rx1, 3 and 4; Rx2 is not powered on.

Forward Redundancy

For nodes with forward redundancy (and A/B switches), this determines whether the inactive receiver is powered or not: • Power down inactive receiver - the receiver feeding the unused side of the A/B switch is

powered off to save power. • Power both receivers - continue powering the inactive receiver. This is required for certain

low-power receiver modules.

Restore Time The Restore Time is the time in Seconds the A/B switch setting will be restored after power has been restored to the primary receiver. The default is 9 and the range is 0-255.

Line VoltageSets whether the node reports AC voltage for a specific AC input (the one that is connected) or both inputs (the node has redundant power, or the AC shorting jumper is installed to provide the same AC source to both power supplies).

General Node Configuration

The Hardware Diagram page shows a configuration table above the diagram for general node settings. See Table 6-4 for descriptions of the node configuration options.

Once the applicable configuration changes have been made, click the Save Changes button to apply the changes.


63018-345-B0-001, Rev. A (05/2016)

Node Module Configuration

1. Click on the gray slot for the module to be configured, or a colored slot for the module to be reconfigured.2. On the popup window, select the module that is installed in that slot (see Fig. 6-21).3. To apply configuration changes, on the popup window click Save Changes, or select Cancel Changes or

Close to exit without making changes.4. Repeat this process for additional modules.

Fig. 6-21, Configuring Module Slots


64 018-345-B0-001, Rev. A (05/2016)

Other Configurations

Configuration choices specific to the transponder, rather than to the fiber node, can be found on the System -> System Data page. From this page, the operator can configure the values reported by several SNMP OIDs:

• sysName (1.3.6.1.2.1.1.5.0)• sysLocation (1.3.6.1.2.1.1.6.0)• sysContact (1.3.6.1.2.1.1.4.0)• commonLogicalID (1.3.6.1.4.1.5591.1.3.1.1.0)

Fig. 6-22, System Data Page


65018-345-B0-001, Rev. A (05/2016)

6.5 Configuring the Web AccessA number of SNMP objects configure the behavior of the Web page, or disable it entirely. These settings can be viewed and set through a MIB browser, or configured at startup using the cable modem configuration file.

The default port for HTTP traffic is port 80, but can be configured to use other ports via the 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 shut down access to the HTTP server for the given interface. The specific OIDs and their default values are listed in Table 6-5. The port must be open to use all of the features described here.

There are both Admin and User usernames and paswords. Both usernames (Admin and User) have the ability to make changes to settings in the Web interface. The passwords can be changed via the Broadcom httpMgmt MIB. The specific OIDs and default values are shown below.

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 0* This parameter is not applicable to this transponder

Table 6-5, OIDs for Port Management

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 AlphaSet

httpUserId 1.3.6.1.4.1.4413.2.2.2.1.1.3.3.0 AlphahttpUserPassword 1.3.6.1.4.1.4413.2.2.2.1.1.3.4.0 AlphaGet

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


66 018-345-B0-001, Rev. A (05/2016)

Configuration and information for the transponder’s login ability can be accessed using the ATI-MGMT-SYS-HTTP-LOGINS-MIB. See the following table for the MIB file details:

ATI-MGMT-SYS-HTTP-LOGINS-MIBComponent Description Values

atiHttpLoginLocalAccess(OID 1.3.6.1.4.1.926.1.3.2.2.4.5.1.0)

This controls whether the device will accept Web interface logins from the local (Ethernet) port. This setting is retained in non-volatile memory.

Notice: atiHttpLoginLocalAccess is enabled by default.

noAccess(1), access(2)

atiHttpLoginRemoteAccess(OID 1.3.6.1.4.1.926.1.3.2.2.4.5.2.0)

This controls whether the device will accept Web interface logins from the network. This setting is retained in non-volatile memory.

Notice: atiHttpLoginRemoteAccess is enabled by default.

NoAccess(1), access(2)

atiHttpLoginState(OID 1.3.6.1.4.1.926.1.3.2.2.4.5.3.0)

This indicates whether any user is currently logged into the Web interface, and if so, the user’s level of access. This object has an associated entry in the Discrete Property Table.

noLogin(1), userLogin(2), adminLogin(3)

aitHttpLoginUser(OID 1.3.6.1.4.1.926.1.3.2.2.4.5.4.0)

This displays the username of the user that is logged in. This is an empty string if there is not a Web login session underway.

atiHttpLoginTime(OID 1.3.6.1.4.1.926.1.3.2.2.4.5.5.0)

If a user is logged into the Web interface, and the device knew the time of day at the point when the login occurred, this is the time when the session began.

atiHttpLoginTimeout(OID 1.3.6.1.4.1.926.1.3.2.2.4.5.6.0)

This is the time, in minutes, that a Web login session may be inactive (time between page loads) before the session automatically ends. This setting is retained in non-volatile memory.

atiHttpLoginForceLogout(OID 1.3.6.1.4.1.926.1.3.2.2.4.5.7.0)

This will always read as normal(1). Set this to forceLogout(2) to cause the current Web login, if any, to be logged out.

normal(1), forceLogout(2)

atiHttpLoginLastUser(OID 1.3.6.1.4.1.926.1.3.2.2.4.5.8.0)

If there has been a login and subsequent logout on the Web interface since the device started, this is the username of that login session.

atiHttpLoginLastStartTime(OID 1.3.6.1.4.1.926.1.3.2.2.4.5.9.0)

If there has been a login and subsequent logout on the Web interface since the device started, and the device knew the time of day at the point when the login occurred, this is the time when that session began.

atiHttpLoginLastEndTime(OID 1.3.6.1.4.1.926.1.3.2.2.4.5.10.0)

If there has been a login and subsequent logout on the Web interface since the device started, and the device knew the time of day at the point when the logout occurred, this is the time when that session ended.

Table 6-7, ATI-MGMT-SYS-HTTP-LOGINS-MIB

67018-345-B0-001, Rev. A (05/2016)

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

Pin Number Configuration Chart for the Ethernet CablePin Name1 Transmit +2 Transmit -3 Receive +4 Unused5 Unused6 Receive -7 Unused8 Unused

Table 7-1, Pin Number Configuration Chart for the Ethernet Cable

68 018-345-B0-001, Rev. A (05/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. Refer to the Cable Labs CM-SP-OSSIv2.0 and SP-BPI+ specifications for details on secure software download.

Transponders running firmware 5.0 or higher can also accept updates using the CHEETAH-MGMT-UPDATE-MIB. This MIB was described in “3.7 Module Firmware Download Using the CHEETAH-MGMT-UPDATE-MIB.”

Transponders running a firmware version prior to 4.10 will first need to update to 4.10 before updating further to firmware version 5.0 or later. Firmware versions prior to 4.10 will not accept firmware version 5.0 or above.

Visit us at www.alpha.com

Alpha Technologies Inc.3767 Alpha WayBellingham, WA 98226 United StatesTel: +1 360 647 2360Fax: +1 360 671 4936

Alpha Technologies Europe Ltd.Twyford House ThorleyBishop’s StortfordHertfordshire, CM22 7PA United KingdomTel: +44 1279 501110Fax: +44 1279 659870

Alpha TechnologiesSuite 1903, Tower 1, 33 Canton Road, KowloonHong Kong City, ChinaPhone: +852 2736 8663Fax: +852 2199 7988

Alpha Technologies Ltd.7700 Riverfront GateBurnaby, BC V5J 5M4 CanadaTel: +1 604 436 5900Fax: +1 604 436 1233Toll Free: +1 800 667 8743

Alpha Technologies GmbHHansastrasse 8D-91126Schwabach, GermanyTel: +49 9122 79889 0Fax: +49 9122 79889 21

Alphatec Ltd.339 St. Andrews St. Suite 101 Andrea ChambersP.O. Box 564683307 Limassol, CyprusTel: +357 25 375 675Fax: +357 25 359 595

Alpha TEK oooKhokhlovskiy Pereulok 16Stroenie 1, Office 403Moscow, 109028 RussiaTel: +7 495 916 1854Fax: +7 495 916 1349

Alphatec BalticS. Konarskio Street 49-201Vilnius, LT-03123 LithuaniaTel: +370 5 210 5291Fax: +370 5 210 5292

Due to continuing product development, Alpha Technologies reserves the right to change specifications without notice. Copyright © 2016 Alpha Technologies. All Rights Reserved. Alpha® is a registered trademark of Alpha Technologies. 018-345-B0-001, Rev. A (05/2016)

Documents

Effective: May 2016 - Alpha Technologies Broadbandbroadband.alpha.com/.../cmd_n_cisco_gs_7000/018345B0.pdf · Safety Notes Alpha considers customer safety and satisfaction its most