Table of Contents

Using Basic Administrative Tools
Maintaining Log Files

On UNIX
On Windows NT

Performing Data Management Tasks
Managing Back-End Processes
Managing Jobs and Resources
Managing Network Events

Administering the CiscoWorks2000 Server

The CiscoWorks2000 Server includes administrative tools to ensure that the server is performing properly:

• Using Basic Administrative Tools---review package options and check log file status.

• Maintaining Log Files---control the size of the log files.

• Performing Data Management Tasks---back up and restore databases.

• Managing Back-End Processes---manage processes to ensure proper operation.

• Managing Jobs and Resources---provide job, resource, and event notification services.

• Managing Network Events---manage the sources that generate events and consumers that receive them.

Using Basic Administrative Tools

You can use these basic administrative tools to perform tasks described in Table 4-1.

Table 4-1: Basic Administrative Tasks

Task	Purpose	Action
View installed software packages.	Lists installed software packages	CiscoWorks2000 Server>Administration> Package Options
View log file status.	Displays log file size and utilization	CiscoWorks2000 Server>Administration> Log File Status

Maintaining Log Files

Log files can grow and fill up disk space. CiscoWorks2000 includes a script that enables you to control this growth.

Files maintained by this script include the following log files:

• Daemon manager

• JRUN

• Web server log files

Most log files are located in directories in the PX_LOGDIR directory. On UNIX systems, this directory is /var/adm/CSCOpx/log and on Windows NT it is $NMSROOT/log. Only JRUN files are not located here; on UNIX machines they are located under NMSROOT/objects,/jrun/jsm-cw2000/logs and on Windows NT they are located in NMSROOT/lib/jrun/jsm-cw2000/logs.

Caution As part of the file back-up procedure, CiscoWorks2000 daemon manager is shut down and restarted. To prevent loss of data, make sure you are not running any critical tasks.

On UNIX

To maintain log files on UNIX:

Step 2 Log in as the superuser and enter the root password.

Step 3 Stop all processes:

• On Solaris: /etc/init.d/dmgtd stop

• On AIX: /etc/rc.dmgtd stop

• On HP-UX: /sbin/init.d/dmgtd stop

Step 4 Perform log maintenance:

$NMSROOT/bin/perl $NMSROOT/cgi-bin/admin/logBackup.pl [-force][-dir destination directory]

where $NMSROOT is the CiscoWorks2000 installation directory, -force allows backup regardless of log file size, and -dir specifies the full path of the destination directory.

Note The target directory must be owned by user bin and group bin. The user must have read, write, and execute permissions, and the group must have at least read permission. Otherwise, the program will terminate with an error message and the log files will not be updated.

Without any options, the script backups up the log files to its default directory, PX_LOGDIR/backup.

Step 5 Verify the procedure was successful by examining the contents of the log files in this location:

/var/adm/CSCOpx/log/*.log

Only log files that reach 90% of their size limits are backed up and the original log file is emptied.

Step 6 Restart the system:

• On Solaris: /etc/init.d/dmgtd start

• On AIX: /etc/rc.dmgtd start

• On HP-UX: /sbin/init.d/dmgtd start

Step 7 Select CiscoWorks2000 > Administration > Log File Status to view your log changes.

On Windows NT

To maintain log files on Windows NT:

Step 2 At the command line, make sure you have the correct permissions.

Step 3 Stop all processes by entering: net stop crmdmgtd

Step 4 Perform log maintenance:

%NMSROOT%\bin\perl %NMSROOT%\cgi-bin\admin\logBackup.pl [-force][-dir destination directory]

where %NMSROOT% is the CiscoWorks2000 installation directory, -force allows backup regardless of log file size, and -dir specifies the full path of the destination directory.

Note If there is a problem, the program will terminate with an error message and the log files will not be updated.

Step 5 Verify the procedure was successful by examining the contents of the log files in the following location:

%NMSROOT%\log\*.log

Only log files that reach 90% of their size limits are backed up and the original log file is emptied.

Step 6 Restart the system:

net start crmdmgtd

Step 7 Select CiscoWorks2000 > Administration > Log File Status to view your log changes.

Performing Data Management Tasks

Regularly perform storage management tasks (see Table 4-3) to ensure that you have a set of database backups in case your current database becomes corrupted or otherwise unusable. When setting up your database backup strategy, consider these guidelines:

• Check the size of the files stored in the backup directory. Some files stored in the backup directory might require additional disk space.

• The backup directory must be writeable by the user bin on UNIX systems.

• Database files are stored using the backup directory structure described in Table 4-2:

  • Format---/generation_number/suite/directory/filename

  • Example---/1/cmf/database/cmf.db

Table 4-2: Backup Directory Structure

Variable	Description	Usage Notes
generation_number	Indicates number of backups	For example, 1, 2, and 3, with 3 being the latest database backup.
suite	Describes application or suite	The CiscoWorks2000 Server suite is cmf. Other optional suites are supported, such as rme or ani.
directory	Describes what is being stored	Directories include database and any suite applications.
filename	Provides name of file that has been backed up	Files include database (.db), log (.log), version (DbVersion.txt), manifest (.tx), tar (.tar), and data files (datafiles.txt).

The suite name used for the CiscoWorks2000 Server database files is cmf. The cmf database includes data backup for the CiscoWorks2000 Server applications. Data management tasks (see Table 4-3) for other suites are also supported. For example, if a suite is installed that uses the ANI Server, the suite name for the ANI Server database files is ani. Refer to the appropriate user guide for suite-specific details.

Table 4-3: Data Management Tasks

Task	Purpose	Action
Backup database.	Performs a database backup now to ensure you have backups if current database becomes corrupted or otherwise unusable	CiscoWorks2000 Server>Administration> Database Management>Back Up Data Now
Schedule regular backups.	Performs database backups on a regular schedule to ensure you have most-recent set of backups if current database becomes corrupted or otherwise unusable	CiscoWorks2000 Server>Administration> Database Management>Schedule Backup
Restore a database.	Replaces damaged or corrupted database with a previously backed up copy	Run script from a command prompt. Refer to the Database Management online help for instructions.

Managing Back-End Processes

CiscoWorks2000 applications use back-end processes to manage application-specific activities or jobs. The process management tools enable you to manage these back-end processes to optimize or troubleshoot the CiscoWorks2000 Server (see Table 4-4). For a description of the CiscoWorks2000 Server processes, refer to the process description table in the online help. For suite-specific processes, refer to the appropriate user guide.

Table 4-4: Process Management Tasks

Task	Purpose	Action
Start process.	Restarts specific processes and displays message, "Running normally"	CiscoWorks2000 Server>Administration> Process Management>Start Process
Stop process.	Stops process and displays message, "Administrator has shut down this server"	CiscoWorks2000 Server>Administration> Process Management>Stop Process
View processes.	Displays process information including state, ID, and other data	CiscoWorks2000 Server>Administration> Process Management>Process Status
View process failures.	Displays the failed process, failure information, and time failure occurred	CiscoWorks2000 Server>Administration> Diagnostics>Process Failures

Managing Jobs and Resources

Job Management provides job, resource, and event notification services to CiscoWorks2000. Use Job Management to browse jobs, release resources and stop and remove jobs (see Table 4-5).

Table 4-5: Job Management Tasks

Task	Purpose	Action
Cancel a scheduled job.	Stops job from running, but keeps it in the Job Management	CiscoWorks2000 Server>Administration> Job Management, then select Stop Job
Remove a job.	Removes job from the Job Management	CiscoWorks2000 Server>Administration> Job Management, then select Remove Job
Unlock an orphaned resource.	Frees resources inadvertently locked due to a system failure Note Use Free Resource only if there are no other options.	CiscoWorks2000 Server>Administration> Job Management, then select Free Resource

Managing Network Events

The Event Distribution Service (EDS) allows you to manage event sources and event consumers. Event sources create network events and event consumers are the recipients of the events (see Table 4-6).

Table 4-6: Event Distribution Tasks

Task	Purpose	Action
Enable or disable debugging or trace message generation.	Diagnosis problems.	CiscoWorks2000 Server>Administration> Event Management>Event Channel Admin, then select Debug
Configure individual services.	Enables setup and configuration of event source or event consumer services, such as queue parameters.	CiscoWorks2000 Server>Administration> Event Management>Event Channel Admin, then select Configure
Associate event filters with a generic consumer.	Enables you to use a filter to specify which events should be passed to each generic consumer.	CiscoWorks2000 Server>Administration> Event Management>Event Consumer Admin
View performance statistics for all internal data queues for the event sources and event consumers.	Displays the work being done by EDS. From these statistics, you can determine whether events are being lost and the high-water mark for setting queue capacity.	CiscoWorks2000 Server>Administration> Event Management>Event Channel Admin, then select Performance
Search the Event Channel log for events that match specific criteria.	Searches and groups events to aid in problem determination.	CiscoWorks2000 Server>Diagnostics> Event Query
View events received from EDS and the event logger.	Monitors or troubleshoots your network.	As a superuser, enter: /opt/CSCOpx/bin/eds -display

Posted: Wed Apr 5 14:40:00 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.