API Guide

NOTE: You are not allowed to use these VLANs for general use.
● Cluster control VLAN 4000 — SFS automatically configures VLAN 4000 on all the switches in a fabric, and uses the
network for all internal fabric operations. When SFS detects an ISL, it assigns the ISL to the tagged member of this VLAN.
This VLAN is PVST enabled with root bridge that is forced on one of a spine switch.
● IP-peer VLAN 4001 to 4079 — SFS automatically configures the leaf and spine network using eBGP as the routing
protocol. SFS uses the reserved VLAN range from 4001 to 4079 for automatic IP addressing to set up the peer connections.
When SFS detects an ISL connection on either a leaf or spine switch, it assigns the ISL to the untagged member of this
VLAN. IP address from reserved range is used for this VLAN. eBGP session is started on the VLAN interface.
● Global untagged VXLAN VLAN 4080 — 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 leaf-to-leaf ICL links. VXLAN requires one VLAN to be assigned globally for untagged port-scoped VLAN (Port, VLAN)
pairs.
● Internal BGP (iBGP) ICL VLAN 4090 — SFS automatically configures iBGP peering between a pair of leaf switches
directly connected over ICL links. VLAN 4090 is created automatically with IP addresses from reserved range for enabling
iBGP sessions between the VLT peer switches.
● VLAN 4094 — 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 VLT ICL ports on leaf switches.
● Default client management network VLAN 4091 — SFS automatically configures an overlay network that is called
client_Management_Network. When a device is connected automatically on to the network fabric, the switch uses the
VLAN mapped to this overlay network. VLAN 4091 is used as the default client management VLAN for the VXLAN network.
● Default client control network — SFS configures a second overlay network that is called Client_Control_Network
for VxRail integrated solutions. VLAN 3939 is used as the default client control VLAN for this VxLAN network. You can
change the VLAN associated with the network, but it is not recommended to change it for VxRail solution deployments.
To check the VLAN configuration formed in SFS-VxRail deployment, use show virtual-network command. Following is the
example output:
OS10# show virtual-network
Codes: DP - MAC-learn Dataplane, CP - MAC-learn Controlplane, UUD - Unknown-Unicast-Drop
Un-tagged VLAN: 4080
Virtual Network: 3939
Description: In-band SmartFabric Services discovery network
VLTi-VLAN: 3939
Members:
VLAN 3939: port-channel1000, ethernet1/1/12, ethernet1/1/13
VxLAN Virtual Network Identifier: 3939
Source Interface: loopback2(172.30.0.0)
Remote-VTEPs (flood-list): 172.30.0.1(CP)
Virtual Network: 4091
Description: Default untagged network for client onboarding
VLTi-VLAN: 4091
Members:
Untagged: ethernet1/1/12, ethernet1/1/13
VLAN 4091: port-channel1000
VxLAN Virtual Network Identifier: 4091
Source Interface: loopback2(172.30.0.0)
Remote-VTEPs (flood-list): 172.30.0.1(CP)
SmartFabric Services logical entities
There are three types of logical entities that are defined for the SmartFabric Services: Networks, uplinks, and server profiles.
Networks
Networks are SmartFabric services templates that are populated once and then can be associated with servers, uplinks, or
interfaces.
With in the context of SmartFabric services, you can define the following four types of networks:
● General purpose networks
● VXLAN networks
● L3 VLAN networks
● L3 Routed networks
SmartFabric Services
123