Facility Administration and Logging

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

This chapter consists of the following sections:

Error Message Storage

Resource Manager 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

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

Any Resource Manager user can view the status of any process by clicking Admin, then selecting System Admin > Process Status. Only users with administrator privileges can start and stop processes. Table 4-1 lists possible back-end processes and their expected status.

Process Name	Process Description
AvInputGen	Availability process
AvLoader	Availability process
AvIcmpPoller	Available ICMP poller
AvSnmpPoller	Available SNMP poller
DbServer	Data storage engine
DIServer	Import server
IcServer	Inventory collector
Proxy	Admin tasks
SyslogAnalyzer	Syslog message analyzer
WebServer	http server

Table 4-1: Back-End Process Status

Process Name Process Description

AvInputGen

Availability process

AvLoader

Availability process

AvIcmpPoller

Available ICMP poller

AvSnmpPoller

Available SNMP poller

DbServer

Data storage engine

DIServer

Import server

IcServer

Inventory collector

Proxy

Admin tasks

SyslogAnalyzer

Syslog message analyzer

WebServer

http server

Table 4-2 describes the possible process states.

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 reporting status.
Transient terminated	The process has completed its function and has terminated normally.

Table 4-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 reporting status.

Transient terminated

The process has completed its function and has terminated normally.

Table of Contents