Bug ID 1026273: HA failover connectivity using the cluster management address does not work on VIPRION platforms

Last Modified: Apr 28, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, TMOS(all modules)

Known Affected Versions:
17.0.0, 16.1.0,,, 16.0.1,, 16.0.0, 15.1.4,, 15.1.3,, 15.1.2,,,,, 14.1.4,, 14.1.3,,,, 13.1.4,,

Opened: Jun 16, 2021
Severity: 3-Major


Upon upgrade to an affected version, failover communication via the management port does not work. You may still see packets passing back and forth, but the listener on the receiving end is not configured, and therefore the channel is not up. Here are a few symptoms you may see: -- Running 'tmsh show cm failover-status' shows a status of 'Error' on the management network. -- Running 'tmctl' commands reports the disconnected state: Example: $ tmctl -l sod_tg_conn_stat -s entry_key,last_msg,status entry_key last_msg status ----------------------------- ---------- ------> 0 0 <--- Notice there is no 'last message' and 'status' is 0, which means disconnected.> 1623681404 1 -- Looking at 'netstat -pan | grep 1026 command output, you do not see the management port listening on port 1026: Example (notice that the management IP from the above example of is not listed): # netstat -pan | grep 1026 udp 0 0* 6035/sod -- Listing /var/run/ contents shows that the chmand.pid file is missing: # ls /var/run/chmand.pid ls: cannot access /var/run/chmand.pid: No such file or directory


If only the management is configured for failover or there are communication issues over the self IP (such as misconfigured port lockdown settings), then the devices may appear to have unusual behavior such as both going active.


-- Running on VIPRION platforms -- Only cluster management IP address is configured: No cluster member IP addresses are configured -- Install a software version where ID810821 is fixed (see https://cdn.f5.com/product/bugtracker/ID810821.html) -- Management IP is configured in the failover configuration


-- Configure a cluster member IP address on each individual blade in addition to the Cluster management IP address.

Fix Information


Behavior Change