cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2264
Views
10
Helpful
1
Comments
Gerson Fabian Morales Marin
Community Member

    Problem Description

    In this document I would like to share some information in regarding to Alarms that RTMT shows up when for example a Linux system such as Call Manager is not under memory pressure and all the Kernel's caches will slowly grow over time. Linux prefers to keep larger caches just in case a process needs information from it. There is not reason to keep that if any process is not really in the need of it, so below I will share with you an option to stop this normal alarm that is getting in RTMT that at the end is just a generic message.

    Error

    Normal error messages will look like the following:

    Available virtual memory below configured threshold . Configured low threshold is 30 % tomcat#1 (1885 MB) uses most of the memory.
     The alert is generated on Thu Jan 08 15:06:52 CST 2015 on node
    Common Disk utilization hits LWM! AppID : Cisco Log Partition Monitoring Tool ClusterID :  NodeID : umhb-ccm-pub  TimeStamp : Thu Jan 08 15:15:27 CST 2015. 
    The alarm is generated on Thu Jan 08 15:15:27 CST 2015

     RTMT Alarms

    Alarm is shown up in RTMT in red and with the following output.

    A way to fix it and get of rid of this alert is accessing in RTMT System>Alert Central then you will be able to see both in red

    Workaround

    1- Go to "LogPartitionLowWaterMarkExeeded" and do a right click then click Set Alert/Properties >Click next> under Treshold move it to 10% > click next>save.

     2- Go to "LogPartitionHighWaterMarkExeeded" and do a right click then click Set Alert/Properties >Click next> under Treshold move it to 15% > click next>save.

    On Call Manager

    3- Go to serviceability in Call Manager>Tools>Control center/Network services> and restart the "Cisco Log Partition Monitoring Tool"

     4- After doing that you can feel free to Clear the alarm doing a right click and clear alarm.

     5- Next step will be go back to "LogPartitionHighWaterMarkExeeded" and do a right click then click Set Alert/Properties >Click next> under Treshold move it to 95% > click next>save.

    6-Go to "LogPartitionLowWaterMarkExeeded" and do a right click then click Set Alert/Properties >Click next> under Treshold move it to 79% > click next>save.

    7-Go to Serviceability on Call Manager one more time >Tools>Control center/Network services> and restart the "Cisco Log Partition Monitoring Tool"

     8-Clear the alarm one more time if shows up

     

    Results

     After cleaning the alarm the RTMT output should be clean and ready to go.

    Note: Keep in mind that if the alarm continues  in RTMT the best option is to collect the "Event viewer application logs" and "Event viewer system logs" and the "Cisco Ris data collector PerdMonLogs" in order to discard any problem with the server.

    In addition to this you can access this link and proceed deleting the logs from RTMT and install the cop file to clean up the partitions.

    Link= https://supportforums.cisco.com/document/12422481/not-enough-disk-space-common-partition-performing-l2-upgrade#Cop_file_installed

     

    I  hope this can help you.

    Regards,

    Gerson Morales (gersomor)

    Comments
    Aman Soi
    Advisor
    Advisor

    excellent DOC[+5]

     

    regds,

    aman

    Getting Started

    Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

    Quick Links