-
Getting Started with NetScaler
-
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
-
Troubleshoot authentication, authorization and auditing issues
-
Configure EULA as an authentication factor in NetScaler nFactor system
-
Configure periodic Endpoint Analysis scan as a factor in nFactor authentication
-
Configure post-authentication Endpoint Analysis scan as a factor in NetScaler nFactor authentication
-
Configure pre-authentication Endpoint Analysis scan as a factor in nFactor authentication
-
Configure pre-auth and post-auth EPA scan as a factor in nFactor authentication
-
Configure prefill user name from certificate in NetScaler nFactor authentication
-
Localize error messages generated by NetScaler nFactor system
-
Configure NetScaler Gateway preauthentication EPA scan for the domain check
-
-
-
-
-
-
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
-
-
-
Monitor the free ports available on a NetScaler appliance for a new back-end connection
-
-
Configure to source NetScaler FreeBSD data traffic from a SNIP address
-
-
-
-
-
Create a certificate signing request and use SSL certificates on a NetScaler appliance
-
Configure SSL acceleration with HTTP on the front end and SSL on the back end
-
Export certificates used on a NetScaler appliance as PFX file
-
Configure SSL monitoring when client authentication is enabled on the back-end service
-
Configure SSL action to forward client traffic if a cipher is not supported on the ADC
-
Configure synchronization of files in a high availability setup
-
-
-
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!
Monitor the free ports available on a NetScaler appliance for a new back-end connection
For communication with the physical servers or other peer devices, the NetScaler appliance uses a Citrix owned IP address as the source IP address. The NetScaler appliance maintains a pool of its IP addresses, and dynamically selects an IP address while connecting with a server. Depending on the subnet in which the physical server is placed, the appliance decides which IP address to use. This address pool is used for sending traffic and monitor probes.
You can display the total number of free ports available on the NetScaler owned IP addresses for a new back-end connection. This information helps you in deciding the need for more NetScaler owned IP addresses if the free ports available are nearing exhaustion.
You can provide the following information for the NetScaler appliance to calculate the total number of free ports available for a new back-end connection:
- Citrix® owned IP address (optional)
- Destination IP address
- Destination port
- TCP or non-TCP protocol
When you specify all the information except specifying a Citrix owned IP address:
-
The NetScaler appliance performs a route lookup for finding all the NetScaler owned IP addresses that can connect to the destination IP address. The appliance then finds and displays the total number of free ports available on these NetScaler owned IP addresses for the specified new back-end connection.
Note:
The NetScaler appliance does not perform ECMP lookup, or LLB lookup path, or PBR lookup path for finding the NetScaler owned IP addresses that can connect to the destination IP address.
When you specify all the information including specifying a Citrix owned IP address:
- The NetScaler appliance displays the number of free ports available on the specified IP address for the specified new back-end connection.
Before you begin
Before you display the total number of free ports available for a new back-end connection, make note of the following points:
-
The NetScaler appliance does not perform ECMP lookup, or LLB lookup path, or PBR lookup path for finding the NetScaler owned IP addresses that can connect to the destination IP address.
-
The NetScaler appliance does not support displaying free ports available on a link local IP address.
Steps for displaying the number of free ports available on a NetScaler appliance for a new back-end connection
To display the total number of free ports available on a NetScaler appliance for a new back-end connection:
At the command prompt type:
|
ipv6_addr>] -destIP <ip_addr | ipv6_addr> -destPort |
Example - total number of free ports available on a standalone NetScaler appliance:
> show portallocation -destip 198.51.100.30 -destport 80 -protocol 1
Freeports available : 64505
Done
> show portallocation -srcip 192.0.2.30 -destip 198.51.100.30 -destport 80 -protocol 1
Freeports available for IPAddress 192.0.2.30 : 20505
Done
<!--NeedCopy-->
Example - total number of free ports available on a Cluster setup:
The following example output displays the total number of free ports available on each node of a two node cluster setup.
> show portallocation -destip 198.51.100.30 -destport 80 -protocol 1
Node Id: 1
Freeports available : 32321
Node Id: 0
Freeports available : 32184
Done
<!--NeedCopy-->
Monitor the ports usage on a NetScaler appliance for back-end connections using SNMP
You can use the PORT-ALLOC-EXCEED SNMP alarm to monitor the ports usage on a NetScaler appliance for back-end connections.
PORT-ALLOC-EXCEED SNMP alarm includes the high-threshold and normal-threshold parameters, which specify the total allocated ports of the NetScaler owned IP addresses as percentages. For example, if the high-threshold parameter is set to 90, the NetScaler appliance generates and sends trap messages when the following event happens:
- when the port allocation percentage exceeds 90 percent on any of the NetScaler owned IP address for the back-end connections
The SNMP alerts help you in deciding the need for more NetScaler® owned IP addresses if the free ports available are nearing exhaustion.
To Monitor the ports usage on a NetScaler appliance for back-end connections using SNMP
At the command prompt type:
|
DISABLED ) -severity |
DISABLED ) -thresholdValue |
- sh snmp alarm PORT-ALLOC-EXCEED
Example:
> set snmp alarm PORT-ALLOC-EXCEED -logging ENABLED -severity Major -state ENABLED -thresholdValue 90 -time 1200
Done
> sh snmp alarm port-alloc-EXCEED
Alarm Alarm Threshold Normal Threshold Time State Severity Logging
----- --------------- ---------------- ---- -------- ------------- --------
1) PORT-ALLOC-EXCEED 80 80 7200 ENABLED Major ENABLED
Done
<!--NeedCopy-->
For more information on configuring SNMP alarms and SNMP trap listeners, see Configuring the NetScaler to generate SNMP traps.
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.