Hi Dojo,
I have an enhanced service protocol that calculates his alarm summary status based on the active alarms of this children. Each time the alarms of this children are clearing, I see the following error in the logs:
2024/08/23 17:09:31.939|SLProtocol - 14676 - 3 - SERVICE NAME|33516|CProtocol::PushAlarmStructure|ERR|-1|SLA (106201/83) not active yet, alarm dropped: VT_ARRAY|VT_VARIANT (7)
0 VT_I4 : 29224562
1 VT_I4 : -1
2 VT_I4 : 0
3 VT_ARRAY|VT_BSTR (69) : 36;29224669;106201;22;4238;31;2024-08-23 17:09:21;0.000000;11;5;5;...
4 VT_BSTR : 106201/82/10...
2024/08/23 17:09:31.955|SLProtocol - 14676 - 3 - SERVICE NAME|11524|CProtocol::PushAlarmStructure|ERR|-1|SLA (106201/83) not active yet, alarm dropped: VT_ARRAY|VT_VARIANT (7)
0 VT_I4 : 29224553
1 VT_I4 : -1
2 VT_I4 : 0
3 VT_ARRAY|VT_BSTR (69) : 36;29224678;106201;22;4238;31;2024-08-23 17:09:21;0.000000;11;5;5;...
4 VT_BSTR : 106201/82/10...
2024/08/23 17:09:31.956|SLProtocol - 14676 - 3 - SERVICE NAME|10756|CProtocol::PushAlarmStructure|ERR|-1|SLA (106201/83) not active yet, alarm dropped: VT_ARRAY|VT_VARIANT (7)
0 VT_I4 : 29224552
1 VT_I4 : -1
2 VT_I4 : 0
3 VT_ARRAY|VT_BSTR (91) : 36;29224679;106201;22;4238;34;2024-08-23 17:09:21;0.000000;11;5;5;...
4 VT_BSTR : 106201/82/7...
2024/08/23 17:09:31.984|SLProtocol - 14676 - 3 - SERVICE NAME|22280|CProtocol::PushAlarmStructure|ERR|-1|SLA (106201/83) not active yet, alarm dropped: VT_ARRAY|VT_VARIANT (7)
0 VT_I4 : 29224568
1 VT_I4 : 1
2 VT_I4 : 1
3 VT_ARRAY|VT_BSTR (54) : 36;29224684;106201;83;1000;35;2024-08-23 17:09:31;1.000000;12;1;5;...
4 VT_BSTR : 106201/82/-1...
Are you aware of what the error signifies?
The error prevents the service alarm calculation, leaving the main service in a critical state, while the individual service elements revert to normal.
Hi Frederic,
This sounds like it will need a very specific investigation, would it be possible to create a collaboration task please. In case, there is something interesting in this for our community, we can then link back here.