[cisco-voip] Sluggish Phones / Requesting Template since upgrade to4.1(3)sr5b

[Linsemier, Matthew]

That's the funny thing.  The event logs are clean. I poll CPU and Memory
via SNMP using SolarWinds Orion NPM and the trend seems to be normal.
The only real spike I get is at 2:00am on Wednesdays and Sundays when I
do backups (up to 50%).  I haven't had RTMT installed in a while but I
will do that today.  I have also been testing Unified Operations Manager
which says there are no issues.  I am running out of disk space on C: (I
have a bit over 3 Gigs free), but I don't see that as a issue.  I will
be purging our CDR records as soon as my peer gets the ISI upgrade
issues resolved.

Anything else that I am missing?

Matt

-----Original Message-----
From: Jason Aarons (US) [mailto:jason.aarons at us.didata.com] 
Sent: Wednesday, June 06, 2007 9:19 AM
To: Linsemier, Matthew; cisco-voip at puck-nether.net
Subject: RE: [cisco-voip] Sluggish Phones / Requesting Template since
upgrade to4.1(3)sr5b

Via Perfmon or RTMT have you logged what the cpu/memory high water marks
have been? Memory leak, high cpu processes, etc. Event Viewer log files
clean?

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Linsemier,
Matthew
Sent: Wednesday, June 06, 2007 8:49 AM
To: cisco-voip at puck-nether.net
Subject: [cisco-voip] Sluggish Phones / Requesting Template since
upgrade to4.1(3)sr5b

All,

We recently went through two upgrades of CCM, 4.1(3)sr5a and then
4.1(3)sr5b from 4.1(3)sr4d.  Over the last couple of days I have had two
instances of sluggish phones (slow dialing, phone continually
re-registers) and "Requesting Template" errors.  The first time I
thought was just a isolated incident of maybe a 7960 going bad (which in
turn affected the 7920 using the shared line of this phone).  I fixed
the problem by deleting the phones (both of them a 7960 and a 7920) and
re-creating them in CallManager.  Today I came into work to another 7960
experiencing the same problem (Requesting Template).  I restarted the
publisher this morning and upon doing so the phone registered without
issue.

Our environment has been rock solid on 4.1(3)sr4d without any error.
However, we try to make it a practice to stay up to date with service
releases since we have had good experiences in doing so in the past.
Short of opening a TAC case, does anyone have any ideas of what could be
going on?  I am wondering if I am hitting a new bug.  Is it possible to
uninstall the previous two service packs (to get back on 4.1(3)sr4d) and
is it even recommended?  

We are slated for a 5.x or 6.x upgrade shortly (about to test them in
the lab) and I am just trying to keep things stable (as they have been)
until then.

Thanks,

Matt
CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may
be protected by one or more legal privileges. It is intended
solely for the use of the addressee identified above. If you
are not the intended recipient, any use, disclosure, copying
or distribution of this communication is UNAUTHORIZED. Neither
this information block, the typed name of the sender, nor
anything else in this message is intended to constitute an
electronic signature unless a specific statement to the
contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete
this communication from your computer. Thank you.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
CONFIDENTIALITY STATEMENT
This communication and any attachments are CONFIDENTIAL and may
be protected by one or more legal privileges. It is intended
solely for the use of the addressee identified above. If you
are not the intended recipient, any use, disclosure, copying
or distribution of this communication is UNAUTHORIZED. Neither
this information block, the typed name of the sender, nor
anything else in this message is intended to constitute an
electronic signature unless a specific statement to the
contrary is included in this message. If you have received this
communication in error, please immediately contact me and delete
this communication from your computer. Thank you.