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.  Multicast VPN with RSVP-TE P2PM LSPs [problem]

    Posted 09-02-2013 08:17

    Dear all,

     

    I'm trying to set up an MVPN in a lab environment using logical-systems. I got an Mx-480, and I have set up the following network using logical-systems with lt interfaces:

     

      CE1 --- PE1 --- P --- PE2 --- CE2

     

    Multicast source (192.168.2.22) is behind CE2, transmiting traffic towards the multicast group 225.1.1.1

    The receiver is connected to CE1 (192.168.11.1 ).

    The RP (10.10.1.22) is statically configured on PE2. All the routers have this static configuration.

     

    All the BGP signaling between PE1 (10.10.1.1) and PE2 (10.10.2.2) seems to work, and the LSP seems to be up.

    Although PE2 receives the multicast traffic, this traffic is not forwarded into the LSP towards PE1, and I dont know why. I dont know if it's a matter of wrong configuration in the basics of MVPN, or any special command that must be activated because I'm using logical-systems.

     

    Some outputs from PE2:

     

    routerpe2@Mx480-re1:PE2> show multicast route instance CE2 detail
    Family: INET

     

    Group: 225.1.1.1
    Source: (null)/0
    Upstream interface: local
    Downstream interface list:
    lt-0/0/0.3
    Session description: MALLOC
    Forwarding statistics are not available
    Next-hop ID: 1048590
    Upstream protocol: MVPN

     

    Group: 225.1.1.1
    Source: 192.168.22.2/32
    Upstream interface: ge-0/0/0.202
    Downstream interface list:
    lt-0/0/0.3
    Session description: MALLOC
    Statistics: 0 kBps, 1 pps, 2663 packets
    Next-hop ID: 1048590
    Upstream protocol: MVPN

    Family: INET6

     

    routerpe2@Mx480-re1:PE2> show route table CE2.mvpn.0

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

     

    1:10.10.1.1:1:10.10.1.1/240
    *[BGP/170] 00:19:22, localpref 100, from 10.10.1.1
    AS path: I
    > to 10.10.12.2 via lt-0/0/0.3, label-switched-path pe2-to-pe1

     

    1:10.10.2.2:1:10.10.2.2/240
    *[MVPN/70] 3d 07:15:03, metric2 1
    Indirect

     

    6:10.10.2.2:1:65001:32:10.10.1.22:32:225.1.1.1/240

    *[PIM/105] 00:52:55
    Multicast (IPv4)
    [BGP/170] 00:19:22, localpref 100, from 10.10.1.1
    AS path: I
    > to 10.10.12.2 via lt-0/0/0.3, label-switched-path pe2-to-pe1

     

    7:10.10.2.2:1:65001:32:192.168.22.2:32:225.1.1.1/240
    *[PIM/105] 00:50:29
    Multicast (IPv4)

     

    routerpe2@Mx480-re1:PE2> show rsvp session statistics

     

    Ingress RSVP: 3 sessions
    To                From        State Packets Bytes LSPname
    10.10.1.1   10.10.2.2 Up     0              0 pe2-to-pe1
    10.10.1.1   10.10.2.2 Up     0              0 10.10.1.1:10.10.2.2:1:mvpn:CE2
    10.10.5.5   10.10.2.2 Up     0              0 pe2-to-p1
    Total 3 displayed, Up 3, Down 0

     

     

    Some outputs from PE1:

     

    routerpe1@Mx480-re1:PE1> show pim join instance CE1
    Instance: PIM.CE1 Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard

     

    Group: 225.1.1.1
    Source: *
    RP: 10.10.1.22
    Flags: sparse,rptree,wildcard
    Upstream protcol: BGP
    Upstream interface: Through BGP

     

    Group: 225.1.1.1
    Source: 192.168.11.1
    Flags: sparse
    Upstream interface: ge-0/0/0.201

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

     

    routerpe1@Mx480-re1:PE1> show multicast route instance CE1 detail
    Family: INET

     

    Group: 225.1.1.1
    Source: (null)/0
    Upstream interface: lsi.16777728
    Downstream interface list:
    ge-0/0/0.201
    Session description: MALLOC
    Statistics: 0 kBps, 0 pps, 0 packets
    Next-hop ID: 1048583
    Upstream protocol: MVPN

    Family: INET6

     

    The routing-instance configuration on PE2 is as follows:

     

     

    routing-instances CE2

    instance-type vrf;
    interface ge-0/0/0.202;
    interface lo0.22;
    route-distinguisher 10.10.2.2:1;
    provider-tunnel {
    rsvp-te {
    label-switched-path-template {
    P2MP;
    }
    }
    }
    vrf-target target:65001:1;
    vrf-table-label;
    routing-options {
    multicast {
    ssm-groups 225.1.0.0/16;
    }
    }
    protocols {
    ospf {
    export OSPF-VPN;
    area 0.0.0.0 {
    interface ge-0/0/0.202 {
    interface-type p2p;
    }
    }
    }
    pim {
    rp {
    local {
    address 10.10.1.22;
    }
    }
    interface ge-0/0/0.202;
    interface lo0.22;
    }
    }
    }
    }
    mvpn {
    mvpn-mode {
    rpt-spt;
    }
    }
    }

     

    Could any one help me with this issue?

     



  • 2.  RE: Multicast VPN with RSVP-TE P2PM LSPs [problem]

     
    Posted 09-03-2013 05:04
    What is the purpose defining 225.1/16 as SSM?


  • 3.  RE: Multicast VPN with RSVP-TE P2PM LSPs [problem]

    Posted 09-03-2013 07:05

    That's because I started using Source Specific Multicast, with shortest path tree, IGMPv3 and the multicast group 225.1.1.1 (ssm group address range is 232/8). But because I couldnt manage to make it work, I moved to shared path tree, without succeed.

     



  • 4.  RE: Multicast VPN with RSVP-TE P2PM LSPs [problem]
    Best Answer

    Posted 09-06-2013 03:31

    I finally made the lab to work. It was a matter of JunOS version.

    For anyone trying to test MVPN with logical-systems in a lab: you must use JunOS release 12.1 or later. With a previous release, all the signaling process will be ok, but the data plane won't work.

    I installed the release 13.2, and it works, even without vt interfaces (it's enough activating vrf-table-label)