bridgegroup
Enthusiast
Enthusiast

no NSX Manager in vSphere web client

Jump to solution

Hello.

I've installed and used NSX Manager 6.1 for several days. Even had some time to install and configure nsx controller.

Several days later I've lost NSX Manager in vSphere web client.

I rebooted NSX Manager several times without any success.

From NSX Manager point of view it seems to be ok.

I'm login as administrator@vsphere.local.

Where can I begin troubleshooting?

Any advices please!

Thanks!

1 Solution

Accepted Solutions
ShanVMLand
Expert
Expert

Re-register the Lookup service and vCenter server in NSX manager.  (reenter those information again)

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

View solution in original post

20 Replies
ShanVMLand
Expert
Expert

Re-register the Lookup service and vCenter server in NSX manager.  (reenter those information again)

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

View solution in original post

bridgegroup
Enthusiast
Enthusiast

Done several times.

did not help.

0 Kudos
Sreec
VMware Employee
VMware Employee

Hi,

    Can you confirm if NSX manager is populated under vCenter Solutions Manager list? I hope there is only one Solution(VCNS/NSX) registered with this VC?

Cheers,
Sree | VCIX-4X| VCAP-4X| VExpert 5x
Please KUDO helpful posts and mark the thread as solved if answered
0 Kudos
bridgegroup
Enthusiast
Enthusiast

Hello

0 Kudos
SamMcGeown
Contributor
Contributor

I had a similar situation, check to see if the extension is registered in the Managed Object Browser (MOB). Also check for a  historical vCNS extension. If either is there, remove it using the process here (step 2) virtualpatel.blogspot.com: How to do Partial / Full Uninstall of NSX Manager / Components reboot vCenter and then re-register from NSX manager.

bridgegroup
Enthusiast
Enthusiast

Hello

0 Kudos
SamMcGeown
Contributor
Contributor

com.vmware.vShieldManager is the extension name for vCNS and NSX - remove that one. By historical I meant that if vCNS was there before, the extension would be there anyway.

YohanTurner
VMware Employee
VMware Employee

This has happened to me several times before and is usually to do with either permissions with the account you are using in vSphere under the vSphere "Roles" icon or with the account not being given administrator access in NSX under the NSX "Roles" icon (inside NSX), however this NSX roles tab will only be available once you have full access again.

Note:  Ensure you that you are logging onto the web client with the same account you are using in the vCenter / NSX Manager registration page.

I would try the following steps:

1. Check vSphere roles and ensure your "administrator@vsphere.local" account has full permissions and access.

1.1 Look also for a 2nd account that has full administrator access and note the username and password . If there isn't one create one.

2. Remove the vCenter registration details you have within the NSX Manager input a incorrect username / password so that authentication fails. Re-enter the correct details using the original correct "administrator@vsphere.local" account, ensure a connection is established and you get the green circle again.  Try NSX again.

3. If that still fails, remove the "administrator@vsphere.local" account in NSX manager and input the details of the new 2nd administrator account you setup or found. Try again.

4. If that still fails are you using AD ? If you are try one of the administrator accounts in AD , that is also listed as a Admin in vSphere, use this account for the vCenter registration using the full AD username eg: "EKGF\administrator" and then try again.

Remember:  Ensure you that you are logging onto the web client with the same account you are using in the vCenter / NSX Manager registration page, so make sure you log out each time and log back in with the correct account.

Yohan

bridgegroup
Enthusiast
Enthusiast

Hello

Hello YohanTurner,

There are several users (internal and AD) in vCenter administrators group.

administrator@vsphere.local is among them.

I've reconnected NSX to vCenter using different usernames (also with wrong credentials) to solve this problem. Unfortunately these steps did not help.

It is NOT a problem concerning roles like here.

Working with NSX - Assigning User Permissions - Wahl Network

For some period of time it works;)

And I did not make any changes on NSX. Only vCenter was rebooted.

0 Kudos
YohanTurner
VMware Employee
VMware Employee

Yes exactly  this is what i am referring to : Working with NSX - Assigning User Permissions - Wahl Network

Did you try using a FQDN eg : svc_nsx@glacier.local, to register vCenter and also logon to the web client with ?

You mentioned sometimes it works......If you can get it working you need to go into NSX Roles and check whats going on, add in accounts that should have access to NSX

Yohan

0 Kudos
bridgegroup
Enthusiast
Enthusiast

Hello YohanTurner,

sorry for my inattention.

It is not my problem. I corrected my previous post.

0 Kudos
SamMcGeown
Contributor
Contributor

In my experience you don't need to redeploy the NSX manager, simply remove the extension in the MOB and then re-register NSX with vCenter. I was not able to find a root cause of the intermittent failure to find NSX Manager, and I was not able to resolve with Chris Wahl's solution, though it is something to check first.

0 Kudos
bridgegroup
Enthusiast
Enthusiast

0 Kudos
Richard__R
Enthusiast
Enthusiast

I know you say it was working at one point (and it's probably an obvious question) but you don't have any firewalls in between the vCenter and Manager do you?

0 Kudos
bridgegroup
Enthusiast
Enthusiast

0 Kudos
vm4u
Contributor
Contributor

Hi

Can you upload the logs ??

To collect diagnostic information for VMware NSX for vSphere:

  1. Through a web browser, log in to the NSX Manager virtual appliance.

    Example: http://NSX_Manager_IP

  2. Under NSX Manager Virtual Appliance Management, click Download Tech Support Log.
  3. Click Download.
  4. Click Save to download the log to your machine.

    Note: The log is compressed and has a.gz file extension.

Regards

0 Kudos
bridgegroup
Enthusiast
Enthusiast

Hello community.

Thank you very much for your help.

What helped me:

1. removing extension

2. rebooting nsx + vcenter

3. re-registering Lookup and vCenter services with right acount

4. adding roles

0 Kudos
thitisue
Contributor
Contributor

I got the same problem too. "Network & Security" icon it not exist on vSphere web client. That recently i can use.

:smileyplain:

0 Kudos
BSheets
Contributor
Contributor

For my issue, NSX was registered using administrator@vsphere.local. I would then log into the web client using my domain account and received the no NSX manager. When I logged in as administrator@vpshere.local the manager was present. Simple solution but could be easily skipped to at least get access and then can adjust permissions for domain accounts.

0 Kudos