HP P2000 HP P2000 G3 MSA System SMU Reference Guide - Page 59

Step 5: Setting the default mapping, Step 6: Confirming vdisk settings, Creating a vdisk

Get HP P2000 PDF manuals and user guides View all HP P2000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 59 highlights

Step 5: Setting the default mapping Specify default mapping settings to control whether and how hosts will be able to access the vdisk's volumes. These settings include: • A logical unit number (LUN), used to identify a mapped volume to hosts. Both controllers share one set of LUNs. Each LUN can be assigned as the default LUN for only one volume in the storage system; for example, if LUN 5 is the default for Volume1, LUN5 cannot be the default LUN for any other volume. • The level of access - read-write, read-only, or no access - that hosts will have to each volume. When a mapping specifies no access, the volume is masked. • Controller host ports through which hosts will be able to access each volume. To maximize performance, it is recommended to map a volume to at least one host port on the controller that the volume's vdisk is assigned to. To sustain I/O in the event of controller failure, it is recommended to map to at least one host port on each controller. After a volume is created you can change its default mapping, and create, modify, or delete explicit mappings. An explicit mapping overrides the volume's default mapping for a specific host. NOTE: When mapping a volume to a host using the Linux ext3 file system, specify read-write access; otherwise, the file system will be unable to mount/present/map the volume and will report an error such as "unknown partition table." To specify the default mapping 1. Select Map. 2. Set the base LUN for the volumes. If this LUN is available, it will be assigned to the first volume and the next available LUNs in sequence will be assigned to any remaining volumes. 3. In the enclosure view or list, select controller host ports through which attached hosts can access each volume. 4. Select the access level that hosts will have to each volume: read-write, read-only, or no-access (masked) 5. Click Next to continue. Step 6: Confirming vdisk settings Confirm that the values listed in the wizard panel are correct. • If they are not correct, click Previous to return to previous steps and make necessary changes. • If they are correct, click Finish to apply the setting changes and finish the wizard. Creating a vdisk To create a vdisk 1. In the Configuration View panel, right-click the system or Vdisks and then select Provisioning > Create Vdisk. 2. In the main panel set the options: • Vdisk name. Optionally change the default name for the vdisk. A vdisk name is case sensitive; cannot already exist in the system; cannot include a comma, double quote, or backslash; and can have a maximum of 20 bytes. • Assign to. If the system is operating in Active-Active ULP mode, optionally select a controller to be the preferred owner for the vdisk. The default, Auto, automatically assigns the owner to load-balance vdisks between controllers. If the system is operating in Single Controller mode, the Assign to setting is ignored and the system automatically load-balances vdisks in anticipation of the insertion of a second controller in the future. • RAID Level. Select a RAID level for the vdisk. • Number of Sub-vdisks. For a RAID-10 or RAID-50 vdisk, optionally change the number of sub-vdisks that the vdisk should contain. HP P2000 G3 MSA System SMU Reference Guide 59

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
HP P2000 G3 MSA System SMU Reference Guide
59
Step 5: Setting the default mapping
Specify
default mapping
settings to control whether and how hosts will be able to access the vdisk’s
volumes. These settings include:
•
A logical unit number (LUN), used to identify a mapped volume to hosts. Both controllers share one set
of LUNs. Each LUN can be assigned as the default LUN for only one volume in the storage system; for
example, if LUN 5 is the default for Volume1, LUN5 cannot be the default LUN for any other volume.
•
The level of access — read-write, read-only, or no access — that hosts will have to each volume. When
a mapping specifies no access, the volume is
masked
.
•
Controller host ports through which hosts will be able to access each volume. To maximize
performance, it is recommended to map a volume to at least one host port on the controller that the
volume’s vdisk is assigned to. To sustain I/O in the event of controller failure, it is recommended to map
to at least one host port on each controller.
After a volume is created you can change its default mapping, and create, modify, or delete explicit
mappings. An
explicit mapping
overrides the volume’s default mapping for a specific host.
NOTE:
When mapping a volume to a host using the Linux ext3 file system, specify read-write access;
otherwise, the file system will be unable to mount/present/map the volume and will report an error such as
“unknown partition table.”
To specify the default mapping
1.
Select
Map
.
2.
Set the base LUN for the volumes. If this LUN is available, it will be assigned to the first volume and the
next available LUNs in sequence will be assigned to any remaining volumes.
3.
In the enclosure view or list, select controller host ports through which attached hosts can access each
volume.
4.
Select the access level that hosts will have to each volume:
read-write
,
read-only
, or
no-access
(masked)
5.
Click
Next
to continue.
Step 6: Confirming vdisk settings
Confirm that the values listed in the wizard panel are correct.
•
If they are not correct, click
Previous
to return to previous steps and make necessary changes.
•
If they are correct, click
Finish
to apply the setting changes and finish the wizard.
Creating a vdisk
To create a vdisk
1.
In the Configuration View panel, right-click the system or
Vdisks
and then select
Provisioning > Create
Vdisk
.
2.
In the main panel set the options:
•
Vdisk name. Optionally change the default name for the vdisk. A vdisk name is case sensitive;
cannot already exist in the system; cannot include a comma, double quote, or backslash; and can
have a maximum of 20 bytes.
•
Assign to. If the system is operating in Active-Active ULP mode, optionally select a controller to be
the preferred owner for the vdisk. The default, Auto, automatically assigns the owner to
load-balance vdisks between controllers. If the system is operating in Single Controller mode, the
Assign to setting is ignored and the system automatically load-balances vdisks in anticipation of the
insertion of a second controller in the future.
•
RAID Level. Select a RAID level for the vdisk.
•
Number of Sub-vdisks. For a RAID-10 or RAID-50 vdisk, optionally change the number of sub-vdisks
that the vdisk should contain.