Users Guide

Unable to register the vCenter in OMNI
Problem
Unable to register the vCenter in OMNI.
Causes
● vCenter server network (ens160) is not assigned a correct port-group during deployment.
● IP addresses assigned to the OMNI interfaces (ens160 and ens192) exist on the same network as of docker default private
network (172.16.0.0/25).
● DNS entries with two or more FQDN names for a vCenter IP address.
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.
● Retain only one FQDN and IP address mapping for a vCenter in the DNS entry.
OMNI is unable to communicate with other devices
Problem
OMNI appliance is unable to communicate with any external devices.
Causes
When the OMNI docker default network range conflicts with the IP address of other entities to which OMNI is connected.
The conflict occurs when:
● The ens160 and ens192 interfaces have IP addresses from the same network as that of docker default network
(172.16.0.0/25) of OMNI.
● The IP address assigned to any external entity such as vCenter, SFS instance, OME-Modular, NSX-T, NTP server, DNS
server, or DHCP server exists on the same network as that of the docker default network of OMNI.
● OMNI is connected to a larger network in which the IP range of one or more subnetworks overlaps with the docker default
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
159