In NetScaler 12.0
In Citrix ADC
In All products
Product Documentation
In NetScaler 12.0
In Citrix ADC
In All products
NetScaler 13.0 NetScaler 12.1 NetScaler 12.0 NetScaler 11.1 NetScaler 10.5
View PDF

Extra management CPU

January 6, 2019
Contributed by:  S S

If you need better performance for configuration and monitoring of a NetScaler MPX appliance, you can allocate an extra management CPU from the appliance’s packet engine pool. This feature is supported on certain NetScaler MPX models and all VPX models except the VPX instances that run on NetScaler SDX appliances. It affects the output of the stat system cpu and stat system commands.

Supported NetScaler MPX models:

  • 25xxx
  • 22xxx
  • 14xxx
  • 115xx
  • 15xxx
  • 26xxx

Note

For NetScaler MPX 26xxx models with more than 20 cores,  the mandatory extra management CPU feature is enabled by default. For NetScaler VPX models, a license that supports atleast 12 vCPUs is required to enable this feature.

Allocate or deallocate an extra management CPU by using the NetScaler CLI

At the command prompt, type one of the following commands:

  • enable extramgmtcpu
  • disable extramgmtcpu

Note

After you enable and disable this feature, the NetScaler appliance displays a warning to restart the appliance, for the changes to take effect.

To show the configured and effective state of an extra management CPU.

At the command prompt, type:

`show extramgmtcpu`

Example

    > show extramgmtcpu


    ConfiguredState:  ENABLED EffectiveState:  ENABLED

Note

In this example, the show command is entered before restarting the appliance.

Parameter descriptions of commands listed in the command line interface

  • enable extramgmtcpu

Enables and dedicates extra CPU for management from PE pool.

See also:

disable system extramgmtcpu

show system extramgmtcpu

  • disable extramgmtcpu

Disables extra CPU for management and returns it to the PE pool.

See also:

enable system extramgmtcpu

show system extramgmtcpu

  • show extramgmtcpu

Displays configured and effective states of the extra management CPU.

Configured and effective state are different if enable extramgmtcpu command has been entered but system is has not been restarted.

See also:

enable system extramgmtcpu

disable system extramgmtcpu

Allocate an extra management CPU by using the GUI

To allocate an extra management CPU by using the GUI, navigate to System > Settings and click Configure Extra Management CPU. From the Configured State drop-down menu, select Enabled and then select OK.

localized image

To check CPU usage, go to System > Settings > Dashboard.

Configure an extra management CPU by using the NITRO API

Use the following NITRO methods and formats to enable, disable, and show an extra management CPU.

To enable an extra management CPU:

HTTP Method: POST

URL: http://<NSIP>/nitro/v1/config/systemextramgmtcpu?action=enable

Payload: {"systemextramgmtcpu":{}}

    curl -v -X POST -H "Content-Type: application/json" -u nsroot:nsroot http://10.102.201.92/nitro/v1/config/systemextramgmtcpu?action=enable -d '{"systemextramgmtcpu":{}}'

To disable an extra management CPU

HTTP Method: POST

URL: http://<NSIP>/nitro/v1/config/systemextramgmtcpu?action=disable

Payload: {"systemextramgmtcpu":{}}

    curl -v -X POST -H "Content-Type: application/json" -u nsroot:nsroot http://10.102.201.92/nitro/v1/config/systemextramgmtcpu?action=disable -d '{"systemextramgmtcpu":{}}'

To show an extra management CPU

HTTP Method: GET

URL: http://<NSIP>/nitro/v1/config/systemextramgmtcpu

Example

    curl -v -X GET -H "Content-Type: application/json" -u nsroot:nsroot http://10.102.201.92/nitro/v1/config/systemextramgmtcpu

Statistics and monitoring

The following examples show the differences in the output of the stat system cpu and stat system commands before and after adding an extra management CPU.

  1. stat system cpu

This command displays statistics of CPUs.

Here is a sample output before adding an extra management CPU on one of the supported models.

Example output

    > stat system cpu

    CPU statistics

    ID         Usage

    8              1

    7              1

    11             2

    1              1

    6              1

    9              1

    3              1

    5              1

    4              1

    10             1

    2              1

Here is the output after adding an extra management CPU on the same MPX appliance.

    > stat system cpu

    CPU statistics

    ID         Usage

    9              1

    7              1

    5              1

    8              1

    11             2

    10             1

    6              1

    4              1

    3              1

    2              1

2. stat system

This command displays CPU use. In the following example, the output before adding an extra management CPU on one of the supported models is:

Mgmt Additional-CPU  usage (%)      0.00

Example output

    > stat system

    NetScaler Executive View

    System Information:

    Up since        Wed Oct 11 11:17:54 2017

    /flash Used (%)                        0

    Packet CPU usage (%)                1.30

    Management CPU usage (%)            4.00

    Mgmt CPU0 usage (%)                 4.00

    Mgmt Additional-CPU  usage (%)      0.00

    Memory usage (MB)                   2167

    InUse Memory (%)                    5.76

    /var Used (%)                          0

In the following example, the output after adding an extra management CPU on the same MPX appliance is:

Mgmt Additional-CPU  usage (%)      0.80

    > stat system

    NetScaler Executive View

    System Information:

    Up since        Wed Oct 11 11:55:56 2017

    /flash Used (%)                        0

    Packet CPU usage (%)                1.20

    Management CPU usage (%)            5.70

    Mgmt CPU0 usage (%)                10.60

    Mgmt Additional-CPU  usage (%)      0.80

    Memory usage (MB)                   1970

    InUse Memory (%)                    5.75

    /var Used (%)                          0

Extra management CPU

January 6, 2019
Contributed by:  S S

In this article

Edit this article