HP Operations Smart Plug-in for Systems Infrastructure Release Notes

for HP Operations Manager for Windows®, HP-UX, Linux, and Solaris

Software version: 2.01

Publication date: February 2012

This document is an overview of the features in HP Operations Systems Infrastructure Smart Plug-ins (SI SPI). It contains important information that is not included in the manuals or the online help. You can find information about the following in this document:

What's New in This Release
Supported Environments
Installation Notes
Enhancements and Fixes
Known Problems, Limitations, and Workarounds
Documentation Updates
Localization Support
Support
Legal Notices

Hidden Text

To simplify navigation, individual Enhancement and Fix items are hidden until you click the link to expand the collapsed text.

Hidden text does not print. To print this document, you can expand selected links before you print or click the Show All button to expand all links. If you use Assistive Technology Tools, activate the Show All button to display all text.

What's New in This Release

HP Operations Smart Plug-in for Systems Infrastructure contains the following feature enhancements:

• SI-DiskPeakUtilMonitor policy to monitor utilization level of the disk on the system. It checks whether the utilization level is full.
• Wildcard characters '*' and '?' supported for all script parameters for filesystem monitoring.
• All SI SPI process monitoring policies are modified to run in a staggered manner to reduce load on opcmona.
• Defect fixes. For more information, see the Infrastructure SPI 2.01 patch text.

For information about customer-related enhancements and software fixes, see Enhancements and Fixes.

Supported Environments

Before installing SI SPI, make sure that your system meets the following minimum requirements for HPOM management server and managed nodes.

To know about the supported operating system architectures, supported operating system release versions, and for recent updates, go to the support matrix URL: HP Software Support Matrix.

Management Server Requirements

The Infrastructure SPIs are supported on HPOM for Windows, HP-UX, Linux, and Solaris operating systems. The following table lists HPOM requirements and the HP Software products you must install on the management server. The patches mentioned are the minimum applicable level. Always apply the latest available patches.

* Contact HP Support to obtain the hotfix.

Supported Agent Versions on Managed Nodes

The Infrastructure SPIs support nodes running Windows, AIX, Linux, HP-UX, or Solaris operating systems. The following table lists the agent versions that you must deploy on the managed nodes. Install the latest patch available for the agents.

Installation Notes

To install Infrastructure SPIs, version 2.01, follow these steps:
Note - Install Infrastructure SPIs version 2.00 from the media before you install Infrastructure SPIs version 2.01.

1. Go to the following web site:
   HP Software Product Patches
2. Log on to the web site with your HP Passport credentials.
   
3. Search the files with the following keywords:
   
   • Smart Plug-in for Systems Infrastructure
   • Smart Plug-in for Cluster Infrastructure
   • Smart Plug-in for Virtualization Infrastructure

The search result includes links to download the files.


4. Click one of the links and download the file on your system.

For more information, see the patch text to install the Infrastructure SPIs on the HPOM management server.

About upgrading Infrastructure SPIs from earlier versions, see HP Operations Smart Plug-in for Infrastructure Installation Guide.

Minimum Disk Space Requirements

Enhancements and Fixes

The following CRs (identified by reference number) are fixed in the current software release. You can view details about each software enhancement or fix using the reference number from the HP Software Support Online. You need a HP passport to access this web site. To set up your passport profile, go to: HP Support.

For the list of defects that are fixed in this release, see the Infrastructure SPI 2.01 patch text.

Known Problems, Limitations, and Workarounds

Limitations

This release of SI SPI has the following limitations:

• The language of the policies auto-deployed on the nodes depends on the locale of the HPOM for Windows management server. It does not depend on the locale of the node.
• The SI SPI tools are not localized.
• Uninstallation of Infrastructure SPI 2.01 will not remove the custom settings of the policies from the management server.

Known Problems and Workarounds for SI SPI and HP Operations agent

For SI SPI:

• Problem: SI-Discovery reports time out for large number of filesystems. For more information, see QCCR1A134939.

  Workaround: Increase the agtrep time out on the node using the following command:
  ovconfchg -ns agtrep -set ACTION_TIMEOUT 30

• Problem: SI-UnixSnmpdProcessMonitor policy sends false alert from a HP-UX 11.31 IA-64 machine with OA 11.02. For more information, see QCCR1A132083

  Workaround: Follow these steps:

  1. Create a copy of SI-UnixSnmpdProcessMonitor policy.
  2. Modify the process name from snmpd to snmpdm and save this policy.
  3. Deploy the new policy to the HP-UX nodes.

• Problem: Enabling alerts for Log monitoring policies for RHEL and SLES on managed nodes running agent as non-root user.

  Workaround: SI SPI supports policies and tools for alternative, non-root user on HTTPS agents. The following policies fail to work on RHEL and SLES systems:

  • SI-LinuxBootLog
  • SI-LinuxSecureLog
  • SI-LinuxKernelLog 2

  To enable alerts for log monitoring for Infrastructure SPIs on non-root agents, follow these steps:

  1. Update the permission of the required log files with the following command:

     For RHEL:
     chmod 444 /var/log/messages
     chmod 444 /var/log/boot.log
     chmod 444 /var/log/secure

     For SLES:
     chmod 444 /var/log/messages
     chmod 444 /var/log/boot.log

  2. Update the permission of OVBBCCB and OPCLE process with the following command:

     chmod 4555 /opt/OV/bin/ovbbccb
     chmod 4555 /opt/OV/lbin/eaagt/opcle

  3. Switch to Non-root user by running the following command:
     

     su - <non-root user name>

  4. Restart ovc by running the following commands:

     ovc -stop
     ovc -start

  5. To check the status of all process, run the command OVC. It displays all process up and running, without any process shown as stopped.

• Problem: Ctrl-M (^M) characters appear in instrumentation scripts for Infrastructure SPI policies. These characters make the scripts difficult to edit on UNIX and Linux systems.

  Workaround: Before you edit or customize the instrumentation scripts, remove the Ctrl-M(^M) characters using the following OS command:

  • On HP-UX, Solaris, Linux, and AIX system run the following command: sed –i “s/^M//g”

    Note that ^M is NOT SHIFT+6 + M. Type CTRL+V+M to enter the command.

  • Alternatively, on Linux system you can run the following: dos2unix (or other such utility on the scripts).

• Problem: For the SNMP nodes added by Infrastructure SPI on HPOM for Windows, the alert appears as critical node may be down.

  Workaround: To manually update the heartbeat polling protocol for the SNMP node to ICMP, follow these steps:

  1. In the HPOM for Windows management server console, right-click the SNMP node.
  2. Choose Properties from the pop-up menu.
  3. Select the Network tab.
  4. Under Heartbeat Polling, change the value of Polling to custom and the value of Ping Protocol to ICMP Only.
  5. Click Apply and then click OK.

• Problem: When you install Infra SPI 2.01 on HPOM for Solaris, the error appears as /etc/opt/OV/share/conf/OpC/mgmt_sv/integration/cfgupld
  /post/cvp _upload.sh: [[: not found. For more information, see QCCR1A126296.
  Workaround: Follow these steps:

  1. Replace #!/bin/sh in the script by #!/usr/xpg4/bin/sh.
  2. If needed, repeat step a) in the following script:
     /etc/opt/OV/share/conf/OpC/mgmt_sv/integration/*/*/cvp
_*.sh
     
     Note: /usr/xpg4/bin/sh should be available on all Solaris systems because it is used in all the OM script (e.g. in /opt/OV/bin/OpC).

• Problem: StoreCollection fails in MS-WindowsFailedLoginsCollector policy. For more information, see QCCR1A130226.
  Workaround: If a lower version (lower than 201.0000) of SI-MSWindowsFailedLoginsCollector policy is deployed to the windows node, follow these steps:

  1. Undeploy the policy from the Windows node.
  2. Run the following command on the OM server to recycle the coda files on the Windows node:
     ovdeploy -cmd "ovc -stop coda && del \"%ovdatadir%\datafiles\coda*\" && ovc -start coda" -host < windows node name>
  3. Deploy the 201.0000 version of the policy on the Windows node.

• Problem: SI-ConfigureDiscovery policy does not restrict the filesystems correctly in the service map. For more information, see QCCR1A128462.
• Problem: NIC Ids mismatch in the discovered NIC services and alert messages. This causes incorrect update in the service map state when alerts related to a particular NIC are received. For more information, see QCCR1A102540.

For HP Operations Agent:

• Problem: CODA stops frequently when Infrastructure SPI monitoring policies are deployed to a vMA4.0 machine with OA11.02. For more information, see QCCR1A132442.
• Problem: Infrastructure monitoring policies that depends on opcmona does not work on HPUX11.31 IA and Solaris 10 SPARC machines when opcmona process is stopped. For more information, see QCCR1A132215.
• Problem: Adaptive threshold policies fail to work on HPUX 11.31. The error appears as Perl Script execution failed: $collectors_hashref. (OpC30-750). For more information, see QCCR1A128243.
• Problem: Multiple error messages appear on SI SPI policies whenever Operations agent is restarted on the node. For more information, see QCCR1A118884
• Problem: During performance testing, opcmona stops. For more information, see QCCR1A108947.

Documentation Updates

The following documentation is available for Systems Infrastructure SPI:

• Installation Guide
• Concepts Guide
• User Guide

The first page of this release notes document contains the following identifying information:

• Version number, which indicates the software version.
• Publish date, which changes each time the document is updated.

To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals

To retrieve a document, select the:

1. Product name.
2. Version list.
3. Operating System.
4. Preferred Language.
5. Document title.
6. Click Open or Download.

You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.

Localization Support

HP supplies Infrastructure SPI localized software and documentation in these languages:

• Japanese
• Simplified Chinese

HP Software Support

This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.

HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

• Search for knowledge documents of interest
• Submit and track progress on support cases
• Submit enhancement requests online
• Download software patches
• Manage a support contract
• Look up HP support contacts
• Review information about available services
• Enter discussions with other software customers
• Research and register for software training

To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.

Legal Notices

©Copyright 2012 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Java is a registered trademark of Oracle and/or its affiliates.