Hi,
OpenSAF currently only works with HPI-A. The HPI-A daemon and libraries used to
test OpenSAF is not the standard release of openhpi, but a modified version of
it. It would be easier to wait until OpenSAF supports HPI-B to integrate it
with your ATCA chassis.
In the hpi daemon configuration you can specify the chassis
(/etc/openhpi/openhpi.conf):
OPENHPI_ON_EP = "{ADVANCEDTCA_CHASSIS,0}"
Which could be set to:
OPENHPI_ON_EP = "{SYSTEM_CHASSIS,2}"
In the hw deployment section of the NCSSystemBOM.xml file you specify the
entity type for the chassis, system controller, and payloads. Take a look of
the output "hpireset" to determine the entity type to use for the payloads and
system controller that you should use in the NCSSystemBOM.xml file. For example:
[94] {ADVANCEDTCA_CHASSIS,0}{PHYSICAL_SLOT,16}{SWITCH_BLADE,0} ATCA-F101 IPMC
[93] {ADVANCEDTCA_CHASSIS,0}{PHYSICAL_SLOT,7}{PICMG_FRONT_BLADE,0} ATCA-7221
In this case SAHPI_ENT_PHYSICAL_SLOT should be used as the entity type for the
system controller (F101 board) as well as the payload card (7221 board).
Other elements in the chassis like fans, power supplies, shelf manager, etc,
are not part of the hw deployment section on the NCSSystemBOM.xml file and will
not be in the AVM database, therefore will never match.
Regards,
Gus Leal-Isla
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of hu jing dong(???)
Sent: Monday, October 08, 2007 6:29 PM
To: [email protected]
Subject: [Users] About Entity Path
Hi all,
1, In function avm_octet_string_2_entity_path(), entity_path->Entry[] is filled
with each pair of {entity_type, entity_instance} in string ep[].
However, if the entity_instance equals zero, the line:
entity_path->Entry[count++].EntityInstance = entity_instance;
won't be executed, therefore count remains (not adds one), and the next pair of
{entity_type, entity_instance} will overwrite the prior. Is it right?
2, Now we try to apply OpenSaf on ATCA chassis. HSM gets the HPI RPT entry by
calling saHpiRptEntryGet, and the "Entity Path" of entry achieved is like
following:
{SAHPI_ENT_ROOT, 0}[repeats several times] {SAHPI_ENT_RACK, 0}
{SAHPI_ENT_ADVANCEDTCA_CHASSIS, 0} {FRCHPI_ENT_SHELF_MANAGER_SLOT, 1}
{FRCHPI_ENT_PICMG_SHELF_MANAGEMENT_CONTROLLER,8}.
Whereas AvM builds hardware deployment database from NCSSystemBOM.xml with the
"Entity Path" like:
{0,0}[repeats several times] {SAHPI_ENT_ROOT, 0} {SAHPI_ENT_SYSTEM_CHASSIS, 6}
...
The two cannot match. So, how to configure hardware deployment in
NCSSystemBOM.xml for ATCA chassis?
Thanks.
Hu Jingdong
_______________________________________________
Users mailing list
[email protected]
http://list.opensaf.org/maillist/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://list.opensaf.org/maillist/listinfo/users
