ISE DB size growing

Frank Lothar Weber · ‎01-15-2013

Hi, all.

Recently we are getting alarm from our Identity Services Engine, stating that the database size exceeds allowed disk size:

show version:

# sh ver

Cisco Application Deployment Engine OS Release: 2.0

ADE-OS Build Version: 2.0.4.018

ADE-OS System Architecture: i386

Hostname: deess01nise01

Version information of installed applications

---------------------------------------------

Cisco Identity Services Engine

---------------------------------------------

Version : 1.1.2.145

Build Date : Fri Oct 26 21:10:35 2012

Install Date : Thu Nov 8 17:56:09 2012

Cisco Identity Services Engine Patch

---------------------------------------------

Version : 2

Install Date : Sun Dec 16 18:22:32 2012

I cannot find anything referring to this alarm, anybody knows what to do ??

RGs

Frank

Rafael Mendes · ‎04-15-2013

Hi Frank,

I have this alarm in my ISE console too, and cannot find anything about this.

I opened the discussion https://supportforums.cisco.com/thread/2211527

Have you found anything about it?

askhuran · ‎04-23-2013

Hi Frank,

Are you running ISE on VMWare or ISE appliance?

I guess your monitoring node requires more space. You may need to regularly backup / clear the logs from the MnT node

On any node that has the Monitoring persona enabled, 30% of the VM disk space is allocated for log storage. For a Monitoring node with 600 GB VM disk space, 180 GB is allocated for log storage. A deployment with 100,000 user endpoints generates 2 GB of logs approximately per day. In this case, you can store 30 days of logs in the Monitoring node, after which you must transfer the old data to a repository and purge it from the Monitoring database. For extra log storage, you can increase the VM disk space. For every 100 GB of disk space that you add, you get 30 GB more for log storage. Depending on your requirements, you can increase the VM disk size up to a maximum of 600 GB or 180 GB log storage. The 30% disk space allotment is applicable only for fresh installations. If you upgrade to 1.1.x, a maximum of 150 GB is allocated for the MnT node irrespective of the VM disk size.

The following may be more helpful:

http://www.cisco.com/en/US/docs/security/ise/1.1.1/installation_guide/ise_vmware.html

Jimmy Harrysson · ‎04-26-2013

Hi

We are running the ISE 3395 appliances and have had this issue for several months. In our case we got it solved by upgrade to 1.1.3. Our problem was the Automatic Purge job was not running as it should causing the database to grow above recommended limits.

Anas Naqvi · ‎09-23-2013

Hi,

Yea, I am with Jimmy, problem could be with the Data Purging. Following is the link that might help,

http://www.cisco.com/en/US/docs/security/ise/1.2/user_guide/ise_mnt.html#wp1054328

http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_mnt.html#wp1074687

sahseth · ‎10-03-2013

Hello,

If you are using Esxi/VM for ISE deployment, there you can increase disk Size and also Purge old files if there present on Disk.

Naresh Ginjupalli · ‎10-05-2013

Hi Frank,

we have known issue with the auto purge process till ISE 1.1.3 and all these are resolved in ISE 1.1.3 Patch 4. So you can upgrade to ISE 1.1.3 Patch 4 or if you are planning for upgrade to ISE 1.2 it is good to perform the purge operation then upgrade. TAC can help to perform the manual purge operations.

Thanks,

Naresh

Ravi Singh · ‎10-07-2013

I would suggest you to open a TAC case for the same. They will help you to purge unused file as well as in update if you are planning one.

blenka · ‎10-08-2013

Monitoring Database Purge

The purging process allows you to manage the size of the Monitoring database by specifying the number of months to retain data during a purge. The default is three months. This value is utilized when the disk space usage threshold for purging (percentage of disk space) is met. For this option, each month consists of 30 days. A default of three months equals 90 days.

Related Topics

•Guidelines for Purging the Monitoring Database

•Purging Older Monitoring Data

Guidelines for Purging the Monitoring Database

The following are some guidelines to follow relating to monitoring database disk usage:

•If the Monitoring database disk usage is greater than 80 percent of the threshold setting, critical alarm is generated indicating that the database size has exceeded the allocated disk size. If the disk usage is greater than 90 percent another alarm is generated.

A purge process runs, creating a status history report that you can view by choosing Operations > Reports > Deployment Status > Data Purging Audit. An information (INFO) alarm is generated when the purge completes.

•Purging is also based on the percentage of consumed disk space for the database. When the consumed disk space for the monitoring database is equal to or exceeds the threshold (the default is 80 percent), the purge process starts. This process deletes only the last seven days of monitoring data, irrespective of what is configured in the Admin portal. It will continue this process in a loop until the disk space is below 80 percent. Purging always checks the Monitoring database disk space limit before proceeding.

Purging Older Monitoring Data

The purging process allows you to manage the size of the Monitoring database.

Before You Begin

To perform the following task, you must be a Super Admin or System Admin.

--------------------------------------------------------------------------------

Step 1 Choose Administration > System > Maintenance > Data Purging.

Step 2 Specify the time period in months, for which the data will be retained. All the data prior to the specified time period will be purged. For this option, each month consists of 30 days. The default of three months equals 90 days.

--------------------------------------------------------------------------------

Note If the configured retention period is less than the existing retention thresholds corresponding to the diagnostics data, then the configured value overrides the existing threshold values. For example, if you configure the retention period as 3 days and this value is less than the existing thresholds in the diagnostics tables (for example, a default of 5 days), then data is purged according to the value that you configure (3 days) in this page.

--------------------------------------------------------------------------------

Step 3 Click Submit.

Step 4 Verify the success of the data purge by viewing the Data Purging Audit report.

Naresh Ginjupalli · ‎10-08-2013

The MNT data purge process is all automated process within ISE, but before ISE 1.1.3 patch 4 there are known issues with this automated process and also the purge configuration mentioned in the ISE GUI is not being followed by implementation logic and thus causing the issue with automated purge process. So I would recommend to do manual purge once and then have a latest version greater than ISE 1.1.3 Patch 4 . With this version the auto purge process issue is rectified.