International Business Machines Corporation

Globalfoundries Inc.

Marcus Bryan Grande

Brian W Hart

Baltazar De Leon, Iii

Vikramjit Sethi

James P Allen

Robert G Kovacs

Omar Cardona

John Leslie Neemidge

Tai-Chien Daisy Chang

Jaime F Nualart

Madhuranath Narasipur Krishna Iyengar

Marshon Larapheal Robinson

A method and technique for updating firmware on a multi-protocol network adapter includes reading parameter values for a firmware update of a multi-protocol network adapter that specify classes of behavior for conducting the firmware update of the multi-protocol network adapter. An update tool determines a reset type defining a type of reset needed to activate the firmware update on the network adapter based on the parameter values, sends a message to the network adapter indicating that a firmware update process is beginning, sends a write request to the network adapter to write the firmware update to select communication protocol functions, and sends a reset request to select communication protocol functions to activate the firmware update using the reset type according to the parameter values.

Unified update tool for multi-protocol network adapter

A method and technique for updating firmware on a multi-protocol network adapter includes: reading parameter values for a firmware update to determine an update scope indicating one or more functions of the network adapter affected by the firmware update and a write scope indicating which of the one or more functions should receive a write request for writing the firmware update to the network adapter. The update tool is operable to: send a message indicating to the one or more functions based on the update scope that a firmware update process is beginning; send a write request to write the firmware update to the one or more functions based on the write scope; send a reset request to reset the one or more functions to activate the firmware update; and send a message indicating to the one or more functions that the firmware update process is completed.

A method of firmware dump collection from a primary dump adapter is provided. The method includes identifying a primary system dump device and a secondary system dump device. An operating system (OS) dump coordinator writes non-disruptive state data to the primary system dump device, and writes disruptive state data to the secondary system dump device. Non-disruptive state data is requested from a hardware device adapter that is connected to the non-primary system dump device. Disruptive state data is requested from the hardware device adapter that is connected to the primary system dump device. The non-disruptive state data is written to the primary system dump device. Disruptive state data is written to the secondary system dump device.

Firmware dump collection from primary system dump device adapter

An approach is provided that collects data from a multi-function adapter that is used by multiple functions. In the approach, a master function is dynamically selected from the group of functions. The approach further allows the master function to perform a disruptive adapter data collection while inhibiting performance of disruptive adapter data collection processes by the other (non-master) functions.

Dynamic data collection communication between adapter functions

Mechanisms are provided for generating a system dump data structure based on device state data. A system dump operation is initialized in a data processing system and a device dump is requested by a dump manager from a device coupled to the data processing system. A collection scope data structure and disruption vector corresponding to the device are retrieved. The collection scope data structure specifies a set of one or more functions in the device for which to collect state data. The disruption vector specifies, for each of the one or more functions, a corresponding level of disruption that will be caused by the device dump. The device dump data is collected from the device in accordance with the collection scope data structure and the disruption vector and the system dump data structure is generated based on the collected device dump data.

Device state capture during operating system dump

A system and method for managing a Fibre Channel adapter is disclosed. When a close request is received by the Fibre Channel adapter, the adapter is set to a quasi-open state. In a quasi-open state, the adapter keeps the link to the Fibre Channel network open, releases extended resources, and maintains minimal resources in order to keep the link open. When a request is received by the adapter while in a quasi-open state, the request is rejected thereby preventing other devices from logging into the quasi-opened device and informing other devices that the quasi-opened device is not currently communicating across the Fibre Channel network. An information handling system and a computer program product for implementing the Fibre Channel adapter quasi-open state are further disclosed.

System and method for efficient management of fibre channel communication

A system and method for remotely waking up a Fibre Channel attached device. A Fibre Channel attached device is set in a quasi-open mode wherein the device summarily rejects most requests and allocates a minimal set of resources to operate the adapter. One request that is not rejected is an activation request received from another Fibre Channel attached device. When an activation request is received, an optional authentication process can be invoked to insure that only authenticated devices issue the activation command. An additional security feature can be used to restrict the devices authorized to activate a device. A list of devices can be stored on nonvolatile storage or in memory. When a requesting device has been authenticated, its address is checked against the list of approved devices before the device adapter is activated.

System and method for fiber channel remote activation and enhanced security

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.

System and method for improved handling of fiber channel remote devices

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.

System and method for fibre channel tracking of SCSI identifiers in known configurations

A GPS device is used in conjunction with a device, such as a SAN device, to record and track the device's location. A device can periodically report its location to one or more computer systems that track device locations. Another device can send a request to other devices requesting the devices' geographic location. The devices, in turn, respond with data corresponding to their geographic location. In the event of a catastrophe or other event rendering devices in one area inoperable, one of the computer systems can be used to identify a location of another device that includes similar data. The GPS data corresponding to a device can also be used to identify a technician that should respond to a device maintenance or repair event.

Growing community of inventors

Pflugerville, TX, United States of America

Marcus Bryan Grande