Dan, I was initially attempting to understand why I could not access specific entities using the bridging command line arguments (-t, -b, -T, -B,) and the -m switch. This led me to the discovery that you had to specify -m 0 to get the PICMG discovery code to run, then to how the target and transit addresses specified on the command line were being used to do addressing in ipmitool. The confusion I had with interpretation of what I was seeing when I used these switches to address entities was very similar to what you are seeing using the switches. Also, there was the more subtle issue that I could not address sensors in an SDR repository that I addressed using the bridging command line arguments due to the issues I outlined in my email thread with Dmitry.
The first major difference between TOB (What you call CVS ROOT) and TOB plus my patch is the fact that on a PICMG platform, my patch will always perform a PICMG address discovery, whereas TOB would only do this if you specified '-m 0'. This is why you get a different answer for ipmitool fru with my patch vrs TOB and also why you found TOB would get you the same result as my patch when you specified '-m 0' with TOB. The other thing you found with my patch is that you can no longer address the "Asis ATCA IPMI Shelf Manager". This is due to the change to always do PICMG discovery of the IPMB address and utilize the discovered address instead of having -m override the discovered address. With the TOB code, an address specified with -m or the default IPMB address 0x20 would always be used unless you specified '-m 0' to force discovery. To fully enable prior functionality, I would have to make the specification of any address with -m <address> inhibit default PICMG discovery. I think this is the right thing to do and I'll update my patch to do this unless folks have any issues with this change. I would also change the man page for -m to state the following: Set the local IPMB address. The default is 0x20 or auto discovered on PICMG platforms so there should be no need to change it for normal operation. With the above change, you will be able to address the Shelf Manager again, but you would have to specify -m 0x20 to do so. Now, when you get down to trying to address specific entities via the bridging command line arguments you will find that certain things just don't get you what you would expect unless you understand the internal implementation of -m, and the bridging command line switches. You showed one example when you tried to address 0x28 with the TOB version. This fails on your system because you didn't specify -m 0 to have ipmitool use the PICMG discovered address instead of the default 0x20 address. You should probably verify that when you add '-m 0' to the following command line you get the same answer as the patched version. Also, you can use -v to see the PICMG discovered address (which I assume is not 0x20 on your platform). a)CVS ROOT: dg:speedy:build => src/ipmitool -I lan -H 192.168.1.8 -A none -t 0x82 fru Error: Unable to establish LAN session FRU Device Description : Builtin FRU Device (ID 0) Get Device ID command failed I did my best to answer your questions, but I'm sure I missed something. Let me know if you need more clarification or details. Thanks for help testing this out, Jim -- Jim Mankovich | jm...@hp.com (US Mountain Time) -- On 4/23/2013 7:47 PM, Dan Gora wrote: > Hi guys, > > I'm working on coming up with a set of test cases to test this patch, > but I'm going to need some help with making sure that everything is > sane and valid. > > First off, can you describe, Jim, what was the problem was initially > in 1.8.12 exactly? What were you trying to read and how were you > connecting and what arguments were you using? I'd like to include > that in the test cases below. > > What I have available is a 2U PICMG system which consists of an ASIS > 2U chassis which contains the following: > > Shelf Manager - PPS ShMM- 500 > Slot 1 - Adax PacketRunner with PPS ATCA carrier IPMC software with 2 > Adax ATM4 AMC cards in AMC slots 2 and 3 with PPS AMC IPMC software > Slot 2 - DTI fabric switch with ??? IPMC software > > There are a few different places from which we would want to run ipmitool: > 1) From a totally external "system manager" system (totally external > from the ATCA chassis) > 2) From the payload of our Adax PacketRunner > 3) From the payload of AMC cards on our PacketRunner. (it's not > totally clear how much functionality we can expect from here) > > Here is what the system addresses look like from an external system manager: > > dg:speedy:build(master) => src/ipmitool -I lan -H 192.168.1.8 -A none > sdr elist all > ShMM-500 | 00h | ok | 240.96 | Dynamic MC @ 10h > ShMM-500 | 00h | ok | 240.96 | Dynamic MC @ 12h > ADAX PR | 00h | ok | 160.96 | Dynamic MC @ 82h > ADAX ATMiv-AMC | 00h | ns | 193.99 | Logical FRU @03h > ADAX ATMiv-AMC | 00h | ns | 193.100 | Logical FRU @04h > ATS0020 | 00h | ok | 160.96 | Dynamic MC @ 84h > > It seems that the major change with this patch is the behavior when I > run ipmitool from the payload of the Adax PacketRunner (aka the APR). > >From the CVS trunk, the default behavior when no bridging arguments > are specified, when run from the payload ipmitool would primarily talk > to the IPMC on the APR. For example 'ipmitool fru' would show only > the FRU information for the APR plus the AMC cards. With the patch > applied, ipmitool now "talks" primarily with the shelf manager. So > with the patch applied 'ipmitool fru' shows all the FRU information > for all boards in the ATCA chassis. > > To my mind, this is a good and a bad thing, and it might not be what > people expect. It's good in that ipmitool behaves the same way if you > run it from the APR's payload or if you run it from an external system > manager connected to the shelf manager. However it might not be what > people expect (and is different from the previous behavior) in that > people probably expect ipmitool to connect to the "local BMC" which > would be the APR's IPMC when run from the APR's payload. > > It's bad because the user doesn't really have any way to know what the > IPMB-0 address is of the local IPMC when running from the APR's > payload. We can get the address records for all the boards in the > ATCA chassis with 'ipmitool sdr elist all', but if there were two APRs > in the chassis, the user would really have no way to know which one > was the local one. This might also affect things like ipmievd which > is supposed to monitor the local BCM's sensors. I'm not really sure > how to resolve this issue. > > > So here are some test cases.. Please have a look though these and make > sure that I'm doing things correctly and that we're getting the > results that we expect. > > FRU information > =============== > > >From external system manager with 'lan' interface connecting to the > shelf manager of the ATCA system: > > 1) Get system FRU information with 'ipmitool fru' > > a) CVS-ROOT (plus my patch to fix lan.c.. sigh..) > > dg:speedy:build => src/ipmitool -I lan -H 192.168.1.8 -A none fru > FRU Device Description : Builtin FRU Device (ID 0) > Board Mfg Date : Thu Jan 22 08:24:00 2009 > Board Mfg : Asis ltd. > Board Product : ATCA IPMI Shelf Manager > Board Serial : 0831234/017 > Board Part Number : ATCAXXU-042-0010 > Product Manufacturer : Asis ltd. > Product Name : ATCA IPMI Shelf Manager > Product Part Number : ATCAXXU-040-0011 > Product Version : > Product Serial : 0932602/002 > > FRU Device Description : ShMM-500 > Board Mfg Date : Thu Jan 22 08:24:00 2009 > Board Mfg : Asis ltd. > Board Product : ATCA IPMI Shelf Manager > Board Serial : 0831234/017 > Board Part Number : ATCAXXU-042-0010 > Product Manufacturer : Asis ltd. > Product Name : ATCA IPMI Shelf Manager > Product Part Number : ATCAXXU-040-0011 > Product Version : > Product Serial : 0932602/002 > > b) with Jim's 0001-PICMG-Sensor-Bridging-Update-1.patch > > dg:speedy:build(master) => src/ipmitool -I lan -H 192.168.1.8 -A none fru > FRU Device Description : Builtin FRU Device (ID 0) > Board Mfg Date : Sun Mar 30 20:00:00 2003 > Board Mfg : Pigeon Point Systems > Board Product : Pigeon Point Systems ShMM-500 > Board Serial : PPS0000000 > Board Part Number : A > Product Manufacturer : Pigeon Point Systems > Product Name : Pigeon Point Systems Shelf Manager > Product Part Number : 000000 > Product Version : Rev 1.00 > Product Serial : PPS0000000 > > FRU Device Description : ShMM-500 > Device not present (No Response) > > FRU Device Description : ShMM-500 > Board Mfg Date : Thu Jan 22 08:24:00 2009 > Board Mfg : Asis ltd. > Board Product : ATCA IPMI Shelf Manager > Board Serial : 0831234/017 > Board Part Number : ATCAXXU-042-0010 > Product Manufacturer : Asis ltd. > Product Name : ATCA IPMI Shelf Manager > Product Part Number : ATCAXXU-040-0011 > Product Version : > Product Serial : 0932602/002 > > FRU Device Description : ADAX PR > Board Mfg Date : Thu Sep 20 21:00:00 2012 > Board Mfg : ADAX, Inc. > Board Product : PacketRunner > Board Serial : 0000146 > Board Part Number : 90-4000-00 > Product Manufacturer : ADAX, Inc. > Product Name : PacketRunner > Product Part Number : 000000 > Product Version : MRL 15 > Product Serial : 0000146 > > FRU Device Description : ADAX ATMiv-AMC (ID 3) > Board Mfg Date : Wed Oct 28 14:12:00 2009 > Board Mfg : ADAX > Board Product : ATM4-AMC > Board Serial : 0000354 > Board Part Number : A > Product Manufacturer : ADAX > Product Name : ATM4-AMC > Product Part Number : 82-6000 > Product Version : MRL 6A > Product Serial : 0000354 > Product Asset Tag : COMM > > FRU Device Description : ADAX ATMiv-AMC (ID 4) > Board Mfg Date : Tue Dec 14 14:12:00 2010 > Board Mfg : ADAX > Board Product : ATM4-AMC > Board Serial : 0000289 > Board Part Number : A > Product Manufacturer : ADAX > Product Name : ATM4-AMC > Product Part Number : 82-6000 > Product Version : MRL 7 > Product Serial : 0000289 > Product Asset Tag : COMM > > FRU Device Description : ATS0020 > Board Mfg Date : Wed Jul 11 09:36:00 2007 > Board Mfg : Diversified Technology, Inc. > Board Product : ATS0020 > Board Serial : 06380116 > Board Part Number : 912100020 > Product Manufacturer : Diversified Technology, Inc. > Product Name : ATS0020 > Product Part Number : 912100020 > Product Version : 1.4 > Product Serial : 06380116 > > Result: Better.. We can see all of the boards in the ATCA chassis now, > but I don't really know what the Asis ACTA Shelf manager is in the > output of the CVS ROOT case. I'm a bit confused by that... > > Also note that if I specify _any_ non-zero value with -m in the CVS > ROOT case above, then I get the same output as I get with Jim's patch. > I'm not really sure what is up with that. It looks like if I specify > a non-zero value with -m, then the PICMG GetDeviceLocator doesn't get > run in the CVS ROOT case. > > 2) Getting FRU information from a specific blade in ATCA chassis. > Here I try and get the FRU information from the APR directly with the > -t 0x82 flag: > > a)CVS ROOT: > dg:speedy:build => src/ipmitool -I lan -H 192.168.1.8 -A none -t 0x82 fru > Error: Unable to establish LAN session > FRU Device Description : Builtin FRU Device (ID 0) > Get Device ID command failed > > b) with Jim's patch: > dg:speedy:build(master) => src/ipmitool -I lan -H 192.168.1.8 -A none > -t 0x82 fru > FRU Device Description : Builtin FRU Device (ID 0) > Board Mfg Date : Thu Sep 20 21:00:00 2012 > Board Mfg : ADAX, Inc. > Board Product : PacketRunner > Board Serial : 0000146 > Board Part Number : 90-4000-00 > Product Manufacturer : ADAX, Inc. > Product Name : PacketRunner > Product Part Number : 000000 > Product Version : MRL 15 > Product Serial : 0000146 > > FRU Device Description : ADAX PR > Board Mfg Date : Thu Sep 20 21:00:00 2012 > Board Mfg : ADAX, Inc. > Board Product : PacketRunner > Board Serial : 0000146 > Board Part Number : 90-4000-00 > Product Manufacturer : ADAX, Inc. > Product Name : PacketRunner > Product Part Number : 000000 > Product Version : MRL 15 > Product Serial : 0000146 > > FRU Device Description : ADAX ATMiv-AMC (ID 3) > Board Mfg Date : Wed Oct 28 14:12:00 2009 > Board Mfg : ADAX > Board Product : ATM4-AMC > Board Serial : 0000354 > Board Part Number : A > Product Manufacturer : ADAX > Product Name : ATM4-AMC > Product Part Number : 82-6000 > Product Version : MRL 6A > Product Serial : 0000354 > Product Asset Tag : COMM > > FRU Device Description : ADAX ATMiv-AMC (ID 4) > Board Mfg Date : Tue Dec 14 14:12:00 2010 > Board Mfg : ADAX > Board Product : ATM4-AMC > Board Serial : 0000289 > Board Part Number : A > Product Manufacturer : ADAX > Product Name : ATM4-AMC > Product Part Number : 82-6000 > Product Version : MRL 7 > Product Serial : 0000289 > Product Asset Tag : COMM > > c) CVS ROOT with -t 0x82 -m 0xX (where X is any non-zero digit) > > dg:speedy:build => src/ipmitool -I lan -H 192.168.1.8 -A none -t 0x82 > -m 34 fru > FRU Device Description : Builtin FRU Device (ID 0) > Board Mfg Date : Thu Sep 20 21:00:00 2012 > Board Mfg : ADAX, Inc. > Board Product : PacketRunner > Board Serial : 0000146 > Board Part Number : 90-4000-00 > Product Manufacturer : ADAX, Inc. > Product Name : PacketRunner > Product Part Number : 000000 > Product Version : MRL 15 > Product Serial : 0000146 > > FRU Device Description : ADAX PR > Board Mfg Date : Thu Sep 20 21:00:00 2012 > Board Mfg : ADAX, Inc. > Board Product : PacketRunner > Board Serial : 0000146 > Board Part Number : 90-4000-00 > Product Manufacturer : ADAX, Inc. > Product Name : PacketRunner > Product Part Number : 000000 > Product Version : MRL 15 > Product Serial : 0000146 > > FRU Device Description : ADAX ATMiv-AMC (ID 3) > Board Mfg Date : Wed Oct 28 14:12:00 2009 > Board Mfg : ADAX > Board Product : ATM4-AMC > Board Serial : 0000354 > Board Part Number : A > Product Manufacturer : ADAX > Product Name : ATM4-AMC > Product Part Number : 82-6000 > Product Version : MRL 6A > Product Serial : 0000354 > Product Asset Tag : COMM > > FRU Device Description : ADAX ATMiv-AMC (ID 4) > Board Mfg Date : Tue Dec 14 14:12:00 2010 > Board Mfg : ADAX > Board Product : ATM4-AMC > Board Serial : 0000289 > Board Part Number : A > Product Manufacturer : ADAX > Product Name : ATM4-AMC > Product Part Number : 82-6000 > Product Version : MRL 7 > Product Serial : 0000289 > Product Asset Tag : COMM > > Results: So the patch seems to fix the problem where we have to > prevent the PICMG GetDeviceLocator from running by specifying a > non-zero -m flag. That seems good to me. > > > The above results seem to be consistent for all the ipmitool fru subcommands. > > thats all for tonight.. More tomorrow. > > thanks > dan > ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
