This could be related to the fact that in earlier versions base interface was not available when VLAN was configured on top of it. In this case difference between create and add makes sense.
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Mike Brown Sent: Wednesday, February 11, 2015 10:47 PM To: toasters@teaparty.net Subject: VLAN create vs. VLAN add
Thought I'd give this mailing list a try with a softball:
I get the difference between vlan create and vlan add in 7-mode:
"If a physical interface does not belong to any VLAN, you can use the vlan create command to make the interface a member of one or more VLANs. However, if the interface is already a member of a VLAN, you should use the vlan add command to add the interface to subsequent VLANs."
but what's so different about each command behind the scenes such that using "add" is better if a VLAN interface has already been created for an interface group?
I've been using "vlan create" in my /etc/rc files for years without noticing a difference. I'll update the way I use each command, but I was wondering what *real* difference was between the two (not just *when* to use them).
So in programming, sometimes, one operation is simply more efficient than another or can be completed in less steps, cycles, instructions, or perhaps with some atomicity. I was thinking this might be the reason, but what do you think?
Thanks,
Mike
--
Mike Brown michael.b.brown3@gmail.commailto:michael.b.brown3@gmail.com Blog: http://VirtuallyMikeBrown.com Twitter: http://twitter.com/VirtuallyMikeBhttp://twitter.com/#%21/VirtuallyMikeB LinkedIn: http://linkedin.com/in/michaelbbrown