Bug ID 727288: Diameter MRF CER/DWR e2e=0, h2h=0 does not comply with RFC

Last Modified: Jun 04, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,,, 14.0.0,,,,,

Fixed In:
15.0.0, 14.1.0

Opened: Jul 09, 2018
Severity: 3-Major


Diameter message routing framework sends Capabilities-Exchange-Request (CER)/Device-Watchdog-Request (DWR) with hop-by-hop (h2h) ID and end-to-end (e2e) ID set to 0 as the server.


The BIG-IP system sends CER and DWR to remote peers. However, the BIG-IP system sends e2e=0 and h2h=0 as the server ID in the CER and DWR requests. This does not comply with RFC 6733 (https://tools.ietf.org/html/rfc6733).


Diameter Message Routing Framework (MRF) in use


Use an DIAMETER_EGRESS iRule event to change the hop-by-hop ID and end-to-end server ID.

Fix Information


Behavior Change