In certain cases, service providers have a private cloud which is separate from the public Internet. Within their environment they use PAT (Port Address Translation) to forward user traffic from their private cloud to the Internet. In these cases, the service provider will have a limited number of public IP address for NATing. When Oracle is deployed for an enterprise customer, if they select one of these providers for multiple Oracle client sites, there is the possibility that multiple Oracle Client WAN links could be PATed/NATed to the same public IP address. Previously, Oracle would validate/learn a path based on the source IP address of the received frame (at the NCN for example). The end result is that the first site brought online would function as expected, with a Oracle Path in the GOOD state. However, at the second Oracle Client site using the same public IP address, the Oracle Path would be in the DEAD state. To resolve this issue, this release has been enhanced to use the source IP address and source port for path learning validation. With this enhancement Oracle has expanded its ability to interoperate with multiple additional Service Provider WAN environments.

All WAN links which may reside behind the same public IP must have Autodetect Public IP enabled in the configuration under Sites > [Site Name] > WAN Links > [WAN Link] > Settings > Basic Settings, as shown below:

Remote sites other than the NCN will not be able to bring up paths on to a client using a shared public IP unless UDP Hole Punching is enabled in the configuration under Connections > [Site Name] > Conduits > [Conduit] > Local Site > WAN Links at the client sites which share the public IP, as shown below: