Doc:latest/evalguide/cmPlugin - Revision history

Prasad: /* Usage of CM-Plugin */

2014-11-13T06:43:02Z

‎Usage of CM-Plugin

Prasad: /* Building the CM-Plugin model and controlling Events in run-time */

2014-11-13T06:28:52Z

‎Building the CM-Plugin model and controlling Events in run-time

Natesh: /* Example Code: */

2013-10-15T15:02:26Z

‎Example Code:

Natesh: /* How to Run cmPlugin model */

2013-10-15T15:01:14Z

‎How to Run cmPlugin model

Natesh: /* Example Code: */

2013-10-15T14:59:41Z

‎Example Code:

Natesh at 11:47, 15 October 2013

2013-10-15T11:47:54Z

Natesh at 09:40, 11 October 2013

2013-10-11T09:40:42Z

Natesh: /* Advanced Usage: */

2013-10-11T09:23:37Z

‎Advanced Usage:

Natesh at 11:59, 10 October 2013

2013-10-10T11:59:48Z

Natesh: /* How to Run cmPlugin model */

2013-10-10T11:46:46Z

‎How to Run cmPlugin model

@@ Line 32: / Line 32: @@
+     {
          /* Define the policy to Allow, Block or Change the events here */
-         if ((event->EventType == SAHPI_ET_SENSOR) && (event->EventDataUnion.SensorEvent.SensorNum == 4))
+         if ((event->EventType == SAHPI_ET_SENSOR) && (event->Severity==SAHPI_MAJOR))
+         {
               event->Severity = SAHPI_MINOR; /* Changing event severity to minor */
+         }
-         else if ((event->EventType == SAHPI_ET_SENSOR) && (event->Source == 0x10))
+         else if ((event->EventType == SAHPI_ET_SENSOR) && (event->Severity==SAHPI_MINOR))
+         {
-              event->Severity = SAHPI_MINOR; /* Changing event severity to minor */
+              event->Severity = SAHPI_MAJOR; /* Changing event severity to minor */
+         }
          return CL_OK;
@@ Line 45: / Line 45: @@
 |}
-In the above example, the Sensor Events from Sensor #4 is changed to lower severity, so that the event is given lower importance or can be ignored and other events which are of importance can be received and processed by Application.
+In the above example, the Sensor Events from high severity is changed to lower severity, so that the event is given lower importance or can be ignored and other events which are of importance can be received and processed by Application.
 ===How to Run cmPlugin model===

@@ Line 15: / Line 15: @@
 The example code containing Application and CM-Policy is available in
-'''[https://github.com/OpenClovis/SAFplus-Platform-Support-Package/tree/master/src/example/cmplugin  PSP/src/example]'''
+'''[https://github.com/OpenClovis/SAFplus-Platform-Support-Package/tree/master/src/example/CmPlugin  PSP/src/example]'''
 ====Usage of CM-Plugin====

@@ Line 167: / Line 167: @@
              (event.EventDataUnion.HotSwapEvent.HotSwapState != event.EventDataUnion.HotSwapEvent.PreviousHotSwapState))
+         {
-              event->Severity = SAHPI_MAJOR; /* Changing event severity to minor */
+              event->Severity = SAHPI_MAJOR; /* Changing event severity to major */
+         }
          else
+         {
-              event->Severity = SAHPI_MINOR; /* Changing event severity to major */
+              event->Severity = SAHPI_MINOR; /* Changing event severity to minor */
+         }
          return CL_OK;

@@ Line 54: / Line 54: @@
 <li>Start the SAFplus Platform on deployed node <code><pre>
-  # cd /root/asp/
+  # cd /root/SAFplus/
-  # ./etc/init.d/asp start</pre></code>
+  # ./etc/init.d/safplus start</pre></code>
 <li>Generate event using HPI Event Simulator OR through actual hardware <code><pre>
-  # cd /root/asp/bin
+  # cd /root/SAFplus/bin
   # ./hpithres</pre></code>
 </ol>

@@ Line 145: / Line 145: @@
              (event.EventDataUnion.SensorEvent.Assertion == SAHPI_TRUE))
+         {
-              event->Severity = SAHPI_MAJOR; /* Changing event severity to minor */
+            return CL_ERR_OP_NOT_PERMITTED; /* Event is skipped and is not forwarded to application */
+         }
          return CL_OK;

@@ Line 46: / Line 46: @@
 In the above example, the Sensor Events from Sensor #4 is changed to lower severity, so that the event is given lower importance or can be ignored and other events which are of importance can be received and processed by Application.
 ===How to Run cmPlugin model===
@@ Line 116: / Line 115: @@
 |Event Specific Data.
 |}

← Older revision		Revision as of 09:40, 11 October 2013
Line 78:		Line 78:

	Severity : SAHPI_MINOR, SAHPI_MAJOR, SAHPI_CRITICAL		Severity : SAHPI_MINOR, SAHPI_MAJOR, SAHPI_CRITICAL
		+
		+	===Details in Event Union===
		+
		+	{\| cellspacing="0" border="1" align="center"
		+	\|+align="bottom"\| '''SA Forum APIs with the SAFplus Platform equivalent'''
		+	\|- style="color:black;background-color:#ffffaa;" align="center"
		+	!SensorEventT
		+	!Event Request Message
		+	\|-
		+	\|SensorNum
		+	\|Sensor #
		+	\|-
		+	\|SensorType
		+	\|Type of Sensor (Ex: Voltage, Temp.)
		+	\|-
		+	\|EventState
		+	\|SAHPI_ES_LOWER_MINOR
		+	\|-
		+	\|
		+	\|SAHPI_ES_LOWER_MAJOR
		+	\|-
		+	\|
		+	\|SAHPI_ES_LOWER_CRITICAL
		+	\|-
		+	\|
		+	\|-
		+	\|
		+	\|SAHPI_ES_UPPER_MINOR
		+	\|-
		+	\|
		+	\|SAHPI_ES_UPPER_MAJOR
		+	\|-
		+	\|
		+	\|SAHPI_ES_UPPER_CRITICAL
		+	\|-
		+	\|SensorSpecific
		+	\|Event Specific Data.
		+	\|}

← Older revision		Revision as of 09:23, 11 October 2013
Line 65:		Line 65:

	===Advanced Usage:===		===Advanced Usage:===
−	HPI layer can handle events for various kinds originated for Resource Details, Domain events, Sensor, Hot-Swap, Watchdog, Software-Events, OEM, User events, Dimi, Fumi events. While developing any event specific change either in Middleware or in Application, the specific event is allowed from PSP and is received by Application and rest of events are suppressed.	+	The Shelf Manager in AdvancedTCA/MicroTCA is notified about health and management status changes in the shelf via standard IPMI event messages that are forwarded to the active Shelf Manager. IPM Controllers are configured to generate event messages when they detect a significant condition getting asserted or deasserted in the system. This includes messages for events such as ‘temperature threshold exceeded’, ‘voltage threshold exceeded’, ‘power fault’, ‘watchdog expired’, etc. IPMI event messages are typically associated with a Sensor. The type and event type of the Sensor associated with an event helps the Shelf Manager and HPI User decide on actions to be taken on account of that event.
		+
		+	HPI layer can handle events for various kinds which can be originated for Resource Details, Domain events, Sensor, Hot-Swap, Watchdog, Software-Events, OEM, User events, Dimi, Fumi events. While developing any event specific change either in Middleware or in Application, the specific event is allowed from PSP and is received by Application and rest of events are suppressed.
		+
		+	The event received is containing fields which indicate
		+
		+	Source : ResourceId of FRU
		+
		+	EventType : Sensor Type
		+
		+	TimeStamp : Time when the HPI Server receives the event.
		+
		+	Severity : SAHPI_MINOR, SAHPI_MAJOR, SAHPI_CRITICAL

@@ Line 45: / Line 45: @@
 |}
-* In the above example, the Sensor Events from Sensor #4 is changed to lower severity, so that the event is given lower importance or can be ignored and other events which are of importance can be received and processed by Application.
+In the above example, the Sensor Events from Sensor #4 is changed to lower severity, so that the event is given lower importance or can be ignored and other events which are of importance can be received and processed by Application.
@@ Line 61: / Line 61: @@
   # cd /root/asp/bin
   # ./hpithres</pre></code>
 The logs are available in var/log/sys.latest and application_name.latest.
-===What you can learn===
+===Advanced Usage:===
-How
+HPI layer can handle events for various kinds originated for Resource Details, Domain events, Sensor, Hot-Swap, Watchdog, Software-Events, OEM, User events, Dimi, Fumi events. While developing any event specific change either in Middleware or in Application, the specific event is allowed from PSP and is received by Application and rest of events are suppressed.