Bug ID 451889: Omitting the attr_type from a RADIUS::avp command in an iRule results in an error.

Last Modified: Jul 18, 2026

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 hf1, 11.5.1 hf2, 11.5.1 hf3, 11.5.1 hf4, 11.5.1 hf5, 11.5.1 hf6, 11.5.1 hf7, 11.5.1 hf8, 11.5.1 hf9, 11.5.1 hf10, 11.5.1 hf11, 11.5.2, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10

Fixed In:
11.6.0

Opened: Mar 11, 2014

Severity: 4-Minor

Related Article: K15533

Symptoms

If one omits the optional attr_type from a RADIUS::avp command in an iRule, the iRule won't work and an error similar to the following is generated in /var/log/ltm: 11.4.0-Final - RADIUS::avp without attr_type resulted in TCL errors! Feb 20 15:25:11 B11000-R71-S12 err tmm1[13161]: 01220001:3: TCL error: /Common/radius_rule <CLIENT_ACCEPTED> - bad optional args "RADIUS::avp": must be index, vendor-id, or vendor-type while executing "RADIUS::avp 1"

Impact

One or more iRules using RADIUS::avp may no longer work.

Conditions

An iRule in version 11.4.0 or higher.

Workaround

Add in the attr_type after each RADIUS::avp command.

Fix Information

Made changes to once again allow the attr_type to be optional for all forms of RADIUS::avp.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips