F.3 Port Numbers and Protocols of Oracle Components
Table F-1 lists the port numbers and protocols used by components that are configured during the installation. By default, the first port in the range is assigned to the component, if it is available.
Table F-1 Ports Used in Oracle Components
Component and Description | Default Port Number | Port Range | Protocol | Used Only On Interconnect |
---|---|---|---|---|
The port number is assigned automatically during installation. You cannot view or modify it afterward. This port is used exclusively with the cluster interconnect, which is a private network that is physically separated from the public network, and uses dedicated hardware for the interconnect. | Dynamic | Dynamic | UDP | Yes |
Cluster Synchronization Service (CSSD) Node restart advisory messages fixed port. This port is used on all interfaces that have broadcast capability. Broadcast occurs only when a node eviction restart is imminent. | 42424 | Dynamic | UDP | Yes |
The port number is assigned automatically during installation. You cannot view or modify it afterward. This port is used exclusively with the cluster interconnect, which is a private network that is physically separated from the public network, and uses dedicated hardware for the interconnect. | Dynamic | Dynamic | UDP | Yes |
Grid Plug and Play (GPNPD) GPNPD provides access to the Grid Plug and Play profile, and coordinates updates to the profile among the nodes of the cluster to ensure that all of the nodes node have the most recent profile. | Dynamic | Dynamic | TCP | No |
Multicast Domain Name Service (MDNSD) Grid Plug and Play uses the mDNS process to locate profiles in the cluster, as well as by GNS to perform name resolution. The mDNS process is a background process on Linux and UNIX, and a service on Windows. | 5353 | Dynamic | UDP/TCP | No |
Shares the Oracle Net port and is configured during installation. To reconfigure this port, use Net Configuration Assistant to reconfigure the Oracle Net listener. See: | Default 1521, (same value as the listener) | modifiable manually to any available port | TCP | No |
Listening port for Oracle client connections to Oracle Connection Manager. You can configure Oracle Connection Manager after installation using Net Configuration Assistant. | 1630 | 1630 | TCP | No |
Oracle Clusterware Daemon (CRSD) CRS daemon (Oracle Cluster Ready Services Daemon) internode connection. The port number is assigned automatically during installation. You cannot view or modify it afterward. This port is used exclusively with the cluster interconnect. | Dynamic | Dynamic | UDP | Yes |
The port number is assigned automatically during installation. You cannot view or modify it afterward. This port is used exclusively with the cluster interconnect. | Dynamic | Dynamic | UDP | Yes |
Oracle Containers for J2EE (OC4J). The CRS Agent uses port 8888 locally to manage the lifecycle of the container. | 8888 23944 (11.2.0.3 and earlier; removed 11.2.0.4) | 8888 | TCP | No |
Oracle Enterprise Manager Database Console HTTP port for Oracle Enterprise Manager Database Control. It is configured during installation. "Changing the Oracle Enterprise Manager Database Console Ports" explains how to modify its port number. | 1158 | 5500–5519 | TCP/HTTP | No |
Oracle Enterprise Manager Database Console RMI port for Oracle Enterprise Manager Database Control. It is configured during installation."Changing the Oracle Enterprise Manager Database Console Ports" explains how to modify its port number. | 5520 | 5520–5539 | TCP | No |
Oracle Enterprise Manager Database Console JMS port for Oracle Enterprise Manager Database Control. It is configured during installation. "Changing the Oracle Enterprise Manager Database Console Ports" explains how to modify its port number. | 5540 | 5540–5559 | TCP | No |
Oracle Enterprise Manager RMI port for Oracle Enterprise Manager to interact with QoS over the public interconnect. | 23792 | Configured manually | RMI | No |
Oracle Grid Interprocess Communication (GIPCD) A support daemon that enables Redundant Interconnect Usage. | 42424 | Dynamic | UDP | Yes |
Oracle Grid Naming Service (GNSD) The Oracle Grid Naming Service daemon provides a gateway between the cluster mDNS and external DNS servers. Thegnsd process performs name resolution within the cluster. | 53 (public), Dynamic (interconnect) | 53 (public), Dynamic (interconnect) | UDP/TCP (public), TCP interconnect | No |
Oracle High Availability Services (OHASD) The Oracle High Availability Services (OHAS) daemon starts the Oracle Clusterware stack. This port is used exclusively with the cluster interconnect. | 42424 | Dynamic | UDP | Yes |
HTTP port for Oracle Management Agent, which is part of Oracle Enterprise Manager. It is configured during installation. "Changing the Oracle Management Agent Port" explains how to modify its port number | 3938 | 1830–1849 | HTTP | No |
Oracle Notification Services (ONS) Port for ONS, used to publish and subscribe service for communicating information about all Fast Application Notification (FAN) events. The FAN notification process uses system events that Oracle publishes when cluster servers become unreachable or if network interfaces fail. Use srvctlto modify ONS ports. If you do not specify the ONS port values, then the ONS daemon listener local port defaults to 6100, and the ONS daemon remote port defaults to 6200. | 6100 (local) 6200 (remote) | Configured manually | TCP | No |
Oracle Real Application Clusters The port number is assigned automatically during installation. You cannot view or modify it afterward. This port is used exclusively with the cluster interconnect. | Dynamic | Dynamic | UDP | Yes |
Allows Oracle client connections to the database over the protocol for Oracle Net. You can configure it during installation. To reconfigure this port, use Net Configuration Assistant. | 1521 | Port number changes to the next available port. Modifiable manually to any available port. | TCP | No |
The Oracle XML DB HTTP port is used if Web-based applications need to access an Oracle database from an HTTP listener. It is configured during installation, but you cannot view it afterward. "Changing the Oracle XML DB Ports" explains how to change its port number. | 0 | Configured manually | HTTP | No |
Oracle XML DB The Oracle XML DB FTP is used when applications need to access an Oracle database from an FTP listener. It is configured during installation, but you cannot view it afterward. "Changing the Oracle XML DB Ports"explains how to change its port number. | 0 | Configured manually | FTP | No |