Bug ID 505097: lsn-pool backup-member not propagated to route table after tmrouted restart

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF6

Opened: Feb 06, 2015

Severity: 3-Major

Related Article: K17152

Symptoms

The lsn-pool backup-member prefix is not in the route table after tmrouted restart, when lsn-pool route-advertisement is enabled.

Impact

No routes for lsn-pool backup-member prefix.

Conditions

An lsn-pool with route-advertisement enabled, and backup-members, backup-member prefix not properly propagated to the route-domain routing table after tmrouted restart.

Workaround

Remove and re-add lsn-pool backup members.

Fix Information

The lsn-pool backup-member prefix is now present in the route table after tmrouted restart, when lsn-pool route-advertisement is enabled.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips