Setting up a Device.CLI.Modify Config activity
|Top Previous Next|
Create a new Activity and select Device.CLI.Modify Config as the Activity Type:
Leave the other options on this tab at their defaults.
Select, for instance, "At Midnight" as the Recurring option in the Times box to run the activity every night at midnight.
Leave all other options on this tab at their defaults.
Select the Devices you want to configure from your CatTools Host.
Set preferences for reporting on this Activity.
Config commands to be entered into the device (Max 10,000 chrs):
This field is where you enter the specific commands to change the configuration of the selected device(s). On a Cisco IOS router, for example, these are commands that you would normally enter in config mode (after entering "config term" at the Enable prompt).
So in a simple example, if you want to change the VTY login password for the router you would enter the following commands in this field:
Line vty 0 4
CatTools will enter config mode and execute these commands exactly as you write them in this field, so be sure to write them exactly as you would if you were configuring the device manually via a telnet session.
Each command must be entered on a separate line. If you enter a blank line between commands then this will be applied just as if you pressed enter in a telnet session.
There is a limit on the size of this field, which is 10,000 characters. This gives you considerable room for putting together quite sophisticated configuration changes.
Within the commands, you can use a number of variables that are replaced by actual values when the commands are presented to the device. See the section Command Variables for a list of variables you can use.
You may also enter meta commands in the list of commands. See the section Meta Commands for an explanation.
The next option is: Or, read commands from file:
This option is preceded by a check-box and is followed by a normal path/filename entry field.
(This option and the one above it are mutually exclusive. If you check the box then the config commands field is deactivated, and the commands are only read from the text file you specify here.)
The rules for entering commands in the text file are the same as they are for entering them in the config commands field. Every line is read as a command to be entered in the devices config mode. A blank line between commands is read as an <Enter>.
The major difference between the two methods is that the text file doesn't have a limit on the number of characters like the config command field does.
Save device output to file: also has a check box and a path/filename field. It is checked by default, and the default filename is based on the device name and the date.
This is basically a device-specific record of each time the activity runs. All output from the device is recorded in the text file, exactly as it would appear in a telnet session.
Each device selected creates its own unique output file.
The following options are all check boxes and all are checked by default.
Overwrite existing capture file: Overwrites the file created by the output from the last run of this Activity. If unchecked, the file is appended, but a new file is created each time the date changes.
Answer [yes] to any confirmation prompts: some commands have confirmations prompts ("are you sure? Y or N") – so the program will automatically answer them in the affirmative, on the assumption that if you entered the commands you actually want them to be executed. If this option is unchecked, then the activity will enter an "n" in response to any confirmation requests.
Stop on error: Aborts the activity immediately on any error condition.
Save running config to start-up config when complete: copies the running config on the device to non-volatile memory, so that the modified config becomes the start-up config.