Last Modified: Apr 17, 2024
Affected Product(s):
BIG-IP Install/Upgrade, vCMP
Known Affected Versions:
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, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 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, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4
Opened: Jun 24, 2019 Severity: 3-Major
VCMP host or guest is upgraded, and the vCMP guest is 'Inoperative', with messages similar to the following in /var/log/ltm: -- warning clusterd[1546]: 013a0005:4: Clusterd using /VERSION for SW specification. -- info clusterd[1546]: 013a0023:6: Blade 1: No info received from slot: Starting up -- err clusterd[1546]: 013a0004:3: result { -- err clusterd[1546]: 013a0004:3: result.code 17237812 -- err clusterd[1546]: 013a0004:3: result.attribute float_mgmt2_ip -- err clusterd[1546]: 013a0004:3: result.message 01070734:3: Configuration error: Cluster alt-address: 192.168.1.246 cannot be the same address family as cluster address: 192.168.1.246 -- err clusterd[1546]: 013a0004:3: } -- err clusterd[1546]: 013a0004:3: Per-invocation log rate exceeded; throttling. -- notice clusterd[1546]: 013a0006:5: Disconnecting from mcpd. -- info clusterd[1546]: 013a0007:6: clusterd stopping...
Upon host/guest upgrade, vCMP guest is 'Inoperative'.
-- Isolated vCMP guest. -- Both 'Address' and 'Alt-Address' are assigned the same IPv4 address. -- Upgrade occurs.
-- For new vCMP guests, or prior to booting the vCMP guest to an affected version for the first time, assign it a management-ip from the vCMP host. This prevents the alt-address from being assigned and the issue from occurring on subsequent upgrades. tmsh modify vcmp <guest_name> management-ip 192.168.1.246/24 -- For existing vCMP guests already on an affected version, but not currently experiencing the issue, assign a management-ip from the vCMP host and remove the alt-address from within the vCMP guest to prevent the issue from occurring in a future upgrade or reboot: host# tmsh modify vcmp guest <guest-name> management-ip 192.168.1.246/24 guest# tmsh modify sys cluster default alt-address none -- When already upgraded and seeing the issue on a guest, set a management-ip from the vCMP host and run the following commands within the guest to remove the alternate address from the configuration file: host# tmsh modify vcmp guest <guest-name> management-ip 192.168.1.246/24 guest# bigstart stop clusterd guest# sed -i s/alt_addr=.*// -i /shared/db/cluster.conf guest# bigstart start clusterd
None