[cisco-voip] Monitoring CallManager

[Ryan West]

Ed,

What useful information are you pulling, if any, from appliance based CM deployments?  I found the OID’s to be rather lacking.  Are you using any SOAP XML queries to populate your graphs, if so, could you share?

Thanks!

-ryan

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ed Leatherman
Sent: Wednesday, August 27, 2008 12:07 PM
To: Mike Brooks
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Monitoring CallManager

FWIW I'm using splunk for sysloging.. more of an after-the-fact research tool than a monitoring tool for us but the search capabilities are very nice and it was relatively easy to setup. Its free as long as your not going to be logging gobs of stuff at it.

RTMT, What's UP, Cacti, IP SLA running across some key links, etc otherwise like alot of folks.

Tried ops manager in its previous ciscoworks incarnation and really didnt like it. Not sure how its improved yet under the new product name.

I only have 2 clusters to manage though so ymmv.
On Fri, Aug 22, 2008 at 9:34 AM, Mike Brooks <2xccie2b at gmail.com<mailto:2xccie2b at gmail.com>> wrote:
Hi everyone,

What are the most common methods used to monitor a large enterprise
VOIP environment (multiple clusters) ?  All clusters are running CM
5.x or 6.x (locked down appliances).

Ops Manager ?
RTMT ?
SNMP MIBs ?
...etc

Has anyone had any success with ops manager ?  I have had nothing but
problems with ops manager.  Your suggestions/input would be greatly
appreciated.

Regards,

Mike Brooks
CCIE#16027 (R&S)
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip



--
Ed Leatherman
Assistant Director, Voice Services
West Virginia University
Telecommunications and Network Operations
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080827/e05542b9/attachment.html>