Serial-Number from CPU

[Konrad Hegner]

How can I read the serial-number from the CPUs on an K380 and rp54x0 machine. By the B2000-machine it is possible by starting the xstm.
But one the other machines is only written: 'N/A'.
If there any other way for read this serial-number.
We need it for our support-conract

Regards Konrad

[Steven E. Protter]

In servers the serial number is usually stamped or attached somewhere on the rack or server. It's not accessible by software as far as I know.

Get a flashlight and look around, you'll find it.

P

[T G Manikandan]

Physically find out the serial number on the machine.

[Nick Wickens]

You should find the serial number on the K class machine on the back of the CD drive door at the front.

There is a machine ID available with the uname -i command but this is not a serial number. If your front door has gone walkies then it might be worth seeing if HP can ID from that machine ID.

[Ravi_8]

Hi,

serial number usually will be on machine itself. you have to look physically.

[Sridhar Bhaskarla]

HI Konrad,

On K380 you have to get it from the backside of the front door.

On RP54x0, you can use cstm to get the serial number.

/usr/sbin/cstm -> map -> sel dev 1 -> info ->infolog

-Sri

[Zeev Schultz]

If you have ignite/isee they provide
a way to see serial number as well (
print_manifest in ignite and isee gui).
K380 either is a sticker somewhere or HP techie
via Boot Menue :).

Regards

Zeev

[MANOJ SRIVASTAVA · Accepted solution]

Hi Konrad


There is a utility called as sysinfo availablw with HP CE's to run and this genreates the serial no tooo .I have attached the script for your convienience.



Manoj Srivastava

[Brian K. Arnholt]

Zeev is correct, if you can't get it from the tag on the back of the machine, you can get it from "print_manifest" under Ignite-UX.

I recently had to audit all my remote CPUs Serial Numbers, and thanks to "print_manifest" it saved me many trips!

Brian

[Ralph Grothe]

Hi Konrad,

I find this topic rather annoying on HP-UX boxes, as the whole thing seems to be handled rather inconsistently by HP.

On some boxes, don't ask me on which models, the print_manifest command may show you the wanted info.
So on these I created this alias for root:

# alias serial
serial='/opt/ignite/bin/print_manifest -s|awk '\''/erial number/{print $NF}'\'

But beware, as said print_manifest reveals the SE No. only on some HP models, only the gods know why.

On the other hand I had a look at the Korn shell script supplied by MANOJ how they accomplished the wizardry.
There they seem to invoke a program called
/bin/getsn
Ouch, sorry folks on my HP boxes I cannot find this binary.

As said the whole mistery HP performs about their serial numbers is such a nuisance in my view.

[Ralph Grothe]

I'd like to apologize for my malposting.
I really should have read the subject line of this thread more carefully.
You were asking about the CPUs' serial numbers.
Stick with cstm in that case (as someone else already correctly posted).
Please ignore the rubbish I posted.
Albeit, the host's serial number mistery I'd still consider an annoyance.

[Konrad Hegner]

Hi Ralph, Hi all with 0 (zero) points!

Yes, it is true I asked about the serial number from the CPUs.

With print_manifest there is no serial-number from the CPU (I know print_manifest). Also with the stm/xstm/cstm is only a serial-number available, if you have the correct version from this tool (probably a newer one), and a K3x0 is a 'old' machine, then also no number!

But I will try this script from Manoj. Anyway thanks for the help.

[Sridhar Bhaskarla]

Konrad,

There is no serial number specific to a CPU. In that case for my superdome, I would be having 64 serial numbers.

For your support-contract which I believe with HP, you would need the system's serial number. And I posted the ways to get it.

By the way print_manifest or sysinfo get the information from the seed files and the seed files are to be updated manually with the serial numbers which HP does with the factory installed OS. If you re-installed the UNIX, then you lose it.

For ex., print_manifest gets the information from /var/opt/ignite/config.local file which is to be updated manually.
Sysinfo reads serial number from a file called system_db from current directory or /usr/local/bin in that order. And you need to populate this file.

-Sri

[Dietmar Konermann]

Konrad,

only "newer" system really know their serial number. This is true for N series, L series, A400/500, the Superdome, and newer workstations. There you get that information through a diag2 driver API from stable storage... newer versions of the diagnostics and the (unsupported) getsn tool (used by sysinfo) call that interface also.

So no chance for your K380. The rp54x0 supports it definitely, so you need newer diagnostics or the getsn tool there.

Best regards...
Dietmar.

[Dietmar Konermann]

Oops, didn't see that you're talking about CPU serial numbers. However, availability of this info may depend on PDC and OnlineDiag's revisions. But what the heck do you need this for? I doubt that contract are linked to CPU serials.