Abstract: Methods, systems, and computer program products are provided for migrating an operating system from a source computer to a destination computer. Some embodiments include identifying a destination adapter of the destination computer that is coupled for data communications to a SAN that is also coupled for data communications to a source adapter of the source computer, logging off a virtual port name of the source adapter from the login manager, deregistering the virtual port name from the source adapter, registering the virtual port name with the destination adapter, and logging on the destination adapter to the login manager with the virtual port name. Typical embodiments also include transferring the operating system from the source computer to the destination computer.

Abstract: Methods, systems, and products are disclosed for implementing a generic kernel extension framework that operate generally to allow one kernel extension to register a function callable by other kernel extensions. A kernel extension can be loaded even if a function it potentially could need is not available. If in fact the running kernel extension does eventually request a function that no other kernel extension has registered to provide, it is failed gracefully with a return error code. The client kernel extension can still function normally, assuming the desired service is non-critical. Example services in the non-critical category may include, for example, advanced error handling functions, statistical functions, reporting functions, and so on, including many others as will occur to those of skill in the art.

Abstract: A method and system for providing multiple input/output paths for accessing storage devices includes providing two or more logical paths between a virtual I/O client partition and a storage device and establishing a physical path between the virtual I/O client partition and the storage device by assigning the storage device to a first logical path of the two or more logical paths. The method further includes reestablishing the physical path by dynamically assigning the storage device to a second logical path of the two or more logical paths in an event of unavailability of the first logical path.

Abstract: When a hypervisor in a computer server receives input/output (I/O) data traffic, the hypervisor sends the I/O data traffic to a security sensor application shared by multiple operating system (OS) partitions. If the security sensor application indicates that the I/O data traffic meets pre-defined security standards in the security sensor application, and the I/O data traffic is addressed to one of the OS partitions in the computer server, the hypervisor sends the I/O data traffic to the applicable OS partition. If the I/O data traffic meets the pre-defined security standards, and the I/O data traffic is not addressed to one of the OS partitions, the hypervisor sends the I/O data traffic to an external destination in a network coupled to the computer server.

Abstract: A system, method, and program product is provided that receives a backup request at a virtual input/output server (VIOS) from a client of the VIOS. The backup request corresponds to a virtual nonvolatile storage that is used by the client. The VIOS retrieves data from the nonvolatile storage device where the virtual nonvolatile storage is stored. The VIOS transmits the retrieved data to a backup server via a computer network, such as the Internet. In one embodiment, a backup software application runs on the VIOS client and a backup proxy software application runs on the VIOS.

Abstract: A method and system for providing multiple input/output paths for accessing storage devices includes providing two or more logical paths between a virtual I/O client partition and a storage device and establishing a physical path between the virtual I/O client partition and the storage device by assigning the storage device to a first logical path of the two or more logical paths. The method further includes reestablishing the physical path by dynamically assigning the storage device to a second logical path of the two or more logical paths in an event of unavailability of the first logical path.

Abstract: A system, method, and program product is provided that receives a backup request at a virtual input/output server (VIOS) from a client of the VIOS. The backup request corresponds to a virtual nonvolatile storage that is used by the client. The VIOS retrieves data from the nonvolatile storage device where the virtual nonvolatile storage is stored. The VIOS transmits the retrieved data to a backup server via a computer network, such as the Internet. In one embodiment, a backup software application runs on the VIOS client and a backup proxy software application runs on the VIOS.

Abstract: In traditional Fiber Channel systems, remote devices connected to the Fiber Channel network using a bridge or included in a storage enclosure are not tracked. If a remote device, such as a SCSI disk device, is removed or swapped, data errors such as data corruption can result. A device identifier corresponding to the remote device is obtained from the remote device. The device identifier may include the remote device's serial number and other identifying information pertaining to the device. The first time the remote device is used, the device identifier is obtained and stored by the Fiber Channel device using the remote device. This device identifier is compared with subsequently obtained identifiers. If the identifiers match, communication with the remote device occurs. However, if the identifiers do not match, an error condition is raised indicating that the remote device has been removed or swapped.

Abstract: In traditional Fibre Channel systems, remote devices connected to the Fibre Channel network using a bridge or included in a storage enclosure are not tracked. A device identifier corresponding to the remote device is obtained from the remote device. The device identifier may include the remote device's serial number and other identifying information pertaining to the device. The remote device's vendor and product identifiers are retrieved and matched against a table of known vendor/product identifiers. If the match is successful, a predefined routine is located based on the match. The predefined routine is repeatedly used to retrieve the device identifier from the remote device. Communication with the remote device continues while the device identifier matches a previously stored device identifier corresponding to the device. When the device identifier no longer matches, an error occurs indicating that the remote device has been removed or swapped.

Abstract: A method and an apparatus is presented for preventing an adapter card that has been reset from issuing spurious error signals due to the fact it is not synchronized with the system at the time it comes out of reset. To prevent spurious errors, the data processing issues a command to the adapter card that is to be reset that disables error checking before the reset command is sent. The reset command is sent next. After the adapter card completes the reset operation, it notifies the system that the reset is completed. The adapter card waits until it receives a command from the system to re-enable error checking before it turns back on error checking. In this manner, the system can insure that error checking is only turned back on synchronously with other system activities so that spurious error signals are not generated.

Abstract: A method, apparatus, and computer implemented instructions for isolating failing hardware in a data processing system. In response to detecting a recovery attempt from an error, an indication of the attempt is stored. A hardware component associated with the error is placed in an unavailable state in response to the error exceeding a threshold for errors.

Abstract: In traditional Fibre Channel systems, remote devices connected to the Fibre Channel network using a bridge or included in a storage enclosure are not tracked. If a remote device, such as a SCSI disk device, is removed or swapped, data errors such as data corruption can result. A device identifier corresponding to the remote device is obtained from the remote device. The device identifier may include the remote device's serial number and other identifying information pertaining to the device. The first time the remote device is used, the device identifier is obtained and stored by the Fibre Channel device using the remote device. The device identifier is obtained by repeatedly querying the remote device to identify the device's serial number. Communication with the remote device takes place if the identified device identifier matches the previously stored device identifier. An error condition occurs if the identifiers do not match.

Abstract: In traditional Fiber Channel systems, remote devices connected to the Fiber Channel network using a bridge or included in a storage enclosure are not tracked. If a remote device, such as a SCSI disk device, is removed or swapped, data errors such as data corruption can result. A device identifier corresponding to the remote device is obtained from the remote device. The device identifier may include the remote device's serial number and other identifying information pertaining to the device. The first time the remote device is used, the device identifier is obtained and stored by the Fiber Channel device using the remote device. This device identifier is compared with subsequently obtained identifiers. If the identifiers match, communication with the remote device occurs. However, if the identifiers do not match, an error condition is raised indicating that the remote device has been removed or swapped.

Abstract: In traditional Fibre Channel systems, remote devices connected to the Fibre Channel network using a bridge or included in a storage enclosure are not tracked. A device identifier corresponding to the remote device is obtained from the remote device. The device identifier may include the remote device's serial number and other identifying information pertaining to the device. The remote device's vendor and product identifiers are retrieved and matched against a table of known vendor/product identifiers. If the match is successful, a predefined routine is located based on the match. The predefined routine is repeatedly used to retrieve the device identifier from the remote device. Communication with the remote device continues while the device identifier matches a previously stored device identifier corresponding to the device. When the device identifier no longer matches, an error occurs indicating that the remote device has been removed or swapped.