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

Last Modified: Aug 19, 2026

Affected Product(s):
BIG-IP CGN(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, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0

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