System and method for enabling interchangeable dedicated management network interface card access via fabric controller

Systems and methods for reducing problems and disadvantages associated with traditional approaches to providing dedicated network interface card access are provided. An information handling system may include a processor, a memory communicatively coupled to the processor, a non-dedicated network interface communicatively coupled to the processor, a dedicated network interface, and a baseboard management controller. The non-dedicated network interface may have a first sideband interface. The dedicated network interface may have a second sideband interface communicatively coupled to the first sideband interface. The baseboard management controller may be communicatively coupled to the second sideband interface.

TECHNICAL FIELD

The present disclosure relates in general to information handling systems, and more particularly to providing interchangeable dedicated management network interface card access via a fabric controller.

BACKGROUND

Traditionally, some information handling systems utilize each of a dedicated network interface card (NIC) and at least one non-dedicated NIC. A dedicated NIC is often used as an interface between an information handling system, which includes the dedicated NIC, and a management network by which an administrator may direct management traffic to a baseboard management controller or similar system via an “out-of-band” communications channel that is isolated from the “in-band” communications channel for which network traffic other than management traffic may be communicated (e.g., via the non-dedicated NIC). However, because isolation of management traffice from non-management traffic often requires additional cabling and network router ports, administrators may often shooce to operate information handling systems in a “shared NIC mode” by which the non-dedicated NIC may communicate both management and non-management traffic.

However, regardless of whether a dedicated NIC mode or shared NIC mode is selected by an administrator, traditional approaches for supporting both have disadvantages. For example, a baseboard management controller (BMC) in a traditional information handling system supporting both modes may require two media access controllers (MACs), as dedicated NICs and non-dedicated NICs may utilize different standards or protocols to communicate with the BMC (e.g., the dedicated NIC may utilize Reduced Media Independent Interface (RMII) to communicate with the BMC and the non-dedicated NIC may utilize Network Controller Sideband Interface (NC-SI) to communicate with the BMC, each of which cannot be electrically or logically shared). Also, using traditional approaches, a Management Data Input-Output/Management Data Clock (MDIO/MDC) bus is also required between the dedicated NIC and the BMC. Moreover, the dedicated NIC may include a PHY that may consume power regardless of whether dedicated NIC mode or shared NIC mode is selected.

SUMMARY

In accordance with the teachings of the present disclosure, the disadvantages and problems associated with providing dedicated NIC access have been reduced or eliminated.

In accordance with an embodiment of the present disclosure, an information handling system may include a processor, a memory communicatively coupled to the processor, a non-dedicated network interface communicatively coupled to the processor, a dedicated network interface, and a baseboard management controller. The non-dedicated network interface may have a first sideband interface. The dedicated network interface may have a second sideband interface communicatively coupled to the first sideband interface. The baseboard management controller may be communicatively coupled to the second sideband interface.

In accordance with another embodiment of the present disclosure, a network interface device may include a sideband interface configured to communicatively couple to a baseboard management controller, a PHY configured to communicatively couple to a network, and a media access control filter interfaced between the PHY and the second sideband interface. The media access device may be configured to filter communications such that management data received by the media access control filter is forwarded while non-management data received by the media access control filter is not forwarded.

Other technical advantages will be apparent to those of ordinary skill in the art in view of the following specification, claims, and drawings.

DETAILED DESCRIPTION

Preferred embodiments and their advantages are best understood by reference toFIGS. 1 and 2, wherein like numbers are used to indicate like and corresponding parts.

FIG. 1illustrates a block diagram of an example system100for providing dedicated NIC access, in accordance with certain embodiments of the present disclosure. As depicted inFIG. 1, system100may include an information handling system102, a management network108, and a non-management network110. Management network108and non-management network may each individually be referred to as “network108” or “network110,” and may collectively be referred to as “networks108,110.”

Information handling system102may generally be operable to receive data from and/or communicate data to one or more other information handling systems via one or both of networks108,110. In certain embodiments, information handling system102may be a server. In another embodiment, information handling system102may be a personal computer (e.g., a desktop computer or a portable computer). As depicted inFIG. 1, information handling system102may include a processor103, a memory104communicatively coupled to processor103, a non-dedicated network interface card (NIC)107communicatively coupled to processor103, a dedicated NIC106communicatively coupled to non-dedicated NIC107, a baseboard management controller (BMC)120communicatively coupled to each of dedicated NIC106and non-dedicated NIC107, a socket124communicatively coupled to dedicated NIC106, and a socket126communicatively coupled to non-dedicated NIC107.

Memory104may be communicatively coupled to processor103and 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). Memory104may include random access memory (RAM), electrically erasable programmable read-only memory (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 information handling system102is turned off.

Dedicated NIC106may include any suitable system, apparatus, or device operable to serve as an interface between information handling system102and management network108. Dedicated NIC106may enable information handling system102to communicate over management network108using any suitable transmission protocol and/or standard, including without limitation all transmission protocols and/or standards enumerated below with respect to the discussion of management network108. In certain embodiments, dedicated NIC106may include or be an integral part of an access controller that may permit an administrator or other person to remotely monitor and/or remotely manage information handling system102(e.g., via an information handling system remotely connected to information handling system102via management network108) regardless of whether information handling system102is powered on and/or has an operating system installed thereon. Accordingly, such access controller may allow for “out-of-band” control of information handling system102, such that communications to and from dedicated NIC106are communicated via a management channel physically isolated from the “in-band” communication between non-management network110and non-dedicated NIC107. In these embodiments (i.e., embodiments where dedicated NIC106may include or be an integral part of an access controller), dedicated NIC106may include or may be an integral part of a Dell Remote Access Controller (DRAC) or an Integrated Dell Remote Access Controller (iDRAC). In addition, in such embodiments, such access controller may allow an administrator to remotely manage one or more parameters associated with operation of information handling system102(e.g., power usage, processor allocation, memory allocation, security privileges, etc.).

In certain embodiments, dedicated NIC106may be removable and/or interchangeable with one or more dedicated NICs106that may or may not be similar to dedicated NIC106depicted inFIG. 1. As an example, a particular dedicated NIC106may be adapted for communication in accordance with the Gigabit Ethernet (GigE) standard, and may be removable interchangeable with one or more other removable and/or interchangeable dedicated NICs106that may be adapted for communication in accordance with other communications standards, such as 10 Gigabit Ethernet (10 GigE) or FibreChannel (FC) standards, for example.

As shown inFIG. 1, dedicated NIC106may include a PHY112, a MAC filter114communicatively coupled to PHY112, and a Network Controller Sideband Interface (NC-SI) device116communicatively coupled to MAC filter114. PHY112may include any system, device, or apparatus configured to communicatively couple a link layer device (e.g., a media access controller or a MAC filter) to a physical medium (e.g., an optical fiber or copper cable coupled to socket124).

MAC filter114may include any system, device, or apparatus configured to filter communications such that management data is further communicated while non-management data is not further communicated. For example, MAC filter114may filter data received from PHY112such that management data is further communicated to NC-SI device116, while non-management data is not further communicated to NC-SI device116. As another example, MAC filter114may filter data received from NC-SI device116such that management data is further communicated to PHY112, while non-management data is not further communicated to PHY112. MAC filter114may utilize any suitable filtering technique, including without limitation layer2address filtering.

NC-SI device116may include any system, device, or apparatus configured to communicatively couple dedicated NIC106to BMC120in accordance with the NC-SI Specification.

Non-dedicated NIC107may include any suitable system, apparatus, or device operable to serve as an interface between information handling system102and non-management network110. Non-dedicated NIC107may enable information handling system102to communicate over non-management network110using any suitable transmission protocol and/or standard, including without limitation all transmission protocols and/or standards enumerated below with respect to the discussion of non-management network110. In certain embodiments, non-dedicated NIC107may include or be an integral part of a LAN on motherboard (LOM), wherein network interface hardware of non-dedicated NIC107is an integral part of a motherboard of information handling system102. In other embodiments, non-dedicated NIC107may include or be an integral part of a host bus adapter (HBA). Although a LOM and an HBA have been identified as examples of non-dedicated NIC107, non-dedicated NIC107is not limited to those examples, and may include any suitable device, system, or apparatus. In certain embodiments, non-dedicated NIC107may be configurable to allow operation in either of a “shared” mode or “unshared” mode. In the shared mode, both management communications and non-management communications for information handling system102may be communicated to and from non-dedicated NIC107. In the unshared mode, non-management communications for information handling system102may be communicated to and from non-dedicated NIC107while management communications are communicated to and from dedicated NIC106in an “out-of-band” channel isolated from the “in-band” channel used for non-management communications.

BMC120may be any suitable system, device or apparatus configured to manage the interface between system management software and platform hardware using any suitable protocol and/or standard, including, without limitation, the Intelligent Platform Management Interface (IPMI) architecture. BMC120may interface with different types of sensors built into information handling system102or its components and may report to BMC120regarding parameters such as temperature, cooling fan speeds, power mode, operating system (OS) status, etc. Accordingly, BMC120may monitor the sensors and may communicate alerts to a system administrator via management network108(in dedicated NIC mode) or via network110(in shared NIC mode) or other means if any of the parameters associated with the sensors vary from preset limits or thresholds, indicating a potential failure of information handling system102or one or more of its various components. The administrator may also remotely communicate with BMC120to take corrective action such as, for example, resetting or power cycling information handling system102or one or more of its components (e.g., to cause a stalled operating system to run again).

As depicted inFIG. 1, BMC120may include media access controller (MAC)122. MAC122may be any suitable device, system or apparatus configured to provide addressing and/or channel access control mechanisms to allow BMC120to communicate with management network108, non-management network110, or other multipoint network.

Socket124may be any suitable modular connector for coupling management network108to dedicated NIC106(e.g., an 8P8C or RJ45 socket). Similarly, socket126may be any suitable modular connector for coupling non-management network110to non-dedicated NIC107(e.g., an 8P8C or RJ45 socket).

Each of networks108,110may be a network and/or fabric configured to communicatively couple information handling system102, other information handling systems, and/or other networked components to each other. Each of networks108,110may include a communication infrastructure, which provides physical connections, and a management layer, which organizes the physical connections and information handling system102. In the same or alternative embodiments, each of networks108,110may allow block I/O services and/or file access services to network-attached computer-readable media.

Each of networks108,110may be implemented as, or may be a part of, a storage area network (SAN), personal area network (PAN), local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a wireless local area network (WLAN), a virtual private network (VPN), an intranet, the Internet or any other appropriate architecture or system that facilitates the communication of signals, data and/or messages (generally referred to as data). Each of management network108,110may transmit data using any storage and/or communication protocol, including without limitation, Fibre Channel, Frame Relay, Asynchronous Transfer Mode (ATM), Internet Protocol (IP), other packet-based protocol, small computer system interface (SCSI), Internet SCSI (iSCSI), Serial Attached SCSI (SAS) or any other transport that operates with the SCSI protocol, advanced technology attachment (ATA), serial ATA (SATA), advanced technology attachment packet interface (ATAPI), serial storage architecture (SSA), integrated drive electronics (IDE), and/or any combination thereof. Each of management network108,110and its various components may be implemented using hardware, software, or any combination thereof. Although depicted as separate networks inFIG. 1, network108and network110may, in certain embodiments, comprise the same network.

In operation, information handling system102may be configured in a dedicated NIC mode or a shared NIC mode. In the dedicated NIC mode, dedicated NIC106may serve as an interface between BMC120and management network108such that out-of-band management communications may be isolated from the in-band non-management communications between non-dedicated NIC107and non-management network110. In a shared NIC mode, non-dedicated NIC107may serve as an interface between BMC120and non-management network110as well as an interface between other components of information handling system102and non-management network110, such that both management and non-management communications are not isolated from and each other and may be communicated to and from non-dedicated NIC107.

FIG. 2illustrates a block diagram of another example system200for providing dedicated NIC access, in accordance with certain embodiments of the present disclosure. As depicted inFIG. 2, system200may include an information handling system202, a management network108, and a non-management network110. Management network108may be identical or similar to management network108ofFIG. 1, and non-management network110may be identical or similar to non-management network110ofFIG. 1.

In addition, information handling system202may be identical or similar to that of information handling system102ofFIG. 1, except that information handling system202may include dedicated NIC206in lieu of dedicated NIC106, and may include an additional socket124.

Similar to dedicated NIC106, dedicated NIC206may include any suitable system, apparatus, or device operable to serve as an interface between information handling system202and management network108. Dedicated NIC206may enable information handling system202to communicate over management network108using any suitable transmission protocol and/or standard, including without limitation all transmission protocols and/or standards enumerated above with respect to the discussion of management network108. In certain embodiments, dedicated NIC206may include or be an integral part of an access controller that may permit an administrator or other person to remotely monitor and/or remotely manage information handling system202(e.g., via an information handling system remotely connected to information handling system202via management network108) regardless of whether information handling system202is powered on and/or has an operating system installed thereon. Accordingly, such access controller may allow for “out-of-band” control of information handling system202, such that communications to and from dedicated NIC206are communicated via a management channel physically isolated from the “in-band” communication between non-management network110and non-dedicated NIC107. In these embodiments (i.e., embodiments where dedicated NIC206may include or be an integral part of an access controller), dedicated NIC206may include or may be an integral part of a Dell Remote Access Controller (DRAC) or an Integrated Dell Remote Access Controller (iDRAC). In addition, in such embodiments, such access controller may allow an administrator to remotely manage one or more parameters associated with operation of information handling system202(e.g., power usage, processor allocation, memory allocation, security privileges, etc.).

In certain embodiments, dedicated NIC206may be removable and/or interchangeable with one or more dedicated NICs206that may or may not be similar to dedicated NIC206depicted inFIG. 2or dedicated NIC106depicted inFIG. 1. As an example, a particular dedicated NIC206may be adapted for communication in accordance with the Gigabit Ethernet (GigE) standard, and may be removable interchangeable with one or more other removable and/or interchangeable dedicated NICs206that may be adapted for communication in accordance with other communications standards, such as 10 Gigabit Ethernet (10 GigE) or FibreChannel (FC) standards, for example.

As shown inFIG. 2, dedicated NIC206may include two or more PHYs112, a MAC filter114communicatively coupled to each PHY112, and an NC-SI device116communicatively coupled to MAC filter114. Each PHY112may be similar or identical to PHY112depicted inFIG. 1. MAC filter114may be similar or identical to MAC filter114depicted inFIG. 1. NC-SI device116may be similar or identical to NC-SI device116depicted inFIG. 1.

Using the methods and systems disclosed herein, problems associated with conventional approaches to providing dedicated NIC access in an information handling system may be improved, reduced, or eliminated. For instance, a dedicated NIC may provide support for management via communications standards that might not otherwise be supported by the particular BMC of the information handling system. As an example, a dedicated NIC using the Gigabit Ethernet standard may be used in an information handling system in which the MAC of the BMC supports a different standard, such as 100 Mbps Ethernet. Accordingly, this particular example would permit full Gigabit Ethernet support within the dedicated NIC without requiring a Gigabit Ethernet MAC in the BMC.

Furthermore, the dedicated NIC's sideband MAC filtering may limit throughput to that supported by the BMC (e.g., 100 Mbps), thus permitting use of existing BMCs with a communication standard different than that of the dedicated NIC. MAC filtering may also include programmable broadcast storm suppression which may reduce the likelihood of storms overpowering the BMC, as compared to traditional approaches.

Additionally, the systems and methods described herein permit operability with a BMC having only one MAC with multi-drop connectivity, thus permitting the use of BMCs with lower hardware complexity, and thus, lower cost.

Moreover, techniques such as “Wake-on-LAN” may be supportable through the dedicated NIC, allowing a packet (e.g., a “magic packet”) to be used on the management network to wake the BMC from a lower power or auxiliary state to full operation and/or easily wake the information handling system without requirement commands supported by IPMI or similar standards.

In addition, no MDIO/MDC bus may be required for configuration as NC-SI or similar sideband standards may not require such a bus, thus reducing hardware complexity.

Further, the use of multiple-port dedicated NIC (e.g., dedicate NIC206) may increase availability over traditional approaches as it may allow failover and teaming on dedicated management network connections. The systems and methods described herein also allow an administrator to bind dedicated and non-dedicated NICS together for both link failover and traffic teaming support. Accordingly, management port stacking synonymous with that used in chassis management controllers may be enabled.

Also, the methods and systems described herein allow for the use of interchangeable management networks or fabrics, as dedicated NICs (e.g., dedicated NIC106and/or dedicated NIC206) may be removable and/or interchangeable. Consequently, numerous usage models are enabled (e.g., a FibeeChannel management domain, iSCSI access to storage area networks) including the use of combinations of controllers.

Although the present disclosure has been described in detail, it should be understood that various changes, substitutions, and alterations can be made hereto without departing from the spirit and the scope of the disclosure as defined by the appended claims.