RAIDWatch® Effortless RAID Management Java-based GUI Manager for Infortrend Disk Array Subsystems User’s Manual Software Revision: 2.3.X (with a sub-version for Mac OS) Version 1.
RAIDWatch User’s Manual Contact Information Asia Pacific (International Headquarters) Infortrend Technology, Inc. 8F, No. 102 Chung-Shan Rd., Sec. 3 Chung-Ho City, Taipei Hsien, Taiwan Tel: +886-2-2226-0126 Fax: +886-2-2226-0020 sales.ap@infortrend.com support.ap@infortrend.com http://esupport.infortrend.com.tw http://www.infortrend.com.tw Infortrend Corporation 3150 Coronado Dr., Unit C Santa Clara, CA 95054 USA Tel: +1-408-988-5088 Fax: +1-408-988-6288 sales.us@infortrend.com http://esupport.infortrend.
RAIDWatch User’s Manual Copyright 2006 First Edition Published 2005 All rights reserved. This publication may not be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written consent of Infortrend Technology, Inc.
RAIDWatch User’s Manual Table of Contents CONTACT INFORMATION ..................................................................................................... II COPYRIGHT 2006................................................................................................................. III First Edition Published 2005............................................................................................ iii Disclaimer ............................................................................
RAIDWatch User’s Manual 3.4.4 Installing RAIDWatch on a Solaris Platform ................................................. 3-7 3.4.5 Installing RAIDWatch on a Mac OS Running Safari Browser ....................... 3-8 3.4.6 Installing RAIDWatch Main Program.......................................................... 3-12 3.4.7 Installing Software Components................................................................... 3-15 3.4.8 Stand-alone (on Host or Subsystem) Installation ............................
RAIDWatch User’s Manual Logical Drive Information.............................................................................................. 5-4 Logical Volume Information........................................................................................... 5-4 Fibre Channel Status...................................................................................................... 5-5 System Information................................................................................................
RAIDWatch User’s Manual CHAPTER 7 CONFIGURATION PARAMETERS 7.1 ACCESSING CONFIGURATION PARAMETERS OPTIONS ........................................ 7-2 7.2 COMMUNICATIONS ................................................................................................ 7-3 7.3 CONTROLLER ......................................................................................................... 7-4 7.4 SYSTEM ........................................................................................................
RAIDWatch User’s Manual 9.3.2.3. Setting LV Parameters ...........................................................................................9-20 LV Assignment ...................................................................................................................9-20 Select Write Policy ..............................................................................................................9-21 9.3.2.4. Click OK to Create LV.............................................................
RAIDWatch User’s Manual 14.1. CENTRALIZED MANAGEMENT INTRODUCTION .................................................. 14-2 14.2. SETTING UP THE UTILITY ................................................................................... 14-2 14.3. CENTRALIZED MANAGEMENT CONNECTION ..................................................... 14-4 14.4. MAINTENANCE & CONFIGURATION ................................................................... 14-4 14.4.1 Icon Labels...............................................
RAIDWatch User’s Manual iSCSI Initiator CHAP Configuration Entries.............................................................6 Table 11-1: Array Information Icons .........................................................................................3 Table 11-2: Severity Level Icons ...............................................................................................6 Table 11-3: Device Icon .....................................................................................................
RAIDWatch User’s Manual Figure 4-22: Create Plug-in Receiver Profile ...........................................................................13 Figure 4-23: Editing the Severity Level ...................................................................................14 Figure 4-24: Selecting the Severity Level ................................................................................15 Figure 4-25: Enabling a Notification Method under Status Row .............................................
RAIDWatch User’s Manual Figure 6-32: Host LUN Mapping Right-click Menu................................................................28 Figure 6-33: The “Outer Shell” System View Window ...........................................................29 Figure 6-34: Opening Device for Multi-Array Management ...................................................30 Figure 7-1: Opening the Configuration Parameters Window.....................................................2 Figure 7-2: The Communication Page ........
RAIDWatch User’s Manual Figure 10-8: iSCSI Initiator Menu .............................................................................................6 Figure 11-1: Selecting Information Windows ............................................................................2 Figure 11-2: Selecting Information Windows ............................................................................3 Figure 11-3: Displaying Enclosure Device Information ............................................................
RAIDWatch User’s Manual User’s Manual Overview Congratulations on your decision to use Infortrend’s RAIDWatch management software program. This management program allows you to control and monitor disk array subsystems from a local host, a remote station connected through a local area network (LAN), In-band host links, or the Internet.
RAIDWatch User’s Manual Chapter 4: Configuration Client Options Describes how to configure the RAIDWatch sub-module configuration client and event notification for faxes, e-mail, broadcast, and so on. Other functionalities of the utility are also described in full. Information about the supported notification levels are also provided to aid in explaining these functions. Chapter 5: RAIDWatch Icons Describes the icons used in RAIDWatch GUI.
RAIDWatch User’s Manual Part 3: System Monitoring Chapter 11: System Monitoring & Management Discusses how to obtain the current status of SAF-TE, I2C, and S.E.S. monitoring devices and get updates on the status of storage system components. Descriptions on how to access these different monitoring devices are given and the type of information that is offered by these devices is shown. Chapter 12: Enclosure Display The Enclosure View customization is discussed fully in this chapter.
RAIDWatch User’s Manual Usage Conventions Throughout this document, the following terminology usage rules apply: “Controller” always refers to Infotrend RAID array controllers. “Subsystem” refers to Infortrend EonStor 8-, 12-, 16-bay or 24-bay RAID array subsystems. “RAIDWatch” refers to the entire program and all of its modules. “RAIDWatch Manager” refers only to the management interface, not to any other parts of the software.
RAIDWatch User’s Manual IMPORTANT! The Important messages emphasis on using RAIDWatch management software. WARNING! Warnings appear where overlooked details may cause damage to the equipment or result in personal injury. Warnings should be taken seriously. Software and Firmware Updates Please contact your system vendor or visit Infortrend’s FTP site (ftp.infortrend.com.tw) for the latest software or firmware updates.
RAIDWatch User’s Manual Revision History November 18, 2006 Added installation procedures for RAIDWatch using Safari browser under Mac OS X. August 16, 2006 Added options recently implemented for iSCSI protocols such as Mutual CHAP, Jumbo Frames, iSCSI initiator access control, etc. May 30, 2006 This version reflects some new functions in firmware, including Enclosure Spare, a different event severity identifier, slot-based resource assignment, etc.
RAIDWatch User’s Manual RAID level 6 is newly added to RAIDWatch 2.2.c. The RAID level 6 function is mentioned in Chapter 2, Chapter 9 as well as a clear description in Appendix C. Several new RAIDWatch functions are added in 2.2.c version according to Firmware version 3.47. Those functions are only available when firmware is running 3.47 or above version. They are explained across Chapter 7 and Chapter 9. May 18, 2005 This manual was revised for RAIDWatch revision 2.2.
RAIDWatch User’s Manual November 15, 2004 Revised for RAIDWatch revision 2.1.b. This is an initial RAIDWatch version to support iSCSI subsystems. The cover of the manual and the header/footer through out the manual were modified to match the hardware manual. Graphics for note, caution, important, and warning messages were added. In Chapter 3, some figures for notification settings were added to make the description more clear.
RAIDWatch User’s Manual Chapter 1 remained largely unchanged with only minor editorial corrections that do not directly affect the content. Chapter 2 was separated into two chapters. In the previous revision, Chapter 2, Installation, described system and platform requirements, installation, and different configuration options. This chapter was separated into Chapter 2 Installation, which describes the new RAIDWatch installer, and Chapter 3 Configuration Options in the new revision.
Chapter 1 Introduction This chapter provides information about the RAIDWatch management program. The following topics are discussed in this chapter: ♦ RAIDWatch Overview – Section 1.1, page 1-1 1.1.1 Product Description 1.1.2 Feature Summary ♦ Featured Highlights – Section 1.2, page 1-3 1.2.1 Graphical User Interface 1.2.2 Enclosure View 1.2.3 Powerful Event Notification Function 1.2.4 Java-based Remote Management ♦ Conceptual Foundation – Section 1.3, page 1-9 1.3.
RAIDWatch User’s Manual 1.1 RAIDWatch Overview 1.1.1 Product Description Infortrend’s innovated RAID manager, RAIDWatch, is a Java-based program specifically designed for use in managing Infortrend’s RAID subsystems. RAIDWatch provides a user-friendly interface that graphically represents disk array elements and simplifies the normally complicated process of array configuration.
Chapter 1: Introduction 1.
RAIDWatch User’s Manual 1.2.2 Enclosure View Figure 0-1: Enclosure View Window The enclosure window shown in Figure 0-1 provides real-time reporting of the status of enclosure components, including components that can be accessed through the front or the rear side of an enclosure. When a drive fails, the system highlights the corresponding LED icon of the failed drive by changing its display color. When you remove a drive, its icon is removed from the enclosure window.
Chapter 1: Introduction RAIDWatch’s sub-module, Configuration Client, that is installed onto a management station and runs independently from the main manager program. Notifications can be sent via the Internet as email messages, via a local network as a broadcast message, SNMP traps, MSN messenger, SMS short message, or via fax/modem as fax messages without location constraints. To setup the event notification options, please refer to Chapter 4 in this manual. 1.2.
RAIDWatch User’s Manual 1.2.4.2 Mode Two: Stand-alone (on Host) For configurations depending on the existing SCSI, iSCSI, or Fibre host connection for RAIDWatch-to-RAID communications. Servers in DAS (Direct Attached Storage) environments, SCSI host models for example, require RAID agents for RAIDWatch commands to pass through and communicate with RAID arrays. RAID agents are installed onto the servers that are directly attached with a RAID subsystem. 1.2.4.
Chapter 1: Introduction Table 0-1 shows the modules installed and the installation mode required: Installation Software Modules Mode One Management Center: Root Agent + Configuration Client utility Mode Two RAID Servers (servers A, B, and C) via inband Mode Three Independent Array Java Runtime Management Station Table 0-1: Software Modules: Heterogeneous RAIDWatch Connection Figure 0-4: Typical RAIDWatch Connection – Heterogeneous 2.
RAIDWatch User’s Manual Figure 0-5: Typical RAIDWatch Connection – Applet Mode 3. Stand-alone/Out-of-Band (on Host) Installation: This installation provides management access with no centralized management utility. Event notification is provided through an independent NPC utility. RAIDWatch accesses RAID subsystems over the network through the command exchanges between a manager station and RAIDWatch programs that exist in array hard drives, (See Figure 0-6.
Chapter 1: Introduction 1.2.5 Multi-Language Support RAIDWatch is a useful RAID management tool that is being used worldwide. The software is currently available in four (4) languages: English, Deutsch, Spanish and Japanese. Support for other languages is under development. The language display is easily changed using the language selection on the program menu bar. As soon as a language is selected, the user interface, wizards, and online help display the chosen language. 1.2.
RAIDWatch User’s Manual 1.3 Conceptual Foundation In order for RAIDWatch to function properly, different software modules must be correctly installed on different servers and stations in a given LAN or WAN. If you follow the default installation during the installation process, RAIDWatch will be installed as a centralized management tool into your system. 1.3.1 Centralized Management (Agent-based) Installation 1.
Chapter 1: Introduction Mode 1 All Modes Centralized Management Centralized Management Server Installed Elements Remote Browser Station Mode 2 Mode 3 Stand-alone on Host Stand-alone on Subsystem Server w/ RAID Directly Attached RAID Subsystem (Applet Mode) (in-band) Root Agent Yes - - - RAID Agents Yes - Yes - RAIDWatch Manager Yes - Yes, if it is used to run RAIDWatch Yes Configuration Client Yes - - - Yes, if it is used to run RAIDWatch Yes Yes - Web Browser Yes Yes
RAIDWatch User’s Manual NOTE: If the In-band connection to RAID arrays is used, the RAIDWatch program can access the arrays only when one logical drive exists and is associated with host ID/LUNs. Another way to establish In-band connection is to configure RAID subsystems’ host-LUN settings. Use LCD panel or RS-232 terminal program to create a logical drive when you are using a completely new hard array before installing RAIDWatch version 2.0 or above.
Chapter 2 RAIDWatch Considerations Before you begin installing RAIDWatch, the following items should be considered: ♦ Background Information – Section 2.1 on Page 2-2 ♦ Definition of Terms – Section 2.2 on Page 2-2 ♦ Operating with Spare Drives – Section 2.3 on Page 2-3 ♦ Operating without Spare Drives – Section 2.4 on Page 2-3 ♦ Before You Start – Section 2.
RAIDWatch User’s Manual 2.1 Background Information Redundant Arrays of Independent Disks (RAID) is a storage technology used to improve the processing capability of storage systems. This technology is designed to provide reliability (i.e., “fault tolerance”) in disk array systems and to take advantage of the performance gains multiple disks can offer. RAID comes with a redundancy feature that ensures fault-tolerant, uninterrupted disk storage operations.
Chapter 2: RAIDWatch Considerations rebuild the array, you will also need to replace the failed drive manually to create another spare in case another drive fails. ♦ Failed drives. These are physical drives that fail due to some type of error. Failed drives appear with red LED marks on their respective icons. ♦ Logical drives. Logical drives are the combinations of multiple physical drives. Combining physical drives into logical drives gives you a disk array with a certain RAID level.
RAIDWatch User’s Manual shutting down the system (hot-swapping). All EonStor subsystems support drive hot-swapping. ♦ If the replacement drive is installed on the same channel and ID (the original drive slot where the faulty drive was), you can then proceed with data rebuilding.
Chapter 3 Installation This chapter describes RAIDWatch requirements and the installation procedure. The following sections are covered in this chapter: System Requirements – Section 3.1, page 3-2 3.1.1 Server Running RAIDWatch 3.1.2 Local Client Running RAIDWatch Manager RAID Chart – Section 3.2, page 3-3 Platform Requirements – Section 3.3, page 3-4 Software Setup – Section 3.4, page 3-5 3.4.1 Before You Start 3.4.2 Installing RAIDWatch on a Windows Platform 3.4.
RAIDWatch User’s Manual 3.1 System Requirements The minimum hardware and software requirements for RAIDWatch are listed below. 3.1.1 Server Running RAIDWatch A server can be chosen as the Centralized Management center, which uses the Configuration Client utility and can be installed with the RAIDWatch manager program using the first installation scheme (Centralized Management).
Chapter 3: Installation ♦ Windows Messaging (MAPI) for Windows 2000/2003 if fax notification support is needed. ♦ Windows NetBEUI support for Windows 2000/2003 must be enabled if network broadcast support notification is needed. Please refer to your Windows documentation for more information. ♦ SNMP traps service for Windows NT if SNMP traps notification is desired. ♦ TCP/IP with a valid IP assigned to each controller/subsystem. Static IP is recommended.
RAIDWatch User’s Manual Role Centralized Management Center Storage pool …. Yes N/A …. Internet Capable Table 3-1: RAID Charting Table ♦ ID/Name – User designated; an ID or name should be a unique identifying label. ♦ Location – A specific geographic reference (e.g., headquarters, Building 3, Equipment Room 100.) ♦ OS – The Operating System running on the particular system. ♦ IP Address – If available. ♦ Role – The purpose fulfilled by the particular system, relative to RAID operations.
Chapter 3: Installation 3.4 Software Setup This section discusses how to install RAIDWatch in your system. Before proceeding with the setup procedure, read through the Before You Start section below. The sections follow will explain how to install RAIDWatch in different operation systems. 3.4.1 Before You Start Before starting the installation, read through the notes listed below: ♦ TCP/IP must be installed and running with a valid IP address assigned to a server.
RAIDWatch User’s Manual Figure 3-1: Product Utility CD Initial Screen Step 4. Click the supported platform on the right-hand side to start the installation process. The current availability is “Windows 2000 and above.” (See Figure 3-2) Figure 3-2: The Platform Window Step 5. If your server or workstation is not ready with Java Runtime (at least version 1.4.2), an install shield will automatically install Java Runtime onto your machine. Please follow the on-screen instructions to proceed. Step 6.
Chapter 3: Installation Step 1. Insert the Infortrend Product Utility CD or RAIDWatch installation CD into the system’s optical drive. Step 2. If you are currently running other applications, close them before proceeding with the setup process. This will minimize the possibility of encountering system errors during setup. Step 3. Open the file manager and change the directory to /mnt/cdrom Step 4. Execute ./linux.sh to start the software installation. Step 5. Be sure to install JRE 1.4.
RAIDWatch User’s Manual Figure 3-3: File Manager Window in Solaris Platform Step 5. A Run window prompt will display. (See Figure 3-4) To install the Java-based GUI RAIDWatch manager main program, type YES and then press Enter. This will launch RAIDWatch manager install shield. Please refer to Section 3.4.5 for step-by-step installation procedures. Figure 3-4: The “Run” Window 3.4.
Chapter 3: Installation password is not available, you may reboot from an installation CD and find the menu item for “Password Reset.” NOTE: You may temporarily disconnect your Mac machine from the network during the time you use the root account to complete specific configuration task. Unauthorized access during the time can cause problems to your OS. Remember to re-connect the cabling after RAIDWatch installation. To enable the root access: Step 1. Login in on the Admin account. Step 2.
RAIDWatch User’s Manual Figure 3-6: The “NetInfo Manager” in the Utilities Sub-folder Step 3. Click on the “Lock” icon on the lower left of the screen before you make configuration changes. Figure 3-7: The “Lock” Icon and Security Option 3-10 Step 4 Locate the “Security” item from the top menu bar. Select “Enable root user.” You will have to enter the administrator’s password to authenticate yourself. Step 5 From this screen you can also enter a new password for root access.
Chapter 3: Installation Find the “password” field, click on the value field to alter it (it should contain just the “*” as an encrypted password). Double-click and then enter a new password. Make sure there are no spaces left in the value field. Step 6 Log out and log in as the “root” user to verify that it worked. Select “Other” from the login screen and manually enter “root” as user name and its associated password.
RAIDWatch User’s Manual 3.4.6 Installing RAIDWatch Main Program (for All Platforms) When the install shield of RAIDWatch main program is launched, follow the steps below to complete the installation. Step 1. To install RAIDWatch, click the Next button at the bottom of the window. If you do not wish to continue with the installation process, select the Cancel button. Figure 3-9: Welcome to the Install Shield Window Step 2.
Chapter 3: Installation Step 3. If you accepted the License Agreement in Figure 3-10, a new window with two installation options will appear. These options, shown in Figure 3-11, are Typical Install and Custom Install. The default is set to Basic Install. All users are recommended to install RAIDWatch program using the default settings. This will create a new “Infortrend Inc” folder on the computer chosen as a management center.
RAIDWatch User’s Manual The new Central Management utility is also installed in this process. The utility provides Online monitoring of Infortrend RAID subsystems in the network. ♦ Stand-alone (on Host) – Selecting this option will install the In-band driver (RAID agents) for servers that are directly attached to a RAID subsystem, and the RAIDWatch software on the local computer. ♦ Stand-alone (on Subsystem) – This will install the software onto the controller/subsystem itself.
Chapter 3: Installation 3.4.7 Installing Software Components RAIDWatch allows you to install its management utility redundantly onto two different servers. This prevents blind time if one server fails or is powered down for expected reasons. Note that if a server is chosen as either the Master or Slave host, RAIDWatch must be manually installed on it. Figure 3-13: Choice of Software Module Redundancy RAIDWatch allows you to select components during the Custom installation process.
RAIDWatch User’s Manual Figure 3-15: Installing Active Step 1. If the Next button from Figure 3-14 was selected, the Install Active window shown in Figure 3-15 will appear. If you wish to stop the installation procedure, then click the Cancel button.
Chapter 3: Installation Step 2. Once the software has been successfully installed, a window indicating the successful installation (see Figure 3-16) will appear. To complete the process and exit the window, click Finish. Figure 3-16: Successful Installation 3.4.
RAIDWatch User’s Manual Step 1. As shown in Figure 3-17 above, enter the IP address or the host name of the controller/subsystem and the controller password in their respective fields. The default for the controller/subsystem IP or password is blank. The preset IP and password should have been configured along with other configuration utilities before proceeding with the RAIDWatch installation.
Chapter 3: Installation Figure 3-19: Successful Installation NOTE: 1. RAIDWatch installation onto a Mac machine requires you to reboot your system for RAID agents to run properly. 2. Some sub-menus in RAIDWatch can be brought up using the menu bar at the top of configuration screen or by a right-click. Since some of the Mac machines do not come with a two-button mouse, using the combination of the command key” also activate these configuration menus.
RAIDWatch User’s Manual Step 4. If you wish to immediately access the RAIDWatch manager, open a web browser and type in the IP address that you used in Figure 3-17. To run the RAIDWatch Manager from the controller, enter the following into the address bar of the web browser: http://www.xxx.yyy.zzz where www.xxx.yyy.zzz is the IP address entered in Figure 3-17. 3.5 Program Updates As Infortrend’s valued customer, you are entitled to free program updates.
Chapter 3: Installation 3.6.2 Related Configuration on Controller/Subsystem The RAID controller or subsystem must make some adjustments as well as the host computer's SNMP settings before the two can communicate using SCSI commands. You can use the RS-232 terminal utility to change the RAID controller settings. Step 1. From the Main Menu, press the Up or Down buttons to select “View and Edit Configuration Parameters.” Step 2.
RAIDWatch User’s Manual NOTE: Be sure to change the Peripheral Device Type to your preference after the in-band host links have been properly connected.
Chapter 4 Configuration Client Options This chapter describes the Configuration Client options. There are a number of different items that users can configure. These include the Root Agent and RAID Agents relationship and the configuration options concerning event notification. The following sections are covered in this chapter: ♦ The Configuration Client Utility – Section 4.1, page 4-2 4.1.1 Start the Configuration Client 4.1.2 Setting Up a Root Agent ♦ Configuration Client – Section 4.2, page 4-6 4.2.
RAIDWatch User’s Manual 4.4.8 MSN Settings 4.4.9 SMS Settings ♦ Auto Discovery – Section 4.5, page 4-26 ♦ Event Severity Levels – Section 4.6, page 4-29 4.6.1 Level 1 Severity Events (Examples) 4.6.2 Level 2 Severity Events (Examples) 4.6.3 Level 3 Severity Events (example) ♦ Event Log Display – Section 4.7, page 4-30 4.1 The Configuration Client Utility 4.1.
Chapter 4: Configuration Client Options Figure 4-2: Configuration Client Shortcut on Windows Startup Menu Step 3. Click on Configuration Client to activate the Configuration Client window as shown in Figure 4-3. The Configuration Client program allows you to configure the following items: ♦ Root Agent (administrative settings) ♦ Auto Discovery ♦ Notification configuration options Figure 4-3: Configuration Client Window 4.1.2 Setting Up a Root Agent Step 1. Launch the Configuration Client program.
RAIDWatch User’s Manual Figure 4-4: Add Host Command Figure 4-5: Input Root Agent Dialog Box NOTE: The Root Agent IP is usually the computer IP where the Configuration Client is installed. Step 3. The connected IP displays on the left of the Connection View window. Select the IP and click the Connect Root Agent Server icon (see Figure 4-6) or right-click on the displayed IP to display the Connect commands.
Chapter 4: Configuration Client Options Figure 4-7: Connect Commands Step 4. The Configure user dialog box appears. Select to log in either as an Administrator or Guest. An administrator has the authority to change any configuration client settings, unlike a guest is allowed to view the settings only. (See Figure 4-8) Figure 4-8: Access Rights Selection Box Step 5.
RAIDWatch User’s Manual Figure 4-10: Left Column of Configuration Client User Interface Step 8. The Module Configuration window will display on the right of the Configuration Client User Interface. You may now start configuring event receivers under each notification method window. Click on the Module Name pull-down list to display all the configuration options. (See Figure 4-11) Figure 4-11: Module Name Pull-down List 4.
Chapter 4: Configuration Client Options Figure 4-12: Major Elements in Configuration Client User Interface 4.2.1 Command Menu • File commands include Add Host and Exit. The Add Host command connects you to a Root Agent host. A Root Agent host is one that is chosen as a management center to manage multiple RAID agents, which are, in turn, used to access different arrays. By connecting to a Root Agent IP, all its subsidiary RAIDs are then managed by the management center.
RAIDWatch User’s Manual • Save Bookmark File: This button allows you to save the current connection profile (as shown in the Navigation panel) as a file to your system drive. A file path dialog box displays when selected. • Connect Root Agent Server: This button allows you to connect to a Root Agent server to begin monitoring, for example, in situations when it has been manually disconnected. NOTE: The Root Agent IP is the IP of the computer where you installed your Configuration Client utility.
Chapter 4: Configuration Client Options Delete Host: Delete the Root Agent Server by selecting this command. Connect: Select this command to connect your computer to the Root Agent Server. Disconnect: To disconnect the Root Agent Server from your computer, select this command. Generate Dummy Event: You can also generate simulated events to test the notification functions once you have configured any or all of the notification methods.
RAIDWatch User’s Manual 4.3.1 Root Agent Settings The Root Agent Setting option is shown in Figure 4-16. Figure 4-16: Root Agent Setting • Administrator Password: This allows you to set an administrator’s password. This is the port number the RAIDWatch centralized manager station will use to communicate with the Root Agent. The default for Administrator is “root.” There is no default password for login as Guest.
Chapter 4: Configuration Client Options Figure 4-17: Agent List under Root Agent Setting Right-click on the Current Value section Figure 4-18: Agent List Right-click Menu Step 3. Enter the IP address of the array you wish the Root Agent to manage. Click OK to complete the process. An example is shown in Figure 4-19. Figure 4-19: Adding RAID Agent IP 4.3.3 Root Agent Log Settings Following are the methods used to keep an administrator constantly notified of the status of managed arrays.
RAIDWatch User’s Manual Step 2. Set an SMTP server address in the SMTP server field so that event log emails can be sent to the administrator. Step 3. Set a valid mail address in the Sender mailbox field and an administrator’s email address in the Recipient Email field. Step 4. The Send period (hour) determines how often an administrator receives event log notifications. Figure 4-20: Root Agent Log Settings 4.3.4 Create Plug-ins with Event Notification 4.3.4.
Chapter 4: Configuration Client Options Step 3. Enter the appropriate data in the Plug-in Description and Plug-in Label fields, and then select an execution file from the Application Program field (if there is more than one). Step 4. Click Create to complete the process. (See Figure 4-21) Figure 4-21: Naming and Associating a Plug-in file Step 5. Select the Plug-in tab from the panel. Click Create Receiver to display an input field dialog box. Step 6.
RAIDWatch User’s Manual 4.4 Event Notification Settings 4.4.1 Configuration Client Notification Methods Configuration Client provides the following methods for sending notifications: SNMP traps, email, LAN broadcast, fax, SMS, and MSN Messenger. Some notification methods, such as the connection to a fax machine, require Windows MAPI support on the servers used as the Configuration Client platform.
Chapter 4: Configuration Client Options Figure 4-24: Selecting the Severity Level 4.4.3 Enabling Notification Functions When all notification settings have been properly configured, remember to enable each notification method by double-clicking the Current Value field in Status row. Set Status to Enable if you want the module to be activated every time the Root Agent is loaded. Please see an example shown in Figure 4-25.
RAIDWatch User’s Manual 4.4.4 SNMP Traps Settings Receiver Side To set a client listening to SNMP traps: Step 1. Open the Module Config page. Use the Module Name pulldown menu to select SNMP trap. Figure 4-27: Selecting SNMP Trap Notification Step 2. To create a new SNMP trap, click the Create button on the top right screen or right-click on the lower half of the configuration screen; the Add SNMP Receiver dialog box will appear.
Chapter 4: Configuration Client Options Step 5. Repeat this process to add more SNMP agents. Sender Side From the Module Config window: Step 1. Find the SNMP settings from the pull-down list. Step 2. Click on the On/Off switch beside the pull-down button to enable SNMP traps notification. Switched ON Switched OFF Step 3. Double-click on the Current Value field of the Status row to enable SNMP traps notification. Step 4. Select the severity level of events to be sent to the receiver station. Step 5.
RAIDWatch User’s Manual Step 2. To create a new email notification, click Create on the top right of the screen or right-click on the lower half of the configuration screen to display the Add Email Recipient dialog box. Right-click on the lower level of Configuration screen Figure 4-31: Adding Email Notification Step 3. An Add Email Recipient dialog box appears. Enter an email address that is able to receive email notification. Figure 4-32: Add Email Recipient Dialog Box Step 4.
Chapter 4: Configuration Client Options Step 5. Enter the mail subject by double-clicking the Current Value field. Step 6. Set your SMTP mail server through which emails will be sent. Step 7. Enter the Account name and Password if your mail server requires these values. SASL is the currently supported mechanism. Step 8. Provide a valid email address as your sender's address. 4.4.6 LAN Broadcast Settings Receiver Side To set a computer to receive broadcast messages: Step 1.
RAIDWatch User’s Manual Figure 4-35: Add Broadcast Receiver Dialog Box Step 4. Select the severity level of events to be sent to the receiver station. Step 5. Repeat this process to add more receivers. NOTE: NETBUES and TCP/IP should be active services on your Centralized Management station for message broadcasting. Sender Side From the Module Config window: Step 1. Find the Broadcast settings from the pull-down list. Step 2.
Chapter 4: Configuration Client Options 4.4.7 Fax Settings In order to use fax notification, a fax modem is required and its parameters must be properly set on the main management station. For NT servers, Widows MAPI services, modem, and fax must be ready and running for the notification methods to work. Receiver Side To set a fax machine to receive event messages: Step 1. Open the Module Configuration page. Use the Module Name pull-down menu to select Fax.
RAIDWatch User’s Manual Figure 4-38: Add FAX Receiver Dialog Box Step 4. Enter the Outside line dial-out number if there is any. Step 5. Enter the Delay Second number. Step 6. Enter the level of Severity of events to be sent via fax. Step 7. Repeat this process to add more receivers. NOTE: The physical connection and fax service with Windows MAPI should be ready before configuring this function. Sender Side From the Module Config window: Step 1. Find the Fax settings from the pull-down list Step 2.
Chapter 4: Configuration Client Options Step 4. Select the severity level of events to be sent to the receiver station. Step 5. The Fax device row shows the fax machine(s) currently available. Check for appropriate setup in the Windows control panel. Step 6. Queue size determines how many events will be accumulated and then sent via a single fax transmission. 4.4.8 MSN Settings Receiver Side To set an MSN messenger address to receive notification messages: Step 1. Open the Module Configuration page.
RAIDWatch User’s Manual Figure 4-41: Add MSN Receive Dialog Box Step 4. Select the severity level of events to be sent to the receiver. Step 5. Repeat this process to add more receivers. Sender Side From the Module Config window: Step 1. Find the MSN settings from the pull-down list. Step 2. Click on the On/Off switch beside the pull-down button to enable MSN notification. Switched ON Switched OFF Step 3. Double-click on the Current Value field of the Status row to enable MSN notification.
Chapter 4: Configuration Client Options ♦ Siemens TC35 ♦ WAVECOM Fast Rack M1206 Please contact Infortrend for the complete list of compatible GSM modems. Receiver Side To set a cell phone to receive notification messages: Step 1. Open the Module Configuration page. Use the Module Name pull-down menu to select SMS Message Service. Figure 4-42: Selecting SMS Notification Step 2.
RAIDWatch User’s Manual Step 5. Repeat this process to add more receivers. Sender Side From the Module Config window: Step 1. Find the SMS settings from the pull-down list. Step 2. Click on the On/Off switch beside the pull-down button to enable SMS notification. Switched ON Switched OFF Step 3. Set Status to Enable if you want the module to be activated every time the Configuration Client is started.
Chapter 4: Configuration Client Options Step 1. Open the Module Configuration page. Use the Module Name pull-down menu to select Auto Discovery option. (See Figure 4-45) Figure 4-45: Auto Discovery Option Step 2. Double-click on the current value under IP scan range row to open the Auto Discovery dialog box. (See Figure 4-46) Figure 4-46: Auto Discovery Dialog Box Step 3. Enter a set of IP range that you want the system to detect in the IP range dialog box.
RAIDWatch User’s Manual Step 7. You may turn on and off this option by double click on current value under Status row (see Figure 4-47) or click on the On/Off switch beside the pull-down button to enable the option. Figure 4-47: Enable/Disable the Auto Discovery NOTE: If you already have the Auto Discovery option turned on, be sure to turn off and then turn on the option for any adjustments that you newly made to take effect.
Chapter 4: Configuration Client Options The Agent List Figure 4-49: The Root Agent List If you like to start using the RAIDWatch manager, please refer to Section 5.2. A Agent List window will automatically show the controllers that were detected by the Auto Discovery option. 4.6 Event Severity Levels RAIDWatch classifies disk array events into three severity levels. Level 1 includes non-critical information events such as initialization of the controller and initiation of the rebuilding process.
RAIDWatch User’s Manual 4.6.2 Level 2 Severity Events (Examples) SCSI Target Select Timeout SCSI Target Phase/Signal Error SCSI Target Unexpected Disconnect SCSI Target Negotiation Error SCSI Target Timed Out SCSI Target Parity Error SCSI Bus Reset Issued SCSI Target Not Ready Error SCSI Target Media Error SCSI Target Hardware Error SCSI Target Unit Attention SCSI Target Unexpected Sense Date SCSI Target Block Reassignment Failure SCSI Target Unexpected Data Over/Underrun Drive SCSI Unrecognized Event 4.
Chapter 4: Configuration Client Options NOTE: The utility does not display events that happened before the utility is started.
RAIDWatch User’s Manual This page is intentionally left blank 4-32 Event Log Icons
Chapter 5 RAIDWatch Icons This chapter introduces icons used in the main configuration access categories: ♦ Navigation Tree Icons – Section 5.1 ♦ Information Icons – Section 5.2 ♦ Maintenance Icons – Section 5.3 ♦ Configuration Icons – Section 5.4 ♦ Event Log Icons – Section 5.5 5.
RAIDWatch User’s Manual Maintenance Logical Drive Physical Drive Task Scheduler Configuration Quick Installation Create Logical Drive Existing Logical Drives Create Logical Volume Existing Logical Volumes Host Channel Host LUN Mapping Configuration Parameters 5-2 Navigation Tree Icons
Chapter 5: RAIDWatch Icons 5.2 Array Information Icons Enclosure View Drive in good condition Drive missing or failed Global Spare Any drive icon showing a color other than black represents a member of a logical drive or a dedicated spare. Black is the default color of a new or used drive. A used drive is a drive that had been used as a member of a logical drive. An empty tray; disk drive not installed This graphic represents a rotation button.
RAIDWatch User’s Manual Tasks Under Process Type of tasks being processed by the subsystem. The Task status window displays icons representing specific configurations. Progress indicator Logical Drive Information A logical drive A partitioned logical drive volume is represented as a color bar that can be split into many segments. Each color segment indicates a partition of a configured array.
Chapter 5: RAIDWatch Icons Fibre Channel Status A Fibre host channel System Information A battery module A RAID controller unit A current sensor A cooling module An enclosure device connected through an I2C bus A power supply An enclosure device connected through SAF-TE (SCSI bus) An enclosure device connected through SES (Fibre link) A drive tray slot A temperature sensor An UPS device A voltage sensor 5.
RAIDWatch User’s Manual Create Logical Drives This window uses the same icons as in the Logical Drive Information window. See Logical Drive Information section. Existing Logical Drives A configured array (logical drive) Create Logical Volume A member of a logical volume, representing a logical drive. Different logical drives are presented using icons of different colors.
Chapter 5: RAIDWatch Icons Host LUN Mapping A logical drive. Different logical drives are presented using icons of different colors. A logical volume A partitioned array volume is represented as a color bar that can be split into many segments. Each color segment indicates a partition of a configured array. Configuration Parameters No icons are used in the window. 5.
RAIDWatch User’s Manual This page is intentionally left blank 5-8 Event Log Icons
Chapter 6 Basic Operations This chapter describes the RAIDWatch screen elements and basic operations. ♦ Starting RAIDWatch Agents – Section 6.1, page 6-3 ♦ Starting RAIDWatch Manager – Section 6.2, page 6-4 6.2.1 Locally or via LAN under Windows 2000/ 2003 Environments 6.2.2 Locally or via LAN under Linux Environments 6.2.3 Locally or via LAN under Solaris Environments 6.2.4 For Remote Management via Web Browser (Any Supported OSes) ♦ Start Using RAIDWatch Manager – Section 6.3, page 6-6 6.3.
RAIDWatch User’s Manual 6.6.3 Logical Drive Information Window 6.6.4 Logical Volume Information Window 6.6.5 Fibre Channel Status Window 6.6.6 System Information Window 6.6.7 Statistics Window ♦ The Maintenance Category – Section 6.7, page 6-19 6.7.1 Logical Drives Maintenance Window 6.7.2 Physical Drives Maintenance Window 6.7.3 Task Schedules Maintenance Window ♦ The Configuration Category – Section 6.8, page 6-23 6.8.1 Quick Installation 6.8.2 Create Logical Drive Window 6.8.
Chapter 6: Basic Operations 6.1 Starting RAIDWatch Agents Once the RAIDWatch software is properly installed, the necessary software agents start automatically each time the host computer is started or reset, e.g., RAID Agents and Root Agents. However, the GUI part of RAIDWatch and the Configuration Client utility need to be manually started.
RAIDWatch User’s Manual 6.2 Starting RAIDWatch Manager The management software interface, RAIDWatch Manager, needs to be started by a network or RAID subsystem manager regardless of which OS is being used. Depending on your setup, you can start RAIDWatch Manager in various ways. For both local and remote management, and under various OSes, starting the program is fairly simple. Please refer to the appropriate sub-sections below for information. 6.2.
Chapter 6: Basic Operations 6.2.2 Locally or via LAN under Linux Environments To startup RAIDWatch manager under Linux environments, follow the steps below: Step 1. After the main program of RAIDWatch manager is installed, the files will be installed on the path: /usr/local/Infortrend Inc/RAID GUI Tools Step 2. To execute RAIDWatch manager, type: ./raidwatch.sh in the terminal screen Step 3. To open configuration client, type: terminal screen 6.2.3 ./configuration.
RAIDWatch User’s Manual 6.3 Start Using RAIDWatch Manager When the RAIDWatch Manager is launched, A RAIDWatch Connection window will first prompt and appear on the screen. (See Figure 6-4) Figure 6-4: RAIDWatch Connection Window On the computer screen, if you don’t see the RAIDWatch Connection window, it can be opened from the RAIDWatch program menu. Click on the System and then select Open Device command, and the RAIDWatch Connection window will prompt up.
Chapter 6: Basic Operations NOTE: If you are not sure of a RAID array’s IP address, you may rely on the Auto Discovery option in the Configuration Client to automatically detect the available RAID arrays that are controlled by root agents. If the Auto Discovery option is enabled, the available RAID array will be shown automatically in the Agent List window that is described in later this section. To use the Auto Discovery option, please refer to Section 4.5: Auto Discovery. Step 2.
RAIDWatch User’s Manual Figure 6-6: Retrieve IP List: IPs Managed by Root Agents Step 2. If you like to add a new root agent, pull-down the Root Agent command menu in the Agent List window and select Add Root Agent. Enter a root agent IP address in the prompt up window. Any RAID systems that are connected to the root agent will be shown in a tree table in the Agent List window. Figure 6-7: Add an Root Agent 6-8 Step 3.
Chapter 6: Basic Operations Discovery. (See Figure 6-8) The new search result will be showing in the Agent List Window. Figure 6-8: Start Auto Discovery Function When the system is executing an auto discovery function, the Auto Discovery option in the System pull-down menu will be temporarily disabled. (See Figure 6-9) Figure 6-9: The system is processing Auto Discovery Function NOTE: Setting up Auto Discovery is shown in Section 4.5: Auto Discovery. 6.3.
RAIDWatch User’s Manual Figure 6-10: Disconnect from a Connected Array Select Logout will close the current management session and return to the Outer Shell window. If you wish to connect to another RAID array, enter its IP address and then click OK to proceed. Click Cancel to close the connection prompt and return to the Outer Shell window. Selecting the Refresh button allows you to re-connect with an array if a RAID system has been temporarily disconnected; e.g.
Chapter 6: Basic Operations RAIDWatch’s main program. Information Default password is “1234.” It is recommended to configure passwords for the first two access levels at the first time you successfully connect to an array. Information users can monitor array status and see event messages.
RAIDWatch User’s Manual 6.5.2 Screen Elements Figure 6-11: GUI Screen Elements The GUI screen can be divided mainly into three (3) separate windows: a tree-structure Navigation Panel, the Information/Configuration window, and the Event Log/Configuration View window at the bottom. Each information or configuration window can also be accessed through the command menus on the upper left corner of the management interface.
Chapter 6: Basic Operations For a summary of commands, see Appendix A, Command Summary. NOTE: Multiple simultaneous RAIDWatch Managers can connect to one RAID subsystem. 6.5.4 Outer Shell Commands The following commands are described in Section 6.5.2 and shown in Figure 6-13. Figure 6-13: Outer Shell Commands ♦ Under System menu, the Open Device command lets you connect to a RAID array. This command triggers the connection prompt. Multiple arrays can be managed each in a separate management window.
RAIDWatch User’s Manual You may click the What’s this? command, move it around the screen, and display related information by a second mouse-click on the screen element you are interested in. 6.5.5 Management Window Commands Figure 6-14: Management Window Commands ♦ The Refresh command sends instructions to the GUI asking to review the connection status. The Logout command under the System menu allows you to disconnect from a controller/subsystem and to end the software session.
Chapter 6: Basic Operations 6.6 The Information Category The Information category allows you to access to information about every aspect of system operation. To access the information category, either select the icon from the navigation tree or go to the Action Command menus and then select Information on the top of the screen. (See Figure 6-15) Figure 6-15: Accessing Information Commands 6.6.
RAIDWatch User’s Manual 6.6.2 Tasks Under Process Window The Tasks Under Process window (shown in Figure 6-17) reminds you of unfinished tasks being processed by a subsystem. The start time and percentage of progress are also displayed on-screen. Figure 6-17: Task Status Window 6.6.3 Logical Drive Information Window The Logical Drive Information window (shown in Figure 6-18) provides the configuration, management, and monitoring functions available in RAIDWatch.
Chapter 6: Basic Operations 6.6.4 Logical Volume Information Window The Logical Volume Information window (shown in Figure 6-19) provides the configuration of a configured volume. The Logical Volume Information window includes three sub-windows: Logical Volume Status, Member Logical Drive(s), and Related Information. Figure 6-19: Logical Volume Information 6.6.
RAIDWatch User’s Manual 6.6.6 System Information Window The System Information window (shown in Figure 6-21) provides key information about the RAID subsystem and the RAID controller unit that powers the subsystem. Enclosure information includes the operating status of power supply, temperature sensors, and cooling fan units. Controller information includes CPU, firmware/boot record version, serial number, CPU and board temperature, voltage, and status of the battery.
Chapter 6: Basic Operations Cache Dirty (%) If you select Cache Dirty (%), a window similar to the one shown in Figure 6-22 will appear. The percentage of the cache block in use is displayed in numbers and the cache hits average is displayed as a graph. The Cache Dirty rate provides cached writes data over the last few minutes and indicates data caching consistency and frequency.
RAIDWatch User’s Manual 6.7.1 Logical Drives Maintenance Window When the Logical Drives maintenance window is opened, the screen shown in Figure 6-24 should appear. Figure 6-24: Maintenance - Logical Drives There are three (3) sub-windows in the Logical Drives maintenance mode window: ♦ The Logical Drives window provides a list of all configured arrays. Use a single mouse-click to select the logical drive you wish to perform maintenance tasks on.
Chapter 6: Basic Operations The system can automatically perform a Media Scan according to a preset task schedule. For more details, please refer to Section 6.7.3. Regenerate Parity - If no verifying method is applied to data writes, this function can often be performed to verify parity blocks of a selected array. This function compares and recalculates parity data to correct parity errors. NOTE: The function is available for logical drive that is configured to RAID level 1, 3, 5 and 6.
RAIDWatch User’s Manual Media Scan – You can set up media scan action to a specific physical drive. To start a media scan, select a drive from the Front View window then set all options in the Functions window and click Apply button. Maintain Spare - You can add a spare drive from the list of the unused drives. The spare chosen here can be selected as global or local spare drive. If you choose to create a local spare drive, enter a logical drive ID in the next page.
Chapter 6: Basic Operations Front View window and then set the conditions in the Functions window. Click Apply to start the action. 6.7.3 Task Schedules Maintenance Window When the Physical Drives maintenance window is opened, the screen shown in Figure 6-26 should appear. Figure 6-26: Task Schedules Window To begin using the Task Schedule functionality, right-click to display the Add New Schedule Task command.
RAIDWatch User’s Manual Figure 6-27: Accessing Configuration Commands 6.8.1 Quick Installation This is a new function in RAIDWatch 2.2 or above version. When you first connect RAIDWatch to a new RAID system without any previous configurations, select Quick Installation and let RAIDWatch guide you thought a simple logical drive creation process. Later, the RAIDWatch program will lead you to a LUN mapping process.
Chapter 6: Basic Operations ♦ A selected physical drive is highlighted by bright blue lines; a second mouse-click on it deselects the drive. Figure 6-28: Selecting Members for a New Logical Drive For detail of creating a logical drive, please refer to Chapter 9 of this document. 6.8.3 Existing Logical Drives Window When the Existing Logical Drives window is opened, the screen shown in Figure 6-29 should appear.
RAIDWatch User’s Manual Figure 6-29: Existing Logical Drives Window 6.8.4 Create Logical Volume Window This window uses the same operation flow as that applied in the Create Logical Drive window. 6.8.5 Existing Logical Volumes Window This window uses the same operation flow as that applied in the Existing Logical Volumes window. NOTE: This window also contains Edit mode commands that are only accessible by a mouse right-click. 6.8.
Chapter 6: Basic Operations Figure 6-30: Channel Window On the Parameters page, channel mode, current data rate, default data rate and current transfer width are displayed. Channel Mode: Only applicable on the EonRAID 2510FS series. This option allows you to change the I/O channel operating mode. The channel mode selections can be: host, drive, RCC, drive +RCC. Default Data Rate: Should only be applied with limitations on current configuration, e.g.
RAIDWatch User’s Manual 6.8.7 Host LUN Mapping Window The Host LUN Mapping window allows you to associate configured arrays with host channel IDs or LUN numbers. This window allows you to create LUN masking entries with host LUN mapping when access control over a Fibre Channel network is necessary. ♦ The Host LUN Mapping window contains four sub-windows: Host LUN(s), WWN Names(s), and Logical Drive(s) or Volume(s).
Chapter 6: Basic Operations window(s) on your screen. You may also select each connected system by clicking the listed systems at the bottom of the Window menu. Figure 6-33: The “Outer Shell” System View Window The window menu includes the following commands: ♦ Next Window: The Next Window command change which window is active. The active window is raised to the top of the screen. If you connect more than one RAID system, this command allows you to switch between different system view windows.
RAIDWatch User’s Manual 6.10 Multi-array Management Figure 6-34: Opening Device for Multi-Array Management Management of multiple arrays is allowed by clicking the Open Device command under the System menu. The Exit command ends the RAIDWatch manager session with all configured arrays. Clicking the Open Device command and the connection wizard is followed. Multiple management windows can be opened.
Chapter 7 Configuration Parameters RAIDWatch Manager enables you to modify the configuration of the disk array controller from your manager console. This chapter describes the following configuration features: ♦ Accessing Configuration Parameters Options - Section 7.1 on page 7-2 ♦ Communications – Section 7.2 on page 7-3 ♦ Controller – Section 7.3 on page 7-4 ♦ System – Section 7.4 on page 7-6 ♦ Password – Section 7.5 on page 7-8 ♦ Threshold – Section 7.
RAIDWatch User’s Manual 7.1 Accessing Configuration Parameters Options To access controller configuration options, either use the Configuration category icons on the Navigation Tree or select the Configuration Parameters command from the command menu to open the Configuration Parameters. The configuration window contains many options that are directly related to array performance, and should be configured before creating logical arrays.
Chapter 7: Configuration Parameters 7.2 Communications To configure the Communication options, select the Communication page, as shown in Figure 7-2, from the Configuration Parameters window. Figure 7-2: The Communication Page RS-232C Port Infortrend RAID subsystems/controllers come with one or two serial ports. Before proceeding with configuration, first select COM1 or COM2 by a single mouse click. ♦ Terminal emulation allows you to enable or disable the terminal emulation option.
RAIDWatch User’s Manual 7.3 Controller “Controller” here refers to the RAID controller unit, which is the main processing unit of a RAID subsystem. The configuration window contains two sub-windows: “Caching” and “Controller Parameters.” To configure the controller’s caching behaviors, select an appropriate value from each of the pull-down menus, as shown in Figure 7-3.
Chapter 7: Configuration Parameters fails, the subsystem firmware automatically switches caching mode to the conservative Write-through. ♦ Optimization Policy Optimization for Random I/O. More common setting. Use this option for environments (e.g., database maintenance) with smaller I/O transactions. Optimization for Sequential I/O. Used for large I/O environments such as video recording and editing. Particularly useful where I/O read/write must be in sequential order. ♦ Sync.
RAIDWatch User’s Manual If the DIMM module installed for data caching supports ECC, you may select to enable or disable the error check function here. When preferences have been set with the configurations above, click Apply to make the changes. 7.4 System To access the System-specific functions, select the System page, as shown in Figure 7-4, from the Configuration Parameters window. Figure 7-4: The System Page Each function is executed by a two-step procedure.
Chapter 7: Configuration Parameters ♦ Shutdown Controller. This prepares the subsystem to be powered off. This function flushes the unfinished writes still cached in controller memory making it safe to turn off the subsystem. ♦ Restore Factory Default. When you apply this function, any settings that you have made in RAIDWatch program will be formated and the original factory default configuration will be restored.
RAIDWatch User’s Manual We strongly recommend using this function to save the configuration profile whenever a configuration change is made. ♦ Save NVRAM to Disk: The configuration profile can also be saved to array hard drives. Each array hard drive will have a replica of the NVRAM backup in its reserved space so that when a drive fails or is being regrouped, the backup remains intact.
Chapter 7: Configuration Parameters Figure 7-6: The Password Page Maintenance Password Users logging in using the Maintainance Password will be able to access the first two configuration categories, Information and Maintenance. You may set the Maintenace Password here and click OK for the change to take effect. Configuration Password Users logging in using the Configuration Password have full access to all configuration options.
RAIDWatch User’s Manual Figure 7-7: The Threshold Page To change the threshold values on a specific monitored item, for example, the CPU Temp Sensor, right-click on the item. The Configuration button will prompt. (See Figure 7-7) Left-click on the Configuration button to bring up the Configuration prompt window. (See Figure 7-8) Figure 7-8: The Threshold Configuration Prompt Window WARNING! The upper or lower thresholds can also be disabled by entering “-1” in the threshold field.
Chapter 7: Configuration Parameters Click Default to restore the default values for both thresholds. Click Cancel to cancel this action and go back to the Threshold page in Configuration Parameter window. 7.7 Redundant Controller Settings This sub-window contains configuration options related to redundant controller configurations. (See Figure 7-9) This Redundant page only displays if your controller/subsystem comes with dual-redundant RAID controllers.
RAIDWatch User’s Manual that if one of the controllers fails, the surviving controller can finish the writes. If controllers are operating using the Write-Through caching mode, the Periodic Cache Flush Time can be manually disabled to save system resources and achieve better performance. NOTE: If periodic cache flush is disabled, the configuration changes made through the Primary controller is still communicated to the Secondary controller.
Chapter 7: Configuration Parameters 7.8 Event Triggered Operations Figure 7-10: The Trigger Page To reduce the chance of data loss caused by hardware failure, the controller/subsystem can automatically commence an auto cache flush upon the detection of the following conditions. When cache contents are forced to be distributed to hard drives the Write-Back caching mode is also switched to the Write-Through mode. 1. Controller Failure 2. BBU Lower or Failure 3. UPS Auxiliary Power Loss 4.
RAIDWatch User’s Manual 7.9 Host-side, Drive-side, and Disk Array Parameters I/O channel host-side, drive-side, and rebuild priority options are included in its specific sub-window. To configure these configuration options, select each configuration page, as shown in Figure 7-11, from the Configuration Parameters window. Figure 7-11: The Host-side Parameters Page Each option is executed by a two-step procedure.
Chapter 7: Configuration Parameters Drive-side Parameters Disk Access Delay Time (Sec): Sets the delay time before the subsystem tries to access the hard drives after power-on. Default is 15 seconds. Drive Check Period (Sec): This is the time interval for the controller to check all disk drives that were on the drive buses at controller startup. The default value is “Disabled.
RAIDWatch User’s Manual function to decide at what interval the subsystem will check the status of these devices. Drive Fail Swap Check Period (Sec): The subsystem scans drive buses at this interval to check if a failed drive has been replaced. Maximum Tag Count: The subsystem supports tag command queuing with an adjustable maximum tag count from 1 to 128. The default setting is “Enabled” with a maximum tag count of 32.
Chapter 7: Configuration Parameters Peripheral Device Type / Peripheral Device Qualifier / Device Supports Removable Media / LUN applicability: If no logical drive has been created and mapped to a host LUN, and the RAID controller is the only device connected to the host SCSI card, usually the operating system will not load the driver for the host adapter. If the driver is not loaded, the host computer will not be able to use the inband utility to communicate with the RAID controller.
RAIDWatch User’s Manual Scanner Device 6 MO Device 7 Storage Array Controller Device 0xC Enclosure Services Device 0xD Unknown Device 0x1f Table 7-2: Peripheral Device Type Settings Cylinder/Head/Sector: Drive capacity is decided by the number of blocks. For some operating systems (Sun Solaris, for example) the capacity of a drive is determined by the cylinder/head/sector count.
Chapter 7: Configuration Parameters Both One-way and Two-way (Mutual) CHAP approaches are available through the “iSCSI Initiator” menu under the “Host LUN mapping” window. NOTE: The CHAP configuration option here enables CHAP configuration menu in the host LUN mapping window. Unlike previous RAIDWatch and firmware revisions, controller name and password are no longer used for CHAP authentication. Figure 7-12: The Other Page for iSCSI Models Jumbo Frames: Jumbo Frames, as specified by the IEEE 802.
RAIDWatch User’s Manual Disk-Array Parameters Figure 7-13: The Disk Array Parameters Rebuild Priority: The rebuild priority determines how much of the system resources are applied when rebuilding a logical drive. Available options are Low, Normal, Improved, and High. The higher priority takes up more system resources and the rebuild process completes more rapidly. However, I/O performance in the meantime is inevitably lower due to the resources consumed.
Chapter 7: Configuration Parameters Maximum Drive Response Timeout (ms): The main purpose for having a maximum response time on hard drives is to ensure delays caused by media errors or drive erratic behaviors do not result in host I/O timeouts. Doing so can avoid the unnecessary efforts dealing with delays especially when drives showing problems are often the failing drives. Below are some operation limitations: • • • Battery shall be present and functioning properly. Write-Back policy is enabled.
RAIDWatch User’s Manual 3. Enhance performance using LMDD test in the sequential reads. 4. The Synchronized Cache Communications between RAID controllers is disabled. NOTE: Some parameters related to AV Optimization will be implemented as system defaults in the append file for specific ODM/OEM models.
Chapter 8 Channel Configuration Using RAIDWatch Manager, you can modify the configuration of any channel on the controller. With RAID controllers such as the EonRAID 2510FS, you can set the channel operation mode to host or drive, enable or disable channel termination, set IDs, set the transfer clock rate for synchronous communications, and select the transfer width. Channel configuration settings are available under Physical View in the RAID View window.
RAIDWatch User’s Manual 8.1 Channel Configuration Window I/O Channel configuration options are available under the Configuration category, which is found in the lower section of the navigation panel. To access the Channel window, use either the command from the Action menu or select the Channel icon from the navigation panel. (See Figure 8-1).
Chapter 8: Channel Configuration Figure 8-2: Selecting a Channel: Fibre Host The following sections describe user-configurable channel parameters. 8.2 User-Configurable Channel Parameters Once the channel has been selected, the screen shown in Figure 8-3 will appear in the content window. The different options are discussed below. NOTE: A SCSI host channel is shown in Figure 8-3.
RAIDWatch User’s Manual Channel Parameters: EonRAID 2510FS Series Figure 8-4: Selecting a Drive Channel: EonRAID 2510FS 8.2.1. Channel Mode This configuration option is exclusively available with the EonRAID 2510FS series. The EonRAID series controller allows flexible reconfigurations of its I/O channels. An I/O channel can be assigned as Host, Drive, dedicated RCC (RCCOM), or Drive+RCCOM channels.
Chapter 8: Channel Configuration 8.2.2. Termination This parameter enables or disables channel SCSI termination on subsystems featuring SCSI host channels. SCSI buses must be properly terminated at both ends; that is, when connecting one end of a SCSI cable to a host HBA, the termination of the channel must be enabled on the subsystem side. An alternate configuration should be applied when multiple enclosures are being cascaded on the host buses.
RAIDWatch User’s Manual Furthermore, certain older SCSI devices may only support narrow transfer and behave abnormally when attempting to negotiate wide transfer. Under such conditions, wide transfer may need to be disabled, forcing the controller to use narrow transfer mode with that device. IMPORTANT! Every time you change the transfer speed, you must reset the controller for the changes to take effect. 8.2.4.
Chapter 8: Channel Configuration Figure 8-5: ID Pool Menu When selecting an ID, be sure that it does not conflict with the other devices on the channel. Preset IDs should have been grayed out and excluded from selection. The ID pool lists all available IDs for the current selection. Highlight the IDs you want to use by selecting their check boxes and click Apply to create either the PIDs (Primary ID) or SIDs (Secondary ID) for the channel.
RAIDWatch User’s Manual This page is intentionally left blank 8-8 Setting the Configurations for a Channel
Chapter 9 Drive Management This chapter focuses on how to create or delete Logical Drives (LDs) and Logical Volumes (LVs). Both LDs and LVs can be partitioned. This chapter describes the following drive management features: ♦ Locating Drives – Section 9.1, page 9-3 ♦ Logical Drive Management – Section 9.2, page 9-3 9.2.1 Accessing the Create Logical Drive Window 9.2.2 Creating Logical Drives • 9.2.2.1 LD Creation • 9.2.2.2 Selecting Drives • 9.2.2.3 Setting RAID Parameters • 9.2.2.
RAIDWatch User’s Manual 9.2.6 Rebuilding Logical Drives 9.2.7 Deleting an LD ♦ Logical Volume Management – Section 9.3, page 9-18 9.3.1 Accessing the Create Logical Volume Window 9.3.2 Creating Logical Volumes • 9.3.2.1 LV Creation • 9.3.2.2 Selecting LDs • 9.3.2.3 Setting LV Parameters • 9.3.2.4 Click OK to Create 9.3.3 Accessing the Existing Logical Volume • 9.3.3.1 Modifying LV Configurations • 9.3.2.2 Expanding a Logical V • 9.3.3.3 Accessing the Expand LV Command Page 9.3.
Chapter 9: Drive Management 9.1. Locating Drives RAIDWatch uses icons to represent subsystem drive trays. In many configuration windows, a single click on a drive tray icon selects a hard drive. Drive status is indicated and automatically refreshed by displaying different icons. The drive tray icons used in the Front View window to instantly display drive status are shown below. By referring to the drive status in the Front View window, you can start to create or configure a logical array.
RAIDWatch User’s Manual NOTE: When you delete a logical drive, all physical drives assigned to the logical drive will be released, making them available for creation or expansion of logical drives. 9.2.1 Accessing the Create Logical Drive Window LDs are created in the Create Logical Drive window and managed in the Existing Logical Drives window. These functional windows are accessed from the command from the Action menu or RAIDWatch’s navigation panel on the left of the GUI screen. Step 1.
Chapter 9: Drive Management Figure 9-2: The Create Logical Drive Window 9.2.2 Creating Logical Drives 9.2.2.1. LD Creation To create a logical drive: Step 1. Select the physical drives that will be used in the LD. (See Section 9.2.2.2) Step 2. Select the following RAID parameters. (See Section 9.2.2.3) ♦ Drive Size ♦ Stripe Size ♦ Initialization Mode ♦ RAID Level ♦ Write Policy Step 3. Click the OK button. (See Section 9.2.2.4) 9.2.2.2. Selecting Drives Step 1.
RAIDWatch User’s Manual 9.2.2.3. Setting RAID Parameters After the physical drives that will be used in the LD have been selected, the RAID parameters for the LD must be selected. Available RAID parameter options can be accessed at the bottom of the configuration screen. Drive Size The value entered in the Drive Size field determines how much capacity from each drive will be used in the logical drive. NOTE: Enter a smaller number if you do not want to use up all of the capacity at this time.
Chapter 9: Drive Management 9.2.2.4. Click OK to Create LD Once the physical drives that will be used in the LD have been selected and all the desired LD parameters have been selected: Step 1. Click OK at the bottom of the LD management window. Step 2. A confirmation window will appear. If you are certain that you want to create the LD with the settings you have selected, click OK. Step 4.
RAIDWatch User’s Manual Figure 9-4: List of LDs From the list shown in Figure 9-4, select the LD for which you wish to change its characteristics or configure. Once this LD has been selected, its members will appear in the Front View sub-window. At the top of the Functions window, three tabs (Properties, Add Disk and Expand) will appear. 9.2.3.1. Modifying LD Configurations After the LD is created, some configurations can be modified in the Properties command page.
Chapter 9: Drive Management 9.2.3.2. Expanding LD by Adding Disks To access the Add Disk command page, select a logical drive and click on the Add Disk tab under Functions window. Figure 9-6: The Add Drive Command Sub-window Step 1. Select the logical drive you wish to expand from the LD list on top of the GUI screen. Step 2. Select the Add Disk tab to display the content panel. Step 3. Select one or more drives you wish to add to the logical drive by single mouse-click from the Front View window.
RAIDWatch User’s Manual Figure 9-7: The Expand Command Sub-window Available Expand Size (MB) If there is an amount of unused capacity in a logical drive, the LD may be expanded. If there is no amount present in the text box, then the LD cannot be expanded. Set Expansion Size A value can be entered in this text box if and only if an amount is shown in the Available Expand Size text box. The value entered into the Expansion Size text box cannot exceed the amount shown above.
Chapter 9: Drive Management 9.2.3.5. Accessing the Migrate LD Command page To access the Migration LD command page, first select a logical drive on the top of the screen and then click on the Migrate Logical Drives tab under Functions window. (See Figure 9-8) NOTE: Only RAID level 5 and 6 support the migration option currently. This function is disabled when a LD is configured as other RAID levels. This function is only applicable on RAID subsystems running Firmware 3.47 or above version.
RAIDWatch User’s Manual WARNING! 1. Different RAID configurations use different sizes of disk space to store parity or mirrored data. When migrating from one to another, disk space might not be enough to hold the original data. So the total drive spaces of new RAID level must not less than original RAID level. 2. To avoid possible problems with OS partition table, a logical drive’s LUN mappings must be deleted before migration.
Chapter 9: Drive Management 9.2.4 Dynamic Logical Drive Expansion 9.2.4.1. What Is It and How Does It Work? Before Dynamic Logical Drive Expansion, increasing the capacity of a RAID system using traditional methods meant backing up, re-creating, and then restoring data. Dynamic Logical Drive Expansion allows you to add new hard disk drives and expand a RAID level 0, 3, 5 or 6 logical drive without powering down the system. 9.2.4.2.
RAIDWatch User’s Manual Mode 2 Expansion, on the other hand, requires the same number of higher-capacity hard disk drives for a given logical drive. Figure 9-10: RAID Expansion Mode 2 (1/3) Figure 9-10 above illustrates expansion of the same 4GB RAID 5 logical drive using Mode 2 Expansion. Drives are copied and replaced, one by one, onto three higher-capacity drives.
Chapter 9: Drive Management RAID Expansion - Mode 2 (3/3) RAID 5 (8GB) n partitions 3 Partition n+1 4 GB 4 GB 4 GB RAID Expansion or RAID 5 (8GB) RAID 5 (4GB) After the RAID Expansion, the additional capacity will appear as another partition. Adding the extra capacity into the existing partition requires OS support. In use Unused Figure 9-12: RAID Expansion Mode 2 (3/3) IMPORTANT! The increased capacity from either expansion type will be listed as a new partition.
RAIDWatch User’s Manual NOTE: Adding a spare drive can be done automatically by selecting the RAID 1+Spare, RAID 3+Spare, RAID 5+Spare or RAID 6+Spare option from the logical drive RAID Level selection dialog box when creating a logical drive. These options apply to RAID 1, RAID 3, RAID 5 and RAID 6 levels respectively. 9.2.5.1. Accessing the Spare Drive Management Screen To open the Spare Drive Management screen, please follow these steps: Step 1.
Chapter 9: Drive Management NOTE: An Enclosure Spare is one that is used to rebuild all logical drives within the same enclosure. In configurations that span across multiple enclosures, a Global spare may participate in the rebuild of a failed drive that resides in a different enclosure. Using Enclosure Spare can avoid disorderly locations of member disk drives if members reside in different enclosures. 9.2.
RAIDWatch User’s Manual the LD being deleted and any data that was previously stored on the LD will be irretrievable. IMPORTANT! Deleting a logical drive irretrievably wipes all data currently stored on the logical drive. Step 1. Select the logical drive you wish to remove with a single mouseclick. Right-click on the adjacent screen area. A command menu will prompt as shown in Figure 9-15. Figure 9-15: Displaying the Logical Drive Command Menu Step 2. Select the Delete Logical Drive command.
Chapter 9: Drive Management NOTE: When you delete a logical volume, all logical drives assigned to it will be released, making them available for new logical volume creation. 9.3.1 Accessing the Create Logical Volume Window LVs are created in the Create Logical View window, which can be accessed either from the navigation panel icon or the command menu on top of the screen. Step 1.
RAIDWatch User’s Manual Figure 9-17: The Create Logical Volume Window 9.3.2 Creating Logical Volumes 9.3.2.1. LV Creation Step 1. Select the LDs that will be used in the LV from the Logical Drives Available panel. Step 2. Select the following RAID parameters: ♦ Write Policy ♦ Assignment Step 3. Information about the selected LDs will appear on the Selected Members panel. Click the OK button. 9.3.2.2. Selecting LDs Step 1.
Chapter 9: Drive Management NOTE: If the redundant controller function has not been enabled or the SIDs are not assigned on drive channels, the LD Assignment pull-down menu will not be available. Select Write Policy Use the Write Policy menu to select Default (Global Setting), Write Through, or Write Back. The same policy will automatically apply to all logical drives (members) included in the logical volume. NOTE: The Default option should be considered as “Not-Specified.
RAIDWatch User’s Manual Figure 9-18: Accessing Existing Logical Volume Window 9.3.3.1. Modifying LV Configurations After the LV is created, some configurations can be modified in the Properties command page. To access the page, select a LV and click on the Properties tab under Functions window. Figure 9-19: Properties command page under Functions window Each option is executed by a two-step procedure.
Chapter 9: Drive Management Write Policy: Write policy can be adjusted on a per logical volume basis. This option allows you to set a write policy for the specific logical volume you selected. “Default” is a neutral value that is coordinated with the controller’s caching mode setting. Other choices are “Write-back” and “Write-through.” 9.3.3.2. Expanding a Logical Volume When members of a logical volume have free and unused capacity, the additional capacity can be added to existing logical volumes.
RAIDWatch User’s Manual Figure 9-21: Logical Volume Parameters Step 3. Available expansion size displays in a text box if there is any amount of unused capacity. Step 4. Click the Expand button at the bottom of the configuration panel. The expand process should be completed in a short while because all unused capacity in the members of a logical volume must be made useful by the same expansion process.
Chapter 9: Drive Management Figure 9-22: Displaying Logical Volume Edit Mode Menu Step 2. You will be asked to confirm that you wish to delete the selected LV. If you are certain that you want to delete the LV then select OK. The logical volume will be deleted and removed from the logical volumes list. 9.4. Partitioning a Logical Configuration 9.4.1 Overview Partitions can be created in both logical drives (LD) and logical volumes (LV).
RAIDWatch User’s Manual 9.4.2 Partitioning a Logical Drive WARNING! Partitioning a configured array destroys the data already stored on it. Partitioning is recommended during the initial setup of your subsystem. You have to move your data elsewhere if you want to partition a configured array. Step 1. Select the logical drive you want to partition. Move your cursor to the Logical Drives window. Right-click to display the Edit Partition command menu. Figure 9-23: The Edit Partition Command Step 2.
Chapter 9: Drive Management Step 6. The Partition Size window displays. Enter the desired capacity and press OK to proceed. Figure 9-25: The Partition Size Window Step 7. Shown below is a capacity partitioned into two. Each partition is displayed in a different color. Repeat the above process to create more partitions or click to view its information. A new partition is created from the existing partition.
RAIDWatch User’s Manual Step 2. Select Edit Partition from the menu. Step 3. The Edit Partition mode window displays as shown below. Figure 9-28: The Edit Partition Window Step 4. If the volume has not been partitioned, all of its capacity appears as one single partition. Single-click to select the partition (the color bar). Step 5. Right-click or select the Edit command to display the Add Partition command. Click to proceed. Step 6. The Partition Size window displays.
Chapter 9: Drive Management 9.5. Physical Drive Maintenance 9.5.1 Read/Write Test Figure 9-31: The Physical Drive Maintenance Window Step1. To access the Read/Write Test maintenance option, select the Physical Drives icon from the functional navigation panel on the left of the RAIDWatch screen. Step 2. Select a new drive from the Front View window.
RAIDWatch User’s Manual Recovery Process: Firmware might attempt to correct some of the errors discovered on drives. The configurable options are: No Recovery, Marking Bad Block, Auto Reassignment, and Attempting Reassign First. If selected, the last option will attempt to reassign bad blocks, and if the reassignment fails, mark those drive sectors as BAD.
Chapter 10 LUN Mapping After creating a logical drive (LD) or logical volume (LV), you can map it as is to a host LUN; or, if partitions are set, you can map each partition to a specific host LUN. RAIDWatch supports eight LUNs per host channel (numbered 0 - 7), each of which appears as a single drive letter to the host if mapped to an LD, LV, or a partition of either. Existing host LUN mappings can also be deleted.
RAIDWatch User’s Manual 10.1.Accessing the LUN Map Table When you want to either create or delete a LUN mapping or an extended LUN mapping, it is necessary to access the LUN Map Table. The LUN Map Table lists the LDs, LVs and partitions that have previously been mapped. To access the LUN Map Table, please follow these steps: Step 1. In the navigation panel under the Configuration category, click on the Host LUN Mapping where you can find the configuration options with the mapping operation.
Chapter 10: LUN Mapping Figure 10-2: Selecting the Host Channel ID Number Step 3. After selecting the ID, the LUN Map Setting window appears as shown in Figure 10-3. Figure 10-3: LUN Map Setting Window 10.2.LUN Mapping 10.2.1. Mapping a Complete LD or LV Step 1. If you want to map a complete LD or LV, make sure that the LD or LV has not been partitioned. Step 2. Follow the steps listed in Section 10.1 above to access the Host LUN Mapping window shown in Figure 10-3. Step 3.
RAIDWatch User’s Manual appears on the right-hand side of the screen. An LD or LV that has not been partitioned should have only one partition. Step 5. Click on the Map LUN button to complete the process. (See Figure 10-4) Figure 10-4: LUN Map Setting Window: Single Partition 10.2.2. Map a Logical Drive or Volume Partition to a Host LUN Step 1. First, partition the logical drive or logical volume. Step 2. Follow the steps listed in Section 10.
Chapter 10: LUN Mapping 10.2.3. Deleting a Host LUN Mapping Step 1. Follow the steps listed in Section 10.1 above to access the LUN Map Setting window shown in Figure 10-2. Step 2. Left-click on a configured LUN and then right-click on the adjacent area. A command menu displays as shown in Figure 10-6. Select Remove LUN Map to complete the process. Figure 10-6: Delete LUN Command Step 3. When prompted for a password or an answer, enter it and click OK.
RAIDWatch User’s Manual Figure 10-7: Host LUN Mapping Window (iSCSI Models) Step 1. To access the iSCSI initiator settings menu, right-click on the iSCSI Initiator column to bring out the configuration menu (shown above and below). Figure 10-8: iSCSI Initiator Menu Step 2. Follow the details in the table below and enter appropriate information and values to establish access control.
Chapter 10: LUN Mapping In here you can manually enter an initiator’s IQN (iSCSI Qualified Name); - or – Host IQN Select from the list of connected initiators by clicking on the pull-down button to display the currently connected initiators. The user name here applies to a one-way CHAP configuration. Identical name and password must be configured on the initiator software or HBA configuration utility.
RAIDWatch User’s Manual 2. Microsoft iSCSI initiator uses IQN as the default User name for CHAP setting. A different User name can be specified here instead of the default. 3. For more information on CHAP-related settings, please refer to the documentation that came with your initiator hardware or software drivers.
Chapter 11 System Monitoring and Management ♦ RAID Information – Section 11.1, page 11-2 11.1.1 The Information Category 11.1.2 Date and Time 11.1.3 Enclosure View 11.1.4 Task Under Process 11.1.5 Event Log List/Configuration List Window ♦ Logical Drive Information – Section 11.2, Page 11-8 11.2.1 Accessing Logical Drive Information ♦ Logical Volume Information – Section 11.3, page 11-10 11.3.1 Accessing Logical Volume Information 11-1 ♦ Fibre Channel Status – Section 11.
RAIDWatch User’s Manual 11.1 RAID Information Unlike its predecessor, RAIDWatch presents access to all information services under one Array Status category. Users logged in using the Information authorization will be allowed to access the information windows while being excluded from other configuration options. Support for device monitoring via SAF-TE, SES, and I2C data buses is the same.
Chapter 11: System Monitoring and Management The Array Information category provides access to seven display windows as listed below: Icon Description Icon for the Array Information category Opens the Enclosure View window Displays the Configuration Tasks currently being processed by the subsystem Opens the Logical Drive information window Opens the Logical Volume information window Opens the Fibre Channel Status window Opens the System View window Opens the Statistics window Table 11-1: Array Information
RAIDWatch User’s Manual 11.1.3 Enclosure View The Enclosure View window displays both the front and the rear views of connected enclosures. For the EonStor subsystems, RAIDWatch displays drive trays in the front view, and system modules (power supplies, cooling modules, etc.) in the rear view. For the EonRAID controllers, RAIDWatch displays FC port modules and LEDs in the front view; powers supplies, cooling modules, and controller modules display in the rear view.
Chapter 11: System Monitoring and Management 11.1.4 Task Under Process Access the Task Under Process window by clicking on the display icon in the RAIDWatch navigation panel. Figure 11-4: Tasks Currently Being Processed 11.1.5 ♦ This window shows the unfinished tasks currently being processed by the subsystem.
RAIDWatch User’s Manual Event Log List Window The Event Log List window generates the system’s event log list at the bottom of the RAIDWatch screen. The Event Log window gives users the real-time monitoring, alerting as well as status reporting of the RAID systems. When a new event is generated, the icon under Severity column will flash to draw user’s attention. The severity icons also indicate the severity level of an event.
Chapter 11: System Monitoring and Management Figure 11-6: Event View Option Window In the Event View Option window, the tabbed panel on the top of the window allow you to switch between the Filter and Column pages. You may set the event sorting criteria, the type of events you like to export, the severity of the event and the time occurrence range in the Filter page of the Event View Option window. The Column page allows you to select the related display items when showing the events.
RAIDWatch User’s Manual setting(s), host LUN list, drive-side parameters, caching parameters, and communication information. Figure 11-7: Configuration List Window Right-click on the Configuration List window will allow you to select four (4) options and they are explained as follow: Export Configuration Data as Text File: When you select this option, the program will save the system’s configuration data to a text file. You may select a file destination in a prompt up Save window.
Chapter 11: System Monitoring and Management drive (RAID) configuration of disk drives cannot afford two failed disk drives. ♦ A logical drive may include members that reside on different enclosures or different drive channels. Doing so can help reduce the chance of downtime if a hardware failure should occur.
RAIDWatch User’s Manual 11.3 Logical Volume Information A logical volume consists of one or many logical drives. Data written onto the logical volume is striped across the members. 11.3.1 Accessing Logical Volume Information Step 1. To access the Logical Volume Information, single-click its display icon on the navigation panel or select the command from the Action command menu. After opening the information window, select a logical volume by single mouse-click.
Chapter 11: System Monitoring and Management 11.4 Fibre Channel Status This window is automatically grayed out on subsystems featuring SCSI or iSCSI host channels. The Fibre Channel Status window displays information such as WWN port name and node name. This information is necessary in storage applications managed by SAN management software or failover drivers. Step 1.
RAIDWatch User’s Manual Figure 11-11: System Information Window Step 1. To access the window, click on the System Information icon on the GUI navigation panel or select the command from the Action command menu. Step 2. Carefully check the display icons in front of the Device Name. Devices are categorized by the data bus by which they are connected.
Chapter 11: System Monitoring and Management Component status is constantly refreshed, yet the refresh time depends on the value set for device bus polling intervals, e.g., polling period set for SAF-TE or SES devices. The EonStor subsystem series supports auto-polling of cascaded enclosures, meaning the status of a connected enclosure is automatically added to the System Information window without the user’s intervention. 11.
RAIDWatch User’s Manual This page is intentionally left blank Statistics 11-14
Chapter 12 Enclosure Display This chapter introduces the enclosure display using the Enclosure View window in the RAIDWatch’s main program. ♦ About The Enclosure View – Section 12.1, page 12-2 ♦ Accessing the Enclosure View – Section 12.3, page 12-4 12.2.1 Connecting to the RAID Agent 12.2.2 Opening the Enclosure View Window 12.2.3 Component Information Enclosure Display ♦ LED Representations – Section 12.3, page 12-4 ♦ Enclosure View Messages – Section 12.
RAIDWatch User’s Manual 12.1 About The Enclosure View Window The RAIDWatch Enclosure View is a customized display that shows a visual representation of the physical RAID controller/subsystem components. The Enclosure View allows you to quickly determine the operational status of critical RAID components. The Enclosure View window shows both the front and rear panel (e.g., the EonRAID 2510FS controller head series, see Figure 12-1).
Chapter 12: Enclosure Display Action Command menus and then select Information/Enclosure View on the top of the screen. (See Figure 12-3) Figure 12-3: Accessing the Enclosure View 12.2.3 Component Information The front and rear views of a RAID subsystem in the Enclosure View window are the exact representations of physical components. This window is particularly useful in monitoring the status of the physical drives.
RAIDWatch User’s Manual 12.3 LED Representations As described earlier (see Section 12.1), the Enclosure View is a direct representation of the physical devices. Almost every major component has its status-indicating LEDs. When a component fails (or some other event occurs), the related LEDs will flash or change the display color. The physical status of the LEDs will be reflected by the LEDs shown in the Enclosure View window.
Chapter 12: Enclosure Display Figure 12-5: Service LED lights up After servicing the subsystem, the administrator should turn off this service LED by manually pressing the service button on the chassis or remotely using the RAIDWatch management software. 12.4 Enclosure View Messages The messages shown in the Enclosure View window provide easy access to information about components of a RAID enclosure that is being monitored. The message tag reports the status of major devices.
RAIDWatch User’s Manual which the drives are connected, the drive’s capacity, transfer rate, and current status. The enclosure components function as a summary of module operating status. The operating status of each module is shown either as operating normally or failed. NOTE: Messages do not always appear instantaneously. After the cursor has been moved onto the component, there is usually a delay of a second before the message tag appears.
Chapter 13 NPC Utility Coupled with Mode Three Installation This chapter introduces the NPC utility. The following topics are discussed: ♦ The NPC Utility – Section 13.1, page 13-2 13.1.1 The NPC Utility 13.1.2 To Access the Utility ♦ Configuring the Utility Options – Section 13.2, page 13-3 13.2.1 SSL 13.2.2 Email Notification 13.2.3 SNMP Traps 13.2.
RAIDWatch User’s Manual 13.1. The NPC Utility 13.1.1 Introduction NPC stands for “Notification Processing Center.” This utility is used to deliver event messages when the main RAIDWatch modules are installed to a RAID subsystem’s segregated disk capacity, the reserved space. NPC is implemented to manage event notification functions since the Configuration Client utility is not available with the Mode 3 installation scheme.
Chapter 13: NPC Utility Coupled with Mode Three Installation Figure 13-2: The NPC Initial Screen 13.2. Configuring the Utility Options 13.2.1 SSL SSL stands for “Secure Sockets Layer Handshake Protocol.” As shown in Figure 13-2 above, the initial screen defaults to the SSL option. Select the check box if you want to enable SSL connection for the management session with the array. NOTE: The configuration will take effect after you restart the network connection or reset the management station. 13.2.
RAIDWatch User’s Manual Figure 13-3: Email Notification – Sender Side Settings Step 2. Fill in or select the following configuration fields: SMTP Server: The Internet mail server used to send event notification. Sender's email: Enter a valid mail address, the "From" part of email notification functionality. Enabled: Select this check box to enable email notification. Subject: Allows you to append a subject matter to event notification emails; e.g., “Events from RAID 3 array.” Step 3.
Chapter 13: NPC Utility Coupled with Mode Three Installation Receiver's email: Shows a list of all the email addresses that the NPC will send a message to. Addresses added will be listed on the right. Severity: Select the severity level of events to be sent to the receiver station. Step 5. Click Apply or OK to complete the configuration. 13.2.3 SNMP Traps Step 1. Click on the Notification Process Center Setting tab and SNMP Trap to display SNMP settings.
RAIDWatch User’s Manual Figure 13-6: SNMP Traps – Receiver Side Settings Host IP: The port number of the agents listening for traps. Severity: Select the severity level of events to be sent to the receiver station. Trap receivers will be added to the Trap Receivers list on the right. Step 5. Click Apply or OK to complete the configuration. 13.2.4 Broadcast Notification Step 1. Click on the Notification Process Center Setting tab and Broadcast to display Broadcast settings.
Chapter 13: NPC Utility Coupled with Mode Three Installation Step 3. Click Apply or OK to proceed with configuration. Note that the configuration will be saved to the reserved space on the array and may cause a short delay. Step 4. Click Broadcasting List from the tabbed panel above. Host IP: The IP address a broadcast message will be sent to. Severity: Select the severity level of events to be sent to the receiver station.
RAIDWatch User’s Manual This page is intentionally left blank 13-8 Configuring the Utility Options
Chapter 14 Centralized Management Utility This chapter introduces the Centralized Management utility. The following topics are discussed: ♦ Centralized Management Section 14.1, page 14-2 ♦ Setting Up the Utility Section 14.2, page 14-2 ♦ Centralized Management Connection Section 14.3, page 14-4 ♦ Maintenance & Configuration Section 14.4, page 14-4 14.4.1 Icon Labels 14.4.
RAIDWatch User’s Manual 14.1. Centralized Management Introduction The Centralized Management utility provides: ♦ Online monitoring of Infortrend RAID subsystems over the network ♦ Creation of instant event logs ♦ Filtering and exporting event logs via text files The Centralized Management utility is an entrance portal to RAIDWatch whereby you can configure and maintain subsystems. Simply click the icon to connect to the subsystem. 14.2.
Chapter 14: Central Management Utility Step 3. Select the Auto Discovery option from the Module Name dropdown box. (See Figure 14-3) Figure 14-3: Auto Discovery Step 4. Define the IP scan range to search the network. Click Finish. Step 5. Double-click the ON/OFF switch. The Root Agent will automatically scan the IP range for available subsystems on the network. Step 6. Check the scan results in RootAgent Setting. IMPORTANT! The Auto Discovery Module only supports the Firmware versions listed below.
RAIDWatch User’s Manual 14.3.Centralized Management Connection Centralized Management will display subsystems based on the Agent IP list. The information is queried from the RootAgent and available subsystems, and they are displayed using colorful icons. Figure 14-4: Not Connected Figure 14-4 shows that Central Management is not connected with the RootAgent and there will be no systems listed in the Centralized Management window.
Chapter 14: Central Management Utility NOTE: Icons that are blinking red have warning messages or events that should be verified. 14.4.2 System Events There are two (2) options when clicking on a system icon. Connecting to the subsystems 1. Double-click a system icon to invoke the subsystem’s event log. The main program will bring out a detailed event list. Filter and export log Figure 14-8: Event List Options 2.
RAIDWatch User’s Manual Figure 14-9: Event View Option The Event log filter option allows you to filter events based on various criteria.
Appendices This chapter details the following: ♦ Command Summary – Appendix A, page App-2 A.1 Menu Commands A.2 Configuration Client Utility Commands ♦ Glossary - Appendix B, page App-7 ♦ RAID Levels - Appendix C, page App-13 C.1 RAID Description C.2 Non-RAID Storage C.3 RAID 0 C.4 RAID 1 C.5 RAID 1(0+1) C.6 RAID 3 C.7 RAID 5 C.8 RAID 6 C.9 RAID 10, 30, 50 ♦ Additional References - Appendix D, page App-19 D.1 Java Runtime Environment D.2 RAIDWatch Update Downloads & Upgrading D.
RAIDWatch User’s Manual Appendix A. Command Summary This appendix describes the commands available in RAIDWatch Manager. These commands are presented either in each configuration window, as command buttons on pull-down menus, or on pop-up menus triggered by a mouse right-click. A.1. Menu Commands This section lists and explains the commands available from the menus in the menu bar. A.1.
Appendices RAIDWatch Window Menu Commands (Outer-Shell Window) Command Description Next Window This command allows you to switch to the display of the next array being connected. This command arranges currently open windows so that they are all visible and occupy an equal part of the RAIDWatch application window. This command arranges currently open windows so that one is placed over the other but every window is still visible. This command functions like the minimize caption button.
RAIDWatch User’s Manual RAIDWatch Action Menu Commands (Management Window) Command Array Information Maintenance Configuration Description Displays the second-level menu, which provides access to all information windows. Access to the information windows can also be found on the navigation panel. Displays the second-level menu, which provides access to all maintenance tasks windows. Access to the maintenance task windows can also be found on the navigation panel.
Appendices Tool Bar Commands Command Description Open Bookmark File Opens a previously saved connection view profile. This profile contains information about the Root Agent server and the RAID arrays being managed by a Root Agent. Saves the current connection view profile onto your system drive. The default file name is “default.npc.” Connects to a Root Agent server, usually the one that you choose as a management and install the Configuration Client utility.
RAIDWatch User’s Manual This page is intentionally left blank App-6 Command Summary
Appendices Appendix B. Glossary Fibre (Also known as “Fibre Channel”) A device protocol (in the case of RAID, a data storage device) capable of high data transfer rates. Fibre Channel simplifies data bus sharing and supports greater speed and more devices on the same bus. Fibre Channel can be used over both copper wire and optical cables. Fiber An optical network data transmission type of cable, which is unrelated to the Fibre Channel described above.
RAIDWatch User’s Manual ISEMS Infortrend Simple Enclosure Management System – an I2C-based enclosure monitoring standard developed by Infortrend Technologies, Inc. JBOD Just a Bunch of Disk – non-RAID use of multiple hard disks for data storage. JRE Java Runtime Environment – the Solaris Java program used to run .JAR applications locally, over a network, or the Internet. Logical Drive Typically, a group of hard disks logically combined to form a single large storage unit.
Appendices NRAID Non-RAID. The capacities of all the drives are combined to become one logical drive (no block striping). In other words, the capacity of the logical drive is the total capacity of the physical drives. NRAID does not provide data redundancy. Parity Parity checking is used to detect errors in binary-coded data. The fact that all numbers have parity is commonly used in data communications to ensure the validity of data. This is called parity checking.
RAIDWatch User’s Manual SASL SASL is the Simple Authentication and Security Layer, a mechanism for identifying and authenticating a user login to a server and for providing negotiating protection with protocol interactions. SCSI Small Computer Systems Interface (pronounced “scuzzy”) – a high-speed interface for mass storage that can connect computer devices such as hard drives, CD-ROM drives, floppy drives, and tape drives. SCSI can connect up to sixteen devices. S.E.S.
Appendices Striping Also called RAID 0. A method of distributing data evenly across all drives in an array by concatenating interleaved stripes from each drive. Stripe Size (A.k.a. “chunk size.”) The smallest block of data read from or written to a physical drive. Modern hardware implementations let users tune this block to the typical access patterns of the most common system applications. Stripe Width The number of physical drives used for a stripe.
RAIDWatch User’s Manual This page is intentionally left blank App-12 Glossary
Appendices Appendix C. RAID Levels This appendix provides a functional description of Redundant Array of Independent Disks (RAID). This includes information about RAID and available RAID levels. C.1. RAID Description Redundant Array of Independent Disks (RAID) is a storage technology used to improve the processing capability of storage systems. This technology is designed to provide reliability in disk array systems and to take advantage of the performance gains multiple disks can offer.
RAIDWatch User’s Manual Figure C-1: Non-RAID Storage C.3. RAID 0 RAID 0 implements block striping where data is broken into logical blocks and striped across several drives. Although called RAID 0, this is not a true implementation of RAID because there is no facility for redundancy. In the event of a disk failure, data is lost. In block striping, the total disk capacity is equivalent to the sum of the capacities of all drives in the array.
Appendices C.4. RAID 1 RAID 1 implements disk mirroring where a copy of the same data is recorded onto two sets of striped drives. By keeping two copies of data on separate disks or arrays, data is protected against a disk failure. If a disk on either side fails at any time, the good disks can provide all of the data needed, thus preventing downtime. In disk mirroring, the total disk capacity is equivalent to half the sum of the capacities of all drives in the combination.
RAIDWatch User’s Manual IMPORTANT! RAID (0+1) will not appear in the list of RAID levels supported by the controller. If you wish to perform RAID 1, the controller will determine whether to perform RAID 1 or RAID (0+1). This will depend on the drive number that has been selected for the logical drive. Figure C-4: RAID 1(0+1) Storage C.6. RAID 3 RAID 3 implements block striping with dedicated parity.
Appendices Figure C-5: RAID 3 Storage C.7. RAID 5 RAID 5 implements multiple-block striping with distributed parity. This RAID level offers the same redundancy available in RAID 3, though the parity information is distributed across all disks in the array. Data and relative parity are never stored on the same disk. In the event a disk fails, original data can be reconstructed using the available parity information. For small I/Os, as few as one disk may be activated for improved access speed.
RAIDWatch User’s Manual C.8. RAID 6 A RAID 6 array is essentially an extension of a RAID 5 array with a second independent distributed parity scheme. Data and parity are striped on a block level across multiple array members, just like in RAID 5, and a second set of parity is calculated and written across all the drives. The goal of this duplication is solely to improve fault tolerance; RAID 6 can handle the failure of any two drives in the array while other single RAID levels can handle at most one fault.
Appendices Appendix D. Additional References This appendix provides direction to additional references that may be useful in creating and operating a RAID, and in using RAIDWatch and RAIDWatch Manager. D.1. Java Runtime Environment JRE (Java Runtime Environment) is a shareware product from Sun/Solaris. Two websites that may be of use relative to JRE are: The main Java website URL: java.sun.com The JRE download website URL: www.sun.com/software/solaris/jre/download.html D.2.
RAIDWatch User’s Manual This page is intentionally left blank App-20 Additional References
