tag-rule (HTTP Header Enrichment)
Syntax
tag-rule rule-name {
term term-number {
from {
destination-address {
(any-ipv4 | any-ipv4 except);
(any-ipv6 | any-ipv6 except);
(any-unicast | any-unicast except);
(prefix | prefix except);
}
destination-address-range {
high address low address <except>;
}
destination-port-range {
high port-number low port-number;
}
destination-ports value;
destination-prefix-list {
(prefix-name | prefix-name except);
}
}
then {
count;
tag tag-name {
encrypt {
hash algorithm;
prefix hash-prefix;
}
ipv4-mask ipv4-mask;
ipv6-mask ipv6-mask;
ipv4-or-value ipv4-or-value;
ipv6-or-value ipv6-or-value;
tag-attribute tag-attr-name;
tag-header header;
tag-separator separator;
}
}
}
}
Hierarchy Level
[edit services hcm]
Description
Configure the tag rules that enrich HTTP headers with the appropriate tags.
You must configure at least one term for a tag rule, but you
can configure multiple terms. Terms are evaluated in the order they
are configured. If a data packet matches all the criteria in the from statement in any of the terms, then the actions specified
in the then statement are applied. If the from statement does not identify any criteria, then all traffic matches.
After a term matches a data packet, further terms are not evaluated.
If no terms match, then the HTTP header is not enriched.
For subscriber traffic under static policy control, a tag rule is used if it is included in the HCM profile specified in a PCC rule that the traffic matches. For subscribers under dynamic policy control, a message from the PCRF identifies the configured HCM profile and tag rules to use for HTTP header enrichment.
Options
rule-name—Name
of the tag rule.
Range: 1 through 63 alphanumeric characters
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 16.1.