HP Availability Manager Installation Instructions 3.0-2

This document, "HP Availability Manager Installation Instructions Version 3.0-2," provides a comprehensive guide for installing and configuring the HP Availability Manager software, designed to collect and analyze system performance data.

Key Components:

1. Data Collector: Gathers performance data from OpenVMS nodes.
2. Data Analyzer: Directs data collection, analyzes the collected data (on Windows or OpenVMS), and facilitates corrective actions.
3. Data Server: Used when the Data Analyzer is on a Wide Area Network (WAN) to communicate with Data Collectors.

Software Packaging:

• Windows Kit: Includes all three components (Data Collector, Data Analyzer, Data Server).
• OpenVMS Kits: The Data Collector is a standalone kit, while the Data Analyzer and Data Server are bundled in a "Combined kit."

Supported Systems:

• OpenVMS: VAX (6.2-7.3), Alpha (6.2-8.3), I64 (8.2-8.3-1H1).
• Microsoft Windows: Windows 2000 Pro, Windows XP Pro.

General Installation Process & Prerequisites:

• Order of Installation: If installing both Data Collector and Data Analyzer/Server on the same OpenVMS node, the Data Collector kit must be installed first, followed by the Combined kit.
• Crucial Pre-installation Steps:
  • Verify required privileges (e.g., OPER, SYSPRV).
  • Evaluate hardware, software, and disk space requirements.
  • Perform a system disk backup.
  • Uninstall previous versions of Availability Manager (especially prior to Version 2.4, which involves specific steps like backing up .ini files and a system reboot).
  • Install the latest POLYCENTER Software Installation (PCSI) patch kit on OpenVMS systems.
  • Read the Release Notes for critical information.
  • For OpenVMS Data Analyzer/Server, ensure the installation disk is ODS-5 formatted and install necessary Java 1.5.0 patch kits.

Platform-Specific Installation Highlights:

• Data Collector on OpenVMS:

  • Installed on every OpenVMS node that will collect data using PRODUCT INSTALL AVAIL_MAN_COL.
  • Instructions for both single-node and cluster-wide installations are provided (using SYSMAN for clusters).
  • Post-installation tasks include merging configuration files (for upgrades), editing password access files (AMDS$DRIVER_ACCESS.DAT), defining logical names (AMDS$LOGICALS.COM), and adding a line to SYS$MANAGER:SYSTARTUP_VMS.COM (@SYS$STARTUP:AMDS$STARTUP START) to ensure the Data Collector starts at boot.
  • Managed Objects functionality (for OpenVMS 7.3+) requires copying SYS$AMCONFIG.DAT to SYS$SYSROOT:[SYSEXE] and rebooting.

• Data Analyzer and Data Server on Windows:

  • Requires local Administrator account and closing other applications.
  • Installed by running AvailManV30-2_i.exe.
  • A system reboot is required after installation.
  • Configuration files (like AvailMan.ini) should be backed up before uninstalling old versions and restored after the new installation.
  • Memory allocation pool (heap) values can be modified for performance.

Operation and Performance Considerations:

• Starting Applications: DCL commands (AVAIL/ANALYZER, AVAIL/SERVER, AVAIL/MOTIF for DECamds) are provided for OpenVMS, along with qualifiers for memory allocation (heap size) and IP port numbers. Windows applications are started via the Start Menu.
• Performance Tuning: The document outlines recommended system quotas (PGFLQUOTA, BYTLM, WSEXTENT, WSMAX) and refers to a Java tool for checking environment settings.
• Concurrent Operation with DECamds: Detailed steps are provided for running Availability Manager and DECamds simultaneously, emphasizing the importance of merging and consolidating shared configuration files (e.g., password and logical name files) to prevent conflicts and ensure both products use the same settings.