Routing

last person joined: 3 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.  MVPN Pruned Forwarding state

    Posted 05-28-2015 09:40
      |   view attached

    Hello,

    I am trying to make work a simple MVPN scheme, a topology picture is attached.  The sender is on the left with an ip 172.15.0.100 sending to group 239.1.2.3, sender site's PE stays in Pruned state despite all necessary conditions to forward:

     

    root@Tokyo# run show pim join extensive instance Red
    Instance: PIM.Red Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard

    Group: 224.0.1.40
        Source: *
        RP: 172.17.17.17
        Flags: sparse,rptree,wildcard
        Upstream interface: Local
        Upstream neighbor: Local
        Upstream state: Local RP
        Uptime: 00:28:33
        Downstream neighbors:
            Interface: ge-0/0/1.0
                172.17.0.1 State: Join Flags: SRW  Timeout: Infinity
                Uptime: 00:28:33 Time since last Join: 00:28:33
                172.17.0.100 State: Join Flags: SRW Timeout: 195
                Uptime: 00:27:46 Time since last Join: 00:00:14
        Number of downstream interfaces: 1

    Group: 239.1.2.3
        Source: 172.15.0.100
        Flags: sparse,spt
        Upstream interface: ge-0/0/1.0
        Upstream neighbor: 172.17.0.100
        Upstream state: Local RP, Join to Source
        Keepalive timeout: 329
        Uptime: 00:21:27
        Downstream neighbors:
            Interface: Pseudo-MVPN
                Uptime: 00:21:27 Time since last Join: 00:21:27
        Number of downstream interfaces: 1

    Instance: PIM.Red Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard





    root@Tokyo# run show multicast route extensive instance Red
    Instance: Red Family: INET

    Group: 239.1.2.3
        Source: 172.15.0.100/32
        Upstream interface: ge-0/0/1.0
        Number of outgoing interfaces: 0
        Session description: Organisational Local Scope
        Statistics: 134 kBps, 89 pps, 101670 packets
        Next-hop ID: 0
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Pruned
        Cache lifetime/timeout: 360 seconds
        Wrong incoming interface notifications: 1
        Uptime: 00:19:23

    Instance: Red Family: INET6



    root@Tokyo# run show route table Red.mvpn.0

    Red.mvpn.0: 5 destinations, 6 routes (5 active, 1 holddown, 0 hidden)
    + = Active Route, - = Last Active, * = Both

    1:1.1.1.1:1:1.1.1.1/240
                       *[MVPN/70] 00:29:14, metric2 1
                          Indirect
    1:2.2.2.2:1:2.2.2.2/240
                       *[BGP/170] 00:26:02, localpref 100, from 2.2.2.2
                          AS path: I, validation-state: unverified
                        > to 10.1.0.2 via ge-0/0/0.0, Push 299792
    5:1.1.1.1:1:32:172.15.0.100:32:239.1.2.3/240
                       *[PIM/105] 00:20:11
                          Multicast (IPv4) Composite
    6:1.1.1.1:1:65111:32:172.17.17.17:32:224.0.1.40/240
                       *[PIM/105] 00:27:17
                          Multicast (IPv4) Composite
    7:1.1.1.1:1:65111:32:172.15.0.100:32:239.1.2.3/240
                       *[PIM/105] 00:20:11
                          Multicast (IPv4) Composite
                        [BGP/170] 00:20:11, localpref 100, from 2.2.2.2
                          AS path: I, validation-state: unverified
                        > to 10.1.0.2 via ge-0/0/0.0, Push 299792

     

    Where could be the issue with this setup? 

     

    Thanks in advance!



  • 2.  RE: MVPN Pruned Forwarding state

    Posted 05-29-2015 03:25

    Ok, seems to be p2mp was missed in the ldp section of listeners' PE and P

     

    root@Tokyo# run show multicast route instance Red extensive
    Instance: Red Family: INET

    Group: 239.1.2.3
        Source: 172.17.0.100/32
        Upstream interface: ge-0/0/1.0
        Downstream interface list:
            ge-0/0/0.0
        Number of outgoing interfaces: 1
        Session description: Organisational Local Scope
        Statistics: 134 kBps, 89 pps, 65040 packets
        Next-hop ID: 1048575
        Upstream protocol: MVPN
        Route state: Active
        Forwarding state: Forwarding
        Cache lifetime/timeout: forever
        Wrong incoming interface notifications: 0
        Uptime: 00:11:23

     

    But no traffic is leaving the sender PE , maybe problem is related to VirtualBox environment ? 



  • 3.  RE: MVPN Pruned Forwarding state
    Best Answer

    Posted 05-30-2015 19:57

    I used iperf and its default packet size  - 1470 , so   increasing mtu on interfaces has allowed the traffic to flow