On Feb 2, 2010, at 1:47 PM, Donour Sizemore wrote: > > On Feb 2, 2010, at 2:25 PM, James Carlson wrote: > >>>> If I have "vlan-announce" set to >>>> "gvrp" and I have only (say) "e1000g0" plumbed, do I get empty GVRP >>>> messages? >>> >>> No. Empty messages aren't sent. >> >> In that case, is there much harm in enabling the feature by default and >> asking users to disable if they don't like it? It seems like (despite >> the inherent problems) it could be a generally helpful thing, along the >> lines of IGMP. > > When there are no VIDs that need to be registered, it just parks the worker > thread. If GVRP is disabled the thread doesn't even exist. > > When there are VIDs, there can performance impact if you aren't actually > using GVRP -- especially on fast links. GVRP JOIN_IN requests must be > resent periodically. A common default from switch manufacturers is 250ms. > That means that GVRP has to grab the perimeter every 250ms. > > Nicolas, what do you think?
Yes there is the performance issue, but I'm more concerned that enabling the feature by default would cause these GVRP messages to start propagating on the networks of our customers who have configured VLANs. It's fine to use these messages in an environment which is expecting them to perform VLAN configuration, such as a cloud-like infrastructure. However GVRP messages might not be welcome in other environments where all VLAN configuration is done from the switch side, and no such messages are expected to be seen on the network. Nicolas. -- Nicolas Droux - Solaris Kernel Networking - Sun Microsystems, Inc. nicolas.droux at sun.com - http://blogs.sun.com/droux
