Lalegre's Posts

Hello @Nani321 Namespaces are managed by WCP service which is needed for Tanzu operations. Even if you are not using it, the service needs to be started. Could you please run:service-control --status wcp If it is down, start it: service-control --start wcp Also here is a Dell KB which could be another solution to the issue, related with the same: https://www.dell.com/support/kbdoc/es-ar/000192615/esxi-host-fails-to-enter-or-exit-maintenance-mode...

Hello @flube, Snapshot are not a backup solutions, they are meant to redirect writes to preserve a previous state for a short period of time. Having it for a long time could lead to performance degradation or even corruption.

Hello @jucagol, As @Kinnison mentioned, he is correct, you need to create a VMkernel with Provisioning checkbox into it and make sure it is connected to a portgroup where the 10Gbps link is being used.

Hello @maksym007, DCUI is the service that provides the integrated Management Console of ESXi, if you connect over IPMI or using SSH and type 'dcui' that is what I am talking about. Then the vsanmgmtd is the service that provides Health and Performance metrics to vCenter and is always running even if you are not using it.  These are just extra-verbose logs that do not produce any harm and you will be seeing it always, they can be disabled by stopping the vsanmgmtd service and adding the host in lockdown mode which will disable dcui, however, you could lose access to the console if not properly configured. If you ask me, I would not put attention to disabling as it does not cause any harm at all.  

Hello @IMTBG, You could do the following: Shutdown one port from the LACP Remove that port from the LACP Create a VSS and add that port Enable the port back Migrate the Management VMkernel to the VSS Migrate the VMs to the VSS after portgroup creations Shutdown remaining port Remove from LACP Add that NIC into the VSS Enable the port back.  

@roynaim, Could you please let us know the NetApp hardware you are using? Also, could you please attach /var/log/vmkernel.log file from the ESXI on your next reply? Try to add the VVol again to generate new logs.

Hello @markey165, If you need to disable the alert, you can go to the vCenter object -> Configure -> Alarm Definitions, then search for "Identity Source LDAP Certificate is about to expire" and click on Disable. Check on the screenshot below:    

@lakul, I believe this could be because of the vSphere Back-in Time but to be sure, could you please share the proper VCSA Build? The one you shared with me is an ESXi one. For getting the vCenter one you could go to the vCenter object into the vSphere Client, click on Summary and you will see the version there.

@kelalg, Have you tried first to log off, clear the cookies of your browser and try again? Sometimes this is a good solution. Also, if this happens through vCenter, have you tried from the Host Client?

@risingflight, As mentioned before by @TheBobkin, the insights will be in the vmware.log file. In order to get it, do the following: Connect to vSphere Client Go to the Datastore View Select the Datastore and click on Files tab Search for the VM Folder Download the vmware.log You could also access to the ESXi over SSH to "/vmfs/volumes/DATASTORE_NAME/VMFOLDER/vmware.log" and read it from there using "tail/less/cat" or the tool of your choice.

@Baktery, Realtek used vmklinux drivers that have been deprecated starting vSphere 7 so you will not be able to get them as they are VMware proprietary and they come embedded into their ISO. However, you could try to use the following USB Network Driver Fling: https://flings.vmware.com/usb-network-native-driver-for-esxi  

@NarinNil, The best way would be getting the latest updated log on the following path on the new appliance deployed: /var/log/vmware/upgrade Also, could you please let us know what is your source build and your destination build of the VCSA? Because there is a vSphere-back in time restriction issue that is also a reason for this error: https://kb.vmware.com/s/article/67077

@aniros, I am getting a lit confused with your scenario. If you decide to use iSCSI Storage, this should be coming from a storage outside of the two ESXi and mount the volumes directly inside the Guest OSes that form the cluster. That way if one ESXi goes down, the secondary ESXi will still have a node running.