This post is more than 5 years old
23 Posts
0
6722
February 28th, 2013 13:00
VNXe 3150 VSI plugin issue that EMC support cannot resolve
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
KEYTOOLZ
23 Posts
0
March 6th, 2013 11:00
Thanks for the hand hlding.
Im ataching the logs now.
KEYTOOLZ
23 Posts
0
March 6th, 2013 11:00
The log TAR file is too large and will not upload. Its just under 200MB
KEYTOOLZ
23 Posts
0
March 6th, 2013 11:00
Thanks for the hand hlding.
Im ataching the logs now.
1 Attachment
emc_dump_collection.tar
keytool
1 Message
0
March 6th, 2013 12:00
Yuli,
I have uploaded both log files to the case I have open with EMC support.
You should have that case number from a previous private message I sent you.
Thanks for the continued assistance.
KEYTOOLZ
23 Posts
0
March 11th, 2013 10:00
I disabled ASA, saved the conig, then re-enabled ASA. I set the password again. I then went into VSI plugin and checked the "enable ASA" box and entered the password.
I get the exact same error.
I dont know the comands or the location to delete the account if it exists in the the VNXe appliance itself.
Is there a search string I can run on the appliance to search if the account exists anywhere?
KEYTOOLZ
23 Posts
0
March 12th, 2013 11:00
I dont know if that is going to be a viable route to resolution but I will try again. I understand you can only help me so much...
This has been in with the EMC support team for weeks but you got me closer to resolution than ever in a couple days.
They never even asked to look at the logs before I provided them per your suggestion...
I appreciate all your help Yuri.
KEYTOOLZ
23 Posts
0
March 13th, 2013 09:00
This is resolved now through support.
The problem was some sort of fix they found.
He said he "followed the primus to get it done". (whatever that means)
he said it was on primus.emc.com but when I tried to connect to that site I could not access it at all.
I don't think I would have this resolved if it was not for all your help Yuli.
finally after weeks of working on this issue.
thanks very much!!