Sifos Technologies PhyView PVA-3000, Reference Manual

Page: 131 / 134

PVA-3000 Reference Manual
December 2, 2019 Sifos Technologies Page
131
6.3.3. Mailbox File Method
PowerShell PSA can be operated in a mode where it will poll the file system, checking for the existence of the file
psa_command.txt , and will execute the commands contained within that file when it is detected.
The command file is created on-the-fly by the external controlling environment. The file contains a series of one or
more valid PowerShell PSA commands that are executed in the order they are listed in the file, from top to bottom.
The PowerShell PSA execution environment communicates that it has completed execution by creating the file
psa_response.txt . This file does not contain any command result text – its sole purpose is to act as a handshake to the
caller.
The Mailbox File technique is substantially less robust than the Socket Interface method because there is no path by
which results developed as a consequence of PowerShell commands are automatically conveyed back to the external
application. This means that commands or scripts passed into PowerShell must have internal capability to retain those
results and feed them back, via data files or other means, to the external application.
The Mailbox File technique is useful in cases where very defined actions need to be performed, such as running a
standard test suite sequence, which by design will store the results to the disk. This technique is not recommended
where a varied set of commands needs to be executed, and where different results are required to make decisions.
The Mailbox File technique, including an example, is discussed in detail in the Sifos Technologies application note
PowerShell PSA - Remote Access Methods ( PowerShell PSA - Remote Access Methods.pdf ).
6.3.4. Batch Mode Methods
PowerShell Tcl (or Wish) consoles can be invoked from any environment where a batch file (Windows) or shell script
(Linux) can be executed. Furthermore, there are several methods by which a user-specified script can automatically
run once the PowerShell console opens. These methods are:
1. PSA Software Contrib Directory
23. Script Call from PowerShell Initialization File
24. PowerShell Launch Program Command Arguments ( Windows only )
A PowerShell PSA console is opened (or installed) in Windows using the PowerShell TCL.exe (or PowerShell
Wish.exe ) executable and in Linux with the PowerShell_TCL.sh or PowerShell_WISH.sh shell scripts. Batch mode
method #1 takes advantage of the fact that any *.tcl file located in the PSA Software Contrib directory will
automatically get sourced into PowerShell. Batch mode #2 involves editing the PowerShell Initialization File to
execute a user-specified command (or command sequence) when PowerShell opens. And Batch mode #3 capitalizes
on a feature of the Windows PowerShell launch executable where a script name file can be attached as an argument to
the PowerShell launch command thus causing that file to source into PowerShell when PowerShell opens.
The Batch Mode technique is generally less robust than the Socket Interface method because there is no path by which
results developed as a consequence of PowerShell script execution are automatically conveyed back to the external
application. This means that commands or scripts passed into PowerShell must have internal capability to retain those
results and feed them back, via data files or other means, to the external application. Batch mode #3 (Windows only)
does enable the remote application to specify an standard output channel to PowerShell such that all command results
could be routed to a user-specified data file.
The Batch Mode technique, including an example, is discussed in detail in the Sifos Technologies application note
PowerShell PSA - Remote Access Methods ( PowerShell PSA - Remote Access Methods.pdf ).
6.4. pva_veriphy Automated Test Application for the PhyView Analyzer
The PhyView Analyzer includes a fully automated 10/100/1000Base-T test application for performing rapid
evaluations of multiple Ethernet ports. This application is accessible from PowerShell PSA software.
pva_veriphy provides a moderate level of physical layer test coverage, testing from 1 to 6 10/100/1000Base-T ports in
as little as 80 seconds or less per port tested. Coverage includes link stability, transmission measurements, and
receiver performance assessment. Using
pva_veriphy , a 24 port 10/100/1000Base-T Ethernet switch can be
evaluated at the physical layer in as little as 30 minutes while a 24 port 10/100Base-T Ethernet switch will test in
approximately 12 minutes . pva_veriphy can be sequenced simply from PowerShell PSA to test Ethernet switches
and routers six ports at a time.