...
Credentials for all connections made by opConfig are configurable from the opConfig GUI ONLY. Before anything else you need to create sets of credentials to access you devices. At this point in time, opConfig supports only Telnet and SSH, and for SSH password-based authentication and RSA with no passphrase is supported.
Starting to Collect Data
Steps to set up your first automated job:
- Configure a device to to be supported by opConfig.
- Create a configuration set
- Schedule a job. There are several ways of schedule a job:
- Create a new virtual operator job: Using the GUI we can create a new job that could be run in a specific time and hour. Note that this option will run once.
- Using the CLI Tool: With the configuration option push_configset.
- Cron job: For the execution of tasks periodically, usually based in the tags of the configurations. An example of some cron jobs for opConfig:
| Code Block |
|---|
# opConfig: hourly command set running
1 * * * * root /usr/local/omk/bin/opconfig-cli.pl quiet=1 act=run_command_sets tags=HOURLY
# and the daily ones
7 7 * * * * root /usr/local/omk/bin/opconfig-cli.pl quiet=1 act=run_command_sets tags=DAILY
# and a daily import from open-audit enterprise
21 4 * * * root /usr/local/omk/bin/opconfig-cli.pl quiet=1 act=import_audit
# and a daily purge of old revisions
40 3 * * * root /usr/local/omk/bin/opconfig-cli.pl act=purge_revisions quiet=1 |
It is also important to review and set accordingly the purging policies.
Related readings
...
...