Alpha CMD-N Cisco GS7000 Technical Manual

Type
Technical Manual
CMD-N GS7000
Technical Manual
Effective: May 2016
Safety Notes
Alpha considers customer safety and satisfaction its most important priority. To reduce the risk of
injury or death and to ensure continual safe operation of this product, certain information is presented
differently in this manual. Alpha tries to adhere to ANSI Z535 and encourages special attention and
care to information presented in the following manner:
The following sections contain important safety information that must be followed during the 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 specic regulatory/code requirements that may affect the placement of equip-
ment and /or installation procedures.
ATTENTION:
NOTICE provides additional information to help complete a specic task or procedure.
NOTICE:
ELECTRICAL HAZARD WARNING provides electrical safety information to PREVENT
INJURY OR DEATH to the technician or user.
WARNING! ELECTRICAL HAZARD
FUMES HAZARD WARNING provides fumes safety information to PREVENT INJURY OR
DEATH to the technician or user.
WARNING! FUMES HAZARD
FIRE HAZARD WARNING provides ammability safety information to PREVENT INJURY OR
DEATH to the technician or user.
WARNING! FIRE HAZARD
This WARNING provides safety information for both Electrical AND Fire Hazards
WARNING! ELECTRICAL & FIRE HAZARD
CAUTION provides safety information intended to PREVENT DAMAGE to material or
equipment.
CAUTION!
GENERAL HAZARD WARNING provides safety information to PREVENT INJURY OR
DEATH to the technician or user.
WARNING! GENERAL HAZARD
3018-345-B0-001, Rev. A (05/2016)
CMD-N GS7000
Technical Manual
018-345-B0-001 Rev. A
Effective Date: May 2016
©
2016 by Alpha Technologies, Inc.
Disclaimer
Images 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 Information
Sales information and customer service in USA
(7AM to 5PM, Pacic Time):
Complete technical support in USA
(7AM to 5PM, Pacic Time or 24/7 emergency support):
Website:
866 944 1482
www.alpha.com
412 923 3486
4 018-345-B0-001, Rev. A (05/2016)
Table of Contents
1.0 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.3 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.4 Technical Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.0 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
2.2 Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3 CMD-N Transponder Specications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
RF Transmit/Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.0 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.1 Provisioning the Transponders in the Network . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 Network Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.4 Cable Modem Conguration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5 Installing the CMD-N Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
GS7000 Node Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1 GHz GS7000 Non-Redundant Node Installation . . . . . . . . . . . . . . . . . . . . . . 22
GS7000 Optical Hub Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.6 Conguring the Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
SA-HMS-FIBERNODEGS7000-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.7 Module Firmware Download Using the CHEETAH-MGMT-UPDATE-MIB . . . . . . . . . . 33
3.8 Checking the LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.0 Provisioning the SNMP Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.1 MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2 Acquiring the Transponders by the SNMP Manager . . . . . . . . . . . . . . . . . . . . . 39
5.0 Using the Craft Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.2 Web Page Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.3 Console Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5018-345-B0-001, Rev. A (05/2016)
6.0 CMD-N Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.2 Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.3 Web Page Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
System Pages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Hardware Diagram Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
HFC Node Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
System Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
DOCSIS Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Alarms Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Modem Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Constellation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.4 Conguring the Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
General Node Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Node Module Conguration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Other Congurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.5 Conguring the Web Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.0 Cable Pinout Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
7.1 Ethernet Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
8.0 Upgrading the CMD-N Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table of Contents
6 018-345-B0-001, Rev. A (05/2016)
Figures
Fig. 1-1, The CMD-N Transponder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Fig. 2-1, CMD-N Transponder Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Fig. 2-2, CMD-N Transponder Upstream Pad Location . . . . . . . . . . . . . . . . . . . . . . . 12
Fig. 3-1, A Typical Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Fig. 3-2, Cable Modem Conguration File Example . . . . . . . . . . . . . . . . . . . . . . . . . 16
Fig. 3-3, Upstream Pad Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Fig. 3-4, Fiber Node Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Fig. 3-5, Fiber Node Transponder Slot and Interface Connector . . . . . . . . . . . . . . . . . . 18
Fig. 3-6, Transponder Mounting Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Fig. 3-7, Transponder RF1 Cable Attachment Points . . . . . . . . . . . . . . . . . . . . . . . . 20
Fig. 3-8, Transponder RF2 Cable Attachment Points . . . . . . . . . . . . . . . . . . . . . . . . 21
Fig. 3-9, Completed Transponder Installation in the Node . . . . . . . . . . . . . . . . . . . . . . 21
Fig. 3-10, Transponder with Return Path Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Fig. 3-11, Pad Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Fig. 3-12, Pad Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Fig. 3-13, Fiber Node Interface Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Fig. 3-14, Fiber Node Transponder Slot and Interface Connector . . . . . . . . . . . . . . . . . . 24
Fig. 3-15, Transponder Mounting Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . 25
Fig. 3-16, Return Path Cable Installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Fig. 3-17, RF1 to Optical Receiver 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Fig. 3-18, RF2 to Optical Receiver 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Fig. 3-19, Completed Transponder Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Fig. 3-20, Upstream Pad Socket with Proper 0 dB Pad Installed . . . . . . . . . . . . . . . . . . 29
Fig. 3-21, Optical Hub Interface Connector on CMD-N . . . . . . . . . . . . . . . . . . . . . . . 30
Fig. 3-22, Optical Hub Transponder Slot and Interface Connector . . . . . . . . . . . . . . . . . 30
Fig. 3-23, Transponder Mounting Screw Locations . . . . . . . . . . . . . . . . . . . . . . . . . 31
Fig. 3-24, Update Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Fig. 3-25, The CMD-N Transponder LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Fig. 5-1, Console Main Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Fig. 5-2, Console Prompt Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Fig. 5-3, Console Device Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Fig. 5-4, Console Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Fig. 6-1, GS7000 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Fig. 6-2, Log in via GS7000 Home Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Fig. 6-3, GS7000 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Fig. 6-4, System Link, Navigation Pane, GS7000 Home Page . . . . . . . . . . . . . . . . . . . 47
Fig. 6-5, Hardware Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Fig. 6-6, HFC Node Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Fig. 6-7, Alarm Settings Popup Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Fig. 6-8, System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Fig. 6-9, DOCSIS Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Fig. 6-10, Limit Properties, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Fig. 6-11, Discrete Properties, Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Fig. 6-12, Modem Log Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Fig. 6-13, Constellation Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
7018-345-B0-001, Rev. A (05/2016)
Tables
Table 1-1, CMD-N Package Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 1-2, Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 1-3, Technical Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Table 2-1, Connector Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 3-1, Network Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 3-2, SA-HMS-FIBERNODEGS7000-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Table 3-3, LED Status Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 4-1, Management Information Base (MIB) Files . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 4-2, Management Information Base (MIB) Files . . . . . . . . . . . . . . . . . . . . . . . . 37
Table 4-3, Additional Supported Management Information Base (MIB) Files . . . . . . . . . . . . 38
Table 4-4, High-resolution optical power in ATI-DEV-HFC-NODES-MIB. . . . . . . . . . . . . . . 38
Table 5-1, OIDs for Usernames, Passwords, Telnet Access for Console Access . . . . . . . . . . 41
Table 5-2, TelnetIpStackInterfaces OID Values and Descriptions . . . . . . . . . . . . . . . . . . 42
Table 5-3, Telnet Access Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Table 5-4, Commands Available in the Device Section of Console Mode . . . . . . . . . . . . . . 43
Table 6-1, Alarm Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 6-2, Downstream Table Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Table 6-3, QAM Constellation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 6-4, Node Conguration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Table 6-5, OIDs for Port Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Table 6-6, OIDs for Usernames and Passwords for Web Interface Access . . . . . . . . . . . . . 65
Table 6-7, ATI-MGMT-SYS-HTTP-LOGINS-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Table 7-1, Pin Number Conguration Chart for the Ethernet Cable . . . . . . . . . . . . . . . . . 67
Fig. 6-14, Normal Centered Dots (Good Sound Quality). . . . . . . . . . . . . . . . . . . . . . . 58
Fig. 6-15, Fuzzy (Low CNR and/or Low MER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Fig. 6-16, Circular Smear (Phase Noise). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Fig. 6-17, Corners Squeezed to Center (Gain Compression) . . . . . . . . . . . . . . . . . . . . 59
Fig. 6-18, Rectangular vs. Square (I-Q Imbalance) . . . . . . . . . . . . . . . . . . . . . . . . . 60
Fig. 6-19, Twisted or Skewed (Quadrature Distortion) . . . . . . . . . . . . . . . . . . . . . . . . 60
Fig. 6-20, GS7000 Hardware Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Fig. 6-21, Conguring Module Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Fig. 6-22, System Data Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Figures
8 018-345-B0-001, Rev. A (05/2016)
1.0 Introduction
1.1 Overview
The CMD-N transponder provides the ability to manage ber nodes and optical hubs through an existing cable modem
infrastructure. Contact an Alpha Technologies representative for a complete listing of supported ber nodes.
The transponder transmits data to a management system over the network’s existing DOCSIS® infrastructure, using
standard SNMP (Simple Network Management Protocol). Status monitoring information is compatible with ANSI/SCTE
HMS standards.
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 ber nodes
Can be network managed through the existing CMTS.
Allows remote control and conguration of the node.
Can provide a remote upgrade of node module rmware.
To the cable network infrastructure, the CMD-N transponder appears as a DOCSIS 2.0 cable modem. The transponder
is assigned an IP address like any other DOCSIS device on the DOCSIS network. The assigned IP address is used to
access the HMS status monitoring data via SNMP and the HMS MIBs.
For complete DOCSIS specications, see Cable Laboratories specications (Cable Labs Public DOCSIS SPECS) at
www.cablelabs.com.
1.0 Introduction, continued
9018-345-B0-001, Rev. A (05/2016)
CMD-N Package Parts List
Description Part Number Qty
CMD-N Cisco GS7000, 1.2GHz 018-345-20 1
CMD-N Cisco GS7000, 1GHz 66900-0722 1
Optional 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 1
10 dB pad N/A 1
Revision History - P/N 050-0201
Version Date Description of Changes and New Features
A 6 / 2009 Initial Release of Document
B 1 / 2010 Formatting and Graphic Updates
C 9 / 2010 Added Support for Cisco’s Optical Hub
D 3 / 2015 Formatting, Section 3.7 MIB Update, Other Minor Section Changes
1.2 Parts List
Table 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 History
This section contains revision tracking information such as document version, release date, and descriptions of changes
and new features.
Revision History - 018-345-B0
Version 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 rmware revision.
Table 1-2, Revision History
1.0 Introduction, continued
10 018-345-B0-001, Rev. A (05/2016)
1.4 Technical Support Contact Information
For technical issues, Cisco customers should call the following Cisco Technical Support and Customer Service Numbers.
Technical Support Contact Information
Region Centers Telephone and Fax Numbers
North America Atlanta, Georgia
Technical Support Customer Service
Toll-Free: 1-800-722-2009
Toll-Free: 1-800-722-2009
Local: 678-277-1120 (Press 3 at
the prompt)
Local: 678-277-1120
Fax: 770-236-5477
Email: customer-service@cisco.
com
Europe, Middle East,
Africa
Belgium
Technical Support Customer Service
Telephone #1: 32-56-445-197 Telephone: 32-56-445-444
Telephone #2: 32-56-445-155 Fax: 32-56-445-051
Fax: 32-56-445-061 Email: [email protected]
Japan Japan
Telephone #1: 81-3-5908-2153
Telephone #2: +81-3-5908-2154
Fax: 81-3-5908-2155
Korea Korea
Telphone: 82-2-3429-8800
Fax: 82-2-3452-9748
China (mainland) China
Telephone: 82-2-3429-8800
Fax: 82-2-3452-9748
All other Asia Pacic
countries & Australia
Hong Kong
Telephone: 852-2588-4746
Fax: 852-2588-3139
Brazil Brazil
Telephone: 11-55-08-9999
Fax: 11-55-08-9998
Mexico, Central
America, Carribean
Mexico
Technical Support Customer Service
Telephone: 52-351512599 Telephone: 52-55-50-81-8425
Fax: 52-3515152599
Fax: 52-55-52-61-0893
All other Latin
America countries
Argentina
Technical Support Customer Service
Telephone: 54-23-20-403340
ext: 109
Telephone: 770236-5662
Fax: 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 Connections
2.1 Overview
The 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 congured 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 Summary
Connector 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 conguration 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
Stat
These indicate transponder status. For details on the LEDs and their indications, see the
section titled “Checking the LEDs” presented in this manual.
Upstream Pad Socket
The 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 Specications
General
DOCSIS: Version 2.0
HMS Monitoring Protocol: SNMP v1
DOCSIS Monitoring Protocol: SNMP v1, v2, v3
RF Interface: Internal
RF Internal Padding: Congurable JXP pad for 15 dB Upstream
Ethernet Interface: RJ45
Operating Temperature: –40°C to +75°C
Humidity: 10% to 90% (non-condensing)
EMI/EMC: FCC Part 15 Class A, CE EN50022 Class A
RF Transmit/Receive
Tx Frequency Range: 5 to 42 MHz
Tx Output Power: +8 to +58 dBmV
Rx Frequency Range: 88 MHz to 860 MHz
Rx Input Level: –15 to +15 dBmV
Channel Bandwidth: 6 and 8 MHz
14 018-345-B0-001, Rev. A (05/2016)
3.0 Installation
Cable modem infrastructures are likely to have unique characteristics; therefore, Alpha Technologies strongly
recommends completely installing one transponder and making it operational before deploying the entire system
throughout 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 conguration data to the cable modem conguration le
Installing the transponder
Powering the transponder and checking the LEDs for status.
3.1 Provisioning the Transponders in the Network
Before installing CMD-N transponders, the transponder must be provisioned in the network 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 transponders 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 Information
Record the values of the network items below to facilitate the deployment process.
Network Worksheet
Network Item Value
Cable Modem MAC Address
Cable Modem IP Address
TFTP Server IP Address
Provisioning Server IP Address
Time of Day Server IP Address
DHCP Server IP Address
Table 3-1, Network Worksheet
3.3 Security
Different 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 ltering may have to be modied 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 Conguration File
Alpha Technologies strongly recommends you ensure that the cable modem conguration le has been successfully
modied and tested prior to deploying transponders into the system in quantity. The transponder manages SNMP lters
and trap destinations via the docsDevNmAccessTable.
To ensure the proper management of SNMP access, such as limiting access to certain SNMP managers or allowing
the transponder to send SNMP/HMS traps, the docsDevNmAccessTable must be populated via the cable modem
conguration le.
Additional OIDs may be added to further congure other options such as the transponder’s HTTP port, its username and
password conguration information (please refer to “6.0 CMD-N Web Interface”), or its support for telnet server access
(please refer to “5.3 Console Access”).
3.0 Installation, continued
16 018-345-B0-001, Rev. A (05/2016)
The following is a sample cable modem conguration le. Include only those OIDs that will provide the desired features
and functionality.
The conguration le 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 Conguration File Example
3.0 Installation, continued
17018-345-B0-001, Rev. A (05/2016)
3.5 Installing the CMD-N Transponder
The 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 congured 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.
3.0 Installation, continued
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
3.0 Installation, continued
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
3.0 Installation, continued
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:
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70

Alpha CMD-N Cisco GS7000 Technical Manual

Type
Technical Manual

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

Finding information in a document is now easier with AI