Abstract: An apparatus and method for determining the power consumption of one or more disk arrays are described. Power consumption information for various hardware components of the array, especially that for the disk drives since these consume more than 90% of the required power, are stored in a static data table in a database which may be controller firmware. Through inspection of this table and the chosen state of the individual disk drives as directed by a controller, one may determine the power use of the array.

Abstract: An apparatus and method for determining the power consumption of one or more disk arrays are described. Power consumption information for various hardware components of the array, especially that for the disk drives since these consume more than 90% of the required power, are stored in a static data table in a database which may be controller firmware. Through inspection of this table and the chosen state of the individual disk drives as directed by a controller, one may determine the power use of the array.

Abstract: A system for updating management entities or devices in a computer system network with configuration change information from the devices being managed. The management entities are configured to discover, monitor and configure managed devices, such as storage systems, connected to the network. Preferably, the managed devices include a comparator which can track changes made to the managed device configuration or properties and report that change back to the various management entities. In this way, the management entities can keep track of the configurations of the various devices that they manage, even though they might not be responsible for issuing the configuration change. This can be accomplished even when managed devices developed by different manufacturers according to different standards or protocols are involved.

Abstract: The present invention provides for a method and computer program product for handling timeout in a standard RPC connection. First, a client establishes a connection with a server with unique identification. After submitting an RPC request, the client system will periodically make secondary requests to the server to determine if the server is still actively processing the primary RPC request. If the secondary request is processed successfully and the server indicates that the primary request is still in progress, the client will continue to wait until either the primary request completes or enough time elapses to warrant another secondary request. The success of the secondary request hinges on finding a match of identification for the primary and secondary requests. If the secondary request fails, this failure is treated as a sign that there is either a network or a server problem, and the client is triggered into taking appropriate corrective action.

Abstract: A host computer environment includes a driver stack having a disk driver and a host bus adapter (HBA) driver. The driver stack further includes a multipath driver functionally embedded between the disk driver and HBA driver. At this hierarchical layer of the driver stack, the multipath driver functions at the command transport protocol level. The disk driver effectively views the multipath driver as a HBA driver type, while the HBA driver effectively views the multipath driver as a disk driver type. The multipath driver is configured to instantiate proxy virtual paths to the disk array that are visible to the host operating system but otherwise conceal the underlying physical paths. The multipath driver retains knowledge of the mapping between the physical and virtual paths. The disk array is configured to report itself to the OS as a non-disk device type, although its true identity is known by the multipath driver.

Abstract: A system for monitoring and managing devices on network comprising one or more managed devices connected to the network and storage means for storing a device management application program associated with each of the managed devices. The system further includes a management station which is in communication with each of the managed devices across the network, and the management station is in communication with the storage means. When a user wishes to monitor, configure, or manage one of the managed devices on the network, the user preferably selects the managed device to be managed and the management station retrieves from the storage means the device management application program associated with the selected managed device. By the management station processing the management application program for the selected managed device, the management station allows the user to monitor the status of the managed device, as well as change the configuration of and fix errors with the managed device.

Abstract: In a storage environment or storage area network having multiple host devices and at least one storage array, the host devices access logical data volumes stored on the storage array through array controllers disposed in the storage array. Multiple host devices can request access to shared ones of the logical data volumes through multiple paths to multiple array controllers, but each logical data volume is controlled or owned by only one array controller at a time. Thus, ownership of shared logical data volumes is transferred between the array controllers as necessary on behalf of the requesting host devices. To prevent ownership transfers from occurring too often, however, ownership of the logical data volumes is made exclusive, or “sticky,” for a period of time after each transfer. During the exclusive ownership period of time, the ownership cannot be transferred.

Abstract: The present invention provides for a method and computer program product for handling timeout in a standard RPC connection. First, a client establishes a connection with a server with unique identification. After submitting an RPC request, the client system will periodically make secondary requests to the server to determine if the server is still actively processing the primary RPC request. If the secondary request is processed successfully and the server indicates that the primary request is still in progress, the client will continue to wait until either the primary request completes or enough time elapses to warrant another secondary request. The success of the secondary request hinges on finding a match of identification for the primary and secondary requests. If the secondary request fails, this failure is treated as a sign that there is either a network or a server problem, and the client is triggered into taking appropriate corrective action.

Abstract: A method of configuring a plurality of managed devices. The method preferably includes selecting a source managed device, obtaining a source configuration description from the source managed device, selecting one or more destination managed devices to be configured, issuing a configuration change command to each of the selected destination managed devices and applying the source configuration description selected from the source managed device to each of the selected destination managed devices. In addition, the method may further include the step of editing the source configuration description before issuing the configuration change commands to the one or more destination managed devices.

Abstract: A storage array contains firmware which maintains topology and other information in a computer system. Individual host computers each have a host context agent which interfaces with both thin client devices and the storage array. A user by a simple GUI command or set of commands may update and/or retrieve topology and other computer system configuration information which is stored by either a host computer or the storage array or both.

Abstract: A system and method for monitoring and managing devices on a network. The system and method preferably comprises a proxy server connected to the network and a managed device connected to the proxy server. The system further comprises storage means for storing a device management application program associated with the managed device, and a management station in communication with the managed device via the proxy server and in communication with the storage means. The management station preferably is configured to retrieve the device management application program from the storage means and process the device management application program. As the management station processes the device management application program, the management station is able to monitor and manage the managed device.

Abstract: Methods and associated systems using probabilistic methods for selecting among a plurality of diagnostic procedures to recover from an error condition in a managed device. Operation of a managed device is overseen by a management device. A management client process operable within the management device communicates with a management service operable within the managed device. Upon detection of an error condition within the managed device, the management service propagates an event to the management client so indicating an error condition. The management client in the management device responds to the event by requesting the managed device to determine the best options for recovery procedures. The managed device then computes a probability of success for each known recovery procedure based upon the present state of the managed device and based upon past successes or failures of recovery procedures for particular error conditions.

Abstract: A system and method for managing device configuration changes. The system and method preferably comprises a management station which issues a configuration change request to a management device and waits for a reply from the managed device. The managed device receives the configuration change request from the management station and processes the change request until the configuration change request is durable on the managed device. The managed device then returns a status to the management station indicating that the configuration request is durable. The management station receives the status from the managed device and stops waiting for reply. In the meantime, the managed device continues processing the configuration change request.

Abstract: A system and method for monitoring and managing devices on a network. The system and method preferably comprises a proxy server connected to the network and a managed device connected to the proxy server. The system further comprises storage means for storing a device management application program associated with the managed device, and a management station in communication with the managed device via the proxy server and in communication with the storage means. The management station preferably is configured to retrieve the device management application program from the storage means and process the device management application program. As the management station processes the device management application program, the management station is able to monitor and manage the managed device.

Abstract: A redundant storage control module (also referred to as RDAC or multi-active controller) maintains a queue of pending I/O requests sent for processing via a first asynchronously operating I/O path. In the event of failure of the first asynchronously operating I/O path, the controller restarts the entire queue of pending I/O requests to a second I/O path without waiting for each request to individually fail from the first path. Some prior techniques required the RDAC module to await failure of each I/O request sent to the failed first I/O path before restarting each failed request on the secondary I/O path. Such techniques greatly extend the total time required to restart all operations sent to a failed I/O path, by awaiting the failure of all I/O requests previously sent to the first I/O path.

Abstract: A RAID storage system which attempts to balance the I/O workload between multiple redundant array controllers is presented. The RAID storage system of the invention utilizes a plurality of redundant array controllers which require static ownership of storage devices for WRITE access requests to the same redundancy parity group. Accordingly, a plurality of storage devices are provided in the system, each of which is owned by one of the redundant array controllers. Each storage device is coupled to both its owner controller and at least one other array controller. Each array controller coupled to a storage device has the ability to read and write data from and to the storage device. Each array controller has a processing queue from which pending read and write access requests are removed and then processed one at a time by the controller. A host computer is provided for dispatching read and write access requests to the redundant array controllers.

Abstract: Methods operable in a SCSI RAID subsystem to enable improved portability in host based RAID management programs. RAID management programs which provide an administrative user interface for managing the operation and configuration of a RAID subsystem have traditionally communicated with the RAID system using control function calls (ioctl) through the operating system's device driver. Ioctl function calls are notoriously non-standardized among different operating systems and even among different versions of certain operating systems. The methods of the present invention are operable within a RAID subsystem to enable use of standardized read and write system function calls to the device driver for communication with a control port within the RAID subsystem. A special LUN is reserved for such read and write administrative calls. The special control port LUN processes the read and write calls to perform the desired RAID management functions on behalf of the management program on an attached host computer.

Abstract: A procedure for scheduling multiple process requests for read/write access to a disk memory device within a computer system. The procedure considers disk characteristics, such as the number of sectors per track, the number of tracks per cylinder, speed of disk rotation and disk controller queuing capability in determining the optimal order for executing process requests. Process requests are placed in packets within an execution queue, each packet including up to a predetermined maximum number of requests. Within the packets, the process requests are sorted in ascending/descending order by the cylinder number to which the requests desire access, while within each cylinder the requests are placed in next-closest-in-time sequence.