HMC andNovaLinkCo-Managed Systems (Disruptive firmware updates only): A co-managed system is managed by HMC and NovaLink,with one of the interfaces in the co-management master mode.Instructions for installing firmware updates and upgrades on systemsco-managed by an HMC and Novalink is the same as above for a HMCmanaged systems since the firmware update must be done by the HMC inthe co-management master mode. Before the firmware update isattempted, one must be sure that HMC is set in the master mode usingthe steps at the following IBM KnowledgeCenter link for NovaLinkco-managed systems: -22A/p9eig/p9eig_kickoff.htmThen the firmware updates can proceed with the same steps as forthe HMC managed systems except the system must be powered off becauseonly a disruptive update is allowed. If a concurrent updateisattempted, the following error will occur: \" HSCF0180E Operation failedfor (). The operationfailed.E302F861 is the error code:\" -22A/p9eh6/p9eh6_updates_sys.htm
The 19-inch PCIe Gen3 4U I/O expansion drawer (#EMX0) provides slots to hold PCIe adapters that cannot be placed into a system node. In 2014, up to two PCIe I/O expansion drawers can be attached per system node, providing PCIe Gen3 adapter slots. Thus a two-node system has a maximum of 48 PCIe Gen3 slots in I/O drawers plus PCIe slots in the system node.
The 90-day temporary elastic CoD processor and memory enablement features enable a system to temporarily activate all inactive processor and memory CoD resources for a maximum of 90 days before you must order another temporary elastic enablement feature number.
With the 2 meter 7014-T42 or feature 0553, a rear rack extension of 8 inches or 20.3 cm (#ERG0) provides space to hold cables on the side of the rack and keep the center area clear for cooling and service access. Including this extension is very, very strongly recommended where large numbers of thicker I/O cables are present or may be added in the future. The definition of a \"large number\" depends on the type of I/O cables used. Probably around 64 short-length SAS cables per side of a rack or around 50 longer-length (thicker) SAS cables per side of a rack is a good rule of thumb. Generally, other I/O cables are thinner and easier to fit in the sides of the rack and the number of cables can be higher. SAS cables are most commonly found with multiple EXP24S SAS drawers (#5887) driven by multiple PCIe SAS adapters. For this reason, it can be a very good practice to keep multiple EXP24S drawers in the same rack as the PCIe Gen3 I/O drawer or in a separate rack close to the PCIe Gen3 I/O drawer, using shorter, thinner SAS cables. The feature ERG0 extension can be good to use even with a smaller numbers of cables as it enhances the ease of cable management with the extra space it provides.
Standard IBM i terms and conditions do not allow either IBM i processor license entitlements or 5250 OLTP (Enterprise Enablement) entitlements to be transferred permanently or temporarily. These entitlements remain with the machine they were ordered for. When you register the association between your primary and on-order CBU system, you must agree to certain terms and conditions regarding the temporary transfer.
Before you can temporarily transfer IBM i processor license entitlements from the registered primary system, you must have more than one IBM i processor license on the primary machine and at least one IBM i processor license on the CBU server. An activated processor must be available on the CBU server to use the transferred entitlement. You may then transfer any IBM i processor entitlements above the minimum one, assuming the total IBM i workload on the primary system does not require the IBM i entitlement you would like to transfer during the time of the transfer. During this temporary transfer, the CBU system's internal records of its total number of IBM i processor license entitlements are not updated, and you may see IBM i license noncompliance warning messages from the CBU system. Such messages that arise in this situation do not mean you are not in compliance.
For example, if you have an 16-core Power 770 as your primary system with four IBM i processor license entitlements (three above the minimum) and two 5250 Enterprise Enablement entitlements (one above the minimum), you can temporarily transfer up to three IBM i entitlements and one 5250 Enterprise Enablement entitlement. During the temporary transfer, the CBU system's internal records of its total number of IBM i processor entitlements is not updated, and you may see IBM i license noncompliance warning messages from the CBU system.
Elastic capacity on demand (elastic CoD) enables processors or memory to be temporarily activated in full-day increments as needed. Charges are based on usage reporting collected monthly. Processors and memory can be activated and turned off an unlimited number of times, whenever you want additional processing resources. With this offering, system administrators have an interface at the HMC to manage the activation and deactivation of resources. A monitor that resides on the server logs the usage activity. You must send this usage data to IBM monthly. A bill is then generated based on the total amount of processor and memory resources utilized, in increments of processor and memory (1 GB) days. Before using temporary capacity on your server, you must enable your server. To do this, order an enablement feature (MES only) and sign the required contracts.
If a Power E870 system node uses the IBM i operating system and the temporarily activated cores were used for IBM i partitions, you must inform the sales team placing the billing feature order which operating system caused the temporary elastic CoD processor use so that the correct feature can be used for billing.
Before requesting temporary capacity on a server, you must \"enable\" it for elastic CoD. To do this, order a no-charge enablement feature (MES only) and sign the required contracts. IBM will generate an enablement code, mail it to you, and post it on the web for you to retrieve and enter on your server. A processor enablement code lets you request up to 90 processor days of temporary unused CoD processor capacity for all your processor cores that have not been permanently activated. For example, if you have 20 processor cores that are not permanently activated, the processor enablement code allows up to 1,800 processor days (20 x 90). If you have reached or are about to reach the limit of 90 processor days per unactivated processor core, place an order for another processor enablement code to reset the number of days you can request. Similarly, a memory enablement code lets you request up to 90 days of temporary unused CoD memory capacity for all your gigabytes of memory that have not been permanently activated. For example, if you had 100 GB of memory that was not permanently activated, the memory enablement code allows up to 9000 GB memory days (100 x 90). If you have reached the limit of 90 memory days per unactivated memory, place an order for another memory enablement code to reset the number of days you can request. Before ordering a new enablement code for either memory or processor temporary CoD, you must first process an MES delete order, deleting the current enablement code installed in the server configuration file.
When Elastic CoD temporary capacity is needed, simply use the HMC menu for elastic CoD and specify how many of the inactive processors or how many gigabytes of memory you would like temporarily activated for some number of days. You will be billed for the days requested, whether the capacity is assigned to partitions or left in the shared processor pool. At the end of the temporary period (days you requested), you must ensure the temporarily activated capacity is available to be reclaimed by the server (not assigned to partitions) or you will be billed for any processor days not returned (per the contract you signed).
When you need temporary capacity, use the Elastic CoD temporary capacity HMC menu for the server and specify how many of the inactive processors or how many gigabytes of memory you would like temporarily activated for some number of days. The user must assign the temporary capacity to a partition (whether or not the machine is configured for LPAR) to begin using temporary capacity.
The contract, signed by the client before receiving the enablement feature, requires the elastic CoD user to report billing data at least once a month (whether there is activity or not). This data is used to determine the proper amount to bill at the end of each billing period (calendar quarter). Failure to report billing data for use of temporary processor or memory capacity during a billing quarter will result in default billing equivalent to 90 processor days of temporary capacity. The sales channel will be notified of client requests for temporary capacity. As a result, the sales channel must order a quantity of billing features (using the appropriate billing features EPJ6, EPJ7, EPJ8, EPJ9, EPJJ, EPJK, EPJL, or EPJM for each billable processor and memory day reported less any outstanding credit balance of processor and memory days).
Utility CoD provides additional processor performance on a temporary basis within the shared processor pool. Utility CoD enables you to place a quantity of inactive processors into the system node's shared processor pool, which then becomes available to the pool's resource manager. When the system node recognizes that the combined processor utilization within the shared pool exceeds 100% of the level of base (purchased/active) processors assigned across uncapped partitions, then a Utility CoD Processor Minute is charged and this level of performance is available for the next minute of use. If additional workload requires a higher level of performance, the system will automatically enable the additional Utility CoD processors to be used. The system continuously monitors and charges for the performance needed above the base (permanent) level. Registration and usage reporting for Utility CoD is made using a public website and payment is based on reported usage. Utility CoD requires PowerVM Enterprise Edition to be active on the 9119-MME. 153554b96e