This section discusses the details and options of each of the individual programs. Because the scripts can modify a large number of routers in a short period of time, the following precautions should be taken:
| • | Run the scripts against test routers until you become familiar with the scripts and their options. Here you can create intentional errors to see how a script behaves and learn how to easily track errors from the summary.log file to the detailed trace-log file (i.e. script_name.log). |
| • | Always run the script with the specific options against several test routers before running it against a large number of production routers. This will ensure that the script is doing what you intended it to do. |
| • | If you have various software versions on your routers, when possible perform test runs against this software version on non-production routers first. |
| • | When making large changes, run the script against a small subset of routers first and then confirm the results. If the desired results are obtained, run the script against the remainder of the routers. |
| • | Possibly insert a delay between routers. This is done with the “DELAY_INTERVAL” variable in the setup.var file (Options->Settings). Here, you can introduce a delay after the script finishes with one router and before it telnets into the next router. |