Re: [ansible-project] Building an ansible job to run customized CLI configurations

On Friday, 23 February 2018 21.42.00 CET Jonathan Umpleby wrote: > So here's an example: > > enable > ** > config terminal > appliance-name "*proxy1*" > > interface 0:0 ;mode > label "MGMT" > ip-address *10.0.0.100* 255.255.255.0 > exit > > interface 1:0 ;mode > label "unused" > reject-inbound

Re: [ansible-project] Building an ansible job to run customized CLI configurations

I mean I guess I can build them all out and may be easier, however I was hoping to figure out this iterative process mostly because I'm looking at rolling out somewhere around 100 appliances across the globe (not just proxySG), that will all need similar interface tweaks. On Friday, February

Re: [ansible-project] Building an ansible job to run customized CLI configurations

One of the many methods is to scp or sftp the full config as a template to the device and save as startup or running config and reload it. Then you don't need to muck around with as much expect logic. On Fri, Feb 23, 2018 at 2:42 PM, Jonathan Umpleby wrote: > So here's an

Re: [ansible-project] Building an ansible job to run customized CLI configurations

So here's an example: enable ** config terminal appliance-name "*proxy1*" interface 0:0 ;mode label "MGMT" ip-address *10.0.0.100* 255.255.255.0 exit interface 1:0 ;mode label "unused" reject-inbound enable disable exit interface 1:1 ;mode label "VLAN TAG#" ip-address *10.0.0.10*

Re: [ansible-project] Building an ansible job to run customized CLI configurations

On Thursday, 22 February 2018 19.44.51 CET Jonathan Umpleby wrote: > So, I'm new to ansible, and I'm hoping to find ways to meet a > customize-able CLI deployment scenario, where 99% of the commands are the > same across devices, but a handful will be unique. > > I was originally thinking about

[ansible-project] Building an ansible job to run customized CLI configurations

So, I'm new to ansible, and I'm hoping to find ways to meet a customize-able CLI deployment scenario, where 99% of the commands are the same across devices, but a handful will be unique. I was originally thinking about using a single response file would cover the 99% (in my example I'm trying