Similar Questions

• VSAN observer reports errors in DupAckRx

  Hello

  We have now successfully started with VSAN.

  After resolving some problems such as phantom messages "host cannot communicate with all the other nodes in the cluster active vsan."

  We get green "health checks", performance of multicast controls works as well.

  But observant VSAN reports a large number of failures of DupAckRx. (see attached screenshot)

  

  Network or vSphere Analyzer reports any network problem.

  Someone at - it an idea of what the errors mean?

  Best regards

  Mike

  These are unrelated to Mike.

  Him "host cannot communicate" is a known issue which we are working to solve.

  Can you please contact our support org for the latest information on what was expected a fix?

• VSAN error: host is in an active VSAN cluster but has no active VSAN service

  Guys,

  When I try to configure the vSAN cluster, I get the below error message:

  VSAN error: host is in an active VSAN cluster but has no active VSAN service

  Help, please.

  Thank you

  John

  Please follow lla: http://www.vmwarearena.com/2014/03/vsan-error-host-is-in-a-vsan-enabled-cluster-but-does-not-have-vsan-service-enabled.html

• vSAN - error of areas

  Hello

  I created a new cluster 3 host in vCenter 6 and active vSAN, added the correct storage (1 x Flash, 3 x HDD). They are all mounted and in good health. switch vSAN has been implemented and is connected by 10 GB switches, MTU sizes on virtual cards are set to 9000 and attached to 9240 on physical switches. As IGMP also enabled on the switches.

  So the problem I have is that I can't migrate all VM storage for the storage of vSAN, the error I get when trying to migrate is:

  "Cannot complete the file was created. This storage strategy requires at least 3 areas fault with guests contributing storage but only 1 was found. Failed to create the object.

  A bit strange that I have 3 domains fault with a host in each.

  Currently, I have not all tracks on the resolution. Any help would be grateful.

  Thank you very much

  An update!

  I solved the problem, it seems that the size of the MTU of the virtual switch did not have virtual cards (9000 MTU size).

  Now everything works fine and dandy! Thanks for your help.

  Thank you

• vSAN 5.5 U2 - Flash Cache error reading configuration ' reason: an error occurred during the configuration of the host.

  Hosts: DL360 G6, dual quad core, 64 GB of RAM

  Discs: 3 SAS 10K rpm and 2 SSD Spidles.

  I am trying to set up one of the hosts of Read Cache Flash but I get the desciptive never so much and the defenseless error message...

  "Configuration on disk/vmfs/device/disks/naa. < longguid > has failed. "Reason: an error occurred during the configuration of the host.

  I hope that there is a log file I can verify for a more profound description of this lame error message.

  Can someone tell me where I can check on this error?

  Thank you

  Oh. k. so, it is the function of Read Cache (vFRC) Flash of vSphere and nothing to do with VSAN

  check the diaries which is throwing this error.

  ESP: /var/log/hostd.log and log/var/log/vmkernel of corresponding calendar. This will show what is happening here

  You can check the following

  one.

  Check if SSD LUNS are not used / no other partition

  # partedUtil getptbl/vmfs/devices/drives.

  b.

  Also check that the SSD lun on that host are local and eligible for the vflash

  List of devices # esxcli storage vflash

  Thank you

• Error "host cannot communicate with all other nodes in the cluster of enabeld VSAN.

  Hello community,

  We have a problem (?).

  We have a cluster VSAN enabled with four hosts. Everything seems perfect,

  -the configuration is good,

  -Displays the page state VSAN "network status: (green arrow) Normal."

  -Displays the disk management page "status: healthy" for all of our groups of disks.

  -Same 'esxcli vsan cluster get"on each host returns a 'HEALTHY '.

  But we have a yellow exclamation littly on each host 'host cannot communicate with all other nodes in the cluster of enabeld VSAN.

  Anyone with the same problem? Anyone with an idea or a hint?

  Thank you!

  Update vcenter to the latest version and the error disappears. Problem solved! The 'old' version of vcenter performed since September 2014, strange.

  Thank you very much for your help!

• "Fatal error: 10 (from resources)" - ESXi 5.5 U1 with motherboard ASUS Z87-DELUXE - VSAN Homelab

  Looking for help to build my 3 node VSAN Home lab.  This section of discussion has a lot of details to help someone else in the same boat as me (present or future).

  The goal:

  Operation of a laboratory at home with ESXi 5.5U1 where the primary storage is VSAN.  Prescription: 3 hosts at least 2 cores and 8 GB of RAM and at least a SSD and a SATA drive for each host.

  The problem:

  When I try to install ESXi 5.5 U1 on my host (ASUS build details below), I get the message "error loading tools.t00 Fatal Error: 10 (from resources)" during the installation process. Installation process is one USB Flash drive to another.

  When I install ESXi U1 5.1 on the same system, everything works perfectly.  Installation process is one USB Flash drive to another.

  Not yet tried ESXi 5.5.

  What I've done so far?  Too much to mention, but here, it's where I made some progress.

  
  

  Custom installer images ESXi to take in charge the following (according to the ESXi Z87 - PRO, Adaptec ASR-6805E, 5.1U , experience before VMware: How do not support SATA AHCI Controller with ESXi 5.5 and http://www.derekseaman.com/2013/08/building-haswell-esxi-server-vsan.html):

  • https://communities.VMware.com/servlet/JiveServlet/download/2278196-112344/VMware-ESXi-drivers-SCSI-aacraid-510.5.2.1.29...
  • https://communities.VMware.com/servlet/JiveServlet/download/2278196-112345/IGB-4.2.16.3-offline_bundle-1138313.zip
  • https://communities.VMware.com/servlet/JiveServlet/download/2278196-112346/NET-e1000e-2.3.2.x86_64.VIB
  • http://vibsdepot.v-front.de/Depot/VFT/SATA-xahci-1.17/SATA-xahci-1.17-1.x86_64.VIB
  • When installing ESXi, use the option "Shift-O" after the ESXi Setup screen and type '< space > formatwithmbr', this allows the USB Flash drive to start the ESXi Hypervisor installed (assuming that Legacy USB is enabled and that the USB is plugged into a USB 2.0 port, does not work with USB 3.0 ports)
  • With ESXi 5.1U1 image, this acknowledged the NETWORK interface integrated Intel I217V

  Set up the parameters for the 'Advanced' in the BIOS (F7 in option):

  • Reset the default BIOS (option F5)
  • CPU Configuration - advanced, "Technology of virtualization Intel" ENABLED
  • Start-up, CSM, Boot - devices only (UEFI disabled) legacy
  • Startup, SVM, Secure Boot - "other OS".

  What settings BIOS configurations / had no impact/weird behavior?

  • When I plug SATA and SSD controller SATA Intel colors 'Brown' ports, ESXi can't see readers at all, no matter what VIB files, I add to the ISO image.  So, I had only work with yellow ASMedia controller ports.
  • I have disconnected the SATA and SSD drives, disabled the Intel and ASMedia controllers.  This did not help.
  • I disabled the office equipment that has no benefit to ESXi (Advanced, Onboard Devices Configuration) - controllers SATA Intel etc., embedded wireless, Bluetooth, Audio.  This did not help.
  • Thinking that Thunderbolt could be a problem, I tried to disable adapters Thunderbolt (Advanced, Onboard Devices Configuration) and then I had problems with the start-up of the image ISO of ESXi.
  • I even added this http://www.virtuallyghetto.com/2013/09/running-esxi-55-on-apple-mac-mini.html Mac Mini Thunderbolt pilot ESXi ISO image, without success.

  What I intend to do?

  • Upgrade firmware Z87 DELUXE (BIOS update tool does not work, "Violation of security checking" reports, will probably have to install Windows 7 to use the updater tool).
  • Try to install ESXi 5.5, then use AUVS to update 1.
  • Continue to build the whole environment with ESXi 5.1 U1 to burn and continue troubleshooting ESXi 5.5 U1 on a single host.

  What is the hardware configuration of ESXi host?

  • Card mother ASUS Z87-DELUXE-DOUBLE (integrated RealTek & Intel I217V NIC, adapters Thunderbolt, 'Brown' Intel 'Yellow' ASMedia SATA connectors and)
  • Information of Z87-DELUXE-DOUBLE BIOS ASUS 1008 x 64, EC Version MBEO-Z87-0224, ME Version 9.0.21345, Build Date 17/05/2013
  • HASWELL from Intel i7-4770 LGA1150 processor
  • 2 x Corsair Vengeance DDR3 8 GB of RAM
  • 1 x Corsair SSD Force 3 240 GB disc
  • 1 x Western Digitial Green 2 to SATA Drive
  • 2 x Corsair 32 GB USB Flash Drives (one for ESXi ISO image prepared with UNetbootin - homepage and downloads and the other is the ESXi startup disk)
  • No PCI-e adapters (using the integrated storage controllers and network)

  Once I get it working, I'll update this thread and provide a detailed http://www.vcdx133.com/ report

  Upgrade to ESXi 5.1 update 1 for ESXi 5.5 Update 1 via esxcli worked.

  Intel Z87 Serial ATA controller is not recognized by ESXi.  Don't know what driver is missing, but the ASMedia Serial ATA controller works.

• Error Code UCS 6140 Cluster

  Hi all

  I'm under a pile of 6140 UCS with 1.4(3q) Version UCSM.

  I have a critical error.

  The error code is F999590. This fault code have no match in the "Cisco UCS errors and Error Messages Reference" doc.

  With the error description, I found:

  fsmFailSwFcSanBorderDeploy

  Error code: F999789

  Message

  [WSF: FAILURE]: sam:dme:SwFcSanBorderDeploy

  Explanation

  None is defined.

  Recommended action

  Copy the message exactly as it appears on the console or in the system log. Research and try to

  solve the problem by using the tools and utilities provided to http://www.cisco.com/tac. Refer also to the

  Release notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you can not solve

  the problem, run the command show support and contact Cisco Technical Support.

  Fault details

  Severity: critical

  Cause: WSF-failed

  mibFaultCode: 999789

  mibFaultName: fsmFailSwFcSanBorderDeploy

  moClass: sw:FcSanBorder

  Type: WSF

  How can I study?

  Thank you very much.

  Florent

  Hello Florent.

  We need more balls and so I suggest you open a service request in the TAC to deepen the following for FI B CF links error message.

  ------------------------------------------

  Code: F999590

  Description: [WSF: FAILURE]: B (FSM:sam:dme:SwFcSanBorderDeploy) CF Uplink port configuration

  The object affected: sys/switch-B/border-fc

  Creation date: 2011-10 - 10T 09: 56:12.953

  -------------------------------------------

  The following information would also contribute to the investigation

  Were there any incompatibility of VSAN between FI and FC switch upstream?

  Is FI running End host or switching mode of CF?

  CF trunking is enabled on these links?

  If the FC ports are rising and active, it could also be where the error got erased but error condition remained on.

  Padma

• VSAN membership down on the CF mapped uplink port

  Hello

  Since I upgrade Cisco UCS Manager, all frame and fabric of interconnections of version 2.2 (1), I have a few minor flaws.

  I configure ports 31 and 32 as FC uplink ports and mapped each port to a vsan:

  Port 31 = VSAN 'blue '.

  32 port = "red" VSAN

  (I know, it is not common to map two different VSAN to the same fabric, but I have to)

  Since the update, I get minor flaws:

  31--> FCoE or FC uplink port is broken on 'red' VSAN / membership-down

  32--> FCoE or FC uplink port is broken on 'blue' VSAN / membership-down

  I have no channels of port FC or FC enabled link mode. Interconnection of fabric is EHM.

  Even in other tissues.

  Can anyone help me or is it the same cosmetic problem as stated in the quote?

  FCoE Uplink vsan membership fault for any vsan not configured upstream Symptom:
  
  Fabric Vsan Membership Down fault message on FCoE uplink ports
  Severity: Major
  Code: F1083
  Name: Fabric Vsan Membership Down
  Conditions:
  Observed with UCSM 2.1 and when FCoE uplink port is configured on the Fabric Interconnect
  Workaround:
  None.Error message is cosmetic.
  

  Thanks in advance

  / Danny

  Hello Danny,

  Yes, it is a cosmetic issue in UCSM 2.2.1

  the question is followed by

  https://Tools.Cisco.com/bugsearch/bug/ CSCum89468

  The one that you cited ( CSCud81857 ) is specific to the rising FI FCoE in version 2.1 of UCSM.

  HTH

  Padma

• Minor Vsan warning

  Hello world

  I have an error in my domain UCS - M name is my VSAN is out of service. Any idea of what is the cause?

  Thank you

  Hi Jeff,

  Walter, a photograph would be extremely useful to restrict your question. However, if the error you receive is a minor alert the bug that you run is;

  https://Tools.Cisco.com/bugsearch/bug/CSCuj71400/?reffering_site=dumpcr

  In the workaround in the bug, you can check if it is indeed the bug. If the alert is not a minor warning and not the bug listed please include a picture of the error message, so we can gather a better understanding of your issue.

  Kind regards

  Qiese Sa'di

• vSAN mini Dell H730 after update02 health

  Hello.

  I have 3 servers based on Dell H730mini. After the upgrade to esxi update02 vSAN was broke (because they were old drivers for the RAID).

  I have excluded all the vmware cluster servers, updated RAID drivers on compatible. After I created a new server cluster and it contains. Everything works.

  However, vSAN health module indicates the error type: "correct version of installed virtual san health invalid query. Relocation of vib module on each server correctly (not work), but in the cluster, all the information indicated the same version "in ESX 0.0.

  ESXi 6.0.0 38255889

  Vserver 6.0.03339083

  Any ideas?

  Hello, it seems to me that you must update vCenter.  Who is on the last version?  Thank you, Zach.

• Maximum latency of VSAN light

  I sent a 2 cluster nodes VSAN on a remote site with a main witness VSAN device located in the data center.

  I usually see latency between 55 and 60 ms between VSANS storage nodes and the witness device... just a little more the 50ms published requirement.

  Of course this will raise an error as much stock of health VSAN is concerned.

  The VSAN itself seems to work fine, at least superficially.

  What is the maximum acceptable value for the latency?

  I have to find another place to host the witness device so that I can reduce the latency of less than 50 ms, or I can continue to operate in this mode?

  Finally, assuming that 60ms latency is tolerable, can I change health check test to be just a little more tolerant of increased latency results?

  Thank you

  This is a known issue, I posted this some time ago and it should be fixed with the next update, you can ignore the warning. 500 ms is the threshold for ROBO and 200ms to stretched. Sorry about that,

• Battle of VSAN (2 node with node witness Cluster) cannot write to VSAN

  I'm having problems with my Cluster active VSAN and can't seem to write in the data store or migrate a virtual machine to download whatever it is him. When I try a vMotion VM over the VSAN DS I get an error "file impossible creation a full operation, an unknown error occurred."

  Here is my layout,

  Two Clusters with the node of witness, one with 2 nodes

  Each host has 2 discs with a Cache and running as FLASH capacity and disk HARD hybrid Type. Field of the fault, I have a witness preferred and secondary each host is divided.

  Here are the best, I got a work around, if I change the host of fd perfered and when updating the domain fault I can during this brief moment write to the data store. That's how I'm migration of VMs for the moment.

  Any suggestions?

  Thank you

  VSAN Checkup shows that everything works well? My guess is that your 2 hosts have problems with communication with the node of witness or vice versa.

  Try to modify the VSAN storage policy to enable ForceProvisioning as a test, if it works, the problem is probably problem of config/route network communicates with the witness.

• All disks in a single host went from vSAN

  Hello

  I recently had a power cut at home. My 3 node cluster came back OK, but I noticed that the vSAN was missing lots of storage.

  After investigation, it seems that all the disks in a single host have been abandoned (all 4 were operating before the incident).

  I tried to reboot the host, but this has not solved the problems I encounter.

  My file server is unable to turn on because of that, I think it was resynchronize components during the power failure happened.

  Because I have data on these discs (my file server), I hesitate to re - install ESXi on the host or do something with the disks

  I am due to upgrade my version of 3 disc format, but that he was reluctant to do this either at the present time because of my data!

  Environment:

  - vCenter Server Appliance 6.0 U2 (build 3634794)

  -ESXi 6.0 Update 2 (build 3620759) on all hosts

  Please can someone advise on the measures I should then carry out?

  See below for information and some screenshots.

  Thank you

  Metadata health check informs me that the disks have failed, but all 4 disks functioned as expected before the power failure:

  

  Research in the "Virtual SAN health status" column, it shows no health information on disks

  

  Comparison to another host:

  

  The host CAN display the disks on it's HBA, see below:

  

  Update:

  Managed to find the size of the memory heap LSOM and the command 'secret' to increase

  For my own sanity and to keep track of what I did, here's what I did.

  You can see where I had already changed their values before the default.

  

  Edit:

  The command VMWare wanted to keep this secret is in their archives here:

  http://vmware1140.rssing.com/Chan-4263175/all_p2889.html

  I do not understand why VMware wants to keep this command of the community? Currently, I am testing now with the two heapsizes to the maximum configuration. My host is starting

  He typed at the origin:

  Dear Simon,

  I tried:

  vsish EI Setup/config/LSOM/intOpts/heapSize 2047

  to increase the heapsize memory LSOM has allocated,

  then did restart, without success on 192.168.240.55,

  He is still unable to establish the Group of disks with memory error...

  And this has changed to:

  Dear Simon,

  I tried the command you gave me in the SR to increase the

  HEAPSIZE memory LSOM allocated, then did restart.

  without success on 192.168.240.55.

  He is still unable to establish the Group of disks with memory error...

• Format disk VSANS for 3.0 is not / / failure realign suite virtual items SAN / / due to the confinement or the absence of file descriptor vmdk, requiring a manual correction.

  Hi all

  After the upgrade of "6.0 Update 2" and try to update the disc format to version 3.0, I received the error message below.

  Impossible to change the route following the virtual items SAN:

  be4db256-0ab4-9801-c523-0cc47a3a34ca, c2bcb056-5d5f-0f02-f096-0cc47a3a3320, c0bcb056-70a6-180c-c583-0cc47a3a3320, e413b256-90b5-dd1a-cce6-0cc47a3a34ca, c2bcb056-64aa-ee1e-0bb3-0cc47a3a3320, c0bcb056-4b47-5529-b59d-0cc47a3a3320, 6644b256-e0f8-3338-737d-0cc47a3a34ca, d411b256-08ea-f83b-9774-0cc47a3a34ca, c0bcb056-a489-9541-efbe-0cc47a3a3320, 3f6abc56-28fd-4a48-4f8a-0cc47a3a34ce, d411b256-784F-a45a-714d-0cc47a3a34ca, c1bcb056-6671-c45c-2254-0cc47a3a3320, 3f6abc56-1061-ab60-e4c8-0cc47a3a34ce, f17bb356-fcdf-3469-502-a-0cc47a3a3320, cfe8b156-606f-ee6a-4356-0cc47a3a34ce, d411b256-4450-3777-e3bf-0cc47a3a34ca, c1bcb056-b24e-cb7a-7b1a-0cc47a3a3320, f17bb356-f008-9581-2468-0cc47a3a3320, 31bdb056-0a02-4882-9094-0cc47a3a34ca, c1bcb056-2a83-a596-ed2c-0cc47a3a3320, f17bb356-08a1-529f-c375-0cc47a3a3320, c1bcb056-4edc-FFAF-bf04-0cc47a3a3320, c1bcb056-c9e2-fec8-1930-0cc47a3a3320, c1bcb056-4e92-e4e4-9b92-0cc47a3a3320-e413b256-dcd0-f6fd-8ae2-0cc47a3a34ca,

  due to the confinement or the absence of file descriptor vmdk, requiring a manual correction.

  Does anyone has an idea to solve this problem?

  The articles and the script are now available to resolve this problem. A more permanent solution is in preparation.

  Details of the issue, including links to the scripts and KBs are here - http://cormachogan.com/2016/03/31/vsan-6-2-upgrade-failed-realign-objects/

  Thank you for your patience.