Network clients outside an Exalogic rack can only access one of multiple EoIB network addresses defined for a created vServer
(Doc ID 1611061.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Exalogic Elastic Cloud Software - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
You have an Exalogic rack deployed in a virtual configuration and have created a vServer with multiple EoIB addresses. However, since the network environment created by default for an Exalogic vServer is dependent on a single default gateway, network clients located outside of the rack cannot successfully access more than one of the defined EoIB addresses until additional routing rules have been established.
You may encounter this issue as a permanent or intermittent inability for a network client sitting on a network outside the Exalogc rack to establish an SSH connection or successfully ping one of a vServer's multiple EoIB IP addresses. When the issue occurs you will be able to successfully reach the IP address of the EoIB network that corresponds to the interface selected as the default gateway.
The default GATEWAY can be identified by executing by running "netstat -r" or "ip route", as shown below:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document