[AusNOG] Work experience in networking/telecoms/DCs? Getting my foot in the door?

[Damien Gardner Jnr]

Or just do like the rest of us and copy, paste, add new vlan on the end? ;-p

On 24 December 2014 at 12:00, Jacob Bisby <ausnog at jdmnet.com.au> wrote:

> In all fairness, you could also alleviate the problem with a much simpler
> "alias" configuration line. No need for an orchestration system to change
> VLAN configs.
>
> - Jacob Bisby
>
> -----Original Message-----
> From: AusNOG [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Chris
> Bennett
> Sent: Wednesday, 24 December 2014 8:17 AM
> To: Nathan Brookfield
> Cc: Cameron Ferdinands; ausnog at lists.ausnog.net
> Subject: Re: [AusNOG] Work experience in networking/telecoms/DCs? Getting
> my
> foot in the door?
>
> > You just gave me shudders with the memories of that one Andy, I've
> > seen that happen on a very big network,
>
> This kind of war story (I've done it too) is one of the simplest examples
> of
> where policy-based deployment / SDN can be harnessed.
>
> From the puppet/chef/ansible world, you would express the addition of a
> vlan
> in plainer english terms, and your orchestration system goes off and does
> it
> (without any of the risk of omitting the word 'add' :) ).
>
> > my favorite though is adding VLAN's to an ether channel port directly
> > and not to the port-channel directly 'sigh'.
>
> Yup, I've seen a customer work interface by interface slowly killing the
> redundancy in a port-channel as they amend the vlan list on the physicals.
>
> However there are still some older switches (3750's in my experience) with
> certain code releases where you amend the vlan list on the port-channel, it
> applies to the running config of both port-channel & physical, but then in
> startup-config, only commits the vlan to the port-channel.  It's left as an
> exercise to the reader as to what happens on next-boot for the port-channel
> on that switch :)
>
> This where the programmer part of a network engineer is needed - I wrote an
> explicit test in my monitoring system that detects a vlan mismatch between
> the running & saved version of a config so myself & colleagues never get
> caught by this kind of problem again :)
>
> Regards,
>
> Chris
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
> database 10922 (20141223) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>



-- 

Damien Gardner Jnr
VK2TDG. Dip EE. GradIEAust
rendrag at rendrag.net -  http://www.rendrag.net/
--
We rode on the winds of the rising storm,
 We ran to the sounds of thunder.
We danced among the lightning bolts,
 and tore the world asunder
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20141224/e01449f3/attachment.html>