service performance manager - ca technologies - ca...

Service Performance Manager

User GuideDocument 5093

NoticeThis documentation (the "Documentation") and related computer software program (the "Software") (hereinafter collectively referred to as the "Product") is for the end user's informational purposes only and is subject to change or withdrawal by CA at any time.

This Product may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Product is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the Documentation for their own internal use, and may make one copy of the Software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the Software are permitted to have access to such copies.

The right to print copies of the Documentation and to make a copy of the Software is limited to the period during which the license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user's responsibility to certify in writing to CA that all copies and partial copies of the Product have been returned to CA or destroyed.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS PRODUCT "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS PRODUCT, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

The use of this Product and any product referenced in the Documentation is governed by the end user's applicable license agreement.

The manufacturer of this Product is CA.

This Product is provided with "Restricted Rights." Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7013(c)(1)(ii), as applicable, or their successors.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Copyright © 2007 CA. All rights reserved.

3

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

SPECTRUM Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Document Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

SPM Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Test Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Test Types Supported by SPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Test Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

SPM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Performance Agents and MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

SPM Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Multiple Ways to Create Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Test Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Automated Test Creation with Test Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Single-Point Test Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Report Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

SPM Tests and Service Level Agreement Management . . . . . . . . . . . . . . . . . . . . . . . . 18

User Roles and SPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

SPM for Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

SPM for Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Access SPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Basic Tasks Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

About Test Host and Test Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Secure an SPM Test Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Secure an SPM Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Overwrite a Security String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4 Service Performance Manager User Guide

Contents

Chapter 2: Finding SPM Components with SPM Searches . . . . . . . . . . . . . . . . . . . . . . . 23

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Perform an SPM Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Search for Specific SPM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

All Test Component Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Criteria-Based Test Host Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Criteria-Based Test Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 3: Working with Performance Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Create Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Create a New Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Create a Different Version of an Existing Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Information About Specific Test Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

DHCP Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32DNS Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32FTP Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32HTTP Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32ICMP (Ping) Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Jitter Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Traceroute Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34POP3 Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34SMTP Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34TCP Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34UDP Echo Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Discover Tests in the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

About Discovery Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Read-Only Discovery Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Read/Write Discovery Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Run Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configure SPM Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Configure General Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

General Parameters - Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39General Parameters for Specific Test Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40About the Test Host Location Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Configure Advanced Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Schedule a Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Create a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Specify Alarm Thresholds for a Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Establish Baseline Data to Determine Valid Thresholds . . . . . . . . . . . . . . . . . . . . . 47Run Tests on an On-Demand Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Activate and Deactivate Test Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Contents

Service Performance Manager User Guide 5

Manage Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Edit a Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Delete a Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 4: Working with Test Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Create Test Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Create a New Test Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Create a Different Version of an Existing Test Template . . . . . . . . . . . . . . . . . . . . . . . 55

Apply a Test Template to Test Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Selectively Apply a Test Template to One or More Test Hosts . . . . . . . . . . . . . . . . . . . 56

Apply a Test Template to a Global Collection Container . . . . . . . . . . . . . . . . . . . . . . . 57

Example Implementation Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Manage Test Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Edit a Test Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Remove the Association Between a Template and a Global Collection . . . . . . . . . . . 61Delete a Test Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 5: Viewing SPM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Test Host Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Test Host Information in the Component Detail View . . . . . . . . . . . . . . . . . . . . . . . . . 64

Test Host Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Test List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Test Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Test Information in the Component Detail Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Test Performance Information in the Component Detail Panel . . . . . . . . . . . . . . . . . . 66

Specify the Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Specify the Test Result Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67View Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Adjust an Axis Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67About the Effect of a Test’s Filter Timeout Data Setting on a Performance Graph . . . 68

SPM Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 6: Generating Reports on Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

SPM Reports from SRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Report Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

How You Generate Performance Reports with SRM . . . . . . . . . . . . . . . . . . . . . . . . . . 72


Contents

SPM Reports from SRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Data Logging Event Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

SPM Result Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

SPM Data Export Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

SPM Test Modification Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 7: Creating and Managing RTM Tests with Command Line Interface (CLI) . . 79

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Create Tests in CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Run Tests in CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Edit Tests in CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Get Test Results in CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Test Parameters Used in CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Required Parameters for Creating Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Required Parameters for Scheduling Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Optional Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Threshold Type Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Latency Threshold Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Packet Loss Threshold Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87HTTP DNS Threshold Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87HTTP TCP Threshold Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88HTTP Download Threshold Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Jitter Source to Destination Packet Loss Threshold . . . . . . . . . . . . . . . . . . . . . . . . 90Jitter Destination to Source Packet Loss Threshold . . . . . . . . . . . . . . . . . . . . . . . . 91Jitter MIA Threshold Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Jitter Late Arrival Threshold Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Jitter Busies Threshold Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Jitter Positive Source to Destination Threshold Parameters . . . . . . . . . . . . . . . . . . 95Jitter Positive Destination to Source Threshold Parameters . . . . . . . . . . . . . . . . . . 96Jitter Negative Source to Destination Threshold Parameters . . . . . . . . . . . . . . . . . 97Jitter Negative Destination to Source Threshold Parameters . . . . . . . . . . . . . . . . . 98

Test Action Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Test Status and Test Results Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

SPM LatestStatus (0x4560004) Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Appendix A: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Firmware Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Timeout Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

ICMP Ping Tests and Extreme Summit Test Host Devices . . . . . . . . . . . . . . . . . . . . . 103

Traceroute Tests and iAgent Test Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Contents


Test Scheduling Caveats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Scheduling Tests in Geographically Distributed Environments . . . . . . . . . . . . . . . . . . 104

Schedule Time Interval and CA SystemEDGE Agent Test Hosts . . . . . . . . . . . . . . . . . 104

Large Number of Tests on a Router Running Off Schedule . . . . . . . . . . . . . . . . . . . . 105

Delayed SpectroSERVER Activation Resulting from External Reads . . . . . . . . . . . . . . . . . 105

Appendix B: SPM Event Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Event Code Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

About SPM Timeout Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115


Contents

9

Preface

Content

“Audience” on page 9

“Organization” on page 9

“Text Conventions” on page 10

“SPECTRUM Documentation” on page 11

“Document Feedback” on page 11

AudienceThis manual is intended for network administrators who use Service Performance Manager (SPM) to configure and run Response Time Tests (RTTs). This manual assumes that you have a working knowledge of SPECTRUM, OneClick, and the various RTT agents included with your network assets.

OrganizationThis guide is organized as follows:

Chapter 1, “Introduction,” on page 13 provides an overview of SPM concepts and features, describes user roles and privileges, describes how to access SPM components from OneClick Console, provides SPM implementation guidelines, and outlines the tasks you can perform with SPM.

Chapter 2, “Finding SPM Components with SPM Searches,” on page 23 describes how to use OneClick Console search capabilities to locate SPM components.

Chapter 3, “Working with Performance Tests,” on page 29 describes how to create tests, discover tests configured on tests hosts, configure tests, schedule tests, set test thresholds, run tests, and manage tests.

Chapter 4, “Working with Test Templates,” on page 53 describes how to create test templates, apply test templates to Global Collection containers, and manage test templates.


Preface

Chapter 5, “Viewing SPM Information,” on page 63 describes SPM information views in OneClick Console.

Chapter 6, “Generating Reports on Test Data,” on page 71 describes SPECTRUM resources for generating SPM reports.

Chapter 7, “Creating and Managing RTM Tests with Command Line Interface (CLI),” on page 79 provides example response time test scripts and describes command line parameters and action codes.

Appendix A, “Troubleshooting,” on page 101 identifies error messages that may be generated during SPM operations and describes corrective actions. It also addresses other maintenance and optional configuration issues.

Appendix B, “SPM Event Codes,” on page 107 lists SPM events by event code, event name, the model types the event can be asserted on, the alarm generated or cleared (if any), and alarm severity.

Text ConventionsThe following text conventions are used where applicable in this document:

Element Convention used Example

Variables

(The user supplies a value for the variable.)

Courier and Italic in angle brackets (<>)

Type the following:

DISPLAY=<workstation name>:0.0 export display

The directory where you installed SPECTRUM or OneClick

(The user supplies a value for the variable.)

<$SPECROOT> Navigate to:

<$SPECROOT>/app-defaults

Linux, Solaris, and Windows directory paths

Unless otherwise noted, directory paths are common to all operating systems, with the exception that slashes (/) should be used in Linux and Solaris paths, and backslashes (\) should be used in Windows paths.

<$SPECROOT>/app-defaults on Linux and Solaris is equivalent to <$SPECROOT>\app-defaults on Windows.

On-screen text Courier The following line displays:

path=”/audit”

User-typed text Courier Type the following path name:

C:\ABC\lib\db

Cross-references Underlined and hypertext-blue See “Organization” on page 9.

References to SPECTRUM documents (title and number)

Italic OneClick Console User Guide (5130)

SPECTRUM Documentation


SPECTRUM DocumentationThe SPECTRUM documentation set is available online at:

http://support.concord.com/support/secure/products/Spectrum_Doc/

Use this site to download the latest documentation updates and additions. To log on to the documentation site, you must supply your contract number and license number.

Document FeedbackPlease send feedback regarding SPECTRUM documents to the following e-mail address:

[email protected]

Thank you for helping us improve our documentation.

http://www.aprisma.com/support/secure/manuals/

mailto:[email protected]


Preface

13

Chapter 1: Introduction

Content

“Overview” on page 13

“SPM Concepts” on page 14

“SPM Features” on page 17

“User Roles and SPM” on page 19

“Getting Started” on page 19

OverviewService Performance Manager (SPM) lets you create, run, and manage performance tests supported by various vendor products managed by SPECTRUM. Performance testing addresses multiple network management requirements. A few representative examples are listed as follows:

• Establishing IT services delivery standards — Enables you to establish service (e.g., HTTP transactions, login validations, file transfers) delivery benchmarks against which you can measure how well services are delivered to service consumers. Understanding what constitutes optimal, acceptable, and unacceptable levels of service delivery is a prerequisite to developing realistic service level agreement goals and obligations.

• Capacity planning — Enables you to determine whether service demands by consumers are underutilizing or exceeding current IT infrastructure capacity.

• Proactive fault management — Enables you to determine where service delivery degradation trends are developing before they impact service customers.



SPM ConceptsThis section describes the SPM components you work with to configure and run performance tests.

Test Hosts

An SPM test host is a model of a device or software agent that supports one or more types of performance tests for IT services. SPECTRUM creates a test host model of type RTM_TestHost during model discovery for each SPM capable device.

A few examples of test host devices and agents are:

• A Cisco router

• A Sun Workstation running iAgent

• A SpectroSERVER

Important: Devices and agents that support SPM must be modeled with read/write community names in order to run SPM tests. Attempts to run tests on test hosts (with the exception of SpectroSERVERs) that are not modeled with a read/write community string will cause an alarm on the test host model.

Tests

A performance, or response time, test is an IT service operation of a particular type (retrieve a Web page, download a file, establish a TCP connection) that returns a result you can use to assess the service’s performance. Where a single test returns a result that can help you determine whether there is a current problem with a service’s viability, a group of tests return aggregate results that can help you determine a service’s viability over a particular timeline or to determine baseline performance standards you can factor into any number of decision making processes regarding your infrastructure.

SPM enables you to create tests (model type RTM_Test) for your test hosts and discover tests previously configured on managed devices. You can schedule tests, run tests on an on-demand basis, specify test thresholds, and incorporate tests into service management and service level agreement systems.

Test Types Supported by SPM

Performance tests supported by SPM fall into three different test categories:

• Network response time tests — These are the most basic network response time tests.

• Network service response time tests — These measure the response time of essential network services.

• Network application response time tests — These measure the response time of essential network applications.

Table 1-1 describes test types supported by SPM.

SPM Concepts


Test Templates

Test templates contain test parameters for a particular test type that you can selectively apply to multiple test host models or automatically apply to test host models added to Global Collection models. SPECTRUM monitors Global Collection content and automatically creates the test specified by the template on test hosts added to the Global Collection. Regardless of how a test template is applied to test hosts, the result is the same — the test defined by the template is created on the test hosts.

See Chapter 4, “Working with Test Templates,” on page 53 for more information.

Table 1-1: SPM Supported Test Types

Test Category Test Type What It Tests

Network response time ICMP Ping ICMP Echo Request messages from the test host to the destination address.

If the test host and source addresses are not the same, then another ICMP Echo Request is issued from the test host to the source address. The resulting ICMP Echo Reply messages are used to determine the round-trip time between the source address and the destination address. A second metric, packet loss, results from these tests. When a series of ICMP Echo requests are made, which is typical of these tests, a coarse measure of packet loss is possible.

Jitter Latency and losses between two endpoints.

This test is designed to measure the quality of the network for applications that cannot tolerate loss or latency, such as VoIP.

Traceroute Round-trip ICMP Echo from the host address to each layer three hop in the discovered path.

Network service response time DHCP Dynamic Host Configuration Protocol IP address assignment.

DNS Domain Name Service domain name to IP address translation.

Network application response time FTP File Transfer Protocol transaction time.

HTTP Hyper Text Transfer Protocol transaction time.

POP3 Post Office Protocol transaction time.

SMTP Simple Mail Transfer Protocol transaction time.

TCP Transmission Control Protocol connection time.

UDP Echo User Datagram Protocol transmission echo round-trip delay.



SPM Alarms

SPM generates various events representing significant occurrences related to response time testing. Some of these events produce alarms designed to notify you that a user-actionable event has occurred. See Appendix B, “SPM Event Codes,” on page 107 for information on these events and alarms.

Also, you can configure SPM to generate an alarm whenever the duration of a response time test exceeds a predetermined threshold on a specific link or path. See “Specify Alarm Thresholds for a Test” on page 45 and “SPM Alarms and Events” on page 70 for more information.

Performance Agents and MIBs

SPM supports the following performance agents and MIBs:

• RFC2925

• Cisco IOS IP SLAs Agent

• CA eHealth SystemEDGE Service Availability agent

• Network Harmoni SLAplus Agent

• iAgent

• JUNOS Real Time Performance Monitor

• Cisco Ping MIB

• Wellfleet Ping MIB

• SPECTRUM ICMP Daemon (ICMPd)

Note: Only current Cisco routers support the RTTMON MIB. Older, pre 11.2 deployments may support only the Cisco Ping MIB.

Table 1-2 lists tests supported by the performance agents and MIBs.

Table 1-2: Agents and Tests

Agents/MIBs Tests

RFC2925 ICMP Ping

Important: You must verify with the vendor whether or not a particular device supports ICMP ping through the RFC2925 MIB.

Cisco IOS IP SLAs Agenta,b

DHCP, DNS, FTP, HTTP, ICMP Ping, Jitter, TCP, UDP

CA eHealth SystemEDGE Service Availability agent

DNS, FTP, HTTP, ICMP Ping, POP3, TCP, SMTP

SPM Features


SPM FeaturesSPM supports multiple vendor and agent performance tests solutions and multiple implementation features.

Multiple Ways to Create Tests

SPM enables you to create tests in the following ways:

• Create a new test from scratch.

• Create a new version from a copy of another test.

• Use SPM Discovery to locate tests configured on test hosts.

• Apply test templates to Global Collection containers. When a test host is added to the container, a test with the configuration settings provided by the template is automatically created on the test host.

Test Scheduling

You can use SPM scheduling capabilities to automate your performance testing. You can use pre-configured schedules provided by OneClick with SPM or you can create your own custom schedules. Scheduling tests enables you to implement performance testing during peak and off-peak hours so you can compare the results from each period and determine realistic performance standards.

Network Harmoni SLAplus Agent

OEM Vendors:Agilent Technologies, InfoVista, Peregrine Systems, Ericsson, Opticom, RedPoint, HP, Micromuse, Response Networks

DNS, HTTP, ICMP Ping

iAgentc DNS, FTP, HTTP, ICMP Ping, POP3

JUNOS Real Time Performance Monitor

ICMP Ping, Jitter

Other Support Cisco Ping MIB, Wellfleet Ping MIBd, SPECTRUM ICMP Daemon (ICMPd)

a. Cisco IOS IP SLAs Agent is supported on Cisco routers running IOS 12.0 or greater.

b. For full-mesh measurements between hubs, Cisco recommends that shadow routers dedicated for IOS IP SLAs use be employed. For more information see Cisco IOS IP SLAs documentation.

c. For more information on SPECTRUM’s iAgent integration, see the iAgent User Guide (5159).

d. SPM supports the Wellfleet-Ping-MIB for Wellfleet routers. It does not support the Nortel Contivity Ping MIB (CONTIV-ITY-INFO-V1-MIB).

Table 1-2: Agents and Tests (Continued)

Agents/MIBs Tests



For example, you may want to schedule a test to run at a specific interval continually, 24 hours a day, seven days a week. Or you may want to schedule tests to run during or after intervals when the infrastructure is in high demand. Whatever the case, you can create test schedules that meet your requirements.

Automated Test Creation with Test Templates

SPM Test templates enable you to set up test configurations and apply them to multiple test hosts. Test templates leverage Global Collection container capabilities. By applying a template to a Global Collection container, you automate the test creation process. SPM creates the test specified by the template for any test host added to the container that supports the test. Modifications to test parameters are equally simple to perform. When you change template parameters, those changes extend to the parameters for all tests created from the template.

Single-Point Test Management

SPM provides you with complete access and control over your test components on multiple landscapes from a single landscape. This means you can create, configure, locate, and manage tests from a single OneClick Console.

Report Options

You can generate summary and detailed SPM performance test result information in a variety of text and graphical formats using the SPECTRUM Report Manager (SRM) application. You can also generate graphical timeline reports using SPECTRUM’s SSLogger and Report Gateway options.

SPM Tests and Service Level Agreement Management

Performance testing is an indispensable component for establishing IT service-obligation benchmarks and monitoring service performance. SPM response time test results provide a finer measure of service performance and viability than a service monitoring system that merely determines whether a service is up or down. Service consumers may consider service delivery speed the determining factor in whether a service meets or does not meet their requirements.

For example, a service consumer may consider a 20-second wait for a Web page as unacceptable when it takes only five seconds on average to retrieve and load a page. In this case, service consumers may consider the sluggish Web service as essentially unavailable, even though the service is accessible.

SPM enables you to specify response time thresholds to measure service performance in terms of latency. This means a service level agreement can stipulate that a service provider guarantee a particular level of response time that meets the service consumer’s requirements. See the Service Manager User Guide (5155) for complete information on creating and managing services and service level agreements in SPECTRUM.

User Roles and SPM


User Roles and SPMA user’s access to SPM functionality depends on the rights granted to the user. A SPECTRUM administrator can configure user roles and rights in OneClick. For more information on configuring user rights, see the OneClick Administration Guide (5166).

SPM for Operators

When logged into SPM as an operator, you can view information for tests and test hosts and run existing response time tests. As an operator, you cannot create, delete, edit, or copy any tests. Operators cannot change the state of the test on any test hosts.

SPM for Administrators

When logged into SPM as an administrator, you have full access to all SPM functionality, including creating, editing, deleting, and discovering tests.

Getting StartedThis section describes how to access SPM components from OneClick Console, outlines tasks you perform with SPM and where to find information about those tasks, and provides important information about how to establish security for tests and test hosts.

Access SPM

SPM components are integrated with and accessed from the OneClick application interface.

Procedure

To access SPM components:

1. Open OneClick Console.

2. Click the Locater tab in the Navigation panel.

3. Click the SPM Searches folder.

Figure 1-1 shows SPM components in the SPM Searches folder.

“Basic Tasks Overview” on page 20 describes the SPM task options and where you can find information about them in this manual.



Figure 1-1: SPM Components

Basic Tasks Overview

Once you have accessed the SPM components list in the OneClick Console Locater, you can begin to work with SPM components:

• To locate a specific test component or groups of components (tests, test hosts, test templates), run a search of SPECTRUM. See Chapter 2, “Finding SPM Components with SPM Searches,” on page 23 for complete information on performing criteria-based searches for SPM components.

• To create tests, configure test parameters, schedule tests, specify test thresholds, manually run tests, discover tests on test hosts, and edit and delete tests, see Chapter 3, “Working with Performance Tests,” on page 29 for instructions.

• To create test templates, selectively apply them to test hosts or to Global Collection containers that include test hosts, and edit and delete test templates, see Chapter 4, “Working with Test Templates,” on page 53 for instructions.

• To create, run, and edit tests from the Command Line Interface, see Chapter 7, “Creating and Managing RTM Tests with Command Line Interface (CLI),” on page 79 for instructions.

Getting Started


• To generate reports on tests, see Chapter 6, “Generating Reports on Test Data,” on page 71 for information on generating reports with SPECTRUM Report Manager and information about time-series reports you can generate with SPECTRUM Report Gateway.

About Test Host and Test Security

You can use the security string setting for test and test host models to restrict access to them only to authorized personnel.

Note: This section assumes you have experience invoking detailed views of SPECTRUM models in OneClick Console and privileges to modify security string settings for models. See the OneClick Administration Guide (5166) for more information on setting up SPECTRUM model security.

For instructions on how to set or modify a security string for a test host or test, see one of the following procedure descriptions:

• “Secure an SPM Test Host” on page 21

• “Secure an SPM Test” on page 22

• “Overwrite a Security String” on page 22

Secure an SPM Test Host

Procedure

To secure a test host:

1. In the Component Details panel, expand the Test Host Details menu for the test host you want to secure.

2. Click set for the Security String parameter (Figure 1-2).

Figure 1-2: Set Security String for SPM Test Host.

3. Specify the security string. Permission to access the test host is granted only to privileged users defined by the security string entered.

Note: All SPM tests associated with a “secured test host” automatically inherit the host security string. To overwrite or remove a security string at a test level (or test host level), see “Overwrite a Security String” on page 22.



Secure an SPM Test

Procedure

To secure a test:

1. In the Component Details panel, expand the Test Details > General menu for the test you want to secure.

2. Click set for the Security String parameter (Figure 1-3).

Figure 1-3: Set Security String for Test

3. Specify the security string. Permission to access the test is granted only to privileged users defined by the security string entered.

Overwrite a Security String

Procedure

To overwrite a security string for a test host or a test:

1. In the Component Details panel, Click set for the Security String parameter.

2. Edit or remove the security string.

23

Chapter 2: Finding SPM Components with SPM Searches

Content


“Perform an SPM Search” on page 23

“Search for Specific SPM Components” on page 25

OverviewSPM Searches provide multiple search criteria options you can use to find existing SPM tests, test hosts, and test templates in SPECTRUM. For complete information on OneClick Search capabilities and configuration options, see the OneClick Console User Guide (5130).

Perform an SPM SearchYou perform search operations from the Locater view in the OneClick Navigation panel.

Procedure

To perform an SPM search, select the type of search you want to run from the SPM Searches folder and click the Search button (Figure 2-1). Some searches require you to enter values (typically IP addresses) in a Search dialog box before you execute the search.



Figure 2-1: SPM Searches in OneClick’s Locater option

Search results appear under the Results tab in the OneClick Contents panel (Figure 2-2). You can select an item returned by a search, view information about it, and perform whatever operation it supports.

Figure 2-2: Search Results

Search for Specific SPM Components


Search for Specific SPM ComponentsThis section describes the different types of searches supported by SPM.

All Test Component Searches

This search category enables you to search for all test hosts, tests, and test templates modeled in SPECTRUM.

Criteria-Based Test Host Searches

You can search for test hosts modeled in SPECTRUM that meet criteria you specify.

IP Address

This search finds the test host with the Network Address or tests hosts associated with the address you specify in the Search dialog box (Figure 2-3).

Note: The Search dialog box does not support searching on partial IPs (for example, 10.253).

Figure 2-3: Test Hosts By - IP Address

State

This search finds test hosts in the following states:

• Active - test hosts that have been activated

• Contact Lost - test hosts that have stopped responding to polls

• Inactive - test hosts that have not been activated or have been deactivated

Supported Test Type

This search finds test hosts that support the following test types:

• DHCP • ICMP • TCP

• DNS • Jitter • TRACEROUTE

• FTP • POP3 • UDP

• HTTP • SMTP



Test Discovery Supported

This search finds test hosts that support test discovery.

Test Discovery Unsupported

This search finds test host that do not support test discovery.

Criteria-Based Test Searches

You can search for tests modeled in SPECTRUM that meet criteria you specify.

Destination Address And Port Number

This search finds tests configured with the Destination Address and Destination Port you specify in the Search dialog box (Figure 2-4). You can enter a partial address string (i.e., 138.42) in the dialog box. Searches with the destination port set to 0 return tests for which destination port is not applicable.

Figure 2-4: Test By - Destination Address and Destination Port

Discovery State

This search finds tests that meet the following criteria related to SPM Discovery:

• Discovery Read-Only — SPM tests discovered in Read-Only mode via SPM Discovery.

• Discovery Read/Write — SPM tests discovered in Read/Write mode via SPM Discovery.

• RTM Domain — SPM Tests created via the SPM user interface (and not through SPM Discovery).

• Stale Different Type — SPM-discovered tests that have a corresponding test on the device of a different test type.

• Stale Entry Not Present — SPM-discovered tests that no longer have a corresponding test on the device.

See “Discover Tests in the Network” on page 35 for information about the SPM Discovery feature.

Name

This search enables you to find the test with the Test Name you specify in the Search dialog box (Figure 2-5).

Search for Specific SPM Components


Figure 2-5: Tests By - Name

Scheduled

This search finds all scheduled tests.

Source Address

This search finds tests configured with the Source Address you specify in the Search dialog box (Figure 2-6). You can enter a partial address string (i.e., 135.48.200) in the dialog box.

Figure 2-6: Test By - Source Address

Source Address, Destination Address, and Port Number

Enter the Source Address, Destination Address, and Destination Port for the test and click OK (Figure 2-7). You can enter partial strings to search for a test using this search. Note that searches with port number set to 0 will return tests for which destination port is not applicable (N/A).



Figure 2-7: Tests By - Source Address, Destination Address, and Port Number

Tests By - Status

This search provides the capability to search for a test by one of the following test statuses:

Tests By - Threshold Exceeded

This search provides a list of all of the tests exceeding their thresholds.

Tests by - Type

Use this search to find all tests of one of the following test types:

• Bad Community String • Scheduled

• Bad Configuration • Stopped

• Device Disabled • Timeout

• Ready To Run • User Disabled

• Running

• DHCP • Jitter

• DNS_LOOKUP • POP3

• FTP • SMTP

• HTTP • TCP_CONNECT

• ICMP_Ping • TRACEROUTE

• UDP

29

Chapter 3: Working with Performance Tests

Content

“Create Tests” on page 29

“Discover Tests in the Network” on page 35

“Configure SPM Tests” on page 38

“Run Tests on an On-Demand Basis” on page 47

“Manage Tests” on page 50

Note: For information about creating and managing response time tests using SPECTRUM’s Command Line Interface, see Chapter 7, “Creating and Managing RTM Tests with Command Line Interface (CLI),” on page 79.

Create TestsYou can create a performance test on a test host using either of the following methods:

• Create a new test from scratch

• Save a different version of an existing test

You can create tests on test hosts that have not been activated. To run the tests, however, the test hosts must first be activated. See “Activate and Deactivate Test Hosts” on page 48 for instructions.

You can also discover pre-configured tests on test hosts using SPM Discovery. It models tests that have been created on test hosts using a non-SPM method (i.e., command line). See “Discover Tests in the Network” on page 35 for more information.



Create a New Test

You can create a new test of any type supported by the test host you select.

Procedure

To create a new test:

1. Use SPM Searches to find test hosts as described in Chapter 2, “Finding SPM Components with SPM Searches,” on page 23.

The test hosts appear in the Contents panel.

2. Select the test host for which you want to create the test, and then use one of the following methods (Figure 3-1) to select a test type:

• Click the New icon and select a test type.

• Right-click a test host entry, select New Test, and select a test type.

Figure 3-1: Create Test

The New Test dialog box appears. It enables you to configure test parameters. See “Configure SPM Tests” on page 38 for complete information on test parameters.

3. Configure test settings, and then click OK to save the test.

Information about the new test you created on the test host appears under the Information tab in the Component Detail panel.

Create Tests


Create a Different Version of an Existing Test

You can create a test by saving a unique version of an existing test. The test can include the same parameter settings, but it must have a different name. Also, you can save the new test to the base test’s test host or a different test host.

Note: You cannot copy tests between domains running different versions of SPECTRUM.

Procedure

To create a new test from a copy of another test:

1. Use SPM Searches to find tests as described in Chapter 2, “Finding SPM Components with SPM Searches,” on page 23.

The tests appear in the Contents panel.

2. Select the test you want to copy, and then use one of the following methods (Figure 3-2) to open the Copy Test dialog box:

• Click the Copy icon.

• Right-click the test you want to copy, and then select Copy Test.

Figure 3-2: Copy Test

The Copy Test dialog box appears. It includes configuration settings you can modify for your new test. See “Configure SPM Tests” on page 38 for complete information on test parameters.

Copied tests are disabled by default, and “_COPY” is appended to the test name. You may want to rename the test, but it is not required.



3. Modify test configuration settings, and then click OK to save the new test.

Information about the new test you created on the test host appears under the Information tab in the Component Detail panel.

Information About Specific Test Types

This section includes information about specific test types you should review before you run the tests.

DHCP Tests

DHCP tests measure the round-trip time (latency) required to get an IP address. The DHCP server must be on the same subnet as the test host performing the DHCP test. To configure the test host to work with your DHCP server’s IP address, see the documentation for the device. For DHCP tests to work on a router, one of the neighboring routers must be a DHCP agent or relay. See the documentation for your device for more information.

Note: DHCP test latency result values that are higher than the value set for timeout for tests run on Cisco router test hosts are the result of a known issue with Cisco IOS 12.2(2)T. See “Firmware Issues” on page 101.

DNS Tests

DNS tests measure DNS lookup time. DNS-based host name-to-address translation must be enabled on the test host device performing the DNS test. To check to see if DNS lookup is enabled and/or to enable it, see the documentation for the device.

DNS test results include the following metrics:

• Latency

• Packet Loss

FTP Tests

FTP tests measure the round-trip time to transfer a file.

FTP test results include the following metrics:

• Latency

• Packet Loss

Note: FTP tests run on Cisco test hosts using the RTTMON MIB require that you enter the user name, password, and file name. FTP tests run on CA eHealth SystemEDGE Service Availability test hosts require that you enter a user name and password, but do not need a file name.

HTTP Tests

HTTP tests measure the round-trip time to get a Web page.

HTTP test results include the following metrics:

• Latency

• HTTP DNS Resolution Time

Create Tests


• HTTP TCP Connection Time

• HTTP Download Time

Considerations

• HTTP tests performed from Harmoni and iAgent test hosts produce latency results only.

• A HTTP test may fail on some Cisco systems using HTTP 1.1. For more information see “Firmware Issues” on page 101.

• The HTTP version configuration setting is only available for HTTP tests run from Cisco test hosts. The Proxy URL setting is only available for HTTP tests run from Cisco and CA eHealth SystemEDGE Service Availability test hosts. See “Configure Advanced Parameters” on page 42 for more information.

• SPM HTTP tests that require authentication are not supported on Cisco test hosts.

ICMP (Ping) Tests

ICMP Ping tests measure round-trip time from a source to a destination address.

ICMP Echo (Ping) test results include the following metrics:

• Latency

• Packet Loss

Considerations

• When using the Cisco IOS IP SLAs Agent, you can configure the ICMP Echo operation payload size by setting the request size. The router adds 36 bytes to the size specified. For example if the request size is 28 bytes, the actual ICMP Packet size is 64 bytes (of IP packet). See Cisco’s IOS IP SLAs Agent documentation for more information.

• The Harmoni agent does not support the configuration of sample count or packet size for ICMP Ping tests.

Jitter Tests

Jitter tests both latency and losses between a test host and a voice-enabled endpoint, but adds a finer measure of the statistical behavior of a sequence of requests. Additionally, Mean Opinion Scoring (MOS) is available when using Cisco test hosts. MOS provides a numerical measure of the quality of human speech at the destination end of the circuit.

Jitter test results include the following metrics:

• Latency • Source to Destination Packet Loss

• Destination to Source Packet Loss • Missing in Action Packet

• Late Arrival Packet • Jitter Busies

• Jitter Positive Source to Destination • Jitter Positive Destination to Source

• Jitter Negative Source to Destination • Jitter Negative Destination to Source

• Mean Opinion Scoring



Traceroute Tests

Traceroute provides both the discovery of the layer three hops between the source and destination addresses, as well as the round-trip ICMP Echo measurement from the host address to each hop in the discovered path.

Traceroute test results include the following metrics:

• Latency

• Packet Loss

• For each hop, IP address and round trip time

POP3 Tests

POP3 tests measure POP3 response (transaction) time.

POP3 test results include the following metrics:

• Latency

• Packet Loss

SMTP Tests

This measures SMTP mail server response (transaction) time.

SMTP test results include the following metrics:

• Latency

• Packet Loss

TCP Tests

TCP tests measure the time required to create a TCP connection.

TCP Connection test results include the following metrics:

• Latency

• Packet Loss

UDP Echo Tests

UDP Echo measures round-trip delay.

Results from UDP Echo tests are:

• Latency

• Packet Loss

UDP tests must be configured to target a destination port known to be listening for UDP traffic. For example, many Cisco devices running IOS IP SLAs use port 1967 and UNIX systems use port 7. Failure to do this can result in timeouts for UDP tests. The Destination Port parameter is set in the General option for UDP tests. (See “Configure General Parameters” for more information.)

Discover Tests in the Network


Discover Tests in the NetworkSPM Test Discovery enables you to discover and model performance tests that have been configured on test hosts but not with SPM.

Considerations

• You must have administrator role privileges to use SPM Test Discovery.

• You must use a device that is supported by SPM Test Discovery.

About Discovery Modes

When you run a discovery, you are prompted to choose whether you want the tests to be created in SPM in one of the following discovery modes:

• Read-Only

• Read/Write

Read-Only Discovery Mode

When you discover tests in read-only mode, you will not be able to edit test configurations after the tests are modeled in SPECTRUM. That is, you will not have SNMP set privileges to the tests. Test Discovery takes schedule information from the tests configured on the device, and then reads test results at the appropriate interval.

Considerations

• Administrator access to read-only tests is similar to that of the Operator user role, with the exception of full access to Threshold parameters. For more information see “Specify Alarm Thresholds for a Test” on page 45.

• Read-only tests cannot be run manually; they must be scheduled.

• Sample Count is always 1.

• You can copy read-only tests to create SPM-based tests.

• To ensure that data from read-only tests are available for response time reports you can generate with SPECTRUM Report Manager, make sure that the test is in the Active state at the time of the read-only discovery. You should also verify that the Events service indication in OneClick is showing the “Up” status.

Read/Write Discovery Mode

When you discover tests in read/write mode, you will be able to edit test configurations after the tests are modeled in SPECTRUM. That is, you will have SNMP set privileges to the tests. Tests on these test hosts can be treated exactly like tests created manually in SPM. That is, they can be run on demand, stopped, and edited. See “Configure SPM Tests” on page 38 for more information.

Considerations

• If the test was activated on the device, the Schedule State field for the Schedule parameter field is set to Enabled.

• Sample Count is set to 1.



Run Discovery

Running a test discovery involves first locating test hosts that support test discovery and then running the discovery on the test hosts.

Procedure

To locate test hosts that support test discovery and run test discovery:

1. Run the SPM Searches option, Test Hosts By > Test Discovery Supported, to locate discovery-compatible tests hosts.

The Contents panel lists test hosts that support test discovery.

2. Select one or more test hosts for which you want to discover tests, and then click the Discover Tests icon (Figure 3-3).

Figure 3-3: Discover Test

Note: The Discover Tests button is disabled if a selected test host is not active or if contact with the host is not established. For more information on activating and deactivating a test host, see “Activate and Deactivate Test Hosts” on page 48.

If the selected test host supports both Read/Write and Read-Only discovery modes, the Discover Tests: Select Discovery Mode dialog (Figure 3-4) appears.

Figure 3-4: Select Discovery Mode

3. Click the button for the test discovery mode you want to run.

The Discover Tests Complete dialog box appears (Figure 3-5) when discovery finishes searching. It indicates how many tests were created and or updated.

Discover Tests in the Network


Figure 3-5: Discover Tests Complete

The Events tab in the Component Detail panel provides additional information about the Discovery for the test host. Table 3-1 lists SPM Test Discovery event codes and descriptions.

Table 3-1: SPM Test Discovery Event Codes

Event Code Event Description

0x04560059 SPM Test No Longer On Device Event

If SPM Test Discovery fails to match an existing SPM Read-Only test to a table entry on the device, this event and a corresponding yellow alarm will be generated on the test model.

0x0456005a SPM Test No Longer Running On Device Event

If SPM reads the test results and detects that the numberOfPktsSent object on the device has not increased, and the operational state on the device is read and found to be InActive, this event will be generated and the following actions occur:

•No data is processed.

•Schedule state on the SPM test is set to Disabled, and no more data will be read.

0x0456005b SPM Duplicate Result Event If SPM reads the test results and detects that the numberOfPktsSent object on the device has not increased, and the operational state on the device is read and found to be Active, this event will be generated and the following actions occur:

•No data is processed.

•Schedule state on the SPM test remains Enabled, therefore data will be processed from the next scheduled test.



Configure SPM TestsWhenever you issue a create, copy, or edit test command, SPM displays a test configuration dialog box where you can specify test parameters, set up a test schedule, and specify test thresholds. Figure 3-6 shows example test configuration categories. Depending on the type of test you are configuring, the test configuration dialog box may contain different options under each configuration category, or may not offer all of the options described in this section.

Figure 3-6: Test Configuration Options

0x0456005c SPM Test Discovery Completion Event

This event, generated after an SPM Test Discovery has run, indicates the mode (Read-Only or Read/Write) in which the discovery was run. May contain any of the following error output:

•No Errors

•No SPM Tests Were Discovered

•Test type is invalid

•Test name is null

•Test timeout is 0

•Test frequency is 0

•Test packet size is 0

•Test sample count is 0

•Test port number is invalid

•Test IP Address is invalid

•Test URL is invalid

•Test host name is invalid

•Test user name is invalid

•Test password is invalid

•Test file name is invalid

0x0456005d SPM Test Type Mismatch Event If SPM Test Discovery matches an existing SPM Read-Only test to a table entry on the device, but it’s of the wrong test type, generate this event and corresponding yellow alarm on the test model.

0x0456005e SPM Stale Test Clear Event Clears 0x4560059 or 0x456005d if subsequent SPM Test Discovery clears condition.

Table 3-1: SPM Test Discovery Event Codes (Continued)

Event Code Event Description

Configure SPM Tests


Procedure

To configure a test:

1. Enter values for the test in the parameter categories for your particular test. For example, test scheduling is disabled by default. If you are not interested in scheduling test runs, you do not have to configure scheduling parameters. The same applies to the test thresholds.

2. Click OK in each parameter category you work with to save your settings. The OK button is disabled if you do not enter required values.

Configure General Parameters

The General tab lets you configure required parameters for a test. Figure 3-7 shows an example configuration dialog box for a ICMP Ping test.

Figure 3-7: General Parameters

General Parameters - Standard

Table 3-2 describes general parameters for all performance tests supported by SPM.

Table 3-2: Standard General Parameters

Parameter Description

Name Specifies the test name. Default: “New SPECTRUM Response Time Test”

Test Host Indicates the IP address of the test host for the test.

Latency Timeout Specifies the number of milliseconds allowed for the response. If no response is received before this timeout occurs, then SPECTRUM generates a timeout event. Any response that arrives after this timeout is ignored.

Default = 5000 milliseconds

Tip: Set the timeout to be higher than the threshold setting.

Note: The Harmoni agent does not support latency timeout configuration.

State Enables and disables the test.

Default = Enabled

Description Specifies test annotations. Default: “SPECTRUM Response Time Test”



General Parameters for Specific Test Types

Table 3-3 describes parameters that may or may not be included under the General tab, depending on the type of test you are working with.

About the Test Host Location Parameter

Test host location refers to the path between the source and destination of a response time test. The location is critical to response time measurement.

Test host locations:

• The test host is the source of the test. See “Source Location” on page 41.

Table 3-3: Test-Type General Parameters


Destination Address Specifies the destination address for the test except those of type DHCP, DNS, HTTP. You can enter an IP address or a host name.

Destination DNS Server Specifies the destination address of the DNS server for DNS tests. You can enter an IP address or a host name.

Lookup Name Specifies the IP Address, host name, or fully qualified domain name (FQDN) of the host in DNS tests.

Note: Some agents, such as iAgent, require the use of a FQDN rather than a host name.

Test Host Location Specifies the location of the test host on the path between the source and destination for ICMP Ping tests.

Default = Source

See “About the Test Host Location Parameter” on page 40 for more information.

Alternate Source Address Specifies the IP Address or host name of the test source location when it is not the test host, as in mid path location and extended path location ICMP Ping test scenarios.

See “About the Test Host Location Parameter” on page 40 for more information.

Browse Lets you choose an Alternate Source Address if the test host on which you are configuring the test is not the source (ICMP) or if you want to choose another test host if you are copying test configurations.

Destination URL Specifies the URL used in HTTP tests.

Destination Port Specifies the port number used by the Jitter, TCP, UDP test. For Mean Opinion Score (MOS) support in Jitter tests, the destination port should be an even numbered port in the range 16384 to 32766 or 49152 to 65534.

User Name Specifies the user name for FTP, POP3, or HTTP test authentication.

Password Specifies the password for FTP, POP3, or HTTP test authentication.

File Name Specifies the file path used for the FTP test.

Voice Test Specifies whether to test voice quality for Jitter tests.

Codec Type Specifies the VOIP codec (audio compression/decompression) type to test: G.711 U-law, G.711 A-law and G.729A.

Note: You can set a voice quality threshold value (100 - 500) for the selected codec with the Mean Opinion Score parameter under the Threshold tab.

Configure SPM Tests


• The test host is located between the source and destination points. See “Mid Path Location” on page 41.

• Test host is not located between the source and destination points. See “Extended Path Location” on page 42.

Note: Only ICMP Ping tests support mid path or extended path tests.

Mid path and Extended path tests are useful only when either the source or destination address is not a test host. In both of these test types, you must configure test host location.

Source Location

In the most common response time test scenario, the source, or starting point, of the test is also a test host (Figure 3-8). In this case, the test host generates a transaction directly with the destination and measures the RTT.

When the source of a test is a test host, response time measurements are the most direct and accurate. For this reason, you should set up tests with a test host as the source whenever possible.

Figure 3-8: Test Host and Source Location Are the Same

Mid Path Location

In a mid path test configuration (Figure 3-9), a test host lies on the path between the source and destination points for which RTT is being measured. The source of the test is not capable of being a test host, so it cannot initiate or perform any response time measurements. A mid path test measures response time as the sum of the following:

(response time (RTT1) from test host to the source) + (response time (RTT2) from test host to the destination).

This is a relative value which approximates actual RTT.

Figure 3-9: Test Host in Mid Path Location Between Source and Destination

Source&

Test HostDestination

RTT

Source Destination

RTT

Test Host RTT2RTT1



Extended Path Location

In an extended path test configuration (Figure 3-10), the source of the test is not capable of being a test host. Additionally, there is no test host located between the source and destination as in the “Mid Path Location” scenario. However, the source lies directly in the path between a test host and the destination. In this case, response time is measured as the difference between the following:

(response time (RTT2) from the test host to the destination) — (response time (RTT1) from the test host to the source)

This is a relative value which approximates actual RTT.

Figure 3-10: Test Host Is in an Extended Path Location

Configure Advanced Parameters

The Advanced tab lets you configure additional parameters for a given test type. Each test type has its own specific parameters. Figure 3-11 shows an example configuration dialog box for a ICMP Ping test.

Figure 3-11: Advanced Parameters

Table 3-4 describes Advanced parameters for all test types.

Test Host Destination

RTT

Source RTT2

RTT1

Configure SPM Tests


Table 3-4: Advanced Parameters


Sample Count Specifies the number of times a test is performed during a test run.

Note: RTTMON may occasionally perform more than the specified sample count repetitions for an SPM test.

Default = 5

Note: The Harmoni agent does not support the configuration of sample count.

Packet Size Specifies the value (in octets) that limits the size of the packets used in the test.

Note: The Harmoni agent does not support packet size configuration.

Type of Service Specifies the Type of Service (TOS) parameter for test packets sent by the test host. A typical implementation example would be to create a response time test with the TOS parameter that VOIP uses and test the performance of the network in routing those packets.

The Type of Service octet in an IP datagram header enables packets with different TOS values to be routed differently.

Proxy URL Specifies the proxy URL for HTTP tests.

See “HTTP Tests” on page 32 for more information.

Alternate Packet Address Specifies an alternate source IP address instead of using the default network address of the device discovered in SPECTRUM.

Note: The Alternate Packet Address field is available for all Cisco test hosts that support IOS IP SLAs Agent.

Alternate Packet Port Specifies an alternate packet port instead of using the default packet port of the device discovered in SPECTRUM.

Note: The Alternate Packet Port field is available for all Cisco test hosts that support IOS IP SLAs Agent.

Filter Timeout Data Specifies whether the Performance tab the OneClick Component Detail panel displays all SPM data or a subset of data minus timeouts.

Default = True (filter timeout data)

HTTP Version Specifies the HTTP version (1.0 and 1.1) for HTTP tests.

Default = 1.1



Schedule a Test

The Schedule tab lets you schedule a test. Figure 3-12 shows an example configuration dialog box for a DHCP test.

Figure 3-12: Schedule Parameters - All Tests

Table 3-5 describes Schedule parameters.

Table 3-5: Schedule Parameters


Schedule State Enables and disables a test schedule.

Default = Disabled

Schedule time interval Specifies the interval between scheduled test runs.

Default = 900 seconds

Schedule Specifies one of the predefined schedules available from the drop-down list. See “Create a Schedule” on page 45 for information on creating additional schedules.

Default = 24/7

Note: Time zones for Schedule are local to the SpectroSERVER where the test host running the scheduled test is modeled.

Threshold Violation Interval Specifies an alternate test interval that can be used during a threshold violation period. Decreasing the interval during a period of high latency can provide more precise data.

Default = 300 seconds.

Important: When the Threshold Violation is exceeded, the test will not resume again until the Threshold Violation Interval is reached whether it is a lower or higher value than the Scheduled Time Interval.

Caution: Setting this value too low can create enough additional traffic and load on the router during a period of high latency to exacerbate the situation.

Configure SPM Tests


Create a Schedule

You can create schedules if the SPM-provided schedules do not meet your particular requirements. Schedules you create are not test-specific; they are available for all tests.

Procedure

To create a test schedule:

1. Click Create in the Schedule tab dialog box.

The Create Schedule dialog box (Figure 3-13) appears.

2. Configure schedule settings, and then click OK.

The new schedule appears in the Schedule drop-down list.

Figure 3-13: Create Schedule Dialog Box

Note: If you create a schedule with Recurrence set to None, the test will run once on the start date, and then the schedule will revert to the default schedule and the schedule will be disabled.

Specify Alarm Thresholds for a Test

The Threshold tab lets you configure alarm thresholds to monitor response time measurements on a specific link or path. Threshold parameters vary from test to test. When a threshold value is exceeded, SPECTRUM generates an event and/or an alarm based on the settings you specify. Figure 3-14 shows an example threshold configuration dialog box for a Jitter test.



Figure 3-14: Threshold Parameters - Jitter Test

Figure 3-6 describes Threshold option parameters. Threshold parameters vary depending on the type of test you are creating.

Table 3-6: Threshold Parameters


Active Thresholds Schedule Specifies one of the predefined schedules during which thresholds are in effect available from the drop-down list. You may want to use this feature if you want to measure test against thresholds only during certain times of the day. See “Create a Schedule” on page 45 for information on creating additional schedules.

Default = 24/7

Note: Time zones for Schedule are local to the SpectroSERVER where the test host running the scheduled test is modeled.

Threshold Events Asserted On Specifies the model from the drop-down list on which events are asserted.

Threshold Types Identifies threshold settings for the threshold types related to a test.

Status Enables and disables each threshold type for a test.

Event Specifies a response time threshold value (greater than 0) that if exceeded results in SPECTRUM generating an event.

Depending on the threshold type, a threshold value can be specified as one the following:

• A time interval in milliseconds (ms)

• A percentage (%) of packet errors encountered

Minor Alarm Specifies a response time threshold value (greater than 0) that if exceeded results in SPECTRUM generating a minor alarm.




Run Tests on an On-Demand Basis


Establish Baseline Data to Determine Valid Thresholds

If you are unsure of the threshold values to use for a test (too high or too low), establish baseline response times that you can use to determine appropriate thresholds.

Procedure

To determine valid thresholds for a test:

1. Schedule multiple test runs over the interval to which you want to apply thresholds to tests.

2. Analyze test result data to determine realistic performance thresholds. See Chapter 5, “Viewing SPM Information,” on page 63 for more information on test performance data.

3. Configure test thresholds based on the results of your analysis.

Run Tests on an On-Demand BasisYou can run tests manually on an on-demand basis if the following criteria are met:

• The test is not scheduled or is scheduled and the schedule is disabled.

• The test is enabled.

Major Alarm Specifies a response time threshold value (greater than 0) that if exceeded results in SPECTRUM generating a major alarm.




Critical Alarm Specifies a response time threshold value (greater than 0) that if exceeded results in SPECTRUM generating a critical alarm.




Threshold Cycles Specifies a value (greater than 0) that indicates the number of consecutive test cycles this test must run in violation of the threshold before SPECTRUM generates an event or alarm.

Clear Threshold Specifies a response time threshold value (greater than 0) that if not exceeded results in SPECTRUM clearing an event or alarm.




Clear Cycles Specifies a value (greater than 0) that indicates the number of consecutive test cycles this test must run in compliance with a threshold before SPECTRUM clears an event or alarm.

Table 3-6: Threshold Parameters (Continued)




• The test host for the test is activated. See “Activate and Deactivate Test Hosts” on page 48 for more information.

You would typically manually run tests for diagnostic purposes. For example, you would run an HTTP test to determine whether a Web server is responsive to requests, or you would run a Jitter test to determine the quality of VoIP transmission.

Procedure

To manually run a test:

1. Use SPM Searches to find the tests you want to run as described in Chapter 2, “Finding SPM Components with SPM Searches,” on page 23.


2. Select the tests you want to run, and then use one of the following methods (Figure 3-15) to run the test:

• Click the Run Tests icon.

• Right-click the test, and then select Run Test.

Figure 3-15: Run Tests

Information about the test appears in the Component Detail panel.

Activate and Deactivate Test Hosts

All test hosts are modeled in SPECTRUM in the active state. Tests can be configured on a test host in either the activated or deactivated stated. However, tests can only be run on activated test hosts.

Run Tests on an On-Demand Basis


Note: If the test host's associated device model is in maintenance mode, an error will be displayed and the test host will not be activated. When the device model is taken out of maintenance mode the test host will be activated if it was activated when the device model went into maintenance mode.

Procedures

To activate a test host:


The test hosts appear in the Contents panel. The State field indicates whether test hosts are Active or Inactive.

2. Select the inactive test host you want to activate, and then use one the following methods (Figure 3-16) to activate it:

• Click the Activate Test Host icon.

• Right click the test host, and then select Activate Test Host.

Figure 3-16: Activate Test Host

To deactivate a test host:


The test hosts appear in the Contents panel. The State field indicates whether test hosts are Active or Inactive.



2. Select the active test host you want to deactivate, and then use one the following methods (Figure 3-17) to deactivate it:

• Click the Deactivate Test Host icon.

• Right click the test host, and then select Deactivate Test Host.

Note: Any tests that are scheduled to run will stop running until the test host is re-activated.

Figure 3-17: Deactivate Test Host

Manage TestsYou can edit parameter settings for any test and delete any test, provided you have the administrative-user and read/write privileges to the test.

Important: Editing and deleting tests should be performed with caution by qualified personnel, especially in cases, for example, when SPM performance test results are being monitored by SLAs (service level agreements) or when tests are being run for infrastructure performance analysis purposes.

Edit a Test

You can edit all test parameter settings as required.

Note: When you edit a test, SPM must stop and restart the test after all changes have been completed. This can disrupt a test schedule. For example, if a test has a 60-minute interval between scheduled runs and it is edited 58 minutes after the last scheduled run, it will run 1 hour and 58 minutes after it has been restarted.

Manage Tests


Procedure

1. Use SPM Searches to find the tests you want to edit as described in Chapter 2, “Finding SPM Components with SPM Searches,” on page 23.


2. Use one of the following methods (Figure 3-18) to open the Edit Test dialog box:

• Click the Edit Test icon.

• Right click the test, and then select Edit Test.

Figure 3-18: Edit Test

3. Modify test parameters as required. See “Configure SPM Tests” on page 38 for details on configuration options.

Delete a Test

When you delete a test, you remove it permanently from SPECTRUM.

Procedure

1. Use SPM Searches to find the tests you want to delete as described in Chapter 2, “Finding SPM Components with SPM Searches,” on page 23.




2. Use one of the following methods (Figure 3-18) to delete the test:

• Click the Delete icon.

• Right click the test, and then select Delete.

The Confirm Delete window appears.

Figure 3-19: Delete Test

3. Click Yes in the Confirm Delete window. (To cancel the deletion, click No.)

53

Chapter 4: Working with Test Templates

Content


“Create Test Templates” on page 54

“Apply a Test Template to Test Hosts” on page 56

“Manage Test Templates” on page 60

OverviewA test template is a test configuration that you can apply to multiple test hosts in a single step to create tests on the test hosts. You configure and edit test templates the same way you do with tests. Where they are different is in their scope of application. When you create a test, you create it on a single test host. When you create a test template, however, you can apply it to multiple tests hosts in the following ways:

• Selectively apply a template to multiple test hosts that support the test specified by the template.

• Apply a template to any number of test hosts that support the tests specified by the templates and that are added to a Global Collection container.

The primary advantages of using a test template are listed as follows:

• You can implement automated bulk performance testing.

• All modifications to test template parameters are automatically applied to the tests on each test host to which the template is applied. For example, changing a threshold value in a template changes that threshold value for all tests derived from it.

• A test template allows you to specify that a test is either a test host or a destination type. A test host type specifies a variable test host but a constant destination. A destination type specifies a constant test host but variable destinations.



Create Test TemplatesSPM provides two ways to create performance test templates:

• Create a new test template from scratch

• Save a different version of an existing test template

Whichever method you use to create a test template, you configure it the same way as you would a test, as described in “Configure SPM Tests” on page 38. You also configure the following template-specific configuration parameters:

• Template Type — This option enables you to specify Test Host or Destination. (The Destination configuration is not available for DHCP and HTTP test templates.)

• Global Collections (Optional) — This option enables you to specify one or more Global Collection containers. OneClick automatically applies the test specified by the template to all test hosts added to it that support the test.

Create a New Test Template

This section describes how to create a new test template from scratch. You must use this method to create a test template if no others have been created.

Procedure

To create a test template:

1. Use SPM Searches to find test templates as described in Chapter 2, “Finding SPM Components with SPM Searches,” on page 23.

Test templates may or may not appear in the Contents panel, depending on whether any have been created.

2. Click the New icon and select a test type (Figure 4-1).

The New Test Template dialog box appears. It enables you to configure test template parameters and also specify one or more Global Collection containers to which you want to apply the template.

Figure 4-1: Create Test Template

Create Test Templates


3. Configure test template settings, and then click OK to save the new template.

Information about the new test template appears under the Information tab in the Component Detail panel.

Create a Different Version of an Existing Test Template

You can create a new test template from a copy of an another template.

Note: You cannot copy test templates between domains running different versions of SPECTRUM.

Procedure

To create a new test template from a copy of another template:


The test templates appear in the Contents panel. If no templates appear, create a new template as described in “Create a New Test Template” on page 54.

2. Select the test template you want to copy, and then use one of the following methods to open the Copy Test dialog box:

• Click the Copy icon (Figure 4-2).

• Right-click the test template you want to copy, and then select Copy Test Template.

Figure 4-2: Copy Test Template

The Copy Test Template dialog box appears. It includes configuration settings you can modify for your new template. Copied test templates are disabled by default, and “_COPY” is appended to the test name. You may want to rename the template, but it is not required.

3. Modify test template configuration settings, and then click OK to save the new template.

Information about the new test template appears under the Information tab in the Component Detail panel.



Apply a Test Template to Test HostsYou can selectively apply a test template to a group of test hosts that support the template test type, or you can automate the process by placing test hosts in a Global Collection container and applying a test template to the container. When a test template is applied to a Global Collection container, tests are automatically created for all test hosts that support the template test type added to the container.

See the Modeling Your IT Infrastructure Administrator Guide (5167) for complete information on creating and configuring Global Collection containers.

Selectively Apply a Test Template to One or More Test Hosts

Manually applying a test template to a selection of test hosts enables you to precisely specify only those test hosts you want to create tests for.

Procedure

To apply a test template to a test host:


The test templates appear in the Contents panel.

2. Select the test template you want to apply, and then use one of the following methods to apply the template:

• Click the Apply Test Template icon (Figure 4-3).

• Right-click the template, and then select Apply Test Template.

Figure 4-3: Apply Test Template

The Select Test Host dialog box (Figure 4-4) appears. It lists test hosts that support the template test type.

Apply a Test Template to Test Hosts


Figure 4-4: List of Test Hosts

3. Select one or more test hosts to which you want to apply the test template, and then click OK.

OneClick creates the test defined by the test template for the selected test hosts. The Contents panel lists tests created from a test host template type using the following format:

Template Name_IP Address

where

Template Name = the name of the template you applied to a test host.

IP Address = the test host IP address.

Apply a Test Template to a Global Collection Container

Applying test templates to Global Collection containers enables you to automate the process of creating tests of different types for multiple test hosts. For example, assume a Global Collection container includes a group of test hosts that only supports ICMP Ping tests, a group that only supports HTTP tests, and a group that supports both. Assume also that numerous tests hosts belonging to each group will be added to the container from time to time.

In this case, two different test templates could be applied to the container to create the tests for the test hosts included in it. One template would specify an ICMP Ping test and the other an HTTP test. ICMP Ping tests would be created for the test hosts that support ICMP Ping tests, and HTTP tests would be created for the test hosts that support HTTP tests.

This example, of course, understates the potential complexity of a “real-life” performance testing implementation, but it does illustrate the ease with which you can use test templates to set up tests on multiple test hosts as an alternative to setting them up on a test-by-test basis. See “Example Implementation Scenario” on page 58 for a more detailed example.

Procedure

To apply a test template to a Global Collection procedure:

1. In the Create Test Template, Copy Test Template, or Edit Test Template dialog box, click the Browse button adjacent to the Global Collection parameter.



A Select Collections dialog box (Figure 4-5) appears.

Figure 4-5: Select or Create Global Collections

2. Select the Global Collections to which you want to apply the template, and then click OK. If there are no Global Collections available or you would prefer to create a new Global Collection for your test hosts, click Create, configure the new Global Collection, and then proceed with the selection process.

Example Implementation Scenario

This section illustrates how test templates can be applied to a Global Collection to implement automated bulk performance testing between a central office location and branch office locations.

Scenario

• An organization’s central location provides domain name lookup and Web services to numerous remote branch locations that connect to the central location on an intermittent basis.

• Infrastructure administrators want to ensure that remote connections to the central location are maintained and that remote branch locations have continuous access to DNS and HTTP services provided by the central location.

• To determine whether service delivery from the main location to the remote locations remains viable, administrators decide to run Ping, DNS, and HTTP tests from remote location edge routers (that support the tests) on a regularly scheduled basis whenever they are brought online (connect to the central location edge router).

• Administrators create a Global Collection configured to include all remote location edge router models as they are brought online.

• Three test templates are applied to a Global Container:

- An ICMP Ping test template configured to create a Ping test on remote-location edge routers that tests connectivity to the central-location router.

Apply a Test Template to Test Hosts


- A DNS test template configured to create a DNS lookup test on remote-location edge routers that tests DNS lookup time from the DNS server from the central location.

- An HTTP test template configured to create an HTTP download test on remote-location edge routers that tests the round-trip time to download a Web page from the HTTP server from the central location.

Example

Figure 4-6 illustrates the example scenario.

Figure 4-6: Test Template Scenario

DNS Server

HTTP Server

RTR

Central Office

Branch Offices

RTR

RTRRTR RTR

Global Collection

Destination

Source Source Source Source

DNS Test Template

HTTP Test Template

Ping Test Template

NY LA Chi Bos

DNS test from each routerHTTP test from each router

Ping test from each router

Applied to collection



Manage Test TemplatesWhen you edit a template, all the tests created from the template are updated with the modified settings. When you remove the association between a template and a Global Collection or delete a template, all tests created from the template are deleted.

Important: Editing and deleting test templates should be performed with caution by qualified personnel, especially in cases when SPM performance test results are being monitored by SLAs (service level agreements) modeled in SPECTRUM or when tests are being run for infrastructure performance analysis purposes.

Edit a Test Template

You can edit all test template parameter settings as required. Changes apply to all tests created by the template. You can also remove the association between a template and a Global Collection when you edit a template.

Procedure

To edit test template settings:



2. Select the test template you want to edit, and then use one of the following methods to edit the template:

• Click the Edit icon (Figure 4-7).

• Right-click the template, and then select Edit Test Template.

Figure 4-7: Edit Test Template

The Edit Test Template dialog box appears.

3. Modify the template’s settings, and then click OK to apply the changes to the template and all tests created from it.

Manage Test Templates


Remove the Association Between a Template and a Global Collection

You can remove the association between a template and a Global Collection by deleting the value in the Global Collections parameter in the Edit Test Template dialog box. When you remove the association, all tests on the test hosts in the collection are deleted.

Delete a Test Template

You can delete all test templates as required. When you delete a template, you also delete all tests created from it.

To delete a template:



2. Select the test template you want to delete, and then use one of the following methods to delete the template:

• Click the Delete icon (Figure 4-8).

• Right-click the template, and then select Delete Test Template.

Figure 4-8: Delete Test Template

A confirmation window prompts you to proceed with or dismiss the deletion (Figure 4-9).

Figure 4-9: Template Deletion Confirmation

Click Yes to delete the test template(s), or click No to dismiss the operation and retain the template(s).

63

Chapter 5: Viewing SPM Information

Content


“Test Host Information” on page 63

“Test Information” on page 65

“SPM Alarms and Events” on page 70

OverviewOneClick Console provides views of test hosts, test templates, tests, and test results derived from SPM searches as described in Chapter 2, “Finding SPM Components with SPM Searches,” on page 23. It also provides detailed information about events and alarms for SPM components. See OneClick documentation for more information about working with OneClick Console views (refreshing views and docking and undocking panels for example) and customizing views (setting table column preferences) to display only the information types you want to view (setting table column preferences).

Tip: Click the Refresh button in every OneClick Console view where it is available to ensure you are viewing up-to-date information.

Test Host InformationOneClick Console displays summary and detailed information about test hosts modeled in SPECTRUM and enables you to perform operations on tests for test hosts. Figure 5-1 shows an example view of a test host located by a “Test Hosts By IP Address” search.



Figure 5-1: Test Host View

The Contents panel table displays information about the selected test host model, the landscape where it is modeled, its state (activated or deactivated), and the test types it supports among the various test types supported by SPM. The Contents panel also provides command icons for creating tests for the test host, for discovering tests configured on the test host, and for activating and deactivating the test host.

Test Host Information in the Component Detail View

The Component Detail panel provides detailed information about a selected test host. The Information tab of the Component Detail panel includes two categories of information about the test host:

• Test Host Details

• Test List

See “SPM Alarms and Events” on page 70 for information about accessing information about alarms and events for SPM components.

Test Host Details

The Test Host Details view provides all the information about the test host, which may or may not be displayed in the customizable Contents panel table, and enables you to set the test host model security string.

Test Information


Test List

Like the Contents panel table, the Test List table displays information about tests for the selected test host. It also provides test command icons for running tests, stopping tests, managing tests, and invoking a Component Detail views for tests.

Test InformationOneClick Console displays summary and detailed information about tests modeled in SPECTRUM and enables you to perform operations on tests. Figure 5-2 shows an example view of tests located by an “All Tests” search.

Figure 5-2: Test Information

The Contents panel table displays information about the selected test model, the landscape where it is modeled, the IP addresses of the test source, test destination, and test host for the test. It also indicates whether the test is scheduled, running, or stopped, the last time the test was run and the resulting status of the test (did or did not violate a threshold), and the test discovery state. The Contents panel also provides command icons for running, stopping, and managing tests.



Test Information in the Component Detail Panel

The Information tab in the Component Detail panel provides detailed information about a selected test:

• Details — Provides information about test configuration settings, including scheduling and test threshold settings.

• Last Run Results — Provides information about the most recent test run, including latency and packet loss values.

• Threshold Results — Provides information about a threshold violations (event, minor, major, critical) resulting from the test.

Note: Regarding the sample count and the % of Threshold values, RTTMON may occasionally perform more than the sample count repetitions specified for an SPM Test. SPM takes this into account, and properly calculates the average, maximum, and minimum results for latency and packet Loss. Because of this, the value for percentage of packet loss can be other than a multiple of (1 / sample count) * 100. For example: If you set sample count to 5, normally the percentage of packet loss will be a value of 0%, 20%, 40%,... 100%. If the agent performs more than 5 repetitions, you may see 0%, 16.66%, 33.33%... 100%.

Test Performance Information in the Component Detail Panel

The Performance tab in the Component Detail panel shows graphical representations of test results. Figure 5-3 shows an example test performance graph.

Important: The Archive Manager for the test’s landscape must be running or SPM to display performance test results.

Figure 5-3: Test Performance Graph

Test Information


Specify the Interval

You can specify the following time intervals for which you want to display performance results:

The All Results option retrieves all result data stored in the SPECTRUM Distributed Data Manager (DDM) database, up to a maximum of 365 days. By default, the DDM stores up to 45 days worth of data. See the Database Management (2601) documentation for more information.

Caution: Retrieving large numbers of result events may negatively impact performance.

Procedure

Select an interval from the drop-down list.

Specify the Test Result Type

You can specify a graph that displays performance latency or packet loss statistics for the selected test.

Procedure

Select either Latency of Packet Loss from the drop-down list.

View Test Data

You can view data from a particular data point in a graph.

Procedure

Position your mouse pointer over the end of a data point line in the graph to display a descriptive label (including date, time, and value) for that data point.

You can also view additional test data (averages, high and low values) in tabular form under the graph.

Adjust an Axis Dimension

You can adjust the dimensions of the X and Y axes as necessary to meet your viewing requirements. For example, you can adjust the X axis to display latency outliers not visible from the default view.

Procedure

Select a zoom percentage from the drop-down list for the X or Y axis, or enter a value.

Note: 100% is the minimum allowable zoom percentage.

• 1 Hr • 3 Hr

• 6 Hr • 12 Hr

• 1 Day • 1 Week

• 4 Weeks • All Results



About the Effect of a Test’s Filter Timeout Data Setting on a Performance Graph

When you configure a test, you can specify that data generated as a result of a test timeout is filtered out of test results. The setting’s default value is True. It will cause gaps in the graph where timeouts or, possibly, test failures have occurred, and you will be unable to discern them. Examples of test failures include lost contact to device, device in maintenance mode, or device failure.

A setting of False, however, will cause the following effects:

• Skewed performance graph auto-scaling — Timeout values may be so far greater than the response time values that exact response time values on the performance graph may be difficult if not impossible to discern.

• Skewed average calculation — Timeout values may be so far greater than response time values that they cause inaccurate average calculations.

• Skewed data while using data export — Timeout values will be prevalent in the exported data, so depending on your post-processing mechanisms, this could produce undesirable results.

Figure 5-4 illustrates some of these effects.

Test Information


Figure 5-4: Filter Timeout Data Results Comparison

The timeout value is of sucha far greater scale . . .

. . . that these valuescannot be discernedon the graph.

Gap may represent timeoutsor test failures.



SPM Alarms and EventsYou can view alarms for SPM components from multiple points in OneClick Console. For comprehensive information about viewing alarms, configuring alarm filters, and performing other activities with alarms in OneClick Console, refer to the OneClick Console User Guide (5130).

Procedures

To view events and alarms for SPM components from the Locater:

1. List the components for which you want to view event and alarm information. SeeChapter 2, “Finding SPM Components with SPM Searches,” on page 23 for more information.

2. In the Contents panel, select a component.

3. In the Component Detail panel, click the Alarms or Events tab to view information.

To view events and alarms for SPM components from the Explorer:

1. Click the Alarms tab in the Contents panel.

2. Enter filtering text (RTM_Test for example) to display the component or group of components.

3. In the Component Detail panel, click the Alarm Details or Events tab to view information.

Figure 5-5 shows an example alarm details view.

Figure 5-5: SPM Test Alarm Details

71

Chapter 6: Generating Reports on Test Data

Content


“SPM Reports from SRM” on page 71

“SPM Reports from SRG” on page 75

OverviewSPECTRUM provides two resources you can use to generate reports on performance testing results:

• SPECTRUM Report Manager (SRM) — Lets you generate summarized and detailed performance test, or round trip time (RTT) test, results in a variety of text and graphical formats on an on-demand or scheduled basis.

• SPECTRUM Report Gateway (SRG) — Lets you generate graphical reports on time-series performance test data.

SPM Reports from SRMSee the Report Manager User Guide (5158) for detailed information on SRM features referenced but not fully described in this section.

SPM report options are included under the Response Time report pack in SRM. SRM provides numerous report content, format, and report organization options. This means you can generate reports with the appropriate type and scope of information for different audiences in your organization interested in performance testing results.

Report Management Options

SRM provides you with multiple options for generating and managing your RTT reports:

• Generate reports on demand. Use this option to generate the most recent RTT test results obtainable.

• Schedule RTT test report generation on a one-time or periodic basis.



• Specify how long you want SRM to retain scheduled RTT test reports or how many reports to retain.

• Specify email recipients for scheduled RTT test reports.

• Schedule RTT test reports for other SRM users.

• Save RTT test report configurations as favorites that you can run repeatedly without having to reconfigure the report.

• Publish RTT test reports in PDF, text, and spreadsheet formats. Use the documents for briefings and presentations on network performance issues.

How You Generate Performance Reports with SRM

You can generate performance reports on demand or schedule reports. This section provides an overview of how you perform these tasks.

Generating RTT reports involves the following steps:

1. Select the type of test you want to generate.

Figure 6-1 shows the SPM report options.

Figure 6-1: Response Time Test Report Pack

2. Configure the report.

Figure 6-2 shows an example portion of a configuration page for an ICMP Ping report.

SPM Reports from SRM


Figure 6-2: Example Response Time Report

3. Generate (view) the report, save the report configuration as a favorite, or schedule the report.

Figure 6-3 shows report command buttons on the configuration page.



Figure 6-3: Generate, Save, or Schedule the Report

4. View and manage report results. At this point you can also schedule the report and save the report as a favorite as you could before you generated the report, you can page through the report and search for text, and you can also publish the report in multiple industry-standard formats and print the report.

Figure 6-4 shows a portion of the report results.

SPM Reports from SRG


Figure 6-4: Report Results

SPM Reports from SRGYou can export SPM result data compiled over an extended period of time using the SPM result logger. SPM result logger output files include a model handle, time stamp, and a list of test-specific result statistics on each line. Once SPM logging is enabled, SPM produces text files containing SPM result data in SSLogger format that can then be used by the SRG reporting utility. All result files are created and saved in an output directory you create. New log files are created after an interval you specify.

• See the OneClick Administration Guide (5166) for information on configuring SPM data export parameters.

• See the Report Gateway User Guide (5141) for information on graphical reports.



Data Logging Event Codes

Table 6-1 lists SPM data logging event codes.

SPM Result Events

For SPM result events, the data above is followed by statistical data particular to the RTM_Test. The event code dictates which of the statistics are relevant.

Note: Irrelevant statistics for a given test type (for example, Jitter statistics for a ping test) are reported as 0.

The remaining 12 reported statistics in a logged event correspond to (in order):

• Latency

• Packet loss

• HTTP response time

• DNS resolution time

• TCP connect time

• HTTP download time

• Jitter response time

• Jitter source to destination time

• Jitter destination to source time

• Jitter MIA

• Jitter late arrival

• Jitter busies

Table 6-1: SPM Data Logging Event Codes

Event Code Event Contains Statistics For...

0x04560000 SPM Result Event Latency and packet loss

(Except for DHCP tests which do not contain data for packet loss.)

0x0456002e SPM Result Event (HTTP) HTTP response time, DNS resolution time,TCP connect time, and HTTP download time

0x04560010 SPM Result Event (Jitter) Jitter response time, Jitter source to destination time, Jitter destination to source time, Jitter MIA, Jitter late arrival, and Jitter busies

0x0456003e SPM Result Event (Traceroute) Latency

SPM Reports from SRG


SPM Data Export Sample

The sample below illustrates the structure of logged SPM test result data:

0x830201d,6PM-7AM_6.6.0.2,1054176719,0x4560000,1,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x8302010,Jitter_6.6.0.2,1054176724,0x4560010,0,0.0,0,0,0,0,5,0.0,0.0,0.0,0.0,0.00x8302012,FTP_6.6.0.2,1054176730,0x4560000,843,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x8302017,TCP_6.6.0.2,1054176748,0x4560000,1,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x830201b,24x7_6.6.0.2,1054176767,0x4560000,1,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x6a00f8a,TCP_6.6.0.0,1054176941,0x4560000,6,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x6c009de,Traceroute_6.6.0.1,1054176872,0x456003e,40,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x6c009d6,FTP_6.6.0.1,1054176872,0x4560000,858,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x6c009e0,TCP_6.6.0.1,1054176872,0x4560000,12,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x8302011,HTTP_6.6.0.2,1054176837,0x456002e,0,0.0,753,5,32,716,0,0.0,0.0,0.0,0.0,0.00x830201f,6-11M-F_6.6.0.2,1054176870,0x4560000,1,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x6c009e6,24x7_6.6.0.1,1054176927,0x4560000,5,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x6c009e8,6PM-7AM_6.6.0.1,1054176937,0x4560000,5,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x6c009d5,HTTP_6.6.0.1,1054176939,0x456002e,0,0.0,19,0,7,12,0,0.0,0.0,0.0,0.0,0.00x6a00f8b,ICMP_6.6.0.0,1054177035,0x4560000,1,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x6c009df,UDP_6.6.0.1,1054176943,0x4560000,3,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x8302019,UDP_6.6.0.2,1054176906,0x4560000,7,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x6c009eb,6-11M-F_6.6.0.1,1054176960,0x4560000,8,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.00x6c009dd,ICMP_6.6.0.1,1054176978,0x4560000,4,0.0,0,0,0,0,0,0.0,0.0,0.0,0.0,0.0

SPM Test Modification Event

SPM test modification events (event code 0x0456000a) contain the following statistical data (in addition to the common data described under “Table 6-1 lists SPM data logging event codes.” on page 76):

• Test name • Source address

• Destination address • Test interval

• Packet size • Sample count

79

Chapter 7: Creating and Managing RTM Tests with Command Line Interface (CLI)

Content


“Create Tests in CLI” on page 80

“Run Tests in CLI” on page 81

“Edit Tests in CLI” on page 81

“Get Test Results in CLI” on page 82

“Test Parameters Used in CLI” on page 82

“Test Action Codes” on page 99

“Test Status and Test Results Parameters” on page 99

OverviewResponse time tests are represented in SPECTRUM as models of model type RTM_Test. You can use SPECTRUM’s CLI to create, run, and edit response time tests and get test results as an alternative method to using the SPM user interface in OneClick (see Chapter 3, “Working with Performance Tests,” on page 29). You can issue test management commands from the CLI command line, or you can embed CLI commands in scripts, which you can run on an ad hoc or scheduled basis.

Important: Before you attempt to create and manage tests with CLI, you should understand Service Performance Manager concepts, CLI commands and command syntax, and SPECTRUM modeling concepts.

See the Command Line Interface (0664) guide for more information about the following CLI commands at your disposal for creating and managing tests:

• ack alarm • destroy • setjump

• connect • disconnect • show

• create • jump • stopShd

• current • seek • update



Note: CLI command references and examples in this chapter use the typographical conventions described in the Command Line Interface (0664) guide

Create Tests in CLIYou can create any of the response time test models supported by SPECTRUM using the CLI create command. See “Required Parameters for Creating Tests” on page 82 for complete information about required test attributes for all tests and specific tests.

The following example script shows how to create a regularly scheduled Ping test. It enables a latency threshold, a latency value that if exceeded triggers a minor alarm, and a latency value that if not exceeded triggers an alarm clear.

#!/bin/ksh

cd $SPECROOT/vnmsh

connect./create model mth=0x4560000 \ attr=0x1006e,val="Ping_Test_1" \ # Test Name

attr=0x4560005,val=0 \ # Test Type is ICMP_Ping

attr=0x4560006,val=10.253.9.8 \ # TestHost address

attr=0x456001f,val=10.253.9.12 \ # Destination IP

attr=0x4560022,val=1 \ # Schedule is enabled

attr=0x4560014,val=600 \ # Test interval is 10 minutes

attr=0x4560035,val=1 \ # Latency Threshold is enabled

attr=0x456009b,val=100 \ # Latency Minor Threshold Set value

attr=0x4560017,val=100 \ # Latency Threshold Clear value

attr=0x4560027,val=2 # Clear Cycles

The following example script shows how to create an HTTP test. Note the formatting required for URL values.

#!/bin/ksh

cd $SPECROOT/vnmsh

connect./create model mth=0x4560000 \ attr=0x1006e,val="Http_Test_1" \ # Test Name

attr=0x4560005,val=5 \ # Test Type is HTTP

attr=0x4560006,val=10.253.9.8 \ # TestHost address

attr=0x456001f,val="http:\/\/www.ca.com\/about.htm" # Destination URL

attr=0x456008d,val="http:\/\/proxyServer" # Proxy URL

attr=0x4560022,val=1 \ # Schedule is enabled

Run Tests in CLI


Run Tests in CLIYou can run a response time test using the CLI update command by specifying the SPM_RUN_TEST action code (0x4560009) and the test model handle. See “Test Action Codes” on page 99 for more information. The following example script shows how to run a single test. You can run multiple tests by specifying multiple tests in the script.

#!/bin/ksh

# this will run a test with the given model handle.

cd $SPECROOT/vnsmh

connect./update action=0x4560009 mh=<testMH>

Edit Tests in CLIYou can edit a response time test using the CLI update command to change test parameter values by specifying new parameter values and issuing an update test action code (0x4560008). The following example script shows how to modify a tests’s schedule interval and test timeout values.

#!/bin/ksh

# change the schedule interval from 15 minutes to 30 minutes (1800 seconds)

# change the test timeout from 5000 ms to 1000 ms

# have the test not filter its timeout data

cd $SPECROOT/vnmsh

connect./update mh=<testMH> attr=0x4560014,val=1800./update mh=<testMH> attr=0x4560025,val=1000./update mh=<testMH> attr=0x45600d6,val=FALSE./update action=0x4560008 mh=$i



Get Test Results in CLIYou can get various test status indications and test results using the CLI show command along with the parameters that return the values you want.

The following example script shows how to get test status and test results. See “Test Status and Test Results Parameters” on page 99.

#!/bin/ksh

# obtain the latestResult status and latency/packet loss values for a given test

cd $SPECROOT/vnmsh

connect./show attributes -e attr=0x4560004 attr=0x4560015 attr=0x456007d mh=<testMH>

Test Parameters Used in CLIThis section lists and describes parameters for creating and scheduling tests and specifying test thresholds. (“Configure SPM Tests” on page 38 describes how to configure RTM_Test model parameters using the Service Performance Manager user interface in OneClick.)

Required Parameters for Creating Tests

These parameters are required for creating response time test models.

Attribute Attribute ID Default Value Description/Usage

Model_Name 0x1006e None Name of the test. Only one test per host can exist with the same name. Duplicate test names are appended with “_COPY”

Test_Type 0x4560005 None Specifies the type of test to create.

0=ICMP_Ping

1=UDP_ECHO

2=TRACEROUTE

3=TCP_CONNECT

4=DNS_LOOKUP

5=HTTP

6=POP3

7=DHCP

8=FTP

9=SMTP

10=Jitter

Once a test is created, this value cannot be changed. If it is changed, it will be reset when the update takes place.

Test Parameters Used in CLI


Required Parameters for Scheduling Tests

Use these parameters to specify test timeout and test schedule management values. (“Schedule a Test” on page 44 describes how to configure test schedule parameters using the Service Performance Manager user interface in OneClick.)

Test_Host_Address 0x4560006 None The IP Address of a test host. This must match the network address of the associated device model.

Once a test is created, this cannot be changed. If it is changed, it will be reset when the update takes place.

Dest_IP_Address 0x456001f None The destination IP address. Used for ICMP_Ping, TRACEROUTE, UDP, TCP, DNS, SMTP, and Jitter tests.

Dest_URL 0x456000f None The destination URL required for HTTP tests. Enclose the URL between double quotes (“ ”), and use escape slashes ( \ ) before forward slashes ( / ). See “Create Tests in CLI” on page 80 for a format example.

Dest_Host_Name 0x456000a None The destination test host name required for DNS tests as the lookup name, and for FTP/POP3 tests as the address on which to perform the transaction.

Dest_Port_Number 0x4560011 None Must be non-zero for TCP/UDP/Jitter tests.

Dest_User_Name 0x456000b None The destination user name. Required for FTP/POP3 tests. Optional for HTTP tests.

Dest_File_Name 0x456000d None The destination file name. Required for FTP tests.

Dest_Password 0x456000e None The destination password. Required for FTP/POP3 tests. Optional for HTTP tests.


Test_Timeout 0x4560025 5000 The number of milliseconds before a test connection to an unresponsive test host times out.

Sched_Frequency 0x4560014 900 Interval in seconds between scheduled test runs.

Schdule_State 0x4560000 0 Specifies whether or not the test schedule is in effect.

0 = DISABLED

1 = ENABLED

Thresh_Frequency 0x456001a 300 Interval in seconds after which a test runs while in a threshold condition.




Optional Parameters

Use these parameters to specify various, optional test parameters. (“Configure Advanced Parameters” on page 42 describes how to specify these parameters using the Service Performance Manager user interface in OneClick.)

TestSchedule_Type 0x456008b 5 Pre-configured test schedules provided with the SPM application.

0 = 7x24

1 = 7A-6P

2 = 6P-7A

3 = MF 8A-8P

4 = MF 6A-11P

Use as an alternative to ACTIVE_SCHED_MH.

Note: Not specifying a value results in a 7x24 schedule

ACTIVE_SCHED_MH 0x456008f None Model handle of a test schedule model.

Use as an alternative to TestSchedule_Type.

Note: Not specifying a value results in a 7x24 schedule.


FILTER_TIMEOUT_DATA 0x45600d6 TRUE Specifies whether the RTM_Test will generate result events for timeouts.

Sample_Count 0x4560068 5 Specifies the number of times during a test run that the test is performed.

Packet_Size 0x4560067 64 Specifies the value (expressed in octets) that limits the size of the packets used in the test.

State 0x4560003 1 Specifies whether or not the test is enabled.

1 = ENABLED

2 = DISABLED

Thresh_Model 0x4560024 0 Specifies the test entity on which threshold events are asserted.

0 = TEST

1 = SOURCE

2 = DESTINATION

3 = HOST




ThreshSchedule_Type 0x4560090 5 Pre-configured threshold schedules provided with the SPM application. Specifies periods during which you want to see SPM threshold alarms.

0 = 7x24

1 = 7A-6P

2 = 6P-7A

3 = MF 8A-8P

4 = MF 6A-11P


THRESH_SCHED_MH 0x4560090 None Model Handle of a Schedule model. Used with the ThreshSchedule_Type parameter.


Source_IP_Address 0x4560008 None For use by Mid_Path/Extended_Path Ping tests only.

Test_Host_Position 0x4560030 0 Specifies test host location.

0 = END_POINT

1 = MID_PATH

2 = EXTENDED_PATH

Proxy_URL 0x456008d None Used by HTTP tests only. Specifies the URL for the test. Enclose the URL between double quotes (“ ”), and use escape slashes ( \ ) before forward slashes ( / ). See “Create Tests in CLI” on page 80 for a format example.

TypeOfService 0x4560099 None Cisco hosts only. Specifies the Type of Service (TOS) octet in an IP datagram header that enables packets with different TOS values to be routed differently. Must be less than 256.

EchoAdminSourceAddress 0x45600b0 None Cisco hosts only. Specifies the IP address or host name of the test when it is not the test host. See “About the Test Host Location Parameter” on page 40 for more information.

EchoAdminSourcePort 0x45600b1 None Cisco hosts only. Specifies the port number used by the tested application (Jitter, TCP, UDP only). It must be less than 65536.

CodecType 0x45600e7 0 Specifies the type of codec used by the router to perform audio compression and decompression. This is important for correct calculation of the Mean Option Score (MOS).0 = NONE

1 = G.711 U-law

2 = G.711 A-law

3 = G.729A




Threshold Type Parameters

You can specify threshold management parameters for all test types. Thresholds are expressed either in terms of response, or transaction time, or packet error or loss, depending on the type of test for which the threshold is specified.

Latency Threshold Parameters


Latency_Thresh_State 0x4560035 0 Specifies whether the latency threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Latency_MinorSetValue 0x456009b 500 Specifies the latency threshold period in milliseconds that must be exceeded before a minor alarm is generated.

Latency_MajorSetValue 0x456009c None Specifies the latency threshold period in milliseconds that must be exceeded before a major alarm is generated.

Latency_CriticalSetValue 0x456009d None Specifies the latency threshold period in milliseconds that must be exceeded before a critical alarm is generated.

Thresh_Set_Value 0x4560016 None Specifies the latency threshold period in milliseconds that must be exceeded before an event is generated.

Thresh_Clear_Value 0x4560017 500 Specifies the latency threshold period in milliseconds the test must not exceed before an event is cleared.

Thresh_Set_Delay 0x4560026 1 Specifies the number of consecutive cycles the test must run in violation of the threshold before an event or alarm is generated.

Thresh_Clear_Delay 0x4560027 1 Specifies the number of consecutive cycles the test must run without exceeding the threshold before an event or alarm is cleared.



Packet Loss Threshold Parameters

HTTP DNS Threshold Parameters


PL_Thresh_State 0x4560034 0 Specifies whether the packet loss threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

PacketLoss_MinorSetValue 0x456009e 20% Specifies the packets lost percentage that must be exceeded before a minor alarm is generated.

PacketLoss_MajorSetValue 0x456009f None Specifies the packets lost percentage that must be exceeded before a major alarm is generated.

PacketLoss_CriticalSetValue 0x45600a0 None Specifies the packets lost percentage that must be exceeded before a critical alarm is generated.

PL_Set_Value 0x456002c None Specifies the packets lost percentage that must be exceeded before an event is generated.

PL_Clear_Value 0x456002e 20% Specifies the packets lost percentage that must not be exceeded before a minor alarm is generated.

PL_Set_Delay 0x456002d 1 Specifies the number of consecutive cycles the test must run in violation of the threshold before an event or alarm is generated.

PL_Clear_Delay 0x456002f 1 Specifies the number of consecutive cycles the test must run without exceeding the threshold before an event or alarm is cleared.


Statistic_1_Thresh_State 0x4560036 0 Specifies whether the HTTP DNS threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Statistic_1_MinorSetValue 0x45600a1 500 Specifies the resolution time threshold period in milliseconds that must be exceeded before a minor alarm is generated.

Statistic_1_MajorSetValue 0x45600a2 None Specifies the resolution time threshold period in milliseconds that must be exceeded before a major alarm is generated.

Statistic_1_CriticalSetValue 0x45600a3 None Specifies the resolution time threshold period in milliseconds that must be exceeded before a critical alarm is generated.



HTTP TCP Threshold Parameters

Statistic_1_Set_Value 0x4560039 None Specifies the resolution time threshold period in milliseconds that must be exceeded before an event is generated.

Statistic_1_Clear_Value 0x456003a 500 Specifies the resolution time threshold the test must not exceed before an event is cleared.

Statistic_1_Set_Delay 0x456003b 1 Specifies the number of consecutive cycles the test must run in violation of the threshold before an event or alarm is generated.

Statistic_1_Clear_Delay 0x456003c 1 Specifies the number of consecutive cycles the test must run without exceeding the threshold before an event or alarm is cleared.


Statistic_2_Thresh_State 0x456003e 0 Specifies whether the HTTP TCP threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Statistic_2_MinorSetValue 0x45600a4 500 Specifies the connection time threshold period in milliseconds that must be exceeded before a minor alarm is generated.

Statistic_2_MajorSetValue 0x45600a5 None Specifies the connection time threshold period in milliseconds that must be exceeded before a major alarm is generated.

Statistic_2_CriticalSetValue 0x45600a6 None Specifies the connection time threshold period in milliseconds that must be exceeded before a critical alarm is generated.

Statistic_2_Set_Value 0x4560041 None Specifies the connection time threshold period in milliseconds that must be exceeded before an event is generated.

Statistic_2_Clear_Value 0x4560042 500 Specifies the connection time threshold that must not exceed before an event is cleared.




HTTP Download Threshold Parameters

Statistic_2_Set_Delay 0x4560043 1 Specifies the number of consecutive cycles the test must run in violation of the threshold before an event or alarm is generated.

Statistic_2_Clear_Delay 0x4560044 1 Specifies the number of consecutive cycles the test must run without exceeding the threshold before an event or alarm is cleared.


Statistic_3_Thresh_State 0x4560046 None Specifies whether the HTTP download threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Statistic_3_MinorSetValue 0x45600a7 500 Specifies the download time threshold period in milliseconds that must be exceeded before a minor alarm is generated.

Statistic_3_MajorSetValue 0x45600a8 None Specifies the download time threshold period in milliseconds that must be exceeded before a major alarm is generated.

Statistic_3_CriticalSetValue 0x45600a9 None Specifies the download time threshold period in milliseconds that must be exceeded before a critical alarm is generated.

Statistic_3_Set_Value 0x4560049 None Specifies the download time threshold period in milliseconds that must be exceeded before an event is generated.

Statistic_3_Clear_Value 0x456004a 500 Specifies the download time latency threshold the test must not exceed before an event is cleared.





Jitter Source to Destination Packet Loss Threshold



Statistic_1_Thresh_State 0x4560036 0 Specifies whether the Jitter source to destination packet loss threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Statistic_1_MinorSetValue 0x45600a1 20% Specifies the percentage of packets that must be lost before a minor alarm is generated.

Statistic_1_MajorSetValue 0x45600a2 None Specifies the percentage of packets that must be lost before a major alarm is generated.

Statistic_1_CriticalSetValue 0x45600a3 None Specifies the percentage of packets that must be lost before a critical alarm is generated.

Statistic_1_Set_Value 0x4560039 None Specifies the percentage of packets that must be lost before an event is generated.

Statistic_1_Clear_Value 0x456003a 20% Specifies the percentage of packets lost that must not be exceeded before an event or alarm is cleared.

Statistic_1_Set_Delay 0x456003b 1 Specifies the number of consecutive cycles the test must run in violation of a threshold before an event or alarm is generated.





Jitter Destination to Source Packet Loss Threshold

Jitter MIA Threshold Parameters


Statistic_2_Thresh_State 0x456003e 0 Specifies whether the Jitter destination to source packet loss threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Statistic_2_MinorSetValue 0x45600a4 20% Specifies the packets lost percentage that must be exceeded before a minor alarm is generated.

Statistic_2_MajorSetValue 0x45600a5 None Specifies the packets lost percentage that must be exceeded before a major alarm is generated.

Statistic_2_CriticalSetValue 0x45600a6 None Specifies the packets lost percentage that must be exceeded before a critical alarm is generated.

Statistic_2_Set_Value 0x4560041 None Specifies the packets lost percentage that must be exceeded before an event is generated.

Statistic_2_Clear_Value 0x4560042 20% Specifies the packets lost percentage that must not be exceeded before a minor alarm is generated.

Statistic_2_Set_Delay 0x4560043 1 Specifies the number of consecutive cycles the test must run in violation of the threshold before an event or alarm is generated.



Statistic_3_Thresh_State 0x4560046 0 Specifies whether the Jitter MIA threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED



Jitter Late Arrival Threshold Parameters

Statistic_3_MinorSetValue 0x45600a7 20% Specifies the percentage of missing in action packets that must be exceeded before a minor alarm is generated.

Statistic_3_MajorSetValue 0x45600a8 None Specifies the percentage of missing in action packets that must be exceeded before a major alarm is generated.

Statistic_3_CriticalSetValue 0x45600a9 None Specifies the percentage of missing in action packets that must be exceeded before a critical alarm is generated.

Statistic_3_Set_Value 0x4560049 None Specifies the percentage of missing in action packets that must be exceeded before an event is generated.

Statistic_3_Clear_Value 0x456004a 20% Specifies the percentage of missing in action packets that must not be exceeded before an event or alarm is cleared.

Statistic_3_Set_Delay 0x456004b 1 Specifies the number of consecutive cycles the test must exceed the threshold before an event or alarm is generated.

Statistic_3_Clear_Delay 0x456004c 1 Specifies the number of consecutive cycles the test must not exceed the threshold before an event or alarm is generated.


Statistic_4_Thresh_State 0x456004e 0 Specifies whether the Jitter late arrival threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Statistic_4_MinorSetValue 0x45600aa None Specifies the percentage of late packets that must be exceeded before a minor alarm is generated.




Jitter Busies Threshold Parameters

Statistic_4_MajorSetValue 0x45600ab 20% Specifies the percentage of late packets that must be exceeded before a major alarm is generated.

Statistic_4_CriticalSetValue 0x45600ac None Specifies the percentage of late packets that must be exceeded before a critical alarm is generated.

Statistic_4_Set_Value 0x4560051 None Specifies the percentage of late packets that must be exceeded before an event is generated.

Statistic_4_Clear_Value 0x4560052 None Specifies the percentage of late packets that must not be exceeded before an event or alarm is cleared.

Statistic_4_Set_Delay 0x4560053 20% Specifies the number of consecutive cycles the test must run in violation of the threshold before an event or alarm is generated.



Statistic_5_Thresh_State 0x4560056 0 Specifies whether the Jitter busies threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED




Statistic_5_MinorSetValue 0x45600ad 20 Specifies the percentage of busy failures that must be exceeded before a minor alarm is generated.

Statistic_5_MajorSetValue 0x45600ae None Specifies the percentage of busy failures that must be exceeded before a major alarm is generated.

Statistic_5_CriticalSetValue 0x45600af None Specifies the percentage of busy failures that must be exceeded before a critical alarm is generated.

Statistic_5_Set_Value 0x4560059 None Specifies the percentage of busy failures that must be exceeded before an event is generated.

Statistic_5_Clear_Value 0x456005a 20 Specifies the percentage of busy failures that must not be exceeded before an event is generated.






Jitter Positive Source to Destination Threshold Parameters


Statistic_6_Thresh_State 0x45600ba 0 Specifies whether the Jitter positive source to destination threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Statistic_6_MinorSetValue 0x45600b4 25 Specifies the percentage of positive Jitter that must be exceeded before a minor alarm is generated.

Statistic_6_MajorSetValue 0x45600b5 None Specifies the percentage of positive Jitter that must be exceeded before a major alarm is generated.

Statistic_6_CriticalSetValue 0x45600b6 None Specifies the percentage of positive Jitter that must be exceeded before a critical alarm is generated.

Statistic_6_Set_Value 0x45600b3 None Specifies the percentage of positive Jitter that must be exceeded before an event is generated.

Statistic_6_Clear_Value 0x45600b7 25 Specifies the percentage of positive Jitter that must not be exceeded before an event is generated.

Statistic_6_Set_Delay 0x45600b8 1 Specifies the number of consecutive cycles the test must run in violation of the threshold before an event or alarm is generated.

Statistic_6_Clear_Delay 0x45600b9 1 Specifies the number of consecutive cycles the test must run without exceeding the threshold before an event or alarm is cleared.



Jitter Positive Destination to Source Threshold Parameters


Statistic_7_Thresh_State 0x45600ce 0 Specifies whether the Jitter positive destination to source threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Statistic_7_MinorSetValue 0x45600bd 25 Specifies the percentage of positive Jitter that must be exceeded before a minor alarm is generated.

Statistic_7_MajorSetValue 0x45600be None Specifies the percentage of positive Jitter that must be exceeded before a major alarm is generated.

Statistic_7_CriticalSetValue 0x45600bf None Specifies the percentage of positive Jitter that must be exceeded before a critical alarm is generated.

Statistic_7_Set_Value 0x45600bc None Specifies the percentage of positive Jitter that must be exceeded before an event is generated.

Statistic_7_Clear_Value 0x45600c0 25 Specifies the percentage of positive Jitter that must not be exceeded before an event is generated.

Statistic_7_Set_Delay 0x45600c1 1 Specifies the number of consecutive cycles the test must run in violation of the threshold before an event or alarm is generated.

Statistic_7_Clear_Delay 0x45600c2 1 Specifies the number of consecutive cycles the test must run without exceeding the threshold before an event or alarm is cleared.



Jitter Negative Source to Destination Threshold Parameters


Statistic_8_Thresh_State 0x45600cc 0 Specifies whether the Jitter negative source to destination threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Statistic_8_MinorSetValue 0x45600c5 25 Specifies the percentage of negative Jitter that must be exceeded before a minor alarm is generated.

Statistic_8_MajorSetValue 0x45600c6 None Specifies the percentage of negative Jitter that must be exceeded before a major alarm is generated.

Statistic_8_CriticalSetValue 0x45600c7 None Specifies the percentage of negative Jitter that must be exceeded before a critical alarm is generated.

Statistic_8_Set_Value 0x45600c5 None Specifies the percentage of negative Jitter that must be exceeded before an event is generated.

Statistic_8_Clear_Value 0x45600c9 25 Specifies the percentage of negative Jitter that must not be exceeded before an event is generated.

Statistic_8_Set_Delay 0x45600ca 1 Specifies the number of consecutive cycles the test must run in violation of the threshold before an event or alarm is generated.

Statistic_8_Clear_Delay 0x45600cb 1 Specifies the number of consecutive cycles the test must run without exceeding the threshold before an event or alarm is cleared.



Jitter Negative Destination to Source Threshold Parameters


Statistic_9_Thresh_State 0x45600d5 None Specifies whether the Jitter negative destination to source threshold is enabled or disabled for a test.

0 = DISABLED

1 = ENABLED

Statistic_9_MinorSetValue 0x45600cf 25 Specifies the percentage of negative Jitter that must be exceeded before a minor alarm is generated.

Statistic_9_MajorSetValue 0x45600d0 None Specifies the percentage of negative Jitter that must be exceeded before a major alarm is generated.

Statistic_9_CriticalSetValue 0x45600d1 None Specifies the percentage of negative Jitter that must be exceeded before a critical alarm is generated.

Statistic_9_Set_Value 0x45600ce None Specifies the percentage of negative Jitter that must be exceeded before an event is generated.

Statistic_9_Clear_Value 0x45600d2 25 Specifies the percentage of negative Jitter that must not be exceeded before an event is generated.

Statistic_9_Set_Delay 0x45600d3 1 Specifies the number of consecutive cycles the test must run in violation of the threshold before an event or alarm is generated.

Statistic_9_Clear_Delay 0x45600d4 1 Specifies the number of consecutive cycles the test must run without exceeding the threshold before an event or alarm is cleared.

Test Action Codes


Test Action CodesUse action codes with the CLI update command to save changes to tests and run tests.

Test Status and Test Results Parameters

SPM LatestStatus (0x4560004) Attribute Values

You can use the latest status attribute with the CLI show command to get status information for the most recently run test.

Action Code Description/Usage

Update test 0x4560008 Update the test after making attribute changes.

Run test 0x4560009 Run the test.

Update and Run test 0x456000a Combination of Update and Run actions.

Attribute Description

1=Ok Test ran successfully.

2=Threshold Test result has exceeded its “Set Value.”

3=Timeout Test timed out.

4=Failed Test failed to create a response time test table entry due to configuration issue.

5=Initial Test has never run.

6=Bad_comm Test failed to create a response time test table entry because of an invalid community name.

7=Running Test is running.

8=Stopped Test has stopped running.

9=Threshold_minor Test result has exceeded its “Minor Set Value.”

10=Threshold_major Test result has exceeded its “Major Value.”

11=Threshold_critical Test result has exceeded its “Critical Value.”



Test Results

Use the CLI show command to get results for a particular test.

Attribute Attribute ID Description

Result_Timestamp 0x456005e The time test last completed.

Latest_Result 0x4560015 Average Response Time (scalar).

TRACEROUTE_Result 0x4560075 TraceRoute Result. List of IP Address Latency Result pairs.

PL_Result 0x456007d % Packet Loss.

DNS_Latest_Result 0x4560037 Average HTTP DNS Lookup Time (scalar).

TCP_Latest_Result 0x456003f Average HTTP TCP Connection Time (scalar).

DL_Latest_Result 0x4560047 Average HTTP Page Download Time (scalar).

JPLSD_Latest_Result 0x456007e % Jitter Packets Loss between Source and Destination.

JPLDS_Latest_Result 0x456007f % Jitter Packets Loss between Destination and Source.

JBUS_Latest_Result 0x4560080 % Jitter Packets Busy.

JMIA_Latest_Result 0x4560081 % Jitter Packets Missing in Action.

JLATE_Latest_Result 0x4560082 % Jitter Packets Arriving Late.

PosJitterSD_LatestResult 0x45600b2 Average Positive Jitter between Source and Destination.

PosJitterDS_LatestResult 0x45600bb Average Positive Jitter between Destination and Source.

NegJitterSD_LatestResult 0x45600c4 Average Negative Jitter between Source and Destination.

NegJitterDS_LatestResult 0x45600cd Average Negative Jitter between Destination and Source.

MOS_Latest_Result 0x45600e5 Mean Opinion Score Value (0 - 500). It provides a numerical measure of the quality of human speech at the destination end of the circuit.

101

Appendix A: Troubleshooting

Content


“Firmware Issues” on page 101

“Timeout Errors” on page 103

“Test Scheduling Caveats” on page 104

“Delayed SpectroSERVER Activation Resulting from External Reads” on page 105

OverviewThis chapter identifies error messages that may be generated during SPM operations and describes corrective action where feasible. Other maintenance and optional configuration issues are also addressed.

Firmware IssuesCertain router firmware revisions, such as the one described in “Cisco IOS 12.0(9)” on page 101, can exhibit instability. CA follows published interfaces to the SNMP agents, and rely on the device vendors to fully support these interfaces. Before deploying SPM, it is advisable that users review device and firmware documentation from the vendor and apply any updates as appropriate.

Cisco IOS

When managing Jitter tests on Cisco IP SLA hosts, note that certain Cisco IOS versions do not allow codec type changes once the test has been run.

Cisco IOS 12.0(9)

Cisco IOS 12.0(9) has an issue that causes the router to reload upon the first SNMP SET performed to validate that the MIB is writable. See the following URL for more information:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120cavs/120mcavs.htm

Cisco IOS 12.0(9) has an issue that causes the router to reload upon an SNMP Get of the supported test types table, which occurs during model activation.



Cisco IOS 12.0(7)T2

Cisco IOS 12.0(7)T2 has an issue which causes the test described in “Traceroute Tests” on page 34 to fail. The problem is that the device does not properly report hop data in the result tables of the CISCO-RTTMON-MIB, which causes SPM to put erroneous data in the result event for average response time. To address this, upgrade your firmware to Cisco IOS 12.1(17).

Cisco IOS below 12.2

Cisco IOS below 12.2 has an issue which causes HTTP version 1.1 tests to fail with a “Request Timed Out” error message. Upgrading to Cisco IOS 12.2 or later versions will fix this issue.

Workaround: Changing the HTTP version from 1.1 to 1.0 may correct the timeout error message. See “Configure Advanced Parameters” on page 42 for more information.

Cisco IOS 12.2(2)T

Cisco IOS 12.2(2)T has an issue that causes the router to intermittently report incorrect operation error codes such that DHCP response time tests that have timed out are reported as “OK.” When this happens during a run of a DHCP test, SPM can report a latency value for that DHCP test that is greater than the timeout value set for the test. To address this, Cisco recommends upgrading your firmware to Cisco IOS 12.2(15)T2.

Cisco IOS 12.2(11)T

Cisco devices running IOS firmware 12.2(11)T and higher will now correctly function as test hosts in SPM. Previously, configured tests would not operate correctly due to changes in the RTTMon MIB.

Cisco IOS 12.3(4)

When running SPM tests, a router running Cisco IOS version 12.3(10a) that is configured for SAA/RTR may crash because of a memory leak in the SAA/RTR process. This issue has been resolved in IOS version 12.3 (11) TO4.

Cisco IOS 12.3(5) and below

In Cisco IOS versions 12.3(5) and below changing the packet size on a “Jitter Tests” on page 33 test will cause the IOS to crash and reboot the router. This issue has been addressed in Cisco IOS 12.3(5.013).

Cisco IOS 12.2(18)SXF3 and 12.2(18)SXF4

Cisco Routers running IOS 12.2(18)SXF3 and Version 12.2(18)SXF4 will crash when SPM tests are run because of Cisco bug CSCin62031. Routers running these IOS versions should not be modeled as test hosts capable of running Cisco IPSLA. To prevent these routers from being modeled as test hosts capable of running Cisco IPSLA, add these commands to the router configuration prior to modeling:

• snmp-server view NoRTTMON internet included

• snmp-server view NoRTTMON ciscoRttMonMIB excluded

• snmp-server community TEST view NoRTTMON RO

If the above configuration commands are added after modeling, then any attempt to run SPM tests will fail gracefully and not cause the router to crash.

Timeout Errors


Riverstone RS-8000 FW 9.0.0.4

Response time tests run from Riverstone RS-8000 (firmware 9.0.0.4) test host devices may return “Bad Configuration” errors. If this occurs, ensure that no two tests configured for the Riverstone test host have exactly the same character length names and rename any such tests as necessary. See “Configure General Parameters” on page 39 for more information.

Timeout ErrorsIn most cases, lack of access is the cause of timeout errors during SPM tests. For example, when Network Address Translation (NAT) is enabled, it can deny access to networks that are not in the list of networks to translate. Thus response time tests for HTTP or ICMP echo from an unlisted range of IPs would result in timeouts.

The solution in this case would be to add the test network to the NAT list and then re-run the tests. Other tests, such as DNS, DHCP, and UDP tests require that the test host device be properly configured for the service being tested.

Timeout errors can also be caused by setting the latency timeout parameter to an invalid value. Valid values for test timeouts can vary from test type to test type, and even from device to device. For example, the CISCO-RTTMON-MIB provides the following guideline in describing its timeout value:To prevent unwanted closure of connections, be sure to set this value to a realistic connection timeout.

Common solutions for timeout errors are:

• Ensure that you have SNMP read/write access on the test host device.

• Ensure that you have access from the test host device to the service being tested (ICMP, HTTP, etc.).

• Ensure that you have set reasonable values for test timeout.

Note: HTTP tests using certain Cisco Routers that run HTTP version 1.1 may fail with a “Request Timed Out” error. See “Firmware Issues” on page 101.

ICMP Ping Tests and Extreme Summit Test Host Devices

Ping tests run from Extreme Summit test host devices can result in timeouts. When you execute a ping from certain Extreme Summit devices, the RFC2925 branch of their MIB agents incorrectly reports a response time of 0. SPM interprets this as a timeout, when in fact the device has replied to the ping. The current workaround is to use a different device as a test host.

Traceroute Tests and iAgent Test Hosts

SPM always reports a timeout when traceroute tests are run on an iAgent test host. This issue has been resolved by iAgent version 16.2.



Test Scheduling CaveatsThis section contains the following information about scheduling tests:

• “Scheduling Tests in Geographically Distributed Environments”

• “Schedule Time Interval and CA SystemEDGE Agent Test Hosts”

• “Large Number of Tests on a Router Running Off Schedule”

Scheduling Tests in Geographically Distributed Environments

In a geographically distributed environment, the following network components can potentially be in different time zones:

• SpectroSERVERs

• OneClick Consoles

• Web servers

• Test host devices

Test scheduling in SPM is based on the time zone of the SpectroSERVER where the test host is modeled. Test results in SPM are based on the time zone local to the OneClick Console. To address the time discrepancy this confusion, choose the 24/7 option when scheduling.

Schedule Time Interval and CA SystemEDGE Agent Test Hosts

In general, to ensure scheduled tests run according to the configured schedule time interval the following algorithm is used to calculate when the scheduled test will run. This is applied after the previous test results are returned.(Schedule Time Interval) - (elapsed time since test last initiated) = (test time)

where (elapsed time since test last initiated) =(sample count) * (timeout).

SPM performs this calculation differently for tests run from CA SystemEDGE agent test hosts. Concord systemEDGE agents require the period over which response time statistics are calculated to be at least 60 seconds.

Tests scheduled to run on a CA SystemEDGE test host calculate:(elapsed time since test last initiated) =(sample count) * (timeout) + (60 seconds).

For example, using the default values for sample count and timeout of 5 and 5000 ms, respectively, yields the following calculation:(elapsed time since test last initiated) =(5 * 5000) + 60 = 85 seconds

Thus, the schedule time interval in this example must be set to greater than 85 seconds for scheduling to work properly.

Delayed SpectroSERVER Activation Resulting from External Reads


Large Number of Tests on a Router Running Off Schedule

Tests may run off schedule in cases where there are large numbers of tests on a single router. This is caused by the large number of snmp-gets performed to enforce the limit of a number of probes of the router. If tests begin to run off schedule, you can disable enforcement off by setting the EnforceMaxProbes/0x45600dc attribute to FALSE for one or more RTM_Test models with the OneClick Attribute Editor.

Delayed SpectroSERVER Activation Resulting from External Reads

For agents that support performance test types via MIB objects, SPECTRUM must perform external reads of these MIB objects at SpectroSERVER activation time to obtain the list of supported test types. This can delay the SpectroSERVER activation time. To remedy delayed activation, you can configure the spm_fast_activate parameter in the .vnmrc file to delay the external reads until the SpectroSERVER has been activated.

Set the default value of spm_fast_activate from No to Yes to prevent SPM from performing external reads until the SpectroSERVER is activated. Note that the agent test host will remain inactive until the SpectroSERVER is activated.

107

Appendix B: SPM Event Codes

Event Code DescriptionsTable B-1 lists SPM events by event code, event name, the model types the event can be asserted on, the alarm generated or cleared (if any), and alarm severity.

Table B-1: Event Codes

Event Code Event Name Model Type Asserted On Alarm Generated or Cleared

Alarm Severity

0x04560000 SPM Result Event RTM_Test None Not Applicable

0x04560001 SPM Timeout Event (See “About SPM Timeout Event” on page 114 for more information.)

RTM_Test 0x04560001 Yellow

0x04560002 SPM Test Host Configuration Failed Event


0x04560003 SPM Threshold Exceeded Event

RTM_Test, RTM_TestHost, Source, or Destination

None Not Applicable



0x04560003 Yellow



0x04560003 Orange



0x04560003 Red

0x04560007 SPM Threshold Cleared Event RTM_Test, RTM_TestHost, Source, or Destination

Clears 0x04560003

Not Applicable

0x04560008 SPM Test Creation Event RTM_Test None Not Applicable

0x0456000a SPM Test Modification Event RTM_Test None Not Applicable

0x0456000b SPM Packet Loss Threshold Exceeded Event


None Not Applicable



0x0456000c SPM Packet Loss Exceeded Event


0x0456000b Yellow

0x0456000d SPM Packet Loss Exceeded Event


0x0456000b Orange

0x0456000e SPM Packet Loss Exceeded Event


0x0456000b Red

0x0456000f SPM Packet Loss Cleared Event


Clears 0x0456000b

Not Applicable

0x04560010 SPM Result Event (Jitter) RTM_Test None Not Applicable

0x04560011 SPM Jitter Packet Loss Source to Destination Exceeded Event


None Not Applicable



0x04560011 Yellow



0x04560011 Orange



0x04560011 Red

0x04560015 SPM Jitter Packet Loss Source to Destination Cleared Event


Clears 0x04560011

Not Applicable

0x04560016 SPM Jitter Packet Loss Destination to Source Threshold Exceeded Event


None Not Applicable

0x04560017 SPM Jitter Packet Loss Destination to Source Exceeded Event


0x04560016 Yellow



0x04560016 Orange



0x04560016 Red

0x0456001a SPM Jitter Packet Loss Destination to Source Threshold Cleared Event


Clears 0x04560016

Not Applicable

0x0456001b SPM Jitter Packet MIA Threshold Exceeded Event


None Not Applicable

0x0456001c SPM Jitter Packet MIA Threshold Exceeded Event


0x0456001b Yellow

Table B-1: Event Codes (Continued)


Alarm Severity

Event Code Descriptions


0x0456001d SPM Jitter Packet MIA Threshold Exceeded Event


0x0456001b Orange

0x0456001e SPM Jitter Packet MIA Threshold Exceeded Event


0x0456001b Red

0x0456001f SPM Jitter Packet MIA Threshold Cleared Event


Clears 0x0456001b

Not Applicable

0x04560020 SPM Jitter Packet Late Arrival Threshold Exceeded Event


None Not Applicable



0x04560020 Yellow



0x04560020 Orange



0x04560020 Red

0x04560024 SPM Jitter Packet Late Arrival Threshold Cleared Event


Clears 0x04560020

Not Applicable

0x04560025 SPM Jitter Busies Threshold Exceeded Event


None Not Applicable



0x04560025 Yellow



0x04560025 Orange



0x04560025 Red

0x04560029 SPM Jitter Busies Threshold Cleared Event


Clears 0x04560025

Not Applicable

0x0456002a SPM Test Pause (Test Host Down) Event

RTM_Test None Not Applicable

0x0456002b SPM Test Restart (Test Host Recontacted) Event


0x0456002c SPM Test Entering Management Mode Event


0x0456002d SPM Test Exiting Management Mode Event


0x0456002e SPM Result Event (HTTP) RTM_Test None Not Applicable

0x0456002f SPM HTTP DNS Resolution Threshold Exceeded Event


None Not Applicable

0x04560030 SPM HTTP DNS Resolution Threshold Exceeded Event


0x0456002f Yellow



Alarm Severity





0x0456002f Orange



0x0456002f Red

0x04560033 SPM HTTP DNS Resolution Threshold Cleared Event


Clears 0x0456002f

Not Applicable

0x04560034 SPM HTTP TCP Connect Threshold Exceeded Event


None Not Applicable



0x04560034 Yellow



0x04560034 Orange



0x04560034 Red

0x04560038 SPM HTTP TCP Connect Threshold Cleared Event


Clears 0x04560034

Not Applicable

0x04560039 SPM HTTP Page Download Threshold Exceeded Event


None Not Applicable

0x0456003a SPM HTTP Page Download Threshold Exceeded Event


0x0456003c Yellow

0x0456003b SPM HTTP Page Download Threshold Exceeded Event


0x0456003c Orange

0x0456003c SPM HTTP Page Download Threshold Exceeded Event


0x0456003c Red

0x0456003d SPM HTTP Page Download Threshold Cleared Event


Clears 0x0456003c

Not Applicable

0x0456003e SPM Result Event (Traceroute)


0x0456003f SPM Traceroute Threshold Exceeded Event


None Not Applicable

0x04560040 SPM Traceroute Threshold Exceeded Event


0x0456003f Yellow



0x0456003f Orange



0x0456003f Red

0x04560043 SPM Traceroute Threshold Cleared Event


Clears

0x0456003f

Not Applicable

0x04560044 SPM Test SNMP Set Failure Event

RTM_TestHost 0x04560044 Yellow



Alarm Severity



0x04560045 SPM Test SNMP Set Failure Cleared Event

RTM_TestHost Clears 0x04560044

Not Applicable

0x04560046 SPM Test Timeout Cleared Event

RTM_Test Clears 0x04560001

Not Applicable

0x04560047 SPM Test Host Configuration Failed Cleared Event


Not Applicable

0x04560048 SPM Too Many Probes On Test Host Event


0x04560049 SPM Too Many Probes on Test Host Cleared Event

RTM_TestHost Clears

0x04560048

Not Applicable

0x0456004a SPM HTTP Result Event RTM_Test None Not Applicable

0x04560054 Bad Ping Result RTM_Test None Not Applicable

0x04560055 Bad Jitter Result RTM_Test None Not Applicable

0x04560056 Bad HTTP Result RTM_Test None Not Applicable

0x04560057 Bad Traceroute Result RTM_Test None Not Applicable

0x04560058 Bad HTTP Result RTM_Test None Not Applicable

0x04560059 SPM Test No Longer On Device Event


0x0456005a SPM Test No Longer Running On Device Event


0x0456005b SPM Duplicate Result Event RTM_Test None Not Applicable

0x0456005c SPM Test Discovery Completion Event

RTM_TestHost None Not Applicable

0x0456005d SPM Test Type Mismatch Event

RTM_Test 0x0456005d Yellow

0x0456005e SPM Stale Test Cleared Event RTM_Test Clears 0x045600590x0456005d

Not Applicable

0x0456005f SPM Positive Jitter Source to Destination Exceeded Event


None Not Applicable

0x04560060 SPM Positive Jitter Source to Destination Exceeded Event


0x0456005f Yellow



0x0456005f Orange



0x0456005f Red

0x04560063 SPM Positive Jitter Source to Destination Cleared Event


Clears 0x0456005f

Not Applicable



Alarm Severity



0x04560064 SPM Positive Jitter Destination to Source Exceeded Event


None Not Applicable



0x04560064 Yellow



0x04560064 Orange



0x04560064 Red

0x04560068 SPM Positive Jitter Destination to Source Cleared Event


Clears 0x04560064

Not Applicable

0x04560069 SPM Negative Jitter Source to Destination Exceeded Event


None Not Applicable

0x0456006a SPM Negative Jitter Source to Destination Exceeded Event


0x04560069 Yellow

0x0456006b SPM Negative Jitter Source to Destination Exceeded Event


0x04560069 Orange

0x0456006c SPM Negative Jitter Source to Destination Exceeded Event


0x04560069 Red

0x0456006d SPM Negative Jitter Source to Destination Cleared Event


Clears 0x04560069

Not Applicable

0x0456006e SPM Negative Jitter Destination to Source Exceeded Event


None Not Applicable

0x0456006f SPM Negative Jitter Destination to Source Exceeded Event


0x0456006e Yellow

0x04560070 SPM Negative Jitter Destination to Source Exceeded Event


0x0456006e Orange

0x04560071 SPM Negative Jitter Destination to Source Exceeded Event


0x0456006e Red

0x04560072 SPM Negative Jitter Destination to Source Cleared Event


Clears 0x0456006e

Not Applicable

0x04560073 SPM Too Many Probes Event RTM_Test None Not Applicable

0x04560074 SPM Bad Community String Event




Alarm Severity



0x04560075 SPM Invalid Destination Address Event


0x04560076 SPM Invalid Destination Address Cleared Event


Not Applicable

0x04560077 SPM Invalid Test Host Event RTM_Test 0x04560077 Yellow

0x04560078 SPM Invalid Test Type Event RTM_Test 0x04560078 Yellow

0x04560079 SPM RTM_TestHost No Device Model Event


0x0456007a SPM RTM_TestHost No Device Model Cleared Event

RTM_TestHost Clears 0x04560079

Not Applicable

0x0456007b SPM Result Failure Event RTM_Test None Not Applicable

0x0456007c SPM Mean Opinion Score (MOS) event


None Not Applicable

0x0456007d SPM Mean Opinion Score (MOS) event


0x456007c Yellow

0x0456007e SPM Mean Opinion Score (MOS) event


0x456007c Orange

0x0456007f SPM Mean Opinion Score (MOS) event


0x456007c Red

0x04560080 SPM Mean Opinion Score (MOS) event


Clears 0x456007c

Not Applicable

0x04560081 Juniper Jitter Result Event RTM_Test, RTM_TestHost, Source, or Destination

None Not Applicable

0x04560082 Bad Juniper Jitter Result RTM_Test, RTM_TestHost, Source, or Destination

None Not Applicable

0x04560083 Juniper RTT Jitter Exceeded Event


None Not Applicable



0x04560083 Yellow



0x04560083 Orange



0x04560083 Red

0x04560087 Juniper RTT Jitter Cleared Event


0x04560083 Not Applicable

0x04560088 Juniper Egress Jitter Exceeded Event


None Not Applicable



0x04560088 Yellow



Alarm Severity



About SPM Timeout EventSPM determines when it is appropriate to generate SPM Timeout Event and its associated alarm:

• SPM Tmeout Event and its related alarm is suppressed if the destination IP of the SPM test represents a SPECTRUM device model that does not have ICMP contact. The alarm appears as a symptom of the “DEVICE HAS STOPPED RESPONDING TO POLLS” alarm of the SPECTRUM device model.

• SPM Timeout Event and its related alarm is not generated if the SPM Test Host does not have SNMP contact at the time that the RTM results are read for a given SPM test.

0x0456008a Juniper Egress Jitter Exceeded Event


0x04560088 Orange

0x0456008b Juniper Egress Jitter Exceeded Event


0x04560088 Red

0x0456008c Juniper Egress Jitter Cleared Event


Clears

0x04560088

Not Applicable

0x0456008d Juniper Egress Jitter Exceeded Event


None Not Applicable

0x0456008e Juniper Egress Jitter Exceeded Event


0x0456008d Yellow

0x0456008f Juniper Egress Jitter Exceeded Event


0x0456008d Orange



0x0456008d Red

0x04560091 Juniper Egress Jitter Cleared Event


Clears

0x0456008d

Not Applicable



Alarm Severity

115

Index

AAccessing SPM 19Action codes

used with CLI update command 99Activate Test Host icon 49Activating test hosts 48Administrator user role 19Agents and MIBs

CA eHealth SystemEdge Service Availability agent 16

Cisco IOS IP SLAs Agent 16iAgent 17JUNOS Real Time Performance Monitor 17Network Harmoni SLAplus Agent 17, 43RFC2925 16

Alarms 16critical for test threshold violations 47for test threshold violations 45major for test threshold violations 47minor for test threshold violations 46viewing 70

Alternate source address for test source 40Apply Test Template icon 56

CCA eHealth SystemEdge Service Availability

agent 16Caveats, test scheduling 104Cisco IOS IP SLAs Agent 16Cisco Ping MIB 16CISCO-RTTMON-MIB 103Codec type

Jitter tests 40mean opinion scoring 40

Command Line Interface (CLI) 79creating tests with 79editing tests with 79optional test parameters 84required test parameters 82retrieving test results 100retrieving test status results 99running tests with 79schedule test parameters 83test action codes 99test parameters 82test schedule parameters 83threshold parameters 86

Community names for test hosts 14Configuring test

schedule parameters 44Configuring tests 38

advanced parameters 42general parameters 39threshold parameters 45

Copy (test template) icon 55Copy (test) icon 31Copying

tests 31, 55Create Schedule dialog box 45Creating

test schedules 45test templates 54tests 29tests automatically with test templates 57tests by copying 31, 55tests with CLI 79


Index

DDeactivate Test Host icon 50Deactivating test hosts 48Delete (test template) icon 61Delete (test) icon 52Deleting

test templates 61tests 52

Destination address for a test 40Destination DNS server 40Destination port for mean opinion score 40Destination URL for HTTP tests 40DHCP tests 15, 32Disable a test 39Disabling test thresholds 46Discovering tests 35Discovery mode

changing for test discovery 36DNS tests 15, 32

destination server 40lookup name 40

Documentconventions 10OneClick document set 11

EEdit (test template) icon 60Edit Test icon 51Editing

test templates 60tests 50tests with CLI 79

Enable a test 39Enabling test thresholds 46Event codes 107

test discovery 37External test reads, effect on SpectroSERVER

activation 105Extreme Summit host devices, ping time-

outs 103

FFilter timeout data 43Filter timeout data setting 68Firmware issues

Cisco IOS 12.0(7)T2 102Cisco IOS 12.0(9) 101Cisco IOS 12.2 102Cisco IOS 12.2(11)T 102

Cisco IOS 12.2(18)SXF3 102Cisco IOS 12.2(18)SXF4 102Cisco IOS 12.2(2)T 102Cisco IOS 12.3(4) 102Cisco IOS 12.3(5) 102Riverstone RS-8000 FW 9.0.0.4 103

FTP tests 15, 32file name 40password 40user name 40

GGlobal Collection 15Global Collections 54Graphs

of test results 66

HHTTP tests 15, 32

destination URL 40HTTP version 43password 40proxy URL 43user name 40

IiAgent 17iAgent test hosts, traceroute timeout 103ICMP 15ICMP Ping tests 33

JJitter tests 15, 33

codec type 40destination port 40voice quality testing 40

JUNOS Real Time Performance Monitor 17

LLatency timeout 39Logging, test data 75Lookup name for DNS tests 40

Index


MMaintenance mode for test hosts 49Mean opinion score 100

destination port range 40MOS, see Mean opinion score

NNetwork application response time tests

FTP 15HTTP 15POP3 15SMTP 15TCP 15UDP 15

Network Harmoni SLAplus Agent 17, 43Network response time tests

ICMP Ping 15Jitter 15traceroute 15

Network service response time testsDHCP 15DNS 15

New (test) icon 30

OOperator user role 19

PPacket Loss 66Packet loss 15Packet size used in tests 43Performance graph for tests 68Performance Tab

graphs of test results 66viewing test results in 66

Ping tests 15alternative source location 40

POP3 tests 15, 34password 40user name 40

RRead/Write test discovery mode 35Read-only test discovery mode 35Reports, test results

Report Gateway 75Report Manager 71

RFC2925 16RTM_Test model parameters

required for tests 82RTTMON

sample count 43, 66RTTMON MIB 16, 103Running tests on demand 47Running tests with CLI 79

SSample Count 66Sample count for tests 43Schedule test parameters 83Scheduling

tests 45Scheduling a test 44Scheduling tests

available schedules 44caveats 104enabling and disabling 44specifying an alternate test run interval 44specifying the test run interval 44

Searchesfor SPM components 23results for SPM 24test hosts 25test templates 25tests 25

Securing SPM tests 22Securing tests hosts 21Security strings, overwriting 22SMTP tests 15, 34Specifying the test host location 40SPM searches 23SPM searches, see Searches

TTCP tests 15, 34Template type 54Test discovery 35

event codes 37Test host location 40


Index

Test hostsactivating and deactivating 48, 49component detail view 64extended path location 42information view 63IP address 39maintenance mode 49mid-path location 41read/write community names 14searches 25securing 21source location 41specify the location between a source and

destinationPing tests

location of test host 40Test parameters

active thresholds schedule 46alternate packet address 43alternate packet port 43alternate source address 40codec type 40description 39destination address 40destination DNS server 40destination URL 40event 46file name 40filter timeout data 43HTTP version 43latency timeout 39lookup name 40optional 84packet size 43password 40proxy URL 43required 82sample count 43schedule 44, 83schedule state 44schedule time interval 44state 39status 46test host IP address 39test host location 40test name 39threshold events asserted on 46threshold types 46threshold violation interval 44thresholds 86type of service 43user name 40voice test 40

Test parameters, thresholdsclear cycles 47clear threshold 47critical alarm 47major alarm 47minor alarm 46threshold cycles 47

Test result attributesused with CLI show command 100

Test Resultsgraphical representation of 66retrieving with CLI 79

Test status result attributesused with CLI show command 99

Test template parametersglobal collections 54template type 54

Test templates 15applying to select test hosts 56applying to test hosts in global collection 57creating 54deleting 61editing 60removing association with a Global

Collection 61searches 25

Test types 32network application response time 14network response time 14network service response time 14

Testscomponent detail view 66configuration 38copying 31, 55creating 29default name 39deleting 52discovering 35editing 50enabling and disabling 39enabling and disabling schedules 44event codes 107information view 65managing with CLI 79name for 39performance view 66running 47scheduling 44, 45scheduling caveats 104searches 25securing 22

Index


service level agreements 18specifying thresholds 45timeout errors 103

Thresholds for tests 45enabling and disabling 46establishing baseline values 47number of violations before an event/alarm is

generated 47scheduling when in effect 46types 46when event is generated 46when events/alarms are cleared 47where violation events are asserted 46

Time Zones 44, 46Timeout errors 103Traceroute tests 15, 34Troubleshooting 101Type of Service (TOS) 43

UUDP tests 15, 34User roles and rights 19

VViolations of test thresholds 45


Index

service performance manager - ca technologies - ca...

Documents