The following will provide the XIV Storage Administrator an understanding of how to
work with both the GUI and xCLI for storage provisioning operations.
Host presentation
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 Volume
To 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 Definition
Under Hosts, right click and select ‘Add Host’
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 Operation
Present the Volume to the Host
Select 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.
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
Open the host and complete the following for each HBA
• Right Click on the HBA
• Select Delete
Host presentation
This process outlines defining a HP host AND including both HBAs in one host
definition
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_srv1
No Mappings
Step 6: Shows the Volume is not listed in the overall list of Volumes
xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD vol_list
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.
Warning: ARE_YOU_SURE_YOU_WANT_TO_DELETE_VOLUME
Step 7b: Verify the volume has been deleted from the XIV
List all volumes to see that the LUN has been deleted.
xcli -m XIV_IP -u XIV_USERID -p XIV_PASSWORD vol_list
test_srv1 default
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.
Performance
The first item to note is the current IOPS for the system is always displayed in the bottom
center 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 the
Monitor 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 displaying
IOPS.
The statistics monitor also illustrates latency and bandwidth.
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 vs. Misses), or
transfer size of I/O as seen by the XIV Storage System. See Figure 9-5 for a better view of the
filter pane.
The filter pane allows the user to select multiple items within a specific filter. For example, the
user 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 user
witnesses both items displayed on the graph.
Alert and Problem History
Monitor - Events
To 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. The
system captures entries for problems with different levels of severity, including warnings and
other informational messages. These informational messages include detailed information
about 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. Without
filtering the events it would be extremely difficult to find the entries for a specific incident or
information.
If you double click on a specific event in the list, you can get more detailed information about
that 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. Transaction
audit with user can only be performed on the XCLI.
Audit
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.
This command shows when new users where created and who created them. It does not
display what userID was created.
:user_defined example
xcli -m 167.210.165.5 -u USERID -p PASSWORD event_list "code=user_defined"
Index Code Severity Timestamp Alerting Cleared User
17 USER_DEFINED Informational 2008-10-14 19:35:06 no yes admin
18 USER_DEFINED Informational 2008-10-14 19:35:50 no yes admin
46 USER_DEFINED Informational 2008-10-15 15:21:01 no yes pjlongse
314 USER_DEFINED Informational 2008-11-21 03:01:11 no yes erust
:user_group_created example
xcli -m 167.210.165.5 -u USERID -p PASSWORD event_list
"code=user_group_created"
Index Code Severity Timestamp Alerting Cleared User
315 USER_GROUP_CREATED Informational 2008-11-21 03:03:45 no yes erust
:access_to_host_granted_to_user_group example
xcli -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 User
317 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 User
308 HOST_DISCONNECTED Informational 2008-11-20 17:56:44 no yes
309 HOST_CONNECTED Informational 2008-11-20 17:56:44 no yes
310 HOST_NO_MULTIPATH_ONLY_ONE_PORT Informational 2008-11-20
17:56:49 no yes
311 HOST_DISCONNECTED Informational 2008-11-20 20:07:59 no yes