Commit eec6615e authored by Maciej Lipinski's avatar Maciej Lipinski

Minor corrections to the document on running tests using xena

parent ee6e5f72
......@@ -21,12 +21,13 @@ The WR switch to test must be connected to the Xena-tester as follow :
\end{table}
\begin{note}
Be careful! Ports on Xena-tester are starting form 0 but from 1 in a WR switch.
Be careful! Ports on Xena-tester are numbered form 0, they are numbered 1 on a WR switch.
\end{note}
The other ports of the WR switch must be connected as described in the \hrefreleasetests document.
Connecting the WR switch to an other module or other ports of the Xena-tester will imply to change all test cases configurations. It is not recommended.
Connecting the WR switch to another module or other ports of the Xena-tester will require
changing all test cases configurations. It is not recommended.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\subsection{Software environment}
......@@ -34,8 +35,8 @@ Connecting the WR switch to an other module or other ports of the Xena-tester wi
%%%%%%
\subsubsection{Xena application}
To run these tests, the Xena application \textbf{XenaManager-2G} is used. This application is only running under Windows.
Usually, settings of \textbf{XenaManager-2G} are stored in 'Documents/Xena/XenaManager-2G' on your local disk. Copy at this location
To run these tests, the Xena application \textbf{XenaManager-2G} is used (version 1.43). This application runs only under Windows.
Usually, settings of \textbf{XenaManager-2G} are stored in 'Documents/Xena/XenaManager-2G' on your local disk. You should copy to this location
the file \href{\gitrepo/xena-tester/xena-tester-configs/xena.xmcfg}{xena.xmcfg} and the
full directory \href{\gitrepo/xena-tester/xena-tester-configs/testcases}{testcases}.
You are ready now to start the application \textbf{XenaManager-2G}.\\
......@@ -55,24 +56,24 @@ To run a test, the following steps must be followed :
\end{itemize}
You are ready to start testing. The rest of the procedure for testing will be explained in next chapters because
it depends on the test to realize.
it depends on the test to run.
%%%%%%
\subsubsection{WR switch configuration}
\label{chap:WR switch configuration}
Each test need a specific configuration of the WR switch as decribed in the \hrefreleasetests document.
Each test needs a specific configuration of the WR switch as described in the \hrefreleasetests document.
To simplify the execution of a test, all switch configurations are already prepared and a bash tool can be use to apply a configuration in the switch.\\
To use it, checkout first the git directory \href{\gitrepo/xena-tester/switch-configs}{switch-configs} on your local machine.\\
Run then the tool 'run.sh'. A menu will appear and invite you to select the configuration to be applied. \\
To use it, first checkout the git directory \href{\gitrepo/xena-tester/switch-configs}{switch-configs} on your local machine.\\
Then run the tool 'run.sh'. A menu will appear and invite you to select the configuration to be applied. \\
\includegraphics[width=17cm]{RunTest.eps}
Applying a switch configuration takes few seconds because a reboot is needed and in some configuration PPSi must be stopped.
The following message 'Type enter to continue' indicates that the configuration has been applied. \\
\includegraphics[width=17cm]{RunTestDone.eps}
Your switch is not ready yet. As few ports of the switch implements the 'Low Phase Drift Calibration', the calibration of the ports can take some time.
So, before to start a test, verify with the 'wr{\_}mon' tool that all ports are up (green color). \\
So, before starting a test, verify with the 'wr{\_}mon' tool that all ports are up (green color). \\
\includegraphics[width=17cm]{wrmon.eps}
You are now ready to run your test.
......@@ -88,13 +89,13 @@ TARGET="switch{\_}name" run.sh
\subsubsection{Data mining}
\label{chap:Data mining}
Some tests uses the 'Statistics Logging' facility in the \textbf{XenaManager-2G} application.
Some tests use the 'Statistics Logging' facility in the \textbf{XenaManager-2G} application.
This facility logs statistics in a file during the execution of a test using the '.csv' format.
At the end of a test, a log file can reach a size of a few MB. Analysing these data can be
very complex. \\
So log files must be purged to keep only interesting informations and add test configurations.
The large fils must be purged to keep only the interesting information and the test configurations must be added.
The bash script \href{\gitrepo/xena-tester/tools/logCleaner.sh}{logCleaner.sh} makes this job
and can be apply on all tests executing the following test pattern:
and can be applied for all tests executing the following test pattern:
\begin{table}[ht!]
\begin{tabular}{ l l l l}
......@@ -119,7 +120,7 @@ dataCollectionName=Forwarding performance: one-to-one ...
}
Before to execute the 'logCleaner.sh' script it is recommended to purge manually the log file from :
Before executing the 'logCleaner.sh' script it is recommended to purge manually the log file from :
\begin{itemize}
\item repeated lines at end of the log. \\
As the logging system cannot be controlled by the scheduler, it continue to log uninteresting data
......@@ -132,7 +133,7 @@ Before to execute the 'logCleaner.sh' script it is recommended to purge manually
For tests which are not following this pattern for testing, specific log cleaner scripts 'spLogCleaner.sh' are provided.
Once the `clean log` is available, generation of data for the test results document can be started.
A set of few bash script are available to generate these data :
A set of few bash script is available to generate these data:
\begin{itemize}
\item 'genData.sh': This script tool generates few files with the extenxion '.dat' containing various extracted
data from the clean log file.
......@@ -166,9 +167,9 @@ testReport
The current structure in the testReport directory is represented in the following figure:
\includegraphics[width=3cm]{tree.eps}
All log files acquired during tests must be copy in the data directory corresponding to the test number.
All scripts for cleaning log files, generating data , pictures and tables must be executed in these data directory.
All resulting data needed by the document will be pushed in the directoty above (corresponding to the test number).\\
All log files acquired during tests must be copied in the data directory corresponding to the test number.
All scripts for cleaning log files, generating data, pictures and tables must be executed in these data directory.
All resulting data needed by the document will be pushed in the directory above (corresponding to the test number).\\
In the directory corresponding to the switch version, just run 'make clean all' to generate the report in pdf format.
......
......@@ -14,7 +14,7 @@ facilities available in the \textbf{XenaManager-2G} application :
\item the 'Capture feature': capture received frames and allow to analyze the different layers in a frame.
\end{itemize}
The second tool that can be use is 'wrs{\_}pstats -t' which must be launched in the tested WR switch. It gives an
The second tool that can be used is 'wrs{\_}pstats -t' which must be launched in the tested WR switch. It gives an
overview of all received and transmitted frames on all ports. Compared to the \textbf{XenaManager-2G} application,
this tool gives a view of what's happening on the other switch ports (3-16).
......@@ -29,12 +29,12 @@ The scheduler is automatically loaded when you load a test case. \\
To start a test you have to :
\begin{itemize}
\item start first the `Statistics Logging`
\item start secondly the `Scheduler`.
\item first, start the `Statistics Logging`
\item second, start the `Scheduler`.
\end{itemize}
When the scheduler has finished is execution and stopped, you can then stop manually the `Statistics Logging`
When the scheduler has finished its execution and stopped, you can then stop manually the `Statistics Logging`
and copy the log file into the associated test data directory.
Do not forget to rename the log file to fit the name declared in the 'config.txt' file relative to the test.
\newline
......@@ -80,8 +80,8 @@ These scheduler configurations are generated from \href{\gitrepo/xena-tester/too
\end{tabular}
\end{table}
These bash scripts can be changed to modify patterns to play. Attention, that any modification
of the pattern in \textbf{sched\_fp\_incr\_fixed\_imb\_s1} configuration, will involve an adjustment of the
These bash scripts can be changed to modify patterns to play. Attention: any modification
of the pattern in \textbf{sched\_fp\_incr\_fixed\_imb\_s1} configuration will involve an adjustment of the
specific clean logger used to decrypt the data.
Regarding tests to execute, the following table gives an overview of all scheduler configuration used :
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment