Bug ID 976517: Tmsh run sys failover standby with a device specified but no traffic group fails

Last Modified: Mar 01, 2021

Bug Tracker

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

Known Affected Versions:
15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 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, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1

Opened: Dec 23, 2020
Severity: 4-Minor

Symptoms

The tmsh run /sys failiover standby device <device> command fails and returns an error if no traffic-group is specified: Syntax Error: There is no failover device with a name (/Common/bigip2.localhost).

Impact

You are required to specify all the traffic groups you want to failover to a peer.

Conditions

Two or more BIG-IPs configured with high availability (HA)

Workaround

For each traffic group that you want to failover to a peer run the tmsh run /sys failover standby. For example if you want to fail over both traffic groups traffic-group-1 and traffic-group-2 to failover to bigip2.localhost, run the following: tmsh run /sys failover standby device bigip2.localhost traffic-group traffic-group-1 tmsh run /sys failover standby device bigip2.localhost traffic-group traffic-group-2 If you want the device to be standby for all traffic groups but you don't care what device takes over as active, run the following command (note there is no traffic-group nor device): tmsh run /sys failover standby

Fix Information

None

Behavior Change