Users Guide

● vCenter server network (ens160) is not assigned with correct port-group during deployment.
● IP addresses assigned to interfaces of OMNI are on the docker private network (172.16.0.0/16).
Resolution
● Ensure that ens160 is connected to the vCenter server network properly during OMNI deployment. For more information,
see Setup OMNI.
● Change the docker private network configuration, see Configure docker private network.
OMNI is unable to communicate with other devices
Problem
OMNI appliance is unable to communicate with any external devices.
Causes
When there is a conflict between the default OMNI docker private network and any other network to which OMNI is connected,
OMNI cannot communicate with the devices in that network.
The conflicts occur when:
● The ens160 and ens192 interfaces have IP addresses assigned from the docker private network (172.16.0.0/16).
● Any external entity such as vCenter, SFS instance, OME-Modular, NSX-T, NTP server, DNS server, and so on, which has IP
address that is assigned from the docker private network.
● OMNI is connected to a larger network in which one or more subnetworks IP range overlaps with the docker private
network.
Resolution
Change the docker private network configuration, see Configure docker private network.
NOTE: OMNI appliance reboots after the docker private network IP address is changed.
Timestamp not synchronized in OMNI
Problem
Logs and events timestamp details are not synchronized with the current data center.
Cause
OMNI does not have the proper NTP server configuration.
Resolution
Check the NTP server configuration in the OMNI appliance. Apply the correct configuration, if required. To check and change
the NTP server setting:
Troubleshooting
187