Managing Pending Restart and automatic restart of endpoints

This page has not been liked. Updated 5/21/14 10:49 AM by DaraMurphyTags: None

Managing pending restart states and automated restart of endpoints

When you add a Fixlet, Task, or Baseline to an Automation Plan and if the Fixlet, Task, or Baseline contains an action script that requires the targeted endpoints to restart, this results in your plan remaining in a Pending restart state, until the endpoints are restarted. If the endpoints are not restarted, the step remains in this wait state and the Automation Plan is effectively stalled. Pending restart is a wait state in IBM® Endpoint Manager, and if the endpoints are not restarted, the Automation Plan cannot progress. To prevent this from happening, add a specific Server Automation Fixlet to your plan to automate the restart of the endpoints and configure the Pending Restart settings to continue the plan.

Some Fixlets, Tasks, and Baselines contain action script that results in the targeted endpoints going into a Pending restart state. The following graphic shows an example of action script that requires a restart.

This graphic shows an example of an action script that requires the endpoints to be restarted.
This graphic shows an example of an action script that requires the endpoints to be restarted.
Some Fixlets and Tasks contain a similar piece of action script, action may require restart. This action script can also result in the targeted endpoints entering a Pending restart state. If your Automation Plan contains steps or failure steps with Fixlets, Tasks, or Baselines that contain this action script, a warning icon is displayed on the Settings tab, indicating that one or more of the steps in the plan contain this action script. You can then move to the Settings tab to configure how you want to manage the Pending restart states. For example, you can choose to continue the plan and add a Fixlet to the plan to restart the endpoints.
Table 1. Pending restart settings. Use Fixlet 126 Restart Endpoint and Wait for Restart to Complete to restart the endpoints.
Option Description
Pause Plan until restart completes This option pauses the Automation Plan until the targeted endpoints are restarted and report success or failure. You must manually restart the endpoints before the plan progresses.
Continue Plan When you select this option the step is regarded as successful upon entering the Pending restart state and the plan moves on to the next step, ignoring the actual step status after the endpoints are restarted. Any associated failure step will not run if the step fails after entering the Pending restart state because the step is regarded as successful. You must add a Fixlet to the plan after the step or steps that require a restart. The following list describes how the plan is executed, depending on which Fixlet you use to restart the endpoints when you have selected the Continue Plan option:
Fixlet 126 Restart Endpoint and Wait for Restart to Complete
The system waits for the restart to complete before moving on to the next step in the plan.
Fixlet 94 Restart Endpoint
The system continues to the next step when this step enters a Pending restart state as the endpoints are being restarted. It attempts to execute the next step while the endpoints might still be restarting. Do not use this Fixlet to manage the Pending restart state and automate the restart of endpoints.
No Fixlet
The next step in the plan will be executed, while the pending restart endpoints from the previous step will remain in a Pending restart state until they are restarted.

 

Important: To safely restart the endpoints before moving on to the next step in the plan, the Fixlet that you must include in the plan to restart the endpoints is 126 Restart Endpoint and Wait for Restart to Complete.