Instant Capacity on Demand (iCOD) User’s Guide for versions B.05.x Fourth Edition Manufacturing Part Number: B9073-90040 December 2003 United States © Copyright 2003 Hewlett-Packard Development Company, L.P. All rights reserved.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Copyright 1979, 1980, 1983, 1985-93 Regents of the University of California. This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California. Copyright 1988 Carnegie Mellon University Copyright 1990-1995 Cornell University Copyright 1986 Digital Equipment Corporation. Copyright 1997 Isogon Corporation Copyright 1985, 1986, 1988 Massachusetts Institute of Technology. Copyright 1991-1997 Mentat, Inc.
Publication History The manual publication date and part number indicate its current edition. The publication date will change when a new edition is released. The manual part number will change when extensive changes are made. To ensure that you receive the new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details. IMPORTANT • First Edition: July 2002, 5990-2943, (iCOD version B.05.00 on HP-UX 11.
Contents 1. About this guide Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP On Demand Solutions Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents For HP-UX 11i v1 - Installing from the Support Plus CD . . . . . . . . . . . . . . . . . . . . . For HP-UX 11.0 - Installing from the HP Software Depot . . . . . . . . . . . . . . . . . . . . . For HP-UX 11i v1 - Installing from the HP Software Depot . . . . . . . . . . . . . . . . . . . For All Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reinstalling iCOD Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6. Frequently Asked Questions iCOD Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Superdome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 7. Temporary Capacity for iCOD Processors Utilizing Temporary Capacity for iCOD Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Temporary Capacity. . . . . . . . . . . . . . . . .
Contents Accidental Activation of an iCOD Cell Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 A. Offline Configuration and Activation of Processors Operating in Offline Activation Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting Your System From the Default Online Activation Mode to Offline Activation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents icod_notify (1M) Manpage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 icod_stat (1M) Manpage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 10
1 About this guide This chapter covers the following topics: • “Introduction” on page 12 • “Overview” on page 14 • “iCOD Information” on page 16 • “Conventions” on page 18 For more in-depth information, see the manpage icod (5).
About this guide Introduction Introduction Welcome Welcome to the Instant Capacity on Demand (iCOD) User’s Guide for versions B.05.x. Hewlett-Packard’s instant Capacity on Demand (iCOD) software product provides the ability to increase or decrease processor capacity instantly on (specified) HP enterprise servers. The iCOD software product is a part of HP’s On Demand Solutions program. This user’s guide provides you with the most recent information on using the iCOD versions B.05.x software (versions B.05.
About this guide Introduction Pay Per Use Pay per use (PPU) is a pricing model in which you are charged for actual processor usage. You acquire a specific hardware platform and number of processors, and are charged for the actual usage, based on the number of active processors in the complex. The billing amounts vary as your processor usage needs increase or decrease. This is different than the traditional financing approaches that are based on fixed payment amounts for a specified period.
About this guide Overview Overview Software Product Overview There are two software products associated with HP’s On Demand Solutions program: • iCOD: product number B9073AA • PPU: product number T1322AA You will find only iCOD versions B.05.x information in this user’s guide. For information on PPU, see the appropriate Pay Per Use User’s Guide. The iCOD product has been available on the HP Support Plus media since March 2000 (version B.01.00). The iCOD version B.05.
About this guide Overview iCOD Supported Hardware Platforms Currently, the iCOD versions B.05.x software is supported on the following HP servers: • N-Class: N4000 • L-Class: L2000 and L3000 • V-Class: V2500 and V2600 — V-Class firmware upgrade - V2500/V2600 Test Station Software Release 3.1 or greater — only dual processor boards are supported • Superdome: SD16000, SD32000, and SD64000 • rp7410 • rp8400 Past iCOD Versions and Supported Platforms iCOD Versions The iCOD version B.05.
About this guide iCOD Information iCOD Information iCOD User’s Guide History This is the fourth edition of the iCOD User’s Guide for versions B.05.x. For versions previous to iCOD B.05.x, the information is contained in the iCOD/PPU User’s Guide for versions B.04.x. Locating the iCOD User’s Guide You can find the iCOD User’s Guide for versions B.05.
About this guide iCOD Information • Printed (part number B9073-90020) — order from the following HP web site: www.hp.com/products1/unixservers/solutions/icod/index.html • December 2003 Instant Information CD • In the iCOD B.05.x software product located in: /usr/share/doc/icodRelNotes.pdf Note, this is an early version of this document. For the most recent information see the documents listed above.
About this guide Conventions Conventions This guide uses these typographic conventions: Boldface Words defined for the first time appear in boldface. Computer Computer font indicates system commands, file names, and literal items — which may be displayed by the computer. For example: file not found User input Bold, computer text indicates literal items that you type.
2 Understanding iCOD Requirements This chapter covers the following topics: • “iCOD Program Requirements” on page 20 • “Software Requirements” on page 21 • “E-Mail Requirements” on page 24 • “Roles Requirement” on page 36 • “License Requirement” on page 37 • “iCOD System Move Requirements” on page 39 • “When iCOD Program Requirements End” on page 40 For more in-depth information, see the manpage icod (5).
Understanding iCOD Requirements iCOD Program Requirements iCOD Program Requirements You must comply with the following HP On Demand Solutions conditions to participate in the iCOD program: • Configure iCOD systems/partitions with the capability to send internet e-mail to the “hp.
Understanding iCOD Requirements Software Requirements Software Requirements iCOD systems are required to run the iCOD software which e-mails asset report information to an audit system located at HP. Your system must continue to send asset reports, via e-mail to HP, until all program requirements are fulfilled. Refer to “When iCOD Program Requirements End” on page 40 for details. IMPORTANT This document lists the patches required to install and run iCOD versions B.05.x known at the time of publication.
Understanding iCOD Requirements Software Requirements Required Patches for HP-UX 11.0 The following patches (or superseded patches) are required for HP-UX 11.0 (at the time of publication). All of these patches are available on the Support Plus media: • • • • • • • • • PHKL_22986: PHKL_23001: PHKL_23180: PHKL_25999: PHCO_22686: PHCO_22733: PHCO_21894: PHCO_21927: PHCO_21928: S700_800 S700_800 S700_800 S700_800 S700_800 S700_800 S700_800 S700_800 S700_800 11.00 11.00 11.00 11.00 11.00 11.00 11.00 11.
Understanding iCOD Requirements Software Requirements Required Patches for HP-UX 11i v1 The following patches (or superseded patches) are required for HP-UX 11i v1: • • • • IMPORTANT PHKL_23154: S700_800 PHKL_25218: S700_800 PDC_SCSI_PARMS, iCOD PHKL_26232: S700_800 FSS iCOD patch PHCO_24477: S700_800 11.11 dflush() patch 11.11 PDC Call retry, hang fix 11.11 Psets Enablement patch, 11.
Understanding iCOD Requirements E-Mail Requirements E-Mail Requirements The iCOD software sends an encrypted e-mail message, which contains the iCOD system’s asset report, to an audit system located at HP. See “iCOD System Configuration Information Reported to HP” on page 31 for details of the information reported to HP. The e-mail requirements are: IMPORTANT • The iCOD system/partition is required to have sendmail installed and configured such that it has the ability to send e-mail to the hp.
Understanding iCOD Requirements E-Mail Requirements You can retrieve the above documentation from the HP web site: docs.hp.com Select: Networking and Communications -> Internet Services to access either of the documents. On Superdome Systems For Superdome systems all iCOD partitions must be configured to send e-mail to HP. This is because each iCOD partition reports the processor information for itself.
Understanding iCOD Requirements E-Mail Requirements Overview of E-mail Routing Across the Internet When sendmail is invoked, by the iCOD software, to send e-mail to HP, sendmail determines where it should initially send the e-mail (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 uses one of the following: • The e-mail is routed to a mail relay host if it is configured in the /etc/mail/sendmail.
Understanding iCOD Requirements E-Mail Requirements • Example 2-1 In some environments, configuring your iCOD system to properly send e-mail from the system to HP can require as little as a two line edit (or none) to the /etc/mail/sendmail.cf file. Configuring mail, including sendmail and DNS configurations, is usually handled by the IT team in most organizations. Example Edit to Sendmail Configuration (/etc/mail/sendmail.cf) DMmy_company.com DSmailhub.my_company.
Understanding iCOD Requirements E-Mail Requirements Steps to Confirm or Diagnose E-mail Configuration After you have configured your iCOD system to send e-mail over the internet you can use the following steps to confirm the e-mail configuration or to aid in debugging the configuration: 1. Send an e-mail message from your iCOD system to an e-mail address in the same domain (intranet) and confirm receipt of the e-mail message. 2.
Understanding iCOD Requirements E-Mail Requirements Configuring iCOD’s FROM E-mail Address One of the e-mail requirements of the iCOD program is that the FROM e-mail address, on e-mail messages sent by the iCOD software from your iCOD system to HP, must be DNS resolvable. The iCOD software uses adm@localhost.domain as the default FROM e-mail address (where localhost is the hostname of your iCOD system and domain is its DNS domain).
Understanding iCOD Requirements E-Mail Requirements Configuring Your Server to Send but Not Receive E-Mail For security reasons, some organizations do not wish to allow incoming mail. If you want your iCOD system to be capable of only sending e-mail, and not receiving e-mail, complete the following configuration procedure: Step 1. To prevent the sendmail daemon from starting up again when your system reboots, edit the /etc/rc.config.d/mailservs file, changing the value of SENDMAIL_SERVER to 0: vi /etc/rc.
Understanding iCOD Requirements E-Mail Requirements iCOD System Configuration Information Reported to HP The iCOD software sends an asset report, via encrypted internet e-mail, to HP’s audit application when one of the following events occur: • the periodic iCOD cron task is triggered • the iCOD system is booted • the iCOD system is shut down • the number of requested active processors is changed The asset report contains iCOD system configuration information.
Understanding iCOD Requirements E-Mail Requirements Configuration Change 32 Reply to Contact Status of System Contact’s request for reply e-mail — if set to “true” (1) causes HP to return an acknowledgment e-mail, if set to “false” (0) causes HP to not return an acknowledgment e-mail System Contact Name The name of the person who is the System Contact (responsible for the system) System Contact Phone The phone number of the person who is the System Contact System Contact E-mail The e-mail address
Understanding iCOD Requirements E-Mail Requirements On HardwarePartitionable Systems: Chapter 2 In addition to the above information, hardware-partitionable systems also report the following to HP (note that all partitions should be configured to send e-mail to HP): Local Partition ID The identifier of the iCOD partition, that the information in the above section applies, and through which the complex information was obtained Total Reporting Partitions The total number of reporting partitions in the co
Understanding iCOD Requirements E-Mail Requirements HP receives an asset report from your iCOD system. Here is an example of an asset report sent from a hardware-partitionable iCOD system: Example 2-2 iCOD B.05.x Asset Report iCOD Version:5.0 Client Type:iCOD-purchase Date:01/01/2002 08:00 Local Date:01/01/2002 02:00 MST Event Type:PERIODIC_SYSTEM_AUDIT Serial number:USR0000000 Software ID:abcdef Hostname:par2 NIS Domain name:. Domain name:par2.corp.com Model:9000/800/SD32000 Uname Output:HP-UX par2 B.11.
Understanding iCOD Requirements E-Mail Requirements Testing E-Mail Transmission of the Asset Report NOTE The following procedure assumes your iCOD system is capable of sending internet e-mail and your system contact information is configured. Execute the following command to send your asset report, via e-mail, to HP: /usr/sbin/icod_notify You should receive an acknowledgment e-mail message from HP confirming the receipt of your asset report.
Understanding iCOD Requirements Roles Requirement Roles Requirement Your organization needs to designate people to fill certain roles for the successful management of iCOD systems. There are two main roles to be filled and they are: 36 • System Contact: This person is usually a system administrator and must have root login privileges on the iCOD system. The system contact controls the number of activated and deactivated processors by use of the icod_modify command.
Understanding iCOD Requirements License Requirement License Requirement iCOD systems require the iCOD software (versions B.04.x and B.05.x) to be licensed. The required license is free and ensures communication between your iCOD system and HP. New for versions B.05.
Understanding iCOD Requirements License Requirement Step 4. After HP receives the asset report, a confirmation e-mail containing the license-key, is sent to the system contact (the system contact was set in Step 2, above). See “Testing E-Mail Transmission of the Asset Report” on page 35 for an example of the acknowledgement e-mail message sent by HP. Retrieve the license-key from the system contact’s e-mail. Step 5.
Understanding iCOD Requirements iCOD System Move Requirements iCOD 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.
Understanding iCOD Requirements When iCOD Program Requirements End When iCOD Program Requirements End IMPORTANT Refer to your contract from HP or the authorized channel partner for details of all On Demand Solutions program requirements. iCOD program requirements end after all of the following requirements have been met: 1. all of the processors in the iCOD system are activated 2.
3 Installing and Uninstalling iCOD Software This chapter covers the following topics: Chapter 3 • “Updating/Installing iCOD Software” on page 42 below • “Reinstalling iCOD Software” on page 48 • “Uninstalling iCOD Software” on page 49 41
Installing and Uninstalling iCOD Software Updating/Installing iCOD Software Updating/Installing iCOD Software Factory Integrated You do not need to install the iCOD software if your processors and Systems software were ordered with your HP enterprise server. The iCOD software was already installed by HP prior to delivery.
Installing and Uninstalling iCOD Software Updating/Installing iCOD Software The required patches for iCOD B.05.01 are listed. You can then retrieve the necessary patches from the HP web site: ITresourcecenter.hp.com For HP-UX 11.0 - Installing from the Support Plus CD Follow this procedure to install or upgrade your HP-UX 11.0 iCOD system to version B.05.01: Step 1. Log in as root. Step 2. Determine the CD drive device file by entering the following command: ioscan -fnC disk Step 3.
Installing and Uninstalling iCOD Software Updating/Installing iCOD Software For HP-UX 11i v1 - Installing from the Support Plus CD Follow this procedure to install or upgrade your HP-UX 11i v1 iCOD system to version B.05.01: Step 1. Log in as root. Step 2. Determine the CD drive device file by entering the following command: ioscan -fnC disk Step 3. Insert the Support Plus CD into the CD drive. Step 4. Mount the CD drive to the desired directory.
Installing and Uninstalling iCOD Software Updating/Installing iCOD Software Step 5. Select the link: B9073AA HP-UX 11.00.depot under software download and download the depot file to the following directory: /var/tmp Note that you can name the download anything but by default it is: /var/tmp/B9073AA_B.05.01_HP-UX_B.11.00_32+64.depot Step 6. On the iCOD system log in as root. Step 7. Install the iCOD bundle by entering the following command: swinstall -s \ /var/tmp/B9073AA_B.05.01_HP-UX_B.11.00_32+64.
Installing and Uninstalling iCOD Software Updating/Installing iCOD Software Step 7. Install the iCOD bundle: swinstall -s \ /var/tmp/B9073AA_B.05.01_HP-UX_B.11.11_32+64.depot ’*’ The interactive swinstall can also be used to install the depot file by setting the target to /var/tmp/. The iCOD B.05.x software is low overhead and non-intrusive. The file system size will increase by approximately 2 MB and a reboot is not required. Step 8. Continue with “For All Installations” on page 46.
Installing and Uninstalling iCOD Software Updating/Installing iCOD Software Step 6. Note, this step is necessary only for add-on systems and it must be performed by a HP service representative (SR). An add-on system is a non-iCOD system that has been converted to an iCOD system. If your system is an add-on, then have your HP SR do the following: a.
Installing and Uninstalling iCOD Software Reinstalling iCOD Software Reinstalling iCOD Software Preserving current iCOD information If you reinstall HP-UX on an iCOD system (for example, installing HP-UX by either cold-installing or installing from a “golden image”), all information in the iCOD configuration file disappears unless you do the following: 1. Before the reinstall, manually save your iCOD data and processor allocation history by backing up the following files: a. /etc/.iCOD_data b. /var/adm/.
Installing and Uninstalling iCOD Software Uninstalling iCOD Software Uninstalling iCOD Software If you have fulfilled all of the iCOD program requirements, see “When iCOD Program Requirements End” on page 40, the system is no longer considered an iCOD system. Therefore, the iCOD software is no longer necessary and can be removed.
Installing and Uninstalling iCOD Software Uninstalling iCOD Software 50 Chapter 3
4 Using iCOD to Manage your Processors This chapter covers the following topics: • “Understanding Configuration Change Notification” on page 52 • “Licensing Considerations” on page 54 • “Setting Your System Contact Information” on page 55 • “Checking the Status of your iCOD System” on page 56 • “Increasing Processor Capacity” on page 58 • “Decreasing Processor Capacity” on page 60 • “Overriding Deferred Processor Activations and Deactivations” on page 62 • “Load-balancing Active Processors”
Using iCOD to Manage your Processors Understanding Configuration Change Notification Understanding Configuration Change Notification When you specify an increase or decrease in the number of active processors — using the icod_modify command — this causes a configuration change. When a configuration change occurs an asset report e-mail is sent to the HP audit application. Additionally, a notification e-mail is sent to the system contact and authorizing manager when a configuration change occurs.
Using iCOD to Manage your Processors Understanding Configuration Change Notification Example 4-1 Configuration Change Notification E-Mail for (non-vPar) iCOD System Subject: iCOD Configuration Change Notification A configuration change has been made to the following system: super.corp.com NOTICE: This system is under an iCOD program contract.
Using iCOD to Manage your Processors Licensing Considerations Licensing Considerations License is Required Licensing is required for the iCOD versions B.05.x software. The required license is free and ensures communication between your iCOD system and HP. IMPORTANT You must apply a valid license prior to activating or deactivating processors. An unlicensed iCOD system is incapable of activating and deactivating processors.
Using iCOD to Manage your Processors Setting Your System Contact Information Setting Your System Contact Information If you need to set the system contact information, use the icod_modify command with the -c option. Note that you must specify a valid internet e-mail address. Here is an example session of icod_modify -c: icod_modify -c “Mary Jones:mjones@corp.com:(970)888-9999“ Contact name: Contact e-mail: Contact phone: NOTE: Chapter 4 Mary Jones mjones@corp.
Using iCOD to Manage your Processors Checking the Status of your iCOD System Checking the Status of your iCOD System The icod_stat command lists the status of the processors in the iCOD system.
Using iCOD to Manage your Processors Checking the Status of your iCOD System Sample Session of icod_stat -v on iCOD Superdome System: /usr/sbin/icod_stat -v Version: Contract type: License applied: 5.0 iCOD-purchase yes Hostname: DNS domain name: IP address: NIS domain name: System model: Serial number: Software ID: supericod supericod.corp.com 11.22.33.55 . 9000/800/SD32000 1234567890 abcdef Contact name: Contact e-mail: Contact phone: From e-mail: Mary Jones mjones@corp.
Using iCOD to Manage your Processors Increasing Processor Capacity Increasing Processor Capacity You have the ability to increase processor capacity instantly on (specified) HP enterprise servers with HP’s On Demand Solutions products. At any time, any number of inactive processors can be activated. An inactive processor under warranty or support automatically replaces a failed processor. HP will also service and replace any failed processor.
Using iCOD to Manage your Processors Increasing Processor Capacity iCOD Activation Example Session IMPORTANT V-Class processors can only be activated in pairs. In the following example session, there are a total of 4 processors in the iCOD system; 2 processors are activated and 2 are inactive processors. In this example, 1 additional processor is activated, leaving the iCOD system with 3 active processors (and 1 inactive processor): icod_modify -a 1 “app. demand:mjones:Bill Price:bprice@corp.
Using iCOD to Manage your Processors Decreasing Processor Capacity Decreasing Processor Capacity You have the ability to decrease processor capacity instantly on HP enterprise servers with the iCOD software. At any time, any number of active processors can be deactivated. Processor deactivation can be useful for load balancing processors in hardware-partitionable iCOD systems.
Using iCOD to Manage your Processors Load-balancing Active Processors Load-balancing Active Processors NOTE This section also applies to virtual partitions (vPars). iCOD offers dynamic resizing of partitions on hardware-partitionable systems (for example, Superdome). Specifically, active processors can be redistributed across any or all partitions of a hardware-partitionable system if those partitions contain iCOD processors.
Using iCOD to Manage your Processors Overriding Deferred Processor Activations and Deactivations Overriding Deferred Processor Activations and Deactivations NOTE Only activation of processors is discussed in this section, but deactivation of processors also applies.
Using iCOD to Manage your Processors Overriding Deferred Processor Activations and Deactivations Example 4-3 Undoing an Accidental Deferred Processor Activation 1. On your system or partition you currently have 2 processors activated and 2 processors inactive. You accidentally perform a deferred activation for 1 additional active processor by entering the following command: icod_modify -D -a 1 [desc]:user-name:mgr-name:mgr-email:mgr-phone 2.
Using iCOD to Manage your Processors Moving a Cell from one Partition to Another Moving a Cell from one Partition to Another When moving a cell from one partition to another partition, in an iCOD system, the number of requested active processors for each partition does not automatically change.
Using iCOD to Manage your Processors Software Application Considerations Software Application Considerations Some software applications size themselves based on the number of available processors when the application is started.
Using iCOD to Manage your Processors Understanding Online vs. Offline Activation Methods Understanding Online vs. Offline Activation Methods Online Activation Mode Online (dynamic) activation occurs when you activate processors, using the icod_modify command in either instant or deferred mode, while HP-UX is running. Online activation is the standard method used to activate processors.
Using iCOD to Manage your Processors Understanding Online vs. Offline Activation Methods NOTE Booting a system to the HP-UX prompt can be time consuming, depending on your software and hardware configuration. For information on how to dynamically activate processors, see “Increasing Processor Capacity” on page 58. For information on how to manually configure processors, see Appendix A, “Offline Configuration and Activation of Processors,” on page 109.
Using iCOD to Manage your Processors Understanding Online vs.
Using iCOD to Manage your Processors Processor Test Activation on iCOD Systems Processor Test Activation on iCOD Systems You may desire to test your iCOD system for improved performance by activating an additional processor. The use of temporary capacity (TiCOD) is required for processor test activations. E-mail connectivity to HP is required for the use of TiCOD. See Chapter 7, “Temporary Capacity for iCOD Processors,” on page 83 for details of TiCOD.
Using iCOD to Manage your Processors Replacement of Failed Processors Replacement of Failed Processors In Online Activation Mode If an active processor fails with a Low Priority Machine Check (LPMC), in your iCOD system, its processor capacity is replaced instantly by an inactive processor, if any are available on the system/partition. The failing processor is marked for deconfiguration during the next system reboot.
Using iCOD to Manage your Processors Replacement of Failed Processors In Offline Activation Mode An inactive processor, if available in the system/partition, needs to be manually configured before the processor capacity of the failed processor can be replaced.
Using iCOD to Manage your Processors Processor Activation or Deactivation Delay with vPars Processor Activation or Deactivation Delay with vPars You may experience a delay with processor activation or deactivation in a vPar environment. For example, if you currently have two active processors in your vPar, and you activate an additional processor, by executing the following command: icod_modify -a 1 “app demand:mjones:Bill Price:bprice@corp.
5 Troubleshooting This chapter covers the following topics: Chapter 5 • “Correcting Activation Mistakes” on page 74 • “Troubleshooting the iCOD Software” on page 75 73
Troubleshooting Correcting Activation Mistakes Correcting Activation Mistakes Too Many Processors Activated on iCOD iCOD On HardwarePartitionable Systems 74 For hardware-partitionable systems under an iCOD contract, deactivating processors in one partition and activating the same number of iCOD processors in another, does not require the payment of an enablement fee as long as the two events occur within the grace period specified in the iCOD agreement.
Troubleshooting Troubleshooting the iCOD Software Troubleshooting the iCOD Software In the event the iCOD software is not functioning, perform the following steps: NOTE The following procedure assumes you have entered your system contact information and you can send e-mail over the internet to the hp.com domain. See “E-Mail Requirements” on page 24 for details on configuring e-mail. 1. Verify that HP is able to receive the e-mail message from the iCOD software: a.
Troubleshooting Troubleshooting the iCOD Software 5. Verify that the executables and configuration files have not been deleted and the permissions are set correctly: • /usr/sbin/icod_stat • /usr/sbin/icod_modify • /usr/sbin/icod_notify • /usr/lib/libicod.sl • /etc/.iCOD_data 6. If any of the files in Step 5 (above) are missing or corrupted then re-install the iCOD software. Refer to “Reinstalling iCOD Software” on page 48 for details. 7.
6 Frequently Asked Questions This chapter covers frequently asked questions on the following topics: Chapter 6 • “iCOD Software” on page 78 • “Superdome” on page 82 77
Frequently Asked Questions iCOD Software 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.
Frequently Asked Questions iCOD Software 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.
Frequently Asked Questions iCOD Software 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” on page 37 for details on licensing your iCOD system.
Frequently Asked Questions iCOD Software 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 Chapter 6 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).
Frequently Asked Questions Superdome Superdome What is the difference between iCOD and pay per use on Superdome? Under iCOD: When iCOD processors are activated, you must pay an enablement fee. iCOD processors cannot be deactivated, unless you are load balancing between partitions in a Superdome complex, and not changing the total number of active processors. Under pay per use: You can activate and deactivate processors as your needs change.
7 Temporary Capacity for iCOD Processors This chapter covers the following topics: Chapter 7 • “Overview of Temporary Capacity” on page 84 • “Ordering Temporary Capacity for New iCOD Processors” on page 85 • “Ordering Temporary Capacity for Existing Systems” on page 85 • “Licensing and Support” on page 85 • “Tracking the Purchase and Use of Temporary Capacity” on page 86 83
Temporary Capacity for iCOD Processors Utilizing Temporary Capacity for iCOD Processors Utilizing Temporary Capacity for iCOD Processors Overview of Temporary Capacity New for iCOD versions B.05.x is temporary capacity. Temporary capacity is a HP software product that enables iCOD customers to purchase (prepaid) processor activation rights, for their iCOD processors, for a limited duration of time. Temporary capacity can be purchased in units of 30 processor-days (43,200 processor-minutes).
Temporary Capacity for iCOD Processors Utilizing Temporary Capacity for iCOD Processors Ordering Temporary Capacity for New iCOD Processors iCOD processors do not automatically include temporary capacity rights. To utilize temporary capacity on newly ordered iCOD processors, you first order iCOD processors as you normally do. In addition, order temporary capacity rights separately, in units of 30 processor-days. There is one temporary capacity product per class of HP server.
Temporary Capacity for iCOD Processors Utilizing Temporary Capacity for iCOD Processors Tracking the Purchase and Use of Temporary Capacity NOTE The reply e-mail message, sent from HP in response to the icod_notify command, includes information on your remaining credits of temporary capacity. The HP audit application tracks temporary capacity usage in increments of minutes.
Temporary Capacity for iCOD Processors Utilizing Temporary Capacity for iCOD Processors It is mandatory for your iCOD system to be able to send e-mail to the HP audit application on a daily basis. This is necessary for HP to monitor usage of your iCOD system so that temporary capacity usage can be tracked. If the audit application stops receiving your iCOD system’s e-mail, then HP makes assumptions on processor usage, specifically: 1.
Temporary Capacity for iCOD Processors Utilizing Temporary Capacity for iCOD Processors 88 Chapter 7
8 iCOD Compatibility with vPars and Psets This chapter covers the following topics: Chapter 8 • “iCOD Compatibility with Virtual Partitions” on page 90 • “iCOD Compatibility with Processor Sets” on page 97 89
iCOD Compatibility with vPars and Psets iCOD Compatibility with Virtual Partitions iCOD Compatibility with Virtual Partitions Overview The iCOD version B.05.x software co-exists with virtual partitions (vPars) version A.02.00 or greater. To co-exist with vPars, the iCOD software modifies processor capacity using the vparmodify command. Assigning a processor to a vPar is equivalent to activation and removing a processor from a vPar is equivalent to deactivation.
iCOD Compatibility with vPars and Psets iCOD Compatibility with Virtual Partitions iCOD Software Compatibility with vPars — Supported Hardware Platforms Table 8-1 Software and Version iCOD B.05.x (B9073AA) iCOD Compatibility with vPars — Supported Hardware Platforms Operating System Version HP-UX 11i v1 Supported Hardware Platforms L-Class, N-Class, and Superdome servers Notes vPar software version A.02.00 or greater is required iCOD Compatibility with vPars — Supported Hardware Platforms The iCOD B.
iCOD Compatibility with vPars and Psets iCOD Compatibility with Virtual Partitions Activation and Deactivation of Processors in a vPar The iCOD software uses the vparmodify command to instantly activate and deactivate processors. The activations and deactivations are accomplished by adding and removing unbound processors from a vPar. NOTE Deferred activations and deactivations are not supported in a vPar environment.
iCOD Compatibility with vPars and Psets iCOD Compatibility with Virtual Partitions icod_stat Output Differences in a vPar The following table outlines the differences between a vPar environment and a non-vPar environment for the icod_stat command’s output: Table 8-2 icod_stat Output Differences in vPars icod_stat Option NOTE Chapter 8 Meaning in a non-vPar Environment Meaning in a vPar Environment -i Displays the number of inactive processors available for immediate activation Displays the number o
iCOD Compatibility with vPars and Psets iCOD Compatibility with Virtual Partitions Example Output of icod_stat -p on a Partitionable System Containing vPars /usr/sbin/icod_stat -p Version: Contract type: License applied: 5.0 iCOD-purchase yes Hostname: DNS domain name: IP address: NIS domain name: System model: Serial number: Software ID: zooVpar0 zooVpar0.com 11.22.33.55 . 9000/800/N4000-44 1234567890 abcdef Contact name: Contact e-mail: Contact phone: From e-mail: Mary Jones mjones@corp.
iCOD Compatibility with vPars and Psets iCOD Compatibility with Virtual Partitions Licensing and vPars Once any vPar or hard partition is valid and licensed, the following are valid and automatically licensed (assuming the iCOD software is installed): • other vPars, within the same complex • other hard partitions, within the same complex Static vPars If a vPar is static (that is, the resources cannot be migrated, added, deleted, or modified) and you attempt to activate or deactivate processors, the iCO
iCOD Compatibility with vPars and Psets iCOD Compatibility with Virtual Partitions LPMC and icod_stat Reporting In a vPar environment, the icod_stat command does not report the correct number of “Unassigned processors that can be assigned” if the following conditions occur: 1. the LPMC monitor marks a failing processor for deconfiguration 2.
iCOD Compatibility with vPars and Psets iCOD Compatibility with Processor Sets iCOD Compatibility with Processor Sets Overview The iCOD version B.05.x software successfully co-exists with processor sets (Psets). To co-exist with Psets, the iCOD software only activates and deactivates processors in the default processor set. Processors in non-default processor sets are not activated or deactivated. NOTE Chapter 8 There must be at least one processor in the default processor set.
iCOD Compatibility with vPars and Psets iCOD Compatibility with Processor Sets iCOD Software Compatibility with Psets — Supported Hardware Platforms Table 8-3 Software and Version iCOD B.05.x (B9073AA) iCOD Compatibility with Psets — Supported Hardware Platforms Operating System Version HP-UX 11i v1 Supported Hardware Platforms Notes L-, N-, V-Class, rp7410, rp8400, and Superdome servers iCOD Compatibility with Psets — Supported Hardware Platforms The iCOD B.05.
iCOD Compatibility with vPars and Psets iCOD Compatibility with Processor Sets Scope of the iCOD Software Interacting with Psets The iCOD software does not provide any additional functionality to specifically support adding or removing processors from a specific Pset, and it does not interfere with any Psets on the system. Processor activations and deactivations are limited to the default Pset.
iCOD Compatibility with vPars and Psets iCOD Compatibility with Processor Sets 100 Chapter 8
9 iCOD Cell Board This chapter covers the following topics: Chapter 9 • “Overview” on page 102 • “iCOD Cell Board — Supported Platforms” on page 102 • “Ordering a New System Containing iCOD Cell Board” on page 103 • “HP-UX License and Support” on page 103 • “iCOD Cell Board Activation Fees” on page 104 • “Activation of an iCOD Cell Board” on page 107 • “Accidental Activation of an iCOD Cell Board” on page 108 101
iCOD Cell Board iCOD Cell Board iCOD Cell Board Overview iCOD Cell Board offers you a way to have additional (inactive) cell board capacity in your iCOD system for growing business needs. When the need arises, these iCOD cell boards, which contain memory and processors, are then available for instant activation and use. Similar to the iCOD CPU program, there is an initial right to access fee for an iCOD cell board.
iCOD Cell Board iCOD Cell Board Ordering a New System Containing iCOD Cell Board Initially, you have the right to access an iCOD cell board by ordering the appropriate HP product number, for your specific class of HP server. Additionally, the memory on the iCOD cell board has a separate HP product number for the right to access. NOTE It is highly recommended to have the same number of processors and amount of memory on all cell boards in a given hard partition (nPartition).
iCOD Cell Board iCOD Cell Board iCOD Cell Board Activation Fees Additional fees are payable to HP when you activate an iCOD cell board. Contact your HP sales representative for details. Activating an iCOD cell board causes at least one processor to become active on that cell board.
iCOD Cell Board iCOD Cell Board Example 9-1 Activating an iCOD Cell Board without increasing the number of total active processors For example, if you have a two cell board nPartition with four active processors on one cell board, and an inactive (iCOD) cell board with four iCOD processors, activating the iCOD cell board results in two active processors per cell board. That is, the iCOD software distributes the number of active processors across the two cell boards.
iCOD Cell Board iCOD Cell Board Example 9-2 Activating an iCOD Cell Board and increasing the number of total active processors In a different scenario, activation of an iCOD cell board can cause the number of requested active processors to be below the minimum required (one active processor per cell board) and necessitate the purchase of the newly activated iCOD processor.
iCOD Cell Board iCOD Cell Board Activation of an iCOD Cell Board An iCOD cell board is configured so that it is assigned to a nPartition; however, it does not participate in the boot of the nPartition. Activating an iCOD cell board is a two step process: Step 1. Set the iCOD cell board’s use-on-next-boot flag to “y” Step 2.
iCOD Cell Board iCOD Cell Board Accidental Activation of an iCOD Cell Board If you inadvertently activate an iCOD cell board, you can de-activate it by following this two step procedure: Step 1. Set the iCOD cell board’s use-on-next-boot flag to “n” Step 2. Perform a reboot of the nPartition IMPORTANT You must deactivate the inadvertently activated cell board within five days or the cell board is considered to be purchased from HP.
A Offline Configuration and Activation of Processors This appendix describes managing your processors in offline activation mode. If you are dynamically activating your inactive processors using the online activation mode, you do not need to read this appendix.
Offline Configuration and Activation of Processors Operating in Offline Activation Mode Operating in Offline Activation Mode This section outlines the basic steps to take when operating in offline activation mode in several situations. Most software applications work fine with the online activation method. However, some applications erroneously regard inactive processors to be active processors. These types of applications may exhibit functional or performance problems.
Offline Configuration and Activation of Processors Operating in Offline Activation Mode Step 3. Boot the system Activating a Deconfigured Processor in Offline Activation Mode At some time after you have deconfigured processors, you may desire to activate the deconfigured processors. To accomplish this, you must first convert the deconfigured processors into deactivated processors, and then activate the processor.
Offline Configuration and Activation of Processors Operating in Offline Activation Mode System state: • • • The system is booted One or more processors are deconfigured No processors are deactivated by iCOD software Procedure: Step 1. Reboot the system and stop the boot process at BCH Step 2. At BCH, configure processors per configuration rules Step 3. Boot the system (iCOD software deactivates the previously deconfigured processors) Step 4.
Offline Configuration and Activation of Processors Receiving a System Alert on L-Class and N-Class on Hard Reset Receiving a System Alert on L-Class and N-Class on Hard Reset When L-Class and N-Class iCOD systems undergo a hard reset, the PDC firmware displays a level 6 system alert for each deconfigured processor. A hard reset is accomplished by either cycling the power, or by entering the RS (reset) command on the Management Processor (MP) interface.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the L-Class and N-Class Servers Configuring and Activating Processors for the L-Class and N-Class Servers This section illustrates the procedure for configuring a processor on both the L-Class and N-Class servers. The BCH interface is practically identical for both classes of servers.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the L-Class and N-Class Servers An L-Class system can contain up to 4 processors. Configure these processors in the following order: • • • • 0 3 1 2 Always deconfigure processors in the reverse order. Step 1. Reboot the system from the system console. Step 2. Access the BCH interface.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the L-Class and N-Class Servers Step 3.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the L-Class and N-Class Servers Step 4.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the L-Class and N-Class Servers Step 6.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the L-Class and N-Class Servers Step 9. Verify from HP-UX that the processors are available with the ioscan HP-UX command. Note the information provided by ioscan on the number of active processors is different from that reported during configuration.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the V-Class Server Configuring and Activating Processors for the V-Class Server This section illustrates the procedure for configuring or activating a processor for the V-Class. For additional information on the V-Class boot sequence and other operating instructions please consult the V2500 Server Operator’s Guide at: docs.hp.com/hpux/hw under V-Class. Step 1.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the V-Class Server Step 3.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the V-Class Server Step 4. Determine if the V-Class has Single or Dual Processor Boards. Determining if the V-Class has Single or Dual Processor Boards If there are a pair processors numbered n and n+16 then the system uses dual processor boards. In the example below there are two processors numbered 0 and 16; therefore, the system uses dual processor boards and the two processors reside on one processor board.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the V-Class Server Dual Processor Board Configuration Sequence 0 and 16 8 and 24 2 and 18 10 and 26 5 and 21 13 and 29 7 and 23 15 and 31 1 and 17 9 and 25 3 and 19 11 and 27 4 and 20 12 and 28 6 and 22 14 and 30 Step 5. Configure the processor with the following command (in this example, we are configuring processors 10 and 26): [0] Command: [0] Command: CPU 10 ON CPU 26 ON Step 6.
Offline Configuration and Activation of Processors Configuring and Activating Processors for the V-Class Server 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 [0] Command: Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor Processor not installed configured, not not installed configured, not not
Offline Configuration and Activation of Processors Configuring and Activating Processors for the V-Class Server processor processor processor processor processor processor /> 2 3 4 5 6 7 24 26 32 34 40 42 processor processor processor processor processor processor CLAIMED CLAIMED CLAIMED CLAIMED CLAIMED CLAIMED PROCESSOR PROCESSOR PROCESSOR PROCESSOR PROCESSOR PROCESSOR Processor Processor Processor Processor Processor Processor This completes the processor offline configuration and activation proces
Offline Configuration and Activation of Processors Configuring and Activating Processors for Hardware-partitionable Systems Configuring and Activating Processors for Hardware-partitionable Systems Activation of processors in offline activation mode on hardware-partitionable systems is not a user executable operation. If you use the offline activation method, and you wish to activate a processor, you need to contact your HP service representative.
B Special Considerations This appendix describes special considerations for iCOD systems.
Special Considerations iCOD and pstat, pstat_getdynamic, and mpctl System Calls iCOD and pstat, pstat_getdynamic, and mpctl System Calls Applications that are dependent on the number of active processors most likely depend on the system calls pstat and mpctl. pstat pstat_getdynamic now returns the number of active processors in pst_dynamic.psd_proc_cnt. In the original release of HP-UX 11.00, it was always the same as pst_dynamic.psd_max_proc_cnt. That field now includes deactivated processors.
Special Considerations iCOD and pstat, pstat_getdynamic, and mpctl System Calls Note that even though these average fields are adjusted, no information is lost because psd_mp_avg_*_min and psd_mp_cpu_time[] still contain deactivated processor values. mpctl MPC_GETNUMSPUS now returns the number of activated processors. Earlier versions of this command reported activated and deactivated processors in this field. MPC_GETFIRSTSPU now returns the first activated processor.
Special Considerations Measurement Software on iCOD Systems Measurement Software on iCOD Systems iCOD systems inherently have fewer active processors than the total number of processors in the system. This fundamental difference between the number of active processors and the total number of processors can cause some processor measurement products and utilities to report incorrect information.
Special Considerations Differences Between Supported Platforms Differences Between Supported Platforms With the iCOD software, HP enterprise servers that are single partition machines — for example: L-, N-, and V-Class servers — have a few differences with multi partition machines, such as Superdome. The differences are summarized as follows. L-, N-, and V-Class Systems System alerts are handled differently on L- and N-Class systems.
Special Considerations Differences Between Supported Platforms On iCOD Superdome Systems: When running the iCOD software on hardware-partitionable systems, the number of iCOD processors is audited for your complex as a whole, not an individual partition. iCOD software must be installed and configured on all partitions that contain iCOD processors. It is important not to remove the iCOD software from all partitions in your complex unless you have activated and purchased all iCOD processors.
Special Considerations Firmware Requirements Firmware Requirements V-Class Systems On V-Class iCOD systems, V-Class firmware upgrade V2500/V2600 Test Station Software Release 3.1 or greater is required. Superdome Systems The Utility subsystem firmware version must be 6.40 or greater. The iCOD software is not supported on firmware versions prior to 6.40.
Special Considerations Dynamic Processor Resilience (DPR) Dynamic Processor Resilience (DPR) The LPMC monitor, within the Support Tools Manager (STM) diagnostics, generates Information events for all cache errors that are detected. After three errors (Threshold) have been detected on a processor in 1440 minutes, or a 24-hour period of time (Period), the monitor deactivates that particular processor, mark it for deconfiguration on the next system reboot, and generate a SERIOUS event.
Special Considerations Requested Active Processors Below Minimum Required Requested Active Processors Below Minimum Required For Partitionable iCOD Systems Your iCOD system has a minimum number of processors that are required to be activated. The minimum number of active processors in a partition is one per cell board. If the requested number of active processors is less than the required minimum number of active processors, the system contact for your iCOD system receives a notification e-mail message.
Special Considerations Requested Active Processors Below Minimum Required 136 Appendix B
C Appendix C Glossary 137
Glossary iCOD Terminology iCOD Terminology The following terms are commonly used in conjunction with iCOD: activated processors Processors that have been turned on by the iCOD software or during installation. Processors are activated with the icod_modify command while HP-UX is running. add-on system A non-iCOD system that has been converted to an iCOD system. This process is performed by a HP service representative. bound processor Bound processors have I/O interrupts assigned to them.
Glossary iCOD Terminology deconfigured processors Processors that have not yet been configured at the boot console interface (BCH). The iCOD software cannot activate a processor that is deconfigured. enablement fee The fee a customer pays to activate and use an iCOD processor. This fee pertains to only the iCOD program. hard partition A physical partitioning of a computer that divides the computer into groups of cell boards where each group operates independently of the other groups.
Glossary iCOD Terminology inactive processor A processor in an iCOD system that is currently inactive, but is capable of activation by use of the icod_modify command. An inactive processor is also referred to as a “deactivated processor”. migrating processors The process of activating and deactivating processors across partitions for load-balancing. See “Load-balancing Active Processors” on page 61 for more information.
Glossary iCOD Terminology right to access The initial fee a customer pays to enter the iCOD program and physically acquire possession of an iCOD (inactive) processor. temporary capacity An HP product that enables customers to purchase prepaid processor activation rights, for a specified (temporary) period of time. Temporary capacity is sold in 30 processor-day increments. Temporary capacity is available on HP-UX 11i v1 only.
Glossary iCOD Terminology 142 Appendix C
D iCOD Manpages This appendix contains the manpages for iCOD commands.
iCOD Manpages iCOD (5) Manpage iCOD (5) Manpage iCOD (5) NAME iCOD – instant Capacity on Demand software for HP-UX DESCRIPTION iCOD provides services for instantly increasing processing capacity on supported HP servers to respond to increasing system demands. When the processing demand significantly changes, the user executes the icod_modify (see icod_modify (1M)) command to instantly activate or deactivate processors, or defer an activation or deactivation until the next reboot.
iCOD Manpages iCOD (5) Manpage 3) Execute the icod_notify command (see icod_notify (1M)) to send an asset report to both HP and to the system contact e-mail address. HP will respond to this asset report by sending a second e-mail to the system contact address. This verifies that e-mail communication with HP has been established. E-mail communication is required between the iCOD server and HP because iCOD servers are required to send asset reports to HP to report iCOD processor usage.
iCOD Manpages iCOD (5) Manpage Software Removal After all contractual obligations have been satisfied, the iCOD software bundle can be uninstalled from the system using the swremove command (see swremove (1M)). NOTE: iCOD software cannot be removed from a system until all processors in the system have been activated. Hardware-Partitionable Systems (e.g. Superdome) Hardware-partitionable systems support more than one instance of an operating system by partitioning the system into separate systems.
iCOD Manpages iCOD (5) Manpage Processor Sets In an environment where processor sets are being used, icod_modify will activate iCOD processors into the default processor set and will deactivate processors only from the default processor set. Activation or deactivation of processors in non-default processor sets is a two step operation, where one step is the migration of processors into or out of the default processor set and the other step is the activation or deactivation of those processors.
iCOD Manpages icod_modify (1M) Manpage icod_modify (1M) Manpage icod_modify (1M) NAME icod_modify – activate and deactivate instant Capacity on Demand (iCOD) processors, change system contact information, and apply a software license to use SYNOPSIS /usr/sbin/icod_modify -c /usr/sbin/icod_modify -l /usr/sbin/icod_modify -f icod_modify [-D] -a <[desc]:usr_name:mgr_name:mgr_e-mail:mgr_phone> icod_modify [-D] -d <[desc]:usr_name:mgr_name:mgr_e-mail:mgr_pho
iCOD Manpages icod_modify (1M) Manpage Options and Arguments icod_modify recognizes the following options and arguments: -c Changes the system contact information, where name is the system contact name, e-mail is the system contact e-mail address, and phone is the system contact phone number. This information is used by HP so that information requested via the icod_notify command can be returned via e-mail. -l Applies a software license to use to the system.
iCOD Manpages icod_modify (1M) Manpage EXTERNAL INFLUENCES Environment Variables • LANG determines the locale to use for the locale categories when both LC_ALL and the corresponding environment variable (beginning with LC_) do not specify a locale. If LANG is not set or is set to the empty string, a default of “C” is used (see lang (5)). • LC_CTYPE determines the interpretation of single- and multi-byte characters. • LC_TIME determines the date and time strings output.
iCOD Manpages icod_notify (1M) Manpage icod_notify (1M) Manpage icod_notify (1M) NAME icod_notify – send asset reports to HP for instant Capacity on Demand (iCOD). Turn change notification on or off. Request response e-mail from HP. SYNOPSIS /usr/sbin/icod_notify /usr/sbin/icod_notify -c /usr/sbin/icod_notify -n on|off DESCRIPTION If no options are specified to icod_notify, an asset report e-mail is sent to HP, root and the system contact e-mail address (see icod_stat (1M)).
iCOD Manpages icod_notify (1M) Manpage Options icod_notify recognizes these options: -c Sends asset report e-mail only to HP. Asset report e-mail will not be sent to root and the system contact e-mail address, and a confirmation e-mail will not be sent to the system contact e-mail address from HP. However, if a license to use hasn't been applied to this system, licensing instructions will be sent to the system contact e-mail address (or root if not specified).
iCOD Manpages icod_notify (1M) Manpage International Code Set Support Single- and multi-byte character code sets are supported. RETURN VALUE icod_notify exits with one of these values: 0 Command succeeded. >0 Command failed; error message sent to STDERR. AUTHOR icod_notify was developed by HP. SEE ALSO icod_modify (1M), icod_stat (1M), icod (5).
iCOD Manpages icod_stat (1M) Manpage icod_stat (1M) Manpage icod_stat (1M) NAME icod_stat – display instant Capacity on Demand (iCOD) processor status, usage information, and system information SYNOPSIS /usr/sbin/icod_stat [-pv] /usr/sbin/icod_stat -a|i|I|t|r /usr/sbin/icod_stat -u DESCRIPTION The icod_stat command displays the processor status, usage information, and system information on a system equipped with iCOD processors.
iCOD Manpages icod_stat (1M) Manpage Appendix D System model: This field displays the model of the system as returned by the model command (see model (1)). Serial number: This field displays the system's serial number. Software ID: This field displays a unique identifier for the system as returned by the getconf command (see getconf (1)). Contact name: This field displays the system contact name for this system, as specified by the user via the icod_modify command.
iCOD Manpages icod_stat (1M) Manpage Information displayed for non-virtual partitions The following status is displayed when icod_stat is run on a non-partitionable system or on a hardware partition where virtual partitions are not being used: Total processors: This field displays the total number of processors physically present in the system. Active processors: This field displays the number of processors being used by the operating system.
iCOD Manpages icod_stat (1M) Manpage Information displayed for virtual partitions The following status is displayed when icod_stat is run on a virtual partition: Assigned processors: This field displays the number of processors assigned to the local virtual partition. Active assigned processors: This field displays the number of assigned processors in the local virtual partition that are active.
iCOD Manpages icod_stat (1M) Manpage Options icod_stat recognizes these options: -a Displays the number of active processors on the system. -i Displays the number of inactive processors available for instant activation. For virtual partitions, displays the number of unassigned processors that can be instantly assigned to the local virtual partition. -I Displays the total number of inactive processors. This number includes any deconfigured processors and inactive processors that cannot be activated.
iCOD Manpages icod_stat (1M) Manpage Requested active processors: The number of processors the user requested to be active. Description: A user specified description documenting why processors were activated or deactivated. Changed by: The name of the individual performing the change to the configuration. Manager: The name of the manager or the individual granting approval for the change. E-mail address: The e-mail address of the authorizing manager.
iCOD Manpages icod_stat (1M) Manpage EXTERNAL INFLUENCES Environment Variables • LANG determines the locale to use for the locale categories when both LC_ALL and the corresponding environment variable (beginning with LC_) do not specify a locale. If LANG is not set or is set to the empty string, a default of “C” is used (see lang (5)). • LC_TIME determines the date and time strings output. • LC_MESSAGES determines the language in which messages (other than the date and time strings) are displayed.
Index A activated processors, defined, 138 activation modes, online and offline, 66 add-on system, defined, 138 asset report e-mail example, 34 information sent to HP, 31 testing e-mail transmission, 35 authorizing manager, role requirement, 36 B bound processor, defined, 138 C cell,moving, 64 configuration change notification, 52 configured processors, defined, 138 configuring processors L- and N-Class, 114 Superdome, 126 V-Class, 120 conventions, User’s Guide, 18 cron configuration requirements, 23 D deac
Index too many processors activated, 74 troubleshooting software, 75 uninstalling software, 49 iCOD audit application, 12 iCOD Cell Board accidental activation, 108 activating, 107 activation fees, 104 supported platforms, 102 iCOD processors, defined, 139 iCOD software frequently asked questions, 78 iCOD software requirements HP-UX 11.
Index iCOD, defined, 139 inactive, defined, 140 migrating, defined, 140 monarch, defined, 140 too many activated on iCOD, 74 unbound, defined, 141 program requirements, On Demand Solutions, 20 Psets compatibility with iCOD, 97 pstat system call, special considerations, 128 User’s Guide conventions, 18 obtaining, 16 V V-Class, firmware requirements, 133 virtual partition, defined, 141 vPars compatibility with iCOD, 90 icod_stat differences, 93 R reinstall, preserving iCOD information, 48 Release Notes, obt
