GaelV's Posts

Hi community ! Here's my issue , i didn't find a working solution on vmware and windows threads.. Template creation : I made a base Windows 2012 R2 Standard VM to create a template. This ... See more...
Hi community ! Here's my issue , i didn't find a working solution on vmware and windows threads.. Template creation : I made a base Windows 2012 R2 Standard VM to create a template. This VM has been added in our domain and then, it's auto activated with KMS. Next to that, I removed the IP configuration and shutdown the VM then create the template. (By the way, i use vCenter 6.0 and ESXis are 5.5 U3) VM from template deployment : I deployed a VM from the previous template by using a Customization Specification, this one simply do the following things : - use the VM's name as computer's name - ask NIC1's IP address - auto-join to the domain with admin username/password - Generate a new SID My problem is :Windows is not activated even if i tried to quit and join the domain again, i also tried to manually activate and reset activation with slmgr but it failed with the 0x8007232B error. Finally, I manually launched a Sysprep OOBE Generalized , do the previous steps again but it still fails. Do some of you have any idea for my case ? Best regards,
I tried these 3 versions : The only one who currently be loaded is the last one (no-custom)... the 2 on top cause the server reboot while loading. I've checked the md5sum for the 3 iso... See more...
I tried these 3 versions : The only one who currently be loaded is the last one (no-custom)... the 2 on top cause the server reboot while loading. I've checked the md5sum for the 3 iso and it's ok so it doesn't seems to be a file issue.
Yes i've tried a 6.0 version and it works (loading is ok, no reboot) but the infrastructure has to be in 5.5 U3b for now, 6.0 is planned for next or two years It's really weird cause I used th... See more...
Yes i've tried a 6.0 version and it works (loading is ok, no reboot) but the infrastructure has to be in 5.5 U3b for now, 6.0 is planned for next or two years It's really weird cause I used the 5.5 U3b on 8x DL360G9 , no problem occurs but since september it happened..
Hello , I'm having an unknown issue while performing an upgrade of ESXi 5.5 U3 on a HP DL360 G9 There is an ESXi 5.1 U3 already installed and i'm trying to upgrade it to 5.5 U3. The HP DL... See more...
Hello , I'm having an unknown issue while performing an upgrade of ESXi 5.5 U3 on a HP DL360 G9 There is an ESXi 5.1 U3 already installed and i'm trying to upgrade it to 5.5 U3. The HP DL360 G9 has been patched with Service Pack ProLiant of April 2017 and also July 2017 to compare if there was any difference while loading ESXi installer. The Loading ESXi Installer screen loads until the end then the server restart by itself without any error code : I tried with other ESXi ISO (5.5 U3 october, and december 2016...) , also BIOS default resetting but the problem still occurs. Do some of you have any advices ? Best regards, Gael
Hi, So i've checked many parameters and stats from the storage array side, it is well configured so my problem is really on ESXi configuration. I followed your advices to find the drivers's... See more...
Hi, So i've checked many parameters and stats from the storage array side, it is well configured so my problem is really on ESXi configuration. I followed your advices to find the drivers's version and to compare to some of our others servers, the firmware was different. The current version was qlnativefc 8.01.02 , on the other servers we have qlnativefc 8.02.00 It should be an interesting point of reflection, i'll update the driver to 8.02.00 then i'll see if this was the main issue or not.
Hi dekoshal, Thank for your great detailed answer, sorry for the delay. I'm checking the "No of outstanding IOs with competing worlds:" parameter, they're all set to 32 (for each device so)... See more...
Hi dekoshal, Thank for your great detailed answer, sorry for the delay. I'm checking the "No of outstanding IOs with competing worlds:" parameter, they're all set to 32 (for each device so) I'm currently reading the scalable storage performance doc then I let you know what i found for my issue. By the way, about the sense code decoder, I have found 2 interesting explanations : Host Status [0x3] TIME_OUT This status is returned when the command in-flight to the array times out. Host Status [0x8] RESET This status is returned when the HBA driver has aborted the I/O. It can also occur if the HBA does a reset of the target. So i think we can confirm there's a relation with latency as we saw in the log.
Thanks for explanation, by default we use 32 and 4 as default values as HP3PAR prescribe. I'm gonna check the log out , but i don't think I've ever seen some lines like that. Edit : I didn'... See more...
Thanks for explanation, by default we use 32 and 4 as default values as HP3PAR prescribe. I'm gonna check the log out , but i don't think I've ever seen some lines like that. Edit : I didn't found the required log, the nearest look like below : 2017-06-23T01:52:30.236Z cpu9:34176)Fil3: 15438: Max retries (10) exceeded for caller Fil3_FileIO (status 'IO was aborted by VMFS via a virt-reset on the device') 2017-06-23T01:52:30.236Z cpu9:34176)BC: 2288: Failed to write (uncached) object '.iormstats.sf': Maximum kernel-level retries exceeded BR Gael
Hi dekoshal, Thank you for your quick answer. I've checked the VMFS datastore which is referred to < Detected a non vi workload on datastore xxx > I saw the flow chart on a VMWare KB, bu... See more...
Hi dekoshal, Thank you for your quick answer. I've checked the VMFS datastore which is referred to < Detected a non vi workload on datastore xxx > I saw the flow chart on a VMWare KB, but the point is we use Adaptative Queuing (QFullSampleSize and Disk.QFullThreshold parameters for each datastore) instead of SIOC, all of our esxi work in that way without have any issue. These parameters are set in line with the HP3PAR values. For me, there's a difference between SIOC and Adaptative Queuing don't you think ? Regards,
Hello, I'm currently working on 6 ESXi 5.5 U3 build 4722766 (on HP DL360 G9 Servers). All of them are linked with fiber through a switch fiber to a HP 3PAR Disk bay where all volumes are stor... See more...
Hello, I'm currently working on 6 ESXi 5.5 U3 build 4722766 (on HP DL360 G9 Servers). All of them are linked with fiber through a switch fiber to a HP 3PAR Disk bay where all volumes are stored. Last night one ESXi has been blocked itself, its log files repeted these lines since last night : 2017-06-22T20:39:05.656Z: <DATASTOREXXXX, 0> Write error to fd 9 2017-06-22T20:40:11.217Z: <DATASTOREXXXX, 0> I/Os from datastore naa.60002ac0000000000000016f00009893 took 60.849006(>= 30.000000) seconds to complete stats computation. Reducing its polling frequency. 2017-06-22T20:41:37.453Z: WARNING: Write 0xff98b66f[512] -> 18 failed. Resource temporarily unavailable 2017-06-22T20:41:37.453Z: <DATASTOREXXXX, 0> Write error to fd 18 2017-06-22T20:41:37.453Z: <DATASTOREXXXX, 0> I/Os from datastore naa.50002ac1a0009893 took 86.234590(>= 30.000000) seconds to complete stats computation. Reducing its polling frequency. 2017-06-22T20:41:37.454Z: WARNING: Write 0xff98b66f[512] -> 9 failed. Resource temporarily unavailable 2017-06-22T20:41:37.454Z: <DATASTOREXXXX, 0> Write error to fd 9 2017-06-22T20:41:37.454Z: WARNING: Write 0xff98b66f[512] -> 5 failed. Resource temporarily unavailable 2017-06-22T20:41:37.454Z: <DATASTOREXXXX5, 0> Write error to fd 5 Because of this issue, VM have been instable and we had to migrate them to another host and they work good now. I've checked volumes on my HP3PAR bay, there's no alert, no alarm, everything looks good and there is the same thing for the switch fiber. By the way, i also have a SIOC alarm whereas it's not activated on the datastore : Do someone has an idea or troubleshooting advice ? I mean the configuration hasn't been changed and it's really weird that this ESXi works wrong instead of other (which have common storage configuration and the same ESXi version work great) Thank you for reading Gael
Hi, I'm working on 2 ESXi 5.5 U3 which have the same datastore attached. Some VM are on the first and some on the second. Sometimes i need to migrate from one to another. For my configurati... See more...
Hi, I'm working on 2 ESXi 5.5 U3 which have the same datastore attached. Some VM are on the first and some on the second. Sometimes i need to migrate from one to another. For my configuration (to decide if i have to use VMW_PSP_MRU or RR following devices), i need to know which devices are RDM and which are not. I've used a great script to detect which device is RDM but this script is based on VMs and not Host. My question is : is there any way to "scan" all datastore attached to a host ? or scanning all files to detect RDM without VM presence ?) (the fabulous  script is here : VMprosVMware: List all RDM disks in Hosts and Virtual Machines via PowerCLI - VMpros  ) Best regards, Gael
UP ! Anybody have an idea ?
Hi everybody ! I work on a HP ProLiant DL360 G7 which host an ESXi 5.5.0 build-4345813- Update 3, which is managed by a vCenter Server 6.0. I was doing my acceptance tests and i got an aler... See more...
Hi everybody ! I work on a HP ProLiant DL360 G7 which host an ESXi 5.5.0 build-4345813- Update 3, which is managed by a vCenter Server 6.0. I was doing my acceptance tests and i got an alert issue : I'd like to have an alert on my vCenter and also by email as i did for storage link for example, so I use the default vCenter alarm (Host hardware power status). I was trying to threw a power alert/alarm by unplugging one of the two power cords. Well, i wait 10-20min at least and there's no alert from vCenter and no mail instead of i got a warning on the ilo web interface. Then i've tried to update and reset sensors ("in my screen : Mise à jour and Réinitialiser capteurs) and only this throw alarm and mail : Then, i plugged my cord in the PSU and the state never came back to Normal unless i make an update and reset sensors... I saw my issue seems known by the HP/VMware communities as i can see on google, but i still not have found a solution. Do you have any idea about my issue ? Thanks for reading/answering ! Gael
For those which will have that kind of problem, i found out how to resolve it besides previous answers of this topic : - list/count all the naa. - think to change Perenially true if they are ... See more...
For those which will have that kind of problem, i found out how to resolve it besides previous answers of this topic : - list/count all the naa. - think to change Perenially true if they are RDM - put Queue Full Threshold and Queue Full Sample Size to the constructor value (4 and 32 following HP 3PAR Best Practices) - check out what are their Path Selection Policy (in my case it was VMW_PSP_MRU but it wasn't the right one) - add and set Custom SATP ALUA rule as a default PSP for vmw satp alua - reboot - check out again the Path Selection Policy. In my case this works great, i need to try it on my others ESXi then i'll update it if needed.
Hi Ralf, Before you answer me, i tried a new installation without any configuration, just to check in the first boot if there's issues or not => I still have issues, the ESXi takes a very long... See more...
Hi Ralf, Before you answer me, i tried a new installation without any configuration, just to check in the first boot if there's issues or not => I still have issues, the ESXi takes a very long time to boot as I had in my first post. I was thinking about the array itself or the physical FC controller or probably bad configuration somewhere. About the LUN0, i haven't heard about it in HP Best Practices document but i'm gonna check it out. About long delays, i didn't have any VM or Microsoft Cluster on this ESXi right now.
I've already checked these site, but i can't find informations about the Thin Provisioning mode to change that bit. I'm gonna check it out and let you know what happened.
For the first command # esxcli storage nmp device list |grep "Path Selection Policy:" |sort |uniq -c       1    Path Selection Policy: VMW_PSP_FIXED      73    Path Selection Policy: VMW_P... See more...
For the first command # esxcli storage nmp device list |grep "Path Selection Policy:" |sort |uniq -c       1    Path Selection Policy: VMW_PSP_FIXED      73    Path Selection Policy: VMW_PSP_RR So i'll do again the rule as you wrote, and applied it again, i also have :   1    Path Selection Policy: VMW_PSP_FIXED      73    Path Selection Policy: VMW_PSP_RR which it seems ok, we're right ? But i get the same kind of error at booting : (i took a screenshot cause i can't paste you the log cause i can't have access until the esxi boot completely, which takes me around 30min...and more ! )
I have 2 HP 3PAR 7200
Hi, I did it but nothing has change, check it out i.e: naa.60002ac00000000000000100000098a4    Device Display Name: 3PARdata Fibre Channel Disk (naa.60002ac00000000000000100000098a4) ... See more...
Hi, I did it but nothing has change, check it out i.e: naa.60002ac00000000000000100000098a4    Device Display Name: 3PARdata Fibre Channel Disk (naa.60002ac00000000000000100000098a4)    Storage Array Type: VMW_SATP_ALUA    Storage Array Type Device Config: {implicit_support=on;explicit_support=off; explicit_allow=on;alua_followover=on; action_OnRetryErrors=off; {TPG_id=256,TPG_state=AO}}    Path Selection Policy: VMW_PSP_RR    Path Selection Policy Device Config: {policy=rr,iops=1,bytes=10485760,useANO=0; lastPathIndex=1: NumIOsPending=0,numBytesPending=0}    Path Selection Policy Device Custom Config:    Working Paths: vmhba1:C0:T2:L7, vmhba1:C0:T0:L7    Is Local SAS Device: false    Is USB: false    Is Boot USB Device: false Path Selection Policy is alright, but there's the same previous errors. (By the way, we use to keep in mind that i'll set up later ,Queue Full Sample Size and Threshold values to 32 and 4 as HP best pratices said...)
Hi fellows ! I had an issue next to ESXi update (HP Custom ESXi 5.5.0 U3 Build 3568722) on a HP ProLiant DL360 G7, freshly updated with the last Service Pack SPP , it works pretty well except ... See more...
Hi fellows ! I had an issue next to ESXi update (HP Custom ESXi 5.5.0 U3 Build 3568722) on a HP ProLiant DL360 G7, freshly updated with the last Service Pack SPP , it works pretty well except the boot time, he takes around 30min to boot because it's stuck to that kind of log for each device (+multipathing), like he scan all 2016-11-30T06:51:17.793Z cpu4:33206)ScsiDeviceIO: 7499: Get VPD 86 Inquiry for device "naa.50002ac0de009893" from Plugin "NMP" failed. Not supported 2016-11-30T06:51:17.796Z cpu4:33206)ScsiDeviceIO: 6202: Could not detect setting of QErr for device naa.50002ac0de009893. Error SCSI reservation conflict. 2016-11-30T06:51:17.796Z cpu4:33206)ScsiDeviceIO: 6716: Could not detect setting of sitpua for device naa.50002ac0de009893. Error SCSI reservation conflict. 2016-11-30T06:51:17.798Z cpu4:33206)ScsiDevice: 3445: Successfully registered device "naa.50002ac0de009893" from plugin "NMP" of type 0 2016-11-30T06:51:17.798Z cpu4:33206)ScsiEvents: 301: EventSubsystem: Device Events, Event Mask: 180, Parameter: 0x41098399cf30, Registered! 2016-11-30T06:51:17.802Z cpu4:33206)StorageApdHandler: 698: APD Handle  Created with lock[StorageApd0x4108a6] 2016-11-30T06:51:17.802Z cpu4:33206)ScsiEvents: 501: Event Subsystem: Device Events, Created! 2016-11-30T06:51:17.803Z cpu4:33206)VMWARE SCSI Id: Id for vmhba2:C0:T0:L27 0x50 0x00 0x2a 0xc0 0xdc 0x00 0x98 0x93 0x56 0x56 0x20 0x20 0x20 0x20 2016-11-30T06:51:17.805Z cpu4:33206)VMWARE SCSI Id: Id for vmhba1:C0:T1:L27 I know some people had this problem in the past, there is no really solutions that have been brought but i also observed a strange things , in esx.conf, some devices are discovered with VMW_PSP_RR (thanks to a user custom rule) which is ok and that's what i want, but the most use VMW_PSP_MRU : /storage/plugin/NMP/device[naa.60002ac0000000000000000d000098a4]/psp = "VMW_PSP_RR" /storage/plugin/NMP/device[naa.50002ac0620098a4]/psp = "VMW_PSP_MRU" /storage/plugin/NMP/device[naa.50002ac145009893]/psp = "VMW_PSP_MRU" /storage/plugin/NMP/device[naa.50002ac145009893]/preferred = "fc.20000000c9691329:10000000c9691329-fc.2ff70002ac009893:20120002ac009893-naa.50002ac145009893" /storage/plugin/NMP/device[naa.50002ac0e7009893]/psp = "VMW_PSP_MRU" What can i do to exclude the VMW_PSP_MRU options from all my devices ? and/or How can i handle the Plugin "NMP" failed ? Do someone have an advice ? Regards, Gael
Thank you both of you, i didn't use the use but it seems interesting for me for automatic reservation, really thank you. Finally i found the solution, as i have an HP3PAR Storage, i looked int... See more...
Thank you both of you, i didn't use the use but it seems interesting for me for automatic reservation, really thank you. Finally i found the solution, as i have an HP3PAR Storage, i looked into the documentation and found that i need to set these values : queue-full-threshold 4 --queue-full-sample-size 32 for each devices (naa.xxxxxxx) (the command is : esxcli storage core device set --device devicename --queue-full-threshold 4 --queue-full-sample-size 32;" I did it after using the HP Custom iso and it works normally, even faster than usual. So it's ok now, thank you again for helping