Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Mechanism to Handle Inter-Systems Action Retries and Errors

IP.com Disclosure Number: IPCOM000249319D
Publication Date: 2017-Feb-16
Document File: 3 page(s) / 205K

Publishing Venue

The IP.com Prior Art Database


Disclosed is a generic infrastructure for handling errors and executing retries at the controller system level when talking to various entities.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.


Mechanism to Handle Inter-Systems Action Retries and Errors

In a Disaster Recovery (DR) solution using a controller system (i.e., KSYS) node, the KSYS periodically needs to gather information from various entities such as Virtual Input/Output Servers (VIOSs), Logical Partitions (LPARs), Hosts (aka CECs), and Hardware Management Consoles (HMCs). For instance, it can query two types of information from a VIOS via the HMC pass through Representational State Transfer (REST) Application Programming Interface (API):

· Capability Information (Exchange) · Client Storage Information

The exchange capability call provides information regarding the various Extensible Markup Language Schema Definitions (XSDs) supported by the VIOS for different problem spaces, viz, storage service provider (SSP), K2/CM and DR, in addition to the Capability exchange itself. The caller is expected to pick the highest version it understands and one that supports the required functionality or features. The client storage information provides information about all the storage devices that are being currently exported to various client LPARs using either Virtual Small Computer System Interface (VSCSI) or N_Port ID virtualization (NPIV) technology.

These queries are issued to the VIOS via the HMC using the HMC’s pass through REST API. As the query routes to the VIOS via the different subsystems such as KSYS <--> HMC <-> RMC <-> VIOS and back, errors can occur at these various levels. Some of these errors surface to...