# Patent

## Title
Reducing impact of a repair action in a switch fabric

## Abstract

Techniques are disclosed for reducing impact of a repair action in a switch fabric. In one embodiment, a server system is provided that includes a first interposer card that operatively connects one or more server cards to a midplane. The first interposer card may include a switch module that switches network traffic for the one or more server cards. The first interposer card may be hot-swappable from the midplane, and the one or more server cards may be hot-swappable from the first interposer card.

## Background
CROSS-REFERENCED TO RELATED APPLICATIONS
This application is a continuation of co-pending U.S. patent application Ser. No. 13/177,611, filed Jul. 7, 2011. The aforementioned related patent application is herein incorporated by reference in its entirety.


BACKGROUND
Although early computer architectures utilized standalone, single computers, often referenced as Personal Computers (PCs), more powerful modern computer systems often use multiple computers that are coupled together in a common chassis. An exemplary common chassis is known as a blade chassis, which includes multiple server blades that are coupled by a common backbone within the blade chassis. Each server blade is a pluggable board that includes at least one processor, on-board memory, and an Input/Output (I/O) interface. The multiple server blades are configured to communicate with one another and to share common resources such as storage devices, monitors, input devices, etc. Further, one or multiple blade chassis may make up a blade system, which is often dedicated to a single enterprise and/or a particular function, such as processing loans, managing payroll, etc.
SUMMARY
One embodiment of the invention provides a system that includes a server card, a midplane, and a first interposer card. The server card includes one or more computer processors and a memory. The midplane includes a fabric interconnect. The first interposer card includes a switch module configured to switch network traffic for the server card. The first interposer card is disposed between the midplane and the server card, thereby operatively connecting the midplane and the server card. The first interposer card is hot-swappable from the midplane, and the server card is hot-swappable from the first interposer card. The system is configured to detect that the switch module has failed. The system is further configured to output for display an indication to perform a repair action on the switch module, upon detecting that the switch module has failed.
Another embodiment of the invention provides a switch module that includes a computer processor and a memory. The memory stores management firmware which, when executed on the computer processor, performs an operation that includes outputting for display an indication to perform a repair action on the switch module, upon detecting that the switch module has failed. The switch module is included in a first interposer card disposed between a midplane and a server card in a server system, thereby operatively connecting the midplane and the server card. The switch module is configured to switch network traffic for the server card. The first interposer card is hot-swappable from the midplane, and the server card is hot-swappable from the first interposer card.
Yet another embodiment of the invention provides a computer-implemented method that includes providing a server system including a midplane, a first interposer card and a server card. The first interposer card is disposed between the midplane and the server card, thereby operatively connecting the midplane and the server card. The first interposer card includes a switch module configured to switch network traffic for the server card. The first interposer card is hot-swappable from the midplane, and the server card is hot-swappable from the first interposer card. The method further includes detecting that the switch module has failed. The method further includes outputting for display an indication to perform a repair action on the switch module, upon detecting that the switch module has failed.



BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
So that the manner in which the above recited aspects are attained and can be understood in detail, a more particular description of embodiments of the invention, briefly summarized above, may be had by reference to the appended drawings.
It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.
FIG. 1 is a block diagram of a computing environment having several hosts with access to a server system, according to one embodiment of the invention.
FIG. 2 illustrates a configuration in which interposer cards are operatively connected to server cards in a server system, according to one embodiment of the invention.
FIG. 3 illustrates a configuration in which an interposer card is operatively connected to two server cards in a server system, according to one embodiment of the invention.
FIG. 4 illustrates a server system configured to reduce impact of a repair action on a switch module, according to one embodiment of the invention.
FIG. 5 also illustrates a server system configured to reduce impact of a repair action on a switch module, according to one embodiment of the invention.
FIG. 6 illustrates a switch fabric for a server system, according to one embodiment of the invention.
FIG. 7 illustrates a server system having a midplane that is coupled with multiple interposer cards, according to one embodiment of the invention.
FIG. 8 illustrates a server system that includes multiple frames, according to one embodiment of the invention.
FIG. 9 illustrates a server system that includes multiple frames, each frame having four chassis, according to one embodiment of the invention.
FIG. 10 is a flowchart depicting a method for reducing impact of a repair action in a switch fabric, according to one embodiment of the invention.
FIG. 11 is also a flowchart depicting a method for reducing impact of a repair action in a switch fabric, according to one embodiment of the invention.



DETAILED DESCRIPTION
Embodiments of the invention reduce impact of a repair action in a switch fabric. As used herein, a switch fabric refers to a network topology where network nodes connect with each other via one or more network switches. In one embodiment, a server system is provided that includes a midplane, a first interposer card, and one or more server cards, each server card corresponding to one or more network nodes. In one embodiment, each server card may be a server blade, also referred to as a blade server or blade. Although described with reference to the first interposer card, the midplane may be configured to couple with a plurality of interposer cards. The first interposer card is disposed between the midplane and the one or more server cards, thereby operatively connecting the midplane to the one or more server cards. Further, the first interposer card includes a switch module that switches network traffic for the one or more server cards. The first interposer card is hot-swappable from the midplane, and the one or more server cards are hot-swappable from the first interposer card.
In one embodiment, when the switch module fails, the switch module may be replaced using a repair action that minimizes or reduces impact to the switch fabric. The repair action includes replacing the first interposer card with a second interposer card that includes a functional switch module and reintegrating the second interposer card into the network fabric via a configuration tool executing on the server system. Due to the packaging of the server system and the hot-swappable properties of the interposer cards and the server cards, the repair action may be performed without disrupting the server system or the switch fabric—e.g., without powering off or restarting the server system and/or switch fabric. Where the switch fabric provides redundancy in terms of connectivity, the repair action may also minimize or reduce impact to the provided redundancy. Accordingly, the impact of the repair action is localized to the server card. In other words, the impact of the repair action to the switch fabric is only to an extent of the first interposer card and/or the server card; the server system and switch fabric—namely, other interposer cards and server cards operatively connected to the midplane—remain operational. Advantageously, the impact of the repair action is reduced compared to a physical configuration or packaging that requires powering off the server system and/or switch fabric to replace the switch module—e.g., by replacing the midplane or by replacing a non-hot-swappable switch card coupled to the midplane. Availability of the server system and/or switch fabric is thereby improved, and costs associated with the repair action are thereby reduced.
In one embodiment, the availability of the server system and/or switch fabric—or redundancy characteristics thereof—may be improved relative to a second packaging of the server system that would require the midplane to be replaced to remedy a failed switch module. For example, the second packaging of the server system may include one or more switch chips interconnected on a single card (or planar board) that is coupled with the midplane. Coupling the single card to the midplane may provide an increased a number of ports, provide increased bandwidth, and/or improve availability of the switch fabric. The second packaging of the server system may also include multiple redundant paths through multiple switch chips, such that the server system can continue to operate if a switch chip fails. However, other failures that affect the single card to the planar board can cause a portion of or even the entire switch fabric to cease functioning. Examples of the other failures include power component failures, Voltage Regulator Module (VRM) failures, power plane shorts, etc.
In one embodiment, even if the switch fabric can remain operational in the presence of one or more failed switch chips, a repair action on the one or more failed switch chips may require the single card, planar board, and/or midplane to be replaced, resulting in a loss of operation of at least the portion of the switch fabric supported by the midplane during the repair action. To avoid the loss of operation during the repair action, the server system may be configured to include a second, fully-redundant single card (or planar board). Alternatively, the server system may be packaged using the techniques disclosed herein to reduce the impact of the repair action on the switch fabric while avoiding the cost of configuring the server system with a second, fully-redundant single card or planar board. Accordingly, the availability of the server system may be improved, because single points of failure (SPOFs) and/or single points of repair (SPORs) are reduced or minimized. SPOFs are said to be eliminated when the server system can continue to operate in the presence of any component failure. SPORs are said to be eliminated when the server system can continue to operate while any (failed) component is being repaired or replaced.
In the following, reference is made to embodiments of the invention. However, it should be understood that the invention is not limited to specific described embodiments. Instead, any combination of the following features and elements, whether related to different embodiments or not, is contemplated to implement and practice the invention. Furthermore, although embodiments of the invention may achieve advantages over other possible solutions and/or over the prior art, whether or not a particular advantage is achieved by a given embodiment is not limiting of the invention. Thus, the following aspects, features, embodiments and advantages are merely illustrative and are not considered elements or limitations of the appended claims except where explicitly recited in a claim(s). Likewise, reference to “the invention” shall not be construed as a generalization of any inventive subject matter disclosed herein and shall not be considered to be an element or limitation of the appended claims except where explicitly recited in a claim(s).
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
FIG. 1 is a block diagram of a computing environment 100 having several hosts with access to a server system 102, according to one embodiment of the invention. Although only three hosts 134a,b,n are depicted for clarity, those skilled in the art will appreciate that additional hosts may have access to the server system 102. The hosts 134a,b,n are connected through a network fabric 132 to the server system 102. Depending on the embodiment, each host 134a,b,n may act as a client that accesses functionality provided by the server system 102 and/or may provide respective server functionality external to the server system 102. The network fabric 132 may be a telecommunications network and/or a local area network (LAN) or wide area network (WAN). In a particular embodiment, the network fabric 132 is the Internet. The server system 102 includes a chassis that houses server blades 104a,b,n. The server blades 104a,b,n are coupled to a midplane 123, which provides mechanical and logical connections (e.g., data and control signal interchange) among the server blades 104a,b,n. Although three server blades 104a,b,n are depicted, those skilled in the art will appreciate that additional server blades may be connected to the midplane 123. Further, although embodiments are described herein with reference to blade systems, other form factors or physical configurations (e.g., rack systems) are broadly contemplated.
Further, although embodiments are described herein with reference to the server blades 104a,b,n being coupled to the midplane 123, those skilled in the art will recognize that more generally, the server blades may be coupled to any printed circuit board (PCB) that serves as a backbone for the chassis, such as a backplane, motherboard, etc. Further still, although embodiments are described herein with reference to the server system 102 having a single chassis, those skilled in the art will recognize that in other embodiments, the server system 102 may include multiple chassis. For example, in an alternative embodiment, the server system 102 may be a blade system that includes at least two blade chassis, each having a plurality of blades.
In one embodiment, the server system 102 further includes one or more management modules 124. In the depicted embodiment, the server system 102 includes a primary management module 124a and a backup management module 124b. Each management module 124 is capable of managing multiple server blades 104. During normal operation, one of the management modules 124 is operatively connected to the server blades 104 via a local area network (LAN) 122, the midplane 123 and a Baseboard Management Controllers (BMCs) 110 of each server blade 104 to form an in-band management pathway. In one embodiment, the network fabric 132 serves as an extension to the LAN 122. The LAN 122 and the BMC 110 are further discussed below.
In one embodiment, the midplane 123 is mounted in the middle of the chassis of the server system 102 and contains circuitry and sockets 112 into which additional electronic devices or cards, including server blades 104, may be inserted. The midplane 123 includes at least one bus for secure in-band internal communication via the BMCs 110 and between the management modules 124 and the server blades 104 and/or amongst the server blades 104 themselves.
In one embodiment, when a server blade 104 is inserted into a specific socket 112, a physical address is established for the server blade 104. For example, assume that server blade 104a is inserted into the socket 112a. In one embodiment, control logic 116a detects presence of the server blade 104a in the socket 112a. The control logic 116a may comport with the Electronics Industry Association (EIA) RS485 Standard for data communication. In other embodiments, the control logic 116a may be compliant with the Phillips' Inter-IC (Inter-Integrated Circuit, or I2C) standard or with an Ethernet network standard. The control logic 116a, operating in conjunction with the management module 124a, assigns a physical address on a bus in the midplane 123 to the server blade 104a responsive to insertion of the server blade 104a into the socket 112a. As shown, each server blade 104 is associated with a respective control logic 116 that is operatively connected to the midplane 123. In an alternative embodiment, multiple server blades 104 may share a single control logic 116.
In one embodiment, each server blade 104 is assigned a unique Internet Protocol (IP) address on the midplane 123. That is, the midplane 123 may support intercommunication using IP addressing protocol, in which each device that is operatively connected to the midplane 123 has an IP address assigned by logic (not shown) that is either within or outside the chassis of the server system 102. For example, a Dynamic Host Configuration Protocol (DHCP) server may be used to assign an IP address to the server blade 104a. Communication with the server blade 104a thereafter occurs via a network interface controller (NIC) 114a associated with the server blade 104a. The NIC 114a may be any type of network communications device allowing the server blade 104a to communicate with other server blades 104b,n and/or computers via the LAN 122 and/or the network fabric 132.
In one embodiment, an integrated module 126a is operatively connected to the NIC 114a. The integrated module 126a may be used in pairs (e.g., with integrated module 126b) to provide redundancy. As is known, Small Computer System Interface (SCSI) refers to a set of standards for physically connecting and transferring data between computers and peripheral devices. In one embodiment, the integrated modules 126 include switch modules 128, such as a Serial Attached SCSI (SAS) switch module. The switch modules 128 provide, for the server blades 104, connectivity to Ethernet, Fibre Channel over Ethernet (FCoE), SAS, etc. In one embodiment, each switch module 128 is a switch chip. Depending on the embodiment, the integrated modules 126 may further include redundant array of independent disks (RAID) controllers 130. Each RAID controller 130 is interconnected to RAID devices, such as storage devices in a RAID configuration. The RAID devices may be located within one or more of the server blades 104. The RAID controllers 130 and the RAID devices may collectively be viewed as a RAID subsystem of the server system 102.
In one embodiment, each storage device may be a persistent storage device. Further, each storage device may be a combination of fixed and/or removable storage devices, such as fixed disc drives, floppy disc drives, tape drives, removable memory cards, solid-state drives or optical storage. The memory 108 and the storage device may be part of one virtual address space spanning multiple primary and secondary storage devices.
In one embodiment, each server blade 104 may have at least one central processing unit (CPU) 106 and a memory 108. The CPU 106 is included to be representative of a single CPU, multiple CPUs, a single CPU having multiple processing cores, and the like. Similarly, the memory 108 may be a random access memory. While the memory 108 is shown as a single identity, it should be understood that the memory 108 may comprise a plurality of modules, and that the memory 108 may exist at multiple levels, from high speed registers and caches to lower speed but larger DRAM chips. The memory 108 may be a flash read-only memory (“flash ROM” or “flash memory”) that can be erased and reprogrammed in units of memory referred to as “blocks.” The memory 108 may also include non-volatile Electrically Erasable Programmable Read Only Memory (EEPROM) that is similar to flash memory, except that EEPROM is erased and rewritten at a byte level and is usually smaller in capacity. Each server blade 104 may be oriented as a processor blade or a storage blade. A processor blade includes one or more processing devices, while a storage blade includes a number of integrated storage devices such as disk drives.
In one embodiment, when the server blade 104 is shipped from a manufacturer, the memory 108 may be pre-burned with firmware, including a basic input/output system (BIOS) and software for monitoring the server blade 104. The monitoring may include controlling storage devices, monitoring and controlling voltages throughout the system, determining the power-on status of the server blade 104, requesting access to a shared keyboard, video, mouse, compact disc read-only memory (CD-ROM) and/or floppy disk drives, monitoring the operating system (OS) running on the server blade 104, etc. Examples of operating systems include UNIX, versions of the Microsoft Windows® operating system, and distributions of the Linux® operating system. More generally, any operating system supporting the functions disclosed herein may be used.
In one embodiment, the management modules 124 are capable of detecting the presence, quantity, type and revision level of each server blade 104, power module 118, and midplane 123 in the system. The management modules 124 may also directly control the operation of each server blade 104 and the power module 118. The management modules 124 may also directly control the operation of cooling fans 120 and other components in the chassis of the server system 102. Directly controlling the operation entails controlling the operation without using the BIOS in the server blades 104. In an alternative embodiment, the management modules 124 may use the BIOS to indirectly control the operation of the cooling fans 120 and the other components in the chassis of the server system 102.
In one embodiment, each server blade 104 includes a baseboard management controller (BMC) 110 that provides local supervisory control of the server blade 104 to which the BMC 110 is associated. Each BMC 110 is configured to communicate with a management module 124 by either using communication path of the LAN 122 (i.e., via an in-band network) or alternatively by using switch modules 128 and NICs 114 (i.e., via an out-of-band network). The management modules 124 may utilize a variety of communications paths in the LAN 122, such as RS485 path, a LAN path, and an I2C path, to communicate with each server blade 104.
In one embodiment, the LAN 240 is an in-band network also comporting with the Electronics Industry Association (EIA) RS485 Standard for data communication. The management modules 124—e.g., either the primary management module 124a or the backup management module 124b if the primary management module 124a is down—communicate via the LAN 122 with the BMC 110, which includes logic for coordinating communication with the server blades 104 via the sockets 112.
In one embodiment, the LAN 122 may be configured to allow communications between the server blades 104 and the management modules 124 relating to the remote BIOS settings and BIOS management. The server blades 104 may use BMCs 110 as proxies to communicate with the management modules 124 through the RS485 protocol. Similarly, the management modules may use BMCs 110 as proxies to communicate with the server blades 104 through the RS485 protocol. In an alternative embodiment, an RS485 connection may be separately made between each server blade 104 and the management modules 124. Additionally, other communications protocols and paths may be utilized over the switch modules 128, such as I2C, TCP/IP, Ethernet, FCoE, etc.
Depending on the embodiment, the server system 102 may also be operatively connected to an input device and/or an output device. The input device may be any device for providing input to the server system 102. For example, a keyboard, keypad, light pen, touch-screen, track-ball, or speech recognition unit, audio/video player, and the like may be used. The output device may be any device for providing output to a user of the server system 102. For example, the output device may be any conventional display screen or set of speakers, along with their respective interface cards, i.e., video cards and sound cards. Further, the input device and output device may be combined. For example, a display screen with an integrated touch-screen, a display with an integrated keyboard, or a speech recognition unit combined with a text speech converter may be used.
FIG. 2 illustrates a configuration 200 in which interposer cards are operatively connected to server cards in a server system, according to one embodiment of the invention. Depending on the embodiment, the interposer card may also be coupled to the server cards and/or the midplane. As described above, in one embodiment, to reduce the impact of a repair action on a failed switch module, the server system is configured to include a midplane 123 and server cards 202, where the midplane and server cards 202 are operatively connected via one or more interposer cards 204. Each server card 202 may correspond to a server blade 104. Each interposer card 204 is hot-swappable and includes one or more switch modules 206. The switch modules 206 switch network traffic for one or more server cards 202 operatively connected with the respective interposer card.
In one embodiment, the server system is configured to detect failure of the switch module 206. Upon detecting failure of the switch module 206, the server system may output for display an indication to perform a repair action on the switch module 206. For example, the indication may be output for display in a graphical user interface (GUI) window or as an alert to be emailed to a user. Depending on the embodiment, the detecting and/or the outputting may be performed by any component of the server system, such as the server cards 202, the switch module 206 and/or firmware contained in the server system. For example, in one embodiment, the server system includes management firmware that monitors health of the server system and detects failure of the switch module 206.
Accordingly, when a switch module 206 fails, the interposer card 204 that includes the switch module 206 may be replaced with an interposer card having a functional switch module. Further, the interposer card 204 may be replaced without requiring the server system and/or switch fabric to be powered off or rebooted, because of the hot-swappable properties of the interposer cards, server cards and/or midplane. The interposer card having a functional switch module may then be reintegrated into the switch fabric via the configuration tool. Depending on the embodiment, the configuration tool may execute on the server system or on another computer connected to the server system via the network fabric 132.
Accordingly, during the duration of replacing the interposer card with the failed switch module, only the failed switch module and associated server cards are unreachable from the network fabric. During the duration of replacing the interposer card with the failed switch module, other switch modules and/or server cards operatively connected to the midplane remain reachable. Accordingly, the impact of the repair action on the failed switch module is localized to the server cards associated with the failed switch module. In other words, the only network nodes that are unreachable from the network fabric during the repair action are the network nodes associated with the server cards operatively connected to the failed switch module.
FIG. 3 illustrates a configuration 300 in which an interposer card is operatively connected to two server cards in a server system, according to one embodiment of the invention. As shown, the interposer card 204 includes the switch module 206 and two Converged Network Adapters (CNAs) 302. The two server cards 202 may each also include two CPUs 106 and a CNA 304. In one embodiment, the CPUs 106 connect to FCoE with CNAs, which contain both Fibre Channel Host Bus Adapter (HBA) and Ethernet NIC functionality. The CNAs may include one or more physical Ethernet ports and may be configured to offload—from the CPUs 106—low level frame processing and/or SCSI protocol functionality traditionally performed by Fibre Channel host bus adapters. As described above, the switch module 206 switches network traffic for the server cards 202. If the switch module 206 fails, the configuration 300 allows the switch module 206 to be replaced without requiring reboot of server cards of other interposer cards coupled with the midplane.
FIG. 4 illustrates a server system 400 configured to reduce impact of a repair action on a switch module, according to one embodiment of the invention. As shown, the server system 400 includes a logical server 402 configured across a processor information technology element (ITE) 404 and an I/O ITE 406. As used herein, an ITE generally refers to any appliance configured to operatively connect to the midplane 123. In an alternative embodiment, the logical server 402 may also be configured across a storage ITE 408. The I/O ITE 406 and storage ITE 408 are configured to provide additional I/O capacity and storage capacity, respectively, to one or more processer ITEs. Depending on the embodiment, each ITE 404, 406, 408 may be integrated as part of one or more server blades or may be coupled with the midplane 123 as a standalone card. The processor ITE 404 includes one or more virtual machines 410, a hypervisor 412, memory 414, processors 416 and hard disk drives 418. The I/O ITE 406 includes a shared I/O ITE component 422 and I/O adapters 424, while the storage IT 408 includes a shared storage ITE component 426 and solid state drives 428.
In one embodiment, the server blade 404 and the ITEs 406, 408 each further include a switch module 206. Each switch module 206 may be a switch chip and may be included in an interposer card (not shown) that is disposed between the midplane 123 and the processor ITE 404 and/or ITE 406, 408. Collectively, the switch modules 206 provide a switch fabric 432. A failing of the switch module 2061 of the processor ITE 404—denoted by an X symbol 430—impacts only the processor ITE 404 and not other ITEs operatively connected to the midplane 123. Accordingly, other logical servers configured across the I/O ITE 406 and/or storage ITE 408 remain operational, and connectivity in the switch fabric 432 remains largely operational—i.e., except for connectivity to the processor ITE 404. Depending on the embodiment, the connectivity in the switch fabric 432 that remains operational may also include redundant connectivity in the switch fabric 432. Further, the switch module 2061 may be replaced without impacting the other ITEs, logical servers, and/or the switch fabric 432. Accordingly, availability of the switch fabric 432 may be improved.
FIG. 5 also illustrates a server system 500 configured to reduce impact of a repair action on a switch module, according to one embodiment of the invention. As shown, the server system 500 includes a first logical server 402 configured across a first processor ITE 404 and the I/O ITE 406. The server system 500 also includes a second logical server 502 configured across a second processor ITE 504 and the I/O ITE 406. In an alternative embodiment, the first logical server 402 and/or the second logical server 502 may also be configured across the storage ITE 408. The ITEs 404, 406, 408, 504 each includes a switch module 206. A failing of the switch module 2061 of the processor ITE 404—denoted by an X symbol 506, impacts only the first processor ITE 404 and not the second processor ITE 504. Accordingly, the second processor ITE 504, the I/O ITE 406 and the storage ITE 408 remain operational and retain connectivity to the switch fabric during failure and/or replacement of the switch module 2061.
FIG. 6 illustrates a switch fabric 432 for a server system, according to one embodiment of the invention. As shown, the switch fabric 432 includes a plurality of switch modules 206, each included in a respective interposer card 204. Each interposer card 204 operatively connects two server cards 202 to the switch fabric 432. Depending on the embodiment, the switch modules may be connected to one another in switch fabric via wiring housed in a midplane, cabling external to the midplane, or a combination thereof. Further, one or more of the switch modules 206 may be coupled with appliances 602 other than the server cards 202. Examples of appliances 602 include network appliances, storage appliances, and I/O appliances. Accordingly, failure and/or replacement of a switch module 206 impacts only the server cards 202 coupled with the switch module 206 and does not otherwise impact the rest of the switch fabric 432 and/or the other server cards.
FIG. 7 illustrates a server system 700 having a midplane 123 that is coupled with a plurality of interposer cards 204, according to one embodiment of the invention. Each interposer card 204 includes a switch module 206 and operatively connects one or two server cards 202 to the midplane 123. The midplane includes fabric wiring that connects the switch modules 206 to form a switch fabric. The server system 700 is configured such that the server cards 202 are hot-swappable from the interposer cards 204. The server system 700 is further configured such that the interposer cards 204 are hot-swappable from the midplane 123. Accordingly, the packaging and hot-swappable properties of the server system 700 allow a faulty switch module 206 to be replaced while minimizing or reducing impact to the server system 700 and/or the switch fabric.
FIG. 8 illustrates a server system 800 that includes multiple frames 804, according to one embodiment of the invention. Each frame includes one or more chassis 802 that are operatively connected via chassis link cards 806 and associated cabling 808. Further, the chassis 802 may be operatively connected across two frames via frame link cards 810 and associated cabling 812. Each chassis 802 houses a midplane 123 that is coupled with one or two server cards 202 via an interposer card 204 according to the techniques disclosed herein. Each interposer card 204 includes a switch module 206 for switching traffic for the server cards 202. The midplanes 123 include fabric wiring for interconnecting the switch modules 206. Together, the switch modules 206, the fabric wiring, the chassis link cards 806 and associated cabling 808, and the frame link cards 810 and associated cabling 812 form a switch fabric for the server system 800. In other words, the switch fabric for the server system 800 includes cross-chassis and cross-frame interconnects. Accordingly, failure and/or replacement of a switch module 206—as denoted by an X symbol 814—merely removes an associated server card 202 from the switch fabric. Operation of the other server cards and/or connectivity of the switch fabric are thereby maintained during the failure and/or replacement of the switch module 206.
FIG. 9 illustrates a server system 900 that includes multiple frames, each frame having four chassis 802, according to one embodiment of the invention. The chassis within each frame may be operatively connected via inter-chassis cabling 904. Chassis from different frames may be operatively connected via inter-frame cabling 906. Each chassis houses a midplane having fabric wiring, at least one interposer card having a switch module, and at least one server card according to the techniques disclosed herein. Together, the switch modules, the fabric wiring, the inter-chassis cabling 904, and the inter-frame cabling 906, and any associated link cards form a switch fabric for the server system 900. The server system 900 is thereby configured to increase availability of the switch fabric and/or of the server system 900 during failure and/or replacement of a switch module.
FIG. 10 is a flowchart depicting a method 1000 for reducing impact of a repair action in a switch fabric, according to one embodiment of the invention. As shown, the method 1000 begins at step 1010, where a provider of a server system packages the server system to include a server card coupled with a first interposer card, where the first interposer card includes a switch module configured to switch network traffic for the server card, thereby providing connectivity between the server card and the switch fabric. The server card may be hot-swappable from the first interposer card. At step 1020, the provider of the server system packages the server system to include a midplane coupled with the first interposer card, where the first interposer card is hot-swappable from the midplane and whereby the impact of the repair action on the switch module is localized to the server card. For example, the repair action on the switch module may include replacing the first interposer card with a second interposer card having a functional switch module. The repair action does not impact operation of other server cards and/or connectivity of the switch fabric. After the step 1020, the method 1000 terminates.
FIG. 11 is a flowchart depicting a method 1100 for reducing impact of a repair action in a switch fabric, according to one embodiment of the invention. As shown, the method 1100 begins at step 1110, where a server system is provided that includes a midplane, a first interposer card, and a server card, where the first interposer card is disposed between the midplane and the server card, thereby operatively connecting the midplane and the server card. The first interposer card includes a switch module configured to switch network traffic for the server card. The first interposer card is hot-swappable from the midplane, and the server card is hot-swappable from the first interposer card. At step 1120, the server system detects that the switch module has failed. At step 1130, upon detecting that the switch module has failed, the server system outputs for display an indication to perform a repair action on the switch module. During the repair action, impact of the repair action on the switch module is localized to the server card and does not impact connectivity of the switch fabric. After the step 1130, the method 1100 terminates.
Advantageously, embodiments of the invention reduce impact of a repair action in a switch fabric. One embodiment of the invention provides a server system that includes a first interposer card disposed between one or more server cards and a midplane. The first interposer card includes a switch module that switches network traffic for the one or more server cards. The first interposer card is hot-swappable from the midplane, and the one or more server cards are hot-swappable from the first interposer card. When the switch module fails, the switch module may be replaced without powering off or restarting the server system and/or switch fabric. Accordingly, the impact of the repair action is localized to the server card. Availability of the server system and/or the switch fabric is thereby improved, and costs associated with the repair action are thereby reduced. Additionally or alternatively, where the switch fabric provides redundancy in terms of connectivity, embodiments of the invention configure the server system so as to reduce impact of the repair action on the provided redundancy.
While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.

## Claims

1. A computer-implemented method to limit impact of a repair action on availability of a server system, the computer-implemented method comprising:
providing the server system, which comprises a midplane, a first interposer card, and a plurality of server cards providing a plurality of compute nodes each having local storage, each server card executing a respective hypervisor that in turn executes a respective plurality of virtual machines, the plurality of server cards including a first server card, wherein the first interposer card is disposed between the midplane and the first server card, thereby operatively connecting the midplane and the first server card, wherein the first interposer card comprises a switch module configured to switch network traffic for the first server card, wherein the first interposer card is hot-swappable from the midplane, wherein the first server card is hot-swappable from the first interposer card;
detecting that the switch module has failed, by operation of one or more computer processors; and
upon detecting that the switch module has failed, outputting for display an indication to perform the repair action on the switch module.

2. The computer-implemented method of claim 1, wherein impact of the switch module failing is localized to the first server card.

3. The computer-implemented method of claim 1, wherein the repair action comprises replacing the switch module, wherein impact of replacing the switch module is localized to the first server card.

4. The computer-implemented method of claim 3, wherein replacing the switch module comprises replacing the first interposer card with a second interposer card comprising a functional switch module.

5. The computer-implemented method of claim 1, wherein at least one of the first server card and the first interposer card is configured to be replaced with a functional replacement, without requiring a restart of the server system and without requiring a restart of a switch fabric that includes the switch module.

6. The computer-implemented method of claim 5, wherein the server system is configured to integrate the functional replacement into the switch fabric, without requiring a restart of the server system and without requiring a restart of the switch fabric.

7. The computer-implemented method of claim 1, wherein the switch module is configured to be replaced without requiring the midplane to be replaced.

8. The computer-implemented method of claim 1, wherein the server system comprises a blade system, wherein each server card comprises a server blade, wherein the network traffic comprises at least one of: (i) Ethernet traffic and (ii) Fibre Channel over Ethernet (FCoE) traffic.

9. The computer-implemented method of claim 1, wherein the plurality of server cards further includes a shared storage node configured to provide shared storage to at least the plurality of compute nodes, wherein the plurality of server cards further includes a shared input/output (I/O) node configured to provide shared I/O adapters to at least the plurality of compute nodes.

10. The computer-implemented method of claim 9, wherein the server system includes management firmware configured to monitor health of the server system and detect that the switch module has failed, wherein an indication that the switch module has failed is output for display to a user via a graphical user interface (GUI) screen upon determining that the switch module has failed.

11. The computer-implemented method of claim 10, wherein a second server card of the plurality of server cards and operatively connected to the second interposer card does not lose connectivity to the switch fabric upon the failure of the switch module of the second interposer card, wherein each interposer card further comprises a converged network adapter (CNA), wherein the interposer interconnect comprises cabling between the CNA of the first interposer card and the CNA of the second interposer card, wherein impact of the switch module failing is localized to the first server card, wherein the repair action comprises replacing the switch module, wherein impact of replacing the switch module is localized to the first server card.

12. The computer-implemented method of claim 11, wherein replacing the switch module comprises replacing the first interposer card with a second interposer card comprising a functional switch module, wherein at least one of the first server card and the first interposer card is configured to be replaced with a functional replacement, without requiring a restart of the server system and without requiring a restart of the switch fabric.

13. The computer-implemented method of claim 12, wherein the server system is configured to integrate the functional replacement into the switch fabric, without requiring a restart of the server system and without requiring a restart of the switch fabric, wherein the switch module is configured to be replaced without requiring the midplane to be replaced.

14. The computer-implemented method of claim 13, wherein the server system comprises a blade system, wherein each server card comprises a server blade, wherein the network traffic comprises, in respective instances, each traffic type selected from: (i) Ethernet traffic and (ii) Fibre Channel over Ethernet (FCoE) traffic, wherein the CNA is configured to support both Fibre Channel Host Bust Adapter (HBA) and Ethernet network interface controller (NIC) functionality.

15. The computer-implemented method of claim 14, wherein each server blade includes a baseboard management controller (BMC) configured to provide local supervisory control of the respective server blade and further configured to communicate with a management module via, in respective instances: (i) an in-band network comprising a local area network (LAN) and (ii) an out-of-band network comprising switch modules and NICs.

16. The computer-implemented method of claim 15, wherein the LAN is configured to facilitate communications between the server blade and the management module relating to remote Basic Input/Output System (BIOS) settings and management, wherein each of the server blade and the management module is configured to use the BMC as a proxy to communicate with one another via a predefined protocol, wherein the predefined protocol comprises a Telecommunications Industry Association 485 (TIA-485) protocol.

17. The computer-implemented method of claim 16, wherein each server blade is operatively connected to a network interface controller (NIC) and is assigned a unique network address via Dynamic Host Configuration Protocol (DHCP), wherein the network address comprises an Internet Protocol (IP) address, wherein each NIC is operatively connected to a pair of integrated modules providing redundancy for one another, wherein the pair of integrated modules includes redundant array of independent disks (RAID) controllers, of which at least one RAID controller is operatively connected to a plurality of storage devices in a predefined RAID configuration.

18. The computer-implemented method of claim 17, wherein the server system includes a plurality of nodes including the plurality of compute nodes, the shared storage node, and the shared I/O node, wherein each node in the server system and reachable from the switch fabric prior to failure of the switch module remains reachable from the switch fabric subsequent to failure of the switch module and prior to the repair action.

19. The computer-implemented method of claim 18, wherein each node in the server system and reachable from the switch fabric prior to failure of the switch module remains reachable from the switch fabric during the repair action, except for any nodes of server cards coupled to the interposer card having the failed switch module, wherein each node is selected from a compute node, a shared storage node, and a shared I/O node.

20. The computer-implemented method of claim 1, wherein the repair action comprises replacing the switch module.