Patent Description:
Equipment racks in data centers provide structural support for various equipment, such as data servers, storage systems, and the like. In some cases, power distribution, environmental control, and network communications capabilities may be integrated with, installed in, or otherwise made available at an equipment rack. Conventional network equipment is mounted in the rack, takes up one or more spaces in the rack, require various length data cables to reach various other equipment in the rack, and provide little or no integration with power distribution capabilities. Documents <CIT>, <CIT>, <CIT>, <CIT> and <CIT> disclose examples of communication network switches according to available prior art.

Aspects and embodiments are generally directed to communication network switches having an advantageous form factor for physical integration at the rack level. Examples of the aspects and embodiments discussed herein provide one or more network ports associated with particular positions within the rack (e.g., a rack U space), and may include further integration with power distribution such that data center management systems may readily or automatically identify power outlets utilized by particular equipment in the rack.

According to one aspect, a communication network switch is provided according to claim <NUM>. The communication network switch includes an elongated enclosure physically configured to be aligned along the height of an equipment rack, a plurality of network ports distributed along a length of the enclosure such that each of the network ports is substantially physically associated with at least one of a plurality of mounting spaces within the equipment rack when the enclosure is installed to the equipment rack, and a controller coupled to the plurality of network ports and configured to provide communications between the plurality of network ports.

Some embodiments may include one or more uplink ports, and the controller may be further configured to provide communications between the plurality of network ports and the uplink ports. In certain embodiments, the controller may be further configured to detect an identifier of a piece of equipment connected to an identified one of the plurality of network ports and to communicate the identifier to a remote system via the one or more uplink ports.

The invention includes a plurality of power outlets distributed along the length of the enclosure such that each of the plurality of network ports may be substantially physically associated with at least one of the plurality of power outlets. The controller is further configured to identify a piece of equipment connected to an identified one of the plurality of network ports and to associate at least one of the plurality of power outlets to the piece of equipment based upon the physical association of the at least one of the plurality of power outlets with the identified network port.

The invention includes a plurality of power outlets distributed along the length of the enclosure such that each of the power outlets is substantially physically associated with at least one of the plurality of mounting spaces.

Various embodiments include the equipment rack.

According to another aspect, a communication network switch,according to claim <NUM>, is provided that includes a plurality of network ports, a plurality of power connections, each of the plurality of power connections logically associated with at least one of the plurality of network ports, and a controller coupled to the plurality of network ports and configured to provide communications between the plurality of network ports.

The controller is further configured to identify a piece of equipment connected to at least one of the plurality of network ports based upon network traffic on the at least one of the plurality of network ports. The controller is further configured to identify at least one of the plurality of power connections as providing power to the piece of equipment based upon the logical association of each of the plurality of power connections with the at least one of the plurality of network ports.

In certain embodiments, each of the plurality of network ports is physically associated with at least one of the plurality of power connections.

The invention includes a chassis physically configured to substantially align along a height of an equipment rack. The plurality of network ports is distributed along the chassis such that each of the network ports is substantially physically associated with at least one of a plurality of mounting spaces within the equipment rack when the enclosure is installed to the equipment rack. The controller is further configured to identify a piece of equipment connected to at least one of the plurality of network ports based upon network traffic on the at least one of the plurality of network ports and to identify at least one of the plurality of mounting spaces as being associated with the piece of equipment based upon the physical association of the at least one of the plurality of mounting spaces with the at least one of the plurality of network ports.

According to another aspect, a method of managing equipment mounted in a rack is provided according to claim <NUM>.

The method includes detecting network activity on a network port, identifying the equipment from the network activity, associating the equipment with the network port, and associating the equipment with at least one of a rack space and a power outlet based upon an affiliation of the at least one rack space or power outlet with the network port.

In some embodiments the method may include communicating to a remote device an identifier of the equipment, the network port, and the at least one rack space or power outlet.

Some embodiments include detecting an amount of power provided via the associated power outlet. Certain embodiments include determining an expected power consumption of the equipment based upon the identification of the equipment, and may include detecting a potential wiring fault based upon a comparison of the expected power consumption to the detected amount of power.

Certain embodiments include identifying an associated rack space based upon an affiliation of the associated rack space with the network port and populating a database to indicate that the equipment is installed in the associated rack space.

Still other aspects, embodiments, examples, and advantages of these exemplary aspects and embodiments are discussed in detail below. Examples disclosed herein may make references to "an example," "some examples," "an alternate example," "various examples," "one example" or the like which are not necessarily mutually exclusive and are intended to indicate that a particular feature, structure, or characteristic described may be included in at least one example. The appearances of such terms herein are not necessarily all referring to the same example.

Various aspects of at least one embodiment are discussed below with reference to the accompanying drawings, which are not intended to be drawn to scale. The drawings are included to provide illustration and a further understanding of the various aspects and embodiments, and are incorporated in and constitute a part of this specification, but are not intended as a definition of the limits of the disclosure. In the drawings:.

Systems and methods discussed herein are directed to network switches configured to provide network connectivity to various equipment within a rack. The network switches are configured to affiliate each network port with either of a physical space in the rack, or a power outlet, or both. The network switches may affiliate the network ports with rack spaces and/or power outlets through a physical affiliation, e.g., proximity of each network port within the chassis/enclosure of the switch to the rack space and/or power outlet. The power outlet(s) may be provided in the same chassis/enclosure as the network ports, in some embodiments. Physical proximity of network ports, power outlets, and rack spaces facilitates ease of installation, reduces cost of varying cables, and reduces the risk of mis-connection of equipment, thus also reducing cost. The network switches may also affiliate network ports with rack spaces and/or power outlets through a logical affiliation, such as may be maintained in the memory of a controller, console, or management system, for example.

Examples of the methods and systems discussed herein are not limited in application to the details of construction and the arrangement of components set forth in the following description or illustrated in the accompanying drawings. The methods and systems are capable of implementation in other embodiments and of being practiced or of being carried out in various ways. Examples of specific implementations are provided herein for illustrative purposes only and are not intended to be limiting. In particular, acts, components, elements and features discussed in connection with any one or more examples are not intended to be excluded from a similar role in any other examples.

Any references to examples, embodiments, components, elements or acts of the systems and methods herein referred to in the singular may also embrace embodiments including a plurality, and any references in plural to any embodiment, component, element or act herein may also embrace embodiments including only a singularity. References in the singular or plural form are not intended to limit the presently disclosed systems or methods, their components, acts, or elements. The use herein of "including," "comprising," "having," "containing," "involving," and variations thereof is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. References to "or" may be construed as inclusive so that any terms described using "or" may indicate any of a single, more than one, and all of the described terms.

<FIG> is an illustration of an equipment rack <NUM> and a network switch <NUM> in accord with at least one embodiment. The equipment rack <NUM> may include a frame <NUM> and mounting rails <NUM> that define a number of rack spaces <NUM> (e.g., rack U spaces), each of which may accommodate a piece of equipment. In various examples, rack-mounted equipment may take up one or more spaces <NUM>. In some examples, equipment may take up less than one space <NUM>, such as by being half-width or half-height of a space <NUM>. Examples of such equipment include servers, data storage gear, network communications equipment, power supply equipment, environmental control equipment, user interface equipment such as keyboards and video displays, and the like. Many of these example pieces of equipment may be network enabled, capable of being connected to a network for the purpose of management of the equipment, or as the primary function of the equipment, or both. For example, a web server may have one or more network interfaces (e.g., network ports, network connectors), to accommodate its primary function out to an internet and also to allow management of the web server. In some examples, the equipment may have one or more network ports for out-of-band (OOB) management and also may have one or more network ports for primary and/or redundant user data connectivity. Other equipment may be network enabled for management purposes only. For example, a cooling component may provide cooling to the rack and be network enabled for monitoring and/or control of the cooling component.

Accordingly, various equipment installed in the rack may be network enabled. The example network switch <NUM> includes network ports <NUM> that provide network connectivity to various equipment in the rack. The network switch <NUM> is physically configured to be mounted vertically, along the vertical length of the rack <NUM>, and substantially, though not necessarily, the full height of the rack <NUM>. In various embodiments, the network switch <NUM> may have a top-down or a bottom-up orientation, for numbering of network ports <NUM> and/or location of power supply cordage (and/or network uplink ports <NUM>, if included). In at least one embodiment, the network switch <NUM> is configured to be mounted in the back of an equipment rack. The network switch <NUM> does not require any of the spaces <NUM> for its physical accommodation, and may be mountable on a rear portion of the rack <NUM>. In some embodiments, the network switch <NUM> may be physically configured to be accommodated in a rear vertical channel of the rack <NUM>, alongside power distribution equipment, and/or integrated with vertically oriented power distribution equipment, which also may be top-down or bottom-up oriented, e.g., for electrical power outlet numbering.

As illustrated in <FIG>, each of the network ports <NUM> is associated with a space <NUM> in the rack <NUM>. In the embodiment shown in <FIG>, two of the network ports <NUM> are associated with a single space <NUM> in the rack <NUM>. In other embodiments, a single network port <NUM> or more network ports <NUM> may be associated with a single space <NUM>. Further to the example network switch <NUM> illustrated in <FIG>, not necessarily all the spaces <NUM> have a network port <NUM> associated therewith. In other embodiments, however, every space of a rack may have a network port associated therewith. Accordingly, in various embodiments, each of a plurality of network ports (e.g., network ports <NUM>) is associated with one space of a rack (e.g., space <NUM>).

Various advantages are provided by the example network switch <NUM>. For example, each of the network ports <NUM> are substantially consistently placed, physically, relative to the rack space <NUM> it serves. Accordingly, network data cables from each network port <NUM> to a piece of equipment mounted in a respective space <NUM> may be of a consistent and minimal length, thereby reducing cabling costs, simplifying cable purchasing and inventory, and reducing the need for complex cable management, e.g., reduced need to route long cables through the rack. Further advantage is had in that each of the plurality of network ports <NUM> is associated with a particular space <NUM>, such that each of the plurality of network ports may be associated with a particular piece of equipment, based upon the known relationship of the network ports to a space in the rack. Such a relationship between network ports and equipment may be discoverable in an automated fashion, without manual data entry. In various embodiments, the network switch <NUM> may include a controller (e.g., a network processor, or a computing system) that identifies various communication layers associated with equipment connected to the network switch <NUM>. For example, a controller (as part of the network switch <NUM>) may identify the physical layer network port <NUM> and associate with it a data link layer identifier, such as a media access control (MAC) identifier, of the piece of equipment plugged in to the particular network port <NUM>. Further, the controller may associate a network layer identifier, such as an Internet Protocol (IP) address, with the particular network port <NUM>. In some embodiments, the controller may communicate an identifier of the network port <NUM> to a higher level network management or data center management system, and the higher level system may form the association of each of various network ports <NUM> to data link, network layer, or other identifiers of the equipment connected to the various network ports <NUM>. In some embodiments, the controller of the network switch <NUM> may perform the network switching function of the network switch <NUM>, e.g., switching and/or routing of protocol datagram units (e.g., cells, frames, packets, etc.) affiliated with any of various network types. In other embodiments, the controller may be separate from the core network switching function.

A further advantage, in some embodiments, includes associating equipment installed in the rack with a particular one of multiple power outlets. For example, while the network switch <NUM> provides a direct association between a network port <NUM> and a rack space <NUM>, a power distribution unit (PDU) may provide a direct association between a power outlet (or connection) and a space <NUM> in the rack <NUM>. Accordingly, a piece of equipment installed in any space <NUM> is network discoverable by, e.g., the network switch <NUM> identifying the equipment from its network traffic, associating the equipment identifier with the network port <NUM> to which it is connected (e.g., the network port <NUM> on which its network traffic is received), associating the equipment to the rack space <NUM> served by the network port <NUM>, and associating the equipment to a power outlet that serves the rack space <NUM> (or is affiliated with the particular network port <NUM>).

The network switch <NUM> may also include uplink ports <NUM> to provide network connectivity to a higher level, e.g., a router or other equipment serving a communication network beyond the rack <NUM>. For example, equipment in the rack <NUM> may communicate with each other or with equipment outside of the rack <NUM>. When a piece of equipment in the rack <NUM> transmits a datagram (frame, packet) through a network interface, the network switch <NUM> receives the datagram at the associated network port <NUM> and switches (or routes, in some embodiments) the datagram from the associated network port <NUM> to one of another network port <NUM> or to one of the uplink ports <NUM>, whichever is appropriate for the destination of the datagram. Switching and routing of network frames and packets is known in the art, and is accordingly not described in further detail herein.

In certain embodiments, the network ports <NUM> may physically conform to a registered jack (RJ) convention, such as an RJ-<NUM> connector having <NUM> conductor positions, as known in the art, and may support various Ethernet or IEEE <NUM>. x or similar protocols. In various embodiments, the network ports <NUM> may be any suitable physical structure to support, e.g., copper or fiber connections, and may support any suitable communications protocol to accommodate various applications.

Various embodiments may include two uplink ports <NUM> as shown in <FIG>, or may include more or fewer uplink ports, or no uplink port. In various embodiments, uplink ports <NUM> may be of higher bit rate than network ports <NUM>. In various embodiments, uplink ports <NUM> may support copper or fiber connections, such as via an RJ-<NUM> electrical connector or a small form-factor pluggable (SFP) optical connector, and may support any of various communications protocols to accommodate various installations and applications.

<FIG> illustrates another example of a network switch <NUM>, similar to the network switch <NUM> of <FIG>, in accord with at least one embodiment, and including a number of network ports <NUM>, and optionally including one or more uplink ports <NUM>. The network switch <NUM> is coupled with a power distribution unit <NUM> that includes a number of power outlets <NUM>. Each of the network switch <NUM> and the power distribution unit <NUM> is physically configured to be mounted vertically, along the vertical length of the rack <NUM>, and substantially, though not necessarily, the full height of the rack <NUM>. Each of the network ports <NUM> is associated with a space <NUM> in the rack, similar to the example network switch <NUM> of <FIG>. Additionally, each of the power outlets <NUM> may be associated with a space <NUM> in the rack <NUM>. Alternately or additionally, each of the power outlets <NUM> may be associated with one or more of the network ports <NUM>. As shown, two network ports <NUM> are associated with each power outlet <NUM>. In alternate embodiments, there may be a one-to-one association between network ports and power outlets, whereby each power outlet is associated with only one network port and each network port is associated with only one power outlet. In various embodiments, multiple power outlets may be associated with a given network port, multiple network ports may be associated with a given power outlet, or any combination of such associations may be included.

In various embodiments, the network switch <NUM> and the power distribution unit <NUM> are configured such that one or more network ports <NUM> is associated with a space <NUM> in the rack <NUM> and such that one or more power outlets <NUM> is associated with a space <NUM> in the rack <NUM>. Accordingly, if a piece of equipment installed in the rack <NUM> is coupled to a particular network port 212a (e.g., via a network cable), the piece of equipment may also be connected to power from a particular associated power outlet 222a, for example. For any given piece of equipment, multiple network ports <NUM> and/or multiple power outlets <NUM> may provide for a redundancy scheme, without detracting from the general concept that the piece of equipment is connected to at least one network port and at least one power outlet that are associated with each other, e.g., via the coupling of the network switch <NUM> and the power distribution unit <NUM>, or are associated with a particular physical space <NUM> in the rack <NUM>.

In some embodiments, the power distribution unit <NUM> may be a simple device, such as a power strip. In various embodiments, however, the power distribution unit <NUM> may be a "smart" device, having any of various power distribution and/or reliable power capabilities. For example, the power distribution unit <NUM> may be controllable to turn power on or off to individual power outlets <NUM>. The power distribution unit <NUM> may be capable of detecting and/or measuring (e.g., metering) power consumption through a particular power outlet <NUM>. The power distribution unit <NUM> may be capable of detecting and/or measuring (e.g., metering) total power consumption through the power distribution unit <NUM>, e.g., of the entire rack <NUM>. The power distribution unit <NUM> may include uninterruptible or backup power capabilities. Accordingly, in various embodiments, the power distribution unit <NUM> may be manageable and may have network communications capability. In some embodiments, the power distribution unit <NUM> may communicate with a central management capability via one of the uplink ports <NUM>. Alternately or additionally, the power distribution unit <NUM> may be managed by a process and/or processor associated with the network switch <NUM>.

In various embodiments, the network switch <NUM> may be coupled to the power distribution unit <NUM> in various fashions. For example, each of the network switch <NUM> and the power distribution unit <NUM> may have matching connectors on respective sides, such that the network switch <NUM> and the power distribution unit <NUM> may be physically mated together to form a unit. Such matching connectors may provide mechanical, electrical, or communications linkages, or any combination of these, as appropriate for various applications. In some embodiments, the network switch <NUM> and the power distribution unit <NUM> may be coupled together by a tethering cable. In some embodiments, the network switch <NUM> and the power distribution unit <NUM> may be configured to fit into a common space of the rack <NUM>, such as a rear space or channel.

In some embodiments, the network switch <NUM> and the power distribution unit <NUM> may operate together physically, in that they are physically installed on the same rack <NUM> and serve common spaces <NUM>, but they may not be physically coupled to each other. For example, a logical coupling of the network switch <NUM> and the power distribution unit <NUM>, e.g., to associate network ports and power outlets with a particular piece of equipment, may be accomplished in part by a remote device, such as a data center management system. For instance, the network switch <NUM> may detect network activity on a given network port and may identify the equipment connected to the network port (as described above) and may provide such information to a data center management system. The data center management system may, with knowledge of which network port the equipment is attached, may determine in which rack space the equipment is installed (by association of the network port with a rack space). The data center management system may then also determine one or more power outlets that may be providing power to the equipment (by association of the power outlet(s) with the rack space).

In various embodiments, the network switch <NUM> and the power distribution unit <NUM> may be more tightly coupled in a logical sense. For example, the network switch <NUM> and the power distribution unit <NUM> may be configured, by suitable processing componentry, to make the same determinations as discussed above with respect to a data center management system. The determined associations of equipment identification, network port identification, rack space, power outlet, or any combination of these, may then be stored in a database or communicated to a data center management system, for example.

In the above description, identification of a rack space is described as an intermediate to associating a piece of equipment to one or more power outlets. In some embodiments, however, identification of a particular rack space may not be necessary, in that one or more power outlets may be associated with one or more network ports, without regard to which particular rack space is served by them.

<FIG> illustrates another example network switch <NUM> in accord with aspects and embodiments described herein. The network switch <NUM> includes integrated power distribution capability. Accordingly, the network switch <NUM> is similar to a combination of the network switch <NUM> and the power distribution unit <NUM> of <FIG> within a single chassis. The network switch <NUM> includes a number of network ports <NUM>, a number of power outlets <NUM>, and an uplink port <NUM>. In various embodiments, and as described above, a network switch may include more or fewer uplink ports, power outlets, or network ports. Similar to the network switches <NUM>, <NUM>, the network switch <NUM> is physically configured to be mounted vertically, along the vertical length of the rack <NUM>, and substantially, though not necessarily, the full height of the rack <NUM>. The network switch <NUM> does not require any of the spaces <NUM> for its physical accommodation, and may be mountable on a rear portion of the rack <NUM>, such as a rear vertical channel of the rack <NUM>. Similar to the network switches <NUM>, <NUM>, each of the network ports <NUM> is associated with a space <NUM> in the rack <NUM>. Similar to the power distribution unit <NUM>, each of the power outlets <NUM> is also associated with a space <NUM> in the rack <NUM>. In some embodiments, network ports <NUM> and power outlets <NUM> may be logically associated into groups <NUM>, the elements of which associated with each other, and each group <NUM> may be associated with a space <NUM> in the rack <NUM>. As described above, there may be one-to-one associations of network ports, power outlets, and spaces <NUM>, or there may be many-to-one or many-to-many associations.

Similar to the network switches <NUM>, <NUM> and the power distribution unit <NUM> described above, the network switch <NUM> may detect network activity on a particular network port <NUM>, thereby identify a piece of equipment connected to the particular network port <NUM>, and associate the piece of equipment with one or more particular power outlets <NUM>. Accordingly, the network switch <NUM> may collect information as to which pieces of equipment are powered by which power outlets, and may provide such information to other equipment, such as a data center management system. Further in some embodiments, the network switch <NUM> may also associate the piece of equipment with the particular space <NUM> in the rack <NUM> that is served by the particular network port <NUM> and/or the particular power outlet <NUM>. Accordingly, the network switch <NUM> may collect information as to which pieces of equipment are installed in which racks <NUM> and rack spaces <NUM>, and may provide such information to other equipment, such as a data center management system.

Accordingly, the network switch <NUM> and/or a data center management system may advantageously use the above described collected information to manage the equipment in a data center, to control network connectivity of the equipment, to provide out-of-band management, such as configuration and software updates, to the equipment, to power-cycle the equipment, to monitor the power consumption of the equipment, and accordingly may thereby be capable of detecting faults in the equipment or predicting failure of the equipment, or determine need for expansion of the equipment capabilities, or consolidating equipment to provide various functions, and all manner of similar or other equipment management capabilities. Collection of the above described information may all be automated, without the need for manual data entry, due to operation of network switches in accord with those described herein.

<FIG> illustrates the example network switch <NUM> connected to equipment <NUM> to provide electrical power and network connectivity to the equipment <NUM>. Each piece of the equipment <NUM>, as shown in this example, includes a pair of power connectors <NUM> and a pair of network connectors <NUM>. In other examples, various pieces of equipment may have more or fewer power and/or network connectors. Each power connector <NUM> is plugged into a power outlet <NUM> of the network switch <NUM>, and each network connector <NUM> is plugged into a network port <NUM> of the network switch <NUM>. When properly connected, as shown, each piece of equipment <NUM> is plugged into one or more power outlets <NUM> that is associated with at least one network port <NUM> into which the piece of equipment <NUM> is also plugged. Accordingly, the network connection(s) of each piece of equipment <NUM> is associated with the power connection(s) of the piece of equipment, the association being maintained by the network switch <NUM>, physically and logically, e.g., by physical proximity in the chassis/enclosure of the network switch <NUM> and by logical association within a controller of the network switch <NUM> and/or a data center management system. In some examples, the network ports <NUM> and/or power outlets <NUM> are also physically and logically associated with a rack space in similar fashion.

<FIG> illustrates a block diagram of the example network switch <NUM> or the example network switch <NUM>. Each of the network ports <NUM>, the power outlets <NUM>, and optional uplink port(s) <NUM>, are coupled to a controller <NUM>. The controller <NUM> may provide multiple functions as previously described, including the switching or routing of network datagrams between the network ports <NUM> (and the uplink ports <NUM> in some examples), storing the association of the network ports <NUM> with rack spaces (e.g., with physical location of the network ports <NUM> along the chassis of the network switch <NUM>), storing the association of the network ports <NUM> with power outlets <NUM>, detecting and identifying the equipment connected to the network ports <NUM> (and associated power outlets <NUM>), and monitoring of power delivered to one or more of the power outlets <NUM>, for example. The controller <NUM> may perform additional or fewer functions in various embodiments. In some embodiments, some functions may be performed by the controller <NUM> in combination with a higher level computing environment, such as in combination with a data center management system, for example. In some embodiments, and as discussed above, a network switch in accord with aspects described herein may not include power outlets, such as the network switch <NUM> of <FIG>, or may be associated with power outlets through a further power distribution unit, such as the case for the network switch <NUM> of <FIG>. Various embodiments of each of these examples may include a controller similar to the controller <NUM> of <FIG>.

<FIG> illustrates a further block diagram of the example network switch <NUM> or the example network switch <NUM>. In various embodiments, power distribution capabilities may include individual switching <NUM> of the power outlets <NUM>, individual metering <NUM> of the power outlets <NUM>, group metering <NUM> of the power outlets <NUM>, and/or battery backup <NUM> power provision (with power switching <NUM>). In some embodiments, additional alternate or redundant power sources may be supported. In some embodiments, some of the power outlets <NUM> may be group switched and/or some of the power outlets may be unswitched. Switching, metering, and network functions may all be under the control of one or more controllers (e.g., the controller <NUM>), and such control may be distributed (e.g., a portion of the functions of the controller <NUM> may be performed on a remote computing platform).

Various embodiments may include any, all, or none, of the various power distribution functionalities described above. For example, in at least one embodiment, a network switch may provide network ports that are associated with rack spaces <NUM> but not include associated power outlets. In various cases, uplink ports may or may not be provided. In some embodiments, power outlets may be provided, with an association to rack spaces <NUM>, as discussed above. In some embodiments, the power outlets may include metering (individual, group, or both). In some embodiments, the power outlets may include switching control such that the power outlets may be turned on or off, e.g., by a controller, with any variation or combination of individual and/or group switching control. Some of the power outlets may be provided with uninterruptible or backup power, etc..

Various embodiments provide various integration between networking functionalities and power provision functionalities. For example, identification and association of a piece of equipment with a rack space <NUM> may be provided via identification of network port traffic and/or power consumption at a power outlet, as described previously. In some embodiments, out-of-band management may be provided to include outlet switching to provide the capability to shut down and/or hard reboot a device. In some embodiments, out-of-band management data and/or passive network monitoring data may be compared with power outlet metering for diagnostic and/or equipment identification purposes.

Various embodiments may include control functionality beyond the equipment rack in which the network switch is associated. For example, network activity and/or power consumption within a rack may be increasing or decreasing and/or may be high or low. In some embodiments, a controller (e.g., controller <NUM>) may identify that the computing load imposed across two racks could be handled by a single rack (e.g., by identification that each of the two racks has relatively low network activity and power consumption, for instance) and may communicate out-of-band management messages to migrate processes running on equipment within one rack to the equipment in the other rack, and to shut down the equipment in the first rack once migration is complete. Similarly, the load on a single rack may increase to exceed the capacity of the equipment in the rack, and in some embodiments a controller may detect the increasing load (e.g., via network activity, out-of-band management data, and/or power consumption) and power up the equipment in an additional rack in response thereto. Existing processes in the first rack may be migrated to the newly powered rack and/or new processes may be assigned to the newly powered rack in response to new demands. In some embodiments, a controller may detect malicious activity within the equipment in a rack and may shutdown the equipment or otherwise power off the rack, possibly including emergency hard power shut-off to prevent infection or corruption of data or other equipment.

Some embodiments include an equipment rack provided to function as an individual data center, e.g., a micro data center. For example, embodiments include an equipment rack having network switch and power distribution capabilities as described herein, along with console capabilities (such as keyboard, video, mouse, etc.), integrated appliances, such as servers and/or additional network switches or routers, temperature control (e.g., cooling), security components, backup power provisions (e.g., batteries, converters, etc.), and the like.

<FIG> illustrates a method <NUM> that may be implemented by a network switch in accord with aspects and embodiments described herein. In a data center environment, where various equipment is installed in racks and connected to one or more network ports associated with a rack space, and in some cases connected to one or more power outlets associated with a rack space, the method <NUM> includes detecting network activity on one of the network ports (block <NUM>), identifying the connected device (e.g., the piece of equipment) and associating it with the network port (block <NUM>). Identification of the connected device may include any of various identification techniques and/or identifiers. In some examples, a MAC address may be a suitable identifier. Various embodiments may further identify the connected device by network layer addresses. For example, either of a MAC address or a network layer address is discoverable by interpreting datagrams transmitted by the connected device. In some embodiments, a query may be made to acquire a different identifier, such as a serial number requested from the connected device, for example, or a database lookup that identifies a make, model, revision, or similar identification and/or combination of identification information.

In some embodiments, the method <NUM> also may associate the connected device with one or more power outlets (block <NUM>), for example via an affiliation between the network port and various power outlet(s), as described previously. In some embodiments, the method <NUM> may associate the connected device with one or more rack spaces (block <NUM>), for example via an affiliation between the network port and various rack space(s), as described previously. In some instances, association of the connected device with one or more power outlets (block <NUM>) may be achieved via a first association with a rack space (block <NUM>) and via an affiliation between the rack space and various power outlet(s). In some embodiments, a data center management system working in combination with a network switch may perform the method <NUM>, or a similar method.

In some embodiments, a localized management console may be provided that works in combination with, or is enabled by, the network switch. In various embodiments, additional actions may be taken, actions may be omitted, or the actions of the example method <NUM> may be taken in varying order. Various embodiments of network switches (in some cases alongside and/or integrated with power distribution units) provide network ports configured to serve specific rack spaces, and may provide power outlets configured to serve specific rack spaces. Accordingly, a method such as the method <NUM> is enabled because an identification of a device in the rack (discovered from the device's network traffic) may therefore be associated with certain network ports, certain rack spaces, and/or certain power outlets, in an automated fashion within human interaction or manual data entry.

Various embodiments may provide further enhanced performance and/or advantageous operation. In one example, a console manager and/or data center management system, with the benefit of a network switch and power distribution unit as described herein, may identify an installed piece of equipment by model number and may retrieve information about the equipment's expected power consumption, and confirm that the associated power outlet is providing approximately the expected amount of power. Such confirmation may be used to further confirm that the correct power outlet has been associated with the equipment, or that the equipment is plugged in to the correct power outlet. Further, a console manager and/or data center management system may identify all the equipment in the rack and determine the power consumption needs of the entire rack, determine whether the power needs exceed a limit, manage which pieces of equipment are allowed to operate (in some instances), and various other management operations. As a further example, a piece of equipment may stop responding to network traffic, and a console manager and/or data center management system may detect the ceased operation and, with knowledge of the power outlet from which power is provided to the particular piece of equipment, may power cycle the piece of equipment to force it to reboot. In some examples, the console manager and/or data center management system may attempt communication with the piece of equipment on a different network port, or attempt other out-of-band management of the device, prior to or instead of forcing a power cycle and reboot.

In some embodiments, a network switch in accord with aspects and embodiments herein, optionally alongside and/or integrated with a power distribution unit, may include, or may provide service to, a user interface such as may include a display, a keyboard, a mouse, etc., for example, and which may be in the form of remote desktop and/or virtual desktop interfaces. For example, in some embodiments, a network switch in accord with those herein may include keyboard, video, and mouse (KVM) switching capabilities to support a KVM console with access to any or all pieces of equipment in the rack. In some embodiments, KVM connections may be provided to the equipment from the network switch, and access to the KVM connections may be provided to a user through a remote or virtual desktop, e.g., via network communications or other means.

In various embodiments, a network switch in accord with aspects and embodiments herein, optionally alongside and/or integrated with a power distribution unit, as described, may be provided with redundancy. For example, two network switches may be provided for a single rack. In another example, a network switch may provide two or more independent network ports associated with the same rack space, to provide redundancy. Similarly, two or more power distribution units may be included and/or a power distribution unit may provide two or more independent power outlets associated with a given rack space.

<FIG> illustrates an example block diagram of computing components forming a computing system <NUM> which may be configured to implement one or more aspects disclosed herein. For example, a controller of any of the network switches and/or power distribution units (e.g., the controller <NUM>) in accord with the aspects and examples described herein, or similar, may include a computing system <NUM>, and may provide a management interface to an operator, or communication capability to other devices, for example.

The computing system <NUM> may include for example a computing platform such as those based on general computing processors, specialized processors, or microcontrollers. Computing system <NUM> may include specially-programmed, special-purpose hardware, for example, a network processor, an application-specific integrated circuit (ASIC), or more generally designed hardware, such as a field programmable gate array (FPGA) or a general purpose processor. Additionally, various aspects of the present disclosure may be implemented as specialized software executing on a computing system <NUM> such as that shown in <FIG>.

The computing system <NUM> may include a processor/ASIC <NUM> connected to one or more memory devices <NUM>, such as a disk drive, memory, flash memory, embedded or on-chip memory, or other device for storing data. Memory <NUM> may be used for storing programs and data during operation of the computing system <NUM>. Components of the computing system <NUM> may be coupled by an interconnection mechanism <NUM>, which may include one or more buses and/or a network. The interconnection mechanism <NUM> enables communications of, e.g., data and instructions, to be exchanged between components of the computing system <NUM>. The computing system <NUM> may also include one or more input devices <NUM>, which may include, for example, a keyboard, a mouse, a touch screen, and the like. The computing system <NUM> may also include one or more output devices <NUM>, which may include, for example, a display, a buzzer, alarm, or other audio indicator, a light, or other visual indicator, and the like. In addition, the computing system <NUM> may contain one or more interfaces (not shown) that may connect the computing system <NUM> to a communication network, in addition to or as an alternative to the interconnection mechanism <NUM>.

The computing system <NUM> may include a storage component <NUM>, which may include a computer readable and/or writeable nonvolatile medium in which signals may be stored to provide a program to be executed by the processor/ASIC <NUM> or to provide information stored on or in the medium to be processed by the program. The medium may, for example, be a disk or flash memory or other non-volatile memory including programmable read-only memory (PROM) of various types, and in some examples may include random access memory (RAM). In some embodiments, the processor may cause data to be read from the nonvolatile medium into another memory <NUM> that allows for faster access to the information by the processor/ASIC <NUM> than does the medium. This memory <NUM> may be a volatile, random access memory such as a dynamic random access memory (DRAM) or static memory (SRAM). It may be located in storage component <NUM> or in memory <NUM>. The processor/ASIC <NUM> may manipulate the data within the memory <NUM> and copy the data to the storage <NUM> after processing is completed. Either or both of the memory <NUM> and storage <NUM> may be integrated in the processor/ASIC <NUM>.

The computing system <NUM> may include a computer platform that is programmable using a high-level computer programming language. The computing system <NUM> may also be implemented using specially programmed or special purpose hardware, e.g. an ASIC. The processor/ASIC <NUM> may execute a core low-level operating system and may also execute a high-level operating system.

In certain embodiments, a network switch and/or a power distribution unit may have a controller in accord with aspects and embodiments disclosed herein and the controller may include a processor, which may be any of the above or other suitable processors, including ASICs, and may run an instruction set or operate upon other logic, to implement control of the UPS components as discussed above.

Claim 1:
A communication network switch (<NUM>, <NUM>) comprising:
a plurality of network ports (<NUM>, <NUM>, <NUM>);
a plurality of power connections, each of the plurality of power connections logically associated with at least one of the plurality of network ports; and
a controller (<NUM>) coupled to the plurality of network ports and configured to provide communications between the plurality of network ports;
wherein the controller is further configured to identify a piece of equipment connected to at least one of the plurality of network ports based upon network traffic on the at least one of the plurality of network ports;
wherein the controller is further configured to identify at least one of the plurality of power connections as providing power to the piece of equipment based upon the logical association of each of the plurality of power connections with the at least one of the plurality of network ports;
wherein the plurality of network ports is distributed along a chassis of the communication network switch such that each of the network ports is physically associated with at least one of a plurality of mounting spaces within an equipment rack when the chassis is installed to the equipment rack, wherein the chassis is physically configured to align along the height of an equipment rack; and
characterised in that
the controller is further configured to identify at least one of the plurality of mounting spaces as being associated with the piece of equipment based upon the association of the at least one of the plurality of mounting spaces with the at least one of the plurality of network ports.