NetScaler Console service

FAQs and other resources

This section lists the reference documentations on configuring and operating Pooled licensing. You can refer to these documents for assistance related to configuration and operation issues.


  1. Where do I find information about the overview and features of Pooled capacity?

    Answer: See Configure Pooled capacity.

  2. How do I convert or migrate perpetual to Pooled licenses and the opposite way?

    Answer: Conversion from a perpetual license to a Pooled capacity license is a one-way license entitlement process. You cannot revert the Pooled capacity license back to perpetual.

  3. How do I deploy the NetScaler Console server?

    Answer: Follow the Getting started document.

  4. How do I add a license to an existing Pooled license and allocate it?

    Answer: Follow the License Management document.

  5. How do I allocate/increase capacity and bandwidth on instances?

    Answer: Follow the License Management document.

License Server Agent

  1. How do I assign the LSA role to a specific agent?

    Answer: The first agent deployed is assigned with the LSA role. If the LSA agent goes down, all the NetScaler instances connected to NetScaler Console for pooled licensing enter into a grace period for one day. The next day, NetScaler Console selects a new agent as the LSA. This behavior is enabled by default.

    Admins can manually select a NetScaler agent as an LSA within 24 hours, instead of waiting for the NetScaler Console service to auto-select an agent after 24 hours of the LSA being down.


    During this transition, NetScaler functionality is not impacted.

  2. How can we determine which agent hosts the License Server role?

    Answer: To know which agent is hosting the LSA role, you can run the following command in the shell:

    cat /mpsconfig/.lmp/agent

    If the output value for “role” is lsa, then that agent is hosting the license server role.

    Agent hosting LSA role

    In the NetScaler Console GUI, you see LSA written next to the IP address of the designated agent.

    Agent designated as LSA

  3. What happens when the agent hosting the LSA role goes down?

    Answer: If the agent hosting the LSA role is offline, all the deployed NetScaler devices configured for pooled capacity licensing go into grace period. The grace period lasts for 30 days and the resources allocated to the NetScaler devices persist through this period. NetScaler instances in this state cannot allocate or modify license allocation until the agent hosting the LSA role comes online again or a new agent with the LSA role is designated.

  4. If the agent hosting the LSA role goes offline for an extended period, will there be a re-election?

    Answer: If the admin does not select a new LSA within 24 hours, the NetScaler Console service automatically selects the next agent that is UP as the new LSA after 24 hours of the LSA agent being down. The grace period of the NetScaler devices ends after the new LSA is elected.

Common issues

  1. Instances running in grace mode due to connectivity failure, upgrade, split brain, and others.

    Answer: See the NetScaler Console license server behavior documented in Configuring NetScaler Pooled capacity.

  2. Licenses not applying or reflecting on instances.

    Answer: See Troubleshoot Pooled capacity license issues.

  3. License allocation is stuck in “sync in progress.”

    Answer: See Troubleshoot Pooled capacity license issues.

  4. Error due to wrong host ID on license file.

    Answer: To identify a NetScaler Console server, you can assign the server a host name. The host name is displayed on the Universal license for NetScaler Console. For more information, see Assign a host name to a NetScaler Console server.

FAQs and other resources