Chapter21 iCOD

8/8/2019 Chapter21 iCOD

1/12

Chapter 21 Instant Capacity On Demand (iCOD)

April 2003 Chapter 21 / Page 1

Chapter 21-

Instant Capacity

On Demand(iCOD)


2/12



INDEX

Introduction 3iCOD customer responsibilities ........................................................................................3

HP field support responsibilities .......................................................................................3

HP response center responsibilities...................................................................................4

iCOD Software and Hardware Requirements 4Hardware requirements .....................................................................................................4

Software requirements HP-UX 11.00 ...............................................................................4

Software requirements HP-UX 11.11 ...............................................................................4

Step by Step (re-)installation of iCOD 5

Activating iCOD CPUs 6

Deactivating iCOD CPUs 7

Redistributing iCOD CPUs across Partitionable Systems 7

iCOD e-mail Requirements 8

iCOD Glossary 10

Additional Information 11


3/12



Introduction

This chapter deals with HPs iCOD program, instant Capacity On Demand, which providescustomers with the ability to allocate additional CPU power for unexpected growth and spikes

in Internet or E-intelligence type of workloads that are difficult to predict. It provides the

customer with the capability to allocate additional CPU power, in addition to those originally

purchased for their HP 9000 Enterprise Servers. The customers must specify how many extra

CPUs they want in reserve and pay a nominal "Right-To-Access Fee" per iCOD CPU.

Currently there are two types of iCOD solutions (clients) being offered. The first type is

iCOD-Purchase (B9073AA) also known as iCOD and the second type is iCOD-Utility or

iCOD PPU (pay per use) (T1322AA).

This document is focused on the so called iCOD-Purchase program only. The iCOD-Utility

option is not fully covered.

Most of the provided information is collected and concentrated from several sources,

especially from the iCOD Users Guide, available from http://docs.hp.com/hpux/pdf/5990-

4343.pdfand the iCOD Familiarization Guide, available from the HP internal site

http://epss.fc.hp.com/icod/misc/documentation.htm. Please take care that this chapter should

only be used as short reference and is not designed to replace the complete and official

guides!

The iCOD program definitely requires that each iCOD system needs to be able to send e-

mails to the hp.com domain. See the following paragraphs for more requirements and

responsibilities.

iCOD customer responsibilities

Provide iCOD systems with the capability to send Internet e-mail to the "hp.com"domain (specifically via /usr/bin/mailx to [email protected]).

Maintain the HP iCOD software, which is a non-intrusive and low overhead softwaremodule that resides on each iCOD system.

Migrate to later iCOD software versions as they become available.Pay the iCOD Right-To-Access fee associated with each iCOD CPU.Not to sell, transfer, assign, pledge or in any way encumber or convey the iCOD

CPUs, without HP's prior written authorization; payment to HP for the purchase of the

iCOD CPU's.

Adherence to the additional terms and conditions as set forth in the HP iCOD Exhibitfor CPUs, signed by the iCOD program participant.

HP field support responsibilities

Verify iCOD software to be installed, install if necessary.Verify the software is valid. This requires the field password.Enter the customer contact information via icod_modify c.Shut down system and install iCOD processors.Reboot system and verify proper execution of iCOD software.
http://wwwpsp.atl.hp.com/lmx_mount/supplan/psp/10/psp10835.htmhttp://wwwpsp.atl.hp.com/lmx_mount/supplan/psp/12/psp12090.htmhttp://wwwpsp.atl.hp.com/lmx_mount/supplan/psp/12/psp12090.htmhttp://docs.hp.com/hpux/pdf/5990-4343.pdfhttp://docs.hp.com/hpux/pdf/5990-4343.pdfhttp://epss.fc.hp.com/icod/misc/documentation.htmhttp://epss.fc.hp.com/icod/misc/documentation.htmhttp://docs.hp.com/hpux/pdf/5990-4343.pdfhttp://docs.hp.com/hpux/pdf/5990-4343.pdfhttp://wwwpsp.atl.hp.com/lmx_mount/supplan/psp/12/psp12090.htmhttp://wwwpsp.atl.hp.com/lmx_mount/supplan/psp/10/psp10835.htm


4/12



Verify e-mail is working, apply License-key from response if necessary.Change number of active processors if necessary.

HP response center responsibilities

Assist HP field support personnel in installing and configuring the iCOD software.Assist the customer in re-installing the iCOD Client Agent on the customers system

according to the iCOD user documentation.

Help the customer get the systems e-mail to send messages to the hp.com domain.

iCOD Software and Hardware Requirements

The implementation of iCOD was done in several phases. Currently phase 5 is in place and it

is recommended to install the current iCOD version on all types of supported iCOD systems.

With this revision the activation of additional processors is achieved via three methods,"instant on-line activation, "off-line activation and deferred activation. No reboot is

required whereas iCOD phase 1 only offered the hard de- and re-configuration of CPUs via

the systems BCH or similar.

Hardware requirements

HP iCOD solutions will be available for all current or new HP customers that have servers

based on PA-8500, PA-8600 or future PA-RISC CPUs. The system platforms supported are

N-Class (N4000) , L-Class (L-2000 and L3000), V-Class systems (V2500 and V2600 with

dual processor boards only, Teststation software 3.1), Superdome (Utility subsystem

firmware 6.40), rp7410 and rp8400 systems.

Software requirements HP-UX 11.00

Extension Pack 9905 or laterSupport Tools Manager, Online DiagnosticsB.11.00.18Patches (may be superseded):

PHKL_22986- 11.00 pstat() patch

PHKL_23001- 11.00 thread_creat() patch

PHKL_23180- 11.00 PM patch

PHCO_22686 - 11.00 top patchPHCO_22733 - 11.00 sar patch

PHCO_21894 - 11.00 vmstat patch

PHCO_21927 - 11.00 iostat patch

PHCO_21928 - 11.00 uptime patch

Software requirements HP-UX 11.11

Support Tools Manager, Online DiagnosticsB.11.11.04Patches (may be superseded):

PHKL_22987- 11.11 pstat() patch

PHKL_23154- 11.11 dflush() patch

PHKL_23176- 11.11 PDC patch
http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_22986http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_22986http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23001http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23001http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23180http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23180http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHCO_22686http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHCO_22733http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHCO_21894http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHCO_21927http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHCO_21928http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_22987http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_22987http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23154http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23154http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23176http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23176http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23176http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23154http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_22987http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHCO_21928http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHCO_21927http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHCO_21894http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHCO_22733http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHCO_22686http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23180http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_23001http://wtec.cup.hp.com/patches-bin/parse/patches-info?Patch=PHKL_22986


5/12



Step by Step (re-)installation of iCOD

In the following section the general steps for installation and configuration of an iCOD

system are listed briefly. Consult the official documentation for a full description.

1. Get and install the recent version (currently 5.00) of the iCOD client software. It can

be either downloaded from http://software.hp.com(search string iCOD) or installed

from a Support Plus CD. The installation itself is done as usual with swinstall(1M).

2. Verify the crontab entry that is configured automatically during installation. As root

user issue crontab l. You should see this entry:

# Send iCOD processor notification at noon daily

0 12 * * * /usr/sbin/icod_notify -c /dev/null 2>/dev/null

3. Enter the customers system contact information. Make sure that a valid e-mail

address is entered! This address used later on by HPs audit system to send

notifications and the license key to.

# icod_modify c John Doe: [email protected]: +4921021234567

If your system is not yet flagged as an iCOD system then you may get this error

message:

ERROR: This system does not contain iCOD processors.

If this statement is not correct, contact your

local support representative to correctly configureyour system.

In this case you need to issue the command icod_modify v first. This commandrequires the hp-only iCOD password. See section section Additional Information for

information where to get this from.

4. Make sure that the FROM field of e-mail sent from the system is externally DNS

resolvable. Otherwise outgoing e-mail will be bounced by the HP mail servers. The

iCOD software agent uses [email protected] as the default FROM e-mail

address (where localhostis the hostname of your iCOD system and domain is its DNS

domain). If the default FROM e-mail address is undesirable, you can configure thesoftware agent (beginning with 5.00) to use a FROM address you specify, e.g.:

# icod_modify f icod-adm@my_company.com

5. View the current iCOD configuration:

# icod_stat

6. Set the number of active processors, e.g. to configure 2 active CPUs:

# icod_modify -s 2 [desc]:user-name:mgr-name:mgr-e-mail:mgr-phone

The following command defers the change until next reboot:
http://software.hp.com/http://software.hp.com/http://software.hp.com/


6/12



# icod_modify D -s 2 [desc]:user-name:mgr-name:mgr-e-mail:mgr-phone

NOTE: As of iCOD client software version 5.00 there is no longer a password

required for this task.

7. Submit a first asset report to HP:

# icod_notify

This command (without the c option, which is used for silent operation) attempts to

send two e-mails executing /usr/bin/mailx, one goes to [email protected], another

one goes to the the contact specified with icod_modify c. The contact person should

receive two e-mails, one from the iCOD system and one as repsonse from

[email protected]. However, there may be a delay in delivery.

The e-mail step is the most critical during the iCOD configuration. See the iCOD e-

mail requirements section on hints how to deal with e-mailing problems.

8. Beginning with iCOD 4.00 a license key needs to applied. The key is included in the

e-mail response [email protected] to the customers contact.

To apply the key enter e.g.:

# icod_modify -l 0E751B21086B276F4C4B56

After that step icod_stat should show License applied: yes . The iCOD

configuration is complete now. The daily icod_notify c issued by cron sends all

audit messages silently.

Activating iCOD CPUs

The moment an iCOD CPU is activated, a purchase order should be submitted to HP or your

authorized channel partner for compensation. Therefore, exercise caution to ensure that an

iCOD CPU is activated purposefully and with organizational approval. This does not apply to

PPU systems (iCOD-Utility).

When you activate an iCOD CPU, the number of active processors in the system increases.

Consequently, this can require you to upgrade the license for some of the software on your

system. A license may be required for HP-UX, HP-supplied software, or software from other

application providers.

NOTE: V-Class processors must always be activated in pairs.

The icod_modify command is used to activate iCOD CPUs.

Example to increase the number of active processors by 2:

# icod_modify -a n [-D] [desc]:user name:mgr name:mgr e-mail:mgr phone# icod_modify a 2 John Doe:[email protected]:+4921021234567
mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]


7/12



Example to set the number of active processors to 8:

# icod_modify -s n [-D] [desc]:user name:mgr name:mgr e-mail:mgr phone

# icod_modify s 8 John Doe:[email protected]:+4921021234567

For deferred online activation, use the D option with the icod_modify command.

If all CPUs are activated (meaning there is no iCOD CPU is left on the system), then the

system is no longer considered to be an iCOD system. The iCOD CPU Agent Software should

be uninstalled. The capability to e-Mail to Hewlett-Packard is no longer required.

Deactivating iCOD CPUs

The icod_modify command is also used to deactivate iCOD CPUs.

Example for deactivation of 2 CPUs:

# icod_modify -d n [-D] [desc]:user name:mgr name:mgr e-mail:mgr phone

# icod_modify d 2 John Doe: [email protected]: +4921021234567

For deferred online deactivation, use the D option with the icod_modify command.

NOTE: As of iCOD client software version 5.00 there is no longer a password required for

deactivating processors.

For hardware-partitionable iCOD systems, deactivating processors in one partition and

activating the same number of iCOD processors in another, will not require an enablement fee

as long as the two events occur within the grace period specified in the iCOD agreement. The

total number of iCOD processors will not change, so HP will not require that the activated

processors be purchased. See section Redistributing iCOD CPUs across Partitionable

Systems. for details.

Redistributing iCOD CPUs across Partitionable Systems

ICOD offers dynamic resizing of partitions on e.g. Superdome systems. Specifically, iCOD

CPUs can be redistributed across any or all partitions. The ability to move iCOD CPUs across

partitions allows you to instantly partition at no charge to you. Its flexibility allows you to

move computing power from partitions where there is an excess of computing power and

redistribute this excess computing power to partitions where more computing power is

needed.

When distributing iCOD CPUs across partitions, the total number of active CPUs in the

complex does not change. However, the number of active CPUs in some partitions decrease,

while the number of active CPUs in other partitions increase.As long as system is in online activation mode, there is no charge. CE operations are

required for offline activation mode and may require a CE service fee.


8/12



A newly deactivated CPU in another partition offsets the cost of a newly activatedCPU.

Example:

Starting scenario:Superdome with two Partitions; Partition 1 has 3 iCOD CPUs, Partition 2 has 2 iCOD CPUs.

Modification Scenario:

You need to add CPUs to Partition 1 but you can afford to take away CPUs from Partition 2

because the active CPUs are underutilized.

Solution:

Decrease iCOD CPUs in Partition 1 by activating one of the iCOD CPUs. Increase iCOD

CPUs in Partition 2, resulting in deactivating one of the active CPUs in Partition 2.

Final Scenario:Superdome with two Partitions; Partition 1 has 2 iCOD CPUs, Partition 2 has 3 iCOD CPUs.

iCOD e-mail Requirements

As part of the auditing process, HP must be able to accurately monitor the use and disposition

of the iCOD processors. E-mail was chosen as the data transport method because of its wide

applicability to a broad scope of companies and its ability to send encrypted data.

NOTE:For hard partitionable systems such as Superdome and rp8400, all iCOD partitions need to

be configured to send e-mail to HP. Each iCOD partition reports the iCOD CPU information

for its partition. It is recommended that the e-mail capability be configured and the iCOD

software be installed on the non-iCOD partitions as well. Performing this function will make

it easier to redistribute iCOD CPUs to partitions that are not currently iCOD partitions if you

decide to do so at a later time.

Before you start:

The iCOD system must be network-accessible to mail servers that are outside your company's

firewalls.

NOTE:

If your iCOD server is on an isolated network, e-mail from the iCOD server will not reach

HP. This will cause your iCOD server to be out of compliance with HP's iCOD Program.

Sendmail

Sendmail is included with the HP-UX core and is installed when HP-UX is ignited. Sendmail

is the application used to send encrypted mail messages from the iCOD CPU agent to HP.

The sendmail daemon, if running, can also be used to receive e-mail.

For the purposes of this e-mail setup, only the ability to send e-mail is required. Mail


9/12



applications invoke sendmail to send e-mail. Sendmail has a configuration file called

/etc/mail/sendmail.cf that offers tremendous flexibility.

High level overview of e-mail routing across the Internet:

When sendmail is invoked to send e-mail to HP by the iCOD software, it first determineswhere it should send the e-mail to (the first hop). Mail often goes through multiple systems

(hops) before it reaches the final destination. To determine the first hop for the e-mail,

sendmail will use one of the following:

1. The e-mail is routed to a mail relay host if it is configured in the sendmail.cf

configuration file. If it is hard-coded software, sendmail will go to a relay host, which

resides in the sendmail.cf configuration file. This is the easiest scenario to implement

and can be done with just a one-line change (DS) to the default sendmail.cf file.

NOTE:

The relay host must be configured to properly route (forward) the mail to the finaldestination.

2. DNS MX records - this method requires that the iCOD server be in an environment

(network) where DNS is operating and properly configured. Sendmail on the iCOD

server will query a DNS server for the name of the mail server to forward the e-mail to

(the mail server for the first hop), in order for the e-mail to reach the final destination

(rsn.hp.com).

In both cases, the following requirements must be met:

1. HP's mail servers receiving mail from the Internet, expect the host that is actuallyconnecting to the HP mail server (the mail server in the last hop before reaching HP)

to be properly registered in DNS (forward and reverse). Otherwise, the HP mail

servers will bounce/reject the e-mail.

2. The 'From' field of the e-mail must also be set so that it is a known address to the

receiving mail server (i.e., the hostname is registered in DNS and advertised on the

Internet). Otherwise, the receiving mail servers at HP will reject/bounce the mail. This

field in the e-mail can also be configured with a simple one-line modification (DM) to

the sendmail configuration file. Another option is to use the f option of the

icod_modify command. For details see section Step by Step (re-)installation ofiCOD.

NOTE:In some DNS environments, no changes to the default sendmail configuration file may be

needed to properly route e-mail from the iCOD server to HP. In some environments,

configuring your iCOD server to properly send e-mail from the iCOD software to HP can

require as little as a two-line edit to the sendmail.cf file. Configuring mail, including sendmail

and DNS configurations, is usually administered by the IT team in most organizations.

Example edit to sendmail configuration (sendmail.cf) on an iCOD server:

Assume hostname is:myICODsystem.my_sitge.my_company.com


10/12



Example sendmail.cf entries:DMmy_company.com

DSmailhub.my_company.com

In this example, using masquerading the "From" field of the e-mail will be set to

user@my_company.com rather than the exact hostname of the iCOD server. This is becausemost organizations do not advertise the names of their internal servers to the Internet,

however they do advertise a few select high level, domain names to the Internet. In this

example, we are assuming the iCOD server is not advertised to the Internet, while hostname

mycompany.com is advertised and reachable from the Internet. In addition, e-mail is forwarded

from the iCOD server to a mail relay host called mailhub.my_company.com . This mail server

may either be directly connected to the Internet and send the e-mail directly to HP, or it may

forward the e-mail to another mail server on its way to HP.

iCOD Glossary

This section describes how the following terms are used in conjunction with iCOD.

activated processors: Processors that are running and available to HP-UX to process your

workloads.

allocated processors: Same as activated processors.

configured iCOD processors: iCOD processors that have been configured at the boot

interface (BCH) and are available for activation.

deallocated processors: Same as deactivated processors.

deactivated processors: Processors that are not available to HP-UX to process your

workloads. Processors that are configured and deactivated are usually available for instant

activation.

deconfigured processors: Processors that have not yet been configured at the boot interface.

iCOD compliance: A customer who has met all terms and conditions of the iCOD purchase

agreement including the e-mail setup requirements.

online activation: The ability to activate an iCOD CPU while HP-UX is running. No reboot

is required. This is done by activating an iCOD processor using the icod_modify command.

This is the default behavior as of iCOD version 2.0.

offline configuration and activation: To manually configure an iCOD CPU for activation

from the boot interface (BCH) and then boot to the UNIX prompt and use the icod_modify

command to activate the processor as you would in the online activation mode (a two step

process). A reboot is required.

partitioning: Breaking up a Superdome or rp8400 complex into two or more logical systems.


11/12



Additional Information

iCOD Users Guide:http://docs.hp.com/hpux/pdf/5990-4343.pdf

iCOD manual pages

icod(5), icod_modify(1M), icod_notify(1M), icod_stat(1M).

HP internal support websitehttp://epss.fc.hp.com/icod

http://epss.fc.hp.com/icod/misc/documentation.htm

iCOD password for processor deactivation with iCOD < 5.00 and for running theicod_modify v command (internal)

http://epss.fc.hp.com/icodpassword/password.htm

iCOD audit reports (iCOD-a Support Query, internal)

http://newshad.rsn.hp.com/icoda/support/index.html

(password on: http://hprtdt58.grc.hp.com/documents/systems/icod/icod.html)

iCOD site of German Response Center (internal)http://hprtdt58.grc.hp.com/documents/systems/icod/icod.html
http://docs.hp.com/hpux/pdf/5990-4343.pdfhttp://docs.hp.com/hpux/pdf/5990-4343.pdfhttp://epss.fc.hp.com/icodhttp://epss.fc.hp.com/icodhttp://epss.fc.hp.com/icod/misc/documentation.htmhttp://epss.fc.hp.com/icod/misc/documentation.htmhttp://epss.fc.hp.com/icodpassword/password.htmhttp://epss.fc.hp.com/icodpassword/password.htmhttp://newshad.rsn.hp.com/icoda/support/index.htmlhttp://newshad.rsn.hp.com/icoda/support/index.htmlhttp://hprtdt58.grc.hp.com/documents/systems/icod/icod.htmlhttp://hprtdt58.grc.hp.com/documents/systems/icod/icod.htmlhttp://hprtdt58.grc.hp.com/documents/systems/icod/icod.htmlhttp://hprtdt58.grc.hp.com/documents/systems/icod/icod.htmlhttp://hprtdt58.grc.hp.com/documents/systems/icod/icod.htmlhttp://hprtdt58.grc.hp.com/documents/systems/icod/icod.htmlhttp://newshad.rsn.hp.com/icoda/support/index.htmlhttp://epss.fc.hp.com/icodpassword/password.htmhttp://epss.fc.hp.com/icod/misc/documentation.htmhttp://epss.fc.hp.com/icodhttp://docs.hp.com/hpux/pdf/5990-4343.pdf


12/12



Chapter21 iCOD

Documents

Transcript of Chapter21 iCOD