Hi Ragha, The service processor on a motherboard "listens" off port 623 and will "steal" packets off the wire that are meant for the service processor. Thus, the OS will never see the packet.
I'd take a look at the IPMI specification for more info. Al -- Albert Chu [EMAIL PROTECTED] 925-422-5311 Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory ----- Original Message ----- From: Raghavendra G <[EMAIL PROTECTED]> Date: Monday, May 29, 2006 10:25 pm Subject: Re: [Freeipmi-users] Some basic questions > Hi Albert, > > If there is no process is running on port 623 then why do we > specify the > port as 623 in the RMCP packets?? I am not able to get how the > packet is > sent to the Service processor? Is it something Inherent in RMCP ?? > Is there > a good documentation about this?? > > Regards, > > On 5/26/06, Albert Chu <[EMAIL PROTECTED]> wrote: > > > > Hi Ragha, > > > > > Lookinginto the problem I've found that on the blades no > process is > > > running on the port 623 (which is the default port used by > rmcpping).> > > No process is required to run w/ port 623 since rmcpping > communicates> with the service processor on a motherboard. If the > service processor > > runs on stand-by power (many motherboards do, yours may not > necessarily)> that means you can even rmcpping a machine when it is > powered off. > > > > > In that case how is the communication b/w BMC and MCs is done?? > > > Is it through the IPMB Bus?? i.e., does BMC and MCs on the blades > > > never use Ethernet to communicate (Specifically MCs not the > processes> like > > > openhpiapps running on blades)?? > > > > I've seen some bladed solutions that only allow remote management > with> the blade manager, and not with an individual blade. It is the > > responsibility of the blade manager to then communicate with each > blade> to do the management activity (power control, sensor > retrieval, etc.). > > I don't know your specific hardware, so I can't really say about > your> particular hardware. > > > > I *think* communication is done through the ICMB bus to the > blades, but > > my terminology understanding may be wrong here. However, I've > also seen > > it done through serial. So it's just up to the implementation. > > > > Al > > > > -- > > Albert Chu > > [EMAIL PROTECTED] > > 925-422-5311 > > Computer Scientist > > High Performance Systems Division > > Lawrence Livermore National Laboratory > > > > > > ----- Original Message ----- > > From: Raghavendra G <[EMAIL PROTECTED]> > > Date: Thursday, May 25, 2006 10:00 pm > > Subject: [Freeipmi-users] Some basic questions > > > > > Hi all, > > > We have an ATCA chassis with Schroff shelf manager (BMC). The > > > chassis has 4 > > > blades each having an MC. I am able to rmcpping the Shelf > > > Manager(BMC) from > > > any of the blades. But I am not able to rmcpping b/w the blades. > > > Lookinginto the problem I've found that on the blades no > process is > > > running on the > > > port 623 (which is the default port used by rmcpping). > > > > > > Is it that only the Shelf Manager can reply to rmcppings but not > > > the MCs on > > > the blades? In that case how is the communication b/w BMC and MCs > > > is done?? > > > Is it through the IPMB Bus?? i.e., does BMC and MCs on the blades > > > never use > > > Ethernet to communicate (Specifically MCs not the processes like > > > openhpiapps running on blades)?? > > > > > > Regards, > > > -- > > > > > > Raghavendra G > > > Software Engineer, > > > Clovis Solutions, Bangalore > > > +91 9880213025 > > > _______________________________________________ > > > Freeipmi-users mailing list > > > [email protected] > > > http://lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > -- > I AM AGAINST THE CURRENT RESERVATION POLICY! > http://youth4equality.org > http://savebrandindia.org > Raghavendra G > Software Engineer, > Clovis Solutions, Bangalore > +91 9880213025 > _______________________________________________ Freeipmi-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/freeipmi-users
