VMware Cloud Community
PhilPollard
Enthusiast
Enthusiast
Jump to solution

vShield Login Error when installing VCD

I am doing an install of vcloud director.

I have installed and configured vshield as per the instructions in the documentation, (also available in KB 1026168) No visible errors are produced, everything works as described in the instructions. I can ping the host, and hitting it with a web page brings up the vshield web console login.

However, when installing VCD and I give it the IP and user and pas (admin/default) for vShield, I get the error "Failed to connect to the vShield Manager. - HTTP/1.1 401 Unauthorized"

I have confirmed there is a network path between, both hosts can see each other, etc.

I have confirmed that vShield is the proper version. I deleted and redeployed another vShield from template and had the same issue.

Seeing "unathorized" and "HTTP" I'm going to guess it is probably not a network connectivity issue.

If I try to log into the web console on vShield with admin/default, I get "Login failed for user 'admin'. Please try again." -- but I can log onto the console with admin/default

I get the feeling I am missing something simple. Please advise?

I am available for consulting: http://www.tsslink.com/ My focus is automation and programming with VMware.
Reply
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

If I try to log into the web console on vShield with admin/default, I get "Login failed for user 'admin'. Please try again." -- but I can log onto the console with admin/default

This is not a licensing issue, but a vShield initialization issue. You should post this on http://communities.vmware.com/community/vmtn/vshield?view=discussions instead.

View solution in original post

Reply
0 Kudos
5 Replies
sjoglekar
Enthusiast
Enthusiast
Jump to solution

You need to check if the licensing informtion for VSM is correct. This error comes up when correct license is not found.

HTH,

Sangeeta

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

If I try to log into the web console on vShield with admin/default, I get "Login failed for user 'admin'. Please try again." -- but I can log onto the console with admin/default

This is not a licensing issue, but a vShield initialization issue. You should post this on http://communities.vmware.com/community/vmtn/vshield?view=discussions instead.

Reply
0 Kudos
vgdas
VMware Employee
VMware Employee
Jump to solution

The login credentials for web-manager  console and CLI console are maintained separately. If you are having  problem in logging into the web-console, probably database initiation  would have failed. You can reboot the system to see if that recovers. If  reboot also doesn't recover the system, then I would recommend to  redeploy vShieldManager ova again and try.
-Govind

PhilPollard
Enthusiast
Enthusiast
Jump to solution

Thank you for the wonderful suggestions:

Re: Licensing issues suggestion

Since you need to access the web interface to add or update the license to vShield, this is a no-go for this partcular problem.

Re: vshield community suggestion

Some posts revealed helpful information on resetting the internal databse or rebooting, both of which I tried several times with no luck.

Re: reboot and redelpoy suggestion

Tried this a few times. On the right track with that

What it was:

I was deploying on some scratch NFS disk to do this. My slow disk. If I moved to my fast disk, then the deploy worked perfectly.

I have confirmed this with several tests, the speed of the disk definitely effects the initialization of vShield Manager.

This is rather disconcerting. That would tend to imply some sort of a race condition either in the initialization of vShield Manager or in the product itself.

Please pass the info along to the appropriate person, if possible. Otherwise, I hope this post might help out similar troubled users.

I am available for consulting: http://www.tsslink.com/ My focus is automation and programming with VMware.
Reply
0 Kudos
carlosVSZ
VMware Employee
VMware Employee
Jump to solution

We published a new KB article that addresses this issue: http://kb.vmware.com/selfservice/documentLinkInt.do?micrositeID=null&externalID=1032712

Reply
0 Kudos