This glossary defines key terms in the context of an OpenVMS computing environment.
A | ||
---|---|---|
Advanced Server for OpenVMS | Supported on OpenVMS Alpha systems only, an OpenVMS-based network operating system compatible with Microsoft networking technology. Allows OpenVMS systems to be file and print servers for Windows desktop users. These users can use Microsoft products and utilities such as Windows Explorer to access file and print resources. Also provides a flexible system for network administration and security. This product supports OpenVMS ODS-5 disk volumes and Extended File Specifications. See also PATHWORKS for Advanced Server (OpenVMS). | |
Availability Manager | A system management tool that enables the system manager to monitor one or more OpenVMS nodes on an extended LAN from an OpenVMS, Windows 2000, or Windows XP system. Availability Manager helps system managers and analysts target a specific node for analysis. The tool collects system and process data from multiple nodes simultaneously; it analyzes the data and displays the output. The Availability Manager (base) software installed with OpenVMS provides the data collection components that allow the system to be monitored by the Availability Manager and by DECamds. | |
AVIO | Accelerated Virtual Input/Output. An I/O protocol that improves virtual I/O performance for network and storage devices used within the Integrity VM environment. The protocol also enables support for a greater number of virtual I/O devices per guest. Special drivers are required on both the VM Host and guests. Participating guests must include a virtual I/O device configured to use the AVIO protocol. | |
B | ||
backing store | The physical device on the VM Host that is allocated to guests, such as a network adapter, disk, or file. | |
Base Operating Environment | See BOE. | |
Baseboard Management Controller | See BMC. | |
BIB | Boot-is-blocked. The state of a cell (on cell-based Integrity servers) that is powered on but not allowed to boot. When all cells assigned to an nPartition are at the BIB state, the nPartition is inactive and no software can run on the nPartition until it is manually booted past BIB. See also cell, nPartition. | |
BladeSystem | HP BladeSystem is comprised of blade compute nodes, integrated connectivity to data and storage networks, and shared power subsystems. See also BladeSystem enclosure, server blades. | |
BladeSystem enclosure | Hardware solution for consolidating server blades and all supporting infrastructure elements (such as storage, network, and power) into a single unit. See also BladeSystem, server blades. | |
BMC | Baseboard Management Controller. A utility provided with HP Integrity servers that allows you to control some management features built into the system board, such as diagnostics, configuration, and hardware management. It enables you to interact with the Extensible Firmware Interface (EFI) and to boot the OpenVMS operating system. See also EFI, MP. | |
BOE | Base Operating Environment. The tier of the Operating Environment for OpenVMS for Integrity servers that offers the base operating system and networking transport products. The contents of this tier are contained in each of the other, higher-level tiers. See also DCOE, OE. | |
boot | The process of loading system software into a processor's main memory. This guide uses the term boot to refer to this process. | |
boot server | A boot server downloads the system software required by a client system. A TCP boot server (TCP/IP Services for OpenVMS BOOTP server) is the host that centralizes configuration and management of an IP address database, such as is used for OpenVMS InfoServer client booting and satellite booting. For satellite booting, the boot server is part of an OpenVMS Cluster; it includes either a MOP server (for OpenVMS Alpha systems) or a BOOTP/TFTP server (for OpenVMS Integrity server systems), and a disk server for the satellite system disk. See also InfoServer, satellite node. | |
bootstrap | See boot. | |
C | ||
CDSA | Common Data Security Architecture. A multiplatform, Open Source security infrastructure. CDSA provides a stable, standards-based programming interface that enables applications to access operating system security services. With CDSA, you can create cross-platform, security-enabled applications. Beginning with Version 2.2, CDSA includes support of Secure Delivery and HRS (Human Recognition Service Standard). CDSA is automatically installed with the operating system. For more information about CDSA, see the HP Open Source Security for OpenVMS, Volume 1: Common Data Security Architecture manual. See also Secure Delivery, HRS. | |
cell | Also known as a cell board: a circuit board that is the basic building block of an nPartition in a server complex (such as any HP midrange and high-end Integrity servers). A cell consists of a symmetric multiprocessor and memory. See also cell-based server, nPartition, server complex, virtual partition. | |
cell-based server | A server in which all cores and memory are contained in cells, each of which can be assigned for exclusive use by an nPartition. Each nPartition runs its own instance of an operating system. See also cell, nPartition, server complex, virtual partition. | |
CI | Computer interconnect. A type of I/O subsystem.
It links computers to each other and to HS See also CI-only cluster, DSSI. | |
CI-only cluster | A computer system consisting of several computers attached to a computer interconnect (CI) through which it communicates with other computers in the cluster. These computers share a single file system. CI provides redundant paths. See also computer interconnect (CI), DSSI-only cluster. | |
Common Data Security Architecture | See CDSA. | |
complex | See server complex. | |
computer interconnect | See CI. | |
concurrent upgrade | The entire OpenVMS Cluster is shut down and unusable while upgrading each system disk. When the cluster reboots, all cluster members start up the upgraded version of the OpenVMS operating system. | |
core | The actual data processing engine within a processor. A single processor might have multiple cores, and a core might support multiple execution threads. Also referred to as a logical CPU. | |
core I/O | Provides the base set of I/O functions required by every nPartition on cell-based Integrity servers. Includes the partition console interface and the network interface. See also cell, cell-based server, nPartition. | |
D | ||
Data Center Operating Environment | See DCOE. | |
DCOE | Data Center Operating Environment. The tier of the Operating Environment for OpenVMS for Integrity servers that offers everything offered by the Base Operating Environment (BOE) plus other capabilities such as system management capabilities, OpenVMS Cluster software, and volume shadowing. See also BOE, OE. | |
DECnet Phase IV | Networking software that allows OpenVMS systems to participate in network task-to-task communications to transfer and copy files, print files, and run applications. DECnet Phase IV networking capabilities are defined in the DIGITAL Network Architecture (DNA) Phase IV. A system-integrated product, DECnet for OpenVMS Integrity servers is a component of the Base Operating Environment (BOE) on the Integrity servers license bundle. See also DECnet-Plus, TCP/IP Services for OpenVMS. | |
DECnet-Plus | Formerly known as DECnet/OSI, DECnet-Plus is the networking software that offers the capabilities defined in the DIGITAL Network Architecture (DNA) Phase V protocols. DECnet-Plus provides the newest DECnet features such as extended addressing and downline-load performance enhancements. DECnet-Plus integrates DECnet and OSI protocols and provides a linkage to TCP/IP. DECnet-Plus for OpenVMS Integrity servers is a component of the Base Operating Environment (BOE) on the Integrity servers license bundle. See also DECnet Phase IV, TCP/IP Services for OpenVMS. | |
DECwindows Motif for OpenVMS | A layered product that provides support for both OSF/Motif, a standards-based graphical user interface, and the X user interface (XUI) in a single, run-time and development environment. DECwindows Motif displays the OSF/Motif user interface, but applications written on either toolkit will run regardless of the environment selected by the user. | |
device name | The name used to identify a device on the system. A device name indicates the device code, controller designation, and unit number, such as DKA0, where DK is the device code, A is the boot device controller designation, and 0 is the unit number on the boot device. | |
diagnostic partition | When present on an OpenVMS Integrity servers system disk, this partition corresponds to the contents of SYS$MAINTENANCE:SYS$DIAGNOSTICS.SYS on the disk. The diagnostic partition and its contents are intended and reserved for use by HP Services. Customer access and use is not supported. | |
Digital Storage System Interconnect | See DSSI. | |
disk server | A computer within a local area cluster that provides an access path to CI, DSSI, and locally connected disks for other computers that do not have a direct connection. | |
DSSI | Digital Storage Systems Interconnect. A medium-bandwidth interconnect. Typically, OpenVMS Alpha nodes use DSSI to access peripherals (such as disks and tapes). See also computer interconnect (CI), DSSI-only cluster. | |
DSSI-only cluster | A computer system consisting of several computers attached to a Digital Storage System Interconnect (DSSI) through which it communicates with other computers in the cluster. These computers share a single file system. See also DSSI, CI-only cluster. | |
E | ||
EFI | Extensible Firmware Interface. The interface between HP Integrity servers operating system and system firmware enabling you to perform such tasks as configuring the firmware and controlling the booting environment. EFI is the Intel specification of an interface between firmware and hardware. See also BMC, MP, POSSE. | |
encryption | A process implemented for data confidentiality that converts sensitive or otherwise private data to an unintelligible form called cipher-text. Decryption reverses the process, taking the unintelligible cipher-text and converting the data back into its original form, called plaintext. Encryption and decryption are also known as encipher and decipher. Encryption for OpenVMS software is based on the Advanced Encryption Standard (AES) alogrithm and is integrated with the operating system. This allows OpenVMS users, system managers, security managers, or programmers to secure their files, save sets, or application data with AES Encryption. | |
Enterprise Operating Environment | See EOE. | |
EOE | Enterprise Operating Environment. Discontinued operating environment for OpenVMS for Integrity servers available prior to OpenVMS Version 8.4 and since replaced by the Data Center Operating Environment (DCOE). See also BOE, DCOE. | |
Extensible Firmware Interface | See EFI. | |
F | ||
FOE | Foundation Operating Environment. Discontinued operating environment for OpenVMS for Integrity servers available prior to OpenVMS Version 8.4 and since replaced by the Base Operating Environment (BOE). See also BOE, DCOE. | |
Foundation Operating Environment | See FOE. | |
G | ||
Global Workload Manager | See gWLM. | |
gWLM | HP Integrity Essentials Global Workload Manager. The VSE Management Software application that provides centralized, intelligent, policy-based resource management across multiple HP servers. The resource-sharing policies increase system utilization and facilitate controlled sharing of system resources. gWLM's monitoring abilities provide both real-time and historical monitoring of resource allocation. See also HP SIM, VSE, WBEM (Web-Based Enterprise Management Services for OpenVMS). | |
H | ||
HP Binary Checker | HP Binary Checker validates the kits signed using HP Code Signing Service (HPCSS). This validator is available with the OpenVMS operating system from OpenVMS Version 8.4 onwards. Changes have been made to VMSINSTAL and PCSI to use the validator. Some of the layered products that use VMSINSTAL will be signed the way in which the PCSI kits were signed. CDSA signing will be discontinued after the OpenVMS Version 8.4 Release. See also CDSA. | |
HP SIM | HP Systems Insight Manager. The unified infrastructure management strategy foundation which provides the platform and framework on which the VSE Management Software products are deployed. HP SIM (an HP implementation of WBEM) provides simplified, centralized management of multiple servers and platforms through a web-based, unified interface. See also gWLM, provisioning, VSE, WBEM (Web-Based Enterprise Management Services for OpenVMS). | |
HP Systems Insight Manager | See HP SIM. | |
HRS | Human Recognition Service Standard. HRS provides generic authentication service suitable for use with any form of human authentication (biometrics) for operation with CDSA. See also CDSA. | |
HSx device | A self-contained, intelligent, mass storage subsystem (for example, an HSJ or HSG) that lets computers in a cluster environment share disks. | |
HSx drive | Any disk or tape drive connected to an HSx device (for example, an HSJ or HSG). A system disk on an HSx drive can be shared by several computers in an OpenVMS Cluster environment. | |
Human Recognition Service Standard | See HRS. | |
Hyper-Threading | Supported on systems that have dual-core processors, this feature provides the ability for processors to create a second virtual core that allows additional efficiencies of processing. For example, a dual-core processor with Hyper-Threading active can run four threads. | |
I | ||
iCAP | Instant Capacity. Supported on cell-based Integrity servers, the HP Utility Pricing Solutions product that allows you to purchase and install additional processing power through the use of a two-step purchase model. Initially, you purchase system components (cores, cell boards, memory) at a fraction of the regular price because the usage rights are not included. These Instant Capacity components are inactive but installed and ready for use. When extra capacity is needed, you pay the remainder of the regular price for the usage rights to activate the components. If the regular price for the component is reduced by the time the usage rights are purchased, the remainder price is proportionally reduced, providing additional savings. After obtaining usage rights, Instant Capacity cores can be turned on by the Instant Capacity software or during installation. Earlier versions of iCAP were referred to as Instant Capacity on Demand, or iCOD. See also TiCAP. | |
iLO | See MP. | |
InfoServer | A general-purpose disk storage server (virtual device server). It can make devices available to client systems on the LAN. Client systems can connect to the virtual devices and use them as though they are locally attached devices. OpenVMS systems connected to the same LAN can boot from a virtual drive available from the InfoServer instead of from a local CD or DVD. | |
Insight Power Manager | See IPM. | |
instance | See OpenVMS instance. | |
Instant Capacity | See iCAP. | |
Integrated Lights Out (iLO) | See MP. | |
Integrity VM | The HP Integrity VM product allows you to install and run multiple systems (virtual machines) on the same physical host system. | |
IPM | Insight Power Manager. An integrated power monitoring and management application that provides centralized control of server power consumption and thermal output at the datacenter level. It extends the capacity of datacenters by enabling the user to control the amount of power and cooling required for servers. | |
K | ||
Kerberos | A network authentication protocol that provides authentication for applications using secret-key crytpography. Kerberos is automatically installed with the OpenVMS operating system. | |
L | ||
layered products | Products, including SIPs, provided by HP and third parties that can installed on an OpenVMS system. See also SIP. | |
local area OpenVMS Cluster system | A configuration consisting of one or more computers that act as a MOP server and disk server, and a number of low-end computers that act as satellite nodes. The LAN connects all of the computers. These computers share a single file system. | |
local drive | A drive, such as a CD, DVD, or disk drive, that is connected directly to a computer. If you have a standalone computer, it is likely that all drives connected to the system are local drives. | |
logical CPU | An execution thread contained within a core on Integrity servers with Intel Itanium Dual-Core processors. With Hyper-Threading enabled, each core can contain multiple logical CPUs. See also core, Hyper-Threading. | |
M | ||
Maintenance Operations Protocol | See MOP. | |
Management Processor | See MP. | |
MCOE | Mission Critical Operating Environment. Discontinued operating environment for OpenVMS for Integrity servers available prior to OpenVMS Version 8.4 and since replaced by the Data Center Operating Environment (DCOE). See also BOE, DCOE. | |
media | Any packaging agents capable of storing computer software (for example, compact discs, magnetic tapes, floppy disks, disk packs, and tape cartridges). | |
migration support | In OpenVMS Clusters, migration support means that HP has qualified the versions for use together in configurations that are migrating in a staged fashion to a newer version of OpenVMS VAX, OpenVMS Alpha, or OpenVMS Integrity servers. Problem reports submitted against these configurations are answered by HP. However, in exceptional cases HP might request moving to a warranted configuration as part of the solution. Migration support helps customers move to warranted OpenVMS Cluster pairs. See also warranted support. | |
Mission Critical Operating Environment | See MCOE. | |
MOP | Maintenance Operations Protocol. A protocol used for operations such as downline loading and upline dumping. See also MOP server. | |
MOP server | A computer system using either the LAN Auxiliary Control Process (LANACP) or DECnet software to downline-load systems using the Maintenance Operations Protocol (MOP). Systems loaded include OpenVMS systems, print servers, and LAT servers. See also MOP. | |
MP | Management Processor. A utility on HP Integrity servers that provides both local and remote access for controlling the system console, reset/power management, and transfer of control (TOC) capabilities. It also allows you interact with the Extensible Firmware Interface (EFI) and to monitor tasks and display detailed information about various internal subsystems. MP is available even when the server main power switch is in the off position. Most entry-class Integrity servers include the Integrated Lights Out (iLO) Management Processor, which provides a complete remote console experience with a web-based GUI and the functionality provided by virtual media (vMedia). See also BMC, EFI. | |
N | ||
nPartition | Node partition. A hard partition within a cell-based server that provides both hardware and software isolation among different instances of the operating system running on a single server. Cell-based servers can be configured either as a single, large, symmetric multiprocessor or as several independent systems. An nPartition has exclusive use of the memory, processor (core), and I/O resources belonging to the cells that are assigned to that partition, and can execute its own operating system image. See also cell, partition, server complex, virtual partition). | |
O | ||
OE | The Operating Environment for OpenVMS for Integrity servers is the model for delivering the OpenVMS Integrity servers operating system, layered products, and documentation. Each operating environment bundles a group of products offered together at a single price based on the number of active cores in the system. See also BOE, DCOE. | |
OE DVD | The Operating Environment DVD containing the OpenVMS for Integrity servers Operating Environment and operating system, and the installation and other procedures described in this manual. | |
OpenVMS Cluster system | A computer system consisting of two or more Alpha, VAX, or Integrity servers computers running HP OpenVMS Cluster software. Many types of cluster interconnect devices can be used to create a cluster environment; for example, CI, DSSI, and LAN devices in a local area network, and Shared Memory CI (SMCI) for OpenVMS Galaxy instances. An OpenVMS Cluster can consist of a single interconnect or a mixed-interconnect cluster with any combination of cluster interconnects. | |
OpenVMS instance | The OpenVMS operating system running in either a soft or hard partition of a hardware platform. To share memory in a hard partition, the GALAXY system parameter must be set. | |
OpenVMS Management Station | A powerful Microsoft Windows based management tool for system managers and others who perform system management tasks on OpenVMS systems. Allows system managers to manage user accounts, printers, and storage across multiple systems, using an intuitive interface that eliminates the need to remember complex OpenVMS DCL syntax, command procedures, and device names. A server component is installed on OpenVMS (automatically if you select all the default values during the installation); a client component is installed on a PC. | |
Operating Environment | See OE. | |
Operating Environment DVD | See OE DVD. | |
operating system CD | The CD containing the OpenVMS Alpha operating system and the installation and other procedures. See also operating system media, Operating Environment DVD. | |
operating system media | The operating system CD or the OE DVD included with your OpenVMS distribution kit. See also operating system CD, OE DVD. | |
P | ||
partition | A subset of the server hardware that includes processor, memory, and I/O resources on which an operating system can run. This type of partitioning allows a single server to run an operating system independently in each partition with isolation from other partitions. See also cell, nPartition, server complex, virtual partition. | |
PATHWORKS for OpenVMS (Advanced Server) | Supported on OpenVMS Alpha and VAX systems only, an OpenVMS network operating system compatible with Microsoft networking technology. Allows OpenVMS systems to be file and print servers for Windows desktop users. Such users can use Microsoft products and utilities such as Windows Explorer to access file and print resources. Also provides a flexible system for network administration and security. See also Advanced Server for OpenVMS. | |
Performance Data Collector | See TDC. | |
platform | A PCSI utility concept in which the OpenVMS operating system is kitted with options for selected other products (for example, DECwindows Motif and networking products) so that the user can opt to install all at once. Generically, a platform is the combination of physical hardware and operating system on which a piece of management or application software runs. | |
POSSE | Pre-OS System Environment. The HP implementation of EFI that extends the EFI Shell and EFI Boot Manager to include additional features for managing hardware and system boot options. See also EFI. | |
Providers | See WBEM Providers for OpenVMS. | |
provisioning | An HP SIM feature that allows you to install or upgrade OpenVMS on one or more servers in the network simultaneously. HP SIM initiates the process and the installation or upgrade automatically continues in the background. See also HP SIM, VSE, WBEM (Web-Based Enterprise Management Services for OpenVMS). | |
R | ||
rolling upgrade | Each system disk in an OpenVMS Cluster is upgraded individually, allowing old and new versions of the operating system to run together. Certain members of the cluster are available for use while others are being upgraded. See also concurrent upgrade. | |
S | ||
satellite node | A computer that is part of a local area cluster. A satellite node is downline loaded from a boot server and then boots remotely from the system disk served by a disk server in the local area cluster. See also disk server, boot server. | |
scratch disk | A blank disk or a disk with files you no longer need. | |
Secure Delivery | Supported by CDSA, Secure Delivery uses public key and digital signature technology to implement a system that provides OpenVMS users the ability to validate files from OpenVMS and third-party OpenVMS vendors. The validation process involves authenticating the originator and verifying the contents of a file. Secure Delivery is integrated into PCSI to automatically ensure that software installed on OpenVMS was not tampered with prior to installation. Most kits included on the OpenVMS distribution media (as of Version 8.3) have been signed using Secure Delivery. See also CDSA. | |
Secure Sockets Layer | See SSL. | |
server blades | Thin, modular, self-contained computer servers containing one or more microprocessors and memory. Server blades are designed for high density and eliminate the need for many components such as power cords and network cables that are present in traditional rack-mount systems. HP server blades support technologies such as hot-plug hard-drives, multiple I/O cards, multi-function network interconnects and Integrated Lights Out. See also BladeSystem, BladeSystem enclosure. | |
server complex | The hardware of a cell-based server that includes all cells, I/O expansion cabinets, cables, cabinet hardware, fans, and power and utilities components. The complex can support multiple instances of an operating system by means of nPartitions. See also cell, nPartition, server complex. | |
SIM | See HP SIM. | |
SIP | System Integrated Product. A product provided by HP that can be installed or upgraded as part of the OpenVMS installation or upgrade. SIPs include required products, such as CDSA, Kerberos, and the base kit for Availability Manager, and on OpenVMS Integrity server systems only, WBEM Services for OpenVMS and WBEM Providers for OpenVMS, and optional products such as DECwindows Motif, DECnet-Plus, DECnet Phase IV, TCP/IP Services for OpenVMS. See also layered products. | |
source drive | The drive that holds the operating system distribution media during an upgrade or installation. This can be a local drive or an InfoServer. The drive contains either the operating system CD or DVD, or a copy of it. | |
SSL | Secure Sockets Layer. The open-standard security protocol for secure transfer of sensitive information over the Internet. HP SSL offers a high degree of confidentiality by allowing server authentication, client authentication, and an encrypted connection that requires all information sent between client and server to be encrypted by the sending software and decrypted by the receiving software. HP SSL for OpenVMS is automatically installed with the OpenVMS operating system. For more information, see the HP Open Source Security for OpenVMS, Volume 2: HP SSL for OpenVMS manual. | |
standalone system | A computer system consisting of a single computer that is not part of a network or OpenVMS Cluster. | |
system disk | The disk from which OpenVMS is typically booted. During an installation or upgrade, this disk is the target disk because it receives files from the source drive. After installation or upgrade, the target drive is booted and becomes the system disk. See also target drive. | |
System Integrated Product | See SIP. | |
Systems Insight Manager | See HP SIM. | |
T | ||
target drive | The drive that holds the system disk during an upgrade or installation, or the drive you designate when backing up the system disk. | |
TCP/IP Services for OpenVMS | HP standard implementation of the TCP/IP and NFS networking protocols, integrated with the OpenVMS operating system installation. Provides interoperability and resource sharing among systems running OpenVMS, UNIX, Windows, and other operating systems that support TCP/IP. TCP/IP provides a comprehensive suite of functions and applications that support industry-standard protocols for heterogeneous network communications and resource sharing. See also DECnet Phase IV, DECnet-Plus. | |
TDC | The Performance Data Collector for HP OpenVMS (TDC) collects and manages configuration and performance data for analysis by other applications. TDC_RT Version 2.2 or later is a run-time only (base) variant of the TDC software that is installed automatically with the OpenVMS operating system for use on specific operating system platforms. By default, data is collected in a file. Subsequently, user applications can retrieve the data from the file. | |
Temporary Instant Capacity | See TiCAP. | |
TiCAP | Temporary Instant Capacity. Supported on cell-based Integrity servers, an HP product option included with Instant Capacity (iCAP) that enables you to purchase prepaid core activation rights for a specified (temporary) period of time. Temporary capacity is sold in 30 processing-day increments (or 720 core-hours), which can be spread across all Instant Capacity cores as required. TiCAP was formerly referred to as TiCOD. See also iCAP. | |
U | ||
UETP | User Environment Test Package. A software package that tests all the standard peripheral devices on your system, various commands and operating system functions, the system's multiple-user capability, DECnet software, and the cluster environment. | |
User Environment Test Package | See UETP. | |
V | ||
VC | Virtual Connect. A set of interconnect modules and embedded software for HP BladeSystem c-Class enclosures; it simplifies the setup and administration of server connections. Where most server interconnect choices come with compromises such as too many cables or too much to manage, VC reduces the number of network cables and simplifies management while adding the unique ability to wire everything once, then add, replace or recover servers in minutes instead of hours or days. HP Virtual Connect includes the HP 1/10Gb Virtual Connect Ethernet Module and HP 4 Gb Virtual Connect Fibre Channel Module for c-Class BladeSystem, and the HP Virtual Connect Manager. | |
Virtual Connect | See VC. | |
virtual console | The virtualized console of a virtual machine that emulates the functionality of the Management Processor interface for Integrity servers. Each virtual machine has its own virtual console from which the virtual machine can be powered on or off and booted or shut down, and from which the guest operating system can be selected. | |
virtual device | An emulation of a physical device. This emulation, used as a device by a virtual machine, effectively maps a virtual device to an entity (for example, s a DVD) on the VM Host. | |
virtual machine | Virtual hardware system. Also called VM. | |
virtual media | See vMedia. | |
virtual partition | A soft partition within a cell-based server that can provide software isolation among different instances of the operating system running on a single server or nPartition. Cell-based servers can be configured either as a single large symmetric multiprocessor or as several independent systems. A virtual partition uses a subset of the system processor, memory, and I/O resources, and includes operating system and application-related software. The HP-UX operating system is the only operating system that can run in a virtual partition. See also cell, partition, nPartition, server complex. | |
Virtual Server Environment | See VSE. | |
vKVM | OpenVMS Version 8.4 adds support for the iLO Integrated Console capability provided by Integrity Servers and blades systems supporting iLO. The enabling functionality that provides this support is referred to as “virtual Keyboard, Video, and Mouse” or vKVM. The feature allows you to connect a virtual serial line from your PC to Integrity servers, enabling your PC, keyboard, and mouse to function as if directly connected to the server. Your window displays the contents of the Integrity server's VGA. | |
vMedia | Virtual Media. A virtual-disk capability included with iLO MP 2 on Integrity servers. vMedia provides virtual devices that mimic physical hardware devices. For example, it can provide a virtual CD/DVD drive that connects over the network to your Integrity servers as if it were physically connected. You can use vMedia to install OpenVMS on Integrity servers that do not include a built-in DVD drive. vMedia can provide the network service for HP SIM provisioning, or it can be used independently of HP SIM. See also HP SIM, provisioning. | |
volume shadowing | The software that performs disk mirroring operations using a redundant array of independent disks (RAID) 1 storage strategy. Provides high data availability for disk devices by ensuring against data loss that results from media deterioration or controller or device failure. This prevents storage subsystem component failures from interrupting system or application tasks. Volume Shadowing for OpenVMS is available as both a separately licensed product on Integrity server systems and a component of the Data Center Operating Environment (DCOE) on Integrity servers. | |
VSE | HP Virtual Server Environment. An integrated virtualization offering for HP-UX servers (including Integrity servers). VSE provides a flexible computing environment that maximizes utilization of server resources. VSE consists of a pool of dynamically sizable virtual servers, each of which can grow and shrink based on service-level objectives and business priorities. See also gWLM, iCAP, TiCAP. | |
W | ||
warranted support | In OpenVMS Clusters, warranted support means that HP has fully qualified the specified versions of OpenVMS coexisting in the cluster and addresses all problems identified by customers using the cluster configuration. See also migration support. | |
WBEM | Web-Based Enterprise Management. A collection of management and Internet standard technologies that aid and unify management of large-scale distributed computing environments. WBEM provides the ability for the industry to deliver a well-integrated set of standard-based management tools, facilitating the exchange of data across otherwise disparate technologies and platforms. See also WBEM Providers for OpenVMS, WBEM Services for OpenVMS. | |
WBEM Providers for OpenVMS | Available on OpenVMS Integrity server systems, a product that enables (along with WBEM Services for OpenVMS) HP Systems Insight Manager (HP SIM) management of the operating system. HP SIM uses WBEM providers to perform such functions as identifying the operating system on the managed system, associating the virtual or physical instances to their respective containers, providing inventory and reports on hardware and software configurations, and monitoring the system remotely for hardware faults. See also provisioning, WBEM Services for OpenVMS, HP SIM. | |
WBEM Services for OpenVMS | A product available on OpenVMS Integrity server systems that provides an industry-standard enterprise management framework and resource description. WBEM’s structured framework is capable of being extended and uses management and Internet standards. Developers of management applications can take advantage of previously done work that exposes resource information and operations; for example, developers can take code that was developed for a specific platform or application and use it with WBEM for the same purposes—WBEM is platform-neutral, enabling reuse of infrastructure, tools, and applications. WBEMCIM is the WBEM Services for OpenVMS file name used in the PCSI kit. CIM stands for the Common Information Model, which differentiates the current OpenVMS WBEM product from the original one that is based on the Simple Network Management Protocol (SNMP). See also WBEM Providers for OpenVMS. | |
Web-Based Enterprises Services | See WEBES. | |
WEBES | Web-Based Enterprises Services. Tool used for hardware fault detection, analysis, and notification on Integrity, ProLiant, and Alpha based servers along with EVA storage systems. WEBES also performs crash analysis on OpenVMS. |