[j-nsp] EX3400 experiences / software recommendation

[Gert Doering]

Hi,

On Wed, Dec 06, 2017 at 07:53:36AM -0600, Aaron Gould wrote:
> Your comment... "(And yes, there's virtualization things connected to these
> switches, so VLANs *do* change... which shouldn't be something to worry
> about, no?)"
> 
> If you are referring to servers running virtualization needing various
> vlans... It's been my experience that I work with the linux/server guys and
> they tell me what vlans they will need and I create that interface to have
> all those vlans... 

This is what I do as well (plus, only on the trunks where it's needed,
and not on trunks going elsewhere - like, there is an ESX virtualization
farm, and an AIX Power8 virtualization thingie, and only some of the VLANs
need to be on both).  So, I do add and remove VLANs frequently - and with
other boxes (EX3300, everything from Cisco) this never caused any issues...

> you might be able to trunk and allow all vlans (1-4094 or
> whatever that top vlan number is :) .... I'm usually more controlling than
> that and add only the vlan tag id's they require.

Well, you might be able to set "vlan members all" on the interface, but
unless you actually create all these VLANs on the switch as well, it
won't do much - if a 802.1q tages comes in for an unknown-to-switch VLAN,
it will just drop it, as there's no bridge table for it, etc.

And no, creating all 4095 VLANs "just in case" is not something I'm
going to try :-)   (but I will postpone vlan changes until after the
upgrade, or to a maintenance window where I can reboot afterwards).

gert

-- 
now what should I write here...

Gert Doering - Munich, Germany                             gert at greenie.muc.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 630 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20171206/e803adc0/attachment.sig>