Concept Guide

● MST with instance id 62: All the SFS 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 interoperates with RSTP. STP is enabled for this
MSTI.
You can change the mode to MSTP once the fabric is created. When you change the mode, the whole fabric goes through a
reboot cycle and the new mode is set to MSTP.
NOTE: Changing the STP mode impact the traffic flow in the cluster.
When the mode is changed, MSTI is created and VLANS are assigned to the 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 STP on server facing ports still holds good.
You can enable MSTP or revert to RPVST using the Edit Default Fabric Settings option available in the SFS UI. Select STP
Mode as MST or Rapid PVST For more information, see Edit Default Fabric Settings.
NOTE: The default spanning-tree priority value that is configured on a SFS-enabled switch for VLANs or instance 0 is:
default priority for RPVST is 32769 and instance 0 priority for MSTP is 61440.
Networks
This section describes the following type of networks that you can create and associate these networks with the entities
present in a fabric:
● General purpose networks
● VXLAN networks
● L3 VLAN networks
● L3 Routed networks
● Multirack L3 VLAN network
NOTE:
You cannot configure this network using SFS GUI. This network template is applicable for NSX-T deployment
and you can configure this network using OMNI UI. For more information about this network type, see OpenManage
Network Integration for SmartFabric Services User Guide, Release 2.0.
You can create these networks using SFS GUI and then associated these networks with servers profiles, uplinks, or interfaces
for traffic flow. For more information, see Create a network.
General purpose networks
General purpose networks can be categorized as L2 VLAN networks in SFS L2 personality and L2 VXLAN networks in SFS L3
personality. In L3 personality, when you create a general purpose network, SFS automatically creates a virtual network (VXLAN)
corresponding to a VLAN network. This virtual network has one-to-one mapping with the network, for each VLAN there exists
a virtual network with VNI same as the VLAN ID. If you delete a VLAN network, it automatically deletes the associated VXLAN
network.
For example, if you create a general purpose network with VLAN ID 50, SFS creates a VLAN 50 and associated VXLAN network
with VNI 50.
VXLAN networks
VXLAN network extends L2 connectivity over an underlay L3 connected network. Association of VXLAN network to interface
creates a binding and associates this interface to VXLAN bridge. L3 VXLAN network supports asymmetric-IRB. Create a virtual
network template and a network template, and associate the virtual network template to network template.
● The virtual network template defines the VNET-ID.
● Network template defines the VLAN ID.
L3 VXLAN network is a VXLAN type of network that contains a list of IP addresses and an anycast IP address. Optionally,
you can specify DHCP relay addresses. L3 VXLAN network can be configured over a leaf switch. L3 VXLAN network can be
attached to an uplink. Each VLTi uplink interface contains an IP address that is allocated from the list of IP addresses that are
configured on the L3 VXLAN network.
L3 VLAN network
L3 VLAN network is used for L3 VLAN underlay. Specify:
● VLAN ID
58
Appendix