Facility Administration and Message 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 /var/adm/CSCOpx/log/daemons.log file.

This chapter consists of the following sections:

Syslog Facility

Resource Manager uses a syslog facility (0 to 7) for storing log messages. By default, all router log messages are written to local7 by Cisco routers. Resource Manager uses the first unused facility in the range local0 through local6 to store log messages. If an unused syslog facility cannot be found at the time of installation, the Resource Manager installation tool stops the installation and gives you the option of aborting or specifying the syslog facility to use for storing log messages.

Error Message Storage

Resource Manager error messages are written to the /var/adm/CSCOpx/log/dmgtd.log file . Because messages are continuously added to this file, you might want to occasionally copy this file to a different name, compress it, and empty dmgtd.log.

Debugging messages from Resource Manager back-end processes are written to the /var/adm/CSCOpx/log/daemons.log file . This file is cleared every time you restart Resource Manager. If you encounter any problems with Resource Manager, these messages will be valuable in debugging the problem. See the "Troubleshooting" appendix for more information about debugging error messages.

Scheduling Scheme

Resource Manager has a self-contained scheduling mechanism (except Software Management, which uses UNIX cron and at) 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	State
DbServer	Data storage engine	Running normally
DIServer	Import server	Running normally
diskWatcher	Disk space monitor	Running normally
AvInputGen	Availability daemon	Running normally
AvIcmpPoller	Availability ICMP¹ poller	Running normally
AvSnmpPoller	Availability SNMP² poller	Running normally
AvLoader	Availability daemon	Running normally
IcServer	Availability collector	Running normally
SyslogAnalyzer	Syslog message analyzer	Running normally
WebServer	http server	Running normally

Table 4-1: Back-End Process Status

Process Name Process Description State

DbServer

Data storage engine

Running normally

DIServer

Import server

Running normally

diskWatcher

Disk space monitor

Running normally

AvInputGen

Availability daemon

Running normally

AvIcmpPoller

Availability ICMP¹ poller

Running normally

AvSnmpPoller

Availability SNMP² poller

Running normally

AvLoader

Availability daemon

Running normally

IcServer

Availability collector

Running normally

SyslogAnalyzer

Syslog message analyzer

Running normally

WebServer

http server

Running normally

¹ICMP Internet Control Message Protocol.
²SNMP Simple Network Management Protocol.

Table 4-2 describes the possible process (or daemon) 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 Daemon 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 to the Daemon Manager.
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 Daemon 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 to the Daemon Manager.

Transient terminated

The process has completed its function and has terminated normally.

Table of Contents