From the Command Line

All of the scripts can be run from the command line for both Unix/Linux and MS Windows. They are run by typing in the individual program name and options. There are slight differences in the setup between running the scripts from Unix/Linux and MS Windows. Note, it is much more common to run the scripts from the command line in Linux, than it is for Windows. In Linux, shell scripts can be built which may contain many scripts all in one shell wrapper.

When running the scripts from the command line, the setup.var file is read from the current directory you are running the script from. If the setup.var does not exist in the current directory, it will automatically be created by the program. When it is created, the SCRIPT_HOME variable will get set to the current directory.

For MS Windows, the scripts are run from the cmd tool window (Start->All Programs->Accessories->command promt).

Although the scripts can be run from any directory, in order to stay organized, it is recommended they be run from the following directories or any new directories you create under these directories:

Below is a list of executable filenames for each of the scripts when run from the command line:

Cisco IOS Scripts	Cisco Pro Scripts	Cisco CatOS Scripts	Cisco PIX Scripts	Generic Scripts	Miscellaneous
cisco_inventory_rpt	check_bgp_nbrs	catos_send_cmds	pix_send_cmds	generic_send_cmds	encrypt_logins
cisco_send_cmds	check_bgp_routes
cisco_send_cmds_rcf	check_eigrp_nbrs
cisco_send_indiv_cmds	check_eigrp_routes
cisco_passwd_change	config_devices_rvf
conf_bkup_show_run
config_cmds
config_devices
config_devices_rcf
config_interface
copy_to_tftp
flash_report
ios_report
ip_account
pinger
tracer

There are some generic options which may or may not apply to all of the scripts. In addition, there may be some required arguments as well as some script specific options. If the required arguments are not entered on the command line, the program will report an error. All programs can be run with the “-help” option to see generic options as well as the required arguments for the script. Below, shows an example of the ios_report program run with the –help option.

$ ios_report -help

*******************************************************
* For more information about Script Automation
* or support issues, contact Technical Support
* E-mail: support@net-sense.com
*******************************************************

-of <file>      Filename where output results are written

-pw <file>       Option for turning interactive off. When
               specified, script will not prompt user for passwords
               The filename with the login information must also
               be specified

-sf <file>      Sources the following file. Used if you need
               to provide additional input to the script
-rf <file>      File with a list of routers to run script against
               If this option is not required, then the script
               is not designed to cycle through a list of routers
-log <file>     File to save detailed trace of script run. If omitted,
               the default trace log file is <script_name.log>. The
               default trace log file will get over written each
               script run. If used, this should be the FIRST argument
               on the command line.

Required Arguments: -of -rf

$

Some options require a filename to be specified. In some cases that file will contain information that is needed by the script. Depending on the option, the format of the file may be a simple text file containing a list of routers or the file may be in TCL format. For the files that are in TCL format, TCL programming knowledge is NOT required. The TCL files edited by the user are only used to set script input variables. The only TCL knowledge required is the following: