Routing

 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.



  • 1.  L3VPN pinging issue

    Posted 10-13-2011 07:24

    Hi all

     

    I have setup a small network to test run a topology/config and am having some issues with L3vpn.

     

    I am running ISIS as IGP over a string of 4 routers.

     

    each end node ( PE ) has a BGP session with remote node for family inet-vpn unicast.

     

    the PE-CE interface has a laptop attached.

     

    Then I created a pair of LSPs between the PE nodes using RSVP.

     

    then I made a routing instance to include the Laptop interface.

     

    I am seeing the following:

     

    1.  The BGP sessions are up.

    2.  The LSPs are up

    3.  The remote PE loopback is listed in table inet.3 and points to the LSP.

    4.  I perform a traceroute to the remote PE loopback and see MPLS output in the traceroute ouput.  So it looks like the packets are following the LSP.

    5.  I added a static route into the routing-instance on each PE so I would advertise the CE-PE route via BGP.

    6.  I see the routes in the remote PE bgp.l3vpn.0 table and also into the remote PE VRF table, these look correct and list the correct LSP, Label values etc.

     

    7.  I can run the >ping mpls l3vpn <VPN-Name>  prefix <x> detail and get responses.

    8.  When I try to run >ping <x> routing-instance <VPN-Name> source <local PE-CE Interface IP>

          I get 100% packet loss.

     

    any ideas on what troubleshooting steps.

     

    I since connected these boxes back to back and it still gives the same issues?

     

    routing-options {                       
        router-id 195.166.196.8;
        autonomous-system 1111;
    }
    
    protocols {
        rsvp {
            interface ge-0/0/0.0;
            interface ge-0/0/1.0;
            interface ge-0/0/3.0;
            interface ge-0/0/4.0;
        }
        mpls {
            label-switched-path to-srx650-voice1 {
                to 10.0.9.10;
            }
            interface ge-0/0/0.0;
            interface ge-0/0/1.0;
            interface ge-0/0/3.0;
            interface ge-0/0/4.0;
        }                                   
        bgp {
            group Voice {
                type internal;
                local-address 195.166.196.8;
                log-updown;
                family inet-vpn {
                    unicast;
                }
                neighbor 10.0.9.10;
            }
        }
     isis {
            reference-bandwidth 10g;
            level 1 {
                disable;
            }
            level 2 {
                wide-metrics-only;
                preference 169;
                external-preference 169;
            }
            interface ge-0/0/0.0 {
                point-to-point;
            }
            interface ge-0/0/1.0 {
                point-to-point;
            }
            interface ge-0/0/3.0 {
                point-to-point;
            }
            interface ge-0/0/4.0 {
                point-to-point;
            }                               
            interface ge-2/0/0.0 {
                point-to-point;
                level 2 metric 60000;
            }
            interface lo0.0 {
                passive;
            }
        }
    }
    routing-instances {
        VoIP {
            instance-type vrf;
            interface ge-0/0/2.0;
            route-distinguisher 195.166.196.8:10012;
            vrf-target target:1111:10012;
            routing-options {
                static {
                    route 192.168.10.6/32 next-hop 192.168.10.6;
                }
            }
        }
    }
    
    srx240> show bgp summary 
    Groups: 1 Peers: 1 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    bgp.l3vpn.0            2          2          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    10.0.9.10              1111         56         53       0       0       20:46 Establ
      bgp.l3vpn.0: 2/2/2/0
      VoIP.inet.0: 2/2/2/0
    
    srx240> show route table bgp.l3vpn.0 detail 
    
    bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
    10.0.9.10:10012:10.20.1.0/24 (1 entry, 0 announced)
            *BGP    Preference: 170/-101
                    Route Distinguisher: 10.0.9.10:10012
                    Next hop type: Indirect
                    Address: 0x161fbf0
                    Next-hop reference count: 6
                    Source: 10.0.9.10
                    Next hop type: Router, Next hop index: 610
                    Next hop: 10.50.1.2 via ge-0/0/4.0 weight 0x1, selected
                    Label-switched-path to-srx650-voice1
                    Label operation: Push 299808
                    Label TTL action: prop-ttl
                    Protocol next hop: 10.0.9.10
                    Push 299808
                    Indirect next hop: 16980f0 262142
                    State: <Active Int Ext>
                    Local AS:  1111 Peer AS:  1111
                    Age: 14:19      Metric2: 10 
                    Task: BGP_1111.10.0.9.10+179
                    AS path: I
                    Communities: target:1111:10012
                    Import Accepted         
                    VPN Label: 299808
                    Localpref: 100
                    Router ID: 85.115.128.210
                    Secondary Tables: VoIP.inet.0
    
    10.0.9.10:10012:10.20.1.2/32 (1 entry, 0 announced)
            *BGP    Preference: 170/-101
                    Route Distinguisher: 10.0.9.10:10012
                    Next hop type: Indirect
                    Address: 0x161fbf0
                    Next-hop reference count: 6
                    Source: 10.0.9.10
                    Next hop type: Router, Next hop index: 610
                    Next hop: 10.50.1.2 via ge-0/0/4.0 weight 0x1, selected
                    Label-switched-path to-srx650-voice1
                    Label operation: Push 299808
                    Label TTL action: prop-ttl
                    Protocol next hop: 10.0.9.10
                    Push 299808
                    Indirect next hop: 16980f0 262142
                    State: <Active Int Ext>
                    Local AS:  1111 Peer AS:  1111
                    Age: 14:19      Metric2: 10 
                    Task: BGP_1111.10.0.9.10+179
                    AS path: I
                    Communities: target:1111:10012
                    Import Accepted
                    VPN Label: 299808
                    Localpref: 100
                    Router ID: 85.115.128.210
                    Secondary Tables: VoIP.inet.0
    
    
    @srx240> show route table VoIP detail 
    
    VoIP.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
    10.20.1.0/24 (1 entry, 1 announced)
            *BGP    Preference: 170/-101
                    Route Distinguisher: 10.0.9.10:10012
                    Next hop type: Indirect
                    Address: 0x161fbf0
                    Next-hop reference count: 6
                    Source: 10.0.9.10
                    Next hop type: Router, Next hop index: 610
                    Next hop: 10.50.1.2 via ge-0/0/4.0 weight 0x1, selected
                    Label-switched-path to-srx650-voice1
                    Label operation: Push 299808
                    Label TTL action: prop-ttl
                    Protocol next hop: 10.0.9.10
                    Push 299808
                    Indirect next hop: 16980f0 262142
                    State: <Secondary Active Int Ext>
                    Local AS:  1111 Peer AS:  1111
                    Age: 8:21       Metric2: 10 
                    Task: BGP_1111.10.0.9.10+179
                    Announcement bits (1): 1-KRT 
                    AS path: I
                    Communities: target:1111:10012
                    Import Accepted
                    VPN Label: 299808
                    Localpref: 100
                    Router ID: 85.115.128.210
                    Primary Routing Table bgp.l3vpn.0
    
    10.20.1.2/32 (1 entry, 1 announced)
            *BGP    Preference: 170/-101
                    Route Distinguisher: 10.0.9.10:10012
                    Next hop type: Indirect
                    Address: 0x161fbf0
                    Next-hop reference count: 6
                    Source: 10.0.9.10
                    Next hop type: Router, Next hop index: 610
                    Next hop: 10.50.1.2 via ge-0/0/4.0 weight 0x1, selected
                    Label-switched-path to-srx650-voice1
                    Label operation: Push 299808
                    Label TTL action: prop-ttl
                    Protocol next hop: 10.0.9.10
                    Push 299808
                    Indirect next hop: 16980f0 262142
                    State: <Secondary Active Int Ext>
                    Local AS:  1111 Peer AS:  1111
                    Age: 8:21       Metric2: 10 
                    Task: BGP_1111.10.0.9.10+179
                    Announcement bits (1): 1-KRT 
                    AS path: I
                    Communities: target:1111:10012
                    Import Accepted
                    VPN Label: 299808
                    Localpref: 100
                    Router ID: 85.115.128.210
                    Primary Routing Table bgp.l3vpn.0
    
    srx240> ping mpls l3vpn VoIP prefix 10.20.1.1 detail                
    Request for seq 1, to interface 75, label 299808, packet size 88 
    Reply for seq 1, return code: Egress-ok, time: 215363.705 ms
            Local transmit time: 2011-10-14 00:19:43 CEST 566.205 ms
            Remote receive time: 2011-10-14 00:23:18 CEST 929.910 ms
    Request for seq 2, to interface 75, label 299808, packet size 88 
    Reply for seq 2, return code: Egress-ok, time: 215363.712 ms
            Local transmit time: 2011-10-14 00:19:44 CEST 566.549 ms
            Remote receive time: 2011-10-14 00:23:19 CEST 930.261 ms
    Request for seq 3, to interface 75, label 299808, packet size 88 
    Reply for seq 3, return code: Egress-ok, time: 215363.569 ms
            Local transmit time: 2011-10-14 00:19:45 CEST 566.717 ms
            Remote receive time: 2011-10-14 00:23:20 CEST 930.286 ms
    Request for seq 4, to interface 75, label 299808, packet size 88 
    Reply for seq 4, return code: Egress-ok, time: 215363.437 ms
            Local transmit time: 2011-10-14 00:19:46 CEST 567.205 ms
            Remote receive time: 2011-10-14 00:23:21 CEST 930.642 ms
    Request for seq 5, to interface 75, label 299808, packet size 88 
    Reply for seq 5, return code: Egress-ok, time: 215363.534 ms
            Local transmit time: 2011-10-14 00:19:47 CEST 566.576 ms
            Remote receive time: 2011-10-14 00:23:22 CEST 930.110 ms
    
    --- lsping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    
    >srx240> ping 10.20.1.1 routing-instance VoIP source 192.168.10.5    
    PING 10.20.1.1 (10.20.1.1): 56 data bytes
    ^C
    --- 10.20.1.1 ping statistics ---
    5 packets transmitted, 0 packets received, 100% packet loss

     

     

     

     


    #bgp.l3vpn.0
    #ping
    #MPLS
    #L3VPN


  • 2.  RE: L3VPN pinging issue
    Best Answer

     
    Posted 10-13-2011 08:07

    hi,

     

    See http://www.juniper.net/techpubs/software/junos/junos95/swconfig-vpns/id-11085532.html#id-11073317 (Pinging the Remote CE Router from the Local PE Router).  Please notice the Limitation on Pinging ... section.

     

    I'm not sure and can't test now if  vrf-table-label discussed in http://forums.juniper.net/t5/Routing/BGP-label-allocation-failure-Need-a-nexthop-address-on-LAN/m-p/110112 will help.

    jtb

     



  • 3.  RE: L3VPN pinging issue

    Posted 10-13-2011 08:18

    Yes I managed to get access to the CE devices at each end and it was working all along!!!

     

    the caveat of not being able to ping from PE to CE sucks

     

    thanks