Hi Keytoolz,  As Zack mentioned above, after we reviewed your VSI logs, the error occured when you tried to add VNXe with ASA enabled was not caused by VSI, it seems that there are something wrong with your DHSM server, so we need your VNXe related log for further investigation, can you try to reproduce this issue and gather the log, then upload the VNXe log here?  There are two ways to gather the data collects from the VNXe:  Method1. Using Unisphere:1.     Go to Settings > Service System. 2.     Enter the service password when prompted. 3.     Once it is done loading, there is an option in the middle pane that says "Collect Service Information".  Select this option and choose "Execute service action". 4.     A dialog box will display asking if you want to gather new logs or existing logs.  Choose "No" to gather new logs. 5.     After the logs are gathered you will be prompted to download the logs to your computer.  Select "Yes" and choose where to save the logs.  Method2. Using Secure Shell (SSH) or console:1.     Log in as service. 2.     Run the command svc_dc. 3.     Open the SFTP client and SFTP into the Management IP address as service. 4.     Go to /EMC/backend/service/data_collection, locate the most recent file and download.  To gather dumps you will need to do the following: 1.     Establish a SSH to the VNXe and login as service. 2.     Take note of which Storage Processor (SP) you are on, the one you are automatically connected is the primary SP. 3.     If you need dumps from the primary SP then move onto step 4.  If you need logs on the peer SP or both SPs do the following:         a.  To get to the peer, type in ssh peer then move on to step 4.        b.  Once you are done with the other steps, you will need to move the files from the peer to the primary SP.        c.  To move the files from peer to primary, type in scp filename.tar peer:/home/service. 4.     Run command cd /EMC/backend/service/data_collection/cores. 5.     Find all directories (not files) that are newest.         a.  The files will look similar to spa_APM123456789_09-25-2012_14-31-23_logs_dump.tgz        b.  Directory names will end in _dir. 6.     Run the command tar -cvf /home/service/choose_a_filename.tar directory_name. The .tar file will be in the /home/service directory. 7.     Open an SFTP client and SFTP into the Management IP address as service. 8.     Go to the /home/service directory, download the new .tar file created
I have installed the unisphere CLI and the vsphere plugin to enable ASA so I can take advantage of snapshots etc.. from within vcenter.  have the bits installed correctly but I still have a problem that EMC support cannot resolve. I have added my VNXe 3150 in the plugin interface on my vsphere client. I am trying to complete the ASA configuration to enable snapshots from within vcenter.   Within Unisphere I have enabled ASA for all ESX nodes and I have set the password for the "asa" user.   I then go to add the password on the vcenter side by clicking EDIT on the VNXe I added, and entering the password as well as hitting the checkbox to enable ASA.   The password will not be accepted. I see the task queue up and then I get an error saying "the operation is not allowed in the current state". I also see a message saying "the remote server returned an error 500 Internal server error"   EMC says the issue is because the VNX NFS interface needs to be able to communicate with the ESX vmkernal interface.  VMware says that is not a problem and works by nature that way since you can ony specify a singel defaut gateway for the NFS storage network interface and the VMkernal interface. Furthermore they say not only EMC but other storage vendors only need to be able to communicate from their management interface to the vmkernal interface in order to take advantage of the enhance storage API's for vsphere 5.1.   The VNX management interface can ping the vmkernal interface without a problem so vmware says this is an EMC issue. The EMC guy I am working with does not know much about VSI plugin and vcenter integration. I asked to escalate but it does not seem to happen I’m in limbo now. No one at EMC seems to be able to do this in a lab or see how it is supposed to work in order to help.  I sure hope someone has done this and knows what the issue is. There is little info on the web and I already read the plugin install instructions and I am installing correctly but it still does not work.  VNXe Interfaces:   NFS = 10.0.1.10 Management = 172.16.2.100   ESX Interfaces:   NFS (vmk1) = 10.0.1.50 & 10.0.1.55   Vmkernal management (vmk0) = 172.16.2.50 & 172.16.2.55  Thanks in advance 
VNXe 3150 VSI plugin issue that EMC support cannot resolve