HP OpenVMS 8.3 manual Virtual Connect, Virtual Media vMedia, Polycenter Software Installation

HP OpenVMS Alpha Version 8.3 and HP OpenVMS Version 8.3-1H1 for Integrity Servers SPD 82.35.14

Alpha systems running OpenVMS Version 8.3 that sup- port a DVD drive. This support provides the additional advantage of allowing a network administrator to boot multiple OpenVMS systems on the network from a sin- gle copy of the OpenVMS distribution CD or DVD.

Using the InfoServer software application on Integrity servers for network booting requires several one-time- only configuration steps unique to OpenVMS Integrity servers. Likewise, using the InfoServer software ap- plication on OpenVMS Alpha servers requires an addi- tional, one-time-only software configuration step. Any configuration procedures that might have been per- formed for network booting using an InfoServer hard- ware system (traditionally used by Alpha systems) are not valid for the OpenVMS I64 or OpenVMS Alpha In- foServer application. Booting from the InfoServer soft- ware application for OpenVMS on Integrity servers dif- fers significantly from booting from the InfoServer hard- ware system traditionally used by OpenVMS Alpha sys- tems or from the InfoServer software application on OpenVMS Alpha systems.

To install or upgrade the operating system over the net- work, OpenVMS Integrity server systems must use the InfoServer software application that is integrated with the OpenVMS operating system. The InfoServer hard- ware traditionally used by OpenVMS Alpha systems is not equipped to handle DVD drives required for the OpenVMS Integrity server distribution media. Open- VMS Alpha systems can use the OpenVMS InfoServer software application or the traditional InfoServer hard- ware system that is independent of OpenVMS. Open- VMS Alpha systems can boot from the distribution CD on DVD drives (DVD drives support both DVDs and CDs).

For additional information, please refer to the HP OpenVMS Version 8.3-1H1 for Integrity Servers Up- grade and Installation Manual.

Virtual Connect

Virtual Connect is a set of interconnect modules and embedded software for HP BladeSystem c-Class en- closures; it simplifies the setup and administration of server connections. HP Virtual Connect includes the HP 1/10Gb Virtual Connect Ethernet Module for c-Class BladeSystem, the HP 4Gb Fibre Channel module, and the HP Virtual Connect Manager.

Virtual Media (vMedia)

Virtual Media (vMedia) is the overall name for a num- ber of different devices that can exist on a PC. These devices appear as local USB disk devices to the host system. vMedia is part of the iLO2-enhanced feature set. On some systems, the iLO2 license is bundled with the hardware, while with others a separate iLO2 license must be purchased to enable the virtual media device.

You can also use vMedia devices to boot, install, or up- grade OpenVMS from over the network, as described in the HP OpenVMS Version 8.3-1H1 for Integrity Servers Upgrade and Installation Manual.

OpenVMS supports vMedia in the following Integrity server systems: BL860c, rx2660, rx3600, rx6600, rx7640, rx8640, and Superdomes with the sx2000 chipset.

Note: The rx7640, rx8640, and Superdome cell-based Integrity servers require an AD307A card to be installed in order for vMedia to function.

POLYCENTER Software Installation

The PCSI utility simplifies the installation and manage- ment of OpenVMS products. It is used to install, update, and deinstall software products that have been prepared with the utility. In addition, the utility provides a database to track the installation, reconfiguration, and deinstal- lation of software. For products installed with other installation technologies, the utility provides a mecha- nism for adding information about them into the product database. The utility also provides the ability to manage dependencies between products during the installation process.

For software providers, the PCSI utility simplifies the task of packaging software by providing a simple, declarative language for describing material for the in- stallation kit and defining how it is installed. The utility handles the functions, while the developer instructs the utility what to do. This significantly reduces the com- plexity and time to develop installation procedures. The language allows the developer to easily specify depen- dencies on other software, manage objects in the exe- cution environment (such as files and directories), and anticipate and resolve conflict before it occurs. The util- ity also significantly simplifies the packaging of multiple software products into one logical product suite.

For OpenVMS Alpha and OpenVMS for Integrity servers, you use the PCSI utility to install the operating system and to install layered products that are compliant with the POLYCENTER utility.

Most of the software product kits included on the Open- VMS Version 8.3-1H1 distribution media are signed us- ing Secure Delivery. A notable exception is the Open- VMS Operation System (the VMS product) because it is shipped in bootable form, not as a single file kit that is signed.

For OpenVMS for Integrity servers, when you install or upgrade the operating system by booting from the dis- tribution media, layered products that have been signed are validated by the PCSI utility with the aid of a digi- tal signature file (called a manifest). Validation involves

20