SUT Query Test Configuration


The following defines the SUT Query parameters of the SUT Query test case. These parameters define the query performed, when it is sent, response parsing.

Parameter Index

Test Options

Query Type

 

 

CPU Utilization

 

Network Test

 

Periodic Query

 

Measurements

 

Collect PCAP Files

Related Measurements


Periodic Query

Use the radio button to enable Periodic Query, and SUT Query will send the command that you provide to the SUT at a periodic interval and print the response in the Test Log.

Target Platform

Use the radio buttons to select the platform that will be queried:

Tcl Parameter: PeriodicQueryDestination

Command

The query sent to the Target Platform. The value must be the exact command string as it would be entered in a telnet session.

Tcl Parameter: PeriodicQueryString

Interval

The number of seconds before the first query is sent and the interval between queries.

Range: 5100

Default: 15

Tcl Parameter: PeriodicQueryRate

^ Back to Top


Query CPU Utilization

Use the radio button to enable Query CPU Utilization, and SUT Query will send the command that you provide to the SUT at a periodic interval, parse the response, and report the result on the Test Summary tab.

Command

A command string, valid for the SUT, that returns CPU usage. The value must be the exact command string as it would be entered in a telnet session.

Tcl Parameter: CpuQueryString

Response Search Pattern

The string that the parser should match and use as the initial starting point for the target token.

Tcl Parameter: CpuQuerySearchToken

Response Offset From Search Pattern

The location of the target token in relation to the Response Search Pattern. The value is the number of characters that the token is offset from the first character of the search pattern.

Range: N/A

Default: 0

Tcl Parameter: CpuQuerySearchOffset

Interval (s)

The number of seconds before the first query is sent and the interval between queries.

Range: 5100

Default: 15

Tcl Parameter: SutQueryTime

TIP: Some devices echo the Query CPU Command in the response to the command. If the Query CPU Response Search Pattern appears in both the command and the response, the first occurrence of the search pattern (the command echo) will be matched. In this case, the Query CPU Response Offset from Search Pattern should begin with the pattern in the command echo rather than the pattern in the response.

Related Measurements

The SUT CPU Utilization measurement is added to the Test Summary tab to report the results of the queries.

^ Back to Top


Network Test

Use the radio button to enable Network Test, add options to the arguments for the "traceroute" or "tracerouteToSut"  or "tracerouteToHost"  commands.

Select "traceroutetoHost" to perform a trace route to a Web Host Name (or FQDN) of the HTTP server that a URL is targeted for. A DNS Server IP is required to trace route to a Web Host Name.  The Measurements in the Trace Route Tab will be generated as well as a .csv file. These KPI's (Key Performance Indicators) per Host Name (or FQDN) will be provided to Spirent VisionWorks Analytics. See Customizing Report Options - VisionWorks Results and Intent of Test.  

Command

Select either "traceroute" or "tracerouteToSUT" (Must select a SUT on Network Devices Tab) or "tracerouteToHost".  

Tcl Parameter: NetworkTestCmd

IP Address

Validating the value to be an IP Address v4 or v6 with optional/mask. Only available when Command = traceroute.

Tcl Parameter: NetworkTestIpAddr

Host Name

Enter Target Host Name. No more than 128 Characters. Only available when Command = tracerouteToHost.

Tcl Parameter: NetworkTestHost

ICMP

Support for "traceroute" or "traceroutToSUT" or "traceroutToHost" using ICMP (-I option).

Tcl Parameter: NetworkTestIcmpEn

DNS Server Address

Enter DNS Server Address. Must be a valid IPv4 or IPv6 address. Only available when Command = tracerouteToHost.

Tcl Parameter: DnsServerAddress

Max TTL

Specify the maximum number of hops tracerouteToSut will probe.

Range: 150

Default: 30

Tcl Parameter: NetworkTestTtl

WaitTime (s)

The number of seconds to wait for a response to a probe.

Range: 110

Default: 5

Tcl Parameter: NetworkTestWaitTime

NQueries

The number of probe packets per hop.

Range: 110

Default: 3

Tcl Parameter: NetworkTestNQueries

 

^ Back to Top


Measurements

Use the radio button to enable Measurements Test, add options to the arguments for the Measurements Panel, Command Panel and User Defined Measurements.

Select for a SUT Query to retrieve and format ORAN L1 Statistics from a remote SUT. 

The SUT Query Test Case will allow a Script to be included as a TDF to parse vendor console or log file output as appropriate to send as measurements. This generic solution will be used to create a Test Session for the L1 statistics and saved as a Template in the ORAN Test Session Library for use by ORAN testing.

Spec Reference : 

DMTF (formerly known as the Distributed Management Task Force):

Measurements

Select Script Interface to SUT.

Options : SSH, RESTFUL-API.  RESTFul API is not currently supported 

Select Script File. Not a CSV file. The script file will receive the SUT output as its standard input, and should write measurement values on its standard output.

Example of Script file : 

Enable Periodic Execution to execute for the Interval (in seconds) that is provided.

Interval (s) - Range is 5 to 100, default 15.

Tcl Parameter: MeasScriptIntf

Tcl Parameter: MeasCfgFile

Tcl Parameter: MeasPeriodicExeEn

Tcl Parameter: MeasPeriodicExeRate

Command

Text box to define command executed on remote SUT. Base64 Encoding of command to be sent to remote SUT. 

The GUI editor allows up to 1024 ASCII characters or can be blank.  Default is blank. The GUI will encode/decode behind the scene. Users work in normal ASCII text.  

In the example above, the Command line is : top -b -d 2.5

Tcl Parameter: MeasCmd

 

User Defined Measurements

Select the Number of Measurements Tabs. Number of Tabs dedicated to User Measurements for this SUT-Query.

Range : 1 to 2

Default : 1

For example, if the configured number of tabs is 1, with 14 measurements, the Periodic Output of the TDF Script could be:

Select a Template. 

Row  Definition in the table :

1. # - Number of User Defined Measurements for the associated table.

2. Measurement Name - Name of the measurement. Range : 1 to256 characters. Valid characters are 0-9a-zA-Z '()+,-./:=?&%

3. Measurement Type - Choices are "int", "time_us", "time_us_min", "float", "string".  default is "int".

4. Variable - Variable reference of the measurement. The measurement variable is displayed for user reference, it is not a Tcl variable.

Tcl Parameter: MeasTabNum

Tcl Parameter: MeasNum_1

Tcl Parameter: MeasType_1_1

Tcl Parameter: MeasLabel_1_1

Add the Systems Under Test (Target SUT) on the Network Devices Tab

^ Back to Top


Collect PCAP Files 

The option to Collect PCAP Files provides the ability to execute a command to a remote SUT via the SUT SSH Connection (SUT and SSH tab are the same as with the Periodic option). 

When the Test Case is stopped, the remote file will be transferred to the Test Server and combined with locally generated PCAP files (enabled on the Port Capture tab of the Test Session.

Tcl Parameter: SutQueryType

Target Platform

Use the radio buttons to select the platform that will be queried:

Tcl Parameter: PcapLocation

Remote File Path

Enter the Path to PCAP on remote/local SUT (for collection in STOP state) .

Tcl Parameter: PcapRemotePath

Include Remote File in Integrated PCAP

Checkbox to indicate whether or not to include the SUT PCAP in the integrated PCAP file.

Tcl Parameter: PcapCombinedEn

Command

The query sent to the Target Platform. The value must be the exact command string as it would be entered in a telnet session.

Tcl Parameter: PcapCmd

 

^ Back to Top