Bug ID 969105: HA failover connections via the management address do not work on vCMP guests running on VIPRION

Last Modified: Dec 17, 2020

Bug Tracker

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

Known Affected Versions:
13.1.0, 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, 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, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2

Opened: Dec 02, 2020
Severity: 3-Major

Symptoms

A high availability (HA) failover connection using the management IP addresses does not work on vCMP guests running on a VIPRION. BIG-IP instances running directly on hardware, on Virtual Edition, and on vCMP guests are unaffected. High availability (HA) failover connections using self IPs are unaffected.

Impact

Failover state determination over the management port is permanently down.

Conditions

1. vCMP guest running on a VIPRION 2. High availability (HA) failover connection using the management IP addresses

Workaround

Run the following command on all Guests: touch /var/run/chmand.pid The workaround will not survive a reboot, so a more permanent workaround is to edit the file /config/startup and add a line to touch /var/run/chmand.pid. Add this line to the end of /config/startup: $(sleep 120; touch /var/run/chmand.pid) & Note: The sleep time of 120 seconds should be tested as it depends on how quickly or slowly the Guest starts up, so the appropriate value for one system may differ from another system.

Fix Information

None

Behavior Change