HP 234664-002 - ProLiant - ML330T02 Manuale di implementazione - Pagina 17

Sfoglia online o scarica il pdf Manuale di implementazione per Desktop HP 234664-002 - ProLiant - ML330T02. HP 234664-002 - ProLiant - ML330T02 26. Visualization and acceleration in hp proliant servers
Anche per HP 234664-002 - ProLiant - ML330T02: Domande frequenti (4 pagine), Manuale di implementazione (35 pagine), Libro bianco tecnico (12 pagine), Aggiornamento del firmware (9 pagine), Panoramica (20 pagine), Manuale introduttivo (22 pagine), Manuale di risoluzione dei problemi (18 pagine), Manuale di implementazione (11 pagine), Manuale di installazione (2 pagine), Manuale di configurazione (2 pagine), Manuale introduttivo (19 pagine), Manuale di aggiornamento (9 pagine), Manuale di aggiornamento (16 pagine), Manuale introduttivo (10 pagine), Manuale di istruzioni per l'installazione (15 pagine), Brief tecnologico (9 pagine)

HP 234664-002 - ProLiant - ML330T02 Manuale di implementazione

Storage requirements

Ensure that the following conditions are met for failover clusters:
• Because improvements in failover clusters require that the storage respond correctly to specific SCSI
commands, the storage must follow the SCSI Primary Commands-3 (SPC-3) standard. In particular,
the storage must support Persistent Reservations as specified in the SPC-3 standard.
• The miniport driver used for the storage must work with the Microsoft Storport storage driver.
• Servers from different clusters must not be able to access the same storage devices (isolate storage
devices, one cluster per device). In most cases, a Logical Unit Number (LUN) that is used for one set
of cluster servers should be isolated from all other servers through LUN masking or zoning.
NOTE
Before starting, the storage administrator must configure several
shared LUNs. It is important that all cluster nodes have access to
the LUNs, and that the host connections are configured to follow
the SPC-3 standard.

Configuring EVA host connections

Make sure the Windows LH Host mode is enabled for each node on the Enterprise Virtual Array
(EVA) through command view. Depending on what command view you have installed, if in the drop-
down there is no "Microsoft Windows LH" then choose custom and type in the custom type field the
following HEX number 00000004198009A8 (Figure 1). If the wrong connection type is configured,
you cannot share the disks between the cluster nodes and the cluster check will fail with a non-SCSI-3
compliant message.
Figure 1. Configuring EVA host properties
17