Purchased HP-UX v3 OE |
HP-UX v3 OE License To Use |
HP-UX v1/v2 OE License To Use |
|---|---|---|
| Base OE | Base OE | Foundation OE Technical Computing OE |
| Virtual Server OE | Base OE Virtual Server OE |
Enterprise OE Foundation OE |
| High Availability OE | Base OE High Availability OE |
Enterprise OE Foundation OE |
| Data Center OE | Base OE Virtual Server OE High Availability OE Data Center OE |
Mission Critical OE Enterprise OE Foundation OE |
Note that the prior version (v1/v2) license provided by the HP-UX 11i version 3 OE license applies to the package content of the designated original OE and the additional package content of the HP-UX v3 OE as long as the HP-UX 11i v1/v2 OE is running in the following ways:
» View the HP-UX 11i v3 OE contents and the value of upgrading from v2 to v3 (PDF, 541 KB)
Option 1: DC-OE or VSE-OE or a combination of DC-OE and VSE-OE (recommended)
Option 2: HA-OE and Integrity Virtual Machines or HP Virtual Partitions or Matrix OE – with this option, only BOE, HA-OE and standalone products can be licensed and run in the guest VMs or vPARs
Option 3: BOE and Integrity Virtual Machines or HP Virtual Partitions or Matrix OE - with this option, only BOE, HA-OE and standalone products can be licensed and run in the guest VMs or vPARs
For most environments, it is usually more cost-effective to license one of the virtualized OEs, either DC-OE or VSE-OE, for the entire nPAR or server. Taking this approach also means it will be easier to maintain software license compliance when the size or definition of the contents of a vPAR or Virtual Machine changes.
In addition to the licenses purchased in the options above, customers can cap their licensing costs for standalone software used within an HP 9000 Container, Virtual Machine or vPAR by purchasing only the number of per-core or per-socket licenses needed. This method is called “à la carte,” and the customer needs to carefully pre-define the size and contents of each HP 9000 Container or virtual partition, and make sure he maintains license compliance if there are any changes. Virtualization Licensing is not applicable for software licensed on a per-server or per-cluster basis. Some ISVs also have virtualization licensing policies that a customer can take advantage of to minimize software costs.