Table Of Contents

Maintaining and Managing the CMM

Viewing Configuration Files

Viewing Log Files

Viewing the events.log File

Viewing the rmspolld.log File

Viewing Apache Log Files

Viewing Database Files

Viewing Device Configuration Files

Viewing Historical Data

Viewing Standard Multicast MIBs

Including Backup Directories

Maintaining and Managing the CMM

---

This section contains information concerning the underlying operation of CMM and will be of most interest to the System Administrator that supports the application.

This chapter covers:

•Viewing Configuration Files

•Viewing Log Files

•Viewing Database Files

•Viewing Device Configuration Files

•Viewing Historical Data

•Viewing Standard Multicast MIBs

•Including Backup Directories

Viewing Configuration Files

Assuming the application is installed on Solaris, the directory location will be /opt/RMSMMT (on Linux it would be /usr/local/netman). Multicast domain configuration files are kept in /opt/RMSMMT/mmtsys/sys and named <domain>.mm.conf, where <domain> is the name of the multicast domain. The file is in the format of option=value. This file should not be edited manually. The polling daemon configuration files are also kept in this directory. The global polling configuration file is rmspoll.conf, and the domain specific files are rmspoll.<domain>.conf. Like the domain configuration files, these files should be modified only through the browser interface. The only time these files should be modified manually is with the assistance of RMS tech support.

Viewing Log Files

The /opt/RMSMMT/mmtsys/sys directory also contains two log files: events.log and rmspolld.log.

Viewing the events.log File

The events.log file contains syslog type messages, shown below, that correspond to the SNMP traps sent by the polling daemon.

monlo:1082550198:172.16.1.9:1.3.6.1.2.1.31.1.1.1.2.10:0:10:631643:0:50

gone:1082550198:192.168.201.254:239.1.1.1:192.168.1.25:0:0:0:0

hi:1082550198:172.16.1.9:239.1.1.1:192.168.1.25:4116:92785:137:100

This file provides the information for the text-based reports provided by CMM. Depending on the polling interval, and number of objects being polled, this file may grow very quickly. It should be rotated along with all other syslog files on the server.

Viewing the rmspolld.log File

The rmspolld.log file contains log messages pertaining to the polling daemon.

04/23/2004 09:40:54 RMS Polling Agent v2.1(1) started successfully. 

04/23/2004 09:55:49 Exiting on SIGTERM                             

Viewing Apache Log Files

The Apache log files are located in /opt/RMSMMT/httpd_perl/logs. When troubleshooting the application, tailing the error_log file (tail -f error_log) will provide useful information. Additional application information can be logged to the error_log file by adding the line debug=1 to the <domain>.mm.conf file mentioned above.

---

Note Turning on this debug option generates a large amount of data and should be used only for short periods in conjunction with working RMS tech support.

---

Viewing Database Files

The database files used by CMM are located in /opt/RMSMMT/mmtsys/db. The topology database created by running discovery is <domain>.topo.db. The S,G cache, also created during discovery, is <domain>.sg.db. The cache file is recreated when the polling daemon is running and polling the RPs. The lock files associated with each database file should never be manually removed. Removing these files could corrupt the databases.

Each domain also has a /opt/RMSMMT/mmtsys/db/<domain> directory associated with it. This directory contains the IOS versions (iosver.db) for the domain. Multicast forwarding tree baselines are also saved in this directory.

The IP address database (ipaddr.db) is also located in opt/RMSMMT/mmtsys/db.

Viewing Device Configuration Files

If TFTP is enabled on the server, and the SNMP read-write community string is supplied, then the application can download router configurations. The configurations are initially stored in the /tftpboot directory. If a configuration is saved from the "Display Router Config" screen, then a directory will be created (/opt/RMSMMT/configs/<device>) to hold the saved configurations.

Viewing Historical Data

PPS data collected by the polling daemon for S,G threshold polling and Layer 2 switch port polling, are stored in RRD files in /opt/RMSMMT/mmtsys/data.

Viewing Standard Multicast MIBs

Certain versions of IOS now support the standard based IPMROUTE and IGMP MIBs. The STDMIBS file in the /opt/RMSMMT/mmtsys/db controls which IOS versions the standard MIBs will be used for. The file currently contains the following entries:

# This file contains versions of IOS that use the standard multicast MIBs.

12.3.*.*

12.2.*.T*

12.2.*.BC*

Including Backup Directories

To backup application specific data, the following directories should be included in any system backups:

/opt/RMSMMT/mmtsys/data

/opt/RMSMMT/mmtsys/db

/opt/RMSMMT/mmtsys/sys

/opt/RMSMMT/configs

Prior to performing backups, the /opt/RMSMMT/K98mmt script should be run to ensure that files are being changed while the backup is being performed.

---

Note Running the K98mmt script stops the Apache server along with the polling daemon. The S98mmt script will only start the Apache server. The polling daemon has to be started from the browser at this time.

---