Deployment Guide

SFS domain or network fabric is interchangeable terminology, and the fabric consists of all switches directly connected to form a single
logical network fabric. The L3 fabric is automatically assigned ID 100 and this ID cannot be changed. The fabric name and description are
automatically assigned, but can be changed through the SFS user interface.
Rack/VLT fabrics
When two leaf switches are discovered on specified VLTi ports, a VLT is automatically created between the two switches to form a
network fabric called the VLT fabric. This VLT fabric is automatically assigned with a fabric ID, a universally unique identifier (UUID).
In a single rack deployment, the network fabric and the VLT fabric represent the same set of switches. In a multi rack deployment, each
rack has a VLT fabric, and all the VLT fabrics and the spine switches together from the network fabric.
Default fabric settings
SFS automatically builds the network fabric using industry-standard Layer 2 and Layer 3 protocols.
Reserved VLANs
To build fabric, SFS reserves VLANs 4000 to 4094 for internal use. You are not allowed to use these VLANs for general use.
• VLAN 4000 — SFS control VLAN
SFS automatically configures VLAN 4000 on all switches that are discovered in the fabric, and uses it for all fabric operations
internally. When a leaf or spine is switch is discovered, the ICL or ISL ports are automatically added as tagged members.
• VLAN 4001 to 4079 — leaf and spine connections
SFS automatically sets up the leaf and spine network configuration using eBGP as the underlay routing protocol. SFS uses the
reserved VLAN range (4001 to 4079) with automatic IP addressing to set up the peer connections. When a spine switch is connected
to the fabric, an ISL is created between the leaf and spine switch. Each ISL link uses a reserved VLAN and the ISL ports that are
configured to be the untagged members of this VLAN. IP addresses from the reserved range are used for this VLAN, and an eBGP
session is started on the VLAN IP interface.
• VLAN 4080 — global untagged VxLAN VLAN
SFS automatically sets up VxLAN overlay networks with EVPN to extend networks between racks in a multi rack deployment.
SmartFabric OS10 requires an untagged VLAN on leaf switches for VxLAN traffic handling when using VLT. VLAN 4080 with
automatic IP addresses from the reserved range is used for leaf-to-leaf interconnect (ICL) links.
• VLAN 4090 — iBGP peering between leaf switches
SFS automatically sets up iBGP peering between a pair of leaf switches directly connected over ICL links. VLAN 4090 with automatic
IP addresses from the reserved range is used for enabling iBGP sessions between the VLT peer switches.
• VLAN 4094 — VLT control VLAN
SFS automatically creates VLAN 4094 on all leaf switches. VLAN 4094 is used for all VLT control traffic between two VLT peer
switches. VLAN 4094 is only added on the VLT interconnect links (ICL ports) on leaf switches.
Default client management network
SFS automatically sets up an overlay network that is called a client management network. When a device is automatically onboarded on to
the network fabric, the device uses the VLAN mapped to this overlay network. This network is a native VLAN unless there is a policy
specifying a different native VLAN. VLAN 4091 is used as the default client management VLAN for this VxLAN network.
NOTE: The embedded SFS user interface allows you to change this VLAN to a specified VLAN.
Default client control traffic network
SmartFabric Services
9