Table Of Contents

Cisco ANA Integrity Service

Cisco ANA Integrity Service

---

This appendix describes how auto-archiving is performed by the integrity service process.

The integrity service is an internal service that runs on the gateway and/or the units that is responsible for the stability of the system, by running integrity tests in order to maintain the database and eliminate clutter in the system.

The service integrity tests are run:

•Manually—The integrity service tests are accessed as part of the Cisco ANA Shell management services, and they can be accessed by telneting the gateway.

To run a test, the user should change to the integrity directory and then enter executeTest followed by the test name. The user can pass parameters to the tests using Cisco ANA Shell.

•Automatically—The integrity service tests are scheduled as crontab commands, to run specific tests at specific intervals. By default the integrity service tests run automatically every 12 hours.

For example, this line in crontab runs the file every_12_hours.cmd at 11:00AM and 11:00PM:

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

The integrity service tests can be defined inside the 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

The first line is written to the gateway log, marking when the test started running, and the next line runs the test.

The integrity service test parameters are defined in the registry. The registry entries responsible for the integrity service can be found at:

mmvm/agents/integrity

---

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

---

The integrity service tests include, for example, 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—Checks that there is enough disk space for tablespace growth.

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