Unisys Corporation

James R Malnati

Robert Jamieson

Donald J Ethen

John Troini

Tyson R Midboe

Paul D Urevig

John E Trierweiler

Melanie A Wolbeck

Elizabeth F Roush

Herbert L Weber

Data channels of a computer system may be remotely monitored to detect data channel degradation. A monitoring agent on a client may execute script commands on the remote computer system to monitor input/output (I/O) rates of a set of channels. The monitoring agent may compute an average data rate of the data channels and compare the I/O rate of each channel to the average. When the I/O rate of a channel falls below the average by at least a threshold amount, an alert may be generated to indicate to an administrator a possible failure with the data channel.

Data rate monitoring to determine channel failure

Non-automated read-and-reply console messages may be automated. These messages may be classified into impact groups in which the messages may be removed from the database or sent to an automation analyzer for analysis. As more messages become automated, a debugging mode may be enabled to allow an operator to respond to a message with a proposed action. If the proposed action is aligned with an action predetermined in response to the automation analysis, the operator may be allowed to respond to future actions.

Identification of progress towards complete message system integration using automation degree of implementation metrics

A system and method for monitoring and correcting device operating states during steady-state operations may be automated. The operating states for devices operating in a steady-state environment may be monitored. Any operating device that is set to operate in an unexpected operating state may be automatically changed to its expected operating state. The operator may then be warned of any incorrect state assignment through a console message that cannot be ignored by the operator.

Device expected state monitoring and remediation

Monitoring of storage systems, including virtual tape libraries (VTLs), may be performed with automated systems. Automated monitoring may be performed through an SSH connection to a storage manager for the storage system. For example, a method may include initiating, by a monitoring server, an SSH connection to a storage manager; issuing commands, by the monitoring server, through the SSH connection to monitor a storage device coupled to the storage manager; receiving, by the monitoring server, responses to the issued commands through the SSH connection; matching, by the monitoring server, the responses to automation rules; and executing, by the monitoring server, commands based on the matched automation rules.

Virtual tape library (VTL) monitoring system

Debug and verify execution modes for computing systems calculating automation degree of implementation metrics

Automation scripts may be examined and compared to a set of new or changed operating system messages to identify potential issues with the automation script that occur with updates to the operating system. When the issue is identified, the reference in the automation script may be updated to refer to the changed operating system message. Further, the reference in the automation script may be modified to address other changes in the system messages, such as changes in information and/or parameters reported in the message.

Automated code parser for reviewing automation scripts

Identification of automation candidates using automation degree of implementation metrics

Systems and methods for multi-threaded server control automation for disaster recovery are described. A method may include initiating a disaster recovery sequence on two or more processors, wherein the disaster recovery sequence comprises a plurality of subsequences. The method may also include implementing the disaster recovery sequence on the two or more processors in parallel, wherein one or more subsequences of the disaster recovery sequence are implemented on the two or more processors in parallel. Upon completion of the disaster recovery sequence, at least one server partition is repurposed from a first configuration, such as a test configuration, to a second configuration, such as a production configuration.

Multi-threaded server control automation for disaster recovery

Systems and methods for automated monitoring of automated server control components are provided. Embodiments may include transmitting a request for state information associated with a component of the automated server control system. At least one of a reception of the state information for the component and a threshold time period without reception of the state information for the component may be detected. Some embodiments may include determining if the received state information for the component comprises an error condition. In some instances, an alert may be output based on at least one of detecting the threshold time period without reception of the state information for the component and determining that the received state information comprises an error condition.

Automated monitoring of server control automation components

Control over servers and partitions within a computer network may be automated to improve response to disaster events within the computer network. For example, a monitoring server may be configured to automatically monitor servers through remote communications sessions. A disaster event may be detected based on information received from the partitions and servers within the network. When a disaster event or events leading to a disaster event are detected, a trouble ticket may be generated. The trouble ticket may also generate an alert displayed to an administrator through a customized hierarchical graphical display. When the administrator is not logged in, messages may be generated to alert the administrator to the problem. The administrator may then log in remotely and respond to the alert.

Automated trouble ticket generation

Control over servers and partitions within a computer network may be automated to improve response to disaster events within the computer network. For example, a monitoring server may be configured to automatically monitor servers through remote communications sessions. A disaster event may be detected based on information received from the partitions and servers within the network. After a disaster event occurs, the monitoring server may automatically execute a script or take other action to make a backup server or partition available. For example, the monitoring server may stop and deactivate a first partition that has failed, activate a second partition that is a mirror image of the first partition, and start the second partition.

Server control automation

The disclosure relates generally to autonomous generation of software documentation, and more specifically to autonomous generation of documentation that describes user-defined rules implemented for a computer management system. In one embodiment, a system for generating documentation comprises a database storing user-defined rules that specify management actions to be triggered, for managing a computer system, responsive to receipt of a system message from the managed computer system. The system further comprises a documentation generation device configured to autonomously generate documentation describing the rules, wherein the documentation contains identification of at least the system message and the corresponding management actions triggered by the rules upon receipt of the system message. In certain embodiments, the system further comprises a database utility device configured to generate a highly-structured representation of the user-defined rules from an autoaction database, and the documentation generation device processes the highly-structured representation to autonomously generate the documentation.

System and method for autonomous generation of software documentation

A method and apparatus for sending a message from a first operator at a first workstation to a second operator at a second workstation in an operations-computing arrangement for operating one or more computer systems. The operations-computing arrangement includes the first and second workstations, which are coupled to respective operations servers. Each operations server is coupled to at least one computer system, each workstation executes software that provides an operator interface for operating a computer system, and each operations server provides an interface to a computer system. The infrastructure used to transmit system-generated event reports to operators at the workstations is used to transmit text messages between operators.

Operator messaging within an environment for operating multiple computing systems

A method and apparatus for operating one or more computer systems via an operations-computing arrangement. The operations-computing arrangement includes a plurality of workstations coupled to a plurality of operations servers, and each operations server is coupled to at least one computer system. Each workstation executes software that provides a user interface for operating a computer system, and each operations server provides an interface to a computer system. A first operations server registers with a second operations server for the second operations server to forward event reports received by the second operations server to the first operations server. The second operations server generates event reports in response to computer system events. Event reports are transmitted from the second operations server to one or more workstations coupled to the second operations server, and also to the first operations server. A user interface on each workstation provides for display of data related to the event reports and for input of controls for operation of the computer systems.

Growing community of inventors

Stillwater, MN, United States of America

James R Malnati