cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/cwsi_2x/cwsi_2_2
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Facility Administration and Message Logging

Facility Administration and Message Logging

This chapter describes Essentials facilities and explains how and where messages are logged. Essentials log messages are written to the Syslog facility. Essentials debugging messages are written to the individual services log files in the registry.

This chapter consists of the following sections:

Error Message Storage

Essentials error messages are written to log files in C:\Program Files\CSCOpx\log. Each file assumes the name of the process that generates the error. Because messages are continuously appended to these files, you might want to occasionally remove the files. The files are recreated automatically.

Scheduling Scheme

Essentials has a self-contained scheduling mechanism that is configured automatically during installation.

Process Status

Any Essentials user can view the status of any process by selecting Admin > System Admin > Process Status. Only users with administrator privileges can start and stop processes. Table 6-1 shows possible back-end processes and their expected statuses.


Table 6-1: Back-End Process Status
Name Description State

AvIcmpPoller

Polls devices using ICMP1 and provides information about whether a device is accessible.

Running normally

AvInputGen

Retrieves polling information from the database and provides AvIcmpPoller and AvSnmpPoller with a list of devices to poll and the frequency with which to poll them.

Running normally

AvLoader

Moves data from AvIcmpPoller and AvSnmpPoller to the Essentials database.

Running normally

AvSnmpPoller

Polls devices using SNMP2 and provides protocol distribution and reload information.

Running normally

AvTrimmer

A transient process that runs on a regular schedule to trim expired availability data from the Essentials database.

Running normally

CasServer

A Change Audit program that provides back-end database services for applications that want to log network changes and for Change Audit reports.

Running normally

ChangeAudit

Consists of the following Java programs which provide the back-end functionality of Device Configuration:

  • CasServer

  • ConfigArchive

  • InvChangeProbe

  • Scheduler

Running normally

CMLogger

Used by Java back-end processes and clients to get error messages from Essentials message catalogs.

Running but busy flag set

ConfigArchive

A Change Audit program that gets configuration files from devices and archives them.

Running normally

ConfigChangeDetector

Detects configuration changes in the network.

Running normally

ConfigPurge

Deletes expired configuration files from the archive.

Running normally

ConfigUpdate

Sweeps managed devices looking for configuration changes.

Running normally

DbServer

A system service: the database engine.

Running normally

DbService

Java database interface.

Running normally

DIServer

Imports and adds devices to the inventory.

Running normally

EDS

A system service that distributes application and network events among Essentials components.

Running normally

EssentialsDbMonitor

A system service that monitors the accessibility of the Essentials database engine, which helps to ensure that the system is not started until the database engine is ready. All database-dependent back-end processes depend on this process.

Running normally

EssentialsOSG

Sybase's open server gateway that allows Java programs to connect to the Essentials database.

Running normally

IcServer

Routinely collects inventory updates from managed devices. Inventory updates are acquired through SNMP queries on MIBs in the devices that maintain inventory information.

Running normally

InvChangeDetector

Detects inventory changes in the network and causes the device database to be updated.

Running normally

InvChangeProbe

A Change Audit program that sends notifications when new devices are managed by DIServer or when managed devices are deleted from inventory.

Running normally

JrunProxyServer

Java servlet engine.

Running normally

JSSsched

Scheduling process.

Running normally

NetsysRpt

Provides configuration files to the NetSys application and acquires NetSys reports for Essentials users.

Running normally

OSGpxDb

Open Server Gateway.

Running normally

Proxy

A system service that allows Essentials back-end processes to perform privileged operations on Windows NT systems that they normally would not be permitted to perform, for example, scheduling jobs on a Windows NT system for Software Management. Without Proxy, the application's Perl code would not allow the scheduling.

Running normally

RmeOrb

One of the system services that is the object request broker (ORB) part of CORBA.

Running normally

Scheduler

A Change Audit program that schedules repeating jobs for the Inventory and Device Configuration back-end processes.

Running normally

SyslogAnalyzer

Filters and forwards messages from routers and switches to the central Essentials server.

Running normally

1ICMP = Internet Control Message Protocol.
2SNMP = Simple Network Management Protocol.

Table 6-2 describes the possible process states.


Table 6-2: Process Status Defined
State Definition

Administrator has shut down this server

The administrator or another program has shut down the process.

Failed to run

The process has failed by exiting or sending a failed init message.

Never started

The process is not configured for autostart. The process must be started manually.

Program started - No mgt msgs received

The process has started but the status has not been reported to the process manager.

Running but busy flag set

The process has successfully started, but does not participate in process management messaging.

Running normally

The process has successfully started and is reporting status.

Transient terminated

The process has completed its function and has terminated normally.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Sep 30 10:24:53 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.