Table Of Contents
Service Assurance Agent for ATM Interfaces
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring SAA ATM Performance Monitoring Operations
Configuring a T1 Performance Monitoring Operation
Configuring a PVC Performance Monitoring Operation
Configuring an ATM Performance Monitoring Operation
Service Assurance Agent for ATM Interfaces
Note
This document applies to Cisco IOS Release 12.2(11)T only.
The commands used for this feature were changed in Cisco IOS Release 12.2(15)T. For documentation of this feature for Release 12.2(15)T and latter, please see the document "SAA SLM for ATM Interfaces".Feature History
This document describes the Service Assurance Agent for ATM Interfaces feature in Cisco IOS Release 12.2(11)T and includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
Monitoring ATM Service Levels
Feature Overview
The Cisco Service Assurance Agent (SAA) is an embedded performance monitoring utility in Cisco IOS software. The Service Assurance Agent for ATM Interfaces (SAA ATM) feature expands the capabilities of SAA by using service level monitoring (SLM) and ATM performance monitoring techniques to provide detailed monitoring statistics for your ATM network. SLM and ATM performance monitoring techniques include gathering physical link and circuit performance statistics. Monitoring service levels for ATM connections allows service providers to ensure that their networks are meeting or exceeding the performance outlined in service level agreements (SLAs).
The SAA ATM feature can also be used with Cisco Networking Services (CNS). A device running CNS, such as the IE2100, can be used to retrieve the ATM performance statistics generated by the SAA. Additionally, these results can be passed to other devices running third-party monitoring software, such as Visual Networks "Uptime" application.
Benefits
By leveraging the performance management capabilities included in Cisco IOS software, users can perform advanced monitoring directly on their existing Integrated Access Devices (IADs), thereby eliminating the need for purchasing additional dedicated monitoring devices. For large networks, this represents a potentially large cost savings.
Restrictions
•
Only T1 ATM interfaces are supported in this release.
•
ATM performance statistics cannot be retrieved from the Cisco IOS devices using SNMP. This feature was designed to provide data by responding to extensible markup language (XML) requests.
Related Features and Technologies
•
Cisco Service Assurance Agent (SAA)
•
Cisco Networking Services (CNS)
Related Documents
•
"Configuring ATM," Cisco IOS Release 12.2
•
"Network Monitoring Using Cisco Service Assurance Agent," Cisco IOS Release 12.2
•
"Cisco Service Assurance Agent Commands," Cisco IOS Release 12.2 T
•
CNS Event Agent Cisco IOS Release 12.2(2)T
Supported Platforms
The SAA ATM feature is supported on the following platforms in Cisco IOS Release 12.2(11)T:
•
Cisco IAD2420 Smart Integrated Access Device (IAD)
•
Cisco 2600 Series with T1 interfaces (Cisco 2650 and 2651 Modular Access Routers)
•
Cisco 3660 Series with T1 ATM interfaces
•
Cisco MC3810 Multiservice Access Concentrators
Platforms above must have ATM interfaces for monitoring to be effective. Monitoring operations can be configured only when the appropriate hardware is available. For example, T1 Inverse Multiplexing over ATM (IMA) monitoring is supported for the Multiport T1 ATM Network Module on Cisco 2600 and Cisco 3600 series routers.
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that are supported on specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator is regularly updated as new platform support is added for features.
Cisco Feature Navigator is a web-based tool that enables you to quickly determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Supported Standards, MIBs, and RFCs
Standards
None
MIBs
None
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Network Management Software page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
None
Prerequisites
Tasks in this document assume you have one or more ATM connections configured, and that you are familiar with SAA configuration.
The oam-pvc manage command should be configured on the system to maintain the correct status for the monitored permanent virtual circuits (PVCs).
Configuration Tasks
See the following sections for configuration tasks for the SAA ATM feature. Each task in the list is identified as either required or optional.
•
Enabling SAA ATM (Required)
•
Configuring SAA ATM Performance Monitoring Operations (Required)
–
Configuring a T1 Performance Monitoring Operation
–
Configuring a PVC Performance Monitoring Operation
–
Configuring an ATM Performance Monitoring Operation
Enabling SAA ATM
Before configuring any SAA ATM operations, you must first enable the SAA ATM feature. To enable ATM performance monitoring, use the following command in global configuration mode:
Command PurposeRouter(config)# atm slm statistics
Enables SAA to collect ATM performance monitoring statistics.
Configuring SAA ATM Performance Monitoring Operations
ATM performance monitoring statistics are gathered using the Service Assurance Agent. Response time and availability information is generated by SAA operations that you configure on the router; these operations use probe packets to simulate other forms of network traffic. The characteristics of that traffic are determined by the type of operation you configure.
The SAA ATM feature introduces three new SAA operations:
•
The T1 performance monitoring operation monitors a specific controller (or group of controllers) by generating statistics for the physical connection layer.
•
The PVC performance monitoring operation monitors the performance over one or more ATM PVCs by generating statistics for the ATM circuit connection layer.
•
The ATM performance monitoring operation monitors the ATM interface by generating statistics for the ATM link connection layer.
For example, suppose you have configured ATM on a T1 controller on an MC3810. To monitor the performance of this ATM interface, you would want to generate performance data for the T1 controller, the ATM interface, and the ATM VC. By using the SAA operations listed above, you can generate the needed controller (DS1) statistics, ATM interface statistics, and ATM VC statistics.
To get the full ATM performance monitoring statistics, you should configure all three operations.
Configuring a T1 Performance Monitoring Operation
You can configure a T1 performance monitoring operation on a specific controller or on an Inverse Multiplexing over ATM (IMA) group of controllers.
To configure a T1 performance monitoring operation on a T1 controller, use the following commands beginning in global configuration mode:
To configure a T1 performance monitoring operation on a T1 IMA group, use the following commands beginning in global configuration mode:
Configuring a PVC Performance Monitoring Operation
The permanent virtual circuit (PVC) SAA operation monitors the performance over one or more ATM virtual circuits (VCs) by generating statistics at ATM circuit connection layer.
To configure an ATM PVC performance monitoring operation, use the following commands beginning in global configuration mode:
Configuring an ATM Performance Monitoring Operation
The ATM performance monitoring operation generates statistics for the ATM interface at the link connection layer.
To configure an ATM performance monitoring operation, use the following commands beginning in global configuration mode:
Note
Unlike other SAA operations, you do not enable the SAA Responder on the operational target (replying) device. Instead, to get the full monitoring statistics for ATM connections, you should enable all three ATM operations on both the sending (agent) device and replying (target) device. The SAA will automatically retrieve the additional statistics generated when the ATM operations are configured on the target device. For ATM performance monitoring operations, it may be helpful to think of the routers as "near-end" and "far-end" devices instead of as "sending" and "replying" devices.
Monitoring ATM Service Levels
To view the gathered statistics for the enabled SAA ATM performance monitoring operations, use one or both of the following commands in EXEC mode:
Configuration Examples
The following example shows the configuration of the three ATM performance monitoring operations using the SAA and includes sample output from the relevant show commands. Note that in this example, no monitoring data has been collected yet, but the output is shown here to give you an example of the specific data points and monitoring metrics.
Router# show running-config | begin rtrrtr 1type slm interface ATM0/0 pvc 200/200enhanced-history interval 450 buckets 100rtr schedule 1 start-time now life foreverrtr 2type atm-slm interface ATM0/0enhanced-history interval 900 buckets 100rtr schedule 2 start-time now life foreverrtr 3type t1-slm controller T1 0/0enhanced-history interval 900 buckets 100rtr schedule 3 start-time now life forever...! Output for rtr operation 1 - ATM Circuit operation.Router# show rtr operational-state 1Entry number:1Modification time:*00:04:48.653 UTC Mon Mar 1 1993Number of operations attempted:0Number of operations skipped:0Current seconds left in Life:0Operational state of entry:PendingLast time this entry was reset:NeverConnection loss occurred:FALSETimeout occurred:FALSEOver thresholds occurred:FALSELatest RTT (milliseconds):UnknownLatest operation return code:UnknownLatest operation start time:UnknownSample Index = 0Echo Receive Time = *00:00:00.002 UTC Mon Mar 1 1993Echo Response Time = 0 (ms)Remote IP Address :0.0.0.0 Remote Product Id :0Remote Interface Type :0 Remote Interface Index:0Remote Circuit Index :0Offered Frames/PDUs :0 Delivered Frames/PDUs:0OAM VC state:0Tx Total Cells:0 Rx Total Cells:0Tx Clp1 Cells: 0 Rx Clp1 Cells:0Tx Max Throughput(bits):0 Rx Max Throughput(bits):0Tx Pdus:0 Rx Pdus:0Tx Errored Pdus:0 Rx Errored Pdus:0Tx OamAis Secs:0 Rx OamAis Secs:0Tx OamRdi Secs:0 Rx OamRdi Secs:0Tx Congested Secs:0 Rx Congested Secs:0Vc Round Trip Delay:0 Vc Unavailable Secs:0Vc Offered Pdu:0 Vc Delivered Pdu:0Vc Rx Cells Above SCR:0Vc Tx Scr Burst Percent1(sec):0 Vc Tx Scr Burst Percent2(sec):0Vc Tx Scr Burst Percent3(sec):0 Vc Tx Scr Burst Percent4(sec):0Vc Tx Scr Burst Percent5(sec):0Circuit Default Burst Nominal Source:0Circuit Default Burst Limit1:0 Circuit Default Burst Limit2:0Circuit Default Burst Limit3:0 Circuit Default Burst Limit4:0Circuit Burst Nominal Source:0Circuit Burst Limit1:0 Circuit Burst Limit2:0Circuit Burst Limit3:0 Circuit Burst Limit4:0! Output for rtr operation 2 - ATM interface operationRouter# show rtr operational-state 2Entry number:2Modification time:*00:05:01.317 UTC Mon Mar 1 1993Number of operations attempted:0Number of operations skipped:0Current seconds left in Life:0Operational state of entry:PendingLast time this entry was reset:NeverConnection loss occurred:FALSETimeout occurred:FALSEOver thresholds occurred:FALSELatest RTT (milliseconds):UnknownLatest operation return code:UnknownLatest operation start time:UnknownLinkState :0Tx Total Cells: 0 Rx Total Cells: 0Tx AAL1 Cells: 0 Rx AAL1 Cells: 0Tx AAL2 Cells: 0 Rx AAL2 Cells: 0Tx AAL5 Cells: 0 Rx AAL5 Cells: 0Tx Path Cells: 0 Rx Path Cells: 0Tx Plcp Framing:0 Rx Plcp Framing:0Tx Plcp Errors: 0 Rx Plcp Errors: 0Tx Corrected Cells: 0 Rx Corrected Cells:0Tx Uncorrected Cells: 0 Rx Uncorrected Cells:0Tx OCD Secs: 0 Rx OCD Secs:0Tx AIS Secs: 0 Rx AIS Secs:0Tx RDI Secs: 0 Rx RDI Secs:0Tx Max Cells Per Secs: 0 Rx Max Cells Per Secs:0Cell Replacement Events: 0 Rx Cell Unanalyzed Data Event:0Tx Burst Percent1(sec): 0 Rx Burst Percent1(sec):0Tx Burst Percent2(sec): 0 Rx Burst Percent2(sec):0Tx Burst Percent3(sec): 0 Rx Burst Percent3(sec):0Tx Burst Percent4(sec): 0 Rx Burst Percent4(sec):0Tx Burst Percent5(sec): 0 Rx Burst Percent5(sec):0Sample Index = 0! Output for rtr operation 3 - T1 controller operation.Router# show rtr operational-state 3Entry number:3Modification time:*00:05:18.333 UTC Mon Mar 1 1993Number of operations attempted:0Number of operations skipped:0Current seconds left in Life:0Operational state of entry:PendingLast time this entry was reset:NeverConnection loss occurred:FALSETimeout occurred:FALSEOver thresholds occurred:FALSELatest RTT (milliseconds):UnknownLatest operation return code:UnknownLatest operation start time:UnknownvnDs1StatRxLineStatus:0vnDs1StatRxBPVs:0, vnDs1StatRxCrcFrameErrors:0vnDs1StatRxErrSecs:0, vnDs1StatRxSevereErrSecs:0vnDs1StatRxUnavailSecs:0 vnDs1StatRxBurstyErrSecs:0Sample Index = 0Command Reference
This section documents the commands used for configuring this feature in Cisco IOS Release 12.2(11)T.. All other commands used with this feature are documented in the Cisco IOS Release 12.2 and 12.2 T command reference publications. See the Related Documents section of this document for a list of references.
atm-slm statistics
To enable the Service Assurance Agent (SAA) or Cisco Networking services (CNS) to collect ATM performance monitoring statistics, use the atm-slm statistics command in global configuration mode. To disable the collection of ATM performance monitoring statistics, use the no form of this command.
atm-slm statistics
no atm-slm statistics
Syntax Description
This command has no arguments or keywords.
Defaults
Collection of ATM performance monitoring statistics is disabled.
Command Modes
Global configuration mode
Command History
Usage Guidelines
To generate and retrieve performance statistics for ATM services using SAA, the SAA ATM feature must first be enabled on the device using the atm-slm statistics global configuration command. (Note that these performance statistics can be retrieved by other applications such as CNS or Visual Uptime.) If this command is not used, other SAA operations (type atm-slm, type slm, or type t1-slm) can not be configured on the system. Service level monitoring (SLM) techniques include gathering physical link and circuit performance statistics.
Disabling the SAA ATM feature with the no atm-slm statistics command will cause any currently configured SAA performance monitoring operations to be removed from the configuration. When SAA ATM is disabled, no CNS/XML requests are processed.
Examples
In the following example, the SAA ATM feature is enabled to collect ATM performance monitoring statistics before a permanent virtual circuit (PVC) SAA performance monitoring operation is configured for ATM interface 0/1:
Router(config)# atm-slm statisticsRouter(config)# rtr 1Router(config-rtr)# type atm-slm interface ATM0/1Router(config-rtr-slm)# enhanced-history interval 900 buckets 100Router(config-rtr-slm)# exitRouter(config)# rtr schedule 1 start-time now life foreverRelated Commands
debug saa slm
To enable the output of detailed event messages for Service Assurance Agent (SAA) ATM performance monitoring, use the debug saa slm command in privileged EXEC mode. To disable message output, use the no form of this command.
debug saa slm
no debug saa slm
Syntax Description
This command has no arguments or keywords.
Defaults
Debug message output is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Service level monitoring (SLM) involves gathering physical link and circuit performance statistics. This command may generate a large amount of debugging messages.
Examples
In the following example, debugging is enabled for the SAA ATM feature and the SAA XML feature for the purposes of debugging the XML requests and responses.
Router# debug saa slmRouter# debug saa xmlRelated Commands
type atm-slm
To configure an ATM Service Assurance Agent (SAA) performance monitoring operation, use the type atm-slm command in SAA response time reporter (RTR) configuration mode. To disable an ATM SAA performance monitoring operation, use the no form of this command.
type atm-slm interface atm-interface-id
no atm-slm interface atm-interface-id
Syntax Description
Defaults
No ATM SAA performance monitoring operations are configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
This command puts you into SAA RTR configuration mode, and should be followed by the enhanced-history configuration command. For ATM SAA operations, the default of one hundred 900-second history buckets should be used.
SAA ATM must be enabled on the device by entering the atm slm statistics global configuration command in order for operational statistics to be generated. Service level monitoring (SLM) techniques include gathering physical link and circuit performance statistics.
To get complete ATM performance monitoring statistics, you should configure all three ATM SAA operations.
Examples
In the following example, SAA operation 1 is configured as an ATM performance monitoring operation:
Router(config)# rtr 1Router(config-rtr)# type atm-slm interface ATM0/0Router(config-rtr-slm)# enhanced-history interval 900 buckets 100Router(config-rtr-slm)# exitRouter(config)# rtr schedule 1 start-time now life foreverRelated Commands
type slm
To configure a permanent virtual circuit (PVC) Service Assurance Agent (SAA) performance monitoring operation, use the type slm command in SAA response time reporter (RTR) configuration mode. To disable a PVC SAA performance monitoring operation, use the no form of this command.
type slm interface interface-number pvc pvc-number
no type slm interface interface-number pvc pvc-number
Syntax Description
interface interface-number
Specifies the ATM interface for the operation.
pvc pvc-number
Specifies the PVC for the operation.
Defaults
No PVC SAA operations are configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
This command puts you into SAA RTR SLM configuration mode, and should be followed by the enhanced-history configuration command. For ATM SAA operations, the default of one hundred 900-second history buckets should be used.
SAA ATM must be enabled on the device by entering the atm slm statistics global configuration command in order for operational statistics to be generated. Service level monitoring (SLM) techniques include gathering physical link and circuit performance statistics.
Examples
In the following example, SAA operation 3 is configured as a PVC SAA performance monitoring operation:
Router(config)# rtr 3Router(config-rtr)# type slm interface ATM0/0 pvc 200/200Router(config-rtr-slm)# enhanced-history interval 900 buckets 100Router(config-rtr-slm)# exitRouter(config)# rtr schedule 3 start-time now life foreverRelated Commands
type t1-slm
To configure a T1 Service Assurance Agent (SAA) performance monitoring operation, use the type t1-slm command in SAA response time reporter (RTR) configuration mode. To disable a T1 SAA performance monitoring operation, use the no form of this command.
type t1-slm {controller t1 controller-number | interface ima-identification-number }
no type t1-slm {controller t1 controller-number | interface ima-identification-number }
Syntax Description
controller t1 controller-number
Specifies the T1 controller for the operation.
interface ima-interface-number
Specifies the Inverse Multiplexing over ATM (IMA) group for the operation.
Defaults
No T1 SAA performance monitoring operations are configured.
Command Modes
SAA RTR configuration
Command History
Usage Guidelines
You can configure a T1 SAA performance monitoring operation on a specific controller, or on an Inverse Multiplexing over ATM (IMA) group of controllers.
This command puts you into SAA RTR configuration mode, and should be followed by the enhanced-history configuration command. For ATM SAA operations, the default of one hundred 900-second history buckets should be used.
SAA ATM must be enabled on the device by entering the atm slm statistics global configuration command in order for operational statistics to be generated. Service level monitoring (SLM) techniques include gathering physical link and circuit performance statistics.
Examples
In the following example, SAA operation 5 is configured as a T1 SAA performance monitoring operation:
Router(config)# rtr 5Router(config-rtr)# type t1-slm controller T1 0/0Router(config-rtr-slm)# enhanced-history interval 900 buckets 100Router(config-rtr)# rtr schedule 5 start-time now life foreverRelated Commands

