Networks and IP addresses used for Isilon storage traffic must be planned before switch configuration and network deployment can begin.
Traffic is divided into five or more networks, as shown in the following table:
Table 2. Network descriptions
Client Management Network
Default untagged network for end hosts devices that support zero-touch deployment with SmartFabric Services (for example, VxRail nodes). This deployment guide does not use this network.
Client Control Network
Default network used to advertise SFS services to other integrated solutions like VxRail. This network is also used for VxRail node discovery and cluster formation.
This deployment guide does not use this network.
Network for switch OOB and server iDRACs. OMNI communicates with SFS over a dedicated OOB interface.
Network for ESXi, vCenter Server, NTP, and DNS traffic.
User-specified network for virtual machine (VM) migration traffic.
User-specified network for Isilon storage traffic.
User-specified network(s) as required for VM data traffic.
User-specified network to existing and external networks.
VLAN IDs and network addresses planned for this deployment example are shown in the following table:
Table 3. VLAN and networks
SFS Client Management
Tagged or Untagged
VM Network A
VM Network B
Isilon storage traffic
L3 uplink (if used)
*Automatically created VLAN
The server interfaces for the external management network may be selected as tagged or untagged. This guide indicates where this option can be applied.
In SmartFabric mode, each VLAN is automatically placed in a VXLAN network with a Virtual Network Identifier (VNI) that matches the VLAN ID. VLAN 4091 is in virtual network 4091, VLAN 1811 is in virtual network 1811, and so on.
The show virtual network command is used to view virtual networks, VLANs, and port-VLAN assignments configured on the leaf switch.