iCOD Software

What software product is required for iCOD on Itanium-based servers running HP-UX 11i v2? The HP software bundle for the iCOD versions B.06.x software, on Itanium-based servers running HP-UX 11i v2, is HP product number B9073BA.

Can one HP enterprise server be under both a pay per use (PPU) and iCOD contract at the same? No, the pay per use and iCOD software bundles are mutually exclusive. They can both be installed on the same HP enterprise server, but because the server can only be purchased using either PPU or iCOD (but not both), the server can only be configured for the purchased pricing solution.

How can I get the iCOD B.06.x software bundle? The iCOD B.06.x software bundle B9073BA is installed at the factory for new systems; however, if you need to install the software it is available from the following:

HP web site: http://software.hp.com (search for “iCOD”)
September 2004 HP-UX 11i v2 Operating Environments (OE) media (DVD)
September 2004 HP-UX 11i v2 Applications Software media (DVD)
December 2004 HP-UX 11i v1 Operating Environments (OE) media (DVD)
December 2004 HP-UX 11i v1 Applications Software media (DVD)

See “Installing iCOD Software” for details of installing the iCOD B.06.x software bundle B9073BA.

One of my HP-UX applications has compatibility issues with the iCOD software. How do I correct the problem? The application may have a problem when processors are activated or deactivated. Some applications size themselves at system startup based on the number of active processors and they don’t adjust for processor increases or decreases. See “Software Application Considerations” for details.

We would like to utilize temporary capacity (TiCOD) on our Itanium-based server. What system configuration is necessary and how do we acquire TiCOD? See Chapter 5 “Temporary Capacity for iCOD Processors” for details of TiCOD. In general, first make sure that e-mail is properly configured for the system you plan on using TiCOD. All partitions in the system must be configured to send e-mail to HP. See “Diagnosing E-mail Configuration” for details. Next, purchase TiCOD from your HP sales representative, acquire and apply the TiCOD codeword, and then you can activate additional processors with TiCOD.

How much history is retained in the iCOD log files? The iCOD log files retain up to 2 MB of iCOD events. An iCOD event occurs, and is written to the log files, when one of the following happen:

The iCOD software sends an asset report to HP (daily at noon)
An iCOD partition is shut down
An iCOD partition is started
An iCOD partition has a configuration change (that is, a processor is activated or deactivated)
A codeword is applied

You can view all events in the iCOD log files by viewing the file /var/adm/icod.log or/var/adm/icod.log.old.

How can I obtain codewords for iCOD components if the iCOD portal is down? If the iCOD portal is down, contact the HP Response Center. The Response Center can create an emergency codeword via the iCOD codeword backup tool. If you do not receive a timely response from the HP Response Center, contact the iCOD administrator by sending an e-mail message to: icod_admin@hp.com. The iCOD administrator can also create an emergency codeword via the iCOD codeword backup tool.

What licensing is required for the iCOD software? For iCOD versions B.06.x, if you desire to utilize additional iCOD components (processors, cell boards, or memory) then you must license them individually. See “License Requirement” for details.

The resulting configuration of my iCOD system does not agree with what I ordered from HP. How did this configuration change occur? The iCOD software is able to control the granularity of processor activation/deactivation to the single processor level. The iCOD ordering and manufacturing rules often do not allow such fine granularity.

The iCOD ordering rules dictate the quantity of active processors and iCOD processors in the cell boards. Because the iCOD software distributes the active processors and iCOD processors (for a given partition) in a manner that optimizes loads across all cells, the end configuration may be different than the original order — but the number of active and icod processors is the same (that is, they match what was ordered).

For example, if you order a rx8620 server with two cell boards, in which cell board #1 contains 4 active processors and cell board #2 contains 2 active processors and 2 iCOD processors (total of 6 active and 2 iCOD processors), at run time, the iCOD software balances the distribution of active processors across the cell boards so that each cell has 3 active processors and 1 iCOD processor.

What e-mail is sent by the iCOD software? The following table lists the e-mail messages sent to the iCOD system from the iCOD software:

Table 8-1 E-mail sent by the iCOD software

Triggered By	E-mail Message
icod_notify (on demand)	An asset report is sent to the reply address, `root`, and HP (the asset report sent to HP is encrypted).
System startup and system shutdown	An encrypted asset report is sent to HP.
icod_modify (if a configuration change occurs)	Information about the configuration change is sent to the system-contact, if specified, and change notification is set to “on”.
`icodd` (daily at noon)	An encrypted asset report is sent to HP.
icodd (when the projected TiCOD balance expiration is less than 5 days)	A TiCOD expiration notification is sent to the system-contact, if specified, and root.
icodd (if more than expected processors, memory, cells, are active — also if TiCOD has a negative balance)	An exception report (for non-compliance) is sent to the system-contact, if specified, and root.

iCOD Software

Technical documentation

» Table of Contents

» Index