ESXi 5.1 separating SAN traffic w / VLAN

Similar Questions

• Config network for SAN traffic

  Please see the image as an attachment. It is what I currently have, the one after is what I think I need to do.

  Here's my number; I think I have install the networking incorrectly for my esx boxes hit the SAN.  For now, it's that everything works fine, however I think I may have made a few extra STREP that does not need to do.  Right now I have a NIC deticated to two different vSwitches which are useless, but SAN traffic.  the more I watch this, more I think that I should have used a unique vSwitch on every box of esx and just added the necessary ports console and core it.  So I would have a unique vswitch on each box dedicated to SAN traffic, each vSwitch would have two network cards current with both console and two ports of kernel.

  Maybe I'm just beating a dead horse because they're all going two do the same thing, but maybe it's something smarter and simpler to go with scenario after since they can load the balance between the two and failover works better.  ???   My biggest concern is, can I have two console different and two ports in different kernel, both on different subnets, to the same vSwitch?

  Thanks for any advice.

  Yes, your thought is good. having two NICS on a unique vswitch will give you more options for failover and load balancing. Having also several ports console and kernal on the same vswitch is not a problem.

  Ben Karciauskas

• HA and SAN traffic on dedicated NIC port

  Hello

  We have a small vmware network 2 HP servers and a SAN. We buy ESS Vsphere with HA.

  If I understand correctly, it is considered preferable for HA and SAN traffic on a port on the network adapter.

  What I need is help with how to implement that.

  We will have 2 spare nic per server ports dedicate to this, one for HA and one for SAN traffic.

  Currently, we use 2 ports per server in swarming mode connected to a subnet and two ports more connected to another subnet, for a total of 4 ports per server. We will buy a 6 port of HP network card very soon, it is most important that they do for our DL 365 HP. This will give us the extra 2 ports per server, to devote to SAN and HA traffic.

  OR should we just use the spare ports 2 Teemed in the SAN and forget to devote to the HA.

  Thank you!!!

  Peter

  HA the traffic runs on the service console / management network. It is advisable to separate, but it is not a must. I will say if you don't have enough NIC to use the grouping of network cards to introduce redundancy, it is more important than anything else, when you run HA.

  Duncan

  VMware communities user moderator | VCP | VCDX

  -

• VMotion traffic isolation, vlan trunking

  We have 2 full length M910 blade servers sitting in the dell blade enclosure. Installed esxi 5.0 on the two blades and joined them to the cluster.

  Each server blade full length a 8 network cards.  2 ports double aboard the card NETWORK and 2-port Ethernet mezzanine card.  All are connected to the internal cisco switch 3130 installed on the module e/s A1, A2, B1 and B2. all the internal switches are stacked together by the network team. and there is a link to internal switch (uplink) and an external switch (ports) that are on the vlan 137

  All the ports that are connected to the esxi host are configured as trunk on the switches of internal physical cisco blade by the network team. in our total case 16 ports (8 cards x 2 servers) are fixed to the internal trunk on cisco switch and there is internal cisco switch uplink and our external switch (located on vlan 137)

  On esxi5.0, we set up a big flat switch affecting all physical network cards to Vswitch 0.
  Please refer page for groups of ports configured.
  
  To isolate the vmotion traffic, we have configured tag (150) vlan different for vmotion. but vmotion does not work. Unable to ping of vmotion ips with each other.  But if I change brand VLAN to 137. vmkping works on the other and work of vmotion.

  If I change brand VLAN other than 137 to any group of ports (for example, management or virtual machine), I'm losing connection to the corresponding port group.

  
  I think that missing configure something on the blade switches internal cisco (3130). Please advise on what needs to be configured. I know that kind of why trunking is required. If you could explain the exact purpose of why the necessary circuits for esx would be great.

  What is advised to configure a virtual switch, such as a large flat switch or multiple switches
  Assigning to each switch port group. recommended configuration to enable balancing the increased load of incoming and outgoing and fail over.  detailed explanation would be really useful for non admins networks

  I will try to describe one of the possible configurations.

  First some facts/support:

  • 2 ESXi hosts
  • 4 blade switches
  • 1 external switch
  • 8 NICs in each server Blade (2 NICs for each of the switches)
  • vmnic0 and vmnic4 are connected to two different switches
  • different subnets / VLAN for vMotion (100), management (101) and VM networks (102,...)
  • all VLANS represent them different IP subnets

  Virtual network configuration:

  • 2 vSwitches: 1 for management, 1 for VM networks and vMotion
  • vSwitch0 for management and vMotion (vmnic0 + vmnic4)
    --> Management ports (VLAN 101) Group: vmnic0 (active), vmnic4 (at rest)
    -> vMotion Port Group: (VLAN 100): vmnic4 (active), vmnic0 (at rest)
  • vSwitch1: VM networks (vmnic1.. 3 + vmnic5...) 7)
    -> VM 1 (VLAN 101) port group
    -> Port VM 2 (VLAN 102) group
    -> ...

  Blade switches:

  • all the VLANS configured in the virtual network are present
  • all ports of downlink to the ESXi hosts are configured to trunk mode, all the VLANS allowed
  • at least 2 uplinks and the external switch configured as a trunk, EtherChannel (LACP)
  • ports of rising and descending liaison (on each of the switches) are a group of track link state

  External switch:

  • all the VLANS configured in the virtual network are present
  • four channels of Port/EtherChannels (LACP), one to each switch blade

  You can configure the VLANS on switches separately or by VTP. In any case, all the VLANS should be present on the switches of. If you need to route traffic between some VLANs, you must either set up a router on your network, or - in the case where the switches support and are properly authorized - configure routing ip (Inter VLAN routing).

  André

• Separation of traffic

  This is the situation: we have a host ESX 3i 3.5 with 3 cards of physic. Management, one for traffic to the virtual machine and iSCSI traffic.

  We want to separate the traffic of different vlans, for example

  Vlan1 = 192.168.1.x / mask 255.255.255.0 / Gateway 192.168.1.1

  VLAN2 = 192.168.2.x / mask 255.255.255.0 / Gateway 192.168.2.1

  VLAN3 = 192.168.3.x / mask 255.255.255.0 / Gateway 192.168.3.1

  so:

  for vlan1, nic1 is vswitch1, it comes to vmkernel port group and the ip address is 192.168.1.2, gateway 192.168.1.1

  for vlan2, nic2 is vswitch2, it is a virtual machine port group and the range of ip addresses will be 192.168.2.x (for each virtual machine)

  for vlan3, nic3 in vswitch3, this should be a group of ports vmkernel (for ISCSI). The problem is the following: for vlan3, the IP range is 192.168.3.x, then, we set up an ip address in this range but rest of the default gateway 192.168.1.1 (the vlan1). If we change our offer

  Is this correct? How can we resolve this situation? What we're doing wrong?

  Thank you

  Yes, with iSCSI traffic (ESXi host groups as storage system iSCSI ports) on the same subnet, there is no need a gateway.

  André

• Several iSCSI SAN on different VLANS

  I have a little trouble to get this configured.

  In our environment, we have 4 guests and 2 EqualLogic iSCSI San. Each host has 3 NICs dedicated to iSCSI traffic, and they have been implemented to use the plugin for Multipathing of Dell with 3 VMKernel iSCSI ports, each bound to a NETWORK adapter physical and then linked to the iSCSI software adapter.

  We want to add a new SAN QNAP out some VMs test & dev environment of low cost data warehouses. The QNAP San not supporting Jumbo frames, we want to move them to their own VIRTUAL local area network.

  Can someone tell me how I can get this set up? I need of course a new VMKernel port running on the VLAN again, but after that I'm stuck.

  Thank you

  First: the initiator will be gracefully demote by using standard images.

  Second, there is nothing that prevents you from using the same trade for the qnap. If it does not manage the same way MPIO, you may need to add more exchanges and vmknics. If you place moderate to heavy load on the qnap it would interfere with the ability of the EMM to balance the load properly but allows to measure.

  We have a group EQL and a Celerra making MPIO in different ways. With Celerra you add several portals (ip addresses) network on different subnets so ideally you set up your trade in this way. For us, this meant adding a second portgroup and vmknic on each vmnic, resulting in a whole bunch of paths to the Celerra said. If our use of Celerra was far from being weak to non-existent I probably don't have it.

  -Anders

• relocation of esxi start from the san LUN

  I have 1 SG by ESXi host and its start-up dedicated to san lun and other LUN datatore. IF I had to reinstall the host esxi via kickstart, do I need to unmask the LUNS of the SG data store before installing?

  I used to do if Imaging is automated. If I do this since an ISO just be careful. That's what I do.

  My Blog of UCS http://realworlducs.com

• 2 guests ESXI 4.1 + 1 SAN + how-to vmotion/ha.

  Hi all

  I just finished with the configuration of two hosts 4.1 esxi, vcenter, storage san; For now, I have a couple of virtual machines running on host 1 (virtual machines are stored on san, I activated with san multipathing LUNS are presented only to host 1 right now).

  I want to activate vmotion & HA.

  Basically, I want to be no interruption of service, as in, if a physical host switches the other Sockets. all of my virtual machines should be stored and managed the san.

  What is the best practice approach?

  Create a cluster? I then make my LUN for both esxi hosts? It is not yet clear. This new cluster has its own iscsi? I have to present LUNS to this new iscsi host?

  Can you please advise with a pdf file or a walkthrough.

  My vcenter's vmotion license and vmwareHA.

  This is a good news

  The fact that HA works means that you shared storage and the network configuration is identical on each host.

  requires specific additional VMkernal and vMotion for vMotion

  Thus, on each host vSwitch, you add a VMKernal and check the vMotion.

  It takes an IP address for each VMKernal server and vMotion.

  After installation make sure that guests can each other on this specific IP ping

  Then vMotion option will be available.

  Here is a video that will explain everything

  vMotion Setup

  Please allow points to useful/correct answers

• Question about VMKernel iSCSI traffic and VLANS

  Hello

  This is a very fundamental question that I'm sure I know the answer too, but I want to ask him anyway just to reassure myself.  As a precursor to my question, the configuration of my ESX infrastructure is best described here: http://www.delltechcenter.com/page/VMware+ESX+4.0+and+PowerVault+MD3000i.  Or more precisely, we have two controllers MD3000i.  Each controller has two ports and each port is configured on two different subnets, with every subnet connected to the different switch.  ESX host are connected to two switches.  The only difference for the guide, is we have two MD3000i configured the same, connection to the same switches.  Each MD ports is configured on the same subnet, but different IP addresses.

  At present, we are in the process of upgrading our two iSCSI switches of humble Dlink DGS - 1224T to Cisco 2960 T of.  The switches have been and continue to be dedicated to iSCSI traffic, however, I'm trying to set up VLAN s on the side of the switch.  Originally, we used the default VLANS on switches, however, after you have added an another MD3000i, noted the Support Dell best practices is to separate each on its own subnet and VLAN MD3000i iSCSI traffic. This would result in iSCSI 4 VLANS, two on each switch and two for each MD3000i.  Firstly, is this in fact of good practices?

  Second, if I migrate preceding 4 iSCSI VLANS, as each switch port will actually be an access port, will there need to complete the VLAN ID field in the VMKernel configuration page? Presumably, this field is used when the tagging VLAN is used, but as our switches do not need any other rocking trunk (as they are dedicated to iSCSI traffic), there should be no need to fill?  I guess it would be prudent to keep the two existing subnets, create two new subnets and make changes to an MD3000i and connection of the ESX host.  Provided the switch and switch ports has been appropriate configured with VLAN on the right, the rest should be transparent and he wouldn't be Intel VLAN in all ESX hosts?

  Would be nice to get answers and thank you in advance!

  Gene

  (1) Yes, it is best practice for ESX iscsi, having an independent network and vlan for iscsi traffic.

  (2) No, there is no need to mention anything in the area of vlan, if you use an access port. Its a mandatory thing than a choice. If you supply the id vland with access port, it loses connectivity.

  Please explain a bit why you need to create two different virtual local networks for each MD3000i. You are going to use several on the same ESX box iscsi storage? Alternatively, you use only a single iscsi and use these 4 ports for the same single VMkernel interface?

  NUTZ

  VCP 3.5

  (Preparation for VCP 4)

• ESXi 4 Boot from SAN?

  I heard that booting from the San with ESXi is supported with the 4.0, but someone tried?  I'm looking at a fervent IBM DS3200 SAS for a small deployment I work on and I wanted to check it works for others before that I have try.

  Mike

  Hi Mike,.

  This works. You must configure SAN setting first in the BIOS. Then the Setup program will detect the LUN. other things are almost the same as the installation on a local hard drive.

  Best regards

  shsun

• ESXi 3.5 patch3 network traffic shaping does not work

  Hello

  Help, please

  the smoothness of the traffic network in esxi 3.5 patch 3 doesn't work

  Mather Board dg35ec

  Thank you

  Welcome to the forums - how is your network set up? What formatting settings you put? Don't forget the traffic shaping is outgoing and applied to each virtual NIC connected to the virtual switch.

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Cannot connect the switch Cisco Cisco SG300 - 28 p spend and traffic through VLANS

  Try to connect the Cisco SG300 - 28 p switch to another switch and proceed 2 VLANS between them.  Not doing any circuit.  If I connect a computer to the port on the SG300 - 28 p I can access the VLAN 2 and take a DHCP address. However, when I connect to another switch on the port and connect it to a port on another switch secondary I am unable to access VLAN 2 and pull an IP address.  I checked that the works of secondary switch (WS-C3560G-48PS-S) connected to the other 3500 s, but not this latest SG300 - 28 p.  Here's the configuration for both, I'm leaving areas that shouldn't matter and add if necessary.  Try to connect the SG300 - 28 p Port 26-WS-C3560 Port 1 port.  Once again, if I connect a computer to port 26 on the SG300 - 28 p I access the VLAN 2 as expected, but not when I connect to channel 2 on the secondary switch.

  Cisco SG300 - 28 p

  !
  interface vlan 1
  Internet name
  !
  interface vlan 2
  LAN name
  IP 172.20.5.11 255.255.0.0
  no ip address dhcp (this is the VLAN I'm moving)
  !
  interface vlan 3
  private name
  !
  interface vlan 4
  name of Nortel
  !
  interface vlan 101
  name Video_Project
  !
  interface gigabitethernet26
  Description VLAN2-ACCESS-CISCO3500
  switchport mode access
  switchport access vlan 2 (this goes to port 1 on the other Cisco 3500 switch to provide access 2 VLAN)

  Cisco 3500

  !
  interface Vlan1
  NATCO Internet description
  no ip address
  no ip route cache
  no ip mroute-cache
  !
  interface Vlan2
  NATCO LAN description
  IP 172.20.5.13 255.255.0.0
  no ip route cache
  no ip mroute-cache (this is the VLAN I'm moving)

  !
  interface Vlan3
  Description LHPrivate
  no ip address
  no ip route cache
  no ip mroute-cache
  !
  interface GigabitEthernet0/1
  switchport access vlan 2 (this is the port that I connect to the SG300 - 28 p)

  !
  interface GigabitEthernet0/2
  switchport access vlan 2 (this is the port I hang my computer to and trying to access VLAN 2 other switch)

  Hello

  Yes, STP is the problem here. As you can see on your release of the Cisco 3500 switch, port Gi0/1 is BKN (The FEW is a shortened form of "Broken").

  This is caused by an incompatibility of versions PLEASE used between the two switches. Small businesses (including series SG300) switches are use legacy STP or Rapid STP (your case), but uses templates to business (such as catalyst 3500) PVST + (each VLAN spanning tree version of STP).

  Two versions between group of switches are compatible only under certain conditions. Important condition is that the two switchports needs to use a VLAN 1, vlan access/native and not any other number VLAN.

  It is to make your communication work, you must:

  • disable the STP at least 3500 Cisco switch:
    • on overall global (Switch (config) # no vlan spanning tree 2)
    • or by the base interface (switch(config-if) # no vlan spanning tree 2)
  • change the configuration of your connection between two switches by following the path:
    • change the switchport trunk (trunk switchport mode) mode
    • do 1 VLAN as native vlan (vlan switchport trunk native 1)
    • Towing VLAN 2 as vlan tagged on that Stump (switchport trunk allow vlan add 2)

• Enable the VLAN on sub interface internet access but block traffic to VLAN native

  I have a 2821 router w / MLS 2024 switches.  Native VLAN(default vlan) is my private network and VLAN 100 is my comments system.  Below is my interface config...

  interface GigabitEthernet0/1

  Description ES_LAN, ETH - LAN$ $$

  IP 10.1.0.2 255.255.0.0

  penetration of the IP stream

  IP nat inside

  IP virtual-reassembly

  automatic duplex

  automatic speed

  !

  !

  interface GigabitEthernet0/1.1

  encapsulation dot1Q 100

  IP 10.3.1.254 255.255.255.0

  penetration of the IP stream

  IP nat inside

  IP virtual-reassembly

  !

  IP default-gateway xx.xxx.xxx.xxx

  IP forward-Protocol ND

  IP http server

  23 class IP http access

  local IP http authentication

  IP http secure server

  IP http timeout policy slowed down 60 life 86400 request 10000

  Default route is defined...

  IP route 0.0.0.0 0.0.0.0 xx.xxx.xxx.xxx

  Access list are...

  access-list 175 deny ip 10.1.0.0 0.0.255.255 10.2.0.0 0.0.255.255

  access-list 175 allow ip 10.1.0.0 0.0.255.255 everything

  access-list 175 deny ip 10.3.1.0 0.0.0.255 10.1.0.0 0.0.255.255

  access-list 175 allow ip 10.3.1.0 0.0.0.255 any

  I want to continue to have access to the guest VLAN in VLAN private to allow the management of points of access etc.

  I want to allow internet access as guest newtork but block it to access my private network.

  Don't know how to do in this regard.  I tried to change the ACLs (remove the 10.3.1.0 entries) and creating an another acl for the Scriptures and applying that VLAN 100 sub interface... so far without success.

  Thanks in advance for the help!

  Hello Chris,

  > From this point of view should I leave the above lines and create another list acl for the 10.3.1.0 of the network and apply entering gig0/1.1?

  I would go this way, as in a simple ACL, you can't express your needs. The ACL to apply on gi0/1.1 will probably need further instructions then the ones I suggested, but divide the problem into smaller manageable pieces is a good strategy.

  > Also with this config would be NAT be performed on each network by making this change?

  Until the internal network and network of comments are on the same side (ip nat inside) there is no NAT triggered in communication between them so that you should not influence the NAT configuration with this change.

  Hope to help

  Giuseppe

• Configuration of Vlan SG300-20 for the desktop and server ESXi

  Hello

  I'm fairly new to network so please, be gentle.  I'm setting up a number of VLANs for my lab at home.

  I recently moved jobs and took an Oracle Apps of the Middleware & role has therefore need to start picking up the Apache, e-Business Suite, etc. of the load balancers so need to segragate my network to allow different configurations, I want to install in my lab ESXi.

  My setup is detailed below:-

  I have a router of dryatek 2860n which is my entry for the installation of the internet on IP 192.168.1.1

  My Cisco switch has been set to 192.168.1.2 and the installer to use the 3 layer.

  I have a number of PCs connected to my switch I want to use to administer my ESXi server and have access to the different VLANS.

  VIRTUAL LANs, I need are the following

  VLAN 1	192.168.1.x/24				By default / Internet Uplink
  VLAN 12	10.0.12.x/24				Workstations
  VLAN 13	10.0.13.x/24				Server management interface
  VLAN 14	10.0.14.x/24				Public Interface Server
  VLAN 15	10.0.15.x/24				Private server interface
  VLAN 20	10.0.20.x/24				Storage

  My esxi server has two network interfaces that will have traffic MGMT, Public and private configured as virtual interfaces in ESXi and one that runs my traffic of storage/nfs mounts on a QNAP NAS, I want to make it work on my network

  Here is how I have the ports

  A Port VLAN membership
  G1	VLAN1
  G13 - 20	VLAN 12		Need to access the VLAN 1, 13, 14, 15, 20
  G9	VLAN 13, 14, 15
  G10	VLAN 20
  G7 - 8	VLAN 20		LAG configured to QNAP NAS

  G13-20 are my workstations that need to be on VLAN 12, but must also be able to connect to 13, 14, 15, 20, SSH, RDP, NFS

  G9 is the Interface of MGMT of ESXi who need to have traffic on VLAN 13, 14, 15

  G10 is ESXi storage Interface that needs to access the VLAN 20 only

  G7/g8 are connect to QNAP that ideally I want to configure as a LAG.   When I get more interfaces in my ESXi Server I'll finally the team to match.

  I set up an ip interface in my CISCO switch to 10.0.12.1 as gateway to my workstations and created a static route in my router to allow traffic to the switch.  This does not quite yet.

  I also installed a default route to 0.0.0.0

  I followed a number of guides, but struggling to get my head around concepts and how to achieve the above configuration.

  Ideally, I want to configure this through the CLI as Ive had no end of problems with the web interface of the Cisco switch.

  I believe need g9 of trunk, and other ACCESS is it exact.

  How the workstatations to access the other VLAN?

  Any help would be appreciated

  Thank you

  Paul

  Hi Paul, to break it down a little.

  Host A connects to port 13.

  config t

  int gi0/13

  switchport mode access

  switchport access vlan 12

  ESXI connects to port 9

  config t

  int gi0/9

  switchport mode trunk

  switchport trunk allowed vlan add 13-15 (keep in mind this vlan 1 is unmarked here and is the IP of your server interface)

  This translates

  ESXI = 192.168.1.x 24 gateway 192.168.1.2

  interface vlan 1

  IP 192.168.1.2 255.255.255.0

  no ip address dhcp

  Host A = 10.0.12.x 24 10.0.12.1

  interface vlan 12

  name of the workstations

  10.0.12.1 IP address 255.255.255.0

  With this basic host configuration at shall communicate to ESXI (no other config on the switch)

  If please try to get the connectivity of base first, then can work on the roads and DHCP.

  -Tom
  Please mark replied messages useful

• Trunking VLAN directly from ESXi in SAN servers

  Hi all

  I think that I made a mistake in choosing to go down this path, see the details of the deployment:

  the installation of the failover network limited bandwidth to a single link (failover) instead of 2 Gbps, which can improve performance.  as the solution of trunking VLAN, however out of despair and the stress very load high,.

  I was thinking of redesigning the network all over again from scratch, using the trunking VLAN directly from Server ESXi in SAN to use 2 x 1 GB Ethernet

  cable to enhance the delivery of data to the VM without the use of any

  switch between SAN and servers.

  What is a possible solution using 2 x ESXi and iSCSI MD3000i SAN?

  Kind regards

  AWT

  Since the SAN has only had 2 NIC by controller,
  + so I guess I can provide only 2 Gbps maximum for the ESXi server +.
  + each using trunking VLAN and leave the rest unused switch ports used by the other server. +

  MD3000i does not aggregate links (like Equallogic, for example), but works with MPIO.

  MPIO ESX is NOT able to aggregate links, but he is able to use the different path for different LUN.

  So the solution is simple build at least 2 LUNS, and working with different path (the path is normally automatically selected by ESX)

  André

  * If you found this device or any other answer useful please consider awarding points for correct or helpful answers