HP AD510A HP StorageWorks 1500 Modular Smart Array Installation Guide (355901- - Page 27

detected and identified by their World Wide Port Name WWPN. As, access. In the ACU

Page 27 highlights

Installation Procedures - All Deployments ■ After configuring the LUNs, remember to: - Verify that all HBA connections to the MSA are recognized, including both paths in a multipath configuration. Each time the MSA is power-cycled, all active connections to the MSA are automatically detected and identified by their World Wide Port Name (WWPN). As needed, manually add the additional connections. Run the ACU or CLI from each host in the network to verify that each of its HBAs has been granted access to the MSA LUNs for that host. If both connections are not granted access, I/O cannot failover to the redundant path. - Identify the operating system of each HBA connection to the MSA by setting the profile (also called Host Mode) of each connection. For example, on Windows systems set the profile to Windows. - Limit access to the LUNs to prevent unintended or unauthorized access. Although not required, HP strongly recommends this security measure. These settings are especially important in heterogeneous environments to prevent servers running different operating systems from accessing the same LUN. For each HBA connection, indicate the LUNs that it can access. In the ACU, enter Selective Storage Presentation (SSP) settings and, in the CLI, build Access Control Lists (ACL). - In active/active multipath configurations, HP recommends disabling host-based Fibre Channel HBA load balancing. By default, MSA firmware balances the LUNs between the two MSA controllers. (Or optionally, you can manually specify the preferred controller path for each LUN.) If HBA load balancing is also enabled at the host, the host instructions will override the MSA instructions, resulting in additional processing time and reduced performance. - In Windows environments, HBA load balancing is set in the HP MPIO DSM Manager. - In Linux environments, HBA load balancing is set via a driver command line option. - In active/active multipath configurations, distribute ownership of the LUNs between the two MSA controllers. Choose one of the following: - Automatic load balancing (Default)-MSA firmware initially assigns ownership of all LUNs to one of the two MSA controllers, and then automatically re-assigns LUN ownership evenly between the controllers based on I/O loads of the LUNs. HP StorageWorks 1500 Modular Smart Array Installation Guide 27

  • 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

Installation Procedures - All Deployments
27
HP StorageWorks 1500 Modular Smart Array Installation Guide
After configuring the LUNs, remember to:
Verify that all HBA connections to the MSA are recognized,
including
both paths in a multipath configuration
. Each time the MSA is
power-cycled, all
active
connections to the MSA are automatically
detected and identified by their World Wide Port Name (WWPN). As
needed, manually add the additional connections. Run the ACU or CLI
from each host in the network to verify that each of its HBAs has been
granted access to the MSA LUNs for that host. If both connections are not
granted access, I/O cannot failover to the redundant path.
Identify the operating system of each HBA connection to the MSA by
setting the profile (also called Host Mode) of each connection. For
example, on Windows systems set the profile to
Windows
.
Limit access to the LUNs to prevent unintended or unauthorized access.
Although not required, HP strongly recommends this security measure.
These settings are especially important in heterogeneous environments to
prevent servers running different operating systems from accessing the
same LUN. For each HBA connection, indicate the LUNs that it can
access. In the ACU, enter Selective Storage Presentation (SSP) settings
and, in the CLI, build Access Control Lists (ACL).
In active/active multipath configurations, HP recommends disabling
host-based Fibre Channel HBA load balancing. By default, MSA
firmware balances the LUNs between the two MSA controllers. (Or
optionally, you can manually specify the preferred controller path for each
LUN.) If HBA load balancing is also enabled at the host, the host
instructions will override the MSA instructions, resulting in additional
processing time and reduced performance.
In Windows environments, HBA load balancing is set in the HP
MPIO DSM Manager.
In Linux environments, HBA load balancing is set via a driver
command line option.
In active/active multipath configurations, distribute ownership of the
LUNs between the two MSA controllers. Choose one of the following:
Automatic load balancing (Default)—MSA firmware initially assigns
ownership of all LUNs to one of the two MSA controllers, and then
automatically re-assigns LUN ownership evenly between the
controllers based on I/O loads of the LUNs.