Install VAAI 1.2.3 on ESX 6.0 could cause ESX server to become unresponsive

Article Number: 504703 Article Version: 4 Article Type: Break Fix



Isilon VAAI,Isilon OneFS,VMware ESX Server

After installing VAAI 1.2.3 plugin on ESX 6.0 server, log file /var/log/isi-nas-vib.log can grow unbounded, eventually filling up /var partition and can cause ESX server to become unresponsive. The log file will continue to be recreated after it is removed.

VAAI 1.2.3 plugin was built with debug enabled by default

WORKAROUND

Uninstall VAAI 1.2.3 plugin until a fix is provided.

OR

Setup a cron job on ESX 6.0 server to periodically remove the log file:

1. ssh into ESX server and login as root user

2. edit /etc/rc.local.d/local.sh, and add the following lines toward the end, before “exit 0”:

/bin/echo ‘*/15 * * * * /bin/rm /var/log/isi-nas-vib.log’ >>/var/spool/cron/crontabs/root

/bin/kill -HUP $(cat /var/run/crond.pid)

/usr/lib/vmware/busybox/bin/busybox crond

3. The reason for the above step is so if ESX server reboots, the workaround will persist after reboot. But at this point workaround has not been set on the ESX server yet.

4. Manually run the above 3 yellow-highlighted commands to implement the workaround on the current ESX server session.

5. Monitor /var/log/syslog.log and make sure you see every 15min an entry such as:

2017-10-03T15:15:01Z crond[35429]: crond: USER root pid 38236 cmd /bin/rm /var/log/isi-nas-vib.log

Related:

  • No Related Posts

ViPR Controller : Deleting a datastore fails with “Unable to find datastore”

Article Number: 525425 Article Version: 2 Article Type: Break Fix



ViPR Controller,ViPR Controller Controller 3.6

The user is unable to delete a VMware datastore and volume via the VIPR Controller Delete Datastore and Volume catalog order.

ViPR Controller UI error

Message: Unable to find datastore DATASTORE_NAME in datacenter DC_NAME

Status: ERROR

Catalog Service: Delete Datastore and Volume

ViPR recognises the volume as a VMware datastore and attempts to unmount and dettach the volume before un-exporting & deleting it.

The datastore was deleted by the user therefore ViPR Controller cannot find the datastore to unmount.


The VMWare datastore was deleted at the ESX layer but the underlying block volume was still exported to the ESX host(s).

Workaround:

Re-create the the datastore again on that particular volume and re-run the “Remove block volume for VMware” order.

Resolution

  1. Remove the Datastore tag on the volume in VIPR-Controller
  2. Perform an “Unexport and Remove Block Volume”order.

To remove the datastore/VMFS volume tag run the command below:

/opt/storageos/clin/bin/viprcli volume tag -remove “vipr:vmfsDatastore-ESX_CLUSTER_URN=DATASTORE_NAME” -pr “PROJECT_NAME” -name “VIPRC_VOLUME_NAME” -tn “TENANT_NAME

Note:

1. ESX_CLUSTER_URN is the URN id of the ESX Cluster in the ViPR-C DB.

To retrieve a list of the clusters and their respective VIPR-C URN id’s please run the following command from the ViPR Cli.

/opt/storageos/bin/dbutils list Cluster | grep “label” -B 12 | grep “id:|label”

2. DATASTORE_NAME is the name of the VMware datstore as it appears in vSphere.

3. PROJECT_NAME is the name VIPR project that the volume is associated to.

4. VIPRC_VOLUME_NAME is the name of the volume as it appears in the ViPR-C UI.

5. TENANT_NAME is the name of the Tenant that the VIPR-C volume is associated to.

ViPR Controller UI errors

[INFO] Tue Sep 11 10:15:22 UTC 2018 Find Datastore did not succeed, will retry: Unable to find datastore DATASTORE_NAME in datacenter DC_NAME

[INFO] Tue Sep 11 10:15:32 UTC 2018 Retrying Find Datastore

[ERROR] Tue Sep 11 10:15:32 UTC 2018 Maximum number of retries exceeded for Find Datastore

[ERROR] Tue Sep 11 10:15:32 UTC 2018 Find Datastore failed with error: ‘Unable to find datastore DATASTORE_NAME in datacenter DC_NAME’

[ERROR] Tue Sep 11 10:15:32 UTC 2018 Unable to find datastore DATASTORE_NAME in datacenter DC_NAME

com.iwave.ext.vmware.VMWareException: Unable to find datastore DATASTORE_NAME in datacenter DC_NAME

at com.emc.sa.service.vmware.tasks.FindDatastore.tryExecute(FindDatastore.java:31)

at com.emc.sa.service.vmware.tasks.FindDatastore.tryExecute(FindDatastore.java:13)

at com.emc.sa.service.vmware.tasks.RetryableTask.tryOnce(RetryableTask.java:62)

at com.emc.sa.service.vmware.tasks.RetryableTask.executeTask(RetryableTask.java:55)

Related:

Re: VIPR Controller: Discover ESX host clusters, then add vCenter Later

hi Sathyaprakash, thank you for your reply,

I added 2 ESX MGT hosts from a chassis manually as type ESX, however I was not able to provision storage to them via VIPR C, either via Create Volume for VMware, error is:

This service is missing required data. This could be caused by:

  • No Options available for field: vCenter
  • Required assets (Host, Switches, Storage Arrays) are not defined or you do not have permission.
  • The system is busy discovering assets (Host, Switches, Storage Arrays).
  • Unable to connect to a ViPR backend server.

I’m looking into this, but not sure how to correctly add individual ESX hosts.

The aliased HBA WWN’s do not show up in the Fabric Manager switches.

VIPR is able to see and provision to other hosts, I have an authentication provider for the domains.

Related:

  • No Related Posts

ScaleIO: Is IPv6 supported in ScaleIO 2.0.1.1 hyper-converged ESXi environment?

Article Number: 494807 Article Version: 3 Article Type: Break Fix



ScaleIO 2.0.1.1,ScaleIO 2.0.1.2,ScaleIO 2.0.1

Is IPv6 supported in ScaleIO 2.0.1.1 hyper-converged ESXi environment?

Due to a possible IPv6 issue between ScaleIO and VMware, one might experience a major performance drop on inbound traffic over uplink traffic in ESX. 5.5 and ESX 6. This affects both SDS and MDM deployed on an ESX.

Currently, for a VMware ESX environment, using IPv6 is supported in an SDC-only deployment (a.k.a. 2-layer).

SDS or MDM on an ESX should not be used in an IPv6 environment.

The issue is addressed in a newer SLES 12.x OVA. This is targeted for ScaleIO 2.1 code and it has a release date of Q3. Please note that this date could change.

Related:

SGOS Downloads

I need a solution

I’m trying to work out how to download a working SGOS image to run some tests in VMWare Workstation. The ESX version normally works, but I have hit an issue importing the ovf I have for 6.7.3.1 I managed to download a few months back. When browsing Symantec’s download site for ProxySG – VSWG I’m presented with a list of versions either General Availability, Early Availability or Patch, but can’t work out what release is going to lead me to a copy for ESX – it all seems to be haphazard. Some labled GA include images for various hypervisors (e.g. 6.7.3.6 has an image for AWS and HyperV but not ESX) whereas other GA releases have no hypervisor images just the .bsci (e.g. 6.7.3.2). Is there any logic to this? And what exactly is an “archived version”? What’s happened to the ESX images, they seem to have disappeared? I’m confused, can anybody offer some insight? Thanks Matt

0

Related:

Re: Unity AFA – my esx hosts Vmware 6.5 were registered with FC conectivity but only the cloning VMs process takes more time compared to VNX

i forgot to integrate unity with vmware,

and VASA provider installation was not completed.

can i install it without disruption? i am in production, with many block luns presented as datastores, and many VMs running.

any impact?

i need to use feature to offload proccess from esx hosts to Unity processors, like my cloning vm.

please any comments?

Related:

  • No Related Posts

Unity AFA – my esx hosts Vmware 6.5 were registered with FC conectivity but only the cloning VMs process takes more time compared to VNX

i forgot to integrate unity with vmware,

and VASA provider installation was not completed.

can i install it without disruption? i am in production, with many block luns presented as datastores, and many VMs running.

any impact?

i need to use feature to offload proccess from esx hosts to Unity processors, like my cloning vm.

please any comments?

Related:

  • No Related Posts

BigFix 9.5.4.38/LMT 9.2.7.0 VM Manager no data

We have BigFix 9.5.4.38 feeding LMT 9.2.7.0, both running on a single Windows 2K12 machine with a MSSQL Express 2014 database for BigFix and ILMT. This setup is at our Cloud Provider where they have access to the BigFix Console and we get access to the ILMT console only via the web URL for VMware ESX 5.5. We worked with the vendor and got the VM Manager to connect and start reporting PVUs correctly. After about 2 days, the VM Manager went back to Inactive state again and PVU values became incorrect. We checked the User ID and Password (that had not changed). We can connect to the VMware ESX URL/port from the BigFix machine, so connectivity is not a problem. The vmman_.properties file in the Config folder was checked and the ID was not locked out due to incorrect password attempts (vmm_communication_locked=false).

With a webex, we did a vmman.bat -stop and then a vmman.bat -run, did a vmman.bat -testconnection (which was successful), we did a vmman.bat -status (which reported no problems with the vm manager) and let the upload happen to ILMT. We recycled the BES FillDB Service, and also forced a manual import from the LMT console, but the status still says Inactive with wrong PVU counts.

We deleted the entry, and recreated it again. It started off in a Pending status (with a successful Test Conn) and then we ran thru the entire process all over again. It can connect via the vmman.bat -testconn but has reverted back to Inactive on ILMT. When we ran the vmman.bat with the -retrievedebug option, from the logs and from the sha1 folder, it appears to me at least that the VM Manager conn is being made in BigFix, BigFix has created the for an upload but nothing happens after that.
I have gone through this URL:
https://www.ibm.com/support/knowledgecenter/en/SS8JFY_9.2.0/com.ibm.lmt.doc/Inventory/admin/c_troubleshooting_no_vm_manager_data.html

I have gone through the debug data and verified that there are no duplicate UUIDs. There is no authentication error in the login.xml. I can see the HostCPUPackage tag in the retrieveProperties.xml file.
I can verify that all the Server IDs (32 chars, without the TLM_VM) are present in the uploadvmman_scan_2_1515602819.xml file. So it looks as though bigFix is getting it ready for Upload. I have restart the BES FillDB and then manually reloaded the ILMT import, but nothing is updating on ILMT.

What steps can I take to either isolate the problem some more or resolve this issue?

Related:

Can you provide additional details on the monitoring capabilities of the VMware agent version 7.2 FP4?

I need to install a VMware agent 7.2 FP4 in a Windows machine which can have the remote access to VCVS 6.5 but my query is:

Q1: Does the VMware agent have the capability to monitor all the ESX servers managed by VCenter or do we need to create a separate instance for these ESX during the agent configuration ?

I have application support for VMWARE VI agent 7.2 FP2 available in HTEMS, I can install VMware 7.2 FP4 in TEMA and the respective support in RTEMS but as of now we cannot install the 7.2 FP4 support in HTEMS because it needs a restart.

Q2: Can we see all the data collection in the TEP Console workspaces with this lower level of support?

Q3: If the upgrading of application support is necessary, could you please tell me is there any way to upgrade the support from VMWARE agent version 7.2 FP2 to 7.2 FP4 in HTEMS without any restart of TEMS application?

Related: