Dot Hill Systems II 200 FC Manuale Utente

Chapter 8 Troubleshooting Your Array

2. Depending on whether the cause of the alarm is a failed component or a controller 

event and which application you are using, silence the alarm as specified in the 
following table.  

Pushing the Reset button has no effect on controller event alarms and muting the 
beeper has no effect on failed component alarms.

8.3

RAID LUNs Not Visible to the Host 

When mapping partitions to LUN IDs, there must be a LUN 0. Otherwise, 

none of the LUNs will be visible.

By default, all RAID arrays are preconfigured with one or two logical drives. For a 
logical drive to be visible to the host server, its partitions must be mapped to host 
LUNs. To make the mapped LUNs visible to a specific host, perform any steps 
required for your operating system. For host-specific information about different 
operating systems, see:

■

Appendix E for the Solaris operating system

■

Appendix F for Windows 200x Server or Windows 200x Advanced Server

■

Appendix G for a Linux server

■

Appendix H for an IBM server running the AIX operating system

■

Appendix I for an HP server running the HP-UX operating system

8.4

Controller Failover

Controller failure symptoms are as follows: 

■

The surviving controller sounds an audible alarm.

■

The RAID Controller Status LED on the failed controller is amber. 

Table 8-6  Silencing Alarms

Failed Component 
Alarms

Use a paper clip to push the Reset button on the right ear of the array.

Controller Event 
Alarms

Using the controller firmware: From the Main Menu, choose system 
Functions 

→ 

Mute beeper. Refer to the 

User’s Guide fore more information.

Using SANscape: Refer to “Updating the Configuration” in the 

User’s Guide for information about the Mute beeper command.

Using the SANscape CLI: Run mute  [controller].
Refer to the 

SANscape CLI User’s Guide for more information.