Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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.3.0, 11.4.0, 11.4.1
Fixed In:
11.5.0, 11.4.1 HF6
Opened: Oct 02, 2013 Severity: 1-Blocking Related Article:
K14962
When single-hop BFD session is configured with certain versions of Cisco or Juniper OS using IPv6 addresses, IPv6 BFD INIT packets sent from the BIG-IP system may be dropped by Cisco because the BIG-IP system sends these IPv6 packets with a recommended default hop limit of 64 instead of 255 as required by RFC 5881. Neighbor debug logs may show if this is the problem.
BFD sessions fail to establish.
This occurs when you configure BFD with IPv6 addresses for the BFD session with newer versions of Cisco or Juniper OS.
None for IPv6 addresses. BFD sessions using IPv4 addresses work correctly.
The BIG-IP system transmits IPv6 BFD for single-hop sessions with a hop limit value of 255.