[j-nsp] vmember limits in EX series stack

[Nick Kritsky]

On Tue, May 1, 2012 at 5:35 PM, Chuck Anderson <cra at wpi.edu> wrote:
> On Mon, Apr 30, 2012 at 08:15:59PM -0700, Naveen Nathan wrote:
>> To manually specify the members for each downstream switch trunk port
>> requires a significant amount of administrative overhead. I would prefer
>> each trunk port just allow all the vlans.
>
> Doesn't that mean you are effectively always sending all broadcast
> traffic on all VLANs down every port?  That seems pretty pessimal.
> Perhaps you could use GVRP or MVRP to automatically maintain VLAN
> memberships.

According to relnotes, GVRP is no longer supported after 11.1.
MVRP could work but I am not sure about cisco-juniper interoperability here.

As per original question, Juniper states pretty clearly:
"If you ignore the warning and
commit such a configuration, the configuration succeeds but you run
the risk of crashing
the Ethernet switching process (eswd) due to memory allocation failure."

If you plan to enable all downstream ports as trunks with "vlan
members all", you are going to exceed this limit not just for 10% but
more than twice. I would not recommend this risk :)