Welcome to Knowledge Base!

KB at your finger tips

This is one stop global knowledge base where you can learn about all the products, solutions and support features.

Categories

All

CRM

Salesforce

ERP

SAP

Storage and Backups

Purestorage Netapp Nutanix

Cloud

AWS

Computing

IBM

Database

MongoDB MySQL PostgreSQL

DevOps

Docker Kubernetes Jenkins GitLab

Mobile

React Native Android

Web

React Angular PHP

Programming

Python

Products

CNC Software (Mastercam) 3D perception 7shifts ABB EV Charging Infrastructure Accelo Aconex (by Oracle) Act-On Actenum Scheduler Actico Compliance Suite ActiveCampaign Adapt Addepar Adobe Captivate Adyen AG Leader Agrivi AgriWebb Agworld Ahrefs Aidoc AIMS360 Akamai Kona Site Defender Algolia Alis by TalentGuard ALLDATA Repair Allscripts Alpaca Trading Altair HyperWorks Altium Designer AMOS Amplitude Anaplan Anessa Biofuel Optimization AppDynamics Applied Epic Applied Materials E3 Aptean ERP Aptean Food & Beverage ERP Aptima Aquatic Informatics’ WaterTrax Arable Arena Solutions PLM Articulate 360 Asana ASML Twinscan Aspen Plus Biochemical Process Modeling Aurora Solar AspenTech APC Athenahealth Atomwise Audiam Audiomovers AspenTech for Refining Autodesk AutoCAD Autosoft AspenTech Pharma Suite Asset Panda Aveva Marine AssetMark Aveva Pipeline Management AVEVA Process Engineering Suite AVEVA Refining Solutions AVEVA Unified Operations Center Avid Media Composer AVL eSuite AWS Ground Station AWS IoT Greengrass Azure IoT Central Azure Space Backbase BatchMaster ERP Benchling Bentley OpenFlows Bentley OpenRoads Bentley OpenUtilities Bentley Systems AssetWise Bentley Systems – OpenRail beonic BevSpot Bigbelly Smart Waste & Recycling System BigCommerce Automotive Bitly Bitmovin Blackbaud BlackBerry AtHoc Blackboard Learn BlackLynx Blend Blue Yonder WMS Bluebeam Revu Bohemia Interactive Simulations (BISim) Bosch Esitronic Diagnostic Bosch IoT Suite Braintree Bright Biomethane Brightpearl Bringg Browzwear Builder Prime Buildertrend BuildTools BWX Technologies' Nuclear Security Cabinet Vision Cadence OrCAD Cadence Virtuoso CAE Canvas LMS Cargowise One Carrier i-Vu CaterZen CattleMax CDK Global Celtx Cerner Pharmacy ChargePoint Cloud Services Charles River Development Check Point CloudGuard Checkout.com Cin7 Circularise Cisco Umbrella Classcraft ClearDATA ClearMetal ClickFunnels ClickUp Climate FieldView Clir Renewables Cloud Lending (Q2 Software) Cobb Accessport ComplianceQuest ComplyAdvantage Conducttr Conservis Continental Connected Vehicle Copper Coupa by LLamasoft CQG Integrated Client Creatio Creatio marketing CropNutrition CrowdStrike Falcon CyberSource Damarel Darktrace Dassault Systèmes CATIA Dassault Systèmes ENOVIA Dataminr DaVinci Resolve DealerSocket DealHub Decisive Farming Deliverect Deltek Costpoint Demandbase Denso EV Thermal Systems DeSL (Digital Enterprise Software) DigitalOcean DJI Ground Station Pro Docebo DrillPlan by Schlumberger DroneDeploy e-Builder Ecochain EcoVadis Edmentum Edsby EFI Live Tuning EFI Optitex EFI PrintSmith Vision Ellie Mae Encompass Ellucian Banner Elucidat Emerson Ovation Emerson Plantweb eMoney Advisor Enact Systems Enfusion Envestnet | Tamarac Epicor ERP Epicor Parts Network Esko ArtiosCAD Esko WebCenter ETQ Reliance QMS Everbridge eVinci™ Micro Reactor by Westinghouse Exostar SCM Fanuc Automation Fanuc Robotics FarmERP FarmLogs FieldAware Finacle Finastra Fusion FinQuery Flatiron Health FoodLogiQ Fortinet FortiGate FourKites Freshworks GDC Technology GE Digital APM GE Digital Plant Applications GE Digital Predix GE Healthcare FlexFactory GE Vernova Genscape Pipeline Solutions Geofeedia GeoSoftware Geotab GEP SMART Gerber Technology GetAccept Gorgias Greenbyte Energy Cloud Greenlight Guru GreenPrinter GreenSlate Guidewire Software Handshake HawkEye 360 Health Catalyst Herdwatch Hexagon Intergraph CAD Hexagon Manufacturing Intelligence Hexagon MSC Software Hexagon PPM Hexagon Safety & Infrastructure Hexcel HexPly Honeywell Enraf Tank Gauging Honeywell Forge Honeywell Forge for Chemicals Honeywell UOP Ecofining Houzz Pro HP Indigo Digital Press HP Tuners VCM Suite HubSpot CRM IBM i2 IBM Watson Health IFS Applications Illuminate Education Imprivata Indra Air Automation InEight Infor CloudSuite Food & Beverage Infor EAM Infor LN Infor WMS Inmarsat Fleet Data Instapage Insurity Intellect QMS Intergraph SmartMarine 3D Intex ERP Intuitive Surgical da Vinci IONOS Ironclad iSpring Suite John Deere Operations Center Johnson Controls Metasys Juro JustFood ERP Kahoot Kahua Kareo KBC Petro-SIM by Yokogawa Keap Kiinaxis RapidResponse Kinaxis RapidResponse Kisters WISKI KLA YieldStar Klaviyo Knewton Alta Kratos OpenSpace KUKA Robotics KUKA Smart Production Kustomer Landr LeadAngel LeanData Lectra Fashion PLM Leidos Integrated ISR Solutions Linode Lithium Balance BMS Lockheed Martin DiamondShield LogicGate Logility LogiNext Mile LuciadLightspeed (Hexagon) Luma Health Mahle Thermal Management Majesco Mallcomm MAM Software Autopart Manhattan TMS Manhattan WMS Mark43 MASS (Cohort plc) MasterControl Manufacturing Excellence MasterControl Quality Excellence Material Exchange McKesson Pharmacy Management MedeAnalytics Medidata Solutions Medtronic CareLink Medtronic Hugo RAS Mentor Graphics (Siemens) MetricStream Microsoft D365 SCM Microsoft Project MilliporeSigma BioContinuum MindTickle Mirakl Mitchell1 ProDemand MODS (Military Operational Decision Support) Moodle Moody’s Analytics Morningstar Direct MRI Facilities Management MuleSoft MyPath Nautilus Labs Navitaire nCino Nearpod Netafim NetApp Netwrix Auditor NextGen Healthcare NICE Actimize NICE Public Safety Nimble Nutshell Nuvation Energy BMS Nuvolo Office Furniture by Haworth Omnisend OneTrust OneWeb Satellite Services Onfleet Optibus Optimizely ONYX InSight Oracle E-Business Suite Oracle FLEXCUBE Oracle TMS Orion Advisor Tech OSISoft PI System Outgrow OVHcloud PagerDuty Palo Alto Networks Cortex XSOAR Palo Alto Networks Prisma Cloud PandaDoc Panorama Education Parrot Analytics Petrel by Schlumberger Philips HealthSuite PipelineManager by Atmos International Pipeliner CRM PitchBook Pix4Dfields Planet Labs Plex Systems PowerSchool PredictHQ Printavo Procore Project44 Proposify Prospera PTC Windchill Quantifi QuarkXPress Quipli Quorum Distribution Software R1 RCM Rackspace Rapyd ReCharge Reynolds and Reynolds Rightsline Riskalyze Roostify Runway ML S&P Capital IQ Sabre AirCentre Safefood 360 Saipher ATC SAP Defense & Security Sapiens CoreSuite Oracle Cloud SCM Oracle NetSuite Plex Manufacturing Cloud QbDVision Ramco Aviation MRO Suite RedTeam SAP EWM SAP Supply Chain Management SAS Analytics Schoology ScreenCloud Sensia Oilfield Monitoring and Control SentinelOne Serpstat Shift Technology Shift72 ShipBob ShipServ Shopify Plus Shopify Plus for Automotive Shotgun (by Autodesk) Siemens Simcenter Signal Sciences SimCentric Technologies SimCorp Dimension SimScale Simutech Multimedia Skedulo SkillMill by Interplay Learning Skyfii SkyWatch EarthCache Slingshot Orbital Smartsheet for Compliance Snapsheet Solutionreach Soyang Europe Green Materials Sparta Systems TrackWise Sphera Sustainability Management Spire Space Services Splunk Enterprise Security Splunk Industrial IoT Square for Retail StormGeo Stratasys 3D Printers Stripe STRIVR StudioBinder SUSE Swissport Symantec Endpoint Security (Broadcom) Synopsys TCAD Syntasa TalentLMS TankVision by Endress+Hauser Teladoc Health Tenable.io Terminus TexGen Thales CipherTrust Thales Manpack EW Suite Thales TopSky-ATC Thinkorswim Thryv Toast POS TotalEnergies Bio Lubricants TraceGains TraceLink Trimble Construction Trove TurnKey Lender Udemy for Business Unbounce Updox Validic Valmet DNA Automation System Varsity Tutors Veeva CRM Veeva MedTech Veeva Quality Veeva Vault Vendasta Veson Nautical IMOS Platform Viewpoint (by Trimble) Vimeo OTT Virbela Vizient VTS VWO Waste Management Open API by AMCS Waystar Wealthfront Wherefour WindRiver Helix Virtualization Platform WoodCAD|CAM Workday Student Worldpay Wrike Xactly Xerox Paper Recycling XOLV Xtime YCharts Yopto Zendesk Marketplace Zoho Zoho Inventory Zonos Zscaler Web-to-Print by Printful Zuppler

Computing-IBM

Power Enterprise Pool compliance

POWER7 information

Power Enterprise Pool compliance

When you share Mobile Capacity on Demand (CoD) resources among servers in a Power® Enterprise Pool , the pool must be in compliance with your CoD licensing agreements.

The resource entitlements for the pool are procured through your CoD licenses, which include a grace period for overuse of these resources. The resource entitlements for the pool must synchronize with the actual usage of those resources. You can temporarily overuse the Mobile CoD pool resources. However, the grace period in your licenses restricts this overuse. When resources are in use beyond the grace period, those resources are overdue and the server is out of compliance with the CoD license. Compliance policies for the Power Enterprise Pool are based on your CoD licenses and these policies enforce resource availability and usage restrictions for the pool.

The Mobile CoD resource compliance of the servers in the pool determines the compliance state of the pool itself. A server is in compliance if the server does not have any unreturned Mobile CoD resources.

A Power Enterprise Pool can have one of the following four compliance states:

In compliance: None of the servers in the pool have any unreturned Mobile CoD resources.

Approaching out of compliance (within server grace period): At least one server in the pool has Mobile CoD resources that are unreturned, and the server grace period for those resources is unexpired. None of the servers in the pool have Mobile CoD resources that are unreturned and overdue.

Out of compliance (within pool grace period): At least one server in the pool has overdue, unreturned Mobile CoD resources and the pool grace period is unexpired.

Out of compliance: At least one server in the pool has overdue, unreturned Mobile CoD resources and the pool grace period is expired.

A Mobile CoD resource becomes an unreturned resource under the following conditions:

You remove the Mobile CoD resource from a server, but the server cannot reclaim the resource because that resource is still in use. For example, the resource is assigned to one or more partitions. You must remove the partition assignments to enable the server to reclaim the resource.
You remove a Mobile CoD resource from a server that is not connected to the master Hardware Management Console ( HMC ) of the pool.

When Mobile CoD resources that are removed from a server become unreturned, a grace period timer starts for the unreturned resources on that server. There is a separate grace period timer for unreturned Mobile CoD processors and for unreturned Mobile CoD memory on each server.

Before a server grace period expires, you must release the unreturned Mobile CoD resources and make them available for the server to reclaim. If a resource remains unreturned after the end of the grace period, the pool is out of compliance. When the pool moves to the out of compliance state, a new grace period timer starts for the pool itself. There is only one grace period timer for the pool. If any servers have overdue Mobile CoD resources when the pool grace period expires, add operations for Mobile CoD resources are restricted to servers with unreturned Mobile CoD resources. This restriction is enforced until there are no servers in the pool with overdue unreturned Mobile CoD resources.

When a server in a pool is out of compliance, or the pool is out of compliance, console messages are displayed on the HMC s that manage the pool.

To view compliance information for a Power Enterprise Pool , complete the following steps:

From the master HMC for the pool, select Systems Management > Power Enterprise Pools .
In the left navigation pane, select the pool name and then select Compliance Information .

Resolving compliance issues

To avoid compliance issues, ensure that Mobile CoD resources are released on a server before you remove the resources from that server. Also, do not remove Mobile CoD resources from a server that is not connected to the master HMC for the pool.

If you want to overuse your Mobile CoD resources when migrating partitions, ensure that all Mobile CoD resources removed from the source server are released and reclaimed by the source server as soon as the migration completes. If the migration fails, immediately remove the Mobile CoD resources added to the destination system and add them back to the source system.

You can resolve unreturned Mobile CoD resources in any of the following ways:

Migrate a partition to another server. After the partition migrates successfully, any resources that are assigned to the partition on the source server are reclaimed automatically.
Remove resources from a running partition by using the appropriate dynamic logical partition (DLPAR) task.
Remove resources from a shutdown partition.
Delete a partition to release resources that are assigned to that partition.
Activate Capacity Upgrade on Demand (CUoD), On/Off CoD, or Trial CoD resources.
Add Mobile CoD resources to the server.

Note: When a server is powered off, any unreturned Mobile CoD resources are reclaimed automatically by the master HMC for the pool.

If the server is not connected to the master HMC for the pool, you must establish a connection from the master HMC to that server. After you reestablish the connection, if any unreturned Mobile CoD resources remain on the server, take one of the previously stated actions to release them. If you cannot reestablish this connection, you can add Mobile CoD resources to the server to resolve the unreturned resources.

Send feedback Rate this page

Last updated: Thu, April 09, 2015

Using Power Enterprise Pools

POWER7 information

Using Power Enterprise Pools

After you obtain your Power® Enterprise Pool configuration file from IBM, you can create and update the Power Enterprise Pools by using the Hardware Management Console ( HMC ).

Create a Power Enterprise Pool

You can create a Power Enterprise Pool by using the HMC .

Ensure that you meet the following prerequisites for creating a Power Enterprise Pool :

Ensure that the configuration file is in the appropriate location. You must place the file on the local system that you are using to remotely access the HMC . This HMC is the master HMC for the new pool.
Ensure that the HMC manages all the servers that are to participate in the pool.
Ensure that all servers that are to participate in the pool are in the standby or the operating state.
Ensure that all servers that are to participate in the pool use firmware that is version 7.8 or later.

To create a Power Enterprise Pool , from the master HMC select Systems Management > Power Enterprise Pools , then click Create Pool .

Update the configuration of a Power Enterprise Pool

After the Power Enterprise Pool is created, you can update the configuration of your pool. You must contact IBM and get a new configuration file for your pool to make the following types of configuration changes:

You can add Mobile Capacity on Demand (CoD) resources to your pool or you can remove Mobile CoD resources from your pool.
You can add servers to your pool or you can remove servers from your pool.
Attention: The HMC deletes the pool automatically if you remove the last server from a pool.

Ensure that you meet the following prerequisites for updating the configuration of a Power Enterprise Pool :

Ensure that you obtained the required configuration file from IBM.
Ensure that the configuration file is in the appropriate location. You must place the file on the local system that you are using to remotely access the master HMC for the pool.
Ensure that any new server that is to participate in the pool is in the standby state or the operating state.
Ensure that any new server that is to participate in the pool uses firmware that is version 7.8 or later.
Ensure that any server to be removed from the pool is in the standby state or the operating state.
Ensure that any server to be removed from the pool does not have any Mobile CoD resource assignments or any unreturned Mobile CoD resources.

When you update the configuration of a pool, the HMC validates the sequence number in the current configuration file. This sequence number must be greater than, or equal to, the sequence number in the last file that was used to create or update the pool. If the current sequence number does not meet this requirement, the update fails. You must obtain the latest configuration file for the pool and update the pool again.

The latest configuration file for a Power Enterprise Pool is available on the Capacity on Demand (CoD) website .

To update the configuration of a Power Enterprise Pool , complete the following steps:

From the master HMC for the pool, select Systems Management > Power Enterprise Pools .
In the Power Enterprise Pools table, right-click on the pool and then select Update Pool .

Allocate Mobile CoD resources to servers in a Power Enterprise Pool

After you create your Power Enterprise Pool , all Mobile CoD processor resources and Mobile CoD memory resources are allocated to the pool. You must use the HMC to allocate Mobile CoD resources to the servers in the pool. You do not have to notify IBM when you allocate resources.

You can assign Mobile CoD resources to partitions in the same manner as you assign permanent resources to partitions. Mobile CoD resources remain on a server until you remove them from that server. Mobile CoD resources do not expire in the same manner as On/Off CoD resources or Trial CoD resources do.

It is easy to move Mobile CoD resources from one server to another when migrating partitions. You can remove Mobile CoD resources from a server and add them to another server, when the resources are still being used on the server from which they were removed. This action allows the processor and memory resources of the migrating partition to exist both on the source and destination servers, and be used by both the servers at the same time, until the migration is complete.

The following are Mobile CoD resource allocation guidelines:

You can add Mobile CoD resources only to servers with unlicensed resources.
If you remove Mobile CoD resources from a server that the server cannot reclaim because they are still in use, these resources become unreturned resources. A grace period timer then starts for the unreturned Mobile CoD resources on that server. If you do not free the unreturned Mobile CoD resources so that the server can reclaim them before the grace period expires, the pool becomes out of compliance.
If the pool is out of compliance and the grace period timer for the pool is expired, you can add Mobile CoD resources only to servers that have unreturned resources. And, you cannot add more resources than the number of unreturned Mobile CoD resources on that server.
When you add Mobile CoD resources to a server, they are used first to satisfy any unreturned CoD resources on that server.

Mobile CoD resource allocation guidelines for a server that is in No Connection , Pending Authentication , or Failed Authentication state:

You can add Mobile CoD resources only to a server with unreturned Mobile CoD resources. The number of resources that you add cannot exceed the number of unreturned Mobile CoD resources on that server.
You can remove Mobile CoD resources from a server. The Mobile CoD resources that you remove from the server become unreturned and a grace period timer starts for these resources. If you do not reconnect the server to the master HMC before the grace period expires, the pool becomes out of compliance.

Mobile CoD resource allocation guidelines for a server that is in Power Off , Power Off In Progress , Error , or Initializing state:

You cannot add Mobile CoD resources to the server.
You can remove Mobile CoD resources from a server and the resources are reclaimed immediately.

Mobile CoD resource allocation guidelines for a server that is in Incomplete or Recovery state, and the server is powered on:

You can add Mobile CoD resources only to a server with unreturned Mobile CoD resources. The number of processors that you add cannot exceed the number of unreturned Mobile CoD resources on that server.
You can remove Mobile CoD resources from the server.

To allocate Mobile CoD processors to servers in a Power Enterprise Pool , complete the following steps:

From the master HMC for the pool, select Systems Management > Power Enterprise Pools .
In the left navigation pane, select the pool name and then select Processor Resources .

To allocate Mobile CoD memory to servers in a Power Enterprise Pool , complete the following steps:

From the master HMC for the pool, select Systems Management > Power Enterprise Pools .
In the left navigation pane, select the pool name and then select Memory Resources .

Set the master HMC for a Power Enterprise Pool

Each Power Enterprise Pool has a master HMC .

Initially, the HMC that you use to create the pool is set as the master HMC of the pool. It is preferred that you configure a backup master HMC for a pool when you create the pool. The backup master HMC must manage all of the servers in the pool. Configuring a backup master HMC for a pool allows you to easily set the backup master HMC as the new master HMC for the pool if the current master HMC becomes unavailable.

Use the following guidelines for designating a new HMC to be the master HMC for a pool:

Whenever possible, use the current master HMC of a pool to set a new master HMC for the pool. You must use the current HMC to set a new master HMC if the current master HMC is running.
You must use the latest configuration file for the pool to set a new master HMC for the pool when the master HMC is down and one of the following conditions also applies:
- The new master HMC is not configured as the backup master HMC for the pool.
- The new master HMC that is configured as the backup master HMC for the pool does not have valid backup data for the pool.
Whenever possible, ensure that you meet the following prerequisites:
- Ensure that all of the servers that participate in the pool are connected to the new master HMC .
- Ensure that the participating servers are in either the standby state or the operating state.
Set a new master HMC before you perform a clean installation of the current master HMC .

You can view information for a pool from any HMC that manages the pool. You must perform all other pool operations from the master HMC of the pool.

Note: The HMC that you use to manage the pool must have a connection to the master HMC . If it does not, the amount and type of information that you can view might be limited.

To configure a backup master HMC for a pool, complete the following steps:

From the master HMC for the pool, select Systems Management > Power Enterprise Pools .
In the left navigation pane, select the pool name and then select General Pool Properties .

To set a new master HMC for a pool, complete the following steps:

From the current master HMC for the pool, select Systems Management > Power Enterprise Pools .
Tip: If the current master HMC is not available, log on to the HMC you want to set as the new master HMC for the pool.
In the left navigation pane, select the pool name and then select General Pool Properties .

View history logs

The master HMC for a Power Enterprise Pool maintains a history log of the Mobile CoD resource usage in the pool. Other Power Enterprise Pool related events that have occurred are also recorded in this history log.

To view the history log for a pool, complete the following steps:

From the master HMC for the pool, select Systems Management > Power Enterprise Pools .
In the left navigation pane, select the pool name and then select View Pool History Log .

Each server maintains a history log of the CoD events that have occurred on the server. Mobile CoD resource usage and other Power Enterprise Pool related events are recorded in this history log.

To view the history log for a server, complete the following steps:

From an HMC managing the server, select Systems Management > Power Enterprise Pools .
In the left navigation pane, select the pool name and then select Processor Resources .
In the Server Processor Information table, right-click on the server and select View Server History Log .

The history log for a server can also be accessed from the Memory Resources screen.

Send feedback Rate this page

Last updated: Thu, April 09, 2015

Read article

Power Enterprise Pools and the master HMC

POWER7 information

Power Enterprise Pools and the master HMC

A single Hardware Management Console ( HMC ) must be selected as the master HMC for a Power® Enterprise Pool . The HMC that is used to create a Power Enterprise Pool is initially set as the master HMC of that pool. A redundant HMC can be configured as a backup. You can set a new master HMC for a pool at any time.

All Power Enterprise Pool change operations can be performed only by the master HMC for the pool.

When you power on or restart a server, ensure that the server is connected to the master HMC . This action ensures that the required Mobile CoD resources are assigned to the server. When both the server and the master HMC are powered off, restart the master HMC first, then restart the server. This ensures that the server can connect to the HMC to obtain its Mobile CoD resource assignments.

Note: If a restarted server is not able to contact the master HMC , it restarts with no Mobile CoD resources. However, when the master HMC connects to the server the Mobile CoD resources are automatically assigned to the server.

Upgrading the master HMC: You cannot perform any Power Enterprise Pool change operations when you are upgrading the master HMC . After the upgrade is complete, you can resume performing pool change operations on the HMC . If you plan to perform any pool change operations when you are upgrading the master HMC , you must set a new master HMC before you start the upgrade.

Installing the master HMC: Performing a clean installation of the master HMC deletes all Power Enterprise Pool data from the HMC . After installation, the HMC cannot resume master HMC functions for the pool until you perform a recovery operation. To avoid this situation, you can set a new master HMC for the pool before you start the clean installation of the current master HMC .

To perform a recovery operation after a clean installation of the HMC , run the following HMC command in a restricted shell terminal:

chcodpool -o recover -p <pool name> -f <configuration file name>

For more information, run the man chcodpool command in a restricted shell terminal on the HMC to view the online help.

Send feedback Rate this page

Last updated: Thu, April 09, 2015

Read article

Power Enterprise Pool configuration file

POWER7 information

Power Enterprise Pool configuration file

The configuration file is a signed XML file that contains the required information to configure a Power® Enterprise Pool .

Pool ID: The unique ID that IBM® assigns to the Power Enterprise Pool .
Sequence number: A numeric value that increments higher whenever IBM updates the configuration file.
Power Enterprise Pool membership codes: An activation code or a termination code for each system that is a member of the pool.
Mobile CoD processor code: The activation code that sets the total number of Mobile CoD processors that you can use in the pool.
Mobile CoD memory code: The activation code that sets the total amount of Mobile CoD memory that you can use in the pool.

You must contact IBM to get a new configuration file to do the following operations:

Create a Power Enterprise Pool
Add systems to a pool or remove systems from a pool
Add Mobile CoD resources to a pool or remove Mobile CoD resources from a pool

You must have the latest configuration file for a pool to do the following operations:

Recover the master Hardware Management Console ( HMC ) for a pool after a clean installation of the master HMC .
Set a new master HMC for a pool.
Note: You do not always need the configuration file to set the master HMC . For more information, see the Power Enterprise Pools and the master HMC.

The latest configuration file for a Power Enterprise Pool is available on the Capacity on Demand (CoD) website

Add or remove systems from Power Enterprise Pools

Adding or removing a system from an established Power Enterprise Pool requires notification to IBM.

An updated addendum must be submitted to the Power Systems™ CoD project office (pcod@us.ibm.com) to add or remove systems from Power Enterprise Pool . When the update is processed, a new pool configuration file is posted on the CoD website.

Before you remove the systems from a pool, all assets (including Mobile CoD resources) that were originally purchased with the system must be returned to that same system serial number. Mobile assets that belong to a system might qualify for transfer to another system serial number depending on normal qualifying guidelines and, if possible, require more administrative action.

Systems that are removed from a pool can join another pool and contribute Mobile CoD resources to the new pool and use Mobile CoD resources of other systems. Mobile CoD resources require a pool ID to be recognized.

Eligible program authorizations

As a result of authorized participation in a Power Enterprise Pools offering, you are authorized to temporarily transfer entitlements for authorized use of each Eligible Program from a Power Systems server that is participating in the pool to another Power Systems server that is also participating in the pool. You must not exceed the maximum number of software licenses within the pool for any specific software agreement.

Required maintenance service and support

Within each Power Enterprise Pool , all participating systems must either be serviced by IBM under warranty or an IBM maintenance service agreement, or not be serviced by IBM. In addition, each eligible program that is entitled for IBM software maintenance (SWMA) on one or more systems that are participating in the pool must also have a valid SWMA agreement on every participating system in the pool that eligible program will execute on.

Additional Power Enterprise Pool requirements

The following are the additional Power Enterprise Pool requirements:

Any licenses for Power software like AIX® , IBM i , and other Power software, that exist on any system in a pool must also be licensed for at least one core on each of the additional systems in the pool.
All systems in a pool must be owned by the same customer enterprise number.
Activations cannot be transferred, moved, or otherwise reassigned across country boundaries.
Integrated Facility for Linux activations are not supported as mobile activations within Power Enterprise Pools but can reside separately on systems within a pool. AIX , IBM i , and Linux operating systems and their workloads are all supported by Power Enterprise Pools .

Send feedback Rate this page

Last updated: Thu, April 09, 2015

Read article