Support Center > Search Results > SecureKnowledge Details
After upgrade to R80.30, BGP peer is stuck in Active state Technical Level
Symptoms
  • The output of the "show bgp peers" command shows the negotiation with peer stuck on Active state

  • In BGP debugs as per sk101399, the routed.log shows:
    The peer establishes with the gateway
    [DATE TIME] bgp_event: peer X.X.X.X [eBGP AS 65232] old state OpenConfirm event RecvKeepAlive new state Established
    This is followed up with a exchange of a few routes (178 in this case) with the peer before the gateway (checkpoint) sends a huge a corrupted BGP AS4_PATH attribute value and the negotiation with the peer breaks down:
    [DATE TIME] BGP SEND message type 2 (Update) length 18539
    [DATE TIME] BGP SEND flags 0x40 code Origin(1): Incomplete
    [DATE TIME] BGP SEND flags 0x40 code ASPath(2): {as4:0 len:6172 seglenbytes: 2 - segtype: 0x02 num_as :0x01} 65230 {as4:0 len:6168 seglenbytes: 510 - segtype: 0x0f num_as :0xff}

    ....
    (corrupted BGP AS4_PATH attribute value is seen here)
    .... ...
    [DATE TIME] bgp_write_message: buffering a partial message (16620 bytes) for peer 10.97.4.43 [eBGP AS 65232]
    [DATE TIME] bgp_outbuf_alloc(2294): requested buffer length is too large (16620) for peer 10.97.4.43 [eBGP AS 65232]
    [DATE TIME] bgp_send: sending 16620 bytes to X.X.X.X [eBGP AS 65232] blocked and spooling failed
    [DATE TIME] bgp_rt_send_peer: peer X.X.X.X [eBGP AS 65232] write failed after 178 routes sent
    [DATE TIME] bgp_peer_close(6292): closing peer 10.97.4.43 [eBGP AS 65232], state is 6 (Established)
    [DATE TIME] bgp_event: peer X.X.X.X [eBGP AS 65232] old state Established event TransportError new state Idle

Cause

In some scenarios, a corrupted BGP AS4_PATH attribute value might result in an invalid, long BGP update that is rejected by the BGP peer.


Solution
Note: To view this solution you need to Sign In .