iCOD Software

What software product is required for iCOD on Superdome servers? There are separate HP software bundles for iCOD and pay per use (PPU). For iCOD, you should install the iCOD software, product number B9073AA. Do not install the PPU software, product number T1322AA, on iCOD systems.

Can I run both the pay per use software and the iCOD software on a L-, N-, or V-Class server that is running HP-UX 11.0? The pay per use and iCOD software bundles are mutually exclusive. That is, they cannot coexist on the same HP enterprise server.

What patches are required for running iCOD B.05.x software, on a HP enterprise server, that is running HP-UX 11i v1? At the initial release of the iCOD B.05.00 software, the following patches are required:

PHKL_23154 dflush() patch
PHKL_25218 PDC Call retry, PDC_SCSI_PARMS, iCOD hang fix
PHKL_26232: S700_800 11.11 Psets Enablement patch, FSS iCOD patch
PHCO_24477: S700_800 11.11 sar(1M) patch
PHKL_22987: 11i pstat() patch — only if your system runs MeasureWare software

How can I get the iCOD B.05.01 software bundle? The iCOD B.05.01 software bundle B9073AA is installed at the factory for new systems. The B9073AA software bundle must be installed by a HP service representative for existing (non-iCOD) systems. The B9073AA bundle is available on the HP web site: software.hp.com. It is not available on the HP-UX 11i v1 Operating Environment (OE) media.

See “Updating/Installing iCOD Software” for details of installing the iCOD B.05.01 software bundle B9073AA.

One of my HP-UX 11i v1 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 online. Some applications size themselves at startup based on the number of active processors and they don’t adjust for processor increases or decreases. You may try offline activation mode for these types of applications. See “Operating in Offline Activation Mode” for details.

We received an e-mail message indicating the system/partition did not report system configuration data. What is the problem and how do I correct it? Make sure that e-mail is properly configured for the system/partition. On hardware-partitionable systems, such as Superdome, all partitions must be configured to send e-mail to HP. See “E-Mail Configuration” for details. Use the icod_notify command to test e-mail connectivity to HP. This command sends an e-mail message to HP, and if the message is received by HP, a reply message is sent to the system contact.

How much history is retained in the iCOD log files? The iCOD log files retain (approximately) the latest 3000 iCOD events. An iCOD event occurs, and is written to the log files, when one of the following happen:

the iCOD system sends an asset report to HP (scheduled in cron to occur daily at noon)
the iCOD system is shut down
the iCOD system is started
the iCOD system has a configuration change (that is, a processor is activated or deactivated)

You can view all events in the iCOD log files by executing the following command:
/usr/sbin/icod_stat -u

Is the iCOD software license applied by HP, before the iCOD system is shipped to the customer? No. HP does not apply the license prior to shipping iCOD systems to customers. The license for the iCOD software must be applied at the customer’s site. This is because the e-mail connectivity to HP is a crucial part of the iCOD software. See “License Requirement” for details on licensing your iCOD system.

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 rp8400 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 6-1 E-mail sent by the iCOD software

Triggered By	E-mail Message
`icod_notify`	An asset report is sent to the system contact, `root`, and HP (the asset report sent to HP is encrypted).
`icod_notify -c` (daily from `cron`, system startup, system shutdown, and configuration change)	An encrypted asset report is sent to HP.
`icod_modify` (if configuration change notification is turned on)	Information about the configuration change is sent to the system contact and the authorizing manager.
`icod_notify -c` (daily from `cron` - if unlicensed system)	If the system is unlicensed, instructions on how to license the system are sent to the system contact. If the system contact is not set, then instructions on how to set the system contact and license the system are sent to `root`.
system boot	Information about the number of requested active processors being below the minimum number of active processors is sent to the system contact, if set, or to `root` if the system contact is not set.

iCOD Software

Technical documentation

» Table of Contents

» Index