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
===============