Évaluations - , GPA:
(
)
)
Fabricant : HP
Taille : 112.78 kb
Nom Fichier :
Langue d'enseignement: 
Le document est chargé, s'il vous plaît patienter
 |
Le document est chargé, s'il vous plaît patienter
Par ce dispositif a également d'autres instructions :
Facilité d'utilisation
Secure Path version
If you choose to use Secure Path, ensure that you have the latest version for your operating system,
available on the HP StorageWorks website:
ht p://h18006.www1.hp.com/storage/index.html
Codeload usage
When a maximally configured system is running at full load, codeload functionality is not effective
because the system may time out before codeload is complete. HP recommends that you always perform
VCS upgrades at an off-peak time.
SSSU
Changing comments on a disk enclosure
Use Command View EVA to change comments on a disk enclosure. If you try to change a disk enclosure
comment using SSSU, the following error message appears:
Error:
Invalid Operation
Changing the name of a disk enclosure
Changing the name of a disk enclosure is not supported with SSSU or Command View EVA. If you try to
change a disk enclosure name using SSSU, the following error message appears:
Error:
Invalid Operation
Logical Volume Manager
Before you create snapshots or snapclones of a device that is managed by Logical Volume Manager
(LVM), be sure to properly configure LVM. After creating a snapshot or snapclone of a physical volume,
always run vgchgid(1M) to break the association between the volume group and the snapshot or
snapclone. Otherwise, snapshots or snapclones appear to LVM as an alternate path to the original
physical volume. This can cause data corruption if the snapshot or snapclone is added later to the volume
group using vgextent(1M), vgimport(1M), or vgscan(1M).
When a path to a device managed by LVM becomes unavailable because of a controller, path link,
switch, or HBA failure, I/O requests can be delayed for up to one minute after the failure. As a result,
the responsiveness of mirrored logical volumes may be affected briefly. When a physical volume
becomes unavailable, applications may experience a delay while an I/O request to that physical volume
times out. By default, this delay takes 30 seconds, but you can change the timeout value using the
pvchange(1M) command.
For a read, LVM selects another mirror and requests I/O again. For a write, LVM records the error and
continues the write operation if the data has been written to at least one mirror. In either case, with
Secure Path installed, this initial timeout can take up to one minute longer. After initial timeout, LVM stores
the physical volume status as unavailable, and subsequent I/O requests are not delayed.
Overloaded EVA configurations
If multiple servers are overloading an EVA, the boot or reboot of one of the servers may time out. If the
combined delayed access to EVA LUNs exceeds 10 minutes, the boot does not complete. To avoid this
situation, restart the boot process and reduce the EVA load.
HP-UX connectivity 4.0C for the 3000/5000 Enterprise Virtual Array release notes
7
... Ce manuel est également adapté pour les modèles :
données dispositifs de traitement - HP StorageWorks EVA3000 EMEA Bundles (112.78 kb)