Special Considerations

Instant Capacity Integration with Virtual Partitions

Boot Time Compliance

In the integrated virtual partition environment, a compliance check is performed whenever a virtual partition is booted. If the total number of processors assigned to all virtual partitions in the current vPar database exceeds the nPartition’s intended active processor count, the Instant Capacity software notifies the vPar monitor, and the monitor prevents any virtual partition from booting until the user performs a hard partition boot and modifies either the vPar configuration or the Instant Capacity intended active count for the nPartition.

Example A-2 vPar Boot Time Compliance Message

To: root@par1.yourorg.com

Subject: vPar Boot Time Compliance

This message is being sent to inform you that a vpar is not being allowed to boot because doing so would take this complex out of compliance from an iCOD perspective. The number of CPUs assigned to this vPar database (/stand/vpdb) exceeds the number of licensed CPUs by 1. To correct this problem, boot this partition back into an nPartition and modify the vPars assigned to this database.

Compatible Virtual Partition Environment

Activation and Deactivation of Processors

The Instant Capacity software co-exists with vPars versions less than A.04.01. In this environment, HP recommends using the icod_modify command when modifying processor capacity in a virtual partition. This is the best way to ensure that the complex remains in a compliant state.

To co-exist with vPars, the Instant Capacity software modifies processor capacity using the vparmodify command. When you execute the icod_modify command to deactivate a processor, it determines how many processors in the local virtual partition are unbound. If enough unbound processors exist to satisfy the request, the appropriate vparmodify command is executed, and the proper number of unbound processors are removed from the local virtual partition.

136

Appendix A