- Integrating NetScaler MAS with NSX Manager by Manual Provisioning
- Integrating NetScaler MAS with NSX Manager by Auto-provisioning
- NetScaler Automation Using NetScaler MAS in Cisco ACI’s Hybrid Mode
NetScaler Management and Analytics System (MAS) integrates with VMware network virtualization platform to automate the deployment, configuration, and management of NetScaler services. This integration abstracts away the traditional complexities associated with physical network topology, enabling vSphere/vCenter admins to programmatically deploy NetScaler services faster.
During load-balancing service insertion and deletion on VMware NSX Manager, NetScaler MAS dynamically provisions and destroys the NetScaler instances. This dynamic provisioning requires the NetScaler VPX license assignments to be automated in NetScaler MAS. When the NetScaler licenses are uploaded to the NetScaler MAS, NetScaler MAS performs the role of license server.
To provision the NetScaler MAS HA setup, install the NetScaler MAS image file that you have downloaded from the Citrix download site. For more information on how to provision NetScaler MAS HA set up, see Deploying NetScaler MAS in High Availability.
To integrate VMware NSX manager with NetScaler MAS that is deployed in a HA mode, you must first enter the virtual IP address of the load balancing NetScaler instance. You must also upload the certificate file that is present on the NetScaler load balancing virtual server to the NetScaler MAS file system.
To provide load balancing configuration information in NetScaler MAS
1. In NetScaler MAS HA node, navigate to System > Deployment.
2. Click HA Settings in the top-right corner, and in MAS-HA Settings page, click MAS-HA Endpoint Details.
3. On MAS-HA Endpoint Details page, upload the same certificate that is already present on the load balancing NetScaler instance.
4. Enter the virtual IP address of the load balancing NetScaler instance and click OK.
When you set up two NetScaler MAS servers in high availability, the two server nodes are in active-passive mode. Log on to the primary NetScaler MAS server node to register VMware NSX manager with NetScaler MAS in HA, to create a communication channel between them.
To register VMware NSX manager with NetScaler MAS in HA
Upload the NetScaler VPX licenses to NetScaler MAS, so that NetScaler MAS can automatically assign licenses to the instances during orchestration with NSX.
To install license files on the NetScaler Management and Analytics System
Note: At any time, you can add more licenses to the NetScaler MAS from the License Settings.
Add the NetScaler images to NetScaler MAS, so that the NetScaler MAS uses these images as defined in the service package.
To upload NetScaler VPX Images in NetScaler MAS
Create service packages in NetScaler MAS to define the set of SLAs, which states how the NetScaler resources are allocated.
To create service packages in NetScaler MAS
Note: In High Availability section, check the box to provision NetScaler instances for HA.
The name of license displayed in the drop-down box shown in the figure above, VPX8000_Enterprise, 2number is an example and is explained as below:
The name of license displayed in the License drop-down box depends on the license that you have purchased from Citrix.
4. Click Continue.
5. The service package is published to NSX Manager. In NSX Manager, navigate to Service Definitions > Service Managers. You can view Citrix NetScaler MAS as one of the service managers. This indicates that the registration is successful and bi-directional communication is established between the NSX manager and NetScaler MAS.
Note: For NetScaler MAS in high availability deployment, the licenses are uploaded only in the NetScaler MAS license server node. Note that the NetScaler MAS nodes are in an active-passive mode.
Perform load balancer service insertion on the existing NSX Edge Gateway, that is, offload the load balancing function from NSX load balancer to NetScaler.
To insert load balancing service on NSX Edge Gateway
1. In NSX Manager, navigate to Home > Networking and Security > NSX Edges, and double-click to select the edge gateway that you have configured.
2. Click Manage, and on the Load Balancer tab, select Global Configuration, and click Edit.
3. Select Enable Load Balancer and Enable Service Insertion to enable them.
4. In Service Definition, select the service package that was published to NSX Manager.
5. Configure one virtual NIC for management interface, and one or more virtual NICs for data interfaces. Select the networks for management and data accordingly.
Note: Select IP Pool option in Primary IP Allocation mode. NetScaler MAS does not support manual or DHCP allocation of IP addresses.
6. Click the refresh icon to see the creation of the run time.
Note: Because you are deploying two NetScaler VPX instances in HA deployment, two run times are created in the NSX manager.
Note: You might have to refresh the screen to view the run times displayed on the screen.
7. Select the run time, click Actions, and select Install from the pop-up menu. For HA, repeat this for the other run time also.
8. When both the virtual machines start, the value of Status changes to "In Service" and that of Install State changes to "Enabled."
Note: You might have to refresh the screen to view the change in status.
9. In NetScaler MAS, navigate to Orchestration > Requests to see progress details of completion of service insertion. You can see that a request to create and update the run time has come in to NetScaler MAS. When the run time has been updated, select the request and click the Tasks button to view that NetScaler MAS has been added in NSX Manager.
For HA, there will be two requests to create and update two run times in NetScaler MAS. When both run times have been updated, select both requests and click the Tasks button to view that two NetScaler MAS HA nodes have been added in NSX Manager.
10. In NetScaler MAS, navigate to Orchestration > SDN Orchestration > VMware NSX Manager > Edge Gateways. In the right-hand side panel, you can view that the NetScaler VPX has been added to the NSX Edge Gateway.
For HA, you can see that two NetScaler VPX instances in HA mode have been added to the NSX Edge Gateway.
11. In NetScaler MAS, navigate to Networks > Licenses >VPX Licenses. Select the NetScaler VPX license and the edition that you have installed.
The NetScaler VPX instances that are in HA mode consume two licenses and the status is displayed on your screen as below.
When the service insertion is complete, you can use StyleBooks to configure the NetScaler instances in one of the following two methods:
Perform the following task to enable configuration of load balancing services on the NSX Edge gateway device using built-in StyleBooks.
As a prerequisite, add the two StyleBooks - nsx-root-params and nsx-lb-mon, to the list of shipped StyleBooks present in NetScaler MAS using the command line tool:
To add the StyleBooks to the list of shipped StyleBooks
4. Restart NetScaler MAS services by entering the "masd" restart command.
Make sure that the two StyleBooks are added in the shipped StyleBooks list before creating pools, members, and virtual servers on VMware NSX Manager GUI.
In NSX Manager, navigate to Home > Networking and Security > NSX Edges, and double-click to select the edge gateway that you have configured.
Create a pool of servers and members of different capacities.
Add as many members as required.
Create a set of virtual servers and assign a pool to each virtual server.
3. In NetScaler MAS, navigate to Orchestration > Requests to see progress details of completion of service creation on the selected NetScaler instance(s).
4. In NetScaler MAS, navigate to Applications > Configuration, and check that the "nsx-lb-mon" config pack has been created.
To create configuration packs through StyleBooks
You can view that the service groups and virtual servers are created by loogin on to the NetScaler VPX instance.
To view the service groups and virtual servers
When the load balancing services are no longer required on the NetScaler VPX instances deployed on the NSX manager, you can delete the service insertions that were performed earlier.
To delete configuration and service insertion