Max, Let me check with the dev team, but at my first glance it reads like an SSH session, was reset by a SSH client. Doesn’t seem like a big deal, but I will check to make sure.
+Chris TME – Spark Call and MediaSense From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Max Harmony Sent: Thursday, May 05, 2016 11:28 AM To: Cisco VOIP <cisco-voip@puck.nether.net> Subject: [cisco-voip] CRITICAL:Active(Not Acknowledged):SyslogSeverityMatchFound:Alarm ID:41383874 - Media Sense GoodMorning All, I received this error and being that I am kind of new to Media Sense, was wondering if anyone is familiar with this error message from Mediasense, please can you advice how to troubleshoot? Device Category MEDIASENSE Alarm Details<https://10.129.13.29/emsam/index.html#pageId=com_cisco_ifm_web_page_alarms&queryParams=Id=41383874&forceLoad=true> Alarm Time Stamp 2016-May-03 20:53:00 EST Alarm Type Name SyslogSeverityMatchFound Alarm Status Active(Not Acknowledged) Alarm Severity CRITICAL Alarm Description SyslogSeverityMatchFound::State=unacknowledged;Component=xxxx;Description= At Tue May 03 21:52:06 EDT 2016 on nodexxxxx; the following SyslogSeverityMatchFound events generated: SeverityMatch : Critical MatchedEvent : May 3 21:51:35 CMS-2 authpriv 2 sshd[1757]: fatal: Read from socket failed: Connection reset by peer [preauth] AppID : Cisco Syslog Agent ClusterID : NodeID : CMS-2 TimeStamp : Tue May 03 21:51:35 EDT 2016 Recommended Action Contact your Cisco support representative for more assistance. Alarm Acknowledged NO
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
