Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
9.4.5, 9.4.6, 9.4.7, 9.4.8, 10.0.0, 10.0.1, 10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.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.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.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.6.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.1.0, 11.2.0, 11.2.1, 11.3.0
Fixed In:
11.5.0
Opened: Jul 09, 2013 Severity: 3-Major Related Article:
K14546
OSPFv3 configured with a non-default metric/metric-type on a redistribute statement doesn't show the non-default metric/metric-type in the config or in any displayed state.
OSPFv3 may redistribute routes using incorrect metrics.
In an HA pair, OSPFv3 configured with redistribution from another protocol using a non-default metric/metric-type, failover.
Restart ospf6d after the unit goes standby: tmsh mod net route-domain <rdid> routing-protocol remove { OSPFv3 } ; tmsh mod net route-domain <rdid> routing-protocol add { OSPFv3 }
OSPFv3 now retains non-default metric/metric-types for redistributed protocols when a unit transitions from active to standby.