Bug ID 698407: OSPF tag updates may not be propagated through process redistribution

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4

Fixed In:
14.0.0

Opened: Dec 11, 2017

Severity: 3-Major

Symptoms

If BIG-IP receives an OSPF LSA with an external tag set and the ensuing route is redistributed into another protocol, including an OSPF process, updates to the tag may not be preserved.

Impact

Routing policy may not be executed correctly leading to misrouted or discarded traffic.

Conditions

-- Redistributing routes from OSPF process to another protocol or process. -- OSPF LSAs with external route tag != 0. -- External route tag changes to 0.

Workaround

Clearing the affected route resolves the issue. This might require clearing the OSPF process. To do so, follow this process: In imish, run the following command: clear ip ospf This interrupts routing that relies on OSPF until the network reconverges.

Fix Information

OSPF external tag updates are correctly propagated through redistribution.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips