Bug ID 921441: MR_INGRESS iRules that change diameter messages corrupt diam_msg

Last Modified: May 29, 2024

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

Known Affected Versions:
15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3

Fixed In:
17.0.0, 16.1.3.1, 15.1.7

Opened: Jun 26, 2020

Severity: 3-Major

Symptoms

-- 'DIAMETER::host origin' command may not be set correctly. There are errors in ltm/log: err tmm[18562]: 014c0001:3: DIAMETER: hud_diam_handle error: Not found

Impact

Using the iRule to change the host origin corrupts the diameter message.

Conditions

-- Virtual server is configured with a diameter profile enabled with an ingress iRule, for example: ltm rule Diameter - iRule { when MR_INGRESS { DIAMETER:: host origin "hostname.realm.example" } } -- Traffic arrives containing CER and ULR messages.

Workaround

None.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips