Downloads |
Table Of Contents
Information About SAA SLM for ATM Interfaces
Enabling Operations on Both Ends of the Connection
How to Configure SAA Monitoring for ATM Connections
Configuring Monitoring of a Physical Interface or Controller
Configuring Monitoring of an ATM Link
Configuring Monitoring of a ATM Circuit
Enabling CNS for SAA Data Retrieval
Configuration Examples for SAA Monitoring for ATM Connections
show rtr enhanced-history distribution-statistics
SAA SLM for ATM Interfaces
The Cisco Service Assurance Agent (SAA) is an embedded performance monitoring utility in Cisco IOS software. The Service Level Monitor (SLM) is one of the features available in the SAA feature set.
The SAA Service Level Monitor (SLM) for ATM Interfaces feature expands the capabilities of SAA by providing detailed monitoring statistics for your ATM network. The SAA SLM can be used to gather statistics for either physical links or circuits. 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).
Specifications for the SAA SLM for ATM Interfaces Feature
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find updated information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Information About SAA SLM for ATM Interfaces
•
•
Information About SAA SLM for ATM Interfaces
To configure the SAA SLM for ATM Interfaces feature, you should understand the following concepts:
•
ATM Service Level Monitoring
The SLM ATM operations provide both active and passive monitoring and can be applied to either interfaces or circuits.
Specifically, this feature provides four operations that perform the following functions:
•
•
•
•
By using these operations together, you can generate statistics for the physical interface, the ATM connection as a whole, and for specific ATM circuits (PVCs). Table 1shows the correspondence between the operation name and the command used to enable the operation.
The metrics provided by SAA service level monitoring operations, such as the ATM SLM operations, are designed to provide information useful in determining that service level agreements (SLAs) are being met (SLA validation). Service providers can use the SLM ATM operations to determine round trip time (RTT), bandwidth usage, throughput, packet loss, burst analysis, delivery ratio, utilization, total frames transmitted, total frames received, and more. The SLM ATM operations can provide over 100 different metrics for traffic analysis.
The SAA for ATM Interfaces feature can 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. An XML Get or Set request can be issued from the IE2100 after the router registers with the CNS event agent. Additionally, these results can be passed, in an XML format, to other devices running third-party monitoring software, such as Visual Networks' UpTime application.
Figure 1 Retrieval Methods for SAA SLM Operational Data
SAA, when used with external applications such as Visual Network's UpTime, provides the information and toolsets required to:
•
•
•
•
Trending, reporting, troubleshooting and planning tools enhance the performance and availability of the integrated access network. This provides short and long-term cost savings through reduced downtime, increased productivity of network support staff, and optimization of the network.
Enabling Operations on Both Ends of the Connection
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 the same operation on both the sending (agent) device and replying (target) device. SAA will automatically retrieve the additional statistics generated when the Frame Relay operations are configured on the target device. For ATM SLM operations, it may be helpful to think of the routers as "near-end" and "far-end" devices instead of as "sending" and "replying" devices.
Restrictions
The following operations are not supported in the CISCO-RTTMON-MIB:
•
•
•
•
•
•
•
This means that ATM performance statistics cannot be retrieved from Cisco IOS devices using SNMP. This feature was designed to provide data by responding to extensible markup language (XML) requests.
How to Configure SAA Monitoring for ATM Connections
To configure SAA Monitoring for ATM connections, perform one or more of the following tasks:
•
•
•
•
Configuring Monitoring of a Physical Interface or Controller
ATM monitoring using SAA can be configured for an interface or controller at the physical layer, for an interface at the data layer, or for a specific circuit. The follow task describes configuring the SAA operation for an ATM interface or controller at the physical layer.
All steps are required unless otherwise indicated.
Restrictions
To enable full statistics gathering for SAA ATM service level monitoring operations, the operation must be configured on both ends of the ATM connection.
Standard SAA distribution and history statistics are not supported in SLM operations; instead, use the show enhanced-history commands. Enhanced history data is stored as individual samples in each bucket. Aggregated (averaged) data for SLM operations is not available from the CLI.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
DETAILED STEPS
Example
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line.Router(config)# atm-slm statisticsRouter(config)# rtr 1Router(config-rtr)# type slm controller T1 0Router(config-rtr-slm-if)# enhanced-history interval 900 buckets 100Router(config-rtr-slm-if)# exitRouter(config)# rtr schedule 1 start-time now life foreverRouter(config)# endRouter#slm1-3810-4# show rtr config 1Entry number: 1Owner:Tag:Type of operation to perform: slm controllerT1/E1/T3/E3 Controller: T1 0Operation timeout (milliseconds): 5000Operation frequency (seconds): 900Next Scheduled Start Time: Start Time already passedLife (seconds): ForeverEntry Ageout (seconds): neverStatus of entry (SNMP RowStatus): ActiveConnection loss reaction enabled: NoTimeout reaction enabled: NoVerify error enabled: NoThreshold reaction type: NeverThreshold (milliseconds): 5000Threshold Falling (milliseconds): 3000Threshold Count: 5Threshold Count2: 5Reaction Type: NoneNumber of statistic hours kept: 2Number of statistic distribution buckets kept: 1Statistic distribution interval (milliseconds): 20Enhanced History:Aggregation Interval:900 Buckets:100Router#Router# show rtr operational-state 1Entry number: 1Modification time: *02:13:28.643 UTC Mon May 5 2003Number of operations attempted: 9Number of operations skipped: 0Current seconds left in Life: ForeverOperational state of entry: ActiveLast time this entry was reset: NeverConnection loss occurred: FALSETimeout occurred: FALSEOver thresholds occurred: FALSELatest RTT (milliseconds): 0Latest operation start time: *02:15:00.007 UTC Mon May 5 2003Latest operation return code: OKDs1StatRxLineStatus: 16385Ds1StatRxBPVs: 0, Ds1StatRxCrcFrameErrors: 0Ds1StatRxErrSecs: 0, Ds1StatRxSevereErrSecs: 0Ds1StatRxUnavailSecs: 0, Ds1StatRxBurstyErrSecs: 0Sample Index = 9Router# show rtr enhanced-history collection-statistics 1Entry number: 1Aggregation Interval: 900Bucket Index: 1Aggregation start time 00:15:00.004 UTC Mon May 5 2003Target Address:Number of failed operations due to a Disconnect: 0Number of failed operations due to a Timeout: 0Number of failed operations due to a Busy: 0Number of failed operations due to a No Connection: 0Number of failed operations due to an Internal Error: 0Number of failed operations due to a Sequence Error: 0Number of failed operations due to a Verify Error: 0Ds1StatRxLineStatus: 16385Ds1StatRxBPVs: 0, Ds1StatRxCrcFrameErrors: 0Ds1StatRxErrSecs: 0, Ds1StatRxSevereErrSecs: 0Ds1StatRxUnavailSecs: 0, Ds1StatRxBurstyErrSecs: 0Sample Index = 1Bucket Index: 2Aggregation start time 00:30:00.005 UTC Mon May 5 2003Target Address:Number of failed operations due to a Disconnect: 0Number of failed operations due to a Timeout: 0Number of failed operations due to a Busy: 0Number of failed operations due to a No Connection: 0Number of failed operations due to an Internal Error: 0Number of failed operations due to a Sequence Error: 0Number of failed operations due to a Verify Error: 0Ds1StatRxLineStatus: 16385Ds1StatRxBPVs: 0, Ds1StatRxCrcFrameErrors: 0Ds1StatRxErrSecs: 0, Ds1StatRxSevereErrSecs: 0Ds1StatRxUnavailSecs: 0, Ds1StatRxBurstyErrSecs: 0Sample Index = 2Bucket Index: 3...
Rotuer# show rtr enhanced-history distribution-statistics 1Point by point Enhanced HistoryEntry = Entry NumberInt = Aggregation IntervalBucI = Bucket IndexStartT = Aggregation Start TimePth = Path indexHop = Hop in path indexComps = Operations completedOvrTh = Operations completed over thresholdsSumCmp = Sum of RTT (milliseconds)SumCmp2L = Sum of RTT squared low 32 bits (milliseconds)SumCmp2H = Sum of RTT squared high 32 bits (milliseconds)TMax = RTT maximum (milliseconds)TMin = RTT minimum (milliseconds)Entry Int BucI StartT Pth Hop Comps OvrTh SumCmp SumCmp2L SumCmp2H n1 900 1 900001 1 1 1 0 0 0 01 900 2 1800003 1 1 1 0 0 0 01 900 3 2700001 1 1 1 0 0 0 01 900 4 3600002 1 1 1 0 0 0 01 900 5 4500004 1 1 1 0 0 0 01 900 6 5400002 1 1 1 0 0 0 01 900 7 6300003 1 1 1 0 0 0 01 900 8 7200001 1 1 1 0 0 0 01 900 9 8100003 1 1 1 0 0 0 0...What to Do Next
If SAA data is to be passed to a CNS enabled router, you should perform the task in the "Enabling CNS for SAA Data Retrieval" section.
Configuring Monitoring of an ATM Link
ATM monitoring using SAA can be configured for an interface at the physical layer, for an interface at the data link layer, or for a specific circuit. The follow task describes configuring the SAA operation for a ATM interface at the data link layer.
Restrictions
To enable full statistic gathering for the SAA ATM service level monitoring operation, the operation must be configured on both ends of the ATM connection.
Standard SAA distribution and history statistics are not supported in SLM operations. Aggregated (averaged) data for SLM operations is not available from the CLI. Enhanced history data is stored as individual samples in each bucket.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
DETAILED STEPS
Example
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line.Router(config)# atm-slm statisticsRouter(config)# rtr 2Router(config-rtr)# type slm atm interface ATM0
Router(config-rtr-slm-atm-if)# ?SAA slm atm interface Configuration Commands:! Only the following list of commands in this mode apply to SLM operations:default Set a command to its defaultsenhanced-history Enable enhanced history collectionexit Exit from RTR configuration modeno Negate a command or set its defaultsowner Owner of Entrytag User defined tagthreshold Operation threshold in millisecondstimeout Timeout of an operationRouter(config-rtr-slm-atm-if)# enhanced-history interval 900 buckets 100Router(config-rtr-slm-atm-if)# exitRouter(config)# rtr schedule 2 start-time now life foreverRouter(config)# endRouter# show rtr configuration 2Entry number: 2Owner:Tag:Type of operation to perform: Slm Atm InterfaceAtm Interface: ATM0Operation timeout (milliseconds): 5000Operation frequency (seconds): 900Next Scheduled Start Time: *12:44:59.851 PDT Fri Mar 26 1993Life (seconds): ForeverEntry Ageout (seconds): neverStatus of entry (SNMP RowStatus): ActiveConnection loss reaction enabled: NoTimeout reaction enabled: NoVerify error enabled: NoThreshold reaction type: NeverThreshold (milliseconds): 5000Threshold Falling (milliseconds): 3000Threshold Count: 5Threshold Count2: 5Reaction Type: NoneNumber of statistic hours kept: 2Number of statistic distribution buckets kept: 1Statistic distribution interval (milliseconds): 20Enhanced History:Aggregation Interval:900 Buckets:100Router# show rtr operational-state 2Entry number: 2Modification time: *17:00:07.502 PDT Sun June 29 2003Number of operations attempted: 2476Number of operations skipped: 0Current seconds left in Life: ForeverOperational state of entry: ActiveLast time this entry was reset: NeverConnection loss occurred: FALSETimeout occurred: FALSEOver thresholds occurred: FALSELatest RTT (milliseconds): 0Latest operation start time: *11:59:59.856 PDT Fri Jul 4 2003Latest operation return code: OKLinkState :0LinkState :0Tx Total Cells: 185 Rx Total Cells: 185Tx AAL1 Cells: 0 Rx AAL1 Cells: 0Tx AAL2 Cells: 0 Rx AAL2 Cells: 0Tx AAL5 Cells: 3 Rx AAL5 Cells: 3Tx Path Cells: 0 Rx Path Cells: 0Tx Plcp Framing: 2 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: 2 Rx Max Cells Per Secs: 2Cell Replacement Events: 0 Rx Cell Unalayzed Data Event: 0Tx Burst Percent1(sec): 900 Rx Burst Percent1(sec): 900Tx 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 = 2476Router# show rtr enhanced-history collection-statistics 2Entry number: 2Aggregation Interval: 900Bucket Index: 1Aggregation start time 11:14:59.856 PDT Thu Jul 3 2003Target Address:Number of failed operations due to a Disconnect: 0Number of failed operations due to a Timeout: 0Number of failed operations due to a Busy: 0Number of failed operations due to a No Connection: 0Number of failed operations due to an Internal Error: 0Number of failed operations due to a Sequence Error: 0Number of failed operations due to a Verify Error: 0LinkState :0Tx Total Cells: 184 Rx Total Cells: 184Tx AAL1 Cells: 0 Rx AAL1 Cells: 0Tx AAL2 Cells: 0 Rx AAL2 Cells: 0Tx AAL5 Cells: 3 Rx AAL5 Cells: 3Tx Path Cells: 0 Rx Path Cells: 0Tx Plcp Framing: 2 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: 2 Rx Max Cells Per Secs: 2Cell Replacement Events: 0 Rx Cell Unalayzed Data Event: 0Tx Burst Percent1(sec): 900 Rx Burst Percent1(sec): 900Tx 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 = 2377Bucket Index: 2Aggregation start time 11:29:59.852 PDT Thu Jul 3 2003...Router# show rtr enhanced-history distribution-statistics 2Point by point Enhanced HistoryEntry = Entry NumberInt = Aggregation Interval (seconds)BucI = Bucket IndexStartT = Aggregation Start TimePth = Path indexHop = Hop in path indexComps = Operations completedOvrTh = Operations completed over thresholdsSumCmp = Sum of RTT (milliseconds)SumCmp2L = Sum of RTT squared low 32 bits (milliseconds)SumCmp2H = Sum of RTT squared high 32 bits (milliseconds)TMax = RTT maximum (milliseconds)TMin = RTT minimum (milliseconds)Entry Int BucI StartT Pth Hop Comps OvrTh SumCmp SumCmp2L SumCmp2H TMax TMin2 900 1 2140200001 1 1 1 0 0 0 0 0 02 900 2 2141100003 1 1 1 0 0 0 0 0 02 900 3 2142000001 1 1 1 0 0 0 0 0 02 900 4 2142900002 1 1 1 0 0 0 0 0 02 900 5 2143800004 1 1 1 0 0 0 0 0 02 900 6 2144700002 1 1 1 0 0 0 0 0 02 900 7 2145600004 1 1 1 0 0 0 0 0 02 900 8 2146500001 1 1 1 0 0 0 0 0 02 900 9 2147400003 1 1 1 0 0 0 0 0 02 900 10 2148300001 1 1 1 0 0 0 0 0 02 900 11 2149200002 1 1 1 0 0 0 0 0 02 900 12 2150100004 1 1 1 0 0 0 0 0 02 900 13 2151000002 1 1 1 0 0 0 0 0 02 900 14 2151900003 1 1 1 0 0 0 0 0 02 900 15 2152800001 1 1 1 0 0 0 0 0 0--More--What to Do Next
If SAA data is to be passed to a CNS enabled router, you should perform the task in the "Enabling CNS for SAA Data Retrieval" section.
Configuring Monitoring of a ATM Circuit
ATM monitoring using SAA can be configured for an interface at the physical layer, for an interface at the data link layer, or for a specific circuit. The follow task describes configuring the SAA operation for a ATM circuit.
Restrictions
To enable full statistic gathering for the SAA ATM service level monitoring operation, the operation must be configured on both ends of the ATM connection.
Standard SAA distribution and history statistics are not supported in SLM operations; instead use the show enhanced history commands. Enhanced history data is stored as individual samples in each bucket. Aggregated (averaged) data for SLM operations is not available from the CLI.
SUMMARY STEPS
All steps are required unless otherwise indicated.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
DETAILED STEPS
Examples
Router> enablePassword:Router# configure terminalEnter configuration commands, one per line.Router(config)# atm-slm statisticsRouter(config)# rtr 3Router(config-rtr)# type slm atm pvc interface ATM0 100/100Router(config-rtr-slm-atm-dlci)# enhanced-history interval 900 buckets 100Router(config-rtr-slm-atm-dlci)# exitRouter(config)# rtr schedule 3 start-time now life foreverRouter(config)# endRouter#Router# show rtr configuration 3 | include TypeType of operation to perform: Slm Atm PvcReaction Type: NoneRouter# show rtr operational-state 3Entry number: 3Modification time: *00:12:35.686 UTC Thur May 1 2003Number of operations attempted: 276Number of operations skipped: 277Current seconds left in Life: ForeverOperational state of entry: ActiveLast time this entry was reset: NeverConnection loss occurred: FALSETimeout occurred: FALSEOver thresholds occurred: FALSELatest RTT (milliseconds): 16Latest operation start time: *21:07:29.988 UTC Sat May 3 2003Latest operation return code: OKSample Index = 277Echo Receive Time = *00:22:30.005 UTC Thur May 1 2003Echo Response Time = 21 (ms)Remote IP Address : 14.1.1.1 Remote Product Id : 2198864392Remote Interface Type : 32 Remote Interface Index: 11Remote Circuit Index : 111Offered Frames/PDUs : 2 Delivered Frames/PDUs: 2Tx Total Frames: 2 Rx Total Frames: 2Tx Total Octets: 60 Rx Total Octets: 70Tx DeFrames: 0 Rx DeFrames: 0Tx MaxThroughput: 448 Rx MaxThroughput: 528Rx FecnSeconds: 0 Rx BecnSeconds: 0OctetsAboveCIR: 0 FramesAboveCIR: 0Unavailable Seconds: 0Tx Burst Percent1(sec): 900 Tx Burst Percent2(sec): 0Tx Burst Percent3(sec): 0 Tx Burst Percent4(sec): 0Tx Burst Percent5(sec): 0Router# show rtr enhanced-history collection-statistics 3Entry number: 3Aggregation Interval: 900!-----------------------------------------------------!Bucket Index: 1Aggregation start time 21:37:29.988 UTC Fri May 2 2003Target Address:Number of failed operations due to a Disconnect: 0Number of failed operations due to a Timeout: 0Number of failed operations due to a Busy: 0Number of failed operations due to a No Connection: 0Number of failed operations due to an Internal Error: 0Number of failed operations due to a Sequence Error: 0Number of failed operations due to a Verify Error: 0Sample Index = 183Echo Receive Time = *00:22:30.006 UTC Thur May 1 2003Echo Response Time = 21 (ms)Remote IP Address : 14.1.1.1 Remote Product Id : 2198864392Remote Interface Type : 32 Remote Interface Index: 11Remote Circuit Index : 111Offered Frames/PDUs : 2 De
