XIV Storage Administrative Procedures

The following will provide the XIV Storage Administrator an understanding of how to work with both the GUI and xCLI for storage provisioning operations.

Storage Provisioning Using the XIV GUI...........................................................................2Host presentation.........................................................................................................2Step 1: Create a Storage Pool......................................................................................2Step 2: Create a Volume..............................................................................................4Step 3: Add a Host Definition.....................................................................................6Step 4: Add Host Port(s) to the Host Definition..........................................................8Step 5: LUN Mapping Operation...............................................................................9Growth of existing host.............................................................................................11Host removal..............................................................................................................12

Storage Provisioning Using the XIV Command Line Interface (xcli)..............................16Host presentation...........................................................................................................16

Step 1: Create a Storage Pool....................................................................................16Step 2: Create a Volume............................................................................................16Step 3: Add a Host Definition...................................................................................16Step 4: Add Host Port(s) to the Host Definition........................................................17Step 5: LUN Mapping Operation.............................................................................17Growth of existing host.............................................................................................18

Host Removal (xcli).......................................................................................................19Step 1: Obtain the Host Name...................................................................................19Step 2: Determine what Volume(s) are presented to the host...................................19Step 3: Determine if the Volume(s) is presented to more than one host...................19Step 4: Unmap the Volume from the host.................................................................20Step 5: Verify that the host does not have any remaining volumes...........................20Step 6: Shows the Volume is not listed in the overall list of Volumes....................20Step 7: Delete the volume..........................................................................................21Step 7a: Volume Deletion..........................................................................................21Step 7b: Verify the volume has been deleted from the XIV......................................21Step 8a: HBA Removal.............................................................................................22Step 8b: HBA removal verification...........................................................................22Step 9a: Host Definition Removal.............................................................................22Step 9b: Host Definition Removal Verification........................................................23

Volume Resizing (both directions)....................................................................................23Reporting...........................................................................................................................24

Performance...................................................................................................................24Alert and Problem History.............................................................................................26

Monitor - Events........................................................................................................26Event severity:...........................................................................................................27

Audit..................................................................................................................................28Security User and Group Related..................................................................................28

Storage Provisioning Using the XIV GUI

Host presentation

Step 1: Create a Storage Pool

Once Pool screen comes up ‘Right Click’ in open area and select ‘Add Pool’.

Create the Pool based on your requirements.You can create a Regular Pool or Thin Provisioning Pool

The Pool ‘std_002’ is created. This screenshot shows the pool status.

Step 2: Create a VolumeTo create a new volume, click on View, Volumes, and select Volumes.

Once in the volumes screen, right click and select ‘Add Volumes’

Select your Pool that your Volume will be created in. Input Volume, Size, and Volume Name. Click Create.

Step 3: Add a Host DefinitionUnder Hosts, right click and select ‘Add Host’

Enter the name of the host and click ‘Add’

ONLY Complete this step if the host is running HP-UXIf your host is not running HP-UX go to Step 4.If the server is running HP-UX you MUST change the server type from ‘default’ to HP-UX. Complete this by right clicking on the host and selecting ‘Change Type’.

Select hpux and select ‘OK’.

Step 4: Add Host Port(s) to the Host DefinitionRight click on newly added host, test_srv2, and select Add Port

Select the Port Type (FibreChannel or iSCSI) and the server HBA wwpn that is going to be presented with XIV Storage and click ‘Add’. Zoning would have been completed prior to this step.Complete this for each HBA in this host.

Expand the server selection to show each of the HBA wwpns that you associated with the new host.

Step 5: LUN Mapping OperationPresent the Volume to the HostSelect View, Hosts and LUNs, and Hosts

Right Click on the host you created in Step 3 and select ‘Map Volumes to This Host’

In the Volumes Table, on left, highlight the Volume you would like to present to the host. It will automatically add it to the first LUN position in the LUNs table.You can change the LUN address if needed by clicking on an available LUN number in the LUNs table, on right.

Click the Map button to complete the LUN Mapping Operation.

You will see that the Volume is no longer available in the Volumes table. At this point the Server can access the storage volume.

Growth of existing host

Complete Step 2 and Step 5

Host removal

Select the Hosts Screen

Highlight the host and select ‘MapVolumes to This Host’

Under the LUNs column, on the right, highlight all of the LUNs from the host.Note: This step presumes all host side LUN operations have been completed by the SA.Click on the Unmap Button to remove the LUN(s) from the host.

Click OK to confirm the Host LUN removal operation.

Return to the Hosts Screen

Open the host and complete the following for each HBA Right Click on the HBA Select Delete

Answer OK for each HBA you delete

Return to the Hosts Screen and Right Click on the host you’re removing and select Delete

Click on OK to complete the Host Removal Process

Storage Provisioning Using the XIV Command Line Interface (xcli)

Host presentationThis process outlines defining a HP host AND including both HBAs in one host definition

Step 1: Create a Storage Poolxcli -m 167.210.165.5 -u USER_NAME -p PASSWORD pool_create "pool=thin_001" "size=50" "snapshot_size=0"Command executed successfully.

Note: snapshot_size must be entered regardless if snaps will be used or not.

Step 2: Create a Volumexcli -m 167.210.165.5 -u USER_NAME -p PASSWORD vol_create "vol= vol01_thin_01" "size=32" "pool=std_001"Command executed successfully.

Step 3: Add a Host Definitionxcli -m 167.210.165.5 -u USER_NAME -p PASSWORD host_define "host=hp_srv1"Command executed successfully.

xcli -m 167.210.165.5 -u USER_NAME -p PASSWORD special_type_set "host=hp_srv1" "type=hpux"Command executed successfully.

xcli -m 167.210.165.5 -u USER_NAME -p PASSWORD host_list

Name Type FC Ports iSCSI Ports User Group Clustermssw2000_a default 10000000C92A972Ctest_srv1_a default 1111111111111111test_srv1_b default 2222222222222222hp_srv1 hpux

Step 4: Add Host Port(s) to the Host DefinitionDefined 2 WWPNs to this host (cmds not shown for this example; see prior examples if needed)xcli -m 167.210.165.5 -u USER_NAME -p PASSWORD host_list

Name Type FC Ports iSCSI Ports User Group Clustermssw2000_a default 10000000C92A972Ctest_srv1_a default 1111111111111111test_srv1_b default 2222222222222222hp_srv1 hpux 0000000000000000,4444444444444444

Step 5: LUN Mapping OperationMap Volume to Host definitionxcli -m 167.210.165.5 -u USER_NAME -p PASSWORD map_vol "host=hp_srv1" "vol=vol01_thin_01" "lun=0"Command executed successfully.

List mappings for hp_srv1xcli -m 167.210.165.5 -u USER_NAME -p PASSWORD mapping_list "host=hp_srv1"LUN Volume Size Master Serial Number Locked0 vol01_thin_01 34 75 no

Growth of existing hostComplete Step 2 and Step 5 to add volumes to an existing host.

Host Removal (xcli)The following steps instruct you how to remove XIV Volumes (LUNs), HBAs, and Host Definitions from the XIV. In this example server test_srv1 will be removed.

Step 1: Obtain the Host NameThe Host Name is the name under the Name field. To confirm the host name, verify it matches the HBA that is in the host you are removing. The HBA WWPN is listed under FC Ports.

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD host_list

Name Type FC Ports iSCSI Ports User Group Clustermssw2003_a default 10000000C92A972C mssw2000 server

dis1tpc003_a default 10000000C92A94F0

test_srv1 default 210000E08B897BC2

Step 2: Determine what Volume(s) are presented to the hostYou supply the name of the host obtained in Step 1. Document the Volume(s) listed in the Volume column.

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD mapping_list host=test_srv1

LUN Volume Size Master Serial Number Locked1 vol002_std_002 17 85 no

Step 3: Determine if the Volume(s) is presented to more than one host. The actions you’d take would vary depending on your configuration and circumstances. In this example it shows the Volume is only presented to server test_srv1.

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD vol_mapping_list vol=vol002_std_002

Host/Cluster Type LUNtest_srv1 host 1

Step 4: Unmap the Volume from the hostYou must enter a –y on the command line to answer yes to remove the LUN. Two examples are provided, one of which does not include the –y.

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD unmap_vol host=test_srv1 vol=vol002_std_002Command executed successfully.

Step 5: Verify that the host does not have any remaining volumes.xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD mapping_list host=test_srv1No Mappings

Step 6: Shows the Volume is not listed in the overall list of Volumesxcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD vol_list

Name Size (GB) Master Name Consistency Group Pool Creator Used Capacity (GB)vol001_std_001 17 std_001 XIV_USERID 11vol002_std_002 17 std_001 XIV_USERID 0vol001_std_001.snapshot_00002 17 vol001_std_001 std_001 XIV_USERIDvol001_std_002 17 std_001 XIV_USERID 0test_vol_001 34 test_std_002 XIV_USERID 16

Only complete the remaining steps if the volume wasn't mapped to any other hosts/cluster. This will delete the Volume and the Host Definition form the XIV.

Step 7: Delete the volume. VERY IMPORTANT to have validated that the volume was not presented to any other hosts. Reference Step 2.

DO NOT PROCEED unless you have verified this volume is not mapped to any other hosts.

Step 7a: Volume DeletionYou must enter a –y on the command line to answer yes to delete the LUN. Two examples are provided, one of which does not include the –y.

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD vol_delete vol=vol002_std_002

Warning: ARE_YOU_SURE_YOU_WANT_TO_DELETE_VOLUME

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD vol_delete vol=vol002_std_002 -yCommand executed successfully.

Step 7b: Verify the volume has been deleted from the XIVList all volumes to see that the LUN has been deleted.xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD vol_list

Name Size (GB) Master Name Consistency Group Pool Creator Used Capacity (GB)vol001_std_001 17 std_001 XIV_USERID 11vol001_std_001.snapshot_00002 17 vol001_std_001 std_001 XIV_USERIDvol001_std_002 17 std_001 XIV_USERID 0test_vol_001 34 test_std_002 XIV_USERID 16

Step 8a: HBA RemovalThis removes the HBA WWPN which is associated to the host definition.

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD host_list

Name Type FC Ports iSCSI Ports User Group Clustermssw2003_a default 10000000C92A972C mssw2000 serverdis1tpc003_a default 10000000C92A94F0test_srv1 default 210000E08B897BC2

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD host_remove_port host=test_srv1 fcaddress=210000E08B897BC2Command executed successfully.

Step 8b: HBA removal verificationThis verifies the WWPN has been logically removed from the XIV

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD host_listName Type FC Ports iSCSI Ports User Group Clustermssw2003_a default 10000000C92A972C mssw2000 server

dis1tpc003_a default 10000000C92A94F0

test_srv1 default

Step 9a: Host Definition RemovalThis removes the host definition from the XIV. The HBA removal, step 8, should be completed prior.

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD host_delete host=test_srv1Warning: ARE_YOU_SURE_YOU_WANT_TO_DELETE_HOST

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD host_delete host=test_srv1 -yCommand executed successfully.

Step 9b: Host Definition Removal VerificationBy running a host listing for the entire XIV you can verify host ‘test_srv1’ has been removed.

xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD host_list

Name Type FC Ports iSCSI Ports User Group Clustermssw2003_a default 10000000C92A972C mssw2000 server

dis1tpc003_a default 10000000C92A94F0

Volume Resizing (both directions)

Resizing a volume requires you to issue a ‘-y’ flag, indicating Yes, to the resizing operation. The first example shows you what occurs if the –y flag is not issued.

xcli -m 167.210.165.5 -u USER_NAME -p PASSWORD vol_resize "vol=vol04_thin_pool_01" "size=34"Warning: ARE_YOU_SURE_YOU_WANT_TO_ENLARGE_VOLUME

xcli -m 167.210.165.5 -u USER_NAME -p PASSWORD vol_resize "vol=vol04_thin_pool_01" "size=34" -yCommand executed successfully.

Reporting

PerformanceThe first item to note is the current IOPS for the system is always displayed in the bottomcenter of the screen. This feature provides simple access to the current stress of the system.The following image displays the GUI and the IOPS display; this figure also describes how to start the statistics monitor.

Select the statistics option from the Monitor menu as shown in Figure 9-3 to display theMonitor default view shown in Figure 9-4.Figure 9-4 shows the system IOPS for the past 24 hours:_ 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 selected. In the default case it is displayingIOPS.The statistics monitor also illustrates latency and bandwidth.

The other options in the statistics monitor act as filters for separating data. These filters areseparated by the type of transaction (reads or writes), cache properties (Hits vs. Misses), ortransfer size of I/O as seen by the XIV Storage System. See Figure 9-5 for a better view of thefilter pane.

Figure 9-5 Filter pane for the statistics monitor

The filter pane allows the user to select multiple items within a specific filter. For example, theuser would like to see reads and writes separated on the graph. By holding down the <CTRL>key on the keyboard and selecting the read option and then the write option the userwitnesses both items displayed on the graph.

Alert and Problem History

Monitor - EventsTo get to the Events window, select Events from the Monitor menu as shown in the following figure. A lot of information and many different events are logged by the XIV Storage System. Thesystem captures entries for problems with different levels of severity, including warnings andother informational messages. These informational messages include detailed informationabout logins, configuration changes and status of attached hosts and paths.

Because many events are logged, the number of entries is typically huge.To get a more useful and workable view, there is an option to filter the events logged. Withoutfiltering the events it would be extremely difficult to find the entries for a specific incident orinformation.

If you double click on a specific event in the list, you can get more detailed information aboutthat particular event, along with a recommendation on what eventual action to take.

Event severity:The events are classified into different severities depending on their impact on the system.Figure 10-6 gives an overview of the criteria and meaning of the different severity levels.

The XIV GUI does not display the user who performed a transaction. Transactionaudit with user can only be performed on the XCLI.

Audit

Security User and Group Related

The Events tool allows you to filter based on Type ‘User’ or ‘User_Group’. You have other parameters you can combine within the filter. By selecting ‘User’ and clicking the Filter Button on the top Right, you will see any Events based on User related tasks that were completed. By selecting ‘User_Group’ and than filter, you can determine what group level Events were completed.

By double clicking on USER_DEFINED Event you can see what UserID was created. The same is true for any of the events, details about the event can be obtained by opening up that event.

All events or tasks performed can be determined by clearing all Filters.

User and Security Group Related using xcliUsing the event_list command you can query the XIV system based on prefined Event Codes. The xcli will provide you with the same output as the GUI and also displays what userID executed the event.

This command shows when new users where created and who created them. It does not display what userID was created.

:user_defined examplexcli -m 167.210.165.5 -u USERID -p PASSWORD event_list "code=user_defined"Index Code Severity Timestamp Alerting Cleared User17 USER_DEFINED Informational 2008-10-14 19:35:06 no yes admin18 USER_DEFINED Informational 2008-10-14 19:35:50 no yes admin46 USER_DEFINED Informational 2008-10-15 15:21:01 no yes pjlongse314 USER_DEFINED Informational 2008-11-21 03:01:11 no yes erust

:user_group_created examplexcli -m 167.210.165.5 -u USERID -p PASSWORD event_list "code=user_group_created"Index Code Severity Timestamp Alerting Cleared User315 USER_GROUP_CREATED Informational 2008-11-21 03:03:45 no yes erust

:access_to_host_granted_to_user_group examplexcli -m 167.210.165.5 -u USERID -p PASSWORD event_list code=access_to_host_granted_to_user_group"Index Code Severity Timestamp Alerting Cleared User317 ACCESS_TO_HOST_GRANTED_TO_USER_GROUP Informational 2008-11-21 03:06:30 no yes erust

:event_list without any event codes in the filter will supply you with all events xcli -m 167.210.165.5 -u USERID -p PASSWORDevent_list "after=2008-11-20.00:00:00"Index Code Severity Timestamp Alerting Cleared User308 HOST_DISCONNECTED Informational 2008-11-20 17:56:44 no yes309 HOST_CONNECTED Informational 2008-11-20 17:56:44 no yes310 HOST_NO_MULTIPATH_ONLY_ONE_PORT Informational 2008-11-20 17:56:49 no yes311 HOST_DISCONNECTED Informational 2008-11-20 20:07:59 no yes