Bug ID 425495: Private tmsh aliases can cause sync failures

Last Modified: Oct 06, 2020

Bug Tracker

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

Known Affected Versions:
11.4.0

Fixed In:
11.5.0

Opened: Jul 17, 2013
Severity: 3-Major
Related AskF5 Article:
K14717

Symptoms

Operations on private tmsh aliases may cause the next sync to fail with an error of the following form: 01071506:3: Current user (%cmi-mcpd-peer-10.0.0.1) doesn't match user name specified in cli alias, my_alias (admin).

Impact

The sync operation will fail.

Conditions

This only occurs if the failover device group has 'full-load-on-sync false'. Note that this is the default value.

Workaround

The full-load-on-sync setting on the failover device group can be set to true (note that this greatly affects performance). Alternately, a full-load sync can be forced with 'modify cm device-group FAILOVER_DEVICE_GROUP_NAME devices modify { CURRENT_DEVICE_NAME { set-sync-leader } }'. Future incremental syncs will then succeed.

Fix Information

Private tmsh aliases no longer cause sync failures.

Behavior Change