After an upgrade to R80.10, BGP peer is stuck in Active state
- After an upgrade to R80.10, BGP peer is stuck in the Active state (previous versions did not exhibit these symptoms).
- Negotiations fail after the first UPDATE packet.
- Routed stops working unexpectedly, and may create a core dump file.
- Running routed debug (according to sk101399) results in:
"[routed] ERROR: aspath_hash_resize: New length (138) is greater than the current length (132)" notification to peer.
"Malformed AS Path"
"AS path attribute problem"
The BGP Peer is using 2-byte AS numbers. R80.10 is not properly handling AS paths from peers that do not support 4-byte AS numbers, specifically when the paths are long.
Note: To view this solution you need to