HP XP P9500 HP StorageWorks P9000 Configuration Guide (AV400-96380, May 2011) - Page 159

Linux, HBA configuration, MPIO software, LUN presentation, Membership partitions

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

Page 159 highlights

them as described previously, you can then use them to create dynamic volumes and file systems, mount them on the cluster nodes, and assign drive letters or junction points. For details on importing and deporting disks, dynamic volume creation and configuration, and file system creation and configuration, see the HP StorageWorks Scalable NAS File Serving Software Administration Guide . Linux The HP Cluster Gateway and HP Scalable NAS software both use the HP PolyServe software as their underlying clustering technology and both have similar requirements for the P9000 disk array. They have both been tested with the P9000 disk arrays and this appendix details configuration requirements specific to P9000 deployments using HP PolyServe Software on Linux. For details on installing and configuring the HP PolyServe software, see the HP PolyServe Matrix Server Installation Guide. For any P9000-specific requirements, see the Enterprise Scalable NAS Products and Solutions Compatibility Matrix, which you can download from http://bizsupport2.austin.hp.com/bc/docs/ support/SupportManual/c01336151/c01336151.pdf. HBA configuration HP recommends using the HBA drivers specifically supported by the P9000 array. Other drivers will work, but may not produce optimal results during failure or failover situations. On the HP Cluster Gateway and, typically, on HP Scalable NAS deployments, the HBA driver is loaded by the HP PolyServe software from the /etc/opt/hpcfs/fc_pcitable file. Set any driver loading options, such as configuring the QLogic failover driver, in this file. MPIO software Configure the HP Cluster Gateway and HP Scalable NAS software running on SuSE SLES9 and Red Hat Enterprise Linux Version 4 to use the QLogic failover driver for their host based multipath I/O software. Configure the HP Cluster Gateway and HP Scalable NAS software running on SuSE SLES10 and Red Hat Enterprise Linux Version 5 to use Device Mapper for their host based multipath I/O software. Array configuration LUN presentation To work correctly with the HP PolyServe clustering technology, all LUNs on the disk array need to be presented identically to all nodes in the cluster. When using the LUNs for a membership partition, create a Linux partition table on the LUNs using a tool such as fdisk. If the LUNs are being used for dynamic volumes or file systems, you do not need to install a partition table on them. Membership partitions HP Scalable NAS uses a set of membership partitions to control access to the SAN and to store the device naming database, which includes the global device names that HP Scalable NAS assigns to the SAN disks placed under its control. The membership partitions must be placed on the SAN, not on local storage. HP Scalable NAS can use either one or three membership partitions, but to ensure that a membership partition is always available, we strongly recommend that you use three membership partitions. HP recommends that you create three LUNs for the membership partitions. Each LUN should be a minimum of 1 GB in size. It is important to partition the membership partition LUNs, which are represented to the operating system as SD devices, appropriately before HP Scalable NAS is configured. (For example, use the fdisk or similar tool.) Linux 159

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
them as described previously, you can then use them to create dynamic volumes and file systems,
mount them on the cluster nodes, and assign drive letters or junction points.
For details on importing and deporting disks, dynamic volume creation and configuration, and
file system creation and configuration, see the
HP StorageWorks Scalable NAS File Serving
Software Administration Guide
.
Linux
The HP Cluster Gateway and HP Scalable NAS software both use the HP PolyServe software as
their underlying clustering technology and both have similar requirements for the P9000 disk array.
They have both been tested with the P9000 disk arrays and this appendix details configuration
requirements specific to P9000 deployments using HP PolyServe Software on Linux.
For details on installing and configuring the HP PolyServe software, see the
HP PolyServe Matrix
Server Installation Guide
.
For any P9000-specific requirements, see the
Enterprise Scalable NAS Products and Solutions
Compatibility Matrix
, which you can download from
h
t
tp://b
i
zsu
ppo
r
t2
.a
u
s
tin
.hp
.co
m/bc/doc
s/
su
ppo
r
t/Su
ppo
r
tMan
ual/c0
1
3
3
6
1
5
1/c0
1
3
3
6
1
5
1
.pdf
.
HBA configuration
HP recommends using the HBA drivers specifically supported by the P9000 array. Other drivers
will work, but may not produce optimal results during failure or failover situations.
On the HP Cluster Gateway and, typically, on HP Scalable NAS deployments, the HBA driver is
loaded by the HP PolyServe software from the
/etc/opt/hpcfs/fc_pcitable
file. Set any
driver loading options, such as configuring the QLogic failover driver, in this file.
MPIO software
Configure the HP Cluster Gateway and HP Scalable NAS software running on SuSE SLES9 and
Red Hat Enterprise Linux Version 4 to use the QLogic failover driver for their host based multipath
I/O software.
Configure the HP Cluster Gateway and HP Scalable NAS software running on SuSE SLES10 and
Red Hat Enterprise Linux Version 5 to use Device Mapper for their host based multipath I/O
software.
Array configuration
LUN presentation
To work correctly with the HP PolyServe clustering technology, all LUNs on the disk array need to
be presented identically to all nodes in the cluster. When using the LUNs for a membership partition,
create a Linux partition table on the LUNs using a tool such as fdisk. If the LUNs are being used
for dynamic volumes or file systems, you do not need to install a partition table on them.
Membership partitions
HP Scalable NAS uses a set of membership partitions to control access to the SAN and to store
the device naming database, which includes the global device names that HP Scalable NAS
assigns to the SAN disks placed under its control. The membership partitions must be placed on
the SAN, not on local storage.
HP Scalable NAS can use either one or three membership partitions, but to ensure that a membership
partition is always available, we strongly recommend that you use three membership partitions.
HP recommends that you create three LUNs for the membership partitions. Each LUN should be a
minimum of 1 GB in size. It is important to partition the membership partition LUNs, which are
represented to the operating system as SD devices, appropriately before HP Scalable NAS is
configured. (For example, use the fdisk or similar tool.)
Linux
159