SGI® InfiniteStorage 15000 RAID User’s Guide 007-5510-002
COPYRIGHT © 2008 SGI. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein. No permission is granted to copy, distribute, or create derivative works from the contents of this electronic documentation in any manner, in whole or in part, without the prior written permission of SGI.
Contents 007-5510-002 1 Introduction ..................................................................................................................................... 1.1 Controller Features ...................................................................................................................... 1.2 The Controller Hardware ............................................................................................................. 1.2.1 Power Supply and Fan Modules ......................
ii 3.4 Security Administration ............................................................................................................. 3.4.1 Monitoring User Logins .................................................................................................... 3.4.2 Zoning (Anonymous Access) ........................................................................................... 3.4.3 User Authentication ..........................................................................................
Contents 007-5510-002 5.6.3 AC INPUT PCM .............................................................................................................. 5.6.4 DC INPUT PCM ............................................................................................................. 5.6.5 DC OUTPUT PCM ......................................................................................................... 5.6.6 PCM Safety and EMC Compliance ...................................................................
8.9 Replacing the DEM ................................................................................................................. 127 Appendix A. Controller Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . 129 Appendix B. Drive Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Appendix C. Cabling Controllers and Drive Enclosures . . . . . . . . . . . . . . . . .
Preface Preface What is in this guide This user guide gives you step-by-step instructions on how to install, configure, and connect the SGI InfiniteStorage 15000 system to your host computer system, as well as to use and maintain the system. Who should use this guide This user guide assumes that you have a working knowledge of the Serial Attached SCSI (SAS) protocol environments into which you are installing this system.
Preface European Regulations This equipment complies with European Regulations EN 55022 Class A: Limits and Methods of Measurement of Radio Disturbance Characteristics of Information Technology Equipment and EN50082-1: Generic Immunity.
Preface Chassis Warning Label: Weight Hazard • Do not lift the drive enclosure by the handles on the power cooling module (PCM); they are not designed to support the weight of the populated enclosure. Safety Important SGI InfiniteStorage 15000 drive enclosures must be always installed in SGI InfiniteStorage 15000 racks. SGI does not authorize or support the use of these drive enclosures in any standalone benchtop or enclosure-on-enclosure stacking configuration.
Preface Power Cooling Module (PCM) Caution Label: Do not operate with modules missing Warning To ensure your system has warning of a power failure please disconnect the power from the power supply, by either the switch (where present) or by physically removing the power source, prior to removing the PCM from the enclosure/shelf. • Do not remove a faulty PCM unless you have a replacement unit of the correct type ready for insertion.
Preface Warning Operation of the Enclosure with ANY modules missing will disrupt the airflow and the drives will not receive sufficient cooling. It is ESSENTIAL that all apertures are filled before operating the unit.
Preface • The electrical distribution system must provide a reliable earth ground for each unit and the rack. • Each power supply in each unit has an earth leakage current of 1.5mA. The design of the electrical distribution system must take into consideration the total earth leakage current from all the power supplies in all the units.
Preface • If the subsystem is used with modules or blanking plates missing for more than a few minutes, the enclosure can overheat, causing power failure and data loss. Such use may also invalidate the warranty. • If you remove any drive module, you may lose data. – If you remove a drive module, replace it immediately. If it is faulty, replace it with a drive module of the same type and capacity • Ensure that all disk drives are removed from the enclosure before attempting to move the rack installation.
Introduction Chapter 1 Introduction The SGI InfiniteStorage 15000 controller is an intelligent storage infrastructure device designed and optimized for the high bandwidth and capacity requirements of IT departments, rich media, and high performance workgroup applications. The controller plugs seamlessly into existing SAN environments, protecting and upgrading investments made in legacy storage and networking products to substantially improve their performance, availability, and manageability.
• Comprehensive, Centralized Management Capability The controller provides a wide range of management capabilities: Configuration Management, Performance Management, Logical Unit Number (LUN) Management, Security Administration, and Firmware Update Management. • Management Options via RS-232 and Ethernet (Telnet) A RS-232 port and Ethernet port are included to provide local and remote management capabilities. SNMP is also supported.
Introduction Front (behind cover panel) A C E G P TEST HOST 1 HOST 1/2 CLI HOST 3 ACT HOST 3/4 CLI TELNET LINK ACT STATUS A B C D E F G H P LINK STATUS LINK S ACT ACT 1 3 2 4 CLI B D F H 1/2 S CTRL STATUS AC FAIL DISK CHANNELS SYSTEM STATUS TEMP STATUS DISK STATUS COM HOST 2 FAN STATUS DC STATUS HOST 4 TEST PLACE PIN HERE LINK ACT AC FAIL MUTE ALARM SILENCE Rear Figure 1–1 SGI InfiniteStorage 15000 IB - Front and Rear Views The controller is a high-perf
1.2.1 Power Supply and Fan Modules Each controller is equipped with two (2) power supply modules and one (1) fan module. The PSU (power supply unit) voltage operating ranges are nominally 110V to 230V AC, and are autoranging. The two Power Supply modules provide redundant power. If one module fails, the other will maintain the power supply and cooling while you replace the faulty module.
Introduction 1.2.2 I/O Connectors and Status LED Indicators Figure 1–3 shows the ports at the back of the controller 4 Infiniband (IB) unit. These ports are for the test of the RAID engine by the manufacturer or other authorized personnel only.
Host port LEDs A C E G P TEST HOST 1 HOST 3 HOST 1/2 CLI ACT HOST 3/4 CLI TELNET LINK ACT STATUS A B C D E F G H P LINK STATUS LINK S ACT ACT 1 3 2 4 CLI B D F H 1/2 S CTRL STATUS AC FAIL DISK CHANNELS SYSTEM STATUS TEMP STATUS DISK STATUS FAN STATUS DC STATUS COM HOST 2 HOST 4 TEST PLACE PIN HERE LINK ACT AC FAIL MUTE ALARM SILENCE Host port LEDs Figure 1–4 Host Port LEDs The four HOST ports are used for IB or FC-8 host connections.
Introduction There are two AC Fail LEDs. Each LED is connected to its power supply independent of the other supply. The LEDs are green to indicate that the AC input to the supply is present. The LEDs turn red if the AC input to the supply is not present. If this occurs, check the LEDs on the front side of the unit. If you lose AC power from one supply cord, the LED for that supply outlet will turn red. Figure 1–5 shows the following status LEDs: System, Controller, Disk, Temperature, DC, and Fan.
Table 1–1 LED Indicators Status Indicator IB DISK ports Led Activity Explanation Solid Green (Infiniband) Physical Connectivity with host Solid Amber Subnet Manager communicating with host Flashing Green Activity.
Introduction Table 1–1 LED Indicators Status Indicator Disk Temp Status DC Fan Status AC Fail FC (FC-8 only) 1.2.
Controller Installation Chapter 2 Controller Installation These steps provide an overview of the controller installation process. The steps are explained in detail in the following sections of this chapter. 1. Unpack the controller system. 2. If it is necessary to install the controller in the 19-inch cabinet(s), contact your service provider. NOTE : Most controller configurations arrive at sites pre-mounted in a 42U or 45U rack supplied by SGI. 3.
Controller Installation 2.2 Unpacking the System Before you unpack your controller, inspect the shipping container(s) for damage. If you detect damage, report it to your carrier immediately. Retain all boxes and packing materials in case you need to store or ship the system in the future. While removing the components from their boxes/containers, inspect the controller chassis and all components for signs of damage. If you detect any problems, contact SGI immediately.
Controller Installation 2.2.3 Connecting the Controller To set up the disk enclosures and connect them to the controller, do the following. 1. There are 10 disk channels on the controller. They correspond with disk ports.
Controller Installation Configuration of disks in the enclosures must be in sets of complete tiers (Channels A through P). Allocating one spare drive per tier gives you the best data protection but this is not required. The spare drives on the controller are global hot spares. 2.2.6 Connecting the RS-232 Terminal For first time set-up, you will need access to an RS-232 terminal or terminal emulator (such as Windows hyperterminal).
Controller Installation Table 2–1 Key Basic Key Assignments Escape Sequence Description Backspace Ctrl-H, 0x08 deletes preceding character Del Del, 0x7F or Esc [3~ deletes current character Up Arrow Esc [A retrieves previous command in the history buffer Down Arrow Esc [B retrieves next command in the history buffer Right Arrow Esc [C moves cursor to the right by one character Left Arrow Esc [D moves cursor to the left by one character Home Esc [H or Esc [1~ moves cursor to the start
Controller Installation 2.3 Configuring the Controller This section provides information on configuring your controller. NOTE :The configuration examples provided here represent only a general guideline. These examples should not be used directly to configure your particular controller. The CLI (command line interface) commands used in these examples are fully documented in sections 3.1 through 3.8—though exact commands may change depending on your firmware version.
Controller Installation The controller supports various disk drive enclosures that can be used to populate the 10 disk channels in both SAS 1x and SAS 2x modes. Each chassis has a limit to the tiers that can be created and supported. Refer to the specific disk enclosure user guides for further information. You can create up to 1024 LUNs in a controller.
Controller Installation For example, to change the system date to March 1, 2009, enter: date 3 1 2009 To set the system time, at the prompt, type: time hh:mm:ss where hh represents the two digit value for hour (00 to 24), mm is the two digit value for minutes, and ss represents the two digit value for seconds For example, to change the system time to 2:15:32 p.m.
Controller Installation 2.3.6 Checking Tier Status and Configuration Use the tier command to display your current tier status. Figure 2–5 illustrates the status of a system containing 80 drives on 8 tiers with both parity modes of 8+1 and 8+2 tiers. The plus sign (+) adjacent to the tier number indicates that the tier is in 8+2 mode.
Controller Installation Figure 2–6 2.3.6.1 Current Tier Configuration Heading Definitions • Total LUNs. LUNs that currently reside on the tier. • Healthy Disk. The “health” of the spare disk currently being used (if any is being used) to replace a disk on the listed tier. The health indication for the spare channel that is physically on the listed tier is found under SP H. • F indicates the failed disk (if any) on the tier. • R indicates the replaced disk (if any) on the tier.
Controller Installation Figure 2–7 Dual Controller Configuration If you require multi-pathing to the LUNs, enable cache coherency. If you do not require multi-pathing, disable cache coherency. To enable/disable the cache coherency function, enter the following (ON enables, OFF disables): dual coherency=on|off You may change the label assigned to each unit. This allows you to uniquely identify each unit in the system. Each unit can have a label of up to 31 characters long. 1.
Controller Installation NOTE : In dual mode, LUNs are “owned” by the controller unit where they are created. Hosts only see the LUNs on the unit to which that they are connected, unless cache coherency is enabled. 1. To display the current cache settings, type: cache 2. Select a cache segment size for your array. For example, to set the segment size to 128KBytes, type: cache size=128 This setting can also be adjusted on-the-fly for specific application tuning: see section 3.2.
Controller Installation After you have initiated LUN format, the message Starting Format of LUN is displayed. You can monitor the format progress by entering the command LUN (see Figure 2–9). Upon completion, this message: Finished Format of LUN 0 displays.
Controller Installation 2.3.9 Setting Security Levels After you have formatted all the LUNs, you can define users’ access rights. Configurations come in two types: • authorized user • host port zoning The Authorized User configuration is highly recommended for use in a SAN environment-- your data is completely secured and no accidental plug-in is allowed to do damage such as data change or deletion. Authorized users have access only to their own and “allowed to share” data.
Controller Installation 2. Check to ensure that the LUN Zoning chart is empty (Figure 2–11). 15000 [1]: zoning LUN Zoning Port World Wide Name External LUN, Internal LUN ----------------------------------------------------------------------------1 21000001FF040004 2 22000001FF040004 3 23000001FF040004 4 24000001FF040004 Figure 2–11 LUN Zoning Screen To add a user: 1. Type: user audit=on The controller reports which users are connected. 2. Type: user add. 3.
Controller Installation 10. Enter a new unique LUN mapping for this user. Options are shown in Table 2–2 on page 26. Table 2–2 LUN Mapping Options. Option G.1 Description GROUP.LUN number P place-holder R Read-Only. Place before the GROUP.LUN N Clear current assignment No Change E EXIT ? Display detailed help text. 11. Connect user 2 and repeat steps 2--10 to specify the host port zoning and LUN mappings with the following changes: - For active host port (step 6), enter port 2 only.
Controller Installation 2.3.9.2 Host Port Zoning (Anonymous Access) Host Port Zoning (Anonymous Access) should only be used for non-SAN environment. Users are given “general admission” to the data. ! Anonymous Access (host port zoning) provides only the minimum level of security. Warning One zoning configuration is supported for each of the host ports. Any unauthorized user accessing the storage is considered “anonymous” and granted zoning access for the host port to which they are connected.
Controller Management Chapter 3 Controller Management 3.1 Managing the Controller The controller provides a set of tools that enable administrators to centrally manage the network storage and resources that handle business-critical data. These include Configuration Management, Performance Management, Remote Login Management, Security Administration, and Firmware Update Management. Bundled together, this is called the controller’s Administrator Utility. 3.1.
3. With the controller ready, press to get the controller prompt. NOTE :To change the baud rate on controller, see section 3.8.3 "Changing Baud Rate for the CLI Interface" in this guide. Remotely - Telnet To configure and monitor the controller remotely, connect the controller to your Ethernet network. Refer to Section 4.1, "Remote Management of the Controller" for information on how to set up the controller’s network interface. 3.1.
Controller Management NOTE : The default administrator account name is “admin” and its password is “password.” Similarly, the default user account name is “user” and its password is “password.” 15000 [1]: login Enter a login name: admin Enter the password: ******** Successful CLI session login. New owner : admin. New security level: Administrative. Figure 3–2 3.1.3.
15000 [1]: whoami CLI session: Current owner : admin. Current security level: Administrative. Figure 3–4 WHOAMI Screen 3.2 Configuration Management The controller provides uniform configuration management across heterogeneous SANs. Status of host ports and storage assets are continuously being monitored. Table 3–1 3.2.
Controller Management The PORT=X|ALL parameter specifies the specific host port(s) (1 to 4) to be affected when used in combination with any of the other parameters: ID, TIMEOUT, SPEED (for FC only), or WWN. The default is to apply changes to ALL host ports. 3.2.1.1 Figure 3–5 FC Host Ports Configuration Screen Figure 3–6 IB Host Ports Configuration Screen Host ID HOST ID= changes the hard loop ID of a host port.
HOST STATUSCLEAR resets the error counts. Figure 3–7 3.2.1.3 IB Host Ports Status Screen Host IB Users HOST ibusers displays additional information on the Infiniband (IB) users logged into the controller. (Figure 3–8). Figure 3–8 3.2.1.4 Host IB Users Screen Host Port Speed HOST SPEED lets you display and change the port speed on the host port(s). You are prompted for the desired speed as well as for the choice of host port(s). 3.2.
Controller Management Figure 3–9 Disk Channel Screen If the channel status is “acquiring loop synchronization,” this may indicate a channel problem. Refer to 4.2.2, "Recovering from Drive Failures" for recovery information. Entering DISK INFO= retrieves information about a specific disk (tier, channel). DISK LIST displays a list of the disks installed in the system and indicates how many were found.
Figure 3–11 Disk Defect List Screen DISK FAIL= instructs the system to fail the specified disk at the physical tier in the range of <1 ...125> and channel in the range of . When a non-SPARE disk is specified and it is failing, the disk will not cause a multi-channel failure. The disk is marked as failed. An attempt is made to replace it with a spare disk.
Controller Management Table 3–2 PHY Link Error Status Block Information SATA AAMUX PHY ERRORS H-RX The number of SATA FIS CRC errors received on the host port of the AAMUX H-TX The number of SATA R_ERR primitives received on the host port indicating a problem with the transmitter of the AAMUX H-Link The number of times the PHY has lost link on the host port. H-Disp The number of frame errors for the host port of the AAMUX.
15000 [1]: disk pls Tier 1 PHY Error Status Blocks Channel B C D E F G H P S A -------------------------------------------------H-RX: . . . . . . . . . . H-TX: . . . . . . . . . . H-Link: . . . . . . . . . . H-Disp: . . . . . . . . . . O-RX: . . . . . . . . . . 0-TX: . . . . . . . . . . O-Link: . . . . . . . . . . 0-Disp: . . . . . . . . . . D-RX: . . . . . . . . . . D-TX: . . . . . . . . . . D-Link: . . . . . . . . . . D-Disp: . . . . . . . . . .
Controller Management 3.2.2.2 Tier Configuration TIER CONFIG displays the detailed tier configuration information for all of the tiers (Figure 3–13). Figure 3–13 Tier Configuration Screen The headings for the Tier Configuration screen indicate the following values or conditions for the tiers. Total LUNs lists the number of LUNs that currently reside on the tier.
Figure 3–14 3.2.2.3 Tier Configuration ALL Screen LUN View Entering the LUN command displays the current status of the LUNs ( ). “Ready” indicates that the LUN is in good condition. The percentage of completion is displayed if the LUN is being formatted or rebuilt. A status of “Unavailable” may result from multiple drive failures. “Ready [GHS]” indicates that a spare drive has been successfully swapped for one of the drives the tier.
Controller Management 15000 [1]: lun list Logical Unit Status LUN Label Status Owner Capacity Serial (Mbytes) Number ------------------------------------------------------------------------vol1 1 0 Ready [GHS] 10002 00015A1300A7 1 vol2 1 Ready 10002 0001A28101A7 2 vol3 1 Ready 10002 0001A29A03A7 3 vol4 1 Ready 10002 0001A2b10400 System Capacity 2240096 Mbytes, 2200088 Mbytes available. Figure 3–16 3.2.2.
3.2.2.7 Status of Drive Enclosures The SES command displays the failures reported by the enclosure (Figure 3–19), through the SCSI Enclosure Services (SES). It also provides a means to access SES specific functions such as disk, channel, and LUN. Drive failures are not displayed using the SES command; you must use the TIER command to view drive status.
Controller Management TIER MAP displays the current mapping mode for the disks in the array. TIER CHANGEMAP changes the current tier mapping for the disks in the array. To change the current tier mapping, do the following: 1. Enter: tier changemap 2. Select the appropriate mapping mode for your drive enclosures and press . 3. For the changes to take effect, enter: restart. NOTE :The CHANGEMAP command should only be used when the system is first configured.
NETWORK TELNETPORT= changes the Telnet port number for the current controller. The system must be restarted before the changes will take effect. Valid port numbers are 0 to 32768; however, the results may be unpredictable if the port number chosen is already in use (on this unit) by either the GUI or SYSLOG facilities. The default port number is 23. 3.2.4.2 SNMP & Syslog NETWORK SNMP=ON|OFF enables and disables the SNMP functionality.
Controller Management 3.2.4.4 Displaying and Editing the Routing Table The ROUTE command displays the current routing table of the system (Figure 3–20) and allows the administrator to change it. The routing table describes how the controller can communicate with the hosts on other networks. 15000 [1]: route Gateway 172.16.0.254 Permanent Routing Table: ========================= destination gateway ---------------------------0.0.0.0 172.16.0.
RESTART DUAL restarts both units. RESTART KILL stops a timed restart that is in progress. 3.2.5.2 System Shutdown SHUTDOWN shuts down the controller unit. If you need to power down the controller, use SHUTDOWN prior to shutting off power. This will cause the controller to flush its cache, abort all format and rebuild operations, and proceed with an orderly shutdown. All hosts actively using the controller should be safely shutdown and all users logged out before using this command.
Controller Management 3.2.6.2 System Time TIME displays the current system time. You can also change the system time. At the prompt, type: time hh:mm:ss where hh represents the two digit value for hour (00 to 24), mm represents the two digit value for minutes, and ss represents the two digit value for seconds. For example, to change the system time to 2:15:32 p.m., type: time 14:15:32 NOTE : The system records time using the military method, which records hours from 00 to 24, not in a.m.
! The DEFAULT command will delete all LUN configuration and data unconditionally. Do not issue this command without guidance from SGI. Warning The system will halt all I/O requests, delete all the LUNs and restore all the parameters back to their default values. This is a destructive operation which will delete all the data stored in the system. The system will ask if you want to erase all the configuration information stored on the disks.
Controller Management To add a 32-bit LUN that will not exceed 2 TB, type: lun add=X To add a 64-bit LUN, that exceeds 2 TB: lun add64=X For both cases, “X” is the Logical Unit with a range of <0..1023>. For either case, the system prompts you for all the necessary information to create the LUN and indicates if the LUN was successfully added to the system.
15000 [1]: lun label Enter the LUN to label (0..1023), ‘e’ to exit: 0 Enter a new label for LUN 0, up to 12 characters: vol1 Logical Unit Status LUN Label Owner Status Capacity Block Tiers Tier List (Mbytes) Size ------------------------------------------------------------------------1 0 vol1 1 Ready [GHS] 10002 512 1 1 1 2 Ready 10002 512 2 1 2 1 Ready 10002 512 3 1 3 2 Ready 10002 512 4 System Capacity 277810 Mbytes, 237802 Mbytes available. Figure 3–24 3.2.9.
Controller Management Use the TIER command to display the current setting (Figure 3–26). The rebuild operation can take up to several hours to complete, depending on the size of the disk and rate of rebuild.
SMART ENABLE enables SMART on all the disk drives installed in the system and updates the parameter blocks on the disk. This enables the Information Exception and the Temperature warnings. However, the user can skip the update part and enter SMART DISKUPDATE later to write the parameter blocks to the disks. SMART DISABLE disables SMART on all the disk drives installed in the system and updates the parameter blocks on the disk.
Controller Management SMART TEST=ON enables the test bit in the Information exception mode page for all the disks installed. Setting the test bit simulates a FALSE SMART trip condition which raises a FALSE check condition to the controller. Currently, this parameter is valid only with Fibre Channel disks. SMART TEST=OFF disables the test bit in the Information exception mode page for all the disks installed. SMART INTERVALTIME displays the interval (in hours) in which the SMART Information will be polled.
For example, a user is given access to internal LUNs 5, 6, and 7, which are mapped to external LUNs 0, 1, and 2, respectively. controller 1 owns LUNs 0 and 1 while controller 2 owns LUN 2. The user is physically connected to controller 1, thus, they will only see LUNs 0 and 1. The user will not be able to access LUN 2. If the user was physically connected to controller Unit 2, the reverse would be true: only LUN 2 would be accessible.
Controller Management 15000 [1]: dual label Enter the number of the unit you wish to rename. LABEL=1 for unit 1, Test System[1] LABEL=2 for unit 2, Test System[2] unit: 1 Enter a new label for unit 1, or DEFAULT to return to the default label. Up to 31 characters are permitted. Current unit name: Test System[1] New unit name: System[1] Figure 3–28 3.2.12.4 Labeling a Controller Unit Singlet The DUAL SINGLET command sets the system in the singlet mode. System recognizes only Unit 1.
15000 [1]: cache Current Cache Settings Write Maximum MF Prefetch LUN Caching Prefetch Bit Ceiling ---------------------------------------------------0 Enabled x1 On 65535 1 Enabled x1 On 65535 2 Enabled x1 On 65535 3 Enabled x1 On 65535 writeback limit: 75% 640.0 Mbytes of Cache Installed Figure 3–29 Cache Setting Screen You can use the LUN=x option to specify which LUN to change. If no LUN is specified, changes will be applied to all the LUNs. Valid LUN values are 0 to 1023.
Controller Management If the MF (Multiplication Factor) parameter is OFF, the system will only prefetch the number of blocks specified by PREFETCH after every read command. If the MF parameter is ON, then the system will multiply the transfer length of the command by the prefetch value to determine how much data will be prefetched. A prefetch value of less than 8 is recommended when the MF parameter is ON. CACHE MF=ON|OFF enables/disables the MF bit on the specified LUN. Default is ON.
3.3.2 Audio/Visual Settings of the System The audio and visual (AV) settings of the system and the disks can be tuned to provide better performance and a lower latency. The writeback and prefetch settings for each LUN are changed with the CACHE command. The AV command displays information about the audio/visual settings of the system (Figure 3–31). Figure 3–31 Current Audio/Visual Settings AV FASTAV=ON|OFF enables/disables the disk fast audio/video read options for streaming data.
Controller Management RC=ON|OFF enables the Read Continuous (RC) option for Audio/Video streaming data; the system starts the data transfer for read operations after RCTIMEOUT is reached, even if the disks commands have not finished. Use this to reduce the latency for read operations in Audio/Visual environments where latency is more important than data integrity. This parameter is saved on a per-LUN basis. Use in combination with the LUN=x parameter to change the settings for a single LUN.
For example, LUNs 0 to 3 are locked in cache and all 50% of the total cache has been filled by data from LUN 0, 1, and 2. Initial Cache Unlocked LUN data Data for LUN 0 Data for LUN 1 Data for LUN 2 When a host issues a read command for data from LUN 3, the following will occur: • The controller unit determines which data to remove from the locked portion of cache, using the LRU algorithm.
Controller Management Figure 3–33 System Performance Statistics Screen Read Hits shows the percentage of Read I/O requests where the data was already in the cache. Prefetch Hits shows the percentage of Read I/O requests where the data was already in the cache due to prefetching. Prefetches shows the percentage of host Read I/O requests to the disks due to prefetching. The bottom of the screen displays the Read and Write performance of the disks.
STATS DELAY displays a histogram of the time it takes for the host and disk I/O requests to complete in 100 msec intervals (Figure 3–34). 15000 [1]: stats delay Command Delay Statistics Time seconds 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 2.0 2.1 2.
Controller Management STATS HOSTDELAY displays a histogram of the time delay between when the last data transfer is set ready and the host command completes (Figure 3–35). The host ready delay information is shown in 100msec intervals. 15000 [1]: stats hostdelay Host Command Ready Delay Statistics Time seconds Port 1 Reads Writes 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 1.1 1.2 1.3 1.4 1.5 1.
STATS DISK displays a histogram of the disks in the system that have taken an unusually long time to complete an I/O request (Figure 3–37). The count is incremented for a disk if that disk takes longer than the other disks to finish an I/O request. This command is used to determine if a disk in the array is slowing down system performance. Normally all the disks in a tier should have similar counts.
Controller Management STATS DUAL displays the statistics for the dual mode messages (Figure 3–38). Figure 3–38 Dual Message Statistics Screen STATS LENGTH displays a histogram of the length of the host I/O requests in 16 kb intervals (Figure 3–39).
STATS OFFSET displays a histogram of the offset of the host I/O requests into the cache segments (Figure 3–40). Host I/O requests with offsets that are not in the 0x0 column may require blocking/ deblocking which can slow down the performance of the system.
Controller Management TIER DELAY=x is used to set the system rebuild/format delay. This value is in 100 millisecond increments. The range is 0 to 1000. The default setting is 30 milliseconds (3 seconds). The REBUILD EXTENT parameter determines how much data to rebuild or format at one time. A small EXTENT value will slow down the rebuild and format operations so they will not affect the performance of the system. Increasing the EXTENT value will allow more data to be rebuilt in a single pass.
TIER VERIFY Displays a summary of verifications. To enable Tier Verify (Figure 3–42): 1. At the prompt, type TIER VERIFY=ON . 2. The system will ask which tier you wish to verify. Enter the tier number or type a for “All.” 3. The system will ask if you want run the Tier Verify operation continuously or not. Type y to run continuously or N to run just once. The default is N. Figure 3–42 Tier Verify ON Screen To disable Tier Verify (Figure 3–43): 1. At the prompt, type TIER VERIFY=OFF .
Controller Management Figure 3–43 Tier Verify OFF Screen TIER VERIFY=X A specified tier will be verified if possible. These API and CLI commands will affect the TIER verification process: • The CLI commands TIER PAUSE, TIER RESUME, TIER STOP. • The API command TIER STATUSCHANGE. LUN operations (add, delete, move) can affect TIER VERIFY operations. As tiers are verified, only LUNs that are valid and formatted are verified.
communication, such as a cable failure, can cause the controller to fail numerous disk drives. Once the loss of communication is resolved, the time to rebuild all the failed drives can take many weeks. The rebuild journals contain bitmaps that indicate which portions of the disks in a tier have been updated with new data while a disk was failed or replaced. The system uses the information in the journals to reduce the rebuild time of drives that have not been swapped out.
Controller Management To display the information about the rebuild journal, use the TIER JOURNAL command (Figure 3–44). To display the information for a specified tier, use the TIER JOURNAL=t command, where t is the specified tier. This screen will give detailed information about the status of the journal and a display of all the journal entries for the tier. This screen will also give more detailed information on the status of the journal and will indicate why it was disabled or invalidated.
NOTE : Improper use of the SES M_WAIT command can prevent the SES monitors from detecting an enclosure fault before the enclosure automatically shuts down. 3.3.4.5 Host Command Timeout The Host Command Timeout parameter allows the system to free up resources and make them available to other users if the request from a particular user cannot be completed. This helps to improve performance in a SAN environment where there are a lot of users accessing the storage. HOST TIMEOUT=X (where X is value range 1..
Controller Management 3.4.1 Monitoring User Logins The AUDIT function continuously monitors logins to the controller and provides alerts in the event of unauthorized login attempts (Figure 3–47). Host Int 15:04:07 User Logout Client1, port:4 S_ID:000004 Host Int 15:04:47 Authenticated Login Client10, port:3 S_ID:000002 Figure 3–47 User Login Messages USER AUDIT=ON|OFF enables/disables the user auditing function. When enabled, the system will display a message when a user logs in or out. Default is OFF.
Figure 3–50 3.4.3 Edit Zoning Configuration Screen User Authentication The controller creates correspondence between users (World Wide Name or GUIDs), storage LUNs, and permissions. The system can store configurations for up to 512 users in total, and the settings apply to all host ports. Each authorized user will only have access to their own and “allowed-to-share” data determined by their customized LUN identification scheme.
Controller Management 3.5 Firmware Update Management SGI periodically releases firmware updates to enhance features of their products. Contact SGI technical support to obtain the latest firmware files. 3.5.1 Displaying Current Firmware Version The VERSION command displays version information of the controller’s hardware and firmware (Figure 3–52). Figure 3–52 3.5.
Figure 3–53 Downloading Controller Firmware 6. Enter the TFTP server’s IP address: TFTP 7. Enter the firmware path and filename: TFTP 8. For the couplet controller configuration, connect and log into the other controller. Repeat Steps 47 above to update the firmware. 9. Enter RESTART to restart the unit(s). NOTE : RESTART can be done at a later time. 10.
Controller Management Figure 3–54 Telnet Statistics The administrator is strongly advised to perform any commands affecting the system’s configuration from the CLI UART only (and not from a Telnet session), and to only perform such commands after issuing the TELNET DISABLE command, so that remote users cannot log into the system in the middle of an administrative command. 3.6.
Within the CLI subshell, the TELNET command allows the administrator to view information regarding the currently active Telnet session (Figure 3–56). Figure 3–56 Telnet Session Information TELNET KILL=m lets the system administrator terminate the remote Telnet session (Figure 3–57). The KILL parameter may also be specified with TELNET KILL=m, where m indicates the number of minutes that will be allowed to elapse before the remote Telnet session is terminated. The valid range is <0..15> minutes.
Controller Management 3.7 System Logs 3.7.1 Message Log All controller events are logged and saved in non-volatile memory. The log will automatically roll over when it is full. LOG displays the log of previous system messages. LOG CLEAR clears the log of all previous messages. LOG CHECKCONDITION displays the Check Condition log. LOG CHECKCONDITION=MORE will display additional information concerning the check condition. LOG CHECKCLEAR clears the Check Condition log, enter LOG CHECKCLEAR. LOG QUIET= ON|OFF.
To display the number of LUN array parity errors detected by the system, use the FAULTS ARRAYPARITY command. The system saves the counts for each tier of all the LUNs. To clear the count of LUN array parity errors in the system, use the FAULTS ARRAYPARITYCLEAR command. FAULTS BUSPARITY displays the number of bus parity and data path errors detected by the system. FAULTS BUSPARITYCLEAR clears the count of errors.
Controller Management 3.8 Other Utilities 3.8.1 APC UPS SNMP Trap Monitor APC_UPS displays the status of the APC UPS SNMP trap monitor (Figure 3–61). 15000 [1]: apc_ups APC UPS SNMP trap monitor is off. No APC UPS faults detected via SNMP trap. Figure 3–61 APC UPS SNMP Trap Monitor Status APC_UPS CLEAR_FAULTS will delete all pending APC UPS faults from the fault list. All APC UPS events that disabled writeback caching will be cleared. 3.8.
Figure 3–64 Displaying the Serial Console Setting CONSOLE BAUD changes the baud rate of the CONFIG port of the controller (Figure 3–65). 15000 [1]: console baud Select 1 2 3 4 5 e the new serial console baud rate from choices below: 9600 - 19200 - 38400 - 57600 - 115200 <- Current setting - escape out of this command Enter selection: Figure 3–65 3.8.4 Changing the Baud Rate CLI/Telnet Session Control Settings You may change the CLI’s and Telnet’s various session control settings.
Controller Management 3.8.6 Disk Reassignment and Miscellaneous Disk Commands The DISK REASSIGN=tc 0xh command allows for the reassigning of defective logical blocks on a disk to an area of the disk reserved for this purpose. The disk is specified by its: tier (t) in the range <1..125>, and channel (c) in the range 0xh is the hexadecimal value of the LBA (Logical Block Address) to be reassigned. The DISK LLFORMAT=tc command allows the user to perform a low level format of a disk drive.
test so it will not affect the performance of the system. Any changes applied to delay will affect tests in progress as well as future testing. This system spare diagnostic delay value is given in 100 millisecond increments. The valid range for 'x' is 0..100. The default is 0. The SPARE PATTERN=x command sets the system spare diagnostics pattern. The test pattern determines the pattern written to the disks during the test.
Troubleshooting Chapter 4 Controller Remote Management and Troubleshooting 4.1 Remote Management of the Controller The controller can be managed locally through the RS-232 interface, or remotely via Telnet. The Administrative Utility is the same regardless of the management interface (RS-232 or Telnet). The controller supports SNMP and allows the system to be remotely monitored. 4.1.1 Network Connection Connect the Telnet port on the back of the controller to your Ethernet network (Figure 4–1).
NOTE : Telnet connections are clear text. If Telnet connections are used, you may expose controller passwords to third parties. For higher security, we recommend that you disengage Telnet access if it is not required. 5. Decide whether the SNMP functionality should be enabled. To enable or disable SNMP, use the appropriate version of the command network SNMP=on|off.
Troubleshooting - ROUTE GATEWAY= sets the current gateway in the network routing table to the specified Internet address. - ROUTE DEL= GATEWAY= deletes gateways from the routing table. - ROUTE ADD= GATEWAY= adds new gateways to the table. - If you have couplet controller, connect to (or Telnet to if this is not the initial set up) and log into the other controller.
4.1.4 SNMP Set Up on Host Computer The following procedure explains how to set up the host computer to monitor the controller’s events (SNMP traps). NOTE : It is not possible to configure the controller through SNMP. Refer to Section 4.1.2 in this guide for information regarding network and SNMP configuration on the controller. Contact SGI to obtain the Management Information Base (MIB) files for the controller. 1.
Troubleshooting 4.1.4.2 Traps • Generic Traps - coldStart (occurs when the controller is restarted) • Enterprise Specific Traps - Any changes in controller MIB. If any variable in the controller MIB changes, a trap will be sent. For example, when a power supply fails or is replaced, a trap is sent. Trap includes ASCII string declaring new status of 15000 element. - 15000 status alerts. Trap includes ASCII string declaring the controller as failed or healed. 4.
4.2.1.2 4. Remove the module’s thumbscrews, then slide the module out of the bay. 5. Slide the module into the bay making sure it is fully inserted. Install the two thumbscrews to secure it. 6. Turn on the power switch. Check that the Status LED is green, indicating that the module is operating normally. 7. Replace the cover panel (if necessary). Fan Failure A fan failure error message will display on your console if the fan module fails. Follow these steps to replace the module.
Troubleshooting NOTE : If more than one disk is failed in a single tier, only the first disk to fail will be replaced by the spare disk. Any disks which fail after the first in each tier will not be reconstructed using a hot spare. 4.2.2.1 Single Drive Failures A single drive failure in any tier does not result in the data loss. The LUN(s) on that tier will continue to operate in degraded mode.
DISK INFO will indicate what spare drive is replacing the failed drive (Figure 4–6). Figure 4–6 4.2.2.2 Obtaining Disk Information Returning the System to a Fault-Tolerant State When you find a failed drive on a tier, replace it as soon as possible so that the tier can return to its optimal state. If you replace the failed drive while a rebuild is taking place, the system will finish rebuilding data on the spare drive first.
Troubleshooting 4.2.2.4 Changing the Rate of Rebuild The commands TIER DELAY and TIER EXTENT control the percentage of processor time allocated to rebuild compared to I/O handling. Rebuild is done in steps. DELAY will control the amount of wait time before rebuilding the next chunk of data. EXTENT determines the size of data used to rebuild. To increase the rate of rebuild, reduce the DELAY value. (See “Resources Allocation” on page 66.
4.2.3 Component Failure on Enclosures The controller implements the SCSI Enclosure Services (SES) protocol to communicate with its drive enclosures. If your enclosures provides SES communications, then enclosure status information of the , including power supply, fan, and presence of drive, will be obtained and evaluated. If a change in status is found, an SES message is displayed on your console (Figure 4–7).
Drive Enclosure Chapter 5 Drive Enclosure System 5.1 The SGI InfiniteStorage 15000 Drive Enclosure The SGI InfiniteStorage 15000 drive enclosure storage system is an ultra dense 4U 60 disk drive enclosure. Figure 5–1 and Figure 5–2 show front and rear views of a drive enclosure, respectively. Module and major components and their locations are shown in Figure 5–3.
30 Drive Bays I/O-B PCMs 8 DEMs I/O-A 30 Drive Bays Figure 5–3 Drive Enclosure Module Locations 5.2 Enclosure Core Product The drive enclosure design concept is based on a subsystem together with a set of plug-in modules and (as supplied) comprises: • Enclosure Chassis with integral Front Panel Drive Status Indicator (Figure 5–9). • Two (2) 1865W Power Cooling (PCM) plug-in modules (Figure 5–4). • Two (2) plug-in Input/Output (I/O) modules (Figure 5–5).
Drive Enclosure 5.2.1 Enclosure Chassis The chassis assembly contains 60 drive bays at the front, each of which accommodates a plug-in drive carrier module. The 60 drive bays are arranged in five rows of twelve drives (5x12). At the rear, the chassis assembly contains two (2) PCMs and two (2) I/O modules. The chassis is fitted with 19-inch rack mounting features which enables it to be fitted to four (4) 19-inch racks and uses four (4) EIA units of rack space. 5.
Table 5–1 PCM LEDs PCM LEDs Normal Operation LEDs Faults LEDs Enclosure Audible Alarm Off GREEN AC Input FAILURE off Off GREEN DC Output FAILURE off Off OFF Fan Fault / Power Supply Fault AMBER Off OFF 5.3.2 ID BLUE Input/Output (I/O) Module The drive enclosure storage subsystem includes an enclosure with rear facing bays which house two (2) I/O modules (Figure 5–5).
Drive Enclosure Host Port 1 Expansion Port 1 Host Port 2 Expansion Port 2 Figure 5–5 I/O Module I Table 5–2 Table 5–2 defines the LED indicators incorporated on the I/O module.
Table 5–2 I/O Module LEDs 5.3.3 I/O Module Amber Fault OFF ON •No Faults present I/O Fault •Off I/O Module Blue Identity ON OFF •Receiving SES Command Not receiving SES Command •Off Drive Carrier Module and Status Indicator The Drive Carrier Module comprises a hard disk mounted in a carrier (Figure 5–6). Each drive bay can house a single Low Profile 1.0 inch high, 3.5 inch form factor disk drive in its carrier.
Drive Enclosure Locking Mechanism Figure 5–7 Note DEM The DEM is a serviceable PCB which may be replaced by trained personnel. Each DEM connects to a single port of the HDD based on the location within the enclosure within which it is installed (Figure 5–8). Each provides power control signals to each drive slot. It controls HDD identify/service LEDs and monitors the status from partner DEM. Each pair set DEM supports 15 drives; there are 8 DEMs in a fully configured system.
cards are fitted to drives. These LEDs indicate drive presence. The Front Display Panel LEDs are defined in Table 5–3. Figure 5–9 Table 5–3 ICON 102 Front Panel Drive Activity Indicators Panel Display Panel LEDs LABEL COLOR Definition Shelf Identify BLUE enclosure Identity System Fault AMBER Enclosure Fault Normal Behavior ON-SES is sending an identity command. OFF-SES is NOT sending an identity command Enclosure Audible Alarm Off ON-one or more components within Off enclosure have failed.
Drive Enclosure Table 5–3 ICON Display Panel LEDs LABEL COLOR Drive Fault AMBER Drive fault ON-one or more HDDs are faulted. SES must determine exact HDD. OFF-no detectable drive faults Off GREEN HDD activity ON-indicates HDD activity OFF-no HDD activity Off Individually HDDs numbered Definition Normal Behavior Enclosure Audible Alarm .
5.4.2 Note Table 5–4 Internal Indicators In some components, the failure LED is internal to the enclosure and visible only when the cover is open. The Internal LED indicators are explained in Table 5–4. INTERNAL LED Indicators Description Location DEM DC Normal Behavior Enclosure Audible Alarm DEM internal to GREEN enclosure ON-1.2VDC regulator circuit correctly functioning OFF- faulty 2.
Drive Enclosure Table 5–5 LEDs on the Rear of the Enclosure Description Location COLOR Normal Behavior Enclosure Audible Alarm SAS Link I/O Module rear of enclosure GREEN ON-a valid SAS link established on at least 1 Off of the 4 SAS links of the 4-wide SAS port. OFF-no SAS links SAS Link Fault I/O Module rear of enclosure AMBER ON-a detectable fault on at least 1 of the 4 SAS links of the 4-wide SAS port. OFF-no detectable faults Off 5.
5.6.2 Weight Item Quantity per System LBS (kg) Extended Weight Chassis Includes Base PCB & Midplane 1 83 83 PCM 2 12 24 I/O Module Drives 2 4 8 60 2 120 1 5 Miscellaneous 5 Total Weight 5.6.3 AC INPUT PCM Input Parameter Value Input Voltage 190 - 264 VAC Input Frequency 47 - 63 Hz and 400 hz Maximum Input Current 13.1A RMS @ 190 VAC Peak Inrush Current 50A @ 230VAC, 250C, 5 msec max Minimum Efficiency measured at 30% and 50% load and nominal line (208 VAC) 5.6.
Drive Enclosure 5.6.5 DC OUTPUT PCM Output Parameter 5.6.6 3.3 VDC Output 5 VDC Output 12 VDC Output Normal Voltage 3.3 VDC 5.10 VDC 12.10 VDC Full Load 5.0A 55.0A 120.0A Peak Load for 1 Second 5.0A 65.0A 130.0A Minimum Load (A) 0.0A 0.0A 0.0A PCM Safety and EMC Compliance Safety Compliance UL 60950 IEC 60950 EN 60950 EMC Compliance CFR47 Part 15B Class A EN55022 EN55024 5.6.
Drive Enclosure Installation Chapter 6 Drive Enclosure Installation 6.1 Introduction Caution When connecting up the drive enclosure subsystem, use only the cables supplied. 6.2 Planning Your Installation Before you begin installation, you should become familiar with the configuration requirements of your drive enclosure system and the correct positions of each of the optional plug-in modules (Table 6–1). .
Table 6–1 Drive Enclosure Configuration Module Location Power Cooling Modules (PCM) Two (2) PCMs must be fitted. Full power and cooling redundancy is provided while a faulty module is replaced. Install the PCMs in lower rear bays A and B. Note: Rear bays are numbered from A and B starting from the left when viewed from the back. I/O Module One or two I/O modules should be Installed in the upper rear bays A & B.
Drive Enclosure Installation Figure 6–2 1X60 Drive Numbering Table.
6.3 Enclosure Installation Procedures Important SGI InfiniteStorage 15000 drive enclosures should only be installed in SGI InfiniteStorage 15000 racks. Mounting and installing these drive enclosures in any other rack is not authorized or supported by SGI. Warning The drive enclosure with all its component parts installed is too heavy for a single person to easily install into a Rack cabinet.
Drive Enclosure Installation 6.5 SAS DEM The drive enclosure contains eight (8) top-loadable DEMs. The DEMs provide the SAS connectivity between the I/O module and the HDDs located within the enclosure. Each DEM connects to a single port of the HDD based on the location within the enclosure in which it is installed. Each of the eight DEMs installed in the enclosure has a unique I2C and SAS address based on a proprietary SAS address generation scheme. 6.
Drive Enclosure Operation Chapter 7 Drive Enclosure Operation 7.1 Before You Begin Before powering up the enclosure, please ensure that all the modules are firmly seated in their correct bays. 7.2 Power On / Power Down Caution Do not operate the subsystem until the ambient temperature is within the specified operating range. If the drives have been recently installed, ensure they have had time to acclimatize before operating them. To Power On the enclosure. • Apply AC power to the enclosure.
7.2.2 I/O Panel LEDs The I/O Panel LEDs fault and status conditions are shown in Figure 7–1. Figure 7–1 I I/O Panel LEDs Table 7–1 defines the LED indicators incorporated on the I/O module.
Drive Enclosure Troubleshooting Chapter 8 Drive Enclosure Troubleshooting 8.1 Overview The SGI InfiniteStorage15000 Drive Enclosure includes an Enclosure Services Processor and associated monitoring and control logic to enable it to diagnose problems within the enclosure’s power, cooling, and drive systems. The sensors for power and cooling conditions are housed within the PCMs. Each unit is independently monitored. 8.2 Initial Start-up Problems 8.2.
3 Check that there is a valid SAS signal present at the I/O connector. If there is no signal present, ensure the cable has been properly inserted. 4 Check the I/O module setup as follows: – Ensure the I/O module has been correctly installed and all external links and cables are securely fitted. – Ensure the maximum cable length has not been exceeded. 8.3 LEDs Green LEDs are always used for good or positive indication. Amber LEDs indicate there is a critical fault present within the module.
Drive Enclosure Troubleshooting • Under Normal conditions, the LEDs should all be illuminated constant GREEN • If a problem is detected, the color of the relevant LED will change to AMBER. Table 8–3 DEM LEDs Location 8.3.4 Color LED Identifier Behavior FRONT Enclosure Amber Enclosure fault ON with a DEM fault. FRONT Enclosure Amber DEM fault ON with a DEM fault. Internal (DEM) Enclosure Amber DEM fault ON with a DEM fault.
Table 8–4 8.3.5 I/O LEDs REAR Enclosure Green SAS Link Activity ON when a valid link is present on any of the 4 links of the 4-wide port. OFF when none of the 4 links of the 4wide port have a valid connection. REAR Enclosure Amber SAS Link Fault ON when a fault is present on any of the 4 links of the 4-wide port. OFF when none of the 4 links of the 4wide port have a fault. Front Panel Drive Activity Indicators The Front Panel Drive Activity Indicators show the aggregated status of all the modules.
Drive Enclosure Troubleshooting Table 8–5 ICON Display Panel LEDs LABEL COLOR Definition Normal Behavior Cover Open AMBER Enclosure cover is open OFF-both cover pieces securely closed and latched in place. ON-either of the cover pieces is NOT securely closed and latched in place DEM Fault AMBER DEM fault OFF-all DEMs operating correctly. ON-at least one DEM has failed; service action required Drive Fault AMBER Drive fault ON-one or more HDDs are faulted. SES must determine exact HDD.
Symptom Cause If the ambient air is cool (below 25 °C) and the fans are observed to increase in speed, then some restriction on airflow may be causing additional internal temperature rise. The first stage in the thermal control process is for the fans to automatically increase in speed when a thermal threshold is reached. This may be caused by higher ambient temperatures in the local environment and may be perfectly normal.
Drive Enclosure Troubleshooting 8.5.2 Thermal Alarm Symptom Cause • Display Panel PCM/ If the internal temperature measured in the airflow Cooling Fault LED. through the enclosure exceeds • An AMBER LED on a pre-set threshold, a thermal alarm will sound. one or more PCMs. • Audible Alarm Sounding. • Air temperature exiting PCM above 35°C. Action 1 Check local ambient environment temperature is below the upper 40°C specification.
8.7 Continuous Operation During Replacement Depending on how the subsystem is set up, if a disk unit fails, it can normally be replaced without interrupting the use of the system. 8.8 Replacing a Module Warning Whenever replacing a module NEVER leave an EMPTY bay in the rear of the enclosure, obtain a replacement before removing the problem part. Please refer to Chapter 6, ”Drive Enclosure Installation” for information on the initial installation of the plug-in modules in the drive enclosure. Warning 8.
Drive Enclosure Troubleshooting To remove an AC PCM - Thumb Screw Model: Warning Do not remove the faulty PCM unless you have a replacement unit of the correct type ready for insertion. If a power supply unit or its fan is faulty, you must replace the whole PCM. As there should always be two PCMs installed, you can continue working while replacing the faulty module. 1 Make sure you identify the faulty PCM correctly from the two modules installed. 2 Lift latch which secures the power supply cord.
8.8.2 Warning I/O Module Do not remove this module unless a replacement can be immediately added. The system must not be run without all units in place. To remove the I/O Module: 1 Release the two latches on the bottom of the unit by simply pulling each latch out and away from unit. 2 Pull the latches forward to cam the module out of the enclosure. 3 Grip the unit securely and withdraw the module.
Drive Enclosure Troubleshooting spindown the drives prior to removal. If this is not possible, we recommend that you perform All steps of the following procedure to ensure that the drive has stopped prior to removal: To Insert the Drive Carrier Module 1 Release the carrier handle by sliding the latch backwards. 2 Insert the carrier into the enclosure. 3 Slide the drive carrier, gently, all the way into the enclosure. 4 Cam the drive carrier home.
A Controller Technical Specifications The following are the technical specifications of the SGI InfiniteStorage 15000 controller. NOTE : Specifications subject to change without notice. Configuration, Performance, & Capacity Host interface IB 4xDDR, FC-8 Drive interface SAS Management interface RS-232 and Ethernet (Telnet) Cache memory 2.
Physical, Power & Environmental Controller chassis (H×W×D, Weight) 3.5" × 19.0" × 31", 45 lbs Electrical/AC 100-120V / 200-240V @ 47-63Hz Power consumption (maximum current) 2.65A @ 208VAC Couplet: 8.0A @ 110VAC, 3.8A @ 230VAC Power consumption (average current) 3.0A @ 110VAC, 1.5A @ 230VAC Couplet: 6.0A @ 110VAC, 4.
B Drive Addressing This appendix illustrates the drive addressing for the disk enclosures. There are two drive numbering options: • 1 x 60 (one set of drives 1 through 60); (Figures B-1and B-3).
Figure B–3 132 Controller-Drive Enclosure Couplet (1x Configuration) 007-5510-002
Figure B–4 Controller-Drive Enclosure Couplet (2x Configuration) A C E G P B D F H S A C E G P B D F H S A B Controller #1 Controller #2 A B Channel A/B C D C D Channel C/D E F E F Channel E/F G H G H Channel G/H P S P S Channel P/S 00 7- 55 10 -0 02 133
C Cabling Controllers and Drive Enclosures This appendix illustrates the proper cabling of the following two configurations: • 2 controllers and 5 drive enclosures (Figures C–1 and C–2) • 2 controllers and 10 drive enclosures (Figures C–3 and C–4) 00 7- 55 10 -0 02 135
A C E G P B D F H S A C E G P B D F H S A Note: To use these cable lengths, controller 1 must be on top and controller 2 must be on the bottom.
A A Channel A B B Channel B C C Channel C D Note: To use these cable lengths, controllers and jbods must be placed in the order as shown.
Figure C–4 138 A A A A B B B B C C C C D D D D E E E E F F F F G G G G H H H H P P P P S S S S Drive Enclosure Cabling (2 Controllers and 10 Drive Enclosures) 007-5510-002
