US20080184271A1 - Automated Diagnostic Service - Google Patents

Automated Diagnostic Service Download PDF

Info

Publication number
US20080184271A1
US20080184271A1 US12/020,864 US2086408A US2008184271A1 US 20080184271 A1 US20080184271 A1 US 20080184271A1 US 2086408 A US2086408 A US 2086408A US 2008184271 A1 US2008184271 A1 US 2008184271A1
Authority
US
United States
Prior art keywords
diagnostic
data processing
code
site
alert
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US12/020,864
Other versions
US7865781B2 (en
Inventor
Thomas James Fox
Eric R. Kern
Charles Christian Queen
Celia Anne Schreiber
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Appvision Corp
Lot Network Inc
Original Assignee
International Business Machines Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by International Business Machines Corp filed Critical International Business Machines Corp
Priority to US12/020,864 priority Critical patent/US7865781B2/en
Publication of US20080184271A1 publication Critical patent/US20080184271A1/en
Application granted granted Critical
Publication of US7865781B2 publication Critical patent/US7865781B2/en
Assigned to LENOVO INTERNATIONAL LIMITED reassignment LENOVO INTERNATIONAL LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: INTERNATIONAL BUSINESS MACHINES CORPORATION
Assigned to LOT NETWORK INC. reassignment LOT NETWORK INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LENOVO INTERNATIONAL LIMITED
Assigned to APPVISION CORP. reassignment APPVISION CORP. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LOT NETWORK INC.
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/50Testing arrangements

Definitions

  • the present invention generally relates to the field of data processing systems and networks and more particularly to performing diagnostic routines on such systems and networks.
  • Performing conventional diagnostics on data processing systems and networks of such systems requires the manual intervention of a systems manager, field service engineer, or the like.
  • the systems manager identifies a problem associated with a particular element of the system, perhaps in response to some form of interrupt, warning message, or other alert generated by a system element. In other cases, the systems manager may simply suspect that a system has a problem.
  • the systems manager then typically gathers information regarding the problematic element and downloads the latest version of diagnostics for the system or element in question. Once downloaded, the systems manager installs the software on the system, runs the diagnostic, analyzes the results, and determines how to fix the problem.
  • the method of diagnosing a system requires a level of human interaction that is undesirably high. It would be beneficial to implement a method and system to automate the diagnostic function to the greatest extent possible.
  • the diagnostic method includes retrieving product data identifying a data processing element in response to an alert generated by the element.
  • the retrieved product data is forwarded to a networked diagnostic site.
  • a diagnostic package is retrieved, the diagnostic package including diagnostic code appropriate for the alerting element.
  • the diagnostic package is forwarded to the data processing system.
  • the diagnostic code is then installed and executed to perform diagnostic testing of the element. Results generated during execution of the diagnostic code may then be used to take machine initiated corrective action.
  • the diagnostic site may be a site on the Internet or a local replica of such a site.
  • FIG. 1 is a block diagram of selected elements of a server, server blade, or blade suitable for use in various embodiments of the invention
  • FIG. 2 illustrates selected elements of a blade center data processing network suitable for use in various embodiments of the invention
  • FIG. 3 depicts selected elements of a local area network emphasizing automated diagnostic servicing elements of the present invention.
  • FIG. 4 is a flow diagram illustrating a method of providing data processing system diagnostic services according to one embodiment of the invention.
  • the present invention contemplates an automated diagnostic service method and system for use in a networked data processing environment.
  • Software or hardware elements in a particular system or network generate alerts in response to problems. These alerts are routed to a management agent that then retrieves information about the problem element. Using the element information, the management agent accesses a diagnostic database to retrieve the most current diagnostic routine available for the problem element. The diagnostic routine is then installed on the problem system, executed, and the resulting diagnostic information is retrieved by the management agent. Based on the results of the diagnostic run, the management agent takes corrective action, if possible, such as downloading an updated driver for a system component
  • FIG. 1 is a block diagram of selected features of a data processing system 100 suitable for use in conjunction with the present invention.
  • the depicted elements of data processing system 100 may be implemented entirely upon a single printed circuit board.
  • data processing system 100 may be alternatively referred to herein as server blade 100 .
  • server blade 100 includes a set of main processors 102 A through 102 N (generically or collectively referred to as processor(s) 102 ) that are connected to a system bus 104 .
  • a common system memory 106 is accessible to each processor 102 via system bus 104 .
  • the system memory is typically implemented with a volatile storage medium such as an array of dynamic random access memory (DRAM) devices.
  • DRAM dynamic random access memory
  • the depicted architecture of server blade 100 is frequently referred to as a symmetric multiprocessor (SMP) system because each processor 102 has substantially equal access to system memory 106 .
  • SMP symmetric multiprocessor
  • a bus bridge 108 provides an interface between system bus 104 and an I/O bus 110 .
  • One or more peripheral devices 114 A through 114 N (generically or collectively referred to as peripheral device(s) 114 ) as well as a general purpose I/O (GPIO) port 112 are connected to I/O bus 110 .
  • Peripheral devices 114 may include devices such as a graphics adapter, a high-speed network adapter or network interface card (NIC), a hard-disk controller, and the like.
  • I/O bus 110 is typically compliant with one of several industry standard I/O bus specifications including, as a common example, the Peripheral Components Interface (PCI) bus as specified in PCI Local Bus Specification Rev 2.2 by the PCI Special Interest Group (www.pcisig.com).
  • PCI Peripheral Components Interface
  • server blade 100 includes a local service processor 116 connected to GPIO port 112 .
  • Local service processor 116 is configured to provide support for main processors 102 . This support may include, for example, monitoring the power supplied to main processor(s) 102 and, in the event of a blade crash, initiating a restart of the main processors.
  • Data processing network 111 also referred to as a blade center 111 , includes a rack enclosure or cabinet 121 that includes a plurality of slots or racks 122 .
  • Each rack 122 is configured to receive a rack mounted device such as a server blade chassis identified by reference numerals 101 a through 101 n (generically or collectively referred to as server blade chassis 101 ) via a suitable connection mechanism such as a traditional edge connector.
  • Each server blade chassis 101 typically contains one or more server blades 100 as described with respect to FIG. 1 .
  • each server blade chassis 101 is a 4U component that may include as many as 16 server blades 100 .
  • blade center 111 includes a set of server blade chassis 101 , each of which includes one or more server blades 100 .
  • Each server blade 100 within server blade chassises 111 a through 101 n is typically connected to a local area network (LAN) through its NIC(s) such that server blades 100 in system 111 can communicate with each other.
  • Blade center 111 may itself be connected to a local area network or intranet to which other blade centers, servers, and other network devices are connected. The entire local area network is likely connected to an external wide area network, such as the Internet, through a gateway or other suitable network device.
  • server blade 100 includes a local service processor 116 configured to monitor the blade's main processor(s) 102 .
  • Network 111 as depicted in FIG. 2 further includes a system management module 120 that is inserted into a slot 124 in cabinet 121 .
  • the dimension of management module 120 is different than the dimension of server blades 100 and management module slot 124 is sized to receive management module 120 while preventing inadvertent insertion of a server blade 100 into the slot.
  • Management module 120 is typically implemented with a management module service processor configured to monitor and control resources and characteristics of network 111 that are shared by each server blade 100 . These resources and characteristics may include, for example, the power applied to cabinet 121 , cabinet cooling fans, and environmental characteristics such as the ambient temperature within cabinet 121 .
  • Portions of the present invention may be implemented as a sequence of processor executable instructions (software) for performing diagnostic servicing of a data processing network where the instructions are stored on a computer readable medium.
  • portions of the software may reside in a volatile storage element such as the system memory 106 depicted in FIG. 1 or an external or internal cache memory (not depicted) of main processor(s) 102 .
  • portions of the software may be stored on a non-volatile storage medium such as a floppy diskette, hard disk, CD ROM, DVD, magnetic tape, or other suitable storage medium.
  • management module 120 may execute portions of the software while the local service processors 116 of each server blade 100 may execute other portions.
  • LAN 117 includes a set of interconnected data processing systems and a management server 125 all connected to an Ethernet intranet 130 although token ring and other network connectivity implementations may be used.
  • Management server 125 is a dedicated server for monitoring the configuration and functionality of the data processing elements in LAN 117 .
  • Management module 120 is configured to facilitate communication between blade center 111 and management server 125 .
  • the set of interconnected data processing systems in LAN 117 is implemented as a blade center 111 that includes a set of server blades 100 and a management module 120 although this is also an implementation detail.
  • the collection of data processing devices may be implemented with conventional standalone server systems, desktop systems, workstations, and so forth.
  • management network 123 enables communication between management server 125 and one or more management modules 120 outside of or sideband with respect to intranet 130 thereby enabling management functionality independent of the functional status of intranet 130 .
  • Management network 123 can be an Ethernet link or any of various industry standard serial busses such as I2C, RS-232, USB, and the like.
  • the diagnostic service elements of the present invention work in conjunction with a network accessible diagnostic web site or other form of data center.
  • the diagnostic data center is represented by an external diagnostic site 140 , accessible via a wide area network (WAN) 135 such as the Internet through a firewall 132 , and a local replica 128 of site 140 , accessible via intranet 130 .
  • Diagnostic sites 128 and 140 include one or more diagnostic programs, routines, sequences, and so forth suitable for diagnosing various data processing hardware and software elements.
  • a provider of diagnostic servicing is responsible for maintaining the content of diagnostic site 140 with the most current diagnostic routines available for all of the elements of the major functional elements of LAN 117 .
  • the diagnostic routines that are found on sites 140 and 128 include code that can be downloaded, installed, executed, and uninstalled by a remote agent.
  • Automated diagnostic servicing is achieved by configuring management module 120 and management server 125 to communicate critical information in response to an alert generated by any of the blades 100 or other data processing elements of blade center 111 .
  • the data processing elements that may generate an alert include any device, subsystem, or software (DSS) in blade center 111 .
  • the information communicated to management server 125 in response to an alert includes vital product data (VPD) that uniquely identifies the alerting DSS to management module 120 .
  • VPD vital product data
  • Each blade 100 as well as other subsystems and software may have unique VPD codes associated with them. In the case of a blade 100 , for example, the VPD code is likely stored in non-volatile memory on the blade.
  • Management module 120 is configured to access local diagnostic site 128 , external diagnostic site 140 , or both upon receiving an alert indicator and the associated VPD. Using the VPD, management module 120 submits a request to the appropriate diagnostic site. The diagnostic site, in turn, uses the VPD to locate diagnostic code appropriate for the alerting DSS. The diagnostic code located by the diagnostic site is then downloaded to management server 125 . Management server 125 then installs the downloaded code on the appropriate system, perhaps in conjunction with management module 120 , and initiates execution of the diagnostic code. When diagnostic code execution completes, the code can be uninstalled to conserve valuable storage. In addition, management server 125 may then analyze the diagnostic results and, if appropriate, take corrective action including, as an example, updating old or corrupted firmware or drivers.
  • Diagnostic servicing begins when an element of the data processing network generates (block 202 ) an alert.
  • the alerting element can be a software element, a device such as a blade 100 , a subsystem such as a network interface card or a disk drive.
  • the alert itself can originate from a hardware interrupt, an operating system error message or warning, or from an application program.
  • Management server 125 may receive the alert directly via intranet 130 or indirectly from management module 120 via the management network 123 .
  • management server 125 retrieves or determines (block 204 ) the identity of the alerting DSS.
  • the identity information includes vital product data (VPD) that uniquely identifies the alerting DSS.
  • Management server 125 then forwards (block 206 ) the VPD and any other information needed to identify the alerting DSS to a network-connected diagnostic site.
  • the diagnostic site can be, for example, a site 140 on an external network such as the Internet or a local replica 128 of the external site. In either case, the diagnostic site is enabled to receive, from a network, information identifying a particular DSS in a system connected to the web site. As its name suggests, the diagnostic site has access to an archive of diagnostic programs and routine for different data processing systems, devices, and software. The diagnostic site responds to the receipt of DSS identification information by using the VPD to create (block 208 ) a download package tailored for the alerting DSS.
  • the download package includes diagnostic code that, when executed on the alerting DSS, performs an appropriate diagnostic check of the DSS.
  • the diagnostic site may compress, encrypt, or otherwise format the diagnostic code for secure and efficient transport over the network.
  • the diagnostic site then delivers (block 210 ) the download package to LAN 117 and, more specifically, to management server 125 .
  • management server 125 Upon receiving a download package from a diagnostic site, management server 125 deploys (block 212 ) the download package to the blade or server 100 in which the alerting DSS resides. The server receiving the download package then auto installs (block 214 ) and executes the diagnostic code. The diagnostic code will typically produce diagnostic results containing information about any problems encountered by the diagnostic code. When execution of the diagnostic code completes, the results are stored, and the diagnostic code is uninstalled from the server. An alert containing the diagnostic results is then generated and forwarded (block 216 ) to the management server 125 .
  • Management server 125 is enabled to analyze (block 218 ) the diagnostic results contained in a results alert. If the management server is capable of resolving the problem indicated by the diagnostic results, it will perform the appropriate corrective action. Otherwise, the management server will notify the service provider to schedule a field service visit to address problems that could not be resolved by the management server on its own.
  • a company may backup its data to tape every Saturday at 2:00 a.m. If a problem is encountered while performing this backup, the backup application or a monitoring daemon or both analyzes the tape drive for problems. If a problem is detected, an alert is generated and published with the problem information. Management server 125 receives this alert and collects the latest diagnostic support file from the external diagnostic site 140 .
  • the diagnostic software on the diagnostic site may be provided by the vendor of the alerting device, by the provider of the diagnostic servicing, or both.
  • the management server then pushes the diagnostic package down to the managed server where the problem occurred. The package is automatically installed, executed, and uninstalled.
  • the results of the diagnostic code are packaged into an alert and sent back to the Management Server 125 .
  • the management server 125 Upon receiving the data, the management server 125 performs problem determination on the data to determine the proper corrective action. If the corrective action can be performed by the management server 125 (e.g., firmware downlevel or driver downlevel), it performs the corrective action. Otherwise, the corrective action is published by alerting the diagnostic service provider with all appropriate information. If the problem is fixed with a firmware/driver update, the server with the tape drive has fixed itself and the next backup will proceed smoothly.

Abstract

A method of providing diagnostic service for a data processing system includes retrieving product data identifying a data processing element in response to an alert generated by the element. The retrieved product data is forwarded to a networked diagnostic site. A diagnostic package is retrieved, the diagnostic package including diagnostic code appropriate for the alerting element. The diagnostic package is forwarded to the data processing system. The diagnostic code is then installed and executed to perform diagnostic testing of the element. Results generated during execution of the diagnostic code may then be used to take machine initiated corrective action. After the results have been generated, the diagnostic software is uninstalled from the data processing system.

Description

    CROSS-REFERENCE TO RELATED APPLICATION
  • This application is a continuation application of and claims priority from U.S. patent application Ser. No. 10/462,254, filed on Jun. 16, 2003.
  • BACKGROUND
  • 1. Field of the Present Invention The present invention generally relates to the field of data processing systems and networks and more particularly to performing diagnostic routines on such systems and networks.
  • 2. History of Related Art
  • Performing conventional diagnostics on data processing systems and networks of such systems requires the manual intervention of a systems manager, field service engineer, or the like. Typically, the systems manager identifies a problem associated with a particular element of the system, perhaps in response to some form of interrupt, warning message, or other alert generated by a system element. In other cases, the systems manager may simply suspect that a system has a problem. The systems manager then typically gathers information regarding the problematic element and downloads the latest version of diagnostics for the system or element in question. Once downloaded, the systems manager installs the software on the system, runs the diagnostic, analyzes the results, and determines how to fix the problem. The method of diagnosing a system requires a level of human interaction that is undesirably high. It would be beneficial to implement a method and system to automate the diagnostic function to the greatest extent possible.
  • SUMMARY OF THE INVENTION
  • The goal identified above is achieved by a method of providing diagnostic service for a data processing system according to the present invention. The diagnostic method includes retrieving product data identifying a data processing element in response to an alert generated by the element. The retrieved product data is forwarded to a networked diagnostic site. A diagnostic package is retrieved, the diagnostic package including diagnostic code appropriate for the alerting element. The diagnostic package is forwarded to the data processing system. The diagnostic code is then installed and executed to perform diagnostic testing of the element. Results generated during execution of the diagnostic code may then be used to take machine initiated corrective action. The diagnostic site may be a site on the Internet or a local replica of such a site.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Other objects and advantages of the invention will become apparent upon reading the following detailed description and upon reference to the accompanying drawings in which:
  • FIG. 1 is a block diagram of selected elements of a server, server blade, or blade suitable for use in various embodiments of the invention;
  • FIG. 2 illustrates selected elements of a blade center data processing network suitable for use in various embodiments of the invention;
  • FIG. 3 depicts selected elements of a local area network emphasizing automated diagnostic servicing elements of the present invention; and
  • FIG. 4 is a flow diagram illustrating a method of providing data processing system diagnostic services according to one embodiment of the invention.
  • While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the drawings and detailed description presented herein are not intended to limit the invention to the particular embodiment disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present invention as defined by the appended claims.
  • DETAILED DESCRIPTION OF THE INVENTION
  • Generally speaking, the present invention contemplates an automated diagnostic service method and system for use in a networked data processing environment. Software or hardware elements in a particular system or network generate alerts in response to problems. These alerts are routed to a management agent that then retrieves information about the problem element. Using the element information, the management agent accesses a diagnostic database to retrieve the most current diagnostic routine available for the problem element. The diagnostic routine is then installed on the problem system, executed, and the resulting diagnostic information is retrieved by the management agent. Based on the results of the diagnostic run, the management agent takes corrective action, if possible, such as downloading an updated driver for a system component
  • Turning now to the drawings, FIG. 1 is a block diagram of selected features of a data processing system 100 suitable for use in conjunction with the present invention. The depicted elements of data processing system 100 may be implemented entirely upon a single printed circuit board. In this embodiment, data processing system 100 may be alternatively referred to herein as server blade 100. In the depicted embodiment, server blade 100 includes a set of main processors 102A through 102N (generically or collectively referred to as processor(s) 102) that are connected to a system bus 104. A common system memory 106 is accessible to each processor 102 via system bus 104. The system memory is typically implemented with a volatile storage medium such as an array of dynamic random access memory (DRAM) devices. The depicted architecture of server blade 100 is frequently referred to as a symmetric multiprocessor (SMP) system because each processor 102 has substantially equal access to system memory 106.
  • In the depicted embodiment of server blade 100, a bus bridge 108 provides an interface between system bus 104 and an I/O bus 110. One or more peripheral devices 114A through 114N (generically or collectively referred to as peripheral device(s) 114) as well as a general purpose I/O (GPIO) port 112 are connected to I/O bus 110. Peripheral devices 114 may include devices such as a graphics adapter, a high-speed network adapter or network interface card (NIC), a hard-disk controller, and the like. I/O bus 110 is typically compliant with one of several industry standard I/O bus specifications including, as a common example, the Peripheral Components Interface (PCI) bus as specified in PCI Local Bus Specification Rev 2.2 by the PCI Special Interest Group (www.pcisig.com).
  • The depicted embodiment of server blade 100 includes a local service processor 116 connected to GPIO port 112. Local service processor 116 is configured to provide support for main processors 102. This support may include, for example, monitoring the power supplied to main processor(s) 102 and, in the event of a blade crash, initiating a restart of the main processors.
  • Turning now to FIG. 2, selected elements of a data processing network 111 according to one implementation of the present invention is depicted. Data processing network 111, also referred to as a blade center 111, includes a rack enclosure or cabinet 121 that includes a plurality of slots or racks 122. Each rack 122 is configured to receive a rack mounted device such as a server blade chassis identified by reference numerals 101 a through 101 n (generically or collectively referred to as server blade chassis 101) via a suitable connection mechanism such as a traditional edge connector. Each server blade chassis 101 typically contains one or more server blades 100 as described with respect to FIG. 1. In one implementation, each server blade chassis 101 is a 4U component that may include as many as 16 server blades 100. Thus, the depicted embodiment of blade center 111 includes a set of server blade chassis 101, each of which includes one or more server blades 100. Each server blade 100 within server blade chassises 111 a through 101 n is typically connected to a local area network (LAN) through its NIC(s) such that server blades 100 in system 111 can communicate with each other. Blade center 111 may itself be connected to a local area network or intranet to which other blade centers, servers, and other network devices are connected. The entire local area network is likely connected to an external wide area network, such as the Internet, through a gateway or other suitable network device.
  • As discussed with respect to FIG. 1, one embodiment of server blade 100 includes a local service processor 116 configured to monitor the blade's main processor(s) 102. Network 111 as depicted in FIG. 2 further includes a system management module 120 that is inserted into a slot 124 in cabinet 121. In the depicted embodiment, the dimension of management module 120 is different than the dimension of server blades 100 and management module slot 124 is sized to receive management module 120 while preventing inadvertent insertion of a server blade 100 into the slot. Management module 120 is typically implemented with a management module service processor configured to monitor and control resources and characteristics of network 111 that are shared by each server blade 100. These resources and characteristics may include, for example, the power applied to cabinet 121, cabinet cooling fans, and environmental characteristics such as the ambient temperature within cabinet 121.
  • Portions of the present invention may be implemented as a sequence of processor executable instructions (software) for performing diagnostic servicing of a data processing network where the instructions are stored on a computer readable medium. During execution, portions of the software may reside in a volatile storage element such as the system memory 106 depicted in FIG. 1 or an external or internal cache memory (not depicted) of main processor(s) 102. At other times, portions of the software may be stored on a non-volatile storage medium such as a floppy diskette, hard disk, CD ROM, DVD, magnetic tape, or other suitable storage medium. In addition, management module 120 may execute portions of the software while the local service processors 116 of each server blade 100 may execute other portions.
  • Referring now to FIG. 3, selected elements of a local area network or LAN 117 suitable for use with an embodiment of the present invention is depicted. LAN 117 includes a set of interconnected data processing systems and a management server 125 all connected to an Ethernet intranet 130 although token ring and other network connectivity implementations may be used. Management server 125 is a dedicated server for monitoring the configuration and functionality of the data processing elements in LAN 117. Management module 120 is configured to facilitate communication between blade center 111 and management server 125.
  • In the depicted embodiment, the set of interconnected data processing systems in LAN 117 is implemented as a blade center 111 that includes a set of server blades 100 and a management module 120 although this is also an implementation detail. In other embodiments, the collection of data processing devices may be implemented with conventional standalone server systems, desktop systems, workstations, and so forth.
  • In the depicted embodiment of LAN 117, the management module 120 of blade center 111 is connected to management server 125 by a dedicated link referred to herein as management network 123. Management network 123 enables communication between management server 125 and one or more management modules 120 outside of or sideband with respect to intranet 130 thereby enabling management functionality independent of the functional status of intranet 130. Management network 123 can be an Ethernet link or any of various industry standard serial busses such as I2C, RS-232, USB, and the like.
  • The diagnostic service elements of the present invention work in conjunction with a network accessible diagnostic web site or other form of data center. In the depicted embodiment of LAN 117, the diagnostic data center is represented by an external diagnostic site 140, accessible via a wide area network (WAN) 135 such as the Internet through a firewall 132, and a local replica 128 of site 140, accessible via intranet 130. Diagnostic sites 128 and 140 include one or more diagnostic programs, routines, sequences, and so forth suitable for diagnosing various data processing hardware and software elements. A provider of diagnostic servicing is responsible for maintaining the content of diagnostic site 140 with the most current diagnostic routines available for all of the elements of the major functional elements of LAN 117. The diagnostic routines that are found on sites 140 and 128 include code that can be downloaded, installed, executed, and uninstalled by a remote agent.
  • Automated diagnostic servicing is achieved by configuring management module 120 and management server 125 to communicate critical information in response to an alert generated by any of the blades 100 or other data processing elements of blade center 111. The data processing elements that may generate an alert include any device, subsystem, or software (DSS) in blade center 111. The information communicated to management server 125 in response to an alert includes vital product data (VPD) that uniquely identifies the alerting DSS to management module 120. Each blade 100 as well as other subsystems and software may have unique VPD codes associated with them. In the case of a blade 100, for example, the VPD code is likely stored in non-volatile memory on the blade.
  • Management module 120 is configured to access local diagnostic site 128, external diagnostic site 140, or both upon receiving an alert indicator and the associated VPD. Using the VPD, management module 120 submits a request to the appropriate diagnostic site. The diagnostic site, in turn, uses the VPD to locate diagnostic code appropriate for the alerting DSS. The diagnostic code located by the diagnostic site is then downloaded to management server 125. Management server 125 then installs the downloaded code on the appropriate system, perhaps in conjunction with management module 120, and initiates execution of the diagnostic code. When diagnostic code execution completes, the code can be uninstalled to conserve valuable storage. In addition, management server 125 may then analyze the diagnostic results and, if appropriate, take corrective action including, as an example, updating old or corrupted firmware or drivers.
  • Referring now to the flow diagram of FIG. 4, a method 200 of providing diagnostic services for a data processing system or network is presented. Diagnostic servicing as depicted in FIG. 4 begins when an element of the data processing network generates (block 202) an alert. As described above, the alerting element (DSS) can be a software element, a device such as a blade 100, a subsystem such as a network interface card or a disk drive. The alert itself can originate from a hardware interrupt, an operating system error message or warning, or from an application program.
  • In the environment of LAN 117 as shown in FIG. 3, an alert is handled by management server 125. Management server 125 may receive the alert directly via intranet 130 or indirectly from management module 120 via the management network 123. In response to an alert, management server 125 retrieves or determines (block 204) the identity of the alerting DSS. The identity information according to one embodiment includes vital product data (VPD) that uniquely identifies the alerting DSS.
  • Management server 125 then forwards (block 206) the VPD and any other information needed to identify the alerting DSS to a network-connected diagnostic site. In LAN 117 as depicted in FIG. 3, the diagnostic site can be, for example, a site 140 on an external network such as the Internet or a local replica 128 of the external site. In either case, the diagnostic site is enabled to receive, from a network, information identifying a particular DSS in a system connected to the web site. As its name suggests, the diagnostic site has access to an archive of diagnostic programs and routine for different data processing systems, devices, and software. The diagnostic site responds to the receipt of DSS identification information by using the VPD to create (block 208) a download package tailored for the alerting DSS. The download package includes diagnostic code that, when executed on the alerting DSS, performs an appropriate diagnostic check of the DSS. The diagnostic site may compress, encrypt, or otherwise format the diagnostic code for secure and efficient transport over the network. The diagnostic site then delivers (block 210) the download package to LAN 117 and, more specifically, to management server 125.
  • Upon receiving a download package from a diagnostic site, management server 125 deploys (block 212) the download package to the blade or server 100 in which the alerting DSS resides. The server receiving the download package then auto installs (block 214) and executes the diagnostic code. The diagnostic code will typically produce diagnostic results containing information about any problems encountered by the diagnostic code. When execution of the diagnostic code completes, the results are stored, and the diagnostic code is uninstalled from the server. An alert containing the diagnostic results is then generated and forwarded (block 216) to the management server 125.
  • Management server 125 is enabled to analyze (block 218) the diagnostic results contained in a results alert. If the management server is capable of resolving the problem indicated by the diagnostic results, it will perform the appropriate corrective action. Otherwise, the management server will notify the service provider to schedule a field service visit to address problems that could not be resolved by the management server on its own.
  • Illustrating an application of the invention, a company may backup its data to tape every Saturday at 2:00 a.m. If a problem is encountered while performing this backup, the backup application or a monitoring daemon or both analyzes the tape drive for problems. If a problem is detected, an alert is generated and published with the problem information. Management server 125 receives this alert and collects the latest diagnostic support file from the external diagnostic site 140. The diagnostic software on the diagnostic site may be provided by the vendor of the alerting device, by the provider of the diagnostic servicing, or both. The management server then pushes the diagnostic package down to the managed server where the problem occurred. The package is automatically installed, executed, and uninstalled. Before being uninstalled, the results of the diagnostic code are packaged into an alert and sent back to the Management Server 125. Upon receiving the data, the management server 125 performs problem determination on the data to determine the proper corrective action. If the corrective action can be performed by the management server 125 (e.g., firmware downlevel or driver downlevel), it performs the corrective action. Otherwise, the corrective action is published by alerting the diagnostic service provider with all appropriate information. If the problem is fixed with a firmware/driver update, the server with the tape drive has fixed itself and the next backup will proceed smoothly.
  • It will be apparent to those skilled in the art having the benefit of this disclosure that the present invention contemplates a method of providing automated diagnostic servicing in a networked environment. It is understood that the form of the invention shown and described in the detailed description and the drawings are to be taken merely as presently preferred examples. It is intended that the following claims be interpreted broadly to embrace all the variations of the preferred embodiments disclosed.

Claims (7)

1-14. (canceled)
15. A data processing system employing automated diagnostic servicing, the data processing system comprising a computer processor, a computer memory operatively coupled to the computer processor, the computer memory having disposed within it computer code means, the data processing system further comprising:
a diagnostic site including computer code means for responding to receipt of identification information by generating a diagnostic package including diagnostic code for a data processing element corresponding to the identification information and further including code means for forwarding the diagnostic package to a sender of the identification information; and
a management server configured to receive an alert from an element of the data processing system, the alert including the identification information indicating the data processing element generating the alert and, in response thereto, to send the identification information to the diagnostic site via a network and further configured to respond to receipt of the diagnostic package from the diagnostic site by installing and executing the diagnostic code.
16. The system of claim 15, wherein the diagnostic code is further enabled to package results generated during execution of the diagnostic code into a results alert and to send the results alert to the server of the data processing system.
17. The system of claim 15, wherein the management server is enabled to use results generated during execution of the diagnostic code to take corrective action.
18. The system of claim 15, wherein the management server is enabled to uninstall the diagnostic code after executing it.
19. The system of claim 15, wherein the networked diagnostic site is further characterized as a diagnostic site on an external network.
20. The system of claim 15, wherein the networked diagnostic site is further characterized as a local replica of a diagnostic site on an external network.
US12/020,864 2003-06-16 2008-01-28 Automated diagnostic service Expired - Fee Related US7865781B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/020,864 US7865781B2 (en) 2003-06-16 2008-01-28 Automated diagnostic service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/462,254 US7350112B2 (en) 2003-06-16 2003-06-16 Automated diagnostic service
US12/020,864 US7865781B2 (en) 2003-06-16 2008-01-28 Automated diagnostic service

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/462,254 Continuation US7350112B2 (en) 2003-06-16 2003-06-16 Automated diagnostic service

Publications (2)

Publication Number Publication Date
US20080184271A1 true US20080184271A1 (en) 2008-07-31
US7865781B2 US7865781B2 (en) 2011-01-04

Family

ID=33511426

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/462,254 Active 2025-02-08 US7350112B2 (en) 2003-06-16 2003-06-16 Automated diagnostic service
US12/020,864 Expired - Fee Related US7865781B2 (en) 2003-06-16 2008-01-28 Automated diagnostic service

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/462,254 Active 2025-02-08 US7350112B2 (en) 2003-06-16 2003-06-16 Automated diagnostic service

Country Status (1)

Country Link
US (2) US7350112B2 (en)

Families Citing this family (85)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040210888A1 (en) * 2003-04-18 2004-10-21 Bergen Axel Von Upgrading software on blade servers
US7590683B2 (en) * 2003-04-18 2009-09-15 Sap Ag Restarting processes in distributed applications on blade servers
US7610582B2 (en) * 2003-04-18 2009-10-27 Sap Ag Managing a computer system with blades
US20040210887A1 (en) * 2003-04-18 2004-10-21 Bergen Axel Von Testing software on blade servers
EP1652100A4 (en) * 2003-07-09 2009-12-16 Hewlett Packard Development Co Carrier network capable of conducting remote diagnostics in a mobile handset
US20050102488A1 (en) * 2003-11-07 2005-05-12 Bullis George A. Firmware description language for accessing firmware registers
US7350115B2 (en) * 2003-12-18 2008-03-25 Intel Corporation Device diagnostic system
US7383461B2 (en) * 2004-02-12 2008-06-03 International Business Machines Corporation Method and system to recover a failed flash of a blade service processor in a server chassis
US7904895B1 (en) 2004-04-21 2011-03-08 Hewlett-Packard Develpment Company, L.P. Firmware update in electronic devices employing update agent in a flash memory card
US7412842B2 (en) 2004-04-27 2008-08-19 Emerson Climate Technologies, Inc. Compressor diagnostic and protection system
US7275377B2 (en) 2004-08-11 2007-10-02 Lawrence Kates Method and apparatus for monitoring refrigerant-cycle systems
US8526940B1 (en) 2004-08-17 2013-09-03 Palm, Inc. Centralized rules repository for smart phone customer care
US20060106796A1 (en) * 2004-11-17 2006-05-18 Honeywell International Inc. Knowledge stores for interactive diagnostics
US20060200711A1 (en) * 2005-02-01 2006-09-07 Schondelmayer Adam H Network diagnostic systems and methods for processing network messages
WO2006083959A2 (en) * 2005-02-01 2006-08-10 Finisar Corporation Network diagnostic system and methods for aggregated links
US20060198312A1 (en) * 2005-02-01 2006-09-07 Schondelmayer Adam H Network diagnostic systems and methods for altering the format and bandwidth of network messages
US8738760B2 (en) * 2005-04-14 2014-05-27 Verizon Business Global Llc Method and system for providing automated data retrieval in support of fault isolation in a managed services network
US7899057B2 (en) 2006-04-28 2011-03-01 Jds Uniphase Corporation Systems for ordering network packets
US20070211696A1 (en) * 2006-03-13 2007-09-13 Finisar Corporation Method of generating network traffic
US20060264178A1 (en) * 2005-05-20 2006-11-23 Noble Gayle L Wireless diagnostic systems
US8107822B2 (en) 2005-05-20 2012-01-31 Finisar Corporation Protocols for out-of-band communication
US20080075103A1 (en) * 2005-05-20 2008-03-27 Finisar Corporation Diagnostic device
US20070038880A1 (en) * 2005-08-15 2007-02-15 Noble Gayle L Network diagnostic systems and methods for accessing storage devices
EP2025095A2 (en) 2006-06-08 2009-02-18 Hewlett-Packard Development Company, L.P. Device management in a network
US8213333B2 (en) 2006-07-12 2012-07-03 Chip Greel Identifying and resolving problems in wireless device configurations
US8590325B2 (en) 2006-07-19 2013-11-26 Emerson Climate Technologies, Inc. Protection and diagnostic module for a refrigeration system
US8752044B2 (en) 2006-07-27 2014-06-10 Qualcomm Incorporated User experience and dependency management in a mobile device
US20080216494A1 (en) 2006-09-07 2008-09-11 Pham Hung M Compressor data module
US8526821B2 (en) 2006-12-29 2013-09-03 Finisar Corporation Transceivers for testing networks and adapting to device changes
US8132166B2 (en) * 2007-05-14 2012-03-06 Red Hat, Inc. Methods and systems for provisioning software
US8561058B2 (en) * 2007-06-20 2013-10-15 Red Hat, Inc. Methods and systems for dynamically generating installation configuration files for software
US8464247B2 (en) * 2007-06-21 2013-06-11 Red Hat, Inc. Methods and systems for dynamically generating installation configuration files for software
US20090037142A1 (en) 2007-07-30 2009-02-05 Lawrence Kates Portable method and apparatus for monitoring refrigerant-cycle systems
US7856574B2 (en) * 2007-09-27 2010-12-21 Microsoft Corporation Internet connectivity evaluation
US9140728B2 (en) 2007-11-02 2015-09-22 Emerson Climate Technologies, Inc. Compressor sensor module
US8713177B2 (en) * 2008-05-30 2014-04-29 Red Hat, Inc. Remote management of networked systems using secure modular platform
US9100297B2 (en) * 2008-08-20 2015-08-04 Red Hat, Inc. Registering new machines in a software provisioning environment
US8930512B2 (en) * 2008-08-21 2015-01-06 Red Hat, Inc. Providing remote software provisioning to machines
US9477570B2 (en) 2008-08-26 2016-10-25 Red Hat, Inc. Monitoring software provisioning
US8838827B2 (en) 2008-08-26 2014-09-16 Red Hat, Inc. Locating a provisioning server
US20100058327A1 (en) * 2008-08-28 2010-03-04 Dehaan Michael Paul Methods and systems for providing customized actions related to software provisioning
US8793683B2 (en) 2008-08-28 2014-07-29 Red Hat, Inc. Importing software distributions in a software provisioning environment
US9111118B2 (en) 2008-08-29 2015-08-18 Red Hat, Inc. Managing access in a software provisioning environment
US8103776B2 (en) * 2008-08-29 2012-01-24 Red Hat, Inc. Systems and methods for storage allocation in provisioning of virtual machines
US9021470B2 (en) 2008-08-29 2015-04-28 Red Hat, Inc. Software provisioning in multiple network configuration environment
US8244836B2 (en) * 2008-08-29 2012-08-14 Red Hat, Inc. Methods and systems for assigning provisioning servers in a software provisioning environment
US9164749B2 (en) 2008-08-29 2015-10-20 Red Hat, Inc. Differential software provisioning on virtual machines having different configurations
US8527578B2 (en) * 2008-08-29 2013-09-03 Red Hat, Inc. Methods and systems for centrally managing multiple provisioning servers
US9952845B2 (en) * 2008-08-29 2018-04-24 Red Hat, Inc. Provisioning machines having virtual storage resources
US8326972B2 (en) * 2008-09-26 2012-12-04 Red Hat, Inc. Methods and systems for managing network connections in a software provisioning environment
US8612968B2 (en) 2008-09-26 2013-12-17 Red Hat, Inc. Methods and systems for managing network connections associated with provisioning objects in a software provisioning environment
US8898305B2 (en) * 2008-11-25 2014-11-25 Red Hat, Inc. Providing power management services in a software provisioning environment
US9124497B2 (en) * 2008-11-26 2015-09-01 Red Hat, Inc. Supporting multiple name servers in a software provisioning environment
US8782204B2 (en) * 2008-11-28 2014-07-15 Red Hat, Inc. Monitoring hardware resources in a software provisioning environment
US8832256B2 (en) * 2008-11-28 2014-09-09 Red Hat, Inc. Providing a rescue Environment in a software provisioning environment
US8775578B2 (en) * 2008-11-28 2014-07-08 Red Hat, Inc. Providing hardware updates in a software environment
US8402123B2 (en) 2009-02-24 2013-03-19 Red Hat, Inc. Systems and methods for inventorying un-provisioned systems in a software provisioning environment
US9727320B2 (en) 2009-02-25 2017-08-08 Red Hat, Inc. Configuration of provisioning servers in virtualized systems
US8892700B2 (en) * 2009-02-26 2014-11-18 Red Hat, Inc. Collecting and altering firmware configurations of target machines in a software provisioning environment
US8413259B2 (en) * 2009-02-26 2013-04-02 Red Hat, Inc. Methods and systems for secure gated file deployment associated with provisioning
US8640122B2 (en) * 2009-02-27 2014-01-28 Red Hat, Inc. Systems and methods for abstracting software content management in a software provisioning environment
US8135989B2 (en) * 2009-02-27 2012-03-13 Red Hat, Inc. Systems and methods for interrogating diagnostic target using remotely loaded image
US8990368B2 (en) 2009-02-27 2015-03-24 Red Hat, Inc. Discovery of network software relationships
US8667096B2 (en) * 2009-02-27 2014-03-04 Red Hat, Inc. Automatically generating system restoration order for network recovery
US9411570B2 (en) * 2009-02-27 2016-08-09 Red Hat, Inc. Integrating software provisioning and configuration management
US9558195B2 (en) 2009-02-27 2017-01-31 Red Hat, Inc. Depopulation of user data from network
US8572587B2 (en) 2009-02-27 2013-10-29 Red Hat, Inc. Systems and methods for providing a library of virtual images in a software provisioning environment
US9940208B2 (en) 2009-02-27 2018-04-10 Red Hat, Inc. Generating reverse installation file for network restoration
US8417926B2 (en) * 2009-03-31 2013-04-09 Red Hat, Inc. Systems and methods for providing configuration management services from a provisioning server
US9250672B2 (en) * 2009-05-27 2016-02-02 Red Hat, Inc. Cloning target machines in a software provisioning environment
US9134987B2 (en) * 2009-05-29 2015-09-15 Red Hat, Inc. Retiring target machines by a provisioning server
US9047155B2 (en) * 2009-06-30 2015-06-02 Red Hat, Inc. Message-based installation management using message bus
US8825819B2 (en) * 2009-11-30 2014-09-02 Red Hat, Inc. Mounting specified storage resources from storage area network in machine provisioning platform
US10133485B2 (en) * 2009-11-30 2018-11-20 Red Hat, Inc. Integrating storage resources from storage area network in machine provisioning platform
US8634415B2 (en) 2011-02-16 2014-01-21 Oracle International Corporation Method and system for routing network traffic for a blade server
US9858241B2 (en) 2013-11-05 2018-01-02 Oracle International Corporation System and method for supporting optimized buffer utilization for packet processing in a networking device
US9285802B2 (en) 2011-02-28 2016-03-15 Emerson Electric Co. Residential solutions HVAC monitoring and diagnosis
US8964338B2 (en) 2012-01-11 2015-02-24 Emerson Climate Technologies, Inc. System and method for compressor motor protection
US9310439B2 (en) 2012-09-25 2016-04-12 Emerson Climate Technologies, Inc. Compressor having a control and diagnostic module
US9803902B2 (en) 2013-03-15 2017-10-31 Emerson Climate Technologies, Inc. System for refrigerant charge verification using two condenser coil temperatures
US9551504B2 (en) 2013-03-15 2017-01-24 Emerson Electric Co. HVAC system remote monitoring and diagnosis
CA2904734C (en) 2013-03-15 2018-01-02 Emerson Electric Co. Hvac system remote monitoring and diagnosis
US9765979B2 (en) 2013-04-05 2017-09-19 Emerson Climate Technologies, Inc. Heat-pump system with refrigerant charge diagnostics
US9489327B2 (en) 2013-11-05 2016-11-08 Oracle International Corporation System and method for supporting an efficient packet processing model in a network environment
US11334406B2 (en) 2019-11-13 2022-05-17 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Systems and methods of presenting diagnostic information of an electronic device at diagnostic equipment

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6195763B1 (en) * 1997-06-02 2001-02-27 Robert Bosch Gmbh Fault diagnostic device and method
US6260160B1 (en) * 1998-06-15 2001-07-10 Siemens Information And Communication Networks, Inc. Remote troubleshooting of a computing device
US6279125B1 (en) * 1998-06-24 2001-08-21 Micron Technology, Inc. Computer system diagnostics
US6425093B1 (en) * 1998-01-05 2002-07-23 Sophisticated Circuits, Inc. Methods and apparatuses for controlling the execution of software on a digital processing system
US6742141B1 (en) * 1999-05-10 2004-05-25 Handsfree Networks, Inc. System for automated problem detection, diagnosis, and resolution in a software driven system
US20040153823A1 (en) * 2003-01-17 2004-08-05 Zubair Ansari System and method for active diagnosis and self healing of software systems
US7124326B1 (en) * 1999-11-15 2006-10-17 Minolta Co., Ltd. Method and apparatus for diagnosing electronic device

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4866635A (en) * 1987-10-19 1989-09-12 Carnegie Group Inc. Domain independent shell for building a diagnostic expert system
US5119377A (en) * 1989-06-16 1992-06-02 International Business Machines Corporation System and method for software error early detection and data capture
US5495610A (en) * 1989-11-30 1996-02-27 Seer Technologies, Inc. Software distribution system to build and distribute a software release
US5367667A (en) * 1992-09-25 1994-11-22 Compaq Computer Corporation System for performing remote computer system diagnostic tests
US5630048A (en) * 1994-05-19 1997-05-13 La Joie; Leslie T. Diagnostic system for run-time monitoring of computer operations
US5539877A (en) * 1994-06-27 1996-07-23 International Business Machine Corporation Problem determination method for local area network systems
US5483637A (en) * 1994-06-27 1996-01-09 International Business Machines Corporation Expert based system and method for managing error events in a local area network
US5627964A (en) * 1994-12-13 1997-05-06 Microsoft Corporation Reduce or fail-safe bootstrapping of a system having a graphical user interface
US5491791A (en) * 1995-01-13 1996-02-13 International Business Machines Corporation System and method for remote workstation monitoring within a distributed computing environment
US5745479A (en) * 1995-02-24 1998-04-28 3Com Corporation Error detection in a wireless LAN environment
US6085244A (en) * 1997-03-17 2000-07-04 Sun Microsystems, Inc. Dynamic test update in a remote computer monitoring system
US5983364A (en) * 1997-05-12 1999-11-09 System Soft Corporation System and method for diagnosing computer faults
US5964891A (en) * 1997-08-27 1999-10-12 Hewlett-Packard Company Diagnostic system for a distributed data access networked system
US6170065B1 (en) * 1997-11-14 2001-01-02 E-Parcel, Llc Automatic system for dynamic diagnosis and repair of computer configurations
US6145096A (en) * 1998-05-06 2000-11-07 Motive Communications, Inc. Method, system and computer program product for iterative distributed problem solving
US6553515B1 (en) * 1999-09-10 2003-04-22 Comdial Corporation System, method and computer program product for diagnostic supervision of internet connections
US6539499B1 (en) * 1999-10-06 2003-03-25 Dell Usa, L.P. Graphical interface, method, and system for the provision of diagnostic and support services in a computer system
US6598183B1 (en) * 2000-01-04 2003-07-22 Cisco Systems, Inc. Software tool for automated diagnosis and resolution of problems of voice, data and VoIP communications networks
US6676018B1 (en) * 2002-08-05 2004-01-13 Diebold, Incorporated Automated banking machine diagnostic system and method

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6195763B1 (en) * 1997-06-02 2001-02-27 Robert Bosch Gmbh Fault diagnostic device and method
US6425093B1 (en) * 1998-01-05 2002-07-23 Sophisticated Circuits, Inc. Methods and apparatuses for controlling the execution of software on a digital processing system
US6260160B1 (en) * 1998-06-15 2001-07-10 Siemens Information And Communication Networks, Inc. Remote troubleshooting of a computing device
US6279125B1 (en) * 1998-06-24 2001-08-21 Micron Technology, Inc. Computer system diagnostics
US6742141B1 (en) * 1999-05-10 2004-05-25 Handsfree Networks, Inc. System for automated problem detection, diagnosis, and resolution in a software driven system
US7124326B1 (en) * 1999-11-15 2006-10-17 Minolta Co., Ltd. Method and apparatus for diagnosing electronic device
US20040153823A1 (en) * 2003-01-17 2004-08-05 Zubair Ansari System and method for active diagnosis and self healing of software systems

Also Published As

Publication number Publication date
US20040255191A1 (en) 2004-12-16
US7865781B2 (en) 2011-01-04
US7350112B2 (en) 2008-03-25

Similar Documents

Publication Publication Date Title
US7865781B2 (en) Automated diagnostic service
US9110766B2 (en) Dynamically recommending changes to an association between an operating system image and an update group
US6970948B2 (en) Configuring system units using on-board class information
US7594219B2 (en) Method and apparatus for monitoring compatibility of software combinations
US6598223B1 (en) Method and system for installing and testing build-to-order components in a defined configuration computer system
US7421490B2 (en) Uniquely identifying a crashed application and its environment
US10037238B2 (en) System and method for encoding exception conditions included at a remediation database
US20020124213A1 (en) Standardized format for reporting error events occurring within logically partitioned multiprocessing systems
EP2472402A1 (en) Remote management systems and methods for mapping operating system and management controller located in a server
US9021317B2 (en) Reporting and processing computer operation failure alerts
US20140122931A1 (en) Performing diagnostic tests in a data center
US7065560B2 (en) Verification of computer program versions based on a selected recipe from a recipe table
Lakner et al. IBM system Blue Gene solution: Blue Gene/Q system administration
US10275330B2 (en) Computer readable non-transitory recording medium storing pseudo failure generation program, generation method, and generation apparatus
US20080177711A1 (en) Build Automation and Verification for Modular Servers
US6973412B2 (en) Method and apparatus involving a hierarchy of field replaceable units containing stored data
US20050033952A1 (en) Dynamic scheduling of diagnostic tests to be performed during a system boot process
GB2342471A (en) Configuring system units
US9459976B1 (en) Repair of computers that have software-related problems
US20150331772A1 (en) Methods for updating diagnostic tools on a hardware device and devices thereof
US7039743B2 (en) System and method of retiring events upon device replacement
US20210334153A1 (en) Remote error detection method adapted for a remote computer device to detect errors that occur in a service computer device
Intel MPCBL0020 Single Board Computer Technical Product Specification
Cisco Release Notes for Cisco iSCSI Driver for HP-UX Version 1.8.1
Cisco Upgrading from Cisco Unity Voice Messaging Release 3.0(1) or Release 3.1(2x) to Release 3.1(3) on the Cisco ICS 7750

Legal Events

Date Code Title Description
STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: LENOVO INTERNATIONAL LIMITED, HONG KONG

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:034194/0291

Effective date: 20140926

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FEPP Fee payment procedure

Free format text: 7.5 YR SURCHARGE - LATE PMT W/IN 6 MO, LARGE ENTITY (ORIGINAL EVENT CODE: M1555); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8

AS Assignment

Owner name: LOT NETWORK INC., ARIZONA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LENOVO INTERNATIONAL LIMITED;REEL/FRAME:049419/0369

Effective date: 20190610

AS Assignment

Owner name: APPVISION CORP., FLORIDA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LOT NETWORK INC.;REEL/FRAME:049555/0112

Effective date: 20181130

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20230104