SFS automatically creates the following components and networks:
Internal SFS components
SFS creates a VLT fabric automatically in the leaf and spine environment. VLT fabric is autoassigned with a fabric-ID, a universally unique identifier (UUID). When a VLT fabric is created, the management IP addresses of the VLT peers are used automatically to set up the VLT backup link. If the management IP address of the peers is changed after the fabric is created, the VLT backup link is updated automatically.
SFS creates a network fabric with the leaf and spine switches automatically. The network fabric is autoassigned with a fabric-ID, a name, and description. The fabric name and description are automatically assigned but can be changed through the SFS UI. For more information, see
Update fabric name and description.
Fabric links create a connection between the switches in a network fabric. Leaf-Spine link is a link formed between a leaf and spine switch. All parallel links with same connectivity are grouped to form a port channel interface. VLT interconnect (VLTi) is a link formed between the two leaf switches in a same rack.
Internal virtual networks
The internal virtual networks created by SFS are:
VLAN 4000 for SFS cluster control
SFS automatically configures VLAN 4000 on all the switches that are discovered in a fabric and uses the network for all internal fabric operations. When a leaf or spine switch is discovered, the VLTi or Leaf-Spine link ports are automatically added as tagged members.
VLAN 4001 to 4079 for leaf and spine connections
SFS automatically configures the leaf and spine network using eBGP as the underlay routing protocol. SFS uses the reserved VLAN range from 4001 to 4079 with automatic IP addressing to set up the peer connections. When SFS detects an Leaf-Spine link connection on either a leaf or spine switch, it assigns the Leaf-Spine link to the untagged member of this VLAN. IP address from reserved range is used for this VLAN, and an eBGP session is started on the VLAN interface.
VLAN 4080 for Global untagged VXLAN
SFS automatically configures VXLAN overlay networks with EVPN to extend networks between racks in a multirack deployment. VLAN 4080 with automatic IP addresses from the reserved range is used for VLTi links. VXLAN requires one VLAN to be assigned globally for untagged port-scoped VLAN (Port, VLAN) pairs.
VLAN 4089—OS10 internal use
In SmartFabric mode, VLAN 4089 is the default VLAN and is reserved for OS10 internal use.
VLAN 4090—iBGP peering between leaf switches
SFS automatically configures iBGP peering between a pair of leaf switches directly connected over VLTi links. VLAN 4090 is created automatically with IP addresses from reserved range for enabling iBGP sessions between the VLT peer switches.
VLAN 4094—VLT control VLAN
SFS automatically creates VLAN 4094 on all leaf switches. This VLAN is used for all VLT control traffic between two VLT peer switches and is added on the VLTi ports on leaf switches.
VLAN 4091—Default client management network
SFS automatically configures 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 the VXLAN network.
NOTE:You can change this VLAN to a specified VLAN through SFS UI.
VLAN 3939—Default client control network
SFS configures a second overlay network that is called
Client_Control_Network for SFS-integrated solutions. When a device such as VxRail is discovered, it is automatically added as a tagged member of this network. SFS enables leader advertisement and fabric discovery by integrated solutions. The SFS leader virtual IP address for VXLAN network is advertised. The VIP address
fde1:53ba:e9a0:cccc:0:5eff:fe00:1100 is fixed and not user configurable.
VLAN 3939 is used as the default client control VLAN for this VXLAN network for SFS-integrated solutions including VxRail and PowerScale solutions. Although you can change the VLAN associated with the default client management and control networks, Dell Technologies recommends not to change the VLANs for VxRail deployments.
To check the networks that are created in SFS-integrated deployment, use
show virtual-network command. Following is the example output :
SFS uses the reserved networks internally by default. If these networks conflict with any networks in the existing deployment, change the default networks using the instructions that are provided in
Edit Default Fabric Settings.
Domain ID and ASN mapping
After you enable the SFS on the switches, SFS:
Associates domain ID for the cluster if it is not assigned when enabling SFS. By default, the domain ID is set to 100.
Autogenerates ASN for the leaf and spine switches in the fabric.
Autogenerates subnet with prefix from domain ID.
NOTE:You can edit the domain ID from
Fabric Settings page. Any change to the domain ID changes the ASN for leaf and spine switches, and the subnet details.
The following table lists the ASN and BGP subnet and VTEP subnet mapped with the domain ID:
Table 1. Domain ID to ASN mapping—OS10 release prior to OS10.5.4.0Domain ID to ASN mapping
Domain ID
Leaf ASN
Spine ASN
Fabric BGP subnet and mask
Fabric VTEP subnet and mask
100
65011
65012
172.16.0.0/16
172.30.0.0/16
101
65015
65016
172.18.0.0/16
172.32.0.0/16
102
65017
65018
172.19.0.0/16
172.33.0.0/16
103
65019
65020
172.20.0.0/16
172.34.0.0/16
104
65021
65022
172.21.0.0/16
172.35.0.0/16
105
65023
65024
172.22.0.0/16
172.36.0.0/16
106
65025
65026
172.23.0.0/16
172.37.0.0/16
107
65027
65028
172.24.0.0/16
172.38.0.0/16
In OS10 version earlier to 10.5.4.0, SFS uses the public IP addresses in domains 101 to 107 for the VTEP subnets by default. You may edit the default fabric settings to change the IP addresses from public to private from
Fabric Settings page.
CAUTION:When you edit the fabric settings, all switches in that domain reboot simultaneously to apply the changes.
From 10.5.4.0 release onwards, SFS uses private subnets for VTEP IP addresses for new fabric deployments as follows:
Table 2. Domain ID to ASN mapping — OS10.5.4.0 and later Domain ID to ASN mapping
Domain ID
Leaf ASN
Spine ASN
Fabric BGP subnet and mask
Fabric VTEP subnet and mask
100
65011
65012
172.16.0.0/16
172.30.0.0/16
101
65015
65016
172.18.0.0/16
172.31.101.0/24
102
65017
65018
172.19.0.0/16
172.31.102.0/24
103
65019
65020
172.20.0.0/16
172.31.103.0/24
104
65021
65022
172.21.0.0/16
172.31.104.0/24
105
65023
65024
172.22.0.0/16
172.31.105.0/24
106
65025
65026
172.23.0.0/16
172.31.106.0/24
107
65027
65028
172.24.0.0/16
172.31.107.0/24
For the existing fabric deployment, even when you upgrade from older OS10 version to OS10.5.4.0 or later, SFS still retains the public VTEP IP addresses. You must edit the VTEP IP addresses to the private range from
Fabric Settings page.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\