HP XP20000/XP24000 Panduan Konfigurasi - Halaman 26

Jelajahi secara online atau unduh pdf Panduan Konfigurasi untuk Beralih HP XP20000/XP24000. HP XP20000/XP24000 40 halaman. Hp storageworks xp disk array configuration guide: vmware (a5951-96106, september 2010)
Juga untuk HP XP20000/XP24000: Catatan Rilis (13 halaman), Manual Integrasi (29 halaman), Catatan Rilis (4 halaman), Panduan Administrator (50 halaman), Panduan Konfigurasi (42 halaman), Panduan Konfigurasi (40 halaman), Panduan Konfigurasi (40 halaman), Panduan Konfigurasi (36 halaman), Panduan Konfigurasi (36 halaman), Panduan Konfigurasi (30 halaman), Panduan Konfigurasi (36 halaman), Catatan Rilis (5 halaman), Panduan Konfigurasi (46 halaman), Panduan Konfigurasi (46 halaman), Panduan Referensi (46 halaman), Panduan Konfigurasi (44 halaman), Panduan Konfigurasi (38 halaman), Panduan Konfigurasi (34 halaman), Panduan Konfigurasi (30 halaman), Panduan Konfigurasi (30 halaman)

Halaman Cetak
HP XP20000/XP24000 Panduan Konfigurasi
Error condition
The disk array performs a self reboot
because the disk array was busy or
it logged a panic message.
The disk array responds "Not Ready"
or the disk array has displayed "Not
Ready" and timed out.
The host detects a parity error.
The host hangs or devices are
declared and the host hangs.

Calling the HP support center

If you are unable to resolve an error condition, contact the HP support center for assistance.

Contact information

Telephone numbers for worldwide technical support are listed on the HP support web site:
http://www.hp.com/support/.

Before you call

Be sure to have the following information available:
•
Technical support registration number (if applicable)
•
Product serial numbers
•
Product model names and numbers
•
Applicable error messages
•
Operating system type and revision level
•
Detailed, specific questions
For continuous quality improvement, calls may be recorded or monitored.
26
Troubleshooting
Recommended action
Reboot the host.
Contact HP.
Check the FCA and make sure it was installed properly. Reboot the
host.
Make sure there are no duplicate disk array TIDs and that disk array
TIDs do not conflict with any host TIDs.