IPMI Message Forwarding via Logical Unit Number Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In blade server systems, the existing IPMI message transmission methods, such as the Send Message command, introduce complexity and delay due to the need for bridging requests and responses, especially in synchronizing these operations across multiple service processors (SPs) within a chassis.
Innovation Solution
The proposed system utilizes the logical unit number (LUN) field in IPMI request messages to directly route messages to the proper destination SP, reducing complexity and delay by employing a network switch interconnected with up to four SPs, each with a unique LUN, and utilizing a processor, non-volatile memory, and system interfaces like LAN or USB for message handling and processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the Send Message command is used for IPMI message transmission in blade server systems, then messages can be routed between service processors, but the system introduces complexity in bridging requests and responses and increases processing delay
Solution Approach 1:
The patent extracts the LUN routing function from the complex Send Message command processing. By utilizing the existing LUN field in IPMI message headers, the system directly routes messages to the appropriate destination SP without requiring complex bridging logic. This separates the simple LUN-based routing function from the complex message forwarding operations.
Solution Approach 2:
The patent performs preliminary routing decisions based on the LUN field before messages enter the complex forwarding path. By examining the LUN field in the message header early in the processing chain, the system determines the destination SP in advance, avoiding later complex bridging operations and reducing overall processing delay.
2Ease of operation
If the Send Message command is used for IPMI message transmission in blade server systems, then messages can be routed between service processors, but processing delay increases due to synchronization requirements
Solution Approach 1:
The patent extracts the routing decision logic from the time-consuming synchronization and bridging operations. By using the LUN field to directly identify the destination SP, the system eliminates the need for complex synchronization protocols and intermediate bridging steps that cause processing delays.
Solution Approach 2:
The system performs destination identification using the LUN field before initiating message forwarding. This preliminary routing action determines the final destination early in the process, avoiding subsequent synchronization delays and multiple hops that would increase processing time.
3Reliability
If complex bridging operations are implemented for message forwarding, then messages can be routed to correct destinations, but processing overhead increases
Solution Approach 1:
The patent extracts the essential routing information from the LUN field in the message header. This extracted LUN value directly identifies the destination SP, eliminating the need for complex bridging operations while maintaining accurate message delivery. The routing decision is based solely on the LUN field, simplifying the processing path.
4Adaptability or versatility
If multiple service processors are interconnected for blade server management, then system monitoring capability is enhanced, but message forwarding complexity increases
Solution Approach 1:
The patent makes the LUN field serve multiple functions: it identifies the destination SP for message routing, serves as a addressing mechanism for inter-SP communication, and enables direct forwarding decisions. This multi-functional use of the existing LUN field eliminates the need for separate addressing and routing mechanisms, reducing forwarding complexity while supporting multiple SPs.
Data Source
AI summary
Certain aspects direct to a system having at most four service processors (SP's). Each of the at most four SP's is assigned with a logical unit number (LUN) of 0 to 3. When the SP receives a message packet, the SP identifies the message packet based on the header of the message packet. The header uses a LUN field to identify a corresponding SP as a destination of the message packet. For the LUN 0 SP, when the message packet is identified as a request message packet for the LUN 0 SP, the SP processes the request message packet to generate a corresponding response message packet. When the message packet is identified as a request message packet for other SP's (LUN 1-3), the SP saves a copy of the header of the request message packet for later response use, and forwards the request message packet to the destination.