-
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!
Configure a pattern set
To configure a pattern set, you must specify the strings that are to serve as patterns. You can manually assign a unique index value to each of these patterns, or you can allow the index values to be assigned automatically.
Note:
Pattern sets are case sensitive (unless you specify the expression to ignore case). Therefore, the string pattern “product1,” for example, is not the same as the string pattern “Product1.”
Points to remember about index values:
- You cannot bind the same index value to more than one pattern.
- An automatically assigned index value is one number larger than the highest index value of the existing patterns within the pattern set. For example, if the highest index value of existing patterns in a pattern set is 104, the next automatically assigned index value is 105.
- If you do not specify an index for the first pattern, index value 1 is automatically assigned to that pattern.
- Index values are not regenerated automatically if one or more patterns are deleted or modified. For example, if the set contains five patterns, with indexes from 1 through 5, and if the pattern with an index of 3 is deleted, the other index values in the pattern set are not automatically regenerated to produce values from 1 through 4.
- The maximum index value that can be assigned to a pattern is 4294967290. If that value is already assigned to a pattern in the set, you must manually assign index values to any newly added patterns. An unused index value that is lower than a currently used value cannot be assigned automatically.
Starting with NetScaler 14.1-12.x release, in addition to using a static string, you can also use an expression to derive the pattern set name and associate the pattern set in policy expression methods like CONTAINS_ANY, EQUALS_ANY, STARTSWITH_ANY. The pattern set name is dynamically derived from the expression and therefore reduces the number of policies that must be created for multiple pattern sets. By creating a dynamic pattern set, you can avoid repetitive configuration.
For example, in releases prior to NetScaler 14.1-12.x release, if there are four pattern sets, you have to create four policies to associate the four pattern sets. From NetScaler 14.1-12.x release onwards, in addition to using a static string, you can also use an expression to derive the pattern set name. The expression helps in reducing the configuration.
For the expression to identify the pattern set as part of its evaluation, you must configure the pattern set as dynamic using the dynamic keyword. The expression considers only those pattern sets that are configured as dynamic. If you have not configured the pattern set as dynamic at the time of pattern set creation, you can set it later as well. You can set dynamic keyword only for non-default pattern sets.
As part of the expression evaluation the following checks are performed:
- If there are no pattern sets that match the expression, then it is considered as an error and the error counter is incremented.
- If there is a pattern set name that matches the expression but it is not marked as dynamic, then it is considered as an error and the error counter is incremented.
Configure a pattern set by using the command line interface
At the command prompt, do the following:
-
Create a pattern set.
add policy patset <name>
Example:
add policy patset samplepatset
-
Bind patterns to the pattern set.
bind policy patset <name> <string> [-index <positive_integer>][-charset ( ASCII | UTF_8 )] [-comment <string>]
Example:
bind policy patset samplepatset product1 -index 1 -comment short description about the pattern bound to the pattern set
Note: Repeat this step for all the patterns you want to bind to the pattern set.
- Verify the configuration.
show policy patset <name>
Configure a pattern set by using the configuration utility
- Navigate to AppExpert > Pattern Sets.
- In the details pane, click Add to open the Create Pattern Set dialog box.
- Specify a name for the pattern set in the Name text box.
- Under Specify Pattern, type the first pattern and, optionally, specify values for the following parameters:
- Treat back slash as escape character—Select this check box to specify that any backslash characters that you might include in the pattern are to be treated as escape characters.
- Index—A user assigned index value, from 1 through 4294967290.
- Verify that you have entered the correct characters, and then click Add.
- Repeat steps 4 and 5 to add more patterns, and then click Create.
Configure a dynamic pattern set
Configure a dynamic pattern set using the CLI
At the command prompt, type the following commands:
-
Create pattern sets.
add policy patset <name> - dynamic yes -
Bind the patterns set to a pattern set.
bind patset <name> <string> -
Add a policy and use an expression instead of pattern set name.
add responder policy <name> <rule> <action> -
Verify the configuration.
show patset -dynamicOnly
Example for configuring dynamic pattern set using the CLI
Create CompA_pat and CompB_pat as the two dynamic pattern sets.
add policy patset CompA_pat -dynamic yes
bind policy patset CompA_pat stringA
add policy patset CompB_pat -dynamic yes
bind policy patset CompB_pat string B
<!--NeedCopy-->
Add a policy with an expression that derives the pattern set name dynamically:
add responder policy samplepolicy1 http.req.hostname.contains_any("Comp" + http.req.url.path.get(1) + "_pat") reset
Consider that http://www.citrix.com/A/home.html or http://www.google.com/B/test.html are the incoming URLs. Based on the incoming URL, the expression “Comp” + http.req.url.path.get(1) + “_pat”, determines the pattern set, CompA_pat or CompB_pat dynamically at the run time. You need not create two separate policies for CompA_pat and CompB_pat.
Verify the configuration using the show command:
> show patset -dynamicOnly
1) Patset: CompA_pat
2) Patset: CompB_pat
Done
<!--NeedCopy-->
Configure a dynamic pattern set using the GUI
- Navigate to AppExpert > Pattern Sets.
- Click Add to open the Create Pattern Set dialog box.
- Specify a name for the data set in the Name text box.
- Click Insert and specify the pattern in the Pattern field. Optionally, specify a value for the Index. Index is a user assigned value, from 1 through 4294967290.
- Verify that you have entered the correct characters, and then click Insert.
- Repeat steps 4 and 5 to add more patterns.
- Select the Dynamic check-box and then click Create.
- Navigate to AppExpert > Responder > Policies > Add.
- Create an expression that can derive the pattern set.
- Fill in the other mandatory fields and click Create.
Set, unset, or remove a dynamic pattern set
To set a non default pattern set as dynamic:
> set patset <name> -dynamic yes
Example:
> set patset CompA_pat -dynamic yes
Done
<!--NeedCopy-->
To unset a non default pattern set as dynamic
> unset patset <name> -dynamic
Example:
> unset patset CompA_pat -dynamic
Warning: [Dynamic attribute turned off. Expressions using this patset or dataset dynamically will not work.]
Done
<!--NeedCopy-->
To remove a dynamic pattern set
> rm patset <name>
Example:
> rm patset CompA_pat
Warning: [Dynamic patset or dataset removed. Expressions using this patset or dataset dynamically will not work.]
Done
<!--NeedCopy-->
Note:
When you unset or remove a dynamic patset, the expression that is using this pattern set does not work.
Configure file-based pattern sets
The NetScaler appliance supports file-based pattern sets.
Configure file-based pattern sets by using the CLI
At the command prompt, type the following commands:
-
Import a new pattern set file into the NetScaler appliance.
import policy patsetfile <src> <name> -delimiter <char> -charset <ASCII | UTF_8> <!--NeedCopy-->Example:
import policy patsetfile local:test.csv clientids_list –delimiter , <!--NeedCopy-->You can import a file from a local device, HTTP server, or FTP server. To add the file from your local device, the file must be available in
/var/tmplocation. -
Add a pattern set file to the packet engine.
add policy patsetfile <patset filename> <!--NeedCopy-->Example:
add policy patsetfile clientids_list <!--NeedCopy--> -
Update an existing pattern set file on the NetScaler appliance.
update policy patsetfile <patset filename> <!--NeedCopy-->Example:
update policy patsetfile clientids_list <!--NeedCopy--> -
Bind patterns to the pattern set.
add policy patset <patset name> -patsetfile <patset filename> <!--NeedCopy-->Example:
add policy patset clientid_patset -patsetfile clientids_list <!--NeedCopy--> -
Verify the configuration.
show policy patsetfile clientids_list Name: clientids_list Patset Name: clientid_patset Number of Imported Patterns: 8 Number of Bound Patterns: 8 (All the patterns bound successfully) Done <!--NeedCopy-->
Configure file-based pattern sets by using the GUI
-
Navigate to AppExpert-> Pattern Set Files.
-
In the Imported pane, click Import.
-
In the Configure Policy Patset File page, select the file you want to import, and click OK.
-
Select the imported file, and click Add.
-
In the Create Policy Patset File page, enter the details, and click Create to add a policy pattern set.
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.