Author Topic: Potential memory issue  (Read 6379 times)

Offline hsearson

  • Jr. Member
  • **
  • Posts: 78
  • Karma: +0/-0
    • View Profile
Potential memory issue
« on: August 25, 2010, 03:04:01 PM »
Can anyone verify that the memory in this controller is unusually resourced out for a MCD 4.1 with only 227 IP Devices running on it?


<   Page  4   of   19    >   Go to:  Log Number Date Time Source DescriptionPage #   value:  Go   
Maintenance Warning Logs
 Log Number       Date       Time       Source       Description       
  3756
  2010/Aug/25
  13:39:26
  Call Control - Security
  Local date/time reset to 2010-AUG-25 13:39:26.00    WED by ESM User.
 
  3755
  2010/Aug/25
  13:38:40
  MemAudit
  memAudit600s: The amount of free memory has exceeded the Major threshold of 5 Mbytes. Current free memory 4 Mbytes out of a total of 512 Mbytes.

 
  3753
  2010/Aug/25
  12:46:18
  Call Control - Maintenance
                                  ------------
Current System Alarm :          | NO ALARM |       viewed from Active
                                ------------



 
  3752
  2010/Aug/25
  12:46:16
  Call Control - Maintenance
  Change in network synchronizing source from  free run to  source  01
Justification :  New synchronizing source has just become available

 
  3725
  2010/Aug/25
  12:38:50
  Call Control - Maintenance
 
 
  3724
  2010/Aug/25
  12:38:50
  Call Control - Maintenance
  ---------------+--------+-------+-------+-------+---------+---------+----------
NETSYNC source |     1  |     1 | 100 % | Minor |   > 0 % |    -    |    -    |
---------------+--------+-------+-------+-------+---------+---------+----------

 
  3723
  2010/Aug/25
  12:38:50
  Call Control - Maintenance
  ---------------+--------+-------+-------+-------+---------+---------+----------
               |Total In|      Unavailable      | Alarm Threshold Percentages
   Category    | System | Total |    %  | Alarm |  MINOR  |  MAJOR  | CRITICAL

 
  3722
  2010/Aug/25
  12:38:50
  Call Control - Maintenance
                                  ------------
Current System Alarm :          |  MINOR   |       viewed from Active
                                ------------



 
  3721
  2010/Aug/25
  12:38:47
  Call Control - Maintenance
  Change in network synchronizing source from  source  01 to  free run
Justification :  system clock at    01   01   01   loses synchronizing source

 
  3717
  2010/Aug/25
  12:38:11
  Call Control - Security
  Local date/time reset to 2010-AUG-25 12:38:11.00    WED by ESM User.
 
User and Device
Hot Desking User
IP Device Only


Offline wobbly_head_bob

  • Jr. Member
  • **
  • Posts: 62
  • Karma: +0/-0
    • View Profile
Re: Potential memory issue
« Reply #1 on: August 26, 2010, 10:44:54 AM »
While I'm not sure if the memory consumption has anything to do with your IP devices per se, its probably worthwhile to schedule (if possible) programmed reboot resource recovery.

"Memory Consumption Threshold
If the amount of free memory becomes less than

10 MB, a minor log is generated and a minor alarm is generated. The alarm is generated to notify the system maintainer that the system should be rebooted. Under normal circumstances, the system should remain up for 2 to 4 days after the alarm is generated. If configured, the system will be reset at the next programmed resource recovery reboot time.

5 MB, a major log is generated and a major alarm is generated.  A schedule reboot should be programmed to reboot the system at the end of the day.

2 MB  a critical log is generated and a critical alarm is raised on the system. The system resets immediately."

"Programmed Reboot Resource Recovery ON/OFF - Turns the programmed reboot on and off. If enabled, a software-controlled reboot will occur at the next occurrence of the specified time ONLY if the available memory threshold has been reached or if a non-critical resource failure occurs. Alarms are raised (Memory Consumption, Memory Fragmentation, Stale Tasks or Memory Avail) and Maintenance Logs generated. See Resource Monitoring for threshold details. Critical system resources may deteriorate to the point where the system performs a software-controlled reboot on its own, before the scheduled reboot time. If this occurs, the reason for the reboot is saved in the "panic" area of the Maintenance Log for the Memory Avail alarm. System Memory Consumption, System Memory Fragmentation and Stale System Tasks generate alarms and maintenance logs at the time of the resource failure."



 

Sitemap 1 2 3 4 5 6 7 8 9 10