US 5,835,700 AGrant
SCSI-coupled Module for Monitoring and Controlling SCSI-coupled Raid Bank and Bank Environment
Issue Date:1998-11-10
•21 Claims
•5 Drawing Sheets
Abstract
An intelligent status monitoring, reporting and control module is coupled to a SCSI bus that interconnects a cluster of SCSI-compatible data storage modules (e.g., magnetic disk drives). The status monitoring, reporting and control module is otherwise coupled to the cluster of SCSI-compatible data storage modules and to power maintenance and/or other maintenance subsystems of the cluster for monitoring and controlling states of the data storage modules and power maintenance and/or other maintenance subsystems that are not readily monitored or controlled directly by way of the SCSI bus. The status monitoring, reporting and control module sends status reports to a local or remote system supervisor and executes control commands supplied by the local or remote system supervisor. The status reports include reports about system temperature and power conditions. The executable commands include commands for regulating system temperature and power conditions.
Metadata
Assignee
- Seagate Technology, Inc.
Inventors
- Guy A. Carbonneau
- Bernie Wu
- Tim Jones
Application Information
Application Number:US 6989519
Filing Date:1996-08-16
Priority Date:1993-11-12
Art Unit:275
Classifications
IPC:
G06F 1130
Field of Search:
395183.2;184.01;182.04;185.1;833;835;838;839;182.03;182.05;183.18;183.17
Patent Drawings (5 sheets)
Description
Background
1. Field of the Invention
The invention relates generally to redundant arrays of data storage devices. The invention relates more specifically to a RAID system that connects to a host computer by way of a SCSI interface and a diagnostics/control module that also connects to the SCSI interface.
2a. Cross Reference to Related Applications
The following copending U.S. patent application is assigned to the assignee of the present application, is related to the present application and its disclosure is incorporated herein by reference:
(A) Ser. No. 08/124,276 filed Sep. 20, 1993 by Larry Kibler et al and entitled, FULL-HEIGHT DISK DRIVE SUPPORT STRUCTURE, now abandoned.
2c. Cross Reference to Related Patents
The following U.S. patent is related to the present application and its disclosure is incorporated herein by reference:
(A) U.S. Pat. No. 5,148,432 issued to Gordon et al. and entitled ARRAYED DISK DRIVE SYSTEM AND METHOD.
3. Description of the Related Art
The use of RAID data storage systems (Redundant Array of Inexpensive Disk-drives) is becoming increasingly popular due to economic and technical reasons.
Data storage strategies are being shifted away from having one large mainframe computer coupled to an array of a few, large disk units or a few, bulk tape units, and are instead being shifted in favor of having many desktop or mini- or micro-computers intercoupled by a network to one another and to many small, inexpensive and modularly interchangeable data storage devices (e.g., to an array of small, inexpensive, magnetic storage disk drives). One of the reasons behind this trend is a desire in the industry to maintain at least partial system functionality even in the event of a failure in a particular system component. If one of the numerous mini/micro-computers fails, the others can continue to function. If one of the numerous data storage devices fails, the others can continue to provide data access. Also increases in data storage capacity can be economically provided in small increments as the need for increased capacity develops.
A common configuration includes a so-called "client/server computer" sandwiched between a local area network (LAN) and a RAID data storage system. Remote users (clients) send requests for read and/or write access to data files contained in the RAID system over the network (LAN). The client/server computer services each request on a time shared basis.
As the client/server computer performs its client servicing tasks, the client/server computer is burdened at the same time with the overhead of attending to mundane tasks such as monitoring the operational status of each disk drive in the RAID system and taking corrective action, or at least issuing an alarm, when a problem develops.
A difficulty develops when the request-servicing bandwidth and/or storage capacity of such a RAID-based client/server system needs to be scaled upwardly. If the number of network users (clients) or request-load per user increases, the request-servicing burden that is placed on the client/server computer tends to increase correspondingly. At some point, the client/server computer bumps against the limits of its data processing speed and system responsiveness suffers.
System responsiveness is disadvantageously degraded by the burden that status monitoring overhead places on the client/server computer. In other words, the status monitoring overhead disadvantageously reduces the ability of the client/server computer to more quickly respond to the ever-growing number of service requests that it receives from the network. In addition, the status-monitoring overhead burden disadvantageously grows as more data storage drives are added to the RAID system. And accordingly, even though the addition of more data storage drives beneficially increases the system's storage capacity, it also tends to degrade system response speed.
The status monitoring function of the client/server computer is typically supported by customized hardware that is added to an expandable bus of the client/server computer. In one configuration, a serial and/or parallel I/O board is inserted into one of the expansion slots of the client/server computer and site-customized cables are routed from this I/O board to status sensors that are mounted on or in various components of the disk array. Monitoring software is loaded into the client/server computer to drive the I/O board, to query the various sensors and to receive status reports back from them. Such an arrangement is disadvantageous in that an expansion slot of the client/server computer is consumed for carrying out the disk-array monitoring function. It is also disadvantageous because of the customized nature of the sensor cables extending from the I/O board. Each RAID server tends to have its own unique configuration. A network having many such uniquely-configured servers is difficult to maintain.
Increasingly, there is a need within the industry for arranging the client/server computer as an off-the-shelf commodity item that can be quickly and inexpensively replaced in case of failure. There is a long felt desire in the industry to avoid customized routings of cables between a stand-alone computer and peripheral sensors. There is a need in the industry for disk drive arrays or other data storage arrays that can be quickly and efficiently serviced in the event of a failure. There is a growing desire in the industry to be able to control all operations of a networked RAID system from a remote control console without adversely affecting normal operations of the network.
Summary of the Invention
The invention helps to attain the above-mentioned objectives by providing a SCSI-coupled module for monitoring and for controlling a SCSI-coupled cluster of devices such as a SCSI-coupled RAID bank.
A structure in accordance with the invention comprises: a cluster of SCSI modules coupled to one another by a SCSI bus, wherein at least one of the SCSI modules has no means for directly reporting to the SCSI bus, the status of power delivered to internal circuitry of the at least one SCSI module or the status of other conditions (e.g., temperature, open door) affecting the operability or security of the at least one SCSI module and wherein a second of the SCSI modules includes status monitoring, reporting and control means for monitoring and directly reporting to the SCSI bus, the status of power delivered to internal circuitry of the at least one SCSI module or the status of other conditions (e.g., temperature) affecting the operability and/or security of the at least one SCSI module. The status monitoring, reporting and control means is optionally provided with control functions so that it can actively control the power delivered to internal circuitry of the at least one SCSI module or the status of other conditions (e.g., temperature, door lockings) affecting the operability and/or security of the at least one SCSI module either in response to commands received over the SCSI bus or on its own initiative.
A method in accordance with the invention comprises the steps of: (a) attaching a status monitoring, reporting and control means to a SCSI bus having a cluster of SCSI modules; (b) operatively coupling the status monitoring, reporting and control means to a power maintenance and/or other environment maintenance subsystems of the cluster; and (c) operating the status monitoring, reporting and control means so that the status monitoring, reporting and control means provides one or more of the following functions: (c.1) providing on-site reports via an on-site indicator means of cluster status and cluster problems to an on-site observer (e.g., by creating appropriate indication patterns on a frontpanel messaging module); (c.2) providing off-site reports via the SCSI bus of cluster status and cluster problems to a remote system supervisor; (c.3) testing the data path integrity of the SCSI bus; (c.4) conveying error history, repair history, usage history and other information about a portable cluster of SCSI modules to which the status monitoring, reporting and control means is attached; (c.5) supporting inventory/asset management functions in a large network containing the SCSI cluster; (c.6) monitoring traffic patterns of SCSI communications to or from members of the cluster; (c.7) switching a configuration of the cluster in response to a sensed degradation event within the cluster; (c.8) monitoring and managing background environmental aspects of cluster operation such as maintaining appropriate temperatures within the cluster, maintaining predefined power levels within the cluster, and assuring system security.
These and other aspects of the invention will be described in more detail below.
Brief Description of the Drawings
The below detailed description makes reference to the accompanying drawings, in which:
FIG. 1A is a generalized block diagram of a non-SCSI to SCSI status transfer system in accordance with the invention;
FIG. 1B is a block diagram of a SCSI-based data access network system (DANS) in accordance with the invention;
FIGS. 2A-2B show schematics of cabinet monitor and control (CMAC) boards in accordance with the invention;
FIG. 3A shows a six drive configuration; and
FIG. 3B shows a bank of drive cabinets each holding eighteen drives.
Detailed Description
Referring to FIG. 1A, there is first shown a generalized block diagram of a non-SCSI to SCSI status transfer system in accordance with the invention. Modules 10, 11, 12, . . . , 15 each include a Small Computer System Interface (SCSI) for enabling SCSI-based data exchange between these modules 10, 11, 12, . . . , 15 in accordance with well known industry standards. Although only four such SCSI modules are shown, it is to be understood that the SCSI data exchange network (or SCSI "channel") can have as many as eight such modules and that each module has a unique SCSI identification number (ID#0 through ID#7). Each module can have within it, as many as 8 uniquely-addressable, SCSI logical units. Thus the SCSI channel can support as many as 64 uniquely-addressable, SCSI logical units.
In the illustrated example, module 10 is assigned SCSI ID#0, module 11 is assigned SCSI ID#1, module 12 is assigned SCSI ID#2, and module 15 is assigned SCSI ID#7. Four additional SCSI modules (not shown) can be inserted between modules 12 and 15 and assigned respective SCSI ID's #3 to #6.
SCSI cables 31-35 interconnect corresponding SCSI modules 10-15 in daisy chain fashion according to well known industry practice. Modules 11-15 are spaced relatively close to one another (they are "clustered") while module 10 is located relatively far (roughly 1 to 25 feet away) from the other modules 11-15. Because of this physical separation, a first power/environment support unit 16 is used to supply electrical power and provide other operational necessities (e.g., cooling) to the cluster of modules 11-15 while a second power/environmental support unit 17 is used to supply electrical power and provide other operational necessities (e.g., cooling) to the out-of-cluster module 10. An electrical/mechanical connection means 36 operatively couples the first power/environmental support unit 16 to the clustered SCSI modules 11-15 while a separate, second electrical/mechanical connection means 37 operatively couples the second power/environmental support unit 17 to separated SCSI module 10.
Module 10 is connected to a system supervisor 2 by means of a communication network 5. Communication between the system supervisor 2 and the remaining cluster of modules 11-15 is substantially limited to that which can be carried over the SCSI network (cables 31-35) to the first module 10, and from there over the communication network 5 to the system supervisor 2.
SCSI modules 11 and 12 do not include means for reporting:, by way of the SCSI network, (1) the status of power delivered to their internal circuitry (e.g., is it at nominal voltage and current, and if not what is the amount of deviation?) or (2) the status of other environmental conditions affecting their operability, such as temperature build-up, or (3) the status of yet other environmental conditions affecting their security, such as their physical removability or actual removal from the cluster.
With regard to the mentioned report items, SCSI communications do not on their own provide definitive answers. If a SCSI module is not responding to SCSI commands, such nonresponsiveness does not specifically indicate whether the cause is due to failure of the SCSI interface, or loss of power, or overheating, or physical removal or disconnect of the module, or some other reason. Because there is no status reporting means in modules 11 and 12, and SCSI communications do not provide definitive answers, the system supervisor 2 has no way of learning about power or environmental problems simply from communications carried out with SCSI modules 11 and 12 over SCSI bus 31-35.
To overcome this problem, a Status Monitoring And ReporTing means 60 (SMARt means 60) is provided within SCSI module 15 for monitoring the status of the first power/environment support unit 16 and the status of nearby modules 11-12, and even its own status, and for reporting the status of these monitored devices to the system supervisor 2 by way of the SCSI network 31-35. Sensors 21, 22, . . . , 25, 26 are attached to respective units 11, 12, . . . , 15 and 16 for monitoring temperature, electrical power levels and other aspects of cluster 11-15 that affect the operatability and/or security of SCSI cluster 11-15. Local sensor lines 51, 52, . . . , 55, 56 respectively connect sensors 21, 22, . . . , 25, 26 to the status monitoring and reporting means 60.
An appropriate intelligence means (e.g., a microcontroller or microcomputer, not shown) is provided within the status monitoring and reporting means (SMARt) 60 for causing it to periodically monitor the status of temperature, electrical power levels and other aspects affecting the operatability and security of SCSI cluster 11-15 and to report worrisome developments to the system supervisor 2 by way of the SCSI network 31-35.
Note that the status monitoring and reporting (SMARt) means 60 is preferably located in the SCSI module 15 that is most distal along the SCSI chain of cables 31-35 from the communication network 5 and the system supervisor 2. The intelligence means (e.g., a microcontroller or microcomputer) within the status monitoring and reporting (SMARt) means 60 can be advantageously used to test the integrity of the data path between the system supervisor 2 and end module 15, that data path including the series of connections made by communication network 5, the SCSI chain of cables 31-35, and the intervening modules 10-12. Appropriate test patterns can be sent from the system supervisor 2 to test for shorts, opens, stuck-at faults and so forth, in the chain of interconnects 5, 31-35. Such techniques for verifying network integrity are well known in the art.
Communications between the status monitoring and reporting (SMARt) means 60 and the system supervisor 2 are carried out using a communications protocol layered on top of the industry standard SCSI protocol. For example, a first one or more bytes of data that is sent during the data transfer phase of a SCSI SEND or RECEIVE operation defines an operation code field (op code) recognizable to one or both of the SMARt means 60 and the system supervisor 2. A following one or more bytes of data that is sent during the data transfer phase of the SCSI SEND or RECEIVE operation defines parameters of the op code. (The op codes and parameters can be inserted in the CDB (command data block) of a SCSI RECEIVE or SEND operation or in a subsequent one or more data blocks.)
More specifically, when the network control console 102 is the initiator of a data exchange operation and wishes to receive information from the SMARt means 60, it sends the corresponding op code and parameters to first module 10 by way of communication network 5. The op code and parameters sent by the network control console 102 are thereafter embedded by module 10 into the CDB (command data block) of a SCSI RECEIVE command which module 10 sends to the status monitoring and reporting means 60 of module 15 by way of SCSI network cables 31-35. The SMARt means 60 analyzes the embedded op code and parameters and responsively returns the desired data during the data phase of the same SCSI RECEIVE operation. If the network control console 102 wishes to ask the SMARt means 60 to perform a particular operation (e.g., to turn on an LED, not shown, that is attached to cluster 11-15), the network control console 102 sends the corresponding op code and parameters to first module 10 by way of communication network 5. The op code and parameters sent by the network control console 102 are thereafter embedded by module 10 into the CDB (command data block) and/or Data Block of a SCSI SEND command which module 10 sends to the status monitoring and reporting means 60 of module 15 by way of SCSI network cables 31-35. The SMARt means 60 analyzes the embedded op code and parameters and responsively executes the requested operation (e.g., turning on the designated LED).
The op codes and parameters sent from the system supervisor 2 to the SMARt means 60 can include, but are not limited to, commands layered on top of a SCSI SEND command having a format Command{Parameterl, Parameter2, . . . } such as: (1) Report{Voltage level at power terminal of, Module11}; (2) Report{Current level at power terminal of, Module12}; (3) Report{Temperature level inside, Module12}; (4) BeginCableTest{Number5}; (5) Report{Status of, AccessDoor6}; (6) Switch{On, LED.sub.-- number, 6}; and so forth. The op codes and parameters sent from the SMARt means 60 to the system supervisor 2 can include, but are not limited to, commands layered on top of a SCSI RECEIVE command such as: (1) Warning{Temperature, above 30.degree. C.}; (2) Warning{-Voltage, below 4.8 VDC); (3) Warning{AccessDoor, Open}; and so forth. Because these op codes and parameters are layered on top of the standard SCSI communications protocol and routed specifically between the status monitoring and reporting (SMARt) means 60 and the system supervisor 2, the OpCodes and {Parameters} do not interfere with other SCSI-based communications between the system supervisor 2 and the remaining modules 10, 11 and 12.
The status monitoring and reporting (SMARt) means 60 can be upgraded to provide active control functions in response to sensed events or commands downloaded from the system supervisor 2. By way of example, in response to a message, Warning{Temperature, above 30.degree. C.} from the SMARt means 60, the system supervisor 2 might respond with an environment control command such Do{Turn, On, ReserveFan}. The upgraded SMARt means 60 will, of course, include appropriate control circuits for carrying out the environmental control actions.
These and other advantages of the architecture shown in FIG. 1A will be better understood by considering the applicability of the architecture to a SCSI-based, data access system.
Referring now to FIG. 1B, a data access network system (DANS) 100 in accordance with the invention comprises as its major components: a local and/or wide area network (LAN/WAN) 105, a host computer 110 and a data storage array subsystem 120, cooperatively coupled as shown with the host computer 110 being sandwiched between the LAN/WAN 105 and the data storage array subsystem 120.
A remotely-located network control console 102 connects by way of the local/wide area network 105 to a network interface module 115 provided within the host computer 110.
A host-internal bus 112 (e.g. EISA or VESA bus) is provided within host computer 110 and operatively coupled to the host-to-network interface module 115. The host-internal bus 112 also connects to a central processing unit (CPU) 111 and to a host-internal memory unit 114 and to a host-to-SCSI adaptor module 117.
A host I/O module 116 is optionally coupled to the internal bus 112 for connecting to one or more serial or parallel input/output devices such as a mouse 116a, a keyboard 116b, and a modem 116c. In this particular embodiment, the modem 116c is advantageously coupled to a wireless paging system comprised of a radio transmitter 106 and a portable paging receiver 103 for the purpose of reporting system problems to a roving administrator as will be explained in more detail below.
A display drive board 113 is further optionally coupled to the internal bus 112 for connecting to an external display (e.g. a Super-VGA monitor). The external display can be used in combination with the mouse device 116a and/or the keyboard 116b and/or another user-input device for enabling on-site interactive communication with the host computer 110.
The components of the host computer 110 are enclosed in an appropriate enclosure 110a (e.g. an IBM-compatible tower). Typically, the host-internal bus 112 is provided on a motherboard together with the host CPU 111 and RAM/ROM portions of the memory unit 114. The host CPU 111 can be an Intel 80486 66 MHz microprocessor or the like. The host-internal memory 114 typically includes a ROM BIOS for power-up booting and sufficient RAM for loading and using desired software packages. The host-internal memory unit 114 will typically also include a host-internal hard disk (not shown) or other appropriate mass storage means for storing host-specific programs and data.
The host-to-network interface module 115 is typically provided on an expansion board which removably connects to an expansion slot of the host-internal bus 112. Module 115 provides appropriate interfacing between the host-internal bus 112 and the host-external communications network 105 as is well known in the art. The LAN/WAN 105 can operate in accordance with an Ethernet protocol or a token ring protocol or other network architectures known in the art.
The host-to-SCSI adaptor module 117 is also typically provided on an expansion board which removably connects to an expansion slot of bus 112. Examples of such SCSI adaptor boards include those made by Adaptec Inc. of California. The SCSI adaptor module 117 will have at least one SCSI channel connector 117a into which a fifty-wire SCSI cable 118a (or a wider SCSI-2 cable) connects. Connection is made through an opening in the host computer enclosure 110a. The SCSI adaptor module 117 can optionally include additional, second, third, or more SCSI channels which are accessed by way of second, third, etc. SCSI channel connectors 117b, 117c, etc. Each of these other SCSI channel connectors 117b, 117c, etc. has its respective SCSI cable 118b, 118c, etc. extending out from the host enclosure 110a.
The data storage array subsystem 120 includes a storage array housing cabinet 121 which houses an array of disk drives 141, 142, etc. and/or an array of other data storage modules (e.g., tape drives).
An internal/external interconnect socket 127 is provided on cabinet 121 for receiving the first-channel SCSI cable 118a (a 50-wire SCSI-1 cable or a 68-wire SCSI-2 cable) and for coupling the SCSI signals found on that cable 118a onto a cabinet-internal SCSI daisy-chaining system 138. The SCSI daisy-chaining system 138 is composed of removable cable segments 138a, 138b and 138c. These three cabinet-internal daisy-chain cable segments, 138a, 138b and 138c, respectively provide SCSI communication from the cabinet internal/external interconnect socket 127 to-and-through a first-cage backplane 133, to-and-through a second-cage backplane 134, and to a CMAC board 150. A power backcable 139 carries electrical power to-and-through the first and second cage backplanes, 133 and 134, for powering a plurality of data storage drives 141, 142, etc. The power backcable 139 also connects to and powers other internal components of subsystem 120 and is supplied from a plurality of redundant and modularly replaceable power supplies 160 also housed in cabinet 121.
Cabinet 121 includes a front access door 121a and a back access door 121b respectively provided at a front and back portions of the cabinet 121. A frontdoor status sensor 122a, such as a microswitch, is provided for detecting whether frontdoor 121a is open or closed. Frontdoor 121a can hinge about the point where sensor 122a is provided, or it can open and close according to other suitable fashions. A backdoor status sensor 122b is similarly provided for detecting the open/closed status of the cabinet back access door 121b.
The number of disk drives 141, 142, etc. or other data storage modules contained within the storage array housing cabinet 121 can be as few as two (2) but it is preferably a number equal to an integer multiple of three such as 3, 6, 9, etc. so that it can support level-5 RAID operations. The number of data storage modules 141, 142, etc. is more preferably a multiple of six such as 6, 12, or 18 for reasons that will become apparent shortly.
When 2 or more data storage modules (141, 142) are provided, it is preferable to provide one or more multi-module support cages 131, 132 within the storage array housing cabinet 121. Each such cage has a pack of 2 or more storage modules (e.g., disk drives) slidably but removably inserted into the cage.
Each cage 131, 132, is itself removable from the storage array housing cabinet 121 such that, when the cage is removed, the pack of data storage modules (e.g., disk drives) 141, 142, etc. contained within the cage is transported without removal from the cage. Also, if there is a CMAC board 150 (described below) attached to the cage, the CMAC board 150 can also be transported without removal from the cage as the cage is removed from the cabinet 121.
In the illustrated embodiment, each of cages 131 and 132 is a tri-disk support cage. A first plurality of as many as three disk drives, 141-143, is inserted into support cage 131 and a second triad of disk drives, 144-146, if present is slidably inserted into the second tri-disk support cage 132. If more drives are to be housed within the storage array housing cabinet 121, additional multi-module support cages (not shown) may be inserted into the cabinet 121 as needed (see FIG. 3B).
First cage 131 has a first printed-circuit board backplane 133 disposed at a rear portion of the cage. The cabinet internal/external interconnect socket 127 removably connects to a left side of the first cage backplane 133 by way of the first daisy-chain cable segment 138a. A left end of the second daisy-chain cable segment 138b removably connects to a right side of the first cage backplane 133. Second cage 132 similarly has a second backplane board 134 disposed at a rear portion of the cage. The right end of the second daisy-chain cable segment 138b removably connects to a left side of the second cage backplane 134. A left end of the third daisy-chain cable segment 138c removably connects to a right side of the first cage backplane 133. A right end of the third daisy-chain cable segment 138c removably connects to the CMAC board 150.
A triad of SCSI signal and power connectors, 133a, 133b and 133c are provided on backplane 133 for slidably but removably making signal and power connections to respective disk drives 141, 142 and 143. Similarly, a triad of SCSI signal/power connectors 134a, 134b, and 134c are provided on the second cage backplane 134 for slidably but removably connecting SCSI signals and power to respective disk drives 144, 145 and 146. (Pin densities of 72 pins per connector or greater are preferred for each of connectors 133a-133c, 134a-134c, so as to allow for expansion from 50-wire SCSI-1 operation to 68-wire SCSI-2 operation.)
Disk drives 141, 142, etc., are modularly replaceable on a "hot-pluggable" basis. Each of drives 141-146 can be inserted into or removed from their respective cages, 131 and 132, by way of the front access door 121a. A frontdoor locking solenoid 124 is provided for selectively locking the front access door 121a in a closed position or allowing it to be opened, in response to an electrical command signal (157).
A plurality of individual-drive locking solenoids 129a-129f are optionally provided for locking respective disk drives 141-146 into respective cages 131 and 132 and preventing unauthorized removal of drives 141-146 from their cages even if the front access door 121a is open. Although not shown, a plurality of microswitches can be included in each cage 131, 132 and operatively coupled to the CMAC board 150 for allowing the CMAC board 150 to determine how many and which slots of each multi-disk support cage 131 are physically filled with a drive. This information can be used to support a rudimentary "asset inventory management" function. Under this function, the CMAC board 150 outputs a report onto the SCSI bus 138 indicating how many drives are contained in the cages 131, 132 and which cage slots are filled.
The cabinet back access door 121b provides access to the modularly replaceable, redundant power supplies 160 and also to a plurality of modularly-replaceable, redundant cooling fans 170 provided within cabinet 121. The redundant power supplies 160 preferably include at least two 70W 110/220 VAC auto sensing power supplies (more preferably 85 Watt 90-240 VAC universal inputting supplies) each providing intelligent 50% load sharing and each switching to full 100%-load support in the event of failure in the other of the power supplies. Each supply should be rated at no less than 65K hours MTBF (Mean Time Between Failure). The redundant cooling fans 170 preferably include at least two exhausting fans rated at 30 CFM each with a noise rating of no more than 28 db each. Each fan should be rated at no less than 65K hours MTBF). The fans are arranged to provide mutually independent direct cooling of the redundant power supplies 160 and the drive cages 131, 132.
The individual disk drives 141, 142, etc., can be physically accessed and, when necessary, quickly replaced by opening the front access door 121a. Replacement is performed by sliding a desired drive 141-146 out from its cage 131, 132 and sliding a new drive into the cage for engagement with the corresponding backplane connector 133a-c or 134a-c. The tri-disk support cages 131 and 132 cannot be removed by way of the front access door 121a. Also, the SCSI daisy-chaining cable segments 138a, 138b and 138c, the power backcable 139, the redundant power supplies 160 and the redundant cooling fans 170 cannot be accessed or removed by way of the front access door 121a. Instead, these latter items can only be accessed for replacement or inspection by way of the cabinet back access door 121b. A backdoor locking solenoid 123 is provided for electronically locking the back access door 121b.
A frontpanel messaging module 126 is provided at a front portion of the disk bank cabinet 121, near front access door 121a. The front panel messaging module 126 includes one or more of the following elements: a liquid crystal display panel (LCD) 126a, a plurality of light emitting diodes (LED's) 126b, a speaker or other audio transducer 126c, and a front panel keyboard 126d.
A cabinet monitor and control (CMAC) board 150 is mounted onto a side of one of card cages 131 or 132 (onto 132 in the illustrated case) and operatively coupled to the cabinet SCSI bus 138. Preferably, the CMAC board 150 terminates one end of the SCSI bus 138 and the host-to-SCSI adaptor module 117 terminates an opposed end of the SCSI bus.
The CMAC board 150 is seen as a SCSI peripheral device on the same SCSI channel (118a) that connects to disk drives 141-146 and to SCSI adaptor board 117. The eight device ID (identification) values on the SCSI channel associated with first SCSI channel connector 117a are allocated as follows in one embodiment: The SCSI adaptor board 117 functions as device ID#0, disk drive 141 functions as device ID#1, drive 142 functions as ID#2, drive 143 functions as ID#3, drive 144 functions as ID#4, drive 145 functions as ID#5, drive 146 functions as ID#6, and the CMAC board 150 functions as device ID#7.
These allocations can be rearranged as desired. In a second embodiment the SCSI adaptor board 117 functions as device ID#7, disk drive 141 functions as device ID#0, drive 142 functions as ID#1, drive 143 functions as ID#2, the CMAC board 150 functions as device ID#3, drive 144 functions as ID#4, drive 145 functions as ID#5, and drive 146 functions as ID#6. The main point to note is that the CMAC board 150 functions as one of the SCSI devices on the same SCSI channel that handles data exchanges of the RAID drives 141, 142, etc.
Sense and control connections are made between the CMAC board 150 and various components of the data storage array subsystem 120 for allowing the CMAC board 150 to sense the status of and/or control the status of various components of subsystem 120.
A first status monitor/control connection 151 is made between the CMAC board 150 and the redundant power supplies 160 for allowing the CMAC board 150 to interrogate the operational status of the power supplies and individually control them. The power supply control functions include switching a particular power supply on or off and adjusting an output voltage or output current parameter of the power supply (e.g., changing the output current itself or changing a current limit or threshold value).
A second status monitor/control connection 152 is made between the CMAC board 150 and the redundant cooling fans 170 for allowing the CMAC board 150 to test and/or control the status of individual ones of these fans 170. The fan control functions include switching a designated fan on or off and switching the fan between different fan speeds. The fan monitoring functions include determining the volume of air moving per unit time through a given fan so as to sense proper operation or the build-up of a blockage in an airway.
A third connection 153 is made between the CMAC board 150 and the backdoor status sensor 122b for allowing the CMAC board 150 to determine whether the back access door 121b is in an open or closed state. A fourth connection 154 is made between the CMAC board 150 and the backdoor locking solenoid 123 for electronically operating the backdoor locking solenoid 123.
A fifth connection 155 connects the CMAC board 150 to one or more temperature sensors 180 distributed about subsystem 120. The temperature sensors 180 can be comprised of thermistors or other appropriate elements located at corresponding areas of cabinet 121. These sensors 180 are used for measuring the temperatures of one or more of the following items: (a) the temperature of the first tri-disk support cage 131 as a whole and/or the temperatures of the individual drives 141-143 found in first cage 131; (b) the temperature of the second tri-disk support cage 132 as a whole and/or the individual temperatures of the drives 144-146 found within second cage 132; (c) the temperature of heat-sensitive electronic components (e.g., integrated circuit packages) found on the CMAC board 150; (d) the temperatures of the redundant power supplies 160 taken as a whole or individually; and (e) the air intake and/or air outlet temperature of each of the redundant fans 170.
A sixth status monitor/control connection 156 is made between the CMAC board 150 and the frontpanel messaging module 126 for allowing the CMAC board 150 to output visual indications on the visual indicating devices 126a and/or 126b of the panel 126. Connection 156 can also be used for outputting alarm or other audio output signals through the audio transducer (speaker) 126c. In some instances it may be desirable to have device 126c operate not merely as an audio output device but also as audio input/output transducer, in which case bidirectional audio signals (such as two-way digitized speech or tone-keyed signals) may be carried over connection 156 between CMAC board 150 and audio transducer 126c.
The sixth status monitor/control connection 156 can be also used to monitor the status of panel keyboard 126d and to transfer keystroke entries to the CMAC board 150.
A seventh connection 157 is made between CMAC board 150 and the frontdoor locking solenoid 124 for allowing the CMAC board 150 to control solenoid 124.
An eighth status monitoring connection 158 is made between CMAC board 150 and the frontdoor status sensor 122a for allowing the CMAC board 150 to detect whether the cabinet front access door 121a is in an open or closed state.
When the individual-drive locking solenoids 129a-129f are present, corresponding connections 159a through 159f are made from the solenoids to the CMAC board 150 for allowing the CMAC board 150 to selectively lock any one or more of the drives 141-146 within its cage and thus prevent unauthorized removal. Also, when the above-mentioned "asset inventory management" microswitches are present for detecting which cage slots are filled or not filled with a drive, further appropriate connections (not shown) are made from those switches to the CMAC board 150.
Although not specifically shown, it should now be apparent to those skilled in the art from the above that other status monitor/control connections can be made between the CMAC board 150 and various additional parts of the data storage array (RAID) subsystem 120 for further detecting unusual movements, lights, sounds, voltages, or other significant signals emanating either from the mass storage drives 141-146 themselves or from their surrounding environment.
The environment sense connections 151-159 of the CMAC board 150 should be removably connected to the CMAC board 150, so that in an event where the CMAC board 150 has to be removed and/or replaced, with or without its cage 132, this operation can be carried out easily and quickly.
FIG. 2A shows a block diagram of the major components found on the CMAC board 150. The CMAC board 150 comprises a SCSI interface module 201 that operatively connects to the cabinet SCSI daisy-chaining system 138. Board 150 receives its operating power from the power backcable 139. The SCSI interface module 201 connects to an on-board micro-controller 202 (or microprocessor). The microcontroller 202 can be a Zilog Z86E21.TM. microcontroller available from Zilog Inc. of California or a like device. The Z86E21.TM. is a single-chip microcontroller containing 8 kilobytes of EEPROM (Electrically Erasable and re-Programmable Read Only Memory) and 236 bytes of general purpose RAM (Random Access Memory). The chip also contains 32 dedicated I/O pins, a full duplex serial port and two counter timers. The serial I/O port on the microcontroller 202 can be used for future expansion of the system. The dedicated I/O pins of the microcontroller 202 connect to a status monitoring/-controlling interface circuit 203 further provided on board 150. The status monitoring/-controlling interface circuit 203 provides level translation and other appropriate coding or decoding functions for interfacing the microcontroller 202 with the above-mentioned status monitor/control connections 151-159.
The SCSI interface module 201 is preferably a Western Digital WD33C93A.TM. single chip SCSI interface controller available from Western Digital Inc. of California or a like device. The WD33C93A.TM. includes an internal microcontroller, a register task file, and SCSI interface logic. All low level SCSI bus protocol operations including SCSI arbitration, bus phase changes, and receive and transfer commands are handled by the WD33C93A.TM. chip (201). When the SCSI interface module 201 needs higher level assistance, it issues an interrupt signal to the Z86E21.TM. microcontroller 202. Software loaded into the internal memory of microcontroller 202 services the interrupt. The software within microcontroller 202 also handles handshaking and message protocol operations for receiving messages from or transferring commands to the SCSI interface module 201. The software loaded into microcontroller 202 comes by way of the SCSI daisy-chaining system 138 or from an add-on ROM chip (not shown). This downloaded software provides appropriate access to the status monitor/-control connections 151-159 and enables some or all of the various operations described below. Such software is well within the purview of those skilled in the art and no special preferred version of such software exists at this time.
If the on-chip memory of the microcontroller 202 is insufficient, an external memory module 205 can be added to the CMAC board 150 for storing instructions and/or data as desired.
FIG. 2B shows one embodiment 150' in more detail. A VI-sourced termination module 137 couples to SCSI bus 138' adjacent to the SCSI port of a WD33C93A.TM. chip (201'). A local 8-bit wide data bus 210 is shared by the WD33C93A.TM. chip (201') and a Z86E21.TM. microcontroller (202'). The local data bus 210 connects to two banks of 32K by 8 bit memory, 205a and 205b. A shared control bus 215 selects the data bus of one bank or the other and provides read/write control. The Z86E21.TM. microcontroller (202') supplies address signals to the 64K memory module 205a/205b by way of a 16 bit wide address bus 216. Units 201' and 202' are clocked by a 10 MHz oscillator 217. A first interface circuit 218 (e.g., 74LS240) supplies 8 bits of straight or decoded sense data to the Z86E21.TM. microcontroller (202'). A second interface circuit 219 (e.g., 7406's) outputs 8 bits of control data from the Z86E21.TM. microcontroller (202'). An RS232 interface circuit 220 (e.g., ICL232) provides bidirectional expansion for further monitor and control operations.
The memory module 205a/205b preferably includes nonvolatile (battery-backed) RAM or Flash-EEPROM which can be loaded with power-up self-diagnostic software, SCSI bus integrity testing software and other software modules that are to be resident independently of the connection to the host computer 110 and the local/wide area network 105. Error history, repair history and usage history data is also preferably stored in the nonvolatile portion of memory module 205a/205b so that one can determine how old the accompanying drives are, how many hours of use time they have accumulated, how many and what kind of errors were encountered either recently or over the life of each drive and what prior repair operations have been performed on each drive.
Also, software should be included in a nonvolatile portion of one or both of the Z86E21.TM. microcontroller (202') and the memory module 205a/205b for managing receipt of non-SCSI status reports from the interface circuitry (218-220) and for layering the status report into a data portion of a SCSI RECEIVE command block, and for sending the command block to the SCSI interface chip 201' for execution. Furthermore, software should be included in a nonvolatile portion of one or both of the Z86E21.TM. microcontroller (202') and the memory module 205a/205b for responding to predefined opcodes layered into a data portion of a received SCSI SEND command, where the opcodes ask the CMAC board 150 to report the status of a condition defined by the opcodes or parameters attached to the opcodes, and for causing the microcontroller to respond by transferring the requested status into a data portion of a SCSI RECEIVE command block, and sending the command block to the SCSI interface chip 201' for execution.
Moreover, download support software should be included in the memory of the CMAC board 150' for allowing the download and execution of additional software instructions from one or both of the host computer 110 and the network control console 102.
While the description of FIG. 1B is directed to a six drive configuration, it should be apparent that the described features are applicable to mass storage banks having many more such drives. Groups of three or six drives each are preferably bundled into each individual cabinet 121. Plural groups of six drives may be each bundled into a single cabinet (see FIG. 3B).
FIG. 3A shows a first possible arrangement in which a single SCSI channel is used for connecting with up to six mass storage drives 141-146 and a CMAC board 150. The seven SCSI devices 141-146, 150 are all enclosed within a double full height enclosure 221. The enclosure 221 is shaped as a vertical tower and the tri-disk support cages (131,132, not shown) are stacked one on the next. The front panel messaging module 126 is positioned at a top left portion of the tower 221. The CMAC board 150 is fastened to a left side of the top cage (131).
The CMAC board 150 is sized to allow the combination of cage 131 and attached board 150 to slip into a standard 51/4 form factor, full-height drive bay of an IBM-PC compatible computer. Such a full-height bay typically measures 5.75 inches in width, 3.35 inches in height and 8 inches in depth. The three individual disk drives 141-143 that slide into cage 131 each measure 1.0 inch or less in height and have form factors of 3.5 inch or less (e.g. Conner CP-30540.TM. disk drives available from Conner Peripherals Inc.). This arrangement leaves at least 0.35 inch of height space to be used for providing tolerance spacing between the drives and tolerance spacing between the cage and the full-height bay.
In one embodiment a main body portion of the tri-disk support cage is 3.30 inches high, 4.75 inches wide and 7 inches deep. The one inch space between the 4.75 inch width of the cage body and the 5.75 inch width of the full-height drive bay is used to accommodate the CMAC board 150 and other electronics boards (such as a status messaging board, not shown) that may also mount to the side of the cage body and fit within the one inch space.
FIG. 3B shows another possible arrangement in which each enclosure 321, 322, 323, etc. of multiple enclosures houses eighteen mass storage drives. Three SCSI channels are used for each enclosure to access the corresponding 18 drives and their three associated CMAC boards (150.1, 150.2 and 150.3). The CMAC boards 150.1-150.3 mount on the left sides of the left drive cages. A common messaging panel 326 is positioned near a top left portion of each enclosure 321, 322, etc. Each enclosure 321, 322, etc. is a triple full height, double wide enclosure capable of receiving six cage assemblies where each of the cage assemblies is tri-disk support cage such as 131.
The multiple-enclosure arrangement shown in FIG. 3B will typically be enclosed in a utility closet within an office building or warehouse. A client/server computer 110 will be housed in a first tower enclosure 110a while tower enclosures 321, 322, 323, etc. house the corresponding mass storage drives of client/server computer 110. This arrangement may be repeated many times in a large warehouse full of mass storage drives and host computers.
The utility closet or warehouse will be typically situated far away from the person or persons who are in charge of monitoring and maintaining the RAID system. If a particular enclosure (110, 321, 322 or 323) needs physical servicing, a moderately-skilled technician is dispatched to the utility closet or warehouse for performing field replacement services on a modular level. In other words, if a particular disk drive (e.g. 141) has failed, the technician will be dispatched to remove the failed drive (e.g. 141) and insert a substitute drive. If one of the redundant power supplies 160 has failed, the technician will remove the failed power supply and replace it with a fresh power supply. A similar replacement operation is used for redundant cooling fans 170.
Servicing preferably takes place in a "hot-pluggable" state, meaning that power continues to be applied to the other non-failing units as servicing takes place and the other units continue to operate in a normal or semi-degraded fashion while the failed unit is replaced.
In the case where the double wide enclosures 321, 322, etc., are used, each enclosure preferably includes at least two 200W 110/220 VAC modular/user replaceable power supplies (and more preferably 250W 90-240 VAC universal inputting supplies) with intelligent load sharing and switching to full-load support in the event of a single supply failure. The supplies are powered by independent AC input lines (not shown). At least three modular/user replaceable exhaust fans (not shown) are provided with a rating of 33 CFM each and with a noise rating of no greater than 28 db each. Minimum MTBF for the power supplies and fans should be at least 65K hours.
Physical access to the internal components of the data storage array subsystem (120 or 320) during normal operations is blocked by closing doors 121a, 121b and actuating the frontdoor and backdoor solenoids 124 and 123 to lock their respective access doors 121a and 121b. Even though the components are physically locked away, a remotely-located network supervisor (102) can nonetheless monitor conditions within the data storage array subsystem (120 or 320) by routing status queries from the network control console 102, over the network 105, through the network interface 115 and through the SCSI adaptor module 117 to a desired CMAC board 150. The transmitted queries can enquire about the operational status of each of the redundant power supplies 160, each of the redundant fans 170, the open/close status of the front and back access doors 121a and 121b, temperature conditions in various parts of the data storage array subsystem (120/320), and so forth.
In response, the addressed CMAC board 150 uses its status monitoring connections 151-158 to detect the desired status. The CMAC board 150 transmits the requested status information back over the cabinet SCSI daisy-chaining system 138 and through SCSI connector 118a, SCSI adaptor board 117, host bus 112, network interface 115 and network 105, to the inquiring console 102. In one embodiment, returned status and alert reports are encoded into an industry-standard format known as SNMP (Simple Network Management Protocol).
If excessive thermal build-up is detected within an enclosure (121 or 321), a corrective command can be sent from the remote console 102 to the corresponding CMAC board 150 asking the CMAC board 150 to switch on an additional cooling fan 170 or increase the speed of an already turned on fan in order to better cool the enclosure.
If an access door (121a or 121b) is sensed as being ajar, an alarm command can be sent from remote console 102 to the CMAC board 150 of the affected enclosure 121/321 for actuating an audible alarm signal through audio transducer 126c and/or a flashing visual indication to visual indicators 126a and/or 126b so as to frighten away an unauthorized intruder and/or to help a later-arriving technician identify the specific enclosure having a door that is not properly closed. Upon arrival, the technician will easily be able to determine which enclosure is affected by listening for the audible alarm and/or looking for blinking visual indicators (e.g. blinking LED's 126b). The visual and/or auditory alarms might be arranged to indicate specifically which door is being sensed as being ajar, the front, the back or both.
The same alarming system can be used for isolating an enclosure containing a component that needs other types of servicing. In the case where the LCD panel 126a is present, the network supervisor may choose to send a message to the technician from remote console 102, by way of the network 105 and the CMAC board 150, such that the message is displayed on the LCD panel 126a. The message might indicate exactly what component needs to be inspected or replaced.
It is possible that a system supervisor or service technician will be away from, or not monitoring the network control console 102, when a condition worthy of alarm is detected by the CMAC board 150 and signalled to the console 102. In such a case, it is advantageous to install paging software in the host computer 110 for sending a corresponding pager message to the portable paging receiver 103 of the system supervisor and/or service technician when an alarm of sufficient priority is detected passing from the CMAC board 150 to the network control console 102. A telephone touch-tone service may be used to not only alert the absent/roving supervisor/technician to call in, but in some cases, touch-tone codes can be used to generate specific messages such as "power supply 002 failed in cabinet 003" on a LCD (liquid crystal display) panel of the portable paging receiver 103. Then, the absent/roving supervisor/technician can immediately proceed to the trouble site without having to make further inquiries through a network control console 102.
The CMAC board 150 may be programmed to act as a requester for any one of drives 141-146 so that the operability of any one of these drives 141-146 may be periodically tested by the CMAC board 150 without burdening the throughput of the LAN/WAN 105. This testing operation is preferably carried out when the CMAC board 150 senses that the cabinet SCSI daisy-chain system 138 is in a quiescent state and no communication is ongoing between the local SCSI adaptor board 117 and the drives 141-146 that are to be monitored by the CMAC board 150. The CMAC board 150 can then try to engage in a limited conversation with each of drives 141-146 just to see whether each of those drives appears to be minimally operational. If one of the drives appears to be non-operational, the CMAC board 150 can send a warning message over the cabinet SCSI daisy-chaining system 138 and through the LAN/WAN network 105 to the network supervising console 102 warning of the problem.
Another function which the CMAC board 150 can undertake when the cabinet SCSI daisy-chain system 138 is in a quiescent state is inventory-taking. Each data storage module within the storage array housing cabinet 121 can be provided with an ability to report its brand name (e.g., Conner CP30540.TM.) over the SCSI bus 138 to the CMAC board 150 in response to a version/capacity request output by the CMAC board 150. The response can included not only the brand name of the data storage module, but also its serial number and details about its storage capacity such as how many bytes are used and how many are free in the module as a whole or even in specific directories. A similar capability reporting function can be built into the modularly-replaceable redundant power supplies 160 and other environment support devices (e.g., the fans 170) of storage array housing cabinet 121. The CMAC board 150 will periodically take inventory (preferably during a quiescent state) of how many drive-support slots in each cage 131, 132 are full or empty, what brand or brands data storage modules are contained in the storage array housing cabinet 121, what power supply and cooling capabilities are available, and so forth. This inventory report can be downloaded to the network control console 102 either periodically or on request so that the manager of a large, ever changing network can get an idea of what is "out there" in terms of number of units, their storage capacities, how much free space is left, where potential storage overflows or underutilizations are developing, and so forth.
Additionally, the CMAC board 150 can be given the task of logging problems for each brand/kind of data storage module and/or power supply and/or other device within its storage array housing cabinet 121. Then when the network supervisor (102) asks for an inventory report, the CMAC board 150 can provide a log of problems for each device. This will help the network supervisor (102) to better perform his or her asset inventory and management duties, part of which is knowing what is "out there" and how is each component of the network behaving in terms of mean-time-between failures, utilization, etc.
Also, in some networks, there are different storage configurations at each site. One six-pack of disk drives might be operating as two level-5 RAID banks while another 6-pack is operating as three level-0 RAID banks. The CMAC board 150 can be asked to keep track of the configuration within its domain and to report this configuration to the network manager periodically or on request.
Logging operations can take place when the host-to-SCSI adaptor module 117 has control of the SCSI channel and is engaged in conversation with one of the plural drives 141-146. The CMAC board 150 may listen in to determine traffic patterns, to detect fatal error messages or the occurrence of a number of non-fatal transaction errors exceeding a predetermined value.
If a fatal error or an excessive number of nonfatal errors is detected for one of the drives 141-146, the CMAC board 150 may even be programmed to initiate a recovery and rebuild operation. It may be programmed to at the same time send an alarm message to the network supervisor through one or both of the network control console 102 and the portable paging receiver 103.
In some instances, a cabinet 121 can have 3 drives operating as a level-5 RAID system and one or two unused drives sitting in reserve. If the CMAC board 150 senses that one of the active RAID drives is beginning to have an error rate exceeding a predefined threshold, the CMAC board 150 can initiate a copy of the data in the failing drive into one of the spare drives, and at the appropriate moment (a bus quiescent moment), switch the back-up drive into the RAID triad (level-5) while removing the failing drive. The CMAC board 150 would inform the host computer 110 of this event-driven switch so that the host readjusts the SCSI ID's that define the RAID bank. The CMAC board 150 would also inform the network control console 102 of this switch so that the network manager is aware of the problem and the reconfiguration. If there are only 3 drives in the RAID bank and one drive is failing, the CMAC board 150 might switch the configuration from RAID level-5 to RAID level-0 (providing there is enough free storage space to support the switch without loss of data).
With regard to background monitoring of traffic patterns, this information can be useful to the network manager so the manager can determine whether additional storage capacity should be added to the network; whether traffic should be redirected in order to more homogeneously load system resources; and/or whether usage traffic to a drive containing licensed software is sufficiently high or low that it would be worthwhile to upgrade or downgrade the terms and cost of a corresponding software-usage licensing agreement.
Those skilled in the field of RAID systems know that RAID level zero operation can be implemented with just two disk drives, each mirroring the data contained in the other. RAID level 5 operation can be implemented with as few as three drives 141-143. If one of the drives fails, the remaining non-failed drives can continue to supply user-desired information, although perhaps at a degraded performance rate. If yet another disk drive fails in the RAID 0 or RAID 5 configuration, it will no longer be possible to rebuild the lost information. Accordingly, when a first failure occurs, it is desirable to bring the failed drive back into an operational mode as soon as possible in order to minimize the danger of permanent data loss. The operational mode might be attained by simply rebuilding the lost data in the failed drive from the data held in the non-failed drives. Such a rebuild can be used without need for replacement, providing that the failure mechanism is of a temporary nature. If the failure mechanism is of a more permanent nature (e.g. a head crash), the failed drive needs to be physically replaced with a new, operational drive and the data of the removed drive needs to be rebuilt into the replacement drive. The CMAC board 150 may be programmed to initiate a rebuild without replacement on its own rather than burdening the network controller 102 with overseeing such a task. A set of indicator lights may be provided on the CMAC board 150 or on the frontpanel messaging module 126 to indicate the data integrity status of each drive. By way of example, a lit green LED might indicate that the corresponding drive is good, red might indicate it is bad and flashing red or green might indicate it is being rebuilt. If a rebuild operation is unsuccessful after one or a predetermined number of tries, the CMAC board 150 can then alert the network controller 102 that higher level intervention is required.
The system 100 shown in FIG. 1B may be advantageously used to make sure that routine installation, maintenance and module replacement operations are carried out in a relatively fool proof manner and that unauthorized personnel are deterred from physically accessing the components within each enclosure 121/321. When an authorized technician is dispatched to replace a failed component in a data storage array subsystem 120/320, the technician is first asked to locate the affected enclosure by looking for a certain pattern of visual and/or auditory indicators (e.g. flashing red LED's and/or a particular alarm tone). Then the technician is asked to key in a pre-arranged password into the panel keyboard 126d of the thusly identified enclosure. A new and unique password can be periodically downloaded over the network 105 into each CMAC board 150 (150.1, 150.4, 150.7 etc., see FIG. 3B) in order to increase system security and assure that the technician opens the correct enclosure. If the technician keys in the correct password, the CMAC board 150 responds by unlocking a predesignated one or both of the front and back access doors 121a and 121b. The network supervisor can command the CMAC board 150 from the remote console 102 as to which of the cabinet access doors, 121a or 121b or both, is to be opened. If a wrong password is entered, the CMAC board 150 might activate a warning alarm.
Upon detecting that the appropriate access door 121a and/or 121b is being opened, the CMAC board 150 can issue a command over the SCSI bus 138 to the enclosed drives 141-146 to place them in a quiescent state. The quiescent state temporarily blocks the SCSI adaptor module 117 within the host 110 from accessing drives 141-146. The CMAC board 150 takes control of the SCSI bus 138/118a at this time. This avoids the danger that noise will be introduced into data transfers due to connector jiggle or other mechanisms while the technician slides a failed component out and replaces it with a fresh component. The invocation of this temporary quiescent state is optional.
The network supervisor (102) can send a message to the technician by way of display panel 126a to indicate exactly which drive is to be replaced. Alternatively, identifying LED's may be placed on individual ones of drives 141-146 or on the side of the tri-disk cage 131. The CMAC board 150 can be instructed from the remote console 102 to cause the LED on the failed unit to blink in a particular pattern, thereby helping the technician to more quickly isolate the failed unit.
The optional drive locking solenoids 129a-129f may be used to provide a further safeguard against removal of an incorrect drive. The network supervisor (102) can command the CMAC board 150 to unlock the solenoid 129a, 129b, etc., of only the failed drive while leaving the remaining solenoids 129 in the locked position. Thus, even if the technician inadvertently tries to remove the wrong drive, the technician will be blocked from doing so by the drive locking solenoid 129. Only when the technician pulls on the appropriate drive will the technician find that this drive is easily removable from its corresponding support cage, 131 or 132.
Although not shown, it is to be understood that similar indicating means can be provided for allowing the CMAC board 150 to indicate which of the redundant power supplies 160 or redundant cooling fans 170 has failed and for preventing the technician from incorrectly removing another one of these units which has not failed.
When a service job is reported to have been completed, by for example the technician keying in a completion code into key panel 126d, the network supervisor 102 can use the CMAC board 150 to run a plurality of status and diagnostic checks; making sure that each of the drives 141-146 is operational; making sure that the front and back access doors 121a-121b are properly closed and locked, making sure that each of the redundant power supplies 160 is operational, making sure that each of the redundant cooling fans 170 is operational and making sure that temperature or other environmental conditions within the enclosure 121 have returned to normal. The network supervisor (102) can then signal the technician by way of LCD panel 126a and/or LEDs 126b that the enclosure is now fully operational and that the technician may now leave the service site and proceed to a next maintenance job.
Once the enclosure checking procedure is complete, the CMAC board 150 can be commanded from the remote console 102 to take drives 141-146 out of the quiescent state and to again let the host SCSI adaptor module 117 have full access to the data within drives 141-146. It should be understood of course, that the quiescent state is an optional operation. Each of drives 141-146, power supplies 160 and cooling fans 170 is "hot-pluggable", meaning that it can be replaced while the remaining components within the affected enclosure 121 continue to operate either at full or at a slightly degraded performance rate.
The above scenario is merely an example of the type of locally-observed and remotely-observed status indications that can be provided by the CMAC board 150. The frontpanel keyboard 126d can be used to locally-initiate status reporting operations or diagnostic operations or access-grant and reconfiguration operations in place of remotely-initiation by the network supervisor (102) of such operations.
In some cases, it may be desirable to remove an entire cage (e.g., 132), with a CMAC board 150 still attached to the cage, from the storage array housing cabinet 121 and to return the removed unit to the shop for failure analysis and repair. This may be the case for example when a failure occurs in a non-replaceable portion of a cage 131, 132 such as in its backplane 133, 134 or in the cabinet monitor and control (CMAC) module 150 itself. The CMAC board 150 may be provided with nonvolatile storage (e.g., flash EEPROM) in which it stores failure history information such as the time of failure, what operations were being performed at and shortly before the failure and so forth. This information may help technicians to better diagnose and repair a problem. When a repaired cage is returned to the field, the nonvolatile portion of the CMAC board 150 can be programmed to contain repair-history information. The error and repair history of each cage can then travel with the cage as it is pulled from one system and later installed in another. An overly-troublesome cage or drive can be isolated through the use of this information and weeded out from the network. In this way the network supervisor can avoid repeated re-attachment of an overly-troublesome cage or drive to the network.
The CMAC board 150 can be used advantageously during first time installation as well as in post-installation repair and recovery. When a new data storage array is first attached to a host computer 110, some of the connections 117a, 127, etc. may be faulty or a fault may lie in one of the cables 118, 138a, 138b, etc. The CMAC board 150 is preferably situated at the terminal end of the SCSI bus 138 furthest away from the host-to-SCSI adaptor module 117.
On power-up, the CMAC board 150 performs self-diagnostics, making sure its own power supply, CPU, memory, I/O circuits and so forth are operational. If a failure is detected, a predefined pattern of lights or other indicators is displayed on frontpanel messaging module 126 so that an on-site technician can determine what has gone wrong.
After power-up self-diagnostics are completed by the CMAC board 150, a data path integrity check can be initiated by the on-site technician keying-in a predefined test code into the frontpanel keyboard 126d or the CMAC board 150 can automatically enter such a test phase on its own. In the data integrity test phase, the CMAC board 150 looks for a predefined set of test patterns to be transmitted from the host-to-SCSI adaptor module 117 to the CMAC board 150 over the SCSI bus 138. The test patterns are selected as known in the art to detect and/or isolate common connection problems such as shorts, opens, stuck-ats, etc. If a data path integrity fault is detected during this phase, the CMAC board 150 will flash a corresponding and predefined pattern of lights and/or alarm tones and/or other indicators out over the frontpanel messaging module 126. This will indicate to the on-site technician that a data path integrity problem exits and perhaps even isolate its location. Once the data path integrity is verified as being fault-free appropriate software can be downloaded into the CMAC board 150 from the network control console 102 for carrying out various other functions.
By way of summary, the above disclosure has shown among other things: (a) how a cabinet monitor and control (CMAC) board 150 can be used to provide on-site reports of the status and problems of a data storage array to an on-site technician (e.g., by creating appropriate indication patterns on the frontpanel messaging module 126) and on-site control over various operational aspects of the array; (b) how the CMAC board 150 can be used to provide off-site reports of array status and problems to a remote system supervisor (102, 103) and remote control over various operational aspects of the array; (c) how the CMAC board 150 can be used to test the data path integrity of the SCSI bus; (d) how the CMAC board 150 can be used to convey error history, repair history and other information about a portable pack of data storage modules (e.g., disk drives) to which the board 150 is attached; (e) how the CMAC board 150 can be used to support inventory/asset management functions in a large network; (f) how the CMAC board 150 can be used to monitor usage traffic patterns among an array of data storage modules and/or switch storage configurations in response to degradation events; (g) how the CMAC board 150 can be used to monitor and manage environmental aspects of array operation such as maintaining appropriate temperature, maintaining power levels, and assuring system security in a background mode without burdening the network supervisor (102) or the host computer (110) with such tasks.
The above disclosure is to be taken as illustrative of the invention, not as limiting its scope or spirit. Numerous modifications and variations will become apparent to those skilled in the art after studying the above disclosure.
By way of example, one or more tri-drive cages 131, 132 can be installed in the drive bay of host computer 110 rather than in separate cabinet 121. The CMAC board 150 would be attached to the side of one such cage 131 or 132 in this instance and a host-internal connector 117d of SCSI adaptor board 117 would be used to communicate with the host-internal CMAC board and its associated drives 141, 142, etc.
By way of further example, the redundant array of data storage units does not have to be composed of magnetic disk drives. It can include re-writable optical drives, tape drive units or other forms of redundant data storage. A triad or six-pack of disk drives can have a half-height DAT (Digital Audio Tape) drive attached thereto for performing data backup. The DAT drive could co-exist on the same SCSI ID as the CMAC board 150 or have its own SCSI ID number. (In the latter case, the number of disk drives on the SCSI channel would have to be reduced to 5.) The CMAC board 150 can be programmed to support tape back-up operations as well as RAID operations. Moreover, one can have a bank of SCSI-responsive DAT drives in place of a bank of disk drives, with the DAT drives providing either primary or back-up storage. The CMAC board 150 can be used to manage such a DAT bank in similar manner to a disk bank.
Given the above disclosure of general concepts and specific embodiments, the scope of protection sought is to be defined by the claims appended hereto.
Claims
What is claimed is:
1. A digital data storage system comprising: a SCSI bus; a plurality of individually transportable data storage units each operatively but removably coupled to the SCSI bus for transferring data stored or data to-be-stored in said data storage unit over the SCSI bus in accordance with SCSI protocol, at least two of said storage units defining a RAID cluster wherein file data is preserved even if one storage unit within the cluster fails; a status defining module operatively coupled to the SCSI bus for transferring status-defining data over the SCSI bus in accordance with the SCSI protocol; a cabinet for securely enclosing the plural data storage units and the status defining module, the cabinet having one or more lockable access doors, at least one of the doors defining a means by way of which one or more of the plural data storage units may be physically accessed for disconnection from the SCSI bus and removal from the cabinet; one or more door locking mechanisms for locking one or more closed ones of the lockable access doors; and one or more door status sensors operatively coupled to the one or more access doors for detecting whether each access door is in an open or closed state, wherein said status defining module includes accessibility reporting means, operatively coupled to said one or more door status sensors, for interrogating the one or more door status sensors and for outputting a door-status report onto the SCSI bus as part of said status-defining data, the door-status report indicating whether each of the one or more access doors is open or closed; and further wherein: one or more of said door locking mechanisms is an automatic door locking mechanism operatively coupled to the status defining module for automatically locking a respective one or more closed ones of the lockable access doors in response to a respective lock activating signal sent by the status defining module; and the status defining module includes means for sending the respective lock activating signal to each respective automatic door locking mechanism.
2. A digital data storage system according to claim 1 wherein said one or more automatic door locking mechanisms are further for automatically unlocking a respective one or more locked ones of the lockable access doors in response to a respective unlocking signal sent by the status defining module; and the status defining module further includes means for sending the respective unlocking signal to each respective automatic door locking mechanism.
3. A digital data storage system according to claim 2 wherein: the status defining module further includes lock-status reporting means for sending a lock-status report over said SCSI bus as part of said status-defining data, the lock-status report indicating whether a given one or more of the automatic door locking mechanisms is in a locked or unlocked state.
4. A digital data storage system comprising: a SCSI bus; a plurality of individually transportable data storage units each operatively but removably coupled to the SCSI bus for transferring data stored or data to-be-stored in said data storage unit over the SCSI bus in accordance with SCSI protocol, at least two of said storage units defining a RAID cluster wherein file data is preserved even if one storage unit within the cluster fails; a status defining module operatively coupled to the SCSI bus for transferring status-defining data over the SCSI bus in accordance with the SCSI protocol; a cabinet for securely enclosing the plural data storage units and the status defining module, the cabinet having one or more lockable access doors, at least one of the doors defining a means by way of which one or more of the plural data storage units may be physically accessed for disconnection from the SCSI bus and removal from the cabinet; one or more door locking mechanisms for locking one or more closed ones of the lockable access doors; and one or more door status sensors operatively coupled to the one or more access doors for detecting whether each access door is in an open or closed state, wherein said status defining module includes accessibility reporting means, operatively coupled to said one or more door status sensors, for interrogating the one or more door status sensors and for outputting a door-status report onto the SCSI bus as part of said status-defining data, the door-status report indicating whether each of the one or more access doors is open or closed; and further wherein: said cabinet is further for securely enclosing two or more modularly-replaceable redundant power supplies; said lockable access doors include first and second automatically lockable access doors that are automatically lockable in response to signals output by the status defining module; the first automatically lockable access door is usable for removing one or more of the data storage units but not usable for removing the two or more modularly-replaceable redundant power supplies; and the second automatically lockable access door is usable for removing one or more of the modularly-replaceable redundant power supplies.
5. A digital data storage system according to claim 4 wherein: said cabinet is further for securely enclosing two or more removable cages, each cage supporting a subset of said plurality of individually transportable data storage units; the first automatically lockable access door is not usable for removing the two or more removable cages; and the second automatically lockable access door is usable for removing one or more of the removable cages.
6. A data storage and communications system comprising: (a) a first computer contained in a first enclosure and functioning as a data-transfer bridge between an external local area network and an external first SCSI bus; (b) a first plurality of removable data storage units located outside said first enclosure, each of said data storage units being operatively but removably coupled to the first SCSI bus for transferring data stored or data to-be-stored in said data storage unit over the SCSI bus in accordance with SCSI protocol, (b.1) wherein each given one of the first plurality of data storage units has no means for directly reporting to the first SCSI bus, the status of a local condition of the given data storage unit, said local condition including at least one member selected from the group consisting of: (b.1a) a local power voltage level of the given data storage unit; (b.1b) a local power current level of the given data storage unit; (b.1c) a local temperature level of the given data storage unit; and (b.1d) a manual removability status of the given data storage unit; (b.1e) a physical presence status of the given data storage unit; and said system further comprising: (c) a first status defining module operatively coupled to the first SCSI bus for transferring status-defining data over the first SCSI bus in accordance with the SCSI protocol, the status defining module being further operatively coupled to said first plurality of data storage units for periodically monitoring one or more of said local conditions of each given data storage unit and for issuing one or more status reports indicative of the monitored one or more local conditions of each given data storage unit over the first SCSI bus in accordance with the SCSI protocol; (a.1) wherein the first computer does not periodically monitor the one or more of said local conditions of each given data storage unit among said first plurality of data storage units independently of said periodic monitoring by the first status defining module.
7. A data storage and communications system according to claim 6 (a.2) wherein the first computer does not have means for periodically monitoring the one or more of said local conditions of each given data storage unit.
8. As data storage and communications system according to claim 6 and further comprising: (d) a second computer located outside the first enclosure and operatively coupled to the local area network so as to communicate with the first status defining module by way of the first SCSI bus and further by way of the first computer functioning as said data-transfer bridge.
9. A data storage and communications system according to claim 8 wherein (c.1) said first status defining module is further for recognizing on its own when a periodically monitored one or more of said local conditions of each given data storage unit is at or degrading towards a predefined, unacceptable state and for responsively issuing a corresponding one or more warning reports indicative of the unacceptable state or degradation thereto over the first SCSI bus in accordance with the SCSI protocol to the second computer by way of the first computer.
10. A data storage and communications system according to claim 6 (a.2) wherein the first computer is further coupled to a wireless paging system; and (c.1) said first status defining module is further for recognizing on its own when a periodically monitored one or more of said local conditions of each given data storage unit is at or degrading towards a predefined, unacceptable state and for responsively issuing a corresponding one or more warning reports indicative of the unacceptable state or degradation thereto over the first SCSI bus in accordance with the SCSI protocol to the wireless paging system by way of the first computer.
11. A data storage and communications system according to claim 6 wherein: (aa) the first computer further functions as a data-transfer bridge between said external local area network and an external second SCSI bus; and said data storage and communications system further comprises: (bb) a second plurality of removable data storage units located outside said first enclosure, each of said second data storage units being operatively but removably coupled to the second SCSI bus for transferring data stored or data to-be-stored in said data storage unit over the second SCSI bus in accordance with SCSI protocol, (bb.1) wherein each given one of the second plurality of data storage units has no means for directly reporting to the second SCSI bus, the status of a local condition of the given data storage unit, said local condition including at least one member selected from said group of local conditions; (cc) a second status defining module operatively coupled to the second SCSI bus for transferring status-defining data over the second SCSI bus in accordance with the SCSI protocol, the status defining module being further operatively coupled to said second plurality of data storage units for periodically monitoring one or more of said local conditions of each given data storage unit among said second plurality and for issuing one or more status reports indicative of the monitored one or more local conditions of each given data storage unit over the second SCSI bus in accordance with the SCSI protocol; (aa.1) wherein the first computer does not periodically monitor the one or more of said local conditions of each given data storage unit among said second plurality of data storage units independently of said periodic monitoring by the second status defining module.
12. A data storage and communications system according to claim 6 wherein at least two of said storage units define a RAID cluster, said RAID cluster being one wherein file data is preserved even if one storage unit within the cluster fails.
13. A data storage and communications system according to claim 6 wherein said status defining module comprises: nonvolatile writable memory means for nonvolatily maintaining a usage history for the first plurality of removable data storage units.
14. A data storage and communications system according to claim 6 wherein said status defining module comprises: serial communication means for carrying serial signals representative of said monitored local conditions.
15. A data storage and communications system according to claim 6 wherein said status defining module comprises: nonvolatile writable memory means for nonvolatily maintaining a history of messaging errors occurring along said first SCSI bus.
16. A data storage and communications system according to claim 6 further comprising: a second enclosure housing said first plurality of removable data storage units and also housing said first status defining module; wherein said first SCSI bus carries SCSI signals between the first and second enclosures; and wherein said second enclosure has a tower configuration within which the first plurality of removable data storage units are disposed in a stacked formation.
17. A data storage and communications system according to claim 16 wherein: (aa) the first computer further functions as a data-transfer bridge between said external local area network and an external second SCSI bus; and said data storage and communications system further comprises: (bb) a second plurality of removable data storage units located outside said first enclosure and housed in the second enclosure, each of said second data storage units being operatively but removably coupled to the second SCSI bus for transferring data stored or data to-be-stored in said data storage unit over the second SCSI bus in accordance with SCSI protocol, (bb.1) wherein each given one of the second plurality of data storage units has no means for directly reporting to the second SCSI bus, the status of a local condition of the given data storage unit, said local condition including at least one member selected from said group of local conditions; (cc) a second status defining module operatively coupled to the second SCSI bus for transferring status-defining data over the second SCSI bus in accordance with the SCSI protocol, the status defining module being further operatively coupled to said second plurality of data storage units for periodically monitoring one or more of said local conditions of each given data storage unit among said second plurality and for issuing one or more status reports indicative of the monitored one or more local conditions of each given data storage unit over the second SCSI bus in accordance with the SCSI protocol; (aa.1) wherein the first computer does not periodically monitor the one or more of said local conditions of each given data storage unit among said second plurality of data storage units independently of said periodic monitoring by the second status defining module; and said system further comprises: a common messaging panel provided on the second enclosure and operatively coupled to the first and second status defining modules for providing a local-site interface between the outside of said second enclosure and the first and second status defining modules.
18. A data storage and communications system according to claim 17 wherein: said common messaging panel outputs an audible alarm signal for identifying the second enclosure as an enclosure that is requesting servicing.
19. A data storage and communications system according to claim 17 wherein: said common messaging panel outputs a flashing visual alarm signal for identifying the second enclosure as an enclosure that is requesting servicing.
20. A data storage and communications system according to claim 17 wherein: said common messaging panel includes key input means operatively coupled to said first and second status defining modules for allowing a service technician to manually supply a pre-defined access request code to the first and second status defining modules; and a verification copy of said pre-defined access request code is downloadable to one or both of the first and second status defining modules by way of the respective first and second SCSI buses.
21. A data storage and communications system according to claim 20 wherein: each of said first and second status defining modules includes means for placing one or more units in the respective first and second plurality of data storage units into a quiescent state.
Patent Citations (12)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3660832 | 1972-05-01 | Hoshall | |
| US3704363 | 1972-11-01 | Salmassy et al. | |
| US5148432 | 1992-09-01 | Gordon et al. | |
| US5303214 | 1994-04-01 | Kulakowski et al. | |
| US5337413 | 1994-08-01 | Lui et al. | |
| US5337414 | 1994-08-01 | Hashemi et al. | |
| US5367647 | 1994-11-01 | Coulsen et al. | |
| US5367670 | 1994-11-01 | Ward et al. | |
| US5502838 | 1996-03-01 | Kikinis | |
| US5548784 | 1996-08-01 | Easley, Jr. et al. | |
| US5586250 | 1996-12-01 | Carbonneau et al. | |
| EPX547844A2 | 1993-06-01 |