Thanks for the info. We are using Lync 2010. and its related MP view does not show any view named Watcher Node. However I tried reinstalling agent on the this server. Would see if that picks up something,
On Wed, Oct 30, 2013 at 10:49 AM, Dominique Dusabeyezu < [email protected]> wrote: > Hi, > > > > Provided you are using 2013, under Watcher Node state inside your Lync MP > view (Call Reliability and Media Quality). When you select the server and > check the detail view, can you see your report server instance? > > Have you installed the lync monitoring reports after initially discovering > your front end servers? If yes, I suggest you remove the agent from the > watcher node and rediscover it. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Srikanth Thumma > *Sent:* Wednesday, October 30, 2013 4:42 PM > *To:* [email protected] > *Subject:* [msmom] Reg. SCOM - Lync 2010 MP Alert > > > > > > Hi Alert, > > Recently we observed following description in one of the Lync alert: > > The Lync Admin was particularly interested in the text highlightened in > yellow. (i.e > > Reporting URL is not available because the reporting pack is not installed. > > To see trouble-shooting reports, please install the reporting pack) .. > > > > I was told *Lync Server Monitoring Reports * are already installed from > their side. And question is how to get that link integrated into these > Alerts. > > I could not find any thing specific to this in Lync MP guide too. > > Any advise would be greatly appreciated. > > > ============================================================== > Alert Name: Call reliability alert for Conference calls > > Source: Microsoft.LS.2010.WatcherNode.CDR > > Alert description: > > Alert description: Audio calls ( with Diagnosis code '25006' ) are failing > at higher than expected rates. > > > > Here are the details for this Call Failure Alert: > > Diagnosis Code = 25006 > > Diagnosis Reason = The callee's primary pool failed to respond in a timely > manner. > > Diagnosis Description = A call failed because the callee's pool failed to > respond. This can happen if the pool is busy or was taken offline while > the request was being processed. Administrators should check the events on > the callee's pool for potential load or capacity issues. Administrators > should also check the toplogy for potential network related errors. > > Media Type = conf:audio-video > > Distinct Users Impacted = 6 > > Total Calls = 408 > > Failed Calls = 7 > > Failure Percentage = 1.7156862745098 > > > > Reporting URL is not available because the reporting pack is not installed. > > To see trouble-shooting reports, please install the reporting pack. > > > > You can also refer to the 'Product Knowledge' and the 'Alert Context' tab > on Alert Properties view for more information and possible resolutions. > > > ========================================== > > Regards, > Sri > > > > ------------------------------ > > > ---------------------------------------------------------------------------------- > Tshwane University of Technology > > ---------------------------------------------------------------------------------- > This email is sent and received in terms of the Electronic > Communications Policy of Tshwane University of Technology. > In line with this policy, this email is private, privileged and > confidential. The full text of the Electronic Mail Disclaimer > can be seen on the TUT web site at > http://www.tut.ac.za/Other/disclaimer/Pages/default.aspx > or obtained by phoning (012) 382-5911 > >
