International Business Machines Corporation

Gary Owen McAfee

Constantinos Kassimis

Jerry Wayne Stevens

Patricia G Driever

Alexandra Winter

Michael G Fitzpatrick

Andrew Hilliard Arrowood

Linwood Hugh Overby, Jr

Sue L Huang

Andrea Lynn Fitzpatrick

Richard P Tarcza

Angelo Macchiano

Kimberly Tekavec Bailey

John Majikes

A method, apparatus and computer program product that allows for maintaining correct states of all sub-components in a state machine, even as sub-components leave the state machine and later rejoin in some previous state. Preferably, this is achieved without requiring the system to remember the states of all sub-components or a log of every event that was fed into the state machine. Thus, the technique does not require any knowledge of the previous state of the sub-components nor the need to preserve a complete log of events that were fed into the state machine. The state machine may be used to enhance the operation of a technological process, such as a workload management environment.

Maintaining state information in a multi-component, event-driven state machine

A method, apparatus and computer program product for improved load balancing provides for the grouping under a same workload of both application instances in an application tier, and data sharing members in a data tier. This grouping enables a workload manager to make recommendations (to load balancer appliances) about how to distribute workload connections, e.g., based on metrics gathered from both the application and data tiers. In this approach, both applications and data sources are grouped into a workload grouping, and health, status and capacity information about both of these tiers (application and data) is then used to determine an overall distribution policy for the workload. These different tiers can reside on the same or different operating system environments.

Combining application and data tiers on different platforms to create workload distribution recommendations

A method that provides for the grouping under a same workload of both application instances in an application tier, and data sharing members in a data tier. This grouping enables a workload manager to make recommendations (to load balancer appliances) about how to distribute workload connections, e.g., based on metrics gathered from both the application and data tiers. In this approach, both applications and data sources are grouped into a workload grouping, and health, status and capacity information about both of these tiers (application and data) is then used to determine an overall distribution policy for the workload. These different tiers can reside on the same or different operating system environments.

The disclosed network resource management system employs a hardware configuration management (HCM) information handling system (IHS) that may couple to a single administered IHS or to multiple administered IHSs via an administrative network. An HCM tool in the HCM IHS may generate, modify and store hardware configuration information, including physical network identifications (PNet IDs), in an HCM database and share the HCM database with the administered IHSs. The administered IHS may be a privileged network access (PNA) IHS. The PNA IHS may receive a privileged network access management (PNAM) database from a PNAM IHS via the administrative network. The PNA tool may extract hardware configuration information, including PNet IDs, from the HCM database and privileged network access information, including PNet IDs, from the PNAM database. The PNA tool may utilize the information, including PNet IDs, to enable the PNA IHS to limit access to privileged networks.

Network resource management system utilizing physical network identification for privileged network access

The disclosed network resource management system employs a hardware configuration management (HCM) information handling system (IHS) that may couple to a single administered IHS or to multiple administered IHSs via an administrative network. An HCM tool in the HCM IHS may generate, modify and store hardware configuration information, including physical network identifications (PNet IDs), in an HCM database and share the HCM database with the administered IHSs. The administered IHS may be a load balancing IHS. A load balancing tool may extract hardware configuration information, including PNet IDs, from the HCM database. The load balancing tool may utilize the hardware configuration information to enable the load balancing IHS to balance adapter loads in the load balancing IHS. The load balancing tool may also utilize the hardware configuration information to enable the load balancing IHS to failover from a failing adapter to other adapters in the load balancing IHS.

Network resource management system utilizing physical network identification for load balancing

The disclosed network resource management system employs a hardware configuration management (HCM) information handling system (IHS) that may couple to a single administered IHS or to multiple administered IHSs via an administrative network. An HCM tool in the HCM IHS may generate, modify and store hardware configuration information, including physical network identifications (PNet IDs), in an HCM database and share the HCM database with the administered IHSs. The administered IHS may be a remote direct memory access (RDMA) enabled network interface controller (RNIC) converging IHS. An RNIC converging tool may extract hardware configuration information, including PNet IDs, from the HCM database. The RNIC converging tool may utilize the hardware configuration information, including PNet IDs, to enable the RNIC converging IHS to communicate over a network with RDMA protocols.

Network resource management system utilizing physical network identification for converging operations

The disclosed network resource management system employs a hardware configuration management (HCM) information handling system (IHS) that may couple to a single administered IHS or to multiple administered IHSs via an administrative network. An HCM tool in the HCM IHS may generate, modify and store hardware configuration information, including physical network identifications (PNet IDs), in an HCM database and share the HCM database with the administered IHSs. The administered IHS may be a bridging IHS. A bridging tool may extract hardware configuration information, including PNet IDs, from the HCM database. The bridging tool may utilize the hardware configuration information, including PNet IDs, to enable the bridging IHS to bridge networks internal to the bridging IHS with networks external to the bridging IHS.

Network resource management system utilizing physical network identification for bridging operations

A Hardware Management Console (HMC) configures virtual networks. The HMC extends Internal Queued Direct I/O to an intra-ensemble data network (IEDN) within a cluster of virtual servers to define a single channel path identifier, and to define a channel parameter. The HMC defines at least one virtual network. The HMC defines a bridge port within each CPC that supports at least one of the virtual servers. The HMC defines a network interface for each virtual server within each cluster. The HMC grants access to a corresponding virtual network for each virtual server.

Growing community of inventors

Raleigh, NC, United States of America

Gary Owen McAfee