Bug ID 533755: Required syntax for iRule command DIAMETER::avp create has changed

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
13.0.0

Opened: Jul 15, 2015

Severity: 3-Major

Symptoms

When saving an iRule which uses 'DIAMETER::avp create', if the command does not have a 'type' argument then a validation warning will be issued. In previous versions, this argument was optional.

Impact

Behavior of the command itself has not changed, and iRules using it will continue to function as expected. This is a change only in the validation of the command.

Conditions

This occurs when calls to 'DIAMETER::avp create' do not provide a 'type' argument.

Workaround

Review all iRules and ensure that calls to 'DIAMETER::avp create' provide a 'type' argument.

Fix Information

None

Behavior Change

When saving an iRule which uses 'DIAMETER::avp create', if the command does not have a 'type' argument then a validation warning will be issued. In previous versions, this argument was optional. Behavior of the command itself has not changed, and iRules using it will continue to function as expected. This is a change only in the validation of the command. You should review all iRules and ensure that calls to 'DIAMETER::avp create' provide a 'type' argument.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips