US 6,145,098 AGrant
System for Displaying System Status
Issue Date:2000-11-07
•35 Claims
•26 Drawing Sheets
Abstract
A fault tolerant computer system for obtaining and displaying, or updating the status of server components through a remote interface and either a local or remote client machine without intervention of the server operating system software. The remote machine accesses the server by use of a dial-in modem connection, while the local machine accesses the server by a local serial connection. The components that can be monitored include, but are not limited to, the following: Power Supplies, Temperatures, Fans, Processors, I/O Groups, I/O Canisters, Serial Numbers, and Revisions.
Metadata
Assignee
- Micron Electronics, Inc.
Inventors
- Ahmad Nouri
- Karl S. Johnson
Application Information
Application Number:US 9423478
Filing Date:1997-10-01
Priority Date:1997-10-01
Art Unit:275
Classifications
IPC:
G06F 1100
Field of Search:
395714200.44;200.47;200.54;200.57;180;182.02;184.0131;47
Patent Drawings (26 sheets)
Description
PRIORITY CLAIM
The benefit under 35 U.S.C. .sctn. 119(e) of the following U.S. provisional application(s) is hereby claimed:
APPENDICES
Appendix A, which forms a part of this disclosure, is a list of commonly owned copending U.S. patent applications. Each one of the applications listed in Appendix A is hereby incorporated herein in its entirety by reference thereto.
Appendix B, which forms part of this disclosure, is a copy of the U.S. provisional patent application filed May 13, 1997, entitled "Remote Software for Monitoring and Managing Environmental Management System" and assigned application Ser. No. 60/046,326. Page 1, line 6 of the provisional application has been changed from the original to positively recite that the entire provisional application, including the attached documents, forms part of this disclosure.
COPYRIGHT RIGHTS
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
1. Field of the Invention
The present invention relates to fault tolerant computer systems. More specifically, the invention is directed to a system for providing remote access and control of server environmental management.
2. Description of the Related Technology
As enterprise-class servers become more powerful and more capable, they are also becoming increasingly sophisticated and complex. For many companies, these changes lead to concerns over server reliability and manageability, particularly in light of the increasingly critical role of server-based applications. While in the past many systems administrators were comfortable with all of the various components that made up a standards-based network server, today's generation of servers can appear as an incomprehensible, unmanageable black box. Without visibility into the underlying behavior of the system, the administrator must "fly blind." Too often the only indicators the network manager has on the relative health of a particular server is whether or not it is running.
It is well-acknowledged that there is a lack of reliability and availability of most standards-based servers. Server downtime, resulting either from hardware or software faults or from regular maintenance, continues to be a significant problem. By one estimate, the cost of downtime in mission critical environments has risen to an annual total of $4.0 billion for U.S. businesses, with the average downtime event resulting in a $140 thousand loss in the retail industry and a $450 thousand loss in the securities industry. It has been reported that companies lose as much as $250 thousand in employee productivity for every 1% of computer downtime. With emerging Internet, intranet and collaborative applications taking on more essential business roles every day, the cost of network server downtime will continue to spiral upward.
While hardware fault tolerance is an important element of an overall high availability architecture, it is only one piece of the puzzle. Studies show that a significant percentage of network server downtime is caused by transient faults in the I/O subsystem. These faults may be due, for example, to the device driver, the adapter card firmware, or hardware which does not properly handle concurrent errors, and often causes servers to crash or hang. The result is hours of downtime per failure, while a system administrator discovers the failure takes some action, and manually reboots the server. In many cases, data volumes on hard disk drives become corrupt and must be repaired when the volume is mounted. A dismount-and-mount cycle may result from the lack of "hot pluggability" in current standards-based servers. Diagnosing intermittent errors can be a frustrating and time-consuming process. For a system to deliver consistently high availability, it must be resilient to these types of faults. Accurate and available information about such faults is central to diagnosing the underlying problems and taking corrective action.
Modern fault tolerant systems have the functionality to provide the ambient temperature of a storage device enclosure and the operational status of other components such as the cooling fans and power supply. However, a limitation of these server systems is that they do not contain self-managing processes to correct malfunctions. Also, if a malfunction occurs in a typical server, it relies on the operating system software to report, record and manage recovery of the fault. However, many types of faults will prevent such software from carrying out these tasks. For example, a disk drive failure can prevent recording of the fault in a log file on that disk drive. If the system error caused the system to power down, then the system administrator would never know the source of the error.
Traditional systems are lacking in detail and sophistication when notifying system administrators of system malfunctions. System administrators are in need of a graphical user interface for monitoring the health of a network of servers. Administrators need a simple point-and-click interface to evaluate the health of each server in the network. In addition, existing fault tolerant servers rely upon operating system maintained logs for error recording. These systems are not capable of maintaining information when the operating system is inoperable due to a system malfunction. Existing systems do not have a system log for maintaining information when the main computational processors are inoperable or the operating system has crashed.
Another limitation of the typical fault tolerant system is that the control logic for the diagnostic system is associated with a particular processor. Thus, if the environmental control processor malfunctioned, then all diagnostic activity on the computer would cease. In traditional systems, if a controller dedicated to the fan system failed, then all fan activity could cease resulting in overheating and ultimate failure of the server. What is desired is a way to obtain diagnostic information when the server OS is not operational or even when main power to the server is down.
Existing fault tolerant systems also lack the power to remotely control a particular server, such as powering up and down, resetting, retrieving or updating system status, displaying flight recorder information and so forth. Such control of the server is desired even when the server power is down. For example, if the operating system on the remote machine failed, then a system administrator would have to physically go to the remote machine to re-boot the malfunctioning machine before any system information could be obtained or diagnostics could be started.
Therefore, a need exists for improvements in server management which will result in greater reliability and dependability of operation. Server users are in need of a management system by which the users can accurately gauge the health of their system. Users need a high availability system that must not only be resilient to faults, but must allow for maintenance, modification, and growth--without downtime. System users must be able to replace failed components, and add new functionality, such as new network interfaces, disk interface cards and storage, without impacting existing users. As system demands grow, organizations must frequently expand, or scale, their computing infrastructure, adding new processing power, memory, storage and I/O capacity. With demand for 24-hour access to critical, server-based information resources, planned system downtime for system service or expansion has become unacceptable.
SUMMARY OF THE INVENTION
The inventive remote access system provides system administrators with new levels of client/server system availability and management. It gives system administrators and network managers a comprehensive view into the underlying health of the server--in real time, whether on-site or off-site. In the event of a failure, the invention enables the administrator to learn why the system failed, why the system was unable to boot, and to control certain functions of the server from a remote station.
One embodiment of the present invention is a system for retrieving or updating system status for a computer, the system comprising: a first computer; a microcontroller capable of providing a retrieve or update system status signal to the first computer; a remote interface connected to the microcontroller; and a second computer connected to the first computer via the remote interface and communicating a retrieve or update system status command to the microcontroller.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a top level block diagram of a server system having a microcontroller network in communication with a local client computer or a remote client computer utilized by one embodiment of the present invention.
FIG. 2 is a detailed block diagram of the microcontroller network shown in FIG. 1.
FIG. 3 is a diagram of serial protocol message formats utilized in communications between the client computer and remote interface shown in FIGS. 1 and 2.
FIGS. 4a and 4b are one embodiment of a flow diagram of a power-on process performed by the microcontroller network and client computer of FIGS. 1 and 2.
FIG. 5 is one embodiment of a flow diagram of the power-on function shown in FIG. 4b.
FIGS. 6a and 6b are one embodiment of a flow diagram of a power-off process performed by the microcontroller network and client computer of FIGS. 1 and 2.
FIG. 7 is one embodiment of a flow diagram of the power-off function shown in FIG. 6b.
FIGS. 8a and 8b are one embodiment of a flow diagram of a reset process performed by the microcontroller network and client computer of FIGS. 1 and 2.
FIG. 9 is one embodiment of a flow diagram of the reset function shown in FIG. 8b.
FIGS. 10a and 10b are one embodiment of a flow diagram of a display flight recorder process performed by the microcontroller network and client computer of FIGS. 1 and 2.
FIG. 11 is one embodiment of a flow diagram of the read non-volatile RAM (NVRAM) contents function shown in FIG. 10b.
FIGS. 12a, 12b and 12c are a detailed block diagram of the microcontroller network components showing a portion of the inputs and outputs of the microcontrollers shown in FIG. 2.
FIGS. 13a and 13b are one embodiment of a flow diagram of a system status process performed by the microcontroller network and client computer of FIGS. 1 and 2.
FIG. 14 is one embodiment of a flow diagram of the system status function shown in FIG. 13b.
FIG. 15 is an exemplary screen display of a server power-on window seen at the client computer to control the microcontroller network of FIGS. 1 and 2.
FIG. 16 is an exemplary screen display of a flight recorder window seen at the client computer to control the microcontroller network of FIGS. 1 and 2.
FIG. 17 is an exemplary screen display of a system status window seen at the client computer to control the microcontroller network of FIGS. 1 and 2.
FIG. 18 is an exemplary screen display of a system status:fans window seen at the client computer to control the microcontroller network of FIGS. 1 and 2.
FIG. 19 is an exemplary screen display of a system status:fans:canister A window seen at the client computer to control the microcontroller network of FIGS. 1 and 2.
DETAILED DESCRIPTION OF THE INVENTION
The following detailed description presents a description of certain specific embodiments of the present invention. However, the present invention can be embodied in a multitude of different ways as defined and covered by the claims. In this description, reference is made to the drawings wherein like parts are designated with like numerals throughout.
For convenience, the description will be organized into the following principal sections: Introduction, Server System, Microcontroller Network, Remote Interface Serial Protocol, Power-On Flow, Power-Off Flow, Reset Flow, Flight Recorder Flow, and System Status Flow.
I. INTRODUCTION
The inventive computer server system and client computer includes a distributed hardware environment management system that is built as a small self-contained network of microcontrollers. Operating independently of the system processor and operating software, the present invention uses one or more separate processors for providing information and managing the hardware environment that may include fans, power supplies and/or temperature.
One embodiment of the present invention facilitates remotely powering-on and powering-off of the server system by use of a client computer. The client computer may be local to the server system, or may be at a location remote from the server system, in which case a pair of modems are utilized to provide communication between the client computer and the server system. A remote interface board connects to the server and interfaces to the server modem. Recovery manager software is loaded on the client computer to control the power-on and power-off processes and to provide feedback to a user though a graphical user interface.
Another embodiment of the present invention facilitates remotely resetting the server system by use of the client computer. Resetting the server system brings the server and operating system to a normal operating state. Recovery manager software is loaded on the client computer to control the resetting process and to provide feedback to a user though a graphical user interface.
Another embodiment of the present invention provides for a system log, known as a "flight recorder," which records hardware component failure and software crashes in a Non-Volatile RAM. With real time and date referencing, the system recorder enables system administrators to re-construct system activity by accessing the log. This information is very helpful in diagnosing the server system.
Initialization, modification and retrieval of system conditions is performed through utilization of a remote interface by issuing commands to the environmental processors. The system conditions may include system log size, presence of faults in the system log, serial number for each of the environmental processors, serial numbers for each power supply of the system, system identification, system log count, power settings and presence, canister presence, temperature, BUS/CORE speed ratio, fan speeds, settings for fan faults, LCD display, Non-Maskable Interrupt (NMI) request bits, CPU fault summary, FRU status, JTAG enable bit, system log information, remote access password, over-temperature fault, CPU error bits, CPU presence, CPU thermal fault bits, and remote port modem. The aforementioned list of capabilities provided by the present environmental system is not all-inclusive.
The server system and client computer provides mechanisms for the evaluation of the data that the system collects and methods for the diagnosis and repair of server problems in a manner that system errors can be effectively and efficiently managed. The time to evaluate and repair problems is minimized. The server system ensures that the system will not go down, so long as sufficient system resources are available to continue operation, but rather degrade gracefully until the faulty components can be replaced.
II. SERVER SYSTEM
Referring to FIG. 1, a server system 100 with a client computer will be described. In one embodiment, the server system hardware environment 100 may be built around a self-contained network of microcontrollers, such as, for example, a remote interface microcontroller on the remote interface board or circuit 104, a system interface microcontroller 106 and a system recorder microcontroller 110. This distributed service processor network 102 may operate as a fully self-contained subsystem within the server system 100, continuously monitoring and managing the physical environment of the machine (e.g., temperature, voltages, fan status). The microcontroller network 102 continues to operate and provides a system administrator with critical system information, regardless of the operational status of the server 100.
Information collected and analyzed by the microcontroller network 102 can be presented to a system administrator using either SNMP-based system management software (not shown), or using microcontroller network Recovery Manager software 130 through a local connection 121 or a dial-in connection 123. The system management software, which interfaces with the operating software (OS) 108 such as Microsoft Windows NT Version 4.0 or Novell Netware Version 4.11, for example, provides the ability to manage the specific characteristics of the server system, including Hot Plug Peripheral Component Interconnect (PCI), power and cooling status, as well as the ability to handle alerts associated with these features when the server is operational.
The microcontroller network Recovery Manager software 130 allows the system administrator to query the status of the server system 100 through the microcontroller network 102, even when the server is down. In addition, the server Operating Software 108 does not need to be running to utilize the Recovery Manager 130. Users of the Recovery Manager 130 are able to manage, diagnose and restore service to the server system quickly in the event of a failure through a friendly graphical user interface (GUI).
Using the microcontroller network remote management capability, a system administrator can use the Recovery Manager 130 to re-start a failed system through a modem connection 123. First, the administrator can remotely view the microcontroller network Flight Recorder, a feature that may, in one embodiment, store all system messages, status and error reports in a circular System Recorder memory. In one embodiment, the System Recorder memory may be a Non-Volatile Random Access Memory buffer (NVRAM) 112. Then, after determining the cause of the system problem, the administrator can use microcontroller network "fly by wire" capability to reset the system, as well as to power the system off or on. "Fly by wire" denotes that no switch, indicator or other control is directly connected to the function it monitors or controls, but instead, all the control and monitoring connections are made by the microcontroller network 102.
The remote interface or remote interface board (RIB) 104 interfaces the server system 100 to an external client computer. The RIB 104 connects to either a local client computer 122 at the same location as the server 100 or to a remote client computer 124 either directly or through an optional switch 120. The client computer 122/124 may in one embodiment run either Microsoft Windows 95 or Windows NT Workstation version 4.0 operating software (OS) 132. The processor and RAM requirements of the client computer 122/124 are such as may be specified by the vendor of the OS 132. The serial port of the client computer 122/124 may utilize a type 16550A Universal Asynchronous Receiver Transmitter (UART). The switch facilitates either the local connection 121 or the modem connection 123 at any one time, but allows both types of connections to be connected to the switch. In an another embodiment, either the local connection 121 or the modem connection 123 is connected directly to the RIB 104. The local connection 121 utilizes a readily available null-modem serial cable to connect to the local client computer. The modem connection may utilize a Hayes-compatible server modem 126 and a Hayes-compatible client modem 128. In one embodiment, a model fax modem V.34X 33.6K available from Zoom is utilized as the client modem and the server modem. In another embodiment, a Sportster 33.6K fax modem available from US Robotics is utilized as the client modem.
The steps of connecting the remote client computer 124 to the server 100 will now be briefly described. The remote interface 104 has a serial port connector (not shown) that directly connects with a counterpart serial port connector of the external server modem 126 without the use of a cable. If desired, a serial cable could be used to interconnect the remote interface 104 and the server modem 126. The cable end of an AC to DC power adapter (not shown, for example 120 Volt AC/7.5 Volt DC) is then connected to a DC power connector (not shown) of the remote interface, while the double-prong end is plugged into a 120 Volt AC wall outlet. One end of an RJ-45 parallel-wire data cable 103 is then plugged into an RJ-45 jack (not shown) on the remote interface 104, while the other end is plugged into a RJ-45 Recovery Manager jack on the server 100. The RJ-45 jack on the server then connects to the microcontroller network 102. The server modem 126 is then connected to a communications network 127 using an appropriate connector. The communications network 127 may be a public switched telephone network, although other modem types and communication networks are envisioned. For example, if cable modems are used for the server modem 126 and client modem 128, the communications network can be a cable television network. As another example, satellite modulator/demodulators can be used in conjunction with a satellite network.
In another embodiment, the server modem to client modem connection may be implemented by an Internet connection utilizing the well known TCP/IP protocol. Any of several Internet access devices, such as modems or network interface cards, may be utilized. Thus, the communications network 127 may utilize either circuit or packet switching.
At the remote client computer 124, a serial cable (for example, a 25-pin D-shell) 129 is used to interconnect the client modem 128 and the client computer 124. The client modem 128 is then connected to the communications network 127 using an appropriate connector. Each modem is then plugged into an appropriate power source for the modem, such as an AC outlet. At this time, the Recovery Manager software 130 is loaded into the client computer 124, if not already present, and activated.
The steps of connecting the local client computer 122 to the server 100 are similar, but modems are not necessary. The main difference is that the serial port connector of the remote interface 104 connects to a serial port of the local client computer 122 by the null-modem serial cable 121.
III. MICROCONTROLLER NETWORK
In one embodiment, the current invention may include a network of microcontrollers 102 (FIG. 1). The microcontrollers may provide functionality for system control, diagnostic routines, self-maintenance control, and event logging processors. A further description of the microcontrollers and microcontroller network is provided in U.S. patent application Ser. No. 08/942402, entitled "Diagnostic and Managing Distributed Processor System".
Referring to FIG. 2, in one embodiment of the invention, the network of microcontrollers 102 includes ten processors. One of the purposes of the microcontroller network 102 is to transfer messages to the other components of the server system 100. The may processors include: a System Interface controller 106, a CPU A controller 166, a CPU B controller 168, a System Recorder 110, a Chassis controller 170, a Canister A controller 172, a Canister B controller 174, a Canister C controller 176, a Canister D controller 178 and a Remote Interface controller 200. The Remote Interface controller 200 is located on the RIB 104 (FIG. 1) which is part of the server system 100, but may be external to a server enclosure. The System Interface controller 106, the CPU A controller 166 and the CPU B controller 168 are located on a system board 150 (also sometimes called a motherboard) in the server 100. Also located on the system board are one or more central processing units (CPUs) or microprocessors 164 and an Industry Standard Architecture (ISA) bus 162 that connects to the System Interface Controller 106. Of course, other buses such as PCI, EISA and Microchannel may be used. The CPU 164 may be any conventional general purpose single-chip or multi-chip microprocessor such as a Pentium.RTM., Pentium.RTM. Pro or Pentium.RTM. II processor available from Intel Corporation, a SPARC processor available from Sun Microsystems, a MIPS.RTM. processor available from Silicon Graphics, Inc., a Power PC.RTM. processor available from Motorola, or an ALPHA.RTM. processor available from Digital Equipment Corporation. In addition, the CPU 164 may be any conventional special purpose microprocessor such as a digital signal processor or a graphics processor.
The System Recorder 110 and Chassis controller 170, along with the System Recorder memory 112 that connects to the System Recorder 110, may be located on a backplane 152 of the server 100. The System Recorder 110 and Chassis controller 170 are the first microcontrollers to power up when server power is applied. The System Recorder 110, the Chassis controller 170 and the Remote Interface microcontroller 200 (on the RIB) are the three microcontrollers that have a bias 5 Volt power supplied to them. If main server power is off, an independent power supply source for the bias 5 Volt power is provided by the RIB 104 (FIG. 1). The Canister controllers 172-178 are not considered to be part of the backplane 152 because they are located on separate cards which are removable from the backplane 152.
Each of the microcontrollers has a unique system identifier or address. The addresses are as follows in Table 1:
The microcontrollers may be Microchip Technologies, Inc. PIC processors in one embodiment, although other microcontrollers, such as an 8051 available from Intel, an 8751, available from Atmel, or a P80CL580 microprocessor available from Philips Semiconductor, could be utilized. The PIC16C74 (Chassis controller 170) and PIC16C65 (the other controllers) are members of the PIC16CXX family of high-performance CMOS, fully-static, EPROM-based 8-bit microcontrollers. The PIC controllers have 192 bytes of RAM, in addition to program memory, three timer/counters, two capture/compare/Pulse Width Modulation modules and two serial ports. The synchronous serial port is configured as a two-wire Inter-Integrated Circuit (I.sup.2 C) bus in one embodiment of the invention. The PIC controllers use a Harvard architecture in which program and data are accessed from separate memories. This improves bandwidth over traditional von Neumann architecture controllers where program and data are fetched from the same memory. Separating program and data memory further allows instructions to be sized differently than the 8-bit wide data word. Instruction opcodes are 14-bit wide making it possible to have all single word instructions. A 14-bit wide program memory access bus fetches a 14-bit instruction in a single cycle.
In one embodiment of the invention, the microcontrollers communicate through an I.sup.2 C serial bus, also referred to as a microcontroller bus 160. The document "The I.sup.2 C Bus and How to Use It" (Philips Semiconductor, 1992) is hereby incorporated by reference. The I.sup.2 C bus is a bidirectional two-wire bus and operates at a 400 kbps rate in the present embodiment. However, other bus structures and protocols could be employed in connection with this invention. For example, the Apple Computer ADB, Universal Serial Bus, IEEE-1394 (Firewire), IEEE-488 (GPIB), RS-485, or Controller Area Network (CAN) could be utilized as the microcontroller bus. Control on the microcontroller bus is distributed. Each microcontroller can be a sender (a master) or a receiver (a slave) and each is interconnected by this bus. A microcontroller directly controls its own resources, and indirectly controls resources of other microcontrollers on the bus.
Here are some of the features of the I.sup.2 C-bus:
Two bus lines are utilized: a serial data line (SDA) and a serial clock line (SCL).
Each device connected to the bus is software addressable by a unique address and simple master/slave relationships exist at all times; masters can operate as master-transmitters or as master-receivers.
The bus is a true multi-master bus including collision detection and arbitration to prevent data corruption if two or more masters simultaneously initiate data transfer.
Serial, 8-bit oriented, bidirectional data transfers can be made at up to 400 kbit/second in the fast mode.
Two wires, serial data (SDA) and serial clock (SCL), carry information between the devices connected to the I.sup.2 C bus. Each device is recognized by a unique address and can operate as either a transmitter or receiver, depending on the function of the device. For example, a memory device connected to the I.sup.2 C bus could both receive and transmit data. In addition to transmitters and receivers, devices can also be considered as masters or slaves when performing data transfers (see Table 2). A master is the device which initiates a data transfer on the bus and generates the clock signals to permit that transfer. At that time, any device addressed is considered a slave.
The I.sup.2 C-bus is a multi-master bus. This means that more than one device capable of controlling the bus can be connected to it. As masters are usually microcontrollers, consider the case of a data transfer between two microcontrollers connected to the I.sup.2 C-bus. This highlights the master-slave and receiver-transmitter relationships to be found on the I.sup.2 C-bus. It should be noted that these relationships are not permanent, but depend on the direction of data transfer at that time. The transfer of data would proceed as follows:
1) Suppose microcontroller A wants to send information to microcontroller B:
microcontroller A (master), addresses microcontroller B (slave);
microcontroller A (master-transmitter), sends data to microcontroller B (slave-receiver);
microcontroller A terminates the transfer.
2) If microcontroller A wants to receive information from microcontroller B:
microcontroller A (master addresses microcontroller B (slave);
microcontroller A (master-receiver) receives data from microcontroller B (slave-transmitter);
microcontroller A terminates the transfer.
Even in this situation, the master (microcontroller A) generates the timing and terminates the transfer.
The possibility of connecting more than one microcontroller to the I.sup.2 C-bus means that more than one master could try to initiate a data transfer at the same time. To avoid the chaos that might ensue from such an event, an arbitration procedure has been developed. This procedure relies on the wired-AND connection of all I.sup.2 C interfaces to the I.sup.2 C-bus.
If two or more masters try to put information onto the bus, the first to produce a `one` when the other produces a `zero` will lose the arbitration. The clock signals during arbitration are a synchronized combination of the clocks generated by the masters using the wired-AND connection to the SCL line.
Generation of clock signal on the I.sup.2 C-bus is the responsibility of master devices. Each master microcontroller generates its own clock signals when transferring data on the bus.
The command, diagnostic, monitoring and history functions of the microcontroller network 102 are accessed using a global network memory model in one embodiment. That is, any function may be queried simply by generating a network "read" request targeted at the function's known global network address. In the same fashion, a function may be exercised simply by "writing" to its global network address. Any microcontroller may initiate read/write activity by sending a message on the I.sup.2 C bus to the microcontroller responsible for the function (which can be determined from the known global address of the function). The network memory model includes typing information as part of the memory addressing information.
Using a network global memory model in one embodiment places relatively modest requirements for the I.sup.2 C message protocol.
All messages conform to the I.sup.2 C message format including addressing and read/write indication.
All I.sup.2 C messages use seven bit addressing.
Any controller can originate (be a Master) or respond (be a Slave).
All message transactions consist of I.sup.2 C "Combined format" messages. This is made up of two back-to-back I.sup.2 C simple messages with a repeated START condition between (which does not allow for re-arbitrating the bus). The first message is a Write (Master to Slave) and the second message is a Read (Slave to Master).
Two types of transactions are used: Memory-Read and Memory-Write.
Sub-Addressing formats vary depending on data type being used.
IV. REMOTE INTERFACE SERIAL PROTOCOL
The microcontroller network remote interface serial protocol communicates microcontroller network messages across a point-to-point serial link. This link is between the RIB controller 200 that is in communication with the Recovery Manager 130 at the remote client 122/124. This protocol encapsulates microcontroller network messages in a transmission packet to provide error-free communication and link security.
In one embodiment, the remote interface serial protocol uses the concept of byte stuffing. This means that certain byte values in the data stream have a particular meaning. If that byte value is transmitted by the underlying application as data, it must be transmitted as a two-byte sequence.
The bytes that have a special meaning in this protocol are:
As stated above, if any of these byte values occur as data in a message, a two byte sequence must be substituted for that byte. The sequence is a byte with the value of SUB, followed by a type with the value of the original byte, which is incremented by one. For example, if a SUB byte occurs in a message, it is transmitted as a SUB followed by a byte that has a value of SUB+1.
Referring to FIG. 3 the two types of messages 201 used by the remote interface serial protocol will be described.
1. Requests 202, which are sent by remote management (client) computers 122/124 (FIG. 1) to the remote interface 104.
2. Responses 204, which are returned to the requester 122/124 by the remote interface 104.
The fields of the messages are defined as follows:
V. POWER-ON FLOW
The microcontroller network 102 (FIG. 1) performs various system administration tasks, such as, for example, monitoring the signals that come from server control switches, temperature sensors and client computers. By such signals, the microcontroller network 102, for example, turns on or turns off power to the server components, resets the server system, turns the system cooling fans to high, low or off, provides system operating parameters to the Basic Input/Output System (BIOS), transfers power-on self test (POST) events information from the BIOS, and/or sends data to a system display panel and remote computers.
Microcontroller Communication
A microcontroller, such as the remote interface microcontroller 200, handles two primary tasks: Sending and Receiving messages.
1. Handling the requests from other microcontrollers:
Incoming messages are handled based on interrupt, where a first byte of an incoming message is the Slave Address which is checked by all controllers connected to the microcontroller bus 160 (FIG. 2). Whichever microcontroller has the matched ID would respond with an acknowledgement to the sender controller. The sender then sends one byte of the message type followed by a two byte command ID, low byte first. The next byte of the message defines the length of the data associated with the message. The first byte of the message also specifies whether it is a WRITE or READ command. If it is a WRITE command, the slave controller executes the command with the data provided in the message and sends back a status response at the end of the task. If it is a READ command, the slave controller gathers the requested information and sends it back as the response. The codes to execute request commands are classified in groups according to the data type to simplify the code.
2. Sending a message to other microcontrollers:
Messages can be initiated by any controller on the bus 160 (FIG. 2). For example, the message can be an event detected by a controller and sent to the System Recorder controller and System Interface controller 106, or it could also be a message from the remote interface 104 (FIG. 1) to a specific controller on the bus 160. The sender usually sends the first byte defining the target processor and waits for the acknowledgement, which is the reverse logic from the Receiving a Message sequence. The sender also generates the necessary clock for the communication.
Referring to FIGS. 4a, 4b and FIG. 1, a Power-On process 270 will now be described. Process 270 begins at start state 272 and if a connection between the client computer 122/124 and the server 100 is already active, process 270 proceeds to directly to state 296. Otherwise, if a connection is not already active, process 270 proceeds to state 273 and utilizes the Recovery Manager software 130 to present a dialog window to the user on a display of the client computer 122/124 requesting information. The user is requested to enter a password for security purposes. The dialog window also has a pair of radio-buttons to select either a serial (local) connection or a modem (remote) connection. If serial is selected, the user is requested to select a COM port. If modem is selected, the user is requested to enter a telephone number to be used in dialing the server modem.
Moving to decision state 274, process 270 determines if a modem-type connection was selected. A modem-type connection is generally utilized in the situation where the client computer 124 is located at a location remote from the server 100. If it is determined at decision state 274 that a modem connection is utilized, process 270 moves to state 276 wherein the client computer 124 is connected to the client modem 128. Moving to state 278, a connection is established between the client modem 128 and the server modem 126 via a communications network 127, as previously described above. Continuing at state 280, the server modem 126 connects with the remote interface 104. Proceeding to state 282, the remote interface 104 connects to the server 100 via the RJ-45 cable 103. Moving to state 286, the Recovery Manager software 130 at the client computer 124 dials the server modem 126 through the client modem 128, handshakes with the remote interface 104, and checks the previously entered password. Process 270 remains at state 286 until a successful communication path with the remote interface 104 is established.
Returning to decision state 274, if a local connection 121 is utilized instead of the modem connection 123, process 270 proceeds to state 288 wherein the local client computer 122 is connected with the remote interface 104. Moving to state 292, the remote interface 104 is connected with the server 100. The previously entered password (at state 273) is sent to the remote interface 104 to identify the user at the local computer 122. If the password matches a password that is stored in the server system 100, the communication path with the remote interface is enabled.
After successful modem communication has been established and the password confirmed at state 286, or at the completion of connecting the remote interface to the server and checking the password at state 292, process 270 continues at state 296. At state 296, the Recovery Manager software 130 will in one embodiment display a recovery manager window 920, which includes a server icon 922 as shown in FIG. 15. A server window panel 928 and a confirmation dialog box 936 are not displayed at this time. The user at the client computer 122/124 then selects the server icon on the display, such as, for example by clicking a pointer device on the icon. Moving to state 298, the server window panel 928 is then displayed to the user. The user confirmation box 936 is not displayed at this time. The user selects a Power On button 930 on the window panel 928 to trigger the power-on operation. Continuing at state 300, the user confirmation dialog box 936 is then displayed on the client computer display. If the user confirms that the server is to be powered up, process 270 proceeds through off page connector A 302 to state 304 on FIG. 4b.
At state 304, the Recovery Manager software 130 at the client computer 122/124 provides a microcontroller network command (based on selecting the Power On button) and sends it to communication layer software. Proceeding to state 306, the communication layer puts a communications protocol around the command (from state 304) and sends the encapsulated command to the server through the client modem 128, the server modem 126 and the remote interface 104. The communications protocol was discussed in conjunction with FIG. 3 above. The encapsulated command is of the Request type 202 shown in FIG. 3. The remote interface 104 converts the encapsulated command to the microcontroller network format, which is described in U.S. patent application Ser. No. 08/942402, entitled "DIAGNOSTIC AND MANAGING DISTRIBUTED PROCESSOR SYSTEM," and in U.S. patent application Ser. No. 08/942160, entitled "SYSTEM ARCHITECTURE FOR REMOTE ACCESS AND CONTROL OF ENVIRONMENTAL MANAGEMENT." Process 270 then continues to a function 310 wherein the server receives the command and powers on the server. Function 310 will be further described in conjunction with FIG. 5.
Moving to state 312, the response generated by the server is then sent to the remote interface 104. In one embodiment, the microcontroller (the Chassis controller 170 in this instance) performing the command at the server returns status at the time of initiation of communication with the microcontroller. At the completion of the power-on operation by the Chassis controller 170, the Recovery Manager 130 sends a read status command to the Chassis controller (using states 304 and 306) to retrieve information on the results of the operation.
Proceeding to decision state 314, process 270 determines if the power on command was successful. If so, process 270 proceeds to state 316 wherein the remote interface 104 sends the response to the server modem 126 indicating the success of the command. Alternatively, if a local connection 121 is utilized, the response is sent to the local client computer 122. However, if the power on is not successful, as determined at decision state 314, process 270 proceeds to state 318 wherein the remote interface 104 sends the response to the server modem (or local client computer) indicating a failure of the command. At the conclusion of either state 316 or 318, process 270 proceeds to state 320 wherein the remote interface 104 sends the response back through the server modem 126 to the client modem 128. Moving to state 322, the client modem 128 sends the response back to the Recovery Manager software 130 at the remote client computer 124. Note that if the local connection 121 is being utilized, states 320 and 322 are not necessary. Proceeding to decision state 324, process 270 determines whether the command was successful. If so, process 270 continues at state 326 and displays a result window showing the success of the command on the display at the client computer 122/124. However, if the command was not successful, process 270 proceeds to state 328 wherein a result window showing failure of the command is displayed to the user. Moving to state 330, the details of the command information are available, if the user so desires, by selecting a details button. At the completion of state 326 or state 330, process 270 completes at end state 332.
Referring to FIG. 5, one embodiment of the server Power On function 310 will now be described. Beginning at start state 360, function 310 proceeds to state 362 and logs the requested power-on to the server 100 in the System Recorder memory 112. Proceeding to decision state 364, function 310 determines if a system over-temperature condition is set. If so, function 310 proceeds to state 366 and sends a over-temperature message to the remote interface 104. Advancing to state 368, because the system over-temperature condition is set, the power-on process is stopped and function 310 returns at a return state 370.
Returning to decision state 364, if the system over-temperature condition is not set, function 310 proceeds to state 372 and sets an internal power-on indicator and a reset/run countdown timer. In one embodiment, the reset/run countdown timer is set to a value of five. Advancing to state 374, function 310 turns on the power and cooling fans for the server system board 150, backplane 152 and I/O canisters. The microcontroller network holds the main system processor reset/run control line in the reset state until the reset/run countdown timer expires to allow the system power to stabilize. When the timer expires then the reset/run control is set to "run" and the system processor(s) begin their startup sequence by proceeding to state 376 and calling a BIOS Power-On Self Test (POST) routine. Moving to state 378, the BIOS initializes a PCI-ISA bridge and a microcontroller network driver. Continuing to state 380, the microcontroller network software monitors: hardware temperatures, switches on a control panel on the server, and signals from the remote interface 104. In one embodiment, state 380 may be performed anywhere during states 376 to 394 because the BIOS operations are performed by the server CPUs 164 (FIG. 2) independently of the microcontroller network 102. Function 310 then moves to a BIOS POST Coldstart function 386. In the Coldstart POST function, approximately 61 BIOS subroutines are called. The major groups of the Coldstart path include: CPU initialization, DMA/timer reset, BIOS image check, chipset initialization, CPU register initialization, CMOS test, PCI initialization, extended memory check, cache enable, and message display.
At the completion of the BIOS POST Coldstart function 386, function 310 proceeds to state 388 where BIOS POST events are logged in the System Recorder memory 112. Proceeding to state 390, the BIOS POST performs server port initialization. Continuing at state 392, the BIOS POST initializes the Operating System related controllers (e.g., floppy controller, hard disk controller) and builds a multi-processor table. Advancing to state 394, the BIOS POST performs an OS boot preparation sequence. Function 310 ends at a return state 398.
VI. POWER-OFF FLOW
Referring to FIGS. 6a, 6b and FIG. 1, one embodiment of a Power-Off process 420 will now be described. Process 420 begins at start state 422 and if a connection between the client computer 122/124 and the server 100 is already active, process 420 proceeds to directly to state 446. Otherwise, if a connection is not already active, process 420 proceeds to state 423 and utilizes the Recovery Manager software 130 to present a dialog window to the user on a display of the client computer 122/124 requesting information. The user is requested to enter a password for security purposes. The dialog window also has a pair of radio-buttons to select either a serial (local) connection or a modem (remote) connection. If serial is selected, the user is requested to select a COM port. If modem is selected, the user is requested to enter a telephone number to be used in dialing the server modem.
Moving to decision state 424, process 420 determines if the modem-type connection 123 will be utilized. The modem-type connection is generally utilized in the situation where the client computer 124 is located at a location remote from the server 100. If it is determined at decision state 424 that a modem connection is utilized, process 420 moves to state 426 wherein the client computer 124 is connected to the client modem 128. Moving to state 428, a connection is established between the client modem 128 and the server modem 126 via the communications network 127. Continuing at state 430, the server modem 126 connects with the remote interface 104. Proceeding to state 432, the remote interface 104 connects to the server 100 via the RJ-45 cable 103. Moving to state 436, the Recovery Manager software 130 at the client computer 124 dials the server modem 126 through the client modem 128, handshakes with the remote interface 104, and checks the previously entered password. Process 420 remains at state 436 until a successful communication path with the remote interface 104 is established.
Returning to decision state 424, if the local connection 121 is utilized instead of the modem connection 123, process 420 proceeds to state 438 wherein the local client computer 122 is connected with the remote interface 104. Moving to state 442, the remote interface 104 is connected with the server 100. The previously entered password (at state 423) is sent to the remote interface 104 to identify the user at the local computer 122. If the password matches the password that is stored in the server system 100, the communication path with the remote interface 104 is enabled.
After successful modem communication has been established and the password confirmed at state 436, or at the completion of checking the password at state 442, process 420 continues at state 446. At state 446, the Recovery Manager software 130 will in one embodiment display the Recovery Manager window 920, which includes the server icon 922 as shown in FIG. 15. The server window panel 928 and the confirmation dialog box 936 are not displayed at this time. The user at the client computer 122/124 then selects the server icon 922 on the display, such as by clicking the pointer device on the icon. Moving to state 448, the server window panel 928 (FIG. 15) is then displayed to the user. The user selects a Power Off button 932 on the window panel 928 to trigger the power-off operation. Continuing at state 450, a user confirmation dialog box is then displayed on the client computer display. If the user confirms that the server is to be powered down, process 420 proceeds through off page connector A 452 to state 454 on FIG. 6b.
At state 454, the Recovery Manager software 130 at the client computer 122/124 provides a microcontroller network command (based on selecting the Power Off button) and sends it to communication layer software. Proceeding to state 456, the communication layer puts a communications protocol around the command (from state 454) and sends the encapsulated command to the server through the client modem 128, the server modem 126 and the remote interface 104. The encapsulated command is of the Request type 202 shown in FIG. 3. Process 420 then continues to a function 460 wherein the server receives the command and powers off the server. Function 460 will be further described in conjunction with FIG. 7.
Moving to state 462, the response generated by the server is then sent to the remote interface 104. In one embodiment, the microcontroller (the Chassis controller 170 in this instance) performing the command at the server returns status at the time of initiation of communication with the microcontroller. At the completion of the power-off operation by the Chassis controller 170, the Recovery Manager 130 sends a read status command to the Chassis controller (using states 454 and 456) to retrieve information on the results of the operation.
Proceeding to decision state 464, process 420 determines if the power off command was successful. If so, process 420 proceeds to state 466 wherein the remote interface 104 sends the response to the server modem 126 indicating the success of the command. Alternatively, if a local connection 121 is utilized, the response is sent to the local client computer 122. However, if the power off is not successful, as determined at decision state 464, process 270 proceeds to state 468 wherein the remote interface 104 sends the response to the server modem (or local client computer) indicating a failure of the command. At the conclusion of either state 466 or 468, process 420 proceeds to state 470 wherein the remote interface 104 sends the response back through the server modem 126 to the client modem 128. Moving to state 472, the client modem 128 sends the response back to the Recovery Manager software 130 at the remote client computer 124. Note that if the local connection 121 is being utilized, states 470 and 472 are not necessary. Proceeding to decision state 474, process 420 determines whether the command was successful. If so, process 420 continues at state 476 and displays a result window showing the success of the command on the display at the client computer 122/124. However, if the command was not successful, process 420 proceeds to state 478 wherein a result window showing failure of the command is displayed to the user. Moving to state 480, the details of the command information are available, if the user so desires, by selecting a details button. At the completion of state 476 or state 480, process 420 completes at end state 482.
Referring to FIG. 7, the server Power-Off function 460 will now be described. Beginning at start state 500, function 460 proceeds to state 502 and logs the requested Power-Off message in the System Recorder memory 112 (FIG. 2) by use of the System Recorder controller 110. Moving to state 504, function 460 clears a system run indicator and clears the reset/run countdown timer. Moving to state 506, function 460 clears an internal power-on indicator. In one embodiment, the power-on indicator is stored by a variable "S4.sub.-- power.sub.-- on". Function 460 utilizes the CPU A controller 166 for state 504 and the Chassis controller 170 for state 506. Continuing at state 508, function 460 turns off the power and the cooling fans for the system board 150, the backplane 152 and the canister(s) associated with the Canister controllers 172-178. Function 460 ends at a return state 512.
VII. RESET FLOW
Referring to FIGS. 8a, 8b and FIG. 1, one embodiment of a Reset process 540 will now be described. Process 540 begins at start state 542 and if a connection between the client computer 122/124 and the server 100 is already active, process 540 proceeds to directly to state 566. Otherwise, if a connection is not already active, process 540 proceeds to state 543 and utilizes the Recovery Manager software 130 to present a dialog window to the user on a display of the client computer 122/124 requesting information. The user is requested to enter a password for security purposes. The dialog window also has a pair of radio-buttons to select either a serial (local) connection or a modem (remote) connection. If serial is selected, the user is requested to select a COM port. If modem is selected, the user is requested to enter a telephone number to be used in dialing the server modem.
Moving to decision state 544, process 540 determines if the modem-type connection 123 was selected. The modem-type connection is generally utilized in the situation where the client computer 124 is located at a location remote from the server 100. If it is determined at decision state 544 that a modem connection is utilized, process 540 moves to state 546 wherein the client computer 124 is connected to the client modem 128. Moving to state 548, a connection is established between the client modem 128 and the server modem 126 via the communications network 127. Continuing at state 550, the server modem 126 connects with the remote interface 104. Proceeding to state 552, the remote interface 104 connects to the server 100 via the RJ-45 cable 103. Moving to state 556, the Recovery Manager software 130 at the client computer 124 dials the server modem 126 through the client modem 128, handshakes with the remote interface 104, and checks the previously entered password. Process 540 remains at state 556 until a successful communication path with the remote interface 104 is established.
Returning to decision state 544, if the local connection 121 is utilized instead of the modem connection 123, process 540 proceeds to state 558 wherein the local client computer 122 is connected with the remote interface 104. Moving to state 562, the remote interface 104 is connected with the server 100. The password previously entered (at state 543) is sent to the remote interface 104 to identify the user at the local computer 122. If the password matches the password that is stored in the server system 100, the communication path with the remote interface 104 is enabled.
After successful modem communication has been established and the password confirmed at state 556, or at the completion of connecting the remote interface to the server and checking the password at state 562, process 540 continues at state 566. At state 566, the Recovery Manager software 130 will in one embodiment display the Recovery Manager window 920, which includes the server icon 922 as shown in FIG. 15. The server window panel 928 and the confirmation dialog box 936 are not displayed at this time. The user at the client computer 122/124 then selects the server icon 922 on the display, such as by clicking the pointer device on the icon. Moving to state 568 the server window panel 928 (FIG. 15) is then displayed to the user. The user confirmation box 936 is not displayed at this time. The user selects a System Reset button 934 on the window panel 928 to trigger the System Reset operation. Continuing at state 570, a user confirmation dialog box is then displayed on the client computer display. If the user confirms that the system is to be reset, process 540 proceeds through off page connector A 572 to decision state 574 on FIG. 8b.
At decision state 574, process 540 determines if the server is currently running (powered up, such as after a power on command has been issued). If not, process 540 continues to state 576 wherein a warning message that the server must be running to execute a system reset is displayed on the client computer display to the user. After the warning has been displayed, process 540 moves to end state 578 to terminate the reset process. However, if the server is running, as determined at decision state 574, process 540 proceeds to state 580.
At state 580, the Recovery Manager software 130 at the client computer 122/124 provides a microcontroller network command (based on selecting the System Reset button) and sends it to the communication layer software. Proceeding to state 582, the communication layer puts a communications protocol around the command (from state 580) and sends the encapsulated command to the server through the client modem 128, the server modem 126 and the remote interface 104. The encapsulated command is of the Request type 202 shown in FIG. 3. Process 540 then continues to a function 590 wherein the server receives the command and resets the server. Function 590 will be further described in conjunction with FIG. 9.
Moving to state 592, the response generated by the server is then sent to the remote interface 104. In one embodiment, the microcontroller (the CPU A controller 166 in this instance) performing the command at the server returns status at the time of initiation of communication with the microcontroller. At the completion of the reset operation by the CPU A controller 166, the Recovery Manager 130 sends a read status command to the CPU A controller (using states 580 and 582) to retrieve information on the results of the operation.
Proceeding to decision state 594, process 540 determines if the system reset command was successful. If so, process 540 proceeds to state 596 wherein the remote interface 104 sends the response to the server modem 126 indicating the success of the command. Alternatively, if a local connection 121 is utilized, the response is sent to the local client computer 122. However, if the system reset is not successful, as determined at decision state 594, process 540 proceeds to state 598 wherein the remote interface 104 sends the response to the server modem (or local client computer) indicating a failure of the command. At the conclusion of either state 596 or 598, process 540 proceeds to state 600 wherein the remote interface 104 sends the response back through the server modem 126 to the client modem 128. Moving to state 602, the client modem 128 sends the response back to the Recovery Manager software 130 at the remote client computer 124. Note that if the local connection 121 is being utilized, states 600 and 602 are not necessary. Proceeding to decision state 604, process 540 determines whether the command was successful. If so, process 540 continues at state 606 and displays a result window showing the success of the command on the display at the client computer 122/124. However, if the command was not successful, process 540 proceeds to state 608 wherein a result window showing failure of the command is displayed to the user. Moving to state 610, the details of the command information are available, if the user so desires, by selecting a details button. At the completion of state 606 or state 610, process 540 completes at end state 612.
Referring to FIG. 9, the server reset function 590 will now be described. Beginning at start state 630, function 590 proceeds to the BIOS POST Warmstart function 384. In the Warmstart function 384, approximately 41 subroutines are called. These include the general operations of: reset flag, DMA/timer reset, chipset initialization, CMOS test, PCI initialization, cache enable, and message display. At the completion of the BIOS POST Warmstart function 384, function 590 proceeds to state 388 where BIOS POST events are logged in the System Recorder memory 112. Proceeding to state 390, the BIOS POST performs server port initialization. Continuing at state 392, the BIOS POST initializes the Operating System related controllers (e.g., floppy disk controller, hard disk controller) and builds a multi-processor table. Advancing to state 394, the BIOS POST performs an OS boot preparation sequence. Moving to state 632, the BIOS initiates an OS boot sequence to bring the operating software to an operational state. Function 590 ends at a return state 636.
VIII. FLIGHT RECORDER FLOW
A Flight Recorder, which includes the System Recorder controller 110 and the System Recorder memory 112, provides a subsystem for recording a time-stamped history of events leading up to a failure in server system 100. The System Recorder memory 112 may also store identification of components of the server system. In one embodiment, the System Recorder 110 is the only controller which does not initiate messages to other controllers. The System Recorder 110 receives event log information from other controllers and stores the data into the System Recorder memory 112. Upon request, the System Recorder 110 can send a portion and/or the entire logged data to a requesting controller. The System Recorder 110 puts a time stamp from a real-time clock with the data that is saved.
Referring to FIGS. 10a, 10b and FIG. 1, one embodiment of a Display Flight Recorder process 670 will now be described. Process 670 begins at start state 672 and if a connection between the client computer 122/124 and the server 100 is already active, process 670 proceeds to directly to state 696. Otherwise, if a connection is not already active, process 670 proceeds to state 673 and utilizes the Recovery Manager software 130 to present a dialog window to the user on a display of the client computer 122/124 requesting information. The user is requested to enter a password for security purposes. The dialog window also has a pair of radio-buttons to select either a serial (local) connection or a modem (remote) connection. If serial is selected, the user is requested to select a COM port. If modem is selected, the user is requested to enter a telephone number to be used in dialing the server modem.
Moving to decision state 674, process 670 determines if the modem-type connection 123 was selected. The modem-type connection is generally utilized in the situation where the client computer 124 is located at a location remote from the server 100. If it is determined at decision state 674 that a modem connection is utilized, process 670 moves to state 676 wherein the client computer 124 is connected to the client modem 128. Moving to state 678, a connection is established between the client modem 128 and the server modem 126 via the communications network 127. Continuing at state 680, the server modem 126 connects with the remote interface 104. Proceeding to state 682, the remote interface 104 connects to the server 100 via the RJ-45 cable 103. Moving to state 686, the Recovery Manager software 130 at the client computer 124 dials the server modem 126 through the client modem 128, handshakes with the remote interface 104, and checks the previously entered password. Process 670 remains at state 686 until a successful communication path with the remote interface 104 is established.
Returning to decision state 674, if the local connection 121 is utilized instead of the modem connection 123, process 670 proceeds to state 688 wherein the local client computer 122 is connected with the remote interface 104. Moving to state 692, the remote interface 104 is connected with the server 100. The previously entered password (at state 673) is sent to the remote interface 104 to identify the user at the local computer 122. If the password matches the password that is stored in the server system 100, the communication path with the remote interface 104 is enabled.
After successful modem communication has been established and the password confirmed at state 686, or at the completion of connecting the remote interface to the server and checking the password at state 692, process 670 continues at state 696. At state 696, the Recovery Manager software 130 will in one embodiment display a Recovery Manager window 940, which includes a Flight Recorder icon 942 as shown in FIG. 16. A Flight Recorder window panel 944 is not displayed at this time. The user at the client computer 122/124 then selects the Flight Recorder icon 942 on the display, such as by clicking the pointer device on the icon. Moving to state 698, the Flight Recorder window panel 944 (FIG. 16) is then displayed to the user. The user selects a Download button 954 on the window panel 944 to trigger the display of the Flight Recorder operation. Note that other options in the Flight Recorder window panel 944 include a Save button 956 for saving a downloaded Flight Recorder (system log or System Recorder memory 112, FIG. 1) and a Print button 958 for printing the downloaded Flight Recorder. Continuing at state 700, a user confirmation dialog box (not shown) is then displayed on the client computer display showing a number of messages in the server system log. Moving to state 702, if the user selects the "OK" button, process 670 displays a progress window of downloaded messages. Process 670 proceeds through off page connector A 703 to state 704 on FIG. 10b.
At state 704, the Recovery Manager software 130 at the client computer 122/124 provides a microcontroller network command (based on selecting the Download Flight Recorder button 954) and sends it to the communication layer software. Proceeding to state 706, the communication layer puts a communications protocol around the command (from state 704) and sends the encapsulated command to the server through the client modem 128, the server modem 126 and the remote interface 104. The encapsulated command is of the Request type 202 shown in FIG. 3. Process 670 then continues to a function 710 wherein the server receives the command and reads the contents of the System Recorder memory 112 (FIG. 1). In one embodiment, each read request generates one response such that the Recovery Manager 130 generates multiple read requests to read the complete system log. The server generates one log response during function 710. Function 710 will be further described in conjunction with FIG. 11.
Moving to state 712, each of the responses generated by the server are then sent one at a time to the remote interface 104. Process 670 then proceeds to state 714 wherein the remote interface 104 sends each response back through the server modem 126 to the client modem 128. Alternatively, if a local connection 121 is utilized, each response is sent directly to the local client computer 122. Moving to state 716, the client modem 128 sends the response back to the Recovery Manager software 130 at the remote client computer 124. Note that if the local connection 121 is being utilized, state 716 is not necessary. Proceeding to decision state 718, process 670 determines whether the entire download of the Flight Recorder was successful by checking for an end of system log messages status. If so, process 670 continues at state 720 wherein the Recovery Manager 130 (FIG. 1) displays (and optionally stores) all messages in the Flight Recorder window panel 944 on the display at the client computer 122/124. However, if the entire download was not successful, process 670 proceeds to state 722 wherein the Recovery Manager 130 displays (and optionally stores) all messages that were received by the Recovery Manager 120 in the Flight Recorder window panel 944. At the completion of state 720 or state 722, process 670 completes at end state 724.
In one embodiment, the Flight Recorder window panel 944 includes four fields: Time Stamp 946, Severity 948, Message Source 950, and Message 952. Each message in the system log 112 includes a time stamp 946 of when the item was written to the log 112. The time stamp includes the date and the local time zone of the client computer 122/124 running the Recovery Manager 130. In one embodiment, the time stamp information is generated by a timer chip 760 (FIG. 12a). The Severity field 948 includes a severity value selected from: unknown, informational, warning, error, and severe/fatal. The Message Source field 950 includes a source selected from: microcontroller network internal, onboard diagnostics, external diagnostics, BIOS, time synchronizer, Windows.RTM., WindowsNT.RTM., NetWare, OS/2, UNIX, and VAX/VMS. The messages in the Message field 952 correspond to the data returned by the controllers on the microcontroller network 102. The controller message data is used to access a set of Message tables associated with the Recovery Manager 130 on the client computer 122/124 to generate the information displayed in the Message field 952. The Message tables include a microcontroller network (wire services) table, a BIOS table and a diagnostics table. An exemplary message from the microcontroller network table includes "temperature sensor #5 exceeds warning threshold". An exemplary message from the BIOS table includes "check video configuration against CMOS". An exemplary message from the diagnostics table includes "correctable memory error".
Referring to FIG. 11, the Read NVRAM Contents function 710 will now be described. Beginning at start state 740, function 710 proceeds to state 742 and loads a block log pointer. The System Recorder memory or NVRAM 112 (FIG. 2) has two 64K byte memory blocks. The first block is a memory block which stores ID codes of the devices installed in the network. Hence, a command addressed to the first block is typically generated by a controller responsible for updating the presence or absence of devices in the network. The second block of the memory 112 is a memory block that stores event messages in connection with events occurring in the network. Hence, controllers addressing the second block do so to add entries to the system log or to read previous entries contained in the system log. The System Recorder uses log address pointers to determine where the next new entry in the log should be placed and also to determine where the log is currently being read from. A further description of the System Recorder 110 and the NVRAM 112 is provided in U.S. patent application Ser. No. 08/942381, entitled, "BLACK BOX RECORDER FOR INFORMATION SYSTEM EVENTS".
Moving to state 744, function 710 reads the log message as addressed by the log pointer. Proceeding to state 746, function 710 returns the log message to the requestor on the microcontroller bus 160 (FIG. 2), which is the remote interface controller 200 in this situation. In one embodiment, the remote interface 104 stores the message in a memory 762 (FIG. 12c) on the RIB. Proceeding to state 748, process 710 increments the log pointer to point to the next address in the NVRAM block. Continuing at decision state 750, function 710 determines if the end of the messages in the System Recorder memory block has been reached. If not, function 710 proceeds to a normal return state 752. If the end of the messages has been reached, as determined at decision state 750, function 710 moves to a return state 754 and returns a End of Messages status. The Recovery Manager 130 utilizes this status information to stop sending requests to read the System Recorder memory 112.
IX. SYSTEM STATUS FLOW
FIGS. 12a, 12b and 12c are a detailed block diagram of the microcontroller network components showing specific inputs and outputs of the microcontrollers. An I/O Canister card 758 has fan speed detection circuitry 766 to provide fan speed information to the Canister controller 172 through a fan multiplexer 767. The CPU A controller 166 receives fan speed information from fan speed detection circuitry 764 through a fan multiplexer 765.
Referring to FIGS. 13a, 13b and FIG. 1, one embodiment of a System Status process 770 will now be described. Process 770 begins at start state 772 and if a connection between the client computer 122/124 and the server 100 is already active, process 770 proceeds to directly to state 796. Otherwise, if a connection is not already active, process 770 proceeds to state 773 and utilizes the Recovery Manager software 130 to present a dialog window to the user on a display of the client computer 122/124 requesting information. The user is requested to enter a password for security purposes. The dialog window also has a pair of radio-buttons to select either a serial (local) connection or a modem (remote) connection. If serial is selected, the user is requested to select a COM port. If modem is selected, the user is requested to enter a telephone number to be used in dialing the server modem.
Moving to decision state 774, process 770 determines if the modem-type connection 123 was selected. The modem-type connection is generally utilized in the situation where the client computer 124 is located at a location remote from the server 100. If it is determined at decision state 774 that a modem connection is utilized, process 770 moves to state 776 wherein the client computer 124 is connected to the client modem 128. Moving to state 778, a connection is established between the client modem 128 and the server modem 126 via the communications network 127. Continuing at state 780, the server modem 126 connects with the remote interface 104. Proceeding to state 782, the remote interface 104 connects to the server 100 via the RJ-45 cable 103. Moving to state 786, the Recovery Manager software 130 at the client computer 124 dials the server modem 126 through the client modem 128, handshakes with the remote interface 104, and checks the previously entered password. Process 770 remains at state 786 until a successful communication path with the remote interface 104 is established.
Returning to decision state 774, if the local connection 121 is utilized instead of the modem connection 123, process 770 proceeds to state 788 wherein the local client computer 122 is connected with the remote interface 104. Moving to state 792, the remote interface 104 is connected with the server 100. The previously entered password (at state 773) is sent to the remote interface 104 to identify the user at the local computer 122. If the password matches the password that is stored in the server system 100, the communication path with the remote interface 104 is enabled.
After successful modem communication has been established and the password confirmed at state 786, or at the completion of connecting the remote interface to the server and checking the password at state 792, process 770 continues at state 796. At state 796, the Recovery Manager software 130 will in one embodiment display a Recovery Manager window 960, which includes a System Status icon 970 as shown in FIG. 17. A System Status window panel 962 is not displayed at this time. The user at the client computer 122/124 then selects the System Status icon 970 on the display, such as by clicking the pointer device on the icon. Moving to state 798, the System Status window panel 962 (FIG. 17) is then displayed to the user. The user selects one of a multiple set of component icons 972-984 on the window panel 962 to initiate a System Status operation. In one embodiment, icon 972 is for Power Supplies, icon 974 is for Temperatures, icon 976 is for Fans, icon 978 is for Processor, icon 980 is for I/O Canisters, icon 982 is for Serial Numbers and icon 984 is for Revisions. When the user selects one of the icons 972-984, the Recovery Manager 130 displays a component window panel to the user, such as exemplary Fans window panel 994 (FIG. 18) if the user selected the Fans icon 976.
In one embodiment, the exemplary Fans window panel 994 (FIG. 18) includes several fields 985-991: field 985 is for Fan Location, field 986 is for Fan Number within the Location, field 987 is for Fan Speed (rpm, as detected by the microcontrollers 166 and 172 (FIG. 12)), field 988 is for Fan Speed Control (high or low), field 989 is for Fault Indicator LED (on or off), field 990 is for Fan Fault (yes or no), and field 991 is for Fan Low-speed Fault Threshold Speed (rpm). Note that this exemplary Fans window panel 994 includes a Refresh button 992 which triggers a retrieval of new values for the fields of the panel.
If the user selects a Canister A icon 1000 in the Recovery Manager window panel 960, the Recovery Manager 130 displays an exemplary Fans detail window panel 1002 (FIG. 19). This exemplary panel 1002 provides status information for the fans of the selected Canister A, which in this embodiment includes a status box 1004 for a Fan 1 and a status box 1006 for Fan 2 along with a Canister Present indicator 1008 and a Fault Indicator Led box 1010. These status items 1004-1010 are refreshed (new status information is retrieved) if the user selects a Refresh button 1012. A Fan Low-speed Fault Threshold Speed entry box 1020 and a Fan Speed Control radio button box 1022 allow the user to enter new values if it desired to change the current settings. An Update operation to change the values of the settings is initiated if the user selects the Update button 1024.
Continuing in FIG. 13a at decision state 799, process 770 determines if the Refresh Status operation is to be performed, if for example, the user selected a Refresh button on one of the System status windows. If so, process 770 proceeds to state 800 and initiates the Refresh operation to retrieve new status information for display to the user. If the Refresh operation is not selected, as determined at decision state 799, process 770 advances to decision state 801 to determine if the Update operation is to be performed, if for example, the user selected a Update button on one of the System status windows. If so, process 770 proceeds to state 802 and initiates the Update operation to update item settings that the user desires to change. At the completion of either state 800 or state 802, or if the user selects another status option (e.g., Help), process 670 proceeds through off page connector A 803 to state 804 on FIG. 13b.
At state 804, the Recovery Manager software 130 at the client computer 122/124 provides a microcontroller network command (based on selecting one of System Status operations (e.g., Update, Refresh)) and sends it to the communication layer software. Proceeding to state 806, the communication layer puts a communications protocol around the command (from state 804) and sends the encapsulated command to the server through the client modem 128, the server modem 126 and the remote interface 104. The encapsulated command is of the Request type 202 shown in FIG. 3. Process 770 then continues to a function 810 wherein the server receives the command and retrieves or updates the selected status information for the selected item(s), e.g., Fans. In one embodiment, for example, each Refresh request generates one response such that the Recovery Manager 130 generates multiple Refresh requests to retrieve the complete set of status information. Function 810 will be further described in conjunction with FIG. 14.
Moving to state 812, each of the responses generated by the server are then sent one at a time to the remote interface 104, Process 770 then proceeds to state 814 wherein the remote interface 104 sends each response back through the server modem 126 to the client modem 128. Alternatively, if a local connection 121 is utilized, each response is sent directly to the local client computer 122. Moving to state 822, the client modem 128 sends the response back to the Recovery Manager software 130 at the remote client computer 124. Proceeding to decision state 824, process 770 determines whether the executed command was a Retrieve (Refresh) or Update command. If the command was a Retrieve, process 770 moves to decision state 826 to determine if the Retrieve operation was successful. If so, process 770 continues to state 828 wherein the Recovery Manager 130 (FIG. 1) displays the new system status information in a System Status window panel (such as window panel 994 (FIG. 18) or window panel 1002 (FIG. 19)) on the display at the client computer 122/124. However, if the Refresh operation was not successful, process 770 proceeds to state 830 wherein the Recovery Manager 130 shows new status information for the items that the new status information has been successfully received (if any).
Returning to decision state 824, if the command was an Update, process 770 moves to decision state 834 to determine if the Update operation was successful. If so, process 770 continues to state 836 wherein the Recovery Manager 130 (FIG. 1) displays an Update Successful indication in the appropriate Status window. However, if the Update operation was not successful, process 770 proceeds to state 838 wherein the Recovery Manager 130 displays an Update Failure indication in the appropriate Status window. Moving to state 840, the details of the command information are available, if the user so desires, by selecting a Details button (not shown). At the completion of any of states 828, 830, 836 or 840, process 770 completes at end state 842.
Referring to FIG. 14, the Server System Status function 810 will now be described. Beginning at start state 870, function 810 proceeds to state 872 wherein each microcontroller on the microcontroller network bus 160 (FIG. 2) checks to see if the address field of the system command received from the recovery manager 130 (FIG. 1) at the client computer matches that of the microcontroller. Continuing at state 874, the addressed microcontroller executes a command, e.g., retrieve data or update data. Continuing at state 876 the addressed microcontroller sends a response message back on the microcontroller bus 160 to the controller that initiated the command, which is the remote interface controller 200 (FIG. 2) in this situation. Moving to decision state 878, function 810 determines whether additional items are selected for retrieval or update. If so, function 810 moves to state 880 to access the next command and then moves back to state 872 wherein each microcontroller again checks to see if it is addressed. The single addressed microcontroller performs states 872, 874 and 876. If there are no more items selected for retrieval or update, as determined at decision state 878, function 810 proceeds to a return state 882 where function 810 completes.
States 878, 880 and 882 are performed by the Recovery Manager 130 at the client computer 122/124. For example, if the user wanted system status on all the fans by selecting the Fan icon 976 (FIG. 18), the Recovery Manager 130 generates one command for each of a selected group of microcontrollers for retrieving fan information. Thus, a command to read fan information from CPU A controller 166 (FIG. 2) is sent out and a response received, followed by a command to and response from Canister A controller 172, and so on through Canister B controller 174, Canister C controller 176 and Canister D controller 178.
In one embodiment, the System Status windows provide the following status information:
System Status: Power Supplies
This window displays power supply status information. To obtain current information, click Refresh. This information includes:
System Status: Temperature
This window displays information about the operational temperatures of the server. To obtain current temperature information, click Refresh. To apply any changes made in this window, click Update.
System Status: Fans
This window displays server and group fan status information. To obtain current status information, click Refresh. The information that appears in this window includes:
System Board Fans
This window displays information about the status of the system board fans. To obtain current information, click Refresh. To apply any changes made in this window, click Update.
Group X Fans
This window displays information about the status of the fans in the selected group. To obtain current information, click Refresh. To apply any changes made in this window, click Update.
Canister X Fans
This window displays information about the status of the fans in the selected canister. To obtain current information, click Refresh. To apply any changes made in this window, click Update.
System Status: Processor
This window displays processor status information. To obtain current information, click Refresh. This information includes:
CPU X Status:
This window displays status information for the selected CPU. To obtain current information, click Refresh. To apply any changes made in this window, click Update.
System Status: I/O Groups
This window displays I/O group status information. To obtain current information, click Refresh. This information includes:
System Status: I/O Canisters
This window displays I/O canister status information. To obtain current information, click Refresh. This information includes:
System Status: Serial Numbers
This window lists the serial numbers of the system board, backplane, canisters, power supplies, and remote interface. To obtain current information, click Refresh.
System Status: Revisions
This window displays server component revision information for the backplane, system board, power supplies, I/O canisters or I/O groups, system interface and remote interface. To obtain current information, click Refresh.
While the above detailed description has shown, described, and pointed out the fundamental novel features of the invention as applied to various embodiments, it will be understood that various omissions and substitutions and changes in the form and details of the system illustrated may be made by those skilled in the art, without departing from the intent of the invention.
Appendix A
Incorporation by Reference of Commonly Owned Applications
The following patent applications, commonly owned and filed on the same day as the present application are hereby incorporated herein in their entirety by reference thereto:
Appendix B
Provisional Patent Application
6391-709:
Title: REMOTE SOFTWARE FOR MONITORING AND MANAGING ENVIRONMENTAL MANAGEMENT SYSTEM
Invs: Ahmad Nouri
THe following documents are attached and form part of this disclosure:
1. Maestro Recovery Manager Analysis--Problem Statement, pp. 1-10.
2. Remote Interface Board Specification, Revision 2 13-000072-01, Jun. 21, 1996, pp. 1-11.
Multiple Node Service Processor Network
A means is provided by which individual components of a system are monitored and controlled through a set of independent, programmable microcontrollers interconnected through a network. Further means are provided to allow access to the microcontrollers and the interconnecting network by software running on the host processor.
Fly-by-wire
A means is provided by which all indicators, push buttons and other physical control means are actuated via the multiple node service processor network. No indicators, push buttons or other physical control means are physically connected to the device which they control, but are connected to a microcontroller, which then actuates the control or provides the information being monitored.
Self-Managing Intelligence
A means is provided by which devices are managed by the microcontrollers in a multiple node service processor network by software running on one or more microcontrollers, communicating via the interconnecting network. Management of these devices is done entirely by the service processor network, without action or intervention by system software or an external agent.
Flight Recorder
A means is provided for recording system events in a non-volatile memory, which may be examined by external agents. Such memory may be examined by agents external to the network interconnecting the microcontrollers.
Replicated components: no single point of failure
A means is provided by which no single component failure renders the monitoring and control capability of the system inoperable.
Extension by serial or modem gateway
A means is provided allowing an external agent to communicate with the microcontrollers by extending the interconnecting network beyond the physical system.
Software means are provided to monitor and/or control a system using a remote agent. Means are provided for implementing an extension to the interconnecting network, converting protocols between media and communicating with and directing the microcontroller, and the state managed by those microcontrollers.
The following provisional patent applications, commonly owned and filed on the same day as the present application, are related to the present application and are incorporated by reference:
COMPUTER SYSTEM HARDWARE INFRASTRUCTURE FOR HOT PLUGGING MULTI-FUNCTION PCI CARDS WITH EMBEDDED BRIDGES (6391-704); invented by:
Don Agneta
Stephen E. J. Papa
Michael Henderson
Dennis H. Smith
Carlton G. Amdahl
Walter A. Wallach
COMPUTER SYSTEM HARDWARE INFRASTRUCTURE FOR HOT PLUGGING SINGLE AND MULTI-FUNCTION PC CARDS WITHOUT EMBEDDED BRIDGES (6391-705); invented by:
Don Agneta
Stephen E. J. Papa
Michael Henderson
Dennis H. Smith
Carlton G. Amdahl
Walter A. Wallach
ISOLATED INTERRUPT STRUCTURE FOR INPUT/OUTPUT ARCHITECTURE (6391-706); invented by:
Dennis H. Smith
Stephen E. J. Papa
THREE BUS SERVER ARCHITECTURE WITH A LEGACY PCI BUS AND MIRRORED I/O PCI BUSES (6391-707); invented by:
Dennis H. Smith
Cariton G. Amdahl
Don Agneta
HOT PLUG SOFTWARE ARCHITECTURE FOR OFF THE SHELF OPERATING SYSTEMS (6391-708); invented by:
Walter A. Wallach
Mehrdad Khalili
Mallikarunan Mahalingarn
John Reed
REMOTE SOFTWARE FOR MONITORING AND MANAGING ENVIRONMENTAL MANAGEMENT SYSTEM (6391-709); invented by:
Ahmad Nouri
REMOTE ACCESS AND CONTROL OF ENVIRONMENTAL MANAGEMENT SYSTEM (6391-710); invented by:
Karl Johnson
Tahir Sheik
HIGH PERFORMANCE NETWORK SERVER SYSTEM MANAGEMENT INTERFACE (6391-711); invented by:
Srikumar Chari
Kenneth Bright
Bruno Sartirana
CLUSTERING OF COMPUTER SYSTEMS USING UNIFORM OBJECT NAMING AND DISTRIBUTED SOFTWARE FOR LOCATING OBJECTS (6391-712); invented by:
Walter A. Wallach
Bruce Findley
MEANS FOR ALLOWING TWO OR MORE NETWORK INTERFACE CONTROLLER CARDS TO APPEAR AS ONE CARD TO AN OPERATING SYSTEM (6391-713); invented by:
Walter A. Wallach
Mallikarunan Mahalingam
HARWARE AND SOFTWARE ARCHITECTURE FOR INTER-CONNECTING AN ENVIRONMENTAL MANAGEMENT SYSTEM WITH A REMOTE INTERFACE (6391-714); invented by:
Karl Johnson
Walter A. Wallach
Dennis H. Smith
Carl G. Amdahl
SELF MANAGEMENT PROTOCOL FOR A FLY-BY-WIRE SERVICE PROCESSOR (6391-715); invented by:
Karl Johnson
Walter A. Wallach
Dennis H. Smith
Carl G. Amdahl
Problem Statement
Introduction
Maestro Recovery Manager(MRM) is a software which locally or remotely manage a Raptor when a server is down or up, operating system died, LAN communication failed, or other server components failed.
User will be able to manage the server in very simple, usable, and friendly GUI environment. MRM use modem for remote and serial communication port for local to communicate with server for diagnostic and recovery.
Primary role of remote management is diagnosing and restoring service as quickly as possible in case of a service failure.
System administrator, LAN administrator in customer shop and NetFrame Technical support will be primary user for the system.
Requirement Sources
MRM requirements comes from the following
1 Focus Group (Customer Support and Training)
2 User Walkthrough held by MRM team and Customer Support in December 1996
3 Down System Management Road map (96) This road map is preliminary road map combined with Up System Management road map.
4 MRM Road Map 97-98 This Road Map presented to Engineering Council Meeting on Mar. 10, 1997.
5 Raptor System, A Bird's Eye View.
6 Raptor Wire Service Architecture
The following requirements have been identified for MRM
Support Remote Management for Diagnostic and Recovery
Remote Management cover remote access to the Raptor Out Of Band management features. Remote Management will use Out of Band, Control Diagnostic and Monitor Subsystem (CDM) remote management to cover the other high value added remote management functions. Primary role of remote management is diagnosing and restoring service as quickly as possible in case of service failure.
Support Remote Management . . . (continue)
The control of Raptor is completely "Fly By Wire"--i.e. no physical switch directly controls any function and no indicator is directly controlled by system hardware. All such functions referred to as "Out of Band " functions are controlled through a CDM. CDM basic functions are available so long as A/C power is available at the input to any of the power supplies.
CDM Subsystem supervises or monitors the following system features.
Power supplies--Presence, status, A/C good, Power on/off and output voltage.
Environment--Ambient and exhaust temperatures, Fan speed, speed control, Fan fault and overtemp indicators.
Processor--CPU Presence, Power OK, Overtemp and Fault, NMI control, System reset, Memory type/location and Bus/Core speed ratio.
I/O--I/O canister insertion/removal and status indicator, PCI card presence, PCI card power and smart I/O processor Out Of Band control.
Historical--Log of all events, Character mode screen image, and Serial number
Support for Object Oriented Graphic User Interface
OO-GUI is graphic user interface with the following characteristic.
User task oriented
It uses tasks which user familiar and daily working with. User does not need to learn the tasks.
User objects
It uses objects which user working with during her or his daily work.
Simplicity and useablity
It is very simple to use and does not need long learning period.
Point and click with context sensitive help
Context sensitive help and point and click will help user to be very productive and get any information he needs on specific object or field or subject.
Drag and drop
Drag and Drop capability works with user object very well to accomplish the tasks.
Release Requirements (ARM V2.0, 4Q96)
Maestro Recovery Manager (MRM)will support the following features locally through serial port and Wire Service Remote Interface card on the Raptor16.
MRM provide user friendly GUI with point and click capability to perform the following tasks which reviewed and accepted by the Focus Group for 4Q96 release.
Power On/Off
MRM support Power On/Off the server.
User can do this task by right mouse click on the server object in the screen and see the result.
Display Flight Recorder.
While the server is working, Wire Service record all the server information in the 64K NVRAM. After the server failed, MRM will display the system log recorded in the NVRAM. User can evaluate the information and find the cause for the server failure. This can be done by right mouse click on the Flight Recorder object in the screen.
System Reset
MRM support rebooting the server by right mouse click on the server object in the screen. This is warm reboot of the server and works as pushing the "reset" button on the server.
Save
MRM will support saving Flight Recorder data, so user can send the file to the technical support for further diagnostic and recovery. It also can save the response for any Wire Service command failure.
On Line help
MRM will support online help contains overview, Getting Started, MRM tasks, Diagnostic and Recovery, and BIOS help.
BO back plane support
MRM will support the server with BO back plane. Server with BO back plane display wrong time stamp. MRM uses NetWare 4.11 Operating system time stamp to display correct time stamp.
Release Requirements MRM V2.1, 1Q97)
Maestro Recovery Manager (MRM) will support Raptor16 Phase 2 for next release as follow. This release will delivered to customer by NetFrame Customer Support on CD.
MRM V2.1
MRM V 2.1 will support the MRM V2.0 plus the following new features for next release.
User Walkthrough Requirements held on Dec. 17, 1996
Recovery and Diagnostic help.
This help enable the user to display help based on message source or severity (fatal error, error, warning,). In each case the help inform the user the cause for the error and what steps to take to solve the problem.
C0/E18 back plane support
New C0 back plane Wire Service, Diagnostic, and BIOS message structure
Release Requirements (MRM V2.2, 2Q97)
MRM V2.2 for Raptor 16
MRM V2.2 will support MRM V2.1 plus the following new features.
Remote connection via modem
MRM supports remote connection to an NF9000-16 via an external modem. MRM needs one external modem for client side and one external modem for the server side. The client modem can be installed and set up via the Windows NT/95 standard control panel/Modems installation. The server side modem has to be set up and connected to the server. Details of installation and setup for the modem are provided in the
NF9000 Maestro Recovery Manager Installation Guide.
MRM does not support internal modems.
The following external Hayes compatible modems have been tested and worked with MRM.
Client Modem
US Robotics Sportster 33.6 Fax modem
ZOOM fax MODEM V.34X 33.6
Server Modem
ZOOM fax MODEM V.34X 33.6
System Status
MRM supports retrieve and update of the system status components.
System status comprised of the following components.
Power Supplies
Temperatures
Fans
Processors
Canisters
Serial Numbers
Revisions
Context-sensitive Help
All elements in the window such as icon, entry field, push button, and radio button have context-sensitive help. This help contains the following type.
What's this
Help push button.
F1 Key
Print
MRM supports printing of flight recorder based on all messages, warning & errors, and errors with one type of font.
Password
Wire Service password is originally set by Manufacturing to "NETFRAME" (case sensitive) for every NF9000-16 server. MRM provides a password changing mechanism for the Wire Service system.
For security purposes, MRM only allows the password to be changed via the local serial port connection and not via the remote connection
Support B0/E18 on NT4.0 server
MRM supports B0/E18 configurations by utilizing a time stamp software component which resides on the NT4.0 server.
Installation instructions for the time stamp are provided in the NTReadMe file on a floppy disk packaged with MRM.
MRM requires the NetFRAME NT Value Add software to operate.
The NetFRAME NT Value Add software will automatically install the time stamp for you. If you have not installed NetFRAME NT Value Add, then you need to install the time stamp provided for you on the NTSup floppy disk.
Support for InstallShield
InstallShield setup software is used to install MRM on the client workstation.
Delivery
MRM package contains the following.
NF9000 Maestro Recovery Manager CD release.
This CD contains MRM software and documentation.
Two support floppy disks for NF9000-16 B0 back plane for NT and NetWare.
Boxes contain above items, Remote Interface Card, adapter, cables, and documentation.
Dependency
MRM version 2.2 depends on the following items:
Remote Interface chip provided by Wire Service(Firm Ware) department.
Remote Interface card provided by Hardware Engineering department.
Remote Interface boxes, cables, and power adapters provided by Manufacturing.
Release Requirements (MRM V2.2, 2Q97)
MRM V2.2 for Raptor 8
MRM V2.2 for Raptor 8 has the same features as MRM v2.2 for Raptor16 with the following different.
Support for C0 back plane and F18 BIOS
System Status
The following components of System Status are different from MRM V2.2 for Raptor16.
Power Supplies
Fans
I/O Groups
Serial Numbers
Revisions
Delivery
MRM package contains the following.
NF9000 Maestro Recovery Manager CD release.
Boxes contain above items, Remote Interface Card, adapter, cables, and documentation.
Claims
Post-issuance certificates present
The text shown below may not reflect later post-issuance changes.
What is claimed is:
1. A system for retrieving or updating system status for a computer, the system comprising: a first computer; a microcontroller configured to provide a retrieve or update system status signal to the first computer, wherein the signal causes retrieval of status information from the first computer or an update of an item setting of the first computer; a remote interface connected to the microcontroller, wherein the remote interface is configured to provide external access to the first computer; and a second computer connected to the first computer via the remote interface and communicating a retrieve or update system status command to the microcontroller.
2. The system defined in claim 1, wherein the remote interface includes an external port for connection to the second computer.
3. The system defined in claim 1, wherein the second computer is at the same location as the first computer.
4. The system defined in claim 1, wherein the second computer is at a location remote to the first computer.
5. The system defined in claim 4, additionally comprising a pair of modems, wherein a first modem connects to the first computer via the remote interface and a second modem connects to the second computer, and wherein the first modem is in data communication with the second modem.
6. The system defined in claim 5, wherein each modem further connects to the public switched telephone network.
7. The system defined in claim 5, wherein each modem further connects to a cable network.
8. The system defined in claim 5, wherein each modem facilitates connection to a satellite.
9. The system defined in claim 1, wherein the remote interface includes a remote interface microcontroller that connects via a bus to the microcontroller.
10. The system defined in claim 1, wherein the remote interface is responsive to a command sent from the second computer to retrieve or update system status from the microcontroller.
11. The system defined in claim 1, wherein the first computer generates status information.
12. The system defined in claim 11, wherein the second computer displays the status information.
13. The system defined in claim 1, wherein the remote interface includes a power source which is independent of a power source for the first computer.
14. The system defined in claim 13, wherein the independent power source included with the remote interface provides power to the first computer when the first power supply fails.
15. The system defined in claim 1, wherein the remote interface is directly connected to and proximately located to the first computer.
16. A system for updating system status for a computer, the system comprising: a first computer comprising: an environmental circuit; and a microcontroller connected to the environmental circuit, wherein the environmental circuit receives item settings; a remote interface connected to the microcontroller; and a second computer in data communication with the first computer via the remote interface, the second computer capable of communicating an update system status command to the microcontroller.
17. The system defined in claim 16, wherein the remote interface is connected to the microcontroller by a microcontroller bus.
18. The system defined in claim 16, wherein the update system status command includes the item settings.
19. The system defined in claim 16, wherein the item settings include a threshold temperature for the first computer.
20. The system defined in claim 16, wherein the item settings include a fan threshold speed for the first computer.
21. A system for retrieving system status for a computer, the system comprising: a first computer comprising: an environmental circuit; and a microcontroller connected to the environmental circuit, wherein the environmental circuit obtains status information; a remote interface connected to the microcontroller; and a second computer in data communication with the first computer via the remote interface, the second computer capable of communicating a retrieve system status command to the microcontroller.
22. The system defined in claim 21, wherein the remote interface is connected to the microcontroller by a microcontroller bus.
23. The system defined in claim 21, wherein the status information comprises a temperature for the first computer.
24. The system defined in claim 21, wherein the status information comprises a fan parameter for the first computer.
25. A microcontroller system for updating the system settings of a first computer, the microcontroller system comprising: a microcontroller bus; and a plurality of microcontrollers that are interconnected by the microcontroller bus and wherein the microcontrollers manage the system settings of the first computer, and wherein a selected one of the microcontrollers communicates an update command to at least one of the other microcontrollers and supplies at least one item setting for updating the system settings.
26. The system defined in claim 25, wherein the item setting is provided by a second computer.
27. The system defined in claim 26, wherein the second computer utilizes a graphical user interface to obtain at least a portion of the item setting from a user.
28. A microcontroller system for retrieving the system status of a first computer having an environmental circuit, the microcontroller system comprising: a microcontroller bus; and a plurality of microcontrollers that are interconnected by the microcontroller bus and wherein the microcontrollers manage the system status of the first computer, and wherein a selected one of the microcontrollers communicates a retrieve system status command to at least one of the other microcontrollers and retrieves system status information from the environmental circuit.
29. The system defined in claim 28, wherein the system status is provided to a second computer.
30. The system defined in claim 29, wherein the second computer utilizes a graphical user interface to display at least a portion of the system status.
31. A system for updating and retrieving system status information of a first computer, the system comprising: a microcontroller bus; a plurality of microcontrollers that are interconnected by the microcontroller bus, wherein at least one of the plurality of microcontrollers is configured to cause retrieval of status information or an update of an item setting; and a recovery manager program executing on a second computer in data communication with the microcontroller bus, the recovery manager program configured to manage system status information of the first computer.
32. The system of claim 31, wherein the recovery manager program obtains, via a graphical user interface, item settings utilized in updating the system status information in the first computer.
33. The system of claim 31, wherein the recovery manager program displays the system status information retrieved from the first computer.
34. The system of claim 31, wherein one of the microcontrollers is a remote interface.
35. The system of claim 34, wherein the remote interface provides a data communication path between the microcontroller bus and the recovery manager program.
Patent Citations (267)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4057847 | 1977-11-01 | Lowell et al. | |
| US4100597 | 1978-07-01 | Fleming et al. | |
| US4449182 | 1984-05-01 | Rubinson et al. | |
| US4672535 | 1987-06-01 | Katzman et al. | |
| US4692918 | 1987-09-01 | Elliott et al. | |
| US4695946 | 1987-09-01 | Andreasen et al. | |
| US4707803 | 1987-11-01 | Anthony, Jr. et al. | |
| US4769764 | 1988-09-01 | Levanon | |
| US4774502 | 1988-09-01 | Kimura | |
| US4821180 | 1989-04-01 | Gerety et al. | |
| US4835737 | 1989-05-01 | Herrig et al. | |
| US4894792 | 1990-01-01 | Mitchell et al. | |
| US4949245 | 1990-08-01 | Martin et al. | |
| US4999787 | 1991-03-01 | McNally et al. | |
| US5006961 | 1991-04-01 | Monico | |
| US5007431 | 1991-04-01 | Donehoo, III | |
| US5033048 | 1991-07-01 | Pierce et al. | |
| US5051720 | 1991-09-01 | Kittirutsunetorn | |
| US5073932 | 1991-12-01 | Yossifor et al. | |
| US5103391 | 1992-04-01 | Barrett | |
| US5118970 | 1992-06-01 | Olson et al. | |
| US5121500 | 1992-06-01 | Arlington et al. | |
| US5123017 | 1992-06-01 | Simpkins et al. | |
| US5136708 | 1992-08-01 | Lapourtre et al. | |
| US5138619 | 1992-08-01 | Fasang et al. | |
| US5157663 | 1992-10-01 | Major et al. | |
| US5210855 | 1993-05-01 | Bartol | |
| US5245615 | 1993-09-01 | Treu | |
| US5247683 | 1993-09-01 | Holmes et al. | |
| US5253348 | 1993-10-01 | Scalise | |
| US5261094 | 1993-11-01 | Everson et al. | |
| US5266838 | 1993-11-01 | Gerner | |
| US5269011 | 1993-12-01 | Yanai et al. | |
| US5272382 | 1993-12-01 | Heald et al. | |
| US5272584 | 1993-12-01 | Austruy et al. | |
| US5276863 | 1994-01-01 | Heider | |
| US5277615 | 1994-01-01 | Hastings et al. | |
| US5280621 | 1994-01-01 | Barnes et al. | |
| US5283905 | 1994-02-01 | Saadeh et al. | |
| US5307354 | 1994-04-01 | Cramer et al. | |
| US5311397 | 1994-05-01 | Harshberger et al. | |
| US5311451 | 1994-05-01 | Barrett | |
| US5317693 | 1994-05-01 | Cuenod et al. | |
| US5329625 | 1994-07-01 | Kannan et al. | |
| US5337413 | 1994-08-01 | Lui et al. | |
| US5351276 | 1994-09-01 | Doll, Jr. et al. | |
| US5367670 | 1994-11-01 | Ward et al. | |
| US5379184 | 1995-01-01 | Barraza et al. | |
| US5379409 | 1995-01-01 | Ishikawa | |
| US5386567 | 1995-01-01 | Lien et al. | |
| US5388267 | 1995-02-01 | Chan et al. | |
| US5402431 | 1995-03-01 | Saadeh et al. | |
| US5404494 | 1995-04-01 | Garney | |
| US5423025 | 1995-06-01 | Goldman et al. | |
| US5430717 | 1995-07-01 | Fowler et al. | |
| US5430845 | 1995-07-01 | Rimmer et al. | |
| US5432715 | 1995-07-01 | Shigematsu et al. | |
| US5432946 | 1995-07-01 | Allard et al. | |
| US5438678 | 1995-08-01 | Smith | |
| US5440748 | 1995-08-01 | Sekine et al. | |
| US5448723 | 1995-09-01 | Rowett | |
| US5455933 | 1995-10-01 | Schieve et al. | |
| US5460441 | 1995-10-01 | Hastings et al. | |
| US5463766 | 1995-10-01 | Schieve et al. | |
| US5471617 | 1995-11-01 | Farrand et al. | |
| US5473499 | 1995-12-01 | Weir | |
| US5483419 | 1996-01-01 | Kaczeus, Sr. et al. | |
| US5485550 | 1996-01-01 | Dalton | |
| US5485607 | 1996-01-01 | Lomet et al. | |
| US5487148 | 1996-01-01 | Komori et al. | |
| US5491791 | 1996-02-01 | Glowny et al. | |
| US5493574 | 1996-02-01 | McKinley | |
| US5493666 | 1996-02-01 | Fitch | |
| US5513314 | 1996-04-01 | Kandasamy et al. | |
| US5513339 | 1996-04-01 | Agrawal et al. | |
| US5517646 | 1996-05-01 | Piccirillo et al. | |
| US5526289 | 1996-06-01 | Dinh et al. | |
| US5528409 | 1996-06-01 | Cucci et al. | |
| US5533193 | 1996-07-01 | Roscoe | |
| US5535326 | 1996-07-01 | Baskey et al. | |
| US5542055 | 1996-07-01 | Amini et al. | |
| US5546272 | 1996-08-01 | Moss et al. | |
| US5548712 | 1996-08-01 | Larson et al. | |
| US5555510 | 1996-09-01 | Verseput et al. | |
| US5559764 | 1996-09-01 | Chen et al. | |
| US5559958 | 1996-09-01 | Farrand et al. | |
| US5559965 | 1996-09-01 | Oztaskin et al. | |
| US5560022 | 1996-09-01 | Dunstan et al. | |
| US5564024 | 1996-10-01 | Pemberton | |
| US5566299 | 1996-10-01 | Billings et al. | |
| US5566339 | 1996-10-01 | Perholtz et al. | |
| US5568610 | 1996-10-01 | Brown | |
| US5568619 | 1996-10-01 | Blackledge et al. | |
| US5572403 | 1996-11-01 | Mills | |
| US5577205 | 1996-11-01 | Hwang et al. | |
| US5579487 | 1996-11-01 | Meyerson et al. | |
| US5579491 | 1996-11-01 | Jeffries et al. | |
| US5581712 | 1996-12-01 | Herrman | |
| US5581714 | 1996-12-01 | Amini et al. | |
| US5584030 | 1996-12-01 | Husak et al. | |
| US5588144 | 1996-12-01 | Inoue et al. | |
| US5592611 | 1997-01-01 | Midgely et al. | |
| US5596711 | 1997-01-01 | Burckhartt et al. | |
| US5598407 | 1997-01-01 | Bud et al. | |
| US5602758 | 1997-02-01 | Lincoln et al. | |
| US5604873 | 1997-02-01 | Fite et al. | |
| US5606672 | 1997-02-01 | Wade | |
| US5608876 | 1997-03-01 | Cohen et al. | |
| US5615207 | 1997-03-01 | Gephardt et al. | |
| US5621159 | 1997-04-01 | Brown et al. | |
| US5621892 | 1997-04-01 | Cook | |
| US5622221 | 1997-04-01 | Genga, Jr. et al. | |
| US5625238 | 1997-04-01 | Ady et al. | |
| US5627962 | 1997-05-01 | Goodrum et al. | |
| US5628028 | 1997-05-01 | Michelson | |
| US5630076 | 1997-05-01 | Saulpaugh et al. | |
| US5631847 | 1997-05-01 | Kikinis | |
| US5632021 | 1997-05-01 | Jennings et al. | |
| US5638289 | 1997-06-01 | Yamada et al. | |
| US5644470 | 1997-07-01 | Benedict et al. | |
| US5644731 | 1997-07-01 | Liencres et al. | |
| US5651006 | 1997-07-01 | Fujino et al. | |
| US5652832 | 1997-07-01 | Kane et al. | |
| US5652839 | 1997-07-01 | Giorgio et al. | |
| US5652892 | 1997-07-01 | Ugajin | |
| US5652908 | 1997-07-01 | Douglas | |
| US5655081 | 1997-08-01 | Bonnell et al. | |
| US5655083 | 1997-08-01 | Bagley | |
| US5655148 | 1997-08-01 | Richman et al. | |
| US5659682 | 1997-08-01 | Devarakonda et al. | |
| US5664118 | 1997-09-01 | Nishigaki et al. | |
| US5664119 | 1997-09-01 | Jeffries et al. | |
| US5666538 | 1997-09-01 | DeNicola | |
| US5668943 | 1997-09-01 | Attanasio et al. | |
| US5668992 | 1997-09-01 | Hammer et al. | |
| US5669009 | 1997-09-01 | Buktenica et al. | |
| US5671371 | 1997-09-01 | Kondo et al. | |
| US5675723 | 1997-10-01 | Ekrot et al. | |
| US5680288 | 1997-10-01 | Carey et al. | |
| US5684671 | 1997-11-01 | Hobbs et al. | |
| US5689637 | 1997-11-01 | Johnson et al. | |
| US5696895 | 1997-12-01 | Hemphill et al. | |
| US5696899 | 1997-12-01 | Kalwitz | |
| US5696949 | 1997-12-01 | Young | |
| US5696970 | 1997-12-01 | Sandage et al. | |
| US5704031 | 1997-12-01 | Mikami et al. | |
| US5708775 | 1998-01-01 | Nakamura | |
| US5708776 | 1998-01-01 | Kikinis | |
| US5712754 | 1998-01-01 | Sides et al. | |
| US5715456 | 1998-02-01 | Bennett et al. | |
| US5717570 | 1998-02-01 | Kikinis | |
| US5724529 | 1998-03-01 | Smith et al. | |
| US5726506 | 1998-03-01 | Wood | |
| US5727207 | 1998-03-01 | Gates et al. | |
| US5732266 | 1998-03-01 | Moore et al. | |
| US5737708 | 1998-04-01 | Grob et al. | |
| US5740378 | 1998-04-01 | Rehl et al. | |
| US5742514 | 1998-04-01 | Bonola | |
| US5742833 | 1998-04-01 | Dea et al. | |
| US5747889 | 1998-05-01 | Raynham et al. | |
| US5748426 | 1998-05-01 | Bedingfield et al. | |
| US5752164 | 1998-05-01 | Jones | |
| US5754797 | 1998-05-01 | Takahashi | |
| US5758165 | 1998-05-01 | Shuff | |
| US5758352 | 1998-05-01 | Reynolds et al. | |
| US5761033 | 1998-06-01 | Wilhelm | |
| US5761045 | 1998-06-01 | Olson et al. | |
| US5761085 | 1998-11-01 | Giorgio | |
| US5761462 | 1998-06-01 | Neal et al. | |
| US5761707 | 1998-06-01 | Aiken et al. | |
| US5764968 | 1998-06-01 | Ninomiya | |
| US5765008 | 1998-06-01 | Desai et al. | |
| US5765198 | 1998-06-01 | McCrocklin et al. | |
| US5767844 | 1998-06-01 | Stoye | |
| US5768541 | 1998-06-01 | Pan-Ratzlaff | |
| US5768542 | 1998-06-01 | Enstrom et al. | |
| US5771343 | 1998-06-01 | Hafner et al. | |
| US5774645 | 1998-06-01 | Beaujard et al. | |
| US5774741 | 1998-06-01 | Choi | |
| US5777897 | 1998-07-01 | Giorgio | |
| US5778197 | 1998-07-01 | Dunham | |
| US5781703 | 1998-07-01 | Desai et al. | |
| US5781716 | 1998-07-01 | Hemphill et al. | |
| US5781744 | 1998-07-01 | Johnson et al. | |
| US5781767 | 1998-07-01 | Inoue et al. | |
| US5781798 | 1998-07-01 | Beatty et al. | |
| US5784555 | 1998-07-01 | Stone | |
| US5784576 | 1998-07-01 | Guthrie et al. | |
| US5787019 | 1998-07-01 | Knight et al. | |
| US5787459 | 1998-07-01 | Stallmo et al. | |
| US5787491 | 1998-07-01 | Merkin et al. | |
| US5790775 | 1998-08-01 | Marks et al. | |
| US5790831 | 1998-08-01 | Lin et al. | |
| US5793948 | 1998-08-01 | Asahi et al. | |
| US5793987 | 1998-08-01 | Quackenbush et al. | |
| US5794035 | 1998-08-01 | Golub et al. | |
| US5796185 | 1998-08-01 | Takata et al. | |
| US5796580 | 1998-08-01 | Komatsu et al. | |
| US5796981 | 1998-08-01 | Abudayyeh et al. | |
| US5797023 | 1998-08-01 | Berman et al. | |
| US5798828 | 1998-08-01 | Thomas et al. | |
| US5799036 | 1998-08-01 | Staples | |
| US5799196 | 1998-08-01 | Flannery | |
| US5801921 | 1998-09-01 | Miller | |
| US5802269 | 1998-09-01 | Poisner et al. | |
| US5802298 | 1998-09-01 | Imai et al. | |
| US5802305 | 1998-09-01 | McKaughan et al. | |
| US5802324 | 1998-09-01 | Wunderlich et al. | |
| US5802393 | 1998-09-01 | Begun et al. | |
| US5802552 | 1998-09-01 | Fandrich et al. | |
| US5802592 | 1998-09-01 | Chess et al. | |
| US5803357 | 1998-09-01 | Lakin | |
| US5805804 | 1998-09-01 | Laursen et al. | |
| US5805834 | 1998-09-01 | McKinley et al. | |
| US5809224 | 1998-09-01 | Schultz et al. | |
| US5809256 | 1998-09-01 | Najemy | |
| US5809287 | 1998-09-01 | Stupek, Jr. et al. | |
| US5809311 | 1998-09-01 | Jones | |
| US5812748 | 1998-09-01 | Ohran et al. | |
| US5812750 | 1998-09-01 | Dev et al. | |
| US5812757 | 1998-09-01 | Okamoto et al. | |
| US5812858 | 1998-09-01 | Nookala et al. | |
| US5815117 | 1998-09-01 | Kolanek | |
| US5815647 | 1998-09-01 | Buckland et al. | |
| US5815652 | 1998-09-01 | Ote et al. | |
| US5821596 | 1998-10-01 | Miu et al. | |
| US5822547 | 1998-10-01 | Boesch et al. | |
| US5835719 | 1998-11-01 | Gibson et al. | |
| US5835738 | 1998-11-01 | Blackledge, Jr. et al. | |
| US5838932 | 1998-11-01 | Alzien | |
| US5841964 | 1998-11-01 | Yamaguchi | |
| US5841991 | 1998-11-01 | Russell | |
| US5845061 | 1998-12-01 | Miyamoto et al. | |
| US5845095 | 1998-12-01 | Reed et al. | |
| US5852720 | 1998-12-01 | Gready et al. | |
| US5852724 | 1998-12-01 | Glenn, II et al. | |
| US5857074 | 1999-01-01 | Johnson | |
| US5857102 | 1999-01-01 | McChesney et al. | |
| US5864653 | 1999-01-01 | Tavallaei et al. | |
| US5864713 | 1999-01-01 | Terry | |
| US5867730 | 1999-02-01 | Leyda | |
| US5875307 | 1999-02-01 | Ma et al. | |
| US5875308 | 1999-02-01 | Egan et al. | |
| US5875310 | 1999-02-01 | Buckland et al. | |
| US5878237 | 1999-03-01 | Olarig | |
| US5878238 | 1999-03-01 | Gan et al. | |
| US5881311 | 1999-03-01 | Woods | |
| US5884027 | 1999-03-01 | Garbus et al. | |
| US5889965 | 1999-03-01 | Wallach et al. | |
| US5892898 | 1999-04-01 | Fujii et al. | |
| US5892928 | 1999-04-01 | Wallach et al. | |
| US5898846 | 1999-04-01 | Kelly | |
| US5898888 | 1999-04-01 | Guthrie et al. | |
| US5905867 | 1999-05-01 | Giorgio | |
| US5907672 | 1999-05-01 | Matze et al. | |
| US5913034 | 1999-06-01 | Malcolm | |
| US5922060 | 1999-07-01 | Goodrum | |
| US5935262 | 1999-08-01 | Barrett et al. | |
| US5936960 | 1999-08-01 | Stewart | |
| US5938751 | 1999-08-01 | Tavallaei et al. | |
| US5941996 | 1999-08-01 | Smith et al. | |
| US5987554 | 1999-11-01 | Liu et al. | |
| US6012130 | 2000-01-01 | Beyda et al. | |
| EPX866403A1 | 1998-09-01 | ||
| JPX5233110 | 1993-09-01 | ||
| JPX7093064 | 1995-04-01 | ||
| JPX7261874 | 1995-10-01 |
Non-Patent Literature (27)
- Davis, T, Usenet post to alt.msdos.programmer, APr. 1997, "Re: How do I create an FDISK batch file?".
- Davis. T., Usenet post to alt.msdos.batch, Apr. 1997, "Re: Need help with automating FDISK and FORMAT . . . ".
- NetFrame Systms 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.RTM. NetWare.RTM. 4.1 SMP, 4.1, and 3.12."
- Shanley, and Anderson, PCI System Architecture, Third Edition, Chapter 15, pp. 297-302, Copyright 1995, "Intro To Configuration Address Space."
- Shanley, and Anderson, PCI System Architecture, Third Edition, Chapter 16, pp. 303-328, Copyright 1995, "Configuration Transactions".
- Sun Microsystems Computer Company, Part No. 802-5355-10, Rev. A, May 1996, "Solstice SyMON User's Guid."
- Sun Microsystems, Part No. 802-6569-11, Release 1.0.1, Nov. 1996, "Remote Systems Diagnostics Installation & User GUide."
- Shanley and Anderson, PCI System Architecture, Third Edition, Chapters 15 & 16, pp. 297-328, CR 1995.
- PCI Hot-Plug Specification, Preliminary Revision for Review Only, Revision 0.9, pp. i-vi, and 1-25, Mar. 5, 1997.
- SES SCSI-3 Enclosure Services, X3T10/Project 1212-D/Rev 8a, pp. i, iii-x, 1-76, and I-1 (index), Jan. 16, 1997.
- Compaq Computer Corporation, Technology Brief, pp. 1-13, Dec. 1996, "Where Do I Plug the Cable? Solving the Logical-Physical SLot Numbering Problem."
- NetFRAME Systems Incorporated, News Release, 3 pages, referring to May 9, 1994, "NetFRAME's New High-Availability ClusterServer Systems Avoid Scheduled as well as Unscheduled Downtime."
- Herr, et al., Linear Technology Magazine, Design Features, pp. 21-23, Jun. 1997, "Hot Swapping the PCI Bus."
- Lockareff, M., HTINews,, http://www.hometoys.com/htinews/dec96/article/lonworks.htm, Dec. 1996, "Lonworks--An Introduction".
- NetFRAME Systems Incorporated, datasheet, Feb. 1992, "NF450FT Network Mainframe".
- NetFRAME Systems Incorporated, datasheet, Mar. 1996, "NetFRAME Cluster Server 8000".
- Schofield, M.J., http://www.omegas.co.uk/CAN/canworks.htm, Copyright 1996, 1997, "Controller Area Network--How CAN Works".
- http://www.nrtt.demon.co.uk/cantech.html, May 28, 1997, "CAN: Technical overview".
- ftp.cdrom.com/pub/os2/diskutil/, PHDX software, phdx.zip download, Mar. 1995, "Parallel Hard Disk Xfer."
- Cmasters, Usenet post to microsoft.public.windowsnt.setup, Aug. 1997, "Re: FDISK switches."
- Hildebrand, N., Usenet post to comp.msdos.programmer, May 1995, "Re: Structure of disk partition info."
- Lewis, L., Usenet post to alt.msdos.batch, Apr. 1997, "Re: Need help with automating FDISK and FORMAT."
- Netframe, http://www.netframe-support.com/technology/datasheets/data.htm, before Mar. 1997, "Netframe ClusterSystem 9008 Data Sheet."
- Simos, M., Usenet post to comp.os.msdos.misc, Apr. 1997, "Re: Auto FDISK and FORMAT."
- Wood, M. H., Usenet post to comp.os.netware.misc, Aug. 1996, "Re: Workstation duplication method for WIN95."
- 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."
- IBM Technical Disclosure Bulletin, 92A+62947, pp. 391-394, Oct. 1992, Method for Card Hot Plug Detection and Control.