I'm using OpenSAF 4.3.1. I cannot upgrade. We are experiencing a problem.
When AMF begins "attempting" to assign CSI assignments it updates the runtime attributes and associations to show assigned and active BEFORE the active CSI has been accepted by the Component. So if I query the CSI using amf-state csiass before the CSI has been accepted by the Component smf-state will show it assigned and active. The same his for the SI. The SI will be assigned to the SU as active BEFORE all the CSI assignments have been accepted by the components in that SU. I checked the runtime state with both immlist and amf-state. Both were consistent in being incorrect. Interestingly enough the opensaf log entries show the correct behavior. The log entry indication the SI was assigned to the SU is not logged until all CSI assignments have been accepted. I assume this is probably a know issue, but is the anyway at all for me to query something that will tell me when the active SI has been assigned for "real"? Components are all SA Aware and using the no redundancy redundancy model. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Opensaf-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-users
