Skip to main content

Initial Configuration of VMware NSX Manager

Here are the steps for the initial configuration of VMware NSX Manager- 

  • Deploy NSX Manager for the vCenter. NSX manager and vCenter have 1:1 binding, so if there are multiple vCenters - multiple NSX manager needs to be deployed each in one vCenter
  • Once NSX manager is deployed, logon to the NSX manager using the IP address or the FQDN of the NSX manager
  • Configure the NTP settings by clicking on "View Summary" on home page and then clicking Configure NTP Servers from Manage - General - Time Setting 
  • Once the NTP time settings are configured, configure look up service and vCenter Server to connect to the NSX manager. Click on manage vCenter registration and click on configure look up service to configure the lookup service. Accept the SSL certificate. Once Lookup service is connected successfully, register the vCenter to the NSX Manager. Note - SSO admin account (administrator@domain.local) needs to be used for the configuration of look up service and registration of vCenter Server.
  • Make sure Lookup service and vCenter Server is connected and with green status.
  • At this point, if you log off and log back in to the vCenter, the NSX manager icon would show up in the vCenter. 

  • But if you logon to the the vCenter with your domain account - you may not be able to see anything under the NSX Manager. First you have to login to vCenter using SSO domain account that you used to register vCenter with NSX manager. Assign the permissions to the required users so they can manage the NSX using their own accounts.
  • Click on the NSX Manager icon. Click on NSX Managers at the bottom which would show register NSX manager with the vCenter. Go to Manage - Users - click on "+" sign to add the users.


  •  Add the NSX license in vCenter and then assign the license to NSX Manager solution.


Comments

Popular posts from this blog

Guest Introspection(GI) NSX Appliance gets Deleted Automatically after vCenter Disconnect

I was working in an environment where NSX was configured with Trend micro deep security in VDI environment to protect VDI desktops. We had 2 vCenters setup in that way and one of the vCenter is showing some odd symptoms. We are seeing some weird actions with NSX manager in one vCenter. So, I lose the connection to the vCenter from fat client, web client is still fine and doesn’t kick me off. In the process, the Guest Introspection appliance or GI VMs (appliance managed by NSX) from some  random hosts were getting deleted automatically -  from the cluster that was protected with NSX. When I checked the windows logs (as vCenter was on windows server) this is what I saw -  I opened a case with VMware support - They reviewed the NSX logs and came to conclusion that this is not the NSX issue but it's vCenter that is deleting those VMs. vCenter gets disconnected for few seconds, then connects back. It doesn't recognizes those GI VMs and starts de...

How to Check Up Time of ESXi Host or Virtual Machine from vCenter Server

To check up time of ESXi host from vCenter server - Logon to vCenter Server -  If using C# (fat) client - click on cluster - on right side pane click on Hosts - select the up time option by right clicking on the header. The column will be added at the end. You can drag and drop column to place it in your view. If using HTML client - click on cluster - on right side pane click on Hosts - select the up time attribute from show/hide column by clicking on the header  If using web (Flash)  client - click on cluster - on right side pane click on related objects - hosts - right click on the header to show/hide column - click on up time attribute Similarly,  you can check the up time for a virtual machine by clicking on the virtual machine tab instead of host tab, but only caveat  is vCenter gives you up time of a virtual machine according to reboots performed from the vCenter. So, rather than rebooting server fr...

VMWare ESXi Host showing Up Time as 0 second

I have seen this more on 5.5 ESXi hosts but the host shows the up time as 0 seconds and CPU and Memory percentage as 0% Easiest way to resolve this is to put the host in maintenance mode and then restart the management agents on the ESXi hosts.  #esxcli services.sh restart But to be more cleaner I prefer to put host in maintenance mode and reboot the host to get the clean state.