Home

Download: sg247659

Contents

1. i Tan Volumes TiO Rate Performance Figure 7 98 Subsystem performance Tivoli Storage Productivity Center volume creation After the Configure Devices tool is used to add an XIV Storage System into Tivoli Storage Productivity Center the NAPI introduced with Tivoli Storage Productivity Center V4 2 is used as the native interface between Tivoli Storage Productivity Center and the XIV Storage System This interface also enables Tivoli Storage Productivity Center to create a volume on the XIV Storage System and to map it to a host by using the Volume Create wizard Choose the XIV Storage System for which you want to create a volume by clicking Disk Manager Storage Subsystem and then click Create Volumes to start the Volume Create wizard The Tivoli Storage Productivity Center XIV user ID must have the storageadmin authority to create volumes 7 7 Tivoli Storage Productivity Center web based GUI Tivoli Storage Productivity Center can be accessed by using a web browser This feature is part of the normal installation and creates a link in the All Programs menu named Tivoli Storage Productivity Center web based GUI This opens a browser window using a link such as https ipaddress 9569 srm Login jsp where ipaddress is the address of the Tivoli Storage Productivity Center server This new GUI interface available with Tivoli Storage Productivity Center 5 1 offers the now common look and feel already available wit
2. Figure B 17 Signed Sun Java Directory certificate information 4 To check the xivstorage certificate click Directory Servers gt xivhost2 storage tucson ibm com 389 Security CA Certificates and click the xivstorage org sample CA Certificate Authority certificate link Figure B 18 shows that the certificate issued to and by the xivstorage CA is valid General Issued To ERMAILADDRESS cagm xivstorage on CN ivstorage O xivstorage L Tucson ST Arizona C U5 Issued By EMAILADDRESS camxivstorage org CN xivstorage O xivstorage L Tucson ST Arizona C US Valid From 6 29 09 2 24 PM Expires On 6 29 10 2 24 PM Type x 509 Serial Number Signature E 015 b0 be 6 Signature Algorithm MOSwithRsA Public Key Sun RSA public key 1024 bits modulus J50536730995091 0675 936705684 90000314 91869988 263283 796281764 8888644 8082 96689992063 936025114 1187158262602 07 280255 94245854174 7085068 94 01681538502256584 090033 9746303836665 963504 2876751283164 927 321393827597558264885346828836943619731303484 9297 670310317170085397 02750869126516194155733126618341 65290624 03 98868860683 public exponent 65537 Version 3 Figure B 18 Certificate information for xivstorage certificate authority 5 To activate the imported certificate click Directory Servers gt xivhost2 storage tucson ibm com 389 Security In the General tab click the Certificate drop down menu and select xivstorage org sample CA certificate as shown
3. Figure B 15 Adding signed certificate Importing a certificate authority certificate Until the xivstorage org CA is designated as a trusted root any certificate signed by that CA is untrusted You must import the CA s certificate using the Directory Service Manager manager application by completing the following steps 1 Click Directory Servers xivhost2 storage tucson ibm com 389 Security gt CA Certificates Add 2 Copy and paste the certificate authority certificate stored in the cacert pem file as shown in Figure B 16 Add Certificate Paste the certificate into the text field below The certificate text must be in ASCII format Indicates required field Server xivhost2 storage tucson ibm cam 389 i xivstorage org sample CA Certificate Authority certificate Certificate Hame amp O BEGIN CERTIFICATE Certificate 14 OSTOCArKgAwIBAgIBADANBgkqhkiG Iw 0 BAQOFADBSMOswCOYDVOOGEw VUZEO MAJGAIUECBMHOX pemSuYTEPMAOGA1UEBxMGVHVjc2 SuMRMwEQYDVOQKEwpdaxzz dG Oy Wad IMAMwEOYDVOOD EwpdaXZ2dG 9y WdlMSAwHgy Koz IhvcNAQKBFHFYUBA aX 2dG Oy Wodllm9y2z4eFwOwOTA2 MjkyMTIOMjNaFwOxMDA2MjkyMTIOMjNaM Hw Cz4 BQNVBAYTAIVTM RAwDgyYDVOOlEwd Bc m16b2 5hMO8wDQYDVOQHEW Ud WNzb 4 E2ARBghVBAoTCnhpdnlOb3 hz 2UxEz4RBgNV BAMTC nhpdnNOb3 hZ 2Ux DAeBgkg hkiG SwOBOOEWEWNhOHh pd n NO b3 hZ 2Uubs nMIGIMAOGC SqG SIb3 DOEBAGUAAAGN jiz 13d t0EVOn 8 Nv pSpV NF 6 266 SqccA Sw M g XC 9 id SPHWEpEYmmGkmGdLFW6 TAI BE
4. Network interface lo for local for status queries StatusInterface eth0 StatusPort 8989 HTTP proxy for connecting to the Internet HTTPProxyHost HTTPProxyPort The parameters referenced in the proxy conf file include the following parameters ListenInterface The network interface name on the host running the Remote Proxy agent that the XIV Storage System contacts when initiating a remote support connection for example ethO IBM XIV Storage System Architecture and Implementation ListenPort The TCP port on which Listenlinterface listens for example 8988 Important The XIV Storage System must be able to contact the host running the XIV Remote Support Proxy agent on the specified ListenInterface and ListenPort to run a remote support connection TargetAddress The network address of the XRSC server to which the XIV Remote Support Proxy agent initiates a connection This address is supplied by IBM Support TargetPort The TCP port of the XRSC server This port is normally set to 443 but confirm this port when you get the TargetAddress information from IBM Support StatusInterface The network interface name where you can query the status of the XIV Remote Support Proxy agent and show any active remote support connections StatusPort The TCP port on which Statuslinterface listens for example 8989 HTTPProxyHost The network address of an external web proxy This parameter is an optional parameter if there is an exis
5. gt Flexible snapshots Full storage virtualization incorporates snapshots that are differential in nature only updated data consumes physical capacity e Multiple concurrent snapshots are possible because a snapshot uses physical space only after a change has occurred on the source e Multiple snapshots of a single master volume can exist independently of each other e Snapshots can be cascaded in effect creating snapshots of snapshots Creation and deletion of snapshots do not require data to be copied and occur immediately When updates occur to master volumes the system s virtualized logical structure enables it to preserve the original point in time data associated with any dependent snapshots by redirecting the update to a new physical location on disk This process referred to as redirect on write occurs transparently from the host perspective and uses the virtualized remapping of the updated data to minimize any performance impact associated with preserving snapshots regardless of the number of snapshots defined for a given master volume Snapshot The XIV snapshot process uses redirect on write which is more efficient than copy on write that is used by many other storage subsystems Chapter 2 IBM XIV Storage System logical architecture and concepts 25 gt Data migration efficiency XIV supports thin provisioning When migrating from a system that supports only regular or thick provisioning XIV
6. oExec StdIn WriteLine exit while oExec StdOut AtEnd0fStream Stringl oExec StdOut ReadLine n Stringl Stringl replace s s g if Stringl length 0 continue Chapter 7 Monitoring 375 strChar Stringl charAt 0 if strValidChars indexOf strChar 1 continue if Stringl gt Threshold Exceeded 1 if Exceeded Command custom event description Medium Latency exceeded threshold of Threshold during 24 hour period ending EndDate severity Severity CmdString xclicmd Command WshShell WScript CreateObject WScript Shell oExec WshShell Exec comspec d q oExec StdIn WriteLine prompt oExec StdIn WriteLine cd oExec StdIn WriteLine CmdString oExec StdIn WriteLine exit while oExec Status 0 WScript Sleep 100 WshShell LogEvent 0 XIV Latency Monitor Script Completed Successfully lt script gt lt job gt The script in Example 7 51 on page 375 also begins with defining variables that are used throughout the process It then builds an XCLI command that is based on these variables and runs the command in a shell The output from XCLI is again customized by using the t option to limit the display to only the specific fields in which we are interested In this case we need only the write hit medium latency field This option makes the output of the XCLI command easy to parse The XCLI command is st
7. After the XIV Remote Support Proxy agent is configured the connection to the XRSC is performed normally from the XIV Storage System as described in XRSC connection on page 326 The agent is a small program that runs on the following Linux versions v Red Hat Enterprise Linux Version 6 0 or later for x86 and x86 64 systems Red Hat Enterprise Linux Version 5 1 or later for x86 and x86 64 systems Red Hat Enterprise Linux Version 4 6 or later for x86 and x86 64 systems SUSE Linux Enterprise Server 11 or later for x86 and x86 64 systems vy y Important Review the latest release notes for updates The host running the agent must have TCP 443 outbound access to XRSC addresses information supplied by IBM Support and listens for inbound connections from the IBM XIV systems Figure 7 54 shows the necessary ports Customer Network Figure 7 54 XIV Remote Support Proxy agent ports For more information about the XIV Remote Support Proxy see the IBM XIV Storage System documentation http publib boulder ibm com infocenter ibmxiv r2 index jsp 7 3 4 Installation The installation files and documentation are at the storage portal website for XIV Click the Downloads tab http www 947 ibm com support entry portal Troubleshooting Hardware System Storag e Disk_systems Enterprise Storage Servers XIV_ Storage System 282810 2812 29 Chapter 7 Monitoring 333 334 On this website expand the list by clicking the M
8. Figure 4 69 Map FC volume to FC host 162 IBM XIV Storage System Architecture and Implementation Select an available volume from the left pane The XIV Storage Management GUI suggests a LUN ID to which to map the volume which can be changed to meet your requirements Click Map and the volume is assigned immediately There is no difference in mapping a volume to an FC or iSCSI host in the XIV Storage Management GUI LUN Mapping for Host view To complete this example start the host server and check connectivity The XIV Storage System has a real time connectivity status overview Click Hosts and Clusters gt Hosts Connectivity to access the connectivity status See Figure 4 70 E Hosts and Clusters l Hosts and Clusters ee Gee Performance Class Volumes by Hosts iSCSI Connectivity 4 70 Hosts Connectivity Figure The Host Connectivity window opens In the example the ITSO Win2008 and ITSO _Win2008 iscsi host definitions which are shown in Figure 4 71 are shown with their corresponding FC and iSCSI connections to the XIV Storage System Standalone Hosts J iTs0_win2008 me 50017380278A1234 EE 50017380275A5678 J TSO_Win2008_ iscsi ign 1991 05 com microsoftadminib 2999unn J Ipar2416 faa 10000000C9COFDD2 Gs a 10000000C9COFDDS w c Figure 4 71 XIV Storage Management GUI example Host connectivity matrix Tip The Hosts Connectivity view
9. Figure 7 56 Add SNMP destination 3 From the Define Destination window which is now open enter a Destination Name a unique name of your choice and the IP or Domain Name System DNS of the server where the SNMP Management software is installed See Figure 7 57 Define Destination Destination Type SNMP Destination Name SystemsDirector IPIDNS 40 1 1 10 pa 0 er ey ee Figure 7 57 Define SNMP destination 4 Click Define to effectively add the SNMP Manager as a destination for SNMP traps In addition set up the rules for the defined SNMP destination as described in Setup notification and rules with the GUI on page 316 Afterward the XIV Storage System is set up to send SNMP traps to the defined SNMP manager The SNMP Manager software processes the received information SNMP traps according to the MIB file 338 IBM XIV Storage System Architecture and Implementation 7 4 2 Using SNMP commands to confirm the XIV Storage System status Although SNMP traps can be received from the XIV Storage System you can also send SNMP get or walk commands to collect status information from the XIV Storage System To accomplish this task you must use an SNMP manager that supports this task and you need to import the XIV Storage System MIB into that manager To send SNMP get commands you must know the SNMP community name By default the community name is set to XIV not public To confirm or change the SNMP comm
10. Here is a brief explanation of the 1dapsearch command line parameters gt H Idap xivhostl xivhostlldap storage tucson ibm com 389 Specifies that the LDAP search query must be sent to the xivhostl xivhostlldap storage tucson ibm com server using port number 389 gt D CN xivtestuserl1 CN Users DC xivhost11dap DC storage DC tucson DC ibm DC com The query is issued on behalf of the xivtestuser1 user registered in Users container in the xivhostlldap storage tucson ibm com Active Directory domain gt w pass2remember The current password of the user xivtestuser1 after the initially assigned password was changed to this new password gt b CN Users DC xivhost1ldap DC storage DC tucson DC ibm DC com Base_DN which is the location in the directory where to perform the search that is the Users container in the xivhostlldap storage tucson ibm com Active Directory domain gt cn xivtestuserl Specifies what object to search for The output of the 1dapsearch command shows the structure of the LDAP object retrieved from the LDAP repository We do not need to describe every attribute of the retrieved object but at least two attributes must be checked to validate the response gt name xivtestuserl gt description Storage Administrator The fact that Idapsearch returns the expected results in our example indicates the following gt The account is indeed registered in Act
11. Mapping logical unit numbers to a host The final configuration step is to map logical unit numbers LUNs to the host To do this task complete the following steps 1 While still in the Hosts and Clusters configuration pane right click the host to which the volume will be mapped and select Modify LUN Mapping from the menu see Figure 4 68 De tiime type ann Standalone Hosts i i iTi 30 Win20 g te ca jem S50017300273A12H Fit ee 50017380278A5678 Edit ITSO Win2008_iscsi Delete i ign 1991 05 com micra Rename g Ipar246 7 Create a Cluster with Selected Hosts g xivwi08 Add to Cluster g xvi Se a or nan g viz ET ee Move to Cluster a xIV4122 E o g swm Add Port J xIV132 Modify LUN Mapping J xIV133 View LUN Mapping a xiv20 Show statistics g XIVA g xv2 Properties g xIV23 Figure 4 68 Map LUN to host The LUN Mapping for Host window opens as shown in Figure 4 69 All Systems View By My Groups gt ITSO gt gt LUN Mapping for Host ITSO_Win2008 System Time 10 35 am Q Name Size GB MON Name Size GB Serial Zejn_02 vol_211 TP_BACKUP_LVM SLES Data _2 sles Data _1 Rybozyme RedHat Data_2 RedHat Data_1 oon mH Fe WH O myvol_13 myvol_12 myvol_11 myvol_10 ITSO_Blade9_LUN_4Mirr ITSO_Blade9_Lun_4_mirr ITSO_Blade9_LUN_3Mirr ITSO_Blade9_Lun_3_mirr ITSO_Blade9_LUN_2Mirr ITSO_Blade9_Lun_2_mirr ITSO_Blade9_LUN_1Mirr ITSO_Blade9_Lun_1_mirr ITSO test_10 ITSO test_09 ITSO test_08
12. System Time a Event Code All Alerting Date Local Time System EventCode ser es 9 20 13 1 06 PM XIV_PFE2 _ USER_HAS FAILED TO _RUN_C User cimmy fr 9 20 13 1 06 PM XIV_PFE2 UWSER_HAS FAILED TO_RUN_C User cimmy fr j y USER_HAS_FAILED_TO_RUN_C User cimmy fr lt I USER_HAS FAILED TO_RUN_C User cimmy fr ETET To Sees A USER_HAS FAILED TO_RUA_C User cimmy fr USER_HAS FAILED _TO_RUN_C User itso_seca F gt ER_HAS FAILED TO_RUB_C User cimmy fr USER_HAS FAILED TO RUN C User cimmy fr USER_HAS FAILED TO_RUN_C User cimmy fr USER_HAS FAILED TO_RUN_C User cimmy fr USER_HAS FAILED TO_RUH_C User cimmy fr Figure 7 55 Configure destination To configure a new SNMP destination complete the following steps 1 From the XIV Storage Management GUI main window select the Monitor icon Chapter 7 Monitoring 337 2 From the Monitor menu select Events to open the Events window as shown in Figure 7 55 on page 337 From the toolbar select Rules and perform the following steps a Click Destinations The Destinations window opens b Select SNMP from the Destinations drop down list c Click the green plus sign and click Destination to add a destination as shown in Figure 7 56 Gateways Destinations All SNMPEMAIL SMS Destinations Destination s desti mboelk de ibm com ai Rules XIV_TRAP 9 155 51 63 of Destination Destination Group
13. Unknown ok 1 38 TB 3 Sec oc atl XIV 2810 13002031BM xivaix 1_pool RAID 10 Unknown ok 91918 Groups xI 2810 1300774 1BM cetl0002 RAID 10 Unknown ok 384 00 GB E Storage Subsystems XI 2810 1300774IBM ITSO_ESX RAID 10 Unknown ok 944 00 GB Disks XI 2810 1300774 IBM jITSO_Windows RAID 10 Unknown ok 9 22 TB Volumes XI 2810 13007741BM OSL_POOL_O RAID10 Unknown ok 15 47 TB xI 2810 1300774 1BM OSL_POOL_THIN RAID 10 Unknown ok 30 94 TB I 2810 MNO0019 IBM test_pool RAID 10 Unknown ok 70 95 TB Storage Pools I 2810 MNO0033 IBM test_pool RAID 10 Unknown ok 14 75 TB I 2810 MNOO035 IBM test_pool RAID 10 Unknown ok 71 67 TB By Storage Subsystem Gi Array Sites H Disk Group Figure 7 94 XIV Storage System storage pools as seen by Tivoli Storage Productivity Center DADA DRA EARBARBAL Volumes A Volume Real Space column was added to report on the hard capacity of a volume while the pre existent Volume Space columns report on the soft capacity of a volume in these reports gt Volume Details window under Disk Manager gt Storage Subsystems Volumes gt Disk Manager Reporting Storage Subsystems Volumes gt Disk Manager Reporting gt Storage Subsystems Volume to HBA Assignment Chapter 7 Monitoring 365 gt Added Backend Volume Real Space for XIV Storage System volumes as back end volumes under Disk Manager Reporting gt Storage Subsystems
14. on page 205 However it is suggested to use the IBM Hyper Scale Management server when managing more than 40 IBM XIV systems For more information see the IBM Redpaper BM Hyper Scale for the XIV Storage System REDP 5053 114 IBM XIV Storage System Architecture and Implementation d Additional actions are available to delete or rename existing groups A menu is displayed by right clicking a group as shown in Figure 4 15 e If you select Rename Group a dialog box is displayed and you can enter a new group name e If you select Delete Group the group is removed Rename Group XIV MHO00 extrabam ITSO_Group Volumes 619 116 Enter A New Group Name Not Available ITSO_2_Group C l h Add System Delete Group Rename Group Figure 4 15 Delete and Rename Group options Note Deleting a group that contains systems also removes those systems from the GUI If you want to delete a group without removing the systems that it contains first move the systems out of the group by right clicking each system and choosing the Move System to option XIV Storage Management software features Both the XIV Storage Management GUI and XCLI are mostly self explanatory with organized structures and simple navigation Some of the standard and newer unique features are described in further detail in this section XIV Storage Management GUI main system view Management of the XIV Storage System begins at the main Syste
15. 348 IBM XIV Storage System Architecture and Implementation However for those systems you must install the IBM Systems Director Storage Control 4 2 1 to discover and collect inventory and monitor the health of devices You must issue the mkdatasource command to begin using IBM Systems Director Storage Control 4 2 1 to manage the storage device For XIV the command is issued as follows smcli mkdatasource c xiv i ip_address u user_id w password In this command ip_address is one of the XIV IP management addresses and user_id and password must match the user_id and password of an authorized XIV administrator For more information about the installation setup and configuration of IBM Systems Director see the documentation available at this website http publib boulder ibm com infocenter director pubs index jsp Compile the MIB file After you have completed the installation of your IBM Systems Director environment you prepare it to manage the IBM XIV Storage System by compiling the provided MIB file Ensure that you always use the latest MIB file provided The most recent MIB file can also manage XIVs on older code levels To compile the MIB file in your environment complete the following steps 1 Inthe IBM Systems Director window click Settings Manage MIBs as shown in Figure 7 68 IBM Systems Director E IBM Systems Director Welcome administrator Problems oe Wiew IBM Systems Director ca Man
16. Export Systems File Pool Alerts Thresholds Support Preferences Modify IP Addresses Exit Shutdown System Figure 3 34 System shutdown 100 IBM XIV Storage System Architecture and Implementation 2 To confirm the shutdown click OK and enter your login password as shown in Figure 3 35 Are you sure you want to shut down the machine and all its components Enter Login Password Figure 3 35 Confirm system shutdown The shutdown takes less than 5 minutes When done all fans and front lights on modules and all UPS lights are off Tip Using the XIV Storage Management GUI is the most convenient and best way to power off the system Using the XCLI From the command prompt issue the following command where XIV_01 is the system name xcli c XIV_01 u admin p adminadmin shutdown y You receive the response Command executed successfully If you are using the XCLI session use the shutdown procedure shown in Example 3 1 Example 3 1 Executing a shutdown from the XCLI session User Name itso Password x Machine IP Hostname 9 155 53 250 connecting XIV_01 gt gt shutdown Password Warning ARE YOU SURE YOU WANT TO SHUT DOWN y n Command executed successfully The shutdown takes less than 5 minutes When done all fans and front lights on modules and all UPS lights are off Chapter 3 IBM XIV architecture components and planning 101 102 Emergency power off The X
17. SSD solid state drive Shows SSD Caching status Locked Status Indicates the locking status of a volume or snapshot Snapshot Modification Status Shows if the snapshot was unlocked or modified Coupling Status Shows the copy services coupling status Snapshot Formatted Shows if the snapshot has been formatted Deletion Priority Indicates the priority of deletion by numbers for snapshots Created GUI Time Shows the creation time of a snapshot as measured at the GUI Created System Time Shows the creation time of a snapshot as measured at the XIV Storage System Created On Master GUI Time Created On Master System Time Creator Volume or snapshot creator name Serial Number Volume or snapshot serial number Most of the volume related and snapshot related actions can be selected by right clicking any row in the table to display a drop down menu of options The options in the menu differ slightly for volumes and snapshots Menu option actions The following actions can be performed through these menu options vy Adding or creating volumes see Creating volumes on page 151 vy Resizing a volume see Resizing volumes on page 154 vy Deleting a volume or snapshot see Deleting volumes on page 155 M Formatting a volume vy Renaming a volume or snapshot M Creating a consistency group with these volumes vy Adding to a consistency group y Removing from a consi
18. Where everything is kept Where the issued certs are kept Where the issued crl are kept database index file default place for new certs The CA certificate The current serial number The current CRL The private key private random number file The extentions to add to the cert Subject Name options Certificate field options how long to certify for how long before next CRL which md to use keep passed DN ordering Extension copying option S SE OEE IBM XIV Storage System Architecture and Implementation how long to certify for how long before next CRL which md to use keep passed DN ordering req distinguished name countryName countryName default countryName_ min countryName_max stateOrProvinceName stateOrProvinceName default localityName localityName default 0 organizationName O organizationName default organizationalUnitName commonName commonName_max emailAddress emailAddress_ max Country Name 2 letter code US 2 2 State or Province Name full name TX Locality Name eg city Tucson Organization Name eg company xivstorage Organizational Unit Name eg section xivstorage org eg your server s hostname 64 ca xivstorage org 64 The directories to store the certificates and keys must be created by running the following command mkdir root xivstorage orgCA root xivstorage orgCA certs root xivstorage orgCA crl root xivstorage orgCA newcerts root xivstorage orgC
19. gt lt fc_port_count value 4 gt lt ethernet_port_count value 4 gt lt io_allowed value yes gt lt io_ enabling priority value 0 gt lt serial value MBC0944037G3E64 gt lt original serial value MBC0944037G3E64 gt lt part_number value 98Y3335 gt lt original_part_number value 98Y3335 gt lt usm_version value 3 6RC1 gt lt bmc_version value 5 06 00000000 gt lt bios version value 5 00 00000000 gt lt fpga_version value 1 00 00000000 gt lt ses_ version value 3 1 0 18 gt lt pdb firmware value 4 01 gt lt pcm_1 firmware value 1 06 gt lt pcm 2 firmware value 1 06 gt lt fan_ controller firmware value UCD90910 2 0 9 0000 100520 2 2 0 gt lt battery_firmware value 0 00 gt lt sas_version value 0a030002h gt lt infiniband hca_ version value 2 9 1810 gt lt cna_version value 2 9 1200 gt lt memory_gb value 24 gt lt temperature value 24 gt lt normalized_ temperature value 22 gt lt chassis serial value SHM0984831PUJDT gt lt chassis_ part _number value 0984831 01 gt lt electronics serial value FTS0941313G167X gt lt electronics part_number value 0941313 04 gt lt module gt lt QUTPUT gt lt XCLIRETURN gt In Example 7 11 the ups_list command describes the status of the uninterruptible power supply UPS component It provides details about when the last test was performed and the results Equally important is
20. 10114 code level 11 4 0 esp4 p20130815 The connection is OK Trying to add the connection The connection has been added The scomu add command allows you to only define one XIV Storage System IP address at a time Repeat the add command for each XIV Storage System management IP address You must run the add command three times for each XIV Storage System Tip If you have clustered SCOM servers you must configure each XIV Storage System and each XIV Storage System management IP address on each server as well as the Root Management Server in the Management Group This action ensures that monitoring continues to work after a failover IBM XIV Storage System Architecture and Implementation 8 Because you defined your IBM XIV systems you can list them and confirm that they are all defined by running scomu list as shown in Example 7 56 The default output format is HTML and the list is displayed in the default web browser as shown in Figure 7 107 Example 7 56 Listing the monitoring systems scomu 1ist 3 connections have been found DE CAUsers Administrato D IBM Storage Management a IBM Storage Management Pack for Microsoft System Center Operations Manager IBM XIV Storage System DEV_TYPE IP USERNAME PASSWORD xiv 10 0 20 103 itso xiv 10 0 20 108 itso xiv 10 0 20 102 itso Figure 7 107 Output of the scomu list command The installation of the IBM Management Pack is complete You now nee
21. 9 155 113 143 389 D cn itso cn Users dc itso dc storage dc ibm dc com w PasswOrd b cn Users dc itso dc storage dc ibm dc com cn xivtestuser2 member0f dn CN xivtestuser2 CN Users DC itso DC storage DC ibm DC com memberOf CN NonXIVgroup CN Users DC itso DC storage DC ibm DC com memberOf CN XIVAdmins CN Users DC itso DC storage DC ibm DC com After all Active Directory groups are created and mapped to corresponding XIV Storage System roles the complexity of managing LDAP user accounts is reduced because the role mapping can now be done through Active Directory group membership management The easy to use point and click interface leaves less room for error when it comes to assigning group membership as opposed to entering text into the description field 5 8 5 OpenLDAP Directory and XIV Storage System role mapping OpenLDAP Directory group membership can be used for XIV Storage System role mapping as described in 5 8 4 Active Directory group membership and XIV role mapping on page 234 by using the memberOf attribute to explicitly identify wnat group memberships that a user has The role mapping mechanism is not restricted to using group membership to identify association to a suitable XIV Storage System role It can use a text based attribute directly identifying the XIV Storage System role the user has been associated with Configuring the XIV Storage System for OpenLDAP Directory Configuration for the OpenLDAP Directory is e
22. Basic configuration planning on page 87 gt IP address of the port all three ports must belong to the same subnet gt Subnet mask gt Default IP gateway if required Provide the following system level IP information not port specific gt IP address of the primary and secondary DNS servers gt IP address or DNS names of the SNMP manager if required gt IP address or DNS names of the SMTP servers Protocols The XIV Storage System is managed through dedicated management ports running TCP IP over Ethernet Management is carried out through the following protocols consider this design when configuring firewalls other security protocols and SMTP relaying gt Proprietary XIV Storage System protocols are used to manage the XIV Storage System from the XIV Storage Management GUI and the XCLI This management communication is performed over TCP port 7778 where the XIV Storage Management GUI XCLI as the client always initiates the connection and the XIV Storage System performs as the server gt XIV Storage System sends and responds to SNMP management packets gt XIV Storage System initiates SNMP packets when sending traps to SNMP managers gt XIV Storage System initiates SMTP traffic when sending emails for either event notification through email or for email to SMS gateways gt XIV Storage System communicates with remote SSH connections over standard TCP port 22 Chapter 3 IBM XIV architecture component
23. Chapter 5 Security 243 244 In Figure 5 79 on page 243 the server type selected must correspond to your specific LDAP directory either Microsoft Active Directory as shown or Sun Directory To view the expiration date of the installed certificate in the XIV Storage Management GUI open the Tools drop down menu at the top of the main XIV Storage Manager GUI window Click Settings LDAP click the Servers tab right click the name of the LDAP server and click Properties as shown in Figure 5 80 Properties FQDN itso storage ibm com Address 9 155 113 143 Base DN CN Users DC itso 0C storage DC Expiration Date 2012 10 03 05 43 20 Has Certificate Yes Port 369 Secure Port 636 Figure 5 80 Viewing the Active Directory server certificate expiration date By default LDAP authentication on an XIV Storage System is configured to use non SSL communication To enable the use of SSL in the XIV Storage Management GUI open the Tools drop down menu at the top of main XIV Storage Manager window Click Settings gt LDAP click the Secure LDAP tab and change the Use SSL setting from No to Yes as shown in Figure 5 81 LDAP Configuration General Use SSL ives Servers Certificate About To Expire Days in advance i User Credentials First Warning Second Warning Role Mappi e ae Third Warning Secure LDAP Parameters Figure 5 81 Enabling SSL for Active Directory LDAP communication IBM XIV Storage Syst
24. EFfk bort NxeStbeWm mil SAahDyPDxZqNo2ZH 2 M1 V3 PCwIDAGQABodHa Figure B 16 Importing the certificate authority certificate 3 After the CA and signed certificates are imported into the local keystore you can use the local certificate management tool to check whether the certificates are correctly imported Click Directory Servers gt xivhost2 storage tucson ibm com 389 Security gt Certificates and click the xivstorage org sample CA certificate link 426 IBM XIV Storage System Architecture and Implementation Figure B 17 shows that the certificate issued to xivhost2 storage tucson ibm com is valid and was issued by the xivstorage certificate authority General lssued To CNl sivhost2 storage tucson ibm com OU ITSO O xivstorage L Tucson S5T Arizona C U5 Issued By EMAILADORESS c amxivstorage or CN ivstorage O xivstorage L Tucson ST Arizona C U5 Walid From TANDS 3 48 PM Expires On 72 10 3 48 PM Type M 509 Serial Number Fi Signature Bm3 6d4 Signature Algorithm MD SwithRSA Public Key Sun RSA public key 1024 bits modulus JI4013 868825707 0663 740436839344 7388592902521 6935889507 FP1lISG354 17217 989988 7955529768116176 4181094 808162003 M44 609855350686161117 7281191517 S27 9092 788208722353744 7377156239184 381783 246525075007 218852 94 9411716333024 29991652533 9877472184384 2526111467 08 9245341361932503 2294 9095 27209088937 1573877 14 2807791146638 985203 public exponent 65537 Version 3
25. However the steps to go through for SMS are self explanatory and are described in Setting up notifications and rules using the XCLI on page 322 To proceed with SMTP click Next 5 Enter the gateway name of the SMTP gateway and click Next Enter the IP address or DNS name of the SMTP gateway for the gateway address and click Next The SMTP Sender Email Address window opens as shown in Figure 7 40 on page 318 Chapter 7 Monitoring 317 Wizard Gateway Create SMTP Sender Email Address x SMTP Sender Email Address In case of Email problems such as wrong Email address aresponse Email is sentto this address You can either specify an address for this server or use the system wide global address Type C Use default sender Sender Default Address Sender Use new sender address it Sender Email xiv01 yourcompanycom au Finish baka s pany J 6 Figure 7 40 SMTP Sender Email Address window 6 Set the sender email address You can use the default or enter a new address If there are email problems such as the wrong email address a response email is sent to this address Depending on how your email server is configured you might need to use an authorized address to ensure correct delivery of notifications Click Finish The Create the Gateway summary window opens as shown in Figure 7 41 Wizard Gateway Create Create the Gateway Create the Gateway Wel View the gateway attribute
26. Later in 6 4 2 Performance analysis on page 279 we describe how you determine whether the XIV Storage System has adequate performance capacity to handle more workload Each XIV Storage System module is carefully designed and has the appropriate processing mechanisms to handle the I O workload of the 12 disk drives There are several aspects to this module I O architecture A cache communicates to each of two serial attached SCSI SAS disk controllers over multiple lanes of the module PCI Express PCle bus The SAS controllers themselves have the appropriate number of processing capabilities to handle the I O requirements of the disk drives that they control These controllers in turn communicate to the disk drives over multiple lanes of the PCle bus All of this communication is handled by the correctly sized processor The cache is also correctly sized so that it can handle the total amount of I O that each module can sustain at peak performance Furthermore the XIV Gen3 with the XIV System software Version 11 1 0 or later also offers the option of an extended SSD cache The SSD cache can boost performance to up to three times for typical online transaction processing OLTP workloads with no additional configuration or tuning needed And with the XIV V11 2 software SSD performance has been further enhanced through optimization of SSD data integrity checking 250 IBM XIV Storage System Architecture and Implementation Note SSD per
27. SEI eas TTT aaa LL anna C I 1 Module 2 Data EE Beet U1 Module 1 Data eg am Pa oi 3 a ATS Figure 1 1 XIV Storage System components Front and rear views Maintenance Module B Module 6 Interface 1 Module 5 Interface Module 4 Interface Module 3 Data UPS 3 UPS 2 UPS 1 The model 214 includes the same components and brings the following enhancements gt Up to twelve 10 GbE ports for connecting to iSCSl attached hosts or twenty two 1 GbE ports gt Up to 15 CPUs providing 90 physical cores 180 logical cores using Intel Hyper Threading technology gt More energy efficient hardware that can reduce power consumption by up to 16 compared to previous models For both models 114 and 214 all of the modules in the system are linked through the two internal redundant InfiniBand module interconnects which enable maximum bandwidth usage and are resilient to at least a single component failure The system models 114 and 214 and all of its components come pre assembled and wired in a lockable rack Chapter 1 IBM XIV Gen3 Storage System overview 5 1 5 XIV Gen3 key design features This section describes the key design features of the XIV Storage System architecture We describe these key design points and underlying architectural concepts in detail in Chapter 2 IBM XIV Storage System logical architecture and concepts on page 17 1 5 1 Massive pa
28. Start Address 94 155 56 101 B De Level 0 Agentless Systems Figure 7 62 Discovery Range SNMP Devices SMI S Storage Devices Physical Platforms Level 2 IBM Director Agents Level 1 IBM Director Core Services Systems 3 155 56 100 9 155 56 102 O Unicast Address Unicast Range End Address Add Import Edit Remove Auto discover period hours 1 ii Presence Check period minutes 14 T OK Cancel Help Level 0 Agentless Systems Pilel Es 3 After you have set up the Discovery Preferences IBM Director discovers the IBM XIV systems and adds them to the IBM Director Console as shown in Figure 7 63 IBM Director Console lel Es Console Tasks Associations View Options Window Help A i iif ir GER T H m ta All Managed Objects SNMP System Object ID w Name a O 44 enterprises 8072 3 2 10 1 3 6 1 4 1 8072 3 2 10 E XY ESP 1 10 01300203 E xXIVESP 1 Y10 0 1300203 mm iA ESP 1 10 0 1300203 Ea XIV 10 0 MNOO050 E XIV 10 0 MNOO05O XIV 10 0 MNOO05O A xiv lab 01 mainz de ipm com TCPIIP Addresses H1552 09 155 53 251 9 155 53 250 9 155 56 101 9 155 56 100 9 155 56 102 Jeg Ge Le i eee E TCP IP Hosts dyn 9 155 53 252 mainz de ibm dyn 9 155 53 251 mainz de ibm dyn 9 155 53 250 mainz de ibm xiv lab 01 a mainz de ibm com xiv lab 01 mainz de ipbm com xiv lab 01b mainz de ibm com xiv lab 01b mainz de ibm com Operating Syst
29. The flash SSD cache can boost performance up to three times for typical OLTP workloads with no additional configuration or tuning needed The net result of this much cache is that the XIV Storage System can be aggressive about prestaging data into cache so that host system reads can be satisfied much faster than if the data must be retrieved from disk This section describes how the XIV Storage System global caching mechanisms work For details about the flash SSD caching see the Redpaper publication Solid State Drive Caching in the IBM XIV Storage System REDP 4842 Chapter 6 Performance 251 The XIV Storage System distributes cache into each module This distributed cache enables each module to concurrently service host I Os and cache to disk access Each module s cache just handles the movement of data into and out of that particular module The processing work that one module does to move data into and out of cache has absolutely no adverse effect on any other module Because of the XIV Storage System grid architecture this cache related I O workload is distributed evenly between all the XIV Storage System modules This situation is different from other enterprise storage systems which use a central memory cache that implements memory locking algorithms that generate access contention To improve memory management each Data Module uses a PCle bus between the cache and the disk controllers which provides a sizable interconnect betwe
30. UPS module complex The UPS module complex consists of three UPS units The UPS units work together to provide a cache battery function to sustain the XIV Storage System in the event of power fluctuations or loss The UPS complex sustains the system for up to 30 seconds in the event of a temporary loss of external power If there is an extended external power failure or outage that is greater than 30 seconds the UPS module complex maintains battery power long enough to allow a safe and orderly shutdown of the XIV Storage System The complex can sustain the failure of one UPS unit and still provide adequate protection against external power outages Internal UPS Although the system is protected by a UPS for internal usage you can reduce the risk of a power outage if you connect the system to an external UPS a backup generator or both The UPS complex is designed and dedicated to supporting the components inside the XIV Storage System rack No external equipment can be plugged into the UPS units The UPS complex is not substitute for traditional power conditioning or sustaining equipment typically found in a data center environment and is intended to be used with existing equipment Important The three uninterruptible power supplies UPSs in the XIV Storage System appear to the central uninterruptible power supply UPS system in the main data center as standard modern storage system power supplies The XIV Storage System does not affect
31. Volume to Backend Volume Assignment gt Volume Details window under Data Manager Reporting Asset By Storage Subsystem lt Subsystem Name gt Volumes gt Data Manager Reporting gt Asset gt System wide Volumes In Figure 7 95 a volume is shown in the ITSO pool It is 1015 GB in size and contains 1015 GB of actual data amp ITSO 80 11 288 0 GB Hard E AVW RedBk_ DB 10 1015 GB 1015 GB Figure 7 95 Volume properties shown in the XIV Storage Management GUI In Figure 7 93 on page 365 the same volume is shown in the Tivoli Storage Productivity Center GUI The volume space shows as 945 56 GB in Tivoli Storage Productivity Center because 1015 GB equals 945 56 GiB The XIV Storage Management GUI rounds down the volume size See Figure 7 96 volume Storage Subsystem SIY Fest Yolume Space 945 56 GB Yolume Real Space 945 56 GB Unavailable Yolume Space MiA Type Ra RAID Level RAID 10 Is Encryptable False Is Encrypted False Flash Copy None Attributes Surfaced Figure 7 96 Volume properties shown in the Tivoli Storage Productivity Center GUI Because of the nature of the XIV Storage System architecture and the fact that each volume is on all disks various reports in the Tivoli Storage Productivity Center GUI do not necessarily provide meaningful information for IBM XIV systems Correlation of disks and volumes for example under the Data Manager Reporting Asset gt
32. XIV Storage Management software on page 103 When working with the statistical information the XIV Storage System collects and maintains the performance data internally As the performance data ages it is consolidated to save space according to the following rules gt Data is kept for 365 days gt Detailed host and volume data is kept for 30 days By selecting specific filters the requested data is mined and displayed This section describes the functionality of the XVI Storage Management GUI and how to retrieve the required data The first item to note is that the current IOPS for the system is always displayed in the bottom center of the window This feature provides simple access to the current load on the system Figure 6 8 illustrates the XIV Storage Management GUI and the IOPS display It also shows how to start the statistics monitor XIV Storage Management Joes Systems Actions View Tools Help O Settings Launch XCLI fj Launch xIvTop amp itso All Systems 2 gt XIV_02_1310114 System v System Time 9 35 AM Q re Monitor XIV_02_ 1310114 Figure 6 8 Starting the statistics monitor on the GUI IBM XIV Storage System Architecture and Implementation Select Statistics from the Monitor menu as shown in Figure 6 8 on page 264 to open the monitor default window that is shown in Figure 6 9 Figure 6 9 shows the system IOPS XIV Storage Management Systems Actions View T
33. admin var Password adminpass Main Script Starts Here var CmdString var Stringl var output var xclicmd xcli m IPAddr u Username p Password var Command vol_ list vol Volume t used capacity CmdString xclicmd Command var WshShell WScript CreateObject WScript Shell var oExec WshShell Exec comspec d q oExec StdIn WriteLine prompt oExec StdIn WriteLine cd oExec StdIn WriteLine CmdString oExec StdIn WriteLine exit while oExec StdOut AtEnd0fStream Stringl oExec StdOut ReadLine n Stringl Stringl replace s s g if Stringl output Stringl if output gt Threshold IBM XIV Storage System Architecture and Implementation Command custom event description Vol Volume exceeded threshold of Threshold GB severity Severity CmdString xclicmd Command WshShell WScript CreateObject WScript Shel1 oExec WshShel Exec comspec d q oExec StdIn WriteLine prompt oExec StdIn WriteLine cd oExec StdIn WriteLine CmdString oExec StdIn WriteLine exit while oExec Status 0 WScript Sleep 100 WshShell LogEvent 0 XIV Vol Monitor Script Completed lt script gt lt job gt The script in Example 7 47 on page 372 begins with defining variables that are used throughout the process It then builds an XCLI command
34. gt LDAP Configuration gt Pools Alerts Thresholds IBM XIV Storage System Architecture and Implementation After you select which settings to paste a dialog window is displayed as shown in Figure 4 25 This window confirms your selection and allows you to begin copying the settings to the target system or to cancel the operation If you choose to proceed the dialog window shows the progress of the operation as it completes Mass Support Configuration Copying Support Configuration from Starbuck MNOO0027 to 1 system Click on Start in order to start operation a eet Figure 4 25 Copying configuration settings Dialog window System Selector menu Available from the hierarchical navigation is a quick access System Selector menu for viewing the status of all systems under management and easy navigating to a specific system This menu is available from the All Systems and group views To access the System Selector menu press Alt S or click the triangle icon to the right of the All Systems or Group Name links as shown in Figure 4 26 Press Alt S repeatedly to cycle though the systems that are shown in the menu xiv XIV Storage Management systems Actions View Tools Help ih All Systems Lonnectivity xv ATV Storage Management Systems Actions View Tools Help Ai w All Systems 7 gt Tucson Lab aj X onnectivity h System Selector Alt s Figure 4 26 Ac
35. he became a customer application engineer for hard disk drives supporting large OEM accounts in Europe In 2007 he joined the European Storage Competence Center as a Product Field Engineer PFE Since 2008 he has supported the XIV Storage System Dietmar holds a degree in Electrical Engineering Roger Eriksson is an STG Lab Services consultant based in Stockholm Sweden who works for the European Storage Competence Center in Mainz Germany He is a Senior Accredited IBM Product Service Professional Roger has over 20 years of experience working on IBM servers and storage including Enterprise and Midrange disk NAS SAN IBM System x IBM System p and IBM BladeCenter He has consulted and performed proof of concepts and education mainly with the XIV product line since December 2008 He has worked with both clients and various IBM teams worldwide He holds a Technical College Graduation in Mechanical Engineering Roman Fridli is a certified IBM XIV Product Field Engineer based in Switzerland He joined IBM in 1998 as a Customer Engineer for Power Systems and Intel Servers including point of sales Since 2012 he has worked for the XIV PFE EMEA Team based in Mainz Germany He holds a degree in Electrical Engineering and multiple certifications in the storage solution and networking area Itzhack Goldberg is an IBM Technical Advisor in the EMEA region for the XIV Storage System based in Haifa Israel Itzhack worked at the IBM Aus
36. rule Name Condition Rule Name Destination Snooze Escalation Finish Figure 7 45 Rule name window 11 To define a rule configure the following settings Rule Name Enter a name for the new rule Names are case sensitive and can contain letters digits or the underscore character _ You cannot use the name of an already defined rule Rule condition setting Select Severity only if you want the rule to be triggered by severity Select Event Code only if you want the rule to be triggered by event Or select Both Severity and event code for events that might have multiple severities depending on a threshold of certain parameters Select the severity trigger Select the minimum severity to trigger the rule s activation Events of this severity or higher trigger the defined rule 320 IBM XIV Storage System Architecture and Implementation Select the event code trigger Select the event code to trigger the rule s activation from the drop down list The list of event codes is predefined and cannot be modified See the XCLI User Manual GC27 2213 for a list of all the available event codes and descriptions to choose from Rule destinations Select destinations and destination groups to be notified when the event s condition occurs Here you can select one or more existing destinations or also define a new destination see Figure 7 46 Wizard Rule Create Rule destinations R
37. striping gt Operating system tunables Application threads The XIV Storage System grid architecture excels at and experiences peak performance when applications employ multiple threads to handle the parallel execution of I Os All modern commercial applications employ multiple I O threads The number of threads are often tunable From an XIV Storage System performance perspective it is best to use the maximum number of threads possible without having a negative impact performance impact on the application within the host server For single threaded applications if there is no compelling reason to run them in a serial fashion run as many of them in parallel as makes sense Host bus adapter and disk queue depth Queue depth is another example of how the XIV Storage System architecture is designed to perform best with real world client production workloads Queue depth is an important host HBA setting because it essentially controls how much data is allowed to be in flight onto the SAN from the host HBA A queue depth of one requires that each I O request is completed before another is started A queue depth greater than one indicates that multiple host I O requests can be waiting for responses from the storage system So the higher the queue depth the more parallel I O goes to the XIV Storage System The disk queue depth is an important OS setting as well that controls how much data is allowed to be in flight for a certain X
38. use ssl Indicates if secure SSL encrypted LDAP communication is mandated If set to yes without configuring both sides for SSL any encrypted communication for LDAP authentication on the XIV Storage System fails first_expiration_event Number of days before the expiration of the certificate to set the first alert Severity warning Set this parameter to a number of days that gives you enough time to generate and deploy a new security certificate second expiration event Number of days before the expiration of the certificate to set the second alert Severity warning third_expiration_event Number of days before the expiration of the certificate to set the third alert Severity warning Securing LDAP communication with SSL In any authentication scenario information is exchanged between the LDAP server and XIV Storage System where access is being sought Secure Sockets Layer SSL can be used to implement secure communications between the LDAP client and server LDAP over SSL LDAPS the secure version of LDAP protocol allows secure communication between the XIV Storage System and LDAP server by using encrypted SSL connections This protocol allows a setup where user passwords never appear in clear text SSL provides methods for establishing identity using X 509 certificates and ensuring message privacy and integrity using encryption To create an SSL connection the LDAP server must have a digital certificate signed by a trusted certi
39. 000 17 00 17 10 17 20 17 30 17 40 17 50 18 00 18 10 18 20 18 30 18 40 18 50 19 00 19 10 19 20 19 30 19 40 19 50 20 00 2010 pr 16 Feb 2012 N Interfaces 9 Read C 64 512 KB IOPS Cc Volumes Ys KB gt 512 KB O Latency hiiia Mi i Topi rf er gets JRW H n _ A 8 64 KB All BW Figure 4 78 Performance Statistics Mem Hit and SSD Hit For a detailed description of flash cache performance see Chapter 6 Performance on page 247 and Solid State Drive Caching in the IBM XIV Storage System REDP 4842 4 7 2 Managing flash cache with XIV Command Line Interface New commands are included in the XCLI that match the possible actions we illustrated for the GUI A useful command is help search ssd which displays a list of all commands related to SSDs This command is illustrated in Example 4 15 Example 4 15 List of commands related to SSDs XIV 1310039 Coruscant gt gt help search ssd Category Name Description system ssd_caching_disable Disables Flash Caching system ssd_caching_enable Enables SSD Caching system ssd_list Lists SSDs used as flash cache in the system system vol default _ssd_ caching get Gets the Default State of the SSD Caching system vol default_ssd_caching_set Sets aDefault State for SSD Caching system vol ssd_caching_set Overrides the Default SSD Caching State for a Volume IBM XIV Storage System Architecture and Implementation The ssd_c
40. 2 Custom monitoring of performance attributes In Example 7 51 we demonstrate how to create a WSH script to monitor system performance specifically the write hit latency and issue a custom event to alert you when the latency reaches a predefined limit The script can be scheduled to run automatically at specific intervals using the standard Windows Task Scheduler Example 7 51 WSH script to monitor write hit latency lt job id XIV_Latency Monitor gt lt script language JScript gt WSH Example for Custom Monitoring of an XIV Latency Performance Modify the following parameters with proper values var IPAddr 192 168 1 150 var Threshold 3000 var Severity Warning var Username admin var Password adminpass Main Script Starts Here var strValidChars 0123456789 var strChar var CmdString var Stringl var output var Exceeded 0 var xclicmd xcli m IPAddr u Username p Password var now new Date var EndDate now getYear now getMonth 1 now getDate 1 00 00 00 var Command statistics get count 1440 interval 1 resolution unit minute t write hit_medium_latency end EndDate CmdString xclicmd Command var WshShell WScript CreateObject WScript Shell var oExec WshShell Exec comspec d q oExec StdIn WriteLine prompt oExec StdIn WriteLine cd oExec StdIn WriteLine CmdString
41. 2621 9 13 61 6 87 20 4798 12 3 2 8 5 3 32 1 67 2 49 29 XIV 2812 7803760 IBM 1 FC_Port 6 1 500173800EB00160 27 09 11 11 13 PM 899 1739 3 870 05 2609 35 13 62 6 82 20 4453 12 4 8 6 3 32 1 66 2 49 30 XIV 2812 7803760 IBM 1 FC_Port 7 1 500173800EB00170 27 09 11 11 13 PM 899 1739 52 877 64 2617 16 13 62 6 85 20 4739 12 3 1 8 5 3 32 1 67 2 49 31 XIV 2812 7803760 IBM 1 FC_Port 8 1 500173800EB00180 27 09 11 11 13 PM 899 1738 06 875 22 2613 28 13 61 6 84 20 4429 12 3 1 8 5 3 32 1 66 2 49 32 XIV 2812 7803760 IBM 1 FC_Port 9 1 500173800EB00190 27 09 11 11 13 PM 899 1739 97 871 77 2611 74 13 62 6 84 20 4524 12 4 x 8 6 3 32 6 2 49 33 XIV 2812 7803760 IBM 1 FC_Port 4 1 500173800EB00140 27 09 11 11 28 PM 900 1737 46 870 49 2607 94 13 6 6 79 20 3911 12 3 1 8 6 3 32 te 2 48 34 XIV 2812 7803760 IBM 1 FC_Port 5 1 500173800EB00150 27 09 11 11 28 PM 900 1744 11 904 97 2649 08 13 63 6 96 20 595 12 2 1 8 4 3 32 1 69 25 Figure 6 30 Tivoli Storage Productivity Center data example The data filters can be used to easily find maximum values The spreadsheet can also be used to generate graphs In our Tivoli Storage Productivity Center data example in Figure 6 30 the following graphs are frequently helpful gt Total IOPS and total bandwidth gt Read IOPS and read response times If ports only a read is a Port send gt Write IOPS and write response times If ports only a write is a Port receive 6 4 Performance evaluation This section describes performance probl
42. 4e or higher is required on the second generation systems The mirroring setup and functionality are otherwise unchanged and fully supported between the two generations For details about the synchronous and asynchronous mirroring functions see the IBM Redbooks publication IBM XIV Storage System Copy Services and Migration SG24 7759 Chapter 1 IBM XIV Gen3 Storage System overview 7 1 6 The XIV Storage System software The XIV Storage System software Version 11 4 in conjunction with XIV Gen3 systems provides the functions of the system which include the following features gt Bundled advanced features All the features of the XIV Storage System including advanced features such as migration and mirroring are included at no additional charge and apply to the entire storage capacity gt Non Disruptive Code Load NDCL System software code can be upgraded without requiring downtime This feature enables non stop production environments to remain running while new code is upgraded The code upgrade is run on all modules in parallel and the process is fast enough to minimize the impact on host applications No data migration or rebuild processing is allowed during the upgrade Mirroring if any is suspended during the upgrade and automatically reactivated upon completion Storage management operations are also not allowed during the upgrade although the status of the system and upgrade progress can be queried It is
43. 5 1 XIV Storage System local credential repository 0 000 cee eee eee 186 5 5 2 Managing user accounts with the XIV Storage Management GUI 190 5 5 3 Security considerations when using Hyper Scale Manager 197 5 5 4 Managing user accounts using the XCLI 0 00 c cee ee 199 5 5 5 Password management and resets 0 000 eee ees 202 5 5 6 Managing multiple systemS 0 cc ee eens 203 5 6 LDAP based authentication 0 ee ete 206 5 6 1 Introduction to Lightweight Directory Access Protocol 206 5 6 2 LDAP directory components aaas cece ee eee ees 206 5 6 3 LDAP product selection 2 i aie cone wen een eels alan HS oR eee eS a eee 208 5 6 4 LDAP role mapping 02a ua cet wackwas ava ree eee da eed as Goan ake wees 208 5 7 Defining LDAP on the XIV Storage System 0 00 eee eee 212 5 7 1 Using the XIV Storage Management GUI LDAP wizard to configure LDAP 213 5 7 2 Using the XIV Storage Management GUI directly to configure LDAP 219 5 7 3 Using XIV Storage System Command Line Interface 222 5 8 LDAP managed user authentication 0 0c eee 223 5 8 1 LDAP repository credential objects 0 0 0 ees 224 5 8 2 Managing LDAP user accounts 0 00 c eee eee ee eens 228 5 8 3 Managing user groups using XCLI in LDAP authentication mode 234 5 8 4 Active Directory group membership and XIV role
44. 5 28 or right click in an empty area of the User Group table and select Add User Group from the menu as shown in Figure 5 28 Ungrouped Add User Add User Group Configure LDAP LDAP Wizard Export Figure 5 28 Add User Group 3 From the Add User Group window that opens enter a meaningful group name and click Add see Figure 5 29 Add User Group System XIV 7826153 x Name LDAP Role Full Access Figure 5 29 Enter new user group name LDAP role The LDAP Role field is not applicable to user group definition in native authentication mode and has no effect even if a value is entered If a user group has the Full Access flag turned on all members of that group have unrestricted access to all snapshots on the system At this stage the user group Application01 Group still has no members and no associations defined Next we create an association between a host and the user group 194 IBM XIV Storage System Architecture and Implementation 4 Right click the name of the user group that you created in order to open a menu and select Update Access Control as shown in Figure 5 30 ON Name OP Category Ungrouped Applica il ail 4 E Eill Edit Delete Update Access Control View Accesible Volumes Properties Sort By d Figure 5 30 Update Access Control for a user group The User Group Access Control window shown in Figure 5 31 opens The window contains t
45. 5 44 gt memberOf in the XIV Group Attribute field gt CN XIVAdmins CN Users DC itso DC storage DC ibm DC com in the Storage Admin Role field gt CN XIVReadonly CN Users DC itso DC storage DC ibm DC com in the Read Only Role field Click Update to save the changes General User ID Attribute sAMAccountName User Name Attribute x userFrincipalName LDAF Serwers XIV Group Attribute memberOf User Credentials Storage Admin Role CN xIVAdmins CN Users DCsitso DC st Read Only Role CN xlVReadonly CN Users DC zitso DC gt Role Mapping Secure LDAP Parameters Figure 5 44 LDAP definitions in XIV Storage Management GUI There is also an XIV Storage Management GUI wizard available to help you with configuring LDAP and role mappings See 5 7 Defining LDAP on the XIV Storage System on page 212 The XIV Storage System administrator informs the LDAP administrator that the XIVAdmin and XIVReadonly groups must be used for role mapping Tip When using role mapping using group memberships such as using the memberOf attribute with Active Directory you must specify the full DN string of the LDAP group name The LDAP server returns the full DN string back to the XIV Storage System during the authentication response and it must match the same path 210 IBM XIV Storage System Architecture and Implementation The LDAP administrator creates a user account in LDAP and assigns the user to the memberOf attribute When the newly
46. 6 2 3 Multipathing considerations XIV Storage System optimum performance is realized through the maximum use of the grid architecture This usage is the most important consideration to achieve maximum XIV Storage System performance Important When planning host connections to XIV Storage System it is important to ensure that all XIV Storage System Interface Modules are used For a detailed discussion about this topic see Chapter 1 Host connectivity in X V Storage System Host Attachment and Interoperability SG24 7904 For the purposes of this book we describe only Fibre Channel FC connectivity although the concepts are the same for both the 1 Gbps or the 10 Gbps iSCSI host connectivity The main multipathing goal from a performance perspective is for the host connectivity to create a balance of the I O workload across all of the resources in the XIV Storage System The best way to achieve this balance is by distributing the host physical connections evenly across all the Interface Modules Providing host I O access to every Interface Module from every host HBA has the following advantages gt Uses the most XIV Storage System cache gt Uses the most XIV Storage System processor capability to handle I O gt Fully uses the XIV Storage System grid architecture gt Minimizes the impact of a host interface hardware failure There are two main multipathing techniques The important point about both multipathing configurations
47. 7 2 XCLI All event commands Defines a Short Message Service SMS gateway 306 IBM XIV Storage System Architecture and Implementation smtpgw_define Defines an SMTP gateway etresan WTP gamwey Event_list command and parameters The following syntax is for the event_list command event_list max_events MaxEventsToList after TimeStamp before TimeStamp min_severity lt INFORMATIONAL WARNING MINOR MAJOR CRITICAL gt alerting lt yes no all gt cleared lt yes no all gt code EventCode object_type lt cons_group destgroup dest dm host map mirror pool rule smsgw smtpgw t arget volume cluster ip_interface 1ldap conf meta_ data object sync_schedule user us er_group 1dap_ server modules status elicense ipsec_connection ipsec_tunnel cross c ons _group gt internal lt yes no al1l gt beg BeginIndex end EndIndex count_all lt yes no gt XIV Storage System Command Line Interface examples To illustrate how the commands operate the event_list command displays the events currently in the system Example 7 21 shows the first few events logged in our system Example 7 21 XCLI viewing events C XIV gt xcli c XIV 6000050 event_list Timestamp Severity Code User Description 2011 10 04 17 00 38 Informational USER DEFINED admin A user with name itso _testuserl and category applicationadmin was defined 2011 10 04 17 01 05 Informational POOL_RENAME admin Storage Pool with name IT
48. 791 GB Figure 4 43 Storage Pools view Chapter 4 IBM XIV Storage Management software 137 The Storage Pools view displays a table of all the pools in the system with a series of gauges for each pool This view gives the administrator a quick grasp and general overview of essential information about the system pools The Storage Pools view can be customized allowing you to show or hide specific columns The Name and Usage columns are required The following optional column values are available Creator Hard Free Hard Total Lock Behavior Snapshots GB Snapshots Total Snapshots Used Soft Free Soft Total System Volumes Used M Vvvvvvrvrvvyvyiyv The capacity consumption by volumes and snapshots within a given storage pool is indicated by various colors The default threshold values are as follows M Blue indicates consumed capacity below 80 Yellow indicates capacity consumption above 80 Orange indicates capacity consumption of over 90 Red indicates that a storage pool has depleted hard capacity vy y The name the size and the separated segments are labeled appropriately In Figure 4 44 you can see an example of storage pool figures The figure depicts the following values for a storage pool gt Used Volumes Physical amount of data already written to the storage pool It is also the sum of space effectively consumed on each of the volumes in the pool gt Volumes Allocated Logical amount of s
49. 8K DBO 0P3 QOPETH 64 GPS QOEPTH 10 OPS QOEPTH 255 Increasing load expressed with threads Figure 6 5 Host side queue depth comparison Disclaimer Performance numbers in this example are valid only for this special test conducted at an IBM lab The numbers do not describe the general capabilities of an XIV Storage System as you might observe them in your environment The green line in the graph is the performance of a host with a queue depth set to 10 Where this line changes slope near 35 000 IOPS you can see the red line at around 44 000 IOPS The red line represents the same host configured with HBA queue depth settings of 64 The difference here at the widest margin is around a 25 boost in lIOPS just by changing the host queue depth setting from 10 to 64 The blue line shows the queue depth which is set to 256 Having the queue depth this high does not provide much of an advantage or disadvantage Higher queue depth in general yields better performance with XIV Storage System It is also important to consider the limitations per port on the XIV Storage System side For example each HBA port on an XIV Storage System Interface Module is designed to sustain up to 1400 concurrent I Os except for model A14 on port 3 when port 4 is defined as an initiator in which case port 3 is set to sustain up to 1000 concurrent I Os With a queue depth of 64 per host port one XIV Storage System port is limited to 21 concurrent host ports
50. AIV Maintenance amp xiv_msms Storage Administrator Figure 5 23 XIV Storage Management GUI users management 5 Change the default password for the admin user which can be accomplished by right clicking the user name and selecting Change Password from the menu as shown in Figure 5 24 You must be logged in as admin to change the admin password i gt cere e emma eel 0 Name Category Ungrouped A 4 M Storage Administrator amp technician Technician iv_development XIV Develo t i SE AE Change Password ee 4 xiv_hostprofiler XIV Host Profiler 4 xw maintenance Properties AIV Maintenance xiv_msms Storage Administrator Figure 5 24 XIV Storage Management GUI admin user change password 6 To add a user you can either click the Add User icon in the menu bar or right click the empty space to get the menu as shown in Figure 5 25 Click Add User A maximum of 128 users are possible in the regular XIV access control Ungrouped seein i 5 amp xiv_development xiv_hostprofiler xiv_maintenance Add User Group xiv_msms Configure LDAP LDAP Wizard Export Figure 5 25 XIV Storage Management GUI Add User option 192 IBM XIV Storage System Architecture and Implementation 7 The Add User window opens A user is defined by a unique name and a password see Figure 5 26 The default role denoted as Category in the window is Storage Administrator A category must be assigned Optionally enter th
51. Applicatiion Critical 20000 eo 5K OLTP Applicatiion 15000 5K OLTP Applicatiion Critical 10000 10K OLTP Applicatiion 5000 10K OLTP Applicatiion Critical Figure 6 6 QoS illustration IOPS The average I O response time in both shows similar behavior The largest response time RT was at the 1 K IOPS limit as shown in Figure 6 7 RT Six Interface Module OLTP Application vs OLTP Application IOPS Limit 1K 10K 300 300 250 250 200 200 ome K OLTP Applicatiion e 1K OLTP Application Critical 150 150 E 5K OLTP Applicatiion amp ome 5K OLTP Applicatiion Critical a Sp 10K OLTP Applicatiion 10K OLTP Applicatiion Critical 50 50 0 0 Elapsed Time Figure 6 7 QoS illustration response time RT Chapter 6 Performance 263 6 3 Performance monitoring During normal operation the XIV Storage System constantly gathers statistical information The data can then be processed using the XIV Storage Management GUI XIV Storage System Command Line Interface XCLI or IBM Tivoli Storage Productivity Center for Disk This section introduces the techniques for processing the statistics data 6 3 1 Using the XIV Storage Management GUI 264 The XIV Storage Management GUI provides a mechanism to gather statistics data For a description of setting up and using the XIV Storage Management GUI see Chapter 4 IBM
52. By Storage Subsystem gt Select a Storage Subsystem Disks branch is not possible Tivoli Storage Productivity Center does not report any volumes under the branch of a particular disk Also because the XIV Storage System storage pools are used to group volumes but not disks no disks are reported for a particular storage pool under that same reporting branch Finally the following reports do not contain any information for XIV Storage System subsystems gt Disk Manager Reporting gt Storage Subsystems Computer Views gt By Computer Relate Computers to Disks gt Disk Manager Reporting gt Storage Subsystems Computer Views gt By Computer Group Relate Computers to Disks gt Disk Manager Reporting gt Storage Subsystems Computer Views gt By Filesystem Logical Volume Relate Filesystems Logical Volumes to Disks gt Disk Manager Reporting gt Storage Subsystems Computer Views gt By Filesystem Group Relate Filesystems Logical Volumes to Disks 366 IBM XIV Storage System Architecture and Implementation gt Disk Manager Reporting Storage Subsystems Storage Subsystem Views gt Disks Relate Disks to Computers These queries when combined with the Small Computer System Interface SCSI inquiry data that Tivoli Storage Productivity Center collects from the hosts allow Tivoli Storage Productivity Center to correlate LUNs reported by the XIV Storage System to LUNs
53. CoD configuration always has one two or three de allocated CoD modules in the configuration There are several considerations for Model 114 and Model 214 CoD configurations gt The minimum CoD system configuration is six modules This configuration requires a minimum of three and a maximum of five CoD activation features between three and five modules are already purchased and between one and three modules are available for purchase gt The next valid CoD configuration is nine modules This configuration requires a minimum of six and a maximum of eight CoD activation features between six and eight modules are already purchased and between one and three modules are available for purchase gt Participation in the CoD program is valid if there are unactivated CoD modules in the system gt When activating allocating CoD modules ensure that there are remaining unactivated CoD modules in the configuration to continue your participation in the CoD program gt Any order that fully activates a CoD configuration and does not include additional unactivated CoD features indicates the client s desire to exit the CoD program 62 IBM XIV Storage System Architecture and Implementation gt There are explicit CoD term limits One year CoD term At the end of one year the system exits the CoD program and automatically activates all remaining unactivated and de allocated CoD modules generating client invoices for all of the rem
54. Connection panel which is shown in Figure 5 18 on page 185 184 IBM XIV Storage System Architecture and Implementation Add IPsec Connection Remote IP 9 155 113 144 Interface VPN Authentication method Passkey Certificate Certificate fig ktopiiTSOitsoCerificate pem E a aa caer Figure 5 18 Add IPSec Connection with certificate authentication In the Remote IP field enter the IP address of the remote workstation you will use to connect over IPSec Choose which XIV Storage System interface type on which you want to establish the IPSec connections The available choices are Management and VPN Select the radio button for the wanted authentication method e For Certificate authentication click Browse to select and upload your certificate file For more information about obtaining certificates see 5 2 1 Managing x509 certificates with the XIV Storage Management GUI on page 175 and Certificate authority setup on page 430 e For Passkey authentication enter the passkey to be used by the host to authenticate in the Passkey field as shown in Figure 5 19 Repeat the passkey in the Passkey Verify field Add IPsec Connection Remote IP 9 155 113 144 Interface vpn Authentication method Passkey O Certificate Passkey TTTTTTT Passkey Verify sescsees Figure 5 19 Add IPSec Connection with passkey authentication 3 Click Create to create the IPSec connection on th
55. DC xivhost1ldap DC storage DC tucson DC ibm DC com objectClass top objectClass person objectClass organizational Person objectClass user cn xivtestuserl description Storage Administrator distinguishedName CN xivtestuserl1 CN Users DC xivhostlldap DC storage DC tucs on DC ibm DC com instancelype 4 whenCreated 20090622172440 0Z whenChanged 20090622180134 0Z 404 IBM XIV Storage System Architecture and Implementation displayName xivtestuserl uSNCreated 98467 uSNChanged 98496 name xivtestuserl objectGUID apHajqyazEyALYHDAJrjNA userAccountControl 512 badPwdCount 0 codePage 0 countryCode 0 badPasswordlime 128901682350000000 lastLogoff 0 lastLogon 128901682415312500 pwdLastSet 128901672940468750 primaryGroupID 513 objectSid AQUAAAAAAAUVAAAAn59T xnd1I1skwvBQmdAQAAA accountExpires 9223372036854775807 logonCount 3 SAMAccountName xivtestuserl SAMAccountType 805306368 userPrincipalName xivtestuser1 xivhostlldap storage tucson ibm com objectCategory CN Person CN Schema CN Configuration DC xivhost1lldap DC storag e DC tucson DC ibm DC com The ldapsearch command syntax might appear overly complex and its output seems difficult to interpret However this output might be the easiest way to verify that the account was created as expected The I1dapsearch command can also be useful for troubleshooting purposes when you are unable to communicate with an Active Directory LDAP server
56. DELIVERY SUCCESSFUL gt gt event_list code CUSTOM EVENT Timestamp Severity Code User Description 2010 10 13 14 15 48 Informational CUSTOM EVENT itso User Initiated Backup Has Started Monitoring statistics The statistics monitor provides information about the performance and workload of the XIV Storage System There is flexibility in how you can visualize the statistics Options are selectable from a control pane at the bottom of the window as shown in Figure 7 17 Interfaces C Rea Oni C MemHit C 08 KB 64512 KB 3 IOPS Volumes ea C 8 64 KB C 512 KB Targets 0 All Figure 7 17 Filter pane for the statistics monitor For detailed information about performance monitoring see Chapter 6 Performance on page 247 Chapter 7 Monitoring 293 Monitoring UPS status with the XIV Storage Management GUI The XIV Storage Management GUI can be used to confirm if all three uninterruptible power supplies UPSs are currently operational If you hover your cursor over a UPS as shown in Figure 7 18 a window opens and shows the health status of that UPS and the Automatic Transfer Switch ATS The ATS generates system event messages if there are problems UPS 2 Charge Level 100 Test 3 13 13 Passed Input Power Yes Status OK NMC OK ATS J1 J2 ATS Status OK Figure 7 18 Monitoring UPS status Monitoring InfiniBand switches The XIV Storage Management GUI can be
57. Define a user using a unique name password and role designated here as category Example 5 3 XCLI user_define gt gt user_define user lab user password XIV R3 password_verify XIV R3 category applicationadmin Command executed successfully Defining user groups with the XCLI To define a user group complete the following steps ave Run user_group_ create as shown in Example 5 4 to create a user group called EXCHANGE CLUSTER 01 Example 5 4 XCLI user_group_create gt gt user_group create user group Application03 Mainz Command executed successfully Spaces Avoid spaces in user group names If spaces are required the group name must be placed between quotation marks such as name with spaces The Application03_Mainz user group is empty and has no associated host The next step is to associate a host or cluster Associate the application_Mainz user group to the Application_host01 host as shown in Example 5 5 Example 5 5 XCLI access_define gt gt access define user _group Application03 Mainz host Application_ host0l Command executed successfully A host has been assigned to the user group The user group does not have any users included Chapter 5 Security 201 3 Add the first user as shown in Example 5 6 Example 5 6 XCLI user_group_add_user gt gt user_group add user user _group Application03 Mainz user lab_user Command executed successfully The user lab_user has been assigned to the Applicat
58. Demo Mode can be accessed by selecting the Demo Mode option indicated by an arrow in the lower right corner of the display as shown in Figure 7 29 on page 310 Chapter 7 Monitoring 309 IBM XIV Mobile Dashboard Figure 7 29 IBM XIV Mobile Dashboard Demo Mode To log on to an actual XIV Storage System use a valid user password and IP address as shown in Figure 7 30 Figure 7 30 Logging on to an XIV Storage System from the IBM XIV Mobile Dashboard After you are connected to the XIV Storage System you can view volume performance or host performance Each window also shows the health and redundancy state of the XIV Storage System The iPad has a screen rotation capability therefore the output can be shown in either landscape or portrait mode The IBM XIV Mobile Dashboard behaves differently depending on which mode you use to show the output If you are having issues with screen rotation consult the following website http support apple com kb HT4085 310 IBM XIV Storage System Architecture and Implementation Volume performance Volume performance is shown when the iPad is in landscape mode as shown in Figure 7 31 From this window you can see up to 120 seconds worth of performance for the highlighted volume Use your finger to rotate the arrow on the blue volume icon to switch the display between IOPS bandwidth in megabytes per second MBps and latency in milliseconds ms The data redundancy state
59. Enabled Default k asimov_044 51 GB 0 GB mirror_pool Enabled Default BS Ey asimov_101 51 GB 0 GB mirror_pool Enabled Default Figure 4 76 SSD field on Volumes and Snapshots view IBM XIV Storage System Architecture and Implementation By default any newly created volume inherits the current system level cache setting System Level Settings gt If flash cache is disabled from System Level Settings it is disabled by default for every new volume defined gt lf flash cache is enabled from System Level Settings it is enabled by default for every new volume defined In the Volumes and Snapshots view shown in Figure 4 76 on page 168 right click a volume row and select Change SSD Caching State from the pop up menu You are presented a dialog box where you can change the status of the SSD Caching Figure 4 77 Change SSD Caching State Volume abby_10 Default Enabled Recommended tis recommended to use the default system 55D caching state To change this go to Menu Tools Settings System Parameters O Manual Enable Disable s p Figure 4 77 Change Volume SSD Caching State window The following information applies to the Change SSD Caching State window gt If the Default Enabled setting is selected the volume follows the current system settings gt You can override the Default by selecting Manual Then the volume no longer follows the current default system setting
60. Hardware Major tJ lt iDay XIV_02_ 13410114 Disk 4 Module amp status is Failed Hardware Major tJ lt 1 Day AIM_02_1340774 Disk 9 Module 6 status is Failed Hardware Major XR lt 1 Day AIW 02_1310114 Disk 1 Module 6 status is Failed Hardware Major se tJ lt 1 Day IW _02_1310114 Disk 7 Module amp status is Failed Hardware Major tJ lt 1 Day AIW 02_1310114 Disk 5 Module 6 status is Failed Hardware Major E tJ lt 1 Day AIW _02_1310114 Disk 3 Module amp status is Failed Hardware Major tJ lt 1 Day AIW 02_1310114 Disk 5 Module 9 status is Failed Hardware Major XN lt 1 Day AIW_O02 1310114 Remote Service Module 6 status is Fail Hardware Major E tJ lt iDay XIV_02_ 1340114 Disk 12 Module 3 status is Failed Hardware Major tJ lt i Day XIV_02_ 1310114 Disk 11 Module 8 status is Failed Hardware Major gt g tJ lt 1Day XIV_02_ 1310114 Disk 10 Module 3 status is Failed Hardware Major x lt 1 Da MIW OF 41340444 Module 8 status is Failed Hardware Maio Figure 7 8 Alerts window 7 1 3 Monitoring an individual XIV Storage System using the GUI You can access the Alerts Events and Statistics for the currently selected machine from the Monitor menu as shown in Figure 7 9 Alerts Events j Figure 7 9 GUI monitor functions Chapter 7 Monitoring 289 Monitoring the system Selecting System from the Monitor menu takes you to the System view which is shown in Figure 7 10 this view is also the default
61. Hyper Scale for the XIV Storage System REDP 5053 XIV can automate storage discovery and provisioning in OpenStack environments using OpenStack Cinder integration See the IBM Redpaper Using the IBM XIV Storage System in OpenStack Cloud Environments REDP 4971 XIV can automate custom storage operation using the new XIV RESTful API See the IBM Redpaper RESTful API Support in XIV REDP 5064 1 6 1 IBM XIV Storage Management tools The IBM XIV Management tools include the XIV Storage Management GUI IBM XIV online monitoring tool XIV Top and IBM XIV Storage System Command Line Interface XCLI Along with IBM XIV Management Tools Version 4 3 the IBM Hyper Scale Manager V1 4 was released The Hyper Scale Manager reduces operational complexity and enhances capacity planning through integrated management for large and multi site XIV deployments 10 IBM XIV Storage System Architecture and Implementation The Hyper Scale Manager deployment is running as a IBM Informix Virtual Appliance above an ESX server VMWare Hypervisor only The other XIV Management Tools GUI XIV Top and XCLI are available for various operating system platforms as listed in the following website http www 03 ibm com systems support storage ssic interoperability wss The Management Tools Host Attachment Kit HAK including the Multi System Manager can be downloaded from the following website http www ibm com support fixcentral The XIV Stora
62. IBM has released a Mobile Dashboard application that can be used to securely monitor the performance and health of your XIV Storage System This application is available for the Apple iPad either iPad 1 iPad 2 or the new iPad Installing the IBM XIV Mobile Dashboard for iPad You need an Apple iPad 1 iPad 2 or new iPad and a valid Apple ID to download the IBM XIV Mobile Dashboard application from the App Store It is a no charge application It can be found by searching the iTunes store as shown in Figure 7 28 or by going to the following website http itunes apple com us app ibm xiv mobi 1e dashboard id465595012 mt 8 App Store gt Business gt IBM Storage Free iPhone and iPad No Ratings Rated 4 2011 Copyright IBM Corp See other notices in the application s resource nard VE directory IBM XIV Mobile Dashboard Universal App IBM Storage gt Details Ratings and Reviews Related Screenshots iPhone iPad All systems Il systems All systems Volurrees chari vimi ima Frame Tim Last 2 Days Bandwidth Y This app is designed for both 5 B AN DWIOTH 586 6 mes demo system 2 Genertied erent 1597 for dima q aymer dame ayain 2 Critical Figure 7 28 IBM XIV Mobile Dashboard at the Apple Store Using the IBM XIV Mobile Dashboard When you start the IBM XIV Mobile Dashboard you have the choice to either run in Demo Mode or to connect to an actual XIV Storage System
63. In Figure 7 90 the properties of an XIV Storage System are shown in the Tivoli Storage Productivity Center GUI Storage Subsystem Details report EIGER ire Storage Subsystems XI 2810 7820119 IBM Details Administrative Services H Data Manager Label xr Fest Data Manager for Databases i Data Manager for Chargeback Status a Normal J Disk Manager endor IBM Bag torage Subsystems Type TM Storage Optimizer Model 114 SAN Planner i amp Monitoring Available Space GB 45 771 3 amp ilerting Consumed Space GB 9 455 56 _ Profile Management Configured Capacity Limit GB 55 226 36 Reporting Remaining Configured Capacity GB 30 610 36 H Fabric Manager l Tape Manager Serial Number 7020119 H Element Manager Revision 11 1 0 RC1 p201202135_ 094718 1 Replication Manager User defined property 1 UDP1 Figure 7 90 XIV Storage System details in the Tivoli Storage Productivity Center GUI The fields in Figure 7 90 show the following information Available Space GB The combined unused soft space inside all defined pools in GiB Consumed Space GB The combined size of all defined volumes and snapshot reserves in all pools in GiB Configured Capacity Limit GB The total of the hard size of all defined pools in GiB All of the hard space inside all of the pools Remaining Configured Capacity GB The total of the
64. Merory use Ee Minor Events lt H Security events lt H Storage events 4H test e Test Hardware Predictive Failure Alert events lt H Test IBM Director Agent offline aS Test Storage events oh Unknown Events B Warning Events sH Threshold Event Filter 4 Add to the Event Log a Define a Timed Alarm to Generate an E nce Define a Timed Alarm to Start a Progra g Log to Textual Log File Postto a News Group NNTP af Resend Modified Event Send an Alphanumeric Page via TAP Send an Event Message to a Console me Send an Internet SMTP E mail Ga Send an SNMP Inform to an IF Host S Send an SNMP Trap to a Netview Host EA Send an SNMP Trap to an IP Host Send a Numeric Page Gal send a TEC Eventto a TEC Server Set an Event System Variable Start a Program on a System Start a Program on the event System Start a Program on the Server Start a Task on the event System Update the Status ofthe ewent Syste Using IBM Systems Director Version 6 In this section we illustrate how to use IBM Systems Director Version 6 to monitor the IBM XIV Storage System If you are still using IBM Director see 7 5 Using IBM Director on page 342 for details To manage most storage systems with IBM Systems Director you must install a piece of management software from a third party It is required for all storage systems except IBM DS8000 XIV SAN Volume Controller and V7000 storage systems which can be managed directly
65. Open m c Browse with Paint Shop Pro 9 Zz j Open in new window Extract All 7 Zip uf Edit with Notepad Open with w LJ Extract Compressed Zipped Folders Share with Select a Destination and Extract Files Restore previous ve Files will be extracted to this folder cs HAK_xhop IBM_XIV_Host_Attachment_Kit_2 0 0 b1530_Windows x64_portable j Select a destination D Send to Select the place where you want to extract the selected item s Then dick the OK button So Libraries i grebman a ji Computer amp Local Disk C es DVD RW Drive D a st 3D10 xiv landisk itso ibm com Ra 4 amp 9 portHAK2 0 9 11 209 112 Z di HAK_2 0 0 Cance Si Network J Books_Docs J CSVs a To view subfolders dick the symbol next to a folder Make New Folder ee rra Figure 7 117 Portable HAK download and unpack Figure 7 117 shows how to download and extract the portable HAK to a network drive Any Windows server that is able to access that network drive is able to use HAK without any other software to install 392 IBM XIV Storage System Architecture and Implementation Extracting the file to a USB flash drive allows all servers that use the corresponding operating system to run HAK without any other software when the USB flash drive is connected The third option is to extract the file locally to the server or workstation and use it directly
66. Secure Shell SSH connection to XRSC either by the XIV Storage Management GUI or XCLI XRSC identifies the XIV Storage System and marks it as connected IBM Support connects to XRSC using SSH over the IBM intranet XRSC authenticates IBM Support against the IBM intranet XRSC then shows the connected client system available to IBM Support O oOo A W N IBM Support then chooses which system to support and connect to Only allowed IBM XIV systems are shown IBM Support logs the intended activity 7 A fully recorded support session starts 8 When complete IBM Support terminates the session and the XRSC disconnects the XIV Storage System array from the remote support system The XRSC Internet servers are hardcoded in XIV Storage System software and no further configuration is required by the client to enable this function aside from turning this feature on using the XIV Storage Management GUI or XCLI This service provides an expedient means for IBM Support to gather required information from the system in the most timely fashion and with the least impact to the client Modem connectivity The modem installed in the rack is optionally used for remote support if the preferred choice of XIV Remote Support Center is not used It enables the XIV System Storage Support Center specialists and if necessary a higher level of support to connect to the XIV Storage System Problem analysis and repair actions without a remote c
67. See wera de hea eh nas Mae die eee a a Oe Sees 393 Appendix A Thin provisioning conceptual examples 395 System level thin provisioning conceptual example 0 000 cee eee ee 396 Regular storage pool conceptual example nananana aa aa eee 397 Thinly provisioned storage pool conceptual example 0 000 cee eee eee 398 Appendix B Additional LDAP information 2 0000 cea 401 Creating user accounts in Microsoft Active Directory 00000 e ee eee 402 Creating user accounts in Sun Java Directory 0 000 eee 408 Securing LDAP communication with SSL 1 eee 416 Windows Server SSL configuration 0 000 ee eens 417 Sun Java Directory SSL configuration anaana cc ee eee 424 Cenilicate authority SCUp srecen he hoe eM outa Reese ght tre inte Bed 430 Related publications 6 2 one venga hae nae so oe Ba eat eae Bae ke ates paws 435 IBM Redbooks publications 2 000 te een nee 435 Oher PuUDICAIONS 420 4oc4us Be SnS Bake eee ddd Lee eae ede de lee eed aed 435 ONNE resou ES aime te 2 ocertee oi e a ase e a utd a ied De Ree alae EE A escle 435 How to get IBM Redbooks publications 0 0 00 ee 436 PEDT OMIEN ale haces Soon esas tee apse de ae al Sat aya hod eal Aenea tat a ch Guede a a tack sas Shem pete tee eens 436 Contents vii viii IBM XIV Storage System Architecture and Implementation Notices This information was develope
68. Static Group groupOfUniqueN ames Dynamic Group groupofUris Certificates Group groupOtCertific ates Entry Type Filtered Role nsFiltered RoleDefinition Domain Component domain Organizational Unit organizationalUnit Referral referral Class of Service cosPointerDefinition User defined Object Classes No user defined objectclass Figure B 6 Object class selection Cancel Enter the attribute values The first field Naming Attribute must remain uid XIV Storage System uses that attribute name for account identification We populate the mandatory attributes with values You can also choose to populate other optional attributes and store their values in the LDAP repository but XIV Storage System does not use those attributes See Figure B 7 on page 412 Appendix B Additional LDAP information 411 412 Required Attributes Allowed Attributes First Name givenname User ID uid Password userPassword Confirm Password E mail mail Telephone Number telephoneNumber Fax Humber Locality 1 Organization oa Organizational Unit ou audio businessCategory carLicen se departmentN umber description destination indicator Step 4 Configure Attributes Enter the attribute values for the new entry For multi valued attributes press the Enter key in the field to make the field taller and enter values on separate lines Naming Attribute User ID tui
69. Storage System hardware 4 1 1 XIV Storage Management software platforms 104 The XIV Storage Management software can be installed on Microsoft Windows Linux AIX HP UX Solaris OSX and iOS systems available from the iOS App Store The software serves aS a management console for the XIV Storage System The XIV Storage Management software is available for download at the following website http www ibm com support fixcentral From this website type 2810 in the Product selector and choose XIV Storage System 2810 2812 Then choose the latest version under Installed Version and your desired operating system under Platform Now click Continue as shown in Figure 4 1 setting started with Fix Central Select product Find product Type the product name to access a list of product choices When using the keyboard to navigate the page use the Tab or down i the results list Product selector sY Storage System 4610 2612 nstalled Version Platform indows Lz Continue Figure 4 1 Fix Central portal The Select fixes page is displayed Scroll down to the section labeled Management tools and select IBM_XIV_Management_Tools package For detailed information about XIV Storage Management software compatibility see the XIV interoperability matrix or the IBM System Storage Interoperation Center SSIC http www ibm com systems support storage config ssic index jsp IBM XIV Storage System Architecture and Implementati
70. TPC connections iSCSI sessions to provide higher throughput gt Provides more robust host connectivity during XIV hot upgrade Model 114 and Model 214 1 GbE There are up to 22 iSCSI ports available for iSCSI over IP Ethernet services The exact port count depends on the number of active Interface Modules See Figure 3 2 on page 61 for details about active Interface Modules These ports support 1 Gbps Ethernet network connection each These ports connect to the user s IP network through the XIV patch panel and provide connectivity to the iSCSI hosts See Figure 3 24 on page 85 for more details about the cabling of these ports You can operate iSCSI connections for various uses gt As an iSCSI target that attached hosts can connect to using the iSCSI protocol gt As an iSCSI initiator for remote mirroring when connected to another iSCSI port gt As an iSCSI initiator for data migration when connected to a iSCSI storage system from another vendor For each iSCSI IP interface you can define these configuration options gt IP address mandatory gt Network mask mandatory gt Default gateway optional The default and highest possible maximum transmission unit MTU is 4500 MTU With XIV software Version 11 2 or later this is changed to a default and maximum MTU of 9000 MTU IBM XIV Storage System Architecture and Implementation Model 214 10 GbE In Model 214 10 GbE slot 3 of the Interface Module is equipped w
71. The architecture can be scaled out by adding new modules to accommodate both new capacity and new performance demands The architecture can also be scaled up by adding more modules up to a total of 15 modules Chapter 2 IBM XIV Storage System logical architecture and concepts 21 Figure 2 3 shows an XIV Storage System scalable conceptual grid architecture Figure 2 3 XIV Storage System scalable conceptual grid architecture Proportional scalability Within the XIV Storage System each module contains all of the pertinent hardware elements that are necessary for a grid topology processing caching and storage All modules are connected through a scalable network This aspect of the grid infrastructure enables the relative proportions of cache processor disk and interconnect bandwidth to remain optimal even when modules are added or removed gt Linear cache growth The total system cache size and cache bandwidth increase linearly with disk capacity because every module is a self contained computing resource that houses its own cache The cache bandwidth scales linearly in terms of both host to cache and cache to disk throughput and the close proximity of cache processor and disk is maintained Cache Flash cache also increases linearly with total memory capacity Flash cache drives are not used to expand the disk capacity but rather to extend the memory capacity allocated to read I Os gt Proportional interf
72. To demonstrate how to interpret the values shown in Tivoli Storage Productivity Center see Figure 7 92 where an XIV Storage System pool called 7SO was created The hard size of the pool is 5016 GB and the soft size of the pool is 10015 GB shown in the XIV Storage Management GUI as 10 TB There is one volume in the pool sized at 1099 GB In that volume is 533 GB of actual data 10 TB Used Volumes of 11 TB Hard rmo R 10 TB Wolumes Allocated of 11 TB Soft Figure 7 92 ITSO pool shown in XIV Storage Management GUI In Figure 7 93 on page 365 the details of the ITSO pool are shown in the Tivoli Storage Productivity Center GUI 364 IBM XIV Storage System Architecture and Implementation Detail for Storage Pool ITSO Storage Subsystem aly Fest Type RAID 10 Status ie Storage Pool Space 10 27 TB Available Storage Pool Space 1 03 TB Configured Capacity Limit 10 27 TB Remaining Configured Capacity 961 538 GE Is Space Efficient true Is pool encryptable False Is pool encrypted False Solid State Non Solid State Easy Tier Easy Tier Status hy Sumber of Disks Sumber of Yolumes Surfaced Yolume Space Un surfaced Yolume Space Backend Yolume Space Figure 7 93 XIV Storage System ITSO storage pool details in Tivoli Storage Productivity Center GUI The values shown in Figure 7 92 on page 364 and Figure 7 93 correspond in the following way Storage Pool Space The soft size of t
73. To disable access repeat the same command with the mode Inactive option Chapter 5 Security 241 5 8 6 Managing multiple systems in LDAP authentication mode The task of managing multiple IBM XIV systems can be simplified by using LDAP authentication mode Because user credentials are stored centrally in the LDAP directory it is no longer necessary to synchronize user credentials among multiple IBM XIV systems After a user account is registered in LDAP multiple IBM XIV systems can use credentials stored in LDAP directory for authentication Because the user s password is stored in the LDAP directory all connected IBM XIV systems authenticate the user with this password If the password is changed all IBM XIV systems automatically accept the new password This mode of operation is often referred to as single sign on SSO Figure 5 78 This mode allows for quick transitions between systems in the XIV Storage Management GUI because the password is entered only once This approach is especially useful in Remote Mirror configurations where the storage administrator is required to frequently switch from source to target system LDAP Single Sign On LDAP protocol XCLI and GUI users LDAP protocol LDAP administrator Figure 5 78 LDAP single sign on Important To allow single sign on in LDAP authentication mode all IBM XIV systems must be configured to use the same set of LDAP configuration parameters for role
74. Tucson State Province st Arizona Country ic us 2 Specify as Subject DN Subject DN Figure B 13 Certificate request IBM XIV Storage System Architecture and Implementation 4 Copy the generated certificate shown in Figure B 14 Request into the xivhost2_cert_req pem file i Operation Completed Successfully The Request was successfully generated Generating the CA Signed Certificate Request for xivhost2 storage tucson ibm com 38 9 Done The request is Certificate request generated by Sun Java tm System Directory 6 0 Common Name xivhost2 storage tucson ibm com Email not specified Phone not specified Organization xivstorage State Arizona Country US BEGIN NEW CERTIFICATE REQUE 4ITBw 7 CCAScCAQAwf 7 ELMAKGAIUEBHMCVYMxEDAQBghVBAgT BOF yaxpybmExDzAh BghVBAcTBLRIYSNwb 7 ENMASGAIUEC MESVRIT ZETMBEGAIUECHMKeG L2csRycmFn ZTEQHCYGAIUEAsM Peal ZaG9zdDlucsRyvcmFn24550dWNzb24duaW tLmNvbT CE Cop BgkghkiG WwOBAQEFAAOB OAwg kCqY EAolxzk ay16NDTiLOWdMmQhreJTFy 9PY MBL BLyvtFItMLqvwGub haouH g2c8rEPLyHAHtvwthwut LWOJ 5Zry LP OEMS Es Select All SEMUZ1KWASMEQLZF dyllQ3gtATCisZZ1 IdPgQXw25wVQ1nfjJWssDN2sbkk YXPKGP53R MCAWEAAaAAMAGGCS qG ST b3DQEBBAUAAAGBATKxS13kWqIutw y PO eee eee Ore a tence Search Google for BEGIN NEW kwc69n 694nRXc81Rca999G6EgT ZOM7 eScF Int DKyExvemKLSYT fSwm5SKt 3 paa View Selection Source Finoa2p2enJd UaTayvyicobuu You must copy
75. Type LDAP Servers XWVUser Unique ID s Groups Secure LDAP Bind amp Cache Test amp Activation Finish Figure 5 53 XIV User tab Directory Services Service User Specify the user account name and its full DN Distinguished Name that will be used to authenticate the XIV system to the Directory Services you ve configured Service User DN CN XIV CN Users DC itsa Password SEER E Confirm Password ssssesss pa finish 216 IBM XIV Storage System Architecture and Implementation 12 In the Unique ID s tab set the parameters for the login See Figure 5 54 In our example the default selections are used The ID Attribute is set to sAMAccountName the Name Attribute to userPrincipalName and the Group Attribute to memberOf In Sun Oracle Directory environments for the Name Attribute use uid for Group Attribute in XIV Storage System use isMember Of LDAP Configuration Directory Services Unique Identifiers Directory Services Unique Identifiers a Welcome l Specify the Unique ID s that will be used to uniquely identify and authenticate Server Type the LDAP user Default recommended value have been applied here LDAP Servers AIV User Pear ER ID Attribute sAMAccountName Unique ID s Groups Name Attribute userPrincipalName Secure LDAP Group Attribute memberOf Bind amp Cache Test amp Activation Finish _ _ _ SSS im low F
76. XIV GUI to import the certificate into your XIV Storage System Click Systems gt System Settings gt Manage Certificates to open the Certificates Management panel In the panel click the Import Certificate icon as shown in Figure 5 5 on page 179 178 IBM XIV Storage System Architecture and Implementation Certificates Management Name Authenticate import Certificate pem p12 Close Figure 5 5 Import certificate PEM file 6 The Import Certificate window opens as shown in Figure 5 6 Import Certificate pem p12 Certificate pem p12 oOpiTSOlitsoCertificate pem Services All XCLI IPSec i CIM Name Password i Figure 5 6 Import signed certificate PEM file Click Browse to open a file browser window and select the signed certificate file In our example the signed certificate file is named itsoCertificate pem Click the corresponding check boxes to select the services that you would like to use this certificate for The following options are available All Use this certificate to secure all communications XCLI Use this certificate to secure XCLI communication only IPSec Use this certificate to secure IPSec traffic for more information about IPSec see 5 4 Configuring Internet Protocol Security connectivity on page 184 CIM Use this certificate to secure Common Information Model CIM agent communications on
77. a 34 GB LUN a 51 GB LUN and a 68 GB LUN The storage pool size is the total of all three LUNs which is 153 GB and about 40 of this storage is used gt Inthe thin pool the host system sees the same three LUN sizes and the total storage pool size is also 153 GB The difference is that the total space corresponding to unused portions of each LUN 34 GB 51 GB and 68 GB in the XIV is not dedicated to those three LUNs but remains available for other storage purposes When a storage pool is created using thin provisioning that pool is defined in terms of both a soft size and a hard size independently as opposed to a regular storage pool in which these sizes are by definition equivalent IBM XIV Storage System Architecture and Implementation ei l mil Regular Pool Figure 2 6 Regular pool versus thin pool Hard pool size Hard pool size is the maximum actual capacity that can be used by all the volumes and snapshots in the pool Thin provisioning of the storage pool maximizes capacity utilization in the context of a group of volumes where the aggregate host apparent or soft capacity assigned to all volumes surpasses the underlying physical or hard capacity allocated to them This utilization requires that the aggregate space available to be allocated to hosts within a thinly provisioned storage pool must be defined independently of the physical or hard space allocated within the syst
78. a specified LDAP directory to authenticate users whose credentials are maintained in the LDAP directory except for the admin technician maintenance and development users which remain locally administered and maintained The benefits of an LDAP based centralized user management can be substantial when considering the size and complexity of the overall IT environment Maintaining local user credentials repositories is relatively straightforward and convenient when dealing with only a few users and a few storage systems However as the number of users and interconnected systems grows the complexity of user account management rapidly increases and managing such an environment becomes a time consuming task In this section we review various benefits of this approach Although the benefits from using LDAP are significant you must also evaluate the considerable planning effort and complexity of deploying LDAP infrastructure if it is not already in place 5 6 1 Introduction to Lightweight Directory Access Protocol The Lightweight Directory Access Protocol LDAP is an open industry standard that defines a standard method for accessing and updating information in a directory A directory is a listing of information about objects arranged in an order that gives details about each object Common examples are a city telephone directory and a library card catalog In computer terms a directory is a specialized database also called a data reposito
79. all configuration and verification steps are completed the XIV Storage System is ready for the LDAP mode to be activated Appendix B Additional LDAP information 407 Creating user accounts in Sun Java Directory Creating an account in Sun Java Directory can be done in many ways using various LDAP clients We used the LDAP graphical user interface GUI client that is part of the Java System Directory Service Control Center web tool that is part of the Sun Java Directory Server product suite The designated description attribute must be populated with the predefined value in order for the authentication process to work From the Sun Java Directory LDAP Server perspective assigning a value to the description attribute is not mandatory and is not enforced by the server itself An LDAP server allows the creation of an account with no value assigned to the attribute However this attribute value is required by the XIV Storage System to establish LDAP role mapping This field must be populated with the predefined value in order for the authentication process to work To start the Sun Java System Directory Service Control Center point your browser to the IP address of your Sun Java Directory LDAP Server for a secure connection on port 6789 In our example we use the following URL to access the Sun Java System Directory Service Control Center https xivhost2 storage tucson ibm com 6789 Before the first user account can be created th
80. allows thick to thin provisioning of capacity Thin provisioned capacity is described in 2 4 Capacity allocation and thin provisioning on page 34 Because of the XIV pseudo random distribution of data the performance impact of data migration on production activity is minimized because the load is spread evenly over all resources gt Automatic and dynamic flash cache utilization for improved performance XIV supports one flash cache extension per module After the optional flash cache device is installed it must be present in all modules the XIV unique caching algorithm manages the flash cache as an extended read only cache to provide a performance boost for specific workloads No need for any specific consideration for flash cache utilization e No software e No decision e No tuning XIV allocates flash read cache space dynamically according to detected workload patterns XIV supports optional selective flash cache activation per logical volume host volume XIV supports nondisruptive online upgrade Flash caching For details about flash caching see 2 5 Flash caching architecture on page 40 or consult the Redpaper publication Solid State Drive Caching Implementation in the IBM XIV Storage System REDP 4842 gt Quality of service QoS The XIV disks and cache are shared at all times among all applications running on the various host servers attached to the XIV system As shown
81. also referred to as an entry in a directory belonging to an object class An object class describes the content and purpose of the object It also contains a list of attributes such as a telephone number or surname that can be defined in an object of that object class 206 IBM XIV Storage System Architecture and Implementation As shown in Figure 5 43 the object with the DN cn mbarlen ou Marketing o IBM belongs to object class objectClass ePerson Directory Root Top _ a ee ou Marketing cn mbarlen objectClass Person objectClass ePerson mail manon ibm com sn Barlen givenName Maron telephoneNumber 112 cn Klaus objectClass Person objectClass ePerson cn tbaren objectClass Person objectClass ePerson mail thomas acme com sn Barlen devicelD Pnntersales objectClass cimPrinter objectClass ePrinter location Printer room 3rd floor owner John Doe Quevename l sprn01 mail Kiebbe ibm com sn Tebbe MmaxCopies 10 Figure 5 43 Example of a Directory Information Tree DIT Object class ePerson contains the following attributes gt cn common name mail sn Surname givenName telephoneNumber YY vV Yy Each attribute has a value assigned to it cn mbarlen mail marion ibm com sn Barlen givenName Marion telephoneNumber 112 M vVvvvy In this example the object represents a single employee record If a record for a new employee in organizational unit ou Marketing of organization 0 IBM
82. and expertise As explained in 2 3 Full storage virtualization on page 24 the XIV Storage System uses true virtualization as one of the basic principles for its unique design With the XIV Storage System each volume is divided into 1 MB partitions and these partitions are distributed pseudo randomly and evenly and duplicated for protection The result is optimal distribution in and across all modules which means that for any volume the physical drive location and data placement are invisible to the user This method dramatically simplifies storage provisioning letting the system automatically lay out the user s volume in an optimal way This method offers complete virtualization without requiring preliminary volume layout planning or detailed and accurate stripe or block size pre calculation by the administrator All disks are equally used to maximize the I O performance and use all the processing power and all the bandwidth available in the storage system XIV Storage System virtualization incorporates an advanced snapshot mechanism with unique capabilities which enables the creation of a virtually unlimited number of point in time copies of any volume without incurring any performance penalties The concept of snapshots is described in detail in Product overview GA382 0791 and IBM XIV Storage System Copy Services and Migration SG24 7759 The Product overview is available for download from the IBM XIV Storage System Informatio
83. any impact or w danger for system operation Figure 7 15 Event severity IBM XIV Storage System Architecture and Implementation Event notification configuration The Events window offers a toolbar Figure 7 16 that contains a setup wizard with the ability to view and modify gateways destinations and rules The wizard can also modify the email addresses for the XIV Storage System and export the events to a comma delimited CSV file for use in an external spreadsheet program Figure 7 16 Event rules configuration Clicking the Setup icon starts the Events Configuration wizard which guides you through the process to create gateways add destinations and define rules for event notification For more information about event notification rules see Setup notification and rules with the GUI on page 316 In addition to the standard system generated events a storage administrator can generate a custom event with their own custom event description and wanted severity level using an XCLI command This command is useful when creating scripts to automate a process You can generate an informational event stating that a process has started or finished as shown in Example 7 1 Example 7 1 Using custom_event gt gt custom_event description User Initiated Backup Has Started severity INFORMATIONAL command 0 administrator command code SUCCESS status 0 status _str Command completed successfully aserver
84. as detailed before There is a performance monitoring summary window for monitoring overall IBM XIV System performance see Figure 7 33 and the ability to view specific performance measurements s ORANGE IBM XIV Mobile Dashboard demo ot po Z EDS demo G iS s OY f SS ae j gt f Ag J j L occo S A j gt BANDWIDTH a i A Ay J j py 7 8 Login f 761 9ms s Figure 7 33 iPhone login and system summary You can monitor IOPS bandwidth and latency by host and by volume see Figure 7 34 Bandwidth IOPS Demo7 __ Demo7 Demo server Demo volume1 B 4 Bandwidth 7 On 4 Figure 7 34 iPhone monitoring screens Chapter 7 Monitoring 313 7 1 12 Mobile Dashboard for Android The IBM XIV Mobile Dashboard is now available for Android It has similar functionality to the Apple iPad and iPhone versions The Demo Mode allows you to experience the available monitoring features without actually connecting to an IBM XIV System The mobile dashboard download is available at the following web page At the welcome screen either enter Demo Mode or add an XIV system In Figure 7 35 the login screen and Demo Mode are shown D a aa D D a a DF Di IBM XIV Mobile Dashboard IBM XIV Mobile Dashboard Exit Demo Mode 4 Username Password Se tO me Demo System 1 Full Redundancy Demo System 2 a Add System wl Add System Figure 7 35 XIV mobile dashboard f
85. bind establishing LDAP connection to work The rule also applies to configurations where the XIV Storage System is configured with only a single server on the Idap_list_servers list shown in Example B 6 Example B 6 Completing and verifying LDAP configuration on XIV xcli c ARCXIVJEMT1 user_id_attrib uid sess Command executed succes xcli c XIV MN00019 Name base_dn xiv_group_attrib third_expiration_event version user_id_attrib current_server use_ss session_cache_period second_expiration_event read_only_role u admin p s8cur8pwd Idap_ config set base_dn dc xivauth ion_cache_period 10 bind_time_limit 30 sfully u admin p s8cur8pwd ldap config get Value dc xivauth description 7 3 sid no 10 14 Read Only Appendix B Additional LDAP information 415 storage admin role Storage Administrator first _expiration event 30 bind time limit 30 To complete our description of the LDAP related configuration parameters at the XIV Storage System we describe the parameters that had default values assigned and did not need to be set explicitly version Version of LDAP protocol used the default is 3 This parameter must never be changed Both Active Directory and Sun Java Services Directory Server Enterprise Edition support LDAP protocol Version 3 user_id attrib LDAP attribute set to identify the user in addition to user name when recording user operations in the XIV Storage System event log
86. by the GUI Each graph is independent and can have separate filters Each of the multiple graphs can be unlocked to show a different time duration than the others Figure 6 14 on page 268 shows this multigraph concept The top graph is the IOPS for the day with separated reads and writes The second graph shows the bandwidth for a few minutes with separated reads and writes which provides quick and easy access to multiple views of the performance metrics Chapter 6 Performance 267 All Interfaces Read Write r T 70 00 72 00 iao 76 00 78 00 s000 ate OOOO Ere mea September 18 2013 September 19 2013 of All Interfaces Read Write Bandwidth MBps So hel soo T 150 D a ee e Too a a IE es _ 19 45 a So oo 55 ECET 10 05 70 70 q 25 20 30 10 35 TETE ETET oO 10 45 ECET ETY September 18 2013 September 19 2013 s _ Mem Hit 0 8 KB 64512 KB 2 IOPS Targets ORWw 3 HeM oO Bw Figure 6 14 Multiple graphs using the XIV Storage Management GUI 2 Day fats There are various additional filters available such as filtering by host volumes interfaces or targets These items are defined on the left side of the filter pane When clicking one of these filters a window opens Highlight the item or select a maximum of four by using the Ctrl key to be filtered and then select click to s
87. can search either by name only or by object type To start the search function click the magnifying glass in the upper right corner of any of the XIV Storage Management GUI windows as illustrated in Figure 4 33 Alternatively you can press Ctrl F to start the search function Snapshots GB aek Behave Read only 9 8 TB Hard 3 8 TB Soft Snapshots reserved 1 015 GB 25 5 TB Hard a lt e a A a Read only TB Wolumes allocated of 25 5 TB Soft 36 Snapshots reserved 516 GB 1 TB Hard Read only 1 TB Sof Snapshots reserved 103 GB 4 9 TB Hard pr k Read only 4 4 TE Soft Snapshots reserved 516 GB 516 GB Hard SN SS Read only 516 GB Soft Snapshots reserved 51 GB 516 GB Hard Read only 516 GB Soft 14 7 TB Hard Figure 4 33 Search in the GUI Chapter 4 IBM XIV Storage Management software 127 128 A Search panel opens as illustrated in Figure 4 34 Enter search text into the field to perform a search across all of the XIV systems managed by the GUI Results are displayed in a tree table view and clicking an item in the search results navigates to that item in the GUI The search results panel can be resized by clicking and dragging the lower right corner of the panel If the search results exceed the size of the panel a scroll bar is displayed at the right side of the panel 34 results found on all systems test ex_pool Apollo 1300474 es
88. click System Settings then click Manage Certificates as shown in Figure 4 22 For more details about certificate management see 5 2 x509 certificate validation and management on page 174 xiv XIV Storage Manageme n Actions View Tools Help ih lt lt p System Settings System Import Systems File LDAP Export Systems File IPsec Prererences Pool Alerts Thresholds Exit Support Modify IP Addresses Shutdown System Figure 4 22 Manage XIV system certificates Note The Manage Certificates menu option is not visible for XIV Systems running system software older than Version 11 2 gt In addition the GUI now supports the management of the trusted certificates used to secure its communication with IBM XIV systems To facilitate the import and management of trusted certificates in the GUI a new Certificates tab has been added to the Management view To access click the Tools portion of the menu bar click Management and then click the Certificates tab in the Management window as shown in Figure 4 23 For more information about the use of certificates see 5 2 x509 certificate validation and management on page 174 Management General Settings Regional Settings g Trusted Certificate Authorities in Local Trust Store Certificates g Other Trusted Certificates in Local Trust Store XIV Type 1 XIV Now 17 2007 Now 16 2008 7 XIV CA ibmXIVDisk ibmXIVDisk Nov 24 2012 Now
89. contains icons that indicate the port type iSCSI or FC for each port Chapter 4 IBM XIV Storage Management software 163 4 6 2 Assigning logical unit numbers to a host by using the XCLI 164 There are several required steps to define a new host and assign LUNs to it One of the prerequisites is that volumes are created in a storage pool Defining a new host To use the XCLI to define a new host complete the following steps 1 Create a host definition for your FC and iSCSI hosts by running host_define as shown in Example 4 10 Example 4 10 XCLI Session example Create host definition gt gt host_define host ITSO Win2008 Command executed successfully gt gt host_define host ITSO Win2008 iscsi Command executed successfully Host access to LUNs is granted depending on the host adapter ID For an FC connection the host adapter ID is the FC HBA WWPN For an iSCSI connection the host adapter ID is the IQN of the host 2 Add the WWPN of the FC host for HBA1 and HBA2 by running host_add_port with the fcaddress parameter as shown in Example 4 11 Example 4 11 Create FC port and add to host definition gt gt host_add_ port host ITSO Win2008 fcaddress 10000000C9831FA2 Command executed successfully gt gt host_add_port host ITSO Win2008 fcaddress 10000000C9831FA3 Command executed successfully 3 Add the IQN of the iSCSI host as shown in Example 4 12 This command is the same host_add_ port command but with the iscsi_n
90. created user logs in to the system IBM XIV systems perform the role mapping as shown in Figure 5 45 XIV System LDAP Server LDAP configuration Idap_config_set User definition xiv_group_attrib Member MemberOf cn X VAdmins storage_admin_role cn xX VAdmins attribute name attribute value compare strings on ngs match Assign user to storageadmin role Figure 5 45 Assigning an LDAP authenticated user to the storageadmin role LDAP role mapping for the applicationadmin role The LDAP account can also be assigned to an applicationadmin role but the mechanism of creating role mapping in this case differs from the one used for storageadmin and readonly role mapping The XIV Storage System assigns a user to the applicationadmin role if it can match the value of the MemberOf attribute with the 1dap_role parameter of any user groups defined in the XIV Storage System If an account is assigned the applicationadmin role it also becomes a member of the user group whose Idap_role parameter matches the value of the user s MemberOf attribute The user group must be created before the user logs in to the system or the login fails The XIV Storage System administrator creates a user group using the user_group create XCLI command as follows user_group create user _group app01 group Idap role cn app01_admins cn Users dc itso dc storage dn ibm dc com Chapter
91. devices must be installed in a modules Chapter 2 IBM XIV Storage System logical architecture and concepts 19 Data Modules At a conceptual level Data Modules function as the elementary building blocks of the system providing storage capacity processing power and caching in addition to advanced system managed services The Data Modules ability to share and manage system software and services are key elements of the physical architecture as shown in Figure 2 2 Architecture Figure 2 2 shows the conceptual architecture only Do not misinterpret the number of connections or modules and other representations as a precise hardware layout FC Ports iSCSI Management Ports Host Interface Interface Module Sw ina Dual EE i iy ziz a iiz gt m fp Tiz EAR E E Flash Flash mmo cary C1 om DF on ame moB A EEN e20 oo 2 aoe Data Mo dule a m o m m o m eoo e e e e o e e o e e E O E E M M M E E N N D a n n o o n n Interface and data modulesare connected each other through an internal switching network Figure 2 2 Architectural overview Interface Modules Interface Modules are equivalent to Data Modules in all aspects with the following exceptions gt In addition to disk cache and processing resources Interface Modules are designed to include both Fibre Channel and IP network Small Computer System Interface iSCSI interfaces for host system connectivity remote mirroring
92. disk initiated behavior such as spontaneous reset or unusually long latencies The system intelligently analyzes this information to reach crucial decisions concerning disk deactivation and phase out The parameters involved in these decisions allow for a sensitive analysis of the disk health and performance Redundancy supported reaction The XIV Storage System incorporates redundancy supported reaction which is the provision that uses the distributed redundant data scheme by intelligently redirecting reads to the secondary copies of data extending the system s tolerance of above average disk service time when accessing primary data locations The system reinstates reads from the primary data copy when the transient degradation of the disk service time has subsided A redundancy supported reaction itself might be triggered by an underlying potential disk error that is ultimately managed autonomically by the system according to the severity of the exposure as determined by ongoing disk monitoring Flexible handling of dirty data In a similar manner to the redundancy supported reaction for read activity the XIV Storage System can also make convenient use of its redundant architecture to consistently maintain write performance Because intensive write activity directed to any given volume is distributed across all modules and drives in the system and the cache is independently managed within each module the system is able to tolerate sustained
93. ele Kan i E y 2x2 AAN chant ho Rayer Ig Fam A e PANTS WANN NEA ere es REE a ba Vy pe oo Pa q 7 R 4 Oo Eee g AGAN ENG ENS z PG PTER eee 5 oie Ie ci E A VA ir oT DoE ais F a Total 1 109835 INRE tex Host ITSO Blade1l HS22 01 IOPS 109835 BW 53 6 Latency 1 9 Ms 120 sec 100 80 5 40 20 current ago time Hosts vIOPS BW MBps Latency ms ITSO_Blade1_HS22 01 109835 53 6 ee eee ITSO_HS22_blade4 0 0 0 0 6 ITSO_TS5220_02 0 0 0 0 0 ITSO_HS22_blade5 0 0 0 2 0 ITSO_Blade2 0 0 0 0 0 ITSO_Bladeg 0 0 0 0 0 garbage 0 0 0 0 0 Figure 7 32 IBM XIV Mobile Dashboard Host view If the IBM XIV Mobile Dashboard is operated in portrait mode by rotating your iPad a list of up to 27 hosts is displayed instead From either the Volume view or the Host window you can log off from the IBM XIV Mobile Dashboard by using the icon in the upper right corner of the display When you restart the application it recalls the IP address and user that were last used but not the password The password must be entered again 312 IBM XIV Storage System Architecture and Implementation 7 1 11 Mobile Dashboard for the Apple iPhone The IBM XIV System Mobile Dashboard is available for the Apple iPhone It has similar functionality to the previous Apple iPad version The demo mode allows you to experience the available monitoring features without actually connecting to an IBM XIV System The login sequence is the same
94. following topics 1 1 What s new in release 11 4 on page 2 1 2 Introduction on page 2 1 3 Total cost of ownership on page 3 1 4 XIV Gen3 Storage System models and components on page 4 1 5 XIV Gens key design features on page 6 1 6 The XIV Storage System software on page 8 1 7 Host support on page 14 YYYY YV Y Y Copyright IBM Corp 2013 All rights reserved 1 1 1 What s new in release 11 4 Release 11 4 of IBM XIV Storage System offers a range of new capabilities with the following features gt It helps secure information assets with industry standard encryption for data at rest using AES 256 bit keys using self encrypting 2 TB 3 TB 4 TB hard drives self encrypting drives SEDs without impacting performance XIV can nondisruptively encrypt volumes already populated with data in minutes XIV supports Key Management Interoperability Protocol KMIP Version 1 0 through IBM Tivoli Key Lifecycle Manager For details about encryption with XIV see the IBM Redpaper X V Security with Data at Rest Encryption REDP 5047 gt Quick start synchronous mirroring with offline initialization and flexible switching between synchronous and asynchronous mirroring gt Space can be dynamically reclaimed with VMware ESXi V5 5 and Microsoft Windows 2012 R2 space reclamation support gt The new IBM Storage Integration Server ISIS which allows for integration of multiple I
95. from there without installing the HAK If the drive or folder is mapped to the network other servers can use the HAK also 7 10 2 XIV Host Profiler The XIV Host Profiler xHoP is a tool that comes as a part of the XIV Host Attachment Kit The xHoP can be used to verify that connected hosts are running with the recommended driver and patch level Chapter 7 Monitoring 393 394 IBM XIV Storage System Architecture and Implementation Thin provisioning conceptual examples In this appendix we further explain thin provisioning principles by examining some basic examples These examples incorporate all of the concepts inherent to the IBM XIV Storage System implementation of thin provisioning This appendix covers the following topics gt System level thin provisioning conceptual example gt Regular storage pool conceptual example gt Thinly provisioned storage pool conceptual example Copyright IBM Corp 2013 All rights reserved 395 System level thin provisioning conceptual example Figure A 1 shows the incremental allocation of capacity to both a regular storage pool anda thinly provisioned storage pool within the context of the global system soft and hard sizes This example assumes that the soft system size has been defined to exceed its hard size The deallocated capacity shown within the system s soft and hard space is represented by a discontinuity to convey the full scope of both the logical and physical view of
96. get Name Value base dn CN Users DC itso DC storage DC i bm DC com Xiv_group_ attrib memberOf third expiration event 7 version 3 236 IBM XIV Storage System Architecture and Implementation user_id attrib objectSid current_server itso storage ibm com use ssl no session cache period 10 second expiration event 14 read only role CN XIVReadonly DC itso DC storage DC ibm DC com storage admin role CN XIVAdmins DC itso DC storage DC ibm DC com first_expiration event 30 bind time limit 30 gt gt user_group update user _group itso app01 group Idap_role cn XIVAppAdmin1 DC itso DC storage DC ibm DC com Command executed successfully gt gt user_group_list user_group itso_app01_ group Name Access All LDAP Role Users itso _app01 group no cn XIVAppAdmin1 DC itso DC storage DC i bm DC com Alternatively the same configuration steps can be accomplished by using the XIV Storage Management GUI To change the LDAP configuration settings using the XIV Storage Management GUI open the Tools menu at the top of the main XIV Storage Manager window click Configure gt LDAP Role Mapping and change the configuration parameter settings Now by assigning Active Directory group membership you can grant access to the XIV Storage System A user in Active Directory can be a member of multiple groups If this user is a member of more than one group with corresponding role mapping XIV fails authentication for this user beca
97. global reserved space includes sufficient capacity to withstand the failure of a full module plus three additional disk drives and still allow the system to create the necessary partition copies to return to full redundancy Tolerance of failures A fully used system tolerates multiple hardware failures including up to an entire module with three subsequent drive failures outside of the failed module If the system is less than 100 full it can sustain more subsequent failures based on the amount of unused disk space that is allocated in the event of failure as a spare capacity For a thorough discussion of how the system uses and manages reserve capacity under specific hardware failure scenarios see 2 6 Encryption for data at rest on page 42 Snapshots The IBM XIV Storage System does not manage a separate global reserved space for snapshots We explore this topic in Storage pool relationships and rules on page 32 Metadata and system reserve The system reserves roughly 4 of the physical capacity for statistics and traces and the distribution table Mirrored copies of data The mirrored copies of data are the secondary partitions described in Partitions on page 27 2 3 4 Storage pool concepts The concept of storage pools is purely administrative Although the hardware resources within the XIV Storage System are virtualized in a global sense the available capacity in the system can be administratively portioned into
98. group we run Idapsearch queries against the Active Directory LDAP server as shown in Example 5 18 Example 5 18 Active Directory group membership Idapsearch queries ldapsearch LLL H Idap 9 155 113 143 389 D cn itso cn Users dc itso dc storage dc ibm dc com w PasswOrd b cn Users dc itso dc storage dc ibm dc com cn itso_appuser1 member0f dn CN itso_appuser1 CN Users DC itso DC storage DC ibm DC com memberOf CN XIVReadonly CN Users DC itso DC storage DC ibm DC com Chapter 5 Security 235 ldapsearch LLL H Idap 9 155 113 143 389 D cn itso cn Users dc itso dc storage dc ibm dc com w PasswOrd b cn Users dc itso dc storage dc ibm dc com CN XIVReadonly dn CN XIVReadonly CN Users DC itso DC storage DC i bm DC com objectClass top objectClass group cn XIVReadonly member CN itso appuserl CN Users DC itso DC storage DC i1bm DC com member CN Almira CN Users DC itso DC storage DC ibm DC com member CN Administrator CN Users DC itso DC storage DC ibm DC com distinguishedName CN XIVReadonly CN Users DC itso DC storage DC ibm DC com instancelype 4 whenCreated 20110831113851 0Z whenChanged 20111004132323 0Z uSNCreated 12856 uSNChanged 41016 name XIVReadonly objectGUID g7 EDY9DALUSZ6fTBfGbkCw objectSid AQUAAAAAAAUVAAAAZaIKWj UHFDf 781VQQAAA SAMAccountName XIVReadonly SAMAccountType 268435456 grouplype 2147483646 objectCategory CN Group CN Schema CN Configuration DC itso DC storage DC
99. group to host association is provided in User group membership for LDAP users on page 227 gt readonly As the name implies users assigned to the readonly role can view only system information A typical use for the readonly role is a user responsible for monitoring system status system reporting and message logging who cannot be allowed to make changes on the system The assignment of the readonly role to an LDAP user is done through the LDAP role mapping process For a detailed description see 5 6 4 LDAP role mapping on page 208 Roles There is no capability to add new user roles or to modify predefined roles In LDAP authentication mode role assignment can be changed by modifying the LDAP attribute memberOf in our example LDAP authentication mode implements a user role mechanism as a form of role based access control RBAC Each predefined user role determines the level of system access and associated functions that a user is allowed to use RBAC The XIV Storage System implements RBAC based authentication and authorization mechanisms All user accounts must be assigned to a single user role Any LDAP user that is assigned to multiple roles will not be authenticated by the XIV Storage System Deleting role assignment by removing the description attribute value in the LDAP object of LDAP users also leads to the inability of the XIV Storage System to authenticate that user 226 IBM XIV Storage System Architectur
100. groups Y VvV vy 7y Only users assigned to the storageadmin role can modify the 1dap_role parameter of a user group Important A user group membership can be defined only for users assigned to the applicationadmin role Chapter 5 Security 227 Figure 5 69 shows the relationship between LDAP user LDAP role XIV Storage System role user group membership associated host mapped volumes and attached snapshots XIV System LDAP Server LDAP configuration ldap_ config_ set User definition MemberOf cn app01_admins attribute name attribute value xiv_ group_ attrib MemberOf User group definition Name app01_ group Ldap_ role cn app01_admins compare strings String matching is done by XIV system Single match group mapping successful Multiple or no matches group mapping failed Assign user to applicationadmin role user becomes member ofapp01_ group group app01_ group associated with host app 01_ host aCCeSs _ define XCLI command creates association between user groupapp01_ group and a host app01_ host ccess q definition host app01_ host map _ vol XCLI command maps volumes app01_vol01 and app01_vol02 to app01_ host host mapping Volumes volume mapped volume app01_vol01 to host app01_ vol02 app01__ administrator user is authorized for snapshot managing snapshots app01
101. gt XiVIFIOPS 1005 gt XiVIFIOPS 1006 gt XiVIFIOPS 1007 gt XiVIFIOPS 1008 gt XiVIFIOPS 1009 gt xivIfStatus xivIfStatus xivI fStatus xivIfStatus gt xivIfStatus gt xivIfStatus INTEGER 0 Gauge32 69 Gauge32 90 INTEGER 49770 INTEGER 7954 6519 6773 6515 6557 6517 6575 OK OK OK OK OK OK sks Gauge32 Gauge32 Gauge32 Gauge32 Gauge32 Gauge32 1004 STRING 1005 STRING 1006 STRING 1007 STRING 1008 STRING 1009 STRING The following fields are shown in Example 7 44 xivMachineStatus xivFailedDisks xivUtilizationSoft xivUtilizationHard XivFreeSpaceSoft XivFreeSpaceHard xivIFIOPS 1004 xivIfIOPS 1005 XivIFIOPS 1006 XivIfFIOPS 1007 XivIFIOPS 1008 xivIfIOPS 1009 xivifStatus xivifStatus xivIfStatus xivifStatus xivifStatus xivIfStatus 1004 1005 1006 1007 1008 1009 Shows if a disk rebuild or redistribution is occurring The number of failed disks in the XIV Storage System The percentage of total soft space that is allocated to pools The percentage of total hard space that is allocated to pools The amount of soft space that is deallocated in GB The amount of hard space that is deallocated in GB The number of IOPS being executed by module 4 at that moment The number of IOPS being executed by module 5 at that moment The number of IOPS being executed by module 6 at that moment The number of IOPS being executed by module 7 at t
102. hit medium latency threshold is exceeded You can see the custom event in the XIV Storage System event log as shown in Figure 7 105 An event notification rule can be defined based on severity or the CUSTOM_EVENT event code to send an email or SNMP message as described in 7 1 10 Monitoring using the IBM XIV Mobile Dashboard on page 309 Event Properties x Severity Warning Date 2010 10 19 16 14 47 Index 4505380 Event Code CUSTOM_EVENT T Shooting Description Medium Latency exceeded threshold of 3000 during 24 hour period ending 2010 10 18 00 00 00 Figure 7 105 A custom event generated by WSH script by using XCLI 7 8 3 Conclusion These simple examples are just a small subset of what can be accomplished by combining the power of XCLI commands with the flexibility of scripting By using the output from multiple commands or multiple fields it is possible to monitor any combination of components or parameters of the system and act upon them based on criteria that you define Similar results can be accomplished on UNIX based platforms by using shell scripting and crontab for scheduling custom monitoring processes Chapter 7 Monitoring 377 7 9 Microsoft System Center Operations Manager Microsoft System Center Operations Manager SCOM is the Microsoft end to end service management product From a single interface you can verify the state health and performance of your Windows servers certain UNIX based com
103. in Figure 7 48 If there are problems the remote specialist is able to analyze problems and also assist an IBM SSR dispatched onsite in repairing the system or in replacing field replaceable units FRUs To enable remote support you must allow an external connection such as either one of the following methods gt A telephone line gt An Internet connection through your firewall that allows IBM to use a Secure Shell SSH connection to your XIV Storage System XRSC connection The XRSC uses a high speed Internet connection but it gives the client the ability to initiate an outbound SSH call to a secure IBM server Firewall rules might need to be configured at the client firewall to allow the XIV Storage System VPN Management ports to connect to the XRSC Tip The type of access required for a remote support connection is outbound port 22 ssh from the XIV Storage System network ports 326 IBM XIV Storage System Architecture and Implementation The XRSC consists of the XIV Storage Server s internal functionality together with a set of globally deployed supporting servers to provide secure IBM support access to the XIV Storage System when necessary and when authorized by the client personnel Objectives and components The XRSC is designed to meet three major objectives gt Security from malicious attack The XRSC was designed with security as a major concern while keeping the system architecture simple and easy to depl
104. in Figure B 19 on page 428 Appendix B Additional LDAP information 427 Directory Servers gt xivhost2 storage tucson ibm com 389 Server Operation Suffixes Entry Management Schema Security ServerConfiguration Seneral Certificates CA Certificates xivhost2 storage tucson ibm com 389 Security SSL Settings SSL Encryption Enabled Configure LDAP Secure Port Configure DSML Secure Port Certificate Default Certificate Default Certificate Cipher Family xivstorage oang sample CA certificate Security Device Internal software Client Authentication LDAP Settings Allow Certificate Based Client authentication DSML Settings Try to use client certificate first Figure B 19 New signed certificate activation As shown in Figure B 20 you are prompted to restart the LDAP server in order for the new certificate to take effect A Restart Required You have modified the Certificate used by the Directory Server You must restart the Directory Server in order this modification to ke taken into account Note Once the Java TM Web Console session has ended this message wil disappear Figure B 20 Manual restart request after activating new certificate 428 Low level SSL validation using the openssl command The easiest way to test the low level SSL connection to the LDAP server is by running the openssl s_client command with the showcerts opt
105. in the Tiles view Cleared systems are hidden in this view Tip To show or hide systems in the Tiles view use the System Selector menu as shown in Figure 4 27 on page 124 The List view as seen in Figure 4 31 displays the details of the selected systems in tabular format The listed systems can be sorted by any column Click a column header to sort by that column Click that header again to toggle between ascending and descending order Right click a column header to customize which column header values are shown or hidden The Name Group and Status columns are required The following optional columns are available IOPS Hard Size Hard Used Hardware Type Hosts Soft Size Soft Used Utilization Version Volumes Vvvvvvrvrvrvyvyiyv Double click any system row to navigate to the System view for that system AN Systems 9 gt Redbook2073 3 XIV 6001546 Stockholm Briefing C KIV 1300208 LBS Tucson XIV PFE3_ 7804143 Ungrouped Systems XIV LAB 01 6000105 Ungrouped Systems 9 155 50 182 Ungrouped Systems Figure 4 31 All Systems List view 9 Systems 4 Groups 4 Disconnected Connection Error Full Redundancy Full Redundancy Connection Error Connection Error Note When one or more systems are selected in the List view the selected rows are highlighted in orange Tip From any of the Systems views you can select multiple systems by holding the Ctrl key while clicking each system While one o
106. inherently handled by all resources It harnesses all storage capacity all internal bandwidth and all processing power currently available in the system Logical volumes are not exclusively associated with a subset of physical resources e Logical volumes can be dynamically resized e Logical volumes can be thinly provisioned as described in 2 4 Capacity allocation and thin provisioning on page 34 gt Consistent performance and scalability Hardware resources are always used equally because all logical volumes always span all physical resources and are therefore able to reap the performance potential of the full system and maintain data integrity e Virtualization algorithms automatically redistribute the logical volumes data and workload when new hardware is added maintaining the system balance while preserving transparency to the attached hosts e If there is a hardware failure data is automatically efficiently and rapidly rebuilt across all the drives and modules in the system This action preserves host transparency equilibrium and data redundancy at all times while virtually eliminating any performance penalty associated with traditional RAID rebuilds This rebuild action works together with the same redistribution activity as when hardware is added There are no pockets of capacity orphaned disk space or resources that are inaccessible because of array mapping constraints or data placement
107. is Open Ldap using the Idap_config_ set XCLI command as follows Idap_config set server _type Open Ldap This command also automatically sets both the user_id_ attrib and user_name_ attrib values to uid Then the xiv_group_attrib configuration value is changed to a description as follows ldap_config_ set xiv_group attrib description The role names must be set to reflect the storageadmin and readonly roles Because there are no group mappings they do not need to have the full DN path as when using group membership Instead we need to only use XIVAdmins and XIVReadonly values for each role as follows gt Idap_config set storage _admin_role XIVAdmins gt Idap_config set read_ only role XIVReadonly The LDAP service user and password must be defined This user is a user that needs no specific permissions within the directory and is only used to view the directory schema Run the following command Idap_config set xiv_user UID XIV 0U Users DC itso DC storage DC i bm DC com Xiv_password PasswOrd Then the LDAP server instance must be defined using the Idap_add_server command as follows Idap_add server fqdn itso storage ibm com port 389 address 9 155 113 137 base _dn QU Users DC itso DC storage DC ibm DC com In Example 5 23 we apply these changes to allow the OpenLDAP connection using the XCLI You must be logged in to the XCLI as the admin user Example 5 23 Configuring XIV Stora
108. is repaired by trained IBM service personnel either remotely with the help of the XRSC or on site by an IBM SSR When problems arise a remote support specialist can connect to the system to analyze the problem repair it remotely if possible or assist the IBM SSR who is onsite Remote support has three ways to connect the system Depending on the client s choice the support specialist can connect by one of the following methods gt Using a modem dial up connection through an analog phone line provided by the client gt Using a secure high speed direct connection through the Internet to the XIV Storage System gt Using the XRSC which allows the client to initiate a secure connection from the XIV Storage System to IBM Using XRSC the XIV Storage System makes a connection to an external XRSC server Using an internal XRSC server the XRSC can connect to the XIV Storage System through the connection made to the external server For more details see Figure 7 48 on page 326 Chapter 7 Monitoring 325 Remote Support Options IBM XIV Storage System External XRSC server Client IBM XRSC Firewall Firewall server EE EE Remote Support Center Internet Direct Op tional Proxy Server Dial up connection PHONE LINE Figure 7 48 Remote support connections XRSC We encourage all clients to use the secure high speed remote support solution enabled by the XRSC These possibilities are shown
109. it has nothing to do with performance XIV Storage System data redistribution is carried out automatically No user intervention is necessary or even possible Chapter 6 Performance 253 6 1 5 Snapshots The performance penalty during an XIV Storage System snapshot is nearly invisible to the I O characteristics of production application workload Snapshots complete near instantly within the XIV Storage System When a snapshot is issued no data is copied The snapshot creates system pointers to the original data As the host writes modified data in the master volume the XIV Storage System redirects the write data to a new partition Only the data that was modified by the host is copied into the new partition which prevents moving the data multiple times and simplifies the internal management of the data See IBM XIV Storage System Copy Services and Migration SG24 7759 for details about how the snapshot function is implemented 6 2 Best practices for optimum performance There are several best practices that can have a positive impact on XIV Storage System performance Important XIV is architecturally designed to support real world client production environments Real world production environments involve multiple application servers making multiple simultaneous I O demands on storage systems When clients decide to purchase the XIV Storage System they have the reasonable expectation that they will migrate existing applications or inst
110. mapping 234 5 8 5 OpenLDAP Directory and XIV Storage System role mapping 238 5 8 6 Managing multiple systems in LDAP authentication mode 242 5 9 Securing LDAP communication with Secure Sockets Layer 243 5 9 1 Configuring XIV to use LDAP over Secure Sockets Layer 243 5 9 2 Maintaining the SSL certificate 0 nanna aaa aa 245 Chapter G Performante occisa cane u ayes oat ence tome a na eens 247 6 1 XIV Storage System software and hardware architecture 045 248 6 1 1 Workload distribution and load balancing 0 0 eee eee 248 6 122 Grid ACME CURE ee sate ald Se Se ete Bc ae a eed Ss pe B dv adie dh ee otk we 250 6 1 3 Caching mechanisms 0 00 cc eee eee ees 251 6 1 4 Data redistribution effects on host systems 0 0000 cee ees 252 6 1 5 oMapSNOlss 2224 445 shou beacons bebe Ge ohne kee ees bates Heo ae Eo ete 254 6 2 Best practices for optimum performance 0000s 254 62 OZN aad cae ahaa 9 Ears OnE ah od Rea enee es aha GR eee 2 254 6 2 2 Number of logical unit numbers 0 0 ees 255 6 2 3 Multipathing considerations 0 00 ees 257 6 2 4 Host considerations duis este eta et ete enw eee cee ore St ee eee 258 6 2 5 Quality OF SCIVICE 2524 eo one de ba aaa dad eat oF and Eaa a aor awa 261 6 3 Fenormance MOMMONIAG sairat he geht hw ae ed toca Ree nee ak te ah es ew Sa 264 6 3 1 Using t
111. mapping If role mapping is set up differently on any two IBM XIV systems it is possible that a user can log in to one but not the other XIV Storage System 242 IBM XIV Storage System Architecture and Implementation 5 9 Securing LDAP communication with Secure Sockets Layer In any authentication scenario information is exchanged between the LDAP server and XIV Storage System where access is being sought Secure Sockets Layer SSL can be used to implement secure communications between the LDAP client and server LDAP over SSL LDAPS the secure version of the LDAP protocol allows secure communications between the XIV Storage System and LDAP server with encrypted SSL connections This protocol allows a setup where user passwords never appear on the wire in clear text SSL provides methods for establishing identity using X 509 certificates and ensuring message privacy and integrity using encryption To create an SSL connection the LDAP server must have a digital certificate signed by a trusted certificate authority CA Companies have the choice of using a trusted CA from another vendor or creating their own certificate authority In this scenario the itso storage iom com CA is used for demonstration purposes 5 9 1 Configuring XIV to use LDAP over Secure Sockets Layer To be operational SSL must be configured on both the client XIV Storage System and the server LDAP server Server configuration includes generating a certificate reque
112. needs to be created the same location in DIT is the same ou Marketing o IBM Additionally the same set of attributes defined by objectClass ePerson are also used The new object is defined using its own set of attribute values because the new employee will have their own name email address phone number and so on For more information about the directory components see Understanding LDAP Design and Implementation SG24 4986 All the objects and attributes with their characteristics are defined in a schema The schema specifies what can be stored in the directory Chapter 5 Security 207 5 6 3 LDAP product selection LDAP authentication for Version 10 2 x or 11 x of the XIV Storage System supports three LDAP server products gt Microsoft Active Directory gt Sun Java System Directory now called Oracle Directory Server Enterprise Edition gt OpenLDAP The current skill set of your IT staff is always an important consideration when choosing any products for centralized user authentication If you have skills in running a particular directory server it might be a wise choice to standardize on this server because your skilled people will best be able to customize and tune the server Your experts will be able to provide the most reliable and highly available implementation for the LDAP infrastructure Microsoft Active Directory might be a better choice for an enterprise with most of its infrastructure components deployed using M
113. not identified Summary of Changes for SG24 7659 07 for IBM XIV Storage System Architecture and Implementation as created or updated on December 18 2013 December 2013 Eighth Edition This revision reflects the addition deletion or modification of new and changed information described below New information gt XIV Gens Release 3 4 hardware gt XIV Storage System software Version 11 4 gt Examples and illustrations reflect XIV Storage Management GUI V4 2 Changed information gt Moved IBM Hyper Scale Manager formerly known as Multi System Management to a separate IBM Redpaper publication IBM Hyper Scale in XIV Storage REDP 5053 gt Various updates for XIV software Version 11 4 gt IBM XIV Gens latest hardware Copyright IBM Corp 2013 All rights reserved XV xvi IBM XIV Storage System Architecture and Implementation IBM XIV Gens Storage System overview The IBM XIV Gen3 Storage System is a high end fully scalable enterprise disk storage system that is based on a grid of standard off the shelf hardware components Its outstanding virtualized grid design allows massive parallelism with balanced paths processors caches and disks with virtually no possibility for hotspots It is designed with an easy to use and intuitive graphical user interface GUI that allows storage administrators to become productive in a short time This chapter provides a high level overview of the XIV Storage System It covers the
114. not authenticate that user 4 Complete the account creation by clicking Next Finish Appendix B Additional LDAP information 403 5 Populate the Description field with a predefined value for the XIV Storage System category role mapping by selecting the xivtestuserl user name right clicking it and clicking Properties Figure B 3 Hi testuserl Properties El Member Of Dial in Environment Sessions Remote control Terminal Services Profile COM General Address Account Profile Telephones Organization sivtestuser First name fo Initials fe Last name FO Display name Jxivtestusert Description Storage Administrata Office Po Telephone number Other E mail Web page Other cad sso Figure B 3 Entering a predefined value into the Description field Complete the account information update by clicking OK After the user account is created in Active Directory its accessibility can be verified from any of the available LDAP clients In our case we used the OpenLDAP client as shown in Example B 1 Example B 1 Active Directory account verification using OpenLDAP client ldapsearch x H Idap xivhost1l xivhostlldap storage tucson ibm com 389 D CN xivtestuserl1 CN Users DC xivhost1ldap DC storage DC tucson DC ibm DC com w pass2remember b CN Users DC xivhost1ldap DC storage DC tucson DC ibm DC com cn xivtestuserl dn CN xivtestuserl CN Users
115. optimum performance It takes care of these tasks automatically 2 1 2 Hardware elements To convey the conceptual principles that make up the XIV Storage System architecture it is useful to first look at the physical design The IBM XIV Storage System configuration includes Data Modules Interface Modules interconnect switches and uninterruptible power supply UPS units For details and components of the physical system architecture see Chapter 3 IBM XIV architecture components and planning on page 57 Modules The primary components of the XIV Storage System are known as modules Modules provide processing cache including an optional flash cache and host interfaces They are composed of off the shelf systems that are based on Intel 18 IBM XIV Storage System Architecture and Implementation The modules are redundantly connected to one another through an internal switched network as shown in Figure 2 1 All of the modules work together concurrently as elements of a grid architecture so the system harnesses the powerful parallelism inherent in such a Distributed Computing Environment We describe the grid architecture in 2 2 Parallelism on page 21 Interface Modules Interface Modules s UPS Units Figure 2 1 XIV Storage System major hardware elements Important Flash cache is an optional feature However if you opt for the flash cache extension flash cache
116. performance requirements of the new application all that is required is to create new LUNs and assign them to the host If however the XIV system was to be used to the maximum of the performance that it can deliver you can use the quality of service QoS feature to ensure that your business critical applications are served in priority with adequate performance from an input output operations per second IOPS and bandwidth standpoint for details see Quality of Service on page 129 Because of the XIV Storage System grid architecture the XIV Storage System actually works more efficiently as multiple application servers are attached The XIV Storage System evenly distributes the production workload over the performance resources of the multiple XIV Storage System Interface Modules and therefore the entire XIV Storage System grid architecture 6 1 2 Grid architecture Each XIV Storage System module contains disk drives that contribute to the data storage Capacity and performance capacity of the XIV Storage System configuration If there is enough available performance capacity within the XIV Storage System to handle the new application s performance requirements the only configuration activity required is to create new LUNs This situation assumes that there is also enough available data storage capacity But what are the considerations if the XIV Storage System does not have additional performance capacity to take on more applications
117. physical architectural design of the system including off the shelf modules network switches and power components new technologies can be adopted easily The IBM XIV Gen3 Storage System provides fully virtualized storage that is designed to eliminate the need for performance tuning planning for capacity and performance growth and numerous other storage management activities The highly intuitive XIV GUI and built in management tools make administrative tasks easy and efficient with little training or expertise required from provisioning volumes to monitoring multiple systems A powerful command line interface CLI supports complex scripting The unified console enables one stop centralized administration of multiple XIV systems Its exceptional flexibility extends to mobile devices giving users the flexibility of performance and capacity monitoring by the IBM XIV Mobile Dashboard supporting the Apple iPhone and Apple iPad and Android devices These design points provide the following benefits gt Reduced total cost of ownership TCO gt Flexibility to meet changing business needs gt Consolidated and virtualized data storage gt High availability and performance characteristics 1 3 Total cost of ownership The total cost of ownership TCO calculation for traditional enterprise storage systems usually includes the following costs gt Cost of initial purchase Cost of subsequent upgrades Cost of hardware and software m
118. roles their level of access and applicable use gt storageadmin The storageadmin Storage Administrator role is the user role with highest level of access available on the system A user assigned to this role can perform changes on any system resource except for maintenance of physical components changing the status of physical components or effecting changes related to encryption gt applicationadmin The applicationadmin Application Administrator role is designed to provide flexible access control over volume snapshots A user assigned to the applicationadmin role can create snapshots of volumes perform mapping of their own snapshots to assigned hosts and delete their own snapshots The user group to which an application administrator belongs determines the hosts and their respective set of mapped volumes that the application administrator is allowed to manage If a user group is defined with access _all yes application administrators who are members of that group can manage all volumes on the system For more details about user group membership and group to host association see User groups on page 189 gt securityadmin The securityadmin Security Administrator role is new with the 11 4 code release and manages certificates key servers and other items related to encryption Defining at least two security administrators is a must because that is the minimum number required to enable recovery keys For deta
119. s time issue time_list and the system retrieves the current time See Example 6 1 for an example of retrieving the XIV Storage System time Example 6 1 Retrieving the XIV Storage System time gt gt time list Time Date Time Zone Daylight Saving Time 11 45 42 2010 09 27 GMT no After the system time is obtained the statistics_get command can be formatted and issued The statistics get command requires various parameters to operate The command requires that you enter a starting or ending time point a count for the number of intervals to collect the size of the interval and the units related to that size The time stamp is modified by the previous time_list command Example 6 2 provides a description of the command Example 6 2 The statistics_get command format statistics get perf_class perfClassName host HostName host_iscsi_name initiatorName host _fc_port WWPN target RemoteTarget remote fc _port WWPN remote ipaddress IPAddress vol VolName ipinterface IPInterfaceName local _fc_port ComponentId lt start TimeStamp end TimeStamp gt module ModuleNumber count N interval IntervalSize resolution _unit lt minute hour day week month gt To further explain this command assume that you want to collect 10 intervals and each interval is for 1 minute The point of interest occurred on 16 June 2009 roughly 15 minutes after 11 45 00 It is important to note that the statistics get command allows you to gather the
120. seen by the host systems Also when the XIV Storage System is providing storage to the IBM System Storage SAN Volume Controller Tivoli Storage Productivity Center can correlate LUNs reported by the XIV Storage System to SAN Volume Controller managed disks MDisks Element Manager Launch If the XIV Storage Management GUI is installed and configured Tivoli Storage Productivity Center can start the XIV Storage System management software Tivoli Storage Productivity Center performance reports The XIV Storage System software V10 2 2 or later enables Tivoli Storage Productivity Center to create performance reports The corresponding XIV Storage System performance monitors must be set up first as described in 7 6 1 Setting up and discovering XIV systems in Tivoli Storage Productivity Center V4 2 or later on page 354 To create a performance report click IBM Tivoli Storage Productivity Center gt Configuration Utility gt Disk Manager Storage Subsystem Performance Management Show Subsystem Performance System Report as shown in Figure 7 97 Eem Tivoli Storage Productivity Center sspc sle 1 Configuration Utility File View Connection Preferences Window Help Lae avigation Tree Administrative Services IBM Tivoli Storage Productivity Center Configure Devices Job Management F Reporting Topology F Monitoring Storage Resource Group Management F Analytics A Alerting Data Manager H Dat
121. sending email notification or mobile phone number for SMS notification e SNMP e EMAIL e SMS e Group of Destinations Wizard Destination Create Select Destination type Select Destination type Event notification destination type can be either a destination group containing other destinations SNMP manager for sending SNMP traps Email address F Welcome for sending Email notification or cellular phone number for SMS notification p EMAIL Name SMS Finish Group of Destinations Figure 7 43 Select Destination type window Depending on the selected type the remaining configuration information that is required differs but is self explanatory The final step in the Events Creation wizard is creating a rule A rule determines what notification is sent It is based on event severity event code or both 9 Click Create Rule as shown in Figure 7 44 on page 320 Chapter 7 Monitoring 319 Wizard Events Configuration Rule Rule Add Rules for event notifications gg Create Rule Destination if Rule Finish lt 6 om oe Figure 7 44 Create Rule window 10 On the Welcome window click Next The Rule Create Rule name window opens as shown in Figure 7 45 Wizard Rule Create Rule name Rule name Enter a name for the new rule Names are case sensitive and may contain letters digits or the character _ You can not use a name of an already defined re a
122. size can also be modified by dragging the right side of the rectangular size indicator Volume size When multiple volumes are created in the same step they all have the same size as specified in the Volume Size field 5 In the Volume Name field specify the name of the volume to define The name of the volume must be unique in the system If you specified that more than one volume is defined they are automatically and successively named by appending an incrementing number to end of the specified name You can manually input the suffix of the first volume by typing a different number 6 Click Create to effectively create and add the volumes to the storage pool Figure 4 57 _50 ee t i _OCS Creating volume mywol 1 3 6 Figure 4 57 Volume creation progress indicator After a volume is successfully added its state is unlocked meaning that write format and resize operations are permitted The creation time of the volume is set to the current time and is never changed Notice the volume name sequence in Figure 4 58 or ITSO 7 846 0 GB Hard myvwol 15 myvol_ 4 myvol_ 13 myvwol iz myvol_ dd myvol_ 10 Figure 4 58 Volumes created Resizing volumes Resizing volumes is an operation that is similar to creating them Only an unlocked volume can be resized When you resize a volume its size is specified as an integer multiple of 109 bytes However the actual new size of the volume is rounded up to th
123. so it is common to filter on one host or the specific volumes associated with that host 6 4 2 Performance analysis The first thing to consider when evaluating performance is the overall nature of the I O characteristics These characteristics typically include the IOPS throughput measured in MBps and latency measured in milliseconds ms Our sample XIV Storage System workload is shown in Figure 6 31 All Interfaces Host p6 570 lab 2v19 Read Write 2 20 000 15 000 10 000 5 000 12 30 12 45 13 00 13 15 13 30 13 45 14 00 14 15 00 15 15 15 30 15 45 16 00 16 15 4 15 14 30 14 45 16 Sep 2011 16 30 All Interfaces Host p6 570 lab 2v19 All Interfaces Host p6 570 lab 2v19 Read Write Latency ms Latency ms Write 14 00 14 30 15 00 15 30 16 00 16 30 12 30 13 00 13 30 14 00 14 30 15 00 15 30 16 00 e 16 Sep 2011 amp 16 Sep 2011 amp Figure 6 31 Host IOPS and response times It is important during initial application testing and early production to document IOPS and response times when the application is running well In this way if an XIV Storage System performance issue is suspected you can compare these known good performance characteristics to the new ones and see if there is a difference If there is no difference chances are that whatever is causing the problem it is not the XIV Storage System Chapter 6 Performance 279 280 Input output operations per second and respo
124. storage tucson iii User logon name pre Windowe 2000 xIvHOST1 LOAP Jrivtestuser Back Cancel Figure B 1 Creating an Active Directory user account The value entered in Full name is what the XIV Storage System uses as the user name The only other mandatory field in this form is User logon name The same xivtestuserl value is entered into both fields The other fields can also be populated but are not required IBM XIV Storage System Architecture and Implementation 3 Create the account by clicking Next A new window opens Figure B 2 New Object User Ea Create in sivhost ldap storage tucson ibm com sers Password tseeseseses Confirm password esseeseeese M User must change password at next logon User cannot change password Password never expires Account is disabled lt Back Cancel Figure B 2 Assigning a password By default the password is set to User must change password at next login After the account is created the user must log on to a server that is part of the Active Directory managed domain to change the password After the password is changed all the security rules and policies related to password management are in effect such as password expiration maintaining password change history verifying password complexity and so on Password If the password initially assigned to an Active Directory user is not changed XIV Storage System does
125. support is provided for XIV Management and VPN ports only and is supported for network functions such as DNS SMTP Lightweight Directory Access Protocol LDAP and Simple Network Management Protocol SNMP Note IPv6 address support is provided by both the XIV GUI and XCLI For more details see Chapter 7 Monitoring on page 285 These specific functions do not support IPv6 only IPv4 is used gt Technician notebook port iSCSI port configuration Host iSCSI connections Mirroring iSCSI connections Support Center and XRSC communication YY vV Yy IBM XIV Storage System software V11 1 1 and later offers US Government IPv6 USGv6 compliance 96 IBM XIV Storage System Architecture and Implementation For more information about how to configure IPv6 see 5 3 Configuring IPv6 addresses on page 182 3 2 3 Management connectivity XIV Storage System is managed through three IP addresses over Ethernet interfaces on the patch panel to be resilient to two hardware failures You must have three Ethernet ports available for management If you require management to be resilient to a single network failure be sure to connect these ports to two switches Make sure that the networking equipment providing the management communication is protected by a UPS Management IP configurations For each of the three management ports you must provide the following configuration information to the IBM SSR upon installation see 3 2 1
126. system see Chapter 2 IBM XIV Storage System logical architecture and concepts on page 17 For disk systems one of the most important contributors to performance is the number of disk drives that can simultaneously work together to handle an application s I O requirements Traditionally this situation has been limited by the number of disk drives that can be connected to Redundant Array of Independent Disks RAID controller pairs As we know XIV Storage System does not follow this traditional approach Instead XIV Storage System evenly distributes every logical unit number LUN assigned to an application across every disk drive in every module of the XIV Storage System This situation is true for every XIV Storage System LUN size and every XIV Storage System module configuration This situation means that on average an application server is using every XIV Storage System disk drive equally To emphasize this point see Figure 6 1 which shows a LUN striped across a traditional RAID 5 array that consists of eight disk drives e Traditional Storage with RAID Array LUNs carved out of single Array e The LUN enjoys the performance of 8 spindles e LUNs compete for the performance of 8 spindles Figure 6 1 Ejight drive RAID array 248 IBM XIV Storage System Architecture and Implementation Now in contrast see Figure 6 2 which shows a LUN virtualized into 1 MB partitions and distributed evenly across 180 drives in a 1
127. the Windows Task Scheduler to schedule the script to run automatically on a daily basis by clicking Start Programs Accessories gt System Tools Scheduled Tasks as shown in Figure 7 103 Vol_Example ud us Vol_Example O E oy Task Schedule Settings Security Task Schedule Settings Security E C WINDOWS Tasks Vol_Example job E At 1 00 AM every day starting 10 20 2010 C Scripts Vol_Example wsf Schedule Task Start time mwa G Start in Schedule Task Daily D fi Run as a Set password L Run only if logged on Enabled scheduled task runs at specified time C Show multiple schedules Figure 7 103 Using Windows Task Scheduler to run custom monitoring scripts After running this script a custom event is generated if the used capacity threshold is exceeded You can see the custom event in the XIV Storage System event log as shown in Figure 7 104 An event notification rule can be defined based on severity or the CUSTOM_EVENT event code to send an email or SNMP message as described in 7 1 10 Monitoring using the IBM XIV Mobile Dashboard on page 309 Event Properties Severity Warning Date 2010 10 19 15 12 31 Index 450495 Event Code CUSTOM EVENT T Shooting Description Vol itso _vol_ 2 exceeded threshold of 700 Figure 7 104 A custom event generated by the WSH script using XCLI 374 IBM XIV Storage System Architecture and Implementation 7 8
128. the XIV Storage System and present options that are available for alerting and monitoring including an enhanced secure remote support capability This book is intended for IT professionals who want an understanding of the XIV Storage System It also targets readers who need detailed advice on how to configure and use the system SG24 7659 07 ISBN 0738439096 l TW k pe Redbooks INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization Experts from IBM Customers and Partners from around the world create timely technical information based on realistic scenarios Specific recommendations are provided to help you implement IT solutions more effectively in your environment For more information ibm com redbooks
129. the central UPS unit in the main data center in a harmful way Figure 3 12 shows an illustration of one UPS module Proactive power problem recognition Proactive power problem correction Battery Buffered operation up to 11 9 minutes UPS 4200 Watt 6000 VA Output Voltage 230 V Frequency 50 60 Hz Input Voltage 100 280 V Frequency 50 60 Hz Input Connection Hard VVire 3 wire Figure 3 12 UPS module The three UPS modules are at the bottom of the rack Each UPS is 3U in height Each UPS has an output of 6 Kilovolt ampere kVA to supply power to all other components in the system 72 IBM XIV Storage System Architecture and Implementation Attention Do not power off the XIV Storage System using the UPS power button because this action can result in the loss of data and system configuration information Powering the system off must be done solely from either the XIV Storage Management graphical user interface GUI or the XCLI To monitor battery life the UPS modules routinely run a self test every 14 days with a 9 hour interval between each UPS To maximize battery life a UPS battery calibration is performed every 120 days This calibration drains the batteries to about 20 and charges them back to 100 This routine operation causes UPS warning lights and UPS audible alarms The best way to determine if the UPS lights and alarms are a real problem is to look in the event log The routine calibration test
130. the current battery charge level A battery that is not fully charged can be a cause of problems in case of power failure The output of the ups_ list command is broken into two lines for easier reading Example 7 11 The ups_list command gt gt ups_list Component ID Status Currently Functioning Input Power On Runtime Remaining Battery Charge Level gt gt ups_ list 1 UPS 1 OK 1 UPS 2 OK 1 UPS 3 OK yes yes 13 100 yes yes 21 100 yes yes 20 100 300 IBM XIV Storage System Architecture and Implementation Last Self Test Date Last Self Test Result Monitoring Enabled UPS Status 03 13 2013 Passed yes ON LINE 03 13 2013 Passed yes ON LINE 03 14 2013 Passed yes ON LINE Example 7 12 shows the switch_list command that is used to show the status of the switches An XIV Storage System Second Generation Model A14 has Ethernet switches An XIV Storage System Gen3 Model 114 reports an InfiniBand switch Example 7 12 The switch_list command gt gt switch_list 1 IB Switch 1 OK OK 0 2013 03 20 00 09 48 OK 1 IB Switch 2 OK OK 0 2013 03 20 00 09 56 OK Power Supply 2 Problematic Fans Problematic Temperatures Problematic Voltages OK 0 0 0 OK 0 0 0 The psu_list command that is shown in Example 7 13 lists all the power supplies in each of the modules You can show an individual power supply unit PSU by using the psu parameter With this command you can also see the actual power consumption of the PSU model 214 is equipped with high
131. the operations described in 4 4 2 Managing storage pools with the XIV Storage Management GUI on page 137 can also be accomplished through the XIV Command Line Interface XCLI Listing pool related commands To get a list of all the storage pool related XCLI commands enter the following command from the XCLI command shell help category storage pool Important The commands shown in this section assume that you started an XCLI Session on the selected system as described in XCLI Session features on page 133 The output that is shown in Example 4 8 is displayed Example 4 8 All the storage pool related commands Category storage pool storage pool storage pool storage pool storage pool storage pool storage pool storage pool storage pool Name cg move pool change config pool config snapshots pool create pool delete pool list pool rename pool resize vol_move Description Moves a Consistency Group all its volumes and all their snapshots and Snapshot Sets from one Storage Pool to another Changes the lock behavior of the storage Pool Changes the Storage Pool snapshot settings Creates a Storage Pool Deletes a Storage Pool Lists all Storage Pools or the specified one Renames a specified Storage Pool Resizes a Storage Pool Moves a volume and all its snapshot from one Storage Pool to another To list the existing storage pools in a system run pool_list A sample output of this command is s
132. the release notes to confirm any changes that you need to perform An upgrade from Version 1 3 to 2 1 requires you to perform these tasks 1 Reinstall the IBM Storage Management Pack by using the same process that you used to install it See 7 9 2 Installing SCOM and the IBM Storage Management Pack on page 379 The upgrade wizard is automatically started For the upgrade from Version 1 3 to Version 2 1 you need to delete your IBM XIV systems by using the scomu command Use the following syntax for the command scomu del t xiv ip lt ip adress gt 2 Before the import of Version 2 1 you need to delete the old XIV management pack in SCOM first as shown in Figure 7 114 Administration Management Packs 93 ae Connected Management Groups Mare T 360 Application Monitoring Dashboards Ea Baselining Tasks Library E Client Monitoring Internal Library E Client Monitoring Library 4 5 Device Management im Agent Managed Ge Agentless Managed Ty Management Servers ay Pending Management E UNIMLinux Computers Client Monitoring Overrides Management Pack Management Pacs E Client Monitoring Views Library a iam Network Management Pt Data Warehouse Internal Library LE Discovery Rules E Data Warehouse Library Se Network Devices B Default Management Pack rad Network Devices Pending Management gt Notifications us Channels fy Subscribers EA Distributed Application Designer Library Health Internal Library E Health Lib
133. the standard ports Server port 389 secure server port 636 Define LDAP Server FODH itso storage ibm com Server Address 9 155 113 143 Search DH CN Users DC itso DC storage DC ibm Server Port Server Secure Port Certificate File Figure 5 64 Define LDAP servers In a default Active Directory implementation for example a server with the Domain Name ldap domain de maps to CN Users DC Ildap DC domain DC de 6 Click Create to save these settings 7 Click User Credentials to define the Service User DN which is used to verify your LDAP settings In Figure 5 65 you can see that a service user named XIV is defined using a complete Service User DN which in this example is CN XIV CN Users DC itso DC storage DC ibm DC com Enter and confirm the user password LDAP General Service User DN gt CN XIV CN Users DC itso DC storage D Password Pe LDAP Servers Confirm Password TTTTTTT User Credentials Role Mapping Secure LDAP Parameters Update Cancel Figure 5 65 LDAP Configuration User Credentials tab Chapter 5 Security 221 8 Click Role Mapping to enter the LDAP attributes that you want to use for the XIV Storage System login See Figure 5 66 for an illustration of the values for Microsoft Active Directory that we used in our example User ID Attribute sAMAccountName User Name Attribute displayName XIV Group Attribute memberOf Storage Admin R
134. the system s capacity Each increment in the diagram represents 17 GB of soft or hard capacity When a regular storage pool is defined only one capacity is specified and this amount is allocated to the storage pool from both the hard and soft global capacity within the system When a thinly provisioned storage pool is defined both the soft and hard capacity limits for the storage pool must be specified These amounts are deducted from the system s global available soft and hard capacity Thin Provisioning System Hard and Soft Size with Storage Pools For a Thin Storage Pool the system The system allocates the amount of space allocates the amount of soft space requested by the administrator in increments requested by the administrator of 17GB independently from the hard space Regular Stora Thin Storage Poo Pool Soft Size Unallocated AN A As z 2 D 9 EEE e D eo l kua System Soft Size P _ System Hard Size Physical View SS vV yY y Regular Storage Thin Storage Pool Unallocatd Pool Hard Size For a Thin Storage Pool the system allocates only the amount of hard space requested by the administrator This space is consumed as hosts issue writes to new areas of the constituent volumes and may require dynamic expansion to achieve the soft space allocated to one or more of the volumes For a Regular Storage Pool the system alloc
135. the system is installed However exceptions can occur for remote locations where the time zone equals the time of the host system location gt Email sender address The email address that is shown in the email notification as the sender gt Remote access The modem number or a client side IP address must be configured for remote support This network connection must have outbound connectivity to the Internet This basic configuration data is entered in the system by the IBM SSR after the physical installation See Basic configuration on page 98 Other configuration tasks such as defining storage pools volumes and hosts are the responsibility of the storage administrator and are described in Chapter 4 IBM XIV Storage Management software on page 103 Network connection considerations Network connection planning is also essential to installing XIV Storage System To deploy and operate the system in your environment a number of network connections are required Fibre Channel connections for host I O over Fibre Channel 1 Gigabit Ethernet connections for host I O over iSCSI 10 Gigabit Ethernet connections for host I O over iSCSI Gigabit Ethernet connections for management Gigabit Ethernet connections for IBM XIV Storage System remote support M vVvvvy All external XIV Storage System connections are connected through the patch panel as explained in 3 1 10 Patch panel on page 85 88 IBM XIV Storage Syst
136. thresholds Appendix A Thin provisioning conceptual examples 399 400 IBM XIV Storage System Architecture and Implementation Additional LDAP information In this appendix we cover the following topics gt Creating user accounts in Microsoft Active Directory gt Creating user accounts in Sun Java Directory gt Securing Lightweight Directory Access Protocol LDAP communication with Secure Sockets Layer SSL including Windows Server SSL configuration and Sun Java Directory SSL configuration gt Certificate authority setup Copyright IBM Corp 2013 All rights reserved 401 Creating user accounts in Microsoft Active Directory 402 Creating an account in Microsoft Active Directory for use by XIV Storage System LDAP authentication is similar to creating a regular user account The only exception is the designated description attribute field This field must be populated with the predefined value in order for the authentication process to work Complete the following steps 1 Start Active Directory Users and Computer by clicking Start Administrative Tools gt Active Directory Users and Computers 2 Right click the Users container and click New User The New Object User window opens Figure B 1 New Object User x Create in sivhost ldap storage tucson ibm com sers First name Initials Last name Full name Jrivtestuser User logon name Jrivtestuser viyvhost ldap
137. unauthorized system appears disabled It also states that the user is unknown If the system has the lab_admin defined with another password the systems are shown in the same state Chapter 5 Security 203 Figure 5 40 shows a single user login view XIV 1310133 G3 IOPS 3014 MIV 02 1310114 Goo XIV LAB 03 1300203 aya Authentication Failure Figure 5 40 Single user login To allow simultaneous access to multiple systems the simplest approach is to have corresponding passwords manually synchronized among those systems Figure 5 41 illustrates the use of user account with passwords synchronized among four IBM XIV systems The storage administrator can easily switch between these systems for the activities without needing to log on each time with another password Each XIV Storage System where the user was successfully authenticated is now displayed in color with an indication of its status MIV 05 G3 T82 G3 MIV 02 1310114 Go IOPS 1823 Sydney Demo XIV_23 XIV 6000050 Figure 5 41 Manual user password synchronization among multiple IBM XIV systems 204 IBM XIV Storage System Architecture and Implementation Direct mode GUI limitations for managing multiple systems The XIV System Management GUI Version 4 1 supports managing multiple IBM XIV systems in a single GUI instance with the following limits gt The maximum number of groups is 12 gt The maximum number of systems within a g
138. useful information In Figure 7 112 two IBM XIV systems are being monitored Monitoring Systems 2 4 E Monitoring solon Ee so cor E UNIX Linux Computers State System ID System Name D Cluster Q Host Ca Agentless Exception Monitoring Q Healthy 40010 XIV PFE2_13400 Q Healthy gt La Application Monitoring A Warning 10114 w 02 1310114 Q Healthy gt Cd Data Warehouse a ig IBM System Storage TT 4 a IBM XIV Systems Sate Detail View D Alerts ts Events len System properties of 40010 EA Systems 7 Display Name 40010 gt Cd Logical Component cx Full Path Mame Wek 2Teamb XVW SW 2k 2 local 10 0 20 113 40010 Eg Physical Components System Name XIV_PFE _1340010 gt La Microsoft Audit Collection Services system ID 40010 gt Cd Microsoft Windows Client iSCSI Name ign 2005 10 com xivstorage 40010 5 Cd blicrosoftiwindows Server System Soft Capacity GB 243392 7 Ca Network Monitoring System Hard Capacity GB 2453592 system Hard Free Space GB 211729 System Soft Free Space GB 211729 gt Cd Operations Manager Cd synthetic Transaction Current Spare Modules 1 gt C UN Linux Computers Current Spare Disks 3 gt Web Application Transaction Monitoring Target Spare Modules 1 gt Ua Windows Service And Process Monitoring Target Spare Disks 3 Version 11 4 0 e594 920150815 Machine Type 2510 Machine Model 214 Machine Serial Number 1340010 Redundancy Status Full Redundancy SC OM Status available Figure 7 112 S
139. write activity to an under performing drive by effectively maintaining a considerable amount of dirty or unwritten data in cache This situation potentially circumvents any performance degradation resulting from the transient and anomalous service time of a given disk drive Chapter 2 IBM XIV Storage System logical architecture and concepts 55 56 Non Disruptive Code Load Non Disruptive Code Load NDCL enables upgrades to the XIV Storage System software from a current version starting with Version 11 1 0 to a later version without disrupting user applications The code upgrade is run on all modules in parallel and the process is fast enough to have no impact on host applications No data migration or rebuild process is allowed during the upgrade Mirroring if any is suspended during the upgrade and automatically reactivated upon completion Storage management operations are also not allowed during the upgrade although the status of the system and upgrade progress can be queried It is also possible to cancel the upgrade process up to a point of no return The NDCL does not apply to specific component s firmware upgrades for example module basic input output system BIOS and host bus adapter HBA firmware These components require a phase in phase out process of the impacted modules Note Starting from Release 11 3 hot firmware upgrade is supported for certain Unified System Management USM SAS disk and flash cac
140. www snia org IBM Director software download matrix page http www ibm com systems management director downloads html Copyright IBM Corp 2013 All rights reserved 435 gt IBM Systems Director documentation http www ibm com systems management director How to get IBM Redbooks publications You can search for view or download IBM Redbooks publications Redpaper publications Technotes draft publications and Additional materials as well as order hardcopy IBM Redbooks publications at this website ibm com redbooks Help from IBM IBM Support and downloads ibm com support IBM Global Services ibm com services 436 IBM XIV Storage System Architecture and Implementation ie Redbooks IBM XIV Storage System Architecture and Implementation 1 0 spine 0 875 lt gt 1 498 460 lt gt 788 pages IBM XIV Storage System Architecture and Implementation Use data at rest encryption with XIV Gen3 now Improve your cloud with RESTful API and OpenStack support Extend productivity with IBM Hyper Scale This IBM Redbooks publication describes the concepts architecture and implementation of the IBM XIV Storage System The XIV Storage System is a scalable enterprise storage system that is based on a grid array of hardware components It can attach to both Fibre Channel Protocol FCP and IP network Small Computer System Interface iSCSI capable hosts This system is a good fi
141. 0 000 After System Time Em Min Severity Hone iai Before System Time a Event Code All 4 acs me kipi TEPEE h_e a A aaa Date Local Time System Event Code ser N 1S 3 13 PM AI O02 1340714 ADMINISTRATOR_PROCESS FAILURE Admin rN 1018 12 3 13 PM XIV _02_1310114 ADMINISTRATOR_PROCESS FAILURE Admin ry 1018 12 2 55 PM AI 07 1370174 ADMINISTRATOR_PROCESS FAILURE Admir A 10 22 42 1 39 PM AIV_01_6000705 ADMINISTRATOR_PROCESS FAILURE Admir A 1022 12 1 58 PM x 01 6000705 ADMINISTRATOR PROCESS FAILURE Admir Figure 7 4 All Systems Events window Chapter 7 Monitoring 287 You can also access events and alerts for all IBM XIV systems from the View drop down menu as shown in Figure 7 5 You can view All Systems Alerts or All Systems Events or return to the All Systems view Systems Actions QES Toos Hep PH O J Add System EF Add A All Systems 12 Search All Systems All Systems oe Connectivity i List Tiles All Systems Alerts All Systems Events RB TucsonLab All Unavailable 3 _ Figure 7 5 The View drop down menu 7 1 2 Monitoring alerts for all defined IBM XIV systems with the GUI 288 The XIV Storage Management GUI allows users to work with alerts across multiple systems regardless of which XIV Storage System is selected In Figure 7 6 the cursor is hovering over the All Systems Alerts indicator in the lower right corner of the GUI Three alerts across the three systems that are currently d
142. 0 2 4 txt Now you are ready to use an SNMP walk command starting with the xiv OID The only thing that you need to change in this line is the management IP address of the XIV Storage System C usr bin gt snmpwalk v 2c c XIV m XIV MIB 10 10 1 10 xiv In the above command the parameters have the following meaning v 2c Forces SNMP Version 2c c XIV The community name It is case sensitive m XIV MIB Forces the use of the XIV Storage System MIB 10 10 1 10 An XIV Storage System Management Module IP address Xiv The root of the XIV Storage System MIB 340 IBM XIV Storage System Architecture and Implementation In Example 7 44 you see some typical output If your XIV Storage System is using Version 10 2 2 or earlier you also get a list of XIV Storage System events If that is the case do not leave the snmpwalk command running press Ctrl c to stop it XIV Storage System code Versions 10 2 4 and higher do not list XIV Storage System events through the snmpwalk command Example 7 44 The output of the snmpwalk command C usr bin gt snmpwalk v 2c c XIV m XIV MIB 10 10 1 10 xiv XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB XIV MIB gt XivMachineStatus STRING Full Redundancy gt XivFai ledDi gt xivUtilizationSoft gt xXivUtilizationHard xivFreeSpaceSoft XivFreeSpaceHard gt XiVIFIOPS 1004
143. 000 j 3500 3000 2500 2000 1500 1000 500 it 12 30 12 45 13 00 13 15 13 30 13 45 14 00 14 15 14 30 1445 15 00 15 15 15 30 15 45 16 00 16 15 16 30 16 Sep 2011 Figure 6 33 Interface Module balance Chapter 6 Performance 283 284 IBM XIV Storage System Architecture and Implementation Monitoring In this chapter we describe the various methods and functions that are available to monitor the IBM XIV Storage System We also show how you can gather information from the system in real time in addition to the self monitoring self healing and automatic alerting functions implemented within the XIV Storage System software This chapter covers the following topics gt You can review or request the current system status and performance statistics at any time You can set up alerts to be triggered when specific error conditions or problems arise in the system Alerts can be conveyed as messages to a user an email and Simple Network Management Protocol SNMP trap or a Short Message Service SMS text to a mobile phone Depending on the nature or severity of a problem the system can automatically alert the IBM Remote Support Center which immediately initiates the necessary actions to promptly repair the system The call home feature must be configured and working properly for this feature to work If you have purchased IBM Tivoli Storage Productivity Center you can configure it to monitor and configure the XIV Storage S
144. 0000 ees 313 7 1 12 Mobile Dashboard for Android 0 0 ee ees 314 7 2 XIV Storage System event notification 0 0 0 ee 315 7 2 1 Configuring the XIV Storage System to send notifications 315 7 2 2 Setting up event notification naa aaaea ees 315 7 3 Call home and remote support 0 0 ce eee 324 7 32 Callhome features eresia meae os jee oo el ee ph be eek ea ee 324 23 2 Remote SUDDON wore cube eStart eee ee ee eee bee ee ee eee 325 7 3 3 XIV Remote Support Proxy 0 0 0 eens 333 TOA MSIANANON eget ods eee eee ee ee eee Kalen Wee eek eee es 333 7 4 Simple Network Management Protocol based monitoring 336 FAT WONMONING OOS 2g 2 da tia ass aes ate het eon Para a OM ea ake Oe el oe a ecd ask 336 7 4 2 Using SNMP commands to confirm the XIV Storage System status 339 7 4 3 Using SNMP get or walk commands with open source software 340 AS USING WN DINGGION eiren aie ge Adane od wield wa ew ede ee eed ane od a bed RI ee 342 7 5 1 Compiling the Management Information Base file 00005 342 7 5 2 Discovering the XIV Storage System 0 0 eee 344 7 5 3 General System Attributes WINdOW 2 0 2 ee 346 TDA CEVENEIOG s das 2 6 ares tie Stee end We are we hee eee ANd we ene Sod uc a ae Mek ee 347 TO EVER ACHONS cewe ar Somes s Sy Sens ed a ced eer wea hire eet Gest mu ah Sheree tad 348 7 6 Using Tivoli Storage P
145. 008 172008 g172008 g172008 g172008 g172008 g172008 g172008 g172008 4172008 10 53 33 PM Director Topology Online 10 39 44 PM 13447 PM 12420 Ph 4 56 34 Ph 4 41 54 Ph 3 50 46 Ph af 40 Ph 3733 PM 3 23 54 PM 2 45 05 Ph 2 32 24 PM 2 32 09 PM 2 19 47 PM 2 07 50 PM 141 PM Director Topology Offline Director Topology Online Director Topology offline Director Topology Online Director Topology Offline Director Topology Online Director Topology offline Director Topology Online Director Topology offline Director Topology Online Director Topology offline Director Topology Online Director Topology offline Director Topology Online Director Topology Offline System W 10 0 MAOO0SO is online System IY Y1 OO MAMOO050 is offline System XW 10 0 MAOO05O is online System IY V1 OO MAMOO050 is offline System XW 10 0 MAOOO50O is online System IY YT OO MNOO050 is offline System XW 10 0 MAOOOSO is online System IY V1 OO MANOO050 is offline System XW 10 0 MAOO05O is online System IY V1 OO MNOO050 is offline System SY 10 0 MAOOO5O is online System IY V1 OO MNMOO050 is offline System XW V1 OO MAOO050 is online System IY V1 OO MAMOO050 is offline System XW Y1 OO MAOO050 is online System IY Y1 OO MAMOO050 is offline Figure 7 66 IBM Director Event Log Event Type Event Text System Mame Severity Category Group Mame Sender Name Director Topology Online System MY Y10 0 MAOO050 sW 10 0 MAOO
146. 01 Tivoli Storage Productivity Center GUI resource overview 370 IBM XIV Storage System Architecture and Implementation Figure 7 102 shows the options that are available from the drop down menu in each quadrant of the display Overview pace 4 Available 46 26 TiB Capacity Last 30 days Space by Host Capacity 0 0 0 o o o o o Space by Host Space by Pool Space by Volume Overall System Activity Most Active Volumes Most Active Modules e 0 0 0 0 0 0 0 6 0 8 4 4 H Free Capacity o Used Capacity Virtual Ca o ora BETETE Space by Pool Space by Volume Largest Pools Largest Volumes 20 4 b 4 fa w 1 000 is 10 0 J 0 m _ 2 o 0 0 test_poo mizror_poo Residen co_Poo stg 40 stg 41 cx 01 cx 02 cx 03 cx 04 Figure 7 102 Tivoli Storage Productivity Center GUI overview customization From the Overview window you can also navigate to detailed information about the XIV Storage System The following links are provided gt Volumes Volume status and capacity Pools Pool status and capacity Disks Status of the XIV disks by module Modules XIV module status Ports Port status and worldwide port name WWPN Host connections Defined host connections and volume mappings YYY V Yy The Overview window is also available from the Alerts display If an alert is related to an XIV Storage System the name of the resource associated with the event is a link to t
147. 050 Harmless Resalution Extended Attributes Values Chapter 7 Monitoring 347 7 5 5 Event actions Based on the SNMP traps and the events you can define various event actions with the Event Action Plan Builder as shown in Figure 7 67 Here you can define various actions for the IBM Director to perform in response to specific traps and events IBM Director offers a wizard to help you define an Event Action Plan Start the wizard by clicking Tasks Event Action Plans Event Action Plan Wizard in the IBM Systems Director Console window The wizard guides you through the setup The window in Figure 7 67 shows that the IBM Director sends for all events an email to a predefined email address or to a group of email addresses Event Action Plan Builder File Edit View Help Event Action Plans Event Filters Actions E AddfRemove event system to Static rd E AddiRemove source group members ta Add a Message to the Console Ticker ig Duplication Event Filter aM Exclusion Event Filter O sR Simple Event Filter OER Event Action Plan OE Log All Events O 4H All Events Add to the Event Log D sR Test Hardware Predictive Failure Al aS Test IBM Director Agent offline aS Test Storage events JA Events P CPU Utilization aS Critical Events aS Environmental sensor events aS Fatal Events aS Hardware Predictive Failure Alert events oH Harmless Events lt H IBM Director Agent offline lt H
148. 13 ios_kbytes_avg G ios_sec latency_prev_avg latency_prev_max read_kbytes_avg reads_sec write_kbytes_avg G writes_sec o psa a m anl se Be 3 l bee i Top s Ha W Bro Figure 6 19 Disk performance view Tetci des ge gueue ze etch ico Queue size etch queue size Aiar E prina mare rN seater ee E Pee e A oa etea E e tn EN re re This disk performance view shows a bar chart of every disk drive in the XIV Storage System configuration There are several different performance metrics from which to choose Here is an explanation of what each one means gt ios _kbytes_ave Average I O size per disk gt read_kbytes_ave Average I O read size per disk gt destage_icp_queue_size Queue size of the pending Instant Copies ICPs we have fora disk This metric is related to snapshot and write workload gt destage_queue_size Number of write commands that are waiting in the queue for the disk This metric increases as writes increase from cache to disk gt jios_sec Number of IOPS for each disk including IOPS in buffer queues 100 is normal 300 is considered high gt reads_sec Number of read IOPS gt writes_sec Number of write IOPS gt latency_prev_avg Average latency gt write_kbytes_avg Average I O write size gt fetch_icp_queue_size Queue size of the pending read ICP gt latency_prev_max Max latency gt fetch_queue_size Number of read commands that a
149. 16 2032 e Hyper Scale Manag Hyper Scale Man Sep 6 2013 Sep 6 2014 Hyper Scale Manag Hyper Scale Man Sep 30 2013 Sep 30 2014 XIV Type 2 XIV May 13 2011 May 18 2014 Figure 4 23 Certificate management in the GUI Chapter 4 IBM XIV Storage Management software 121 122 Copy and paste of system configuration settings To facilitate efficient configuration of system settings when managing multiple IBM XIV systems the GUI supports copying the settings of one system in order to paste those settings to one or more other systems To use this feature first right click the system that contains the configuration settings that you want to copy and choose Copy System Configuration as shown in Figure 4 24 Starbur Modify IP Addresses Remove System Move System To Suspend Monitoring View Events View Statistics View Storage Pools View Volumes by Pools View Volumes View Hosts View Mirroring View Migration Show Certificate View XIV Connectivity View Migration Connectivity Launch XCLI Launch XW Top Copy System Configuration Paste Support Configuration Paste LDAP Configuration Paste Pool Alerts Thresholds Properties Figure 4 24 Copy and paste system configuration settings Next right click a target system and choose to paste the appropriate settings The following configuration settings can be pasted to the target system each in a separate step gt Support Configuration
150. 1_npiv XIV_ORA_oravg_LPAR2_NPIV _ en oa ens l os 24 14 05 24 19 05 24 24 05 24 29 05 24 34 z 4 44 05 24 49 05 24 54 O5 24 s59 05 25 04 05 25 09 05 24 39 05 24 1 Sep 2011 Figure 1 4 XIV Top The tool is designed to quickly display the volumes or hosts that are consuming the most system resources at any given time Information can be sorted in various ways and saved to a file for use in spreadsheet applications 1 6 5 XIV Storage Management XCLI The XIV Storage Management XCLI is a comprehensive command line interface to configure and monitor the system All the functions available in the XIV Storage Management GUI are also available in the XCLI The XCLI can be used in a shell environment to interactively configure the system or as part of a script to perform lengthy or complex tasks Example 1 1 shows an XCLI command being run in a Windows DOS shell Example 1 1 XCLI commands in a Windows DOS shell C gt xcli c XIV_LAB config get Name dns_primary dns_secondary System name internal email subject_format iscsi_name maximal snapshot deletion priority timezone fc_proof ntp_ server ups_control Value 192 168 1 2 192 168 1 3 XIV LAB 01 EBC 2810 A14 6012345 severity description iqn 2005 10 com xivstorage 000105 4 7200 yes 192 168 1 100 yes Chapter 1 IBM XIV Gen3 Storage System overview 13 Support center port type Management The XCLI is installed as part o
151. 24 13 37 41 INFO Enter write end time idx 2013 09 24 13 37 41 INFO Exit write end time_idx 2013 09 24 13 37 41 INFO end time 2013 09 24 13 29 18 last index 8972 2013 09 24 13 37 41 INFO Exit get_xiv_events 2013 09 24 13 37 41 INFO Finished collecting events from xiv 10114 successful ly 2013 09 24 13 37 41 INFO Return items to scom 2013 09 24 13 37 41 INFO Exit collect In Example 7 58 the discovery process for monitoring is run against the same XIV Storage System in about 16 seconds Example 7 58 The scom_xiv log 2013 09 24 13 30 09 INFO Enter discover device by configuration 2013 09 24 13 30 09 INFO Connecting to 10 0 20 102 2013 09 24 13 30 11 INFO 1 IBM XIV Storage System is found device ID 10114 code level 11 4 0 esp4 p20130815 2013 09 24 13 30 11 INFO Started discovering 10114 2013 09 24 13 30 11 INFO Enter get_xiv_devices 2013 09 24 13 30 12 INFO Exit get_xiv_devices 2013 09 24 13 30 14 INFO Enter get_xiv_host_mapping 2013 09 24 13 30 16 INFO XIV host url 10 0 20 102 discovered 2013 09 24 13 30 16 INFO XIV 10 0 20 102 can be connected 2013 09 24 13 30 17 INFO Exit discover_configuration 2013 09 24 13 30 18 INFO Exit get_xiv_host_mapping 2013 09 24 13 30 18 INFO Finished discovery for xiv 10114 successfully 2013 09 24 13 30 18 INFO Returning data to SCOM 2013 09 24 13 30 25 INFO Exit discover _device by configuration As you add additional devices the total time to complete a scan increa
152. 30 password 4support command 0 administrator command code SUCCESS Status 0 Status str Command completed successfully aserver DELIVERY SUCCESSFUL gt gt support_center_status State Connected sessions Timeout min Module Connected since idle 0 27 6 1 Module 4 2010 10 08 10 49 40 The status shows an idle state until an XRSC representative establishes a connection at which time it shows a state of busy as shown in Example 7 34 Example 7 34 Connection busy gt gt support_center_status State Connected sessions Timeout min Module Connected since busy l 40 2 1 Module 4 2010 10 08 10 49 40 To terminate the Remote Support Center connection run the support_center_disconnect command as shown in Example 7 35 Example 7 35 Disconnect from the support center gt gt support_center_disconnect command 0 administrator command code SUCCESS Status 0 Status str Command completed successfully aserver DELIVERY SUCCESSFUL 332 IBM XIV Storage System Architecture and Implementation gt gt support_center_ status State Connected sessions Timeout min Module Connected since no connection 7 3 3 XIV Remote Support Proxy The optional XIV Remote Support Proxy agent can be used when one or more XIV systems do not have direct access to the Internet for example due to firewall restrictions You can use the XIV Remote Support Proxy agent to facilitate the connection to the XRSC
153. 300 5 Ei My Reports Storage Subsystem Performance By volume amp System Reports A MT 2810 6000105 16M gpfs_3 1D 14095 Oct 5 2010 6 00 02 PM 300 5 Y P i Data Al XIV 2810 6000105 IEM gpfs_4 ID 14941 Oct 5 2010 6 00 02 PM 300 5 Eb Disk A XIv 2610 6000105 IBM itso_aix_1 ID 7342 Oct 5 2010 6 00 02 PM 300 5 J Array Performance 5 KIV 2510 6000105 IBM itso_aix_2 1D 7343 Oct 5 2010 6 00 02 PM 300 5 controler Cache Performanca 5l KIV 2810 6000105 IBM NS6004 Data _1 10 15079 Jock 5 2010 6 00 02 PM 300s Controller Performance a ___ _ famme 5 KIv 2610 6000105 I6M NS6004 Data 2 1D 15080 Oct 5 2010 6 00 02 PM 300 s eT Group Performance aeons a a re au _oManaged Disk Group Performance A xIv 2810 6000105 1BM N56004_Data_3 ID 15081 Oct S 2010 6 00 02 PM 300s Port Performance Al XI 2810 6000105 16M N56006_data_m__2 ID 15083 Oct 5 2010 6 00 02 PM 300 s Subsystem Performance 5 ZIv 2610 6000105 I6M NS600B_data_m_3f1D 15084 Oct 5 2010 6 00 02 PM 300 Top Active Volumes Cache Hit Performance 5 XIv 2810 6000105 IBM Onstor_Core_1 ID 14034 Oct 5 2010 6 00 02 PM 300 s Top Volumes Data Rate Performance Al XIV 2810 6000105 IBM Onstor_Core_2 ID 14035 _ Oct 5 2010 6 00 02 PM 300s Top Yolumes Disk Performance S xTV 2810 6000105 IBM ONStor_Lun_1 1D 13790 Oct 5 2010 6 00 02 PM 3005
154. 4TB 36 TB 4 0 TB 44TB 48 TB 52 B 56 TB 6 0 TB 4 8 TB 7 2 TB 8 0 TB 8 8 TB 9 2 B 10 4 TB 11 2TB 12 0 TB 24 26 3 5 3 8 39 42 42 45 46 49 49 53 58 51 56 61 Figure 3 2 Partial configurations Gen3 For more information about usable capacity see 2 3 Full storage virtualization on page 24 3 1 3 Capacity on Demand XIV Storage System Gen3 has an optional pricing model that allows clients to purchase data storage capacity as it is used This feature is called Capacity on Demand CoD Restriction Capacity on Demand is not available for the 1 TB drive option Chapter 3 IBM XIV architecture components and planning 61 CoD means that an XIV Storage System Gen3 can be ordered with a certain amount of authorized storage capacity as well as extra storage capacity that is not intended to be used initially and will be purchased later as this additional storage is allocated to XIV Storage System storage pools IBM is alerted that this storage is being used and an invoice is generated to authorize the use of this additional storage This situation is referred to as purchasing a module activation feature The XIV Storage System provides IBM with reports of allocated storage by way of call home features modem or email and IBM invoices clients if licensed capacity is exceeded An XIV Storage System in the CoD program must be able to call home to IBM This requirement is mandatory The advantage of CoD is that storage purchases can be
155. 5 Security 211 After the LDAP administrator creates the user account and assigns the app01_administrator value to the Member Of attribute the user can be authenticated by the XIV Storage System The role assignment and group membership inheritance for a newly created user is shown in Figure 5 46 XIV System LDAP Server LDAP configuration ldap_config_set User definition xiv_group_attrib MemberOf MemberOf cn app01_admins attribute name attribute value User group definition Name cn app03_ group User group definition Name cn app02_group User group definition Name app01_group Ldap_role cn app01_admins compare strings Strings match Assign user to applicationadmin role User becomes part of app01_ group user group Figure 5 46 Assigning an LDAP authenticated user to the applicationadmin role If the XIV Storage System cannot find a match for the value assigned to the MemberOf attribute of a user the user is denied system access 5 7 Defining LDAP on the XIV Storage System This section describes how to configure the XIV Storage System in an existing LDAP environment Important When upgrading the XIV Storage System software firmware any prior LDAP configuration on the XIV Storage System might be reset Ensure that you have saved the LDAP configuration information if you need to reload it All users but not th
156. 5 module XIV Storage System configuration XIV full rack Every LUN is carved out of 180 spindles Every LUN enjoys the performance of 180 spindles Figure 6 2 XIV Storage System full rack with 180 drives In a traditional storage system it is common for an application s performance requirements to be greater than the performance capabilities of a single RAID array To engage multiple traditional RAID arrays into providing the performance requirements of an application one or more of the following techniques must be used gt Break up the application into multiple LUNs and distribute them among several RAID arrays gt Use operating system logical volume striping techniques to distribute the operating system across the performance capabilities of multiple RAID arrays gt Storage subsystem striping techniques that create LUNs that are striped across multiple RAID arrays It is common for these traditional storage system performance techniques to be combined to meet the performance requirements of an application These techniques are a necessity with traditional storage They can become challenging if there is ever the need to change these configurations because more storage capacity or more performance capacity is required These activities require specialized skills and much work With XIV Storage System there is no need to resort to these multiple techniques Each XIV Storage System LUN has only one disk performan
157. 6 11 159 213 4194 2003 06 16 11 159 846 4166 2003 06 16 11 127 BEZ 3374 00 06 16 11 g8 84s e433 eUUS U6 16 11 115 806 3080 eUUS U6 16 11 115 ede slz4 eUUS U6 16 11 48 ll 1lebe eUUS U6 16 11 132 F6 SUSE Figure 6 28 Output from statistics_get command using the module filter IBM XIV Storage System Architecture and Implementation 6 3 4 Tivoli Storage Productivity Center Tivoli Storage Productivity Center contains enhanced performance metrics for the XIV Storage System For more information see the Tivoli Storage Productivity Center website http www 03 ibm com systems storage software center index html On the IBM Redbooks publication main page search for Tivoli Storage Productivity Center to find several Redbooks publications about how to use the product For more information that relates to the XIV Storage System see 7 6 Using Tivoli Storage Productivity Center on page 353 It is possible to see comprehensive XIV Storage System I O performance characteristics from Tivoli Storage Productivity Center The most effective use of this data is to extract this data from the Tivoli Storage Productivity Center database into comma separated values CSV files and then import them into a spreadsheet This data is useful for performance reporting analysis and archiving Tivoli Storage Productivity Center is a good way to evaluate XIV Storage System performance The Tivoli Storage Productivity Center data that is m
158. 6 21 xv XIV Storage Management systems Actions View Tools Help ih lt lt amp Settings be Launch xcu Launch x1vTop All Systems 2 gt System Figure 6 21 Start XIV Top from the XIV Storage Management GUI Desktop amp admin System Time 5 09PM OQ gt XIV Top can also be started within the statistic view from the lower left corner of the XIV Storage Management GUI Statistics Monitor Filter pane See Figure 6 10 on page 265 Chapter 6 Performance 271 272 The XIV Top tool that is shown in Figure 6 22 is designed to quickly show the volumes or hosts that are consuming the most system resources at any given time Information can be sorted in various ways and exported to a file for use in spreadsheet applications XIV Top XIV LAB 03 1300203 Volumes amp Hosts Volume Name Latency mS BW MBps XIV_ORA_oravg_LPAR1_npiv Host Name Latency mS BW MBps p7 770 02_XIV_RAC_VIO1 XIV_ORA_rootvg_LPAR_3 XIV_RAC_LPAR2_NPIV XIV_ORA_CRS1_VSCSI p7 770 02_XIV_RAC_VIO2 XIV_ORA_DAT_VSCSI_04 p7 770 01_XIV_RAC_VIO3 XIV_ORA_DAT_VSCSI_05 p7 770 01_XIV_RAC_VIO4 XIV_ORA_DAT_VSCSI_06 ATS_zLinux_z9_MTS_mcelini2 XIV_ORA_DAT_VSCSI_07 XIV_ORA_DAT_VSCSI_08 Slelclicicic alS el lolololololo Performance Chart WS_LPAR1 XIV_ORA_rootvg_LPAR_1_npiv XIV_ORA_oravg_LPAR2_NPIV 05 24 14 05 24 19 05 24 24 05 24 29 05 24 34 IBM XI
159. 6 IBM XIV Storage System Architecture and Implementation After saving the CSR file the Certificates Management panel shows your pending certificate request as shown in Figure 5 4 Certificates Management a Close Authenticated Services NX og ig Figure 5 4 Pending CSR Use the CSR file that you just created to obtain a signed x509 certificate either from a trusted CA vendor or from your organization s own CA server For more information about setting up your own CA server and creating your own signed certificate see Certificate authority setup on page 430 Chapter 5 Security 177 Tip Depending on what certificate authority server is used to create your signed privacy enhanced mail PEM file the contents of the file might differ slightly For example when OpenSSL is used to generate a signed PEM file the file might contain plain text metadata details about the CA server and the certificate To import the PEM file into an XIV Storage System it must conform to the x509 standard PEM file format That is it should only contain the actual encrypted certificate and the enclosing BEGIN CERTIFICATE and END CERTIFICATE tags as shown below MITEFTCCAv2gAwI BAgIBJZANBgkqhki GQwOBAQUFADBLMQswCQYDVQQGEwJVUZELMAkKGALUECBMC QVoxDDAKBgNVBAoTA01 CTTENMASGALUECXMESVRTTZESMBAGALUEAxMJeG1 2Q0Fob3NOMB4XDTEz MDMyMDIZNTKOMVoXDTEOMDMyMDIZNTkKOMVowTDELMAkGALUEBhMCVVMxCZAJBgNVBAgTAkFaMQ8w D
160. 73800EB00170 27 09 11 10 43 PM 900 1739 63 874 19 2613 82 13 61 6 83 20 439 12 3 1 8 5 3 32 1 66 2 49 19 XIV 2812 7803760 IBM 1 FC_Port 8 1 500173800EB00180 27 09 11 10 43 PM 900 1737 87 873 19 2611 05 13 6 6 82 20 4277 12 3 I 8 5 3 32 1 66 2 49 20 XIV 2812 7803760 IBM 1 FC_Port 9 1 500173800EB00190 27 09 11 10 43 PM 900 1739 61 870 31 2609 93 13 61 6 81 20 4235 12 3 11 8 6 3 32 1 66 2 49 21 XIV 2812 7803760 IBM 1 FC_Port 4 1 500173800EB00140 27 09 11 10 58 PM 900 1752 1 879 29 2631 39 13 7 6 87 20 5752 12 3 p e i 8 6 3 34 1 67 25 22 XIV 2812 7803760 IBM 1 FC_Port 5 1 500173800EB00150 27 09 11 10 58 PM 900 1758 79 878 86 2637 65 13 72 6 87 20 5869 12 2 i 8 5 3 34 1 67 25 23 XIV 2812 7803760 IBM 1 FC_Port 6 1 500173800EB00160 27 09 11 10 58 PM 900 1753 36 879 14 2632 5 13 72 6 86 20 5854 12 3 11 8 6 3 34 1 67 25 24 XIV 2812 7803760 IBM 1 FC_Port 7 1 500173800EB00170 27 09 11 10 58 PM 900 1753 44 879 54 2632 99 13 71 6 86 20 5719 12 2 1 8 5 3 34 1 67 25 25 XIV 2812 7803760 IBM 1 FC_Port 8 1 500173800EB00180 27 09 11 10 58 PM 900 1754 36 875 27 2629 63 13 72 6 84 20 5572 12 2 1 8 5 3 34 1 67 2 5 26 XIV 2812 7803760 IBM 1 FC_Port 9 1 500173800EB00190 27 09 11 10 58 PM 900 1753 72 882 18 2635 9 13 71 6 88 20 5901 12 3 1 8 5 3 34 1 67 29 27 XIV 2812 7803760 IBM 1 FC_Port 4 1 500173800EB00140 27 09 11 11 13 PM 899 1737 81 869 12 2606 93 13 61 6 82 20 4265 12 4 11 8 6 3 32 1 66 2 49 28 XIV 2812 7803760 IBM 1 FC_Port 5 1 500173800EB00150 27 09 11 11 13 PM 899 1743 12 878 78
161. 8 See also Figure 3 15 on page 75 and Figure 3 20 on page 81 CompactFlash 4GB Industrial Figure 3 18 Module Compact Flash Card This card is the boot device of the module and contains the software and module configuration files Important Because of the configuration files the Compact Flash Card is not interchangeable between modules and it is not user serviceable Cooling fans To provide enough cooling for the disks processor and system board the system includes 10 fans located between the disk drives and the system board Cool air is pulled from the front of the module through the disk drives The air flow and the alignment of the fans ensures the appropriate cooling of the entire module even if a fan is failing Enclosure management card The enclosure management card is located between the disk drives and the system board In addition to the internal module connectivity between the drive backplane and the system board this card is the backplane for the 10 fans Furthermore it includes fan control and the logic to generate hardware alarms in the case of problems in the module 3 1 8 Interface Modules From a hardware perspective the XIV Storage System Gens Interface Modules are the same as the Data Modules in the corresponding Model 114 or Model 214 See the diagram in Figure 3 19 on page 80 Additional hardware Fibre Channel HBAs and Ethernet adapters differentiate the Interface Module from a Data Module Cha
162. 9 objectClass top sn xivtestuser2 cn xivtestuser2 description custom role 01 search result search 2 result 0 Success The URI format used with the H option specifies that LDAPS must be used on port 636 the LDAP secure port Certificate authority setup This section describes the setup and use of the certificate authority that was used with all example scenarios in this book to issue certificates OpenSSL comes with most Linux distributions by default Information about OpenSSL can be found at the OpenSSL website http www openss1 org Creating the CA certificate To set up the CA for the xivstorage org domain we need to make certain assumptions We modify openss1 cnf to reflect these assumptions to the CA That file can be found in usr share ssl openss1 cnf Portions of that file are shown in Example B 13 Example B 13 openssl cnf CA default dir certs crl_dir database new certs dir certificate serial cr private key RANDFILE x509 extensions name_opt cert_opt default days default_crl_days default_md preserve copy extensions default days default_crl_days default_md preserve 430 root xivstorage orgCA dir certs dir crl dir index txt dir newcerts dir cacert pem dir serial dir crl pem dir private cakey pem dir private rand usr_cert ca_default ca_default 365 30 md5 no copy 365 30 md5 no A EERE H H H
163. 92 GB Snapshots Size 8345 GB eaer Figure 4 46 Resizing pool Chapter 4 IBM XIV Storage Management software 141 The resize operation can also be used to change the type of storage pool from thin provisioned to regular or from regular to thin provisioned see Figure 4 47 Change the type of pool in the Resize Pool window button selection gt When a regular pool is converted to a thin provisioned pool you must specify an additional soft pool size parameter besides the existing hard pool size The soft pool size must be greater than or equal to the hard pool size gt When a thin provisioned pool is changed to a regular pool the soft pool size parameter disappears from the window in fact its value is equal to the hard pool size If the space consumed by existing volumes exceeds the pool s actual hard size the pool cannot be changed to a regular type pool In this case you must specify a minimum hard pool size equal to the total capacity consumed by all the volumes within this pool Resize Pool ITSO XIV PFE GEN3 1310133 O amp Regular Pool G Ze Thin Pool Pool Hard 37 892 GB System Allocated System Pools 4 Free 59 6 454 GB 93 663 GB Pool Hard Size 37892 GB Pool Soft Size 59609 GB Snapshots Size 8345 GB Lock Behavior Read Only Figure 4 47 Resizing and changing the type of a pool The remaining soft capacity is displayed under the Pool Soft Size setting and calculat
164. A Restriction Do not connect these ports to the user client network XIV Remote Support Center To facilitate remote support by XIV Storage System personnel you configure a dedicated Ethernet port for remote access This port must be connected through the organizational firewall so that XIV Storage System personnel can access the XIV Storage System if required The XIV Remote Support Center XRSC merges XIV internal functionality together with a set of globally deployed supporting servers to provide secure IBM support access to the XIV Storage System when necessary and when authorized by the client personnel Figure 3 31 provides a representation of the data flow of the XIV Storage System to IBM Support Customer Network Customer DMZ The Internet IBM Network Customer Staff nly Array Optional Pross Server ARSC External Server SRSC Internal Server AlY Support Figure 3 31 XIV Remote Support Center An optional Remote Support Proxy can be used when one or more IBM XIV systems do not have direct access to the Internet for example because of firewall restrictions You can use the XIV Remote Support Proxy to facilitate the connection to the XIV Remote Support Center For more information about the Remote Support Proxy see the nstallation and User s Guide GA32 0795 94 IBM XIV Storage System Architecture and Implementation To initiate the remote connection process complete the following steps 1 Initiate an Internet based
165. A private OpenSSL uses a couple of files to maintain the CA These files must be created by running the following commands gt touch root xivstorage orgCA index txt gt echo 01 gt gt root xivstorage orgCA serial The access rights on the directories and files need to be reviewed to restrict access to the CA and most importantly to the private key as far as possible To certify the CA certificate for 365 days run the OpenSSL command directly as shown in Example B 14 Example B 14 Generating the CA certificate openssl req new x509 days 365 keyout root xivstorage orgCA private cakey pem out root xivstorage orgCA cacert pem Generating a 1024 bit RSA private key wee ttttt writing new private key to root xivstorage orgCA private cakey pem Enter PEM pass phrase Verifying Enter PEM pass phrase You are about to be asked to enter information that will be incorporated into your certificate request What you are about to enter is what is called a Distinguished Name or a DN There are quite a few fields but you can leave some blank For some fields there will be a default value If you enter the field will be left blank Appendix B Additional LDAP information 431 432 Country Name 2 letter code US State or Province Name full name Arizona Locality Name eg city Tucson Organization Name eg company xivstorage Organizational Unit Name eg section Common
166. B in size gt A partition contains either a primary copy or secondary copy of data Each partition is mapped to a single physical disk e This mapping is dynamically managed by the system through innovative data distribution algorithms to preserve data redundancy and equilibrium For more information about the topic of data distribution see Logical volume layout on physical disks on page 28 e The storage administrator has no control or knowledge of the specific mapping of partitions to drives Secondary copy partitions are always placed in a separate module from the one containing the primary copy partition Important In the context of the XIV Storage System logical architecture a partition consists of 1 MB 1024 KB of data Do not confuse this definition with other definitions of the term partition The diagram in Figure 2 4 on page 24 illustrates that data is uniformly yet randomly distributed over all disks Each 1 MB of data is duplicated in a primary and secondary partition for redundancy The system ensures that the primary partition and its corresponding secondary partition are never located within the same module to protect against a single point of failure Chapter 2 IBM XIV Storage System logical architecture and concepts 27 Logical volumes The XIV Storage System presents logical volumes to hosts in the same manner as conventional subsystems However both the granularity of logical volumes and the mappin
167. BM storage arrays through one console can be deployed gt XIV can improve your cloud environment Automate storage discovery and provisioning in an OpenStack environment using OpenStack Cinder integration For more information see the IBM Redbooks publication Using the IBM XIV Storage System in OpenStack Cloud Environments REDP 4971 00 Deployment of secure robust automated clouds with the latest open standards and integration support including OpenStack and a RESTful API Improved scale out data protection with Hyper Scale Consistency by coordinating concurrent snapshots across multiple XIV systems gt IBM Hyper Scale Manager 1 4 is designed to further drive operational efficiency for large and multi site deployments and provide integrated management and health monitoring of XIV systems across the enterprise gt The new 800 GB flash caching option available for 4 TB systems supports top performance levels at a much higher density and an exceptionally low cost per TB 1 2 Introduction The XIV Gen3 Storage System architecture is designed to deliver performance scalability and ease of management while harnessing the high capacity and cost benefits of serial attached SCSI SAS drives The system uses off the shelf components therefore allowing for faster adoption of newer generation hardware The XIV Storage System incorporates fully automated recovery processes A data redistribution takes place automatically af
168. CCB570A2ZE Session ID ctx Master Key 1074DC7 ECDD9FC302781C876B3101C9C618BB07402DD7062E7 EA3AB794CA9C5D1A33447EE254288CEC S86BBB6CD264DCA Key Arg None Krb5 Principal None Start Time 1246579854 Timeout 300 sec Verify return code 0 ok Basic secure LDAP validation using the ldapsearch command After you have confirmed that the SSL connection is working properly you must verify that you are able to search your LDAP directory using LDAPS on port 636 This action confirms that the LDAP server can communicate using an SSL connection In Example B 12 we use OpenLDAP client for the SSL connection validation A CA certificate needs to be added to the key ring file used by OpenLDAP client The TLS_CERTS option in the OpenLDAP configuration file typically etc openldap 1ldap conf specifies the file that contains certificates for all of the certificate authorities that the client recognizes Example B 12 Testing LDAP over SSL by using the Idapsearch command usr bin ldapsearch x H lIdaps xivhost2 storage tucson ibm com 636 D uid xivtestuser2 dc xivauth w pwd2remember b dc xivauth extended LDIF LDAPv3 base lt dc xivauth gt with scope subtree filter uid xivtestuser2 requesting ALL xivtestuser2 xivauth dn uid xivtestuser2 dc xivauth uid xivtestuser2 objectClass inetOrgPerson objectClass organizational Person objectClass person Appendix B Additional LDAP information 42
169. CLI commands or by notification A flexible system of filters and rules allows you to generate customized reports and notifications For details about how to create customized rules see 7 1 9 Defining notification rules on page 308 7 1 6 Viewing events in the XIV Storage Management GUI The XIV Storage Management GUI provides a convenient and easy to use view of the event log To get to the view shown in Figure 7 26 right click the Monitor icon from the main XIV Storage Management GUI window and click Events from the menu Systems Actions View Tools Help ih Wi xy Setup Eg Rules amp Email Settings Export 4 itso A All Systems 2 gt KIV_PFE2_1340010 o Events w Q Events 4 242 System Time 11 10 AM System Time Ea Min Severity System Time H Event Code Date LocalTime System Event Code J User j Description 9 20 13 1 08 PM PFEZ USER HAS FAILED TO_RUN_C User cimmy from IP 9 155 90 67 f 9 20 43 1 06 PM PFE2 USER HAS FAILED TO RUN_C User cimmy from IP 39 155 90 67 f USER_HAS FAILED TO_RUN_C User cimmy from IP 9 155 90 67 f USER_HAS FAILED TO_RUN_C User cimmy from IP 9 155 90 67 f USER_HAS FAILED TO_RUN_C User cimmy from IP 9 155 90 67 f USER_HAS FAILED TO _RUN_C User itso_secadmin from IP 9 15 USER_HAS FAILED TO _RUN_C User cimmy from IP 9 155 90 67 f USER_HAS FAILED TO _RUN_C User cimmy fro
170. COM Systems view 386 IBM XIV Storage System Architecture and Implementation Monitors The following XIV Storage System components are monitored by SCOM Each monitor is refreshed every 300 seconds gt Logical components These components are user defined constructs Host Mappings Mirrorings This component is not monitored if the XIV Storage System user that was used to define the XIV Storage System to SCOM has only read only privileges Storage Pools Volumes gt Physical components These components represent XIV Storage System hardware or XIV Storage System definitions that relate to hardware Hosts and clusters appear in this list because they represent physical hardware Clusters Disks Fibre Channel Ports Hosts IP Interfaces iSCSI Ports Modules Diagram view It is possible to show any of the views from SCOM as a diagram by right clicking an object and clicking Open Diagram View For example a failed disk can be displayed as a subcomponent of a module as shown in Figure 7 113 where disk 12 on module 7 has failed All other components of module 7 are currently healthy and are gathered together 1 Disk 6 4 Healthy F Figure 7 113 SCOM diagram view Chapter 7 Monitoring 387 7 9 6 Upgrading the IBM Storage Management Pack 388 If a new version of the IBM Storage Management Pack for Microsoft System Center Operations Manager is released check
171. Disk Manager Storage Subsystems Subsystem a Label Type Model Status Available Space GB Consumed Space GB Configured Real Space GB Available Real Space Storage Optimizer al xIv 2810 1300203 IBM xIv 414 a Normal 26 256 35 584 55 696 SAN Planner A XIV 2810 6000105 1BM ow A14 Normal 25 136 40 064 61 744 Monitoring Figure 7 89 List storage subsystems 7 6 2 XIV Storage System Tivoli Storage Productivity Center reports Tivoli Storage Productivity Center V4 2 includes basic capacity and asset information in tabular reports and in the topology viewer In addition logical unit number LUN correlation information and performance data is available Tivoli Storage Productivity Center probes collect the following information from the IBM XIV systems gt Storage pools Volumes Disks Ports Host definitions LUN mapping and masking information YY vV Yy Capacity Space is calculated differently in the XIV Storage Management GUI and the XCLI than in Tivoli Storage Productivity Center gt XIV defines space this way 1 GB as 10 1 000 000 000 bytes 1 TB as 10 1 000 000 000 000 bytes gt Tivoli Storage Productivity Center defines space this way 1 GiB as 2 1 073 741 824 bytes 1 TiB as 27 1 099 511 627 776 bytes These different definitions are why capacity information might appear to differ and seem wrong when comparing the XIV Storage Management GUI with the Tivoli Sto
172. ESOURCES TYPES IANA RTPROTO MIB IANAifType MIB IF MIB INET ADDRESS MIB IP FOR WARD MIB IP MIB RFCLiS5 SMI RFCL213 MIB SNMP COMMUNITY MIB SNMP FRAMEWORK MIB SNMP MPD MIB SMMP MOTIFICATION MIB SMMP PROeY MIB SMMP TAR GET MIB SMMP LISER BASED SM MIB SMMP VIEW BASED ACM MIB SMMPy2 COMF SMMPy2 MIB SMHMPy2 SMI SMHMPy2 TC SMHMPy2 TM era Q Tip Depending on what is already installed in your environment you might need to download the UCD SNMP MIB file MIB files can be downloaded from the following web page http www oidview com mibs 2021 md 2021 1 html Discover the IBM XIV Storage System After loading the MIB file into the IBM Director the next step is to discover the IBM XIV systems in your environment Therefore configure the IBM System Director for auto discovery 1 From the IBM Systems Director select Inventory System Discovery as shown in Figure 7 71 oystems Director Welcome Administrator View all tasks aj Home ayten DES EN Home Find a Task Find a Resource System Discovery Resource Explorer Welcome Use system discovery to discover manageable resources now o My Startup Pages host name discover resources of the same type for a range of discoveries including importing IP addresses and requesting Automation 7 Learn more about using discovery El Inventory enero hese Select a discovery option View and Collect Inventory Single IPv4 address zl Release Manageme
173. Fibre Channel port to the host Restriction Direct host to XIV Storage System connectivity is not supported The implementation must use a SAN fabric either single or dual SAN switches Dual fabric configurations are preferable 92 IBM XIV Storage System Architecture and Implementation Fibre Channel cabling and configuration Fibre Channel cabling must be prepared based on the required fiber length and the selected configuration When installing an XIV Storage System complete the following Fibre Channel configuration procedures gt You must configure Fibre Channel switches that are zoned correctly to allow access between the hosts and the XIV Storage System The specific configuration to follow depends on the specific Fibre Channel switch It is best to have a separate zone for each initiator gt Hosts must be set up and configured with the appropriate multipathing software to balance the load over various paths For multipathing software and setup see the specific operating system section in X V Storage System Host Attachment and Interoperability SG24 7904 iSCSI network configurations Logical network configurations for iSCSI are equivalent to the logical configurations that are suggested for Fibre Channel networks The following options are available gt Redundant configuration Each module connects through two ports to two Ethernet switches and each host is connected to the two switches This design provides a network ar
174. Figure 4 20 Management General Settings Language English United States Default Regional Settings Time zone Use XM system time zone Time Format 12 Hours Default Certificates Figure 4 20 Regional Settings tab in the GUI Disabled menu item tooltips For each GUI menu item that is disabled the menu item contains a tooltip that explains the reason why the item is disabled To view the tooltip mouse over the circled icon at the right of the menu item as shown in Figure 4 21 Storage Administrator amp e min itso_user Application Administr amp technician Technician 4 xiv_development it Edit i xiv_hostprofiler Delete 4 xiv_ maintenance 3 4 xiv_msms Change Password trator 232 Application01_Group Add To Group Properties Selected user is notin a user group Figure 4 21 Disable menu item tooltips 120 IBM XIV Storage System Architecture and Implementation Secure Sockets Layer certificate management Enhanced Secure Sockets Layer SSL certificate support in XIV System Management software 4 3 improves the flexibility and security of managing IBM XIV systems in two ways gt Support for the use of self signed certificates for securing communications between the GUI and XIV Systems running System software Version 11 2 or later whether via direct mode or via the Multi System Manager To manage the self signed certificates on an XIV Storage System click Systems in the menu bar
175. Figure B 9 Entry creation confirmation After the user account is created in Sun Java Directory LDAP its accessibility can be verified by using any of the available LDAP clients In our example Example B 4 we use the Sun Java Directory LDAP client Example B 4 Sun Java Directory account verification using Sun Java Directory LDAP client opt sun dsee6 bin Idapsearch b dc xivauth h xivhost2 storage tucson ibm com D uid xivtestuser2 dc xivauth w pwd2remember uid xivtestuser2 dn uid xivtestuser2 dc xivauth Appendix B Additional LDAP information 413 uid xivtestuser2 description Storage Administrator objectClass inetOrgPerson objectClass organizational Person objectClass person objectClass top Sn xivtestuser2 cn xivtestuser2 The ldapsearch command syntax might appear overly complex and its output seems difficult to interpret However this output might be the easiest way to verify that the account was created as expected The I1dapsearch command can also be useful for troubleshooting purposes when you are unable to communicate with a Sun Java Directory LDAP server Here is a brief explanation of the 1dapsearch command line parameters h xivhost2 storage tucson ibm com Specifies that the LDAP search query must be sent to the xivhost2 xivhostlldap storage tucson ibm com server using the default port 389 b dc xivauth Base_ DN which is the location in the DIT D uid xivtestuser2 dc xivauth The query issued on
176. IV Storage Management GUI To change the LDAP configuration settings in the XIV Storage Management GUI open the Tools menu at the top of the main XIV Storage Manager window click Configure gt LDAP Role Mapping and change the configuration parameter settings Associating roles in OpenLDAP Because we are just using a text string to identify a user in an XIV Storage System group role the string must be added to the description attribute In Example 5 24 we add the XIVAdmins role association to the itso user Because we are using a command line utility a text file is used to feed in the relevant commands into the ldapmodify command Example 5 24 Adding role association to an OpenLDAP user Cat user_mod xivadmins itso dn uid itso ou Users dc itso dc storage dc ibm dc com changetype modify replace description description XIVAdmins 240 IBM XIV Storage System Architecture and Implementation ldapmodify x r f user_mod_ xivadmins itso D cn Manager dc itso dc storage dc ibm dc com w PASSWOrd v Idap_initialize lt DEFAULT gt replace description XIVAdmins modifying entry uid itso ou Users dc itso dc storage dc ibm dc com modify complete ldapsearch LLL b ou Users dc itso dc storage dc ibm dc com D cn Manager dc itso dc storage dc ibm dc com w PASSWOrd uid itso description dn uid itso ou Users dc itso dc storage dc ibm dc com description XIVAdmins We can assign the XIVReadonly va
177. IV Storage System Machine Types 2810 and 2812 do not have an emergency power off EPO switch but you can connect the XIV Storage System to a room emergency power off EPO EPO precaution Powering off the XIV Storage System using a room EPO switch results in data loss and possible loss of configuration An IBM SSR is required to recover an XIV Storage System that was turned off using a room EPO switch If the XIV Storage System loses ac power but is not powered off using an EPO circuit data and configuration are preserved Local laws National or local building electrical fire prevention safety and other laws or regulations can address or control the manner in which information technology equipment is installed within certain facilities and environments The application of those laws or regulations can depend on considerations of factors beyond the nature or design of the equipment to be installed It is a client s responsibility to interpret and identify any laws or regulations applicable to the installation of information technology in its environment and to inform IBM IBM Business Partners or their designated installers of any actions not identified in this document that are necessary to install information technology equipment in the client s facilities in accordance with such applicable laws or regulations Contact your IBM SSR for more information about connecting to a room EPO switch IBM XIV Storage System Architecture and Impl
178. IV Storage System volume to the HBA The disk queue depth depends on the number of XIV Storage System volumes attached to this host from one XIV Storage System and the HBA queue depth For example if you have a host with just one XIV Storage System volume attached and two HBAs with an HBA queue depth of 64 you must configure a disk queue depth of 128 for this XIV Storage System volume to be able to fully use the queue of the HBAs The XIV Storage System architecture eliminates the common storage concept of a large central cache Instead each component module in the XIV Storage System grid has its own dedicated cache The XIV Storage System algorithms that stage data between disk and cache work most efficiently when multiple I O requests are coming in parallel which is when the host queue depth becomes an important factor in maximizing XIV Storage System I O performance It is generally best to configure large host queue depths to ensure that you use the parallelism of the XIV Storage System architecture A best practice is starting with a queue depth of 64 per HBA to ensure usage of the XIV Storage System parallel architecture Tip A queue depth of 64 is the best host HBA queue depth to start with for planning purposes Chapter 6 Performance 259 260 Figure 6 5 shows a queue depth comparison for a database I O workload 70 percent reads 30 percent writes 8 K block size and DBO Database Open Host Side Queue Depth ee 70 30
179. Implementation Latency and all the other metrics for that matter can also be shown for individual or multiple Fibre Channel or iSCSI interfaces volumes or hosts For more information about latency see 6 4 2 Performance analysis on page 279 Another popular view of performance is the percentage of read hits as shown in Figure 6 13 Read hits are the total read requests that are satisfied by reading the data from the XIV system cache Also shown are the cache hits satisfied from the DRAM memory cache and the SSD cache The read cache misses shown are the read requests that were satisfied by retrieving the data from the disk drives Again there is more information about latency in 6 4 2 Performance analysis on page 279 r vi te A Systems Actions View Tools Help O amp admin A AllSystems 4 gt SUERURG Statistics v System Time 8 52PM Q Hit Miss Memory Hit SSD Hit All Interfaces IOPS Read 1400 1415 1430 14445 15 00 1515 15 30 1545 16 00 1615 16 30 16 45 1700 1715 1730 1T45 March 12 2013 Interfaces Hi Q0 8 KB O 64 512 KB Volumes 8 64 KB _ gt 512 KB ATSXIV 1310715 2 6B 5356 lt lt tuttredundaney Figure 6 13 Read hits In certain cases the user needs to see multiple graphs at one time On the right side of the filter pane there is a selection to add graphs see Figure 6 10 on page 265 Up to four graphs are managed
180. Issued by xivstorage Yalid from 6 29 2009 to 6 29 2010 Je You have a private key that corresponds to this certificate Issuer Statement Figure B 11 Certificate information window Appendix B Additional LDAP information 421 To check the xivstorage certificate open the Console Root Certificates Local Computer gt Trusted Certification Authorities Certificates folder and select the certificate issued by xivstorage Figure B 12 shows that the certificate issued to and by the xivstorage CA is valid Certificate This certificate is intended for the following purposefs All issuance policies All application policies Issued to xivstorage Issued by xivstorage Valid from 6 29 2009 to 6 29 2010 Issuer Statement Figure B 12 Certificate information window for xivstorage certificate authority Low level SSL validation using the openssl command The easiest way to test the low level SSL connection to the LDAP server is by running the openssl s_client command with the showcerts option This command connects to the specified host and lists the server certificate the certificate authority chain supported ciphers SSL session information and verify return code If the SSL connection worked the openssl s_ client command result in the verify return code is 0 ok Example B 9 shows the output of the openssl s_client command connecting a Linux server xivstorage org to the Active Directory server xiv
181. Line Interface 145 AS NVOUMES oserye eae a r nd ante Satay a 1h aaa a a ne een Be Rare wrens 147 4 5 1 Managing volumes with the XIV Storage Management GUI 148 4 5 2 Managing volumes with XIV Command Line Interface 157 4 6 Host definition and mapping 2 0 ee eens 159 4 6 1 Assigning LUNs to a host using the XIV Storage Management GUI 159 4 6 2 Assigning logical unit numbers to a host by using the XCLI 164 AT Fas GaC he saorsa ue 2 GLE SOE FSO dais See SAE ES See Sonera eee 165 4 7 1 Managing flash cache with the XIV Storage Management GUI 166 4 7 2 Managing flash cache with XIV Command Line Interface 170 Chapter 5 Sec rity a berries Goes dS oh oe BS ee ee Bee 5 ee a ee 173 IBM XIV Storage System Architecture and Implementation 51 IPAYSICAl ACCESS SCCUMI tices ee baa eetad Fa prear debate esate a S 174 5 2 x509 certificate validation and management 000 ee ee eee 174 5 2 1 Managing x509 certificates with the XIV Storage Management GUI 175 5 3 Configuring IPVO addresses cca teses tani ordain s Rade ca tee teen ele Bed 182 202 l ENaDINO IP VO SUDDONG 4c 2 ccec0 6252 TE T bee bao ea be pE 182 5 3 2 Configuring IPv6 addresses 0 0 eee eens 182 5 4 Configuring Internet Protocol Security connectivity 00 ccc 184 5 5 Native user authentication 0 0 0 ce eee ee eee eee 186 5
182. MMOO080 9 155 56 102 xiv lab 01b mainz de ihm com Linux 2 6 2 A viv lab 01 mainz de ibm com 9 155 53 252 xiv lab 01b mainz de ibm com G Display System Attributes XI ESP 1 10 0 1300203 Tof EA SNMP Devices General Attributes System information System Mame AIVESP 1 V10 0 1300203 System Factory ID SMAP Devices System State Online System Presence Check Setting minutes 15 Securellnsecure supported false Access Denied false Encryption Enabled false TCPIP Addresses 99155 53 252 TOPIAP Hosts t dyn 9 155 53 252 mainz de ibm com Operating System Linus O8 Major Version z OS Minor version G System Mame MiB AIVESP 1 V10 0 1300203 System Description MiB Linu nextra 1 300203 module 6 2 6 16 46 253 xiv 1 64 66 _64 nextra 1 SMP Tue Jul 15 02 43 02 UTC 2008 x86_64 System Contact MIB Unknown System Location MiB Unknown System Object ID iMIB2 enterprises 8072 3 2 100 3 6 1 4 1 9072 3 2 10 System Uptime Mib2 5 hours 2 minutes 6 seconds 1812664 Figure 7 64 General System Attributes window 346 IBM XIV Storage System Architecture and Implementation 7 5 4 Event log To open the event log right click the entry corresponding to your XIV Storage System and select Event Log from the menu shown in Figure 7 65 lel ES T IBM Director Console Console Tasks Associations View Options Window Help ff amp m A e te J all Managed Objects SNMP System Object ID Y Mame a TCPIP Addresses TCPIIP H
183. Manager main window System view XIV background All Systems view 112 IBM XIV Storage System Architecture and Implementation 4 If multiple IBM XIV systems are configured for management in the GUI each system is always visible in the All Systems view regardless of the credentials provided However only systems that are successfully authenticated with the current credentials are accessible Move the cursor over the appropriate XIV Storage System and click it to open the XIV Storage System Management view of that system To return to the All Systems view click the back arrow in the menu bar or the All Systems link in the hierarchical navigation as seen in Figure 4 11 BE XI Storage Management File View Tools Help dod E Settings fA Li Ga sree Ju a By My Grow EWAH System Figure 4 11 Navigate back to All Systems view 5 For ease of management the GUI supports logical grouping of IBM XIV systems a To create a group right click an empty area of the All Systems view and select Add Group as shown in Figure 4 12 Add System Add Group Group By Figure 4 12 Add Group Tip To create a group there must be more than one XIV Storage System configured in the GUI b The Add New Group dialog that is shown in Figure 4 13 is displayed Enter a name for the new group and click OK Add New Group Enter A New Group Name ITSO_Group OK Figure 4 13 Add New Group c The new group now is disp
184. Name eg YOUR name xivstorage Email Address ca xivstorage org During the creation of the certificate any missing information must be provided Also the information that has been defined by using the defaults in the openss1 cnf file must be confirmed The password for the CA private key must be given during the creation process This password is needed whenever the CA s private key is used The following command can be used to view the CA certificate openssl x509 in cacert pem text Signing a certificate The client or server that needs to obtain a certificate must create a certificate signing request and send this request to the CA Certificate request details can be viewed by running the following command openssl req in xivhostl_ cert_req pem text xivhost1 cert_req pem is the certificate signing request and is generated on the xivhost1 xivhost1ldap storage tucson ibm com server Signing a certificate for the xivhost1 server To sign the certificate run the openss1 command with a specified policy as shown in Example B 15 Example B 15 Signing certificate for xivhost1 server openssl ca policy policy_anything cert cacert pem keyfile private cakey pem out xivhostl_cert pem in xivhost1l_cert_req pem Using configuration from usr share ssl openssl cnf Enter pass phrase for private cakey pem Check that the request matches the signature Signature ok Certificate Details Serial Number 1 0x1 Validity Not B
185. P addresses of the XIV Storage System modules 4 5 and 6 Figure 7 79 shows how to view the management IP addresses Right click a particular XIV Storage System in the All Systems view from the XIV Storage Management GUI and select Modify IP Addresses Edit System XW _02_ 1310114 System Name AIV_02 1310114 IP Host name 1 9 155 53 250 IP Host name 9 155 53 251 IP Host name 3 9 155 53 252 Connect Directly Figure 7 79 Showing the management IP addresses Discovery phase To add the XIV Storage System to Tivoli Storage Productivity Center start the Configure Devices wizard Click IBM Tivoli Storage Productivity Center Configure Devices as shown in Figure 7 80 on page 356 Proceed with the steps to add discover and probe an XIV Storage System in Tivoli Storage Productivity Center Chapter 7 Monitoring 355 i Configure Devices Avigation Tree i Administrative Services CS Select Device T Select Device Type evice Type FE Services ores Ue The wizard adds and configures devices that can be administered an H Data Server Select Device Productivity Center Device Server Data Collection _ Replication Server Summ Select the type of devices to be added Data Sources CIMOM Agents Results eds Data Storage Resource i C Pabrics Switches 2 Inband Fabric Agents Computers Dut of Band Fabric Agent Storage Subsystems TPC Servers Mware YI Data Source Discovery f Storage Subsystem i Tape Librarie
186. Priority Front XRSC 2 195 110 41 141 22 0 Front XRSC 3 195 110 411 142 22 0 Contact your support representative if the support_center_list commands do not return a value and you want to use this feature Next you can see what the status of the connection is by running the support_center_status command Example 7 31 Example 7 31 Check support center connection status gt gt support_center_status State Connected sessions Timeout min Module Connected since no connection In this example no connections are currently established To start a session run support _center_connect followed by support_center_status as shown in Example 7 32 Example 7 32 Connect to support center gt gt support_center_connect command 0 administrator Chapter 7 Monitoring 331 command code SUCCESS Status 0 Status str Command completed successfully aserver DELIVERY SUCCESSFUL gt gt support_center_ status State Connected sessions Timeout min Module Connected since idle 0 no timeout 1 Module 4 2010 10 08 10 45 35 If no parameters are specified with the support_center_connect command the timeout values default to never and no password is used You can specify the parameters for timeout idle _ timeout and password as shown in Example 7 33 The timeout values are in the format hh mm when using the XCLI commands Example 7 33 Specify connection parameters gt gt support_center_connect timeout 01 00 idle _timeout 00
187. QYDVQQHEwWZUdWNzb24xDTALBgNVBAoTBG1 0c28xEDAOBgNVBAMTB3hpdmhvc3QwggEiMA0GCSqG SIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4hOTzzsk9W oMfd9 3qwZchx2ZbUjDmbwhW5 jy f 9qbb at6UeqavD2mGTX fceLo7 ZwFC5M5PL1LMiD Scz2FWaMH58srwwBo5vUvM 3 P Du H1Xb9FwoyF uUAy IpNkaoMf j L96ToFONLZ22PTi048e3Tnk4d trLir2kt1fzBf5VChAl79K9aMm N7 PFkjuWJu vBPSySyCZGhuTLZOERO4xN9zwXHrhohSnBwOZV kN5NgEVZ6K s 0tUheksEo 4Mqmhnu3 00xjH PYHM7Wu9HrYZU2F Dm2byr 1 4ZOL9IcHNd aCMtraJ6 N6nPiGeFbRS7uUTPmA9VOT f 7AgMBAAGj ggEBMIH MAkGA1UdEwQCMAAWEQYJYIZIAYb4QgEBBAQDAgZAMCwGCWCGSAGG EIBDQQTFh1PcGVu UINMIEd1 bmVyYXR1I ZCBDZXJOaWZpY 2 FOZTAdBgNVHQ4EFgQU2 imuYrU0FeaVUnsjk9jhajwAMsww ewYDVROjJBHQwcoAUMsOyREEVImhVvzy1 yXAUSYsca7ehT6RNMESxCZAJBgNVBAYTAIVIMQswCQYD VQQIEwJ BW j EMMAoGALUEChMDSUJNMQOwCwY DVQQLEwRJVFNPMRIWEAYDVQQDEw 4aXZDQWhvc3SC CQCq40FWskg2IDAJBgNVHREEAjAAMAkGA1UdEgQCMAAwDQYJKoZI hvcNAQEFBQADggEBAGghgptA 19QB IuMirBN9QyzUwyi gpGcxnwxcSUwRHbC aqoB4jGSZszd0OM3kXctAveli0hh7t bJvN5yYHc SaojSPjQYyQNHK6FuNVB1 DqkLUrRDoX6Bt PUBv fQ0asZIVQhY4000bUJg1 GscSuzUkt6m9 s0g YSw57qDRRD7 jHwzxXCzBpNjKOnVcSu Hy8XUa78z871KCkZKxcc t2HV7 InrBbVDzcBu0rerZuuT mzLrmzuoN1uo07isIUqjhAXf30Swat 9NVvXFQYTJxiyxIA5M0i 13tBnqWwQ6PJUKwTbntf7Ra32W5g ZTdA7 jDMNSItV fqaM 1bXrk5cOy Eig If the PEM file that you receive contains any other details open the file with a text editor remove the additional details and save the PEM file before you import it via the XIV GUI 5 When you have obtained the signed certificate return to the
188. SO was renamed ITSO2 2011 10 04 17 51 00 Informational MAP VOLUME admin Volume with name itso_ app0l_vol01 was mapped to LUN 1 for host with name itso app02 2011 10 04 17 51 58 Informational MAP VOLUME admin Volume with name itso_app0O1l vol02 was mapped to LUN 2 for host with name itso app02 Chapter 7 Monitoring 307 Example 7 22 shows the command for listing all instances when the user was updated The USER UPDATED event is generated when a users password email or phone number is modified In this example the t option is used to display specific fields such as index code description of the event time stamp and user name The description field provides the ID that was modified and the user field is the ID of the user performing the action Example 7 22 View USER_UPDATED event with the XCLI C XIV gt xcli c XIV 6000050 t index code description timestamp user_name event list code USER_UPDATED Index Code Description Timestamp User 1089 USER UPDATED User with name admin was updated 2009 07 10 21 45 50 admin 1091 USER _UPDATED User with name admin was updated 2009 07 10 21 45 51 admin 1092 USER _UPDATED User with name technician was updated 2009 07 10 21 45 52 xiv_development 1093 USER_UPDATED User with name technician was updated 2009 07 10 21 45 53 xiv_development 7 1 9 Defining notification rules Example 7 23 describes how to set up a rule in the XCLI to notify the storage
189. Sockets Layering Secure Sockets Layer SSL certificates are used to secure communication between the XIV Storage Management tools and IBM XIV systems Beginning with XIV Storage System software Version 11 2 the use of self signed certificates is supported Robust user auditing with access control lists The XIV Storage System software offers the capability for robust user auditing with access control lists ACLs to provide more control and historical information Chapter 1 IBM XIV Gen3 Storage System overview 9 gt Support for IBM Tivoli Storage Productivity Center Tivoli Storage Productivity Center can discover IBM XIV systems and all internal components and manage capacity for storage pools including allocated deallocated and available capacity with historical trending on utilization It can also receive events and define policy based alerts based on user defined triggers and thresholds gt VMware vStorage API Array Integration VAAI support Using VAAI moves the storage related tasks that were previously performed by VMware onto the storage system Transferring the processing burden reduces performance impact speeds processing frees VMware for more mission critical tasks such as adding applications simplifies management and positions the virtual environment for additional capacity and scalability When hardware acceleration is enabled with XIV System Storage operations such as VM provisioning VM cloning and VM migrati
190. Storage Management tools 0 ce es 10 1 6 2 IBM XIV Storage Management GUI 0 2 20 ee 11 1 6 3 IBM Hyper Scale Manager GUI 0 0 0 0 cc ees 12 1 6 4 XIV Storage Management online monitoring with XIV Top 12 1 6 5 XIV Storage Management XCLI 2 0 00 cee ees 13 Vat THOS SUDDOM a naa 084 50 02220 east cea nes et he kee hho es baka bees ee eee 14 Chapter 2 IBM XIV Storage System logical architecture and concepts 17 2 1 Architecture OVENVIEW 24 24 552 ee 402442 82 m bb iaeidee See44Oe 6 ted eee ees 18 2 TAY Fed S eenaa ana Yee ba ooo Oo peed or Re Soe a a See wee ee hess 18 2 1 2 Hardware elements o 24424454 14142400308 44205 002405 4 ne os a ee 24 18 22 Parallels MM 2 S28 i Sota a Gates cette ene elke Seashell k coe S a fade 21 2 2 1 Hardware parallelism and grid architecture n nnna aaaea 21 222 Sottware parallel SMi aerea a a a a A a E AE Cae oe ew eed 23 2 3 Fullstorage virtualization rssmi dreka eesti Aaa a a a D 24 2 3 1 XIV Storage System virtualization design n a saana aaaea 24 23 2 LOgical SVSteM CONCEPIS isrener pake a a a italy wat E AE 26 23 9 OVStEM CAPACI aeant eea Saw ae ate taht ee Ras dene ge Ml ahd a a 30 234 Storage Pool CONCEDIS nseri awe tL ec es ite Se ete ded 31 2 4 Capacity allocation and thin provisioning 0 0c cee eee ees 34 Copyright IBM Corp 2013 All rights reserved iii iv 20 Flash caching architecture 2 0 ette
191. Storage System planning and preparation tasks must take place before the system is scheduled for delivery and installation in the data center A sales representative will arrange a Technical Delivery Assessment TDA meeting to go over site specific details and to ensure that the correct information is gathered before the delivery of the system Installation planning involves the following major areas gt Ordering the appropriate hardware configuration Current requirements Future requirements gt Configuration planning Basic configurations Network connections Management connections gt Physical installation 3 2 1 Basic configuration planning You must complete the configuration planning worksheets and checklists found in the Planning topic of the IBM XIV Storage System Information Center to allow the IBM service support representative SSR to physically install and configure the system The configuration planning worksheets can also be found in the BM XIV Storage System Gen3 Models 281x 11x and 281x 21x Planning Guide SC27 5412 Additional documentation is available from the XIV Storage System Information Center at http publib boulder ibm com infocenter ibmxiv r2 index jsp You must provide the IBM SSR with the information required to attach the system to your network for operations and management and enable remote connectivity for IBM support and maintenance Chapter 3 IBM XIV architecture compo
192. Storage System Architecture and Implementation IBM XIV Storage System logical architecture and concepts In this chapter we elaborate on various underlying design and architectural concepts of the IBM XIV Storage System that was introduced in Chapter 1 IBM XIV Gen3 Storage System overview on page 1 This chapter covers the following topics 2 1 Architecture overview on page 18 2 2 Parallelism on page 21 2 3 Full storage virtualization on page 24 2 4 Capacity allocation and thin provisioning on page 34 2 5 Flash caching architecture on page 40 2 6 Encryption for data at rest on page 42 2 7 Reliability Availability and Serviceability RAS on page 43 YY YYY V Yy Copyright IBM Corp 2013 All rights reserved 17 2 1 Architecture overview IBM XIV Storage System Gen3 carries on the XIV tradition of providing several architecture design factors that contribute to its unique operational capabilities gt Virtual grid based array design to minimize storage complexity gt Self tuning and self healing to deliver performance and availability without manual tuning gt Easy storage management and provisioning an intuitive graphical user interface GUI to simplify the storage operation within a virtualized storage architecture gt Enhanced connectivity and reliability to strengthen the end to end performance without disruption to the service gt Innovative ca
193. System Gen3 can use flash drives which are also referred to as solid state drives SSDs in each module Flash drives are used as secondary read cache between disks and the dynamic random access memory DRAM cache Data is always placed in both cache units and disk access is avoided when data is in SSD flash drive cache Because the SSD flash drive cache is multiple times larger than the DRAM cache this feature is highly effective in regard to the read cache hit ratio XIV Storage software V11 1 or later is a prerequisite for using SSDs in Model 114 Table 3 1 shows the main hardware components of the IBM XIV Storage System Gens Table 3 1 XIV Storage System Gen3 hardware overview Model 114 Model 214 1 GbE Model 214 10 GbE IBM T42 42U IBM T42 42U IBM T42 42U All Modules Intel Quad core CPU Intel Six core CPU Intel Six core CPU 24 GB DDR memory 48 GB DDR3 1 3 GHz memory 48 GB DDR3 1 3 GHz memory 12x SAS drives 12x SAS drives 12x SAS drives 2x Redundant Power 2x High Efficient Power Supplies 2x High Efficient Power Supplies Supplies module 2U 2U 2U In addition to Data Module 2x iSCSI Ports 10 GbE In addition to Data Module 2x iSCSI Port on Module 4 Interface In addition to Data Module Module 2x iSCSI Port on Module 4 4x iSCSI Ports on active Modules 4x iSCSI Ports on active Modules 4x 8 Gbps FC ports 4x 8 Gbps FC ports 4x 8 Gbps FC ports 2X 36 ports InfiniBand 2X 36 ports InfiniBand 2x 36 ports Infin
194. System Level Settings it is enabled by default for every new volume defined Setting flash cache at a volume level The Volumes and Snapshots view in the XIV Management GUI includes a new field that indicates the flash cache status for the volumes that are defined in the system In the Volumes and Snapshots tabular view there is a new column labeled SSD It displays the flash cache status for all the volumes By default the SSD column shown in Figure 4 76 is not visible To add it use the instructions in 4 5 1 Managing volumes with the XIV Storage Management GUI on page 148 168 xiv XIV Storage Management gt a p o File View Tools Help O p Add Volumes itso li ms Vi My Grou Volumes and Snapshots System Time 05 44pm Q SSD amp abby 10 51GB 0GB test_pool b asimov_125 51 GB 0 GB mirror_pool Enabled Default w asimov_105 51 GB 0 GB mirror_pool Enabled Default b abby_12 51 GB 0 GB test_pool Enabled Default b asimov_038 51 GB 0 GB mirror_pool Enabled Default w adams_127 51 GB 0 GB mirror_pool Enabled Default he w asimov_107 51 GB 0 GB mirror_pool Enabled Default LE b adams_065 51 GB 0 GB mirror_pool Enabled Default w asimov_040 51 GB 0 GB mirror_pfgl Enabled Default amp w asimov_117 51GB 0 GB mirror_pool Enabled Default w asimov_109 51 GB 0 GB mirror_pool Enabled Default b adams_067 51 GB 0 GB mirror_pool Enabled Default sg b asimov_042 51 GB 0 GB mirror_pool
195. System Status and Health Tareshalds z Le mmslsih storage tucson ibm com l Service and Support d Compliance Policy E nextrabam storage tucson ibm co i E Properties Compliance lssues Figure 7 74 Select Event Log The Event Log window is displayed as shown in Figure 7 74 To look at the details of a specific event select it from the list then select Properties from the Actions pull down menu as shown in Figure 7 75 nextrabamil storage tucson ibm com Events Delete Create Filter Actions x Search the table Sd Delete Select Event Source Severity 2 Cate Create Filter C Mo text nextrab amp Unknown Alert i a i a J Properties i eee ora No text nextrabs aani ini SP Unknown Alert _ a So Columns Fa a Mo text nextrabam Unknown Alert Export Mo text nextrabam Unknown Alert Select All Mo text nextrabam Unknown Alert Deselect All 4a Mo text nextrabarm Show Filter Row Unknown Alert Ho text nextrabam Clear All Filters Pe Unknown Alert Mo text nextrabam Edit Sort Unknown Alert miim jimin iim iim iim Ho text nextrabar _ Cear All Sort Unknown Alert Figure 7 75 Select event IBM XIV Storage System Architecture and Implementation The event details properties panel is now open and you can examine the detailed description for the corresponding XIV event as highlighted in Figure 7 76 General Da
196. Tasks Associations View S4135 Window Help Console Preferences O amp O i g G Server Preferences Discovery Preferences s SNMP System Object ID V Name a User Administration 0 44 enterprises 8072 3 2 10 1 3 6 1 anne jonika E XIV V10 0 MN00050 PE a xiv lab 01a mainz de ibm com Linux 2 6 Auditing Administration AI 10 0 MNOO0S0 reo iv lab 01 mainz de ibm com Linux 2 6 E XIV 10 0 MNOO050 9 155 56 102 xiv lab 01b mainz de ibm com Linux 2 6 amp amp xiv lab 01 mainz de ipm com 9 155 56 102 xiv lab 01 b mainz de ibm cam TCP IP Hosts Operating System eg Ready Host x345 tic 31 User ID X345 TIC 31 Administrator 4 objects Figure 7 61 Discovery preferences 2 In the Discovery Preferences window shown in Figure 7 62 on page 345 complete the following steps to discover IBM XIV systems a Click the Level 0 Agentless Systems tab b Click Add to open a window to specify whether you want to add a single address or an address range Select Unicast Range Unicast Because each XIV Storage System is presented through three IP addresses select Unicast Range when configuring the auto discovery preferences c Next enter the address range for the IBM XIV systems in your environment Set the Auto discover period and the Presence Check period as well IBM XIV Storage System Architecture and Implementation amp Discovery Preferences Address Entries
197. Threading Technology HT Technology which delivers two processing threads per physical core Consequently a fully configured system provides the processing power of ninety physical or 180 logical cores using the Hyper Treading Technology Because of Integrate Power Gates the power consumption of inactive kernels is near zero which makes this processor highly efficient With six cores and the mentioned feature the processor is powerful enough to manage the basic workload of all modules and the additional workload in the Interface Modules Note Four core and six core modules can be intermixed in Model 114 with software 11 2 or later in case of FRU replacement or miscellaneous equipment specification MES installation DDR3 memory model 214 XIV Storage System Gen3 Model 214 is equipped with up to 48 GB 3 x 16 GB dual inline memory module DIMM fast DDR3 synchronous dynamic random access memory SDRAM per module All modules have 48 GB installed A 48 GB RAM is compatible with an earlier version to 24 GB RAM and therefore accepts a 48 GB RAM FRU to a 24 GB RAM system but does not accept a 24 GB RAM FRU to a 48 GB RAM system The SDRAMs are provided from two different vendors and cannot be intermixed Power supplies The modules in Model 214 are powered by two redundant high efficiency power supply units HE PSU which have reduced power consumption compared to previous standard PSUs They are monitored by the software and can be indiv
198. V 2812 7803760 IBM 1 FC_Port 9 1 500173800EB00190 27 09 11 10 13 PM 900 1749 25 878 42 2627 66 13 69 6 95 20 6437 12 3 al 8 6 3 34 1 69 2 51 9 XIV 2812 7803760 IBM 1 FC_Port 4 1 500173800EB00140 27 09 11 10 28 PM 900 1736 98 871 87 2608 85 13 57 6 81 20 3832 12 4 11 8 6 3 31 1 66 2 48 10 XIV 2812 7803760 IBM 1 FC_Port 5 1 500173800EB00150 27 09 11 10 28 PM 900 1743 38 870 18 2613 56 13 61 6 79 20 3998 12 3 i 8 6 3 32 1 65 2 48 11 XIV 2812 7803760 IBM 1 FC_Port 6 1 500173800EB00160 27 09 11 10 28 PM 900 1738 53 871 46 2609 99 13 61 6 8 20 4071 12 4 i 8 6 3 32 1 66 2 49 12 XIV 2812 7803760 IBM 1 FC_Port 7 1 500173800EB00170 27 09 11 10 28 PM 900 1739 41 870 09 2609 5 13 6 6 79 20 393 12 3 1 8 6 3 32 1 65 2 48 13 XIV 2812 7803760 IBM 1 FC_Port 8 1 500173800EB00180 27 09 11 10 28 PM 900 1738 81 868 17 2606 98 13 6 6 78 20 3843 12 3 1 8 6 3 32 1 65 2 48 14 XIV 2812 7803760 IBM 1 FC_Port 9 1 500173800EB00190 27 09 11 10 28 PM 900 1738 21 873 36 2611 58 13 59 6 81 20 3991 12 3 1 8 5 3 31 1 66 2 48 15 XIV 2812 7803760 IBM 1 FC_Port 4 1 500173800EB00140 27 09 11 10 43 PM 900 1740 84 873 74 2614 58 13 63 6 81 20 4366 12 4 11 8 6 3 32 1 66 2 49 16 XIV 2812 7803760 IBM 1 FC_Port 5 1 500173800EB00150 27 09 11 10 43 PM 900 1745 24 871 34 2616 58 13 63 6 81 20 4323 12 4 11 8 6 3 32 1 66 2 49 17 XIV 2812 7803760 IBM 1 FC_Port 6 1 500173800EB00160 27 09 11 10 43 PM 900 1738 2 871 18 2609 38 13 6 6 8 20 4003 12 3 1 8 6 3 31 1 66 2 48 18 XIV 2812 7803760 IBM 1 FC_Port 7 1 5001
199. V Storage System Architecture and Implementation XCLI Session XIV 6000037 PFE connecting A XIV 6000037 PFE gt ats_list Component ID Status Currently Functioning Input Line 1 Input Line 2 Output 30A 1 Output 30A 2 Output S04 3 Output 104A Firmware Version 3 Phase LATS 1 OK yes yes yes no yes no yes 4 no KIV 6000037 PFE gt Figure 3 9 Output of ats_list command Four ATS features can be ordered with the XIV Storage System Order them to correspond to the type of alternating current electric power generation transmission and distribution used in the client location When ordering the XIV Storage System order the correct feature that meets both local power regulations and client requirements The four ATS features are shown in Figure 3 10 9890 ATS for wordwide use single phase 60 A 9811 9813 9891 ATS for United States Canada Latin America and Japan three phase delta 60 A 9820 9892 ATS for EMEA and Asia Pacific except Japan three phase wye 30 A 9822 9894 ATS for United States Canada Latin America and Japan three phase delta 30 A 9824 Figure 3 10 ATS features Figure 3 10 also shows the power cords line cords that are associated with each ATS Figure 3 11 shows the details associated with each power cord feature These power cords are also country specific Because each country has specific testing and certification requirements these power cords cannot be used in countries other than those count
200. V Storage System Architecture and Implementation 05 24 39 os 1 Sep 2011 5 24 44 05 24 49 05 24 54 05 24 59 05 25 04 The initial XIV Top window is divided into two horizontal sections the Volumes and Hosts section and the Performance Chart section You can collapse or expand each section by clicking the arrow icon on the right side of the header of each section Figure 6 23 Latency ms BW MBps Host Name IOPS Latency ms BW MBps a a eeleeeelgg JHE 0 556 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 55 0 0 0 0 0 0 0 0 0 0 0 0 0 0 S 2 sleceeezice amp elcie Figure 6 23 XIV Top with Performance Chart section collapsed Each column of the Volumes and Hosts section can be sorted in ascending or descending order by clicking the column and toggling the direction of the sort indicator Figure 6 24 on page 274 Chapter 6 Performance 273 XIV Top XIV_02_1310114 Allinterfaces v Refresh every 4 seconds Volumes amp Hosts Volume Name IOFS Latency ms BWW MBps Host Name XIVWS_HS24_lab13 4 0 0 Blade5 L 24 05 0 0 Blade9 HS22V3 Blade2 L 24 02 Blade3 L 24 03 Blade4 L 524 04 Blade6 LS21 06 Blade7 HS22V2 WS_ESK Team2 1TSO_LPAR4 WS_ESX Team3 WS_ESX Team4 Basic WS Team Win Basic WS Team3 Win WS_ESX Teams WS_ESX Teams Basic WS Team Win WS ESX Te
201. V performance with application specific workloads are at the following web page http www 03 ibm com support techdocs atsmastr nsf Web WhitePapers Copyright IBM Corp 2013 All rights reserved 247 6 1 XIV Storage System software and hardware architecture There are several aspects of the XIV Storage System hardware and software architecture that contribute to the ability of an XIV Storage System to provide excellent performance to real world production applications In this section we describe the following topics gt Workload distribution Grid architecture Caching and extended flash caching Data redistribution Snapshots YY vV Yy 6 1 1 Workload distribution and load balancing One of the main reasons that the XIV Storage System achieves exceptional performance is because the XIV Storage System architecture imposes an elegant way to equally and in parallel use every component within the XIV Storage System grid Equal utilization of every component maximizes performance in three ways gt XIV Storage System engages the performance capabilities of all the drives all the time gt XIV Storage System engages the performance capabilities of every module in the grid gt XIV Storage System eliminates disk hotspots The XIV Storage System stripes and mirrors data in 1 MB partitions across all the disks in the system It disperses the 1 MB partitions in a pseudo random distribution For more details about the architecture of the
202. VMware Site Recovery Manager that simplify the use of storage replication software with VMware vSphere gt Fix Central provides fixes and updates for your XIV System software hardware and operating system at this website http www ibm com support fixcentral swg selectFixes parent Enterprise Storage Servers amp product ibm Storage Disk XIV StoragetSystemt 282810 2812 29 amp release A 11 amp platform Al1 amp function al gt IBM XIV Management Console for VMware vCenter XIV Management Console for VMware vCenter integrates XIV storage with the VMWare VSphere management console to allow more efficient management of VMWare components on XIV storage They link through the IBM Support Portal IBM XIV Storage System Architecture and Implementation gt IBM XIV MSCS Agent The XIV MSCS Agent maintains volume mirroring between two IBM XIV systems and Microsoft failover clusters IBM XIV Provider xProv for Windows VSS XIV VSS Provider integrates XIV Storage System snapshot capabilities with Microsoft Windows Shadow Copy Services They link through the IBM Support Portal IBM Storage Management Pack for Microsoft SCOM The IBM Storage Management Pack for Microsoft Systems Center Operations Manager SCOM is a set of software modules or management packs which allow you to access and monitor IBM storage systems using the host based Microsoft SCOM interface Chapter 1 IBM XIV Gen3 Storage System overview 15 16 IBM XIV
203. XIV product line since March of 2008 He holds a BS degree in Electrical Engineering from the University of Arizona where he graduated with honors Thanks to the following people for their contributions to this project Eyal Abraham Diane Benjuya Amy Blea Ramy Buechler Theodore Gregg Rony Shapiro Yossi Siles George Thomas Moshe Weiss IBM Thanks also to the authors of the previous editions Roger Eriksson Wilhelm Gardt Andrew Greenfield Jana Jamsek Suad Musovich Nils Nause Markus Oscheka Rainer Pansky In Kyu Park Francesco Perillo Paul Rea Carlo Saba Hank Sautter Jim Sedgwick Eugene Tsypin Anthony Vandewerdt Anthony Vattathil Kip Wagner Alexander Warmuth Peter Wendler Axel Westphal and Ralf Wohlfarth Special thanks to ESCC team in IBM Mainz Germany for hosting the project and making equipment available in their lab Now you can become a published author too Here s an opportunity to spotlight your skills grow your career and become a published author all at the same time Join an ITSO residency project and help write a book in your area of expertise while honing your experience using leading edge technologies Your efforts will help to increase product acceptance and customer satisfaction as you expand your network of technical contacts and relationships Residencies run from two to six weeks in length and you can participate either in person or as a remote resident working from your home base Fin
204. _ snap01 and snapshot app01_snap02 app01_ snap02 app01_ snap01 EEEE E Figure 5 69 User group membership for LDAP user 5 8 2 Managing LDAP user accounts Managing user accounts in LDAP authentication mode is done using LDAP management tools The XCLI commands and XIV Storage Management GUI tools cannot be used for creating deleting modifying or listing LDAP user accounts The set of tools for LDAP account management is specific to the LDAP server type The same set of LDAP management tools can also be used for account removal modification and listing 228 IBM XIV Storage System Architecture and Implementation Generating LDAP account lists To generate a list of all LDAP user accounts registered under the Base_DN the XIV Storage System configuration parameter specifying the location of LDAP accounts in the DIT use the ldapsearch queries that are shown in Example 5 12 and Example 5 13 Example 5 12 Generating list of LDAP accounts registered in OpenLDAP Directory ldapsearch LL H ldap localhost 389 x b ou Users dc itso dc storage dc ibm dc com D uid itso ou Users dc itso dc storage dc ibm dc com w PasswOrd uid grep uid uid itso uid zejn uid almira uid xivtestuser Example 5 13 Generating list of LDAP accounts registered in OpenLDAP Directory ldapsearch x H ldap 9 155 113 143 389 x b cn Users dc itso dc storage dc ibm dc com D cn itso cn Users dc itso dc storage dc ibm dc com w Pass
205. a Manager for Databases H Data Manager for Chargeback H Disk Manager H Fabric Manager Figure 7 97 Show performance report Services Data Manager Disk Manager Fabric Manager Tape Manager Element Manager Replication Manag Refresh H E H Storage Subsystems Z total 2 Normal 0 Critical 0 Warning 0 Unreachable CIMOM Discovery Storage Subsystem Probes Storage Subsystem Performance Management Create Subsystem Performance Monitor Reporting Show Subsystem Performance System Report Define By Storage Subsystem Report Define The performance statistics of a storage subsystem are collected by a performance monitor job Only a storage subsyste performance monitor job rum against it Afterward you can drill down into the details of any storage subsystem or even deeper into the single volume view and create Tivoli Storage Productivity Center reports or graphs as shown in Figure 7 98 on page 368 Chapter 7 Monitoring 367 Element Management m al x ie a avigation Tree Selection Storage Subsystems Drill down from XI 2810 6000105 IBM Administrative Services IBM Tivoli Storage Productivity Center Configuration Utility Number of Rows 42 Configure Devices Subsystem Yolume Time Interval Read 1 0 Job Management i Reporting S sO eTV 26 10 6000105 IBM gpfs_1f1D 14093 Oct 5 2010 6 00 02 PM 300 5 Er 5 Iy 2510 6000105 IBM gpfs 2f1D 14034 Oct5 2010 6 00 02 PM
206. a from 168 drives because there is no data from the failed drive in the same XIV Storage System module that contains the failed drive The amount of data from the failed drive on each of the remaining 168 drives represents a small percentage of the total data on each drive The XIV Storage System makes a copy of this data and redistributes it on reserved space on the remaining 179 drives So this operation reads a small amount of data from 168 drives and in turn writes the same small amount of data to 179 drives This operation represents many spindles doing little work to recover from a drive failure Consider the following observations about XIV Storage System data redistribution gt Additional drive usage is small which means that applications hardly notice any I O performance differences gt The speed at which an XIV Storage System can redistribute data is fast because of all the disk spindles involved resulting in relatively short rebuild and redistribution times as compared to RAID rebuild times gt There is no concern for data access patterns because all XIV Storage System drives equally share the production I O workload and redistribution workload gt The redistribution process also has the advantage of massive parallel computing because each module works in parallel to manage only 12 drives and to generate data copies as quickly as possible gt An XIV Storage System is data aware which means that XIV protects or redistribu
207. ace Modules also have additional functions and features associated with host system connectivity The modules communicate with each other through the internal and redundant switched network The software services and distributed computing algorithms running within the modules collectively manage all aspects of the operating environment Design principles The XIV Storage System grid architecture by virtue of its distributed topology ensures that the following design principles are possible gt Performance The relative effect of the loss of a single component is minimized All modules are able to participate equally in handling the total workload This design principle is true regardless of access patterns The system architecture enables excellent load balancing even if certain applications access certain volumes or certain parts within a volume more frequently gt Compatibility Modules consist of standard off the shelf components Because components are not specifically engineered for the system the resources and time required for the development of newer hardware technologies are minimized This benefit coupled with the efficient integration of computing resources into the grid architecture enables the system to realize the rapid adoption of newer hardware technologies available without the need to deploy a whole new subsystem gt Scalability Computing resources can be dynamically changed
208. ace growth Interface Modules house Ethernet and Fibre Channel host interfaces and are able to access not only the local resources within the module but also the entire system With every Interface Module added the system proportionally scales both the number of host interfaces and the bandwidth to the internal resources gt Constant switching capacity The internal switching capacity is designed to scale proportionally as the system grows preventing bottlenecks regardless of the number of modules This capability ensures that internal throughput scales proportionally to capacity 22 IBM XIV Storage System Architecture and Implementation gt Embedded processing power Because each module incorporates its own processing power with cache and disk components the ability of the system to perform processor intensive tasks such as aggressive prefetch caching sophisticated cache updates snapshot management and data distribution is always maintained regardless of the system capacity 2 2 2 Software parallelism In addition to the hardware parallelism the XIV Storage System also employs sophisticated algorithms to achieve optimal software parallelism Modular software design The XIV Storage System internal operating environment consists of a set of software functions that are loosely coupled with the hardware modules These software functions are on one or more modules and can be redistributed among modules as required therefore ensuring r
209. aching disable and ssd_ caching enable commands which are listed in Example 4 15 on page 170 are restricted commands that can be used only with the IBM technician s authority These commands are used by the IBM technician to bring SSDs online when they are phased into the XIV system at installation time Use the ssd_list command to get a list of SSDs that are used as flash cache in the system The output is shown in Example 4 16 Example 4 16 List of SSDs XIV 1310039 Coruscant gt gt ssd_ list Component ID Status Currently Functioning Capacity Target Status Vendor Model Size Serial Firmware Fru Group Temperature 1 S D 321 OK yes 512GB XIV MTFDDAA512MAR 1KAAB 488378 0200BB81 MA40 99Y0720 42 1 SSD 2 1 OK yes 512GB XIV MTFDDAA512MAR 1KAAB 488378 0200BB78 MA40 99Y0720 40 1 SSD 6 1 OK yes 512GB XIV MTFDDAA512MAR 1KAAB 488378 0200BB71 MA40 99Y0720 47 1 SSD 4 1 OK yes 512GB XIV MTFDDAA512MAR 1KAAB 488378 O200BB95 MA40 99Y0720 47 13S SD21 1 OK yes 512GB XIV MTFDDAA512MAR 1KAAB 488378 O200BB7A MA40 99Y0720 39 L lt SSDe521 OK yes 512GB XIV MTFDDAA512MAR 1KAAB 488378 O200BB7D MA40 99Y0720 43 System level flash cache The vol_default_ssd_ caching get command is used to check the default flash cache setting enabled or disabled as illustrated in Example 4 17 Example 4 17 Check SSD Caching state XIV 1310039 Coruscant gt gt vol_ default _ssd caching_get Command executed successfully default enabled XIV 1310039 Coruscant gt gt vol defa
210. ack Figure 2 10 Write path The diagram is intended to be viewed as a conceptual topology Therefore do not interpret the specific numbers of connections and so on as literal depictions Also for our purposes the Interface Modules are depicted on a separate level from the Data Modules However in reality the Interface Modules also function as Data Modules The following numbers correspond to the numbers in Figure 2 10 1 A host sends a write request to the system Any of the Interface Modules that are connected to the host can service the request because the modules work in an active active capacity The XIV Storage System does not load balance the write requests across the different Interface Modules Load balancing must be implemented by host administrators using multipathing and the SAN administrators using correct zoning to equally distribute the host requests among all Interface Modules For more information about host attachment see the Redbooks publication X V Storage System Host Attachment and Interoperability SG24 7904 2 The Interface Module uses the system configuration information to determine the location of the primary module that houses the referenced data which can be either an Interface Module including the Interface Module that received the write request or a Data Module The data is written only to the local cache of the primary module 3 The primary module uses the system configuration information to determ
211. addresses IP1 IP2 and IP3 with each command To avoid redundantly typing and recalling IP addresses use a predefined configuration name By default XCLI uses the system configurations defined when adding systems to the XIV Storage Management GUI To list the current configurations use the command shown in Example 4 1 Example 4 1 List Configurations XCLI command excerpt c Users itso gt xcli L System Managements IPs XIV LAB 03 1300203 192 168 0 1 192 168 0 2 192 168 0 3 XIV 02 1310133 192 168 0 4 192 168 0 5 192 168 0 6 Chapter 4 IBM XIV Storage Management software 133 Commands When running a command you must specify either a configuration or IP address but not both To issue a command against a specific XIV Storage System you must supply the user name and the password for that system The default user is admin and the default password is adminadmin which can be used with the following parameters u user Or user user Sets the user name that is used to run the command p password or password password The XCLI password that must be specified to run a command in the system m IP1 m IP2 m IP3 Defines the IP addresses of the XIV Storage System Example 4 2 illustrates a common command execution syntax on a given XIV Storage System Example 4 2 Simple XCLI command c Users itso gt xcli u itso p PasswOrd m 192 168 0 1 user_list Managing the XIV Storage System by using the XCLI always requires that yo
212. administrator when a user s access control has changed The rule itself has four event codes that generate a notification The events are separated with commas with no spaces around the commas If any of these four events are logged the XIV Storage System uses the relay destination to issue the notification Example 7 23 Setting up an access notification rule using the XCLI C XIV gt xcli c XIV 6000050 rule create rule test rule codes ACCESS OF USER GROUP _TO CLUSTER _REMOVED ACCESS OF USER GROUP_TO HOST REMOVED sACCESS TO CLUSTER GRANTED TO USER _GROUP ACCESS TO HOST GRANTED TO USER GROUP dests email dest Command executed successfully A simpler example is setting up a rule notification for when a user account is modified Example 7 24 creates a rule on the XIV Storage System called ESP that sends a notification whenever a user account is modified on the system The notification is transmitted through the relay destination Example 7 24 Create a rule for notification with the XCLI C XIV gt xcli c c XIV 6000050 rule create rule user_ update codes USER UPDATED dests email dest Command executed successfully The same rule can be created in the XIV Storage Management GUI For more details about configuring the system to provide notifications and setting up rules see Chapter 7 Monitoring on page 285 308 IBM XIV Storage System Architecture and Implementation 7 1 10 Monitoring using the IBM XIV Mobile Dashboard
213. administrator intends a 300 MBps limit for that host the administrator user must set the QoS bandwidth limit for that host to 300 and the Bandwidth Limit per Interface is automatically set to 50 gt With six Interface Modules the enforcement is 50 MBps per Interface Module thereby limiting the host to an aggregate bandwidth of 300 MBps 50 MBps x 6 Modules 300 MBps If only two Interface Modules were used the limit for the host is 100 MBps 50 MBps x 2 Modules 100 MBps gt Ifthe host has only connections to two Interface Modules in a full six Interface Module system the actual host bandwidth limitation is only 100 MBps with this performance class setting 50 MBps x 2 Modules 100 MBps Therefore if the user intends to have a 300 MBps bandwidth limitation with two Interface Modules connected in a full six Interface Module system the Bandwidth Limit per Interface is 150 MBps and the Bandwidth Limit must be set to 900 Limitation by input output operations per second Again the Interface Modules enforce the limitations If the intent is to set the limitation at 10 000 IOPS for a given host in a six Interface Module configuration the IOPS limit should be set to 10 000 and the enforcement is 1 666 10 000 6 for each Interface Module If the host is attached to just two Interface Modules in a full six Interface Module system the host IOPS limitation would be only 3332 with this performance class setting 1666 IOPS x 2 Interface Mo
214. age DC ibm C Server Port Server Secure Port z s pe Certificate File Figure 5 51 Define LDAP Server window Chapter 5 Security 215 Now you can see your added server reflected in the table as shown in Figure 5 52 LDAP Configuration Directory Services Server Configuration x Directory Services Server Configuration E Welcome Add Remove or modify your Directory Services servers If you plan on using Secure LDAP please make sure you attach the appropriate LDAP Server certificate pem format for each server you configure Server Type LDAP Servers XIV User Unique ID s itso storage ibm com Groups Secure LDAP Bind amp Cache Test amp Activation Finish p Figure 5 52 LDAP Servers tab Finish c Cancel 9 Add more LDAP servers if necessary or click Next to continue with the configuration process 10 From the XIV User tab as shown in Figure 5 53 define one user this user must be an already defined LDAP user that will be used by XIV to validate the LDAP settings That user does not need any special permissions 11 As shown in Figure 5 53 enter the complete user DN for LDAP which in our example is CN XIV CN Users DC itso DC storage DC ibm DC com Enter the password for this user as well The password is not saved it is only used for this wizard process Click Next LDAP Configuration Directory Services Service User x Welcome Server
215. age MIBs amp Automation Inventory Manage MIBs Release Management Select MIB module to load Security Available MIB Modules ADAPTEC ASM EXT STORAGE MGMT STN System Configuration System Status and Health ALTEON CHEETAH LAYER4 MIB ALTEON CHEETAH LAYER MIB Task Management ALTEON CHEETAH NETWORK MIB ALTEOQN CHEETAH SWITCH MIB El Settings ALTEON CS PHYSICAL MIB Encryption Preferences Manage MIBs Navigation Preferences Event Log Preferences Autoe Rename BLADE ROOT MIB Server Preferences T BLADESPPALT MIB IT Renistr and CMS Recictration k BNT GbESM 24 10G L2L3 MIB aa aait i R ae E BRIOGE MIB Agent Manager Configuration Brocade REG MIB Brocade TC CHEETAH TRAP MIB CIRPACK MIB CI5C0 C2900 MIB CISCO COP MIB CISCO CLUSTER MIB CISC0 CONFIG MAN MIB CISCO ENTITY VENDORTYPE OIB MIB CISC0 FLASH MIB CISC0 IMAGE MIB CISCO MAC NOTIFICATION MIB CIS5C0 MEMORY POOL MIB CISCO PAGP MIB Figure 7 68 Import MIB 2 Inthe Managed MIBs window click Import MIB File Chapter 7 Monitoring 349 350 3 In the Import MIB File window that is shown in Figure 7 69 specify the directory and file name of the MIB file that you want to import that is XIV MIB and click OK A status window indicates the progress Import MIB Fike To import a file type a file name or click Brovee to select a file a ate Figure 7 69 Browse window MIB file extension IBM Systems Director accepts only MIB files t
216. age System Architecture and Implementation i IBM Tivoli Storage Productivity Center sspc sle 1 Configuration Utility File View Connection Preferences Window Help Element Management s m a x jp avigation Tree Services Data Manager Disk Manager Fabric Manager Tape Manager Element Manager Replication Manager Refresh Storage Subsystems Subsystem XI 2610 6000105 IBM 4I V 2610 1300203 IBM Administrative Services IBM Tivoli Storage Productivity Center Configure Devices Job Management Reporting Topology Monitoring Storage Resource Group Management Analytics Alerting Data Manager Data Manager for Databases Data Manager for Chargeback Disk Manager Fabric Manager Tape Manager Element Manager Replication Manager Status Enabled for Provisioning Enabled for Performance A14 A Normal fa Yes XIV Show Storage Subsystem Details Show Storage Subsystem Asset Report Storage Topology Storage subsystems like D58000 Storage Area Network SAN volume Controllers and XIV are managed via their own native interface Other storage subsystems are managed by CIM Agents CIM Agents managing those other storage subsystems need to be added and a CIMOM discovery job needs to be run For all types of subssytems the Configure Devices wizard can be run to add and configure the devices The prerequisite to enabling a storage subsystem for provisioning and pe
217. aining CoD storage capacity Two year CoD term At the end of two years the system exits the CoD program and automatically activates all remaining unactivated and de allocated CoD modules generating client invoices for all of the remaining CoD storage capacity Three year CoD term At the end of three years the system exits the CoD program and automatically activates all remaining unactivated and de allocated CoD modules generating client invoices for all of the remaining CoD storage capacity gt A warranty for all physically installed modules begins when they are initially powered on They are being used to store data and contributing to performance regardless of whether they have been purchased or not gt Adding more CoD modules effectively creates a rolling CoD term gt XIV Storage System call home capabilities must be enabled to participate in the XIV CoD program Figure 3 3 shows an example of the valid capacities in decimal TB of an XIV Storage System Gens with 2 TB drives The table shows that the capacity per CoD activation varies depending on the exact configuration For example a machine with 10 physical modules has 102 6 TB of usable capacity If the client purchased seven activations they can use 71 82 TB of that 102 6 TB With each extra activation the client could use an extra 10 26 TB of usable capacity If they purchase a total of 10 activations without purchasing any extra physical modules they exit t
218. aintenance Cost of storage management Cost of electricity and cooling Yv vy Yy The XIV Storage System includes software licenses for all features and functionality There is no need to purchase additional software licensing when you decide to add more capacity to your system or use an advanced feature such as mirroring or data migration To augment the capacity additional hardware must be purchased or you can also take advantage of the Capacity on Demand option 1 Twelve TB using 15 x 800 GB flash drives in XIV Gen3 systems equipped with 4 TB disk drives Chapter 1 IBM XIV Gen3 Storage System overview 3 The IBM XIV Storage System Management software suite along with the virtualized grid architecture greatly simplifies the layout and management of data within the storage system which reduces the cost of managing it Snapshots and test environments are created in seconds Data migration is dramatically simple and fast remote mirroring is easy and is supported even between XIV Gen3 and the XIV second generation Storage System By reducing complexity the system minimizes the IT resources required to manage storage freeing individuals for other tasks The XIV Storage System Gen3 uses a grid array of low cost high capacity 1 TB 2 TB 3 TB or 4 TB SAS drives for storing data which provides performance similar to Fibre Channel FC drives in traditional storage systems The grid architecture used in the XIV Storage System eliminates th
219. al QoS IOPS value at the per interface level is 100 000 IOPS with a minimum of 1 IOPS The maximum total QoS BW value at the per interface level is 10 000 with a minimum of 1 Performance class creation using the XCLI If creating a performance class using the XCLI specifying a non zero value is not required as it is when using the XIV Storage Management GUI Therefore when using XCLI an unlimited performance class can be created Figure 4 37 shows the tree table view where hosts in the Unlimited Group can be dragged to the wanted QoS classes In addition both IOPS and bandwidth limits can be adjusted by right clicking either setting and clicking Edit 53 Unlimited Group AIX_P570_2_Ipar2 AIX_Ipar _iscsi Secondary_Sys id IOPS Limit 180000 20000 4 WS _bladecenter_sle_45v6 WS _bladecenter_sle_5v5 WS_bladecenter_sle_ 5v4 WS _bladecenter_sle_5v3 WS_bladecenter_sle_5v WS_bladecenter_sle_45vi QoS grp3 j Bandwidth Limit 142000 2000 x6 D wWwSs_Lpars WS_Lpar_4 a g g g g g Figure 4 37 Quality of service QoS To export details shown in the QoS tree table view click the Export icon in the toolbar at the top of the GUI window For more details see Copy and paste of system configuration settings on page 122 The XIV GUI as we just demonstrated offers an intuitive method for managing QoS delivery in IBM XIV systems The XIV CLI allows the user to schedule QoS features through scripts whic
220. all new applications to the XIV Storage System and experience great performance In this section we describe the following topics gt Sizing gt Number of LUNs gt Multipathing considerations gt Host considerations Application threads Host bus adapter HBA queue depth Logical volume manager striping Operating system tunables gt Quality of service QoS 6 2 1 Sizing By far the most important aspect of XIV Storage System performance is to properly size the system based on performance requirements Each XIV Storage System configuration from six modules to 15 modules has different performance capabilities We call this performance capacity Performance capacity is different from the data storage capacity associated with each XIV Storage System configuration If the data storage requirement indicates that a 12 module XIV Storage System is needed to store all the data and that a 15 module system is required to satisfy the performance requirements of the applications then a 15 module system is required 254 IBM XIV Storage System Architecture and Implementation In addition to the number of modules another way to properly balance the needs of both capacity and performance in tandem is to appropriately select the hard disk drive HDD capacity of the XIV Storage System configuration However for purposes of planning for future storage needs it is also important to remember that the IBM XIV systems support homogeneo
221. ally low because this time is the average time required for the write I O operation to travel from the XIV Fibre Channel interface to cache Write response times are highly dependent upon the size of the average write I O operation Very large write I Os take longer for disk storage systems to process For transaction workloads with write I O sizes of 32 KB or less it is common to observe write response times in the single digit millisecond range The best way to evaluate write response times is to compare them to the write response times recorded during good performance periods Reads take longer than writes normally because some reads invariably must be retrieved from spinning disks and this task takes time Caching storage systems mitigate this situation by detecting certain patterns in read I O characteristics and prestaging data into cache The XIV Storage System has exceptionally aggressive prestaging algorithms for sequential reads that place this data in DRAM cache The XIV System also prestages small block random read data into the XIV Gen3 flash drives as described in 2 5 2 Flash caching algorithm and concepts on page 41 When read data is prestaged in flash or DRAM cache the read request can be satisfied at cache I O speeds This is called a read hit But invariably certain data typically random in nature must be retrieved from disk This is called a read miss Read response times are the weighted average of these fast read cache h
222. also possible to cancel the upgrade process up to a point of no return Firmware NDCL does not apply to certain component firmware upgrades for example module basic input output system BIOS or similar firmware These cases might require a phase in phase out process or a similar process of the impacted modules which can be scheduled for a separate maintenance period to reduce impact to production environments gt Support for flash SSD caching System software manages the flash caching There is nothing that the storage administrator must configure The storage administrator can enable or disable the extended flash cache at the system level or on a per host volume level The XIV software will dynamically and adaptively use the flash as an extended read cache boosting application performance by up to three times for active application workloads XIV System software Version 11 4 contains enhancements that significantly increase the I O performance of the flash cache by up to 4 5 times over systems without it This is accomplished by storing and computing all flash SSD data integrity checksum activities in dynamic random access memory DRAM during normal operation rather than on the flash gt Support for multiple snapshots The snapshot capabilities within the XIV Storage System software use a metadata redirect on write design that allows snapshots to occur in a subsecond time frame with little performance impact The system is d
223. am4 XIVWS_HS24_14 ITSO_LPAR2 XIVWS_HS24_14_4 WS ESK6 4 WS_ESK 5 4 WS _ESK 44 WS _ESK 34 WS5_ESX_2 4 WS ESX 414 magic_wol_006 magic_vol_005 magic _vol_002 snapshot_00 magic_vol_002 magic_vol_004 Basic_W5 Team4_ vol Figure 6 24 Sort columns in ascending or descending order The IOPS latency or bandwidth for up to four volumes or four hosts can be viewed in the Performance Chart section The controls to select the volumes hosts and options operate in much the same way as the Statistics tool from within the GUI Figure 6 25 XIV top XIV_02_1310114 Al interfaces Refresh every 4 amp seconds itso Storage Administrator Volumes amp Hosts y Performance Chart ITSO_Blade5_Perf WS_ESX_5_1 WS_ESX_4_1 WS_ESX11 13 55 09 13 55 14 13 55 19 13 55 24 13 55 29 13 55 34 13 55 39 13 55 44 13 55 49 13 55 54 13 55 59 13 56 04 September 19 2013 Figure 6 25 Display performance information for up to four volumes or hosts with XIV Top 274 IBM XIV Storage System Architecture and Implementation 6 3 3 Using the XIV Storage System Command Line Interface The second method to collect statistics is by using the XIV Storage System Command Line Interface XCLI operation To access the XCLI Session see Chapter 4 IBM XIV Storage Management software on page 103 First you must retrieve the system s time To retrieve the system
224. ame parameter Example 4 12 Create iSCSI port and add to the host definition gt gt host_add_port host ITSO Win2008 iscsi iscsi_name iqn 1991 05 com microsoft win gj5e8kr49ee itso storage ibm com Command executed successfully IBM XIV Storage System Architecture and Implementation Mapping logical unit numbers to a host The final configuration step is to map LUNs to the host definition Complete the following steps 1 Map LUNs to the host definition by using the commands shown in Example 4 13 Fora cluster the volumes are mapped to the cluster host definition There is no difference for FC or iSCSI mapping to a host Example 4 13 XCLI example Map volumes to hosts gt gt map_vol host ITSO Win2008 vol myvol_ 14 lun 1 Command executed successfully gt gt map_vol host ITSO Win2008 vol myvol 15 lun 2 Command executed successfully gt gt map_vol host ITSO Win2008 iscsi vol myvol_10 lun 1 Command executed successfully 2 To complete the example start the server and check the host connectivity status from the XIV Storage System point of view Example 4 14 shows the output for both hosts Example 4 14 XCLI example Check host connectivity gt gt host_connectivity_list host ITSO Win2008 Host Host Port Module Local FC port Local iSCSI port Type ITSO Win2008 10000000C9831FA2 1 Module 9 1 FC Port 9 2 FC ITSO Win2008 10000000C9831FA3 1 Module 5 1 FC Port 5 2 FC gt gt host_connectivity_list host ITSO Win2008 iscsi Host Ho
225. among all applications and all hosts are attached to the same resources division of these resources among both critical and noncritical applications might have an unintended adverse performance on critical applications In response to this issue limiting the rate of noncritical IOPS and bandwidth by specifying and then enforcing limits on the maximum amount of low priority OPS and bandwidth on a host basis is ideal As a result the QoS feature in the XIV Storage System enables better performance for the critical host applications that run concurrently with the noncritical host applications on the same XIV Storage System We explained in Quality of Service on page 129 how to set QoS by defining performance classes in terms of IOPS and bandwidth limitation and then assigning specific hosts to a given performance class Each host can be assigned only a single performance class at a time However there is no limit in the number of hosts within a given class Chapter 6 Performance 261 Limitation by bandwidth The Interface Modules enforce the configured limitations The intended limitation value depends on the number of Interface Modules being used by the hosts within the same performance class The maximum rate value specified is multiplied by the number of Interface Modules installed in the XIV system to determine the rate for the class For example a noncritical host is connected to all six Interface Modules gt Ifthe application
226. ample shows how to resize one of the existing volumes vol resize vol myvol_ 16 size 103 Cannot shrink If you attempt to decrease a volume s size by using the XCLI you receive a CAN NOT SHRINK VOLUME message Create a volume and migrate the data to the new volume To rename an existing volume run the following command vol_rename new_name myvol_ 17 vol myvol_16 To delete an existing created volume run the following command vol delete vol myvol_ 17 For details on how to manage volume SSD Caching through the XCLI see 4 7 2 Managing flash cache with XIV Command Line Interface on page 170 158 IBM XIV Storage System Architecture and Implementation 4 6 Host definition and mapping Because the XIV Storage System can be attached to multiple heterogeneous hosts it is necessary to specify which particular host can access which specific logical drives in the XIV Storage System Mappings must be defined between hosts and volumes in the XIV Storage System The XIV Storage System is able to manage single hosts or hosts grouped together in clusters 4 6 1 Assigning LUNs to a host using the XIV Storage Management GUI There are a number of steps required to define a new host and assign LUNs to it One of the prerequisites is that volumes must be created in a storage pool Defining a host To define a host complete the following steps 1 Inthe XIV Storage System main GUI window hover the cursor over the Hosts and Cl
227. and CHAP Secret Add Host System Cluster Standalone Hosts Name Type default CHAP Name CHAP Secret Ears Cancel Figure 4 63 Add host details 5 Repeat steps 2 and 3 to create additional hosts In our scenario we add another host that is called ITSO_Win2008 iscsi 6 Host access to LUNs is granted depending on the host adapter ID For a Fibre Channel FC connection the host adapter ID is the FC host bus adapter HBA worldwide port name WWPN For an iSCSI connection the host adapter ID is the host iSCSI qualified name IQN To add a WWPN or IQN to a host definition right click the host and select Add Port from the menu as seen in Figure 4 64 Standalone Hosts ITSO _Win2006 iscsi Ipar216 xivids xIVA20 xIV421 AIW422 xivi26 XIWA32 XIVA33 xiv20 xIV24 Edit Delete Rename Create a Cluster with Selected Hosts Atd to Cluster Mowe to Cluster Modify LUN Mapping View LUN Mapping Show statistics Properties g g g g g g g g g g g g g g J Figure 4 64 XIV Storage Management GUI example Add port to host definition 160 IBM XIV Storage System Architecture and Implementation 7 The Add Port window opens as shown in Figure 4 65 Select port type of FC or iSCSI In this example an FC host is defined Add the WWPN for HBA1 If the host is correctly connected and has completed a port login to the storage area network SAN switch at least once the WWPN is shown in
228. and Migration SG24 7759 XIV Storage System Host Attachment and Interoperability SG24 7904 XIV Storage System SSD Caching Implementation REDP 4842 Using the IBM XIV Storage System with OpenStack Cloud Environments REDP 4971 XIV Storage System in VMware Environments REDP 4965 IBM Hyper Scale in XIV Storage REDP 5053 RESTful API Support in XIV REDP 5064 XIV Security with Data at Rest Encryption REDP 5047 XIV Gen3 with SVC and Storwize V7000 REDP 5063 Other publications These publications are also relevant as further information sources YYYY YV Yy IBM XIV Remote Support Proxy Installation and User s Guide GA32 0795 IBM XIV Storage System Application Programming Interface GC27 3916 IBM XIV Storage System Planning Guide GC27 3913 IBM XIV Storage System Product Overview GC27 3912 IBM XIV Storage System User Manual GC27 3914 IBM XIV Storage System Management Tools Version 4 0 User Guide SC27 4230 00 IBM XIV Storage System XCLI Utility User Manual GC27 3915 Online resources These websites are also relevant as further information sources gt IBM XIV Storage System Information Center http publib boulder ibm com infocenter ibmxiv r2 index jsp IBM XIV Storage System website http www ibm com systems storage disk xiv index html IBM System Storage Interoperability Center SSIC http www ibm com systems support storage config ssic index jsp Storage Networking Industry Association SNIA website http
229. and data migration activities Figure 2 2 conceptually illustrates the placement of Interface Modules within the topology of the XIV Storage System architecture gt The system services and software functionality associated with managing external I O is located exclusively on the Interface Modules Module interconnect switches The XIV Storage System contains a redundant switched network based on InfiniBand that transmits both data and metadata traffic between the modules Traffic can flow between two Interface Modules between two Data Modules and between an Interface Module and a Data Module 20 IBM XIV Storage System Architecture and Implementation 2 2 Parallelism The concept of parallelism pervades all aspects of the XIV Storage System architecture by using a balanced redundant data distribution scheme with a pool of distributed or grid computing resources To explain the principle of parallelism further it is helpful to consider the ramifications of both the hardware and software implementations independently We then examine virtualization principles in 2 3 Full storage virtualization on page 24 Important The XIV Storage System uses parallelism at both hardware and software levels 2 2 1 Hardware parallelism and grid architecture The XIV grid design Figure 2 3 on page 22 has the following characteristics gt Both Interface and Data Modules work together in a distributed computing sense However the Interf
230. and password information must be provided along with system information as shown in Figure 4 40 ca C Windows system32 cmd exe lel icrosoft Windows Wersion 6 1 7681 opyright c 2009 Microsoft Corporation All rights reserved H Users itsocd c Program Files x86 BA StoragesSAIUSa 1G Frogram Files cx BM Storages IUSAILUGUI gt xcli exe u itso p Passwird m 192 168 0 1 user_list ane Category Group Active Email Address Area Code Phone Number xiv_development xiv_deve lopment yes xiv_maintenance xiv_maintenance yes admin storageadmin yes echnician technician Yes itso storageadmin yes of Figure 4 40 Starting XCLI from a Windows command prompt Tip For convenience and easier access to XCLI commands add the following value c Program Files x86 IBM Storage XIV XIVGUI to the Path system variable This allows XCLI commands to be run from a command window in any directory For complete and detailed documentation of the XCLI see the IBM XIV Storage System XCLI Reference Guide GC27 3914 and the IBM XIV Storage System Information Center at http publib boulder ibm com infocenter ibmxiv r2 index jsp 132 IBM XIV Storage System Architecture and Implementation XCLI Session features XCLI Session offers command and argument completions along with possible values for the arguments Within a session there is no need to enter user information or IP addresses for each command For example gt Torun a comma
231. and system unavailability To eliminate or greatly reduce this risk the XIV Storage System rack can be equipped with lockable doors The XIV Generation 3 rack security kit is available by ordering RPQ 881190 Important Protect your XIV Storage System by locking the rack doors and monitoring physical access to the equipment 5 2 x509 certificate validation and management All communication among the XIV graphical user interface GUI XIV Storage System Command Line Interface XCLI Hyper Scale Manager and XIV systems uses Secure Sockets Layering SSL via x509 certificates The use of x509 certificates provides for secure authentication and encryption of all communication between the XIV software components Previous versions have required the use of the default built in certificate Beginning with XIV Storage System software Version 11 2 and XIV Storage Management software Version 4 1 you have the flexibility to install and use your own x509 certificates in addition to the built in certificate You can choose to use a certificate that is signed by either a trusted certificate authority CA vendor or your organization s own private CA server For more information about creating and using your own CA server see Certificate authority setup on page 430 Four steps are required to use your own certificate 1 Generate a certificate signing request CSR file from the XIV Storage System 2 Obtain a signed certificate using the CSR
232. and therefore unproven and potentially unmonitored increasing the possibility for a second failure during an array rebuild Important If an XIV Gen3 storage system is equipped with flash cache the flash cache does not participate in the rebuild process because flash cache is only used as extended read cache Therefore the most recent written data must be taken from the disk drives For the same reason a flash cache device failure does not initiate a rebuild or redistribution process For details see 2 5 Flash caching architecture on page 40 or consult the Redpaper publication Solid State Drive Caching Implementation in the IBM XIV Storage System REDP 4842 Redistributing after a failure The redistribution phase starts at the same time as the rebuilding phase after an XIV Storage System disk or module failure However the XIV Storage System GUI begins to report only on redistribution progress after the rebuilding phase is complete and the system has been restored to full redundancy In the redistributing phase the XIV Storage System data partitions both primary and secondary copies continue to be rearranged into the new optimized pseudo random target distribution Redistribution is a low priority self tuning process Notice the status bar in the lower right corner of the XIV Storage Management GUI in Figure 2 12 on page 52 which shows the progress of the redistributing process The percentage complete is in bright green an
233. ands with open source software You can test SNMP get and walk commands to an XIV Storage System using the open source software package net snmp on a Windows workstation This package provides a tool to compile the MIB and issue SNMP commands You can download net snmp from the following website http sourceforge net projects net snmp files net snmp Download the installation executable file and not the source code Because you have downloaded and installed net snmp download the XIV Storage System MIB to C usr share snmp mibs You can get the MIB from the following website http www 01 ibm com support docview wss uid ssg1S4000913 Consideration It is possible to retrieve the MIB contents from an XIV Storage System by running mib_get However in testing we found that the downloaded MIB contained line numbers which confused the MIB compilation process Force a compilation of all MIBs to compile the XIV Storage System MIB by running the following command C usr bin gt snmptranslate Dparse mibs In the output that you get look for messages such as the ones shown in Example 7 43 The module numbers might be different depending on how many MIBs exist in that folder Example 7 43 MIB translation messages XIV MIB is in C usr share snmp mibs XIV MIB 10 2 4 txt Module 72 XIV MIB is in C usr share snmp mibs xiv 10 2 x mib txt Checking file C usr share snmp mibs XIV MIB 10 2 4 txt XIV MIB is now in C usr share snmp mibs XIV MIB 1
234. arks or registered trademarks of Oracle and or its affiliates UNIX is a registered trademark of The Open Group in the United States and other countries Other company product or service names may be trademarks or service marks of others X IBM XIV Storage System Architecture and Implementation Preface This IBM Redbooks publication describes the concepts architecture and implementation of the IBM XIV Storage System The XIV Storage System is a scalable enterprise storage system that is based on a grid array of hardware components It can attach to both Fibre Channel Protocol FCP and IP network Small Computer System Interface iSCSI capable hosts This system is a good fit for clients who want to be able to grow capacity without managing multiple tiers of storage The XIV Storage System is suited for mixed or random access workloads including online transaction processing video streamings images email and emerging workload areas such as Web 2 0 and storage cloud The focus of this edition is on the XIV Gen3 hardware Release 3 4 running Version 11 4 of the XIV system software With this version XIV Storage System offers 4 TB drives and enhanced caching with optional 800 GB flash cache devices solid state drives SSDs per module IBM XIV software Version 11 4 XIV Gen3 supports encryption for all capacity points This version also scales XIV snapshot management out with the new Hyper Scale Consistency by coordinatin
235. arthquake Resistance for IBM Hardware Products IBM Corporate Bulletin C B 1 9711 009 9202 Installation of the required floor hardware and the earthquake resistance kit is disruptive If the earthquake resistance kit is installed on an existing XIV Storage System the XIV Storage System must be turned off and temporarily moved while the floor is prepared and the kit is installed The rack tie downs are intended for securing a frame weighing 1134 kg 2500 Ibs per rack These tie downs are designed to secure the rack on either a non raised floor or a raised floor installation IBM XIV Storage System Architecture and Implementation IBM has made every effort to conduct limited tests but not all situations are tested and the drawings and data are provided on an as is basis with no warranty of any kind express or implied Rather IBM has provided the information to help procure the parts needed You can either install the design or request IBM to install the design as a service For more details see the BM XIV Storage System Gen3 Models 281x 11x and 281x 21x Planning Guide SC27 5412 Rear door heat exchanger The rear door heat exchanger is an optional water cooled device that is mounted on the rear of an XIV Storage System to cool the air that is heated and exhausted by devices inside the rack A supply hose delivers chilled water to the heat exchanger A return hose delivers warm water back to the water pump or chiller referred to as th
236. artitions Chapter 2 IBM XIV Storage System logical architecture and concepts 29 2 3 3 System capacity The XIV Storage System has two different concepts of storage capacity worth discussion gt Net usable capacity gt System reserve capacity Net usable capacity Net usable capacity is the available data storage capacity that comes with the purchased XIV System configuration It is a function of the drive size 1 TB 2 TB 3 TB or 4 TB and the number of modules The calculation of the net usable capacity of the system consists of the total disk count less disk space reserved for sparing which is the equivalent of one module plus three more disks This number is then multiplied by the amount of capacity on each disk drive that is dedicated to data 98 and reduced by a factor of 50 to account for data mirroring achieved by the secondary copy of data For example an XIV Storage System with 15 modules populated with 2 TB disk drives has a net usable capacity of approximately 161 TB based on the following formula 180 15 2 TB 98 2 161 7 The net usable capacity depends on the module configuration and disk drive type For more details see Table 2 1 Table 2 1 Net usable capacity depends on module configuration and disk drive type TB decimal Towinamberofmowies fe fo o o e e Net capacity with 1 TB disk 28 44 51 56 63 67 drives TB TB TB TB TB TB Net capacity with 2 TB disk 55 88 102 111 125 134 d
237. as a single LDAP group applicationadmin Defined as a single LDAP group per XIV User Group Important An LDAP user cannot be a member of more than one LDAP group that is associated to an XIV Storage System role mapping In native mode a role is explicitly assigned to a user at the time of user account creation In LDAP mode the role of a specific user is determined at the time the user logs in to an XIV Storage System 208 IBM XIV Storage System Architecture and Implementation Planning considerations When initially planning to use LDAP based authentication with XIV Storage System the LDAP server administrator must decide on which LDAP attribute can be used for role mapping As described in 5 6 2 LDAP directory components on page 206 each LDAP object has a number of associated attributes The type of LDAP object classes used to create a user account for XIV Storage System authentication depends on the type of LDAP server being used The Sun Oracle Directory server and OpenLDAP uses the inetOrgPerson LDAP object class and Active Directory uses the organizationalPerson LDAP object class for definition of user accounts for XIV Storage System authentication For a detailed definition of the inetOrgPerson LDAP object class and list of attributes see the Internet FAQ archive website http www fags org rfcs rfc2798 html For a detailed definition of the organizational Person LDAP object class and list of attributes see the Micr
238. as shown in Example 7 46 Example 7 46 Using the snmpwalk command without an OID C usr share snmp mibs gt snmpwalk v 2c c XIV m XIV MIB 10 10 1 10 SNMPv2 SMI mib 2 1 1 0 STRING Linux nextra Wal1StC0O module 4 2 6 16 46 268 xiv 220 x86 64 ixssl0 2 4 1 SMP Tue Nov 16 00 43 46 UTC 2010 x86 64 SNMPv2 SMI mib SNMPv2 SMI mib lie 2 OID SNMPv2 SMI enterprises 8072 3 2 10 1 3 2 1 2 0 2 1 3 0 Timeticks 235647520 27 days 6 34 35 20 7 5 Using IBM Director In this section we show how to use IBM Director to monitor the XIV Storage System IBM Director is an example of a possible SNMP manager for an XIV Storage System Other SNMP managers can be used with XIV Storage System as well IBM Director provides an integrated suite of software tools for a consistent single point of management and automation With IBM Director IT administrators can view and track the hardware configuration of remote systems in detail and monitor the usage and performance of critical components such as processors disks and memory All IBM clients can download the latest version of IBM Director code from the IBM Director Software Download Matrix website http www 03 ibm com systems software director downloads index html For detailed information regarding the installation setup and configuration of IBM Director see the documentation available at this website http www ibm com systems management director 7 5 1 Compiling the Manageme
239. assuming that each host fills up the entire 64 depth queue for each request The point here is that for larger configurations more than 20 it is important to include queue depth in your production planning IBM XIV Storage System Architecture and Implementation Logical Volume Manager striping In general the XIV Storage System architecture does not require the use of host based Logical Volume Manager LVM striping techniques to improve I O performance because each XIV Storage System volume is already striped across all the drives in the XIV Storage System Generally it is better not to use any LVM striping or any other method that stripes the data such as ASM on Oracle unless it is required for specific reasons If LVM striping is being considered test the application with and without striping Normally operating system striping techniques have a small negative impact on XIV Storage System performance For example LVM striping might adversely affect XIV Storage System caching algorithms Consider a large sequential read Normally an XIV Storage System aggressively prefetches this data into cache But if this data exists on multiple LUNs because of LVM striping as soon as the operating system calls for data from a different LUN the sequential nature of the read is interrupted and must be detected again by XIV Storage System on the different LUN XIV Storage System is not unique in this regard because all caching storage systems experie
240. ate import wizard by clicking Action All Tasks gt Import Click Next to continue 3 Select the file that you want to import The xivstorage org CA certificate is in the cacert pem file Click Next to continue 4 Select the Place all certificates in the following store option and ensure that the certificate store field is set to Trusted Root Certification Authorities Click Next to continue 5 The CA certificate is now imported Click Finish to close the wizard 420 IBM XIV Storage System Architecture and Implementation After the CA and server certificates are imported into the local keystore you can then use the local certificate management tool to check whether the certificates are correctly imported Open the Console Root Certificates Local Computer Personal Certificates folder and select the certificate issued to xivhostl xivhostlldap storage tucson ibm com Figure B 11 shows that the certificate that was issued to xivhostl xivhostlldap storage tucson ibm com is valid and was issued by the xivstorage CA The certificate has a corresponding private key in the keystore The Ensures the identity of the remote computer text indicates that the certificate has the required server authentication key usage defined Certificate El Ed This certificate is intended for the following purposefs eEnsures the identity of a remote computer Issued to xivhostl xivhostildap storage tucson ibm com
241. ates an amount of hard space that is equivalent to the size defined for the pool by the administrator Figure A 1 Thin provisioning at the system level 396 IBM XIV Storage System Architecture and Implementation Regular storage pool conceptual example Next Figure A 2 represents a focused view of the regular storage pool that is shown in Figure A 1 on page 396 and shows the division of both soft and hard capacity among volumes within the pool The regular pool is the same size 102 GB in both diagrams Regular Provisioning Example Storage Pool with Volumes Volume 1 The block definition allows Even for block defined volumes For a Regular Storage Pool Allocated Soft hosts to see a precise the system allocates logical the soft size and hard size are Space number of blocks capacity in increments of 17GB equal A J o Volume 1 Size 10GP Block Definition Volume 2 Size Snapshot Reserve gt gt w D fe ir gt gt 4 gt oa Volume 1 Consumed Volume 2 Consumed Unused Snapshot Reserve Unused Hard Space Hard Space v v Volume 1 Volume 2 Allocated Hard Allocated Hard In a Regular Storage Pool the maximum Space Space The consumed hard space grows as hard space available to be consumed by a host writes accumulate to new areas volume is guaranteed to be equal to the of th
242. ation enables continuity of operations so that all scripts relying on this association continue to work Optional account attributes In this section we describe optional attributes for email and phone numbers gt Email Email is used to notify specific users about events through email messages Email addresses must follow standard formatting procedures Acceptable value Any valid email address A default value is not defined gt Phone and area code Phone numbers are used to send SMS messages to notify specific users about system events Phone numbers and area codes can be a maximum of 63 digits hyphens and periods Acceptable value Any valid telephone number A default value is not defined 5 5 2 Managing user accounts with the XIV Storage Management GUI This section illustrates the use of the XIV Storage Management GUI in native authentication mode for creating and managing user accounts as well as for creating user groups and defining group membership Adding users with the XIV Storage Management GUI The following steps require that you initially log on to the XIV Storage System with storage administrator access rights storageadmin role If this is the first time that you are accessing the system use the predefined user admin default password adminadmin 190 IBM XIV Storage System Architecture and Implementation Follow these steps 1 Open the XIV Storage Management GUI and log on as shown in Figure 5 21
243. ator first _expiration event 30 bind time limit 30 To complete our description of the LDAP related configuration parameters at the XIV Storage System we must describe the parameters that had default values assigned and did not need to be set explicitly version Version of the LDAP protocol used the default is 3 This parameter must never be changed Both Active Directory and Sun Java Services Directory Server Enterprise Edition support LDAP protocol Version 3 user_id attrib LDAP attribute set to identify the user in addition to user name when recording user operations in the XIV event log The default objectSiD value corresponds to the existing attribute name in Active Directory LDAP object class use ss Indicates if secure SSL encrypted LDAP communication is mandated The default value is no If set to yes without configuring both sides for SSL encrypted communication LDAP authentication fails at the XIV Storage System first_expiration_event Number of days before the expiration of the certificate to set the first alert Severity warning Set this parameter to a number of days that gives you enough time to generate and deploy a new security certificate second expiration event Number of days before the expiration of the certificate to set the second alert Severity warning third expiration event Number of days before the expiration of the certificate to set the third alert Severity warning Now that
244. ator when using the XIV Storage Management GUI in direct mode XIV Storage Management command line interface The XCLI is a powerful text based tool that enables you to issue simple commands to configure manage or maintain the system including commands used to connect to hosts and applications The XCLI interface can be used in an XCLI Session environment to interactively configure the system or as part of a script to perform lengthy and complex tasks Tip The XIV Storage Management GUI executes XCLI commands during its operation Therefore anything that is available in the XIV Storage Management GUI can also be achieved through XCLI This chapter presents some of the common XCLI commands used by the administrator to interact with the system XIV Storage Management Top graphical user interface The XIV Storage Management Top GUI provides the user with a simple tool for monitoring system performance on a host and volume level See Chapter 7 Monitoring on page 285 for more information Chapter 4 IBM XIV Storage Management software 105 4 2 XIV Storage Management software installation This section illustrates the step by step installation of the XIV Storage Management software under Microsoft Windows 2008 GUI software Although the illustrations in this chapter apply to an IBM XIV Storage System Gen3 the Version 4 3 XIV Storage Management GUI software also can be used with XIV Storage System second generation systems Users
245. ault gateway optional The default and highest possible MTU is 9000 MTU Note With Model 214 10 GbE the number of iSCSI ports is divided in half per Interface Module but because there are 10 GbE ports the iSCSI bandwidth is five times greater than with Model 114 and Model 214 1 GbE Chapter 3 IBM XIV architecture components and planning 83 3 1 9 InfiniBand module interconnect The internal network is based on two redundant 36 port InfiniBand switches InfiniBand is a switch fabric architecture characterized as fast with low latency Each of the modules Data or Interface has an InfiniBand HCA that is cabled to each of the InfiniBand switches The switches are also linked to each other See Figure 3 22 for a logical view of this connectivity For external views of the adapter and its ports see Figure 3 15 on page 75 Figure 3 19 on page 80 and Figure 3 20 on page 81 Module 1 Module 2 ae Module 15 Figure 3 22 InfiniBand internal cabling This network topology enables maximum bandwidth usage because the switches are used in an active active configuration The InfiniBand switches are also tolerant to any failure of the following individual network components gt Ports gt Links gt Switches Figure 3 23 shows the two InfiniBand switches installed in the XIV rack The cabling has been removed from the top InfiniBand switch to show a better view of the switch itself Figure 3 23 Model 114 dual 36 port InfiniBa
246. be deleted and select Delete 2 Click to delete the volume Maintaining volumes There are various other operations that can be issued on a volume See Menu option actions on page 150 for more information The usage of these operations is obvious and you can initiate an operation by right clicking one These following operations are available gt Format a volume A formatted volume returns zeros as a response to any read command The formatting of the volume is done logically and no data is written to the physical storage space allocated for the volume Consequently the formatting action is performed instantly gt Rename a volume A volume can be renamed to a unique name in the system A locked volume can also be renamed gt Lock and unlock a volume You can lock a volume so that hosts cannot write to it A volume that is locked is write protected so that hosts can read the data stored on it but they cannot change it The volume displays then as a lock icon In addition a locked volume cannot be formatted or resized In general locking a volume prevents any operation other than deletion that changes the volume s image Lock and unlock Master volumes are set to unlocked when they are created Snapshots are set to locked when they are created gt Consistency groups XIV Storage System enables a higher level of volume management provided by grouping volumes and snapshots into sets called consistency groups This gro
247. bed for Tivoli Storage Productivity Center to collect detailed information Probes use agents to collect statistics including data about drives pools and volumes The results of the probe jobs are stored in the repository and are used in Tivoli Storage Productivity Center to supply the data necessary for generating a number of reports including Asset Capacity and Storage Subsystem reports To configure the probe for XIV Storage System continue the following steps in the wizard 1 Select the XIV Storage System and click Next Now you have various options to specify the probe details as shown in Figure 7 83 on page 358 Chapter 7 Monitoring 357 358 i Configure Devices Specify data collection Select Device Type v P Specify how the data will be collected From the storage subsystems If managing a collection of devices in w Select Device the same manner a monitoring group should be applied IF the device should be monitored in a unique way S Data Collection choose a monitoring template IF a monitoring template is chosen provide a prefix that will be applied to th created probes and alerts in order to ensure their names are unique Summary Results Use a monitoring group or template Monitoring Group 7 Subsystem Advanced Group Subsystem Advanced Group Subsystem Basic Group Subsystem Standard Group Select monitoring group TRCUser Subsystem Adyance Run repeatedly beginning a Repeat Ever
248. behalf of the xivtestuser2 user in the dc xivauth Sun Java Directory repository w pwd2remember The current password of the xivtestuser2 user uid xivtestuser2 Specifies what object to search The output of the Idapsearch command shows the structure of the object found We do not need to describe every attribute of the returned object but at least two attributes must be checked to validate the response gt uid xivtestuser2 gt description Storage Administrator The fact that 1dapsearch returns the expected results in our example indicates the following 1 The account is registered in Sun Java Directory 2 We know where in the Sun Java Directory repository the account is located 3 We know the valid password 4 The designated attribute description has a predefined value of Storage Administrator When the Sun Java Directory account verification is complete we proceed with configuring XIV Storage System for LDAP authentication mode We still have a few unassigned LDAP related configuration parameters in our XIV Storage System as shown in Example B 5 Example B 5 Remaining XIV LDAP configuration parameters gt gt Idap_ config get Name Value base_dn Xiv_group_ attrib description third expiration event 7 version 3 user_id attrib objectSiD 414 IBM XIV Storage System Architecture and Implementation current_server use ss session_cache_period second expiration event read only role storage admin role first _expi
249. belongs to a consistency group cannot be moved without moving the entire consistency group As shown in Figure 4 48 in the Volume by Pools view right click the appropriate volume and initiate a Move to Pool operation to change the location of a volume aiw XIV Storage Management Systems Actions View Tools Help ih QJ a Add Volumes E Add Pool Th Co j All Systems 8 gt Littleton 5 gt Volumes by Pools OLS Name Size GB Used GB f e CKO_Thin_01 Resize a Delete t cko_vol_004 Format E cko_vol_002 cko vol_003 Rename LA i s Create a Consistency Group With Selected Volumes cko_vol_005 test_001 test_mirror_002 cofares_dr Move to Pool Create Snapshot ex_pool Create Snapshot Advanced Mike Copy this Volume Primary site Create Mirror Ge amp G windows prd Map selected volumes Map selected volumes manually View Volume Mapping Show statistics Apollo 1300474 Properties Figure 4 48 Volumes by Pools view Chapter 4 IBM XIV Storage Management software 143 In the pop up window select the appropriate storage pool as shown in Figure 4 49 Click OK to move the volume into this pool Move Volume to Pool Select Pool Tso r a Tso hannes ee e e lt o Figure 4 49 Move volume to another pool Pool alert thresholds You can use the XIV Storage Management GUI to configure pool usage thresholds to trigger color coded visual al
250. ble 3 3 XIV power consumption Model 281x 114 Model 281x 214 With SSDs in Without SSDs With SSDs in Without SSDs kVA High in kVA High kVA High in kVA High of disk performance performance performance performance drives Idle Idle Idle Idle 46 4 4 1 3 7 5 1 47 45 4 0 44 40 5 59 55 49 59 5 2 Important Model 214 reduces power consumption by up to 16 compared to previous models and generations thanks to the high efficiency power supply unit PSU and the new six core CPUs Thermal dissipation Table 3 4 indicates the cooling thermal dissipation requirements for a 15 module rack To support capacity upgrades the installation site must provide cooling capacity to support full rack configurations Table 3 4 Thermal dissipation Modeltype Thermal dissipation kBTU hour 1 TB limited capacity eolx 114 227 22 7 24 0 19 1 20 1 20 5 2814 214 19 1 Physical space requirements The physical requirements for the room where the XIV Storage System will be installed must be checked ahead of the arrival of the machine IBM assists with this activity For the latest and most accurate information see the IBM XIV Storage System Gen3 Models 281x 11x and 281x 21x Planning Guide SC27 5412 gt The floor must be able to withstand the weight of a fully co
251. c tools coupled with intelligent analysis and low tolerance thresholds provide an even greater level of refinement of the disk behavior diagnostic tests and the performance and reliability driven reaction For example the XIV Storage System measures the specific values of parameters including but not limited to these possibilities gt Reallocated sector count f the disk encounters a read or write verification error it designates the affected sector as reallocated and relocates the data to a reserved area of spare space on the disk This spare space is a parameter of the drive itself and is not related in any way to the system reserve spare capacity that is described in Global spare Capacity on page 31 gt Disk temperature The disk temperature is a critical factor that contributes to premature drive failure and is constantly monitored by the system gt Raw read error The raw read error count provides an indication of the condition of the magnetic surface of the disk platters and is carefully monitored by the system to ensure the integrity of the magnetic media itself gt Spin up time The spin up time is a measure of the average time that is required for a spindle to accelerate from zero to 7200 rpm The XIV Storage System recognizes abnormal spin up time as a potential indicator of an impending mechanical failure Likewise for additional early warning signs the XIV Storage System continually monitors other aspects of
252. can be created gt Group names are case sensitive gt In native authentication mode a user group can contain up to eight members gt If auser group is defined with access all yes users assigned to the applicationadmin role who are members of that group can manage all snapshots on the system gt A user must be assigned to the storageadmin role to be permitted to create and manage user groups Important A user group membership can be defined only for users assigned to the applicationadmin role User group and host associations Hosts and clusters can be associated with only a single user group When a user is a member of a user group that is associated with a host that user is allowed to manage snapshots of the volumes mapped to that host User group and host associations have the following properties gt User groups can be associated with both hosts and clusters This configuration enables limiting group member access to specific volumes gt Ahost that is part of a cluster can be associated only with a user group through user group to cluster association Any attempts to create user group association for that host fail gt When a host is added to a cluster the association of that host is removed Limitations on the management of volumes mapped to the host is controlled by the association of the cluster gt When a host is removed from a cluster the association of that cluster remains unchanged This configur
253. capabilities to the new drive or module When a replacement module is phased in there are concurrently 168 disks reading and 12 disks writing Therefore the time to completion is determined by the data throughput to the replacement module While the read frequency to the existing disks is low a low impact on host performance during the process is guaranteed When a replacement disk is phased in there are concurrently 179 disks reading and only one disk writing In this case the new drive determines the achievable throughput of the redistribution process Again the impact on host transactions is small and not noticeable Transient soft and hard system size Capacity that is required for restoring non redundant data during a rebuild is depending on availability obtained in this order gt Deallocated system hard capacity Hard capacity that was not assigned to any storage pools at the time of the failure gt Reserve spare capacity The system reserves enough capacity to sustain the consecutive non concurrent failure of three drives and an entire module If it is already consumed replacement hardware must be phased in to ensure that data redundancy can be restored When sufficient deallocated hard capacity is available the system withholds allocating reserve spare space to complete the rebuild or phase out process to provide additional protection As a result it is possible for the system to report a maximum soft size that
254. cation mode user group membership cannot be defined using the XIV Storage Management GUI or XCLI The group membership is determined at the time the LDAP authenticated user logs in to the XIV Storage System based on the information stored in the LDAP directory A detailed description of the process of determining user group membership can be found in 5 6 4 LDAP role mapping on page 208 Starting with XIV Storage System software V10 2 2 it is now possible to delete user groups when LDAP authentication is enabled Chapter 5 Security 233 5 8 3 Managing user groups using XCLI in LDAP authentication mode Various commands and options are available to manage user groups roles and associated host resources through the XCLI To use the XIV Storage Management GUI to define user groups complete the following steps 1 Run user_group create as shown in Example 5 16 to create a user group called itso _app02 group with the corresponding LDAP role itso _app01_admin Example 5 16 XCLI user_group_create in LDAP authentication mode gt gt user group create user _group itso app02 group Idap_role CN itso_app02 admin CN Users DC itso DC storage DC i1bm DC com Command executed successfully Spaces Avoid spaces in user group names If spaces are required the group name must be placed between single quotation marks such as name with spaces The itso _app02 group user group is empty and has no associated hosts or clusters The next s
255. ccess right set to no This user can now perform snapshots of volumes mapped to the hosts ITSO Apphost1 and ITSO Apphostz The user can also map unmap and delete snapshots from the application group 5 5 3 Security considerations when using Hyper Scale Manager Hyper Scale Manager allows access and distributes tasks among the following users gt Root user The Root user is an OS super user that carries out administrative tasks gt Server Admin user The Server Admin carries out inventory configuration tasks gt Maintenance user The Maintenance user carries out Hyper Scale Manager configuration tasks This user is the client s way to interact with any of the Hyper Scale Manager operations using Secure File Transfer Protocol SFTP such as setting logs copying the upgrade file and getting backups Chapter 5 Security 197 Note This section is meant as information only For more assistance and directions see the IBM XIV Storage System Management Tools Version 4 0 User Guide SC27 4230 00 Root user operations The menu that is shown in Figure 5 36 list various configuration options for the Hyper Scale Manager tool which is available for the root user Security options are under 5 and 6 The Hyper Scale Manager user must log in to the Hyper Scale Manager with root credentials to access the menu items Refer to the IBM XIV Storage System Management Tools Version 4 0 User Guide SC27 4230 00 for detailed instructions The LDAP serve
256. ce limitation and that is the full performance potential of the entire XIV Storage System which includes all disks and modules in the XIV Storage System configuration The consequence of this massive parallel approach and the way data is effectively laid out within the XIV Storage System grid is that LUNs can be easily resized without physical disk layout concerns It is unlikely that an XIV Storage System LUN will ever be reconfigured for performance reasons Chapter 6 Performance 249 What if you add more than one application to a host server and consider multiple host systems in a typical client computing environment For traditional storage systems where RAID arrays or groups of arrays are dedicated to an application the considerations for providing the adequate number of disk drives to handle the application performance requirements increase linearly with the number of applications These groups of arrays become islands within the traditional storage system Realistically several of these islands are sized correctly for the application s performance requirements where others are oversized to handle application performance growth projections The islands that are undersized are a performance bottleneck problem that must be addressed For the XIV Storage System there are no special considerations for multiple applications on multiple application servers If there is adequate spare performance capacity in the XIV Storage System to handle the
257. certificate needs to be added to the key ring file used by the OpenLDAP client The TLS_CERTS option in the OpenLDAP configuration file typically etc openldap 1dap conf specifies the file that contains certificates for all of the certificate authorities the client recognizes See Example B 10 Example B 10 Testing LDAP over SSL by using the Idapsearch command usr bin ldapsearch x H ldaps xivhostl xivhostlldap storage tucson ibm com 636 D CN xivtestuserl CN Users DC xivhost1ldap DC storage DC tucson DC ibm DC com w pass2remember b CN Users DC xivhost1ldap DC storage DC tucson DC ibm DC com dn CN xivtestuserl CN Users DC xivhost1ldap DC storage DC tucson DC ibm DC com objectClass top objectClass person objectClass organizational Person objectClass user cn xivtestuserl description Storage Administrator distinguishedName CN xivtestuserl CN Users DC xivhostlldap DC storage DC tucs on DC ibm DC com search result search 2 result 0 Success The Uniform Resource Identifier URI format used with the H option specifies that LDAPS must be used on port 636 the LDAP secure port Appendix B Additional LDAP information 423 Sun Java Directory SSL configuration 424 This section describes the usage of an SSL protocol for communicating with the Sun Java Directory Creating a Sun Java Directory certificate request To configure SSL for Sun Java LDAP Directory you must create a CER and ha
258. cess the System Selector menu Chapter 4 IBM XIV Storage Management software 123 When activated the System Selector menu is displayed as illustrated in Figure 4 27 uv XWV Storage Management Systems l Actions View Tools Help ih lt lt A AllSystems 7 a Connectivity system Selector ioe All Systems ik e Apollo 1300474 f Starbuck MN00027 A Littleton J Toaster MN00016 4 of 4 Systems P XIV Galactica 1340009 E f xiv 1310062 Dantooine nf f xiv 1310077 Alba A Tucson Lab f xiv 7826153 3 of 3 Systems Figure 4 27 The System Selector menu Tip To select multiple systems from the System Selector menu hold the Ctrl key while clicking each system Views Selector menu The GUI supports several view styles for displaying information about the systems being managed To change the current view use the Views Selector menu by pressing Alt X or by clicking the triangle icon at the far right of the hierarchical navigation as shown in Figure 4 28 av ATV Storage Management systems Actions View Tools Help ih A AllSystems 8 Connectivi Figure 4 28 Views Selector menu When viewing all systems or a group of systems three useful views are available Use the Views Selector menu to modify the current view to best suit the management task you are performing The Connectivity view as seen in Figure 4 29 on page 125 provides a three dimensional view of the s
259. cessor and cache complex To communicate with the SAS drives this HBA uses the SAS 2 0 standard which is a performance improvement over its SAS 1 0 predecessor This SAS HBA also realizes processor efficiencies because it does not have to complete a SAS to SATA conversion SAS also outperforms SATA because unlike SATA it features full duplex communication with each disk SAS disk drives XIV Storage System Gen3 modules can be configured with 2 TB 3 TB SAS drives Drive sizes cannot be intermixed within the same XIV Storage System These drives use the SAS 2 0 protocol and run at 7200 rpm They incorporate industry standard Self Monitoring Analysis and Reporting Technology SMART for enhanced reliability through prediction and early recognition of drive failure conditions The drive itself has data prefetch and cache drive buffer storage control algorithms that improve drive performance These drives are also capable of the following reliability features gt Background media scan to detect drive media errors gt Media pre scan to allow the drive to repair media errors gt Deferred auto reallocation which allows the drive to reallocate unreadable locations on a subsequent write command gt Idle read after write which uses drive idle time to verify the integrity of recently written data This SAS drive also exhibits significant performance gains for large block I O All XIV Storage System disks are installed in the front of the modu
260. ching with optional flash cache coupled with high density storage to reduce the footprint and address energy efficiency while sustaining the performance 2 1 1 Features The XIV Storage System architecture incorporates various features designed to uniformly distribute data across internal resources This unique data distribution method fundamentally differentiates the XIV Storage System from conventional storage subsystems offering numerous availability performance and management benefits across both physical and logical elements of the system The XIV Storage System has a native virtual storage design that is both efficient and simple to use It eliminates all physical disk Redundant Array of Independent Disks RAID management tasks The XIV Storage System is basically an Enterprise Class storage system where storage management involves defining capacity a logical unit number LUN ora volume and assigning the capacity to a host system The XIV Storage System hardware architecture is a dramatic shift from traditional RAID based parity data protection From a performance perspective the XIV Storage System is able to automatically involve all of the disk drives the whole system cache including its optional flash cache extension and processors in doing the work of handling I O Scalability is also a strength of the XIV Storage System The XIV Storage System is able to scale without administrative involvement to redistribute data or tune for
261. chitecture resilient to a failure of any individual network switch or module gt Single switch configuration A single switch interconnects all modules and hosts gt Single port host solution Each host connects to a single switch and a switch is connected to two modules IP configuration The configuration of the XIV Storage System iSCSI connection is dependent on your network In the high availability configuration the two client provided Ethernet switches used for redundancy can be configured as either two IP subnets or as part of the same subnet The XIV Storage System iSCSI configuration must match the client s network You must provide the following configuration information for each Ethernet port gt IP address gt Netmask gt MTU optional MTU configuration is required if your network supports an MTU which differs from the standard one The largest possible MTU must be specified From the XIV Storage System with software Version 11 2 or later the largest MTU size is increased to 9000 If the iSCSI hosts are on another subnet than the XIV Storage System a default IP gateway per port must be specified Important An XIV Storage System running on software Version 11 2 or later has an increased largest possible MTU size of 9000 gt Default gateway optional Because the XIV Storage System always acts as a Transmission Control Protocol TCP server for iSCSI connections packets are always routed through the Etherne
262. components from failing because of power problems all power components in the XIV Storage System are redundant gt To protect against loss of client utility power the XIV Storage System is designed to attach to two independent power sources XIV supplies two power cables that should be plugged into redundant external power sources The other ends of the redundant cables are routed inside the XIV rack and attached to the XIV Automatic Transfer Switch ATS For most XIV power solutions the ATS allows power from one of the redundant feeds to power the XIV rack If there is an external power failure the ATS transfers the load to the redundant power cord gt The XIV Storage System has three internal UPSs The XIV Storage System can run on two of these UPSs so that no system component loses power if one of the three UPSs experiences a hardware failure This redundant design is n 1 because the XIV Storage System has one redundant UPS Chapter 3 IBM XIV architecture components and planning gt The UPS complex has enough battery reserves to sustain two emergency power shutdowns gt Each module has two independent power supplies During normal operation both power supplies operate on half of the maximal load If one power supply fails the remaining operational power supply can take over and the module continues its operation without any noticeable impact After the failing power supply is replaced the power load balancing is restor
263. control panel on the front of the UPS as illustrated in Figure 3 32 E E E E F ATERI Figure 3 32 Locate Test button Important Do not confuse the Test button with the power off button which is normally protected by a cover The Test button is the one circled in Figure 3 32 2 Use both hands as shown in Figure 3 33 on page 100 to press each of the three Test buttons simultaneously Chapter 3 IBM XIV architecture components and planning 99 Figure 3 33 Use both hands to press the three Test buttons simultaneously This action starts applying power to the components in the rack and initiates the boot process for the Interface Modules and Data Modules Powering off the system Powering off the system must be done solely from either the XIV Storage Management GUI or the XCLI You must be logged on as Storage Administrator the storageadmin role Important Do not power off the XIV Storage System using the UPS power button because this action can result in the loss of data and system configuration information Using the XIV Storage Management GUI From the XIV Storage Management GUI complete the following steps 1 Click Systems System Settings in the system main window toolbar and click Shutdown System as shown in Figure 3 34 xiv XIV Storage Management CZAI Actions view Tools Hep T Settings BM Launch xc BJ Launch xivTop ten System Settings System Import Systems File LDAP
264. controlled by using XCLI and is charged with starting a connection terminating a connection because of timeout or client request and trying the connection again in case it terminates unexpectedly gt Optional Remote Support Proxy The Remote Support Client can access the Remote Support Center Front Server directly or through an optional proxy server The optional Remote Support Proxy can be used when one or more IBM XIV systems do not have direct access to the Internet for example because of firewall restrictions You can use the Remote Support Proxy to facilitate the connection to the XRSC More information about the Remote Support Proxy can be found in the IBM XIV Remote Support Proxy Installation and User s Guide GA32 0795 gt Remote Support Center Front Server Internet Front Servers are on an IBM DMZ of the Internet and receive connections from the Remote Support Client and the IBM XIV Remote Support Back Server Front Servers are security hardened machines that provide a minimal set of services namely maintaining connectivity to connected Clients and to the Back Server They are strictly inbound and never initiate anything on their own accord No sensitive information is ever stored on the Front Server and all data passing through the Front Server from the Client to the Back Server is encrypted so that the Front Server cannot access this data Chapter 7 Monitoring 327 328 gt Remote Support Center Back Server IBM
265. corporates innovative provisions to mitigate isolated disk level performance anomalies through redundancy supported reaction This topic is described in Redundancy supported reaction on page 55 Flexible handling of dirty data is described in Flexible handling of dirty data on page 55 Disaster recovery Enterprise class environments must account for the possibility of the loss of both the system and all of the data as a result of a disaster The XIV Storage System includes the provision for remote mirror functionality as a fundamental component of the overall disaster recovery strategy Write path redundancy Data arriving from the hosts is temporarily placed in two separate caches before the XIV Storage System acknowledges that the write is received and begins to write the data to the disk drives in separate modules This design guarantees that the data is always protected against possible failure of individual modules even before the data is written to the disk drives Chapter 2 IBM XIV Storage System logical architecture and concepts 45 46 Figure 2 10 illustrates the path that is taken by a write request as it travels through the system Hosts issue write lOs to the subsystem via the FC and or iSCSI ports on the Interface Modules Multi path is managed on the host side Os flow between modules over the redundant switched ethernet fabric Data is written to two Data Modules bef sts receive lO complete
266. cted workload patterns Figure 2 7 XIV flash caching overview The caching algorithm is embedded in the XIV System software firmware and makes the flash cache integration completely transparent to the user or storage administrator No tuning of the cache is required to get the potential performance boost The flash caching feature is supported automatically by the XIV unique caching algorithm which dynamically adapts to detected I O request patterns 2 5 2 Flash caching algorithm and concepts Caching operations are split into two groups main and extended gt The main cache handles host write I Os and then destages them directly to the disk drive gt The extended cache handles the caching of random read miss operations less than 64 KB Sequential read prefetches larger than 64 KB are handled in main dynamic random access memory DRAM cache Flash caching For more details about flash caching see the Redpaper publication Solid State Drive Caching Implementation in the IBM XIV Storage System REDP 4842 A flash cache map is built as read misses occur in the DRAM cache which is known as flash cache learning The process is depicted in Figure 2 8 on page 42 Chapter 2 IBM XIV Storage System logical architecture and concepts 41 If Read data lt 64KB and Read Miss Operation Host requests random data andit is not in DRAM uiters D Checks for hit on extended cache Flash l f hit data is moved fro
267. ction covers the following topics gt XIV Host Attachment Kit overview gt Portable XIV Host Attachment Kit gt XIV Host Profiler XHoP Chapter 7 Monitoring 389 7 10 1 XIV Host Attachment Kit overview The IBM XIV Host Attachment Kit HAK is a software package that simplifies connecting the XIV Storage System to a host It provides a CLI tool to simplify different host side tasks Storage Area Network SAN Boot OS fram SAN optional Fibre Channel FC fabric or SUSE Oracle Solaris or Microsoft Windows Server or IBM XIV Ethernet LAN WAN Storage f System i Host operating system OS IBM AIX HP UNIX Linux RedHat Private network IBM XIW FASB Sore Ale E N Sieg ae nape p r A A Host Attachment Kit Detection and Storage pools i management of XIV ul storage systems and jinside the IBM XIV Storage System Figure 7 116 Host Attachment Kit in relation to XIV HAK supports different operating systems and is available for the following platforms Windows AIX Linux HP UX and Solaris For more detailed information about the different versions of the supported operating systems see the correct release notes You can perform the following functions with the HAK gt Properly configure the host to work with XIV operating system and native multipathing configuration Detect IBM XIV systems physically connected to the host and define the host and ports on the
268. ction icons is shown in Figure 4 17 on page 118 gt Main Display This area provides a graphical representation of the XIV Storage System Move the cursor over a specific hardware component module disk and uninterruptible power supply UPS unit to open a status callout for that component Additionally click the arrow to the lower right of the system to see a view of the system patch panel Move the cursor over a port to open a status callout for that port gt Menu Bar This area is used for configuring the system and as an alternative to the function icons Also various user tools pertaining to XIV Storage System are available here gt Tool Bar This area contains a dynamic contextual set of actions based on the current view gt User Indicator Identifies the current authenticated user Click the user indicator to log in with alternate credentials gt System Info Menu Displays details about the current system To change the displayed details click the small triangle menu at the left of this menu Available details for display include the following Hardware details System Time The time on the XIV System 116 IBM XIV Storage System Architecture and Implementation Local Time The time on the management workstation running the GUI System software version gt Hierarchical Navigation Provides a hierarchical view of the current system or group with contextual drop down menus gt Current System s I
269. d Full Name cn xivtestuser2 Last Name sn xivtestuser facsimileTelephoneN umber eee xivtestuser2 OOOO Storage Administrator muuu Figure B 7 Entering object attribute values IBM XIV Storage System Architecture and Implementation 5 A Summary window Figure B 8 shows what you have selected and entered in the previous steps You can go back and change parameters if you want to do so Otherwise proceed with the entry creation Step 5 Summary Review your settings and click finish if they are correct Entry DH uid xivtestuser2 dc xivauth Object Class User inetQrg Person Full Hame cm x vtestuserz Last Name sn xivtestuser2 description Storage Administrator User ID uid xivtestuserz Password userPassword PEPEEREEEEEEEEEEE DEE EES Cancel Figure B 8 Reviewing entry settings If all the information was entered correctly you get an Operation Completed Successfully message in the window that opens Figure B 9 If the operation failed for one reason or another you must go back and make necessary changes before resubmitting your request ey Operation Completed Successfully The Entry was successfully created Creating New Entry on xivhost2 storage tucson ibm com 389 Creating entry vid xivtestuser2 dc xivauth on Directory Server xivhost2 storage tucson ibm com 389 Done Operation Completed Successfully Close window upon completion
270. d Type Access Problems Compliance IP Addres La nextrabarni storage tucson ibm com Previous Operating System ox ox ox 3 11 237 119 La nextrabarmd storage tucson ibr com Previous Operating System on on ox B11 237 123 La nextrabarm2 storage tucson ibm com Previous Operating System on ox ox 3 11 237 121 Figure 7 73 View and collect inventory At this point the IBM Systems Director is ready to receive SNMP traps from the discovered IBM XIV system 4 To review select Inventory gt View and Collect Inventory Refresh View With the IBM Systems Director you can display general information about your IBM XIV systems monitor the event log and browse more information Event log To open the event log right click the corresponding IBM XIV Storage System within the View and Collect Inventory window and select Event Log within System Status and Health from the pop up menu that is shown in Figure 7 74 Discover How E Stopping discovery protocols Schedule Create Group Remove Rename Discovered Manageable Systems acions Add ta Acti iai ESSEE Automation Performance Summar Hame menta Active Status i Release Management Ewent Log Remote Access Security hd o nite rs Network Diagnostics SNMP Browser La nextrabarmd storage tucson ibm co La nextrabam2 storage tucson ibm co System Configuration A xivbarmn storage tucson ibrn com b b b b b b p b
271. d as described in 7 3 Call home and remote support on page 324 A problem record is generated with XIV Storage System Support and an IBM service support representative SSR contacts the client to report the problem and follow up with repair actions Event Properties System XIV_PFE_04 1310133 Severity Major Date Local Time 2 28 13 5 01 PM Index 290 707 Event Code COMPONENT NETWORK _LINK_IS DOWN T Shooting Please contact support Description Network interface to 1 MaintenanceModule 16 on 1 NIC 3 5 link disconnected Figure 7 14 Event properties Event severity The events are classified into a level of severity depending on their effect on the system Figure 7 15 gives an overview of the criteria and meaning of the various severity levels Severity The Events are categorized in these five categories K n Critical Critical an event have occured where one ore more parts have failed and the redundancy and machine operation can be affected XN Major Major an event have occured where a part have failed and the redundancy is temporary affected ex failing disk x Minor Minor an event occured where a part have failed but system is still fully redundant and have no operational impact iss Warning Warning information for the user that something in the system have changed but no impact for the system en Informational Informational event is for information only without
272. d you can proceed with LDAP entry creation To create an LDAP entry login to the Java Console using your own user ID and password select the Directory Service Control Center DSCC link in the Services section Authenticate to Directory Service Manager application In the Common Tasks tab click Directory Entry Management Create New Entry 408 IBM XIV Storage System Architecture and Implementation Now you can start the New Entry configuration wizard by completing the following steps 1 Select a server instance Sun Java Directory allows you to create multiple instances of an LDAP server However the only instance that uses port 389 for non SSL LDAP and port 636 for SSL LDAP communication can be used for XIV LDAP authentication services Select an instance configured on port 384 as shown in Figure B 4 Step 1 Specify the Directory Server Choose the Directory Server where the entry will be created Server xivhost storage tucson ibm com 389 Cancel Figure B 4 Selecting a Directory Server instance 2 Select the new entry location as shown in Figure B 5 The LDAP administrator determines the location of a new entry Unlike the Active Directory LDAP repository where location is directly linked to the domain name Sun Java Directory LDAP server provides greater flexibility in terms of placement for the new entry Step 2 Specify Entry Location Provide the location ON where the entry will be written in the Di
273. d configurations A fully populated rack contains nine Data Modules and six Interface Modules for a total of 15 modules The total usable capacity is 161 TB for a complete system when equipped with 2 TB drives 243 TB of usable capacity when fully populated with 3 TB drives and 422 TB of usable capacity when fully populated with 4 TB drives Because each module in Model 214 contains up to 48 GB of memory in the 4 TB disk configuration a full rack contains up to 720 GB of memory that can be used to handle host read and write I O requests Model 114 has up to 24 GB installed per module which equates to 360 GB for the full rack The SSD extended caching option adds 400 GB of read cache capacity to each module for a total of 6 TB in a fully populated configuration 15 modules In the 4 TB version of the Model 214 the flash cache option can be ordered in 800 GB of read cache capacity to each module for a total of 12 TB in a fully populated configuration 15 modules Summary gt Each Interface Module of the XIV Gen3 Model 114 contains four 8 Gbps Fibre Channel ports and one 4 port 1 GbE adapter except Interface Module 4 which has only two iSCSI ports gt Each Interface Module of the XIV Gen3 Model 214 1 GbE contains four 8 Gbps Fibre Channel ports and one 4 port 1 GbE adapter except Interface Module 4 which has only two iSCSI ports gt Each Interface Module of the XIV Gen3 Model 214 10 GbE contains four 8 Gbps Fibre Channel
274. d for products and services offered in the U S A IBM may not offer the products services or features discussed in this document in other countries Consult your local IBM representative for information on the products and services currently available in your area Any reference to an IBM product program or service is not intended to state or imply that only that IBM product program or service may be used Any functionally equivalent product program or service that does not infringe any IBM intellectual property right may be used instead However it is the user s responsibility to evaluate and verify the operation of any non IBM product program or service IBM may have patents or pending patent applications covering subject matter described in this document The furnishing of this document does not grant you any license to these patents You can send license inquiries in writing to IBM Director of Licensing IBM Corporation North Castle Drive Armonk NY 10504 1785 U S A The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS OR IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF NON INFRINGEMENT MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE Some states do not allow disclaimer of express or implied warranties in cer
275. d out more about the residency program browse the residency index and apply online at ibm com redbooks residencies html Comments welcome Your comments are important to us We want our books to be as helpful as possible Send us your comments about this book or other IBM Redbooks publications in one of the following ways gt Use the online Contact us review IBM Redbooks publications form found at ibm com redbooks gt Send your comments in an email to redbooks us ibm com gt Mail your comments to IBM Corporation International Technical Support Organization Dept HYTD Mail Station P099 Preface xiii 2455 South Road Poughkeepsie NY 12601 5400 Stay connected to IBM Redbooks publications XIV Find us on Facebook http www facebook com IBMRedbooks Follow us on twitter http twitter com ibmredbooks Look for us on LinkedIn http www linkedin com groups home amp gid 2130806 Explore new Redbooks publications residencies and workshops with the IBM Redbooks publications weekly newsletter https www redbooks ibm com Redbooks nsf subscribe 0penForm Stay current on recent Redbooks publications with RSS Feeds http www redbooks ibm com rss html IBM XIV Storage System Architecture and Implementation Summary of changes This section describes the technical changes made in this edition of the book and in previous editions This edition might also include minor corrections and editorial changes that are
276. d the percentage that is yet to be complete is in light green Chapter 2 IBM XIV Storage System logical architecture and concepts 51 xv XIV Storage Management ie x File View Tools Help O Settings MJ Launch xcLi fj Launch xivTop itso XIV 02 1310114 System System Time 01 04pm Q enerne istributing 38 ea e E Cos m total Figure 2 12 Redistributing Important Redistribution is a low priority self tuning process during which the XIV Storage System is fully redundant Effects of a flash cache failure If a flash cache device starts to fail or fails completely it is phased out like any of the other XIV grid components There is no data loss because the flash cache is not involved in any phase of the process of storing data or maintaining data redundancy The flash caching algorithms populate the extended flash cache with copies of primary data partitions If a flash cache device fails no data is lost The flash cache degraded module continues to serve reads from its DRAM cache and large sequential reads from disk All small read misses are redirected to the secondary partition copies which are on modules with functioning flash cache This behavior evenly distributes the extended flash caching duties of the module with the failed flash device to all other modules therefore balancing the use of the remaining extended flash cache across all modules There is no rebuild or redistribution of data as a r
277. d to import the specific product packs into SCOM 7 9 3 Importing the management packs The installation of the IBM Storage Management Pack does not import the management packs themselves into SCOM You must import each specific management pack for each storage system type Complete the following steps 1 On the SCOM Administration window right click Management Packs and select Import Management Packs as shown in Figure 7 108 on page 382 The Import Management Packs window opens Chapter 7 Monitoring 381 File Edit View Go Tasks Tools Help Administration Manageme 4 8 Administration al Q Laok fa a Connected Management Groups d Marne 4 Fa Device Management Pt 360 App im Agent Managed ini i E5 Baseliniy G Agentless Managed z Client t lent gl Management Servers a Pending Management Pt Client hy H UNIMLinuxe Computers B Client M Ta Client M 2 Discovery Wizard T a C5 Network T Data Wa Discove B Create Managerment Pack Data Wg Network Download Management Packs a E Distribut ral Network Import Management Packs Z Health Figure 7 108 Importing management packs into SCOM 2 Click Add and then click Add from disk An online catalog connection message is displayed Click No to locate the management pack locally The Select Management Packs to Import window opens Select the C ProgramFiles IBM Storage Host IBMStorageSCOM mps directory and select the following two file
278. d used to analyze and possibly repair the faulty system If there is no XIV Remote Support Center XRSC or other broadband connection available the only way to connect is through the modem and Maintenance Module For more information about remote connections see XIV Remote Support Center on page 94 Modem The modem installed in the rack is optionally used for remote support if the preferred choice of XIV Remote Support Center is not selected It enables the IBM specialists and if necessary a higher level of support to connect to the XIV Problem analysis and repair actions without a remote connection can be complicated and time consuming Modem The modem is not available in all countries 86 IBM XIV Storage System Architecture and Implementation 3 2 Hardware planning overview This section provides an overview of planning considerations for the XIV Storage System including a reference listing of the information required for the setup The information in this section includes requirements for M Physical installation gt Delivery requirements gt Site requirements gt Cabling requirements For more detailed planning information see the IBM XIV Storage System Gen3 Models 281x 11x and 281x 21x Planning Guide SC27 5412 Additional documentation is available from the XIV Storage System Information Center at http publib boulder ibm com infocenter ibmxiv r2 index jsp For a smooth and efficient installation of the XIV
279. deferred until the storage capacity is needed There is a small price premium associated with purchasing CoD storage over the traditional way of paying for all storage capacity in the whole configuration up front It is common for clients to stay in the XIV Capacity on Demand program until the XIV Storage System configuration has reached nine modules and then switch to purchasing normal non CoD modules to further expand the capacity of the XIV Storage System Switching from a CoD configuration to a non CoD configuration is allowed but then you cannot later purchase more CoD capacity The most important aspect of all CoD configurations is that the system is delivered with the same hardware configuration as the non CoD system All modules are active The XIV Storage System uses the performance capabilities of all the disk drives in the configurations purchased storage and CoD de allocated and unpurchased storage This scenario means that data is initially distributed over all the drives in the entire XIV Storage System configuration There are no restrictions on the normal functionality of the XIV Storage System The full performance capacity of all the modules in the rack are used even though some of the modules are unused CoD modules The basic configuration rule to keep in mind about the XIV Storage System Gen3 CoD program is that there can be only up to three de allocated CoD modules in the configuration This configuration means that every valid
280. dentials between local and LDAP repositories or vice versa the task can be greatly simplified if the same set of rules is applied to both local and centralized repositories In fact the set of rules enforced by the XIV Storage System for local user names must be used for LDAP as well because it is the most restrictive of the two For details about XIV Storage System limitations for user names see User name on page 186 Special consideration must be given to using the space character in user names Although this feature is supported by LDAP it has a potential for making certain administrative tasks more difficult because the user names in this case must be enclosed in quotation marks to be interpreted correctly The same set of locally stored predefined user names exists on the XIV Storage System regardless of the authentication mode Users technician and admin are always authenticated locally even on a system with activated LDAP authentication mode Avoid creating LDAP user accounts with the same names If a user account with the same user name is registered in both local and LDAP repositories and LDAP authentication mode is in effect LDAP authentication takes precedence and the XIV Storage System performs authentication using LDAP account credentials The only exception to this rule is the predefined user names listed in the previous paragraph To reduce complexity and simplify maintenance it is generally not desirable to have the
281. dules 3332 IOPS If the intent is to have a 10 K IOPS limitation for a host connected to only two Interface Modules in a full six Interface Module system IOPS Limit Per Interface must be set to 5000 or IOPS Limit for the performance class needs to be set to 30 000 Users must consider these Interface Module multiplication factors to properly meet expected limitations Quality of service illustration To illustrate the QoS effect we used it with two OLTP applications one designated as critical the other noncritical running on the XIV system They were set to run at about 30 K IOPS total We repeated the test with three different levels of QoS limitations 1 K 5 K and 10 K In each test both applications start simultaneously The noncritical application uses the QoS after applications first run concurrently for 5 to 10 minutes Within one minute after enforcing QoS the critical application shows performance improvements 262 IBM XIV Storage System Architecture and Implementation The critical application in Figure 6 6 shows an IOPS improvement from 15 K to 27 K 76 by limiting noncritical OLTP host application IOPS to 1 K The critical OLTP host application IOPS also improved to 53 and 23 respectively after limiting noncritical host applications to 5 K and 10 K IOPS Six Interface Module OLTP Application vs OLTP Application IOPS Limit 1K 10K 30000 30000 loo m 1K OLTP Application 25000 ome 1K OLTP
282. e 200 shows the various commands and a brief description for each command The table also indicates the user role that is required to issue specific commands Chapter 5 Security 199 Important With XIV Storage software V11 4 a new secadmin role is introduced and required to execute specific commands related to encryption management Details are covered in the IBM Redpaper X V Security with Data at Rest Encryption REDP 5047 D S D F do gt lt QO Ea Y O O CD Y a 9 S S S Q S 3 3 D X A Command Description Role required to use command Defines an association between a user group and a access_define storageadmin host access_delete Deletes an access control storageadmin definition access_list Lists access control definitions storageadmin readonly and applicationadmin user_define Defines a new user storageadmin user_delete Deletes a user storageadmin user_list Lists all users or a specific user storageadmin readonly and applicationadmin user_rename Renames a user storageadmin user_update Updates a user You can storageadmin and rename the user change a applicationadmin password modify the Access All setting modify email area code or phone number user_group_add_user Adds a user to a user group storageadmin user_group_create Creates a user group storageadmin user_group_delete Deletes a user group storageadmin user_group_list Lists all user groups or a storagead
283. e 5 15 Update VPN IP Interface Figure 5 15 Update VPN Interface Chapter 5 Security 183 Enter the corresponding two IPv6 addresses in the fields shown in Figure 5 16 and click Update Update IP Interface VPN IPv4 Address 1 0 0 0 0 IPv4 Address 2 0 0 0 0 IPv6 Address 1 0 0 0 0 0 0 0 0 0 IPv6 Address 2 0 0 0 0 0 0 0 0 0 Netmask Default Gateway 0 0 0 0 MTU 1500 Update Cancel Figure 5 16 Update VPN port IPv6 addresses 5 4 Configuring Internet Protocol Security connectivity Internet Protocol Security IPSec is a protocol suite that allows for enhanced security of IP communications through the authentication and encryption of IP packets The XIV Storage System software and XIV Management tools allow for the use of passkey or certificate authentication to establish IPSec connectivity between management workstations and the management or VPN ports of IBM XIV systems To configure IPSec connectivity between a management workstation and an XIV Storage System perform the following steps 1 In the GUI navigate to the System view of the chosen XIV Storage System and click Systems System Settings IPSec to open the IPSec panel as shown in Figure 5 17 IPsec IPsec Connections Enable IPsec innit E Remote IP EEE EEE Close Figure 5 17 IPSec configuration 2 Click the green plus icon on the right to open the Add IPSec
284. e 7 25 Disk 12 Module 7 Capacity 2TB Temperature 0 C Status Failed Deferred Functioning yes Figure 7 25 XIV Storage System Gen3 disk in a deferred replacement state 7 1 4 Monitoring with XIV Storage System Command Line Interface The XIV Storage System Command Line Interface XCLI provides various commands to monitor the XIV Storage System and gather real time system status monitor events and retrieve statistics See 4 1 XIV Storage Management software introduction on page 104 for more information about how to set up and use the XCLI System monitoring Various XCLI commands are available for system monitoring For more information about these commands see the XCLI Utility User Manual and Commands Reference books which are available at the following website http publib boulder ibm com infocenter ibmxiv r2 index jsp Chapter 7 Monitoring 297 The state_list command which is shown in Example 7 2 gives an overview of the general status of the system In the example the system is operational data is fully redundant no shutdown is pending ssd_caching is enabled on the system level and encryption is not supported Example 7 2 The state_list command gt gt state_list Category Value system state on target state on safe mode no shutdown reason No Shutdown off type of f redundancy status Full Redundancy ssd_caching disabled encryption Not Supported In Example 7 3 the system_capaci
285. e B 8 shows how to import the signed certificate by running the certreq command Confirm that the certificate is imported correctly by running certutil Example B 8 Accepting the signed certificate into the local certificate keystore C gt certreq accept xivhostl_ cert pem C SSL gt certutil store my Certificate 0 Serial Number 01 Issuer E ca xivstorage org CN xivstorage O xivstorage L Tucson S Arizona C US Subject CN xivhost1 xivhostlldap storage tucson ibm com Non root Certificate Cert Hash shal e2 8a dd cc 84 47 bc 49 85 e2 31 cc e3 23 32 c0 ec d2 65 3a Key Container 227151T702e 7d7b2105f4d2ce0T6f38e 8aa08b0a e9a6 4a73 9dce c84e45aec165 Provider Microsoft RSA SChannel Cryptographic Provider Encryption test passed CertUtil store command completed successfully Importing a certificate authority certificate Until the xivstorage org CA is designated as a trusted root any certificate signed by that CA is untrusted You must import the CA s certificate using the local certificate management tool into the Trusted Certification Authorities folder in the local keystore To start the local certificate management tool click Start Administrative tools gt Certificates Local Computer and complete the following steps 1 After the certificate tool opens select the Console Root Certificates Local Computer Trusted Certification Authorities folder 2 Start the certific
286. e Chapter 5 Security on page 173 Tip The Demo Mode option which is seen in Figure 4 8 on page 110 is accessed by selecting the Demo Mode check box and clicking Login No credentials are required This demo mode is useful for learning how the XIV Storage Management software works without needing an actual XIV system Note If the GUI is configured to connect to an IBM Hyper Scale Manager the login dialog window shows an additional Mode drop down field The following drop down options are available gt Direct for direct mode connection gt Manager for connecting via an IBM Hyper Scale Manager gt Demo for running the GUI in demonstration mode For more information about using Manager mode refer to the IBM Redpaper BM Hyper Scale for the XIV Storage System REDP 5053 Connecting to an XIV Storage System To connect to an XIV Storage System initially add the system to make it visible in the XIV Storage Management GUI by specifying its IP addresses To add the XIV Storage System complete the following steps 1 Ensure that the management workstation is set up to access the LAN subnet where the XIV Storage System is located Tip It is a good idea to verify the connection by pinging the IP addresses of the XIV Storage System When starting the XIV Storage Management GUI on the management workstation for the first time the Add System Management window automatically opens 2 Enter the IP address or set of IP addresse
287. e LDAP administrator must create a suffix A suffix also known as a naming context is a DN that identifies the top entry in the directory hierarchy A Sun Java Directory LDAP server can have multiple suffixes each identifying a locally held directory hierarchy for example o ibm or in our specific example dc xivauth To create a suffix log on to the Java Console using your own user ID and password and select the Directory Service Control Center DSCC link in the Services section Authenticate to the Directory Service Manager application In the Common Tasks tab click Directory Entry Management Create New Suffix or Replication Topology Then complete the following steps 1 Enter Suffix Name Specify the new suffix DN In our example we use dc xivauth Click Next 2 Choose Replication Options Accept the default Do Not Replicate Suffix LDAP replication is beyond the scope for this book 3 Choose Servers Click xivhost2 storage tucson ibm com 389 in the Available Servers list and click Add The server name is displayed in the Chosen Servers list Click Next Choose Settings Accept the default of Use Default Settings Choose Database Location Options Accept the default database location Click Next Choose Data Options Select Create Top Entry for the Suffix Click Next N O A Review the settings for the suffix about to be created and click Finish if they are correct After the new suffix creation is confirme
288. e Management software in Windows 7 or Windows Server 2008 are as follows Processor Dual core processor or equivalent Memory 512 MB of RAM 1 GB of RAM and above recommended Disk capacity 150 MB Screen resolution 1024 x 768 1024 x 768 1920 x 1200 recommended At the time of writing this book we used IBM XIV Storage Management GUI Version 4 3 Later XIV Storage Management GUI releases might differ slightly in appearance Complete the following steps to install the XIV Storage Management software 1 Locate the XIV Storage Manager installation file Double click the installation file and in the dialog window that is displayed choose the language for the installation and click OK You then see the initial installation window for the XIV Storage Management GUI installation as shown in Figure 4 3 Click Next to proceed E EM dv Storage Management GUI o E Introduction Introduction InstalAnywhere will guide you through the installation of IBM XY License Agreement Storage Management GUI Configure Installation tis strongly recommended that you quit all programs before Pre Installation Summary continuing with this installation Installing Click the Next button to proceed to the next screen Ifyou want ta change something on a previous screen click the Previous button You may cancel this installation at any time by clicking the Cancel button XIV InstalAnywhere Cancel Previou
289. e System Simple Network Management Protocol SNMP is an industry standard set of functions for monitoring and managing TCP IP based networks and systems SNMP includes a protocol a database specification and a set of data objects A set of data objects forms a Management Information Base MIB The SNMP protocol defines two terms agent and manager instead of the client and server terms that are used in many other TCP IP protocols An SNMP agent is implemented in the XIV Storage System which sends SNMP traps to an SNMP manager such as IBM Systems Director to indicate that an event has occurred By default the trap is sent to UDP port 162 The SNMP manager can also request certain information from the XIV Storage System using SNMP get or walk commands These commands are sent to the XIV Storage System on UDP port 161 336 IBM XIV Storage System Architecture and Implementation Management Information Base The information that you can receive from the XIV Storage System by sending an SNMP get request or the contents of an SNMP trap sent from the XIV Storage System are defined in an MIB The structure of a MIB is defined as an Internet standard in RFC 1155 The MIB forms a tree structure that consists of object identifiers OIDs Most hardware and software vendors provide you with extended MIB objects to support their own requirements The SNMP standards allow this extension by using the private subtree which is called an enterprise spec
290. e XIV System The completed connection is shown in Figure 5 20 on page 186 Chapter 5 Security 185 IPsec IPsec Connections Enable IPsec __ Interface Remote IP lt Figure 5 20 Completed IPSec connection configuration 4 When an IPSec connection is established from the remote IP address connection details can be viewed by right clicking the connection entry and choosing Show tunnels as shown in Figure 5 20 5 5 Native user authentication To prevent unauthorized access to the configuration of the storage system and ultimately to the information stored on its volumes the XIV Storage System uses password based user authentication Password based authentication is a form of challenge response authentication protocol where the authenticity of a user is established by presenting that user with a question challenge and comparing the answer response with information stored in a credential repository Note If you plan to use the Hyper Scale Manager see the IBM Redpaper BM Hyper Scale for the XIV Storage System REDP 5053 and 5 5 3 Security considerations when using Hyper Scale Manager on page 197 5 5 1 XIV Storage System local credential repository By default the XIV Storage System is configured to use native XIV managed user authentication Native user authentication uses the credential repository stored locally on the XIV Storage System The XIV local credential repository maintains th
291. e and Implementation User group membership for LDAP users A user group is a group of application administrators who share a set of snapshot management permissions The permissions are enforced by associating the user groups with hosts or clusters User groups are defined locally on the XIV Storage System User group membership for an LDAP user is established during the login process by matching the designated LDAP attribute value with the 1dap_role parameter assigned to a user group A user group is associated with host volumes through access definition An LDAP user which is a member of the user group is permitted to manage snapshots of volumes mapped to the host associated with the user group User groups have the following characteristics in LDAP authentication mode gt Only users assigned to the applicationadmin role can be members of a user group An LDAP user can only be a member of a Single user group A maximum of eight user groups can be created In LDAP authentication mode there is no limit on the number of members in a user group Y Y Yy 7y lf a user group is defined with access_al1 yes users assigned to the applicationadmin role who are members of that group can manage all snapshots on the system The ldap_role user group parameter can be assigned only a single value The ldap_role parameter must be unique across all defined user groups Only users assigned to the storageadmin role can create modify and delete user
292. e commands shown in this section assume that you started an XCLI Session on the selected system as described in XCLI Session features on page 133 Replace the example name values to perform the commands Example 4 9 shows the output of the command Example 4 9 All the volume related commands Category volume volume volume volume volume volume volume volume volume volume volume volume volume volume volume Name reservation clear reservation key list reservation list vol_by_id vol_copy vol_create vol delete vol disable vaai vol_enable_vaai vol_ format vol_ list vol_lock vol_rename vol_resize vol_unlock Description Clears reservations of a volume Lists reservation keys Lists volume reservations Prints the volume name according to its specified SCSI serial number Copies a source volume onto a target volume Creates a new volume Deletes a volume Disables VAAI support for a specified volume Enables VAAI support for a specified volume Formats a volume Lists all volumes or a specific one Locks a volume so that it is read only Renames a volume Resizes a volume Unlocks a volume so that it is no longer read only and can be written to To list the existing volumes in a system run the following command vol_list pool ITSO Pool For a list of existing volumes in a storage pool run the following command vol_list pool ITSO Pool The result of this command is similar t
293. e email address and phone number for the user Click Add to create the user and return to the Users window Add User System XIV 7826153 Name New Password 6 12 ij Retype New Password Category Storage Administrator x User Group None i Email Address Phone Number Figure 5 26 XIV Storage Management GUI Add User attributes 8 If you need to test the user that you defined click the current user name shown in the upper right of the IBM XIV Storage Management window Figure 5 27 and log in with the new user s credentials Storage Administrator a Figure 5 27 XIV Storage Management GUI quick user change Defining user groups with the XIV Storage Management GUI The IBM XIV Storage System can simplify various user management tasks using the capability to create user groups Groups User groups apply only to users that are assigned to the applicationadmin role A user group can also be associated with one or multiple hosts or clusters The following steps illustrate how to create user groups add users with application administrator role to the group and how to define host associations for the group 1 Ensure that you are logged in as admin or another user with storage administrator rights and in the Users window In our scenario we create a user group called Application0Ol Group Chapter 5 Security 193 2 To add a user group either click the Add User Group icon shown in Figure
294. e following information gt Username User password User role User group Optional account attributes YY vV Yy User name A user name is a string of 1 63 characters that can contain only a z A Z 0 9 _ and space symbols User names are case sensitive The XIV Storage System is configured with a set of predefined user accounts Predefined user names and corresponding default passwords exist to provide initial access to the XIV Storage System at the time of installation for system maintenance and for integration with applications such as the IBM Tivoli Storage Productivity Center 186 IBM XIV Storage System Architecture and Implementation The following user accounts are predefined on the XIV Storage System gt technician This account is used by the IBM service support representative SSR to install the XIV Storage System gt admin This account provides the highest level of client access to the system It can be used for creating new users and changing passwords for existing users in native authentication mode Important Use of the admin account should be limited to the initial configuration when no other user accounts are available Access to the admin account needs to be restricted and securely protected gt xiv_development and xiv_maintenance user These IDs are special case predefined internal IDs that can only be accessed by qualified IBM development personnel and SSRs Predefined user accounts cann
295. e nearest valid size which is an integer multiple of 17 GB 154 IBM XIV Storage System Architecture and Implementation Attention The size of the volume can be decreased with the XIV Storage Management GUI However to avoid possible data loss contact your IBM XIV Storage System support personnel if you need to decrease a volume size Mapped volume size cannot be decreased Not all host operating systems support dynamic volume resizing Consult with the host vendor documentation about whether your host OS supports resizing volumes dynamically and what restrictions and warnings there are The volume address space is extended at the end of the existing volume to reflect the increased size and the additional capacity is logically formatted that is zeros are returned for all read commands When resizing a regular volume not a writable snapshot all storage space that is required to support the additional volume capacity is reserved static allocation This configuration guarantees the functionality and integrity of the volume regardless of the resource levels of the storage pool containing that volume Resizing a master volume does not change the size of its associated snapshots These snapshots can still be used to restore their individual master volumes at their initial sizes Resize Volume myvol_15 New Size 567 GB p a r pee Figure 4 59 Resize an existing volume To resize vol
296. e need for idle spare drives in the event of a drive failure As a result all drives in the system are fully utilized reducing the amount of idle components The system s use of very high density drives maximizes physical space per floor tile offering maximum capacities of 325 usable TB in 4 TB disk drive configurations High density storage can significantly reduce power space and cooling costs and offers much lower cost per terabyte relative to comparable systems These features and more reduce the overall TCO of the XIV Storage System 1 4 XIV Gen3 Storage System models and components 4 The XIV Gen3 Storage System family consists of two machine types and two models gt Machine type model 2812 114 2812 214 gt Machine type model 2810 114 2810 214 The 2812 supports a 3 year warranty to complement the 1 year warranty offered by the existing and functionally equivalent 2810 All of the machine types are available in the following modules configurations gt Six modules including three Interface Modules gt Nine to fifteen modules including six Interface Modules The 114 model includes the following components which are visible in Figure 1 1 on page 5 gt Three to six Interface Modules each with 12 SAS disk drives 1 TB 2 TB 3 TB or 4 TB but no intermixing gt Three to nine Data Modules each with 12 SAS disk drives 1 TB 2 TB 3 TB or 4 TB but no intermixing gt Flash caching support Eac
297. e patie et are aa esaad Ena 40 25 1 Flash cachhng OVEIVIOW srie 5e0 brothers ehh is oe E hea owe ee a 40 2 5 2 Flash caching algorithm and concepts 000 cee eee ee eee 41 2 0 ENChyDIOMIOr Gala alesh serria Maw wae ei Ra ge eG Or ewe eee Rees 42 2 7 Reliability Availability and Serviceability RAS 0 0 00 eee eee 43 2 7 7 1 Resilient architecture 22 28 Spee a ewe eon eae o Save eed a es 44 2 7 2 Preserving data redundancy Rebuilding and redistributing 48 2 7 3 Exclusive additional functions for reliability and availability 54 Chapter 3 IBM XIV architecture components and planning 57 3 1 IBM XIV Storage System Gen3 2 0 eee 58 3 1 1 Fully populated configurations 0 0c ee eee 60 3 1 2 Partially populated configurations 0 0 ee ee 60 Sila Capacity ON Demand aciaci tennis iach wars ade acai Ana doa ana boa Se geabe 61 3 1 4 XIV Storage System Model 114 and Model 214 hardware components 65 SOF RACK 4c tanh iss oes sie eh eens Baa E Re eo ees he Send eee eee 65 3 16 IPOWCE componens tice ee eee ee Se i eR OS ewes 69 3 1 7 Data Modules and Interface Modules 0 0 0 cee eee eee 73 3 1 8 Interface ModuleS 5 2acule dhe twee Cee et eee ee eee eee BS 79 3 1 9 InfiniBand module interconnect 0 00 ee ee eee 84 3 110 Pateh panela ue ate see i a Gated a bee Maree SS Sa he ee a EA 85 Solel d Hardware SUPPO cfs Saeki ce
298. e predefined users that you eventually created for native authentication are deactivated not deleted when you activate the LDAP mode in the XIV Storage System Defined users no longer appear in the XIV Storage System user settings However they are not deleted and are shown and activated again if you eventually disable the LDAP authentication 212 IBM XIV Storage System Architecture and Implementation There are three ways to configure the LDAP on the XIV Storage System gt The XIV Storage Management GUI LDAP wizard gt The regular XIV Storage Management GUI windows gt The XCLI You can see examples for all methods in the following sections The first step for the XIV Storage System administrator to do is verify domain name server DNS name resolution as shown in Example 5 7 Example 5 7 DNS name resolution verification gt gt dns _ test name itso storage ibm com Name IP Primary DNS IP Secondary DNS itso storage ibm com 9 155 113 143 If the dns_test command returns an unexpected result do not proceed further with the configuration steps until the DNS name resolution issue is resolved Important As a best practice the LDAP server and XIV Storage System must have their clocks synchronized to the same time source be registered and be configured to use the same DNS servers 5 7 1 Using the XIV Storage Management GUI LDAP wizard to configure LDAP To configure LDAP by using the XIV Storage Management GUI LDAP wizard co
299. e secondary cooling loop The primary cooling loop supplies the building chilled water to secondary cooling loops air conditioning units and so on The hoses for the secondary cooling loop are not included with this option The XIV Storage System Gens rack that is installed with this option can be on a raised floor or a non raised floor The required planning for the rear door heat exchanger is extensive Details can be found in the BM XIV Storage System Planning Guide GA32 0770 Weight and height reduction The XIV Storage System Gens weight and height reduction feature removes the top four modules from the rack and ships them separately This option leaves the rack weighing approximately 1018 kg 2240 Ibs This option reduces the weight loading on floors and elevators that are used when moving the XIV Storage System rack from the truck to the final position in the installation site An IBM service support representative SSR installs the components that were shipped separately during system installation Also if this feature is ordered the IBM SSR can also remove the rack top cover to reduce the rack total height to help with moving the rack through low clearance obstacles Power consumption Table 3 3 on page 68 details the power consumption of the XIV Gen3 module configurations The measurements were taken in an environment with a room temperature of 25 C 77 F Chapter 3 IBM XIV architecture components and planning 67 Ta
300. e this I O The overall net effect is a good balance between the Interface Modules which is good But in this example the Interface Modules are only being used one at a time For optimum performance it is best to use all the XIV Storage System Interface Modules all the time This task can be accomplished by having six host servers with one XIV Storage System LUN or by having one host server with six XIV Storage System LUNs Because most computing environments use multiple application servers having one LUN per server is fine But when the XIV Storage System is dedicated to one host system consider matching the number of LUNs to the number of multipathing paths This whole discussion of the number of hosts and LUNs is closely linked to queue depth as described in Host bus adapter and disk queue depth on page 259 256 IBM XIV Storage System Architecture and Implementation Compared to other storage systems the XIV Storage System configuration typically ends up with a lower overall LUN count because the XIV Storage System architecture removes the limitations of traditional RAID arrays Older storage architectures often require small volumes such as meta volumes to use more drive spindles Older architectures also require many LUNs to employ striping techniques to engage enough disk spindles to handle high I O requirements XIV Storage System is optimized to use all drive spindles and eliminates the inconvenience of managing many volumes
301. e toolbar from in the Storage Pools view or right click in an empty area of the Storage Pools view and click Add Pool An Add Pool window opens as shown in Figure 4 45 Add Pool XIV PFE GEN3 1310133 SS Regular Pool eS Thin Pool AT m System Allocated 1 System Pools 9 l Free 88 Pool Size 4319 GB Snapshots Size 447 GB Pool Name s Figure 4 45 Add Pool 2 You must choose Regular Pool or Thin Pool according to your needs Based on the pool type you choose the available fields differ For a Thin Pool enter values for the following fields Pool Hard Size Specify the upper limit of hard capacity Pool Soft Size Specify the upper limit of soft capacity Lock Behavior Specify the behavior in case of depleted capacity This value specifies whether the storage pool is locked for write or whether it is disabled for both read and write when running out of storage space The default value is Read only For a regular pool enter the Pool Size field the required size of the storage pool 3 In the Snapshots Size field enter the required size of the reserved snapshot area 4 Inthe Pool Name field enter a name it must be unique across the storage system for the storage pool 5 Click Add to add this storage pool 140 IBM XIV Storage System Architecture and Implementation Resizing storage pools This action can be used to both increase or decrease a storage pool size Capacity calculatio
302. e total available hard space that is left for pool creation Configured Capacity Limit GB The combined hard size of all defined pools in TiB which is GiB divided by 1024 Remaining Configured Capacity GB The remaining hard space space not used by volumes or snapshots in all defined pools in TiB which is GiB divided by 1024 Tip In Figure 7 91 on page 363 you can see the Last Probe Time showing when Tivoli Storage Productivity Center last communicated with the XIV Storage System Suppose that the information showing in Tivoli Storage Productivity Center differs from the information shown in the XIV Storage Management GUI or XCLI even after converting from binary GiB or TiB to decimal GB or TB If this situation occurs you might need to run a fresh probe in Tivoli Storage Productivity Center to update the information being shown in Tivoli Storage Productivity Center Determining the available and total hard space using Tivoli Storage Productivity Center A common task is to analyze how much space is available for configuration Focusing on hard space there are three useful measures shown in Figure 7 91 gt Unformatted Disk Space shows how much hard space is available to create new pools gt If you are planning to convert your pools to thin provisioning pools you can use Remaining Configured Capacity to determine how much hard space remains in the existing pools Chapter 7 Monitoring 363 gt To determine total ha
303. e tucson ibm com domain controller The subject field is set to CN xivhost1 xivhostlldap storage tucson ibm com which is the FQDN of the domain controller Use the certreq command to generate the certificate request file Example B 7 Text instruction file for certificate request generation Version Signature Windows NT NewRequest Subject CN xivhost1l xivhost1lldap storage tucson ibm com KeySpec 1 KeyLength 1024 Can be 1024 2048 4096 8192 or 16384 Larger key sizes are more secure but have a greater impact on performance Exportable TRUE MachineKeySet TRUE SMIME False PrivateKeyArchive FALSE UserProtected FALSE UseExistingKeySet FALSE ProviderName Microsoft RSA SChannel Cryptographic Provider ProviderType 12 RequestType PKCS10 KeyUsage Oxa0 EnhancedKeyUsageExtension OID 1 3 6 1 5 5 7 3 1 3 this is for Server Authentication C SSL gt certreq new xivhostl cert_req inf xivhostl_ cert_req pem C SSL gt Appendix B Additional LDAP information 419 Signing and importing a Windows server certificate After the CER is generated xivhost1_cert_req pem you must send the request to the certificate authority to be signed For more information about signing this certificate see Signing a certificate for the xivhost1 server on page 432 After the signed certificate is returned you must import the certificate into the local machine s personal keystore Exampl
304. e viewed by the XIV Storage Management GUI or XCLI using a separate command After the alerting event is cleared it is removed from this list but it is still visible with the event_list command See Example 7 17 Example 7 17 The event_list_uncleared command gt gt event_list_uncleared No alerting events exist in the system Monitoring statistics The statistics gathering mechanism is a powerful tool The XIV Storage System continually gathers performance metrics and stores them internally Using the XCLI data can be retrieved and filtered by using many metrics Example 7 18 provides an example of gathering the statistics for 10 days with each interval covering an entire day The system is given a time stamp as the ending point for the data Because of the magnitude of the data being provided it is best to redirect the output to a file for further post processing For a more in depth view of performance see Chapter 6 Performance on page 247 Example 7 18 Statistics for 10 days gt gt statistics get count 10 interval 1 resolution_unit day end 2013 03 19 14 00 00 The usage_get command is a useful tool to provide details about the current utilization of pools and volumes The system saves the usage every hour for later retrieval This command works the same as the statistics get command You specify the time stamp to begin and end the collection and the number of entries to collect In addition you need to specify the pool name or t
305. e volume soft size that was allocated Figure A 2 Volumes and snapshot reserve space within a regular storage pool Consider Volume 1 Although Volume 1 is defined as 19 737 900 blocks 10 GB the soft capacity allocated is nevertheless composed of the minimum number of 17 GB increments needed to meet or exceed the requested size in blocks which is in this case only a single 17 GB increment of capacity The host however sees exactly 19 737 900 blocks When Volume 1 is created the system does not initially allocate any hard capacity At the moment that a host writes to Volume 1 even if it is just to initialize the volume the system allocates 17 GB of hard capacity The hard capacity allocation of 17 GB for Volume 1 is shown in Figure A 2 although clearly this allocation is never fully used if the host defined capacity remains only 10 GB Unlike Volume 1 Volume 2 has been defined in terms of gigabytes and has a soft capacity allocation of 34 GB which is the amount that is reported to any hosts that are mapped to the volume In addition the hard capacity consumed by host writes has not yet exceeded the 17 GB threshold Therefore the system has so far only allocated one increment of 17 GB hard capacity The hard capacity and the soft capacity allocated to a regular storage pool are equal by definition Therefore the remaining 17 GB of soft capacity assigned to Volume 2 is effectively preserved and remains available within
306. e wide owe mee oA eee ea Se 86 3 2 Hardware planning OvervieW 1 0 ee teens 87 3 2 1 Basic configuration planning 0 cee ee ee eee eee 87 3 2 2 IPv6 addressing and planning 0 cc eee eee 95 3 2 3 Management connectivity 0 0 0 ee eee eee 97 3 2 4 IBM XIV Storage System physical installation 0 0 00 c eee eee 98 3 2 5 System power on and power off sasaaa aaea ea ea ee eee 99 Chapter 4 IBM XIV Storage Management software 0005 103 4 1 XIV Storage Management software introduction 0 000 eee 104 4 1 1 XIV Storage Management software platforms 0 000 eee eee 104 4 1 2 XIV Storage Management software interfaces 0 000 cee eee eee 105 4 2 XIV Storage Management software installation 00000 eee 106 4 2 1 XIV Storage Management GUI and XCLI software upgrade 106 4 2 2 XIV Storage Management software installation steps for direct uSe 107 4 3 XIV Storage Management software uSage 2 cee eee 109 4 3 1 XIV Storage Management GUI used in direct mode 0005 110 4 3 2 XIV Storage System Command Line Interface 0 000s 131 4A SlOka Ge DOO miie a gaea a Gaal a Boe eed Mateo ase end DR AS dG aE escls 135 4 4 1 Function of storage poolS 0 eee 136 4 4 2 Managing storage pools with the XIV Storage Management GUI 137 4 4 3 Managing storage pools with XIV Command
307. ects with positive performance implications gt Only actual data is redistributed XIV Storage System is data aware which means that the work of redistribution is only necessary on partitions that contain actual data Partitions that do not contain data do not take up any XIV Storage System performance resources during redistribution gt All disk drives in the original configuration contribute equally to the redistribution activity This situation results in the fastest redistribution times possible and minimizes stress on the drives One of the most impressive and unique aspects of the XIV Storage System grid architecture is that as more modules are added to the system performance basically scales up linearly Again this situation is because each module contains a balanced amount of additional processors cache disk performance and bandwidth capacity 6 1 3 Caching mechanisms From a total system perspective the XIV Storage System has ample cache The XIV Storage System Gen3 Model 214 system with 4 TB drives for example was announced with 48 GB of cache per module for a fully configured system cache size of 720 GB The XIV Gens with the XIV System software Version 11 1 0 or later also offers the option of an extended SSD cache This extension provides an additional 6 TB of read cache on a 15 module system Since XIV System software Version 11 4 0 the read cache extension with flash drives can be up to 12 TB on a 15 module system
308. ed Automatic Transfer Switch The Automatic Transfer Switch ATS shown in Figure 3 8 supplies power to all three UPSs and to the Maintenance Module If there is a power problem on one line the ATS reorganizes the power and switches to the other line The operational components take over the load from the failing power source or power supply This rearrangement is performed by the ATS ina seamless manner such that the system operation continues without any application impact Important When connecting the XIV Storage System to a 30 A power source ensure that the facility circuit breakers can handle the inrush currents and differing power loads For example D Curve type breakers provide higher tolerances to allow temporary loads to flow without tripping the facility circuit Locations in Europe Middle East and Africa EMEA Australia and New Zealand should take special note of this information OUTPUT Port overview P1 P2 P3 UPS power sockets P4 maintenance module power socket EEF2 F3 UPS circuit breaker F4 maintenance module circuit breaker X807 ATS monitoring to UPS 3 network port ATS monitoring to Module 4 x807 X804 Figure 3 8 Automatic Transfer Switch The ATS is monitored by the system and generates system event messages in case of problems The status of the ATS can also be viewed with the ats_list XIV Storage System Command Line Interface XCLI command as shown in Figure 3 9 on page 71 70 IBM XI
309. ed by the system in the following manner Remaining Soft Capacity Current Storage Pool Soft Size Remaining System Soft Size Current Storage Pool Hard Size Deleting storage pools To delete a storage pool right click the storage pool and select Delete The system asks fora confirmation before deleting this storage pool The capacity of the deleted storage pool is reassigned to the system s free capacity which means that the free hard capacity increases by the size of the deleted storage pool Consideration You cannot delete a storage pool if it still contains volumes 142 IBM XIV Storage System Architecture and Implementation Moving volumes between storage pools In order for a volume to be moved to a specific storage pool there must be enough room for the volume to be there If there is not enough free capacity meaning that adequate capacity has not been allocated the storage pool must be resized or other volumes must be moved out first to make room for the new volume When moving a master volume from one storage pool to another all of its snapshots are moved along with it to the destination storage pool You cannot move a snapshot alone independent of its master volume The destination storage pool must have enough free storage capacity to accommodate the volume and its snapshots The exact amount of storage capacity allocated from the destination storage pool is released at the source storage pool A volume that
310. ed by the IBM XIV maintenance team Important As a best practice the default admin password must be changed at installation time to prevent unauthorized access to the system For instructions to change this password see Adding users with the XIV Storage Management GUI on page 190 Chapter 5 Security 187 188 The following restrictions apply when working with passwords in native authentication mode For security purposes passwords are not shown in user lists Passwords are user changeable Users can change only their own passwords Only the predefined user admin can change the passwords of other users Passwords are changeable from both the XCLI and the XIV Storage Management GUI Passwords are case sensitive User password assignment is mandatory at the time a new user account is created Creating user accounts with an empty password or removing a password from an existing user account is not permitted VvvvvvyvyY User roles There are eight predefined user roles in the XIV Storage Management GUI and the XCLI Roles are referred to as categories and are used for day to day operation of the XIV Storage System The first four categories listed below storageadmin applicationadmin securityadmin and read only are allowed to have multiple users created with these roles the other four are preassigned by the system and do not allow additional users to be created with these roles The following section describes predefined
311. ed in the Events window that is shown in Figure 7 12 Because many events are logged the number of entries is typically huge Date Local Time System EventCode 2 27 13 10 47 PM USER_HAS FAILED TO_RUN_C 2 27 13 10 47 PM USER_HAS FAILED TO_RUN_C USER_HAS FAILED TO_RUN_C USER _HAS FAILED TO_RUN_C USER_HAS FAILED TO_RUN_C USER_HAS FAILED TO_RUN_C USER_HAS FAILED TO_RUN_C USER_HAS FAILED TO_RUN_C USER_HAS FAILED TO_RUN_C USER_HAS FAILED TO_RUN_C VTS 4a DAA DEE We amp eo HAEC FAN EM Ti ONM C Figure 7 12 Events window D System ib 2 27 43 2 27 13 mee 2 27 43 11 00 PM To get a more useful and workable view there is an option to filter the events logged Without filtering the events it might be difficult to find the entries for a specific incident or information Figure 7 13 shows the possible filter options for the events System Time HE Min Severity System Time HE Event Code Uncleared Figure 7 13 Event filter Chapter 7 Monitoring 291 292 If you double click a specific event in the list you can get more detailed information about that particular event along with the best troubleshooting actions to take Figure 7 14 shows details for a critical event where an internal network link is down For this type of event contact XIV Storage System Support immediately Notification happens automatically if call home and remote support are enable
312. efficiency power supply units Example 7 13 The psu_list command gt gt psu_list Component ID Status Currently Functioning Hardware Status Power 1 PSU 1 1 OK yes OK 143 12W 1 PSU 1 2 OK yes OK 104 14W 1 PSU 15 1 OK yes OK 143 12W LePSUs1532 OK yes OK 100 20W By using the x parameter more detailed information about the actual values can be displayed See Example 7 14 Example 7 14 The psu_list x psu 1 PSU 1 1 command gt gt psu_list x psu 1 PSU 1 1 lt XCLIRETURN STATUS SUCCESS COMMAND LINE psu_list x psu 1 PSU 1 1 gt lt OQUTPUT gt lt psu id 3e403100014 gt lt component_id value 1 PSU 1 1 gt lt status value 0K gt lt currently functioning value yes gt lt requires service value gt lt service reason value gt lt hardware_ status value 0K gt lt serial value PMA0963415G01GR gt lt part_number value 0963415 05 gt lt original serial value PMA0963415G01GR gt lt original part_number value 0963415 05 gt lt fru_descriptor value DC gt lt original fru_descriptor value DC gt lt firmware_version value 1 06 gt lt voltage 12v value 12 18V gt lt voltage 5v value 5 11V gt Chapter 7 Monitoring 301 lt current value 12 07A gt lt power value 147 01W gt lt psu gt lt OUTPUT gt lt XCLIRETURN gt Events Events can also be managed with XCLI commands Various commands are available to list filter close and send notifications fo
313. efined to the GUI are shown You can access the alert information regardless of which system you are working with or which window is displayed a Hardware Alerts 3 k r Failed XIV_PFE1 6000050 Disk 5 Module 5 Phasing Gut KIW_PFE_04_ 1310133 Disk 2 Module 14 Failed KIV_PFE_03_ 7804143 Fan 6 Module 15 Figure 7 6 All Alerts window IBM XIV Storage System Architecture and Implementation In Figure 7 7 the cursor is hovering the alerts indicator for a single system allowing the quantity of alerts to be displayed for just that system A AllSystems gt Mainz_Building12 Connectivity Systems Selector q 1k ef xv_01_so00105 J xv ozion O Mainz B f xw_PFE_04_1310133 3 of 3 Syst Total alerts for this system 70 Figure 7 7 System level alert summary As shown in Figure 7 8 selecting the alert icon for the system displays that system s specific alerts in a new window A All Systems 3 gt Mainz_Building12 3 gt Alerts Q Alerts 21 When System Description Type tJ lt 1 Day XIV_02_ 1340114 IB Port 1 Module 3 status is Failed Hardware Major tJ lt i1Day XIV_02_ 1340114 IB Port 2 Module amp status is Failed Hardware Major tJ lt 1 Day AIO 13470714 Disk 2 Module 6 status is Failed Hardware Major tJ lt i1Day XIV_02_ 1310114 Disk amp Module 6 status is Failed Hardware Major tJ lt i Day XIV_02_ 1340114 Disk 6 Module amp status is Failed
314. efore Jun 29 21 35 33 2009 GMT Not After Jun 29 21 35 33 2010 GMT Subject commonName xivhost1 xivhost1ldap storage tucson ibm com X509v3 extensions X509v3 Basic Constraints CA FALSE Netscape Comment OpenSSL Generated Certificate X509v3 Subject Key Identifier C8 EB 8D 84 AB 86 BB AF 5B 74 4D 35 34 0E C5 84 30 A1 61 84 X509v3 Authority Key Identifier keyid A8 0B D1 B5 D6 BE 9E 61 62 E3 60 FF 3E F2 BC 4D 79 FC E3 5A IBM XIV Storage System Architecture and Implementation DirName C US ST Arizona L Tucson 0 xivstorage CN xivstorage emai 1 Address ca xivst orage org serial 00 X509v3 Extended Key Usage TLS Web Server Authentication X509v3 Key Usage Digital Signature Key Encipherment Certificate is to be certified until Jun 29 21 35 33 2010 GMT 365 days Sign the certificate y n y 1 out of 1 certificate requests certified commit y nly Write out database with 1 new entries Data Base Updated Appendix B Additional LDAP information 433 434 IBM XIV Storage System Architecture and Implementation Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this book IBM Redbooks publications For information about ordering this publication see How to get IBM Redbooks publications on page 436 The following documents might be available in softcopy only YYYY YYY V Y IBM XIV Storage System Copy Services
315. elect This action moves the highlighted item to the lower half of the window To generate the graph you must click the green check mark on the lower right side of the window Your new graph is generated with the name of the filter at the top of the graph See Figure 6 15 for an example of this filter All Interfaces Host Blade5 L 21 05 mie Read Write Blade41 521 04 P Blade5 L521 06 Blade7 HS22V2 hana E E a Shep 10 25 70 30 September 19 2013 of 70 45 70 40 10 45 70 50 i Mem Hit 18 64 512 KB POPs a Summ Om Osse oee ons i JSDH 68 B j gt B j Latency _ Targets Saw Tuan ro Al BM e tom Figure 6 15 Example of a host filte On the left side of the chart in the blue bar there are various tools to assist you in managing the data 268 IBM XIV Storage System Architecture and Implementation Figure 6 16 shows the chart toolbar in more detail Figure 6 16 Chart toolbar The top two tools magnifying glasses zoom in and out for the chart and the second set of two tools adjusts the X axis and the Y axis for the chart Finally the bottom two tools allow you to export the data to a comma separated file or print the chart to a printer On the right end of the filter pane is a time duration selector These selections are helpful to quickly navigate to different times In Figure 6 17 if Hour is selected the time scale is reset to the last hou
316. elect MIB to Compile 3 In the Select MIB to Compile window shown in Figure 7 60 specify the directory and file name of the MIB file that you want to compile and click OK A status window indicates the progress A Select MIB to Compile File Name Directories AlY2 MIB rmik a xI MIE mib XI 2 MIB mik E win_nt Is CI AGFS Cancel C d 2953237 dh46b8107 295599981 O9dsd C Documents and Settings 9 inetpub 9 Program Files PA RECYCLER List Files of Type Drives Source C Local Figure 7 60 Compile MIB When you compile a new MIB file it is also automatically loaded in the Loaded MIBs file directory and is ready for use Chapter 7 Monitoring 343 To load an already compiled MIB file complete the following steps 1 In the MIB Management window click File Select MIB to load 2 Select the MIB that you load in the Available MIBs window click Add Apply and OK This action loads the selected MIB file and the IBM Director is ready to be configured for monitoring the XIV Storage System 7 5 2 Discovering the XIV Storage System 344 After loading the MIB file in to IBM Director you must discover the IBM XIV systems in your environment Therefore configure the IBM Director for auto discovery by completing the following steps 1 From the IBM Director Console window click Options gt Discovery Preferences as shown in Figure 7 61 IBM Director Console MEE Console
317. elected systems with visual indicators for replication relationships between systems and group membership For each system the system name serial number system software version and hardware version Gen3 only are displayed Click the balloon above a system to change the balloon value The following values are available System IOPS System Utilization System Status System Number of Hosts System Number of Volumes System Hardware Type YYYY YV Y 124 IBM XIV Storage System Architecture and Implementation A AllSystems 9 gt Redbook2013 3 C Connectivity d XIV 131 7 Alba G3 IOPS 189 278 XIV 13 tooine G3 IOPS 73 607 Figure 4 29 All Systems Connectivity view Note When one or more systems are selected in the Connectivity view the cleared systems appear grayed out The Tiles view as seen in Figure 4 30 displays the selected systems in a grid format For each system the following details are displayed Group name if applicable System name and serial number System software version Current system IOPS Capacity usage System status including indicators for hardware problems or alerts A All Systems 9 gt Redbook2013 3 Ties D YYYY YV Y XIV 1310062 Dantooine 11 4 0 i XIV 1310077 Alba IOPS 20423 IOPS 174497 XIV_02_1310114 IOPS 20 20 Figure 4 30 All Systems Tiles view Chapter 4 IBM XIV Storage Management software 125 126 Note Only selected systems are visible
318. em Linux 2 6 Linux 2 6 Linux 2 6 Linux 2 6 Linux 2 6 Linux 2 6 Host x345 tic 31 User ID X345 TIC 31 Administrator 7 objects Figure 7 63 IBM Director Console IBM Director and IBM Director Console are ready to receive SNMP traps from the discovered IBM XIV systems With IBM Director you can show general information about your IBM XIV systems monitor the event log and browse for more information Chapter 7 Monitoring 345 7 5 3 General System Attributes window Double click the entry corresponding to your XIV Storage System in the IBM Director Console window to show the General System Attributes as shown in Figure 7 64 This window gives you a general overview of the system status amp IBM Director Console Miel Console Tasks Associations View Options Window Help go iz tii de Gale m H eP te JI All Managed Objects SNMP System Object ID Y Name a TCPIP Addresses TOPIIP Hosts Operating System Oy enterprises o072 3 2 10 1 3 6 1 4 1 0072 3 2 10 meil ESP 1 VI0 0 1300203 9 155 599 242 dyn 9 155 53 252 mainz deibm Linux 2 6 GSA ESP 1 VI0 0 1300203 9 155 539 2414 dyn 9 155 53 251 mainz deibm Linux 2 6 Ge XV ESP 1 V10 0 1300203 9 155 539 240 dyn 9 165 53 2450 mainz deibm Linux 2 6 mE AV V1 OO MNOO0S0 4 155 56 101 xi lab 01a mainz de ibm com Linux 2 6 ATY V4 0 0 MNOO050 9 155 586 7100 xiv lab 01 mainz de ibm com Linux 2 6 6 y VIO
319. em during hardware failures and the equilibrium resulting from the automatic redistribution of data across all newly installed hardware are fundamental characteristics of the XIV Storage System architecture These capabilities minimize exposure to cascading failures and the associated loss of access to data Consistent performance The XIV Storage System can adapt to the loss of an individual drive or module efficiently and with relatively minor impact compared to monolithic architectures 44 IBM XIV Storage System Architecture and Implementation Although traditional monolithic systems employ an N 1 hardware redundancy scheme the XIV Storage System uses a grid topology This topology can sustain a component failure and maximize consistency and transparency from the perspective of attached hosts The potential impact of a component failure is vastly reduced because each module in the system is responsible for a relatively small percentage of the system s operation A controller failure in a typical N 1 system results in a dramatic up to 50 reduction of available cache processing power and internal bandwidth Conversely the loss of a module in the XIV Storage System translates to only 1 15th of the system resources and does not compromise performance nearly as much as the same failure with a typical architecture For more information about this topic see Chapter 6 Performance on page 247 Additionally the XIV Storage System in
320. em Architecture and Implementation 5 9 2 Maintaining the SSL certificate A new SSL certificate must be installed before the existing one expires If you let your SSL certificate expire XIV Storage System LDAP authentication is no longer possible until you either disable SSL or install the new certificate on both the LDAP server and the XIV Storage Server Before the SSL certificate expires the XIV Storage System issues three notification events The first LDAP SSL Certificate About to Expire event is shown in Figure 5 82 Event Properties Severity Warning Date 2011 10 04 16 51 38 Index 61639 Event Code TO T Shooting Description SSL Certificate of LDAP server itso storage ibm com is about to expire on 2011 11 01 14 55 16 first notification Figure 5 82 First notification of SSL certificate of LDAP server expiration Chapter 5 Security 245 246 IBM XIV Storage System Architecture and Implementation Performance This chapter describes how the IBM XIV Storage System software and hardware work together to provide high performance characteristics These characteristics inherent to the XIV Storage System design deliver optimized and consistent performance Admittedly there is little that clients need to do within an XIV Storage System that can contribute to performance gains beyond what the XIV Storage System automatically provides and that includes the optional flash caching solid state drive SSD cac
321. em Architecture and Implementation After adding one or more LDAP servers you can now define the login attributes in the XIV Storage System In Example 5 9 you can see an example for a possible Microsoft Active Directory implementation Example 5 9 XCLI LDAP configuration XIV 02 1310114 gt gt ldap_ config set server_type Microsoft Active Directory Xiv_group_attrib memberOf storage admin role CN XIVAdmins CN Users DC itso DC storage DC i bm DC com read only_role CN XIVReadonly CN Users DC itso DC storage DC ibm DC com xiv_user CN XIV CN Users DC itso DC storage DC ibm DC com user_id_attrib sAMAccountName user_name_attrib displayName Command executed successfully For a detailed description of the LDAP role mapping see 5 6 4 LDAP role mapping on page 208 The XIV Storage System configuration parameters storage _admin role read_only_role and xiv_group attrib must have values assigned for LDAP role mapping to work After the configuration is submitted successfully you can check your values by running Idap_config_get Now that all the configuration and verification steps are completed the LDAP mode can be activated by running 1dap_mode_set as shown in Example 5 10 Example 5 10 Enabling the XIV LDAP mode XIV 02 1310114 gt gt ldap_ mode set mode Active Warning ARE YOU SURE YOU WANT TO ENABLE LDAP AUTHENTICATIONy Command executed successfully LDAP mode When you activate the LDAP mode it deactivates all de
322. em Architecture and Implementation For details about the host connections see XIV Storage System Host Attachment and Interoperability SG24 7904 Fibre Channel connections When shipped the XIV Storage System is by default equipped with 24 Fibre Channel ports assuming a fully populated 15 module rack The XIV Storage System supports 50 micron fiber cabling If you have other requirements or special considerations contact your IBM SSR The 24 Fibre Channel FC ports are available from the six Interface Modules four in each module and they are internally connected to the patch panel Of the 24 ports 12 are provided for connectivity to the switch network for host access and the remaining 12 are for use in remote mirroring or data migration scenarios however they can be reconfigured for host connectivity Adhere to this guidance on Fibre Channel connectivity The external client provided cables are plugged into the patch panel For planning purposes Figure 3 26 highlights the maximum values for various Fibre Channel parameters for your consideration Maximum values FC parameters Modell 114 Model 214 1 GbE and Model 214 10 GbE Maximum number of Interface Modules with iSCSI ports Maximum number of 8 GB FC ports Maximum queue depth per FC host port 1400 Maximum queue depth per mapped volume per host port target port volume Maximum FC ports for mirror migration connections default configuration Maximum number of concur
323. em for that pool Therefore the storage pool hard size that is defined by the storage administrator limits the physical capacity that is available collectively to volumes and snapshots within a thinly provisioned storage pool The aggregate space that is assignable to host operating systems is specified by the storage pool soft size Regular storage pools segregate the hard space reserved for volumes from the hard space consumed by snapshots by limiting the soft space allocated to volumes However thinly provisioned storage pools allow the totality of the hard space to be consumed by volumes with no guarantee of preserving any hard space for snapshots Logical volumes take precedence over snapshots and can be allowed to overwrite snapshots if necessary as hard space is consumed The hard space that is allocated to the storage pool that is unused the incremental difference between the aggregate logical and actual volume sizes can however be used by snapshots in the same storage pool Careful management is critical to prevent hard space for both logical volumes and snapshots from being exhausted Ideally hard capacity utilization must be maintained under a certain threshold by increasing the pool hard size as needed in advance Chapter 2 IBM XIV Storage System logical architecture and concepts 37 38 Storage pools and snapshots gt As described in Storage pool relationships and rules on page 32 storage pools control when and w
324. em solving techniques for XIV Storage System performance 6 4 1 Problem solving steps 278 The problem solving steps consist of the problem definition collecting good data and performance analysis Problem definition A good problem definition includes the following types of information gt Which application is having performance problems What is a description of the problem from the application perspective What operating system performance characteristics indicate that the problem is XIV Storage System performance IBM XIV Storage System Architecture and Implementation gt What LUNs are dedicated to this application gt How is the application server zoned gt During what time period is the problem experienced gt What is the XIV Storage System configuration There can always be more than one performance problem It is best to define these performance issues separately but to note if they are related Collecting good data The next thing to do is to collect good data The data collected typically begins slightly before the problem begins and ends slightly after the performance problem duration In this way ideally it is possible to see the abnormalities in the performance data elevated response times for example begin and end This task is fairly easy to do with the XIV Storage Management GUI performance statistics Typically a performance issue is being experienced from a particular application server
325. ementation IBM XIV Storage Management software This chapter describes the tasks performed by a storage administrator to configure the IBM XIV Storage System using the XIV Storage Management software As of this publication the current version of the XIV Storage Management software is Version 4 3 The chapter covers the following topics XIV Storage Management software introduction XIV Storage Management software installation XIV Storage Management software usage Storage pools Volumes Host definition and mapping SSD Caching Scripts YY YYYY Y Y Important Illustrations in this chapter mostly apply to an IBM XIV Storage System Gen3 fully configured with 2 TB drives The IBM Hyper Scale Manager which allows an administrator to monitor and configure many systems simultaneously is discussed in the IBM Redpaper IBM Hyper Scale for the XIV Storage System REDP 5053 Copyright IBM Corp 2013 All rights reserved 103 4 1 XIV Storage Management software introduction The XIV Storage System software runs internally on all system modules both Data and Interface Modules and provides all the functional capabilities The functions and nature of this software are equivalent to what is typically referred to as microcode or firmware on other storage systems The XIV Storage Management software also referred to as XIV Management Tools is used to communicate with the XIV Storage System software which in turn interacts with the XIV
326. en the disk and the cache This design aspect allows large amounts of data to be quickly transferred between the disks and the cache by the bus Having a large bus bandwidth allows the XIV Storage System to use small cache pages This large bus bandwidth between the disk and the cache also allows the system to perform many small requests in parallel again improving the performance A least recently used LRU algorithm is the basis for the cache management algorithm This feature allows the system to generate a high hit ratio for frequently used data The efficiency of the cache usage for small transfers is high when the host is accessing the same data set The cache algorithm starts with a single 4 KB page and gradually increases the number of pages prefetched until an entire partition 1 MB is read into cache If the access results in a cache hit the algorithm doubles the amount of data prefetched into the system The prefetching algorithm continues to double the prefetch size until a cache miss occurs or the prefetch size maximum of 1 MB is obtained Because the modules are managed independently if a prefetch crosses a module boundary the logically adjacent module for that volume is notified to begin pre staging the data into its local cache 6 1 4 Data redistribution effects on host systems 252 This section describes the effects that the application server experiences during XIV Storage System data rebuild and redistribution For ou
327. eparated on the graph By holding down Ctr1 on the keyboard and selecting the read option and then the write option you can see both items on the graph Chapter 6 Performance 265 As shown in Figure 6 11 one of the lines represents the read IOPS and the other line represents the write IOPS On the GUI these lines are drawn in separate colors to differentiate the metrics The other most popular speed metric is bandwidth BW measured in MBps This selection process can be performed on the other filter items as well All Interfaces Read Write IOPS 36 000 34 000 32 000 30 000 28 000 26 000 24 000 22 000 20 000 13 000 ada yi Nh 6 000 4 000 2 000 0 3 2 50 12 45 13 00 13 15 13 30 13 45 14000 1405 1 30 1465 15 00 1515 15 30 15 45 16 00 16 15 16 30 16 Sep 2011 Read Hit C Mem Hit C 0 8 KB O 64 512 KB a a AAW TDS EP hour iaa ad ig D aS AE dki LJ baia KB 7 dle KB Figure 6 11 Multiple filter selection One of the most meaningful performance metrics is latency which is measured in milliseconds Figure 6 12 shows the read and write latency for the entire XIV system All Interfaces Latency ms 16 22 00 00 00 02 00 04 00 06 00 42 00 14 00 16 00 18 00 20 00 22 00 08 00 10 00 Cw March 11 2013 March 12 2013 Figure 6 12 Latency 266 IBM XIV Storage System Architecture and
328. equirements for the pool change later on the pool s type can be changed nondisruptively Tip Thin provisioning management is performed individually for each storage pool and running out of space in one pool does not affect other pools 4 4 2 Managing storage pools with the XIV Storage Management GUI In this section we describe how to manage storage pools using the XIV Storage Management GUI Important Illustrations in this chapter mostly apply to an XIV Storage System fully configured with 1 TB drives Managing pools with the XIV Storage Management GUI is fairly simple and intuitive The related tasks can be reached either through the menu bar or the corresponding function icon on the left called Pools as shown in Figure 4 42 um Pools Volumes by Pools j Figure 4 42 Opening the Pools menu To view overall information about the storage pools click Storage Pools from the Pools menu that is shown in Figure 4 42 This opens the Storage Pools view as shown in Figure 4 43 Name Usage napshots GB Teck Behavior 51 GB Used Volumes 3441 GB Hard amp Gene C Read Only 1015 GB Wolumes Allocated 361 GB 3441 GB Sof Snapshots Reserved 361 GB 52 GB Used Volumes of 1514 GB Hard i f 6 hannes ReadOnly 1015 GB Volumes Allocated 344 GB 3011 GB Soft Snapshots Reserved 344 GB 860 GB Used Volumes 7846 GB Hard Used 17 GB 2 2013 GB Volumes Allocated 7846 GB Soft Snapshots Reserved
329. erts at various severity levels These alerts are system based across all pools and viewable in the XIV Storage Management GUI by all users configured with the particular system System events are also produced based on specified values The default pool usage threshold values are for warning 80 minor 90 and major 95 To configure pool thresholds from the XIV Storage Management GUI Storage Pools view click the Pool Thresholds icon in the toolbar or right click an empty area in the view and choose Pool Thresholds This opens the dialog window that is shown in Figure 4 50 Pool Alert Thresholds Volumes Usage 0 Informational i 5j H snapshots Usage 3 Wanin 30 1 w Minor M 0 Critical M 5 Restore Factory Defaults r F Update Cancel Figure 4 50 Set pool alert thresholds Enable a specific class of Volumes Usage or Snapshots Usage threshold alert by checking the box next to it To adjust the value of an enabled threshold click and drag the slider bar or type in the corresponding numerical value Events The XIV Storage System has several predefined events that are triggered when system pool usage is depleting Rules can be set to receive email alerts for these events For more information about setting up email event notifications see Chapter 7 Monitoring on page 285 144 IBM XIV Storage System Architecture and Implementation 4 4 3 Managing storage pools with XIV Command Line Interface All of
330. es Sf i WF 0S ila fn ee a A N me ee gt Witche w oe JAGU Jaraa tb LE Server Resources Network arf Resources Capacity Recent Jobs Unacknowledged Alerts l i Storage Systems gt Last Day Last Day i Renortin Pool Space 103 86 TiB ee ED eee rep 0 Warning 13 Warning F 4 Successful Fi 1 Informational View all jobs View all alerts View performance jobs Figure 7 100 Tivoli Storage Productivity Center GUI storage resources Chapter 7 Monitoring 369 Selecting Storage Systems displays a list of the available storage systems Double click the name of a storage system and the Overview window is displayed See Figure 7 101 Storage Productivity Center Logout Storage Resources Storage Systems XIV Coruscant v Tip wD Overview ool Space a a Home Available 46 26 TiB Capacity Last 30 days Space by Host 6 Storage XIV Coruscant Resources IBM XIV System z General 4 R 3 Server Properties Resources Alerts 20 8 Jobs 4 6 Internal Resources erana Volumes 303 Resources Pools 3 Disks 72 PB Free capacity J Used capacity j virtual ca Modules 6 lii Ports 8 OOS Space by Pool Space by Volume ie onnections Reporting Largest Pools Largest Volumes Related Resources None gt 1 000 i GS o l 50940 stg 41 0l c02 c03 c04 Figure 7 1
331. esigned to support multiple full or differential snapshots of a volume Any of the snapshots can be made writable and then snapshots can be taken of the newly writable snapshots snapshots of snapshots Volumes can even be restored from these writable snapshots 8 IBM XIV Storage System Architecture and Implementation Synchronous and asynchronous remote mirroring to another XIV Storage System Synchronous or asynchronous remote mirroring can be performed over FC or IP iSCSI connections Synchronous remote mirroring is used when a zero recovery point objective RPO is required For practical reasons latency ensure that the distance is less than 100 km 62 miles For longer distances asynchronous replication is more appropriate The XIV software V11 4 now offers quick start synchronous mirroring with offline initialization and flexible switching between synchronous and asynchronous mirroring Support for thin provisioning Thin provisioning allows administrators to overprovision allocated storage within a storage pool This task is done by defining volume sizes that are larger than the physical capacity of the storage pool Unlike other approaches the physical capacity of the storage pool only needs to be larger than the actual consumed size of the volumes within that pool Physical capacity of the storage pool needs to be increased only when actual written data of the volumes comes close to the physical pool size Support for Microso
332. esiliency under changing hardware conditions An example of this modular design is located specifically in the Interface Modules All six Interface Modules actively manage system services and software functionality associated with managing external I O Also three of the Interface Modules deliver the system s management interface service for use with the XIV Storage System Data distribution algorithms Data is distributed across all drives in a pseudo random fashion The patented algorithms provide a uniform yet random spreading of data which is divided into 1 MB partitions across all available disks to maintain data resilience and redundancy Figure 2 4 on page 24 shows how all drives are used evenly by partition units regardless of applications or the size of assigned logical volumes The storage administrator does not need to worry about data placement impact on performance Chapter 2 IBM XIV Storage System logical architecture and concepts 23 Data is spread across all drives 1MB partition distribution Even Disk utilization Oracle Partition Partition o00a Partition Figure 2 4 Pseudo random data distribution For more details about the topic of data distribution and storage virtualization see 2 3 2 Logical system concepts on page 26 2 3 Full storage virtualization The data distribution algorithms employed by the XIV Storage System are innovative and unique in that they are deeply integrated into the sys
333. esult of a flash device failure All the primary partitions on the module with the failed flash device remain the primary partition But because of the reduced extended flash cache the specific module limits its caching duties 52 IBM XIV Storage System Architecture and Implementation Redistribution after adding modules or drives The redistribution process that happens after a rebuild is the same process that results from the following events gt The replacement of a failed disk drive or module following a rebuild which is also known as a phase in gt When one or more modules are added to upgrade the capacity of the system Important The client s storage administrators cannot perform a phase in to replace a failed disk or module These operations must be performed by IBM technicians Therefore it is not a good idea to purposely pull an XIV Storage System disk drive to test the redundancy mechanisms because storage administrators are not authorized to get a drive back into the system The XIV Storage System data distribution has the following characteristics gt The redistribution process is triggered by the phase in of a new drive or module and differs from a rebuild or phase out in the following ways The system does not need to create secondary copies of data to reinstate or preserve full data redundancy The concentration of data on each physical disk decreases gt The redistribution is dependent on the writing
334. evels to hosts that are connected to the same system The QoS feature is intended to enhance performance of critical business applications that run concurrently with noncritical applications Because the XIV Storage System disk and cache are shared among all applications and all hosts are attached to the same resources division of these resources among both critical and noncritical applications might have an unintended adverse performance on critical applications To address this issue QoS allows you to limit the rate of noncritical IOPS and bandwidth by specifying and then enforcing limits on the maximum amount of low priority OPS and bandwidth on a host group basis As a result the QoS feature in the XIV Storage System enables better performance for the critical group of host applications that run concurrently with the noncritical host group applications on the same XIV Storage System If you are using QoS up to four performance classes are configurable each with distinct IOPS and bandwidth BW limits that are enforced for the hosts in that class However each host can belong to only a single performance class at a specific time There is no limit to the number of hosts that can be within a single group Note If more than one host is added to the performance class be aware that all hosts in this performance class share the resources setup on the performance class For example if two hosts are added to a 10000 IOPS performance class the t
335. events Snapshots and consistency groups Monitor Hosts and Clusters Access system alerts Manage host and cluster events and monitor configuration system system performance connectivity and quality of service Pools Remote Administer a related Define and then regulate group of similarly all system mirroring and provisioned logical migration related volumes and their Operations Snapshots Access E Govern users and user A groups to control system e access Figure 4 17 Menu items in XIV Storage Management software Tip Depending on the current user role more systems administrative actions might be available in the menu items 118 IBM XIV Storage System Architecture and Implementation XIV Storage Management GUI features Several notable features in XIV Storage Management Version 4 3 facilitate efficient system configuration and management by using the XIV Storage Management GUI Tree Table When working with the XIV Storage Management GUI a standardized view has been introduced called the Tree Table TT view As shown in Figure 4 18 in the Pools Volumes by Pools view this feature presents the navigation of several views Pools Volumes Hosts and Clusters using a tree like table view This view can be useful when accessing the current storage related views and making changes accordingly Name Size GB AIX PFE_pool AIX PFE_LPAR_4 AIX_PFE_LPAR_ AIX _ PFE_LPAR 3 andy jub2012 andy_volt andy_
336. ey expire The password if set must be given to the IBM Support representative in order for them to establish a connection Use of a password is not required and can be left blank Using Never for the timeout values results in the connection remaining open until explicitly disconnected Connect Support Center Session Timeout Never Idle Timeout Never Connection Password a oT E Figure 7 52 Starting an XRSC connection After the connection to the XRSC has been established you can disconnect the session by clicking the Disconnect Support Center icon as shown in Figure 7 53 on page 331 IBM XIV Storage System Architecture and Implementation Support Center Status connecting Connected Support Sessions 0 Address Front XRSC 2 195 110 41 1 Disconnect Support Center Fort Type Management i Close Figure 7 53 Disconnecting a Remote Support Center session Starting an XRSC connection using XCLI The following XCLI commands are used to manage Remote Support Center connections gt support_center_list gt support_center_status gt support_center_connect gt support_center_disconnect To start an XRSC connection using GUI open a list of the available support centers that were configured during system installation by issuing the support_center_list XCLI command as shown in Example 7 30 Example 7 30 List available support centers gt gt support_center_list Name Address Port
337. f 16x2 bytes According to this rule the smallest pool size is 17 GB When creating a storage pool the system initially provides a default snapshot size of 10 However you might want to adjust this value depending on how snapshots are used your workload characteristics and your requirements for how long snapshots must be kept This value can be set at the time of creation or dynamically changed later depending on your needs Snapshot size The snapshot size default or specified is a subset of the specified pool size It does not allocate more space Sizing must consider volumes that are to be added to or exist in the specific storage pool the current allocation of storage in the total system capacity and future activity within the storage pool especially regarding snapshot propagation from creating too many snapshots Upon depletion of space in a pool the system progressively deletes snapshots in the pool to free up space for additional write requests For more information see Chapter 1 Snapshots in IBM XIV Storage System Copy Services and Migration SG24 7759 The system enables the assignment of the entire available capacity to user created storage pools The storage pool is initially empty and does not contain volumes However you cannot create a storage pool with zero capacity Chapter 4 IBM XIV Storage Management software 139 To create a storage pool complete the following steps 1 Click Add Pool in th
338. f the FULL GUI installation or it can be installed alone 1 7 Host support 14 The XIV Storage System can be attached to various host operating systems including the following ones Microsoft Windows VMware ESX IBM AIX HPUX Linux Oracle Solaris YYYY YV Y For details about each operating system and versions supported see the IBM XIV interoperability matrix or the IBM System Storage Interoperation Center SSIC at the following website http www ibm com systems support storage config ssic index jsp There are also various software agents available to help you manage environments that connect to an XIV Storage System An IBM storage driver for OpenStack is also available For more information about this topic see the IBM Redpaper publication Using the IBM XIV Storage System with OpenStack Cloud Environments REDP 4971 You can also consult the following resources gt Tivoli Storage Productivity Center Storage Resource Agent http publib boulder ibm com infocenter tivihelp v4r1 index jsp topic 2Fcom i bm tpc_V42 doc 2Ffqz0_r_whats_new release 4 2 html This tool provides support for XIV Storage System provisioning data path explorer and performance management reporting gt VMware vCenter Site Recovery Manager SRM Storage Replication Adapter http downloads vmware com d info datacenter_downloads vmware vcenter_site rec overy manager 4_ 0 Storage Replication Adapters are software modules for
339. ficate authority CA Companies have the choice of using a trusted CA from a vendor or creating their own certificate authority In this scenario the xivauth org CA is used To be operational SSL must be configured on both the client and the server Server configuration includes generating a certificate request obtaining a server certificate from a CA and installing the server and CA certificates 416 IBM XIV Storage System Architecture and Implementation Windows Server SSL configuration To configure SSL for LDAP on a Windows Server you must install the Management Console MMC snap in to manage local certificates Then you must create a certificate request CER and have the CER signed by a CA Finally you import the signed certificate into the local keystore import a CA certificate as a trusted root CA and then reboot the server for the new configuration to take effect Installation of the local certificates Management Console snap in Install the certificate snap in for MMC to allow you to manage the certificates in your local machine keystore by completing the following steps i 2 3 Start the MMC by selecting Start gt Run Enter mmc a and select OK Click the File Add Remove Snap in menu to open the Add Remove Snap in window Click Add to open the Add Standalone Snap In window Click the Certificates snap in and then click Add Select the Computer Account option to manage system wide certificates Click Ne
340. file either from a CA vendor or with your own CA server 3 Install the signed certificate on the XIV Storage System 4 Instruct the XIV GUI to trust the new signed certificate 174 IBM XIV Storage System Architecture and Implementation 5 2 1 Managing x509 certificates with the XIV Storage Management GUI This section shows how to prepare and configure the XIV Storage System to use x509 certificates Creating a CSR and importing the signed x509 certificate The following steps demonstrate how to use the XIV GUI to use your own x509 certificate 1 In the GUI navigate to the System view of the chosen XIV Storage System and click Systems System Settings Manage Certificates to open the Certificates Management panel as shown in Figure 5 1 Certificates Management Generate CSR Authenticated Services lt Figure 5 1 Certificates Management panel 2 Click the Generate CSR icon in this panel to open the Generate CSR panel as shown in Figure 5 2 Generate CSR Name itsoCentificate Subject ICN xivhost O itsolL Tucson ST AZIC Ut Bits 2 045 pe co ko Figure 5 2 Generate CSR file Enter a unique value for the name of the certificate in the Name field In our example we use the value itsoCertificate for the name In the Subject field enter a value for the subject of the certificate The subject field represents the values that uniquely identify this system and are commo
341. fined users on the XIV Storage System and only LDAP users with the appropriate group role have access to the system The LDAP authentication mode is now configured activated and ready to be tested A simple test that can validate the authentication result is to open an XCLI session using the credentials of a newly created Active Directory account xivtestuserl and run Idap_user_test This command can be successfully executed only by a user authenticated through LDAP 5 8 LDAP managed user authentication When the XIV Storage System is configured for LDAP authentication user credentials are stored in the centralized LDAP repository The LDAP repository is on an LDAP Server and is accessed by the XIV Storage System using an LDAP protocol Chapter 5 Security 223 5 8 1 LDAP repository credential objects 224 The LDAP repository maintains the following types of credential objects that are used for XIV Storage System authentication LDAP user name LDAP user password LDAP user role User groups y vy y LDAP user name The XIV Storage System limitations for acceptable user names such as number of characters and character set no longer apply when user names are stored in an LDAP repository Each LDAP product has its own set of rules and limitations that applies to user names Generally do not use long names and non alphanumeric characters even if your LDAP product of choice supports it If you eventually decide to migrate user cre
342. form this operation See Figure 6 27 fora sample of the output for the command Example 6 4 The statistics_get command using the host filter gt gt statistics get host adams end 2009 06 16 11 45 00 count 10 interval 1 resolution unit minute Time Read Hit Medium Ops Read Hit Medium Latency Read Hit Medium Throughput 2003 06 16 149 2092 4489 2003 06 16 136 2689 4219 2009 06 16 141 3016 3897 2009 06 16 293 ede S068 2003 06 16 418 S030 12574 2003 06 16 391 3101 12518 2003 06 16 445 3554 13858 2003 06 16 518 3536 15748 2003 06 16 490 S243 14852 2003 06 16 S70 S628 11531 Figure 6 27 Output from the statistics_get command using the host filter In addition to the filter just shown the statistics get command can filter iSCSI names host worldwide port names WWPNs volume names modules and many more fields As an additional example assume that you want to see the workload on the system for a specific module The module filter breaks out the performance on the specified module Example 6 5 pulls the performance statistics for module 5 during the same time period of the previous examples Figure 6 28 shows the output Example 6 5 The statistics_get command using the module filter gt gt statistics get end 2009 06 16 11 45 00 module 5 count 10 interval 1 resolution unit minute Time Read Hit Medium 0ps Read Hit Medium Latency Read Hit Medium Throughput 2003 06 16 11 354 B94 99820 2009 06 16 11 165 gel 4485 2003 06 1
343. formance has been further enhanced in XIV V11 2 through optimization of SSD data integrity checking This module architecture is explored from a different perspective Would it be possible for the XIV Storage System module to have one of the most powerful multi core processors available today Would it be possible for each module to have more cache or faster disk controllers or faster bus speeds or faster disk drives The answer to all these questions is yes But what would be the point in having the latest fastest most expensive components available if the total system can drive these components to only a fraction of their performance capabilities The XIV Storage System module is carefully designed to use the performance capacity of individual components in a balanced way as the total system approaches its peak performance capabilities As an example consider the new 6 core CPUs introduced in XIV Gen3 model 214 There was a need to upgrade the CPU with more processing capacity to support the 10 Gb IP network Small Computer System Interface iSCSI available with XIV System software V11 2 When a partial XIV Storage System configuration needs more performance capacity it is a simple matter of adding more modules to the XIV Storage System configuration When modules are added the XIV Storage System software automatically redistributes the existing data The XIV System has a maximum of 15 modules This data redistribution has many interesting asp
344. free space consumed by the volume is the smallest multiple of 17 GB that is greater than the specified size For example if we request an 18 GB volume to be created the system rounds this volume size to 34 GB For a 16 GB volume size request it is rounded to 17 GB Figure 4 55 on page 152 gives you various basic examples of volume definition and planning in a thinly provisioned pool Chapter 4 IBM XIV Storage Management software 151 Pool Soft Size 51 GB Pool Soft Size 51 GB Pool Hard Size 34 GB Pool Hard Size 34 GB Volume Volume II Volume III 17 GB 17 GB Pool hard size gt 17 GB x number of volumes in the pool Pool Soft Size 51 GB Pool Hard Size 34 GB l l Volume II 34 GB l l Figure 4 55 Planning the number of volumes in a thin provisioned pool Figure 4 55 shows the volumes with the minimum amount of capacity but the principle can be used for larger volumes as well Plan carefully the number of volumes or the hard size of the thinly provisioned pool because of the minimum hard capacity that is consumed by one volume If you create more volumes in a thinly provisioned pool than the hard capacity can cover the I O operations against the volumes fail at the first I O attempt Volumes Plan the volumes in a thin provisioned pool in accordance with this formula Pool Hard Size gt 17 GB x number of volumes in the pool The size of a
345. ft Windows Server 2012 The XIV Storage System enables clients to take advantage of recent Windows enhancements such as space reclamation that can help increase capacity usage and lower TCO Support for in band data migration of heterogeneous storage The XIV Storage System is also capable of acting as a host gaining access to volumes on an existing storage system The system is configured as a proxy to respond to requests between the current hosts and the storage while migrating all existing data in the background In addition the XIV Storage System supports thick to thin data migration which allows the system to reclaim any allocated space that is not occupied by actual data Authentication using Lightweight Directory Access Protocol LDAP LDAP can be used to provide user logon authentication allowing the XIV Storage System to integrate with Microsoft Active Directory AD Open LDAP or Oracle Sun Java Systems Directory Server Multiple directory servers can be configured to provide redundancy in case one server becomes unavailable Encryption for data at rest IBM XIV Storage System Gen3 with software Version 11 4 0 is designed to help secure data with industry standard encryption for data at rest while avoiding performance impact For details about encryption with XIV see the IBM Redpaper X V Security with Data at Rest Encryption REDP 5047 Secure communications between management software and IBM XIV systems via Secure
346. g of logical volumes to physical disks differ gt Every logical volume consists of 1 MB 1024 KB constructs of data known as partitions gt The physical capacity associated with a logical volume is always a multiple of 17 GB decimal because the volume spans all physical drives in the system because of the grid nature of the architecture Although it is possible to present a block designated logical volume to a host that is nota multiple of 17 GB the actual physical space that is allocated for the volume is always the sum of the minimum number of 17 GB increments needed to meet the block designated Capacity Capacity The initial physical capacity allocated by the system upon volume creation can be less than this amount as described in Logical and actual volume sizes on page 34 gt A maximum total of 12 000 volumes including snapshots can be concurrently created on the system Storage pools Storage pools are administrative boundaries that enable storage administrators to manage relationships between volumes and snapshots and to define separate capacity provisioning and snapshot requirements for separate applications or departments Storage pools are not tied in any way to physical resources nor are they part of the data distribution scheme We describe storage pools and their associated concepts in 2 3 4 Storage pool concepts on page 31 Snapshots A snapshot represents a point in time copy of a volume Snapsho
347. g concurrent snapshots of volumes that are spread across multiple XIV systems and belong to one application In the first few chapters of this book we describe many of the unique and powerful concepts that form the basis of the XIV Storage System logical and physical architecture We explain how the system is designed to eliminate direct dependencies between the hardware elements and the software that governs the system In subsequent chapters we explain the planning and preparation tasks that are required to deploy the system in your environment by using the intuitive yet powerful XIV Storage Manager GUI or the XIV command line interface XCLI We describe the performance characteristics of the XIV Storage System and present options that are available for alerting and monitoring including an enhanced secure remote support capability This book is intended for IT professionals who want an understanding of the XIV Storage System It also targets readers who need detailed advice on how to configure and use the system Copy services and data migration features are covered in the Redbooks publication IBM XIV Storage System Copy Services and Migration SG24 7759 Host operating systems and other integration aspects are addressed in a separate publication IBM XIV Storage System Host Attachment and Interoperability SG24 7904 Refer also to the IBM Redpaper publication Using XIV in VMware environments REDP 4965 For details about thin provis
348. ge Management GUI XIV Top and XCLI tools are bundled together in a single downloadable package for each supported operating system There is also a separate XCLI package for AIX Linux Solaris and HPUX There is also a mobile monitoring dashboard version available for the iPhone and the iPad as well as Android devices 1 6 2 IBM XIV Storage Management GUI The IBM XIV Storage Management GUI acts as the management console for the storage system A simple and intuitive GUI enables storage administrators to manage and monitor all system aspects easily with almost no learning curve Figure 1 2 shows one of the top level configuration windows where you can also see flash SSD status Version 11 1 or later of the XIV System software is required for flash cache support File View Tools Help T Settings Launch XCLI J Launch xIvTop itso All Systems View By My Groups gt XIV 1310039 C gt System System Time 05 46pm Q SSD 1 Status OK Module 5 Status Figure 1 2 The XIV Storage Management GUI Chapter 1 IBM XIV Gen3 Storage System overview 11 The XIV Storage Management GUI also contains a demonstration mode To use the demonstration mode after the initial GUI program launch select Demo for the Mode and then click Login as shown in Figure 1 3 A password is not required There is also a Manager mode by which you can activate the Hyper Scale Storage Manager as shown in Figure 1 3 Storage Manage
349. ge System Architecture and Implementation It is also possible to create set credentials with xcli protect This command prompts you for the user and password and then stores them in a secure file in the system The defined default credentials are for the XCLI installation that is used These credentials are used when no credentials are supplied by using u and p or defined as environment variables See Example 4 5 Example 4 5 xcli protect C Users IBM ADMIN gt xcli protect User name itso Password Confirm password Credentials saved locally Getting help with XCLI commands To get help about the usage of commands assuming that you have set and logged in as a valid user proceed as shown in Example 4 6 Example 4 6 XCLI help commands c Users itso gt xcli c Users itso gt xcli c XIV2 help c Users itso gt xcli c XIV2 help command user_list format full The first command prints out the usage of xcli The second one prints all the commands that can be used by the user in that particular system The third one shows the usage of the user_list command with all the parameters There are various parameters to get the result of a command in a predefined format The default is the user readable format Specify the s parameter to get it in a comma separated format or specify the x parameter to obtain an XML format Fields The XML format contains all the fields of a particular command The user and the comma separated formats p
350. ge System to use OpenLDAP Directory groups for role mapping gt gt Idap_config set server_type Open Ldap Command executed successfully gt gt Idap_config set xiv_group attrib description Command executed successfully gt gt Idap_config set read_only role XIVReadonly Command executed successfully gt gt Idap_config set storage admin _role XIVAdmins Command executed successfully Chapter 5 Security 239 gt gt Idap_config set xiv_user UID XIV 0U Users DC itso DC storage DC ibm DC com Xiv_password Passw0rd Command executed successfully gt gt Idap_add server fqdn itso storage ibm com port 389 address 9 155 113 137 base _dn 0U Users DC itso DC storage DC ibm DC com Command executed successfully gt gt Idap_config get Name Value current_server version 3 Xiv_group_ attrib description storage admin role XIVAdmins read only role XIVReadonly session cache period 20 bind time limit 20 user_id_attrib uid first _expiration event 30 second expiration event 14 third expiration event 7 use ssl no Xiv_user UID XIV 0U Users DC itso DC storage DC i1 bm DC com server type Open Ldap user_name attrib uid group search depth 0 group search max_queries 39 group search stop when found yes gt gt Idap_list_servers FQDN Address Base DN itso storage ibm com 9 155 113 137 QU Users DC itso DC storage DC ibm DC com Alternatively the same configuration steps can be accomplished by using the X
351. gn host After the XIV Remote Support Proxy agent has been configured and started successfully new support center definitions must be entered on the XIV Storage System These definitions are done by your XIV Storage System support personnel An example of a configuration is shown in Example 7 40 Example 7 40 support_center_list of entry using XIV Remote Proxy XIV PFE GEN3 1310133 gt gt support_center_list Name Address Port Priority xivproxy 9 155 113 137 8988 5 Now a remote support connection can be made as shown in Example 7 41 Example 7 41 Establishing a remote support connection XIV PFE GEN3 1310133 gt gt support_center_connect Command executed successfully command line xiv python nextra remote support_client remote support client connect I 2810 114 1310133 m 1 Module 2 d xivproxy 9 155 113 137 8988 5 XIV PFE GEN3 1310133 gt gt support_center_ status State Connected sessions Timeout min Module Connected since Destination idle 0 no timeout 1 Module 2 2011 09 27 15 55 48 xivproxy 9 155 113 137 8988 More information about the Remote Support Proxy is in the BM XIV Remote Support Proxy Installation and User s Guide GA32 0795 7 4 Simple Network Management Protocol based monitoring The XIV Storage System supports Simple Network Management Protocol SNMP for monitoring 7 4 1 Monitoring tools SNMP based monitoring tools such as IBM Tivoli NetView or IBM Systems Director can be used to monitor the XIV Storag
352. gt STORAGE_POOL_SNAPSHOT_USAGE_INCREASED Then increase the pool size accordingly 2 4 Capacity allocation and thin provisioning Thin provisioning is a central theme of the virtualized design of the XIV Storage System because it uncouples the virtual or apparent allocation of a resource from the underlying hardware allocation The XIV Storage System implementation of thin provisioning provides these benefits gt Capacity associated with specific applications or departments can be dynamically increased or decreased per the demand imposed at a given point in time without necessitating an accurate prediction of future needs Physical capacity is only committed to the logical volume when the associated applications execute writes aS opposed to when the logical volume is initially allocated gt Because the total system capacity is designed as a globally available pool thinly provisioned resources share buffer of free space which results in highly efficient aggregate capacity usage without pockets of inaccessible unused space With the static inflexible relationship between logical and physical resources commonly imposed by traditional storage subsystems each application s capacity must be managed and allocated independently This situation often results in a large percentage of the total system capacity remaining unused because the capacity is confined within each volume at a highly granular level gt Capacity acquisitio
353. gt TPCUser Subsystem Advanced Probe TPCUser Subsystem Basic Probe PCUser Subsystem Standard Probe TPCUser Tape Advanced Probe gt TPCUser Tape Basic Probe TP gt Storage Resource Group Management Analytics Alerting TPCUser Tape Standard Probe C Server Probes e gt a a x 2 4 Edit Probe Creator TPCUser Name Subsystem Standard Probe Description Probe the Standard subsystem group Enabled Iv View Job History What to PROBE When to Run Alert Available Se omputer Groups Computers Clusters Fabric Groups Fabrics Tape Library Groups Tape Library Storage Subsystem Groups Storage Subsystems All Storage Subsystems gt I 2810 1300203 IBM 1 2810 6000105 IBM Hypervisors Current Selections Seotorage Subsystem Groups TPCUser Subsystem Standard Group X I 2810 1300203 IBM IV 2810 6000105 IBM Figure 7 86 Verifying the probe details Chapter 7 Monitoring 359 Performance monitoring XIV Storage System software V10 2 2 or higher can use the performance monitoring feature in Tivoli Storage Productivity Center V4 2 You can set up this feature with the Disk Manager Complete the following steps 1 Click IBM Tivoli Storage Productivity Center Configuration Utility Disk Manager tab Subsystem Performance Monitors Create Subsystem Performance Monitor to create a performance monitor as sho
354. gt gt dest_define dest emailtest type EMAIL email_address test ibm com smtpgws ALL heartbeat_test_hour 12 00 heartbeat_test_days Mon Command executed successfully gt gt dest_define dest smstest type SMS area_code 555 number 5555555 smsgws ALL Command executed successfully gt gt dest_define dest snmptest type SNMP snmp_manager 9 9 9 9 Command executed successfully gt gt dest_list Name Type Email Address Area Code Phone Number SNMP Manager User ITSO Catcher SNMP itsocatcher us ibm com smstest SMS 555 5555555 snmptest SNMP 9 9 9 9 emailtest EMAIL test ibm com Chapter 7 Monitoring 323 Finally the rules can be set for which messages can be sent Example 7 28 provides two examples of setting up rules The first rule is for SNMP and email messages and all messages even informational messages are sent to the processing servers The second example creates a rule for SMS messages Only critical messages are sent to the SMS server and they are sent every 15 minutes until the error condition is cleared Example 7 28 Rule definitions gt gt rule create rule emailtest min_severity informational dests emailtest snmptest Command executed successfully gt gt rule_create rule smstest min_severity critical dests smstest snooze time 15 Command executed successfully gt gt rule _list Name Minimum Severity Event Codes Except Codes Destinations Active Escalation Only ITSO Major Major all ITSO Catcher yes no emai ltest Inf
355. h Data or Interface Module can be equipped with one 400 GB flash SSD as fast read cache 6 TB for a full system with 15 modules In configurations using the 4 TB drives an 800 GB flash is available increasing the read cache to 12 TB for a full system with 15 modules gt An uninterruptible power supply UPS module complex comprising three redundant UPS units gt Two InfiniBand module interconnects and redundant power supplies RPSs gt A Maintenance Module gt An Automatic Transfer Switch ATS for external power supply redundancy 2 The 1 TB drives are actually stripped down 2 TB drives IBM XIV Storage System Architecture and Implementation gt A modem which is connected to the Maintenance Module for externally servicing the system The modem feature code FC 9101 is not available in all countries Module 15 Data Module 14 Data Module 13 Data Module 12 Data Module 11 Data Module 10 Data Module 9 Interface Module 8 Interface Module 7 Interface Module 6 Interface Module 5 Interface Module 4 Interface Module 3 Data Module 2 Data Module 1 Data UPS 3 ef lll ees geet IEF EEH a tL mes AT EE Em u i p Sar LL mim Wi w ra Module 15 Data Module 14 Data Module 13 Data Module 12 Data Module 11 Data Module 10 Data Module 9 Interface Module 8 Interface Module 7 Interface InfiniBand Module InfiniBand Module u Hie SS Tia
356. h can dynamically modify the QoS classes to ensure that the wanted level of performance is achieved Important When using the QoS Performance Class feature XIV consistently limits throughput to the specified QoS limits regardless of the host s I O demand 130 IBM XIV Storage System Architecture and Implementation Volume identification in hexadecimal The XIV Storage Management GUI can now be configured to show hexadecimal volume serial numbers rather than decimal volume serial numbers as shown in Figure 4 38 To enable this setting click the Tools portion of the menu bar click Management and select Hexadecimal in the Volume Serial drop down field CUS_Jake CUS_Lisa_143 CUS_ Zach Demo_Xen_1 Demo_Xen_2 Demo_Xen_NPIV_1 wap gt dirk DiskShadow SSS i 4 Unmap gt Figure 4 38 Volume identification in hexadecimal 4 3 2 XIV Storage System Command Line Interface As with the XIV Storage Management GUI the XIV Storage System Command Line Interface XCLI is an intuitive tool for managing IBM XIV systems More details are provided in this section Starting the XIV Command Line Interface The XCLI Session can be started in Windows by clicking Start gt Programs Alternatively if the Create Desktop XCLI icon was selected during the installation the XCLI Session shortcut is on the desktop Additionally an XCLI executable function is available for use from the command line These various methods
357. h other IBM Storage System interfaces Convenient links to related information make navigation quick and easy The following details give you an overview of the features that are available in the new web based GUI as it relates to the XIV Storage System 368 IBM XIV Storage System Architecture and Implementation The Home Dashboard window gives a general view of the current configured resources and their status From this window you can select various options for displaying more information as depicted in Figure 7 99 Storage Productivity Center Home Dashboard v Resources mous Server Resources p putes 0 2 Alay Spc Network Resources Capacity Recent Jobs Unacknowledged Alerts ul Storage Systems Last Day Last Day Poo Space OR i B6 Aoo CA 5 5 m 3 3 Failed 3 amp O Critical ee a 0 Warning 13 Warning C 4 Successful 1 Informational View all jobs View all alerts View performance jobs Figure 7 99 Tivoli Storage Productivity Center GUI Dashboard The icons on the left side of the display provide links to groups of related resources The XIV Storage System details are under the Storage Resources icon See Figure 7 100 The overview window can be easily customized to show the information that is most relevant to your requirements Storage Productivity Center Logout TER Home Dashboard v 7 Y Home a E Storage TAAI area Resourc
358. hannel and iSCSI ports rear view model 114 214 1 GbE Interface module az eaceons aaran Y_ereres a soletes ogot Borwase gasscos eRT ell Soistecese FRIAR Jada Figure 3 20 XIV Model 114 214 1 GbE and Model 214 10 GbE Interface Module with FC iSCSI ports Fibre Channel connectivity Each XIV Storage System Gen3 Interface Module has two 2 port 8 Gbps HBAs from Emulex Each HBA has eight PCle 2 0 lanes to the processor complex The HBAs feature hot upgradable firmware capability N Port ID Virtualization NPIV support and support 1400 concurrent exchanges per port There are four Fibre Channel ports available in each Interface Module for a total of 24 Fibre Channel ports in a fully configured XIV Storage System Certain partial rack configurations do not use all ports even though they might be physically present The Fibre Channel ports support 2 4 and 8 Gbps full duplex data transfer over short wave fibre links using 50 micron multi mode cable It is not possible to attach this HBA to a 1 Gbps SAN switch The allocation and use of specific ports in each module depend on your environment your specific requirements in terms of resiliency the nature of your host I O traffic and whether you use mirroring or not Most illustrations in this book show ports 1 and 3 allocated for host connectivity Ports 2 and 4 can be reserved for additional host connectivity or remote mirror and data migration connectivi
359. hat include an extension of MIB If your MIB file uses another extension you must rename it to MIB before the import When you import a new MIB file it is automatically loaded into the Available MIB Modules directory and is ready for use To load an imported MIB file complete the following steps 1 Select the MIB that you want to load within the Available MIBs Modules selection in the Manage MIBs window To support XIV be sure to load both UCD SNMP MIB and XIV MIB 2 Click Add Apply and OK This action loads the selected MIB file and the IBM Systems Director is ready to be configured for monitoring the IBM XIV Storage System as illustrated in Figure 7 70 Available MIB Modules ALTE OH CHEETSH LAYER 4 MIB ALTEOH CHEETASH LAYER MIB ALTEOGH CHEETSH NET YW ORE MIB ALTEOGH CHEETAH SWITCH MIB ALTEGH C5 PHYSICAL MIB ALTEGH ROOT MIB AQS ACL MIB AQS FAILOVER CPG MIB AOS G0O5 MIB BoP4 MIB BLADE MIB ELADE R OGT MIEB ELADESPPFALT MIEB BAMT GbESM 24 10G6 L2L3 MIB BRICGE MIB Brocade REG MIB Brocade TC THEETAH TRAP MIB CIRPACK MIB CIS CO C2900 MIB CISCO CDOP MIB CIS CO CLUSTER MIB CIS CO COMFIG hMAN MIB CISCO ENTIT yY VENDORT TPE GID MIB CIS 0O FLASH MIB CISCO IMAGE MIB CISCO MAC HOTIFICATICH MIB CIS CO MEMOR Y POOL MIB CIS CO PAGP MIB CISCO PING MIB Figure 7 70 XIV MIB file added IBM XIV Storage System Architecture and Implementation Loaded MIB Modules CME MIB HOST RESOURCES MIB HOST R
360. hat moment The number of IOPS being executed by module 8 at that moment The number of IOPS being executed by module 9 at that moment The status of module 4 at that moment The status of module 5 at that moment The status of module 6 at that moment The status of module 7 at that moment The status of module 8 at that moment The status of module 9 at that moment Tip In the output shown in Example 7 44 you can see the xivFreeSpaceSoft output and xivFreeSpaceHard output This information is only useful if you want to confirm how much space is not allocated to a pool If you have already allocated all usable hard and soft space to your pools this command confirms that there is no free space available outside your existing pools There might be significant free space within your pools Chapter 7 Monitoring 341 lf you want to cut the output back to a single field OID use the syntax shown in Example 7 45 You can also run the snmpget command to get the same output Example 7 45 SNMP walks with a single OID C usr bin gt snmpwalk v 2c c XIV m XIV MIB 10 10 1 10 xivFailedDisks XIV MIB xivFailedDisks INTEGER 0 C usr bin gt snmpwalk v 2c c XIV m XIV MIB 10 10 1 10 xivFreeSpaceSoft XIV MIB xivFreeSpaceSoft INTEGER 17111 If you start the SNMP walk without a start point you get a more interesting output You see the Linux version being run by the XIV Storage System modules and the uptime of the module you are probing
361. he Overview window In this way details about the resource are easily available for investigation into the cause of a specific alert 7 8 Custom monitoring The previous sections of this chapter focused on the predefined methods of monitoring the XIV Storage System We now look at ways to combine the various commands options and features so that you customize the monitoring of the XIV Storage System based on your specific needs or requirements Chapter 7 Monitoring 371 Combining the power of XCLI with the flexibility of scripting languages creates endless possibilities and ways to monitor the system For example you can create a script to monitor a specific component and alert you when it exceeds a custom threshold that you define 7 8 1 Custom monitoring of a volume 372 Example 7 47 demonstrates how to create a Windows Scripting Host WSH script to monitor the capacity of a specific volume and issue a custom event to alert you when the used capacity reaches a predefined limit The script can be scheduled to run automatically at specific intervals using the standard Windows Task Scheduler Example 7 47 WSH script to monitor a volume lt job id XIV_Vol_Monitor gt lt script language JScript gt WSH Example for Custom Monitoring of an XIV Volume Modify the following parameters with proper values var IPAddr 192 168 1 150 var Volume itso vol 2 var Threshold 700 var Severity Warning var Username
362. he CoD program and are able to use all of the 102 6 TB If they instead purchase one more activation for a total of eight and one more physical module for a total of 11 they are able to use 81 091 TB of 111 5 TB of usable capacity Each extra activation now buys 10 136 TB Figure 3 3 shows an example of the valid capacities in TBs of an XIV Storage System Gen3 with 2 TB drives 82 080 88 000 92 340 1600 111 500 115 408 114 146 117 307_ 125 900 124 523 127 971 129 040 161 300 Figure 3 3 CoD capacities for an XIV Storage System Gen3 with 2 TB drives Chapter 3 IBM XIV architecture components and planning 63 Figure 3 4 shows an example of the valid capacities in TBs of an XIV Storage System Gen3 with 3 TB drives 225 300 227 080 243 300 Figure 3 4 CoD capacities for an XIV Storage System Gen3 with 3 TB drives Figure 3 5 shows an example of the valid capacities in TBs of an XIV Storage System Gen3 with 4 TB drives 157 956 163 709 186 390 184 173 190 575 207 100 211 750 209 462 64 IBM XIV Storage System Architecture and Implementation 3 1 4 XIV Storage System Model 114 and Model 214 hardware components The system architecture of the XIV Storage System is designed wherever possible to use off the shelf components except for the Automatic Transfer Switch ATS that are not dependent upon specifically designed hardware or proprietary technology This architecture is optimi
363. he XIV Storage Management GUI 0 2 0 0 ee ee 264 OOZ WSING XIN TOD rini itn ee ee BAY a AEE a Reis aaan Pee i 271 6 3 3 Using the XIV Storage System Command Line Interface 275 6 3 4 Tivoli Storage Productivity Center 0 0 ce ees 277 6 4 Performance evaluation 0 0 ccc eee eee eas 278 Contents vV vi 64 1 Problem SOIVING SIGNS 4ac0c bGostaesa dt 1b abe eee oS been cd eRe aates 278 6 4 2 Feroimance ANalySIS 3252 40cse 59k Vertaal ee y RE Seed had Pea had 279 Chapter 7 Monitoring aana 0c ccc eee eee eee 285 7 1 Monitoring with XIV Storage Management GUI and XCLI 286 7 1 1 Monitoring by using the Systems menu 0 0 0 cee ee 286 7 1 2 Monitoring alerts for all defined IBM XIV systems with the GUI 288 7 1 3 Monitoring an individual XIV Storage System using the GUI 289 7 1 4 Monitoring with XIV Storage System Command Line Interface 297 11 5 AW QUGIVEVENT IOGOING 22 2 60265002 8osd thE CaO Need edad e cakes 304 7 1 6 Viewing events in the XIV Storage Management GUI 304 lel EVCNUAUNOUICS 4 vichie eaa te aa eae ew ead A 305 7 1 8 Viewing events using the XCLI 0 0 0 ee 306 7 1 9 Defining notification rules 0 0 0 eee tes 308 7 1 10 Monitoring using the IBM XIV Mobile Dashboard 5 309 7 1 11 Mobile Dashboard for the Apple iPhone 00
364. he components For details contact your IBM technical support Optional flash cache upgrade Flash cache can be upgraded by using the Miscellaneous Equipment Specification MES process if the XIV system was originally installed without flash cache Flash cache installation is a concurrent nondisruptive process to be performed by an IBM technician After flash cache is inserted into the XIV modules and enabled it is immediately ready for use by the XIV software Depending on the usage profile it helps improve performance IBM XIV Storage System Architecture and Implementation Copyright IBM Corp 2013 All rights reserved IBM XIV architecture components and planning This chapter describes the hardware architecture of the IBM XIV Storage System Gen3 family There are currently two models available for the Gen3 the newer Model 214 and the Model 114 This chapter covers the physical components for both models including the system rack Interface Modules Data Modules Management Modules disk drives network switches and power distribution devices There are two machine types associated with the XIV Storage System the 2810 and the 2812 The machine types refer to the standard warranty period IBM XIV systems with a machine type of 2810 have a 1 year warranty and ones with a machine type of 2812 havea 3 year warranty This chapter also includes an overview of the planning and other tasks required before and after deployme
365. he level of reliability standards attained by the XIV Storage System entails self diagnosis and early detection mechanisms that automatically phase out components before they actually fail In real systems the failure rate is not constant over time but rather increases with service life and duty cycle By actively gathering component statistics to monitor this trend the system ensures that components do not operate under conditions beyond an acceptable threshold of reliability and performance Therefore the XIV Storage System self healing mechanisms increase the already high level of availability of the system even further and also safeguard critical operations such as a rebuild from further component failures Total cost of ownership TCO is an important advantage of the XIV Storage System The self healing mechanisms make service actions less frequent When service actions are necessary to replace drives or modules the XIV Storage System has already automatically undergone rebuild and redistribution tasks to adapt itself to the changing configuration After component replacement the XIV Storage System automatically absorbs the new hardware into the new configuration The XIV Storage System leads the industry in the amount of time that is required to adapt to the new configurations All of these provisions together minimize maintenance time and costs and are key to the low TCO of the XIV Disk scrubbing The XIV Storage System maintains a scr
366. he names of all the hosts and clusters defined to the XIV Storage System The left pane shows the list of unauthorized hosts and clusters for this particular user group and the right pane shows the list of hosts that have already been associated to the user group User Group Access Control x Access Control for Application01_Group Unauthorized Hosts Clusters Authorized Hosts Clusters CLU_SOLMAN ITSO_Apphost2 SR test ITSO_Apphost1 p6 5704ab 2v19 Application host01 ITSO Blade 1780 Blade 3655_AMD Figure 5 31 Access Control Definitions window 5 Add or remove hosts from either list by selecting a host and clicking the appropriate arrow Finally click Update to save the changes Chapter 5 Security 195 196 You can verify which group that hosts have been associated with by viewing it in the Hosts and Clusters window See Figure 5 32 Name Type Cluster Access 3 Standalone Hosts g x3655_AMD default F SR test default Q p6 S704ab 2v19 default ITS0_Blade2 default ITS0_Blade1 default J IT 0_Apphost2 default Application01_Group J ITSO_Apphosti default Application01_Group J Application_host0d default Application03_ Mainz 3 CLU_SOLMANHN Ts0_Blades default CLU_SOLMAN Application02_Group Figure 5 32 Hosts and groups associations After a host or multiple hosts has been associated with a user group you can define user membership for the user group a user must have the application admini
367. he pool 10015 GB equals 9 11 TiB Available Storage Pool Space The unused soft space in the pool in binary TiB Configured Capacity Limit The hard size of the pool 5016 GB equals 4 56 TiB Remaining Configured Capacity The unused hard size in the pool in binary TiB Figure 7 94 shows how Tivoli Storage Productivity Center can report on XIV Storage System storage pools Navigation Tree Selection Storage Subsystems Administrative Services Services Data Sources Storage Pools By Storage Subsystem Number of Rows 19 Discovery Storage Subsystem Storage Pool tTypefs Track Format Status Storage Pool Space Available Storage Pool Space E Configuation test_pool RAID10 Unknown Tok T 45 48TB 7 7 IH IBM Tivoli Storage Productivity Center aiv 2810 13002091BM bfs_regular RAID 10 Unknown ok 944 00 GB ee Manager xIV 2810 13002091BM bis_source RAID 10 Unknown ok 96 00 GB Data Manager for Databases oe l Data Manager for Chargeback I 2810 1300209 BM bfs_target RAID 10 Unknown ok 96 00 GB Disk Manager XI 2810 1300209 BM bfs_thin RAID 10 Unknown ok 1 83 TB Storage Subsystems XI 2810 1300209BM ES _pool RAID 10 Unknown ok 3 64 TB Storage Optimizer xI 2810 1300209BM ITSO_SVC RAID 10 Unknown ok 7 83 TB SAN Planner XI 2810 1300209 IBM ITSO_test RAID 1O Unknown ok 64 00 GB 1 Monitoring XI 2810 1300209 1BM mirror_pool RAID 10 Unknown ok 298 00 GB Alerting XI 2810 13002091BM WindowsThinPool RAID 10
368. he volume name See Example 7 19 Example 7 19 The usage_get command by pool gt gt usage get pool ITSO 3 max 5 start 2013 09 19 08 00 00 end 2013 09 19 19 00 00 Time Volume Usage MiB Snapshot Usage MiB 2013 09 19 08 00 00 0 2013 09 19 09 00 00 0 2013 09 19 10 00 00 1920087 2013 09 19 11 00 00 1920087 2013 09 19 12 00 00 1920087 O OOOO Chapter 7 Monitoring 303 The usage is displayed in MB Example 7 20 shows that the volume is using 1920 GB of space Example 7 20 The usage_get command by volume gt gt usage get vol ITSO Blade5 Perf max 5 start 2013 09 19 08 00 00 end 2013 09 19 19 00 00 Time Volume Usage MiB Snapshot Usage MiB 2013 09 19 08 00 00 0 2013 09 19 09 00 00 0 2013 09 19 10 00 00 1920077 2013 09 19 11 00 00 1920082 2013 09 19 12 00 00 1920082 O OOOO 7 1 5 XIV audit event logging The XIV Storage System uses a centralized event log For any command that has been executed that leads to a change in the system an event entry is generated and recorded in the event log The object creation time and the user are also logged as object attributes The event log is implemented as a circular log and is able to hold a set number of entries When the log is full the system wraps back to the beginning If you need to save the log entries beyond what the system normally holds you can issue the event_list XCLI command and save the output to a file Event entries can be viewed by the XIV Storage Management GUI X
369. hich snapshots are deleted when there is insufficient space assigned within the pool for snapshots gt The soft snapshot reserve capacity and the hard space allocated to the storage pool are consumed only as changes occur to the master volumes or the snapshots themselves not as snapshots are created gt Fora more detailed explanation of snapshot deletion priority see IBM XIV Storage System Copy Services and Migration SG24 7759 Soft pool size Soft pool size is the maximum logical capacity that can be assigned to all the volumes and snapshots in the pool Thin provisioning is managed for each storage pool independently of all other storage pools gt Regardless of any unused capacity that might be in other storage pools snapshots within a given storage pool are deleted by the system according to the corresponding snapshot pre set priority if the hard pool size contains insufficient space to create an additional volume or increase the size of an existing volume Snapshots are deleted only when a write occurs under those conditions and not when allocating more space gt As described in Thinly provisioned storage pools on page 36 the storage administrator defines both the soft size and the hard size of thinly provisioned storage pools and allocates resources to volumes within a given storage pool without any limitations imposed by other storage pools The designation of a storage pool as a regular pool or a thinly provisio
370. hing feature However there are several best practices from a host perspective that can have a positive impact on XIV Storage System performance In addition the chapter describes XIV Storage System performance monitoring techniques using the IBM XIV Storage Management graphical user interface GUI and XIV Top Performance problem solving techniques are also described We provide guidance about how to interpret XIV Storage System performance information to determine objective levels of XIV Storage System performance characteristics such as response times I O rates and throughput Performance is one of the primary strengths of the XIV Storage System In this chapter we describe the following topics as they pertain to XIV Storage System performance y 6 1 XIV Storage System software and hardware architecture on page 248 6 2 Best practices for optimum performance on page 254 6 3 Performance monitoring on page 264 6 4 Performance evaluation on page 278 vY vyv Yy A popular topic that this chapter does not cover concerns the actual performance feeds and speeds of the XIV Storage System The IBM Storage Performance Team generally authors an XIV performance white paper when a significant XIV Storage System hardware or software performance enhancement becomes available This paper is at the following website http public dhe ibm com common ssi ecm en tsw03123wwen TSW03123WWEN PDF More white papers about XI
371. hms the latest XIV Gen3 components help meet requirements for extremely high performance workloads The latest Gen3 model can provide over its predecessors up to 4 5 times better performance for random database type workloads and up to 13 7 GBps sequential read throughput 1 5 7 Thin provisioning The system supports thin provisioning at the storage pool level which is the capability to allocate additional storage space to applications on a just in time and as needed basis allowing the most efficient use of available resource As a result significant cost savings are achieved compared to traditional provisioning techniques This benefit is achieved by defining a logical capacity that is larger than the actual physical capacity used 1 5 8 Processing power The XIV Storage System open architecture uses the latest processor technologies and is more scalable than solutions that are based on a closed architecture 1 5 9 SAN connectivity The XIV Storage System provides up to 24 x 8 Gb FC ports and up to 12 x 10 Gb Ethernet ports for iSCSI connection 1 5 10 Inter generational mirroring Mirroring between XIV Gen3 model 114 or model 214 and XIV second generation model A14 systems is supported The following prerequisites must be met however gt The XIV System software Version 11 1 0 or higher is required for the Gen3 systems Models 114 and Version 11 2 0 or higher for the Gen3 Model 214 gt The XIV System software Version 10 2
372. hostl xivhostlldap storage tucson ibm com This command connects to the Active Directory server using the secure LDAP port 636 Example B 9 Low level SSL validation using the openssl s_client openssl s_client host xivhostl xivhostlldap storage tucson ibm com port 636 CAfile cacert pem showcerts Server certificate subject CN xivhostl xivhostlldap storage tucson ibm com issuer C US ST Arizona L Tucson 0 xivstorage CN xivstorage emai Address ca xivsto rage org New TLSv1 SSLv3 Cipher is RC4 MD5 422 IBM XIV Storage System Architecture and Implementation Server public key is 1024 bit SSL Session Protocol TLSvl Cipher RC4 MD5 Session ID 9E240000CE9499A4641F421F523ACC347ADB91B3F6D3ADD5F91E271B933B3F4F Session ID ctx Master Key F05884E22B42FC4957682772E8FB1CA7772B8E4212104C28FA234F10135D88AE496187447313149F2E 89220E6F4DADF3 Key Arg None Krb5 Principal None Start Time 1246314540 Timeout 300 sec Verify return code 0 ok Attention To complete the configuration of SSL for the Active Directory you must reboot the Windows server Basic secure LDAP validation using the ldapsearch command After you have confirmed that the SSL connection is working you must confirm that you are able to search your LDAP directory using LDAP on a secure port This action confirms that the LDAP server can communicate using an SSL connection In our example we use the OpenLDAP client for SSL connection validation A CA
373. hown in Figure 4 51 Name Pete ITSO Gene SLES ITSO S ize GB 3011 7846 3441 206 Soft Snap Soft Hard Hard Vols GB Size GB Empty GB Size GB Vols GB Locked 1015 344 1651 1514 51 no 2288 791 4766 7846 946 no 1256 361 1824 3441 206 no 103 34 68 206 0 no Figure 4 51 Result of the pool_list command To create a pool enter the following command pool create pool ITSO Pool 2 size 515 snapshot_size 103 The size of the storage pool is specified as an integer multiple of 109 bytes but the actual size of the created storage pool is rounded up to the nearest integer multiple of 16x290 bytes The snapshot_size parameter specifies the size of the snapshot area within the pool It is a mandatory parameter and you must specify a positive integer value for it Run the following command to resize an existing pool pool resize pool ITSO Pool 2 size 704 snapshot_size 154 Chapter 4 IBM XIV Storage Management software 145 With this command you can increase or decrease the pool size The pool_create and the pool resize commands are also used to manage the size of the snapshot area within a storage pool To rename an existing pool run the following command pool rename pool ITSO Pool 2 new_name ITSO Pool To delete a pool run the following command pool delete pool ITSO Pool Approve or deny deletion by responding y n when prompted or use the y parameter with the pool delete command to approve deletion T
374. i E class 2 Public Primary Certification Class 2 Public Primary Certification r H Trusted Root Certification Authorities store contains 103 certificates Figure B 10 Windows certificate MMC snap in local computer Generating a Windows Server certificate request You must use the certreq command to generate a certificate request The certreq command uses a text instruction file which specifies the attributes needed to generate a certificate It contains attributes such as the subjects common name certificate key length and additional key usage extensions Active Directory requires that the certificate meet the following requirements gt The private key and certificate for the local machine must be imported into the local computer s personal keystore gt The fully qualified domain name FQDN for the Active Directory must be in the common name CN in the subject field or DNS entry in the subject alternative name extension gt The certificate must be issued by a CA that the Active Directory server and the XIV Storage System trust gt The certificate must contain the enhanced key usage extension that specifies the server authentication object identifier OID 1 3 6 1 5 5 7 3 1 This OID indicates that the certificate is used as an SSL server certificate IBM XIV Storage System Architecture and Implementation Example B 7 shows the text instruction file used to generate the certificate for the xivhostlldap storag
375. iBand 1U Maintenance Module 1x Modem 1U Maintenance Module 1x Modem 1U Maintenance Module 1x Modem Maintenance Module and Modem Full Rack 15x Modules 15x Modules 15x Modules 180x disks 2 TB disks 161 TB 3 TB disks 243 TB 360 GB memory cache 6 TB flash cache 6x Interface Modules 24x FC ports 22x iSCSI ports 9x Data Modules 180x disks 2 TB disks 161 TB 3 TB disks 243 TB 4 TB disks 422 TB 360 GB cache with 2 TB 3 TB disks 720 GB cache with 4 TB disks 6 TB flash cache 12 TB flash cache with 4 TB disks 6X Interface Modules 24x FC ports 22x iSCSI ports 9x Data Modules 180x disks 2 TB disks 161 TB 3 TB disks 243 TB 4 TB disks 422 TB 360 GB cache with 2 TB 3 TB disks 720 GB cache with 4 TB disks 6 TB flash cache 12 TB flash cache with 4 TB disks 6x Interface Modules 24x FC ports 12x iSCSI ports 9x Data Modules All XIV Gen3 hardware components ship preinstalled in a standard IBM T42 19 inch rack Data and Interface Modules provide the processing caching and storing of data All modules can be considered Data Modules in that they each contain a processor memory and 12 serial attached SCSI SAS drives The SAS drives can be 2 TB and 3 TB The SAS SED drives can be 2 TB 3 TB or 4 TB The Interface Modules are Data Modules but with more capabilities The Interface Modules have unique s
376. iated with high lOPS or bandwidth usage is typically an indication of a performance problem This can occur because of failure to adhere to best practices at the logical configuration level at any or all stages of the I O path and as a result of an insufficient storage hardware configuration to meet the peak I O workload demands It is critical to consider both avenues and not just one in isolation The former issue can be investigated by using the XIV Storage System GUI in conjunction with host configuration and monitoring tools to identify potential bottlenecks or non ideal implementation practices based on the concepts presented in this chapter The other possible action is to evaluate the potential performance impact of upgrading and adding XIV Storage System hardware to meet the specific aggregate I O workload requirements This can be investigated in part by engaging IBM or an IBM Business Partner to perform a Disk Magic study However keep in mind that Disk Magic assumes end to end logical configuration best practices have been implemented from the application layer to the storage subsystem layer Therefore attempting to use Disk Magic as the sole basis for diagnosing or isolating a performance issue might very well result in drawing an invalid conclusion and potentially prolong the duration of the problem Response times are a good measure of how well the XIV Storage System is performing The XIV System GUI uses the term atency They are both
377. ibm DC com In the first ldapsearch query we intentionally limited our search to the member Of attribute at the end of the 1dapsearch command so that the output is not obscured with unrelated attributes and values The value of the memberOf attribute contains the DN of the group The second ldapsearch query illustrates the CN XIVReadonly LDAP object content Among other attributes it contains the member attribute that points at the DN of the user defined as a member The attribute member is a multivalued attribute there can be more than one user assigned to the group as a member Member0f is also a multivalued attribute and a user can be a member of multiple groups The XIV Storage System can now be configured to use the member Of attribute for role mapping In Example 5 19 we map the Active Directory group XIVReadonly to the XIV read_only_role XIlVStorageadmin to the storage_admin_role and XIV user group app01_ group to Active Directory group XIVapp01_group You must be logged on as admin Example 5 19 Configuring XIV to use Active Directory groups for role mapping gt gt Idap_config set xiv_group_attrib member0f Command executed successfully gt gt Idap_config set read_only_role CN XIVReadonly CN Users DC itso DC storage DC ibm DC com Command executed successfully gt gt Idap_config set storage_admin_role CN XIVAdmins CN Users DC itso DC storage DC ibm DC com Command executed successfully gt gt Idap_config
378. ic rules This flexibility allows the storage administrator to decide for example where to direct alerts for various event types All these settings can also be done with XCLI commands Chapter 7 Monitoring 315 Setup notification and rules with the GUI To set up email or SMS notification and rules complete the following steps 1 From the XIV Storage Management GUI main window select the Monitor icon From the Monitor menu select Events to open the Events window as shown in Figure 7 37 xv XIV Storage Management Systems Actions View Tools Help ih D9 xr Setup E Rules T Email Settings z Export A All Systems gt RIV PFE 1340070 T Events F a Events 4 274 System Time Man Severity None Fae System Time All Alerting Date Local Time Event Code User 9 20 43 1 08 PM PFE2 USER HAS FAILED TO RUN _C 9 20 13 1 06 PM USER_HAS FAILED TO RUN_C z Monitor USER_HAS FAILED TO_RUN_C D413 ecco ee USER HAS FAILED TO_RUN_C alip ee m USER_HAS_FAILED_TO_RUH_C User cimi USER_HAS FAILED TO_RUN_C User itso SER HAS FAILED TO_RUN_C User cim USER_HAS FAILED TO_RUN_C User cim USER_HAS FAILED TO_RUN_C User cim PFEZ WSER_HAS FAILED TO_RUN_C User cim 9 20 13 12 54 PM XIV_PFE2 USER_HAS FAILED TO_RUN_C User cil Figure 7 37 Setup notification and rules 2 From the toolbar click Setup to start the Events Configuration wizard The wiza
379. icies Software Restriction Policies Application Control Policies k IP Security Policies on Local Computer Advanced Audit Policy Configuration Figure 5 67 Default Active Directory Password Policy settings If there is a user s password expiration or account lockout the user receives the message that is shown in Example 5 11 when attempting to log in to XCLI Example 5 11 XCLI authentication error because of account lockout gt gt Idap_ test user xivtestuserl password PasswOrd Error LOGIN FAILURE USER NOT AUTHENTICATED BY LDAP SERVER Details User xivtestuserl was not authenticated by LDAP server jtso storage ibm com The XIV Storage Management GUI in this situation also fails with the error message shown in Figure 5 68 MIV 02 1310114 wa GF Figure 5 68 XIV Storage Management GUI authentication failure because of account lockout Although password policy implementation greatly enhances overall security of the system all advantages and disadvantages of such implementation must be carefully considered One of the possible disadvantages is increased management impact for account management as a result of implementing complex password management policies Chapter 5 Security 225 Passwords A comprehensive solution for user password policy implementation is beyond the scope of this book LDAP user roles There are predefined user roles also referred to as categories used for day to day operation of the XIV Storage S
380. icrosoft Windows operating system Sun Java Systems Directory Oracle Directory Server Enterprise Edition provides support for UNIX like operating systems including Linux and Microsoft Windows OpenLDAP is simple small and easy to set up All LDAP servers share many basic characteristics because they are based on the industry standards Request for Comments RFC However because of implementation differences they are not always entirely compatible with each other For more information about RFC particularly regarding LDAP RFC 4510 4533 see the following website http www ietf org rfc html Current implementation of LDAP based user authentication for XIV Storage System does not support connectivity to multiple LDAP servers of various types However it is possible to configure an XIV Storage System to use multiple LDAP servers of the same type to eliminate a single point of failure The XIV Storage System supports communication with a single LDAP server at a time The LDAP authentication configuration allows specification of multiple LDAP servers that the XIV Storage System can connect to if a given LDAP server is inaccessible 5 6 4 LDAP role mapping Before any LDAP user can be granted access to XIV Storage System the user must be a member of an appropriate LDAP group There are three predefined role mappings when using LDAP storageadmin Defined as a single LDAP group securityadmin Defined as a single LDAP group readonly Defined
381. idually replaced with no need to stop using the module The power supply is a field replaceable unit FRU Each power supply is cabled to a different UPS unit 76 IBM XIV Storage System Architecture and Implementation SAS SED disk drives The XIV Storage System Gen3 modules can be configured with 2 TB 3 TB or 4 TB SAS Self Encrypted Drives SEDs These drives use the SAS 2 0 protocol and run at 7200 rpm They incorporate industry standard Self Monitoring Analysis and Reporting Technology SMART for enhanced reliability through prediction and early recognition of drive failure conditions The difference from normal SAS disk drives is that SAS SED drives enable the capability for encryption for data at rest See X V Security with Data at Rest Encryption REDP 5047 Model 114 and Model 214 common components Model 114 and Model 214 share the following components System board The XIV Storage System system board uses the PCle 2 0 bus which is twice the speed of the XIV Storage System Gen 2 PCle 1 0 bus and features more PCle lanes than its predecessor The system board has one RS 232 serial port one USB port and two Ethernet ports which are used for internal XIV Storage System management The monitor port and three USB ports are unused SAS host bus adapter The SAS host bus adapter SAS HBA is the controller card for the SAS disk drives in each module This HBA uses eight lanes of the PCle 2 0 bandwidth to communicate with the pro
382. ific MIB Because each vendor has a unique MIB subtree under the private subtree there is no conflict among vendors original MIB extensions The XIV Storage System comes with its own specific MIB You can download the MIB from IBM at the following website https www 304 ibm com support docview wss uid ssg1 4000913 Alternatively you can also use the mibget command from the XCLI For an SNMP trap sent by an XIV Storage System the MIB defines the following object IDs 1 3 6 1 4 1 2021 77 1 3 1 1 1 xivEventIndex A unique value for each event 1 3 6 1 4 1 2021 77 1 3 1 1 2 xivEventCode The code of the event 1 3 6 1 4 1 2021 77 1 3 1 1 3 xivEventTime The time of the event 1 3 6 1 4 1 2021 77 1 3 1 1 4 xivEventDescription A description of the event 1 3 6 1 4 1 2021 77 1 3 1 1 5 xivEventSeverity The severity of the event 1 3 6 1 4 1 2021 77 1 3 1 1 6 xivEventTroubleshooting Trouble shooting information XIV Storage System SNMP setup Configuring a new trap destination To use SNMP monitoring with the XIV Storage System you must first configure it to send SNMP traps to an SNMP manager such as the IBM Systems Director server which is defined in your environment Figure 7 55 shows where to start to set up the SNMP destination For more information see Setup notification and rules with the GUI on page 316 xiv XIV Storage Management systems Actions View Tools Help ih lt lt System Time Min Severity Non Type
383. igure 5 54 Unique ID s tab 13 Ask your LDAP admin for the value of those parameters in your environment Click Next to save the settings and proceed 14 In the Groups tab that is shown in Figure 5 55 you must define the group attributes that the XIV Storage System considers for the permissions These groups must be defined in LDAP LDAP Configuration Directory Services Groups Directory Services Groups ee Enter the full DN Distinguished Name of the groups that will be used to Server Type provide the StorageAdmin and the ReadOnly permission s to the LDAP users Adding Directory Services users to these groups will provide them with the LDAP Servers proper privileges on the XIV system XIV User E LIAN TPR ET Storage Admin Role CN XIVAdmins CN Users D Unique ID s Groups Read Only Role CN XVReadonly CN Us ers Secure LDAP Bind amp Cache Test amp Activation Finish a Ema Figure 5 55 Groups tab Chapter 5 Security 217 218 Our example has an LDAP group named XIVAdmins and another one named XIVReadonly 15 Define the role with the complete DN path In our example the Admin role is CN XIVAdmins CN Users DC itso DC storage DC ibm DC com and the Read Only role is CN XIVReadonly CN Users DC ibm DC storage DC ibm DC com as shown in Figure 5 55 on page 217 Click Next until you reach the Test and Activation tab 16 From the Test and Activati
384. igure 7 106 IBM Management Pack custom installation 5 Follow the prompts to complete the installation Chapter 7 Monitoring 379 380 6 The installation of the Storage Management Pack creates an icon on the desktop entitled IBM Storage SCOM control Utility Command Prompt Doubling clicking this icon opens a Windows command prompt in the correct directory to use the IBM provided scomu command You now need to use the scomu command from within this command prompt to add your IBM XIV systems to the monitoring list Use the following syntax for this command scomu add t xiv ip lt ip address gt username lt username gt password lt password gt Tip Pay close attention to the syntax You must use the double dash where required or the command fails So for example password works but password does not An example of the syntax you use and the expected responses is shown in Example 7 55 The device ID is the serial number of the XIV Storage System In Example 7 55 the device ID is 10114 because the XIV Storage System serial number is 1310114 The user name and password combination must be for an existing user name defined to the XIV Storage System If a read only user is used mirroring is not monitored Example 7 55 Adding an XIV Storage System to the SCOM monitoring list scomu add t xiv ip 10 0 20 102 username itso password password Connecting to the device 1 IBM XIV Storage System is found device ID
385. il IBM XIV Storage System Architecture and Implementation Use data at rest encryption with XIV Gen3 now Improve your cloud with RESTful API and OpenStack support Extend productivity with IBM Hyper Scale Bertrand Dufrasne Dietmar Dausner Roger Eriksson Roman Fridli ltzhack Goldberg Markus Oscheka Stephen Solewin Redbooks ibm com redbooks l International Technical Support Organization IBM XIV Storage System Architecture and Implementation December 2013 SG24 7659 07 Note Before using this information and the product it supports read the information in Notices on page Ix Eighth Edition December 2013 This edition applies to Release 3 4 of the XIV Storage System with XIV Storage System software Version 11 4 Copyright International Business Machines Corporation 2013 All rights reserved Note to U S Government Users Restricted Rights Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp Contents NOCES oreesa baste cog fs an eta G pate ead we cetera wrens geste ae erage era eee IX WA GOINGS o sis c5 an rete Yi fice ks ol ey Lid wag te Ree or Bh wee et Sd enh Bae X PITEIdJCE uaan a a hen Ra a hee a Aa ee ee ee eee ees xi AUNO oraraa E les a a Gee N A ar O a A ra ra E xii Now you can become a published author too anann 2 ce es xiii COMMEMS WECOME renarna emo Hey Mie a aa a eae de eile a E ied xiii Stay connected to IBM Redbooks
386. ils about encryption with XIV see the IBM Redpaper X V Security with Data at Rest Encryption REDP 5047 gt readonly As the name implies users assigned to the readonly role can only view system information A typical use for the readonly role is a user who is responsible for monitoring system status system reporting and message logging and who must not be permitted to make changes on the system gt technician The technician role has a single predefined user name technician assigned to it and it is intended to be used by IBM support personnel for maintaining the physical components of the system The technician is limited to the following tasks physical system maintenance and phasing components in or out of service The technician has restricted access to the IBM XIV Storage System Architecture and Implementation system and is unable to perform any configuration changes to pools volumes or host definitions on the XIV Storage System gt xiv_development The xiv_development role has a single predefined user name xiv_development assigned to it and it is intended to be used by IBM development personnel gt xiv_maintenance The xiv_maintenance role has a single predefined user name xiv_maintenance assigned to it and it is intended to be used by IBM maintenance personnel gt xiv_hostprofiler The xiv_hostprofiler role has a single predefined user name xiv_hostprofiler assigned to it and it is intended to be
387. imum number of discrete 17 GB increments needed to meet the requested size specified in 512 byte blocks However the size that is reported to hosts is equivalent to the precise number of blocks defined Incidentally the snapshot reserve capacity associated with each storage pool is a soft capacity limit and it is specified by the storage administrator although it effectively limits the hard capacity consumed collectively by snapshots as well Actual volume size Tip Defining logical volumes in terms of blocks is useful when you must precisely match the size of an existing logical volume on another system This value reflects the total size of volume areas that were written by hosts The actual volume size is not controlled directly by the user and depends only on the application behavior It starts from zero at volume creation or formatting and can reach the logical volume size when the entire volume has been written Resizing of the volume affects the logical volume size but does not affect the actual volume size The actual volume size reflects the physical space used in the volume as a result of host writes It is discretely and dynamically provisioned by the system not the storage administrator The discrete additions to actual volume size can be measured in two ways by considering the allocated space or the consumed space The allocated space reflects the physical space used by the volume in 17 GB increments The consumed space reflec
388. ine the location of the secondary module that houses the copy of the referenced data Again this module can be either an Interface Module or a Data Module but it is not the same as the primary module The data is redundantly written to the local cache of the secondary module IBM XIV Storage System Architecture and Implementation After the data is written to cache in both the primary and secondary modules the host receives an acknowledgement that the I O is complete which occurs independently of the data being destaged to physical disk System shutdown and power on sequence When the XIV Storage System detects that all power is lost it waits for 30 seconds to ensure that this outage is not a temporary power outage During this time it runs on three uninterruptible power supply UPS units that are part of every XIV Storage System configuration The XIV Storage System needs only two of these units to be operational The third UPS unit is redundant If power is not restored within 30 seconds the XIV Storage System executes a graceful shutdown sequence There is enough battery power in the XIV Storage System to execute such a shutdown sequence twice Because of the XIV Storage System grid topology a system shutdown event essentially entails the graceful shutdown of all modules within the system Each module can be thought of as an independent entity that is responsible for managing the destaging of all data in cache that has not already been w
389. ing and use _ssd caching default For an illustration see Example 4 19 Example 4 19 State of a volume XIV 1310039 Coruscant gt gt vol_ list x vol Res Fra Vol _02 lt XCLIRETURN STATUS SUCCESS COMMAND LINE vol_list x vol Res Fra Vol _02 gt lt QUTPUT gt lt volume id bec1240012f gt lt creator value itso gt lt creator category value storageadmin gt lt id value bec1240012f gt lt name value Res Fra _Vol_02 gt lt size value 17 gt lt ssd_caching value disabled gt lt use_ssd_ caching_default value yes gt lt volume gt lt QUTPUT gt lt XCLIRETURN gt The value of the use_ssd_ caching default parameter indicates whether the volume follows the default system state for flash cache gt Ifthe value is yes the volume follows the default system state for flash cache gt Ifthe value is no the volume does not inherit the default setting for flash cache It means that if the global system setting for the caching is changed the volume keeps its current ssd_caching value 172 IBM XIV Storage System Architecture and Implementation Security This chapter describes the IBM XIV Storage System security features from various perspectives The chapter covers the following topics Physical access security x509 certificate validation and management Configuring IPv6 addresses Configuring Internet Protocol Security IPSec Connectivity Native user authentication Considerations when u
390. ing the keyword never for these two parameters allows the connection to remain established indefinitely gt The client can also choose to set a unique password for a session when it is initiated This password must be provided to the IBM Support representative in order for them to complete the authentication process and access the XIV Storage System gt In addition the client can see the XRSC connectivity status at any time disconnected idle or in session and can choose to forcibly disconnect the connection regardless of whether a support session is in progress or not Although forcibly terminating a support session using the timeout or force disconnect mechanisms is not desirable these mechanisms do exist and the client has full control over whether to proceed with a support session The initiation or loss of connection to the XRSC causes the system to generate events that can be seen on the machine s event log These events can be forwarded to any destination of the client s choice like any other event using the XIV Storage System event rules mechanism Connection loss events whether because of a transport error timeout or due to specific client action specify whether the connection was idle or in use at the time of disconnection A warning event is issued 15 minutes before the timeout parameter disconnects a busy support session If the connection is lost because of a network error before the timeout for the session has exp
391. intranet The Back Server manages most of the logic of the system It is located within the IBM intranet The Back Server is access controlled Only IBM employees authorized to perform remote support of the XIV Storage System are allowed to use it and only through specific support interfaces not with a CLI or a GUI shell The Back Server is in charge of authenticating a support person It provides the support person with a user interface Ul through which to choose a system to support based on the support person s permissions It also provides the list of systems currently connected to the Front Servers and manages the remote support session as it progresses logging it allowing additional support persons to join the session and so on The Back Server maintains connection to all Front Servers Support people connect to the Back Server using any SSH client or an HTTPS connection with any browser Figure 7 49 provides a representation of the data flow of the XIV Storage System to IBM Support Customer Network Customer DMZ Figure 7 49 XRSC To initiate the remote connection process the following steps are performed 1 oOo 7 eE bh The client initiates an Internet based SSH connection to XRSC either through the XIV Storage Management GUI or XCLI XRSC identifies the XIV Storage System and marks it as connected Support personnel connect to XRSC using SSH over the IBM intranet XRSC authenticates the support person again
392. iods Interface Module balance Another important thing to check when evaluating XIV Storage System performance is the balance of I O across the different Interface Modules This evaluation requires an understanding of the SAN cabling and zoning But if the preferred multipathing configuration described in 6 2 3 Multipathing considerations on page 257 is followed every host uses every Interface Module equally which can be seen in the XIV Storage Management GUI IBM XIV Storage System Architecture and Implementation In Figure 6 33 Interface Modules 4 8 all have basically the same I O characteristics This balance is typical and desirable Interface Module 9 has no I O during most of this workload Then at 14 45 it starts to perform its share of the job of handling the I O workload Ina normal situation all Interface Modules work together all the time There are certain older operating systems such as VMware ESX 3 5 that do not use more than one path to a volume On these operating systems ensure that you use more than one volume and that the paths for the volumes are balanced across all Interface Modules You can accomplish this task by changing the preferred path for these volumes so that these operating systems cannot harm the performance of other operating systems or applications Compare Interfaces gu 847 ELE KAY IOPS 9000 3500 3000 7500 7000 6500 aN nil 6000 ANTI 5500 5000 i pi 4500 4
393. ion This command connects to the specified host and lists the server certificate the certificate authority chain supported ciphers SSL session information and verify return code If the SSL connection works the openssl s_ client command result in the verify return code is 0 ok Example B 11 shows the output of the openssl s_client command connecting a Linux server xivstorage org to the Sun Java Directory server xivhost2 storage tucson ibm com This command connects to the Sun Java Directory server using the secure LDAP port 636 Example B 11 Low level SSL validation using the openssl s_client Openssl s_ client host xivhost2 storage tucson ibm com port 636 CAfile cacert pem showcerts Server certificate subject C US ST Arizona L Tucson 0 xivstorage OQU ITSO CN xivhost2 storage tucson ibm com issuer C US ST Arizona L Tucson 0 xivstorage CN xivstorage emailAddress ca xivsto rage org IBM XIV Storage System Architecture and Implementation Acceptable client certificate CA names 0 Sun Microsystems CN Directory Server CN 636 CN xivhost2 storage tucson ibm com C US ST Arizona L Tucson 0 xivstorage CN xivstorage emai 1Address ca xivstorage or g SSL handshake has read 2144 bytes and written 328 bytes New TLSv1 SSLv3 Cipher is AES256 SHA Server public key is 1024 bit Compression NONE Expansion NONE SSL Session Protocol TLSvl Cipher AES256 SHA Session ID 48B43B5C985FE1F6BE3F455F8350A4155DD3330E6BD09070DDCB80D
394. ion03_Mainz user group This user is an applicationadmin with the Full Access right set to no 5 5 5 Password management and resets Password management in native authentication mode is internal to the XIV Storage System The XIV Storage System has no built in password management rules such as password expiration preventing reuse of the same passwords or password strength verification Furthermore if you want to log on to multiple systems at the same time through the XIV Storage Management GUI your user ID must be registered with the same password on all IBM XIV systems managed by the XIV Storage Management GUI In native authentication mode if users can log in they can change their own passwords The predefined admin user is the only user that is authorized to change other users passwords Direct access to a user credential repository is not permitted System security is enforced by allowing password changes only through the XIV Storage Management GUI and XCLI Figure 5 38 shows how to change a password Right click the selected user in the Users window and click Change Password from the menu Ungrouped technician Technician w development XIV Development ee Change Password esas aaa Properties AIV Maintenance amp amp amp xiv_hostprotiler AIV Host Profiler amp xiv_maintenance amp xiv_msms Storage Administrator Figure 5 38 XIV Storage Management GUI Change Password menu The Change Passwo
395. ioning and space reclamation refer to the Redpaper XIV Thin Provisioning and Space Reclamation REDP 5001 For information about XIV deployment in an OpenStack environment refer to the Redpaper Using the IBM XIV Storage System with OpenStack Cloud Environments REDP 4971 For information about IBM Hyper Scale refer to the Redpaper BM Hyper Scale in XIV Storage REDP 5058 For information on encryption refer to the Redpaper XIV Security with Data at Rest Encryption REDP 5047 Copyright IBM Corp 2013 All rights reserved xi Authors This book was produced by a team of specialists from around the world This book was produced by a team of specialists from around the world working for the International Technical Support Organization at the IBM European Storage Competence Center in Mainz Germany Bert Dufrasne is an IBM Certified Consulting I T Specialist and Project Leader for IBM System Storage disk products at the International Technical Support Organization ITSO San Jose Center He has worked at IBM in various I T areas He has authored many IBM Redbooks publications and has also developed and taught technical workshops Before joining the ITSO he worked for IBM Global Services as an Application Architect He holds a Master s degree in Electrical Engineering Dietmar Dausner is a certified XIV Product Field Engineer in Germany for the EMEA region and joined IBM as a manufacturing test engineer for storage devices Later
396. ions 4dd new storage subsystems or CIMOMs by providing the connection properties Once the connection Select Device properties have been added click next to continue IF you wish to remove one of the connections select ik From the table and click remove w Select Device Type c gt Configure storage subsystem connections Device Type iem aly Discover storage subsystems IP Address ja 155 53 252 Select Storage Subsystems Username Jtpcadmin Data Collection Password Pieter Summary Results Add Clear IF Address 3 15553 250 9 155 53 251 Remove Figure 7 81 Configure storage subsystem connections 6 After all three IP addresses are added click Next and the wizard automatically performs a discovery 7 Click Next again and the discovered XIV Storage System is shown as unconfigured storage as shown in Figure 7 82 E Configure Devices Select Storage Subsystems vw Select Device Type vf Select Device subsystems that you wish bo configure Configure storage subsystem connections 9 155 55 251 a Discover storage subsystems gt Select Storage Subsystems Data Collection Suramar Results Figure 7 82 New XIV Storage System discovered in Tivoli Storage Productivity Center Probing phase Tivoli Storage Productivity Center discovered new storage subsystems Select the unconfigured storage IP Address Name a Device The newly added XIV Storage System must be pro
397. ip You can use the y parameter at the end of a command that requires confirmation to have it auto approved This parameter is useful for scripting Run the following command to move the volume named Zejn_02 to ITSO Pool 3 vol_move pool ITSO Pool 3 vol Zejn_ 02 The command succeeds only if the destination storage pool has enough free storage capacity to accommodate the volume and its snapshots The command moves a particular volume and its snapshots from one storage pool to another one However if the volume is part of a consistency group the entire group must be moved In this case the cg_move command is the correct solution cg move cg Mainz01 CG pool ITSO Pool 3 All volumes volume snapshots and snapshot groups of the consistency group are moved Thinly provisioned pools To create thinly provisioned pools specify the hard_size and the soft_size parameters For thin provisioning concepts see 2 4 Capacity allocation and thin provisioning on page 34 A typical storage pool creation command with thin provisioning parameters can be issued as shown in the following example pool create pool ITSO Pool hard_size 807 soft_size 1013 lock behavior read_only Snapshot _size 206 The soft_size parameter is the maximal storage capacity seen by the host and cannot be smaller than the hard_size parameter which is the hard physical capacity of the storage pool If a storage pool runs out of hard capacity all of its volumes are
398. ired the system automatically tries to reconnect to any of the configured XRSC servers While a support session is in progress the XIV Storage System generates events and shows the machine s status on the GUI window as usual Therefore for example the client can see the process of phasing out a module or the restart of client visible machine services as they happen Starting an XRSC connection using the GUI The XRSC definitions are configured at the time the system is installed To start the connection from the GUI click Tools gt Support Center as shown in Figure 7 50 aw XIV Storage Management systems Actions View Help ih KI th Settings ia Launch XCLI ia Launch XIVTop A AllSystems 2 gt Gaza Commands Log Collect Support Logs Partitions Count KIVTOP KCLI Management Figure 7 50 Starting an XRSC Remote Support Center connection Chapter 7 Monitoring 329 330 Select the wanted support center from the list and click the Connect Support Center icon as shown in Figure 7 51 Support Center Status no connection Front XRSC 2 195 110 41 141 Connect Support Center f Port Type Management R Close Figure 7 51 Select the wanted support center and click the Connect Support Center icon The window shown in Figure 7 52 prompts you for the Session Timeout Idle Timeout and Connection Password values The timeout values are specified in minutes and disconnect the session when th
399. is temporarily less than the allocated soft capacity The soft and hard system sizes do not revert to the original values until a replacement disk or module is phased in and the resulting redistribution process is completed Important Although it is possible to resize or create volumes snapshots or storage pools while a rebuild is underway do not perform these activities until the system completes the rebuild process and restores full data redundancy Chapter 2 IBM XIV Storage System logical architecture and concepts 53 2 7 3 Exclusive additional functions for reliability and availability This section describes other features that contribute to XIV Storage System reliability and availability Disaster recovery All high availability SAN implementations must account for the contingency of data recovery and business continuance following a disaster as defined by the organization s recovery point and recovery time objectives The provision within the XIV Storage System to efficiently and flexibly create nearly unlimited snapshots coupled with the ability to define consistency groups of logical volumes constitutes integral elements of the data preservation strategy In addition the XIV Storage System data mirroring functionality facilitates excellent potential recovery point and recovery time objectives as a central element of the full disaster recovery plan Proactive phase out and self healing mechanisms A further enhancement to t
400. is that each host engages the I O services of each XIV Storage System Interface Module Experience has shown that the first multipathing configuration in Figure 6 3 on page 256 is the best overall general purpose configuration Host multipathing reliability during path error recovery in certain operating systems is complicated by increasing numbers of paths per LUN Certainly for host systems with two HBAs the six paths per LUN method is the best way to go The following information relates to Figure 6 3 on page 256 gt Each host is equipped with dual HBAs Each HBA or HBA port is connected to one of two FC switches gt Each of the FC switches has a connection to three separate Interface Modules gt Each LUN has six paths Chapter 6 Performance 257 The second multipathing configuration that is shown in Figure 6 4 is more appropriate for benchmarking and higher performance host systems with the highest I O requirements The primary differentiator is the host s ability to handle the higher number of paths per LUN It is not a best practice to use the configuration in Figure 6 4 for most production applications The primary reason has to do with the complexity that the added paths per LUN imposes on the host multipathing software Host 1 D Host 2 gt N oD Host 3 Q N gt x Host 4 co Host 5 Patch Panel FC Ports SAN Hosts Figure 6 4 Multipath configuration for larger hosts The following inf
401. isk Magic that aligns client performance requirements with both the performance capacity and data storage capacity of an XIV Storage System configuration Disk Magic is licensed to IBM and IBM Business Partners 6 2 2 Number of logical unit numbers When planning an XIV Storage System logical configuration consider how many logical unit numbers LUNs to configure per host or per application With an XIV Storage System there is no need to create many LUNs As a matter of fact when planning to deploy applications on an XIV Storage System the primary design principle should be fewer LUNs and larger LUNs Every XIV Storage System LUN regardless of size is already architecturally automatically configured within the XIV Storage System for optimum performance A planning item to any application migration to the XIV Storage System is the significant consolidation of the number of LUNs Small quantities of volumes and LUNs are simpler to manage Using fewer LUNs compared to a traditional storage subsystem benefit read cache hit rates and improves space utilization because there are less orphaned physical capacity allocations However if you must separate logs from data or need to separate LUNs to create a disaster recovery strategy that includes snapshots consistency groups and volume replication you might need to use more volumes In addition certain host platforms still require multiple volumes The best approach is to examine the app
402. ist filter NOTOK Component ID Status Currently Functioning 1 Disk 7 12 Failed yes In Example 7 9 the module_1list command shows details about the modules themselves If the module parameter is not provided all the modules are displayed In addition to the status of the module the output describes the number of disks number of Fibre Channel FC ports and number of IP network Small Computer System Interface iSCSI ports Example 7 9 The module_list command gt gt module_list module 1 Module 4 Component ID Status Currently Functioning Target Status Type Data Disks FC Ports 1 Module 4 OK yes g3 0 interface 12 4 iSCSI Ports Temperature 2 22 It is possible to use the x XCLI parameter with commands to provide even more information about a component The x parameter shows the output of a command in XML format You can see the additional information as displayed in Example 7 10 Example 7 10 Using x parameter to show additional information in XML format gt gt module_list module 1 Module 4 x lt XCLIRETURN STATUS SUCCESS COMMAND LINE module_ list module 1 Module 4 x gt lt QUTPUT gt lt module id 5760a900003 gt lt component_id value 1 Module 4 gt Chapter 7 Monitoring 299 lt status value 0K gt lt currently functioning value yes gt lt requires service value gt lt service reason value gt lt target status value gt lt type value g3 0_interface gt lt disk bay count value 12
403. istrator when using the XIV Storage Management GUI as either regular or thinly provisioned When using the IBM XIV Storage System Command Line Interface XCLI there is no specific parameter to indicate thin provisioning for a storage pool You indirectly and implicitly create a storage pool as thinly provisioned by specifying a pool soft size greater than its hard size With a regular pool the host apparent capacity is guaranteed to be equal to the physical capacity reserved for the pool The total physical capacity allocated to the constituent individual volumes and collective snapshots at any given time within a regular pool reflects the current usage by hosts because the capacity is dynamically consumed as required However the remaining deallocated space within the pool remains reserved for the pool and cannot be used by other storage pools In contrast a thinly provisioned storage pool is not fully backed by hard capacity meaning that the entirety of the logical space within the pool cannot be physically provisioned unless the pool is transformed first into a regular pool However benefits can be realized when physical space consumption is less than the logical space assigned because the amount of logical capacity assigned to the pool that is not covered by physical capacity is available for use by other storage pools Figure 2 6 on page 37 shows a regular storage pool and a thin pool gt Inthe regular pool the host system sees
404. it is necessary to perform concurrent operations collectively across a set of volumes so that the result of the operation preserves the consistency among volumes For example effective storage management activities for applications that span multiple volumes or creating point in time backups is not possible without first employing consistency groups This consistency between the volumes in the group is paramount to maintaining data integrity from the application perspective By first grouping the application volumes into a consistency group it is possible to later capture a consistent state of all volumes within that group at a given point in time using a special snapshot command for consistency groups Issuing this type of a command results in the following process 1 Complete and destage writes across the constituent volumes 2 Suspend I O activity simultaneously across all volumes in the consistency group 3 Create the snapshots 4 Resume normal I O activity across all volumes The XIV Storage System manages these suspend and resume activities for all volumes within the consistency group Consistency Additional mechanisms or techniques such as those provided by the Microsoft Volume Shadow Copy Service VSS framework might still be required to maintain full application consistency from a host system perspective For more information see IBM XIV Storage System Copy Services and Migration SG24 7759 Storage pool relationships a
405. itecture components and planning 85 3 1 11 Hardware support This section covers important features of the XIV Storage System used by internal functions and IBM Maintenance if a problem arises with the system Module USB to Serial connections The Module USB to Serial connections are used by internal system processes to keep the inter communication between the modules active when the normal network connection is not operational Modules are linked together with USB to Serial cables in groups of three These links are also used by IBM Maintenance for repair to the internal network The connection sequence is shown in Figure 3 25 gt Seed i 1 2 seee seseo oli 9 mm mmm c PB RRRRR i H doam M ORE EN sdi ME AH He sea anagement d E Connections USB to Serial kj SBS eew eee ae F PDO PA CKD KK RK kk kD m HRI CH efoto fi SS 555 PSs 652505 ie a 33 i eepo ananasas l ssnannn OR a mm 8h Figure 3 25 Module USB to serial Maintenance Module The 1U Maintenance Module and the modem which are installed in the middle of the rack are used for XIV Storage System support and for the IBM personnel to maintain and repair the system This device is only used to gain remote access to the XIV System through the modem for support personnel When there is a software or hardware problem that needs the attention a remote connection is required an
406. ith a 10 GbE adapter The adapter is a Mellanox ConnectX 2 EN network interface card as shown in Figure 3 21 It serves two 10 GbE ports using Optical Transceiver Modules SFP Mellanox Connect lt 2 EN network interface card SFP Optical Transceivers oe en pen aa i i l p ae 5 i ee F Figure 3 21 Model 214 10 GbE adapter The 10 GbE adapter provides enhanced iSCSI host connectivity and provides adequate infrastructure for potential FCoE Fibre Channel over Ethernet functionality if IBM decides to Offer it There are up to twelve 10 GbE ports available for iSCSI over IP Ethernet services The number of active ports depends on the number of modules installed in the rack See Figure 3 2 on page 61 The active ports are connected to the client s IP network through the patch panel For that reason the patch panel in Model 214 10 GbE differs from the patch panel in the previous Model 114 and Model 214 1 GbE as shown in Figure 3 24 on page 85 You can operate iSCSI connections for various uses gt As an iSCSI target that attached hosts can connect to using the iSCSI protocol gt As an iSCSI initiator for remote mirroring when connected to another iSCSI port gt As an iSCSI initiator for data migration when connected to an iSCSI storage system from another vendor For each iSCSI IP interface you can define these configuration options gt IP address mandatory gt Network mask mandatory gt Def
407. its and the slow reads from disk The amount of cache also has a significant impact on read cache hits The more cache that you have the more data you can put in there that can result in a read hit XIV cache sizes can be described only as huge A full rack has 720 GB of DRAM cache and 12 TB of flash cache High read cache hit percentages are the most significant factor in good read performance and low read response times The nature of the application read I O is what defines the read cache hit percentage If the XIV algorithms do a good job of prestaging data into flash or DRAM cache the read cache hit percentage is high XIV plays a large part in read cache hit percentages as well XIV has exceptionally aggressive read data prestaging algorithms to get this read data into the huge XIV System cache And XIV has a fixed number of spinning disks But all these factors are fixed When you see variations in the read hit percentage in the XIV statistics GUI it is the application that is causing these variations Read response times are highly dependent upon the size of the average read I O operation Very large read I Os take longer for disk storage systems to process For transaction workloads with read I O sizes of 32 KB or less it is common to observe read response times in the low double digit millisecond range Again the best way to evaluate read response times is to compare them to the read response times recorded during good performance per
408. ity exceeds the available hard capacity by 51 GB you can thinly provision the volumes collectively by up to 66 7 assuming that the snapshots are preserved and the remaining capacity within the pool is allocated to volumes Snapshot R This is the volume size defined during CAE aa volume creation resizing Fe Snapshots Volume 3 Soft Size Volume 4 Soft Size Consumed 34GB 51GB Soft Space Unused A A M Logical View For a Thin Storage Pool the pool soft size is greater than the pool hard size The snapshot reserve limits the maximum hard space that can be consumed by snapshots but for a Thin Storage Pool it does not guarantee that hard space will be available 2 gt T 2 D gt ou Volume 3 Volume 4 napshots Unused Consumed Consumed Consumed Hard Space Hard Space ard Space a ar This is the physical space consumed collectively by the snapshots in the pool Since snapshots are differential at Volume 3 Volume 4 the partition level multiple snapshots can potentially exist Allocated Allocated within a single 17GB increment of capacity Hard Space Hard Space The consumed hard space grows as host writes In a Thin Storage Pool the maximum hard space consumed by a volume accumulate to new areas of the volume The is not guaranteed to be equal to the size that was allocated because it is system
409. ive Directory gt The distinguished name DN of the LDAP object is known and valid Appendix B Additional LDAP information 405 gt The password is valid gt The designated attribute description has a predefined value assigned Storage Administrator When the Active Directory account verification is completed we can proceed with configuring the XIV Storage System for LDAP authentication mode We still have a few unassigned LDAP related configuration parameters in our XIV Storage System as shown in Example B 2 Example B 2 Remaining XIV LDAP configuration parameters gt gt Idap_ config get Name Value base dn Xiv_group attrib description third expiration event 7 version 3 user_id attrib objectSiD current_server use ssl no session_cache_period second expiration event 14 read only role Read Only storage admin role Storage Administrator first_expiration event 30 bind time_limit 0 The parameters are defined as follows base dn The base DN distinguished name which is the parameter that specifies where in the Active Directory LDAP repository that a user can be located In our example we use CN Users DC xivhost1ldap DC storage DC tucson DC ibm D C com as the base DN see Example B 1 on page 404 current_server A read only parameter that cannot be populated manually This parameter is updated by the XIV Storage System after the initial contact with the LDAP server is established ses
410. ized conventional RAID arrays By comparison the array rebuild workload is greatly dissipated greatly reducing the relative impact on host performance Inaconventional RAID array the whole disk is re created which often includes unused space Conventional RAID array rebuilds place many times the normal transactional load on the disks and substantially reduce effective host performance gt The XIV Storage System maintains universally accessible reserve space on all disks in the system as described in Global spare capacity on page 31 Standard dedicated spare disks used during a conventional RAID array rebuild might not be globally accessible to all arrays in the system gt Hotspots are statistically eliminated because the XIV Storage System maintains access density equilibrium which reduces the chances of isolated workload induced failures gt The XIV Storage System data distribution eliminates localized drive stress and associated additional heat generation gt Modules intelligently send information to each other directly There is no need fora centralized supervising controller to read information from one Disk Module and write to another Disk Module 50 IBM XIV Storage System Architecture and Implementation gt All disks are monitored for errors poor performance or other signs that might indicate that a full or partial failure is impending Dedicated spare disks in conventional RAID arrays are inactive
411. ject Discovery For all objects of class XIV Monitor Computer Object Discoveries 2 gt Tasks Management pack objects are now scoped to Xiv device Configuration Xiv Monitor Computer Change Scope x 7 Q Look for Find Now Clear A Object Discovery Name Target Management Pack Enabled byd Properties 4 Discovered Type XW device Configuration 1 py XIV Configuration Discovery gt XIV Monitor Computer IBM Storage XIV Yes ae AT FAA Properties i E E i Ee Overrides gt 4 Discovered Type XN Monitor Enabl napig cay Monitor Computer Discover Windows Computer IBM Storage XIV Yes BS Overrides gt Disable the Object Discovery j Delete Del Override the Object Discovery gt For all objects of class XI Monitor Computer Summa gt CR Refresh F5 Y For a group For a specific object of class XIV Monitor Computer For all objects of another class Figure 7 110 SCOM Object Discovery settings 3 From the Override Properties window select the Override check box in the IntervalSeconds row and then use the cursor to select the Override Value check box You can now change the value in seconds from 600 to a different value Click OK to apply the change Selecting a shorter monitoring interval At first glance a monitoring interval of 10 minutes appears to be long If you decide to reduce the intervals you must decide which interval values to use Although a long monitoring interva
412. l might sound good additional monitoring increases the workload of both the monitored devices and of the SCOM server This situation might lead to unforeseen consequences One method you can use is to determine how quickly SCOM is able to complete a scan of your devices The default log folder for SCOM is C ProgramFiles IBM Storage Host IBMStorageSCOM 1og In that folder you see two files for each device type The XIV Storage System uses the following log files scom_xiv log This log file is updated when SCOM checks the state of each monitored XIV Storage System component scom_xiv_event log This log file is updated when SCOM collects new events from the XIV Storage System event logs Chapter 7 Monitoring 383 In Example 7 57 the event log for an XIV Storage System is examined in about 3 seconds In this example one new event is identified Example 7 57 The scom_xiv_event log 2013 09 24 13 37 38 INFO Enter collect 2013 09 24 13 37 39 INFO Connecting to 10 0 20 102 2013 09 24 13 37 40 INFO 1 IBM XIV Storage System is found device ID 10114 code level 11 4 0 esp4 p20130815 2013 09 24 13 37 41 INFO Enter get_xiv_events 2013 09 24 13 37 41 INFO Enter get_begin time _idx 2013 09 24 13 37 41 INFO Exit get begin time_idx 2013 09 24 13 37 41 INFO begin time 2013 09 24 13 26 37 begin idx 8971 2013 09 24 13 37 41 INFO event list after 2013 09 24 13 26 37 2013 09 24 13 37 41 INFO adding 1 new events to SCOM 2013 09
413. layed in the All Systems view See Figure 4 14 on page 114 You can add a maximum of 12 storage systems to a group and you can have a maximum of 12 groups Systems already configured in the GUI that are not part of a group can be added to a group by dragging and dropping them onto the wanted group Chapter 4 IBM XIV Storage Management software 113 To add a system to a group right click the Group and select Add System Figure 4 15 on page 115 In this case the Add Managed System dialog box is shown as in Figure 4 9 on page 111 Complete the dialog box as explained in 4 3 1 XIV Storage Management GUI used in direct mode on page 110 Figure 4 14 shows the XIV Group on the All Systems view xiv XIV Storage Management bo la File View Tools Hep A lt Add System EZ Add Group itso Gen3 78 023 Bee G3 XIV Fest 7820119 63 XIV MNO00 extrabam Volumes 628 116 ITSO_Group _ B Not Available Figure 4 14 XIV Group on All Systems view Tip With the XIV GUI V4 3 in direct mode you can manage up to 12 groups in the All Systems view A group can contain a maximum of 12 IBM XIV systems and any particular system can belong to only one group A single GUI instance can manage a maximum of 144 systems To manage more than 144 systems in direct mode multiple instances of the GUI can be started each with a different profile For detailed information see Direct mode GUI limitations for managing multiple systems
414. les with 12 disks per module Each single SAS disk is installed in a disk tray which connects the disk to the backplane and includes the disk indicators on the front If a disk is failing it can be replaced easily from the front of the rack The complete disk tray is one FRU which is latched in its position by a mechanical handle Chapter 3 IBM XIV architecture components and planning 77 Important IBM performs all disk replacements in an XIV Storage System SAS disks in the XIV Storage System must never be swapped within a module or placed in another module because of the internal tracing and logging data that they maintain In the XIV Gens disks are replaced according to the IBM standard maintenance strategy in deferred maintenance This means that IBM is alerted with the third failing disk in the system and arranges the replacement of all three failing disks in one repair action by the IBM service support representative SSR Optionally with extended maintenance each failing disk is replaced immediately after it was failed InfiniBand host channel adapter The InfiniBand host channel adapter HCA is a 2x dynamic device reconfiguration DDR host channel adapter that features 20 Gbps of internal bandwidth and has low latency The two ports are cabled to redundant InfiniBand switches inside the XIV Storage System Gen3 rack The InfiniBand HCA has the task of protocol processing which offloads this workload from the module s
415. lications first and make a layout strategy that meets the application needs Chapter 6 Performance 255 One of the most important considerations for the number of LUNs required for optimum performance in an XIV Storage System environment is application I O threads As a rule of thumb if the application must use multiple LUNs to allocate or create multiple threads to handle the I O then use multiple LUNs However most modern enterprise applications are sophisticated enough to define multiple I O threads independent of the number of LUNs or the number of LUNs has no effect on application threads In this case there is no compelling reason to have multiple LUNs Multiple LUNs might be needed to use queues on the host HBAs or I O buffers on the host operating system Another important consideration for the number of LUNs in an XIV Storage System environment has to do with parallelism of I Os across the XIV Storage System Interface Modules Using the multipathing design detailed in Figure 6 3 as an example consider one application server with one XIV Storage System LUN Host 1 D Host 2 gt oD Host 3 Q N gt S lt Host 4 co Host 5 Patch Panel FC Ports SAN Hosts Figure 6 3 Six paths per LUN is the best overall multipathing configuration This application server uses six paths in a round robin fashion to perform I O to this LUN Each XIV Storage System Interface Module is used one at a time to handl
416. ll create the program s shortcut in the following License Agreement menu Configure Installation IBM IV 4 3 Pre Installation Summary Installing Setup will create desktop icons for the following components F IBM XIV GUI IBM XIV Top 7 IBM XIV XCLI xiv lnstallAnywhere Cancel Previous Figure 4 5 Select Start Menu folder and desktop icons IBM XIV Storage System Architecture and Implementation 5 Figure 4 6 displays the setup configuration confirmation window Review your selections and click Install to complete the installation E EM XIV Storage Management GUI lol E a Pre Installation Summary Introduction Please review the following before continuing License Agreement Product Hame pea eee ene IBM XM Storage Management GUI Pre Installation Summary Install Folder talimot CAProgram Files IBM StorageiXIAXIVGUI Shorteut Folder E Users IBM_ADMIN AppData Roaming MicrosoffiWindows Sta Menu ProgramsiiBM XIV Storage Management GUI Disk Space Information ffor Installation Target Required 550 51 MegaBytes Available 3 522 989 MegaBytes lnstallAnvwhere Cancel Previous j Figure 4 6 Pre Installation Summary window 6 The final installation window is shown in Figure 4 7 Click Done to exit the installer E EM Iv Storage Management GUI i sc Introduction Introduction lnstallAncwhere will guide you through the installation of IBM xi Licen
417. locked to all write commands Even though write commands that overwrite existing data can be technically serviced they are blocked to ensure consistency To specify the lock_behavior parameter which is the behavior when capacity reserve has been depleted in a thin provisioned pool run the following command pool change config pool ITSO Pool lock _behavior no_io This command specifies whether the storage pool is locked for write or whether it disables both read and write when running out of storage space Lock The lock_behavior parameter can be specified for non thin provisioning pools but it has no effect 146 IBM XIV Storage System Architecture and Implementation 4 5 Volumes After defining storage pools the next logical step in system configuration is volume management The XIV Storage System offers logical volumes as the basic data storage element for allocating usable storage space to attached hosts This logical unit concept is known and is widely used by other storage subsystems and vendors However the volume segmentation and its distribution over the physical disks is not conventional in the XIV Storage System Traditionally logical volumes are defined within various Redundant Array of Independent Disks RAID arrays where their segmentation and distribution are manually specified The result is often a suboptimal distribution within and across modules expansion units and is dependent upon the administrators knowledge
418. lue to the description attribute or any other defined application admin LDAP role in the XIV We can now test with XCLI if that user can authenticate with the LDAP server and has the correct XIV role mapping as shown in Example 5 25 Example 5 25 Testing if an LDAP user has the correct XIV role mapping permission gt gt dap_test user itso password Passw0rd fqdn itso storage ibm com Command executed successfully If a user does not have a value or an incorrect value in the description attribute then an appropriate error is displayed as shown in Example 5 26 Example 5 26 Testing an LDAP user without correct XIV role mapping permission gt gt dap_test user PHB password n0ldea fqdn itso storage ibm com Error LOGIN FAILURE USER MISSING GROUP ATTRIBUTE Details User PHB is missing the group attribute description gt gt dap_test user Wally password K0ffee fqdn itso storage ibm com Error LOGIN FAILURE USER HAS NO RECOGNIZED ROLE Details User Wally has no recognized LDAP role Activating LDAP authentication After you can confirm LDAP users are tested successfully with the correct LDAP permissions you can enable LDAP authentication by changing the XIV Storage System LDAP mode using the 1dap_set_mode XCLI command as shown in Example 5 27 Example 5 27 Enabling LDAP in XIV Storage System gt gt dap_mode_set mode Active Warning ARE YOU SURE YOU WANT TO ENABLE LDAP AUTHENTICATION y n Command executed successfully
419. ly If the certificate type is PCKS12 p12 file extension enter values for the Name and Password for the certificate Chapter 5 Security 179 Click Import to complete the import of the signed certificate into the XIV Storage System The successfully imported certificate is shown in Figure 5 7 Certificates Management ri ap 7 Authenticated SX a Close Figure 5 7 Imported certificate Optionally repeat steps 1 6 for any additional IBM XIV systems that you want to secure with your own certificate Trusting the signed x509 certificate in the XIV GUI certificate When you have imported your own certificate into the XIV Storage System that system will present this certificate to the management tools GUI XCLI and so on that you use to connect to that system Because this is a new certificate the GUI reports a certificate error when connecting to that system as shown in Figure 5 8 XIV Galactica 1340009_ Figure 5 8 GUI certificate error 180 IBM XIV Storage System Architecture and Implementation Proceed to resolve the certificate error 1 To resolve this error you must configure the GUI to trust the new certificate To do so right click the system and choose Manage Certificate as shown in Figure 5 9 Modify IP Addresses Remove System Move System To Suspend Monitoring Manage Certificate Figure 5 9 Manage XIV Storage System certificate 2 The GUI display
420. m 9 MIV 02 1310114 gt Users Figure 5 61 Configure LDAP icon amp Add User Add User Group G Configure LDAP gt LDAP Wizard Configure LDAP 3 Inthe LDAP configuration menu that is shown in Figure 5 62 set the value of Use LDAP to Yes and choose the LDAP Server Type that you want to use In our example we selected Microsoft Active Directory Click the LDAP Servers tab to go to the next step LDAP General Use LDAP LDAP Server Type LDAP Servers Current Server IP User Credentials Role Mapping Secure LDAP Parameters Update Figure 5 62 LDAP configuration General Yes 3 Cancel Microsoft Active Directory 4 Inthe LDAP Servers window in the LDAP configuration click the green plus icon as shown in Figure 5 63 LDAP General LDAP Servers User Credentials Role Mapping Secure LDAP Parameters Update Figure 5 63 LDAP configuration Servers 220 Cancel IBM XIV Storage System Architecture and Implementation 5 In the window that opens enter the FQDN which is the DNS name of the LDAP server such as itso storage ibm com in our example Also enter the LDAP server IP address and the Search DN which in our Active Directory implementation is CN Users DC itso DC storage DC ibm DC com as shown in Figure 5 64 If your LDAP server uses nonstandard port numbers enter those accordingly Leave these fields blank to use
421. m IP 9 155 90 67 f USER HAS FAILED TO_RUN_C User cimmay from IP 9 155 90 67 f 9 20 13 12 54 PM _ USER_HAS FAILED TO _RUN_C User cimmy from IP 9 155 90 67 f 9 20 43 12 54 PM USER_HAS FAILED TO_RUN_C User cimmy from IP 9 155 90 67 f Figure 3 7 26 XIV Storage Management GUI Events main view 304 IBM XIV Storage System Architecture and Implementation The window is split into two sections gt The top part contains the management tools such as wizards in the menu bar anda series of input fields and drop down menus that act as selection filters gt The bottom part is a table displaying the events according to the selection criteria Use the table tile bar or headings to enable or change sort direction The system progressively loads the events into the table A progress indicator is visible at the lower right of the table as shown in Figure 7 27 User xiv_development from IP User technician from IP 9 155 179 User te 1943 out of 1943 Figure 7 27 Loading events into the table 7 1 7 Event attributes This section describes all the available event types event codes and their severity levels Severity levels You can select one of six possible severity levels as the minimal level to be displayed gt None Includes all severity levels gt Informational Changes such as volume deletion size changes or host multipathing gt Warning Volume usage limit
422. m flash to DRAM Else forwards the read request unmodified eck to SAS disk drives eee 4 Disk drives send data to DRAM Into a 512KB buffer page When bufer is filled up it is sequentially dest aged to the flash cache log structured Main Cache DRAM Ifhit serves data 4kread hit gra nul arity Serves data to host and writes 512KB buffers log structure d to flash cache Extended Cache Flash Sequential I O detection bypasses flash Sequential pre fetch routed directly to disk Sequential pre fetchis fast and thus no need to go thru flash cache Large block lt 64 KB reads are likely caused SAS Disks by sequential streaming tasks Figure 2 8 Cache learning The cache node immediately checks the extended cache for the requested I O If the requested I O exists in the extended flash cache it is served to the host through the main cache The I O operation is now complete and is recorded as a flash cache read hit If the operation results in a true read miss not in the DRAM cache and not in extended flash cache the request is forwarded in an unmodified state to the disk drive SAS layer The I O is retrieved from the disk drive and served to the host through the main cache From a host perspective the I O operation is now complete and is recorded as a read miss The related pages are copied into reserved buffers in the main cache Important Any read larger than 64 KB bypa
423. m view which is shown in Figure 4 16 on page 116 From this view the administrator can quickly access the status of the system Depending on the user permissions the interface might differ slightly Perspective The figures listed in this chapter depict the interface layout from a storage administrator perspective Not all options are available to the application administrator and read only permission levels Chapter 4 IBM XIV Storage Management software 115 Menu Bar Tool Bar System Info Menu User Indicator xv XIV Storage Management i eee Systems Actions View Tools Help te amp Gy Settings BMJ Launch xci fE Launch xiv Top All Systems 7 gt Tucson Lab 2 gt System v Hierarchical Navigation Function Icons amp Function Menus Volumes Volumes and Snapshots J M a i n K Snapshot Tree D j S p a y Consistency Groups i Snapshot Group Tree Current System s Indicator XIV 7370062 Dantooine 555 D E Status Bar amp Status Area Figure 4 16 Storage Manager main window System view The main window System view is divided into the areas noted in Figure 4 16 gt Function Icons and Function Menus On the left side of the main window in the System view a Set of vertically stacked icons is used to navigate between the functions of the XIV Storage Management GUI Move the cursor over an icon to preview the function menu for that icon A brief description of each of the fun
424. me When removing a volume from a storage pool the size of the storage pool does not decrease by the size of the volume gt The system defines capacity using decimal metrics 1 GB is 1 000 000 000 bytes using decimal metrics By contrast 1 GiB is 1 073 741 824 bytes using binary metrics The following principles apply to snapshots gt gt Snapshots are structured in the same manner as logical or master volumes Snapshot reserve The system preemptively deletes snapshots if the snapshots fully consume the allocated space of the storage pool Therefore you must ensure that adequate space is allocated for snapshot reserve when defining a storage pool The snapshot reserve must be a minimum of 34 GB Snapshots are automatically deleted only when there is inadequate physical capacity available within the context of each storage pool This process is managed by a snapshot deletion priority scheme Therefore when the capacity of a storage pool is exhausted only the snapshots that are in the affected storage pool are deleted in order of the deletion priority Chapter 2 IBM XIV Storage System logical architecture and concepts 33 Important Snapshot deletion occurs automatically and older snapshots will be deleted without warning whenever a new snapshot is taken and space is insufficient to hold new volume or snapshot data To control this behavior monitor the following events gt STORAGE_POOL_VOLUME_USAGE_INCREASED
425. ment User xiv_development Password Mode Direct Manager 1 9 155 59 232 Direct Licens ed Materials Property of IBM Corporation and otherfs Co Py ene 2008 2012 IBM an XIV are registered trader neg of IBM Corpora ation n in the Unie dS ather isuria ar both Figure 1 3 XIV GUI Demo mode 1 6 3 IBM Hyper Scale Manager GUI The IBM Hyper Scale Manager GUI acts as the management console for multiple XIV systems either in a Direct mode or in a Manager mode 1 6 4 XIV Storage Management online monitoring with XIV Top 12 The XIV Top application allows you to view and monitor performance information for defined volumes and hosts in real time See Figure 1 4 on page 13 for an illustration IBM XIV Storage System Architecture and Implementation XIV LAB 03 1300203 Volumes amp Hosts All Interfaces v Refresh every 4 seconds itso Storage Administrator Volume Name XIV_ORA_oravg_LPAR 1_npiv XIV_ORA_rootvg_LPAR_3 XIV_ORA_CRS1_VSCSI XIV_ORA_DAT_VSCSI_04 XIV_ORA_DAT_VSCSI_05 XIV_ORA_DAT_VSCSI_06 XIV_ORA_DAT_VSCSI_07 XIV_ORA_DAT_VSCSI_08 Slelcicic co alS IOPS Latency a BW MBps Host Name IOPS Latency mS BW MBps 0 735 0 808 0 341 p7 770 02_XIV_RAC_VIO1 XIV_RAC_LPAR2_NPIV p7 770 02_XIV_RAC_VIO2 p7 770 01_XIV_RAC_VIO3 0 694 p7 770 01_XIV_RAC_VIO4 1 342 ATS_zLinux_z9_MTS_mcelini2 0 0 WS_LPAR1 0 0 Performance Chart pai XIV_ORA_rootvg_LPAR_
426. mentioned previously snapshots in regular storage pools can be automatically deleted by the system to provide space for newer snapshots For thinly provisioned pools snapshots can be deleted to free more physical space for volumes Volume locking If more hard capacity is still required after all the snapshots in a thinly provisioned storage pool have been deleted all the volumes in the storage pool are locked preventing any additional consumption of hard capacity There are two possible behaviors for a locked volume read only the default behavior or no I O at all In either case your applications stop in a way that is not predictable Important Volume locking prevents writes to all volumes in the storage pool The thin provisioning implementation in the XIV Storage System manages space allocation within each storage pool so that hard capacity depletion in one storage pool never affects the hard capacity available to another storage pool There are both advantages and disadvantages gt Because storage pools are independent thin provisioning volume locking on one storage pool never cascades into another storage pool gt Hard capacity cannot be reused across storage pools even if a certain storage pool has free hard capacity available This limitation can lead to a situation where volumes are locked because of the depletion of hard capacity in one storage pool while there is available capacity in another storage pool It is still po
427. min readonly and specific one applicationadmin user_group_remove_user Removes a user from a user storageadmin group user_group_update Updates a user group storageadmin Adding users with the XCLI management workstation and a storageadmin user is required For more information about installing the XIV Management software including the XCLI see 4 2 XIV Storage Management software installation on page 106 The following examples assume a Windows management workstation To add users complete the following steps h Use the user_list command to obtain the list of predefined users and categories as shown in Example 5 1 on page 201 This example assumes that no users other than the default users have been added to the system 200 IBM XIV Storage System Architecture and Implementation Example 5 1 XCLI user_list gt gt user_ list Name Category Group Active Access All xXiv_development xiv_development yes Xiv_maintenance xiv_maintenance yes admin storageadmin yes technician technician yes espadmin storageadmin yes itso storageadmin yes lab admin applicationadmin Application0O1 Group yes see N If this system is a new system change the default password for the admin user by running update_user as shown in Example 5 2 Example 5 2 XCLI user_update gt gt user_update user admin password New PasswOrd password_verify New Passw0rd Command executed successfully Add a user as shown in Example 5 3
428. modules Total numberof interface modules Number of active irterfacemodules Interfacemodule9 state Interfacemodule8 state Interfacemodule7 state Interfacemodule6 state Interfacemoduled state Interfacemodule4 state FC ports iSCSI ports 1 Gops mod 114 iSCSI ports 1O0Gbos mad 214 Number of ds ks Usable capacity 1 2 3 4TB of CPUs oe perModule Vemary 24 GBpermodulew 1 23 TB Mema y 48 GB permodulew 4 TB Optional for 2 3 4TB XI Vs 400 GB SSD Cache Optional for 4TB XI Vs 0GB FlashCache Power kVA GerB 2 SSD 6 9 10 11 12 13 14 15 partial partial partial partial patial partid partial full 3 3 4 5 6 7 8 9 3 6 6 6 6 6 6 6 2 4 4 5 5 6 6 6 Dis led Dis abled Erabed Enabled Enabled Enabed Enabled Enabe d Enabled Enabled Enabdled Enabled Enabed Enabled Enabe d Enabled Enabled Enabled Enabled Enabed Enabled Dis abled Disabled Dis abled Ds abled Disaded Enabled Enabed Enabled Enabled Enabed Enabled Enabled Enabdled Enabled Enabed Enabled Enabled Enabed Enabled Enabled Enabled Enabled Enabed Enabled 8 16 16 2 20 24 24 24 6 14 14 18 18 22 2 22 4 8 8 10 10 12 12 12 72 10 120 12 144 156 168 18 2 TB 44TB 51 TB 561TB 63 TB 67 TB 75 B 81 TB 5 TB 88TB 102TB 111 TB 14 TB 14TB 149 TB 161TB amp TB 132 TB 154TB 168 TB 190 TB 206 TB 25 TB 243TB 112TB 177 TB 207TB 225 B 24 TB 272 TB 201 TB 25TB 6 9 10 11 12 13 14 15 144TB 216 TB A40TB 264 B 288 TB 312 TB 336 TB X 0TB 28TB 432 TB 480TB 8 TB 576 TB 64 TB 672 TB 720TB 2
429. mplete the following steps 1 Right click the Access icon and click Users as shown in Figure 5 47 Figure 5 47 Users 2 Click the LDAP Wizard icon on the toolbar as shown in Figure 5 48 Add User i Add User Group th Configure LDAP ai LDAP Wizard Export 4 ar Users OQ User 9 LDAP Wizard 2 32 PM Figure 5 48 LDAP Wizard icon The LDAP wizard opens the LDAP Configuration Welcome window Click Next to start the configuration In the Server Type tab as shown in Figure 5 49 on page 214 you can choose the Server Type from the corresponding drop down menu You can use either a Microsoft Active Directory or a Oracle Sun Directory server Chapter 5 Security 213 3 Click Next to choose Microsoft Active Directory as we did in this example LDAP Configuration Directory Services Type Directory Services Type Welcome Choose which Directory Services would you like to use for authentication Server Type LDAP Servers XIV User FA EREDA Unique ID s Server Type O TRA T Microsoft Active Directory Groups Sun Directory Secure LDAP Bind amp Cache Test amp Activation Finish lt iw Figure 5 49 Server Type tab 4 From the LDAP Servers tab click the plus sign icon at the right to add an LDAP server to the configuration as shown in Figure 5 50 LDAP Configuration Directory Services Server Configuration Directory Service
430. mputer Trusted Root Certification Authorities Certific jim E3 E Fil Action View Favorites Window Help Certificates Local Computer ESJ4B4 ECOM Root CA ABA ECOM Root CA _ Personal J Autoridad Certificadora de la Asoc Autoridad Certificadora de la Asoc Autoridad Certificadora del Colegi Autoridad Certificadora del Colegii Baltimore EZ by DST Baltimore EZ by DST enterprise TEES eer as Belgacom E Trust Primary CA Belgacom E Trust Primary C4 p Take rine sists Teruna mA aies E caw HET SecureNet CA Class 4 C amp W HET SecureNet CA Class A a EE CAW HET SecureNet CA ClassB CAW HKT SecureNet CA Class B Es caw HET SecureNet c Root C amp M HET SecureWet CA Root Third Party Root Certification Authorities Trusted People cew HET SecureNet CA SGC Root C amp W HKT SecureNet CA SGC Root Other People Certisign Autoridade Certificadora ACZ fisign Autoridade Certificador Certificate Enrollment Requests f certisign Autoridade Certificador Certisign Autoridade Certificador Spc E Certisign Autoridade Certificadora Certisign Autoridade Certificadora E certisign Autoridade Certificadora Certisign Autoridade Certificadora class 1 Primary CA Class 1 Primary CA class 1 Public Primary Certification Class 1 Public Primary Certification class 1 Public Primary Certification Class 1 Public Primary Certification E class 2 Primary CA Class 2 Primary CA T Oleee 9 Mohli Meina sen mekik mkin Oleee 9 mohhi Meine mea eki Fi mnk
431. must allocate new 17GB increments to possible for the volumes in the pool to collectively exhaust all hard space the volume as space is consumed allocated to the pool This will cause the pool to be locked Figure A 3 Volumes and snapshot reserve space within a thinly provisioned storage pool 398 IBM XIV Storage System Architecture and Implementation Consider Volume 3 in Figure A 3 on page 398 The size of the volume is defined as 34 GB However less than 17 GB has been consumed by host writes so only 17 GB of hard capacity have been allocated by the system In comparison Volume 4 is defined as 51 GB but Volume 4 has consumed 17 34 GB of hard capacity and therefore has been allocated 34 GB of hard space by the system It is possible for either of these two volumes to require up to an additional 17 GB of hard capacity to become fully provisioned Therefore at least 34 GB of additional hard capacity must be allocated to this pool in anticipation of this requirement Finally consider the 34 GB of snapshot reserve space shown in Figure A 3 on page 398 If a new volume is defined in the unused 17 GB of soft space in the pool or if either Volume 3 or Volume 4 requires additional capacity the system sacrifices the snapshot reserve space to give priority to the volume requirements Normally this scenario does not occur because additional hard space must be allocated to the storage pool as the hard capacity usage crosses certain
432. must be rebuilt if necessary and redistributed to the new pseudo random distribution Either way the XIV Storage System data redundancy mechanisms must accommodate the change These redundancy mechanisms are sometimes referred to as autonomic because these procedures are self managing They happen without any storage administrator intervention When a disk drive or a module is replaced during normal maintenance or additional data storage capacity is added to an existing XIV System configuration the XIV System moves existing primary and secondary data partitions to the new hardware This process occurs in such a way that results in an even distribution of partitions across all disk drives and modules At no time during this process does the XIV System become non redundant This distribution process consists of the following activities gt Creates a target data distribution gt Begins to redistribute the redundant data according to the new target data distribution This process is known as redistributing Redistribution is further described in Redistribution after adding modules or drives on page 53 When the full redundancy of data is compromised because of a disk drive or module failure the XIV Storage System immediately identifies the non redundant partitions and begins the rebuild process The rebuild process is similar to the redistribution process and consists of the following activities gt Creates a target data distributi
433. must provide the required completed information sheet that is referenced in 3 2 1 Basic configuration planning on page 87 98 IBM XIV Storage System Architecture and Implementation The basic configuration steps are as follows Set the Management IP addresses client network gateway and netmask Set the system name Set the email sender address and SMTP server address Set the primary DNS and the secondary DNS Set the SNMP management server address Set the time zone Set the NTP server address Configure the system to send events to IBM call home Configure and test remote support OONOORWD Completing the physical installation After the IBM SSR completes the physical installation and initial setup the IBM SSR performs the final checks for the XIV Storage System 1 Power off and power on the machine using the XIV Storage Management GUI or XCLI 2 Check the Events log carefully for problems 3 Verify that all settings are correct and persistent The installation is complete and the XIV Storage System is ready to be handed over to the client to configure and use See Chapter 4 IBM XIV Storage Management software on page 103 for more information about that topic 3 2 5 System power on and power off Strictly follow these procedures to power on and power off your XIV Storage System Power on To power on the system complete these steps 1 On each UPS look for the Test button on the
434. n Center at this location http publib boulder ibm com infocenter ibmxiv r2 index jsp Volumes can also be grouped into larger sets called consistency groups and storage pools See 2 3 4 Storage pool concepts on page 31 Chapter 4 IBM XIV Storage Management software 147 Important As shown in Figure 4 52 the basic hierarchy of the logical storage concepts of an XIV Storage System is as follows gt gt gt gt A volume can have multiple snapshots A volume can be part of one and only one consistency group A volume and its corresponding snapshots are always part of only one storage pool All volumes of a consistency group must belong to the same storage pool Storage Pool Consistency Group TestVol Snapshots from CG Figure 4 52 Basic storage hierarchy 4 5 1 Managing volumes with the XIV Storage Management GUI To start a volume management function from the XIV Storage Management GUI you can either click View gt Volumes Volumes and Snapshots from the menu bar or mouse over the Volumes icon and then select the appropriate menu item See Figure 4 53 Consistency Groups i i Snapshot Group Tree Figure 4 53 Opening the Volumes menu 148 IBM XIV Storage System Architecture and Implementation The Volumes and Snapshots menu item is used to list all the volumes and snapshots that have been defined in this particular XIV Storage System An example of the resulti
435. n and deployment can be more effectively deferred until actual application and business needs demand additional space in effect facilitating an on demand infrastructure Logical and actual volume sizes The physical capacity that is assigned to traditional volumes is equivalent to the logical capacity presented to hosts This situation does not have to be the case with the XIV Storage System thin provisioning For a given XIV Storage System logical volume there are effectively two associated sizes the logical volume size and the actual volume size The physical capacity allocated for the volume is not static but it increases as host writes fill the volume Logical volume size The logical volume size is the size of the logical volume that is observed by the host as defined upon volume creation or as a result of a resizing command The storage administrator specifies the volume size in the same manner regardless of whether the volume s storage pool is a thin pool or a regular pool 34 IBM XIV Storage System Architecture and Implementation The volume size is specified in one of two ways depending on units gt Interms of gigabytes The system allocates the soft volume size as the minimum number of discrete 17 GB increments needed to meet the requested volume size gt In terms of blocks The capacity is indicated as a discrete number of 512 byte blocks The system allocates the soft volume size consumed within the storage pool as the min
436. n is performed in respect to the total system net capacity All reductions and increases are reflected in the remaining free storage capacity Storage pool size gt When increasing a storage pool size you must ensure that the total system capacity holds enough free space to enable the increase in storage pool size gt When decreasing a storage pool size you must ensure that the storage pool itself holds enough free capacity to enable a reduction in size This operation is also used to shrink or increase the snapshot capacity inside the storage pool This alteration affects only the space within the storage pool In other words increasing snapshot size consumes the free capacity only from the corresponding pool To change the size of one storage pool in the system right click a pool in the Storage Pools view Figure 4 43 on page 137 and select Resize The window shown in Figure 4 46 opens Change the pool hard size soft size or the snapshot size to match your new requirements Within the storage pool gauge the vertical dotted line to the left with the blue triangles is the consumed capacity and the vertical dotted line to the right with the white circles is the snapshot size Resize Pool ITSO XIV PFE GEN3 1310133 a SS Regular Pool s Thin Pool 4 Pool Size 37 892 GB H 0 I I nr er System Allocated l T Pools 4 l 5 Free 72 6 454 GB New Size 378
437. n page 75 gt Redundant power supplies gt Enclosure management card 74 IBM XIV Storage System Architecture and Implementation Figure 3 15 shows the rear of the Data Module with its ports and connectors XIV Gen3 Data Module Memory Flash Card SSD Slot pi 9 ue e n an i a a a W noa oe 5 e Dasta tn at WE meses Sesese OG dD a eee Shek en ee meee ene 9 a ese j menene fee ETATETATATE TES a p da dainai Management Independent Power USB RS 232 Serial Supply modules 2 x GigE NIC InfiniBand Ports Figure 3 15 XIV Storage System Gen3 Data Module connections that are used Model 114 unique components Data Modules and Interface Modules in the Model 114 have the following specific components Quad core processor The XIV Storage System Gen3 Model 114 processor is a third generation Intel Nehalem micro architecture Westmere 32 nm processor with a 2 4 GHz clock speed There is one processor per module This processor features turboboost and hyperthreading and is more energy efficient than its predecessors This processor is specifically sized to handle the I O workload required in the XIV Storage System Gen3 modules DDR3 memory model 114 XIV Storage System Gen3 has faster DDR3 memory that is twice the speed of its DDR2 predecessor Each XIV Storage System Gens has 24 GB which is 8 GB of more mem
438. n the affected storage pool are deleted Size of storage pools The size of storage pools and the associations between volumes and storage pools are constrained by the following circumstances gt The size of a storage pool can range from 17 GB up to 325 TB on XIV Storage System Gen3 systems equipped with 4 TB disks Tip To determine the maximum pool size use the system_capacity_list command Look at the column titled Max Pool Size gt The size of a storage pool can always be decreased limited only by the space already consumed by the volumes and snapshots in that storage pool gt Volumes can be moved between storage pools without any limitations if they are not part of a consistency group and there is enough free space in the target storage pool Volumes that are part of a consistency group can be moved together as a group Important All of these operations are handled by the system at the metadata level and they do not cause any data movement copying from one disk drive to another They are completed almost instantly and can be done at any time without affecting the applications Thin provisioned pools Thin provisioning is the practice of allocating storage on a just in time and as needed basis by defining a logical or soft capacity that is larger than the physical or hard capacity Thin provisioning enables XIV Storage System administrators to manage capacity based on the total soace consumed rather than jus
439. napshots view Volumes are listed in a tabular format If the volume has snapshots then a or a icon displays on the left Snapshots are listed under their master volumes and the list can be expanded or collapsed at the volume level by clicking the or icon Snapshots are listed as a subbranch of the volume of which they are a replica and their row is indented and slightly shaded The Master column of a snapshot shows the name of the volume of which it is a replica If this column is empty the volume is the master Tip To customize the columns in the lists right click one of the column headings and make the required selection of attributes The default column set does not contain the Master column You can also resize the columns to allow for longer names or to make more columns visible Table 4 1 details the available columns of the Volumes and Snapshots view Table 4 1 Columns in the Volumes and Snapshots view System Name of the XIV Storage System to which this volume or snapshot belongs Size GB Volume or snapshot size The value is zero if Y the volume is specified in blocks Used GB Used capacity in a volume Chapter 4 IBM XIV Storage Management software 149 150 Size Blocks Volume size in blocks Size Disk Volume size in GB Used Capacity MiB Consumed capacity in binary mebibytes Y 2 bytes Master Snapshot master s name Consistency Group Consistency group name Storage pool name
440. nce this situation As mentioned earlier there are reasons why LVM striping has performance benefits from a host perspective An interesting example is with certain applications that are better able to use the performance capabilities of the host operating system by using LVM striping These efficiencies are realized on the host kernel buffer utilizations This application was fully tested without LVM striping and with LVM striping using different stripe sizes The net result was a 25 overall performance improvement using host LVM striping Operating system tunables It is common to experience significant performance improvements by tuning the I O characteristics of the operating system Most of these characteristics are kernel I O buffers memory buffers or file system tunables The specifics for each operating system are complex and outside the scope of this book This activity is a common one that cannot be overlooked during migration planning You can find more information about this topic in X V Storage System Host Attachment and Interoperability SG24 7904 6 2 5 Quality of service We previously introduced the quality of service QoS feature QoS allows the XIV Storage System to deliver multiple service levels to hosts connected to the same system The QoS feature is intended to enhance performance of critical business applications that run concurrently with noncritical applications As the XIV Storage System disk and cache are shared
441. nd type the command gt For command completion type part of a command and press Tab to see possible valid commands gt Forcommand argument completion type a command and press Tab to see a list of values for the command argument Figure 4 41 shows an example of an XCLI Session gt gt user_ lt TAB gt user_define user_delete user_group add _ user user_group create user_group delete user_group list user_group remove user user_group rename user_group update user_list user_rename user_update gt gt user_list lt TAB gt Show_users user gt gt user_list user lt TAB gt xiv_development xiv_maintenance admin technician ITSO gt gt user_list user admin Name Category Group Active Email Address Area Code Phone Number Access All admin storageadmin yes Figure 4 41 XCLI Session example Customizing the XCLI environment For convenience and more efficiency in using the XCLI use the XCLI Session environment and start XCLI Session from the XIV Storage Management GUI menu However if you want to write scripts to run XCLI commands it is possible to customize your management workstation environment As part of the XIV Storage System high availability features each system is assigned three IP addresses When running a command the XCLI utility is provided with these three IP addresses and tries each of them sequentially until communication with one of the IP addresses is successful You must pass at least one of the IP
442. nd rules Storage pools facilitate the administration of relationships among logical volumes snapshots and consistency groups Storage pools have the following size considerations gt Fora fully populated XIV Storage System equipped with 1 TB 2 TB 3 TB or 4 TB drives the storage pool size can range from 17 GB the minimum size that can be assigned to a logical volume to 80 TB with 1 TB disk drives 161 TB with 2 TB disk drives 243 TB with 3 TB disk drives or 325 TB with 4 TB disk drives gt For partially populated XIV Storage System configurations the maximum hard storage pool size is always equal to the maximum usable capacity of the configuration or 80 TB with 1 TB disk drives 161 TB with 2 TB disk drives 243 TB with 3 TB disk drives or 325 TB with 4 TB disk drives whichever is less gt Snapshot reserve capacity is defined within each storage pool and is effectively maintained separately from logical or master volume capacity The same principles apply for thinly provisioned storage pools with the exception that space is not guaranteed to be available for snapshots because of the potential for hard space depletion 32 IBM XIV Storage System Architecture and Implementation The following principles govern the relationships between logical entities within the storage pool gt An XIV Storage System LUN or logical volume can have multiple independent snapshots This logical volume is also known as a mas
443. nd switches Each InfiniBand switch contains 36 ports that have 40 Gbps full bidirectional bandwidth per port Port to port latency is less than 100 nano seconds Each switch has 2 88 Tbps switching throughput The switches are powered by redundant power supplies and fan modules to eliminate any single point of failure Additionally each switch has several RJ 45 management ports that are used by the XIV Storage System InfiniBand is also scalable well beyond the current 15 modules in a single XIV Storage System rack 84 IBM XIV Storage System Architecture and Implementation 3 1 10 Patch panel The patch panel is at the rear of the rack The Fibre Channel ports on the Interface Modules are connected to the patch panel using 50 micron cables All external connections must be made through the patch panel In addition to the host connections and to the network connections more ports are available on the patch panel for service connections Figure 3 24 shows the details for the patch panel and the ports The patch panel has had various redesigns of the labeling based on the production date Patch panel Patch panel 1 GbE 10 bE Lal Fibre Chanel connections a RCE connections Maintennce Console connections o Mana gement connections GUI or CLI ARSC connections Remote Support Tn Service Ports a IBM SSRICE e eee Modem fi Figure 3 24 Connection details of patch panel ports Chapter 3 IBM XIV arch
444. ndicator Indicates the currently selected systems or group gt Status Bar and Status Area These indicators are at the bottom of the main window of the System view This area indicates the overall operational status of the currently selected IBM XIV Storage System or group of systems The values displayed are in the context of the current systems The leftmost indicator shows the amount of soft or hard storage capacity currently allocated to the storage pools and provides alerts when certain capacity thresholds are reached Click the indicator to toggle between soft and hard values As the physical or hard capacity consumed by volumes with the storage pool passes thresholds the color of this meter indicates that extra hard capacity might need to be added to one or more storage pools The center indicator displays in real time the number of I O operations per second IOPS The rightmost indictor shows the general system status and various operational states of the XIV Storage System An alerts icon might be displayed that if selected shows alerts and corresponding events For more information see 7 1 Monitoring with XIV Storage Management GUI and XCLI on page 286 Chapter 4 IBM XIV Storage Management software 117 Figure 4 17 shows the XIV Storage Management software menu items XIV Storage Manager Menu icons Systems Volumes View all managed Create delete and edit systems alerts storage volumes their and
445. ne America Phoenix Parameters NTP Server SNMP DNS Primary DNS Secondary Misc l Use IPv6 Yes Mo Volume Default 55D Caching ja Figure 5 11 Enable IPv6 In the drop down box for Use IPv6 select Yes and click Update 5 3 2 Configuring IPv6 addresses In the main window click the Backview arrow next to the XIV System Storage image in the main window as shown in Figure 5 12 This opens the view of the system ports Backview Figure 5 12 GUI Backview arrow 182 IBM XIV Storage System Architecture and Implementation Configuring management port IPv6 addresses To configure IPv6 addresses on a management port right click that port and select Update Management IP Interface as shown in Figure 5 13 Figure 5 13 Update Management IP Interface Enter the corresponding three IPv6 addresses in the fields shown in Figure 5 14 and click Update Update IP Interface Management IPv4 Address 1 IPv4 Address 2 IPv4 Address 3 IPv6 Address 1 i IPv6 Address 2 is IPv6 Address 3 x Netmask Default Gateway MTU eee Figure 5 14 Update management port IPv6 addresses Configuring VPN port IPv6 addresses 9 11 209 187 9 11 209 188 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 255 255 254 0 9 11 2081 1500 Cancel To configure IPv6 addresses on a VPN port right click that port and select Update VPN IP Interface as shown in Figur
446. ned XIV Storage System users Only the LDAP user with the appropriate group role has access to the system You will also be logged out from the XIV Storage Management GUI gt All local users and passwords will be reactivated again after you have disabled the LDAP mode and return to the native mode This situation means that the users are deactivated and not deleted 18 Check the summary and click Finish You might be asked if you are sure that you want to enable LDAP now because it will log you off the system afterward See Figure 5 58 LDAP Mode Modification Are you sure you want to modify LDAP mode and logout from the current system Figure 5 58 Activation confirmation Click OK 19 When you get a confirmation that LDAP was tested and configured as shown in Figure 5 59 click OK again to close the window Wizard LDAP Configuration LDAP was tested and configured successfully OK Figure 5 59 End of LDAP configuration 5 7 2 Using the XIV Storage Management GUI directly to configure LDAP Configuring LDAP in an XIV Storage System can also be done directly through the XIV Storage Management GUI rather than using the LDAP wizard Complete the following steps 1 Hover the cursor over the Access icon and click Users as shown in Figure 5 60 on page 220 Chapter 5 Security 219 Figure 5 60 Users tab 2 Click the Configure LDAP icon on the toolbar as shown in Figure 5 61
447. ned pool can be dynamically changed by the storage administrator gt When a regular pool needs to be converted to a thinly provisioned pool the soft pool size parameter must be explicitly set in addition to the hard pool size which remains unchanged unless updated gt When a thinly provisioned pool must be converted to a regular pool the soft pool size is automatically reduced to match the current hard pool size If the combined allocation of soft capacity for existing volumes in the pool exceeds the pool hard size the storage pool cannot be converted This situation can be resolved if individual volumes are selectively resized or deleted or moved to another storage pool to reduce the soft space consumed System level thin provisioning The definitions of hard size and soft size apply at the subsystem level because it is necessary to allow the full system to be defined in terms of thin provisioning to achieve the full potential benefit previously described The ability to defer deployment of additional capacity on an as needed basis The XIV Storage System architecture allows you to define a global system capacity in terms of both a hard system size and a soft system size When thin provisioning is not activated at the system level these two sizes are equal to the system s physical capacity IBM XIV Storage System Architecture and Implementation Hard system size The hard system size represents the physical disk capacity that is a
448. nents and planning 87 Enter all the required information into each worksheet to prevent further inquiry and delays during the installation see 3 2 4 IBM XIV Storage System physical installation on page 98 gt Interface Module Interface Modules 4 5 and 6 need an IP address netmask and gateway This address is necessary to manage and monitor the XIV Storage System using either the XIV Storage Management GUI or XCLI Each Interface Module needs a separate IP address in case a module is failing gt Domain Name Server lf Domain Name System DNS is used in your environment the XIV Storage System must have the IP address netmask and gateway from the primary DNS server and if available also from the secondary server gt Simple Mail Transfer Protocol gateway The Simple Mail Transfer Protocol SMTP gateway is needed for event notification through email The XIV Storage System can initiate an email notification which is sent out through the configured SMTP gateway IP address or server name netmask and gateway gt Network Time Protocol time server XIV Storage System can be used with a Network Time Protocol NTP time server to synchronize the system time with other systems To use this time server the IP address or server name netmask and gateway must be configured It is a best practice to enter the information for an NTP server gt Time zone Usually the time zone depends on the location where
449. nfigured XIV Storage System Gens which is 1044 5 kg 2302 Ib For racks with less than 15 modules subtract 28 6 kg 63 Ib for each module less than 15 to get the approximate weight requirement for your rack 68 IBM XIV Storage System Architecture and Implementation gt Adequate cooling is required for the XIV Storage System Gen configuration ordered Enough clearance around the system must be left for cooling and service The thermal dissipation of a fully configured XIV Storage System Gen3 Model 114 with 2 TB drives is 22 7 kBTU hour and 24 kBTU hour with 3 TB drives The thermal dissipation of a fully configured XIV Storage System Gen3 Model 214 with 2 TB drives is 19 KBTU hour 20 1 kBTU hour with 3 TB drives and 20 5 kBTU hour with 4 TB drives Airflow is from front to back gt Building features such as any ramps elevators and floor characteristics must also be considered The following measurements in Figure 3 7 are provided for your convenience 120 cm 47 2 in 120 cm 47 2 in 120 cm 47 2 in re Adjacent rack l 195 n maximum 86 cm oe pe 33 9 in 66 cm 26 0 in ny l Be ay POOO 10 cm 3 9 in Adjacent rack i a ce a te a ec a eee xivi0178 Figure 3 7 Rack clearances Model 114 3 1 6 Power components This section describes power components and their redundancy Power redundancy To prevent the complete rack or single
450. ng window is shown in Figure 4 54 mame Size GB Used GBY Consistency Pook Th Created lll Sn demo1_07 65 GB Disabled Default demo1_06 65 GB Disabled Default demo1_05 65 GB Disabled Default demo1_04 65 GB Disabled Default demo1_03 65 GB Disabled Default demo1_02 85 GB 0GB Disabled Default demo1_01 85 GB 0GB Disabled Default AV_RedBk_DB_10 1015 GB 1015 GB ITSO Disabled Default AV_RedBk_DB_09 1015 GB 1015 GB ITSO Disabled Default AV_RedBk_DB_08 1015 GB 1015 GB ITSO Disabled Default AV_RedBk_DB_07 1015 GB 1015 GB ITSO Disabled Default AV_RedBk_DB_06 1015 GB 1015 GB ITSO Disabled Default AV_RedBk_DB_05 1015 GB 1015 GB ITSO Disabled Default AV_RedBk_DB_04 1015 GB 1015 GB ITSO Disabled Default AV_RedBk_DB_03 1015 GB 1015 GB ITSO Disabled Default AV_RedBk_DB_02 1015 GB 1015 GB ITSO Disabled Default AV_RedBk_DB_01 1015 GB 1015 GB ITSO Disabled Default 17GB_600 17 GB 0GB test_pool Disabled Default 17GB_599 17 GB 0GB test_pool Disabled Default 17GB_598 17 GB 0 GB test_pool Enabled Manually Set 17GB_597 17 GB 0GB test_pool Disabled Default 17GB_596 17 GB 0GB test_pool Disabled Default 17GB_595 17 GB 0GB test_pool Disabled Default 17GB_594 17 GB 0GB test_pool Disabled Default 17GB_593 17 GB 0GB test_pool Disabled Default 17GB_592 17 GB 0GB test_pool Disabled Default edd oll oil cdl cll AL AMA ofl oA oA cA ofl oA oll ofl oA ofl ofl oA oA oA oA oA oA ol a Figure 4 54 Volumes and S
451. nly called collectively the distinguished name DN The acceptable format for the subject field is a string of attribute value pairs each preceded by a slash Spaces are not permitted In our example we use the value CN xivhost 0 itso L Tucson ST AZ C US Chapter 5 Security 175 Choose a value for the encryption strength in the Bits field In our example we choose 2048 bit encryption Tip The subject field in an x509 certificate uniquely identifies the host that the certificate belongs to It is recommended that at a minimum the following field attributes be included in the subject or your certificate request gt CN common name O organization L locality ST state C country YY vV y Check with your CA vendor or CA server administrator to determine whether they require any additional attributes in the subject of your certificate request 3 Click Generate to generate the CSR file A file browser window opens as shown in Figure 5 3 prompting you to save the CSR file to your local workstation Choose the appropriate location and save the CSR file You provide this file to your CA to produce a signed certificate Save CSR Savein ITSO amp F Name Date modified elie Ey Recent Places Desktop fad m No items match your search i Libraries LS Computer a Network a File name itsoCertificate cer Save as type All Files Figure 5 3 Save the CSR file 17
452. non thinly provisioned system as regular storage pools gt The soft system size is a purely logical limit However you must exercise care when the soft system size is set to a value greater than the maximum potential hard system size It must be possible to upgrade the system s hard size to be equal to the soft size Therefore defining an unreasonably high system soft size can result in full capacity depletion It is for this reason that defining the soft system size is not within the scope of the storage administrator role gt If it is necessary to increase the soft system size beyond the maximum hard system size for a particular XIV Storage System model there is a procedure that IBM performs that can accomplish this task Contact your IBM Technical Advisor or IBM sales team for more details There are conditions that might temporarily reduce the system s soft limit For more details see 2 7 2 Preserving data redundancy Rebuilding and redistributing on page 48 Depletion of hard capacity Using thin provisioning creates the inherent danger of exhausting the available physical capacity If the soft system size exceeds the hard system size the potential exists for applications to fully deplete the available physical capacity Important Upgrading the system beyond the full 15 modules in a single frame is currently not supported Chapter 2 IBM XIV Storage System logical architecture and concepts 39 Snapshot deletion As
453. ns or XIVADMINS are recognized as equal strings To simplify XIV Storage System administration however treat both the XIV Storage System configuration parameter and LDAP attribute value as though they were case sensitive and assign the XIVAdmins value to both The XIVAdmins and XIVReadonly names are used because both strings can be easily associated with their corresponding XIV Storage System roles storageadmin and readonly It is not necessary to use the same names in your XIV Storage System configuration Chapter 5 Security 209 However if you were to change these parameters consider using names that are self descriptive and easy to remember to simplify the LDAP server administration tasks Every time the LDAP server administrator creates a new XIV System Storage account one of the names must be entered as a description attribute value except for the applicationadmin role as we explain in LDAP role mapping for the applicationadmin role on page 211 After being configured in both XIV and LDAP changing these parameters although possible can potentially be time consuming because each existing LDAP account must be changed individually to reflect the new attribute value The configuration tasks can also be done from the XIV Storage Management GUI On the main XIV Storage Management window click Systems gt System Settings select the LDAP option and select the Role Mapping tab Enter the following variables as shown in Figure
454. nse time When it comes to XIV Storage System performance analysis there are a few questions gt Is XIV providing the bandwidth or IOPS required by the application gt Is XIV providing adequate read and write response times Because the XIV Storage System can have different configurations depending on the number of modules each of these configurations has different performance capabilities For a given production workload the different XIV Storage System configurations provide different performance characteristics As the application performance demands increase two things happen to the XIV Storage System performance characteristics 1 The XIV Storage System provides more OPS throughput MBps until it has reached its maximum performance capacity 2 The XIV Storage System response time latency would tend to increase especially as the XIV configuration approaches its maximum performance capacity Figure 6 32 is an example of a typical IOPS versus response time curve It is based on theoretical I O workload characteristics Typical I O characteristics include the following gt IOPS I O size for both reads and writes Cache hits for both reads and writes Percentage of reads versus writes Percentage of both reads and writes that are sequential YY vV y Example IOPS vs Response Time Curve Latencyin ms uw 98 OD O LC QO AL AL OQ LO OL OL LO OQ OL OL AL AL OL OQ OL AL ML OL OQ OC OQ AL LC OC OC PL OL aS
455. nt IP address Security LI Figure 7 71 Select System Discovery 2 Inthe System Discovery window that is shown in Figure 7 72 follow these steps to discover IBM XIV systems a Select Range of IPv4 addresses b Next enter the address range for the IBM XIV systems in your environment Also set the Auto discover period and the Presence Check period c Click Discover Now IBM systems Director Welcome Administratea Wiew all tasks zj TES ree lt a Home Find a Task Find a Resource System Discovery Resource Explorer Welcome Use system discovery to discover manageable a My Startup Pages host name discover resources of the same type discoveries including importing IP addresses an Automation 7 Learn more about using discovery El Inventory System Discovery en View and Collect Inventory Range of Pwd addresses Release Management Starting IP address i es ee liis Security Ending IP address is ee eae System Configuration System Status and Health Select the resource type to discover ale All Remote Access k Hl Task Management Settings Discover How Figure 7 72 Enter IP addresses range Chapter 7 Monitoring 351 352 3 The IBM Systems Director now discovers the IBM XIV systems in the specified range and adds them to the inventory as displayed in Figure 7 73 Discovered Manageable Systems Actions Y Name Discovere
456. nt Information Base file After you have completed the installation of your IBM Director environment you can prepare it to manage the XIV Storage System by compiling the provided Management Information Base MIB file 342 IBM XIV Storage System Architecture and Implementation Ensure that you always use the latest MIB file provided To compile the MIB file in your environment complete the following steps 1 At the IBM Director Console window click Tasks SNMP Browser Manage MIBs as shown in Figure 7 59 T IBM Director Console Console ies 9 Associations View Options Window Help 7 O Oh a __ Asset ID f CIM Browser 4 Configure Alert Standard Format cates TCPVIP Addresses ga Configure SNMP Agent 0 Se Event Action Plans 9 155 56 101 gt Event Log 9 155 56 100 ES External Application Launch 9 155 56 102 9 155 56 102 4 File Transfer Hardware Status Esa Microsoft Cluster Browser Network Configuration ae Process Management aa Remote Control H Remote session Resource Monitors ay Scheduler E Sewer Configuration Manager A SNMP Browser a Sotware Distribution Fa System Accounts tal Active Console Viewer E Message Browser Manage MIBs El SNMP Browser xI 10 0 MMOOOS0 i Help for SNMP Browser M all Managed Ol TCPIIP iv lab 04 iv lab 04 iv lab 04 iv lab 04 Figure 7 59 Manage MIBs 2 Inthe MIB Management window click File gt S
457. nt of an IBM XIV Storage System This chapter covers the following topics gt IBM XIV Storage System Gens gt Hardware planning overview 57 3 1 IBM XIV Storage System Gen3 The XIV Storage System Gen3 Model 214 shares all of the concepts and software architecture of its predecessor Model 114 Compared to the Model 114 the Model 214 consists of hardware upgrades that deliver significant performance improvements The primary hardware component upgrades are in the following areas gt Interface and Data Modules Processor Memory Power Supply Unit 1TB 27B 3TB and 4 TB serial attached SCSI SAS self encrypting drives SEDs 400 GB flash drive cache option or 800 GB flash drive with 4 TB configurations gt Interface Modules Two port 10 GbE adapter The XIV Storage System Gen3 shown in Figure 3 1 is a scalable enterprise storage system based on a grid array of hardware components The architecture offers the highest performance through maximized and balanced utilization of all disks a true distributed cache implementation and exceptional performance characteristics It also offers superior reliability through its distributed architecture redundant components self monitoring and self healing attributes Figure 3 1 IBM XIV Storage System Gen3 Front and rear views 1 The 1 TB drives are actually stripped down 2 TB drives 58 IBM XIV Storage System Architecture and Implementation The XIV Storage
458. ntation precludes the usage of traditional RAID algorithms in the architecture As described in Partitions on page 27 the XIV Storage System architecture divides logical volumes into 1 MB partitions This granularity and the mapping strategy are integral elements of the logical design that enable the system to realize the following features and benefits gt Partitions that make up a volume are distributed on all disks using a pseudo random distribution function which is described in 2 2 2 Software parallelism on page 23 The distribution algorithms seek to preserve the equality of access among all physical disks under all conceivable conditions and volume access patterns Essentially although not truly random in nature the distribution algorithms in combination with the system architecture preclude the occurrence of hotspots e A fully configured XIV Storage System contains 180 disks and each volume is allocated across at least 17 GB decimal of capacity that is distributed evenly across all disks e Each logically adjacent partition on a volume is distributed across a separate disk Partitions are not combined into groups before they are spread across the disks e The pseudo random distribution ensures that logically adjacent partitions are never striped sequentially across physically adjacent disks For a further overview of the partition mapping topology see 2 2 2 Software parallelism on page 23 Each di
459. nter operations manager aspx To install the IBM Storage Management Pack for SCOM complete the following steps 1 Download the relevant IBM Management Pack to the SCOM server x86 or x64 After it is downloaded double click IBM_Storage_MP_for_SCOM windows to start the installation 2 If the IBM Storage Solutions External Runtime Components are not installed you are prompted to install them This package installs a version of Python called xPYV which is used by the IBM Storage Management Pack for scripting It does not interfere with any versions of Python you already have installed 3 After the Runtine Components have been installed the Storage Management Pack InstallationShield wizard now opens Click Next and you are prompted to accept the IBM license 4 You are now prompted to either do a complete installation or a custom installation Because the IBM Storage Management Pack consists of four management packs you can choose which packs to install The list of packs is shown in Figure 7 106 The size of each pack is trivial less than 200 KB each Custom Setup Select the program Features you want installed Click on an icon in the list below to change how a Feature is installed Feature Description Management Packs gt SAN volume Controller Storwize Y7 000 IBM Flex System w7000 This Feature requires 140KB on vour hard drive Install to Ci Program Files IBMi Storage Host BM storages CoM InstallShield F
460. nterface Modules and switch B s zone is connected to port 3 on the Interface Modules For more information see the IBM Redbooks publication BM XIV Storage System Host Attachment and Interoperability SG24 7904 Chapter 3 IBM XIV architecture components and planning 91 Single switch solution This configuration is resilient to the failures of a single Interface Module host bus adapter and cables but in this configuration the switch represents a single point of failure If the switch goes down because of a hardware failure or because of a software update the connected hosts lose all data access Figure 3 30 shows this configuration option ELENE ELEA T THH EUNDI 22 a nt a ELE UN E Hosts with 1 HBA Ee SELLE TMN TT e p Woqg ES FE L Switch JUUN 1 j J i OMS il aA L p IEIS ETEITCNSILITEEE E a ie Pete kB BBs _ 2t B E a Figure 3 30 Non redundant configuration Use a single switch solution only when no second switch is available or for test environments Single HBA host connectivity Hosts that are equipped with a single Fibre Channel port can access only one switch This configuration is resilient to the failure of an individual Interface Module but there are various possible points of failure switch cable and HBA that can cause access loss from the host to the XIV Storage System This configuration which is not desirable for any production system is used if there is no way of adding a second
461. o the output shown in Figure 4 60 on page 158 Chapter 4 IBM XIV Storage Management software 157 Name Size GB Master Name Consistency Group Pool Creator Used Capacity GB myvol_ 10 223 ITSO itso myvol_ 11 223 ITSO itso myvol 12 223 ITSO itso myvol_ 13 223 ITSO itso myvol 14 223 ITSO itso myvol_ 15 344 ITSO itso Figure 4 60 vol_list command output To find and list a specific volume by its SCSI ID serial value run the following command vol by id id 23 To create a volume run the following command vol create size 51 pool ITSO Pool vol myvol_ 16 The size can be specified either in gigabytes or in blocks where each block is 512 bytes If the size is specified in blocks volumes are created in the exact size specified If the size is specified in gigabytes the actual volume size is rounded up to the nearest 17 GB multiple making the actual size identical to the free space consumed by the volume This rounding up prevents a situation where storage space is not fully used because of a gap between the free space used and the space available to the application The volume is logically formatted at creation time which means that any read operation results in returning all Zeros as a response To format a volume run the following command vol_format vol myvol_ 16 All data stored on the volume is lost and unrecoverable If you want to bypass the warning message put y directly after the XCLI command The following ex
462. oductivity Center GUI Chapter 6 Performance 277 After loading this data into a spreadsheet certain formatting is helpful to prepare the spreadsheet for the easiest use See Figure 6 30 for the following formatting suggestions gt Sort by date and time gt Freeze panes in cell E3 gt Data filters in row 2 A B G D E F G H K L M N AM AN AO Port Total Port Overall Port Port Port Send Receive Port Port Send Receive Port Port Send Receive Total Port Port Send Receive Total Port Response Response Response Bandwidth Bandwidth Bandwidth 1 Subsystem Port WWPN Time Interval I O Rate I O Rate I O Rate Data Rate Data Rate Data Rate Time Time Time Percentage Percentage Percentage lt x x x x x x x z z z z z z 3 XIV 2812 7803760 IBM 1 FC_Port 4 1 500173800EB00140 27 09 11 10 13 PM 900 1748 19 877 48 2625 67 13 69 6 91 20 6006 12 4 1 1 8 6 3 34 1 68 2 91 4 XIV 2812 7803760 IBM 1 FC_Port 5 1 500173800EB00150 27 09 11 10 13 PM 900 1755 05 876 38 2631 43 13 71 6 92 20 6366 12 3 1 1 8 6 3 34 1 69 2 51 5 XIV 2812 7803760 IBM 1 FC_Port 6 1 500173800EB00160 27 09 11 10 13 PM 900 1748 74 876 65 2625 39 13 69 6 9 20 5969 12 4 Li 8 6 3 34 1 68 2 51 6 XIV 2812 7803760 IBM 1 FC_Port 7 1 500173800EB00170 27 09 11 10 13 PM 900 1750 07 876 83 2626 91 13 7 6 93 20 6282 12 3 1 8 6 3 34 1 69 2 51 7 XIV 2812 7803760 IBM 1 FC_Port 8 1 500173800EB00180 27 09 11 10 13 PM 900 1749 06 878 22 2627 28 13 7 6 92 20 6191 12 3 al 8 5 3 34 1 68 2 51 8 XI
463. oe S N se a S a S Se ANY s s ay oe Ss s se ay amp Ss se se ay O AY ge ay Y YN NNW WY VY WY OP OF FD DW KE RK RH mH oO OH YY DY HD S amp S Total 1 0 Rate I Os per second Figure 6 32 Example IOPS versus response time curve IBM XIV Storage System Architecture and Implementation The slope of the curve is almost flat as IOPS increase through most of the graph But when the IOPS reach 50 000 the latency begins to increase rapidly This point is what is referred to as the knee of the IOPS versus response time curve The shape of this curve is typical of all spinning disk systems The actual IOPS versus latency numbers the slope of the flat section and the location of the knee would be different for each different disk system The main point that we want to make here is that the goal is to run production workloads in the horizontal section of the curve As you monitor performance if you begin to notice that response times are increasing significantly over their normal levels it is time to determine the cause before the application owners begin to complain There are many things that can cause response times to increase in this way such as the following reasons gt Fibre Channel or iSCSI SAN network issues gt Host performance issues causing the I Os to be delivered slowly gt Pushing the XIV Storage System configuration to its performance limits operating in the knee Prolonged periods of high response times assoc
464. of starting the XCLI functions are covered in the following list gt XCLI Session Click the XCLI program shortcut in the programs menu or on the desktop You are prompted for user credentials and the IP address of the XIV system you want to manage Alternatively from the XIV GUI use the XCLI link in the Tools drop down menu of the menu bar or right click in the System view and choose Launch XCLI as shown in Figure 4 39 on page 132 Initiating an XCLI Session from within the XIV Storage Management GUI automatically provides the current user ID and password and connects to the system selected Tip XCLI Session is the easiest way to issue XCLI commands against XIV Storage Systems Figure 4 39 on page 132 shows the process of starting XCLI from the Systems menu Chapter 4 IBM XIV Storage Management software 131 Modify IP Addresses Remove System Create A Group Containing This System Suspend Monitoring View Events View Statistics View Storage Pools XIV 02 1310114 11 0 0 63 View Volumes by Pools View Volumes View Hosts View Mirroring View Migration View Mirroring Connectivity View Migration Connectivity j Launch XCLI SS Launch XIVTop Properties Figure 4 39 Starting XCLI from the Systems menu gt XCLI command prompt Another means to start the XCLI is through the Windows command prompt This method can be useful for scripting commands for configuration related matters When using this method user
465. of the XIV Storage System is shown in the upper right corner in this example it is in Full Redundancy but it can be Rebuilding or Redistributing Swipe to the left to go to the Hosts window Total 100794 XIV 02 1310114 Volume ITSO Blade1 IOmeter 57 120 sec 100 80 60 ago Volumes ITSO_Blade1_lOmeter ITSO_HS22_blade4 Lpar3_lun35 Lpar3_lun34 Lpar3_lun33 Lpar3_lun32 Lpar3_lun31 v TOPS 100793 1 CO Oo amp IOPS 100793 curre nt time BW MBps Latency ms 49 2 2 0 0 0 TA 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Figure 7 31 IBM XIV Mobile Dashboard Volume view BW 49 2 MBps Latency 2 0 Ms Full Redundancy I If the Mobile Dashboard is displayed in portrait mode by rotating your iPad a list of up to 27 volumes is displayed instead Chapter 7 Monitoring 311 Host view The Host performance window is displayed when the iPad is in landscape mode as shown in Figure 7 32 From this window you can see up to 120 seconds worth of performance for the highlighted host Use your finger to rotate the arrow on the purple host icon to switch the display between IOPS bandwidth in MBps and latency in ms The data redundancy state of the XIV Storage System is shown in the upper right corner in this example it is in Full Redundancy but it can potentially also be Rebuilding or Redistributing Swipe to the right to go to the Volumes window Pou aes ae Peal ae MT at ie 8
466. offer multiple selections when only one XIV Storage System is defined to the GUI _ Connectivity SL i r a 1 All Systems Alerts All Systems Events Figure 7 1 Systems menu view The All Systems window m If you select All Systems you are taken to a view showing all the defined IBM XIV systems By default the current input output operations per second IOPS for each XIV Storage System is displayed However by right clicking the green box at the top of any defined XIV Storage System you can change all the IBM XIV systems to different metrics This action is shown in Figure 7 2 XIV_PFE2_1340010 G32 Show Systems lOPS Show Systems Utilization Show Systems Status Show Systems Number of Hosts Show Systems Number of Volumes Show Systems Hardware Type Figure 7 2 Changing the All Systems view IBM XIV Storage System Architecture and Implementation Possible metrics include IOPS systems utilization usage of hard space as a percentage systems status the IBM XIV systems are fully redundant redistributing or rebuilding number of defined hosts or number of defined volumes with the number of snapshots shown in brackets and system hardware type XIV generation disk type and hardware configuration The All Alerts window An alert is defined as a critical event or hardware failure in one of the monitored IBM XIV systems If you open the All Alerts window you see all the current aler
467. oftware and hardware that provide Fibre Channel and IP network Small Computer System Interface iSCSI host connectivity Important Disks of different sizes cannot be intermixed within the same XIV Storage System configuration XIV Storage System software Version 11 0 1 or later is required for using 3 TB disks and XIV Storage System software Version 11 4 0 or later is required for using the SAS SED drives in 2 TB 3 TB or 4 TB Chapter 3 IBM XIV architecture components and planning 59 The bottom of the rack contains three uninterruptible power supplies UPSs that supply power to all XIV Storage System components They also provide enough battery backup power for emergency XIV Storage System shutdown if main power is lost for more than 30 seconds A Maintenance Module and two InfiniBand switches are installed near the middle of the rack just above module 6 The InfiniBand network provides redundant and fast communications paths between the modules This grid network ensures communication between all modules even if one of the switches or a cable connection fails Furthermore this grid network provides the capabilities for parallelism and the execution of a data distribution algorithm that contributes to the performance of the XIV Storage System All cabling between the modules and switches including the internal power connections are fully redundant using two sets of cables All cables use industry standard plugs 3 1 1 Fully populate
468. ole CN XIVAdmins CN Users DC itso DC storage DC ibm DC com Read Only role CN XIVReadonly CN Users DC itso DC storage DC ibm DC com LDAP General User ID Attribute sAMAccountName User Name Attribute i userPrincipalName LDAP Servers Pe XIV Group Attribute memberOf User Credentials Storage Admin Role CN xIVAdmins CN Users DC its0 DC st Read Only Role z CN XWReadonly CN Users DC itso DC Role Mapping Secure LDAP Parameters Figure 5 66 LDAP Configuration Role Mapping tab LDAP mode When you activate the LDAP mode it deactivates all defined users on the XIV Storage System and only LDAP users with the appropriate group role have access to the system You will also be logged out from the XIV Storage Management GUI 9 Click Update and the configuration is now finished 5 7 3 Using XIV Storage System Command Line Interface 222 The quickest method for configuring LDAP in an XIV Storage System is to use the XIV Storage System Command Line Interface XCLI You must define your LDAP Server in the XIV Storage System as shown in Example 5 8 Example 5 8 XCLI add server XIV 02 1310114 gt gt ldap_ add server fqdn itso storage ibm com address 9 155 113 143 base _dn CN Users DC itso DC storage DC i bm DC com Command executed successfully XIV 02 1310114 gt gt ldap_list servers FQDN Address Base DN itso storage ibm com 9 155 113 143 CN Users DC itso DC storage DC ibm DC com IBM XIV Storage Syst
469. on gt Makes a copy of the non redundant partitions and writes them according to the new target distribution This process is known as rebuilding gt Simultaneously begins to redistribute the redundant data according to the new target data distribution This process is known as redistributing Note After an XIV Storage System component failure rebuild and redistribution begin immediately and at the same time The following sections take a closer look at XIV data rebuild and redistribution 48 IBM XIV Storage System Architecture and Implementation Rebuilding after a failure When a disk drive or a module fails the XIV Storage System data distribution algorithms automatically identify the non redundant partitions and then begins the rebuilding process The XIV Storage System then makes copies of just those non redundant partitions and places this data in reserved areas of the disk drives that exist for just this circumstance During this rebuilding period the XIV Storage System is not redundant Therefore this phase is a self healing phase to get back to full redundancy and is done at a high priority within the XIV Storage System Note XIV Storage System software Version 11 2 introduced enhancements that significantly reduce rebuild times by as much as 50 To illustrate this rebuild scenario we purposely failed module 13 as shown in Figure 2 11 Notice the status bar in the lower right corner of the XIV Storage Management GUI sho
470. on 4 1 2 XIV Storage Management software interfaces The XIV Storage Management tools include a graphical user interface XIV Storage Management GUI an XIV Storage System Command Line Interface XCLI and XIV Storage Management Top GUI XIV Top which is used to monitor performance XIV Storage Management GUI The XIV Storage Management GUI or XIV GUI is an intuitive graphical user interface that lets you perform most administrative and technical operations depending upon the user role for one or several IBM XIV systems The motivation behind XIV Storage Management and the resulting GUI design is to eliminate the complexities of system management Typical operational challenges such as setup configuration changes general administration and more are achieved with a few clicks The XIV Management GUI supports two methods for connecting to IBM XIV systems gt Direct mode to one or more IBM XIV systems but acting on one XIV system at a time gt Manager mode through the IBM Hyper Scale Manager Note The IBM Hyper Scale Manager reduces operational complexity and enhances Capacity planning through integrated management of multiple XIV systems It is ideal for large and multi site XIV deployments For more information about the IBM Hyper Scale Manager see the IBM Redpaper BM Hyper Scale for the XIV Storage System REDP 5053 This chapter contains descriptions and illustrations of tasks that are performed by a storage administr
471. on Monitoring health alert Alert Description CA Windows Service And Process Monitoring b 1 Disk 6 4 Disk 1 Disk 6 4 hs ace W2K12Team6 XIVWSW2K12 local 10 0 20 102 Description status is Failed the cause must be investigated to 10114 1 Module 6 1 Disk 6 4 determine the required fix Alert Monit _ Disk Monitor eated 9 24 2013 2 31 00 PI Figure 7 111 SCOM Alerts window Chapter 7 Monitoring 385 Events The Events window shows events for each monitored XIV Storage System SCOM places XIV Storage System events into three categories gt Information gt Error gt Warning The list of events is refreshed every 10 minutes Events do not have or need a resolution status The initial event collection that SCOM runs does not collect events that are more than two days old There is no way to change this setting After the initial collection of events SCOM collects only new events created since the last event collection up to a maximum of 300 events per collection SCOM then examines the new events to see if alerts need to be raised A short delay might occur between the collection of the events and the creation of the alert Systems SCOM lists all defined IBM XIV systems that are being monitored in the Systems window By default the systems monitoring list is refreshed every 30 minutes From the Systems view it is possible to confirm the health of all the monitored components of each XIV Storage System and collect
472. on complete dramatically faster and with minimal impact to the ESX server increasing scalability and storage performance gt Host Rate Limiting Quality of service QoS The XIV Storage System system resources such as storage and cache constitute a virtualized environment that is shared by all hosts and applications This approach lends itself exceptionally well to accommodate high performance requirements for multiple applications with similar performance objectives through fair resource allocation In environments with applications that have various performance objectives the XIV Host Rate Limiting feature enables the client to restrict the system s processing power allocated to specified host applications maximizing the power available for applications requiring the utmost performance gt Support for IPv6 and IPSec IPv6 and IPSec are supported in XIV Gen starting with software Version 11 1 x The IPv6 support applies only to management ports The internal XIV addresses are still IPv4 no change Starting with Version 11 1 1 the XIV Gens offers US Government USG IPv6 compliance gt XIV is well suited for cloud deployments The grid design stripes data across all modules and spindles incorporating data redundancy for consistent and predictable I O performance that is always load balanced To scale out XIV supports IBM Hyper Scale Mobility and IBM Hyper Scale Consistency for scale out needs See the IBM Redpaper BM
473. on describes the basic steps to follow to get started using the GUI Signing onto the XIV Storage Management GUI When starting the XIV Storage Management GUI for the first time a login window prompts you for a user name and its corresponding password before granting access to the XIV Storage System The default user is admin and the default corresponding password is adminadmin Figure 4 8 Storage Management User admin Password TrTTTtititt ty Login gt Licensed Materials Property of IBM Corporation and other s Copyright amp 2008 2012 IBM and XIV are registered trademarks of IBM Corporation in the United States other countries or both Figure 4 8 Login window with default access Important Remember to change the default passwords to correctly secure your system For more information see 5 5 5 Password management and resets on page 202 The default admin user comes with the storage administrator storageadmin role The XIV Storage System offers role based user access management that consists of the already mentioned storage administrator application administrator security administrator and read only role The direct mode access is allowed for stand alone instances of the GUI on users workstations and desktops as well as the demo mode 110 IBM XIV Storage System Architecture and Implementation For more information about user security and roles and how to manage multiple storage systems se
474. on tab that is shown in Figure 5 56 enable LDAP by setting Use LDAP to Yes You can also test your LDAP with a user already defined in LDAP LDAP Configuration Test and Complete LDAP Authentication x Test and Complete LDAP Authentication aisi Provide a User Name and Password that has already been configured on your Directory Services to verify configuration If needed please go back and review your configuration before finishing Server Type LDAP Servers XIV User mes Use LDAP Yes Unique ID s a Groups Test LDAP configuration Secure LDAP a User Name XIV Bind amp Cache z Fassword LLL f Test amp Activation Finish Figure 5 56 Test and Activation tab 17 At this stage click Finish to complete the setup or click Next to go to the exit and summary window that is shown in Figure 5 57 LDAP Configuration Exit this wizard x Exit this wizard Welcome Exit this wizard Server Type LDAP Servers AIV User Unique ID s User Name CN xIV CN Users DC ite0 DC storage DC ibm DC com Groups ID Attribute sAMAccountName Secure LDAP 5 5 Name Attribute Bind amp Cache userPrincipalName Test amp Activation Group Attribute os memberOf Finish Storage Admin Role Figure 5 57 Wizard summary IBM XIV Storage System Architecture and Implementation LDAP mode considerations gt After you activate the LDAP mode it deactivates all previously defi
475. onnection can be complicated and time consuming Remote mirroring connectivity Planning the physical connections also includes considerations when the XIV Storage System is installed in a Remote Copy environment Contact advanced IBM XIV Storage System support for assistance in planning remote mirroring connectivity to ensure maximum resilience to hardware failures and connection failures Remote Copy links which connect the direct primary system and secondary system must also be planned for before the physical installation The physical Remote Copy links can be Fibre Channel links direct or through a SAN or iSCSI port connections using Ethernet However iSCSI is not the best option for this usage Planning for growth Consider growth and the future I O demands of your business Most applications and databases grow quickly and the need for greater storage capacity increases rapidly Planning for growth before the implementation of the first XIV Storage System in the environment can save time and effort in the future 3 2 2 IPv6 addressing and planning Internet Protocol Version 6 or IPv6 is intended to supplement and over time replace the IPv4 protocol that is still largely used today Getting ready to make the transition to IPv6 is becoming critical for some companies because the pool of available IPv4 addresses is already depleted IPv6 is described by the Internet Engineering Task Force IETE RFC2460 Chapter 3 IBM XIV architect
476. ools Help O A All Systems 3 gt XIV 7826153 v Statistics v System Time 11 31 AM Q All Interfaces enung 10 40 10 45 10 50 10 55 11 00 11 05 11 10 1115 11 20 March 8 2013 Interfaces O 0 8 KB 64 512 KB olumes F 8 64 KB gt 512 KB i Al XIV 7826153 Figure 6 9 Default statistics monitor view In Figure 6 9 the X axis of the graph represents the time and can vary from minutes to months The Y axis of the graph is the measurement that is selected The default measurement is IOPS The statistics monitor can also illustrate latency and bandwidth in the same graph or in the multigraph view The other options in the statistics monitor act as filters for separating data These filters are separated by the type of transaction reads or writes cache properties hits compared to misses and cache memory hits or flash SSD cache hits or the transfer size of I O as seen by the XIV Storage System The filter pane has been updated to reflect support for SSD Caching and to filter between read I Os from the main cache Mem Hit and read I Os from the extended SSD cache Figure 6 10 shows a detailed view of the filter pane C Mem Hit 0 8 KB O 64 512 KB SSD Hit 8 84 KB O gt 512 KB Figure 6 10 Filter pane for the statistics monitor The filter pane allows you to select multiple items within a specific filter for example if you want to see reads and writes s
477. or Android login and Demo Mode There are performance monitoring windows for overall IBM XIV System performance host performance and volume performance You can also view specific performance measurements In Figure 7 36 on page 315 the system performance and volume performance are depicted 314 IBM XIV Storage System Architecture and Implementation P al All Systems 5 Connected 5 Connected Volumes chart view Bandwidth IOPS Latency Demo Volume 53 jemo Systel Bandwidth IOPS Latency 2 8 mb s 0 0 ms a ee CURRENT IOPS 3 456 Demo Volume 15 4 3 mb s Q Iy 0 ateg of 1913 OTB Volumes System Volumes Figure 7 36 XIV mobile dashboard for Android System and Volumes performance 7 2 XIV Storage System event notification The XIV Storage System allows you to send alerts by email SMS messages and SNMP traps 7 2 1 Configuring the XIV Storage System to send notifications You can configure the XIV Storage System using flexible rules to ensure that notification is sent to the correct person or group of people according to the various parameters This event notification is similar to but not quite the same as XIV Storage System call home which is described in 7 3 Call home and remote support on page 324 7 2 2 Setting up event notification Configuration options are available from the XIV Storage Management GUI You have the flexibility to create a detailed events notification plan based on specif
478. or main GUI window for the selected system Systems Actions View Tools Help O Settings E Launch xci fj Launch xivTop amp admin amp All Systems 12 gt Lab_Mainz 6 gt v System v System Time 10 29PM Q ALLEE 0000009 XIV_PFE2_1340010 EE xa Figure 7 10 Monitoring the IBM XIV Storage System The System view shows a graphical representation of the XIV Storage System rack with its components You can click the curved arrow at the lower right of the picture of the rack to show a view of the patch panel Figure 7 10 shows the patch panel for an XIV Storage System Gen3 Model 214 You get a quick overview in real time about the system s overall condition and the status of its individual components The display changes dynamically to provide details about a specific component when you hover the cursor over that component Status bar indicators at the bottom of the window which are shown in Figure 7 11 indicate the overall operational levels of the XIV Storage System Hardware Alerts 1 ja Phasing In XI _PFE_04 1310133 Disk 2 Module 14 XIV_PFE_04 1310133 130 954 aB 72 it Figure 7 11 Status bar indicators 290 IBM XIV Storage System Architecture and Implementation The following information describes the status bar indicators in Figure 7 11 on page 290 gt The first indicator on the left shows the amount of soft or hard storage capacity currently alloca
479. orage networks and replication For detailed information about Tivoli Storage Productivity Center V4 2 see BM Tivoli Storage Productivity Center 4 2 Release Guide SG24 7894 01 Starting with Tivoli Storage Productivity Center V4 2 a new method for data collection by way of a native application programming interface API is available The native API is an internal native interface to IBM Storage systems such as XIV Storwize V7000 SAN Volume Controller and IBM System Storage DS8000 Previously Tivoli Storage Productivity Center communicated with the XIV Storage System through a Common Information Model object manager CIMOM agent SMI S compliant also called SMI S agent embedded in the XIV Storage System software Figure 7 77 on page 354 shows a schematic view of both methods The Native API NAPI enables additional Tivoli Storage Productivity Center functions and performance data collection and requires Version 10 2 2 or later of the XIV Storage System software Chapter 7 Monitoring 353 TPC Server TPG Server Single process NAFI Subs stems Data Collection Logic a ction TPC Sener Data Collection TRC Serer CIMOM longe gt e Proxy Server Native herf Figure 7 77 Tivoli Storage Productivity Center data collection before V4 2 on left V4 2 on right 7 6 1 Setting up and discovering XIV systems in Tivoli Storage Productivity Center V4 2 or later If you are still using Tivoli Storage Productivit
480. ore Results link After you download the correct package to the Linux host you can run the file as root and it starts the installation wizard Example 7 36 shows the installation of the proxy agent Example 7 36 Remote Support Proxy agent installation xivproxy installer rpm 1 3 1 b612 sles11 x86 64 bin Starting installer please wait International License Agreement for Non Warranted Programs Part 1 General Terms BY DOWNLOADING INSTALLING COPYING ACCESSING CLICKING ON AN ACCEPT BUTTON OR OTHERWISE USING THE PROGRAM LICENSEE AGREES TO THE TERMS OF THIS AGREEMENT IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF LICENSEE YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND LICENSEE TO THESE TERMS IF YOU DO NOT AGREE TO THESE TERMS Press Enter to continue viewing the license agreement or Enter 1 to accept the agreement 2 to decline it or 99 to go back to the previous screen 3 Print 1 Xivproxy O off l off 2 off 3 on 4 off 5 on 6 off Installation completed successfully You can edit the proxy conf file which is in the etc xiv folder to add the relevant connectivity settings as shown in Example 7 37 Example 7 37 Extract of the proxy conf file Configuration file for XIV remote support proxy Network interface and port that the XIV system will connect to ListenInterface eth0 ListenPort 8988 Remote support server address as supplied by IBM TargetAddress 195 110 41 141 TargetPort 443
481. ormation relates to the configuration that is shown in Figure 6 4 gt Each host is equipped with dual HBAs Each HBA or HBA port is connected to one of two FC switches gt Each of the FC switches has a connection to a separate FC port of each of the six Interface Modules gt Each LUN has 12 paths Each host HBA is physically connected to all six of the XIV Storage System Interface Modules This setup provides the ability for each HBA to involve the maximum available I O capabilities For XIV Storage System each Interface Module has two 2 port Fibre Channel adapters It is a best practice that each zone is physically connected to one port on each XIV Storage System Fibre Channel adapter For example switch A s zone can be connected to port 1 on the Interface Modules and switch B s zone can be connected to port 3 on the Interface Modules 6 2 4 Host considerations The XIV Storage System provides maximum performance when the application hosts can engage all the components of the XIV Storage System grid architecture with parallel I O requests to the LUNs Ideally the host workload can be tailored to use multiple threads to simultaneously use multiple paths and access data on multiple volumes The following considerations can significantly affect XIV Storage System performance gt Application threads gt HBA and disk queue depth 258 IBM XIV Storage System Architecture and Implementation gt Logical Volume Manager LVM
482. ormational all emailtest snmptest yes no smstest Critical all smstest yes no Example 7 29 shows how to delete rules destinations and gateways It is not possible to delete a destination if a rule is using that destination And it is not possible to delete a gateway if a destination is pointing to that gateway Example 7 29 Deletion of notification setup gt gt rule delete y rule smstest Command executed successfully gt gt dest_delete y dest smstest Command executed successfully gt gt smsgw delete y smsgw test Command executed successfully 7 3 Call home and remote support The call home function allows the XIV Storage System to send event notifications to the XIV Remote Support Center XRSC This function enables both proactive and failure notifications to be sent directly to IBM for analysis The XRSC takes appropriate action up to dispatching an IBM service support representative SSR with a replacement part or engaging level 2 or higher level support to ensure complete problem determination and a solution Important The configuration of call home and the configuration of remote support facilities are recommended to assist with failure detection diagnosis and resolution 7 3 1 Call home feature Call home is always configured to use SMTP and is only configured by qualified IBM SSRs typically when the XIV Storage System is first installed If an event is received by the XRSC that requires service or investiga
483. ory than the model A14 DDR3 also uses less power than DDR2 At 24 GB per module a full XIV Storage System Gen3 has 360 GB of memory Part of the memory is used as module system memory the rest is used as cache memory Cache consists of both read cache where the module holds previously read data and pre fetched data plus write cache where the module holds data that is being cached before being de staged to disk When the optional SSD cache extension is installed Model 114 software 11 1 0 or later each module gets an extra 400 GB capacity for use as an extension of the DDR3 cache Power supplies The modules are powered by a redundant power supply unit PSU cage with dual 850 W PSU assemblies as shown in Figure 3 16 on page 76 These power supplies are redundant and can be individually replaced with no need to stop using the module The power supply is a field replaceable unit FRU Each power supply is cabled to a different UPS unit Chapter 3 IBM XIV architecture components and planning 75 e ro s x lt Figure 3 16 Redundant module power supply units Model 214 unique components Data Modules and Interface Modules in Model 214 have the following specific components Six core processor Model 214 modules are powered by a six core Intel Westmere CPU E5645 processor which is based on the 32 nm technology and 2 4 GHz clock frequency Equipped with 12 MByte L3 cache and DDR3 1333 Mhz the CPU is featuring Hyper
484. osoft website http msdn microsoft com en us 1ibrary ms683883 VS 85 aspx In our illustration we use both the Active Directory member0Of attribute and the OpenLDAP description attribute for role mapping The mapping is done by assigning the appropriate attribute value to the xiv_group_attrib configuration parameter with the I1dap_config_set XCLI command Idap_config_ set xiv_group_attrib member0f It can also be defined in the XIV Storage Management GUI as described in LDAP role mapping for the storageadmin and readonly roles LDAP role mapping for the storageadmin and readonly roles The XIV Storage System administrator requires two LDAP group names that are used for storageadmin and readonly role names in LDAP In our example the XIV Storage System administrator uses the XIVAdmins and X VReadonly LDAP group names for mapping to storageadmin and readonly roles This mapping needs to be entered using the full DN because this full DN is the populated value in the member Of attribute The XIV Storage System administrator sets corresponding parameters in the XIV Storage System Idap_config set storage_admin_role CN XIVAdmins CN Users DC itso DC storage DC i bm DC com Idap_config set read_only_role CN XIVReadonly CN Users DC itso DC storage DC i bm DC com Case sensitivity The LDAP server does not use case sensitive string matching for the memberOf attribute value For example XI1VAdmins xivadmi
485. ost useful for XIV Storage System performance is contained in the following reports gt By Storage Subsystem overall statistics on the entire XIV Storage System By Module Node gt gt By Volume gt By Port Figure 6 29 shows where this data is in the Tivoli Storage Productivity Center GUI W IBM Tivoli Storage Productivity Center Intelsx3850X5 ad mel stg ibm Storage Subsystem Performance By Storage Subsystem File View Connection Preferences Window Help gt 8 x 21m Selection Storage Subsystems avigation Tree Administrative Services IBM Tivoli Storage Productivity Center Storage Subsystem Performance By Storage Subsystem Data Manager S Number of Rows 1 Data Manager for Databases Data Manager for Chargeback Subsystem Time Interval Read I O Rate normal Read I O Rate sequential Re Disk Manager g Al xIv 2812 7803760 18M 06 10 2011 5 58 10 PM 899 5 Nia Nia tI i Storage Subsystems Storage Optimizer SAN Planner Monitoring Alerting Profile Management Reporting Groups Storage Subsystems Storage Subsystem Performance By Controller By 1 0 Group By Module Node By Array By Managed Disk Group By Yolume By Managed Disk By Port Constraint iolations Fabric Manager Tape Manager Element Manager Replication Manager 1 7 12 PM A D amp tal Op enojo Figure 6 29 Tivoli Storage Pr
486. osts Operating System 0 2 enterprises 8072 3 2 10 01 5 6 1 4 1 8072 5 2 105 E xY ESP 1 Y10 0 1300203 9 155 53 252 dyn 9 1 55 53 252 mainz de ibm Linux 2 6 Ge xIVESP 1 V10 0 1300203 9 155 63 251 dyn 9 1 55 53 251 mainzde ibm Linux 2 6 E EY ESP 1 eee 9 155 63 250 dyn 9 155 53 250 mainz de ibm Linux 2 6 2 XIV V10 0 M Sued 9 155 56 101 xivlab Ola mainzde ibm com Linux 2 6 Ea AlYY10 0 M eee 9 155 586 1700 xiv lab 01 mainz de ibm com Linux 2 6 a AN 10 0 M e ene nek 94 155 56 102 xiv lab 01b mainz de ibm com Linux 2 6 9 155 533 252 xiv lab 01b mainz de ibm com iv lab O1 mcu a SNMP Browser Event Log Remote Session Set Presence Check Interval All Available Recordings All Available Thresholds Resource Monitors Set Status a Figure 7 65 Select Event Log The Event Log window can be configured to show the events for a defined time frame or to limit the number of entries to show Selecting a specific event shows the Event Details in a pane on the right side of the window as shown in Figure 7 66 Event Log XI 10 0 MNOOO50 File Edit View Options Help g Ge Events 100 Last 1Weeks W22008 11 31 09 AM Director Topology Online QA008 11 15 31 AM Director Topology Offline 91 2008 Event Details Values Q2r2008 11 31 09 AM Event Text System XW 10 0 MMOO080 is online System IY V1 OO MMOO050 is offline Keywords Date Time ai f2008 ai f2008 ai f2008 ai f2008 ai f2008 ai f2
487. ot be deleted from the system and are always authenticated natively by the XIV Storage System even if the system operates under Lightweight Directory Access Protocol LDAP authentication mode User accounts can initially be created by the admin user only After the admin user creates a user account and assigns it to the storageadmin Storage Administrator role then other user accounts can be created by this storageadmin user In native authentication mode the system is limited to creating up to 128 user accounts This number includes the predefined users User password The user password is a secret word or phrase used by the account owner to gain access to the system The user password is used at the time of authentication to establish the identity of that user User passwords can be 6 12 characters long using the characters a z A Z amp _ 153 lt gt and and must not include any space between characters In native authentication mode the XIV Storage System verifies the validity of a password at the time the password is assigned Predefined users have the following default passwords assigned at the time of XIV Storage System installation see Table 5 1 Table 5 1 Default passwords Predefined user Default password technician Predefined Only used by the XIV Storage System technicians xiv_development Predefined Only used by the IBM XIV development team xiv_maintenance Predefined Only us
488. otal number of both hosts IOPS can never be higher than 10000 IOPS Management of this feature is easy when you use the QoS Performance Class view of the Hosts and Cluster function menu To configure a performance class complete the following steps 1 Select the QoS Performance Class view from the Hosts and Clusters menu and click Add Performance Class on the toolbar A dialog opens as shown in Figure 4 36 Add Performance Class System XM_PFE_04_1310133 ae Name lOps Limit 6 600 000 Bandwidth Limit 6 60 000 Figure 4 36 Add Performance Class window Chapter 4 IBM XIV Storage Management software 129 2 Enter a suitable performance class name either an IOPS limit a BW limit or a combination of both based on business needs There are two choices when entering the limitation settings total or interface The total intended limitation settings depend on the number of Interface Modules being used by the hosts within the same performance class The maximum rate setting is multiplied by the number of Interface Modules installed in the XIV Storage System For example in a fully populated XIV Storage System the maximum total QoS IOPS value is 600 000 IOPS with a minimum of 6 IOPS The maximum total QoS BW value is 60 000 with a minimum of 6 Conversely QoS settings can also be specified on a per Interface Module level Taking into account the information presented earlier on a fully populated system the maximum tot
489. ouncements or other publicly available sources IBM has not tested those products and cannot confirm the accuracy of 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 This information contains examples of data and reports used in daily business operations To illustrate them as completely as possible the examples include the names of individuals companies brands and products All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental COPYRIGHT LICENSE This information contains sample application programs in source language which illustrate programming techniques on various operating platforms You may copy modify and distribute these sample programs in any form without payment to IBM for the purposes of developing using marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written These examples have not been thoroughly tested under all conditions IBM therefore cannot guarantee or imply reliability serviceability or function of these programs Copyright IBM Corp 2013 All rights reserved Ix Trademarks IBM the IBM logo and ibm com are trademarks or registered trademarks of International Business Machines Cor
490. oy It relies on standard proven technologies and minimizes the logic code that must be located either on the external XRSC server or on client machines The architecture of the XRSC anticipates and handles various potential attack vectors including encryption protocol and authentication logic The design of the XRSC identifies analyzes and defends against these and other possible attack routes gt Simplicity of implementation and design Simplicity enhances security facilitates implementation at the client site decreases staff training costs and ultimately lowers total cost of ownership TCO by allowing more issues to be resolved quickly and with fewer unnecessary visits by support personnel to client premises gt Accessibility by support personnel The auditing features of the XRSC both enhance security and enable easy reassignment of a Support case among support personnel The XRSC can expedite escalation of support cases to higher level support and allows IBM SSRs to pool knowledge to resolve complex client issues Underlying architecture The XIV remote support mechanism has four major components gt Remote Support Client machine internal The Remote Support Client is a software component inside the XIV Storage System that handles remote support connectivity It relies only on a single outgoing Transmission Control Protocol TCP connection and has no capability to receive inbound connections of any kind The Client is
491. pace reserved for all defined volumes in the storage pool gt Hard pool size Storage pool hard limit It represents the physical storage capacity allocated to volumes and snapshots in the storage pool See 4 4 1 Function of storage pools on page 136 for a detailed description gt Soft pool size Storage pool soft limit It is the limit for the total soft sizes of all the volumes in the storage pool See 4 4 1 Function of storage pools on page 136 for a detailed description Figure 4 44 provides an example of storage pool and size numbers Data written to Storage pool storage pool hard lim it GE Used Volumes THI6 GE Hard i T846 GE Soft at Snapshots Reser Size ofall Storage pool volumes defined soft lim it Figure 4 44 Storage pool and size numbers 138 IBM XIV Storage System Architecture and Implementation To export details shown in the Storage Pools view click the Export icon in the toolbar at the top of the GUI window For more details see Copy and paste of system configuration settings on page 122 Creating storage pools The creation and resizing of storage pools is straightforward and you need to only take care with the size allocation and reallocation The name of a storage pool must be unique in the system Pool size The size of the storage pool is specified as an integer multiple of 10 bytes but the actual size of the created storage pool is rounded up to the nearest integer multiple o
492. performance data from any time period The time stamp is formatted as YYYY MM DD hh mm ss where the YYYY represents a four digit year MM is the two digit month and DD is the two digit day After the date portion of the time stamp is specified you specify the time where hh is the hour mm is the minute and ss represents the seconds Example 6 3 shows a typical use of this command Example 6 3 The statistics_get command example gt gt statistics get end 2009 06 16 11 45 00 count 10 interval 1 resolution_unit minute Figure 6 26 on page 276 shows sample output of the statistics The output shown is a small portion of the data provided Chapter 6 Performance 275 276 Time Read Hit Medium Ops Read Hit Medium Latency Read Hit Medium Throughput 2003 06 16 11 S418 ech 111382 2003 06 16 11 S583 2769 119298 2003 06 16 11 SBS rae 121695 2003 06 16 11 3430 3121 118067 2003 06 16 11 3548 3108 117711 cUUS UE 16 11 Sard eds LOS533 eUUS UE 16 11 esl serl gzl e00g 06 16 11 aoul Babe rEGF eUUS U6 16 11 EEIE S168 74384 eUUS U6 16 11 alas 3449 BS 100 Figure 6 26 Output from statistics_get command Extending this example assume that you want to filter out a specific host defined in the XIV Storage System By using the host filter in the command you can specify for which host you want to see performance metrics which allows you to refine the data that you are analyzing See Example 6 4 for an example of how to per
493. ple 5 14 Example 5 14 LDAP query for generating a list of XIV user accounts amp amp objectCategory user cn xiv description Read Only description Storage Administrator description app To create this query click Saved Queries New Query gt XIV Storage Accounts and select the query name in this example Click Define Query Click Find gt Custom Search gt Advanced and paste the LDAP query from Example 5 14 into the Enter LDAP Query field When a new user account is created and its name and attributes satisfy the search criterion this user account automatically appears in the XIV Storage Accounts view Any LDAP XIV Storage Management GUI front end supporting the LDAP Version 3 protocol can be used for creating views and managing LDAP entries XIV user accounts Table 5 4 provides a list of commands that cannot be used for user account management when LDAP authentication mode is active Table 5 4 XIV commands unavailable in LDAP authentication mode XIV command user_define user_update user_rename user_group_add_user user_group_remove_user Authentication When the XIV Storage System operates in LDAP authentication mode user account creation listing modification and removal functionality is provided by the LDAP server The user_list command can still operate when LDAP authentication mode is active However this command shows only locally defined XIV user accounts and not LDAP account
494. ponents This XIV Gen3 rack security kit is available by ordering RPQ 88S1190 The XIV Storage System Gen3 rack should be considered a dedicated unit for XIV Storage System Spare space within the rack cannot be used for other equipment Rack space Unused rack space cannot be used for other purposes The XIV Storage System Gen3 rack has four optional features as described in Table 3 2 Table 3 2 Rack features for XIV Storage System Gen3 0080 Ruggedized rack option 0082 Rear door heat exchanger 0200 Weight and height reduced shipping 0203 Radio frequency identification device Chapter 3 IBM XIV architecture components and planning 65 66 Figure 3 6 shows the XIV Storage System Gen3 T42 rack Figure 3 6 XIV Storage System Gen3 rack Ruggedized rack option The ruggedized rack option is an optional kit for stabilizing the XIV Storage System Gens rack so that the rack complies with IBM earthquake resistance standards It is important for IBM XIV systems to be adequately restrained during earthquakes to prevent human injury and limit potential damage to critical system components such as hard disk drives The optional ruggedized rack option includes hardware that secures the rack to the floor and cross braces on the front and rear of the rack which prevents the rack from twisting The earthquake resistance option brings the XIV Storage System into compliance with earthquake resistance objectives that are documented in E
495. poration in the United States other countries or both These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol or indicating US registered or common law trademarks owned by IBM at the time this information was published Such trademarks may also be registered or common law trademarks in other countries A current list of IBM trademarks is available on the Web at http www ibm com legal copytrade shtml The following terms are trademarks of the International Business Machines Corporation in the United States other countries or both AIX Informix Storwize BladeCenter NetView System p DS6000 Power Systems System Storage DS8000 Redbooks System x IBM Redpaper Tivoli IBM Flex System Redbooks logo g XIV The following terms are trademarks of other companies Intel Intel logo Intel Inside logo and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries Linux is a trademark of Linus Torvalds in the United States other countries or both LTO the LTO Logo and the Ultrium logo are trademarks of HP IBM Corp and Quantum in the U S and other countries Microsoft Windows and the Windows logo are trademarks of Microsoft Corporation in the United States other countries or both Java and all Java based trademarks and logos are tradem
496. ports and one 2 port 10 GbE adapter 3 1 2 Partially populated configurations The XIV Storage System Gen3 is also available in partially populated configurations of 6 9 10 11 12 13 or 14 modules allowing for more granularity of capacity options Modules can be added as capacity needs increase up to 15 modules Different size drives cannot be intermixed within the same IBM XIV Storage System The SSD Caching extension is also available with partially populated configurations The SSD extension is required for each module present in the partial configuration 60 IBM XIV Storage System Architecture and Implementation In Figure 3 2 certain Interface Modules are labeled Disabled This label means that the Interface Module is not running the special software that characterizes an Interface Module and the host interface adapters are not functional They still function as Data Modules As modules are added to the XIV Storage System configurations these Interface Modules become Enabled from an interface perspective Certain partial rack configurations do not use all host attachment interface ports even though they might be physically present The interface ports are activated automatically as more modules are added to the system Details about these configuration options and the various capacities drives ports and memory are provided in Figure 3 2 Rack Configuration Tdalnumbe of modules Corfiguation type Total numberof data
497. processor and communicates with the processor complex over eight lanes of PCle 2 0 bus bandwidth InfiniBand does extensive end to end link level protocol checking so it is reliable Flash cache One of the most important features of the XIV Storage System Gen3 is the upgrade with flash cache The optional flash cache option is available for Gen3 Model 214 and Model 114 running software Version 11 1 0 or later XIV Gen3 systems can be equipped with a 400 GB SSD for every module and the XIV Gens with 4 TB drives can be equipped with a 400 GB or 800 GB SSD for every module The installation is nondisruptive For a 15 module system this configuration represents 6 TB of read flash cache with the 400 GB SSD feature and with 800 GB SSD it has 12 TB read flash cache For partial configurations see Figure 3 17 Number of modules Number of Memory cache in GB 1 TB Memory cache in Flash cache in TB in the rack en limited capacity 2 TB 3TB GB 4 TB optional 400 GB s00 GB Oooo o ee e 2 4 4 8 SS O SE N SE O 36 72 4 0 8 0 Figure 3 17 Processors and cache There is not an additional disk tier to manage the XIV Storage System Gen3 software manages this flash cache automatically This flash cache feature further improves performance for read workloads especially random read workloads 78 IBM XIV Storage System Architecture and Implementation Memory flash card Each module contains a Compact Flash Card The card is shown in Figure 3 1
498. pter 3 IBM XIV architecture components and planning 79 Redundant power supplies CPU Figure 3 19 Interface Module Depending on the XIV Storage System Gens model a different number of adapters are installed in the Interface Modules gt Model 114 and 214 1 GbE Two 2 port 8 Gbps Fibre Channel HBAs One 4 port iSCSI 1 Gbps Ethernet adapter gt Model 214 10 GbE Two 2 port 8 Gbps Fibre Channel HBAs One 2 port iSCSI 10 Gbps Ethernet adapter These two interface adapter types are used for host attachment to the XIV Storage System The ports can also be used to establish remote mirror links and data migration paths with another remote IBM XIV Storage System or storage systems from other vendors migration For the detailed number of usable iSCSI ports in IBM XIV Storage System Gen3 partial configurations refer to Figure 3 2 on page 61 Figure 3 20 on page 81 shows a schematic view rear view of the two Interface Modules with Fibre Channel and iSCSI ports All Fibre Channel and iSCSI ports used for external connections are internally connected to a patch panel where the external connections are made The patch panel layout depends on the XIV model See 3 1 10 Patch panel on page 85 which shows the two different patch panels 80 IBM XIV Storage System Architecture and Implementation Figure 3 20 shows an XIV Model 114 214 1 GbE and XIV Model 214 10 GbE Interface Module with Fibre C
499. publications n nanana aaaea aaa xiv Summary of changes s e5 6 6 se cos Sy aed Sh Ou oes CeCe pase ee Bee a XV December 2013 Eighth Edition 0 2 0 nes XV Chapter 1 IBM XIV Gen3 Storage System overview 000 cee 1 1 1 What s new in release 11 4 0 0 0 0 ccc teens 2 C2 MAMVOOUCHOM ca rans a 4 ne e Grek cued ests sana tg ase Braet eemno a Be bere wets 2 2 1 3 Total cost of ownership 1 2 0 0 0 0 ee eet eens 3 1 4 XIV Gen3 Storage System models and components 0000 eee eee eee 4 1 5 XIV GenS key design features 0 0 eee eens 6 1 5 1 Massive parallelism 0 20 000 eee eee ees 6 232 NVOLKIOdC DAlaNClAG y sceri 2 eh nee ake BURNS a eine ed Ce eee eS 6 12353 SSM CANIG os acne aredi aR BR iE Dat Oe amp ven Se or as Sentech He SA 20 aide DS NS 6 154 IFASLONVETCOUIIG s c 0 ce iarere heee Sk Rie oe cae ae Boas eet ee eee 6 15 5 Ue VINGAlIZAUON lt 4 wes netetie Se ooh ese eee RE Eee es eae eek noe eee 6 1 5 6 Flash caching Optional 22 vo 0 424 425540 25 eee S165 5 1S eeh Ges Bee aE 7 1o 7 TAIN PLOVISIONING sss te penh e bo OS oe OE RE ae Re eee awk A 7 W0 6 IPTOCCSSING DOW CI errian Biss Won bend na heads a Pater wd walle oe ee Mae 7 15 9 SAIN COMMECUV IVY senao toe ana echt a dain de abate E a 7 15 10 Inter Generatlonall MINOMAG eris se anes ahead ew LAGAN oa a Nae a 7 1 6 The XIV Storage System software 0 0 0 0 ce eee ees 8 1 6 1 IBM XIV
500. puter systems and other data center equipment based on the availability of relevant management packs SCOM can generate alerts when it identifies issues with availability performance configuration or security Depending on your needs using SCOM delivers the following benefits gt Storage administrators can monitor multiple storage products from different vendors gt Microsoft customers can monitor IBM systems using their familiar tools gt System administrators can manage both storage systems and other IT systems from a single consistent interface A key feature of SCOM is its use of management packs which contain application or product specific rules and filters Vendors can create their own management packs relevant to their own products The IBM Storage Management Pack for SCOM is actually a set of management packs that allow you to access and monitor the following IBM storage systems using Microsoft SCOM IBM System Storage DS8000 IBM Storwize V3500 since Version 2 1 IBM Storwize V3700 since Version 2 1 IBM Storwize V7000 IBM Flex System V7000 since Version 1 3 IBM System Storage SAN Volume Controller IBM XIV Storage System YYYY YV Y Yy The rules provided by the management packs remove a significant amount of work when implementing a monitoring solution SCOM itself offers methods to monitor four areas of focus gt Availability gt Configuration gt Performance gt Security Currently the IBM S
501. r group has the Full Access flag turned on all members of that group have unrestricted access to all snapshots on the system At this stage the user group itso _app01_group is still empty 4 Next add a host to the user group by right clicking the name of the user group that you have created to open a menu and select Update Access Control as shown in Figure 5 74 Category Ungrouped Tem itso_app01_group Edit Delete Update Access Control View Accesible Volumes Properties Sort By Figure 5 74 Updating access control for a user group 232 IBM XIV Storage System Architecture and Implementation The User Group Access Control window that is shown in Figure 5 75 opens The window contains the names of all the hosts and clusters defined on the XIV Storage System User Group Access Control Access Control for itso_app01_group Unauthorized Hosts Clusters Authorized Hosts Clusters PFE_XYRA_02 vShpere1 ISCSI sven_thinkpad M3655 _XIVPFE lt lt o Figure 5 75 Access Control Definitions window The left pane shows the list of unauthorized hosts and clusters for this particular user group and the right pane shows the list of hosts that have already been associated with the user group 5 Add or remove hosts from either list by selecting a host and clicking the appropriate arrow 6 Finally click Update to save the changes Unlike in native authentication mode in LDAP authenti
502. r from the current time Similarly Day Week Month and Year can be selected to easily see the performance statistics for these different time durations Also notice the refresh button to the right which updates the graph with the latest information Figure 6 17 Time duration selector Also you can select Custom and a window opens where you can specify a certain date and time Figure 6 18 After you specify the date and time you can select the white box at the bottom of the window and a one hour view of performance data ending at the selected date and time is displayed To change the view from this specific date and time you must use the chart toolbars in the upper left corner of the Statistics view September 2013 E Sun Mon Tue Wed Thu Fri Sat Select September 2043 Figure 6 18 Custom date and time selector Chapter 6 Performance 269 Another interesting view of XIV Storage System performance in the XIV Storage Management GUI can be found by selecting the icon of an XIV Storage System disk drive found in the lower left corner of the XIV Storage Management GUI as shown in Figure 6 19 J Data Modules Disks Statuses ios_sec 80 70 60 50 40 30 20 10 0 4 i N D 2 2 2 o o g 2 2 2 D Wel iy t iy 9 Q w y gt 2 2 2 2 3 3 3 a S 3 8 2 3 8 2 D 4 F f S g i i ii S 9 9 9 9 Q amp La Sep 19 20
503. r is set up during the installation of Hyper Scale Manager See 4 3 XIV Storage Management software usage on page 109 Hyper Scale Manager is running Server Configuration Options Gather Manager Logs Show Audit Log Show Upgrade Logs Manager Inventory Options Backup Restore Options Change root Password Change maintenance Password Change Manager Access Code Start Stop Hyper Scale Manager Service 11 Replace Hyper Scale Manager Certificate 12 Change XIV GUI Communication Ports 13 Change RESTful Interface Port 14 Upgrade Hyper Scale Manager 15 Reboot 16 Shutdown 17 Exit Your Selection gt Figure 5 36 Root user menu window Tip It is a best practice to configure at least one admin level credential user ID and password to be the same as the MSMS login credentials user ID and password Server Admin operations The menu that is shown in Figure 5 37 on page 199 is the Manager Inventory Options menu Using this menu allows the administrator to manage the inventory of IBM XIV systems monitored by the Hyper Scale Manager and control their status 198 IBM XIV Storage System Architecture and Implementation From a security standpoint the following options are available gt Reauthenticate all users This option forces the reauthentication of all GUI logged in users on all XIV This option can be used when there is an authentication change for users and you want it to take effect immediately gt Changing
504. r more systems are selected you can perform an action on those systems together by right clicking any selected system This action brings up a contextual menu allowing you to perform the wanted action IBM XIV Storage System Architecture and Implementation Messages When the Status area alerts the user messages of real time problems in the environment are reported See Figure 4 32 for an example of a real time alert that is displayed on the top left side of the GUI panel Following are examples of the types of messages gt Hardware problem disk modules fan or service Utilization problem pool hard capacity System status Uncleared alerting events System to system connection problem YY vV Yy A Al Systems gt Mainz_Building12 3 gt New Hardware Alert AIW 02 1310114 UPS CHARGE LEVEL Figure 4 32 Event messaging If a configuration related message is noted and clicked regardless of which XIV Storage System is being administered the user is taken directly to the system in question to further review the message contents The user is taken to the event log where the additional details can be viewed Refer to All Systems Events window on page 287 Search and view filtering The XIV Storage Management GUI features a Search function This function allows for easy searches within the XIV Storage Management GUI for configuration related items You can search across all the GUI managed storage systems and you
505. r purposes here we refer to these rebuild and redistribution actions as data redistribution because we are focused on the effects that these redistribution actions have on the storage I O performance seen by the application server For a full discussion on data rebuild and redistribution these concepts are covered in 2 7 2 Preserving data redundancy Rebuilding and redistributing on page 48 When for instance an XIV Storage System disk fails the storage system takes that drive offline identifies the actual data partitions that the drive contained and locates the copy of those data partitions within the rest of the XIV Storage System drives The XIV Storage System then makes a copy of only that actual data and moves that data evenly across each of the remaining disk drives The performance impact during this data redistribution is negligible to the I O characteristics that an XIV Storage System can provide to application servers A redistribution will not take place for a flash drive failure because the optional flash drives are not involved in data retention or redundancy They are merely used as read cache IBM XIV Storage System Architecture and Implementation Consider a fully populated XIV Storage System that experiences this drive failure In this example the XIV Storage System reads data from 168 drives Each drive contains an equal portion of the mirror data copies of the data from the failed drive The XIV Storage System reads dat
506. r the events There are many commands and parameters available We illustrate just a few of the options of the event_list command Various parameters can be used to sort and filter the output of the event_list command See Table 7 1 for a list of the most commonly used parameters Table 7 1 The event_list command parameters max_events max_events Lists a specific number of events lt event_list max_events 100 gt after Lists events after the specified lt event_list after 2008 08 11 04 04 27 gt date and time before Lists events before the specified lt event_list before 2008 08 11 14 43 47 gt date and time min severity Lists events with the specified lt event_list min severity major gt and higher severities lt event_list alerting no gt alerting Lists events for which an alert was sent or for which no alert was sent lt event_list alerting yes gt cleared Lists events for which an alert lt event_list cleared yes gt was Cleared or for which the alert lt event_list cleared no gt was not cleared These parameters can be combined for better filtering In Example 7 15 two filters were combined to limit the amount of information displayed The first parameter max_events allows only five events to be displayed The second parameter is the date and time that the events must not exceed In this case the event occurred approximately 1 5 minutes before the cutoff time Example 7 15 The event_list command
507. raceful shutdown sequence under either of these conditions gt The battery charge remaining in two or more UPS units hits a certain threshold which is conservatively set just above the amount of battery power required to fully destage data from cache to disk and gracefully shutdown the entire system twice gt The system detects the loss of external power for more than 30 seconds Chapter 2 IBM XIV Storage System logical architecture and concepts 47 Power on sequence Upon start up the system verifies that the battery charge levels in all UPS units exceed the threshold necessary to guarantee that a graceful shutdown can occur twice If the charge level is inadequate the system halts the start up process until the charge level reaches the minimum required threshold Important If there is a complete power loss in the data center the XIV automatically powers up when power is reapplied If this is not the behavior you want contact IBM technical support to learn how to disable this feature 2 2 Preserving data redundancy Rebuilding and redistributing As described in Data distribution algorithms on page 23 the XIV Storage System dynamically maintains the pseudo random distribution of data across all modules and disks while ensuring that two copies of data exist at all times when the system reports Full Redundancy When there is a change to the hardware configuration as a result of adding new hardware or a failed component data
508. rage Productivity Center GUI when in fact it is the same size Because the XIV Storage System also provides thin provisioning additional columns for the thin provisioning storage pools were introduced to the Tivoli Storage Productivity Center GUI The Tivoli Storage Productivity Center configured space is equivalent to the XIV Storage System soft capacity and Tivoli Storage Productivity Center real space is equivalent to the XIV Storage System hard space Chapter 7 Monitoring 361 Additional Configured Capacity Limit and Remaining Configured Capacity columns were introduced to report on the hard capacity of a subsystem while the pre existing Consumed Space and Available Space columns now report on the soft capacity of a subsystem in the following reports gt Storage Subsystem list Click Disk Manager Storage Subsystems to view this report gt Storage Subsystem Details Click Disk Manager Storage Subsystems and select a storage subsystem to view this report gt Storage Subsystem Details Click Data Manager Reporting gt Asset By Storage Subsystem to view storage subsystem details gt Storage Subsystem Reports can be created with user specified columns See the following Tivoli Storage Productivity Center GUI menu items Data Manager Reporting gt Asset gt System wide gt Storage Subsystems Data Manager Reporting gt TPC wide Storage Space Disk Space By Storage Subsystem
509. rallelism The system architecture ensures full usage of all system components Any input output I O activity involving a specific logical volume in the system is always inherently handled by all spindles The system harnesses all storage capacity and all internal bandwidth It also takes advantage of all available processing power for host initiated I O activity and system initiated activity such as rebuild processes and snapshot generation All disks processors switches and other components of the system contribute to the performance of the system at all times 1 5 2 Workload balancing The workload is evenly distributed over all hardware components at all times All disks and modules are used equally regardless of access patterns Although applications might access certain volumes more frequently than other volumes or access certain parts of a volume more frequently than other parts the overall load on the disks and modules is balanced perfectly Pseudo random distribution ensures consistent load balancing even after adding deleting or resizing volumes and adding or removing hardware This balancing of all data on all system components minimizes the possibility of a hotspot 1 5 3 Self healing Protection against concurrent double disk failure is provided by an efficient rebuild process that brings the system back to full redundancy in minutes In addition the XIV Storage System extends the self healing concept resuming redundanc
510. rary i ae Subscriptions E EMS Copy Ctrl C a Product Connectors Hi IBM Syste p T0 Internal Connectors Image Lik a ag Resource Pools E Image Lib Export Managerment Fack P i Run As Configuration BG Image Lik X Delete Del 2 Accounts E Image Lib Figure 7 114 Delete the XIV management pack IBM XIV Storage System Architecture and Implementation 3 Import the updated management packs as described in 7 9 3 Importing the management packs on page 381 In Figure 7 115 you can see that Version 1 3 0 0 is imported for IBM System Storage and that both management packs Version 2 1 0 0 are selected for import Select Management Packs Hep Import list eb Add Properties X Remowe Hame Version Release Date Status EULA IBM System Storage A a ee e wf IBM Storage WIV Status details IBM System Storage version 1 3 0 0 ts imported Install Cancel Figure 7 115 Upgrading the management packs 4 Since Version 2 1 you need to define the SCOM management server with the scomu command The syntax for the command follows if you run it on the management server scomu cmd sc set servername localhost 5 Now add the XIV systems again as shown in Example 7 55 on page 380 with the following scomu command scomu add t xiv ip lt ip address gt username lt username gt password lt password gt 7 10 XIV Host Attachment Kit and Host Profiler information This se
511. ration event bind time_limit no 14 Read Only Storage Administrator 30 0 The parameters are as follows base_dn user_id_attrib current_server session cache period bind time_limit The populated values are Base DN which is the parameter that specifies where in the Sun Java Directory DIT a user can be located In our example we use dc xivauth as base DN The LDAP attribute set to identify the user in addition to the user name when recording user operations in the XIV Storage System event log The default value for the attribute is objectSiD which is suitable for Active Directory but not for Sun Java Directory LDAP The objectSiD attribute is not defined in the inetOrgPerson object class used by Sun Java Directory In our example we set it to uid A read only parameter that cannot be populated manually It is updated by the XIV Storage System after the initial contact with the LDAP server is established The duration in minutes that the XIV Storage System keeps user credentials in its cache before discarding the cache contents If a user repeats a login attempt within session_cache_period minutes from the first attempt authentication is done based on the cache content without contacting the LDAP server for user credentials The timeout value in seconds after which the next LDAP server on the Idap_list_ servers is called The default value for this parameter is 0 It must be set to a non zero value in order for
512. rd guides you through the configuration of gateways destinations and rules From the initial Welcome panel click Next or Gateway to open the Events Configuration Gateway window as shown in Figure 7 38 Wizard Events Configuration Gateway x Gateway Add SMTP Email Gateways or SMS gateways Note that you must first define an SMTP gateway before you define an SMS gateway Destination x Define Gateway Rule Finish 6 lt oe Figure 7 38 Define Gateway window 316 IBM XIV Storage System Architecture and Implementation 3 Click Define Gateway The Gateway Create Welcome window that is shown in Figure 7 39 opens Click Next The Gateway Create Select gateway type window opens as shown in Figure 7 39 Wizard Gateway Create Select gateway type Select gateway type SMTP gateways are used to send Email notifications SMS gateways are used to send SMS notifications Type Name SMTP Address Sender Finish p r a p Figure 7 39 Select gateway type 4 When the wizard prompts for the type of the gateway either SMTP for email notification or SMS if an alert or information will initiate an SMS click either SMTP or SMS Gateways An SMTP gateway must be defined before you can define an SMS gateway because SMS messages are sent from the XIV Storage System in the form of an email The next steps differ for SMTP and SMS Our illustration from this point forward is for SMTP
513. rd space in your XIV Storage System you can sum together Unformatted Disk Space and Configured Capacity Limit Because these two values are in binary TB TiB the resulting value does not match the decimal GB value shown for hard space in the XIV Storage Management GUI A simple conversion is to multiply the TiB value shown in Tivoli Storage Productivity Center by 1 0995 to generate a decimal TB value close to the one shown in the XIV Storage Management GUI variations occur because Tivoli Storage Productivity Center rounds the values down Table 7 3 shows the usable hard space in binary TiB that is reported by Tivoli Storage Productivity Center The value varies based on the model of XIV Storage System the size of the drives being used and the number of modules that are physically installed Variation by 0 01 TB might occur due to rounding Table 7 3 XIV total hard space in binary TiB as reported by Tivoli Storage Productivity Center Modules XIV Gen3 with 2 TB XIV Gen3 with 3 TB 93 34 140 88 mooo a aa Storage pools Tivoli Storage Productivity Center can report on XIV Storage System storage pools To assist with this action new Configured Real Space and Available Real Space columns reporting on the hard capacity of a storage pool were added to the Storage Pool Details report This report can be accessed by clicking Data Manager Reporting gt Asset gt By Storage Subsystem lt Subsystem Name gt Storage Pools
514. rd window that is shown in Figure 5 39 on page 203 opens Enter the New Password and then retype it for verification in the appropriate field only alohanumeric characters are allowed Click Update 202 IBM XIV Storage System Architecture and Implementation Change Password System XIV 7826153 Name admin New Password 6 12 S Retype New Password Figure 5 39 XIV GUI Change Password window 5 5 6 Managing multiple systems Managing multiple IBM XIV systems is straightforward in native authentication mode Authorization rule for managing multiple systems Because user credentials are stored locally on every XIV Storage System you must keep the same user name and password on separate IBM XIV systems to allow for quick transitions between systems in the XIV Storage Management GUI This approach is especially useful in Remote Mirror configurations where the storage administrator is required to switch from source to target system Figure 5 40 on page 204 shows the XIV Storage Management GUI view of multiple systems when using non synchronized passwords For this example the systems named XIV 1310133 and XIV 02 131 114 have a user account named lab_admin that provides the storage admin level of access Because the user ID is not configured for the all IBM XIV systems only the two systems are currently shown as accessible The user can see the other system but is unable to access it with the lab_admin user the
515. re For a complete and detailed description of all actions and commands that relate to the flash cache see the Redpaper publication Solid State Drive Caching in the IBM XIV Storage System REDP 4842 4 7 1 Managing flash cache with the XIV Storage Management GUI You can check the health and status of SSDs used for the flash cache in the main system view Moving the mouse cursor over a module displays a pop up panel showing the temperature and status of major module components When SSD disks are present the SSD status is displayed at the bottom of the pop up panel If the SSD is operational a green 0K status is displayed as illustrated in Figure 4 72 Module 5 g3 0_interface Temperature 29 C Status OK Data Service OK Interface Service OK Remote Service OF PSUs OF Fans OK SSD OK Figure 4 72 Module status view with SSD 1 Clicking a module number opens a full perspective view of the module and its components as shown in Figure 4 73 on page 167 From that view you can also check the SSD status If an SSD is installed place the mouse cursor over the SSD in the module view gt SSD is highlighted in green if the status is OK and phased in gt SSD is highlighted in yellow if it is phased out gt SSD is highlighted in red if it failed 166 IBM XIV Storage System Architecture and Implementation Tools Help ih J T Settings A Launch XCLI p Launch XIVTop iew By M
516. re 3 29 on page 91 is more appropriate for benchmarking and higher performance host systems with the highest I O requirements The primary differentiator is the host s ability to handle the higher number of paths per LUN You should not use the configuration in Figure 3 29 on page 91 for most production applications because the host multipathing itself provides enough reliability during path recovery scenarios 90 IBM XIV Storage System Architecture and Implementation Host 1 D Host 2 gt N oD Host 3 Q N gt S lt Host 4 co Host 5 Patch Panel FC Ports SAN Hosts Figure 3 29 Multipathing configuration for larger hosts The following information relates to the configuration that is shown in Figure 3 29 gt Each host is equipped with dual HBAs Each HBA or HBA port is connected to one of two FC switches gt Each of the FC switches has a connection to a separate FC port of each of the six Interface Modules gt Each LUN has 12 paths Each host HBA is physically connected to all six of the XIV Storage System Interface Modules This configuration provides the ability for each HBA to use the maximum available I O capabilities For XIV Storage System each interface module has two 2 port Fibre Channel adapters It is a best practice that each zone is physically connected to one port on each XIV Storage System Fibre Channel adapter For example switch A s zone is connected to port 1 on the I
517. re waiting in the disk queue IBM XIV Storage System Architecture and Implementation 6 3 2 Using XIV Top In addition to the XIV Storage Management GUI performance statistics options you can also use XIV Top for additional and more granular system performance statistics The XIV Top application allows you to view and monitor performance information for defined volumes and hosts in real time There are multiple ways to access the XIV Top utility gt To start XIV Top directly from the GUI desktop right click within the All systems view on the XIV Storage System that you want to monitor See Figure 6 20 v XIV Storage Management max A O Systems Actions View Tools Help A Ausystems 5 gt IOPS 29 225 ATSXIV 10115 IOPS 28 XIV 7820784 XIV 1310062 Dantooine B 68 ts v Connectiviy v XIV 1310062 Dantooine 11 f Add System EZ Add Group 3 0 GZ KIV 131 7 Alba Modify IP Addresses ELCAN Remove System 3 Create A Group Containing This System Suspend Monitoring View Events View Statistics View Storage Pools View Volumes by Pools View Volumes View Hosts IOPS 109 793 View Mirroring View Migration Show Certificate View XIV Connectivity View Migration Connectivity Launch XCLI Copy System Configuration Properties Figure 6 20 Starting XIV Top from the main GUI desktop gt Start XIV Top from the XIV Storage Management GUI desktop Figure
518. rectory Server Indicates required field Parent for example de example de com DN Previous i Figure B 5 Selecting the entry location Cancel Appendix B Additional LDAP information 409 410 The location of all entries for XIV Storage System accounts must be the same because the XIV Storage System has only one LDAP configuration parameter that specifies the location In our example we use dc xivauth as the entry location for XIV Storage System user accounts The location name is the same as the suffix name in this example There are certain similarities between Windows file system and LDAP directory structures You can think of LDAP suffixes as drive letters A drive letter can contain directories but you can also put files onto the root directory on a drive letter In our example we put a new account at the level by analogy of a root directory the dc xivauth location As your LDAP repository grows it might no longer be practical to put types of entries into the same location In this case just like with Windows file system you can create subdirectories and place new entries there The LDAP equivalent of what has become a directory hierarchy in your file system is called the Directory Information Tree DIT After the entry location is selected and the XIV Storage System is configured to point to that location all the new account entries can be created only in that location Select an object class for the new en
519. remaining hard space space not used by volumes or snapshots inside all defined pools in GiB Figure 7 91 on page 363 shows the details for an XIV Storage System as shown in Tivoli Storage Productivity Center Do not use the fields that show the Disk Space Available Disk Space Physical Disk Space Formatted Space and Formatted Space with No Volumes Although values are shown for some of these fields the methods used to calculate them do not apply well to the XIV Storage System They are used for other storage products 362 IBM XIV Storage System Architecture and Implementation Detail for Storage Subsystem lt X1 Fest Group Manufacturer Model Serial Number Firmware Revision Number of Disks Disk Space Available Disk Space Physical Disk Space TPCUser Subsystem Standard Group IBM 114 fo20119 11 1 0 RC1 p20120213_094716 106 193 49 TE 141 61 TE 193 49 TE Formatted Space 56 67 TB Formatted Space with No Yolumes 47 44 TE Overall Unavailable Disk Space Mid Unformatted Disk Space 23 07 TB Configured Capacity Limit 56 67 TB Remaining Configured Capacity 31 57 TB Sumber of olumes 630 Yolume Space 20 34 TB Backend Yolume Space oO Last Probe Time Mar 1 2012 1 15 40 PM Last Probe Status Succeeded Probing 4gent xivexe 1 Figure 7 91 XIV Storage System details shown in Tivoli Storage Productivity Center The remaining fields in Figure 7 91 show the following information Unformatted Disk Space Th
520. rent host logins FC adapter Maximum number of concurrent host logins Interface Module ee Oo ee Maximum FC ports for host connections default configuration Oo w Maximum number of concurrent host logins 15 Module XIV 2000 Maximum number of hosts ports defined WWPN IQNs 4000 Figure 3 26 Fibre Channel parameters Values in Figure 3 26 apply to Version 11 4 of the XIV Storage System software iSCSI connections The external client provided Ethernet cables Model 114 and Model 214 1 GbE or optical cables model 214 10 GbE are plugged into the patch panel For planning purposes highlight the maximum values for various iSCSI parameters for your consideration As with Fibre Channel it is important to plan your connectivity based on these maximums Maximum values iSCSI parameters Modell 114 Model 214 1 GbE Model 214 10 GbE Maximum number of Interface Modules with iSCSI ports Maximum number of 1 GB iSCSI ports Interface Module 4 only have 2 ports Maximum number of 10 GB iSCSI ports Coa oOo o Maximum number of hosts ports defined WWPN IQNs 4000 4000 4000 Figure 3 27 iSCSI parameters 12 These values are correct at the time of writing this book for Version 1 4 of the XIV Storage System software Chapter 3 IBM XIV architecture components and planning 89 Host multipathing There are two main multipathing techniques For both multipathing configurations each host engages the I O services of ever
521. rformance monitor is automatically submitted 4 If you want to review or change the sampling and scheduling select the performance monitor click Disk Manager gt Monitoring gt Subsystem Performance Monitors and click Sampling and Scheduling as seen in Figure 7 88 Disk Manager Storage Subsystems Sampling and Scheduling alert Storage Subsystems Sampling F Storage Optimizer HSAN Planner Monitoring Interval length Gathered performance data will represent averages over this interwal Groups Gather data every S minutes Advanced fe J obs Sub f BE En Duration ee m Continue gathering data For p Hours Ebilerting Continue indefinitely amp Profile Management Reporting Scheduling Figure 7 88 Performance Monitor details 360 IBM XIV Storage System Architecture and Implementation Configuration information and reporting Figure 7 89 shows a list of various XIV Storage System subsystems as reported in Tivoli Storage Productivity Center IBM Tivoli Storage Productivity Center sspc sle 1 Storage Subsystems File View Connection Preferences Window Help Element Management s B a x 2 avigation Tree Storage Subsystems Administrative Services IBM Tivoli Storage Productivity Center Add Storage Subsystem volumes Data Manager Data Manager for Databases Launch Element Manager Data Manager for Chargeback Storage Subsystems
522. rformance monitoring is a probe job of the storage subsystem Detailed information on probe jobs can be found on the Disk Manager tab in the Storage Subsystem Probes section Storage subsystem performance function is only available with certain IBM Tivoli Storage Productivity Center packages See the User Guide For details fe FR AE FE RE A a Detailed information about CIM Agents is found on the Services tab CIMOM Discovery Storage Subsystem Probes Storage Subsystem Performance Management Alerting Figure 7 85 Disk Manager tab If you want to modify the probe you created click IBM Tivoli Storage Productivity Center gt Monitoring gt Probes and choose the correct group in our case Subsystem Standard Probe Click When to Run to adjust the schedule or Alert if you want to modify the alerts as shown in Figure 7 86 IBM Tivoli Storage Productivity Center sspc sle 1 Edit Probe e View Connection Preferences Window Help Element Management Administrative Services IBM Tivoli Storage Productivity Center Configuration Utility Configure Devices Job Management Reporting Topology Monitoring Probes TPCUser Computer Advanced Probe TPCUser Computer Basic Probe TPCUser Computer Standard Probe TPCUser Default Probe TPCUser Fabric Advanced Probe gt TPCUser Fabric Basic Probe TPCUser Fabric Standard Probe
523. ries in which they were intended to be used 981 1 9890 Line cord for United States Canada Latin Hubbell Hubbell Hubbell America and Japan with plug single phase HBL360P6V04 HB L360 RW HBL 360C6W 60 A two wires ground 9813 9890 Line cord for EMEA and Asia Pacific except Hardwired or Not applica ble Not applicable Japan hard wired single phase 60 A two wires uses client ground provided connector 9820 9891 Line cord for United States Canada Latin Hubbell Hubbell Hubbell America and Japan with plug three phase 60 A HBL460P9V05 HBL460 R9W HBL460C9W three wires ground 9822 9892 Line cord for EMEA and Asia Pacific except Hardwired or Not applicable Not applicable Japan hard wired three phase 30 A three uses client wires neutral ground provided connector 9824 9894 Line cord for United States Canada Latin Hubbell Hub bell Hubbell America and Japan with plug three phase 30A HBL430P9V04 HBL430R9W HBL430C9W three wires ground Note Line cords are provided with the connector part numbers shown Receptacle part numbers shown are recommended Although equivalentreceptacles can be used itis the responsibility of the customer to verify compatibility Figure 3 11 Power cord features For more information about the appropriate ATS and power cord selection see the BM XIV Storage System Gen3 Models 281x 11x and 281x 21x Planning Guide SC27 5412 Chapter 3 IBM XIV architecture components and planning 71
524. ring through the exploded drawing as seen in Figure Figure 7 22 PSU 1 m Status OK interface Module 9 Status Figure 7 22 Component status in module explosion drawing Hover over a component to show the actual status of the single component in the module The example in Figure 7 22 shows the status of PSU 1 The status and temperature of the module can be inspected also in this view Click the thermometer to toggle between Celsius C and Fahrenheit F If a module s temperature exceeds a default threshold a small yellow or red triangle is displayed to indicate that the module temperature is higher than normal as shown in Figure 7 23 Figure 7 23 Module temperature threshold exceeded If you hover your cursor over a disk the status and temperature of the disk are shown Figure 7 24 on page 297 296 IBM XIV Storage System Architecture and Implementation Disk 11 Module 10 Capacity 3TB Temperature 32 C Status OK Figure 7 24 Disk status and temperature Deferred disk replacement XIV Storage System Gen3 has the concept of deferred disk replacement which means that up to two failed disks can be marked for replacement later If a third disk or another component fails the XIV Storage System notifies IBM to replace all the failed components at the same time A disk that has been placed into a deferred replacement state will not be red in color but a shade of pink as shown in Figur
525. ritten to the disk drive The data in cache that must be written to disk within each module consists of equal parts primary and secondary copies of data but never contains both primary and secondary copies of the same data Write cache protection Each module in the XIV Storage System contains a local independent space reserved for caching operations within its system memory Destage The system memory space is reserved for write operations However the close proximity of the cache and the disk drives with the enforcement of an upper limit for data that has not been destaged enforced on a per drive basis ensures that the full destage occurs while operating under battery power Important The extended flash cache layer is non volatile memory and all data in flash cache is protected for either scheduled or non scheduled system shutdown The XIV Storage System does not use flash cache for write All write I Os are staged and mirrored out of main cache only DRAM layer The writes are flushed from main cache to the disk drive layer as part of the normal write destaging However on shutdown the primary cache DRAM related metadata is dumped to the flash cache Upon the next XIV Storage System start up the metadata is read back and validated for correctness For more information see the Redpaper publication Solid State Drive Caching Implementation in the IBM XIV Storage System REDP 4842 Shutdown trigger events The system executes the g
526. rives TB TB TB TB TB TB Net capacity with 3 TB disk 84 132 154 168 190 203 drives TB TB TB TB TB TB Net capacity with 4 TB disk 112 177 207 225 254 272 drives TB TB TB TB TB TB Note The system defines capacity by using decimal metrics One GB is 1 000 000 000 bytes using decimal metrics By contrast 1 GiB is 1 073 741 824 bytes using binary metrics The XIV Storage System reserves physical disk capacity for gt Global spare capacity gt Metadata including statistics and traces gt Mirrored copies of data 30 IBM XIV Storage System Architecture and Implementation Global spare capacity The dynamically balanced distribution of data across all physical resources by definition eliminates the need of dedicated spare drives that are necessary with conventional RAID technologies Instead the XIV Storage System reserves capacity on each disk drive to provide adequate space for the redistribution or rebuilding of redundant data in the event of a hardware failure This global spare capacity approach offers advantages over dedicated hot spare drives which are used only upon failure and are not used otherwise therefore reducing the number of spindles that the system can use for better performance Also those non operating disks are not typically subjected to background scrubbing processes In XIV all disk drives are operating all the time and are subject to examination which helps detect potential reliability issues with drives The
527. roductivity Center 0 0 00 353 7 6 1 Setting up and discovering XIV systems in Tivoli Storage Productivity Center V Z OM IAL uasai ei eG kts Gee acin ah Aah he eee ee E de eee ets Be 354 7 6 2 XIV Storage System Tivoli Storage Productivity Center reports 361 7 7 Tivoli Storage Productivity Center web based GUI 0 0000 c eee 368 7 0 CUSO MONON essas aean Soe rere a ETAT Eh od Rae Deer eG alates 371 7 8 1 Custom monitoring of a volume 0 0 eee 372 7 8 2 Custom monitoring of performance attributes 0 0 0 eee eee 375 7 0 3 GONCIUSION a5 amp cence one ena 6 ioe ee oe Ca ae SI ae oss oS Oe ew oe Sea 377 7 9 Microsoft System Center Operations Manager 00 cee eee eee 378 7 9 1 PrereguiSileS regire aban eee atte S on BS Seba dais See ease eee tee 378 7 9 2 Installing SCOM and the IBM Storage Management Pack 379 7 9 3 Importing the management packS 00 ees 381 7 9 4 Configuring the SCOM Management Pack 0000 e eee eee eee 383 7 9 5 Monitoring your XIV Storage System with SCOM 0000 eee 385 7 9 6 Upgrading the IBM Storage Management Pack 00000 eee 388 7 10 XIV Host Attachment Kit and Host Profiler information 00005 389 7 10 1 XIV Host Attachment Kit overview 0 00 cee ens 390 IBM XIV Storage System Architecture and Implementation Pose AV IOSE Fel OMe brec ts tees tates crat hat amp
528. roup is 12 gt The maximum number of managed systems is 144 Important You are advised to use Hyper Scale Manager when managing more than 40 IBM XIV systems For more information see the IBM Redpaper BM Hyper Scale in XIV Storage REDP 5053 It is possible to control more than 144 XIV Systems on a single workstation by creating another user profile and starting another instance of the GUI gt Using multiple profiles for accessing a different set of systems from the same workstation Access each profile by a command line switch where lt user_dir gt is the profile name Xivgui exe h lt user_dir gt Multiple instances of the GUI can be opened each with a different profile Figure 5 42 which can be useful for the following purposes e Managing more than 144 XIV Systems e Managing different XIV systems using different credentials Each profile has its own list of managed systems IBM XIV GUI Properties General Shortcut Compatibility Security giv IBM XIV GUI Target type Application Target location XIVGUI Target orage AW AIVGUPaxdvguiexe i c gt User _A Start in C Program Files BM Storage AIVAIVGLU Comment Figure 5 42 User profile for Multi System Management Chapter 5 Security 205 5 6 LDAP based authentication The XIV Storage System offers the capability to use LDAP server based user authentication When LDAP authentication is enabled the XIV Storage System accesses
529. rovide just the default fields as a result To list the field names for a specific xcli command use the t parameter as shown in Example 4 7 Example 4 7 XCLI field names c Users itso gt xcli c XIV2 t name fields help command user_list Scripts XIV Storage Management software XCLI commands can be used in scripts or batch programs if you need to use repetitive or complex operations The XCLI can be used in a shell environment to interactively configure the system or as part of a script to perform specific tasks as shown in Example 4 3 on page 134 In general the XIV Storage Management GUI or the XCLI Session environment virtually eliminate the need for scripts 4 4 Storage pools We introduced the concept of XIV storage pools in 2 3 4 Storage pool concepts on page 31 Chapter 4 IBM XIV Storage Management software 135 4 4 1 Function of storage pools Storage pools manage a related group of logical volumes and their snapshots Storage pools offer the following key benefits gt Improved management of storage space Specific volumes can be grouped within a storage pool giving you the flexibility to control the usage of storage space by specific applications a group of applications or departments gt Improved regulation of storage space Automatic snapshot deletion occurs when the storage capacity limit is reached for each storage pool Therefore when a storage pool s size is exhausted only the snapshots that are i
530. ructured in a way to provide output during a custom window of time In Example 7 52 we gather data from every minute during a 24 hour period on the previous day that the script is run Example 7 52 Limiting the output of XCLI commands using the t option var Command statistics get count 1440 interval 1 resolution unit minute t write hit_medium_ latency end EndDate In Example 7 53 each resulting value is compared to the threshold If any one of them exceeds the value it sets a flag to be used to generate a custom event Example 7 53 Looping through the XCLI command output while oExec StdOut AtEnd0fStream Stringl oExec StdOut ReadLine n Stringl Stringl replace s s g if Stringl length 0 continue 376 IBM XIV Storage System Architecture and Implementation strChar Stringl charAt 0 if strValidChars indexOf strChar 1 continue if Stringl gt Threshold Exceeded 1 In Example 7 54 we see again how to generate a custom event when our wanted threshold is exceeded Example 7 54 Using XCLI to generate a custom event if Exceeded Command custom event description Medium Latency exceeded threshold of Threshold during 24 hour period ending EndDate severity Severity After running this script you can see the custom event in the XIV Storage System event log as shown in Figure 7 105 After running this script a custom event is generated if the write
531. running older versions are strongly encouraged to upgrade to Version 4 3 or later 4 2 1 XIV Storage Management GUI and XCLI software upgrade 106 If a previous version of the XIV Storage Management GUI is installed it is best to uninstall the existing version before installing the newer version The existing IBM XIV systems profile file which is a list of defined IBM XIV systems and groups is not deleted after the older version is uninstalled This file is then recognized by the new installed version You can save the local IBM XIV systems profile file by exporting it from the XIV Storage Management GUI as shown in Figure 4 2 It is saved as an XML file and is then available for importing into the newly installed XIV Storage Management GUI which overwrites the existing systems profile Tip The saved IBM XIV systems profile can be imported on extra systems on which the XIV Storage Management GUI is installed to ensure an identical systems view across all installations ire View Tools Help A p Shutdown System Import Systems File Export Systems File Modify IP Addresses Exit Figure 4 2 Export file IBM XIV Storage System Architecture and Implementation 4 2 2 XIV Storage Management software installation steps for direct use In this section we describe the GUI installation procedure and its usage for a direct connection to the XIV systems Important The minimum requirements for installing the XIV Storag
532. ry that stores typed and ordered information about objects A particular directory might list information about users the objects consisting of typed information such as user names passwords and email addresses Directories allow users or applications to find resources that have the characteristics needed for a particular task Directories in LDAP are accessed by using the client server model An application that wants to read or write information in a directory does not access the directory directly but uses a set of programs or application programming interfaces APIs that cause a message to be sent from LDAP client to LDAP server An LDAP server retrieves the information requested on behalf of the client application and returns the requested information if the client has permission to see the information LDAP defines a message protocol used between the LDAP clients and the LDAP directory servers This protocol includes methods to search for information read information and to update information based on permissions 5 6 2 LDAP directory components An LDAP directory is a collection of objects organized in a tree structure The LDAP naming model defines how objects are identified and organized Objects are organized in a tree like structure called the Directory Information Tree DIT Objects are arranged within the DIT based on their distinguished name DN Distinguished name defines the location of an object within the DIT Each object is
533. s IBM Storage Common mp IBM Storage XIV mp 3 When the files are selected click Open The Import Management Packs window now lists the Management Packs to be added 4 Click Install to start the import as shown in Figure 7 109 When the Management Packs are successfully imported click Close Select Management Packs Help Import list s Add Properties XK Remove Name Version Release Date Status EULA J IBM Storage XIV Status details This management pack is ready to import Figure 7 109 Install the Management Packs 382 IBM XIV Storage System Architecture and Implementation You have now imported the Management Packs into SCOM 7 9 4 Configuring the SCOM Management Pack SCOM monitors various different constructs such as alerts events systems and components Each construct has a data collection interval that ranges from 300 seconds to 1800 seconds the time varies based on the construct This situation means that if you add an XIV Storage System to SCOM using the scomu add command there might be a delay before the XIV Storage System is displayed in any of the views Changing the default discovery intervals To change the default discovery intervals complete the following steps 1 In the left pane of the Operations console click Authoring Management Pack Objects Object Discoveries 2 Click XIV Configuration Discovery right click and click Overrides Override the Ob
534. s Switches and Subsystem Netware Filer Windows Domain NAS al Mware YI Data Source Configuration TBM Tivoli Storage Productivity Configuration Utility a onfigure Devices Job Management Figure 7 80 Configure Devices wizard The discovery usually takes a few minutes and can be run on a schedule How often you run a discovery depends on the dynamic of your environment It must be run to detect a new subsystem and to perform basic health checks of all CIMOMs and other storage subsystems Tivoli Storage Productivity Center configuration wizard To use the Tivoli Storage Productivity Center wizard complete the following steps 1 Click IBM Tivoli Storage Productivity Center Configure Devices to start the wizard 2 Click Storage Subsystem and click Next 3 Click Add and configure new storage subsystem and click Next 4 Click IBM XIV as the Device Type and enter the required information IP Address For the XIV Storage System this address corresponds to the three management IP address of the XIV Storage System Start with the first IP address Username The XIV Storage System user that is created for Tivoli Storage Productivity Center Password The password of the XIV Storage System 5 Click Add and complete step 4 for the other IP addresses as shown in Figure 7 81 on page 357 356 IBM XIV Storage System Architecture and Implementation E Configure Devices Configure storage subsystem connect
535. s In that case you can select one of these options Enable Flash cache is enabled for the selected volume Disable Flash cache is disabled for the selected volume Tip The overall System Status Setting for the SSD Caching is shown in parentheses You can select more than one volume in the Volumes and Snapshots view if you need to change the SSD Caching State for a list of volumes Flash cache performance statistics The Performance Statistics view is updated to reflect flash cache On GUI 4 0 some new metrics have been added for Read I O gt Mem Hit Metrics for read I O Main cache gt SSD Hit Metrics for read I O Extended SSD cache Chapter 4 IBM XIV Storage Management software 169 The graphic in Figure 4 78 shows a common trend when you enable flash cache Total Memory Hit red line is going up because of flash cache Meanwhile Read Miss blue line is going down Flash cache Hit purple line is going up side by side with Total Memory Hit hsv XIV Storage Management x File View Tools Help A 9 xiv_development All Systems View By My Groups Statistics System Time 07 21pm Q All Interfaces oy Hit Miss Memory Hit SSD Hit Hit Miss D 1OPS Read 4 50 000 45 000 5 th 40 000 5 a 16 02 12 19 10 35 000 g Hit Miss 1OPS 49134 30 000 SSD Hit 10PS 19265 Memory Hit IOPS 17562 7 Miss IOPS 12307 iaaii i i IOPS 36827 gt 09 20 000 F 15 000 10 000 5
536. s and planning 97 SMTP server For correct operation of the XIV Storage System call home function the SMTP server must function as follows gt Be reachable on port 25 for the XIV Storage System client specified management IP addresses gt Allow relaying from the XIV Storage System client specified management IP addresses gt Allow the XIV Storage System to send emails The default sender address is fromxiv il ibm com but this address can be changed gt Allow recipient addresses of xiv cal home western hemisphere vnet ibm com and xiv cal lhome eastern hemisphere vnet ibm com Additionally you can choose the shorter alias recipient address xiv west vnet ibm com and xiv east vnet ibm com 3 2 4 IBM XIV Storage System physical installation After all previous planning steps are completed and the system is delivered to its final location the physical installation can begin An IBM SSR completes all the necessary tasks and the first logical configuration steps up to the point where you can connect the IBM XIV Storage System through the XIV Storage Management GUI and the XCLI Configuring storage pools logical unit numbers LUNs and attaching the XIV Storage System to the host are storage administrator responsibilities See Chapter 4 IBM XIV Storage Management software on page 103 for more information Physical installation It is the responsibility of the client or moving contractor to unpack and move the XIV Storage Sys
537. s as shown in Example 5 15 Example 5 15 user_list command output in LDAP authentication mode gt gt user_list show_users al Name Category Group Active Xiv_devel opment Xiv_devel opment yes Xiv_maintenance Xiv_maintenance yes admin storageadmin yes technician technician yes GPreadonly readonly no gt gt ldap mode get Mode Active gt gt 230 IBM XIV Storage System Architecture and Implementation As shown in Example 5 15 on page 230 the Active parameter is set to no for the GPReadonly user The parameter specifies whether a user can log in to the current authentication mode All predefined local XIV Storage System users can still log in when LDAP authentication mode is active Defining user groups with the XIV Storage Management GUI in LDAP authentication mode User group information is stored locally on the XIV Storage System regardless of the authentication mode The user group concept applies only to users assigned to an application_administrator role A user group can also be associated with one or multiple hosts or clusters To create user groups add users with application administrator role to the group and define host associations for the group complete the following steps 1 Be sure to log in as admin or another user with storage administrator rights From the Access menu click Users as shown in Figure 5 71 In our scenario we create a user group called itso app01 group The user groups can be
538. s for redundancy of the XIV Storage System in the IP Host name fields Click Add to add the system to the XIV Storage Management GUI See Figure 4 9 Add Managed System System Group Ungrouped Systems IP Host name 1 IP Host name IP Host name 3 Connect Directly Add Cancel Figure 4 9 Add Managed System window Chapter 4 IBM XIV Storage Management software 111 Tip XIV System software 11 1 and later support IPv6 addressing for the XIV Storage System management ports For information about configuring IPv6 see 5 3 Configuring IPv6 addresses on page 182 Tip If the workstation is correctly configured for Domain Name Service DNS resolution host names can be used Important The Connect Directly check box is for an IBM service representative to use to connect their notebook to the XIV through the two notebook ports on the patch panel This option must not be used by general GUI users 3 The XIV Storage Management system view window opens as shown in Figure 4 10 Further administrative actions can be taken XIV Storage Management File View Tools Hep O f Add system JIL Add Group XIV LAB 03 1300 XIV PFE GEN3 G2 Settings Launch XCLI Launch XIVTo A Y 5 5 r XIV 02 1310114 69 CZE System System Time 02 10 pm Selecting the desired IBM XIV Storage System from the All Systems view transitions the Main Window to the System view Figure 4 10 XIV foreground Storage
539. s Next Figure 4 3 Installation Introduction window 2 The window prompts you to accept the IBM License Software Agreement Read the license select accept both the IBM and the non IBM terms and click Next to proceed Chapter 4 IBM XIV Storage Management software 107 108 3 The installation window that is shown in Figure 4 4 is where the installation directory is specified Enter an installation location or proceed with the default location provided Click Next to proceed E IBM XIV Storage Management GUI gt E mE Choose Install Folder Introduction License Agreement Please choose a destination folder for this installation Configure Installation Pre Installation Summary Installing Where would you like to install Program Files IBM Storage Ivi sI aUI Restore Default Folder Choose InstallAnywhere Cancel Previous Figure 4 4 Choose the installation directory For new installations or if installing in a new directory and a previous GUI installation exists a program shortcut called IBM XIV 4 3 is created in the Start Menu folder In addition three optional desktop icons are created as indicated in Figure 4 5 If you choose to install into a folder that already contains an installation of the GUI this dialog is skipped Therefore click Next to proceed FA Teh XIV Storage Management GUI o mee Choose Shortcuts Folder w Introduction Setup wi
540. s Server Configuration ii Add Remove or modify your Directory Services servers If you plan on using Server Type Secure LDAP please make sure you attach the appropriate LDAP Server certificate pem format for each server you configure LDAP Servers Add LDAP Server XIV User Unique ID s Groups Secure LDAP Bind amp Cache Test amp Activation Finish Figure 5 50 Adding LDAP servers 214 IBM XIV Storage System Architecture and Implementation 5 8 In the window that opens Figure 5 51 enter the fully qualified domain name FQDN which is the DNS name of the LDAP server such as itso storage ibm com in our example Also enter the LDAP server IP address and the Search DN which in our Active Directory implementation is CN Users DC itso DC storage DC ibm DC com as shown in Figure 5 51 For example in a default Active Directory implementation a server with the domain name ldap domain de maps to CN Users DC ldap DC domain DC de If you need a certification file for the connection to your LDAP server add it here for the connection If your LDAP server uses nonstandard port numbers enter those accordingly Leave these fields blank to use the standard ports Server port 389 secure server port 636 Click Create to save the settings Define LDAP Server FODH itso storage ibm com Server Address 9 155 113 143 Search DW ij eN Us ers DC itso DC stor
541. s and create the gateway or cancel and discards all Sateen changes in this wizard Type Gateway Name ITSO Mail Gateway Address Gateway Type SMTP Gateway Address au ibm com Sender Email xiv01 yourcompany com au iii n as kaw oe Figure 7 41 Create the Gateway Summary 7 Review the information you entered on this window If all is correct click Create If not click Back until you are at the information that needs to be changed Or select the buttons on the left to take you directly to the information that needs to be changed Next the Events Configuration wizard guides you through the setup of the destinations where you configure email addresses or SMS receivers Figure 7 42 on page 319 shows the Destination window of the Events Configuration wizard 318 IBM XIV Storage System Architecture and Implementation Wizard Events Configuration Destination Destination Add Destinations smnp email sms or group of destinations objects eT Rule x Create Destination Finish Figure 7 42 Add Destination window 8 Click Create Destination to open the Welcome window Then click Next to proceed The Select Destination type window opens as shown in Figure 7 43 On this window you configure the following settings Type Event notification destination type can be either a destination group containing other destinations SNMP manager for sending SNMP traps email address for
542. s available with HAK 1 7 and later Portable HAK can be used in three different ways gt Locally on a host Download and unpack on your local host gt Centrally from a network drive Download and unpack to a network drive gt From a portable USB flash drive Download and unpack to a USB flash drive To use the portable HAK download the zip or tar gz file according to your operating system and unpack the file depending on the method that you want to use See the example for Windows a shown in Figure 7 117 on page 392 Chapter 7 Monitoring 391 fix pack IBM_XIV_Host_Attachment_Kit_for_Windows_v2 0 0 IBM XIV Host Attachment Kit for Windows Version 2 0 0 The following files implement this fix 4 IBM 2 0 0 HAG pdf IBM_XIV_HAK_for Windows 2 0 0 RN_pdf 4 IBM_XIV_Host_Attachment_Kit_2 0 0 b1530_Windows x64_exe 4 IBM_XIV_Host_Attachment_Kit_2 0 0 b1530 Windows x64_portable zip 4 IBM_XIV_Host_Attachment_Kit_2 0 0 b14 aN 4 IBM_XIV_Host_Attachment_Kit_2 0 0 b1 Open Link in IE Tab gt Open Link in New Window Bookmark Thijs Link Save Link As Copy Link Location Share with E mail Burn New folder q fil A Name Date modified fs HAK and Xhop pptx 22 03 2013 10 30 HAK2 0_xhop ppt 22 03 2013 10 30 IBM_XIV_HAK_2 0 0_HAG pdf 22 03 2013 10 40 IBM_XIV_HAK_for_Windows_2 0 0_RN pdf 22 03 2013 10 40 22 03 2013 14 40 1 IBM XV Hort te een ee ne
543. s produce an event that looks similar to the event that is shown in Figure 3 13 Event Properties Severity Informational Date 2011 06 04 13 22 71 Index 3644 Event Code UPS CALIBRATION STARTED T Shooting Description UPS manual calibration started for 1 UPS 1 Figure 3 13 UPS calibration 3 1 7 Data Modules and Interface Modules The hardware of the Interface Modules and Data Modules in the IBM XIV Gen is based on an Intel server platform that is optimized for data storage services A module is 87 9 mm 3 46 inches 2U tall 483 mm 19 inches wide and 707 mm 27 8 inches deep Figure 3 14 on page 74 shows a representation of the inside of a Data Module Chapter 3 IBM XIV architecture components and planning 73 Redundant power supplies InfiniBand CPU AA Clack FENS 7 v i wate A y gj 2 JPeaaaeee Fans oe Figure 3 14 Data Module 1 ai re ee Both the Data and Interface Modules on XIV Storage System Gens contain the following hardware features gt System board with a PCle 2 0 bus with the following management ports Figure 3 15 on page 75 RS 232 serial port USB port one used three unused Two Gb Ethernet ports gt Quad core or six core processor gt Memory gt SAS host bus adapter HBA gt SAS disk drives gt InfiniBand host channel adapter gt SSD slot see Figure 3 15 on page 75 gt Fan bank gt Memory flash card see Figure 3 15 o
544. s reach 80 failing message sent gt Minor Power supply power input loss volume usage over 90 and component TEST failed gt Major Component failed disk user system shutdown volume and pool usage 100 UPS on battery or Simple Mail Transfer Protocol SMTP gateway unreachable gt Critical Module failed or UPS failed Event codes For a list of event codes see the BM XIV Storage System User Manual GC27 3914 Event types The following event types can be used as filters specified with the object_type parameter in the XCLI command cons_group Consistency group destgroup Event destination group dest Event notification group dm Data migration host Host map Volume mapping mirror Mirroring pool Pool rule Rule smsgw SMS gateway smtpgw SMTP gateway target FC iSCSI connection volume Volume mapping cluster Cluster Vvvvvvvrvrvrvrvvviyvy siy Chapter 7 Monitoring 305 ip_interface IP interface ldap_conf LDAP configuration meta_data_object Metadata events sync_schedule Schedules user User user_group User group ldap_server LDAP server modules_status Modules status Vvvvvvvyyv Yy 7 1 8 Viewing events using the XCLI Table 7 2 provides a list of all the event related commands available in the XCLI This list covers setting up notifications and viewing the events in the system For a more in depth discussion of system monitoring see Chapter 7 Monitoring on page 285 Table
545. s that any read operation results in returning all zeros as a response To create volumes with the XIV Storage Management GUI complete the following steps 1 Click the Add Volumes icon in the Volume and Snapshots view see Figure 4 54 on page 149 or right click in the body of the window not on a volume or snapshot and click Add Volumes The window that is shown in Figure 4 56 opens Create Volumes Select Pool VMW UNMAP 8 466 GB Allocated i Number of Volumes 1 Volume Size 17 Volume Name Figure 4 56 Create Volumes view 2 From the Select Pool field select the pool where this volume should be stored See 4 4 2 Managing storage pools with the XIV Storage Management GUI on page 137 fora description of how to define storage pools The storage size and allocation of the selected storage pool is shown textually and graphically The blue portion of the bar indicates the space already allocated in this storage pool The shaded portion of the bar outlined with a rectangular size indicator indicates the space that will be allocated to this volume or volumes after it is created The remaining gray portion of the bar indicates the space that remains free after this volume or volumes is allocated 3 In the Number of Volumes field specify the required number of volumes Chapter 4 IBM XIV Storage Management software 153 4 Inthe Volume Size field specify the size of each volume to define The
546. s the details of the new certificate as shown in Figure 5 10 Click Trust Always to trust this certificate for all future connections Certificate Details This security certificate is not trusted You can trust this certificate for this session only Trust Once or always Trust Always Status Issuedto Issued by Validity Details eit nee e IE Not trustee xivhost xiveA from Mar 25 2013 to Apr 24 2013 Show Details EE p Figure 5 10 Certificate Details window The certificate error is resolved and you are now able to securely connect to this system from the GUI using your own x509 certificate Chapter 5 Security 181 Note The XIVTop tool uses the same certificate store as the XIV GUI Trusting a certificate in the GUI means that the XIVTop tool will also trust that certificate 5 3 Configuring IPv6 addresses The use of IPv6 addressing for XIV Storage System management and virtual private network VPN ports is supported by XIV Storage System software Version 11 1 and later To use IPv6 addressing you must first enable it on the XIV Storage System 5 3 1 Enabling IPv6 support In the GUI navigate to the System view of the chosen XIV Storage System and click Systems System Settings System to open the System panel then click the Parameters tab as shown in Figure 5 11 KIV 7626153 Settings General iSCSI Name iqn 2005 10 com_xivstorage 026153 Time Zo
547. same user names registered in local and LDAP repositories If a user account was registered in the local repository on the XIV Storage System before the LDAP authentication mode was activated this account is accessible while LDAP authentication is in effect The account becomes accessible again upon deactivation of the LDAP authentication mode IBM XIV Storage System Architecture and Implementation LDAP user passwords User passwords are stored in the LDAP repository when the XIV Storage System is in LDAP authentication mode Password management becomes a function of the LDAP server The XIV Storage System relies entirely on the LDAP server to provide password management functionality such as enforcing initial password resets password strength and password expiration Various LDAP server products provide their own sets of tools and policies for password management Figure 5 67 shows a technique that can be used for password management E Local Security Policy OF x File Action View Help e iz Security Settings El Ca Account Policies a Enforce password history 8 passwords remembered H Maximum password age 120 days a Minimum password age 1 days H Minimum password length 8 characters Ca Account Lockout Policy Ca Kerberos Policy pee ole ia Password must meet complexity requirements Enabled ett ie ED a Securty H Store passwords using reversible encryption Disabled etwork List Manager Policies Public Key Pol
548. se Agreement Storage Management GUI Configure Installation Itis strongly recommended that you quit all programs before Pre Installation Summary continuing with this installation Installing Click the Met button to proceed to the next screen Ifyou want to change something on a previous screen click the Previous button You may cancel this installation at any time by clicking the Cancel button XIV InstallAnyvwhere Cancel Previous Mert Figure 4 7 Completing the setup 4 3 XIV Storage Management software usage Now that the XIV Storage Management software has been installed the introduction and explanation of some features of the XIV Storage Management GUI and XCLI can be useful in further configuration and storage management Chapter 4 IBM XIV Storage Management software 109 Beginning with the XIV Storage Management GUI this section describes the following topics gt Signing into the XIV Storage Management GUI gt Connecting to IBM XIV systems gt Overview of the management and system views gt Review of XIV Storage Management GUI features Next moving to the XCLI the following topics are described Launching the XCLI XCLI Session features Customizing the XCLI environment Using XCLI help M vy y 4 3 1 XIV Storage Management GUI used in direct mode The XIV Storage Management GUI is a multi function tool for individually managing one or more IBM XIV systems This secti
549. se systems Detect XIV volumes or LUNs Report IBM XIV systems and volumes accessible from the host Perform data collection to analyze problems 390 IBM XIV Storage System Architecture and Implementation Starting with HAK 1 7 two different versions are available gt The installable and executable version Installs all the folders on the host and extract files Creates paths and links Sets environmental variables Contains installation files for the installable HAK that are either exe Windows or tar gz AIX Linux HP UX or Solaris gt The portable version Unpacks to any drive directory and does not require that you install it on the XIV attached host No need to set any environmental variables Functions such as xiv_diag and xiv_host_profiler are frequently updated based on interoperability requests and IBM System Storage Interoperation Center SSIC updates Different HAK versions that can be used on the same host Multiple hosts that can access HAK on a shared drive mount For more details see Portable XIV Host Attachment Kit on page 391 The download page for HAK versions is on the Fix Central website http www 933 ibm com support fixcentral Also see the IBM System Storage Interoperation Center SSIC at the following website http www 03 ibm com systems support storage ssic interoperability wss Portable XIV Host Attachment Kit A portable HAK version i
550. selected from the Access menu padlock icon Figure 5 71 Select user groups 2 Inthe User Groups window to add a user group either click the Add User Group icon shown in Figure 5 72 in the menu bar or right click in an empty area of the User Groups table and select Add User Group from the menu Fa g xiv XIV Storage Management p a Systems Actions View Tools Help ih 3 Ada User 3 Ada User Group g ANSystems 8 gt Tucson Lab 3 gt Users Q E ee 1 OT Name Category Phone Ungrouped Add User Add User Group Configure LDAP LDAP Wizard sue Export a Figure 5 72 Add User Group selection Chapter 5 Security 231 3 In the Add User Group window enter a meaningful group name specify a role for LDAP role mapping as described in 5 6 4 LDAP role mapping on page 208 and click Add Figure 5 73 To avoid potential conflicts with already registered user groups the XIV Storage System verifies the uniqueness of the group name and the role If a user group with the same name or the same role exists in the XIV Storage System repository the attempt to create a user group fails and an error message is displayed Add User Group System XIV 1310062 Dantooine 7 Name LDAP Role Full Access Eas Sa Figure 5 73 Enter new user group name and role for LDAP role mapping The Full Access flag has the same significance as in native authentication mode If a use
551. separate and independent storage pools Essentially storage pools function as a means to effectively manage a related group of similarly provisioned logical volumes and their snapshots Improved management of storage space Storage pools form the basis for controlling the usage of storage space by imposing a Capacity quota on specific applications a group of applications or departments enabling isolated management of relationships within the associated group of logical volumes and snapshots A logical volume is defined within the context of only one storage pool Because storage pools are logical constructs a volume and any snapshots associated with it can be moved to any other storage pool if there is sufficient space within the target storage pool Chapter 2 IBM XIV Storage System logical architecture and concepts 31 As a benefit of the system virtualization there are no limitations on the associations between logical volumes and storage pools In fact manipulation of storage pools consists exclusively of metadata transactions and does not trigger any copying of data Therefore changes are completed instantly and without any system performance degradation Consistency groups A consistency group is a group of volumes of which a snapshot can be made at the same point in time therefore ensuring a consistent image of all volumes within the group at that time The concept of a consistency group is common among storage subsystems in which
552. ses because the scans are performed serially Allow a significant buffer of time between the completion of one scan and the start of the next scan 384 IBM XIV Storage System Architecture and Implementation 7 9 5 Monitoring your XIV Storage System with SCOM The IBM Storage Management Pack monitors each XIV Storage System for what it classifies as events and alerts These items are updated every 600 seconds In addition various components of each XIV Storage System are monitored and the status is updated every 300 seconds Components can be in one of three states gt Healthy gt Warning gt Error Alerts Alerts are events that need to be investigated They indicate that an application or device needs attention They can be thought of as a to do list for an administrator Alerts are generated in two ways gt By monitoring the event logs of each managed device gt By monitoring the health state of each component For example if the XIV Storage System marks a module or disk as Failed SCOM raises a Critical alert If a component changes from Failed to Ready SCOM raises a Warning alert Examples of alert monitors include Disk Monitor Module Monitor and XIV System Monitor Tip If a component fails and is then repaired for example when a disk fails and is then replaced with a new disk the resolution state of the Critical alert is automatically changed by SCOM from New to Closed However new alerts might be created with a se
553. sing Multi System Management LDAP based authentication Defining LDAP on the XIV Storage System LDAP managed user authentication Securing LDAP communication with Secure Sockets Layer Vvvvvvrvrvyvrvyvy Y Important An important aspect of XIV security is the support for data at rest encryption which is introduced with XIV Storage software V11 4 The encryption topic is covered in the IBM Redpaper X V Security with Data at Rest Encryption REDP 5047 Copyright IBM Corp 2013 All rights reserved 173 5 1 Physical access security When installing an XIV Storage System you need to apply the same security best practices that you apply to any other business critical IT system A good reference on storage security can be found at the Storage Networking Industry Association SNIA website http www snia org forums ssif programs best_ practices A common risk with storage systems is the retention of volatile caches The XIV Storage System is perfectly safe in regard to external operations and a loss of external power If there is a power failure the internal uninterruptible power supply UPS units provide power to the system The UPS enables the XIV Storage System to gracefully shut down However if someone gains physical access to the equipment that person might manually shut off components by bypassing the preferred process In this case the storage system is likely to lose the contents of its volatile caches resulting in a data loss
554. sion cache period Duration in minutes that the XIV Storage System keeps user credentials in its cache before discarding the cache contents If a user repeats the login attempt within session cache period minutes from the first attempt authentication is done from the cache content without contacting the LDAP server for the user credentials bind time limit The timeout value in seconds after which the next LDAP server on ldap_list_servers is called The default value for this parameter is 0 It must be set to a non zero value in order for bind establishing an LDAP connection to work The rule also applies to configurations where the XIV Storage System is configured with only a single server on the Idap_list_servers list 406 IBM XIV Storage System Architecture and Implementation The populated values are shown in Example B 3 Example B 3 Completing and verifying LDAP configuration on XIV gt gt Idap_ config set base _dn CN Users DC xivhost1ldap DC storage DC tucson DC ibm DC com session cache period 10 bind time limit 30 Command executed successfully xcli c XIV MN00019 u ITSO p redb0Ok ldap config get Name Value base dn CN Users DC xivhost1ldap DC storage DC tucson DC ibm DC com Xiv_group_ attrib description third expiration event 7 version J user_id_attrib objectSiD current_server use ssl no session cache period 10 second expiration event 14 read only role Read Only storage admin role Storage Administr
555. sk has its data mirrored across all other disks excluding the disks in the same module Each disk holds approximately one percent of any other disk in other modules Disks have an equal probability of being accessed regardless of aggregate workload access patterns gt The following information is described in XIV Storage System virtualization design on page 24 The storage system administrator does not plan the layout of volumes on the modules lf there is space available volumes can always be added or resized instantly with a negligible impact on performance There are no unusable pockets of capacity known as orphaned spaces gt When the system is scaled out through the addition of modules a new data distribution is created where just a minimum number of partitions are moved to the newly allocated Capacity to arrive at the new distribution table The new capacity is fully used within a few hours and with no need for any administrative intervention Therefore the system automatically returns to a state of equilibrium among all resources gt Upon the failure or phaseout of a drive or module a new XIV Storage System data distribution is created where data in non redundant partitions is copied and redistributed across the remaining modules and drives The system rapidly returns to a state in which all partitions are again redundant because all disks and modules participate in re creating the necessary p
556. ssentially the same as other directories The only difference is that we use the description attribute with OpenLDAP If the description attribute is already in use then you can substitute any suitable unused text attribute The schema in our example has been built with the same DN base but OpenLDAP has some subtle differences For example individual user objects are defined as UID type objects as opposed to using CN type with Active Directory Also the Users group is a OU type object as shown in Example 5 22 Example 5 22 Listing objects in an OpenLDAP schema ldapsearch LLL b ou Users dc itso dc storage dc ibm dc com D cn Manager dc itso dc storage dc ibm dc com w PASSWOrd OU Users dn ou Users dc itso dc storage dc ibm dc com objectClass top objectClass organizationalUnit ou Users 238 IBM XIV Storage System Architecture and Implementation Idapsearch LLL b ou Users dc itso dc storage dc ibm dc com D cn Manager dc itso dc storage dc ibm dc com w PASSWOrd dn dn ou Users dc itso dc storage dc ibm dc com dn uid itso ou Users dc itso dc storage dc ibm dc com dn uid zejn ou Users dc itso dc storage dc ibm dc com dn uid almira ou Users dc itso dc storage dc ibm dc com dn cn XIVAdmins ou Users dc itso dc storage dc ibm dc com dn cn XIVReadonly ou Users dc itso dc storage dc ibm dc com dn uid phb ou Users dc itso dc storage dc ibm dc com The XIV administrator must specify that the LDAP server type
557. sses the extended flash cache When the buffer reaches 512 KB it is written sequentially to the flash cache as a log structured write This method helps to prolong the life of the flash cache Note The XIV is able to retain the data in the flash cache between system restarts and code upgrades XIV Storage System software Version 11 2 introduced improved flash caching algorithms providing a performance boost of up to 4 5 times over systems without flash cache for random database type workloads This boost is accomplished by storing and computing all flash cache related data integrity checking tasks in DRAM rather than on the flash cache 2 6 Encryption for data at rest IBM XIV Storage System Gen3 Model 214 with software Version 11 4 0 for machine types 2810 and 2812 introduces industry standard encryption for data at rest while avoiding a performance impact All capacity points 1 TB 2 TB 3 TB and 4 TB are supported using self encrypting hard drives SED and software based encryption ready flash cache Implemented with AES 256 bit keys encryption can be done with data already on disk hot encryption It is non disruptive and takes only a matter of minutes 42 IBM XIV Storage System Architecture and Implementation Key management is accomplished with Tivoli Key Lifecycle Manager TKLM or its replacement the IBM Security Key Lifecycle Manager which offers production ready key management and is based on Key Management Interoperabilit
558. ssible for the storage administrator to intervene to redistribute hard capacity 2 5 Flash caching architecture Starting with the XIV System software Version 11 1 0 the XIV Storage System Gen3 supports an optional flash caching feature that significantly improves performance for small block random read I O workloads 2 5 1 Flash caching overview XIV flash caching is implemented as an extension of the primary cache layer Flash cache is used exclusively as a read cache Each module supports 400 GB cache which allows the caching layer to be expanded up to 6 TB Starting with software Version 11 4 a flash cache of 800 GB per module for a total of 12 TB in a fully populated system with 4 TB drives can be used optionally to further boost performance With flash caching illustrated in Figure 2 7 on page 41 there is no need to relocate data Because flash cache is used as read cache only when data in cache is no longer accessible it can simply be dropped and replaced by more relevant data This approach allows for the flash cache to be used very effectively in highly dynamic environments where data patterns are constantly changing To have a holistic solution the caching architecture must also deliver good write performance 40 IBM XIV Storage System Architecture and Implementation CACHE Flash Cache mapped as an p extension ot memory DRAM Layer 550 Layer Allocates Flash Cache slots dynamically according to the dete
559. st obtaining a server certificate from a CA and installing the server and CA certificates The cacert pem file is ready to be uploaded to the XIV Storage System When a new LDAP server is added to the XIV Storage System configuration a security certificate can be entered in the optional certificate field If the LDAP server was originally added without a certificate you must remove that definition first and add a definition with the certificate LDAP server When defining the LDAP server with a security certificate in XIV Storage System the fully qualified name of the LDAP server must match the issued to name in the client s certificate For registering the LDAP server with a security certificate it might be easier to use the XIV Storage Management GUI because it has a file upload capability see Figure 5 79 XCLI can also be used but in this case you need to cut and paste a long string containing the certificate into the XCLI session To define the LDAP server in the XIV Storage Management GUI from the menu bar click Systems Settings LDAP click the LDAP Servers tab and then press the green plus sign on the right panel Define LDAP Server FQDN itso storage ibm com 9155 113 143 Server Address Search DN ON Users DOC itso DC storage DC ibm Server Port Server Secure Port Certificate File ay P ji Figure 5 79 Defining Active Directory LDAP server with an SSL certificate
560. st Port Module Local FC port Type ITSO Win2008 iscsi iqn 1991 05 com microsoft win gjbe8kr49ee itso storage ibm com 1 Module 6 SCSI ITSO Win2008 iscsi iqn 1991 05 com microsoft win gj5e8kr49ee itso storage ibm com 1 Module 5 iSCSI In Example 4 14 there are two paths per host FC HBA and two paths for the single Ethernet port that was configured See X V Storage System Host Attachment and Interoperability SG24 7904 for details related to host definitions and volume mapping 4 7 Flash cache Flash cache is an optional feature introduced and supported by the XIV system software Version 11 1 0 on an XIV Gen3 system Flash cache adds up to 12 TB of management free caching power to a fully configured 15 module storage system The flash cache automatically adjusts to the workload providing a performance boost for small I O random reads No additional configuration or tuning is necessary by the storage administrator However XIV Storage Manager GUI Version 4 offers enhancements to support flash cache allowing the storage administrator to perform several optional actions for example gt Check the flash cache status in each module gt Enable or disable flash cache at system level gt Enable or disable flash cache at volume level Chapter 4 IBM XIV Storage Management software 165 The remainder of this section shows the essential actions that an administrator can perform through the GUI and the XCLI to manage the flash cache featu
561. st the IBM intranet XRSC then shows the connected client system available to the support personnel The IBM Support person then chooses which system to support and to which system to connect Only permitted IBM XIV systems are shown IBM Support personnel log their intended activity 7 A fully recorded support session commences 8 When complete the support person terminates the session and the XRSC disconnects the XIV Storage System from the remote support system Client usage scenario After a client has decided that remote support is needed possibly because of a telephone request from a remote support professional communication between the XRSC and the client site must be established This process is always initiated by the client and always remains under the client s control It proceeds as follows gt The client tells the XIV Storage System to connect to the XRSC using a specific XCLI command Until this command is issued an XIV Storage System will not connect to the XRSC for any reason IBM XIV Storage System Architecture and Implementation gt The client can set a regular timeout and an idle timeout for the connection using an optional parameter in the connection command A timeout causes the connection to be dropped after a specified length of time whether a support session is in progress or not while an idle timeout causes the connection to be dropped after a certain period of inactivity Specify
562. stem Architecture and Implementation The new Active Directory group creation window is shown in Figure 5 76 New Object Group E R Create in itso storage ibrm com Users tS Group name sIvReadonly Group name ore Windows 2000 xIvReadonly Group scope Group type Domain local i Security i Global Distribution f Universal cei Figure 5 76 Creating Active Directory group To assign an existing user to the new group complete the following steps 1 Start Active Directory Users and Computers by selecting Start Administrative Tools Active Directory Users and Computers 2 Expand the Users container right click the user name that you want to make a member of the new group and select Add to a group 3 In the Select Groups window click Add gt Advanced Find Now From the presented list of existing user groups click XIVReadonly and click OK 4 You can now see a group selection window as shown in Figure 5 77 Confirm your choice by clicking OK Select Groups Fx Select this object type Groups or Built in security principals Object Types From this location tsa storage ibm com Locations Enter the object names to select examples slv Readonl Check Names Advanced Cancel Z Figure 5 77 Active Directory group selection window To illustrate the new memberOf attribute in the existing LDAP user object and the new LDAP object representing the XIVReadOnly
563. stency group IBM XIV Storage System Architecture and Implementation gt Moving volumes between storage pools See Moving volumes between storage pools on page 143 gt Creating a snapshot gt Creating a snapshot advanced gt Overwriting a snapshot gt Copying a volume or snapshot gt Locking and unlocking a volume or snapshot gt Mappings gt Change SSD Caching State gt Displaying properties of a volume or snapshot gt Changing a snapshot s deletion priority gt Duplicating a snapshot or a snapshot advanced gt Restoring from a snapshot Creating volumes When you create a volume in a traditional or regular storage pool the entire volume storage Capacity is reserved static allocation You cannot define more space for volumes in a regular storage pool than the actual hard capacity of the pool which guarantees the functionality and integrity of the volume When you create a volume in a thin provisioned pool the capacity of the volume is not reserved immediately to the volumes However a basic 17 1 GB piece which is taken out of the storage pool hard capacity is allocated at the first I O operation In a thin provisioned pool you are able to define more space for volumes than the actual hard capacity of the pool up to the soft size of the pool The volume size is the actual net storage space as seen by the host applications not including any mirroring or other data protection impact The
564. storage Management User admin Password ecccceceee Mode Diop Login Licensed Materials Property oF IBM Corporation and other s Copyright 2008 2012 IBM and XIV are a registered trademarks of IEM Corporation in the United States other countries or bath Figure 5 21 XIV Storage Management GUI login 2 Users are defined per system If you manage multiple systems and they have been added to the XIV Storage Management GUI select the particular system with which you want to work 3 In the main Storage Manager GUI window hover the cursor over the padlock icon to display the Access menu All user access operations can be performed from the Access menu see Figure In the Version 3 XIV Storage Management GUI only the Users menu option shows Click Users as shown in Figure Figure 5 22 XIV Storage Management GUI Access menu 4 By default the Ungrouped group is displayed and is shown in a collapsed state Click the plus symbol to expand its state If the storage system is being accessed for the first time the window shows the predefined users only as shown in Figure 5 23 on page 192 The default columns are Name Category Phone Email and Group Chapter 5 Security 191 o Name Category Ungrouped 4 admin Storage Administrator amp technician Technician amp xw _ development KIV Development amp xiv_hostprofiler XIV Host Profiler amp xiv_maintenance
565. strator role to be added to a user group Go to the Users window and right click the user name to display the menu From the menu see Figure 5 33 select Add to Group to add this user to a group Category Storage Administrator technician _ Technician xiv_development Edit evelopment xiv_hostprofiler Delete ost Profiler xiv_maintenance aintenance xiv_msms hangs PASAMAN ge Administrator Add To Group Remove From Group ApplicationO1 Group Properties Figure 5 33 Add a user to a group IBM XIV Storage System Architecture and Implementation 7 From the Select User Group window that opens select the group that you want from the drop down list and click OK see Figure 5 34 Select User Group Add User to User Group f Application01_Group a Application02 Group Application01_ Group EEE po E Figure 5 34 Select User Group window The lab_admin user has been added as a member to the Application01_Group user group in this example 8 Verify this group membership under the Application01_Group section of the Users window as shown in Figure 5 35 Category Phone Email Ungrouped aie Application0O1_Group a lab_admin applicationadmin 0049 5219185 lab_admin domain de Application01_Group ais Application02_Group Figure 5 35 View user group membership The lab_admin user is an applicationadmin with the Full A
566. t Apollo 1300474 est XIV 1310077 Alba J 3 sl E ex vol_Atest every5minutes 121001_110726 ex_vi E ex vol 5 test everySminutes 121001 110105 ex_v E ex_vol_45 test everySminutes 121001_ 110726 ex_v E last replicated test_mirror_002 test_mirror_002 E last replicated test_mirror_002 test_mirror_002 t as 9 test1 2 clus Starbuck MNOO027 test ESMCLUSTER Starbuck MNOO027 a g Figure 4 34 Search window The search function is also available within all table views of objects within the GUI You can filter items displayed in the table by typing a text string in the box located above the table See Figure 4 35 for an example which illustrates the Volume and Shapshots view filtering the view to display all volumes that contain the ITSO string in the name field The string can be anywhere in the name not just at the beginning Volumes and Snapshots Q itso gt lume 6 of 476 Snapshot 0 of 11 System Size GB Used GB AIO 1370114 24 GB 10 GB AIV_O2_ 1310714 24 GB 10 GB AIW O02 13470114 24 GB 6 GB AIW O02 1370114 24 GB 6 GB AIW 02 1370714 51 GB 9 GB AI _ O02 1370114 51 GB 9 GE Figure 4 35 Local table filter IBM XIV Storage System Architecture and Implementation Consisten cy Group ae es rs ee Quality of Service Quality of Service QoS is a feature that allows the XIV Storage System to deliver multiple service l
567. t architecture As with any enterprise class system redundancy pervades every aspect of the XIV Storage System including the hardware internal operating environment and the data itself However the design elements including the distribution of volumes across the whole of the system in combination with the loosely coupled relationship between the underlying hardware and software elements empower the XIV Storage System to realize unprecedented resiliency The resiliency of the architecture encompasses not only high availability but also excellent maintainability serviceability and performance under ideal conditions resulting from planned or unplanned changes to the internal hardware infrastructure such as the loss of a module Availability The XIV Storage System maximizes continuous operation and minimizes the performance degradation associated with nondisruptive planned and unplanned events while providing the capability to preserve the data in a disaster High reliability The XIV Storage System not only withstands individual component failures by quickly and efficiently reinstating full data redundancy but also monitors permanently and phases out individual components before data redundancy is compromised We describe this topic in detail in Proactive phase out and self healing mechanisms on page 54 The collective high reliability provisions incorporated within the system constitute multiple layers of protection from unplanned ou
568. t for clients who want to be able to grow capacity without managing multiple tiers of storage The XIV Storage System is suited for mixed or random access workloads including online transaction processing video streamings images email and emerging workload areas such as Web 2 0 and storage cloud The focus of this edition is on the XIV Gen3 hardware Release 3 4 running Version 11 4 of the XIV system software With this version XIV Storage System offers 4 TB drives and enhanced caching with optional 800 GB flash cache devices solid state drives SSDs per module IBM XIV software Version 11 4 XIV Gen3 supports encryption for all capacity points This version also scales XIV snapshot management out with the new Hyper Scale Consistency by coordinating concurrent snapshots of volumes that are spread across multiple XIV systems and belong to one application In the first few chapters of this book we describe many of the unique and powerful concepts that form the basis of the XIV Storage System logical and physical architecture We explain how the system is designed to eliminate direct dependencies between the hardware elements and the software that governs the system In subsequent chapters we explain the planning and preparation tasks that are required to deploy the system in your environment by using the intuitive yet powerful XIV Storage Manager GUI or the XIV command line interface XCLI We describe the performance characteristics of
569. t port from which the iSCSI connection was initiated The default gateways are required only if the hosts are not on the same Layer 2 subnet as the XIV Storage System Chapter 3 IBM XIV architecture components and planning 93 The IP network configuration must be ready to ensure connectivity between the XIV Storage System and the host before the physical system installation gt Ethernet virtual local area networks VLANs if required must be configured correctly to enable access between hosts and the XIV Storage System gt IP routers if present must be configured correctly to enable access between hosts and the XIV Storage System Mixed iSCSI and Fibre Channel host access XIV Storage System does not support mixed concurrent access from the same host to the same volume through FC and iSCSI simultaneously A single host could access different volumes where some volumes are accessed using FC and some are accessed using iSCSI You could also access the same volume from separate hosts using various connection methods if those hosts use a form of clustered file or operating system IBM service ports The XIV Storage System has two Ethernet ports dedicated for the use of service personnel The system serves as a Dynamic Host Configuration Protocol DHCP server and automatically configures the notebook These ports are only for IBM maintenance personnel for example an IBM service support representative SSR or IBM Technical Advisor T
570. t the space allocated Thin provisioning can be specified at the storage pool level Each thin provisioned pool has its own hard capacity which limits the actual disk space that can be consumed and soft capacity which limits the total logical size of volumes defined The difference in the pool size depends on the type of pool gt Hard pool size The hard pool size represents the physical storage capacity allocated to volumes and snapshots in the storage pool The hard size of the storage pool limits the total of the hard volume sizes of all volumes in the storage pool and the total of all storage consumed by snapshots gt Soft pool size This size is the limit on the total soft sizes of all the volumes in the storage pool The soft pool size has no effect on snapshots 136 IBM XIV Storage System Architecture and Implementation For more detailed information about the concept of thin provisioning and a detailed discussion of hard and soft size for storage pools and volumes see 2 4 Capacity allocation and thin provisioning on page 34 and the Redpaper publication BM XIV Thin Provisioning and Space Reclamation REDP 5001 When using the XIV Storage Management GUI you specify what type of pool is wanted Regular Pool or a Thin Pool when creating the pool See Creating storage pools on page 139 When using the XCLI you create a thinly provisioned pool by setting the soft size to a value greater than its hard size If the r
571. tages and minimize the possibility of related service actions Maintenance freedom Although the potential for unplanned outages and associated corrective service actions are mitigated by the reliability attributes inherent in the system design the XIV Storage System autonomic features minimize the need for storage administrators to conduct non preventative maintenance activities that are purely reactive in nature This is done by adapting to potential issues before they are manifested as a component failure The continually restored redundancy with the self healing attributes of the system effectively enable maintenance activities to be decoupled from the instigating event such as a component failure or malfunction and safely carried out according to a predefined schedule In addition to the system s diagnostic monitoring and autonomic maintenance a proactive and systematic approach to maintenance is augmented because the entirety of the logical topology is continually preserved optimized and balanced according to the physical state of the system The modular system design also expedites the installation of any replacement or upgraded components while the automatic and transparent data redistribution across all resources eliminates the downtime even in the context of individual volumes associated with these Critical activities High availability The rapid restoration of redundant data across all available drives and modules in the syst
572. tain transactions therefore this statement may not apply to you This information could include technical inaccuracies or typographical errors Changes are periodically made to the information herein these changes will be incorporated in new editions of the publication IBM may make improvements and or changes in the product s and or the program s described in this publication at any time without notice Any references in this information to non IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you Any performance data contained herein was determined in a controlled environment Therefore the results obtained in other operating environments may vary significantly Some measurements may have been made on development level systems and there is no guarantee that these measurements will be the same on generally available systems Furthermore some measurements may have been estimated through extrapolation Actual results may vary Users of this document should verify the applicable data for their specific environment Information concerning non IBM products was obtained from the suppliers of those products their published ann
573. te and Time Apr 5 2012 10 07 23 AM Component Type 1 Component Category SMMPVisolorg dodinternet private Venterprises ucdavis xivMIBYxiv Component Instance Condition Condition Value Source nextrabami storage tucson ibm cam Category Sender Name Time Event Occurred Time Event Received iso org dod internet mgmt mib 2 system sysName 0 iso org dod internet private enterprises ucdavis xivMIB xivMachine xivEvents xivEventTable xivEventEntry xivEventIndex iso org dod internet private enterprises ucdavis xivMIB xivMachine xivEvents xivEventTable xivEventEntry xivEventCode iso org dod internet private enterprises ucdavis xivMIB xivMachine xivEvents xivEventTable xivEventEntry xivEventTime iso org dod internet private enterprises ucdavis xivMIB xivMachine xivEvents xivEventTable xivEventEntry xivEventDescription iso org dod internet private enterprises ucdavis xivMIB xivMachine xivEvents xivEventTable xivEventEntry xivEventSeverity informational 1 Figure 7 76 Event details 7 6 Using Tivoli Storage Productivity Center Starting with Version 10 2 2 of the XIV Storage System software integration with Tivoli Storage Productivity Center V4 2 or higher also allows XIV Storage System performance monitoring from Tivoli Storage Productivity Center Tivoli Storage Productivity Center is an integrated suite for managing storage systems Capacity st
574. ted to storage pools and provides alerts when certain capacity thresholds are reached As the physical or hard capacity consumed by volumes within a storage pool passes certain thresholds the color of this meter indicates that additional hard capacity might need to be added to one or more storage pools Clicking the icons on the right side of the indicator bar that represent up and down arrows toggles the view between hard and soft capacity Our example indicates that the system has a usable hard capacity of 158934 GB of which 72 or 114296 GB is used You can also get more detailed information and perform more accurate capacity monitoring by looking at storage pools see 4 4 2 Managing storage pools with the XIV Storage Management GUI on page 137 gt The second indicator in the middle shows the number of IOPS gt The third indicator on the far right shows the general system status and for example indicates when a redistribution is underway Monitoring events To get to the Events window select Events from the Monitor menu as shown in Figure 7 12 Extensive information and many events are logged by the XIV Storage System The system captures entries for problems with various levels of severity including warnings and other informational messages These informational messages include detailed information about logins configuration changes and the status of attached hosts and paths All of the collected data can be review
575. tem architecture itself instead of at the host or storage area network level To appreciate the value inherent to the virtualization design that is used by the XIV Storage System remember the various aspects of the physical and logical relationships that make up conventional storage subsystems Specifically traditional subsystems rely on storage administrators to plan the relationship between logical structures such as arrays and volumes and physical resources such as disk packs and drives to strategically balance workloads meet capacity demands eliminate hotspots and provide adequate performance 2 3 1 XIV Storage System virtualization design The implementation of full storage virtualization employed by the XIV Storage System eliminates many of the potential operational drawbacks that can be present with conventional storage subsystems while maximizing the overall usefulness of the subsystem 24 IBM XIV Storage System Architecture and Implementation The XIV Storage System virtualization offers the following benefits gt Easier volume management Logical volume placement is driven by the distribution algorithms freeing the storage administrator from planning and maintaining volume layout The data distribution algorithms manage all of the data in the system collectively without deference to specific logical volume definitions Any interaction whether host or system driven with a specific logical volume in the system is
576. tem as close as possible to its final destination before an IBM SSR can start the physical installation Carefully check and inspect the delivered crate and hardware for any visible damage If there is no visible damage and the tilt and shock indicators show no problem sign for the delivery Before starting the physical installation ensure that an electrician is available who is able to handle the power requirements in the environment up to the XIV Storage System power connectors The physical installation steps are as follows 1 Place and adjust the rack in its final position in the data center 2 Check the XIV Storage System hardware When the machine is delivered with the weight reduction feature FC 0200 the IBM SSR installs the removed modules and components into the rack 3 Connect the XIV Storage System power cords to the client provided power source and advise an electrician to switch on the power connections 4 Perform the initial power on of the machine and perform necessary checks according to the given power on procedure 5 To complete the physical steps of the installation the IBM SSR performs various final checks of the hardware before continuing with the basic configuration Basic configuration After the completion of the physical installation steps the IBM SSR establishes a connection to the XIV Storage System through the patch panel see 3 1 10 Patch panel on page 85 and completes the initial setup You
577. tep is to associate a host or cluster with the group 2 Associate the itso app02 group user group to host itso app02 as shown in Example 5 17 Example 5 17 XCLI access_define gt gt access define user _group itso app02 group host itso app02 Command executed successfully 5 8 4 Active Directory group membership and XIV role mapping In Active Directory a user can be a member of a single group or multiple groups An LDAP group is a collection of users with common characteristics Group is defined in the Active Directory container Users A group is defined first as an empty container and then existing users Can be assigned as members of this group A group is represented as a separate object in the LDAP DIT and gets a distinguished name DN assigned to it Groups defined in the Active Directory can be used for XIV Storage System role mapping When a user becomes a member of a group in the Active Directory it gets a new attribute assigned The value of the new attribute points to the DN of the group Member 0f is the name of that attribute The Member Of attribute value determines the Active Directory group membership To create a group in Active Directory complete the following steps 1 Start Active Directory Users and Computers by clicking Start Administrative Tools gt Active Directory Users and Computers 2 Right click the Users container and click New Group 3 Enter a group name and click OK 234 IBM XIV Storage Sy
578. ter new hardware is added removed or has failed Only the data necessary to keep the system fully redundant is redistributed minimizing recovery time and data movement Because of this powerful distribution algorithm the performance is always consistent 2 IBM XIV Storage System Architecture and Implementation Flash solid state drive SSD Caching available as an option adds up to 12 TB of management free caching power to the whole system providing up to three times better performance for application workloads without the need for setup administration or migration policies The XIV flash caching feature is described in more detail in the IBM Redpaper publication Solid State Drive Caching in the IBM XIV Storage System REDP 4842 The virtualized grid architecture and algorithms that are used divide the host data into 1 MB partitions and distribute them pseudo randomlly across all disks leading to a consistent load on all components and eliminating hotspots During the distribution process the data is always mirrored by ensuring that each 1 MB partition is kept in at least two separate locations within the system Clients receive exceptionally low total cost of ownership because the system software licensing includes quality of service QoS snapshots thin provisioning data migration asynchronous and synchronous mirroring and an intuitive GUI combined with dramatic efficiencies in capacity power and space Because of the unique
579. ter volume A master volume and all of its associated snapshots are always in the same storage pool A volume can only be part of a single consistency group and a single storage pool All volumes of a consistency group must be in the same storage pool The space allocated for a storage pool can be dynamically changed by the storage administrator The storage pool can be increased in size The storage pool can be decreased in size It is limited only by the space that is consumed by the volumes and snapshots that are defined within that storage pool The designation of a storage pool as a regular pool or a thinly provisioned pool can be dynamically changed even for existing storage pools Thin provisioning is described in depth in 2 4 Capacity allocation and thin provisioning on page 34 The storage administrator can relocate logical volumes between storage pools without any limitations if there is sufficient free space in the target storage pool lf necessary the target storage pool capacity can be dynamically increased before volume relocation assuming sufficient deallocated capacity is available in the system When a logical volume is relocated to a target storage pool sufficient space must be available for all of its snapshots to be in the target storage pool as well Important gt When moving a volume into a storage pool the size of the storage pool is not automatically increased by the size of the volu
580. tes only actual data that has been written XIV Storage System does not bother protecting empty or free capacity that exists within a failed drive or module This situation is different from how RAID based arrays handle rebuilds and is one of the reasons why XIV Storage System rebuilds are fast It is easy to extend this discussion to a failed XIV Storage System module because the same redistribution scenario takes place The only difference is that now the data redistribution involves 12 drives rather than just one All the concepts and considerations and advantages still apply The rebuild and redistribution take longer because more data is involved The lOPS and megabytes per second MBps experience basically no change in the performance supplied to the applications Compare XIV Storage System redistribution to a RAID 5 array failure and rebuild gt The entire data storage capacity must be rebuilt using parity recalculation not just actual user data gt The rebuild process imposes a significant stress on the drives which can lead to additional drive failures gt The rebuild has a significant impact on the performance capabilities of the array gt Rebuild times are typically much longer when compared to XIV Storage System redistribution XIV Storage System redistribution is the same mechanism that redistributes data when a module is added to an XIV Storage System with the same considerations And it is worth noting that although
581. that is based on these variables and runs the command in a shell The output from XCLI commands can be customized using the t option to limit the display to only the specific fields in which we are interested In this case we need only the used capacity value of the volume Therefore the t option is used to limit the output to only the used capacity field as shown in Example 7 48 This option makes the output of the XCLI command easy to parse Example 7 48 Limiting output of XCLI commands using the t option var Command vol_list vol Volume t used capacity You can get a complete list of the field options available for any command by using the XCLI help option with the format full parameter as shown in Example 7 49 Example 7 49 Using the XCLI help command to list available output fields gt gt help command vol_list format full The output from the XCLI command is parsed and compared with the predefined custom threshold If the threshold is exceeded an XCLI command is used to create a custom event with a custom description and severity level as shown in Example 7 50 An event rule can be used on the XIV Storage System to notify a user of the condition Example 7 50 Using XCLI to generate a custom event if output gt Threshold Command custom event description Vol Volume exceeded threshold of Threshold GB severity Severity Chapter 7 Monitoring 373 After the script is created use
582. the System Machine Account password The System Machine Account is a system user that monitors the system on the Hyper Scale Manager The password can be changed either from the root menu or via the GUI In addition the password must be changed on all systems gt Changing the server admin password This menu option changes the System Machine Account password See the BM XIV Storage System Management Tools Version 4 0 User Guide SC27 4230 00 for detailed instructions Hyper Scale Manager is running System Inventory List Add System Modify System Remove System System Monitoring Suspend System Monitoring Resume Re authenticate All Users Change System Machine Account Manage System Certificates 10 Manage Capacity Planning Data 11 Back to previous menu Your Selection gt Figure 5 37 Manager Inventory Options menu Maintenance user operations Accessing the MSMS with maintenance credentials allows you to perform various maintenance tasks such as gathering server logs backing up or restoring the database replacing the security certificate or upgrading the MSM Refer to the IBM XIV Storage System Management Tools Version 4 0 User Guide SC27 4230 00 for detailed instructions 5 5 4 Managing user accounts using the XCLI This section summarizes the commands and options available to manage user accounts user roles user groups group memberships and user group to host associations through the XCLI Session Table 5 3 on pag
583. the drop down list box Otherwise you can manually enter the WWPN into the Port Name field Adding ports from the drop down list is less prone to error and is the best method However if hosts have not yet been connected to the SAN or zoned then manually adding the WWPNs is the only option Add Port System AIV Galactica 1340009 Host Name ITSO_Win2008 Port Type FC Port Name 5001738027840183 pe ce Cancel Figure 4 65 XIV Storage Management GUI example Add FC port WWPN Repeat steps 5 and 6 to add the second HBA WWPN Ports can be added in any order 8 To add an iSCSI host in the Add Port window specify the port type as iSCSI and enter the IQN of the HBA as the iSCSI Name See Figure 4 66 Add Port System XIV Galactica 1340009 Host Name TSO Win2008 Port Type iSCS iSCSI Name Cancel Figure 4 66 XIV Storage Management GUI example Add iSCSI port 9 The host is displayed with its ports in the Hosts window as shown in Figure 4 67 TsO Winz008 aa 50017300273 A12H FC jee 50017300278A5678 FC ITSO Winz008_iscsi default W ign 1991 05 com microsoftadminib 2999unn iSCSI Figure 4 67 List of hosts and ports Chapter 4 IBM XIV Storage Management software 161 In this example the hosts itso Win2008 and itso Win2008 iscsi are the same physical host but they have been entered as separate entities so that when mapping LUNs the FC and iSCSI protocols do not access the same LUNs
584. the pool s hard space until it is needed by Volume 2 Because the pool s soft capacity does not exceed its hard capacity there is no way to allocate soft capacity to effectively overcommit the available hard capacity Appendix A Thin provisioning conceptual examples 397 The final reserved space within the regular storage pool that is shown in Figure A 2 on page 397 is dedicated for snapshot usage The diagram shows that the specified snapshot reserve capacity of 34 GB is deducted from both the hard and soft space defined for the regular storage pool This deduction guarantees that this space is available for consumption collectively by the snapshots associated with the pool Although snapshots consume space at the partition level the snapshot reserve capacity is still defined in increments of 17 GB The remaining 17 GB within the regular storage pool have not been allocated to either volumes or snapshots All soft capacity remaining in the pool is backed by hard capacity The remaining unused soft capacity is always less than or equal to the remaining unused hard capacity Thinly provisioned storage pool conceptual example The thinly provisioned storage pool that was introduced in Figure A 1 on page 396 is explored in detail in Figure A 3 The hard capacity and the soft capacity allocated to this pool are the same in both diagrams 136 GB of soft capacity and 85 GB of hard capacity are allocated Because the available soft capac
585. the request and send it to the Certificate Authority to obtain your certific ate Operation Completed Successtully Figure B 14 Generated certificate Signing and importing a server certificate After the CER is generated xivhost2_cert_req pem you must send the request to the certificate authority to be signed For more information about signing this certificate see Signing a certificate for the xivhost1 server on page 432 After the signed certificate Generating the CA Signed Certificate Request Close xivhost2_cert pem file is returned you must import the certificate into the local machine s personal keystore Appendix B Additional LDAP information 425 To add the signed certificate to the Directory Service Manager manager application click Directory Servers xivhost2 storage tucson ibm com 389 Security gt Certificates Add Copy and paste the certificate stored in the xivhost2_cert pem file as shown in Figure B 15 Add Certificate Paste the certificate into the text field below The certificate text must be in ASCI format Indicates required Server xivhost2 storage tucson ibm cam 389 Certificate xivstorage org sample CA certificate Name Certificate Certificate Data Version 3 0x2 Serial Number 2 0x2 Signature Algorithm mdSWithRSAEncryption ae ee Not Before Jul 2 22 48 43 2009 GMT Not After Jul 2 22 48 43 2010 GMT Subject Public Key Info
586. the same thing The best way to determine whether response times are good or bad is to compare them to the values recorded when the application was known to be performing well If the response times compare closely it is likely that the XIV Storage System is still providing good performance There are several things to consider when evaluating XIV Storage System response times gt Do not be alarmed at sudden spikes in IOPS or response times Most production applications are not sensitive enough to experience performance issues associated with spikes that only last for one reporting interval which in the case of XIV Storage System is 1 minute gt Itis the prolonged elevated response times that most transaction based workloads notice as poor performance Prolonged can be 10 minutes or an hour or more because this measurement is dependent upon the application gt Response times can be different depending on the type of workload the XIV Storage System is servicing During batch processing when throughput MBps is the primary performance objective it is normal and common for batch response times to be higher for prolonged periods gt Be careful about lumping response times into one number Response times should be associated with either reads or writes Notice the read and write response times in Figure 6 31 on page 279 Chapter 6 Performance 281 282 Write response times for caching storage systems such as XIV Storage System are norm
587. this approach greatly simplifies the tasks of the storage administrator However when the system is running at full capacity it can have the adverse effect that noncritical applications are served at the same level as the business critical applications The QoS feature allows you to prevent such situations With QoS the storage administrator can specify and enforce limits on the performance of low priority workloads by limiting input output operations per second IOPS and bandwidth on a per host basis 2 3 2 Logical system concepts In this section we elaborate on the logical system concepts which form the basis for the system full storage virtualization Logical constructs The XIV Storage System logical architecture incorporates constructs that underlie the storage virtualization and distribution of data which are integral to its design The logical structure of the system ensures that there is optimum granularity in the mapping of logical elements to both modules and individual physical disks guaranteeing an equal distribution of data across all physical resources 26 IBM XIV Storage System Architecture and Implementation Storage Pool Volume Volume Partition 1MB Figure 2 5 Logical system virtualization concept Partitions The fundamental building block of a logical volume is known as a partition Partitions have the following characteristics on the XIV Storage System gt All partitions are 1 MB 1024 K
588. tin lab from 1989 to 1997 for the development of the AIX Logical Volume Manager and File System He has won an award for the design and development of a data recovery suite for AIX Following that assignment Itzhack worked on the code load design and development of the DS6000 He holds a degree in Computer Science Markus Oscheka is an IT Specialist for Proof of Concepts and Benchmarks in the Disk Solution Europe team in Mainz Germany His areas of expertise include the setup and demonstration of IBM System Storage solutions in various environments such as IBM AIX Linux Microsoft Windows VMware ESX and Solaris He has worked at IBM for 12 years He has performed many proof of concepts with Copy Services on DS8000 XIV SVC and V7000 as well as performance benchmarks with DS8000 XIV SVC V7000 He has performed many proof of concepts and performance benchmarks for disk storage products He has contributed and acted as co project lead for DS8000 and XIV Redbooks He has spoken at several System Technical Universities He holds a degree in Electrical Engineering from the Technical University in Darmstadt xii IBM XIV Storage System Architecture and Implementation Stephen Solewin is an XIV Corporate Solutions Architect for IBM in Tucson Arizona He has 16 years of experience working on IBM storage including Enterprise and Midrange Disk LTO drives and libraries SAN storage virtualization and storage software Steve has worked on the
589. ting web proxy service and it is not possible to open the firewall for the host running the proxy HTTPProxyPort The TCP port on which HTTPProxyHost listens After you configure the proxy conf file you can start the proxy service by running service proxy start and then run service proxy status to confirm that the XIV Remote Support Proxy agent is running as shown in Example 7 38 Example 7 38 Starting the Remote Proxy and check its status bc h 15 b6 service xivproxy start Starting IBM XIV remote support proxy done bc h 15 b6 service xivproxy status IBM XIV remote support proxy running Listen address 9 155 113 137 8988 Target address 195 110 41 141 443 Running since Sep 27 15 40 56 Open connections 0 Failed connections 0 Total connections 0 Example 7 39 shows a query of the XIV Remote Support Proxy agent to check its status from a remote location by using Telnet In this example there are two active remote support connections from separate IBM XIV systems using the proxy Example 7 39 Querying the status of the XIV Remote Support Proxy agent using Telnet telnet 9 155 113 137 8989 Trying 9 155 113 137 Connected to 9 155 113 137 Escape character is Listen address 9 155 113 137 8988 Target address 195 110 41 141 443 Running since Sep 27 15 40 56 Open connections 2 Failed connections 0 Chapter 7 Monitoring 335 Total connections 2 Connection to 9 155 113 137 closed by forei
590. tion the event typically triggers a new IBM problem management record PMR 324 IBM XIV Storage System Architecture and Implementation Because call home uses the clients network and SMTP service IBM cannot guarantee the delivery of events Therefore events must be monitored by the client as described in 7 2 XIV Storage System event notification on page 315 When the call home feature is configured and events are received by the XRSC periodic heartbeat events are also received The heartbeats are monitored by IBM and the client is notified if the heartbeats are not received or are no longer received There is an IBM service called Electronic Service Call ESC where you can monitor service calls that are specific to a customer account ID The ESC gives you the ability to verify that a service ticket has been raised following an appropriate event and to open a new service call The ESC website is shown http www ibm com support esc Contact your local IBM SSR to have your user ID associated with a specific customer ID in ESC The SMTP address for call home is configured separately from the general XIV Storage System SMTP setting If the client s mail server gateway changes a service call must be logged to have the internal call home SMTP setting changed Tip Email relaying on the SMTP gateway server might need to be enabled to allow call home events to be sent to IBM 7 3 2 Remote support The XIV Storage System
591. to obtain the status of specific system components such as disks modules or adapters 298 IBM XIV Storage System Architecture and Implementation The component_1ist command which is shown in Example 7 6 gives the status of all hardware components in the system The filter option filter lt FAILED NOTOK gt is used to return information only about failing components The first example shows a failed disk in module 4 slot 9 and the second example shows that all components are in an OK status Example 7 6 The component_list command gt gt component_list filter NOTOK Component ID Status Currently Functioning 1 Disk 4 9 Failed no gt gt component_list filter NOTOK No components match the given criteria As shown in Example 7 7 the disk_list command provides more in depth information for any individual disk in the XIV Storage System which might be helpful in determining the root cause of a disk failure If the command is issued without the disk parameter all the disks in the system are displayed Example 7 7 The disk_list command gt gt disk_list disk 1 Disk 13 10 Component ID Status Currently Functioning Capacity GB Vendor Model Size Serial 1 Disk 13 10 OK yes 21B IBM XIV 1T32000444 1878632 QWM4PHXG Example 7 8 shows a disk that is failed but in a deferred replacement state For more details about this state see Deferred disk replacement on page 297 Example 7 8 Disk in deferred replacement gt gt component_l
592. torage Management Pack focuses on availability 7 9 1 Prerequisites To monitor your XIV Storage System with SCOM you must meet the following prerequisites gt Microsoft System Center Operations Manager 2007 R2 Microsoft System Center Operations Manager 2012 or Microsoft System Center Operations Manager 2012 SP1 gt IBM Storage Management Pack V1 2 V1 3 or V2 1 for SCOM gt XIV Storage System software V10 2 2 or later The XIV Storage Management GUI or XCLI does not need to be installed on the SCOM server The IBM Storage Management Pack installs all the software that is required for SCOM to access the XIV Storage System 378 IBM XIV Storage System Architecture and Implementation 7 9 2 Installing SCOM and the IBM Storage Management Pack Installing SCOM onto a Windows server is not a trivial task and is beyond the scope of this publication Assuming that SCOM is already installed and operating correctly this section shows you how to install the IBM Storage Management Pack for SCOM The release notes and installation instructions are available at the XIV Storage System Information Center http www ibm com support fixcentral swg quickorder parent Enterprise StoragetSer vers amp product ibm Storage Disk XIV StoragetSystem 2810 2812 amp release All amp platform Al1 amp function al 1 amp source fc You can also see the Microsoft System Center Operations Manager website http www microsoft com en us server cloud system ce
593. tore XIV to full redundancy At the end of the rebuilding period the XIV Storage System is again fully redundant The XIV Storage System rebuild process has the following characteristics gt The rebuild of data is many times faster than conventional RAID array rebuilds and can complete in a short period for a fully provisioned system Statistically the chance of exposure to data loss or a cascading hardware failure is minimized because of both the short rebuild time required and the low I O workload imposed on any given disk Rebuilding conventional RAID arrays can take many hours to complete depending on the type of the array the number of drives and the ongoing host generated transactions to the array The stress imposed on the drives of conventional RAID arrays during rebuilds is high raising the risk of additional hardware failure of the RAID member disks In XIV a typical rebuild is measured in minutes not hours For example a fully populated 15 module XIV System with the usable capacity of 240 TB rebuilds in less than 50 minutes The rebuild process can complete 25 to 50 more quickly for systems that are not fully provisioned which equates to a rebuild completion in as little as 15 minutes The rebuild time is linear and decreases with the amount of written data gt The XIV Storage System rebuilds only actual data The number of drives participating in the rebuild is about 20 times greater than in most average s
594. try Unlike a predefined object class for a user account in Active Directory LDAP Sun Java Directory LDAP presents you with a choice of object class types The LDAP object class describes the content and purpose of the object It also contains a list of attributes such as a name surname or telephone number Traditionally the inetOrgPerson object class type is used for LDAP objects that describe personal information To be compatible with XIV Storage System an object class must include a minimal set of attributes These attributes are as follows uid User identifier user name userPassword User password description configurable LDAP role mapping attribute You can select another object class type if it contains the same minimal set of attributes The object class type can enforce certain rules For example various attributes can be designated as mandatory in which case a new LDAP object cannot be created without assigning a value to that attribute For the inetOrgPerson object there are two mandatory attributes cn Full Name also called Common Name sn Full Name also called Surname IBM XIV Storage System Architecture and Implementation Although it is possible to populate these two objects with various values we use the uid value to populate both the cn and sn attributes See Figure B 6 Step 3 Choose Object Class Choose the object type of the entry you want to create User inetOngPerson ae
595. ts and failures for every system shown in the GUI In Figure 7 3 you can see that there are several alerts for two different IBM XIV systems although there are no current failures If you double click an alert the next relevant window opens For example in Figure 7 3 there are several pool alerts Therefore double clicking a pool alert changes the window to show the relevant pool highlighted on the pools view of the relevant XIV Storage System system systems Actions View l Tools Help Ah wi 2 Export A AllSystems 12 AllSystems Alens Q Alerts 5 l Description lt 1 Hour AIV PFE_03 76041435 Fan 6 Module 15 status is Failed Warning lt 1 Hour XIV_01_ 6000705 Pool AW_VMVWARE_ FCM snapshotreservedi Warning lt 1 Hour AlV_047_ 6000705 Pool AW_VWINDOWS snapshot reserved is 33 Warning lt 4 Hour xIV_04_ 6000705 Pool Test snapshot reserved is 66 full Minor lt 1 Hour KIW _01_6000105 Pool ymesx_35 test_backup XIV_labdis 79 Minor Figure 7 3 All Alerts window of the All Systems menu All Systems Events window If you select the All Systems Events view a combined event log is displayed and shows all events for all systems that are defined to the GUI In Figure 7 4 you can see events from three different systems in a combined view This view can be sorted and filtered to reduce the number of events or change the order in which they are displayed A sAlSystems G Al Systems Events Q Events 1
596. ts are like volumes except snapshots incorporate dependent relationships with their source volumes which can be either logical volumes or other snapshots Because they are not independent entities a given snapshot does not necessarily wholly consist of partitions that are unique to that snapshot Conversely a snapshot image does not share all of its partitions with its source volume if updates to the source occur after the snapshot was created Logical volume layout on physical disks The XIV Storage System manages the distribution of logical volumes over physical disks and modules with a dynamic relationship between primary data partitions secondary data partitions and physical disks This virtualization of resources in the XIV Storage System is governed by the data distribution algorithms Distribution table The distribution table is created at system startup and contains a mapping of every primary and secondary partition and the module and physical disk where they are located When hardware changes occur a new distribution table is created and delivered to every module Each module retains redundant copies of the distribution table 28 IBM XIV Storage System Architecture and Implementation Volume layout At a conceptual level the data distribution scheme can be thought of as a mixture of mirroring and striping Although it is tempting to think of this scheme in the context of RAID 1 0 10 or 0 1 the low level virtualization impleme
597. ts the physical space used by the volume in 1 MB partitions In both cases the upper limit of this provisioning is determined by the logical size assigned to the volume gt Capacity is allocated to volumes by the system in increments of 17 GB because of the underlying logical and physical architecture There is no smaller degree of granularity than 17 GB For more details see 2 3 2 Logical system concepts on page 26 gt Application write access patterns determine the rate at which the allocated hard volume Capacity is consumed and therefore the rate at which the system allocates additional increments of 17 GB up to the limit defined by the logical volume size As a result the storage administrator has no direct control over the actual capacity allocated to the volume by the system at any given point in time gt During volume creation or when a volume has been formatted there is zero physical capacity assigned to the volume As application writes accumulate to new areas of the volume the physical capacity allocated to the volume grows in increments of 17 GB and can ultimately reach the full logical volume size gt Increasing the logical volume size does not affect the actual volume size Chapter 2 IBM XIV Storage System logical architecture and concepts 35 36 Thinly provisioned storage pools Where volumes are effectively thinly provisioned automatically by the system storage pools can be defined by the storage admin
598. ty This configuration is generally the choice for clients who want more resiliency ports 1 and 3 are on separate adapters or availability in case of adapter firmware upgrade one connection remains available through the other adapter From a performance perspective each adapter has its own performance bandwidth capabilities and dedicated PCle bus bandwidth If you do not use mirroring you can also change port 4 to a target port Fibre Channel ports Using more than 12 Fibre Channel ports for host connectivity does not necessarily provide more bandwidth A best practice is to use enough ports to support multipathing without overburdening the host with too many paths to manage See IBM XIV Storage System Host Attachment and Interoperability SG24 7904 for more information Chapter 3 IBM XIV architecture components and planning 81 82 iSCSI connectivity With the 10 GbE adapter that equips the Model 214 10 GbE there are differences in iSCSI connectivity between the Model 114 Model 214 1 GbE and Model 214 10 GbE In addition improvements were made in the XIV Storage software Version 11 2 with a new iSCSI implementation with significant performance enhancements gt Network protocol processing has been moved from the Linux kernel to a user space application based on the open source Lightweight IP LWIP stack This change results in significant CPU processing efficiencies gt Using multiple Transmission Control Protocol
599. ty_list command shows an overview of used and free Capacity system wide In the example both the hard and soft usable capacity is 161326 GB with 42022 GB of free hard capacity and 39010 GB of free soft capacity It also shows that all spare Capacity is still available Example 7 3 The system_capacity_list command gt gt system capacity list Soft Hard Max_Pool Size FreeHard FreeSoft SpareModules Spare Disks TargetSpareModules TargetSpareDisks 161326 161326 80654 42022 39010 1 3 1 3 In Example 7 4 the version_get command shows the current version of the XIV Storage System code installed on the system Knowing the current version of your software assists you in determining when upgrades are required Example 7 4 The version_get command gt gt version_ get Version 11 2 0 a In Example 7 5 the time_list command is used to retrieve the current time from the XIV Storage System This time is normally set at the time of installation Knowing the current system time is required when reading statistics or events In certain cases the system time might differ from the current time at the user s location Therefore knowing when something occurred according to the system time assists with debugging issues Example 7 5 The time_list command gt gt time_list Time Date Time Zone Daylight Saving Time 23 05 28 2013 03 19 GMT no Time Date Time Zone System components status In this section we present various XCLI commands that are used
600. u specify these same parameters To aid in usage define and use specific environment variables Open a command prompt window in this case in Windows 2008 R2 and set values for specific environment variables as shown in Example 4 3 Example 4 3 Script file setup commands setx XIV_XCLIUSER itso setx XIV_XCLIPASSWORD PasswOrd setx XCLI_CONFIG_ FILE HOMEDRIVE HOMEPATH My Documents xcli xiv_systems txt The XCLI requires user and password options So if user and passwords are not specified the default environment variables XIV_XCLIUSER and XIV_XCLIPASSWORD are used Also the XCLI_CONFIG FILE variable file must be populated before setting the environment variable The configuration in this example is stored in a file under the user s home directory A separate file can be specified by f or file applicable to configuration creation configuration deletion listing configurations and command execution Alternatively the environment variable XCLI_CONFIG_FILE if defined determines the file s name and path After running the setup commands the shortened command syntax works as shown in Example 4 4 Example 4 4 Short command syntax c Users itso gt xcli a XIV2 m 192 168 0 4 m 192 168 0 5 m 192 168 0 6 c Users itso gt xcli c XIV2 user_list Options In the previous example the a option is used to name the XIV Storage System designated with the m addresses as XIV2 and referred to accordingly afterward 134 IBM XIV Stora
601. ubbing algorithm that runs continuously as a background process scanning all disks for checksum errors It assures data integrity by alerting corrective actions before user data becomes compromised Therefore redundancy is not only implemented as part of the basic architecture of the system but it is also continually monitored and restored as required In summary the data scrubbing process has the following attributes gt Verifies the integrity and redundancy of stored data even across mirrors gt Enables early detection of disk errors and their early recovery gt Runs as a background process on each module and all disks simultaneously gt Zeroes out partitions that are not allocated to the user data space A complete scrubbing cycle takes about one week for a system with 1 TB disks two weeks for a system with 2 TB disks and so on 54 IBM XIV Storage System Architecture and Implementation Enhanced monitoring and disk diagnostic tests The XIV Storage System continuously monitors the performance level and reliability standards of each disk drive within the system using an enhanced implementation of Self Monitoring Analysis and Reporting Technology SMART tools As typically implemented in the storage industry SMART tools indicate whether certain thresholds have been exceeded which gives an alert that a disk is at risk for failure and therefore needs to be replaced However as implemented in XIV Storage System the SMART diagnosti
602. ule destinations Welcome Select destinations and destinations groups to be notified when the event s Unselected Destinations Selected Destinations Severity Anthony f eae a Create Destination lt lt 6 lt Figure 7 46 Select destination Rule snooze Defines whether the system repeatedly alerts the defined destination until the event is cleared If so a Snooze time must be selected Check Use snooze timer and enter a snooze time in minutes Rule escalation Allows the system to send alerts by other rules if the event is not cleared within a certain time If so an escalation time and rule must be specified i Check Use escalation rule li Click Escalation Rule iii Enter an escalation time in minutes iv Click Create Escalation Rule Chapter 7 Monitoring 321 12 0n the summary window shown in Figure 7 47 review the information that you entered Go back if you need to make changes If everything is correct click Create Wizard Rule Create Create the rule Create the rule Welcome View the rule attributes and create the rule or cancel and discards all changes u Rule Name ITSO_Catcher Destination Min Severity Critical Destinations Anthony Figure 7 47 Rule Create window Setting up notifications and rules using the XCLI You use the same process to set up the XIV Storage System for notification using the XCLI as you
603. ult _ssd caching get Command executed successfully default disabled If the default status is enabled flash cache is enabled on all volumes in the system unless the status is manually changed Otherwise if default status is disabled flash cache is disabled for all volumes in the system Tip With the flash cache state enabled you can explicitly disable any volume that you do not want to include in the extended caching If you want to change the flash cache state globally for the system you can issue one of the following commands vol _ default _ssd_ caching set default enabled set the SSD Caching enabled vol default _ssd caching set default disabled set the SSD Caching disabled Chapter 4 IBM XIV Storage Management software 171 Volume level flash cache Use the vol_ssd_caching set command to set the flash cache status for a specific volume and eventually override the system default setting You must specify the vol and state parameters when you issue the command as illustrated in Example 4 18 Example 4 18 SSD Caching set for a volume XIV 1310039 Coruscant gt gt vol_ssd caching set vol Res Fra Vol 01 state enabled Command executed successfully XIV 1310039 Coruscant gt gt vol_ssd caching set vol Res Fra Vol 01 state disabled Command executed successfully You can also use the vol_1list command with the x flag and the vol parameter to display all of the volume properties which now include two additional values ssd_cach
604. umes using XIV Storage Management GUI complete the following steps 1 Right click the row of the volume to be resized and select Resize The total amount of storage is presented both textually and graphically The amount that is already allocated by the other existing volumes is shown in blue The amount that is free is shown in gray The current size of the volume is displayed as a dotted outline box around the storage pool gauge 2 In the New Size field type the new value or drag the edge of the outline box 3 Click Update to resize the volume Deleting volumes Using the XIV Storage Management GUI deleting a volume is as easy as creating one Chapter 4 IBM XIV Storage Management software 155 Important After you delete a volume or a snapshot all data stored on the volume is lost and cannot be restored All the storage space that was allocated or reserved for the volume or snapshot is freed and returned to its storage pool The volume or snapshot is then removed from all the logical unit number LUN maps that contain mapping of this volume Deleting a volume deletes all the snapshots associated with this volume even snapshots that are part of snapshot groups A volume can be deleted even if the volume is in the lock state but a volume cannot be deleted if the volume is mapped to a host or part of a consistency group To delete a volume or snapshot complete the following steps 1 Right click the row of the volume to
605. unity name click System Settings and then open the SNMP window that is shown in Figure 7 58 MM 1310133 Settings General SNMP Contact Parameters SNMP Location SNMP Community SNMP SNMP Trap Community Misc Unknown Unknown AlV AV Figure 7 58 Set or show the XIV Storage System SNMP community name You can also set or show SNMP information including the community name by running config get and config_set as shown in Example 7 42 Example 7 42 XIV Storage System SNMP commands XIV_1312611 gt gt config_ get Name dns_primary dns_ secondary system name Snmp_location snmp contact Snmp_community snmp_trap_ community system id machine type machine model machine serial number email sender_address email reply to address email subject format internal email subject_format iscsi_name maximal snapshot_deletion_ priority timezone fc_proof ntp_ server ups_ control Support center port type isns_ server ipv6 state ipsec_state Value XIV XIV 032611 2810 214 1312611 severity description ign 2005 10 com xivstorage 032611 A 0 yes yes Management enabled disabled Chapter 7 Monitoring 339 ipsec_track_tunnels no impending power_loss detection method UPS XIV_1312611 gt gt config_set name snmp_location value IBM Mainz Command executed successfully XIV_1312611 gt gt config_get name snmp_location Name Value snmp_location IBM Mainz 7 4 3 Using SNMP get or walk comm
606. uping is especially useful for cluster specific volumes gt Copy a volume You can copy a source volume onto a target volume All the data that was previously stored on the target volume is lost and cannot be restored gt Snapshot functions The XIV Storage System advanced snapshot feature has unique capabilities that enable the creation of a virtually unlimited number of copies of any volume with no performance penalties gt Map a volume Although the storage system sees volumes and snapshots at the time of their creation the volumes and snapshots are visible to the hosts only after the mapping procedure For more information about mapping see 4 6 Host definition and mapping on page 159 156 IBM XIV Storage System Architecture and Implementation gt Changing SSD Caching State Provides the ability to change the SSD Caching State for selected volumes By default volumes follow the SSD Caching system setting With this option you can manually override the default system setting for specific volumes For detailed information see 4 7 Flash cache on page 165 4 5 2 Managing volumes with XIV Command Line Interface All of the operations explained in 4 5 1 Managing volumes with the XIV Storage Management GUI on page 148 can also be performed through the command line interface To get a list of all the volume related commands enter the following command in an XCLI Session help category volume Important Th
607. ure components and planning 95 IPv6 addressing The IBM XIV with system software Version 11 1 0 or higher supports both IPv4 and IPv6 internet addressing IPv6 when compared to IPv4 provides the following advantages Larger address space 128 bit 24128 3 4x1038 addresses Fixed subnet size 64 bits 2464 18 4 quintillion addresses Eliminates the need for network address translation NAT Supports stateless auto configuration and network renumbering Inter operability with IPv4 by fixed subnet size 64 bit addresses Built in protocol for multicasting Mandatory support for IPSec IBM XIV Storage System has pre announced support IPSec in a future release YYYY YV Y Yy IPv6 compared to IPv4 addressing scheme The larger IPv6 addressing requires a change in the way IP addresses are represented gt I IPv4 architecture Uses 32 bit addressing with four groups of decimal numbers 1 254 separated by dots such as this example 9 54 100 124 gt I IPv6 architecture Uses 128 bit addressing with eight groups of four hexadecimal digits representing 16 bits separated by a colon such as this example 2001 0DB8 0000 0000 0008 0800 200C 417A Shorthand rules can be applied 2001 DB8 0 0 8 800 200C 417A Leading zeros within a 16 bit value can be removed 2001 DB8 8 800 200C 417A One group of consecutive zeros replaced with double colon IPv6 is supported by the IBM XIV Storage System IPv6
608. us drive configurations only Therefore ensure that the initial selection of drive capacity is viable in terms of forecasting capacity growth requirements Note Gen3 Model 114 systems running Version 11 1 1 or later of the XIV system software support 1 TB of capacity per spindle Using smaller drives maximizes the ratio of dynamic random access memory DRAM and flash cache to disk capacity also termed the backstore Using smaller drives also increases the potential maximum viable aggregate workload access density the ratio of IOPS to each unit of consumed capacity In performance terms the result is that the aggregate potential working set size that can be achieved with 100 capacity utilization is greatest when 1 TB drives are selected In addition to the impact to caching also consider that decreasing the drive size obviously decreases the maximum potential amount of data that can be accessed by each physical HDD arm This means that the viable achievable physical disk IOPS per unit of capacity is maximized Performance requirements can be determined in a number of ways including the following methods gt Benchmark testing gt Application vendor specifications based on benchmark testing gt Existing I O performance characteristics on existing storage being replaced by XIV Storage System It is the client s responsibility to provide performance requirements However IBM licenses a performance modeling and sizing tool called D
609. use the role cannot be uniquely identified In Example 5 20 the xivtestuser1 user can be mapped to Storage Admin and Read Only roles which is why the authentication failure followed by the USER HAS MORE THAN ONE RECOGNIZED ROLE error message occurs Example 5 20 LDAP user mapped to multiple roles authentication failure xcli c XIV 6000050 u xivtestuserl p PasswOrd Idap_user_test Error USER HAS MORE THAN ONE RECOGNIZED ROLE Details User xivtestuser has more than one recognized LDAP role ldapsearch LLL H Idap 9 155 113 143 389 D cn itso cn Users dc itso dc storage dc ibm dc com w PasswOrd b cn Users dc itso dc storage dc ibm dc com cn xivtestuserl member0f dn CN xivtestuserl CN Users DC itso DC storage DC ibm DC com memberOf CN XIVReadonly CN Users DC itso DC storage DC ibm DC com memberOf CN XIVAdmins CN Users DC itso DC storage DC ibm DC com Chapter 5 Security 237 An LDAP user can be a member of multiple Active Directory groups and successfully authenticate to an XIV Storage System if only one of those groups is mapped to an XIV Storage System role As illustrated in Example 5 21 the xivtestuser2 user is a member of two Active Directory groups XIVAdmins and NonXIVgroup Only XIVAdmins is mapped to an XIV role Example 5 21 LDAP user mapped to a single roles authentication success xcli c XIV 6000050 u xivtestuser2 p Passw0rd ldap user test Command executed successfully ldapsearch LLL H Idap
610. used for gathering additional information about hosts attached to the XIV User roles There is no capability to add new user roles or to modify predefined roles In native authentication mode after a user is assigned a role the only way to assign a new role is to first delete the user account and then re create it Table 5 2 shows the predefined users and their roles Table 5 2 Predefined user role assignment reetnedeer ere xiv_msms storageadmin Native authentication mode implements user role mechanism as a form of role based access control RBAC Each predefined user role determines the level of system access and associated functions that a user is allowed to use RBAC The XIV Storage System implements role based access control RBAC based authentication and authorization mechanisms All user accounts must be assigned to a single user role Assignment to multiple roles is not permitted Deleting or modifying role assignment of natively authenticated users is also not permitted User groups A user group is a group of application administrators who share a set of snapshot creation permissions The permissions are enforced by associating the user groups with hosts or clusters User groups have the following characteristics gt Only users assigned to the applicationadmin role can be members of a user group gt A user can be a member of a single user group Chapter 5 Security 189 gt A maximum of eight user groups
611. used to confirm the status of the InfiniBand switches If you hover your cursor over a switch as shown in Figure 7 19 a window opens and shows the status of that switch IB Switch 2 PS1 Power OK PS Power OK Status OK Ports OK Figure 7 19 Monitoring UPS InfiniBand switches 294 IBM XIV Storage System Architecture and Implementation Monitoring the Maintenance Module The XIV Storage Management GUI can be used to confirm the status of the Maintenance Module If you hover your cursor over a switch as shown in Figure 7 20 a window opens and shows the status of that module Maintenance Module Status OK Figure 7 20 Monitoring Maintenance Module Monitoring each module and disk status and temperature The XIV Storage Management GUI can be used to monitor the status of each XIV Storage System module and each XIV Storage System disk You can hover the cursor over a module in the location shown in Figure 7 21 The cursor changes to a magnifying glass icon By hovering the cursor over this location you can confirm the health of each module component and the module s temperature Module 7 93 0_ interface Temperature 69 F Status OK Data Service OK Interface Service OK Remote Semice OK PSUs OK Fans OK SSD OK Figure 7 21 Module status Chapter 7 Monitoring 295 If you left click the module the module is removed from the rack and the status of the module components can be verified by hove
612. used with the XIV Storage Management GUI The three step process includes all the required configurations to allow the XIV Storage System to provide notification of events gt Gateway gt Destination gt Rules The gateway definition is used for SMTP and SMS messages There are various commands that are used to create and manage the gateways for the XIV Storage System Example 7 25 shows an SMTP gateway being defined The gateway is named test and the messages from the XIV Storage System are addressed to xiv us ibm com When added the existing gateways are listed for confirmation In addition to gateway address and sender address the port and reply to address can also be specified There are various other commands that are available for managing a gateway Example 7 25 The smtpgw_define command gt gt smtpgw_ define smtpgw test address test ibm com from_address xiv us ibm com Command executed successfully gt gt smtpgw_list Name Address Priority ITSO Mail Gateway us ibm com 1 test test ibm com 2 The SMS gateway is defined in a similar method The difference is that the fields can use tokens to create variable text instead of static text When specifying the address to send the SMS message tokens can be used instead of hardcoded values In addition the message body also uses a token to have the error message sent instead of a hardcoded text 322 IBM XIV Storage System Architecture and Implementation Gateways An SMTP gate
613. usters icon and select Hosts and Clusters see Figure 4 61 Hosts and Clusters l QoS Performance Class Hosts Connectivity N Volumes by Hosts iSCSI Connectivity Figure 4 61 Hosts and Clusters menu 2 The Hosts window opens and shows a list of hosts if any that are already defined To add a host or cluster click either Add Host or Add Cluster in the menu bar see Figure 4 62 In our example we select Add Host Add Host is used for a single host that is assigned a LUN or multiple LUNs Add Cluster is used for a group of hosts that share a LUN or multiple LUNs File View Tools Help A O Hi Add Host oi Add Cluster Figure 4 62 Add new host 3 The Add Host window opens as shown in Figure 4 63 on page 160 From the System Cluster drop down menu choose a cluster for the host choose Standalone Hosts for no cluster Enter a Name for the host Select a Type for the host choose the default unless the host type is hpux or zvm Important Do not change the host type of a host that has mapped volumes because the volumes will be inaccessible to the host If you need to change the host type remove all mappings first change the host type and remap the volumes afterward Chapter 4 IBM XIV Storage Management software 159 4 Optionally if this host will use Challenge Handshake Authentication Protocol CHAP authentication for IP network Small Computer System Interface iSCSI enter values for CHAP Name
614. vailable within the XIV Storage System Obviously the system s hard capacity is the upper limit of the aggregate hard capacity of all the volumes and snapshots and can be increased only by installing new hardware components in the form of individual modules and associated disks or groups of modules There are conditions that can temporarily reduce the system s hard limit For more details see 2 7 2 Preserving data redundancy Rebuilding and redistributing on page 48 Soft system size The soft system size is the total global and logical space available for all storage pools in the system When the soft system size exceeds the hard system size it is possible to logically provision more space than is physically available allowing the benefits of thin provisioning of storage pools and volumes to be realized at the system level The soft system size limits the soft size of all volumes in the system and has the following attributes gt Itis not related to any direct system attribute and can be defined to be larger than the hard system size if thin provisioning is implemented The storage administrator cannot set the soft system size Storage pools If the storage pools within the system are thinly provisioned but the soft system size does not exceed the hard system size the total system hard capacity cannot be filled until all storage pools are regularly provisioned Therefore it is best to define all storage pools in a
615. ve the CER signed by a CA Then import the signed certificate into the local keystore import a CA certificate as a trusted root CA and then restart the LDAP server for the new configuration to take effect Generating a Sun Java Directory server certificate request To generate a certificate request using the Sun Java Web Console tool complete the following steps 1 Point your web browser to HTTPS port 6789 in our example https xivhost2 storage tucson ibm com 6789 2 Log on to the system and select Directory Service Control Center DSCC and authenticate to Directory Service Manager 3 Click Directory Servers xivhost2 storage tucson ibm com 389 Security gt Certificates Request CA Signed Certificate Complete the certificate request form A sample of the certificate request form is shown in Figure B 13 Request CA Signed Certificate This will generate a certificate request The text of the request will appear on the progress dialog This text should be submitted to a Certificate Authority who will process it and issue a certificate You can submit the request either by sending the text in an amp mail message to the CA or by submitting it through the CA s web site Indicates required field Server xivhost2 storage tucson ibm cam 389 eee Specify Values Separately Common Name ieni xiv hest2 storage tucson ibm com Organization o xivstorage Organizational Unit fou ITSO City Locality 1
616. verity of Warning which indicates that the status is now Ready Each alert appears in IBM XIV Systems Alerts tab with the Resolution State New Change it manually to Closed if necessary as shown in Figure 7 111 Monitoring lt Alerts 19 4 B Monitoring 4 Look for Find Now Clear iis So a senese I Path Source Name Resolution Sate Created R Agentless Exception Monitoring 4 Severity Critical 1 Application Monitorin ee a a i 2 Lx rrr ae New 9 24 2013 2 31 00 PM C Data WWarehouse Open gt 4 Severity 3 cA IBM System Storage il Notification subscripti 44 ption 27 4 Ga IBM XIV ay A W2K12 ee New 9 24 2013 1 37 43 PM gt Alerts A waki Set Resolution State New 9 24 2013 1 37 41 PM Events W2kig Close Alert Awaiting Evidence 9 24 2013 1 37 41 PM 55 Systems A WK Forward to Assigned to Engineering 9 24 2013 1 27 42 PM Logical Components A wki Maintenance Mode Acknowledged 9 24 2013 1 27 42 PM Eg Physical Components A W2K12 Bo d Scheduled 9 24 2013 1 27 42 PM werrides b C Microsoft Audit Collection Series A W2K12 y sae ne Resolved 9 24 2013 1 27 42 PM i j i lew or edit the settings of this monitor A a ee aes A wok Refresh F5 New 9 24 2013 1 27 42 PM a Network Monitoring lt Personalize wiew C Operations Manager _ Synthetic Transaction Alert Det cd Properties CA UNIX Linux Computers i r i CA Web Application Transacti
617. vol E andy_vol snapshot_00007 dirk_test dirk_test GR_Poolt data_1 103 GB data_ 103 GB data 3 103 GB data_4 103 GB Figure 4 18 Tree lable Export to comma separated values format In addition to the previously supported events and statistics frames the XIV Storage Management GUI Version 4 3 supports exporting to comma separated values CSV for all GUI tabular views The new Export icon is available for all these views as shown in Figure 4 19 When the icon is clicked a window opens prompting you to save the export file to your local workstation we songe venanen o a Systems Actions View Tools Hep A O gt Add Voldr i A AN Systems 8 gt Tucson Lab 0 gt v Volumes and Snapshots m Name Size GB Used GB Consistency Figure 4 19 Export to CSV icon Chapter 4 IBM XIV Storage Management software 119 Regional settings and time zone awareness It is common for storage administrators to manage storage systems from locations that are geographically separated from those systems GUI Version 4 enhances support for this scenario by introducing time zone awareness Throughout the GUI many details can be displayed in both system time time on the XIV Storage System and local time time on the workstation running the GUI To configure the regional settings for the GUI click Tools in the menu bar click Management and then click the Regional Settings tab as shown in
618. volume can be specified either in gigabytes GB gibibytes GiB or in blocks where each block is 512 bytes If the size is specified in blocks volumes are created in the exact size specified and the size is not rounded up It means that the volume shows the exact block size and capacity to the hosts but consumes a 17 GB size in the XIV Storage System This capability is relevant and useful in migration scenarios If the size is specified in GB the actual volume size is rounded up to the nearest 17 1 GB multiple making the actual size identical to the free space consumed by the volume This rounding up prevents a situation where storage space is not fully used because of a gap between the free space used and the space available to the application If the size is specified in GiB the volume is specified in binary gigabytes in multiples of 299 and is rounded up to the nearest 16 GiB multiple which is physically the same total size as the equivalent reported gigabyte size 152 IBM XIV Storage System Architecture and Implementation GB versus GiB and XIV Storage System volumes gt A gigabyte is a decimal multiple of a byte unit 1 GB equals 10 bytes 1 000 000 000 bytes gt A gibibyte is a binary multiple of a byte unit 1 GiB equals 2 bytes or 1 073 741 824 bytes When you create a volume on an XIV Storage System it allocates multiples of 17 1 GB 16 GiB The volume is logically formatted at creation time which mean
619. wOrd cn grep cn cn Users cn krbtgt cn itso appuserl cn Domain Computers cn Domain Controllers cn xivtestuser3 The queries generating LDAP account lists are provided as a demonstration of LDAP tools capabilities to perform a search of information stored in the LDAP directory and generate simple reports Both queries are issued on behalf of the LDAP administrator account cn Manager OpenLDAP cn Directory Manager Oracle Sun Java Directory and cn Administrator Active Directory A privileged account such as LDAP administrator has the authority level that allows it to list create modify and remove other user accounts The Active Directory management interface allows you to build custom views based on LDAP search queries Figure 5 70 shows the building of a query that generates the list of XIV Storage System accounts whose names start with XIV and whose description is one of the following three Storage Administrator Read Only or starts with app Active Directory Users and Computers Iofs File Action View Help w 4 X E ds BR Batra E Active Directory Users and Comput Type Description El C Saved Queries XIV Admin User Admin H Maly Storage Accounks x sivcestuserl User gJ itso storage ibr com Figure 5 70 Active Directory query listing XIV accounts Chapter 5 Security 229 To generate the XIV Storage System Accounts view we used the LDAP query that is shown in Exam
620. way must be defined before you can define an SMS gateway because SMS messages are sent from the XIV Storage System in the form of an email Example 7 26 provides an example of defining an SMS gateway The following tokens are available to be used for the SMS gateway definition gt areacode This escape sequence is replaced by the destination s mobile or cellular phone number area code gt number This escape sequence is replaced by the destination s cellular local number gt message This escape sequence is replaced by the text to be shown to the user gt These symbols are replaced by the for or for Example 7 26 The smsgw_define command gt gt smsgw define smsgw test email_address areacode number smstest ibm com subject_line XIV System Event Notification email _body message Command executed successfully gt gt smsgw_list Name Email Address SMTP Gateways test areacode number smstest ibm com all When the gateways are defined the destination settings can be defined There are three types of destinations gt SMTP or email gt SMS gt SNMP Example 7 27 provides an example of creating a destination for all three types of notifications For the email notification the destination receives a test message every Monday at 12 00 Each destination can be set to receive notifications on multiple days of the week at multiple times Example 7 27 Destination definitions
621. wing the completed percentage of the rebuilding progress The percentage completed is in light green and is reported in our example as 30 complete The percentage that is yet to be completed is in yellow Remember that the redistribution process is also running even though the XIV Storage Management GUI reports only the rebuilding xv XIV Storage Management mm X File View Tools Help Settings MJ Launch xci BMJ Launch xiv Top itso XIV 02 1310114 System System Time 12 00pm A elkr eas aS 3 61 E Cos ETE total Figure 2 11 Rebuilding If there is a disk failure in a fully configured XIV Storage System there are only 168 disks reading because there is no non redundant data on the other disks within the same module as the failed disk Concurrently there are 179 disks writing to preserve full data distribution Chapter 2 IBM XIV Storage System logical architecture and concepts 49 lf there is a module failure the copies of non redundant data are read from all the remaining modules in the system because none of the disks within a given module contain the secondary copies of data on any of the disks in the module Therefore during a rebuild resulting from a module failure in a fully configured XIV Storage System there are concurrently 168 disks 180 disks in the system minus 12 disks in a module reading and 168 disks writing Important The rebuilding phase is a high priority self healing process to res
622. with two filters combined gt gt event_list max_events 5 before 2013 03 08 18 00 00 Timestamp Severity Code User Description 2013 03 08 16 23 09 Informational USER LOGIN HAS SUCCEEDED User xiv_maintenance from IP 2013 03 08 16 23 41 Informational TARGET CONNECTION ESTABLISHED Target named XIV_04 1340008 2013 03 08 16 23 41 Informational TARGET CONNECTION ESTABLISHED Target named XIV_04 1340008 2013 03 08 16 24 14 Warning USER_HAS_ FAILED TO RUN COMMAND User xiv_administrator from 2013 03 08 16 28 35 Informational USER LOGIN HAS SUCCEEDED User xiv_development from IP 302 IBM XIV Storage System Architecture and Implementation The event list can also be filtered for severity Example 7 16 shows all the events in the system that contain a severity level of Major and all higher levels such as Critical Example 7 16 The event_list command filtered for severity gt gt event_list min_severity Major max_events 5 Timestamp 2013 03 18 13 05 20 2013 03 18 13 05 43 2013 03 19 14 27 22 2013 03 19 14 27 40 Severity Code User Description Major TARGET DISCONNECTED Target named XIV_04 1340008 i Major TARGET LINK DOWN BEYOND THRESHOLD Target named XIV_04 1340008 Major TARGET DISCONNECTED Target named XIV_04 1340008 Major TARGET LINK DOWN BEYOND THRESHOLD Target named XIV_04 1340008 Certain events generate an alert message and do not stop until the event has been cleared These events are called alerting events and can b
623. wn in Figure 7 87 ie IBM Tivoli Storage Productivity Center sspc sle 1 Create Subsystem Performance Monitor Fie view Connection Preferences Window Help Element Management m a x amp javigation Tree Create Subsystem Performance Monitor Administrative Services Creator administrator Name unnamed IBM Tivoli Storage Productivity Center a Configuration Utility Description Configure Devices Enabled v Job Management Reporting Topology Available subsystems Selected subsystems Monitoring I 2810 6000105 IBM Storage Resource Group Management Analytics Alerting Storage Subsystems Sampling and Scheduling Alert Data Manager for Databases Data Manager for Chargeback Disk Manager Storage Subsystems Storage Optimizer SAN Planner Monitoring Groups Jobs a Alerting Profile Management Reporting Fabric Manager Tape Manager Element Manager Replication Manager Figure 7 87 Subsystem Performance Monitors panel Optional You can also click Disk Manager Monitoring gt Subsystem Performance Monitors to open the Subsystem Performance Monitors view 2 Afterward select the XIV Storage System and click the double arrow icon to move the selected system from the Available subsystems into the Selected subsystems section 3 Click Save and specify the subsystem performance monitor name Afterward the subsystem pe
624. xt to continue Click the Local Computer option to manage certificates on the local computer only Click Finish then Close and then OK to complete the snap in installation Click File gt Save as and save the console configuration in the SYSTEMROOT system32 directory with a file name of localcert msc Create a shortcut in the Administrative Tools folder in your Start menu by right clicking the Start menu and then Open All Users Click the Program folder and then the Administrative Tools folder Click File New Shortcut Enter the location of the saved console SYSTEMROOT system32 localcert msc in the Type the location of the item field Click Next to continue Enter the name of the new shortcut Certificates Local Computer in the Type a name for this shortcut field 10 To start the local certificate management tool click Start Administrative tools gt Certificates Local Computer Appendix B Additional LDAP information 417 418 When the local certificate management tool starts it appears as shown in Figure B 10 The certificates used by Active Directory are in the Console Root Certificates Local Computer Personal Certificates folder The list of trusted root certificates authorities is in the Console Root Certificates Local Computer Trusted Certification Authorities Certificates folder vai localcert Console Root Certificates Local Co
625. y 1 days Figure 7 83 Specifying probe details Specify the probe details Use a monitoring group or template Select the predefined Monitoring Group or create your own new group by selecting Monitoring Template Select monitoring group Specify Subsystem Advanced Group Subsystem Basic Group or Subsystem Standard Group Tip Configure individual probes for every XIV Storage System system but set them to run at various times After clicking Next you get an overview of your configured probe Figure 7 84 shows the details of the Subsystem Standard Group including the scheduling of the probe and the alerts Monitoring Group Subsystem Standard Group TPCUser Subsystem Standard Probe Run repeated beginning at Oct 6 2010 1 00 00 AM Run on these days Monday Wednesday The selected group partakes in 16 alert definitions Alerts Pool Discovered Standard Pool Status Change Offline Standard Pool Status Change Online Standard Pool Capacity Change Standard Yolume Not Found Standard Figure 7 84 Probe summary Confirm the summary by clicking Next Click Finish and a background probe is started automatically Click IBM Tivoli Storage Productivity Center Configuration Utility Disk Manager to check the status of your XIV Storage System You can also use the Disk Manager to run a new Discovery to create a probe or to modify the alerts Figure 7 85 on page 359 IBM XIV Stor
626. y Center V4 1 x Tivoli Storage Productivity Center manages and monitors the XIV Storage System through its CIM agent embedded in the XIV Storage System code You need to upgrade to Tivoli Storage Productivity Center V4 2 or later so that you can use the new data collection process and the Native API to interface with the XIV Storage System To add an XIV Storage System to your Tivoli Storage Productivity Center configuration complete the following steps 1 Create an XIV Storage System user and password that will be used by Tivoli Storage Productivity Center 2 Note the IBM XIV Storage System management IP address 3 Start the Tivoli Storage Productivity Center configure devices wizard to discover and probe the XIV Storage System 4 Create a performance monitor XIV Storage System user creation Create a normal XIV Storage System user and password on the XIV Storage System by using the XIV Storage Management GUI as shown in Figure 7 78 on page 355 This user and password is used in Tivoli Storage Productivity Center 354 IBM XIV Storage System Architecture and Implementation Add User X Name tpcadmin New Password 6 12 eecccces Retype New Password TTT Category Read Only M User Group None Email Address Phone Number Figure 7 78 User creation XIV Storage System management IP addresses To add an XIV Storage System into Tivoli Storage Productivity Center you must know the management I
627. y Groups gt XIV 1310039 C gt System System Time SSD 1 Status OK AAA are Module 5 29 C Status Figure 4 73 SSD status Tip Flash cache can be dynamically enabled and disabled at any time Setting flash cache at the system level By default flash cache is enabled for all volumes defined in the XIV system To enable or disable flash cache for the entire XIV system select Settings from the toolbar in the main System view as indicated in Figure 4 74 File View Tools Help 1 inge Launch xcLi f Launch xivTop All Systems View By My Groups gt XIV 1310039 C Figure 4 74 Opening system settings Chapter 4 IBM XIV Storage Management software 167 The system Settings panel is displayed Select the Parameters tab The Global SSD Flash Caching default can be set to Enabled or Disabled as shown in Figure 4 75 XIV 1310039 Coruscant Settings General iSCSI Name iqn 2005 10 com_xivstorage 010039 Parameters Time one US Arizona NTP Server 9 11 107_12 wal DNS Primary 2002 90b e0f2 208 202 55ffe5d dbcc Misc DNS Secondary Yes Global SSD Caching Enabled ere a Cancel Figure 4 75 System settings for Global SSD Caching By default a newly created volume follows the System Level Settings System Level Settings gt If flash cache is disabled from System Level Settings it is disabled by default for every new volume defined gt If flash cache is enabled from
628. y Protocol KMIP Version 1 0 This methodology provides a centralized and simplified key management and the separation of key storage from data storage Figure 2 9 shows the initial configuration Encryption Initial Configuration 1 Configure TKLM J 2 Point XIVto TKM mp 5 Request amp Receve ESK 4 XIV configures disks with XMK den ved per disk key 6 Use ESK to Wrap XMK 3 AIV generates random XMK T Store weapped XMK Figure 2 9 Encryption Initial configuration For more information see the IBM Redpaper X V Security with Data at Rest Encryption REDP 5047 2 7 Reliability Availability and Serviceability RAS The XIV Storage System unique modular design and logical topology fundamentally differentiate it from traditional monolithic systems This architectural divergence extends to the exceptional reliability availability and serviceability aspects of the system In addition the XIV Storage System incorporates autonomic and proactive monitoring and self healing features that can transparently and automatically restore the system to full redundancy within minutes of a hardware failure and take preventive measures to preserve data redundancy even before a component malfunction occurs For more information about the XIV Storage System parallel modular architecture see 2 2 Parallelism on page 21 Chapter 2 IBM XIV Storage System logical architecture and concepts 43 2 1 Resilien
629. y XIV Storage System Interface Module Experience has shown that the first multipathing configuration in Figure 3 28 is the best overall general purpose configuration Host multipathing reliability during path error recovery in some operating systems is complicated by increasing numbers of paths per logical unit number LUN Certainly for host systems with two HBAs using the six paths per LUN is a best practice Tip Six paths per LUN is the best practices multipathing configuration There is no performance or reliability benefit in using too many paths Going beyond 12 paths per volume has no benefit because most operating systems have more processing overhead handling the paths and cause longer times for recovery Going beyond six paths rarely has much benefit Use four or six paths per volume as a standard Do not go below four paths Figure 3 28 shows how six paths per LUN is the best overall multipathing configuration Q ur gt V Q O 4 T O eur gt gt lt m Patch Panel FC Ports Figure 3 28 Six paths per LUN is the best overall multipathing configuration The following information relates to Figure 3 29 on page 91 gt Each host is equipped with dual HBAs Each HBA or HBA port is connected to one of two FC switches gt Each of the FC switches has a connection to three separate Interface Modules gt Each LUN has six paths The second multipathing configuration that is shown in Figu
630. y even after failures in components other than disks such as a failure of a whole module 1 5 4 Fast drive rebuild The enhanced XIV architecture improves drive rebuild time For example the rebuild time of a fully utilized 2 TB drive can be as fast as 26 minutes even under a heavy load 1 5 5 True virtualization Unlike other system architectures storage virtualization is inherent to the basic principles of the XIV Storage System design Physical drives and their locations are hidden from the user which dramatically simplifies storage configuration letting the system lay out the user s volume in the optimal way The automatic layout maximizes the system s performance by using system resources for each volume regardless of the user s access patterns With the XIV Storage System design you no longer must decide which type of data protection to use for storing data or how many drives you need to dedicate for a specific application Allocate the needed storage space and the system does the rest This feature allows the user to respond to growing storage needs in minutes instead of hours or days as with traditional storage systems 6 IBM XIV Storage System Architecture and Implementation 1 5 6 Flash caching optional For ultra high performance needs XIV Gens optionally offers up to 12 TB of management free flash caching which is available to all system data and can be installed nondisruptively Operating with advanced flash algorit
631. ystem You can use SNMP walk and get commands using the IBM supplied XIV SNMP Management Information Base MIB to monitor the health of the XIV Storage System If you have IBM Systems Director you can configure it to get SNMP events from the XIV Storage System If you are using Microsoft System Center Operations Manager you can use it to monitor your XIV Storage System In addition the secure remote support feature allows remote monitoring and repair by IBM support personnel We also describe the call home function secure remote support and repair procedures Finally the Host Attachment Kit now offers a data collection feature that can be used for problem analysis It is described at the end of this chapter Copyright IBM Corp 2013 All rights reserved 285 7 1 Monitoring with XIV Storage Management GUI and XCLI The XIV Storage Management graphical user interface GUI and XIV Storage System Command Line Interface XCLI include many features that allow you to monitor the system These features include monitoring for alerts events and failed components 7 1 1 Monitoring by using the Systems menu 286 You can show the health state alerts and events for multiple IBM XIV systems from the Systems menu By selecting the Systems view as shown in Figure 7 1 you can work witha particular storage system or show All Systems Alerts or All Systems Events for every XIV Storage System defined to the GUI The Systems menu does not
632. ystem In the following section we describe predefined roles their level of access and applicable use The roles are as follows gt storageadmin The storageadmin Storage Administrator role is the user role with the highest level of access available on the system A user assigned to this role can perform changes on any system resource except for maintenance of physical components or changing the status of physical components The assignment of the storageadmin role to an LDAP user is done through the LDAP role mapping process For a detailed description see 5 6 4 LDAP role mapping on page 208 gt applicationadmin The applicationadmin Application Administrator role is designed to provide flexible access control over volume snapshots Users that are assigned to the applicationadmin role can create snapshots of specifically assigned volumes perform mapping of their own snapshots to an assigned host and delete their own snapshots The user group to which an application administrator belongs determines the set of volumes that the application administrator is allowed to manage If a user group is defined with access all yes application administrators who are members of that group can manage all volumes on the system The assignment of the applicationadmin role to an LDAP user is done through the LDAP role mapping process For a detailed description see 5 6 4 LDAP role mapping on page 208 A detailed description of user
633. zed for flexibility so that as newer and higher performing components are made available in the marketplace development is able to incorporate this newer technology into the base system design at a faster pace than was traditionally possible The following sections describe the hardware components that build up the XIV Storage System For more detailed planning information see 3 2 Hardware planning overview on page 87 Also see the BM XIV Storage System Planning Guide The latest version of the planning guide is available in both PDF format and HTTP format from the XIV Storage System Information Center at the following location http publib boulder ibm com infocenter ibmxiv r2 index jsp All XIV Storage System Gens configurations have the following components Rack Power components Data Modules and Interface Modules InfiniBand module interconnect Patch panel Support hardware YYYY YV Y Hardware Because the XIV Storage System hardware architecture is designed using off the shelf components and can easily adapt to new hardware it is possible that there will be hardware changes before this book is refreshed 3 1 5 Rack All of the XIV Storage System hardware components are installed in an IBM T42 rack as shown in Figure 3 6 on page 66 Adequate space is provided to house all components and to properly route all cables The rack door and side panels can be locked with a key to prevent unauthorized access to the installed com

Download Pdf Manuals

Related Search

Related Contents

2kw Downflow Fan Heater Installation and Operating Instructions  LTM 1160-5.1  RADIO STROBE VARIANT INSTALLATION MANUAL    図面集のご利用にあたって  Parker Products OPS1200 User's Manual  Technical Organization  AV Center 取扱説明書  

Copyright © All rights reserved. Failed to retrieve file