What is my Oracle Field Service IP?
Environment:
Oracle Field Service (OFS), All versions in legacy datacenters. All OCI-based instances, see IP Address Range.
Resolution:
Your interaction with OFS is accomplished by several end points: Login Portal (login.etadirect.com), API Portal (api.etadirect.com) and others (automatically defined/pre-defined), which depends on your location or legal agreement.
1. Login Portal (login.etadirect.com) and API Portal (api.etadirect.com) addresses are defined based on your location (country) using GEO IP, which belong to the following list and can be associated with any of them:
Datacenters |
IPs |
|
---|---|---|
Inbound (Customer->ORACLE) |
Outbound (ORACLE->Customer) |
|
London/ Slough |
141.145.57.64/27 141.144.12.192/26 |
141.145.57.24/29 |
Amsterdam |
140.86.57.0/27 130.162.1.64/26 |
140.86.57.64/29 |
Chicago |
129.152.171.128/27 129.152.199.64/26 |
129.152.170.96/29 |
Ashburn |
129.157.14.0/27 129.157.138.192/26 |
129.157.14.64/29 |
2. OFS service end point
In most cases your environment is behind AKAMAI, pinging your URL would return as an alias in the ksd.akamaiedge.net domain.
3. OFS Firewall IP
Note that you will not be able to ping either your host IP or OFS's Source IP as network commands are disabled for these. If OFS Support Team asks you to provide traceroute or ping to our systems, please provide this using the IPs below (based on your location or legal agreement):
Datacenters |
IP |
---|---|
London/Slough UKDC2 |
141.145.57.28 |
Amsterdam NLDC1 |
140.86.57.68 |
Chicago USDC2 |
129.152.170.100 |
Ashburn USDC6 |
129.157.14.68 |
4. SMTP used by OFS
Datacenters |
IP |
---|---|
London/Slough UKDC2 |
141.145.57.28 141.145.47.18 141.145.47.19 |
Amsterdam NLDC1 |
140.86.57.68 160.34.31.18 160.34.31.19 |
Chicago USDC2 |
129.152.170.100 160.34.15.18 160.34.15.19 160.34.15.20 160.34.15.21 |
Ashburn USDC6 |
129.157.14.68 129.152.47.20 129.152.47.21 |
Frequently Asked Questions
Q: Will my PROD and TEST environments have the same public IP address, or it will be different?
A: Those are going to be different Public IPs as we've got different certificates for different domains (*.etadirect.com, *.test.etadirect.com, etc)
Q: Are these IPs going to be fixed or dynamic?
A: Your environments will have an IP in the range of the Datacenter they are hosted on (Chicago or London). Both PROD and TEST will point to either Chicago or London, as these will act as Primary Datacenters. Please see above table to find out the IP ranges for each Datacenter (Inbound column).
Q: If something happens to the Primary DC and we have to move to Disaster Recovery DC (Failover), is the IP going to be the same or it will change?
A: Amsterdam and Ashburn will act as Disaster Recovery datacenters, so after failover your environments will have an IP in those DCs IP range.