Spirent TestCenter Command Sequencer V3

Spirent TestCenter
Command Sequencer
www.spirentcampus.com
NoCodeTM Automation
To quickly and easily automate tests, Spirent TestCenter
provides NoCodeTM Automation.
Regression testing (different product releases)
Multiple hardware platform testing
Multiple parameter testing such as varying the number of active

sessions, frame size, QoS settings, etc.
Multiple protocol testing
NoCodeTM Automation includes:

Command Sequencer
GUI to Script
2
Spirent TestCenter Command Sequencer
Accelerate Test Case Development
Design Test
Designing and creating New
Code Test
Test Cases typically requires a
Configure DUT
substantial commitment from
an organization.
Download Test
Spirent TestCenter’s NoCodeTM
Collect Results Automation accelerates the
Test Case Development Cycle.
Present Results
Interpret Results
No
Correct?
Yes
3
Command Sequencer Overview
The Command Sequencer is a Complete Visual
Programming Environment that:
Allows customized testing.
Allows automatic “Batch-mode” testing.
Allows the introduction of “real world” events into a test.
Emulate link failures, route flapping, router failures, etc.
Allows you to build a complex series of events in order to truly stress

a router or switch
• Run continuously over a weekend.
• Ideal way to locate subtle problems such as small memory leaks.
Allows you to insert External Events – “White Box Testing”.

4
Command Sequencer Control
User can build and execute a sequence of interactive steps
(commands).
Flexible - Insert, change, delete, move command steps.
Control structure commands:
Loop commands for iteration control
Pass/Fail result status implemented for specific Verify commands
Conditional Processing commands (Branching), includes Pass/Fail
on Test Results.
Group commands together.
Integrate with Test Management frameworks (Stop Sequencer)
Provides access to unlimited customization (Custom Tools)

5
Accessing the Command Sequencer
6
Creating a Command Sequence
There are two ways to create a custom sequence.

1. Manually within the Command Sequencer.
2. Using various Test Wizards.
7
Command Sequence and Test Config.
Command Sequencer contains Commands only.
You must have a test configuration that you wish to act upon.
8
Creating a Sequence Manually
Select the Edit Sequence button.
9
Command Sequencer – Groups
Choose to view all, or specific command groups.
10
Command Groups
Narrow down commands by groups.
11
Command Sequencer – Commands
Read the command description.
12
Adding Commands
Highlight command
Select ADD button, double click or drag and drop the
command.
13
Editing Commands
Double click, or right click > Edit Command… to edit the

command.
14
Modifying Parameters
Name your command
Modify the parameters
15
Inserting Commands – Drag and Drop
Left click on the command and drag to point arrow below

command you want it to follow.
16
Re-ordering Commands
There are two ways to move a command:

Select the MOVE UP or MOVE DOWN button.
Use the left mouse button to drag and drop.
17
Saving the Sequence
When finished adding / editing the commands, select OK to

save them.
18
Edit Stop Routine
You can also move Stop
commands into the Stop Routine.
Stop Commands are always
performed even if the sequence is
aborted.
19
Starting the Test Sequence
Step through commands.

Run all at once.
20
Following the Test Sequence
Watch each command step in lower left of browser.
21
Stop or Pause the Test Sequence
Pause the test. Stop the test.

Break the loop running.
22
Event Results
Create a Chart in the Results Browser to track incremental results
Events are annotated with the assigned name and any comments
Width of the flap indication line depicts the amount of time that it
took to implement that event
23
Creating a Sequence Using the
Custom Test Wizard
Go to Wizards… > Configuration Wizards > Sequence
Generator > Custom Test.
24
Custom Test – Parameters
Set test type
Set load
Set frame size
25
Timed Test Parameters
Set the time or bursts
Use the port or

stream settings
or specify a fixed or
random value for load
units and/or frame
size.
26
Stepped Test Parameters
Step the load
Step the frame size
27
Throughput Test Parameters
Set the load
Set the frame size
28
Set Test Options
29
Enable Preview
To view the commands select Enable Preview.
30
Creating a Sequence using
Test Wizards
Creates the Traffic and associated

Command Sequence all in one
31
RFC 2544 Command Sequence
32
BreakPoints
33
Creating a Sequencer Loop
34
Specifying Loop Options (Fixed)
35
Specifying Loop Options (Continuous)
36
Iteration Commands
37
Verify Status Commands
Use Verify Status Commands to

display Pass/Fail Status of that
Command.
38
Verify ArpND Command
For this example we did not

Start ARP within Command
Sequencer.
Verify Arp Status Command
displays Red LED indicating
that ARPs did not Resolve.
39
Verify Link Command
Verify Link Status Command

displays Red LED indicating
that Physical Link is not up.
40
Verify Results Command
Verifies Traffic was sent.

41
Conditional Processing Commands
Conditional Processing commands allow branching decisions
based on command status.
Decision
42
Conditional Command Usage
43
Conditional Command Usage Continued
44
If Else Example
45
Conditional Command Warning
46
Stop Command Sequencer
The Stop Command Sequencer command will exit the
sequencer and return a user defined message.
Very useful in conjunction with branching commands.
47
Branching Results w/Stop Sequencer
48
Goto Command
49
Running an External Process
The Run External Process command allows access to
external scripts and processes.
Command Sequence
tclsh84 config.tcl
Script to
Configure DUT
SPT-5000A
SPT-5000A
er
w
Po
er
w et
Po es
R
et
es p
R m
Te
p n
m Fa
Te
nk
n Li
Fa us
at
St
nk w
er
Li
us Po
at
St
er
CAUTION
Pow STATICSENSITIVE
CAUTION
STATICSENSITIVE
Spirent TestCenter Spirent TestCenter

50
Run External Process Command
51
Configuring Run External Command
52
Run External Process Example
53
Run Custom Command
The Run Custom Command extends the Command

Sequencer by allowing Spirent provided extensions for
custom configuration, control, or analysis.
Requires advanced customization tools.
Provides endless flexibility for commands not included within
the Command Sequencer.
Not a typical user function.
54
Custom Tool Example
Custom software
55
Calling Custom Script
56
Passing Parameters to the Script
When you execute the Global Services: Run Custom
Command you can pass it parameters:
TCL script accesses the parameters using the stc::scriptParameters
array variable
Sample parameter argument list:
• -MinTol 5 –MaxTol 25 –Step 3
57
GUI to API for the Command Sequencer
58
Spirent TestCenter API Commands
A script can use Spirent TestCenter 2.X API commands
within or without the Command Sequencer.
Spirent TestCenter 2.X API Commands are called differently

for scripts that use the Command Sequencer and for scripts
that do not use the Command Sequencer.
AnalyzerStart without the Command Sequencer and
AnalyzerStartCommand within the Command Sequencer.
GeneratorStart without the Command Sequencer and

GeneratorStartCommand within the Command Sequencer.
See Command Object Index of the Object Reference for all API
commands.
59
Command Sequencer API Commands
60
End of Topic
www.spirentcampus.com
61

Spirent TestCenter Command Sequencer V3

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Spirent TestCenter Command Sequencer V3

Hochgeladen von

Copyright:

Verfügbare Formate

Spirent TestCenter

 Multiple hardware platform testing

 Multiple parameter testing such as varying the number of active

 Multiple protocol testing

 NoCodeTM Automation includes:

 Allows automatic “Batch-mode” testing.

 Allows the introduction of “real world” events into a test.

 Emulate link failures, route flapping, router failures, etc.

 Allows you to build a complex series of events in order to truly stress

• Ideal way to locate subtle problems such as small memory leaks.

 Allows you to insert External Events – “White Box Testing”.

 Provides access to unlimited customization (Custom Tools)

 There are two ways to create a custom sequence.

 Select the Edit Sequence button.

 Choose to view all, or specific command groups.

 Narrow down commands by groups.

 Read the command description.

 Double click, or right click > Edit Command… to edit the

Name your command

Modify the parameters

 Left click on the command and drag to point arrow below

 There are two ways to move a command:

 When finished adding / editing the commands, select OK to

 Step through commands.

 Watch each command step in lower left of browser.

Pause the test. Stop the test.

Set test type

Set frame size

Set the time or bursts

Use the port or

Set the time or bursts

Step the load

Step the frame size

Set the time or bursts

Set the load

Set the frame size

 To view the commands select Enable Preview.

Creates the Traffic and associated

 Use Verify Status Commands to

 For this example we did not

 Verify Link Status Command

 Verifies Traffic was sent.

Spirent TestCenter Spirent TestCenter

 The Run Custom Command extends the Command

 Spirent TestCenter 2.X API Commands are called differently

 GeneratorStart without the Command Sequencer and

Das könnte Ihnen auch gefallen

Multiple hardware platform testing

Multiple parameter testing such as varying the number of active

Multiple protocol testing

NoCodeTM Automation includes:

Allows automatic “Batch-mode” testing.

Allows the introduction of “real world” events into a test.

Emulate link failures, route flapping, router failures, etc.

Allows you to build a complex series of events in order to truly stress

Allows you to insert External Events – “White Box Testing”.

Provides access to unlimited customization (Custom Tools)

There are two ways to create a custom sequence.

Select the Edit Sequence button.

Choose to view all, or specific command groups.

Narrow down commands by groups.

Read the command description.

Double click, or right click > Edit Command… to edit the

Left click on the command and drag to point arrow below

There are two ways to move a command:

When finished adding / editing the commands, select OK to

Step through commands.

Watch each command step in lower left of browser.

To view the commands select Enable Preview.

Use Verify Status Commands to

For this example we did not

Verify Link Status Command

Verifies Traffic was sent.

The Run Custom Command extends the Command

Spirent TestCenter 2.X API Commands are called differently

GeneratorStart without the Command Sequencer and