>>The only thing we can make sure that will come in order is NCSMDS_DOWN and 
>>NCSMDS_UP.
>>So I still think that MDS should clear the down timer when receiving 
>>NCSMDS_UP.

You mean  NCSMDS_DOWN and NCSMDS_UP MDS events  are kept on separate sockets 
(Dsock and BSRsock) ?

or

NCSMDS_DOWN/NCSMDS_UP MDS events  and  "withdrawn event timer"  events   are 
kept on separate sockets (Dsock and BSRsock) ?

I understand you  observations as follows :

In your setup, some times you are  receiving  the  NCSMDS_UP  for IMMA  earlier 
than
the previous "withdrawn event timer" expire, which was started  to remove the 
NCSMDS_DOWN  for the same  IMMA  info as new IMMA ,
which is being kept on different socket is getting processed after   the new 
NCSMDS_UP  for IMMA ( same adest+svc_id ) and  removing the PID information of 
the new  same adest+svc_id.

is that right ?




---

** [tickets:#1825] MDS: When saImmOmInitialize was invoked, MDS sent ‘pid = 0’ 
in MDS_CALLBACK_RECEIVE_INFO.**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Fri May 13, 2016 12:34 PM UTC by Rafael
**Last Updated:** Thu May 19, 2016 10:46 AM UTC
**Owner:** nobody
**Attachments:**

- 
[sc2_mds.log](https://sourceforge.net/p/opensaf/tickets/1825/attachment/sc2_mds.log)
 (2.6 MB; text/x-log)


This happens only some of the time. 

First this is called from an application:

    saImmOmInitialize(immHandle, NULL, &version)

Then the system log shows this error:

    May 13 02:31:53 sc2 osafimmnd[6042]: WA immnd_evt_proc_imm_init: PID 0 
(7150) for 2020fb1d13cb8, MDS problem?
     May 13 02:31:53 sc2 osafimmnd[6042]: WA immnd_evt_proc_imm_init: PID 0 
(7150) for 2020fb1d13cb8, MDS problem?
     May 13 02:31:55 sc2 osafimmnd[6042]: NO Ccb 176 COMMITTED (LDE)
     May 13 02:31:55 sc2 osafimmnd[6042]: WA immnd_evt_proc_imm_init: PID 0 
(7150) for 2020fb1d13cb8, MDS problem?
     May 13 02:31:55 sc2 osafimmnd[6042]: WA immnd_evt_proc_imm_init: PID 0 
(7150) for 2020fb1d13cb8, MDS problem?


---

Sent from sourceforge.net because [email protected] 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.
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to