[j-nsp] ng-mvpn problem
Mihai
mihaigabriel at gmail.com
Tue Oct 22 14:20:03 EDT 2013
Hello,
lo0.777 has the rp address, and the lt-1/1/10.770 is the link between
PE and multicast source (it's a single MX with logical-systems and I
already tried the same setup with physical interfaces between PE and CE
with the same result):
x> show configuration interfaces lo0 unit 777
family inet {
address 20.20.20.111/32;
}
x> show configuration interfaces lt-1/1/10.770
description x-a;
encapsulation ethernet;
peer-unit 771;
family inet {
address 10.100.1.1/24;
}
On 10/22/2013 08:07 PM, Antonio Sanchez-Monge wrote:
> Hi Mihai,
>
> Doesn't ring a bell at first sight. What's the configuration of interfaces
> lo0.777 and lt-1/1/10.770 ?
>
> Thanks,
>
> Ato
>
>
>
>
> On 10/22/13 6:56 PM, "Mihai Gabriel" <mihaigabriel at gmail.com> wrote:
>
>> Hello,
>>
>> I have a basic setup with 2 PE's (X and Z) , one multicast source
>> attached
>> to X and one receiver attached to Z.
>> I configured a NG-MVPN with rsvp-te between PE's but X doesn't send SA
>> autodiscovery to Z so the traffic is dropped.
>>
>> x> show configuration routing-instances
>> mvpn {
>> instance-type vrf;
>> interface lt-1/1/10.770;
>> interface lo0.777;
>> route-distinguisher 1:1;
>> provider-tunnel {
>> rsvp-te {
>> label-switched-path-template {
>> default-template;
>> }
>> }
>> }
>> vrf-target target:1:1;
>> vrf-table-label;
>> protocols {
>> pim {
>> rp {
>> local {
>> address 20.20.20.111;
>> }
>> }
>> interface all;
>> }
>> mvpn;
>> }
>> }
>>
>>
>> z> show configuration routing-instances
>> mvpn {
>> instance-type vrf;
>> interface lt-1/1/10.772;
>> route-distinguisher 1:2;
>> provider-tunnel {
>> rsvp-te {
>> label-switched-path-template {
>> default-template;
>> }
>> }
>> }
>> vrf-target target:1:1;
>> vrf-table-label;
>> protocols {
>> pim {
>> interface all;
>> }
>> mvpn;
>> }
>> }
>>
>>
>> x> show multicast route instance mvpn extensive
>> Instance: mvpn Family: INET
>>
>> Group: 239.1.1.1
>> Source: 10.100.1.2/32
>> Upstream interface: lt-1/1/10.770
>> Session description: Organisational Local Scope
>> Statistics: 10 kBps, 10 pps, 1291 packets
>> Next-hop ID: 0
>> Upstream protocol: PIM
>> Route state: Active
>> Forwarding state: Pruned
>> Cache lifetime/timeout: 360 seconds
>> Wrong incoming interface notifications: 0
>> Uptime: 00:10:37
>>
>> Instance: mvpn Family: INET6
>>
>> x> show route receive-protocol bgp 20.20.20.2 table mvpn.mvpn.0
>>
>> mvpn.mvpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
>> Prefix Nexthop MED Lclpref AS path
>> 1:1:2:20.20.20.2/240
>> * 20.20.20.2 100 I
>>
>> z> show route receive-protocol bgp 20.20.20.1 table mvpn.mvpn.0
>>
>> mvpn.mvpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
>> Prefix Nexthop MED Lclpref AS path
>> 1:1:1:20.20.20.1/240
>> * 20.20.20.1 100 I
>>
>> x> show mpls lsp p2mp
>> Ingress LSP: 1 sessions
>> P2MP name: 1:1:mvpn:mvpn, P2MP branch count: 1
>> To From State Rt P ActivePath LSPname
>> 20.20.20.2 20.20.20.1 Up 0 *
>> 20.20.20.2:1
>> :1:mvpn:mvpn
>> Total 1 displayed, Up 1, Down 0
>>
>> Egress LSP: 1 sessions
>> P2MP name: 1:2:mvpn:mvpn, P2MP branch count: 1
>> To From State Rt Style Labelin Labelout LSPname
>> 20.20.20.1 20.20.20.2 Up 0 1 SE 16 -
>> 20.20.20.1:1:2:mvpn:mvpn
>> Total 1 displayed, Up 1, Down 0
>>
>> Transit LSP: 0 sessions
>> Total 0 displayed, Up 0, Down 0
>>
>> Am i doing something wrong?
>>
>> Thanks
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>
>
>
More information about the juniper-nsp
mailing list