HP Surestore 64 FW 05.01.00 and SW 07.01.00 HP StorageWorks SAN High Availabil - Page 137
Obtaining Professional Services, Storage-level access control
View all HP Surestore 64 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 137 highlights
Physical Planning Considerations For persistent binding: ■ Each server HBA is explicitly bound to a storage volume or LUN, and access is explicitly authorized (access is blocked by default). ■ The process is compatible with OSI standards. The following are transparently supported: - Different operating systems and applications. - Different storage volume managers and file systems. - Different fabric devices, including disk drives, tape drives, and tape libraries. ■ If the server is rebooted, the server-to-storage connection is automatically re-established. ■ The connection is bound to a storage port WWN. If the fiber-optic cable is disconnected from the storage port, the server-to-storage connection is automatically re-established when the port cable is reconnected. The connection is also automatically re-established if the storage port is cabled through a different director or switch port. Access control can also be implemented at the storage device as an addition or enhancement to redundant array of independent disks (RAID) controller software. Data access is controlled within the storage device, and server HBA access to each LUN is explicitly limited (access is blocked by default). Storage-level access control: ■ Provides control at the storage port and LUN level, and does not require configuration at the server. ■ Supports a heterogeneous server environment and multiple server paths to the storage device. ■ Is typically proprietary and protects only a specific vendor's storage devices. Storage-level access control may not be available for many legacy devices. Obtaining Professional Services Planning and implementing a multi-switch fabric can be a complex and difficult task. HP recommends that you obtain planning assistance from our professional services organization before implementing a fabric topology. SAN High Availability Planning Guide 137