The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco ONS 15454 nodes use TCP/IP to communicate with a variety of devices, such as Cisco Transport Controller (CTC) and Cisco Transport Manager (CTM). This document summarizes the port number usage for TCP/UDP to create proper filtering.
Note: The information in this document is subject to change in future software and hardware releases.
Cisco recommends that you have knowledge of these topics:
Cisco ONS 15454.
Introduction to TCP/IP.
The information in this document is based on these software and hardware versions:
Cisco ONS 15454.
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.
The Timing, Communications and Control (TCC), or TCC2 or TCC+ cards facilitate the TCP/IP connectivity. The types of devices in this list communicate with the ONS 15454 nodes:
SNMP management station
Ports are grouped based on the type of services, and the information currently available. Port numbers are listed for both ends of the sessions for TCP and UDP. TCP is implied if UDP is not specified.
When the client port number is a random number, it appears as any. The port number on ONS 15454 appears as NE:port number, if the port number is fixed. If a client device is not specified, it appears as ANY.
When you deploy TCP/IP filtering, you must evaluate the filters in the lab first to determine whether all necessary services are still available.
This port is for HyperText Transfer Protocol (HTTP) access.
In the next few sections, * represents a fixed port number that you can configure. ** represents a proxy-port in the range between 10240 and 12288.
This port is for Common Object Request Broker Architecture (CORBA) command connection. The default is 57790. You can configure this port to the Standard IANA IIOP Port (683), or a user-defined constant.
This port is for CORBA event and alarm connection. Although this port is dynamically allocated by default, you can configure this port.
This port enables you to set up and control the proxy.
This port is meant for HTTP and CORBA for proxy targets.
This port is for CORBA event and alarm connection from proxy targets.
This port is dynamic (as per the current functionality), but you can make this port static. In order to use a fixed CORBA Listener port on CTM Server 3.0 complete these steps:
Install CTM Server 3.0.
Log on as root to the Solaris machine where CTM Server is installed.
Change the directory to /opt/CiscoTransportManagerServer/bin.
Edit the jne454.sh file to add this user property before the line "Xbootclasspath": Dong.orb.iioplistenerport=<Port Number> e.g. –Dong.orb.iioplistenerport=5555.
Caution: Save the original jne454.sh file before you modify it. An incorrectly modified jne454.sh file will make your NEs unavailable in CTM.
Start the CTM Server.
CTC:any NE:port IIOP
NE:any CTC:port IIOP
You can configure either port in the CTC.INI (Windows) or .ctcrc (Unix) to be:
Standard IANA IIOP port (683).
Software Activate and Revert Diagnostics:
NE:any CTC/CTM: 9500
Note: This port is dynamic (9500 to 9550) in CTM 3.0 and later.
In release 3.3 and later, HTTP (TCP port 80) handles file transfers.
ANY: 161 NE: 162