Patent Description:
As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.

Existing server architectures either provide a single monolithic server capable of running one operating system (or a single hypervisor running multiple virtualized operating systems) and input/output ("I/O") resources at a time, or bulky blade server chassis providing multiple servers and I/O control modules in a single chassis. A system chassis with multiple information handling systems with various peripheral and I/O capabilities common to the chassis as a whole may provide advantages, as it allows a blade server chassis in a small form factor, thereby providing a blade server chassis with a size comparable to the size of a monolithic server. Implementation of a system chassis with multiple information handling systems with various peripheral and I/O capabilities common to the chassis as a whole presents numerous challenges.

<CIT> discloses a method, system, and software instructions for allocating power in an information handling system, which are operable to respond to a power profiling request by transitioning a processing resource to a first power consumption state and obtaining and storing a first power consumption value.

<CIT> discloses systems and methods, which provide altitude-dependent fan control for a plurality of electronic subsystems using a shared air pressure sensor. Each server or multi-server chassis of a rack system is a subsystem of the rack system. Each subsystem receives its own on-board fan or blower module. The shared air pressure sensor senses air pressure and outputs a signal to all of the subsystems. Each subsystem then independently regulates its own fan speed according to the signal output by the shared air pressure sensor.

<CIT> discloses a baseboard management controller (BMC) of a blade server module in an information handling system.

<CIT> discloses a method for managing information from an operating system based environment includes determining whether the information is to be communicated to a chassis management module.

In the following, the parts of the description and drawings referring to embodiments which are not covered by the claims are not presented as embodiments of the invention but as background art or examples useful for understanding the invention.

In accordance with the teachings of the present disclosure, the disadvantages and problems associated with traditional approaches to monitoring and management in an information handling system chassis may be reduced or eliminated.

Technical advantages of the present disclosure may be readily apparent to one skilled in the art from the figures, description and claims included herein. The objects and advantages of the embodiments will be realized and achieved at least by the elements, features, and combinations particularly pointed out in the claims.

It is to be understood that both the foregoing general description and the following detailed description are examples and explanatory and are not restrictive of the claims set forth in this disclosure.

A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:.

Preferred embodiments and their advantages are best understood by reference to <FIG>, wherein like numbers are used to indicate like and corresponding parts.

For the purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a personal digital assistant (PDA), a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components of the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more busses operable to transmit communication between the various hardware components.

For the purposes of this disclosure, computer-readable media may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; as well as communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.

In this disclosure, the term "information handling resource" may broadly refer to any component system, device or apparatus of an information handling system, including without limitation processors, busses, memories, input-output devices and/or interfaces, storage resources, network interfaces, motherboards, electro-mechanical devices (e.g., fans), displays, and power supplies.

<FIG> illustrates a perspective view of a chassis <NUM> for receiving modular information handling resources, in accordance with embodiments of the present invention, with certain elements (e.g., walls for enclosing components within chassis <NUM>) cut-away or removed in order to show information handling resources internal to chassis <NUM>. Chassis <NUM> may be an enclosure that serves as a container for various information handling systems and information handling resources, and may be constructed from steel, aluminum, plastic, and/or any other suitable material. Although the term "chassis" is used, chassis <NUM> may also be referred to as a case, cabinet, tower, box, enclosure, and/or housing. In certain embodiments, chassis <NUM> may be configured to hold and/or provide power to a plurality of information handling systems and/or information handling resources. As depicted in <FIG>, chassis <NUM> may include one or more slots <NUM> configured to receive drawers <NUM> for carrying information handling resources, as described in greater detail below. For example, some drawers <NUM> may include one or more information handling systems. As another example, some drawers <NUM> may include one or more peripherals (e.g., hard disk drives, graphics processing units, etc.) associated with information handling systems disposed in another drawer <NUM>.

Each drawer <NUM> may include an interface connector <NUM> configured to electrically couple to a midplane <NUM>, thus providing electrical coupling between information handling resources carried on the various drawers <NUM> to each other and/or one or more networks or devices external to chassis <NUM>. Midplane <NUM> may comprise any system, device, or apparatus configured to interconnect information handling resources of chassis <NUM> with each other. Accordingly, midplane <NUM> may include slots, pads, and/or other connectors configured to receive corresponding electrical connectors of information handling resources in order to electrically couple information handling systems disposed in drawers <NUM> and/or information handling resources to each other.

A chassis management controller (CMC) <NUM> may be communicatively coupled to midplane <NUM> and may comprise any system, device, or apparatus configured to facilitate management and/or control of components of chassis <NUM>, information handling systems modularly coupled within, and/or one or more of its component information handling resources. CMC <NUM> may be configured to issue commands and/or other signals to manage and/or control information handling systems coupled to slots <NUM> and/or information handling resources of chassis <NUM>. CMC <NUM> may comprise a microprocessor, microcontroller, DSP, ASIC, field programmable gate array ("FPGA"), EEPROM, or any combination thereof.

In addition or alternatively, CMC <NUM> may also provide a management console for user/administrator access to these functions. For example, CMC <NUM> may provide for communication with a user interface (e.g., user interface <NUM>), permitting a user to interact with CMC <NUM> and configure control and management of components of chassis <NUM> by CMC <NUM>. As another example, CMC <NUM> may implement Web Services Management ("WS-MAN") or another suitable management protocol permitting a user to remotely access a CMC <NUM> to configure chassis <NUM> and its various information handling resources. A CMC <NUM> interfaces with a network interface separate from a traditional network interface of chassis <NUM>, thus allowing for "out-of-band" control of chassis <NUM>, such that communications to and from CMC <NUM> are communicated via a management channel physically isolated from an "in band" communication channel with the traditional network interface. Thus, for example, if a failure occurs in chassis <NUM> that prevents an administrator from interfacing with chassis <NUM> via a traditional network interface and/or user interface <NUM> (e.g., operating system failure, power failure, etc.), the administrator may still be able to monitor and/or manage chassis <NUM> (e.g., to diagnose problems that may have caused failure) via CMC <NUM>. In the same or alternative embodiments, CMC <NUM> may allow an administrator to remotely manage one or more parameters associated with operation of chassis <NUM> and its various information handling resources (e.g., power usage, processor allocation, memory allocation, security privileges, etc.).

One or more air movers <NUM> may be communicatively coupled to CMC <NUM>, and may include any mechanical or electro-mechanical system, apparatus, or device operable to move air and/or other gasses. In some embodiments, an air mover <NUM> may comprise a fan (e.g., a rotating arrangement of vanes or blades which act on the air). In other embodiments, an air mover <NUM> may comprise a blower (e.g., a centrifugal fan that employs rotating impellers to accelerate air received at its intake and change the direction of the airflow). In these and other embodiments, rotating and other moving components of an air mover <NUM> may be driven by a motor. The rotational speed of such motor may be controlled by one or more control signals communicated from CMC <NUM>. In operation, an air mover <NUM> may cool information handling systems and information handling resources of chassis <NUM> by drawing cool air into chassis <NUM> from outside chassis <NUM>, expel warm air from inside chassis <NUM> to the outside of chassis <NUM>, and/or move air across one or more heatsinks (not explicitly shown) internal to chassis <NUM> to cool one or more information handling systems and/or information handling resources. Although <FIG> depicts chassis <NUM> as having two air movers <NUM>, chassis <NUM> may include any suitable number of air movers <NUM>.

As shown in <FIG>, chassis <NUM> may include one or more power supplies <NUM>. Generally speaking, a power supply <NUM> may include any system, device, or apparatus configured to supply electrical current to one or more information handling resources within chassis <NUM>.

A user interface <NUM> may include any system, apparatus, or device via which a user may interact with chassis <NUM> and its various components by facilitating input from a user allowing the user to manipulate chassis <NUM> and output to a user allowing chassis <NUM> to indicate effects of the user's manipulation. For example, user interface <NUM> may include a display suitable for creating graphic images and/or alphanumeric characters recognizable to a user, and may include, for example, a liquid crystal display, a cathode ray tube, a plasma screen, and/or a digital light processor projection monitor. In certain embodiments, such a display may be an integral part of chassis <NUM> and receive power from one or more power supplies <NUM> of chassis <NUM>, rather than being coupled to chassis <NUM> via a cable. In some embodiments, such display may comprise a touch screen device capable of receiving user input, wherein a touch sensor may be mechanically coupled or overlaid upon the display and may comprise any system, apparatus, or device suitable for detecting the presence and/or location of a tactile touch, including, for example, a resistive sensor, capacitive sensor, surface acoustic wave sensor, projected capacitance sensor, infrared sensor, strain gauge sensor, optical imaging sensor, dispersive signal technology sensor, and/or acoustic pulse recognition sensor. In these and other embodiments, user interface <NUM> may include other user interface elements (e.g., a keypad, buttons, and/or switches placed in proximity to a display) allowing a user to provide input to chassis <NUM>. In these and other embodiments, user interface <NUM> may include one or more visual indicators, such as light-emitting diodes, for example, for communicating information to a user. User interface <NUM> may be coupled to CMC <NUM> and/or other components of chassis <NUM>, and thus may allow a user to configure various information handling systems and/or information handling resources of chassis <NUM>.

<FIG> and <FIG> depict various views of an example chassis drawer 104A for carrying modular information handling resources, in accordance with embodiments of the present invention. <FIG> illustrates a perspective view of an example chassis drawer 104A for carrying modular information handling resources, wherein drawer 104A is in an open position drawn from chassis <NUM>, in accordance with embodiments of the present disclosure. <FIG> illustrates a perspective view of chassis drawer 104A for carrying modular information handling resources, wherein drawer 104A is in a closed position relative to chassis <NUM>, in accordance with embodiments of the present disclosure.

As shown in <FIG> and <FIG>, chassis drawer 104A may comprise an inner member <NUM>, an intermediate member <NUM> mechanically coupled to inner member <NUM>, and a carrier member <NUM> mechanically coupled to intermediate member <NUM>. Inner member <NUM> may be constructed from steel, aluminum, plastic, and/or any other suitable material. Although inner member <NUM> may have any suitable size and/or shape, inner member <NUM> is depicted in the embodiments of <FIG> and <FIG> as having two substantially planar and parallel opposite sides defining a drawer height coupled to each other by a substantially planar bottom generally perpendicular to the sides defining a drawer width and a guide flange extending from and running perpendicular to and along the length of each side such that the flanges project towards each other. In some embodiments, inner member <NUM> may be mechanically coupled to the internal mechanical structure of chassis <NUM>, such that inner member <NUM> is fixed relative to chassis <NUM>.

Intermediate member <NUM> may be constructed from steel, aluminum, plastic, and/or any other suitable material. Although intermediate member <NUM> may have any suitable size and/or shape, intermediate member <NUM> is depicted in the embodiments of <FIG> and <FIG> as having two generally parallel and planar opposite sides coupled to each other by a substantially planar bottom generally perpendicular to the sides. The height of the sides and the width of the bottom may be such that the corresponding sides and bottom of inner member <NUM> provide a mechanical guide for intermediate member <NUM> as chassis drawer 104A is opened and closed. Intermediate member <NUM> may be mechanically coupled to inner member <NUM> via bearings and/or other mechanical components such that intermediate member <NUM> may slide relative to inner member <NUM> in a direction perpendicular to the drawer height and drawer width defined by inner member <NUM>. In some embodiments, intermediate member <NUM> may be limited in the distance it may be drawn from chassis <NUM> through any combination of suitable structural elements. Similarly, in some embodiments, other mechanical components may restrict motion of intermediate member <NUM> relative to inner member <NUM> as chassis drawer 104A is translated from the open position to the closed position.

Carrier member <NUM> may be constructed from steel, aluminum, plastic, and/or any other suitable material. Although carrier member <NUM> may have any suitable size and/or shape, carrier member <NUM> is depicted in the embodiments of <FIG> and <FIG> as having a substantially planar top <NUM> and a substantially planar bottom <NUM> generally parallel to each other defining a width and depth of carrier member <NUM>, the top <NUM> and bottom <NUM> mechanically coupled to each other by one or more structural elements defining a height of carrier member <NUM>, such that top <NUM> and bottom <NUM> are generally perpendicular to the sides of intermediate member <NUM>. Carrier member <NUM> may also include a face <NUM> mechanically affixed to top <NUM> and/or bottom <NUM>. As shown in <FIG> and <FIG>, top <NUM> may include one or more openings (e.g., above bays <NUM>) allowing for gaseous fluid to pass through. Similarly, bottom <NUM> may also include one or more openings (e.g., below bays <NUM>) allowing for gaseous fluid to pass through.

In some embodiments, face <NUM> may be substantially equal in width to the width of carrier member <NUM> and substantially equal to the height of carrier member <NUM>. In these and other embodiments, face <NUM> may include handles, pull tabs, and/or other features allowing a person to pull on face <NUM> in order to translate chassis drawer 104A from a closed position to an open position in a direction generally parallel to the depth of top <NUM> and bottom <NUM>. In these and other embodiments, face <NUM> may include a grill, vent, and/or other opening allowing gaseous fluid to enter and/or exit through face <NUM>.

As shown in <FIG>, each side of carrier member <NUM> (e.g., portions of carrier member <NUM> between the edges of and substantially parallel to top <NUM> and bottom <NUM>) may include a web <NUM> configured to mechanically couple carrier member <NUM> to intermediate member <NUM>, as well as openings for a plurality of bays <NUM>.

Each of the various bays <NUM> defined by drawer 104A may include one or more electrical components for coupling an information handling resource (e.g., a hard disk drive) inserted into such bay <NUM> to other information handling resources of chassis <NUM>. For example, a backplane (not explicitly shown) may couple a modular information handling resource disposed in a bay <NUM> to interface connector 118A, which, as described above, may in turn be coupled to midplane <NUM>. In some embodiments, the various information handling resources may be coupled to interface connector 118A such that when chassis drawer 104A is drawn open relative to chassis <NUM>, such information handling resources maintain electrical conductivity to interface connector 118A and interface connector 118A may maintain electrical conductivity to midplane <NUM>, thus permitting insertion or removal of an information handling resource without affecting operation of other information handling resources carried by chassis drawer 104A. In such embodiments, interface connector 118A may only be decoupled from midplane <NUM> when the entirety of chassis drawer 104A is removed from chassis <NUM>.

<FIG> illustrates a perspective view of another example chassis drawer 104B for carrying information handling resources, in accordance with embodiments of the present invention. Although not labeled in detail as in <FIG> and <FIG>, chassis drawer 104B may include one or more mechanical and/or structural elements (e.g., similar or identical to inner member <NUM>, intermediate member <NUM>, and carrier member <NUM>) for translating chassis drawer 104B between open and closed positions relative to chassis <NUM>. Similar to chassis drawer 104A, the various information handling resources carried by chassis drawer 104B may be coupled to interface connector 118B such that when chassis drawer 104B is drawn open relative to chassis <NUM>, such information handling resources maintain electrical conductivity to interface connector 118B and interface connector 118B may maintain electrical conductivity to midplane <NUM>, thus permitting insertion or removal of an information handling resource without affecting operation of other information handling resources carried by chassis drawer 104B. In such embodiments, interface connector 118B may only be decoupled from midplane <NUM> when the entirety of chassis drawer 104B is removed from chassis <NUM>.

In the particular chassis drawer 104B depicted in <FIG>, a backplane <NUM> may have thereon a plurality (e.g., four) of processors <NUM> and a chipset associated with each processor <NUM>, thus defining four independent information handling systems carried by chassis drawer 104B. Interface connector 118B may also be coupled to backplane <NUM>, thus coupling processors <NUM> to information handling resources of chassis <NUM> external to chassis drawer 104B. In addition, the particular chassis drawer 104B depicted in <FIG> may include a plurality (e.g., four) of hard disk drives <NUM> communicatively coupled to backplane <NUM> (and thus one or more of processors <NUM>) via a drive backplane <NUM>.

As shown in <FIG>, chassis drawer 104B may comprise a user interface <NUM>. User interface <NUM> may include any system, apparatus, or device via which a user may interact with compute nodes (e.g., via a remote access controller such as an Integrated Dell Remote Access Controller or "iDRAC" for example) of chassis drawer 104B and its various components by facilitating input from a user allowing the user to compute nodes and to indicate effects of the user's manipulation. For example, user interface <NUM> may include a display suitable for creating graphic images and/or alphanumeric characters recognizable to a user, and may include, for example, a liquid crystal display, a cathode ray tube, a plasma screen, and/or a digital light processor projection monitor. In some embodiments, such display may comprise a touch screen device capable of receiving user input, wherein a touch sensor may be mechanically coupled or overlaid upon the display and may comprise any system, apparatus, or device suitable for detecting the presence and/or location of a tactile touch, including, for example, a resistive sensor, capacitive sensor, surface acoustic wave sensor, projected capacitance sensor, infrared sensor, strain gauge sensor, optical imaging sensor, dispersive signal technology sensor, and/or acoustic pulse recognition sensor. In these and other embodiments, user interface <NUM> may include other user interface elements (e.g., a keypad, buttons, and/or switches placed in proximity to a display) allowing a user to provide input to one or more compute nodes of chassis drawer 104B. In these and other embodiments, user interface <NUM> may include one or more visual indicators, such as light-emitting diodes, for example, for communicating information to a user.

Although <FIG> depict particular example chassis drawers <NUM>, chassis drawers <NUM> with other configurations may be employed consistent with the systems and methods herein disclosed. For example, in some embodiments, a chassis drawer <NUM> similar to that of chassis drawer 104B may include only one processor, such that the chassis drawer includes one compute node.

<FIG> illustrates an example functional block diagram of chassis <NUM> depicted in <FIG>, wherein chassis <NUM> has disposed in one of its slots <NUM> a chassis drawer 104B carrying a plurality of information handling systems <NUM>, in accordance with embodiments of the present invention.

As shown in <FIG>, chassis <NUM> may include other chassis drawers <NUM>, wherein such chassis drawers <NUM> may carry information handling systems, hard disk drives, and/or other information handling resources which may or may not be similar to chassis drawers 104A and 104B described above.

As shown in <FIG>, chassis drawer 104B may include a plurality of information handling systems <NUM> (e.g., 502a-d), each of which may comprise a server or other suitable computing node, an in-band switch <NUM>, an out-of-band switch <NUM>, one or more sensor <NUM>, and one or more other information handling resources <NUM>. Among other components, an information handling system <NUM> may comprise a processor <NUM>, a network interface <NUM> communicatively coupled to its associated processor <NUM>, and a remote access controller (RAC) <NUM>.

A processor <NUM> may include any system, device, or apparatus configured to interpret and/or execute program instructions and/or process data, and may include, without limitation, a microprocessor, microcontroller, digital signal processor ("DSP"), application specific integrated circuit ("ASIC"), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data. In some embodiments, processor <NUM> may interpret and/or execute program instructions and/or process data stored in a memory or other computer-readable media accessible to processor <NUM>.

A network interface <NUM> may comprise any suitable system, apparatus, or device operable to serve as an interface between an associated information handling system <NUM> and a private communication network internal to chassis drawer 104B formed by information handling systems <NUM> and in-band switch <NUM>. Network interface <NUM> may enable an associated information handling system <NUM> to communicate using any suitable transmission protocol and/or standard. In some embodiments, network interface <NUM> may comprise one or more network interface cards, or "NICs. " In other embodiments, network interface <NUM> may comprise one or more local area network (LAN)-on-motherboard (LOM) devices. In these and other embodiments, network interface <NUM> may include a plurality of NICs, LOMs, or other network interface devices, in order to provide communication redundancy or robustness.

A RAC <NUM> may be implemented by, for example, a microprocessor, microcontroller, DSP, ASIC, EEPROM, or any combination thereof. RAC <NUM> may be configured to communicate with CMC <NUM>. Such communication may be made, for example, via private management network fabric implemented using out-of-band switch <NUM>. RAC <NUM> may be configured to provide out-of-band management facilities for management of an associated information handling system <NUM>. Such management may be made by CMC <NUM> even if information handling system <NUM> is powered off or powered to a standby state. A RAC <NUM> may include a processor, memory, and network connection separate from the rest of its associated information handling system <NUM>. In certain embodiments, A RAC <NUM> may include or may be an integral part of a baseboard management controller (BMC), Dell Remote Access Controller (DRAC) or an Integrated Dell Remote Access Controller (iDRAC).

In-band switch <NUM> may comprise any system, device, or apparatus configured to couple network interfaces <NUM> of information handling systems <NUM> to external network interface <NUM> and perform switching between network interfaces <NUM> and an external communication network communicatively coupled to external network interface <NUM> based on a network configuration of various ports (not explicitly shown) of network interfaces <NUM>, in-band switch <NUM>, and external network interface <NUM>, as described in greater detail below. In-band switch <NUM> may comprise a PCIe switch, a generalized PC bus switch, an Infiniband switch, or other suitable switch.

Similarly, out-of-band switch <NUM> may comprise any system, device, or apparatus configured to couple RACs <NUM> of information handling systems <NUM> to CMC <NUM> and perform switching between RACs <NUM> and CMC <NUM> in order to provide for centralized management of individual information handling systems <NUM> via a management console coupled to CMC <NUM> (e.g., via CMC management port <NUM>).

As shown in <FIG>, an external network interface <NUM> may be communicatively coupled to midplane <NUM>. External network interface <NUM> may comprise any suitable system, apparatus, or device operable to serve as an interface between chassis <NUM> and a network external to chassis <NUM>. External network interface <NUM> may enable an information handling system <NUM> to communicate with such external network using any suitable transmission protocol and/or standard. In some embodiments, external network interface <NUM> may comprise one or more network interface cards, or "NICs. " In other embodiments, external network interface <NUM> may comprise one or more input/output module (IOM) devices. In these and other embodiments, external network interface <NUM> may include a plurality of NICs, IOMs, or other network interface devices, in order to provide communication redundancy or robustness.

In addition, as shown in <FIG>, CMC <NUM> may include storage media <NUM> and a CMC management port <NUM>. Storage media <NUM> may include any system, device, or apparatus configured to retain program instructions and/or data for a period of time (e.g., computer-readable media). Storage media <NUM> may include RAM, EEPROM, a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to CMC <NUM> is turned off.

CMC management port <NUM> serves as a network interface between CMC <NUM> and a remote management console configured to allow a user to remotely manage components of chassis <NUM> via an out-of-band network physically isolated from an in-band network coupled to external network interface <NUM>. CMC management port <NUM> may communicate with such remote management console via any suitable management protocol or standard, including without limitation Intelligent Platform Management Interface (IPMI) and Simple Network Management Protocol (SNMP).

Sensor <NUM> may be coupled to midplane <NUM> and may include any suitable system, device, or apparatus that measures a physical quantity and converts it into a signal which can be read by a processor <NUM>, RAC <NUM>, and/or CMC <NUM>. For example, a sensor <NUM> may include a temperature sensor (e.g., thermocouple, thermistor, thermostat, etc.), a speed sensor (e.g., a Hall effect sensor used to determine rotational speed of an air mover (e.g., an air mover <NUM>), or any other suitable sensor for detecting a physical quantity associated with chassis <NUM> or a component thereof. Based on a measured physical quantity of a sensor <NUM>, an information handling system <NUM> or a component thereof may take an action. As an example, in embodiments in which sensor <NUM> comprises a temperature sensor, an information handling system <NUM> may take corrective or remedial action in response to a sensed temperature exceeding a threshold, such as causing an increase in speed of an air mover <NUM>, reducing power consumption of an information handling system <NUM>, and/or other remedial action. For simplicity of exposition, only one sensor is depicted in <FIG>. However, in embodiments of the present disclosure, a chassis <NUM> may include any number of any combination of types of sensors <NUM>.

One or more information handling resources <NUM> may be communicatively coupled to midplane <NUM> or otherwise disposed in chassis <NUM> and may include one or more processors, service processors, basic input/output systems, buses, memories, I/O devices and/or interfaces, storage resources, network interfaces, motherboards, air movers, power supplies, and/or any other components and/or elements suitable for use in an information handling system. Such information handling resources <NUM> may also include air movers <NUM> and power supply <NUM> depicted in <FIG> but not otherwise depicted in <FIG>. As is known in the art, some information handling resources <NUM> may operate in accordance with firmware instructions stored on a computer-readable medium integral to or otherwise accessible to the information handling resource.

Users of existing rack servers may be accustomed to monitoring and management of an information handling system chassis in which updates to information resources of a chassis are managed and applied by a RAC and which sensors are monitored by a RAC. However, in a distributed modular chassis system such as that depicted in <FIG>, such traditional approaches may not be desired or available, as a CMC may "own" such chassis-level sensors and information handling resources and thus the CMC is responsible for physical management and monitoring of such sensors and information handling systems.

In addition, users of existing rack servers may be accustomed to monitoring and management of an information handling system chassis in which RACs include computer-readable media for storing data and instructions locally to the RAC (e.g., via a flash or secure digital (SD) card). However, in a distributed modular chassis system such as that depicted in <FIG>, physical computer-readable media local to each RAC may not be desired or available, due to physical space limitations.

<FIG> illustrates a flow chart of an example method <NUM> for monitoring chassis-level sensors <NUM>, in accordance with embodiments of the present invention. According to some embodiments, method <NUM> may begin at step <NUM>. As noted above, teachings of the present disclosure may be implemented in a variety of configurations of chassis <NUM>. As such, the preferred initialization point for method <NUM> and the order of the steps comprising method <NUM> may depend on the implementation chosen.

At step <NUM>, CMC <NUM> monitors one or more sensors <NUM> by receiving signals from the one or more sensors <NUM> indicative of the physical quantities measured by such sensors <NUM>.

At step <NUM>, CMC <NUM> may determine if a measured physical quantity of a sensor <NUM> has changed by more than a threshold amount. For example, for a temperature sensor, such threshold amount may be equal to five degrees Celsius. If such a change has occurred, method <NUM> may proceed to step <NUM>. Otherwise, step <NUM> may repeat until such a change has occurred.

At step <NUM>, responsive to a change of a measured physical quantity of a sensor <NUM> by more than the threshold amount, CMC <NUM> may communicate to a RAC <NUM> (e.g., via out-of-bound switch <NUM>) present on a chassis drawer <NUM> disposed in chassis <NUM> an indication that such a change has occurred. Such indication may include an IPMI over LAN command or other suitable command communicated between CMC <NUM> and RAC <NUM> via out-of-band switch <NUM>.

At step <NUM>, responsive to receipt of the indication from CMC <NUM> that a change has occurred in a measured physical quantity of a sensor <NUM>, RAC <NUM> may communicate a request to CMC <NUM> to retrieve (e.g., download) sensor information from CMC <NUM> and may receive the sensor information from CMC <NUM>. Such download may be performed using trivial file transfer protocol (TFTP), IPMI over LAN, or other suitable protocol or standard for file transfer. RAC <NUM> may, alone or in concert with an associated processor <NUM>, process the sensor information in order to model performance of chassis <NUM> components, initiate responsive action to a measured physical quantity, and/or perform any other action. Accordingly, a RAC <NUM> may model chassis <NUM> components in the same fashion as it would in a rack server. CMC <NUM> serves as a proxy between sensors <NUM> and RAC <NUM>.

Although <FIG> discloses a particular number of steps to be taken with respect to method <NUM>, method <NUM> may be executed with greater or fewer steps than those depicted in <FIG>. In addition, although <FIG> discloses a certain order of steps to be taken with respect to method <NUM>, the steps comprising method <NUM> may be completed in any suitable order.

Method <NUM> may be implemented using CMC <NUM>, a remote access controller <NUM>, and/or any other system operable to implement method <NUM>. In certain embodiments, method <NUM> may be implemented partially or fully in software and/or firmware embodied in computer-readable media and executable on a processor or controller.

<FIG> illustrates a flow chart of an example method <NUM> for management of chassis-level information handling resources <NUM>, in accordance with examples embodimenfeo of the present disclosure. According to some embodiments, method <NUM> may begin at step <NUM>. As noted above, teachings of the present disclosure may be implemented in a variety of configurations of chassis <NUM>. As such, the preferred initialization point for method <NUM> and the order of the steps comprising method <NUM> may depend on the implementation chosen.

At step <NUM>, a user may upload to RAC <NUM> a firmware image for a chassis-level information handling resource <NUM>. Such firmware image may include updated firmware for such information handling resource <NUM>. A user may upload the firmware image to RAC <NUM> in any suitable manner, including without limitation, by issuing proper commands via user interface <NUM> or a keyboard-video-mouse interface (not explicitly shown) coupled to chassis <NUM> or a chassis drawer <NUM> including such RAC <NUM>. Such file may be uploaded from a readily-removable computer-readable medium (e.g., flash drive, secure digital (SD) card, etc.), communicatively coupled to RAC <NUM> via a suitable external media interface (e.g., Universal Serial Bus port, SE port) of chassis <NUM> or a chassis drawer <NUM> including such RAC <NUM> (not explicitly shown). During upload, the user may also provide an indication regarding to which information handling resource <NUM> the firmware image is to be applied. Alternatively, the firmware image itself, or metadata associated therewith, may indicate to which information handling resource <NUM> the firmware image is to be applied.

At step <NUM>, RAC <NUM> may communicate to a CMC <NUM> (e.g., via out-of-bound switch <NUM>) an indication that such a firmware update is to be applied to one or more information handling resources <NUM>. Such indication may include an IPMI over LAN command or other suitable command communicated between RAC <NUM> and CMC <NUM> via out-of-band switch <NUM>.

At step <NUM>, responsive to receipt of the indication from RAC <NUM> that a firmware update is available, CMC <NUM> may retrieve the firmware image from RAC <NUM>. Such transfer may be performed using trivial file transfer protocol (TFTP), IPMI over LAN, or other suitable protocol or standard for file transfer.

At step <NUM>, responsive to receipt of the firmware image, CMC <NUM> may perform the firmware update by applying the firmware image to the appropriate information handling resource <NUM>. During such firmware update, CMC <NUM> may, from time-to-time communicate an indication to RAC <NUM> regarding the status of the update. Such indication may include an IPMI over LAN command or other suitable command communicated between RAC <NUM> and CMC <NUM> via out-of-band switch <NUM>. Accordingly, a RAC <NUM> may perform firmware updates and manage chassis <NUM> components in the same fashion as it would in a rack server, with CMC <NUM> serving as an intermediary between information handling resources <NUM> and RAC <NUM>.

<FIG> illustrates a flow chart of an example method <NUM> for allocation of storage media <NUM> associated with CMC <NUM> to a RAC <NUM>, in accordance with examples of the present disclosure. According to some embodiments, method <NUM> may begin at step <NUM>. As noted above, teachings of the present disclosure may be implemented in a variety of configurations of chassis <NUM>. As such, the preferred initialization point for method <NUM> and the order of the steps comprising method <NUM> may depend on the implementation chosen.

At step <NUM>, a RAC <NUM> may determine if storage local to RAC <NUM> (e.g., within the chassis drawer <NUM> comprising the RAC <NUM>) is present and available. If local storage is not available, method <NUM> may proceed to step <NUM>. Otherwise, method <NUM> may end.

At step <NUM>, in response to storage local to RAC <NUM> being available, RAC <NUM> may send a request to CMC <NUM> (e.g., via out-of-band switch <NUM>) to allocate a portion of storage media <NUM> as storage for RAC <NUM>. Such request may include an IPMI over LAN command or other suitable command communicated between RAC <NUM> and CMC <NUM> via out-of-band switch <NUM>.

At step <NUM>, responsive to the request from RAC <NUM>, CMC <NUM> may determine if a portion of storage media <NUM> is available responsive to the request from RAC <NUM>. If a portion of storage media <NUM> is available, method <NUM> may proceed to step <NUM>. Otherwise, method <NUM> may end.

At step <NUM>, CMC <NUM> may allocate a portion of storage within storage media <NUM> to RAC <NUM>. At step <NUM>, CMC <NUM> may create a share (e.g., a Network File System (NFS) share) comprising the allocated portion. At step <NUM>, CMC <NUM> may communicate the share name or other identifying information for the created share to RAC <NUM>. Such communication may include an IPMI over LAN command or other suitable command communicated between CMC <NUM> and RAC <NUM> via out-of-band switch <NUM>.

At step <NUM>, in response to receipt of the share name, RAC <NUM> may mount the share as a logical storage medium of RAC <NUM>. Accordingly, should RAC <NUM> require file storage I/O, it may issue the appropriate I/O commands to the mounted share, and a portion of storage media <NUM> may serve as virtual storage for RAC <NUM>.

Similarly, portions of storage media <NUM> may also be allocated for a plurality of RACs <NUM> present in chassis <NUM> using methods similar to those described with respect to method <NUM>.

Claim 1:
A method to provide a management console for a user or administrator, comprising, in a chassis (<NUM>) having a plurality of slots (<NUM>) each configured to receive a module (<NUM>) having one or more information handling systems (<NUM>) wherein each slot (<NUM>) is configured to electrically and communicatively couple the module (<NUM>) to other components of the chassis (<NUM>):
receiving, by a chassis management controller (<NUM>) integral to the chassis (<NUM>), a signal from a sensor (<NUM>) integral to the chassis (<NUM>), the signal indicative of a physical quantity measured by the sensor (<NUM>); characterized by
communicating, from the chassis management controller (<NUM>) to a remote access controller (<NUM>) integral to at least one module (<NUM>) disposed in the plurality of slots (<NUM>), sensor information in conformity with the signal, wherein the chassis management controller (<NUM>) is configured to serve as a proxy between the sensor (<NUM>) and the remote access controller (<NUM>), wherein the chassis management controller (<NUM>) interfaces with a network interface separate from a network interface of the chassis (<NUM>), which allows out-of-band control of the chassis (<NUM>) such that communications to and from the chassis management controller (<NUM>) are communicated via a management channel physically isolated from an in-band communication channel with the network interface of the chassis (<NUM>).