Re: get Device Information

From: Andreas Schulze (b79xan_at_gmx.de)
Date: 11/28/03 

Date: Fri, 28 Nov 2003 13:42:16 +0100

"Bernd Huebenett" <huebenet@de.ibm.com> schrieb im Newsbeitrag
news:bq79r6$5ag$1@sp15at20.hursley.ibm.com...
> Andreas Schulze wrote:
>
> >
> > Hallo Bernd,
> >
> > yes, lsvpd extracts its output from the ODM.
> >
> > Regards,
> > Andreas
> >
>
> Hi Andreas,
>
> but AIX doesn't seem to store all the VPD in CuVPD.
> I am looking for a way to retrieve the VPD directly from the ODM.
>
> (root@localhost)/> odmget CuVPD | grep -p pdisk0
> CuVPD:
> name = "pdisk0"
> vpd_type = 0
> vpd = "*MFIBM *TMDMVC36B"
>
> (root@localhost)/> odmget CuVPD | grep -p rmt0
> CuVPD:
> name = "rmt0"
> vpd_type = 0
> vpd = "*MFHP *TM\n\
> IBM-C568303030!D*Z1C209*SN2126S175*LIA1700292*PN19P0798 *F19P0802
> *ECH27417 *Z0\n\
> 0180020283000038*Z3L1 "
>
>
> (root@localhost)/>lscfg -vl rmt0
> EINHEIT POSITION BESCHREIBUNG
>
> rmt0 10-60-00-1,0 SCSI-4-mm-Bandlaufwerk (20480 MB)
>
> Hersteller .................HP
> Maschinentyp und Modell ....IBM-C568303030!D
> Einheitenspezifikation(Z1)C209
> Seriennummer ...............2126S175
> Einheitenspezifikation(LI)A1700292
> Teilenummer ................19P0798
> FRU-Nummer .................19P0802
> Stand der techn. Änderung ..H27417
> Einheitenspezifikation(Z0)0180020283000038
> Einheitenspezifikation(Z3)L1
>
> (root@localhost)/>lscfg -vl pdisk0
> EINHEIT POSITION BESCHREIBUNG
>
> pdisk0 30-70-1A7D-06-P Physisches SSA160-Plattenlaufwerk
> (36400 MB)
>
> Hersteller .................IBM
> Maschinentyp und Modell ....DMVC36B
> Teilenummer ................18P2199
> ROS-Ebene und ID ...........0061
> Seriennummer ...............F80F90A47K
> Stand der techn. Änderung ..F25900
> Einheitenspezifikation(Z2)CUSNA061
> Einheitenspezifikation(Z3)18P2199
> Einheitenspezifikation(Z4)01284
>
>
> Bye,
> Bernd
>
Hallo Bernd,

lsvpd extracts information from the classes PdAt, PdDv, CuVPD, CuAt and
CuDv. So I would guess that it is just a question of definition (by IBM) in
which class of the ODM the information is stored. lsattr on the other hand
might give more information than hardware and software levels of devices.
There might also be a difference between IBM products and other vendors (the
rmt0 in your example is an HP). For those reasonsI would not worry too much
about a different output.
If my assumptions are true it is a question of knowing in which class what
information to retrieve. (Btw, you seem to work for IBM - don't you have the
possibility to ask a developer directly? If you can - plse share the answer
with us :-))

The following screenshot shows that some information of the lsattr output is
stored not in the CuVPD but in the CuAt class:
# lsattr -El pdisk0
adapter_a ssa0 Adapter connection
False
connwhere_shad 002035E5291100D SSA Connection Location
False
[some snipped]
#
Now greping for the corresponding entires in the Customizable Attributes:
# odmget CuAt |grep -p pdisk0
CuAt:
        name = "pdisk0"
        attribute = "connwhere_shad"
        value = "002035E5291100D"
        type = "R"
        generic = "D"
        rep = "s"
        nls_index = 55

CuAt:
        name = "pdisk0"
        attribute = "adapter_a"
        value = "ssa0"
        type = "R"
        generic = "D"
        rep = "s"
        nls_index = 51
[ four more entries snipped here]

HTH,
Andreas

Relevant Pages