When the Job Viewer's Status column shows Errors for the executed Job, it individually lists all devices exhibiting errors. Clicking on an Error link for any device shows the location of the error in the Process Log. Errors appear in red. Errors can be due to many issues, including typos in a command directive, incorrect use of an attribute or mistakes in device group assignment.
If a script generates a list of errors, keep the Job Viewer window open, go to Configuration Management –> Job Management –> Scripts in NetMRI and edit the script to fix the errors. Back in the Job Viewer, click the Rerun Errors button. A form page appears in the window, used to re-run the script against the devices that failed the script execution in the existing job instance. Clicking Run Now executes a new Job without the need to go back through the Script Run Now wizard.
Failure to match a pattern in device output will not generate errors – a Filter Does Not Match message appears in yellow in the Process Log page. This typically indicates that a pattern specified in a Script-Filter: attribute or Trigger-Filters: attribute does not appear in the CLI output generated through the script, or that the pattern is incorrectly specified through a typo or an incorrect regular expression.
Note: Exercise caution when writing and executing CCS scripts. Because error checking is not precise even in the best of cases, it is possible to execute endless loops that may result in needing to reboot the NetMRI appliance to stop the runaway job. Test scripts against a single network device and avoid running scripts against production networks until you are certain the script will have a properly finite execution.