Test 974: Power Systems Technical Support for i

Computing Needs Analysis (13%)

1. Collect information to evaluate the current computing environment, including Performance Data, National Language support, Operating Systems (for example, i5/OS, AIX, Linux), Platforms (for example iSCSI and Blade), HA/DR, SAN vs. Internal, and Tape.
2. Analyze customer requirements for system performance and availability (for example, response times, batch performance, I/O performance, disk protection, and downtime tolerance).
3. Determine the customer's system network connectivity requirements, including Enterprise Extenders.
4. Evaluate compatibility of application software for the targeted hardware and its requisite operating system (including guest operating systems and applications).
5. Determine user application and system management requirements, based on factors including (but not limited to) 5250 Enterprise Enablement, DB2 Web Query, System i Access, System i Access for Web, IBM Licensed Program Products and IBM Systems Director.
6. Determine the requirements for software on IBM i (including Java, WebSphere, Domino, Sametime, Quickr, PHP, capacity, performance, clustering, and availability).

Determine backup requirements, considerations, and strategies for all operating environments.

Relate Power Systems and IBM i technologies to Customer Needs (34%)

1. Describe features, functions and benefits of Power Systems hardware (for example, smart IOA, POWER5+, POWER6, auxiliary write cache, SCSI, SAS, Fibre, Integrated Virtual Ethernet (IVE) and Virtual I/O Server (VIOS)).
2. Describe features, functions and benefits of system management tools such as Management Central, and IBM Systems Director.
3. Describe features, functions and benefits of client accessibility tools such as System i Access, NetServer, DB2 Web Query, System i Access for Web, WDSc, and ODBC.
4. Explain i5/OS network security considerations (intrusion detection, encryption, firewall capabilities, VPN, EIM, SSL, etc.).
5. Explain the use and benefits of HA/DR management tools available, such as Backup Recovery Media Services, Virtual tape, Job Scheduler, iCluster and HA Solutions Manager (HASM).
6. Describe how i5/OS meets customers' needs for high availability and resiliency (for example, disk protection options such as RAID5/6 and mirroring, hot spare, SAN, redundant power supplies, and UPS).
7. Determine how hardware virtualization (LPAR) meets a customer's needs. Describe LPAR benefits including switched I/O, capped and uncapped processor resource allocation, hosted hardware resources, etc.
8. Explain virtualization as it relates to hosting i5/OS, Microsoft Windows Server, AIX, and Linux on Power Hardware (including iSCSI).
9. Compare and contrast console options (HMC, LAN) and when each is appropriate.
10. Compare and contrast Internal disk vs External (SAN) and determine which is appropriate.
11. Explain differences between current and previous System i servers, such as capped and uncapped processor capabilities, cache, HSL/RIO/12X capabilities, card and disk technologies, and CPW.
12. Describe rack options and design considerations (including space, placement, power, and cooling).
13. Describe the upgrade options from previous System i models.
14. Describe the differences among packages and editions and the relative benefits of each.
15. Identify software licensing issues (including i5/OS, LPPs, and IBM software products) with LPAR requirements, including capped/uncapped and pooled processor implications.
16. Describe HMC and DST security.

Solution Design (24%)

1. Determine which existing components are usable when designing a new solution.
2. Match customer storage requirements to the newly designed system (consider disk, independent ASPs, clustering, SAN, virtual and physical tape, iSCSI, network, growth and requirements for partitioning).
3. Given customer I/O requirements, apply card type and placement, IOP and IOA requirements and constraints to existing and new hardware in the customer environment. Consider available card slot types (PCI-X DDR, PCIe) and the impact on partitioning.
4. Employ current performance data gathering and analysis tools to determine proper CPW configuration, including memory, CBU, on-demand processors and on-demand memory. Consider memory placement (slot availability and performance).
5. Apply the SPT. Describe its uses, and consider interaction with HMC, import/deploy/export, eConfig, and implementation (round-tripping).
6. Apply shared and dedicated processor rules including the use of capped and uncapped processors, processor pools, and the use of Virtual Processors.
7. Determine required console and control panel features, placement, and potential networking considerations (for example, HMC, LAN Console, ASMI).
8. Determine resources necessary to implement the customer's backup and recovery policies. Consider performance, maintenance windows, BRMS, software and hardware encryption, virtual tape and resource switchability (VIOS, FlashCopy, XSM, HASM, iCluster,Global- and Metro-Mirror, etc.).
9. Determine resources necessary to implement networking, including system and network bandwidth, LAN/WAN, protocols, Virtual Ethernet, redundancy, etc.

Implementation Planning (11%)

1. Determine the physical planning requirements, including floor space, placement in racks, power requirements, rack configuration, cabling, and network port/drop requirements.
2. Determine appropriate migration methodology, considering data, device interoperability between systems, supported OS and application software, LPAR migration, and card and system availability requirements during migration. Include considerations for media used on both source and target systems.
3. Plan the system software installation and configuration. Consider LPAR, guest Operating Systems and time required to install.
4. Validate communications requirements. Consider multiple systems on the network, Virtual IP Addressing (VIPA), physical port requirements, host names, Line descriptions, etc.

Solution Implementation (18%)

1. Configure disk storage units. Consider Independent ASPs and clustering, RAID, mirroring, system and user ASP management, and hot spare.
2. Configure attachment to external system devices (for example, SAN, iSCSI, Intelligent PDUs, tape libraries, SAN fabric). Consider card type, bus type and performance.
3. Implement the available Ethernet adapters (10/100, Gigabit, 10 Gigabit, Host Ethernet Adapter), both physical cards and virtual adapters. Consider link speed, frame size, duplex and security.
4. Create or migrate an LPAR configuration. Relate card type and placement (IOP/IOA), and rack or drawer requirements and constraints to existing and new hardware in the customer environment. Deploy the System Plan. Consider technical characteristics of primary/secondary partitions and older hardware.
5. Apply shared and dedicated processor rules. Include capped, uncapped, dedicated, and processor pool groups.
6. Configure support for guest operating systems and partitions. Use appropriate tools. Apply rules for tape, virtual resource allocation, and kernel support.
7. Configure and implement the console and migrate from other console types as required (for example, HMC, redundant HMC, Operations, LAN console). Consider remote browser access, security, and support.
8. Install and configure i5/OS and related IBM licensed program products (for example, license keys, feature codes, cryptographic support, cumulative/group fix packages, system firmware, and SLIC refreshes). Consider mixed release level implications for an LPAR environment.