Users Guide
Table Of Contents
- OpenManage Network Integration for SmartFabric Services User Guide Release 2.0
- Change history
- Overview of OMNI, SFS, VxRail, and PowerEdge MX
- SmartFabric Services
- OpenManage Network Integration
- OMNI vCenter integration
- Access the OMNI stand-alone portal
- Access the OMNI Fabric Management Portal
- OMNI Appliance Management user interface
- OMNI automation support for PowerEdge MX SmartFabric
- OMNI automation support for NSX-T
- OMNI support for SmartFabric instances
- Lifecycle management
- Troubleshooting
- Logs and support data for troubleshooting
- Verify OMNI VM connectivity
- Unable to add SmartFabric instance in OMNI
- Missing networks on server interfaces
- Unable to launch OMNI UI
- OMNI plug-in does not show service instance
- Unable to register the vCenter in OMNI
- OMNI is unable to communicate with other devices
- Timestamp not synchronized in OMNI
- Reset OMNI VM password
● Check the relationship status between the vCenter and service instances. For more information, see Relationship
information. If the relationship is not formed correctly, delete and reconfigure the SmartFabric instance and vCenter.
● If the southbound interface is a general ESXi server, create a server interface profile manually. If there is no server profile,
no relationship is created. For more information about creating server interface profile, see server interface.
● Ensure that the service instance and vCenter are in In Service mode. The automation is not enabled if any of the relevant
vCenters or SmartFabric instances is in Maintenance mode.
If the relationship status is correct and the automation is running, yet the issue persists, restart the automation service for the
respective vCenter. Restart the automation services for the vCenter from the OMNI UI, see OMNI Appliance Management UI.
After restart, OMNI synchronizes all the configurations again through automation.
Unable to launch OMNI UI
This information provides troubleshooting information when you are unable to launch OMNI plug-in from vCenter and as a
stand-alone UI.
Unable to launch OMNI plug-in from vCenter
Problem
Unable to launch OMNI plug-in from vCenter.
vCenter does not show the OMNI plug-in option in the menu even after the vCenter is registered with OMNI through OMNI
Fabric Management UI. vCenter also shows OMNI plug-in download errors, after the vCenter is registered with OMNI.
Causes
1. OMNI is not able to communicate with the vCenter due to SSL certificate errors.
2. vCenter could not resolve OMNI FQDN.
Resolution
1. Install a new SSL certificate, see Generate and Install SSL certificates.
NOTE: After installing the certificate, unregister and re-register the vCenter instance again.
2. Ensure that the DNS is configured for the vCenter and is reachable. Also, DNS should have forward and reverse lookup
configuration for OMNI FQDN or IP address.
If the problem still persists, try to unregister and register the OMNI appliance with vCenter again. For more information, see
Register vCenter with OMNI.
Unable to launch stand-alone OMNI UI
Problem
Unable to launch the OMNI VM as a stand-alone application.
Cause
● vCenter server network connection (ens160) IPv6 configuration is not set to Ignore.
● OMNI essential services are not running.
Resolution
● Enter the IPv6 configuration for vCenter server network (ens160) to Ignore. For more information, see Setup OMNI.
● Check if the OMNI essential services are running using Appliance management UI. If OMNI UI is not accessible, check the
OMNI management service status on the OMNI VM console. To check the services status:
1. From the OMNI management menu, enter the selection as 3. OMNI management service menu.
2. Select 4. Restart OMNI management service to restart all the database and web essential services.
NOTE: To restart the automation services, go to OMNI Appliance Management UI and restart the services.
Troubleshooting 185