Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Port Settings for SRC Components

 

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

Table 1: Default Port Settings for SRC 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

Diameter server

Communications between the MX Series router and the Diameter server.

TCP 3868

Sample residential portal with Tomcat

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)

JBoss

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 SRC environment, such as the SAE, NIC, and SNMP.

TCP 389

Network Time Protocol (NTP)

Communications between the NTP server and the C Series Controller.

TCP 123

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 routers running JunosE Software.

TCP 3288

Blocks Extensible Exchange Protocol (BEEP) connection from routers running Junos OS.

TCP 3333

BEEP with Transport Layer Security (TLS)

TCP 3434

Session store data replication.

TCP 8820

SAE Web Admin

Secure HTTP.

TCP 8443

SNMP agent

SNMP communications between SNMP subagents and the master SRC SNMP agent.

UDP 8030

SNMP get and set messages.

UDP 161

SNMP traps.

UDP 162

SSH

Secured connection to a C Series Controller.

TCP 22

TELNET

Connection to a C Series Controller.

TCP 23

TACACS

Communications between the TACACS server and the C Series Controllers.

TCP 49

We recommend that you configure NTP to synchronize time on the network. See the documentation for the NTP server for your system.