Bug ID 454407: BGP on GRE tunnels causes updates to use invalid next_hop of 0.0.0.0

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.6.0

Opened: Mar 27, 2014
Severity: 3-Major
Related Article:
K15485

Symptoms

The BGP peer sends a Notification Error Message: (UPDATE Message Error/Invalid NEXT_HOP Attribute.) and BGP session is reset to active state.

Impact

BGP session is not established and so no routing info is exchanged.

Conditions

A GRE tunnel is created between two LTMs and A BGP peer session is created across this tunnel between the two LTMs.

Workaround

On each LTM, create a routemap as follows: route-map NEXTHOP permit 10 set ip next-hop "self-ip on GRE tunnel" primary Applying the route-map to the neighbor in the bgp config solves this: neighbor x.x.x.x route-map NEXTHOP out

Fix Information

BGP session over GRE tunnels is established with a correct next_hop value.

Behavior Change