International Business Machines Corporation

Alexandra Winter

Jerry Wayne Stevens

Patricia G Driever

Constantinos Kassimis

Gary Owen McAfee

Richard P Tarcza

Angelo Macchiano

Gustav E Sittmann, Iii

Kimberly Tekavec Bailey

Waleri Fomin

Donald W Schmidt

Utz Bacher

Martin Taubert

Thomas Donald Moore

Stefan Reimbold

Andreas Gerstmeier

Dietmar Friedrich Decker

Andreas Scheuring

Gustav Sittmann Iii

Monitoring network addresses and managing data transfer of an electronic data processing system. A first data packet including a first source network address and a first target network address is received via a first system link of a first converged interface. The first source network address is a unique network address assigned to a subsystem of the electronic data processing system. The first converged interface checks whether the first source network address is registered in a first source table assigned to the first converged interface. If the first source network address is not registered in the first source table, a registration of the first source network address is added to the first source table and it is announced to the remaining converged interfaces of the electronic data processing system that the first source network address is registered for the first computer system.

Monitoring network addresses and managing data transfer

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.

Virtual network configuration and management

A computer implemented method for sharing physical memory among logical partitions. A computer reserves physical memory of a Central Electronic Complex (CEC) for communication within the CEC as a shared memory pool. The computer creates a first logical partition using resources of the CEC that are not reserved as the shared memory pool. The computer creates a second logical partition using resources of the CEC that are not reserved as the shared memory pool. The computer creates a virtual local area network (VLAN) having at least two addresses within the CEC. The computer allocates a portion of the shared memory to the VLAN as the shared memory pool.

Physical memory shared among logical partitions in a VLAN

Automatically converting a synchronous data transfer to an asynchronous data transfer. Data to be transferred from a sender to a receiver is initiated using a synchronous data transfer protocol. Responsive to a determination that the data is to be sent asynchronously, the data transfer is automatically converted from the synchronous data transfer to the asynchronous data transfer.

Facilitating communication between isolated memory spaces of a communications environment

A method of operating a computer system comprising a bridge port between a hardware local area network (LAN) and a virtual switch includes providing a first hash table by the hardware LAN to the virtual switch via the bridge port, wherein the first hash table comprises addresses of a first plurality of VMs that comprise the hardware LAN, wherein the first plurality of VMs communicate with the hardware LAN via respective hardware network interface cards (NICs); and updating a second hash table in the virtual switch to include the addresses of the first hash table, wherein the second hash table further comprises addresses of a second plurality of VMs of the virtual switch, wherein the second plurality of VMs communicate with the virtual switch via respective virtual NICs.

Bridge port between hardware LAN and virtual switch

Performing logical partition (LPAR)-to-LPAR communication in a network computing environment. Read or write requests to different memory areas of a single computer memory are controlled by a storage control element, where the requests are issued by different multiple operating systems using a general network transfer format. A request is sent by a first operating system to said storage control element, where the request is executed with a processor instruction. A result of the request is received by the same or a second operating system. A modified processor instruction is sent to the storage control element, which implements an execution of the instruction synchronously performed to the sending of the instruction, without buffering the request of the instruction in a dedicated queue.

Growing community of inventors

Boeblingen, Germany

Alexandra Winter