GaelV's Posts

Perfect thanks, i'll come back to you asap
I've tried but it's empty.. tried to rename in .txt and .zip but same issue
Could you just make a .txt or a .zip ? because the .txt.zip failed my 7zip extractor ...
Thanks, let see if there's any VIB conflicts Could you make a file with the current output of these 2 commands : esxcli software vib get esxcli software vib list I'd like to check if the... See more...
Thanks, let see if there's any VIB conflicts Could you make a file with the current output of these 2 commands : esxcli software vib get esxcli software vib list I'd like to check if there's any conflict between VIBs
Huum weird... Could you post a screenshot of your issue when you say ? I have the Dell Opoenmanage VIB installed and can see everything Hardware related perfectly fine in openmanage but in ESX... See more...
Huum weird... Could you post a screenshot of your issue when you say ? I have the Dell Opoenmanage VIB installed and can see everything Hardware related perfectly fine in openmanage but in ESXI I have tonnes of "intel chipset C620" items with "Cannot report on the current status of this physical element" next to it.
It was my mistake, sorry. Right, what happen if you reset then update sensors in ESXi menu ? Or in local CLI : services.sh restart localcli hardware ipmi sel clear
The v9.3 from yesterday ? (last release on dell site is august 06th)
Thanks, Have you updated your hardware with the latest Dell EMC OpenManage Server Driver Pack ? (the last release is v9.3.0) Take a loot at Support pour PowerEdge T440 | Pilotes et téléchar... See more...
Thanks, Have you updated your hardware with the latest Dell EMC OpenManage Server Driver Pack ? (the last release is v9.3.0) Take a loot at Support pour PowerEdge T440 | Pilotes et téléchargements | Dell France to download it, and you should compare if all of your drivers/firmwares (even for raid controller) are in the same version or older.
Hi ReazBaksh​ I've just quickly check if your Startech pex1394b3 is compatible with ESXi using this link VMware Compatibility Guide - I/O Device Search and i think it's not compliant unfortun... See more...
Hi ReazBaksh​ I've just quickly check if your Startech pex1394b3 is compatible with ESXi using this link VMware Compatibility Guide - I/O Device Search and i think it's not compliant unfortunately. It seems FireWire is not supported at all..
Hi garethrobson​ Could you provide me the CPU and RAID controller you're using ? Thanks !
Hello, I had the same issues on earlier ESXi versions, do your volumes get the following tuning as advised by HPE ? : queue-full-threshold 4 queue-full-sample-size 32 (Sometimes there's t... See more...
Hello, I had the same issues on earlier ESXi versions, do your volumes get the following tuning as advised by HPE ? : queue-full-threshold 4 queue-full-sample-size 32 (Sometimes there's this one in addition "queue-depth 128" but it's not advised to change it if not needed...) You can check it with the following command : esxcli storage core device list It will give you the list of all your volumes with associated parameters, then you can take a look at the QueueFull Sample Size, Queue Full Threshold and Device Max Queue Depth if needed. If the value is different from those advised by HPE, here's the command to set the value for one volume (test with only one or two volumes first, then if it works, apply it to all) : esxcli storage core device set --device device_name --queue-full-threshold 4 --queue-full-sample-size 32 Finally, have you tried to modify the PSP Options of your current rule to "1" ? The defaults settings is 1000, which means the device switch the next path after 1000 I/Os, HPE/3PAR advise to set it to 1. esxcli storage nmp satp rule add -s “VMW_SATP_ALUA” -P “VMW_PSP_RR” -O “iops=1” -c “tpgs_on” -V “3PARdata” -M “VV” -e “HP 3PAR Custom Rule” Let me know if it improves the situation Source (page 37/172 of Hpe 3PAR StoreServ VMware ESX/ESXi Implementation Guide.pdf) : https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=2ahUKEwjAzd_xnvDjAhVr5eAKHdRxBQ8QFjABegQIAhAC&url=ht…
Be careful with the hardware compatibility, maybe your hardware is supported for 6.5 but not for 6.7 Check it with : VMware Compatibility Guide - System Search To answer to your needs i would... See more...
Be careful with the hardware compatibility, maybe your hardware is supported for 6.5 but not for 6.7 Check it with : VMware Compatibility Guide - System Search To answer to your needs i would do the following things : 1) Backup your ESXi configuration using vSphere CLI : vicfg-cfgbackup --server=ESXi_host_IP_address --username=root -s output_file_name Using PowerCLI (remote) : Get-VMHostFirmware -VMHost ESXi_host_IP_address -BackupConfiguration -DestinationPath output_directory 2) If you run ESXi on server, i'd use the Custom Image from manufacturer Here's for Dell 6.7U2 : VMware ESXi 6.7 U2 | Détails sur le pilote | Dell France Here's for HPE 6.7U2 check out this link : http://vibsdepot.hpe.com/mapping/SPP-HPE_Custom-Image-vibsdepot-mapping-Gen9-later.pdf Else, just get the current ESXi 6.7 from VMWare Téléchargez VMware vSphere 3) Stop all your VMs before doing anything (and if you can, do a backup if you're not confident ) 4) Copy the .zip freshly downloaded with WinSCP to your ESXi in /update/ for example (you can create a new folder called update) 5) Connect to the ESXi with CLI (locally) or PowerCLI (remotely) and use the following command to update (like offline update) : Example : " esxcli software vib update -d /update/Your_ZIP.zip" Then reboot 6) Once the ESXi is rebooted, check the version with the command : "vmware -v" , it will give you the running version and build. 7) Boot your VM as usual --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.
Hi Still the same error as i had about nicsettings adapter... New-VM : 06/08/2019 10:44:29    New-VM          Server task failed: A specified parameter was not correct: nicsettings:adapter... See more...
Hi Still the same error as i had about nicsettings adapter... New-VM : 06/08/2019 10:44:29    New-VM          Server task failed: A specified parameter was not correct: nicsettings:adapter:ip Au caractère Ligne:1 : 1 + New-VM -Name 'WEB001' -VMHost $VMHost -Datastore 'DST_SYS' ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : NotSpecified: (:) [New-VM], VimException     + FullyQualifiedErrorId : Security_Impl_TaskResultConverter_TaskNotSucceeded,VMware.VimAutomation.ViCore.Cmdlets.Commands.NewVM weird isn't it ? i only have 1 nic adapter on my template. Maybe i have to specify it ? I give a try with the "Position 1" parameter, i think it will works !
I've tried the one with "UseStaticIP" parameter because it could help me in the future for using .csv doc. But i still got an error with my cli (i didn't paste the $VMHost, $Template and $Spec... See more...
I've tried the one with "UseStaticIP" parameter because it could help me in the future for using .csv doc. But i still got an error with my cli (i didn't paste the $VMHost, $Template and $Spec but they're ok) PS C:\> New-VM -Name 'WEB001' -VMHost $VMHost -Datastore 'DST_XXX' -Template $Template -OSCustomizationSpec $Spec | Set-OSCustomizationNicMapping -IPmode UseStaticIP -IpAddress "192.168.0.1" -SubnetMask "255.255.255.0" -DefaultGateway "192.168.0.1" -Dns "X.X.X.X.X","X.X.X.X.X" New-VM : 31/07/2019 11:30:12 New-VM          Server task failed: A specified parameter was not correct: nicsettings:adapter:ip Au caractère Ligne:1 : 1 + New-VM -Name 'WEB001' -VMHost $VMHost -Datastore 'DST_XXX ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : NotSpecified: (:) [New-VM], VimException     + FullyQualifiedErrorId : Security_Impl_TaskResultConverter_TaskNotSucceeded,VMware.VimAutomation.ViCore.Cmdlets.Commands.NewVM I tried with simple quote and double quote, nothing changes, i've also tried with only one DNS... but still the same error.
Hi, Weird, i did it with Interactive Mode, something there's differences with Automatic mode. I've just find out the mail that vmware support send me to completely resolve the issue, it wor... See more...
Hi, Weird, i did it with Interactive Mode, something there's differences with Automatic mode. I've just find out the mail that vmware support send me to completely resolve the issue, it works for me but i don't know if it could works for everyone, so i won't be responsible if the following cli affects your server, software or anything. As a reminder, i had the issue with HP ML350 Gen10 with ESXi 6.5 Update 2. The support told me : 1) Update the server with the SPP [done] 2) Update the ESXi to Update 3 3) Finally, put this cli in ssh : "localcli hardware ipmi sdr list  |grep "Cooling Unit 1 Fans " &&  esxcfg-advcfg -s 49 /UserVars/HardwareHealthIgnoredSensors" 4) Reboot 5) Everything's work fine. I repeat, it works for me because the vmware support told me to do this, maybe if the warning is about different devices, it won't work for you. Let me know
Thanks for answering, If i follow your example, the GUI specify to "prompt the user for ip address", i have the same behaviour in mine, but when you try to deploy a new vm with the same specif... See more...
Thanks for answering, If i follow your example, the GUI specify to "prompt the user for ip address", i have the same behaviour in mine, but when you try to deploy a new vm with the same specification by using PowerCLI, it didn't prompt the ip address and i think we have to specify each parameters manually isn't it ? So if i use "Set-OSCustomizationNicMapping" to my deploy command line, i'm afraid it will duplicate some settings I've already set using the GUI (dns server, ip to be prompted , netmask etc...)
Hi, I've just read the script and it seems to don't use any OSCustomization template, it make the deal but it's kind of wordy (write each time cpu, ram etc... whereas i already package it on a... See more...
Hi, I've just read the script and it seems to don't use any OSCustomization template, it make the deal but it's kind of wordy (write each time cpu, ram etc... whereas i already package it on a vcenter customization template) I think there's something to do with OSCustomizationNicMapping function but i can't manage it ...
Hi ClemFandango​ Is it safe for me to run the upgrade from VMWare image for 6.7 update 2 to the Dell custom image for 6.7 update 2 ? First of all , do a backup of your ESXi configuration. ... See more...
Hi ClemFandango​ Is it safe for me to run the upgrade from VMWare image for 6.7 update 2 to the Dell custom image for 6.7 update 2 ? First of all , do a backup of your ESXi configuration. To answer to your question, i would say yes, the differences between VMWare and Manufacturer custom image is about drivers. I lived the same issues with HPE servers and i didn't have any problems while update from vmware image to HPE Custom. After the upgrade just do an Update Manager Scan from your vCenter to check if inadvertently some drivers, patches, or extensions miss to your ESXi to be fully compliant. Let me know how it runs
Hi @pondhop Before reinstalling be aware that some ESXi version can't be installed on some old servers (you should check the hardware compatibility matrix VMware Compatibility Guide - System ... See more...
Hi @pondhop Before reinstalling be aware that some ESXi version can't be installed on some old servers (you should check the hardware compatibility matrix VMware Compatibility Guide - System Search  ) and check if your vcenter can list and add ESXi from different version (i.e. maybe a vCenter 6.7 can't list an ESXi 3.5... i don't know) In general the update include more than just a patch, they contains many patches, drivers, extension... The patch for Spectre/Meltdwon for  ESXi 6.7 is known as "ESX670-201808401-BG" and seems to be embedded on the full update. VMware Knowledge Base If you can, i advise you to update your servers to the ESXi 6.7 Update 2,, here's the release note for informations : VMware ESXi 6.7 Update 2 Release Notes
Hi, jtihng​ First , you should check if you've selected the right network adapters , use the right vlan if needed , and if you use an IP address accessible through your network. Then try to pin... See more...
Hi, jtihng​ First , you should check if you've selected the right network adapters , use the right vlan if needed , and if you use an IP address accessible through your network. Then try to ping the hostname/address, if you can so it means you should access to the ESXi web console or ssh. If it ping but you still can't access the webconsole or connect to SSH, go in your ESXi (using Local console) , then F2 > Troubleshooting Options and Enable ESXi Shell AND Enable SSH. Let me know if it helps or not.