Defining an Initial Configuration > Reviewing Port Settings for SDX Components

Reviewing Port Settings for SDX Components

If you use firewall software within your internal network, ensure that firewall settings allow traffic to and from components in your SDX environment. Table 16 lists the default port settings for SDX components.

For information about default port settings for applications in the SDX application library, see Chapter 1, Installing the SDX Applications in the SDX Application Library Guide.

 Table 16:  Default Port Settings for SDX Components  

 Component
 Type of Communication
 Default Port Setting

 Applications, such as portals, that use the SAE Common Object Request Broker Architecture (CORBA) remote application programming interface (API)

 CORBA remote API connections to the SAE.

 TCP 8801


 Cable modem termination system (CMTS) devices

 Connection requests.

 TCP 3918


 Sample residential portal with Tomcata

 Starting Tomcat server.

 TCP 8005


 Apache JServ Protocol (AJP) requests for Tomcat.

 TCP 8009


 Responses to incoming HTTP requests from Tomcat.
 This port is an alternative to port 80.

 TCP 8080)


 JBossb

 Remote method invocation (RMI) requests.

 TCP 1099


 Communications for the Java Naming and Directory Interface (JNDI).

 TCP 1100


 License server

 Messages from SAEs to the license server.
 All SAEs in a configuration must be able to reach the license server. 

 TCP 9000


 LDAP

 Communications between LDAP and other components in an SDX environment, such as the SAE, NIC, and SNMP.

 TCP 389


 Network information collector (NIC)

 Communications between the NIC host and components, such as portals, that use the NIC.
 All components that use NIC resolution must be able to reach the NIC host.

 TCP 8810


 RADIUS

 Communications between RADIUS and the SAE.

 UDP 1812


 Communications between RADIUS and the SAE for RADIUS accounting.

 UDP 1813


 Redirect engine

 Redirection requests.

 TCP 8800


 SAE

 Common Open Policy Service (COPS) connection from JUNOSe routers.

 TCP 3288


 Blocks Extensible Exchange Protocol (BEEP) connection from JUNOS routers.

 TCP 3333


 Session store data replication.

 TCP 8820


 SAE Web Admin

 Secure HTTP.

 TCP 8443


 SNMP agent

 SNMP communications between SNMP subagents and the master SNMP agent.

 UDP 8030


 SNMP get and set messages.

 UDP 161


 SNMP traps.

 UDP 162

Footnote: ^a For more information about ports that Tomcat uses, see http://jakarta.apache.org/tomcat

Footnote: ^b For more information about ports that JBoss uses, see http://www.jboss.org/products/jbossas

Footnote: In addition, we recommend that TCP port 123 be open for the Network Time Protocol (NTP). We recommend that you configure NTP to synchronize time on the network. See the documentation for the NTP server for your system.