Migration and Upgade The next generation iseries...simplicity in an on demand world

Transcription

1 IBM eserverj iseriesj Migration and Upgade The next generation iseries......simplicity in an on demand world January, May 2003

2 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration (subset) I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

3 Notes: Agenda This foil lists the major grouping of topics in this presentation. This page is repeated at the beginning of each main topic. The System Handbook GA and the January iseries On Demand hardware announcement letters contain a complete set of supported from and to migration/upgrade features. You can also find additional information through the official iseries migration web site at See also the References foil in the References and Summary section of this presentation.

4 Upgrade or Migrate? Recent vintage hardware more likely to be eligible for upgrade Example: PCI I/O Tower devices to PCI -X I/O Tower V5R2 not supported on older hardware - requires migration Example: 4xx and 5xx processor family Consider migration if: Converting to new HSL PCI-X I/O Server Consolidation - partitioning Short maintenance windows for upgrades Upgrades include upgrade to an Edition package Interactive capacity requirements - know what you will need Capacity on demand (permanent and/or temporary) Solution Assurance may be required in many cases (e.g. pre-planning pre-sales i870, i890, moving to HSL,...)

5 Notes: Upgrade or Migrate? One of the decisive factors for selecting an upgrade (retain machine serial number) of an existing system or replacing the hardware will be based on the number of components that can be reused on the new system. Features, such as SPD towers, migration towers and SPD IOAs are not supported on the new hardware; other components, such as slower disk or tape drives, might be replaced since they are not delivering the performance or usability features one is looking for. Remember also that any 4xx and 5xx systems do not support V5R2, so a side-by-side migration will be required. Another criteria that will decide whether or not to select a straightforward upgrade will be the maximum allowable downtime the service delivery can tolerate. Also, a simple box upgrade will take considerably less time than if you need, at the same time, change the RAID5 implementation by introducing the new RAID5 controllers, or have to replace all expansion towers with new expansion towers. Remember also that upgrading from an LPAR environment will take more time to bring up the system again, especially when adding or changing the configuration drastically. This announcement introduces a line of products that greatly expand configurations able to accept consolidation and enable a very useful way to dynamically adjust server and partitioning resources (i.e. processors) than before; the enhanced support, offered by V5R2, for hosting Linux, Windows and UNIX applications allows using a single footprint for a variety of workloads. Combined with the excellent management tools provided by tools such as iseries Navigator, an offering for a consolidated server becomes a very attractive proposition to deliver outstanding levels of service delivery. With the new systems (i810, i825, i870, i890 (#2497/#2498), the notion of different interactive capacity cards has disappeared. This means that instead you need to validate whether or not the server can run with either OLTP capacity, such as offered by the Standard Edition, or with the full processor CPW 5250 OLTP capacity, as included in the Enterprise Edition. Finally, the upgrade or migration choice for such a hardware change will be influenced by the budget. In some occasions, especially when the original system has older components, you also need to consider the recurring costs for manpower (e.g. the attended time needed for handling backup volumes will be shorter if the backup/restore medium is automated or faster than the new one), maintenance, floorspace, power and cooling to complete this picture. Please also to the Planning chart later in this presentation for more details on the outline of an upgrade or migration process. Note, the February System Handbook, GA , contains detailed charts for older system processor feature to new system processor features and recommended I/O IOP, controller (IOA), and device replacement when not supported n the target server. We have much of this information in this presentation but it is not complete. Also, consider the February 2003 edition of the IBM eserver iseries Migration and Upgrades at V5R1 and V5R2, SG for more update and migration scenarios and considerations than can be covered in this presentation.

6 Server and I/O Tower Upgrades, Migration at a Glance $xxxx 6 disk slots 7 PCI slots 5074 $xxxx up to 45 disk slots 14 PCI slots FC 5079 = 2 x 5074 in rack 5078 $xxxx 14 PCI slots FC 0578 in rack PCI-X & 15k rpm disk support* $xxxx 12 disk slots 7 PCI-X slots 0595 rack mount 5094 $xxxx up to 45 disk slots 14 PCI-X slots FC 5294 = 2 x 5094 in rack 5088 $xxxx 14 PCI-X slots FC 0588 in rack * 507x towers cannot be migrated to 509x, 5088 towers References: IBM eserver iseries Server Migration: System Migration and Upgrades at V5R1 and V5R2, SG Installation and physical planning at ITSO Redbooks Redpaper - IBM eserver iseries Supported Upgrades, REDP0322, available February 24, 2003, to be updated May 2003

7 Notes: Server and I/O Tower Upgrades at a Glance This foil shows graphics from the Marketing Product Positioning presentation for server to server upgrades and disk I/O tower to disk I/O tower upgrades. The bold lines between an older and upgraded to / migrated to system indicates the primary "to system." The disks and the PCI cards need to be accommodated in a 5074 or a 5094 based on their compatibility. Some of the expansion units can be converted to work with the new models. However detailed planning needs to be done before beginning the expansion unit conversion if you are upgrading a partitioned server. Review other documentation on hardware migration detail. For example, the following current I/O tower disk drives can be moved: 7.2K rpm #4308 (4 GB) 7.2K rpm #4314 (8.5 GB) 7.2K rpm #4324 (17.5 GB) All 10K rpm disks iseries has spent extensive hours testing upgrade and migration testing of upgrades to minimize the impact to "hours of operation" required to run a business. Note that many other vendors do not yet have the extensive capacities to support upgrades the way the iseries does. Upgrades are defined as moving to the new server from an existing server and retaining the existing system's serial number. Migration is used to mean actually "moving" current hardware to the new system, independent of retaining the serial number. Notes: Additional iseries presentations and other marketing materials can be found on the IBM Systems Sales Web site at: w3.ibm.com/sales/systems/iseries/ There is also a Migration redbook being updated: IBM eserver iseries Server Migration: System Migration and Upgrades at V5R1 and V5R2, SG (red draft Feb 2003) See the Hardware presentation in the May 2003 Announcements Technical Overview set of presentations The following ITSO Redpaper is intended to be a summary of supported upgrades/migrations that can be updated as necessary - IBM eserver iseries Supported Upgrades, REDP0322, update planned for May 15, 2003

8 Your flexible friend - iseries upgrades 820, 830, 840 to 810, 825, 870, 890 are plug and go upgrades - Roll-in new server Physically move disk or migrate load source Plug cables and IPL Could use new tower (507X or 509X) as migration tower 7xx to new 810, 825, 870, 890 No SPD or Migration towers Could use PCI tower + conversion (5065 to 5074) as migration tower Use load source migration to save a reload Must do thorough preparation Load new release and test Plan, Plan... review, compare new versus current HSL, IOPs, IOAs, etc.. Must maintain RAID sets if moving disks

9 Notes: our flexible friend - iseries upgrades The key points regarding upgrades to the new i810, i825, i870, i890 are: Easy to Upgrade in iseries Upgrades throughout the product range Many simple tasks can create a complex environment First we will discuss 8xx to 8xx upgrade. This from existing 8xx models to new models available with this announcement. Typically these are simple plug and go upgrades, meaning that provided the prerequisite active has occurred, we should be able to disconnect the existing system and reconnect the new system. The process for this upgrade is as follows: The preliminary upgrade tasks have been carried out We can roll-in the new upgrade. Unpack the system and any additional I/O hardware.. The existing system is powered down, and any disk and I/O are removed from the system unit The I/O is relocated into the new system unit and the external I/O is reattached. The system is then IPL'ed to DST. Any resource issues are fixed and the system is brought online. This is a very simplified version of what really happens. If the customer does not want to physically move their disks and I/O. Then you could choose to use a new or existing tower as a 'migration tower'. Moving all user data and the load source from the system unit to an expansion tower. Similar to the SPD migration tower. The other key upgrade is from 7xx to new 8xx. There are two types of this upgrade available. From 7xx to existing 820, 830, 840 and from 7xx to i810, i825, i870 and i890. We will not cover the former method here, but we will later. If you are planning to move from 7xx to servers available with this announcement and the 890 you cannot have any SPD based hardware or migration towers on the system. They must be removed before or as part of the upgrade. To save time during the upgrade you could plan to move the existing I/O and data to an SPD/PCI tower (5065/5066). Again this could be used as a migration tower. The load source and user data are migrated from the existing SPD hardware and the system unit into the SPD/PCI tower. This tower is then converted as part of the upgrade and attached to the new system. The load source is recovered and new I/O added and the system could be up and running. To perform successful upgrades you must do preparation. You must load the new release and test. You should also Plan, Plan... Especially for HSL and any new IOPs, IOAs, etc.. This is important for the preservation of existing RAID sets if moving disks.

10 New Model considerations

11 Model considerations Model 890 (i890) Existing 890s (0197/0198 base, 2487/2488 standard) available until May 2003 Model 870 (i870) Same as 890 with less in it... has #0126 reduction feature (same as i890) Model 825 (i825) 5 disks per Expansion tray Note for upgrade from Model 820 has 6 per tray Model 810 (i810) HSL not HSL-2 Model 800 (iseries 800) Upgrade from 800 (300) to 800 (950 CPW) Do not get additional Twinax, memory and disk WebSphere express not required HSL not HSL-2

12 Notes: Model considerations This foil summarizes the new models - from an upgrade viewpoint. The existing feature code Model 890s will be available until 2Q03. These model will retain the existing Permanent Capacity Upgrade on Demand capabilities - up to 14 days of temporary activation and permanent processor upgrade - by number of processors. There is no "number of processor days" temporary activation as there is on the new January 2003 models.. The new Model 870 is basically the same as 890, but with less processors and associated hardware inside. The Model 870 has the #0126 reduction feature available, this is the same as the current and new Model 890 height reduction feature. The Model 825 offers 5 disks per Expansion tray with a a total of 15 disks in the base system unit. The can give a potential problems to upgrades from Model 820. The model 820 has 6 disks per disk can, making a total possible of 18 disks. This can cause the following potential upgrade issues. If we were to upgrade a Model 820 with 6 disks and there was no plan to increase the base. The order would contain an extra 5108 feature solely for one disk unit. If the customer has ordered additional expansion towers there may be alternatives to the If the disks in the expansion were the same size as the Model 820 the 6th disk could possibly be relocated there (provided it could be removed from the system unit before the upgrade). If the disk is a different size the customer might wish to remove the disk and leave it out of the new configuration. If you understand the current 270 model structure the Model 810 is very similar. It does not have HSL-2 ports, the ports are HSL. This means the cables from a Model 270 will be supported. The model 810 does support a mixture of PCI and PCI-X expansion towers. So there could still be the need for HSL to HSL-2 conversion cables. The Model 800 (typically referred to as the iseries 800) is the "baby" of the new servers. But it is a "big baby" as it is 15 times as powerful as the older B70 and could fit in one 9332 disk draw!!! When upgrading the model 800 within its range from the Value to Enterprise, you do not get all the features you would if you had brought the Enterprise Edition in the first place. You will not get the Twinax card and the additional memory and disk. WebSphere express is also not required. Again as with the Model 810, the Model 800 is HSL not HSL-2.

13 General server considerations General HSL- HSL-2 cables (conversion) on 8i25, i870, i890 RAID to RAID 35GB vs. 70 GB drives Buy Enterprise Edition upfront - less expensive than upgrade No IXS on Standard to Enterprise upgrade Must load V5R2 (Feb 2003 level) and PTFs to support new hardware before upgrade

14 Notes: General server considerations This chart out lines the considerations that can apply across the whole server range. Key Points: HSL and the need for planning Need to examine current application environment - Standard (limited 5250 OLTP CPW) or Enterprise (full 5250 OLTP CPW and suite of software products) before making a decision. The term "5250 OLTP" (On Line Transaction Processing) is being introduced to distinguish applications doing 5250 I/O operations from the more generic term - "interactive" used in the past. The Performance presentation contains more details on this subject, and the System Handbook does as well. You should be loading V5R2 (Feb 2003 level) whether you are upgrading or not. However, when upgrading, you need to ensure you have the right level of V5R2 software to run the new hardware. We discuss this later in the personation. In general the HSL rule are not complex, provided you do read them! We have made it very easy to move I/O from existing HSL based system to the new models by employing a HSL to HSL-2 conversion cable. This cable can be used both ways round. From an existing model to a new tower or from an existing tower to a new model. With the new #2757 PCI-X Disk Controller comes a new implementation of RAID-5. When you move you RAID sets from an existing adapter to a new RAID adapter. The existing RAID structure will be removed and the new structure will be created. The new I/O structure and the new 70 GB 15K RPM drives offer 35GB 15K RPM performance with twice the capacity. There is more information about this in the Technical Overview Performance presentation. We suggest that the customers think about the Edition they are buying. It may be less expensive to buy the Standard Edition, but if you find you need to upgrade to Enterprise later, this is more expensive than the initial Enterprise Edition. There may be features not available with the Edition upgrade. For example, there is no IXS on a Standard to Enterprise Edition upgrade on the iseries 800, i810, but the i825, i870, i890 Enterprise Edition does include one 1.6 GHz IXS with 1 GB of memory. As the newly announce products and features all require V5R2 (Feb 2003 level) we suggest customer get this new code and start test an implementation now rather than just before any potential upgrade. A foil later in this presentation describes how to get the correct V5R2 software updates when upgrading to a new server or adding the new I/O to an existing 270, 820, 830, 840, and 890. Also. after the information on system to system upgrades, the topics of I/O feature migration and HSL versus HSL-2 are covered.

15 Existing Models still available Earlier models supported by V5R2 includes: 6xx, Sxx, 7xx, 170, 150, 250, 270, 820, 830, 840 Earlier models which can still be ordered from IBM as "new boxes" 250, 270, 820, 830, 840 Earlier models which can be upgraded to newest models 7xx, 270, 820, 830, 840 (7xx upgrades available until October 8, 2003)

16 Notes: Existing Models still available This shows emphasizes that the existing Models are still available. Earlier models supported by V5R2 includes 6xx, Sxx, 7xx, 170, 150, 250, 270, 820, 830, 840 Earlier models which can still be ordered from IBM as "new boxes" include: 250, 270, 820, 830, 840 Earlier models which can be upgraded to the newest models: 7xx (7xx upgrades available until October 8, 2003) 270 (upgrade from/to only specific models) 820, 830, 840

17 Upgrade Paths Summary 270 i800 i810 i825 i870 i890 x (#2469/7430) 720 x x 730 x x 740 x x x i820 x x x i830 x x x i840 x x i800 i810 x i825 x x x i870 x x i890 x

18 Notes: Upgrade Paths Summary This is a simple table showing which servers can upgrade into the new January 2003 systems. Note, the single 270 upgrade into the model 810 is from a (processor CPW 2350) with Interactive Feature #1520 (70 CPW) to the with the Enterprise Edition - feature #7430). As stated earlier, for more detailed upgrade combinations, see: w3.ibm.com/sales/systems/iseries/ There is also a Migration redbook being updated: IBM eserver iseries Server Migration: System Migration and Upgrades at V5R1 and V5R2, SG (red draft Feb 2003) See the Hardware presentation in the May 2003 Announcements Technical Overview set of presentations The following ITSO Redpaper is intended to be a summary of supported upgrades/migrations that can be updated as necessary - IBM eserver iseries Supported Upgrades, REDP0322, update planned for May 15, 2003 The next foils provide a look at the new upgrade possibilities available with the May 2003 announcement.

19 May 2003: Additional Upgrade Paths Increase Flexibility Lower price upgrades to entry to new 810 entry 820 entry to new 810 entry Simpler, direct upgrades to 825 from 720, 730 and 820 New 810 up through larger 810s

20 720, 730, 740 to 810, 825, 870, 890 One-step Hardware MES Upgrade Paths F R O M TO Model Proc * 2061 x x x x 2062 x x x x x 2063 x x x x 2064 x x 730 * 2065 x x x x 2066 x x x 2067 x x x 2068 x x = new May * 2069 x x x 2070 x x x x * 720, 730, 740 upgrades orderable only through October 7, 2003

21 820, 830 to 810, 825, 870, 890 One-step Hardware MES Upgrade Paths F R O M TO = new May 2003 Model Proc x x x x x 2396 x x x 2397 x x x 2398 x x 2435 x x x x x 2436 x x x 2437 x x x 2438 x x 830* 2400 x 2402 x x x 2403 x x x 2349 x x x x 0153 x x *Note: all 830 processors of 4/8-way must be activated before upgrade

22 800, 810, 825, 870, 890 One-step Hardware MES Upgrade Paths F R O M Model Proc x x x x 2466 x x 2467 x 2469 TO = new May x x x x 2498

23 New Structure: Simplification, all on one single table MODEL N-WAY SERVER FEATURE SW GROUP PROCESSOR FEATURE CPW STANDARD EDITION FEATURE* 800 EDITION FEATURE* 5250 CPW ENTERPRISE EDITION FEATURE* CUoD ACTIVATION FEATURE TEMPORARY ENABLEMENT FEATURE TEMPORARY BILLING FEATURE: Standard / Enterprise On/Off PREPAID FEATURE Standard / Enterprise ** i i i i i810 2 i810 1 i810 1 i810** ** 05/ P P P P P P P P P P P / / / / N/A / / N/A / / N/A / / N/A / / N/A 7430 N/A N/A N/A N/A 7410 N/A 7412 N/A N/A N/A N/A 7407 N/A 7409 N/A N/A N/A N/A 7404 N/A 7406 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A * The Edition feature number appears in system value QPRCFEAT and DSHPDWRSC TYPE(*AHW) CEC Processor feature code

24 Notes: Simplification, all on one single table This single table shown here contains the complete overview of the new family of iseries severs with the different feature codes and some of the most important specific properties of the different server features that come available with this announcement. Note: The Edition feature number appears in system value QPRCFEAT and DSHPDWRSC TYPE(*AHW) CEC "Processor feature code" parameter. This value is also shown for the CAPACITY CARD CCIN value when performing temporary Capacity Upgrade on Demand through the Service Tools interface. The system value QPRCFEAT may be used by software products using software tier licensing. Announced May, 2003 A set of 30 Processor Days prepaid Temporary Capacity on Demand (TCoD) features were announced May, 2003 for the 825, 870, and 890 models. - On/Off Prepaid for Model 825, for Model 870, and Model 890 features. Upon purchase of this prepaid feature, the customer's TCoD account will be credited for 30 processor days for each feature ordered. A customer's system must be enabled for On/Off Capacity on Demand before ordering one of these features. Availability of these prepaid features is May 23, econfig support is to be June 9, 2003.

25 Basic Question: Doing any 5250 OLTP work? If you plan on doing "zero" 5250 OLTP work, select Standard Edition Limited single 5250 Administrative job supported Multiple 5250 jobs will quickly exceed this capacity If you plan on doing any "multiple jobs" 5250 OLTP work, select Enterprise Edition Plan ahead. Starting with Standard Edition and later upgrading to Enterprise Edition will be significant additional cost

26 Notes: Basic Question: Doing any 5250 OLTP work? The term 5250 OLTP is introduced with the January 2003 announcements. This describes the same work that has been included in the term "interactive" in previous releases. It simply means are you doing 'production work" with jobs doing 5250 display or printer I/O operations. On the i810, i825, i870, and i890 systems the Standard Edition essentially is the same as the previous 270, 820, 830, 840, and 890 BASE feature systems. That is, the base system and the Standard Edition will permit a single 5250 job to take a reasonable amount of TOTAL SYSTEM CPU UTILIZATION for administrative purposes. However, if multiple 5250 I/O jobs are active they are quickly prohibited from consuming very much CPU utilization. If you are on an Enterprise Edition, you simply manage 5250 work along with other work as you did/do on systems where the Interactive CPW rating was/is equivalent to the Processor CPW rating - job priorities with the RUNPTY job parameter. The following snapshot of all system processor CPW-based upgrade/migration features shown only include target systems when 5250 OLTP work is being done - the Enterprise Edition.

27 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration (subset) I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

28 Notes: System to System Upgrade Examples This separator page begins a series of tables showing most, but not all of the supported system to system upgrades. We show only the target Enterprise Editions supporting more than a single 5250 administrative job. That is, you are doing full 5250 OLTP applications. If you are satisfied to use a single 5250 administrative job, you can upgrade to the corresponding Standard Edition. The System Handbook, GA , and the January 20, 2003 iseries On Demand hardware announcement letters contain a complete set of supported from and to migration/upgrade features. The following ITSO Redbooks document should be considered the official source for valid upgrade/migration system features list: IBM eserver iseries Supported Upgrades, REDP0322, planned availability February 24, 2003

29 Upgrade: i270 to i810 (assuming 5250 OLTP) From Processor From Interactive To Processor To Edition

30 Notes: Upgrade: i270 to i810 (assuming 5250 OLTP) In this and the following supported sets of system to system migration tables we only show the cases where 5250 OLTP applications will be run on the target system. Therefore, until further notification, only Enterprise Editions are listed. If 5250 OLTP work is not planned, then the target could be a supported Standard Edition package - except: for this 270 to 810 upgrade which requires a 270 with Interactive feature #1520 to upgrade only to an 810 with the Enterprise Edition package which has full 5250 capacity any exception noted in IBM eserver iseries Supported Upgrades, REDP0322, planned availability February 24, 2003

31 Upgrade Details: i270 to i810 Doing any 5250 OLTP work? Processor and Backplane are replaced #7104 System Unit Expansion needs conversion to #7116 #7123 DASD Expansion Unit needs conversion to #7136 Memory cards migrate CD-ROM/DVD/Tape/IOPs/IOAs/Disk units in i270 and Expansion Towers migrate #9767 base non-raid disk controller cannot be used in i810 Replace with Ultra SCSI Disk Controller / Tape Adapter #5705 (no RAID) Move up to 2778/4778, 2782, or 2757 (all RAID capable) New covers - order #0133 conversion feature if i270 is in a rack (#0551) Optional #7002 HSL Enabler is no longer required since i810 comes standard with HSL port enabled

32 Notes: Upgrade Details: i270 to i810 The i270 is the only product in the existing product range, with the exception of the i890, that allows an upgrade where parts are replaced, making it an attractive box for upgrades. Remember also that such an upgrade of an i270 to an i810 lifts the limitation of DASD space for this type of footprints - but does require enablement of 5250 CPW capacity. When you are considering an upgrade of an i270 to an i810, you might want to take advantage of other significant technology changes at the same moment, such as the introduction of new disk controllers (the #2757) and/or new disk units, running at higher rotational speeds, to lift a possibly existing bottleneck of I/O throughput. Such an upgrade can easily be achieved on i270 upgrades. If you are upgrading an existing i270 to an i810, and the base system has up to 6 disk units connected to a #9767 disk controller and uses mirrored protection, you need to replace this disk controller, since it is not supported on the i810. For that purpose, you may choose a #5705 disk controller if you want to maintain this level of protection on the disk units. If your upgrade plan includes to add disk units and to replace mirrored protection with RAID protection, you can order either a #2757, a #2782, or a #4778 as a replacement for the returned #9767. During your migration process and once you have replaced the #9767 with one of the controllers from the above list, you will have to stop mirroring, start RAID5 protection, add the disks which made up the mirrored pair to the system - eventually together with the addition of any newly ordered disks -, and finally balance the disks for capacity. Remember that an i270 supports, besides the #9767, only the #2763, #4748 and #4778 disk controllers, so if you are planning to install one of the newly announced disk controllers, you will have to wait to perform this procedure after the upgrade to the i810 target configuration.

33 Upgrade: Model 720 to i810 (assuming 5250 OLTP) From Processor From Interactive To Processor To Edition Any Any

34 Upgrade Details: Model 720 to i810 Doing any 5250 work? All upgrades are Roll-in / Roll-out Memory: All new memory cards required Base memory returned to IBM Feature memory property of customer Feature CD-ROM/Tape migrate IOPs/IOAs/DASD that can migrate: See System Handbook, GA

35 Upgrade Paths: Model 720 to i825 (assuming 5250 OLTP) From Processor From Interactive To Processor To Edition Any

36 Upgrade Details: Model 720 to i825 Doing any 5250 OLTP work? All upgrades are Roll-in / Roll-out Memory: All new memory cards required Base memory returned to IBM Feature memory property of customer No expansion towers migrate Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i825 System Unit need to be converted to #46xx i825 requires DVD IOPs/IOAs/DASD that can migrate: See System Handbook, GA

37 Upgrade Path: Model 730 to i825 (assuming 5250 OLTP) From Processor From Interactive To Processor To Edition Any

38 Upgrade Paths: Model 740 to i825 (assuming 5250 OLTP) Model 740 From Processor From Interactive To Processor To Edition Any

39 Upgrade Details: Model 730 / 740 to i825 Doing any 5250 work? All upgrades are Roll-in / Roll-out Memory: All new memory cards required Base memory returned to IBM Feature memory property of customer No expansion towers migrate Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i825 System Unit need to be converted to #46xx i825 requires DVD IOPs/IOAs/DASD that can migrate: See System Handbook, GA

40 Upgrade Paths: Model 730 to i870 (assuming 5250 OLTP) From Processor From Interactive i870 To Processor To Edition Any

41 Upgrade Paths: Model 740 to i870 (assuming 5250 OLTP) Model 740 From Processor From Interactive i870 To Processor To Edition Any

42 Upgrade Paths: Model 740 to i890 (assuming 5250 OLTP) Model 740 From Processor From Interactive i890 To Processor To Edition Any Any

43 Upgrade Details: Model 730 / 740 to i870 / i890 Doing any 5250 OLTP work? All upgrades are Roll-in / Roll-out Memory: All new memory cards required Base memory returned to IBM Feature memory property of customer No expansion towers migrate Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i825 System Unit need to be converted to #46xx i825 requires DVD IOPs/IOAs/DASD that can migrate: See System Handbook, GA

44 Upgrade Paths: i820 to i810 (assuming 5250 OLTP) From Processor From Interactive To Processor To Edition 2435 Any Any Any

45 Upgrade Details: i820 to i810 Doing any 5250 OLTP? All upgrades are Roll-in / Roll-out Memory: All new memory cards required All HSL expansion towers migrate (i810 has a maximum of 4 towers) Migration towers and any connected SPD towers cannot be used on i810 Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate No feature conversions required IOPs/IOAs/DASD that can migrate: #9767 cannot be used in i810 Replace with Ultra SCSI Disk Controller / Tape Adapter #5705 (no RAID) Move up to 2778/4778, 2782, or 2757 (all RAID capable) See System Handbook, GA

46 Upgrade Paths: i820 to i825 (assuming 5250 OLTP) From Processor From Interactive To Processor To Edition Any Any

47 Upgrade Details: i820 to i825 Any 5250 OLTP work? All upgrades are Roll-in / Roll-out Memory: All new memory cards required All HSL expansion towers migrate Migration towers and any connected SPD towers cannot be used on i825 Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i825 System Unit need to be converted to #46xx i825 requires DVD IOPs/IOAs/DASD that can migrate: see below #9767 cannot be used in i825 Replace with Ultra SCSI Disk Controller / Tape Adapter #5705 (no RAID) Move up to 2778/4778, 2782, or 2757 (all RAID capable) See System Handbook, GA

48 Upgrade Paths: i820 to i870 (assuming 5250 OLTP) From Processor From Interactive To Processor To Edition Any

49 Upgrade Details: i820 to i870 Doing any 5250 OLTP work? All upgrades are Roll-in / Roll-out Memory: All new memory cards required All HSL expansion towers migrate #5075 is not supported on i870, but can be converted to #5074 Migration towers and any connected SPD towers cannot be used on i825 Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i870 System Unit need to be converted to #46xx i870 requires DVD IOPs/IOAs/DASD that can migrate: #9767 cannot be used in i870 Replace with Ultra SCSI Disk Controller / Tape Adapter #5705 (no RAID) Move up to 2778/4778, 2782, or 2757 (all RAID capable) See System Handbook, GA

50 Upgrade Paths: i830 to i825 (assuming 5250 OLTP) From Processor From Interactive To Processor To Edition 2400, 2402 Any

51 Upgrade Details: i830 to i825 Doing any 5250 OLTP? All upgrades are Roll-in / Roll-out Memory: All new memory cards required All HSL expansion towers migrate Migration towers and any connected SPD towers cannot be used on i825 Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i825 System Unit need to be converted to #46xx i825 requires DVD IOPs/IOAs/DASD that can migrate: See System Handbook, GA

52 Upgrade Paths: i830 to i870 (assuming 5250 OLTP) From Processor 2400, 2402, 2439 From Interactive To Processor To Edition

53 Upgrade Details: i830 to i870 Doing any 5250 OLTP work? All upgrades are Roll-in / Roll-out Memory: All new memory cards required All HSL expansion towers migrate Migration towers and any connected SPD towers cannot be used on i870 Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i870 System Unit need to be converted to #46xx i870 requires DVD IOPs/IOAs/DASD that can migrate See System Handbook, GA

54 Upgrade Paths: i830 to i890 (assuming 5250 OLTP) From Processor From Interactive To Processor To Edition 2402, 2403, 2349 Any , 2349 Any

55 Upgrade Details: i830 to i890 Doing any 5250 work? All upgrades are Roll-in / Roll-out Memory: All new memory cards required All HSL expansion towers migrate Migration towers and any connected SPD towers cannot be used on i890 Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i890 System Unit need to be converted to #46xx i890 requires DVD IOPs/IOAs/DASD that can migrate See System Handbook, GA

56 Upgrade Paths: i840 to i870 (assuming 5250 OLTP) From Processor From Interactive To Processor To Edition Any

57 Upgrade Details: i840 to i870 Doing any 5250 work? All upgrades are Roll-in / Roll-out Memory: All new memory cards required All HSL expansion towers migrate Migration towers and any connected SPD towers cannot be used on i870 Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i870 System Unit need to be converted to #46xx i870 requires DVD IOPs/IOAs/DASD that can migrate: See System Handbook, GA

58 Upgrade Paths: i840 to i890 (with/without 5250 OLTP) From Processor From Interactive To Processor To Edition N/A

59 Notes: i840 to i890 (with/without 5250 OLTP) In this foil we include supported both no 5250 OLTP and with 520 OLTP application target feature and editions. As a reminder, 7422 is a Standard Edition and 7424, 7427 are Enterprise Editions. See the foil "New Structure: Hardware Simplification and Editions" for Standard and Enterprise Edition values.

60 Upgrade Details: i840 to i890 All upgrades are Roll-in / Roll-out Memory: All new memory cards required All HSL expansion towers migrate Migration towers and any connected SPD towers cannot be used on i890 Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i890 System Unit need to be converted to #46xx i890 requires DVD IOPs/IOAs/DASD that can migrate: See System Handbook, GA

61 Upgrade Paths: i800 to i800 From Processor From Package To Processor To Edition

62 Notes: Upgrade Paths: i800 to i800 This and the following series of foils show upgrades within the new January 2003 systems. Both Standard and Enterprise Editions are included. Toward the beginning of this presentation, refer to the foil "New Structure: Hardware Simplification, Editions" for a list of processor features and corresponding editions.

63 Upgrade Paths: i810 to i810 From Processor From Package To Processor To Edition

64 Upgrade Paths: i825 to i825 / i870 From Processor From Package To i825 To Processor To Edition From Processor From Package To i870 To Processor To Edition

65 Upgrade Details: i825 to i825 / i870 All upgrades are Roll-in / Roll-out Memory: All new memory cards required All HSL expansion towers migrate #5075 is not supported on i870, but can be converted to #5074 Migration towers and any connected SPD towers cannot be used on i890 Conversion offered for #5065/#5066 to #5074/#5079 Feature CD-ROM/Tape migrate Features migrated to i890 System Unit need to be converted to #46xx i890 requires DVD IOPs/IOAs/DASD that can migrate: See System Handbook, GA

66 Upgrade Paths: i870 to i870 / i890 From Processor From Package To i870 To Processor To Edition From Processor From Package To i890 To Processor To Edition

67 Upgrade Paths: i890 From Processor From Interactive or Package To Processor To Edition 0197 N/A

68 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

69 Notes: Feature Conversions for New Hardware We now cover a set of topics that include I/O conversions and main storage memory considerations.

70 Expansion Units Migration and SPD towers are not supported: Replace them with new towers - optionally, rekit disk units Upgrade 5065 to 5074, 5066 to 5079 Upgrade 5075 to 5074 No upgrades from 5074 to new 5094, 5079 to new 5294

71 Main Storage IBM eserver iseries Memory cards from existing hardware does not migrate to new systems Exception: memory cards from i can be used in i Base memory returns to IBM Feature memory remains property of customer - no memory conversions

72 Disk Unit Conversion Re-kittable 10 K RPM disk units can be converted to new systems and expansion towers Description Original Feature Code Target Feature Code 8.5 GB 10 K RPM 17.5 GB 10 K RPM

73 Support for Internal Storage Devices Internal tapes 4x82-4x83-4x84-4x86-4x87 are supported via IOA controllers 2757*, 2763, 2782*, 4748, 4778, 5705*, 9778 CD-ROM 4x25, DVD-RAM 4x30 and DVD-ROM 4x31 are supported via IOA controllers 2757*, 2763, 2782*, 4748, 4778, 5705*, 9778 *New as of January 2003

74 I/O Adapters IBM eserver iseries All IO adapters supported on current 8xx servers migrate to new servers See the following tables for conversion or replacement of PCI adapters and IOPs, previously housed in SPD buses

75 PCI IOA Feature Replacement or Conversion SPD BUS PCI HSL BUS R(EPLACE) OR C(ONVERT) Short Description #2718 #2768 / #5702 R Magnetic Media Controller #2720 # #4746 R WAN / Twinaxial Adapter #2721 #2742 / #4745 R 2-Line WAN Adapter #2722 #4746 R Twinaxial Adapter #2723 #4723 C 10 Mbps Ethernet Adapter #2724 #2744 R Token Ring Adapter #2726 #2763 / #4778 R Disk Unit Controller #2729 #2749 R Magnetic Media Controller #2740 #2763 / #4778 / #2757 R Disk Unit Controller #2741 #4748 / #2778 / #2757 R Disk Unit Controller #2745 #4745 C 2-Line WAN Adapter #2746 #4746 C Twinaxial Adapter #2748 #4748 C Disk Unit Controller #2750 #4750 C ISDN U Adapter #2751 #4751 C ISDN S/T Adapter #2761 #4761 C 8-Line Integrated Modem #2778 #4778 C Disk Unit Controller #2815 #4815 C 155 Mbps UTP OC3 ATM Adapter #2816 #4816 C 155 Mbps MMF ATM #2818 #4818 C 155 Mbps SMF ATM

76 Notes: PCI IOA Feature Replacement or Conversion -1 The following I/O Adapters (controllers) can be used but are "grayed out" as they are not recommended to covert to as the newer technology controller also listed: # PCI RAID Disk Unit Ctrl # PCI Magnetic Media Ctlr

77 PCI IOP Feature Replacement or Conversion SPD BUS PCI HSL BUS (R)eplace or (C)onvert) Short Description #4802 #4801 C Cryptographic Coprocessor #2809 #2843 / #2844 R LAN/WAN Workstation IOP #2824 #2843 / #2844 R IOP #2851 #2791 / #2799 R Integrated NetFinity Server #2854 #2791 / #2799 R Integrated NetFinity Server #2865 #2791 / #2799 R Integrated NetFinity Server

78 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

79 The Basics IBM eserver iseries Migration or Upgrade process always consists of: Requirements gathering Solution design and validation Components (hardware, software, services) selection Solution implementation Several iterations possible - each activity has multiple sub-activities Planning of each activity is key

80 Notes: The Basics There is no major difference between planning for migration or upgrade of existing servers, as compared to with previous releases. There are however some issues which will need special care, such as the replacement or migration of the load source, since a customer might be interested in replacing the current I/O subsystems in his server at the same time. Also, the January 2003 Power4 systems do not support SPD I/O attachment, not even migration towers. As always, the major requirement is to clearly understand and document the customer requirements and/or expectations, both from an operational and procedural way. In this phase, you will typically define what service delivery levels the customer wants to achieve with the new server, and how the migration or upgrade will be performed. This is a step in which all of the information will be collected, pertaining to throughput, response times, availability of the system, current footprint configuration, operational procedures and quantified and qualified expectations of the customer. Once this task is completed, a first design of the solution can be made, where no specific component is being selected, to validate the proposal with the customer. This step can lead into an iteration or specification of customer requirements, to refine the solution design. After the completion of the solution design the component can be defined, consisting of configurations, performance and throughput predictions, service engagements, procedures to be followed, timings, etc. See also APAR II3440, on the required level of PTFs for upgrading the V5R2 code to the correct level for support of the new hardware: Software Requirements for Model 800, 810, 825, 870, and certain 890 models If your newly shipped server from IBM is one of the models listed above, the correct level of software is shipped with your server. Proceed to section Requirements to support the new terms and conditions of OS/400 licensing to validate licensing information on your new server. If you are planning to upgrade your existing server to one of these new servers, you must have both requirement below: resave level B (RSB on the label) or later for V5R2 and PTF cumulative package xxxx or later for V5R2 This level of code must be on each partition of your existing server you are upgrading.

81 General server considerations General HSL- HSL-2 cables (conversion) RAID to RAID 35 GB vs. 70 GB drives Buy enterprise upfront - less expensive than upgrade No IXS on Standard to Enterprise Must load V5R2 (Feb 2003 level) and PTFs to support new hardware before upgrade

82 Notes: General server considerations This chart out lines the considerations that can apply across the whole server range. Key Points: HSL and the need for planning Need to examine current application environment - Standard (limited 5250 OLTP CPW) or Enterprise (full 5250 OLTP CPW and suite of software products) before making a decision. The term "5250 OLTP" (On Line Transaction Processing) is being introduced to distinguish applications doing 5250 I/O operations from the more generic term - "interactive" used in the past. The Performance presentation contains more details on this subject, and the System Handbook does as well. You should be loading V5R2 (Feb 2003 level) whether you are upgrading or not. However, when upgrading, you need to ensure you have the right level of V5R2 software to run the new hardware. We discuss this later in the personation. In general the HSL rules are not complex, provided you do read them! We have made it very easy to move I/O from existing HSL based system to the new models by employing a HSL to HSL-2 conversion cable. This cable can be used both ways round. From an existing model to a new tower or from an existing tower to a new model. With the new #2757 PCI-X Disk Controller comes a new implementation of RAID-5. When you move you RAID sets from an existing adapter to a new RAID adapter. The existing RAID structure will be removed and the new structure will be created. The new I/O structure and the new 70 GB 15K RPM drives offer 35 GB 15K RPM performance with twice the capacity. There is more information about this in the Technical Overview Performance presentation. Important notes: We suggest that the customers think about the Edition they are buying. It may be less expensive to buy the Standard Edition, but if you find you need to upgrade to Enterprise later, this is more expensive than the initial Enterprise Edition price. There may be features not included with the Edition upgrade. For example, there is no IXS on a Standard to Enterprise Edition upgrade. When purchased new, the i825, i870, i890 Enterprise Edition does include one 1.6 GHz IXS with 1 GB of memory. As the newly announce products and features all require V5R2 (Feb 2003 level) we suggest customer get this new code and start test an implementation now rather than just before any potential upgrade. A following foil describes how to get the correct V5R2 software updates when upgrading to a new server or adding the new I/O to an existing 820, 830, 840, and 890. The next foil discusses Load Source Migration considerations - a very important topic when upgrading or migrating!

83 Load Source Upgrade Flowchart Yes Load Source Change? No No Load Source Migration? Yes No Move Load Source? Yes Unload/Reload Services Check/Provide Disk Slots

84 Notes: Load Source Upgrade Flowchart When you are upgrading an existing 8xx server, you need to consider how you will implement the load source unit. Here are some of the possibilities and procedures on how to handle different types of load source migration scenario's: The load source unit, together with the disks that form its protection scheme (mirroring or RAID5) are removed from the current, or source, system unit and transferred into the new, or target, system, using the same disk adapter from the source system unit. This is by far the easiest way to migrate, since both the disk controller and its disk units will be transferred to the new system. The only exception is for the i270 to i810 upgrade where the i270 has a# 9767 base disk controller, since it is sent back to IBM after the upgrade. In this case, a new disk controller needs to be ordered on the i810, such as the #5705. In any of these cases, you have to make sure that there are enough free disk slots in the target system to house the same amount of disks from the source system in order to preserve the protection setup the source system was using (RAID5 arrays or mirrored sets). The load source unit, together with the disks that form its protection scheme (mirroring or RAID5) are removed from the current, or source, system unit and transferred into the new, or target, system, using new disk adapter technology that is acquired with the upgrade. When using RAID5 protection, the new disk adapter, such as the 2757, will, at IPL time, rearrange the parity distribution on the existing disks, according to the new algorithms used by these controllers. This requires a longer IPL time than would be needed otherwise. There will be a new load source unit, with a different capacity and/or format in the target system. In this case, you can either select to perform a full unload/reload or to use the load source migration utility to bring up the new system. If you want to use the load source migration as a service offering from IBM or a Business Partner, you need to make sure that enough disk slots are available under the disk adapter in the target system to match the existing configuration, depending on the existing protection setup (RAID5 or mirroring) and the required protection setup on the target system. For upgrades from 7xx, the same rules apply, but in this case, rekitting eligible SPD disks to 43xx needs to be included in the proposal and statement of work. All other cases will require an unload/reload. It is therefore essential that, before any upgrade can be considered, a detailed planning be performed, consisting of: Careful documentation of the existing disk protection and disk location in the system racks and expansion units. In certain cases, you might want to see this updated in the customer inventory records, especially if the load source specify does not represent what kind of unit the customer uses. Documentation of customer objectives for the upgrade, including: Maximum allowable downtime Expected changes in protection or capacity of the disk configuration Documentation of customer procedures for backup and recovery, including procedures for unload/reload Planning for intervention of service personnel during the upgrade When preparing any upgrade, we recommend to use the Solution Assurance procedure to catch any other possible issues and to avoid problems during the upgrade.

85 Hardware/Software Prerequisites

86 Hardware Support with V5R2 (Feb 2003 Level) Model 150, 6xx, S10, S20, S30, S40 and SB1 Not supported on the OS/400 release following V5R2 ATM (Asynchronous Transfer Mode) technology Not supported on the OS/400 release following V5R2 Hardware not supported at V5R2 Model 4xx/5xx 13GB QIC tape drives, Diskette drives, ISDN adapters Upgrades from 6xx, Sxx boxes into the new models. Hardware not supported by new models Migration towers are not supported on 800, i810, i825, i870 and the i890 Older SPD attached PCI towers are not supported (can convert) Internal QIC tape drives: 1.2GB, 2.5GB and 13GB SPD IOPs/IOAs are not supported Withdrawn hardware list and suggestions at:

87 Notes: Hardware Support with V5R2 (Feb 2003 Level) This foil gives the best summary of "older hardware" features V5R2 support statements. Migration Towers 5033,5034,5035 and 5077 are not supported on the new models. The SPD attached PCI towers are also not supported on the new models. The disks and the PCI cards need to be accommodated in a 5074 or a 5094 based on their compatibility. Some of the expansion units can be converted to work with the new models. However detailed planning needs to be done before beginning the expansion unit conversion if you are upgrading a partitioned server. Special note: Detailed planning is required to reassign the bus numbers while upgrading a partitioned server. Since the migration towers are no longer supported on the new models, all SPD only devices need to be connected to equivalent PCI IOAs which are supported on the new models. The device/ioa compatibility matrix along with the device support on the models need to be verified before moving the SPD attached devices..

88 Notes: Hardware Support with V5R2 (Feb 2003 Level) -2 This link tells you the features which are not supported by V5R2: If what you're looking for is an announcement letter of features which are no longer marketed, the announcement letter (US) is letter : Note the distinction between withdrawal from marketing and withdrawal of support. The withdrawal from marketing is a formal IBM announcement. A feature may be supported on new releases or systems long after it is no longer marketed. Withdrawal from support is not typically an announcement, but is generally conveyed through something like the planning web pages when a new software release or hardware model family is introduced. There is also a formal end of hardware maintenance at some point. IBM Technical Services (ITS) will declare this at a machine-type/model level when they determine that they are no longer going to provide maintenance under maintenance agreements for a given model. This is not done at a feature level. Being sound business persons, the ITS will keep maintenance agreements available as long as they are profitable.

89 HSL Planning and Considerations

90 HSL on new Models at V5R2 (Feb 2003 level) Mixed HSL on new Models 800 and 810 are both HSL HSL-2 available/supported on: i825, i870, i890 New PCI-X towers: 5088, 5095, 5094, 5294 HSL-2 with flexibility built in When connecting HSL towers to HSL-2 ports, you need (at least one) HSL to HSL-2 cable Copper HSL and Copper HSL-2 can be intermixed

91 Notes: HSL on new Models at V5R2 (Feb 2003 level) This foils lists the major "points to consider" in the HSL loop and cabling considerations when migrating (or upgrading) to new server hardware configuration. The mixing of new technology hardware with existing older technology hardware is a prime consideration. We include the listed topics in the following foils. Note: Support for the HSL-2 cables implies that with some future edition of the associated HSL adapters on both the iseries and the I/O towers on a loop consisting only of HSL-2 cables, higher maximum bits per second will be supported. At this time the planned availability of such adapters is not known.

92 HSL Rules and where to find them New rules for new servers and I/O econfig has some base rules built in You must plan your upgraded HSL environment Aim to achieve 'balanced' loops Try to segregate types of high demand I/O Tape, disk, and gigabit Ethernet IXA a special case Risk of loop split Migration tower iseries System Builder V5R2 (SG , System Handbook V5R2, GA , Private tower iseries Server Migration Redbook - IBM eserver iseries Server Migration: System Migration and Upgrades at V5R1 and V5R2, SG , http//:www-1.ibm.com/servers/eserver/iseries/ha/systemdesign.html Switchable tower Switchable tower Private tower

93 Notes: HSL Rules and where to find them As you can see, understanding HSL rules and making "best performance" choices require careful planning if you already have a large number of I/O devices on your existing system. xseries servers supported via the HSL cable attached to the Integrated xseries Server Adapter (IXA) needs special attention to ensure its functioning does not significantly impact the throughput of other devices on the same loop. We review the latest techniques and considerations in the next foils. Note the references for additional information.

94 HSL Loop Maximums System Maximums HSL Loops HSL Loops supporting fiber optic cables I/O Towers * 47* 47* IXA Cards in xseries towers I/O Towers and IXA Cards HSL OptiConnect Loops ** 14** HSL Migration Tower HSL Loop Maximums I/O Towers IXA Cards in xseries towers I/O Towers and IXA Cards HSL OptiConnect Loop - 2 systems I/O Towers and IXA Cards HSL OptiConnect Loop - 3 systems I/O Towers and IXA Cards N/A N/A N/A N/A * I/O Tower maximums do not include the base I/O tower attached to model 840, 870 and 890 ** OptiConnect not recommend on first loop (used to access load source device) Other notes: Maximum number of I/O towers per loop is 6. Maximum number of IXA per loop is 8. Maximum number of total I/O towers and IXA per loop is 9. Maximum number of non PCI-X I/O towers and IXA per loop is 5 total on each of the 825 1st and 2nd loops. Non PCI-X towers include the #0578, #5078, #5074, #5075, and the #5079 which counts as two towers. An I/O Tower has two HSL Ports (0 and 1). On Model 825 the IXA loop maximums vary by loop.

95 Notes: HSL Loop Maximums This is a nice summary chart, showing the maximum HSL loops on each of the 270 and 8xx servers, as well as the maximum towers per loop.

96 System Unit Cable Options Cable feature Cable name Copper m HSL Copper cable X X X X m HSL Copper cable X X X X m HSL Copper cable note 2 X m HSL to HSL-2 cable X X X X X X m HSL to HSL-2 cable note 2 X X X m HSL-2 cable X X m HSL-2 cable X X Fiber Optic (see note 1) m HSL Optical cable X X X m HSL Optical cable X X X m HSL Optical cable X X X m HSL Optical cable X X X SPCN m SPCN cable X X X X X X m SPCN cable X X X X X X m SPCN cable X X X X X X M SPCN cable X X X X X X m Fiber Optic SPCN cable X X X m Fiber Optic SPCN cable X X X Note 1: Fiber Optic cable requires a base or feature optical HSL Port card in the system Note 2: Not supported on the A1 port of the model 820. It is supported on the A0 port. General note: Fiber optic SPCN (System Power Control Network) cables include two copper to fiber adapters, p/n 90H

97 Notes: System Unit Cable Options Here you see the HSL cabling features available for Copper, Optical and SPCN (System Power Control Network) connections. See the notes for the appropriate table cell at the bottom of this foil.

98 I/O Tower Cable Options Cable feature Copper Cable name IXA card m HSL Copper cable X X X X X m HSL Copper cable X X X X X m HSL Copper cable X X X X X m HSL to HSL-2 cable X X X X X X X X X m HSL to HSL-2 cable X X X X X X X X X m HSL-2 cable X X X X m HSL-2 cable X X X X Fiber Optic (see note) m HSL Optical cable X X X X X X X m HSL Optical cable X X X X X X X m HSL Optical cable X X X X X X X m HSL Optical cable X X X X X X X SPCN m SPCN cable X X X X X X X X X m SPCN cable X X X X X X X X X m SPCN cable X X X X X X X X X m SPCN cable X X X X X X X X X m Fiber Optic SPCN cable X X X X X X X X m Fiber Optic SPCN cable X X X X X X X X note: Optical cable requires a base or feature optical HSL Port card in the tower note: 8093 same as a 8094 bottom and a 5074 top note: Fiber optic SPCN cables include two copper to fiber adapters, p/n 90H

99 Notes: I/O Tower Cable Options Here you see the HSL cabling features available for Copper, Optical and SPCN (System Power Control Network connections. See the notes for the appropriate table cell at the bottom of this foil. The next sequence of foils show some examples of HSL configurations.

100 HSL Migration Examples

101 Notes: HSL Migration Examples The next set of foils show some examples of the "more planning required" migration of an i820 to a new i825. showing HSL to HSL-2 cabling and IXA considerations. The following examples are not an exhaustive treatment of all possible HSL cable and I/O tower placement considerations.

102 HSL Migration Example (source system) 5074 Tower HSL cable HSL cable HSL Loop Model 820 HSL cable HSL cable xseries with HSL Adapter (IXA) 5074 Tower Note : If the bottom 5074 was a migration tower then the xseries & the top 5074 positions must be reversed.

103 Notes: HSL Migration Example (source system) The following charts demonstrate the flexibility that HSL provides for iseries in general and for upgrades. The chart show an example of a typical server upgrade where an 820 system (source systems) with two 5074 towers and an IXA, which is to be upgraded to an 825 (target system on the next foil). Key Points: This is a simple "plug and go" upgrade with the special consideration added of the I/O tower containing the IXA. Note the IXA and its position in the loop The source system is an 820 which has got only one HSL loop and therefore both the 5074s and the IXA are on one loop. The single loop on the Model 820 has always been a limiting factor - forcing expansion unit, migration tower and IXA mixture on the same loop.

104 HSL Migration Example (Target system) HSL-2 to HSL Cable 5074 Tower HSL Loop HSL to HSL cable HSL-2 to HSL Cable 5074 Tower Note: Three spare HSL cables HSL-2 to HSL cable Model 825 HSL Loop xseries with HSL Adapter HSL-2 to HSL cable

105 Notes: HSL Migration Example (Target system) This chart shows the resulting configuration of the 820 to 825 upgrade and the new HSL configuration. A key point is the 825 offers a great deal of flexibility and expansion is such a small package, including up to three HSL loop capability. The target i825, with its up to three HSL loops capability enables us to distribute the towers and the IXA across two different loops providing isolation and possible performance gains. The upgraded 825 system uses two of the possible three HSL loops. Note: On the source system the number of HSL cables used is 4. This leaves three spare HSL cables. In the target system, we use HSL-1 cables - 1 HSL to HSL-2 cable - 4 The target system needs 4 new HSL to HSL-2 cables (conversion cables) included in the order. Note on the HSL cabling costs. These cables are rather expensive, so be sure to include HSL cables in your planning.

106 Upgrade and adding two new I/O towers: 1 loop 5074 Tower HSL-2 to HSL Cable HSL cable 5074 Tower HSL Loop HSL cable HSL-2 to HSL cable xseries with HSL Adapter System i825 HSL-2 cable 5094 Tower HSL-2 cable 5094 Tower Note: Mix of PCI and PCI-X towers in one loop

107 Notes: Upgrade alternative: 825, 1 HSL loop This chart provides an alternative HSL solution to the previous chart but adds two new 5094 PIC-X I/O towers. This offers the least expensive option, but you should try to stay away from this if possible, because. of the exposure to errors affecting all I/O on the same loop. Also, it does not provide the best workload and I/O performance possibilities. While the IXA card on the same loop is a bi-directional device, its presence carries the risk that it can be inadvertently powered down. This breaks the loop. While the other expansion units are still connected to the system, the resiliency has been reduced. If a port or cable should fail while the IXA adapter is powered off. The adjacent expansion unit will fail.

108 Upgrade and adding two I/O towers: 2 loops 5074 Tower HSL to HSL-2 Cable HSL Loop HSL cable HSL to HSL-2 Cable 5074 Tower HSL-2 cable 5094 Tower HSL Loop HSL-2 cable HSL-2 cable 5094 Tower Note: PCI and PCI-X towers are on separate loops

109 Notes: Upgrade -adding two I/O towers: 2 loops In this example we do not show the xseries with HSL adapter. Rather we are showing a recommended best performance 825 HSL loop configuration when migrating 2 older PCI I/O towers and adding 2 new PCI-X I/O towers. We just placed them on separate loops. If you still had the xseries with HSL adapter you are faced with using a third HSL loop or adding the xseries with HSL adapter to one of the two loops - with the same consideration discussed on the preceding foil. This is the end of specific HSL loop considerations in this presentation. See the redbook listed earlier or the references at the end of this presentation for more complete scenarios and considerations.

110 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

111 Model Upgrades to new models review The supported model upgrades to new models can be broadly classified as: 270 to to to 810 7xx to 810, 825, 870, ,830,840, 825, 870, 890 to 825, 870, 890 Upgrades to rack mounted servers Note: For supported upgrades refer to V5R2 System Handbook, GA , January 24, 2003 iseries On Demand Announcement letter, redpaper IBM eserver iseries Supported Upgrades, REDP0322, IBM eserver iseries Server Migration: System Migration and Upgrades at V5R1 and V5R2, SG (red draft Feb 2003) The methods for achieving these model upgrades are: Load Source Migration Convert or relocate disks Unload/Reload Side-by-side In general you should carry out a Solution Assurance for any upgrade

112 General upgrade preliminary tasks Ensure installed release at latest fix level Install V5R2 (Feb 2003 level) before full system saves Full system saves before and after upgrade At least two saves Full tape clean before and after each save Ensure there is space for relocated and new components CD, disks, IOAs

113 Upgrade/Migration Scenarios Example-1 Customer has a 270 (Processor feature #2434) system with 6 disks on a #9767 controller with mirrored protection. Existing server is running V5R2 (Feb 2003 Level) Customer would like to upgrade to an 810 (processor feature #2469) RAID parity protection in the new server, is a requirement. New DASD controller #2757 ordered Additional Ethernet IOA ordered

114 Upgrade/Migration Scenarios Upgrade Tasks: Preliminary tasks Stop Mirrored protection on the source system Processor and Backplane replaced in the new machine Install old memory modules (Same memory modules supported) + any new ones New controller #2757 installed on the new backplane. (#9767 is not supported on 810) New Ethernet IOA installed Disks, CDROM, tape unit (not 13GB) and other IOPs may be migrated Migration depends on space/cost At IPL RAID protection started on the new machine Old Processor/Backplane returned to IBM Do a full system save This completes the upgrade activity

115 Upgrade/Migration Scenarios: Example - 2: Customer has a (processor CPW 2350) with Interactive Feature #1520 (70 CPW) and wants to replace it with an 810(#2469 processor feature) Target 810 must have Enterprise Edition #7430 Customer has five disks on the source machine with RAID on a #4748 controller Target machine has a new controller #2757 IOA

116 Upgrade/Migration Scenarios: Migration tasks: Preliminary tasks Upgrade not possible. New machine (migration) is brought in Old memory cards not supported. New memory installed on the machine DASD units removed from the old machine and installed on #2757 on the 810 CDROM/DVD/Tape units migrated from 270 to 810 provided there is space IOPs/IOAs migrated from 270 to 810 (provided there are available slots) During first IPL, RAID is restructured for each existing RAID set under a new #2757 NOTE: during this restructure activity, data is unprotected. Old 270 remains with customer Do a full system save This completes the upgrade activity

117 Upgrade/Migration Scenarios Example - 3: Customer has an AS/ machine with #2748 controller with an 8 GB load source. Customer upgrading to an 825 machine with 17.5 GB load source. Customer has an expansion tower 5065 connected to the source machine. Current server is at V5R2. This causes an additional step to install and test V5R2 (February 2003) PTFs. Possible scenarios depending planned disk configuration changes Many newer 10k RPM drives in base that will be reused Mixed disk drives configuration in base (size and speed) Few or no 10k RPM drives in base that will be reused Mixing disk sizes on target machines may impact performance

118 Upgrade/Migration Scenarios: Load Source Migration Upgrade steps with load source migration: Preliminary tasks Install 5065 or 5066 and drives to meet planned needs One drive to remain non-configured for Load Source Migration (LSM) Roll-in/Roll-out upgrade. All new memory DIMMs. Old memory not supported. Move user data from drives to be removed and spread across ASP The ASP includes the new drives in the 5065 tower Copy load source to non-configured disk unit in 5065 Convert 5065 to 5074 (replace IOPs/IOAs as required) Connect 5074 to new 825 Convert feature CDROM/tape to #46xx before migrating to 825 CEC Migrate/convert supported PCI IOAs Migrate/convert supported DASD features Migrate load source with LSM utility Return old 720 processor, frame to IBM. Do a full system save This completes the upgrade activity

119 Upgrade/Migration Scenarios: No Load Source Migration Upgrade steps with disk relocation (no load source change): Perform preliminary tasks Install 5065 or 5066 to meet planned needs Roll-in/Roll-out upgrade. All new memory DIMMs. Old memory not supported. Move user data from drives to be removed across ASP This includes the new drives in 5065 Convert 5065 to 5074 (replace IOPs/IOAs as required) Connect 5074 to new 825. Convert feature CDROM/tape to #46xx before migrating to 825 CEC. Migrate/convert supported PCI IOAs. Convert supported DASD features. IPL from converted Load Source Unit Return old 720 processor, frame to IBM Do a full system save This completes the activity

120 820, 830, 840, i890 to i825, i870, i890 upgrade summary Assume all I/O supported with latest PCI Very simple upgrades Carry out preliminary tasks Power down Unplug disks and I/O from old CEC Plug disks and I/O into new CEC Mixing disk sizes on target machines may impact performance

121 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

122 LPAR IBM eserver iseries Planning and information gathering is vital before LPAR upgrade Existing 820, 830, 840 to 820, 830, 840 follow existing V5 rules 270 to , 830, 840, 890 to 825, 870, 890 All partitions V5R2 (Feb 2003 level) Simple plug and go if Partition 0 (primary) owns all resources in system unit After automatic bus renumbering, fix bus ownership Add new resources to partitions as required Adapt partition to new processing resources 7xx to 825, 870, 890 All partitions V5R2 (Feb 2003 level) Disk Migration While Active (DMWA) to move user data to new or existing disk units in PCI towers Upgrade to new hardware Simple load source migration After automatic bus renumbering, fix bus ownership Recreate LPAR and adapt partitions to new processing resources

123 LPAR Upgrade considerations Can be simple - many simple tasks, but overall a complex process Ensure all partitions at most current release May be Roll-in/Roll-out Determine current system and target system resource allocations and bus ownership Assign new features, memory, processors Moving to and from CUoD systems Processor activation Memory installation May need IPL to make changes to Partition 0 (primary) Minimum / Maximum processor, storage allocations Upgrade to Model Ethernet LAN console only on Partition 0

124 7xx to 8xx example Simple upgrade process for complex environment OS/400 to V5R2 (Feb 2003 announce) Two LPARs (Primary and Secondary) Migrate storage to PCI tower Copy load source Convert 5066 to 5079 Copy load source to new server Bus renumbering Recreate LPAR configuration Reallocate resources Primary Secondary

125 8xx to 8xx LPAR upgrade Even simpler upgrade... Partitions to V5R2 (Feb 2003 Level) Add new tower to existing system Remove SPD hardware Unplug disk from Model 820 Plug disk into Model 825 Reallocate resources Go... If using a new disk IOA (e.g. #2757) you must remember RAID change processing Primary Primary Secondary Secondary

126 Side-by-side upgrade option Existing Side-by-Side P RPQ with a fee Up to 56 days Limited availability for upgrades to pre-feb 2003 Models 830 and 840 Redefined Side-by-Side P Information Only RPQ Only available through a special bid approval process -requires a negotiated price/contract for temporary software license, and... Up to 56 days to complete

127 Notes: Side by Side option Information only RPQ has existed in the past for side-by-side upgrades to earlier systems that included 830, 830, 840 target systems. That earlier support was chargeable. Starting in January 2003, this is ab Information only RPQ and, when approved through a special bids process, no longer has a price. Here are more details. This is an informational RPQ that provides the necessary information, guidelines and process to allow a customer to run two servers with the same type/serial number concurrently for a limited time period when upgrading to an iseries processor. The processor upgrade must be an upgrade which replaces a very large portion of the physical CEC to be a viable side by side. The two servers consist of: Source system: 720, 730, 740, 820, 825, 830, 840 which is being upgraded to an 825, 830, 840, 870, or 890 Target system: resulting 825, 830, 840, 870, or 890 Only published upgrade paths are supported. A side by side within a model is not allowed, that is, no 825 to 825, 830 to 830, etc. Also, an 870 to 890 is not supported as a side by side upgrade. A side by side is only available via the special bid process. A special bid must be completed by the appropriate geography pricer for each side by side. The special bid will establish the price for the side by side, provide a temporary software license and allow a retention of the return MES parts/features for a specified period of time not to exceed 8 weeks. A services contract will normally be required to cover the cost of additional service time and trips associated with a side by side. Prices for the special bid are dependent on the length of time and the resulting iseries model.

128 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

129 Upgrading in HA Environments Consider the two categories (types) of HA environments: Full replication environment ("full HA") Independent Auxiliary Storage Pool (iasp) switchable environment ("limited/planned high availability") Planning is essential You must test Will the customer business accept no protection during upgrade? If no, third system or LPAR will be required to maintain protection Operating system environment Create switchable test environment Application upgrade considerations Create switchable test environment - LPAR Is application available at new release? Is a data migration program required?

130 Notes: Upgrading in HA This foil reminds us of the extra importance of the planning considerations for upgrading/migrating to a new server in a "high availability" environment. If using a High Availability (HA) software package you need to get the software vendor involved. If performing your own "switching of I/O (disks/entire I/O tower)" you need to plan when to do the switch. In all situations you need to work with the business to determine how much "down time" they can tolerate and then do appropriate planning. A third system may be required. The next foils discusses the simpler, limited high availability, technique of using IASP switching between systems.

131 Upgrading Independent ASPs

132 Upgrade iasps Creation, switching IASPs enables most QSYS.LIB objects to be supported, New hardware does not impact V5R2 General Availability of iasp capabilities V5R1 to V5R2 upgrade Simple upgrade, all conversion automatic at vary on Cannot go back once V5R1 iasp varied on to V5R2 operating system Switchable iasps Create test environment Switch to backup server Upgrade primary partition (Partition 0) Switch back Upgrade backup server

133 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

134 Upgrading integrated Windows os environments Coming from older internal PC servers FSIOP, IPCS, INS, IXS to new IXS or IXA The latest 1.6 GHz Integrated xseries of iseries (IXS) Only supports Windows 2000 Server and Advanced Server operating systems (os) You must perform new Windows install to migrate Windows "Plug-n-Play" detects new hardware From existing Models 270, 8xx with IXA to new models of 8xx HSL-2 supports IXA, but HSL-2 to HSL conversion cable required No specific upgrade requirements When in HSL loop with migration tower, IXA position is critical Enterprise Edition includes an IXS under i825, i870, i890 (#2497/#2498)

135 Notes: Upgrading integrated Windows os environments This foil reminds us of the specific Windows operating systems supported on the newer Integrated xseries Servers for iseries supported on the internal IXS and externally via the IXA. Note that we covered the positioning of an Integrated xseries Servers for iseries HSL loop positioning much earlier in this presentation, starting with the "HSL Migration" section.

136 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

137 Upgrading Linux Partitions to V5R2 V5R2 adds Linux partition support of ESS external disks via direct attach to the #2766 Fiber Channel Disk adapter The LP9002L PowerPC Linux device driver available from Emulex Corporation Distribution v4.20p support Turbolinux Server 7.0 and SuSE Linux Enterprise Server 7: Yes Red Hat Linux 7.1: No No support for 2765 Tape adapter Up to 10 Linux partitions per on different iseries processor features 1-way processor = 9 Linux partitions 2-way processor = 19 Linux partitions 32-bit to 64-bit upgrades - V5R1 to V5R2 New January 2003 IOA support is included in SLES8 or driver update to SLES7 Linux version upgrades: there are no upgrade paths: re-install Linux

138 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

139 SAN and upgrades Automatic switch from 1GB/sec (V5R1) to 2 GB/sec on #2766/#2765 by installing V5R2 New #2757 controller (IOA) supports existing Fibre Channel adapters As of January 2003: no performance improvement expected Switch support Same as V5R2 General Availability SAN is unaware of server upgrade Add any new Fibre Channel IOAs Connect to SAN device (tape or disk) Any new LUNs appear as non-configured disks

140 Tape subsystems

141 Tape IBM eserver iseries New IOAs: Ultra SCSI Tape Controller #5702 Ultra SCSI Disk Controller / Tape Adapter #5705 SAN support for tape: Great support distance, up to 10km for Tape vaulting flexibility, zoning allows multi-system attach to single subsystem speed, 1GB/sec or 2GB/sec No change to #2765 support from V5R General Availability

142 Notes: Tape IBM eserver iseries This foils give us a January 2003 general update on tape support on V5R2. Note the two new IOAs, which are described in more detail on the next foil.

143 Ultra SCSI Disk Controller / Tape Adapters Ultra SCSI Tape Controller #5702 Two external Ultra SCSI ports Attachment for selected external tape and optical devices Support for LVD SCSI LTO Devices (358x-Lxx) Ultra SCSI Disk Controller / Tape Adapter #5705 No write cache Internal Ultra SCSI bus with support for up to 6 Disk Units (no RAID support), for the required DVD and optional removable media feature External Ultra SCSI bus with support for selected Magnetic Media and Optical devices Support for LVD SCSI LTO Devices (358x-Lxx)

144 Notes: Ultra SCSI Disk Controller / Tape Adapters The #5705 adapter has two Ultra SCSI ports, the first port is an internal port supporting up to 6 internal disk units and up to two internal removable media devices, the second port is external, please find supported devices and combinations below. The #5702 external SCSI adapter has two external Ultra SCSI ports. Devices supported on the external SCSI ports of the #5705 and the two ports of the #5702 PHYSICAL INTERFACE for both #5702 and external port of #5705 : VHDCI --- compare with #2749 : HD68 358x LTO drives with LVD (Low Voltage Differential) SCSI interface, more in general the 358X-Lxx tape devices and tape libraries with LVD connectivity Model QIC-SLR Tape Bridge Box Model GB 8mm Tape Drive Model /4-inch Tape Autoloader Model CD-ROM Bridge Box Model DVD-RAM Drive Possible combinations on a single port: One Model QIC-SLR Tape Bridge Box One GB 8mm Tape Drive One Model /4-inch Tape Autoloader One Model CD-ROM Bridge Box One Model DVD-RAM Drive One Model and one Model (the two devices are daisy-chained) One Model and one Model (the two devices are daisy-chained with the Model physically connected first) One Model and one Model (the two devices are daisy-chained with the Model physically connected first) One Model and one Model (the two devices are daisy-chained with the Model physically connected first) One Model and one Model (the two devices are daisy-chained with the Model physically connected first) One Model and one Model (the two devices are daisy-chained with the Model physically connected first)

145 Ultrium Stage-2 and Second Generation LTO 200 GB per cartridge and 35 MB / sec data transfer rate (uncompressed) Ultrium Stage-2 implemented in 3580 L23 and 3580 H with tape drive canister features # 1474 (LVD SCSI) # 1475 (HVD SCSI) # 1476 (Fibre) LVD SCSI connect to # 5702 and External port of # 5705 HVD SCSI connects to # 2749 Fibre channel connects to # 2765 Ultrium stage 2 drives can read and write Ultrium stage 1 media with improved performance

146 Notes: Ultrium-2 and Second Generation LTO During 1H 2003 IBM plans to announce the new Linear Tape-Open (LTO) IBM TOTAL STORAGE ULTRIUM-2 Tape Drives, which more than doubles tape drive performance over the LTO Ultrium Tape Drive (Ultrium 1) with up to 35 MB/sec native data transfer rate (70 MB/sec with 2:1 compression). In addition, with the use of the new IBM TotalStorage LTO Ultrium 200 GB Data Cartridge, the Ultrium 2 Tape Drive doubles the tape cartridge capacity up to 200 GB native capacity (400 GB with 2:1 compression) MODELS H23 AND L23 offer high capacity, performance, and technology designed for the midrange open systems environment. The Model L23 comes with a SCSI Ultra 160 LVD attachment, while the Model H23 comes with a UltraSCSI HVD attachment. The IBM LTO Tape Library 3584 now supports the IBM TOTALSTORAGE ULTRIUM-2 Tape Drives. These IBM Ultrium 2 Tape Drives come with SCSI Ultra 160 LVD, Ultra SCSI HVD, or switched fabric 2 Gbps Fibre Channel attachments for connection to open system servers including the iseries. The 3580 Model H23 and the UltraScalable Tape Library 3584, with the LTO Ultrium 2 HVD Drive Canister (#1475), can be attached to iseries and AS/400 models that support Version 5 Release 1 (V5R1), or later (depending on adapter type), and the following adapters: Feature PCI Magnetic Media Controller Feature PCI Ultra Magnetic Media Controller Feature 6534, Magnetic Media Controller The 3580 Model L23 and the UltraScalable Tape Library 3584, with the LTO Ultrium 2 LVD Drive Canister (#1474), can be attached to iseries and AS/400 models that support Version 5 Release 2 or later (depending on adapter type), and the following adapters : Feature PCI-X Ultra Tape Controller Feature PCI-X Ultra Tape Controller (external Ultra SCSI port) The UltraScalable Tape Library 3584, with the LTO Ultrium 2 Fibre Drive Canister (#1476), can be attached to iseries models that support Version 5 Release 1 (V5R1), or later (depending on adapter type), and the following adapter: PCI Fibre Channel Tape Controller (#2765) PRODUCT PREVIEW : IBM intends to further introduce and integrate the IBM TotalStorage Ultrium 2 Tape Drive technology in additional or alternative IBM LTO Ultrium 358x products. Previews provide insight into IBM plans and direction. Specific availability dates, ordering information, and terms and conditions will be provided when the product is announced. The IBM Ultrium 2 Tape Drives can read and write original LTO Ultrium Data Cartridges at original Ultrium-1 capacities and with improved performance up to 20 MB/sec native data transfer rate (40 MB/sec with 2:1 compression). Remember when configured in a SAN network, optimum performance may be affected by the number of switches between the system and the tape devices.

147 IBM TotalStorage - Enterprise Storage Server

148 External Disk - Enterprise Storage Server (ESS) No change to #2766 support from 2002 Multiple disk targets 32 devices per #2766 #2766 supports 1Gbit (V5R1) or 2 Gbit (V5R2) New IBM TotalStorage Enterprise Storage Server F GB - up to 55.9 TB Supports 15K rpm disks 18.2 GB, 36.4 GB, 72.8GB Up to 64 GB cache 2 Gbit SAN support RAID - 5 or RAID -10 Standard or Turbo processor feature Standard: 2 x 4-way SMP Turbo: 2 x 6-way SMP

149 Notes: External Disk - Enterprise Storage Server (ESS) The ESS is an intelligent disk system designed to provide high-performance high-availability, and high-capacity disk storage. The Model 800 is the third generation of the ESS and maintains the functionality, stability and reliability. Flexible capacity and performance are further enhanced with support for multiple disk drive capacities (18.2, 36.4, 72.8, and GB) at 10,000 and (18.2, 36.4 GB and 72.8 GB) 15,000 rpm. A storage subsystem's ability to scale upward, is in large measure gated by the performance needed to take advantage of the shear capacity it offers. Matching performance to scalability is thus a key component in delivering world class storage consolidation solutions. More details can be found at the following web site: Connectivity with iseries over 2 Gbps Fibre Channel is enabled with #2766 under V5R2 for higher performance, while supporting current customer investments by maintaining compatibility with existing 1Gb solutions. All components in the Fibre Channel connection need to be 2 Gbps enabled to make use of this ability.

150 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

151 IBM Services for Upgrades and Migration Installation and Implementation Services AS/400 BRMS Installation Services AS/400 System Transition Services IBM Implementation Services for iseries clustering and independent auxiliary storage pools IBM Implementation Services - for pseries and iseries LPAR Implementation Services - for iseries security* ServicePac for Installation Services Maintenance Hardware Maintenance Services Migration iseries Upgrade and Migration Services V5R2 Migration Services for AS/400 - Data Migration AS/400 Server Consolidation Services * New in 2003

152 IBM Services for Upgrades and Migrations 2 High Availability High Availability Services for AS/400 High Availability Server Assessment for Small and Medium Business Operational Support Account Advocate Advanced Support Consult Line On-site Technical Advocate On-site Technical Assistant PM eserver iseries (PM/400e) For more information:

153 Notes: IBM Services for Upgrade and Migration This foils summarizes IBM services related to iseries on this and the preceding foil. IBM Global Services (IGS) has a huge breadth of services available. Most service offerings are updated with each release. Included in these foils are services related to upgrade or migration. High Availability High Availability Services for AS/400 - Get the software and expertise you need to help keep your AS/400 system running smoothly and continuously. High Availability Server Assessment for Small and Medium Business - Help improve your system availability with a cost-effective, comprehensive assessment of your environment. Installation and Implementation Services AS/400 BRMS Installation Services - Help protect your information systems with quick, customized installations and on-site education. AS/400 System Transition Services - Smooth, effective, customized software migration from your present AS/400 system to a newer iseries system IBM Implementation Services for iseries clustering and independent auxiliary storage pools - Provides planning and implementation of Version 5 Release 1/Version 5 Release 2 clustering and IASP support IBM Implementation Services - for pseries and iseries LPAR - Plans and installs logical partitioning on your new or existing pseries or iseries servers Implementation Services - for iseries security - Helps you plan and implement basic security functions on iseries for the security level you need. This is newly expanded in ServicePac for Installation Services - Affordable, on-site installation and configuration services for notebook and desktop systems Maintenance Hardware Maintenance Services - Maintenance levels for IBM PC to enterprise server hardware Migration iseries Upgrade and Migration Services V5R2 - Helps you plan and implement your iseries upgrade Migration Services for AS/400 - Data Migration - Reduce downtime with a smooth migration and installation of direct access storage devices. Migration Services for AS/400 consolidation - Tap into our expert knowledge to migrate quickly and help prevent major system downtime.

154 Notes: IBM Services for Upgrade and Migration Operational Support Advanced Support - Highest level of remote software support which can be tailored to meet your needs Consult Line - Toll-free, scheduled telephone support for complex questions on RS/6000, AS/400 and S/390 systems, and PC and third-party software On-site Technical Advocate - On-site technical resources give your staff a helping hand On-site Technical Assistant - Platform-specific, on-site technical resources give your staff a helping hand Performance Management for zseries and pseries - Reports to assist with managing performance and capacity of the system. This is listed here indicate there is a PM for these other platforms as well as for iseries. PM eserver iseries (formerly PM/400e) - Enhance efficiency and fine-tune your iseries system with regularly scheduled usage reports. This includes basic reporting at no additional charge and additional charge more detailed reports. You can have your iseries performance data sent to PM eserver iseries and your or an authorized business partner can review performance history of your systems. You or they can input this summarized performance data to the Workload Estimator for sizing exercises..

155 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

156 Summary IBM eserver iseries Upgrades from 820, 830, 840 to new models Can be very simple Upgrades from 7xx to new models Well thought out MES process HSL cabling, I/O towers per loop need to be planed for SPD and older PCI I/O not supported on i825, i870, i890 Easy migration of newer PCI New upgrade paths 7xx upgrades 270, 820, 830, 840, 890 to 810, 825, 870, 890 upgrades May 2003: includes new entry model

157 Resources IBM eserver iseries IBM iseries Migration website iseries Information Center Memo to Users - available on home page of Information Center (provides national language version iseries Technology Center (itsc) IBM Services - Custom Technology Center (CTC) IBM server sales: Select Servers -> iseries -> iseries Sales Kit IBM PartnerInfo: Select Servers -> iseries -> iseries Sales Kit

158 Resources - 2 IBM Redbooks IBM eserver iseries - select iseries: IBM eserver iseries Server Migration: System Migration and Upgrades at V5R1 and V5R2, SG ITSO Redbooks Redpaper - IBM eserver iseries Supported Upgrades, REDP0322, planned availability February 24, 2003

159 Agenda IBM eserver iseries Basic upgrade and migration considerations System to system processor features migration I/O and main storage memory Key planning considerations - hardware, software, and HSL General upgrade and migration methods LPAR High Availability Windows Integration Linux Tape and external DASD iseries Services from IBM Global Services (IGS) References and Summary Appendix: Case Study example

160 Notes: Appendix: Example Case Study This example is a theoretical case study of an existing multi-system complex running several applications and a High Availability backup server. The systems are currently 830 models with similar, but exactly the same DASD, tape and main storage memory configurations. This example is given because it is more complex than the example given earlier in this presentation.

161 Several servers, several applications

162 Case Study Example: ERP Environment - 1 Service Delivery System Footprints: ERP Production: iseries V4R5 20 GB of main storage 90 * GB drives on 7 * x748 in 9074 (+ 5101) and * 2743 Gb and 1 * /100 Mb Ethernet 2 * 2749 Tape controllers ERP Backup (High Availability): iseries V4R5 20 GB of main storage 5077 Migration Tower 90 * GB drives on 7 * x748 in 9074 (+ 5101) and * 2743 Gb and 1 * /100 Mb Ethernet 2 * 2749 Tape controllers

163 Notes: Case Study Example: ERP Environment - 1 This foils begins our example case study description. There is an Enterprise Resource Planning (ERP) application on one server with a "hot backup" server.

164 Case Study Example: ERP Environment - 2 Service Delivery System Footprints: QA: iseries V4R5 6 GB of main storage 5077 Migration Tower 45 * GB drives on 3 * x748 in 9074 (+ 5101) 42 * x GB drives on MFIOP in 9057 and on 2 * 6533 in 5083/ * /100 Mb Ethernet and 1 * 4746 Twinax 1 * 6534 Tape controller Development: iseries V4R5 6 GB of main storage 5077 Migration Tower 45 * GB drives on 7 * x748 in 9074 (+ 5101) 12 * GB drives and 20 * GB drives on 2 * 6533 in 5083/ * 4 GB drives on MFIOP in * 4838 and 1 * 4746 Twinax Gb 1 * 6534 Tape controller

165 Notes: Case Study Example: ERP Environment - 2 This is the second of two application and servers descriptions. Two systems with two applications are listed -a QA and a powerful Development system.

166 Case Study Example: Objectives Requirements for: Processing power Production estimated to grow by 50% over the next year: Current CPU utilization at 70% Response times around 0.5 second per transaction Processing power for QA and Development largely insufficient: Estimated to run correctly if doubling the capacity Storage capacity (all servers) growing by 75% over the next year: Current capacity of 65% I/O rate around 10 per spindle per second Footprint consolidation of QA and Development Consolidation of storage for 15 Print/File servers and current iseries servers on single storage server infrastructure

167 Case Study Example: Constraints and Assumptions No 5250 interfaces active on any of the servers Global Data Center (GDC) implementation allows for 3 hours downtime per week (Sunday, 4-7 AM) QA database is exact copy of Production database (Save/Restore operation) High Availability solution is based on Data Replication only HA Server is located within 400 meter - not a real Disaster/Recovery solution Since the startup of the GDC, no single takeover was required Geographically distinct places can be used for hosting Backup and Production server Consider partitioning of the Backup Server to host both Development and QA server - during failover, a maximum of processing resources are assigned to the Backup server ERP application level is currently used

168 Notes: Case Study: Constraints and Assumptions This foil lists the constraints and assumptions used for the upgrade/migration. Note the consideration of perhaps using LPAR to host Development and QA on the same server as the ERP application backup. We assume a current release level of the ERP application , in our example.

169 Case Study Example: Solution Outline Consolidate Backup, Q&A and Development server using Logical Partitioning on a single server Consolidate storage on ESS server for OS/400 ERP servers and Print/File servers Upgrade ERP Production server: Validate ERP application release level runs on V5R2 or obtain updated ERP version Processing and storage capacity: Acquisition of system upgrade and expansion units Reuse of storage capacity from Backup, Q&A and Development server Migrate 3590 tape configuration from SCSI attachment to Fibre Channel (requires new tape "devices" or new FC feature Upgrade Backup server: Partition the system for Q&A, development and Backup Use Linux partitions for File/Print servers Add storage capacity to accommodate for: Storage needs DASD redistribution to Production server

170 Notes: Case Study Example: Solution Outline The proposed solution goes beyond a simple upgrade of a number of existing servers. The new components introduced here are: Server partitioning, to reduce the number of iseries footprints from 4 to 2; however, the number of server instances will increase, since the design attempts to avoid single points of failure, therefore using a so-called Thin Primary partition in the partitioned server. This partitioned server will house: The existing Backup server. The resource requirements for running data replication are light for the processor and main storage part, but equally high as for the disk storage capacity on the Production server. When this Backup server has to resume during a failover the service delivery for the Production server, its processing resources have to grow accordingly. The Q/A server. The Development server. Dedicated Storage Servers. Since the current geographical distribution of the servers is quite limited (the Production, Q/A and Development server are in the same room, the Backup server is located 200 m away, on the same campus), there is no real Disaster/Recovery possibility. The introduction of a Storage Server, attached via fibre optics to the server, allows to house the storage on a second campus, about 20 km away. This Storage Server will also be used to house the data of the existing Wintel File/Print Servers. Introducing extra storage capacity also means that the existing internal DASD capacity of the three servers can be added to the Production server, thus covering the needs for extra disk capacity on this server. Migrate 3590s from SCSI attachment to FC allows to put the tape devices at a greater distance from the Production server. In a later phase (beyond this example), it will be envisaged to replace the File/Print Servers running on a Wintel platform onto a Linux partition on the iseries servers to further optimize the management of the server farm.

171 Case Study Example: Solution Outline -2 Validate no 5250 applications in the future: Consider Standard Edition (limited 5250 OLT for administration) or Enterprise Edition because of integrated software products Collect iseries performance data (iseries Navigator Collection Services) and use available sizing or capacity planning tools IBM: Workload Estimator BMC Software, inc. Patrol for iseries - Predict Other tools

172 Notes: Case Study Example: Solution Outline -2 Understand that no future 5250 applications will be added. If yes, you can consider the Standard Edition for the target server. However, you should also understand the included software products and price of the corresponding Enterprise edition, to determine the best return on investment. Ensure you collect performance measurement data again and use available sizing (iseries Workload Estimator) or capacity planning tools (BMC Software inc. Patrol for iseries - Predict) or equivalent products to properly size the consolidated server. In a later phase (beyond this example), it is envisaged to replace the File/Print Servers running on a Wintel platform onto a Linux partition on the iseries servers to further optimize the management of the server farm.

173 Case Study Example: Solution Schematic Overview Before Upgrade / Migration Production Backup Q/A Development Partitioned System Production Backup Q/A Development After Upgrade / Migration

174 Case Study Example: Solution Details - The Big Picture Upgrade all servers to a V5R2 level Planning: Backup server Q/A and Development servers Production server Backup, Q/A and Development servers: Attain ESS skills or contract for service to install Attach 5078s with 2766 Install ESS capacity and configure Migrate DASD capacity from internal to external DASD Upgrade Backup server to i870; configure Logical Partitioning to house Q/A and Development Production server: Attach DASD capacity from three other servers Upgrade to i870

175 Notes: Case Study Solution Details - The Big Picture The objective of the planning is to provide as little as possible downtime for the production environment and to minimize the time of having the production environment to run unprotected by its Backup server. The first task would be to prepare the computer room on the second campus to host the ESS server, including putting in place all networking infrastructure (switches, cabling, etc.). At the same time, additional 5078 expansion units and 2766 FC attachments are installed on the Backup, Q/A and Development servers. Once the ESS is operational, data can be moved from the internal DASD storage and brought over to the ESS; since this data migration can be done during normal operations, the impact is minimal. Once the data is removed from the internal DASD, the 5074 expansion towers can be attached to the Production server and any existing SPD 10K RPM disks can be migrated to that server also. The second task is to upgrade the Backup server to an i870. In the base upgrade, we will provide hardware to support initially 2 partitions: one will act as thin primary, the other one will be the Backup server. Once this upgrade is completed, phase three will consist of migrating the existing DASD capacity of both Q/A and Development servers to be hosted on the Backup server in a logical partitioning environment. Since this will not require an unload/reload, the downtime for this operation will be limited. The final task will be to upgrade the Production server to an i870. Since at that time the Backup server has enough capacity to sustain the normal service delivery, a roll swap between the Production server and the already upgraded Backup server will help to reduce the downtime of the available services.

176 Trademarks and Disclaimers 8 IBM Corporation All rights reserved. References in this document to IBM products or services do not imply that IBM intends to make them available in every country. The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both: 400 BRMS Host Integration Series JustMail Payment Manager Stylized ADSTAR Client Series Host on Demand MQSeries Payment Server SystemView Advanced Function Printing ClusterProven Host Publisher MQSeries Integrator PCOM VisualAge for Java AFP CODE/400 HTTP Server for AS/400 Net.Commerce PowerPC VisualAge for RPG AIX DataGuide IBM Net.Data PowerPC AS WebSphere AnyNet DB2 IBM Logo NetFinity Print Service Facility WebSphere Advanced Edition Application Development DB2 Extenders IBM Network Station NetView pseries WebSphere Commerce Suite APPN DB2 UDB for AS/400 Information Warehouse NUMA-Q PSF WebSphere Development Tools for AS/400 AS/400 DB2 Universal Integrated Language Environment OfficeVision S/390 WebSphere Standard Edition AS/400e e-business logo Intelligent Printer Data Stream OS/2 San Francisco Workpad AT e(logo) Server, IPDS Operating System/400 Screen Publisher xseries BrioQuery Enterprise Storage Server iseries OS/400 SmoothStart cc:mail, Domino.Doc, Freelance, LearningSpace, Lotus, Lotus Domino, Lotus Notes, inotes, QuickPlace, Sametime, and Word Pro are trademarks of Lotus Development Corporation in the United States, other countries, or both. Tivoli and NetView are trademarks of Tivoli Systems Inc. in the United States, other countries, or both. C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or both and is used by IBM Corporation under license. ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. IBM's VisualAge products and services are not associated with or sponsored by Visual Edge Software, Ltd. Linux is a registered trademark of Linus Torvalds. UNIX is a registered trademark of The Open Group in the United States and other countries. SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. Other company, product and service names may be trademarks or service marks of others. Information is provided "AS IS" without warranty of any kind. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Information in this presentation concerning non-ibm products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute an endorsement of such products by IBM. Sources for non-ibm list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-ibm products. Questions on the capability of non-ibm products should be addressed to the supplier of those products. All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller for the full text of the specific Statement of Direction. Some information in this presentation addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance, function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here to communicate IBM's current investment and development activities as a good faith effort to help with our customers' future planning. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. Photographs shown are of engineering prototypes. Changes may be incorporated in production models.