Ibm Bto SNV1 Student Guide Book 1 225 300 PDF

V10.
0
Student Notebook
Uempty
Service Assistant: Manage System
(Bypasses front panel)
SVC system IP
© Copyright IBM Corporation 2011, 2014
Figure 2-79. Service Assistant: Manage System SNV13.0
Notes:
Click Manage System in the navigation tree of the Service Assistant to open the System
Information pane. Within the system edit boxes specify the cluster name (also known as system
name) and the cluster IP network information.
Next, click the Create System button to cause the cluster to be created.
The terms SVC cluster and SVC system are used interchangeably. SVC system is favored during
system setup.
© Copyright IBM Corp. 2011, 2014 Unit 2. SVC planning and cluster initialization 2-91
Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Student Notebook
Cluster created with node1
Cluster:
NAVY_SVC
Figure 2-80. Cluster created with node1 SNV13.0
Notes:
After the single node SVC cluster has been created the System Information pane displays the name
and the IP address of the cluster. The visual shows a cluster named NAVY_SVC has been created.
It has a cluster management address of 10.6.76.60. However, this front panel will only display the
system name on the second line as indicated. The node status has changed from candidate to
active.
2-92 SVC Implementation Workshop © Copyright IBM Corp. 2011, 2014

V10.0
Student Notebook
Uempty
System Setup Wizard: Initial login
superuser
passw0rd
Figure 2-81. System Setup Wizard: Initial login SNV13.0
Notes:
The IBM SAN Volume Controller GUI is used to complete the cluster setup. Open the browser to
https://management_IP_address. The SVC GUI recognizes that the configuration of the cluster is in
its initial stages and will start the System Setup Wizard upon initial contact with the cluster.
Log in to initialize the cluster using the default username superuser and the default password is
passw0rd with a zero in place of the letter “o”. This is also the default login credentials used for
accessing the management GUI, unless otherwise.
With SVC v7, the opportunity to change the default password for the superuser is prompted
immediately after initial login. With SVC v6, the superuser’s password can be changed during
system setup.
Student Notebook
System Setup Wizard: Welcome
Figure 2-82. System Setup Wizard: Welcome SNV13.0
Notes:
The Welcome to System Setup page of the System Setup Wizard opens and is followed by the
ensuing sequence of tasks to complete system setup is listed.
During the initial setup of the system the installation wizard asks for various information that you
should have created during planning and have available during this installation process. If you do
not have this information ready or choose not to configure some of these settings during the
installation process you can configure them later through the management GUI.

V10.0
Student Notebook
Uempty
System Setup Wizard: System licenses
Figure 2-83. System Setup Wizard: System licenses SNV13.0
Notes:
The License agreement is the first step. Read and accept the license agreement to be able to
continue the configuration. In addition, the Licensed Functions pane enables the specification of the
additional licenses purchased to expand the base functions included with the SVC. These
expanded functions include:
• Virtualization: The number of terabytes licensed to be virtualized by this system.
• FlashCopy: The licensed capacity for FlashCopy mappings. The used capacity for FlashCopy is
the sum of the capacity of source volumes defined in FlashCopy mappings.
• Global and Metro Mirror: The licensed capacity for Metro Mirror and Global Mirror relationships.
The used capacity is the sum of the capacities of all the volumes defined in Metro or Global
Mirror relationships
• Real-time Compression: The number of terabytes licensed for compression.
When the Apply and Next > button is clicked, the GUI generates the necessary CLI commands to
update the license settings.
Student Notebook
System Setup Wizard: System name, date and

time
Figure 2-84. System Setup Wizard: System name, date and time SNV13.0
Notes:
The system or cluster name can be changed during system setup. If you have more than one
system in your environment it would be best to define names by which they can easily be
determined.
Next, date and time can be set either manually or with an NTP server.
Click the Apply and Next > button to cause the GUI to generate and display the SVC CLI
commands used to achieve the desired settings specified in the panels.

V10.0
Student Notebook
Uempty
System Setup Wizard: Stretched system

• Option to create a stretched system
• Mandatory three sites needed for a stretched cluster

implementation.
– Site1: Production site 1
– Site2: Production site 2
– Site3: A site at a different location can be used to house the quorum
disk
Figure 2-85. System Setup Wizard: Stretched system SNV13.0
Notes:
With the v7.3 release, during the initial configuration of the system the GUI now features the ability
to create a stretched system. From the Stretch System window of the GUI, if you choose to create
a stretched system during the initial configuration, you will need to specify the sites that are
included. These are the mandatory three sites needed for a stretched cluster implementation.
• Site1: Production site 1
• Site2: Production site 2
• Site3: A site at a different location can be added to house the quorum disk
You can also enable a stretched system after the cluster is completed using the GUI System Details
option.
Student Notebook
System Setup Wizard: Add Nodes
Figure 2-86. System Setup Wizard: Add Nodes SNV13.0
Notes:
The next step of the system setup process is to add the remaining candidate nodes since the
cluster only consists of one node at this point.
Each node belongs to one and only one I/O group and two nodes comprise an I/O group. Up to four
I/O groups comprise an SVC cluster and they are known as io_grp0, io_grp1, io_grp2, and io_grp3.
I/O groups are populated with nodes in sequence starting with io_grp0. Click the empty slot in the
io_grp0 enclosure to start the add node process and select a node from the Add Node drop down
list.
An appropriate name can be specified for the node being added and click Add Node. The
addnode command is generated by the GUI to add the node to I/O group 0.
All the nodes in the cluster must run the same level of SVC code. When a node is being added to
the cluster its software level is verified. If a mismatch is discovered the Cluster software is shipped
to the joining node for installation which will cause the add node process to potentially take up to 30
minutes.

V10.0
Student Notebook
Uempty
System Setup Wizard: Second node added
Figure 2-87. System Setup Wizard: Second node added SNV13.0
Notes:
As displayed by the system rack, at this point the cluster is comprised of a single I/O group with two
nodes; node1 (default name) and NODE2.
Additional candidate nodes (two in the example scenario) can be added by clicking the empty node
slots in sequence for the next I/O group. Alternatively, these nodes can be added after initial system
setup has completed.
Click Apply and Next > to continue with system setup.
If you return to the Service Assistant GUI of node1, you would now see that both node1 and node2
are active in the cluster. The other two nodes still are in candidate status.
Student Notebook
System Setup Wizard: External Storage
Figure 2-88. System Setup Wizard: External Storage SNV13.0
Notes:
Once the nodes have been added you have the option to assign external storage devices to the
sites.

V10.0
Student Notebook
Uempty
System Setup Wizard: Call Home
Figure 2-89. System Setup Wizard: Call Home SNV13.0
Notes:
Return to System Setup: The next step in the sequence is to set up Call Home contact details and
configure the email settings to be used (email address, SMTP server) for event notification. These
options can also be specified and updated after system setup.
Ensure that the email server accepts SMTP traffic because some enterprises do not permit SMTP
traffic especially if the destination email address is outside the enterprise.
Student Notebook
System setup: Summary
Figure 2-90. System setup: Summary SNV13.0
Notes:
Review the setting values in the Summary pane. Click the Finish button to complete system setup.

V10.0
Student Notebook
Uempty
SVC system status and capacity view
SVC cluster IP
Menu options within function
Function
icons
Figure 2-91. SVC system status and capacity view SNV13.0
Notes:
After the initial configuration is finished the cluster GUI opens to the Monitoring > System view. A
system rack containing the nodes of the cluster is shown. The rack implicitly conveys that a
maximum of four I/O groups or eight nodes can form one SVC cluster.
The SVC cluster name and code level are displayed at the bottom of the system rack. Clicking it
opens a notebook with general information about the cluster as well as cluster capacity usage data.
The cylindrical column next to the rack provides cursor sensitive displays of physical, allocated, and
virtual capacity values for the cluster.
The navigation tree on the left of the panel contains function icons. Each icon provides a menu of
functions. The bread crumbs across the top of the panel identifies the navigation path taken, from
cluster name > function icon name > menu within function with a quick navigation drop-down
list to navigate within the function. The GUI opening view from system setup is cluster name >
Monitoring > System.
The SVC cluster name is always shown at the root of the navigation path. In environments with
multiple SVC clusters, it is important to verify which SVC cluster is being configured or investigated.
Student Notebook
Add nodes after SVC system has been created
Figure 2-92. Add nodes after SVC system has been created SNV13.0
Notes:
Additional nodes can be added to an existing cluster by clicking a node slot in the I/O group
enclosure of the system rack. After SAN zoning is updated, candidate nodes can then be detected
and added.
In this example, two more candidate nodes are being added to io_grp1 - NODE3 and NODE4.

V10.0
Student Notebook
Uempty
io_grp1 added and I/O group details
Figure 2-93. io_grp1 added and I/O group details SNV13.0
Notes:
Both nodes of io_grp1 have been added to the cluster to complete the 4-node cluster configuration
of the example environment.
Clicking the io_grp1 enclosure area opens the properties notebook for io_grp1. The Real-time
Compression active indicator can be found here; as well as the bitmap space used for various
advanced functions (this will be addressed in subsequent units of this course).
Student Notebook
Rename an SVC node

SVC v7.3:
• Select Monitoring > System Details,
expand view, and highlight node to rename.
• From Action menu select Rename Node
• Enter the name of the node and click
Rename.
SVC v7.2:
• From the system graphical
view, select a node and then
select the Manage tab.
• Enter node name and click
the Save button.
Figure 2-94. Rename an SVC node SNV13.0
Notes:
With the v7.3 release, to rename a node you will now have to select System Detail, expand the
view and highlight the node you wish to rename. Then select from the Action menu, Rename
Node.
With the v7.2 release, to rename the node, select the Manage tab of its notebook and type a new
name in the edit box. Clicking the Save button causes the GUI to generate the chnode -name
command to change its name NODE1.
In general, changing an object name is not a concern as SVC processing is done by object IDs, not
object names. One exception is the case of changing the name of a node if the iSCSI protocol is
being used for host data access to the node.
Be aware that the SVC node name is part of the node’s IQN name. Thus changing the node name
requires more planning as the iSCSI host connections need to be updated; otherwise, it might
cause an iSCSI-connected hosts to lose access to their volumes.

V10.0
Student Notebook
Uempty
SVC GUI: Home > Overview
Overview of
managed
resources
Three system status indicators: Available from all views.
Figure 2-95. SVC GUI: Home > Overview SNV13.0
Notes:
IBM SAN Volume Controller includes an easy-to-use management GUI to help monitored,
managed, and configured for IBM Storwize family of products. You can easily access the GUI using
a supported web browser, and entering the system management IP address.
After you have successfully logged in to the management GUI, the Home window is displayed
showing the Overview panel.
The Overview panel contains three main sections for navigating through the management tool.
1. On the far left of the window are eight function icons.
2. In the middle of the window is a diagram that illustrates a task flow of how storage is
provisioned, as well as existing configuration. You can hover over the icons or click an icon to
provides extended help references.
3. The Status Indicators that is located at the bottom of the window, provide information about
Capacity usage, Compression ratio, Running Tasks and the Health Status of the system. The
Status Indicators are visible from all panels in the GUI.
Resources managed by the cluster are itemized and updated dynamically.
Student Notebook
SVC GUI: Functions icons
Figure 2-96. SVC GUI: Functions icons SNV13.0
Notes:
The functions icons were grouped to show all of the options available. You can hover the cursor
over any one of the eight function icons to display the associated menu options. You can use the
various function icons to examine available storage, create storage pools, create host objects,
create volumes and map volumes to host object, create user access, update system software, and
configure network settings.

V10.0
Student Notebook
Uempty
Keywords
• Physical planning
• Logical planning
• IBM SAN Volume Controller 2145-DH8
• IBM SAN Volume Controller 2145-24F
• IBM SAN Volume Controller 2145-CG8 / 2145-CF8
• IBM SAN Volume Controller 2145 UPS
• Back-end storage
• SAN Zoning
• Fabric zoning
• Virtualization
• Technician port
• Cluster initialization
• Cluster system
• Service Assistant Tool
• SAN Volume Controller GUI
• Secure Shell (SSH) key
• Stretched System
• MDisks
• Storage pool
• Worldwide Node Name
• Worldwide port name
Figure 2-97. Keywords SNV13.0
Notes:
Listed are keywords that were used in this unit.
Student Notebook
Checkpoint (1 of 2)
1. Which of the following SVC 2145 nodes require a 2145 UPS unit
a. 2145-CG8
b. 2145-CF8
c. 2145-GA4
d. 2145-DH8
2. Which of the following is not a function of Ethernet port 1 of each SVC

node:
a. Cluster management IP
b. Service Assistant IP
c. iSCSI IP
d. Cluster alternate management IP
3. True or False: To access the SVC GUI, a user name with a password
must be defined. To access the SVC CLI, a user name can be defined
with a password or SSH key; or both.
Figure 2-98. Checkpoint (1 of 2) SNV13.0
Notes:
Write your answers here:

V10.0
Student Notebook
Uempty
Checkpoint (2 of 2)
4. True or False: The SVC cluster is defined as a SCSI host to an
attaching storage system so that LUNs of the storage system can be
assigned to the SVC. These LUNs become MDisks in the SVC.
5. True or False: Fibre Channel hosts are defined to the SVC by their
HBA WWPNs.
Figure 2-99. Checkpoint (2 of 2) SNV13.0
Notes:
Write your answers here:
Student Notebook
Unit summary
Having completed this unit, you should be able to:
• Determine planning and implementation requirements associated with
the SAN Volume Controller (SVC)
• Implement the physical hardware and cable requirements for the SVC
2145 nodes
• Implement the logical configuration of IP addresses, network
connections, zoning fabrics, and storage attachment to the SVC 2145
nodes
• Integrate the SVC 2145-DH8 into an existing SVC environment
• Execute SVC cluster creation using the Technician port, front panel, or
remotely using the Service Assistant interface
• Identify the basic usage and functionality of IBM SAN Volume Controller
GUI menu
• Implement user creation, authentication, and SSH key generation to
facilitate access to the SVC system management
Figure 2-100. Unit summary SNV13.0
Notes:

Unit 3. SVC
storage provisioning
V10.0
Student Notebook
Uempty
Unit 3. SVC storage provisioning
What this unit is about

This unit examines the planning guidelines and best practices for installing
and configuring the SAN Volume Controller (SVC) environment. The SVC
physical environment (rack location and UPS connection) and IP and SAN
network connections are discussed. Storage system LUN configuration for
SVC assignment is addressed. SVC quorum disk placement and
management are examined.
This unit also illustrates the steps necessary to initialize and create an SVC
cluster, using both the front panel interface and the Service Assistant
interface. Role-based management access to both the GUI and CLI are
introduced. Centralized volume provisioning from the SVC managed
back-end storage systems to attaching host servers is demonstrated with a
step by step walk-through using the GUI and complemented with the CLI.
What you should be able to do

After completing this unit, you should be able to:
• Identify storage resources to be assigned to host systems
• Summarize process of defining storage array
• Execute GUI and CLI operations to create storage resources
• Coordinate the placement of SVC quorum disks and designate the active
quorum disk if desired
• Implement the external storage MDisk allocation to facilitate I/O load
balancing across zoned storage ports
How you will check your progress

Accountability:
• Checkpoint questions
• Hands-on lab exercises
© Copyright IBM Corp. 2011, 2014 Unit 3. SVC storage provisioning 3-1
Student Notebook
Unit objectives
After completing this unit, you should be able to:
• Identify storage resources to be assigned to host systems
• Summarize process of defining storage array
• Execute GUI and CLI operations to create storage resources
• Coordinate the placement of SVC quorum disks and designate
the active quorum disk if desired
• Implement the external storage MDisk allocation to facilitate
I/O load balancing across zoned storage ports
Figure 3-1. Unit objectives SNV13.0
Notes:

V10.0
Student Notebook
Uempty
SVC storage provisioning topics (1 of 6)

• Storage array structure
– Managed Disks (MDisks)
– Pools
– Volumes
– Data migration
– Copy Services
• Storage provisioning walkthrough
– Examine external storage
– Create storage pool
– Create host object
– Create volumes and map to host object
– Remove MDisk from storage pool
– Modify storage capacity
– Implement external storage MDisk allocation
– Add MDisk back to storage pool
Figure 3-2. SVC storage provisioning topics (1 of 6) SNV13.0
Notes:
This topic examines the storage array structure, by defining the components of the array.
Student Notebook
SVC storage structure

• Before you can use a storage resource from the SAN Volume Controller,
you need to configure the resource
Collection of
MDisks to
SSDs that
provide capacity
physically reside
for volumes
in the SVC node*
Managed disks
(unit of storage Assignable
Storage servers
virtualized by storage capacity
to be virtualized
system) to host
* SVC 2145-CG8, F8, and 2145-24F expansion enclosure internal drives are displayed
with in the GUI as internal drives
Figure 3-3. SVC storage structure SNV13.0
Notes:
The SVC GUI Overview diagram illustrates the components that need to be configured. Clicking the
icons in this area provides extended help references including a link to a short video presentation to
explain the topic in more detail.

V10.0
Student Notebook
Uempty
Internal SSDs or external HDD/SDD drives

• Internal SSD drives (only)
– 2145-CG8 and CF8 models (single cluster)
• Up to 8SSD drives (4 per node)
– 2145-DH8 (single cluster)
• With the optional 2145-24F expansion enclosure, up to 48 SSD drives
(24 per enclosure)
• External (HDD/SDD) drives
– Storage servers independent of the SVC nodes
Figure 3-4. Internal SSDs or external HDD/SDD drives SNV13.0
Notes:
SVC can use any supported external SSD storage device or provide its own internal SSD storage.
Internal storage is the RAID-protected storage that is directly attached to the system using the drive
slots in the front of the node or with the expansion enclosure. The system automatically detects the
drives that are attached to it.
For SVC 2145-CG8, or 2145-CF8 nodes, one or more pairs of nodes can contain 0 - 4 flash drives
per node. The drives are only visible to the SVC system to which they are installed.
For the SVC 2145-DH8 nodes support up to two (optional) expansion enclosures for each I/O
group, with one expansion enclosure attached to each node in the I/O group, delivering up to 48
flash drives of internal raw capacity per I/O group.
The SVC node manages external storage subsystems using the SAN or FCoE connections. These
are storage devices that are discovered out on the fabric and presented as external disk systems to
the SVC node.
Student Notebook
Internal drive attributes

• A disk falls under five categories
– Unused
Spare
– Candidate (hotspare drive)
– Member
– Spare
Member
– Failed (part of an array)
Candidate
(ready for use)
Failed
Unused
(Service needed)
(newly added)
Figure 3-5. Internal drive attributes SNV13.0
Notes:
The internal storage menu option displays and manages these drives. From this menu, you can
place internal disk drives into storage pools. This window also provides the option to display the
internal drives based on their capacity and speed.
The internal drives in the SVC node cluster can be assigned to several usage roles, which either
can be unused, candidate, spare, or failed. The meanings of these roles are:
• Unused: The drive is not member of an MDisk
• Candidate: The drive is available for use in an array
• Member: The drive is member of an MDisk
• Spare: The drive can be used as a hot spare if required
• Failed: The drive was either intentionally taken offline or failed due to an error

V10.0
Student Notebook
Uempty
RAID protection for internal storage

• With v7.3 release, SVC 2145-DH8 supports RAID levels:
– RAID 0: striping with no redundancy (1 to 8 drives)
– RAID 1: mirroring (2 drives - one on each node)
– RAID 5: striping with parity, can survive one drive fault (3 to 15 drives)
– RAID 6: striping with double parity, can survive two drive faults (5 to 16 drives)
– RAID 10: RAID 0 on top of RAID 1 (2 to16 drives)
• RAID array automatically added to storage pool as MDisk
• SVC 2145-C8* model supports only RAID 0, 1 and 10 (only)
RAID
Array
disk Storage
RAID presets Pool
RAID
Array
disk
Drives
Figure 3-6. RAID protection for internal storage SNV13.0
Notes:
A Redundant Array of Independent Disks (RAID) is a method of configuring drives for high
availability and high performance. The internal SSD drives need to be included in a RAID grouping
used for performance and to provide protection against the failure of individual drives. These drives
are referred to as members of the array.
For the SVC 2145-DH8 model, drives on different nodes are configured to form RAID 0, 1, 5, 6, and
10 arrays. For SVC 2145-CG8, or 2145-CF8 models, drives on different nodes are configured to
form only RAID 1 or RAID 10 arrays. These arrays are presented as MDisks, which can be added to
storage pools in the same way as MDisks that are discovered on external storage systems are
added. If the MDisks are created from different tiers of storage then Easy Tier can be used to
automatically manage migration of highly used data to faster drives.
The SAN Volume Controller also supports hot-spare drives. When a RAID member drive fails, the
system automatically replaces the failed member with a hot-spare drive and resynchronizes the
array to restore its redundancy.
The management GUI uses RAID presets for setting up RAID configuration, along with the internal
RAID software or volume mirroring is used to provide redundancy. Each array has a RAID level.
Student Notebook
Different RAID levels provide different degrees of redundancy and performance, and have different
restrictions regarding the number of members in the array.
RAID Presets:
• RAID 0 arrays stripe data across the drives. The system supports RAID 0 arrays with just one
member, which is similar to traditional JBOD attach. RAID 0 arrays have no redundancy, so they
do not support hot spare takeover or immediate exchange. A RAID 0 array can be formed by
one to eight drives (one to 4 on the CG8 and CF8 models). All drives in an RAID-0 array must
be located in the same node.
• RAID 1 arrays stripe data over mirrored pairs of drives. A RAID 1 array mirrored pair is rebuilt
independently. A RAID 1 array can be formed by two drives only. The pair of drives must contain
one drive from one node in the I/O group and one drive from the other node in the same I/O
group
• RAID 5 arrays stripe data over the member drives with one parity strip on every stripe. RAID 5
arrays have single redundancy. The parity algorithm means that an array can tolerate no more
than one member drive failure. A RAID 5 array can be formed by 3 to 16 drives.
• RAID 6 arrays stripe data over the member drives with two parity stripes (known as the P-parity
and the Q-parity) on every stripe. The two parity strips are calculated using different algorithms,
which give the array double redundancy. A RAID 6 array can be formed by 5 to 16 drives.
• RAID 10 arrays have single redundancy. Although they can tolerate one failure from every
mirrored pair, they cannot tolerate two-disk failures. The drives are specified as a sequence of
drive pairs. Each pair of drives must contain one drive from a node in the I/O group and a drive
from the other node in the same I/O group. One member out of every pair can be rebuilding or
missing at the same time. A RAID 10 array can be formed by 2 to 16 drives.

V10.0
Student Notebook
Uempty
To configure internal SSD RAID -MDisk

2
1
3
Figure 3-7. To configure internal SSD RAID -MDisk SNV13.0
Notes:
To configure internal storage, select from the Pools menu option Internal Storage. Next, from the
Internal Storage panel select the flash drive you want to configure. Click Configure Storage, and
indicate whether you want to include the unused drive in the RAID SSD configuration. Based on the
drives discovered with in the system, you can use the Recommended configuration that presents
with a suggested preset RAID level or the Select a different configuration. The option to select a
different configuration offers a more flexible way for the configuration of the internal storage as
compared to the recommended configuration preset in terms of drive selection, RAID level, and
storage pool to be used.
Click Finish to create the array.
Student Notebook
External storage system
Figure 3-8. External storage system SNV13.0
Notes:
External storage systems can be displayed by clicking the Pools function icon in the navigation tree
then selecting the External Storage menu option. You can use this option to add MDisks to existing
pools, import them as image mode volumes, or rename them. System migration is used to virtualize
and migrate existing external storage disks to the SVC.
Four controller entries are listed with their default names (controllerx). Notice that each controller
entry is associated with an ID. These controllers are storage systems (actually WWNNs) that have
been zoned with the SVC node ports. The SVC has performed device logins with these storage
system ports to discover LUNs that have been assigned to the SVC.
Review the controller0 entry: The device type of 1726-4xx FastT indicates it as a DS3400. The
WWNN value displayed identifies the specific storage system. Click the + (plus) sign of the
controller entry to list LUNs presented. LUNs are displayed as MDisk entries. The LUN number
column represents the DS3400 assigned LUN numbers of these MDisks.
To uniquely identify an MDisk in the SVC inventory it is correlated to a specific storage system and
the specific LUN number assigned by that storage system. The SVC assigns to the MDisk a default
object name and object ID.

V10.0
Student Notebook
Uempty Upon discovery, the MDisk has an assigned access mode of unmanaged meaning it has been
identified but is currently not being used by the SVC. It will not be used by the SVC until further
administrator action.
Return to the controller entries: Device type of 2107900 indicates that controller1 is a DS8000.
Device type 2145 with a serial number of 2076 represents a Storwize V7000 system. Recall the
Storwize V7000 has two WWNNs and each is represented as an individual controller thus
controller2 and controller3 collectively represent one Storwize V7000 system.
Student Notebook
Managed disks are SCSI LUNs

MDisks - access modes:
SCSI LUNs become • Unmanaged mode becomes
managed mode (free space)
managed disks (MDisks) • Unmanaged mode becomes image
mode (existing data)
R6 R1 R6 R10 R10 R10 R5 R5 R5

LUN LUN LUN LUN LUN LUN LUN LUN LUN
SCSI LUNs assigned to SVC

SCSI LUNs
from"surfaced"
SAN attachedfrom RAID
storage controllers
systems
R6 R1 R6 R10 R10 R10 R5 R5 R5

LUN LUN LUN LUN LUN LUN LUN LUN LUN
IBM system HP system EMC system
Figure 3-9. Managed disks are SCSI LUNs SNV13.0
Notes:
Traditionally SCSI LUNs surfaced by RAID controllers are presented to application host servers as
physical disks.
With the SAN Volume Controller (SVC) serving as the insulating layer, SCSI LUNs become the
foundational storage resource owned by the SVC and are referred to as managed disks (MDisks).
A one-to-one relationship exists between the SCSI LUNs and the managed disks.
The SVC takes advantage of the basic RAID controller features (such as RAID 1, 5, 6, or 10) but
does not depend on large controller cache or host independent copy functions associated with
sophisticated storage systems. The SVC has its own cache repository and offers network-based
Copy Services.
Managed disks have associated access modes. These modes, which govern how the SVC cluster
uses MDisks, are:
• Unmanaged: The default access mode for LUNs discovered from the SAN fabric by the SVC.
These LUNs have not yet been assigned to a storage pool.
• Managed: The standard access mode for a managed disk that has been assigned to a storage
pool. The process of assigning a discovered SCSI LUN to a storage pool automatically changes

V10.0
Student Notebook
Uempty the access mode from unmanaged to managed mode. In managed mode space from the
managed disk can be used to create virtual disks.
• Image: A special access mode reserved for SCSI LUNs that contain existing data. Image mode
preserves the existing data when control of this data is turned over to the SVC. Image mode is
specifically designed to enable existing data to become SVC-managed. SCSI LUNs containing
existing data must be added to the SAN Volume Controller as image mode.
Student Notebook
Storage pools and extents
Extent 1
Extent 2
Extent 3
Pool_IBMSAS
Extent 4
R5 Extent 5
R5 R5
Pool_HPbox
R5 ...
Pool_EMCbox
R10 R10 Extent-n
Extent-n
R10
R10 Managed disks

R5 R5 provide usable
R5 blocks or extents
of physical storage
A storage pool is also known as a MDisk group
Extent size: 16 MB to 8192 MB
Figure 3-10. Storage pools and extents SNV13.0
Notes:
Managed disks are grouped by the storage administrator into one or more pools of storage known
as storage pools, or managed disk groups. The grouping is typically based on performance and
availability characteristics. While a storage pool can span multiple storage systems, for availability
and ease of management it is generally recommended that a storage pool be populated with
MDisks from the same storage system.
The MDisks are placed into storage pools where they are divided into a number of extents which
are numbered sequentially, starting with 0.
The extents can range in size from 16 MB to 8192 MB as defined by the SVC administrator.

V10.0
Student Notebook
Uempty
Pool extent size and SVC cluster capacity

• Best practice:
– Determine extents size based on storage growth trends/forecasts and correlate
to SVC cluster capacity
– Use the SAME extent size value for all storage pools in the SVC cluster
Extent size Cluster capacity
16 MB 64 TB
32 MB 128 TB
64 MB 256 TB
128 MB 512 TB
256 MB 1 PB
512 MB 2 PB
1024 MB 4 PB Default
2048 MB 8 PB
4096 MB 16 PB SVC v6
8192 MB 32 PB
Figure 3-11. Pool extent size and SVC cluster capacity SNV13.0
Notes:
The extent size can be set to 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, or 8192 MB. It is set by
the administrator at the storage pool level when it is defined. Once set, the extent size stays
constant for the life of the pool.
The choice of the extent size affects the total amount of storage that can be managed by an SVC
cluster. A 16 MB extent size supports a maximum capacity of 64 TB, and the 32 MB extent size
supports up to 128 TB. Increasing capacity based on the powers of 2, the 8192 MB extent size
allows for 32 PB of SVC-managed storage. The SVC GUI defaults to an extent size of 1024 MB
with v7. To avoid wasting storage capacity, the volume size should be allocated as a multiple of the
extent size. Use the same extent size across all storage pools in the SVC cluster to facilitate easy
migration of volume data from one storage pool to another.
Student Notebook
External storage tier 0 MDisks: Specify tier
SVC MDisks from

external
storage systems
MDiskX MDiskY
External Storage External Storage

system LUN system LUN
created with created with
SSD drives; flash technology;
assigned to SVC assigned to SVC
Examples: DS8000 or Example: IBM

Storwize V7000 FlashSystem
Figure 3-12. External storage tier 0 MDisks: Specify tier SNV13.0
Notes:
MDisks from external storage systems created from SSDs or flash storage are discovered by the
SVC on the SAN as unmanaged mode MDisks with a default technology type of hard disk drive.
Since there is no interface for the SVC to automatically discern the technology attributes of the
drives that created the MDisks in attaching storage systems, an interface is provided through both
the GUI and the CLI to enable the administrator to update the technology tier of these MDisks to
solid-state drive.
In SVC terminology, solid-state drive (SSD) is used to denote tier 0 storage. The backing
technology could be SSDs or flash systems (such as the IBM FlashSystem storage system).

V10.0
Student Notebook
Uempty
SSD-based MDisks: Sub-volume SSD optimization

Best practice: Place MDisks with same availability and
performance attributes from the same storage system
in the same storage pool (except Easy Tier)
PoolSSD_EasyTier
SSD
array
R5 MDisk*
R5 R5
Hybrid storage pools
PoolextSSD_ET_HPbox R5
MDiskX Pool_FlashSystem
R10
R10
MDiskY1
R10 R10 MDiskY2
MDiskY3 Best practice: Allocate one

LUN (MDisk) per array
*Tier 0 MDisks can also be SCSI LUNs from storage systems

Figure 3-13. SSD-based MDisks: Sub-volume SSD optimization SNV13.0
Notes:
A storage pool that contains both HDD-based MDisks along with SSD-Flash MDisks is also known
as a hybrid storage pool. These SSD-Flash MDisks could be created from SVC node internal SSDs
or LUNs from external storage systems created from SSDs or flash technology. Easy Tiering is
automatically active when mixing different media in hybrid capacity pools. IBM Easy Tier performs
automatic data placement within that storage pool by moving high-activity data onto better
performing storage. Flash drives provide host servers with a pool of high-performance storage for
critical applications.
Student Notebook
Terminology and concepts review

*Maximum volume size = 256 TB
Volumes
BLUEAV1
BLUEWV1 REDAV3
200 GB
100 GB 5 GB
BLUELV2
BLUEARC REDWV2
BLUELV1 20 GB REDAV2
100 GB 10 GB
20 GB 20 GB
EasyTier_HybridPool REDBOX_POOL
SSDmdisk
BLUE1
1.8 TB
292 GB
RED1 RED2
BLUE4
BLUE2 200 GB
1.8 TB 200 GB
1.8 TB BLUE3
1.8 TB MDisks
Storage pools
*Maximum MDisk size = 1 PB
Figure 3-14. Terminology and concepts review SNV13.0
Notes:
To review terminology and concepts:
• Managed disks (SCSI LUNs) are grouped into storage pools. A maximum of 128 managed
disks can be grouped into one storage pool.
• Storage pools contain managed disks. These disks or LUNs are typically large in size (ideally
same-sized) and for availability from the same storage system. A maximum of 128 storage
pools are supported per SVC cluster.
• Volumes are mappings of extents contained in one or more managed disks residing in the same
storage pool.
• A maximum of 8192 volumes are supported per SVC cluster with four I/O groups, each I/O
group supporting 2048 volumes.
• A volume can be up to 256 TB in size.

V10.0
Student Notebook
Uempty
Volume contains pointers to MDisk extents

Example: Host volume size = 756 MB 756 MB
Create a volume whose size is 756 MB -

the volume is comprised of volume
three 256 MB extents
Extent 1a Extent 2a Extent 3a

Extent 1b Extent 2b Extent 3b
Extent 1c Extent 2c Extent 3c
Extent 1d Extent 2d Extent 3d

A volume is also known as a VDisk
Extent 1e Extent 2e Extent 3e
Extent 1f Extent 2f Extent 3f
Extent 1g Extent 2g Extent 3g Storage pool
extent size = 256 MB
Managed Disks (MDisks)
Figure 3-15. Volume contains pointers to MDisk extents SNV13.0
Notes:
A volume is a logical disk that the clustered system presents to a hosts connected over a Fibre
Channel or Ethernet network. A volume also represents the mapping of extents contained in one or
more MDisks of a storage pool.
When an application server needs a disk capacity of a given size a volume of that capacity can be
created from a storage pool that contains MDisks with free space (unallocated extents).
The SVC creates the volume by allocating extents from a given storage pool. The number of
extents required is based on the extent size attribute of the storage pool and the capacity requested
for the volume. By default, extents are taken from all MDisks contained in the storage pool in round
robin fashion until the capacity of the volume is fulfilled.
Prior to SVC v6, a storage pool is referred to as a MDisk group and a volume is referred to as a
virtual disk (VDisk). These terms are still used and the CLI command syntax is still based on the
traditional terms of MDisk group and VDisk.
Student Notebook
Volumes: Striped across managed disks

• Volume is the mapping of extents striped across MDisks
• Best practice:
– Volume size should be a multiple of the extent size of the storage pool
Storage pool
(name, extent size) Volume
Extent 1a
Extent 1a Extent 2a Extent 3a Extent 2a
Extent 1b Extent 2b Extent 3b Extent 3a
Extent 1c Extent 2c Extent 3c Extent 1b
Extent 1d Extent 2d Extent 3d Extent 2b
Extent 1e Extent 2e Extent 3e Extent 3b
Extent 1f Extent 2f Extent 3f
Extent 1c
Extent 1g Extent 2g Extent 3g
Extent 2c
Extent 3c
Managed Disks (MDisks)
Figure 3-16. Volumes: Striped across managed disks SNV13.0
Notes:
The extents from a given storage pool are used by the SVC to create volumes. A volume essentially
contains pointers to its assigned extents of a given storage pool. The advantage with storage
virtualization is that the host is “decoupled” from the underlying storage so the virtualization
appliance can move the extents around without impacting the host system.
Volumes are mapped to the application server hosts in the SAN conceptually in the same manner
as SCSI LUNs are mapped to host ports from storage systems or controllers (also known as LUN
masking).

V10.0
Student Notebook
Uempty
Volume: Three virtualization types

Extent 1a
1. Striped Extent 2a
Extent 3a
BLUE1
Extent 1b 1.4 TB
BLUEWV1 Extent 2b
10 GB Extent 3b BLUE3
Extent 1c 1.4 TB
BLUE2
Extent 2c
1.4 TB
Extent 3c
Extent 1d
Existing data
3. Image
2. Sequential Extent 5a
Extent 5b
Extent 4a
Extent 5c
Extent 4b BLUDATV Extent 5d BLUDATA
Extent 4c 800 MB
BLUEWV2 Extent 5e 800 MB
Extent 4d BLUE4
1 GB Extent 5f
Extent 4e 300 GB
Extent 5g
Extent 4f
Partial extent
Extent 4g
Figure 3-17. Volume: Three virtualization types SNV13.0
Notes:
When a volume is defined, one of the three virtualization types is specified:
• Striped (default): A striped volume is allocated one extent in turn from each managed disk that
has free extents (or a subset of managed disks known as a stripe set) in the storage pool. This
process continues until the space required for the volume has been satisfied.
• Sequential: A sequential volume is where the extents are allocated one after the other from one
managed disk to the next manage disk to create the volume given enough consecutive free
extents are available on that managed disk.
• Image mode: Image mode volumes are special volumes that have a direct relationship with one
managed disk. They are used to migrate existing data into and out of the clustered system.
Image mode simplifies the transition of storage from a non-virtualized to a virtualized
environment without requiring physical data movement or conversion.
Student Notebook
Data migration options: Import existing data

Non-virtualized: Existing data coexistence
Extent 5a Image mode
Extent 5b MDisk
Extent 5c
BLUDATV Extent 5d
BLUDATA
800 MB Extent 5e
800 MB
Extent 5f
Extent 5g
BLUEPOOL
Image type Partial extent
volume
BLUE1 BLUE3
300 GB BLUDATA
Migrate 300 GB
BLUE2 800 MB
Striped Extent 1x 300 GB BLUE4
Extent 3y 300 GB
Extent 4g
BLUDATV Extent 5d Managed mode
Virtualized 800 MB Extent 5e
Extent 5f
Extent 1y
Figure 3-18. Data migration options: Import existing data SNV13.0
Notes:
Image type volumes allow existing data to be controlled and managed by the SVC cluster without
data conversion or virtualization.
An image type volume represents a direct one-to-one mapping between the extents that are on the
image mode managed disk (which is a SCSI LUN that contains existing data) and extents on the
volume. In other words, the data is not virtualized and is accessed as-is.
When an image type volume is created, its corresponding MDisk is concurrently assigned to a
storage pool in image access mode. And the volume consists of extents of the image mode MDisk.
The last extent of the image type volume might potentially be a partial extent since the
corresponding MDisk might not map exactly on the storage pool extent size boundaries.
After volume extents are established, extents (that is, the application data) can be moved to other
MDisks without disrupting application data access. After the first extent is migrated or moved, the
volume’s virtualization type changes from image to striped and the MDisk’s access mode changes
from image to managed.

V10.0
Student Notebook
Uempty
Data migration options: Storage systems
Segregating data access

Server1 Application access from storage infrastructure
volume management
Storage PoolA Storage PoolB
MDisks R5 R5 R5 R5 R5 R5
SCSI LUNs R5 R5 R5 R5 R5 R5
LUN LUN LUN LUN LUN LUN
Storage system
migration
RAID Controller RAID Controller
Storage SystemA Storage SystemB
Figure 3-19. Data migration options: Storage systems SNV13.0
Notes:
A volume represents the mapping of a collection of MDisk extents.
Data movement from one extent to another is reflected by updating the volume mapping to the new
extent locations. The SVC supports this change in volume mapping thus allowing data movement
or data migration to occur transparently, without interrupting host data access to the volume.
Examples of usage of the data migration capability include:
• Moving workload off older storage hardware in preparation for its removal.
• Moving workload onto newly installed storage (new storage systems or newer drives within an
existing storage system).
• Moving workload to a lower-cost storage tier.
• Moving workload to rebalance storage system usage.
Student Notebook
Facilitating migration: Volume extent pointers

Segregating data access
from storage infrastructure
management
Extent 1a volume Extent 1a
Extent 2a Extent 2a
Extent 3a Extent 3a
Extent 1b Extent 1b
Extent 2b Extent 2b
Extent 3b Extent 3b
Extent 1c Extent 1c
Extent 2c Extent 2c
Storage PoolA Extent 3c Extent 3c
Storage PoolB
R5 R5 R5
R5 R5 R5
R5 R5 R5
R5 R5 R5
LUN LUN LUN
LUN LUN LUN
RAID Controller
RAID Controller
Storage SystemA
Storage SystemB
Figure 3-20. Facilitating migration: Volume extent pointers SNV13.0
Notes:
As data is being moved from one extent to another during data migration, the volume mapping is
updated by the SVC without affecting host application data access.
Servers only need to use the volume (extent pointers) enabling storage management activities to
occur with no host disruption as storage system LUNs are allocated or moved.

V10.0
Student Notebook
Uempty
Reverse migration: Export to image

Non-virtualized: Existing Data Coexistence
Image Extent 5a
Image mode
Extent 5b MDisk
Extent 5c
BLUDATV Extent 5d BLUDATA
Migrate 800 MB Extent 5e 60 GB
Extent 5f
Extent 5g
BLUEGRP1
Migrate to image
BLUE1 BLUE3
300 GB 200 GB
BLUE2
Striped Extent 1x
300 GB BLUE4
Extent 3y 300 GB
Extent 4g
Extent 5d
BLUDATV
800 MB
Virtualized 800 MB
Extent 5e
Extent 5f
Extent 1y
Unmanaged
mode
Figure 3-21. Reverse migration: Export to image SNV13.0
Notes:
SVC v2.1 introduced the migrate-to-image option to reverse the migration from the virtualized realm
back to non-virtualized. Data extents associated with a striped type volume are collocated to an
empty or unmanaged destination MDisk and the volume is returned to the image virtualization type
with the destination MDisk placed in image access mode.
The volume can then be deleted from SVC management causing its related MDisk or SCSI LUN to
be set in unmanaged access mode. The SCSI LUN can then be unassigned from the SVC ports
and assigned back to the original owning host with the storage system.
The migrate to image function also allows an image type volume backed with extents of an MDisk in
one storage pool to be backed by another MDisk in the same or different storage pool while
retaining the image virtualization type.
In essence, the volume virtualization type is not relevant to the migrate to image function. The
outcome is one MDisk containing all the data extents for that corresponding volume.
Student Notebook
Fully allocated versus thin-provisioned volumes

Extent 9 LBAn
LBAn Extent 8
5 GB Extent 7
Fully allocated volume:
Extent 6
Entire LBA range
Extent 5 allocated at creation
volume
Extent 4
Extent 3
LBA0
Extent 2
Extent 1
Warning threshold
Host sees two Extent 0
LBA0 for pool free space
5 GB volumes
(LBA0 – LBAn) Storage pool - example
extent size 512 MB
Extent 3 Thin-provisioned volume:
LBAn Extent 2 LBA range allocated in
5 GB Extent 1 grain size increments
Virtual Capacity Extent 0 based on write activity
Volume 2 GB
real capacity
Real Capacity Additional real capacity acquired either:
LBA0 • Automatically – autoexpand (GUI default)
rsize parm • Manually – non-autoexpand (CLI default)
Figure 3-22. Fully allocated versus thin-provisioned volumes SNV13.0
Notes:
The SVC Thin Provisioning function extends storage utilization efficiency and economy to all SVC
supported storage systems. A volume can be created either as fully allocated or Thin-Provisioned.
A thin-provisioned volume is created with two capacities - virtual and real. The virtual capacity is the
capacity seen by host servers as well as SVC services such as FlashCopy and Metro/Global
Mirroring. The real capacity defines the amount of capacity actually allocated from disk systems
represented by storage pools. The real capacity can be increase either manually (command-line
default) or automatically (GUI default).
For fully allocated volumes, its entire capacity is acquired at creation and the entire logical block
address (LBA) range is allocated at the same time. For thin-provisioned volumes, only the real
capacity is acquired at its creation. Space within the allocated real capacity is allocated in
grain-sized increments corresponding to an LBA range dictated on write activity.

V10.0
Student Notebook
Uempty
Volume Mirroring: Two copies of extents

Extent 9 Copy created:
Extent 8 • At creation or
Extent 7 • After creation
Extent 6
Copy 0 Extent 5
Extent 4 Pool1
Extent 3
5 GB Extent 2
Extent 1
Host sees ONE
Extent 0 extent size
5 GB volume Volume
volume
(LBA0 – LBAn)
512 MB
Copy 1 Extent 4
Extent 3
Pool2
Extent 2
Copy has its own: Extent 1
• Storage pool extent size
Extent 0
• Virtualization type 1024 MB
• Fully allocated or thin
Figure 3-23. Volume Mirroring: Two copies of extents SNV13.0
Notes:
The Volume Mirroring function enables two sets of MDisk extents to be associated with one volume.
These two sets of extents or copies of the volume can reside in the same or different storage pools
(or storage systems) hence providing higher availability to applications at the local site.
If a volume is created with two copies, these copies use the same virtualization policy (that is,
striped, sequential, image, Thin Provisioned or fully allocated). A copy can also be added to an
existing volume. In this case, the two copies do not have to share the same virtualization policy.
When a copy is added, the SVC automatically synchronizes the new copy so that it contains the
same data as the existing volume copy. The volume is available for host server access during the
synchronization process.
Student Notebook
Volume Mirroring and I/O processing

SVC node Read/write requests
I/O stack
SCSI Target
Forwarding
Oblivious volume
Replication to
volume
Upper Cache mirroring
FlashCopy Reads
Mirroring
writes Writes
Thin Provisioning Compression
Lower Cache
Pool1 Pool2
Virtualization Easy Tier 3 extents extents
Forwarding
• Promotes high availability at local site
RAID • Expands data migration flexibility
Forwarding • Enables non-disruptive conversions
Thin-Provisioned ÅÆ fully allocated
SCSI Initiator
• Allows mirrored copy to be split as new volume
Figure 3-24. Volume Mirroring and I/O processing SNV13.0
Notes:
When a host writes to a mirrored volume the SVC writes the data to both volume copies. When a
host reads a mirrored volume the SVC picks one of the volume copies known as the primary copy
to read from. If a volume copy is temporarily unavailable (for example, because the RAID controller
that provides the storage pool is unavailable) the volume remains accessible to servers. The SVC
tracks areas of the volume that are written and resynchronize these areas when both volume
copies are available.
The ability to create a volume copy affords additional management flexibility. A storage controller
might fail or be taken offline for maintenance and not affect application access. A thin-provisioned
volume can easily be converted to fully allocated or vice versa. A volume can be migrated from one
storage pool to another and acquire a different extent size. The original copy can then be deleted.
These activities occur within the SVC totally transparent to attaching servers and user applications.

V10.0
Student Notebook
Uempty
Real-time compression does it “on the fly”

SVC
node I/O stack Active primary data
SCSI Target of host
Forwarding • Host servers operate with uncompressed data
Replication • Copy services operate with uncompressed data
• Compression implemented within Thin Provisioning layer of
Upper Cache node I/O stack
FlashCopy
• Only uses physical storage for compressed data
• Volume Mirroring allows non-disruptive conversions –
Mirroring uncompressed ÅÆ compressed
Random Access
Thin Provisioning Compression
Compression Engine
Lower Cache (RACE)
Easy Tier 3 Available with v6.4.0
Virtualization
Forwarding A compressed volume is

2145-DH8 a variation of
RAID a thin-provisioned volume.
Compression
Forwarding Volume properties
Accelerator card includes uncompressed
required Compressed volume capacity indicator.
SCSI Initiator in storage box
Figure 3-25. Real-time compression does it "on the fly" SNV13.0
Notes:
Beginning with v6.4.0, Real-time Compression (RtC) software is embedded in the SVC to address
the requirement of data reduction for active primary data while ensuring application performance.
However, in order to use the compression function, you must obtain the IBM Real-time
Compression license and the hardware level for both nodes within the I/O group must be either
SAN Volume Controller 2145-DH8, 2145-CG8, or 2145-CF8 for that I/O group to support
compression. SAN Volume Controller 2145-DH8 nodes must have two processors, 64 GB of
memory, and at least one Compression Accelerator adapter installed in order to use compression.
Compression technology delivered by the Random Access Compression Engine (RACE) has been
integrated seamlessly into the Thin Provisioning layer of the node I/O stack so that existing features
are supported for compressed volumes.
A compressed volume is a variation of a thin-provisioned volume. While host servers and Copy
Services operate with uncompressed data, data compression occurs “on the fly” so that physical
storage is only consumed for compressed data.
Student Notebook
For existing volumes the Volume Mirroring function can be used to non-disruptively add a
compressed copy and then the original volume copy can be deleted. A compressed volume can
also become uncompressed using the same volume copy functionality provided by Volume
Mirroring.

V10.0
Student Notebook
Uempty
Easy Tier v3
• Supports any combination of 1 - 3 tiers
• MDisks for the SVC always displays as Enterprise
í Unless using the SSD Flash expansion enclosure, you must designate the
tiers on the SVC
í Other members of the Storwize family, the tiers are known as:
í ENT is Enterprise 15K/10K SAS or FC and Nearline is NL-SAS 7.2L or SATA
Tier 0 Tier 1 Tier 2

Flash/SSD ENT NL
Flash/SSD ENT NONE
Flash/SSD NL NONE
NONE ENT NL
Flash/SSD NONE NONE
NONE ENT NONE
NONE NONE NL
Figure 3-26. Easy Tier v3 SNV13.0
Notes:
With the release of the 7.3 code, Easy Tier v3 now support any combination of tiers 1-3. MDisks in
the SVC will always be displayed as Enterprise (ENT) unless you are using the 2145-24F
expansion enclosure that supports only SSD Flash drives. Otherwise, you must change the
description of the tiers on the SVC so it can identify them correctly.
This table lists the supported combination of drives within a storage pool tier. An example, you
could have Flash/SSD, ENT, and NL as Tier 1, or you could have ENT and NL, or a single tier using
any of the three tiers listed.
Student Notebook
Easy Tier: Automatic data placement mode

Volume
Easy Tier performs workload statistical data collection
which is enabled by default in a hybrid storage pool.
SSD MDisk
Hybrid
storage pool
Hot extents
Cold extents migrate up
migrate down
Extent size
11 GB volume 1024 MB
Four extents identified as hot
Automatically and transparently
migrate extents to SSD tier HDD MDisks
• Monitors performance of each extent to determine data temperature
• Creates migration plan for optimal extent placement every 24 hours
• Migrates extents within pool per plan over 24 hour period (limited number of extents chosen to
migrate every five minute interval)
Figure 3-27. Easy Tier: Automatic data placement mode SNV13.0
Notes:
The Easy Tier automatic data placement mode is enabled by default if a multi-tiered storage pool is
created. I/O activity of all the volumes of the multi-tiered storage pool are monitored by Easy Tier.
Extents associated with hot spots of these volumes are migrated dynamically to the SSD
technology tier to reduce I/O latency. Easy Tier complements SVC and storage system cache to
enhance back-end device performance. Cold extents are automatically migrated to the lower-cost
storage tier to optimize storage infrastructure utilization.
If desired, volumes of a multi- tiered storage pool can be disabled from automatic data placement at
the single volume level. Easy Tier provides I/O statistics measurements only for these volumes.
A statistic summary file is created and can be offloaded from the SVC cluster. This file can be
analyzed with the IBM Storage Tier Advisory Tool (STAT). This analysis provides a report on the
number of extents migrated to SSD-based MDisks and if it would make sense for more SSD-based
MDisks to be added.

V10.0
Student Notebook
Uempty
Easy Tier: Evaluation mode

Volume
Easy Tier performs workload statistical data collection
which can be turned on in a single tier storage pool.
If SSD MDisk
Single tier
storage pool
Hot extents
Cold extents migrate up
migrate down
Extent size
11 GB volume 1024 MB
Four extents identified as hot
– candidates for SSD tier
HDD MDisks
• Monitors performance of each extent to determine data temperature
• Provides analysis (using STAT) of benefits to workload if SSDs were added (prior to any SSD
acquisition)
Figure 3-28. Easy Tier: Evaluation mode SNV13.0
Notes:
To identify the potential benefits of using SSDs to optimize the storage infrastructure prior to any
SSD investment, Easy Tier can be manually set on in a single tiered storage pool. Easy Tier then
runs in evaluation mode to measures the I/O activity of the volumes in the pool.
The statistic summary file created can be offloaded from the SVC cluster. This file can be analyzed
with the IBM Storage Tier Advisory Tool (STAT). This analysis provides an understanding about the
benefits to the workload if SSD-based MDisk were added.
Student Notebook
FlashCopy: Point-in-time copy
BLUEWV1 REDAV2
100 GB BLUEAV1 2 GB REDWV2
2 GB
3 GB
BLUEARC REDLV2
BLUELV1
100 GB 20 GB
20 GB Consistency group
BLUEPOOL REDPOOL
BLUE1 BLUE3
1.8 TB 1.8 TB BLUE5 RED1 RED2
1.6 TB 200 GB 200 GB
Storwize BLUE2
1.8 TB BLUE4
family
1.8 TB
DS5000 DS8000
DS4000 XIV
Cluster-wide copy
FlashSystem
DS3000
NetApp And so DS6000
HDS HPQ EMC Sun
N series on... ESS
Figure 3-29. FlashCopy: Point-in-time copy SNV13.0
Notes:
The SAN Volume Controller offers a network-based SAN-wide FlashCopy (point-in-time copy or
PIT) capability obviating the need to use copy service functions on a storage system-by-storage
system basis.
FlashCopy makes a point in time copy of the content of a source volume onto a target volume.
Although the copy operation takes a finite amount of time to complete, the resulting data on the
target volume is presented as if the copy appears to have completed instantaneously.
Related volumes can be defined as a single management entity known as a consistency group.
When an application has related data that spans multiple volumes the consistency group enforces
cross volume consistency or dependent write operations across those volumes. Consistency
groups are used to ensure that related volumes are treated atomically.
FlashCopy operations can be performed across separate source storage systems, and can be
mapped to dissimilar target storage systems.

V10.0
Student Notebook
Uempty
Metro and Global Mirror: Continuous copy

Site-A Metro Mirror
REDV5
SAN Volume Controller Pair
30 GB
REDV6
1 GB
(synchronous copy)

Global Mirror
Switch (asynchronous copy)
Managed disks (MDisks)
DS8000 Blue1 Blue2 Blue3
DS6000
XIV Switch BLUEV5
BLUEV6
30 GB
DS5000 Storwize 1 GB
N series DS3000 family
DS4000
FlashSystem
Interswitch Link (ISL)

or FCIP solutions Managed disks (MDisks) Site-B
Blue1 Blue2 Blue3
DS6000
NetApp and so on DS5000 Storwize DS8000
HDS HPQ EMC Sun
N series … DS3000 family FlashSystem
Figure 3-30. Metro and Global Mirror: Continuous copy SNV13.0
Notes:
In addition to FlashCopy, the Metro/Global Mirror feature is also a networked-based, SAN-wide,
storage system independent advanced copy service provided by the SAN Volume Controller.
Designed for disaster recovery, mirroring allows one or more volumes at a primary site be mirrored
to a secondary site. The SAN fabrics at the two sites are connected using interswitch links (ISL) or
SAN distance extension solutions. For testing or continuous data protection purposes, intracluster
mirroring operations are also supported.
In synchronous mode Metro Mirror provides a consistent and continuous copy, that is, the volume
at the secondary site is an exact match of the volume at the primary site. The host application writes
data to the primary site volume but does not receive the status on the write operation until that write
operation is in the SVC cache at the secondary site. In asynchronous mode Global Mirror enables
the distance between two SVC clusters to be extended while reducing latency by posting the
completion of local write operations independent from the corresponding write activity at the
secondary site. As with FlashCopy, consistency groups are supported to allow related volumes to
be treated atomically.
Student Notebook
SVC storage provisioning topics (2 of 6)

• Storage array structure
– Managed Disks (MDisks)
– Pools
– Volumes
– Data migration
– Copy Services
• Storage provisioning walkthrough
– Examine external storage
– Create storage pool
– Create host object
– Create volumes and map to host object
– Remove MDisk from storage pool
– Modify storage capacity
– Implement external storage MDisk allocation
– Add MDisk back to storage pool
Figure 3-31. SVC storage provisioning topics (2 of 6) SNV13.0
Notes:
In this walkthrough, we will highlight the steps in which to create and provision SVC storage
resources using the SVC GUI and CLI commands.

V10.0
Student Notebook
Uempty
Examine/identify external storage system
Click plus + sign to expand view
Figure 3-32. Examine/identify external storage system SNV13.0
Notes:
In order to configure devices such as storage pools and volumes so that the server can use them to
store data, examine the storage resource that is available. To do so, click the Pools function icon in
the navigation tree and then select the External Storage menu option.
In this example, four controllers entries are listed with their default names (controllerx), and each
controller entry is associated with an ID. These controllers are storage systems (actually WWNNs)
that have been zoned with the SVC node ports and the SVC has performed device logins with
these storage system ports to discover LUNs that have been assigned to the SVC.
The first controller that is highlighted (controller0) is identified by the device type of 1726-4xx FastT
which indicates it is a DS3400. The WWNN value displayed identifies the specific storage system.
Expand the view by clicking the + (plus) sign of the controller entry to list LUNs presented. LUNs
are displayed as MDisk entries. The LUN number column represents the DS3400 assigned LUN
numbers of these MDisks.
To uniquely identify an MDisk in the SVC inventory it is correlated to a specific storage system and
the specific LUN number assigned by that storage system. SVC assigns to the MDisk a default
object name and object ID.
Student Notebook
Upon discovery the MDisk has an assigned access mode of unmanaged meaning it has been
identified but is currently not being used by the SVC. It will not be used by the SVC until further
administrator action.
To identify the remaining controller entries, the device type of 2107900 indicates that controller1 is
a DS8000. Device type 2145 with a serial number of 2076 represents a Storwize V7000 system.
Recall the Storwize V7000 has two WWNNs and each is represented as an individual controller.
Thus controller2 and controller3 collectively represent one Storwize V7000 system.

V10.0
Student Notebook
Uempty
Rename a storage system
Rename the storage system

whose ID is 0
3
Figure 3-33. Rename a storage system SNV13.0
Notes:
The storage system default names are automatically assigned by the system. It can be difficult to
properly identify a system under this naming convention. Therefore, adhering to naming convention
standards to create a more self-documenting environment will often save time for problem
determination. To change the name of a system:
1. Right-click the entry and select the Rename option from the pop-up list.
2. Enter a new system name in the Rename Storage System pane, and click the Rename button.
When you initiate a task, the GUI generates a list of commands that were used to complete the
task. In this example, a chcontroller -name command was used to rename the storage
system.
3. Once task is completed, click the Close button.
Student Notebook
Storage system (controller) rename

IBM_2145:NAVY_SVC:NAVYadmin>lscontroller -delim ,
id,controller_name,ctrl_s/n,vendor_id,product_id_low,product_id_high
0,NAVYDS3K, ,IBM ,1726-4xx, FAStT
1,controller1,75V9721FFFF ,IBM ,2107900 ,
2,controller2,2076 ,IBM ,2145 ,
3,controller3,2076 ,IBM ,2145 ,
IBM_2145:NAVY_SVC:NAVYadmin>lscontroller 1
id 1
controller_name controller1 Use WWNN value to
WWNN 5005076306FFC534
mdisk_link_count 4 ascertain storage system
max_mdisk_link_count 4
degraded no
vendor_id IBM
product_id_low 2107900
product_id_high
product_revision 5.78
ctrl_s/n 75V9721FFFF
allow_quorum yes
. . .
IBM_2145:NAVY_SVC:NAVYadmin>chcontroller -name NAVYDS8K 1
IBM_2145:NAVY_SVC:NAVYadmin>chcontroller -name NAVYSWV7KN2 2
IBM_2145:NAVY_SVC:NAVYadmin>chcontroller -name NAVYSWV7KN1 3
IBM_2145:NAVY_SVC:NAVYadmin>lscontroller -delim ,
id,controller_name,ctrl_s/n,vendor_id,product_id_low,product_id_high
0,NAVYDS3K, ,IBM ,1726-4xx, FAStT
1,NAVYDS8K,75V9721FFFF ,IBM ,2107900 ,
2,NAVYSWV7KN2,2076 ,IBM ,2145 ,
3,NAVYSWV7KN1,2076 ,IBM ,2145 ,
Figure 3-34. Storage system (controller) rename SNV13.0
Notes:
Adhering to the best practice of using meaningful names for objects (instead of staying with the
SVC assigned default names) the storage systems (also known as controllers) of the cluster are
renamed.
The lscontroller command output provides a summary entry for each storage system of the
cluster. This output format is referred to as the concise view as it provides high-level summary or
concise information for each object - namely object ID, name, and device type.
The lscontroller x output (where x is the object ID of the controller) provides much more detail about
the specific object as a more verbose view. For example, an additional key field found in the
verbose view is the WWNN of the controller which enables the association of the controller entry in
the SVC inventory with its physical entity counterpart.
Once the correct storage system has been pinpointed a meaningful name can be assigned. To
rename the storage system merely add a ch to the object category. Thus, the chcontroller
command with -name allows a new name to be assigned to the specified object (identified by ID or
name).

V10.0
Student Notebook
Uempty
Rename an MDisk
Access mode: unmanaged,

managed, and image
1
Rename the MDisk

whose ID is 0
3
Figure 3-35. Rename an MDisk SNV13.0
Notes:
The disk drives that are discovered within the storage device are automatically assigned a default
name and sequentially numbered (mdisk#). The GUI automatically presents a list of all unmanaged
MDisks by object name and ID. However, each drive’s availability can be identified by an access
mode which determines how the cluster uses the MDisk. The possible modes are:
• Unmanaged: The MDisk is not used by the cluster.
• Managed: The MDisk is assigned to an MDisk group and is providing extents that virtual disks
(VDisks) can use.
• Image: The MDisk is assigned directly to a VDisk with a one-to-one mapping of extents between
the MDisk and the VDisk.
If you add a managed disk that contains existing data to a managed disk group, you will lose the
data that it contains. The image mode is the only mode that will preserve this data.
To change the name of an mdisk:
1. Right-click an MDisk (managed disk) entry and select Rename from the pop-up list to rename
the MDisk.
Student Notebook
2. Enter a more descriptive name in the Rename MDisk pane, and click the Rename button. The
GUI generates the chmdisk -name command to rename the given MDisk. In this example
notice the pattern in the commands to change the name of an SVC object:
- A ch prefix is added to an object category to form the command
- chmdisk to change an Mdisk
- chcontroller to change a controller (also known as a storage system) or chnode to
change a node.
- A keyword, such as -name, is used to identify the attribute to be changed typically with a
value assigned. In this case -name is used to identify the new name.
- A name or an object ID of the entity to be changed is identified at the very end of the
command.
3. Once task is completed, click the Close button.

V10.0
Student Notebook
Uempty
Rename multiple MDisks: GUI multi-select
Best practice: Rename storage systems and MDisks 3

for ease of identification and troubleshooting.
Figure 3-36. Rename multiple MDisks: GUI multi-select SNV13.0
Notes:
As a productivity aid the GUI offers multi-select for some functions so that the same action can be
applied to multiple entries or objects. The Ctrl or Shift keys can be used to select multiple entries.
Right-click to view the pop-up list of options applicable for multiple objects.
Right-click to select the Rename option from the pop-up list. In the Rename MDisks pane multiple
edit boxes are available, one for each selected object. Cut and paste is supported so that the same
character string can be pasted in each edit box to minimize editing.
When the Rename button is pushed, the GUI generates as many chmdisk -name commands as
needed to change the name of each selected MDisk.
Student Notebook
Rename DS8K MDisks and create pool (mdiskgrp)

IBM_2145:NAVY_SVC:NAVYadmin>detectmdisk
IBM_2145:NAVY_SVC:NAVYadmin>lsmdisk -filtervalue
controller_name=*DS8K -delim ,
id,name,status,mode,mdisk_grp_id,mdisk_grp_name,capacity,ctrl_LUN_#,
controller_name,UID,tier
10,mdisk10,online,unmanaged,,,100.0GB,4012402000000000,NAVYDS8K,6005076306f
fc534000000000000122000000000000000000000000000000000,generic_hdd
fc534000000000000122100000000000000000000000000000000,generic_hdd
fc534000000000000124000000000000000000000000000000000,generic_hdd
fc534000000000000124100000000000000000000000000000000,generic_hdd
Use LUN_# and UID to

ascertain MDisk to LUN correlation
IBM_2145:NAVY_SVC:NAVYadmin>chmdisk -name DS8KNAVY1220 mdisk10

IBM_2145:NAVY_SVC:NAVYadmin>chmdisk -name DS8KNAVY1221 11
IBM_2145:NAVY_SVC:NAVYadmin>mkmdiskgrp -ext 1024 -mdisk 10:11:12:13

-name DS8K_FC15Kpool -warning 80%
MDisk Group, id [1], successfully created
Figure 3-37. Rename DS8K MDisks and create pool (mdiskgrp) SNV13.0
Notes:
Use the detectmdisk command to scan for newly assigned LUNs to the SVC from storage
systems. This is analogous to cfgmgr in AIX or Rescan Disks in Windows. Recall newly
discovered LUNs become MDisks with an access mode of unmanaged.
The lsmdisk command is filtered to list MDisks from a controller whose name begins with *DS8K.
This output displays four MDisk entries, each with an access mode of unmanaged from the DS8K.
Each MDisk’s DS8K assigned LUN number can be determined from its MDisk entry.
The MDisks are immediately renamed, following installation naming conventions to identify the
storage system and the LUN number assigned by the storage system.
A storage pool containing these four MDisks is created with the CLI mkmdiskgrp command,
specifying an extent size of 1024 MB or 1 GB for the four MDisks of the DS8K_FC15Kpool. Taking
a cue from the GUI, a capacity warning threshold of 80% is also requested. Note the command
prompt returned with the object ID assigned to the newly created pool.

V10.0
Student Notebook
Uempty
Storage system and MDisks renamed
Figure 3-38. Storage system and MDisks renamed SNV13.0
Notes:
The visual shows the DS3400 storage system and its MDisks have been renamed. Naming
conventions might be revised and object names changed subsequently without impacting SVC
processing.
Student Notebook
Create a storage pool
1
2
4 Optional
5
GUI default
extent size
6
Figure 3-39. Create a storage pool SNV13.0
Notes:
Next, you will group the physical disk capacity into one logical entity called a storage pool.
From the same Pools menu:
1. Select MDisks by Pool from the quick navigation drop-down list.
2. Select the New Pool button to create a storage pool.
3. Within the Create Pool panel, enter a pool name. The name for the pool should be chosen to
adhere to naming conventions.
4. You can use the Choose icon option to add a visual descriptor for the pool.
5. Click the Advanced Setting option.
- Accept the GUI defaults provided. However, you can use this option to modify these default
values:
• The default extent size is 1 GB with v7. Remember that it is desirable to have the same
extent size for all pools in the SVC cluster. If all pools use this extent size of 1 GB, the
maximum capacity the cluster can address or manage is 4 PB. The drop-down list is
used to change the extent size.

V10.0
Student Notebook
Uempty • The default warning threshold for the pool is 80%.

If the CLI is invoked directly to create a pool there is no default extent size and a value
must be specified. Also, the warning threshold defaults to 0 (no warning) unless it is
explicitly specified.
6. Click the Next button.
Student Notebook
Select MDisks for storage pool
8
Figure 3-40. Select MDisks for storage pool SNV13.0
Notes:
Select the MDisks to include in the pool. The visual shows the first four MDisk entries are selected.
After you have verified your selection, click the Create button.

V10.0
Student Notebook
Uempty
Create storage pool with four MDisks
mdiskgrp =
storage pool
Easy Tier = auto
Extent size = 1024 MB
Warning threshold = 80% full
0 3
1 2
DS3KNAVY0
2
DS3KNAVY1 DS3KNAVY2 DS3KNAVY3
DS3K_SASpool
Figure 3-41. Create storage pool with four MDisks SNV13.0
Notes:
The mkmdiskgrp command is generated by the GUI to create the pool. In this example, an MDisk
group, also known as a storage pool, is created by the GUI with a name of DS3K_SASpool using
the specified attributes set in the Advanced Settings pane.
The four MDisks previously selected are added to this pool by their object IDs. The Easy Tier
function is set to be automatically active when two tiers of storage technology are detected to be in
the pool. Actually this is the default behavior of the SVC Easy Tier function and thus the
-easytier keyword need not have been coded.
An object ID is automatically assigned to the newly created pool.
Student Notebook
Storage pool created
30 x 4 = 117?
0 3
1 2
Why is the pool capacity
DS3KNAVY0 less than the physical
DS3KNAVY3
DS3KNAVY1 DS3KNAVY2 capacity?
DS3K_SASpool
Figure 3-42. Storage pool created SNV13.0
Notes:
Examine the detailed view of the newly created pool. The four MDisks now have an access mode of
managed and belong to the pool named DS3K_SASpool. Observe that each disk assigned to the
pool have a 30 GB capacity. At this point no volumes have been created yet the total pool capacity
is reported to be less than the sum of the capacities of the four MDisks. A capacity of 3 GB of space
appears to be missing. Why?

V10.0
Student Notebook
Uempty
SVC quorum index indicators

SVC automatically allocates three quorum disks to:
• Resolve SVC system tie-breaking node state issues
• Store and maintain SVC configuration metadata
IBM_2145:NAVY_SVC:NAVYadmin>svcinfo lsquorum
quorum status id name controller controller active object override
index ID name type
0 online 2 DS3KNAVY2 0 NAVYDS3K no mdisk no
1 online 1 DS3KNAVY1 0 NAVYDS3K yes mdisk no
2 online 3 DS3KNAVY3 0 NAVYDS3K no mdisk no
Active = yes
active quorum Active = no
0 1 2 3 standby quorum
active
quorum 1 quorum 0 quorum 2
DS3KNAVY0 DS3KNAVY1 DS3KNAVY2 DS3KNAVY3
DS3K_SASpool
IBM_2145:NAVY_SVC:NAVYadmin>svcinfo lsfreeextents DS3KNAVY0

id 0
number_of_extents 27
IBM_2145:NAVY_SVC:NAVYadmin>svcinfo lsfreeextents 3
id 3
number_of_extents 26 quorum index using 1 extent
Figure 3-43. SVC quorum index indicators SNV13.0
Notes:
During a storage pool creation the SVC automatically allocates space within the managed mode
MDisks to create three quorum disks. The three quorum disks are used to resolve tie-breaking
cluster state issues and track cluster control information or metadata.
You can used the lsquorum command to list the quorum disks. Quorums are identified by three
quorum index values - 0, 1, and 2. One quorum index is the active quorum and the others are in
stand-by mode. For this example, the active quorum is index 1 resident on MDisk ID 1
(DS3KNAVY1).
The quorum size is affected by the amount of objects in the cluster and the extent size of the pools.
For this example, the pool extent size is 1 GB, and based on the number of free extent available, a
quorum disk is deduced to be using one extent or 1 GB (an extent being the smallest unit of
allocation). Three quorum disks of 1 GB each explain the missing 3 GB seen in the storage pool
capacity value.
The remaining extents of a quorum MDisk are available to be assigned to volumes (VDisks).
Student Notebook
Pool properties: CLI lsmdiskgrp command

IBM_2145:NAVY_SVC:NAVYadmin>lsmdiskgrp DS3K_SASpool
id 0
name DS3K_SASpool
status online mdiskgrp =
mdisk_count 4
vdisk_count 1 storage pool
capacity 117.00GB
extent_size 1024
free_capacity 107.00GB
virtual_capacity 10.00GB
used_capacity 10.00GB 0
real_capacity 10.00GB 10 GB
overallocation 8 volume
warning 80
easy_tier auto
easy_tier_status inactive
tier generic_ssd 0
tier_mdisk_count 0 1 2 3
tier_capacity 0.00MB
tier_free_capacity 0.00MB 3 exts 3 exts
tier generic_hdd 2 exts 2 exts
tier_mdisk_count 4 DS3KNAVY0 DS3KNAVY3
tier_capacity 117.00GB DS3KNAVY1 DS3KNAVY2
tier_free_capacity 107.00GB
compression_active no
compression_virtual_capacity 0.00MB
compression_compressed_capacity 0.00MB DS3K_SASpool
compression_uncompressed_capacity 0.00MB
Figure 3-44. Pool properties: CLI lsmdiskgrp command SNV13.0
Notes:
To answer the previous question: Why is the pool capacity less than the physical capacity? The
missing 3 GB is for SVC usage and is used by SVC quorum disks.
The details of the pool can be displayed by the lsmdiskgrp command specified with the pool
name (DS3K_SASpool).

V10.0
Student Notebook
Uempty
MDisk properties: Quorum index indicator

IBM_2145:NAVY_SVC:NAVYadmin>lsmdisk DS3KNAVY1
id 1
name DS3KNAVY1
status online
mode managed
mdisk_grp_id 0
mdisk_grp_name DS3K_SASpool
capacity 30.0GB
quorum_index 1 1
block_size 512 active
controller_name NAVYDS3K
ctrl_type 4 quorum 1
ctrl_WWNN 200400A0B875EF1F
controller_id 0 DS3KNAVY1
path_count 4
max_path_count 4
ctrl_LUN_# 0000000000000001
UID
600a0b800075ef1f000002d74dd224a200000000000000000000000000
000000
preferred_WWPN 203500A0B875EF1F Storage system
active_WWPN 203500A0B875EF1F
fast_write_state empty logical drive ID
raid_status
raid_level
redundancy
strip_size
spare_goal
spare_protection_min
balanced
tier generic_hdd © Copyright IBM Corporation 2011, 2014
Figure 3-45. MDisk properties: Quorum index indicator SNV13.0
Notes:
As seen in the lsquorum output, MDisk ID 1 (DS3KNAVY1) contains quorum index 1 which is the
active quorum. Only managed mode MDisks can be used as quorum disks.
Notice the detailed lsmdisk output for this MDisk has an entry of quorum index 1.
Each MDisk has a UID value which is the serial number externalized by the owning storage system
for the LUN and appended with many bytes of zeroes.

Ibm Bto SNV1 Student Guide Book 1 225 300 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ibm Bto SNV1 Student Guide Book 1 225 300 PDF

Uploaded by

Copyright:

Available Formats

V10.

Service Assistant: Manage System

(Bypasses front panel)

© Copyright IBM Corporation 2011, 2014

Figure 2-79. Service Assistant: Manage System SNV13.0

Cluster created with node1

© Copyright IBM Corporation 2011, 2014

Figure 2-80. Cluster created with node1 SNV13.0

2-92 SVC Implementation Workshop © Copyright IBM Corp. 2011, 2014

System Setup Wizard: Initial login

© Copyright IBM Corporation 2011, 2014

Figure 2-81. System Setup Wizard: Initial login SNV13.0

System Setup Wizard: Welcome

© Copyright IBM Corporation 2011, 2014

Figure 2-82. System Setup Wizard: Welcome SNV13.0

2-94 SVC Implementation Workshop © Copyright IBM Corp. 2011, 2014

System Setup Wizard: System licenses

© Copyright IBM Corporation 2011, 2014

Figure 2-83. System Setup Wizard: System licenses SNV13.0

System Setup Wizard: System name, date and

© Copyright IBM Corporation 2011, 2014

2-96 SVC Implementation Workshop © Copyright IBM Corp. 2011, 2014

System Setup Wizard: Stretched system

• Mandatory three sites needed for a stretched cluster

© Copyright IBM Corporation 2011, 2014

Figure 2-85. System Setup Wizard: Stretched system SNV13.0

System Setup Wizard: Add Nodes

© Copyright IBM Corporation 2011, 2014

Figure 2-86. System Setup Wizard: Add Nodes SNV13.0

2-98 SVC Implementation Workshop © Copyright IBM Corp. 2011, 2014

System Setup Wizard: Second node added

© Copyright IBM Corporation 2011, 2014

Figure 2-87. System Setup Wizard: Second node added SNV13.0

System Setup Wizard: External Storage

© Copyright IBM Corporation 2011, 2014

Figure 2-88. System Setup Wizard: External Storage SNV13.0

2-100 SVC Implementation Workshop © Copyright IBM Corp. 2011, 2014

System Setup Wizard: Call Home

© Copyright IBM Corporation 2011, 2014

Figure 2-89. System Setup Wizard: Call Home SNV13.0

System setup: Summary

© Copyright IBM Corporation 2011, 2014

Figure 2-90. System setup: Summary SNV13.0

2-102 SVC Implementation Workshop © Copyright IBM Corp. 2011, 2014

SVC system status and capacity view

Menu options within function

Figure 2-91. SVC system status and capacity view SNV13.0

Add nodes after SVC system has been created

© Copyright IBM Corporation 2011, 2014

2-104 SVC Implementation Workshop © Copyright IBM Corp. 2011, 2014

io_grp1 added and I/O group details

© Copyright IBM Corporation 2011, 2014

Figure 2-93. io_grp1 added and I/O group details SNV13.0

Rename an SVC node

© Copyright IBM Corporation 2011, 2014

Figure 2-94. Rename an SVC node SNV13.0

2-106 SVC Implementation Workshop © Copyright IBM Corp. 2011, 2014

SVC GUI: Home > Overview

Three system status indicators: Available from all views.

© Copyright IBM Corporation 2011, 2014

Figure 2-95. SVC GUI: Home > Overview SNV13.0

SVC GUI: Functions icons

© Copyright IBM Corporation 2011, 2014