-
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 proxy support for outbound calls to IDP or third party endpoints
-
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
-
Configure protected user as an authentication factor in NetScaler nFactor authentication
-
Localize error messages generated by NetScaler nFactor system
-
Configure NetScaler Gateway preauthentication EPA scan for the domain check
-
-
-
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
Source IP address whitelisting for GSLB communication channels
-
Use case: Deployment of domain name based autoscale service group
-
Use case: Deployment of IP address based autoscale service group
-
-
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
-
-
-
-
Support for hybrid Post Quantum cryptography on the frontend
-
-
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!
Configuring policy extensions
When your policy extension file is ready, import it to the NetScaler appliance. The import process copies the extension file into a directory on the NetScaler appliance and checks for syntax errors.
After the import, you have to make the extension file available for use in the policy expressions.
Note:
- Use the
importcommand to download the file content from an external source\<src\>, or an internal source, onto the NetScaler file system.- Use the
addcommand to load the file content into one or more packet engines for the first time.- If the file content is updated, you can download the new content to the NetScaler file system by using the
importcommand with the overwrite argument.- Use the
updatecommand to load the updated content to one or more packet engines.
Configure policy extensions by using the CLI
-
Import the policy extension file to the NetScaler Appliance, from either a web server (using HTTP) or your local workstation.
-
HTTP Import
If you have a web server available, you can store the extension file in the webserver directory and import it to the NetScaler appliance.
import ns extension <src> <name> [-comment<string>] [-overwrite] <!--NeedCopy-->Example:
import ns extension http://myhost/path/to/extension myextension -comment "Custom crc calculation" <!--NeedCopy--> -
Local Import
You can use the SSH client to copy the extension file from your workstation to the
/var/tmpdirectory of the NetScaler appliancescp extension-file-name <ns-userid@ns-ip-addr>:/var/tmp <!--NeedCopy-->where,
-
extension-file-nameis the name of the extension file on your client machine. -
ns-useridis the NetScaler appliance user with permission to write to /var/tmp. -
ns-ip-addris the NetScaler IP address.
After copying the file to the NetScaler appliance, run the import command on the NetScaler appliance.
import ns extension local:<extension-file-name> <extension-name> <!--NeedCopy-->Note:
The CLI must be used to import a local extension file, by running the
importcommand. -
-
-
Add the policy extension to the packet engine for evaluation.
add ns extension <name> [-comment <string>] <!--NeedCopy-->Example:
add ns extension myextension <!--NeedCopy-->
After an extension file is imported, you can update it, if you included the -overwrite parameter in the import command, or remove it. You can also display the details of an imported extension file.
Update an extension file on the NetScaler appliance from the source
At the command prompt, type:
update ns extension <name>
<!--NeedCopy-->
Note:
You can update the extension file only after importing the specified extension file to the NetScaler appliance with the -overwrite parameter.
Example:
update ns extension myextension
<!--NeedCopy-->
Remove an extension file from the NetScaler appliance
At the command prompt type:
rm ns extension <name>
<!--NeedCopy-->
Example:
rm ns extension myextension
<!--NeedCopy-->
Display the details of the specified extension function on the NetScaler appliance
At the command prompt, type:
show ns extension <name>
<!--NeedCopy-->
Example:
show ns extension myextension
<!--NeedCopy-->
Configure policy extensions by using the GUI
-
Import the policy extension file to the NetScaler Appliance, from either a web server (using HTTP) or your local workstation.
-
Navigate to AppExpert > Policy Extensions, click Policy Extension, from the Import From drop-down list, select the URL for the location of the extension file that you want to import.
-
Navigate to AppExpert > Policy Extensions, and on the Policy Extension tab, import the extension file by selecting File in the Import From drop-down list.
-
-
Add the policy extension to the packet engine for evaluation.
Navigate to AppExpert > Policy Extensions, and on the Policy Extensions tab, add the extension file.
Update an extension file on the NetScaler appliance from the source
Navigate to AppExpert > Policy Extensions, and on the Policy Extensions tab, update the extension file.
Remove an extension file from the NetScaler appliance
Navigate to AppExpert > Policy Extensions, and on the Policy Extensions tab, remove the extension file.
Display the details of the specified extension function on the NetScaler appliance
Navigate to AppExpert > Policy Extensions, and on the Policy Extensions Functions tab, click the drop-down list arrow of the extension function that you want to see the details.
Share
Share
In this article
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.