HP BLc7000 HP Direct-Connect External SAS Storage for HP BladeSystem Solutions - Page 34

or Command Line Interface CLI., HP 2000 Family Modular Smart Array reference guide

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

Page 34 highlights

• The MSA controller and its drives are configured using the Storage Management Utility (SMU) or Command Line Interface (CLI). ◦ For information about configuring storage in the SMU, see the HP 2000 Family Modular Smart Array reference guide. ◦ For information about configuring storage in the CLI, see the HP 2000 Family Modular Smart Array CLI reference guide. • (Optional but strongly recommended) Map each MSA2000sa storage volume to ports on the server blades. (This is called explicit mapping. Other HP utilities use a similar concept termed Selective Storage Presentation (SSP) or Access Control Lists (ACL).) When you set up explicit maps, you specify for each volume, the hosts that can access it. If a new server is installed in the BladeSystem c-Class enclosure, storage volumes will not be visible to that server until explicitly mapped. When you do not set up explicit maps for each volume, all server blades with P700m Controllers that are contained in the same SAS zone can access the storage. If a new server is installed in the BladeSystem c-Class enclosure, the storage volumes will be immediately visible to that server. ◦ For information about mapping volumes using the SMU, see "Managing Host Access to Volumes" in the HP 2000 Family Modular Smart Array reference guide. ◦ For information about mapping volumes using the CLI, see the "Map volume" section in the HP 2000 Family Modular Smart Array CLI reference guide. • When mapping, be sure to choose all MSA2000sa controller ports (A0, A1, B0, and B1), to guarantee access in the event of a controller, port, or cable failure. During a failover, if access is granted to all MSA2000sa controller ports, I/O will fail over to ports on the surviving controller. 34 Device information

  • 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
•
The MSA controller and its drives are configured using the Storage Management Utility (SMU)
or Command Line Interface (CLI).
◦
For information about configuring storage in the SMU, see the
HP 2000 Family Modular
Smart Array reference guide
.
◦
For information about configuring storage in the CLI, see the
HP 2000 Family Modular
Smart Array CLI reference guide
.
•
(Optional but strongly recommended) Map each MSA2000sa storage volume to ports on the
server blades. (This is called explicit mapping. Other HP utilities use a similar concept termed
Selective Storage Presentation (SSP) or Access Control Lists (ACL).)
When you set up explicit maps, you specify for each volume, the hosts that can access it. If
a new server is installed in the BladeSystem c-Class enclosure, storage volumes will not be
visible to that server until explicitly mapped.
When you do
not
set up explicit maps for each volume, all server blades with P700m
Controllers that are contained in the same SAS zone can access the storage. If a new server
is installed in the BladeSystem c-Class enclosure, the storage volumes will be immediately
visible to that server.
◦
For information about mapping volumes using the SMU, see “Managing Host Access to
Volumes” in the
HP 2000 Family Modular Smart Array reference guide
.
◦
For information about mapping volumes using the CLI, see the “Map volume” section in
the
HP 2000 Family Modular Smart Array CLI reference guide
.
•
When mapping, be sure to choose all MSA2000sa controller ports (A0, A1, B0, and B1), to
guarantee access in the event of a controller, port, or cable failure. During a failover, if access
is granted to all MSA2000sa controller ports, I/O will fail over to ports on the surviving
controller.
34
Device information