Exalogic Virtual: Newly Created vServers Having Only 1 VNIC Causing Issues Of Unable to SSH To vServers
(Doc ID 1986564.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Exalogic Elastic Cloud Software - Version 18.104.22.168.2 to 22.214.171.124.2
In Exalogic Virtual Release 126.96.36.199.2 issue of unable to SSH to newly created vServers is observed.
Looking into the issue further newly created vServers are having only 1 VNIC instead of 2 VNICs. In this case Exalogic Eight Rack running Exalogic Virtual release 188.8.131.52.2 was being used. So the newly created vServers should be having 2 VNICs. 1 VNIC each on 2 IB NM2-GW Switches.
The issue of only 1 VNIC existing can be verified by checking the GUID's of the newly created vServers on both the NM2-GW IB Switches.
Verification can be done by following methods.
- Get the GUID's of the newly created vServer by looking into the vm.cfg file. And then look for the GUID on the NM2-GW IB Switches. This can be done by running "showvnics" command on the IB Switches and see if the GUID of the vServer is present.
- Run "mlx4_vnic_info -l" command on the newly created vServer. This command should show 2 VNIC's in case of Eight rack 1 VNIC each on both the IB NM2-GW switches. In this case the command was returning only 1 VNIC.
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