Cheetah Transponder CMD-N GS7000 User Guide

Document Number: 050-0201
Version C
September 8, 2010
CMD-N Cisco GS7000 Transponder User Manual
NOTE: For detailed information about enabling Voice Over IP (VoIP) functionality, please refer to Cheetah
Technologies, LP document VoIP Test Point User Manual for Cheetah DOCSIS-based Transponders
and End-of-Line Devices (part number 050-0104).
CheetahTM is a trademark of Cheetah Technologies, LP

VELCRO is a registered trademark of Velcro Industries B.V.
DOCSIS is a registered trademark of Cable Television Laboratories, Inc.
All other trademarks and registered trademarks are the property of their respective owners.
The copyright and trade secret laws of the United States and other countries protect this material. It may not
be reproduced, distributed, or altered in any fashion by any entity, including other Cheetah Technologies
business units or divisions, without the expressed written consent of Cheetah Technologies, LP.
This document contains proprietary information that shall be distributed or routed only within Cheetah
Technologies and to its authorized clients, except with written permission of Cheetah Technologies, L.P.
Information contained within this document is subject to change without notice.
Document Number: 050-0201 Rev C (September 2010)
© 2010 Cheetah Technologies, LP All Rights Reserved.

PROPRIETARY – CHEETAH TECHNOLOGIES, LP AND AUTHORIZED CLIENTS ONLY
Page 2 of 62    Revision C Doc: 050-0201

  
TABLE OF CONTENTS
CHAPTER 1: Introduction .................................................................................................... 5

1.1 Overview ........................................................................................................................................................... 5
1.2 Parts List ........................................................................................................................................................... 6
1.3 Revision History................................................................................................................................................ 6
1.4 Technical Support Contact Information.......................................................................................................... 6
CHAPTER 2: Connections .................................................................................................... 8

2.1 Overview ........................................................................................................................................................... 8
2.2 Connector Summary ........................................................................................................................................ 9
2.3 CMD-N Transponder Specifications .............................................................................................................. 10
2.3.1 General ........................................................................................................................................... 10
2.3.2 RF Transmit/Receive ..................................................................................................................... 10
CHAPTER 3: Installation ................................................................................................... 11

3.1 Provisioning the Transponders in the Network ............................................................................................ 11
3.2 Your Network Information.............................................................................................................................. 12
3.3 Security ........................................................................................................................................................... 12
3.4 Cable Modem Configuration File................................................................................................................... 12
3.5 Installing the CMD-N Transponder................................................................................................................ 14
3.5.1 GS7000 Node Installation..............................................................................................................14
3.5.2 GS7000 Optical Hub Installation ...................................................................................................19
3.6 Configuring the transponder using the SA-HMS-FIBERNODEGS7000-MIB ............................................... 22
3.7 Module Firmware Download Using the CTLP-DOWNLOAD-MIB .................................................................. 24
3.8 Checking the LEDs ......................................................................................................................................... 25
CHAPTER 4: Provisioning the SNMP Manager .................................................................... 27

4.1 MIB Files ......................................................................................................................................................... 27
4.2 Acquiring the Transponders by the SNMP Manager.................................................................................... 28
CHAPTER 5: Using the Craft Port ....................................................................................... 29

5.1 Overview ......................................................................................................................................................... 29
5.2 Web Page Access ........................................................................................................................................... 29
5.3 Console Access .............................................................................................................................................. 29
CHAPTER 6: CMD-N Web Interface .................................................................................... 33

6.1 Overview ......................................................................................................................................................... 33
6.2 Configuring the sysname and syslocation OIDs ........................................................................................... 33
6.3 Configuration Pages....................................................................................................................................... 34
6.3.1 Configuration Data Page ................................................................................................................34
6.3.2 GS7000 Configuration Data Page ................................................................................................ 35
6.4 Status page for software information ........................................................................................................... 37
6.5 Status Page for Connection Information ...................................................................................................... 38
6.6 Status Page for the SNMP Event Log ........................................................................................................... 39
6.7 HMS Fiber Node Data Page........................................................................................................................... 40
6.8 HSIA Diagnostics Page: Ping Command ...................................................................................................... 41
6.8.1 Input parameters ........................................................................................................................... 42
6.8.2 Controlling the Ping Test................................................................................................................ 43
6.8.3 Test Results.................................................................................................................................... 43
6.8.4 Simultaneous Access..................................................................................................................... 44
6.8.5 HSIA Diagnostics Page: Traceroute Command ........................................................................... 44
6.8.6 Input Parameters ........................................................................................................................... 45
6.8.7 Controlling the Traceroute Test..................................................................................................... 45
6.8.8 Test Results.................................................................................................................................... 45
Revision C Doc: 050-0201    Page 3 of 62

 
6.8.9 Simultaneous Access..................................................................................................................... 46

6.8.10 Legal ............................................................................................................................................... 46
6.9 RF Constellation Page.................................................................................................................................... 47
6.9.1 Controls .......................................................................................................................................... 47
6.9.2 Downstream Data .......................................................................................................................... 47
6.9.3 Interpreting QAM Constellation Data by Visual Inspection ......................................................... 48
6.10 MTA Status Page ............................................................................................................................................ 53
6.11 MTA DHCP Page ............................................................................................................................................. 54
6.12 MTA Quality of Service (QoS) Page................................................................................................................ 55
6.13 MTA Provisioning Page................................................................................................................................... 56
6.14 MTA Event Log Page ...................................................................................................................................... 57
CHAPTER 7: Cable Pinout Details ...................................................................................... 58

7.1 Ethernet Cable................................................................................................................................................ 58
CHAPTER 8: Upgrading the CMD-N Firmware ...................................................................... 59
Index ............................................................................................................................... 60

  
CHAPTER 1: INTRODUCTION
1.1 OVERVIEW
The CMD-N transponder provides the ability to manage fiber nodes and optical hubs through an existing
cable modem infrastructure. Please see your Cheetah 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.
Figure 1. The CMD-N Transponder
The CMD-N transponder:

• Uses ANSI/SCTE HMS standards
• Measures analog or receives digital SCTE/HMS data from fiber nodes
• Can be network managed through your existing CMTS.
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.2 PARTS LIST

Table 1 lists the transponder and any other items that are available as an option. For damage or
discrepancies, please contact your Cheetah Technologies representative.
Table 1. CMD-N Package Parts List
Description Part Number Qty
CMD-N Cisco GS7000 66900-0722 1
Optional GS7000 RF Cable Kit (this kit is required for cable
modem downstream frequencies above 140 MHz) 66905-0340 1
Note: This Cable Kit is not required for Optical Hub Integrations.
0 dB pad N/A 1
10 dB pad N/A 1
1.3 REVISION HISTORY
This section contains revision tracking information such as document version, release date, and
descriptions of changes and new features.
Table 2. Revision History
Version Date Descriptions of Changes and New Features
A 6/2009 Initial release of document
B 1/2010 Formatting & Graphic Updates
C 9/2010 Added support for Cisco’s Optical Hub
1.4 TECHNICAL SUPPORT CONTACT INFORMATION

For technical issues Cisco customers should call the following Cisco Technical Support and Customer
Service Numbers in your area.
Region Centers Telephone and Fax Numbers
North America Cisco Services For Technical Support, call:
Atlanta, Georgia  Toll-free: 1-800-722-2009
United States  Local: 678-277-1120 (Press 2 at the prompt)
For Customer Service, call:
 Toll-free: 1-800-722-2009
 Local: 678-277-1120 (Press 3 at the prompt)
 Fax: 770-236-5477
 Email: customer-service@cisco.com
Europe, Belgium For Technical Support, call:
Middle East,  Telephone: 32-56-445-197 or 32-56-445-155
Africa  Fax: 32-56-445-061
 Telephone: 32-56-445-444
 Fax: 32-56-445-051
 Email: service-elc@cisco.com
Japan Japan  Telephone: 81-3-5908-2153 or +81-3-5908-2154
 Fax: 81-3-5908-2155

  
Region Centers Telephone and Fax Numbers

Korea Korea  Telephone: 82-2-3429-8800
 Fax: 82-2-3452-9748
 Email: songk@cisco.com
China (mainland) China  Telephone: 86-21-2401-4433
 Fax: 86-21-2401-4455
 Email: xishan@cisco.com
All other Asia Pacific Hong Kong  Telephone: 852-2588-4746
countries & Australia  Fax: 852-2588-3139
 Email: saapac-support@cisco.com
Brazil Brazil  Telephone: 11-55-08-9999
 Fax: 11-55-08-9998
 Email: fattinl@cisco.com or ecavalhe@cisco.com
Mexico, Mexico For Technical Support, call:
Central America,  Telephone: 52-3515152599
Caribbean  Fax: 52-3515152599
 Telephone: 52-55-50-81-8425
 Fax: 52-55-52-61-0893
 Email: sa-latam-cs@cisco.com
All other Argentina For Technical Support, call:
Latin America countries  Telephone: 54-23-20-403340 ext 109
 Fax: 54-23-20-403340 ext 103
 Telephone: 770-236-5662
 Fax: 770-236-5888
 Email: keillov@cisco.com
CHEETAH TECHNOLOGIES TECHNICAL SUPPORT
1-866-944-1482
cheetahsupport@cheetahtech.com
Cheetah Technologies, L.P.

381 Mansfield Avenue
Pittsburgh, PA 15220
www.cheetahtech.com

 
CHAPTER 2: 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
configured for different implementations. If the transponder is to be used in a GS7000 node then the 10
pad must be used. If the transponder is to be used in a GS7000 Optical Hub then the 0 pad must be
used. The locations of these items are shown in Figure 2 and Figure 3.
* The Craft port provides local access to the transponder. However, it is important to note that the Craft
port is a fully functional standard Ethernet port capable of providing all the functionality of any standard
Ethernet connection.
Downstream
Interface RF Cable
Connector Connectors
Label with LEDs

Transponder
Serial Number
Craft Port
Tamper
Sensor
Figure 2. CMD-N Transponder Connections

  
Upstream Pad
Socket with Pad
Installed
Figure 3. CM D-N Transponder Upstream Pad Location
2.2 CONNECTOR SUMMARY
Table 3. Connector Summary

Connector Description
The Forward (Downstream) RF1 cable is the physical connection to the forward RF -20dB test point of
DS RF1 CABLE optical receiver 1 (OPTRX1).
The Forward (Downstream) RF2 cable is the physical connection to the forward RF -20dB test point of
DS RF2 CABLE optical receiver 2 (OPTRX2).
The Craft port provides a local, physical connection to the transponder. In addition, the Craft port is a
CRAFT fully functional standard Ethernet port capable of providing all the functionality of any standard
Ethernet connection.
INTERFACE The Interface Connector is the physical connection point at which the transponder attaches to the
CONNECTOR node or optical hub.
TAMPER The Tamper Sensor provides an indication of physical tampering (opening of the node enclosure).
SENSOR
The CMD-N transponder includes six green LEDs:

· PWR
· DS
· US
LED Indicators · 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.
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 pad must be used. If the transponder is to be used in a
GS7000 Optical Hub then the 0 pad must be used.
Downstream
Pad Socket Note: If a pad with a value less than 10 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.

 
2.3 CMD-N TRANSPONDER SPECIFICATIONS
2.3.1 GENERAL
DOCSIS: Version 2.0

HMS Monitoring Protocol: SNMP v1
DOCSIS Monitoring Protocol: SNMP v1, v2, v3
RF Interface: Internal
RF Internal Padding: Configurable 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
2.3.2 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

  
CHAPTER 3: INSTALLATION
Cable modem infrastructures are likely to have unique characteristics; therefore, Cheetah Technologies
strongly recommends completely installing one transponder and making it operational before deploying
the entire system throughout your 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 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.
NOTE: Some provisioning systems require that the transponder’s MAC address be added to the CMTS prior
to installing the transponder to achieve full functionality.
Figure 4. A Typical Network

 
3.2 YOUR NETWORK INFORMATION

The following worksheet will aid you in gathering the network information you will need as you move
through the deployment process.
Table 4. 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
The deployment of a Cheetah DOCSIS-based transponder is similar to provisioning a standard subscriber

cable modem and MTA with certain exceptions, owing to the transponder being a test device. For
instance, care must be used when provisioning, such that it is not invoiced in the billing system or
mistakenly blocked. Cable operators will want to adapt the deployment strategy to fit their unique
operational landscape. The introduction of a new device type in the DOCSIS network touches several OSS
systems and disciplines whose participation is necessary for a successful and timely deployment.
3.3 SECURITY
Different security methods are used to ensure network integrity. Some common issues are:
• A subscriber account (where the transponder is the subscriber) may be required for each
transponder
• The transponder’s MAC address may have to be pre-loaded into the CMTS
• MAC filtering may have to be modified to allow MAC addresses starting with 00:10:3F:xx:xx:xx to
be registered and 00:26:97:xx:xx:xx to be registered
• For SNMP access, UDP ports 161 and 162 must not be blocked
• Firewalls must allow communication between the cable modem and the various servers.
3.4 CABLE MODEM CONFIGURATION FILE

Cheetah 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 CHAPTER 6: CMD-N Web Interface), or
its support for telnet server access (please refer to SECTION: 5.3 Console Access).
The following is a sample cable modem configuration file. Include only those OIDs that will provide the
desired features and functionality.

  
Figure 5. Cable Modem Configuration File Exam ple
NOTE: 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.

 
3.5 INSTALLING THE CMD-N TRANSPONDER

The following sections provide information for installing the CMD-N transponder in the following devices:
• GS7000 Node
• GS7000 Optical Hub.
Refer to the appropriate section for installing the CMD-N transponder into your particular hardware.
3.5.1 GS7000 NODE INSTALLATION

1. Remove the transponder from the shipping package.
2. Ensure the correct pad for the desired application is installed in the pad socket. For GS7000
Node installations, verify the use of the 10 pad in the transponder pad socket. If any other size
pad is in place (e.g., a zero (0) pad), replace it with the 10 pad as shown below.
Note: If a pad with a value less than 10 is used and the transponder is used in a GS7000 Node, there is a
risk the output power of the transponder may be too high for the node transmitter.
Figure 6. Upstream Pad Socket with Proper Pad Installed
3. Position the transponder so that the interface connector shown in Figure 7 aligns with the node's
interface connector shown in Figure 8.

  
Interface
Connector
Figure 7. Fiber Node Interface Connector
Fiber Node
Interface
Connector
Figure 8. Fiber Node Transponder Slot and Interface Connector
4. 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 Figure 9.

 
Transponder
Screw Locations
Figure 9. Transponder M ounting Screw Locations
5. If the downstream cable modem frequency is above 140 MHz, attach the Forward RF1 cable to
the Optical Receiver 1 -20 dB test point. Route the cable(s) appropriately within the node.
Please refer to Figure 10.
IMPORTANT: The cable must be inserted into the Optical Receiver 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 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.

  
Transponder RF1
Connection
Node RCVR 1
Connection
Figure 10. Transponder RF1 Cable Attachment Points
6. If the downstream cable modem frequency is above 140 MHz, attach the Forward RF2 cable to
the appropriate Optical Receiver 2 -20 dB test point. Route the cable(s) appropriately within the
node. Please refer to Figure 11.
IMPORTANT: 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.
Transponder RF2
Connection
Node RCVR 2
Connection
Figure 11. Transponder RF2 Cable Attachment Points

 
Figure 12. Completed Transponder Installation in the Node

  
3.5.2 GS7000 OPTICAL HUB INSTALLATION

1. Remove the transponder from the shipping package.
2. 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 (zero) pad in the transponder pad socket. If any
other size pad is in place (e.g., a 10 pad), replace it with the 0 pad as illustrated.
Figure 13. Upstream Pad Socket with Proper Zero Pad Installed
3. Position the transponder so that the interface connector shown in Figure 14 aligns with the
node's interface connector shown in Figure 15.

 
Interface
Connector
Figure 14. Optical Hub Interface Connector on CMD-N
Optical Hub
Interface
Connector
Figure 15. Optical Hub Transponder Slot and Interface Connector
4. 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 Figure 16.

  
Transponder
Screw Locations
Figure 16. Transponder M ounting Screw Locations

 
3.6 CONFIGURING THE TRANSPONDER USING THE SA-HMS-FIBERNODEGS7000-MIB

Before the transponder can monitor the node it will need to be setup for how the node is configured. This
can be accomplished by using either the SA-HMS-FIBERNODEGS7000-MIB or through the GS7000
Configuration Data page for the GS7000 node, but can only be accomplished through the GS7000
Configuration Data page for the GS7000 optical hub. This section describes how to configure the
transponder using the SA-HMS-FIBERNODEGS7000-MIB.
For information on how to configure the transponder by using the GS7000 Configuration Data page see
the section entitled, “GS7000 Configuration Data Page”.
The OIDs used to configure the node are listed in the following table:
Table 5. SA-HMS-FIBERNODEGS7000-MIB
Component Description
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.
saFnForwardConfig • threeXRx1-2-4FwdSeg(3) - Forward RF signal for each
(OID 1.3.6.1.4.1.1429.1.6.5.2.5) 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 Configures the power supply slots to indicate whether a power
(OID 1.3.6.1.4.1.1429.1.6.5.2.9.1.2) 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 Sets the time in seconds the A/B switch setting will be restored
(OID 1.3.6.1.4.1.1429.1.6.5.2.8) after power has been restored to the primary receiver.
The default is 9 and the range is 0-255.
saFnOpticalReceiverSlot Configures the receiver slots to indicate if a receiver is installed
(OID 1.3.6.1.4.1.1429.1.6.5.2.4.1.2) or not installed. Set the active slots to Mount and the slots, if
any, that do not have an installed receiver to Unmount.
saFnOpticalReceiverLoPwrLimit Sets the minimum threshold level for the input signal to the A/B
switch in mW. The default is 0.50 and the range is 0.25-2.40.
(OID 1.3.6.1.4.1.1429.1.6.5.2.4.1.4)
Note: When the saFnOpticalReceiverLoPwrLimit
(OID 1.3.6.1.4.1.1429.1.6.5.2.4.1.4) is set, the LOLO alarm
limit for the fnOpticalReceiverPower (OID
1.3.6.1.4.1.5591.1.5.5.1.2) is also set.
In the same respect, when the LOLO alarm limit is set for
the fnOpticalReceiverPower (OID 1.3.6.1.4.1.5591.1.5.5.1.2),
the saFnOpticalReceiverLoPwrLimit (OID
1.3.6.1.4.1.1429.1.6.5.2.4.1.4) is also set.
Because the accuracy of the
saFnOpticalReceiverLoPwrLimit is in hundredths and the
accuracy of the fnOpticalReceiverPower is in tenths, when
the value is set for the saFnOpticalReceiverLoPwrLimit,
the LOLO alarm limit for the fnOpticalReceiverPower will
be rounded to the nearest tenth.

  
saFnOpticalReceiverHiPwrLimit Sets the maximum threshold level for input signal to the A/B
switch in mW.
(OID 1.3.6.1.4.1.1429.1.6.5.2.4.1.3)
The default is 2.00 and the range is 0.25-2.40.
Note: This parameter is not implemented within the
transponder in versions less than 4.1.0.
When the saFnOpticalReceiverHiPwrLimit
(OID 1.3.6.1.4.1.1429.1.6.5.2.4.1.3) is set, the HIHI alarm
limit for the fnOpticalReceiverPower (OID
1.3.6.1.4.1.5591.1.5.5.1.2) is also set.
In the same respect, when the HIHI alarm limit is set for
the fnOpticalReceiverPower (OID 1.3.6.1.4.1.5591.1.5.5.1.2),
the saFnOpticalReceiverHiPwrLimit (OID
1.3.6.1.4.1.1429.1.6.5.2.4.1.3) is also set.
Although the saFnOpticalReceiverHiPwrLimit displayed
accuracy is to the hundredth, the actual accuracy is only
to the tenth.
The accuracy of the fnOpticalReceiverPower is in tenth, so

when the value is set for the
saFnOpticalReceiverHiPwrLimit, the HIHI alarm limit for
the fnOpticalReceiverPower will be truncated to display
tenths.
saFnReturnLaserSlot Configures the transmitter slots to indicate if a transmitter is
(OID 1.3.6.1.4.1.1429.1.6.5.2.2.1.2) installed or not installed. Set the active slots to Mount and the
slots, if any, that do not have an installed transmitter to
Unmount.

 
3.7 MODULE FIRMWARE DOWNLOAD USING THE CTLP-DOWNLOAD-MIB

With firmware version 4.1.0 and greater, the CMD-N transponder for the GS700 has the ability to
download firmware to Optical Amps and Optical Switches by using the CTLP-Download MIB (OID
1.3.6.1.4.1.2082.5.10.1).
Note: 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 during 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.
A firmware download to the modules can be accomplished in one of two ways, management style
download or provisioning style download.
To start a management initiated download, set the downloadModuleType, downloadServer, and
downloadFilename to the correct values. Then set the downloadAdminStatus to either startDownload(1)
or forceDownload(2).
To setup a provisioning style download so the transponder will use the module download information
supplied by the provisioning server during boot up or reboot, In the CM config file set the
downloadModuleType to 2, downloadServer, and downloadFilename to the correct values, and the
downloadAdminStatus to startDownload(1).
Note: If the provisioning style of download is desired it is strongly recommended to set the
downloadAdminStatus to startDownload(1) in the CM config file. If the downloadAdminStatus is set to
forceDownload(2) in the CM config file then upon every reboot the transponder will download the
firmware to all modules even if they are at the current version.
The following OIDs are used for the Module Download Feature:
• downloadServer (OID 1.3.6.1.4.1.2082.5.10.1.1.1) – 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.
• downloadModuleType (OID 1.3.6.1.4.1.2082.5.10.1.1.2) – The type of download to be executed.
Must be set to other(2). Type cm(1) is used for other integrations and is not applicable in this
instance.
• downloadFilename (OID 1.3.6.1.4.1.2082.5.10.1.1.3) – The file name of the software image to be
loaded into the device.. If the file is unknown and the OID is read, the returned value will be
(unknown).
• downloadAdminStatus (OID 1.3.6.1.4.1.2082.5.10.1.1.4) – Begins the download to the
module(s).
o 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.
o 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
downloadAdminStatus will report forceDownload if read.
o allowProvisioning(3) – Not supported in this application. Although this is not supported
for application and does not affect anything if set. It is also the default state of
downloadAdminStatus.
o ignoreProvisioning(4) – When set, firmware upgrade information will be disregarded.
After a download is completed the downloadAdminStatus will report ignoreProvisioning.
• downloadOperStatus (OID 1.3.6.1.4.1.2082.5.10.1.1.5) – Reflects the operational status of
the firmware download. The following are the possible states.
o Downloading(1) – Downloading the file to the transponder.
o Programming(2) – Programming of the module in progress.

  
o completeProvisioning(3) – Not supported in this application. Indicates the

provisioning upgrade has completed.
o completeManagement(4) – startDownload or forceDownload completed
successfully.
o completeWithExceptions(5) – Indicates the firmware download has completed but
one or more modules failed to download the firmware successfully.
o failedTftp(6) – Transfer of the file failed.
o failedCrc(7) – Firmware file Crc error.
o failed Timeout(8) – Device did not respond when firmware download attempted.
o Failed Other(9) – An unknown error occurred when attempting the firmware
download.
• downloadMessage (OID 1.3.6.1.4.1.2082.5.10.1.1.6) – A text message providing the latest
download status information.
3.8 CHECKING THE LEDS

The CMD-N transponder includes 6 green LEDs:
• Online • Pwr
• Elink • DS
• Stat • US
On initial power up, the LEDs will remain off for several seconds after which time the DS, US, and Online
LEDs will blink, in unison, 6 times. After this sequence completes, the LEDs indicate the status. The Pwr,
DS, US, Online, and Elink LEDS conform to the DOCSIS OSSI specification.
Figure 17. The CM D-N Transponder LEDs

 
Table 6. LED Status Summary

LED Function State Meaning
Power LED Off The transponder is switched off or is not functioning.
Pwr (Note: this LED is not tied
directly to line power) On The transponder is on.
Downstream LED: Indicates The transponder is scanning for a downstream DOCSIS

Blinking
status with respect to channel.
DS downstream scanning and
The transponder has locked onto and synchronized with
synchronization. On
a downstream DOCSIS channel.
Upstream LED: Indicates The transponder is obtaining upstream parameters and
Blinking
status with respect to is performing initial ranging.
US acquisition of upstream
parameters and initial The transponder has completed a successful initial
On
ranging. ranging sequence.
Online LED: Indicates status The transponder is currently involved in the IP

Blinking
with respect to the completion initialization process.
Online of the IP initialization process
and when the unit is The transponder has completed the IP initialization
On
operational. process and is operational.
CPE Link LED: Indicates A CPE device is not connected to the transponder's
Off
status with respect to the Ethernet port.
Elink bridging of data to and from a
CPE device connected to the Blinking The transponder is bridging data to/from a CPE device.
transponder's Ethernet port.
Status LED: Indicates the Data is not being transferred between the two
Off
presence or absence of data processors.
Stat
transference between the
transponder's two processors. Blinking Data is being transferred between the two processors.

  
CHAPTER 4: PROVISIONING THE SNMP MANAGER

4.1 MIB FILES
The following MIB (Management Information Base) files are required for the SNMP Manager to collect
data from the transponder. The files in Table 7 can be found on the Society of Cable Telecommunications
(SCTE) web site www.scte.org. The files in Tables 8 and 9 are provided by Cheetah Technologies or Cisco.
There are dependencies between MIB files, so compile them in the order shown in the following tables.
Table 7. Management Information Base (MIB) Files
Former
ANSI/SCTE # Title
HMS #
ANSI/SCTE 36 2002 HMS 028 SCTE-ROOT Management Information Base (MIB) Definitions
Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-ROOTS Management
ANSI/SCTE 37 2003 HMS 072
Information Base (MIB) Definition
Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-PROPERTY-MIB
ANSI/SCTE 38-1 2002 HMS 026
Management Information Base (MIB) Definition
Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-ALARMS-MIB
Management Information Base (MID) Definition
Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-COMMON-MIB
Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-FIBERNODE-MIB
Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-Transponder-Interface-
Bus(TIB)-MIB Management Information Base (MIB) Definition
ANSI/SCTE 131 2007 SCTE-HMS VOIP MIB
HMS VoIP Test Management Information Base (MIB) Definition SCTE-HMS-VOIP-MIB
ANSI/SCTE 85-3 HMS 118 SCTE-HMS-HE-OPTICAL-AMPLIFIER-MIB
ANSI/SCTE 85-4 HMS 119 SCTE-HMS-HE-OPTICAL-SWITCH-MIB
Table 8. Management Information Base (MIB) Files

Provider Title
Cheetah Technologies Lighthouse HMS Extensions MIB
Cheetah Technologies CTLP-DOWNLOAD-MIB
Cisco SA-HMS-FIBERNODEGS7000-MIB
Table 9. Additional Supported Management Information Base (MIB) Files

Title Title
BRCM-BFC-MGMT-MIB EtherLike-MIB
BRCM-CM-MGMT-MIB IF-MIB
BRCM-EMTA-MGMT-MIB IGMP-STD-MIB
BRCM-HTTP-MGMT-MIB IP-MIB
BRCM-SNMP-MGMT-MIB RFC1213-MIB
BRCM-SSH-MGMT-MIB SLED-MIB
BRCM-TELNET-MGMT-MIB SNMPv2-MIB
BRIDGE-MIB TOLLGRADE-HTTP-MGMT-MIB
DISMAN-PING-MIB TOLLGRADE-VOIP-ALERT-THRESHOLDS-MIB
DOCS-BPI2-MIB TOLLGRADE-VOIP-CONFIG-MIB
DOCS-CABLE-DEVICE-DRAFT-MIB TOLLGRADE-VOIP-LOG-MIB

 
Title Title
DOCS-CABLE-DEVICE-MIB TOLLGRADE-VOIP-MIB
DOCS-CABLE-DEVICE-TRAP-MIB TOLLGRADE-VOIP-ONDEMAND-MIB
DOCS-IF-MIB TOLLGRADE-VOIP-OPTIONS-MIB
DOCS-QOS-MIB TOLLGRADE-VOIP-REPORTS-MIB
DOCS-TEST-MIB TOLLGRADE-VOIP-TRAPS-MIB
ENTITY-MIB UDP-MIB
eSAFE-MIB USB-MIB
4.2 ACQUIRING THE TRANSPONDERS BY THE SNMP MANAGER
The transponder must first complete its initialization/registration from the Cable Modem configuration
file. The transponder will then send a warm start trap to the SNMP Manager (as specified in the cable
modem configuration file). This trap provides the SNMP Manager with the MAC and IP addresses of the
transponder and should, depending on the configuration of the manager software, initiate monitoring the
fiber node.

  
CHAPTER 5: USING THE CRAFT PORT

5.1 OVERVIEW
The 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 CHAPTER 6: 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 ACCESS

To access the transponder locally utilizing a web browser, follow the procedure outlined below.
Connect a standard CAT5 Ethernet cable between the transponder and a laptop or similar device.
Open the web browser.
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.
The transponder's home page will appear.
Please refer to CHAPTER 6: CMD-N Web Interface for more detailed information on using the
transponder's web interface.
5.3 CONSOLE ACCESS
NOTE: Console access is intended for use by factory-trained technicians and is not recommended for use
by technicians in the field.
IMPORTANT! 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 11). In addition, the default username and password may be altered if desired.
Table 10 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 11
contains a list of the values for the telnetIpStackInterfaces OID along with the definition of each value. Table
12 provides a matrix describing the settings of the different access options. Change these values as deemed
necessary.
Table 10. OIDs for Usernames, Passwords, Telnet Access for Console Access
Parameter OID Default
0x40 (hex)
telnetIpStackInterfaces 1.3.6.1.4.1.4413.2.2.2.1.1.1.1.0 (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 cheetah
telnetPassword 1.3.6.1.4.1.4413.2.2.2.1.1.1.3.0 cheetah

 
telnetServerControl 1.3.6.1.4.1.4413.2.2.2.1.1.1.4.0 1 (enabled)
Table 11. TelnetIpStackInterfaces OID Values and Descriptions

Value Setting
0xC0 CM Interface enabled and Craft port Interface enabled.
0x80 CM Interface enabled and Craft port Interface disabled.
0x40 CM Interface disabled and Craft port Interface enabled.
0x00 CM Interface disabled and Craft port Interface disabled.
Table 12. Telnet Access Matrix

telnetServerControl OID telnetIpStackInterfaces OID Result
Value Value
Telnet access is disabled and both interfaces
0 0x00
are disabled.
Telnet access is enabled and both interfaces
1 0x00
are disabled.
Telnet access is enabled, the CM interface is
1 0x40 disabled, and the Craft port interface is
enabled.
1 0x80 enabled, and the Craft port interface is
disabled.
1 0xC0 enabled, and the Craft port interface is
enabled.
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.
Using your telnet client software and IP address 192.168.100.1, establish a telnet session to the
transponder. The following screen will appear.
NOTE: If you have difficulty establishing communications with the transponder, try changing the laptop's
IP address value to 192.168.100.2 and its subnet mask value to 255.255.255.0.

  
Figure 18. Console Main Page
4. Press the Enter key. At the login prompt enter the appropriate user name (the default is
cheetah) and press the Enter key. Next, enter the appropriate password (the default is cheetah)
and press the Enter key. The following screen will appear.
Figure 19. Console Prompt Page
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 hms
directory. For additional information about the use of the console commands, please contact
Cheetah Technical Support at 1-866-944-1482.
Table 13 provides a list of the commands in the hms section available via console mode along with a
brief description of each command.
Table 13. Commands Available in the hms Section of Console Mode
Command Description
devices Displays the modules that have been discovered in the Fiber Node.
dumps Toggles the serial dump feature on and off.
images Displays the firmware image information.
rawio Displays the raw input and output values from the transponder's two processors.
smio Displays the status monitoring IO values.
Toggles the spidump feature on and off. The spidump data consists of the communications
spidump
information between the two processors.
spistats Displays the SPI statistics.
status Displays general transponder information (i.e., firmware version, IP addresses, etc.).

 
To switch to the hms section, type cd hms at the prompt and press Enter. The following screen
appears.
To display a listing of all of the available commands, type ? and press Enter.
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.

  
CHAPTER 6: CMD-N WEB INTERFACE

6.1 OVERVIEW
A web interface is available on the CMD-N transponder. The default port for HTTP traffic is port 80, but
can be configured to use other ports via the Cheetah 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 14. The port must be open to use
all of the features described here.
The interface can be accessed by typing the cable modem IP address of the transponder into your web
browser. The interface includes status data for the cable modem, the HMS transponder, High Speed
Internet Access (HSIA) diagnostics, and the MTA (Media Terminal Adapter) in VoIP systems.
Table 14. OIDs for Port Management

httpCMMgmtPort 1.3.6.1.4.1.2082.5.5.1.1.1.0 80
httpCPEMgmtPort 1.3.6.1.4.1.2082.5.5.1.1.2.0 80
httpCPU2MgmtPort * 1.3.6.1.4.1.2082.5.5.1.1.3.0 8008
* This parameter is not applicable to this transponder
NOTE: None of the pages automatically refresh, so the user must manually reload each one to view the most
current data.
6.2 CONFIGURING THE SYSNAME AND SYSLOCATION OIDS
It is also possible to configure the sysName (1.3.6.1.2.1.1.5.0) and sysLocation (1.3.6.1.2.1.1.6.0)

OIDs from the web interface. This feature is password protected. There are both Admin and User
usernames and passwords. Both usernames (Admin and User) have the authority to set sysName and
sysLocation. The passwords can be changed via the Broadcom httpMgmt MIB. The specific OIDs and
default values are shown below.
Table 15. OIDs for Usernames and Passwords for Web Interface Access
httpAdminId 1.3.6.1.4.1.4413.2.2.2.1.1.3.1.0 admin
httpAdminPassword 1.3.6.1.4.1.4413.2.2.2.1.1.3.2.0 cheetah
httpUserId 1.3.6.1.4.1.4413.2.2.2.1.1.3.3.0 cheetah
httpUserPassword 1.3.6.1.4.1.4413.2.2.2.1.1.3.4.0 cheetah

 
6.3 CONFIGURATION PAGES

To access the configuration page click the Config link at the top of the page.
6.3.1 CONFIGURATION DATA PAGE

If the Configuration Data page is not the active page, click the Configuration button in the left pane.
The Configuration Data page appears.
• To download a sysName and/or sysLocation to the transponder, enter a sysName and/or a
sysLocation in the appropriate fields and click the Apply button. After the Apply button is clicked a
login dialog will appear if the login process had not been performed previously during the current
session. After the login dialog appears enter the correct user name and password and click Ok.
• The Device Type displays the type of device the transponder is configured. FN is displayed for Fiber
Node.
• The Device combo box displays the different devices and network configurations the transponder
can be configured to operate within. The device that is displayed without the box extended is the
device the transponder is configured for. Choosing the appropriate device type is necessary to
ensure the device is properly controlled and monitored. The available options are the following:
o Cisco GS7000
o Cisco GS7000 Dual IP
To change the Device select the appropriate device type and then click the Apply button. After the
Apply button is clicked a login dialog will appear if the login process had not been performed
previously during the current session. After the login dialog appears enter the correct user name and
password and click Ok.
For additional information on Dual IP addressing, please refer to the DOCSIS Transponder Dual IP
Configuration Manual (document Number 050-0191).
Figure 20. Configuration Data Page

  
6.3.2 GS7000 CONFIGURATION DATA PAGE

Before the transponder can monitor the node it will need to be setup for how the node is configured. This
can be accomplished by using either the SA-HMS-FIBERNODEGS7000-MIB or through the GS7000
Configuration Data page for the GS7000 node, but can only be accomplished through the GS7000
Configuration Data page for the GS7000 optical hub. This section describes how to configure the
transponder through the GS7000 Configuration Data page.
For information on how to configure the transponder by using the SA-HMS-FIBERNODEGS7000-MIB see
the section entitled, “Configuring the transponder using the SA-HMS-FIBERNODEGS7000-MIB”.
If the GS7000 Configuration Data page is not the active page, click the GS7000 button in the left pane.
The GS7000 Configuration Data page appears.
Set the appropriate fields in the following table and then click the Apply button. After the Apply button
is clicked a login dialog will appear if the login process had not been performed previously during the
current session. After the login dialog appears enter the correct user name and password and click Ok.
Table 16. Node Configuration Options

Sets the GS7000 device type.
Node Type • deviceGS7000

• deviceGS7000opticalHubNode
• deviceGS7002opticalHub
The forward configuration of the node.
• oneX/twoXFwdSeg - Forward RF signal for all ports comes from one or two optical
receivers.
• fourXFwdSeg - Forward RF signal for each port comes from separate optical
receivers.
Forward Configuration • threeXRx1-2-4FwdSeg - 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 - 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.
Power Supply Slots The maximum number of power supplies that can be installed in the node. Set the
installed power supplies to Mount and the power supply, if any, that is not installed to
Unmount.
A/B Switch 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.
Receiver Slots 1-4 The maximum number of receiver slots or slots to the left of the transponder in the node
(Slots 3-6) or optical hub. Set the active slots to one of the following; Optical Receiver, Optical
Amplifier or Optical Switch. The slots, if any, that do not have a module installed, set
to Empty.
Lo Switching Limit The minimum threshold level for the input signal to the A/B switch. The default is 0.50
(mW) and the range is 0.25-2.40.
Note: When the Lo Switching Limit is set, the LOLO alarm limit for the
fnOpticalReceiverPower (OID 1.3.6.1.4.1.5591.1.5.5.1.2) is also set.
In the same respect, when the LOLO alarm limit is set for the
fnOpticalReceiverPower (OID 1.3.6.1.4.1.5591.1.5.5.1.2), the Lo Switching Limit is
also set.
Because the accuracy of the Lo Switching Limit is in hundredths and the accuracy
of the fnOpticalReceiverPower is in tenths, when the value is set for the
saFnOpticalReceiverLoPwrLimit, the LOLO alarm limit for the
fnOpticalReceiverPower will be rounded to the nearest tenth.

 
Hi Switching Limit The maximum threshold level for the input signal to the A/B switch. The default is 2.00
(mW) and the range is 0.25-2.40.
Note: This parameter is not implemented within the transponder in versions less
than 4.1.0.
When the Hi Switching Limit is set, the HIHI alarm limit for the
fnOpticalReceiverPower (OID 1.3.6.1.4.1.5591.1.5.5.1.2) is also set.
In the same respect, when the HIHI alarm limit is set for the
fnOpticalReceiverPower (OID 1.3.6.1.4.1.5591.1.5.5.1.2), the Hi Switching Limit is
also set.
The accuracy of both the Hi Switching Limit and the fnOpticalReceiverPower is
tenths.
Transmitter Slots 1-4 The maximum number of transmitter slots or slots to the right of the transponder in the
(Slots 8-11) node or optical hub. Set the active slots to one of the following; Return Laser, Optical
Amplifier or Optical Switch. The slots, if any, that do not have a module installed, set to
Empty.
Figure 21. GS7000 Configuration Data Page

  
6.4 STATUS PAGE FOR SOFTWARE INFORMATION

Select the Status tab to view details on the software running in the cable modem.
Figure 22. Status Page for Software Information

 
6.5 STATUS PAGE FOR CONNECTION INFORMATION

Click the Connection button to see detailed status information related to the current connection to the
CMTS.
See Note 1
See Note 2
Figure 23. Status Page for Connection Information
NOTE 1: Downstream Power has 18 dB internal padding.

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

  
6.6 STATUS PAGE FOR THE SNMP EVENT LOG

Click the Event Log button to view recent event log entries.
Figure 24. Status Page for the SNM P Event Log

 
6.7 HMS FIBER NODE DATA PAGE

Select the HMS tab to view HMS fiber node or optical hub data. The help button refers to a web page at
the Cheetah Technologies Corporate web site. Click on a link to view the parameters associated with that
particular module, or click the View All link to view all of the parameters at once.
The color of each module indicates the highest level of alarm present in that module at the time. Clicking
on the module displays the parameter(s) responsible for the alarm(s). The following is a list of the module
colors and their meanings.
• Dark Gray: The module is not present in the node or has not been configured to be monitored.
• Green: The module has no alarms.
• Yellow: The module has at least one parameter in the minor alarm state.
• Red: The module has at least one parameter in the major alarm state.
Figure 25. HMS Fiber Node Data Page

  
Figure 26. HMS Optical Hub Data Pages
6.8 HSIA DIAGNOSTICS PAGE: PING COMMAND

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

 
Figure 27. HSIA Diagnostics Page: Ping Command
6.8.1 INPUT PARAMETERS
Table 17. Input Parameters for the Ping Command

Input Parameters Descriptions
Target IP address or Either a standard IPv4 dotted-quad address is entered, or a host name. The address entered will be
Name unconditionally given to the DNS resolver; a dotted-quad will be resolved the same value, and a name
will be resolved to its IPv4 address.
The final IPv4 address to be pinged is shown in parenthesis beside the host field.
Ping from what There is a maximum of 3 choices, and these choices depend on what is available in the unit.
Source a. Cable Modem. Always available.
b. CPE. Available if the CPE stack is activated.
c. EMTA. Available if the VoIP stack is licensed and activated.
Number of Pings Range 1 to 100.

Ping Size Range 64 to 1518. 64 is the standard size.
Timeout Range 1 to 60 seconds. Standard value is 5 seconds.

  
6.8.2 CONTROLLING THE PING TEST

The Ping Test is controlled by the following buttons.
Table 18. Control Buttons on the Ping Screen
Button Description
Start Test Starts the ping test. Each of the values provided in the input fields is evaluated for validity.
• If the host name field is blank, the test will not proceed. (The exception is leaving it blank when a
previous name had been entered. In that case, that name will be used.)
• Range checking on the parameters. Any parameter out of range will be ignored, and the default
value used.
Any issues with the parameters will be displayed at the top of the results box.
When the test is started, the web page will begin to automatically refresh. Also, a message will be
displayed:
Ping in use from <source>; pkings xxx; size yyy; timeout zzz seconds
indicating the parameters actually in use. This message is also in the text box.
Abort Test Stops any ping test currently in progress.
Clear Results Clears the results window.
6.8.3 TEST RESULTS
Below the test control buttons is a text area that displays the results of the ping test. Any issues with the
parameters will be displayed at the top of the results box. During a test, the web page will automatically
refresh to show the current results. This refresh stops once the test is completed.
The results area permits the user to select results and copy them for pasting into another program. This
is accessed by standard web browser methods: either left-clicking in the box and pressing CTRL-A (select
all), or right-clicking in the box and clicking “Select all”, OR by simply using the mouse cursor, and
selecting those lines of interest. Copy is done via standard commands used on the system in question
(e.g., under Windows, use CTRL-C to copy.) Figure 23 shows a typical set of Ping results.
Pinging from Cable Modem: pings 25; size 64 bytes; timeout 5 seconds
Pinging cms-pit.tollgrade.com ...

Reply from 172.16.0.11: bytes= 64 seq=0 time=10 ms TTL=62
Ping statistics:
Pings sent: 25 (1 per second); Replies received: 25 (1 per second)
Bytes sent: 1600 (66 per second); Bytes received: 1600 (66 per second)
25 replies passed verification (0 failed)
Min time: 0 ms; Max time: 10 ms; Avg time: 6 ms; Total time: 24230 ms
Figure 23. Ping Results

 
6.8.4 SIMULTANEOUS ACCESS

Access by more than one user is possible; however, only a single test can be run at a time. When the
“Ping in use” message is displayed (see Section 6.8.2 Controlling the Ping Test), no other test can be
started. Through the use of a temporary cookie, only the original user can abort an active test.
6.8.5 HSIA DIAGNOSTICS PAGE: TRACEROUTE COMMAND
Click the Traceroute button to view the traceroute diagnostics page. The HSIA-Traceroute Web Interface
is accessed from the Connection form that is first displayed when the transponder is accessed.
Figure 28. HSIA Diagnostics Page: Traceroute Command

  
6.8.6 INPUT PARAMETERS
Table 19. Input Parameters for the Traceroute Command

Input Parameters Descriptions
Target IP address or Either a standard IPv4 dotted-quad address or a host name is entered. The address entered will be
Name unconditionally given to the DNS resolver; a dotted-quad will be resolved the same value, and a name
will be resolved to its IPv4 address. The final IPv4 address to be Tracerouted is shown in parenthesis
beside the host field.
Traceroute from what There is a maximum of 3 choices, and these choices depend on what is available in the unit.
Source a. Cable Modem. Always available
b. CPE. Available if the CPE stack is activated.
c. EMTA. Available if the VoIP stack is licensed and activated
Max Hops Range 1 to 255; default is 30. Also known as Max TTL, which is Maximum Time-To-Live.
Traceroute Size Range 0 to 1518. 0 is the standard size, resulting in packets of 40 bytes (inclusive of all overhead).
Port Port to use. Standard is 33434 as the initial port.
6.8.7 CONTROLLING THE TRACEROUTE TEST
The Traceroute Test is controlled by the following buttons.

Table 20. Control Buttons on the Traceroute Screen
Button Description
Start Test Starts the Traceroute test. Each of the values provided in the input fields is evaluated for validity.
• If the host name field is blank, the test will not proceed. (The exception is leaving it blank when a
previous name had been entered. In that case that name will be used.)
• Range checking on the parameters. Any parameter out of range will be ignored, and the default
value used.
Any issues with the parameters will be displayed at the top of the results box.
When the test is started, the web page will begin to automatically refresh. Also, a message will be
displayed:
Traceroute in use from <source>; max TTL xxx; size yyy; port nnnnn
indicating the parameters actually in use. This message is also in the text box.
Abort Test Stops any traceroute test currently in progress.
Clear Results Clears the results window.
6.8.8 TEST RESULTS
Below the test control buttons is a text area that displays the results of the Traceroute test. Any issues
with the parameters will be displayed at the top of the results box. During a test, the web page will
automatically refresh to show the current results. This refresh stops once the test is completed.
The results area permits the user to select results and copy them for pasting into another program. This
is accessed by standard web browser methods: either left-clicking in the box and pressing CTRL-A (select
all), or right-clicking in the box and clicking “Select all”, OR by simply using the mouse cursor, and
selecting those lines of interest. Copy is done via standard commands used on the system in question
(e.g., under Windows, use CTRL-C to copy.)

 
Figure 29 shows a typical set of Traceroute results.
Figure 29. Traceroute Results
6.8.9 SIMULTANEOUS ACCESS

Access by more than one user is possible; however, only a single test can be run at a time. When the
“Traceroute in use” message is displayed (see Section 6.8.7 Controlling the Traceroute Test), no other
test can be started. Through the use of a temporary cookie, only the original user can abort an active
test.
6.8.10 LEGAL
The code in use to implement Traceroute originates from a third party. It had been modified slightly by
Broadcom, and subsequently modified by Cheetah Technologies to suit our purposes. The header of the
file is included here.
* Copyright (c) 1990, 1993

* The Regents of the University of California. All rights reserved.
*
* This code is derived from software contributed to Berkeley by
* Van Jacobson.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
* 3. All advertising materials mentioning features or use of this software
* must display the following acknowledgement:
* This product includes software developed by the University of
* California, Berkeley and its contributors.
* 4. Neither the name of the University nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
Figure 30. Traceroute Legal Agreement

  
6.9 RF CONSTELLATION PAGE

Select the RF tab to access the Constellation page. The QAM constellation map is useful in diagnosing
line problems that might otherwise go undiagnosed. This section provides useful information on how to
interpret the information presented in the QAM map. The interface consists of a panel of variables and
the constellation map itself. At the device level, the QAM functionality is only supported by Cheetah
products that are based on the ECMM technology.
Figure 31. Constellation Page
6.9.1 CONTROLS
• Run — Start the sampling of data by pushing the Run button. The unit will acquire 100 samples and
then stop.
• Stop — Use the Stop button to end the sampling.
6.9.2 DOWNSTREAM DATA

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

 
6.9.3 INTERPRETING QAM CONSTELLATION DATA BY VISUAL INSPECTION

The usefulness of the QAM constellation comes in the ability to recognize common shapes and
configurations within the map. Examples of the data shown in the table below are illustrated in the
figures that follow.
Table 21. QAM Constellation Shape Summary
Shape Focus Impairment Description
Individual
cells and Dots are centered in the individual QAM quadrants. The
Normal
entire QAM QAM constellation has a uniform square shape.
constellation
Low CNR
Individual Individual cells of QAM constellation contain a fuzzy and
and/or
cells diffused pattern.
Low MER
Individual cells of QAM constellation contain diffused hollow

Individual Coherent circles or “doughnuts”. This indicates an interfering carrier
cells Interference and shows the effect of not allowing the carrier to ever reach
the proper point in the target range.
Individual cells contain a complete and fairly uniform smear

Individual Gaussian up to all decision boundaries, and is usually caused by
cells Noise improper system setup, too many amplifiers in a cascade,
damaged/ overheated hardware, and/or low power.
Entire QAM QAM constellation consists of smeared, concentric, circular

Phase Noise
constellation patterns.
QAM constellation looks uniformly square, but the outside

Entire QAM Gain
corners appear to be “smashed” toward center of grid
constellation Compression
(compression in the RF plant).
I-Q Imbalance
Entire QAM Overall appearance of QAM constellation is rectangular
in the
constellation rather than the desired square shape (square inequality).
Modulator
Entire QAM Quadrature Overall appearance of QAM constellation has a twisted or

constellation Distortion skewed parallelogram shape.

  
Figure 32. Sam ple QAM Constellation—Norm al Centered Dots (Good Sound Quality)
Figure 33. Sample QAM Constellation—Fuzzy (Low CNR and/or Low M ER)

 
Figure 34. Sample QAM Constellation—"Doughnuts" (Coherent Interference)
Figure 35. Sam ple QAM Constellation—Gaussian Noise

  
Figure 36. Sample QAM Constellation—Circular Smear (Phase Noise)
Figure 37. Sample QAM Constellation—Corners Squeezed to Center (Gain

Compression)

 
Figure 38. Sam ple QAM Constellation—Rectangular vs. Square (I-Q Im balance)
Figure 39. Sam ple QAM Constellation—Twisted or Skewed (Quadrature Distortion)

  
6.10 MTA STATUS PAGE

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

 
6.11 MTA DHCP PAGE

Click the DHCP button to view the Dynamic Host Communications Protocol (DHCP) information.
Figure 41. MTA DHCP Page

  
6.12 MTA QUALITY OF SERVICE (QOS) PAGE

Click the QoS button to view the Quality of Service (QoS) parameters.
Figure 42. M TA Quality of Service (QoS) Page

 
6.13 MTA PROVISIONING PAGE

Click the Provisioning button to view the MTA provisioning details.
Figure 43. MTA Provisioning Page

  
6.14 MTA EVENT LOG PAGE

Click the Event Log button to view the MTA Event Log information.
Figure 44. MTA Event Log Page

 
CHAPTER 7: CABLE PINOUT DETAILS

7.1 ETHERNET CABLE
Following is the pin number configuration chart for the Ethernet cable.
Table 22. Pin Number Configuration Chart for the Ethernet Cable
Pin Name
1 Transmit +
2 Transmit -
3 Receive +
4 Unused
5 Unused
6 Receive -
7 Unused
8 Unused

  
CHAPTER 8: UPGRADING THE CMD-N FIRMWARE
The firmware in the CMD-N transponder can be upgraded in the same fashion as any other DOCSIS-
compliant cable modem. Please refer to the Cable Labs CM-SP-OSSIv2.0 and SP-BPI+ specifications for
details on secure software download.

 
INDEX
050-0191, 34 CTRL-A, 43, 45

192.168.100.1, 29, 30 CTRL-C, 43, 45
192.168.100.2, 30 deployment strategy, 12
-20 dB test point, 16, 17 device type, 12
255.255.255.0, 30 DHCP button, 54
66900-0722, 6 DHCP Server IP address, 12
66905-0340, 6 digital data, 5
abort an active test, 44, 46 DNS resolver, 42, 45
Admin, 33 docsDevNmAccessTable, 12
alarm, 22, 23, 35, 36, 40 DOCSIS, 2, 5, 12
color codes, 40 device, 5
analog data, 5 network, 5, 12
ANSI standards, 5, 27 OSSI specification, 25
billing system, 12 specifications, 5
boot up, 24 dotted-quad address, 42, 45
Broadcom, 33, 46 Download MIB, 24
Cable Labs, 5, 59 downloadAdminStatus, 24
cable modem, 5, 11, 12, 28, 33, 37 downloadFilename, 24
configuration file, 12 downloadMessage, 25
infrastructure, 5 downloadModuleType, 24
cable modem configuration file, 12, 28 downloadOperStatus, 24
Cable Modem IP address, 12 downloadServer, 24
Cable Modem MAC address, 12 downstream cable modem frequency, 16, 17
cable network, 5 Downstream data, 47
infrastructure, 5 Downstream Power, 38
cable operators, 12 DS RF 1 port, 16, 17
Cable Pinout, 58 DS RF 2 port, 16, 17
CAT5 Ethernet cable, 29, 30 Dual IP, 34
craft port, 8, 9, 29 Configuration Manual, 34
Channel Bandwidth, 10 establishing communications with the transponder,
Cheetah Technical Support, 31 30
Cisco, 6, 27, 34 Ethernet cable
Technical Support, 6 pins, 58
CMTS, 5, 11, 12, 38 Ethernet connector, 8
requested transmit level, 38 EURO DOCSIS, 5
Commands Available in the hms Section of event log, 39, 53, 57
Console Mode, 31 button, 39, 57
config file, 24 entries, 39
configuration chart, 58 firewalls, 12
configuration data firmware download, 24, 25
adding, 11 forceDownload, 24, 25
Configuration Data page, 22, 34, 35 forward RF -20dB test point, 9
configuration file, 11, 12 Forward RF signal, 22, 35
Connection button, 38 Forward RF2 cable, 17
Connection form, 41, 44 Frequency Range, 10
Connection Information, 38 GS7000 Configuration Data page, 22, 35
Connector Summary, 9 GS7000 Node, 14
Console Access, 29 Installation, 14
console mode, 31 GS7000 Optical Hub, 8, 9, 14, 19
constellation map, 47 Installation, 19
Constellation page, 47 header, 46
Contact Information, 7 help button, 40
CPE stack, 42, 45 Hi Switching Limit, 36
Craft Port, 8, 29, 30, 33 HMS 023, 27
CTLP-DOWNLOAD-MIB, 24, 27 HMS 024, 27

  
HMS 026, 27 node, 8, 9, 14, 15, 16, 17, 19, 22, 28, 35, 36, 38,
HMS 027, 27 40
HMS 029, 27 Node Configuration Options, 35
HMS 050, 27 node interface connector, 8
HMS 072, 27 OIDs, 12, 22, 24, 29, 33
HMS Fiber Node Data Page, 40 configuring, 33
hms section, 31, 32 default values, 33
HMS status monitoring data, 5 Optical Amps, 24
HMS tab, 40 optical hub, 5, 9, 22, 35, 36, 40
hmsinit file, 28 Optical Switches, 24
hmsinit.ini, 28 optical tamper sensor, 8
home page, 29 OPTRX1, 9
host name, 42, 43, 45 OPTRX2, 9
HSIA Diagnostics Page, 41 OSS, 12
HSIA tab, 41 Output Power, 10
HSIA-Ping Web Interface, 41 Outside Plant Status Monitoring, 27
HSIA-Traceroute Web Interface, 44 Overview, 5
HTTP port, 12, 33 pads, 6, 8, 9, 10, 14, 19, 38
HTTP traffic, 33 node vs. optical hub, 9
httpAdminId, 33 output power warning, 9
httpAdminPassword, 33 socket, 8
httpUserId, 33 use in nod vs. optical hub, 8
httpUserPassword, 33 Parameters, 42
Hybrid Fiber/Coax, 27 Parts List, 6
initialization, 28 password, 12, 29, 31, 33, 34, 35
Input Level, 10 pin numbers, 58
input parameters, 42, 45 ping, 41, 42, 43, 44
installation, 11 ping test, 42, 43
recommendations, 11 aborting, 43
interface connector, 14, 19 results, 43
Interface Connector, 9, 15, 20 starting, 43
internal padding, 38 power, 25
interpreting qam constellation data, 48 power supplies, 22, 35
Introduction, 5 power supply, 40
IP address, 5, 12, 24, 30, 33, 42, 45 power supply data, 40
IPv4, 42, 45 Powering the transponder, 11
LED Status Summary, 26 pad socket, 9
LEDs, 8, 9, 11, 25 provisioning, 11, 12
Legal, 46 button, 56
Lighthouse HMS Extensions MIB, 27 details, 56
login dialog, 34, 35 Server IP address, 12
login process, 34, 35 SNMP Manager, 27
MAC address, 11, 12, 28 systems, 11
MAC filtering, 12 Transponders, 11
Management Information Base, 27 QAM constellation, 47, 48
management initiated download, 24 shape summary, 48
management system, 5 QAM functionality, 47
Media Terminal Adapter, 33 QAM map, 47
MIBs, 5, 27, 33 QoS button, 55
mother board, 15, 20 Quality of Service (QoS), 55
MTA, 12, 33, 53, 54, 55, 56, 57 RCVR 1, 16, 17
Status Page, 53 RCVR 2, 16, 17
tab, 53 reboot, 24
network, 11, 12 refresh, 33, 43, 45
integrity, 12 registration, 28
management, 5 revision tracking, 6
provisioning, 11 RF output level, 38
typical, 11 RF Transmit/Receive, 10
worksheet, 12 RF1 cable, 9, 16

 
RF1 Cable Attachment Points, 17 telnet console session, 29

RJ-45, 8 telnet server access, 12, 29
Run button, 47 temporary cookie, 44, 46
SA-HMS-FIBERNODEGS7000-MIB, 22, 27, 35 test control buttons, 43, 45
SCTE 36 2002, 27 TFTP Server IP address, 12
SCTE 37 2003, 27 threshold level, 22, 23, 35, 36
SCTE 38-1 2002, 27 Time of Day Server IP address, 12
SCTE 38-2 2002, 27 timeout, 42
SCTE 38-3 2002, 27 Cheetah Technologies
SCTE 38-4 2002, 27 Corporate web site, 40
SCTE 38-7 2002, 27 Traceroute, 44, 45, 46
SCTE HMS standards, 5 button, 44
SCTE-HMS, 27 Command, 45
secure software download, 59 legal agreement, 46
security, 12 results, 46
server Test, 45
security issues, 12 transponder status, 9
shipping package, 14, 19 traps, 12, 28
Simple Network Management Protocol, 5 UDP ports, 12
Simultaneous Access, 44, 46 characteristics, 11
SNMP, 5, 12, 27, 39 University of California, 46
filters and trap destinations, 12 Upgrading the CMD-N Firmware, 59
Manager, 28 Upstream attenuation, 38
Society of Cable Telecommunications (SCTE), 27 Upstream Pad Socket, 14, 19
software, 28, 37, 46 Upstream RF path, 38
download, 59 upstream signal
Specifications, 10 attenuating, 8
startDownload, 24, 25 User, 2, 33
status, 5, 9, 11, 25, 33, 38, 53 username, 12, 29, 31, 33, 34, 35
LEDS, 8 View All link, 40
Status page, 37, 53 VoIP, 2, 33, 42, 45
Status tab, 37 warm start, 28
Stop button, 47 web browser, 29, 33, 43, 45
subscriber account, 12 Web Page Access, 29
sysLocation, 33, 34 Windows, 43, 45
sysName, 33, 34 www.cablelabs.com, 5
tamper sensor, 8, 9 www.cheetahtech.com, 7
telnet access, 29, 30 www.scte.org, 27
Telnet Access Matrix, 30
∇ ∇ ∇

  

Cheetah Transponder CMD-N GS7000 User Guide

Uploaded by

Copyright:

Available Formats

Cheetah Transponder CMD-N GS7000 User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cheetah Transponder CMD-N GS7000 User Guide

Uploaded by

Copyright:

Available Formats

Document Number: 050-0201

CheetahTM is a trademark of Cheetah Technologies, LP

© 2010 Cheetah Technologies, LP All Rights Reserved.

Page 2 of 62 Revision C Doc: 050-0201

CHAPTER 1: Introduction .................................................................................................... 5

CHAPTER 2: Connections .................................................................................................... 8

CHAPTER 3: Installation ................................................................................................... 11

CHAPTER 4: Provisioning the SNMP Manager .................................................................... 27

CHAPTER 5: Using the Craft Port ....................................................................................... 29

CHAPTER 6: CMD-N Web Interface .................................................................................... 33

Revision C Doc: 050-0201 Page 3 of 62

6.8.9 Simultaneous Access..................................................................................................................... 46

CHAPTER 7: Cable Pinout Details ...................................................................................... 58

CHAPTER 8: Upgrading the CMD-N Firmware ...................................................................... 59

Page 4 of 62 Revision C Doc: 050-0201

Figure 1. The CMD-N Transponder

The CMD-N transponder:

Revision C Doc: 050-0201 Page 5 of 62

1.2 PARTS LIST

1.3 REVISION HISTORY

1.4 TECHNICAL SUPPORT CONTACT INFORMATION

Page 6 of 62 Revision C Doc: 050-0201

Region Centers Telephone and Fax Numbers

CHEETAH TECHNOLOGIES TECHNICAL SUPPORT

Cheetah Technologies, L.P.

Revision C Doc: 050-0201 Page 7 of 62

Label with LEDs

Figure 2. CMD-N Transponder Connections

Page 8 of 62 Revision C Doc: 050-0201

Figure 3. CM D-N Transponder Upstream Pad Location

2.2 CONNECTOR SUMMARY

Table 3. Connector Summary

The CMD-N transponder includes six green LEDs:

Revision C Doc: 050-0201 Page 9 of 62

2.3 CMD-N TRANSPONDER SPECIFICATIONS

DOCSIS: Version 2.0

Tx Frequency Range: 5 to 42 MHz

Page 10 of 62 Revision C Doc: 050-0201

3.1 PROVISIONING THE TRANSPONDERS IN THE NETWORK

Figure 4. A Typical Network

Revision C Doc: 050-0201 Page 11 of 62

3.2 YOUR NETWORK INFORMATION

Table 4. Network Worksheet

The deployment of a Cheetah DOCSIS-based transponder is similar to provisioning a standard subscriber

3.4 CABLE MODEM CONFIGURATION FILE

Page 12 of 62 Revision C Doc: 050-0201

Figure 5. Cable Modem Configuration File Exam ple

Revision C Doc: 050-0201 Page 13 of 62

3.5 INSTALLING THE CMD-N TRANSPONDER

3.5.1 GS7000 NODE INSTALLATION

Figure 6. Upstream Pad Socket with Proper Pad Installed

Page 14 of 62 Revision C Doc: 050-0201

Figure 7. Fiber Node Interface Connector

Figure 8. Fiber Node Transponder Slot and Interface Connector

Revision C Doc: 050-0201 Page 15 of 62

Figure 9. Transponder M ounting Screw Locations

Page 16 of 62 Revision C Doc: 050-0201

Figure 10. Transponder RF1 Cable Attachment Points

Figure 11. Transponder RF2 Cable Attachment Points

Page 2 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 3 of 62

Page 4 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 5 of 62

Page 6 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 7 of 62

Page 8 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 9 of 62

Page 10 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 11 of 62

Page 12 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 13 of 62

Page 14 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 15 of 62

Page 16 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 17 of 62

Page 18 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 19 of 62

Page 20 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 21 of 62

Page 22 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 23 of 62

Page 24 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 25 of 62

Page 26 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 27 of 62

Page 28 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 29 of 62

Page 30 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 31 of 62

Page 32 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 33 of 62

Page 34 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 35 of 62

Page 36 of 62    Revision C Doc: 050-0201

Revision C Doc: 050-0201    Page 37 of 62

Page 38 of 62    Revision C Doc: 050-0201