Table Of Contents

Purging the Database

Configuring Event Purging Values Using Registry Editor

Scheduling Automatic Event Purging

Cisco ANA Integrity Service

Purging the Database

---

This chapter describes how to automatically purge traps, events, and alarms from the Cisco ANA database. The tasks involved in configuring automatic purging are:

1.  Configuring the length of time to keep traps, events, and alarms in the database.

2.  Adding an entry to the cron table so that events older than the specified length of time are purged automatically on a regular basis.

This chapter also describes Cisco ANA integrity service and how to schedule integrity service tests to maintain system stability.

This chapter includes the following sections:

•Configuring Event Purging Values Using Registry Editor

•Scheduling Automatic Event Purging

•Cisco ANA Integrity Service

Configuring Event Purging Values Using Registry Editor

The length of time for which database events, traps, and alarms are retained is specified in the registry. The relevant entries in the registry are in the site hive under site/mmvm/agents/integrity/partitioning and are listed in Table 13-1. The default length of retention is 14 days, as indicated by the totalHistorySize key for each entry.

Table 13-1 Event Entries in the Cisco ANA Registry 

Entry	Description
com.sheer.imo.IAffectedSNC	Subnetwork connections
com.sheer.imo.IAlarmTicket	Tickets
com.sheer.imo.IAuditEvent	Audit
com.sheer.imo.IEventHistory	Event history
com.sheer.imo.IProvisioningEvent	Provisioning
com.sheer.imo.ISecurityEvent	Security
com.sheer.imo.IServiceAlarm	Service alarms
com.sheer.imo.ISyslogAlarm	Syslog alarms
com.sheer.imo.ISystemEvent	System alarms
com.sheer.imo.ITrapValue	Traps
com.sheer.imo.IV1TrapAlarm	V1 trap alarms
com.sheer.imo.IV2TrapAlarm	V2 trap alarms

Figure 13-1 shows an example of the Registry Editor with the relevant entries.

Figure 13-1 Registry Editor with Event Entries

To change the length of time for which these events, traps, and alarms are retained:

---

Step 1 Using Registry Editor, log into the Cisco ANA gateway.

Step 2 Choose File > Connect to Golden Source.

Step 3 In the Golden Source dialog box, choose Template from the drop-down list and then click OK.

Step 4 After the registry loads, under All Hives, navigate to site/mmvm/agents/integrity/partitioning.

Step 5 For each entry in Table 13-1, complete the following steps:

a. Select the entry in the registry tree.

b. In the workspace table, right-click totalHistorySize, then choose Override. The Create Entry dialog box appears.

c. In the Value field, enter the number of days Cisco ANA is to retain the events and click OK. The entry in the workspace table is updated with the new value.

d. Repeat Step 5a through Step 5c until you have set the value for totalHistorySize for each entry in Table 13-1.

Step 6 Exit Registry Editor. The new values take effect immediately and are used the next time the cron job takes effect. See Scheduling Automatic Event Purging for information on scheduling the cron job.

---

Scheduling Automatic Event Purging

To ensure that events are purged automatically on a regular basis, schedule a cron job.

---

Step 1 Log into the Cisco ANA gateway as user sheer.

Step 2 Enter the following command to edit the cron table:

crontab -e 

Step 3 Add the following line to purge database events twice a day at 11:15 a.m. and 11:15 p.m.:

15 11,23 * * * cd /export/home/sheer/Main ; ./mc.csh localhost 8011 integrity.executeTest 
partitioning > /dev/null 2>&1 

---

Note See crontab(1) in the Solaris documentation for a detailed explanation about the cron table format.

---

---

Cisco ANA Integrity Service

The Cisco ANA integrity service is responsible for maintaining system stability by running integrity tests to maintain the database and eliminate clutter in the system. It is an internal service that runs on a gateway or units.

You can run service integrity tests either manually or automatically:

•Manually—The integrity service tests are accessed as part of Cisco ANA Shell management services and can be run by connecting to the gateway using Telnet.

To run a test manually, connect to the gateway using Telnet, navigate to the integrity directory, and then enter executeTest followed by the test name. You can pass parameters to the tests by using Cisco ANA Shell.

•Automatically—Using cronjob commands, you can schedule specific integrity service tests to run at specific intervals. By default, integrity service tests run automatically every 12 hours.

For example, the following line in the crontab file runs the file every_12_hours.cmd at 11:00 a.m. and 11:00 p.m.:

0 11,23 * * * local/cron/every_12_hours.cmd > /dev/null 2>&1

In this example, the integrity service tests are defined in the every_12_hours.cmd file; for example:

echo "`date '+%d/%m/%y %H:%M:%S -'` running integrity.executeTest alarm"

cd ~/Main ; ./mc.csh localhost 8011 integrity.executeTest alarm >& /dev/null

In this example, the first line is written to the gateway log and indicates the test start time. The next line runs the test.

Integrity service test parameters are defined in the registry.

---

Note Changes to the registry should be performed only with the support of Cisco. For details, contact the Cisco ANA Project Manager or Cisco Account Team.

---

Integrity service tests include the following:

•Alarm—Deletes cleared alarms if the alarm count (the total number of alarms currently in the gateway) is above the defined threshold.

•businessObject—Checks for invalid OIDs in business objects.

•Capacity—Checks the disk space capacity.

•archiveLogs—Deletes Oracle logs.

•tablespace—Verifies that there is enough disk space for tablespace growth.

•workflowEngine—Deletes all complete workflows that started before a configured period of time.