Restart ESXi vvold service | restart esxi service | vvOL iscisi volume inaccessible

Error:

vvOL iscisi volume inaccessible

Solution:

[root@localhost:~] chkconfig -l vvold

vvold                   on

[root@localhost:~] /etc/init.d/vvold stop

/etc/init.d/vvold stop, PID 566186

Added 566186 to /var/run/vmware/.vmware-vvol.lock-dir/vvold-lock-dir-pid (1)

watchdog-vvold: Terminating watchdog process with PID 528725

vvold stopped.

Successfully cleared vvold memory reservation

PID 566186 removed /var/run/vmware/vvold-done-calling-start

Removed /var/run/vmware/.vmware-vvol.lock-dir

[root@localhost:~] /etc/init.d/vvold start

/etc/init.d/vvold start, PID 566231

Added 566231 to /var/run/vmware/.vmware-vvol.lock-dir/vvold-lock-dir-pid (1)

vvold max reserve memory set to 200

WaitVvoldToComeUp /var/run/vmware/.vmware-vvol.started created

vvold started successfully!

PID 566231 Created /var/run/vmware/vvold-done-calling-start

Removed /var/run/vmware/.vmware-vvol.lock-dir

[root@localhost:~]

ONTAP SVM root volume Load Sharing Mirror(LSM)

 ONTAP root volume Load Sharing Mirror(LSM)

A load-sharing mirror reduces the network traffic to a FlexVol volume by providing additional read-only access to clients.A load-sharing mirror is mounted in the same area of the SVM namespace as its source volume. This is useful for frequently read, but infrequently updated data, such as shared binary files

Steps:

1. Create destination Volume:

C1_SVM1::> volume create -vserver vs0 -volume root_dest -aggregate sti8_vsim_ucs571x_aggr1 -size 2GB -type DP

[Job 241] Job succeeded: Successful

2)Create the Mirror relation

C1_SVM1::> snapmirror create -source-path vs0:root_vs0 -destination-path vs0:root_dest -type LS

[Job 243] Job succeeded: SnapMirror: done

3)Initialize the mirror

C1_SVM1::> snapmirror initialize-ls-set -source-path vs0:root_vs0

[Job 245] Job is queued: snapmirror initialize-ls-set for source "C1_SVM1://vs0/root_vs0".

4)Verify the relationship

snapmirror show -destination-path vs0:root_dest

ISCSI vVOL Datastore created by Netapp VSC/OTV is inaccessible

Error:

ISCSI vVOL Datastore created by Netapp VSC/OTV is inaccessible

Solution:

Add the iscisi LIF to ESXI 

 ESXI->Configure->Software iSCSI adapter->Dynamic Discovery

Do a rescan storage adapter.

Now already created VSC/OTV vVOL datastore will be available for use.

Enabling "VASA provider" from OTV/VSC is failing

 Error:

Enabling "VASA provider" from OTV/VSC is failing

Solution:

make sure the time sync is proper between Vcenter and netapp VSC

Increase SSH Connection Timeout in Linux

•  sudo vi /etc/ssh/sshd_config

        #ClientAliveInterval 

        #ClientAliveCountMax

• These config value will be used as timeout as below:

        Timeout value = ClientAliveInterval * ClientAliveCountMax

So if you want the timeout interval as 3600second, use below details in the config:

ClientAliveInterval  1200

ClientAliveCountMax 3

• Once you update the config reload ssh using below command

        sudo systemctl reload sshd

vcenter Server Root user password expired.

 Error:

Root user password expired.

Solution:

Login to VCSA through ssh with root.

it will prompt for changing the password.

 please provide old passwords and a new passwords.

VMWare ESXi 7 U1 Stop Time Sync with Host (Time Drift with NTP host for VMs)

Error:

 Noticed VMs in ESXi 7u1 had a time drift issue with NTP configuration.

Solution:

Power Off the VM host.

• Right click on VM ->Edit settings
• VM Options->Advanced
• Click on Edit Configurations

• Add Config Parameters and give below Params and Vlaue

tools.syncTime = 0
time.synchronize.continue = 0
time.synchronize.restore = 0
time.synchronize.resume.disk = 0
time.synchronize.shrink = 0
time.synchronize.tools.startup = 0
time.synchronize.tools.enable = 0
time.synchronize.resume.host = 0

• Power ON the VM

ESXi command to check license expired details

 

To check the license details:

vim-cmd vimsvc/license --show

To see the license expired date details:

vim-cmd vimsvc/license --show | grep -i date

Create resource Pool and vApp option is disabled

 Issue:

Create resource Pool and vApp option is disabled

Solution:

For enabling vApp to Resource Pool in vCenter server, HA cluster and DRS should be enabled.

1. Connect to your vCenter Server web client. Make sure that a cluster is created.

2. Go to Hosts and Clusters, select your cluster, open the Manage tab, then open the Settings tab, and select Services > vSphere DRS.

3. In the opened Edit Cluster Settings window, tick the Turn On vSphere DRS checkbox, and set DRS automation, power management, and advanced options if needed.

VMware vCenter services and details

 To restart any service :

 service-control --stop <Service>

 service-control --start <Service>

vCenter Server Appliance Services:

 

Service Name	Description
applmgmt	VMware Appliance Management Service
vmware-cis-license	VMware License Service
vmware-cm	VMware Component Manager
vmware-eam	VMware ESX Agent Manager
vmware-sts-idmd	VMware Identity Management Service
vmware-invsvc	VMware Inventory Service
vmware-mbcs	VMware Message Bus Configuration Service
vmware-netdumper	VMware vSphere ESXi Dump Collector
vmware-perfcharts	VMware Performance Charts
vmware-rbd-watchdog	VMware vSphere Auto Deploy Waiter
vmware-rhttpproxy	VMware HTTP Reverse Proxy
vmware-sca	VMware Service Control Agent
vmware-sps	VMware vSphere Profile-Driven Storage Service
vmware-stsd	VMware Security Token Service
vmware-syslog	VMware Common Logging Service
vmware-syslog-health	VMware Syslog Health Service
vmware-vapi-endpoint	VMware vAPI Endpoint
vmware-vdcs	VMware Content Library Service
vmafdd	VMware Authentication Framework
vmcad	VMware Certificate Service
vmdird	VMware Directory Service
vmware-vpostgres	VMware Postgres
vmware-vpx-workflow	VMware vCenter Workflow Manager
vmware-vpxd	VMware vCenter Server
vmware-vsm	VMware vService Manager
vsphere-client	vSphere Web Client
vmware-vws	VMware System and Hardware Health Manager
vmware-vsan-health	VMware vSAN Health Service

Restart VMware Webclient service

SSH to vCentre Server and run below commands 

 -> Flex UI: 

                service-control --stop vsphere-client

               service-control --start vsphere-client

  -> HTML5 UI: 

                service-control --stop vsphere-ui

                service-control --start vsphere-ui