Product Documentation

Configuring Nodegroups for Spotted and Partially-Striped Configurations

Aug 31, 2016
To configure a nodegroup for spotted and partially-striped configurations you must first create a nodegroup and then bind the required nodes to the nodegroup. You must then associate the required entities to that nodegroup. The entities that are bound to the nodegroup will be:
  • Spotted - If bound to a nodegroup that has a single node.
  • Partially striped - If bound to a nodegroup that has more than one node.
Some points to remember:
  • GSLB is supported on a cluster only when GSLB sites are bound to nodegroups that have a single cluster node. For more information, see Setting Up GSLB in a Cluster.
  • NetScaler Gateway is supported on a cluster only when the VPN virtual servers are bound to nodegroups that have a single cluster node. The sticky option must be enabled on the nodegroup.
  • For versions prior to NetScaler 11, application firewall is supported only on individual cluster nodes (spotted configuration). Application firewall profiles can be associated only with virtual servers that are bound to nodegroups that have a single cluster node. This means that application You are not allowed to do the following:
    • Bind application firewall profiles to striped or partially striped virtual servers.
    • Bind the policy to a global bind point or to user-defined policy labels.
    • Unbind, from a nodegroup, a virtual server that has application firewall profiles.
  • NetScaler 11 introduced application firewall support for striped and partially-striped configurations. For more information, see Application Firewall Support for Cluster Configurations.

Check NetScaler Features Supported in a Cluster to see the NetScaler versions from which GSLB, NetScaler Gateway, and application firewall are supported in a cluster.

To configure a nodegroup by using the command line interface

  1. Log on to the cluster IP address.
  2. Create a nodegroup. Type:

    add cluster nodegroup <name> -strict (YES | NO)

    Example
    > add cluster nodegroup NG0 -strict YES
  3. Bind the required nodes to the nodegroup. Type the following command for each member of the nodegroup:

    bind cluster nodegroup <name> -node <nodeId>

    Example: To bind nodes with IDs 1, 5, and 6.
    > bind cluster nodegroup NG0 -node 1 
    > bind cluster nodegroup NG0 -node 5 
    > bind cluster nodegroup NG0 -node 6
  4. Bind the entity to the nodegroup. Type the following command once for every entity that you want to bind:

    bind cluster nodegroup <name> (-vServer <string> | -identifierName <string> | -gslbSite <string> -service <string>)

    Note: The gslbSite and service parameters are available from NetScaler 10.5 onwards.
    Example: To bind virtual servers VS1 and VS2 and rate limit identifier named identifier1.
    > bind cluster nodegroup NG0 -vServer VS1 
    > bind cluster nodegroup NG0 -vServer VS2 
    > bind cluster nodegroup NG0 -identifierName identifier1
  5. Verify the configurations by viewing the details of the nodegroup. Type:

    show cluster nodegroup <name>

    Example
    > show cluster nodegroup NG0

To configure a nodegroup by using the configuration utility

  1. Log on to the cluster IP address.
  2. Navigate to System > Cluster > Node Groups.
  3. In the details pane, click Add.
  4. In the Create Node Group dialog box, configure the nodegroup:
    1. Under Cluster Nodes, click the Add button.
      • The Available list displays the nodes that you can bind to the nodegroup and the Configured list displays the nodes that are bound to the nodegroup.
      • Click the + sign in the Available list to bind the node. Similarly, click the - sign in the Configured list to unbind the node.
    2. Under Virtual Servers, select the tab corresponding to the type of virtual server that you want to bind to the nodegroup. Click the Add button.
      • The Available list displays the virtual servers that you can bind to the nodegroup and the Configured list displays the virtual servers that are bound to the nodegroup.
      • Click the + sign in the Available list to bind the virtual server. Similarly, click the - sign in the Configured list to unbind the virtual server.