SierraNet M408 User Manual Download

Transcript
InFusion Scenarios
4.6.13
TeledyneLeCroy
Scenario Libraries
Libraries are repositories that hold Scenarios. This section describes the ways that you can manipulate Scenarios within Libraries.
Scenario Library Item Multi-Selection
The Scenario Library lists support conventional multi‐selection via mouse‐clicks and keyboard modifiers. The Copy Scenario item from the right‐click context menu will operate on all selected items:


Hold down the Ctrl key on the keyboard and click on items to toggle their selec‐
tion state.
Select a first item, then hold down the Shift key and select a second item; all items from the first item to the second item will be selected.
Global and Project Libraries
The scenarios saved in the Global Library are available to reuse for all projects. The scenarios saved in the Project Library are only available for the current project. You may transfer Scenarios between these libraries by drag‐n‐drop or copy/paste.
Adding Scenarios from Global to Project can only work if the protocol is similar, else it will be greyed out and unselectable. Import/Export of Scenarios
Users can export a scenario (or multiple scenarios) to a file. Export is available via right click pop up menu. Scenarios can then be archived on your host machine’s hard drive.
There are two ways to import a library, if the user wants to import file into a existing library, they have to right click on the existing library and select import library. If the user wants to make a new library, there is an icon to import a library in library pane toolbar.
4.6.14
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 example, 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).
SierraNet M408 Protocol Analyzer User Manual
199