Cisco WAN Manager

Document ID: 29005

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
      Configuration Files
The process.conf File
The scmctrlsvr.conf File
The scmcollsvr.conf File
The parserconfig.stats File
The agerconfig.stats File
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document provides information about the different configuration files for the Statistics Collection Manager (SCM).

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

• Cisco WAN Manager 11.0

• Cisco WAN Manager 10.5

• Cisco WAN Manager 10.4

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Configuration Files

These configuration files are in the SCM subsystem:

• process.conf

• scmctrlsvr.conf

• scmcollsvr.conf

• parserconfig.stats

• agerconfig.stats

• scmproxy.conf

This document does not describe all the parameters in these files, but looks at important lines. The document updates Cisco Technical Support when new information comes from the cases.

The process.conf File

The process.conf file contains the Cisco WAN Manager processes that start when the core starts. Two of those processes follow:

scmctrlsvr on on . scmctrlsvr 
scmcollsvr on on . scmcollsvr slavefish

You only need to change the host name argument of the server that runs the SCM control server, which is where scmctrlsvr runs. In this example, the host name argument to change is slavefish. To change the name, use the script cnfcollsvr. You find cnfcollsvr under the scripts directory.

You can offload the parse of statistics from 10.5.10 to a standalone SCM server. You can set a statsparser to parse data locally with a cnfstatsparser script. This script adjusts the entry spwatchdog in the process.conf file.

spwatchdog on off . spwatchdog slavefish

The host name where statsparser runs is slavefish.

The watchdog process that manages statsparser and statsager is spwatchdog. On a Cisco WAN Manager server, the host name for spwatchdog is the name of that Cisco WAN Manager server. On a standalone SCM, the host name can be either of these:

• the name of the server for which the standalone SCM works (which indicates no local statistic data parse)

• the name of that standalone SCM (which indicates local parse)

The scmctrlsvr.conf File

This information is from the scmctrlsvr.conf file:

• MAX_NODE_PER_COLLSVR 250—Defines the maximum number of nodes that a collector can collect.

• MAX_PARALLEL_COLLSVRS 1—Specifies the allowance (2) or nonallowance (1) of dual collection.

The scmcollsvr.conf File

This information is from the scmcollsvr.conf file:

• MAX_NODES 250—The maximum number of nodes that a collector can collect.

• HISTORY_FILES 1—The number of history files that a collector must pull from a node when collection begins. (The recommendation is 0–3.)

The parserconfig.stats File

The argument that follows is important for the Cisco WAN Manager server. On the Cisco WAN Manager server, statsparser can populate either the Stratacom database or the statsdb database. On a standalone SCM, the parser populates statsdb only. (There is no Stratacom database.)

-d 0 : -d is database 0 - stratacom, 1 - statsdb 

The agerconfig.stats File

-d 0 : is similar to parserconfig.stats.

NetPro Discussion Forums - Featured Conversations

Related Information

• Samples and Tips section of Cisco WAN Manager Technical Support
• Cisco WAN Manager Releases
• Software Download - Cisco WAN StrataView Patches ( registered customers only)
• Technical Support - Cisco Systems