Installing Management Center for IDS Sensors 1.2 and Monitoring Center for Security 1.2
Troubleshooting
Download this chapter
TroubleshootingTroubleshooting
give_us_feedback

Table of Contents

Troubleshooting
Understanding IDS MC and Security Monitor Installation Error Messages
 Viewing IDS MC and Security Monitor Process Status

Troubleshooting

This appendix provides troubleshooting information for Management Center for IDS Sensors (IDS MC) and Monitoring Center for Security (Security Monitor). It contains the following sections:

Understanding IDS MC and Security Monitor Installation Error Messages

Table A-1 shows installation error messages, their probable causes, and possible solutions.

Table A-1   Installation Error Messages

Error Message  Probable Cause  Possible Solution 

Cannot find required component Core.

CiscoWorks Common Services is not installed.

Install CiscoWorks Common Services.

Unable to retrieve package name (idsmdc_m).

Corrupt Security Monitor or CiscoWorks Common Services installation.

Reinstall Security Monitor. If this message persists, contact TAC.

Unable to retrieve package name (idsmdc_c).

Corrupt IDS MC or CiscoWorks Common Services installation.

Reinstall IDS MC. If this message persists, contact TAC.

Unable to retrieve package version (idsmdc_m).

Corrupt Security Monitor software or CiscoWorks Common Services installation.

Reinstall CiscoWorks Common Services and Security Monitor. If this message persists, contact TAC.

Unable to retrieve package version (idsmdc_c).

Corrupt IDS MC software or CiscoWorks Common Services installation.

Reinstall CiscoWorks Common Services and IDS MC. If this message persists, contact TAC.

Unable to register Security Monitor Resource with CiscoWorks Common Services Client Registrar.

Corrupt CiscoWorks Common Services installation.

Reinstall CiscoWorks Common Services and Security Monitor. If this message persists, contact TAC.

Unable to register IDS MC Resource with CiscoWorks Common Services Client Registrar.

Corrupt CiscoWorks Common Services installation.

Reinstall CiscoWorks Common Services and IDS MC. If this message persists, contact TAC.

Unable to initialize Security Monitor Configuration Manager Database.

Corrupt CiscoWorks Common Services installation.

Reinstall CiscoWorks Common Services and Security Monitor. If this message persists, contact TAC.

Unable to initialize IDS MC Configuration Manager Database.

Corrupt CiscoWorks Common Services installation.

Reinstall CiscoWorks Common Services and IDS MC. If this message persists, contact TAC.

Viewing IDS MC and Security Monitor Process Status

Any CiscoWorks user can view the status of any process by selecting Server Configuration > Administration > Process Management > Process Status from the CiscoWorks navigation tree.

Note   From a client, only users with administrator privileges can start and stop processes. From the server, only users with local administrator privileges can start and stop processes.

To view the process status, follow these steps:

Step 1   Log into the CiscoWorks Server.

The CiscoWorks Server desktop appears.

Step 2   Select Server Configuration > Administration > Process Management > Process Status.

The Process Status page appears.

Step 3   Verify the status of the following processes:

  • Apache—To check that the web server is running properly.
  • ASANYs_SqlCoreDB—To check that the SQL database is running properly.
  • daframework—To check that the device agent is running properly.
  • fms—To check that the database is running properly.
  • IDS_Analyzer—To check that the service that processes event rules and requests user-specified notifications when appropriate is running properly.
  • IDS_Backup—To check that the service that backs up and restores the IDS MC and Security Monitor database is running properly.
  • IDS_DbAdminAnalyzer—To check that the service that periodically applies active database rules to the current state of the server is running properly.
  • IDS_DeployDaemon—To check that the service that manages all configuration deployments is running properly.
  • IDS_EvsServer—To check that the service that manages most Event Viewer data processing is running properly.
  • IDS_Notifier—To check that the service that receives notification requests (script, e-mail, and/or console) from other subsystems and performs the requested notification is running properly.
  • IDS_Receiver—To check that the service that receives IDS and syslog events and stores them in the database is running properly.
  • IDS_ReportScheduler—To check that the service that generates all scheduled reports is running properly.
  • JRunProxyServer (Windows only)—To check the Java servlet engine is running properly.
  • lm—To check that the fms database lock manager is running properly.
  • NRPostOfficeD—To check that the postoffice service, which enables communication to IDS Sensors, is running properly.
  • Tomcat—To check that the Java servlets that make up the IDS MC and Security Monitor user interface are running properly.
  • WebServer—To check that the Apache web server is running properly.