The present invention relates generally to computer networks, and more particularly but not exclusively to network switches.
A computer may have a communication port that may be linked to a communication port of another computer. For example, a server computer may have a communication port in the form of a network interface card (NIC) port. The server computer may send and receive network traffic by way of its communication port.
A server computer may also have a service processor, such as a baseboard management controller (BMC). Generally speaking, a BMC is a special-purpose processor that monitors the physical state of the server computer. The BMC may include sensors for measuring the physical condition of the computer, such as power supply voltage, fan speed, internal chassis temperature, etc. The BMC operates largely independent of the central processing unit (CPU) and operating system (OS) of the server computer. The BMC has a dedicated communication port for communicating with a remote server management computer. The communication port of the BMC is separate from communication ports that are employed by the server computer for general communications with other computers.
In one embodiment, a server management switch discovers and identifies its switch ports that are connected to communication ports of baseband management controllers (BMC's) of server computers. The server management switch isolates the identified BMC-connected switch ports such that network traffic on a BMC-connected switch port is restricted to a switch port that has a connection, either directly by a link or over a server management network, to a server management computer. Network traffic on BMC-connected switch ports are monitored and controlled in various ways to further protect the BMC's from security attacks.
These and other features of the present invention will be readily apparent to persons of ordinary skill in the art upon reading the entirety of this disclosure, which includes the accompanying drawings and claims.
The use of the same reference label in different drawings indicates the same or like components.
In the present disclosure, numerous specific details are provided, such as examples of systems, components, and methods, to provide a thorough understanding of embodiments of the invention. Persons of ordinary skill in the art will recognize, however, that the invention can be practiced without one or more of the specific details. In other instances, well-known details are not shown or described to avoid obscuring aspects of the invention.
A server computer 150 may comprise a conventional server computer, such as those available from Super Micro Computer, Inc. of San Jose, Calif. For example, the server computers 150 may comprise rack mount servers or blade servers. A server computer 150 may have a communication port, such as a NIC port, for communicating with other server computers 150. More particularly, the communication ports of the server computers 150 may be connected to switch ports of one or more network switches 160. Network traffic (i.e., data being communicated) from an originating server computer 150 to a receiving server computer 150 may be forwarded by a network switch 160. A network switch 160 may be a conventional network switch, such as those available from Super Micro Computer, Inc., Cisco Systems, Inc., and other network device vendors. Generally speaking, a network switch is a dedicated network device for receiving and forwarding data packets by packet switching. A network switch may receive network traffic from an originating computer on a switch port, and route/forward the network traffic to a destination computer on another switch port.
In the example of
A server management computer 170 may be configured to perform server management functions for the server computers 150. The server management computer 170 may be a conventional computer that is running a commercially-available system management software (SMS) for managing server computers. A difference between the server management computer 170 and other computers is that the server management computer 170 communicates with one or more BMC's intermittently or periodically to manage the corresponding server computers 150.
The server management computer 170 may be connected to the server management switch 110 directly by a link or indirectly over a server management network 180. The server management network 180 may be configured to carry all server management network traffic in the network 100, i.e., network traffic between the server management computer 170 and BMC's of server computers 150. The server management network 180 may include other switches and network devices (not shown) that provide network connection between the server management switch 110 and the server management computer 170.
In the example of
In the example of
A link is a physical connection that directly connects a switch port of a network switch to a communication port of a computer. A link may comprise an Ethernet cable, a backplane connection, or other wired connection. In the example of
In one embodiment, the server management switch 110 is configured to perform switching or routing not just for BMC's, but for general data communication ports as well. This is reflected in
In the example of
A switch port 227 of the server management switch 110 has a connection directly or indirectly to the server management computer 170. For example, a link may directly connect the switch port 227 to a communication port 230 (e.g., NIC port) of the server management computer 170. In the example of
In one embodiment, switch ports that are connected to BMC communication ports are isolated from switch ports that have no connection to the server management computer 170. That is, network traffic on a BMC-connected switch port is restricted to a particular switch port, such as only to and from a switch port that has a connection to the server management computer 170. Any other switching or routing to or from the BMC-connected switch port will be blocked by the server management switch 110. More particularly, the server management switch 110 blocks switching or routing of network traffic between a switch port connected to a BMC communication port and another switch port that is not connected to the server management computer 170. A network administrator may manually indicate, e.g., using a menu or other user interface, that the switch port 227 is connected to the server management computer 170 as part of a user-configured setting of the server management switch 110.
In the example of
In the example of
The BMC security module 301 may comprise instructions that, when executed by the CPU 251, cause the server management switch 110 to discover and identify BMC-connected switch ports, isolate the BMC-connected switch ports, and monitor and control network traffic on each BMC-connected switch port.
In the example of
The server management switch 110 isolates each of its BMC-connected switch ports (step 402). More specifically, the server management switch 110 may automatically perform a port isolation procedure for each identified BMC-connected switch port. The port isolation procedure restricts network traffic such that network traffic to and from a BMC-connected switch port can only originate from or be destined to a switch port that is connected to the server management computer 170. The port isolation may be enforced a variety of ways depending on the particulars of the server management switch 110. In one of embodiment, port isolation is performed by modifying an egress mask table in an application specific integrated circuit (ASIC) of the server management switch 110. The egress mask table indicates whether a particular egress switch port can transmit packets that are received on a particular ingress switch port. By default, all switch ports will have the egress mask bits enabled for all the ingress switch ports. Based on the required port isolation, the egress mask of a switch port (e.g.,
Referring to
Continuing the method 400 of
The server management switch 110 may automatically rate limit all network traffic on BMC-connected switch ports (step 411). This protects a BMC 153 from excessive network traffic and other security attacks that may overwhelm the capacity of the BMC 153 to respond. In one embodiment, the server management switch 110 has preconfigured default permissible rates for each type of allowed network traffic. The server management switch 110 may also allow user configurations to override these permissible rates. The server management switch 110 may be configured to identify a BMC-connected switch port that tries to send or receive network traffic exceeding the permissible rate by an abnormal margin. The server management switch 110 may, as part of its alert mechanism, report such identified BMC-connected switch ports to the server management computer 170 or to any other device that is configured to be alerted in the event of a detected network anomaly.
As is well-known, Transport Control Protocol (TCP) and User Datagram Protocol (UDP) are in so-called transport layer of network traffic. A BMC 153 may use various TCP or UDP ports to communicate with the server management computer 170 for different types of network traffic. The server management switch 110 may be configured to monitor all of the open TCP/UDP ports in BMC's 153 (step 412). The server management switch 110 may detect any unexpected TCP/UDP port opened in the BMC's 153 and raise a corresponding alert in response thereto. The alert may include sending a warning or report to the server management computer 170 or to any other device that is configured to receive such alerts. The server management switch 110 may also be configured to raise an alert in response to detecting any abnormal closure of TCP/UDP ports that are expected to be open. TCP/UDP ports that are expected to be open and/or authorized may be user-configurable and indicated in a table for reference.
The server management switch 110 may be configured to block all network traffic on a BMC-connected switch port that goes to unauthorized TCP/UDP ports of BMC's 153 (step 413). This protects a BMC 153 from security attacks originating from the Internet, and prevents any compromised BMC 153 from sending out abnormal traffic by opening unknown TCP/UDP ports. The server management switch 110 may also be configured to block network traffic to particular, predetermined TCP/UDP ports of BMC's 153.
The server management switch 110 may be configured to monitor and record Internet Protocol (IP) addresses of network traffic on BMC-connected switch ports (step 414).
The server management switch 110 may be configured to generate various alerts, such as warnings and reports, as part of the method 400 when any abnormal network behavior is detected from a BMC-connected switch port. The server management switch 110 may send these alerts to the server management computer 170 or to any other device configured to receive them.
Network switches with secured BMC-connected switch ports have been disclosed. While specific embodiments of the present invention have been provided, it is to be understood that these embodiments are for illustration purposes and not limiting. Many additional embodiments will be apparent to persons of ordinary skill in the art reading this disclosure.
This application claims the benefit of U.S. Provisional Application Ser. No. 62/838,463, filed on Apr. 25, 2019, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
8417774 | Flynn | Apr 2013 | B2 |
8732829 | Johnson | May 2014 | B2 |
9191823 | Rieger | Nov 2015 | B2 |
9800547 | Lee | Oct 2017 | B2 |
9807055 | Lee | Oct 2017 | B2 |
9916270 | Richardson | Mar 2018 | B2 |
9998359 | Itkin | Jun 2018 | B2 |
10069718 | Khemani | Sep 2018 | B2 |
10148746 | Itkin | Dec 2018 | B2 |
10911405 | Harland | Feb 2021 | B1 |
20050286430 | Koga | Dec 2005 | A1 |
20140165183 | Dharmadhikari | Jun 2014 | A1 |
20140344431 | Hsu | Nov 2014 | A1 |
20150156212 | Khatri | Jun 2015 | A1 |
20160170923 | Kutch | Jun 2016 | A1 |
20160248697 | Masuyama | Aug 2016 | A1 |
20160308886 | Lee | Oct 2016 | A1 |
20170109531 | Wang | Apr 2017 | A1 |
20170155573 | Khemani | Jun 2017 | A1 |
20170244640 | Lin | Aug 2017 | A1 |
20180183758 | Itkin | Jun 2018 | A1 |
20190004901 | Ryan | Jan 2019 | A1 |
20190273700 | Itkin | Sep 2019 | A1 |
20200278935 | Borikar | Sep 2020 | A1 |
Entry |
---|
Edward Tetz. “Network Basics: TCP/UDP Socket and Port Overview”, Cisco Networking All-In-One for Dummies, publicly posted as of Jun. 13, 2018, 3 pages. (Year: 2018). |
Number | Date | Country | |
---|---|---|---|
20200344269 A1 | Oct 2020 | US |
Number | Date | Country | |
---|---|---|---|
62838463 | Apr 2019 | US |