-
Getting Started with NetScaler
-
Deploy a NetScaler VPX instance
-
Optimize NetScaler VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Apply NetScaler VPX configurations at the first boot of the NetScaler appliance in cloud
-
Configure simultaneous multithreading for NetScaler VPX on public clouds
-
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
-
-
Deploy a NetScaler VPX instance on AWS
-
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
-
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
-
Protect AWS API Gateway using the NetScaler Web Application Firewall
-
Configure a NetScaler VPX instance to use SR-IOV network interface
-
Configure a NetScaler VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Network architecture for NetScaler VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a NetScaler VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Deploy a NetScaler high-availability pair on Azure with ALB in the floating IP-disabled mode
-
Configure a NetScaler VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the NetScaler high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure a NetScaler VPX standalone instance on Azure VMware solution
-
Configure a NetScaler VPX high availability setup on Azure VMware solution
-
Configure address pools (IIP) for a NetScaler Gateway appliance
-
Deploy a NetScaler VPX instance on Google Cloud Platform
-
Deploy a VPX high-availability pair on Google Cloud Platform
-
Deploy a VPX high-availability pair with external static IP address on Google Cloud Platform
-
Deploy a single NIC VPX high-availability pair with private IP address on Google Cloud Platform
-
Deploy a VPX high-availability pair with private IP addresses on Google Cloud Platform
-
Install a NetScaler VPX instance on Google Cloud VMware Engine
-
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
-
-
-
-
-
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
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
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 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
-
Authentication and authorization for System Users
-
-
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)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
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.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
SNMP support for admin partitions
A partitioned NetScaler appliance uses the SNMP infrastructure for partition rate limiting and for monitoring partition resource utilization details.
SNMP traps for admin partition rate limiting
On a partitioned NetScaler appliance, a PARTITION-RATE-LIMIT alarm can generate nine SNMP traps for notifying a partition resource (such as bandwidth, connection, or memory) has reached its limit or returned to normal.
The following nine SNMP traps are generated when:
- partitionCONNThresholdReached. The number of active connections for a partition exceeds its high threshold percentage.
- partitionCONNThresholdNormal. The number of active connections is less than or equal to the normal threshold percentage.
- partitionBWThresholdReached. The partition’s bandwidth usage reaches its high threshold percentage.
- partitionMEMThresholdReached. The current memory usage of the partition exceeds its high threshold percentage.
- partitionMEMThresholdNormal. The current memory usage of the partition becomes less than or equal to the normal threshold percentage.
- partitionMEMLimitExceeded. The current memory usage of the partition exceeds its memory limit percentage.
- partitionCONNLimitExceeded. The number of active connections for a partition exceeds its configured limit and new connections are being dropped.
- partitionCONNLimitNormal. The number of active connections for a partition goes below its configured limit and the partition can now accept a new connection.
- partitionBWLimitExceeded. The current bandwidth usage for a partition has exceeded its configured limit.
The threshold values for the SNMP traps are non-configurable and are the following:
- High threshold = 80% (applicable for all partition rate limit traps)
- Low threshold = 60% (applicable for all partition rate limit traps)
- Memory limit = 95% (applicable only for partition memory traps)
Configuring PARTITION-RATE-LIMIT alarm
To configure the PARTITION-RATE-LIMIT alarm in a specific partition and enable generation of the SNMP trap messages.
- Enable PARTITION-RATE-LIMIT Alarm
- Configure PARTITION-RATE-LIMIT Alarm
- Configure SNMP Trap Destination
To enable PARTITION-RATE-LIMIT alarm by using the CLI
At the command prompt, type the following commands:
enable snmp alarm PARTITION-RATE-LIMIT
show snmp alarm PARTITION-RATE-LIMIT
To configure PARTITION-RATE-LIMIT Alarm by using the CLI
At the command prompt, type the following command:
set snmp alarm PARTITION-RATE-LIMIT \[-state \( ENABLED | DISABLED )] \[-severity <severity>] \[-logging \( ENABLED | DISABLED )]
To configure the SNMP trap destination by using the CLI
At the command prompt, type the following command:
add snmp trap <trapClass> <trapDestination> \[-version <version>] \[-td <positive\_integer>] \[-destPort <port>] \[-communityName <string>] \[-srcIP <ip\_addr|ipv6\_addr>] \[-severity <severity>] \[-allPartitions \( ENABLED | DISABLED )]
To configure the PARTITION-Rate-Limit alarm by using the GUI
Navigate to System > SNMP > Alarms, select PARTITION-RATE-LIMIT alarm, and configure the alarm parameters.
To configure the SNMP trap destination by using the GUI
Navigate to System > SNMP > Trap, specify the IP address of the destination device.
SNMP monitoring for partition resource utilization
Using SNMP, you can monitor a partition’s resource (such as bandwidth, connection, and memory) utilization details at real time on a NetScaler appliance. It is done by sending an SNMP request (such as SNMP GET, SNMP GET BULK, SNMP GETNEXT, or SNMP WALK) from the SNMP Manager.
Note
To monitor partition resources, you must configure the SNMP community in the default partition. Wherein, the partitionTable is maintained in the default partition, and the SNMP communication is done through the NSIP address of the appliance.
Consider a scenario where a NetScaler administrator wants to know the bandwidth usage of partition P1 on the appliance. The SNMP Manager retrieves this information by sending an SNMP GET request on the corresponding OID (partitionCurrentBandwidth) to the NSIP address of the appliance. The SNMP agent on the default partition retrieves and sends the current bandwidth usage of P1 to the SNMP Manager through the NSIP address.
The following table lists the SNMP counters which are part of partitionTable and its description:
SNMP Parameter | SNMP OID | Description |
---|---|---|
partitionName | 1.3.6.1.4.1.5951.4.1.1.88.1.1 | Partition name |
partitionCurrentBandwidth | 1.3.6.1.4.1.5951.4.1.1.88.1.2 | Current bandwidth usage of the partition. |
partitionCurrentConnections | 1.3.6.1.4.1.5951.4.1.1.88.1.3 | Current number of active connections of the partition. |
partitionMemoryUsagePcnt | 1.3.6.1.4.1.5951.4.1.1.88.1.4 | Current Memory usage (in percentage) of the partition. |
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.