• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2559
  • Last Modified:

Dell PowerVault MD3220i Setup with VMware ESXi IP & Subnet Questions

Hi Everyone

I'm setting up an MD3220i (Dell PowerVault SAN) with an ESXi server. I have two switches for redundancy and one ESXi server with four ports on the back. I've followed all the documentation provided by Dell, but have a few general questions around the IP addressing. I have asked on the Dell forums, but as usual do not seem to be getting an answer (not as good as Expert Exchange!).

I've enclosed a diagram of exactly how my setup looks and placed the IP configuration of the two controllers at the bottom of the post.

ESXi:

I've created a switch with virtual kernels for each physical port and have bound them to each physical port, configuration below

iSCSI01
vmk1: 10.0.1.3

iSCSI02
vmk1: 10.0.1.4

I've carved up LUNs on the PowerVault and formatted some volumes in VMFS, and everything appears to be working fine.

Now my questions are as follows:

Are the IP address for the PowerVault correct? I have subnetted ports from each card in groups, and just specified an overall gateway. Should they be sub-netted in this way?
Does the gateway matter? I have specified an overall gate way, but as this is a closed off iSCSI does it make a difference?
Does the IP address of the vmk's matter? I have given them a static address on the same subnet as two of the NICs from the PowerVault, but what about the other two subnets I created? I've left the gateway for these unspecified, does that matter? Should it be the same as the one on my PowerVault, or the gateway for our internal network?

As you can see, my weak points are IP Networking. What Im really looking for are simple explanations, I've read a lot of documentation provided by Dell and found it very conflicting.  

Any information would be great. Thanks everyone.

Here is the IP address configuration of my PowerVault:

Controller 0:

IN 0 Port:

  IPv4:

   IP address: 10.0.1.1

   Mask: 255.255.255.0

   Gateway: 10.0.0.10

 IN 1 Port:

  IPv4:

   IP address: 10.0.2.1

   Mask: 255.255.255.0

   Gateway: 10.0.0.10

 IN 2 Port:

  IPv4:

   IP address: 10.0.3.1

   Mask: 255.255.255.0

   Gateway: 10.0.0.10

 IN 3 Port:

  IPv4:

   IP address: 10.0.4.1

   Mask: 255.255.255.0

 

Controller 1:
  IN 0 Port:

  IPv4:

   IP address: 10.0.1.2

   Mask: 255.255.255.0

   Gateway: 10.0.0.10

 IN 1 Port:

  IPv4:

   IP address: 10.0.2.2

   Mask: 255.255.255.0

   Gateway: 10.0.0.10

 IN 2 Port:

  IPv4:

   IP address: 10.0.3.2

   Mask: 255.255.255.0

   Gateway: 10.0.0.10

 IN 3 Port:

  IPv4:

   IP address: 10.0.4.2

   Mask: 255.255.255.0

   Gateway: 10.0.0.10

link to Dell Deployment guide for ESXi

http://www.dell.com/downloads/global/products/pvaul/en/md-family-deployment-guide.pdf


Setup1.png
switch1.JPG
switch2.JPG
0
explorersup
Asked:
explorersup
2 Solutions
 
amwinsitCommented:
The Gateways won't be used by the iSCSI traffic because it is on the same subnet but since this is ESXi HA uses the default gateway to make sure it isn't isolated, so the only vmkernal port that needs a default gateway is your management vmkernal. How many nics do you have in your server? If possible you want to split you iSCSI vSwitches from your VM Network vSwitches and if applicable make sure you vMotion is definatly on a dedicated nic. You don't need to have all the ports on different subnets on iSCSI VLAN should suffice but if it is already setup it should be fine as long as you setup the vlan ID on the vmkernal ports so they get associated with the correct nics or if you can setup a single nic per iSCSI vmkernal port and plug that into an access port on the switch.
0
 
ocelot00Commented:
amwinsit is correct that the gateway is not needed for iSCSI traffic.  Using multiple subnets for the ports on the MD3200i is recommended by Dell.  The only other thing I noticed is it looks like you need to modify the NIC teaming settings.  I recommend that you follow the best practice from VMWare that the VMkernel ports are assigned 1 to 1 with a physical nic. The second nic will be unused in the nic teaming tab, not standby. For reference see page 17 in the deployment guide.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now