- Description has changed:

Diff:

~~~~

--- old
+++ new
@@ -1,3 +1,3 @@
 In ATCA architectures the PICMG 3.0 spec states that for non-recoverable 
temperature sensor assertions, the shelf manager will automatically shut down 
the FRU. This shows up as an "extraction pending" request from HPI. The PLM 
implementation cannot currently differentiate between the shelf manager 
bringing the FRU down, and the operator attempting an extraction by manual 
extraction. Both of these initiate the deactivation policy.
 
-The shelf manager automatically shutting down the FRU, in this case, can cause 
HE isolation to fail because the FRU has already begun shutting down when the 
readiness impact call is made.  In this case the deactivation request will 
fail. The code needs to handle the isolation failure and return TRY_AGAIN in 
this case.
+The shelf manager automatically shutting down the FRU, in this case, can cause 
HE isolation to fail because the FRU has already begun shutting down when the 
readiness impact call is made.  In this case the deactivation request will 
fail. The code currently correctly handles this case by setting the 
isolate-pending flag. But, some shelf managers will attempt to reactivate the 
FRU, once it has been deactivated. PLM should reject an activation if the HE is 
operationally disabled.

~~~~




---

** [tickets:#1751] PLM: handle isolation failures**

**Status:** review
**Milestone:** 4.6.2
**Created:** Tue Apr 12, 2016 07:05 PM UTC by Alex Jones
**Last Updated:** Tue Apr 12, 2016 07:59 PM UTC
**Owner:** Alex Jones


In ATCA architectures the PICMG 3.0 spec states that for non-recoverable 
temperature sensor assertions, the shelf manager will automatically shut down 
the FRU. This shows up as an "extraction pending" request from HPI. The PLM 
implementation cannot currently differentiate between the shelf manager 
bringing the FRU down, and the operator attempting an extraction by manual 
extraction. Both of these initiate the deactivation policy.

The shelf manager automatically shutting down the FRU, in this case, can cause 
HE isolation to fail because the FRU has already begun shutting down when the 
readiness impact call is made.  In this case the deactivation request will 
fail. The code currently correctly handles this case by setting the 
isolate-pending flag. But, some shelf managers will attempt to reactivate the 
FRU, once it has been deactivated. PLM should reject an activation if the HE is 
operationally disabled.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to