Bug ID 598854: sipdb tool incorrectly displays persistence records without a pool name

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2

Fixed In:
13.0.0, 12.1.2, 11.6.1 HF2

Opened: Jun 13, 2016
Severity: 3-Major

Symptoms

MRF SIP persistence records added for a forwarding route (a peer object without a pool), will not be displayed properly by sipdb

Impact

The persistence entry is correctly stored in the persistence table and will operate correctly. Due to the bug in the sipdb tool, this entry will not be viewable for debugging purposes.

Conditions

If a persistence record is added for a route that does not contain a pool, this persistence entry will not be displayed correctly.

Workaround

None

Fix Information

The fix corrects the sipdb tool so that entries which do not have a pool name will display correctly.

Behavior Change