-
Getting Started with Citrix NetScaler
-
Deploy a Citrix NetScaler VPX instance
-
Install a NetScaler VPX instance on Microsoft Hyper-V servers
-
Install a NetScaler VPX instance on Linux-KVM platform
-
Prerequisites for Installing NetScaler VPX Virtual Appliances on Linux-KVM Platform
-
Provisioning the NetScaler Virtual Appliance by using OpenStack
-
Provisioning the NetScaler Virtual Appliance by using the Virtual Machine Manager
-
Configuring NetScaler Virtual Appliances to Use SR-IOV Network Interface
-
Configuring NetScaler Virtual Appliances to use PCI Passthrough Network Interface
-
Provisioning the NetScaler Virtual Appliance by using the virsh Program
-
Provisioning the NetScaler Virtual Appliance with SR-IOV, on OpenStack
-
Configuring a NetScaler VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
-
-
Upgrade and downgrade a NetScaler appliance
-
-
-
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Use source IP address of the client when connecting to the server
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
-
Use case 3: Configure load balancing in direct server return mode
-
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
-
Use case 7: Configure load balancing in DSR mode by using IP Over IP
-
Use case 10: Load balancing of intrusion detection system servers
-
Use case 11: Isolating network traffic using listen policies
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
-
Configuring CloudBridge Connector between Datacenter and AWS Cloud
-
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
-
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
-
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.
Este artigo foi traduzido automaticamente.
这篇文章已经过机器翻译.放弃
Translation failed!
Extra management CPU
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.
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.
- 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
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.