Is anyone else experiencing slowness when navigating through pages under the Networking and Security plug-in within the WebClient. I just registered the NSX Managers at both of our sites to each of our vCenters and ever since pages have been loading very slowly. Oddly enough this just seems to be when I log in with a domain account that has access to NSX and vCenter. If I login with the local SSO account (administrator@vsphere.local) everything work as expected. We are running NSX 6.0.5 and vSphere 5.5 u1 and both vCenters are connected through Linked Mode.
Yes, I've seen this before. try to change the login to NSX from fully-qualified username@acma.com to AD\username.
Please update if it help.
I assume that you mean the login to the Web Client? I have tried both ways and they yield similar results. username@domain.com or domain\username.
It's in the Networking and Security -> NSX Manager -> Manage -> Users. When you add a user (or a group) in there, create it in DOMAIN\user or DOMAIN\group format.
I just tried that and it doesn't seem to help the slow load times. Basically I am not getting either one of the NSX Mangers displaying for 15-20 minutes after I go into that section on the Web Client. This is with a domain user that has access into NSX. If I use the domain service account that was used to register each NSX Manager with vCenter it is a little faster. If I use the local SSO admin account it is instantaneous.
This looks like a bug. Please open a support case.
Case has already been opened on my end. We hope to have a quick resolution on this. Thanks for providing ideas.
is the problem get resolved ? can you please update ....
No the problem hasn't been resolved yet. We have had the hardest time getting any traction on this case with GSS. I finally got a communication back from them but at this point it is looking like a bug even in version 6.1. We tried to go to 6.1 yesterday and the slowness still persists.
Switching from using user@domain to domain\user worked for me. I have been receiving error 2032, 2036, 1009 for days. Hopefully logging in like this will get me by until a fix is released. This definitely seems like a bug.
My case has finally been escalated to engineering for investigation. It appears that there is a bug with NSX and SSO. Using local SSO users is fine and using AD accounts that are members of few groups in AD (i.e. less than 5) is also acceptable, however when you have users that are members of a large amount of AD groups this really slows down NSX loading times in the Web Client. I have been seeing around 3 minute load times. Switching the user format doesn't improve matters for us either.
I will keep everyone updated once I have a resolution.
Thank you for sharing this info.
Currently have a support ticket open with VMware for the same issue.. these are my findings so far:
After logging into the vSphere Web Client, then clicking on Networking & Security, the time taken for NSX Managers to change from [--] to [1]:
---
Account, Number of Groups, Time Taken
AD Account 1, 1 group, 15sec
AD Account 2, 19 groups, 1min46sec
AD Account 3, 53 groups, 3min29sec
admin@vsphere.local, 0 groups, 0 sec - showed [1] straight away, did not show [--].
Glynn
Thank you for sharing this information. Our ticket is still open on this same issue and has been escalated to NSX engineering for a fix. I am still awaiting word on what the fix is and when it will be available. I am glad to hear that we are not the only ones experiencing this issue so maybe this will put more pressure on them to get a fix out faster.
Jordan
Did you ever get a resolution? I have found that if you use a SSO local group, but add the domain users or domain groups to it then things work very quickly.
Thanks,
Tommy
On your NSX Manager unconfigure the Lookup Service options under the manage tab. You should find that all webClient is now usable and NSX much quicker.
Unconfigure the Lookup Service will prevent you to authenticate users with vCenter SSO. only local user will work.
I agree. But it is what is causing the problem. I have a support ticket in to Vmware for this issue as well.
Hi guys I wanted to inform you that I have encountered this problem distressing . However I can tell you even if late that the problem you can solve it by adding records in the reverse lookup zone on your DNS . You not just add a PTR the product will become a splinter .
A greeting