Bug ID 504021: lsn-pool member routes not properly propagated to routing table when lsn-pool routing-advertisement is enabled

Last Modified: Oct 17, 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, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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: Jan 30, 2015

Severity: 3-Major

Symptoms

lsn-pool with route-advertisement enabled does not have routes properly propagated to the routing-table.

Impact

route entries for lsn-pool members with route-advertisement enabled.

Conditions

when route-domain routing protocol is enabled after lsn-pool route-advertisement is enabled and lsn-pool member added.

Workaround

Either 1) restart tmrouted after enable routing-protocol for the desired route-domain. 2) toggle routing-advertisement on lsn-pool after enable routing-protocol for the desired route-domain.

Fix Information

route-domain with routing-protocol enabled will have routes for lsn-pool members, regardless of ordering in which routing-protocol or route-advertisement is enabled.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips