Bug ID 434211: Cluster IP address not included in IP routing table on primary blade

Last Modified: Nov 22, 2021

Bug Tracker

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

Known Affected Versions:
11.4.0, 11.4.1

Fixed In:
11.4.0 HF6

Opened: Oct 16, 2013
Severity: 2-Critical
Related Article:
K15257

Symptoms

The primary blade in a clustered system may send management traffic sourced from the blade IP address associated with the management port instead of from the cluster IP address. In addition, traffic sourced from the management interface of a VCMP guest may fail with an ICMP 'destination unreachable' message.

Impact

Services that receive traffic from the management interface of the primary blade in a physical cluster may not recognize the cluster as the source of the traffic. Services that depend on traffic sourced from the management interface of a VCMP guest may fail.

Conditions

On a physical cluster, functionality that generates traffic over the management interface of the primary blade (such as RADIUS authentication, remote logging, ping) result in traffic sourced from the IP address of the primary blade, not the cluster floating IP address. On a VCMP guest, functionality that generates traffic over the management interface of the guest may fail with an ICMP 'destination unreachable' message.

Workaround

None.

Fix Information

The primary blade in a clustered system now sends management traffic sourced from the cluster IP address. In addition, traffic sourced from the management interface of a VCMP guest no longer fails with an ICMP 'destination unreachable' message.

Behavior Change