Automation of the Xena tester

Xena,xena Networks Company's network tester, can also cover the Ethernet L2~L7 layer tester, but the function is simple, the interface is very concise, use it more intuitive and convenient.

Automated test scenarios for 1.Xena

Test the at frame on the PC-->TCL Drive Library SIG_TEQ_XENA.TCL-----(Ethernet cable)----->xena Chassis

PC on the Xena not install the client Xenamanager can. Xena's chassis internal command is not a TCL-formatted command, but a Xena script that Xena its own support;

Tcl driver only with Xena chassis set up 1 socket session to send Xena script command to chassis, And gets the return value. So the test PC can not install Xena desktop client Xenamanager, but it is best to load it, easy to see the script execution effect immediately.

After installing Xenamanager, its installation directory will have 1 Xenascriptclient_20.exe, this should be used to manually issued Xena script command to chassis, no use.

Because the Xena chassis internal command is the unique format of the Xena Script command, the SIG_TEQ_XENA.TCL file does not require "package require XXX" to load what Xena dedicated library

Architectural Hierarchy of 2.Xena

Xena the agent used to receive the command should be inside the meter chassis, but the desktop client also provides 1 simple script run boxes that can be executed in Windows under the command

Because Xena chassis receives the command of its own format, the packaging language used can be arbitrary, such as: Tcl,rerl,python,java,excel/vba ... Just set up 1 TCP/IP connections with chassis, send command to Xena hardware and receive return line. The client software is not required to be installed.

When a socket is established between the test PC and the Xena chassis, 22611 is the scripting port specified by Xena-chassis.

Issued to Chassis of the Command is case- insensitive , but Chassis The returned contents are in uppercase.

The Xena level of instrumentation management from the client application is:

testbed--->chassis--->module--->port

1. Testbed is the logic of the management software, you can manually add multiple.

2.1 chassis corresponds to 1 IP, 1 physical chassis, from this level is the automation to consider. Generally 1 chassis only 1 module 0, 1 module with multiple ports below.

API format for 3.Xena

Chassis command handles the basic information and configuration of the chassis itself, rather than the overall control of its module modules or port test ports for scripting sessions. The return value of a command is typically a list format that contains multiple elements.

Some command commands have both set and get functions at the end of the add "? "Is get.

Xena the general format of the internal command, the command prefix is different, mainly divided into the following categories:

(1) Some parameter setting and reading of "C_" chassis chassis
(2) "m_" module (equivalent to the card level in Ixia, Xena without pluggable cards) Some parameter setting and reading
(3) Some parameters of "P_" Port are set and read
(4) Some parameters of "Ps_" stream are set and read

After Xena's internal command is issued, the chassis return value and its meaning:

<OK> issued to chassis and executed successfully

<NOTLOGGEDON> did not use C_logon + correct chassis password login chassis beforehand

<NOTRESERVED> not issued a x_reservation for the resources you want to change?

<NOTWRITABLE> This parameter is read-only and cannot be written

<NOTREADABLE> This parameter is write-only and cannot be read

<NOTVALID> This operation is invalid in the current chassis state and cannot be performed, such as changing the port configuration parameters that are streaming

<BADMODULE> the index value parameter of the provided module is out of bounds

<BADPORT> the index value parameter of the supplied port is out of bounds

The sub-index value of the <BADINDEX> parameter "sub-index" is incorrect

<BADSIZE> the value of the data provided is inappropriate, beyond reasonable scope

The data value provided by <BADVALUE> is incorrect

<FAILED> failed to produce results

Features of 4.Xena at

Xena configuration Traffic Header (Ethernetii,mpls,vlan,ip all belong to the message header, the following is the specific message content)

1. Gets or modifies the specific parameter value of the field block previously added, typically converted to 16 binary or 2 binary number processing
2. Xena is special, it can not directly set the field value as Ixia,spirenttestcenter, but in accordance with the bytes in the report text segment directly change the value of 16 or 2 bytes, after the set up directly as a whole issued. This makes the Xena drive library programming cumbersome, but there is a benefit in the coding process, to help you review the various protocol message construction, the order of each field, the location, each byte represents what meaning and so on. After writing this library, the harvest is still very large.

This article is simply an introduction to the Xena Automation principle, and the detailed Xena API can be found in the specific API official documentation.

Automation of the Xena tester