Similar Questions

• You can install vCenter as a virtual machine with fault tolerance

  The benefits of having vCenter as a virtual machine are features such as HA and snapshots, is there a problem with having a fault tolerance enabled on a virtual machine that is the vCenter server to manage fault tolerance?

  He couldn't see in the documentation for fault tolerance limits

  Well...

  vCenter lists 2 CPUs as required and FT only works with one...

  -Matt

  VCP, vExpert, Unix Geek

• What are the requirements\limitation for configuration of fault tolerance?

  What do I need to do properly configured?

  Here are a few good links providing the requirements and details:

  http://KB.VMware.com/kb/1010601

  http://communities.VMware.com/blogs/vmroyale/2009/05/18/VMware-fault-tolerance-requirements-and-limitations

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  repository scripts vGhetto

  VMware Code Central - Scripts/code samples for developers and administrators

  http://Twitter.com/lamw

  If you find this information useful, please give points to "correct" or "useful".

• for vmware esxi fault tolerance specifications 5

  Can someone tell me where I can find documents to show me the fault tolerance support in version 5?  Are we still liminted to 1vcpu?  How many virtual machines can be set to feet?

  Hello.

  Not much changed. I keep it updated constantly:

  http://communities.VMware.com/blogs/vmroyale/2009/05/18/VMware-fault-tolerance-requirements-and-limitations

  Good luck!

• VMware Fault Tolerance

  Hello

  VMware Fault Tolerance is a good solution for virtual machines in Production? What is the requirements, benefits and the Limitations of FT?

  Hello

  Yes FT is the good soltion for Production VM, Pleace check the bottom of the article for more information

  http://www.google.co.in/#sclient=psy&hl=en&source=hp&q=VMware+Fault+Tolerance+overview%2C+requirements%2C+benefits+%26+Limitations+site%3A+blog.srinfotec.com&pbx=1&oq=VMware+Fault+Tolerance+overview%2C+requirements%2C+benefits+%26+Limitations+site:+blog.srinfotec.com&aq=f&aqi=&aql=&gs_sm=e&gs_upl=1716l8806l1l9026l25l23l0l0l0l0l496l5193l0.4.17.0.1l22l0&bav=on.2,or.r_gc.r_pw.&fp=1ad7a99e02298f12&biw=1366&bih=604

  or

  http://blog.srinfotec.com/?p=243

  concerning

  Rohit

• "Support clustering features such as fault tolerance" option greyed out (unavailable)

  Hello

  For a customer, we try to simulate a SQL using MSCS failover.

  I found a lot of information on the configuration, using only the virtual machines.

  However, for some reason, we cannot select the option 'support clustering features such as fault tolerance', when trying to create the quorum disk in Vsphere.  (See the image)

  We have deployed 1 DC (W2K3 - x 86) and 2 servers SQL 2005 on a W2k3 x 64 environment.

  We use Vsphere 4.0 and ESX 3.5

  I am relatively new to this configuration and I couldn't find any document appropriate, pointing in the right direction.

  Thanks in advance.

  Armand

  Looking again at your attachment, the processor is on the list supported for FT, but upgrade to / with ESX 4 is also a requirement.

  Its interesting to look at the limits of the feet as well. The big one for us, it's that it currently works only on Virtual Machines with 1 vCPU and no more.

  Good luck!

  http://communities.VMware.com/blogs/vmroyale/2009/05/18/VMware-fault-tolerance-requirements-and-limitations

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

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

• Fault tolerance of CAN 'high speed '.

  There is a lot of information on "Low Speed CAN" being "Fault tolérant."  In other words, every time CAN - H or CAN - L is shorted to either on the ground or + 12v, the other non-court-circuit CAN online will continue to work, but with the problems of timing and reduced immunity to noise.  But there is an absolute lack of information on the high-speed CAN fault tolerance (i.e., 125 kb/s speeds).  And if one wants to face that at high speed is as Fault Tolerant as SLOW, why then isn't high speed MAY also deemed "Fault Tolerant"?

  Can someone point me to an ISO document or other official document that specifically speaks to about high-speed CAN and what happens when lines CAN be is shorted to ground or + 12v?  I need a 'official' source of information on this subject, not only his own personal experience or hear - say.

  Thank you.

  ISO 11898-2: 2003 should be a good source for an official response

  http://www.ISO.org/ISO/catalogue_detail.htm?CSNUMBER=33423

• WLC balancing without fault tolerance

  Hello, I need 13 points of service and provide load balancing between all connected AP

  Fault tolerance is not a concern at the present time where my reasoning below.

  I look at by specifying two 4402 controllers with the AP 12 license and configure them both in a single group of mobility, I then manually specify the primary access point controller and distributed accordingly between controllers one on access point two controllers for example 7 and 6 on the other.

  Could I ask if it could it be an acceptable method?

  Concerning

  Hi Mark,

  It is a perfectly acceptable design. If/when fault tolerance becomes a review a 25 model AP can be purchased to provide protection for the two 12 AP WLC Fail-over.

  I hope this helps!

  Rob

• On R2 2012 Windows fault tolerance

  We had a problem with fault tolerance.

  We tried to use a Windows Server 2012 R2 for FT, but when they tried to activate it on the virtual machine; 1 vCPU is allowed.

  It does not have a configuration of 2 or 4 vCPU.

  Probably you have already tried it, but you use the Web Client?

  The FT for more than 1 CPU is something you can do only by using the web client.

  Best regards

• VSAN 6.2 'method of fault tolerance' is not available

  Hello

  I installed 4 6, 0u2 ESXi hosts, each equipped with 3 flash devices and a VCVA 6.0U2

  I built the VSAN cluster without activating dedup and compression.

  But when I try to build a raid5 storage strategy, I can't find the parameter of the method of fault tolerance to allow coding of erasure with RAID5,

  I found the after fault tolerance method parameter enabled dedup and compression.

  Is this good?

  It's surprising. I have 60U2 basic vsan cluster where I am able to see 'Method of fault tolerance' the two option of raid 0 and raid 5/6 without activation of compression and deduplication.

  Can you confirm that you have all the flash disk group when you tried this option

  You can logout/login to the webclient service and check if you are able to see (there is a known, documented problem where some of the policies will not be visible unless you disconnect/connect back to the user interface)

  Was it installed or upgraded charges. If you upgrade, you did the upgrade of the disk version. I think that features will not appear if the upgrades of the disc are not (and automatically activating dedup/compression is an upgrade of the disk)

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

• Protect both virtual machines with features of ESXI fault tolerant clustered disk

  Hello world

  I read the following:

  VMware vSphere with operations management: fault tolerance | United States

  The line that interests me is:

  "VMware vSphere® fault tolerance (FT) ensures the continued availability of the applications in the event of server failure by creating an instance of live snapshots of a virtual machine that is always up to date with the first virtual machine. In the event of hardware failure, vSphere FT triggers automatically failover - ensure no interruption of service and prevent data loss. »

  Question:

  FT can protect both virtual machines that share disks in a cluster configuration? (A cluster SQL instance for example)

  FT can protect both virtual machines that share disks in a cluster configuration? (A cluster SQL instance for example)

  No, you can't, because there is an incompatibility with FT.

  Refer to the documentation for all requirements and interoperability: interoperability of fault tolerance

• Certs host message-&gt; vm fault-tolerant

  Salvation communities,.

  I get the following error message configuration of fault tolerance for a virtual machine, we have in our environment

  The configuration of the fault tolerance of the entity {entityName} has a problem: check the host certificates indicator undefined vcenter Server

  Hi Aneetu,

  The box "check certificates of the host" is unchecked in the SSL settings for vCenter Server. You must check this box if it isn't already