"Its not supported" is the wrong phrase.  "Its broken" is more appropriate.  
Whatever design choices that were made in the past that led to this, as you 
said, "mind-blowing" caveat, Juniper needs to go backwards and fix it.

On Tue Aug 31st, 2010 8:01 AM CDT Chris Evans wrote:

>Try configuring an irb, igmp, igmp-snooping and a trunk port on 10.x code.
>It will tell you its not supported.  It's never been supported per JTAC.
>Also as per jtacs comment they put that statement in newer code as they
>didn't know it wasnt supported before.  I asked jtac to update the
>documentation.
> > Is this in documentation somewhere? I just did a quick pass through the
>IGMP
>> snooping docs and I did not see it stated anywhere in there... maybe I
>missed
>> it.
>>
>>
>>
>>
>>
>> ________________________________
>> From: Derick Winkworth <dwinkwo...@att.net>
>> To: Chris Evans <chrisccnpsp...@gmail.com>; Gavin Tweedie <g...@narx.net>
>> Cc: juniper-nsp@puck.nether.net
>> Sent: Tue, August 31, 2010 7:13:37 AM
>> Subject: Re: [j-nsp] 10.3 on MX960 with MPC only?
>>
>> ###########
>> I'm not even going to mention that
>>
>> IGMP-Snooping isn't support on trunk interfaces which blows my mind.
>> ############
>>
>>
>> wow!
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to