This post is more than 5 years old
10 Posts
0
6598
vRealize Operations Manager (vROps) login for SANHQ
I've downloaded and installed the vRealize Operations Management Pack for Dell EqualLogic but I don't understand what username and password are used when configuring the vROps Adapter. I've gone through the instructions (Dell Storage PS Series vRealize Operations Management Pack - Administrator Pack) multiple times with no success. (Reference page 13) By using the ConfigureRestService.exe get and netstat -a commands I have verified port 1443 is available and listening. When configuring the vROps Adapter to connect to SANHQ it's asking for the Username and Password for the SANHQ Rest API. I've tried multiple Domain and Local accounts with no success and users cannot be defined in SANHQ. I don't understand what account it's asking for. Can anyone help?
ngemc
10 Posts
0
March 1st, 2018 10:00
OK, so... I corrected my issue with a "shotgun" approach. Only after completely uninstalling and reinstalling SANHQ was I able to successfully connect from vROps.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 1st, 2018 07:00
Hello,
Try using the account that the SANHQ service is using. Under Services, look for EQLperfx.
There are two accounts that are needed for vRops. One for SANHQ one for the Virtual Center server.
Regards,
Don
ngemc
10 Posts
0
March 1st, 2018 07:00
I tried that again. The SANHQ service uses the "Local System Account" by default so I changed it to a known domain account. Performing a Test Connection from vROps still fails with error "Unable to establish a valid connection to the target system. Enter correct SAN Headquarters credentials to fetch Array objects."
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 1st, 2018 07:00
Hello,
Try using the account that the SANHQ service is using. Under Services, look for EQLperfx.
There are two accounts that are needed for vRops. One for SANHQ one for the Virtual Center server.
Regards,
Don
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 1st, 2018 08:00
Hello,
Yeah sorry couldn't be more help. The screenshot came from a lab system so I know it works. :)
You are running vRops v1.3 correct? v1.2 looked for 443, which would require SANHQ v3.2.
VMware changed it to 1443 in VRops v1.3 so that requires SANHQ v3.3
Regards,
Don
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 1st, 2018 08:00
Hello,
Try the local Administrator account. I've seen problems using an AD domain account with local services.
Don
ngemc
10 Posts
0
March 1st, 2018 08:00
Thank you. I am running SANHQ 3.3. I was hoping someone in the community had seen this work successfully and could offer any advice before I went the route of a support case.
ngemc
10 Posts
0
March 1st, 2018 08:00
I've set the EQLXPerf windows service to run as the local administrator account and tried to connect from vROps and still no success. Same Error.
ngemc
10 Posts
0
March 1st, 2018 08:00
I'm running SANHQ 3.3.1 & vROps 6.6 with Dell Storage PS Series Adapter 01.03.007. Can you post the screenshot again? I don't see one from you earlier.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 1st, 2018 08:00
Hello,
Best suggestion I have now is open a support case so they can take a closer look.
You are running SANHQ v3.3+ correct?
Regards,
Don
ngemc
10 Posts
0
March 1st, 2018 09:00
Yes, I have tried that too. Thanks for your help.
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 1st, 2018 09:00
Hello,
It was just a dialog box showing the two entries needed. Not all the screenshots are showing up.
It shows as MACHINENAME\Administrator Then the password.
Did you add in the host\username?
Don
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 1st, 2018 10:00
Hello,
That's a new one for sure. Sounds like some kind of permission issue on that E:\ drive would be my first guess.
Don
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
March 1st, 2018 10:00
Hello,
Thanks for letting us know. I'm so glad you got it working.
Re: SANHQ. Was this server upgraded from 3.2. to 3.3.1 or a fresh install of 3.3.1 from day one?
I'm wondering if something didn't get upgraded properly, so as to be on the correct port.
That's just a guess.
Regards,
Don
ngemc
10 Posts
0
March 1st, 2018 10:00
I have a suspicion but was unable to fully confirm it. I originally had SANHQ (fresh 3.3 install) installed to an E:\ drive with historical data restored from a previous version. I tried reinstalling 3.3 over the top and that did not fix the issue. I then moved on to uninstalling and reinstalling to the E drive wiping the data. This too did not resolve the issue. I then uninstalled and reinstalled to the C:\ drive and it started working. To help confirm this theory I uninstalled and reinstalled back to the E:\ drive and it stopped working again.