International Business Machines Corporation

Gaurav Kakkar

Douglas Michael Boecker

Jinu Joy Thomas

Santosh Puranik

Christopher L Bostic

Disclosed aspects relate to service interface topology management for a shared pool of configurable computing resources. A management engine may detect a first linkage error event for a first set of data traffic with respect to a first service interface cable which connects a first global service processor with a set of hardware devices. A second service interface cable which connects a second global service processor with the set of hardware devices may be sensed. Based on and in response to the first linkage error event for the first set of data traffic, the management engine may determine to access the set of hardware devices by utilizing the second service interface cable. The first set of data traffic may be routed to the set of hardware devices via the second service interface cable.

Service interface topology management

Disclosed aspects relate to dynamic cable-linkage management for a shared pool of configurable computing resources having a set of cable-linkage topology data. A first connection between a first service processor and a plurality of compute nodes may be sensed by a first mapping engine which is coupled with a first service processor on a set of control nodes. A plurality of node identifiers may be established on the plurality of compute nodes by the first mapping engine. Based on the plurality of node identifiers and the set of cable-linkage topology data, a first device path map may be determined. A set of data traffic may be routed via the first connection between the first service processor and the plurality of compute nodes based on the first device path map.

Dynamic cable-linkage management

Fault isolation for a computer system having multiple FRUs in an FSI chain uses logic embedded in a device driver to determine first failure data and a logical error identifier. The logical error identifier represents a hardware logical area of the fault. The fault is then mapped to a segment of the system based on a self-describing system model which includes FRU boundary relationships for the devices. Operation of the device driver is carried out by a flexible service processor. The device driver uses the first failure data to identify a link at a failure point corresponding to the fault and determine a failure type at the link, then maps the link and the failure type to the logical error identifier. After identifying the segment, the device driver can generate a list of callouts of the field replaceable units associated with the segment which require replacement.

Growing community of inventors

Bengaluru, India

Gaurav Kakkar