Firewall Rules Between the Gateway and the Customer Network
The ports outlined in this table are required for accessing the Gateway customer
interfaces (command line and web interfaces) as well as ports required for
integrating syslog and user management email notifications.
Table 4 Firewall Rules Between the Gateway and the Customer Network
|
|
|
|
|
Customer User Desktop/Intranet
|
Gateway
|
ICMP Type 0 and 8
|
Optional: Used by customers to test connectivity to the
Gateway from their internal networks.
|
|
Gateway
|
Customer default gateway on DMZ
|
ICMP Type 0 and 8
|
Ping between the Gateway and the default router is temporarily
used during installation of the Gateway to confirm network
connectivity.
|
|
Customer User Desktop/Intranet
|
Gateway
|
TCP/22
|
Customer access to CLI for network and syslog configuration of
the Gateway.
|
|
Customer User Desktop/Intranet
|
Gateway
|
HTTPS/443
|
Customer access to Portal interface for administration of the
Gateway and access to services.
|
|
Customer User Desktop/Intranet
|
amr.oracle.com
Note -
This IP address may resolve to multiple working IP
addresses.
|
HTTPS/443
|
Provides authorization for customer access to the Gateway
portal.
|
|
Customer User Desktop/Intranet
|
login-ext.identity.oraclecloud.com
Note -
This IP address may fail over between Oracle data
centers.
|
HTTPS/443
|
Provides authentication for customer access to the Gateway
portal.
|
|
Gateway
|
Customer syslog server
|
UDP/514
|
Rule required if the customer enables the Gateway Audit
Logging feature.
|
|
Customer User Desktop/Intranet
|
Gateway ILOM
|
TCP/22
|
Customer access from ILOM to assist in failure
troubleshooting.
|
|
Customer User Desktop/Intranet
|
Gateway ILOM
|
HTTPS/443
|
Customer access from ILOM to assist in failure
troubleshooting.
|
|
Customer User Desktop/Intranet
|
Gateway
|
HTTPS (TCP/7799)
|
(Optional)
Users of the Oracle Advanced Monitoring and Resolution service
and the Oracle Lifecycle Support services can access a Reporting
Dashboard on the Gateway.
|
|