Bug ID 767329: Mirrored persistence records are not identified in tmsh output

Last Modified: Nov 15, 2019

Bug Tracker

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

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 15.0.0, 15.0.1

Opened: Apr 01, 2019
Severity: 4-Minor

Symptoms

Listing persistence records in a chassis with intra-chassis mirroring using 'tmsh show ltm persistence persist-records all-properties' does not distinguish the mirrored record from the active record.

Impact

The output is confusing and potentially misleading, by implying that a persistence key is owned by two different TMMs.

Conditions

-- Intra-chassis mirroring is configured. -- Mirroring in the persistence profile or virtual server is configured.

Workaround

None.

Fix Information

None

Behavior Change