Unsolved
This post is more than 5 years old
16 Posts
0
1915
vCenter VSI connection failure
Hello everyone,
we have got the following configuration:
EMC VNX 5300
VMWare vSphere 4.1.0 Build 348481 (with NFS storage connection)
vCenter Server 4.1.0 Build 345043 running on Windows 2008 64bit
On the vCenter Server EMC Virtual Storage Integrator 4.0.1.67 and Solution Enabler 7.210 is installed.
We use an NFS Export that holds the virtual machines for the ESX Servers.
I try to add the VNX as a "File" Device in the Unified Storage Management plugin.
After typing in the IP of the VNX control station and the user informations I get an error message
"Could not connect to File Storage System 172.16.201.60"
vCenter Server IP 172.16.201.31
Control Station IP 172.16.201.60
Storage SPA IP 172.16.201.61
Storage SPB IP 172.16.201.62
ESX-1 Console IP 172.16.201.21
ESX-2 Console IP 172.16.201.22
I am able to ping the control station and both storage processors from the vCenter Server and from the ESX service console.
What's wrong here?
Best regards
Robert
JoshHutt
13 Posts
0
June 14th, 2011 10:00
Please attach the USM feature's log file.
It can be found here: %APPDATA%\EMC\Virtual Storage Integrator\vSphere4\Logs\EMC.VSI.VSphere4.Features.USD.UnifiedStorageManagement.txt
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
June 14th, 2011 10:00
Attached...
1 Attachment
EMC.VSI.VSphere4.Features.USD.UnifiedStorageManagement.txt
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
June 14th, 2011 10:00
I'm seeing the same issue here, any resolution or items that should be checked?
I have this setup for 4.0 that points to the same array and all works great.
JoshHutt
13 Posts
0
June 14th, 2011 11:00
PBradz, in your case it looks like your stored credentials could be corrupt. Delete the contents of '%APPDATA%\EMC\Unified Storage\Config' and restart your vSphere Client, then try to add the VNX File credentials again.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
June 14th, 2011 12:00
Schweet!
I had not thought of trying that as everything else seems to be working...that's probably not the only corrupt thing on this box
I'll give it a go.
Thanks Josh!
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
June 15th, 2011 05:00
Thanks Josh, worked perfectly!
JoshHutt
13 Posts
0
June 15th, 2011 08:00
Glad to hear it!