Networking VMotion and fault tolerance

Similar Questions

• VCenter Server SSL settings flag and fault tolerance

  I work my way down the checklist to go ft and seem to have a final hurdle.  I need to check the box 'vCenter requires a check of the host SSL certificates' in the VCenter server settings dialog box.  I'd love to do it, but the fine print is a bit scary.  It seems that if I check the box, SSL Digital footprints to the ESX host will be compared with SSL Digital footprints that vCenter recorded for them.  Whether all withdrew, I'm off to the races.  If not, I'm afraid that the hosts will be removed from the surface of the Earth (vCenter)!

  So, two questions: is there a way to make this verification of fingerprint digital ssl manually in advance?  And the process is really also sinister that my mental image makes?  Probably, if I uncheck the box, everything will return to normal (less the ability to implement FT) but I'd be happy to hear from someone who has been there.

  Thank you.

  McZ

  Don't forget to accept than the ESXs of fingerprints before you check off the box (at the bottom of the same windows).

  If you not agree, you will see that all your ESX lost the connection.

  But also in this case, don't worry... simple reconnect them

  André

• NEITHER 9852 communication with fault tolerant CAN materials

  Hello

  I have a cRio 9074 and recently bought a module NI 9852 2-port low-speed/fault-tolerant CAN.

  It's my first attempt at network comms in cRio and I realized that none of the devices with that I want to communicate are immune to failures and fault-tolerant physical layer requires different endings to 'normal' high speed MAY (immediately after I broke the seal on the box, of course!)

  Is it possible that I can configure the physical layer for this configuration to work reliably (alebit to)< 125="" kbps="" and="" with="" no="" fault="">

  Kind regards

  Chris

  I'm sorry. The low speed / transceivers and breakdown-tolerant high speed MAY use different communication protocols.

  HS CAN is recessive when CANH and CANL are both to nominally under 2, 5V. It is dominant when CANH is 3.5V and CANL is 1, 5V.

  LS CAN is recessive when CANH is a CHANNEL and 0V to 5V. It is dominant when CANH is 3.6V and CANL is 1.4V.

  You can see that they are almost the same for the dominant, but different for recessive. In addition, the sequence of end between two buses is different. For a HS-bus, you usually resistance 120 ohm between CANH and CANL at both ends of your bus.  A bus of the LS, you have a terminating resistor separate for CANH and CANL (for RTH and RTL).

• SAN multisite and VMware Fault Tolerance

  Hello

  My apologies if this is in the wrong section.

  I have a requirement for the two main rooms, with SAN and ESX hosts in each room.

  In total I have, for the sake of arguments, 200 VMS, with a split 50-50, so 100 in each room Basic.

  I want to use VMware of fault tolerance for machines remain operational in the event of a major failure or the other room Basic.

  I think I can use Multisite SAN to do.

  Please see attached diagram fo what I want to do, I know that the diagram is not correct but I drew it fast just to try to explain the scenario.

  What I want to know (or have help on) is:

  Is it possible to use fault tolerance in this way have no downtime in the result of a failure of basic room? (basic rooms are not very remote and use the same networks)

  How does multi-site SAN work, are there articles I can read to help me understand this?

  Multisite perhaps SAN iSCSI or fibrechannel?

  Thank you.

  SAN should resemble a single San for all ESXes. It doesn't matter how you do it.

  > If I my synchronous SAN mirror, might simply use FT for the vcenter as well?

  It is possible for the small environment. In general, vCenter requires 2 vCPU, while FT works for uniprocessor VMs only. But do not overestimate FT, it is not a universal solution and the universal answer.

  > Also with FT, can you specify the server host in the cluster to act as the secondary?

  Directly - no. The only way - to create link VM to any resource that is available for 2 ESXes only.

  ---

  MCSA, MCTS, VCP, VMware vExpert 2009

  http://blog.vadmin.ru

• Network: Etherchannel vs. Fault Tolerance

  Here's my question.  I'm not a network guru but I understand if you assign NIC several ports to a virtual switch you gained transmit bandwidth (all ports are used to send), but that the same is not true on the receive side because you need a MAC and a layer of arbitration that can distribute traffic entering.  My hypothesis is that there is no way to go other than having two network adapters to the same switch and using Etherchannel trunking.

  So now, we have a trade off power.  If I choose alternative NIC to different switches for the fault tolerance, I am limited to only 1 GB on the side of the reception no matter what I do.

  If I have strange ESX hosts goes to switch A and even attending the B switch, it does not help much nor how many stores are building a reserve of 50% in their ESX capacity reservations.

  So assuming that my above assumptions are met, I'm curious to know what strategies and practices other stores allows to increase the pipeline of reception beyond 1 GB (without using 10gbE) without exposing to excessive exposure to a change of failure event.

  Thank you!

  Yes, that's basically it.

  I attended a VMWorld 2008 session given by a VMware employee who specializes in the robot of networking. He said that the "from port ID" is the method to use which is the reason why it is by default most recommended balancing. Hash TCP/IP method is OK, but has the configuration requirements of specific physical switch (EtherChannel), which makes it risky to be set up properly or poorly maintained. The hash of the IP would allow a simple VM for potentially communicate with multiple hosts on multiple physical links, but in most environments, it is not really necessary.

  Yes, when you have a redundant configuration of physical switches the redundant natachasery for the virtual switch should be distributed to multiple switches.

• Tolerance of performance and fault NFS

  I would like your ideas on tolerance Performance NFS and fault...

  Goal: Provide the best: active fault tolerance, through put and load balancing using only NFS data stores.

  Data: Each ESX Server has 2 1000 NIC FULL, one going to each switch, switch 2 blades on Cisco Catalyst 6500, 4 connections per storage device goes 2 - FAS3100 series NetApp

  Here is what I have so far (below), did I miss something?  :

  • 1. Networking (6.8)

  • a. impliment cross stack Etherchannel

  • b. strategy for load balancing to create Etherchannel IP

  • 2 storage

  • a. configure the NetApp with Multimode ALIVE network

  • b. assign Alliases for each Volume with an IP address only (6.7)?

  • 3 Vmware

  • a. When you add storage, use a unique IP address for each data store.

  • b. change Vswitch defined political balancing "route based on the hash of the IP.

  Referance:

  NetApp and Vmware Virtual Infrastructure 3 - best practices in storage | TR3428 | v 4.4

  OK that looks like at 3750's stacked, you should still be able to Etherchannel.  If these switches also support devices on the production network I also recommend to create a VLAN separate strictly for your storage space if you don't have already done.

• Network reconfiguration/addition Vmotion and FT

  Hey people,

  I came in a VMware configuration that includes 3 guests (5.5 Enterprise license), with lit HA.  As I am trying to understand more advanced features, it seems that the network is not configured in the best conditions. It was determined at the start when I tried to learn a little more about FT, and the first message that I got was that it has not defined the FT network.  So I plunged in each host's network configuration and found the following:

  

  As this table shows, there is no defined network FT or vMotion.  Therefore, the question of the day would be, can I add in the each host (with its own IP address range) without impacting the production? My placement of these networks would be on vSwitch1.  Normally, I'd also have the management on the same network switch (where all port core services would be a vSwitch and VM on the other switch, but as I said, this has been inherited by me).

  Thanks in advance for the help.

  James

  Here's my recommendation

  This recommendation is if you just want to play with FT...

  in a productive environment I would recommend ad two vmnic to split the traffic iscsi and vmotion/FT.

  concerning

• Host of migration on 2 no and 2 network vMotion

  Hello

  I'm trying to migrate virtual machines between the two groups.  I use a host on the new cluster as the go between.  This host is connected to two no and two networks of vMotion.

  I would say that I can't have the two vMotion active network at the same time.  So I uncheck the checkbox vMotion IDE oucederomsurlesecondport a vMotion vmk and allowing it on the other hand.  But I find that I have to reboot the host to get to ping or vMotion to the bottom of the other network for vMotion.

  It seems that this is not the second connection.  If I consult the routing table, it is empty for the second connection.

  It seems that I just need to force her to arp on the second connection.  Or somehow for vMotion service restart.

  Any ideas?

  Thank you

  Mike G.

  The problem turned out the vMotion subnet get pinned to a vmk / uplink that was not yet active.  I discovered using esxcfg-Highway - l

  So here's a ping on the failure of network vMotion.

  ~ # vmkping 333.444.1.65

  PING 333.444.1.65 (333.444.1.65): 56 data bytes

  -333.444.1.65 - ping statistics

  3 packets transmitted, 0 packets received, 100% packet loss

  Here's the arp table.  He is aware of the subnet, but it's somehow pinned to the layer of VMware to vmk6.  vmk6 is vMotion on fabric B, which is currently not working due to the non-vmware of the reasons.

  ~ # esxcfg - road - l

  VMkernel itineraries:

  Interface of network gateway subnet mask

  777.444.124.0 255.255.255.0 subnet local vmk1

  777.444.125.0 255.255.255.0 subnet local vmk3

  333.444.1.0 255.255.255.0 subnet local vmk6

  555.888.128.0 255.255.255.0 subnet local vmk4

  555.888.158.0 255.255.255.0 subnet local vmk0

  by default 0.0.0.0 555.888.158.1 vmk0

  Here are the arp table after I deleted vmk6 via vCenter.  333.444.1.0 is now pinned to vmk5.  Or deactivation of vMotion, dropping the uplink or a reboot would turn the road to vmk5.  Only deleting vmk6 fix it.  vmk5 is vMotion on A fabric, that works.

  ~ # esxcfg - road - l

  VMkernel itineraries:

  Interface of network gateway subnet mask

  777.444.124.0 255.255.255.0 subnet local vmk1

  777.444.125.0 255.255.255.0 subnet local vmk3

  333.444.1.0 255.255.255.0 subnet local vmk5

  555.888.128.0 255.255.255.0 subnet local vmk4

  555.888.158.0 255.255.255.0 subnet local vmk0

  by default 0.0.0.0 555.888.158.1 vmk0

  Here's the ping works once vmk6 has disappeared.

  ~ # vmkping 333.444.1.65

  PING 333.444.1.65 (333.444.1.65): 56 data bytes

  64 bytes from 333.444.1.65: icmp_seq = 0 ttl = 64 time = ms 0,346

  64 bytes from 333.444.1.65: icmp_seq = 1 ttl = 64 time = 0,121 ms

  64 bytes from 333.444.1.65: icmp_seq = 2 ttl = 64 time = 0.146 ms

• 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.)

• 6.0 Update 01 vSphere fault tolerance

  Hello everyone,

  I have a problem whene I activate Fault Tolerance on dv01.

  It is the configuration of my physics

  • 2 ESXi 06 update01 build 3073146
  • 1 cluster HA active
    • Ordered admission disabled
    • Disabled DRS
  • 1 with port configuration of vMotion group vDS
  • 1 starndar vSwitch for Fault Tolerance with 2 x Intel® Ethernet Converged Network Adapter X 520 - T2 10 Gbps
  • e

  Dv01 Config

  • 4 vCPU
  • 3 ramdisk stored a first shared data store datastore01 1.35 to:
    • Reset Eager 136 GB Thik provisioning
    • 500 GB Thik provisioning eager to zero
    • 600 GB Thik provisioning eager to zero
  • connected to the port vDS group 1 VMXNet3 network adapter
  • latest VMware tools installed
  • Guest OS Windows Server

  When activated the fault tolerance, I chose the ESXi02 and second datastore02 shared data store 1.28 at: the vmdk and vmx file is created successfully and I free 44Go on the datastore02 of a second.

  But whene I try to turn on this dv01 I have this error

  • vCenter car not power on the secondary VM
  • and whene I look on the event, the error is not "enough space for the secondary virtual machine."

  Can someone help me, please to fix this whene I enabled FT on litle VM02 with 1 thin vdisk, is working but for dv01 is not work

  THX in advance

  Best regards

  Hi DZinit,

  The computation of the space you need on the second data store, you take the file vswp into account. This will generate enough to on and be equal to the size of RAM allocated to the VM.

• Advice on how best to configure the network adapters and virtual switch in ESX host

  I'm new to VMware and am its implementation.  I got my training a few weeks ago, and now I'm configing my hosts.  I have 3 guests, each have 2 network cards.  There is a virtual switch that ESX creates when it is installed (vSwtich0).  The books said that it is advisable to delete the VM network port of virtual machine that is assigned to the value group default virtual switch and put it on another virtual switch so that you keep your management network separated from the network of the vm for performance and security.  If I do this, all my virtual machines will have to go to 1 NIC b/c I only have 2 NICs per host.  I thought that I have just to keep all my groups of ports on the default vSwitch0 and add my second NETWORK adapter so that I can take advantage of the Association of NICs for redundancy and load balancing.  However, I'm not sure on the performance and the security risks.  Do you have any ideas or advice?  I could also create two virtual switches and put my virtual machines on one which would have a NETWORK card dedicated and put my service and Kernal VM console on another virtual switch with a dedicated network card.  However, in this scenario, I have no fault tolerance or load balancing.  We are a small shop and we have about 10-15 VMs on each host.  I don't have access to b/c distributed switching we paid only for the company (not more).  Thank you.

  Hi and welcome to the forums,

  With 10-15 VMs per box and I guess that I would seriously consider adding two extra cards for each host in the production machines. You could then do something like:

  vSwitch0 - vmnic0, vmnic2, vmnic3 - Console of Service, VM LAN network

  vSwitch1 - vmnic1 - VMkernel

  That would give you redundancy and performance to access your hosts (SC) and also for all your virtual machines. The VMkernel would get a NETWORK card dedicated for vMotion and could be on a separate network. He didn't need redundancy really as if the NIC sank the only issue is that you cannot vmotion virtual machines. In this case you would just move one of the NIC workgroup through to those switches manually.

  If you only have 2 network cards, then I would say having a vSwitch with two attached network adapters and VLAN the VMkernel may be off. I want absolutely to the redundancy of having two cards together.

  Hope this helps,

  Dan

• Fault tolerance limits

  I would like to implement fault tolerance for a couple of our virtual machines, but I was reading and I have a few questions.

  1. it is said that you must have 2 vmkernel NIC dedicated to fault tolerance. Can it be shared with vmotion NIC?

  2 FT does not support SMP. Is this still the case? We lack ESX 4 Update 1.

  3 FT does not support snapshots. VReplicator allows us to reproduce our vm. This creates a snapshot during replication. That are not or not be possible?

  Thank you

  Scott

  1. you need at least 1 vmkernal NETWORK card dedicated for FT (or a new VIRTUAL local network, if you have 10 GbE) there is a lot of traffic that will be flowing for this shot

  -You can see a design on my website http://kendrickcoleman.com/index.php?/Tech-Blog/vsphere-host-nic-configuration.html

  2. Yes. You can't have FT w / 1 vCPU VMs currently. But if you have some awesome Nehalem procs, you may only have 1vCPU for your boxes of criticism

  3. they will fail. The snapshots are not possible on the VMS FT. As a result, backups will not work. I know it's one of the huge problems of scenario best IP, Setup a script to make a virtual machine out of FT, run the backup, and then select FT. A lot of work for a final result.

• XEON X 3210 fault-tolerant

  Hello

  I have a Dell PowerEdge 840 and 860 servers, they are also supposedly compatible with ESXi and vCenter.

  I downloaded the trial version of vCenter Server and ESXi and wanted to build a cluster.

  Unfortunately, this is not possible because it supports the CPU is not a fault-tolerance.

  These and the following hardware configurations

  Dell PowerEdge 840 and 860
  
  CPU: Intel Xeon X 3210 with VT turned on in the BIOS.
  RAM: 8 GB / system
  Hard drives: Dell 840 GB RAID 10 4 x 320
  Reference Dell 860 1, 2 x 500 GB RAID
  System: ESXi 4.10, 381 591
  VCENTER 4.1 345 043
  Network: a network of 100 MB of Internet traffic map
  and a single 1000 MB card for traffic network.

  According to Intel, the processor over VT is supported.

  
  Thanks for the help in advance.

  ICH verfuge über einen Dell Poweredge 840 und 860 server, sharp auch angeblich scripte sind mit Vcenter und ESXI.

  ICH habe mir die Testversion von Vcenter Server und ESXI runtergeladen und ein Cluster can actually wanted.

  Leider ist dies nicht possible, da die CPU´s keine Errortolerant unterstuzten.

  Es sich und die following Hardwarekonfigurationen more

  Dell Poweredge 840 und 860
  
  CPU: Intel Xeon X 3210 mit aktivierten VT im BIOS.
  Arbeitsspeicher: 8 GB I system
  Speaker: Dell RAID 10 4 x 320 GB 840
  Reference Dell 860 RAID 1 2 x 500 GB
  System: ESXI 4.10, 381591
  VCenter 4.1, 345043
  Netzwerk: I eine Netzwerkkarte 100 MB as Internettrafic
  und I eine Netzwerkkarte 1000 MB as den internal traffic.

  Laut Intel hat der oben genannte Prozessor auf support VT.

  
  Vielen Dank für die Hilfe im Voraus.

  3210 x is not supported for FT. http://KB.VMware.com/kb/1008027

• SAN with VMware Fault Tolerance storage redundancy

  We built a new data center, with the idea in mind to use VMware Fault Tolerance to create a virtual environment without service interruption between two data centers.  The goal is to have the VMs to continue to operate even with the loss of access to an entire datacenter, including SAN storage units.

  I'm looking for a way for a vSphere 4 virtual infrastructure to be able to write to storage replicated in two different datacenters (with low latency of connections between data centers).  We can do with the networks and host servers, but I found nothing in the documentation of tolerance to failures to mention something else 'shared storage' we have experienced a failure of the individual units of SAN storage (including total loss of hundreds of virtual machines) and hope that we can eliminate the unit of storage as a single point of failure.

  Someone did he do it, or how it could be done?

  Hello

  In order to clarify what idle-jam talks about, you can watch this video of HP and VMware on YouTube.

  -hth

  Kind regards.

• Fault tolerance switch port guidelines

  I am setting up our lab to test fault tolerance. I plan to use a vSwitch sperate isolated FT and separate FT VLAN. Are there specific indications for siwthc trial paramΦtres I can give to my network group. I want to just make sure that the physical ports are configured before idelly I start testing.

  I didn't know that your plan was to use vSwitch dedicated only for FT traffic and nothing else.

  So, I recommended that you use the "load-driven" (new feature in 4.1) for a better distribution of traffic between natachasery on vswitch but also for network IO contol to partition the link between the different types of traffic. But you are right, as long as the vswitch is dedicated for FT, no need to use it.

  The extent of the Cisco switch port config, if you run the two natachasery to the same switch, you can use etherchannel, although the single link 1 Gbit/s is more than enough for traffic FT. Also, I recommend to enable portfast on ports involved to avoid any interruption when other devices added to the network, triggering the spanning tree protocol recalucations.

  For traffic to

  distribue distributed by grouping network adapters, configure the virtual switch through which the logging

  traffic flow on the road based on IP hash policy. This strategy uses

  source IP address and destination of traffic flows to

  determine the uplink. Pairs of feet between different hosts ESX employ more than

  a pair of source address and destination for logging of FT.

  To use the route depending on the hash IP policy, the physical switch ports must be configured etherchannel mode.