Cisco WAN Manager Installation and Configuration Guide, 12.0
Statistics Collection Manager Configuration
Downloads: This chapterpdf (PDF - 228.0KB) The complete bookPDF (PDF - 3.1MB) | Feedback

Statistics Collection Manager Configuration

Table Of Contents

Statistics Collection Manager Configuration

Description of Modules

Integrated Statistics Collection Manager

Standalone Statistics Manager

Standalone Statistics Collector

Combining SCM, SSM, and SSC Configurations

User Configuration

SCMProxy

SCMGateway.conf

Setting Up the SCM Configurations

Configuring with the SCMGateway.conf File

Changing the CWM machine to which SSM is pointing

Getting the SSM main menu

Setting up the SCM domain list

Setting Up a SCM forcedswitchover list

Setting Up a Redundant SSM on CWM host


Statistics Collection Manager Configuration


The CWM Statistics Collection Manager (SCM) software is comprised of three major modules as follows.

Integrated Statistics Collection Manager

Standalone Statistics Manager (SSM)

Standalone Statistics Collector (SSC).

These modules can be configured in a wide variety of ways allowing both high performance and high level redundancy to suit users' needs.

This appendix describes:

Each of these modules.

The variety of ways in which these modules can be installed to suit different network needs.

Description of Modules

This section provides a description of each of the SCM modules.

Integrated Statistics Collection Manager

The Integrated Statistics Collection Manager (SCM) resides and operates within the same workstation as the CWM server. When CWM is installed, the Integrated SCM is always installed automatically.

An example of a CWM server workstation with Integrated SCM is shown in Figure A-1.

Notice that the Integrated SCM is made up of a Statistics Controller to manage the stats collection function, a Statistics Collector to perform the actual stats collection, and a Statistics Parser that parses stats files into the stats database.

Figure A-1 CWM with Integrated SCM

Standalone Statistics Manager

The Standalone Statistics Manager (SSM) resides in a separate workstation and not in the CWM workstation. The installation of SSM is quite independent of CWM and is installed from the SSM/SSC CD.

The purpose of this separation is to achieve better performance through the use of a dedicated workstation (instead of sharing the hardware with the CWM functions). Figure A-2 shows a system consisting of one CWM host and one Standalone Statistics Manager. There are several things to note.

Communication between CWM and SSM is through WANDEST; a WANDEST Server resides in the CWM machine and a WANDEST Client resides in the SSM machine. The WANDEST Client is part of SSM and is installed automatically when SSM is installed. WANDEST Server is a separate Cisco product and is not part of the CWM product, it must be ordered and installed separately.

The statistics database resides on the SSM machine and can only have the statsdb format and features, the user cannot save statistics in stratacom in the SSM machine.

Figure A-2 shows no statistics functions in the CWM host. In reality, the Integrated SCM does exist in the CWM host but is not activated. However, this need not be the case, the Integrated SCM could be activated so that both the CWM host machine and the SSM machine are collecting statistics.

Figure A-2 CWM with Standalone Statistics Manager

Standalone Statistics Collector

Under the control of the Statistics Controller, the Standalone Statistics Collector (SSC) uses FTP (or TFTP) to collect statistics from the network nodes and place them in directories for parsing by the Statistics Parsers.

The SSC resides in a separate workstation, not in the CWM workstation and not in the SSM workstation. The installation of SSC is quite independent of CWM and is installed from the SSM/SSC CD

Figure A-3 shows a configuration in which the statistic collection function is further decoupled from the CWM host and the SSM. The diagram shows one CWM workstation, one SSM workstation, and one SSC workstation.

With this configuration, the statistic collection functions are spread across two workstations and do not use the resources of the CWM host. In this way, the maximum number of network nodes and connections which can be supported is increased.

Using SSMs and SSCs, there are several other configuration types that can improve performance and provide redundancy. These configuration types are discussed later in this appendix.

Figure A-3 Standalone Statistics Collector

The figure shows how the Statistics Controller manages both the Statistics Collector and the Statistics Parser. The Statistics Controller communicates with CWM to obtain details about the network nodes. When CWM and the Statistics Controller are in different workstation, they use WANDEST (server and client) to communicate with each other. The Statistics Controller also communicates with the SCM Gateway to the network. This gateway is separate from the CWM Gateway.

The statistics are collected by the Statistics Collector, passed to the Statistics Parser and then stored in the statistics database.

Combining SCM, SSM, and SSC Configurations

SCMs, SSMs, and SSCs can be combined to accommodate a wide variety of network need regarding performance (maximum nodes and connections supported), database storage, and redundancy.

In general the following rules apply.

Multiple SSMs can be configured to be primary or secondary so that a secondary can take over automatically the functions of a failed primary

Multiple SSMs and SSCs can be configured to that they duplicate each other's functions. For example, two SSCs can be collecting statistics from the same nodes at the same time. In this way, if there is a failure of one, the other SSC continues stats collection without interruption.

SSMs are where the statsdb databases reside. Multiple SSMs, therefore, increase the database storage capacity and provide the safety of spreading the collected statistics across several independent workstations.

Some examples follow.

Figure A-4 shows a configuration in which there is one SSM and three SSCs. Each SSC collects statistics for a particular set of nodes and the statistics collected from all three SSCs are stored in a single statsdb database in the SSM. As shown in the diagram, no redundancy is provided. If an SSC fails, the statistics for its nodes are no longer collected. If the SSM fails, all statistics collection stops.

Figure A-4 Multiple SSCs

This basic configuration can be modified in a variety of ways to provide redundancy. For example, the SSM can be backed up by one or two standby SSMs (designated Secondary and Tertiary) so that a standby can take over automatically in the event of a failure in the Primary. Also, multiple SSCs can be configured to collect statistics from the same network nodes.

The following figures provide examples of redundant configurations.

Figure A-5 shows a configuration in which two SSMs are each used with its own SSCs. This configuration permits two redundancy schemes.

In the first scheme, one SSM is designated as a primary and the other as a secondary which is in standby mode. The primary collects statistics and stores them in its statsdb database. If the primary fails, the secondary takes over the statistics collection automatically storing statistics in its statsdb database. The statistics collected before the failure continue to reside in the primary's database. This arrangement requires that an SCM Gateway be configured between SSM1 and SSM2. The configuration is specified through the SCMGateway.conf file that resides in the CWM server in /usr/users/svplus/config.

The second scheme is to have both SSMs running independently with each storing statistics in their own databases through their own SSC. If the SSCs on SSM 1 and the SSCs on SSM 2 are configured to collect statistics from the same set of nodes, the result is two independent collections systems with each duplicating the functions of the other. This configuration, therefore, provides complete redundancy.

Figure A-5 Redundant SSMs and SSCs

Figure A-6 shows a configuration which is merely an extension of the previous example. Each of the two SSMs have multiple SSCs. For a particular SSM, each of the SSCs can be assigned to its own set of nodes in the network.

Figure A-6 Extended SSM and SSC Redundancy

User Configuration

The user can configure the stats collection functions either through an SCM GUI in CWM or through ScmProxy (For details about configuring through the SCM GUI, please refer to the Cisco WAN Manager User Guid)e.

Configuration of the SCM gateways is accomplished through the SCMgateway.conf file.

SCMProxy

ScmProxy is a software module that resides in the CWM host and provides an alternative user interface to the GUI. To launch scmproxy, the user is first required to create a nodelist file that specifies the nodes from which statistics are to be collected. This list has the following format.

<CollParams:<templateName><primary,secondary,tertiary collsvrNames ><iprouting>> 
node_name1 
node_name2 
... 
node_nameN 
<CollParams:<templateName><primary,secondary,tertiary collsvrNames ><iprouting>> 
node_name1 
node_name2 
... 
node_nameN
Example:
<CollParam:<MGX8850_template><ssc1,ssc2,ssc3><inband>> 
jbpop1-1 
<CollParam:<MGX2_test><ssc3><inband>> 
UpperRed 
popeye13.

The file consists of a number of records where each record specifies the stats template to be used, a collection server/parser server pair, and a list of nodes in the network for which the servers are collecting statistics.

template_name: This is the name of the applicable template. Statistics templates can be created from the SCM GUI and saved in StrataCom database.

primary, secondary,tertiary collsverNames: This item specifies the names of the primary, secondary, and tertiary collection serves.

routinginfo: This field can be "in-band" or "outband." The field depends on the routing method to the nodes.

node_name1, node_name2, etc. are node names in the network that the servers are collecting statisitics.

ScmProxy must be started from the CWM host machine by typing:

scmproxy<nodelist_filename> where "nodelist_filename" is the name the user has given to node list file.

ScmProxy then displays a menu from which the user can select from the following options.

Enable Statistics

Disable Statistics

Start Collection

Stop Collection

Exit the program

SCMGateway.conf

The SCM gateways used for statistics collection are defined independently of the CWM gateways used for CWM (this separation of gateways is new in this release and different from earlier releases). The user specifies the network gateways to be used for statistics collection through the SCMGateway.conf file with the following format.

## Default: DomainGatewayList 
## Usage: DomainGateWayList tmonda dilbag sgharat 
DomainGatewayList SCM1 SCM2 SCM3

In this example, SCM1, SCM2, and SCM3 are the names of the SCM gateways.

Setting Up the SCM Configurations

Setting up SCM configurations with standalone servers consists of the following steps.


Step 1 Plan the number of workstations to be used for statistics collection. Determine the number for statistics management and the number for statistics collection.

Step 2 List the network nodes to be associated with each Statistics collector.

Step 3 For each workstation install CWM, SCM, or SCC as appropriate.

For the CWM server machine this installation is performed automatically as part of the CWM installation. For each standalone machine choose the appropriate installation options according to the plan developed in step 1.

Step 4 Start CWM.

Step 5 Using either the SCM GUI in CWM or ScmProxy, set up the planned configuration (see Cisco WAN Manager User Guide, Release 12 for details).


Configuring with the SCMGateway.conf File

This section describes how to setup an SSM using the SCMGateway.conf file.

Changing the CWM machine to which SSM is pointing

When installing SSM, the user is prompted to enter the name of CWM machine to which it points. To change the CWM machine after installation, use the updatescminfo script by entering
updatescminfo <CWM hostname>"

Getting the SSM main menu

Type SCM in command line.

Setting up the SCM domain list

In the SCMGateway.conf, add the a list of SCM gateways in "DomainGatewayList" section. (for example, DomainGatewayList <hostname_1> <hostname_2> <hostname_3>...).

Setting Up a SCM forcedswitchover list

In SCMGateway.conf, add the other machine's name in "ForcedSwitchOver" section (for example, ForcedSwitchOver <new primary hostname>).

When a forcedswitchover occurs, the primary role is transferred to this remote machine.

Setting Up a Redundant SSM on CWM host

In SCMGateway.conf, specify the remote SSM list in "RedundantSCMList" section (for example, if cwm1, cwm2 are the StandAlone SSM's and cwm0 is a cwm machine, the SCMGateway.conf on cwm0 should be RedundantSCMList cwm1 cwm2).


Note This is the only way for the SCM Gateway on the local machine to know the presence of other SCM Gateway.