Thursday, 10 September 2015

NSX Controller

NSX Controller serves as the central control point for all logical switches within a network and maintains information about all hosts, VXLANs and Distributed Logical Routers.

NSX Controllers are required if we are planning to deploy:
1. Distributed Logical Router
2. VXLAN using Unicast mode and Hybrid mode.

NSX Controller cluster contain Maximum or Minimum 3 controller node.

Their are few roles, which should be perform by these node.

1. API Provider: Used to handle HTTP web service requests from external clients (handles northbound REST API traffic) and initiates processing by other controller node task.
To configure the listen-ip we can use the following command.

set control-cluster role switch_manger listen-ip <IP address>

2. Persistence Server: stores data from the Network Virtualization Platform (NVP) API and vDS devices that must be persisted across all controller nodes in case of node failures or shutdowns.

3. Logical Manager: Monitors when end hosts arrive or leave vDS devices (such as host joining VXLAN VTEP,UTEP,MTEP) and configures the vDS forwarding states to implement logical connectivity and policies.

4. Switch Manager: Maintains management connections for one or more vDS devices.

5. Directory Server: manage VXLAN and the distributed logical routing directory of information.

run the following command to find which host is master node for each role: "Show control-cluster roles"


this result shows that a single controller cluster node is master for all the roles.

If master NSX controller instance for a role fails, the cluster elects a new master for that role from the available NSX controller instances.

NSX controller instances are on the control plane, so an NSX controller failure does not affect data plane traffic.

1 comment: