Cisco Transport Manager

The "Gateway Not Ready for Network Element" Error Message on Cisco Transport Manager

Document ID: 65372

Updated: Jun 30, 2005



This document describes one reason for the occurrence of the "Gateway Not Ready for Network Element" message on the Cisco Transport Manager (CTM) server. This message appears when you issue a Gateway/TL1 command in the Operational Support System (OSS) on the CTM server. This document also provides a procedure to troubleshoot the issue.



Cisco recommends that you have knowledge of these topics:

  • Cisco Transport Manager

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco Transport Manager version 4.6 and earlier

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.


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


CTM Gateway/TL1 is a CTM process that forwards autonomous messages and requests northbound TL1 messages to an OSS that collects alarms and conditions from the servers of multiple vendors. Occasionally, in response to a Gateway/TL1 command in the OSS system, this message appears:

Gateway Not Ready for Network Element

This message indicates that the CTM Gateway/TL1 has not established a connection, or has lost connection to the Gateway Network Element (GNE).


Complete these steps in order to solve this problem:

  1. Use the CTM client to confirm that the Operational State of the NE is “In Service” (IS), and the communication state is "Available". Complete these steps:

    1. Click the NE (see arrow A in Figure 1).

    2. Click the Status tab in the Network Element Properties pane (see arrow B in Figure 1).

    3. Verify the Operation State (see arrow C in Figure 1). If the Operation State displays "Out of Service", investigate the reason. Place the NE In Service if appropriate (see arrow E in Figure 1).

    4. Verify the Communication State (see arrow D in Figure 1). If the Communication State is "Unavailable", troubleshoot and resolve the unavailable state of the NE.

      Figure 1 – Network Element Property: Status


  2. Run the Trace Route test on the CTM server to confirm that IP connectivity exists between the CTM server and the NE. Here is the trace route format for CTM that runs on a UNIX system:

    traceroute <ip address>
  3. Verify whether you have configured the NE with the correct gateway on the CTM client. Check the IP address that appears before the NE IP address in the Trace Route you just performed. Verify whether the IP address belongs to another NE (and NOT to a router or switch). If so, that NE is the gateway for the first NE. Otherwise this NE is its own gateway.

  4. Click to highlight the target NE in the CTM client. The right pane displays the NE Properties. Complete these steps:

    1. Click the Address tab (see arrow A in Figure 2).

    2. Change the GNE ID appropriately, if required (see arrow B in Figure 2).

      Figure 2 – Network Element Property: Address


  5. Verify whether you have configured the correct user name and password for the NE in the CTM client. Complete these steps:

    1. Select Administration > Control Panel (see Figure 3). The control panel for CTM appears (see Figure 4).

      Figure 3 – Administration > Control Panel


    2. Click Security Properties (see arrow A in Figure 4).

      Figure 4 – Security Properties


    3. Select the correct NE model type on the right pane, for example, 15454, 15327, or 15600 (see arrow B in Figure 4).

    4. Verify whether the user name and password are correct in the Gateway/TL1 - NE Connection section (see arrow C in Figure 4).

  6. Place the NE Out Of Service (OOS), and then back In Service (IS) (see arrow E in Figure 1).

  7. Wait for about eight minutes for the connection to re-establish between the CTM TL1 Gateway and the NE before you retry the TL1 command.

Related Information

Updated: Jun 30, 2005
Document ID: 65372