Worked on this issue recently where, after upgrading to ESXi 5.5, a rescan on a software ISCSI initiator was taking a long time to complete. About 10 minutes.
There were only two LUN’s presented to the software ISCSI initiator
The software ISCSI initiator was configured to discover LUN’s from four targets.
The vmkernel.log and hostd.log did not show any errors or relevant messages for the ISCSI initiator.
The software ISCSI daemon logs into the following file: /var/log/syslog....
In order to check if a snapshot chain is broken in ESXi 5.x and later:
Run the command:
`vmkfstools -e -v10 .vmdk
For e.g: vmkfstools -e -v10 “XP-64-000003.vmdk”
Login to the vCenter Server appliance using the VM console or using putty:
The default credentials are:
Username: root
Password: vmware
Run the following command:
/opt/vmware/share/vami/vami\_config\_net
For purging data look at the following VMware KB: http://kb.vmware.com/kb/2008223
For removing resources/data collected for stale non existing VM’s look at, http://kb.vmware.com/kb/2020638
To connect to the Capacity IQ database:
1. SSH to the UI VM.
2. Switch to the postgres user using the command: su - postgres 3. Connect to the database using the command: psql cmapp
4. To list all tables, type \\d at the cmapp=# prompt.
5. For hep with SQL commands type \\h at the cmapp=# prompt.
6. For help with PSQL commands type \\? at the cmapp=# prompt.