[cisco-voip] using Nagios to monitor MCS servers

[Lelio Fulgenzi]

RTMT is pull when you're using it, but when you setup alarms and stuff, it's more like timed pulls. 

OK, not really a pull. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Jason Fuermann" <JBF005 at shsu.edu> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, "Abebe Amare" <abucho at gmail.com> 
Cc: "cisco voip" <cisco-voip at puck.nether.net> 
Sent: Friday, June 12, 2009 12:01:05 PM GMT -05:00 US/Canada Eastern 
Subject: RE: [cisco-voip] using Nagios to monitor MCS servers 




Does RTMT push, I thought it pulled, it says “Successfully pulled data from server side”. At any rate, I do agree, push is better than pull, and RTMT is pretty good (not perfect), but I still can’t integrate RTMT in the tool that monitors the rest of our network/servers. 



Also, if SNMP is a problem for the CUCM then should we be developing some kind of script that pulls from the RIS Data Collector? 





From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca] 
Sent: Friday, June 12, 2009 10:43 AM 
To: Abebe Amare 
Cc: cisco voip; Fuermann, Jason 
Subject: Re: [cisco-voip] using Nagios to monitor MCS servers 




RTMT? 

It's gotten a lot better, and it's really your only solution going forward with appliances I think. 

I think you can do SNMP, but push beats pull in my opinion. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Abebe Amare" <abucho at gmail.com> 
To: "Jason Fuermann" <JBF005 at shsu.edu> 
Cc: "cisco voip" <cisco-voip at puck.nether.net> 
Sent: Friday, June 12, 2009 11:36:28 AM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] using Nagios to monitor MCS servers 


If using third party tools is not recommended, what is Cisco's recommended way to monitor the performance (CPU, memory, paging) utilization of these servers? We chose nagios because it is free and easy to use. 

regards, 

Abebe A. 


On Fri, Jun 12, 2009 at 5:32 PM, Fuermann, Jason < JBF005 at shsu.edu > wrote: 



Would you mind elaborating on the issues? I wouldn’t think snmp gets every few minutes would be that big an issue (at least compared to a single get). Of course, I could also see a single get spiking the cpu and causing a code yellow, I just wouldn’t expect it. Just curious cause we are using snmp to monitor our cluster. 





From: cisco-voip-bounces at puck.nether.net [mailto: cisco-voip-bounces at puck.nether.net ] On Behalf Of Wes Sisk 
Sent: Friday, June 12, 2009 9:09 AM 
To: abuch 
Cc: cisco voip 
Subject: Re: [cisco-voip] using Nagios to monitor MCS servers 





It is possible but I would caution you to take careful inventory of functionality and alarms before and after implementing nagios. we have seen numerous service impacting issues caused by monitoring tools. 

Regards, 
Wes 

On Friday, June 12, 2009 2:59:03 AM, abuch <abucho at gmail.com> wrote: 


Dear, 

What do you thinks of using Nagios to monitor performance utilization of Cisco MCS servers running windows 2003 like UCCX, WFO QM and Unity? 

regards, 

Abebe Amare 

System Engineer, VivaCell 


_______________________________________________ cisco-voip mailing list cisco-voip at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip 






_______________________________________________ cisco-voip mailing list cisco-voip at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090612/6a4e054b/attachment.html>