Users Guide
Configuring FEC using OME-M
You can configure FEC on interfaces from OME-M when the switch is in Fabric mode.
OME-M 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 OME-M for IOM in full-switch mode is not
supported.
The FEC configuration from OME-M is supported for 25, 50, and 100G speeds and for uplink ports only in Smartfabric mode.
The FEC configuration from OME-M 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.
On OS10 switches, FEC is configured by default based on the media that is connected. For 25G AOC and SR transceivers, the
default FEC mode is CL108-RS. If the peer device such as a storage controller does not support CL108-RS, but supports only
CL74-FC, the ports do not come up. Auto negotiation does not configure the FEC settings correctly. For the ports to come up,
you must manually change the FEC settings on the OS10 switch to CL74-FC using the OME-M UI.
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.
You can enable MSTP or revert back to RPVST using the web-UI. To enable MSTP or revert back to RPVST:
1. In the web-UI, click the Edit Default Fabric Settings link. The Edit Default Fabric Settings window appears.
2. In the STP Mode field, select the MST or Rapid PVST option.
3. Click OK. Depending on the option that you select either MSTP is enabled or the configuration is reverted back to RPVST.
NOTE:
The default user-configurable spanning-tree priority value that is configured on a Layer3 fabric enabled switch for
VLANs or instance 0 is as follows: default priority for RPVST is 32769 and instance 0 priority for MSTP is 61440.
SmartFabric commands
You can enter SmartFabric Services show commands from the OS10 CLI to view SmartFabric configuration information,
including:
● SmartFabric cluster role (master or backup) and cluster member information
142
SmartFabric Services