Deployment Guide

SFS Master
SFS uses Keepalived protocol, running on VLAN 4000, to elect one in the fabric as a Master switch. Only a leaf switch can be elected as a
Master.
In a single SFS domain, there is only one Master switch at any given time, and the rest of the leaf switches are designated as the backup.
A new Master is elected from the backup switches when the Master fails to provide high-availability to the fabric.
NOTE: Spine switches cannot be elected as a Master node within SFS.
Master advertisement
Once a Master is elected, it initiates all applications to automatically build the network fabric. The Master VIP is advertised using mDNS
Avahi services for applications to automatically discover the fabric through inband networks.
SFS REST services
The SFS REST service is started on the Master node. Applications consuming or integrating with SFS use this REST service for day 2
fabric operations. Communication is performed with the fabric using the IPv6 VIP assigned to the SFS Master, or using the IPv4 out-of-
band Management IP of the Master.
A default REST_USER account is created to authenticate all REST queries. The default password is admin and it is recommended to
change this password through VxRail Manager or OMNI.
NOTE: OMNI communicates with SmartFabric REST Services through REST_USER account only.
Master high availability
SFS uses an internal distributed data store where all fabric configuration is saved. This data is synchronized with all backup switches
ensuring the Master, and the backup switches are always had the same view of the fabric. With a Master failover, the switch taking over
as the Master uses its internal data store to continue fabric operations.
When the fabric is expanded, the newly added switches receive all fabric policies from the SFS Master, once the switches are added to
the domain.
Preferred Master
You can select a designated set of leaf switches as the Preferred Master. When a Master is elected for a fabric, the switches that are
configured as Preferred Master have a higher priority to become the Master switch. If none of the switches are configured as the
Preferred Master, any other leaf switch can become the Master.
When fabric is expanded, newly added switches may come up and from a fabric among themselves, and elect a Master before they are
connected to the existing fabric. When the new fabric merges with the running fabric, Keepalived protocol elects a Master switch from
the new leaf switches joining the fabric which overwrites the configuration in the existing fabric. It is critical to ensure that the leaf nodes
in the existing fabric are set up to be Preferred Master before expanding the fabric to prevent this.
NOTE:
When you create an uplink using the SFS GUI or OMNI detects at least one uplink, the Preferred Master is
automatically set on all leaf switches in the fabric, then.
SFS domain or network fabric
8
SmartFabric Services