Hello and welcome to Dell Networking Solutions Engineering
In this video
we will be looking at deploying
VMware Virtual SAN
on PowerEdge FX2 chassis.
This will be part 1 of this video.
In this example, the FX2 chassis contains
four FC430 servers, two FD332 storage blocks
and two FN410S.
Let's take a look at the topology that is used
in this example.
This is a simple scenario using one Top Of Rack switch.
Most data center solutions would have 2 Top Of Rack switches.
There are four FC430 servers and, two
FN410S IO modules, in the chassis.
Port channels 15 and 14 run from top of rack switch
S4048 to FN410S modules in slot A1 and A2.
The two FN410S modules that we are using here
are in standalone mode.
It requires zero touch.
Hence we won't be looking at any configuration
on the FN410S in this video.
Before configuring VSAN,
let's take a look at the configuration of Port channel 15 on S4048.
There is a description added to the link.
We give it as portmode hybrid and we make it switchport.
Note that the interfaces Te 1/15 as well as interface Te 1/16
are part of this port channel.
We use the protocol LACP to add these two interfaces,
to port channel 15.
Moving on to the next port channel, which is port channel 14,
we can see that the interfaces 13 and 14,
are part of this port channel.
The configuration is similar to the configuration of port channel 15.
Protocol LACP is used here.
For VSAN, we create VLAN 30.
We assign an IP address to the VLAN.
We tag the port channels 14, as well as 15,
with VLAN 30.
One important part of the configuration,
is to make sure that,
we use IGMP snooping command here,
which is ip igmp snopping querier.
In addition, make sure that igmp snooping is enabled.
Use "ip igmp snooping enable" command
in the global configuration mode, to activate igmp snooping.
VSAN uses multicast to deliver meta data traffic,
among cluster nodes.
Igmp snooping querier is used to limit the physical switchports
participating in the multicast group,
to only VSAN VMKernel interfaces.
Let's take a look at the environment that has been set up
using VMware VSphere web client, before we enable VSAN.
There is a cluster created with 4 hosts.
Let's take a look at one of the hosts.
Click on manage,
followed by networking.
There is a standard switch that has been created: vSwitch0.
The VM Kernel VSAN that we are using in this example,
is associated with vSwitch0.
The two physical adapters vmnic0 and vmnic1,
are associated with vSwitch0,
through which they can interact with VMKernel port VSAN.
Let's take a look at vSwitch0 settings.
The settings in Properties, Security, and Traffic shaping
are left to their default settings.
Click on Teaming and failover.
Load balancing, Network failure detection,
Notify switches and, Fallback options
are left at default.
We have vmnic0 as an active adapter
and vmnic1 as a standby adapter.
Let's take a look at the VM Kernel
adapter that we are using in this case.
This Kernel adapter has been named VSAN
It has been tagged to a VLAN id of 30.
It has been assigned an IP address.
As we scroll down the properties, we can look at
the information that's displayed for active as well as standby adapters.
Let's take a look at the storage section.
Click on the storage tab.
In this section that says storage adapters,
we are able to see the 8 disks that will be used in this example.
Note that all the drive types are flash.
For all the 4 hosts used in this example,
8 disks are presented from the 2 FD332 storage blocks.
In this video, we looked at the configuration on S4048 switch,
that was used as a Top Of Rack switch,
as well as the environment used in this example
through VMware vSphere web client.
In the next video,
we will be looking at enabling VSAN,
and validating VSAN.
Thanks for watching this video.