Last Modified: Jul 23, 2021
See more info
Known Affected Versions:
13.1.0, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.1, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.1.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.1.4, 22.214.171.124, 14.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.2, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.1.3, 188.8.131.52, 14.1.4, 184.108.40.206, 220.127.116.11, 18.104.22.168, 15.1.0, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 15.1.1, 15.1.2, 18.104.22.168, 15.1.3, 22.214.171.124, 16.0.0, 126.96.36.199, 16.0.1, 188.8.131.52, 184.108.40.206
Opened: Dec 02, 2020
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 as vCMP guests running on an appliance are unaffected. HA failover connections using self IPs are unaffected.
Failover state determination over the management port is permanently down.
-- vCMP guest running on a VIPRION -- HA failover connection using the management IP addresses (unicast and/or multicast)
While self IP-based HA failover connections are not affected by this issue, F5 recommends configuring failover connections over both management IPs and self IPs (as detailed in K37361453: Configuring network failover for redundant VIPRION systems :: https://support.f5.com/csp/article/K37361453). To mitigate this issue, run the following command on each blade of every guest: touch /var/run/chmand.pid The workaround does 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. Alternatively, You can use instructions in K11948: Configuring the BIG-IP system to run commands or scripts upon system startup :: https://support.f5.com/csp/article/K11948 to issue commands at system startup after verification if mcpd is up and ready, e.g.: #!/bin/bash source /usr/lib/bigstart/bigip-ready-functions wait_bigip_ready # Customized startup command(s) can be added below this line. touch /var/run/chmand.pid # Customized startup command(s) should end above this line.