思博伦网络测试培训06-SmartBits_SmartApp

SmartApplications

Topics Overview

Introduction

User Interface

Card Configuration

Traffic Configuration

Test Setup

Running a Test

Interpreting Results

What is SmartApplications?

SmartApplications is based on Internet Engineering Task Force (IETF) Benchmarking Methodologies Working Group RFCs.

RFC 1242 “Benchmarking Terminology for Network Interconnection Devices”

RFC 2544 “Benchmarking Methodology for Network Interconnect Devices”

SmartApplications provides you with industry-standard Benchmark testing of interconnect devices.

SmartApplications supports 10/100/1000 Ethernet, Token Ring, ATM and Frame Relay mixed-topology testing.

SmartApplications provides support for most currently released cards.

SmartApps supports remote one-way latency testing using GPS.

SmartApplications provides Layer 2 and Layer 3 tests.

SmartApplications provides “Next Hop”Router tests.

SmartApplications supports 1 to 1, 1 to Many, and Many to 1tests.

SmartApplications provides Uni. and Bi-directional tests.

SmartApplications was designed to test a device/system, not a live Network.

RFC 1242 Overview

RFC 1242, "Benchmarking Terminology for Network Interconnection Devices," was authored by Scott Bradner of Harvard University in July 1991. It defines a number of terms that are used in describing performance benchmarking tests and the results of such tests. Some of the terms defined by RFC 1242 are:

–Back-to-back –Constant Load

–Data link frame size –Fragment

–Frame Loss Rate –Inter Frame Gap –Latency

–Link Speed Mismatch

–MTU-mismatch behavior –Overhead behavior –Overloaded behavior –Policy based filtering –Restart behavior –Router

–Single frame behavior –Throughput

RFC 2544 Summary

Suggested frame sizes for Ethernet testing:

64, 128, 256, 512, 1024, 1280, 1518

At least five frame sizes SHOULD be tested for each test condition

The Throughput test should be at least 60 seconds per iteration

The Latency test should be at least 120 seconds per iteration and must be run at least 20 times with average taken. Also, it should run at the determined

Throughput rate.

Frame Loss rate resolution must not be greater then 10%

The Back-to-Back test trial length must be at least 2 seconds and should be repeated at least 50 times with the average taken

All tests should be run with and without filters enabled on the DUT Either Layer 2 MAC or Layer 3 Protocol addresses depending on the DUT Traffic should be sent Bi-directionally

An application level datagram echo request is used for the test data frame in the protocols that support such a function

For TCP/IP a UDP Echo Request is used