Routing

last person joined: 5 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  Trouble pinging to the bgp route from ibgp core

    Posted 12-14-2016 17:51

    Hello,

     

    I have three route reflector configured in the core where, R3(RR) is directly connected and R5(RR) is connected to R3. I'm trying to do ping from R5 to T1 or T2 but i can't ping there. Please advise what i'm doing wrong here.

     

    Please find attached config file for R3, R5, T1 and T2 Router.

     

    root@R5# run traceroute 120.120.0.1 
    traceroute to 120.120.0.1 (120.120.0.1), 30 hops max, 40 byte packets
    traceroute: sendto: No route to host
     1 traceroute: wrote 120.120.0.1 40 chars, ret=-1
     *traceroute: sendto: No route to host
    traceroute: wrote 120.120.0.1 40 chars, ret=-1
     *traceroute: sendto: No route to host
    traceroute: wrote 120.120.0.1 40 chars, ret=-1
    ^C
    
    
    [edit]
    root@R5# run traceroute 130.130.0.1    
    traceroute to 130.130.0.1 (130.130.0.1), 30 hops max, 40 byte packets
     1  10.0.2.2 (10.0.2.2)  26.487 ms  19.353 ms  20.133 ms
     2  * *^C
    [edit]
    root@R5# 
    
    
    root@R5# run show bgp summary 
    Groups: 2 Peers: 4 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0               
                          17         10          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    10.0.2.2              65000     958107       7567       0       3  2d 4:16:13 4/6/6/0              0/0/0/0
    10.0.2.10             65000     958108       7512       0       3  2d 4:16:09 2/6/6/0              0/0/0/0
    10.0.9.6              65001       7040       7505       0       3  2d 4:16:12 2/3/3/0              0/0/0/0
    10.0.9.7              65001       7071       7535       0       3  2d 4:16:10 2/2/2/0              0/0/0/0
    
    root@R3# run show bgp summary 
    Groups: 3 Peers: 6 Down peers: 2
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0               
                          17          9          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    10.0.2.1              65001       7568     959101       0       3  2d 4:16:33 3/5/5/0              0/0/0/0
    10.0.3.4              65000     961927     961715       0       3  2d 4:16:36 3/5/5/0              0/0/0/0
    10.0.6.1              65000          0          0       0       4     5:04:34 Active
    10.0.6.2              65000          0          0       0       4     5:04:44 Active
    172.16.0.14           65222       1255       1666       0       3     9:23:20 1/3/3/0              0/0/0/0
    172.16.0.18           65222       1376       1795       0       0    10:21:38 2/4/4/0              0/0/0/0
    

    Any suggestion would be highly appriciated.

     

     

    Thanks,

    Jay

     

     

    Attachment(s)

    txt
    T2.txt   1 KB 1 version
    txt
    R5.txt   1 KB 1 version
    txt
    T1.txt   910 B 1 version
    txt
    R3.txt   3 KB 1 version


  • 2.  RE: Trouble pinging to the bgp route from ibgp core

    Posted 12-14-2016 18:13

    Try to ping with source address of lo0 interface

     ping source XXX 130.130.0.1

     

    P.S. also you can configure default-address-selection to use address from lo0 interface by default



  • 3.  RE: Trouble pinging to the bgp route from ibgp core

    Posted 12-14-2016 18:40

    Thanks for the quick reply.

     

    I can't ping using source address as well.

    root@R5# run ping source 10.0.3.5 130.130.0.1 
    PING 130.130.0.1 (130.130.0.1): 56 data bytes
    ^C
    --- 130.130.0.1 ping statistics ---
    13 packets transmitted, 0 packets received, 100% packet loss
    [edit]
    root@R5#

    Thanks,

    Jay

     



  • 4.  RE: Trouble pinging to the bgp route from ibgp core
    Best Answer

     
    Posted 12-15-2016 02:16

    Hi, 

     

    I would suggest checking on T1 & T2 for return routes to R5.

    Also, doesn't seem to be having a route for 120.120.0.1 on R5.

     

    Cheers,

    Ashvin



  • 5.  RE: Trouble pinging to the bgp route from ibgp core

    Posted 12-15-2016 06:47

    Thanks Ashvin!!. I really appriciate your help.

     

    Policy wasn't configured correctly on T1 and T2, That's why i wasn't able to traceroute to T1 and T2 from R5. Corrected the policy and i can see route for 120.120/16 and 130.130/16 from R5.

     

    root@R5# run show route 120.120/16 
    
    inet.0: 30 destinations, 36 routes (30 active, 0 holddown, 1 hidden)
    + = Active Route, - = Last Active, * = Both
    
    120.120.0.0/16     *[BGP/170] 00:12:59, localpref 100
                          AS path: (65000) 65222 I, validation-state: unverified
                        > to 10.0.2.2 via ge-0/0/1.0
                        [BGP/170] 00:12:59, localpref 100, from 10.0.2.10
                          AS path: (65000) 65222 I, validation-state: unverified
                        > to 10.0.2.2 via ge-0/0/1.0
    
    [edit]
    root@R5# run show route 130.130/16 
    
    inet.0: 30 destinations, 36 routes (30 active, 0 holddown, 1 hidden)
    + = Active Route, - = Last Active, * = Both
    
    130.130.0.0/16     *[BGP/170] 17:45:09, localpref 100
                          AS path: (65000) 65222 I, validation-state: unverified
                        > to 10.0.2.2 via ge-0/0/1.0
                        [BGP/170] 17:45:09, localpref 100, from 10.0.2.10
                          AS path: (65000) 65222 I, validation-state: unverified
                        > to 10.0.2.2 via ge-0/0/1.0
    
    root@R5# run traceroute 120.120.0.1 
    traceroute to 120.120.0.1 (120.120.0.1), 30 hops max, 40 byte packets
     1  10.0.2.2 (10.0.2.2)  16.230 ms  19.230 ms  20.068 ms
     2  172.16.0.14 (172.16.0.14)  30.458 ms !N  24.768 ms !N  30.504 ms !N
    
    [edit]
    root@R5# run traceroute 130.130.0.1 
    traceroute to 130.130.0.1 (130.130.0.1), 30 hops max, 40 byte packets
     1  10.0.2.2 (10.0.2.2)  16.034 ms  20.610 ms  18.814 ms
     2  172.16.0.18 (172.16.0.18)  30.151 ms !N  29.722 ms !N  20.103 ms !N

     

     Thanks,

    Jay