Bug ID 710996: VIPRION outgoing management IPv6 traffic from primary blade uses the cluster member IP

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,,,,,,,, 14.0.0,,,,,, 14.0.1,

Fixed In:

Opened: Mar 20, 2018
Severity: 3-Major


The behavior of outgoing IPv6 management and IPv4 management traffic from the primary blade differs: IPv4 traffic is sourced from the cluster IP IPv6 traffic is sourced from the cluster member IP


The blade IP address, rather than the cluster floating IP, will be used as the source IP when querying the RADIUS server for remote-auth login against the management port.


IPv6 configured on the 'cluster' address and 'cluster member' address.


There is no workaround at this time.

Fix Information


Behavior Change