NSX is deployed as a license entitlement for customers to apply to their infrastructure. SoftLayer supplies the licenses on a per-processor basis (pricing does not change for number of cores per CPU). An NSX license is required on every server that utilizes an NSX component (Management, Control, or Data Plane). NSX adds additional networking capabilities to the platform and allows for the creation of a robust overlay network for system security, tenant segmentation, and hybrid cloud environments that span providers or extend from on-prem private clouds.
Customers can add firewalls, load balancing, VPN, NAT services, VXLAN-based micro segmentation to their environment with support for automation through a RESTful API.
Licenses are added to the servers with the following process:
- Log in to vCenter Server with the vSphere Client.
- In the Home screen, under Administration, click Licensing.
- Click Solutions tab.
- In the product list, click VMware NSX for vSphere.
- Click License Key or Enter New license key.
- Click OK.
NSX Installation Steps
- Deploy NSX Manager
- Register NSX Manager with the vCenter Server
- vSphere Web Client is used to deploy the NSX Controller instances through NSX Manager.
- Prepare vSphere Hosts using the NSX Manager to install the VIBs on the hosts in the cluster.
- Once NSX Controllers have been deployed on all applicable Hosts define and configure the NSX Components such as Edge Gateways, Load Balancers, and Firewalls
Enabling NSX for a solution requires additional vSphere nodes beyond the standard compute nodes.
Virtual Appliance on Management Cluster in a 1:1 relationship with vCenter. Normal HA vSphere features recommended. NSX Manager includes scheduled/on-demand backup capabilities. It requires IP connectivity to vCenter, controller, NSX Edge
|NSX Release||vCPU||Memory||OS Disk|
|6.2 Large Scale||4||24GB||60GB|
NSX Controller Nodes
Deployed as virtual appliances from the NSX Manager UI. Each appliance communicates via a distinct IP address typically within the same subnet as the NSX manager, but not a hard requirement. It is recommended to deploy at least 3 controller VMs to at least 3 separate physical vSphere nodes. These act as active-active-active with job deliniation defined by the NSX Manager. When a node fails, a "majority rules" failover takes place to redistribute the workload to the remaining controllers. NSX does not natively enforce this design practice; leverage the native vSphere anti-affinity rules to avoid deploying more than one controller node on the same ESXi server. Typical VM sizing Per VM:
|Controller VMs||vCPU||Reservation||Memory||OS Disk|
An upgraded Virtual Distributed Switch (VDS) deployed to all hosts to implement distributed capabilities.
NSX Edge Services Gateway
Deployed as multi-function VM appliances as needed in the environment. For routing-only, an active cluster of up to 8 gateways can be deployed. For any/all other services, it is deployed in an active-standby deployment. Communications external to the VM environment will require SoftLayer assigned portable IPs. This includes any NAT pools, VIPs, and VPN endpoints.
|X-Large||6||8GB||Suitable for L7 High Performance LB|
|Quad-Large||4||1GB||Suitable for high performance ECMP and FW deployment|
|Large||2||1GB||Small DC & Single Service|
|Compact||1||512MB||Small Deployments or Single Service use or PoC|