Teledyne LeCroy SierraNet M168 User Manual Ver.1.50 - Manual (Page 218)

Teledyne LeCroy InFusion Scenarios
216 SierraNet M168 Protocol Analyzer User Manual
Actions is Stop Scenario, the other Actions will NOT be carried out. To stop the Scenario
after the requested Actions have been carried out, you should branch to a new state
which stops the Scenario.
After defining the Event and Actions within the Global Rules panel, you can save the
Scenario and run it.
4.5.7 Sequences
The Global Rules are all you need for simple test Scenarios. However, a Scenario also can
contain one or two sequences, which can define multiple states and allow branching
between states. With a sequence, you also can do looping, which allows you to repeat a
test state or to execute a test for a specified period of time.
As with Global Rules, the menu‐driven interface guides you in building a sequence. Some
of the prompts are different, however, because you now are encapsulating groups of
Events and Actions as distinct states. Recall that a state is a combination of Events and
Actions at a specific point in time. If the Event or Combined Event defined by a state
occurs, the corresponding Action or set of Actions follows. You can enter multiple
Actions, which take place simultaneously. If one of the Actions is Stop Scenario, the other
Actions are carried out. To stop the Scenario after the requested Actions have been
carried out, you should branch to a new state which stops the Scenario.
InFusion hardware provides the capacity to have up to two sequences co‐existing in a
Scenario in addition to the Global Rules. Recall that both the Global Rules and any
sequences are active at all times. Each is a separate “state machine,” having the behavior
of a particular test state at any point in time. Because the Global Rules has the capacity
for only one state, you can view it as a “degenerative state machine.”
4.5.8 Scenario Libraries
You can create any number of Scenarios, which you then can archive on your host
machine’s hard drive. Libraries are windows that hold Scenarios.
4.5.9 Traffic Direction
The direction for traffic modification is defined on a global basis for the entire Scenario. In
other words, any Scenario Action that modifies line traffic only affects the traffic flowing
in the direction established at the top of the Scenario, in the Scenario Properties.
Scenario Events can be monitored in either direction, and therefore the parameters for
Events provide the ability to specify the intended direction for monitoring traffic for that
Event.
You identify direction of traffic change, or modification, in terms of traffic origin. The
application uses the following conventions:
 From P1/P3: Change is made to traffic coming from Port 1 or Port 3 (for exam‐
ple, CRC error is injected into traffic stream sent from P1/P3 to P2/P4).
 From P2/P4: Modification is made to traffic coming from the Port 2 or Port 4 (for
example, CRC error is injected into traffic stream sent from P2/P4 to P1/P3).