NSX Manager & NSX Controller

[hs77]

vNiC's of NSX Manager and NSX Controller are attached to which Port Groups.

Are they VMkernel Management Port Groups or Virtual Machine Port Groups.

[SRoland]

It must be Virtual Machine port-group, but from the question it seems that you are about to use standard vSwitch, where the option to chose it is valid.

I would rather recommend to use distributed switch to get all available NSX functions and features if you have the possibility ( i.e. licensed )

For additional help please the NSX Virtualization and Design Guide

HTH

[hs77]

I will be using Distributed switch only.

[admin]

NSX Manager and Controllers are regular VMs, connected to regular dvPg.

[hs77]

Dmitrik when i use NSX HOL 1403 i see controller VMs connected Distributed Management VMkernel Port Group.

[admin]

There is no requirement for them to be so; in fact this is the first time I'm hearing about such configuration.

All deployments I've seen had Manager and Controllers on regular dvPortgroups; typically Management, since Controllers and NSX Manager need to be able to reach each other and all hosts' vmk0 interfaces via IP.

[alsmaster]

Totally agree with DimitriK.  NSX Manager and NSX Controllers are VMs and can only connect to a dvPort Group and not a VMkernel Port Group.

[hs77]

My point is that they are connecting to dvport group only. But this dvport group is VMkernel Port Group and Not VM Port group. Thats what I am saying.

[writeerasereloa]

NSX manager is a virtual machine and should be attached to a Virtual Machine port group. According to the documentation it does not specify a requirement or preference for either a standard or distributed switch. NSX Manager just needs connectivity to the vCenter Server, ESXi host, and NSX Edge instances, vShield Endpoint module, and NSX Data Security virtual machine.

VMware recommends that you install NSX Manager on a dedicated management cluster separate from the cluster(s) that NSX Manager manages. Each NSX Manager manages a single vCenter Server environment. The NSX Manager requires connectivity to the vCenter Server, ESXi host, and NSX Edge instances, vShield Endpoint module, and NSX Data Security virtual machine. NSX components can communicate over routed connections as well as different LANs. 

The NSX Manager should be run on an ESX host that is not affected by downtime, such as frequent reboots or maintenance mode operations. You can use HA or DRS to increase the resilience of the NSX Manager. If the ESX host on which the NSX Manager resides is expected to require downtime, vMotion the NSX Manager virtual appliance to another ESX host. Thus, more than one ESX host is recommended.

Ensure that the following ports are open:

■	Port 443/TCP from, to, and among the ESX host, the vCenter Server, and NSX Data Security
■	443/TCP from the REST client to NSX Manager for using REST API calls
■	80/TCP and 443/TCP for using the NSX Manager user interface and initiating connection to the vSphere SDK

NSX 6 Documentation Center

[admin]

I understand, and I'm saying that the configuration you're seeing is incorrect.

NSX Manager and Controllers should be connected to a regular dvPg (NSX Manager isn't visible here, but it would be on the same dvPg in a normal environment):

[hs77]

I see Controller VMs are connected to "Mgmt_Edge_VDS-Mgmt" Port Group. This is a Management VMkernel Port Group. I have checked this number of times.

Inventories>Host & Clusters. Expands Host section. select "esx-01a.corp.local" and double click it.

Manage Tab>Networking>VMKernel adpators. You will see "Mgmt_Edge_VDS-Mgmt" Port Group as VMk0.

[admin]

In my screenshot vdPg name is "Mgmt_Edge_VDS - VM Mgmt", not "Mgmt_Edge_VDS - Mgmt" (note the missing "VM" in dvPg name).

vmk0 is connected to the different dvPg.

In old labs Mgmt_Edge_VDS - Mgmt was used to connect both vmk0 and Controllers; but that doesn't make dvPg "Mgmt_Edge_VDS - Mgmt" any "special". You can mix vmkX and regular VMs on the same dvPg, but for NSX it's not a requirement for NSX Manager or Controllers to be connected to the same dvPg where there are any connected vmkX adapters.

[hs77]

You go to VM and Templates and select any one of the controller VM.

Click Manage Tab>Settings>VM Hardware.

Network Adaptor 1 is connected to Mgmt_Edge_VDS - Mgmt

See the image below. Click it and you will see clear and bigger image.

( I am talking of HOL-SDC-1403)

[rbudavari]

There is no concept of a virtual machine portgroup vs VMkernel portgroup on the VDS - both VM vnics and VMkernel vmknics can connect to dvPorts on the same portgroups. While it is common to dedicate networks for VMkernel management (vmk0) compared to VM management this is not a requirement.

[hs77]

I don't agree with your statement 'There is no concept of a virtual machine portgroup vs VMkernel portgroup on the VDS"

in vDS we create Virtual machine Port Group Centrally once and VMkernel Port Group are created individually on each host.

Anyhow leave this point.

You mean to say we can connect vNIC of NSX Controller to the VMK0 Port group as it is in HOL 1403.

[rbudavari · Accepted solution]

We might be confusing the terminology - it is the VMkernel adapters that are created locally on each host (not the portgroup). Anyway let's move on as you suggest.

Yes, it is possible to use the same portgroup for the NSX Controller or other management VM vNICs as per the HOL.

[hs77]

Thanks for the clarification.

But when we create VMkernel Adaptors on a host a corresponding Port group is created in vDS.

[rbudavari]

That is true for the Standard vSwitch (even there technically it is a port not a portgroup) - on the VDS you are asked for an existing distributed portgroup. The details aren't that important though