How to find Rack vs. System/Chassis Serial Numbers on any Engineered System.

Asset ID:	1-71-1915853.1
Update Date:	2016-03-28
Keywords:

Solution Type Technical Instruction Sure

Solution 1915853.1 : How to find Rack vs. System/Chassis Serial Numbers on any Engineered System.

Applies to:

Oracle Database Appliance Software - Version 2.1.0.1 and later
Oracle Exadata Storage Server Software - Version 11.2.1.2.0 and later
Oracle Database Appliance - Version All Versions and later
Oracle SuperCluster M6-32 Hardware - Version All Versions and later
SPARC SuperCluster T4-4 - Version All Versions and later
Linux x86-64
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)

Goal

How to query the system (from OS shell prompt) for Engineered System's Rack Serial Number, and other useful HW-related info.

Solution

Engineered Systems (ES), including ExaData (ED), SuperCluster (SC), and Oracle Database
Appliance (ODA), that need a Field Service Task (FST), require a HardWare (HW) Customer
Support Identifier (CSI) #, for which a HW Serial Number (SN) is also needed.

While there are many SNs associated w/the various components, for CSI/FST purposes, there are
only 2 types that matter: the "Rack" SN (for the _entire_ ES), a.k.a. Top Level Identifier (TLI),
which is strongly preferred, or alternatively, the "Chassis", a.k.a. "Product", or "System" SN
(which varies for each node in the Rack).

Rack SNs, are 10-character alphanumeric strings that, on ED & SC, always contain the 2-character
substring "AK", either at the beginning or in the middle, with the other 8 being numeric digits, e.g.
"AKnnnnnnnn" or "nnnnAKnnnn". The format for Chassis/Product/System (C/P/S) SN varies, as do the
exact commands to retrieve these, depending on the OS/HW platform, of which there are 3 for ES:

1) Linux x86-64 (ED, DB nodes, default, only for ED Storage Cells & ODA),
2) Solaris x86-64 (ED, DB nodes, alternate/option),
3) Solaris SPARC (SC, DB nodes, only)

On each of the above, there are multiple commands that can show the C/P/S SN, but only 1 that
can show the Rack SN, namely 'ipmitool' (which can show both). Alas, its location is different for
each OS Platform, and note that Solaris actually has 2 different versions in 2 different locations,
only 1 of which actually implements the required subcommands (sunoem cli):

Linux: /usr/bin/ipmitool # (only location, but doesn't work on ED V1)
Solaris x86-64: /opt/ipmitool/bin/ipmitool # (not /usr/sbin/ipmitool)
Solaris SPARC: /opt/ipmitool/sbin/ipmitool # (not /usr/sbin/ipmitool)

The above is NOT a typo; the location _is_ slightly different between the 2 Solaris platforms, so
you need to either specify the appropriate absolute path above in the following commands, or
prepend the directory to the PATH environment variable. The examples below assume the latter.

ipmitool sunoem cli "show /SP system_identifier"

The "system_identifier" string also shows the general type of ES (ED vs. SC vs. ODA), but does _not_
always identify the HW generation (V2 vs. X2, etc.), so to provide further info that _will_ help identify
the HW gen, you can also include (conveniently, in the same command!) the "system_description":

ipmitool sunoem cli "show /SP system_description system_identifier"

Although the CSI #s are _supposed_ to be associated with _Rack_ SNs, sometimes we find that
_Chassis_ SNs were entered instead, so to get that, use:

ipmitool sunoem cli "show /SYS product_serial_number"

However, unlike the "system_identifier", the above shows _only_ the SN, with no other identifying
info, so it is helpful to also include the model name:

ipmitool sunoem cli "show /SYS product_name product_serial_number"

The above is especially useful when it is important to distinguish between say a Compute Node vs.
a Storage Cell. All of the above can be combined and piped through a filter as follows:

{ ipmitool sunoem cli "show /SP system_description system_identifier" ; \
ipmitool sunoem cli "show /SYS product_name product_serial_number" ; \
} | grep = ;

which provides a nice summary, as in the following examples from several types of ES:

ODA V1:
        system_description = SUN FIRE X4370 M2 SERVER, ILOM v3.0.16.22.d, r83408
        system_identifier = Oracle Database Appliance
        product_name = SUN FIRE X4370 M2 SERVER
        product_serial_number = 1138FMW001
ODA X3-2:
        system_description = SUN FIRE X4170 M3, ILOM v3.1.2.10.d, r83372
        system_identifier = ODA X3-2 V2 node1 1329FM0007
        product_name = SUN FIRE X4170 M3
        product_serial_number = 1328FML11A
ED X2-8:
        system_description = Sun Fire X4800, ILOM v3.0.16.16, r69500
        system_identifier = Exadata Database Machine X2-8 1102AK23EF
        product_name = Sun Fire X4800
        product_serial_number = 1041FMA006
SC T4:
        system_description = SPARC T4-4, ILOM v3.0.16.9.b, r77667
        system_identifier = Oracle SPARC SuperCluster T4-4 AK00022779
        product_name = SPARC T4-4
        product_serial_number = 1139BDY8C1
SC T5:
        system_description = SPARC T5-8, ILOM v3.2.1.5.b, r83085
        system_identifier = Oracle SuperCluster T5-8 AK00129215
        product_name = SPARC T5-8
        product_serial_number = AK00124884

NOTE: The above queries all work on _all_ (SUN/Oracle) hardware generations of _all_
Engineered Systems, _except_ the very 1st (V1) Hewlett-Packard HW-based Exadata.

However, for the newer HW generations, starting w/X3 for ED & ODA, and T5 for SC,
there is an alternate (but preferred) query instead:

ipmitool sunoem cli "show /System" | grep = | egrep 'id|mod|ser'

which produces the following output on various newer systems:

ODA:
        model = ODA X3-2
        serial_number = 1329FM0007
        component_model = SUN FIRE X4170 M3
        component_serial_number = 1328FML11A
        system_identifier = ODA X3-2 V2 node1 1329FM0007
ED:
        model = Exadata X4-2 Upgrade
        serial_number = AK00176297
        component_model = SUN SERVER X4-2
        component_serial_number = 1349NML05V
        system_identifier = (none)
SC:
        model = SuperCluster T5-8
        qpart_id = Q9527
        serial_number = AK00129215
        component_model = SPARC T5-8
        component_serial_number = AK00124884
        system_identifier = Oracle SuperCluster T5-8 AK00129215

Now, ipmitool relies on the ILOM, and sometimes (for various reasons) that may
(temporarily) not be working right, so an alternative may be needed. For Linux-
based (ED & ODA) systems, that is '/usr/sbin/dmidecode' (which is the only option
for ED V1), but by itself that produces way too much output, so you need to restrict
it to just "System" info, by using the '-t 1' switch, and then filter it, as follows:

dmidecode -t 1 | egrep 'Product|Serial'

Product Name: SUN FIRE X4170 M3
Serial Number: 1328FML11A

However, this only gets us the chassis SN for whichever node the above is run
on, so to get all of them (e.g. on an all-Linux ED) requires dcli:

dcli -g ~/all_group -l root -t "dmidecode -t 1" | egrep 'Product|Serial'

The equivalent on Solaris x86-64 (ED) is '/usr/sbin/smbios', which likewise
needs switches & filters as follows:

smbios -i 1 | grep : | head -4 | grep -v ': *$'

Alas, there is no such equivalent on Solaris SPARC (SuperCluster); the closest is
'/usr/sbin/prtdiag', the 1st line from which provides only the HW gen:

prtdiag | head -1

System Configuration: Oracle Corporation sun4v SPARC T4-4

and, w/the -v switch, the last provides the Chassis SN:

prtdiag -v | tail | sed -n '/^Ch/{p;n;n;p;}' | paste - -

Chassis Serial Number 1139BDY8C1

Of course, a Solaris ED or SC still uses Linux on the Storage Cells, so the
dcli command above would have to be modified & split in two, i.e.:

dcli -g ~/cell_group -l root -t "dmidecode -t 1" | egrep 'Product|Serial'

and (for Solaris ED only):

dcli -g ~/dbs_group -l root -t "smbios -i 1 | grep : | head -4 | grep -v ': *$'"

The ipmitool commands can of course also be run with dcli, and as with any of
the previous examples, it can be helpful to capture the output from all nodes
to a single file e.g.:

{ dcli -g ~/all_group -l root -t 'ipmitool sunoem cli \
"show /SYS product_name product_serial_number"' | grep = ; } | tee \tmp\SNs.log

Another alternative for SuperClusters using Logical Domains (LDOMs) is the command:

virtinfo -a | grep serial

Chassis serial#: 1140BDY906

That's all !

Support: once you have the Rack and/or System/Chassis SN(s), you can use MOS Analytics to lookup the CSI:

https://mos-analytics.us.oracle.com/analytics/saw.dll?Dashboard&PortalPath=%2Fshared%2FGCS%20Support%20Delivery%20Analytics%2F_portal%2FEngineered%20Systems&Page=PLA%20CSI%20Lookup

(Note: above link can also be used for reverse lookup of SN from CSI.)

Attachments

This solution has no attachment