0904 1296C CPTS Test Guide

P/N 340-1296-001 REV C

Test Guide

CDMA2000 Performance Test SystemVersion 1.2September 2004

Spirent Communications, Inc.26750 Agoura RoadCalabasas, CA91302 USA

Support ContactsU.S.E-mail: [email protected]: http://support.spirentcom.comToll Free: 1-800-SPIRENT (1-800-774-7368)Phone: + 1 818-676-2616Fax: +1 818-880-9154

EuropeE-mail: [email protected]: http://support.spirentcom.comPhone: +33 (0) 1 61 37 22 70Fax: +33 (0) 1 61 37 22 51

Copyright© 2004 Spirent Communications, Inc. All Rights Reserved.

All of the company names and/or brand names and/or product names referred to in this document, in particular, the name "Spirent" and its logo device, are either registered trademarks or trademarks of Spirent plc and its subsidiaries, pending registration in accordance with relevant national laws. All other registered trademarks or trademarks are the property of their respective owners. The information contained in this document is subject to change without notice and does not represent a commitment on the part of Spirent Communications. The information in this document is believed to be accurate and reliable, however, Spirent Communications assumes no responsibility or liability for any errors or inaccuracies that may appear in the document.

Limited WarrantySpirent Communications, Inc. (“Spirent”) warrants that its Products will conform to the description on the face of order, that it will convey good title thereto, and that the Product will be delivered free from any lawful security interest or other lien or encumbrance.

Spirent further warrants to Customer that hardware which it supplies and the tangible media on which it supplies software will be free from significant defects in materials and workmanship for a period of twelve (12) months, except as otherwise noted, from the date of delivery (the “Warranty Period”), under normal use and conditions.

To the extent the Product is or contains software (“Software”), Spirent also warrants that the Software, if properly used by Licensee in accordance with the Software License Agreement, shall operate in material conformity with the specification for such Software for a period of ninety (90) days from the date of delivery (the “Warranty Period”). Spirent does not warrant that the functions contained in the Software will meet a specific requirement or that the operation will be uninterrupted or error free. Spirent shall have no warranty obligations whatsoever with respect to any Software which has been modified in any manner by Customer or any third party.

Defective Products and Software under warranty shall be, at Spirent's discretion, repaired or replaced or a credit issued to Customer's account for an amount equal to the price paid for such Product provided that: (a) such Product is returned to Spirent after first obtaining a return authorization number and shipping instructions, freight prepaid, to Spirent's location in the United States; (b) Customer provides a written explanation of the defect or Software failure claimed by Customer; and (c) the claimed defect actually exists and was not caused by neglect, accident, misuse, improper installation, improper repair, fire, flood, lightning, power surges, earthquake, or alteration. Spirent will ship repaired Products to Customer, freight prepaid. Except as otherwise stated, any claim on account of defective materials or for any other cause whatsoever will conclusively be deemed waived by Customer unless written notice thereof is given to Spirent within the Warranty Period. Spirent reserves the right to change the warranty and service policy set forth above at any time, after reasonable notice and without liability to Customer.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, ALL IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, ARE HEREBY EXCLUDED, AND THE LIABILITY OF SPIRENT, IF ANY, FOR DAMAGE RELATING TO ANY ALLEGEDLY DEFECTIVE PRODUCT SHALL BE LIMITED TO THE ACTUAL PRICE PAID BY THE CUSTOMER FOR SUCH PRODUCT. THE PROVISIONS SET FORTH ABOVE STATE SPIRENT'S ENTIRE RESPONSIBILITY AND CUSTOMER'S SOLE AND EXCLUSIVE REMEDY WITH RESPECT TO ANY BREACH OF ANY WARRANTY.

mailto:[email protected]

http://support.spirentcom.com



CDMA2000 Performance Test System Test Guide | iii

Contents

About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Manual Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Related Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6How to Contact Us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 1: Test Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10PDSN-FA Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Simple IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Simple IP Virtual Private Network (VPN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Simple IP Virtual Private Routed Network (VPRN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Mobile IP - FA Nodal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12MIP Reverse Tunnel - FA Nodal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12MIP VPN - FA Nodal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13MIP Network Based VPN - FA Nodal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

HA Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Mobile IP - HA Nodal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14MIP Reverse Tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15MIP VPN - HA Nodal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15MIP Network Based VPN - HA Nodal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

End-to-End Test Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16MIP - End-to-End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16MIP Reverse Tunnel - End-to-End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17MIP VPN - End-to-End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17MIP Network Based VPN - End-to-End. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 2: Test Case Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Simple IP Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Simple IP VPN Test Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24FA Nodal Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28HA Nodal Test Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34End-to-End MIP Test Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Network Host Test Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Test Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Capacity Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Capacity Test Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Capacity Test Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Contents

iv | CDMA2000 Performance Test System Test Guide

Session Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Session Loading Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Session Loading Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Session Loading With Mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Session Loading With Mobility Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Session Loading With Mobility Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Session Loading Rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Session Loading Rate Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Session Loading Rate Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Session Activation Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Session Activation Rate Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Session Activation Rate Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Intra-PDSN Handoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Intra-PDSN Handoff Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Intra-PDSN Handoff Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Intra-PDSN Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Intra-PDSN Rate Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Intra-PDSN Rate Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

MIP Revocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68MIP Revocation Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68MIP Revocation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Inter-PDSN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Inter-PDSN Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Inter-PDSN Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Inter-PDSN Handoff Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Inter-PDSN Handoff Rate Set Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Inter-PDSN Handoff Rate Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Data Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Continuous Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85SUT Query Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Protocol Configuration Set Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Modifying MIP Protocol Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Modifying RP Protocol Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Modifying L2TP Protocol Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Modifying PPP Protocol Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 3: Test Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Variable Parameter Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Simple IP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Simple IP VPN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112MIP FA Nodal Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113MIP HA Nodal Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115End-to-End Mobile IP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Common Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118SUT Query Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Test Activity Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Capacity Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Contents

CDMA2000 Performance Test System Test Guide | v

Session Loading Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Session Loading with Mobility Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Session Loading Rate Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Session Activation Rate Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Intra-PDSN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Intra-PDSN Rate Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131MIP Revocation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Inter-PDSN Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Inter-PDSN Rate Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138L2TP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140RP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142PPP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Data Traffic Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148MIP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164MIP Parameters for HA Nodal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Chapter 4: Test Case Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Rate Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Test Summary Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Test Summary Measurements for CPU Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Test Summary Measurements for Mobility Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Test Summary Measurements for MIP Revocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Test Summary Measurements for L2TP VPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178RP Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179PPP Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Mobile IP Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185MIP Node Emulator Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192FA Emulation Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193HA Emulation Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196PCF Emulation Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Network Host Emulator Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Data Traffic Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Interpreting Data Traffic Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199L2TP Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204L2TP Node Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Rate Test Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Appendix A: ESD Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211General Equipment Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Workstation Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Appendix B: Fiber Optic Cleaning Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . 213Cleaning Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

vi | CDMA2000 Performance Test System Test Guide

CDMA2000 Performance Test System Test Guide | 1

About this Guide

In About this Guide...

This portion of the Test Guide contains the following topics:

Manual Content....2

Conventions....3

Related Manuals....4

Acronyms....4

Glossary....6

How to Contact Us....8

About this GuideManual Content

2 | CDMA2000 Performance Test System Test Guide

Manual ContentThe purpose of this document is to provide the user with the necessary information to configure various types of test cases for the CDMA2000 Performance Test System (CPTS) and interpret test session results.

Important: The CDMA2000 Performance Test System User Guide is a prerequisite to this document. It contains detailed procedures for managing test cases, as well as creating and running test sessions.

The table below describes the sections in this guide and their intended audience.

Section Audience Description

“About this Guide” All CPTS users Provides information on this guide including its purpose, the intended audience, content and organization, conventions used, related documentation, online Help, and how to contact technical support.

Chapter 1, “Test Configurations”

All CPTS users Provides information and diagrams concerning the basic test configurations supported by the CPTS.

Chapter 2, “Test Case Set Up”

All CPTS users Provides detailed procedures for the set up and configuration of test cases.

Chapter 3, “Test Parameters”

All CPTS users Provides detailed descriptions of each configurable parameter.

Chapter 4, “Test Case Measurements”

All CPTS users Provides detailed descriptions of each measurement provided by the CPTS.

Appendix A, “ESD Requirements”

All CPTS users Explains precautions to protect against damage from electrostatic discharge (ESD). This information applies to Spirent Communications hardware.

Appendix B, “Fiber Optic Cleaning Guidelines”

All CPTS users Explains cleaning guidelines for Spirent Communications products that contain fiber optic components, such as fiber optic transmitters and receivers.

“Index” All CPTS users Provides a comprehensive index listing.

About this GuideConventions


Conventions This section explains the typographical conventions used in this guide.

Note: The Spirent Mobility 2500 system is now known as the Landslide 2500 system. Any references to "TAS" in this manual are equivalent to "Landslide Manager." Any references to "Test Server" are equivalent to "Landslide 2500." Any references to "Mobility 2500 ES" are equivalent to "Landslide 2500 ES." The CDMA2000 Performance Test System and GPRS Performance Test System are applications that run on the Landslide 2500 system.

• Italics are used to indicate titles of books, volumes, documents, sections of documents (such as chapters), areas or panes within windows, tabs, field or parameter names, and for general emphasis. For example:

• For detailed descriptions of test operations including test configurations, test cases, and test results, see the CDMA2000 Performance Test System Test Guide.

• The Traffic area of the window contains four options.

• The test results provide information on the packet loss of the device.

• Bold type is used to indicate selections made during a procedure (such as menu options that you select, or tabs or buttons that you click). Bold type is also used for names of parameters being acted upon, for parameter options, and to indicate directory paths. For example:

• To open a new test session window, select New on the Wireless Packet Test Sys-tem File menu.

• Select the User or Global library from the Library pull-down menu.

• This file is stored in directory /usr/sms/data/log_auto_archive, and it is named old_logs.

• Courier text is used for code samples and to indicate text or commands that you need to enter exactly as shown.

• User-specific information are in italics and enclosed in “<>” (<backup_directory>).

• Notes, cautions, warnings, and important information are indicated as follows:

Note: Calls attention to additional information or explanation.

! Caution: Calls attention to procedures or practices that should be followed to avoid damage to hardware, or corruption and possible loss of software files and/or data.

Warning: Calls attention to operating procedures or practices that should be followed to avoid bodily injury or damage to equipment.

Important: Calls attention to important information or characteristics that might be overlooked.

About this GuideRelated Manuals


Tip: Calls attention to helpful information about a product's operation or setup that eases its use.

Identifies procedures.

Related Manuals• Landslide 2500 Installation Guide or Landslide 2500 ES Installation Guide

• CDMA2000 Performance Test System User Guide

Acronyms• AA - Agent Advertisement

• AAA - Authentication, Authorization, and Accounting

• ACCM - Asynchronous Control Character Map

• ACK - Acknowledge

• BSID - Base Station ID

• CANID - Current Access Network ID

• CDMA - Code Division Multiplex Access

• CHAP - Challenge Handshake Authentication Protocol

• CPU - Central Processing Unit

• CPTS – CDMA2000 Performance Test System

• FA - Foreign Agent

• FAMN - Foreign Agent-Mobile Node

• FTP - File Transfer Protocol

• GUI - Graphical User Interface

• HA - Home Agent

• HTTP - Hypertext Transfer Protocol

• IP - Internet Protocol

• IPCP - PPP Internet Protocol Control Protocol

• IP/IP - IP in IP encapsulation

About this GuideAcronyms


• IPSec - IP Security Protocol

• L2TP - Layer 2 Tunneling Protocol

• LAC - L2TP Access Concentrator

• LAN - Local Area Network

• LCP - Link Control Protocol

• LNS - L2TP Network Server

• MEI - Mobility Event Indicator

• MIP - Mobile Internet Protocol

• MN - Mobile Node

• MS - Mobile Station

• NAI - Network Access Identifier

• PAP - Password Authentication Protocol

• PANID - Previous Access Network ID

• PCF - Packet Control Function

• PDSN - Packet Data Serving Node

• PDSN-FA - Packet Data Serving Node - Foreign Agent

• PPP - Point-to-Point Protocol

• QOS - Quality of Service

• RP - Radio Packet

• RRP - Registration Reply

• RRQ - Registration Request

• RRV - Registration Revocation

• RRVA - Registration Revocation Acknowledgement

• SMTP - Simple Mail Transfer Protocol

• SPI - Security Parameter Index

• SUT – System(s) Under Test

• TAS – Test Administration Server

• TCP - Transmission Control Protocol

• TS – Test Server(s)

• UDP - User Datagram Protocol

• VJ - Van Jacobson compression

About this GuideGlossary


• VLAN - Virtual Local Area Network

• VPN - Virtual Private Network

• VPRN - Virtual Private Routed Network

• WAP - Wireless Application Protocol

Glossary

Distribution Model - Fixed

A fixed distribution model provides a constant rate which does not deviate from the user selected rate. For example, if a user selects a session activation rate of 200 sessions/second, selecting a fixed distribution model will result in 200 activations every second.

Distribution Model - Uniform

The uniform distribution model evenly distributes the user selected rate between a minimum and maximum range. The width of this range is user-defined as a percentage of the mean (user selected rate). For example, if the user selects a rate of 200 sessions/second and a deviation from mean of 10%, then the actual sessions/second rate will be evenly distributed between 180 sessions/second and 220 sessions/second.

Distribution Model - Normal

A normal distribution model allows the user to specify a rate which is randomly distributed in a bell shaped fashion. The shape of the bell is user-defined as a percentage of the mean (user selected rate). The width of the bell curve is 4 times the standard deviation. For example, if the user selects a rate of 200 sessions/second and a standard deviation of 10%, then the actual connect rate will vary in a bell shaped distribution between 120 sessions/second and 280 sessions/second (4 * the min/max value).

Distribution Model - Poisson

Poisson distribution allows the user to specify a rate which is randomly distributed across a Poisson bell curve between a minimum and maximum range. The width of this range is user-defined as a percentage of the mean (user selected rate). For example, if the user selects a rate of 200 sessions/second and a deviation from the mean of 10%, then the actual connect rate will vary in a Poisson shaped distribution between 180 sessions/second and 220 sessions second.

Intra-PDSN Handoff

A mobility event that occurs when a mobile node moves from one PCF to another PCF on the same PDSN. The handoff is processed by the PDSN-FA.

About this GuideGlossary


Inter-PDSN Handoff

A mobility event that occurs when a mobile node moves from one PDSN-FA to another PDSN-FA. The handoff is processed by the HA.

Test Case The smallest test element that can be configured for execution on a single test server.

Test Session A collection of one or more configured test cases used to run a test on one or more test servers.

About this GuideHow to Contact Us


How to Contact UsTechnical support is available Monday through Friday between 06:00 and 18:00 Pacific Time.

To obtain technical support for any product, please contact our Technical Support Department using any of the following methods:

U.S.

E-mail: [email protected]: http://support.spirentcom.comToll Free: 1-800-SPIRENT (1-800-774-7368)Phone: + 1 818-676-2616Fax: +1 818-880-9154

Europe

E-mail: [email protected]: http://support.spirentcom.comPhone: +33 (0) 1 61 37 22 70Fax: +33 (0) 1 61 37 22 51

In addition, the latest versions of user manuals, application notes, and software and firmware updates are available on the Spirent Communications Customer Service Center website at http://support.spirentcom.com.

Company Address

Spirent Communications, Inc.26750 Agoura RoadCalabasas, CA 91302USA







Chapter 1

Test Configurations

This chapter provides detailed information on the test configurations.

In this chapter...

This chapter contains the following topics:

Purpose....10

PDSN-FA Configurations....10

HA Configurations....14

End-to-End Test Configurations....16

Test ConfigurationsPurpose


PurposeThe following sections describe each of the test configurations supported by the CPTS. The CPTS may be used to test in multiple test configurations through the selection of various test scenarios.

PDSN-FA ConfigurationsThis section describes the various configurations and the simulation capabilitiesof the system.

Simple IP

When a user selects a test scenario requiring a Simple IP access model, the user configures the emulated nodes shown in Figure 1-1. In this configuration, the CPTS emulates the MN(s), a single or multiple PCF(s) as well as the network side of the PDSN-FA.

Figure 1-1 shows the PDSN-FA Simple IP configuration.

Figure 1-1 PDSN-FA Simple IP Configuration

Simple IP Virtual Private Network (VPN)

When a user selects a test scenario requiring a Simple IP VPN access model, the user configures the emulated nodes shown in Figure 1-2. In this configuration, the CPTS emulates the mobile nodes (MN(s)), a single or multiple PCF(s) as well as the security gateway on the network side of the PDSN-FA.

Figure 1-2 shows the PDSN-FA Simple IP VPN configuration.

Test ConfigurationsPDSN-FA Configurations


Figure 1-2 PDSN-FA Simple IP VPN Configuration

Simple IP Virtual Private Routed Network (VPRN)

When a user selects a test scenario requiring a Simple IP VPRN access model, the user configures the emulated nodes shown in Figure 1-3. In this configuration, the CPTS emulates the MN(s), a single or multiple PCF(s) as well as the security gateway on the network side of the PDSN-FA.

Figure 1-3 shows the PDSN-FA Simple IP VPRN configuration.

Figure 1-3 PDSN-FA Simple IP VPRN Configuration



Mobile IP - FA Nodal

When a user selects a test scenario requiring a MIP - PDSN-FA nodal access model, the user configures the emulated nodes shown in Figure 1-4. In this configuration, the CPTS emulates the MN(s), a single or multiple PCF(s), the HA, as well as the network host.

Figure 1-4 shows the PDSN-FA MIP configuration.

Figure 1-4 PDSN-FA MIP Configuration

MIP Reverse Tunnel - FA Nodal

When a user selects a test scenario requiring a MIP reverse tunnel - PDSN-FA nodal access model, the user configures the emulated nodes shown in Figure 1-5. In this configuration, the CPTS emulates the MN(s), a single or multiple PCF(s), the HA, and the network host.

Figure 1-5 shows the PDSN-FA MIP Reverse Tunnel configuration.



Figure 1-5 PDSN-FA MIP Reverse Tunnel Configuration

MIP VPN - FA Nodal

When a user selects a test scenario requiring a MIP VPN - PDSN-FA nodal access model, the user configures the emulated nodes shown in Figure 1-6. In this configuration, the CPTS emulates the MN(s), a single or multiple PCF(s), the HA, and the network host.

Figure 1-6 shows the PDSN-FA MIP VPN configuration.

Figure 1-6 PDSN-FA MIP VPN Configuration

MIP Network Based VPN - FA Nodal

When a user selects a test scenario requiring a MIP networked based VPN - PDSN-FA nodal access model, the user configures the emulated nodes shown in Figure 1-7. In this configuration, the CPTS emulates a single or multiple PCF(s), and the HA.

Test ConfigurationsHA Configurations


Figure 1-7 shows the PDSN-FA MIP Network Based VPN configuration.

Figure 1-7 PDSN-FA MIP Network Based VPN Configuration

HA Configurations

Mobile IP - HA Nodal

When a user selects a test scenario requiring a MIP - HA nodal access model, the user configures the emulated nodes shown in Figure 1-8. In this configuration, the CPTS emulates the MN(s), a single PDSN-FA, as well as the network host.

Figure 1-8 shows the HA MIP configuration.

Figure 1-8 HA MIP Configuration

Test ConfigurationsHA Configurations


MIP Reverse Tunnel

When a user selects a test scenario requiring a MIP Reverse Tunnel - HA nodal access model, the user configures the emulated nodes shown in Figure 1-9. In this configuration, the CPTS simulates the MN(s), a single PDSN-FA, and the network host.

Figure 1-9 shows the HA MIP Reverse Tunnel configuration.

Figure 1-9 HA MIP Reverse Tunnel Configuration

MIP VPN - HA Nodal

When a user selects a test scenario requiring a MIP VPN - HA nodal access model, the user configures the emulated nodes shown in Figure 1-10. In this configuration, the CPTS emulates the MN(s), a single PDSN-FA, and the network host.

Figure 1-10 shows the HA MIP VPN configuration.

Figure 1-10 HA MIP VPN Configuration

Test ConfigurationsEnd-to-End Test Configurations


MIP Network Based VPN - HA Nodal

When a user selects a test scenario requiring a MIP Network Based VPN - HA nodal access model, the user configures the emulated nodes shown in Figure 1-11. In this configuration, the CPTS emulates the MN(s), a single PDSN-FA, and the security gateway.

Figure 1-11 shows the HA MIP Network Based VPN configuration.

Figure 1-11 HA MIP Network Based VPN Configuration

End-to-End Test Configurations

MIP - End-to-End

When a user selects a test scenario requiring a MIP - End-to-End access model, the user configures the emulated nodes shown in Figure 1-12. In this configuration, the CPTS emulates the MN(s), a single or multiple PCF(s), as well as the network host.

Figure 1-12 shows the End-to-End MIP configuration.



Figure 1-12 End-to-End MIP Configuration

MIP Reverse Tunnel - End-to-End

When a user selects a test scenario requiring a MIP reverse tunnel End-to-End access model, the user configures the emulated nodes shown in Figure 1-13. In this configuration, the CPTS emulates the MN(s), a single or multiple PCF(s), and the network side interface.

Figure 1-13 shows the End-to-End MIP Reverse Tunnel configuration.

Figure 1-13 End-to-End MIP Reverse Tunnel Configuration

MIP VPN - End-to-End

When a user selects a test scenario requiring a MIP VPN - End-to-End access model, the user configures the emulated nodes shown in Figure 1-14. In this configuration, the CPTS emulates the MN(s), a single or multiple PCF(s), and the network side interface.

Figure 1-14 shows the End-to-End MIP VPN configuration.



Figure 1-14 End-to-End MIP VPN Configuration

MIP Network Based VPN - End-to-End

When a user selects a test scenario requiring a MIP Network Based VPN - End-to-End access model, the user configures the emulated nodes shown in Figure 1-15. In this configuration, the CPTS emulates the MN(s), a single or multiple PCF(s), and the network side interface.

Figure 1-15 shows the End-to-End MIP Network Based VPN configuration.

Figure 1-15 End-to-End MIP Network Based VPN Configuration


Chapter 2

Test Case Set Up

This chapter provides detailed information on the test case set up.

In this chapter...


Purpose....20

Simple IP Test Cases....20

Simple IP VPN Test Cases....24

FA Nodal Test Cases....28

HA Nodal Test Cases....34

End-to-End MIP Test Cases....38

Network Host Test Cases....42

Test Activities....45

Capacity Tests....45

Session Loading....47

Session Loading With Mobility....50

Session Loading Rate....54

Session Activation Rate....57

Intra-PDSN Handoff....60

Intra-PDSN Rate....64

MIP Revocation....68

Inter-PDSN....72

Inter-PDSN Handoff Rate....77

Data Verification....82

Continuous Data....85

SUT Query Options....88

Protocol Configuration Set Up....93

Test Case Set UpPurpose


PurposeThe CPTS provides a variety of test capabilities, including:

• Capacity tests

• Performance tests

• Traffic tests

• Soak tests

The basic building blocks for these test capabilities are the pre-packaged test cases found in the Basic test library. Each of these test cases is designed for specific test configurations:

• Simple IP

• Simple IP VPN

• FA Nodal

• HA Nodal

• End-to-End

The following sections describe how to use these test cases to perform a variety of testing.

Important: The CPTS User Guide is a prerequisite to this document. It contains detailed procedures for managing test cases, as well as creating and running testsessions.

Simple IP Test CasesThe purpose of the Simple IP test case is to test a single PDSN using the Simple IP access model. To create a test session for a Simple IP test configuration, the user first selects the Simple IP Test Case from the Basic library.

After selecting the Simple IP test case, a Resource Selector window opens as shown in Figure 2-1.

This is the starting point for setting up a variety of tests and allows the user to modify any of the parameters identified in “Simple IP Parameters” in Chapter 3.

A general description of this window is found in Table 2-1. Using the configurable parameters displayed, the user can create a variety of test sessions as described in the following paragraphs.

Test Case Set UpSimple IP Test Cases


Figure 2-1 Simple IP Resource Selector Window

Table 2-1 Simple IP Resource Selector Window

Item Description

Fields

Parameter Fields

The Resource Selector window displays a list of tabs. The tabs are dependent on the particular test case. Each tab contains parameter fields that can be modified for the selected test case. Many of these fields contain default values, and the test case can be used without modifying the default values. The test operator must enter those fields that do not contain a default value. For the Simple IP Test Case, the following tabs are displayed.

Tabs

General Provides access to the parameters described in “Simple IP Parameters” (Table 3-1) and “Common Parameters” (Table 3-6).

Test Activity Provide access to the parameters described in “Test Activity Configuration Parameters” (Table 3-8).



To create a Simple IP test session, follow the steps described in Procedure 2-1.

RP Provides access to the parameters described in “RP Protocol Configuration Parameters” (Table 3-20).

PPP Provides access to the parameters described in “PPP Protocol Configuration Parameters” (Table 3-21).

Data Traffic Provides access to the parameters described in “Data Traffic Parameters” (Table 3-22).

SUT Query Provides access to the parameters described in “SUT Query Configuration Parameters” (Table 3-7).

Buttons

Show Hidden Parameters

Allows the user to determine when parameters are displayed in the Resource Selector window. When Show Hidden Parameters is selected, all parameters are displayed with a checkbox to the left side of the parameter name. Those with a check in the box are hidden unless Show Hidden Parameters is selected. To hide a parameter from normal viewing, simply check the box next to the parameter name. To display a hidden parameter at all times, clear the checkbox.

View Measurements

Displays the test measurements that are collected for the selected test case. Refer to Chapter 4, “Test Case Measurements,” for a list of measurements associated with each basic test case.

Apply Applies any parameter changes to the selected test case.

Cancel Cancels the Resource Selector window.

Table 2-1 Simple IP Resource Selector Window (Continued)

Item Description

Procedure 2-1 Create Simple IP Test

1. Use the scroll bar on the right to navigate through the configurable parameters if necessary.

2. Select the General tab.

3. In the System Under Test (Foreign Agent) field, use the pull-down tab to select a pre-configured SUT to be tested.



4. In the Number of Sessions (1 – 200,000) field, enter the total number of sessions desired.

Tip: To test the full capacity of the SUT, this should be a number that exceeds the stated capacity of the SUT.

5. In the Session Connect Rate (Sessions/Second) field, enter the rate desired for establishing the sessions.

6. In the Session Disconnect Rate (Sessions/Second) field, enter the rate desired for session deactivations.

7. In the Session Rate Interval Distribution field, use the pull-down tab to select the desired distribution method. If Fixed is not selected, an additional parameter will be displayed that defines the boundaries of the distribution model. Set the Maximum Deviation from Mean if the Uniform or Poisson method was selected. Set the Standard Deviation if the Normal method was selected.

8. Select the Test Activity tab to configure the desired test activity as described in “Test Activities.”

The procedure for setting up any of the available test activities for a Simple IP test case are described in:• “Set Up Capacity Test” (Procedure 2-7)• “Set Up Session Loading Test” (Procedure 2-8)• “Set Up Session Loading Rate Test” (Procedure 2-10)• “Set Up Session Activation Rate Test” (Procedure 2-11)• “Set Up Intra-PDSN Handoff Test” (Procedure 2-12)• “Set Up Intra-PDSN Rate Test” (Procedure 2-13)• “Set Up Session Loading With Mobility Test” (Procedure 2-9)Note: When selecting an Intra-PDSN handoff test activity or an Intra-PDSN handoff rate test activity, you must also configure the parameters on the RP #2 tab. Refer to “Modify RP Protocol Parameters” (Procedure 2-22).

9. Select the RP tab to configure the RP parameters as described in “Modify RP Protocol Parameters” (Procedure 2-22).

10. Select the PPP tab to configure the PPP parameters as described in “Modify PPP Protocol Parameters” (Procedure 2-24).

11. Select the Data Traffic tab to configure the desired data traffic as described in “Set Up Data Verification” (Procedure 2-17) and “Set Up Continuous Data” (Procedure 2-18).

12. Select the SUT Query tab to configure the desired SUT Query as described in “Set Up SUT Query” (Procedure 2-19).

Procedure 2-1 Create Simple IP Test (Continued)

Test Case Set UpSimple IP VPN Test Cases


The measurements associated with the Simple IP test are defined in the following tables:

• “Test Summary Measurements” (Table 4-1)

• “RP Measurements” (Table 4-6)

• “PPP Measurements” (Table 4-7)

• “PCF Emulation Measurements” (Table 4-12).

Simple IP VPN Test CasesThe purpose of the Simple IP VPN test case is to test a single PDSN in a Simple IP VPN configuration. To build a test session for a Simple IP VPN test configuration, the user first selects the Simple IP VPN Test Case from the Basic library. After selecting the Simple IP VPN test case, a Resource Selector window opens as shown in Figure 2-2.

This is the starting point for setting up a variety of tests and allows the user to modify any of the parameters identified in “Simple IP VPN Parameters” in Chapter 3.

A general description of this window is found in Table 2-2. Using the configurable parameters displayed, the user can create a variety of test sessions as described in the following paragraphs.

13. Click Apply to use the configured parameters.

14. The test case may now be saved as a custom test case, saved as a test session or executed. Refer to the CPTS User Guide for more information.

Procedure 2-1 Create Simple IP Test (Continued)



Figure 2-2 Simple IP VPN Resource Selector Window

Table 2-2 Simple IP VPN Resource Selector Window

Item Description

Fields

Parameter Fields

The Resource Selector window displays a list of tabs. The tab names and number of tabs is dependent on the particular test case. Each tab contains parameter fields that can be modified for the selected test case. Many of these fields contain default values, and the test case can be used without modifying the default values. The test operator must enter those fields that do not contain a default value. For the Simple IP Test Case, the following tabs are displayed.

Tabs

General Provides access to the parameters described in “Simple IP Parameters” (Table 3-1) and “Common Parameters” (Table 3-6).

L2TP Provide access to the parameters described in “L2TP Protocol Configuration Parameters” (Table 3-19).



To create a Simple IP VPN test session follow the steps described in Procedure 2-2.




PPP/L2TP Provides access to the parameters described in “PPP Protocol Configuration Parameters” (Table 3-21).



Buttons



View Measurements

Displays the test measurements that are collected for the selected test case. Refer to the section on Chapter 4, “Test Case Measurements,” for a list of measurements associated with each basic test case.



Table 2-2 Simple IP VPN Resource Selector Window (Continued)

Item Description

Procedure 2-2 Create Simple IP VPN Test







Tip: To test the full capacity of the SUT, this should be a number that exceeds the stated capacity of the SUT.




8. Select the L2TP tab to configure the L2TP parameters as described in “Modify L2TP Protocol Parameters” (Procedure 2-23).


10. Select the PPP tab to configure the PPP parameters as described in “Modify PPP Protocol Parameters” (Procedure 2-24).

11. Select the PPP/L2TP tab to configure the PPP parameters as described in “Modify PPP Protocol Parameters” (Procedure 2-24).

Procedure 2-2 Create Simple IP VPN Test (Continued)

Test Case Set UpFA Nodal Test Cases


The measurements associated with the Simple IP VPN test are defined in the following tables:




• “L2TP Measurements” (Table 4-17)


FA Nodal Test CasesThe purpose of FA Nodal test cases is to test a PDSN-FA in a nodal configuration, where the CPTS emulates the HA node. To build a test session for an FA Nodal test configuration, the user first selects the FA Nodal Test Case from the Basic library. After selecting the FA Nodal test case, a Resource Selector window opens as shown in Figure 2-3. A general description of this window is found in Table 2-3.


The procedure for setting up any of the available test activities for a Simple IP VPN test case are described in:• “Set Up Capacity Test” (Procedure 2-7)• “Set Up Session Loading Test” (Procedure 2-8)• “Set Up Session Loading Rate Test” (Procedure 2-10)• “Set Up Session Activation Rate Test” (Procedure 2-11)• “Set Up Intra-PDSN Handoff Test” (Procedure 2-12)• “Set Up Intra-PDSN Rate Test” (Procedure 2-13)• “Set Up Session Loading With Mobility Test” (Procedure 2-9)Note: When selecting an Intra-PDSN handoff test activity or an Intra-PDSN handoff rate test activity, you must also configure the parameters on the RP #2 tab. Refer to “Modify RP Protocol Parameters” (Procedure 2-22).





Procedure 2-2 Create Simple IP VPN Test (Continued)



This is the starting point for setting up a variety of tests and allows the user to modify any of the parameters identified in “MIP FA Nodal Parameters” in Chapter 3. Using the configurable parameters displayed, the user can create a variety of test sessions as described in the following paragraphs.

Figure 2-3 FA Nodal Resource Selector Window



Table 2-3 FA Nodal Resource Selector Window

Item Description

Fields

Parameter Fields

The Resource Selector window displays a list of tabs. The tab names and number of tabs is dependent on the particular test case. Each tab contains parameter fields that can be modified for the selected test case. Many of these fields contain default values, and the test case can be used without modifying the default values. The test operator must enter those fields that do not contain a default value. For the FA Nodal Test Case, the following tabs are displayed.

Tabs

General Provides access to the parameters described in “MIP FA Nodal Parameters” (Table 3-3) and “Common Parameters” (Table 3-6).


MIP HA Provides access to the HA Home Address Pool and Subnet Mask fields as described in “MIP FA Nodal Parameters” (Table 3-3).



MIP Provides access to the parameters described in “MIP Parameters” (Table 3-23).



Buttons





To create a MIP FA Nodal test session, follow the steps described in Procedure 2-3.

View Measurements




Table 2-3 FA Nodal Resource Selector Window (Continued)

Item Description

Procedure 2-3 Create MIP FA Nodal Test




4. In the HA Node Address area, use the pull-down tab of the Physical Interface field to select the physical ethernet port to be used for the HA emulator.

5. In the IP Address field, enter the IP address of the emulated HA node. Note: This IP address must be selected from the pool of virtual addresses associated with the physical interface selected.

6. In the HA Node Address area, select Default Routing or Specify Next Hop IP Address.

7. If Specify Next Hop IP Address is selected, enter the IP address of the router to be used for the next hop in the IP Address field.

8. In the HA Node Port Number field, enter the desired port number for the HA Node.







13. Select the MIP HA tab to configure the HA Home Address Pool field and Subnet Mask field as described in the following two steps.

14. In the HA Home Address Pool field, enter the starting IP address to be used for the MIP sessions’ Home Address. Note: Each session is given a unique Home Address IP address starting with the IP address entered by incrementing the value entered for each session.

15. In the Subnet Mask field, enter the subnet mask for the HA Home IP Address.Note: The subnet must be large enough to accommodate the total number of sessions specified in the General tab.


17. Select the PPP tab to configure the PPP parameters as described in “Create Simple IP Test” (Procedure 2-1).

18. Select the MIP tab and select the MIP protocol parameters as described in “Modify MIP Protocol Parameters” (Procedure 2-20).


Note: The procedure for setting up any of the available test activities for an FA nodal test case are described in:• “Set Up Capacity Test” (Procedure 2-7)• “Set Up Session Loading Test” (Procedure 2-8)• “Set Up Session Loading With Mobility Test” (Procedure 2-9)• “Set Up Session Loading Rate Test” (Procedure 2-10)• “Set Up Session Activation Rate Test” (Procedure 2-11)• “Set Up Intra-PDSN Handoff Test” (Procedure 2-12)• “Set Up Intra-PDSN Rate Test” (Procedure 2-13)• “Set Up MIP Revocation Test” (Procedure 2-14)Note: When selecting an Intra-PDSN handoff test activity or an Intra-PDSN handoff rate test activity, you must also configure the parameters on the RP #2 tab. Refer to “Modify RP Protocol Parameters” (Procedure 2-22).

Procedure 2-3 Create MIP FA Nodal Test (Continued)

Test Case Set UpHA Nodal Test Cases


The measurements associated with the MIP FA Nodal Test are defined in the following tables:




• “Mobile IP Measurements” (Table 4-8)

• “HA Emulation Measurements” (Table 4-11)


HA Nodal Test CasesThe purpose of HA Nodal test case is to test an HA node in a nodal configuration, where the CPTS emulates the PDSN-FA node. To build a test session for a HA Nodal test configuration, the user first selects the HA Nodal test case from the Basic library. (Refer to the CPTS User Guide for more information.) After selecting the HA Nodal Test Case, a Resource Selector window opens as shown in Figure 2-4. A general description of this window is found in Table 2-4.

This is the starting point for setting up a variety of tests and allows the user to modify any of the parameters identified in “MIP HA Nodal Parameters” in Chapter 3.





Procedure 2-3 Create MIP FA Nodal Test (Continued)



Figure 2-4 HA Nodal Resource Selector Window



Table 2-4 HA Nodal Resource Selector Window

Item Description

Fields

Parameter Fields

The Resource Selector window displays a list of tabs. The tab names and number of tabs is dependent on the particular test case. Each tab contains parameter fields that can be modified for the selected test case. Many of these fields contain default values, and the test case can be used without modifying the default values. The test operator must enter those fields that do not contain a default value. For the HA Nodal Test Case, the following tabs are displayed.

Tabs

General Provides access to the parameters described in “MIP HA Nodal Parameters” (Table 3-4) and “Common Parameters” (Table 3-6).





Buttons



View Measurements






To create a test session for a HA Nodal configuration, follow the steps described in Procedure 2-4.

Procedure 2-4 Create HA Nodal Test



3. In the System Under Test (Home Agent) IP field, use the pull-down tab to select a pre-configured SUT to be tested.

4. In the Foreign Agent Node Address area, use the pull-down tab of the Physical Interface field, to select the physical ethernet port to be used for the PDSN-FA emulator.

5. In the IP Address field, enter the IP address of the emulated PDSN-FA Node. Note: This IP address must be selected from the pool of addresses associated with the physical interface selected.

6. In the Foreign Agent Node Address area, select Default Routing or Specify Next Hop IP Address.


8. In the Foreign Agent Node Port Number field, enter the desired port number for the PDSN-FA Node.






Test Case Set UpEnd-to-End MIP Test Cases


The measurements associated with the a HA Nodal test are defined in the following tables:



• “FA Emulation Measurements” (Table 4-10).

End-to-End MIP Test CasesThe purpose of End-to-End test cases is to test two SUTs in a PDSN-FA and a HA node configuration. To build a test session for an End-to-End test configuration, the user first selects the End-to-End Mobile IP test case from the Basic library. (Refer to the CPTS User Guide for more information.) After selecting the End-to-End Mobile IP test case, a Resource Selector window opens as shown in Figure 2-5. This is the starting point for setting up a variety of tests and allows the user to modify any of the parameters identified in “End-to-End Mobile IP Parameters” in Chapter 3.


Note: The procedure for setting up any of the available test activities for a HA nodal test case are described in:• “Set Up Capacity Test” (Procedure 2-7)• “Set Up Session Loading Test” (Procedure 2-8)• “Set Up Session Loading Rate Test” (Procedure 2-10)• “Set Up Session Activation Rate Test” (Procedure 2-11)• “Set Up Inter-PDSN Test” (Procedure 2-15)• “Set Up Inter-PDSN Handoff Rate Test” (Procedure 2-16)• “Set Up MIP Revocation Test” (Procedure 2-14)• “Set Up Session Loading With Mobility Test” (Procedure 2-9)Note: When selecting an Inter-PDSN handoff test activity or an Inter-PDSN handoff rate test activity, you must also configure the parameters on the RP #2 tab. Refer to “Modify RP Protocol Parameters” (Procedure 2-22).



17. Click Apply to use the selected configuration.

18. The test case may now be saved as a custom test case, saved as a test session or executed. (Refer to the CPTS User Guide for more information.)

Procedure 2-4 Create HA Nodal Test (Continued)



A general description of this window is found in Table 2-5.

Figure 2-5 MIP End-to-End Resource Selector Window



Table 2-5 MIP End-to-End Resource Selector Window

Item Description

Fields

Parameter Fields

The Resource Selector window displays a list of tabs. The tab names and number of tabs is dependent on the particular test case. Each tab contains parameter fields that can be modified for the selected test case. Many of these fields contain default values, and the test case can be used without modifying the default values. The test operator must enter those fields that do not contain a default value. For the End-to-End Test Case, the following tabs are displayed.

Tabs

General Provides access to the parameters described in “MIP End-to-End Parameters” (Table 3-5) and “Common Parameters” (Table 3-6).




Test Activity Provide access to the parameters described in “Test Activity Configuration Parameters” (Table 3-8)



Buttons





To create a test session for an end-to-end test configuration, follow the steps described in Procedure 2-5.

View Measurements




Table 2-5 MIP End-to-End Resource Selector Window (Continued)

Item Description

Procedure 2-5 Create MIP End-to-End Test



3. In the System Under Test (Foreign Agent) field, use the pull-down tab to select a pre-configured SUT to be tested as the PDSN-FA.

4. In the System Under Test (Home Agent) field, use the pull-down tab to select a pre-configured SUT to be tested as the HA.

5. In the SUT HA Port Number field, enter the port number to be used for the SUT HA.

6. In the Secondary Home Agent field, use the pull-down tab to select Enabled or Disabled.

7. If Secondary Home Agent is set to Enabled, use the pull-down tab in the System Under Test (Home Agent #2) field, select the pre-configured SUT for the second HA.






The measurements associated with the MIP End-to-End test case are defined in the following tables:





13. Select the Test Activity tab to configure the desired test activity as described in “Test Activities”

Note: The procedure for setting up any of the available test activities for an end-to-end test case are described in:• “Set Up Capacity Test” (Procedure 2-7)• “Set Up Session Loading Test” (Procedure 2-8)• “Set Up Session Loading Rate Test” (Procedure 2-10)• “Set Up Session Activation Rate Test” (Procedure 2-11)• “Set Up Intra-PDSN Handoff Test” (Procedure 2-12)• “Set Up Intra-PDSN Rate Test” (Procedure 2-13)• “Set Up Inter-PDSN Test” (Procedure 2-15)• “Set Up Inter-PDSN Handoff Rate Test” (Procedure 2-16)Note: When selecting an Intra-PDSN or Inter-PDSN handoff test activity or an Intra-PDSN or Inter-PDSN handoff rate test activity, you must also configure the parameters on the RP #2 tab. Refer to “Modify RP Protocol Parameters” (Procedure 2-22).





Procedure 2-5 Create MIP End-to-End Test (Continued)

Test Case Set UpNetwork Host Test Cases





Network Host Test CasesThe purpose of the Network Host test case is to provide an emulated network host in another test case, in another test session, or on a remote test server. This test case would be used on another test server when the user wants to configure a test case that maximizes the amount and rate of the data traffic sent to the mobile node by using the full capacity of a test server to generate the traffic.

To build a test session using a remote network host, the user can include this test case in the same test session as the data test, or in a new test session, by selecting the Network Host Test Case from the Basic library. (Refer to the CPTS User Guide for more information.) After selecting the Network Host Test Case, a Resource Selector window opens as shown in Figure 2-6.

When the emulated network host is local to the test server performing the data test, the host is normally defined as part of the data test. Refer to “Data Verification” and “Continuous Data.”

A general description of this window is found in Table 2-6.

Figure 2-6 Network Host Resource Selector Window



To create a test session for using a remote network host, follow the steps described in Procedure 2-6.

Table 2-6 Network Host Resource Selector Window

Item Description

Fields

Parameter Fields

The Resource Selector window displays a list of tabs. The tab names and number of tabs is dependent on the particular test case. Each tab contains parameter fields that can be modified for the selected test case. Many of these fields contain default values, and the test case can be used without modifying the default values. The test operator must enter those fields that do not contain a default value. For the Network Host Test Case, the following tabs are displayed.

Tabs

General Provides access to the parameters for setting up the network host IP addressing.

Data Traffic Provides access to the parameters for setting up the type of data to be processed by the network host.

Buttons



View Measurements






Procedure 2-6 Create Network Host Test



3. In the Network Host Node Address area, use the pull-down tab of the Physical Interface field, to select the physical ethernet port to be used for the network host emulator.

4. In the adjacent IP Address field, enter the IP address of the emulated network host node. Note: This IP address must be selected from the pool of addresses associated with the physical interface selected.

5. In the Network Host Node Address area, select Default Routing or Specify Next Hop IP Address.


7. In the Number of Sessions field, enter the maximum number of simultaneous sessions that the network host will be required to handle.

8. Select the Data Traffic tab.Note: Refer to “Data Traffic Parameters” (Table 3-22) for the definition of the data specific parameters.

9. In the Payload Data Size area, configure the data parameters as desired to achieve the specific response packet size or data rate desired.

10. In the Packet Interval Distribution field, use the pull-down tab to select the desired distribution method. If Fixed is not selected, an additional parameter will be displayed that defines the boundaries of the distribution model. Set the Maximum Deviation from Mean if the Uniform or Poisson method was selected. Set the Standard Deviation if the Normal method was selected.

11. In the Packet Size Distribution field, use the pull-down tab to select the desired distribution method. If Fixed is not selected, an additional parameter will be displayed that defines the boundaries of the distribution model. Set the Maximum Deviation from Mean if the Uniform or Poisson method was selected. Set the Standard Deviation if the Normal method was selected.

12. In the Type of Service field, enter the type of service value desired.

13. In the Time to Live field, enter the desired time to live value.

Test Case Set UpTest Activities


The measurements associated with the Network Host test are defined in “Network Host Measurements” (Table 4-13).

Test ActivitiesThe CPTS provides the flexibility to provide a variety of test activities in a variety of test configurations. Each configuration is described in detail in Chapter 1, “Test Configurations.” The following paragraphs provide an overview of the various test activities that can be performed using the CPTS. Each of the test activities described below are available for selection from the Test Activity tab which appears when a specific test case has been selected. The procedures contained below only deal with the configuration parameters associated with specific test activities. For detailed information on overall test setup, refer to “Test Case Set Up” for the specific test case.

Capacity TestsA key measurement of a PDSN’s capability is its capacity for simultaneous sessions. The CPTS provides Capacity tests for all test configurations and access models.

For all of the Capacity tests, the CPTS begins establishing sessions at a rate specified by the user. This should be a rate less than the maximum session rate supported by the system under test. The TS continues to establish sessions until the number of sessions specified by the user has been reached or the user stops the test. Once the capacity of the PDSN has been reached, all subsequent session activation attempts fail. By setting the requested number of sessions higher than the supported capacity of the PDSN, the user can determine the actual capacity.

14. In the Protocol field, use the pull-down tab to select the desired data type. The options are HTTP, FTP, WAP, SMTP, RAW, PING (ICMP) UDP, and TCP.Note: This selection must be the same as selected for the corresponding test case emulating the mobile node.

15. Configure the parameters associated with the specific data type selected to mirror the parameters used in the test case that will be sending traffic to the network host.



Procedure 2-6 Create Network Host Test (Continued)

Test Case Set UpCapacity Tests


If all sessions are established successfully, the test server keeps all sessions active for the length of the specified duration or until stopped, and then begins deactivating each of the sessions at the specified disconnect rate.

Capacity Test Set Up

A Capacity test activity is set up from the Test Activity tab of a selected test case as shown in Figure 2-7. The configurable parameters for a Capacity test activity are briefly described in Table 2-7. More detailed parameter definitions can be found in “Capacity Parameters” in Chapter 3.

Figure 2-7 Capacity Resource Selector Window

To create a test session for measuring a PDSN’s session capacity, follow the steps described in Procedure 2-7.

Table 2-7 Capacity Resource Selector Window

Item Description

Fields

Test Activity Pull-down menu to select a desired test activity.Note: The Capacity test activity is available in all test cases.

Session Start Retries

Options are Enabled or Disabled. Enabled indicates that the test case retries session activations if they are unsuccessful.

Disconnect Initiated By

Determines the originator of the session disconnect. The options are Mobile Node, PCF, and Mobile Node PPP.

Test Case Set UpSession Loading


Measurements associated with the Capacity test activity are defined in “Test Summary Measurements” (Table 4-1).

Capacity Test Options

There are several options available to the user during the setup of the Capacity test as described in the following paragraphs.

Capacity Test with SUT Query

The user has the option of enabling a SUT Query during the Capacity test. Refer to “SUT Query Options.”

Session Verification

The user has an option of enabling data traffic during the Capacity test. Refer to “Data Verification.”

Continuous Data

The user has the option of enabling continuous data traffic during the Capacity test. The selected data type is transmitted continuously while the sessions are active. Refer to “Continuous Data.”

Session LoadingA key test of a PDSN’s performance is its ability to process real-world activity for a long period of time. Session Loading allows the user to emulate real-world activity so that the PDSN is handling multiple events, such as session activations, and session deactivations at the same time.

Procedure 2-7 Set Up Capacity Test

1. Select the Test Activity tab on the Resource Selector window.

2. The Test Activity field has a default entry of Capacity. Note: If this is a saved test case that is being modified, use the pull-down tab to select Capacity.

3. In the Session Start Retries field, select Enabled or Disabled. If Enabled is selected, the test case retries all failed test session activations.

4. In the Session Disconnect Initiated By field, use the pull-down tab to select the source of the session deactivation, either the Mobile Node, the PCF, or the Mobile Node PPP layer.



During the Session Loading test activity, the test case begins setting up sessions at a selected rate of activations per second. Each session is maintained for the specified session hold time. At that time, the session is deactivated and left idle for the specified session pending, or idle, time and then is reactivated. The test continues in this manner through the specified duration period or until the test is stopped.

This results in session activations and deactivations occurring in a real-world model. To further reflect real-world conditions, the user may enable data traffic during the session hold time and use distribution models to vary session and bearer traffic rates.

Session Loading Set Up

A Session Loading test activity is set up from the Test Activity tab of a selected test case as shown in Figure 2-8. The configurable parameters for a Session Loading test activity are briefly described in Table 2-8. More detailed parameter definitions can be found in “Session Loading Parameters” in Chapter 3.

Figure 2-8 Session Loading Resource Selector Window

Table 2-8 Session Loading Resource Selector Window

Item Description

Fields

Test Activity Pull-down menu to select a desired test activity.Note: The Session Loading test activity is available in all test cases.



To create a test session for performing session loading, follow the steps described in Procedure 2-8.

Measurements associated with the Session Loading test activity are defined in “Test Summary Measurements” (Table 4-1).

Session Loading Options

There are several options available to the user during the setup of the Session Loading test as described in the following paragraphs.

Session Loading with SUT Query

The user has the option of enabling a SUT Query during the Session Loading test. Refer to “SUT Query Options.”


The user has an option of enabling data traffic during the Session Loading test. Refer to “Data Verification.”

Session Pending Time (Seconds) (1 - 100000)

Specifies the number of seconds that the session is idle before the next activation.

Session Hold Time (Seconds) (1 - 100000)

Specifies the number of seconds the session is active.

Table 2-8 Session Loading Resource Selector Window (Continued)

Item Description

Procedure 2-8 Set Up Session Loading Test


2. In the Test Activity field, use the pull-down tab to select Session Loading.

3. In the Session Pending Time field, enter the number of seconds the session should be idle following a deactivation.

4. In the Session Hold Time field, enter the number of seconds the session should be active, following activation.

Test Case Set UpSession Loading With Mobility


Continuous Data

The user has the option of enabling continuous data traffic during the Session Loading test. The selected data type is transmitted continuously during the session hold interval. Refer to “Continuous Data.”

Session Loading With MobilitySession Loading With Mobility allows the user to emulate real-world activity so that the PDSN is handling multiple events, such as session activations and deactivations, with the addition of handoffs at the same time.

During the Session Loading With Mobility test activity, the test case begins setting up sessions at a selected rate of activations per second. Each session is maintained for the specified session hold time. After session activation, the test waits the specified handoff time, and then performs the specified number of handoffs. At end of the specified session hold time, the session is deactivated and left idle for the specified session pending, or idle, time and then is reactivated. The test continues in this manner for the specified duration or until the test is stopped.

This results in session activations, deactivations, and handoffs occurring in a real-world model. To further reflect real-world conditions, the user may enable data traffic during the session hold time and use distribution models to vary session and bearer traffic rates.

Session Loading With Mobility Set Up

A Session Loading With Mobility test activity is set up from the Test Activity tab of a selected test case as shown in Figure 2-9. The configurable parameters for a Session Loading With Mobility test activity are briefly described in Table 2-9. More detailed parameter definitions can be found in “Session Loading with Mobility Parameters” in Chapter 3.



Figure 2-9 Session Loading With Mobility Resource Selector Window

Table 2-9 Session Loading With Mobility Resource Selector Window

Item Description

Fields

Test Activity Pull-down menu to select a desired test activity.Note: The Session Loading With Mobility test activity is available in all test cases.



To create a test session for Session Loading With Mobility, follow the steps described in Procedure 2-9.

Session Pending Time (Seconds) (1 - 10000)

Specifies the number of seconds that the session is idle before the next activation.

Session Hold Time (Seconds) (1 - 10000)

Specifies the number of seconds the session is active.

Handoff Time (Seconds)

The length of time after a session activation that the handoff event occurs.

Number of Handoffs

The number of handoff events to perform for each session activation.

Mobility Type Identifies the type of mobility event. The options available depend on the test configuration. For a Simple IP test case and an FA Nodal test case, Intra-PDSN is the only option. For an HA nodal test case, Inter-PDSN is the only option. For an end-to-end test case both Intra-PDSN and Inter-PDSN are options.

System Under Test #2 (Foreign Agent)

Conditional on Inter-PDSN selected for Mobility Type in an end-to-end test case. Use the pull-down tab to select a second pre-configured SUT.

Foreign Agent Node Address #2

Conditional on Inter-PDSN selected for Mobility Type in an HA nodal test case. Area for entering the physical interface and logical IP address for the second PDSN-FA node emulator.

Foreign Agent #2 Port Number

Conditional on Inter-PDSN selected for Mobility Type in an HA Nodal test case. Field for entering the desired port number of the second emulated PDSN-FA node.

Table 2-9 Session Loading With Mobility Resource Selector Window (Continued)

Item Description

Procedure 2-9 Set Up Session Loading With Mobility Test


2. In the Test Activity field, use the pull-down tab to select Session Loading With Mobility.



Measurements associated with the Session Loading With Mobility test activity are defined in “Test Summary Measurements” (Table 4-1) and “Test Summary Measurements for Mobility Testing” (Table 4-3).

Session Loading With Mobility Options

There are several options available to the user during the setup of the Session Loading With Mobility test as described in the following paragraphs.

SUT Query

The user has the option of enabling a SUT Query during the Session Loading With Mobility test. Refer to “SUT Query Options.”


The user has an option of enabling data traffic during the Session Loading With Mobility test. Refer to “Data Verification.”

3. In the Session Pending Time field, enter the number of seconds the session should be idle following a deactivation.

4. In the Session Hold Time field, enter the number of seconds the session should be kept active following an activation.

5. In the Handoff Time field, enter the amount of time the test should wait, following session activation, before performing the handoff event. This is also used as the delay value between handoffs if multiple handoffs are specified.

6. In the Number of Handoffs field, enter the desired number of handoffs to be performed on each active session during the sessions hold time.

7. In the Mobility Type field, use the pull-down menu to select the desired Mobility Type. The options are Intra-PDSN and Inter-PDSN. For a Simple IP test case and an FA Nodal test case, Intra-PDSN is the only option. For an HA Nodal test case, Inter-PDSN is the only option. For an End-to-End MIP test case both Intra-PDSN and Inter-PDSN are options.

8. If Inter-PDSN is selected, a second PDSN-FA must be identified. In an end-to-end test case, use the pull-down tab in the System Under Test (Foreign Agent) #2 field, to select a second pre-configured SUT. In an HA Nodal case, enter the IP address information for the emulated second PDSN-FA node in the Foreign Agent Node Address #2 area.

Procedure 2-9 Set Up Session Loading With Mobility Test (Continued)

Test Case Set UpSession Loading Rate


Continuous Data

The user has the option of enabling continuous data traffic during the Session Loading With Mobility test. The selected data type is transmitted continuously during the session hold interval. Refer to “Continuous Data.”

Session Loading RateThe purpose of the Session Loading Rate test is to determine the maximum processing rate of the PDSN. It works similar to the Session Loading test activity, with the difference being that the Session Loading Rate test continues to increase the rate of sessions until a user-defined error threshold is exceeded.

During the Session Loading Rate test activity, the test case begins setting up sessions at a selected rate of activations per second for a user-defined session loading time. The sessions are maintained for the specified session hold time. At that time, the session is deactivated and left idle for the specified session pending, or idle, time and then is reactivated.

The test continues in this manner until the selected session loading time expires. At that time, the CPTS examines the error rate, and determines whether the error threshold has been exceeded. If the error rate is not exceeded, the test decreases the hold and pending times by their respective adjustment values, and runs the test again for the specified session loading time.

Once the error threshold has been exceeded, the test continues to run at the same rate until stopped or until the error percentage drops below the threshold. Should the session loading run time expire while the error percentage is below the error threshold, the session hold and pending times are decreased again.

Session Loading Rate Set Up

A Session Loading Rate test activity is set up from the Test Activity tab of a selected test case as shown in Figure 2-10. The configurable parameters for a Session Loading Rate test activity are briefly described in Table 2-10. More detailed parameter definitions can be found in “Session Loading Rate Parameters” in Chapter 3.



Figure 2-10 Session Loading Rate Resource Selector Window

Table 2-10 Session Loading Rate Resource Selector Window

Item Description

Fields

Test Activity Pull-down menu to select a desired test activity.Note: The Session Loading Rate test activity is available in all test cases.

Initial Pending Time (Seconds) (1 - 100)

Specifies the initial number of seconds that the session is idle before the next activation. This value is adjusted automatically by the Pending Backoff Amount, if the test does not exceed the error threshold.



To create a test session using the Session Loading Rate test activity, follow the steps described in Procedure 2-10.

Initial Hold Time (Seconds) (1 - 100)

Specifies the initial number of seconds the session is active. This value is adjusted automatically by the Hold Backoff Amount, if the test does not exceed the error threshold.

Pending Backoff Amount (Seconds) (1 - 100)

Specifies the amount of time to reduce the current pending time, if the error threshold has not been exceeded.

Hold Backoff Amount (Seconds) (1 - 100)

Specifies the amount of time to reduce the current hold time, if the error threshold has not been exceeded.

Session Loading Time (Seconds) (1 - 1000)

This specifies the amount of time to run the session loading activity before checking the error threshold and making adjustments to the hold and pending times.

Important: This value should be a minimum of 10 times the Initial Hold Pending Time for best results.

Error Threshold Percentage (1 - 99)

Specifies the error threshold in terms of percentage of errors in relation to the number of successful sessions.

Table 2-10 Session Loading Rate Resource Selector Window (Continued)

Item Description

Procedure 2-10 Set Up Session Loading Rate Test


2. In the Test Activity field, use the pull-down tab to select Session Loading Rate.

3. In the Initial Pending Time field, enter the initial number of seconds the session should be idle following a deactivation.

4. In the Initial Hold Time field, enter the initial number of seconds the session should be active, following activation.

Test Case Set UpSession Activation Rate


Measurements associated with the Session Loading Rate test activity are defined in “Test Summary Measurements” (Table 4-1) and “Rate Test Measurements” (Table 4-19).

Session Loading Rate Options

Other test options are not recommended during a Session Loading Rate test. Other activities may invalidate the test results due to increased CPU utilization on the SUT. The purpose of rate tests is to measure the maximum rates with no other activity present.

Session Activation RateThe purpose of the Session Activation Rate test is to determine the maximum activation rate of the PDSN at various capacity levels. It is designed to determine if the SUT’s maximum activation rate varies dependent on the total number of sessions active.

During the Session Activation Rate test activity, the test case begins setting up sessions at a selected rate of activations per second for a user-defined time period or for a specified block of sessions. At the end of the time period, or once the block of sessions has been activated, the test checks to see if the error threshold has been exceeded. If not, the test initiates another activation run and activates the next block of sessions or activates sessions for a timed run.

If the error threshold is exceeded, the test deactivates the last set of sessions, decreases the activation rate by the specified back off percentage, and repeats the round of activations at the lower rate. Once that round has completed at a rate that does not exceed the error threshold, the test continues with the next round of activations.

5. In the Pending Backoff Amount field, enter the number of seconds that is used to reduce the current pending time, following a successful session loading time period.

6. In the Hold Backoff Amount field, enter the number of seconds that is used to reduce the current hold time, following a successful session loading time period.

7. In the Session Loading Time field, enter the duration in number of seconds for each Session Loading period.

Important: This value should be at least 10 times the value of the combined Initial Pending Time and Initial Hold Time for best results.

8. In the Error Threshold Percentage field, enter the desired error threshold.

Procedure 2-10 Set Up Session Loading Rate Test (Continued)



Session Activation Rate Set Up

A Session Activation Rate test activity is set up from the Test Activity tab of a selected test case as shown in Figure 2-11. The configurable parameters for a Session Activation Rate test activity are briefly described in Table 2-11. More detailed parameter definitions can be found in “Session Activation Rate Parameters” in Chapter 3.

Figure 2-11 Session Activation Rate Resource Selector Window

Table 2-11 Session Activation Rate Resource Selector Window

Item Description

Fields

Test Activity Pull-down menu to select a desired test activity.Note: The Session Activation Rate test activity is available in all test cases.



To create a test session using the Session Activation Rate test activity, follow the steps described in Procedure 2-11.

Activation Method

Selects the method to be used for determining the activation period. The options are By block or By time. If By block is selected, the activation rate test performs the test on a block by block basis, for the specified block size. If By time is selected, the activation rate test performs the test based on a time period basis, based on the specified time.

Block Size (1 - 200,000)

Contingent on By block selected for Activation Method. Specifies the block size in number of sessions. All sessions in the block will be activated before checking the error threshold.

When By time is selected, the Time Period parameter is displayed, which specifies the amount of time the activation rate test runs before checking the error threshold. The number of sessions established during each time period will be dependent on the activation rate specified in the General tab.


Specifies the error threshold in terms of percentage of errors in relation to the number of successful activations.

Wait Time (Seconds) (1 - 100)

Specifies the amount of time to wait before starting the next round of activations.

Backoff Rate (Percent) (1 - 100)

Specifies the amount by which the activation rate is decreased if the error threshold is exceeded.

Table 2-11 Session Activation Rate Resource Selector Window (Continued)

Item Description

Procedure 2-11 Set Up Session Activation Rate Test


2. In the Test Activity field, use the pull-down tab to select Session Activation Rate.

3. In the Activation Method field, use the pull-down tab to select By block or By time.

Test Case Set UpIntra-PDSN Handoff


Measurements associated with the Session Activation Rate test activity are defined in “Rate Test Measurements” (Table 4-19).

Session Activation Rate Options

Other test options are not recommended during a Session Activation Rate test. Other activities may invalidate the test results due to increased CPU utilization on the SUT. The purpose of rate tests is to measure the maximum rates with no other activity present.

Intra-PDSN HandoffThe purpose of the Intra-PDSN handoff test activity is to determine the PDSN’s ability to process handoffs from one simulated PCF to another simulated PCF. By running an Intra-PDSN handoff test at various capacity levels and various handoff rates, the user can determine the maximum handoff rate supported at various capacity levels.

During the Intra-PDSN handoff test activity, the test case begins setting up sessions at a selected rate of activations per second until the total number of activations is achieved.

If the user selects When Session Started, for the Mobility Start Type, the test waits for a specified time and then performs a handoff for each session as it is activated. If When Session Started is selected, the user also has the option selecting either Single Handoff or Continuous Handoff. If Single Handoff is selected, the test will perform one handoff for each session as it is established. If Continuous Handoff is selected, the test will perform continuous handoffs for each session, waiting for the specified time between handoffs.

If the user selects When All Sessions Started, for the Mobility Start Type, the test waits for the specified time after all sessions are active before performing handoffs for all active sessions based on the specified handoff rate. In this mode, a distribution model can be applied to the handoff rate, or it can remain fixed throughout the test. After all active sessions have been handed off, the test then begins handing back all of the sessions. This continues until the test is stopped or the specified test duration is reached.

4. If By block was selected as the Activation Method, then enter the desired block size in the Block Size field.

If By time was selected as the Activation Method, then enter the desired time for each run in the Time Period field.


6. In the Wait Time field, enter the amount of time the test waits before beginning the next round.

7. In the Backoff Rate field, enter the percentage to be used to reduce the activation rate when the error threshold is exceeded.

Procedure 2-11 Set Up Session Activation Rate Test (Continued)



Intra-PDSN Handoff Set Up

An Intra-PDSN handoff test activity is set up from the Test Activity tab of a selected test case as shown in Figure 2-12. The configurable parameters for an Intra-PDSN handoff test activity are briefly described in Table 2-12. More detailed parameter definitions can be found in “Intra-PDSN Parameters” in Chapter 3.

Figure 2-12 Intra-PDSN Handoff Resource Selector Window

Table 2-12 Intra-PDSN Handoff Resource Selector Window

Item Description

Fields

Test Activity Pull-down menu to select a desired test activity.Note: The Intra-PDSN test activity is not available in HA Nodal test cases.

Mobility Delay Time (Seconds) (1 - 100000)

Specifies the amount of time to wait following a session activation, or following activation of all sessions, before performing a handoff.



To create a test session using the Intra-PDSN test activity, follow the steps described in Procedure 2-12.

Mobility Start Type

Specifies whether the handoff events should occur as each session is established, When Session Started, or after all sessions are established, When All Sessions Started.

Mobility Rate (Sessions/Second) (0 - 1000)

Conditional on When All Sessions Started as the Mobility Start Type. Specifies the rate in handoffs per second to be used once all sessions have been established.

Mobility Rate Interval Distribution

Conditional on When All Sessions Started selected as Mobility Start Type. Selects the distribution method to be applied to the Mobility Rate. The options are Fixed, Uniform, Normal, and Poisson.

Maximum Deviation from Mean (Percent of Mean) (1 - 99)

Conditional on Uniform, or Poisson selected as Mobility Rate Interval Distribution. Limits the standard deviation in the selected distribution model to a percentage of the mean.

When Normal is selected, the Standard Deviation parameter is displayed, which sets the standard deviation as a percentage of the mean.

Handoff Mode Conditional on When Session Started selected as Mobility Start Type. Selects either a single handoff per session, or continuous handoffs. The options are Single Handoff or Continuous Handoff.

Table 2-12 Intra-PDSN Handoff Resource Selector Window (Continued)

Item Description

Procedure 2-12 Set Up Intra-PDSN Handoff Test


2. In the Test Activity field, use the pull-down tab to select Intra-PDSN.

3. In the Mobility Delay Time field, enter the amount of time to wait before initiating handoffs.

4. In the Mobility Start Type field, use the pull-down tab to select When All Sessions Started or When Session Started.



Measurements associated with the Intra-PDSN handoff test activity are defined in “Test Summary Measurements for Mobility Testing” (Table 4-3).

Intra-PDSN Handoff Options

There are several options available to the user during the setup of the Intra-PDSN handoff test as described in the following paragraphs.

SUT Query

The user has the option of enabling a SUT Query during the Intra-PDSN handoff test. Refer to “SUT Query Options.”


The user has an option of enabling data traffic during the Intra-PDSN handoff test. Refer to “Data Verification.”

Continuous Data

The user has the option of enabling continuous data traffic during the Intra-PDSN handoff test. The selected data type is transmitted continuously during the session activated interval. Refer to “Continuous Data.”

5. If When All Sessions Started was selected as the Mobility Start Type:• Enter the desired rate in the Mobility Rate field.• In the Mobility Rate Interval Distribution field, use the pull-down tab to

select the desired distribution method. If Fixed is not selected, an additional parameter will be displayed that defines the boundaries of the distribution model. Set the Maximum Deviation from Mean if the Uniform or Pois-son method was selected. Set the Standard Deviation if the Normal method was selected.

If When Session Started was selected as the Mobility Start Type, use the pull-down tab in the Handoff Mode field to select Single Handoff or Continuous Handoff.

6. Select the RP #2 tab, and configure the parameters for the second PCF emulator as described in “Modify RP Protocol Parameters” (Procedure 2-22)

Procedure 2-12 Set Up Intra-PDSN Handoff Test (Continued)

Test Case Set UpIntra-PDSN Rate


Intra-PDSN RateThe purpose of the Intra-PDSN handoff rate test activity is to determine the rate at which a PDSN can accept handoffs from one simulated PCF to another simulated PCF at various capacity levels. It is designed to determine whether a PDSN’s maximum handoff rate varies depending on the total number of active sessions.

During the Intra-PDSN handoff rate test activity, the test case first activates the total number of sessions requested between PCF #1 and the PDSN-FA. After waiting the specified delay time, the test begins handing off sessions, from PCF #1 to PCF #2, at a selected rate of activations per second for the specified time period or for a specified block of sessions. At the end of the time period, or once the block of sessions has been handed off, the test checks to see if the error threshold has been exceeded. If it has not, the test will handoff the next block of sessions or will handoff sessions for the specified time period.

If the error threshold is exceeded, the test will hand back the last block of sessions, decrease the handoff rate by the specified back off percentage, and handoff that block at the lower rate. Once that block has been handed off at a rate that does not exceed the error threshold, the test continues with the next block or time period.

Intra-PDSN Rate Set Up

An Intra-PDSN handoff rate test activity is set up from the Test Activity tab of a selected test case as shown in Figure 2-16. The configurable parameters for an Intra-PDSN handoff rate test activity are briefly described in Table 2-16. More detailed parameter definitions can be found in “Intra-PDSN Rate Parameters” in Chapter 3.



Figure 2-13 Intra-PDSN Rate Resource Selector Window

Table 2-13 Intra-PDSN Rate Resource Selector Window

Item Description

Fields

Test Activity Pull-down menu to select a desired test activity.Note: The Intra-PDSN Rate test activity is not available in HA Nodal test cases.




The amount of time to wait before performing a handoff.

Mobility Start Type

Specifies when the handoff events should occur. When All Sessions Started is the only option.


Specifies the rate in handoffs per second to be used.


Selects the distribution method to be applied to the Mobility Rate. The options are Fixed, Uniform, Normal, and Poisson.




Activation Method

Selects the method to be used for determining the handoff period. The options are By block or By time. If By block is selected, the sessions are handed off on a block by block basis, for the specified block size. If By time is selected, the sessions are handed off for the specified time.

Block Size (1 - 200,000)

Contingent on By block selected for Activation Method. Specifies the number of sessions, block size, to be handed off before checking the error threshold.

Time Period (Seconds) (1 _ 86400)

Contingent on By time selected for Activation Method. Specifies the amount of time the rate test hands off sessions before checking the error threshold.


Specifies the error threshold in terms of percentage of errors in relation to the number of successful handoffs.

Table 2-13 Intra-PDSN Rate Resource Selector Window (Continued)

Item Description



To create a test session using the Intra-PDSN Rate test activity, follow the steps described in Procedure 2-12.


Specifies the amount of time to wait prior to starting the next Intra-PDSN handoff rate test run.


Specifies the amount to decrease the Mobility Rate if the error threshold is exceeded.

Table 2-13 Intra-PDSN Rate Resource Selector Window (Continued)

Item Description

Procedure 2-13 Set Up Intra-PDSN Rate Test


2. In the Test Activity field, use the pull-down tab to select Intra-PDSN Rate.


4. In the Mobility Start Type field, use the pull-down tab to select When All Sessions Started. Note: That is the only option available for an Intra-PDSN Rate test activity.

5. In the Mobility Rate field enter the desired handoff rate in sessions/second.

6. In the Mobility Rate Interval Distribution field, use the pull-down tab to select the desired distribution method. If Fixed is not selected, an additional parameter will be displayed that defines the boundaries of the distribution model. Set the Maximum Deviation from Mean if the Uniform or Poisson method was selected. Set the Standard Deviation if the Normal method was selected.


8. If By block was selected as the Activation Method, then enter the desired block size for the handoff run in the Block Size field.

If By time was selected as the Activation Method, then enter the desired time for each handoff run in the Time Period field.


Test Case Set UpMIP Revocation


Measurements associated with the Intra-PDSN Rate test activity are defined in “Test Summary Measurements for Mobility Testing” (Table 4-3) and “Rate Test Measurements” (Table 4-19).

Intra-PDSN Rate Options

Other test options are not recommended during Intra-PDSN Rate test measurements. Other activities may invalidate the test results due to increased CPU utilization on the SUT. The purpose of rate test measurements is to measure the maximum rates with no other activity present.

MIP RevocationThe purpose of the MIP Revocation test activity is to determine the PDSN’s ability to process MIP revocations. This test activity is only available in the HA nodal configuration.

By running a MIP Revocation test at various capacity levels and various revocation rates, the user can determine the maximum revocation rate supported at various capacity levels.

During the MIP Revocation test activity, the test case begins setting up sessions at a selected rate of activations per second until the total number of activations is achieved.

If the user selects When All Sessions Started, for the Revocation Start Type, the test waits the specified start time after all sessions are active and then begins performing revocations at the selected rate for all active sessions.

If the user selects When Session Started, for the Revocation Start Type, the test waits the specified start time and performs a revocation for each session as it is established.

MIP Revocation Set Up

A MIP Revocation test activity is set up from the Test Activity tab of a selected test case as shown in Figure 2-14. The configurable parameters for a MIP Revocation test activity are briefly described in Table 2-14. More detailed parameter definitions can be found in “MIP Revocation Parameters” in Chapter 3.

10. In the Wait Time field, enter the amount of time the test waits before beginning the next handoff period or block.

11. In the Backoff Rate field, enter the percentage to be used to reduce the handoff rate when the error threshold is exceeded.

12. Select the RP #2 tab, and configure the parameters for the second PCF emulator as described in “Modify RP Protocol Parameters” (Procedure 2-22).

Procedure 2-13 Set Up Intra-PDSN Rate Test (Continued)



Figure 2-14 MIP Revocation Resource Selector Window



Table 2-14 MIP Revocation Resource Selector Window

Item Description

Fields

Test Activity Pull-down menu to select a desired test activity.Note: The MIP Revocation test activity is not available in SIP, SIP VPN, or End-to-End Mobile IP test cases.

RSE Flag (0 - 1)

A 1 indicates the Revocation Support Extension should be included in the Registration Request and Registration Reply messages. Options are 0 or 1.

RSE Type (128 - 255)

Identifies the type value to be used when constructing the Revocation Support Extension.

Inform Bit (0 - 1)

Indicates whether the mobile node should initiate the revocation. Options are 0 or 1. A 0 indicates that it should.

RSE Length (0 - 1000)

Indicates the length of the Revocation Support Extension.

RRV Type (0 - 1000)

Indicates the message type value to be used for RRV messages.

RRVA Type (0- - 1000)

Indicates the message type value to be used for RRVA messages.

Revocation Time (Seconds) (0 - 10000)

Specifies the period to wait before beginning revocations once all sessions are established or after each session is established.

Revocation Start Type

Specifies whether the revocation events should occur as each session is established, When Session Started, or after all sessions are established, When All Sessions Started.

Revocation Rate (Session/Second) (0 - 1000)

Conditional on When All Sessions Started as the Revocation Start Type. Specifies the rate in revocations per second to be used once all sessions have been established.



To create a test session using the Intra-PDSN test activity, follow the steps described in Procedure 2-14.

Revocation Rate Interval Distribution

Conditional on When All Sessions Started selected as Revocation Start Type. Selects the distribution method to be used for the Revocation Rate. The options are Fixed, Uniform, Normal, and Poisson.


Conditional on Uniform, or Poisson selected as Revocation Rate Interval Distribution. Limits the standard deviation in the selected distribution model to a percentage of the mean.


Table 2-14 MIP Revocation Resource Selector Window (Continued)

Item Description

Procedure 2-14 Set Up MIP Revocation Test


2. In the Test Activity field, use the pull-down tab to select MIP Revocation.

3. In the RSE Flag field, enter a 1 if the Revocation Support Extension should be included in the Registration Request and Registration Reply messages.

4. In the RSE Type field, enter the type value to be used when constructing the Revocation Support Extension.

5. In the Inform Bit field, enter a 1 if the HA/PDSN-FA should inform the mobile node of a revocation.

6. In the RSE Length field, enter the length of the Revocation Support Extension.

7. In the RRV Type field, enter the message type value to be used for RRV messages.

8. In the RRVA Type field, enter the message type value to be used for RRVA messages.

9. In the Revocation Time field, enter the amount of time to wait before initiating revocations.

10. In the Revocation Start Type field, use the pull-down tab to select When All Sessions Started or When Session Started.

Test Case Set UpInter-PDSN


Measurements associated with the MIP Revocation test activity are defined in “Test Summary Measurements For MIP Revocation” (Table 4-4).

MIP Revocation Options

There are several options available to the user during the setup of the MIP Revocation test as described in the following paragraphs.

SUT Query

The user has the option of enabling a SUT Query during the MIP Revocation test. Refer to “SUT Query Options.”


The user has an option of enabling data traffic during the MIP Revocation test. Refer to “Data Verification.”

Continuous Data

The user has the option of enabling continuous data traffic during the MIP Revocation test. The selected data type is transmitted continuously during the session activation interval. Refer to “Continuous Data.”

Inter-PDSNThe purpose of the Inter-PDSN handoff test activity is to determine the ability to process handoffs from one PDSN to another PDSN. By running an Inter-PDSN handoff test at various capacity levels and various handoff rates, the user can determine the maximum handoff rate supported at various capacity levels. The Inter-PDSN handoff test can be done in two different configurations. In the HA Nodal configuration, the handoffs are done between two emulated PDSN-FA nodes on the CPTS test servers. This verifies the HA’s

11. If When All Sessions Started was selected as the Revocation Start Type, then enter the desired rate in the Revocation Rate field.

12. If When All Sessions Started was selected as the Revocation Start Type, use the pull-down tab in the Revocation Rate Interval Distribution field to select the desired distribution model. If Fixed is not selected, an additional parameter will be displayed that defines the boundaries of the distribution model. Set the Maximum Deviation from Mean if the Uniform or Poisson method was selected. Set the Standard Deviation if the Normal method was selected.

Procedure 2-14 Set Up MIP Revocation Test (Continued)



ability to handle the handoffs between two PDSN-FAs. In the end-to-end configuration, the handoffs are done between two PDSN-FA SUTs, and it determines the ability of the PDSN-FAs to accept handoff requests.

During the Inter-PDSN handoff test activity, the test case begins setting up sessions at a selected rate of activations per second until the total number of activations is achieved.

If the user selects When Session Started, for the Mobility Start Type, the test waits for the specified delay time and performs a handoff for each session as it is activated. The user also has the option of selecting either Single Handoff or Continuous Handoff. If Single Handoff is selected, the test will perform one handoff for each session as it is established. If Continuous Handoff is selected, the test will perform continuous handoffs for each session, waiting the specified delay time between handoffs.

If the user selects When All Sessions Started, for the Mobility Start Type, the test waits the specified delay time after all sessions are active, and then begins performing handoffs for all active sessions based on the specified handoff rate. The test continues performing handoffs until all active sessions have been handed off. It then begins handing each session back to the original PDSN-FA. This continues for the specified duration or until the test is stopped.

Inter-PDSN Set Up

An Inter-PDSN handoff test activity is set up from the Test Activity tab of a selected test case as shown in Figure 2-15. The configurable parameters for an Inter-PDSN handoff test activity are briefly described in Table 2-15. More detailed parameter definitions can be found in “Inter-PDSN Parameters” in Chapter 3.



Figure 2-15 Inter-PDSN End-to-End Resource Selector Window

Table 2-15 Inter-PDSN End-to-End Resource Selector Window

Item Description

Fields

Test Activity Pull-down menu to select a desired test activity.Note: The Inter-PDSN test activity is available in HA Nodal and End-to-End Mobile IP test cases.


Specifies the second PDSN-FA to be used for the Inter-PDSN test.Note: In an HA Nodal configuration, an area is displayed to identify the node address for an emulated second PDSN-FA node as shown in “Inter-PDSN Handoff Rate Resource Selector Window” (Figure 2-16).



To create a test session using the Inter-PDSN test activity, follow the steps described in Procedure 2-15.



Mobility Start Type

Specifies whether the handoff events should occur as each session is established, When Session Started, or after all sessions are established, When All Sessions Started.


Conditional on When All Sessions Started as the Mobility Start Type. Specifies the rate in handoffs per second to be used once all sessions have been established.Note: When using an HA Nodal test, the upper limit of this rate is 4,000.


Conditional on When All Sessions Started selected as Mobility Start Type. Selects the distribution method to be used for the Mobility Rate. The options are Fixed, Uniform, Normal, and Poisson.


Conditional on Uniform, or Poisson selected as Revocation Rate Interval Distribution. Limits the standard deviation in the selected distribution model to a percentage of the mean.


Handoff Mode Conditional on When Session Started selected as Mobility Start Type. Selects either a single handoff per session, or continuous handoffs. Options are Single Handoff or Continuous Handoff.

Table 2-15 Inter-PDSN End-to-End Resource Selector Window (Continued)

Item Description

Procedure 2-15 Set Up Inter-PDSN Test


2. In the Test Activity field, use the pull-down tab to select Inter-PDSN.

3. If the Basic test case selected was the End-to-End MIP test case, use the pull-down tab in the System Under Test #2 field, to select a pre-configured SUT.



Measurements associated with the Inter-PDSN test activity are defined in “Test Summary Measurements for Mobility Testing” (Table 4-3).

Inter-PDSN Options

There are several options available to the user during the setup of the Inter-PDSN handoff test as described in the following paragraphs.

SUT Query

The user has the option of enabling a SUT Query during the Inter-PDSN test. Refer to “SUT Query Options.”


The user has an option of enabling data traffic during the Inter-PDSN test. Refer to “Data Verification.”

4. If the Basic test case selected was the HA Nodal test case, enter the address information for the second PDSN-FA node emulator in the Foreign Agent Node Address #2 fields, and the port number for the second PDSN-FA in the Foreign Agent #2 Port Number field.


6. In the Mobility Start Type field, use the pull-down tab to select When All Sessions Started or When Session Started.

7. If When All Sessions Started was selected as the Mobility Start Type, enter the desired rate in the Mobility Rate field.

If When Session Started was selected as the Mobility Start Type, use the pull-down tab in the Handoff Mode field to select Single Handoff or Continuous Handoff.

8. If When All Sessions Started was selected as the Mobility Start Type, use the pull-down tab in the Mobility Rate Interval Distribution field to select the desired distribution model. If Fixed is not selected, an additional parameter will be displayed that defines the boundaries of the distribution model. Set the Maximum Deviation from Mean if the Uniform or Poisson method was selected. Set the Standard Deviation if the Normal method was selected.

Procedure 2-15 Set Up Inter-PDSN Test (Continued)

Test Case Set UpInter-PDSN Handoff Rate


Continuous Data

The user has the option of enabling continuous data traffic during the Inter-PDSN test. The selected data type is transmitted continuously during the session activation interval. Refer to “Continuous Data.”

Inter-PDSN Handoff RateThe purpose of the Inter-PDSN handoff rate test activity is to determine the rate at which handoffs from one PDSN to another PDSN can be processed at various capacity levels. The test can be done in two different configurations. In the HA Nodal configuration, the handoffs are done between two emulated PDSN-FA nodes on the CPTS test servers. This tests the rate at which the HA can process handoffs between two PDSN-FAs. In the end-to-end configuration, the handoffs are done between two PDSN-FA SUTs, and the test determines the rates at which the PDSN-FAs can process handoff requests.

During the Inter-PDSN handoff rate test activity, the test case first activates the total number of sessions requested between PDSN-FA #1 and the HA. After waiting the specified delay time, the test begins handing off sessions from PDSN-FA #1 to PDSN-FA #2 at a selected rate of activations per second for a specified time period or for a specified block of sessions. At the end of the time period, or once the block of sessions has been handed off, the test checks to see if the error threshold has been exceeded. If it has not, the test will handoff the next block of sessions or will handoff sessions for the specified time period.

If the error threshold is exceeded, the test will hand back the last run of sessions, decrease the handoff rate by the specified back off percentage, and handoff that block at the lower rate. Once that block has been handed off at a rate that does not exceed the error threshold, the test continues with the next block or time period.

Inter-PDSN Handoff Rate Set Up

An Inter-PDSN handoff rate test activity is set up from the Test Activity tab of a selected test case as shown in Figure 2-16. The configurable parameters for an Inter-PDSN handoff rate test activity are briefly described in Table 2-16. More detailed parameter definitions can be found in “Inter-PDSN Rate Parameters” in Chapter 3.



Figure 2-16 Inter-PDSN Handoff Rate Resource Selector Window



Table 2-16 Inter-PDSN Handoff Rate Resource Selector Window

Item Description

Fields

Test Activity Pull-down menu to select a desired test activity.Note: The Inter-PDSN Rate test activity is available in HA Nodal and End-to-End Mobile IP test cases.


Area for entering the node address for the emulated second PDSN-FA.

In an End-to-End Mobile IP configuration, a pull-down tab is displayed to select the PDSN-FA #2 SUT as shown in “Inter-PDSN End-to-End Resource Selector Window” (Figure 2-15).

Physical Interface

The IP address of the physical ethernet port to be used on the test server for the emulated second PDSN-FA. The virtual IP Address selected will come from the pool of addresses associated with this interface.

IP Address The virtual IP address to be used for the emulated second PDSN-FA.

Default Routing

Selects default routing for accessing the emulated second PDSN-FA.

Specify Next Hop IP Address

Selects a specific route for accessing the emulated second PDSN-FA. Points to a specific router to ensure correct path is taken for accessing the node.

IP Address IP address for the specific router or port to be used when Specify Next Hop IP Address is selected.


The port number to be used with the emulated second PDSN-FA’s IP address.



Mobility Start Type

Specifies whether the handoff events should occur after all sessions are established, When All Sessions Started. When All Sessions Started is the only option for Inter-PDSN Rate test activity.



Mobility Rate (Session/Second) (0 - 4000)

Specifies the rate in handoffs per second to be used once all sessions have been established.Note: When using an End-to-End test, the upper limit of this rate is 1,000.


Conditional on When All Sessions Started selected as Mobility Start Type. Selects the distribution method to be used for the Mobility Rate. The options are Fixed, Uniform, Normal, and Poisson.




Activation Method

Selects the method to be used for determining the handoff period. The options are By block or By time. If By block is selected, the sessions are handed off on a block by block basis, for the specified block size. If By time is selected, the sessions are handed off for the specified time.

Block Size (1 - 200,000)

Contingent on By block selected for Activation Method. Specifies the number of sessions, block size, to be handed off before checking the error threshold.

Time Period (Seconds) (1 - 86400)

Contingent on By time selected for Activation Method. Specifies the amount of time the rate test hands off sessions before checking the error threshold.


Defines the percentage of errors that must occur before reducing the Mobility Rate.


The amount of time to wait before checking the error threshold and, if necessary, adjusting the Mobility Rate.


The amount by which the Mobility Rate will be reduced after the Error Threshold Percentage has been exceeded.

Table 2-16 Inter-PDSN Handoff Rate Resource Selector Window (Continued)

Item Description



To create a test session using the Inter-PDSN test activity, follow the steps described in Procedure 2-12.

Procedure 2-16 Set Up Inter-PDSN Handoff Rate Test


2. In the Test Activity field, use the pull-down tab to select Inter-PDSN Rate.

3. If the Basic test case selected was the End-to-End MIP test case, use the pull-down tab in the System Under Test #2 field, to select a pre-configured SUT.

4. If the Basic test case selected was the HA Nodal test case, enter the address information for the second PDSN-FA node emulator in the Foreign Agent Node Address #2 fields.

5. Enter the port number for the second PDSN-FA in the Foreign Agent #2 Port Number field


7. In the Mobility Start Type field, use the pull-down tab to select When All Sessions Started. Note: That is the only option available for an Inter-PDSN Rate test activity.

8. In the Mobility Rate field enter the desired handoff rate in sessions/second for the handoff rate.

9. In the Mobility Rate Interval Distribution field, use the pull-down tab to select the desired distribution method. If Fixed is not selected, an additional parameter will be displayed that defines the boundaries of the distribution model. Set the Maximum Deviation from Mean if the Uniform or Poisson method was selected. Set the Standard Deviation if the Normal method was selected.


11. If By block was selected as the Activation Method, then enter the desired block size in the Block Size field.

12. If By time was selected as the Activation Method, then enter the desired time for each run in the Time Period field.


Test Case Set UpData Verification


Measurements associated with the Inter-PDSN Rate test activity are defined in “Test Summary Measurements for Mobility Testing” (Table 4-3) and “Rate Test Measurements” (Table 4-19).

Inter-PDSN Handoff Rate Options

Other test options are not recommended during Inter-PDSN rate test measurements. Other activities may invalidate the test results due to increased CPU utilization on the SUT. The purpose of rate test measurements is to measure the maximum rates with no other activity present.

Data VerificationData verification is a data test option available in conjunction with other test activities. When data verification is selected, the test performs a simple data path integrity test for each active session. As each session is successfully established a one-time ping message is sent over the session to the specified network host. If the ping is not successful, the session is torn down, the session error counter is incremented, and the session is retried. Counters are maintained for both successful and failed ping attempts.

Data verification is set up from the Data Traffic tab of a selected test case as shown in Figure 2-17. The configurable parameters for a data verification test activity are briefly described in Table 2-17. More detailed parameter definitions can be found in “Data Traffic Parameters” in Chapter 3.

14. In the Wait Time field, enter the amount of time the test waits before beginning the next session period or block.

15. In the Backoff Rate field, enter the percentage to be used to reduce the handoff rate when the error threshold is exceeded.

Procedure 2-16 Set Up Inter-PDSN Handoff Rate Test (Continued)



Figure 2-17 Data Verification Resource Selector Window

Table 2-17 Data Verification Resource Selector Window

Item Description

Fields

Data Traffic Pull-down menu to select a data activity. The options are Disabled, Verification, and Continuous.

Network Host Selects the location for the network host emulator. The options are Local (resides on the same test server as the test case) or Remote (resides on a different test server).

Network Host Node Address

Area for entering the address of the network host if Local selected for Network Host. If Remote is selected, used to enter the IP address of the remote network host.



To create a test session using data verification activity, follow the steps described in Procedure 2-17.

Physical Interface

The IP address of the physical ethernet port to be used on the test server for the emulated network host. The virtual IP Address selected will come from the pool of addresses associated with this interface.

IP Address The virtual IP address to be used for the emulated network host.

Default Routing

Selects default routing for accessing the emulated network host.


Selects a specific route for accessing the emulated network host. Points to a specific router to ensure correct path is taken for accessing the node.

IP Address IP address for the specific router or port to be used when Specify Next Hop IP Address is selected.

Data Start Delay (Milliseconds) (1 - 60,000)

Specifies the amount of time to wait following a session activation before transmitting a Ping message to the network host.

Type of Service (0 - 255)

Specifies the type of service to request. This parameter is used by some networks to determine service precedence. Normally the higher the value, the higher the precedence of the service.

Time to Live (1 - 255)

Specifies the length of time in seconds that a datagram may stay in the internet. This value is decremented by each module that processes the datagram. When the value reaches zero, the datagram is discarded.

Table 2-17 Data Verification Resource Selector Window (Continued)

Item Description

Procedure 2-17 Set Up Data Verification

1. Select the Data Traffic tab on the Resource Selector window.

2. In the Data Activity field, use the pull-down tab to select Verification.

3. In the Network Host field, use the pull-down tab to select Local or Remote.

Test Case Set UpContinuous Data


Measurements associated with the Data Verification option are defined in “Network Host Measurements” (Table 4-13) and “Data Traffic Measurements” (Table 4-16).

Continuous DataThe Continuous Data traffic test is more advanced than the verification test. With this test, data packets of a user-defined protocol are transported over the sessions when they become established. Not only is the traffic type (protocol packets) user-defined, but also the user specifies the size of the packets and the rate at which the packets are transmitted. Distribution models can be used to shape the data traffic and simulate real-world traffic activity. Data packet transmission can start when each session is established or the traffic can be started after all sessions are successfully established. This is also user-defined. Once traffic is started, packets are continuously transmitted until the test is terminated.

Continuous data is set up from the Data Traffic tab of a selected test case as shown in Figure 2-18. The configurable parameters for a continuous data test activity are described in “Data Traffic Parameters” in Chapter 3.

4. If Remote was selected for Network Host, enter the network host’s IP address in the Network Host Node Address field.Note: To use a remote network host emulator, the user must set up a Network Host test case as described in “Network Host Test Cases.”

If Local was selected, configure the emulated network host:• Use the Physical Interface pull-down tab to select the test sever’s ethernet

address that will be used for the emulated network host’s interface.• Enter a virtual IP Address, selected from the pool of addresses associated

with the Physical Interface, for the network host node.• Select either Default Routing or Specify Next Hop IP Address. Enter the

IP Address for the next hop if Default Routing was not selected.

5. In the Data Start Delay field, enter the amount of time to wait before the start of data transmission following the session activation.



Procedure 2-17 Set Up Data Verification (Continued)



Figure 2-18 Continuous Data Resource Selector Window

To create a test session using continuous data activity, follow the steps described in Procedure 2-18.



Procedure 2-18 Set Up Continuous Data

1. Select the Data Traffic tab on the Resource Selector window.

2. In the Data Activity field, use the pull-down tab to select Continuous.

3. In the Network Host field, use the pull-down tab to select Local or Remote.

4. If Remote was selected for Network Host, enter the network host’s IP address in the Network Host Node Address field.Note: To use a remote network host emulator, the user must set up a Network Host test case as described in “Network Host Test Cases.”

If Local was selected, configure the emulated network host:• Use the Physical Interface pull-down tab to select the test sever’s ethernet

address that will be used for the emulated network host’s interface.• Enter a virtual IP Address, selected from the pool of addresses associated

with the Physical Interface, for the network host node.• Select either Default Routing or Specify Next Hop IP Address. Enter the

IP Address for the next hop if Default Routing was not selected.

5. In the Traffic Start field, use the pull-down tab to selected When All Sessions Established (Capacity Test Only) or When Session Established.

6. In the Data Start Delay field, enter the desired delay time before traffic is initiated following session activation or after all sessions are established.

7. In the Payload Data Size area, configure the data parameters as desired to achieve a the specific packet size or data rate desired.

8. In the Packet Interval Distribution field, use the pull-down tab to select the desired distribution method. If Fixed is not selected, an additional parameter will be displayed that defines the boundaries of the distribution model. Set the Maximum Deviation from Mean if the Uniform or Poisson method was selected. Set the Standard Deviation if the Normal method was selected.

9. In the Packet Size Distribution field, use the pull-down tab to select the desired distribution method. If Fixed is not selected, an additional parameter will be displayed that defines the boundaries of the distribution model. Set the Maximum Deviation from Mean if the Uniform or Poisson method was selected. Set the Standard Deviation if the Normal method was selected.



Test Case Set UpSUT Query Options


Measurements associated with the Continuous Data option are defined in “Network Host Measurements” (Table 4-13) and “Data Traffic Measurements” (Table 4-16).

SUT Query OptionsThe SUT Query option provides a mechanism for collecting CPU usage information from the SUT in real-time during a test session using an automated telnet capability.

In addition to reporting CPU usage, SUT Query allows the user to define automatic rate adjustments that are triggered when the actual CPU usage is above or below the specified target. When CPU usage is below the target rate, test rates are increased and when the CPU usage is above the target rate, test rates are decreased. This allows the development of tests that can determine a variety of rates that can be achieved by the SUT without producing an intolerable load on the CPU.

SUT Query is set up from the SUT Query tab of a selected test case as shown in Figure 2-19. The configurable parameters for SUT query test activity are described in Table 2-18.

12. In the Protocol field, use the pull-down tab to select the desired data type. The options are Ping (ICMP), HTTP, FTP, WAP, SMTP, RAW, UDP, and TCP.

13. Configure the parameters and options for the selected data type using the guidelines in “Data Traffic Parameters” in Chapter 3.

An Error Inject option is also available and includes several methods of producing invalid data traffic packets.

Procedure 2-18 Set Up Continuous Data (Continued)



Figure 2-19 SUT Query Resource Selector Window

Table 2-18 SUT Query Resource Selector Window

Item Description

Fields

SUT Query Enables automatic query of SUT for CPU real-time usage or a user-defined periodic query. Options are Enabled or Disabled.

Target SUT Prompt

Expected prompt from the target SUT that is key for sending user-defined commands.



Query CPU Utilization

Enables automatic query of the SUT CPU Usage. Options are Enabled or Disabled.

Query CPU Command

Conditional on Query CPU Utilization set to Enabled. The command to be used for the SUT Query.

Query CPU Response Search Pattern

Conditional on Query CPU Utilization set to Enabled. The string to be used for parsing the response tokens from the CPU.

Query CPU Response Offset from Search Pattern

Conditional on Query CPU Utilization set to Enabled. Points the test to the parameter to be parsed. The number represents the location of the target token in relation to the string entered in the Query CPU Response Search Pattern field.

SUT Query Time (Seconds) (5 - 100)

Conditional on Query CPU Utilization set to Enabled. Sets the interval in seconds between queries.

Dynamic Rate Adjustment

Conditional on SUT Query set to Enabled. Enables automatic rate adjustment based on SUT CPU real-time usage. Options are Enabled or Disabled.

Target SUT CPU Rate (Percent) (1 - 100)

Conditional on Dynamic Rate Adjustment set to Enabled. Sets the target for SUT CPU usage. If current usage is less than target, session rate is increased. If current usage is greater than target, session rate is decreased.

Session Connect Adjustment Rate (Sessions/Second)

Conditional on Dynamic Rate Adjustment set to Enabled. Rate in sessions/second that session activation rate is increased or decreased based on SUT CPU usage.

Session Disconnect Adjustment Rate (Sessions/Second)

Conditional on Dynamic Rate Adjustment set to Enabled. Rate in sessions/second that session deactivation rate is increased or decreased based on SUT CPU usage.

Table 2-18 SUT Query Resource Selector Window (Continued)

Item Description



Dynamic Mobility Adjustment Rate (Sessions/Second)

Conditional on Dynamic Rate Adjustment set to Enabled. Rate in sessions/second that the session handoff rate is increased or decreased based on SUT CPU usage.

Accelerated Dynamic Rate Adjustment

Conditional on Dynamic Rate Adjustment set to Enabled. Enables accelerated dynamic rate adjustment if CPU Usage is outside of normal dynamic adjustment range. Options are Enabled or Disabled.

Accelerated Rate Threshold

(+/-) (2 - 50)

Conditional on Accelerated Dynamic Rate Adjustment set to Enabled. Applies a threshold range to the Target CPU Rate. If the SUT CPU usage is within this threshold, then the normal adjustment rate is applied. If the returned value is outside of this range, then the accelerated adjustment rate is used.

Accelerated Session Connect Adjustment Rate (Sessions/Second)

Conditional on Accelerated Dynamic Rate Adjustment set to Enabled. Accelerated adjustment rate for session connects.

Accelerated Session Disconnect Adjustment Rate (Sessions/Second)

Conditional on Accelerated Dynamic Rate Adjustment set to Enabled. Accelerated adjustment rate for session disconnects.

Allow Adjusted Rate to Exceed Connect/Disconnect Rate

Conditional on Dynamic Rate Adjustment set to Enabled. Allows the adjusted rate to exceed the rate specified for session connect rate or session disconnect rate. Options are Enabled or Disabled.

Periodic Query

Conditional on SUT Query set to Enabled. Enables periodic query of the SUT or a Test Server during a test. The options are Disabled or Enabled.


Item Description



To include the SUT Query option in a test case, follow the steps described in Procedure 2-19.

Periodic Query Target Platform

Conditional on Periodic Query set to Enabled. The target platform for the query. The options are SUT or Test Server.

Periodic Query Command

Conditional on Periodic Query set to Enabled. The file name of the script to be executed for the query.

Periodic Query Time (Seconds) (5 - 100)

Conditional on Periodic Query set to Enabled. Specifies the interval time between queries to the SUT.


Item Description

Procedure 2-19 Set Up SUT Query

1. Select the SUT Query tab on the Resource Selector window.

2. In the SUT Query field, use the pull-down tab to select Enabled.

3. In the Target SUT Prompt field, enter the expected prompt from the SUT.

4. Use the pull-down tab in the Query CPU Utilization field to select Enabled.

5. Enter the exact command string of the CPU query to be sent to the CPU in the Query CPU Command field.

6. Enter the string or token to be used for the search of the response from the CPU in the Query CPU Response Search Pattern field.

7. Enter the offset value in the Query CPU Response Offset from Search Pattern field.

Important: This offset is the starting location of the target token in relation to the Query CPU Response Search Pattern.

8. Enter the desired query time in the SUT Query Time field.

Test Case Set UpProtocol Configuration Set Up


Measurements associated with the SUT Query option are defined in “Test Summary Measurements for CPU Query” (Table 4-2).

Protocol Configuration Set UpThe CPTS allows the user to set all of the key protocol parameters for the MIP, RP, PPP, and L2TP protocol layers. Some of these parameters must be set to correspond to the values expected by the SUT. Other values may be set to create error conditions. All of the protocol parameters are assigned default values and can be used without modification. The following paragraphs describe the procedures required to modify these parameters.

9. Use the pull-down tab in the Dynamic Rate Adjustment field to select Enabled or Disabled.

If Dynamic Rate Adjustment is enabled:• Enter the desired target CPU rate in the Target SUT CPU Rate field.• Enter the desired rate in the Session Connect Adjustment Rate field.• Enter the desired rate in the Session Disconnect Adjustment Rate field.• Enter the desired rate in the Dynamic Mobility Adjustment Rate field.• Use the pull-down tab in the Accelerated Dynamic Rate Adjustment field

to select Enabled or Disabled.• Use the pull-down tab in the Allow Adjusted Rate to Exceed Connect/

Disconnect Rate to select Enabled or Disabled.

10. If Accelerated Dynamic Rate Adjustment was enabled in the previous step:• Enter the desired threshold in the Accelerated Rate Threshold field.• Enter the desired rate in the Accelerated Session Connect Adjustment

Rate field.• Enter the desired rate in the Accelerated Session Disconnect Adjustment

field.

11. In the Periodic Query field, use the pull-down tab to select Enabled or Disabled.

If Periodic Query is enabled:• Use the pull-down tab in the Periodic Query Target Platform field to

select SUT or Test Server.• Enter the command string to be sent to the CPU in the Periodic Query

Command field.• Enter the desired time in the Periodic Query Time field.

Procedure 2-19 Set Up SUT Query (Continued)



Modifying MIP Protocol Parameters

When performing tests in a FA nodal, HA nodal, or End-to-End Mobile IP test configuration, configure the MIP protocol parameters as shown in “MIP Tab” (Figure 2-20).

Figure 2-20 MIP Tab

The parameters for an FA nodal or End-to-End configuration may be modified by following the steps described in Procedure 2-20. Detailed descriptions for these parameters can be found in “MIP Parameters” (Table 3-23). Use Procedure 2-21 to configure the parameters for an HA nodal configuration.



Procedure 2-20 Modify MIP Protocol Parameters

1. Select the MIP tab from the Resource Selector window.

2. In the Use Reverse Tunnel field, use the pull-down tab to select Enabled or Disabled, based on the access model desired. Refer to Chapter 1, “Test Configurations,” for a description of the MIP and MIP Reverse Tunnel access models. Note: The Reverse Tunnel configuration is also used for the MIP VPN access model.

3. In the MIP HA Secret field, enter the code expected by the Home Agent for processing MIP sessions.

4. In the Request Simultaneous Bindings field, enter the number of simultaneous bindings desired.

5. In the Request Broadcast Datagrams, enter the number of broadcast datagrams desired.

6. In the Encapsulation Mode field, enter the value for the encapsulation mode desired.

7. In the Use HMAC Authentication field, use the pull-down tab to select Disabled or Enabled. Note: Enabled selects HMAC authentication for AAA server authentication. Disabled defaults to the more common Radius AAA authentication.

8. In the HA Lifetime (Seconds) (1 – 65535) field, enter the desired value for the HA lifetime timer.

9. In the Retries field, enter the number of retries desired in attempting to establish a MIP session with the SUT.

10. In the Reregistration Time (Seconds) (0 – 100) field, enter the desired time for reregistration to occur on each MIP session, or enter 0 to disable reregistration.Note: When enabled, the registration will occur the specified number of seconds prior to the expiration of the HA Lifetime timer. For example, if 20 seconds is specified for the Reregistration Time, and the HA Lifetime is set to 10,000, then the reregistration will occur after the session has been active for 9,980 seconds.

11. In the FA HA SPI field, enter the SPI value to be sent from the PDSN-FA to the HA.

12. In the FA HA Secret field, enter the secret value to be sent from the PDSN-FA to the HA.



The parameters for an HA nodal configuration may be modified by following the steps described in Procedure 2-21. Detailed descriptions for these parameters can be found in “MIP Parameters for HA Nodal Testing” (Table 3-24). Use Procedure 2-20 to configure the parameters for an FA nodal or End-to-End configuration.

13. In the Home Address field, enter the starting IP address to be used with each MIP session.

Important: See “MIP Parameters” in Chapter 3 for detailed guidelines regarding the Home Address.

14. In the MN Home Agent SPI field, enter the SPI to be sent from the mobile nodes to the HA.

15. In the MN AAA SPI field, enter the SPI value to be sent from the mobile node to the AAA Radius server.

16. In the MN AAA Secret field, enter the secret value to be sent from the mobile node to the AAA Radius server.

17. In the Co-located Care of Address field, enter the IP address for the co-located “Care Of” address.

18. In the HA Retries field, enter the desired number of retries to be attempted when setting up a MIP session between the PDSN-FA and the HA.

19. In the HA Connection Type field, enter the value of the connection type to be used when connecting to the HA.

20. In the NAI field, enter the starting network address indicator to be used for identifying the mobile nodes.Note: This value is incremented for each session to create a unique NAI for each session. See “Variable Parameter Values” in Chapter 3 for more information.

21. Click Apply to use the new MIP parameters to the selected test case.

Procedure 2-20 Modify MIP Protocol Parameters (Continued)

Procedure 2-21 Modify HA Nodal MIP Protocol Parameters

1. Select the MIP tab from the Resource Selector window.

2. In the Request Simultaneous Bindings field, enter the number of simultaneous bindings desired.

3. In the Request Broadcast Datagrams, enter the number of broadcast datagrams desired.



4. In the Encapsulation Mode field, enter the value for the encapsulation mode desired.

5. In the Use HMAC Authentication field, use the pull-down tab to select Disabled or Enabled. Note: Enabled selects HMAC authentication for AAA server authentication. Disabled defaults to the more common Radius AAA authentication.

6. In the HA Lifetime (Seconds) (1 – 65535) field, enter the desired value for the HA lifetime timer.

7. In the Home Address field, enter the starting IP address to be used with each MIP session.

Important: See “MIP Parameters” in Chapter 3 for detailed guidelines regarding the Home Address.

8. In the MN-FA Challenge Size field, enter the number of digits in the MN-FA Challenge field or a 0 to disable the challenge extension.

9. In the MN-FA Challenge field, enter the value that will be included in the challenge extension if the MN-FA Challenge Size is greater than 0.

10. In the FA SPI field, enter the SPI value to be sent to the PDSN-FA.

11. In the FA Secret field, enter the secret value to be used in the FA HA authentication extension.

12. In the MN-HA SPI field, enter the SPI value to be used in the MN HA authentication extension.

13. In the MN-HA Secret field, enter the secret value to be used in the MN HA authentication extension.

14. In the FA HA SPI field, enter the SPI value to be sent from the PDSN-FA to the HA.

15. In the FA HA Secret field, enter the secret value to be sent from the PDSN-FA to the HA.

16. In the MN AAA SPI field, enter the SPI value to be sent from the mobile node to the AAA Radius server.

17. In the MN AAA Secret field, enter the secret value to be sent from the mobile node to the AAA Radius server.

18. In the Co-located Care of Address field, enter the IP address for the co-located “Care Of” address.

Procedure 2-21 Modify HA Nodal MIP Protocol Parameters (Continued)



Measurements associated with the MIP signaling are defined in “Mobile IP Measurements” (Table 4-8).

Modifying RP Protocol Parameters

For SIP, FA Nodal and End-to-End test configurations the user may set up the RP protocol parameters as shown in “RP Tab” (Figure 2-21) and as described in “RP Protocol Configuration Parameters” (Table 3-20) by following the steps identified in Procedure 2-22.

Important: These parameters must be set up to match the expected and configured values at the PDSN-FA.

19. In the HA Retries field, enter the desired number of retries to be attempted when setting up a MIP session with the HA.

20. In the Reregistration Time (Seconds) (0 – 100) field, enter the desired time for reregistration to occur on each MIP session, or enter 0 to disable reregistration.Note: When enabled, the registration will occur the specified number of seconds prior to the expiration of the HA Lifetime timer. For example, if 20 seconds is specified for the Reregistration Time, and the HA Lifetime is set to 10,000, then the reregistration will occur after the session has been active for 9,980 seconds.

21. In the HA Connection Type field, enter the value of the connection type to be used when connecting to the HA.

22. In the NAI field, enter the starting network address indicator to be used for identifying the mobile nodes.Note: This value is incremented for each session to create a unique NAI for each session. See “Variable Parameter Values” in Chapter 3 for more information.

23. Click Apply to use the new MIP parameters to the selected test case.

Procedure 2-21 Modify HA Nodal MIP Protocol Parameters (Continued)



Figure 2-21 RP Tab

Procedure 2-22 Modify RP Protocol Parameters

1. Select the RP tab from the Resource Selector window.

2. In the RP Type field, use the pull-down tab to select Open RP type.

3. In the PCF Node Address area, use the pull-down tab of the Physical Interface field, to select the physical ethernet port to be used for the PCF emulator.



4. In the PCF Node Address area, enter the IP address of the first emulated PCF Node in the Starting IP Address field.

Important: This IP address must be selected from the pool of virtual IP addresses associated with the physical interface selected.

5. In the PCF Node Address area, enter the total number of PCFs to be emulated in the Number of PCFs (Max of 1000) field.

6. In the PCF Node Address area, select Default Routing or Specify Next Hop IP Address.

7. If Specify Next Hop IP Address is selected, enter the IP address of the router to be used for the next hop in the adjacent field.

8. In the PCF Node Port Number field, enter the desired port number for the PCF Node.

9. In the System Under Test (Foreign Agent) Port Number field, enter the desired port number for the SUT.

10. In the Lifetime (Seconds) (1 – 65535) field, enter the desired timer value for the RP lifetime.

11. In the Reregistration Time (Seconds) (5 – 100) field, enter the desired time for RP reregistrations.Note: The registration will occur the specified number of seconds prior to the expiration of the Lifetime timer. For example, if 20 seconds is specified for the Reregistration Time, and the Lifetime is set to 10,000, then the reregistration will occur after the session has been active for 9,980 seconds.

12. In the User Zone field, in the appropriate user zone value to be used in the RP messaging.

13. In the Air Link QOS field, enter the appropriate QOS value to be used in the RP messaging.

14. In the Open RP SPI field, enter the SPI value to be sent to the PDSN-FA.

15. In the Open RP Secret field, enter the secret code to be sent to the PDSN-FA.

16. In the Protocol Type field, use the pull-down tab to select the type of PPP protocol, Unstructured (0x8881) or PPP (0x880b).Note: Unstructured corresponds to Async on the PPP tab, and PPP corresponds to Sync on the PPP tab. This value must be consistent with the selection of Async or Sync on the PPP tab.

Procedure 2-22 Modify RP Protocol Parameters (Continued)



17. In the Dormancy field, use the pull-down tab to select Enabled or Disabled.

If Enabled is selected:• Enter the desired time in the Dormancy Time in Seconds field.• In the Short Data Burst field, use the pull-down tab to select Enabled

or Disabled.

18. In the Redirection field, use the pull-down tab to select Enabled or Disabled for re-direction. Note: Some vendor equipment uses redirection for load sharing across multiple PDSN’s.

19. In the Normal Vendor Specific Extension, use the pull-down tab to select Enabled or Disabled.

If Enabled is selected:• In the PANID SID field, enter the System Identification field for the

Previous Access Network Identifier.• In the PANID NID field, enter the Network Identification field for the

Previous Access Network Identifier.• In the PANID PZID field, enter the Packet Zone Identifier field for the

Previous Access Network Identifier.• In the CANID SID field, enter the System Identification field for the

Current Access Network Identifier.• In the CANID NID field, enter the Network Identification field for the

Current Access Network Identifier.• In the CANID PZID field, enter the Packet Zone Identifier field for the

Current Access Network Identifier.Note: Enabled includes the normal vendor specific extension in the RP messaging.

20. In the Retries field, enter the number of retries to be attempted for RP session set up.

21. In the Starting MS ID field, enter the starting number for the sequential assignment of mobile station IDs for the RP sessions.

22. In the BS ID field, enter the appropriate base station ID code.

23. In the Starting PCF Session ID field, enter the appropriate PCF session ID.Note: This value will be incremented for each session.

24. In the F1 field, enter the Forward Mux Option value.Note: The F1-F10 parameters populate the customer/organization specific extension of the Active Start Airlink Record.

25. In the F2 field, enter the Reverse Mux Option value.




Measurements associated with RP signaling are defined in “RP Measurements” (Table 4-6).

Modifying L2TP Protocol Parameters

For Simple IP VPN test configurations the user may set up the L2TP protocol parameters shown in “L2TP Tab” (Figure 2-22) and described in “L2TP Protocol Configuration Parameters” (Table 3-19) by following the steps identified in Procedure 2-23.

Important: These parameters must be set up to match the expected and configured values at the PDSN.

26. In the F3 field, enter the Forward Rate value.

27. In the F4 field, enter the Reverse Rate value.

28. In the F5 field, enter the Service Option value.

29. In the F6 field, enter the Forward Traffic Type value.

30. In the F7 field, enter the Reverse Traffic Type value.

31. In the F8 field, enter the FCH Frame Size value.

32. In the F9 field, enter the Forward Radio Configuration value.

33. In the F10 field, enter the Reverse Radio Configuration value.

34. Click Apply to use the new RP parameters in the selected test case.




Figure 2-22 L2TP Tab



Procedure 2-23 Modify L2TP Protocol Parameters

1. Select the L2TP tab from the Resource Selector window.

2. In the Security Gateway area, use the pull-down tab of the Physical Interface field, to select the physical ethernet address of to be used for the Security Gateway emulator.

3. In the Security Gateway area, enter the starting IP address of the emulated Security Gateway Node in the Starting IP Address field. Note: This IP address must be selected from the pool of addresses associated with the physical interface selected. This is the starting address for a pool of Security Gateway IP addresses that can be used for emulating multiple Security Gateways.

4. In the Security Gateway area, enter the desired number of Security Gateway emulations in the No. IP (Max of 1000) field.Note: A separate L2TP tunnel is established for each security gateway. If using IPSec, an IPSec tunnel must be pre-configured for each tunnel using the same IP addresses.

5. In the Security Gateway area, select Default Routing or Specify Next Hop IP Address.


7. In the Security Gateway Port Number field, enter the desired port number for the Security Gateway.

8. In the System Under Test (Foreign Agent) L2TP field, use the pull-down tab to select a pre-configured SUT.

9. In the System Under Test (Foreign Agent) L2TP Port Number field, enter the desired port number for the SUT.

10. In the Tunnel Connect Rate (Sessions/Second) field, enter the desired tunnel connect rate.

11. In the Tunnel Disconnect Rate (Sessions/Second) field, enter the desired tunnel disconnect rate.

12. In the Tunnel Name field, enter the name to be used when setting up the L2TP tunnels.

13. In the Retries field, enter the desired number of retries to be attempted for a failed tunnel activation.

14. In the VPN Session ID field, enter the session ID value to be used during tunnel setup.



Measurements associated with the L2TP layer are defined in “L2TP Measurements” (Table 4-17).

Modifying PPP Protocol Parameters

For Simple IP, Simple IP VPN, FA Nodal and End-to-End MIP test configurations, the user may set up the PPP protocol parameters shown in and described in “PPP Protocol Configuration Parameters” (Table 3-21) by following the steps identified in Procedure 2-24.

Important: These parameters must be set up to match the expected and configured values at the PDSN-FA.

15. In the Starting Calling ID, enter the desired ID to be used as the starting calling ID. This value will be incremented for each session.

16. Click Apply to use the new L2TP parameters for the selected test case.

Procedure 2-23 Modify L2TP Protocol Parameters (Continued)


Figure 2-23 PPP Tab

Procedure 2-24 Modify PPP Protocol Parameters

1. Select the PPP or the PPP/L2TP (for Simple IP VPN test case) tab from the Resource Selector window.

2. In the Magic Number field, enter the magic number expected at the PDSN-FA.

3. In the Retries field, enter the number of retries to be attempted following a failed attempt to set up a PPP session.



Measurements associated with the PPP layer are defined in “PPP Measurements” (Table 4-7).

4. In the Authorization field, use the pull-down tab to select the desired authentication protocol. The options are None, Any, CHAP, or PAP.

If authorization is enabled:• In the User Name field, enter the user name to be sent from the

Mobile Node to the PDSN-FA for the PPP session. This name must be unique for each session. See “Variable Parameter Values” in Chap-ter 3 for instructions.

• In the Password field, enter the password to be used for the PPP ses-sions.

Note: The option Any, allows the use of either CHAP or PAP.

5. In the Synchronization Mode field, use the pull-down tab to select Async or Sync.

6. If Synchronization Mode is set to Async, use the pull-down tab in the ACCM field to select Enabled or Disabled.

If ACCM is enabled:• Use the pull-down tab in the Forced Equivalent field to select

Enabled or Disabled. • Enter the desired ACCM Hex value in the ACCM value (Hex for-

mat) (0x0 - 0xFFFFFFFF) field.

7. If Synchronization Mode is set to Async, use the pull-down tab in the Error Inject field to select error injection at the PPP layer. The options are None, Bad HDLC Checksum for all Data Packets, or Bad HDLC Checksum for all Control Packets.

Important: If error injection is selected, it will be applied to all PPP sessions within the configured test case.

8. Use the pull-down tab in the Van Jacobson Compression field to select Enabled or Disabled.

If Van Jacobson Compression is Enabled, use the pull-down tab in the Van Jacobson Slot ID Compression to select Enabled or Disabled.

9. Click Apply to use the new PPP parameters for the selected test case.

Procedure 2-24 Modify PPP Protocol Parameters (Continued)



Chapter 3

Test Parameters

This chapter provides detailed information on the test case configuration parameters used to setup and modify existing test cases.

In this chapter...This chapter contains the following topics:

Purpose....111

Variable Parameter Values....111

Simple IP Parameters....111

Simple IP VPN Parameters....112

MIP FA Nodal Parameters....113

MIP HA Nodal Parameters....115

End-to-End Mobile IP Parameters....117

Common Parameters....118

SUT Query Parameters....119

Test Activity Parameters....122

Capacity Parameters....122

Session Loading Parameters....124

Session Loading with Mobility Parameters....125

Session Loading Rate Parameters....127

Session Activation Rate Parameters....128

Intra-PDSN Parameters....129

Intra-PDSN Rate Parameters....131

MIP Revocation Parameters....133

Inter-PDSN Parameters....135

Inter-PDSN Rate Parameters....138

L2TP Parameters....140

Test Parameters


RP Parameters....142

PPP Parameters....146

Data Traffic Parameters....148

MIP Parameters....164

MIP Parameters for HA Nodal....168

Test ParametersPurpose


PurposeThe CPTS allows the user to modify the configurable parameters that are used by each test case. These parameters contain default values that are defined by the CPTS. The user can view and change any of the default parameters using the GUI interface. Certain parameters must be provided by the user and do not have default values.

The user can modify any of the following test configuration information as applicable.

Important: The range values shown in the following tables are based on a standard server configuration with a standard license. Some range values may be less, based on platform or license issued.

Variable Parameter ValuesCertain parameters require that a unique value is provisioned for each session. The system accomplishes this through an auto-increment feature that is activated when a value is entered in one of three available formats.

• sometext - The value “sometext” is used in every session.

• @sometext - If the first character is “@,” then the system prepends spcoastn to the user-supplied value, where n is incremented for each session and begins at either 1 or the session number depending on whether the value is used in the PPP User Name parameter or the MIP NAI parameter.

• somete#xt, somename#@sometext, or somename@some#text - When “#” is included in the user-supplied value, it will be replaced by an incrementing value which begins at either 1 or the session number depending on whether the value is used in the PPP User Name parameter or the MIP NAI parameter.

• some#(nnn)name@sometext - Similar to the example above, but the starting point for the incremented value is nnn. The value to be incremented can accommodate 15 digits and must be enclosed in parentheses.

Note: The increment flag (#) can be placed at any position in the text string, but only one flag per string is permitted.

The following parameters are supported by the auto-increment feature:

• User Name (see “PPP Parameters” and “Data Traffic Parameters”)

• NAI (see “MIP Parameters” and “MIP Parameters for HA Nodal”)

Simple IP ParametersThe user can modify any of the following test configuration information when performing tests in a Simple IP test configuration.

Test ParametersSimple IP VPN Parameters


Table 3-1 describes the Simple IP test configuration parameters.

In addition to the configuration information shown in Table 3-1, the user can modify the configuration information in the following tables:

• “Common Parameters” (Table 3-6)

• “Test Activity Configuration Parameters” (Table 3-8)

• “Capacity Parameters” (Table 3-9)

• “Session Loading Parameters” (Table 3-10)

• “Session Loading Rate Parameters” (Table 3-12)

• “Session Activation Rate Parameters” (Table 3-13)

• “Intra-PDSN Parameters” (Table 3-14)

• “Intra-PDSN Rate Parameters” (Table 3-15)

• “Session Loading With Mobility Parameters” (Table 3-11)

• “RP Protocol Configuration Parameters” (Table 3-20)

• “PPP Protocol Configuration Parameters” (Table 3-21)

• “Data Traffic Parameters” (Table 3-22).

• “SUT Query Configuration Parameters” (Table 3-7)

Simple IP VPN ParametersThe user can modify any of the following test configuration information when performing tests in a Simple IP VPN test configuration.

Table 3-2 describes the Simple IP VPN test configuration parameters.

Table 3-1 Simple IP Parameters

Parameter Default Value

Range Description

System Under Test (Foreign Agent)

N/A N/A Identifies the system to be tested. Use the pull-down tab to select a pre-configured System Under Test.

Test ParametersMIP FA Nodal Parameters




• “L2TP Protocol Configuration Parameters” (Table 3-19)











• “Data Traffic Parameters” (Table 3-22).


MIP FA Nodal ParametersTable 3-3 describes the MIP FA Nodal test configuration parameters.

Table 3-2 Simple IP VPN Parameters


Range Description


N/A N/A Identifies the system to be tested. Use the pull-down tab to select a pre-configured System Under Test.

Test ParametersMIP FA Nodal Parameters


Table 3-3 MIP FA Nodal Parameters


Range Description


N/A N/A Identifies the system to be tested.

HA Node Address N/A N/A An area for entering the physical interface and logical IP address for the HA node emulator.

Physical Interface N/A N/A A pull-down tab for selecting a physical ethernet port for the emulated HA node.

IP Address N/A N/A The emulated HA node’s virtual IP address, selected from a pool of IP addresses associated with the physical interface.

Default Routing N/A N/A A button for selecting the test server’s default routing as the route to be used by the emulated HA node. Refer to the Landslide 2500 Installation Guide for instructions on configuring the routing protocols and static routes used by a test server.


N/A N/A A button for selecting a specific route for the emulated HA node to use. This allows the user to force traffic over a specific ethernet port. If this button is selected, the adjacent field is used to enter the IP address of the next hop.

HA Home Address Pool

0.0.0.0 N/A Appears on the MIP HA tab during FA Nodal testing. Starting IP address for the HA Home Address Pool. This address is incremented to the next valid IP address for each mobile node, based on the subnet mask entered below.

Subnet Mask 0.0.0.0 N/A Appears on the MIP HA tab during FA Nodal testing. Subnet Mask for the HA Home Address Pool IP addresses.Note: The subnet must be large enough to accommodate the total number of sessions specified in the General tab.

Test ParametersMIP HA Nodal Parameters











• “MIP Revocation Parameters” (Table 3-16)




• “MIP Parameters” (Table 3-23)

• “Data Traffic Parameters” (Table 3-22)


MIP HA Nodal ParametersTable 3-4 describes the MIP HA Nodal test configuration parameters.

Table 3-4 MIP HA Nodal Parameters


Range Description

System Under Test (Home Agent) IP

N/A N/A Identifies the system to be tested.

Foreign Agent Node Address

N/A N/A An area for entering the physical interface and logical IP address information for the PDSN-FA node emulator.

Physical Interface N/A N/A A pull-down tab for selecting a physical ethernet port for the emulated PDSN-FA node.

Test ParametersMIP HA Nodal Parameters









• “Inter-PDSN Parameters” (Table 3-17)

• “Inter-PDSN Rate Parameters” (Table 3-18)

• “MIP Revocation Parameters” (Table 3-16)


• “MIP Parameters for HA Nodal Testing” (Table 3-24)



IP Address N/A N/A The emulated PDSN-FA node’s virtual IP address, selected from a pool of IP addresses associated with the physical interface.

Default Routing N/A N/A A button for selecting the test server’s default routing as the route to be used by the emulated PDSN-FA node. Refer to the Landslide 2500 Installation Guide for instructions on configuring the routing protocols and static routes used by a test server.


N/A N/A A button for selecting a specific route for the emulated PDSN-FA node to use. This allows the user to force traffic over a specific ethernet port. If this button is selected, the adjacent field is used to enter the IP address of the next hop.

Foreign Agent Port Number

434 N/A Identifies the port number to be used with the PDSN-FA emulator IP address.

Table 3-4 MIP HA Nodal Parameters (Continued)


Range Description

Test ParametersEnd-to-End Mobile IP Parameters


End-to-End Mobile IP ParametersTable 3-5 describes the MIP End-to-End test configuration parameters.










• “Inter-PDSN Parameters” (Table 3-17)

• “Inter-PDSN Rate Parameters” (Table 3-18)




Table 3-5 MIP End-to-End Parameters


Range Description


N/A N/A Identifies the PDSN-FA system to be tested.

System Under Test (Home Agent)

N/A N/A Identifies the HA system to be tested.

SUT HA Port Number

434 N/A Specifies the port number to be used with the SUT HA IP address.

Secondary Home Agent

Disabled N/A Enables the ability to specify a secondary home agent.

System Under Test (Home Agent #2)

N/A N/A Conditional on Secondary Home Agent set to Enabled. Used to specify an alternate HA when the primary HA is not reachable.

Test ParametersCommon Parameters


• “MIP Parameters” (Table 3-23)



Common ParametersTable 3-6 describes the common test configuration parameters. These parameters are configured from the General tab.

Table 3-6 Common Parameters


Range Description

Number of Sessions

1 1 - 200,000

Number of simultaneous sessions to be established.

Session Connect Rate (Sessions/Second)

1 1 - 1,000 Rate in sessions/second to be used for establishing sessions.Note: When using an HA Nodal test, the upper limit of this rate is 4,000.

Session Disconnect Rate (Sessions/Second)

1 1 - 1,000 Rate in sessions/second to be used for deactivation of sessions.Note: When using an HA Nodal test, the upper limit of this rate is 4,000.

Session Rate Interval Distribution

Fixed N/A Selects the distribution model to be used for the Session Connect and Session Disconnect Rates. Options are Fixed, Uniform, Normal and Poisson. Refer to “Glossary” in “About this Guide” for model definitions and examples.

Maximum Deviation from Mean (Percent of Mean)

10 1-99 Conditional on Uniform or Poisson selected as Session Rate Interval Distribution model. Limits the standard deviation in the selected distribution model.

Standard Deviation (Percent of Mean)

0 0 - 100 Conditional on selection of Normal distribution model. Sets the standard deviation to be used for the normal distribution model.

Test ParametersSUT Query Parameters


SUT Query ParametersTable 3-7 describes the test configuration parameters associated with the SUT Query capability. These parameters are configured from the SUT Query tab and are available when the SUT Query field is set to Enabled.

Table 3-7 SUT Query Configuration Parameters


Range Description

SUT Query Disabled N/A Enables automatic query of SUT for CPU real-time usage or a user-defined periodic query. Options are Enabled or Disabled.

Target SUT Prompt )# N/A The expected prompt from the target SUT that is key for sending user-defined commands.

Query CPU Utilization

Disabled N/A Enables automatic query of the SUT CPU Usage. Options are Enabled or Disabled.

Query CPU Command

show overload cpu cmc p0 mode= brief

N/A Conditional on Query CPU Utilization set to Enabled. The command string to be used for the SUT Query.Note: The user must enter the exact command string to be sent to the SUT following the expected prompt.

Query CPU Response Search Pattern

CPU N/A Conditional on Query CPU Utilization set to Enabled. The string to be used for parsing the response tokens from the CPU.

Query CPU Response Offset from Search Pattern

3 N/A Conditional on Query CPU Utilization set to Enabled. Points the test to the starting point for the parsing area of the CPU response. The number represents the location of the target token in relation to the string entered in the Query CPU Response Search Pattern field.

SUT Query Time (Seconds)

15 5 - 100 Conditional on Query CPU Utilization set to Enabled. The interval in seconds between queries.



Dynamic Rate Adjustment

Disabled N/A Conditional on Query CPU Utilization set to Enabled. Enables automatic rate adjustment of session connect rate, based on SUT CPU real-time usage. Options are Enabled or Disabled.

Target SUT CPU Rate (Percent)

78 1 - 100 Conditional on Dynamic Rate Adjustment set to Enabled. Sets the target for SUT CPU usage. If current usage is less than target, session rate is increased. If current usage is greater than target, session rate is decreased.

Session Connect Adjustment Rate (Sessions/Second)

1 N/A Conditional on Dynamic Rate Adjustment set to Enabled. The rate in sessions/second that session activation rate is increased or decreased based on SUT CPU usage.

Session Disconnect Adjustment Rate (Sessions/Second)

1 N/A Conditional on Dynamic Rate Adjustment set to Enabled. The rate in sessions/second that session deactivation rate is increased or decreased based on SUT CPU usage.

Dynamic Mobility Adjustment Rate (Sessions/Second)

1 N/A Conditional on Dynamic Rate Adjustment set to Enabled. The rate in sessions/second that mobility events are increased or decreased based on SUT CPU usage.

Accelerated Dynamic Rate Adjustment

Disabled N/A Conditional on Dynamic Rate Adjustment set to Enabled. Enables accelerated dynamic rate adjustment if the SUT CPU usage is outside of normal dynamic adjustment range. Options are Enabled or Disabled.

Table 3-7 SUT Query Configuration Parameters (Continued)


Range Description



Accelerated Rate Threshold (+/-)

10 2 - 50 Conditional on Accelerated Dynamic Rate Adjustment set to Enabled. Applies a threshold range to the Target CPU Rate. If the SUT CPU usage is within this threshold, then the normal adjustment rate is applied. If the returned value is outside of this range, then the accelerated adjustment rate is used.

Accelerated Session Connect Adjustment Rate (Sessions/Second)

5 N/A Conditional on Accelerated Dynamic Rate Adjustment set to Enabled. The accelerated adjustment rate for session connects.

Accelerated Session Disconnect Adjustment Rate (Sessions/Second)

5 N/A Conditional on Accelerated Dynamic Rate Adjustment set to Enabled. The accelerated adjustment rate for session disconnects.

Allow Adjusted Rate to Exceed Connect/Disconnect Rate

Disabled N/A Conditional on Dynamic Rate Adjustment set to Enabled. Allows the adjusted rate to exceed the rate specified in the General tab for session connect or disconnect rate. Options are Enabled or Disabled.

Periodic Query Disabled N/A Enables periodic query of the SUT or a Test Server during a test. Options are Enabled or Disabled.

Periodic Query Target Platform

SUT N/A Conditional on Periodic Query set to Enabled. The target platform for the query. The options are SUT or Test Server.

Periodic Query Command

N/A N/A Conditional on Periodic Query set to Enabled. The file name of script to be executed for the query.

Periodic Query Time (Seconds)

15 5 - 100 Conditional on Periodic Query set to Enabled. The time interval between queries of the target platform.

Table 3-7 SUT Query Configuration Parameters (Continued)


Range Description

Test ParametersTest Activity Parameters


Test Activity ParametersTable 3-8 describes the test activity configuration options. These parameters are selected on the Test Activity tab.

Capacity ParametersTable 3-9 describes the Capacity Test configuration options. These parameters are available when Capacity is the selected Test Activity.

Table 3-8 Test Activity Configuration Parameters


Range Description

Test Activity Capacity N/A Selects the desired test activity. The options are Capacity, Session Loading Test, Session Loading Rate Test, Session Activation Rate, Intra-PDSN, Intra-PDSN Rate, Inter-PDSN, Inter-PDSN Rate, MIP Revocation, and Session Loading With Mobility.Note: The actual test activities shown are dependent on the test case selected.

Test ParametersCapacity Parameters


Table 3-9 Capacity Parameters


Range Description

Session Start Retries

Enabled N/A Enables retry attempts after a failure to establish a session. The options are Enabled or Disabled.

If a session fails while being established, the CPTS increments a failed session counter. The test system makes one attempt to start each session, and then it optionally tries to restart any sessions that had previously failed. The session restart is only attempted if the Session Start Retries feature is set to Enabled. The test server continues restarting sessions until all the sessions have been established or the session failure rate hits 100%.

A session failure includes, but is not limited to, the following types of failures:• Failure to reach established state• Any failure after session established• Failure to ping network host after ses-

sion established, if data verification selected

• Session failure after successful ping

Test ParametersSession Loading Parameters


Session Loading ParametersTable 3-10 describes the Session Loading Test configuration options. These parameters are available when Session Loading is the selected Test Activity.

Disconnect Initiated By

Mobile Node

N/A The emulated mode for disconnecting sessions. The options are Mobile Node, PCF, and Mobile Node PPP.

Mobile Node Disconnect process:

The test server sends a registration request with the lifetime set to zero. This causes the MIP layer to de-register. Then, the PPP layer sends a terminate request to the PDSN. After the test receives the terminate acknowledgement, the test tears down the RP layer. This is initiated by a registration request with the lifetime of zero. As a result the PDSN tears down the RP layer and everything is disconnected.

Mobile Node PPP Disconnect process:

Same as above, except the disconnect begins with the PPP layer first sending a terminate request. In this case the MIP layer is left hanging and does not get a chance to gracefully disconnect.

PCF Disconnect process:

Same as in the above scenarios, but this time the disconnect begins with the RP layer sending a lifetime of zero to initiate the disconnect request. In this case both MIP and PPP are left hanging and do not get a chance to gracefully terminate.

Table 3-9 Capacity Parameters (Continued)


Range Description

Test ParametersSession Loading with Mobility Parameters


Session Loading with Mobility ParametersTable 3-11 describes the Session Loading With Mobility Test configuration options. These parameters are available when Session Loading With Mobility is the selected Test Activity.

Important: When Session Loading with Mobility is selected as the test activity, a new tab, RP #2, is added to the Resource Selector window. See “RP Protocol Configuration Parameters” (Table 3-20).

Table 3-10 Session Loading Parameters


Range Description

Session Pending Time (Seconds)

1000 1 - 100,000

The wait time between when a session is deactivated and the start of a new activation.

Session Hold Times (Seconds)

1000 1 - 100,000

The length of time a session is maintained following an activation. At the end of this time, the session is deactivated.

Table 3-11 Session Loading With Mobility Parameters


Range Description

Session Pending Time (Seconds)

1000 1 - 100,000

The wait time between a session deactivation and the start of a new activation.

Session Hold Time (Seconds)

1000 1 - 100,000

The length of time a session is maintained following an activation. At the end of this time, the session is deactivated.

Handoff Time (Seconds)

60 1 - 10,000 The length of time after a session is activated before the handoff event occurs. This is also used as the delay value between handoffs, if multiple handoffs are specified.

Number of Handoffs

2 1 - 10,000 The number of handoff events to perform for each session activation.

Test ParametersSession Loading with Mobility Parameters


Mobility Type Intra-PDSN

N/A The type of mobility event. The options available depend on the test configuration. For Simple IP and FA Nodal test cases, Intra-PDSN is the only option. For an HA nodal test case, Inter-PDSN is the only option. For an End-to-End test case both Intra-PDSN and Inter-PDSN are options.


N/A N/A Conditional on Inter-PDSN selected for Mobility Type in an End-to-End test case. The options will include SUTs that have been defined for the system.


N/A N/A Conditional on Inter-PDSN selected for Mobility Type in an HA Nodal test case. An area for entering the physical interface and logical IP address for the second PDSN-FA node emulator.

Physical Interface N/A N/A Conditional on Inter-PDSN selected for Mobility Type in an HA Nodal test case. A pull-down tab for selecting the physical ethernet port to be used for the emulated second PDSN-FA node.

IP Address N/A N/A Conditional on Inter-PDSN selected for Mobility Type in an HA Nodal test case. The emulated second PDSN-FA node’s virtual IP address, selected from a pool of IP addresses associated with the physical interface.

Default Routing N/A N/A Conditional on Inter-PDSN selected for Mobility Type in an HA Nodal test case.

A button for selecting the test server’s default routing as the route to be used by the emulated second PDSN-FA node. Refer to the Landslide 2500 Installation Guide for instructions on configuring the routing protocols and static routes used by a test server.

Table 3-11 Session Loading With Mobility Parameters (Continued)


Range Description

Test ParametersSession Loading Rate Parameters


Session Loading Rate ParametersTable 3-12 describes the Session Loading Rate Test configuration parameters. These parameters are available when Session Loading Rate is the selected Test Activity.


N/A N/A Conditional on Inter-PDSN selected for Mobility Type in an HA Nodal test case. A button for selecting a specific route for the emulated second PDSN-FA node to use. This allows the user to force traffic over a specific ethernet port. If this button is selected, the adjacent field is used to enter the IP address of the next hop.


434 N/A Conditional on Inter-PDSN selected for Mobility Type in an HA Nodal test case. Field for entering the desired port number of the emulated second PDSN-FA node.

Table 3-11 Session Loading With Mobility Parameters (Continued)


Range Description

Table 3-12 Session Loading Rate Parameters


Range Description

Initial Pending Time (Seconds)

100 1 - 10,000 The initial wait time between a session deactivation and the start of a new activation.

Initial Hold Time (Seconds)

100 1 - 10,000 The initial length of time a session is maintained following an activation. At the end of this time, the session is deactivated.

Pending Backoff Amount (Seconds)

1 1 - 1,000 The number of seconds to subtract from the Initial Pending Time when a run has been completed without exceeding the error threshold.

Test ParametersSession Activation Rate Parameters


Session Activation Rate ParametersTable 3-13 describes the Session Activation Rate Test configuration parameters. These parameters are available when Session Activation Rate is the selected Test Activity.

Hold Backoff Amount (Seconds)

1 1 - 1,000 The number of seconds to subtract from the Initial Hold Time when a run has been completed without exceeding the error threshold.

Session Loading Run Time (Seconds)

1000 1 - 10,000 The amount of time to wait after a run before checking the error threshold and either adjusting the activation rate and repeating the last run, or starting the next run.Note: This value should be a minimum of 10 times the Initial Hold Pending Time for best results.

Error Threshold Percentage

1 1 - 99 The error threshold to determine whether further adjustments should be made to the Initial Hold Time and Initial Pending Time. It is a percentage of sessions that encounter errors. If this threshold is exceeded, the test continues to run at the same rate until either the run is completed within the error threshold or the test is manually stopped. If a run is subsequently completed within the error threshold, the test continues to decrease the pending and hold times.

Table 3-12 Session Loading Rate Parameters (Continued)


Range Description

Test ParametersIntra-PDSN Parameters


Intra-PDSN ParametersTable 3-14 describes the Intra-PDSN Test configuration parameters. These parameters are available when Intra-PDSN is the selected Test Activity.

Important: When Intra-PDSN is selected as the test activity, a new tab, RP #2, is added to the Resource Selector window. See “RP Protocol Configuration Parameters” (Table 3-20).

Table 3-13 Session Activation Rate Parameters


Range Description

Activation Method By block N/A Determines whether a run of session activations is based on the number of total sessions, By block, or the amount of time, By time, requested for each run.

Block Size 10 1 - 200,000

Conditional on By block selected for Activation Method. The number of total sessions to be activated during each run.

Time Period (Seconds)

10 1 - 86,400 Conditional on By time selected for Activation Method. This value defines the length of the activation run.

Error Threshold Percentage (1-99)

10 1 - 99 The percentage of errors that must occur before reducing the activation rate.

Wait Time (Seconds)

5 1 - 100 The amount of time to wait after an activation run before checking the error threshold and either reducing the activation rate and repeating the last round of activations, or starting the next activation run.

Back Off Rate (Percent)

10 1 - 100 The amount of reduction in the context activation rate after the error threshold has been exceeded. For example, if this value is 10%, and the current activation rate is 100 sessions per second, the rate is reduced to 90 sessions per second after exceeding the error threshold.

Test ParametersIntra-PDSN Parameters


Table 3-14 Intra-PDSN Parameters

Parameter Default Value Range Description

Mobility Delay Time (Seconds)

10 1 - 100,000

The number of seconds to wait after a session is started, or after all sessions are established, before performing a handoff.

Mobility Start Type When All Sessions Started

N/A The method to be used for starting handoff events. The options are When All Sessions Started (no mobility events occur until all requested sessions have been started) or When Session Started (mobility events are initiated for each session as it is started).

Mobility Rate (Sessions/Seconds)

1 0 - 1,000 Conditional on When All Sessions Started selected as Mobility Start Type. The rate at which mobility events occur.


Fixed N/A Conditional on When All Sessions Started selected as Mobility Start Type. The distribution model to be applied to the Mobility Rate. The options are Fixed, Uniform, Normal, and Poisson. Refer to “Glossary” in “About this Guide” for model definitions and examples.


10 1-99 Conditional on Uniform or Poisson selected as Mobility Rate Interval Distribution. Limits the standard deviation in the selected distribution model to a percentage of the mean.

Test ParametersIntra-PDSN Rate Parameters


Intra-PDSN Rate ParametersTable 3-15 describes the Intra-PDSN Rate test configuration parameters. These parameters are available when Intra-PDSN Rate is the selected Test Activity.

Important: When Intra-PDSN Rate is selected as the test activity, a new tab, RP #2, is added to the Resource Selector window. See “RP Protocol Configuration Parameters” (Table 3-20).


10 0-100 Conditional on Normal selected as Mobility Rate Interval Distribution. The standard deviation to be used in the model.

Handoff Mode Single Handoff

N/A Conditional on When Session Started selected as Mobility Start Type. The options are Single Handoff or Continuous Handoff.Note: When Continuous Handoff is selected, Mobility Delay Time is used to trigger the mobility events for each session.

Table 3-14 Intra-PDSN Parameters (Continued)


Table 3-15 Intra-PDSN Rate Parameters



10 1 - 100,000

The number of seconds to wait before performing a handoff.


N/A The method to be used for starting handoff events. The only option available for Intra-PDSN Rate is When All Sessions Started (no handoffs occur until all requested sessions have been started).


1 0 - 1,000 The rate at which handoffs occur.

Test ParametersIntra-PDSN Rate Parameters



Fixed N/A The distribution model to be applied to the Mobility Rate. The options are Fixed, Uniform, Normal, and Poisson. Refer to “Glossary” in “About this Guide” for model definitions and examples.


10 1-99 Conditional on Uniform or Poisson selected as Mobility Rate Interval Distribution. Limits the standard deviation in the selected distribution model to a percentage of the mean.


10 0-100 Conditional on Normal selected as Mobility Rate Interval Distribution. The standard deviation to be used in the model.

Activation Method By block N/A Determines whether a run of intra-PDSN handoffs is based on the number of total sessions handed off, By block, or the amount of time, By time, requested for each run.

Block Size 10 1 - 200,000

Conditional on By block selected for Activation Method. The number of total sessions handed off during each run.


10 1 - 86,400 Conditional on By time selected for Activation Method. The length of time to handoff sessions.


10 1 - 99 The percentage of errors that must occur before reducing the Mobility Rate.

Table 3-15 Intra-PDSN Rate Parameters (Continued)


Test ParametersMIP Revocation Parameters


MIP Revocation ParametersTable 3-16 describes the MIP Revocation Test configuration parameters. These parameters are available when MIP Revocation is the selected Test Activity.

Wait Time (Seconds)

5 1 - 100 The amount of time to wait before checking the error threshold and, if necessary, adjusting the Mobility Rate.


10 1 - 100 The amount by which the Mobility Rate will be reduced after the Error Threshold Percentage has been exceeded. For example, if this value is 10%, and the current Mobility Rate is 100 sessions per second, the rate is reduced to 90 sessions per second after exceeding the error threshold.

Table 3-15 Intra-PDSN Rate Parameters (Continued)


Table 3-16 MIP Revocation Parameters


RSE Flag 0 0 - 1 A 1 indicates the Revocation Support Extension should be included in the Registration Request and Registration Reply messages. Options are 0 or 1.

RSE Type 137 128 - 255 The type value to be used when constructing the Revocation Support Extension.

Test ParametersMIP Revocation Parameters


Inform Bit 0 0 - 1 Indicates whether the mobile node should be informed of the revocation. Options are 0 or 1. A 0 indicates that it should.

When set to 1, the FA agrees to allow the HA to be involved in determining whether the MN should be informed of the revocation. When set to 0, the FA determines, based on its own provisioning, whether the MN should be informed of the revocation.

RSE Length 6 0 - 1,000 Indicates the length of the Revocation Support Extension.

RRV Type 7 0 - 1,000 Indicates the message type value to be used for Registration Revocation (RRV) messages.

RRVA Type 15 0 - 1,000 Indicates the message type value to be used for Registration Revocation Acknowledgement (RRVA) messages.

Revocation Time (Seconds)

10 0 - 10,000 The period to wait before beginning revocations.

Revocation Start Type

When All Sessions Started

N/A Determines when revocations begin. Options are When All Sessions Started (revocation processing does not begin until all requested sessions have been started) or When Session Started (revocation processing begins for each session as it is started).

Revocation Rate (Sessions/Second)

1 0 - 1,000 Conditional on When All Sessions Started selected as Revocation Start Type. Rate in sessions/second that revocations are processed.

Table 3-16 MIP Revocation Parameters (Continued)


Test ParametersInter-PDSN Parameters


Inter-PDSN ParametersTable 3-17 describes the Inter-PDSN Test configuration parameters. These parameters are available when Inter-PDSN is the selected Test Activity.

Revocation Rate Interval Distribution

Fixed N/A Conditional on When All Sessions Started selected as Revocation Start Type. Selects the distribution model to be applied to the Revocation Rate. The options are Fixed, Uniform, Normal, and Poisson. Refer to “Glossary” in “About this Guide” for model definitions and examples.


10 1-99 Conditional on Uniform or Poisson selected as Revocation Rate Interval Distribution. Limits the standard deviation in the selected distribution model.


10 0-100 Conditional on Normal selected as Revocation Rate Interval Distribution. Sets the standard deviation for the model.

Table 3-16 MIP Revocation Parameters (Continued)


Table 3-17 Inter-PDSN Parameters



N/A N/A Conditional on End-to-End Mobile IP test case. A pull-down tab for selecting a pre-configured system under test.


N/A N/A Conditional on HA Nodal test case. An area for entering the physical interface and logical IP address for the second PDSN-FA node emulator required to support inter-PDSN handoff.



Physical Interface N/A N/A Conditional on HA Nodal test case. A pull-down tab for selecting a physical ethernet port for the emulated second PDSN-FA node.

IP Address N/A N/A Conditional on HA Nodal test case. The emulated second PDSN-FA node’s virtual IP address, selected from a pool of IP addresses associated with the physical interface IP address.

Default Routing N/A N/A Conditional on HA Nodal test case. A button for selecting the test server’s default routing as the route to be used by the emulated second PDSN-FA node. Refer to the Landslide 2500 Installation Guide for instructions on configuring the routing protocols and static routes used by a test server.


N/A N/A Conditional on HA Nodal test case. A button for selecting a specific route for the emulated PDSN-FA node to use. This allows the user to force traffic over a specific ethernet port. If this button is selected, the adjacent field is used to enter the IP address of the next hop.


434 N/A Conditional on HA Nodal test case. Port number to be used with Foreign Agent #2’s IP address.


10 1 - 100,000

The number of seconds to wait after a session is started, or after all sessions are started before performing a handoff.

Table 3-17 Inter-PDSN Parameters (Continued)





N/A The method to be used for starting mobility events. The options are When All Sessions Started (no mobility events occur until all requested session activations have been started) or When Session Started (mobility events are initiated for each session as it is started).


1 0 - 1000 Conditional on When All Sessions Started selected as Mobility Start Type. Rate at which mobility events occur.Note: When using an HA Nodal test, the upper limit of this rate is 4,000.


Fixed N/A Conditional on When All Sessions Started selected as Mobility Start Type. Selects the distribution model to be used for the Mobility Rate. The options are Fixed, Uniform, Normal, and Poisson. Refer to “Glossary” in “About this Guide” for model definitions and examples.


10 1-99 Conditional on Uniform or Poisson selected as Mobility Rate Interval Distribution. Limits the standard deviation in the selected distribution model.


10 0-100 Conditional on Normal selected as Mobility Rate Interval Distribution. Sets the standard deviation to be used in the model.

Handoff Mode Single Handoff

N/A Conditional on When Session Started selected as Mobility Start Type. Selects either a single handoff per session, or continuous handoffs. Options are Single Handoff or Continuous Handoff.

Table 3-17 Inter-PDSN Parameters (Continued)


Test ParametersInter-PDSN Rate Parameters


Inter-PDSN Rate ParametersTable 3-18 describes the Inter-PDSN Rate Test configuration parameters for use during HA Nodal testing or End-to-End Mobile IP testing. These parameters are available when Inter-PDSN is the selected Test Activity.

Table 3-18 Inter-PDSN Rate Parameters


Range Description


N/A N/A Conditional on End-to-End Mobile IP test. A pull-down tab for selecting a pre-configured system under test.


N/A N/A Conditional on HA Nodal test. An area for entering the physical interface and logical IP address for the emulated second PDSN-FA node required to support inter-PDSN handoff.

Physical Interface N/A N/A Conditional on HA Nodal test. A pull-down tab for selecting a physical ethernet port for the emulated second PDSN-FA node.

IP Address N/A N/A Conditional on HA Nodal test. The emulated second PDSN-FA node’s virtual IP address, selected from a pool of IP addresses associated with the physical interface.

Default Routing N/A N/A Conditional on HA Nodal test. A button for selecting the test server’s default routing as the route to be used by the emulated second PDSN-FA node. Refer to the Landslide 2500 Installation Guide for instructions on configuring the routing protocols and static routes used by a test server.


N/A N/A Conditional on HA Nodal test. A button for selecting a specific route for the emulated PDSN-FA node to use. This allows the user to force traffic over a specific ethernet port. If this button is selected, the adjacent field is used to enter the IP address of the next hop.

Test ParametersInter-PDSN Rate Parameters



434 N/A Conditional on HA Nodal test. Port number to be used with Foreign Agent #2’s IP address.


10 1 - 100,000

The number of seconds to wait after a session is started, or after all sessions have been started, before performing a handoff.


N/A Determines when handoffs begin. The only option is When All Sessions Started (handoffs begin when all requested sessions have been started).


1 0 - 1,000 The rate at which mobility events occur.Note: When using an HA Nodal test, the upper limit of this rate is 4,000.


Fixed N/A The distribution model to be applied to the Mobility Rate. The options are Fixed, Uniform, Normal, and Poisson. Refer to “Glossary” in “About this Guide” for model definitions and examples.


10 1-99 Conditional on Uniform or Poisson selected as Mobility Rate Interval Distribution. Limits the standard deviation in the selected distribution model.


10 0-100 Conditional on Normal selected as Mobility Rate Interval Distribution. Sets the standard deviation for the model.

Activation Method By block N/A Determines whether a run of inter-PDSN handoffs is based on the number of total sessions handed off, By block, or the amount of time, By time, requested for each run.

Block Size 10 1 - 200,000

Conditional on By block selected for Activation Method. Defines the number of total sessions to be handed off during each run.

Table 3-18 Inter-PDSN Rate Parameters (Continued)


Range Description

Test ParametersL2TP Parameters


L2TP ParametersTable 3-19 describes the L2TP Protocol configuration parameters.


10 1 - 86,400 Conditional on By time selected for Activation Method. Defines the total length of the run.


10 1 - 99 Defines the percentage of errors that must occur before reducing the Mobility Rate.

Wait Time (Seconds)

5 1 - 100 The amount of time to wait before checking the error threshold and, if necessary, adjusting the Mobility Rate.


10 1 - 100 The amount by which the Mobility Rate will be reduced after the Error Threshold Percentage has been exceeded. For example, if this value is 10%, and the current Mobility Rate is 100 sessions per second, the rate is reduced to 90 sessions per second after exceeding the error threshold.

Table 3-18 Inter-PDSN Rate Parameters (Continued)


Range Description

Table 3-19 L2TP Protocol Configuration Parameters


Range Description

Security Gateway N/A N/A An area for entering the IP information for the emulated security gateway.

Physical Interface N/A N/A A pull-down tab for selecting a physical ethernet IP address for the emulated security gateway.

Starting IP Address N/A N/A The security gateway’s virtual IP address, selected from a pool of IP addresses associated with the physical interface. If more than one No. IPs is selected, this will be the starting security gateway address.

Test ParametersL2TP Parameters


No. IPs (Max of 1000)

1 1 - 1000 The number of security gateway nodes to be emulated.

Default Routing N/A N/A A button for selecting the test server’s default routing as the route to be used by the emulated security gateway. Refer to the Landslide 2500 Installation Guide for instructions on configuring the routing protocols and static routes used by a test server.


N/A N/A A button for selecting a specific route for the emulated security gateway to use. This allows the user to force traffic over a specific ethernet port. If this button is selected, the adjacent field is used to enter the IP address of the next hop.

Security Gateway Port Number

1701 N/A The desired IP port number for the security gateway.

System Under Test (Foreign Agent) L2TP

N/A N/A A pull-down tab for selected a pre-configured system under test.

System Under Test (Foreign Agent) L2TP Port Number

1701 N/A The desired IP port number for the L2TP tunnel.

Tunnel Connect Rate (Sessions/Second)

1 N/A The desired tunnel connect rate.

Tunnel Disconnect Rate (Sessions/Second)

1 N/A The desired tunnel disconnect rate.

Tunnel Name tunnel name

N/A The tunnel name to be used during tunnel setup.

Retries 3 N/A The number of times to retry setting up an unsuccessful tunnel attempt.

Table 3-19 L2TP Protocol Configuration Parameters (Continued)


Range Description

Test ParametersRP Parameters


RP ParametersTable 3-20 describes the RP Protocol configuration parameters. When a test involves mobility (Intra-PDSN, Intra-PDSN Rate, Inter-PDSN, Inter-PDSN Rate, or Session Loading With Mobility), an RP#2 tab is presented to configure the RP protocol for the second PDSN-FA or PCF node.

VPN Session ID 1 N/A The session ID to be used when setting up the VPN tunnels.

Starting Calling ID 300000 N/A The calling ID to be used when setting up sessions through the L2TP VPN tunnel.Note: This value is incremented for each session.

Table 3-19 L2TP Protocol Configuration Parameters (Continued)


Range Description

Table 3-20 RP Protocol Configuration Parameters


Range Description

RP Type Open N/A Denotes the RP protocol to use for testing.

Open RP Conditional Parameters

PCF Node Address N/A N/A An area for entering the physical interface and logical IP address information for the emulated PCF node.

Physical Address N/A N/A A pull-down tab for selecting the physical port for use as the emulated PCF node.

Starting IP Address N/A N/A The PCF node’s virtual IP address, selected from a pool of IP addresses associated with the physical interface. If more than one PCF node is configured, this will serve as the starting IP address.

Number of PCFs (Max of 1000)

1 1 - 1000 The total number of PCF(s) to be configured.



Default Routing N/A N/A A button for selecting the test server’s default routing as the route to be used by the emulated PCF node. Refer to the Landslide 2500 Installation Guide for instructions on configuring the routing protocols and static routes used by a test server.


N/A N/A A button for selecting a specific route for the emulated PCF node to use. This allows the user to force traffic over a specific ethernet port. If this button is selected, the adjacent field is used to enter the IP address of the next hop.

PCF Node Port Number

699 N/A Port number to be used with the PCF Node IP address.

System Under Test (Foreign Agent) Port Number

699 N/A Port number to be used with the System Under Test IP address.

Lifetime (Seconds) 65535 1 - 65535 The maximum amount of time a session is maintained without a reregistration request. The value 65535 means that the lifetime will not expire.

Reregistration Time (Seconds)

20 5 - 100 This value specifies the amount of time prior to the expiration of the lifetime timer that a reregistration request is sent.

User Zone 0 N/A Open RP user zone.

Air Link QOS 0 N/A Open RP air link quality of service.

Open RP SPI 1000 N/A Open RP SPI value.

Open RP Secret secret N/A Password for establishing RP tunnel.

Protocol Type Unstructured (0x8881)

N/A Identifies the type of link layer protocol/network layer protocol used by the mobile node. The options are PPP (0x880b) and Unstructured (0x8881).Note: The user must select the protocol type used by the SUT.

Table 3-20 RP Protocol Configuration Parameters (Continued)


Range Description



Dormancy Disabled N/A A pull-down tab to enable dormant session processing. The options are Disabled or Enabled.Note: This should only be set to Enabled, if the SUT supports dormant sessions.

Dormancy Time In Seconds

300 1 - 1,000 Conditional on Dormancy set to Enabled. Time after activation that a session is changed to the dormant state.

Short Data Burst Disabled N/A Conditional on Dormancy set to Enabled. A pull-down tab to enable short data burst messaging capability. The options are Enabled or Disabled.Note: This option should only be set to Enabled if the SUT supports short data burst processing.

Redirection Disabled N/A Allows the PDSN to specify an alternate PDSN within the Unknown PDSN response message. Options are Enabled or Disabled.

Normal Vendor Specific Extension

Disabled N/A Allows the use of the normal vendor specific extensions included in the RP messaging. The options are Enabled or Disabled. Note: If the Normal Vendor Specific Extension is Enabled, it will be included in the RP messaging and the Previous Access Network Identifier and Current Access Network Identifier may be configured by the user.

PANID SID 0x0 0x0 - oxFFFF

Conditional on Normal Vendor Specific Extension set to Enabled. System Identification field for the Previous Access Network Identifier.

PANID NID 0x0 0x0 - oxFFFF

Conditional on Normal Vendor Specific Extension set to Enabled. Network Identification field for the Previous Access Network Identifier.



Range Description



PANID PZID 0x0 0x0 - oxFF

Conditional on Normal Vendor Specific Extension set to Enabled. Packet Zone Identifier field for the Previous Access Network Identifier.

CANID SID 0x0 0x0 - oxFFFF

Conditional on Normal Vendor Specific Extension set to Enabled. System Identification field for the Current Access Network Identifier.

CANID NID 0x0 0x0 - oxFFFF

Conditional on Normal Vendor Specific Extension set to Enabled. Network Identification field for the Current Access Network Identifier.

CANID PZID 0x0 0x0 - oxFF

Conditional on Normal Vendor Specific Extension set to Enabled. Packet Zone Identifier field for the Current Access Network Identifier.

RP Parameters

Retries 3 0 - 10 Number of times to retry in establishing sessions.

Starting MS ID 300000 N/A Starting mobile subscriber ID to be used in establishing sessions. This ID is incremented to provide a unique MS ID for each session.

BS ID bsid12 N/A Base station ID to be used in establishing sessions.

Starting PCF Session ID

1 N/A Starting PCF session ID to be used in establishing RP sessions. This ID is incremented to provide a unique PCF Session ID for each session.

F1 1 N/A Forward Mux Option parameter in the customer/organization specific extension of the Active Start Airlink Record.

F2 1 N/A Reverse Mux Option parameter in the customer/organization specific extension of the Active Start Airlink Record.



Range Description

Test ParametersPPP Parameters


PPP ParametersTable 3-21 describes the PPP Protocol configuration parameters available on the PPP and PPP/L2TP tabs.

F3 240 N/A Forward Rate parameter in the customer/organization specific extension of the Active Start Airlink Record.

F4 240 N/A Reverse Rate parameter in the customer/organization specific extension of the Active Start Airlink Record.

F5 33 N/A Service Option parameter in the customer/organization specific extension of the Active Start Airlink Record.

F6 1 N/A Forward Traffic Type parameter in the customer/organization specific extension of the Active Start Airlink Record.

F7 1 N/A Reverse Traffic Type parameter in the customer/organization specific extension of the Active Start Airlink Record.

F8 2 N/A FCH Frame Size parameter in the customer/organization specific extension of the Active Start Airlink Record.

F9 1 N/A Forward Radio Configuration parameter in the customer/organization specific extension of the Active Start Airlink Record.

F10 1 N/A Reverse Radio Configuration parameter in the customer/organization specific extension of the Active Start Airlink Record.



Range Description

Test ParametersPPP Parameters


Table 3-21 PPP Protocol Configuration Parameters


Range Description

Magic Number 654321 1 - 4294967295

The magic number to use when establishing a PPP session.Note: Hex, decimal, or binary values are valid for this parameter. Decimal is selected by default; click Hex or Bin to change the value type.

Retries 3 0 - 10 Number of retry attempts when establishing a PPP session.

Authorization None N/A Identifies the type of authentication to be used. The options are None, Any, CHAP, or PAP.

User Name @domain N/A Conditional on Authorization set to Any, CHAP, or PAP. The name to be used in establishing PPP sessions. The default value will supply a unique User Name for each session (see “Variable Parameter Values”).

Password pword N/A Conditional on Authorization set to Any, CHAP, or PAP. Password to be used in establishing PPP sessions.

Synchronization Mode

Async N/A Selects either Synchronous or Asynchronous mode for the PPP communication. Options are Async and Sync.Note: This must be set to correspond to the SUT.

ACCM Disabled N/A Conditional on Async selected as Synchronization Mode. Enables ACCM negotiation with the PPP peer. Options are Enabled or Disabled.Note: This must be set to correspond to the SUT.

Test ParametersData Traffic Parameters


Data Traffic ParametersTable 3-22 describes the data test configuration parameters. These parameters are presented on the Data Traffic tab.

Refer to “Interpreting Data Traffic Measurements” in Chapter 4 for more information about data types and payload sizes, and how they relate to measurements.

Forced Equivalent Disabled N/A Conditional on ACCM set to Enabled. When set to Enabled, this option requires that the peer negotiate using the ACCM value that is specified. Options are Enabled or Disabled.

ACCM value (Hex format)

0x0 0x0 - 0xFFFFFFFF

Conditional on ACCM set to Enabled. 32 bit hex value which specifies what values between 0 and 31 to be escaped. If bit 3 of the ACCM value is set, then all bytes of value 3 are escaped within the message.

Error Inject None N/A Conditional on Synchronization Type set to Async. Used to select error injection at the PPP layer. The options are None, Bad HDLC Checksum for all data packets, or Bad HDLC Checksum for all control packets.

Van Jacobson Compression

Disabled N/A A pull-down tab to enable Van Jacobson header compression.

Van Jacobson Slot ID Compression

Disabled N/A Conditional on Van Jacobson Compression set to Enabled. A pull-down tab to enable Van Jacobson slot ID compression.

Table 3-21 PPP Protocol Configuration Parameters (Continued)


Range Description



Table 3-22 Data Traffic Parameters


Range Description

Data Traffic Disabled N/A Enables and selects type of data traffic. Options are Disabled, Verification, and Continuous. When Disabled is selected, none of the parameters below are displayed.

Network Host Local N/A Identifies the type of network host to be used for data testing. The options are Local (uses the test case’s built-in network host emulator) or Remote (uses an emulated network host in a different test case or session).Note: A remote host can also run on another test server to maximize the data traffic received by the mobile node.


N/A N/A Conditional on Remote selected for Network Host. The IP address for a network host emulator.Note: When using a network host emulator in a different test session, the Network Host test case must be running before this test case is started (see “Network Host Test Cases” in Chapter 2).


N/A N/A Conditional on Local selected for Network Host. An area for entering the physical interface and logical IP address information for the emulated network host.

Physical Address N/A N/A A pull-down tab for selecting the physical port for use as the emulated network host node.

IP Address N/A N/A The virtual IP address to be used for the emulated network host, selected from the pool of IP addresses associated with the physical interface.



Default Routing N/A N/A A button for selecting the test server’s default routing as the route to be used by the emulated network host node. Refer to the Landslide 2500 Installation Guide for instructions on configuring the routing protocols and static routes used by a test server.


N/A N/A A button for selecting a specific route for the emulated network host node to use. This allows the user to force traffic over a specific ethernet port. If this button is selected, the adjacent field is used to enter the IP address of the next hop.

Conditional Parameters based on Continuous selected as Data Traffic type

Traffic Start When All Sessions Estab-lished (Capacity Test Only)

N/A Indicates when the CPTS should begin sending bearer traffic. Options are When All Sessions Established (Capacity Test Only) or When Session Established.Note: When All Sessions Established cannot be used with Session Loading or Rate tests.

Data Start Delay (Milliseconds) (1 - 60000)

1000 1 - 60,000 Start delay for sending bearer traffic, either after a session is established, or after all sessions are established.

Payload Data Size N/A N/A Any two of the following three parameters must be set. The third parameter should be cleared and generated by clicking the Calculate button. Normally Packets/Second and Packet Size are specified, and Data Rate is calculated.

Table 3-22 Data Traffic Parameters (Continued)


Range Description



Packets/Second 1 N/A Number of packets to be sent each second by each emulated MN. The maximum recommended rate is 100 packets/second (pps). To achieve 1000 pps in the test session, provision 10 MN sessions on the General tab. Each MN session will simultaneously send data at 100 pps.Note: When large packet sizes are used, the actual data packet rate will vary as fragmentation occurs.

Important: Each test server is limited to a maximum rate of 40,000 pps. Traffic to and from the MN and network host emulators are included in this limit. When using a local network host emulator in a test case, for example, this rate cannot exceed 10,000 pps:• 10,000 pps sent from the MN• 10,000 pps received by the network

host• 10,000 pps sent from the network host• 10,000 pps received by the MN

Therefore, when using a local network host, the maximum number of sessions that can be provisioned at the recommended rate of 100 pps is 100 (100 sessions x 100 pps = 10,000 pps).

This rate can be doubled by selecting a Remote emulated network host which runs on another test server (see “Network Host Test Cases” in Chapter 2).



Range Description



Packet Size (bytes) 64 8-65535 Size of the data payload in the packets to be sent.

When using FTP, the packet size is the size of the simulated file that is downloaded from the network host. With HTTP, the packet size is the simulated web page content. These will be reported in the Payload Bytes Received measurement. In all other protocols, the data payload is sent from the MN to the network host.

To protect packet header integrity and the round trip delay counter, the following guidelines should be followed for the minimum packet size:• RAW - minimum 28 bytes• ICMP - minimum 8 bytes• UDP - minimum 28 bytes• TCP - minimum 16 bytesNote: Fragmentation will occur at the base IP layer if the packet size is greater than 1364 bytes.

Data Rate (bits/second)

512 N/A Number of bits to be sent per second. This value is normally calculated based on Packets/Second and Packet Size, not specified.

Packet Interval Distribution

Fixed N/A Determines the distribution model to be used for shaping the bearer traffic rate. Options are Fixed, Uniform, Normal, and Poisson. Refer to “Glossary” in “About this Guide” for model definitions and examples.

Important: Selecting any model other than Fixed will reduce the data throughput by as much as half due to the extra processing required to randomize the packet rate.



Range Description




10 1-99 Conditional on Uniform or Poisson selected as Packet Interval Distribution. Limits the standard deviation in the selected distribution model.


10 0-100 Conditional on Normal selected as Packet Interval Distribution. Sets the standard deviation to be used for selected Data Rate.

Packet Size Distribution

Fixed N/A Determines the distribution model to be used for bearer traffic packets. Options are Fixed, Uniform, Normal, and Poisson. Refer to “Glossary” in “About this Guide” for model definitions and examples.Note: The integrity of the data packet headers is protected when using a distribution model. The packet size will not be reduced by an amount that would truncate the packet headers.


10 1-99 Conditional on Uniform or Poisson selected as Packet Size Distribution model. Limits the standard deviation in the selected distribution model.


10 0-100 Conditional on Normal selected as Packet Size Distribution model. Sets the standard deviation to be used for selected Packet Size.



Range Description




0 0 - 255 Specifies the quality of service to request. This parameter is the decimal value of an 8 bit QOS indicator defined as follows:• Bits 0-2: Precedence

111 = Network Control110 = Internetwork Control101 = CRITIC/ECP100 = Flash Override011 = Flash010 = Immediate000 = Routine

• Bit 3: Delay (0 = normal, 1 = low)• Bit 4: Throughput (0 = normal, 1 =

high)• Bit 5: Reliability (0 = normal, 1 = high)• Bits 6-7: Reserved for future use

A value of 0 indicates normal QOS.


64 1 - 255 Specifies the length of time in seconds that a datagram may stay in the internet. This value is decremented by each module that processes the datagram. When the value reaches zero, the datagram is discarded.

Protocol PING (ICMP)

N/A Selects the type of data to be sent. The options are PING (ICMP), HTTP, FTP, WAP, SMTP, RAW, UDP, and TCP.

Conditional Parameters Based on HTTP selected as Protocol

URL #1 N/A N/A 1st URL address to be included in HTTP GET request. This URL is mandatory.Note: If more than one URL is entered, the test cycles through the URLs. For example, if 3 URLs are provided in a test with 5 sessions, session 1 will use URL #1, session 2 will use URL #2, session 3 will use URL #3, session 4 will use URL #1, and session 5 will use URL #2.

URL #2 N/A N/A 2nd URL address to be included in HTTP GET request.



Range Description



URL #3 N/A N/A 3rd URL address to be included in HTTP GET request.

URL #4 N/A N/A 4th URL address to be included in HTTP GET request.





Source Port 2000 N/A Port for the test server IP address to be used to send the HTTP traffic.

Destination Port 80 N/A Port on the Network Host IP address to be used as the destination port.

HTTP Version 1.1 N/A A pull-down tab to select the desired HTTP version of data to use. The options are 1.1 and 1.0.

HTTP Request Header

User-Agent: xPTS/1.1\r\nKeep-Alive: 300\r\nConnection: keep-alive\r\n

N/A The header to be used in the HTTP Request message.Note: The default request header specifies HTTP version 1.1. If 1.0 is selected in HTTP Version, the system will modify the message header accordingly. The header that is displayed here will not be changed



Range Description



HTTP Response Header

HTTP/1.1 200 OK\r\nDate: Mon, 03 May 2004 23:59:59 GMT\r\nServer: xPTS/1.2 (Red.Hat.Linux)\r\nConnection: Keep-Alive\r\n

N/A The header to be used in the HTTP Response message.Note: The default response header specifies HTTP version 1.1. If 1.0 is selected in HTTP Version, the system will modify the message header accordingly. The header that is displayed here will not be changed.

Error Inject None N/A A pull-down tab for selecting a type of error injection in the data traffic. The options are None, IP Total Length Set to 0, IP Checksum Corrupted, Payload Checksum Corrupted, Prevent Fragmentation, Bad Source IP.Note: If error injection is selected it will apply to all data transmissions within the selected test case.

Conditional Parameters based on FTP selected as Protocol

Source Port 2000 N/A Port for the test server IP address to be used to send the FTP traffic.

Destination Port 21 N/A Port on the Network Host IP address to be used as the destination port for FTP traffic.




Range Description



Conditional Parameters based on WAP selected as Protocol.

URL #1 N/A N/A 1st URL address to be included in WAP GET request. This URL is mandatory.Note: If more than one URL is entered, the test cycles through the URLs. For example, if 3 URLs are provided in a test with 5 sessions, session 1 will use URL #1, session 2 will use URL #2, session 3 will use URL #3, session 4 will use URL #1, and session 5 will use URL #2.

URL #2 N/A N/A 2nd URL address to be included in WAP GET request.

URL #3 N/A N/A 3rd URL address to be included in WAP GET request.

URL #4 N/A N/A 4th URL address to be included in WAP GET request.





Source Port 2000 N/A Port for the test server IP address to be used to send the WAP traffic.

Destination Port 9200 N/A Port on the Network Host IP address to be used as the destination port for WAP traffic.

Underlying Protocol

TCP N/A A pull-down tab for selecting the transport protocol to be used under the WAP layer. The options are TCP and UDP.



Range Description




Conditional Parameters based on SMTP selected as Protocol

Source Port 2000 N/A Port for the test server IP address to be used to send the SMTP traffic.

Destination Port 25 N/A Port on the Network Host IP address to be used as the destination port for SMTP traffic.


Conditional Parameters based on RAW selected as Protocol



Range Description



Host Initiated Transfer

Disabled N/A Determines if the emulated network host initiates the traffic, or if the mobile node emulator initiates the traffic. The options are Disabled (mobile node initiates traffic) or Enabled (network host initiates traffic).Note: Setting Host Initiated Transfer to Enabled will result in unidirectional traffic from the network host to the mobile node, with the exception of the packets send by the MN to announce the connection and to terminate the connection.

Important: Host Initiated Transfer cannot be used in session loading tests when dynamic MN addressing is used.

Host Data Expansion (0 - 100)

1 0 - 100 Conditional on Host Initiated Transfer set to Disabled. Specifies whether the host should return the same data as sent or expand the data. The value entered is a multiplier, with a value of 2 indicating double the received traffic, etc.Note: A value of 0 in the Host Data Expansion (0 - 100) field will result in the Network Host returning no traffic, creating unidirectional data from the mobile node to the network host.

Important: Host Data Expansion cannot be used in session loading tests when dynamic MN addressing is used.


Conditional Parameters based on PING (ICMP) selected as Protocol



Range Description










Conditional Parameters based on UDP selected as Protocol



Range Description









Source Port 2000 N/A Port for the test server IP address to be used to send the UDP traffic.

Destination Port 2001 N/A Port on the Network Host IP address to be used as the destination port for UDP traffic.



Range Description




Conditional Parameters based on TCP selected as Protocol


Disabled N/A Determines if the emulated network host initiates the traffic, or if the MS emulator initiates the traffic. The options are Disabled (MS initiates traffic) or Enabled (network host initiates traffic).Note: Setting Host Initiated Transfer to Enabled will result in unidirectional traffic from the network host to the MS, with the exception of the packets send by the MS to announce the connection and to terminate the connection.

Important: Host Initiated Transfer cannot be used in session loading tests when dynamic MS addressing is used.

Host data expansion

1 0 - 100 Conditional on Host Initiated Transfer set to Disabled. Specifies whether the host should return the same data as sent or expand the data. The value entered is a multiplier, with a value of 2 indicating double the received traffic, etc.Note: A value of 0 in the Host Data Expansion (0 - 100) field will result in the Network Host returning no traffic, creating unidirectional data from the MS to the network host.

Important: Host Data Expansion cannot be used in session loading tests when dynamic MS addressing is used.



Range Description



Source Port 2000 N/A Port for the test server IP address to be used to send the TCP traffic.

Destination Port 2001 N/A Port on the Network Host IP address to be used as the destination port for TCP traffic.


Conditional Parameters based on Verification selected as Data Traffic type.

Data Start Delay (Milliseconds) (1 - 60000)

1000 1 - 60,000 Start delay for sending bearer traffic, either after a session is established.



Range Description

Test ParametersMIP Parameters


MIP ParametersTable 3-23 describes the MIP Protocol configuration parameters.


0 0 - 255 Specifies the quality of service to request. This parameter is the decimal value of an 8 bit QOS indicator defined as follows:• Bits 0-2: Precedence

111 = Network Control110 = Internetwork Control101 = CRITIC/ECP100 = Flash Override011 = Flash010 = Immediate000 = Routine

• Bit 3: Delay (0 = normal, 1 = low)• Bit 4: Throughput (0 = normal, 1 =

high)• Bit 5: Reliability (0 = normal, 1 = high)• Bits 6-7: Reserved for future use

A value of 0 indicates normal QOS.


64 1 - 255 Specifies the length of time in seconds that a datagram may stay in the internet. This value is decremented by each module that processes the datagram. When the value reaches zero, the datagram is discarded.



Range Description



Table 3-23 MIP Parameters


Range Description

Use Reverse Tunnel

Enabled N/A Selects reverse tunnel test configuration. Options are Enabled or Disabled.Note: This must be set to Enabled for MIP VPN configuration.

MIP HA Secret secret N/A The secret code to be used in the MIP HA authentication extension in the RRQ message.Note: This must be set to correspond to the SUT.

Request Simultaneous Bindings

0 N/A Number of simultaneous bindings to be requested in the MIP RRQ message.

Request Broadcast Datagrams

0 N/A Number of broadcast datagrams to be requested in the MIP RRQ message.

Encapsulation Mode

None N/A Identifies the MIP encapsulation mode.Note: This is not supported at this time.

Use HMAC Authentication

Disabled N/A Enables or disables the use of HMAC encryption in the MN-AAA authentication extension in the MIP RRQ message. The options are Enabled or Disabled.Note: Enabled selects HMAC encryption for AAA server authentication. Disabled defaults to the more common Radius AAA authentication.

HA Lifetime (Seconds)

65535 1 - 65535 Lifetime value to be used for the Home Agent. This is the maximum amount of time a session is maintained without a reregistration request. The value 65535 means that the lifetime will not expire.Note: This must be set to correspond to the SUT.

Retries 3 N/A Number of retries to be used following an unsuccessful effort to establish a MIP session to the PDSN-FA.




20 0 - 100 The amount of time prior to the expiration of the lifetime timer expires that a reregistration request is sent. A value of 0 disables reregistration.

FA HA SPI 1000 N/A SPI value to be used in the FA HA authentication extension in the MIP RRQ message.Note: This must be set to correspond to the SUT.

FA HA Secret secret N/A Secret code to be used in the FA HA authentication extension in the MIP RRQ message.Note: This must be set to correspond to the SUT.

Home Address 0.0.0.0 N/A Mobile Node’s Home IP Address. A value of 0.0.0.0 allows the HA to assign an available IP address to the MN(s), and an IP address allows the MN to inform the HA of its address.

If an IP address is entered, it must be valid for the HA’s Home Address Pool for a session to be established. It will be used as the address for the first MN and will be incremented for each subsequent MN.Note: The number of available IP addresses must be equal to or greater than the total number of sessions specified on the General tab in order to establish the number of sessions specified in the General tab.

MN Home Agent SPI

1000 N/A SPI to be used in the MN HA authentication extension to the MIP RRQ message.Note: This must be set to correspond to the SUT.

Table 3-23 MIP Parameters (Continued)


Range Description



MN AAA SPI 1000 N/A SPI value to be used in the MN AAA authentication extension in the MIP RRQ message.Note: This must be set to correspond to the SUT.

MN AAA Secret secret N/A Secret code to be used in the MN AAA authentication extension in the MIP RRQ message.Note: This must be set to correspond to the SUT.

Co-located Care of Address

0.0.0.0 N/A IP address to be used as Care Of Address in the MIP RRQ message. Typically this value is set to 0.0.0.0 and the Care Of Address value is obtained when the MN receives the agent advertisement message.

HA Retries 3 N/A Number of retries to be used following an unsuccessful effort to establish a MIP session to the HA.Note: This value is not applicable to End-To-End tests.



Range Description

Test ParametersMIP Parameters for HA Nodal


MIP Parameters for HA NodalTable 3-24 describes the MIP Protocol configuration parameters for HA Nodal Testing.

HA Connection Type

FA Supplied Care Of Address

Type of connection requested at HA. Used for building the registration request header. Options are Co-Located Care of Address, FA Supplied Care of Address, or Home Address.

Co-Located Care of Address:

The address entered in Co-Located Care of Address is used to populate the Care of Address field in the RRQ message and the source IP field in the IP header.

FA Supplied Care of Address:

The Foreign Agent IP address received in the agent advertisement is used to populate the Care of Address field in the RRQ message. The Home Address is used to populate the source IP field in the IP header.

Home Address:

The address entered in Co-Located Care of Address is used to populate the Care of Address field in the RRQ message. The Home Address is used to populate the source IP field in the IP header.

NAI @domain NAI value to be used. The default value will supply a unique NAI for each session (see “Variable Parameter Values”).Note: This must be set to correspond to the SUT.



Range Description



Table 3-24 MIP Parameters for HA Nodal Testing


Range Description

Use Reverse Tunnel

Enabled N/A Selects reverse tunnel test configuration. Options are enabled or disabled.Note: This must be set to Enabled for MIP VPN configuration.

Request Simultaneous Bindings

0 N/A Number of simultaneous bindings to be requested in the MIP RRQ message.

Request Broadcast Datagrams

0 N/A Number of broadcast datagrams to be requested in the MIP RRQ message.

Encapsulation Mode

None N/A Identifies the MIP encapsulation mode.Note: This capability is not supported at this time.

Use HMAC Authentication

Disabled N/A Enables or disables the use of HMAC encryption in the MN-AAA authentication extension in the MIP RRQ message. The options are Enabled or Disabled.Note: Enabled selects HMAC encryption for AAA server authentication. Disabled defaults to the more common Radius AAA authentication.

HA Lifetime (Seconds)

65535 1 - 65535 Lifetime value to be used for the Home Agent. This is the maximum amount of time a session is maintained without a reregistration request. The value 65535 means that the lifetime will not expire.Note: This must be set to correspond to the SUT.



Home Address 0.0.0.0 N/A Mobile Node’s Home IP Address. A value of 0.0.0.0 allows the HA to assign an available IP address to the MN(s), and an IP address allows the MN to inform the HA of its address.

If an IP address is entered, it will be used as the address for the first MN and will be incremented for each subsequent MN.Note: The number of available IP addresses must be equal to or greater than the total number of sessions specified on the General tab.

MN-FA Challenge Size

0 N/A Number of digits in the MN-FA Challenge extension to be used in the MIP RRQ message. A value of 0 disables the extension.

MN-FA Challenge 0 N/A The value that will be included in the challenge extension if MN-FA Challenge Size is greater than 0.

FA SPI 0 N/A SPI value to be used in the FA authentication extension in the MIP RRQ message.

FA Secret secret N/A Secret code to be used in the FA HA authentication extension to the MIP RRQ message.

MN-HA SPI 1000 N/A SPI value to be used in the MN HA authentication extension in the RRQ message.Note: This must be set to correspond to the SUT.

MN-HA Secret secret N/A Secret code to be used in the MN HA authentication extension in the RRQ message.Note: This must be set to correspond to the SUT.

Table 3-24 MIP Parameters for HA Nodal Testing (Continued)


Range Description



FA HA SPI 0 N/A SPI value to be used in the FA HA authentication extension in the MIP RRQ message.Note: This must be set to correspond to the SUT.

FA HA Secret secret N/A Secret code to be used in the FA HA authentication extension in the MIP RRQ message.Note: This must be set to correspond to the SUT.

MN AAA SPI 1000 N/A SPI value to be used in the MN AAA authentication extension in the MIP RRQ message.Note: This must be set to correspond to the SUT.

MN AAA Secret secret N/A Secret code to be used in the MN AAA authentication extension in the MIP RRQ message.Note: This must be set to correspond to the SUT.

Co-located Care of Address

0.0.0.0 N/A IP address to be used as Care Of Address in the MIP RRQ message. Typically this value is set to 0.0.0.0 and the Care Of Address value is obtained when the MN receives the agent advertisement message.

HA Retries 3 N/A Number of retries to be used following an unsuccessful effort to establish a MIP session to the HA.


20 0 - 100 This value specifies the amount of time prior to the expiration of the lifetime timer expires that a reregistration request is sent. A value of 0 disables reregistration.



Range Description



HA Connection Type

FA Supplied Care Of Address

N/A Type of connection requested at HA. Used for building the registration request header. Options are Co-Located Care of Address, FA Supplied Care of Address, or Home Address.

Co-Located Care of Address:

The address entered in Co-Located Care of Address is used to populate the Care of Address field in the RRQ message and the source IP field in the IP header.

FA Supplied Care of Address:

The Foreign Agent IP address received in the agent advertisement is used to populate the Care of Address field in the RRQ message. The Home Address is used to populate the source IP field in the IP header.

Home Address:

The address entered in Co-Located Care of Address is used to populate the Care of Address field in the RRQ message. The Home Address is used to populate the source IP field in the IP header.

NAI @domain N/A NAI value to be used. The default value will supply a unique NAI for each session (see “Variable Parameter Values”).Note: This must be set to correspond to the SUT.



Range Description


Chapter 4

Test Case Measurements

This chapter provides detailed information on the test case measurements.

In this chapter...


Purpose....174

Rate Calculations....174

Test Summary Measurements....174

Test Summary Measurements for CPU Query....177

Test Summary Measurements for Mobility Testing....177

Test Summary Measurements for MIP Revocation....178

Test Summary Measurements for L2TP VPN....178

RP Measurements....179

PPP Measurements....182

Mobile IP Measurements....185

MIP Node Emulator Measurements....192

FA Emulation Measurements....193

HA Emulation Measurements....196

PCF Emulation Measurements....197

Network Host Emulator Measurements....198

Data Traffic Measurements....199

L2TP Measurements....204

L2TP Node Measurements....207

Rate Test Measurements....208

Test Case MeasurementsPurpose


PurposeThe CPTS provides a variety of measurements that are available based on test configuration and test activity. The following tables provide a description of each of the measurements collected by the CPTS.

The aggregate measurements for all test cases in the test session are displayed on each report tab by default. If a test session includes more than one test case, the measurements for one test case can be displayed by using the Current Report pull-down tab at the top of the Reports tab to select a test case, and then clicking Change. If more than one test case uses the same protocol, the aggregate measurements on that protocol’s tab will include all instances of the protocol in the test session when Current Report is set to Summary.

The type of measurements displayed can also be changed. By default, all reports display measurements that are cumulative through the life of the test. Measurements collected over each interval can be displayed by right-clicking a measurement and choosing to display interval values in either that measurement or all measurements (refer to the User Guide for examples).

Interval measurements are calculated by subtracting the previous interval’s cumulative measurements from the latest interval’s cumulative measurements. Because of this, some measurements may display a negative value when set to interval reporting: Sessions Established will show a negative number as sessions are disconnected, for example. Measurements that report averages should not be set to interval reporting.

Rate CalculationsWhen interpreting measurements that deal with “per second” rates, it is important to note that the calculation is based on the actual processing time (in milliseconds) rather than the Elapsed Time displayed on the report tab. For example: 169,470 packets were processed during a 15 second interval, which would seem to result in a 11,298 packets/second rate (169,470 / 15), but the value displayed in the packets/second measurement is 12,035.34 because the actual processing time was 14,081 milliseconds, not 15 seconds (169,470 / 14.081).

Test Summary MeasurementsThe measurements described in Table 4-1 are collected by the CPTS and reported on the Test Summary tab for all test cases regardless of the configuration or the test activity. Additional measurements can appear on this tab when the SUT Query option is enabled (Table 4-2), when running a mobility test activity (Table 4-3), when running a MIP Revocation (Table 4-4) test activity, or when using L2TP VPN connections in a SIP VPN test case (Table 4-5).

Test Case MeasurementsTest Summary Measurements


Table 4-1 Test Summary Measurements

Counter Description

Elapsed Time The amount of time the test has been running.

Start Time Start time for the current test.

Test Duration The defined duration of the current test.

Est. Time Remaining Estimated time until completion of the current test. This value will be 0 unless the test duration is set prior to starting the test.

Attempted Connect Rate (Sessions/Second)

Current rate at which the CPTS is attempting to activate sessions as specified in the test definition. Refer to “Rate Calculations” for an explanation of how rates are calculated.Note: When conducting a test measuring rates, where the test automatically adjusts the rate for activation, this rate will vary. For other tests, it remains constant based on user input.

Attempted Disconnect Rate (Sessions/Second)

Current rate at which the CPTS is attempting to deactivate sessions as specified in the test definition. Refer to “Rate Calculations” for an explanation of how rates are calculated.Note: When conducting a test measuring rates, where the test automatically adjusts the rate for deactivation, this rate will vary. For other tests, it remains constant based on user input.

Actual Connect Rate (Sessions/Second)

The actual rate of successful activations as measured over the last reporting period. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Actual Disconnect Rate (Sessions/Second)

The actual rate of successful deactivations as measured over the last reporting period. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Sessions Established The number of sessions currently established.

Test Case MeasurementsTest Summary Measurements


Sessions Pending The total number of currently idle sessions, waiting to be activated.Note: The sum of Sessions Established and Sessions Pending will not necessarily equal the number of MN sessions specified in the test definition at any given time while sessions are being established. Some sessions will be in a transitory state at the time the measurements are collected.

Session Errors The total number of session errors generated across all layers during the test. A session error is defined as a transition into the idle state after an abnormal event.

Session errors are summarized as follows:• In End-to-End Mobile IP and FA Nodal tests, Session

Errors reports the sum of all errors at the RP, PPP, MIP, and Traffic layers.

• In HA Nodal tests it reports errors at the MIP and Traffic layers.

• In SIP tests it reports errors at the RP, PPP, and Traffic layers.

• In SIP VPN tests it reports errors at the RP, L2TP, PPP, and Traffic layers.

• When continuous data traffic is enabled and TCP is used, a failure to establish the data session is counted as a ses-sion error. Data verification failures are also counted as session errors.

Attempted Session Connects

The total number of session connects were attempted over the life of the test as specified in the test definition.

Attempted Session Disconnects

The total number of session disconnects that were attempted over the life of the test as specified in the test definition.

Actual Session Connects

The total number of Attempted Session Connects that were successful.

Actual Session Disconnects

The total number of Attempted Session Disconnects that were successful.

Average Session Connect Time

The average time elapsed from the time an activation request is sent to the PDSN, until the session is successfully established. This value is averaged for all successful activations across all layers.

Table 4-1 Test Summary Measurements (Continued)

Counter Description

Test Case MeasurementsTest Summary Measurements for CPU Query


Test Summary Measurements for CPU QueryThe measurements described in Table 4-2 are collected by the CPTS and reported on the Test Summary tab, in addition to the other test measurements, when CPU Query is enabled.

Test Summary Measurements for Mobility TestingThe measurements described in Table 4-3 are collected by the CPTS and reported on the Test Summary tab, in addition to the other test measurements, when a mobility test activity is selected. These measurements are reported for the following test activities:

• Session Loading With Mobility

• Intra-PDSN

• Intra-PDSN Rate

• Inter-PDSN

• Inter-PDSN Rate.

Average Session Disconnect Time

The average time elapsed from the time a deactivation is initiated, until the session is deactivated. This value is averaged for all successful deactivations across all layers.

Table 4-1 Test Summary Measurements (Continued)

Counter Description

Table 4-2 Test Summary Measurements for CPU Query

Counter Description

SUT CPU Utilization (Percent)

The reported percentage of CPU real-time usage for the SUT, based on the last CPU Query.

Table 4-3 Test Summary Measurements for Mobility Testing

Counter Description

Actual Handoff Rate (Handoffs/Second)

The actual rate of successful handoffs as measured over the last reporting period. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Test Case MeasurementsTest Summary Measurements for MIP Revocation


Test Summary Measurements for MIP RevocationThe measurements described in Table 4-4 are collected by the CPTS and reported on the Test Summary tab, in addition to the other test measurements, when MIP Revocation test activity is selected.

Test Summary Measurements for L2TP VPNThe measurements described in Table 4-5 are collected by the CPTS and reported on the Test Summary tab, in addition to the other test measurements, when L2TP VPN Connection is enabled for a Simple IP VPN test case.

Handoff Attempts The total number of times an RP handoff is attempted. Although this value is the sum of Handoff Successes and Handoff Failures, the equation may not hold true at any given time during handoff processing since some sessions may be in a transitory state when the measurements are collected.

Handoff Successes The total number of times RP handoff attempts that succeeded.

Handoff Failures The total number of times RP handoff attempts that failed.

Table 4-3 Test Summary Measurements (Continued) for Mobility Testing (Continued)

Counter Description

Table 4-4 Test Summary Measurements For MIP Revocation

Counter Description

Actual Revocation Rate (Revocations/Second)

The actual rate of successful revocations as measured over the last reporting period. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Revocation Attempts The total number of times a revocation is attempted. Although this value is the sum of Revocation Successes and Revocation Failures, the equation may not hold true at any given time during revocation processing since some sessions may be in a trisector state when the measurements are collected.

Revocation Successes The total number of revocation attempts that succeeded.

Revocation Failures The total number of revocation attempts that failed.

Test Case MeasurementsRP Measurements


RP MeasurementsThe measurements described in Table 4-6 are collected by the CPTS, and reported on the RP tab, when testing in a SIP, Simple IP VPN, FA Nodal, or End-to-End test configuration.

Table 4-5 Test Summary Measurements For L2TP VPN

Counter Description

Tunnels Established The total number of tunnels established.

Tunnels Pending The total number of tunnels waiting to be established or idle.

L2TP Tunnels Established

The total number of L2TP tunnels established.

L2TP Tunnels Pending The total number of L2TP tunnels waiting to be established or idle.

Table 4-6 RP Measurements

Counter Description


Attempts The number of initial Open RP sessions attempted. Although this value is the sum of Successes and Failures, the equation may not hold true at any given time during session processing since some sessions may be in a trisector state when the measurements are collected.

Successes The number of Open RP sessions successfully established.

Failures The number of Open RP sessions that failed due to one of the failure codes listed below.

Reregistrations The total number of reregistration requests sent.



PDSN Terminations The total number of PDSN terminations that have occurred. A PDSN termination is defined as an update message sent from the PDSN to the PCF. To complete the PDSN termination, the PCF will send a RACK message to acknowledge the update message, followed by a registration request message with a lifetime of 0. When the PCF receives the registration reply from the PDSN, the PDSN termination is complete.

PCF Terminations The number of PCF terminations that have occurred. A PCF termination is defined as an RP registration message sent by the PCF side with a lifetime of zero. When the PCF receives a registration reply message from the PDSN, the PCF termination is complete.

Failure Unspecified(128)

The number of registration reply messages received with an error code value of 128. This counter is incremented when a registration request is rejected by the PDSN without a valid cause code.

Failure Admin Prohibited(129)

The total number of registration requests denied by the PDSN due to admin prohibited (129).

Redirections The total number of registration reply messages received with an error code value of 136, and which also provided an alternate PDSN IP address. The PCF will attempt to register with the PDSN IP address provided in the registration reply message as a result.

Failure Insufficient Resources(130)

The total number of registration reply messages received with an error code value of 130. This error code indicates that the PDSN is rejecting the RP registration request because of a shortage of resources such as memory.

Failure Authentication(131)

The total number of registration reply messages received with an error code value of 131. This error code indicates that the PDSN is rejecting the RP registration request because the MN failed authentication.

Failure ID Mismatch(133)

The total number of registration reply messages received with an error code value of 133. This error code indicates that the PDSN is rejecting the RP registration request because replay protection failed.

Table 4-6 RP Measurements (Continued)

Counter Description



Failure Poorly Formed Request(134)

The total number of registration reply messages received with an error code value of 134. This error code indicates that the PDSN is rejecting the RP registration request because of a problem with the message such as a missing mandatory extension.

Failure Unknown PDSN Address(136)

The total number of registration reply messages received with an error code value of 136. This error code indicates that the PDSN is rejecting the RP registration request because the PDSN IP address in the header of the message is not known to be a valid PDSN address.

Failure PCF Tunnel Not Recognized(137)

The total number of registration reply messages received with an error code value of 137. This error code indicates that the PDSN is rejecting the RP registration request because the PCF is not recognized.

Failure T Bit Not Set(138)

The total number of registration reply messages received with an error code value of 138. This error code indicates that the PDSN is rejecting the RP registration request because reverse tunneling is mandatory and the T bit in the RP registration request is not set.

Failure Unsupported Vendor ID(141)

The total number of registration reply messages received with an error code value of 141. This error code indicates that the PDSN is rejecting the RP registration request because the vendor ID in the CVSE/NVSE extension is not a supported vendor ID.

Registration Reply Timeout

The total number of registration requests sent to the PDSN with no response.

Registration Reply Retries Exceeded

The total number of registration attempts that resulted in the number of retry attempts being exceeded.

Lifetime Expired The total number of Open RP termination requests (registration request with a lifetime of zero) sent from the emulated PCF.

Active to Dormant Count

The total number of sessions that have changed status from active to dormant. RP sessions enter the dormancy state by sending a registration request to the PDSN with an air link record type of stop.


Counter Description

Test Case MeasurementsPPP Measurements


PPP MeasurementsThe measurements described in Table 4-7 are collected by the CPTS, and reported on the PPP tab, when testing in a SIP, Simple IP VPN, FA Nodal, or End-to-End test configuration.

Dormant to Active Count

The total number of sessions that have changed status from dormant to active. RP sessions exit the dormancy state by sending a registration request to the PDSN with an air link record type of start.

Disconnect Count The total number of sessions that have been disconnected.

Average Connect Time Average time in microseconds that it takes to establish an RP session.

Average Disconnect Time

Average time in microseconds that it takes to tear down an RP session.

Short Data Burst Originating Packet Count

The total number of originating short data burst registration requests packets sent.

Short Data Burst Originating Byte Count

The total number of originating short data burst registration requests bytes sent.

Short Data Burst Terminating Packet Count

The total number of terminating short data burst registration requests packets sent.

Short Data Burst Terminating Byte Count

The total number of terminating short data burst registration requests bytes sent.

Short Data Burst Failure Count

The total number of short data burst registration reply messages received with an unsuccessful error code.

Short Data Burst Response Count

The total number of short data burst registration reply messages received with a successful code.


Counter Description



Table 4-7 PPP Measurements

Counter Description


Attempts The total number of attempts to establish a new PPP session. Although this value is the sum of Successes and Failures, the equation may not hold true at any given time during session processing since some sessions may be in a trisector state when the measurements are collected.

Successes The total number of successful attempts to establish a PPP session.

Failures The sum of the following PPP errors: PAP Retries Exceeded, PAP Authorization Failures, CHAP Timeouts, CHAP Authorization Failures, LCP Termination ACKs Received, LCP Retries Exceeded, LCP NAKs Received, LCP Rejects Received, LCP Terminations Received, IPCP Retries Exceeded, IPCP Rejects Received, and IPCP Terminations Received.

IP Allocations This field indicates the number of IP addresses allocated by the PPP layer.Note: This measurement is only applicable to SIP tests, as with SIP the PPP layer is responsible for providing the MN with its home address.


Average Connect Time Average time in microseconds that it takes to establish a PPP session.


Average time in microseconds that it takes to tear down a PPP session.

PAP Authorization Attempts

The total number of PAP authorization attempts.

PAP Authorization Successes

The total number of PAP authorization successes.

PAP Authorization Failures

The total number of PAP authorization failures

PAP Timeouts The total number of timeouts waiting for a PAP authentication.



PAP Retries Exceeded The total number of PAP authentication attempts that resulted in the number of PPP retry attempts being exceeded.

CHAP Authorization Attempts

The total number of CHAP authorization attempts.

CHAP Authorization Successes

The total number of CHAP authorization attempts that succeed.

CHAP Authorization Failures

The total number of CHAP authorization attempts that fail.

CHAP Timeouts The total number of timeouts waiting for a CHAP authentication.

LCP Requests Sent The total number of LCP configuration requests sent.

LCP Requests Received The total number of LCP configuration requests received.

LCP Rejects Sent The total number of LCP configuration rejects sent.

LCP Rejects Received The total number of LCP configuration rejects received.

LCP NAKs Sent The total number of LCP configuration NAKs sent.

LCP NAKs Received The total number of LCP configuration NAKs received.

LCP ACKs Sent The total number of LCP configuration ACKs sent.

LCP ACKs Received The total number of LCP configuration ACKs received.

LCP Termination ACKs Sent

The total number of LCP termination ACKs sent.

LCP Termination ACKs Received

The total number of LCP termination ACKs received.

LCP Terminations Sent The total number of LCP terminations sent.

LCP Terminations Received

The total number of LCP terminations received.

LCP Restarts The total number of LCP restarts.

LCP Timeouts The total number of LCP timeouts.

Table 4-7 PPP Measurements (Continued)

Counter Description

Test Case MeasurementsMobile IP Measurements


Mobile IP MeasurementsThe measurements described in Table 4-8 are collected by the CPTS, and reported on the Mobile IP tab, during FA Nodal, HA Nodal, and End-to-End testing.

LCP Retries Exceeded The total number of LCP retries that resulted in the number of PPP retries being exceeded.

IPCP Requests Sent The total number of IPCP configuration requests sent.

IPCP Requests Received

The total number of IPCP configuration requests received.

IPCP Rejects Sent The total number of IPCP configuration rejects sent.

IPCP Rejects Received The total number of IPCP configuration rejects received.

IPCP NAKs Sent The total number of IPCP configuration NAKs sent.

IPCP NAKs Received The total number of IPCP configuration NAKs received.

IPCP ACKs Sent The total number of IPCP configuration ACKs sent.

IPCP ACKs Received The total number of IPCP configuration ACKs received.

IPCP Timeouts The total number of IPCP timeouts.

IPCP Retries Exceeded The total number of IPCP retries that resulted in the number of PPP retries being exceeded.

IPCP Terminations ACKs Received

The total number of IPCP termination ACKs received.

IPCP Terminations Received

The total number of IPCP terminations received.

Table 4-7 PPP Measurements (Continued)

Counter Description

Table 4-8 Mobile IP Measurements

Counter Description


Agent Advertisements Received

The total number of agent advertisements received from the PDSN-FA.



Agent Solicitations Sent

The total number of agent solicitations sent to the PDSN-FA.

RRQ Messages Sent The total number of registration requests sent to the PDSN-FA.

RRP Messages Received

The total number of registration replies received from the PDSN-FA.

FA Reason Unspecifed(64)

The total number of registration reply messages received with an error code value of 64. This error code indicates that the PDSN-FA is rejecting the MIP registration request for unknown reasons.

FA Admin Prohibited(65)

The total number of registration reply messages received with an error code value of 65. This error code indicates that provisioning on the PDSN-FA is rejecting the MIP registration request.

FA Insufficient Resources(66)

The total number of registration reply messages received with an error code value of 66. This error code indicates that the PDSN-FA is rejecting the MIP registration request because of a shortage of resources such as memory.

FAMN Authorization Failures(67)

The total number of registration reply messages received with an error code value of 67. This error code indicates that the PDSN-FA is rejecting the MIP registration request because the MN failed authentication with the PDSN-FA.

FAHA Authorization Failures(68)

The total number of registration reply messages received with an error code value of 68. This error code indicates that the PDSN-FA is rejecting the MIP registration request because the HA failed authentication with the PDSN-FA.

FA Requested Lifetime Too Long(69)

The total number of registration reply messages received with an error code value of 69. This error code indicates that the PDSN-FA is rejecting the MIP registration request because the requested lifetime is too long.

FA Poorly Formed Request(70)

The total number of registration reply messages received with an error code value of 70. This error code indicates that the PDSN-FA is rejecting the MIP registration request because of a problem with the message such as a missing mandatory extension.

Table 4-8 Mobile IP Measurements (Continued)

Counter Description



Poorly Formed Reply(71)

The total number of registration reply messages received with an error code value of 71. This error code indicates that the PDSN-FA is rejecting the MIP registration reply received from the HA because of a problem with the message such as a missing mandatory extension.

FA Requested Encapsulation Unavailable(72)

The total number of registration reply messages received with an error code value of 72. This error code indicates that the PDSN-FA is rejecting the MIP registration request because the requested mode of encapsulation is not supported.

FA Requested VJ Compression Unavailable(73)

The total number of registration reply messages received with an error code value of 73. This error code indicates that the PDSN-FA is rejecting the MIP registration request because the requested VJ Compression is not supported.

Requested Reverse Tunnel Unavailable(74)

The total number of registration reply messages received with an error code value of 74. This error code indicates that the PDSN-FA is rejecting the MIP registration request because the requested reverse tunneling is not supported.

Reverse Tunnel Is Mandatory And T Bit Not Set(75)

The total number of registration reply messages received with an error code value of 75. This error code indicates that the PDSN-FA is rejecting the MIP registration request because the reverse tunneling is required but the T bit in registration request is not set.

Mobile Node Too Distant(76)

The total number of registration reply messages received with an error code value of 76. This error code indicates that the PDSN-FA is rejecting the MIP registration request because mobile node is physically too far from the PDSN-FA.

Invalid Care Of Address(77)

The total number of registration reply messages received with an error code value of 77. This error code indicates that the 'D' bit is set to 0, and the specified care of address is not offered by the PDSN-FA.

Registration Timeout(78)

The total number of registration reply messages received with an error code value of 78. This error code indicates that the PDSN-FA is rejecting the MIP registration request because the registration request has been pending for more than 7 seconds.


Counter Description



Delivery Style Not Supported(79)

The total number of registration reply messages received with an error code value of 79. This error code indicates that the PDSN-FA is rejecting the MIP registration request because it does not implement the encapsulating delivery style.

FA Home Network Unreachable(80)

The total number of registration reply messages received with an error code value of 80. This error code indicates that the Home Agents home network is unreachable from the PDSN-FA.

FA Home Agent Host Unreachable(81)

The total number of registration reply messages received with an error code value of 81. This error code indicates that Home Agents host is unreachable from the PDSN-FA.

FA Home Agent Port Unreachable(82)

The total number of registration reply messages received with an error code value of 82. This error code indicates that the Home Agent’s port is unreachable from the PDSN-FA.

FA Home Agent Unreachable(88)

The total number of registration reply messages received with an error code value of 88. This error code indicates that the Home Agent is unreachable from the PDSN-FA.

Vendor Specific Reason(89)

The total number of registration reply messages received with an error code value of 89.

Non Zero Home Address Required(96)

The total number of registration reply messages received with an error code value of 96. This error code indicates that the PDSN-FA cannot manage pending registration request records with a home address of 0.0.0.0.

Missing Nai(97) The total number of registration reply messages received with an error code value of 97. This error code indicates that the PDSN-FA received a registration reply from the HA that was missing the NAI.

Missing Home Agent(98)

The total number of registration reply messages received with an error code value of 98. This error code indicates that the PDSN-FA received a registration reply from the HA that contained a Home Agent address of 0.0.0.0.

Missing Home Address(99)

The total number of registration reply messages received with an error code value of 99. This error code indicates that the PDSN-FA received a registration reply from the HA that contained a Home address of 0.0.0.0.


Counter Description



FA Error 1(100) The total number of registration reply messages received with an error code value of 100.This error code indicates an unsupported Vendor-ID, or that the PDSN-FA is unable to interpret Vendor-CVSE-Type in the CVSE sent by the MN to the PDSN-FA.

FA Error 2(101) The total number of registration reply messages received with an error code value of 101.This error code indicates an unsupported Vendor-ID, or that the PDSN-FA is unable to interpret Vendor-CVSE-Type in the CVSE sent by the HA to the PDSN-FA.

Unknown Challenge(104)

The total number of registration reply messages received with an error code value of 104.This error code indicates that the MN has moved to a new PDSN-FA that is unable to validate the challenge in the registration request.

Missing Challenge(105)

The total number of registration reply messages received with an error code value of 105.This error code indicates that the PDSN-FA received a registration request that was missing the challenge value.

Stale Challenge(106) The total number of registration reply messages received with an error code value of 106.This error code indicates that the PDSN-FA received a registration request that used a stale challenge value (e.g., this challenge value had been used in a previous registration request).

HA Reason Unspecifed(128)

The total number of registration reply messages received with an error code value of 128. This error code indicates that the HA is rejecting the MIP registration request for unknown reasons.

HA Admin Prohibited(129)

The total number of registration reply messages received with an error code value of 129. This error code indicates that provisioning on the HA is rejecting the MIP registration request.

HA Insufficient Resources(130)

The total number of registration reply messages received with an error code value of 130. This error code indicates that the HA is rejecting the MIP registration request because of a shortage of resources such as memory.


Counter Description



HAMN Authorization Failures(131)

The total number of registration reply messages received with an error code value of 131. This error code indicates that the HA is rejecting the MIP registration request because the MN failed authentication with the HA.

HAFA Authorization Failures(132)

The total number of registration reply messages received with an error code value of 132. This error code indicates that the HA is rejecting the MIP registration request because the PDSN-FA failed authentication with the HA.

Registration Identification Mismatch(133)

The total number of registration reply messages received with an error code value of 133. This error code indicates that the HA is rejecting the MIP registration request because it failed replay protection.

HA Poorly Formed Request(134)

The total number of registration reply messages received with an error code value of 134. This error code indicates that the HA is rejecting the MIP registration request because of a problem with the message such as a missing mandatory extension.

Too Many Simultaneous Bindings(135)

The total number of registration reply messages received with an error code value of 135. This error code indicates that the HA is rejecting the MIP registration request because the number of current registrations for the MN exceeds the maximum number of bindings provisioned on the HA for that MN.

Unknown Home Agent Address(136)

The total number of registration reply messages received with an error code value of 136. This error code indicates that the MN is performing dynamic home agent address resolution and the home agent is providing the MN with its IP address.

Reverse Tunnel Unavailable(137)

The total number of registration reply messages received with an error code value of 137. This error code indicates that the HA is rejecting the MIP registration request because the requested reverse tunneling is not supported.


The total number of registration reply messages received with an error code value of 138. This error code indicates that the HA is rejecting the MIP registration request because reverse tunneling is required but the T bit in the registration request is not set.


Counter Description



Requested Encapsulation Not Available(139)

The total number of registration reply messages received with an error code value of 139. This error code indicates that the HA is rejecting the MIP registration request because the requested mode of encapsulation is not supported.

HA Error 1(140) The total number of registration reply messages received with an error code value of 140.This error code indicates an unsupported Vendor-ID, or that the HA is unable to interpret Vendor-CVSE-Type in the CVSE sent by the MN to the HA.

HA Error 2(141) The total number of registration reply messages received with an error code value of 141. This error code indicates an unsupported Vendor-ID, or that the HA is unable to interpret Vendor-CVSE-Type in the CVSE sent by the PDSN-FA to the HA.

HA UDP Encapsulation Unavailable(142)

The total number of registration reply messages received with an error code value of 142. This is used by the HA to distinguish a registration denial caused by an unavailable UDP tunnel encapsulation mode from a denial caused by unavailable standard tunnel encapsulation requested by use of the 'T' bit together with either 'M' or 'G' bit.

FA Busy The total number of agent advertisements received indicating that the PDSN-FA is busy and cannot accept new mobile registrations.

Reregister Attempts The total number of reregistration messages sent.

No Registration Reply The total number of timeouts that have occurred while waiting for a registration reply message in response to a registration request message.

MIP Attempts The total number of MIP session attempts.

MIP Successes The total number of successful MIP session attempts.

MIP Failures The total number of MIP session attempts that failed due to one of the errors listed.

Registration Retries Exceeded

The total number of MIP registration attempts that resulted in the number of retry attempts being exceeded.

Deregistration Messages Sent

The total number of registration messages sent containing a lifetime value of zero, indicating that the call should be deregistered.


Counter Description

Test Case MeasurementsMIP Node Emulator Measurements


MIP Node Emulator MeasurementsThe measurements described in Table 4-12 are collected by the CPTS, and reported on the MIP Node tab, when testing in a SIP, FA Nodal, HA Nodal, or End-to-End test configuration.

Deregistration Reply Messages Received

The total number of deregistration reply messages received.


Average Connect Time The average time in microseconds that it takes to establish a MIP session.


The average time in microseconds that it takes to tear down a MIP session.


Counter Description

Table 4-9 MIP Node Emulation Measurements

Counter Description


MIP Total Received Packets

The total number of packets received at the MIP node emulator.

MIP Total Sent Packets The total number of packets sent by the MIP node emulator.

MIP Total Received Bytes

The total number of bytes received by the MIP node emulator.

MIP Total Sent Bytes The total number of bytes sent by the MIP node emulator.

MIP Total Packets The total number of packets processed by the MIP node emulator.

MIP Total Bytes The total number of bytes processed by the MIP node emulator.

MIP Total Packets/Sec The data throughput rate in packets per second.

MIP Total Bits/Sec The data throughput rate in bits per second.

Test Case MeasurementsFA Emulation Measurements


FA Emulation MeasurementsThe measurements described in Table 4-10 can be collected by the CPTS, and reported on the FA Emulation tab, when testing in the HA Nodal configuration.

Table 4-10 FA Emulation Measurements

Counter Description


RRQ Messages Sent The total number of registration requests sent to the HA.

RRQ Messages Non VPN Sent

The total number of registration requests sent for non-HA VPN subscribers.

RRQ Messages VPN Sent

The total number of registration requests sent for HA-VPN subscribers.

RRP Messages Received

The total number of registration replies received from the HA.

De-registration Messages Sent

The total number of registration messages sent by the emulated PDSN-FA containing a lifetime value of zero, indicating that the call should be deregistered.

De-registration Reply Messages Received

The total number of de-registration replies received from the HA.

RRV Messages Sent The total number of registration revocation messages sent.

RRV Messages Received

The total number of registration revocation messages received.

RRVA Messages Sent The total number of registration revocation acknowledgement messages sent.

RRVA Messages Received

The total number of registration revocation acknowledgement messages received.

HA Reason Unspecifed(128)

The total number of registration reply messages received with an error code value of 128. This error code indicates that the HA is rejecting the MIP registration request for unknown reasons.

HA Admin Prohibited(129)

The total number of registration reply messages received with an error code value of 129. This error code indicates that provisioning on the HA is rejecting the MIP registration request.



HA Insufficient Resources(130)

The total number of registration reply messages received with an error code value of 130. This error code indicates that the HA is rejecting the MIP registration request because of a shortage of resources such as memory.

HAMN Authorization Failures(131)

The total number of registration reply messages received with an error code value of 131. This error code indicates that the HA is rejecting the MIP registration request because the MN failed authentication with the HA.

HAFA Authorization Failures(132)

The total number of registration reply messages received with an error code value of 132. This error code indicates that the HA is rejecting the MIP registration request because the PDSN-FA failed authentication with the HA.

Registration Identification Mismatch(133)

The total number of registration reply messages received with an error code value of 133. This error code indicates that the HA is rejecting the MIP registration request because it failed replay protection.

HA Poorly Formed Request(134)

The total number of registration reply messages received with an error code value of 134. This error code indicates that the HA is rejecting the MIP registration request because of a problem with the message such as a missing mandatory extension.

Too Many Simultaneous Bindings(135)

The total number of registration reply messages received with an error code value of 135. This error code indicates that the HA is rejecting the MIP registration request because the number of current registrations for the MN exceeds the maximum number of bindings provisioned on the HA for that MN.

Unknown Home Agent Address(136)

The total number of registration reply messages received with an error code value of 136. This error code indicates that the MN is performing dynamic home agent address resolution and the home agent is providing the MN with its IP address.

Reverse Tunnel Unavailable(137)

The total number of registration reply messages received with an error code value of 137. This error code indicates that the HA is rejecting the MIP registration request because the requested reverse tunneling is not supported.

Table 4-10 FA Emulation Measurements (Continued)

Counter Description




The total number of registration reply messages received with an error code value of 138. This error code indicates that the HA is rejecting the MIP registration request because reverse tunneling is required but the T bit in the registration request is not set.

Requested Encapsulation Not Available(139)

The total number of registration reply messages received with an error code value of 139. This error code indicates that the HA is rejecting the MIP registration request because the requested mode of encapsulation is not supported.

HA Error 1(140) The total number of registration reply messages received with an error code value of 140.This error code indicates an unsupported Vendor-ID, or that the HA is unable to interpret Vendor-CVSE-Type in the CVSE sent by the MN to the HA.

HA Error 2(141) The total number of registration reply messages received with an error code value of 141. This error code indicates an unsupported Vendor-ID, or that the HA is unable to interpret Vendor-CVSE-Type in the CVSE sent by the PDSN-FA to the HA.

HA UDP Encapsulation Unavailable(142)

The total number of registration reply messages received with an error code value of 142. This is used by the HA to distinguish a registration denial caused by an unavailable UDP tunnel encapsulation mode from a denial caused by an unavailable standard tunnel encapsulation (requested by use of the 'T' bit together with either 'M' or 'G' bit).

Reregister Attempts The total number of reregistration messages that have been sent from the emulated PDSN-FA.

FA MIP Attempts The total number of FA MIP session attempts.

FA MIP Successes The total number of successful FA MIP session attempts.

FA MIP Failures The rotal number of FA MIP session attempts that failed due to one of the errors listed.

FA No Registration Reply

The total number of MIP registration attempts that received no reply.

FA Registration Retry Exceeded

The total number of PDSN-FA registration attempts that resulted in the number of retry attempts being exceeded.

FA Disconnect Count The total number of sessions disconnected.


Counter Description

Test Case MeasurementsHA Emulation Measurements


HA Emulation MeasurementsThe measurements described in Table 4-11 can be collected by the CPTS, and reported on the HA Emulation tab, when in an FA Nodal configuration.

FA Average Connect Time

Average time in microseconds that it takes to establish a MIP session.

FA Average Disconnect Time

Average time in microseconds that it takes to tear down a MIP session.


Counter Description

Table 4-11 HA Emulation Measurements

Counter Description


RRQ Messages Received

The total number of registration requests received from the PDSN-FA

RRP Messages Sent The total number of registration replies sent to the PDSN-FA.

RRV Messages Sent The total number of registration revocation messages sent to the PDSN-FA.

RRV Messages Received

The total number of registration revocation messages received from the PDSN-FA.

RRVA Messages Sent The total number of registration revocation acknowledgement messages sent to the PDSN-FA.

RRVA Messages Received

The total number of registration revocation acknowledgement messages received from the PDSN-FA.

HAMN Authorization Failures

The total number of registration requests denials sent due to HA mobile node authorization failure.

HAFA Authorization Failures

The total number of registration requests denials sent due to HA FA authorization failure.

HA MIP Successes The total number of successful HA MIP attempts.

HA Disconnect Count The total number of sessions disconnected.

Test Case MeasurementsPCF Emulation Measurements


PCF Emulation MeasurementsThe measurements described in Table 4-12 are collected by the CPTS, and reported on the Open RP PCF tab, when testing in a SIP, Simple IP VPN, FA Nodal, or End-to-End test configuration.

HA Average Connect Time

The average time in microseconds that it takes to establish a MIP session.

HA Average Disconnect Time

The average time in microseconds that it takes to tear down a MIP session.

Table 4-11 HA Emulation Measurements (Continued)

Counter Description

Table 4-12 PCF Emulation Measurements

Counter Description


Total Received Packets The total number of packets received at the PCF. This count includes all control packets destined for the higher layer protocols such as RP, PPP, and MIP, and all data packets destined for the traffic layer.

Total Sent Packets The total number of packets sent by the PCF. This count includes all control packets sent for the higher layer protocols such as RP, PPP, MIP and all data packets sent for the traffic layer.

Total Received Bytes The total number of bytes received.

Total Sent Bytes The total number of bytes sent.

Total Packets The total number of packets processed by the PCF.

Total Bytes The total number of bytes processed by the PCF.

Total Packets/Sec The data throughput rate in packets per second. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Total Bits/Sec The data throughput rate in bits per second. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Test Case MeasurementsNetwork Host Emulator Measurements


Network Host Emulator MeasurementsThe measurements described in Table 4-13 are collected by the CPTS, and reported on the Network Host tab, when performing data plane testing using an emulated network host.

Important:

• When using an emulated network host and Host Data Expansion is enabled, all measurements that record total packets or bytes sent from the emulated network host will be multiplied by the value entered (see “Data Traffic Parameters” in Chapter 3).

• When Host Initiated Transfer is enabled, two packets will be received from the MN and recorded in the packets and bytes received measurements: one packet to announce the establishment of the data session (SYN) and one to terminate the data session (ACK).

Table 4-13 Network Host Measurements

Counter Description


Host Sent Packets The total number of packets sent by the host.

Host Received Packets The total number of packets received by the host.

Host Sent Bytes The total number of bytes sent by the host.

Host Received Bytes The total number of bytes received by the host.

Host Packets The total number of packets processed by the host.

Host Bytes The total number of bytes processed by the host.

Host Invalid Packets Received

The total number of invalid packets received by the host.

Host Latency Packet Count

The total number of packets received by the host.

Host Average Packet Latency

The average packet latency, measured in microseconds, and measured on data sent by the mobile node emulator and received at the network host.

Host Packets/Sec The data throughput rate in packets per second. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Host Bits/Sec The data throughput rate in bits per second. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Test Case MeasurementsData Traffic Measurements


Data Traffic MeasurementsThe data measurements described in Table 4-16 are collected by the CPTS, and reported on the Data Traffic tab, when performing data plane testing.

Important:

• When Host Data Expansion is enabled, all measurements that record total packets or bytes received from the network host will be multiplied by the value entered (see “Data Traffic Parameters” in Chapter 3).

• When Host Initiated Transfer is enabled, two packets will be sent to the network host and recorded in the packets and bytes sent measurements: one packet to announce the establishment of the data session (SYN) and one to terminate the data session (ACK).

Interpreting Data Traffic Measurements

In addition to the notes above, the information collected in the packets and bytes sent and received measurements is affected by the protocol selected and the Payload Data Size definition. As a general rule, the payload bytes measurements report the data payload only, the TCP bytes measurements report the sum of the data payload and the TCP header, and the total bytes measurements report the sum of the data payload, the TCP header, and the IP header (the IP header is not applicable to MIP). The tables below correlate the payload (PL) definition and the affected measurements using a sample payload definition.

Important: The samples below were generated from a test session using an extremely slow data rate (.05 packets/second) in order that the single packet or message sequence sent is contained in the same interval as the response packet or message sequence. During normal testing message sequences and responses will often be captured in separate inter-vals.

With simple data types (send a packet, receive a packet), the payload measurements report only the user-defined payload as shown in the sample in Table 4-14.

Note: ICMP and RAW are not included in the payload bytes sent and received measurements.



With more complex data types (those that use message sequences), the packets/second portion of the payload definition equates to transactions/second, and the payload bytes measurements include not only the data payload but the request and response commands. Each message is included in the packets sent and received measurements.

Table 4-15 shows the message sequence and associated measurements for complex data types.

Table 4-14 Simple Data Type Measurements

Proto-col

PL Size

PL Bytes Sent

PL Bytes Rcvd

TCP Bytes Sent(PL + TCP)

TCP Bytes Rcvd(PL + TCP)

Total Bytes Sent(PL+TCP+IP)

Total Bytes Rcvd(PL+TCP+IP)

ICMP 64 0 0 0 0 IP Hdr: 20

ICMP Hdr: 8

PL: 64

92 bytes

IP Hdr: 20

ICMP Hdr: 8

PL: 64

92 bytes

WAP/UDP

URL size

33 (header + URL)

199 (response)

0 0 IP Hdr: 20

UDP Hdr: 8

PL: 33

61 bytes

IP Hdr: 20

UDP Hdr: 8

Resp: 199

227 bytes

RAW 28 0 0 0 0 IP Hdr: 20

RAW Hdr: 8

PL: 28

56 bytes

IP Hdr: 20

RAW Hdr: 8

PL: 28

56 bytes

UDP 28 28 28 0 0 IP Hdr: 20

UDP Hdr: 8

PL: 28

56 bytes

IP Hdr: 20

UDP Hdr: 8

PL: 28

56 bytes

TCP 16 16 16 TCP Hdr: 20

PL: 16

36 bytes

TCP Hdr: 20

PL: 16

36 bytes

IP Hdr: 20

TCP Hdr: 20

PL: 16

56 bytes

IP Hdr: 20

TCP Hdr: 20

PL: 16

56 bytes



Table 4-15 Complex Data Type Measurements

Msg PL Size

PL Bytes Sent

PL Bytes Rcvd





HTTP 10 SYN: 0

1GET: 114

ACK: 0

114 bytes

SYN/ACK: 0

2OK: 161

161 bytes

SYN: 24

GET: 134

ACK: 20

178 bytes

SYN/ACK: 20

OK: 181

201 bytes

SYN: 44

GET: 154

ACK: 40

238 bytes

SYN/ACK: 40

OK: 201

241 bytes

FTP 10 SYN: 0

USER: 14

PASS: 14

PASV: 6

SYN: 0

ACK: 0

RETR: 15

FIN/ACK: 0

ACK: 0

49 bytes

SYN/ACK: 0

spec pw: 34

logged in: 20

pasv: 47

SYN/ACK: 0

Response: 53

3Data: 10

Closing: 55

ACK: 0

219 bytes

SYN: 24

USER: 34

PASS: 34

PASV: 26

SYN: 24

ACK: 20

RETR: 35

FIN/ACK: 20

ACK: 20

237 bytes

SYN/ACK: 20

spec pw: 54

logged in: 40

pasv: 67

SYN/ACK: 20

Response: 73

Data: 30

Closing: 75

ACK: 20

399 bytes

SYN: 44

USER: 54

PASS: 54

PASV: 46

SYN: 44

ACK: 40

RETR: 55

FIN/ACK: 40

ACK: 40

417 bytes

SYN/ACK: 40

spec pw: 74

logged in: 60

pasv: 87

SYN/ACK: 40

Response: 93

Data: 50

Closing: 95

ACK: 40

579 bytes

WAP/TCP

N/A SYN: 0

4PSH/ACK: 57

ACK: 0

57 bytes

SYN/ACK: 0

4PSH: 457

457 bytes

SYN: 24

PSH/ACK: 77

ACK: 20

121 bytes

SYN/ACK: 20

PSH: 477

497 bytes

SYN: 44

PSH/ACK: 97

ACK: 40

181 bytes

SYN/ACK: 40

PSH: 497

537 bytes



SMTP 10 SYN: 0

Cmd: 14

5ACK: 0

Mail Fr: 27

ACK: 0

RCPT TO: 25

ACK: 0

Data: 6

ACK: 0

6Body: 15

ACK: 0

QUIT: 6

ACK: 0

93 bytes

SYN/ACK: 0

Response: 71

Response: 8

Response: 8

Response: 46

Response: 8

Response: 50

191 bytes

SYN: 24

Cmd: 34

ACK: 20

Mail Fr: 47

ACK: 20

RCPT TO: 45

ACK: 20

Data: 26

ACK: 20

Body: 35

ACK: 20

QUIT: 26

ACK: 20

357 bytes

SYN/ACK: 20

Response: 91

Response: 28

Response: 28

Response: 66

Response: 28

Response: 70

331 bytes

SYN: 44

Cmd: 54

ACK: 40

Mail Fr: 67

ACK: 40

RCPT TO: 65

ACK: 40

Data: 46

ACK: 40

Body: 55

ACK: 40

QUIT: 46

ACK: 40

617 bytes

SYN/ACK: 40

Response: 111

Response: 48

Response: 48

Response: 86

Response: 48

Response: 90

471 bytes

1GET will vary by request header size. In this example, the default request header was used (HTTP).

2OK includes the response header, the HTML tags, and the defined payload (HTTP).

3Data is the defined payload (FTP).

4PSH/ACK and PSH include the request and response headers and URL and will vary by the URL size (WAP/TCP).

5An ACK will be sent for every response from the network host to prevent re-transmission from the host. (SMTP)

6Message body includes the defined payload plus 5 bytes for EOM code (SMTP).

Table 4-15 Complex Data Type Measurements (Continued)

Msg PL Size

PL Bytes Sent

PL Bytes Rcvd





Table 4-16 Data Traffic Measurements

Counter Description




Data Verify Attempts The total number of attempts to send verification data. Although this value is the sum of Data Verify Successes and Data Verify Failures, the equation may not hold true at any given time during data verification since some sessions may be in a transitory state when the measurements are collected.

If a session cannot be established for reasons that have nothing to do with the data layer, Data Verify Attempts and Total Session Attempts Count will not be incremented since the session never reached the state where data traffic could be attempted.Note: Collected during data verification testing.

Data Verify Successes The total number of verification sessions that were successfully established from the mobile node to the network host.Note: Collected during data verification testing.

Data Verify Failures The total number of unsuccessful verification sessions. These failures will be included in the Session Errors measurement on the Test Summary tab.Note: Collected during data verification testing.

Total Session Attempts Count

The total number of session setup attempts.Note: When a data session that uses TCP cannot be established, the Session Errors measurement on the Test Summary tab is incremented.

Total Session Setup Success

The total number of successful session setups.

Total Packets Sent The total number of packets sent to the far end.

Total Packets Received The total number of packets received from the far end.

Total Packets Invalid The total number of invalid packets received from thefar end.

Total Packets Lost The total number of lost data packets detected by the traffic layer. Due to the way TCP sequence numbers work, the actual lost packets may actually be greater than this count but never less.

Total Duplicate Packets The total number of duplicate packets received from the far end.

Table 4-16 Data Traffic Measurements (Continued)

Counter Description

Test Case MeasurementsL2TP Measurements


L2TP MeasurementsThe L2TP measurements described in Table 4-17 are collected by the CPTS, and reported on the L2TP tab, when testing in a Simple IP VPN test configuration.

Total Fragments Sent The total number of data fragments sent. Fragmentation will occur when the data packet size is greater than 1364 bytes.

Total Fragments Received

The total number of data fragments received.

Total Ping Requests Received

The total number of ping requests received from the far end. This includes ping requests received during verification testing and those received during continuous data testing.

Average Packet Round Trip Delay

The average time required for packets to be sent to and returned from the far end.

Payload Bytes Sent The total number of payload data bytes sent, excluding the bytes in the IP/TCP headers.

Payload Bytes Received

The total number of payload data bytes received, excluding the bytes in the IP/TCP headers.

TCP Bytes Sent The total number of TCP protocol bytes sent, excluding the bytes in the IP header.

TCP Bytes Rcvd The total number of TCP protocol bytes received, excluding the bytes in the IP header.

Total Bytes Sent The total number of bytes sent by the traffic layer.

Total Bytes Received The total number of bytes received by the traffic layer.

Table 4-16 Data Traffic Measurements (Continued)

Counter Description

Table 4-17 L2TP Measurements

Counter Description


Session Data Bytes Sent

The total number of session data bytes sent by the secure gateway emulator.



Session Data Bytes Received

The total number of data bytes received by the secure gateway emulator.

Session Data Packets Sent

The total number of data packets sent by the secure gateway emulator.

Session Data Packets Rcvd

The total number of data packets received by the secure gateway emulator.

Session Attempts The total number of L2TP sessions attempted.

Session Successes The total number of L2TP sessions established.

Session Failures The total number of L2TP session failures.

Session Failure Unspecified

The total number of session failures due to failure unspecified.

Session Tunnel Failure The total number of session failures due to tunnel failure.

Session MEI Set The total number of sessions with MEI set.

Session MEI Not Set The total number of sessions with MEI not set.

Session LNS Terminations

The total number of LNS terminations.

Session LAC Terminations

The total number of LAC terminations.

Session Failures Insufficient Resources

The total number of session failures due to insufficient resources.

Session Failures Poorly Formed Request

The total number of session failures due to poorly formed request.

Session Timeout Failures

The total number of session failures due to timeout.

Session Handoff Attempts

The total number of handoff attempts.

Session Handoff Completions

The total number of handoff completions.

Session No Carrier The total number of session failures due to no carrier.

Table 4-17 L2TP Measurements (Continued)

Counter Description



Session Busy The total number of session failures due to session busy.

Session No Dialtone The total number of session failures due to no dialtone.

Session Framing Error The total number of session failures due to framing error.

Session Vendor Specific

The total number of session failures due to vendor specific error code.

Session Try Another Destination

The total number of session failures due to try another destination.

Tunnel Attempts The total number of tunnel attempts

Tunnel Successes The total number of tunnel successes.

Tunnel Failures The total number of tunnel failures.

Tunnel LNS Terminations

The total number of LNS terminations.

Tunnel LAC Terminations

The total number of LAC terminations

Tunnel Failure Insufficient Resources

The total number of tunnel failures due to insufficient resources.

Tunnel Failure Authentication

The total number of tunnel failures due to authentication error.

Tunnel Failure Poorly Formed Request

The total number of tunnel failures due to poorly formed request.

Tunnel Failure Unspecified

The total number of tunnel failures due to unspecified reason.

Tunnel Unsupported Version

The total number of tunnel failures due to unsupported version.

Tunnel Vendor Specific The total number of tunnel failures due to vendor specific reason.

Tunnel Try Another Dest

The total number of tunnel failures due to try another destination.

Tunnel Fsm Error The total number of tunnel failures due to Fsm error.


Counter Description

Test Case MeasurementsL2TP Node Measurements


L2TP Node MeasurementsThe L2TP Node measurements described in Table 4-18 are collected by the CPTS, and reported on the L2TP Node tab, when testing in a Simple IP VPN test configuration.

Tunnel Requestor Shutdown

The total number of tunnel failures due to requestor shutdown.

Tunnel Control Channel Exists

The total number of tunnel failures due to control channel exists.

Tunnel Delivery Failure The total number of tunnel failures due to delivery failure.

Tunnel Control Pkts Sent

The total number of control packets sent.

Tunnel Control Pkts Rcvd

The total number of control packets received.

Tunnel Data Pkts Sent The total number of data packets sent.

Tunnel Data Pkts Rcvd The total number of data packets received.

Disconnect Count The total number of L2TP tunnels disconnected.

Average Connect Time The average time in microseconds that it takes to establish an L2TP tunnel.


The average time in microseconds that it takes to tear down an L2TP tunnel.


Counter Description

Table 4-18 L2TP Node Measurements

Counter Description


Total Received Packets The total number of packets received at the L2TP node emulator.

Total Sent Packets The total number of packets sent by the L2TP node emulator.

Total Received Bytes The total number of bytes received

Test Case MeasurementsRate Test Measurements


Rate Test MeasurementsThe rate test measurements described in Table 4-19 are collected by the CPTS, and reported on the Rate Test tab, when performing a Session Loading Rate test, a Session Activation Rate Test, an Intra-PDSN Rate test, or an Inter-PDSN Rate test.

Total Sent Bytes The total number of bytes sent.

Total Packets The total number of packets processed by the L2TP node emulator.

Total Bytes The total number of bytes processed by the L2TP node emulator.

Total Packets/Sec The data throughput rate in packets per second. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Total Bits/Sec The data throughput rate in bits per second. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Table 4-18 L2TP Node Measurements

Counter Description

Table 4-19 Rate Test Measurements

Counter Description


Test Type Identifies the type of rate test activity. Options are Session Loading Rate, Session Activation Rate, Intra-PDSN Rate, and Inter-PDSN Rate.

Interval Start Time The start time for the current rate test interval.

Current Hold Time (Seconds)

The current hold time being used for the current test interval. The hold time is adjusted based on error threshold.

Current Pending Time (Seconds)

The current pending, or idle, time being used for the current test interval. This value is adjusted based on the error threshold.

Error Count of Previous Interval

The error count from the previous test interval.

Test Case MeasurementsRate Test Measurements


Connects in last Interval

The total number of session connects during the last test interval.

Disconnects in last Interval

The total number of session disconnects during the last test interval.

Actual Rate of Previous Interval (Sessions/Second)

The actual rate achieved during the last test interval. Refer to “Rate Calculations” for an explanation of how rates are calculated.

Target Session Loading Rate (Sessions/Second)

The target session loading rate requested by the user.

Block Size The size of the session or handoff block tested in the previous test interval.

Total Sessions Established

The total number of sessions established in the previous test interval.

Block Errors The total number of session errors in the previous test interval.

Block Error Rate (Percentage)

The percentage of errors occurring while testing the previous block or last test interval.

Block Test Rate (Sessions/Second)

The activation or handoff rate used during the last block test or last test interval.

Table 4-19 Rate Test Measurements (Continued)

Counter Description



Appendix A

ESD Requirements

Spirent Communications manufactures and sells products that require industry standard precautions to protect against damage from electrostatic discharge (ESD). This document explains the proper process for handling and storing electrostatic discharge sensitive (ESDS) devices, assemblies, and equipment.

The requirements presented in this document comply with the EIA Standard, ANSI/ESD S20.20-1999: Development of an Electrostatic Discharge Control Program, and apply to anyone who handles equipment that is sensitive to electrostatic discharge. Such equipment includes, but it not limited to:

• All electronic assemblies manufactured by Spirent Communications

• Discrete and integrated circuit semiconductors

• Hybrid microcircuits

• Thin film passive devices

• Memory modules

! Caution: Failure to comply with the requirements explained in this document poses risks to the performance of ESDS devices, as well as to your investment in the equipment.

General Equipment Handling

Whenever you handle a piece of ESDS equipment, you must be properly grounded to avoid harming the equipment. Also, when transporting the equipment, it must be packaged properly. Follow the requirements below to help ensure equipment protection.

• Wrist straps must be worn by any person handling the equipment to provide normal grounding.

• The use of foot straps is encouraged to supplement normal grounding. If foot straps are used exclusively, two straps (one on each foot) should be used. Note that foot straps are only applicable in environments that use ESD flooring and/or floor mats.

• Hold ESDS equipment by the edges only; do not touch the electronic components or gold connectors.

• When transporting equipment between ESD protected work areas, the equipment must be contained in ESD protective packaging. Equipment that is received in ESD protective packaging must be opened either by a person who is properly grounded or at an ESD protected workstation.

Appendix A: ESD Requirements


• Any racks or carts used for the temporary storage or transport of ESDS equipment must be grounded either by drag chains or through direct connection to earth ground. Loose parts that are not protected by ESD-safe packaging must not be transported on carts.

Workstation Preparation

The ideal setup for working with ESDS equipment is a workstation designed specifically for that purpose. Figure A-1 illustrates an ESD protected workstation. Please follow the requirements listed below to prepare a proper ESD protected workstation.

• The ESD Ground must be the equipment earth ground. Equipment earth ground is the electrical ground (green) wire at the receptacles.

• An ESD protected workstation consists of a table or workbench with a static dissipative surface or mat that is connected to earth ground. A resistor in the

grounding wire is optional, providing that surface resistance to ground is ≥ 105 to

≤ 109 Ω.

• The workstation must provide for the connection of a wrist strap. The wrist strap must contain a current limiting resistor with a value from ≥ 250K Ω to ≤ 10M Ω.

• ESD protective flooring or floor mats are required when floor-grounding devices (foot straps/footwear) are used or when it is necessary to move in between ESD protected workstations when handling ESDS equipment.

Figure A-1. ESD Protected Workstation

Note: The equipment needed for proper grounding is available in ESD service kits, such as the ESD Field Service Kit available from Spirent Communications (P/N 170-1800). Additional information on ESD can be found on the following website: http://www.esda.org/aboutesd.html.

ESD protective surface or matOptional resistor

Wrist strap

ESD protective floor mat (optional)

http://www.esda.org/aboutesd.html


Appendix B

Fiber Optic Cleaning Guidelines

Spirent Communications manufactures and sells products that contain fiber optic components, including fiber optic transmitters and receivers. These components are extremely susceptible to contamination by particles of dirt or dust, which can obstruct the optic path and cause performance degradation. To ensure optimum product performance, it is important that all optics and connector ferrules be kept clean.

This document presents guidelines for maintaining clean fiber optic components. Spirent Communications recommends that these guidelines be followed very closely.

! Caution: • Failure to comply with the guidelines explained in this document poses risks to the performance of fiber optic-based devices, as well as to your investment in the equipment.

• Whenever you handle a piece of equipment that contains fiber optic components, you must be properly grounded to avoid harming the equipment. See the Appendix in this document titled ESD Requirements for more details on ESD.

Cleaning Guidelines

To ensure the cleanliness of fiber optic components, follow the guidelines below:

• Use fiber patch cords (or connectors if you terminate your own fiber) only from a reputable supplier. Low-quality components can cause many hard-to-diagnose problems during an installation.

• Dust caps are typically installed on fiber optic components to ensure factory-clean optical devices. These protective caps should not be removed until the moment of connecting the fiber cable to the device. Ensure that the fiber is properly terminated, polished, and free of any dust or dirt. Also make sure that the location of installation is as free of dust and dirt as possible.

• Should it be necessary to disconnect the fiber device, reinstall the protective dust caps.

• If you suspect that the optics have been contaminated, alternate between blasting with clean, dry, compressed air and flushing with methanol to remove particles of dirt.



Index

Aacronyms 4

Ccapacity

parameters 122capacity test 45

continuous data 47options 47session verification 47set up 46SUT query 47

cleaning guidelines, fiber optics 213common parameters 118configurations

MIP end-to-end 16MIP FA nodal 12MIP HA nodal 14MIP network based VPN end-to-end 18MIP network based VPN FA nodal 13MIP network based VPN HA nodal 16MIP reverse tunnel 15MIP reverse tunnel end-to-end 17MIP reverse tunnel FA nodal 12MIP VPN end-to-end 17MIP VPN FA nodal 13MIP VPN HA nodal 15simple IP 10simple IP VPN 10simple IP VPRN 11

contacts 8content 2continuous data 85conventions 3

Ddata verification 82

Eend-to-end

test case 38end-to-end MIP

parameters 117equipment handling

ESD service kits 212guidelines 211

preparing your workstation 212ESD requirements 211

FFA nodal

test case 28

Gglossary 6guidelines

(equipment handling) 211

HHA nodal

test case 34

Iinter-PDSN 72

continuous data 77options 76parameters 135, 138session verification 76set up 73SUT query 76

inter-PDSN handoff rate 77options 82set up 77

intra-PDSN handoff 60continuous data 63options 63parameters 129session verification 63set up 61SUT query 63

intra-PDSN rate 64options 68parameters 131set up 64

LL2TP parameters 140

Mmeasurements

data traffic 199FA emulation 193

Index


HA emulation 196L2TP 204L2TP node 207MIP node emulator 192mobile IP 185network host emulator 198PCF emulation 197PPP 182rate test 208RP 179test summary 174

CPU usage 177L2TP VPN 178MIP revocation 178session loading 177

MIPend-to-end

configurations 16test case 38

FA nodalconfigurations 12parameters 113test case 28

HA nodalconfigurations 14parameters 115, 168test case 34

reverse tunnelconfigurations 15

MIP network based VPNend-to-end

configurations 18FA nodal

configurations 13HA nodal

configurations 16MIP parameters 164MIP reverse tunnel

end-to-endconfigurations 17

FA nodalconfigurations 12

MIP revocation 68options 72parameters 133set up 68

MIP VPNend-to-end

configurations 17FA nodal

configurations 13HA nodal

configurations 15

Nnetwork host

test case 42

Pparameters

capacity 122common 118end-to-end MIP 117inter-PDSN 135, 138intra-PDSN handoff 129intra-PDSN rate 131L2TP 140MIP 164MIP FA nodal 113MIP HA nodal 115, 168MIP revocation 133PPP 148RP 142session activation rate 128session loading 124session loading rate 127session loading with mobility 125simple IP 111simple IP VPN 112SUT query 119test activity 122

PPP parameters 148protocol parameters 93

L2TP 102MIP 94PPP 105RP 98

Rrate calculations 174related manuals 4requirements

electrostatic discharge 211RP parameters 142

Ssession activation rate 57

options 60parameters 128set up 58

session loading 47continuous data 50options 49parameters 124session verification 49set up 48SUT query 49

session loading rate 54options 57parameters 127set up 54

session loading with mobility 50continuous data 54options 53parameters 125session verification 53

Index


set up 50SUT query 53

simple IPconfigurations 10parameters 111test case 20

simple IP VPNconfigurations 10parameters 112test case 24

simple IP VPRNconfigurations 11

Spirent Communicationscompany address 8technical support 8

SUT query 88parameters 119

Ttechnical support 8test activities 45test activity parameters 122test cases 20

Vvariable parameter values 111

Wworkstation preparation 212

Documents

0904 1296C CPTS Test Guide