Abstract:
A method and system for remotely isolating faults in computer network devices coupled to a computer network. A plurality of first computer units are coupled to the computer network. The plurality of first computer units are located on a user side of the computer network. A plurality of second computer units are coupled to the computer network. The plurality of second computer units are located on a service provider side of the network. One of the plurality of second computer units is designated to provide computing services to one of the plurality of first computer units. One of the plurality of first computer units experiencing a fault communicating with its designated second computer unit uses another of the plurality of first computer units as a proxy computer unit to remotely isolate the fault.

Description:
BACKGROUND OF THE INVENTION  
       [0001]     1. Statement of the Technical Field  
         [0002]     The present invention relates to desktop blade computer systems and more particularly to a desktop computer blade system and method for identifying and isolating faults that occur within the system.  
         [0003]     2. Description of the Related Art  
         [0004]     The increasing popularity of consolidating hardware and server application location through server blade technology has led to the development of desktop blade systems. Unlike the consolidation of servers into server blade systems, desktop blade systems by design separate the user and the “desktop” processing unit. For example, a typical desktop blade system includes one or more racks in a computer room or area each having one or more “blades” installed therein, i.e. a “bladecenter”. Each blade in the bladecenter is a processing unit which is allocated to a user and provides the same functionality as if the processing unit were located on the user&#39;s desk. The user is provided with a small deskside device at the user&#39;s desk which provides interfaces for a display unit and interface devices such as a keyboard, mouse and USB ports. The deskside device is typically hardwired to the bladecenter or coupled to the bladecenter using a known networking technology such as Ethernet.  
         [0005]     Using Ethernet and the Internet Protocol (“IP”) as an example, video and keyboard/mouse information travel across the IP network via routers/switches from the deskside unit to the desktop processor in the bladecenter. The separation of these devices over distance and via the IP network adds a number of points of failure that do not exist in traditional desktop computer installations where the desktop processor is located at the user location and is directly connected to the peripheral devices. More particularly, in a desktop blade environment, points of failure include the network, the deskside unit and the desktop processor blade (and/or the bladecenter). As a result, the user can&#39;t readily assist with the identification of the nature of the problem and has no way to communicate with the bladecenter if there is a problem.  
         [0006]     As a result of the above-described shortcomings, current desktop blade system implementations require time consuming and expensive visits to the deskside to identify and correct the problem. Also, during this time, the user can not use their computer, thereby impacting productivity. It is therefore desirable to have a desktop blade system and method which can allows the system itself to identify the source of faults problems and take autonomic corrective action. In the case where autonomic corrective action can not be taken, such as may occur when a non-redundant hardware, e.g., the deskside unit, failure requires a visit by a technician, it is desirable to have a system and method which isolates the fault.  
       SUMMARY OF THE INVENTION  
       [0007]     The present invention addresses the deficiencies of the art in respect to authentication and provides a novel and non-obvious desktop blade system and method, for identifying faults and taking autonomic corrective action. In this regard, the system makes use of the UDP protocol and the existence of other deskside units to attempt to have a deskside unit experiencing a problem communicate with other deskside units to have those units assist with the identification and resolution of the problem.  
         [0008]     According to one aspect, the present invention provides a system for remotely isolating faults in computer network devices coupled to a computer network. A plurality of first computer units are coupled to the computer network. The plurality of first computer units are located on a user side of the computer network. A plurality of second computer units are coupled to the computer network. The plurality of second computer units are located on a service provider side of the network. One of the plurality of second computer units is designated to provide computing services to one of the plurality of first computer units. One of the plurality of first computer units experiencing a fault communicating with its designated second computer unit uses another of the plurality of first computer units as a proxy computer unit to remotely isolate the fault.  
         [0009]     According to another aspect, the present invention provides a method for remotely isolating faults in computer network devices coupled to a computer network. The computer network devices include a plurality of first computer units coupled to the computer network in which the plurality of first computer units are located on a user side of the computer network, a plurality of second computer units coupled to the computer network in which the plurality of second computer units are located on a service provider side of the network and one of the plurality of second computer units is designated to provide computing services to one of the plurality of first computer units. One of the plurality of first computer units is determined to be experiencing a fault communicating with its designated second computer unit. Another of the plurality of first computer units is used as a proxy computer unit to remotely isolate the fault.  
         [0010]     According to still another aspect, a machine readable storage device having stored thereon a computer program for remotely isolating faults in computer network devices coupled to a computer network is provided. The computer network devices include a plurality of first computer units coupled to the computer network in which the plurality of first computer units are located on a user side of the computer network, a plurality of second computer units coupled to the computer network in which the plurality of second computer units are located on a service provider side of the network and one of the plurality of second computer units is designated to provide computing services to one of the plurality of first computer units. The computer program includes a set of instructions which when executed by a machine causes the machine to perform a method in which one of the plurality of first computer units is determined to be experiencing a fault communicating with its designated second computer unit. Another of the plurality of first computer units is used as a proxy computer unit to remotely isolate the fault.  
         [0011]     Additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The aspects of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.  
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0012]     The accompanying drawings, which are incorporated in and constitute part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. The embodiments illustrated herein are presently preferred, it being understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown, wherein:  
         [0013]      FIG. 1  is a diagram of an exemplary system constructed in accordance with the principles of the present invention;  
         [0014]      FIG. 2  is a flow chart of the overall process of the present invention;  
         [0015]      FIG. 3  is a flow chart of the client content request preparation and transmission process (Step S 210 ) of  FIG. 2 ; and  
         [0016]      FIG. 4  is a flow chart of the process of notifying the proxy deskside device and using the proxy deskside device to further isolate the fault (Step S 316 ) of  FIG. 3 .  
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0017]     The present invention advantageously provides a method and system for fault isolation and notification for desktop blade system in a manner which minimizes the need for the desktop blade user to participate in the problem determination process despite the multiple points of failure existent in a desktop blade system. The present invention therefore provides a method and system allows a user, via a deskside device that can not connect to a desktop blade to automatically notify the bladecenter to take autonomic corrective action. If an autonomic fix is not possible, the present invention provides the ability to isolate the fault, thereby facilitating problem resolution.  
         [0018]     Referring now to the drawing figures in which like reference designators refer to like elements there is shown in  FIG. 1 a  system constructed in accordance with the principles of the present invention and designated generally as “ 100 ”. System  100  includes deskside units  102   a  and  102   b  (collectively referred to herein as deskside unit  102 ) in electronic communication with bladecenter  104  via communication network  106 .  
         [0019]     Bladecenter  104  includes one or more desktop blades  108  (two of which are shown in  FIG. 1  as desktop blade  108   a  and  108   b ), and a bladecenter controller  110 . Bladecenter  104  is typically located on the service provider side of communication network  106  in a service provider facility where multiple bladecenters  104  can be co-located and efficiently managed and maintained. Bladecenter controller  110  includes the hardware necessary to allow bladecenter  104  to communicate with other devices, to control bladecenter functions such as the allocation of individual desktop blades  108  to users, i.e., the allocation of desktop blades  108  to deskside units  102  and to perform other functions described herein. Bladecenter controller  110  can include a central processing unit, input/output interfaces, volatile and non-volatile memory, network interfaces and any other hardware as may be known in the art to control the operation of bladecenter  104 . Accordingly, a computing network is formed by the devices shown in  FIG. 1 . For example, computing network devices are those devices coupled to communication network  106 , such as bladecenter  104  and/or its constituent parts and desktop units  102 .  
         [0020]     Desktop blade hardware is generally known in the art and typically includes those hardware elements required to allow desktop blades  108  to function as a desktop personal computer, to communicate with and accept control commands from bladecenter controller  110  and to perform the inventive functions described herein. For example, desktop blades  108  include a central processing unit, operating system, volatile and/or non-volatile memory and interface hardware and software needed to allow desktop blade  108  to communicate with bladecenter controller  110  and deskside units  102 . Of note, although  FIG. 1  shows a single connection to communication network  106  from bladecenter controller  110 , the invention is not so limited. It is contemplated that direct connections between one or more desktop blades  108  and communication network  106  can be made. Desktop blades  108  communicate with bladecenter controller  110  using a communication backplane within the bladecenter  104  chassis or using any other technique as may be known in the art.  
         [0021]     Communication network  106  can be any network capable of transporting information from a deskside unit  102  to a bladecenter  104 . Examples of communication network  106  include Internet Protocol (IP) networks such the Internet, a telephone network and an electric company power distribution network. However, for the sake of simplicity, communication network  106  is referred to herein in the context of an IP network.  
         [0022]     Deskside unit  102  can be any deskside device capable of performing the functions described herein and is located on the user side of communication network  106  at or near the user&#39;s physical work space. For example, deskside unit  102  includes hardware for communicating with communication network  106  as well as appropriate software to do the same. Deskside unit  102  also includes components such as non-volatile and volatile storage devices and interface hardware and software to support peripheral devices such as a keyboard  112 , mouse  114  and monitor  116 . In operation, deskside unit  102  allows a user to view display screens on monitor  116  that were assembled by a desktop blade  108 . Techniques for performing this function are known. Similarly, techniques for providing data to desktop blade  108  based on a user&#39;s manipulation of keyboard  112  and mouse  114  are known.  
         [0023]     As described below in detail, deskside unit  102  preferably includes communication software that allows deskside unit  102  to also communicate with other deskside units  102 . For example, the user datagram protocol (UDP) portion of the IP protocol stack can be used for such communication. It is presumed that one of skill in the art can implement the functions described herein with respect to deskside unit  102  to deskside unit  102  communication using a protocol like UDP.  
         [0024]     In addition, although the example below is described with respect to UDP, it is contemplated that other broadcast and non-broadcast methods of communicating with and locating other deskside units  102  can be used. For example, deskside units  102  can be configured with a predefined list of addresses, such as IP addresses, for other deskside units  102  can may be available to assist with fault isolation and resolution. A deskside unit  102  experiencing a problem could try to communicate with other deskside units  102  in its subnet. There are also other registration class broadcast methods that can be used such as the CISCO Group Multicast Protocol (“CGMP”), Generic Attribute Registration Protocol (“GARP”) and GARP Multicast Registration Protocol (“GMRP”). A router registration class could be defined for a system that would allow a deskside unit  102  to send an IP packet to the router that would then be sent to every registered deskside unit  102 .  
         [0025]     Fault identification and autonomic process  118  is performed by deskside units  102  and bladecenter  104 . This process is described below in detail with reference to  FIGS. 2-4 .  
         [0026]     The overall process of the present invention is described with reference to  FIG. 2 . Initially, deskside unit  102  tests for proper network configuration (not shown). Such tests are known in the art and may include tests to determine whether IP, gateway and Domain Name System (“DNS”) server addresses were acquired, such as via the Dynamic Host Configuration Protocol (“DHCP”), that the deskside unit  102  can find the gateway, DNS servers, etc. The user is alerted if this basic startup testing fails. Assuming the basic network configuration is proper, when the user wishes to log on, deskside unit  102  detects this request and transmits a packet to bladecenter  104  to initiate the login (Step S 200 ). The login request is a request to get assigned a desktop blade  108 , obtain authorization for access, etc. Under normal operation, once authorized, user screens are sent to the deskside unit  102  for display on monitor  116 . In accordance with the present invention, deskside unit  102  includes a timeout function so that if user screens are not returned, it is assumed something is wrong and fault isolation is commenced (Step S 202 ). If user screens are returned, the desktop blade system  100  is presumed to be in normal operation (Step S 204 ) and the process of the present invention ends. If user screens are not returned after a predetermined timeout period, fault isolation commences.  
         [0027]     Initially, the problematic deskside unit  102  determines if another deskside unit  102  can be found (Step S 206 ). Under one embodiment, the problematic deskside unit  102  can broadcast UDP packets in which the UDP packets have an identification field that can be reserved for the function of locating another deskside unit  102 . It is contemplated that all deskside units  102  constructed in accordance with the principles of the present invention can include software within the IP stack that will answer such a UDP broadcast request. Within the UDP packet is the IP address of the broadcasting deskside unit  102 . For the sake of simplicity and ease of discussion, the problematic deskside unit  102 , i.e., the deskside unit  102  that is having trouble receiving the user screens from bladecenter  104  will be referred to herein as deskside unit  102   a.  The other deskside unit  102 , i.e., the deskside unit  102  that is acting as the “proxy” to assist with problem isolations/resolution will be referred to herein as deskside unit  102   b.    
         [0028]     If deskside unit  102   a  cannot find another deskside unit, i.e., cannot find deskside unit  102   b  within a predetermined timeout period, it is presumed that the network is down (Step S 208 ). The user is notified of this problem and instructed to contact the information technology department for further assistance. Of course, if no user screens are returned and deskside unit  102   a  cannot locate another deskside unit  102 , it is also possible that deskside unit  102   a  has had a major failure in which case the user would presumably also notify the information technology department of the same.  
         [0029]     If another deskside unit  102  can be located, this other device is used as a “proxy” for fault isolation and problem resolution (Step S 210 ). As noted above, deskside  102   b  serves this purpose as described herein.  
         [0030]     The step of using another deskside unit  102  as a proxy for fault isolation and problem resolution (Step S 210 ) is explained in detail with reference to  FIG. 3 . If another deskside unit  102 , such as deskside unit  102   b  is located, deskside unit  102   a  transmits a request to proxy deskside unit  102   b  inquiring as to whether deskside unit  102   b  can communicate with bladecenter  104  (Step S 300 ). If proxy deskside unit  102   b  cannot communicate with bladecenter  104 , proxy deskside unit  102   b  notifies deskside unit  102   a  that deskside unit  102   b  cannot communicate with bladecenter  104  and that communication network  106  must be down at some point between deskside units  102  and bladecenter  104  (Step S 302 ). In addition, it is also contemplated that, upon receiving indication from proxy deskside unit  102   b  that it cannot communicate with bladecenter  104 , deskside unit  102   a  can make the determination that communication network  106  is down. In either case, the user is notified of the network outage. A message can be generated and transmitted to the information technology department alerting of the network outage and the user can be instructed to contact the information technology group (because it is possible that the network outage may render the information technology group unreachable through communication network  106 ).  
         [0031]     If the proxy deskside unit  102   b  can communicate with bladecenter  104 , deskside unit  102   a  instructs proxy deskside unit  102   b  to notify bladecenter  104  that deskside unit  102   a  cannot connect (Step S 304 ). Bladecenter  104 , via bladecenter controller  110 , tests deskside blade  108  assigned to deskside unit  102   a  (Step S 306 ). If the desktop bladecenter  108  is good (Step S 308 ), bladecenter controller  110  reboots blade  108  (Step S 310 ). If the desktop blade  108  is not good, bladecenter controller  110  assigns another desktop blade  108  (Step S 312 ), and the failed blade action policy is implemented (Step S 314 ).  
         [0032]     For example, a failed blade action policy may include notifying a particular information technology professional that blade has failed, automatically powering down the failed desktop blade  108 , performing automated diagnostics on failed desktop blade  108  and/or creating log entries, etc.  
         [0033]     Regardless of whether the desktop blade  108  is good and was rebooted (Step S 310 ) or failed and a new blade assigned, proxy deskside unit  102   b  is used to facilitate notification processing to further assist with isolation and resolution (Step S 316 ) and the process returns to step S 200  (see  FIG. 2 ) so that the user can try to log onto the desktop blade  108  again.  
         [0034]     Step S 316  is described in detail with reference to  FIG. 4 . Bladecenter  104 , via bladecenter controller  110 , sends an instruction packet to proxy deskside unit  102   b  indicating the action that was taken (Step S 400 ), e.g., that the desktop blade  108  assigned to desktop unit  102   a  has been rebooted or that the new desktop blade  108  has been assigned to deskside unit  102   a.  Proxy deskside unit  102   b  forwards the instruction packet to the deskside unit under test, i.e., deskside unit  102   a  (Step S 402 ). Deskside unit  102   b  waits for a predetermined time for deskside unit  102   a  to respond to acknowledge receipt of the instruction (Step S 404 ). If an acknowledgment was received, it is assumed that deskside unit  102   a  is operational and the process ends. In this case, either the problem has been resolved by the assignment of a new desktop blade  108  or there is a problem with communication network  106  and the information technology department has been notified or the user is instructed to notify the information technology department.  
         [0035]     If acknowledgment is not received from deskside unit  102   a,  proxy deskside unit  102   b  performs diagnostic testing on deskside unit  102   a  in an attempt to further isolate the fault (Step S 406 ). Actual diagnostic tests like memory tests, software operation, network communication interface tests, and the like are known and are beyond the scope of the present invention. If deskside unit  102   a  passes the diagnostic testing, it is known that deskside unit  102   a  is operational and that, because the original blade  102   a  assigned to deskside unit  102   a  is operational or has been substituted with another desktop unit  108 , the network connection from deskside unit  102   a  to bladecenter  104  is down (Step S 410 ).  
         [0036]     Proxy deskside unit  102   b  reports the communication network failure to the information technology department (Step S 412 ) and alerts deskside unit  102   a  that another deskside unit  102  should be used as a proxy to communicate with desktop blade  108  (Step S 414 ). In this case, although communications with bladecenter  104  may be slower due to the additional routing that packets between deskside unit  102   a  and desktop blade  108  will take, communications will at least enable the user to perform work. Of note, if, in accordance with Step S 414 , a deskside unit  102  is needed by deskside unit  102   a  for communication with desktop blade  108 , any other deskside unit  102  can be used. Put another way, the proxy deskside unit is not limited to the deskside unit  102   b  that initially responded to the request from deskside unit  102   a  for assistance, described above with respect to Steps S 206  and S 210 . In determining which deskside unit  102  will assist deskside unit  102   a  as a communication proxy for actual work (as opposed to fault isolation), algorithms such as using the deskside unit with the lowest processor load, fastest communication response time, etc., can be used.  
         [0037]     If deskside unit  102   a  does not pass the diagnostic testing (Step S 408 ) it is determined that deskside unit  102   a  has failed (Step S 416 ). Proxy deskside unit  102   b  reports the failure (Step S 418 ) to the information technology department. In addition, if deskside unit  102   a  is partially operational, proxy deskside unit  102   b  can alert deskside unit  102   a  of the failure so that the user can also be notified of the failure and that the information technology department has been alerted.  
         [0038]     It is contemplated that notifying the information technology group in any fashion described above can result in the automatic generation of a trouble ticket. Depending on the failure, information relating to the trouble ticket can be provided to the user so that the user has confidence that the problem has been identified and that the information technology group has been notified and will attend to the problem.  
         [0039]     Although the present invention has been described within the context of a computer using deskside units  102  and bladecenters  104 , the invention is not limited to such. It is contemplated that the present invention can be implemented in any environment which uses units proximate a user, i.e., on a user side of a network, coupled to or in communication with a bank of centrally located processing devices. For example, the present invention can be implemented in a cable television network for isolation determining problems between set-top cable boxes and/or cable modems and cable company controllers located at a cable company facility. The present invention can also be implemented in a telephone system for determining problems between a telephone, DSL modem, etc. located at a user facility and telephone company controlled equipment located at a telephone company facility.  
         [0040]     The present invention can be realized in hardware, software, or a combination of hardware and software. An implementation of the method and system of the present invention can be realized in a centralized fashion in one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system, or other apparatus adapted for carrying out the methods described herein, is suited to perform the functions described herein.  
         [0041]     A typical combination of hardware and software could be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein. The present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which, when loaded in a computer system is able to carry out these methods.  
         [0042]     Computer program or application in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following a) conversion to another language, code or notation; b) reproduction in a different material form. Significantly, this invention can be embodied in other specific forms without departing from the spirit or essential attributes thereof, and accordingly, reference should be had to the following claims, rather than to the foregoing specification, as indicating the scope of the invention.