US20040148329A1 - Storage device system and storage device system activating method - Google Patents

Storage device system and storage device system activating method Download PDF

Info

Publication number
US20040148329A1
US20040148329A1 US10/673,162 US67316203A US2004148329A1 US 20040148329 A1 US20040148329 A1 US 20040148329A1 US 67316203 A US67316203 A US 67316203A US 2004148329 A1 US2004148329 A1 US 2004148329A1
Authority
US
United States
Prior art keywords
storage device
processor
control section
device system
management terminal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/673,162
Inventor
Hiroshi Ogasawara
Yutaka Takata
Naotaka Kobayashi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Assigned to HITACHI, LTD. reassignment HITACHI, LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KOBAYASHI, NAOTAKA, OGASAWARA, HIROSHI, TAKATA, YUTAKA
Publication of US20040148329A1 publication Critical patent/US20040148329A1/en
Priority to US12/348,088 priority Critical patent/US7882206B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present invention relates to a novel storage device system capable of being connected on a plurality of different types of networks, or more particularly, to a method of controlling activation of the storage device system.
  • a technology for connecting a system including a disk array composed of a plurality of disk drives (hereinafter, a storage device system) to an information processing system over a leased line network (or a storage area network (SAN)) so as to realize fast access to a large amount of information stored in the storage device system.
  • a storage device system a disk array composed of a plurality of disk drives
  • SAN storage area network
  • communications equipment conformable to a fibre channel protocol is generally used to construct a network.
  • a network system referred to as a network attached storage (NAS) has been developed for realizing access at a file level to a storage device system by interconnecting the storage device system that includes a plurality of storage devices and an information processing system over a network that adopts a TCP/IP (which stands for transmission control protocol/Internet protocol) protocol.
  • TCP/IP transmission control protocol/Internet protocol
  • the information processing system can gain a file-level access to the storage device system.
  • a large-scale NAS accommodating a storage device system which is managed based on a RAID (redundant arrays of inexpensive disks) technology and includes a file system is attracting attention because it provides an enormous storage resource called a midrange-class or enterprise-class resource.
  • Patent Document 1 Japanese Unexamined Patent Application Publication No. 2002-351703
  • the conventional NAS is realized by connecting an information processing system, which has a TCP/IP communication feature and the capability of a file system, to a storage device system that has neither the TCP/IP communication feature nor the capability of a file system.
  • An installation space for the connected information processing system is therefore needed.
  • the information processing system and storage device system are often interconnected over a SAN because of the necessity of fast communication. Communication control equipment and a communication control feature must therefore be included.
  • a main object of the present invention is to provide a novel storage device system capable of being connected to a plurality of different types of networks, and to provide a storage device control system and a method of controlling activation of the storage device system which are needed to invent the storage device system.
  • a storage device system in accordance with the present invention comprises: a plurality of storage devices in which information is stored; a storage device control section that controls storage of information in the plurality of storage devices; and a connection unit connected to the storage device control section.
  • the storage device system further comprises a first communication control section including: a first processor that is connected on a first network external to the storage device system, that converts information of a first form, which is received over the first external network, into information of a second form, and that issues a request for access to the plurality of storage devices; and a second processor that accesses the plurality of storage devices via the connection unit and storage device control section in response to the access request issued from the first processor, and that controls activation of the first processor.
  • FIG. 1 is a block diagram showing the overall configuration of a storage device system in accordance with an embodiment of the present invention
  • FIG. 2 is a block diagram showing the configuration of a management terminal included in the embodiment
  • FIG. 3 shows a physical disk management table employed in the embodiment
  • FIG. 4 shows an LU management table employed in the embodiment
  • FIG. 5 shows the appearance of the storage device system in accordance with the embodiment
  • FIG. 6 shows the appearance of a storage device control system included in the embodiment
  • FIG. 7 shows the hardware configuration of a channel control unit CHN included in the embodiment
  • FIG. 8 is an explanatory diagram concerning the contents of data stored in a memory included in the embodiment.
  • FIG. 9 shows metadata employed in the embodiment
  • FIG. 10 shows lock data employed in the embodiment
  • FIG. 11 shows a communication path linking a CPU and an I/O processor which are included in the channel control unit CHN included in the embodiment;
  • FIG. 12 shows data to be transferred from the I/O processor to the CPU according to the embodiment
  • FIG. 13 shows data to be transferred from the CPU to the I/O processor according to the embodiment:
  • FIG. 14 shows the hardware configuration of the channel control unit CHN which is included in the embodiment and which has an internal LAN;
  • FIG. 15 shows a disk control unit included in the embodiment
  • FIG. 16 shows the software configuration of the storage device system in accordance with the embodiment.
  • FIG. 17 is a flowchart describing activation and installation performed in the storage device system in accordance with the embodiment.
  • FIG. 1 is a block diagram showing the overall configuration of a storage device system in accordance with the embodiment.
  • a storage device system 600 has a storage device control system 100 and storage devices 300 .
  • the storage device control system 100 controls the storage devices 300 according to a command received from any of information processing systems 200 .
  • the storage device system 100 receives an input/output request for data from any of the information processing systems 200 , and performs processing for the purpose of receiving or transmitting data stored in the storage devices 300 .
  • Data is stored in a logical volume or logical unit (LU) that is a storage area logically defined in a physical storage area provided by a disk drive included in each of the storage devices 300 .
  • LU logical volume or logical unit
  • the storage device control system 100 transfers various commands, which are used to manage the storage device system 600 , to or from the information processing systems 200 .
  • Power supplies 111 supply power to the storage device system 600 , and are realized with batteries connected to an external power supply.
  • a plurality of power supplies is mounted in the storage device system for the purpose of redundancy.
  • the storage device system 600 is physically divided into two or more power supply groups in terms of power supply.
  • first to fourth channel control units 110 belong to a first power supply group
  • fifth to eighth channel control units 110 belong to a second power supply group.
  • All redundant components of the storage device system 600 are classified into two or more power supply groups.
  • components belonging to a group of redundant components are designed not to belong to the same power supply group.
  • the power supplies 111 are divided into two or more groups.
  • Power is supplied from an external power supply to the two or more groups of power supplies 111 over independent cables.
  • the two or more groups of power supplies 111 supply power to the assigned groups of power supplies.
  • the two or more groups of power supplies 111 each include a plurality of power supplies. Since the storage device system 600 has redundancy, if a certain power supply breaks down, the storage device-system 600 can keep operating. Furthermore, even if external power supply to the two or more groups of power supplies 111 is discontinued, the storage device system 600 can keep operating.
  • the information processing systems 200 are computers each having a central processing unit (CPU) and a memory.
  • the CPU included in each of the information processing systems 200 runs various programs, whereby various features are implemented.
  • the information processing systems 200 may be, for example, personal computers, workstations, or main frame computers.
  • the first to third information processing systems 200 are connected to the storage device control system 100 over a local area network (LAN) 400 .
  • the LAN 400 may be the Internet or a leased line network. Communications over the LAN 400 between the first to third information processing systems 200 and the storage device control system 100 are carried out based on, for example, a TCP/IP protocol.
  • the first to third information processing systems 200 transmit a data access request (data input/output request for requesting data in units of a file) (hereinafter, a file access request) to the storage device system 600 while designating a filename.
  • a backup device 910 is connected on the LAN 400 .
  • the backup device 910 is a disk device such as a magneto-optical disk (MO), CD-rewritable (CD-R) disk, or DVD-RAM, or a tape device such as a digital audio tape (DAT) cartridge, cassette tape, open tape, or cartridge tape.
  • a tape device such as a digital audio tape (DAT) cartridge, cassette tape, open tape, or cartridge tape.
  • DAT digital audio tape
  • the backup device 910 may be connected to the first information processing system 200 . In this case, backup data of data stored in the storage devices 300 can be acquired via the first information processing system 200 .
  • the storage device control system 100 includes first to fourth channel control units 110 .
  • the storage device control system 100 uses the first to fourth channel control units 110 to receive file access requests issued from the first to third information processing systems 200 respectively over the LAN 400 .
  • a network address for example, IP address
  • the first to fourth channel control units behave as if to be independent network attached storage (NAS) devices, and can independently provide the first to third information processing systems 200 with NAS service.
  • NAS network attached storage
  • the first to fourth channel control units 110 will be called the channel control units CHN 110 .
  • the storage device system 600 includes the first to fourth channel control units 110 that independently provide NAS service, NAS servers that are conventionally realized with independent computers are integrated into the one storage device system 600 . Consequently, the storage device system 600 can be managed as a whole. Maintenance work including determination or control of various settings, life management, and version management can be efficiently carried out.
  • Power is supplied from the power supplies 111 to the channel control units 110 via the storage device control system 100 . Since the channel control units 110 can be dismounted from the storage device control system 100 , power supply to the channel control units 110 is discontinued by physically removing the channel control units 110 from the storage device control system 100 . Moreover, when the channel control units 110 are mounted in the storage device control system 100 , power supply to the channel control units 110 is enabled.
  • the channel control units 110 have a power supply circuit. When the power supply circuit is controlled by running a program implemented by a plurality of LSIs mounted on each of the channel control units 110 , power supply to the circuit elements incorporated in the channel control unit can be started or discontinued.
  • Each of the first to fourth channel control units 110 included in the storage device control system 100 included in the present embodiment is realized with: hardware formed on circuit boards that are integrated into a unit; and software including an operating system (OS) to be run by the hardware, and an application program to be run on the OS or an executable object code to be executed by the hardware.
  • OS operating system
  • the features that are conventionally implemented by part of hardware are realized by software.
  • the storage device system 600 of the present embodiment can therefore be operated flexibly, and meet diverse and varied users' needs so as to provide delicate service.
  • the third and fourth information processing systems 200 are connected to the storage device control system 100 via a storage area network (SAN) 500 .
  • the SAN 500 is a network over which data is transferred in units of a block, which is a management unit of data stored in the storage areas offered by each storage devices 300 , between the storage devices 300 and the third and fourth information processing systems 200 . Communications over the SAN 500 between the third and fourth information processing systems 200 and the storage device control system 100 are performed based generally on a fibre channel protocol.
  • the third and fourth information processing systems transmit a data access request (hereinafter, block access request), which requests access to data in units of a block, to the storage device system 600 according to the fibre channel protocol.
  • block access request data access request
  • a backup device 900 supporting the SAN is connected to the SAN 500 .
  • the information processing system communicates with the storage device control system 100 over the SAN 500 , backup data of data stored in the storage devices 300 is stored in the backup device 900 supporting the SAN.
  • the fifth information processing system 200 is connected to the storage device control system 100 without the intervention of a network such as the LAN 400 or SAN 500 .
  • the fifth information processing system 200 may be formed with, for example, a main frame computer. Communications between the fifth information processing system 200 and storage device control system 100 are achieved based on a communications protocol, for example, the FICON (which stands for fibre connection)®, ESCON (which stands for enterprise system connection)®, ACONARC (which stands for advanced connection architecture)®, or FIBARC (which stands for fibre connection architecture)®.
  • the fifth information processing system 200 transmits a block access request to the storage device system 600 according to the communications protocol.
  • the storage device control system 100 communicates with the fifth information processing system 200 using the seventh and eighth channel control units 110 .
  • the seventh and eighth channel control units 110 will be called the channel control units CHA 110 .
  • a storage device system 610 located at a remote place (secondary site) away from the installation site (primary site) of the storage device system 600 is connected on the SAN 500 .
  • the storage device system 610 is utilized as a system into which data is copied by a replication or remote copy feature that will be described later.
  • the storage device system 610 may be connected to the storage device system 600 over a communication network such as the SAN 500 or an ATM (which stands for asynchronous transfer mode) network.
  • a communication network such as the SAN 500 or an ATM (which stands for asynchronous transfer mode) network.
  • channel control units 110 having an interface (channel extender) that permits use of the communication network are adopted as the channel control units 110 .
  • the storage devices 300 include numerous disk drives (physical disks), and provide the information processing systems 200 with a storage area. Data is stored in a logical unit (LU) that is a storage area logically defined on a physical storage area provided by the disk drives.
  • LU logical unit
  • the disk drives any of various disk drives including, for example, a hard disk drive, a flexible disk dive, and a semiconductor storage device can be adopted.
  • the storage devices 300 may be formed with a disk array composed of a plurality of disk drives. In this case, the storage area provided for the information processing systems 200 is formed with a plurality of disk drives managed as a redundant array of inexpensive disks (RAID).
  • RAID redundant array of inexpensive disks
  • the storage device control system 100 and the storage devices 300 may be, as shown in FIG. 1, directly connected to each other or may be connected to each other over a network. Furthermore, the storage devices 300 may be designed as an integral part of the storage device control system 100 .
  • the LUs offered by the storage devices 300 includes a user LU accessible to the information processing systems 200 and a system LU for use in controlling the channel control units 110 .
  • An OS to be run in the channel control units CHN 110 is also stored in the system LU.
  • the channel control units 110 are associated with the LUs. In other words, accessible LUs are determined for the respective channel control units 110 . Otherwise, the plurality of channel control units 110 may share the same LU.
  • the user LU and system LU may be called a user disk and a system disk respectively.
  • the storage device control system 100 comprises the channel control units 110 , a common memory 120 , a cache memory 130 , disk control units 140 , a management terminal 160 , and a connection unit 150 .
  • the channel control units 110 include a communication interface via which the channel control units communicate with the information processing systems 200 , and have the capability to transfer a data input/output command to or from the information processing systems 200 .
  • the channel control units CHN 110 receive a file access request from the first to third information processing systems 200 . Consequently, the storage device system 600 provides the first to third information processing systems 200 with NAS service.
  • the channel control units CHF 110 that refer to the fifth and sixth channel control units receive a block access request conformable to the fibre channel protocol from the third and fourth information processing systems 200 . Consequently, the storage device system 600 provides the third and fourth information processing systems 200 with data storage service permitting fast access.
  • the channel control units CHA 110 receive a block access request, which conforms to the FICON, ESCON, ACONARC, or FIBARC protocol, from the fifth information processing system 200 . Consequently, the storage device system 600 provides a mainframe computer such as the fifth information processing system 200 with data storage service.
  • the channel control units 110 are interconnected together with the management terminal 160 over the internal LAN 151 . Consequently, a microprogram or the like to be run by the channel control units 110 can be transmitted from the management terminal 160 and installed in the channel control units.
  • the configuration of the channel control units 110 will be detailed later.
  • connection unit 150 is connected to the channel control units 110 , common memory 120 , cache memory 130 , and disk control units 140 . Transfer of data or a command among the channel control units 110 , common memory 120 , cache memory 130 , and disk control units 140 is achieved via the connection unit 150 .
  • the connection unit 150 is formed with, for example, a switch such as a super-fast crossbar switch that suits data transmission because of its fast switching, or a bus. Since the channel control units 110 are interconnected via the switch, compared with the conventional configuration that NAS servers realized with respective computers are interconnected over a LAN, the efficiency in communications among the channel control units 110 has greatly improved. Moreover, fast file sharing and fast failover can be achieved.
  • the common memory 120 and cache memory 130 are storage memories shared by the channel control units 110 and disk control units 140 .
  • the common memory 120 is used mainly to store control information and commands, while the cache memory 130 is used mainly to store data.
  • a data input/output command a certain channel control unit 110 has received from a certain information processing system 200 is a Write command.
  • the channel control unit 110 writes the Write command in the common memory 120 , and writes written data, which has been received from the information processing system 200 , in the cache memory 130 .
  • the disk control units 140 monitor the common memory 120 . When the disk control units 140 detects that the Write command has been written in the common memory 120 , the disk control units 140 read the written data from the cache memory 130 in response to the command, and write the data in the storage devices 300 .
  • a data input/output command a certain channel control unit 11 has received from a certain information processing system 200 is a Read command.
  • the channel control unit 110 writes the Read command in the common memory 120 , and reads data, which is requested with the Read command sent from the information processing system 200 , from the cache memory 130 . If data requested with the Read command is not written in the cache memory 130 , the channel control unit 110 or disk control units 140 read the data, which is requested with the Read command, from the storage devices 300 , and writes the data in the cache memory 130 .
  • the common memory 120 and cache memory 130 are included independently of the channel control units 110 and disk control units 146 .
  • the present embodiment is not limited to this mode.
  • the common memory 120 and cache memory 130 may be broken up and distributed into the channel control units 110 and disk control units 140 .
  • the connection unit 150 connects the channel control units 110 and disk control units 140 which include the distributed portions of the broken up common memory and cache memory.
  • the disk control units 140 control the storage devices 300 .
  • the disk control units 140 write data in the storage devices 300 in response to a data Write command any of the channel control units 110 has received from any of the information processing systems 200 .
  • the disk control units 140 convert a data access request, which is transmitted from any of the channel control units 110 and requests access to an LU by designating the logical address of the LU, into a data access request that requests access to a physical disk by designating the physical address of the physical disk. If the physical disks included in the storage devices 300 are managed as a RAID, data is accessed according to the principle of the RAID.
  • the disk control units 140 extend control to manage a duplicate of data stored in the storage devices 300 or create a backup thereof.
  • the disk control units 140 extend control so as to store a duplicate of data stored in the storage device system 600 located at the primary site into the other storage device system 610 located at the secondary site (replication or remote copy) for the purpose of preventing loss of data in case of a disaster.
  • the disk control units 140 are interconnected together with the management terminal 160 over a communication network such as the internal LAN 151 , and can therefore communicate with one another. Consequently, a microprogram or the like to be run by the disk control units 140 can be transmitted from the management terminal 160 and installed in the disk control units 140 .
  • the configuration of the disk control units 140 will be described later.
  • the management terminal 160 is a computer that maintains or manages the storage device system 600 .
  • the arrangement of physical disks can be determined, an LU to be employed can be designated, and a microprogram to be run in the channel control units 110 can be installed.
  • the arrangement of physical disks included in the storage devices 300 it means that, for example, the number of physical disks can be increased or decreased, or the RAID levels can be changed (from RAID level 1 to RAID level 5 ).
  • the management terminal 160 can be used to check the operating state of the storage device system 600 , to locate a broken region, to install an OS to be run by the channel control units 110 , or to perform any other work. Moreover, the management terminal 160 is connected to an external maintenance center over a LAN or a telephone line. The management terminal 160 can therefore be used to monitor if a failure occurs in the storage device system 600 or to immediately cope with a failure. Occurrence of a failure is notified by, for example, an OS, an application program, or driver software. The notification is performed based on the HTTP protocol or simple network management protocol (SNMP), or by electronic mail.
  • SNMP simple network management protocol
  • the above determination or extension of control is directed by an operator using as a user interface a Web page provided by a Web server realized with the management terminal 160 .
  • the operator or the like handles the management terminal 160 so as to determine an object of failure monitoring or the contents thereof or determine a failure notification destination.
  • the management terminal 160 may be incorporated in the storage device control system 100 or may be disposed externally. Moreover, the management terminal 160 may be formed with a computer dedicated to maintenance or management of the storage device control system 100 and storage devices 300 , or may be formed with a general-purpose computer provided with a maintenance/management feature.
  • FIG. 2 is a block diagram showing the configuration of the management terminal 160 .
  • the management terminal 160 comprises a CPU 161 , a memory 162 , a port 163 , a recording medium reader 164 , an input device 165 , an output device 166 , and a storage device 168 .
  • the CPU 161 is responsible for control of the entire management terminal 160 .
  • the CPU 161 implements the capability of a Web server.
  • a physical disk management table 162 a , an LU management table 162 b , and the program 162 c are stored in the memory 162 .
  • the physical disk management table 162 a is a table used to manage physical disks (or disk drives) included in the storage devices 300 .
  • FIG. 3 shows the physical disk management table 162 a .
  • FIG. 3 lists physical disks bearing disk numbers 001 to 006 among numerous physical disks included in the storage devices 300 .
  • a storage capacity, a RAID level, and a use situation are specified relative to each physical disk.
  • the LU management table 162 b is a table used to manage LUs logically defined on the physical disks.
  • FIG. 4 shows the LU management table 162 b .
  • FIG. 4 lists LUs bearing LU numbers 1 to 3 among numerous LUs defined on the storage devices 300 . A physical disk number, a storage capacity, and a RAID level are specified relative to each LU.
  • the recording medium reader 164 is a device for reading a program or data from a recording medium 167 .
  • the read program or data is stored in the memory 162 or storage device 168 . Consequently, the program 162 c recorded in the recording medium 167 can be read from the recording medium 167 using the recording medium reader 164 , and stored in the memory 162 or storage device 168 .
  • a flexible disk, a CD-ROM, or a semiconductor memory can be adopted as the recording medium 167 .
  • the recording medium reader 162 may be incorporated in the management terminal 160 .
  • the storage device 168 is, for example, a hard disk drive, a flexible disk drive, or a semiconductor storage device.
  • An operator or the like uses the input device 165 to enter data that is transferred to the management terminal 160 .
  • a keyboard or a mouse is adopted as the input device 165 .
  • the output device 166 is a device for transmitting information to outside.
  • a display or printer is adopted as the output device 166 .
  • the port 163 is connected on the internal LAN 151 , whereby the management terminal 160 can communicate with the channel control units 110 or disk control units 140 . Moreover, the port 163 may be connected on the LAN 400 or connected on a telephone line.
  • the management terminal 160 is connected to the power supplies 111 . Power is supplied from the power supplies 111 to the management terminal 160 .
  • FIG. 5 shows the appearance of the storage device system 600 in accordance with the present embodiment.
  • FIG. 6 shows the appearance of the storage device control system 100 .
  • the storage device system 600 in accordance with the present invention has the storage device control system 100 and storage devices 300 put in respective housings.
  • the housings accommodating the storage devices 300 are located by the both sides of the housing accommodating the storage device control system 100 .
  • the storage device control system 100 has the management terminal 160 located in the center of the face thereof.
  • the management terminal 160 is shielded with a cover. As shown in FIG. 6, when the cover is opened, the management terminal 160 becomes usable.
  • the management terminal 160 shown in FIG. 6 is formed as a so-called notebook personal computer. Alternatively, the management terminal 160 may have any other form.
  • slots in which the channel control units 110 are inserted are formed below the management terminal 160 . Circuit boards in which the channel control units 110 are implemented are inserted in the slots.
  • the storage device system 600 in accordance with the present embodiment has, for example, eight slots. Referring to FIG. 5 and FIG. 6, guide rails are formed so that the channel control units 110 can be smoothly inserted in the eight slots. When the channel control units 110 are inserted in the slots along the guide rails, the channel control units 110 are mounted in the storage device control system 100 . Moreover, the channel control units 110 inserted in the slots can be pulled forwards along the guide rails and thus removed.
  • the channel control units 110 include the channel control units CHN 110 , CHF 110 , and CHA 110 .
  • the channel control units 110 are interchangeable in terms of a size, the locations of the connectors, and the pin configurations of the connectors. Any of the channel control units 110 can be mounted in the eight slots. Consequently, for example, the channel control units CHN 110 may be mounted in all the eight slots. Otherwise, for example, as shown in FIG. 1, four channel control units CHN 110 , two channel control units CHF 110 , and two channel control units CHA 110 may be mounted in the eight slots. Moreover, a slot in which no channel control unit 110 is mounted may be included.
  • the channel control units 110 are provided as circuit boards that can be mounted in the slots, that is, identical units.
  • Each of the identical units may be composed of a plurality of circuit boards. Namely, even if a unit is composed of a plurality of circuit boards, as long as the circuit boards are interconnected and integrated into a unit, and can be mounted all together in a slot formed in the storage device control system 100 , the unit is encompassed in the concept of one of identical circuit board.
  • the other components of the storage device control system 100 including the disk control units 140 and common memory 120 are mounted on the back of the storage device control system 100 , though they are not shown in FIG. 5 and FIG. 6.
  • the storage device control system 100 includes fans 170 used to release heat dissipated from the channel control units 110 .
  • the fans 170 are located on the top of the storage device control system 100 , and also disposed above the slots of the channel control units 110 .
  • a system and a device having conventional configurations and being sold as, for example, SAN products can be utilized as the storage device control system 100 and storage devices 300 respectively which are put in the housings.
  • the existing system can be utilized readily.
  • the storage device system 600 of the present embodiment can be constructed readily by utilizing existing products.
  • the channel control units CHN 110 , CHF 110 , and CHA 110 coexist in the storage device system 600 . Consequently, a storage device system capable of being connected on different types of networks can be constructed. Specifically, the storage device system 600 is connected on the LAN 400 using the channel control units CHN 110 , and connected on the SAN 500 using the channel control units CHF 110 , and can therefore be called an SAN/NAS-integrated storage device system.
  • the storage device system 600 uses, as mentioned above, the channel control units CHN 110 to receive a file access request from the first to third information processing systems 200 , and provides the first to third information processing systems 200 with NAS service.
  • FIG. 7 shows the hardware configuration of the channel control units CHN 110 .
  • the hardware of each channel control unit CHN 110 is one unit that will be called an NAS board.
  • the NAS board includes one circuit board or a plurality of circuit boards. More particularly, the NAS board accommodates a network interface 111 , an input/output controller 114 , board coupling connectors 116 , communication connectors 117 , and a file server 800 . These circuit elements are integrated into one unit.
  • the input/output controller 114 includes a nonvolatile RAM (NVRAM) 115 and an input/output (I/O) processor 119 .
  • NVRAM nonvolatile RAM
  • I/O input/output
  • Power is supplied from the power supplies 111 included in the storage device system 600 to each of the channel control units CHN 110 via a power supply connector 750 .
  • Each of the channel control units CHN 110 includes a power supply control circuit 751 and a hardware register 752 that controls the power supply control circuit 751 .
  • start or disconnection of power supply to the input/output controller 114 and file server 800 can be controlled.
  • hardware-like actions including rebooting of the input/output controller 114 or file server 800 or shift to a diagnosis mode can be controlled by modifying the values specified in the hardware register 752 .
  • the I/O processor 119 in the input/output controller can control like hardware the start or disconnection of power supply to the CPU 112 included in the file server 800 , the rebooting, or the shift to the diagnosis mode.
  • the CPU 112 in the file server 800 may control the start or disconnection of power supply to the I/O processor 119 in the input/output controller, the rebooting, and the shift to the diagnosis mode.
  • the network interface 111 includes a communication interface via which the channel control unit communicates with the information processing systems 200 .
  • Each of the channel control units CHN 110 receives a file access request sent from any of the information processing systems 200 according to, for example, a TCP/IP protocol.
  • Communication connectors 117 are connectors via which the channel control unit communicates with the information processing systems 200 .
  • the communication connectors 117 included in each of the channel control units CHN 110 are connectors via which the channel control units CHN 110 can be connected on the LAN 400 , and which are conformable to the Ethernet®.
  • the file server 800 includes a CPU 112 , a memory 113 , a basic input/output system (BIOS) 801 , and a nonvolatile RAM 804 .
  • the CPU 112 is responsible for control to be extended in order to allow the own channel control unit CHN 110 to act as a NAS board.
  • the CPU 112 controls a file sharing protocol such as the NFS (which stands for network file system) or CIFS (which stands for common Internet file system) and a TCP/IP protocol.
  • the CPU 112 analyzes a file access request that designates a file, converts data, which is treated in units of a file into control information stored in the memory 113 using a conversion table (not shown) that lists the data in relation to the LUs defined in the storage devices 300 . Moreover, the CPU 112 produces a data writing or reading request that requests writing or reading of data in or from an LU defined in the storage devices 300 , or transmits the data writing or reading request to the I/O processor 119 .
  • the BIOS 801 is software that when the power supply of the own channel control unit CHN 110 is turned on, is loaded in the memory 113 and executed first in the course of activating the CPU 112 .
  • the BIOS 801 is stored in a nonvolatile medium, for example, a flash memory and included in the own channel control unit CHN 110 .
  • the CPU 112 executes software translated by the BIOS 801 and stored in the memory 113 so as to initialize or diagnose relevant components. Furthermore, the CPU 112 issues a directive such as a command to the I/O processor 119 via the BIOS 801 so as to store a predetermined program, for example, a boot for loading an OS in the memory 113 .
  • the boot for loading an OS places a major portion of the OS stored in the storage devices 300 in the memory 113 , whereby the OS is activated in the CPU 112 . Consequently, the CPU 112 can perform processing to allow the own channel control unit CHN 110 to act as a file server.
  • the file server 800 has the nonvolatile RAM 804 in which a network boot loader conformable to the PXE (which stands form preboot execution environment) standard or the like is stored, and can perform network booting that will be described later.
  • Various programs and data items are stored in the memory 113 .
  • Various programs for example, metadata 730 and a lock table 720 shown in FIG. 8, and an NAS manager 706 shown in FIG. 16 are stored in the memory 113 .
  • the metadata 730 is information produced in association with a file managed by a file system.
  • the metadata 730 contains, for example, an address in a LU in which the data in a file is stored, the data size, and other information specifying the storage place of the file.
  • the metadata 730 may contain information of a file size, an owner, and a time instant of update.
  • the metadata 730 may be produced in association not only with a file but also with a directory.
  • FIG. 9 shows an example of the metadata 730 .
  • the metadata 730 is stored in the LUs defined in the storage devices 300 .
  • the lock table 720 is a table used to exclusively control access to a file gained by the first to third information processing systems 200 .
  • the exclusive control enables the first to third information processing systems 200 to share the same file.
  • FIG. 10 shows the lock table 720 .
  • the lock table 720 includes a file lock table 721 and an LU lock table 722 .
  • the file lock table 721 is a table indicating whether a file is locked. If a certain file is opened by any of the information processing systems 200 , the file is locked. The other information processing systems 200 are inhibited from accessing the locked file.
  • the LU lock table 722 is a table indicating whether each LU is locked. If any of the information processing systems 200 accesses a certain LU, the LU is locked. The other information processing systems 200 are inhibited from accessing the locked LU.
  • the input/output controller 114 transfers data or a command to or from the disk control units 140 , the cache memory 130 , the common memory 120 , and the management terminal 160 .
  • the input/output controller 114 includes the I/O processor 119 and nonvolatile RAM 115 .
  • the I/O processor 119 is formed with, for example, a microcomputer implemented in one chip.
  • the I/O processor 119 controls transfer of a data writing or reading request, which is issued to an LU defined in the storage devices 300 , and data, and relays communication between the CPU 112 and disk control units 140 .
  • the nonvolatile RAM 115 is a nonvolatile memory in which a program based on which the I/O processor 119 extends control are stored. The contents of the program stored in the nonvolatile RAM 115 are written or rewritten in response to a directive issued from the management terminal 160 or the NAS manager 706 that will be described later.
  • FIG. 11 shows a concrete example of a communication path between the CPU 112 and I/O processor 119 included in each of the channel control units CHN 110 .
  • the I/O processor 119 and CPU 112 are physically connected to each other via a communication memory 802 and a group of hardware registers 803 included in the own channel control unit CHN 110 .
  • the communication memory 802 and group of hardware registers 803 are accessible to either the CPU 112 or I/O processor 119 .
  • the group of hardware registers 803 is connected to a circuit that starts or discontinues power supply to the CPU 112 .
  • the I/O processor 119 accesses the group of hardware registers 803 , whereby the power supply of the CPU 112 can be controlled via the group of hardware registers 803 .
  • the group of hardware registers 803 produces, if necessary, an interrupt signal or the like to an entity that is an object of access so as to notify that the group of hardware registers has been accessed.
  • the group of hardware registers 803 has a plurality of capabilities including the capability to notify that the group of hardware registers has been accessed. The plurality of capabilities is assigned to respective registers constituting the group of hardware registers 803 on a hardware basis.
  • FIG. 12 and FIG. 13 show examples of a data structure stored in the communication memory 802 included in each of the channel control units CHN 110 .
  • FIG. 12 shows a data structure used to transfer information from the I/O processor 119 to the CPU 112 .
  • FIG. 13 shows a data structure used to transfer information from the CPU 112 to the I/O processor 119 .
  • Information to be transferred between the CPU 112 and I/O processor 119 is a group of information items to be transferred when the CPU 112 and I/O processor 119 are activated responsively to start of power supply or the like.
  • Information to be transferred from the I/O processor 119 to the CPU 112 includes a type of activated device, a diagnosis execution flag, a plurality of drive numbers, time instant information, the number of command retries, a command timeout value, and a plurality of temperature information items.
  • the type of activated device refers to the type of device that is activated in response to a command translated by the BIOS 801 when the CPU 112 is activated.
  • the type of activated device is, for example, “network” or “disk drive.”
  • the drive number is a number with which a disk drive in which an OS is loaded is selected when the type of activated device is “disk drive.” According to the present embodiment, the concept of a LU is introduced into the storage devices 300 .
  • the OS or the like is stored in an LU. Therefore, an LU number assigned to each LU is regarded as the drive number. Priorities are assigned to the drive numbers. Assuming that drive number 0 has priority over drive number 1 , the CPU 112 first attempts to activate the LU assigned drive number 0 . If the CPU 112 fails in the activation, the CPU 112 attempts to activate the LU assigned drive number 1 . When the CPU 112 is activated, the I/O processor 119 uses the diagnosis execution flag to direct the BIOS 801 to execute hardware diagnosis for the peripheries of the file server 800 . For example, when initialization of the file server 800 is completed, if the CPU 112 alone is reactivated, the BIOS 801 need not re-execute hardware diagnosis.
  • the I/O processor 119 when the I/O processor 119 appropriately sets the diagnosis execution flag, the CPU 112 is prevented from re-executing hardware diagnosis for the file server 800 .
  • the CPU 112 uses the time instant information when the BIOS 801 or OS is run in the CPU 112 .
  • the I/O processor 119 acquires the time instant information from the management terminal 160 , and hands it to the CPU 112 . Consequently, the management terminal 160 , I/O processor 119 , and CPU 112 can share the same time instant information.
  • the number of command retries and command timeout value are treated as conditions.
  • the number of command retries refers to the number of times by which the BIOS 801 or OS residing in the CPU 112 retries a command when the command issued from the CPU 112 to the I/O processor 119 fails.
  • the command timeout value refers to a timeout.
  • the temperature information is a value specified for the CPU 112 so that the CPU 112 can sense an abnormality in a temperature change thereof.
  • the I/O processor 119 can freely determine the type of activated device, drive numbers, time instant information, number of command retries, command timeout value, and plurality of temperature information items.
  • the present embodiment is not limited to this mode.
  • these values may be stored as initial values in the nonvolatile memory in which the BIOS is stored.
  • an operator may enter the values at the management terminal 160 or the values may be registered in the memory included in the management terminal 160 in advance so that the management terminal 160 can hand the values to the I/O processor 119 .
  • the diagnosis execution flag is set based on logical judgment made during activation of the I/O processor 119 or by the operator. When the diagnosis execution flag is set based on logical judgment made during activation of the I/O processor 119 , the actions of the CPU 112 or the run of the BIOS 801 loaded in the CPU 112 can be controlled by the I/O processor 119 .
  • FIG. 13 shows a data structure used to transfer information from the CPU 112 to the I/O processor 119 .
  • a BIOS version specifies the version of an object code produced by the BIOS 801 . The BIOS version is transferred from the CPU 112 to the I/O processor 119 , and from the I/O processor 119 to the management terminal 160 .
  • a MAC address specifies a MAC (which stands for media access control) address in the CPU 112 .
  • the MAC address is a unique identifier assigned to hardware, and needed to assign an IP address required by the IP protocol to a DHCP (which stands for dynamic host configuration protocol) server on a LAN. 0 padding information is needed to fill out a word and has nothing to do with information.
  • DHCP which stands for dynamic host configuration protocol
  • FIG. 14 shows the hardware configuration in which the CPU 112 and I/O processor 119 are connected to each other over the internal LAN 151 .
  • the CPU 112 and I/O processor 119 are also connected to each other over the internal LAN 151 , and can therefore communicate with the management terminal 160 over the internal LAN 151 . Consequently, for example, the CPU 112 runs the network boot loader stored in advance in the nonvolatile RAM 804 so as to download activation software from the management terminal 160 into the memory 113 and execute the activation software. Eventually, a network booting process is executed with the management terminal 160 used as a server and the CPU 112 used as a client.
  • Network booting is a method according to which: a network boot loader in a client and the management terminal 160 acting as a server activate and execute a boot residing in the management terminal 160 on a LAN for the purpose of loading an OS according to the combination of the IP protocol and the protocols of DHCP, TFTP (which stands for trivial file transfer protocol), and FTP (which stands for file transfer protocol) on the basis of, for example, the PXE standard or the like.
  • FIG. 15 is a block diagram showing the hardware configuration of each of the disk control units 140 .
  • the disk control units are connected to the storage devices 300 and also connected to the channel control units CHN 110 via the connection unit 150 .
  • the disk control units 140 read or write data from or in the storage devices 300 by themselves or under the control of the channel control units CHN 110 .
  • Each of the disk control units 140 comprises an interface block 141 , a memory 143 , a CPU 142 , a nonvolatile RAM 144 , and board coupling connectors 145 which are integrated into a unit.
  • the interface block 141 includes a communication interface via which the disk control unit communicates with the channel control units 110 via the connection unit 150 , a communication interface via which the disk control unit communicates with the storage devices 300 , and a communication interface via which the disk control unit communicates with the management terminal 160 over the internal LAN 151 .
  • the CPU 142 is responsible for control of the entire disk control unit 140 , and communicates with the channel control units 110 , storage devices 300 , and management terminal 160 .
  • Various programs stored in the memory 143 and nonvolatile RAM 144 are run, whereby the features of the disk control units 140 included in the present embodiment are implemented.
  • the features implemented in the disk control units 140 include control of the storage devices 300 , control of a RAID, management of a duplicate of data stored in the storage devices 300 , backup control, and control of remote control.
  • the nonvolatile RAM 144 is a nonvolatile memory in which a program according to which the CPU 142 extends control is stored. The contents of the program stored in the nonvolatile RAM 144 are written or rewritten in response to a directive given at the management terminal 160 or issued from the NAS manager 706 .
  • each of the disk control units 140 includes the board coupling connectors 145 .
  • each of the disk control units 140 is electrically connected to the storage device control system 100 .
  • FIG. 16 shows the software configuration of the storage device system 600 in accordance with the present embodiment.
  • the CPU 112 and I/O processor 119 are included in each of the channel control units CHN 110 .
  • the number of CPUs 112 and the number of I/O processors 119 may be one, or a plurality of CPUs 112 and a plurality of I/O processors 119 may be included.
  • An OS 701 and diverse applications including the NAS manager 706 are run in the CPU 112 , whereby the CPU 112 acts as an NAS server.
  • a microprogram implementing a controller is run in the I/O processor 119 .
  • a RAID controller 740 runs in the CPU 142 included in each of the disk control units 140 .
  • the CPU 161 included in the management terminal 160 acts as a network boot server 703 .
  • the network boot server 703 transfers a mini kernel 704 and an OS image 705 from the storage medium 167 or storage device 168 thereof to the CPUs 112 included in the channel control units CHN 110 over the internal LAN 151 .
  • the network boot server 703 includes, for example, DHCP (which stands for dynamic host configuration protocol) server.
  • the network boot server 703 assigns an IP address or a MAC address to each of the CPUs 112 and the I/O processors 11 included in the channel control units CHN 110 , and to the CPU 161 , and enables transfer between the management terminal 160 and the CPUs 112 or between the CPU 161 and the I/O processors 119 .
  • the CPUs 112 act as a client and issues a DHCP request or a file transfer request to the network boot server 703 . After the network booting is completed, the CPUs 112 each execute the mini kernel 704 . Finally, each of the CPUs 112 installs the OS image 705 in the storage devices 300 via the I/O processor 119 .
  • FIG. 16 also shows the software configuration of each of the information processing systems 200 .
  • Some of the information processing systems 200 adopt a network file system (NFS) 711
  • the other information processing systems 200 adopt a common Internet file system (CIFS) 713 .
  • the NFS 711 is a file sharing protocol adopted mainly by a UNIX® operating system 714
  • the CIFS 713 is a file sharing protocol adopted mainly by a Windows® operating system 715 .
  • the channel control units CHN 110 each act as a NAS server.
  • the power supply of the storage device system 600 is turned on.
  • the channel control units CHN 110 are inserted into the storage device system 600 whose power supply has already been turned on, whereby power is supplied from the storage device system 600 to the power supply circuits included in the channel control units CHN 110 .
  • power may be supplied to the channel control units CHN 110 .
  • the former procedure that after the channel control units CHN 110 are inserted into the storage device system 600 , the power supply of the storage device system 600 itself is turned on will be described below.
  • FIG. 17 describes a flow ranging from a step of turning on the power supply of the storage device system 600 , through a step of installing the OS image 705 from the management terminal 160 to the storage devices 300 , to a step of activating the OS installed in the storage devices 300 so that the storage device system 600 will act as an NAS system.
  • FIG. 17 lists the actions of the CPUs 112 , I/O processors 119 , management terminal 160 , and storage devices 300 while associating them with one another. Time passes from above to below in the drawing. In the drawing, arrows drawn with solid lines indicate transmission of control information, and arrows drawn with dot lines indicate flows of data.
  • the power supply of the storage device system 600 is turned on (step 1 for the CPUs 112 , step 1 for the I/O processors 119 , step 1 for the management terminal 160 , step 1 for the storage devices 300 ).
  • the CPUs 112 autonomously start activating the respective BIOSs (step 2 for the CPUs 112 ).
  • the I/O processors 119 initialize the hardware of the channel control units CHN 110 (step 2 for the I/O processors 119 ).
  • the management terminal 160 activates the OS and software installed thereon (step 2 for the management terminal 160 ).
  • the storage devices 300 activate the respective disk drives which spin the disks (step 2 for the storage devices 300 ).
  • the spinning is completed at the timing that the CPUs 112 perform activation for the second time (step 8 for the storage devices 300 ).
  • the present embodiment since the power supply of the entire storage device system 600 is turned on, power is simultaneously supplied to all of the CPUs 112 , I/O processors 119 , management terminal 160 , and storage devices 300 .
  • the present embodiment is not limited to this mode.
  • the power supply of the storage device system 600 has already been turned on, if a new channel control unit CHN 110 is added to the storage device system 600 , power is not supplied to the CPU 112 and I/O processor 119 included in the channel control unit CHN 110 until the power supply connector 750 of the channel control unit CHN 110 is coupled to the storage device system 600 .
  • the disk drives have already been activated and the disks have already been spun, extra control need not be extended.
  • the I/O processors 119 verify at step 12 that the disk drives have already spun the disks, and immediately pass control to the next step 13 . For example, when power supply to the management terminal 160 alone is discontinued because of maintenance or the like, even if a new channel control unit CHN 110 is added to the storage device system 600 , the I/O processors 119 cannot communicate with the management terminal 160 at step 10 .
  • the I/O processors 119 repeat step 10 regularly until the power supply of the management terminal 160 is turned on again. Otherwise, an emergency alarm LED included in the storage device system 600 or a communication line may be used to notify a maintenance engineer or the like of the fact that the power supply of the management terminal 160 should be turned on. Thus, the maintenance engineer or the like may be prompted to turn on the power supply of the management terminal 160 so that control can be passed to the next step.
  • the BIOS 801 waits for a directive issued from the I/O processor 119 (step 3 for the CPUs 112 ).
  • a diagnosis start request is issued to the CPU 112 in order to direct start of hardware diagnosis (step 4 for the I/O processors 119 ).
  • the diagnosis start request is transmitted using either the communication memory 802 or the group of hardware registers 803 or both of them.
  • the CPUs 112 When the CPUs 112 detect the diagnosis start request, the CPUs 112 start diagnosing hardware (step 4 for the CPUs 112 ). When hardware diagnosis is completed (step 5 for the CPUs 112 ), the CPUs 112 store respective MAC addresses, which is assigned to the internal LAN 151 ports thereof, in the respective communication memories 802 (step 6 for the CPUs 112 ). When the I/O processors 119 sense that the MAC addresses have been stored in the respective communication memories 802 (step 6 for the I/O processors 119 ), the I/O processors 119 access the respective groups of hardware registers 803 so as to issue a CPU reset directive. Consequently, the CPUs 112 are physically reset (step 7 for the I/O processors 119 ).
  • the power supply is restarted (step 7 for the CPUs 112 ).
  • the CPUs 112 reactivate the respective BIOSs (step 8 for the CPUs 112 ), and wait for a directive issued from the respective I/O processors 119 (step 9 for the CPUs 112 ).
  • the management terminal 160 When the management terminal 160 completes activation, it starts installation. An operator may perform the installation, or the installation may be executed under the control of the CPU 161 according to a predefined program. Hereinafter, an operator shall perform the installation, and the CPU 161 included in the management terminal 160 shall perform processing according to an entry the operator made at the input device 165 .
  • the management terminal 160 queries the I/O processors 119 about the MAC addresses, and receives the MAC addresses assigned to the CPUs 112 from the I/O processors 119 (step 10 for the management terminal 160 ). The operator enters and determines the number of command retries to be permitted after activation of the OS, a timeout value, and temperature information (step 11 for the management terminal 160 ).
  • These values entered by the operator are transmitted from the management terminal 160 to the I/O processors 119 included in the channel control units CHN 110 over the internal LAN 151 .
  • the operator directs the management terminal 160 to install a new OS.
  • the OS installation directive is transmitted from the management terminal 160 to the I/O processors 119 (step 11 for the management terminal 160 ).
  • the I/O processors 119 verify whether the disk drives in the storage devices 300 have spun the disks so as to judge whether the storage devices 300 are usable (step 12 for the I/O processors 119 ). Since the disk drives in the storage devices 300 have already spun the disks (step 8 for the storage devices 300 ), the I/O processors 119 detect whether the disk drives have completed spinning the disks (step 13 for the I/O processors 119 ). If it cannot be detected that the disk drives have completed spinning the disks, the I/O processors 119 return an error response to the management terminal 160 so as to notify that the disk drives have not spun the disks.
  • the I/O processors 119 If the I/O processors 119 detect that the disk drives have completed spinning the disks, the I/O processors 119 store, in addition to the temperature information, number of command retries, and retry timeout value received from the management terminal 160 , a diagnosis execution flag and a type of activated device in the respective communication memories 802 (step 14 for the I/O processors 119 . Since hardware diagnosis has already been completed (at step 4 and step 5 for the CPUs 112 ), it is-unnecessary to perform hardware diagnosis again. Consequently, the I/O processors 119 set the diagnosis execution flag to a value that directs skip of hardware diagnosis.
  • the CPUs 112 must install the OS image 705 existent in the management terminal 160 into the storage devices 300 during activation after the CPUs 112 wait for a directive sent from the respective I/O processors. Consequently, the I/O processors 119 specify a network boot disk as the type of activated device, and stores the type of activated device in the respective communication memories 802 (step 14 for the I/O processors 119 ).
  • the I/O processors 119 access the respective groups of hardware registers 803 and notify the respective CPUs 112 of the fact that the information items have been stored (step 15 for the I/O processors 119 ). The notification is intended to direct the CPUs 112 to execute processing.
  • the CPUs 112 sense whether the respective I/O processors 119 have issued a directive that processing should be continued (step 15 for the CPUs 112 ).
  • the CPUs 112 acquire the temperature information, number of command retries, retry timeout value, diagnosis execution flag, and type of activated device from the respective communication memories 802 (step 16 for the CPUs 112 ). Since a network boot disk is specified as the type of activated device, the CPUs 112 start network booting (step 17 for the CPUs 112 ). Network booting progresses along with data communication over the internal LAN 151 between the boot loader running in each of the CPUs 112 and the network boot server 703 implemented in the management terminal 160 .
  • the network boot server 703 uses the MAC address information of each of the CPUs 112 (acquired at step 10 for the management terminal 160 ) to communicate with the boot loader.
  • the CPUs 112 issue a network boot request to the network boot server 703 implemented in the management terminal 160 according to the PXE (which stands for preboot execution environment) standard (step 18 for the CPUs 112 ).
  • the management terminal 160 receives the network boot request over the internal LAN 151 (step 18 for the management terminal 160 ).
  • the CPUs 112 act as network boot clients (step 19 for the CPUs 112 ).
  • the management terminal 160 acts as the network boot server (step 19 for the management terminal 160 ).
  • the management terminal 160 allows the CPUs 112 to download the mini kernel 704 .
  • the mini kernel 704 downloaded into each of the CPUs 112 permits transfer of the OS image 705 , which resides in the management terminal 160 , to the storage devices 300 (step 20 for the CPUs 112 ).
  • the OS image 705 is installed in the storage devices by way of the I/O processors 119 , cache memory 130 , and disk control units 140 under the control of the CPUs 112 included in the channel control units CHN 110 .
  • the CPUs 112 issue an installation completion notification to the respective I/O processors 119 (step 21 for the CPUs 112 ).
  • the I/O processors 119 detect the installation completion notification (step 21 for the I/O processors 119 ), the I/O processors access the respective groups of hardware registers 803 so as to issue a CPU reset directive, and thus reset the respective CPUs 112 (step 22 for the I/O processors 119 ). Consequently, power is re-supplied to the CPUs 112 (step 22 for the CPUs 112 ).
  • the CPUs 112 reactivate the respective BIOSs 801 (step 23 for the CPUs 112 ), and wait for a directive sent from the I/O processors 119 (step 24 for the CPUs 112 ).
  • the I/O processors 119 store time instant information, a type of activated device, and activated drive number information in the respective communication memories 802 (step 25 for the I/O processors 119 ). In this case, the I/O processors 119 specify a disk drive as the type of activated device.
  • the I/O processors 119 access the respective groups of hardware registers 803 so as to issue a processing continuation directive to the respective CPUs 112 (step 26 for the I/O processors 119 ).
  • the CPUs 112 detect the CPU processing continuation directive (step 26 for the CPUs 112 ), the CPUs 112 acquire the time instant information from the respective communication memories 802 (step 27 for the CPUs 112 ), and issue a command to the respective I/O processors 119 .
  • the CPUs 112 thus allow the respective I/O processors 119 to start disk booting (step 28 for the CPUs 112 ).
  • the CPUs 112 allow the respective I/O processors 119 to load the OS image 705 stored in the storage devices 300 (step 29 for the CPUs 112 ). In this case, the OS image 705 is loaded from the storage devices 300 to the CPUs 112 by way of the disk control units 140 , cache memory 130 , and I/O processors 119 .
  • the OS image 705 is loaded into the CPUs 112 , the CPUs 112 pass control from the respective BIOSs 801 to the OS image 705 . Consequently, the OS is activated (step 30 for the CPUs 112 ). This permits the channel control units CHN 110 to act as NAS devices and permits the storage device system 600 to act as an NAS system (step 31 for the CPUs 112 ).
  • the I/O processors 119 control the respective CPUs 112 .
  • This enables installation of a new OS over a network or enables booting for installing the OS.
  • the CPUs 112 and I/O processors 119 included in the respective channel control units 110 , the CPU 161 included in the management terminal 160 , the CPUs 142 included in the respective disk control units 140 , and the storage devices 300 cooperate with one another. Consequently, the storage device system 600 can be activated efficiently for a limited period of time. Moreover, software can be installed efficiently.
  • the CPUs 112 used as file servers must often be controlled on a hardware basis. Specifically, when the CPUs 112 are activated or an OS is installed in the CPUs 112 , the CPUs 112 must be re-booted, and power supply to the CPUs 112 must be started, discontinued, or restarted. This work is daily performed on a normal server computer. A maintenance engineer or a user manually performs the work at any time while looking at a screen image displayed on the operator console. In the storage device system 600 in which the file servers are incorporated in the form of hardware, the servers themselves need not support a special screen image or a user interface to be displayed on the console.
  • the above hardware operations are automatically performed according to a program installed in the I/O processors 119 through communications with the I/O processors 119 . Consequently, activation of the servers and installation of an OS can be automated.
  • a UNIX or any other general-purpose OS can be adapted to the OS to be installed in the file servers with minimal modification. Since the UNIX or any other general-purpose OS is widely adopted as an OS to be installed in file servers, it is advantageous that the UNIX or any other general-purpose OS can be installed with a little modification. Moreover, this leads to a reduction in the period required for development.
  • the storage device controller section that has a close relationship with the disk drives can control booting, OS installation, and other work to be performed by the file server section during a period of time during which the disk drives spin the disks or any other physical movements are made.
  • a section of a storage device system whose hardware is restricted that is, in which the period of time during which disk drives spin disks is restricted can actively control booting of the entire system or installation as soon as the hardware-related restriction is lifted. From this viewpoint, the storage device system in accordance with the present invention is an efficient and reasonable system.
  • the present embodiment has been described by taking for instance a method of turning on the power supply of the storage device system 600 itself after the channel control units CHN 110 are inserted into the storage device system 600 .
  • the present embodiment is not limited to this mode.
  • the channel control units CHN 110 may be inserted into the storage device system 600 whose power supply has already been turned on in order to supply power to the channel control units CHN 110 .
  • a novel storage device system capable of being connected on a plurality of different types of networks. Furthermore, there are provided a storage device control system and a method of controlling activation of the storage device system which are needed to invent the storage device system.

Abstract

Provided is a storage device system capable of being connected on a plurality of different types of networks. Also provided are a storage device control system and a method of controlling activation of the storage device system which are needed to invent the storage device system. A storage device system in accordance with the present invention comprises: a plurality of storage devices in which information is stored; a storage device control section that controls storage of information in the plurality of storage devices; and a connection unit connected to the storage device control section. Furthermore, the storage device system comprises a first communication control section that includes: a first processor which is connected to the storage device control section via the connection unit and also connected on a first network external to the storage device system, which converts information of a first form received over the first external network into information of a second form, and which issues a request for access to the plurality of storage devices; and a second processor which accesses the plurality of storage devices via the connection unit and the storage device control section in response to the access request issued from the first processor, and which controls activation of the first processor.

Description

  • The basic foreign application filed on Jan. 24, 2003, No. 2003-015525 in Japan is hereby incorporated by reference. [0001]
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention [0002]
  • The present invention relates to a novel storage device system capable of being connected on a plurality of different types of networks, or more particularly, to a method of controlling activation of the storage device system. [0003]
  • 2. Description of the Related Art [0004]
  • In recent years, an amount of data being treated by a computer system has rapidly increased. In order to efficiently utilize and manage such abundant data, a technology has been developed for connecting a system including a disk array composed of a plurality of disk drives (hereinafter, a storage device system) to an information processing system over a leased line network (or a storage area network (SAN)) so as to realize fast access to a large amount of information stored in the storage device system. In order to realize fast data transfer by connecting the storage device system to the information processing system over the SAN, communications equipment conformable to a fibre channel protocol is generally used to construct a network. [0005]
  • On the other hand, a network system referred to as a network attached storage (NAS) has been developed for realizing access at a file level to a storage device system by interconnecting the storage device system that includes a plurality of storage devices and an information processing system over a network that adopts a TCP/IP (which stands for transmission control protocol/Internet protocol) protocol. Within the NAS, since a system having the capability of a file system is connected to the storage device system, the information processing system can gain a file-level access to the storage device system. Recently, a large-scale NAS accommodating a storage device system which is managed based on a RAID (redundant arrays of inexpensive disks) technology and includes a file system is attracting attention because it provides an enormous storage resource called a midrange-class or enterprise-class resource. [0006]
  • Patent Document 1: Japanese Unexamined Patent Application Publication No. 2002-351703 [0007]
  • However, the conventional NAS is realized by connecting an information processing system, which has a TCP/IP communication feature and the capability of a file system, to a storage device system that has neither the TCP/IP communication feature nor the capability of a file system. An installation space for the connected information processing system is therefore needed. Moreover, the information processing system and storage device system are often interconnected over a SAN because of the necessity of fast communication. Communication control equipment and a communication control feature must therefore be included. [0008]
  • SUMMARY OF THE INVENTION
  • Accordingly, a main object of the present invention is to provide a novel storage device system capable of being connected to a plurality of different types of networks, and to provide a storage device control system and a method of controlling activation of the storage device system which are needed to invent the storage device system. [0009]
  • A storage device system in accordance with the present invention comprises: a plurality of storage devices in which information is stored; a storage device control section that controls storage of information in the plurality of storage devices; and a connection unit connected to the storage device control section. The storage device system further comprises a first communication control section including: a first processor that is connected on a first network external to the storage device system, that converts information of a first form, which is received over the first external network, into information of a second form, and that issues a request for access to the plurality of storage devices; and a second processor that accesses the plurality of storage devices via the connection unit and storage device control section in response to the access request issued from the first processor, and that controls activation of the first processor.[0010]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram showing the overall configuration of a storage device system in accordance with an embodiment of the present invention; [0011]
  • FIG. 2 is a block diagram showing the configuration of a management terminal included in the embodiment; [0012]
  • FIG. 3 shows a physical disk management table employed in the embodiment; [0013]
  • FIG. 4 shows an LU management table employed in the embodiment; [0014]
  • FIG. 5 shows the appearance of the storage device system in accordance with the embodiment; [0015]
  • FIG. 6 shows the appearance of a storage device control system included in the embodiment; [0016]
  • FIG. 7 shows the hardware configuration of a channel control unit CHN included in the embodiment; [0017]
  • FIG. 8 is an explanatory diagram concerning the contents of data stored in a memory included in the embodiment; [0018]
  • FIG. 9 shows metadata employed in the embodiment; [0019]
  • FIG. 10 shows lock data employed in the embodiment; [0020]
  • FIG. 11 shows a communication path linking a CPU and an I/O processor which are included in the channel control unit CHN included in the embodiment; [0021]
  • FIG. 12 shows data to be transferred from the I/O processor to the CPU according to the embodiment; [0022]
  • FIG. 13 shows data to be transferred from the CPU to the I/O processor according to the embodiment: [0023]
  • FIG. 14 shows the hardware configuration of the channel control unit CHN which is included in the embodiment and which has an internal LAN; [0024]
  • FIG. 15 shows a disk control unit included in the embodiment; [0025]
  • FIG. 16 shows the software configuration of the storage device system in accordance with the embodiment; and [0026]
  • FIG. 17 is a flowchart describing activation and installation performed in the storage device system in accordance with the embodiment.[0027]
  • DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • Referring to the drawings, an embodiment of the present invention will be described below. [0028]
  • FIG. 1 is a block diagram showing the overall configuration of a storage device system in accordance with the embodiment. [0029]
  • (Example of Overall Configuration) [0030]
  • A [0031] storage device system 600 has a storage device control system 100 and storage devices 300. The storage device control system 100 controls the storage devices 300 according to a command received from any of information processing systems 200. For example, the storage device system 100 receives an input/output request for data from any of the information processing systems 200, and performs processing for the purpose of receiving or transmitting data stored in the storage devices 300. Data is stored in a logical volume or logical unit (LU) that is a storage area logically defined in a physical storage area provided by a disk drive included in each of the storage devices 300.
  • Moreover, the storage [0032] device control system 100 transfers various commands, which are used to manage the storage device system 600, to or from the information processing systems 200.
  • [0033] Power supplies 111 supply power to the storage device system 600, and are realized with batteries connected to an external power supply. A plurality of power supplies is mounted in the storage device system for the purpose of redundancy. Specifically, the storage device system 600 is physically divided into two or more power supply groups in terms of power supply. When the storage device system 600 is divided into, for example, two power supply groups, first to fourth channel control units 110 belong to a first power supply group, and fifth to eighth channel control units 110 belong to a second power supply group. All redundant components of the storage device system 600 are classified into two or more power supply groups. Moreover, components belonging to a group of redundant components are designed not to belong to the same power supply group. Moreover, the power supplies 111 are divided into two or more groups. Power is supplied from an external power supply to the two or more groups of power supplies 111 over independent cables. The two or more groups of power supplies 111 supply power to the assigned groups of power supplies. Moreover, the two or more groups of power supplies 111 each include a plurality of power supplies. Since the storage device system 600 has redundancy, if a certain power supply breaks down, the storage device-system 600 can keep operating. Furthermore, even if external power supply to the two or more groups of power supplies 111 is discontinued, the storage device system 600 can keep operating.
  • The [0034] information processing systems 200 are computers each having a central processing unit (CPU) and a memory. The CPU included in each of the information processing systems 200 runs various programs, whereby various features are implemented. The information processing systems 200 may be, for example, personal computers, workstations, or main frame computers.
  • Referring to FIG. 1, the first to third [0035] information processing systems 200 are connected to the storage device control system 100 over a local area network (LAN) 400. The LAN 400 may be the Internet or a leased line network. Communications over the LAN 400 between the first to third information processing systems 200 and the storage device control system 100 are carried out based on, for example, a TCP/IP protocol. The first to third information processing systems 200 transmit a data access request (data input/output request for requesting data in units of a file) (hereinafter, a file access request) to the storage device system 600 while designating a filename.
  • A [0036] backup device 910 is connected on the LAN 400. The backup device 910 is a disk device such as a magneto-optical disk (MO), CD-rewritable (CD-R) disk, or DVD-RAM, or a tape device such as a digital audio tape (DAT) cartridge, cassette tape, open tape, or cartridge tape. When the information processing system communicates with the storage device control system 100 over the LAN 400, backup data of data stored in the storage devices 300 is stored in the backup device 910. The backup device 910 may be connected to the first information processing system 200. In this case, backup data of data stored in the storage devices 300 can be acquired via the first information processing system 200.
  • The storage [0037] device control system 100 includes first to fourth channel control units 110. The storage device control system 100 uses the first to fourth channel control units 110 to receive file access requests issued from the first to third information processing systems 200 respectively over the LAN 400. Specifically, a network address (for example, IP address) on the LAN 400 is assigned to each of the first to fourth channel control units 110. The first to fourth channel control units behave as if to be independent network attached storage (NAS) devices, and can independently provide the first to third information processing systems 200 with NAS service. Hereinafter, the first to fourth channel control units 110 will be called the channel control units CHN110. Thus, the storage device system 600 includes the first to fourth channel control units 110 that independently provide NAS service, NAS servers that are conventionally realized with independent computers are integrated into the one storage device system 600. Consequently, the storage device system 600 can be managed as a whole. Maintenance work including determination or control of various settings, life management, and version management can be efficiently carried out.
  • Power is supplied from the [0038] power supplies 111 to the channel control units 110 via the storage device control system 100. Since the channel control units 110 can be dismounted from the storage device control system 100, power supply to the channel control units 110 is discontinued by physically removing the channel control units 110 from the storage device control system 100. Moreover, when the channel control units 110 are mounted in the storage device control system 100, power supply to the channel control units 110 is enabled. The channel control units 110 have a power supply circuit. When the power supply circuit is controlled by running a program implemented by a plurality of LSIs mounted on each of the channel control units 110, power supply to the circuit elements incorporated in the channel control unit can be started or discontinued.
  • Each of the first to fourth [0039] channel control units 110 included in the storage device control system 100 included in the present embodiment is realized with: hardware formed on circuit boards that are integrated into a unit; and software including an operating system (OS) to be run by the hardware, and an application program to be run on the OS or an executable object code to be executed by the hardware. In the storage device system 600 of the present embodiment, the features that are conventionally implemented by part of hardware are realized by software. The storage device system 600 of the present embodiment can therefore be operated flexibly, and meet diverse and varied users' needs so as to provide delicate service.
  • The third and fourth [0040] information processing systems 200 are connected to the storage device control system 100 via a storage area network (SAN) 500. The SAN 500 is a network over which data is transferred in units of a block, which is a management unit of data stored in the storage areas offered by each storage devices 300, between the storage devices 300 and the third and fourth information processing systems 200. Communications over the SAN 500 between the third and fourth information processing systems 200 and the storage device control system 100 are performed based generally on a fibre channel protocol. The third and fourth information processing systems transmit a data access request (hereinafter, block access request), which requests access to data in units of a block, to the storage device system 600 according to the fibre channel protocol.
  • A [0041] backup device 900 supporting the SAN is connected to the SAN 500. When the information processing system communicates with the storage device control system 100 over the SAN 500, backup data of data stored in the storage devices 300 is stored in the backup device 900 supporting the SAN.
  • The fifth [0042] information processing system 200 is connected to the storage device control system 100 without the intervention of a network such as the LAN 400 or SAN 500. The fifth information processing system 200 may be formed with, for example, a main frame computer. Communications between the fifth information processing system 200 and storage device control system 100 are achieved based on a communications protocol, for example, the FICON (which stands for fibre connection)®, ESCON (which stands for enterprise system connection)®, ACONARC (which stands for advanced connection architecture)®, or FIBARC (which stands for fibre connection architecture)®. The fifth information processing system 200 transmits a block access request to the storage device system 600 according to the communications protocol.
  • The storage [0043] device control system 100 communicates with the fifth information processing system 200 using the seventh and eighth channel control units 110. Hereinafter, the seventh and eighth channel control units 110 will be called the channel control units CHA110.
  • A [0044] storage device system 610 located at a remote place (secondary site) away from the installation site (primary site) of the storage device system 600 is connected on the SAN 500. The storage device system 610 is utilized as a system into which data is copied by a replication or remote copy feature that will be described later. The storage device system 610 may be connected to the storage device system 600 over a communication network such as the SAN 500 or an ATM (which stands for asynchronous transfer mode) network. In this case, for example, channel control units 110 having an interface (channel extender) that permits use of the communication network are adopted as the channel control units 110.
  • (Storage Device) [0045]
  • The [0046] storage devices 300 include numerous disk drives (physical disks), and provide the information processing systems 200 with a storage area. Data is stored in a logical unit (LU) that is a storage area logically defined on a physical storage area provided by the disk drives. As the disk drives, any of various disk drives including, for example, a hard disk drive, a flexible disk dive, and a semiconductor storage device can be adopted. The storage devices 300 may be formed with a disk array composed of a plurality of disk drives. In this case, the storage area provided for the information processing systems 200 is formed with a plurality of disk drives managed as a redundant array of inexpensive disks (RAID).
  • The storage [0047] device control system 100 and the storage devices 300 may be, as shown in FIG. 1, directly connected to each other or may be connected to each other over a network. Furthermore, the storage devices 300 may be designed as an integral part of the storage device control system 100.
  • The LUs offered by the [0048] storage devices 300 includes a user LU accessible to the information processing systems 200 and a system LU for use in controlling the channel control units 110. An OS to be run in the channel control units CHN110 is also stored in the system LU. Moreover, the channel control units 110 are associated with the LUs. In other words, accessible LUs are determined for the respective channel control units 110. Otherwise, the plurality of channel control units 110 may share the same LU. Hereinafter, the user LU and system LU may be called a user disk and a system disk respectively.
  • (Storage Device Control System) [0049]
  • The storage [0050] device control system 100 comprises the channel control units 110, a common memory 120, a cache memory 130, disk control units 140, a management terminal 160, and a connection unit 150.
  • The [0051] channel control units 110 include a communication interface via which the channel control units communicate with the information processing systems 200, and have the capability to transfer a data input/output command to or from the information processing systems 200. For example, the channel control units CHN110 receive a file access request from the first to third information processing systems 200. Consequently, the storage device system 600 provides the first to third information processing systems 200 with NAS service. The channel control units CHF110 that refer to the fifth and sixth channel control units receive a block access request conformable to the fibre channel protocol from the third and fourth information processing systems 200. Consequently, the storage device system 600 provides the third and fourth information processing systems 200 with data storage service permitting fast access. Moreover, the channel control units CHA110 receive a block access request, which conforms to the FICON, ESCON, ACONARC, or FIBARC protocol, from the fifth information processing system 200. Consequently, the storage device system 600 provides a mainframe computer such as the fifth information processing system 200 with data storage service.
  • The [0052] channel control units 110 are interconnected together with the management terminal 160 over the internal LAN 151. Consequently, a microprogram or the like to be run by the channel control units 110 can be transmitted from the management terminal 160 and installed in the channel control units. The configuration of the channel control units 110 will be detailed later.
  • The [0053] connection unit 150 is connected to the channel control units 110, common memory 120, cache memory 130, and disk control units 140. Transfer of data or a command among the channel control units 110, common memory 120, cache memory 130, and disk control units 140 is achieved via the connection unit 150. The connection unit 150 is formed with, for example, a switch such as a super-fast crossbar switch that suits data transmission because of its fast switching, or a bus. Since the channel control units 110 are interconnected via the switch, compared with the conventional configuration that NAS servers realized with respective computers are interconnected over a LAN, the efficiency in communications among the channel control units 110 has greatly improved. Moreover, fast file sharing and fast failover can be achieved.
  • The [0054] common memory 120 and cache memory 130 are storage memories shared by the channel control units 110 and disk control units 140. The common memory 120 is used mainly to store control information and commands, while the cache memory 130 is used mainly to store data.
  • For example, assume that a data input/output command a certain [0055] channel control unit 110 has received from a certain information processing system 200 is a Write command. In this case, the channel control unit 110 writes the Write command in the common memory 120, and writes written data, which has been received from the information processing system 200, in the cache memory 130. On the other hand, the disk control units 140 monitor the common memory 120. When the disk control units 140 detects that the Write command has been written in the common memory 120, the disk control units 140 read the written data from the cache memory 130 in response to the command, and write the data in the storage devices 300. Moreover, for example, assume that a data input/output command a certain channel control unit 11 has received from a certain information processing system 200 is a Read command. In this case, the channel control unit 110 writes the Read command in the common memory 120, and reads data, which is requested with the Read command sent from the information processing system 200, from the cache memory 130. If data requested with the Read command is not written in the cache memory 130, the channel control unit 110 or disk control units 140 read the data, which is requested with the Read command, from the storage devices 300, and writes the data in the cache memory 130.
  • In the foregoing present embodiment, the [0056] common memory 120 and cache memory 130 are included independently of the channel control units 110 and disk control units 146. The present embodiment is not limited to this mode. Alternatively, the common memory 120 and cache memory 130 may be broken up and distributed into the channel control units 110 and disk control units 140. In this case, the connection unit 150 connects the channel control units 110 and disk control units 140 which include the distributed portions of the broken up common memory and cache memory.
  • The [0057] disk control units 140 control the storage devices 300. For example, as mentioned above, the disk control units 140 write data in the storage devices 300 in response to a data Write command any of the channel control units 110 has received from any of the information processing systems 200. Moreover, the disk control units 140 convert a data access request, which is transmitted from any of the channel control units 110 and requests access to an LU by designating the logical address of the LU, into a data access request that requests access to a physical disk by designating the physical address of the physical disk. If the physical disks included in the storage devices 300 are managed as a RAID, data is accessed according to the principle of the RAID. Moreover, the disk control units 140 extend control to manage a duplicate of data stored in the storage devices 300 or create a backup thereof. The disk control units 140 extend control so as to store a duplicate of data stored in the storage device system 600 located at the primary site into the other storage device system 610 located at the secondary site (replication or remote copy) for the purpose of preventing loss of data in case of a disaster.
  • The [0058] disk control units 140 are interconnected together with the management terminal 160 over a communication network such as the internal LAN 151, and can therefore communicate with one another. Consequently, a microprogram or the like to be run by the disk control units 140 can be transmitted from the management terminal 160 and installed in the disk control units 140. The configuration of the disk control units 140 will be described later.
  • (Management Terminal) [0059]
  • The [0060] management terminal 160 is a computer that maintains or manages the storage device system 600. By handling the management terminal 160, the arrangement of physical disks can be determined, an LU to be employed can be designated, and a microprogram to be run in the channel control units 110 can be installed. Herein, when it says that the arrangement of physical disks included in the storage devices 300 can be determined, it means that, for example, the number of physical disks can be increased or decreased, or the RAID levels can be changed (from RAID level 1 to RAID level 5).
  • Furthermore, the [0061] management terminal 160 can be used to check the operating state of the storage device system 600, to locate a broken region, to install an OS to be run by the channel control units 110, or to perform any other work. Moreover, the management terminal 160 is connected to an external maintenance center over a LAN or a telephone line. The management terminal 160 can therefore be used to monitor if a failure occurs in the storage device system 600 or to immediately cope with a failure. Occurrence of a failure is notified by, for example, an OS, an application program, or driver software. The notification is performed based on the HTTP protocol or simple network management protocol (SNMP), or by electronic mail. The above determination or extension of control is directed by an operator using as a user interface a Web page provided by a Web server realized with the management terminal 160. The operator or the like handles the management terminal 160 so as to determine an object of failure monitoring or the contents thereof or determine a failure notification destination.
  • The [0062] management terminal 160 may be incorporated in the storage device control system 100 or may be disposed externally. Moreover, the management terminal 160 may be formed with a computer dedicated to maintenance or management of the storage device control system 100 and storage devices 300, or may be formed with a general-purpose computer provided with a maintenance/management feature.
  • FIG. 2 is a block diagram showing the configuration of the [0063] management terminal 160.
  • The [0064] management terminal 160 comprises a CPU 161, a memory 162, a port 163, a recording medium reader 164, an input device 165, an output device 166, and a storage device 168.
  • The [0065] CPU 161 is responsible for control of the entire management terminal 160. When a program 162 c stored in the memory 162 is run, the CPU 161 implements the capability of a Web server. A physical disk management table 162 a, an LU management table 162 b, and the program 162 c are stored in the memory 162.
  • The physical disk management table [0066] 162 a is a table used to manage physical disks (or disk drives) included in the storage devices 300. FIG. 3 shows the physical disk management table 162 a. FIG. 3 lists physical disks bearing disk numbers 001 to 006 among numerous physical disks included in the storage devices 300. A storage capacity, a RAID level, and a use situation are specified relative to each physical disk.
  • The LU management table [0067] 162 b is a table used to manage LUs logically defined on the physical disks. FIG. 4 shows the LU management table 162 b. FIG. 4 lists LUs bearing LU numbers 1 to 3 among numerous LUs defined on the storage devices 300. A physical disk number, a storage capacity, and a RAID level are specified relative to each LU.
  • The [0068] recording medium reader 164 is a device for reading a program or data from a recording medium 167. The read program or data is stored in the memory 162 or storage device 168. Consequently, the program 162c recorded in the recording medium 167 can be read from the recording medium 167 using the recording medium reader 164, and stored in the memory 162 or storage device 168. A flexible disk, a CD-ROM, or a semiconductor memory can be adopted as the recording medium 167. The recording medium reader 162 may be incorporated in the management terminal 160. The storage device 168 is, for example, a hard disk drive, a flexible disk drive, or a semiconductor storage device. An operator or the like uses the input device 165 to enter data that is transferred to the management terminal 160. For example, a keyboard or a mouse is adopted as the input device 165. The output device 166 is a device for transmitting information to outside. For example, a display or printer is adopted as the output device 166. The port 163 is connected on the internal LAN 151, whereby the management terminal 160 can communicate with the channel control units 110 or disk control units 140. Moreover, the port 163 may be connected on the LAN 400 or connected on a telephone line.
  • As described in conjunction with FIG. 1, the [0069] management terminal 160 is connected to the power supplies 111. Power is supplied from the power supplies 111 to the management terminal 160.
  • (Appearance) [0070]
  • FIG. 5 shows the appearance of the [0071] storage device system 600 in accordance with the present embodiment. FIG. 6 shows the appearance of the storage device control system 100.
  • As shown in FIG. 5, the [0072] storage device system 600 in accordance with the present invention has the storage device control system 100 and storage devices 300 put in respective housings. The housings accommodating the storage devices 300 are located by the both sides of the housing accommodating the storage device control system 100.
  • The storage [0073] device control system 100 has the management terminal 160 located in the center of the face thereof. The management terminal 160 is shielded with a cover. As shown in FIG. 6, when the cover is opened, the management terminal 160 becomes usable. The management terminal 160 shown in FIG. 6 is formed as a so-called notebook personal computer. Alternatively, the management terminal 160 may have any other form.
  • Slots in which the [0074] channel control units 110 are inserted are formed below the management terminal 160. Circuit boards in which the channel control units 110 are implemented are inserted in the slots. The storage device system 600 in accordance with the present embodiment has, for example, eight slots. Referring to FIG. 5 and FIG. 6, guide rails are formed so that the channel control units 110 can be smoothly inserted in the eight slots. When the channel control units 110 are inserted in the slots along the guide rails, the channel control units 110 are mounted in the storage device control system 100. Moreover, the channel control units 110 inserted in the slots can be pulled forwards along the guide rails and thus removed. Moreover, connectors through which the channel control units 110 are electrically connected to the storage device control system 100 are located at the front ends in the depth directions of the slots. The channel control units 110 include the channel control units CHN110, CHF110, and CHA110. The channel control units 110 are interchangeable in terms of a size, the locations of the connectors, and the pin configurations of the connectors. Any of the channel control units 110 can be mounted in the eight slots. Consequently, for example, the channel control units CHN110 may be mounted in all the eight slots. Otherwise, for example, as shown in FIG. 1, four channel control units CHN110, two channel control units CHF110, and two channel control units CHA110 may be mounted in the eight slots. Moreover, a slot in which no channel control unit 110 is mounted may be included.
  • As mentioned above, the [0075] channel control units 110 are provided as circuit boards that can be mounted in the slots, that is, identical units. Each of the identical units may be composed of a plurality of circuit boards. Namely, even if a unit is composed of a plurality of circuit boards, as long as the circuit boards are interconnected and integrated into a unit, and can be mounted all together in a slot formed in the storage device control system 100, the unit is encompassed in the concept of one of identical circuit board.
  • The other components of the storage [0076] device control system 100 including the disk control units 140 and common memory 120 are mounted on the back of the storage device control system 100, though they are not shown in FIG. 5 and FIG. 6.
  • Moreover, the storage [0077] device control system 100 includes fans 170 used to release heat dissipated from the channel control units 110. The fans 170 are located on the top of the storage device control system 100, and also disposed above the slots of the channel control units 110.
  • By the way, a system and a device having conventional configurations and being sold as, for example, SAN products can be utilized as the storage [0078] device control system 100 and storage devices 300 respectively which are put in the housings. In particular, when the connectors of the channel control units CHN110 are shaped so that the channel control units can be mounted in the slots formed in a conventional housing as they are, the existing system can be utilized readily. Namely, the storage device system 600 of the present embodiment can be constructed readily by utilizing existing products.
  • According to the present embodiment, the channel control units CHN[0079] 110, CHF110, and CHA110 coexist in the storage device system 600. Consequently, a storage device system capable of being connected on different types of networks can be constructed. Specifically, the storage device system 600 is connected on the LAN 400 using the channel control units CHN110, and connected on the SAN 500 using the channel control units CHF110, and can therefore be called an SAN/NAS-integrated storage device system.
  • (Channel Control Unit) [0080]
  • The [0081] storage device system 600 in accordance with the present embodiment uses, as mentioned above, the channel control units CHN110 to receive a file access request from the first to third information processing systems 200, and provides the first to third information processing systems 200 with NAS service.
  • FIG. 7 shows the hardware configuration of the channel control units CHN[0082] 110. As illustrated, the hardware of each channel control unit CHN110 is one unit that will be called an NAS board. The NAS board includes one circuit board or a plurality of circuit boards. More particularly, the NAS board accommodates a network interface 111, an input/output controller 114, board coupling connectors 116, communication connectors 117, and a file server 800. These circuit elements are integrated into one unit. Furthermore, the input/output controller 114 includes a nonvolatile RAM (NVRAM) 115 and an input/output (I/O) processor 119.
  • Power is supplied from the power supplies [0083] 111 included in the storage device system 600 to each of the channel control units CHN110 via a power supply connector 750. Each of the channel control units CHN110 includes a power supply control circuit 751 and a hardware register 752 that controls the power supply control circuit 751. When values are specified in the hardware register as if to be programmed, start or disconnection of power supply to the input/output controller 114 and file server 800 can be controlled. Aside from the control of power supply or the start or discontinuation of power supply, hardware-like actions including rebooting of the input/output controller 114 or file server 800 or shift to a diagnosis mode can be controlled by modifying the values specified in the hardware register 752. Consequently, the I/O processor 119 in the input/output controller can control like hardware the start or disconnection of power supply to the CPU 112 included in the file server 800, the rebooting, or the shift to the diagnosis mode. Alternatively, the CPU 112 in the file server 800 may control the start or disconnection of power supply to the I/O processor 119 in the input/output controller, the rebooting, and the shift to the diagnosis mode.
  • The [0084] network interface 111 includes a communication interface via which the channel control unit communicates with the information processing systems 200. Each of the channel control units CHN110 receives a file access request sent from any of the information processing systems 200 according to, for example, a TCP/IP protocol. Communication connectors 117 are connectors via which the channel control unit communicates with the information processing systems 200. The communication connectors 117 included in each of the channel control units CHN110 are connectors via which the channel control units CHN110 can be connected on the LAN 400, and which are conformable to the Ethernet®.
  • The [0085] file server 800 includes a CPU 112, a memory 113, a basic input/output system (BIOS) 801, and a nonvolatile RAM 804. The CPU 112 is responsible for control to be extended in order to allow the own channel control unit CHN110 to act as a NAS board. The CPU 112 controls a file sharing protocol such as the NFS (which stands for network file system) or CIFS (which stands for common Internet file system) and a TCP/IP protocol. The CPU 112 analyzes a file access request that designates a file, converts data, which is treated in units of a file into control information stored in the memory 113 using a conversion table (not shown) that lists the data in relation to the LUs defined in the storage devices 300. Moreover, the CPU 112 produces a data writing or reading request that requests writing or reading of data in or from an LU defined in the storage devices 300, or transmits the data writing or reading request to the I/O processor 119. The BIOS 801 is software that when the power supply of the own channel control unit CHN110 is turned on, is loaded in the memory 113 and executed first in the course of activating the CPU 112. The BIOS 801 is stored in a nonvolatile medium, for example, a flash memory and included in the own channel control unit CHN110. The CPU 112 executes software translated by the BIOS 801 and stored in the memory 113 so as to initialize or diagnose relevant components. Furthermore, the CPU 112 issues a directive such as a command to the I/O processor 119 via the BIOS 801 so as to store a predetermined program, for example, a boot for loading an OS in the memory 113. The boot for loading an OS places a major portion of the OS stored in the storage devices 300 in the memory 113, whereby the OS is activated in the CPU 112. Consequently, the CPU 112 can perform processing to allow the own channel control unit CHN110 to act as a file server. Moreover, the file server 800 has the nonvolatile RAM 804 in which a network boot loader conformable to the PXE (which stands form preboot execution environment) standard or the like is stored, and can perform network booting that will be described later.
  • Various programs and data items are stored in the [0086] memory 113. Various programs, for example, metadata 730 and a lock table 720 shown in FIG. 8, and an NAS manager 706 shown in FIG. 16 are stored in the memory 113. The metadata 730 is information produced in association with a file managed by a file system. The metadata 730 contains, for example, an address in a LU in which the data in a file is stored, the data size, and other information specifying the storage place of the file. The metadata 730 may contain information of a file size, an owner, and a time instant of update. Moreover, the metadata 730 may be produced in association not only with a file but also with a directory. FIG. 9 shows an example of the metadata 730. The metadata 730 is stored in the LUs defined in the storage devices 300.
  • The lock table [0087] 720 is a table used to exclusively control access to a file gained by the first to third information processing systems 200. The exclusive control enables the first to third information processing systems 200 to share the same file. FIG. 10 shows the lock table 720. As shown in FIG. 10, the lock table 720 includes a file lock table 721 and an LU lock table 722. The file lock table 721 is a table indicating whether a file is locked. If a certain file is opened by any of the information processing systems 200, the file is locked. The other information processing systems 200 are inhibited from accessing the locked file. The LU lock table 722 is a table indicating whether each LU is locked. If any of the information processing systems 200 accesses a certain LU, the LU is locked. The other information processing systems 200 are inhibited from accessing the locked LU.
  • The input/[0088] output controller 114 transfers data or a command to or from the disk control units 140, the cache memory 130, the common memory 120, and the management terminal 160. The input/output controller 114 includes the I/O processor 119 and nonvolatile RAM 115. The I/O processor 119 is formed with, for example, a microcomputer implemented in one chip. The I/O processor 119 controls transfer of a data writing or reading request, which is issued to an LU defined in the storage devices 300, and data, and relays communication between the CPU 112 and disk control units 140. The nonvolatile RAM 115 is a nonvolatile memory in which a program based on which the I/O processor 119 extends control are stored. The contents of the program stored in the nonvolatile RAM 115 are written or rewritten in response to a directive issued from the management terminal 160 or the NAS manager 706 that will be described later.
  • FIG. 11 shows a concrete example of a communication path between the [0089] CPU 112 and I/O processor 119 included in each of the channel control units CHN110. The I/O processor 119 and CPU 112 are physically connected to each other via a communication memory 802 and a group of hardware registers 803 included in the own channel control unit CHN110. The communication memory 802 and group of hardware registers 803 are accessible to either the CPU 112 or I/O processor 119. The group of hardware registers 803 is connected to a circuit that starts or discontinues power supply to the CPU 112. Consequently, the I/O processor 119 accesses the group of hardware registers 803, whereby the power supply of the CPU 112 can be controlled via the group of hardware registers 803. When the CPU 112 or I/O processor 119 accesses the group of hardware registers 803, the group of hardware registers 803 produces, if necessary, an interrupt signal or the like to an entity that is an object of access so as to notify that the group of hardware registers has been accessed. The group of hardware registers 803 has a plurality of capabilities including the capability to notify that the group of hardware registers has been accessed. The plurality of capabilities is assigned to respective registers constituting the group of hardware registers 803 on a hardware basis.
  • FIG. 12 and FIG. 13 show examples of a data structure stored in the [0090] communication memory 802 included in each of the channel control units CHN110. FIG. 12 shows a data structure used to transfer information from the I/O processor 119 to the CPU 112. FIG. 13 shows a data structure used to transfer information from the CPU 112 to the I/O processor 119. Information to be transferred between the CPU 112 and I/O processor 119 is a group of information items to be transferred when the CPU 112 and I/O processor 119 are activated responsively to start of power supply or the like.
  • Information to be transferred from the I/[0091] O processor 119 to the CPU 112 includes a type of activated device, a diagnosis execution flag, a plurality of drive numbers, time instant information, the number of command retries, a command timeout value, and a plurality of temperature information items. The type of activated device refers to the type of device that is activated in response to a command translated by the BIOS 801 when the CPU 112 is activated. The type of activated device is, for example, “network” or “disk drive.” The drive number is a number with which a disk drive in which an OS is loaded is selected when the type of activated device is “disk drive.” According to the present embodiment, the concept of a LU is introduced into the storage devices 300. The OS or the like is stored in an LU. Therefore, an LU number assigned to each LU is regarded as the drive number. Priorities are assigned to the drive numbers. Assuming that drive number 0 has priority over drive number 1, the CPU 112 first attempts to activate the LU assigned drive number 0. If the CPU 112 fails in the activation, the CPU 112 attempts to activate the LU assigned drive number 1. When the CPU 112 is activated, the I/O processor 119 uses the diagnosis execution flag to direct the BIOS 801 to execute hardware diagnosis for the peripheries of the file server 800. For example, when initialization of the file server 800 is completed, if the CPU 112 alone is reactivated, the BIOS 801 need not re-execute hardware diagnosis. In this case, when the I/O processor 119 appropriately sets the diagnosis execution flag, the CPU 112 is prevented from re-executing hardware diagnosis for the file server 800. The CPU 112 uses the time instant information when the BIOS 801 or OS is run in the CPU 112. The I/O processor 119 acquires the time instant information from the management terminal 160, and hands it to the CPU 112. Consequently, the management terminal 160, I/O processor 119, and CPU 112 can share the same time instant information. The number of command retries and command timeout value are treated as conditions. The number of command retries refers to the number of times by which the BIOS 801 or OS residing in the CPU 112 retries a command when the command issued from the CPU 112 to the I/O processor 119 fails. The command timeout value refers to a timeout. The temperature information is a value specified for the CPU 112 so that the CPU 112 can sense an abnormality in a temperature change thereof.
  • According to the present embodiment, the I/[0092] O processor 119 can freely determine the type of activated device, drive numbers, time instant information, number of command retries, command timeout value, and plurality of temperature information items. The present embodiment is not limited to this mode. Alternatively, these values may be stored as initial values in the nonvolatile memory in which the BIOS is stored. Otherwise, an operator may enter the values at the management terminal 160 or the values may be registered in the memory included in the management terminal 160 in advance so that the management terminal 160 can hand the values to the I/O processor 119. The diagnosis execution flag is set based on logical judgment made during activation of the I/O processor 119 or by the operator. When the diagnosis execution flag is set based on logical judgment made during activation of the I/O processor 119, the actions of the CPU 112 or the run of the BIOS 801 loaded in the CPU 112 can be controlled by the I/O processor 119.
  • FIG. 13 shows a data structure used to transfer information from the [0093] CPU 112 to the I/O processor 119. A BIOS version specifies the version of an object code produced by the BIOS 801. The BIOS version is transferred from the CPU 112 to the I/O processor 119, and from the I/O processor 119 to the management terminal 160. A MAC address specifies a MAC (which stands for media access control) address in the CPU 112. The MAC address is a unique identifier assigned to hardware, and needed to assign an IP address required by the IP protocol to a DHCP (which stands for dynamic host configuration protocol) server on a LAN. 0 padding information is needed to fill out a word and has nothing to do with information.
  • FIG. 14 shows the hardware configuration in which the [0094] CPU 112 and I/O processor 119 are connected to each other over the internal LAN 151. As illustrated, the CPU 112 and I/O processor 119 are also connected to each other over the internal LAN 151, and can therefore communicate with the management terminal 160 over the internal LAN 151. Consequently, for example, the CPU 112 runs the network boot loader stored in advance in the nonvolatile RAM 804 so as to download activation software from the management terminal 160 into the memory 113 and execute the activation software. Eventually, a network booting process is executed with the management terminal 160 used as a server and the CPU 112 used as a client. Network booting is a method according to which: a network boot loader in a client and the management terminal 160 acting as a server activate and execute a boot residing in the management terminal 160 on a LAN for the purpose of loading an OS according to the combination of the IP protocol and the protocols of DHCP, TFTP (which stands for trivial file transfer protocol), and FTP (which stands for file transfer protocol) on the basis of, for example, the PXE standard or the like.
  • FIG. 15 is a block diagram showing the hardware configuration of each of the [0095] disk control units 140. As already described, the disk control units are connected to the storage devices 300 and also connected to the channel control units CHN110 via the connection unit 150. The disk control units 140 read or write data from or in the storage devices 300 by themselves or under the control of the channel control units CHN110.
  • Each of the [0096] disk control units 140 comprises an interface block 141, a memory 143, a CPU 142, a nonvolatile RAM 144, and board coupling connectors 145 which are integrated into a unit.
  • The [0097] interface block 141 includes a communication interface via which the disk control unit communicates with the channel control units 110 via the connection unit 150, a communication interface via which the disk control unit communicates with the storage devices 300, and a communication interface via which the disk control unit communicates with the management terminal 160 over the internal LAN 151.
  • The [0098] CPU 142 is responsible for control of the entire disk control unit 140, and communicates with the channel control units 110, storage devices 300, and management terminal 160. Various programs stored in the memory 143 and nonvolatile RAM 144 are run, whereby the features of the disk control units 140 included in the present embodiment are implemented. The features implemented in the disk control units 140 include control of the storage devices 300, control of a RAID, management of a duplicate of data stored in the storage devices 300, backup control, and control of remote control.
  • The [0099] nonvolatile RAM 144 is a nonvolatile memory in which a program according to which the CPU 142 extends control is stored. The contents of the program stored in the nonvolatile RAM 144 are written or rewritten in response to a directive given at the management terminal 160 or issued from the NAS manager 706.
  • Moreover, each of the [0100] disk control units 140 includes the board coupling connectors 145. When the board coupling connectors 145 are mated with respective connectors formed on the storage device control system 100, each of the disk control units 140 is electrically connected to the storage device control system 100.
  • (Software Configuration Diagram) [0101]
  • FIG. 16 shows the software configuration of the [0102] storage device system 600 in accordance with the present embodiment. As already described, the CPU 112 and I/O processor 119 are included in each of the channel control units CHN110. The number of CPUs 112 and the number of I/O processors 119 may be one, or a plurality of CPUs 112 and a plurality of I/O processors 119 may be included. An OS 701 and diverse applications including the NAS manager 706 are run in the CPU 112, whereby the CPU 112 acts as an NAS server. A microprogram implementing a controller is run in the I/O processor 119. A RAID controller 740 runs in the CPU 142 included in each of the disk control units 140. The CPU 161 included in the management terminal 160 acts as a network boot server 703. The network boot server 703 transfers a mini kernel 704 and an OS image 705 from the storage medium 167 or storage device 168 thereof to the CPUs 112 included in the channel control units CHN110 over the internal LAN 151. The network boot server 703 includes, for example, DHCP (which stands for dynamic host configuration protocol) server. The network boot server 703 assigns an IP address or a MAC address to each of the CPUs 112 and the I/O processors 11 included in the channel control units CHN110, and to the CPU 161, and enables transfer between the management terminal 160 and the CPUs 112 or between the CPU 161 and the I/O processors 119. For network booting, for example, the CPUs 112 act as a client and issues a DHCP request or a file transfer request to the network boot server 703. After the network booting is completed, the CPUs 112 each execute the mini kernel 704. Finally, each of the CPUs 112 installs the OS image 705 in the storage devices 300 via the I/O processor 119.
  • FIG. 16 also shows the software configuration of each of the [0103] information processing systems 200. Some of the information processing systems 200 adopt a network file system (NFS) 711, and the other information processing systems 200 adopt a common Internet file system (CIFS) 713. The NFS 711 is a file sharing protocol adopted mainly by a UNIX® operating system 714, while the CIFS 713 is a file sharing protocol adopted mainly by a Windows® operating system 715.
  • (Activation and Installation Performed by the Storage Device System) [0104]
  • A description will be made of a procedure according to which the channel control units CHN[0105] 110 are activated with power supplied thereto. By following the activating procedure, the channel control units CHN110 each act as a NAS server. In order to supply power to the channel control units CHN110, for example, after the channel control units CHN110 are inserted into the storage device system 600, the power supply of the storage device system 600 itself is turned on. Otherwise, the channel control units CHN110 are inserted into the storage device system 600 whose power supply has already been turned on, whereby power is supplied from the storage device system 600 to the power supply circuits included in the channel control units CHN110. Thus, power may be supplied to the channel control units CHN110. The former procedure that after the channel control units CHN110 are inserted into the storage device system 600, the power supply of the storage device system 600 itself is turned on will be described below.
  • FIG. 17 describes a flow ranging from a step of turning on the power supply of the [0106] storage device system 600, through a step of installing the OS image 705 from the management terminal 160 to the storage devices 300, to a step of activating the OS installed in the storage devices 300 so that the storage device system 600 will act as an NAS system. FIG. 17 lists the actions of the CPUs 112, I/O processors 119, management terminal 160, and storage devices 300 while associating them with one another. Time passes from above to below in the drawing. In the drawing, arrows drawn with solid lines indicate transmission of control information, and arrows drawn with dot lines indicate flows of data.
  • A description will be made orderly. [0107]
  • To begin with, the power supply of the [0108] storage device system 600 is turned on (step 1 for the CPUs 112, step 1 for the I/O processors 119, step 1 for the management terminal 160, step 1 for the storage devices 300). Responsively, the CPUs 112 autonomously start activating the respective BIOSs (step 2 for the CPUs 112). The I/O processors 119 initialize the hardware of the channel control units CHN110 (step 2 for the I/O processors 119). The management terminal 160 activates the OS and software installed thereon (step 2 for the management terminal 160). The storage devices 300 activate the respective disk drives which spin the disks (step 2 for the storage devices 300). When the disk drives spin the disks, physically rotational movements, stability of the rotational movements, and hardware diagnosis are carried out. The spinning therefore requires some time. Herein, the spinning is completed at the timing that the CPUs 112 perform activation for the second time (step 8 for the storage devices 300).
  • According to the present embodiment, since the power supply of the entire [0109] storage device system 600 is turned on, power is simultaneously supplied to all of the CPUs 112, I/O processors 119, management terminal 160, and storage devices 300. The present embodiment is not limited to this mode. For example, when the power supply of the storage device system 600 has already been turned on, if a new channel control unit CHN110 is added to the storage device system 600, power is not supplied to the CPU 112 and I/O processor 119 included in the channel control unit CHN110 until the power supply connector 750 of the channel control unit CHN110 is coupled to the storage device system 600. In this case, it is thought that the disk drives have already been activated and the disks have already been spun, extra control need not be extended. Nevertheless, the I/O processors 119 verify at step 12 that the disk drives have already spun the disks, and immediately pass control to the next step 13. For example, when power supply to the management terminal 160 alone is discontinued because of maintenance or the like, even if a new channel control unit CHN110 is added to the storage device system 600, the I/O processors 119 cannot communicate with the management terminal 160 at step 10.
  • In this case, the I/[0110] O processors 119 repeat step 10 regularly until the power supply of the management terminal 160 is turned on again. Otherwise, an emergency alarm LED included in the storage device system 600 or a communication line may be used to notify a maintenance engineer or the like of the fact that the power supply of the management terminal 160 should be turned on. Thus, the maintenance engineer or the like may be prompted to turn on the power supply of the management terminal 160 so that control can be passed to the next step.
  • In each of the [0111] CPUs 112, the BIOS 801 waits for a directive issued from the I/O processor 119 (step 3 for the CPUs 112). When initialization of the I/O processor 119 and initialization of the hardware of the own channel control unit CHN110 are completed, a diagnosis start request is issued to the CPU 112 in order to direct start of hardware diagnosis (step 4 for the I/O processors 119). At this time, the diagnosis start request is transmitted using either the communication memory 802 or the group of hardware registers 803 or both of them.
  • When the [0112] CPUs 112 detect the diagnosis start request, the CPUs 112 start diagnosing hardware (step 4 for the CPUs 112). When hardware diagnosis is completed (step 5 for the CPUs 112), the CPUs 112 store respective MAC addresses, which is assigned to the internal LAN 151 ports thereof, in the respective communication memories 802 (step 6 for the CPUs 112). When the I/O processors 119 sense that the MAC addresses have been stored in the respective communication memories 802 (step 6 for the I/O processors 119), the I/O processors 119 access the respective groups of hardware registers 803 so as to issue a CPU reset directive. Consequently, the CPUs 112 are physically reset (step 7 for the I/O processors 119). Consequently, after power supply to the CPUs 112 is discontinued temporarily, the power supply is restarted (step 7 for the CPUs 112). The CPUs 112 reactivate the respective BIOSs (step 8 for the CPUs 112), and wait for a directive issued from the respective I/O processors 119 (step 9 for the CPUs 112).
  • When the [0113] management terminal 160 completes activation, it starts installation. An operator may perform the installation, or the installation may be executed under the control of the CPU 161 according to a predefined program. Hereinafter, an operator shall perform the installation, and the CPU 161 included in the management terminal 160 shall perform processing according to an entry the operator made at the input device 165. After the installation is started, the management terminal 160 queries the I/O processors 119 about the MAC addresses, and receives the MAC addresses assigned to the CPUs 112 from the I/O processors 119 (step 10 for the management terminal 160). The operator enters and determines the number of command retries to be permitted after activation of the OS, a timeout value, and temperature information (step 11 for the management terminal 160). These values entered by the operator are transmitted from the management terminal 160 to the I/O processors 119 included in the channel control units CHN110 over the internal LAN 151. The operator directs the management terminal 160 to install a new OS. When the operator specifies a network boot disk as a type of activated device, the OS installation directive is transmitted from the management terminal 160 to the I/O processors 119 (step 11 for the management terminal 160).
  • In response to the OS installation directive, the I/[0114] O processors 119 verify whether the disk drives in the storage devices 300 have spun the disks so as to judge whether the storage devices 300 are usable (step 12 for the I/O processors 119). Since the disk drives in the storage devices 300 have already spun the disks (step 8 for the storage devices 300), the I/O processors 119 detect whether the disk drives have completed spinning the disks (step 13 for the I/O processors 119). If it cannot be detected that the disk drives have completed spinning the disks, the I/O processors 119 return an error response to the management terminal 160 so as to notify that the disk drives have not spun the disks. If the I/O processors 119 detect that the disk drives have completed spinning the disks, the I/O processors 119 store, in addition to the temperature information, number of command retries, and retry timeout value received from the management terminal 160, a diagnosis execution flag and a type of activated device in the respective communication memories 802 (step 14 for the I/O processors 119. Since hardware diagnosis has already been completed (at step 4 and step 5 for the CPUs 112), it is-unnecessary to perform hardware diagnosis again. Consequently, the I/O processors 119 set the diagnosis execution flag to a value that directs skip of hardware diagnosis. Moreover, the CPUs 112 must install the OS image 705 existent in the management terminal 160 into the storage devices 300 during activation after the CPUs 112 wait for a directive sent from the respective I/O processors. Consequently, the I/O processors 119 specify a network boot disk as the type of activated device, and stores the type of activated device in the respective communication memories 802 (step 14 for the I/O processors 119). When various information items are stored in the communication memories 802, the I/O processors 119 access the respective groups of hardware registers 803 and notify the respective CPUs 112 of the fact that the information items have been stored (step 15 for the I/O processors 119). The notification is intended to direct the CPUs 112 to execute processing.
  • The [0115] CPUs 112 sense whether the respective I/O processors 119 have issued a directive that processing should be continued (step 15 for the CPUs 112). The CPUs 112 acquire the temperature information, number of command retries, retry timeout value, diagnosis execution flag, and type of activated device from the respective communication memories 802 (step 16 for the CPUs 112). Since a network boot disk is specified as the type of activated device, the CPUs 112 start network booting (step 17 for the CPUs 112). Network booting progresses along with data communication over the internal LAN 151 between the boot loader running in each of the CPUs 112 and the network boot server 703 implemented in the management terminal 160. The network boot server 703 uses the MAC address information of each of the CPUs 112 (acquired at step 10 for the management terminal 160) to communicate with the boot loader. The CPUs 112 issue a network boot request to the network boot server 703 implemented in the management terminal 160 according to the PXE (which stands for preboot execution environment) standard (step 18 for the CPUs 112). The management terminal 160 receives the network boot request over the internal LAN 151 (step 18 for the management terminal 160). During network booting, the CPUs 112 act as network boot clients (step 19 for the CPUs 112). On the other hand, the management terminal 160 acts as the network boot server (step 19 for the management terminal 160). As a result of communication performed during network booting, the management terminal 160 allows the CPUs 112 to download the mini kernel 704. The mini kernel 704 downloaded into each of the CPUs 112 permits transfer of the OS image 705, which resides in the management terminal 160, to the storage devices 300 (step 20 for the CPUs 112). The OS image 705 is installed in the storage devices by way of the I/O processors 119, cache memory 130, and disk control units 140 under the control of the CPUs 112 included in the channel control units CHN110. After the installation is completed, the CPUs 112 issue an installation completion notification to the respective I/O processors 119 (step 21 for the CPUs 112). When the I/O processors 119 detect the installation completion notification (step 21 for the I/O processors 119), the I/O processors access the respective groups of hardware registers 803 so as to issue a CPU reset directive, and thus reset the respective CPUs 112 (step 22 for the I/O processors 119). Consequently, power is re-supplied to the CPUs 112 (step 22 for the CPUs 112). The CPUs 112 reactivate the respective BIOSs 801 (step 23 for the CPUs 112), and wait for a directive sent from the I/O processors 119 (step 24 for the CPUs 112).
  • The I/[0116] O processors 119 store time instant information, a type of activated device, and activated drive number information in the respective communication memories 802 (step 25 for the I/O processors 119). In this case, the I/O processors 119 specify a disk drive as the type of activated device. The I/O processors 119 access the respective groups of hardware registers 803 so as to issue a processing continuation directive to the respective CPUs 112 (step 26 for the I/O processors 119).
  • When the [0117] CPUs 112 detect the CPU processing continuation directive (step 26 for the CPUs 112), the CPUs 112 acquire the time instant information from the respective communication memories 802 (step 27 for the CPUs 112), and issue a command to the respective I/O processors 119. The CPUs 112 thus allow the respective I/O processors 119 to start disk booting (step 28 for the CPUs 112). The CPUs 112 allow the respective I/O processors 119 to load the OS image 705 stored in the storage devices 300 (step 29 for the CPUs 112). In this case, the OS image 705 is loaded from the storage devices 300 to the CPUs 112 by way of the disk control units 140, cache memory 130, and I/O processors 119.
  • When the [0118] OS image 705 is loaded into the CPUs 112, the CPUs 112 pass control from the respective BIOSs 801 to the OS image 705. Consequently, the OS is activated (step 30 for the CPUs 112). This permits the channel control units CHN110 to act as NAS devices and permits the storage device system 600 to act as an NAS system (step 31 for the CPUs 112).
  • Consequently, according to the present embodiment, when the power supply of the [0119] storage device system 600 is turned on, the I/O processors 119 control the respective CPUs 112. This enables installation of a new OS over a network or enables booting for installing the OS. Furthermore, the CPUs 112 and I/O processors 119 included in the respective channel control units 110, the CPU 161 included in the management terminal 160, the CPUs 142 included in the respective disk control units 140, and the storage devices 300 cooperate with one another. Consequently, the storage device system 600 can be activated efficiently for a limited period of time. Moreover, software can be installed efficiently.
  • The [0120] CPUs 112 used as file servers must often be controlled on a hardware basis. Specifically, when the CPUs 112 are activated or an OS is installed in the CPUs 112, the CPUs 112 must be re-booted, and power supply to the CPUs 112 must be started, discontinued, or restarted. This work is daily performed on a normal server computer. A maintenance engineer or a user manually performs the work at any time while looking at a screen image displayed on the operator console. In the storage device system 600 in which the file servers are incorporated in the form of hardware, the servers themselves need not support a special screen image or a user interface to be displayed on the console. Namely, according to a certain procedure like the one employed in the present invention, the above hardware operations are automatically performed according to a program installed in the I/O processors 119 through communications with the I/O processors 119. Consequently, activation of the servers and installation of an OS can be automated. A UNIX or any other general-purpose OS can be adapted to the OS to be installed in the file servers with minimal modification. Since the UNIX or any other general-purpose OS is widely adopted as an OS to be installed in file servers, it is advantageous that the UNIX or any other general-purpose OS can be installed with a little modification. Moreover, this leads to a reduction in the period required for development. Furthermore, assuming that the present storage device system is divided into a file server section and a storage device controller section, the storage device controller section that has a close relationship with the disk drives can control booting, OS installation, and other work to be performed by the file server section during a period of time during which the disk drives spin the disks or any other physical movements are made. In other words, a section of a storage device system whose hardware is restricted, that is, in which the period of time during which disk drives spin disks is restricted can actively control booting of the entire system or installation as soon as the hardware-related restriction is lifted. From this viewpoint, the storage device system in accordance with the present invention is an efficient and reasonable system.
  • The present embodiment has been described by taking for instance a method of turning on the power supply of the [0121] storage device system 600 itself after the channel control units CHN110 are inserted into the storage device system 600. The present embodiment is not limited to this mode. Alternatively, the channel control units CHN110 may be inserted into the storage device system 600 whose power supply has already been turned on in order to supply power to the channel control units CHN110.
  • The present embodiment has been described so far. The embodiment is presented for a better understanding of the present invention, but the present invention is not limited to the embodiment. The present invention can be varied or modified without a departure from the gist thereof, and encompasses the equivalents. [0122]
  • According to the present invention, there is provided a novel storage device system capable of being connected on a plurality of different types of networks. Furthermore, there are provided a storage device control system and a method of controlling activation of the storage device system which are needed to invent the storage device system. [0123]

Claims (18)

What is claimed is:
1. A storage device system comprising:
a plurality of storage devices in which information is stored;
a storage device control section for controlling storage of information in said plurality of storage devices;
a connection unit connected to said storage device control section; and
a first communication control section including: a first processor that is connected to said storage device control section via said connection unit and also connected on a first network external to said storage device system, that converts information of a first form received over said first external network into information of a second form, and that issues a request for access to said plurality of storage devices; and a second processor that accesses said plurality of storage devices via said connection unit and said storage device control section in response to the access request issued from said first processor, and that controls activation of said first processor.
2. A storage device system according to claim 1, further comprising a second communication control section connected on a second network external to said storage device system, wherein:
said first communication control section is formed with the same circuit board as said second communication control section is.
3. A storage device system according to claim 1, wherein:
said first processor diagnoses the hardware thereof;
said second processor issues a request for start of hardware diagnosis of said first processor to said first processor.
4. A storage device system according to claim 3, further comprising a management terminal connected to each of said first communication control section and said second communication control section, wherein:
said second processor issues a request for start of first processing to said first processor; and
said first processor acquires first software from said management terminal in response to the first processing start request issued from said second processor.
5. A storage device system according to claim 4, wherein said first processor acquires second software from said management terminal under the control of the first software acquired from said management terminal, and writes the second software in said plurality of storage devices via said connection unit and said storage device control section.
6. A storage device system according to claim 5, wherein:
said second processor issues a request for start of second processing to said first processor;
said first processor acquires the second software written in said plurality of storage devices via said connection unit and said storage device control section in response to the second processing start request issued from said second processor.
7. A storage device system according to claim 4, wherein both the first processing start request and second processing start request contain time instant information.
8. A storage device system according to claim 1, wherein:
said first communication control section includes a storage device in which third software is stored;
said first processor activates the third software so as to activate said first communication control section, and waits for a request issued from said second processor.
9. A storage device system according to claim 8, further comprising a second communication control section that is connected on a second network external to said storage device system, wherein:
said first communication control section is formed with the same circuit board as said second communication control section is.
10. A storage device system according to claim 9, wherein:
said first processor diagnoses the hardware thereof; and
said second processor issues a request for start of hardware diagnosis of said first processor to said first processor.
11. A storage device system according to claim 10, further comprising a management terminal connected to each of said first communication control section and said second communication control section, wherein:
said second processor issues a request for start of first processing to said first processor; and
said first processor acquires first software from said management terminal in response to the first processing start request issued from said second processor.
12. A storage device system according to claim 11, wherein said first processor acquires second software from said management terminal under the control of the first software acquired from said management terminal, and writes the second software in said plurality of storage devices via said connection unit and said storage device control section.
13. A storage device system according to claim 12, wherein:
said second processor issues a request for start of second processing to said first processor; and
said first processor acquires the second software written in said plurality of storage devices via said connection unit and said storage device control section in response to the second processing start request issued from said second processor.
14. A storage device system according to claim 11, wherein both said first processing start request and said second processing start request contain time instant information.
15. A method of activating a storage device system that comprises a plurality of storage devices in which information is stored, a storage device control section which controls storage of information in said plurality of storage devices, a connection unit connected to said storage device control section, and a first communication control section connected to said storage device control section via said connection unit and also connected on a first network external to said storage device system, wherein:
a first processor that converts information of a first form received over said first external network into information of a second form, and issues a request for access to said plurality of storage devices has the activation thereof controlled by a second processor that accesses said plurality of storage devices via said connection unit and said storage device control section in response to the access request issued from said first processor;
said second processor issues a request for start of hardware diagnosis of said first processor to said first processor; and
said first processor performs hardware diagnosis in response to the hardware diagnosis start request issued from said second processor.
16. A storage device system activation method according to claim 15, wherein:
said storage device system includes a management terminal connected to each of said first communication control section and said second communication control section;
said second processor issues a request for start of first processing to said first processor; and
said first processor acquires first software from said management terminal in response to the first processing start request issued from said second processor.
17. A storage device system activation method according to claim 16, wherein said first processor acquires second software from said management terminal under the control of the first software acquired from said management terminal, and writes the second software in said plurality of storage devices via said connection unit and said storage device control section.
18. A storage device system activation method according to claim 17, wherein:
said second processor issues a request for start of second processing to said first processor; and
said first processor acquires the second software written in said plurality of storage devices via said connection unit and said storage device control section in response to the second processing start request issued from said second processor.
US10/673,162 2003-01-24 2003-09-30 Storage device system and storage device system activating method Abandoned US20040148329A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/348,088 US7882206B2 (en) 2003-01-24 2009-01-02 Storage device system and storage device system activating method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2003-015525 2003-01-24
JP2003015525A JP4274523B2 (en) 2003-01-24 2003-01-24 Storage device system and start method of storage device system

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/348,088 Continuation US7882206B2 (en) 2003-01-24 2009-01-02 Storage device system and storage device system activating method

Publications (1)

Publication Number Publication Date
US20040148329A1 true US20040148329A1 (en) 2004-07-29

Family

ID=32732807

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/673,162 Abandoned US20040148329A1 (en) 2003-01-24 2003-09-30 Storage device system and storage device system activating method
US12/348,088 Expired - Fee Related US7882206B2 (en) 2003-01-24 2009-01-02 Storage device system and storage device system activating method

Family Applications After (1)

Application Number Title Priority Date Filing Date
US12/348,088 Expired - Fee Related US7882206B2 (en) 2003-01-24 2009-01-02 Storage device system and storage device system activating method

Country Status (2)

Country Link
US (2) US20040148329A1 (en)
JP (1) JP4274523B2 (en)

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030061382A1 (en) * 2001-09-21 2003-03-27 Dell Products L.P. System and method for naming hosts in a distributed data processing system
US20040215878A1 (en) * 2003-01-20 2004-10-28 Hitachi, Ltd. Method of controlling storage device controlling apparatus, and storage device controlling apparatus
US20050114615A1 (en) * 2003-11-26 2005-05-26 Hiroshi Ogasawara Disk array system
US20050120263A1 (en) * 2003-11-28 2005-06-02 Azuma Kano Disk array system and method for controlling disk array system
US20050141184A1 (en) * 2003-12-25 2005-06-30 Hiroshi Suzuki Storage system
US20050149645A1 (en) * 2004-01-06 2005-07-07 Hitachi, Ltd. Storage control device
US20050149672A1 (en) * 2003-05-22 2005-07-07 Katsuyoshi Suzuki Disk array apparatus and method for controlling the same
US20060008782A1 (en) * 2004-07-08 2006-01-12 Williams Jennette L Device for teaching phonetic alphabet
JP2006048392A (en) * 2004-08-05 2006-02-16 Internatl Business Mach Corp <Ibm> Information processor, program, recording medium and control method
US20060085522A1 (en) * 2004-10-19 2006-04-20 Spry Andrew J Method and apparatus for fully automated iSCSI target configuration
US20060164550A1 (en) * 2003-04-24 2006-07-27 Kyosuke Yoshimoto Video device, video module unit, and video device operation method
US20060184823A1 (en) * 2005-02-17 2006-08-17 Kunihito Matsuki Access control device and interface installed in same
US20070168046A1 (en) * 2003-08-04 2007-07-19 Mitsubishi Denki Kabushiki Kaisha Image information apparatus and module unit
US20080155082A1 (en) * 2006-12-22 2008-06-26 Fujitsu Limited Computer-readable medium storing file delivery program, file delivery apparatus, and distributed file system
US20080301365A1 (en) * 2003-05-22 2008-12-04 Hiromi Matsushige Storage unit and circuit for shaping communication signal
US20090109790A1 (en) * 2007-10-29 2009-04-30 Elpida Memory, Inc. Semiconductor device including anti-fuse circuit, and method of writing address to anti-fuse circuit
US7823010B2 (en) 2004-02-04 2010-10-26 Hitachi, Ltd. Anomaly notification control in disk array
US20100302833A1 (en) * 2009-05-29 2010-12-02 Elpida Memory, Inc. Semiconductor device having nonvolatile memory element and manufacturing method thereof
US20110246597A1 (en) * 2010-04-02 2011-10-06 Swanson Robert C Remote direct storage access
CN104423896A (en) * 2013-08-19 2015-03-18 索尼公司 Storage control device, storage device, information processing system, and storage control method
US10560553B2 (en) * 2016-09-14 2020-02-11 International Business Machines Corporation Assigning IP pools to file access protocols for NAS failover

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4472498B2 (en) * 2004-11-25 2010-06-02 日本電信電話株式会社 Storage connection method of diskless boot system, system, management server, storage, and program therefor
WO2012137411A1 (en) * 2011-04-01 2012-10-11 パナソニック株式会社 Interface relay device and interface relay method
DE102011107092B4 (en) 2011-07-11 2017-09-14 Fujitsu Ltd. Computer system, method for starting a server computer, server computer, management station and use
CN104253734A (en) * 2013-06-27 2014-12-31 宇宙互联有限公司 Transmission management device, system and method
CN104253753A (en) * 2013-06-27 2014-12-31 宇宙互联有限公司 Transmission management device, system and method
JP7263101B2 (en) * 2019-04-26 2023-04-24 キヤノン株式会社 Information processing device, data verification method

Citations (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5285528A (en) * 1991-02-22 1994-02-08 International Business Machines Corporation Data structures and algorithms for managing lock states of addressable element ranges
US5504873A (en) * 1989-11-01 1996-04-02 E-Systems, Inc. Mass data storage and retrieval system
US5548724A (en) * 1993-03-22 1996-08-20 Hitachi, Ltd. File server system and file access control method of the same
US5659718A (en) * 1994-08-19 1997-08-19 Xlnt Designs, Inc. Synchronous bus and bus interface device
US5671377A (en) * 1994-07-19 1997-09-23 David Sarnoff Research Center, Inc. System for supplying streams of data to multiple users by distributing a data stream to multiple processors and enabling each user to manipulate supplied data stream
US5710881A (en) * 1993-11-09 1998-01-20 Hewlett Packard Company Data merging method and apparatus for shared memory multiprocessing computer systems
US5774731A (en) * 1995-03-22 1998-06-30 Hitachi, Ltd. Exclusive control method with each node controlling issue of an exclusive use request to a shared resource, a computer system therefor and a computer system with a circuit for detecting writing of an event flag into a shared main storage
US5832222A (en) * 1996-06-19 1998-11-03 Ncr Corporation Apparatus for providing a single image of an I/O subsystem in a geographically dispersed computer system
US5928327A (en) * 1996-08-08 1999-07-27 Wang; Pong-Sheng System and process for delivering digital data on demand
US6006342A (en) * 1997-12-11 1999-12-21 International Business Machines Corporation Failover and failback system for a direct access storage device
US6078990A (en) * 1998-02-06 2000-06-20 Ncr Corporation Volume set configuration using a single operational view
US6105136A (en) * 1998-02-13 2000-08-15 International Business Machines Corporation Computer system which is disabled when it is disconnected from a network
US6105122A (en) * 1998-02-06 2000-08-15 Ncr Corporation I/O protocol for highly configurable multi-node processing system
US6173374B1 (en) * 1998-02-11 2001-01-09 Lsi Logic Corporation System and method for peer-to-peer accelerated I/O shipping between host bus adapters in clustered computer network
US6253271B1 (en) * 1997-10-22 2001-06-26 Auspex Systems, Inc. Bridge for direct data storage device access
US20010005894A1 (en) * 1999-12-27 2001-06-28 Masahiro Fukui Remote power management system of information processing apparatus or the like
US6282642B1 (en) * 1998-11-18 2001-08-28 International Business Machines Corporation System for presetting a first or second remote boot protocol by a computer remotely receiving and storing a boot parameter prior to being powered on
US6286038B1 (en) * 1998-08-03 2001-09-04 Nortel Networks Limited Method and apparatus for remotely configuring a network device
US6421711B1 (en) * 1998-06-29 2002-07-16 Emc Corporation Virtual ports for data transferring of a data storage system
US20020105830A1 (en) * 2001-02-08 2002-08-08 United Microelectronics Corp. Double-bit non-voltatile memory unit and corresponding data read/write method
US6438586B1 (en) * 1996-09-30 2002-08-20 Emc Corporation File transfer utility which employs an intermediate data storage system
US20020116452A1 (en) * 2000-03-03 2002-08-22 Surgient Networks, Inc. Network connected computing system including storage system
US20020152339A1 (en) * 2001-04-09 2002-10-17 Akira Yamamoto Direct access storage system with combined block interface and file interface access
US20020178143A1 (en) * 2001-05-25 2002-11-28 Kazuhisa Fujimoto Storage system, a method of file data backup and method of copying of file data
US6513097B1 (en) * 1999-03-03 2003-01-28 International Business Machines Corporation Method and system for maintaining information about modified data in cache in a storage system for use during a system failure
US20030093541A1 (en) * 2001-09-28 2003-05-15 Lolayekar Santosh C. Protocol translation in a storage system
US20030225735A1 (en) * 2002-05-30 2003-12-04 Weber Bret S. Apparatus and method for providing transparent sharing of channel resources by multiple host machines utilizing mixed mode block and file protocols
US20040139168A1 (en) * 2003-01-14 2004-07-15 Hitachi, Ltd. SAN/NAS integrated storage system
US20040205294A1 (en) * 2003-01-20 2004-10-14 Hitachi, Ltd. Method of controlling storage device controlling apparatus, and storage device controlling apparatus
US20040215878A1 (en) * 2003-01-20 2004-10-28 Hitachi, Ltd. Method of controlling storage device controlling apparatus, and storage device controlling apparatus
US6880104B2 (en) * 2000-12-21 2005-04-12 Nec Corporation Computer system for mutual communication through network and its memory management method
US7062595B2 (en) * 2001-04-24 2006-06-13 Broadcom Corporation Integrated gigabit ethernet PCI-X controller

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH03138752A (en) 1989-10-25 1991-06-13 Canon Inc Information processor
JPH06161974A (en) 1992-11-24 1994-06-10 Komatsu Ltd Diagnosing method for multi-cpu board
US5854905A (en) * 1996-09-03 1998-12-29 Intel Corporation Extensible bios for boot support of devices on multiple hierarchical buses
US6499073B1 (en) * 1997-05-13 2002-12-24 Micron Electronics, Inc. System using programmable processor for selectively enabling or disabling power to adapter in response to respective request signals
JP3614650B2 (en) 1998-03-20 2005-01-26 富士通株式会社 Multiprocessor control system and boot device and boot control device used therefor
US6263441B1 (en) * 1998-10-06 2001-07-17 International Business Machines Corporation Real-time alert mechanism for signaling change of system configuration
US6990685B1 (en) * 2000-06-15 2006-01-24 Dell Products L.P. System and method for tracking bootable devices
US20030105830A1 (en) * 2001-12-03 2003-06-05 Duc Pham Scalable network media access controller and methods

Patent Citations (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5504873A (en) * 1989-11-01 1996-04-02 E-Systems, Inc. Mass data storage and retrieval system
US5285528A (en) * 1991-02-22 1994-02-08 International Business Machines Corporation Data structures and algorithms for managing lock states of addressable element ranges
US5548724A (en) * 1993-03-22 1996-08-20 Hitachi, Ltd. File server system and file access control method of the same
US5710881A (en) * 1993-11-09 1998-01-20 Hewlett Packard Company Data merging method and apparatus for shared memory multiprocessing computer systems
US6502136B1 (en) * 1994-03-24 2002-12-31 Hitachi, Ltd. Exclusive control method with each node controlling issue of an exclusive use request to a shared resource, a computer system therefor and a computer system with a circuit for detecting writing of an event flag into a shared main storage
US6330604B1 (en) * 1994-03-24 2001-12-11 Hitachi, Ltd. Exclusive control method with each node controlling issue of an exclusive use request to a shared resource, a computer system therefor and a computer system with a circuit for detecting writing of an event flag into a shared main storage
US5671377A (en) * 1994-07-19 1997-09-23 David Sarnoff Research Center, Inc. System for supplying streams of data to multiple users by distributing a data stream to multiple processors and enabling each user to manipulate supplied data stream
US5659718A (en) * 1994-08-19 1997-08-19 Xlnt Designs, Inc. Synchronous bus and bus interface device
US5774731A (en) * 1995-03-22 1998-06-30 Hitachi, Ltd. Exclusive control method with each node controlling issue of an exclusive use request to a shared resource, a computer system therefor and a computer system with a circuit for detecting writing of an event flag into a shared main storage
US5832222A (en) * 1996-06-19 1998-11-03 Ncr Corporation Apparatus for providing a single image of an I/O subsystem in a geographically dispersed computer system
US5928327A (en) * 1996-08-08 1999-07-27 Wang; Pong-Sheng System and process for delivering digital data on demand
US6438586B1 (en) * 1996-09-30 2002-08-20 Emc Corporation File transfer utility which employs an intermediate data storage system
US6253271B1 (en) * 1997-10-22 2001-06-26 Auspex Systems, Inc. Bridge for direct data storage device access
US6006342A (en) * 1997-12-11 1999-12-21 International Business Machines Corporation Failover and failback system for a direct access storage device
US6105122A (en) * 1998-02-06 2000-08-15 Ncr Corporation I/O protocol for highly configurable multi-node processing system
US6078990A (en) * 1998-02-06 2000-06-20 Ncr Corporation Volume set configuration using a single operational view
US6173374B1 (en) * 1998-02-11 2001-01-09 Lsi Logic Corporation System and method for peer-to-peer accelerated I/O shipping between host bus adapters in clustered computer network
US6105136A (en) * 1998-02-13 2000-08-15 International Business Machines Corporation Computer system which is disabled when it is disconnected from a network
US6421711B1 (en) * 1998-06-29 2002-07-16 Emc Corporation Virtual ports for data transferring of a data storage system
US6286038B1 (en) * 1998-08-03 2001-09-04 Nortel Networks Limited Method and apparatus for remotely configuring a network device
US6282642B1 (en) * 1998-11-18 2001-08-28 International Business Machines Corporation System for presetting a first or second remote boot protocol by a computer remotely receiving and storing a boot parameter prior to being powered on
US6513097B1 (en) * 1999-03-03 2003-01-28 International Business Machines Corporation Method and system for maintaining information about modified data in cache in a storage system for use during a system failure
US20010005894A1 (en) * 1999-12-27 2001-06-28 Masahiro Fukui Remote power management system of information processing apparatus or the like
US20020116452A1 (en) * 2000-03-03 2002-08-22 Surgient Networks, Inc. Network connected computing system including storage system
US6880104B2 (en) * 2000-12-21 2005-04-12 Nec Corporation Computer system for mutual communication through network and its memory management method
US20020105830A1 (en) * 2001-02-08 2002-08-08 United Microelectronics Corp. Double-bit non-voltatile memory unit and corresponding data read/write method
US20020152339A1 (en) * 2001-04-09 2002-10-17 Akira Yamamoto Direct access storage system with combined block interface and file interface access
US7062595B2 (en) * 2001-04-24 2006-06-13 Broadcom Corporation Integrated gigabit ethernet PCI-X controller
US20020178143A1 (en) * 2001-05-25 2002-11-28 Kazuhisa Fujimoto Storage system, a method of file data backup and method of copying of file data
US20030093541A1 (en) * 2001-09-28 2003-05-15 Lolayekar Santosh C. Protocol translation in a storage system
US20030225735A1 (en) * 2002-05-30 2003-12-04 Weber Bret S. Apparatus and method for providing transparent sharing of channel resources by multiple host machines utilizing mixed mode block and file protocols
US20040139168A1 (en) * 2003-01-14 2004-07-15 Hitachi, Ltd. SAN/NAS integrated storage system
US20040205294A1 (en) * 2003-01-20 2004-10-14 Hitachi, Ltd. Method of controlling storage device controlling apparatus, and storage device controlling apparatus
US20040215878A1 (en) * 2003-01-20 2004-10-28 Hitachi, Ltd. Method of controlling storage device controlling apparatus, and storage device controlling apparatus

Cited By (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030061382A1 (en) * 2001-09-21 2003-03-27 Dell Products L.P. System and method for naming hosts in a distributed data processing system
US7155595B2 (en) 2003-01-20 2006-12-26 Hitachi, Ltd. Method of controlling storage device controlling apparatus, and storage device controlling apparatus
US20040215878A1 (en) * 2003-01-20 2004-10-28 Hitachi, Ltd. Method of controlling storage device controlling apparatus, and storage device controlling apparatus
US7788457B2 (en) 2003-01-20 2010-08-31 Hitachi, Ltd. Method of controlling storage device controlling apparatus, and storage device controlling apparatus
US20070061534A1 (en) * 2003-01-20 2007-03-15 Hitachi, Ltd. Method of controlling storage device controlling apparatus, and storage device controlling apparatus
US20060164550A1 (en) * 2003-04-24 2006-07-27 Kyosuke Yoshimoto Video device, video module unit, and video device operation method
US20080301365A1 (en) * 2003-05-22 2008-12-04 Hiromi Matsushige Storage unit and circuit for shaping communication signal
US8200898B2 (en) 2003-05-22 2012-06-12 Hitachi, Ltd. Storage apparatus and method for controlling the same
US7685362B2 (en) 2003-05-22 2010-03-23 Hitachi, Ltd. Storage unit and circuit for shaping communication signal
US8151046B2 (en) 2003-05-22 2012-04-03 Hitachi, Ltd. Disk array apparatus and method for controlling the same
US20050149672A1 (en) * 2003-05-22 2005-07-07 Katsuyoshi Suzuki Disk array apparatus and method for controlling the same
US20090150609A1 (en) * 2003-05-22 2009-06-11 Katsuyoshi Suzuki Disk array apparatus and method for controlling the same
US8429342B2 (en) 2003-05-22 2013-04-23 Hitachi, Ltd. Drive apparatus and method for controlling the same
US20070168046A1 (en) * 2003-08-04 2007-07-19 Mitsubishi Denki Kabushiki Kaisha Image information apparatus and module unit
US20050138287A1 (en) * 2003-11-26 2005-06-23 Hitachi, Ltd. Disk array system
US20060230227A1 (en) * 2003-11-26 2006-10-12 Hitachi, Ltd. Disk array system
US7043604B2 (en) 2003-11-26 2006-05-09 Hitachi, Ltd. Disk array system
US20080114933A1 (en) * 2003-11-26 2008-05-15 Hitachi, Ltd. Disk array system
US20050114615A1 (en) * 2003-11-26 2005-05-26 Hiroshi Ogasawara Disk array system
US7581062B2 (en) 2003-11-26 2009-08-25 Hitachi, Ltd. Disk array system
US7376787B2 (en) 2003-11-26 2008-05-20 Hitachi, Ltd. Disk array system
US7099996B2 (en) * 2003-11-26 2006-08-29 Hitachi, Ltd. Disk array system
US20050154942A1 (en) * 2003-11-28 2005-07-14 Azuma Kano Disk array system and method for controlling disk array system
US20050117462A1 (en) * 2003-11-28 2005-06-02 Azuma Kano Disk array system and method for controlling disk array system
US20050117468A1 (en) * 2003-11-28 2005-06-02 Azuma Kano Disk array system and method of controlling disk array system
US20050120264A1 (en) * 2003-11-28 2005-06-02 Azuma Kano Disk array system and method for controlling disk array system
US20050120263A1 (en) * 2003-11-28 2005-06-02 Azuma Kano Disk array system and method for controlling disk array system
US8468300B2 (en) 2003-11-28 2013-06-18 Hitachi, Ltd. Storage system having plural controllers and an expansion housing with drive units
US7865665B2 (en) 2003-11-28 2011-01-04 Hitachi, Ltd. Storage system for checking data coincidence between a cache memory and a disk drive
US20070170782A1 (en) * 2003-12-25 2007-07-26 Hiroshi Suzuki Storage system
US20070063587A1 (en) * 2003-12-25 2007-03-22 Hiroshi Suzuki Storage system
US7671485B2 (en) 2003-12-25 2010-03-02 Hitachi, Ltd. Storage system
US20050141184A1 (en) * 2003-12-25 2005-06-30 Hiroshi Suzuki Storage system
US6988151B2 (en) 2004-01-06 2006-01-17 Hitachi, Ltd. Storage control device with a plurality of channel control sections
US20050149645A1 (en) * 2004-01-06 2005-07-07 Hitachi, Ltd. Storage control device
US8365013B2 (en) 2004-02-04 2013-01-29 Hitachi, Ltd. Anomaly notification control in disk array
US8015442B2 (en) 2004-02-04 2011-09-06 Hitachi, Ltd. Anomaly notification control in disk array
US7823010B2 (en) 2004-02-04 2010-10-26 Hitachi, Ltd. Anomaly notification control in disk array
US20060008782A1 (en) * 2004-07-08 2006-01-12 Williams Jennette L Device for teaching phonetic alphabet
JP2006048392A (en) * 2004-08-05 2006-02-16 Internatl Business Mach Corp <Ibm> Information processor, program, recording medium and control method
US20060126464A1 (en) * 2004-08-05 2006-06-15 Kosugi Tomoaki Information processing system, program, recording medium, and control method
JP4629382B2 (en) * 2004-08-05 2011-02-09 インターナショナル・ビジネス・マシーンズ・コーポレーション Information processing apparatus, program, recording medium, and control method
US7584272B2 (en) * 2004-10-19 2009-09-01 Lsi Corporation Method and apparatus for fully automated iSCSI target configuration
US20060085522A1 (en) * 2004-10-19 2006-04-20 Spry Andrew J Method and apparatus for fully automated iSCSI target configuration
EP1693755A1 (en) * 2005-02-17 2006-08-23 Hitachi, Ltd. Storage control device for reporting fault recovery and fault occurence information
US7478267B2 (en) 2005-02-17 2009-01-13 Hitachi, Ltd. Access control device and interface installed in same
US20060184823A1 (en) * 2005-02-17 2006-08-17 Kunihito Matsuki Access control device and interface installed in same
US20080155082A1 (en) * 2006-12-22 2008-06-26 Fujitsu Limited Computer-readable medium storing file delivery program, file delivery apparatus, and distributed file system
US7952950B2 (en) 2007-10-29 2011-05-31 Elpida Memory, Inc. Semiconductor device including anti-fuse circuit, and method of writing address to anti-fuse circuit
US20090109790A1 (en) * 2007-10-29 2009-04-30 Elpida Memory, Inc. Semiconductor device including anti-fuse circuit, and method of writing address to anti-fuse circuit
US8422327B2 (en) 2009-05-29 2013-04-16 Elpida Memory, Inc. Semiconductor device having nonvolatile memory element and manufacturing method thereof
US20100302833A1 (en) * 2009-05-29 2010-12-02 Elpida Memory, Inc. Semiconductor device having nonvolatile memory element and manufacturing method thereof
US20110246597A1 (en) * 2010-04-02 2011-10-06 Swanson Robert C Remote direct storage access
US9015268B2 (en) * 2010-04-02 2015-04-21 Intel Corporation Remote direct storage access
CN104423896A (en) * 2013-08-19 2015-03-18 索尼公司 Storage control device, storage device, information processing system, and storage control method
US10560553B2 (en) * 2016-09-14 2020-02-11 International Business Machines Corporation Assigning IP pools to file access protocols for NAS failover

Also Published As

Publication number Publication date
JP4274523B2 (en) 2009-06-10
US20090157856A1 (en) 2009-06-18
JP2004227361A (en) 2004-08-12
US7882206B2 (en) 2011-02-01

Similar Documents

Publication Publication Date Title
US7882206B2 (en) Storage device system and storage device system activating method
US7219144B2 (en) Disk array system and fault information control method
US7099996B2 (en) Disk array system
US7574575B2 (en) Disk array device including a system LU for storing control information in the disk array and backup LU for backing up the control information and controlling method thereof
EP0552873B1 (en) Modifying system configuration in a computer system
US6973587B1 (en) Systems and methods for out-of-band booting of a computer
JP4001877B2 (en) Automatic recovery from hardware errors in the I / O fabric
US5920709A (en) Bus interface for IDE device
US6976058B1 (en) Computer card for storing bootable images and providing remote management functions
US7305670B2 (en) Method of installing software on storage device controlling apparatus, method of controlling storage device controlling apparatus, and storage device controlling apparatus
US20080005502A1 (en) Storage device controlling device and control method for storage device controlling device
US20060174150A1 (en) Storage system and power control method therefor, adapter and power control method therefor, and storage controller and control method therefor
JP2004145854A (en) Method and system for data backup and recovery
US7376761B2 (en) Configuration data management
CN1834912B (en) ISCSI bootstrap driving system and method for expandable internet engine
US20040177226A1 (en) Storage system with snapshot-backup capability and method for the same
US7266596B2 (en) Dynamic storage space linking

Legal Events

Date Code Title Description
AS Assignment

Owner name: HITACHI, LTD., JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:OGASAWARA, HIROSHI;TAKATA, YUTAKA;KOBAYASHI, NAOTAKA;REEL/FRAME:014550/0039

Effective date: 20030901

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION