Differentiating among multiple management control instances using IP addresses

Patent metadata

Field	Value
Publication number	US-9729440-B2
Application number	US-201514628256-A
Country	US
Kind code	B2
Filing date	Feb 22, 2015
Priority date	Feb 22, 2015
Publication date	Aug 8, 2017
Grant date	Aug 8, 2017

Abstract

A network adapter includes one or more ports and circuitry. The one or more ports are configured to connect to a communication network. The circuitry is coupled to a network node that includes multiple hosts, and is configured to exchange management packets between a control server and a Baseboard Management Controller (BMC) that runs at least first and second BMC instances that share a single MAC address and are associated respectively with first and second hosts, and to exchange, over the communication network via the one or more ports, data packets between the hosts and one or more remote nodes.

First claim

The invention claimed is:

1. A network adapter serving a network node that comprises multiple physical hosts, the network adapter comprising:
one or more physical ports, configured to connect the network adapter to a communication network;
one or more physical host interfaces, configured to connect the network adapter to the physical hosts of the network node, and to exchange over the communication network, via the physical ports and the physical host interfaces, data packets between first and second physical hosts and one or more remote nodes;
a physical sideband interface, configured to connect the network adapter to a hardware-implemented Baseboard Management Controller (BMC), which runs at least first and second BMC instances that are assigned a single shared Medium Access Control (MAC) address and are associated respectively with the first and second physical hosts; and
circuitry that comprises one or more packet filters and that is connected to the physical ports and to the physical sideband interface, is configured to:
separate between the data packets and the management packets, using the packet filters, based at least on the single shared MAC address assigned to the first and second BMC instances; and
exchange over the communication network, via the physical ports and the physical sideband interface, the management packets between the BMC and a control server.

2. The network adapter according to claim 1 , wherein the circuitry is configured to exchange the management packets by maintaining respective associations between the first and second BMC instances and the first and second hosts.

3. The network adapter according to claim 2 , wherein the circuitry is configured to maintain the associations by holding a respective different IP address for each of the first and second BMC instances.

4. The network adapter according to claim 3 , wherein the circuitry is configured to exchange the management packets by routing the management packets related to the first or second BMC instance based at least on one of the respective IP address and the single MAC address.

5. The network adapter according to claim 2 , wherein the circuitry is configured to exchange the management packets by routing the management packets to and from the first or second BMC instance based on the associations.

6. The network adapter according to claim 2 , wherein the circuitry is configured to emulate, using the associations, a separate respective NIC for each of the first and second BMC instances.

7. The network adapter according to claim 2 , wherein the physical sideband interface comprises physical sideband interfaces of two or more different types for exchanging the management packets, and wherein the circuitry is configured to select a respective one of the physical sideband interfaces for each of the first and second BMC instances based on the respective associations.

8. The network adapter according to claim 7 , wherein the circuitry is configured to transition from using one of the physical sideband interfaces having a first type by one of the first and second BMC instances to using one of the physical sideband interfaces having a second different type by the same BMC instance.

9. The network adapter according to claim 8 , wherein the circuitry is configured to transition from using one of the physical sideband interfaces of the first type when the one of the physical sideband interfaces having the first type becomes unavailable.

10. The network adapter according to claim 1 , wherein the circuitry is configured to identify a management packet that is destined for multiple BMC instances, to send the identified management packet to the BMC only once when the BMC supports duplication of packets to multiple BMC instances, and to send a respective duplicate of the identified management packet to each of the BMC instances to which the identified packet is destined, otherwise.

11. A method for remote management, comprising:
in a network node that comprises multiple physical hosts, a Baseboard Management Controller (BMC) that runs at least first and second BMC instances that are assigned a single shared Medium Access Control (MAC) address and are associated respectively with first and second physical hosts, and a network adapter that comprises one or more physical ports for connecting to the communication network, one or more physical host interfaces for connecting to the physical hosts, a physical sideband interface for connecting to the BMC, and circuitry that comprises one or more packet filters and that is connected to the physical ports and to the physical sideband interface, exchanging over the communication network, via the physical ports and the physical sideband interface, management packets between a control server and the BMC; and
exchanging over the communication network, via the physical ports and the physical host interfaces, data packets between the hosts and one or more remote nodes,
wherein exchanging the management packets and the data packets comprises separating between the data packets and the management packets, using the packet filters, based at least on the single shared MAC address assigned to the first and second BMC instances.

12. The method according to claim 11 , wherein exchanging the management packets comprises maintaining respective associations between the first and second BMC instances and the first and second hosts.

13. The method according to claim 12 , wherein maintaining the associations comprises holding a respective different IP address for each of the first and second BMC instance.

14. The method according to claim 13 , wherein exchanging the management packets comprises routing the management packets related to the first or second BMC instance based at least on one of the respective IP address and the single MAC address.

15. The method according to claim 12 , wherein exchanging the management packets comprises routing the management packets to and from the first or second BMC instance based on the associations.

16. The method according to claim 12 , and comprising emulating, using the associations, a separate respective NIC for each of the first and second BMC instances.

17. The method according to claim 12 , wherein the physical sideband interface comprises physical sideband interfaces of two or more different types for exchanging the management packets, and wherein exchanging the management packets comprises selecting a respective one of the physical sideband interfaces for each of the first and second BMC instances based on the respective associations.

18. The method according to claim 17 , wherein selecting the respective one of the physical sideband interfaces comprises transitioning from using one of the physical sideband interfaces having a first type by one of the first and second BMC instances to using one of the physical sideband interfaces having a second different type by the same BMC instance.

19. The method according to claim 18 , wherein selecting the one of the physical sideband interfaces comprises transitioning from using the one of the physical sideband interfaces having the first type when the one of the physical interfaces of the first type becomes unavailable.

20. The method according to claim 11 , wherein exchanging the management packets comprises identifying a management packet that is destined for multiple BMC instances, sending the identified management packet to the BMC only once when the BMC supports duplication of packets to multiple BMC instances, and sending a respective duplic

Assignees

• Mellanox Technologies Ltd
• Mellanox Technologies Ltd

Inventors

• Itkin Yuval

Classifications

• H04L43/028

  by filtering · CPC title

• H04L45/74 Primary

  Address processing for routing · CPC title