Users Guide
Table Of Contents
- OpenManage Network Integration for SmartFabric Services User Guide Release 2.1
- Contents
- About this guide
- Change history
- Overview of OMNI, SFS, VxRail, and PowerEdge MX
- OpenManage Network Integration
- OMNI vCenter integration
- Access the OMNI stand-alone portal
- Access the OMNI Fabric Management Portal
- OMNI Appliance Management user interface
- SmartFabric management with OMNI
- OMNI feature support matrix
- View SmartFabric instance overview
- View fabric topology
- Manage switches in a fabric
- SmartFabric bulk configuration
- Configure server interface profile
- Configure and manage uplinks
- Configure networks and routing configuration
- Configure global settings for SmartFabric
- View fabric events and compliance status
- OMNI automation support for PowerEdge MX SmartFabric
- OMNI automation support for NSX-T
- Lifecycle management
- Troubleshooting
- Troubleshooting tools
- 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
NOTE: The sudo password is the same as the password set for the admin user.
NOTE: Root user is disabled by default. To set the password to enable root user, use the OMNI VM console CLI menu. You
can only access root user through the console.
Setup OMNI
This information describes how to set up the OMNI appliance with the required network interface configurations.
NOTE: The OMNI initial configuration setup can be performed using the vCenter OMNI VM console only.
Dell Technologies recommends checking the docker private network setting before setting up OMNI to avoid any conflict with
any of the external networks to which OMNI is connected.
The OMNI default docker IP address is 172.16.0.1/25. If there is a network conflict, OMNI cannot communicate with the other
entities. The conflicts occur when:
● The ens160 and ens192 interfaces have IP addresses assigned from the docker private network (172.16.0.0/25).
● Any external entity such as vCenter instance, SFS instance, OME-Modular, NSX-T has IP address that is assigned in 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.
To avoid the conflict, change the docker private network setting, see Configure docker private setting.
Network interface profile configuration
1. Select 0. Full Setup.
22
OpenManage Network Integration