[cisco-voip] using Nagios to monitor MCS servers

[Wes Sisk]

For our own CUOM product we've seen rapid repeated SNMP queries and AXL 
reads spike CPU and cause code yellow just as you fear.

In the specific case of Nagios it caused CSCsk46770 which is a PSIRT 
issue so limited information is available.


I am not recommending against this approach.  I am only recommending to 
take inventory of system health and behavior before and after 
implementation. We have repeatedly observed monitoring tools causing 
significant impact.

/Wes

On Friday, June 12, 2009 10:32:15 AM, 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> 
> <mailto: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 <mailto: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/f807f758/attachment.html>