Abstract: According to one exemplary embodiment, a method for VIOS failover in an environment with a physical storage adapter is provided. The method may include assigning the physical storage adapter to a first VIOS, wherein the physical storage adapter has I/O connectivity to at least one storage device. The method may include configuring a first I/O path between the first VIOS and a second VIOS. The method may include configuring a second I/O path from a client partition to the first VIOS, wherein the second I/O path is set as a primary I/O path. The method may include configuring a third I/O path from the client partition to the second VIOS. The method may include determining the first VIOS is inaccessible. The method may include unassigning the physical storage adapter from the first VIOS. The method may include assigning the physical storage adapter to the second VIOS.

Abstract: According to one exemplary embodiment, a method for VIOS failover in an environment with a physical storage adapter is provided. The method may include assigning the physical storage adapter to a first VIOS, wherein the physical storage adapter has I/O connectivity to at least one storage device. The method may include configuring a first I/O path between the first VIOS and a second VIOS. The method may include configuring a second I/O path from a client partition to the first VIOS, wherein the second I/O path is set as a primary I/O path. The method may include configuring a third I/O path from the client partition to the second VIOS. The method may include determining the first VIOS is inaccessible. The method may include unassigning the physical storage adapter from the first VIOS. The method may include assigning the physical storage adapter to the second VIOS.

Abstract: According to one exemplary embodiment, a method for VIOS failover in an environment with a physical storage adapter is provided. The method may include assigning the physical storage adapter to a first VIOS, wherein the physical storage adapter has I/O connectivity to at least one storage device. The method may include configuring a first I/O path between the first VIOS and a second VIOS. The method may include configuring a second I/O path from a client partition to the first VIOS, wherein the second I/O path is set as a primary I/O path. The method may include configuring a third I/O path from the client partition to the second VIOS. The method may include determining the first VIOS is inaccessible. The method may include unassigning the physical storage adapter from the first VIOS. The method may include assigning the physical storage adapter to the second VIOS.

Abstract: According to one exemplary embodiment, a method for VIOS failover in an environment with a physical storage adapter is provided. The method may include assigning the physical storage adapter to a first VIOS, wherein the physical storage adapter has I/O connectivity to at least one storage device. The method may include configuring a first I/O path between the first VIOS and a second VIOS. The method may include configuring a second I/O path from a client partition to the first VIOS, wherein the second I/O path is set as a primary I/O path. The method may include configuring a third I/O path from the client partition to the second VIOS. The method may include determining the first VIOS is inaccessible. The method may include unassigning the physical storage adapter from the first VIOS. The method may include assigning the physical storage adapter to the second VIOS.

Abstract: An embodiment of the invention is associated with a virtualized environment that includes a hypervisor, client LPARs, and virtual servers that each has a SEA, wherein one SEA is selected to be primary SEA for connecting an LPAR and specified physical resources. A first SEA of a virtual server sends a call to the hypervisor, and in response the hypervisor enters physical adapter capability information, contained in the call and pertaining to the first SEA, into a table. Further in response to receiving the call, the hypervisor decides whether or not the first SEA of the virtual server should then be the primary SEA. The hypervisor sends a return call indicating its decision to the first SEA.

Abstract: An embodiment of the invention is associated with a virtualized environment that includes a hypervisor, client LPARs, and virtual servers that each has a SEA, wherein one SEA is selected to be primary SEA for connecting an LPAR and specified physical resources. A first SEA of a virtual server sends a call to the hypervisor, and in response the hypervisor enters physical adapter capability information, contained in the call and pertaining to the first SEA, into a table. Further in response to receiving the call, the hypervisor decides whether or not the first SEA of the virtual server should then be the primary SEA. The hypervisor sends a return call indicating its decision to the first SEA.

Abstract: An embodiment of the invention is associated with a virtualized environment that includes a hypervisor, client LPARs, and virtual servers that each has a SEA, wherein one SEA is selected to be primary SEA for connecting an LPAR and specified physical resources. A first SEA of a virtual server sends a call to the hypervisor, and in response the hypervisor enters physical adapter capability information, contained in the call and pertaining to the first SEA, into a table. Further in response to receiving the call, the hypervisor decides whether or not the first SEA of the virtual server should then be the primary SEA. The hypervisor sends a return call indicating its decision to the first SEA.

Abstract: An embodiment of the invention is associated with a virtualized environment that includes a hypervisor, client LPARs, and virtual servers that each has a SEA, wherein one SEA is selected to be primary SEA for connecting an LPAR and specified physical resources. A first SEA of a virtual server sends a call to the hypervisor, and in response the hypervisor enters physical adapter capability information, contained in the call and pertaining to the first SEA, into a table. Further in response to receiving the call, the hypervisor decides whether or not the first SEA of the virtual server should then be the primary SEA. The hypervisor sends a return call indicating its decision to the first SEA.

Abstract: A method, system and computer program product for transferring data between two applications over a local network connection. The invention establishes a socket connection between the applications and transfers data through the socket connection using a pseudo socket layer interface when the two endpoints of the socket connection are on the same host. Socket application program interface comprises socket buffers for sending and receiving data. A connecting application identifies and establishes a connection with a listening socket, and places data directly in the socket receive buffer of the receiving socket. If the other end of the socket connection is on a remote host, then data is transferred using underlying network facilities.

Abstract: Methods for migrating logical partitions. The method may include dynamically discovering a destination system for migration; remotely creating an environment on the destination system for accepting the runtime migration; and migrating a running logical partition from a source system to the destination system. The source system may be managed by a source management system and the destination system may be managed by a destination management system. Dynamically discovering the destination system for migration may comprise establishing a communications channel between the source management system and the destination management system; obtaining a list of candidate systems from the destination management system; and validating resources of at least one candidate system.

Abstract: A method, system and computer program product for transferring data between two applications over a local network connection. The invention establishes a socket connection between the applications and transfers data through the socket connection using a pseudo socket layer interface when the two endpoints of the socket connection are on the same host. Socket application program interface comprises socket buffers for sending and receiving data. A connecting application identifies and establishes a connection with a listening socket, and places data directly in the socket receive buffer of the receiving socket. If the other end of the socket connection is on a remote host, then data is transferred using underlying network facilities.

Abstract: Methods, systems, and products for migrating logical partitions. The method may include dynamically discovering a destination system for migration; remotely creating an environment on the destination system for accepting, the runtime migration; and migrating a running logical partition from a source system to the destination system. The source system may be managed by a source management system and the destination system may be managed by a destination management system. Dynamically discovering the destination system for migration may comprise establishing a communications channel between the source management system and the destination management system; obtaining a list of candidate systems from the destination management system; and validating resources of at least one candidate system.

Abstract: A host enables any adapter of multiple adapters of the host to concurrently support any VIPA of the multiple VIPAs assigned to the host. Responsive to a failure of at least one particular adapter from among the multiple adapters, the host triggers the remaining, functioning adapters to broadcast a separate hardware address update for each VIPA over the network, such that for a failover in the host supporting the multiple VIPAs the host directs at least one other host accessible via the network to address any new packets for the multiple VIPAs to one of the separate hardware addresses of one of the remaining adapters.

Abstract: A host enables any adapter of multiple adapters of the host to concurrently support any VIPA of the multiple VIPAs assigned to the host. Responsive to a failure of at least one particular adapter from among the multiple adapters, the host triggers the remaining, functioning adapters to broadcast a separate hardware address update for each VIPA over the network, such that for a failover in the host supporting the multiple VIPAs the host directs at least one other host accessible via the network to address any new packets for the multiple VIPAs to one of the separate hardware addresses of one of the remaining adapters.

Abstract: A computer implemented method, apparatus, and computer usable program code to determine whether an acknowledgment packet from an end point acknowledges receipt of unsent data in response to receiving the acknowledgement packet over a connection with the end point. A determination is made as to whether acknowledgement packets for unsent data have been received sequentially a selected number of times over the connection in response to the acknowledgement packet being for unsent data. The acknowledgment packet is dropped if acknowledgement packets have been received sequentially the selected number of times over the connection.

Abstract: A computer implemented method, apparatus, and computer usable program code to determine whether an acknowledgment packet from an end point acknowledges receipt of unsent data in response to receiving the acknowledgement packet over a connection with the end point. A determination is made as to whether acknowledgement packets for unsent data have been received sequentially a selected number of times over the connection in response to the acknowledgement packet being for unsent data. The acknowledgment packet is dropped if acknowledgement packets have been received sequentially the selected number of times over the connection.

Abstract: Methods, systems, and media to reduce delays associated with port assignments are disclosed. More specifically, embodiments include hardware and/or software to delay binding of selected port numbers to instances of applications. Some embodiments identify port numbers for which applications generate multiple bind calls that may connect with unique remote ports. The port numbers are stored in a port list that is accessible to the protocol stack and memory is allocated for storing flags and additional port configuration data. When a bind call is associated with a port number bound to another application instance and the port number is included in the port list, the bind call may then be delayed until a connect is received from the corresponding application instance. When the resulting four tuple is unique for the computer system, the corresponding application instance is bound to the port number and connected with the remote port.