iCOD Requirements

Program Requirements

You must comply with the following HP Utility Pricing Solutions conditions to participate in the iCOD versions B.06.x program:

For the specific details on your individual iCOD program requirements refer to your Utility Pricing Solutions contract from HP or your authorized channel partner. Participants of the Utility Pricing Solutions program who do not meet these requirements may be in breach of contract. This results in unnecessary expense for both the iCOD program participant and HP.

Software Requirements

Every HP-UX partition in an iCOD system is required to have the iCOD software installed and the icodd daemon running. You must maintain the iCOD software until all program requirements are fulfilled and the system is no longer considered an iCOD system. Refer to “When iCOD Program Requirements End” for details.

HP-UX 11i v1 Requirements

For iCOD Versions B.06.x on
HP-UX 11i v1

The following software is required for iCOD versions B.06.x on HP-UX 11i v1:

• HP-UX 11i v1

• iCOD software bundle B9073BA (versions B.06.x) — installed automatically when the HP-UX 11i v1 Operating Environment (OE) is installed

• The kernel configuration must include the diag2 module

• WBEM B8465BA bundle (version 1.05 or higher) is required for iCOD versions B.06.50 and above

• nPartition provider NPar bundle (version B.11.11.01.03 or higher, available from the OE) is required for iCOD versions B.06.50 and above

Your iCOD system is shipped with all of the above software. In the event your system’s operating system is reinstalled or installed with Ignite-UX, ensure that the above software requirements are satisfied.

	NOTE: On hp 9000 servers rp8400 and rp7410, PDHC firmware version 2.03 is required.

Required Patches for HP-UX 11i v1

The following patches (or superseded patches) are required for HP-UX 11i v1:

• PHKL_22987: S700_800 11.11 pstat() patch - Only if your system runs MeasureWare software

• PHKL_23154: S700_800 11.11 dflush() patch

• PHKL_25218: S700_800 11.11 PDC Call retry, PDC_SCSI_PARMS, iCOD hang fix

• PHKL_26232: S700_800 11.11 Psets Enablement patch,
  FSS iCOD patch

• PHKL_30197: S700_800 11.11 Psets & vPar, Reboot hangs, serial number

• PHCO_24396: S700_800 11.11 /etc/default/tz patch

• PHCO_24477: S700_800 11.11 sar (1M) patch

• PHCO_29832: S700_800 11.11 reboot(1M) patch

• PHCO_29833: S700_800 11.11 killall(1M) patch

	IMPORTANT: For the most recent required patches, see the iCOD Installation page on the HP web site http://software.hp.com (search for “B9073BA”).

E-mail Requirements

Previous versions of the iCOD software (prior to B.06.x) required e-mail connectivity to HP in order to send asset reports as encrypted e-mail messages. iCOD versions B.06.x require e-mail connectivity to HP only:

In addition to the above e-mail requirements, the FROM e-mail address, on e-mail messages sent by the iCOD software from your iCOD system, must be DNS resolvable. See “Configuring iCOD’s FROM E-mail Address” for details of the iCOD FROM e-mail address.

To verify your e-mail connection to HP, see “Diagnosing E-mail Configuration”.

Roles Requirement

Your organization may designate a person to fill a system-contact role for the successful management of iCOD systems. The iCOD system-contact receives the following types of e-mail messages from the iCOD software:

If a system-contact is not specified, processor change notification e-mail messages are not sent from the iCOD partition. However, the root account continues to receive compliance exception notification and TiCOD expiration notification.

License Requirement

An iCOD component is a system component (processor, cell, or memory) that has not been licensed with HP. Before you can use an iCOD component, it must be licensed with HP.

iCOD versions B.06.x manage the licensing of iCOD components through the use of license codewords. After an iCOD component is purchased from HP, a right-to-use (RTU) codeword is available for retrieval from the HP iCOD web portal, located at: http://www.hp.com/go/icod/portal

	NOTE: Contact your HP sales representative in order to purchase an iCOD component. After you have purchased the component, HP sends you a letter informing you how to retrieve the RTU codeword.

After the RTU codeword is retrieved from the iCOD web portal, the RTU codeword is applied by the use of the icod_modify command, with the -C option. An iCOD component becomes a licensed (non iCOD) component after the RTU codeword is applied.

System Move Requirements

If you are planning to move your iCOD system from its current street address you must notify HP for authorization before the system is moved. A move within a building or site that does not change the street address does not require notification to HP.

HP generally authorizes any change of address for an iCOD system as long as the move does not involve crossing national borders.

Before moving the iCOD system, contact the HP iCOD administrator to get an “iCOD Move Authorization Number.” HP has the right to refuse authorization in certain situations. Allow for at least one week for HP to process the authorization. To request authorization for the move, send an e-mail message to the iCOD administrator at icod_admin@hp.com and include the following information:

The iCOD administrator replies to the system-contact, via e-mail, with an authorization number for the specific system move. E-mail or some other form of written authorization from HP must be received before moving the iCOD system.

When iCOD Program Requirements End

	IMPORTANT: Refer to your contract from HP or the authorized channel partner for details of all Utility Pricing program requirements.

iCOD program requirements end after the following requirement has been met:

At this point the system is no longer an iCOD system. E-mail connectivity to HP is not required.