MegaRAID Configuration Console (MCC) This chapter describes the MegaRAID Configuration Console (MCC) and contains these sections: 1.0 "Features and Architecture," 2.0 "Installation," 3.0 "Using the MCC Software Utility," MCC is a software utility that can be run using LSI Logic RAID-aware custom web server. Because of this, no third-party software is required, and the entire code is in JAVA, making MCC platform independent. 1.0 Features and Architecture You would typically configure and administer the arrays and drives using a configuration utility. MCC enables you to connect to a host system and perform the following operations: - Get information about the configuration. - Track the health of the arrays and physical drives. - Track S.M.A.R.T. (self-monitoring analysis and reporting technology) status of the physical drives to monitor drive performance and reliability. - Rebuild an array. - Perform a consistency check on an array. - Check the error log where all drive failures are reported. Note that you need to use the BIOS Configuration Utility to configure arrays, but you can use the MCC to monitor the configuration and perform rebuilds and other operations. A host system has a suite of software running that is controller- and host operating system-dependent. These are (starting from low level and going to high level) the firmware, the drivers, the RAID API, and finally the RAID Server. Any configuration utility resides above this stack of software. MCC is a web-enabled solution for RAID array and drive administration. A user with just a web browser and Internet connection can connect to a host system using LSI Logic custom RAID-aware WebServer or by a WebServer/JSP configuration. Multiple RAID systems can exist on a LAN. The WebServer can be a part of a LAN, which routes the user to the desired RAID system, though the system can work in a Standalone mode, also. Note: You must install Java Run-time Environment (JRE) before you install the MCC for Linux and Windows. The MCC package for Linux is based on JRE and cannot be launched without it. The link to the appropriate download for Java is http://java.sun.com/j2se/1.4/download.html. 1.1 Features The following is a list of the characteristics of MCC: - User-friendly and Web-accessible through an HTML-based graphic user interface (GUI) - Internet browser required (Internet Explorer 5 or higher recommended) - Operating system independent (Client side). - Client side works on all major Internet browsers. - RAID Server works on the following servers: Whistler, Windows NT, Windows 2000, and Linux. - Support for IDE MegaRAID - RAID configuration management - Standard RAID operation management - Alerts and notification management - Co-exists with and enhances existing management environment, such as Power Console Plus. - Dynamic screen updates - Remote adapter/disk firmware installation - Ability to run both in Network and in Standalone modes - Support for all the latest MegaRAID products - Depends on hardware. See the hardware user manual for more information. 1.2 Architecture 1.2.1 MegaRAID Console Server This server holds databases for all registered RAID servers and responds to Internet browser requests. MegaRAID Console server runs WEBRAID and REGSERV programs. 1.2.2 Registration Server (REGSERV) The Registration Server contains a database of all computers that have registered as users of the RAID Server. Before any computer running RAID Server can use the MCC, it must be registered in the Registration Server. This application runs on Red Hat Linux, Windows NT, and Windows 2000. 1.2.3 Registering the Host Machine in MegaRAID Console Server In order to manage several MegaRAID controllers in different machines on the network, the MegaRAID Console Server maintains an internal database of all MegaRAID locations. Each MegaRAID controller must register with the MegaRAID Console Server database. The MegaRAID Console Server internet protocol (IP) address is located in the following files: Windows: %Winbootdir%System32\Drivers\Etc\Regserv.dat Linux: /Etc/host Note: If MCC is running in Stand-alone mode, 'localhost' must be added to the file mentioned above. 1.2.4 Web Server This application runs on MegaRAID Console Server and responds to Internet browser requests. The browser connects directly to LSI Logic specialized RAID-aware Web Server that has the Java Bean built in. By default, installation sets the Web Server port number to 3570. Note: LSI Logic Web Server can co-exist with any other Web Server that you might currently have in your machine. LSI Logic Web Server can be configured to listen to any port you choose, helping to avoid any potential conflict. This solution does not need any third-party software and is totally platform independent. 1.2.5 RAID Server This is the system that has MegaRAID controllers and their monitoring applications, such as RaidServ. RaidServ (called RAID_SERV in Windows NT Service Manager) is a communication layer between MegaRAID Monitoring Console and the IDE software utility and driver. RaidServ is required in all IDE RAID configurations. For IDE, RAIDSERV communicates with the MCC and Spy software utilities to get data about RAID. The RAID Server software runs in any server that has at least one MegaRAID controller and is registered with the Registration Server. 2.0 Installation This section describes the following: - Items required for installation and supported operating systems - Installation procedures for Windows NT, 2000, XP, and Server 2003) - Installation procedures for Red Hat Linux The system must have the items listed in Table 1. Some of the operating systems require that the items be installed before you install the MCC. Table 1. Items Required for Installation Service Internet Java Runtime Pack Browser* Environment (JRE) ------------------------------------------------------------------- Windows NT 4 5 or greater Yes JRE 1.2 or greater Windows 2000 No Not required JRE 1.2 or greater Windows XP SP1 Yes JRE 1.2 or greater Windows Server 2003 N/A Yes JRE 1.2 or greater Red Hat Linux No Yes JRE 1.2 or greater MCC supports the following browsers: - Internet Explorer 5.x or greater - Netscape 4.0 or greater - Opera 5.2 or greater 2.1 Installation Steps for Windows Systems MCC Release 1.x supports only Microsoft Windows NT and Windows 2000 operating systems. Insert the CD in your computer and run the Setup.EXE program, using the following directory: CD-ROM Drive Letter>:/Setup.EXE Setup.EXE installs the required components listed in Table 2 if they are not already installed. When the first installation screen displays, follow the instructions on the installation screens. To install MCC software utilities, follow the instructions on the installation screens. For local administration of a system, install MegaRAID Web Server and MegaRAID Server. For remote administration of different machines, install MegaRAID Web Server, MegaRAID Server, and MegaRAID Registration Server. MegaRAID Registration Server must be installed on only one machine in the network. Click Install to begin the installation, Back to review or change any installation settings, or Cancel to exit the Wizard. This screen displays the progress of the installation. Click Finish to complete the installation. 2.1.1 Unattended installation steps for Windows Systems Note: For unattended installations, the default password will be "megaraid". For each feature, the command line option for each is as follows: Setup /s /v"/qn ADDLOCAL=WEBSERVER" Setup /s /v"/qn ADDLOCAL=RAIDSERVER" [no dependencies - standalone] Setup /s /v"/qn ADDLOCAL=RAIDSERVER_NET" [dependency on REG_SERVER] Setup /s /v"/qn ADDLOCAL=RAIDSERVER_SPY" [dependency on SpySer] Setup /s /v"/qn ADDLOCAL=RAIDSERVER_NETSPY" [dependency on REG_SERVER & SpySer] Setup /s /v"/qn ADDLOCAL=REGISTRATION_SERVER" Setup /s /v"/qn ADDLOCAL=IDE_SNMP" Setup /s /v"/qn ADDLOCAL=SCSI_SNMP" To install more than one feature, the command line is as follows: Setup /s /v"/qn ADDLOCAL=FeatureName1,FeatureName2" To change the path of installation, INSTALLDIR can be set to a new path: Setup /s /v"/qn ADDLOCAL=FeatureName INSTALLDIR=\"path\"" To uninstall individual features, the command line is as follows: Setup /s /v"/qn REMOVE=FeatureName1" To uninstall all features, the command line is as follows: Setup /s /v"/qn REMOVE=ALL" To uninstall from a path changed from the default path of installation, the command line is as follows: Setup /s /v"/qn REMOVE=FeatureName INSTALLDIR=\"path\"" For a default load of the software, use the following sample command line: setup /s /v"/qn ADDLOCAL=JRE,WEBSERVER,REGISTRATION_SERVER,RAIDSERVER_NETSPY,IDE_SNMP LOGFILE_DIRECTORY=C:\TEMP /l*v c:\setup.log" 2.2 Installation for Linux Systems This section describes the Red Hat Linux installation procedure. Note: You must install Java Run-time Environment (JRE) before you install the MCC for Linux. The MCC package for Linux is based on JRE and cannot be launched without it. The link to the appropriate download for Java is http://java.sun.com/j2se/1.4/download.html. Table 2 lists the MCC features and the conditions necessary to use them. Table 2. MCC Features and Requirements Feature Requirement -------------------------------------------------------------------------- MegaRAID The TCP stack must be running for the Web Server to Web Server function. There is no requirement for installing Web Server. Web Server is installed in the /opt/LSI directory. There are no RPMs required. The.jar files and directories are simply copied to the /opt/LSI directory. MegaRAID The TCP stack must be running for the Registration Server to Registration function. There is no requirement for installing Server Registration Server. It is installed in /usr/sbin. RegSvr-x.y-z.i386.rpm IDE RAID IDE RAID can be installed only if the "megaraid" driver is detected by the system as loaded. The system checks whether the directory /proc/megaraid exists and is readable. RAID Server: RAID Server can be installed only if the "megaraid" driver is detected by the system as loaded. RSLinux-x.y-z.i386.rpm Spy-rh- x.y-z.i386.rpm Simple network management protocol (SNMP): SNMP can be installed only if the "megaraid" driver is detected by the system as loaded. Spy-rh- x.y-z.i386.rpm exsnmp- x.y-z.i386.rpm Note: See Section 2.6, "How to Install and Extend snmp Agent," for further detail on this feature. 2.2.1 Installing JRE in Linux Systems Perform the following steps to install JRE in Red Hat Linux: Note: Linux is case sensitive, so type all commands exactly as shown. Step 1. Place the CD-ROM into the CD-ROM drive. Step 2. If the CD-ROM is not already mounted, mount it by typing: eject Then place the CD-ROM into the CD drive and type: mount /mnt/cdrom Step 3. If the CD-ROM is already mounted, type: umount /mnt/cdrom Then place the CD-ROM into the CD drive, and type: mount /mnt/cdrom The files on the CD-ROM must be copied to a directory on the hard drive. You can copy these files to an existing directory or create a new directory. Step 4. To create a new directory, type: cd / Then type: mkdir , for example, mkdir java. Step 5. Perform the following steps to switch directories to the CDROM drive, and then copy the files to the directory on the hard drive you want to install into. (Perform these steps in order). a. To switch to the CD-ROM drive, type: mount /mnt/cdrom b. To display a list of the files on the CD, type: ls c. To copy the files from your CD to your hard drive, type: cp * / where destination is the directory on the hard drive you are copying to. For example, cp * /root would copy all the files on the CD-ROM to the directory /root. Step 6. Change to the directory you just copied the files into, and then look at the files in the directory Step 7. Type: cd / Step 8. Type: ls In the directory, you should see a file that ends with ".bin". This is the installation package that you want to run. Step 9. To run the installation package, which creates an RPM file, type: / for example, ./j2re-1_4_0_02-linux-i586-rpm.bin. This creates a file with a similar name with an RPM extension. For example, ./j2re-1_4_0_02-linux-i586-rpm.bin creates a file named j2re-1_4_0_02-fcs-linux-i586-rpm. Step 10. To get a list of files, type: ls Next, you install the RPM package. Step 11. In the directory in which the RMP package was created, type: rpm -ivh for example, rpm -ivh j2re-1_4_0_02-fcs-linux-i586-rpm Step 12. Open .bash_profile to add Java to the path. Step 13. Choose either PICO or VI as your text editor. Step 14. To edit the .bash_profile using PICO, type: cd /root then type: pico .bash_profile Step 15. To edit .bash_profile using VI, type: cd /root then type: vi .bash_profile The following displays on the screen, regardless of the text editor you use: # .bash_profile # Get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi # User specific environment and startup programs PATH=$PATH:$HOME/bin BASH_ENV=$HOME/.bashrc USERNAME="root" export USERNAME BASH_ENV PATH Step 16. Move the cursor to the line that starts with PATH=. Step 17. After PATH=, type: /usr/java/j2re1.4.0_02/bin: This changes PATH=$PATH:$HOME/bin to PATH=/usr/java/j2re1.4.0_02/bin:$PATH:$HOME/bin. Step 18. Save the file and exit. a. If using PICO, press to save the file. When prompted to save the file with changes, click Yes, then press to save as .bash_profile. b. If using VI, type the following to save the file: :wq Step 19. Close the terminal window and reboot. Step 20. During reboot, log on to Linux. The Java installation is complete. 2.2.2 Installing MCC in Linux Systems Perform the following steps to install MCC in Red Hat Linux: Note: Linux is case sensitive, so type all commands exactly as shown. You must install Java Run-time Environment (JRE) before you install the MCC for Linux systems. The MCC installation for Linux systems installs only in the Xterminal screen and does not execute properly in full screen shell (CTRL-ALT-F1). Make sure you install the from the GUI Xterminal screen only. Step 1. Place the CD-ROM into the CD-ROM drive. Step 2. If the CD-ROM is not already mounted, mount it by typing: eject then place the CD-ROM into the CD drive, and type: mount /mnt/cdrom Step 3. If the CD-ROM is already mounted, type: umount /mnt/cdrom then place the CD-ROM into the CD drive, and type: mount /mnt/cdrom The files on the CD-ROM must be copied to a directory on the hard drive. You can copy these files to an existing directory or create a new directory. Step 4. To create a new directory, type: cd / then type: mkdir , for example, mkdir java. Step 5. Perform the following steps to switch directories to the CDROM drive, and then copy the files to the directory on the hard drive. (Perform these steps in order). a. To switch to the CD-ROM drive, type: mount /mnt/cdrom b. To see a listing of files on the CD, type: ls c. To copy the files from your CD to your hard drive, type: cp * / where destination is the directory on the hard drive you are copying to. For example, cp * /root would copy all the files on the CD-ROM to the directory /root. Step 6. Change to the directory you just copied the files into, then look at the files in the directory. Step 7. Type: cd / Step 8. Type: ls In the directory, you should see a file that ends with "jar.zip", for example, a file such as MCCLinux_1.28-7.jar.zip. You need to rename this package so that it only ends with .jar. For example, MCCLinux_1.28-7.jar.zip becomes MCCLinux_1.28-7.jar. Step 9. To change the filename, type: mv For example, mv MCCLinux_1.28-7.jar.zip MCCLinux_1.28-7.jar. Step 10. Install the .JAR package by typing: java -jar <.JAR package name> For example, java -jar MCCLinux_1.28-7.jar Step 11. Go to the Xterminal window or console, and type: SetPass (with the letters "S" and "P" capitalized). Step 12. Enter a password. This is your MMC full access password. This is a case sensitive password, as are all passwords and commands in Linux. Step 13. Close the Xterminal Window. Step 14. Go to the Main Menu/Gnome Menu (the button on the bottom left). Next, if you are using Linux Red Hat 7.2 and 7.3, go to Programs > Start MegaRAID Web Server. If using Linux Red Hat 8.0, go to Extras > Other > Start MegaRAID Server. The MCC displays the version number and which port the console is listening on (it should be port 3570). Leave this program running. Step 15. Open up Netscape Communicator (or Mozilla if you are using Red Hat 8.0). Step 16. Go to URL http://localhost:3570. Your MegaRAID configuration screen displays. The installation procedure is complete. 2.2.3 Uninstalling MCC in Linux Systems Perform the following steps to uninstall MCC in Linux: Step 1. Switch to a graphical user interface (GUI). Access the directory /opt/LSI/_uninst Step 2. At the shell prompt, type: java -jar uninstall.jar Note: MCC installation does not support component updates. You can uninstall a feature and reinstall it. 2.2.4 Configuring Web Server and RAID Servers There are two ways to run MCC. The first is locally, where all the components are in a single machine. The second is in the network, with multiple systems running RAID servers. The following description applies to both. - The Web server is unaware of the registration server. It knows only about RAID servers. - RAID servers are unaware of the Web server. They know only about the Registration server. - Registration server is unaware of both - Web server and RAID servers. There must be only one Registration Server running in the network. It can co-exist with either Web Server or any RAID Server. Of course, in the LOCAL setup, all the components run on a same machine. Perform the following steps to configure Web Server and RAID Servers. Step 1. Registration Server must be running before the RAID Servers are started. Start Registration Server by typing the following at the prompt: /usr/sbin/RegSvr (/usr/sbin/RegSvr -stop to stop) Step 2. Next, make a RAID Server aware of the Registration Server. To do this perform the following steps: a. Open /etc/regserv.dat b. Type either the Internet Protocol (IP) address or the name of the server running the Registration Server. c. If you are using the name instead of the IP address, make sure the name is resolvable. (Try pinging the server using name.) d. If the name is not resolved, you can add the name to "hosts" file. (/etc/hosts) e. If everything is running locally, you can type "localhost" or 127.0.0.1 in the first line of /etc/regserv.dat. The steps above must be done in each machine where RAID Server is running. After that is done, all RAID Servers can be started. Step 3. To start a RAID Server, type the following at the prompt: /user/sbin/RSLinux (Type /usr/sbin/StopServer to stop a RAID Server) Step 4. Web Server must now be made to point at any of the RAID Servers. Perform the following steps to point Web Server to a RAID Server. a. Open the file /opt/LSI/mcc.properties This file contains many NAME=VALUE pairs. b. Locate the name "RAID_SERVER_NAME" c. Type either the name or IP of a RAID Server. d. If you are using the name, make sure it is resolvable. (Try pinging the machine using the name). If the name is not resolved, you can add the name to "hosts" file. (/etc/hosts) e. If everything is running locally, you may type RAID_SERVER_NAME=localhost Step To start WebServer, run: /opt/LSI/startup.sh 2.3 How to Set and Modify the Full Access Password The password must be set on every machine that runs RAID Server (RSLinux). Perform the following steps to set the password for the first time. Step 1. Type /usr/sbin/SetPass at the shell prompt. The SetPass utility prompts you to enter a new password and confirm it. Length of the password must not be more than 40 characters. Step 2. If a password has already been set, you can use SetPass to modify it. The password is maintained in the file /etc/raidpass.val Note: The password needs to be set every time you uninstall and install MCC. 2.4 Log File Information Log files log messages whose severity value is equal or more than the value set in the file /etc/rslinux.cfg. The log files, RSMessages.log and PollMessages.log, are created in the directory /var/log. The file /usr/sbin/RSLinux -ver prints version information. 2.5 Limiting the Size of Log Files MCC contains a feature to limit the size of log files. Perform the following steps to use this feature. Step 1. Open the file /etc/rslinux.cfg. This is basically an INF type of file with parameters in the form of NAME=VALUE. Step 2. Set the maximum size (in bytes) that the log file can be, using the NAME "max_log" field. RAID Server periodically examines the file size and reduces the file to half the maximum size set. For example, if the maximum size is 2 Mbytes, then when the file exceeds 2 Mbytes, it is truncated to roughly 1Mbyte in size. The default value is 1 Mbyte. Step 3. Use the NAME "trim_interval" field to specify the length of time until the next check of the log size. This check is to determine whether the log file needs to be reduced in size. The default value is 120 minutes. The oldest messages are deleted first. 2.6 How to Install and Extend snmp Agent To install and extend the snmp (simple network management protocol) agent, perform the following steps: Step 1. Get the source code of standard snmp and copy it in your machine. a. Download the file 'ucd-snmp-4.2.1.tar.gz' from the download section on the site 'http://netsnmp. sourceforge.net/'. b. Copy the file under '/usr' directory. c. Uncompress it using 'tar -zxvf'. This creates a directory 'ucd-snmp-4.2.1' Step 2. Compile the source and install the standard snmp agent. a. Go to the directory '/usr/ ucd-snmp-4.2.1'. b. Run configuration using './configure' (you may need to press enter 4-5 times). c. Run 'make' to build the agent. d. Run 'make install' to install it Note: The step2 installs the snmp agent (i.e. snmpd) under '/usr/local/sbin/'. In Linux you may have another snmp agent (i.e. snmpd) under '/usr/sbin/' with standard distribution. Don't confuse it with this. Step 3. Extend the snmp agent for 'Spy' support. Install the rpm file exsnmp-2.0-9.i386.rpm using "rpm -i exsnmp-2.0-9.i386.rpm" which will do the following: a. Copy the file 'MegaRaid.so', which is a dynamic link library to communicate with spy, under /lib b. Copy a proper snmp configuration file spysnmpd.conf under /etc/snmp/. The file spysnmpd.conf contains an entry "dlmod MegaRaid /lib/MegaRaid.so" (at the very last line). You can use this to obtain IDERAID information can through the 'Spy' daemon. Step 4. Run the extended snmp agent Note: If the snmp agent is already installed in the machine (e.g. in Red Hat Linux you may have it already) then step 1-2 is not required. a. Make sure 'Spy' is running before starting the snmpd agent. Then stop and start the agent using '/etc/rc.d/init.d/snmpd -c /etc/snmp/ spysnmpd.conf' b. You can test the agent using: 'snmpwalk localhostpublic.iso.org.dod.internet .private.enterprises.3582.1' 5.3 Using the MCC Software Utility This section describes the MCC software utility. You can use the software utilities that come with MCC to perform the following actions: - Get information about the configuration. - Track the health of the arrays and physical drives. - Track S.M.A.R.T. status of the physical drives. - Rebuild an array. - Perform a consistency check on array. - Check error log where all drive failures are reported. To log onto the RAID Server, enter the Internet address in the Internet browser. The MCC screen displays. Click the server name to select the RAID Server you want to configure. Continue the log-on procedure by selecting View Only or Full Access. Table 3 describes the access options. Table 3. Access Options Option Description ------------------------------------------------------------------------ View Only Allows you to only view the RAID configuration. It does not allow you to perform rebuilds or check consistency. Full Access This allows you to view, configure, and manage the RAID configuration. This option requires you to supply the Full Access Password. Table 4 displays the contents of MCC main screen. It is broken up into five frames. Table 4. Main Screen Contents Frame Description --------------------------------------------------------------------------- Top The top frame displays the following information: - Server ID that you are logged on to. - Mode you are logged on in. - Type of RAID you are using. Left This frame lists the following options (described in Table 5): - Scan Devices - Configuration View - Device Progress - Log Data - Advanced - Back Plane - Close Server Middle Upper This frame displays the Physical Disk Drive View. Middle Lower This frame displays the Logical Disk Drive View. Right This frame displays the type of actions you can perform. It also displays extended options and links when certain links are selected. Table 5 describes the options in the left frame. You can click the options to perform actions or display the related screens. Table 5. Options on the Main Screen Name Description ------------------------------------------------------------------------- Scan Devices Rescans the system for new hard drives. After you click this button, the driver rescans all PCI devices. You will notice a significant decrease in system performance for a few seconds. Config View Displays the RAID configuration, media errors, and status of the drives and arrays. It also allows you to start activity on a particular array. - Logical View - displays information about the arrays. - Physical View - displays all hard drives attached. Device Progress Displays the progress bar for the current activity on the MegaRAID. The progress bar displays the time left and percentage complete. Possible actions include the following: - Rebuild - Consistency check Log Data Displays activity log information. All actions add records to the activity log file. The size of this file can be modified by clicking the Advanced button. Advanced Allows you to modify the parameters for the RAID system. Back Plane Some systems can have built-in back plane devices. MCC supports several types of back planes. See the user manual for your system. Close Server Returns you to the list of available servers. Note: The proper way to exit MCC is to click the Close Server button. If you exit any other way, there is a two-minute window in which you cannot log back in with full access. A small browser window runs in the background as soon as you log on to the RAID Server. It constantly refreshes the view so you have the most current information. 3.1 RAID Properties To view the RAID properties, click the button next to the RAID controller. After you click the button, the RAID ID displays in the right frame, and the link to the RAID Properties page displays below the ID. Click on the word Properties. The Property Description screen then displays. Table 6 provides a description of each field. To exit this screen, click Config View or Scan Devices. Table 6. RAID Properties Field Description --------------------------------------------------------------- Model Specifies the model number. Driver Version Specifies the driver version. ROM Version Specifies the ROM version. Revision Specifies the revision. Interrupt Specifies the interrupt. Bus Master Specifies the Bus Master Base Address. Base Address PCI Bus ID Specifies the PCI Bus ID. Device ID Specifies the Device ID. Primary Channel Specifies the Primary Channel Base Address. Base Address Primary Channel Specifies the Primary Channel Control Address. Control Address Secondary Specifies the Secondary Channel Base Address. Channel Base Address Secondary Specifies the Secondary Channel Control Address. Channel Control Address 3.2 Physical Drive To view the Physical Drive Properties and Error Status, click the button next to physical drive you want to view. After you click the button, the Physical Drive ID displays in the right frame. The links to the RAID Properties and Error Status page are listed as shown below. Click on the link Properties to display the Physical Drive Properties. Click the Error Status to display the Physical Drives Error Status. 3.2.1 Physical Drive Properties This screen displays the physical drive properties. Table 7 provides a description of each field. To exit this screen, click on Config View or Scan Devices. Table 7. Physical Drive Properties Field Description -------------------------------------------------------------------------- Firmware Specifies the firmware version of the physical drive. Status Specifies gives the status of the physical drive. (online or offline) Errors Specifies gives the number of errors in the physical drive. S.M.A.R.T. Specifies the S.M.A.R.T. (self-monitoring analysis and Status reporting technology) status of the physical drive. S.M.A.R.T. helps monitor and predict the reliability and performance of the hard drive. The options for this are Disabled, OK, or Error. Disabled means S.M.A.R.T. is off and physical drive does not collect statistical data. OK means S.M.A.R.T. is on and no errors found. Error status means S.M.A.R.T. is on and some errors found; this is a serious warning that means the drive has to be replaced. Logical Drive Specifies the logical drive information about this physical drive. (by drive letter or volume) Capacity Specifies the capacity of this physical drive. Transfer Mode Specifies the type of transfer mode used on this physical drive. Part of Array Specifies the part of the array wo which this physical drive belongs. The RAID mode for a striped array (RAID 0) is called performance, and for a mirrored array (RAID 1) is called reliability. Connection Specifies the type of IDE connection that is used to connect this drive to the RAID controller. (primary or secondary, master or slave) Model Specifies the model number of the physical drive. Serial Number Specifies the serial number of the physical drive. 3.2.2 Physical Drive Error Status This screen displays the physical drive error status. Table 8 provides a description of each field. Table 8. Physical Drive Error Status Field Description --------------------------------------------------------------------- Time and Date Specifies the time and date the error was logged. Error Specifies the error type. See Table 9 for the error codes. Sector Specifies the sector that contains the error. Error codes for the physical drives display when you select the Error Log view. Table 9 provides a list and description of the error codes. Table 9. Physical Drive Errors Code Description ------------------------------------------------------------ Error 01 Media read error. The disk surface is damaged. Error 02 Media write error. The disk surface is damaged. Error 03 Media verify error. Error 04 Missing drive type. 3.2.3 Array To display the Array Properties, perform a Check Consistency, or rebuild the array, click the icon in the lower middle frame next to Array. After you click the icon, the Array ID displays in the right frame. The links to the Array Properties, Check Consistency, and Rebuild display as shown on the screen. Click the word Properties to view the Array Properties. The Array operations are described in the following information. Note: Due to high resource usage during Rebuild and Consistency Check operations in the Windows operating system, only one action per RAID Server is allowed in Windows. Check Consistency and Rebuild menu items appear only for the appropriate array (see the subsection entitled "Array Check Consistency" and the subsection entitled "Array Rebuild Device Progress"). Array Check Consistency - Click Check Consistency to check the correctness of the redundant data in an array. You can choose to make the data on both drives identical. This function can be performed only on RAID1 and RAID10 arrays. After you click Check Consistency, the options in Table 10 display in the right frame. Table 10. Check Consistency Options Code Description ------------------------------------------------------------------------- Check All Partitions Check this option to perform the consistency check on all valid partitions (logical drives). Option is valid only for Windows Raid Servers. Abort Check When the Check Consistency begins, the words Consistency Checking Consistency flash next to the array that is being checked. You can abort the Check Consistency by clicking Abort Check Consistency in the right frame. You can view the progress of the Check Consistency by clicking Device Progress in the left frame. Check Consistency This screen displays the progress of the Check Device Progress Consistency. Table 11 provides a description of each field. Table 11. Check Consistency Progress Field Descriptions Field Description ------------------------------------------------------------------------ Array Specifies the array number being checked. Operation Specifies the type of operation being performed. Example: Check Consistency. Percentage Indicates the percentage completed. Time Left Indicates the estimated time left to complete the task. Progress Displays graphical representation of the progress. To exit this screen, click Config View or Scan Devices. Array Rebuild Device Progress - The Array Rebuild Device Progress screen displays the Array Rebuild Progress. Table 12 provides a description of each field. Table 12. Array Rebuild Device Progress Field Descriptions Field Description ------------------------------------------------------------------------ Array This field gives the array number being rebuilt. Operation This field gives the type of operation being performed. Example: Rebuild. Percentage This field gives the percentage complete. Time Left This field gives the estimated time left to complete the task. Progress This gives a graphical representation of the progress. To exit this page, click on Config View or Scan Devices. Array Properties - This screen displays the Array Properties. Table 13 provides field descriptions. Table 13. Array Property Field Descriptions Field Description ------------------------------------------------------------------------ Mode Displays the RAID level. IDE RAID supports RAID 0, 1, and 10. Status Displays the health of the array. The array health status can be one of the following: On Line - Working within normal parameters. Off Line - All drives have failed. Deteriorated - One of the drives has failed. Logical Drive Displays the logical drive letters or volume names. Stripe Size Displays the stripe size. A stripe size is the minimal amount of data that can be written to the drive in one write. Note: RAID level 1 does not have a stripe size parameter. Stripe size parameters are available for RAID level 0 and RAID level 10 array sets only. The stripe size parameter can be set only when the array is created. Capacity Displays the actual size of the array. This size is reported to Operating System. Error Threshold This parameter is user defined. Users can define the error threshold on each drive. For more information on how to set the error threshold, see the Advanced menu description. Constituent Displays the physical drives joined to an array. Physical Drives To exit this page, click on Config View or Scan Devices. 3.2.4 Log Data This screen displays the Log Data screen. Use the scroll bar to view the log. To exit this page, click on Config View or Scan Devices. 3.2.5 Advanced Settings This screen displays the Advanced Settings of the MCC. Table 14 provides a description of each field. Table 14. Advanced Settings Field Description ----------------------------------------------------------------------- Fail Physical Drive if Marks drive as Failed when error threshold is Error Threshold reached. After this drive is marked as Failed, it Reached can't be used anymore. Drive status can be changed only from the BIOS Configuration Utility (). This option is not set by default. Start Rebuilding if MCC begins an automatic rebuild if the array has Error Threshold more than a specified number of errors. If so, it Reached starts an automatic rebuild. This option is valid only for arrays set for reliability mode (RAID 1 mirrored arrays). Check Array for MCC checks the number of errors in the arrays to Rebuild at Startup see if they need rebuilding. Stop Rebuilding if If the maximum number of errors allowed is found Rebuilding Error in an array during rebuild, MCC will stop the Threshold Reached rebuild. Make Contents of If MCC finds mismatches between two mirrored Array Drives Identical (RAID 1) arrays, it will copy the data from one after Check drive to the other to make them identical. Consistency error found This option is valid only for arrays set for reliability mode (RAID 1 mirrored arrays). Delete Activity Log This deletes the activity log file if it reaches Files when it reaches the maximum allowable size (as set in the box maximum Allowed Size below this item). If checked, the activity log file is overwritten when it reaches the maximum size. If not checked, the file stops updating when it reaches the maximum size and is not updated anymore. Activity Log File Size Use this box to select the maximum size for the activity log file. Enable S.M.A.R.T. on If this option is checked, it enables S.M.A.R.T. Physical Drive monitoring of all physical drives. S.M.A.R.T. Poll Interval: This setting allows you to set the time interval that S.M.A.R.T. status is checked. Note: S.M.A.R.T. stands for self-monitoring, analysis, and reporting technology. This feature is built into the hard drive that checks for potential problems that can crash the hard drive. Not all hard drives have this feature. To exit this page, click on Config View or Scan Devices. Backplane - This screen displays the backplane information of the RAID array. Different backplanes can have different features. This application shows the following: - Current temperature inside the backplane - Error log - Fan speed To exit this page, click Config View or Scan Devices. Close Server - To exit this RAID server, click Close Server in the left frame.