API Guide

Fabric operations and life cycle management
Dell EMC Open Manage Network Integration (OMNI) is an efficient REST API-based plugin, integrated with VMware's vCenter.
The plugin enables vCenter to easily deploy and manage a large virtual network of VMs and physical underlay on a VxRail HCI
stack. Using OMNI, you can do day two operations and management of the hyper-converged fabric.
You can do the common lifecycle operations using OMNI.
● Upgrade OS10 software in a network fabric
● Replace a switch in a fabric
For more information about OMNI, see VMware Integration for VxRail Fabric Automation SmartFabric User Guide.
Configuring FEC using MSM
You can configure FEC on interfaces from MSM when the switch is in Fabric mode.
MSM sends the FEC value that is to be configured for the interface and this value is configured for the interface. This
configuration is not retained across breakout modes. Configuration of FEC from MSM for IOM in full-switch mode is not
supported.
The FEC configuration from MSM is supported for 25, 50, and 100G speeds and for uplink ports only in Smartfabric mode. The
FEC configuration from MSM is not supported for spinner ports(breakout FEM, virtual ports) and the server ports.
FEC has two parameters configured and negotiated. The configured FEC is the user configured value and the negotiated value
is the value that is negotiated based on optics and peer.
This feature is enabled only when the switch is in Fabric mode.
SFS Support for MSTP on Layer3 fabric
The default spanning tree mode in smart fabric services is Rapid-PVST.
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 (VLANs from 4001-4091).
● STP is enabled on all user created VLANs.
● STP is disabled on server facing port.
In case you need to inter-operate switches controlled by SFS to external switches which are running RSTP or MSTP, SFS has
an API to change the Global Fabric STP mode to MSTP. In this case SFS will create 2 reserved MSTIs:
● MST with instance id 63: Clustering control VLAN (VLAN 4000) is part of this instance. Spine switches are configured to
take over as STP root for this MSTI.
● MST with instance id 62: All the inter switch reserved VLANs (4001-4091) are part of this configuration. On this MSTI,
spanning tree is disabled.
● All user created VLANs are part of CST (default MST instance), which inter-operates with RSTP. STP is enabled for this
MSTI.
● STP is disabled at port-level for all server facing ports.
By default, the STP mode is rPVST+. You can change the mode to MSTP once the fabric is build out. When you change the
mode, the whole fabric goes through a reboot cycle and the new mode will be set as MSTP. This step is traffic impacting.
When the mode is changed, MSTi are created and VLANS are assigned to these MSTi. The CST is configured with STP priority
such that SFS controlled switches have lower priority to become a root bridge.
There is no change on existing STP behavior for SFS controlled entities because of this change. All other STP behaviors such as
Disabling of STP on server facing ports still holds good.
SmartFabric Services
133