Hi,
SA_AMF_NTFID_SI_UNASSIGNED is sent when SI is transitioned from
assigned state to unassigned state[As per Specs: the service instance
transitioned to the unassigned assignment state]. When SI is added, then it
doesn't transition, but comes into being in unassigned state. So, alarm is not
sent. This is expected behaviour.
Thanks
-Nagu
> -----Original Message-----
> From: Kang-sen Lu [mailto:[email protected]]
> Sent: 08 August 2014 18:15
> To: [email protected]
> Subject: [users] About SI_UNASSIGNED alarm generation
>
> I am new to opensaf.
>
> I have a question about SI_UNASSIGNED alarm generation.
>
> If a SI is new added, and there were no SUs to be assigned to SI.
>
> The SI will be in SI_UNASSIGNED state. But there is no alarm being sent out
> through NTF. Is this the expected behavior?
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and search
> up to 200,000 lines of code with a free copy of Black Duck Code Sight - the
> same
> software that powers the world's largest code search on Ohloh, the Black Duck
> Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> _______________________________________________
> Opensaf-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/opensaf-users
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
