-
AppExpert Applications and Templates
-
Configure application authentication, authorization, and auditing
-
-
Advanced Policy Expressions: Working with Dates, Times, and Numbers
-
Advanced Policy Expressions: Parsing HTTP, TCP, and UDP Data
-
Advanced Policy Expressions: IP and MAC Addresses, Throughput, VLAN IDs
-
-
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 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.
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 file-based pattern sets
The Citrix ADC 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 Citrix ADC 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/tmp
location. -
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 Citrix ADC 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.