Nel mio home lab ho installato la mia prima versione di vCenter 7.0
https://kb.vmware.com/s/article/2001041
#Mi collego all’Host ESXi dove devo copiare la ISO
Connect-ViServer <hostname>
#Visualizzo l’elenco dei datastore
Get-Datastore
#Seleziono il datastore che mi interessa
$datastore = Get-Datastore “<nome del datastore>”
#Eseguo il mount del PSDrive sotto ds:
New-PSDrive -Location $datastore -Name ds -PSProvider VimDatastore -Root “”
#Lancio la copia
Copy-DatastoreItem -Item c:……Windows2016.iso -Destinatiom ds:ISO
Stamattina abbiamo trovato un host ESXi 6.7u1 in questo stato, da KB 58874 dobbiamo procedere con l’aggiornamento alla 6.7u2 oppure abbiamo come possibile soluzione temporanea applicare il seguente comando su tutte schede di rete:
esxcli network nic queue loadbalancer set –rsslb=false -n vmnicX
Nella versione ESXi 6.7, tra tutti i cambiamenti, è presente un modifica al parametro action_OnRetryErrors.
La modifica del parametro action_OnRetryErrors ha effetto su come viene gestita la Test Unit Ready (TUR), processo di controllo se un PATH verso una LUN di uno storage array è attivo o no.
Fino alla versione 6.0/6.5 questo parametro era impostato a OFF, quindi nel caso di perdita di un PATH l’host ESXi continuava a eseguire un polling sul path fino al ripristino.
Nella nuova versione 6.7 questo paramentro è messo a ON e quindi al primo errore il path viene messe “DEAD” e non vengono successivamente eseguite verifiche sullo stato del PATH,
In caso di storage SAS con connessione a HOST ESXi con due path (Attivo/passivo) la situazione creata nella versione 6.7 può risultare critica, perchè:
Per risolvere il problema si può procedere con le indicazioni di questa KB di VMware:
ESXi 6.7 hosts with active/passive or ALUA based storage devices may see premature APD events during storage controller fail-over scenarios (67006)
After upgrade my vsphere infrastructure to 5.5 i have problem of disconnect network after reboot:
https://communities.vmware.com/thread/498472
Now i have change on my vm windows the network adapter type from e1000 to vmxnet3
I have used this step :
– Save IP Address configuration
– Shutdown VM
– Copy Mac Address
– Remove E1000 network adapter
– Add vmxnet3 network adapter and set manual mac address
– Boot VM
– For windows 2008 and older set devmgr_show_nonpresent_devices=1
– Remove, if present, the old network adapter
– Configure ip address…
For clone disk and clone vm without vcenter :
cd /vmfs/volumes/Datastore01Raid10
/vmfs/volumes/537dfea4-903a2d25-a8c3-00237da1046c # ls
SRVAPP01 SRVDC02 win2008R2ent
/vmfs/volumes/537dfea4-903a2d25-a8c3-00237da1046c # mkdir template2008
vmfs/volumes/537dfea4-903a2d25-a8c3-00237da1046c # vmkfstools -i SRVDC02/SRVDC02.vmdk template2008/template2008.vmdk
Destination disk format: VMFS zeroedthick
Cloning disk ‘SRVDC02/SRVDC02.vmdk’…
Clone: 100% done.
/vmfs/volumes/537dfea4-903a2d25-a8c3-00237da1046c #
And select custom configuration for add existing disk 
and after select other option for the disk “Use an existing virtual disk”
and select the vmdk create .
xseries 2350 M4 + vmware esxi 5.1
Donwload megacli software from ibm site
How to install?
You need have active ssh connection to the esxi server
Install to esxi server :
esxcli software vib install /tmp/vmware-esx-MegaCli-8.04.07.vib –no-sig-check
(The installation probably need put the host in manintenece mode and reboot server)
How to use?
Go to /opt/lsi/MegaCli/ and run ./MegaCli with option :
Check the status all of HD:
./MegaCli -PDList -aALL
or single HD
./MegaCli -PDInfo -PhysDrv [E:S] -aALL (E is the enclosure and is the slot)
Download the log of controller:
./MegaCli -AdpEventLog -GetEvents -f events.log -aALL && cat event.log
Show info configuration:
./MegaCli -AdpAllInfo -aALL
Show controller configuration:
./MegaCli -CfgDsply -aALL
Battery status:
./MegaCli -AdpBbuCmd -aALL
Show rebuild status:
./MegaCli -PDRbld -ShowProg -PhysDrv [E:S] -aALL
And more info:
./MegaCli -h
If an ESXi 5.1 host does not successfully install, serial line logging can be configured when booting the installer using advanced kernel boot-time parameters. This takes effect for the current boot, and does not persist across future reboots.
To enable serial-line logging during installation:
> runweasel debugLogToSerial=1 logPort=com1
It is possible only whit virtual hardware 8.
Remove from inventory mymachine
Edit mymachine.vmx file and add this:
sound.present = “TRUE”
sound.allowGuestConnectionControl = “false”
sound.virtualDev = “hdaudio”
sound.filename = “-1”
sound.autodetect = “TRUE”
sound.pciSlotNumber = “34”
Save file and reinvetory virtualmachine.
Now:
~ # esxcfg-scsidevs -a
vmhba38 ahci link-n/a sata.vmhba38 (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
vmhba39 ahci link-n/a sata.vmhba39 (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
vmhba0 ahci link-n/a sata.vmhba0 (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
vmhba1 qla2xxx link-n/a fc.20000024ff0aa474:21000024ff0aa474 (0:17:0.0) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA
vmhba2 megaraid_sas link-n/a unknown.vmhba2 (0:22:0.0) LSI / Symbios Logic MegaRAID SAS Fusion Controller
vmhba3 qla2xxx link-n/a fc.20000024ff0aa479:21000024ff0aa479 (0:32:0.0) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA
vmhba40 ahci link-n/a sata.vmhba40 (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
vmhba32 bnx2i unbound iscsi.vmhba32 Broadcom iSCSI Adapter
vmhba33 bnx2i unbound iscsi.vmhba33 Broadcom iSCSI Adapter
vmhba34 bnx2i unbound iscsi.vmhba34 Broadcom iSCSI Adapter
vmhba35 bnx2i unbound iscsi.vmhba35 Broadcom iSCSI Adapter
vmhba36 ahci link-n/a sata.vmhba36 (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
vmhba37 ahci link-n/a sata.vmhba37 (0:0:31.2) Intel Corporation Patsburg 6 Port SATA AHCI Controller
~ # vmkload_mod -s qla2xxx | grep Version
Version: Version 902.k1.1-9vmw, Build: 799733, Interface: 9.2 Built on: Aug 1 2012
~ #