Andy, Ok, this is kind of confusing; two FRU locations for the same entity (though physically, one is for the mini-bmc(passive), the other for the addon imm (active)).
The entity 7.1 (system board.1st instance) has the following from the SDR: 1. MC device locator record with device id = 0 2. FRU device locator record with device id = 1 Different device id is valid for other entities, but for a system board entity, shouldn't this match at all times. Otherwise, there will be inconsistencies in FRU records as described by the phrase below. ".... FRU Device ID #00 at LUN 00b is predefined as being the FRU Device for the FRU that the management controller is located on...." The above statement presumes the active mc. It does not make sense to retrieve info from a passive mc. For one thing, there is no fru device locator record in the sdr that has device id = 0; although that exists (hidden). The above quote presumes that the fru device locator record with device id=0 exist. Anything not found in the sdr records, cannot be considered official. The strange consequence: updates are done on the active mc's fru; but reading at id=0 above does not provide info from the active mc. Having to retrieve the fru info of an mc other than device id=0 is pretty cumbersom. One has to traverse the sdr records and retrieve the correct device id. Any insights will be helpful Andy. Thanks. Michael ---- Original message ---- >Date: Mon, 22 Jan 2007 17:16:01 -0500 >From: "Cress, Andrew R" <[EMAIL PROTECTED]> >Subject: RE: [Openipmi-developer] FRU dev id on IMM Module >To: <[EMAIL PROTECTED]>, <[email protected]> > >Sure, to find the MC dev id you just read the SDR IPMB MC Locator record >(shown on the second line of the fruconfig output) to get the IMM FRU >information. > >However, loading the FRU information from fru device id 0 WILL still >give you the baseboard FRU information. So, reading FRU data from >FruDeviceId 0 will still work fine, in all IPMI systems, and that is the >last section of the output I attached. > >The baseboard is where all of the devices and sensors connect, so most >likely that is really what you want to do anyway. Is that what you >meant by FRU updates and appropriate FRU entries? You don't really use >the IMM FRU entries except as inventory for that plugin card. > >Andy > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Monday, January 22, 2007 5:05 PM >To: Cress, Andrew R; [email protected] >Subject: RE: [Openipmi-developer] FRU dev id on IMM Module > >Andy, > >Thanks for the clarification. > >Wouldn't this configuration pose as a problem: FRU updates are done to >the active bmc, w/c is device id 1; yet on bootup, we expect it to be at >device id 0. > >Anyway, to retrive the active bmc device id? Or to determine that the >mini-bmc is overriden? > >The code is used on both type of machines, I have to be able to >programmatically detect which device id is actually active and retrieve >the appropraite FRU entries. Thanks. > >Michael, > >On the Jarrell motherboard where the IMM resides, there is a default >mini-BMC and then the IMM plugin with IPMI 2.0 and the advanced >features. So, there are actually two BMCs, but only one is active at a >time. That is why the IMM has a FRU Device ID of 1, since the mini-BMC >occupied FRU ID 0. > >This should not pose a problem, and attached is the output from >'fruconfig' (from ipmiutil) on a TIGI2U system with an IMM. You can see >from the attached immfru.txt that the SlaveAddress/ChannelNumber for the >IMM BMC is 20/00, while the SlaveAddress/FruDeviceID is 20/01. > >The IPMI 1.5 text you reference is similar to text in section 37.7 about >the FRU Device ID, and is still true, since the mini-BMC on that >motherboard is FRU Device ID 0, but it is inactive. > >Andy ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
