...
Below is a description of how to configure them and a little explanation of what they do.
| Table of Contents |
|---|
Credentials (for connecting to devices)
conf/credential_sets.nmis holds the credential sets that are used when connecting to a device. Even if auto discovery is not use the credentials still need to live in this file.
...
| Code Block |
|---|
chmod 600 conf/credential_sets.nmis |
Connections
Connections tell opConfig how to connect to the devices you would like to gather configuration data from. Connections can be auto-discovered if opConfig is attached to an NMIS configuration.
...
NOTE: If the command_sets you want to run filter based on os_info then you will need to define the required data in order for opConfig-cli.pl to match the connections you require. At the very least os_info->os will need to be defined but for many devices it is likely you will want to define more than that so your command sets can target the device with better commands.
Command Sets
A default command_sets.nmis file is provided. It defines a list of "command sets" to be run on devices that match the criteria laid out by each specific command set (usually by the os_info hash inside the command set). As many sets as you like can be added, with as many commands as you like.
...
A quick note, every opConfig try and bundle as many commands for the same device together into a single session (or connection if you like). If you would like the command set, or the individual command to be run on it's own connection (a good idea for long running commands), you can set run_commands_on_separate_connection => 'true' to run each command in that command set on it's own, or run_command_on_separate_connection => 'true' to run that specific command on it's own.
Running command sets
| Code Block |
|---|
bin/opConfig-cli.pl act=run_command_sets |
...