Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

CCM running at max memory (1 gig)

Hi. Running CCM 4.1.3 sr1 and memory is maxed out. I noticed that logging into the CCM administration page takes a long time as well as navigating through the different areas of administration but don't know if it is related to the mem usage. Does anyone else have this symptom of high mem usage? If so, what is the fix? Add more memory? I figure on doing that, but would like to know if it is something else possibly. Below is an error indicating a low kernel stack.

Event Type: Warning

Event Source: SAVRT

Event Category: None

Event ID: 1005

Date: 8/24/2005

Time: 1:51:14 PM

User: N/A

Computer: CORPCCM01

Description:

Symantec AntiVirus Auto-Protect could not scan file C:\WINNT\System32\RDPDD.dll for viruses due to low kernel stack.

Data:

0000: 00 00 00 00 02 00 4c 00 ......L.

0008: 00 00 00 00 ed 03 07 80 ....í..€

0010: 00 00 00 00 00 00 00 00 ........

0018: 00 00 00 00 00 00 00 00 ........

0020: 00 00 00 00 00 00 00 00 ........

Any help would be appreciated.

Steve

1 ACCEPTED SOLUTION

Accepted Solutions
Community Member

Re: CCM running at max memory (1 gig)

We got 4.13 CCM with 1.0G Memory with new server. We noticed that the memory run really low immediately.

We did whatever we can, for intance limit memory usage for SQL, but not much help. Finally, we upgraded to 2.0G. Everything is fine now.

2 REPLIES
Cisco Employee

Re: CCM running at max memory (1 gig)

Physical Memory Recommendations for Cisco CallManager Vers. 4.0

http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_bulletin0900aecd80284099.html

Cisco recommends a minimum of 1 GB of physical memory on all servers running Cisco CallManager 4.0 and higher.

Publisher that is running Cisco CallManager service - 2 GB recommended

Community Member

Re: CCM running at max memory (1 gig)

We got 4.13 CCM with 1.0G Memory with new server. We noticed that the memory run really low immediately.

We did whatever we can, for intance limit memory usage for SQL, but not much help. Finally, we upgraded to 2.0G. Everything is fine now.

176
Views
3
Helpful
2
Replies
CreatePlease to create content