Cisco WAN Manager User's Guide, 12.0 - Collecting Statistics [Cisco WAN Manager]

Table Of Contents

Collecting Statistics

Statistics Collection Modules

Statistics Overview

Types of Statistics

Statistics Collection Manager Functions

SCM Gateway Support

Managing with Statistics Collection Manager

Assigning Network Nodes for Statistics Manager

Verifying the IP Address

Launching the Statistics Collection Manager

Launching the Standalone Statistics Manager

Navigating with Statistics Collection Manager

Statistics Collection Manager Main Window

Statistics Collection Manager Menus

Refreshing the Statistics Collection Manager Window

Configuring the Statistics Collection Manager Statistics Database

Configuring the Standalone Collector

Adding the Standalone Collector

Deleting the Standalone Collector

Enabling Statistics

Editing Templates

Deleting Templates

Disabling Collection Statistics

Starting and Stopping the Collection Process

Monitoring the Collection Process

Configuring the ScmProxy

Creating the ScmProxy Node List

Launching the ScmProxy

Collecting Statistics

This chapter describes how to collect statistics by using Cisco WAN Manager (CWM).

Contents of this chapter include:

•Statistics Collection Modules

•Statistics Overview

•Managing with Statistics Collection Manager

•Configuring the ScmProxy

Statistics Collection Modules

The following modules comprise the CWM Statistics Collection Manager (SCM):

•Integrated Stats 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.

•Standalone Stats Manager (SSM)—Resides in a separate workstation and not in the CWM workstation. CWM and SSM communicate through WANDEST. A WANDEST server resides in the CWM machine and a WANDEST client resides in the SSM machine. The statistics database resides on the SSM machine and has only the statsdb format and features. SSM always points to a primary CWM machine.

•Standalone Stats Collector (SSC)—Resides in a separate workstation and not in the SSM workstation. With this configuration, the statistic collection functions are spread across two workstations and do not use the resources of the CWM host. The maximum number of network nodes and connections that can be supported is increased.

Integrated SCM, SSM, and SSC can be combined to accommodate a wide variety of network needs regarding performance, for example, maximum nodes and connections supported, database storage, and redundancy.

For more information about configuring the Integrated SCM, SSM, and SSC, refer to the Cisco WAN Manger Installation Guide for Solaris 8, Release 12.

Statistics Overview

Statistics are numerical values derived from the contents of event counters that are located on the service modules in the switch. The counters record the number of occurrences for a particular network event, for example, the number of cells that are transmitted or received on a specific trunk. A single switch contains separate counters for hundreds of discrete network events.

The event counters on the service modules continue to accumulate the counts of network events whether or not the counters are ever read by an operator or collected by the CWM station. If the content of a counter is read by you or by another application, the counter value is defined as a statistic. A single statistic refers to a counter value for a single entity, for example, a user connection. If you enable statistics for ATM connections on a node and that node has 1000 connections, you are dealing with 1000 entities that is associated with a separate set of counters. If you requested CWM to collect ten different statistics for each user connection, for example, the number of cells transmitted and received, cells discarded with CLP=0, cells discarded with CLP=1, and so forth, this results in the collection of 10,000 statistic values from that node alone on every collection cycle.

Contents of this section include:

•Types of Statistics

•Statistics Collection Manager Functions

Types of Statistics

Table 7-1 lists the types of statistics.

Table 7-1 Statistics Types

Name

Description

Summary Statistics

Specifies that the summary statistics are accessible through the command line interface (CLI), for example, the dspchstats command on the Cisco BPX series or the dspchancnt command on the Cisco MGX nodes. Summary statistics, which is also referred as real-time statistics, can also be accessed using SNMP.

Summary or real-time statistics are not collected by CWM.

Interval Statistics

Provides a record of the number of events over a specific period of time, for example, the previous
30 minutes.

Interval statistics are also known as history statistics, and are derived from the same event counters as summary statistics.

Note Interval statistics are collected by CWM.

The following subtypes are supported:

Name

Description

TFTP Statistics

Enables all active instances of a given entity on one or all nodes of a certain type. For example, you can enable trivial file transfer protocol (TFTP) statistics for all BXM ATM trunks on all Cisco BPX nodes in the network.

TFTP statistics are called bulk statistics that are enabled and collected by SCM. TFTP statistics are stored in the CWM statistics database and are used for performance monitoring and user billing applications.

User Statistics

Tests user statistics that are enabled through node CLI commands, for example, cnftrkstats command. User statistics are enabled for a single entity one node at a time.

Auto Statistics

Supports the statistical alarm feature on network switches. Auto statistics are automatically enabled through switch software once a given network element such as a card, line, or trunk is activated.

Note Before setting up CWM for statistics collection, you must decide how often and what type of statistics to collect.

The following statistic examples are used:

•Performance monitoring at network and element levels

•Resource and capacity planning

•Threshold crossing alerts, for example, alarms

•Usage records for billing

•Traffic management

Statistics Collection Manager Functions

The following functions for statistics collection are

•Collect statistics.

•Enable statistics.

•SCM Standalone Collector.

•Statistics collection in SCM is always timed based.

•History Files Collection specifies that the history files collection is set from one to a maximum of three files for a collection. The default for the history files collection is set to one.

•If SCM Gateway is not configured, dual Collection is applicable to all nodes in SCM. SSM points to the primary CWM to get data and traps.

The following statistics are

•QBin stats and virtual port stats for BPX.

•WingZ provides an adhoc statistics report.

•Additional statistic types for a FRSM PVC connection and port, AUSM port, and PXM1 card statistics on PXM1-based switches (Cisco MGX 8850, Cisco MGX 8250, and Cisco MGX 8230). For more detailed information, refer to the Cisco WAN Manager Database Interface Guide,
Release 12 and Release Notes for Cisco WAN Manager 12.

Note•Before collecting the PNNI SPVC/P connection statistic on CWM, use the cnfpnstat command on the switch to enable the PNNI statistics. If you do not enable the PNNI statistics collection on the switch first, the statistics file will not have any statistics.

For more information about the cnfpnstat command, refer to the Cisco MGX 8830,
Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference, Release 4.

•On PXM45, the PNNI statistics are supported only on PXM45B/C.

•Peak interval is not supported on PNNI statistics. 15 minute collection interval is supported only.

SCM Gateway Support

Statistics collection is populated from the Primary SCM to the Secondary SCM. Primary gateways save enabling information and forward data to the Secondary host through the Stats Master.

SCM provides a gateway and domain different from the CWM Gateway.

By configuring the SCM Gateway, statistics collection is started only on a Primary SCM machine. The Secondary SCM acts as a redundant stats machine for the Primary SCM machine. If a gateway switchover is done or if the Secondary machine becomes the Primary SCM, the new Primary machine takes over the statistics collection for all the nodes and cards managed by the previous Primary machine. The statistics data, which is collected by the new Primary machine, is parsed into its own database and is located in both the previous and new Primary machines. The Stats Reporting Tool queries the database in both machines to get the statistic data.

For information about SCM configuration and SCM Gateway configuration, refer to the Cisco WAN Manager Installation Guide for Solaris 8, Release 12.

To display the SCM Gateway Monitor, complete the following procedure:

Step 1 Choose Apps > SCM Gateway Monitor.

Figure 7-1displays the SCM Gateway Monitor.

Figure 7-1 SCM Gateway Monitor

Step 2 Click Det to detect state of the connection either Up or Down.

Figure 7-2 displays the detection window.

Figure 7-2 SCM Gateway Monitor: Detection

Step 3 Click Close to close the detection window.

Step 4 Click Close to exit the SCM Gateway Monitor.

Managing with Statistics Collection Manager

This section describes how to manage SCM for SSM and SSC.

The following configuration tasks are used:

•Assigning Network Nodes for Statistics Manager

•Launching the Statistics Collection Manager

•Launching the Standalone Statistics Manager

•Navigating with Statistics Collection Manager

•Configuring the Statistics Collection Manager Statistics Database

•Configuring the Standalone Collector

•Enabling Statistics

•Editing Templates

•Deleting Templates

•Disabling Collection Statistics

•Starting and Stopping the Collection Process

•Monitoring the Collection Process

Assigning Network Nodes for Statistics Manager

If the node or nodes are actively managed by CWM, you must define the statistics manager that is the only CWM station permitted to enable and disable statistics collection on that specific node. You can have multiple masters in the network, but a node responds to enable and disable commands only from that CWM station that is defined as the manager.

You must access the node CLI to configure the Statistics Manager. A manager must be defined for every node where you want to collect statistics, which is both routing nodes and feeder nodes.

To assign network nodes for the statistics manager, complete the following procedure:

Step 1 Open a terminal window.

Step 2 Enter the nslookup <machine-name> command or the configured IP address to locate the IP address of the machine as shown in the following example:
tballraker2% nslookup tballraker2
tballraker2%
Replace <machine-name> with the name of the applicable machine. The example shows that tballraker2 is the machine name.

Step 3 Depending on the node, enter the applicable command to configure the statistic master:

a. Enter the cnfstatsmgr <IP address> command for Cisco MGX 8850 (PXM1), Cisco MGX 8220, Cisco MGX 8250, Cisco MGX 8230 as shown in the following example:
M8950_SF.7.PXM.a > cnfstatsmgr 172.28.131.96
M8950_SF.7.PXM.a >
Replace <IP address> with the local area network (LAN) interface that connects the CWM station to the network. The example shows that 172.28.131.96 is the IP address.

b. Enter the cnfstatmast <IP Address> command for Cisco BPX switch or Cisco IGX switch.

Replace <IP address> with the local area network (LAN) interface that connects the CWM station to the network.

c. Enter the cnfstatsmgr <index> <IP Address> command for Cisco MGX 8830 (PXM1E),
Cisco MGX 8850 (PXM1E and PXM45), Cisco MGX 8950, or Cisco SES node as shown in the following example:
M8950_SF.7.PXM.a > cnfstatsmgr 4 172.28.131.96
M8950_SF.7.PXM.a >
Replace <index> with 4 that defines the master statistics manager.

Replace <IP address> with the LAN interface that connects the CWM station to the network. The example shows that 172.28.131.96 is the IP address.

Step 4 Enter the dspstatsmgr command to display the current statistics manager setting for the active controller card on a Cisco MGX node. The following example shows the statistics manager setting for IP address 172.28.131.96:
M8950_SF.7.PXM.a > dspstatsmgr
 Statistics Manager     IP Address
 ------------------     ----------
 Primary                0.0.0.0 
 Secondary              0.0.0.0 
 Tertiary               0.0.0.0 
 Statistics Master      172.28.131.96 
M8950_SF.7.PXM.a >
Verifying the IP Address

This section describes how to verify that the IP address for the CWM station is registered.

Note This procedure is applicable only for Cisco MGX 8830 (PXM1E), Cisco
MGX 8850 (PXM1E and PXM45), Cisco MGX 8950, Cisco MGX 8850 (PXM1), Cisco MGX 8220, Cisco MGX 8250, Cisco MGX 8230, or Cisco SES node.

To verify that the IP address of the CWM station is registered, complete the following procedure:

Step 1 Open a terminal window.

Step 2 Enter the dsptrapmgr command to verify that the IP address of the CWM station is registered. The following example is shown:
M8950_SF.7.PXM.a > dsptrapmgr
     ipAddress     PortNum  RowStatus   ReadTrapFlag  NextTrapSeqNum
  ---------------  -------  ----------  ------------  --------------
  172.29.52.25      2500       Add           Off       520
  LastTrapSeqNum:     1019
  NumOfValidEntries:  1
M8950_SF.7.PXM.a >
Launching the Statistics Collection Manager

To launch the Statistics Collection Manager (see Figure 7-3), choose Apps > Statistics Collection Manager or click the Statistics Collection Manager icon from the toolbar.

Figure 7-3 Statistics Collection Manager Main Window: Enabling View

1

Menu bar

2

Browse window

3

View selection tabs

4

Statistics list pane

5

Collection parameters pane

—

—

Launching the Standalone Statistics Manager

The WANDEST client is bundled with the SSM installation and SSM has a wrapper script for WANDEST client. The script takes the uploaded data and puts it into the stratacom database. The logging for the script is located in the /usr/users/svplus/log/scmupload.log directory.

If CWM is in the gateway, WANDEST uploads and traps are always received from the primary CWM. For more information about installing and setting up the configuration for SSM, refer to the Cisco WAN Manager Installation Guide for Solaris 8, Release 12.

To launch the standalone statistics manager (SSM), complete the following procedure:

Step 1 Open a terminal window.

Step 2 When the login prompt appears, you must:

a. Enter the login name svplus.

b. Enter the password svplus.

The following example is shown:
login: svplus
Password: 
Last login: Mon Mar  3 09:28:17 from dhcp-171-71-29-
Sun Microsystems Inc.   SunOS 5.8       Generic February 2000
You have new mail.
tballraker2%
Note The default configured username is svplus and the password is svplus. For information about how to change the default configured password, see "Getting Started with Cisco WAN Manager."

Step 3 At the prompt, enter SCM. See the following screen.
tballraker2% SCM
Welcome to Standalone Statistics Manager Release 12.0.00_Feb19.SOL28 W3
 Standalone Statistics Manager is being run from the workstation, "tballraker2"s
              MAIN MENU 
              --------- 
             1) Start SCM core
             2) Stop SCM core
             3) Start SCM GUI
             4) DB Upload from CWM
             x) Exit
enter number or x to exit:
Step 4 To select any of the Standalone Statistics Manager main menu options listed in Table 7-2, specify the number and press Return.

Table 7-2 SSM Main Menu Options

Menu Option

Description

1) Start SCM core

Starts the core processes for SCM, for example, watchdog, SCM control server, SCM collection server, statsparser, cwmftpd, and so forth. SCM also uploads data from the WANDEST server in CWM.

2) Stop SCM core

Stops the watchdog and all processes that are running on the SSM machine in relation to the SSM.

3) Start SCM GUI

Starts the SCM graphical user interface for SSM.

4) DB Upload from CWM

Forces upload of data from the WANDEST server.

x) Exit

Exits SCM.

Step 5 Enter option 1 (Start SCM core) to start the SCM core process at the prompt.

Press Return.

Observe the messages that are displayed.

Step 6 Enter option 3 (Start SCM GUI) to launch the standalone SCM. See Figure 7-3 for the Statistics Collection Manager main window.

Note The standalone SSM displays the same main window and interface as the SCM.

Navigating with Statistics Collection Manager

The following sections describe the navigation of statistics collection manager:

•Statistics Collection Manager Main Window

•Statistics Collection Manager Menus

•Refreshing the Statistics Collection Manager Window

Statistics Collection Manager Main Window

After launching the SCM or standalone statistics manager applications for the first time, you will see a root node called the Enabling Root in the left panel of the window (see Figure 7-3). The Statistics Collection Manager main window includes six options (see Table 7-3).

You can toggle between three views by clicking the Enabling View, Collecting View, or Monitoring View tabs (see Figure 7-3).

Table 7-3 Statistics Collection Manager Main Window Options

Options

Task

Menu bar

For a definition, see Table 7-4.

Browse window

Provides a hierarchical list of all networks discovered by CWM, and beneath each network all nodes are listed and grouped by platform and card types.

By viewing a hierarchical list of network elements, you can:

•Select a node to edit the collection parameters or to begin or end statistics collection.

•Select a specific node or element to configure statistics collection.

•Display the statistics collection parameters after selecting a node.

View selection tabs

Displays the following tab views:

Note Only the Monitoring View tab provides tab options.

Tab Option

Tab Task

Enabling View

Displays the network nodes and elements.

Collecting View

Accesses statistics collection.

Monitoring view

Tab Option

Tab Task

Log

Displays the collection log pane.

Monitor

Provides the activity for the current hour that includes the number of files for each node in active collection mode.

Statistics list pane

Displays the selected statistics for the node or nodes highlighted in the hierarchy tree from the browse window.

Collection parameters pane

Displays the current collection parameters for the node or nodes highlighted in the hierarchy tree from the browse window.

Statistics Collection Manager Menus

The menu bar provides available menu options for the SCM and standalone SCM applications.

The options and functions are listed in Table 7-4.

Table 7-4 Statistics Collection Manager Menu Bar

Menu-Bar Options

Task

File

New SCM GUI¹

Launches a new instance of SCM. You can launch up to four SCM instances.

Close

Closes the current instance of SCM.

Exit¹

Exits all instances of the SCM.

Enabling

Edit Current Collection Parameters

Edits the current collection parameters.

Edit with Default Parameters

Edits the current collection parameters with default parameters.

Edit with Template

Edits with the template.

Disable Collection Statistics

Disables collection statistics.

For more information, see the "Disabling Collection Statistics" section.

Edit Template

Edits the template.

For more information, see the "Editing Templates" section.

Delete Template

Deletes a template.

For more information, see the "Deleting Templates" section.

Collecting

Start Collection

Begins collecting statistics from the selected nodes if the node has enabled statistics.

Note The start collection option is not enabled unless statistics are enabled for a network element.

For more information about starting a collection, see the "Starting and Stopping the Collection Process" section.

Stop Collection

Stops collecting statistics from the selected nodes if the statistics are already being collected.

For more information about stopping a collection, see the "Starting and Stopping the Collection Process" section.

Configuration

Stats DB Configuration

Sets statistics parameters for the file and database that includes save statistics files, purge file, purge interval, and password.

For more information, see the "Configuring the Statistics Collection Manager Statistics Database" section.

Standalone Collector Configuration

Adds or deletes standalone statistics collectors for SSM in CWM.

For more information, see the "Configuring the Standalone Collector" section.

Apps

SCM Gateway Monitor

Displays the SCM gateway monitor window (see Figure 7-1).

Help

Displays the server and client versions.

¹This option is available only for SSM.

Refreshing the Statistics Collection Manager Window

SCM provides a window refresh option to display all changes made to the node configurations.

Note The window refresh option applies only to primary, secondary, and tertiary configurations.

To refresh the SCM window, complete the following procedure:

Step 1 Double-click the root node to collapse the expanded hierarchical tree.

Step 2 Expand the tree again to see the new configuration.

Configuring the Statistics Collection Manager Statistics Database

Prior to starting the collection process, several parameters relating to the statistics database require review and possibly configuration. Depending upon the selection, the statistics database configuration parameters must be checked along with the in band and out-of-band addresses. TFTP and FTP are used to transfer files using the network IP address for in-band communications, and the LAN IP address for out-of-band communications.

To configure the SCM statistics database, complete the following procedure:

Step 1 Choose Configuration > Stats DB Configuration to display the Stats DB Hosts Configuration Dialog (see Figure 7-4).

Figure 7-4 Stats DB Host Configuration Dialog

Step 2 Choose the name of the CWM host where the statistics database is located in the Stats DB Host drop-down arrow.

Step 3 Click either yes or no radio buttons to enable or disable parsed data in the Parsing Data area.

If yes, the stats parser process takes the file collection by the collection server and parses the data and puts it into the database.

If no, the stats parser process takes the file and puts it into the purge directory. The stats parser does not parse and does not put the data into the database.

Step 4 From the Statistics File Configuration area, you must:

a. Click the Save radio button to save the statistics files on the collection server host.

The toggle controls the ability to save files as they are parsed from the statistics parser. If you click the Do not Save radio button, the statistics files are not placed into the /usr/users/svplus/purge directory.

Note The save directory is not configurable.

The default is Save.

b. Specify the directory that is used to store incoming files to be parsed in the Save to Directory field.

c. Click the Purge radio button to automatically purge the saved files in the Purge File area. If you click the Do not Purge radio button, the purged files are not deleted from the /usr/users/svplus/purge directory.

Note Cisco recommends that you delete old files.

The default is Purge.

d. Specify the number of configurable days which old files are purged from the /usr/users/svplus/purge directory when space in your hard disk's incoming partition drops below 20 MB in the Purge Interval (days) field.

The files with a date "N" days older than today's date are purged. "0" means that no purging is done.

The range is from 1-366 days. The default is three days.

Step 5 From the Statistics Database Configuration area, you must:

a. Determine how many hours the statistics files are retained on the DB Host prior to being purged.

b. Enter the applicable hours for the data that needs to be maintained by the CWM database in the Purge Interval (hours) field.

Note If the database contains insufficient space for statistics storage, the statistics collection process can shut down. If so, reduce the purge interval to twelve hours.

The range is from 1-8784 hours or one year. The default is 24 hours.

Step 6 From the Statistic FTP Configuration area, you must:

a. Enter the file transfer protocol (FTP) username in the User Name field.

The default is svplus.

b. Enter the FTP password in the Password field.

Note Asterisks are displayed.

c. Reenter your FTP password for confirmation in the Confirm Password field.

Step 7 Click Apply to apply the configuration parameters for the selected Stats DB Host.

Step 8 Click OK. The following message is shown:
Successfull Configure
Configuring the Standalone Collector

This section describes the following configuration tasks for the SSC:

•Adding the Standalone Collector

•Deleting the Standalone Collector

Adding the Standalone Collector

To add the standalone collector, complete the following procedure:

Step 1 Choose Configuration > Standalone Collector Configuration.

Figure 7-5 displays the SSC Configuration dialog.

Figure 7-5 SSC Configuration Dialog

Step 2 Enter the applicable name for the collector.

Step 3 Click Add to add the collector.

Deleting the Standalone Collector

To delete the standalone collector, complete the following procedure:

Step 1 Choose Configuration > Standalone Collector Configuration to display the SSC Configuration dialog (see Figure 7-5).

Step 2 Select the applicable collector that you want to delete.

Step 3 Click Delete to delete the collector.

Enabling Statistics

This section describes how statistics are enabled for collection on a node. The example used is to enable statistics collection for an AXSME card for an ATM connection on a Cisco MGX 8850 (PXM45) node. The same process applies to other objects and node types. The term object applies to the following network statistics that are enabled:

•cards

•connections

•lines

•ports

•trunks

Depending upon the process, Table 7-5 lists the letter indicators.

Table 7-5 Statistics View Definitions

Letter

Definition

I

Inactive

E

Enabled

C

Actively Collecting

To enable statistics for an AXSME card for an ATM connection on a Cisco MGX 8850 (PXM45) node, complete the following procedure:

Step 1 From the Browse window, right-click a single node or all nodes of the same platform type and choose Edit with Default Parameters or choose Enabling > Edit with Default Parameters.

Figure 7-6 displays the Statistics Enable Dialog.

Note Statistics Enable is accepted only from the CWM machine, which is registered as Statistics Master on the nodes. For information about configuring statistics manager, see the "Assigning Network Nodes for Statistics Manager" section.

Figure 7-6 Statistics Enable Dialog

Step 2 Choose the applicable card type from the Card Family drop-down arrow. The example (see Figure 7-6) shows axsmeoc3-12_50.

Note The card types differ according to the node type.

Step 3 Choose the object type for the collection. The example (see Figure 7-6) shows Conn-AXSME_ATM_conn.

For an AXSME card, the choices include connection, line, port, and physical line.

Once an object is selected, a list of available statistics for that object type is displayed in the Unselected pane.

Step 4 Choose one, all, or any combination of statistics to be enabled for the collection.

Step 5 Move the applicable statistics to the Selected pane. If necessary, you can repeat the process for additional objects and statistics sets.

Step 6 Enter the peak interval in the Peak Interval (Sec) field. The default value is 300 sec.

Note The collection of peak value statistics is enabled separately.

Step 7 Once you are satisfied with the object and statistics selections, click Next to view the Statistics Enable Dialog (see Figure 7-7).

Figure 7-7 Next Statistics Enable Dialog

The Statistics Enable Dialog allows you to alter the collection parameters for the selected node or nodes.

Table 7-6 describes the modifiable statistics collection parameters and descriptions.

Table 7-6 Statistics Collection Parameters

Parameter

Description

Collection Period (Minutes)

Defines the interval between statistics files. The collection period refers to the time it takes to create a stats file. The file includes multiple buckets.

The choices are 5, 10, and 15 min.

The default is 15 min.

Time-Out Period (Minutes)

Defines the period where SCM attempts to retrieve uncollected statistics files. The time-out value is defined in min for TFTP GET requests. The value is increased on busy networks, which is configured for a high value.

The choices are 60, 90, and 120 min.

The default is 120 min.

Bucket Interval (Minutes)

Defines the bucket interval period value (in min) to be kept for the single bucket on the node. The bucket interval must be less than the collection period, which is a multiple of the bucket interval.

The choices are 5, 10, and 15 min.

The default is 15 min.

Number of Retries

Defines the number of retries the child process makes in attempting to get files from the network.

The default is 3 retries.

Peak Statistics Enable

Enables or disables the collection of peak statistics. The peak value represents the maximum value of buckets.

The default is No.

Use as a default template

Defines whether or not the configured collection parameters are used as the default for the applicable node(s) or object(s).

The default is Yes.

Step 8 Choose the applicable interval value in the Collection period (Minutes) drop-down arrow.

Step 9 Choose the applicable time out period in the Time out period (Minutes) drop-down arrow.

Step 10 Choose the applicable time for the bucket interval in the Bucket interval (Minutes) drop-down arrow.

Step 11 Enter the number of retries in the Number of Retries field.

Step 12 Choose either Yes or No to enable or disable the peak statistics in the Peak statistics enable drop-down arrow.

Step 13 Choose either Yes or No to configure the collection parameters as the default template in the Use as a default template drop-down arrow.

Step 14 Click Save to save the modified collection parameters.

Step 15 Click Finish to implement the selected values and send a confirmation back to the SCM controller server.

When the statistics are enabled, a letter (E) follows the node name (see Figure 7-8). For letter indicators, see Table 7-5.

Figure 7-8 displays the node collection status in the Browse window.

Figure 7-8 Update Stats enabling information

Editing Templates

To edit templates, complete the following procedure:

Step 1 Select the applicable template to edit from the Browse window (see Figure 7-9).

The example shown is AXSM_ENH_Enabling (T1E1), which are AXSMT1E1 based templates.

Figure 7-9 Statistics Collection Manager: Edit Template Option

Step 2 Right-click the AXSM_ENH_Enabling (T1E1) to choose Edit Template or choose Enabling > Edit Template.

Figure 7-10 displays the Template Dialog.

Figure 7-10 Statistics Collection Manager: Template Dialog

Step 3 Click OK to display the Statistics Enable Dialog (see Figure 7-6).

Follow Step 2 to Step 15 in the "Enabling Statistics" section.

Deleting Templates

To delete templates, complete the following procedure:

Step 1 Select the applicable template to delete from the Browse window (see Figure 7-11). The example shown is AXSM_ENH_Enabling (T1E1), which are AXSMT1E1 based templates.

Figure 7-11 Statistics Collection Manager: Delete Template

Step 2 Right-click the AXSM_ENH_Enabling (T1E1) to choose Delete Template or choose Enabling > Delete Template.

Figure 7-12 displays the Delete Template dialog.

Figure 7-12 Delete Template Dialog

Step 3 Select the template that you want to delete from the list of templates.

Step 4 Click Delete.

Disabling Collection Statistics

To disable statistics collection, complete the following procedure:

Step 1 Right-click a node and choose Disable Collection Statistics. Or select a node and choose Enabling > Disable Collection Statistics.

Figure 7-13 displays the statistics confirmation dialog.

Figure 7-13 Statistics Disabling Confirmation

Step 2 Click Yes to disable the statistics.

Starting and Stopping the Collection Process

This section describes the collection process and the primary, secondary, and tertiary collection servers of SCM.

SCM primary, secondary, and tertiary collection servers provide distributed collection and statistics collection redundancy. SCM redundancy happens when the secondary and tertiary SCM collection servers still continue to collect statistics when the primary SCM collection server is not reachable or completely shut down. Distributed collection happens when you can distribute statistics collection from all switch nodes to different SCM collection servers.

For example, if the connection to the primary SCM shuts down for any reason, whether the FTP or TFTP connection is disrupted, or if primary SCM shuts down, the secondary SCM takes over the statistics collection process. If the secondary SCM shuts down, the tertiary SCM takes over the statistics collection process.

Primary, secondary, and tertiary is always dependent upon the assignment of the collection server. You can use the cnfcollsvr command to redirect collectors to a CWM host.

To start the collection process, complete the following procedure:

Step 1 Click the Collecting View tab.

Step 2 Right-click a node where the collection is enabled and choose Start Collection. Or select a node and choose Collecting > Start Collection.

Note To start a collection, you can also select multiple nodes.

Figure 7-14 displays the Start Collection dialog to collect configuration for the primary, secondary, and tertiary collection servers.

Figure 7-14 Start Collection Dialog

The following statistics collection configuration are configured and defined from the Start Collection Dialog (see Figure 7-14):

•Primary Collection Server

•Secondary Collection Server

•Tertiary Collection Server

Step 3 Choose either In Band or Out-of-Band routing to access the node in the IP Routing drop-down arrow.

Step 4 Once the configuration is completed, click Start Collection to display the SCM main window again.

Figure 7-15 displays the active collection indicator (C) for the selected node.

Figure 7-15 Collecting View Window

To stop a collection, complete the following procedure:

Step 1 Select an active, collecting node to choose Collecting > Stop Collection.

Note To stop a collection, you can also select multiple nodes.

Step 2 Click Stop Collection. The node will revert to enabled status on the SCM main window.

Monitoring the Collection Process

You can use the SCM to monitor the progress of the collection process.

To monitor the collection process by using SCM, complete the following procedure:

Step 1 Click the Monitoring View tab to monitor the statistics collection.

Step 2 Click the Log tab to display the log view (see Figure 7-16).

Figure 7-16 Monitoring View: Log Information

The following information is displayed:

•Lists the status of all outstanding collection requests.

•Lists the files that are collected in ascending order. The following file name format is shown:
nodename,<month><day><year><time>
Time is defined in Greenwich Mean Time (GMT).

Step 3 Click the Monitor tab to view the monitor (see Figure 7-17).

Figure 7-17 Monitoring View: Monitor Information

The following information is displayed:

•Provides current hour activity that includes the number of files collected for each node in the active collection mode.

•Provides the collection status for all nodes where the statistics collection started.

•Provides error indications in the event of a breakdown of FTP.

Configuring the ScmProxy

The ScmProxy is an alternative interface to the Statistics Collection Manager application that enables and disables statistics, and starts and stops collecting statistics on multiple nodes. It also uses a node list file to discover the SSM and SSC topology. The node list file describes the SCM server configurations (which managers are connected to which collectors) and lists the network nodes that each collection server supports.

The ScmProxy configuration tasks include the following procedures:

•Creating the ScmProxy Node List

•Launching the ScmProxy

Creating the ScmProxy Node List

You are required to create a ScmProxy node list file first.

To create the ScmProxy node list file, complete the following procedure:

Step 1 Open a terminal window.

Step 2 At the prompt, create a node list file with the following format:
<CollParams:<templateName><primary,secondary,tertiary collsvrNames ><iprouting>>
node1
node2
...
nodeN
<CollParams:<templateName><primary,secondary,tertiary collsvrNames ><iprouting>>
node1
node2
...
nodeN
The node list consists of a number of records where each record specifies the stats template to be used, a collection server pair, parser server pair, and a list of nodes in the network where the servers are collecting statistics. If a template other than the standard platform template is used, it is formed first before using the SCM GUI.

Table 7-7 lists the parameters for the node list file.

Table 7-7 Node List Parameters for ScmProxy

Name

Definition

template_name

Specifies the name of the template applicable to all nodes listed after the parameters. Stats templates are created from the SCM GUI. The templates are saved in stratacom database.

primary, secondary, tertiary collsvrNames

Specifies the name of the collection server host that performs FTP and TFTP of files. The collection server can be on a CWM host or in a standalone SCM.

Note If a collection server is on the same machine, you must specify the local host.

iprouting

Specifies either inband or outofband fields. A value of 0 indicates inband routing. A value of 1 indicates outofband routing. The field depends on the routing method to the node.

node_name1
node_name2

Specifies the node names in the network that the servers are collecting statistics.

You can specify multiple CollParam entries in the input file as shown in the following ScmProxyHost file:
<CollParam:<MGX8850_template><cwmhost><inband>>
jbpop1-1
<CollParam:<MGX2_test><cwmhost><inband>>
UpperRed
popeye13
<CollParam:<BPX_template><cwmhost><outofband>>
nmsbpx09
jbbpx1
jbbpx2
<CollParam:<MGX8220_template><cwmhost><inband>>
axis154
axis160
axis245
axis250
Launching the ScmProxy

The ScmProxy must be started from the CWM host machine.

To launch the ScmProxy, complete the following procedure:

Step 1 Open a terminal window.

Step 2 Enter the scmproxy command as shown in the following example:
tballraker2% scmproxy <nodelist_filename>
tballraker2%
Replace <nodelist_filename> parameter with the name you gave to the node list file. The filename is the name of the input file that contains the template, hosts, and node information.

When the scmproxy is started with the correct input file, the following menu is displayed:
Welcome to SCM Proxy
MENU
---------
1) Enable Statistics
2) Disable Statistics
3) Start Collection
4) Stop Collection
x) Exit
Enter number or x to exit.
Note An error message is displayed if the node list file contains incorrect data, for example, a template that does not exist. Otherwise, the selected option is invoked.

Wingz and summary reports are not supported by the Standalone Stats Manager.

For information about launching Wingz and summary reports from a CWM console, see "Generating Reports," Overview of Summary Reports and Wingz Reports section.