Bug ID 425495: Private tmsh aliases can cause sync failures

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:

Fixed In:

Opened: Jul 17, 2013

Severity: 3-Major

Related Article: K14717


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- doesn't match user name specified in cli alias, my_alias (admin).


The sync operation will fail.


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


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

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips