DeviceConfigMonitor
This monitor tries to retrieve configuration from the network device and shows the status of that retrieval (success, failed, and so on).
Configuration and use
Parameter |
Description |
Default value |
Required |
||
script-file |
Script file to use to retrieve configuration.
Place script files in the |
default.dcb |
username |
Username for SSH login.
Overwrite in metadata as |
admin |
password |
Password for SSH login.
Overwrite in metadata as |
admin |
Optional |
||
config-type |
If device has multiple configurations, specify the config-type with each service.
The config-type and service name suffix should match (kebab-case for service name, camelCase for config-type).
Overwrite in metadata as |
default |
ssh-port |
SSH port for the target device.
Overwrite in meatadata as |
22 |
ssh-timeout |
SSH maximum timeout after which SSH session will be closed.
Overwrite in metadata as |
60000 |
schedule |
Schedule to fetch configuration, in the form of cron expression.
Defaults to never run; overwrite this in metadata with proper cron expression.
Overwrite in metadata as |
never |
retention-period |
Maximum retention period after which configs without any updates will be deleted from database.
Overwrite in metadata as |
P1Y |
host-key |
SSH fingerprint of the remote host key.
If this is specified, the provided fingerprint will be used to verify the host key of the remote host.
The key must be encoded as |
unchecked |
auth-key |
SSH Private key used to authenticate. This must be specified in PEM format. If unspecified, key authentication is not used. |
unused |
shell |
If specified, this command is executed on the remote host instead of a login shell. |
Default login shell |
Schedule and interval
The service uses an interval of 300 seconds and a cron expression for the schedule. The monitor checks every 300 seconds (interval) for the next trigger time in the cron schedule. It retrieves the configuration only when the next trigger time matches the current time (current time must be greater than the trigger time). For example, if the monitor checks at 11:59 p.m., but the trigger time is 12:00 a.m., the monitor will retrieve the configuration at the next check interval at 12:04 a.m.