Bidirectional Proxy Event Subscription for BMC Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a multi-host cluster environment, the exclusion of a baseboard management controller's (BMC) dedicated out-of-band (OOB) interface from the management domain prevents direct communication between the BMC and the cluster management resource, necessitating hundreds or thousands of persistent connections for event notification messaging, which is inefficient.
Innovation Solution
Provisioning a host with a pair of proxy resources: one to forward traffic from the in-band management interface to the BMC's link-local interface and another to forward traffic from the link-local interface to the cluster manager's management network interface, enabling event subscription and notification messaging without increasing in-band traffic or requiring dedicated persistent connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single proxy is used to forward event notifications from BMC to cluster manager, then device complexity is reduced, but reliable event delivery cannot be guaranteed due to potential proxy failures
Solution Approach 1:
The patent divides the proxy functionality into two separate proxies: a first proxy that forwards traffic from the in-band management interface to the BMC's link-local interface, and a second proxy that forwards traffic from the link-local interface to the cluster manager's management network interface. This segmentation isolates failure domains and ensures that events can still be delivered reliably even if one proxy fails, resolving the contradiction between simplicity and reliability.
2Object-affected harmful factors
If the BMC's dedicated OOB interface is excluded from the management domain, then security is improved, but direct communication between BMC and cluster manager is prevented, requiring hundreds or thousands of persistent connections
Solution Approach 1:
The patent introduces proxy resources as intermediaries that operate within the management domain to forward event notifications between the BMC and cluster manager. These proxies enable indirect communication through the in-band management interface, eliminating the need for the BMC's OOB interface to be included in the management domain while avoiding the need for numerous persistent connections. This resolves the contradiction between security and communication efficiency.
3Reliability
If persistent connections are established for event notification messaging, then reliability of event delivery is improved, but resource utilization increases significantly
Solution Approach 1:
The patent implements a periodic polling mechanism where the cluster manager sends periodic subscription requests to the proxies to check for new events. This periodic action replaces the need for persistent connections, as events are delivered through scheduled polling cycles rather than continuous open connections. This resolves the contradiction between reliable event delivery and resource utilization by maintaining reliability through periodic checks while significantly reducing the resource overhead of maintaining hundreds or thousands of persistent connections.
Data Source
AI summary
Disclosed methods provision a host with a pair of proxy resources. A first proxy resource may be configured to forward traffic from an in-band management interface of the host to a link-local interface of a BMC or the like. The second proxy resource is configured to forward traffic received via a link-local interface of the host to a management network interface of a cluster manager. Upon receiving an event subscription message from the cluster manager via the in-band management interface of the host, the event subscription message is forwarded by the first proxy to the link-local interface of the BMC to register a link-local interface of the host as a subscriber for one or more events. Responsive to receiving an event notification from the BMC via the link-local interface of the host, the event notification is automatically forwarded to the management network interface of the cluster manager.

