HP OpenVMS Systems

The following notes describe features available and problems that are corrected in Version 3.4 of the Management Agents for OpenVMS.

These notes are in the following categories:

» features

» problems corrected

» operation notes

» problems and limitations that remain in version 3.4

» trademarks

Insight Management Agents as a single Kit

With Version 3.4 of Insight Management Agents, you can download a single kit for any versions of Alpha or Integrity servers. With this, the kit name is no longer bound to major versions of the operating system.

On Alpha systems, instead of "HP AXPVMS V73_MGMTAGENTS", "HP AXPVMS V82_MGMTAGENTS"on a "PRODUCT SHOW PRODUCT" command, the Insight Management Agents V3.4 appears as "HP AXPVMS MGMTAGENTS".

Similarly, on Integrity Platforms, the Insight Management Agents V3.4 appears as “HP I64VMS MGMTAGENTS” on a “PRODUCT SHOW PRODUCT” command.

Supports Smart array (CPQIDA) SNMP agent on OpenVMS V8.2, V8.2-1 and V8.3 Integrity Servers (OpenVMS I64) and OpenVMS V7.3-2, V8.2 and V8.3 Alpha Servers

Version 3.4 of the Management Agents provides support for Smart array (CPQIDA) SNMP agent, which monitors the SA6402, SA6404 and P400 controllers and associated disks on Integrity Servers. The Smart array (CPQIDA) SNMP subagent is supported on OpenVMS Alpha Servers for monitoring SA5300A and SA6400A controllers and associated disks.

Support for HP OpenVMS V8.2, V8.2-1 and V8.3 Integrity Servers and HP OpenVMS V7.3-2, V8.2 and V8.3 Alpha Servers  

Version 3.4 of the Management Agents provides support for OpenVMS 8.2, 8.2-1 and V8.3 on I64 Integrity Servers and OpenVMS 7.3-2, 8.2 and 8.3 on Alpha Servers.

Environmental Information (Temperature/Fan and Power Sensors) on I64 systems

Version 3.4 of the Management Agents provides details on the temperature/fan sensor information under the Environment link and power sensor information under the Power Supply link on OpenVMS V8.2-1 or later I64 systems and on Rx1620, Rx2620, Rx4640, Rx7620, Rx7640, Rx8620, Rx8640, Rx3600, Rx6600, Rx2660 and Integrity Superdome Servers.

Non-zero CPU utilization

Version 3.4 of the Management Agents displays the CPU utilization as a non-zero value. Whenever the utilization of the CPU goes below 1%, it will always display the default value as 1%.

Font of DCLSHOW changed to Lucida Console

Version 3.4 of the Management Agents displays DCLshow pages (for selected text) with the "Lucida Console" font, which is commonly available on most of the Personal Computers.

Additional Storage traps

Version 3.4 of Management Agents for Open VMS supports generation of traps, when a Storage Disk is mounted or dismounted.

Support for Secure Sockets Layer (SSL) and Certificates

Version 3.4 of the Management Agents for OpenVMS provides a Secure HTTP server that uses Secure Sockets Layer (SSL) security for all communication between the OpenVMS server and web browser. By default, a self-signed certificate is generated, but for increased security, this can be replaced by a certificate signed by a Certificate Authority. For more information, refer to Section 3 of the User Guide.

Note that as a result of this change, the URL to access the Device Home Page on your OpenVMS system is changed to https://host:2381.

OpenVMS Account Login and OS Authentication

Version 3.4 of the Management Agents for OpenVMS uses OpenVMS user accounts for login security instead of the built-in accounts used in older versions. The user name and password are authenticated against the OpenVMS account database, which increases the security of the system. Anonymous access is disabled by default.

OpenVMS accounts are mapped to the Management Agents internal "administrator" and "operator" accounts. The OpenVMS system administrator maps users to one of these accounts using the WBEM$ADMIN and WBEM$OPERATOR rights identifiers. For more information, refer to Section 3.1, "Introduction to Using the Secure HTTP Server for OpenVMS" in the User Guide.

Additional CPU Utilization Thresholds

Version 3.4 of the Management Agents for OpenVMS allows you to define thresholds on CPU utilization for time intervals of 1 minute, 5 minutes, 30 minutes and 1 hour. If the CPU utilization for a time interval exceeds the threshold, an SNMP trap is generated. Thresholds can be defined separately for each CPU.

Support for Falling Thresholds

Version 3.4 of the Management Agents for OpenVMS supports falling thresholds for File System utilization, CPU utilization, and Physical Memory utilization. Select the "Enable Falling Thresholds" option on the page displaying File System, CPU utilization and Memory utilization data to enable falling thresholds. When this option is enabled, SNMP traps are generated when the utilization drops below the critical and warning thresholds.

Location of Temperature Sensors and Fan Sensors

Version 3.4 of the Management Agents displays the location of temperature sensors and fans on GS80, GS160, GS320 and later systems.

Note:  Refer to the Installation Guide for the prerequisites for viewing environmental details on GS80 and later systems.

Support for HP OpenView

Version 3.4 of the Management Agents allows OpenVMS systems to be managed from HP OpenView Network Node Manager (NNM) using the Systems Insight Manager plug-in. The following functions are available through NNM:

• NNM recognizes OpenVMS systems and displays an appropriate icon on the network map.
• NNM recognizes SNMP traps generated by the Management Agents for OpenVMS.
• The Device Home Page on an OpenVMS system can be launched using the 'Web Enabled' link from NNM.
• The color of the icon in the OpenView Network Node Manager reflects the overall system status similar to Systems Insight Manager.

Additional DCL SHOW Commands

The following additional DCL commands are available from the DCL SHOW agent:

Web pages updated to Version 5.5 of the Insight Manager web pages

The Management Agents for OpenVMS have been updated to use Version 5.5 of the Insight Manager web pages.

Defining logical names used by the Management Agents for OpenVMS

Version 3.4 of the Management Agents uses the file SYS$MANAGER: WBEM$LOGICALS.COM to define all the logical names used by the Management Agents for OpenVMS. This file lists all the logical names supported by the agents, but the lines are commented out by default. Using a text editor, open this file, uncomment the lines containing the logical names you require, and edit the parameters if required. This file includes comments that explain the significance of each logical name.

The startup procedure runs this file to define the logical names required by the Management Agents. These logical names are deleted during the shutdown procedure.

Improved Management Agent kit installation procedures

The Version 3.4 Management Agents kit includes changes in installation procedures that no longer require kit installation on each member node in an OpenVMS cluster environment sharing common system disk. Management kit installation now installs node specific files on each member node present at the time of installation.

Also included are improved procedures that check and alert the user if Management Agents or ACU-XE processes are running at install time. These processes must be terminated before continuing with the installation to ensure correct delivery of kit components.

This section describes the problems that are corrected in this release of the Management Agents for OpenVMS.

• OpenVMS Management Agents displays wrong CPU speed on systems with Montecito CPUs.
• Invoking of OpenVMS Management station from the Insight Management agents fails on IE6.0 SP2, due to browser restriction to access local files.
• The WBEM$GSVIEW process abnormally terminates on a GS series OpenVMS system having TCPWARE stack.
• OpenVMS Management Agents does not set the thresholds after 3 to 4 days on an OpenVMS system having TCPWARE stack.
• OpenVMS Management Agents does not recognize the WBEM$ADMIN identifier and provide admin privilege, if WBEM$OPERATOR Identifier is granted first to a user in SYSUAF.
• OpenVMS Management Agents does not install properly, as it used “MC” verb instead of “MCR”.
• WBEM$CPQSTORE abnormally terminates on a OpenVMS I64 system connected to a tape drive.
• OpenVMS Management Agents causes backups to fail on a system due to tape device polling.
• WBEM$SVRCLU process terminates on a cluster member at startup.
• OpenVMS Management Agents does not terminate the WBEM$CPQIDA process during shutdown of the product.
• OpenVMS Management Agents does not stop the WBEM$CPQIDA process, on invoking shutdown procedure:
  @SYS$SPECIFIC:[WBEM]WBEM$SHUTDOWN.COM
• OpenVMS Management Agents does not allow setting of Disk/CPU/Memory thresholds.
• OpenVMS Management Agents raises threshold traps when shadow disk is un-mounted and remounted with the /FOREIGN option.
• OpenVMS Management Agents does not raise power failure traps on Alpha systems at the startup of the agents.
• Management Agents Kit V3.1 for I64 systems does not display a proper CPU type.
• IP restriction inclusion range does not restrict requests from the IP range specified.
• The NIC subagent enters into a compute bound state on OpenVMS Alpha V7.3-2 or later and OpenVMS I64 V8.2 or later systems.
• WBEM$SERVER crashes with Page Quota exceeded violation on systems having large number of smart array controllers.
• OpenVMS Management Agents does not support single login from Systems Insight Manager.
• OpenVMS DCL Show Commands renders stale HTML Pages of previous session.
• Systems Insight Manager does not recognize VMS clusters.
• Leaving the browser undisturbed for a while prompts you to login again. Revisiting a page containing a POST request after logging in again results in empty data being sent to the web application.
• Information about multipath disks is displayed incorrectly.
• The World Wide Name information for Fiber Channel Controller's is displayed incorrectly.
• The Product Remove operation on the Management Agents in an OpenVMS Cluster sharing a common system disk succeeds on the first node. Subsequent Product Remove Operations on other nodes of the cluster fail.

Please note that the Management Agents for OpenVMS places a version limit of four on files in the following directories:

[WBEM.WEB.IM]
[WBEM.WEB.IM.WEBAGENT.TEMP]

Upgrade

• Before upgrading your OpenVMS operating system to a Major release (for example, upgrading from Version 7.3 to 8.2) or to a new feature release (for example, upgrading from Version 7.3-2 to 8.2), you must remove the Management Agents from your system before performing the upgrade. After upgrading OpenVMS, install a version of the Management Agents that is appropriate for the new version of OpenVMS.

  For example, if you are upgrading from OpenVMS version 7.3-2 to 8.2, you must remove the Management Agents before upgrading OpenVMS, using the following DCL command

  $ PRODUCT REMOVE V73_MGMTAGENTS

Browser

• With Internet Explorer 5.5 and update version SP1;Q288993; Q290108; Q299618, manually refreshing the utilization pages may cause the WBEM$SERVER process to hang. Upgrading to Internet Explorer 5.5 SP2 resolves this problem.
• If you use HP Secure Web Browser (Mozilla) or Netscape Version 6.2 and later, and attempt to log in with a different user name, the login screen may reappear with the new user name listed instead of the Device Home Page. If this happens, click the "Device Home Page" link displayed on the page to manually switch to the device page.

Environmental

• Temperature sensor readings are displayed incorrectly on OpenVMS I64 systems.
• Environmental information such as Temperature/Fan/Power sensors is displayed as failed even when the physical entity is absent for which the sensor was monitoring on the I64 systems.
• Environmental information such as temperature, fan status, and power supply information on Next Generation HP Alpha Servers (GS1280, ES47, ES80 and later) will only be available on systems running OpenVMS Version 7.3-2 or later.
• On the newer generation AlphaServer systems (GS, ES45, DS25 and later), the Power Supply link lists all power sensors available on the system rather than the physical power supplies.
• On the newer generation AlphaServer systems (GS, ES45, DS25 and later), the Environment link lists all fan sensors available on the system rather than the physical fans.

• In system environments containing Smart Array (KZPDC-xx) hardware, the CPQIDA (Smart Array) storage agent process will sometimes exit without warning. The effect of this will be seen as an absence of Smart Array links under the Mass Storage category in the Management Agent's Device Home page. Stopping and re-starting the Management Agents via the WBEM$SHUTDOWN and WBEM$STARTUP scripts should restore the Smart Array links. This issue will be addressed in a future release of the Management Agents kit.

Certificates

• WBEM$SERVER process crashes when you click “Create PKCS#10 Data” button in the Options web page of Insight Management Agents. The "Create PKCS#10 Data” button is used to generate a custom certificate.
• A System Insight Manager Certificate containing multiple dots does not get imported properly into the Insight Management Agents that is installed on ODS-2 disks.

Others

• WBEM$CPQHEALTH process hold onto OPERATOR.LOG file. To delete and create a new OPERATOR.LOG, the Insight Management Agents needs to be shutdown before deleting OPERATOR.LOG and started back after the new OPERATOR.LOG is created.
• Firmware Revision not available on I64 Integrity Servers.
• WBEM process hangs inconsistently on the GS series system running VMS 7.3-2 or later.

MultiNet and TCPware are registered trademarks of Process Software.

All other trademarks and registered trademarks are the property of their respective holders.

© Copyright 2007 Hewlett-Packard Development Company, L.P. All rights reserved.

» return to the Management Agents home page