Hi Angel,
In terms of having a regular execution of puppet device, you could utilise
the device_manager and set up a run_interval parameter:
https://forge.puppet.com/puppetlabs/device_manager#run_interval
which will set up a regular cron job.
Also, it is worth adding cisco_ios::server to your pu
I have it working and I can run puppet device to send configuration to
device.
Now, I would like to configure the agent proxy so I don't have to
manually run puppet device to send configuration to devices, but to
puppet agent doing it for me in every run. Is this possible, how do I
have to
Angel,
No problem, I'm very glad you found resolution to this!
I would be interested to hear any feedback you may have during usage of the
cisco_ios module.
And of course, community PRs are always welcome to the project :)
Thanks!
Regards,
Will
On Wednesday, December 5, 2018 at 1:05:06 PM
El 5/12/18 a las 12:11, Will Meek escribió:
Hi Angel,
Thank you for the detail so far!
The only way I can reproduce this on my setup is with having
puppetlabs-cisco_ios 0.5.0 installed in the production environment,
whereby puppet tries to pick up the old 'ios' provider rather than the
>0.6
Hi Angel,
Thank you for the detail so far!
The only way I can reproduce this on my setup is with having
puppetlabs-cisco_ios 0.5.0 installed in the production environment, whereby
puppet tries to pick up the old 'ios' provider rather than the >0.6.0
'cisco_ios' provider.
puppet device --verbo
I don't know what have I touch (if it's really my fault), but it's not
working again.
This is the manifest to configure the proxy agent:
node default {
include cisco_ios::proxy
device_manager {'switch_cisco_pruebas':
type => 'cisco_ios',
credentials => {
address =>
El 30/11/18 a las 15:16, Will Meek escribió:
Hi Angel,
I'm having a look at this now.
The manifest you supplied looks to be device_manager setup, which is
executed either by an agent (if set in an environment) or 'puppet apply'
rather than 'puppet device'.
This sets up the device.conf ready
Hi Angel,
I'm having a look at this now.
The manifest you supplied looks to be device_manager setup, which is
executed either by an agent (if set in an environment) or 'puppet apply'
rather than 'puppet device'.
This sets up the device.conf ready for puppet device.
Can you tell me if you get
