Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
attribute must be one of the following:
|
|
|
Important: This attribute is customer specific, and is only available in Release 8.3 and later releases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Important: This attribute is customer specific, and is only available in Release 8.3 and later releases.
|
|
Important: This attribute is customer specific, and is only available in Release 8.3 and later releases.
|
|
|
|
Important: This attribute is customer specific, and is only available in Release 8.3 and later releases.
|
|
Important: This attribute is customer specific, and is only available in Release 8.3 and later releases.
|
|
Important: This attribute is customer specific, and is only available in Release 8.3 and later releases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Important: This attribute is customer specific, and is only available in ‘ 8.3 and later releases.
|
|
|
|
Important: This attribute is customer specific, and is only available in Release 8.3 and later releases.
|
|
|
|
Unique sequence number (per sn-sequence -group and radius-nas-ip-address) of UDR identifier and linearly increasing in UDR file.
|
|
|
|
|
|
Important: This attribute is interchangeable with radius-nas-ip-address for other systems.
|
|
|
|
Important: This attribute is customer specific, and is only available in Release 8.3 and later releases.
|
|
|
|
|
|
Important: This attribute is customer specific, and is only available in Release 8.3 and later releases.
|
priority must be an integer from 1 through 65535. Up to 50 position priorities (across all
attribute,
event-label, and
rule-variable) can be configured.
A particular field in UDR format can be entered multiple times at different priorities. While removing the UDR field using the no attribute command either you can remove all occurrences of a particular field by specifying the field name or a single occurrence by additionally specifying the optional
priority keyword.
label must be an alpha and/or numeric string of 1 through 63 characters in length.
priority must be an integer from 1 through 65535.
protocol must be one of the following with specified rule:
priority must be an integer from 1 through 65535.
A particular field in UDR format can be entered multiple times at different priorities. While removing the UDR field using the no rule-variable command either you can remove all occurrences of a particular field by specifying the field name or a single occurrence by additionally specifying the optional priority keyword.