|
If ever NetApp Filers KM for PATROL does not function properly (e.g. : displays components as missing while actually present or fails to detect several components as it should etc.), it is possible to reinitialize the configuration and let the KM re-start monitoring from scratch. The above cases of malfunction can occur after a configuration change or after a software/hardware upgrade.
 A backup of the PATROL Agent configuration is always performed and saved in the $PATROL_HOME/config directory before a reinitialization of the KM.
| 1. | To reinitialize NetApp Filers KM for PATROL: Right-click the KM main icon > KM Commands > Reinitialize KM: |
Setting the Reinitialize Options
| 2. | Select the options as per your specific needs: |
Alert thresholds and actions
| ▪ | Remove manually customized alert thresholds: Selection removes all customized thresholds. |
| ▪ | Reset the threshold mechanism mode to default: Selection makes the KM revert to the default mode i.e. NetApp Filers KM for PATROL selects the mechanism that is best suited to the system. |
| ▪ | Reset Alert Actions: Selection removes all manually set Alert Actions and reverts to basic default actions i.e. Trigger a PATROL event and Annotate a parameter graph. |
Misc. options
| ▪ | Deactivate the debug mode: Selection deactivates the debug mode if manually enabled. |
| ▪ | Restore and resume paused/removed objects: Selection restores all paused or removed objects. |
| ▪ | Remove Java Settings: Selection removes the custom Java settings (path and credentials). The KM will try to automatically find a suitable JRE. |
Save reinitialize settings
| ▪ | Save reinitialize settings: Selection saves the defined settings that will then be considered as default. |
In cases where configurations have been manually set in the PATROL Agent, there will be an additional section called Internal KM engine options displaying the used configuration variables and the option whether or not to remove them.
| 
