Error acknowledging alarms in Operator Console
Article ID: 274231
Updated On:
Products
Issue/Introduction
Suddenly it was not possible to acknowledge alarms from the OC, and error messages appeared in the ems.
The steps in the KB have been followed:
https://knowledge.broadcom.com/external/article/216257/ems-probe-leaking-memory-and-crashing-af.html
And alarms can now be acknowledged, but the error messages persist in the ems logs
Aug 30 00:36:02:780 [attach_socket, ems] java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.nimsoft.events.common.callbacks.AbstractCallbackService.invoke(AbstractCallbackService.java:39)
at com.nimsoft.events.common.callbacks.CallbackServiceMethodCallback.cbExecute(CallbackServiceMethodCallback.java:19)
at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.performCallback(NimServerSession.java:225)
at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.handleMessage(NimServerSession.java:178)
at com.nimsoft.nimbus.NimServerSession$NimServerSessionThread.run(NimServerSession.java:123)
Caused by: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'nametoip' name = '/xxx/xxx_PrimaryHub/xxx/sdgtw_message_hub'
at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:622)
Environment
Release : 20.3.3/ 20.4 CU8
probe : ems
Resolution
The root cause of this issue is that whenever we are loading/refreshing the alarm viewer in OC, it triggers an EMS callback which internally calls the sdgtw_message_hub probe which is deprecated now.
So whenever the callback is triggered from OC, it throws the error.
This will be fixed in the upcoming UIM/OC release i.e. 23.4.
Feedback
