|
|
This chapter provides the following sections on how to maintain Cisco Enterprise Accounting (CEA), troubleshoot problems you may encounter, and report unresolved problems to Cisco Systems:
For Cisco Enterprise Accounting release-specific information, see the Cisco Enterprise Accounting Release Notes, available on the Cisco Connection Documentation CD or on the World Wide Web at Cisco Connection Online.
The Cisco Enterprise Accounting (CEA) data collection engine runs as a UNIX daemon background process. A few maintenance tasks are required to ensure efficient operation of this software over long periods of time. The frequency at which these tasks must be performed depends on various factors such as call volume and available disk space and memory.
The CEA data collection engine should be shutdown using the cea_killds command prior to rebooting the workstation. Once the workstation has been rebooted, use the cea_startds command to restart data collection.
Some ISDN calls that are in progress when the CEA data collection engine shuts down may finish by the time CEA restarts. Routers retain the call information in the Cisco ISDN MIB for a limited time. If CEA is down longer than the Cisco ISDN MIB retain time, the CEA data collection engine cannot record a disconnect time for the affected calls. You may wish to remove active calls from your cea_datastore file before you restart CEA data collection. Refer to the "Remove Active Calls from the Datastore" section for details.
The logfiles for the CEA data collection engine are contained in the $CEAHOME/svr/log/ directory. Since CEA processes append to the end of the existing logs, these log files will grow large over time and should be cleaned up periodically to conserve disk space. These files should not be removed while CEA is running but can be safely moved or deleted when CEA is not running.
To remove the existing logfiles, use the following command:
cea_rmlogsTo save the existing logfiles, use the following command:
cea_savelogsTo make a copy of the existing call history while the CEA data collection engine is running, use the cea_archive command.
 | Caution Do not use the UNIX cp command to archive the cea_datastore file when the CEA data collection engine is running. The resulting file may be unusable. |
The cea_datastore file can be safely copied via the UNIX cp command when the CEA data collection engine is not running.
If your current cea_datastore file has been damaged, you can replace it with an archived copy.
Step 1 Shutdown the CEA data collection engine.
cea_killdsStep 2 Remove the $CEAHOME/svr/data/cea_datastore file.
rm $CEAHOME/svr/data/cea_datastoreStep 3 Copy your archived file to $CEAHOME/svr/data/cea_datastore.
cp your_archived_database $CEAHOME/svr/data/cea_datastoreStep 4 Remove active calls from the archived file. Refer to the "Remove Active Calls from the Datastore" section for details.
Step 5 Restart CEA data collection.
cea_startdsThe cea_datastore file, which contains the raw call data, is continually appended rather than overwritten. Over time, this file will grow very large, consuming disk space and increasing the time required to start the CEA data collection engine. This file should be erased periodically. You may wish to make a copy of the file before removing it. See the "Archive the Call History" section for details.
| Caution Do not remove the call history while CEA is running. |
You can remove the existing call history with the following command:
rm $CEAHOME/svr/data/cea_datastoreTo remove active call records in the cea_datastore file, use the cea_cleanup command before you start the CEA data collection engine.
| Caution Do not use the cea_cleanup command while CEA is running. |
Your existing cea_datastore file will be preserved as the file cea_datastore.save, and all calls without a disconnect time will be removed from the cea_datastore file.
Routers can be added or removed from the cea_hosts.cnf file at any time to reflect changes to your network. Whenever you modify the cea_hosts.cnf file, execute the cea_config to re-read the configuration file while CEA is running. You do not need to shut down the CEA data collection engine when making these changes.
If you have set the $CEAAUTOVIEW environment variable, CEA will also make the necessary changes to your SunNet Manager database. However, CEA will not remove old routers which are no longer monitored from the SunNet Manager database. If you wish to remove these manually from the SunNet Manager database, follow the instructions provided by SunNet Manager documentation.
The data collection engine software includes administrative commands to help you maintain CEA. Table 3-1 lists the commands found in the $CEAHOME/svr/bin directory.
For more information on these commands, see the man pages.
The Cisco Enterprise Accounting (CEA) Windows application Tools menu contains commands for administrative maintenance tasks, including cleaning up files and archiving the database.
When you delete a record in CEA, the record is no longer available for use but still occupies disk space on the hard drive. In order to erase the record and free the disk space, you must use the Clean Up Files command.
The Clean Up Files command removes deleted records from your hard disk and rebuilds the indexes.
You may need to run the Clean Up Files command in situations such as:
To clean up your files, select the Clean Up Files command on the Tools menu. The CEA window displays messages and a status bar indicating its progress.
CEA contains several databases, all of which are located in the Data folder. The database that contains your data is named VTRU.DCT.
You can archive your current VTRU database and store it in a folder that you select. You might want to do this to back up your database as a precaution or to save current data for historical purposes, such as to provide proof of telephone abuse. Depending on your needs, you may not need to archive your entire database to accomplish this purpose. You also can export a record set, which is much simpler and faster to do.
| Caution Do not save the database file simply by copying it to another folder using the Explorer, as you would any other file. Copying the database file in this manner makes its contents unusable. |
An archived database has the same name as your current database, so you cannot archive your database more than once to the same folder. If you want to archive databases from different time periods, archive them to different folders.
To archive the database, perform the following steps:
Step 1 Select the Archive Database command on the Tools menu. The Select Directory dialog box appears.
Step 2 To archive the database to another drive, select the drive in the Drive box.
Step 3 Select a folder where you want to store the archived database. The Archive folder is the default. To open or close folders in the list, double-click the folder icon or the folder name.
Step 4 Click the Select button to start the archival process.
To use the data in an archived database, you must move it back to your Data folder.
Step 1 Save your current database by archiving it to a folder than does not already contain an archived database.
Step 2 Using the Explorer, copy the archived database to your Data folder, overwriting the current database.
Step 3 Run the reports or record sets that you need on the old data.
Step 4 When you are finished with the old data, copy your current database back to the Data folder using the Explorer.
The Utilities application allows you to perform the following tasks:
You can limit the operation to data from a certain time period or with a specific Device ID.
To troubleshoot the data collection engine, read the logfiles and use the supplied troubleshooting commands to check the status of the data collector.
Table 3-2 lists the logfiles for the CEA data collection engine, which are contained in the $CEAHOME/svr/log/ directory.
The following example display shows a normal cea_ds_logfile containing startup messages.
**** CEA Server Started At Jan 23 1997 18:55:52 PID=24580 ****
Jan 23 1997 18:55:53 Loading record 0 from /home/ceahome/svr/data/cea_datastore...
Jan 23 1997 18:55:53 51 records loaded from /home/ceahome/svr/data/cea_datastore
Jan 23 1997 18:55:53 CEA Server Init Completed
Jan 23 1997 18:55:53 cea_dc_main started (PID=24582)
Jan 23 1997 18:55:54 Started /home/ceahome/svr/bin/cea_dc_polld c2503lp (PID=24586)
Jan 23 1997 18:55:54 Started /home/ceahome/svr/bin/cea_dc_polld gw (PID=24587)
The following example display shows a normal cea_dc_logfile.<host> when logging is enabled.
Jan 23 1997 18:55:54
***cea_dc_polld started (PID=24587) ***
Jan 23 1997 18:55:56 Adding interface BRI0: B-Channel 1
Jan 23 1997 18:55:58 Adding interface BRI0: B-Channel 2
Jan 23 1997 18:56:10 Config finished ....
Jan 23 1997 18:56:11 Awake in state=sleeping ....
Jan 23 1997 18:56:13 Sleeping for 10 mins ....
Use the cea_chkds and cea_chkprocs commands to verify that CEA is running.
Common problems during startup include the following:
Use the cea_chkprocs command to verify that the data collector process, called cea_dc_polld, is running for the affected router.
Common problems which interfere with data collection include the following:
If the CEA data collector appears to be stuck, use the cea_wakedc command to manually initiate polling. A known SunNet Manager problem may have caused this problem.
Enable detailed logging to get more information. Change cea_hosts.cnf file and invoke the cea_config command to increase log detail. Refer to the "Configure the cea_hosts.cnf File" section in the "Installation and Configuration Procedures" chapter for details on the cea_hosts.cnf file.
Cisco Enterprise Accounting (CEA) provides the Port Monitor and Database Recovery tool to assist you in troubleshooting.
If CEA is not collecting data, perform the following steps to check your application:
Step 1 Make sure all cables are properly connected.
Step 2 Make sure the data collection engine is included in the C:Windows\hosts file.
Step 3 Within CEA, select the Settings pull-down menu. Select the Recording Setup command. You will return to the setup screen that you completed in the initial installation. Make sure the settings on this screen are correct. Double check to make sure that the correct port is set and that the device you have selected is correct.
Step 4 Make sure there is call activity. In small companies, it may be possible that there is no call activity at the time. If this is possible in your environment, make a couple of outside calls, and ask some co-workers to do the same.
The Database Recovery Tool rebuilds your CEA database. You can use it to restore corrupted files in the following situations:
The Database Recovery Tool does the following tasks:
You cannot lose data when you use the Database Recovery Tool. A copy of all your files resides in the Recover folder. The Recover folder remains until you manually delete it.
To rebuild your data files using the Database Recovery Tool, do the following:
Step 1 Be sure that CEA is not running. If it is running, the recovery process cannot access some of the files.
Step 2 Select the Database Recovery Tool option in your CEA program group. A message appears that explains the recovery process and asks if you want to continue with it.
Step 3 Click the Yes button. The recovery process begins and displays an indicator of its progress. When it is finished, a message appears stating "Database recovery complete."
Step 4 Click the OK button.
Step 5 Start CEA and try various activities to see if the files are working properly.
Step 6 When you are sure that everything is working as it should, delete the Recover folder.
The Command Line command on the Tools menu opens a window that allows you to enter Visual FoxPro commands. You can use it to manually perform certain maintenance and troubleshooting procedures.
| Caution Use the command line only under the guidance of a Technical Support Representative. |
If you receive an error message, verify that you have tried the recommended action for resolving the error. Check for any release-specific information that may apply to a problem in the Cisco Enterprise Accounting Release Notes.
If there is a problem with the SPARC station data collection engine, obtain a copy of the cea_datastore and cea_hosts.cnf files in $CEAHOME/svr/data. Save a copy of all available log files in $CEAHOME/svr/log. Capture the result returned by the cea_chkprocs command, and document any additional console messages. Be sure to capture all this information before restarting Cisco Enterprise Accounting (CEA).
In the CEA Windows application, the View Log File command under the Tools menu displays messages.
To help solve any problems you may encounter using CEA, have the following information ready when you call Cisco Systems for support:
If possible, try to reproduce the problem and explain the steps that allow you to reproduce the problem.
|
|