Doc:latest/sdkguide/shelfManagement - Revision history

Stone: /* AMF Hardware Manager API Example */

2013-06-28T19:24:20Z

‎AMF Hardware Manager API Example

Stone: /* SAFplus Hardware Management */

2013-06-28T19:23:48Z

‎SAFplus Hardware Management

Stone at 19:17, 28 June 2013

2013-06-28T19:17:45Z

Stone: Created page with "== SAFplus Hardware Management == SAFplus can be integrated with an ATCA chassis manager via an additional product called the SAFplus Platform Support Package. However, for ..."

2013-06-28T19:16:37Z

Created page with "== SAFplus Hardware Management == SAFplus can be integrated with an ATCA chassis manager via an additional product called the SAFplus Platform Support Package. However, for ..."

New page

== SAFplus Hardware Management ==

SAFplus can be integrated with an ATCA chassis manager via an additional product called the SAFplus Platform Support Package.

However, for non-ATCA systems, SAFplus provides some simple APIs to allow your custom hardware manager to report errors to the AMF. If your hardware manager can report a sensor error such as a severe overtemperature event to the AMF, this will allow the AMF to transition AIS (software) services onto a redundant blade before a failure actually occurs.

=== AMF Hardware Manager API ===

The AMF API is located in the header file "clCmIpi.h", and implementation in the libmw.a library. This API is only available to SAF-aware applications that have successfully initialized AMF services (saAmfInitialize API). The following events can be communicated to the AMF:

*'''CL_CM_BLADE_SURPRISE_EXTRACTION'''
The node was abruptly removed

*'''CL_CM_BLADE_REQ_EXTRACTION'''
The node's power button was pushed or latch was opened -- extraction is imminent.

*'''CL_CM_BLADE_REQ_INSERTION'''
The node's latch was closed

*'''CL_CM_BLADE_NODE_ERROR_REPORT'''
Your software has determined (via a sensor read) that failure is imminent. Software applications should be transitioned away from this node.

*'''CL_CM_BLADE_NODE_ERROR_CLEAR'''
The node has returned to nominal behavior, software applications may be returned to this node.

This event type is combined with information identifying the FRU (node) that has the problem:

typedef struct
{
/** The event (described above) */
ClCmCpmMsgTypeT cmCpmMsgType;
/** The slot number (node identifier) with the problem */
ClUint32T physicalSlot;
/** For future use */
ClUint32T subSlot ;
/** Not to be used by AMF, can be used by the hardware manager to identify the problem */
ClUint32T resourceId;
} ClCmCpmMsgT;

And passed to the AMF via a simple API:

extern ClRcT clCpmHotSwapEventHandle(ClCmCpmMsgT *pCmCpmMsg);

The AMF will use this information to move software applications on nodes with no issues to standby nodes, or to transition applications back to nodes that have returned to a nominal state.

@@ Line 52: / Line 52: @@
 The following routine generates a node error report or error clear based on the passed "asserted" variable.
 <code>
 void clCmInformAMFBySlot(ClUint32T slotId, ClBoolT asserted)

@@ Line 27: / Line 27: @@
 This event type is combined with information identifying the FRU (node) that has the problem:
 typedef struct
+{
@@ Line 38: / Line 39: @@
      ClUint32T resourceId;
 } ClCmCpmMsgT;
+</code>
 And passed to the AMF via a simple API:
 extern ClRcT clCpmHotSwapEventHandle(ClCmCpmMsgT *pCmCpmMsg);
 The AMF will use this information to move software applications on nodes with no issues to standby nodes, or to transition applications back to nodes that have returned to a nominal state.

@@ Line 7: / Line 7: @@
 === AMF Hardware Manager API ===
-The AMF API is located in the header file "clCmIpi.h", and implementation in the libmw.a library.  This API is only available to SAF-aware applications that have successfully initialized AMF services (saAmfInitialize API).  The following events can be communicated to the AMF:
+The AMF API is located in the header file "clCmIpi.h", and implementation in the libmw.a library.  This API is only available to SAF-aware applications that have successfully initialized AMF services (via the saAmfInitialize API).  The following events can be communicated to the AMF:
 *'''CL_CM_BLADE_SURPRISE_EXTRACTION'''