Update Operations Agent installations

Administration > Setup and Maintenance > Monitored Nodes

Alternatively, click Monitored Nodes.

To determine whether an update is necessary, first refresh the agent version of the node by synchronizing the installed packages information with the server. You can then check the agent version in the Operations Agent column of the nodes list. (A hyphen (-) indicates that no agent is installed.)

If you want to deploy an agent update to a node, select the node and the newer agent version, and then start the deployment. You can track the progress of the update by monitoring the corresponding deployment job.

Before you can update the agent software, you must obtain the updated agent packages and upload them to the database using the opr-package-manager command-line interface.

1. In the Node Views browser in the Monitored Nodes page, select a node filter (from any of the filter categories). Alternatively, select a node group.

2. Make sure the package information of the node is up-to-date in OMi by synchronizing the installed packages information:

   1. Select the node and click Synchronize Installed Packages Information.

      To contact multiple nodes in parallel, hold down the Ctrl or Shift key while selecting them, and then click Synchronize Installed Packages Information.

      Tip For information about synchronizing policy template assignments, see Assignment Synchronization.

   2. Optional. Check the progress of the package synchronization request in the Deployment Jobs page (see Deployment Jobs for more information).

   3. In the Monitored Nodes page, click Refresh to update the information displayed.

3. Select the node for which you want to view the installed packages and click Edit Item. The Edit Monitored Nodes dialog box opens.

4. Click the Installed Packages tab. The tab displays a description of the installed packages as well as detailed version information.

   Tip Information about the installed packages is also available in the Node Details > Additional Information section of the Monitored Nodes page.

1. In the Node Views browser in the Monitored Nodes page, select a node filter (from any of the filter categories). Alternatively, select a node group.

2. Optional. Check the agent version that is currently installed on the monitored node in the Operations Agent column of the nodes list. More information about the installed packages is available in the Node Details > Additional Information section of the Monitored Nodes page.

3. Upload the HPE Operations Agent deployment packages to which you want to update the agent. For details, see How to upload HPE Operations Agent deployment packages to OMi.

4. Select the node you want to update and click Update Operations Agent.

   To update multiple nodes in parallel, hold down the Ctrl or Shift key while selecting them. Then click Update Operations Agent.

   The Update Operations Agent dialog box opens.

5. Select the version to which you want to update the agent installation:

   • Update to Latest Hotfixes installs the hotfixes that are available on the server and that apply to the agent version installed on the monitored node.

   • Update to Latest Version installs the latest patch or base version on the monitored node.

   • Update to Specific Version enables you to select the version to install on the monitored node. If you select the current version, the hotfixes for that version are installed.

     This option is only available when the selected monitored nodes can be updated to a common version. If a node already has a later version than the target version, the option is disabled.

   OMi creates a deployment job for each update task.

6. Optional. View the progress and status of the deployment job. Navigate to the Deployment Jobs page:

   Administration > Monitoring > Deployment Jobs

   Alternatively, click Deployment Jobs.

7. In the Monitored Nodes page, click Refresh to update the information displayed.

1. Obtain the HPE Operations Agent deployment packages:

   • The HPE Operations Agent deployment packages are available on the HPE Operations Agent media, which is included in the OMi media kit. Make sure the OMi server (gateway or data processing server) can access the deployment packages on the HPE Operations Agent media.

   • Agent patches can be obtained from the Software Support Online web site (as ISO image files): http://support.openview.hp.com/selfsolve/patches. Mount the ISO images so that they are accessible to the OMi server (gateway or data processing server).

   • Agent hotfixes are available from HPE Software Support on request.

2. Upload the deployment packages. On the OMi server (gateway or data processing server), run the opr-package-manager command-line interface.

   Example:

   The following command uploads the Operations-agent deployment packages from the M:\Agent_Setup\packages\ directory.

   opr-package-manager.bat ‑username myU ‑password myPwd ‑upload_packages OVO-Agent.xml ‑input M:\Agent_Setup\packages\

   You can also restrict the upload to one or more specific platforms.

   Example:

   To upload deployment packages for Windows only, run the following command:

   opr-package-manager.bat ‑username myU ‑password myPwd ‑upload_packages OVO-Agent.xml ‑input M:\Agent_Setup\packages\ ‑platform WIN

   For more information, see opr-package-manager Command-Line Interface.

3. Optional. Verify that the packages are now available in OMi. Run the opr-package-manager command-line interface with the ‑list_packages option:

   opr-package-manager.bat ‑username myU ‑password myPwd ‑list_packages ‑format xml > allPgks.xml

   You can view the XML output in any of the major browsers.

Problem: If the computer on which an agent update is running shuts down during the deployment, the deployment job fails and the update does not complete successfully. Restarting the deployment job fails because the previous interruption of the agent update left the agent in an undefined state.

Solution: Update the agent by manually installing the desired agent version on the agent system. If the deployment was interrupted after the agent packages were deployed, you can find them in the <DataDir>/installation/incoming/bundles/ directory.

Problem: If the computer on which a deployment job is running shuts down during the deployment or if the deployment jobs is canceled, the agent update might fail. If the deployment was interrupted after the packages were deployed, the agent update might complete successfully.

Solution: Wait for the agent update to complete and then check the installation log files on the agent:

• Windows: %ovdatadir%log\oainstall.log

• UNIX and Linux: /var/opt/OV/log/oainstall.log

• AIX: /var/opt/OV/log/oainstall.log

If the agent installed successfully, synchronize the installed packages information. For details, see How to view the packages installed on a Monitored Node.