Routing

Expand all | Collapse all

BGP session in routing-instance unable to connect to neighbor

Jump to Best Answer
  • 1.  BGP session in routing-instance unable to connect to neighbor

    Posted 05-21-2019 00:52

    Hello. I’m facing a problem with a new routing instance on MX-5 router. BGP session won’t establish.

     

    May 17 18:09:16.583791 BGP_SET_INTERFACE_FAILED: bgp_set_peer_if: BGP peer 172.10.0.2 (External AS 78313) interface not found. Leaving peer idled

    May 17 18:12:04.071366 bgp_connect_complete: error connecting to 172.10.0.2 (External AS 78313): Socket is not connected

    May 17 18:19:34.072282 bgp_connect_complete: error connecting to 172.10.0.2 (External AS 78313): Socket is not connected

    May 17 18:20:40.690218 bgp_color_sync_start:1421: 172.10.0.2 (External AS 78313): Color sync start for nlri's:

    May 17 18:20:47.111615 bgp_connect_timeout: BGP_78313.172.10.0.2_Connect

    May 17 18:20:47.111710 bgp_connect_start: peer 172.10.0.2 (External AS 78313)

    May 17 18:20:47.111765 bgp_event: peer 172.10.0.2 (External AS 78313) old state Active event ConnectRetry new state Connect

    May 17 18:20:47.112951 task_get_socket: domain AF_INET type SOCK_STREAM protocol 0 socket 136

    May 17 18:20:47.113006 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option RecvBuffer(0) value 16384

    May 17 18:20:47.113042 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option SendBuffer(1) value 16384

    May 17 18:20:47.113081 task_set_socket: task BGP_78313.172.10.0.2 socket 136

    May 17 18:20:47.113140 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option NonBlocking(8) value 1

    May 17 18:20:47.113177 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option ReUsePort(38) value 1

    May 17 18:20:47.113213 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option PathMTUDiscovery(26) value 0

    May 17 18:20:47.113292 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option RoutingTable(27) value 8

    May 17 18:20:47.113331 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option TOS(16) value 192

    May 17 18:20:47.113366 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option DontRoute(5) value 1

    May 17 18:20:47.113399 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option IifRestrict(36) value 1

    May 17 18:20:47.113433 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option TTL(15) value 1

    May 17 18:20:47.113470 Eval BFD turn-on, currently off for peer 172.10.0.2 (External AS 78313)(fl:)instance AZURE (kern-id 😎

    May 17 18:20:47.113506 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option TcpAggressiveTransmission(59) value 0

    May 17 18:20:47.113540 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option EnableTcpNoDelay(63) value 0

    May 17 18:20:47.114323 task_timer_reset: reset BGP_78313.172.10.0.2_Connect

    May 17 18:20:47.114379 task_timer_set_oneshot_latest: timer BGP_78313.172.10.0.2_Connect interval set to 2:28

    Routing instance:

    [CODE]

    RI-2 {

    instance-type virtual-router;

    interface ge-1/1/0.435;

    routing-options {

    autonomous-system 54553;

    }

    protocols {

    bgp {

    group IPv4-AZURE {

    type external;

    traceoptions {

    file bgplog size 10k files 10;

    flag all;

    }

    import IPv4-FILTER-IN;

    export IPv4-PEER-FILTER-OUT;

    neighbor 172.10.0.2 {

    peer-as 78313;

    }

    }

    }

    }

    }

    Interface ge-1/1/0

    [CODE]

    vlan-tagging;

    unit 120 {

    vlan-id 120;

    family inet {

    }

    address 1.1.1.1/30;

    }

    unit 435 {

    vlan-id 435;

    family inet {

    address 172.10.0.1/30;

    }

    }

    I’m able to ping BGP neighbor via routing-instance.

    [CODE]

    ping 172.10.0.2 routing-instance RI-2

    PING 172.10.0.2 (172.10.0.2): 56 data bytes

    64 bytes from 172.10.0.2: icmp_seq=0 ttl=255 time=27.840 ms

    64 bytes from 172.10.0.2: icmp_seq=1 ttl=255 time=27.870 ms

    64 bytes from 172.10.0.2: icmp_seq=2 ttl=255 time=27.766 ms

    64 bytes from 172.10.0.2: icmp_seq=3 ttl=255 time=27.817 ms

    BGP neighbor status

    [CODE]

    > show bgp neighbor 172.10.0.2

    Peer: 172.10.0.2+179 AS 12076 Local: 172.10.0.1+54833 AS 5453

    Group: IPv4-RI2 Routing-Instance: RI-2

    Forwarding routing-instance: RI-2

    Type: External State: Connect Flags: <>

    Last State: Active Last Event: ConnectRetry

    Last Error: None

    Export: [ IPv4-PEER-FILTER-OUT ] Import: [ IPv4-FILTER-IN ]

    Options: <Multihop Preference AddressFamily PeerAS Refresh>

    Address families configured: inet-unicast

    Holdtime: 90 Preference: 170

    Number of flaps: 0

    Trace options: detail open

    Trace file: /var/log/bgplog size 0 files 1



  • 2.  RE: BGP session in routing-instance unable to connect to neighbor
    Best Answer

    Posted 05-21-2019 01:16

    Hi MICDUF,

     

    Please check firewall filter on lo0.0 interface if it allowed bgp connection between  172.10.0.1 <--> 172.10.0.2

    If routing instance does not have assotiated lo0 interface than lo0.0 filter is applied on this RI.

     

    Also please note that setting bgp traceoptions with file size of 10K can criple your box by intensive disk activity.

    It is better to set filesize of 10M or 100M and number of files to 2-5.

     

    Thanks,

    Alex



  • 3.  RE: BGP session in routing-instance unable to connect to neighbor

    Posted 05-21-2019 01:52
    Thanks Alex that was the problem.