Similar Questions

• Snapshots for virtual machines fault-tolerant

  VSphere availability guide says that you can not fault tolerant VMs snapshot. Otherwise, how would a backup virtual machines?

  If you need to snap for backup, you can stop FT, do the blink of an eye, make the backup, delete the snap and reactivate FT.

  You cannot schedule directly (in the special section), but there are useful scripts that can toggle pi of CLI.

  André

• 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

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

• I would like to know what version of ESXi, vSphere would support the fault tolerance

  I would like to know what version of ESXi, vSphere support (Standard, Enterprise or Enterprise Plus) fault tolerance.

  It is available in Advanced, Enterprise and Enterprise Plus - http://www.vmware.com/products/vsphere/mid-size-and-enterprise-business/buy.html.

  Dave

  VMware communities user moderator

  Now available - vSphere Quick Start Guide

  You have a system or a PCI with VMDirectPath?  Submit your specifications to Officieux VMDirectPath HCL.

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

• 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

• Impossible to enable Fault Tolerance on a cluster of ESXi 4.1

  Can anyone offer any suggestions as to what I may have missed in the attempt of activation FT on our VM vcentre?

  The Setup is a cluster of 3 nodes Dell R610 (record identical machine) with an iSCSI SAN, licenses are Enterprise

  VCentre VM runs on this cluster and I would allow to FT.

  Cluster goes on Site 2.5.2 brilliantly, all green ticks and not a red cross. VCentre VM disk has been eager to zero cloned, CD/disks removed, only uses 1 vCPU

  When I try to activate FT I get an error "the VM runs in a monitor mode that is not compatible to the fault tolerance", which is breathtaking in its usefulness

  Any ideas where to go from here? Is there a more detailed log than that presented in the gui VI who can point me in the right direction?

  Stephen Dunne wrote:

  When I try to activate FT I get an error "the VM runs in a monitor mode that is not compatible to the fault tolerance", which is breathtaking in its usefulness

  See KB 1036775 for instructions on changing the mode of monitoring.  For the compatibility of fault tolerance, you want to 'use Intel VT-X/AMD-V for the instruction set virtualization and software for MMU virtualization.'

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

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

• Default on MK1655GSX - what can I do?

  Hello

  Please help me!

  I have a fault on my Toshiba HDD: MK1655GSX. There is no reaction from the HARD drive at all. It seems to be an electronic fault.
  What can I do?
  How to buy an identical HARD drive and change the Platinum?

  Thank you
  Frank

  Hi Frank

  Maybe it sounds stupid to ve you but I never heard that someone tried to fix the defective HARD drive.
  I use laptops more aged 14 and so far two times HARD drive was defective.
  First problem was a defective mechanical parts and the second time I've been frustrated because more bad sectors have been listed after the HARD drive test.

  In both cases I bought new HARD drive and after installing recovery image, everything was OK again.
  Hard drives are cheap more so I think you should just buy a new one and the problem is solved.

• Pixel white dot on Satellite A100. What can I do?

  Hello

  I have two of them (these are white dots that can be on the white pages) I am currently using software undead pixel
  What can I do? I don't want their
  It's terrible.
  My Satellite A100 237 I have warranty related it a week ago
  It works on this situation?
  I wait your message
  Thank you and best regards...

  Hello Selim

  Usually it is not big thing to do because there is a kind of tolerance of dead pixels and if you have only two of them it is staged as usual.

  Please contact your local dealer and talk to them. Perhaps, it will be possible to exchange the unit.

  Good bye

• 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