Bug ID 753637: Diameter MBLB profile does not change the hop-by-hop ID by default

Last Modified: Sep 14, 2023

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

Known Affected Versions:
13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6

Fixed In:
15.0.0

Opened: Dec 19, 2018

Severity: 3-Major

Symptoms

The Diameter MBLB profile does not change the hop-by-hop ID.

Impact

The hop-by-hop ID is not changed.

Conditions

Diameter MBLB virtual server.

Workaround

None.

Fix Information

The Diameter MBLB profile can now change the hop-by-hop id when enabled by the db key Diameter.mblb.hopid_replace to enable.

Behavior Change

There is a new db key 'Diameter.mblb.hopid_replace' that you can enable to automatically set the hop-by-hop ID.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips