US 6,523,131 B1Grant

Method for communicating a software-generated pulse waveform between two servers in a network

Issue Date:2003-02-18

•18 Claims

•11 Drawing Sheets

Abstract

A method of monitoring a status condition of a first server with a second server in a server network, and also providing synchronization and messaging between the two servers, the method including: transmitting a software-generated pulse waveform from the first server to a device coupled to the first server, wherein the software-generated pulse waveform is comprises a first command corresponding to a logic level low and a second command corresponding to a logic level high; setting said device to a first state during logic level lows of said pulse waveform and to a second state during logic level highs of said pulse waveform; receiving the software-generated pulse waveform with the second server by determining when said device is in the first state and when it is in the second state; and determining when said device no longer changes from the first state to the second state. In order to provide synchronization and messaging, said pulse waveform is frequency modulated in order to communicate specified commands and/or reference points between the two servers.

Metadata

Assignee

Micron Technology, Inc.

Inventors

Bruce Findlay
Michael Chrabaszcz

Application Information

Application Number:US 09/658,333

Filing Date:2000-09-08

Priority Date:1997-05-13

Art Unit:7

Classifications

IPC:

G06F 1100

Field of Search:

714 4714 5714 42714 43

Patent Drawings (11 sheets)

Description

[0002] This application is a division of to U.S. patent application Ser. No. 08/942,221 entitled, “A System for Communicating a Software Generated Pulse Waveform Between Two Servers in a Network,” which was filed on Oct. 1, 1997, now U.S. Pat. No. 6,163,853 which claims benefit of provisional application Ser. No. 60/046,327 filed May 13, 1997.

INCORPORATION BY REFERENCE OF COMMONLY OWNED APPLICATIONS

[0003] The following patent applications, commonly owned and filed Oct. 1, 1997, are hereby incorporated herein in their entirety by reference thereto:


	Application
Title	No./Patent No.

“System Architecture for Remote Access and	08/942,160/6,266,721
Control of Environmental Management”
“Method of Remote Access and Control of	08/942,215/6,189,109
Environmental Management”
“System for Independent Powering of Diagnostic	08/942,410/6,202,160
Processes on a Computer System”
“Method of Independent Powering of Diagnostic	08/942,320/6,134,668
Processes on a Computer System”
“Diagnostic and Managing Distributed Processor	08/942,402/6,338,150
System”
“Method for Managing a Distributed Processor	08/942,448/6,249,885
System”
“System for Mapping Environmental Resources to	08/942,222/6,122,758
Memory for Program Access”
“Method for Mapping Environmental Resources	08/942,214/6,199,173
to Memory for Program Access”
“Hot Add of Devices Software Architecture”	08/942,309
“Method for The Hot Add of Devices”	08/942,306/6,247,080
“Hot Swap of Devices Software Architecture”	08/942,311/6,192,434
“Method for The Hot Swap of Devices”	08/942,457/6,304,929
“Method for the Hot Add of a Network Adapter	08/943,072/5,892,928
on a System Including a Dynamically Loaded
Adapter Driver”
“Method for the Hot Add of a Mass Storage	08/942,069/6,219,734
Adapter on a System Including a Statically
Loaded Adapter Driver”
“Method for the Hot Add of a Network Adapter	08/942,465/6,202,111
on a System Including a Statically Loaded
Adapter Driver”
“Method for the Hot Add of a Mass Storage	08/962,963/6,179,486
Adapter on a System Including a Dynamically
Loaded Adapter Driver”
“Method for the Hot Swap of a Network Adapter	08/943,078/5,889,965
on a System Including a Dynamically Loaded
Adapter Driver”
“Method for the Hot Swap of a Mass Storage	08/942,336/6,249,828
Adapter on a System Including a Statically
Loaded Adapter Driver”
“Method for the Hot Swap of a Network Adapter	08/942,459/6,219,734
on a System Including a Statically Loaded
Adapter Driver”
“Method for the Hot Swap of a Mass Storage	08/942,458/6,173,346
Adapter on a System Including a Dynamically
Loaded Adapter Driver”
“Method of Performing an Extensive Diagnostic	08/942,463/6,035,420
Test in Conjunction with a BIOS Test Routine”
“Apparatus for Performing an Extensive	08/942,163/6,009,541
Diagnostic Test in Conjunction with a BIOS Test
Routine”
“Configuration Management Method for Hot	08/941,268/6,148,355
Adding and Hot Replacing Devices”
“Configuration Management System for Hot	08/942,408/6,243,773
Adding and Hot Replacing Devices”
“Apparatus for Interfacing Buses”	08/942,382/6,182,180
“Method for Interfacing Buses”	08/942,413/5,987,554
“Computer Fan Speed Control Device”	08/942,447/5,990,582
“Computer Fan Speed Control Method”	08/942,216/5,962,933
“System for Powering Up and Powering Down a	08/943,076/6,122,746
Server”
“Method of Powering Up and Powering Down a	08/943,077/6,163,849
Server”
“System for Resetting a Server”	08/942,333/6,065,053
“Method of Resetting a Server”	08/942,405/6,330,690
“System for Displaying Flight Recorder”	08/942,070/6,138,250
“Method of Displaying Flight Recorder”	08/942,068/6,073,255
“Synchronous Communication Interface”	08/943,355/6,219,711
“Synchronous Communication Emulation”	08/942,004/6,068,661
“Software System Facilitating the Replacement or	08/942,317/6,134,615
Insertion of Devices in a Computer System”
“Method for Facilitating the Replacement or	08/942,316/6,134,614
Insertion of Devices in a Computer System”
“System Management Graphical User Interface”	08/943,357
“Display of System Information”	08/942,195/6,046,742
“Data Management System Supporting Hot Plug	08/942,129/6,105,089
Operations on a Computer”
“Data Management Method Supporting Hot Plug	08/942,124/6,058,445
Operations on a Computer”
“Alert Configurator and Manager”	08/942,005
“Managing Computer System Alerts”	08/943,356
“Computer Fan Speed Control System”	08/940,301/6,247,898
“Computer Fan Speed Control System Method”	08/941,267
“Black Box Recorder for Information System	08/942,381/6,269,412
Events”
“Method of Recording Information System	08/942,164/6,282,673
Events”
“Method for Automatically Reporting a System	08/942,168/6,243,838
Failure in a Server”
“System for Automatically Reporting a System	08/942,384/6,170,067
Failure in a Server”
“Expansion of PCI Bus Loading Capacity”	08/942,404/6,249,834
“Method for Expanding PCI Bus Loading	08/942,223/6,195,717
Capacity”
“System for Displaying System Status”	08/942,347/6,145,098
“Method of Displaying System Status”	08/942,071/6,088,816
“Fault Tolerant Computer System”	08/942,194/6,175,490
“Method for Hot Swapping of Network	08/943,044/6,324,608
Components”
“A Method for Communicating a Software	08/942,221/6,163,853
Generated Pulse Waveform Between Two Servers
in a Network”
“A System For Communicating a Software	08/942,409/6,272,648
Generated Pulse Waveform Between Two Servers
in a Network”
“Method for Clustering Software Applications”	08/942,318/6,134,673
“System for Clustering Software Applications”	08/942,411/6,363,497
“Method for Automatically Configuring a Server	08/942,319/6,212,585
after Hot Add of a Device”
“System for Automatically Configuring a Server	08/942,331/6,263,387
after Hot Add of a Device”
“Method of Automatically Configuring and	08/942,412/6,154,835
Formatting a Computer System and Installing
Software”
“System for Automatically Configuring and	08/941,955/6,138,179
Formatting a Computer System and Installing
Software”
“Determining Slot Numbers in a Computer”	08/942,462/6,269,417
“System for Detecting Errors in a Network”	08/942,169
“Method of Detecting Errors in a Network”	08/940,302
“System for Detecting Network Errors”	08/942,407/6,105,151
“Method of Detecting Network Errors”	08/942,573

COPYRIGHT RIGHTS

[0004] A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

[0005] 1. Field of the Invention

[0006] The invention relates to communications between two computer systems. More particularly, the invention relates to providing communications between two servers in a server network, for monitoring the operational status of the servers, synchronizing events or actions initiated by the servers, and providing messaging capability between the two servers.

[0007] 2. Description of the Related Technology

[0008] As computer systems and networks become more complex, various systems for promoting fault tolerance in these networks have been developed. One method of preventing network down-time due to the failure or removal of a fileserver from a server network, is to implement “server mirroring.” Server mirroring as it is currently implemented requires a primary server, a primary storage device, a backup server, a backup storage device and a unified operating system linking the two servers and storage devices. The purpose of the backup server is to resume the operations of the primary server should it become inoperational. An example of a mirrored server product is provided by Software Fault Tolerance Level 3 (SFT III) provided by NOVELL INC., 1555 North Technology Way, Orem, Utah, as an add-on to its NetWare 7 4.x product. SFT III maintains servers in an identical state of data update. It separates hardware-related operating system (OS) functions on the mirrored servers so that a fault on one hardware platform does not affect the other.

[0009] The server OS is designed to work in tandem with two servers. One server is designated as a primary server, and the other is a secondary server. The primary server is the main point of update; the secondary server is in a constant state of readiness to take over. Both servers receive all updates through a special link called a mirrored server link (MSL), which is dedicated to this purpose. The servers also communicate over the local area network (LAN) that they share in common, so that one knows if the other has failed even if the MSL has failed. When a failure occurs, the second server automatically takes over without interrupting communications in any user-detectable way. Each server monitors the other server's NetWare 7 Core Protocol (NCP) acknowledgments over the LAN to see that all requests for that server are serviced and that OSs are constantly maintained in a mirrored state.

[0010] When the primary server fails, the secondary server detects the failure and immediately takes over as the primary server. The failure is detected in one or both of two ways: the MSL link generates an error condition when no activity is noticed, or the servers communicate over the LAN, each one monitoring the other's NCP acknowledgment. The primary server is simply the first server of the pair that is brought up. It then becomes the server used at all times and it processes all requests. When the primary server fails, the secondary server is immediately substituted as the primary server with identical configurations. The switch-over is handled entirely at the server end, and work continues without any perceivable interruption.

[0011] Although server mirroring increases security against down-time caused by a failed server, it does so at a considerable cost. This method of providing fault tolerance requires the additional expense and complexity of standby hardware that is not used unless there is a failure in the primary server.

[0012] Another method of providing fault tolerance in a server network which does not require additional redundant (mirrored) hardware is referred to as “clustering” the servers in the network. Under one type of clustering method, a replicated Network Directory Database (NDD) operates in conjunction with server resident processes, running on a cooperating set of servers called a cluster, to remap a network resource to an alternate server, in the event of a primary server failure. A remappable resource is called a clustered resource. The records/objects in the replicated database contain for each clustered network resource, a primary and a secondary server affiliation. Initially, all users access a network resource through the server identified in the replicated database as being the primary server for the network resource. When server resident processes detect a failure of that primary server, the replicated database is updated to reflect the failure of the primary server, and to change the affiliation of that network resource from its primary to its backup server.

[0013] This remapping occurs transparently to whichever user/client is accessing the network resource.

[0014] As a result of the remapping, all users access the clustered network resource through the server identified in the replicated database as the backup server for the resource. When the primary server returns to service, the replicated resident processes detect a return to service of the primary server, the replicated database is again updated to reflect the resumed operation of the primary server. As a result of these latter updates to the replicated database, all users once again access the network resource through the server identified in the replicated database as the primary server for the clustered network resource. This remapping of clustered network resource affiliations also occurs transparently to whichever user/client is accessing the network resource, and returns the resource to its original fault tolerant state. A further discussion of the operation and theory of clustered networks is provided in a U.S. provisional patent application, entitled, “Clustering Of Computer Systems Using Uniform Object Naming And Distributed Software For Locating Objects,” which is listed above under the heading “Priority Claim.”

[0015] The clustering method of remapping the affiliation of a network resource, reduces the amount of hardware, software and processing overhead required to provide fault tolerance, when compared with the mirrored server technique. However, in both of these methods and systems, a rather inefficient and costly method of monitoring the status of each server in the network is utilized. In order to detect that a primary server has failed, for example, these methods require both a primary server and a secondary server to communicate messages and commands across a LAN line and to process received messages and commands in accordance with a specified monitoring protocol.

[0016] One drawback of this method of providing communications between two or more servers within a server network is that it relies on a dedicated communications line, the LAN line, to communicate messages between the servers in the network. The LAN line is a valuable system resource which should be allocated only when necessary. Additionally, communicating across the LAN line is not totally reliable. If the bandwidth capacity of the LAN line is reached, or if the LAN line becomes physically damaged, it will not be able to handle communications from one server to another. Therefore, in order to provide a reliable method of monitoring and/or communicating between servers, a secondary method of communicating in the event that the LAN line becomes disabled is typically required. One such prior art secondary method includes a first server writing data, commands or information to an intermediate hard drive connected to a SCSI bus and a second server which reads the data, commands or information from the hard drive. Therefore, the hard drive serves as an intermediate depository for communicating between the SCSI adapters of two or more servers. One problem with this approach is that it creates a dependency on that device which is often a central point of failure. For example, if the hard drive “crashes,” the two servers will not be able to communicate with each other.

[0017] A typical prior art LAN handshake protocol between two servers includes the following steps: a first adapter of a first server will send a NetWare7 Core Protocol (NCP) packet to a second adapter card of a second server in order to check whether a second server is handling all its requests. The first adapter card must then wait for the second adapter card to receive the NCP signal, process it, and then send a response, which contains the intranetware address of the second adapter card. If the first adapter does not receive the intranetware address data in response to its NCP packet, the first adapter will wait for a specified amount of time after which the handshake protocol “times out” and ends, resulting in a failure to achieve a communications link with the first server.

[0018] This approach is time-consuming and requires much “overhead” in terms of processing time and logic circuitry to process and synchronize the series of commands and data transferred between the adapters of two servers trying to communicate with one another. Therefore, what is needed is a method and system for establishing communications between two or more servers within a server network such that the status of a server may be monitored, events and actions initiated by the servers may be synchronized with one another, and two or more servers may communicate with one another in a cost efficient and reliable manner. Additionally, such a method and system should reduce the amount of required “overhead”, in terms of processing time and system resources.

SUMMARY OF THE INVENTION

[0019] The invention addresses the above and other needs by providing a method and system of communicating between two servers of a server network so as to monitor the status of each server by the other, to time and/or synchronize the events and actions initiated by one server with respect to the other, and further to provide bi-directional messaging capability between the two servers.

[0020] In one embodiment of the invention, a method of monitoring an operational status of a first server with a second server, includes: successively transmitting first and second command signals to a device coupled to the first server, wherein the first command signal places the device in a first status condition and the second command signal places the device in a second status condition; and monitoring a status condition of the device with the second server, coupled to the device, wherein a change in the status condition of the device indicates that the first server is operational.

[0021] In another embodiment, a method of monitoring a status condition of a first server with a second server in a server network, includes: transmitting a software-generated pulse waveform from the first server to a device coupled to the first server, wherein the software-generated pulse waveform comprises a first command corresponding to a logic level low and a second command corresponding to a logic level high; setting the device to a first state during logic level lows of the pulse waveform and to a second state during logic level highs of the pulse waveform; receiving the software-generated pulse waveform with the second server by determining when the device is in the first state and when it is in the second state; and determining when the device no longer changes from the first state to the second state.

[0022] In a further embodiment, a method of monitoring a status condition of a first server by a second server, includes: transmitting SCSI Reserve and Release commands from the server to a SCSI device, coupled to the first server; and monitoring a released/reserved status of the SCSI device with the second server.

[0023] In yet a further embodiment, a method of assigning control over a network resource, includes: transmitting SCSI Reserve and Release commands from a first server to a SCSI device, coupled to the first server; monitoring a released/reserved status of the SCSI device with a second server; determining if the first server is operational; and if it is determined that the first server has failed, assigning control over the SCSI device to the second server.

[0024] In another embodiment, a method of synchronizing a first operation carried out by a first server with a second operation carried out by a second server, includes: ransmitting a software-generated pulse waveform, having a first frequency, from the first server to a device coupled to the first server; receiving the pulse waveform with the second server by monitoring a status condition of the device; transmitting from the first server a synchronization signal to the device by changing the frequency of the pulse waveform to a second frequency; detecting by the second server the synchronization signal by detecting a change in frequency of the pulse waveform; changing at the first server the frequency of the pulse waveform back to the first frequency; detecting by the second server a change in frequency from the second frequency back to the first frequency; and setting in both servers a reference point in time at a beginning of a first cycle of the pulse waveform after it has returned to the first frequency.

[0025] In yet another embodiment, a method of providing communications between a first server and a second server, includes: transmitting a first software-generated pulse waveform from the first server to a first device coupled to the first server, wherein the first pulse waveform changes a status condition of the first device between a first state and a second state; receiving the first software-generated pulse waveform with the second server by sampling the status condition of the first device; frequency modulating the first pulse waveform so as to encode a message into the pulse waveform; and reading the message with the second server by sampling the status condition of the first device at a predetermined first sampling rate.

[0026] In another embodiment, a method of providing communications between a first server and a second server, includes: executing a first pulse transmitter program in the first server so as to transmit a first software-generated pulse waveform from the first server to a first device coupled to the first server, wherein the pulse waveform changes a status condition of the first device between a first state and a second state; executing a first pulse receiver program in the second server so as to receive the first software-generated pulse waveform by sampling the status condition of the first device; frequency modulating the first pulse waveform so as to encode a first message into the first pulse waveform; reading the first message with the second server by sampling the status condition of the first device at a predetermined first sampling rate; executing a second pulse transmitter program in the second server for transmitting a second software-generated pulse waveform from the second server to a second device coupled to the second server, wherein the second pulse waveform changes a status condition of the second device between a third state and a fourth state; executing a second pulse receiver program in the first server for receiving the second software-generated pulse waveform with the first server by sampling the status condition of the second device; frequency modulating the second pulse waveform so as to encode a second message into the second pulse waveform; and reading the second message with the first server by sampling the status condition of the second device at a predetermined second sampling rate.

BRIEF DESCRIPTION OF THE DRAWINGS

[0027] FIG. 1 is a block diagram of a clustered server network having two file servers coupled to a SCSI device in accordance with one embodiment of the invention.

[0028] FIG. 2 illustrates a pulse waveform representing the reserved (logic high) and released (logic low) states of a SCSI device.

[0029] FIG. 3 is flowchart diagram illustrating the steps of one embodiment of a pulse transmitter software program for generating a software-generated pulse waveform in accordance with the invention.

[0030] FIG. 4 illustrates one method of sampling the software-generated pulse waveform by determining if the SCSI device is reserved or released at a predetermined sampling frequency.

[0031] FIG. 5 is a flowchart diagram illustrating the steps of one embodiment of a pulse receiver software program for receiving the software-generated pulse waveform in accordance with the invention.

[0032] FIG. 6 illustrates a pulse waveform being sampled at predetermined reference points, 180 degrees apart on the waveform, for purposes of monitoring the waveform for its presence in accordance with one embodiment of the invention.

[0033] FIG. 7 illustrates a pulse waveform being sampled at predetermined reference points, which are several cycles apart on the waveform, for purposes of monitoring the waveform for its presence in accordance with the invention.

[0034] FIG. 8 is a flowchart diagram illustrating one method of monitoring the pulse waveform in accordance with one embodiment of the invention.

[0035] FIG. 9 illustrates a modulated pulse waveform which may be utilized for the purpose of timing and/or synchronizing two servers with respect to one another in accordance with one embodiment of the invention.

[0036] FIG. 10 is a flowchart diagram illustrating one method of modulating the pulse waveform in order to provide a timing and synchronization signal for two servers in accordance with one embodiment of the invention.

[0037] FIG. 11 illustrates a modulated pulse waveform for providing messaging capability between two servers in accordance with one embodiment of the invention.

[0038] FIG. 12 illustrates a messaging protocol that may be utilized by two servers in accordance with one embodiment of the invention.

[0039] FIGS. 13A-13C together form a flowchart diagram illustrating a messaging protocol between two servers in accordance with one embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

[0040] The invention is described in detail below with reference to the figures, wherein like elements are referenced with like numerals throughout.

[0041] The invention utilizes command signals sent from a SCSI adapter card to a SCSI device in order to reserve and release access time to that device by that server. Referring to FIG. 1, a block diagram of one embodiment of a clustered server network 100 is illustrated. The server network 100 includes a first file server computer 101 having a first SCSI host adapter card 103 coupled thereto. The first adapter card 103 is coupled to a SCSI device 105 for communicating commands and data to and from the SCSI device 105 by means of a first SCSI bus 107. The server network 100 also includes a second file server computer 109 having a second SCSI host adapter card 111 contained therein. The second adapter card 111 is also connected to the SCSI device 105 by means of a second SCSI bus 113. In another embodiment, each of the servers, 101 and 109, may be connected to two or more common SCSI devices, such as SCSI device 105, in order to provide fault tolerance and redundancy in the event that the SCSI device 105 becomes inoperational or otherwise damaged.

[0042] Typically, during normal operating conditions, only one server is allowed access and control of a single SCSI device at any one time. In order to arbitrate access and control over a SCSI device between multiple servers, a second SCSI host protocol is typically used in order to provide this function. In such a protocol, only one server is designated as a host server to the SCSI device and other servers may not access the device when the host server is accessing or desires to access the device. This protocol is accomplished by the SCSI commands of Reserve Unit, Release Unit, and Test Unit Ready, which are transmitted to the SCSI device by the servers connected to that device.

[0043] However, as described above, in a clustered server network, the assignment and control of host and backup status to each of the servers in the network is accomplished by means of a cluster data software program which maps and remaps the affiliation of a particular device to a particular server. Therefore, in a clustered network, the use of the SCSI Reserve and Release commands are not necessary to establish which server is the host server of a particular SCSI device. Therefore, the SCSI command protocol for establishing access rights to a SCSI device are no longer necessary and these command signals are free to be manipulated and utilized for other purposes.

[0044] Embodiments of the invention take advantage of these idle command signals and utilize the Reserve Unit, Release Unit and Test Unit Ready commands in order to communicate from one server to another. The Reserve Unit command and Release Unit command may serve as unique logic levels, while the Test Unit Ready command is used to read and monitor these “logic levels.” By manipulating the Reserve and Release commands a “software generated pulse waveform” may be created to communicate messages from one server to another.

[0045] In order to generate this software-generated pulse waveform, at least the host server is encoded with a “Pulse Transmitter” software program (hereinafter “pulse transmitter” or “pulse transmitter module”) which generates the Reserve and Release signals, or commands, and transmits them to a SCSI device. The processing time and circuitry overhead to create this pulse waveform is nominal. As used herein, the term “module” refers to any software program, subprogram, subroutine of a program, or software code capable of performing a specified function. Also, as used herein, the terms “command,”“signal” and “data” and any conjugations and combinations thereof, are used synonymously and interchangeably and refer to any information or value that may be transmitted, received or communicated between two electronic systems.

[0046] To further illustrate the concept of creating a software-generated pulse waveform, reference is made to FIG. 2. In this figure, the Reserve command is represented as a logic level high and the Release command is represented as a logic level low. However, it should be kept in mind that this is only a convenient way of “labelling” these commands for the purpose of using them as a signalling tool. These commands in actuality are streams of data which are transmitted to a SCSI device for the purpose of reserving or releasing access to the device. As shown in FIG. 2, the time that the device is reserved is represented by a logic level high beginning at a rising edge 201 and ending at a falling edge 203. The period of time between the rising and falling edges 201 and 203, respectively, is referred to as the “Reservation time” (Rvt). The time that the device is released is represented by a logic level low beginning at the falling edge 203 and ending at a rising edge 205. The period of time between the falling and rising edges 203 and 205, respectively, is referred to as the “Release time” (Rlt). For the purpose of providing a signal that a host server 101, is “alive” and operational, the pulse waveform may be uniform, that is Rvt=Rlt. However, it is not required that it be uniform. For example, Rvt may equal ½×Rlt. Furthermore, as described in further detail below, for the purpose of providing timing and synchronization signals, and messaging capability, this pulse waveform may be frequency modulated, for example, in order to provide messages, commands, timing reference points, etc.

[0047] In order to transmit this pulse waveform to the SCSI device, the pulse transmitter software code makes a call to a specified SCSI driver program contained within a hard drive that is currently loaded in memory and executed on the host server 101. The SCSI driver then utilizes the SCSI adapter card 103, otherwise known as the SCSI initiator or SCSI board, to send either a Reserve or Release command to the SCSI device.

[0048] Referring to FIG. 3, a flowchart diagram of one embodiment of the software code for transmitting a software pulse waveform to a SCSI device is illustrated. The process begins at start 300 and proceeds to step 301 in which the pulse transmitter sends a Reserve command to the device. In step 303, the pulse transmitter will wait until a prespecified amount of reservation time (Rlt) has elapsed. In step 305, the pulse transmitter determines whether to continue pulse generation. If in step 305 it is determined to discontinue pulse generation, the process moves to step 307 where it ends. On the otherhand, if in step 305 it is determined that the pulse transmitter is to continue pulse generation, in step 309, it will send a Release command to the device. In step 311, the pulse transmitter will then wait until a prespecified period of release time (Rlt) has elapsed. In step 313, the pulse transmitter once again determines whether to continue pulse generation. If the answer is no, the process goes to step 307 where it ends. If the answer is yes, the process loops back to step 301 so that the above steps may be repeated.

[0049] In order to communicate between the host server 101 and the secondary, or backup, server 109, a “Pulse Receiver” program (hereinafter “pulse receiver” or “pulse receiver module”) within the backup server 109 may listen to the pulse generated by the pulse transmitter of the host server. Similar to the pulse transmitter within the host server 101, the pulse receiver is a software program stored within a memory of the backup server 109 and executed by the backup server 109. To detect the state of the pulse, the pulse receiver may send a “Test Unit Ready” command to the device 105 (FIG. 1). Upon receiving the Test command, the device 105 may indicate whether it is reserved, indicating a failed test, or released, indicating a successful test by transmitting back to the pulse receiver, response data which contains information pertaining to its reserved/released status. The rate at which the “Test Unit Ready” command is transmitted to the SCSI device 105, otherwise known as the sample rate herein, is typically much faster than the rate at which the pulse waveform changes state. Therefore, the “Test Unit Ready” command in a sense “samples” the reservation time period (Rvt) and the release time period (Rlt) in order to ascertain the shape and frequency of the software pulse waveform.

[0050] Referring to FIG. 4, a graphical representation of the Test Unit Ready command sampling protocol is illustrated. The results of the Test Unit Ready command are indicated by either an “S” or a “F”, wherein S indicates a successful test when the device 105 is released by the host server 101 and F indicates a failed test when the device 105 is reserved by the host server 101. As shown in FIG. 4, the released status is represented as a logic level low at elements 401 and 403 of the software pulse waveform 400 and the reserved status is represented as logic level highs at elements 405 and 407 of the software pulse waveform 400. Above the pulse waveform 400, the results of the “Test Unit Ready” command are indicated by S and F, wherein S (successful test) corresponds to the released status and F (failed test) corresponds to the reserved status. It should be noted that since a logic level high was arbitrarily selected as representing the reserved status and the logic level low was arbitrarily selected as representing the released status, these representations can be switched and still provide the signalling functionality as described above in accordance with the invention.

[0051] FIG. 5 illustrates a flowchart diagram of one embodiment of a pulse receiving process in accordance with the invention. The process starts at 500 and proceeds to step 501 wherein the secondary server 109 (FIG. 1) sends a Test Unit Ready command to the SCSI device 107 (FIG. 1) in response to which the device 107 will transmit data back to the secondary server 109. In step 503, the secondary server 109 determines whether the device 107 is ready to accept a SCSI command by processing the response data received by the device 107. If the result of the Test Unit Ready command is a success, the process moves to step 505 where the secondary server 109 records that the status of the device 107 is released, reflecting a “S” in the software generated pulse waveform as shown in FIG. 4. If the result of the Test Unit Ready command is a failure, the process moves to step 507 where the secondary server 109 records that the status of the device 107 is reserved, reflecting a “F” in the software generated pulse waveform as shown in FIG. 4. In step 509, the secondary server 109 waits until the next sample of the pulse waveform is to be taken. In step 511, a determination is made as to whether to continue taking samples. If the answer is Yes, the process goes back to step 501 and the above process steps are repeated. If the answer is No, the process ends at step 513.

[0052] The foregoing describes one embodiment of a process for transmitting a software-generated pulse waveform by a first server 101 and receiving the software-generated pulse waveform by a second server 109, in accordance with the invention. Some useful applications of the software-generated pulse waveform are described below.

Pulse Waveform as “Heartbeat” of Primary Server

[0053] The pulse waveform can be monitored by a secondary server to determine if a primary server is present and operational. The primary server can send a pulse waveform to the secondary server as described above in order to tell the secondary server that it is “alive and well.” In this way, the pulse waveform serves as a kind of “heartbeat” of the first server which the second server listens for. If the pulse transmitter sends a constant pulse, the waveform can be determined and predicted. This does not mean that the reservation time Rvt must be equal to the release time Rlt, but rather all Rvt's are predictable and all Rlt's are predictable. A pulse with a smaller Rvt minimizes the amount of time a device is reserved, while still creating a heartbeat.

[0054] In order to determine the shape, or period, of the pulse waveform, the second server sends a Test Unit Ready command to a SCSI device in order to sample the waveform as described above. The second server can ascertain the cyclic period of the pulse waveform by noting the transition points (from S to F or F to S) of the waveform and recording the number of samples taken between the transition points after several successive cycles of the waveform. Once the waveform is known, there is no need to keep sampling the waveform at the previous sampling rate in order to monitor the presence of the waveform. Instead, samples can be taken out of phase from the transition points and less frequently based on the known period of the waveform in order to ascertain its presence. By taking samples less frequently, the processing time and circuitry overhead of this communication and monitoring method is significantly reduced. This concept is described in greater detail below with reference to FIGS. 6 and 7.

[0055] Referring to FIG. 6, a software-generated pulse waveform is shown. After the second server has determined the period of the waveform 600, it does not need to sample the waveform at the sampling rate. Instead the second server samples the waveform at a first reference point 601 and at a second reference point 603 approximately 1801 out of phase from the first reference point 601. Because the second server has previously recorded the shape and period of the waveform, it sends a Test Unit Ready command to the SCSI device at a time corresponding to the reference point 601 and expects to see a “S” (a successful test result indicating a Released status). Similarly, at reference point 603, it expects to see a “F” (a failed test result indicating a Reserved status). It is appreciated that the reduced number of Test Unit Ready commands that must be transmitted to the SCSI device and the reduced number of results that must be subsequently processed significantly reduces processing time and other system resources that must be allocated to perform this function.

[0056] To further decrease the overhead of monitoring the pulse waveform, samples can be taken several cycles apart on the pulse waveform as shown in FIG. 7. FIG. 7 illustrates a pulse waveform 700, wherein the second server samples the waveform 700 at a first reference point 701 where it expects to see a release state. After several cycles of the waveform, the second server samples the waveform 700 at a second reference point 703 where it expects to see a reserve state.

[0057] By monitoring the pulse waveform as described above, the operational status of the first server can be determined by the second server. The first server is considered operational if the expected results of the monitoring process are obtained. However, if the results indicate a constant released state, either the monitoring mechanism (the reference points) are out of synchronization or the first server is dead and the heartbeat has flatlined. Going out of synchronization is possible, but not common. Therefore, in one embodiment, the monitoring process of the invention checks for this possibility by “recalibrating” the pulse receiving process. This is done by repeating the sampling process as described above with respect to FIGS. 4 and 5. In this way, the presence of the pulse can be reverified. Once the shape and cyclic period of the pulse waveform generated by the first server has been redetermined, the second server can once again begin monitoring the waveform at the recalibrated reference points. However, if the pulse waveform is no longer present, it is determined that the first server is dead. In a clustered system, the second server can send a command to the Network Directory Database (NDD) to inform the NDD that it is assuming control over the resources previously handled by the first server. FIG. 8 illustrates a flowchart diagram of one embodiment of the process of monitoring the “heartbeat” of the first server. The process starts at 800 and proceeds to step 801, where the first server executes the pulse transmitter by sending Reserve and Release commands to the SCSI device. In step 803, the second server executes the pulse receiver by sending Test Unit Ready commands to the SCSI device, until at least one full cycle of the pulse waveform has been sampled. In step 805, the second server determines the reference points at which the pulse waveform is to be subsequently sampled in order to monitor its presence. In step 807, the second server waits until the next reference point of the waveform is to be sampled. In step 809, the second server samples the waveform at the reference point and determines whether the expect result was obtained. If the expected result is obtained, the process moves to step 811 wherein the second server determines whether to continue monitoring the first server. If the answer is Yes, the process moves back to step 807 and proceeds once again from this step. If the answer is No, the process ends at step 817.

[0058] If in step 809, the expected results are not obtained, the process moves to step 813 in which the pulse waveform, or “heartbeat” is recalibrated as described above. In step 815, the second server determines whether the heartbeat has flatlined, i.e., whether the pulse waveform is still present. If it is determined that the heartbeat is still there, the process moves back to step 807 and once again proceeds from there. However, if in step 815 it is determined that the heartbeat has flatlined, the first server is deemed dead, and the process ends at step 817.

Pulse Waveform as Clock

[0059] Another use of the pulse generator is to provide a clock which may be used to synchronize time and events carried out by two or more servers. FIG. 9 illustrates one method of using the pulse waveform as a synchronizing mechanism. Based on the heartbeat design, a pulse waveform 900 is generated by a first server which acts as a time master. A second server acts as a time slave and runs the pulse receiver program as described above with respect to FIG. 5 to sample the pulse waveform. Similar in concept to a radio station sounding a bell to synchronize time, the time master will disrupt its usual pulse waveform and send a synchronization signal. In FIG. 9, this synchronization signal is indicated by a change in frequency starting at element 901 of the pulse waveform 900. The change in frequency may generate a pulse waveform at half the original frequency, for example. At element 903, the slave server, expecting to see a logic level high but seeing a logic level low instead, recognizes the change in frequency and restarts sampling of the pulse waveform. At element 905 of the waveform 900, the slave server knows the frequency of the synchronization signal. At element 907, the master server returns to normal frequency. The slave recognizes the change in frequency at element 909 when it expects to see a low level but instead sees a high level. The slave then marks the beginning of that cycle as “Time 0”. The beginning of each cycle thereafter is successively numbered as T1, T2, etc. Therefore, both the master and slave servers now have a common reference point in time, T0, which can be used to synchronize processes and events occurring in the two servers.

[0060] FIG. 10 shows a flowchart of one embodiment of the process of synchronizing two servers in accordance with the invention. The process starts at step 1000 and proceeds to step 1010 where the first server (the time master) runs the pulse transmitter program. In step 1020, the second server (the time slave) runs the pulse receiver program in order to sample and record the pulse waveform generated and transmitted by the time master. This sampling is performed at a sampling rate which is much faster than the frequency of the pulse waveform. In step 1030, the master sends a synchronization signal by changing the frequency of the pulse waveform to one half its original frequency, for example. In step 1040, the slave detects the synchronization signal. In step 1050, the master returns to the normal frequency of the original pulse waveform. In step 1060, the slave detects the change back to the original frequency and marks the beginning of the first cycle of the reinstated original frequency as “Time 0”. In step 1070, the second server determines if the perceived change in frequency of the pulse waveform is due to a flatline condition of the pulse waveform. If in step 1070, it is determined that the pulse waveform has not flatlined, the process moves to step 1080 and the master and slave servers update their time counters and set time T0 as a common reference point in time for synchronization purposes. The process then moves back to step 1070 and checks whether the pulse waveform has flatlined. Each time it is determined that the pulse waveform is still present, the master and slave servers increment, i.e., update, their timers by one. However, if in step 1070, it is determined that the pulse waveform has flatlined, the process ends as step 1090 and synchronization has failed.

Pulse Waveform as Messaging Device

[0061] In the embodiment described above, the communication between the two servers is unidirectional (from master to slave) and the slave does not acknowledge synchronization with the master. A bidirectional clock can be implemented as an enhancement to the above timing mechanism in which the slave can acknowledge the detection of Time 0 so that the master receives validation of synchronization. In a bidirectional clock system, both servers run both the pulse transmitter and the pulse receiver programs. Also, a second SCSI device to which the second server is the host server must be provided in order to implement bidirectional communications between the first and second servers. With this arrangement, the second server “owns” the second SCSI device and transmits Reserve and Release commands to the second SCSI device and the first server samples and monitors the status of the second SCSI device as described above.

[0062] With a bidirectional communication protocol as described above, the invention may also be utilized to provide not only timing and synchronization between two servers but also messaging between the two servers. Since the pulse waveform can be bi-directional and there are no restrictions on the waveform, a messaging protocol can be established between the two servers via the SCSI bus using frequency modulation. A simple Request/Acknowledge protocol, with session control (the ability for both sides to initiate communication) may be used.

[0063] Referring to FIG. 11, one embodiment of a bi-directional pulse waveform message signal is illustrated. A message is incorporated into the pulse waveform by modulating the duration or pulse width of the Reserved state (indicated by a logic level high) of the waveform. As shown in FIG. 11, a “R” is indicated at element 1101, a “T” is indicated at element 1103 and a “S” is indicated at element 1105. A group of Rvt values, each separated by a constant Rlt make up a command or message. The message shown in FIG. 11 is the “RTS” signal which is a request to send a command to the other server (begin communication session). This command signal as well as others is described in further detail below with respect to FIG. 12. When no communication is occurring, a uniform Rvt=Rlt pulse is sent.

[0064] As mentioned above, to accommodate a bidirectional communication mechanism, both file servers must run the pulse transmitter and pulse receiver programs, and both servers must each “own” one device to which it can transmit Release and Reserve commands while the other server samples the status of that device at the sample rate. FIG. 12 illustrates one example of a possible communication protocol between two file servers. A second server 109 first sends a Request to Send (RTS) command to the first server 101 The first server 101 then responds with a Ready to Receive (RTR) signal which establishes communications between the two servers. Next, the second server 109 sends a Request (REQ) signal to the first server 101. The first server 101 then sends back either an Acknowledge (ACK) signal or Not Acknowledge (NAK) signal which indicates that the first server 101 can or cannot process the second server's request. After receiving a NAK signal, the second server 109 will terminate communications by sending a Relinquish (REL) to the first server 101. If an acknowledge (ACK) signal is sent back, the first server 101 will process the request signal from the second server 109 and send a Result (RES) signal to the second server 109 after which the second server terminates communications by sending a Relinquish (REL) signal to the first server 101.

[0065] The following is a summary of the messages/commands discussed above:

[0066] RTS: Request to send a command to the other file server (begin communication session).

[0067] RTR: Ready to receive-other server agrees to accept a command.

[0068] REQ: The command requesting certain actions/data on the part of the receiving server (defined by application).

[0069] ACK: The other server acknowledges the arrival and ability to service the command.

[0070] NAK: The other server does not support that command.

[0071] RES: The results of the command.

[0072] REL: The initiating server relinquishes control (end of session).

[0073] Referring to FIGS. 13A-13C a flowchart diagram of one embodiment of a bi-directional communication protocol in accordance with the invention is illustrated. The process starts at 1300 and proceeds to step 1301 wherein both servers start running the pulse transmitter program to generate a uniform pulse waveform wherein Rvt=Rlt. In step 1303, both servers initiate the pulse receiver program to continuously sample the pulse waveform generated by the other server. As used herein the term “continuous sampling” means that the pulse receiver is sampling the pulse waveform at every “tick” or cycle of the sampling frequency, which is greater than the frequency of the pulse waveform, in order to determine the shape and frequency of the waveform, rather than sampling at only select reference points of the waveform for monitoring purposes.

[0074] In order to the simplify the discussion, the following description of the remaining portions of the flowchart is provided from the perspective of only one of the two servers, the first server. However, it is understood that the roles of the first and second servers are interchangeable in the following discussion. In step 1305, the first server determines whether it has a message to send to the second server. If the first server does not have a message queued to send to the second server, the process moves to step 1307 wherein the first server determines whether a Request to Send (RTS) command has been sent by the second server. If the first server has not received a RTS signal from the second server, the process returns to step 1305, wherein the first server continues to poll itself as to whether it has a message to send to the second server. If in step 1307, it is determined that the second server has sent a RTS signal to the first server, the process moves to step 1309 as shown in FIG. 13B. In step 1309, the first server sends back a Ready to Receive (RTR) signal to the second server, agreeing to accept a command from the second server. Thereafter, in step 1311, the first server receives the request (command) from the second server and decodes the request. In step 1313, the first server determines whether it can support or accommodate the request from the second server. If it is determined that the first server can support the request, in step 1315, the first server sends an acknowledgement (ACK) signal to the second server. In step 1317, the first server passes the request up to an application software program running on the first server to process the request. In step 1319, the first server sends the results of the application program to the second server. In step 1321, the first server waits for a relinquish (REL) signal from the second server which terminates communications between the two servers and sends the process back to step 1305 of FIG. 13A at which point the first server once again resumes polling whether it has a message to send to the second server.

[0075] If in step 1313, the first server determines that it does not support the request sent by the second server, in step 1323, the first server sends a Not Acknowledge (NAK) signal to the second server which informs the second server that the first server does not support that command. The process then moves back to step 1305 wherein the first server continues to poll itself as to whether it has a message to send to the second server.

[0076] If in step 1305, the first server determines that it has a message queued to be sent to the second server, the process moves to step 1325 of FIG. 13C. In step 1325, the first server sends a Request to Send (RTS) signal to the second server which requests the second server to accept a command from the first server. In step 1327, the first server will wait for a Ready to Receive (RTR) from the second server. In step 1329, the first server determines if a timeout period has expired. If the timeout period has expired before a RTR signal is received from the second server, the process moves to step 1331 in which the first server passes an error message to application software indicating that the second server is not responding. The process then moves back to step 1305 of FIG. 13A.

[0077] If in step 1329, the first server receives a RTR signal from the second server before the timeout period expires, the process moves to step 1333 in which the first server will send a request, or command, to the second server. In step 1335, the first server determines whether an acknowledge (ACK) signal has been returned by the second server. If the second server does not send an ACK signal or, instead, sends back a Not Acknowledge (NAK) signal, the process moves back to step 1331 in which the first server sends an error signal to the application software indicating that the second server does not support the request. However, if in step 1335, the first server receives the ACK signal from the second server, the process moves to step 1337 in which the first server receives the response (RES) signal(s) from the second server and passes the response to application software for processing. Thereafter, in step 1339, the first server sends a relinquish (REL) signal to the second server thereby terminating communications with the second server. The process then moves back to step 1305 wherein the first server determines whether it has a message to send. If not, in step 1307, the first server determines if the second server wants to send it a message. This process may be recursive and continue to execute until it is terminated by each of the servers.

[0078] As described above, the invention provides an efficient and reliable method and system for communicating between two servers in a server network. Because the communication method and system does not transmit data to be stored in an intermediate device, such as a hard disk drive, it does not depend on the presence or operational status of such a device. Rather, some embodiments of the invention take advantage of an existing protocol for establishing control of a SCSI device, namely, the Reserve and Release commands sent by a host server to a SCSI device. By sampling and monitoring the Reserve and Release status of the SCSI device by a second server which is also coupled to the device, the second device can monitor the presence and operational status of the host server, without directly communicating to the host server via an intermediate disk drive as is done in prior art systems. The Reserve and Release status of the SCSI device is used to generate a software-generated pulse waveform which serves as a sort of “heartbeat” of the host server and which can be monitored by the second server. Because the Reserve and Release commands are already implemented in existing SCSI device protocols, the method and system of the invention, once established, requires very little overhead, in terms of processing time and system resources, and is inexpensive to implement.

[0079] Because there are no limitations as to the shape and frequency of the software generated pulse waveform, the waveform may be frequency modulated in order to provide timing and synchronization signals to two servers. Additionally, by implementing each server as both a sender of Reserve and Release commands to a respective SCSI device, and a monitor of a the respective SCSI device, bidirectional communications can be established between the two servers. This method and system of communication between two servers is further advantageous in that it may be implemented with existing resources and command protocols between a server and a SCSI device and, additionally, it can be turned on and off as desired.

[0080] The invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims, rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

What is claimed is:

1. A method of assigning control over a network resource, comprising:

transmitting SCSI Reserve and Release commands from a first server to a SCSI device, coupled to the first server;

monitoring a released/reserved status of the SCSI device with a second server;

determining if the first server is operational; and

if it is determined that the first server has failed, assigning control over the SCSI device to the second server.

2. The method of claim 1 wherein the step of assigning control over the SCSI device to the second server comprises notifying a Network Directory Database that the first server has failed and that the second server is now the host server to the SCSI device.

3. The method of claim 1 wherein a change in the released/reserved status of the SCSI device indicates that the first server remains operational and a constant reserved status of the SCSI device indicates that the first server has failed.

4. A method of synchronizing a first operation carried out by a first server with a second operation carried out by a second server, comprising:

transmitting a software-generated pulse waveform, having a first frequency, from the first server to a device coupled to the first server;

receiving the pulse waveform with the second server by monitoring a status condition of the device;

transmitting from the first server a synchronization signal to the device by changing the frequency of the pulse waveform to a second frequency;

detecting by the second server the synchronization signal by detecting a change in frequency of the pulse waveform;

changing at the first server the frequency of the pulse waveform back to the first frequency;

detecting by the second server a change in frequency from the second frequency back to the first frequency; and

setting in both servers a reference point in time at a beginning of a first cycle of the pulse waveform after it has returned to the first frequency.

5. The method of claim 4 wherein:

the pulse waveform is uniform when it is at the first frequency such that a first period of time corresponding to a logic level high of the pulse waveform is equal to a second period of time corresponding to a logic level low of the pulse waveform;

the act of changing the frequency of the pulse waveform comprises changing at least one of the first and second periods of time; and

the act of receiving the software-generated pulse waveform with the second server comprises sampling the status condition of the device at a predetermined sampling rate, wherein the logic level high of the pulse waveform sets a status condition of the device to a first state and the logic level low of the pulse waveform sets the status condition of the device to a second state.

6. The method of claim 5 wherein:

the logic level high of the pulse waveform is represented by a SCSI Reserve command which reserves access to the device exclusively to the first server;

the logic level low of the pulse waveform is represented by a SCSI Release command which releases the device from exclusive access by the first server; and

the act of sampling the status condition of the device comprises:

repetitively transmitting a SCSI Test command from the second server to the device at the sampling rate; and

receiving a response signal for each Test command which indicates the status condition of the device.

7. A method of synchronizing a first operation carried out by a first server with a second operation carried out by a second server, comprising:

transmitting a software-generated pulse waveform from the first server to a device coupled to the first server, wherein the pulse waveform is uniform such that a first period of time corresponding to a logic level high of the pulse waveform is equal to a second period of time corresponding to a logic level low of the pulse waveform, and wherein the logic level high of the pulse waveform sets a status condition of the device to a first state and the logic level low of the pulse waveform sets the status condition of the device to a second state;

receiving the software-generated pulse waveform with the second server by sampling the status condition of the device;

transmitting a synchronization signal from the first server to the device by frequency modulating the software-generated pulse waveform so as to vary at least one of the first and second periods;

receiving the synchronization signal with the second server by detecting a change in frequency of the pulse waveform; and

resuming transmission of the uniform pulse waveform to the device, wherein the second server detects the resumption in frequency and marks a beginning of a first cycle of the uniform pulse waveform, after the synchronization signal, as a reference point in time, and the first server also marks the beginning of the first cycle of the uniform pulse waveform as a reference point in time.

8. A method of synchronizing a first operation performed by a first server with a second operation performed by a second server, comprising:

executing a pulse transmitter program in the first server, said program successively transmitting SCSI Reserve and Release commands from the first server to a SCSI device so as to place the SCSI device in successive states of reserved and released status, wherein the states of the SCSI device serve as a basis for a software-generated pulse waveform;

executing a pulse receiver program in the second server, said program sampling the software-generated pulse waveform at a predetermined sampling rate;

determining when the pulse waveform has changed from a first frequency to a second frequency; and

determining when the pulse waveform has changed from the second frequency back to the first frequency, wherein the first and second server each record a beginning of a first cycle of the pulse waveform after it has changed from the second frequency back to the first frequency as a common reference point in time.

9. A method of providing communications between a first server and a second server, comprising:

transmitting a first software-generated pulse waveform from the first server to a first device coupled to the first server, wherein the first pulse waveform changes a status condition of the first device between a first state and a second state;

receiving the first software-generated pulse waveform with the second server by sampling the status condition of the first device;

frequency modulating the first pulse waveform so as to encode a message into the pulse waveform; and

reading the message with the second server by sampling the status condition of the first device at a predetermined first sampling rate.

10. The method of claim 9 wherein when the first server is not sending a message to the second server, the first pulse waveform is uniform such that a first period of time corresponding to a logic level high of the first pulse waveform is equal to a second period of time corresponding to a logic level low of the first pulse waveform, and wherein the logic level high of the pulse waveform sets a status condition of the first device to a first state and the logic level low of the first pulse waveform sets the status condition of the first device to a second state.

11. The method of claim 10 wherein:

the act of receiving the first pulse waveform comprises sending a SCSI Test command to the first device at the first sampling rate and receiving a response from the first device as to its status condition;

the logic level high of the first pulse waveform is represented by a SCSI Reserve command;

the logic level low of the first pulse waveform is represented by a SCSI Release command;

the first device is a first SCSI device;

the first state is a reserved status condition; and

the second state is a released status condition.

12. The method of claim 11 further comprising:

transmitting a second software-generated pulse waveform from the second server to a second device coupled to the second server, wherein the second pulse waveform changes a status condition of the second device between a third state and a fourth state;

receiving the second software-generated pulse waveform with the first server by sampling the status condition of the second device;

frequency modulating the second pulse waveform so as to encode a second message into the second pulse waveform; and

reading the message with the first server by sampling the status condition of the second device at a predetermined second sampling rate.

13. The method of claim 12 wherein when the second server is not sending a message to the first server, the second pulse waveform is uniform such that a third period of time corresponding to a logic level high of the second pulse waveform is equal to a fourth period of time corresponding to a logic level low of the second pulse waveform, and wherein the logic level high of the second pulse waveform sets the status condition of the second device to the third state and the logic level low of the second pulse waveform sets the status condition of the second device to the fourth state.

14. The method of claim 13 wherein:

the logic level high of the first pulse waveform is represented by a SCSI Reserve command;

the logic level low of the first pulse waveform is represented by a SCSI Release command;

the first device is a first SCSI device;

the first state is a reserved status condition;

the second state is a released status condition;

the act of receiving the second pulse waveform comprises sending a SCSI Test command from the first server to the second device at the second sampling rate and receiving a response from the second SCSI device as to its status condition,

the logic level high of the second pulse waveform is represented by a second SCSI Reserve command;

the logic level low of the second pulse waveform is represented by a second SCSI Release command;

the second device is a second SCSI device;

the third state is a reserved status condition; and

the fourth state is a released status condition.

15. The method of claim 9 further comprising:

receiving the second software-generated pulse waveform with the first server by sampling the status condition of the second device;

frequency modulating the second pulse waveform so as to encode a second message into the second pulse waveform; and

reading the message with the first server by sampling the status condition of the second device at a predetermined second sampling rate.

16. A method of providing communications between a first server and a second server, comprising:

executing a first pulse transmitter program in the first server so as to transmit a first software-generated pulse waveform from the first server to a first device coupled to the first server, wherein the pulse waveform changes a status condition of the first device between a first state and a second state;

executing a first pulse receiver program in the second server so as to receive the first software-generated pulse waveform by sampling the status condition of the first device;

frequency modulating the first pulse waveform so as to encode a first message into the first pulse waveform;

reading the first message with the second server by sampling the status condition of the first device at a predetermined first sampling rate;

executing a second pulse transmitter program in the second server for transmitting a second software-generated pulse waveform from the second server to a second device coupled to the second server, wherein the second pulse waveform changes a status condition of the second device between a third state and a fourth state;

executing a second pulse receiver program in the first server for receiving the second software-generated pulse waveform with the first server by sampling the status condition of the second device;

frequency modulating the second pulse waveform so as to encode a second message into the second pulse waveform; and

reading the second message with the first server by sampling the status condition of the second device at a predetermined second sampling rate.

17. The method of claim 16 wherein:

when the first server is not sending the first message to the second server, the first pulse waveform is uniform such that a first period of time corresponding to a logic level high of the first pulse waveform is equal to a second period of time corresponding to a logic level low of the first pulse waveform, and wherein the logic level high of the pulse waveform sets a status condition of the first device to a first state and the logic level low of the first pulse waveform sets the status condition of the first device to a second state; and

when the second server is not sending the second message to the first server, the second pulse waveform is uniform such that a third period of time corresponding to a logic level high of the second pulse waveform is equal to a fourth period of time corresponding to a logic level low of the second pulse waveform, and wherein the logic level high of the second pulse waveform sets the status condition of the second device to the third state and the logic level low of the second pulse waveform sets the status condition of the second device to the fourth state.

18. The method of claim 17 wherein:

the logic level high of the first pulse waveform is represented by a first SCSI Reserve command;

the logic level low of the first pulse waveform is represented by a first SCSI Release command;

the first device is a first SCSI device;

the first state is a reserved status condition;

the second state is a released status condition;

the logic level high of the second pulse waveform is represented by a second SCSI Reserve command;

the logic level low of the second pulse waveform is represented by a second SCSI Release command;

the second device is a second SCSI device;

the third state is a reserved status condition; and

the fourth state is a released status condition.

Patent Citations (292)

Patent	Date	Inventor	Cited By
US4057847(A)	1977-11-01	Lowell et al.	Applicant
US4100597(A)	1978-07-01	Fleming et al.	Applicant
US4449182(A)	1984-05-01	Rubinson et al.	Applicant
US4672535(A)	1987-06-01	Katzman et al.	Applicant
US4692918(A)	1987-09-01	Elliott et al.	Applicant
US4695946(A)	1987-09-01	Andreasen et al.	Applicant
US4707803(A)	1987-11-01	Anthony, Jr. et al.	Applicant
US4769764(A)	1988-09-01	Levanon	Applicant
US4774502(A)	1988-09-01	Kimura	Applicant
US4821180(A)	1989-04-01	Gerety et al.	Applicant
US4835737(A)	1989-05-01	Herrig et al.	Applicant
US4894792(A)	1990-01-01	Mitchell et al.	Applicant
US4949245(A)	1990-08-01	Martin et al.	Applicant
US4999787(A)	1991-03-01	McNally et al.	Applicant
US5006961(A)	1991-04-01	Monico	Applicant
US5007431(A)	1991-04-01	Donehoo, III	Applicant
US5033048(A)	1991-07-01	Pierce et al.	Applicant
US5051720(A)	1991-09-01	Kittirutsunetorn	Applicant
US5073932(A)	1991-12-01	Yossifor et al.	Applicant
US5103391(A)	1992-04-01	Barrett	Applicant
US5118970(A)	1992-06-01	Olson et al.	Applicant
US5121500(A)	1992-06-01	Arlington et al.	Applicant
US5136708(A)	1992-08-01	Lapourtre et al.	Applicant
US5138619(A)	1992-08-01	Fasang et al.	Applicant
US5157663(A)	1992-10-01	Major et al.	Applicant
US5210855(A)	1993-05-01	Bartol	Applicant
US5245615(A)	1993-09-01	Treu	Applicant
US5247683(A)	1993-09-01	Holmes et al.	Applicant
US5253348(A)	1993-10-01	Scalise	Applicant
US5265098(A)	1993-11-01	Mattson et al.	Applicant
US5266838(A)	1993-11-01	Gerner	Applicant
US5269011(A)	1993-12-01	Yanai et al.	Applicant
US5272382(A)	1993-12-01	Heald et al.	Applicant
US5272584(A)	1993-12-01	Austruy et al.	Applicant
US5276863(A)	1994-01-01	Heider	Applicant
US5277615(A)	1994-01-01	Hastings et al.	Applicant
US5280621(A)	1994-01-01	Barnes et al.	Applicant
US5283905(A)	1994-02-01	Saadeh et al.	Applicant
US5307354(A)	1994-04-01	Cramer et al.	Applicant
US5311397(A)	1994-05-01	Harshberger et al.	Applicant
US5311451(A)	1994-05-01	Barrett	Applicant
US5317693(A)	1994-05-01	Cuenod et al.	Applicant
US5329625(A)	1994-07-01	Kannan et al.	Applicant
US5337413(A)	1994-08-01	Lui et al.	Applicant
US5351276(A)	1994-09-01	Doll, Jr. et al.	Applicant
US5367670(A)	1994-11-01	Ward et al.	Applicant
US5379184(A)	1995-01-01	Barraza et al.	Applicant
US5386567(A)	1995-01-01	Lien et al.	Applicant
US5388267(A)	1995-02-01	Chan et al.	Applicant
US5402431(A)	1995-03-01	Saadeh et al.	Applicant
US5404494(A)	1995-04-01	Garney	Applicant
US5423025(A)	1995-06-01	Goldman et al.	Applicant
US5430717(A)	1995-07-01	Fowler et al.	Applicant
US5430845(A)	1995-07-01	Rimmer et al.	Applicant
US5432715(A)	1995-07-01	Shigematsu et al.	Applicant
US5432946(A)	1995-07-01	Allard et al.	Applicant
US5438678(A)	1995-08-01	Smith	Applicant
US5440748(A)	1995-08-01	Sekine et al.	Applicant
US5448723(A)	1995-09-01	Rowett	Applicant
US5455933(A)	1995-10-01	Schieve et al.	Applicant
US5460441(A)	1995-10-01	Hastings et al.	Applicant
US5463766(A)	1995-10-01	Schieve et al.	Applicant
US5471617(A)	1995-11-01	Farrand et al.	Applicant
US5471634(A)	1995-11-01	Giorgio et al.	Applicant
US5473499(A)	1995-12-01	Weir	Applicant
US5483419(A)	1996-01-01	Kaczeus, Sr. et al.	Applicant
US5485550(A)	1996-01-01	Dalton	Applicant
US5487148(A)	1996-01-01	Komori et al.	Applicant
US5491791(A)	1996-02-01	Glowny et al.	Applicant
US5493574(A)	1996-02-01	McKinley	Applicant
US5493666(A)	1996-02-01	Fitch	Applicant
US5513314(A)	1996-04-01	Kandasamy et al.	Applicant
US5513339(A)	1996-04-01	Agrawal et al.	Applicant
US5517646(A)	1996-05-01	Piccirillo et al.	Applicant
US5526289(A)	1996-06-01	Dinh et al.	Applicant
US5528409(A)	1996-06-01	Cucci et al.	Applicant
US5530810(A)	1996-06-01	Bowman	Applicant
US5533193(A)	1996-07-01	Roscoe	Applicant
US5533198(A)	1996-07-01	Thorson	Applicant
US5535326(A)	1996-07-01	Baskey et al.	Applicant
US5539883(A)	1996-07-01	Allon et al.	Applicant
US5542055(A)	1996-07-01	Amini et al.	Applicant
US5546272(A)	1996-08-01	Moss et al.	Applicant
US5548712(A)	1996-08-01	Larson et al.	Applicant
US5555510(A)	1996-09-01	Verseput et al.	Applicant
US5559764(A)	1996-09-01	Chen et al.	Applicant
US5559958(A)	1996-09-01	Farrand et al.	Applicant
US5559965(A)	1996-09-01	Oztaskin et al.	Applicant
US5560022(A)	1996-09-01	Dunstan et al.	Applicant
US5564024(A)	1996-10-01	Pemberton	Applicant
US5566299(A)	1996-10-01	Billings et al.	Applicant
US5566339(A)	1996-10-01	Perholtz et al.	Applicant
US5568610(A)	1996-10-01	Brown	Applicant
US5568619(A)	1996-10-01	Blackledge et al.	Applicant
US5572403(A)	1996-11-01	Mills	Applicant
US5577205(A)	1996-11-01	Hwang et al.	Applicant
US5579487(A)	1996-11-01	Meyerson et al.	Applicant
US5579491(A)	1996-11-01	Jeffries et al.	Applicant
US5581712(A)	1996-12-01	Herrman	Applicant
US5581714(A)	1996-12-01	Amini et al.	Applicant
US5584030(A)	1996-12-01	Husak et al.	Applicant
US5586250(A)	1996-12-01	Carbonneau et al.	Applicant
US5588121(A)	1996-12-01	Reddin et al.	Applicant
US5588144(A)	1996-12-01	Inoue et al.	Applicant
US5592610(A)	1997-01-01	Chittor	Applicant
US5592611(A)	1997-01-01	Midgely et al.	Applicant
US5596711(A)	1997-01-01	Burckhartt et al.	Applicant
US5598407(A)	1997-01-01	Bud et al.	Applicant
US5602758(A)	1997-02-01	Lincoln et al.	Applicant
US5606672(A)	1997-02-01	Wade	Applicant
US5608876(A)	1997-03-01	Cohen et al.	Applicant
US5615207(A)	1997-03-01	Gephardt et al.	Applicant
US5621159(A)	1997-04-01	Brown et al.	Applicant
US5621892(A)	1997-04-01	Cook	Applicant
US5622221(A)	1997-04-01	Genga, Jr. et al.	Applicant
US5623625(A)	1997-04-01	Thompson et al.	Examiner
US5625238(A)	1997-04-01	Ady et al.	Applicant
US5627962(A)	1997-05-01	Goodrum et al.	Applicant
US5628028(A)	1997-05-01	Michelson	Applicant
US5630076(A)	1997-05-01	Saulpaugh et al.	Applicant
US5631847(A)	1997-05-01	Kikinis	Applicant
US5632021(A)	1997-05-01	Jennings et al.	Applicant
US5638289(A)	1997-06-01	Yamada et al.	Applicant
US5644470(A)	1997-07-01	Benedict et al.	Applicant
US5644731(A)	1997-07-01	Liencres et al.	Applicant
US5651006(A)	1997-07-01	Fujino et al.	Applicant
US5652832(A)	1997-07-01	Kane et al.	Applicant
US5652839(A)	1997-07-01	Giorgio et al.	Applicant
US5652892(A)	1997-07-01	Ugajin	Applicant
US5652908(A)	1997-07-01	Douglas et al.	Applicant
US5655081(A)	1997-08-01	Bonnell et al.	Applicant
US5655083(A)	1997-08-01	Bagley	Applicant
US5655148(A)	1997-08-01	Richman et al.	Applicant
US5659682(A)	1997-08-01	Devarakonda et al.	Applicant
US5664118(A)	1997-09-01	Nishigaki et al.	Applicant
US5664119(A)	1997-09-01	Jeffries et al.	Applicant
US5666538(A)	1997-09-01	DeNicola	Applicant
US5668943(A)	1997-09-01	Attanasio et al.	Applicant
US5668992(A)	1997-09-01	Hammer et al.	Applicant
US5669009(A)	1997-09-01	Buktenica et al.	Applicant
US5671371(A)	1997-09-01	Kondo et al.	Applicant
US5675723(A)	1997-10-01	Ekrot et al.	Applicant
US5680288(A)	1997-10-01	Carey et al.	Applicant
US5684671(A)	1997-11-01	Hobbs et al.	Applicant
US5689637(A)	1997-11-01	Johnson et al.	Applicant
US5696895(A)	1997-12-01	Hemphill et al.	Applicant
US5696899(A)	1997-12-01	Kalwitz	Applicant
US5696949(A)	1997-12-01	Young	Applicant
US5696970(A)	1997-12-01	Sandage et al.	Applicant
US5704031(A)	1997-12-01	Mikami et al.	Applicant
US5708775(A)	1998-01-01	Nakamura	Applicant
US5708776(A)	1998-01-01	Kikinis	Applicant
US5712754(A)	1998-01-01	Sides et al.	Applicant
US5715456(A)	1998-02-01	Bennett et al.	Applicant
US5717570(A)	1998-02-01	Kikinis	Applicant
US5721935(A)	1998-02-01	DeSchepper et al.	Applicant
US5724529(A)	1998-03-01	Smith et al.	Applicant
US5726506(A)	1998-03-01	Wood	Applicant
US5727207(A)	1998-03-01	Gates et al.	Applicant
US5732266(A)	1998-03-01	Moore et al.	Applicant
US5737708(A)	1998-04-01	Grob et al.	Applicant
US5740378(A)	1998-04-01	Rehl et al.	Applicant
US5742514(A)	1998-04-01	Bonola	Applicant
US5742833(A)	1998-04-01	Dea et al.	Applicant
US5747889(A)	1998-05-01	Raynham et al.	Applicant
US5748426(A)	1998-05-01	Bedingfield et al.	Applicant
US5752164(A)	1998-05-01	Jones	Applicant
US5754797(A)	1998-05-01	Takahashi	Applicant
US5758165(A)	1998-05-01	Shuff	Applicant
US5758352(A)	1998-05-01	Reynolds et al.	Applicant
US5761033(A)	1998-06-01	Wilhelm	Applicant
US5761045(A)	1998-06-01	Olson et al.	Applicant
US5761085(A)	1998-06-01	Giorgio	Applicant
US5761462(A)	1998-06-01	Neal et al.	Applicant
US5761707(A)	1998-06-01	Aiken et al.	Applicant
US5764924(A)	1998-06-01	Hong	Applicant
US5764968(A)	1998-06-01	Ninomiya	Applicant
US5765008(A)	1998-06-01	Desai et al.	Applicant
US5765198(A)	1998-06-01	McCrocklin et al.	Applicant
US5767844(A)	1998-06-01	Stoye	Applicant
US5768541(A)	1998-06-01	Pan-Ratzlaff	Applicant
US5768542(A)	1998-06-01	Enstrom et al.	Applicant
US5771343(A)	1998-06-01	Hafner et al.	Applicant
US5774645(A)	1998-06-01	Beaujard et al.	Applicant
US5774741(A)	1998-06-01	Choi	Applicant
US5777897(A)	1998-07-01	Giorgio	Applicant
US5778197(A)	1998-07-01	Dunham	Applicant
US5781703(A)	1998-07-01	Desai et al.	Applicant
US5781716(A)	1998-07-01	Hemphill et al.	Applicant
US5781744(A)	1998-07-01	Johnson et al.	Applicant
US5781767(A)	1998-07-01	Inoue et al.	Applicant
US5781798(A)	1998-07-01	Beatty et al.	Applicant
US5784555(A)	1998-07-01	Stone	Applicant
US5784576(A)	1998-07-01	Guthrie et al.	Applicant
US5787019(A)	1998-07-01	Knight et al.	Applicant
US5787459(A)	1998-07-01	Stallmo et al.	Applicant
US5787491(A)	1998-07-01	Merkin et al.	Applicant
US5790775(A)	1998-08-01	Marks et al.	Applicant
US5790831(A)	1998-08-01	Lin et al.	Applicant
US5793948(A)	1998-08-01	Asahi et al.	Applicant
US5793987(A)	1998-08-01	Quackenbush et al.	Applicant
US5794035(A)	1998-08-01	Golub et al.	Applicant
US5796185(A)	1998-08-01	Takata et al.	Applicant
US5796580(A)	1998-08-01	Komatsu et al.	Applicant
US5796934(A)	1998-08-01	Bhanot et al.	Applicant
US5797023(A)	1998-08-01	Berman et al.	Applicant
US5798828(A)	1998-08-01	Thomas et al.	Applicant
US5799036(A)	1998-08-01	Staples	Applicant
US5799196(A)	1998-08-01	Flannery	Applicant
US5801921(A)	1998-09-01	Miller	Applicant
US5802269(A)	1998-09-01	Poisner et al.	Applicant
US5802298(A)	1998-09-01	Imai et al.	Applicant
US5802305(A)	1998-09-01	McKaughan et al.	Applicant
US5802324(A)	1998-09-01	Wunderlich et al.	Applicant
US5802393(A)	1998-09-01	Begun et al.	Applicant
US5802552(A)	1998-09-01	Fandrich et al.	Applicant
US5802592(A)	1998-09-01	Chess et al.	Applicant
US5803357(A)	1998-09-01	Lakin	Applicant
US5805804(A)	1998-09-01	Laursen et al.	Applicant
US5805834(A)	1998-09-01	McKinley et al.	Applicant
US5809224(A)	1998-09-01	Schultz et al.	Applicant
US5809256(A)	1998-09-01	Najemy	Applicant
US5809287(A)	1998-09-01	Stupek, Jr. et al.	Applicant
US5809311(A)	1998-09-01	Jones	Applicant
US5812748(A)	1998-09-01	Ohran et al.	Applicant
US5812750(A)	1998-09-01	Dev et al.	Applicant
US5812751(A)	1998-09-01	Ekrot et al.	Examiner
US5812757(A)	1998-09-01	Okamoto et al.	Applicant
US5812858(A)	1998-09-01	Nookala et al.	Applicant
US5815117(A)	1998-09-01	Kolanek	Applicant
US5815647(A)	1998-09-01	Buckland et al.	Applicant
US5815652(A)	1998-09-01	Ote et al.	Applicant
US5821596(A)	1998-10-01	Miu et al.	Applicant
US5822547(A)	1998-10-01	Boesch et al.	Applicant
US5835719(A)	1998-11-01	Gibson et al.	Applicant
US5835738(A)	1998-11-01	Blackledge, Jr. et al.	Applicant
US5838932(A)	1998-11-01	Alzien	Applicant
US5841964(A)	1998-11-01	Yamaguchi	Applicant
US5841991(A)	1998-11-01	Russell	Applicant
US5845061(A)	1998-12-01	Miyamoto et al.	Applicant
US5845095(A)	1998-12-01	Reed et al.	Applicant
US5852720(A)	1998-12-01	Gready et al.	Applicant
US5852724(A)	1998-12-01	Glenn, II et al.	Applicant
US5857074(A)	1999-01-01	Johnson	Applicant
US5857102(A)	1999-01-01	McChesney et al.	Applicant
US5864653(A)	1999-01-01	Tavellaei et al.	Applicant
US5864713(A)	1999-01-01	Terry	Applicant
US5867730(A)	1999-02-01	Leyda	Applicant
US5875307(A)	1999-02-01	Ma et al.	Applicant
US5875308(A)	1999-02-01	Egan et al.	Applicant
US5875310(A)	1999-02-01	Buckland et al.	Applicant
US5878237(A)	1999-03-01	Olarig	Applicant
US5878238(A)	1999-03-01	Gan et al.	Applicant
US5881311(A)	1999-03-01	Woods	Applicant
US5884027(A)	1999-03-01	Garbus et al.	Applicant
US5889965(A)	1999-03-01	Wallach et al.	Applicant
US5892898(A)	1999-04-01	Fujii et al.	Applicant
US5892928(A)	1999-04-01	Wallach et al.	Applicant
US5898846(A)	1999-04-01	Kelly	Applicant
US5898888(A)	1999-04-01	Guthrie et al.	Applicant
US5905867(A)	1999-05-01	Giorgio	Applicant
US5907672(A)	1999-05-01	Matze et al.	Applicant
US5909568(A)	1999-06-01	Nason	Applicant
US5911779(A)	1999-06-01	Stallmo et al.	Applicant
US5913034(A)	1999-06-01	Malcolm	Applicant
US5922060(A)	1999-07-01	Goodrum	Applicant
US5930358(A)	1999-07-01	Rao	Applicant
US5935262(A)	1999-08-01	Barrett et al.	Applicant
US5936960(A)	1999-08-01	Stewart	Applicant
US5938751(A)	1999-08-01	Tavallaei et al.	Applicant
US5941996(A)	1999-08-01	Smith et al.	Applicant
US5964855(A)	1999-10-01	Bass et al.	Applicant
US5983349(A)	1999-11-01	Kodama et al.	Applicant
US5987554(A)	1999-11-01	Liu et al.	Applicant
US6009535(A)	1999-12-01	Halligan et al.	Examiner
US6012130(A)	2000-01-01	Beyda et al.	Applicant
US6145089(A)	2000-11-01	Le et al.	Examiner
US6163853(A)	2000-12-01	Findlay et al.	Examiner
US6170028(B1)	2001-01-01	Wallach et al.	Applicant
US6173346(B1)	2001-01-01	Wallach et al.	Applicant
US6179486(B1)	2001-01-01	Wallach et al.	Applicant
US6192434(B1)	2001-02-01	Wallach et al.	Applicant
US6219734(B1)	2001-04-01	Wallach et al.	Applicant
US6247080(B1)	2001-06-01	Wallach et al.	Applicant
US6247099(B1)	2001-06-01	Skazinski et al.	Examiner
US6272648(B1)	2001-08-01	Findlay et al.	Examiner
US6304929(B1)	2001-10-01	Wallach et al.	Applicant
EP866403(A1)	1998-09-01		Applicant
JP4333118(A)	1992-11-01		Applicant
JP5233110(A)	1993-09-01		Applicant
JP7093064(A)	1995-04-01		Applicant
JP7261874(A)	1995-10-01		Applicant

Non-Patent Literature (26)

SPARCstorage Array User's Guide—Sep. 1996, Chapter 8, Getting Started.Applicant
Plasmon M-Series M52, M104, M156, and M258 Optical Disk Library Systems, SCSI Software Interface Specification, Document No. 303432C, Nov. 1996.Applicant
Institute of Information & Computer Sciences, scsi-faq/part1, last modified Mar. 31, 1998.Applicant
Cmasters, Usenet post to microsoft.public.windowsnt.setup, Aug. 1997, “Re: FDISK switches”.Applicant
Compaq Computer Corporation, Phenix Technologies, LTD, and Intel Corporation, specification, 55 pages, May 5, 1994, “Plug & Play BIOS Specification”.Applicant
Davis, T., Usenet post to alt.msdos.batch, Apr. 1997, “Re: Need help with automating FDISK and FORMat . . . ”.Applicant
Davis, T, Usenet post to alt.msdos.programmer, Apr. 1997, “Re: How do I create and FDISK batch file?”.Applicant
Gorlick, M., Conf. Proceedings: ACM/ONR Workshop on Parallel and Distributed Debugging, pp. 175-181, 1991, “The Flight Recorder: An Architectural Aid for System Monitoring”.Applicant
Hildebrand, N., Usenet post to comp.msdos.programmer, May 1995, “Re: Structure of disk partition into”.Applicant
IBM Technical Disclosure Bulletin, 92A+62947, pp. 391-394, Oct. 1992, Method for Card Hot Plug Detection and Control.Applicant
Lewis, L., Usenet post to alt.msdos.batch, Apr. 1997, “Re: Need help with automating FDISK and FORMAT”.Applicant
Lyons, Computer Reseller News, Issue 721, pp. 61-62, Feb. 3, 1997, “ACC Releases Low-Cost Solution for ISPs”.Applicant
M2 Communications, M2 Presswire, 2 pages, Dec. 19, 1996, “Novell IntranetWare Supports Hot Pluggable PCI from NetFRAME”.Applicant
NetFrame Systems Incorporated, Doc. No. 78-1000226-01, pp. 1-2, 5-8, 359-404, and 471-512, Apr. 1996, “NetFrame Clustered Multiprocessing Software: NW0496 DC-ROM for Novel® NetWare® 4.1 SMP, 4.1, and 3.12”.Applicant
Netframe, http://www.netframe-support.com/technology/datasheets/data.htm, before Mar. 1997, “Netframe ClusterSystem 9008 Data Sheet”.Applicant
PCI Hot-Plug Specification, Preliminary Revision for Review Only, Revision 0.9, pp. i-vi, and 1-25, Mar. 5, 1997.Applicant
Rigney, PC Magazine, 14(17): 375-379, Oct. 10, 1995, “The One for the Road (Mobile-aware capabilities in Windows 95)”.Applicant
SES SCSI-3 Enclosure Services, X3T10/Project 1212-D/Rev 8a, pp. i, iii-x, 1-76, and I-1 (index), Jan. 16, 1997.Applicant
Shanley, and Anderson, PCI System Architecture, Third Edition, Chapter 15, pp. 297-302, Copyright 1995, “Intro To Configuration Address Space”.Applicant
Shanley, and Anderson, PCI System Architecture, Third Edition, Chapter 16, pp. 303-328, Copyright 1995, “Configuration Transactions”.Applicant
Shanley, and Anderson, PCI System Architecture, Third Edition, p. 382, Copyright 1995.Applicant
Simos, M., Usenet post to comp.os.msdos.misc, Apr. 1997, “Re: Auto FDISK and FORMAT”.Applicant
Sun Microsystems, Part No. 802-6569-11, Release 1.0.1, Nov. 1996, “Remote Systems Diagnostics Installation & User Guide”.Applicant
Sun Microsystems Computer Company, Part No. 802-5355-10, Rev. A, May 1996, “Solstice SyMON User's Guid”.Applicant
Wood, M. H., Usenet post to comp.os.netware.misc, Aug. 1996, “Re: Workstation duplication method for WIN95”.Applicant
ftp.cdrom.com/pub/os2/diskutil/, PHDX software, phdx.zip download, Mar. 1995, “Parallel Hard Disk Xfer”.Applicant

Abstract

Description

INCORPORATION BY REFERENCE OF COMMONLY OWNED APPLICATIONS

[0003] The following patent applications, commonly owned and filed Oct. 1, 1997, are hereby incorporated herein in their entirety by reference thereto:


	Application
Title	No./Patent No.

“System Architecture for Remote Access and	08/942,160/6,266,721
Control of Environmental Management”
“Method of Remote Access and Control of	08/942,215/6,189,109
Environmental Management”
“System for Independent Powering of Diagnostic	08/942,410/6,202,160
Processes on a Computer System”
“Method of Independent Powering of Diagnostic	08/942,320/6,134,668
Processes on a Computer System”
“Diagnostic and Managing Distributed Processor	08/942,402/6,338,150
System”
“Method for Managing a Distributed Processor	08/942,448/6,249,885
System”
“System for Mapping Environmental Resources to	08/942,222/6,122,758
Memory for Program Access”
“Method for Mapping Environmental Resources	08/942,214/6,199,173
to Memory for Program Access”
“Hot Add of Devices Software Architecture”	08/942,309
“Method for The Hot Add of Devices”	08/942,306/6,247,080
“Hot Swap of Devices Software Architecture”	08/942,311/6,192,434
“Method for The Hot Swap of Devices”	08/942,457/6,304,929
“Method for the Hot Add of a Network Adapter	08/943,072/5,892,928
on a System Including a Dynamically Loaded
Adapter Driver”
“Method for the Hot Add of a Mass Storage	08/942,069/6,219,734
Adapter on a System Including a Statically
Loaded Adapter Driver”
“Method for the Hot Add of a Network Adapter	08/942,465/6,202,111
on a System Including a Statically Loaded
Adapter Driver”
“Method for the Hot Add of a Mass Storage	08/962,963/6,179,486
Adapter on a System Including a Dynamically
Loaded Adapter Driver”
“Method for the Hot Swap of a Network Adapter	08/943,078/5,889,965
on a System Including a Dynamically Loaded
Adapter Driver”
“Method for the Hot Swap of a Mass Storage	08/942,336/6,249,828
Adapter on a System Including a Statically
Loaded Adapter Driver”
“Method for the Hot Swap of a Network Adapter	08/942,459/6,219,734
on a System Including a Statically Loaded
Adapter Driver”
“Method for the Hot Swap of a Mass Storage	08/942,458/6,173,346
Adapter on a System Including a Dynamically
Loaded Adapter Driver”
“Method of Performing an Extensive Diagnostic	08/942,463/6,035,420
Test in Conjunction with a BIOS Test Routine”
“Apparatus for Performing an Extensive	08/942,163/6,009,541
Diagnostic Test in Conjunction with a BIOS Test
Routine”
“Configuration Management Method for Hot	08/941,268/6,148,355
Adding and Hot Replacing Devices”
“Configuration Management System for Hot	08/942,408/6,243,773
Adding and Hot Replacing Devices”
“Apparatus for Interfacing Buses”	08/942,382/6,182,180
“Method for Interfacing Buses”	08/942,413/5,987,554
“Computer Fan Speed Control Device”	08/942,447/5,990,582
“Computer Fan Speed Control Method”	08/942,216/5,962,933
“System for Powering Up and Powering Down a	08/943,076/6,122,746
Server”
“Method of Powering Up and Powering Down a	08/943,077/6,163,849
Server”
“System for Resetting a Server”	08/942,333/6,065,053
“Method of Resetting a Server”	08/942,405/6,330,690
“System for Displaying Flight Recorder”	08/942,070/6,138,250
“Method of Displaying Flight Recorder”	08/942,068/6,073,255
“Synchronous Communication Interface”	08/943,355/6,219,711
“Synchronous Communication Emulation”	08/942,004/6,068,661
“Software System Facilitating the Replacement or	08/942,317/6,134,615
Insertion of Devices in a Computer System”
“Method for Facilitating the Replacement or	08/942,316/6,134,614
Insertion of Devices in a Computer System”
“System Management Graphical User Interface”	08/943,357
“Display of System Information”	08/942,195/6,046,742
“Data Management System Supporting Hot Plug	08/942,129/6,105,089
Operations on a Computer”
“Data Management Method Supporting Hot Plug	08/942,124/6,058,445
Operations on a Computer”
“Alert Configurator and Manager”	08/942,005
“Managing Computer System Alerts”	08/943,356
“Computer Fan Speed Control System”	08/940,301/6,247,898
“Computer Fan Speed Control System Method”	08/941,267
“Black Box Recorder for Information System	08/942,381/6,269,412
Events”
“Method of Recording Information System	08/942,164/6,282,673
Events”
“Method for Automatically Reporting a System	08/942,168/6,243,838
Failure in a Server”
“System for Automatically Reporting a System	08/942,384/6,170,067
Failure in a Server”
“Expansion of PCI Bus Loading Capacity”	08/942,404/6,249,834
“Method for Expanding PCI Bus Loading	08/942,223/6,195,717
Capacity”
“System for Displaying System Status”	08/942,347/6,145,098
“Method of Displaying System Status”	08/942,071/6,088,816
“Fault Tolerant Computer System”	08/942,194/6,175,490
“Method for Hot Swapping of Network	08/943,044/6,324,608
Components”
“A Method for Communicating a Software	08/942,221/6,163,853
Generated Pulse Waveform Between Two Servers
in a Network”
“A System For Communicating a Software	08/942,409/6,272,648
Generated Pulse Waveform Between Two Servers
in a Network”
“Method for Clustering Software Applications”	08/942,318/6,134,673
“System for Clustering Software Applications”	08/942,411/6,363,497
“Method for Automatically Configuring a Server	08/942,319/6,212,585
after Hot Add of a Device”
“System for Automatically Configuring a Server	08/942,331/6,263,387
after Hot Add of a Device”
“Method of Automatically Configuring and	08/942,412/6,154,835
Formatting a Computer System and Installing
Software”
“System for Automatically Configuring and	08/941,955/6,138,179
Formatting a Computer System and Installing
Software”
“Determining Slot Numbers in a Computer”	08/942,462/6,269,417
“System for Detecting Errors in a Network”	08/942,169
“Method of Detecting Errors in a Network”	08/940,302
“System for Detecting Network Errors”	08/942,407/6,105,151
“Method of Detecting Network Errors”	08/942,573