[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 288
  • Last Modified:

Questions about this Virtual Environment setup.

We're trying to plan our VMware implementation and I need some guidance. I'm good at naviagating around VirtualCenter and can work my way around ESX, but I am a newbi when it comes to networking.

We have the following hardware to install.
2 Dell R805's (ESX Servers, 8 NICs each)
1 EqualLogic SAN Array 300Gbx16 (2 controllers with 3 ports each)
2 48 port Dell PowerConnect 5448s (I only showed 30 ports in the diagram).

We built this diagram a while ago, but I think it needs some refreshing and comments from the "Experts".
Blue - EqualLogic connections
Orange - ESX1 connections
Green - ESX2 connections

So how do I work out the different networks here? Remember I'm using my BASIC network understanding. Please correct where needed.
Thoughts...
VLAN
192.168.1.x for the SAN traffic.
Does each of the controllers on the SAN Array get a different IP Address?
SA1 (controller 1) = 192.168.1.1
SA2 (controller 2) = 192.168.1.2
We were told that the 'boot' traffic should be on a different ip address then the general talking traffic of the VMs.  What do you guys think about this?  This is why there are a pair of nics for the boot traffic (C) and the general talking traffic (D).  Does this make sense?  

I guess I should probably stop there and make sure i'm on the right path before proceeding.

I really appriciate the help guys! Thanks!


See the attached
0
GWitek
Asked:
GWitek
  • 3
  • 3
1 Solution
 
65tdCommented:
Attachment missing?
I would use one nic for the service console, one for vmkernal traffic and at least one nic for the VM's, out of the 5 left use 2 for iSCSI and the last 3 for VM's (including the 1st zVM nic) in a trunked configuration.

Lots of documents at vmwares site:
http://www.vmware.com/support/pubs/vi_pages/vi_pubs_35u2.html
and VLAN trunking:
http://www.vmware.com/pdf/esx3_vlan_wp.pdf
Similar Q and HW(?):
http://episteme.arstechnica.com/eve/forums/a/tpc/f/833003030931/m/435004022931
0
 
GWitekAuthor Commented:
Here is the attached file. Sorry.
AllTraffic1.0.jpg
0
 
philtpaikCommented:
8 NICs is plenty to have a good setup. If it was my setup I would set it up this way:


For both ESX servers:

NIC1&2 - vswitch1 Service Console & VMkernel (I know they want you to separate the two, but I think you gain much more by NIC TEAMING them and keeping both together. Depending on you set this up, you may want to tag these also or if they are in the same subnet, you can leave them as access ports)

NIC3,4,5 - vswitch 1 VM Network (NIC TEAM and create Virtual Port Groups with VLAN tags on those switch)

NIC 6,7,8 - vswitch2 VM Network (NIC TEAM and dedicate this for iSCSI traffic only)



For the Dell Switches:

Ports for NIC1&2 - configure for access ports that match the vlan of the service console and vmkernel or trunk ports and tag the other end if they are on separate vlans)

Ports for NIC 3,4,5 - Configure as trunk ports

Ports for NIC 6,7,8 - Configure as access ports for iSCSI VLAN.


Hope that can be somewhat useful.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
philtpaikCommented:
8 NICs is plenty to have a good setup. If it was my setup I would set it up this way:


For both ESX servers:

NIC1&2 - vswitch0 Service Console & VMkernel (I know they want you to separate the two, but I think you gain much more by NIC TEAMING them and keeping both together. Depending on you set this up, you may want to tag these also or if they are in the same subnet, you can leave them as access ports)

NIC3,4,5 - vswitch1 VM Network (NIC TEAM and create Virtual Port Groups with VLAN tags on those switch)

NIC 6,7,8 - vswitch2 VM Network (NIC TEAM and dedicate this for iSCSI traffic only)



For the Dell Switches:

Ports for NIC1&2 - configure for access ports that match the vlan of the service console and vmkernel or trunk ports and tag the other end if they are on separate vlans)

Ports for NIC 3,4,5 - Configure as trunk ports

Ports for NIC 6,7,8 - Configure as access ports for iSCSI VLAN.


Hope that can be somewhat useful.

EDITED: vswitch1 to vswitch0....sorry typo and i dont wanna get you confused
      
0
 
GWitekAuthor Commented:
Awesome. Just what I was looking for.

A few questions:
1. When you say "NIC TEAM" i'm firmilar with teaming for redundancy. NIC1 is active and NIC2 doesn't kick in unless it seneses NIC1 has failed. Using your example above with NIC 3,4,5: Would this be set up the same way? 2 Redundant NICS?  What do I gain by doing this?  I've been learning about aggregation, is this what you're doing here? 3x1000mbs = 3000mbs? I thought there was a third party software you has to use?

2. I just started learning about VLANs and Port Groups. VLAN is actually saying "I want ports 1-4 to be in VLAN0 and no other traffic from any other port can get to it.".  How do "Port Groups" factor into these VLANs, they sound similar.

3. Can you elaborate on "Configure as truck ports"?

Thank you for you time with this!  It is really helping!
0
 
philtpaikCommented:
1) NIC team on VMware is not really aggregation as you call it since each NIC will have its own MAC. I'm not sure if it is possible with to setup it up with ether-channel. If you wanted all 3000mbps on those three ports, you would be able to do so by making all the NICs in your team active.

2) In VMware, each virtual switch has x number of ports that you assign to it. Instead of assigning each port to each machine, you create port groups with different VLAN tags. When you create a VM, for the networking portion you assign it to a port group. VMware then places this machine in that particular "port group" of the switch.

This is the same thing as tagging each port on a physical switch, except for the fact that you dont need to know the port number and configure the port each time you move the machine.

3) Trunk ports are ports are basically ports that can pass along ANY or ALL VLAN traffic. As opposed to access ports which only allow 1 particular VLAN traffic.

0
 
GWitekAuthor Commented:
Thanks for all the tips guys!

After hours upon hours on threads and the phone I have a better description of what we're going for.
Reminder of what hardware we're dealing with...
2 Dell R805's (ESX Servers, 8 NICs each)
1 EqualLogic SAN Array 300Gbx16 (2 controllers with 3 ports each)
2 48 port Dell PowerConnect 5448s (I only showed 30 ports in the diagram). - These switches are not stackable.

We're really taking a hit by these switches not being stackable.  What we're doing is mainly relying on Switch A and if the entire switch fails we'll have the passive NIC on SwitchB.  What do you guys think about a 2Gb pipe for the iSCSI and LAN traffic?  We'll have about 4 VMs running in this setup. They push about 1100 IOPS.

AllTraffic1.0.jpg
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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