On Tue, Oct 22, 2013 at 03:59:42PM -0600, Stacy W. Smith wrote:
> Because you are injecting traffic with ping and "bypass-routing interface
> lt-1/1/10.771" logical-system a is NOT the first-hop router. It's simply
> acting as a multicast source that's pumping traffic with destination IP
> 225.1
2013 8:49 AM
To: Antonio Sanchez Monge mailto:amo...@juniper.net>>
Cc: "Stacy W. Smith" mailto:st...@acm.org>>,
"juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>"
mailto:juniper-nsp@puck.nether.net>>
Subject: Re: [j-nsp] ng-mvpn problem
Hello,
You are always right :) Everything works as expected now.
Thanks,
Mihai
On Wed, Oct 23, 2013 at 2:04 AM, Antonio Sanchez-Monge
wrote:
> Agreed, that should do the trick too :)
>
>
> On 10/23/13 1:01 AM, "Stacy W. Smith" wrote:
>
> >Agreed.
> >
> >The lt-1/1/10.770 interface which is i
Agreed, that should do the trick too :)
On 10/23/13 1:01 AM, "Stacy W. Smith" wrote:
>Agreed.
>
>The lt-1/1/10.770 interface which is in VRF mvpn on logical-system x must
>have PIM enabled (or multicast forwarding enabled). If running PIM, it
>must be the DR.
>
>I wasn't suggesting disabling P
Agreed.
The lt-1/1/10.770 interface which is in VRF mvpn on logical-system x must have
PIM enabled (or multicast forwarding enabled). If running PIM, it must be the
DR.
I wasn't suggesting disabling PIM on the lt-1/1/10.770 interface which is in
VRF mvpn on logical-system x, just disabling PI
You need PIM in the interface towards the source IMHO
On 10/23/13 12:47 AM, "Stacy W. Smith" wrote:
>Yes, that would also work, but since logical-system a is really just
>emulating a multicast source, there's really no need for it to run PIM. A
>typical multicast source would not be running PI
Yes, that would also work, but since logical-system a is really just emulating
a multicast source, there's really no need for it to run PIM. A typical
multicast source would not be running PIM.
--Stacy
On Oct 22, 2013, at 4:44 PM, Antonio Sanchez-Monge wrote:
> Solution would be setting a high
Solution would be setting a higher PIM priority in lt-1/1/10.770, so that
it becomes the DR
On 10/23/13 12:40 AM, "Antonio Sanchez-Monge" wrote:
>That's a brilliant analysis Stacy, I think you nailed it (awaiting Mihai's
>confirmation).
>
>
>On 10/22/13 11:59 PM, "Stacy W. Smith" wrote:
>
>>
That's a brilliant analysis Stacy, I think you nailed it (awaiting Mihai's
confirmation).
On 10/22/13 11:59 PM, "Stacy W. Smith" wrote:
>On Oct 22, 2013, at 2:44 PM, Mihai wrote:
>> Removing PIM fromlt-1/1/10.770 is not a solution because the PE will
>>not learn about the source and the multic
On Oct 22, 2013, at 2:44 PM, Mihai wrote:
> Removing PIM fromlt-1/1/10.770 is not a solution because the PE will not
> learn about the source and the multicast group.
Actually, removing lt-1/1/10.770 from PIM would allow the source and multicast
group to be learned, and fix the problem (as long
Do understand correctly that the source of the traffic is a logical-system on
the same router? How are you generating the multicast traffic?
I believe the issue is running PIM on the first-hop interface facing the
source. The router is expecting either PIM-register encapsulated traffic from
ups
You understand correctly. The source,PE's and the receiver are on the
same MX running Junos 12.3R3.4.
Removing PIM from lt-1/1/10.770 is not a solution because the PE will
not learn about the source and the multicast group.Changing the
multicast group didn't change anything.
mx# run ping logi
Junos version?
> On 22/10/2013, at 20:20, "Mihai" wrote:
>
> 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 t
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
fam
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" wrote:
>Hello,
>
> I have a basic setup with 2 PE's (X and Z) , one multicast source
>attached
>to X and one receiver attached t
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
16 matches
Mail list logo
