Switching

 View Only

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



Expand all | Collapse all

BGP_EXTENDED_NH_NLRI_MISMATCH: bgp_process_ext_nh_cap: mismatch extended nexthop

This thread has been viewed 5 times
  • 1.  BGP_EXTENDED_NH_NLRI_MISMATCH: bgp_process_ext_nh_cap: mismatch extended nexthop

    Posted 05-23-2022 10:57

    Hello,

    We are having weird problem in establishing BGP session.
    Model: mx204
    Junos: 20.3R1.8
    May 19 13:05:32.068xxx Group ready, new=N, rtq ready=N, act rib=2, rto nexttme<-0
    May 19 13:05:36.959029 advertising graceful restart receiving-speaker-only capability to neighbor xx.xx.xx.xx (External AS xxx)
    May 19 13:05:36.959043 advertising LLGR receiving-speaker-only capability to neighbor xx.xx.xx.xx (External AS xxx)
    May 19 13:05:36.959086 BGP_EXTENDED_NH_NLRI_MISMATCH: bgp_process_ext_nh_cap: mismatch extended nexthop encoding NLRI with xx.xx.xx.xx (External AS xxx): peer: <inet-unicast inet-multicast inet-vpn-unicast>(7) us: <>(0) (instance vrf2)
    May 19 13:05:36.959143 bgp_process_ext_nh_cap:405: NOTIFICATION sent to xx.xx.xx.xx (External AS xxx): code 2 (Open Message Error) subcode 7 (unsupported capability) Capability other than MP
    May 19 13:05:36.959149 Notify sent to xx.xx.xx.xx (External AS xxx), code 2, subcode 7
    May 19 13:05:36.959190 bgp_peer_close_and_restart: peer xx.xx.xx.xx (External AS xxx), state is 4 (OpenSent) event RecvOpen, flags=0x0
    May 19 13:05:36.959196 bgp_peer_close_and_restart: closing peer xx.xx.xx.xx (External AS xxx), state is 4 (OpenSent) event RecvOpen
    May 19 13:05:36.959205 BGP peer xx.xx.xx.xx (External AS xxx) CLOSE: close socket 138
    May 19 13:05:36.959238 bgp_peer_close_and_restart: 8380: BGP peer xx.xx.xx.xx (External AS xxx): state OpenSent task close fd -1
    May 19 13:05:36.959443 bgp_delete_pending_set_impatient: peer xx.xx.xx.xx (External AS xxx) job-exist:no, flags:, need-job:no
    May 19 13:05:36.959455 bgp_peer_post_close:8016 BGP Peer xx.xx.xx.xx (External AS xxx) CLOSE: post close cleanup - NEED restart, (last_flap NoEvent, state Idle, flags )


    Other side is running Cisco and they replied

    Peering does not function properly due to mismatched capabilities between peers. Please see the tech note on why this is a problem:

    https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/116189-problemsolution-technology-00.html

    has configured "capability suppress all" on the neighbor toward your end to bring up the BGP session.

    Can someone tell me what is causing this issue? We have two more carriers with bgp established with same settings only one carrier having issue.
    Thanks



  • 2.  RE: BGP_EXTENDED_NH_NLRI_MISMATCH: bgp_process_ext_nh_cap: mismatch extended nexthop

    Posted 06-07-2022 09:52
    The issue seems to be a capability issue, indeed.

    Are you using IOS-XR and Junos to form this peering? for IOS-XR, 6.6.3 introduced support for rfc5549, which is the Extended Next-Hop Capability. Please try the following:

    <neighbor x.x.x.x capability-suppress extended-next-hop>

    Elvin