Configurations of VMotion and VLAN

Similar Questions

• Wiring of VMotion and VLan question...

  Hello

  I understand the VLANS and how they work, but I'm not really a 'network' guy and I have a few questions...

  My servers are dl380 g6 with 8 network ports. I intend using two for console service, two for vmotion and the other 4 for my virtual switch of production. I know there is no way of vswitches configuration, but it's my game to date plan.

  My question is how can I configure a vlan and segment the traffic for vmotion? I have 4 ports on my physical switch that I put aside for this vlan vmotion. How can I set this up? Wwhat can I do on the switch and how do I have to create a separate subnet in the DNS? ABLES

  My plan is to pass the cables from the ports on esx hosts I put aside for vmotion to the physical switch ports...

  I'm not too sure about that...

  Thank you! points will be awarded to anyone.

  Hello.

  My question is how can I configure a vlan and segment the traffic for vmotion? I have 4 ports on my physical switch that I put aside for this vlan vmotion. How can I set this up? Wwhat can I do on the switch and how do I have to create a separate subnet in the DNS? ABLES

  What kind of physical switch are you using?  Here is a link to the Cisco documentation to create the VLAN on Catalyst switches.  Create a layer 2 VLAN and create VMkernel interfaces with the appropriate IP addresses.  Don't worry about DNS or Routing and keep things simple, if you can.

  Good luck!

• How configure sg300-10 and VLAN ID can be seen in the wireshark

  Hello, everyone,

  I have a question to ask. I brought a new switch sg300-10. I want to use to send ethernet packets. I plugged it with my laptop via port1. On the side of the laptop, I used wireshark to capture. But I have not found that the VLAN ID has been shown in the wireshark (I changed the registry of my laptop, so VLAN IDS must be displayed if it is contained in the frame). So I think the switch was not to configure and the id vlan does not appear in the framework that has been sent by swith. Does anyone know how to understand?

  Thank you

  Hi Jiang, if your administrative computer is connected to port 1, may not understand the tag VLAN. That's why it has the appearance of the GUI hangs.

  -Tom
  Please mark replied messages useful

• Network configuration for ISCSI and VMotion

  Hello

  I have an ESX host configured with the iSCSI storage and am currently working on the best way to affect my NIC I a four VMK vSwitch and two nic

  http://communities.VMware.com/message/1428385#1428385

  I also have an additional switch for VMotion.

  vSwitch3

  -

  ---

  -VMkernel

  -Service 2 console

  -

  ---

  vmnic6

  -

  ---

  vmnic7

  -

  ---

  vmnic6 and vmnic7 are both on the San.

  After adding the new VMkernel and activation of vmotion, I was wondering why this has not shown as an additional path to the storage (I want to know if this is another question). Then I ran "esxcli swiscsi nic list d vmhba33" and of course, only the first four VMK was listed.

  Why the new VMKernel is not automatically linked to vmhba33?

  It would be a bad idea?

  See you soon

  Just to play devil's advocate, why shouldn't be VMotion and SAN traffic on the same link though?

  the iSCSI traffic MUST have a low latency and no mistake.

  VMotion can create advanced that could generate problems in iSCSI traffic.

  No idea why it does not automatically bind well?

  Can you vmkping each IPs Eql?

  You have to add each interface vmkernel of initiator iSCSI, with a command like this?

  esxcli swiscsi nic add - n vmk0 d vmhba34

  André

• Networking VMotion and fault tolerance

  We will configure separate vSwitches for management, vMotion and FT. Each will have a pair of physical interfaces. I wanted to know if it is advisable to have separate IP space for management of ESX, vMotion and FT of if they are all on the same VLAN? If the load is a determining factor, assume heavy vMotion and load FT. 192GO by potential server for 40-50 virtual machines per host.

  I'm a newbie to networking Yes, if separate IP space is a recommendation, which is the basis behind this reasoning?

  I recommend you set up 3 different IP subnets. The subnet IP public/business for the network management and two separate for vMotion private IP subnets and FT. All three go in the VMkernel and from what I've read so far, put them on the same subnet may cause problems with routes traffic through the appropriate interfaces. In addition to this, it makes sense for safety, as amvmware already mentioned.

  André

• Random virtual machines after vMotion and Storage vMotion network loss

  Hi all -

  I have a couple of tickets open with VMware and our supplier of SAN, EqualLogic, on this issue.  Since the configuration of our production and DMZ clusters we noticed that the virtual machines will sometimes drop network connectivity after a successful vMotion and Storage vMotion.  Sometimes, although much less frequently, virtual machines also spontaneously lose network overnight.  What happened only a few times.  The strange thing is that the other guests on the VM host are fine - they lose any network.  Actually, I can do no more than 3 computers virtual host to another, and 2 of 3 can switch correctly, so that we lose the network.  The work around?  Simply 'disconnect' from the virtual NETWORK card 'reconnect' and the virtual machine will start the return packets.  I can also switch the VM troubled return to the host State and it will find the network.  I can it reboot and re - win network.  I can re - install the virtual card completely, and she re - win network.

  VMware has seen a lot of mistakes of SAN in our log files in order to update us our SAN firmware to the latest version.  That seems to have fixed that but we still have the issue.  Here are some of the specifications - all environments are virtually identical except for memory:

  Of PowerEdge R810

  NICs Broadcom 5709

  EqualLogic SAN running 5.0.5 F/W

  We use frames.  ESXi is fully patched.  I haven't seen a boss or not, it is only some guest operating system that loses the network, but we are a Windows environment.

  When a virtual machine loses the network, we can not:

  • Ping to it
    
  • Ping it
    
  • Ping him at the virtual machines on the same host or vSwitch
    
  • Ping outside our network
    
  • resolve DNS, etc..
    

  I followed some KBs VMware without success, including:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1003839
  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & externalId = 1002811 (port security is not enabled)

  -All the VMware tools have been updated to the latest version correct and corresponds to the ESXi host
  -Connected to the service ESXi console, I cannot ping the VM problem by name of host or IP address, but I can ping do not affected by the issue of the OTHER virtual machines.  I can also pings the service console.
  -Connected to the troubled virtual machine itself, I cannot ping other virtual machines, I can't resolve host names, I cannot ping by IP.  The machine virtual CAN ping itself by IP, but not hostname.  I cannot ping other virtual computers on the same virtual switch or network by either IP or host name.  I can't ping the vSwitch network management.
  -All vSwitches are configured in the same way and the same.
  -Notify the switches is set to yes
  -There are a lot of available virtual ports
  -We tried the E1000 and VMXNET virtual cards with no difference.
  -All cards are configured to negotiate, but we tried to force individuals speeds as well as with no difference

  I appreciate your help.  I have problems getting anywhere on this issue with the sellers.

  wkucardinal wrote:

  Still having the issue...

  Sometimes, it might be useful to really check that all uplinks VMNIC for all VLAN does work them. Try this is to create a new portgroup on the vSwitch used by your virtual machines on the host of the first, put a test VM on the portgroup, then go into the NIC teaming policy from the new portgroup and select "Override switch command failover."

  Then down vmnic all except one in unused, then only a single VMNIC is active. Then set the portgroup VLAN to a production of VLAN and try to see if we could ping some expected from the different addresses. If it works, then move VMNIC work until unused and move up to another asset. Try again, and this for all the vmnic. If it works, then you have verified that the configuration of VLANS and other settings are correct on the physical switch in the face of this host ports.

  If several VLANs, repeat the process for all other productions VLAN. Then repeat on the other hosts.

  While that may take some time, occurs if everything is properly configured on the physical switches. When occurs a vMotion virtual machine gets a new "Port code" and is assigned to a new outgoing VMNIC. If there is an error of configuration on one or more physical ports that might seem random, but may still happen on VLAN x on y VMNIC. Given that Port ID policy you use indeed spread randomly VMs on the vmnic these problems may be difficult to diagnose. (Make a disconnection of the VM vNIC gives the virtual machine a new port-ID, which it will move to a new outgoing VMNIC, which might seem to solve the problem.)

• SD205 (switch) and VLAN

  In addition to all my switches Cisco Catalyst (successful), I have a bunch of Linksys SD205 unmanaged switches on my local network.

  I want to configure my network for VLANs, which means I have all my managed Cisco switches will change to a "Routing" configuration   This configuration works well with Cisco Catalyst switches

  Question: the SD205 can operate in this environment?  I know I can't put one of the ports on the SD205 to be 'delivery', but I would like to connect the SD205 to a port of Cisco, which is "effective", so that the devices on the SD205 can communicate to the rest of the world.

  So far, I have not crowned success, then - maybe - they won't work in a shared resource environment.  Someone at - it a definitive answer?  If they simply can't do it, I will stop wasting my time!

  Thank you

  # A unmanaged switch is not compatible 802. 1 q. It will pass any frame ethernet that was 802. 1 q tagged. The only executives who pass through a switch are unmarked, frames that is the VLAN port on the catalyst native.

  If you want to use unmanaged switches, you have to connect to a port configured in mode access, Member of a single VLAN. For example, you can configure a port on the catalyst for access VLAN 10 mode and connect a switch to that port. All devices connected to the switch unmanaged will be VLAN 10. This as you can do.

  But several VLANS: alert the unmanaged switches is impossible because all frames ethernet on the switch must not be tagged.

• Subinterfaces and VLAN

  Hi all

  I was hired on with a State... Now its been awhile, but I do not remember how subinterfaces and VLAN all link together!

  Now correct me where I'm wrong (please), but them VLAN is created on the correct first switches?  When you create a VLAN on a switch you don't need ip or gateway address by default because them VLANS are the switch.  If you want intervlan routing you need a router.  Then, you configure a port trunking between the switch and router (ISL, 802. 1 q).  Now in the router, you can create a VLAN, and here you inter the ip subnet or the default gateway addresses correct?  This is where I get confused as to what reasons do you need subinterfaces?  How they roped VLAN and what would be the logical flow of data?

  Anyhelp would be appreciated!

  Yes you are right. If you are using the layer 2 switch and want to make the intervlan Routing then you need Layer 3 router device. But you must configure the interfaces sub with the default gateway to route traffic. Because there is a single trunk between swich and router so we need sup interfaces for multiple VLANs.

  Interface FastEthernet0/0.1

  Encapsulation dot1q 10 (10 represent 10 ID VLAN)

  10.1.1.1 IP address 255.255.255.0

  If you use a layer 3 switch, then you point all sub interfaces need so then you can create the interface vlan with the default gateway. You must enable ip Routing.

  Interface vlan 10

  10.1.1.1 IP address 255.255.255.0

  Hope this will help.

  Please rate if this can help.

  Thank you

• VPN and VLAN

  We have a site divided into 2 IEE802.1Q VLAN, using no switches Cisco. They have a PIX515 for Internet access. It is also configured to provide inbound VPN access for management and general purpose of access.

  In principle it is possible to set up a new VPN connection which is reflected by its interior traffic be tagged with a specific VLAN ID while all other traffic (including other VPN connections) remain without a label?

  If the PIX ends your VPN from the outside that the answer is no. If the VPN is coming from outside, and ending at the PIX she never travels a VLAN. VLAN tagging is used to identify what VLAN came from a source image and what VLAN it is intended for a current switch vlan can 'route' frame through the appropriate VIRTUAL LAN. Why you want to tag from outside VPN traffic? If it's to control access, you can specify 2 VLANS and VLAN 3 on the PIX (as long as it has code 6.3) and control what VLAN, you want that each group VPN access to through the use of the ACL. Each VLAN on a PIX is treated as a physical interface. It has its own security prefs (0-100) and can have ACL applied to them as well as the physical interfaces.

• Configuration of several interfaces vlan on a layer 3 switch

  I am trying to incorporate a layer 3 switch in a network. (see figure 1 below). My problem is that in the configuration below, the layer 3 switch seems to offer no additional benefit on a layer 2 switch, because it does not pass packets from Layer 3, instead, it will take an additional router configuration.

  If I set up 2 interfaces like no switchports (diagram2) and create virtual interfaces on the switch of level 3, that is to say 0.1/g0, g0/0.2, 0.3/g0, g0/1.1,g0/1.2, g0/1.3, configure dot1q encapsulation and add ip addresses and subnets on each interface, so I understand that I can use the switch of level 3 as a router.

  However this introduces a new problem now, VLAN 1 is on both interfaces, so devices in VLAN 1 on each interface will have point to the default gateway on this specific interface and features of VLAN 1 on G0/0.1 interface must be configured with a different subnet than those on G0/1.1 interface.

  It does not seem logical, am I missing something?

  Assignment.jpg

  

  Figure 1

  assignment2.jpg

  

  Paul

  On a L3 switch you do not configure subinterfaces (usually).

  You create what's called Lass (Switched Virtual Interfaces) instead of this, and what are your L3 interfaces.

  If your L3 switch ports are ports of L2 or other trunks or assigned to a VLAN specific.

  For each VLAN you want to route you create then a SVI IE. -

  int vlan
  IP x.x.x.x
  No tap

  and the default gateway for clients in this vlan is the IP assigned to the SVI.

  Any other configuration of L3 interface, you add to the SVI.

  The only time wherever you actually use the ports of L3 is when you connect to a router for example.

  Jon

• IPS mode vlan inline and VLAN 1

  I am installing a 4255 IPS in pair mode for the vlan inline, but I encountered a problem.

  The thing is that we have a network with multiple VLANs. Some of the servers as well as some users are connected to VLAN 1. The servers are connected to a separate switch.

  I would like to isolate the servers behind the IP addresses.

  I created a new vlan 90, paired with the VLAN 1 on the IPS and placed the server in the new VLAN 90. But this doesn't seem to work.

  I have tryied to put the trunk of the IPS on the main switch on the switch where the servers are located, but in both cases, it did not work.

  I noticed that this configuration seems to work with VLAN different VLAN 1 but I can't make it work with the VLAN 1.

  Does anyone have an idea what could be the problem?

  Thank you.

  VLAN 1 is by default the Vlan for the trunk port native.

  Traffic vlan native out of the port trunk will not have a header vlan.

  So when the sensor receives the traffic it cannot change the header VLANs for vlan 90.

  The sensor will not add a header vlan for packets that do not contain not one.

  If you have two options.

  Either use a vlan different from 1.

  Or the easier method is to change your switch configuration so that a vlan different is defined as the Vlan for the trunk port native.

  Each switch may be different in order to designate the vlan for the trunk port native.

  For the Cat 6K running IOS is "switchport trunk vlan native.

  http://www.Cisco.com/en/us/partner/docs/switches/LAN/catalyst6500/IOS/12.2Sx/configuration/guide/Layer2.html#wp1034721

• Create 2 VLAN (VLAN 1 and VLAN 2)

  Hi all

  I need help and advice with my new Cisco SF300-48. I want to create 2 vlan (vlan 1 and vlan 2). The switch is set at layer 2.

  example:

  VLAN 1 (port 1, 2, 3), vlan 2 (port 4, 5, 6)

  VLAN 1 can communicate with each other (port 1, 2, 3) and vlan 2 can communicate with each other (port 4, 5, 6)

  But vlan 1 cannot communicate with vlan 2.

  Any help would be appreciated

  Thank you

  Johan

  Well, as far as I understand the message communication between the VLAN is not necessary. The thing is, that all ports LAN VIRTUAL (for example VLAN 1 with ports 1, 2, and 3) cannot communicate with each other. Did you check the configuration of the port / VLAN (VLAN configured to each port configuration right / right about the tag-no identified)?

• vMotion and vReplication on a crossover cable?

  Hello

  I am trying to configure 2 ESXi6 hosts physically connected to each other using cables ADJUSTABLE. I want to put in place so that vMotion and vReplication traffic happen using the ADJUSTABLE cables. This is my setup:

  vCenter - 192.168.130.0

  vReplication - 192.168.130.5

  ESXi 1:

  NIC0 - vSwitch0 - vmk0 (192.168.120.50 - Mgmt traffic); default gateway - 192.168.120.5

  NIC1 - vSwitch1 - vmk1 (10.10.10.10 - vMotion, vReplication, Provisioning)

  ESXi 2:

  NIC0 - vSwitch0 - vmk0 (192.168.120.51 - Mgmt traffic); default gateway - 192.168.120.5

  NIC1 - vSwitch1 - vmk1 (10.10.10.11 - vMotion, vReplication, Provisioning)

  ESXi1 and ESXi2 are connected using the crossover on NIC1 cable and I tested ping using SSH between the two ESXis and it works very well on the network 10.10.10.x. I tried to select one of the virtual machines offline, then selected vMotion and it fails to approximately 23% with an error "Could not connect to host". Just as an FYI - without cross-over cables and the NIC1 on the two hosts I tested successfully with vReplication, so I know of files can be copied using the 192.168.120.x network.

  Can someone please help with this? Help, advice or comments are appreciated.

  Thank you

  Sau

  OK figured it. It's the firewall ESXi. I had to activate the 10. range in the IPS allowed for NFC 902. Looks like it's using the cross on connection. Thank you for all your help.

  -Sau

• County of vMotion and Storage vMotion over the last 24 hours

  I am under the below a line to count the number of vMotion and Storage vMotion, which happened in the past 24 hours in the middle and it not give me the required result, but when I combine them in the script that I use to collect additional information, it's just returns 0 (zero) as the County.

  Rely on Storage vMotion and vMotion

  Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) |

  Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.relocate" - or $_.Info.DescriptionId - eq "StorageResourceManager.applyRecommendation"} |

  Measure-object | Select-Object - ExpandProperty County

  Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) |

  Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.migrate"} |

  Measure-object | Select-Object - ExpandProperty County

  Combined script

  Get-Cluster |

  {ForEach-Object

  $Cluster = $_

  $VMHost = $Cluster | Get-VMHost

  $CpuUsageMhz = $VMHost | Measure-object-property CpuUsageMhz-sum | Select-Object - ExpandProperty sum

  $CpuTotalMhz = $VMHost | Measure-object-property CpuTotalMhz-sum | Select-Object - ExpandProperty sum

  $MemoryUsageGB = $VMHost | Measure-object-property MemoryUsageGB-sum | Select-Object - ExpandProperty sum

  $MemoryTotalGB = $VMHost | Measure-object-property MemoryTotalGB-sum | Select-Object - ExpandProperty sum

  $Cluster | Select-Object - property @{Name = "ClusterName"; Expression = {$_.} Name}},

  @{Name = 'vSphere HA'; Expression = {$_.} HAEnabled}},

  @{Name = 'Analysis HA-Host'; Expression = {$_.} ExtensionData.Configuration.DasConfig.HostMonitoring}},

  @{Name = 'HA-Failover capacity'; Expression = {$_.} ExtensionData.Summary.CurrentFailoverLevel}},

  @{Name = 'HA-Admission Control'; Expression = {$_.} HAAdmissionControlEnabled}},

  @{Name = 'Configuration problem'; Expression = {[string]: join (",", ($_.))} ExtensionData.ConfigIssue | {{(Select-ExpandProperty FullFormattedMessage))}}.

  @{Name = 'vSphere DRS'; Expression = {$_.} DrsEnabled}},

  @{Name = "The DRS automation level"; Expression = {$_.} DrsAutomationLevel}},

  @{Name = "Use of the CPU (Mhz)"; Expression is {$CpuUsageMhz}},

  @{Name = "Cpu (Mhz) Total"; Expression is {$CpuTotalMhz}},

  @{Name = 'Cpu use (%) » ; {Expression = {[Math]: Round(100*$CpuUsageMhz/$CpuTotalMhz)}},

  @{Name = "use (GB) of memory"; Expression is {$MemoryUsageGB}},

  @{Name = "Total (GB) of memory"; Expression is {$MemoryTotalGB}},

  @{Name = 'use of memory (%) » ; {Expression = {[Math]: Round(100*$MemoryUsageGB/$MemoryTotalGB)}},

  @{Name = 'VMS NB'; Expression = {$_ |} Get - VM | Measure-object | {{Select-Object - ExpandProperty County}},

  @{Name = 'Virtual machines without VMXNET3 NB'; Expression = {$_ |} Get - VM | Get-NetworkAdapter | WHERE-object {$_.} Type - not "Vmxnet3"} | Measure-object | {{Select-Object - ExpandProperty County}},

  @{Name = 'VMotions NB'; Expression = {$_ |} Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) | Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.migrate"} | Measure-object | {{Select-Object - ExpandProperty County}},

  @{Name = 'SvMotions NB'; Expression = {$_ |} Get-VIEvent - MaxSamples ([int]: MaxValue)-start (Get-Date). AddDays(-1) | Where {$_.} GetType(). {Name - eq "TaskEvent" - and $_.Info.DescriptionId - eq "VirtualMachine.relocate" - or $_.Info.DescriptionId - eq "StorageResourceManager.applyRecommendation"} | Measure-object | {{Select-Object - ExpandProperty County}}

  } |

  Export-Csv "C:\Script\Clusters.csv" - NoTypeInformation - UseCulture

  Could you please someone check the script above and let me know if there is something wrong

  Thank you!!

  But wait a minute, you mean that the "Num vMotions" and "Num of SvMotions" properties have a value of 0?

  This is normal, since you ask for events for the entity of the group, while you should do it for all the virtual machines in the cluster.

  Try the attached version.

• Question on vNetworking and VLAN...

  Our server ESXi hosts and vCenter are version 5.1.  We add a few new servers which will be on our 10GB network.  Our guests up to this point have been on 1 GB.  We do not use the distributed switch.

  How is it important that separate us the Traffic Management and vMotion VM on VLANS separated when using 10 GB network?  We will have management, vMotion and groups of VMS ports on separate vSwitches.  We have our servers on the 1 GB using the VLANS separated but I wonder why is this necessary if you use the 10GB network.

  Really it shouldn't make a difference if you have 1 GB or 10 GB - the main reasons network to separate traffic through the VLAN is security and performance.

  Security - you want to make sure that the management traffic is isolated as it is essential for the control of your environment and the vmotion is not encrypted.

  Performance - again be capable of managing the environment is the key and by isolating the traffic will ensure that he will have the necessary bandwidth

  Also don't forget since you already VLAN have implemented the simplest method for new virtual machines communicate will be on the same VLAN