Document Name: Spheras Storage Director Installation and User Guide Part Number MAN-00005-UG Revision 1.
Revision History Rev Approved Date 1.0 ECO-3679 Sep., 2003 Table 1 Revision History 2 Change Description Released with SPHSSD 2.
Contents Contents - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3 List of Figures - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7 Preface - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Proprietary Rights Notice - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Document Description - - - - - - - - - - - - - - -
2.7.2 Updating Your Spheras Storage Director Server with Linux and Solaris- - - 42 2.8 Starting the Spheras Storage Director Client- - - - - - - - - - - - - - - - - - - - - - 43 Chapter 3 Setting up the Spheras Storage Director Client - - - - - - - - - - - - - - 3.1 Security access levels - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3.2 Passwords - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3.
.11 Backing Up a Controller Configuration - - - - - - - - - - - - - - - - - - - - - - - - 107 Chapter 6 Monitoring Activities - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6.1 Monitoring All Servers - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6.2 Monitoring Events - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6.2.1 Viewing Events - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6.2.
A.1.2 Windows - Manually Configuring a Microsoft IIS HTTP Web Server - - A.1.3 Linux - Manually Configuring an Apache HTTP Web Server - - - - - - - A.1.4 Solaris - Manually Configuring an Apache HTTP Web Server - - - - - - - Appendix B Detailed Information About Configurations - - - - - - - - - - - - - - - - - B.1 What is the purpose of your array? - - - - - - - - - - - - - - - - - - - - - - - - - - - - B.2 RAID Levels - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - B.
List of Figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36 Figure 37 Figure 38 Figure 39 Figure 40 Figure 41 Figure 42 Figure 43 Figure 44 Figure 45 Figure 46 Figure 47 Spheras Storage Director Client an
Figure 48 Figure 49 Figure 50 Figure 51 Figure 52 Figure 53 Figure 54 Figure 55 Figure 56 Figure 57 Figure 58 Figure 59 Figure 60 90 Figure 61 Figure 62 Figure 63 Figure 64 Figure 65 Figure 66 Figure 67 Figure 68 Figure 69 Figure 70 Figure 71 Figure 72 Figure 73 Figure 74 Figure 75 Figure 76 Figure 77 Figure 78 Figure 79 Figure 80 Figure 81 Figure 82 Figure 83 Figure 84 Figure 85 Figure 86 Figure 87 Figure 88 Figure 89 Figure 90 Figure 91 Figure 92 Figure 93 Figure 94 Figure 95 Figure 96 8 Controller Prop
Figure 97 Figure 98 Figure 99 Figure 100 Figure 101 Figure 102 Figure 103 Figure 104 Figure 105 Figure 106 Figure 107 Figure 108 Figure 109 Figure 110 Figure 111 Figure 112 Figure 113 Figure 114 Figure 115 Figure 116 Task Monitoring - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Logical Drive Initialization Warning - - - - - - - - - - - - - - - - - - - - - - Logical Drive Consistency Check - - - - - - - - - - - - - - - - - - - - - - - - Edit a WWN Table - - - - - - - - - - - - - - -
Preface Proprietary Rights Notice This document contains proprietary information of Adaptec, Inc. The information contained herein is not to be used by or disclosed to third parties without the prior express written permission of an officer of the Adaptec, Inc. Any product or products described herein is/are a licensed product of Adaptec, Inc. Document Description Document GEN-00005-UG, First Edition, September 2003 This document describes the SANbloc 2500, Spheras Storage Director.
12 Spheras Storage Director Installation and User Guide
Chapter 1 Introduction The Spheras Storage Director™ (SSD) is a browser-based, remote configuration and management tool supporting external RAID controllers. The Spheras Storage Director console uses Java™ technology via an applet running in a supported World Wide Web browser environment. 1.
Figure 1 Spheras Storage Director Client and Server Relationship This diagram shows how the client talks with the server. Spheras Storage Director uses Java RMI (Remote Method Invocation) as Internet connectivity paths that are used when the client talks with the server that launched it (Server B). It also shows how Server B will talk to the other servers in response to the user interacting with the other servers via the client machine. 1.
1.4.3 Spheras Storage Director Requirements The Spheras Storage Director architecture is a client/server relationship. You can use a remote client to manage several servers. Hardware requirements and software requirements for the installation and operation of the Spheras Storage Director are described in the following sections. Refer to your workstation documentation, server documentation, and to the operating system documentation for more information on hardware and operating system requirements. 1.4.
1.4.6 Using Host Bus Adapters and Drivers A Host Bus Adapter (HBA) connects a host system to either a SCSI bus or a fibre loop. This device usually performs the lower layers of the SCSI or Fibre Channel protocol and normally operates in the initiator role. One or more HBAs may be integrated into a host/server computer, cluster of host computers, or SAN. For current information on the latest HBAs and compatible drivers, see the following web site: http://www.adaptec.com 1.4.
Chapter 2 Installation and Startup For complete installation and startup information, see the PDF version of the Spheras Storage Director Software: Installation and User’s Guide located on the distribution CD ROM. This section assumes that the network administrator for your site will be performing these installation procedures. Before installing the Spheras Storage Director Server and Client, read 1.4.3 Spheras Storage Director Requirements on page 15 section.
The Spheras Storage Director software is not designed to support the connection of multiple servers to a single storage subsystem. While it is possible to connect multiple servers to a single storage subsystem, this configuration can cause communication problems that affect the Spheras Storage Director software. In contrast, a single server can be connected to multiple storage subsystems. The Spheras Storage Director software is a based upon a classic client/server model.
(Many Linux environments will automount the CD drive.) 5 Locate the CDROM and find the setup.bin file in the following path: /ssd/linux/setup.bin 6 Like Windows, there are several ways to run a program. Here are two methods: Browse using a file manager to: /mnt/cdrom/ssd/linux Double click on setup.bin In a console window, type: cd /mnt/cdrom/ssd/linux type: ./setup.bin 7 The InstallShield Wizard starts and the Spheras Storage Director Installer Welcome screen opens. Proceed to 2.
2.3.1 Server Installation Steps This section describes the installation of the server component of the Spheras Storage Director. For information on installing the client component, see 2.3.2 Client Installation Steps on page 28. 1 After starting the installation using the setup program specified 2.2.1 Starting the Install Process on page 18, the InstallShield Wizard starts and the welcome screen is displayed. The InstallShield Wizard will first prepare the Java Virtual Machine.
Figure 3 Spheras Storage Director license agreement Click Next. The License Agreement is displayed. 2 Read the license agreement. Select the “I accept the terms of the license agreement” radio button to accept the terms of the agreement and continue. If you select the “I do not accept the terms of the license agreement,” you will not be allowed to continue the installation. A dialog box will open asking if you wish to cancel the setup. Click OK to cancel the installation. 3 Click Next.
Figure 4 4 Choose the type of installation Figure 5 22 Choose the location for the server installation Choose Installation Type Spheras Storage Director Installation and User Guide
5 Click Next. In the Java RMI (Remote Method Invocation) Port Number field, use the default port number or type a desired port number. The RMI port represents the connectivity path that the server uses to communicate with the client. All Spheras Storage Director Servers must use the same RMI port number to be controlled by a single Spheras Storage Director Client. Note: Figure 6 6 The value that you specify for the RMI port cannot be less than 1024. Set the Server RMI Port Number Click Next.
to manually configure your HTTP server after installing the Spheras Storage Director code.
7 Click Next. A summary of what will be installed is displayed. Note that the total size of your installation may not match what is shown here. Figure 8 Installation summary © 2003, Adaptec, Inc.
8 Click Install. The installation process begins. During installation, files are decompressed and copied to the destination folder that you previously chose. You will also see flashing blank windows during the installation. This is part of the automatic HTTP configuration.
9 When the installation of the server code is complete, the following dialog is displayed. Select whether or not you want to view the readme file and click Next. Figure 10 Server installation complete © 2003, Adaptec, Inc.
10 When the installation is complete, the Finish dialog box opens. Click Finish to complete the installation. Figure 11 Installation Complete 11 Proceed to one of the following sections: To install the client code, see 2.3.2 Client Installation Steps on page 28. If you do not need to set up any additional clients, see: • 2.4 Windows: Post-Installation Configuration and Verification on page 36 • 2.5 Linux: Post-Installation Configuration and Verification on page 37 • 2.
Figure 12 Installation Welcome © 2003, Adaptec, Inc.
2 Click Next. The License Agreement is displayed. Figure 13 Spheras Storage Director license agreement 3 Read the license agreement. Select the “I accept the terms of the license agreement” radio button to accept the terms of the agreement and continue. If you select the “I do not accept the terms of the license agreement,” you will not be allowed to continue the installation. A dialog box will open asking if you wish to cancel the setup. Click OK to cancel the installation. 4 Click Next.
Figure 14 Choose the location for the client installation Figure 15 Choose the type of installation © 2003, Adaptec, Inc.
Select the radio button for the component that you want to have installed. 5 Click Next. Enter the IP address or host name for one of the servers that you want to connect to. (You can add additional servers later. See: 3.4 Adding a New Server on page 48.
6 Click Next. A summary of what will be installed is displayed. Note that the total size of your installation may not match what is shown here. Figure 17 Installation summary © 2003, Adaptec, Inc.
7 Click Install. The installation process begins. During installation, files are decompressed and copied to the destination folder that you previously chose.
Figure 19 Client installation complete © 2003, Adaptec, Inc.
9 When the installation is complete, the Finish dialog box opens. Click Finish to complete the installation. Figure 20 Installation complete 10 Proceed to one of the following sections: • 2.4 Windows: Post-Installation Configuration and Verification on page 36. • 2.5 Linux: Post-Installation Configuration and Verification on page 37. • 2.6 Solaris Post-Installation Configuration and Verification on page 39. 2.4 Windows: Post-Installation Configuration and Verification 2.4.
Scroll down the list and locate Apache2. Right-click on the service and select Stop. Right-click on the same service again and select Start. 4 If you did not install your HTTP server prior to installing the Spheras Storage Director server, your HTTP server was not configured automatically during the installation process. To configure your HTTP server, see Appendix A Manually Configuring HTTP Servers on page 201. 5 Set up a user ID on the system that is running the Spheras Storage Director server.
4 If you did not install your HTTP server prior to installing the Spheras Storage Director server, your HTTP server was not configured automatically during the installation process. To configure your HTTP server, see , Appendix A Manually Configuring HTTP Servers on page 201. 5 Set up a user ID on the system that is running the Spheras Storage Director server. The Spheras Storage Director server uses existing user IDs on the server running it to authenticate users and assign authorities to them. See 3.
11 Proceed to 2.8 Starting the Spheras Storage Director Client on page 43. 2.6 Solaris Post-Installation Configuration and Verification This section contains additional items that must be configured or verified on Solaris systems. 2.6.1 1 Define Devices and Target/LUN Combinations Modify the sd.conf file to define devices and target/lun combinations. In a console window enter: cd /kernel/drv Open the sd.conf file with an editor.
name="sgen" class="scsi" target=1 lun=0; name="sgen" class="scsi" target=1 lun=1; name="sgen" class="scsi" target=1 lun=2; name="sgen" class="scsi" target=1 lun=3; name="sgen" class="scsi" target=1 lun=4; name="sgen" class="scsi" target=1 lun=5; name="sgen" class="scsi" target=1 lun=6; name="sgen" class="scsi" target=1 lun=7; name="sgen" class="scsi" target=2 lun=0; name="sgen" class="scsi" target=2 lun=1; name="sgen" class="scsi" target=2 lun=2; name="sgen" class="scsi" target=2 lun=3; name="sgen" class="s
4 If you did not install your HTTP server prior to installing the Spheras Storage Director server, your HTTP server was not configured automatically during the installation process. To configure your HTTP server, see A.1.4 Solaris - Manually Configuring an Apache HTTP Web Server on page 210. 5 Set up a user ID on the system that is running the Spheras Storage Director server.
Director Servers with the latest version; failure to do this will affect the ability of the Spheras Storage Director Server to communicate with other Spheras Storage Director Servers. Only the Spheras Storage Director Server requires updating. The Client is a Java Applet that communicates with the Server and does not require updating. 2.7.
4 To ensure compatibility with the new Spheras Storage Director Server, it is recommended that you remove any previous installations of JRE. The Spheras Storage Director installation process detects that JRE is not installed and installs a compatible version. 5 You are now ready to reinstall the Spheras Storage Director Server software. See 2.3.1 Server Installation Steps on page 20. 6 After you have installed the Spheras Storage Director Server launch the Client, see 2.3.
is based on a userid/password defined to the server through the operating system specific user management services. Once a userid has been authenticated, the appropriate authorization for the userid will be determined from its group memberships on the server. See 3.1 Security access levels on page 45. To learn more about the navigation features and options that the Spheras Storage Director Client provides, see , Chapter 4 Navigating the Spheras Storage Director Client on page 55.
Chapter 3 Setting up the Spheras Storage Director Client This section describes the security access levels, passwords, and method to sign onto the Spheras Storage Director Client. The process to add Servers and create Server Groups is also described. 3.1 Security access levels The Spheras Storage Director Client authenticates with the Spheras Storage Director server.
Figure 21 Logon Dialog Use the following steps to logon to Spheras Storage Director: 1 Type your User name. Select a user name with access privileges on the server that correspond to the desired access level in Spheras Storage Director. User names are encrypted when transmitted across the network. There is no limit on the User name length. See 3.1 Security access levels on page 45 for more information. 2 Enter your password in the login dialog.
4 Click Group->New on the menu bar and the New Server Group dialog box opens. Figure 22 New Server Group Dialog Box 5 In the Server Group Name field, type the desired name of the server group you are adding. All characters are acceptable and there is no limit to the number of characters you can enter. Naming a server group is a way of identifying a site or collection of related server computers. For example, names like Payroll or Domestic Sales can be used.
From the tool bar, click Properties Right-click the server group and select Properties Deleting Server Groups 3.3.3 Deleting a Server Group allows you to delete any previously defined Server Group. However, you cannot delete the system-defined All Servers group, as this is part of the root directory of the navigation area.
3.4.1 1 To define a new server: Click Server->New on the menu bar, the New Server dialog box opens. Figure 24 New Server Dialog Box 2 Type the IP Address or Host Name of the server you want to add. All characters are acceptable and there is no limit to the number of characters, you can enter. 3 The New Server Description field is optional. All characters are acceptable and there is no limit, to the number of characters you can enter. 4 Click Connect to Server.
addresses. If you do not know the IP addresses of the controllers or the controller does not have an IP address, see 8 Select IP settings on page 85 for information on how to set up IP addresses. • Dynamic discovery of controllers - allows the server to automatically discover all controllers that share its subnet. • iHosts file (default) - only the IP addresses of the controllers that are listed in the iHosts file will be discovered. See 3.7 Editing the iHosts File on page 52.
To delete a server, follow these steps: 1 Select a server from the navigation area or the content area. Figure 25 Deleting a Server Warning 2 From the menu bar, click Server->Delete or Right-click the server->Delete. A warning dialog box opens. 3 Click Yes to delete the selected server or click No to close the dialog box without deleting a server. 3.
4 From the menu bar click Group->Replicate or right-click Group->Replicate in the navigation area. The Replicate Information dialog box opens confirming the replication. Figure 26 5 Replicate Information Dialog Box Click OK. Replication can also be done when creating a new server group. See 3.4 Adding a New Server on page 48. 3.7 Editing the iHosts File The iHosts file contains the IP addresses for controllers that are not a part of the subnet of your Spheras Storage Director Server.
1 Click Server->Edit iHosts File. The Edit iHosts File opens. Figure 27 Edit an iHost File 2 Using the format of the Example given, type in your desired IP Addresses. You can also copy, cut, and paste your IP Address information. It is important to use the format shown in the example. Failure to do so may affect the ability of the server to discover controllers. 3 Remember to uncomment your IP addresses by removing the “#” symbol. 4 Select File->Save. 5 Select File->Exit to close the iHosts File.
54 Spheras Storage Director Installation and User Guide
Chapter 4 Navigating the Spheras Storage Director Client This section describes the navigation features and options that the Spheras Storage Director Client provides. 4.1 Components of the Spheras Storage Director Opening Screen When starting up the Spheras Storage Director Client (with servers defined), the opening screen displays a menu bar, tool bar, path indicator, navigation area, content area, and status bar.
Figure 28 Spheras Storage Director Opening Screen 6 Object status: Shows the number of objects or selected objects in the content area. 7 Logon status: Shows the user name and the current access level.
4.2 Status Icons The following icons display the status of the controller system. These icons will display on the node tree in the navigation area and in the content area. Some icons display only when using the Physical View. Optimal State Icon Warning State Icon Error State Icon All resources are optimal At least one resource is in a Warning State Serious State Icon Critical State Icon An error has occurred that did not cause data loss, usually a software error.
The physical drive is in a normal running state (Physical View Only). The physical drive is in a not selected state (Physical View Only). This means that a physical drive is in the slot, but not part of the resource or set of resources being viewed. The physical drive may have failed due to transient errors. Physical Drive Not Supported The physical drive is in a not supported state (Physical View only). This icon is also used with enclosure status. 4.
The Group Menu contains the following options: Properties: Displays the Server Group name, description, and server members and non-members. New: Opens the New Server Group Window and allows you to create new server groups. Delete: Opens the Delete Server Group dialog box and allows you to delete a server group. Also, gives you the option to delete all servers that were members of this server group.
4.3.3 Figure 32 Controller Menu Controller menu The Controller Menu contains the following options: Properties: Allows you to change or modify various parameters for the selected controller. Configure Unused Storage: Configures unused storage with assistance or manually. Change Host/LUN mapping: Opens the Host/LUN mapping dialog box for you to modify the mapping. Delete Storage Configuration: Deletes the configuration of the selected controller.
accessed on those drives. Disk scrubbing is not enabled by default. See 7.4 Disk Scrubbing on page 188 for more information. 4.3.4 Event Menu Figure 33 Event menu The Event Menu contains the following options: Properties: Allows you to view or change event log properties and event handling settings. Clear Log: Clears the event log of the selected server. Print Log: Opens a browser window to allow printing of the event log.
The Logical Menu has the following options: Properties: Allows you to view or change logical drive properties. New: Opens the Manual Configuration Wizard and allows you to create a new logical drive. Expand: Opens the Manual Configuration Wizard and allows you to expand an existing logical drive. Delete: Deletes the selected logical drive. Initialize: Initializes the selected logical drives. See 7.
4.3.8 Figure 37 Physical Menu Physical menu The Physical Menu contains the following options: Properties: Allows you to view physical drive properties. Make Hot Spare: Makes the selected physical drive a hot spare. Remove Hot Spare: Returns the physical drive to the unused status. Locate: Blinks the LED(s) of the selected physical drive(s). Spin Down: Prepares the physical drive for removal. Force Online/Offline: Allows you to force a physical drive online or offline. 4.3.
Locate: 4.3.11 Figure 40 Blinks the LED(s) of the physical drive(s) contained by the selected enclosure. View Menu View menu The View Menu contains the following options: Text: Enabled when there is a text based view for the node selected in the navigation area. Physical: Enabled when there is a physical based view for the node selected in the navigation area. Physical views are available for physical drives, unused drives, failed drives, and hot spares.
4.4 Toolbar and Toolbar Icons Figure 42 Toolbar The Toolbar contains icons for the following functions: 1 Opens the Configure Unused Storage with Assistance Wizard. 2 Opens the Configure Unused Storage Manually Wizard. 3 Opens the property page of the selected object. 4 Refreshes the navigation and content area views. 5 Toggles between the text and physical views. 6 Displays Help for what is currently displayed in the content area. 4.
66 Spheras Storage Director Installation and User Guide
Chapter 5 Configuration Activities The following configuration activities are included in this section: • 5.1 Setting Event Log Properties on page 67 • 5.3 Setting and Modifying Controller Properties on page 73 • 5.4 Creating Storage Configurations on page 86 • 5.5 Spanning in Spheras Storage Director on page 99 • 5.6 Expanding a Logical Drive on page 100 • 5.7 Deleting a Logical Drive on page 101 • 5.8 Expanding an Array on page 102 • 5.9 Deleting an Array on page 104 • 5.
Figure 43 Event Log Properties Dialog Box: General Tab Open the Event Log Properties dialog box by selecting Event-> Properties on the menu bar. In the Event Properties Dialog box, under the General tab, set the new event log size. Select Alert Map.
Figure 44 Event Log Properties Dialog Box: Alert Map Tab Choose which event severity levels should be sent to the operating system event log by enabling or disabling the corresponding check boxes. Enable or disable check boxes to launch the appropriate notification application corresponding to the event severity level. Click Create New Notification Application to add an application to launch. The Add Notification Application dialog box opens. © 2003, Adaptec, Inc.
Figure 45 Event Properties Dialog Box: Notification Application Tab Click New to add a new notification application. Click Edit to edit an existing notification application. Click Delete to delete a notification application.
Figure 46 Add Notification Application Dialog Box Type the name and path of the desired application to launch. If you don’t remember the name or path of the application, click Browse. Use an existing application or create an application (such as a shell script) that sends e-mails, pages, or faxes. Type a description of the application (for example: Bob’s Pager). Click Delete to delete an existing application parameter. Click Edit to edit an existing application parameter.
User Defined: You can type your own parameter string (for example: pager or email) by typing over the User Defined parameters. Event Message ID: The number that is displayed in the ID column of the events table (for example, 389). Event Message Severity: The severity level of the event. Event Address: The contents of the address column of the events table (for example: ctl:0 chn:0 tgt:1). Element ID: A text string that contains unique identifiers for each of the resources associated with the error.
; EVENT_ELEMENT_ID (world wide names and/or serial numbers of devices involved ;in the event (eg. “Controller world wide name:2000 0080e5 11ea07”) Locate the “Page On Call Manager” section in the file. Format this section of the cfg.ini file by using the following information as an example. The example below describes an Event Alert Application, which launches the application c:\pagemgr.
1 Open the Controller Properties; click Controller->Properties on the menu bar. Figure 48 Controller Properties Dialog Box: General: Summary Tab The Summary tab displays a summary of installed controller features and the status of the controller.
2 Select Status. Figure 49 Controller Properties Dialog Box: General: Status Tab The Status Tab displays the Name, Status, and Mode of the controller. It also displays whether Conservative cache is active or not and the reason. If the controller is not in conservative cache mode, the Reason field is greyed out.
3 Select Basic. Figure 50 Figure 50 Controller Properties Dialog Box: Basic In the Basic tab, you have the following options: Enable read ahead: When enabled, reads data to the next stripe boundary (based on stripe size), and retains in cache any data beyond the size of the actual read request. The Read Ahead function improves data retrieval performance by allowing the controller to read into cache a full stripe of data at a time. This greatly improves the percentage of cache hits.
function should remain enabled during normal controller operation. A controller reset is required before this parameter takes effect. Enable background initialization:When enabled, this option allows a single logical drive or multiple logical drives to be initialized as a background operation while reads and writes are being performed. Background initialization is invoked automatically upon receipt of the first read/ write command from the host.
• Physical drive rebuild rate: When changing from Multi-TID or MultiPort to master/slave or inactive, all mappings on the inactive ports are lost. A rate of 50 assigns the maximum allowable resources to a drive rebuild, allowing the rebuild to proceed at its fastest. Lowering the number devotes more resources to I/Os and consequently slows the Rebuild process. This parameter takes effect immediately without resetting the controllers.
4 Select Advanced. Figure 51 Controller Properties Dialog Box: Advanced In the Advanced tab, you have the following options: Conservative cache mode when ...
• The Conservative Cache Mode Parameter is enabled for a dual-active controller configuration, and a controller failure has occurred. • A MORE™ (Mylex® Online RAID Expansion) operation is initiated. During a MORE operation, the system automatically enters into conservative cache mode. After MORE completes, the system drives are restored to their original settings. • A Power supply has failed (not the removal of a power supply).
Kill drive on predicted failure: When enabled, allows a physical drive to detect a Predicted Failure Analysis event and, if a spare exists, the spare drive is made offline and a rebuild begins immediately. Poll now: When selected, the controller polls immediately and then reverts to the regular polling schedule. A message dialog box opens stating, “Polling for predicted drive failures has started. Any events generated as a result of this polling can be viewed in the event log.” 5 Select Expert.
Reset propagation: When enabled, a reset detected by one port may be propagated out of the other ports including ports on the partner controller. Report check condition for invalid LUN:When enabled, reports the check condition affecting the handling of the Inquiry command when the referenced LUN is invalid. Note: A controller reset is required to make a change to this option take affect.
6 Select Duplex Mode. Figure 53 Controller Properties Dialog Box: Expert: Duplex Mode Dialog Tab In the Duplex Mode Tab, you have the following options: Report busy status during failback:When enabled, causes all pending commands to be quietly dropped during failback. This is intended to help hosts that are confused by Queue Full. Note: A controller reset is required to make a change to this option take affect. Enable auto restore: The default is disabled.
7 Select Fibre. Figure 54 Figure 54 Controller Properties Dialog Box: Fibre: Host Ports Tab In the Host Ports Tab, you have the following options: Controller worldwide name: Displays the host identity of a Host Bus Adapter of a server on the fibre channel loop by slot number. Node name retention: When enabled, each controller shares its node name with its partner controller, and those names are used through all phases of failover and failback.
Note: A controller reset is required to make a change to this option take affect. Host port speed: Sets a 1 or 2 Gigabits per second for Auto Negotiate speed for the selected host ports. Hard loop addressing: Enables hard loop IDs on a controller. Note: A controller reset is required to make a change to this option take affect. ID field: 8 is displayed only if Hard Loop Addressing is enabled. It allows you to select a value 0-125.
For dual-active controllers, when one controller has been discovered, and the other only partially discovered, the state of the discovered controller is displayed in the Spheras Storage Director. You set the IP address of the partially discovered controller here. If you do not set an address and a failover occurs, the status of the dual-active pair reverts to partially discovered.
of all RAID levels as well as Capacity, Availability, and Performance (CAP) strategies and other useful configuration information. 5.4.1 Multiple Configuration Tool Locking Spheras Storage Director provides a Multiple Configuration Tool Lock feature that enables write access to be locked on a controller system. The configuration locking occurs when a configuration is being performed by another configuration tool. The following message is displayed “Another configuration session is in progress.
Figure 58 Configure Unused Storage with Assistance: Fault Tolerance Dialog Box Configure the following options for fault tolerance: Select Fault Tolerance. This option is disabled if there is only one available unused drive in the system. Select the number of hot spares from the drop-down list. This option is only available with Fault Tolerance. The hot spare option is disabled if there are only two available unused drives in the system. Click Next or press the Enter key.
Figure 59 Configure Unused Storage with Assistance: RAID Level Dialog Box Choose one of the following RAID Level options: Parity RAID (RAID level 5). This option is the default if there are three or more unused drives available in the system. Mirrored drives (RAID level 1). If you selected the No Fault Tolerance check box, the following RAID level dialog box opens. © 2003, Adaptec, Inc.
Figure 60 Configure Storage with Assistance: No Fault Tolerance RAID Level Dialog Box Choose one of the following RAID Level options: Data Striping (RAID level 0). This option is selected by default if there is more than one unused drive available in the system. No Data Striping (JBOD). Click Next or press the Enter key. The Logical Drives dialog box opens.
Figure 61 Note: Configure Unused Storage with Assistance: Logical Drives Dialog Box. The dialog shown in this figure is displayed if the controller property Enable Background Initialization is enabled. If the controller property Enable Background Initialization is disabled, an additional check box is displayed which allows you to Enable Foreground Initialization. From the drop-down list, select the number of logical drives you wish to create (1-32).
Click Next or press the Enter key. The Summary dialog box opens. Figure 62 Configure Unused Storage with Assistance: Summary Dialog Box Examine the configuration summary for details about the configuration you have set up. If you want to start over, click Cancel. If you want to make changes, click Back to return to the appropriate dialog box. If you are satisfied with the configuration that you have set up, click Finish or press the Enter key to apply the new configuration to the controller. 5.4.
Figure 63 Configure Storage Manually The Manual Storage Configuration dialog box opens. Note: Only those previously-configured arrays that have unused capacity are shown in this dialog. © 2003, Adaptec, Inc.
Figure 64 Manual Storage Configuration To create a disk array, perform the following: Spheras Storage Director automatically creates an array for you. The new array (New Array 1) is displayed in the tree node. From the Physical Drives pane, select a physical drives to add to the array. Click Add to Array (or drag and drop). The physical drives are displayed in the tree node under the selected array. Repeat steps 1-3 until you have the desired amount of disks in your array.
If you want to start over, click Cancel and reopen the dialog box. When you have finished creating the disk arrays, click Next or the Create Logical Drive tab to continue your configuration. The Create Logical Drive Tab displays. Figure 65 Manual Storage Configuration: Create Logical Drive Tab The Create Logical Drives Tab is where you configure your disk arrays into logical drives. You must create at least one logical disk on each array. A maximum of 32 logical drives can be created per controller.
Type the amount of available capacity for this logical drive. If your total configuration has only one logical drive that uses all available capacity, the default sizes should not be changed. If you intend to create additional logical drives, enter a smaller number to reserve the desired capacity. The Array Usage pie chart indicates how the capacity is being used. Select Write Cache if you want this logical drive to use Write Back Caching. Write Back Caching improves performance, but puts data at risk.
Figure 66 Manual Storage Configuration: Host/LUN Mapping Tab The Host/LUN Mapping Tab is where you sequentially map LUN numbers to logical drives. The controller uses a World Wide Name (WWN) to uniquely identify host computers that have logged into the controller. A list of valid hosts and their corresponding WWNs is provided to Spheras Storage Director in order to configure the host to LUN mapping. Once logical drives are configured, the controller maintains a table of WWNs for each logical drive.
Figure 67 Host/LUN Mapping Tab: Custom LUN Mapping Dialog Box The custom LUN Mapping dialog box allows you to manage host access to a logical drive/LUN number. Use the assigned LUN drop-down box to select the LUN number for a particular logical drive column. Then use the check boxes at the intersection of each logical drive column Figure 67 Host/LUN Mapping Tab: Custom LUN Mapping Dialog Box on page 98 and host row to allow or deny host access.
The Summary Tab displays. Figure 68 Manual Storage Configuration: Summary Tab The Summary tab displays details about the configuration that will be set up according to your configuration choices: If you want to change some of your choices, click Back If you want to start over, click Cancel If you accept the configuration as presented in the Summary tab, click Finish or press the Enter key to apply the new configuration to the controller. 5.
5.6 Expanding a Logical Drive Online capacity expansion is the ability to increase the size of a logical system drive while normal reads and writes occur. The expansion can be obtained when you change the RAID level, or increase the amount of space on the physical drives allocated to the logical drive, or both. When performing this operation, you cannot change the write cache, initialize drive, or stripe size of an existing logical drive.
Figure 69 Manual Storage Configuration: Expand Logical Drive Highlight the Physical Drive that you want to use in the expansion. Click the Add to Array button followed by the Next button. Under the Expand Logical Drive tab, click Next followed by Finish to expand the capacity of your existing logical drive. If you want to add an additional logical drive to the existing configuration, click on the New Logical Drive button, select the RAID type of the new logical drive, followed by Next and Finish.
The Delete a Logical Drive Warning dialog box opens. Figure 70 Figure 70 Deleting a Logical Drive Type your Administrative password in the password field. Click OK. The logical drive is deleted. 5.8 Expanding an Array You can expand an existing array by adding physical drives to the array. The existing array can be expanded to a maximum of 16 drives.
The system drive to be expanded must be online and in Optimal state. The capacity of each of the added disk drives must be greater than or equal to that of the smallest disk drive in the RAID set. Using the enlarge system drive option, the system drive specified is enlarged as well as having its data striped across a larger number of physical disk drives. For this option, the system drive specified must be the only system drive on the pack of disk drives being migrated.
Figure 71 Manual Storage Configuration: Expand Logical Drive Select which physical drives you want to add to the Array. Click Next to move to the Create Logical Drive tab. If a logical drives exists on the array, you have two options: Leave the existing logical drives unchanged. Add one new logical drive. Go to the Create Logical Drive tab if you wish to create a new logical drive. See Figure 65 Manual Storage Configuration: Create Logical Drive Tab on page 95 for detailed configuration information.
In the navigation area, right-click on the Array that you want to delete or select Array->Delete from the menu. Select Delete. The Delete an Array Warning dialog box opens. Figure 72 Delete an Array Type your Administrative password in the password field. Click OK. The array and its contents are deleted. 5.10 Restoring a Controller Configuration from a Previously Saved File Restoring a configuration downloads a previously-saved controller configuration from a file on the server to the controller.
Figure 73 Restore Controller Configuration The Restore Controller Configuration dialog box opens. Figure 74 Restore Controller Configuration Dialog Box Select the configuration file that you want to restore. CAUTION: Restoring a controller configuration to an already-configured controller can cause loss of data. Click Open.
The Summary tab of the Manual Configuration Wizard opens. The tab shows the configuration that you are about to restore. Figure 75 Figure 75 Restore Configuration Summary Tab Click Finish to restore your configuration. Click Cancel to keep the existing configuration. 5.11 Backing Up a Controller Configuration Backing Up a configuration saves a controller configuration to the server.
Figure 76 Figure 76 Backup Controller Configuration In the Backup Configuration dialog box Figure 77 Backup Controller Configuration Dialog Box on page 108 type a name for the configuration file you want to save to the controller. Figure 77 Backup Controller Configuration Dialog Box Click Save to save the configuration file.
Chapter 6 Monitoring Activities This section describes the following monitoring activities that Spheras Storage Director performs: • 6.1 Monitoring All Servers on page 109 • 6.2 Monitoring Events on page 109 • 6.3 Monitoring a Controller on page 113 (monitoring controller activity, reviewing controller configuration) • 6.5 Physical Disk and Logical Drive Monitoring on page 117 (reviewing physical device and logical drive information, and locating arrays) • 6.
Figure 78 Selecting Events to View Events display in the content area of Spheras Storage Director and can be any of the following. See 4.2 Status Icons on page 57 for a description of the icons representing the event status: • • • Informational or Optimal (level 5) • An informational message showing a good status and no action is required. • Resources in an Optimal state are considered protected.
Note: On Linux operating systems, the event log time-stamps may become off by one hour due to daylight saving time. For details on how the Linux system clock works, see www.tldp.org/HOWTO/mini/Clock-2.html • The controller where the event originated • The controller address • The event ID number • The event description 6.2.2 Viewing Event Details The Event Details dialog box displays event information for a single event.
Figure 80 Event Details Dialog Box The Event Details dialog box displays information about the selected event. The information includes if applicable (not shown in Figure 80 Event Details Dialog Box on page 112), the serial number of the physical drive and the World Wide Name of an enclosure. The Previous button changes the content of the display to the event that is earlier (downward) in the log. The Next button changes the display to the event that is later (upward) in the log.
1 Click Event -> Event Filter from the menu bar. Figure 81 Select Event Filter The Event Filer dialog box opens (Figure 82 Event Filter Dialog Box on page 113). Figure 82 2 Event Filter Dialog Box Check or uncheck the event types to display and click OK. The events displayed in the content area are refreshed. The Event Filter settings are only saved for the current session. If you log out and log back onto the Client, your filter settings are lost. 6.2.
Figure 83 Monitoring a Controller (text view) Figure 84 Monitoring a controller (physical view) The content area displays all of the components of the controller including events related to the controller. The content area displays the information either in the Text View or the Physical View.
To get information about all controllers that are connected to a particular server, click on Controllers in the navigation area. This view displays the following information in the content area: • The name of each controller. • The model of each controller. • The mode of each controller: simplex, duplex, or failover. • The mode of the cache: normal or conservative cache. • The status of each controller (determined by the most severe status of the controller itself or its components).
Figure 85 Displaying Array Information (physical view) The content area displays array information either in the Text View or the Physical View. Both views contain the following information: • The array number. • The number and total capacity of the logical drives defined on the array. • The number and total capacity of the physical drives on the array. • The status of components in the array.
Figure 86 Select Array Properties • The most severe status of any logical drive in the array. • The number of physical drives in the array. • The number of logical drives in the array. • The total capacity of the array. • The total amount of used and unused space held by this array. 6.5 Physical Disk and Logical Drive Monitoring This section describes how Spheras Storage Director monitors physical disks and logical drives. 6.5.
Figure 87 118 Displaying Physical Drive Information (text view) Spheras Storage Director Installation and User Guide
Figure 88 Displaying physical drive information (physical view) The content area displays the physical drive information in either the Text View or the Physical View. If you are displaying the information using the Text View, the content area displays information about the physical drive including name, capacity, enclosure, channel, ID, and Status (see Figure 87 Displaying Physical Drive Information (text view) on page 118).
Figure 89 Physical Drive Properties Dialog Box The Physical Drive Properties dialog box displays the following information: • The current status of the disk (online, rebuilding, failed, or suspected failed) • The drive channel negotiated transfer speed (MB/second) • The negotiated drive channel bus width (in bits) • The drive channel • Loop ID number • The associated enclosure number where the disk resides • The physical capacity of the disk device • The vendor or source of the drive • Th
• The ANSI version supported • Whether the following parameters are set to Yes or No: Linked Commands, and Command Queuing • The maximum data transfer width (in bits) 6.5.2 Displaying Logical Drive Information To monitor activities on a logical drive, select a logical drive from the navigation area. Figure 90 Displaying Logical Drive Information (text view) The content area displays the logical drive information. In the text view, the following information is displayed about the logical drive.
There are two ways to view information about a specific logical drive: • Select a logical drive in the navigation area and view the information in the content area • Click Logical->Properties from the menu bar. Figure 91 Logical Drive Properties The Logical Drive Properties dialog box opens and displays information about the logical drive, see the previous information for a description of the contents. You can also enable or disable the write cache using the checkbox on this dialog.
• The host access of each logical drive. • The capacity or each logical drive. • The status of each logical drive. • The RAID level of each logical drive. • Whether write back cache is enabled or disabled for each logical drive. • The stripe size of each logical drive. • The array number where each logical drive resides. Click on an individual logical drive to view its information. 6.
Figure 93 Figure 93 Individual Enclosure Information When a specific enclosure is selected, the following is displayed: • • • • • 124 Alarms: • Name and icon • Status: Element Not Present, Optimal, Warning or Failed • Current details: blank or Alarm On • Description Fans: • Name and icon • Status: Element Not Present, Optimal, Critical, or Failed • Current details: Fan stopped, Speed: Low, or Speed: High • Description Power Supplies: • Name and icon • Status: Element Not Present,
• Description To view Enclosure Properties and change the temperature thresholds, click Enclosure->Properties. Figure 94 • Viewing Enclosure Properties The Enclosure Properties dialog box opens and displays Figure 94 Viewing Enclosure Properties on page 125. Notes: 1 When you make changes to the Enclosure Properties it takes a few minutes before the changes are displayed. 2 If the SSD server is unable to retrieve the information from the controller, the default values are displayed.
6.7 Monitoring the Battery Backup Unit The optional Battery Backup Unit (BBU) maintains memory content in the presence of an ac power failure. The principal purpose of the BBU is to provide stable memory power during ac power glitches and short power outages, however, the BBU is capable of sustaining memory content for an extended period. The length of memory power backup is dependent upon the cache memory size and the particular battery pack used by the BBU.
Figure 96 BBU Properties Dialog Box The BBU Properties dialog box opens and the following information is displayed. • The status of the BBU is: • Optimal • Low Power • Fast Charging • Discharging • Recondition Needed • Recondition (Fast Charging) • Recondition (Discharging) • Recondition Active • The current power level of the battery expressed as hours or minutes of charge. This value changes as the battery is discharged or charged.
6.8 Monitoring Long Operation Tasks To monitor long operation tasks, select the Task Monitor from the navigation area. Figure 97 Task Monitoring The in progress tasks are displayed in the content area. The following task types are displayed.
6.9 Server View The server view displays the following information: The name of the server’s components: events and controllers. The number of events and controllers on this server. The status of the controllers on this server, either optimal, warning, serious, or critical. The description of the components on this server.
The following controller events could occur: Event ID 388 Type of Event Critical 389 Warning Controller has been reset. Check the controller’s configuration and restore as necessary. (Resetting a controller may cause loss of data or loss of access to data.) 390 Informational Controller is found. Nothing. 391 Critical Controller is gone. System is disconnecting Replace the controller and apply a from this controller. configuration. 395 Critical Controller is gone.
Usually a non-optimal logical drive or physical device failure. User action is needed to prevent data loss or loss of access to data. User may need to replace hardware. Resources in a serious state should be considered Vulnerable according to RAB guidelines. 6.9.4.3 Warning Icon: An error has occurred that did not cause data loss, usually a software error. User may need to retry a command. 6.9.4.
3 4 5 6 7 8 Table 2 132 Name MLXEV_PHYSDEV_HARD_ERROR Description Physical disk error found. Cause A bad sector was found on the physical disk. Mechanical failure on the physical disk. Host SCSI device detected illegal instruction. Target device generated unknown phase sequence. Action If problem occurs frequently: – Replace the physical disk. – Contact your service representative.
9 Name Description Cause Action Address Severity Source Name Description Cause 10 Action Address Severity Source Name Description Cause 11 Action Address Severity Source Name Description Cause 12 Action Address Severity Source Name Description Cause 13 Action Address Severity Source Name Description Cause 14 Action Address Severity Source Table 2 MLXEV_PHYSDEV_REBUILD_ERROR Rebuild stopped with error. Due to some unknown error on the controller, rebuild failed. Try rebuild again.
15 16 17 18 19 20 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Table 2 134 MLXEV_PHYSDEV_UNCONFIGURED A previously configured disk is now available. User set the physical device to unconfigured.
21 Name MLXEV_PHYSDEV_COMMAND_RETRIED Description SCSI command retried on physical disk. Cause The command may have timed out. Bus reset may have occurred. Device reset may have occurred. Action None Address ctl: 0 chn: 13 tgt: 14 Severity 3 (Warning) Source InP_old Name MLXEV_PHYSDEV_PARITY_ERROR Description Parity error found. Cause A physical device did not generate proper parity. The controller failed; did not check parity properly. Cable failed. Improper cable length.
26 27 28 29 30 31 Table 2 136 Name MLXEV_PHYSDEV_ACTIVESPARE Description Active spare found. Cause Physical disk was configured. Manual active spare was done. Automatic active spare was done Action None Address ctl: 0 chn: 13 tgt: 14 Severity 4 (Information) Source InP_old Name MLXEV_PHYSDEV_WARMSPARE Description Warm spare found. Cause Physical disk was configured. Manual warm spare was done. Automatic warm spare was done.
32 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source 33 34 35 36 37 38 Table 2 MLXEV_PHYSDEV_INIT_CANCELED Initialization canceled. User cancelled the operation.
39 40 41 42 43 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Cause Action Address Severity Source Name Description MLXEV_PHYSDEV_SCSITMO_DEAD A physical disk failed because a command to the disk timed out. SCSI command timed out on the device. Replace physical disk and rebuild it. ctl: 0 chn: 13 tgt: 14 1 (Serious) InPro MLXEV_PHYSDEV_SYSRESET_DEAD A physical disk failed because of the system reset.
46 Name MLXEV_PHYSDEV_NOTRDY_DEAD Description A physical disk failed because device is not ready. Cause Physical disk not spinning, just turned bad. Power to the physical disk failed. Action Replace physical disk and rebuild it. Check power and rebuild device. Address ctl: 0 chn: 13 tgt: 14 Severity 1 (Serious) Source InPro Name MLXEV_PHYSDEV_MISSING_DEAD Description A physical disk failed because the physical disk was not found on start up. Cause Physical disk not connected. Physical disk not responding.
52 53 54 55 56 57 58 Table 2 140 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source MLXEV_PHYSDEV_REBUILD Physical disk status changed to rebuild.
59 Name Description Cause Action Address Severity Source Name Description Cause Action 60 Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause 61 62 Action Address Severity Source Name Description Cause 63 Action Address Severity Source Name Description Cause 64 Action Address Severity Source Table 2 MLXEV_PHYSDEV_MOVING_TO_OTHER_CHN Physical disk is switching from one channel to the other channel.
65 66 Name MLXEV_PPILOT_LOGICAL_DISK_PATH_FAILOVER Description A storage access path has shifted to the alternate path. Cause PATHpilot is unable to access storage on the original path, but is able to use the alternate path. A PATHpilot failover has occurred. Action Investigate possible causes (such as cabling, controller failure, HBA failure).
70 Name MLXEV_PHYSDEV_PORT_FAILED Description Physical disk port has failed or cannot operate at the configured channel speed. Cause Physical disk hardware failure. Physical disk is not compatible with system. Enclosure disk slot hardware failure. Action Replace physical disk. Replace disk enclosure. Address ctl: 0 chn: 13 tgt: 14 Severity 2 (Error) Source ExPro Name MLXEV_CTLDEV_MIRROR_RACE_ENTRY_FAILED Description Mirror race recovery failed for logical drive.
76 77 78 79 80 Name MLXEV_CFG_COD_DROPPED Description A COD with unsupported features has been detected. Cause Firmware does not support certain features in that COD. COD import is to wrong system. Action COD data is sequestered. Obtain compatible firmware then reimport the COD or import the COD to a different system. Address ctl: 0 Severity 4 (INFORMATION) Source InPro Name MLXEV_CTLDEV_BBU_NEW_BATTERY Description New battery found.
81 Name MLXEV_SYSDEV_REBUILD_FAILED_ON_PARTNER Description Rebuild stopped on controller failure. Cause Rebuild moved to the surviving controller because the partner, which was running the rebuild, failed. Action None. Address ctl: 0 logdrv: 15 Severity 4 (Information) Source ExPro Name MLXEV_SYSDEV_CHECK_CONSISTENCY_FAILED_ON_ PARTNER Description Check Consistency stopped on controller failure. Cause Check Consistency failed because the partner, which was running the Check Consistency, failed.
86 Name Description Cause Action 87 Address Severity Source Name Description Cause Action 88 89 Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action 90 Address Severity Source Name Description Cause Action Address Severity Source Table 2 146 MLXEV_CFG_COD_GROUP_NOT_INSTALLED_LDD_ USED Configuration group not installed due to logical drive conflict. Logical drive already configured in another group.
91 Name MLXEV_PPILOT_PRIMARY_DISK_NOT_FOUND Description A primary logical drive was not found during initialization. Cause PATHPilot reported a primary logical drive was lost during power cycle. Action Investigate possible causes such as cabling, controller failure, or HBA failure. Address PATHpilot: Last HBTL: 12,13,14,15 Severity 3 (Warning) Source PATHpilot Name MLXEV_PPILOT_NO_PATH_FOR_LD_FOUND Description No paths were found for a logical drive during initialization.
97 98 99 100 101 Table 2 148 Name MLXEV_PHYSDEV_TRANSPORT_ERROR Description One or more transport errors occurred during data transfer to or from a physical device in the last hour. Cause Fibre Channel CRC errors were detected by the controller or a physical device during the last hour. Physical devices were installed or removed causing momentary Fibre Channel loop disruption. Physical devices are not properly seated in the enclosure.
102 Name MLXEV_SYSDEV_PFA_STOP Description Finished predicted failure analysis on every physical disk. Cause Controller finished predicted failure analysis on the physical disks. Action Address Severity Source Name Description Cause Action Address Severity Source Name Description None ctl: 0 4 (Information) ExPro MLXEV_SYSDEV_BKGND_PATROL_START Background patrol started or was resumed. Background patrol started.
132 133 134 135 136 137 138 Table 2 150 Name MLXEV_SYSDEV_CHECK_SYSDEV_FAILED Description Consistency check on logical drive failed. Cause A logical device became critical. A logical device failed. Action See request sense data for more information. Address ctl: 0 logdrv: 15 Severity 2 (Error) Source ExPro InPro Name MLXEV_SYSDEV_CHECK_PHYSDEV_FAILED Description Consistency check failed due to physical disk failure. Cause A physical disk failed. Action See request sense data for more information.
139 Name Description Cause Action Address Severity Source Name Description Cause MLXEV_SYSDEV_REBUILD_DONE Rebuild on logical drive is over. Rebuild completed successfully only for this logical drive. None ctl: 0 logdrv: 15 4 (Information) InPro MLXEV_SYSDEV_REBUILD_CANCELED Rebuild on logical drive has been cancelled. User cancelled rebuild. Higher priority rebuild started. Action Restart the rebuild if required.
146 147 148 149 150 151 Table 2 152 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source MLXEV_SYSDEV_INIT_CANCELED Logical drive initialization cancelled. User cancelled the initialization. Restart initialization if required.
Name Description Cause Action Address Severity Source Name Description Cause 153 Action Address Severity Source Name Description Cause 154 Action Address Severity Source Name Description Cause 155 Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause 156 157 158 Action Address Severity Source Table 2 MLXEV_SYSDEV_EXPANDCAPACITY_ERROR Expand capacity stopped with error.
159 Name MLXEV_SYSDEV_DATA_FOR_BLOCK_LOST Description Data for disk block has been lost due to logical drive problem. Cause Data retained in RAID cache for a Write-Back Logical Drive cannot be stored to the physical medium because of logical drive problem. The logical drive problem might be caused by multiple physical medium errors, multiple physical devices offline, or other reasons.
178 Name MLXEV_SYSDEV_BG_INIT_PAUSED Description Logical drive background initialization paused. Cause Background initialization paused due to a higher priority operation.
258 259 272 273 274 275 Table 2 156 Name MLXEV_AEMI_FAN_FAILED Description Fan failure. Cause Cable connection is broken. Fan failure. Action Replace fan. Address ctl: 0 chn: 13 tgt: 14 Fan: 15 Severity 1 (Serious) Source InP_old Name MLXEV_FMTFAN_NOTPRESENT Description Storage cabinet fan is not present. Cause Enclosure management connection is broken. Management hardware failure. Fan is not present. Action Refer to the enclosure manufacturer’s service manual.
288 Name MLXEV_FMTHEAT_BAD Description Over temperature. Temperature is above 70 °C. Cause Room temperature is too high. Fan failure. Sensor failure. Action Turn off the system and let it to cool down. Adjust the room temperature. Address ctl: 0 chn: 13 tgt: 14 Heat Sensor: 15 Severity 1 (Serious) Source InP_old Name MLXEV_FMTHEAT_CRITICAL Description Temperature is above 50 °C. Cause Room temperature is high. Fan failure. Action Replace fan. Turn off the system. Adjust the room temperature.
305 306 307 308 309 310 311 Table 2 158 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source MLXEV_FMTSTWK_CRITICAL Storage Works enclosure reported critical state.
320 Name MLXEV_ENCLFAN_FAILED Description Fan failure. Cause Cable connection broken. Fan failure Action Replace fan. Address ctl: 0 enclosure: 13 unit: 14 Severity 1 (Serious) Source ExPro InPro Name MLXEV_ENCLFAN_OK Description Fan has been restored. Cause Faulty fan has been replaced. Cable is connected properly. Action None Address ctl: 0 enclosure: 13 unit: 14 Severity 4 (Information) Source ExPro InPro Name MLXEV_ENCLFAN_NOTPRESENT Description Fan is not present.
326 327 328 329 330 331 Table 2 160 Name MLXEV_ENCLHEAT_BAD Description Temperature is over safe limit. Failure imminent. Cause Room temperature is too high. Fan failure. Sensor failure. Action Turn off the system and let it to cool down. Adjust the room temperature. Address ctl: 0 enclosure: 13 unit: 14 Severity 1 (Serious) Source ExPro InPro Name MLXEV_ENCLHEAT_CRITICAL Description Temperature is above working limit. Cause Room temperature is too high. Fan failure.
332 Name MLXEV_ENCLACCESS_OFFLINE Description Enclosure access is offline. Cause Enclosure management connection is broken. Management hardware failure. Action Refer to enclosure manufacturer’s service manual. Address ctl: 0 enclosure: 13 Severity 1 (Serious) Source ExPro InPro Name MLXEV_ENCLSES_SOFTADDR_OCCURRED Description Enclosure soft addressing detected. Cause Enclosure has duplicate loop IDs (soft addressing). Potential data corruption. Action Refer to enclosure manufacturer’s service manual.
338 339 340 384 385 386 Table 2 162 Name MLXEV_ENCLOSURE_SHUTDOWN Description Physical disks in enclosure are being spundown. Cause Enclosure temperature is too high. Fan failure. Sensor failure. Action Turn off the enclosure and repair the problem causing the critical overtemperature condition. After the problem is repaired, recover by power cycling the entire system including the controllers.
388 Name Description Cause Action Address Severity Source Name Description Cause Action 389 Address Severity Source Name Description Cause 390 Action Address Severity Source Name Description Cause 391 Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source 392 393 394 Table 2 MLXEV_CTLDEV_DEAD Controller is dead. System is disconnecting from this controller.
395 396 397 398 399 400 401 Table 2 164 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source MLXEV_CTLDEV_POWER_OFF Controller is gone.
402 403 404 405 406 407 408 Table 2 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause MLXEV_CTLDEV_BBU_RECOND_ABORT Battery reconditioning is canceled. User cancelled the battery reconditioning. Restart the battery reconditioning, if required.
409 410 411 Name Description Cause Action Address Severity Source Name Description Cause MLXEV_CTLDEV_BBU_CALIBRATE_ABORT Battery calibration cycle was canceled. User canceled the battery calibration cycle. None ctl: 0 4 (Information) ExPro MLXEV_CTLDEV_BBU_NO_BATTERY Battery is not present. The battery electronics are present, but a battery was not detected. Action Address Severity Source Name Description Cause Install or connect the battery.
412 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause 413 414 415 416 417 418 Action Address Severity Source Table 2 MLXEV_CTLDEV_NORMAL_CACHE_MODE Controller entered normal cache mode.
419 Name Description Cause Action Address Severity Source Paramtype Params MLXEV_CTLDEV_UPDATE_PTNR_STATUS Updated partner's status.
423 Table 2 Name Description Cause Action Address Severity Source Paramtype Params MLXEV_CTLDEV_KILL_PTNR Disabled partner. – Refer to enclosure manufacturer’s service manual.
423 (Cont) 424 425 426 Table 2 170 Params 0x0310 : name_WBSYNCH_CHAN0 : “Write-back sync to partner chan 0” 0x0311 : name_WBSYNCH_CHAN1 : “Write-back sync to partner chan 1” 0x0312 : name_WBSYNCH_CHAN2 : “Write-back sync to partner chan 2” 0x0313 : name_WBSYNCH_CHAN3 : “Write-back sync to partner chan 3” 0x0314 : name_WBSYNCH_CHAN4 : “Write-back sync to partner chan 4” 0x0315 : name_WBSYNCH_CHAN5 : “Write-back sync to partner chan 5” 0x0316 : name_NEGOTIATE_FWBUILD : “FW build mismatch” 0x0317 : name
427 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause 428 429 Action Address Severity Source Name Description Cause 430 Action Address Severity Source Name Description Cause 431 Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action 432 433 Address Severity Source Table 2 MLXEV_CTLDEV_MIRROR_RACE_RECOVERY_FAILED Mirror race recovery failed.
434 435 436 437 438 439 Table 2 172 Name MLXEV_CTLDEV_NEGOTIATION_SAME_ID Description Dual-active negotiation failed IDs. Cause Controller IDs are not unique. Both controllers have the same ID. Action Replace, adjust, or add components so that the controllers have the correct IDs. Address ctl: 0 Severity 2 (Error) Source ExPro Name MLXEV_CTLDEV_NEGOTIATION_BOARD_TYPE Description Dual-active negotiation failed board types. Cause Board types differ. Both controllers must be of the same type.
440 Name MLXEV_CTLDEV_MIRROR_RACE_TABLE_ERROR Description Error in mirror race table. Cause Logical drives appear in the mirror race table that do not exist in the configuration. Possible data integrity issue. Action Check configuration for accuracy, run consistency check and restore consistency. Address ctl: 0 logdrv: 15 Severity 1 (Serious) Source ExPro Name MLXEV_CTLDEV_STOP_REJECTED Description A replacement controller attempted to stop the surviving controller.
517 518 519 520 521 522 640 Table 2 174 Name MLXEV_SYSTEM_DEAD Description Lost connection to the server or server is down. Cause Lost network connection to the server. Server shutdown. Action None Address None Severity 1 (Serious) Source Client Name MLXEV_AUTOBOOT_CHANGED Description Automatic reboot count has changed. Cause Controller has rebooted. Automatic reboot has rearmed itself or was reconfigured.
641 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source 642 643 644 645 700 701 Table 2 MLXEV_CHANNEL_OK Channel online. Cable reconnected. None.
702 703 800 801 802 803 804 Table 2 176 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source MLXEV_LOG_REQUEST_SENSE Request sense. A physical disk has generated an error.
805 806 807 808 809 Name Description Cause Action Address Severity Source Name Description Cause Action Address Severity Source Name Description Cause MLXEV_CFG_COD_IMPORT_FAILED Configuration on disk import failed. The controller could not import the configuration. None ctl: 0 3 (Warning) ExP_old MLXEV_DEBUG_DUMP_GENERATED A debug dump exists on this system. The controller aborted and created debug dump information. Contact field support for assistance in retrieving the data.
896 Name Description Cause Action Address Severity Source Paramtype Params Table 2 178 MLXEV_FATAL_HANG Internal controller is hung. Internal controller is hung. Power controller off and on. ctl: 0 version: 13.
Params Table 2 0x80000024 : name_FATAL_HANG_80000024 : “Fatal Hang COD_ Write Data Contest size is greater than Scratch space” 0x80000025 : name_FATAL_HANG_80000025 : “Fatal Hang COD_ Invalid Read/Write Data Area Code.
Params Table 2 180 0x80000095 : name_FATAL_HANG_80000095 : “Fatal Hang FW_ R5 Check Consistency - Bad Memory Status” 0x80000096 : name_FATAL_HANG_80000096 : “Fatal Hang FW_BOOT_ No NIOP” 0x80000097 : name_FATAL_HANG_80000097 : “Fatal Hang FW_ Unimplemented opcode” 0x800000A1 : name_FATAL_HANG_800000A1 : “Fatal Hang EBHW_ SDRAM status Bad” 0x800000A2 : name_FATAL_HANG_800000A2 : “Fatal Hang EBHW_ SDRAM no Memory” 0x800000B1 : name_FATAL_HANG_800000B1 : “Fatal Hang EBHW_ No NIOP” 0x800000B2 : name_FATAL_HA
Params Table 2 0x800000E3 : name_FATAL_HANG_800000E3 : “Fatal Hang I960HWXOR _ Bad Address” 0x800000E8 : name_FATAL_HANG_800000E8 : “Fatal Hang FW_HW Board Model Not supported” 0x800000E9 : name_FATAL_HANG_800000E9 : “Fatal Hang FW_ Memory Size not supported” 0x800000F4 : name_FATAL_HANG_800000F4 : “Fatal Hang FW_ Bad Memory Allocation” 0x800000F5 : name_FATAL_HANG_800000F5 : “Fatal Hang FW_ Bad Memory Status” 0x800000F6 : name_FATAL_HANG_800000F6 : “Fatal Hang FW_ Bad Memory Unlock” 0x800000F7 : name_FAT
Params Table 2 182 0x80000122 : name_FATAL_HANG_80000122 : “Fatal Hang SMQS_ Active Q length 0 - Resume IO” 0x80000131 : name_FATAL_HANG_80000131 : “Fatal Hang TBBU_ Bad LC link End” 0x80000132 : name_FATAL_HANG_80000132 : “Fatal Hang TBBU_ Bad Memory Size” 0x80000133 : name_FATAL_HANG_80000133 : “Fatal Hang TBBU_ No Memory to allocate” 0x80000134 : name_FATAL_HANG_80000134 : “Fatal Hang TBBU_ Unexpected Dirty Lines” 0x80000141 : name_FATAL_HANG_80000141 : “Fatal Hang BBU_ Bad Read Status” 0x80000142 : n
Params Params Table 2 0x80000217 : name_FATAL_HANG_80000217 : “Fatal Hang HWISP_ NULL DP8031” 0x80000218 : name_FATAL_HANG_80000218 : “Fatal Hang HWISP_ NULL DP8032” 0x80000219 : name_FATAL_HANG_80000219 : “Fatal Hang HWISP_ NULL DP8033” 0x8000021A : name_FATAL_HANG_8000021A : “Fatal Hang HWISP_ NULL DP8034” 0x8000021B : name_FATAL_HANG_8000021B : “Fatal Hang HWISP_ NULL DP8035” 0x80000220 : name_FATAL_HANG_80000220 : “Fatal Hang HWISP_ Stale Entry 0x80000221 : name_FATAL_HANG_80000221 : “Fatal Hang HWIS
897 Name Description Cause Action Address Severity Source Paramtype Name Description Cause Action Address Severity Source Paramtype Params MLXEV_FATAL_BRKP Internal controller firmware breakpoint. Internal controller has encountered a firmware breakpoint. Power controller off and on. ctl: 0 version: 13.14 – 15 param: 0x23222120 1 (Serious) InPro value MLXEV_I960_HW_ERROR Internal controller i960 processor error. Internal controller has encountered i960 processor specific error.
Chapter 7 Maintenance Activities Maintenance processes include the following activities, that you may need to perform on arrays: • 7.1 Running a Logical Drive Initialization on page 185 • 7.2 Running a Logical Drive Consistency Check on page 186 • 7.3 Running a Manual Rebuild on page 187 • 7.4 Disk Scrubbing on page 188 • 7.5 Editing a WWN Table on page 188 • 7.6 Forcing a Physical Drive Online or Offline on page 189 • 7.
1 Select a logical drive from the navigation area or the content area. 2 Click Logical->Initialize from the menu bar. Figure 98 Logical Drive Initialization Warning A Warning dialog box displays telling you that this process is data-destructive. 3 Type your password. 4 Click OK to confirm the initialization. 5 See 6.8 Monitoring Long Operation Tasks on page 128 to monitor the progress of your initialization or cancel it. 7.
1 Select a logical drive from the navigation area or the content area. 2 Click Logical->Check Consistency from the menu bar. Figure 99 Logical Drive Consistency Check A Warning dialog box displays telling you that this process could result in data loss. 3 Select the Automatically reconstruct data if errors are found checkbox if desired. CAUTION: Using this option can result in data loss. 4 Type your password. 5 Click OK to confirm the consistency check. 6 6.
1 Remove and replace the failed disk drive. 2 Allow sufficient time for the new disk drive to spin up. The drive should appear in an Un-configured state. 3 To rebuild an array, click Array->Rebuild. A message dialog box opens to confirm that the drive rebuild is in progress. 4 Click OK to complete the drive rebuild. 7.4 Disk Scrubbing Note: Disk scrubbing is not available on all RAID controller firmware versions.
1 Click Controller->Edit WWN Table. The Edit WWN Table opens. Figure 100 Edit a WWN Table The WWN Table displays entries (WWN and Host Name) for every host that has ever accessed the controller. 2 Select the WWN that you want to delete. 3 Click OK. The disconnected hosts that you selected are removed from the table. Note: The controller does not allow the user to delete entries for hosts that are connected. The controller takes a few minutes to recognize this change.
1 Select the physical drive that you want to force online/offline. 2 Click Physical->Force Online or Physical->Force Offline on the menu bar or right-click Physical drive->Force Online/Offline. An information dialog box opens telling you that the physical drive you have selected is now online/offline. The dialog box also displays the ID number of the physical drive. Figure 101 3 7.7 Forcing a Physical Drive Online/Offline Information Dialog box Click OK.
4 Click OK. To locate an enclosure, select the enclosure in the navigation area and select Locate from the Enclosure pull-down menu. 7.8 Updating a Controller’s Firmware The firmware update utility is used to update firmware by “flashing” the new code stored in a specified .ima file to the on-board flash memory. As maintenance releases of the firmware become available, this utility allows you to keep your controller current. Note: Updating controller firmware requires the controller to reboot.
2 Type your password. 3 Click OK. The Update Firmware dialog box opens. Figure 104 4 Firmware Update Type the name of the appropriate image file (.ima) in the “New firmware image file on field,” or click Browse to locate the file. Note: Spheras Storage Director does not impose any length limitation on the file path. If you select Browse, the Open Image file dialog box is displayed, see Figure 105 Open Image File Dialog Box on page 193.
Figure 105 Open Image File Dialog Box © 2003, Adaptec, Inc.
5 Navigate to and select the image file name. 6 Click Open. The .ima file name is displayed in the “New firmware image file on” field. The details of the firmware file are displayed in the “New firmware image information” field. Figure 106 Upgrade Firmware Details 7 Click OK. 8 A warning message, “This firmware update requires the controller to reboot. The reboot takes approximately 30 seconds to complete. Any I/O must be stopped.” is displayed. 9 Click Yes to complete the firmware update.
1 In the navigation area right-click the BBU -> Recondition or select BBU -> Recondition Battery. 2 An information dialog box opens confirming that the battery is now being reconditioned and to check the Task Monitor to view the status. Figure 107 Reconditioning a Battery Information Dialog Box 3 Click OK. 4 Open the Task Monitor to view the status of the recondition. See 6.8 Monitoring Long Operation Tasks on page 128 for more information about the Task Monitor. 7.
1 Click Controller->Shutdown on the menu bar. The Controller Shutdown Warning dialog box opens. Figure 108 Controller Shutdown Warning Dialog Box 2 Type your Administrative password in the password field. 3 Click OK. The controller can be physically powered off when its status changes to Shutdown. See the Task Monitor to view the progress. 7.11 Repair Actions • 7.11.1 General Repairs on page 196 • 7.11.2 Repair an Array on page 197 • 7.11.3 Repair a Logical Drive on page 197 • 7.11.
Remember that some events are the result of other events; one event can cause a cascade of others if left unfixed. For example, a problem with a hard drive causes a warning event, “Hard drive error found”, which could lead to a consistency check error event, “Consistency check on logical drive error”, which could lead to a serious event, “A hard disk has failed”, which could lead to a critical event, “A logical drive has failed.” 7.11.
• If expanding a logical drive, make sure that the logical drive and physical drives can support the expansion. See 5.6 Expanding a Logical Drive on page 100 for more information. 7.11.4 Repair a Controller To repair a controller, first see 6.2.2 Viewing Event Details on page 111. The event details tell you the event ID and give you a description of the event that caused the controller to need repair.
To repair an enclosure, first see 6.2.2 Viewing Event Details on page 111. The event details tell you the event ID and give you a description of the event that caused the enclosure to need repair. Using this information, take measures to fix the problem: • If the BBU needs to be reconditioned or power is low, recondition the BBU. • Remove access to the enclosure and power down. • Check, all cable connections, to be sure none is disconnected or broken. • Replace any parts that need to be replaced.
200 Spheras Storage Director Installation and User Guide
Appendix A Manually Configuring HTTP Servers For information about manually configuring HTTP servers, see the PDF version of the eArray Director Software: Installation and User’s Guide located on the distribution CD ROM. Note: Use the procedures in this section if you elected not to have your HTTP server automatically configured during installation of the Spheras Storage Director server or if you have trouble with your HTTP server. Refer to the following sections: A.
Alias /SSD/ "{your path}" Windows example: Alias /SSD/ "C:/Program Files/Adaptec/Spheras Storage Director Server/discreet/dsm/" The alias allows your machine to access the Spheras Storage Director Server and launch the Spheras Storage Director Client. In the example above, replace the text {your path} with the full path where Spheras Storage Director Server has been installed on your system.
Figure 109 Internet Information Services Internet Information Services Dialog Box Locate your web sever in the left pane, in this example it’s called Default Web Site, Figure 110 IIS – Selecting a new virtual directory on page 203. Right-click Your Web Server->New->Virtual Directory. Figure 110 IIS – Selecting a new virtual directory Select a New Virtual Directory The Virtual Directory Creation Wizard Welcome Window opens. © 2003, Adaptec, Inc.
Figure 111 Virtual directory creation welcome screen Virtual Directory Creation Wizard Welcome Dialog Box Click Next. The Virtual Directory Alias dialog box opens.
Figure 112 Spheras storage director alias Virtual Directory Alias Type an Alias for the Spheras Storage Director. The path will be the destination folder of your Spheras Storage Director Server, see Figure 113 Web site content directory on page 206. Click Next. The Web Site Content Directory dialog box opens. © 2003, Adaptec, Inc.
Figure 113 Web site content directory Web Site Content Directory In the Directory field, type the path; or click Browse to navigate to the directory. The path will be the destination folder of your Spheras Storage Director Server. See Figure 113 Web site content directory on page 206, for an example of a path. Click Next. The Access Permissions dialog box opens.
Figure 114 Virtual directory access permissions Select Access Permissions Select the Read option. This is the only option required by Spheras Storage Director. Select other options if desired. Click Next. © 2003, Adaptec, Inc.
Figure 115 Virtual directory creation complete screen Complete Your Virtual Directory Creation Click Finish. The Microsoft IIS HTTP Web Server manual configuration is complete. Refresh the Microsoft IIS HTTP Web Server. Go to the Control Panel and launch the Services dialog box. Locate “IIS Admin Service” and click Stop, then click Start. Alternately, you can use the Internet Services Manager to stop and restart your HTTP server. A.1.
# # We include the /icons/ alias for FancyIndexed directory listings. If you # do not use FancyIndexing, you may comment this out. # Alias /icons/ “/usr/local/apache/icons/” # Important: keep this line here Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all You must type the Alias exactly at the location it appears in the previous step.
./apachectl stop then type ./apachectl start The Apache HTTP Web Server manual configuration is complete. A.1.4 Solaris - Manually Configuring an Apache HTTP Web Server In order for the Spheras Storage Director Client to interact with the Spheras Storage Director Server, an HTTP server must be installed on a minimum of one server.
# this, ask your network administrator. # If your host doesn’t have a registered DNS name, enter its IP address here. # You will have to access it by its address (e.g., http://123.45.67.89/) # anyway, and this will make redirections work in a sensible way. # ServerName Modify this variable by typing in your IP address or DNS name here. If this variable is not changed, the Apache server will use it’s own IP address (127.0.0.1) and run as a loop back server.
Figure 116 Apache Installation The Apache HTTP Web Server manual configuration is complete.
Appendix B Detailed Information About Configurations For information about selecting the best configuration for your system, see the PDF version of the eArray Director Software: Installation and User’s Guide located on the distribution CD ROM. To determine the best configuration for your system, you need to answer some questions and make some decisions about the type of configuration you need; what you can afford; and what components you have.
• Disk performance The controller makes the RAID implementation and the disks’ physical configuration transparent to the host operating system. This means the host operating system drivers and software utilities are unchanged, regardless of the RAID level selected. B.2 RAID Levels Selecting the proper RAID level for a specific data storage application requires consideration is given to the benefits of each technique.
With Spanning = RAID 30 Benefits: Provides for high transfer rate and high availability, at an inherently lower cost than mirroring. Drawbacks: Transaction performance is poor because all RAID Level 3 array member disks operate in lockstep. Drives: Minimum, 3. Maximum, 16. Fault Tolerance: Yes B.2.3 RAID 5: Striping with Parity The controller stripes blocks of data and parity information across all drives.
B.3 RAID Rules When connecting devices and configuring them to work with a RAID controller, follow this set of guidelines: • To lessen their impact on the SCSI bus, connect SCSI-based tape, CD-ROM and other non-disk devices on a single channel, which preferably does not service any disk drives • If using more than two drives, distribute them equally among all the channels on the controller. This results in better performance.
I want to emphasize performance _____ (see B.2 RAID Levels on page 214) I have ____ channels on the array controller (usually 1, 2, or 3). I plan to ___ /not to ____ use a Hot Spare disk. I do ____ /do not _____ have a battery backup for the controller cache. I do ____ /do not _____ have a UPS for the array. B.4.
Not Fault Tolerant Table 4 No fault-tolerant RAID levels are configured for any of the drives in the array. Maximum availability conditions An additional measure of fault-tolerance (or improved availability) is achieved using a Hot Spare (Standby) disk. This disk is powered-on but idle during normal array operation. If a failure occurs on a disk in a fault-tolerant set, the Hot Spare disk takes over for the failed drive.
B.6.1 Array Configuration Table: Overview Consider these points when using the tables: To determine the approximate capacity of a particular configuration, assume that each physical disk has a unit capacity of one. The value in the Effective Capacity column will indicate the effective available capacity for a Drive Group with a given RAID level. A configuration, is fault-tolerant or has enhanced availability, if there is an asterisk after the value in the Effective Capacity column.
A:o Table 6 A:JBOD A:1 Array configuration – One drive Array Configuration: Two Drives Drives and Drive Groups Possible RAID Levels A:o A:JBOD Effective Capacity A:1 B:o B:JBOD B:1 A:oo A:0 A:2 A:1 A:1* Table 7 Array configuration – Two drives Array Configuration: Three Drives Drives and Drive Groups Possible RAID Levels Effective Capacity A:o A:JBOD A:1 B:o B:JBOD B:1 C:o C:JBOD C:1 A:oo A:0 A:2 O A:1/SBY A:1** A:ooo A:5 Table 8 A:0+1 A:2 A:1:5* A:0 A:3 Array config
Array Configuration: Five Drives Drives and Drive Groups Possible RAID Levels Effective Capacity A:o A:JBOD A:1 B:o B:JBOD B:1 C:o C:JBOD C:1 D:o D:JBOD D:1 E:o E:JBOD E:1 A:oooo A:5/SBY A:3** O B:0+1/SBY A:2** A:oo A:0 A:2 B:oo A:1/SBY B:1** O B:0 B:2 B:1/SBY B:1** A:5 A:4* A:0+1 A:2.5* A:0 A:5 A:ooo A:5 A:2* B:oo A:0+1 A:1.
B:oo A:0+1 A:2 B:0 B:2 B:1 B:1* A:ooo A:5/SBY A:2** B:oo A:0+1/SBY A:1.5** O B:0 B:2 B:1 B:1* A:ooo A:5 A:2* B:ooo B:5 B:2* A:& B: 5+0 A: & B: 4** A:0+1 A:1.5* B:0+1 B:1.
Table 12 B: 0+1/SBY B: 1.5** A:& B: 0+1+0/SBY A: & B: 3*** Array Configuration - Seven drives Array Configuration: Eight Drives Drives and Drive Groups Possible RAID Levels Effective Capacity A:o A:JBOD A:1 B:o B:JBOD B:1 C:o C:JBOD C:1 D:o D:JBOD D:1 E:o E:JBOD E:1 F:o F:JBOD F:1 G:o G:JBOD G:1 H:o H:JBOD H:1 I:o I:JBOD I:1 A:oooooooo A:5 A:7* A:0+1 A:4* A:0 A:8 A:5/SBY A:6** A:0+1/SBY A:3.5** O A:0 A:7 A:ooooo A:5/SBY A:4** B:oo A:0+1/SBY A:2.
B:oooo B:5 B:3* A: & B: 5+0 A: & B: 6** A:0+1 A:2* B:0+1 B:2* A: & B: 0+1+0 A: & B: 4* A:0 B:4 A:oooo A:5/SBY A:3* B:ooo A:0+1/SBY A:2* O B:5/SBY B:2* B:0+1/SBY B:1.
Glossary A Active/Active A synonym for Dual Active controllers. Under normal operating conditions, both controllers in a dual active controller configuration are actively processing I/O. Application-Specific Integrated Circuit, a chip created for a specific application. Array Multiple disk drives configured to behave as a single, independent disk drive. See also Disk Array. Asynchronous Data Transfer Data transfer not synchronized to a set timing interval.
power failure, the BBU can hold data in the cache for a RAID subsystems, see Internal RAID Controller). A bridge certain amount of time. Once power is restored the data can RAID controller is often referred to as an External RAID be saved to a disk. Controller. Benchmarks Burst Data Rate A set of conditions or criteria against which a product or The speed at which a specific amount of data is sent or system is measured.
Channel Any path used for the transfer of data and control of information between storage devices and a storage controller or I/O adapter. Also refers to one SCSI bus on a The amount of data per unit of time moved through a channel or I/O bus in the course of execution of an I/O load, usually expressed in MBps. Device Driver disk array controller. Each disk array controller provides at least one channel.
to the disk, and writes the data out to a new location on the disk. Since the problem has been resolved, no error is reported to the system. Disk System A storage system capable of supporting only disks. Drive Groups A group of individual disk drives (preferably identical) that are logically tied to each other and are addressed as a single unit. In some cases this may be called a drive “pack” when referring to just the physical devices.
A magnetically coated disk substrate that spins inside a disk drive and is used as the storage medium for digital data. Hard Disk Drive (HDD) Hot Swap The exchange of a replacement unit in a storage system for a defective unit. The exchange requires human intervention, but the system can continue to perform its normal functions (compare with Auto Swap, Cold Swap, The main data storage unit of a computer. Host Any computer system to which disks are attached and and Warm Swap).
JBOD Just A Bunch of Disks (Drives), a number of disk drives, usually in an enclosure. JBOD implies that the disks do not use RAID technology and function independently. L Latency Refers to the complete duplication of data on one disk drive to another disk drive, this duplication occurs simultaneously with each write operation: each disk will be the mirror image of the other (also known as RAID Level 1).
several virtual disks whose entire capacity approximates that of the underlying disk or array. PCI RAID Levels Disk array controllers support four RAID Advisory Board approved (RAID 0, RAID 1, RAID 3, and RAID 5), two special (RAID 0+1, and JBOD), and three spanned (RAID Peripheral Component Interconnect, a standardized 10, 30, and 50) RAID levels.
The inclusion of extra components of a given type in a A type of read and write operation where entire blocks of system (beyond those the system requires to carry out its data are accessed one after another in sequence, as opposed functions). to randomly.
standby disk will automatically replace the failed drive and 1, block 2 on SCSI drive 2, block 3 on SCSI drive 3, block the data will be rebuilt. The system administrator can 4 on SCSI drive 1, block 5 on SCSI drive 2, and so on. This disconnect and remove the bad disk and replace it with a storage method increases the disk system throughput by new disk. The administrator can then make this new disk a ensuring a balanced load among all drives. standby.
Warm Swap The exchange of a defective disk with a working disk while power is maintained to the system, but I/O operations have ceased. Web A number of computers, servers, or networks linked together in a matrix. Write-Back Cache A caching strategy whereby write operations result in a completion signal being sent to the host operating system as soon as the cache (not the disk drive) receives the data to be written.
Index A Active Termination 225 Active/Active 225 Active/Passive 225 Alert Map 69 ANSI 225 Applet 225 Application Alerts launching 72 Array 225 configuration table 219 creating 94 deleting 104 expanding 102 menu 62 monitoring 115 properties 116 purpose of 213 Assisted Configuration 87 fault tolerance 88 no fault tolerance 90 Automatic Rebuild 80, 225 B Background Initialization 77, 225 Backing Up controller configuration 107 Battery Backup Unit 126, 225 monitoring 126 properties 126 reconditioning 194, 195 B
advanced 79 basic 76 expert 81 Fibre 84 general 74 IP settings 85 Conventions 13 D Data Transfer Rate 227 Debug Port 82 speed 82 Disk Scrubbing 188 E Enclosure displaying 123 monitoring 123 properties 125 Enclosure Menu 63 Event Details 111 Events 109 details 111 filtering 112 monitoring 109 notification application 69 parameters 71 setting 67 viewing 109 Expanding array 102 logical drive 100 F Failover 228 Failure 228 Fibre Channel 228 Firmware updating 191 Foreground Initialization 91, 96, 228 Frame contr
LUN Mapping 230 custom 98 M Maintenance 185 editing a world wide name table 188 logical drive consistency check 187 logical drive initialization 185 logical drive rebuild 187 Manual Configuration 92 create array 93 creating a hot spare 94 creating a logical drive 95 Menus 58 Monitoring 109 array 115 battery backup unit 126 controller 113 enclosure 123 events 109 logical drives 117 long operations 128 physical disks 117 Multiple Configuration Tool Lock 87 Multi-port Reset 81 N Navigation Features 55 New Serv
deleting 48 Server Groups creating new 46 setting up 46 Server Menu 59 sgen.conf, Solaris configuration 40 Shut Down a controller 195 Smart Large Host Transfers 80 Solaris configuration sd.conf 39 sgen.
