This document describes the pinouts used for making a management cable for the Cisco 600 series Customer Premises Equipment (CPE). The cable allows the user to manage and configure the Cisco 600 from a Windows PC running HyperTerminal. This document specifically covers PCs that have a communications port (COM port) with a DB-9 serial port connector and the Cisco 600 CPE, which has an RJ-45 serial port.
For more information on document conventions, see the Cisco Technical Tips Conventions.
There are no specific prerequisites for this document.
The information in this document is based on the hardware versions below.
The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.
The following is a typical management cable shipped with the Cisco 600 CPE.
Using the required connectors and cable, build a management cable using the following diagram as a guide.
When you finish building the management cable, follow the steps below to properly use it.
Connect the cable's DB-9 female connector to the DB-9 (male) serial COM port of your PC.
Connect the cable's RJ-45 male connector to the management port (labeled "MGMT") of your Cisco 600 CPE.
Configure your terminal access program (such as HyperTerminal in Windows) with the following settings:
Press Enter until you see the prompt (such as cbos>, modem1> or usa>). When you see the prompt, the PC and CPE are communicating.
Note: If the computer has only a DB-25 serial port, a DB-9 to DB-25 adapter is also needed. Also, the same cable can be used to connect a dumb terminal to the Cisco 600 management port.
|| Data Carrier Detect (CD)
|| Receive Data (RD)
|| Transmitted Data (TD)
|| Data Terminal Ready (DTR)
|| Signal Ground (GND)
|| Data Set Ready (DSR)
|| Request To Send (RTS)
|| Clear To Send (CTS)
|| Ring Indicator (RI)
There is currently no verification procedure available for this configuration.
There is currently no specific troubleshooting information available for this configuration.