|
Post Script Run Checks |
Top Previous Next |
|
After a script has completed it is important to check the summary.log file. From the GUI, just click the Summary Log button (located in the middle of the GUI) and the file will be displayed. For command line script runs, this file is located in the same directory that the script is run from. This file reports any type of errors that occurred while the script was run. Furthermore, the contents of this file are cumulative. Meaning, every time this script is run, the results are appended to this file. If there were no errors, the script reports:
+++++++++Script Passed Test!+++++++++
If there were errors, the script reports:
“###### There were errors! ######”
along with additional information about the error.
Below shows a portion of the summary.log file for several script runs. This file can be viewed using the UNIX more <filename>, the cat <filename>, or the tail -20 <filename> commands. This extract shows results for two script runs, the most recent run having errors.
[allan@linux-1 tcl]$> more summary.log
If the summary log shows that a script run had errors, then a more detailed investigation as to why the error occurred may be necessary. This is accomplished by looking at a more detailed log file of the script run. The name of the detailed log file is the “script_name.log”. (For example, the default trace-log for the Cisco IOS Report script is ios_report.log.) This file is located in the directory where the script is run from and contains a complete trace of everything that was displayed to the screen as well as the error message that was in the summary.log file. (NOTE: This file only contains the contents of the most recent script run. The contents of the previous script run are removed!!! (If you wish to keep the contents of this file, save this file to another name or use the –log option on the command line when running the script) Using the error message in the sample summary.logabove, the user would search the effic_passwd_change.log file for the string “ERROR20” to obtain more information about the problem. Performing that search below, shows that the router reported “Wrong password!” when attempting to log in. In this particular case, the wrong passwords were entered to login to this router.
Connected to cpe. Escape character is '^]'.
Efficient 5851 SDSL [ATM] Router (5851-005) v5.3.160 Ready Login: * Wrong password! Try logging in again. Login: ERROR20 Loop NA: Proc_bug: Login Failed for <cpe, Efficient device>. Possible bad password ERROR20cont Loop NA: Skipping device. This may cause problems for rest of script
|