Before beginning switch configuration and network deployment, plan all the networks and the IP addresses used for those networks. Traffic is divided into different networks, as shown in the following table:
Network | Purpose |
External management | Network for ESXi, vCenter Server, NTP, and DNS traffic |
vMotion | Network for virtual machine (VM) migration traffic |
PowerStore | Network for PowerStore storage traffic |
Isilon | Network for Isilon storage traffic |
VM networks | Networks as required for VM data traffic |
Uplink network | Network to existing and external networks |
The following table shows the VLAN IDs and network addresses planned for the examples in this guide:
VLAN ID | Description | Network | Gateway | Server interfaces |
1811 | External management | 172.18.11.0/24 | 172.18.11.254 | Tagged or Untagged |
1812 | vMotion | 172.18.12.0/24 | None | Tagged |
1814 | VM Network A | 172.18.14.0/24 | Optional, 172.18.14.254 | Tagged |
1815 | VM Network B | 172.18.15.0/24 | Optional, 172.18.15.254 | Tagged |
1819 | Discovery network for PowerStore | 172.18.19.0/24 | 172.18.19.254 | Untagged |
1820 | PowerStore storage traffic | 172.18.20.0/24 | 172.18.20.254 | Tagged |
1801 | Isilon storage traffic | 172.18.1.0/24 | 172.18.1.254 | Tagged |
1816 | L3 VLAN uplink (if used) | 172.18.16.0/24 | 172.18.16.254 | NA |
Select the server interfaces for the external management network as tagged or untagged. This guide indicates where this option can be applied.
In SmartFabric mode, each network is created as a General Purpose network. that has a 1 VLAN to 1 Virtual Network Identifier (VNI) relationship. 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.