HP 4400 HP StorageWorks 4400 Enterprise Virtual Array getting started guide (5 - Page 23

Best practices, Planning best practices, SAN management best practices

Page 23 highlights

4 Best practices For additional useful information on configuring and managing your storage system, see the following: • HP StorageWorks Enterprise Virtual Array configuration best practices white papers, available from http://h18006.www1.hp.com/storage/arraywhitepapers.html • Best practices section of the HP StorageWorks SAN design reference guide, available on the Manuals page of the HP Business Support Center website: http://www.hp.com/support/manuals. Click Disk Storage Systems under Storage, and then select your EVA model. Best practices in this section are grouped as follows: • Planning best practices • SAN management best practices • Installation and configuration best practices Planning best practices • Sign up with Subscriber's Choice to receive notifications and alerts about your EVA4400 and other HP devices: http://www.hp.com/go/e-updates. Registering your products is strongly recommended, because it provides HP with a communication path for issues and updates. • Confirm that the hardware and software components you plan to use are supported for use with the EVA4400. Before installing your EVA4400 and before making any configuration changes, check the HP StorageWorks Enterprise Virtual Array compatibility reference. • Read the HP StorageWorks SAN design reference guide. This guide contains useful information about setting up and managing iSCSI and Fibre Channel networks and is available on the HP Storage Networking website: http://www.hp.com/go/san. SAN management best practices • Label all physical devices and cables. • Label each HBA to identify its WWN. • Label both ends of each cable with a number or color-coding scheme. Include "to" or "from" information on each label to allow you to quickly identify each cable. • Label each host with its name, alias, and operating system. • Use plugs and end caps on unused device ports and cables. Never leave ports exposed. • Draw physical and logical maps of your network. • Topology map-Technological SAN topology and fabric interconnect scheme; including a strategy to accommodate expansion and technological advances. • Hardware/Device configuration map-Physical layout of all network components, including device names and aliases, the WWN and physical location of each node and device. This information is needed when configuring the storage, entering connection information, and setting up multipathing; it is also needed for future configuration changes, reference, troubleshooting purposes, and verifying connectivity. • Storage map-Defines the storage system configuration and settings, such as LUN allocation and Vraid levels. • Zoning, path, or accessibility map-Defines the communications access settings for devices and user ports in the SAN, including which devices are allowed to communicate with each other and which hosts can access which LUNs. 4400 Enterprise Virtual Array getting started guide 23

  • 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

4 Best practices
For additional useful information on con
guring and managing your storage system, see the following:
HP StorageWorks Enterprise Virtual Array con
guration best practices white papers, available from
h
t
t
p
:
/
/
h
1
8
0
0
6
.
w
w
w
1
.
h
p
.
c
o
m
/
s
t
o
r
a
g
e
/
a
r
r
a
y
w
h
i
t
e
p
a
p
e
r
s
.
h
t
m
l
Best practices section of the
HP StorageWorks SAN design reference guide
, available on the Manuals
page of the HP Business Support Center website:
h
t
t
p
:
/
/
w
w
w
.
h
p
.
c
o
m
/
s
u
p
p
o
r
t
/
m
a
n
u
a
l
s
. Click
Disk
Storage Systems
under Storage, and then select your EVA model.
Best practices in this section are grouped as follows:
Planning best practices
SAN management best practices
Installation and con
guration best practices
Planning best practices
Sign up with Subscriber's Choice to receive noti
cations and alerts about your EVA4400 and
other HP devices:
h
t
t
p
:
/
/
w
w
w
.
h
p
.
c
o
m
/
g
o
/
e
-
u
p
d
a
t
e
s
. Registering your products is strongly
recommended, because it provides HP with a communication path for issues and updates.
Con
rm that the hardware and software components you plan to use are supported for use with
the EVA4400. Before installing your EVA4400 and before making any con
guration changes,
check the
HP StorageWorks Enterprise Virtual Array compatibility reference
.
Read the
HP StorageWorks SAN design reference guide
. This guide contains useful information
about setting up and managing iSCSI and Fibre Channel networks and is available on the HP
Storage Networking website:
h
t
t
p
:
/
/
w
w
w
.
h
p
.
c
o
m
/
g
o
/
s
a
n
.
SAN management best practices
Label all physical devices and cables.
Label each HBA to identify its WWN.
Label both ends of each cable with a number or color-coding scheme. Include “to” or “from”
information on each label to allow you to quickly identify each cable.
Label each host with its name, alias, and operating system.
Use plugs and end caps on unused device ports and cables. Never leave ports exposed.
Draw physical and logical maps of your network.
Topology map—Technological SAN topology and fabric interconnect scheme; including a
strategy to accommodate expansion and technological advances.
Hardware/Device con
guration map—Physical layout of all network components, including
device names and aliases, the WWN and physical location of each node and device.
This information is needed when con
guring the storage, entering connection information,
and setting up multipathing; it is also needed for future con
guration changes, reference,
troubleshooting purposes, and verifying connectivity.
Storage map—De
nes the storage system con
guration and settings, such as LUN allocation
and Vraid levels.
Zoning, path, or accessibility map—De
nes the communications access settings for devices
and user ports in the SAN, including which devices are allowed to communicate with each
other and which hosts can access which LUNs.
4400 Enterprise Virtual Array getting started guide
23