Finding serial number of machine

[Andrew Hoffman]

Is their a script or command that I can run on a system to find out the serial number. I have inherited about 250 systems and need to do an audit

[Michael Steele_2]

There is a system id number (* or host id *) and the server serial number are often confused. The system id number resides on the system board, is sometimes referred to as the software serial number, is installed by a HP CE, is used for licensing, and can be displayed with 'uname -i.'

The serial number is altogether different and only appears on the outside of the HP server. It is often referred to as the hardware serial number. The HW S/N is linked to your system handle and is used by HP as an alternate means of identifying your HW support contract when opening a HW call, or, when the system handle is unavailable.

On a L2000 for instance the S/N will appear under the right side bottom panel when facing the front of the server, or, at the bottom of the front panel also when facing the server.

On a K Class server, (* bless them *), the HW S/N is printed behind the front panel.

The location of these HW S/N's will vary from HP server to HP server. (* sorry *)

If you're looking for a list of server S/N's, and this is certainly a critical list to have, then it might be easier for you to contact your HP Sales rep, the person who handles your support contracts, and have him accumulate a list. It will probably be incomplete so also refer to your HP sales order number and shipping manifest. The S/N will also appear on these documents.

There is also an ignite command called print_manifest that may be useful when obtaining the system id. One fault with print_manifest thought is it has mislabeled the system id as server serial number.

/opt/ignite/bin/print_manifest

This thread rehashes everything nicely:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x8c98c3d7fb78d4118fef0090279cd0f9,00.html

[Michael Steele_2]

There is a system id number (* or host id *) and the server serial number are often confused. The system id number resides on the system board, is sometimes referred to as the software serial number, is installed by a HP CE, is used for licensing, and can be displayed with 'uname -i.'

The serial number is altogether different and only appears on the outside of the HP server. It is often referred to as the hardware serial number. The HW S/N is linked to your system handle and is used by HP as an alternate means of identifying your HW support contract when opening a HW call, or, when the system handle is unavailable.

On a L2000 for instance the S/N will appear under the right side bottom panel when facing the front of the server, or, at the bottom of the front panel also when facing the server.

On a K Class server, (* bless them *), the HW S/N is printed behind the front panel.

The location of these HW S/N's will vary from HP server to HP server. (* sorry *)

If you're looking for a list of server S/N's, and this is certainly a critical list to have, then it might be easier for you to contact your HP Sales rep, the person who handles your support contracts, and have him accumulate a list. It will probably be incomplete so also refer to your HP sales order number and shipping manifest. The S/N will also appear on these documents.

There is also an ignite command called print_manifest that may be useful when obtaining the system id. One fault with print_manifest though is it has mislabeled the system id as server serial number.

/opt/ignite/bin/print_manifest

This thread rehashes everything nicely:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x8c98c3d7fb78d4118fef0090279cd0f9,00.html

[Andrew Hoffman]

Many Thanks for you quick responce. Looks like a pen and paper and a day in the LAB.

Thanks

@ndrew

[Michael Steele_2 · Accepted solution]

Hey, how's about 10 big ones?

[Sridhar Bhaskarla]

Hi,

If you are looking the Serial number to be used for HP support, then it depends on the hardware.

For older systems like K-class etc., you will have to physically look at the server. For the newer ones like RPs and Superdomes, you can get it from 'cstm'.

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

You will find the serial number here.

If you are stil using the factory loaded OS that came with the systems when you purchased them, then you can use /opt/ignite/bin/print_manifest to get the serial number. HP keeps the serial number in a seed file under /var/opt/ignite/defaults directory while loading the OS which would be read by print_manifest command. Subsequent reloads of OS will overwrite that information and print_manifest may print no|incorrect serial number.

If you are looking for the machine identification or the permanent SPU id for licenses, you would use either 'uname -i' or '/opt/ifor/ls/bin/i4target' depending on the type of the license vendor supports.

-Sri

[Geoff Wild]

SysInfo 2.04 by HP ESSO

Will give you that and more...

Here's how they do it:

# Function: f_get_serial
#
#
function f_get_serial
{
# check for libc.2 and is it executable
#
serial_number=""
if [[ -x ${where}/getsn ]]
then
if [[ -x /usr/lib/libc.2 ]]
then
Debug "running getsn"
print "Attempting to retrieve serial number."
check_sn=$(${where}/getsn 2>&1 | grep "Serial Number:")
if [[ ${check_sn} != *Available* ]]
then
serial_number=$(echo $check_sn | awk '{print $NF}')
Debug "getsn completed.....returned $SERIAL"
else
Debug "getsn completed.....serial not available"
fi
else
Debug "getsn failed.....libc.2 not found"
fi
else
Debug "Error: getsn not found or not executable."
fi
} # end of f_get_serial

[Michael R. Monteith]

if you have diagnostics running on your system you can do:

echo "sel path 'system' ; info; wait infolog" |cstm|grep -i "system serial number"

Otherwise you can run the attached program getsn from HP. Mind you that only systems like N-Class and above will return the serial number.

Michael

[Marlene Smith]

if ignite-ux is installed on your box - you can look at the manifest in /var/opt/ignite/recovery/latest, or issue a print_manifest and direct output to a file. I recommend doing the print_manifest as it is handy when you need it as well.

HTH

[Marlene Smith]

if ignite-ux is installed on your box - you can look at the manifest in /var/opt/ignite/recovery/latest, or issue a print_manifest and direct output to a file. I recommend doing the print_manifest as it is handy when you need it as well.

HTH