[cisco-voip] Code Yellow

Tim Smith thsglobal at gmail.com
Sun Oct 11 19:54:12 EDT 2009


Just out of interest, are most people leaving traces on detailed level in
production?

Cheers,

Tim.

On Mon, Oct 12, 2009 at 10:03 AM, Peter Slow <peter.slow at gmail.com> wrote:

> ...but since you are on an appliance version of CUCM, ignore what i
> said about virus scanners =)
>
> On Sun, Oct 11, 2009 at 7:02 PM, Peter Slow <peter.slow at gmail.com> wrote:
> > steven, code yellows can be caused by a number of things, and are
> > indications of a service affecting event that prevented new calls from
> > being established. typical causes  are server performance issues (high
> > cpu utilization by a non-ccm process such as a virus scanner, a
> > failing disk drive or raid controller etc) but causes can also be
> > internal to CCM such as a call routing loop or events involving large
> > numbers of devices that cause an exceptional load on your callmanager.
> >
> > you should probably open a case - did you have traces set to detailed?
> > you'll want to gather perfmon logs as well.
> >
> > -Peter
> >
> > On Sun, Oct 11, 2009 at 2:24 PM, Steven Sarte <steven.sarte at gmail.com>
> wrote:
> >> Received a Code Yellow alert from RTMT for one of my subscribers.  Has
> >> anyone ever get this before?  I did check RTMT and it everything looks
> >> fine.  Can anyone else provide some guidance.
> >>
> >> Callmanager 7.x
> >>
> >> Thanks,
> >> Steven
> >> _______________________________________________
> >> 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/20091012/624d9be8/attachment.html>


More information about the cisco-voip mailing list