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
Default client control traffic network
SFS sets up a second overlay network that is called client control network for VxRail integrated solutions. When a VxRail node
is discovered, it is automatically added as a tagged member of this network. SFS also enables the mDNS Avahi service on this
network for master advertisement and fabric discovery by integrated solutions. The SFS Master virtual IP for VXLAN network is
advertised. The VIP address is fde1:53ba:e9a0:cccc:0:5eff:fe00:1100 is fixed and not user configurable.
VLAN 3939 is used as the default client control VLAN for this VXLAN network. Although you can change the VLAN associated
with this, it is not recommended to change it for VxRail integrated solution deployments.
Spanning-tree protocol
SFS uses RPVST+ as the default spanning tree protocol to build leaf and spine switches.
Spanning-tree protocol is disabled for VXLAN networks. SFS automatically creates user networks as VXLAN networks in the
fabric. For a Layer 2 uplink from the fabric to the external network, the uplink ports in the fabric are configured as VXLAN
access interfaces and spanning-tree BPDUs are not sent to the external network.
SFS support for MSTP on L3 fabric: By default, the STP mode is RPVST+. You can change the mode to MSTP once the
fabric is built from SFS UI. When you change the mode, the whole fabric goes through a reboot cycle and the new mode is set
as MSTP.
NOTE: Changing the mode impacts traffic in the SFS as fabric reboots.
The spanning tree behavior for Layer3 fabric is as follows:
● STP is enabled on Cluster control VLAN (VLAN 4000). The spine switches are configured to take over the STP root role.
● STP is disabled on all inter leaf-spine VLANs and leaf-leaf VLAN (4001-4091).
● STP is enabled on all user created VLANs.
● STP is disabled on server facing port.
NOTE:
VLANs used for setting up the leaf and spine eBGP peering are automatically set up to prevent loops while having
nonblocking connections between the leaf and spine switches.
SFS and OMNI supported solutions
OMNI 2.0 with the SmartFabric Services OS10 release supports the following qualified solutions. See the Solutions Support
Matrix for the latest supported versions for all the qualified solutions. :
Table 4. Qualified solutions
Qualified Solutions Dynamic discovery Onboarding type vCenter/Day 2 automation
VxRail Yes Automatic Yes
PowerEdge MX NA NA Yes
PowerStore X (ESXi) Yes Import from Fabric or vCenter Yes
PowerStore T Yes Import from Fabric No
Isilon front-end/PowerScale No Manual No
Other devices running ESXi No Import from vCenter or Manual Yes
Other devices running
Windows or Linux-based
Operating Systems
No Import from Fabric Yes
NOTE: In PowerEdge MX, the servers are discovered and onboarded through OME-Modular.
NOTE: Other devices can be supported provided they meet the industry Ethernet standards and are compatible with
SmartFabric-enabled switches.
14 SmartFabric Services