System and method of forwarding IPMI message packets based on logical unit number (LUN)

A method of forwarding messages in a blade server system, comprising:

• receiving, at a service processor (SP) of the blade server system, a message packet from a system interface of the SP, wherein the blade server system comprises a network switch and at most four SP's interconnected with one another via the network switch, wherein each of the at most four SP's is assigned with a logical unit number (LUN) of 0, 1, 2 or 3, and wherein the message packet comprises a header identifying the message packet as a request message packet or a response message packet, wherein the header comprises a LUN field identifying one of the at most four SP's of the blade server system;
• based on the header and the LUN field of the message packet, identifying, at the SP, the message packet as a first request message packet having one other of the at most four SP's as a destination of the message packet, an intermediate response message packet from one other of the at most four SP's in response to the first request message packet, or a second request message packet having the SP as the destination of the message packet by:
• identifying whether a value of the LUN field of the message packet matches the LUN assigned to the SP;
• when the value of the LUN field of the message packet matches the LUN assigned to the SP, determining the message packet as the second request message, and
• when the value of the LUN field of the message packet does not match the LUN assigned to the SP, identifying one other of the at most four SP's having the LUN assigned with the value of the LUN field of the message packet as an identified SP, and determining the message packet as the first request message packet or the intermediate response message packet by:
• identifying, based on the header of the message packet, the message packet as the request message packet or the response message packet;
• when the header of the message packet indicates the message packet as the request message packet, determining the message packet as the first request message packet having the identified SP as the destination;
• and
• when the header of the message packet indicates the message packet as the response message packet, determining the message packet as the intermediate response message packet from the identified SP;
• when the message packet is the first request message packet, saving, at the SP, a copy of the header of the first request message packet, and sending the first request message packet to the destination;
• when the message packet is the intermediate response message packet in response to the first request message packet, retrieving, at the SP, the saved copy of the header of the first request message packet, and replacing the header of the intermediate response message packet with the saved copy of the header of the first request message packet to generate a final response message packet;
• and
• when the message packet is the second request message packet, processing, at the SP, the second request message packet to generate a second response message packet in response to the second request message packet.

A non-transitory computer readable medium storing computer executable codes, wherein the codes, when executed at a processor of a service processor (SP) of a blade server system, are configured to

• receive a message packet from a system interface of the SP, wherein the blade server system comprises a network switch and at most four SP' s interconnected with one another via the network switch, wherein each of the at most four SP's is assigned with a logical unit number (LUN) of 0, 1, 2 or 3, and wherein the message packet comprises a header identifying the message packet as a request message packet or a response message packet, wherein the header comprises a LUN field identifying one of the at most four SP's of the blade server system,
• identify, based on the header and the LUN field of the message packet, the message packet as a first request message packet having one other of the at most four SP's as a destination of the message packet, an intermediate response message packet from one other of the at most four SP's in response to the first request message packet, or a second request message packet having the SP as the destination of the message packet by:
• identifying whether a value of the LUN field of the message packet matches the LUN assigned with the SP,
• when the value of the LUN field of the message packet matches the LUN assigned with the SP, determining the message packet as the second request message, and
• when the value of the LUN field of the message packet does not match the LUN assigned with the SP, identifying one other of the at most four SP's having the LUN assigned with the value of the LUN field of the message packet as an identified SP, and determining the message packet as the first request message packet or the intermediate response message packet by:
• identifying, based on the header of the message packet, the message packet as the request message packet or the response message packet,
• when the header of the message packet indicates the message packet as the request message packet, determining the message packet as the first request message packet having the identified SP as the destination, and
• when the header of the message packet indicates the message packet as the response message packet, determining the message packet as the intermediate response message packet from the identified SP,
• when the message packet is the first request message packet, save a copy of the header of the first request message packet, and send the first request message packet to the destination,
• when the message packet is the intermediate response message packet in response to the first request message packet, retrieve the saved copy of the header of the first request message packet, and replace the header of the intermediate response message packet with the saved copy of the header of the first request message packet to generate a final response message packet, and
• when the message packet is the second request message packet, process the second request message packet to generate a second response message packet in response to the second request message packet.