SmartBits
Performance Analysis System
SmartApplications
User Guide
Version 2.50
January 2002
P/N 340-0027-002 REV H
Spirent Communications, Inc.
(800) 886-8842 Toll Free
(818) 676-2300 Phone
(818) 881-9154 FAX
Copyright 2002 Spirent Communications, Inc. All Rights Reserved.
The information contained in this document is the property of Spirent Communications, and is furnished for use by
recipient only for the purpose stated in the Software License Agreement accompanying the document. Except as permitted by such License Agreement, no part of this publication may be reproduced, stored in a retrieval system, or
transmitted, in any form or by any means, without the prior written permission of Spirent Communications, Inc.
Disclaimer
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.
Trademarks
AST II, ScriptCenter, SmartApplications, SmartBits
, SmartCableModem,SmartFabric,SmartFlow,
SmartLib, SmartMetrics, SmartMulticastIP,SmartSignaling,SmartTCP, SmartVoIPQoS,
SmartWindow,SmartxDSL, TeraMetrics, TeraMobileIP, TeraRouting Tester, TeraVPN,VAST,and
WebSuite are trademarks or registered trademarks of Spirent Communications, Inc.
All other trademarks and registered trademarks are the property of their respective owners.
Warranty
Spirent Communications warrants to recipient that hardware which it supplies with this document (“Product”) will be
free from significant defects in materials and workmanship for a period of twelve (12) months from the date of
delivery (the “Warranty Period”), under normal use and conditions.
Defective Product under warranty shall be, at Spirent Communications’ discretion, repaired or replaced or a credit
issued to recipient’s account for an amount equal to the price paid for such Product provided that: (a) such Product is
returned to Spirent Communications after first obtaining a return authorization number and shipping instructions,
freight prepaid, to Spirent Communications’ location in the United States; (b) recipient provide a written explanation of
the defect claimed; 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 Communications
will ship repaired Product to recipient, freight prepaid, within ten (10) working days after receipt of defective Product.
Except as otherwise stated, any claim on account of defective materials or for any other cause whatsoever will
conclusively be deemed waived by recipient unless written notice thereof is given to Spirent Communications within
the Warranty Period. Product will be subject to Spirent Communications’ standard tolerances for variations.
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 COMMUNICATIONS INC., IF
ANY, FOR DAMAGES RELATING TO ANY ALLEGEDLY DEFECTIVE PRODUCT SHALL BE LIMITED TO THE
ACTUAL PRICE PAID BY THE PURCHASER FOR SUCH PRODUCT. IN NO EVENT WILL SPIRENT
COMMUNICATIONS INC. BE LIABLE FOR COSTS OF PROCUREMENT OF SUBSTITUTE PRODUCTS OR SERVICES,
LOST PROFITS, OR ANY SPECIAL, DIRECT, INDIRECT, CONSEQUENTIAL, OR INCIDENTAL DAMAGES,
HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, ARISING IN ANY WAY OUT OF THE SALE
AND/OR LICENSE OF PRODUCTS OR SERVICES TO RECIPIENT EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE
OF ANY LIMITED REMEDY.
ii SmartApplications User Guide
Contents
About this Guide 1
Purpose ...................................................................... 2
Audience ..................................................................... 2
ManualContents ............................................................... 2
ConventionsUsedinThisGuide................................................... 3
RelatedManuals ............................................................... 3
OnlineHelp................................................................... 4
HowtoContactUs.............................................................. 4
Chapter 1 SmartApplications Overview 5
WhatisSmartApplications? ...................................................... 6
What are SmartCards and Modules? . . .............................................. 7
SupportedCardsandModules..................................................... 7
Chapter 2 Basic Test Theory 9
General Testing Methodology. ................................................... 10
TestTerminology ......................................................... 10
AddressLearningforSmartCards............................................. 11
Throughput Test Methodology ................................................... 12
Acceptable Loss Throughput................................................. 13
Latency Test Methodology . . . ................................................... 14
Packet Loss Rate Test Methodology . . ............................................. 16
Back-to-BackTestMethodology.................................................. 17
Chapter 3 Install and Connect 19
Install SmartApplications ....................................................... 20
SystemRequirements ...................................................... 20
InstallingfromtheCD...................................................... 21
Launch SmartApplications....................................................... 21
Chapter 4 Basic Navigation and Tools 23
FeaturesoftheMainWindow.................................................... 24
Menus .................................................................. 25
LaunchButtons ........................................................... 28
ToolbarButtons........................................................... 29
PortSelectionArea ........................................................ 31
ChartingTestResults........................................................... 33
SmartApplications User Guide iii
Contents
Chapter 5 Set Up Tests 35
SummaryofStepstoSetupaTest ................................................ 36
ConnecttheDeviceUnderTest................................................... 36
SmartBitsConnectionSetup..................................................... 37
ConnectUsingaSerialPort.................................................. 38
ConnectUsinganEthernetPort .............................................. 40
Making the Connection . . ................................................... 41
LinkingMultipleSmartBitsChassis........................................... 42
Multi-UserAccess......................................................... 43
ReservingCards........................................................... 44
Starting and Stopping a Test . . ................................................... 46
SetUpTestConfigurations...................................................... 48
TestConfigurationOptions.................................................. 49
PreferenceTab............................................................ 55
Offeredvs.IntendedLoad................................................... 58
SavingaTestConfiguration ................................................. 59
SelectTestPorts .............................................................. 60
Hub,Slot,andPortNumbering............................................... 61
AllowedPortPairCombinations.............................................. 61
Running1to1Tests....................................................... 64
Running1toMany/Manyto1Tests........................................... 66
ConfigureTestPorts ........................................................... 67
ConfiguringMultiplePortsatOnce ........................................... 68
ConfiguringaPortsIndividually.............................................. 70
ConfiguringEthernetPorts .................................................. 71
ConfiguringTokenRingPorts ............................................... 74
ConfiguringATMPorts..................................................... 79
ConfiguringWANPorts .................................................... 96
RouterTesting............................................................... 115
SetupNextHopTests......................................................... 117
SetUpIP/UDP/IPXProtocols................................................... 119
SetupATM1-to-Many/Many-to-1TestswithPVCCLIP............................. 123
Chapter 6 Run Tests 125
TestPhases.................................................................. 126
DeviceUnderTestInitialization............................................. 126
LoadGeneration ......................................................... 126
ViewingTestResults.......................................................... 127
Results Window by Test Tab................................................ 127
ViewingtheResultsofPreviousConfigurations ................................ 129
ViewingandPrintingTestReports........................................... 130
GeneratingHTMLTestReports................................................. 133
ViewingandPrintingASCIITextReportFiles ..................................... 136
Sample Reports – Throughput Test........................................... 137
SampleReports–LatencyTest.............................................. 140
SampleReports–PacketLossTest........................................... 143
SampleReports–Back-to-BackTest ......................................... 146
ViewingLogContents......................................................... 149
iv SmartApplications User Guide
Chapter 7 Test Examples 151
Throughput Test — Example . .................................................. 152
Setup — Throughput Test Example . . . ....................................... 152
Results — Throughput Test Example . . ....................................... 154
SampleTestLog ......................................................... 155
SampleTestReport....................................................... 156
LatencyTest—Example ...................................................... 157
SampleTestConfiguration ................................................. 157
SampleTestResultsWindowforLatency ..................................... 158
PacketLossTest—Example ................................................... 159
SampleTestConfiguration ................................................. 159
Sample Results Window . .................................................. 160
Back-to-BackTest—Example.................................................. 161
SampleTestConfiguration ................................................. 161
Sample Results Window . .................................................. 162
Glossary 163
AcronymsandAbbreviations ............................................... 163
Terminology ............................................................ 166
Contents
Index 169
SmartApplications User Guide v
vi SmartApplications User Guide
About this Guide
In
About this Guide...
This portion of the user guide contains the following sections:
• Purpose.....2
• Audience.....2
• Manual Contents.....2
• Conventions Used in This Guide.....3
• Related Manuals.....3
• Online Help.....4
• How to Contact Us.....4
SmartApplications User Guide 1
About this Guide
Purpose
Purpose
This user guide provides information on all procedures required to perform tests using
SmartApplications 2.50 application software. This includes details on software
installation, test setup, and test result interpretation.
Audience
This user guide is for users of SmartApplications 2.50 software. It is assumed that users of
this guide are familiar with Microsoft Windows and SmartBits equipment, and have an
intermediate knowledge level of data communications theory.
Manual Contents
This guide contains the following chapters:
Chapter Title Description
1 SmartApplications Overview Provides an overview of SmartApplications.
Basic Test Theory Explains general theory of operation and rules for testing.
3 Install and Connect Lists system requirements and explains how to connect your PC to
the SmartBits and DUT.
4 Basic Navigation and Tools Describes the SmartApplications main window and results
windows, including menus and task buttons.
5SetUpTests Explains procedures required to set up SmartApplications tests.
6RunTests Explains procedures to start, stop, and run tests, and view reports.
7 Test Examples Provides sample test scenarios and explains test results.
2 SmartApplications User Guide
Conventions Used in This Guide
This guide uses the following conventions:
• Italics are used for document names and special terms.
• Menu options, field names, and tab names are bolded.
• Paths are shown with “greater than” symbols: Test > Setup Options > Throughput.
In this example, you would click on the Te st menu option, then on the Setup Options
selection,andthenontheThroughput tab.
• Directory and file names are shown in Helvetica.
• The terms packet and frame are used interchangeably.
• The term card is used to refer generally to any SmartCard or module for SmartBits
systems.
Notes, cautions, and other important user information are shown as follows:
Note: Includes related information and tips.
About this Guide
Conventions Used in This Guide
!
Caution: Includes related precautions.
Important: Includes related important.
Warning: Includes related warnings to prevent damage to equipment and or injury.
Related Manuals
Additional SmartBits documentation that is related to this User Guide include:
• SmartBits Getting Started
• SmartBits System Overview and Reference
• Using GPS with SmartBits
SmartApplications User Guide 3
About this Guide
Online Help
Online Help
SmartApplications provides online Help for all windows and tabs. You can access online
Help in two ways:
• Press the F1 key from the window about which you wish information.
• From the menu bar, select Help > Contents to view the entire contents of the Help
file or Help > Search forHelpOntosearchbyaspecifictopicorword.
Chart Facility Help
SmartApplications includes a chart facility that can be used to represent test results
graphically. The facility contains a separate Help file called First Impression. If you
access Help from a chart-related window in either of the ways listed above, you will view
chart-related Help only. Once you return to the Results window, you can view
SmartApplications Help.
How to Contact Us
Technical support is available Monday through Friday between 07:00 and 18:00 Pacific
Standard Time.
To obtain technical support for any product, please contact our Technical Support
Department using any of the following methods:
Phone: +1 800.886.8842 (available in the U.S. and Canada)
+1 818.676.2589
Fax: +1 818.880.9154
E-mail: smartbits.support@spirentcom.com
In addition, the latest versions of application Help files, application notes, and software
and firmware updates are available on our website at:
http://www.spirentcom.com
Company Address
Spirent Communications of Calabasas
26750 Agoura Road
Calabasas, CA 91302
USA
+1 818.676.2300
4 SmartApplications User Guide
1
SmartApplications Overview
In this Chapter
This chapter contains the following sections:
• What is SmartApplications?.....6
• What are SmartCards and Modules?.....7
• Supported Cards and Modules.....7
SmartApplications User Guide 5
Chapter 1: SmartApplications Overview
What is SmartApplications?
What is SmartApplications?
SmartApplications is an easy-to-use suite of tests for LAN switches and routers
connecting to Ethernet, ATM, Wide Area Network (WAN), or Token Ring networks. It
enables you to test how well a device performs with either packet-based or stream-based
network traffic, as simulated by the SmartBits system. You can assess the performance of
a device under test (DUT) with up to 768 ports.
SmartApplications tests are based on:
• RFC 1242, Benchmarking Terminology for Network Interconnection Devices, edited
by Scott Bradner (sob@harvard.edu)
• An informational document, Benchmarking Methodology for Network Interconnect
Devices, edited by Scott Bradner
• RFC 2544, Benchmarking Methodology for Network Interconnect Devices, edited by
Scott Bradner and Jim McQuaid (mcquaidj@netscout.com)
RFC 1242 and RFC 2544 outline the following tests for network devices:
• Throughput
• Latency
• Frame Loss Rate
• Back-to-Back
These tests are implemented in SmartApplications.
RFC 1242 also contains a complete definition of the terms for which the tests are named.
RFC 2544 describes how to measure and test performance, including specific formats in
which to report test results and maximum frame rates to use with specific frame sizes.
RFC 1242 and RFC 2544 are available at www.ietf.org
The informational document is available at the NDTL ftp site: ndtl.harvard.edu
.
.
6 SmartApplications User Guide
Chapter 1: SmartApplications Overview
What are SmartCards and Modules?
SmartCards and modules are custom-designed printed circuit boards (PCBs) that fit within
a SmartBits chassis to generate, capture, and analyze network packet data.
SmartBits systems use two types of cards and modules, depending on chassis type.
SmartCards are designed to fit into the SMB-2000 and SMB-200 chassis.
Modules are designed to fit into the SMB-6000B and SMB-600 chassis. They provide a
higher port density than do SmartCards.
For simplicity, the term card is sometimes used to refer to any SmartCard or module in a
SmartBits system.
Supported Cards and Modules
SmartApplications 2.50 may be used with the follow SmartCards and modules.
Table 1-1. Supported SmartCards and Modules
What are SmartCards and Modules?
Chassis Network Topology SmartCard or Module
SMB-6000 10/100Mb Ethernet LAN-6100A 100Mb Ethernet TP
LAN-6101A 10/100Base-TX SmartMetrics
Gigabit Ethernet LAN-6200A(s) 1000Base-SX
LAN-6201A(s) 1000Base-SX SmartMetrics
LAN-6201B 1000Base-X GBIC SmartMetrics
SMB-600/6000B 10/100Mb Ethernet LAN-3100A 10/100Base-TX SmartMetrics
LAN-3101A 10/100Base-TX TeraMetrics
LAN-3102A 10/100Base-TX SmartMetrics
LAN-3111A 100Base-FX SmartMetrics
LAN-3302A 10/100Base-T TeraMetrics
10/100/1000Mb Ethernet
and
Gigabit Ethernet
LAN-3200A(s) 1000Base-SX
LAN-3201As 1000Base-SX SmartMetrics
LAN-3201B 1000Base-X GBIC SmartMetrics
LAN-3300A 10/100/1000Base-T SmartMetrics
SmartApplications User Guide 7
Chapter 1: SmartApplications Overview
Supported Cards and Modules
Table 1-1. Supported SmartCards and Modules (continued)
Chassis Network Topology SmartCard or Module
SMB-600/6000B
(continued)
10/100/1000Mb Ethernet
and
Gigabit Ethernet
(continued)
LAN-3301A 10/100/1000Base-T TeraMetrics
LAN-3310A 1000Base-X GBIC SmartMetrics
LAN-3311A 1000Base-X GBIC TeraMetrics
SMB-200/2000 ATM AT-9015 1.544Mb T1
AT-9020 2.048Mb E1
AT-9025 25Mb
AT-9034(B) 34Mb E3
AT-9045B 45Mb DS3
AT-9155(C)(Cs) 155Mb
AT-9622(s) 622Mb
Gigabit Ethernet GX-1405B(s) 1Gb Ethernet Fiber
GX-1420A 1Gb Copper Ethernet TP
GX-1420B 100Mb/1Gb Copper Ethernet TP
10Mb Ethernet ML-5710 100Mb SmartMetrics Ethernet and USB
(only Ethernet mode is supported)
100Mb Ethernet ML-7710 100Mb SmartMetrics VLAN Ethernet TP
Token Ring TR-8405 4/16 Token Ring
WAN WN-3405 8Mb V.35 Frame Relay
8 SmartApplications User Guide
ST-6410 10Mb Full Duplex Ethernet TP
ML-7711 100Mb SmartMetrics VLAN Ethernet Fiber
SX-7210 100Mb Ethernet VLAN MII
SX-7410B 100Mb Ethernet VLAN TP
SX-7411 100Mb Ethernet VLAN Fiber
WN-3415 1.544Mb T1 Frame Relay
WN-3420A 2.048Mb E1 Frame Relay
2
Basic Test Theory
In this Chapter...
This chapter contains the following sections:
• General Testing Methodology.....10
• Throughput Test Methodology.....12
• Latency Test Methodology.....14
• Packet Loss Rate Test Methodology.....16
• Back-to-Back Test Methodology.....17
SmartApplications User Guide 9
Chapter 2: Basic Test Theory
General Testing Methodology
General Testing Methodology
Each SmartApplications test has two features in common:
• Each test measures device forwarding capabilities, and
• Each requires a pair of SmartBits SmartCards to test frame forwarding: one card is the
transmitter, the other is the receiver.
Before testing a device you must:
1 Identify the number of the ports you want to test.
2 Ensure that each port to be tested has a unique MAC address.
You can chose multiple packet sizes and test durations, as specified in the RFC.
SmartApplications logs test results into individual standard ASCII files that you can view
or print with standard utilities.
Test Terminology
Te st The term test refers to the test type, such as Throughput or Latency, run for a specific
frame size.
Iteration An iteration occurs when SmartApplications varies the transmission rate, based on the last
failed rate, while maintaining the frame size. The specified test resolution and number of
repetitions determines the accuracy of results.
Trial A trial is a set of iterations for a specific frame size, with varying transmission rates.
Within a test, trials are used to determine the optimal rate of traffic for that frame size. It is
possible to have multiple trials for one frame size. Detailed results display multiple trial
results. You specify the number of trials in the Setup Test Configuration window.
Figure 2-1 illustrates these terms.
Sample Test Configuration
Figure 2-1. Trial and Iterations for a Sample Test Configuration
10 SmartApplications User Guide
Address Learning for SmartCards
SmartApplications assumes that the device under test (DUT) has no knowledge of any
forwarding or routing required. To initialize the DUT’s forwarding tables, the SmartBits
sends learning packets.
You can also instruct the SmartBits to send learning packets between every test trial, to
refresh a device forwarding table before addresses are eliminated by aging.
Table 2-1 shows the makeup of the learning packets that are sent.
Table 2-1. Learning Packet Contents
Packet Area Size (Bytes) How Used
Destination 6 MAC address.
Source 6 MAC address.
Protocol Variable Matching user selection of IP, UDP, IPX, or 32 bytes of
Chapter 2: Basic Test Theory
General Testing Methodology
All zeros or All 0xFF.
Test Specific 12 Packet Loss and Back-to-Back
SixbytesoftheSmartBitsstampinanASCIIstring
(NETCOM), and six bytes of the destination address.
Throughput
A six-byte incrementing counter with six bytes of
destination MAC address.
Latency
A six-byte decrementing counter with six bytes of
destination MAC address.
Rest of Packet n Length varies, depending on the fill pattern for the
selected protocol type.
CRC 4 Error detection.
SmartApplications User Guide 11
Chapter 2: Basic Test Theory
Throughput Test Methodology
Throughput Test Methodology
The Throughput test tests the fastest rate at which a device can forward frames without
error. If a single frame is dropped, the test fails and is repeated at a lower throughput rate.
The throughput test satisfies the terminology criteria of RFC 1242 and the test
methodology specified in RFC 2544. From RFC 1242, throughput is:
“the maximum rate at which none of the offered frames are dropped by the device.”
From RFC 2544, the methodology to measure throughput is to:
“send a specific number of frames at a specific rate through the DUT and then count
the frames that are transmitted by the DUT.”
SmartApplications measures throughput by first sending a series of frames with a
particular source and destination MAC address to the device under test. The frames are
sent from one SmartBits port and are intended to be received by a second SmartBits port.
Interframe Gap InterFrame Gap is determined by the initial rate in the test setup. If the initial rate is set to
100%, frames are sent initially with the gap set to the minimum legal size for the topology
and speed of the transmitting SmartCard.
How frames are
sent and counted
The number of frames sent is determined by the length of time the test is to run. Frames
are validated by counting only frames generated by the sending port, not any packets sent
by the switch. Keep-alive and routing update frames are not counted as received frames.
Initial frame rate If the initial rate is 100%, the frame rate for the first trial, for a given frame length, is the
maximum rate for the topology and speed of the transmitting SmartCard.
Test progress 1 If all frames from the transmitting SmartBits port are received by the receiving port,
no further trials are attempted and the maximum frame rate is recorded as the throughput.
2 If the first trial fails (if even a single frame is lost), the second trial frame rate drops to
20% lower than the failed rate.
3 The third trial and each subsequent trial uses a binary search to determine a rate that is
halfway between the last failed rate and the last successful rate.
4 The test finishes when the frame loss percent is less than or equal to the resolution
1
value in the test setup (depending on the interframe gap resolution of the card
Test results Test results are automatically logged to a file showing maximum data rate by port pair and
).
aggregate frame data rate. Also logged is the percentage achieved of maximum theoretical
frame data rate for each selected frame size.
This test is performed for a user-specified number of times and the results are averaged.
1. Refer to the SmartBits System Reference manual for information on the gap resolution of specific
cards and modules.
12 SmartApplications User Guide
Acceptable Loss Throughput
In some cases, differences in clock tolerances between the DUT port and the SmartBits
port will cause Throughput test results to show frame loss. This frame loss does not reflect
the capability of the switch or router, but rather is the result of these clocking variances.
To compensate for this, you can run a SmartApplications Throughput test in a mode
termed Acceptable Loss Throughput. When this mode is selected, you specify what
percentage of frame loss is to be discounted when evaluating the test’s success or failure.
If you enable Acceptable Loss Throughput (by setting a loss value), the SmartApplications
main window changes to show the alternate test mode (Figure 2-2). The Throughput Test
Results window and Test Report also include information on the acceptable loss
performance.
See “Set Up Test Configurations” on page 48 for details on setting values.
Throughput with Acceptable Loss enabled
Chapter 2: Basic Test Theory
Throughput Test Methodology
Figure 2-2. Throughput Test with Acceptable Loss
SmartApplications User Guide 13
Chapter 2: Basic Test Theory
Latency Test Methodology
Latency Test Methodology
The Latency test measures latency as defined in RFC 1242, as described below for both
store-and-forward devices and bit-forwarding devices.
How SmartApps
calculates latency
Cut-through
(bit-forwarding)
latency
calculation
Store and
forward latency
calculation
The sending SmartCard sends a burst of frames at a user-specified frame size through the
DUT at a user-specified throughput rate. In the middle of the burst stream, it inserts one
frame with an identifying trigger (tag). The time when the trigger frame is fully
transmitted is the Transmit Timestamp. The time the receiving SmartCard recognizes the
trigger frame is the Receive Timestamp. SmartApplications calculates latency as:
(Receive Timestamp) minus (Transmit Timestamp) = Latency
Specifically, SmartApplications first measures the cut-through rate and then calculates the
store and forward rate with this calculation:
(Cut-through Rate) minus (Frame Bit Time) = Store and Forward Rate
The Latency test is performed at a user-specified frame rate.
For cut-through device measurements, SmartApplications calculates latency as FIFO (first
in-first out), meaning that it calculates the difference between the time that the end of the
first bit of a transmitted frame reaches the DUT’s input port (Transmit Timestamp) and
the time the first bit of the same frame is seen on the DUT's output port (Receive
Timestamp).
If NA (“Not Applicable”) appears in either of the columns labeled S&F (Store &
Fo rw ar d)inthetestResults window, this is because the S&F calculation is zero or less,
indicating that the DUT is a cut-through device.
For store and forward device measurements, SmartApplications calculates latency as
LIFO (last in-first out), meaning it calculates the difference between the time that the end
of the last bit of a transmitted frame reaches the DUT’s input port (Transmit Timestamp)
and the time that the end of the first bit of the same frame leaves the DUT’s output port
(Receive Timestamp).
Note:
1) It is recommended that you run the Throughput test before you run the Latency test in
order to obtain the optimum throughput rate of the DUT. Then use the throughput rate
obtained from the Throughput test for the Max Rate in the Latency test. Using a proven
optimum rate prevents the tagged frame from being lost due to performance rate issues. If
the tagged frame is not received, you may see a very large number for the RcvByte field of
the Log file.
2) SmartApplications always measures latency and yields results for both store and
forward devices and bit-forwarding (cut-through) devices regardless of the DUT. When
viewing results, use the result that is appropriate for your type of device.
14 SmartApplications User Guide
Chapter 2: Basic Test Theory
Latency Test Methodology
SmartMetrics
Compensation
Mode
This mode enables SmartApplications to render the same latency results as would be
produced by other SmartBits applications (such as SmartWindow) in SmartMetrics mode,
when the transmitter and receiver are running at different speeds.
With the option is disabled, the Latency test runs as usual, with the trigger pattern at the
usual offset in the frame. In this case, however, if the transmitter and receiver are running
at different speeds, the latency result will be different from what it would be in a
SmartMetrics test run through (for example) SmartWindow.
In contrast, when this option is enabled, the trigger pattern is offset to the same position in
the frame where the Signature field would be placed in a SmartMetrics test. As a result,
SmartApplications can produce the same latency result as a SmartMetrics application.
The SmartMetrics Compensation mode makes it possible to maintain continuity with past
results, when this is desired.
You can enable SmartMetrics Compensation Mode by selecting Setup > Test
Configuration from the main menu, the opening the Latency tabontheSetup Test
Configuration window.
Limits on Latency
Te st in g
Use the
when you wish to make test results from
SmartApplications compatible with results
from SmartMetrics tests run using other
SmartBits applications, such as SmartWindow
or SmartFlow, when the transmitter and
receiver are running at different speeds.
SmartMetrics Compensation Mode
The following limitation applies to latency tests using 10/100Mb cards in the SMB-200 or
SMB-2000. With these cards and chassis, the latency test duration is limited to 112
seconds when the packet size is 64 bytes and you are testing at 100% rate in the 100Mb
mode.
SmartApplications User Guide 15
Chapter 2: Basic Test Theory
Packet Loss Rate Test Methodology
Packet Loss Rate Test Methodology
This test measures the percentage of frames lost by the DUT that should have been
forwarded, based on the total number of packets sent.
The Frame Loss Rate test satisfies the terminology criteria of RFC 1242 and the test
methodology specified in RFC 2544. From RFC 1242, Frame Loss Rate is:
“percentage of frames that should have been forwarded by a network device under
steady state (constant) load that were not forwarded due to a lack of resources.”
The test allows for varying frame sizes from 64 bytes to 1518 bytes for Ethernet ports, and
up to 8188 for Token Ring ports.
From RFC 2544, the methodology to measure frame loss is to:
“Send a specific number of frames at a specific rate through the DUT to be tested and
count the frames that are transmitted by the DUT.”
How frames are
counted
How the test runs The Frame Loss Rate test operates in essentially the same manner as the Throughput test.
Frames are validated by counting only frames generated by the sending port, not any
packets sent by the switch. Keep-alive and routing update frames are not counted as
received frames.
1 First a packet burst is performed at the maximum possible rate for a user-specified
period of time.
2 After all packets are sent, the receiving port is queried to determine how many packets
were received.
3 The number of packets not received is determined and the percentage of loss is calcu-
lated, based on the total number of packets sent.
Note: For Many-to-1/1-to-Many test configurations between ATM and Ethernet or ATM
and Frame Relay: If the DUT bundles multiple streams into one virtual circuit,
SmartApplications counters reflect the number of packets received on a per virtual circuit
basis (not per stream).
This test is performed a user-specified number of times and the results averaged.
16 SmartApplications User Guide
Back-to-Back Test Methodology
Back-to-Back tests the buffering capability of the device under test.
The Back-to-Back test satisfies the terminology criteria of RFC 1242 and the test
methodology specified in RFC 2544. From RFC 1242, the Back-to-Back test is performed
by:
“fixed length frames presented at a rate such that there is the minimum legal separation (maximum rate) for a given medium between frames over a sort to medium period
of time, starting from an idle state.”
The test allows for varying frame sizes from 64 bytes to 1518 bytes for Ethernet ports, and
8188 bytes for Token Ring ports.
From RFC 2544, the methodology to measure back-to-back frames is to:
“Send a burst of frames with minimum inter-frame gaps to the DUT and count the
number of frames forwarded by the DUT.”
Chapter 2: Basic Test Theory
Back-to-Back Test Methodology
How frames are
counted
How the test runs The Back-to-Back test operates in essentially the same manner as the Throughput test.
Frames are validated by counting only frames generated by the sending port, not any
packets sent by the switch. Keep-alive and routing update frames are not counted as
received frames.
1 First a packet burst is performed for a user-specified period.
2 If all packets are received at the receiving port, the test is successful and testing is
stopped.
3 If even one packet is lost, the number of packets sent in the burst is halved and retried.
4 If all packets are successfully received at this point, the packet burst is then chosen
halfway between the successful and unsuccessful trials, and retried.
5 This pattern repeats until the actual number of packets that can be forwarded in a burst
is determined.
This test is performed a user-specified number of times and the results are averaged.
SmartApplications User Guide 17
18 SmartApplications User Guide
3
Install and Connect
In this Chapter...
This chapter contains the following sections:
• Install SmartApplications.....20
• Launch SmartApplications.....21
SmartApplications User Guide 19
Chapter 3: Install and Connect
Install SmartApplications
Install
SmartApplications
It is assumed that you are familiar with Microsoft Windows and basic SmartBits
operation.
System Requirements
To ru n SmartApplications 2.50, you must have the following:
Hardware
• SMB-200
SMB-2000
SMB-600
SMB-6000B (formerly SMB-6000)
• At least two SmartCards or modules.
• IBM PC or 100% compatible.
• Pentium 200 or above.
• VGA video or better (recommended).
• 16 MB of RAM for Windows 95 / 98
—or—
32 MB of RAM for Windows NT.
• 10MBfreeharddiskspace.
Software
• Windows 95, Windows 98 or Windows NT 4.0 (see “Operating System
Requirements” below for detailed requirements).
• SmartBits Firmware 10.10 or higher.
• SmartApplications software.
Operating System Requirements
Operating System Version / Updates Required RAM (Mbytes)
Windows 95 B and C with current Service Packs
and library updates.
Windows 98 First and Second Edition. 32
Windows NT 4.0 Service Pack 6A. 64
Windows 2000 Professional Edition. 64
32
20 SmartApplications User Guide
Installing from the CD
SmartApplications is provided on one CD-ROM disk. To install the program, refer to the
instructions on the CD case.
Chapter 3: Install and Connect
Launch SmartApplications
Launch
Installation Using
AutoPlay (if enabled) will automatically begin the installation process.
1 Insert the SmartApplications installation CD in the CD-ROM drive. The Install Shield
window is displayed.
2 Select Install SmartApplications [Ver#].
3 Follow the instructions until all SmartBits software is installed.
If
AutoPlay
If AutoPlay is disabled or your PC does not support an automatic installation process, you
can use the following alternative procedure.
1 From the Start Menu, select Run.
2 When the Run dialog box appears, type:
<cd-rom drive>:\SETUP
—in the Command Line, then click OK.
3 Follow the instructions displayed as the installation program installs the software.
is Not Enabled
AutoPlay
SmartApplications
From the Start menu, select Programs > SmartBits Applications > SmartApplications.
The SmartApplications main window displays.
How to Close
To c los e SmartApplications, click the Close button at the top right corner of the screen.
or
Select File > Exit from the menu bar.
SmartApplications
SmartApplications User Guide 21
22 SmartApplications User Guide
4
Basic Navigation and Tools
In this Chapter
This chapter contains the following sections:
• Features of the Main Window.....24
• Charting Test Results.....33
SmartApplications User Guide 23
Chapter 4: Basic Navigation and Tools
s
Features of the Main Window
Features of the Main Window
SmartApplications provides a dynamic main window that changes according to the
selections you make—for example, selecting a 1-to-Many or 1-to-1 test type.
Figure 4-1 highlights the key elements.
Menu Bar
To ol B ar
Test Launch
buttons
Port Selection
area
Figure 4-1. Main Window Elements
Connection Status
A connection status indicator (bottom right of main window) and the status message
Connected shows when SmartApplications is connected to the SmartBits. When
disconnected, the light is grey and the message Disconnected displays.
24 SmartApplications User Guide
Card Attribute
area
Connection
status
Loading...