On 12-Feb-15 6:10 AM, santosh satapathy wrote:
> Hi Praveen,
>
> I am currently using older version 4.3.1 in the customer LAB where this
> is happening. Could you please let me know if this issue is fixed in
> later versions 4.5? It is not easy to upgrade the versions to the latest
> and rollback in case does not work. It would be helpful if I get a prior
> confirmation if the issue is at all fixed in 4.5 before even raising the
> ticket.
Issue is not fixed in any version.
Thanks,
Praveen
>
> Best regards,
> Santosh
>
>
> On Mon, Jan 19, 2015 at 8:56 PM, praveen malviya
> <[email protected] <mailto:[email protected]>> wrote:
>
>
>
> On 20-Jan-15 2:27 AM, santosh satapathy wrote:
>
> Hi,
>
> I am noticing a early state change notification on ha state
> assigned for a
> SU comprising couple of components, when start the SU in order
> to monitor
> with ntfsubsrbibe -s.
>
> I get the notification when the HA state active is being
> assigned, rather
> then its assigned successfully after a 1 min time (see the logs high
> lighted for timing). In the SU the individual components
> responds to the
> setCSICallback when after making sure that they are fully done
> with the
> initialization.
>
> Please let me know if this the correct behavior?
>
> Please raise a ticket.
> AMF is sending this notification when it is creating SUSI
> relationship. It should be sent when the assignment is over.
>
> Thanks
> Praveen
>
>
> Payload node Logs:
> +++++++++++++++
>
> Jan 19 10:59:51 node1 osafamfnd[2192]: NO
> 'safSu=testsu,safSg=testsu,__safApp=TestApp' Presence State
> UNINSTANTIATED =>
> INSTANTIATING
> Jan 19 11:00:09 node1 osafamfnd[2192]: NO
> 'safSu=testsu,safSg=testsu,__safApp=TestApp' Presence State
> INSTANTIATING =>
> INSTANTIATED
> Jan 19 *11:00:10* node1 osafamfnd[2192]: NO Assigning
> 'safSi=testsu,safApp=TestApp' ACTIVE to
> 'safSu=testsu,safSg=testsu,__safApp=TestApp'
> Jan 19 *11:01:00* node1 osafamfnd[2192]: NO Assigned
> 'safSi=testsu,safApp=TestApp' ACTIVE to
> 'safSu=testsu,safSg=testsu,__safApp=TestApp'
>
>
> === Jan 19 *11:00:10 *- State Change ===
> eventType = SA_NTF_OBJECT_STATE_CHANGE
> notificationObject = "safSu=testsu,safSg=testsu,__safApp=TestApp"
> notifyingObject = "safApp=safAmfService"
> notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC___AMF.102 (0x66)
> additionalText = "Admin state of
> safSu=testsu,safSg=testsu,__safApp=TestApp
> changed"
> sourceIndicator = SA_NTF_MANAGEMENT_OPERATION
> State ID = SA_AMF_ADMIN_STATE
> New State: SA_AMF_ADMIN_UNLOCKED
>
> === Jan 19 *11:00:10* - State Change ===
> eventType = SA_NTF_OBJECT_STATE_CHANGE
> notificationObject = "safSi=testsu,safApp=TestApp"
> notifyingObject = "safApp=safAmfService"
> notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC___AMF.111 (0x6f)
> additionalText = "The Assignment state of SI
> safSi=testsu,safApp=TestApp
> changed"
> sourceIndicator = SA_NTF_OBJECT_OPERATION
> State ID = SA_AMF_ASSIGNMENT_STATE
> New State: SA_AMF_ASSIGNMENT_FULLY___ASSIGNED
>
>
>
>
> --
> Best Regards,
> Santosh
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Opensaf-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-users
