SLErrors: Alarms that don’t always reach the destination

Solved839 viewsalarms ERR SLAlarmForwarding slerrors SLNet
1
0 Comments

Hi, all!

I am receiving some reports from my development area that an "in house app" is not receiving all the alarms.
I observe that if the conditions defined in the correlation were met, but for some strange reason on some occasions my correlations were not triggered.

Tracking by alarm id within SLErrors of the DMA I found the following error log:

2021/07/26 11:19:21.887|SLAlarmForwarding.txt|SLNet.exe|LogError|ERR|0|34|Notify SNMP Agent Failed: Alarm(Id: 6360937) for Managers (ids): with exception: System.Runtime.Remoting.RemotingException: Requested Service not found

Server stack trace:
at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Interop.SLSnmpAgent.ISNMPAgent.Notify(Int32 eType, Object varInfo1, Object varInfo2)
at Skyline.DataMiner.Net.AlarmForwarding.AlarmForwardingManager.HandleStackItemNewAlarmEvent(StackItemAlarm stackItemAlarm, List`1 selectedTargets, Boolean forceSend, Dictionary`2 oldTargets)

I would like to be clear if the error message was generated as a response from the destination or was caused by my origin.
I hope you can help me with this issue

Regards

Christhiam Aaron Calatayud Franco [DevOps Advocate] Selected answer as best 4th August 2021

1 Answer

1
1.39K 1 Comment

Hi Christhiam Aaron,

This is a weird error to encounter. The error indicates there is an issue in the communication between the local SLNet and the Local SNMPAgent-process. From an initial glance it looks like the process can correctly setup the initial communication, but gets blocked during a notify-call. The communications happens through .net remoting and since both processes run locally this should be fairly reliable.

When the issue occurs can you check the following

-Are both the SLNet and SLSNMPAgent process running and healthy.

-Is there an Antivirus or firewall that could block communication

-Are there errors in the Event viewer that are related to this.

Christhiam Aaron Calatayud Franco [DevOps Advocate] Selected answer as best 4th August 2021
Christhiam Aaron Calatayud Franco [DevOps Advocate] commented

Okay, thank you very much for the observation
Regards