I like that a VLAN is only added if needed as we use VTP to sync the VLAN databases across the switches. Adding the VLAN once is enough then :-) -----Original Message----- From: racktables-users-bounce@xxxxxxxxxxxxx [mailto:racktables-users-bounce@xxxxxxxxxxxxx] On Behalf Of Denis Ovsienko Sent: Friday, July 11, 2014 2:50 PM To: racktables-users@xxxxxxxxxxxxx Subject: [racktables-users] Re: 802.1q VLAN propagation 11.07.2014, 12:34, "Christof" <mail@xxxxxxxxxxx>: > Hi List, > > i'm testing the 802.1q feature in racktables 0.20.8 at the moment. My > goal was to manage my vlans completely and I was quite satisfied up to > now. But I stuck. > My intend was to propagate a newly created vlan to all switches in a > 802.1q domain as it is created. But as it seems racktables only > configures the new vlan on a switch if something changed (i.e. port in > any other vlan). > > Is there any way to tell racktables, to add a vlan on creation? Hi Christof. This feature was designed to keep the list of VLANs on each switch as short as possible, that is, to remove (or not to add) a VLAN from the switch unless at least one port uses that VLAN or the VLAN propagation is set to "permanent" (the default is "auto"). As far as the code reads now, RackTables would _not_ put all the switches of a domain to the sync queue after the user added/removed a "permanent" VLAN to/from that domain. If so, this could be a space for improvement, yes. -- Denis Ovsienko
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
