20081219_VIOS_DS8k_DS4k_LUN_Identification

System Storage & System p Virtualization: Virtual I/O Server: DS8000/DS4000 LUN Identification and MPIO Attributes:

System Storage & System p Virtualization: Virtual I/O Server: DS8000/DS4000 LUN Identification and MPIO Attributes Gero Schmidt, ATS System Storage, System p & Storage CoP,ESCC Mainz EMail: gerosch@de.ibm.com System p & Storage CoP – (2008-12-18)

Fibre Channel Disk Identification:

2 Fibre Channel Disk Identification The VIOS uses several methods to tag devices that back virtual SCSI disks: Unique device identifier (UDID) IEEE volume identifier VIOS Identifier Comments The tagging method may have a bearing on the block format of the disk. The preferred disk identification method for virtual disks is the use of UDIDs . This is the method used by AIX MPIO support (Default PCM and vendor provided PCMs) Because of the different data format associated with the PVID method, customers with non-MPIO environments should be aware that certain actions performed in the VIOS LPAR, using the PVID method, may require data migration, that is, some type of backup and restore of the attached disks. Hitachi Dynamic Link Manager (HDLM) version 5.6.1 or above with the unique_id capability enables the use of the UDID method and is the recommended HDLM path manager level in a VIO Server. Note: By default, unique_id is not enabled PowerPath version 4.4.2.2 has also added UDID support. Note: Care must be taken when upgrading multipathing software in the VIOS particularly if going from pre-UDID version to a UDID version. Legacy devices (those vSCSI devices created prior to UDID support) need special handling. See vendor instructions for upgrading multipathing software on the VIOS. See vendor documentation for details. Some information can be found at: EMC: www.emc.com/interoperability/matrices/EMCSupportMatrix.pdf Hitachi: www.hds.com/assets/pdf/wp_hdlm_mpio_in_vio_TM-001-00.pdf

Identify DS8000 LUNs with UDIDs w/SDDPCM (1/2):

3 Identify DS8000 LUNs with UDIDs w/SDDPCM (1/2) $ lsdev -type disk name status description hdisk0 Available IBM MPIO FC 2107 -> with Host Attachment Script & SDDPCM installed $ lsdev -dev hdisk0 -vpd hdisk0 U789D.001.DQD73M9-P1-C1-T1-W500507630711CD16-L40 3E 40 00 00000000 IBM MPIO FC 2107 Manufacturer................IBM Machine Type and Model......2107900 Serial Number............... 75CT272 3E00 hdisk0 => DS8000 S/N 75CT272 LUN ID 3E00 [...] $ lspath status name parent connection DS8000 IO ports (see DSCLI # lsioport output): Enabled hdisk0 fscsi0 500507630711cd16 ,40 3e 40 00 00000000 WWPN 500507630711cd16 = DS8k Port I0213 Enabled hdisk0 fscsi1 500507630719cd16 ,40 3e 40 00 00000000 WWPN 500507630719cd16 = DS8k Port I0313 WWNN 5005076307ffcd16 = DS8k WW Node Name $ lsdev -dev hdisk0 -attr attribute value description user_settable PCM PCM/friend/sddpcm PCM True PR_key_value none Reserve Key True algorithm load_balance Algorithm True [...] lun_id 0x40 3e 40 00 00000000 Logical Unit Number ID False lun_reset_spt yes Support SCSI LUN reset True max_transfer 0x100000 Maximum TRANSFER Size True node_name 0x 5005076307ffcd16 FC Node Name False pvid 00cc6de10da3c6560000000000000000 Physical volume identifier False [...] scsi_id 0x20300 SCSI ID False start_timeout 180 START unit time out value True unique_id 200B 75CT272 3E00 07210790003IBMfcp Device Unique Identification False ww_name 0x500507630711cd16 FC World Wide Name False

Identify DS8000 LUNs with UDIDs w/SDDPCM (2/2):

4 Identify DS8000 LUNs with UDIDs w/SDDPCM (2/2) VIOS restricted padmin access: $ lsdev -type disk | grep 2107 | while read a b; do echo "$a $(lsdev -dev $a -vpd|grep Serial)"; done hdisk0 Serial Number............... 75CT272 3E00 hdisk1 Serial Number...............75CT2723000 hdisk2 Serial Number...............75CT2723001 hdisk0 => DS8000 S/N 75CT272 LUN ID 3E00 hdisk3 Serial Number...............75CT2723200 hdisk4 Serial Number...............75CT2723201 hdisk5 Serial Number...............75CT2723401 VIOS root access: $ oem_setup_env # pcmpath query device DEV#: 0 DEVICE NAME: hdisk0 TYPE: 2107900 ALGORITHM: Load Balance SERIAL: 75CT272 3E00 ========================================================================== Path# Adapter/Path Name State Mode Select Errors 0 fscsi1/path1 OPEN NORMAL 10697 0 1 fscsi0/path0 OPEN NORMAL 10574 0 # odmget -q attribute=unique_id CuAt CuAt: name = "hdisk0" attribute = "unique_id" value = "200B 75CT272 3E00 07210790003IBMfcp" hdisk0 => DS8000 S/N 75CT272 LUN ID 3E00 type = "R" generic = "" rep = "nl" nls_index = 79 dscli> lshostconnect Date/Time: 15. September 2008 09:49:13 CEST IBM DSCLI Version: 5.4.0.520 DS: IBM.2107-75CT272 DS8000 DSCLI Name ID WWPN HostType Profile portgrp volgrpID ESSIOport =============================================================================================== ftss_vios_1_0 0014 10000000C978380C pSeries IBM pSeries - AIX 4 V4 all dscli> lsfbvol -volgrp v4 Date/Time: 15. September 2008 09:49:31 CEST IBM DSCLI Version: 5.4.0.520 DS: IBM.2107-75CT272 Name ID accstate datastate configstate deviceMTM datatype extpool cap (2^30B) cap (10^9B) cap (blocks) ============================================================================================================== ftss_3E00 3E00 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040

Identify DS4000 LUNs with IEEE IDs w/RDAC (1/2):

5 Identify DS4000 LUNs with IEEE IDs w/RDAC (1/2) $ lsdev -type disk name status description hdisk6 Available 1814 DS4700 Disk Array Device hdisk7 Available 1814 DS4700 Disk Array Device hdisk8 Available 1814 DS4700 Disk Array Device $ lsdev -dev hdisk7 -vpd hdisk7 U789D.001.DQD73M9-P1-C2-T1-W201600A0B811F9B2-L 4 000000000000 1814 DS4700 Disk Array Device DS4000 Profile: LOGICAL DRIVE NAME: lp1_data1 Logical Drive ID: 60:0a:0b:80:00:11:fa:78:00:00:35:d6:48:c5:db:a1 DS4000 IEEE Volume ID MAPPINGS (Storage Partitioning - Enabled (2 of 64 used))------------------- VOLUME NAME LUN CONTROLLER ACCESSIBLE BY VOLUME STATUS lp1_data1 4 B Host Group VIOs_Gruppe_1 Optimal DS4000 SCSI LUN ID $ lsdev -dev hdisk7 -attr attribute value description user_settable PR_key_value none Persistant Reserve Key Value True cache_method fast_write Write Caching method False ieee_volname 600A0B800011FA78000035D648C5DBA1 IEEE Unique volume name False lun_id 0x000 4 000000000000 Logical Unit Number False max_transfer 0x100000 Maximum TRANSFER Size True prefetch_mult 1 Multiple of blocks to prefetch on read False pvid 00cc6de152b2a0570000000000000000 Physical volume identifier False q_type simple Queuing Type False queue_depth 10 Queue Depth True raid_level 5 RAID Level False reassign_to 120 Reassign Timeout value True reserve_policy no_reserve Reserve Policy True rw_timeout 30 Read/Write Timeout value True scsi_id 0x21000 SCSI ID False size 10240 Size in Mbytes False write_cache yes Write Caching enabled False

Identify DS4000 LUNs with IEEE IDs w/RDAC (2/2):

6 Identify DS4000 LUNs with IEEE IDs w/RDAC (2/2) VIOS restricted padmin access: $ lsdev -type disk|grep DS4|while read a b; do lsdev -dev $a -vpd|grep hd; lsdev -dev $a -attr|grep ieee; done hdisk6 U789D.001.DQD73M9-P1-C2-T1-W201600A0B811F9B2-L 3 000000000000 1814 DS4700 Disk Array Device ieee_volname 600A0B800011FA78000035D748C5DC0B IEEE Unique volume name False hdisk7 U789D.001.DQD73M9-P1-C2-T1-W201600A0B811F9B2-L 4 000000000000 1814 DS4700 Disk Array Device ieee_volname 600A0B800011FA78000035D648C5DBA1 IEEE Unique volume name False hdisk8 U789D.001.DQD73M9-P1-C2-T1-W201600A0B811F9B2-L 5 000000000000 1814 DS4700 Disk Array Device ieee_volname 600A0B800011F9B20000606148C5D942 IEEE Unique volume name False VIOS root access: $ oem_setup_env # fget_config -Av ---dar0--- User array name = 'ds4700-tic-1' dac0 ACTIVE dac1 ACTIVE Disk DAC LUN Logical Drive hdisk6 dac1 3 lp11_data1 hdisk7 dac0 4 lp1_data1 hdisk8 dac1 5 lp2_data1

Identify DS8k/4k LUNs in VIO Client LPARS:

7 Identify DS8k/4k LUNs in VIO Client LPARS # lsdev -Cc disk hdisk0 Available Virtual SCSI Disk Drive hdisk1 Available Virtual SCSI Disk Drive hdisk2 Available Virtual SCSI Disk Drive # lsdev -Cc adapter | grep vscsi | while read a b; do lscfg -vl $a | grep vscsi; done vscsi0 U9117.MMA.06C6DE1-V34- C20 -T1 Virtual SCSI Client Adapter vscsi1 U9117.MMA.06C6DE1-V34- C25 -T1 Virtual SCSI Client Adapter # lsdev -Cc disk|grep "Virtual SCSI"|while read a b; do lscfg -vl $a; odmget -q attribute=unique_id CuAt|grep -p "$a\"" | grep value; done hdisk0 U9117.MMA.06C6DE1-V34- C25 -T1-L 81 0000000000 Virtual SCSI Disk Drive ID81 on vscsi1 value = "3520 200B 75CT272 3000 07210790003IBMfcp 05VDASD03AIXvscsi„ hdisk1 U9117.MMA.06C6DE1-V34- C20 -T1-L 83 0000000000 Virtual SCSI Disk Drive ID83 on vscsi0 value = "3520 600A0B800011FA78000035D648C5DBA1 05VDASD03AIXvscsi„ hdisk2 U9117.MMA.06C6DE1-V34- C20 -T1-L 82 0000000000 Virtual SCSI Disk Drive ID82 on vscsi0 value = "3520 200B 75CT272 3001 07210790003IBMfcp 05VDASD03AIXvscsi„ # odmget -q attribute=unique_id CuAt | egrep "name|value" name = "hdisk0" value = "3520 200B 75CT272 3000 07210790003IBMfcp 05VDASD03AIXvscsi„ DS8000 S/N 75CT272 LUN 3000 name = "hdisk1" value = "3520 600A0B800011FA78000035D648C5DBA1 05VDASD03AIXvscsi„ DS4000 LUN with IEEE identifier 600A0B800011FA78000035D648C5DBA1 name = "hdisk2" value = "3520 200B 75CT272 3001 07210790003IBMfcp 05VDASD03AIXvscsi„ DS8000 S/N 75CT272 LUN 3001

UDIDs and IEEE IDs in VIO Server & Client LPARS:

8 UDIDs and IEEE IDs in VIO Server & Client LPARS $ lsdev -type disk|grep hdisk|while read a b; do echo "$a $(lsdev -dev $a -attr|grep -E 'unique|ieee')"; done hdisk0 unique_id 200B75CT2723E0007210790003IBMfcp Device Unique Identification False hdisk1 unique_id 200B 75CT272 3000 07210790003IBMfcp Device Unique Identification False hdisk2 unique_id 200B75CT272300107210790003IBMfcp Device Unique Identification False hdisk3 unique_id 200B75CT272320007210790003IBMfcp Device Unique Identification False hdisk4 unique_id 200B75CT272320107210790003IBMfcp Device Unique Identification False hdisk5 unique_id 200B75CT272340107210790003IBMfcp Device Unique Identification False hdisk6 ieee_volname 600A0B800011FA78000035D748C5DC0B IEEE Unique volume name False hdisk7 ieee_volname 600A0B800011FA78000035D648C5DBA1 IEEE Unique volume name False hdisk8 ieee_volname 600A0B800011F9B20000606148C5D942 IEEE Unique volume name False # odmget -q attribute=ieee_volname CuAt # odmget -q attribute=unique_id CuAt CuAt: CuAt: name = "hdisk7" name = "hdisk1" attribute = "ieee_volname" attribute = "unique_id" value = " 600A0B800011FA78000035D648C5DBA1 " value = " 200B 75CT272 3000 07210790003IBMfcp " type = "R" type = "R" generic = "D" generic = "D" rep = "s" rep = "nl" nls_index = 85 nls_index = 42 # odmget -q attribute=unique_id CuAt CuAt: name = " hdisk0 " attribute = "unique_id" value = "3520 200B 75CT272 3000 07210790003IBMfcp 05VDASD03AIXvscsi" type = "R" generic = "" rep = "n" hdisk0 => DS8000 S/N 75CT272 with LUN ID 3000 nls_index = 0 CuAt: name = " hdisk1 " attribute = "unique_id" value = "3520 600A0B800011FA78000035D648C5DBA1 05VDASD03AIXvscsi" type = "R" generic = "" rep = "n" hdisk1 => DS4000 LUN IEEE ID 600A0B800011FA78000035D648C5DBA1 nls_index = 0 VIO Client VIO Server

Dual VIOS – Overview MPIO Attributes :

9 Dual VIOS – Overview MPIO Attributes

Virtual SCSI General Notes….:

10 Virtual SCSI General Notes…. Notes If you are using FC Multi-Path I/O on the VIOS , set the following fscsi device values (requires switch attach): dyntrk=yes (Dynamic Tracking of FC Devices) fc_err_recov= fast_fail (FC Fabric Event Error Recovery Policy) (must be supported by switch) If you are using MPIO on the VIOC set the following hdisk device values on the VIOS : reserve_policy=no reserve (Reserve Policy) If you are using MPIO on the VIOC, set the following vscsi/hdisk device values: hcheck_interval = 20 (Health Check Interval; default: 0 = disabled ) vscsi_path_to = 30 (Virtual SCSI Path Timeout; default:0 = disabled )

Dual VIOS - Attributes of the Fibre Channel Adapter:

11 Dual VIOS - Attributes of the Fibre Channel Adapter Changing the attributes of the Fibre Channel adapter (fscsiX): fc_err_recov dyntrk $ chdev -dev fscsi0 -attr fc_err_recov=fast_fail dyntrk=yes -perm fscsi0 changed $ lsdev -dev fscsi0 -attr attribute value description user_settable attach switch How this adapter is CONNECTED False dyntrk yes Dynamic Tracking of FC Devices True fc_err_recov fast_fail FC Fabric Event Error RECOVERY Policy True scsi_id 0x660c00 Adapter SCSI ID False sw_fc_class 3 FC Class for Fabric True The reason for changing the fc_err_recov attribute to fast_fail is that if the Fibre Channel adapter driver detects a link event, such as a lost link between a storage device and a switch, then any new I/O or future retries of the failed I/O operations will be failed immediately by the adapter until the adapter driver detects that the device has rejoined the fabric. The default setting for this attribute is delayed_fail . Setting the dyntrk attribute to yes makes AIX tolerate cabling changes in the SAN. Be aware that this function is not supported on all storage systems. Check with your storage vendor for support. Reboot the Virtual I/O Servers for the changes to the Fibre Channel devices to take effect.

Dual VIOS - Attributes of the hdisk (DS4000):

12 Dual VIOS - Attributes of the hdisk (DS4000) With Dual VIOS the disks need to be accessed through both Virtual I/O Servers. The reserve_policy for each disk must be set to no_reserve on VIO_Server#1 and VIO_Server#2. Change the reserve_policy attribute to no_reserve using the chdev command. $ chdev -dev hdisk2 -attr reserve_policy=no_reserve hdisk2 changed $ lsdev -dev hdisk2 -attr attribute value description user_settable PR_key_value none Persistant Reserve Key Value True cache_method fast_write Write Caching method False ieee_volname 600A0B8000110D0E0000000E47436859 IEEE Unique volume name False lun_id 0x0003000000000000 Logical Unit Number False max_transfer 0x100000 Maximum TRANSFER Size True prefetch_mult 1 Multiple of blocks to prefetch on read False pvid none Physical volume identifier False q_type simple Queuing Type False queue_depth 10 Queue Depth True raid_level 5 RAID Level False reassign_to 120 Reassign Timeout value True reserve_policy no_reserve Reserve Policy True rw_timeout 30 Read/Write Timeout value True scsi_id 0x660a00 SCSI ID False size 20480 Size in Mbytes False write_cache yes Write Caching enabled False

Dual VIOS - VSCSI & MPIO Attributes in Client Partitions:

13 Dual VIOS - VSCSI & MPIO Attributes in Client Partitions # lsdev -Cc disk hdisk0 Available Virtual SCSI Disk Drive hdisk1 Available Virtual SCSI Disk Drive # chdev -l vscsi0 -a vscsi_path_to=30 -P vscsi0 changed # chdev -l hdisk0 -a hcheck_interval=20 -a hcheck_mode=nonactive –P (Reboot required) hdisk0 changed # lsattr -El hdisk0 PCM PCM/friend/vscsi Path Control Module False algorithm fail_over Algorithm True hcheck_cmd test_unit_rdy Health Check Command True hcheck_interval 20 Health Check Interval True hcheck_mode nonactive Health Check Mode True max_transfer 0x40000 Maximum TRANSFER Size True pvid 00cc6de1cdcfd6130000000000000000 Physical volume identifier False queue_depth 3 Queue DEPTH True reserve_policy no_reserve Reserve Policy True # lsattr -Rl hdisk0 -a algorithm fail_over only fail_over supported with vscsi devices # lsattr -Rl hdisk0 -a hcheck_mode enabled failed nonactive # lsattr -Rl hdisk0 -a hcheck_interval 0...3600 (+1) 0 means disabled On the virtual SCSI client adapter the virtual SCSI adapter path timeout feature should be configured. It allows the client adapter to check the health of Virtual I/O Server servicing a particular adapter and detect if a Virtual I/O Server is not responding to I/O requests. In such a case the client will failover to an alternate path if the Virtual SCSI adapter path timeout is configured nonactive (default) means healthcheck command is sent down to paths that have no active I/O, including paths with a state of failed.

Setting the Path Priority in VIO Client Partition:

14 Setting the Path Priority in VIO Client Partition Client SCSI Adapter vscsi0 Client SCSI Adapter vscsi1 hdisk0 rootvg LVM AIX Client Partition 1 MPIO default PCM failover only Client SCSI Adapter vscsi0 Client SCSI Adapter vscsi1 hdisk0 rootvg LVM AIX Client Partition 2 MPIO default PCM failover only Virtual I/O Server 1 Virtual I/O Server 2 PRIO1 PRIO2 PRIO2 PRIO1 vhost0 vhost1 vhost0 vhost1 # chpath -l hdisk1 -p vscsi1 -a priority=2 path Changed # lspath -AHE -l hdisk0 -p vscsi1 attribute value description user_settable priority 2 Priority True -> alternate I/O path # lspath -AHE -l hdisk0 -p vscsi0 attribute value description user_settable priority 1 Priority True -> preferred I/O path Change path priority: # lspath -AHE -l hdisk0 -p vscsi0 attribute value description user_settable priority 1 Priority True (1 = highest path priority) Display path priority: achive manual load distribution across both VIO server lpars

SCSI Queue Depth:

15 SCSI Queue Depth VIO Server PowerVM VIO Client vscsi0 scsi0 vtscsi0 vhost0 Logical Volumes VIO Server PowerVM VIO Client vscsi0 scsi0 vtscsi0 vhost0 Physical Disk Virtual Disks from LVs Physical Disk or LUN Queue Depth 1-256 Default: 3 (Single Queue per Disk or LUN) Virtual SCSI Client Driver 512 command elements (CE) 2 CE for adapter use 3 CE for each device for recovery 1 CE per open I/O request Virtual Disk Queue Depth 1-256 Default: 3 Sum should not be greater than physical disk queue depth Virtual Disk from Physical Disk or LUN

Disclaimer:

16 Disclaimer Copyright © 2008 by International Business Machines Corporation No part of this document may be reproduced or transmitted in any form without written permission from IBM Corporation. Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This information could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or programs(s) at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's intellectually property rights, may be used instead. It is the user's responsibility to evaluate and verify the operation of any on-IBM product, program or service. The performance information contained in this document was derived under specific operating and environmental conditions. The results obtained by any party implementing the products and/or services described in this document will depend on a number of factors specific to such party’s operating environment and may vary significantly. IBM makes no representation that these results can be expected in any implementation of such products and/or services. Accordingly, IBM does not provide any representations, assurances, guarantees, or warranties regarding performance. THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted according to the terms and conditions of the agreements (e.g., IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. IBM is not responsible for the performance or interoperability of any non-IBM products discussed herein. The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY, 10504-1785, U.S.A.

Trademarks:

17 Trademarks The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both. The following are trademarks or registered trademarks of other companies. * All other products may be trademarks or registered trademarks of their respective companies. Notes : Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput 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 improvements equivalent to the performance ratios stated here. IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply. All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions. This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area. All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are 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. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce. For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml: *, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA, WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, BladeCenter® Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market. Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States.