PER410 & PER620 sysid does not match lookup table in sys.ini

I guess my assumption here is that our Dell PowerEdge 410 and 620 servers should always have sysids of 028C and 04CE ([MACH] lookup has 028C=PER410 and 04CE=PER620). And based on that assumption we should be able to properly do a platform discovery. Because the sysids that are actually returned are not on the [MACH] list in sys.ini, I don't know if all bought PER410s and PER620s are going to be properly discoverable via the provided toolkit, only modified toolkit (modified sys.ini), and that makes me think I am missing something big here!

By the way, The two PER620 machines I have are evals, and for a while I thought the strange sysid numbers were because of that, until I went back and looked at the sysid of one of our PER410s we resell and saw a sysid that is also not on the list. The list ends at 0529. 80XX is wayyyyyy to high a number to be part of that list. Just strange!

Hello Rob

Could you tell me where the 810b and 8122 values are reported? What command are you using?

Thanks

The sysid is reported by the BIOS, and stored on the system board. The BIOS is programmed to function with a specific system ID, and that is the ID it reports.

These systems should always report that system ID, but if you order new systems with a different system board and BIOS they may report differently. A BIOS can be programmed to report any system ID that it wants, but in general our BIOS reports the ID on the board.

Thanks

Yes. command:

    syscfg --sysid

returns 810B and 8122, for the two different platforms, respectively.

In tkenvset.sh we have $MACH set via syscfg --sys.ini    .... If I manually add to the end of [MACH] lookup, a couple lines that read

    810b=PER410

    8122=PER620

... then I can get those strings assigned to environment variable $MACH and do a proper platform discovery, however, using the given sys.ini (from DTK, untouched) with the tkenvset.sh script, platform discovery fails, and it is because $MACH never gets set, because the reported sysid is not found anywhere on the lookup table supplied with the DTK.

looking at the [MACH] lookup table in sys.ini, I expect that these two platforms should have system IDs of 028C and 04CE, respectively. These should be reported using the command syscfg --sysid. But because the real reported sysid for these two platforms id not found in the {MACH] lookup,  platform discovery fails. (not trying to be incredibly redundant, just very explicative :)

We buy these, and resell them with our software to perform a very specific task. Sounds like this is the expected sysid for these units. Can I trust that those sysid numbers will always be the same for each platform?

Okay, well Platform Discovery is very important here now because our product hardware (same software) will now be 410s and 620s, and in order to support the existing r410 platforms out there and now r620s because of the end-of-life of the 410s, we would be very reliant on all of these system's sysid being always consistent for future deployment as well as  legacy support. So. I'm just needing to know if those particular unlisted sysid numbers are definitely known to be assigned to all machines of the like, and then I can go forward using the new sysid numbers for platform discovery. I'm not sure if I should be asking this here in the support forum or if I should ask our company's procurement guy to get a definitive answer about it from the Dell sales rep he deals with.

Thanks so much for your help!

I'm not sure if I should be asking this here in the support forum or if I should ask our company's procurement guy

I would check with your sales rep. As long as there are no revision changes to the hardware you are purchasing then the IDs should stay the same.

Thanks