The HPI Open Session function, saHpiSessionOpen(), supports an option for specifying an implementation‐specific default domain. Since the Radisys implementation allows the client to run remotely, Radisys explicitly specifies the default domain on the client. The Radisys HPI client library (HCL) uses an environment variable (SAHPI_UNSPECIFIED_DOMAIN_ID) to specify the default domain ID. If an application uses this environment variable, it must be set to the IP address of the active Shelf Manager prior to using the library in the open session function. The Radisys HCL, provided as a shared library, implements and responds to all functions defined in the SAF HPI Specification. The HPI domain, resource, entity, and management instrument architecture is compliant with the SAF Mapping Specification. The mapping specification describes most of the resources and associated management instruments provided by the Radisys HPI implementation. Table 5 on page 54 lists Radisys‐ specific resources not found in the mapping specification.
4
Changing Shelf Settings Using HPI
The DomainId needed for opening HPI sessions on the Radisys platform’s HPI Interface is derived from the Shelf Manager’s IP address. See Writing HPI applications on page 57 for more information on deriving the DomainId parameter from IPv4 addresses.
The resource identifier parameter, ResourceId, for any resource in the Radisys platform's HPI Interface is formatted for easy preliminary identification of the entity being represented by
Table 5. Radisys-specific resources Resource
type1
Container
resource Description Entity (type, location)2 Lifetime3
Shelf Root This logical resource represents the shelf. There is exactly one created by each HPI server.
This resource is implemented as described in the mapping specification. However, the format of the entity instance of the shelf resource is Radisys-specific.
(SAHPI_ENT_ADVANCEDTCA_CHASSIS, Shelf Id) The entity instance of the shelf resource is the first 4 bytes of the shelf address, and is an encoding of the physical location of the shelf.
Static
SPM slot Shelf This logical resource represents the slot occupied by a shelf peripheral module (SPM).
(SAHPI_ENT_OEM_SPECIFIC, SPM Site Number) Static Virtual SPM
slot
Shelf This logical resource provides support for the logical virtual SPM in the shelf. The virtual SPM represents the functionality accessible only through the active SPM.
(SAHPI_ENT_OEM_SPECIFIC+2, 1) Static
SPM SPM slot This physical resource represents the SPM. (SAHPI_ENT_IO_BLADE, Site Number of SPM) Dynamic COM-E Slot SCM FRU
resource
This logical resource represents the COM-E module slot carried by the ATCA-2210.
(SAHPI_ENT_OEM_SPECIFIC+3, 1) Dynamic COM-E
Module
COM-E slot This physical resource represents the COM-E module that can be installed on an ATCA-2210 .
(SAHPI_ENT_ADD_IN_CARD, COM-E slot site number)
Dynamic RCM slot Shelf This physical resource represents the slot
occupied by the RCM.
(SAHPI_ENT_OEM_SPECIFIC, RCM Site Number) Static RCM RCM slot This physical resource represents the RCM. (SAHPI_ENT_IO_BLADE, RCM Site Number) Dynamic
Notes:
1. The resource types listed in this table may be different depending on the applicable modules. For example, the ATCA-7220 PPM does not have a COM-E slot or an SPM.
2. The site number used for the entity location refers to the site number associated with the physical slot listed in the AdvancedTCA address table contained in the shelf FRU information.
3. The Lifetime column specifies when the resource is added or removed from the resource presence table (RPT). Static resources are created on power-up and are never removed from the RPT. Dynamic resources are created when the resource is detected as present and deleted from the RPT when the resource is detected as absent.
4
Changing Shelf Settings Using HPI
55 The following is the ResourceId format used by shelf and Shelf Manager resources in the HPI resource presence table (RPT): The following is the ResourceId format used by FRU and slot resources in the RPT: XXYYZZ XX, YY, and ZZ each represent one byte in hexadecimal format, thus making the ResourceId 3 bytes long. Important: The ResourceId should not be used as the primary identification mechanism. HPI applications should use the entity path of a resource to properly identify its type and location. For details on entity path construction, see the SAF Mapping Specification. 0x01 Shelf resource. This represents the entire shelf and provides access to some shelf‐ related configuration such as the shelf address, Shelf Manager IP address, and so forth. This resource contains an inventory data record that also provides access to the shelf FRU information. 0x02 Shelf Manager resource. This represents the Shelf Manager and all functionality associated with the dedicated active Shelf Manager at IPMB address 0x20. XX Resource location. This is the location or instance number of the site, such as the physical slot number, associated with the entity represented by the resource. For AMCs, this is the AMC site number on a carrier. For non‐intelligent FRUs, it is the device‐specific site number on the proxy FRU. YY Resource type. This indicates the type of the entity being represented by the resource. For a FRU, this is the ATCA Site Type associated with the slot in which the FRU is installed. For debugging purposes, the Radisys resource types are identified in Resource types of slots and FRUs in the RPT on page 135. ZZ IPMB address of the entity represented by the resource. For details, see IPMB addresses of slots and FRUs on page 134. For AMCs and non‐intelligent FRUs, this is the IPMB address of the carrier or proxy FRU, respectively.