SVC setup steps Assuming that the SVC or Storwize V7000 is zoned to the XIV, switch to the SVC or Storwize V7000 and run the following commands: 1. Detect the XIV volumes either by using the svctask detectmdisk CLI command, or use the SVC or Storwize V7000 GUI shown in Figure 11 to click Pools MDisks by Pools Detect MDisks . Figure 11 Detecting MDisks by using the SVC or Storwize V7000 GUI 2. List the newly detected MDisks, shown in Figure 12 on page 22 and Example 14 on page 22, where there are three free MDisks. They are 2.91 TiB in size (3201 GB).
22 IBM XIV Gen3 with IBM System Storage SAN Volume Controller and Storwize V7000 Figure 12 XIV MDisks detected by the SVC or Storwize V7000 Example 14 Command for New XIV MDisks detected by SVC IBM_2076:V7000-ctr-10:superuser> lsmdisk -filtervalue mode=unmanaged id name status mode mdisk_grp_id mdisk_grp_name capacity .... 1 mdisk1 online unmanaged 2.9TB .... 2 mdisk2 online unmanaged 2.9TB .... 3 mdisk3 online unmanaged 2.9TB .... 3. Create a pool (or MDisk group) on the SVC or Storwize V7000 by clicking New Pool . Figure 13 shows the Create Pool window. Figure 13 Create an MDisk group or pool by using the XIV MDisks 4. When you are prompted, select which MDisks to place into the pool, as shown in Figure 14 on page 23.
IBM XIV Gen3 with IBM System Storage SAN Volume Controller and Storwize V7000 23 Figure 14 Select MDisks to include in the SVC or Storwize V7000 pool In the Storwize V7000 or SVC GUI, there is no way to define the extent size for the pool. It defaults to 256 MB for SVC or Storwize V7000 firmware versions before 7.1. With 7.1, it defaults to 1024 MB. The SVC CLI offers the choice to specify a different extent size, but it also defaults to 256 MB before firmware Version 7.1. This is not an issue. However, if you choose to use the CLI, you can specify an extent size of 1024 MB, as shown in Example 15. Example 15 Command to create the MDisk group IBM_2076:V7000-ctr-10:superuser> svctask mkmdiskgrp -name XIV_02 -mdisk 1:2:3 -ext 1024 MDisk Group, id , successfully created 5. Relocate quorum disks, if necessary, as documented in “Using an XIV system for SVC or Storwize V7000 quorum disks” on page 15. Important: Adding a new managed disk group to the SVC might result in an SVC or Storwize V7000 report that you exceeded the virtualization license limit, with an event code 3025 or a message, such as CMMVC6373W: The virtualized storage capacity that the cluster is using exceeds the virtualized storage capacity that is licensed . Although this does not affect operation of the SVC, you continue to receive this error message until you correct the situation either by removing the MDisk group or by increasing the virtualization license. If you are not replacing the non-XIV disk with the XIV, ensure that you purchased an additional license. Then, increase the virtualization limit by using the svctask chlicense -virtualization xx command (where xx specifies the new limit in TB). Storwize V7000 licenses external storage by enclosure rather than TB. A 15-module XIV requires 15 enclosure licenses.
24 IBM XIV Gen3 with IBM System Storage SAN Volume Controller and Storwize V7000 6.
You've reached the end of your free preview.
Want to read all 54 pages?
- Spring '08
- Computer data storage, Host adapter, XIV, Storwize V7000, IBM SAN Volume Controller