Posted on

Clear log files Vmware vCenter Server Appliance

vCenter Server Appliance (VCSA) disks

To view the status of vCenter Server Appliance (VCSA) disks

https://[IP_o_FQDN_VCSA]:5480

Check disk space

Connect to vcenter using putty

Use this command to see the available disk space :

df -h

Locate and Remove Old Files

Using rm command via putty or a software like WinSCP you can delete the old files named localhost_access* in these folders :

  • /storage/log/vmware/lookupsvc
  • /storage/log/vmware/eam/web/
  • /storage/log/vmware/sso/tomcat/
  • /storage/log/vmware/vsphere-ui/logs/access/
Posted on

Nakivo : Backup da Vmware su QNAP

Di seguito un promemoria dei passi per eseguire la configurazione di una struttura composta da un server Vmware che contiene una appliance Nakivo e che deve eseguire i backup su un nas QNAP.

Installare l’appliance Nakivo sul server Vmware

Seguire i seguenti passaggi dalla seguente documentazione :

https://helpcenter.nakivo.com/User-Guide/Content/Deployment/Installing-NAKIVO-Backup-and-Replication/Deploying-VMware-Virtual-Appliance.htm

Configurazione QNAP

Nel QNPA creare una cartella dedicata (es. NakivoBck) , senza il cestino di rete (togliere il flag dalle proprietà della cartella).

Installare nel QNAP il Transporter Nakivo

documentazione : https://mecdata.it/2023/08/updating-nakivo-appliance-in-environment-with-qnap-nas/

Configurazione Nakivo

Usare il browser Edge per entrare in Nakivo

Alla voce Nodes configurare il Transporter di destinazione cioè quello inserito nel QNAP

Passare alla sezione Repositories. Creare unn nuovo backup Repository.

Selezionare CIFS Share e compilare

Name : un nome per identificare il repository sul transporter (qnap)

Assigned Trasporter : selezionare il trasporter inserito precedentemnete

Path to the share : \\ip del nas\cartella

username : del nas

password : del nas

 

Posted on

“Failed bios lock” when installing HPE Reseller Option Kit (ROK) 2019 – 2022 Server

Installing the HPE Re-seller Option Kit (ROK) Windows 2019 or 2022 Standard and Datacenter server software onto VMware virtual machine you should received “Failed BIOS Lock” error which means the HPE branded OS software needs HPE hardware to run.

To solve it, shout down virtual machine and :

  • Enter the Edit Settings of the VM
  • VM Options, Advanced, Edit Configuration, Add Configuration Params then type:
  • Name field: smbios.addHostVendor
  • Value field: TRUE

Posted on

vmware workstation – unable to connect guest to my PCIe LPT port

Scenario

You are are using vmware workstation and you have mount on your computer a PCIe LPT card. You are unable to connect this LPT port to your guest vm.

Solution

Uninstall VM-Ware and to Reinstallit


Note

Posted on

VMWARE – UNABLE TO REMOUNTING NFS datastore from the ESXi

You cannot see nfs datastore on esxi. Try to do the munting, but the procedure fails saying that the datastore already exists.

To resolve this issue, remove and re-add the datastore via the command line

  1. To list the mounted datastores on the host:
    esxcli storage nfs list
  2. Make a note of the NFS datastore from step 1. Run this command to delete the NFS mount:esxcli storage nfs remove -v NFS_Datastore_Name

 


Run this command to mount the NFS datastore:

esxcli storage nfs add -H NFS_IP|NFS_HOSTNAME -s Share_mount_point_on_the_NFS -v DatastoreName

Documentation

Posted on

vmware – lost connection to nfs datastore

In your vmware environment you have created a nfs datastore but when you are trying to copy files to it, you lost the connection.

Symptoms

You can check the file vmkernel.log that you can find in your esx host in :

/var/log

You should find these lines of error :

Lost connection to the server xxx.xxx.xxx.xxx mount point /yourdatastorefolder mounted as ........... ("yourdatastorename")

Restored connection to the server xxx.xxx.xxx.xxx mount point /yourdatastorefolder mounted as ........... ("yourdatastorename")

or

vmnic3: 4026 bytes packet couldn't be sent (mtu=1500)

or

vmnic3: oversized tsoMss: 8948, mtu=1500

Solution

As explained in vmware documentation you have to check communication with your nfs datastore. So using , for example Putty over ssh, you can :

Ping your nfs datastore

vmkping xxx.xxx.xxx.xxx

Find your vmkernel network card :

esxcfg-vmknic -l

In the output you can see the MTU value of your network card and which is the vmkernel network card. Now you can ping your datastore using the network card, trying different MTU values :

vmkping -I vmk1 -s 1420 xxx.xxx.xxx.xxx

You probably need to change the MTU of your esx host’s network card. Maybe you have an MTU set to 9000 and you need to set it to 1500.

Using the vsphere client : Configuration – Networking. Select vmkernel network card and select “Properties” . Select “Vmkernel” and click on “Edit” :

Change MTU:

You will be able to see the new MTU value using the previou command :

esxcfg-vmknic -l