Document ID: 29010
Contents
Introduction
Before You Begin
Conventions
Prerequisites
Components Used
On the Switches
Step-by-Step Procedure to Collect Statistics
Verify
Troubleshoot
Related Information
Introduction
This document provides information on how statistics collection works on MGXs version 2.0 and above.
Before You Begin
Conventions
For more information on document conventions, see the Cisco Technical Tips Conventions.
Prerequisites
There are no specific prerequisites for this document.
Components Used
The information in this document is based on the software and hardware versions below.
-
Cisco WM 11.0
-
Cisco WM 10.5
-
PXM45 and AXSM cards
The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.
On the Switches
Statistics collection works differently on PXM45 based platforms. The implementation on the switch software is improved with every release.
Before 2.75
Before version 2.75 there was no concept of Stats Master. Cisco WM sends an enable file but this one is discarded by the switch. Statistics collection is enabled by default on any AXSM board. To be able to collect connection statistics, it must first be enabled on the switch while creating the connections. On the CLI, there is a parameter in addcon to enable statistics on the local end. dspcon shows that statistics are enabled. When creating a connection with Connection manager, there is a toggle button to enable statistics on that connection. The difference with the CLI is that CM enables statistics on both ends at the same time instead of only one end with addcon.
With 2.75
With version 2.75 statistics collection can be disabled on the whole switch but there is still no notion of Stats Master.
From 3.0
From version 3.0 statistics are enabled per card. There is a notion of Stats Master. Check the commands: cnfstatsmgr, dspstatsmgr.
Once enabled, the AXSM card collects statistics and puts them together into files every 00, 15, 30, 45 minutes. Cisco WM picks these files using FTP. Statistics files are kept in memory and can be collected only once (two with legacy nodes - dual collection feature). However, from 10.5.10 patch 2, this dual-collection feature is extended to all the nodes.
On the Switch, check these commands to see the statistics collections process:
For bucket statistics (statistics that are uploaded to Cisco WM):
-
To check for the list of files generated and the details on a per card basis, AXSM CLI command - sfmdbshow can be used (TAC use only).
-
On the PXM, to get the details of statistics files for all the cards, the command to be used is sumdbshow (TAC use only).
-
On the AXSM CLI, for each interval, the accumulated counter values can be displayed by using dsplnbucketcnt, dspportbucketcnt and dspcdbucketcnt commands. These counters start from zero at the start of every new interval (00, 15, 30, 45 minutes) and the final values at the end of the interval are written to the statistics file that is uploaded. These commands are useful when you want to check what is actually written in the statistics files.
For running statistics, the counters continue to accumulate values until they are explicitly cleared or the card resets. You can display these counter values using dsplncnt, dspcdcnt, dspportcnt and dspchancnt commands. These counter values can be cleared by using clrlncnt, clrcdcnt, clrportcnt and clrchancnt commands.
The running statistics commands can be used for real-time traffic monitoring and debugging.
As for legacy nodes, statistics files are timestamped with GMT time. The statsparser feeds the database only with statistics selected by the user during the enable statistics operation.
There are two types of files generated for each logical slot :
-
GEN files: These files contain statistics for line, port, and card. The polling interval is one minute and the file is generated at the end of 15 minutes (statistics collected by default).
-
CON files: These files contain the statistics for the connections configured on the card that have statistics enabled. The polling interval is five minutes and the file is generated at the end of 15 minutes.
Step-by-Step Procedure to Collect Statistics
Follow these steps:
-
Proceed after the PNNI network with MGXs has been discovered successfully.
-
Add SPVC connections with the stat_enable flag set to TRUE. On MGX PNNI nodes, you must enable statistics on a connection basis (on the AXSM card, use dspcon to check if statistics are enable, and cnfcon ... -stat 1 or Connection Manager gui to enable it).
-
Configure the statistic master on the switches: cnfstatsmgr
-
Enable statistics from ScmGui (or from scmproxy from 10.5.10), either by default parameters, or by template.
-
Start collection and verify that statistics files have been enqueued in the Statistic Collection Manager (SCM) log window. Make sure you have LAN/WAN reachability depending on IN/OUT of band statistics collection chosen from SCM GUI.
Note: Use the nodeip <node_name> command on Cisco WM to get the inband IP.
-
Wait 15 minutes to see any files are collected from the switch. *-Gen-* files for line, port and card statistics and *-Con-* files for the connection statistics.
-
If statsparser is chosen to parse the statistics data, you will see the following:
-
all statistics data stored in database
-
connection_data table for conn statistics
-
axsm_ln_data table for line statistics
-
ausm_port_data table for port statistics
-
axsm_cd_data table for card statistics
-
-
The statsparser moves statistics file from the incoming directory to the purge directory.
-
You can use the Wingz report to see the statistics data in the database.
The Statistic Summary chapter in the Cisco WM Database Interface Guide includes the statistics that you can collect. These statistics are organized by card type. For example, ATM connection statistics on the MGX 8850 R2 are found under the AXSM Connection Statistics link.
Verify
There is currently no verification procedure available for this configuration.
Troubleshoot
There is currently no specific troubleshooting information available for this configuration.
Related Information
| Updated: Jan 31, 2006 | Document ID: 29010 |
