Cisco ONS 15800 Series DWDM Platforms

Discovering Unknown CMP IP Addresses

Document ID: 13561

Updated: Oct 01, 2006



If you do not know the IP address of the Control and Monitoring Processor (CMP), you can use the procedure in this document in order to avoid the need for a Return Material Authorization (RMA).



There are no specific requirements for this document.

Components Used

This document is not restricted to specific software and hardware versions.


Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Find an IP Address

In order to retrieve the IP address, you can use a crossed DB9 (female-to-female) cable to connect to the debug port of the CMP.

A crossed DB9 cable has these pin connections:

Signal 9-PINs Signal
Ground 5 <----> 5* Ground
Transmit 3 <----> 2 Receive
Receive 2 <----> 3 Transmit
RTS 7 <----> 8 CTS
DSR,CD 1,6 <----> 4 DTR
CTS 8 <----> 7 RTS
DTR 4 <----> 6,1 DSR,CD

* The ONLY wire that is not crossed.

Ensure that the connection speed is equal to 38400 bps for a Transaction Language 1 (TL1) agent or a Q3 agent.

For the proprietary agent, release 2.0.0 and later connects at 38,400 bps. Earlier releases connect at 19,200 bps.

The connection speed you require depends on the software agent currently loaded on the CMP. Newer releases of the software require 384000 bps and older releases require 19200 bps. Users must be able to connect to all CMPs with either 19200 bps or 384000 bps.


You can retrieve the IP address through either terminal emulation software or CPTK.

Terminal Emulation

Complete these steps in order to retrieve the IP address:

  1. Configure the terminal emulation with these values:

    • No flow control

    • 8 Bits

    • 1 Stop Bit

    You can also represent these values as N,8,1.

  2. Configure the emulation with local echo and Carriage Return/Line Feed (CR/LF) characters.

  3. Issue these commands:

    Note: Use CAPITAL letters.

    • LCION—The LCION command opens a CPLT session.

      However, when you issue this command, the CMP does not respond visually. Hence, you need local echo, which is normal.

    • 001PWD1,82,ROOT,WMUX—Logon as a superuser. The response is 001PWD1,82,ROOT,WMUX.

      If you receive no response, you must unplug the CMP and replace it in order to force a reload. Wait five minutes and restart the procedure from step 1.

    • 001GET1,5—Get the IP address. The response is 001GEA1,5 nnn.nnn.nnn.nnn, where nnn.nnn.nnn.nnn represents the IP address.

    • 001GET1,6—Get the IP subnet mask. The response is 001GEA1,6 nnn.nnn.nnn.nnn, where nnn.nnn.nnn.nnn represents the subnet mask.

    • 001GET1,8—Get the gateway IP address. The response is 001GEA1,8 nnn.nnn.nnn.nnn, where nnn.nnn.nnn.nnn represents the gateway address.

    • 001PWD1,83—Logout.

    During this process, after you log on, there are regular displays of 000NTF1,1002. 000NTF1,1002 appears every few seconds, which is normal, and is a CMP keep-alive action.


Complete these steps in order to retrieve the IP address:

  1. Connect to the debug port of the CMP with a crossed DB9 (female-to-female) cable.

  2. Start CPTK as normal, and connect to the system.

  3. When the system requests for a password, type WMUX (in CAPITAL letters).

  4. The normal window appears, but all slots are empty.

  5. From the Action menu, choose CMP Information.

    This procedure enables you to obtain the IP address of the CMP.

    You now have the required information to connect to the CMP through IP, and reset the IP address if necessary.


There is currently no verification procedure available for this procedure.


There is currently no specific troubleshooting information available for this procedure.

Related Information

Updated: Oct 01, 2006
Document ID: 13561