Routing

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

Anyway to find which AS the remote site tries to peer with?

  • 1.  Anyway to find which AS the remote site tries to peer with?

    Posted 16 days ago
    I can find remote AS number from traceoptions, but it seems I could not find which AS the remote tries to peer with. Anyway to find it out ?

    Say, remote AS is 1111, my AS is 2222, but the remote site peers with 3333. Can I find this without asking the remote site ?

    thanks !!


  • 2.  RE: Anyway to find which AS the remote site tries to peer with?

     
    Posted 16 days ago
    My recollection is the standard messages log only says the AS is a mismatch

    show log messages

    And you need to configure bgp trace options to get a log with all the details.

    https://www.juniper.net/documentation/en_US/junos/topics/topic-map/bgp-troubleshooting.html


    ------------------------------
    Steve Puluka BSEET - Juniper Ambassador
    IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
    http://puluka.com/home
    ------------------------------



  • 3.  RE: Anyway to find which AS the remote site tries to peer with?

    Posted 15 days ago
    I enabled traceoptions, but I did not find which AS the remote site tried to connect to.
    Oct 11 02:50:10.174796 BGP RECV 172.31.1.1+64272 -> 172.31.2.1+179
    Oct 11 02:50:10.174815 BGP RECV message type 3 (Notification) length 21
    Oct 11 02:50:10.174827 BGP RECV Notification code 2 (Open Message Error) subcode 2 (bad peer AS number)
    Oct 11 02:50:10.177903 BGP RECV 172.31.1.1+64272 -> 172.31.2.1+179
    Oct 11 02:50:10.178046 bgp_peer_close_and_restart: closing peer 172.31.1.1 (External AS 1111), state is 5 (OpenConfirm) event RecvNotify
    Oct 11 02:50:10.178923 bgp_event: peer 172.31.1.1 (External AS 1111) old state OpenConfirm event RecvNotify new state Idle
    Oct 11 02:52:38.344999 BGP RECV 172.31.1.1+50117 -> 172.31.2.1+179
    Oct 11 02:52:38.345804 BGP RECV message type 1 (Open) length 59
    Oct 11 02:52:38.345989 BGP RECV version 4 as 1111 holdtime 90 id 172.31.1.1 parmlen 30
    Oct 11 02:52:38.346007 BGP RECV MP capability AFI=1, SAFI=1
    Oct 11 02:52:38.346017 BGP RECV Refresh capability, code=128
    Oct 11 02:52:38.346026 BGP RECV Refresh capability, code=2
    Oct 11 02:52:38.346693 BGP RECV Restart capability, code=64, time=120, flags=
    Oct 11 02:52:38.346830 BGP RECV 4 Byte AS-Path capability (65), as_num 1111
    Oct 11 02:52:38.352306 task_set_option_internal: task BGP_1111_3333.172.31.1.1+50117 socket 115 option RecvBuffer(0) value 16384
    Oct 11 02:52:38.354905 bgp_process_4byte_aspath_cap():312 AS4-Peer 172.31.1.1 (External AS 1111)(RECV): 4 byte AS Cap value stored 1111
    Oct 11 02:52:38.355047 bgp_event: peer 172.31.1.1 (External AS 1111) old state OpenSent event RecvOpen new state OpenConfirm
    Oct 11 02:52:38.515913 BGP RECV 172.31.1.1+50117 -> 172.31.2.1+179
    Oct 11 02:52:38.515939 BGP RECV message type 3 (Notification) length 21
    Oct 11 02:52:38.515953 BGP RECV Notification code 2 (Open Message Error) subcode 2 (bad peer AS number)
    Oct 11 02:52:38.516991 BGP RECV 172.31.1.1+50117 -> 172.31.2.1+179
    Oct 11 02:52:38.517129 bgp_peer_close_and_restart: closing peer 172.31.1.1 (External AS 1111), state is 5 (OpenConfirm) event RecvNotify
    Oct 11 02:52:38.522272 bgp_event: peer 172.31.1.1 (External AS 1111) old state OpenConfirm event RecvNotify new state Idle
    ​

    The remote site was configured as follows:

    set routing-instances S1-101 protocols bgp group TovMX1 type external
    set routing-instances S1-101 protocols bgp group TovMX1 multihop
    set routing-instances S1-101 protocols bgp group TovMX1 local-address 172.31.1.1
    set routing-instances S1-101 protocols bgp group TovMX1 local-as 1111
    set routing-instances S1-101 protocols bgp group TovMX1 neighbor 172.31.2.1 peer-as 2222
    

    I am wondering whether I can find 2222 in the log on my site.

    thanks a lot !!