Bug ID 587707: Traffic group in Message Routing profile must match traffic group in Virtual Address

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
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,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,

Opened: Apr 14, 2016
Severity: 3-Major


If the virtual address for a virtual server that uses a message router profile (SIPRouter, DiameterRouter, MessageRouter) uses a different traffic group than the router profile, after failover, the wrong device will respond to ARP requests.


Connection failover may not work as the wrong device will respond to ARP requests after failover.


The virtual address for a virtual server containing a message router profile has a different traffic group selected than the router profile.


Manually ensure the traffic group for all virtual addresses matches the router profile used by the virtual servers that use the virtual address.

Fix Information


Behavior Change