Bug ID 767397: tmsh does not consistently display persistence records present on non-primary blades

Last Modified: Jun 13, 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, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 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, 15.0.0

Opened: Apr 01, 2019
Severity: 4-Minor

Symptoms

Listing persistence records in a chassis with match-across-services enabled in the persistence profile does not consistently display records present on non-primary blades. Records on the non-primary blade disappear and reappear.

Impact

There is no impact to persistence. This is a reporting error. Persistence records do not actually disappear.

Conditions

-- The match-across-services option is enabled in the persistence profile. -- The profile is used by two virtual servers listening on the same address but different ports. -- A specific mode and key is selected in the tmsh query.

Workaround

None.

Fix Information

None

Behavior Change