Re: [Openhpi-devel] HPI to ATCA mapping

[Benoit G. <gu...@th...>]

Renier Morales wrote:

>
> The implementation is supposed to give you a compliant HPI/ATCA tree.=20
> Specifically, the OpenHPI plugin (ipmi, ipmidirect, snmp_bc, etc.)=20
> talking to the platform you are interested in is the one that gives=20
> you the tree.

I guess I do something wrong, or I misunderstand the ATCA model. The=20
discovered platform is scanned through RMCP requests sent to the=20
platform Shelf Manager.

I have a /etc/openhpi/openhpi.conf file containing this:

## Section for ipmidirect plugin using RMCP:
handler libipmidirect {
#        entity_root =3D "{SYSTEM_CHASSIS,7}"
        entity_root =3D "{ADVANCEDTCA_CHASSIS,7}"
        name =3D "lan"         # RMCP
        addr =3D "shelfman"   # Host name or IP address
        port =3D "623"         # RMCP port
        auth_type =3D "none"   # none, md2, md5 or straight
        auth_level =3D "admin" # operator or admin
#        username =3D ""
#        password =3D ""
        MultipleDomains =3D "no"  # "yes" creates a domain for this handl=
er
        DomainTag =3D "Chassis 1" # Used if MultipleDomains=3D"yes"
        logflags =3D ""      # logging off
}

hpitop gives a tree like this:

{ADVANCEDTCA_CHASSIS,7}
    |
    +--- {ADVANCEDTCA_CHASSIS,7}{SHELF_MANAGER,0}{OEM_SYSINT_SPECIFIC,0}
    |    |__ Sensor Num: 0, Type: OEM_SENSOR, Category: SENSOR_SPECIFIC,=20
Tag: FRU 0 HOT_SWAP
    |    |__ Sensor Num: 1, Type: OEM_SENSOR, Category: SENSOR_SPECIFIC,=20
Tag: IPMB LINK
    |    |__ Sensor Num: 120, Type: TEMPERATURE, Category: THRESHOLD,=20
Tag: Chassis Temp 1
    |    |__ Sensor Num: 121, Type: TEMPERATURE, Category: THRESHOLD,=20
Tag: Chassis Temp 2
    |    |__ Sensor Num: 132, Type: RESERVED2, Category:=20
SENSOR_SPECIFIC, Tag: BMC Watchdog
    |    |__ Sensor Num: 133, Type: SYSTEM_EVENT, Category:=20
SENSOR_SPECIFIC, Tag: SYSTEM EVENT
    |    |__ Watchdog Num: 0, Tag: Watchdog
    |
    +--- {ADVANCEDTCA_CHASSIS,7}{SHELF_MANAGER,0}{OTHER,1}
    |    |__ Sensor Num: 2, Type: OEM_SENSOR, Category: SENSOR_SPECIFIC,=20
Tag: FRU 1 HOT_SWAP
    |    |__ Sensor Num: 129, Type: ENTITY_PRESENCE, Category:=20
SENSOR_SPECIFIC, Tag: Shelf FRU # 1
    |    |__ Sensor Num: 130, Type: ENTITY_PRESENCE, Category:=20
SENSOR_SPECIFIC, Tag: Shelf FRU # 2
    |    |__ Inventory Idr Num: 1, Num Areas: 4, Tag: Shelf FRU Info
    |
    +--- {ADVANCEDTCA_CHASSIS,7}{SHELF_MANAGER,0}{OTHER_CHASSIS_BOARD,2}
    |    |__ Sensor Num: 4, Type: OEM_SENSOR, Category: SENSOR_SPECIFIC,=20
Tag: FRU 3 HOT_SWAP
    |    |__ Sensor Num: 161, Type: OEM_SENSOR, Category:=20
SENSOR_SPECIFIC, Tag: Slot 2 State
    |
    +--- {ADVANCEDTCA_CHASSIS,7}{SHELF_MANAGER,0}{OTHER_CHASSIS_BOARD,8}
    |    |__ Sensor Num: 10, Type: OEM_SENSOR, Category:=20
SENSOR_SPECIFIC, Tag: FRU 9 HOT_SWAP
    |    |__ Sensor Num: 167, Type: OEM_SENSOR, Category:=20
SENSOR_SPECIFIC, Tag: Slot 8 State

I thought it should be something like this:

    |
    +--- {ADVANCEDTCA_CHASSIS,7}{SHELF_MANAGER_SLOT,1}{SHELF_MANAGER,0}
    |    ...
    +---=20
{ADVANCEDTCA_CHASSIS,7}{SHELF_FRU_DEVICE_SLOT,2}{SHELF_FRU_DEVICE,1}
    |
    +---=20
{ADVANCEDTCA_CHASSIS,7}{SHELF_FRU_DEVICE_SLOT,8}{SHELF_FRU_DEVICE,2}


What do you think? I use release 0.2.8.

Regards,

--=20
Beno=EEt Guillon                gu...@th...
TCT/3S                        tel. : 33 (0)4 98 16 33 90
=20
THALES COMPUTERS