On Tue, 2011-12-20 at 11:20 -0800, Ryan Cox wrote: > Al, > > I tried iterating from 0xC0 through 0xCF on some Dell M610s and didn't > find the slot number. I compared the results of several that were in > the same chassis so that most of the information would be the same. I > saw no differences that seemed to indicate the slot number. The only > differences at all that I saw from blades in the same chassis were at > 0xC3 and 0xC5 (expected). We don't have asset tags set or I would > expect to see differences in 0xC4.
Sorry it didn't work. It was worth a shot :-) Al > Ryan > > On 12/19/2011 11:04 AM, Albert Chu wrote: > > Hi Chris, > > > > I might be misunderstanding your question, but it seems you want to > > figure out what type of board is inside each slot? I assume the > > ipmi-oem Dell command 'get-system-info' isn't enough b/c you only get > > the board name and not the slot number? > > > > I don't know of any OEM commands for this, so the first thing is I'd bug > > Dell, b/c someone there might be able to provide it (you will have to > > fight them to get to the right people, the first line support will > > likely have no idea). If you get something from them, please let the > > list know and we can put it in ipmi-oem. > > > > Depending on your willingness to try and reverse engineer something, > > there might be a way to determine it. The following is an ipmi-raw that > > should implement the same thing as "ipmi-oem dell get-system-info > > asset-tag" > > > > /usr/sbin/ipmi-raw 0 6 59 0 0xC4 0 0 > > > > In ipmi-oem here's a comment on the parameter numbers: > > > > * guid parameter = 0xC3 > > * asset-tag parameter = 0xC4 > > * service-tag parameter = 0xC5 > > * chassis-service-tag parameter = 0xC6 > > * chassis-related-service-tag parameter = 0xC7 > > * board-revision parameter = 0xC8 > > > > This is what we know of or have been told. It wouldn't be hard to > > imagine that 0xC9, 0xCA ,0xCB might return your slot number. > > > > Al > > > > On Sun, 2011-12-18 at 06:39 -0800, DeRamus, Chris wrote: > >> I've just learned about the wonders of IPMI this past month and have > >> re-written our inventory system from scratch to take advantage of the data > >> the FreeIPMI suite of tools provides easy access to. Right now the only > >> drawback is that I have to run a secondary script at each co-location to > >> access each of our Dell M1000e chassis, running proprietary racadm command > >> over SSH to correlate which 10g/11g PowerEdge blades are running in the > >> various slots. I've been digging through the documentation in hopes of > >> finding either a oem command that I can run or even a ipmi-raw command > >> that can be passed to each blade to pull this data, but so far I've come > >> up short. > >> > >> Has anyone on this list been able to identify a method to capture this > >> particular information? Dell's OMSA utility also provides the slot > >> information as seen in the output below. > >> > >> #> omreport chassis info > >> Chassis Information > >> > >> Index : 0 > >> Chassis Name : Main System Chassis > >> Host Name : xxxxxxxxxxxx > >> iDRAC6 Version : 1.60 > >> Chassis Model : PowerEdge M600 > >> Chassis Lock : Not Present > >> Chassis Service Tag : XX11YY2 > >> Server Module Service Tag : YY11XX2 > >> Server Module Location : Slot 14<-- This is what I need > >> Flash chassis identify LED state : Off > >> Flash chassis identify LED timeout value : 300 > >> > >> Thanks in advance for the time guys. > >> > >> --Chris > >> _______________________________________________ > >> Freeipmi-users mailing list > >> [email protected] > >> https://lists.gnu.org/mailman/listinfo/freeipmi-users > >> > > > -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list [email protected] https://lists.gnu.org/mailman/listinfo/freeipmi-users
