Check Firewall Settings
When setting up Oracle Communications Session Delivery ManagerOracle Communications Session Delivery Manager in your network, you may have a firewall between the clients (browsers, SOAP, REST etc.) and the OCSDM cluster, and a firewall between the OCSDM cluster and other devices.
Figure 1-2 OCSDM in your Network with a Firewall between the clients
Note:
You cannot have firewalls between the servers in a cluster.If firewalls exist on either side of the OCSDM cluster, ensure the ports listed in the following table are open. If your operating system comes with a firewall, you need to apply the same criteria. You must switch off the firewall in your operating system or ensure these ports are available.
Table 1-1 Communication Between OCSDM Cluster and Network Clients
| Port Number | Protocol | Service | Configurable | Affects Firewall? | Purpose |
|---|---|---|---|---|---|
| 8443 | TCP | HTTPS | N | Y | Apache port. HTTPS port for client/server communication. |
| 8080 | TCP | HTTP | N | Y | HTTP port for client/server communication. |
Table 1-2 Communication Between OCSDM Cluster and Network Devices
| Port Number | Protocol | Service | Configurable | Affects Firewall? | Purpose |
|---|---|---|---|---|---|
| 161 | UDP | SNMP | N | Y | SNMP traffic between the SDM server and the device. |
| 162 | UDP | SNMP | N | Y | SNMP trap reporting from the device to the OCSDM server. |
| 21 | TCP | FTP | N | Y | Used for file transfer. |
| 22 | TCP | SFTP/SSH | N | Y | Used for secure file transfer (such as Route Manager and LRT updates) and SSH sessions between OCSDM and southbound devices (For example, SBC). |
| 3001/ 3000 | TCP | ACP/ACLI | N | Y | Used by OCSDM to communicate with all versions of a device. |
Table 1-3 Communication Between OCSDM Servers in the Cluster
| Port Number | Protocol | Service | Configurable | Affects Firewall? | Purpose |
|---|---|---|---|---|---|
| 22 | TCP | SFTP | N | Y | Used to transfer files between OCSDM servers. |
| 1098 | TCP | RMI | N | Y | RMI Communication between host members in a cluster. |
| 1099 | TCP | RMI Lookup | N | Y | RMI registry port. Used for the RMI communication between host members in a cluster. |
| 8005 | TCP | HTTP | N | Y | Tomcat shutdown port used by the shutdown script. Can be blocked on a firewall because it is local to the OCSDM server. |
| 8009 | TCP | Apache | N | Y | Tomcat port. |
| 8088 | UDP | Coherence | N | Y | Used by the OCSDM Coherence REST application to handle HTTP requests on localhost and port 8088. |
| 9000 | TCP | Berkeley | N | Y | Berkeley database. |
| 61616 | TCP | Apache | N | Y | Message broker. |
Either port 8080 (HTTP) or port 8443 (HTTPS) must be open on the firewall, depending on which port you select between the network client and OCSDM server.
Note:
Ports are assigned dynamically through Remote Method Invocation (RMI) dynamic port allocation. If you are enabling and configuring iptables, all traffic must be allowed between servers in the cluster. Communication between clustered OCSDM servers must not be restricted.