HLAPI Command Reference - Spirent · HLAPI Command Reference ... The Knowledge Base gives you...

Spirent LandslideTM AutomationHLAPI Command ReferenceFebruary 2013

PN 71-006XXX Rev A

Spirent Communications, Inc.26750 Agoura RoadCalabasas, CA91302 USA

Copyright

© 2013 Spirent Communications, Inc. All Rights Reserved.

All of the company names and/or brand names and/or product names referred to in this document, in particular,the name “Spirent” and its logo device, are either registered trademarks or trademarks of Spirent plc and itssubsidiaries, pending registration in accordance with relevant national laws. All other registered trademarks ortrademarks are the property of their respective owners. The information contained in this document is subjectto change without notice and does not represent a commitment on the part of Spirent Communications. Theinformation in this document is believed to be accurate and reliable, however, Spirent Communications assumes noresponsibility or liability for any errors or inaccuracies that may appear in the document.

Limited Warranty

Spirent Communications, Inc. (“Spirent”) warrants that its Products will conform to the description on the faceof order, that it will convey good title thereto, and that the Product will be delivered free from any lawful securityinterest or other lien or encumbrance.

Spirent further warrants to Customer that hardware which it supplies and the tangible media on which it suppliessoftware will be free from significant defects in materials and workmanship for a period of twelve (12) months,except as otherwise noted, from the date of delivery (the “Hardware Warranty Period”), under normal use andconditions.

To the extent the Product is or contains software (“Software”), Spirent also warrants that, if properly used byCustomer in accordance with the Software License Agreement, the Software which it supplies will operate inmaterial conformity with the specifications supplied by Spirent for such Software for a period of ninety (90)days from the date of delivery (the “Software Warranty Period”). The “Product Warranty Period” shall meanthe Hardware Warranty Period or the Software Warranty Period, as applicable. Spirent does not warrant that thefunctions contained in the Software will meet a specific requirement or that the operation will be uninterruptedor error free. Spirent shall have no warranty obligations whatsoever with respect to any Software which has beenmodified in any manner by Customer or any third party.

Defective Products and Software under warranty shall be, at Spirent's discretion, repaired or replaced or a creditissued to Customer's account for an amount equal to the price paid for such Product provided that: (a) such Productis returned to Spirent after first obtaining a return authorization number and shipping instructions, freight prepaid, toSpirent's location in the United States; (b) Customer provides a written explanation of the defect or Software failureclaimed by Customer; and (c) the claimed defect actually exists and was not caused by neglect, accident, misuse,improper installation, improper repair, fire, flood, lightning, power surges, earthquake, or alteration. Spirent willship repaired Products to Customer, freight prepaid, based on reasonable best efforts after the receipt of defectiveProducts. Except as otherwise stated, any claim on account of defective materials or for any other cause whatsoeverwill conclusively be deemed waived by Customer unless written notice thereof is given to Spirent within theWarranty Period. Spirent reserves the right to change the warranty and service policy set forth above at any time,after reasonable notice and without liability to Customer.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, ALL IMPLIED WARRANTIES, INCLUDINGBUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENTAND FITNESS FOR A PARTICULAR PURPOSE, ARE HEREBY EXCLUDED, AND THE LIABILITY OFSPIRENT, IF ANY, FOR DAMAGE RELATING TO ANY ALLEGEDLY DEFECTIVE PRODUCT SHALL BELIMITED TO THE ACTUAL PRICE PAID BY THE CUSTOMER FOR SUCH PRODUCT. THE PROVISIONSSET FORTH ABOVE STATE SPIRENT'S ENTIRE RESPONSIBILITY AND CUSTOMER'S SOLE ANDEXCLUSIVE REMEDY WITH RESPECT TO ANY BREACH OF ANY WARRANTY.

Contents

3

Contents

How to Contact Us......................................................................................................4How to Test with Landslide HLAPI........................................................................... 5Common Functions.....................................................................................................6Test Cases................................................................................................................. 51

AAA Server Node.................................................................................................. 52DHCP Server Node................................................................................................89GGSN Node............................................................................................................94IP APP Node........................................................................................................ 101WIFI Offload Gateway Nodal.............................................................................. 106

Sub Functions......................................................................................................... 127Function Index.........................................................................................................202

How to Contact Us

4

How to Contact Us

To obtain technical support for any Spirent Communications product, please contact our Support Servicesdepartment using any of the following methods:

Americas

Email: [email protected]: http://support.spirent.comToll Free: +1 800-SPIRENT (+1 800-774-7368) (North America)Phone: +1 818-676-2616Hours: Monday through Friday, 05:30 to 18:00 Pacific Time

Europe, Africa, Middle East

Email: [email protected]: http://support.spirent.comPhone: +33 (1) 6137 2270 (France)Phone: +44 1803 546333 (UK)Hours: Monday through Thursday 09:00 to 18:00, Friday 09:00 to 17:00, Paris Time

Asia Pacific

Email: [email protected]: http://support.spirent.comPhone: +86 (800) 810-9529 (toll-free mainland China only)Phone: +86 (10) 8233 0033 (China)Hours: Monday through Friday 09:00 to 18:00 Beijing Time

The Spirent Knowledge Base (http://support.spirent.com) is designed to serve your technical informationneeds. The Knowledge Base gives you access to tens of thousands of documents that help answer yournetwork analysis and measurement questions. New content is added daily by Spirent's communicationsand networking experts. Sign in with your user ID and password to gain access to additional content thatis available only to customers – user manuals, Help files, release notes, Tech Bulletins, and more. Whenyou sign in, you can also use the Knowledge Base to download software and firmware, and to manageyour SRs.

Information about Spirent Communications and its products and services can be found on the maincompany website at http://www.spirent.com.

Company Address

Spirent Communications, Inc.26750 Agoura RoadCalabasas, CA 91302USA

mailto:[email protected]

http://support.spirent.com






http://www.spirent.com

How to Test with LandSlide HLAPI

5

How to Test with Landslide HLAPI

The Spirent Landslide High Level API (HLAPI) is designed by Spirent to meet the high demands ofautomation testing by customers. HLAPI hides the lower-level APIs of Spirent Landslide, making testequipment easier to automate.

The following steps will give you a general idea of how to configure and run test sessions with LandslideHLAPI:

1. Connect to the TAS.

To test with Landslide, first you need to connect to the TAS. The HLAPI function for this islsh::connect. This function will also create a default test session. If you don’t want to use the defaultvalues configured in the test session, you can call lsh::test_session_config to configure it.

2. Create and configure a test session.

If you want to create a test session in addition to the one just created with lsh::connect, calllsh::test_session_create. You can use lsh::test_session_config to configure the secondtest session.

3. Create and configure a test case.

A test case is the core of a test script. After a test session is created, you create the test case under it.For each area of the API there are at least two functions related to test cases. One function is for basicconfiguration of the test case, and the other function(s) is for additional configurations.

For example, with DHCP server you use the function lsh::dhcp_server_node_configfor basic configuration of the test case. To configure additional information (IP pools), you uselsh::ip_pools_config.

To help identify the basic configuration function, it will always have node or nodal in its name, as inlsh::dhcp_server_node_config.

4. Validate the test sessions.

If there are errors in the configuration, you can’t save or run the test session, so you need to validate eachtest session to see if the configuration is acceptable. Use lsh::validate.

5. Run the test session.

After validating each test session you can start the test.

6. Get real-time results.

You can get results while the test session is running. These are called real-time results.

7. Stop the test session.

You can stop the test session manually using lsh::stop_test.

8. Get the end-of-test results.

You can also get test results after the test session has stopped. These are called end-of-test (EOT)results.

Multiple Test Cases in a Single Script

You can configure more than one test case in a single test script. You can either configure all the test casesin one test session, or configure each test case in a separate test session.

• If you configure all test cases in the same test session, then you can configure the automation controlsteps in the test session to determine the sequence of the test cases.

• If you configure the test cases in different test sessions, then you can start the corresponding test sessionto start the test case, and then manually control the starting and stopping of each test session. You canmanually control the sequence of the test cases in the test script.

Common Functions

6

Common Functions

Functions:lsh::connectlsh::criterion_configlsh::test_session_createlsh::test_session_configlsh::test_case_configlsh::report_options_configlsh::validatelsh::test_controllsh::run_testlsh::stop_testlsh::abort_testlsh::get_resultslsh::capturelsh::ger_tac_reportlsh::sut_configlsh::log_configlsh::automation_configlsh::get_session_statuslsh::automation_step_buidlerlsh::reserve_portslsh::dmf_configlsh::dmf_control_configlsh::get_handlelsh::save

lsh::connect

Name: lsh::connect

Purpose: This function is used to connect to the Landslide TAS. At the same time, a test session and the corresponding report options are created.

Synopsis: lsh::connect -device <TAS address> -username <user name> -password <password>

Arguments:

-device Specifies the IP address of the TAS that you want to connect to. -username Specifies the user name used to connect to the TAS. -password Specifies the password.

Return Values: test_handle The test session handle, which will be used when you want to modify the test session, or create a test case. Will be returned only when the status is 1. status Success (1) or failure (0) of the operation. log Returned only when the status is 0.

Common Functions

7

Examples: set ret [::lsh::connect \ -device $device \ -username $username \ -password $password ]\ Return: {status 1} {test_handle java0x4}

lsh::criterion_config

Name: lsh::criterion_config

Purpose: Create automation control steps, which define the test flow when the test executes multiple test cases. The order is the steps sequence when created.

Synopsis: lsh::criterion_config -test_hnd < ALPHANUM > -condition { TestStateOrStepCondition|MeasurementCondition| CompareMeasurementsCondition|TcStateCondition } -result_type{ PASS|FAIL|LOG} -start<ANY> -stop<ANY> -expire<ANY> -reset<ANY> -start_logical_not_en{true|false} -stop_logical_not_en{true|false} -expire_logical_not_en{true|false} -reset_logical_not_en{true|false}_ -operator {==|!=|>|>=|<|<=} -test_state_step <ANY> -view_ts <NUMERIC> -view_tc <NUMERIC> -test_case_state{UNINITIALIZED|INITIALIZING |INITIALIZED|STARTING |STARTED|RUNNING|STOPPING|STOPPED|CLEANUP} -tab2 <ANY> -view_summary2 {true|false} -measurement2<ANY> -view_ts2<NUMERIC> -view_tc2<NUMERIC> -tab<ANY> -view_summary {true|false} -measurement<ANY> -value<NUMERIC>Arguments: -test_hnd Specifies the test session handle.

-condition The condition that the criterion monitors. Possible values: TestStateOrStepCondition - A condition that compares a test session's state, or step, to a user specified value. MeasurementCondition - A condition that compares a measurement to a user specified value. CompareMeasurementsCondition - A condition that compares two measurements to each other TcStateCondition - a condition that compares a test case's state to a user specified value. Default: Test_State_Step

Common Functions

8

-result_type Determines the status of the criterion when the condition is true or expired. Possible values: PASS - The criterion is set to PASSED when the condition is true; FAILED when expired. FAIL - the criterion is set to FAILED when the condition is true; PASSED when expired. LOG - the criterion is set to OCCURRED when the condition is true; PENDING when expired. Default: PASS

-start The index of the criterion or special enumeration value that indicates when this criterion starts monitoring its condition. Possible values are: START_OF_TEST - The start of test, before anything occurs. END_OF_TEST: The very end of test. START_OF_ITERATION - The start of a test iteration. This only occurs in a multi-iteration test when the test reaches the "INIT" state. END_OF_ITERATION - The end of test iteration. This occurs for all tests each time the test reaches the "FINAL" state. <value> - The index of the criterion that indicates when to start this criterion. Default: START_OF_TEST

-stop The index of the criterion or special enumeration value that indicates when this criterion expires. Possible values are: NEVER - In essence, monitor until the very end of the test START_OF_ITERATION - The start of test iteration. This only occurs in a multi-iteration test when the test reaches the "INIT" state. END_OF_ITERATION - The end of test iteration. This occurs for all tests each time the test reaches the "FINAL" state. <value> - The index of the criterion that indicates when to stop this criterion.

-expire The index of the criterion or special enumeration value that indicates when this criterion expires. Possible values are: END_OF_TEST - The very end of test. START_OF_ITERATION - Default value. The start of test iteration. This only occurs in a multi-iteration test when the test reaches the "INIT" state. END_OF_ITERATION - The end of test iteration. This occurs for all tests each time the test reaches the "FINAL" state. <value>: the index of the criterion.

-reset The index of the criterion or special enum value that indicates when this criterion resets. Possible values are:

Common Functions

9

NEVER - Never reset the criterion. START_OF_ITERATION - Default value. The start of test iteration. This only occurs in a multi-iteration test when the test reaches the "INIT" state. END_OF_ITERATION - the end of test iteration. This occurs for all tests each time the test reaches the "FINAL" state. <value> - the index of the criterion indicates when to reset this criterion.

-start_logical_not_en When true, indicates that the criterion will start monitoring its condition when the -start is not true. Only valid when the -start is a specific user criterion. Possible values: true, false Default: false

-stop_logical_not_en When true, indicates that the criterion will stop monitoring its condition when -stop is not true. Only valid when -stop is a specific user criterion. Possible values: true, false Default: false

-expire_logical_not_en When true, indicates that the criterion will expire when -expire is not true. Only valid when the -expire is a specific user criterion. Possible values: true, false Default: false

-reset_logical_not_en When true, indicates that the criterion will reset when -reset is not true. Only valid when the -reset is a specific user criterion. Possible values: true, false Default: false

-operator Possible values: == - Equals != - Not Equals > - Greater Than >= - Greater Than or Equals < - Less Than <= - Less Than or Equals Default: ==

-test_state_step The state or step to compare to. Valid only when condition is TestStateOrStepCondition. Possible values are: INIT - test is starting an iteration, test cases are being initialized. STARTING - Test cases have been initialized and are being started. STARTED - Test cases have been started RUNNING - Test is running nominally STOPPING - Test cases are being stopped STOPPED - Test cases have been stopped CLEANUP - Test cases are being cleaned up WAIT_FOR_TRANSFERS - Test has completed the last iteration and any TS generated files are being transferred to the TAS. FINAL - Test has completed a iteration, all TCs are down

Common Functions

10

COMPLETE - Test has completed normally COMPLETE_ERROR - Test has completed with system errors <N> - Step <N> of automation control <N_Delay> - In the delay of step <N> <N_WAITING> - In a wait step <N> Default: INIT

-view_ts The test server index, when condition is TcStateCondition - Indicates the test case to monitor. MeasurementCondition - Includes the measurement, or summary indicator. CompareMeasurementsCondition - Includes the first measurement, or summary indicator.

-view_tc The test case index, when -condition is TcStateCondition - indicates the test case to monitor MeasurementCondition - includes the measurement, or summary indicator CompareMeasurementsCondition - includes the first measurement, or summary indicator

-test_case_state The state to compare to. Valid only when condition is TcStateCondition. Possible values: UNINITIALIZED - test case is idle. Default value. INITIALIZING - test case is initializing, resources are being allocated. INITIALIZED - test case is initialized, resources are allocated. STARTING - test case is starting, test is being started. STARTED - test case is started, sessions are starting. RUNNING - test case is running, all sessions are up. STOPPING - test case is stopping, sessions are coming down. STOPPED - test case is stopped. CLEANUP - test case is cleaning up. Default - UNINITIALIZED

-tab2 The name of the tab that contains the second measurement. Valid only when condition is CompareMeasurementsCondition.

-view_summary2 When true, a summary view measurement (second) will be used. Valid only when condition is CompareMeasurementsCondition. Possible values: true, false Default: false

-measurement2 The name of second measurement. Valid only when condition is CompareMeasurementsCondition.

-view_ts2 The test server index that includes the second measurement, or summary indicator. Valid only when -view_summary2 is false.

-view_tc2 The test case index that includes the second measurement, or summary indicator. Valid only when -view_summary2 is false.

Common Functions

11

-tab The name of the tab that contains the measurement (condition is CompareMeasurementsCondition) or first measurement for MeasurementCondition.

-view_summary When true, a summary view measurement will be used. Valid only when condition is MeasurementCondition or CompareMeasurementsCondition. Possible values: true, false Default: false

-measurement The name of measurement (condition is MeasurementCondition) or first measurement for condition CompareMeasurementsCondition.

-value The value to use for comparison. Valid only when -condition is MeasurementCondition

Return Values status Success (1) or failure (0) of the operation. log Returned only when the status is 0

Examples: set ret [lsh::criterion_config -test_hnd $test\ -result_type PASS\ -start START_OF_TEST\ -stop START_OF_ITERATION\ -expire END_OF_ITERATION\ -reset START_OF_ITERATION\ -condition TcStateCondition\ -test_case_state UNINITIALIZED\ -view_ts 0\ -view_tc 0\ ] keylget ret status sta if {$sta == $FAIL} { puts "failed to create_criterion . $ret" exit; } else { puts "successfully create_criterion. $ret" }

lsh::test_session_create

Name: lsh::test_session_create

Purpose: This function is used to create a test session. Besides the test session created in the lsh::connect, you can create another test session with this function in one script.

Synopsis: lsh::test_session_create -lib <ANY> -name <ANY> -keywords <ANY> -duration <ANY> -iterations <ANY> -reserve_ports <ANY>

Arguments:

Common Functions

12

-lib Specifies where the test session will be saved. Default: "Global" -name Specifies the name of the test session Default: "test_from_lstapi" -keywords Specifies the keywords of the test session Default: "" -duration Specifies the duration of the test session Default: 0 -iterations Specifies the number of the iterations. Default: 1 -reserve_ports Determines whether to reserve the port. when it is true, you can configure which ts and which port on this ts will be reserved. Default: false

Return Values test_handle The test session handle, which will be used when you want to modify the test session, or create test case. Will be returned only when the status is 1. status Success (1) or failure (0) of the operation. log Returned only when the status is 0.

Examples: set ret [::lsh::test_session_create \ -lib sms\ -name "test_session_from_script"] Return: {status 1} {test_handle java0x6}

lsh::test_session_config

Name: lsh::test_session_config

Purpose: This function is used to configure the test session created earlier.

Synopsis: lsh::test_session_config -test_hnd <test session handle> -lib <ANY> -name <ANY> -keywords <ANY> -description <ANY> -duration <ANY> -iterations <ANY> -reserve_ports <ANY> -cpu_thres_hold <0-100>

Arguments: -test_hnd Specifies the test handle which will be modified.

Common Functions

13

-lib Specifies where the test session will be saved. Default: "Global" -name Specifies the name of the test session Default: "test_from_lstapi" -keywords Specifies the keywords of the test session Default: "" -description The description of the test session -duration Specifies the duration of the test session Default: 0 -iterations Specifies the number of the iterations. Default: 1 -reserve_ports Specifies if the port will be reserved. When it is true, you can configure which ts and which port on this ts will be reserved. Default: false -cpu_thres_hold Specifies the TS CPU Threshold. Range:0-100 Default: 95

Return Values: status Success (1) or failure (0) of the operation log Returned only when the status is 0

Examples: set ret [::lsh::test_session_config \ -test_hnd $test\ -lib sms\ -name "test_session_from_script"] Return: {status 1}

lsh::test_case_config

Name: lsh::test_case_config

Purpose: Used to configure the test case.

Synopsis: lsh::test_case_config -tc_hnd <test case handle> -lib < ALPHANUM> -name < ALPHANUM> -keywords < ALPHANUM> -associated_phys < NUMERIC> -description < ALPHANUM> -linked { true|false}

Arguments: -tc_hnd Specifies the test case handle.

Common Functions

14

-lib The name of the library the test case is, or will be, stored in on the TAS. Default: Global -name The name of the test case. Default: -keyword Specific words that identify the test case. Default: "" -associated_phys The names of any phys not used in the test case that still need to be associated with this test case for port reservation feature. Default: 0 -description The description of the test case instance. Default: 1 -linked Indicates if the test case is linked and should be reloaded from the saved test case each time the test session is opened. This is only valid when the test case instance represents a user-saved test case. Default: false

Return Values status Success (1) or failure (0) of the operation. log Returned only when the status is 0.

Examples: set ret [lsh::test_case_config \ -tc_hnd $test_case_handle\ -lib "sms"\ -name "test_case_created_from_script"] Return: {status 1}

lsh::report_options_config

Name: lsh::report_options_config

Purpose: Used to configure the report options.

Synopsis: lsh::report_options_config -test_hnd <test session handle> -view_type <ANY> -form {Excel|Text} -per_interval {true|false} -auto_save_en {true|false} -auto_save_interval <NUMERIC> -gen_eot_db_en {true|false} -req_max_interval_num <NUMERIC> -gen_zip_inc_tc_diagrams_en {true|false} -l47_subtotal {None|Mobile_Node|DMF} -l47_per_session {true|false} -l3_per_session {true|false} -mobile_access_per_session {true|false} -core_nodes_per_node {true|false}

Common Functions

15

-ts_report_en {true|false} -ts_report_per_session_en {true|false} -ts_report_per_mn_en {true|false} -per_session_option {all|partial} -per_mn_option {all|partial} -start_session <NUMERIC> -sessions_num <NUMERIC> -start_mn <NUMERIC> -mns_num <NUMERIC>

Arguments: -test_hnd Specifies the test session handle under which the test report option is configured. -view_type Select the report level from the View drop-down list. You can capture a Summary report, individual reports for All Test Cases, or Summary and Each Test Case in Separate Files for a individual test cases in the list.

-form Specifies the format of the file type. Default: Excel -per_interval Check the Use Per Interval box to set the report values to per-interval. If the box is cleared, cumulative report values will be captured. The cumulative report also includes the Per-Interval values for Rate and Div (calculated) measurements. Default: false -auto_save_en Check the Auto Save Every box to periodically save your Test Report during the test. By default, a Test Report will be saved every 4 hours. Modify the Hours field to change the report cycle. Default: false -auto_save_interval Specifies the auto save interval when the auto_save_en is set to true. Default: false Dependency: auto_save_en true -gen_eot_db_en Specifies whether to Generate End-of-test Database option to save a test report database that can be opened and viewed with the Landslide Results Manager report viewer. Default: false -req_max_interval_num Specifies the Requested maximum Number of Intervals to indicated the maximum number of intervals reported in the database. -gen_zip_inc_tc_diagrams_en Specifies whether to generate a zip file containing the test case diagrams Default: false -l47_subtotal Select Sub-Totals by protocol, DMF instance, or no sub-totals generated for Layer 4 - 7. The possible value can be None, DMF or Mobile_Node Default: None -l47_per_session Enables or disables the l4-7 per session report. When it is true, the per session related option can be configured. Default: false -l3_per_session Enables or disables the l3 per session report. When it is true, the per session related option can be configured. Default: false

Common Functions

16

-mobile_access_per_session Enables or disables the Mobile Access Transport per session report. When it is true, the per session related option can be configured. Default: false -core_nodes_per_node Enables or disables the Core Network Nodes per Node report. When it is true, the per node related option can be configured. Default: false -ts_report_en Specifies whether to include the EOT report amd whether to generate the report during test. Default: false Dependency: l47_subtotal Mobile_Node, l47_per_session true, l3_per_session true, mobile_access_per_session true -ts_report_per_session_en Specifies whether to include the per session data in the EOT report. Default: false Dependency: ts_report_en true -ts_report_per_mn_en Specifies whether to include the Mobile Node Data in the EOT report. Default: false Dependency: l47_subtotal Mobile_Node&ts_report_en true -per_session_option Specifies if all the session will be included in the report. Default: all Dependency: l47_per_session true, l3_per_session true, mobile_access_per_session true -per_mn_option Specifies if all the Mobile Node included in the report. Default: all Dependency: l47_subtotal Mobile_Node -start_session When not all of the sessions will be included in the report, should specify the start session. Default: 0 Dependency: per_session_option partial -sessions_num When not all of the sessions will be included in the report, should specify the number of session. Default: 0 Dependency: per_session_option partial -start_mn When not all of the Mobile Node will be included in the report, should specify the start Mobile Node. Default: 0 Dependency: per_mn_option partial -mns_num When not all of the Mobile Node will be included in the report, should specify the number of Mobile Node. Default: 0 Dependency: per_mn_option partial

Return Values: status Success (1) or failure (0) of the operation. log Returned only when the status is 0.Examples:

Examples: set ret [::lsh::report_options_config \ -test_hnd $test_session_handle\ -form "Text"\

Common Functions

17

-l47_subtotal Mobile_Node\ -l47_per_session true\ -ts_report_en true\ -ts_report_per_session_en true\ -per_mn_option partial\ -per_session_option partial\ -start_mn 1\ -mns_num 5\ -start_session 3\ -sessions_num 6] Return: {status 1}

lsh::validate

Name: lsh::validate

Purpose: Used to do the validation for the test session. This function should be performed before save or run the test session.

Synopsis: lsh::validate -test_hnd <test session handle>

Arguments: -test_hnd The handle of the test session.

Return Values: val_state State of the validation result. status Success (1) or failure (0) of the operation. log Log information of the validation.

Examples: set ret [lsh::validate -test_hnd $test_session_handle]

Return: {val_state Valid} {log {{} Valid-Ready-To-Run-Or-Save}} {status 1}

lsh::test_control

Name: lsh::test_control

Purpose: Used to to start, stop, abort or continue a test session. You can also use this function to replace following functions: lsh::run_test, lsh::stop_test, and lsh::abort_test.

Synopsis: lsh::test_control -test_hnd <test session handle> -action{run|stop|abort|continue}

Arguments: -test_hnd The handle of the test session which will be started.

-action

Common Functions

18

The action to do with the test session. Possible values: run - Starts the test session. stop - Stops the test session. abort - Abort the test session. continue - Continues the test session when the test session is in the waiting status

Return Values status Success (1) or failure (0) of the operation.

Examples: set ret [lsh::test_control -test_hnd $test -action run] return: {status 1} set ret [lsh::test_control -test_hnd $test -action stop] return: {status 1} set ret [lsh::test_control -test_hnd $test -action continue] return: {status 1}

lsh::run_test

Name: lsh::run_test

Purpose: Used to start a test session

Synopsis: lsh::run_test -test_hnd <test session handle>

Arguments: -test_hnd The handle of the test session which will be started.

Return Values: status Success (1) or failure (0) of the operation.

Examples: set ret [lsh::run_test -test_hnd $test] Return: {status 1}

lsh::stop_test

Name: lsh::stop_test

Purpose: Used to stop a test session

Synopsis: lsh::stop_test -test_hnd <test session handle>

Arguments: -test_hnd The handle of the test session which will be stopped.

Common Functions

19


Examples: set ret [lsh::stop_test -test_hnd $test] Return: {status 1}

lsh::abort_test

Name: lsh::abort_test

Purpose: Used to abort a test session

Synopsis: lsh::abort_test -test_hnd <test session handle>

Arguments: -test_hnd The handle of the test session which will be aborted.


Examples: set ret [lsh::abort_test -test_hnd $test] Return: {status 1}

lsh::get_results

Name: lsh::get_results

Purpose: Used to get the results. Two types of test results are available: Real time result during the test session, or EOT result after the test session stops.

Synopsis: lsh::get_results -test_hnd <test session handle> -tab <the tab name> -name <name of the returned result>

Arguments: -test_hnd Specifies the test session handle. -tab Specifies the tab name. Will return the result of the specified tab. -name Specifies the argument name. Will return the result of the specified argument. Note: If only the name is specified and the tab is not specified, then all the test result will be returned.

Examples:

Common Functions

20

set r1 [::lsh::get_results -test_hnd $test -tab "Test Summary" -name "Start Time"] {{Test Summary} {{{Start Time} {Mon Dec 10 08:45:56 UTC 2012}}}} {status 1} set r2 [::lsh::get_results -test_hnd $test -tab "Test Summary"] {{Elapsed Time} {21 Sec(s) }} {{Test Summary} {{{Start Time} {Mon Dec 10 08:45:56 UTC 2012}} {{Client Data Nodes Established} 0} {{Client Data Nodes Pending} 0} {{Basic Data Flow Resources Started} 0} {{Advanced Data Flow Resources Started} 0} {{Enhanced L4-L7 Data Flow Resources Started} 0} {{Accounting Started Sessions} 0} {{Accounting Stopped Sessions} 0}}} {status 1} set r3 [::lsh::get_results -test_hnd $test -name "Start Time"] {{Elapsed Time} {20 Sec(s) }} {{Test Summary} {{{Start Time} {Mon Dec 10 09:05:28 UTC 2012}} {{Client Data Nodes Established} 0} {{Client Data Nodes Pending} 0} {{Basic Data Flow Resources Started} 0} {{Advanced Data Flow Resources Started} 0} {{Enhanced L4-L7 Data Flow Resources Started} 0} {{Accounting Started Sessions} 0} {{Accounting Stopped Sessions} 0}}} {RADIUS {{{Access Requests Sent} 5} {{Access Accepts Received} 0} {{Access Rejects Received} 0} {{Access Request Timeouts} 4} {{Access Challenges Received} 0} {{Accounting Requests Sent} 0} {{Accounting Starts Sent} 0} {{Accounting Stops Sent} 0} {{Accounting Interims Sent} 0} {{Accounting Responses Received} 0} {{Accounting Request Timeouts} 0} {{Poorly Formed Received} 0} {{Authentication Failed} 0} {{Average Access Response Time} {0 us}} {{Minimum Access Response Time} {0 us}} {{Maximum Access Response Time} {0 us}} {{Access Response Count} 0} {{Average Node2 Access Response Time} {0 us}} {{Minimum Node2 Access Response Time} {0 us}} {{Maximum Node2 Access Response Time} {0 us}} {{Node2 Access Response Count} 0} {{Average Accounting Start Response Time} {0 us}} {{Minimum Accounting Start Response Time} {0 us}} {{Maximum Accounting Start Response Time} {0 us}} {{Accounting Start Response Count} 0} {{Average Accounting Stop Response Time} {0 us}} {{Minimum Accounting Stop Response Time} {0 us}} {{Maximum Accounting Stop Response Time} {0 us}} {{Accounting Stop Response Count} 0} {{Average Accounting Interim Response Time} {0 us}} {{Minimum Accounting Interim Response Time} {0 us}} {{Maximum Accounting Interim Response Time} {0 us}} {{Accounting Interim Response Count} 0} {{Sessions Stopped by EAP} 0} {{Port Identifier Conflict} 0}}} {{NAS Node} {{{Total Received Packets} 5} {{Total Sent Packets} 5} {{Total Received Bytes} 795} {{Total Bits Received/Sec} 333.202} {{Total Sent Bytes} 655} {{Total Bits Sent/Sec} 274.525} {{Total Invalid Received Packets} 5} {{Total Packets} 0} {{Total Bytes} 0} {{Total Received Packets Discarded} 0} {{Total Sent Packets Discarded} 0} {{Total Discarded Packets} 0} {{Total Received Fragments} 0} {{Total Received Fragmented Packets} 0} {{Total Received Non-Fragmented Packets} 5} {{Total Sent Fragments} 0} {{Total Sent Fragmented Packets} 0} {{Total Sent Non-Fragmented Packets} 5} {{IPsec Tunnel Attempts} 0} {{IPsec Tunnel Successes} 0} {{IPsec Tunnel Failures} 0} {{IPsec Unhandled Packets} 0} {{Pings Received} 0} {{Pings Sent} 0} {{Ping replies Received} 0} {{Accounting On Request Sent} 0} {{Accounting On Response Received} 0} {{Accounting Off Request Sent} 0} {{Accounting Off Response Received} 0} {{EAP Identity Request Count} 0} {{EAP Identity Response Count} 5} {{EAP Success Count} 0} {{EAP Failure Count} 0} {{EAP Notification Count} 0} {{EAP NAK Response Count} 0} {{EAP Expanded NAK Response Count} 0} {{EAP Unknown Method Type Count} 0} {{EAP Timeout Count} 4} {{EAP Average Setup Time} {0 us}} {{EAP Minimum Setup Time} {0 us}} {{EAP Maximum Setup Time} {0 us}} {{EAP Setup Count} 0} {{SIM Start Request Count} 0} {{SIM Start Response Count} 0} {{SIM Challenge Request Count} 0} {{SIM Challenge Response Count} 0} {{SIM Fast Reauthentication Request Count} 0} {{SIM Fast Reauthentication Response Count} 0} {{SIM Client Error Response Count} 0} {{SIM Notification Request Count} 0} {{SIM Notification Response Count} 0} {{SIM Success Count} 0} {{SIM Failure Count} 0} {{SIM Authentication Success Count} 0} {{SIM Authentication Failure Count} 0} {{SIM Malformed Message Count} 0} {{SIM Timeout Count} 0}}} {{TS CPU Utilization} {{{TS(ls-ts3)[0] Avg CPU Utilization (%)} 0}}} {status 1}

lsh::capture

Name:

Common Functions

21

lsh::capture

Purpose: Used to capture the packets sent and received during the testing.

Synopsis: lsh::capture -action { Start|Stop|Retrieve} -ts <test server name> -intf <interface of the ts> -dir <directory>

Arguments: -action Specifies whether you want to start, stop or retrieve the captured packet. -ts Specifies on which test server you will start, stop or retrieve the captured packet. -intf Specifies on which interface of the specified test server you will start, stop or retrieve the captured packet. -dir When you want to retrieve the captured packet, specify the directory of the file will be saved.

Return Values status Success (1) or failure (0) of the operation.

Examples: Starts the capture: set ret [lsh::capture -ts $ts_name -action "Start" -intf "eth1"] Return: { status 1}

Stops the capture: set ret [lsh::capture -ts $ts_name -action "Stop" -intf "eth1"] Return: { status 1}

Retrieves the capture file: set ret [lsh::capture -ts $ts_name\ -action "Retrieve"\ -intf "eth1" \ -dir "D:/Landslide/captured_file"] Return: { status 1}

lsh::ger_tac_report

Name: lsh::ger_tac_report

Purpose: Used to generate a TAC Report for a Test.

Synopsis: lsh::ger_tac_report -test_hnd < test session handle > -report_dir_name <name of TAC Report> -overwrite {"yes"| "no"}

Arguments: -test_hnd

Common Functions

22

Specifies the test session handle. -report_dir_name Specifies the name of the TAC Report. The directory is included. -overwrite Specifies whether overwrite TAC Report when generating it. Default value is "no".


Examples: set report_file "D:/TAC_Report" set ret [lsh::ger_tac_report\ -test_hnd $test\ -report_dir_name $report_file\ -overwrite "yes"\ ]

lsh::sut_config

Name: lsh::sut_config

Purpose: Used to configure the SUT. With this function, you can add, modify or delete a SUT on the TAS.

Synopsis: lsh::sut_config -mode { add|modify|delete} -name <name of SUT> -ip <ip addr of SUT> -manage_ip_addr < management ip addr of SUT > -username <user name of SUT> -password<password of SUT>

Arguments: -mode Specifies the mode of the SUT action, the possible value is add, modify or delete. It is mandatory -name Specifies the name of the SUT. It is mandatory -ip The ip address of the SUT. -manage_ip_addr The management ip address of the SUT. -username The user name of the SUT. -password The password of the SUT.


Examples: set ret [::lsh::sut_config\ -mode add\ -name sut_add_from_script\ -ip 10.0.0.2\

Common Functions

23

-manage_ip_addr 10.0.0.1\ -username hehe\ -password abcd]

lsh::log_config

Name: lsh::log_config

Purpose: Used to configure the log information, specify the log files name and where to save the log files.

Synopsis: lsh::log_config -logfile <ANY> -log {0|1} -ls_logfile <ANY> -ls_log {0|1} -lsh_logfile <ANY> -lsh_log {0|1} -lsh2lsmapping {0|1} -lsh2lsmappingfile <ANY> -log_level {0|1|2|3|4|5|6|7}

Arguments: -logfile The file name of the Landslide HLAPI log. Default: "ltapi_logfile" Dependency: log 1 -log Specifies whether the Landslide HLAPI log file will be generated. Possible Values: 0, 1. Default: 0 -ls_logfile The file name of the LandSlide native command log. Default: "ls_logfile" Dependency: ls_log 1 -ls_log Specifies whether the LandSlide command log file will be generated. It will not generate defaultlly. Default: 0 -lsh_logfile The file name of the Landslide HLAPI command log. Only the Landslide HLAPI command will be included. Default: lsh_logfile Dependency: lsh_log 1 -lsh_log Specifies whether the Landslide HLAPI command log file will be generated. Default: 0 -lsh2lsmapping Specifies whether the HLAPI-LandSlide command mapping log file will be generated. Default: 0 -lsh2lsmappingfile The file name of the HLAPI-LandSlide command mapping log. The Landslide HLAPI and the LandSlide commands will be included. Default: lsh2lsmappingfile Dependency: lsh2lsmapping 1

Common Functions

24

-log_level Specifies the log level. Possible value is: 0,1,2,3,4,5,6,7 0: emergency 1: alert 2: critical 3: error 4: warn 5: notify 6: info 7: debug Default: 7


Examples: set ret [::lsh::log_config \ -log 1\ -logfile "D:/ltapi_logfile"\ -ls_log 1\ -ls_logfile "D:/ls_logfile" \ -lsh_log 1\ -lsh_logfile "D:/lsh_logfile" \ -lsh2lsmapping 1\ -lsh2lsmappingfile "D:/sh2lsmappingfile"]

Return: {status 1}

lsh::automation_config

Name: lsh::automation_config

Purpose: Creates automation control steps, which define the test flow when the test executes multiple test cases. The order is the steps sequence when created.

Synopsis: lsh::automation_config -test_hnd < ALPHANUM > -tc_handle <ANY> -function {Loop_Start|Loop_End|Wait|""} -tc_activity {Init|Start|Stop|Cleanup|""} -predecessor_tc_handle <ANY> -predecessor_state {RUNNING|STOPPED|""} -delay_or_loop <NUMERIC>

Arguments: -test_hnd Specifies the test session handle

-tc_handle Specified the test case on which to perform an activity. It can be obtained from any test case creating function, such as aaa_server_node_config.

-function Specicial functions of the test case to perform Possible values: Loop_Start - The start of a loop. Loop_End - The end of a loop (number of loops is stored in the

Common Functions

25

delay_or_loop of this step) Wait - A WAIT step "" - A blank step used to build an AND grouping of predecessor conditions

-tc_activity The action that occurs on the given test case when the step is executed Possible values: "" - Empty string is allowed for Loop_Start, Loop_End and Wait steps Init - Initializes the test case Start - Starts the test case Stop - Stops the test case Cleanup - Releases test case resources Default: ""

-predecessor_tc_handle Specified the predecessor test case on which to perform an activity. It can be obtained from any test case creating function, such as aaa_server_node_config. Default: -1

-predecessor_state The state the predecessor test case must be in before the step's activity is executed. Possible values: RUNNING - The RUNNING state STOPPED - the STOPPED state "" - No predecessor. Function should also be "" Default: ""

-delay_or_loop The time in seconds to delay, after the predecessor condition is met, before executing the step. Or, for a Loop_End step, this sets the number of loops to execute in this step. Default: 0


Examples: set ret [lsh::automation_config -test_hnd $test\ -tc_handle $tc1\ -tc_activity Init\ -delay_or_loop 0\ -predecessor_tc_handle $tc2\ -predecessor_state RUNNING\ ]

lsh::get_session_status

Name: lsh::get_session_status

Common Functions

26

Purpose: Provides a fuction API to get certain test session's current status

Synopsis: lsh::get_session_status -test_hnd < ALPHANUM >

Arguments: -test_hnd Specifies the test session handle Return Values Idle The test seesion status is idle Running The test seesion status is in running Waiting The test seesion status is in waiting

Examples: set session_status [::lsh::get_session_status -test_hnd $test]

lsh::automation_step_buidler

Name: lsh::automation_step_buidler

Purpose: Provides a quick way to build certain patterns of automation control. You may add steps to a set of TCs by selecting a pattern of steps and it will insert the automation steps

Synopsis: lsh::automation_step_buidler -test_hnd < ALPHANUM > -tc_hnd <ANY> -mode [series|pyramid|parallel]

Arguments: -test_hnd Specifies the test session handle. -tc_hnd Specified the test case handle(or list) which included in the step builder. It can be more than one test cases. -mode Possible values: Series - Runs each TC separately (Init Start Stop Cleanup Init Start Stop Cleanup). The default value. Pyramid - Starts all TCs and then stops all TCs in reverse order (Init Start Init Start Stop Cleanup Stop Cleanup). Parallel - Initializes, starts and runs TC in parallel (Init Init Start Start Stop Stop Cleanup Cleanup).


Examples: lsh::automation_step_buidler -test_hnd $test\ -tc_hnd "$tc2 $tc1"\ -mode parallel

Common Functions

27

lsh::reserve_ports

Name: lsh::reserve_ports

Purpose: Specifies which test server and ports on the test server will be reserved.

Synopsis: ::lsh::reserve_ports -test_hnd <test session handle> -type{Ip|Route|both} -ts_name<test server name> -ports< ALPHANUM > -ip_addr<IP> -mask<ANY> -ip_num< NUMERIC > -dst<IP> -route_mask<ANY> -gateway<IP>

Arguments: -test_hnd Specifies the test session handle, under which the test ports reservation is configured. This argument is mandatory -type Specifies whether to reserve the IP ranges or the Static routes. This argument is mandatory Possible values: Ip, Route, both Default: Ip -ts_name The test server name you want to reserve. This is mandatory. -ports The ports on the test server specified in ts_name will be reserved. It can be a list to reserve more than one ports on this test server, such as eth1 Dependency: This argument is available when type is set to Ip or both. -ip_addr The starting ip address of the port, if it is a list, the length of the list should be equal to the length of ports list Dependency: This argument is available when type is set to Ip or both. -mask The mask of the ports' IP address. It can be a list, and if the length of the list is less than the list of the ports, it will add the default value /24 for the ports. Default: /24 Dependency: This argument is available when type is set to Ip or both. -ip_num The number of the addresses in the pool. It can be a list, and if the length of the list is less than the list of the ports, it will add the default value 1 for the ports. Default: 1 Dependency: This argument is available when type is set to Ip or both. -dst The destination IP address of the static route to be reserved. It is mandatory when you want to reserve the static route. Dependency: This argument is available when type is set to Route or both.

Common Functions

28

-route_mask The mask of the destination IP address. It is mandatory when you want to reserve the static route. Dependency: This argument is available when type is set to Route or both. -gateway The gateway of the destination IP address. It is mandatory when you want to reserve the static route. Dependency: This argument is available when type is set to Route or both.


Examples: set ret [::lsh::reserve_ports -test_hnd $test\ -type Ip\ -ts_name "ls-ts3"\ -ports "eth1 eth2"\ -ip_addr "$ts_eth1 $ts_eth2"\ -mask "/18"\ -ip_num 1]

Return: {status 1}

lsh::dmf_config

Name: lsh::dmf_config

Purpose: Creates and modifies the Data Message Flow (DMF) with Landslide HLAPI. The DMF created is saved in the TAS, and can be called in the test case configuration directly.

Synopsis: lsh::dmf_config -mode {create|modify} -dmf_hnd <ANY> -lib <ANY> -name <ANY> -description <ANY> -keywords <ANY> -data_protocol {ping|raw|udp|tcp|sctp|http|https|ftp|tftp|smtp|pop3| imap |rtcp|rtp|sip|mms|rtsp|wsp|wv|cust} -under_layer_protocol {none|udp|tcp|sctp|http|wtp|tls|raw} -start_pause {true|false} -total_reties <0-9999999999999> -data_res_time <3000-2000000000> -connect_only {true|false} -persistent_connection {true|false} -transactions {continuous|limited} -transactions_num <0-9999999999999> -transaction_rate <1.0-99999999999.9> -packet_size <4-65535> -host_data_expansion_ratio <1-10> -distr_trans_interval_dist {Fixed|Uniform|Normal|Poisson} -distr_max_interval_deviation <1-99> -distr_standard_interval_deviation <0-100> -distr_packet_size_dist {Fixed|Uniform|Normal|Poisson} -distr_max_size_deviation <1-99> -distr_standard_size_deviation <0-100> -billing_include_syn_en {true|false} -billing_include_sub_flow_en {true|false} -billing_generate_record_en {true|false}

Common Functions

29

-client_port_mode {Fixed|Random|Sequential_Range| Sequential_with_Random_Start} -client_port <0-65535> -client_port_min <0-65534> -client_port_max <1-65535> -server_port <0-65535> -tcp_push {true|false} -slow_start {true|false} -initing_side {Client|Server} -socket_init_side {Client|Server} -socket_disc_side {Client|Server} -disconnect_type {FIN|RST} -force_3way_handshake_en {true|false} -tcp_sctp_retrans_timer {dynamic_algorithm|fixed_retry} -fixed_retry_time <100-30000> -window_size <2000-1073741824> -window_scalling_en {true|false} -window_scalling_factor <0-14> -max_segment_size <0-9250> -vtag_mask <HEX> -vtag_value <HEX> -payload_protocol_id <0-4294967295> -tos <0-255> -ttl <1-255> -protocol_id <0-255> -segment_size <64-65535> -dmf_from_tdf_en {true|false} -no_fin_ack_wait -tdf_lib <ANY> -tdf_name <ANY> -paste_buffer1_name <ANY> -paste_buffer1_size <0-4095> -paste_buffer1_initial_value <ANY> -paste_buffer2_name <ANY> -paste_buffer2_size <0-4095> -paste_buffer2_initial_value <ANY> -paste_buffer3_name <ANY> -paste_buffer3_size <0-4095> -paste_buffer3_initial_value <ANY> -paste_buffer4_name <ANY> -paste_buffer4_size <0-4095> -paste_buffer4_initial_value <ANY> -paste_buffer5_name <ANY> -paste_buffer5_size <0-4095> -paste_buffer5_initial_value <ANY> -paste_buffer6_name <ANY> -paste_buffer6_size <0-4095> -paste_buffer6_initial_value <ANY> -paste_buffer7_name <ANY> -paste_buffer7_size <0-4095> -paste_buffer7_initial_value <ANY> -paste_buffer8_name <ANY> -paste_buffer8_size <0-4095> -paste_buffer8_initial_value <ANY> -paste_buffer9_name <ANY> -paste_buffer9_size <0-4095> -paste_buffer9_initial_value <ANY> -paste_buffer10_name <ANY> -paste_buffer10_size <0-4095> -paste_buffer10_initial_value <ANY> -security_ims_aka_en {true|false} -security_http_digest_en {true|false} -security_aka_version {1|2} -security_algorithm {md5|md5-sess} -security_secret_key <HEX> -security_password <HEX> -security_operator_variant <HEX> -security_aka_in_ipsec_en {true|false} -security_digest_uri <ANY> -security_cnonce <ANY> -security_nonce_count <0-999999999999999999>

Common Functions

30

-security_fixed_rand_en {true|false} -security_fixed_rand <HEX> -security_fixed_nonce_en {true|false} -security_fixed_nonce <HEX> -subflows_lib <ANY> -subflows_name <ANY> -active_until_subflows_complete {true|false} -stop_on_error {true|false} -tls_cert_tdf_lib <ANY> -tls_cert_tdf_name <ANY> -tls_sslv2_en {true|false} -tls_sslv3_en {true|false} -tls_tlsv1_en {true|false} -tls_ciphers_adh_aes128_sha {true|false} -tls_ciphers_adh_aes256_sha {true|false} -tls_ciphers_adh_des_cbc_sha {true|false} -tls_ciphers_adh_des_cbc3_sha {true|false} -tls_ciphers_adh_rc4_md5 {true|false} -tls_ciphers_aes_128_sha {true|false} -tls_ciphers_aes_256_sha {true|false} -tls_ciphers_des_cbc_md5 {true|false} -tls_ciphers_des_cbc_sha {true|false} -tls_ciphers_des_cbc3_md5 {true|false} -tls_ciphers_des_cbc3_sha {true|false} -tls_ciphers_dhe_dss_aes128_sha {true|false} -tls_ciphers_dhe_dss_aes256_sha {true|false} -tls_ciphers_dhe_dss_rc4_sha {true|false} -tls_ciphers_dhe_rsa_aes128_sha {true|false} -tls_ciphers_dhe_rsa_aes256_sha {true|false} -tls_ciphers_edh_dss_des_cbc_sha {true|false} -tls_ciphers_edh_dss_des_cbc3_sha {true|false} -tls_ciphers_edh_rsa_des_cbc_sha {true|false} -tls_ciphers_edh_rsa_des_cbc3_sha {true|false} -tls_ciphers_exp_adh_des_cbc_sha {true|false} -tls_ciphers_exp_adh_rc4_md5 {true|false} -tls_ciphers_exp_des_cbc_sha {true|false} -tls_ciphers_exp_edh_dss_des_cbc_sha {true|false} -tls_ciphers_exp_edh_dss_rsa_cbc_sha {true|false} -tls_ciphers_exp_rc2_cbc_md5 {true|false} -tls_ciphers_exp_rc4_md5 {true|false} -tls_ciphers_exp1024_des_cbc_sha {true|false} -tls_ciphers_exp1024_dhe_dss_des_cbc_sha {true|false} -tls_ciphers_exp1024_dhe_dss_rc4_sha {true|false} -tls_ciphers_exp1024_rc2_cbc_md5 {true|false} -tls_ciphers_exp1024_rc4_md5 {true|false} -tls_ciphers_exp1024_rc4_sha {true|false} -tls_ciphers_idea_cbc_md5 {true|false} -tls_ciphers_idea_cbc_sha {true|false} -tls_ciphers_null_md5 {true|false} -tls_ciphers_null_sha {true|false} -tls_ciphers_rc2_cbc_md5 {true|false} -tls_ciphers_rc4_64_md5 {true|false} -tls_ciphers_rc4_md5 {true|false} -tls_ciphers_rc4_sha {true|false} -window_scaling_factor <0-14>

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - Creates a new DMF and configure the parameters in the DMF, save the DMF to the library specified in the -lib

modify - modify the parameters in the DMF specified by -dmf_hnd.

-dmf_hnd Specifies the handle of the DMF. This argument is mandatory when the -mode is set to modify.

Common Functions

31

-lib Specifies the library of the DMF stored. It can be either library on the TAS. Default: sms -name The name of the DMF -description Description of the DMF -keywords The keywords can be given for the DMF created or will be modified. Default: -data_protocol The protocol to be used in the message flow. Possible values: ping, raw, udp, tcp, sctp, http, https, ftp, tftp, smtp, pop3, imap , rtcp, rtp, sip, mms, rtsp, wsp, wv, or cust. Note: The availability of a protocol depends on whether the test system is licensed for this protocol. Default: ping -under_layer_protocol When an Advanced Data Protocol can run over different transport protocols, you can choose which will be used. The possible value of under_layer_protocol is none - when the protocol is ping, raw, udp, tcp, sctp, http, https, ftp, tftp, smtp, pop3 or imap. udp - rtcp, rtp, sip, mms, rtsp, wsp, wv or cust. tcp - tcp, rtp, sip, rtsp or cust. sctp -tcp, rtp, sip, rtsp or cust. wtp - mms, wsp or wv http - mms or wv. tls -cust. raw -cust. Default: none -start_pause Determine whether to enable to start the Mainflow DMFs in the paused state or not. If it is true you can start the mainflow DMF when it is in the paused state. Default: false -total_reties The maximum number of attempts made by the client or server to send a request message after the Data Response Time has expired. Default: 0 Range: 0-9999999999999 Dependency: data_protocol is http, https, ftp, tftp, smtp, pop3, imap, rtcp, rtp, sip, mms, rtsp, wsp, wv, or cust. -data_res_time The number of milliseconds to wait for a response from the other end. Default: 60000 Range: 3000-2000000000 Dependency: data_protocol is http, https, ftp, tftp, smtp, pop3, imap, rtcp, rtp, sip, mms, rtsp, wsp, wv or cust -connect_only Enables or disables option to open socket and close without traffic (TCP/SCTP only). If it is true, only the messages associated with socket establishment and tear down would be seen for each transaction. Default: false Dependency: data_protocol tcp|sctp -persistent_connection When an Advanced Data protocol runs over TCP or SCTP and supports non-persistent connections, you can control whether the connection is maintained for the duration of the message flow execution with this

Common Functions

32

argument. When it is true, the connection is established when the message flow begins, and is maintained through all iterations of the message flow until the final message is received. When it is faslse, the connection is established and then disconnected for each iteration of the message flow. Default: false -transactions Defines the type of the transaction executed after data traffic begins. Possible Values: continuous, limited Default: continuous -transactions_num Defines the number of times a transaction is executed after data traffic begins. Default: 0 Range: 0-9999999999999 Dependency: -transactions is limited -transaction_rate Specifies the number of times the test will attempt to execute the transaction every second in each of the MN sessions Default: 1.0 Range: 1.0-99999999999.9 -packet_size Default: 64 Range: 4-65535 Dependency: data_protocol is ping, raw, udp, tcp, sctp when the data_protocol is tcp or sctp, the connect_only should be true at the time -host_data_expansion_ratio Use this together with transaction_rate and packet_size to calculate the totoal throughput. Default: 1 Range: 1-10 Dependency: data_protocol is ping, raw, udp, tcp, sctp when the data_protocol is tcp or sctp, the connect_only should be true at the time -distr_trans_interval_dist Default: Fixed -distr_max_interval_deviation Default: 10 Range: 1-99 Dependency: distr_trans_interval_dist Uniform|Poisson -distr_standard_interval_deviation Default: 10 Range: 0-100 Dependency: distr_trans_interval_dist Normal -distr_packet_size_dist Default: Fixed Dependency: data_protocol is ping, raw, udp, tcp, sctp when the data_protocol is tcp or sctp, the connect_only should be true at the time -distr_max_size_deviation Default: 10 Range: 1-99 Dependency: distr_packet_size_dist Uniform|Poisson -distr_standard_size_deviation Default: 10 Range: 0-100 Dependency: distr_packet_size_dist Normal -billing_include_syn_en Determine whether to include the SYN, SYN/ACK, and ACK in the per-flow attribute values. Default: false Dependency: data_protocol ping, raw, udp, tcp, sctp, http, https,

Common Functions

33

ftp, tftp, smtp, pop3, imap, rtcp, rtp, sip, mms, rtsp, wsp, wv or cust -billing_include_sub_flow_en Determine to include the subflow in the mainflow or not Default: false Dependency: data_protocol ping, raw, udp, tcp, sctp, http, https, ftp, tftp, smtp, pop3, imap, rtcp, rtp, sip, mms, rtsp, wsp, wv or cust -billing_generate_record_en Determine to generate a separate S-LDR for each DMF transaction or not Default: false Dependency: data_protocol ping, raw, udp, tcp, sctp, http, https, ftp, tftp, smtp, pop3, imap, rtcp, rtp, sip, mms, rtsp, wsp, wv or cust -client_port_mode Choose one client port mode. Possible value: Fixed, Random, Sequential_Range, Sequential_with_Random_Start Default: Fixed Dependency: data_protocol udp|tcp|sctp|http|https|ftp|tftp| smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust &under_layer_protocol none|udp|tcp|sctp|http|wtp|tls -client_port The port to be used with the MS's IP address for the selected data protocol Default: 2004 Range: 0-65535 Dependency: client_port_mode Fixed|Sequential_Range -client_port_min The minimum of the client port Default: 49152 Range: 0-65534 Dependency: client_port_mode Sequential_Range| Sequential_with_Random_Start -client_port_max The maximum of the client port. Default: 49152 Range: 1-65535 Dependency: client_port_mode Sequential_Range |Sequential_with_Random_Start -server_port The port to be used with the Network Host's IP address for the selected data protocol. Default: 2005 Range: 0-65535 Dependency: data_protocol udp|tcp|sctp|http|https|ftp|tftp |smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust &under_layer_protocol none|udp|tcp|sctp|http|wtp|tls -tcp_push Determines whether to simulate TCP Push procedure or not. Possible Values: true, false Default: false Dependency: data_protocol tcp|sctp|http|https|ftp|smtp|pop3 |imap|rtcp|rtp|sip|mms|rtsp|wv|cust & under_layer_protocol none|tcp|http|sctp|tls -no_fin_ack_wait Determines whether to enable the No Fin/ACK wait. Possible Values: true or false Default: fasle Dependency: data_protocol tcp|sctp|http|https|ftp|smtp|pop3 |imap|rtcp|rtp|sip|mms|rtsp|wv|cust| &under_layer_protocolnone|cp|http|sctp|tls

-slow_start Enables or disables the three features (Slow Start feature, Congestion Avoidance feature, Fast Retransmit feature)

Common Functions

34

Possible Values: true, false Default: false Dependency: data_protocol tcp|sctp|http|https|ftp|smtp|pop3 |imap|rtcp|rtp|sip|mms|rtsp|wv|cust &under_layer_protocol none|tcp|http|sctp|tls -initing_side Determines which entity sends the first packet. Either Client or Server side may start the subflow with any of the Basic Data protocols. Default: Client Dependency: data_protocol ping|raw|udp|tcp|sctp -socket_init_side Use this to determine which entity will initiates the TCP connection. Default: Client Dependency: data_protocol ftp|tftp|rtcp|rtp|cust -socket_disc_side Use this to determine which entity tears down a TCP connection Default: Client Dependency: data_protocol http|https|ftp|smtp|pop3 |imap|rtcp|rtp|sip|mms|rtsp|wv|cust &under_layer_protocol none|tcp|http|sctp|tls -disconnect_type Specifies in which type the TCP socket will be torn down, whether by sending a FIN and waiting for a FIN ACK or by sending a RST to the other TCP Default: FIN Dependency: data_protocol tcp|sctp|http|https|ftp|smtp|pop3 |imap|rtcp|rtp|sip|mms|rtsp|wv|cust &under_layer_protocol none|tcp|http|sctp|tls -force_3way_handshake_en When the Data Protocol runs over TCP or SCTP, you can control whether the connection is considered established with a SYN/ACK from the Network Host with -force_3way_handshake_en. When-force_3way_handshake_en is false, the connection is considered established, and data transmission by the application layer can begin, when the SYN/ACK is received by the MN. When -force_3way_handshake_en is true, the connection is not considered established, and data transmission by the application layer cannot begin, until the confirming ACK is received by the Network Host. Default: false Dependency: data_protocol http|https|ftp|smtp|pop3|imap |rtcp|rtp|sip|mms|rtsp|wv|cust &under_layer_protocol none|tcp|http|sctp|tls -tcp_sctp_retrans_timer Define the retry time with TCP/SCTP Retransmission Timer, the possible value of it are: dynamic_algorithm or fixed_retry. When it is fixed_retry, you can specify the number of the milliseconds for the timer with specifying -fixed_retry_time Default: dynamic_algorithm Dependency: data_protocol tcp|sctp|http|https|ftp|smtp |pop3|imap|rtcp|rtp|sip|mms|rtsp|wv|cust &under_layer_protocol none|tcp|http|sctp|tls -fixed_retry_time Specifies the number of the milliseconds for the timer Default: 3000 Range: 100-30000 Dependency: tcp_sctp_retrans_timer fixed_retry -window_size The TCP Window Size controls the flow of data, For more efficient use of high bandwidth networks, a larger TCP window size may be used. Default: 32768 Range: 2000-1073741824 Dependency: data_protocol tcp|sctp|http|https|ftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wv|cust

Common Functions

35

&under_layer_protocol none|tcp|http|sctp|tls -window_scalling_en Determine if the TCP window can be scaled to a larger size. Default: false Dependency: data_protocol tcp|sctp|http|https|ftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wv|cust &under_layer_protocol none|tcp|http|sctp|tls -window_scalling_factor The value communicates a Scale Factor to be applied to TCP received window. Default: -1 Range: 0-14 Dependency: window_scalling_en true -max_segment_size Specifies the maximum amount of data that a segment can hold. The maximum segment size (MSS) is the largest amount of data, specified in bytes, that your communications device can handle in a single unfragmented data packet. MSS does not include the TCP headers. Range: 0-9250 Default: 0 Dependency: data_protocol tcp|http|https|ftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wv|cust &under_layer_protocolnone|tcp|http|tls -vtag_mask VTAG MASK is a 32-bit field that identifies how much of the field will be determined by the "Value" field. Default: 0x0 Dependency: data_protocol sctp|rtcp|rtp|sip|rtsp|cust&under_layer_protocol none|sctp -vtag_value Indicates the actual value that will be set for an emulated destination server. Default: 0x0 Dependency: data_protocol sctp|rtcp|rtp|sip|rtsp|cust&under_layer_protocol none|sctp -payload_protocol_id The Payload Protocol ID is only available when the Data Protocol is SCTP or Custom and the Underlying Layer is SCTP (for Custom Data Protocol). This allows you to manually set the Payload Protocol ID when selecting DMF protocol as SCTP. Default: 0 Range: 0-4294967295 Dependency: data_protocol sctp|rtcp|rtp|sip|rtsp|cust&under_layer_protocol none|sctp -tos Type of Service defines the requested quality of service at the IP layer for the data packets. It uses an 8 bit QOS indicator formatted as follows: Bits 0-2: Precedence 111 = Network Control 110 = Inter-network Control 101 = CRITIC/ECP 100 = Flash Override 011 = Flash 010 = Immediate 000 = Routine

Common Functions

36

Bit 3: Delay (0 = normal, 1 = low) Bit 4: Throughput (0 = normal, 1 = high) Bit 5: Reliability (0 = normal, 1 = high) Bits 6-7: Reserved for future use Default: 0 Range: 0-255 -ttl The number of hops that a datagram may take in its path to a destination. This value is decremented by each module that processes the datagram. When the value reaches zero, the datagram is discarded. Default: 64 Range: 1-255 -protocol_id The Protocol ID indicates the IP Layer Protocol used Default: 255 Range: 0-255 Dependency: under_layer_protocol raw -segment_size When you use any protocol, you can define the maximum number of payload bytes in each packet. If the number of bytes in a message is larger than Segment Size, the message will be divided into the number of messages required to meet the threshold. Default: 1000 Range: 64-65535 -dmf_from_tdf_en Determine if the explicit values for each DMF is get from Test Data File. Default: false -tdf_lib If the explicit values for each DMF is get from Test Data File, specify the lib of the Test Data File. Default: sms Dependency: dmf_from_tdf_en true -tdf_name If the explicit values for each DMF is get from Test Data File, specify the name of the Test Data File. Default: Dependency: dmf_from_tdf_en true -paste_buffer1_name The name of buffer1. Default: Buffer_1 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer1_size The size of buffer1. Default: 0 Range: 0-4095 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer1_initial_value The initial value of buffer1. Default: Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer2_name Default: Buffer_2 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust

Common Functions

37

-paste_buffer2_size Default: 0 Range: 0-4095 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer2_initial_value Default: Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer3_name Default: Buffer_3 Dependency: data_protocol http|https|ftp|tftp |smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer3_size Default: 0 Range: 0-4095 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer3_initial_value Default: Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer4_name Default: Buffer_4 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer4_size Default: 0 Range: 0-4095 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer4_initial_value Default: Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer5_name Default: Buffer_5 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer5_size Default: 0 Range: 0-4095 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer5_initial_value Default: Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer6_name Default: Buffer_6 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer6_size Default: 0 Range: 0-4095 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer6_initial_value

Common Functions

38

Default: Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer7_name Default: Buffer_7 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer7_size Default: 0 Range: 0-4095 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer7_initial_value Default: Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer8_name Default: Buffer_8 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer8_size Default: 0 Range: 0-4095 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer8_initial_value Default: Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer9_name Default: Buffer_9 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer9_size Default: 0 Range: 0-4095 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer9_initial_value Default: Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer10_name Default: Buffer_10 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer10_size Default: 0 Range: 0-4095 Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -paste_buffer10_initial_value Default: Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -security_ims_aka_en Enable IMS AKA authentication in DMF. Default: false

Common Functions

39

Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -security_http_digest_en Enable HTTP Digest authentication in DMF. Default: false Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -security_aka_version The verson of the AKA. Default: 1 Dependency: security_ims_aka_en true -security_algorithm The algorithm used to calculate authentication credentials for IMS AKA or HTTP Digest. Default: md5 Dependency: security_ims_aka_en true,security_http_digest_en true -security_secret_key The key associated with the MN's IMS private identity. The MN and the HSS both maintain this key and the HSS informs the S-CSCF of an MN's private key during the registration process. Default: 0x00 Dependency: security_ims_aka_en true -security_password The MN's HTTP Digest password. Default: 0x00 Dependency: security_http_digest_en true -security_operator_variant The 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Default: 0x63BFA50EE6523365FF14C1F45F88737D Dependency: security_ims_aka_en true -security_aka_in_ipsec_en Determine if the AKA will be used in the IPSec Default: false Dependency: security_ims_aka_en true -security_digest_uri The URI of the authenticating server Dependency: security_ims_aka_en true,security_http_digest_en true -security_cnonce The Client Nonce is transmitted in the client's authentication response and is used by both the client and server for mutual authentication and message integrity protection. Dependency: security_ims_aka_en true,security_http_digest_en true -security_nonce_count The number of times the client has transmitted the same CNonce. Range: 0-999999999999999999 Dependency: security_ims_aka_en true,security_http_digest_en true -security_fixed_rand_en Determine if the static RAND will be sent in every IMS AKA challenge. Default: false Dependency: security_ims_aka_en true -security_fixed_rand The static RAND will be sent in every IMS AKA challenge. Default: 0x00000000000000000000000000000001 Dependency: security_ims_aka_en true -security_fixed_nonce_en Determine if the static Nonce that will be sent in every HTTP Digest challenge.

Common Functions

40

Default: false Dependency: security_http_digest_en true -security_fixed_nonce The static Nonce that will be sent in every HTTP Digest challenge. Default: 0x00000000000000000000000000000001 Dependency: security_http_digest_en true -subflows_lib The library of the subflow located. Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -subflows_name The name of the subflow. Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -active_until_subflows_complete Ensure that the main DMF flow remains active until the subflows complete (are active). Default: false Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -stop_on_error enables you to direct the DMF to stop executing in any MN session when a transaction fails to complete due to a socket error. Default: false Dependency: data_protocol http|https|ftp|tftp|smtp|pop3|imap|rtcp|rtp|sip|mms|rtsp|wsp|wv|cust -tls_cert_tdf_lib The library of the Certificate File TDF located. Dependency: data_protocol https,under_layer_protocol tls -tls_cert_tdf_name The name of the Certificate File TDF located. Dependency: data_protocol https,under_layer_protocol tls -tls_sslv2_en Enable the SSL version SSLv2. Default: flase Dependency: data_protocol https,under_layer_protocol tls -tls_sslv3_en Enable the SSL version SSLv3. Default: false Dependency: data_protocol https,under_layer_protocol tls -tls_tlsv1_en Enable the SSL version TLSv1. Default: false Dependency: data_protocol https,under_layer_protocol tls -tls_ciphers_adh_aes128_sha Select the ciphers ADH-AES128-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_adh_aes256_sha Select the ciphers ADH-AES256-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_adh_des_cbc_sha ADH-DES-CBC-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_adh_des_cbc3_sha

Common Functions

41

ADH-DES-CBC3-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_adh_rc4_md5 ADH-RC4-MD5 Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_aes_128_sha AES-128-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_aes_256_sha AES-256-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_des_cbc_md5 DES-CBC-MD5 Default: false Dependency: tls_sslv2_en true -tls_ciphers_des_cbc_sha DES-CBC-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_des_cbc3_md5 DES-CBC3-MD5 Default: false Dependency: tls_sslv2_en true -tls_ciphers_des_cbc3_sha DES-CBC3-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_dhe_dss_aes128_sha DHE-DSS-AES128-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_dhe_dss_aes256_sha DHE-DSS-AES256-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_dhe_dss_rc4_sha DHE-DSS-RC4-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_dhe_rsa_aes128_sha DHE-RSA-AES128-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_dhe_rsa_aes256_sha DHE-RSA-AES256-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_edh_dss_des_cbc_sha EDH-DSS-DES-CBC-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_edh_dss_des_cbc3_sha EDH-DSS-DES-CBC3-SHA

Common Functions

42

Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_edh_rsa_des_cbc_sha EDH-RSA-DES-CBC-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_edh_rsa_des_cbc3_sha EDH-RSA-DES-CBC3-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_exp_adh_des_cbc_sha EXP-ADH-DES-CBC-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_exp_adh_rc4_md5 EXP-ADH-RC4-MD5 Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_exp_des_cbc_sha EXP-DES-CBC-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_exp_edh_dss_des_cbc_sha EXP-EDH-DSS-DES-CBC-SHA Default: false Dependency: tls_tlsv1_en true, tls_sslv3_en true -tls_ciphers_exp_edh_dss_rsa_cbc_sha EXP-EDH-DSS-RSA-CBC-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_exp_rc2_cbc_md5 EXP-RC2-CBC-MD5 Default: false Dependency: tls_tlsv1_en true,tls_sslv2_en true -tls_ciphers_exp_rc4_md5 EXP-RC4-MD5 Default: false Dependency: tls_tlsv1_en true,tls_sslv2_en true,tls_sslv3_en true -tls_ciphers_exp1024_des_cbc_sha EXP1024-DES-CBC-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_exp1024_dhe_dss_des_cbc_sha EXP1024-DHE-DSS-DES-CBC-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_exp1024_dhe_dss_rc4_sha EXP1024-DHE-DSS-RC4-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_exp1024_rc2_cbc_md5 EXP1024-RC2-CBC-MD5 Default: false Dependency: tls_tlsv1_en true -tls_ciphers_exp1024_rc4_md5 EXP1024-RC4-MD5 Default: false

Common Functions

43

Dependency: tls_tlsv1_en true -tls_ciphers_exp1024_rc4_sha EXP1024-RC4-SHA Default: false Dependency: tls_tlsv1_en true -tls_ciphers_idea_cbc_md5 IDEA-CBC-MD5 Default: false Dependency: tls_sslv2_en true -tls_ciphers_idea_cbc_sha IDEA-CBC-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_null_md5 NULL-MD5 Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_null_sha NULL-SHA Default: false Dependency: tls_tlsv1_en true,tls_sslv3_en true -tls_ciphers_rc2_cbc_md5 RC2-CBC-MD5 Default: false Dependency: tls_sslv2_en true -tls_ciphers_rc4_64_md5 RC4-64-MD5 Default: false Dependency: tls_sslv2_en true -tls_ciphers_rc4_md5 RC4-MD5 Default: false Dependency: tls_tlsv1_en true,tls_sslv2_en true,tls_sslv3_en true -tls_ciphers_rc4_sha RC4-SHA Default: false Dependency: tls_tlsv1_en true -window_scaling_factor Specifies the Scale Factor to be applied to TCP received window. Range: 0-14 Default: 0 Dependency: window_scaling_en true

Return Values dmf_handle The DMF handle, which will be used when you want to modify the DMF, or configure more parameters on this DMF. Will be returned only when the status is 1 and the -mode is create. status Success (1) or failure (0) of the operation

log Returned only when the status is 0

Examples: set ret [::lsh::dmf_config \ -mode create \ -lib nana\ -name dmf_from_script_https\ -data_protocol https\ -start_pause true\ -total_reties 44\ -data_res_time 7777\

Common Functions

44

-persistent_connection true\ -transactions limited\ -transactions_num 1\ -transaction_rate 2.0\ -distr_trans_interval_dist Poisson\ -distr_max_interval_deviation 20\ -billing_include_syn_en true\ -billing_include_sub_flow_en true\ -billing_generate_record_en true\ -client_port_mode Random\ -server_port 3333\ -tcp_push true\ -slow_start true\ -socket_disc_side Server\ -disconnect_type FIN\ -force_3way_handshake_en true\ -tcp_sctp_retrans_timer fixed_retry\ -fixed_retry_time 3333\ -window_size 11111\ -window_scalling_en true\ -max_segment_size 99\ -tos 4\ -ttl 60\ -segment_size 999\ -paste_buffer1_name https_Buffer_1\ -paste_buffer1_size 11\ -paste_buffer1_initial_value 1\ -paste_buffer2_name https_Buffer_2\ -paste_buffer2_size 12\ -paste_buffer2_initial_value 2\ -paste_buffer3_name https_Buffer_3\ -paste_buffer3_size 13\ -paste_buffer3_initial_value 3\ -paste_buffer4_name https_Buffer_4\ -paste_buffer4_size 14\ -paste_buffer4_initial_value 4\ -paste_buffer5_name https_Buffer_5\ -paste_buffer5_size 14\ -paste_buffer5_initial_value 5\ -paste_buffer6_name https_Buffer_6\ -paste_buffer6_size 16\ -paste_buffer6_initial_value 6\ -paste_buffer7_name https_Buffer_7\ -paste_buffer7_size 17\ -paste_buffer7_initial_value 7\ -paste_buffer8_name https_Buffer_8\ -paste_buffer8_size 18\ -paste_buffer8_initial_value 8\ -paste_buffer9_name https_Buffer_9\ -paste_buffer9_size 19\ -paste_buffer9_initial_value 9\ -paste_buffer10_name https_Buffer_10\ -paste_buffer10_size 20\ -paste_buffer10_initial_value 10\ -security_ims_aka_en true\ -security_aka_version 2\ -security_algorithm md5-sess\ -security_secret_key 0x11\ -security_operator_variant 0x444444444\ -security_aka_in_ipsec_en true\ -security_digest_uri abcd\ -security_cnonce efg\ -security_nonce_count 666\ -security_fixed_rand_en true\ -security_fixed_rand 0x1111111111111\ -tls_cert_tdf_lib sms\ -tls_cert_tdf_name temp.tdf\ -tls_sslv2_en true\ -tls_ciphers_des_cbc_md5 true\ -tls_ciphers_des_cbc3_md5 true]

Common Functions

45

keylget ret dmf_handle dmf_https

lsh::dmf_control_config

Name: lsh::dmf_control_config

Purpose: Used to configure the message flow controls.

Synopsis: lsh::dmf_control_config -mode {create|modify} -dmf_hnd <ANY> -cmd_hnd <ANY> -control_type {command|transaction|event_send|event_wait} -command_apply_to {Both|Client|Server} -command_apply_to_client {true|false} -command_client_msg_type {None|Request|Response} -command_client_wait_resp_en {true|false} -command_client_msg_filter_data {None|Automatic|tdf} -command_client_msg_filter_offset <NUMERIC> -command_client_msg_padded_size <0-1000000> -command_client_msg_tdf_lib <ANY> -command_client_msg_tdf_name <ANY> -command_client_msg_inc_all_data_en {true|false} -command_client_msg_verify_message_en {true|false} -command_client_msg_first_byte_to_check <NUMERIC> -command_client_msg_num_bytes_to_check <NUMERIC> -command_client_msg_send_delay <0-2000000000> -command_server_msg_type {None|Request|Response} -command_server_wait_resp_en {true|false} -command_server_msg_filter_data {None|Automatic|tdf} -command_server_msg_filter_offset <NUMERIC> -command_server_msg_padded_size <0-1000000> -command_server_msg_tdf_lib <ANY> -command_server_msg_tdf_name <ANY> -command_server_msg_inc_all_data_en {true|false} -command_server_msg_verify_message_en {true|false} -command_server_msg_first_byte_to_check <NUMERIC> -command_server_num_bytes_to_check <NUMERIC> -command_server_msg_send_delay <0-2000000000> -event_send_apply_to {Both|Client|Server} -event_send_target <ANY> -event_send_event {SUBFLOW_START|SUBFLOW_STOP|TRANS_START |TRANS_COMPLETE|RESTART_SOCKET |USER_DEFINED_EVENT_1|USER_DEFINED_EVENT_2 |USER_DEFINED_EVENT_3|USER_DEFINED_EVENT_4 |USER_DEFINED_EVENT_5|USER_DEFINED_EVENT_6| USER_DEFINED_EVENT_7|USER_DEFINED_EVENT_8| USER_DEFINED_EVENT_9|USER_DEFINED_EVENT_10| SOCKET_OPEN|GOTO_COMMAND|IPSEC_TUNNEL_1_START| IPSEC_TUNNEL_2_START|IPSEC_TUNNEL_3_START| IPSEC_TUNNEL_4_START|IPSEC_TUNNEL_1_STOP| IPSEC_TUNNEL_2_STOP|IPSEC_TUNNEL_3_STOP|IPSEC_TUNNEL_4_STOP |EXECUTE_AKA|SOCKET_CLOSE} -event_wait_apply_to {Both|Client|Server} -event_wait_source <ANY> -event_wait_event {SUBFLOW_START|SUBFLOW_STOP|TRANS_START| TRANS_COMPLETE|RESTART_SOCKET|USER_DEFINED_EVENT_1| USER_DEFINED_EVENT_2|USER_DEFINED_EVENT_3| USER_DEFINED_EVENT_4|USER_DEFINED_EVENT_5| USER_DEFINED_EVENT_6|USER_DEFINED_EVENT_7| USER_DEFINED_EVENT_8|USER_DEFINED_EVENT_9| USER_DEFINED_EVENT_10|SOCKET_OPEN|GOTO_COMMAND| IPSEC_TUNNEL_1_START|IPSEC_TUNNEL_2_START| IPSEC_TUNNEL_3_START|IPSEC_TUNNEL_4_START|

Common Functions

46

IPSEC_TUNNEL_1_STOP|IPSEC_TUNNEL_2_STOP| IPSEC_TUNNEL_3_STOP|IPSEC_TUNNEL_4_STOP| EXECUTE_AKA|SOCKET_CLOSE} -transaction_start <NUMERIC> -transaction_end <NUMERIC>

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - create a new message control command on the specified DMF handle. modify - modify the parameters on message control command on the specified message control command. -dmf_hnd The handle of the DMF. it is mandatory when the mode is create. -cmd_hnd The handle of the message control command. It is mandatory when the mode is modify. -control_type The type of the controls in the message flow. Possible values are: command, transaction, event_send , event_wait. It is mandatory. -command_apply_to When the control type is command, specify which side the command will be applied to. Possible value are: Both, Client, Server Default: Both Dependency: control_type command -command_client_msg_type When the control type is command, specify the message type on the client side. Default: None Dependency: command_apply_to Both|Client -command_client_wait_resp_en When the control type is command, specify whether to force the flow to wait until a certain message is received by either the Client or the Server. Default: false Dependency: command_client_msg_type None|Request -command_client_msg_filler_data The filler type of the data in the Request or response message. Possible value are: None, Automatic, tdf Default: None Dependency: command_apply_to Both|Client -command_client_msg_filter_offset If the filler data included, determine the offset of the filler Default: 0 Dependency: command_client_msg_filler_data Automatic|tdf -command_client_msg_padded_size If the filler data included, specify the padded message size. Default: 0 Range: 0-1000000 Dependency: command_client_msg_filler_data Automatic -command_client_msg_tdf_lib If the filler data is defined in the test data file, specify the library that the tdf stored. Dependency: command_client_msg_filler_data tdf -command_client_msg_tdf_name

Common Functions

47

If the filler data is defined in the test data file, specify the nameof the tdf. Dependency: command_client_msg_filler_data tdf -command_client_msg_inc_all_data_en Determine if all data will be included as header in every segment before filler start. Default: false Dependency: command_client_msg_filler_data Automatic|tdf -command_client_msg_verify_message_en Determine whether to verify the message after the receiving end. Default: false Dependency: command_apply_to Both|Client -command_client_msg_first_byte_to_check If the message will be verified after the receiving end, specify the first byte to be check. Default: 0 Dependency: command_client_msg_verify_message_en true -command_client_msg_num_bytes_to_check If the message will be verified after the receiving end, specify the number of byte to be check. Default: 0 Dependency: command_client_msg_verify_message_en true -command_client_msg_send_delay Specifies the send delay time of the massage. Default: 0 Range: 0-2000000000 Dependency: command_apply_to Both|Client -command_server_msg_type When the control type is command, specify the message type on the client side. Default: None Dependency: command_apply_to Both|Server -command_server_wait_resp_en When the control type is command, specify whether to force the flow to wait until a certain message is received by either the Client or the Server Default: false Dependency: command_server_msg_type None|Request -command_server_msg_filler_data The filler type of the data in the Request or response message. Possible value are: None, Automatic, tdf Default: None Dependency: command_apply_to Both|Server -command_server_msg_filler_offset If the filler data included, determine the offset of the filler Default: 0 Dependency: command_server_msg_filler_data Automatic|tdf -command_server_msg_padded_size If the filler data included, specify the padded message size Default: 0 Range: 0-1000000 Dependency: command_server_msg_filler_data Automatic -command_server_msg_tdf_lib If the filler data is defined in the test data file, specify the library that the tdf stored Dependency: command_server_msg_filler_data tdf -command_server_msg_tdf_name If the filler data is defined in the test data file, specify the nameof the tdf.

Common Functions

48

Default: Dependency: command_server_msg_filler_data tdf -command_server_msg_inc_all_data_en Determine if all data will be included as header in every segment before filler start. Default: false Dependency: command_server_msg_filler_data Automatic|tdf -command_server_msg_verify_message_en Determine whether to verify the message after the receiving end. Default: false Dependency: command_apply_to Both|Client -command_server_msg_first_byte_to_check If the message will be verified after the receiving end, specify the first byte to be check Default: 0 Dependency: command_server_msg_verify_message_en true -command_server_num_bytes_to_check If the message will be verified after the receiving end, specify the number of byte to be check. Default: 0 Dependency: command_server_msg_verify_message_en true -command_server_msg_send_delay Specifies the send delay time of the massage Default: 0 Range: 0-2000000000 Dependency: command_apply_to Both|Server -event_send_apply_to When the control type is event_send, specify where the control will be applied to Default: Both Dependency: control_type event_send -event_send_target When the control type is event_send, specify target where the event will be sent Dependency: control_type event_send -event_send_event When the control type is event_send, specify the type of the event Default: TRANS_START Dependency: control_type event_wait -event_wait_apply_to When the control type is event_wait, specify where the control will be applied to Default: Both Dependency: control_type event_wait -event_wait_source When the control type is event_wait, specify the source where the event it sent from. Dependency: control_type event_wait -event_send_event When the control type is event_wait, specify the type of the event Default: TRANS_START Dependency: control_type event_wait -transaction_start When the control type transaction, specify where to put the transaction start Default: 0 Dependency: control_type transaction -transaction_end

Common Functions

49

When the control type transaction, specify where to put the transaction stop Dependency: control_type transaction

Return Values cmd_handle The command handle, which will be used when you want to modify command, or configure more parameters on command. Will be returned only when the status is 1 and the -mode is create. status Success (1) or failure (0) of the operation log Returned only when the status is 0

Examples: set ret [::lsh::dmf_control_config \ -mode create\ -dmf_hnd $dmf_https\ -control_type command\ -command_apply_to Both]

lsh::get_handle

Name: lsh::get_handle

Purpose: Used to get the test session, test case or dmf handle.

Synopsis: ::lsh::get_handle -lib<lib name> -name<test session name> -type<test|tc|dmf>Arguments: -lib the library where the test session is stored

-name The name of the test session which you want to get the handle -type Specify which kind of handle to get Possible values: test - Gets the test session handle tc - Gets the test case handle Dmf - Gets the dmf handle

Return Values handle The handle returned. It can be test session, test case or dmf handle.

status Success (1) or failure (0) of the operation. log Returned only when the status is 0.

Examples: set ret [::lsh::get_handle\ -lib "sms"\ -name "IP_APP_Inter_PSDN"\ -type "test"]

Return: {status 1} {handle test2}

set ret [::lsh::get_handle\ -lib sms\

Common Functions

50

-name "ip app sim auth"\ -type tc] Return: {status 1} {handle tc1}

set ret [::lsh::get_handle\ -lib sms\ -name "brt_dmf_http"\ -type dmf] Return: {status 1} {handle dmf1}

lsh::save

Name: lsh::save

Purpose: Used to save the test session, test case or DMF.

Synopsis: ::lsh::save -handle -overwrite {true | false}

Arguments: -handle The handle of the test case, the test session or the dmf, currently you only support to save the test session , test case and dmf with this API. -overwrite Specify whether to overwrite the test case, test session or dmf if it has already saved on the TAS. It will be overwrite only when you specify the value to be ture.


Examples: lsh::save -handle test1 Return: {status 1} lsh::save -handle test1 -overwrite true Return: {status 1}

Test Cases

51

Test Cases

This section includes basic configurations for all supported test cases.

AAA Server Node

52

AAA Server Node

Functions:lsh:: aaa_server_node_config

lsh:: aaa_server_node_config

Name: lsh:: aaa_server_node_config

Purpose: Creates or modifies the AAA server Node test case. This function only serves as the basic configurations required by the test case. To run the test case successfully, you must call some sub-functions that would make the configuration complete.

Synopsis: lsh:: aaa_server_node_config -mode{create|modify} -test_hnd<ALPHANUM> -tc_hnd<ALPHANUM> -ts_name<ANY> -protocol{Radius|Diameter} -num_authen_sessions<NUMERIC> -num_account_sessions_rad<NUMERIC> -deactivation_rate<DECIMAL> -num_account_sessions_dia<NUMERIC> -ip_address_allocation_rad{true|false} -addr_pool_sel_method_rad{Default_Pool_Selection_Cycle_Method |Pool_Name_in_Called-Station-Id} -ip_address_allocation_dia{true|false} -addr_pool_sel_method_dia{Default_Pool_Selection_Cycle_Method| Pool_Name_in_Called-Station-Id} -dual_stack_en{true|false} -disconn_sim_en{true|false} -rad_coa_simulation_en{true|false} -dia_ipsec_en{true|false} -nas_sut_ip<IP> -nas_sut_port<NUMERIC> -hss_sut_ip<IP> -hss_sut_host<ANY> -hss_sut_realm<ANY> -aaa_server_intf_type{eth|atm} -aaa_server_phy_intf<ANY> -aaa_server_intf_ip_addr<IP> -aaa_server_mac<MAC> -aaa_server_nexthop<IP> -aaa_server_forced_eth_intf{eth1|eth2} -aaa_server_addr_err_inj{0|1|2|3|4} -aaa_server_addr_err_dist{0|1} -dia_host<ANY> -dia_realm<ANY> -rad_user_name<ANY> -rad_passwd_en{true|false} -rad_password<ANY> -rad_use_eap_en{true|false} -rad_eap_send_msk{0|1} -mult_eap_en{true|false} -rad_meap_user_name<ANY> -rad_use_digest_en{true|false} -rad_digest_realm<ANY> -rad_digest_algorithm{md5|md5_sess} -rad_digest_qop{auth|auth_int} -rad_apply_tdf_acct_en{true|false}

AAA Server Node

53

-rad_apply_tdf_acct<ANY> -rad_apply_tdf_auth_en{true|false} -rad_apply_tdf_auth<ANY> -rad_aaa_auth_port<NUMERIC> -rad_aaa_acct_port<NUMERIC> -rad_vsa_db_size_acct<NUMERIC> -rad_vsa_db_size_auth<NUMERIC> -rad_aaa_secret_acct<ANY> -rad_aaa_secret_auth<ANY> -rad_wait_acct_start_time<NUMERIC> -rad_aaa_ha_support_en{true|false} -rad_sending_proxy_state_en{true|false} -rad_inc_user_name_aam{true|false} -rad_coa_send_access_accept_after{access_request_is_received| coa_ack_is_received|access_request_plus_delay} -rad_coa_accept_delay_time<NUMERIC> -rad_coa_auth_secret<ANY> -rad_send_coa_acct_en{true|false} -rad_send_coa_auth_en{true|false} -rad_send_coa_acct_sut_ip<IP> -rad_send_coa_auth_sut_ip<IP> -rad_coa_retries<NUMERIC> -rad_coa_retry_time<NUMERIC> -eap_user_name<ANY> -eap_expanded<NUMERIC> -eap_retries<NUMERIC> -eap_retry_time<NUMERIC> -eap_wimax_mip_en{true|false} -eap_wimax_root_key<ANY> -eap_wimax_mip_scheme{PMIP|CMIP} -eap_combined_eap_en{true|false} -eap_device_identity<ANY> -eap_device_secret<ANY> -eap_tdf_to_auth_para_en{true|false} -eap_tdf_to_auth_para<ANY> -eap_md5_en{true|false} -eap_md5_password<ANY> -eap_md5_tdf_to_para_en{true|false} -eap_md5_tdf<ANY> -eap_gtc_en{true|false} -eap_gtc_token<ANY> -eap_gtc_tdf_to_para_en{true|false} -eap_gtc_tdf<ANY> -eap_sim_en{true|false} -eap_sim_operator_var<ANY> -eap_sim_encryption_algorithm{3gpp|3gpp2} -eap_sim_secret_key<ANY> -eap_sim_family_key<ANY> -eap_sim_use_hardcoded_val_en{true|false} -eap_sim_sres<ANY> -eap_sim_kc<ANY> -eap_sim_permanent_id_en{true|false} -eap_sim_permanent_id<ANY> -eap_sim_id_type{fast_reauth|pseudo|permanent} -eap_sim_fast_reauth_max<NUMERIC> -eap_sim_tdf_to_para_en{true|false} -eap_sim_tdf_to_sim_para<ANY> -eap_aka_en{true|false} -eap_aka_operator_var<ANY> -eap_aka_encryption_algorithm{3gpp|3gpp2|usim} -eap_aka_secret_key<ANY> -eap_aka_family_key<ANY> -eap_aka_sqn_en{true|false} -eap_aka_sqn<NUMERIC> -eap_aka_permanent_id_en{true|false} -eap_aka_permanent_id<ANY> -eap_aka_request_id<NUMERIC> -eap_aka_amf_value<NUMERIC> -eap_aka_id_type{fast_reauth|pseudo|permanent} -eap_aka_fast_reauth_max<NUMERIC> -eap_aka_tdf_to_para_en{true|false}

AAA Server Node

54

-eap_aka_tdf<ANY> -eap_mschapv2_en{true|false} -eap_mschapv2_password<ANY> -eap_mschapv2_tdf_to_para_en{true|false} -eap_mschapv2_tdf<ANY> -eap_tls_en{true|false} -eap_tls_gen_pairwise_master_key{true|false} -eap_tls_reauth_en{true|false} -eap_tls_gen_wimax_msk_en{true|false} -eap_tls_pre_shared_key_en{true|false} -eap_tls_pre_shared_key<ANY> -eap_tls_include_certs_en{true|false} -eap_tls_private_key_file_type{installed|tdf} -eap_tls_private_key_file{private-rsa-key.pem| public-rsa-key.pem|x509-certificate.pem} -eap_tls_private_key_tdf<ANY> -eap_tls_x509_cert_file_type{installed|tdf} -eap_tls_x509_cert_file{private-rsa-key.pem| public-rsa-key.pem|x509-certificate.pem} -eap_tls_x509_cert_tdf<ANY> -eap_tls_num_of_entries<NUMERIC> -eap_tls_file_format{RSA|EVP} -eap_tls_first_entry<NUMERIC> -eap_tls_peap_en{true|false} -eap_tls_peap_ver<NUMERIC> -eap_tls_peap_mschapv2_en{true|false} -eap_tls_peap_mschapv2_password<ANY> -eap_tls_peap_mschapv2_tdf_to_para_en{true|false} -eap_tls_peap_mschapv2_tdf<ANY> -eap_tls_peap_mschapv2_eap_header_en{true|false} -eap_tls_fast_en{true|false} -eap_tls_fast_pac_en{true|false} -eap_tls_fast_md5_en{true|false} -eap_tls_fast_md5_password<ANY> -eap_tls_fast_md5_tdf_to_para_en{true|false} -eap_tls_fast_md5_tdf<ANY> -eap_tls_fast_gtc_en{true|false} -eap_tls_fast_gtc_token<ANY> -eap_tls_fast_gtc_tdf_to_para_en{true|false} -eap_tls_fast_gtc_tdf<ANY> -eap_tls_fast_sim_en{true|false} -eap_tls_fast_sim_operator_var<ANY> -eap_tls_fast_sim_encryption_algorithm{3gpp|3gpp2} -eap_tls_fast_sim_password<ANY> -eap_tls_fast_sim_family_key<ANY> -eap_tls_fast_sim_use_hardcoded_val_en{true|false} -eap_tls_fast_sim_sres<ANY> -eap_tls_fast_sim_kc<ANY> -eap_tls_fast_sim_permanent_id_en{true|false} -eap_tls_fast_sim_permanent_id<ANY> -eap_tls_fast_sim_id_type{fast_reauth|pseudo|permanent} -eap_tls_fast_sim_fast_reauth_max<NUMERIC> -eap_tls_fast_sim_tdf_to_para_en{true|false} -eap_tls_fast_sim_tdf<ANY> -eap_tls_fast_aka_en{true|false} -eap_tls_fast_aka_operator_var<ANY> -eap_tls_fast_aka_encryption_algorithm{3gpp|3gpp2|usim} -eap_tls_fast_aka_secret_key<ANY> -eap_tls_fast_aka_family_key<ANY> -eap_tls_fast_aka_sqn_en{true|false} -eap_tls_fast_aka_sqn<NUMERIC> -eap_tls_fast_aka_permanent_id_en{true|false} -eap_tls_fast_aka_permanent_id<ANY> -eap_tls_fast_aka_request_id<NUMERIC> -eap_tls_fast_aka_amf_value<NUMERIC> -eap_tls_fast_aka_id_type{fast_reauth|pseudo|permanent} -eap_tls_fast_sim_fast_reauth_max<NUMERIC> -eap_tls_fast_aka_tdf_to_para_en{true|false} -eap_tls_fast_aka_tdf<ANY> -eap_tls_fast_mschapv2_en{true|false} -eap_tls_fast_mschapv2_password<ANY>

AAA Server Node

55

-eap_tls_fast_mschapv2_tdf_to_para_en{true|false} -eap_tls_fast_mschapv2_tdf<ANY> -eap_tls_fast_mschapv2_eap_header_en{true|false} -eap_tls_ttls_enable{true|false} -eap_tls_ttls_method{CHAP|EAP|PAP|MSCHAPV1|MSCHAPV2} -eap_tls_ttls_user_name<ANY> -eap_tls_ttls_chap_password<ANY> -eap_tls_tdf_to_para_en{true|false} -eap_tls_tdf<ANY> -meap_user_name<ANY> -meap_expanded<NUMERIC> -meap_retries<NUMERIC> -meap_retry_time<NUMERIC> -meap_wimax_mip_en{true|false} -meap_wimax_root_key<ANY> -meap_wimax_mip_scheme{PMIP|CMIP} -meap_combined_eap_en{true|false} -meap_deviceid<ANY> -meap_device_secret<ANY> -meap_gen_tdf_to_para_en{true|false} -meap_gen_tdf<ANY> -meap_md5_en{true|false} -meap_md5_password<ANY> -meap_md5_tdf_to_para_en{true|false} -meap_md5_tdf<ANY> -meap_gtc_en{true|false} -meap_gtc_token<ANY> -meap_gtc_tdf_to_para_en{true|false} -meap_gtc_tdf<ANY> -meap_sim_en{true|false} -meap_sim_operator_var<ANY> -meap_sim_encryption_algorithm{3gpp|3gpp2} -meap_sim_secret_key<ANY> -meap_sim_family_key<ANY> -meap_sim_use_hardcoded_val_en{true|false} -meap_sim_sres<ANY> -meap_sim_kc<ANY> -meap_sim_permanent_id_en{true|false} -meap_sim_permanent_id<ANY> -meap_sim_id_type{fast_reauth|pseudo|permanent} -meap_sim_fast_reauth_max<NUMERIC> -meap_sim_tdf_to_para_en{true|false} -meap_sim_tdf<ANY> -meap_aka_en{true|false} -meap_aka_operator_var<ANY> -meap_aka_encryption_algorithm{3gpp|3gpp2|usim} -meap_aka_secret_key<ANY> -meap_aka_family_key<ANY> -meap_aka_sqn_en{true|false} -meap_aka_sqn<NUMERIC> -meap_aka_permanent_id_en{true|false} -meap_aka_permanent_id<ANY> -meap_aka_request_id<NUMERIC> -meap_aka_amf_value<NUMERIC> -meap_aka_id_type{fast_reauth|pseudo|permanent} -meap_aka_fast_reauth_max<NUMERIC> -meap_aka_tdf_to_para_en{true|false} -meap_aka_tdf<ANY> -meap_mschapv2_en{true|false} -meap_mschapv2_password<ANY> -meap_mschapv2_tdf_to_para_en{true|false} -meap_mschapv2_tdf<ANY> -meap_tls_en{true|false} -meap_tls_gen_pairwise_master_key{true|false} -meap_tls_reauth_en{true|false} -meap_tls_gen_wimax_msk_en{true|false} -meap_tls_pre_shared_key_en{true|false} -meap_tls_pre_shared_key<ANY> -meap_tls_include_certs_en{true|false} -meap_tls_private_key_file_type{installed|tdf} -meap_tls_private_key_file{private-rsa-key.pem|public-rsa-key.pem

AAA Server Node

56

|x509-certificate.pem} -meap_tls_private_key_tdf<ANY> -meap_tls_x509_cert_file_type{installed|tdf} -meap_tls_x509_cert_file{private-rsa-key.pem|public-rsa-key.pem |x509-certificate.pem} -meap_tls_x509_cert_tdf<ANY> -meap_tls_num_of_entries<NUMERIC> -meap_tls_file_format{RSA|EVP} -meap_tls_first_entry<NUMERIC> -meap_tls_peap_en{true|false} -meap_tls_peap_ver<NUMERIC> -meap_tls_peap_mschapv2_en{true|false} -meap_tls_peap_mschapv2_password<ANY> -meap_tls_peap_mschapv2_tdf_to_para_en{true|false} -meap_tls_peap_mschapv2_tdf<ANY> -meap_tls_peap_mschapv2_eap_header_en{true|false} -meap_tls_fast_en{true|false} -meap_tls_fast_pac_en{true|false} -meap_tls_fast_md5_en{true|false} -meap_tls_fast_md5_password<ANY> -meap_tls_fast_md5_tdf_to_para_en{true|false} -meap_tls_fast_md5_tdf<ANY> -meap_tls_fast_gtc_en{true|false} -meap_tls_fast_gtc_token<ANY> -meap_tls_fast_gtc_tdf_to_para_en{true|false} -meap_tls_fast_gtc_tdf<ANY> -meap_tls_fast_sim_en{true|false} -meap_tls_fast_sim_operator_var<ANY> -meap_tls_fast_sim_encryption_algorithm{3gpp|3gpp2} -meap_tls_fast_sim_password<ANY> -meap_tls_fast_sim_family_key<ANY> -meap_tls_fast_sim_use_hardcoded_val_en{true|false} -meap_tls_fast_sim_sres<ANY> -meap_tls_fast_sim_kc<ANY> -meap_tls_fast_sim_permanent_id_en{true|false} -meap_tls_fast_sim_permanent_id<ANY> -meap_tls_fast_sim_id_type{fast_reauth|pseudo|permanent} -meap_tls_fast_sim_fast_reauth_max<NUMERIC> -meap_tls_fast_sim_tdf_to_para_en{true|false} -meap_tls_fast_sim_tdf<ANY> -meap_tls_fast_aka_en{true|false} -meap_tls_fast_aka_operator_var<ANY> -meap_tls_fast_aka_encryption_algorithm{3gpp|3gpp2|usim} -meap_tls_fast_aka_secret_key<ANY> -meap_tls_fast_aka_family_key<ANY> -meap_tls_fast_aka_sqn_en{true|false} -meap_tls_fast_aka_sqn<NUMERIC> -meap_tls_fast_aka_permanent_id_en{true|false} -meap_tls_fast_aka_permanent_id<ANY> -meap_tls_fast_aka_request_id<NUMERIC> -meap_tls_fast_aka_amf_value<NUMERIC> -meap_tls_fast_aka_id_type{fast_reauth|pseudo|permanent} -meap_tls_fast_aka_fast_reauth_max<NUMERIC> -meap_tls_fast_aka_tdf_to_para_en{true|false} -meap_tls_fast_aka_tdf<ANY> -meap_tls_fast_mschapv2_en{true|false} -meap_tls_fast_mschapv2_password<ANY> -meap_tls_fast_mschapv2_tdf_to_para_en{true|false} -meap_tls_fast_mschapv2_tdf<ANY> -meap_tls_fast_mschapv2_eap_header_en{true|false} -meap_tls_ttls_enable{true|false} -meap_tls_ttls_method{CHAP|EAP|PAP|MSCHAPV1|MSCHAPV2} -meap_tls_ttls_user_name<ANY> -meap_tls_ttls_chap_password<ANY> -meap_tls_tdf_to_para_en{true|false} -meap_tls_tdf<ANY> -aaa_app_application{nasreq|dia_eap|wimax_mipv4|wm_interface |s6b_interface|sta_interface|s6b_sta_swx_inerface} -aaa_app_wimax_ha4_com_code_en{true|false} -aaa_app_wimax_ha4_com_code<NUMERIC> -aaa_app_state_mode{stateful|stateless}

AAA Server Node

57

-aaa_app_acct_ts_time<NUMERIC> -aaa_app_user_name<ANY> -aaa_app_password_en{true|false} -aaa_app_password<ANY> -aaa_app_mul_dea_msg{0|1} -aaa_app_succ_dea_msg{0|1} -aaa_app_meap_user_name<ANY> -dia_product_name<ANY> -dia_vendor_id<NUMERIC> -dia_acct_avp_db_size<NUMERIC> -dia_auth_avp_db_size<NUMERIC> -dia_trans_protocol{tcp|sctp} -dia_num_peers<NUMERIC> -dia_retry_time<NUMERIC> -dia_watchdog_time<NUMERIC> -dia_proxy_en{true|false}

Available Sub Function(s): lsh::ip_pools_config: Used to configure the IP Pools on this test case.

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - Creates a new test case and the parameters in the test session specified by the -test_hnd. modify - modify the parameters on the test case specified by the -tc_hnd. -test_hnd Specifies the test session handle on which the test case will be added. This argument is mandatory when the -mode is set to create. -tc_hnd Specifies the test case handle. This argument is mandatory when the -mode is set to modify. It can be used to modify the parameters configured on this test case. -ts_name #### Specifies on which the test case will be added. This argument is mandatory when the -mode is set to create. -protocol Specifies the protocol used in AAA server. Possible value: Radius,Diameter Default: Radius -num_authen_sessions The number of simultaneous RADIUS or Diameter authentication sessions that are supported by the node. Range: 1-400000 Default: 1

-num_account_sessions_rad The number of simultaneous RADIUS accounting sessions that are supported by the node. Range: 1-400000 Default: 1 This argument is available when -protocol is set to Radius.

-deactivation_rate The rate at which the test attempts to deactivate MN/MS sessions. When the control plane is used, this rate is the number of MNs/MS that will attempt to disconnect their control sessions every second. When the control plane is not used, this rate is the number of MNs/MS that will stop sending data or release their data connections every second. Range: 0.0010-3000.0 Default: 1.0 This argument is available when -disconn_sim_en is set to

AAA Server Node

58

true, or protocol is set to Diameter.

-num_account_sessions_dia The number of simultaneous Diameter accounting sessions that will be supported by the node. Range: 1-400000 Default: 1 This argument is available when -protocol is set to Diameter.

-ip_address_allocation_rad Enables/disables IP Address Allocation feature in AAA radius node. IP Address Allocation is an optional feature in the AAA Server Node test case, and is designed to provide IP address allocation in a GPRS network. You can define up to 30 address pools containing either IPv4 or IPv6 addresses with the IP Pool Manager, and the virtual server will issue addresses from the pools to authenticated MNs. Possible Values:true,false Default: false This argument is available when -protocol is set to Radius.

-addr_pool_sel_method_rad Specifies the address pool selection method used in IP Address Allocation feature in AAA radius node. Possible Values: Default_Pool_Selection_Cycle_Method, Pool_Name_in_Called-Station-Id Default: Pool_Name_in_Called-Station-Id This argument is available when -ip_address_allocation_rad is set to true.

-ip_address_allocation_dia Enables/disables IP Address Allocation feature in AAA diameter node. IP Address Allocation is an optional feature in the AAA Server Node test case, and is designed to provide IP address allocation in a GPRS network. You can define up to 30 address pools containing either IPv4 or IPv6 addresses with the IP Pool Manager, and the virtual server will issue addresses from the pools to authenticated MNs. Possible Values:true,false Default: false This argument is available when -protocol is set to Diameter. -addr_pool_sel_method_dia Specifies the address pool selection method used in IP Address Allocation feature in AAA radius node. Possible value: Default_Pool_Selection_Cycle_Method, Pool_Name_in_Called-Station-Id Default: Pool_Name_in_Called-Station-Id This argument is available when -ip_address_allocation_dia is set to true.

-dual_stack_en Enables/disables dual stacks in AAA server node. Possible Values:true,false Default: false This argument is available when -ip_address_allocation_rad is set to true.

-disconn_sim_en Enables/disables disconnect-simulation in AAA server node. When the node sends a Disconnect Request, the AAA session stops and tears down the AAA Session immediately. Possible value:true,false Default: false -rad_coa_simulation_en Enables/disables COA simulation in AAA server node. Possible value:true,false Default: false

AAA Server Node

59

-dia_ipsec_en Enables/disables ipsec in AAA diameter server node. Possible Values:true,false Default: false This argument is available when -protocol is set to Diameter.

-nas_sut_ip Specifies the IP address of NAS SUT. This argument is available when -disconn_sim_en is set or -rad_coa_simulation_en is set to true. -nas_sut_port Specifies the IP port of NAS SUT. Range: 0-65535 Default: 3799 This argument is available when -disconn_sim_en or -rad_coa_simulation_en is set to true.

-hss_sut_ip Specifies the IP address of HSS SUT. This argument is available when -aaa_app_application is set to s6b_sta_swx_inerface. -hss_sut_host Specifies the host of HSS SUT. Default: HSSServer.Spirent.com This argument is available when -aaa_app_application is set to s6b_sta_swx_inerface.

-hss_sut_realm Specifies Realm serviced by the SUT. Default: Spirent.com This argument is available when -aaa_app_application is set to s6b_sta_swx_inerface.

-aaa_server_intf_type Specifies the type of the physical interface. Possible value: eth,atm Default: eth -aaa_server_phy_intf Specifies which enabled Ethernet Interface will be used for AAA Server. It is the Ethernet interface name, such as "eth1","eth2". -aaa_server_intf_ip_addr Specifies the IP address of the AAA Server node. When the physical interface type is "eth", it is the AAA Server node's actual IP address, it is one of the address pool associated with physical interface. When the physical interface type is "atm", it is the source address for all the traffic sent by the node. The address that you enter will be incremented for each node. -aaa_server_mac Specifies the MAC address of the AAA Server node. -aaa_server_nexthop If don't want to use the default route, you can specify a physical device's IP address in the test network to use this IP address as the next hop. -aaa_server_addr_err_inj Specifies the Error Inject in advanced test node setting. Possible value: 0: None 1: Packet Discard 2: IP Total Length Set to 0 3: IP Checksum Corrupted 4: Payload Checksum Corrupted Default: 0

AAA Server Node

60

-aaa_server_addr_err_dist Specifies the Error Distribution in advanced test node setting. Possible value: 0: Fixed 1: Random Default: 0

-dia_host Specifies the host of AAA Diameter server Node. Default: NAS.Spirent.com This argument is available when -protocol is set to Diameter.

-dia_realm Specifies Realm serviced by the AAA Diameter server Node. Default: Spirent.com This argument is available when -protocol is set to Diameter.

-rad_user_name Specifies the user name used for Radius. Default: @domain This argument is available when -protocol is set to Radius.

-rad_passwd_en Enables/disables password input in AAA Radius server node. Possible Values:true,false Default: false This argument is available when -protocol is set to Radius.

-rad_password Specifies the password that is used for all user names. Default: secret This argument is available when -rad_passwd_en is set to true.

-rad_use_eap_en Specifies whether use EAP authentication. Possible value:true,false Default: false -rad_eap_send_msk Specifies whether send MSK in access accept via RFC2548 VSA. Possible Values:true,false Default: false This argument is available when -rad_use_eap_en is set to true.

-mult_eap_en Specifies whether use multiple EAP authentication. Possible value:true,false Default: false -rad_meap_user_name Specifies the user name used for multiple EAP authentication. Default: @domain This argument is available when -mult_eap_en is set to true.

-rad_use_digest_en Specifies whether use digest authentication for Radius. Possible Values:true,false Default: false This argument is available when -protocol is set to Radius.

-rad_digest_realm Specifies the realm used by digest authentication for Radius. Default: aaa.com This argument is available when -rad_use_digest_en is set to true.

-rad_digest_algorithm Specifies the algorithm used by digest authentication for Radius. Possible value: md5,md5_sess Default: md5 This argument is available when -rad_use_digest_en is set to true.

AAA Server Node

61

-rad_digest_qop Specifies the QOP (Quality of Protection) used by digest authentication for Radius. Possible Values: auth,auth_int Default: auth This argument is available when -rad_use_digest_en is set to true.

-rad_apply_tdf_acct_en Specifies whether apply test data file to accounting parameter values for Radius. Possible Values:true,false Default: false This argument is available when -protocol is set to Radius.

-rad_apply_tdf_acct Specifies test data file to accounting parameter values for Radius. This argument is available when -rad_apply_tdf_acct_en is set to true. -rad_apply_tdf_auth_en Specifies whether apply test data file to authentication parameter values for Radius. Possible Values:true,false Default: false This argument is available when -protocol is set to Radius.

-rad_apply_tdf_auth Specifies test data file to authentication parameter values for Radius. This argument is available when -rad_apply_tdf_auth_en is set to true. -rad_aaa_auth_port Specifies the UDP port that is used for Radius authentication on all SUTs. Range: 0-65535 Default: 1812 This argument is available when -protocol is set to Radius.

-rad_aaa_acct_port Specifies the UDP port that is used for Radius accounting on all SUTs. Range: 0-65535 Default: 1813 This argument is available when -protocol is set to Radius.

-rad_vsa_db_size_acct Indicates the VSA size allocated for accounting packet flow descriptors and allows you to define the database memory to run VSA packets. Range: 200-4000 Default: 200 This argument is available when -protocol is set to Radius.

-rad_vsa_db_size_auth Indicates the VSA size allocated for authentication packet flow descriptors and allows you to define the database memory to run VSA packets. Range: 200-4000 Default: 200 This argument is available when -protocol is set to Radius.

-rad_aaa_secret_acct The shared secret between a RADIUS NAS and AAA server that is included, along with other values, in the encrypted Accounting field in the Access Request messages sent to the SUT. Default: secret This argument is available when -protocol is set to Radius.

-rad_aaa_secret_auth The shared secret between a RADIUS NAS and AAA server that is included, along with other values, in the encrypted Authenticator field in the

AAA Server Node

62

Access Request messages sent to the SUT. Default: secret This argument is available when -protocol is set to Radius.

-rad_wait_acct_start_time The number of milliseconds that the virtual server will wait for an Accounting Request-start message. Range: 0-1000000 Default: 20000 This argument is available when -protocol is set to Radius and -ip_address_allocation_rad is set to true.

-rad_aaa_ha_support_en Specifies whether use AAA-HA Support to have the AAA server act like WiMAX AAA server. Possible Values:true,false Default: false This argument is available when -protocol is set to Radius.

-rad_sending_proxy_state_en Enables/disables Proxy-State attribute handling if there is a proxy AAA Server between the NAS and the authenticating server. Possible Values:true,false Default: false This argument is available when -protocol is set to Radius.

-rad_inc_user_name_aam Specifies whether include user name in Access Accept Message. Possible Values:true,false Default: false This argument is available when -protocol is set to Radius.

-rad_coa_send_access_accept_after Indicates when an Access Accept message response is sent to NAS. Possible Values: access_request_is_received,coa_ack_is_received,access_request_plus_delay Default: access_request_is_received This argument is available when -rad_coa_simulation_en is set to true.

-rad_coa_accept_delay_time Specifies the number of seconds for the test to wait for before sending the Access Request to NAS. Range: 5-65535 Default: 10 This argument is available when -rad_coa_send_access_accept_after is set to access_request_plus_delay.

-rad_coa_auth_secret Indicates the shared authentication secret key that is known to both the NAS and the AAA Server. Default: secret This argument is available when -rad_coa_simulation_en is set to true.

-rad_send_coa_acct_en Enables/disables sending COA for accounting message from SUT. Possible Values:true,false Default: false This argument is available when -rad_coa_simulation_en is set to true.

-rad_send_coa_auth_en Enables/disables sending COA for authentication message from SUT. Possible Values:true,false Default: false This argument is available when -rad_coa_simulation_en is set to true.

-rad_send_coa_acct_sut_ip Specifies SUT for accounting message sending. This argument is available when -rad_send_coa_acct_en is set to true. -rad_send_coa_auth_sut_ip Specifies SUT for authentication message sending.

AAA Server Node

63

This argument is available when -rad_send_coa_auth_en is set to true. -rad_coa_retries Specifies The number of times a message is re-transmitted. Enter 0 to disable retries. Range: 1-65535 Default: 5 This argument is available when -rad_coa_simulation_en is set to true.

-rad_coa_retry_time Indicates the amount of time, in milliseconds, the test waits for a response, if a response is expected. When the time expires and the Retries has not been exceeded, the message is re-transmitted. Range: 1-65535 Default: 1000 This argument is available when -rad_coa_simulation_en is set to true.

-eap_user_name The MN's user name, NAI, or IMSI that will be sent or expected in the EAP Identity response. Default: @domain This argument is available when -mult_eap_en is set to true, or -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface}

-eap_expanded Enables/disables support for vendor-specific authentication methods. Range: 0-1 Default: 0 This argument is available when -mult_eap_en is set to true, or -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface}

-eap_retries Defines the number of times a message will be transmitted when the expected response or follow-on request has not been received. Enter 0 to disable retries. Range: 0-65535 Default: 0 This argument is available when -mult_eap_en is set to true, or -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface}

-eap_retry_time Defines the elapsed time (in seconds) between each try until the configured retry count is reached. Range: 0-65535 Default: 5 This argument is available when -mult_eap_en is set to true, or -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface}

-eap_wimax_mip_en Enables/disables Use the WiMAX MIP Root Key. Possible value:true,false Default: false This argument is available when -mult_eap_en is set to true, or -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface}

-eap_wimax_root_key Use the WiMAX MIP Root Key to enable WiMAX MIP Root Key generation and

AAA Server Node

64

distribution This argument is available when -eap_wimax_mip_en is set to true.

-eap_wimax_mip_scheme Specifies MIP Scheme. Possible Values:PMIP,CMIP Default: PMIP This argument is available when -eap_wimax_mip_en is set to true.

-eap_combined_eap_en Enables/disables Use the EAP authentication scheme using a challenge combined with a device ID, password and hash algorithm. Possible value:true,false Default: false This argument is available when -mult_eap_en is set to true, or -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface}

-eap_device_identity Indicates the Device ID sending the EAP challenge This argument is available when -eap_combined_eap_en is set to true.

-eap_device_secret Indicates the Device password/secret. Default: 0x1234567890abcdef1234567890abcdef This argument is available when -eap_combined_eap_en is set to true.

-eap_tdf_to_auth_para_en Enables/disables apply authentication parameter from tdf.} Possible value:true,false Default: false This argument is available when -mult_eap_en is set to true, or -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface}

-eap_tdf_to_auth_para Specifies the TDF for applying authentication parameters. This argument is available when -eap_tdf_to_auth_para_en is set to true.

-eap_md5_en Enables/disables MD5 authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-eap_md5_password Specifies password for MD5 authentication. Default: pword This argument is available when -eap_md5_en is set to true.

-eap_md5_tdf_to_para_en Enables/disables apply MD5 parameters from tdf. Possible Values:true,false Default: false This argument is available when -eap_md5_en is set to true.

-eap_md5_tdf Specifies the tdf for applying MD5 parameters. This argument is available when -eap_md5_tdf_to_para_en is set to true.

-eap_gtc_en

AAA Server Node

65

Enables/disables support for GTC authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-eap_gtc_token Specifies token for GTC authentication. Default: pword This argument is available when -eap_gtc_en is set to true.

-eap_gtc_tdf_to_para_en Enables/disables apply GTC parameters from tdf. Possible Values:true,false Default: false This argument is available when -eap_gtc_en is set to true.

-eap_gtc_tdf Specifies the tdf for applying GTC parameters. This argument is available when -eap_gtc_tdf_to_para_en is set to true.

-eap_sim_en Enables/disables support for SIM authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-eap_sim_operator_var Specifies the 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Default: 0x63BFA50EE6523365FF14C1F45F88737D This argument is available when -eap_sim_encryption_algorithm is set to 3gpp.

-eap_sim_encryption_algorithm Specifies method of cryptographic encryption of the data to be transmitted between the MN and the AAA Server. Possible Values: 3gpp,3gpp2 Default: 3gpp This argument is available when -eap_sim_en is set to true.

-eap_sim_secret_key Specifies the shared key that is known to both the MN and the AAA Server. Default: 0x0123456789ABCDEF0123456789ABCDEF This argument is available when -eap_sim_en is set to true.

-eap_sim_family_key Specifies 32-bit identifier used by the 3GPP2 Enhanced Cryptographic Algorithm. Default: 0x41484147 This argument is available when -eap_sim_encryption_algorithm is set to 3gpp2.

-eap_sim_use_hardcoded_val_en Enables/disables use hard-coded values to define fixed SRES AND Kc values. Possible Values: true,false Default: false This argument is available when -eap_sim_en is set to true.

-eap_sim_sres Specifies the SRES value that will be used to formulate the challenge response for all MNs. Default: 0x000000000000 This argument is available when -eap_sim_use_hardcoded_val_en is set to

AAA Server Node

66

true.

-eap_sim_kc Specifies the key that will be used to derive new keying material for all MNs. Default: 0x00000000000000000000000000000000 This argument is available when -eap_sim_use_hardcoded_val_en is set to true.

-eap_sim_permanent_id_en Indicates whether permanent identity can be used. Possible Values:true,false Default: false This argument is available when -eap_sim_en is set to true.

-eap_sim_permanent_id Indicates the permanent identity used on full authentication only. This argument is available when -eap_sim_permanent_id_en is set to true.

-eap_sim_id_type Specifies the ID type for re-authentication. Possible Values: fast_reauth,pseudo,permanent Default: fast_reauth This argument is available when -eap_sim_en is set to true.

-eap_sim_fast_reauth_max Specifies the Max counter of fast re-authentication. Range: 1-65535 Default: 65535 This argument is available when -eap_sim_id_type is set to fast_reauth.

-eap_sim_tdf_to_para_en Enables/disables apply SIM parameters from TDF. Possible Values:true,false Default: false This argument is available when -eap_sim_en is set to true.

-eap_sim_tdf_to_sim_para Specifies the tdf for applying SIM parameters. This argument is available when -eap_sim_tdf_to_para_en is set to true.

-eap_aka_en Enables/disables support for AKA authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-eap_aka_operator_var Specifies the 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Default: 0x63BFA50EE6523365FF14C1F45F88737D This argument is available when -eap_aka_encryption_algorithm is set to 3gpp.

-eap_aka_encryption_algorithm Specifies method of cryptographic encryption of the data to be transmitted between the MN and the AAA Server. Possible Values: 3gpp,3gpp2,usim Default: 3gpp This argument is available when -eap_aka_en is set to true.

-eap_aka_secret_key Specifies the shared key that is known to both the MN and the AAA Server. Default: 0x0123456789ABCDEF0123456789ABCDEF This argument is available when -eap_aka_en is set to true.

-eap_aka_family_key Specifies 32-bit identifier used by the 3GPP2 Enhanced Cryptographic

AAA Server Node

67

Algorithm. Default: 0x41484147 This argument is available when -eap_aka_encryption_algorithm is set to 3gpp2.

-eap_aka_sqn_en Enables/disables Starting Sequence Number input. Possible Values:true,false Default: false This argument is available when -ip_address_allocation_rad is set to true.

-eap_aka_sqn Specifies the Starting Sequence Number. Range: 0- 281474976710655 Default: 1 This argument is available when -eap_aka_sqn_en is set to true.

-eap_aka_permanent_id_en Indicates whether permanent identity can be used. Possible Values:true,false Default: false This argument is available when -eap_aka_en is set to true.

-eap_aka_permanent_id Indicates the permanent identity used on full authentication only. This argument is available when -eap_aka_permanent_id_en is set to true.

-eap_aka_request_id Selects Send Request Identity to include AKA-Identity in response to a valid EAP-Request/AKA-Identity from the server. Range: 0- 1 Default: 1 This argument is available when -eap_aka_sqn_en is set to true.

-eap_aka_amf_value With EAP-AKA authentication, in order to reduce the risk of node vulnerability, the AKA algorithm is computed with the AMF separation bit set to 1, and the peer checks to ensure that this is indeed the case. Range: 0- 2 Default: 0 This argument is available when -eap_aka_sqn_en is set to true.

-eap_aka_id_type Specifies the ID type for re-authentication. Possible Values: fast_reauth,pseudo,permanent Default: fast_reauth This argument is available when -eap_aka_en is set to true.

-eap_aka_fast_reauth_max Specifies the Max counter of fast re-authentication. Range: 1-65535 Default: 65535 This argument is available when -eap_aka_id_type is set to fast_reauth.

-eap_aka_tdf_to_para_en Enables/disables apply AKA parameters from TDF. Possible Values:true,false Default: false This argument is available when -eap_aka_en is set to true.

-eap_aka_tdf Specifies the tdf for applying AKA parameters. This argument is available when -eap_aka_tdf_to_para_en is set to true.

-eap_mschapv2_en Enables/disables support for MSCHAPV2 authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface |

AAA Server Node

68

s6b_sta_swx_inerface} Possible value:true,false Default: false

-eap_mschapv2_password Specifies password for MSCHAPV2 authentication. Default: pword This argument is available when -eap_mschapv2_en is set to true.

-eap_mschapv2_tdf_to_para_en Enables/disables apply MSCHAPV2 parameters from tdf. Possible Values:true,false Default: false This argument is available when -eap_mschapv2_en is set to true.

-eap_mschapv2_tdf Specifies the tdf for applying MSCHAPV2 parameters. This argument is available when -eap_mschapv2_tdf_to_para_en is set to true.

-eap_tls_en Enables/disables support for TLS authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-eap_tls_gen_pairwise_master_key Enables/disables generate pairwise master key. Possible Values:true,false Default: false This argument is available when -eap_tls_en is set to true.

-eap_tls_reauth_en Enables/disables re-authentication. Possible Values:true,false Default: false This argument is available when -eap_tls_en is set to true.

-eap_tls_gen_wimax_msk_en Enables/disables generate WiMax MSK. Possible Values:true,false Default: false This argument is available when -eap_tls_en is set to true.

-eap_tls_pre_shared_key_en Enables/disables Pre shared key cipher suites. Possible Values:true,false Default: false This argument is available when -eap_tls_en is set to true.

-eap_tls_pre_shared_key Specifies the pre-shared key. This argument is available when -eap_tls_pre_shared_key_en is set to true.

-eap_tls_include_certs_en Enables/disables include certificates. Possible Values:true,false Default: true This argument is available when -eap_tls_en is set to true. AND eap_tls_pre_shared_key_en false

-eap_tls_private_key_file_type Defines the type of private key file. Possible Values: installed,tdf Default: installed This argument is available when -eap_tls_include_certs_en is set to true.

AAA Server Node

69

-eap_tls_private_key_file Specifies the private key file. Possible Values: private-rsa-key.pem,public-rsa-key.pem,x509-certificate.pem Default: private-rsa-key.pem This argument is available when -eap_tls_private_key_file_type is set to installed.

-eap_tls_private_key_tdf Specifies the TDF used as private key file. This argument is available when -eap_tls_private_key_file_type is set to tdf.

-eap_tls_x509_cert_file_type Defines the type of X509 certificate file. Possible Values: installed,tdf Default: installed This argument is available when -eap_tls_include_certs_en is set to true.

-eap_tls_x509_cert_file Specifies the X509 certificate file. Possible Values: private-rsa-key.pem,public-rsa-key.pem,x509-certificate.pem Default: private-rsa-key.pem This argument is available when -eap_tls_x509_cert_file_type is set to installed.

-eap_tls_x509_cert_tdf Specifies the TDF used as X509 certificate file. This argument is available when -eap_tls_x509_cert_file_type is set to tdf.

-eap_tls_num_of_entries Spesifies the number of entries. Default: 0 This argument is available when -eap_tls_include_certs_en is set to true.

-eap_tls_file_format Specifies the file format. Possible Values: RSA,EVP Default: RSA This argument is available when -eap_tls_include_certs_en is set to true.

-eap_tls_first_entry Specifies the first entry. Default: 0 This argument is available when -eap_tls_include_certs_en is set to true.

-eap_tls_peap_en Enables/disables peap TLS authentication. Possible Values:true,false Default: false This argument is available when -eap_tls_en is set to true.

-eap_tls_peap_ver Specifies the version of peap in tls authentication. Range: 0-1 Default: 0 This argument is available when -eap_tls_peap_en is set to true.

-eap_tls_peap_mschapv2_en Enables/disables support for MSCHAPV2 in peaq tls authentication. Possible Values:true,false Default: false This argument is available when -eap_tls_peap_en is set to true.

-eap_tls_peap_mschapv2_password Specifies password for MSCHAPV2 in peaq tls authentication. Default: pword This argument is available when -eap_tls_peap_mschapv2_en is set to true.

AAA Server Node

70

-eap_tls_peap_mschapv2_tdf_to_para_en Enables/disables apply MSCHAPV2 parameters from tdf. Possible Values:true,false Default: false This argument is available when -eap_tls_peap_mschapv2_en is set to true.

-eap_tls_peap_mschapv2_tdf Specifies the tdf for applying MSCHAPV2 parameters. eap_tls_peap_mschapv2_tdf_to_para_en true

-eap_tls_peap_mschapv2_eap_header_en Enables/disables Microsoft PEAP includes EAP header on the EAP message. Possible Values:true,false Default: true This argument is available when -protocol is set to Radius. AND eap_tls_peap_mschapv2_en true

-eap_tls_fast_en Enables/disables fast TLS authentication. Possible Values:true,false Default: false This argument is available when -eap_tls_en is set to true.

-eap_tls_fast_pac_en Defines credential to a peer for optimized network authentication. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_en is set to true.

-eap_tls_fast_md5_en Enables/disables support for MD5 authentication. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_en is set to true.

-eap_tls_fast_md5_password Specifies password for MD5 authentication. Default: pword This argument is available when -eap_tls_fast_md5_en is set to true.

-eap_tls_fast_md5_tdf_to_para_en Enables/disables apply MD5 parameters from tdf. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_md5_en is set to true.

-eap_tls_fast_md5_tdf Specifies the tdf for applying MD5 parameters. This argument is available when -eap_tls_fast_md5_tdf_to_para_en is set to true.

-eap_tls_fast_gtc_en Enables/disables support for GTC authentication. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_en is set to true.

-eap_tls_fast_gtc_token Specifies token for GTC authentication. Default: pword This argument is available when -eap_tls_fast_gtc_en is set to true.

AAA Server Node

71

-eap_tls_fast_gtc_tdf_to_para_en Enables/disables apply GTC parameters from tdf. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_gtc_en is set to true.

-eap_tls_fast_gtc_tdf Specifies the tdf for applying GTC parameters. This argument is available when -eap_tls_fast_gtc_tdf_to_para_en is set to true.

-eap_tls_fast_sim_en Enables/disables support for SIM authentication. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_en is set to true.

-eap_tls_fast_sim_operator_var Specifies the 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Default: 0x63BFA50EE6523365FF14C1F45F88737D This argument is available when -eap_tls_fast_sim_encryption_algorithm is set to 3gpp.

-eap_tls_fast_sim_encryption_algorithm Specifies method of cryptographic encryption of the data to be transmitted between the MN and the AAA Server. Possible Values: 3gpp,3gpp2 Default: 3gpp This argument is available when -eap_tls_fast_sim_en is set to true.

-eap_tls_fast_sim_secret_key Specifies the shared key that is known to both the MN and the AAA Server. Default: 0x0123456789ABCDEF0123456789ABCDEF This argument is available when -eap_tls_fast_sim_en is set to true.

-eap_tls_fast_sim_family_key Specifies 32-bit identifier used by the 3GPP2 Enhanced Cryptographic Algorithm. Default: 0x41484147 This argument is available when -eap_tls_fast_sim_encryption_algorithm is set to 3gpp2.

-eap_tls_fast_sim_use_hardcoded_val_en Enables/disables use hard-coded values to define fixed SRES AND Kc values. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_sim_en is set to true.

-eap_tls_fast_sim_sres Specifies the SRES value that will be used to formulate the challenge response for all MNs. Default: 0x000000000000 This argument is available when -eap_tls_fast_sim_use_hardcoded_val_en is set to true.

-eap_tls_fast_sim_kc Specifies the key that will be used to derive new keying material for all MNs. Default: 0x00000000000000000000000000000000 This argument is available when -eap_tls_fast_sim_use_hardcoded_val_en is set to true.

-eap_tls_fast_sim_permanent_id_en

AAA Server Node

72

Indicates whether permanent identity can be used. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_sim_en is set to true.

-eap_tls_fast_sim_permanent_id Indicates the permanent identity used on full authentication only. This argument is available when -eap_tls_fast_sim_permanent_id_en is set to true.

-eap_tls_fast_sim_id_type Specifies the ID type for re-authentication. Possible Values: fast_reauth,pseudo,permanent Default: fast_reauth This argument is available when -eap_tls_fast_sim_en is set to true.

-eap_tls_fast_sim_fast_reauth_max Specifies the Max counter of fast re-authentication. Range: 1-65535 Default: 65535 This argument is available when -eap_tls_fast_sim_id_type is set to fast_reauth.

-eap_tls_fast_sim_tdf_to_para_en Enables/disables apply SIM parameters from TDF. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_sim_en is set to true.

-eap_tls_fast_sim_tdf_to_sim_para Specifies the tdf for applying SIM parameters. This argument is available when -eap_tls_fast_sim_tdf_to_para_en is set to true.

-eap_tls_fast_aka_en Enables/disables support for AKA authentication. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_en is set to true.

-eap_tls_fast_aka_operator_var Specifies the 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Default: 0x63BFA50EE6523365FF14C1F45F88737D This argument is available when -eap_tls_fast_aka_encryption_algorithm is set to 3gpp.

-eap_tls_fast_aka_encryption_algorithm Specifies method of cryptographic encryption of the data to be transmitted between the MN and the AAA Server. Possible Values: 3gpp,3gpp2,usim Default: 3gpp This argument is available when -eap_tls_fast_aka_en is set to true.

-eap_tls_fast_aka_secret_key Specifies the shared key that is known to both the MN and the AAA Server. Default: 0x0123456789ABCDEF0123456789ABCDEF This argument is available when -eap_tls_fast_aka_en is set to true.

-eap_tls_fast_aka_family_key Specifies 32-bit identifier used by the 3GPP2 Enhanced Cryptographic Algorithm. Default: 0x41484147 This argument is available when -eap_tls_fast_aka_encryption_algorithm is set to 3gpp2.

-eap_tls_fast_aka_sqn_en Enables/disables Starting Sequence Number input. Possible Values:true,false

AAA Server Node

73

Default: false This argument is available when -ip_address_allocation_rad is set to true.

-eap_tls_fast_aka_sqn Specifies the Starting Sequence Number. Range: 0- 281474976710655 Default: 1 This argument is available when -eap_tls_fast_aka_sqn_en is set to true.

-eap_tls_fast_aka_permanent_id_en Indicates whether permanent identity can be used. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_aka_en is set to true.

-eap_tls_fast_aka_permanent_id Indicates the permanent identity used on full authentication only. This argument is available when -eap_tls_fast_aka_permanent_id_en is set to true.

-eap_tls_fast_aka_request_id Select Send Request Identity to include AKA-Identity in response to a valid EAP-Request/AKA-Identity from the server. Range: 0- 1 Default: 1 This argument is available when -eap_tls_fast_aka_sqn_en is set to true.

-eap_tls_fast_aka_amf_value With EAP-AKA authentication, in order to reduce the risk of node vulnerability, the AKA algorithm is computed with the AMF separation bit set to 1, and the peer checks to ensure that this is indeed the case. Range: 0- 2 Default: 0 This argument is available when -eap_tls_fast_aka_sqn_en is set to true.

-eap_tls_fast_aka_id_type Specifies the ID type for re-authentication. Possible Values: fast_reauth,pseudo,permanent Default: fast_reauth This argument is available when -eap_tls_fast_aka_en is set to true.

-eap_tls_fast_aka_fast_reauth_max Specifies the Max counter of fast re-authentication. Range: 1-65535 Default: 65535 This argument is available when -eap_tls_fast_aka_id_type is set to fast_reauth.

-eap_tls_fast_aka_tdf_to_para_en Enables/disables apply AKA parameters from TDF. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_aka_en is set to true.

-eap_tls_fast_aka_tdf Specifies the tdf for applying AKA parameters. This argument is available when -eap_tls_fast_aka_tdf_to_para_en is set to true.

-eap_tls_fast_mschapv2_en Enables/disables support for MSCHAPV2 authentication. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_en is set to true.

-eap_tls_fast_mschapv2_password Specifies password for MSCHAPV2 authentication. Default: pword

AAA Server Node

74

This argument is available when -eap_tls_fast_mschapv2_en is set to true.

-eap_tls_fast_mschapv2_tdf_to_para_en Enables/disables apply MSCHAPV2 parameters from tdf. Possible Values:true,false Default: false This argument is available when -eap_tls_fast_mschapv2_en is set to true.

-eap_tls_fast_mschapv2_tdf Specifies the tdf for applying MSCHAPV2 parameters. This argument is available when -eap_tls_fast_mschapv2_tdf_to_para_en is set to true.

-eap_tls_fast_mschapv2_eap_header_en Enables/disables Microsoft PEAP includes EAP header on the EAP message. Possible Values:true,false Default: true This argument is available when -eap_tls_fast_mschapv2_en is set to true.

-eap_tls_ttls_enable Enables/disables TTLS extensions. To enable an authentication method with an AAA Server within EAP-TLS. Possible Values:true,false Default: false This argument is available when -eap_tls_en is set to true.

-eap_tls_ttls_method Specifies authentication method used in TTLS. Possible Values: CHAP,EAP,PAP,MSCHAPV1,MSCHAPV2 Default: CHAP This argument is available when -eap_tls_ttls_enable is set to true.

-eap_tls_ttls_user_name Specifies user name for certain authentication method used in TTLS. This argument is available when -eap_tls_ttls_enable is set to true and -eap_tls_ttls_method is set to one of the following values: {CHAP| PAP| MSCHAPV1| MSCHAPV2}

-eap_tls_ttls_chap_password Specifies password for certain authentication method used in TTLS. This argument is available when -eap_tls_ttls_enable is set to true and -eap_tls_ttls_method is set to one of the following values: {CHAP| PAP| MSCHAPV1| MSCHAPV2}

-eap_tls_tdf_to_para_en Enables/disables apply TLS parameters from TDF. Possible Values:true,false Default: false This argument is available when -eap_tls_en is set to true.

-eap_tls_tdf Specifies the tdf for applying TLS parameters. This argument is available when -eap_tls_tdf_to_para_en is set to true.

-meap_user_name The MN's user name, NAI, or IMSI that will be sent or expected in the MEAP Identity response. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Default: @domain

-meap_expanded Enables/disables support for vendor-specific authentication methods. Range: 0-1 This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Default: 0

AAA Server Node

75

-meap_retries Defines the number of times a message will be transmitted when the expected response or follow-on request has not been received. Enter 0 to disable retries. Range: 0-65535 This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Default: 0

-meap_retry_time Defines the elapsed time (in seconds) between each try until the configured retry count is reached. Range: 0-65535 This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Default: 5

-meap_wimax_mip_en Enables/disables Use the WiMAX MIP Root Key. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-meap_wimax_root_key Use the WiMAX MIP Root Key to enable WiMAX MIP Root Key generation and distribution This argument is available when -meap_wimax_mip_en is set to true. -meap_wimax_mip_scheme Specifies MIP Scheme. Possible Values:PMIP,CMIP Default: PMIP This argument is available when -meap_wimax_mip_en is set to true.

-meap_combined_eap_en Enables/disables Use the MEAP authentication scheme using a challenge combined with a device ID, password and hash algorithm. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-meap_device_identity Indicates the Device ID sending the MEAP challenge This argument is available when -meap_combined_eap_en is set to true. -meap_device_secret Indicates the Device password/secret. Default: 0x1234567890abcdef1234567890abcdef This argument is available when -meap_combined_eap_en is set to true.

-meap_tdf_to_auth_para_en Enables/disables apply authentication parameter from tdf. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

AAA Server Node

76

-meap_tdf_to_auth_para Specifies the TDF for applying authentication parameters. This argument is available when -meap_tdf_to_auth_para_en is set to true. -meap_md5_en Enables/disables MD5 authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-meap_md5_password Specifies password for MD5 authentication. Default: pword This argument is available when -meap_md5_en is set to true.

-meap_md5_tdf_to_para_en Enables/disables apply MD5 parameters from tdf. Possible Values:true,false Default: false This argument is available when -meap_md5_en is set to true.

-meap_md5_tdf Specifies the tdf for applying MD5 parameters. This argument is available when -meap_md5_tdf_to_para_en is set to true. -meap_gtc_en Enables/disables support for GTC authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-meap_gtc_token Specifies token for GTC authentication. Default: pword This argument is available when -meap_gtc_en is set to true.

-meap_gtc_tdf_to_para_en Enables/disables apply GTC parameters from tdf. Possible Values:true,false Default: false This argument is available when -meap_gtc_en is set to true.

-meap_gtc_tdf Specifies the tdf for applying GTC parameters. This argument is available when -meap_gtc_tdf_to_para_en is set to true. -meap_sim_en Enables/disables support for SIM authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-meap_sim_operator_var Specifies the 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Default: 0x63BFA50EE6523365FF14C1F45F88737D This argument is available when -meap_sim_encryption_algorithm is set to 3gpp.

-meap_sim_encryption_algorithm Specifies method of cryptographic encryption of the data to be

AAA Server Node

77

transmitted between the MN and the AAA Server. Possible Values: 3gpp,3gpp2 Default: 3gpp This argument is available when -meap_sim_en is set to true.

-meap_sim_secret_key Specifies the shared key that is known to both the MN and the AAA Server. Default: 0x0123456789ABCDEF0123456789ABCDEF This argument is available when -meap_sim_en is set to true.

-meap_sim_family_key Specifies 32-bit identifier used by the 3GPP2 Enhanced Cryptographic Algorithm. Default: 0x41484147 This argument is available when -meap_sim_encryption_algorithm is set to 3gpp2.

-meap_sim_use_hardcoded_val_en Enables/disables use hard-coded values to define fixed SRES AND Kc values. Possible Values:true,false Default: false This argument is available when -meap_sim_en is set to true.

-meap_sim_sres Specifies the SRES value that will be used to formulate the challenge response for all MNs. Default: 0x000000000000 This argument is available when -meap_sim_use_hardcoded_val_en is set to true.

-meap_sim_kc Specifies the key that will be used to derive new keying material for all MNs. Default: 0x00000000000000000000000000000000 This argument is available when -meap_sim_use_hardcoded_val_en is set to true.

-meap_sim_permanent_id_en Indicates whether permanent identity can be used. Possible Values:true,false Default: false This argument is available when -meap_sim_en is set to true.

-meap_sim_permanent_id Indicates the permanent identity used on full authentication only. This argument is available when -meap_sim_permanent_id_en is set to true. -meap_sim_id_type Specifies the ID type for re-authentication. Possible Values: fast_reauth,pseudo,permanent Default: fast_reauth This argument is available when -meap_sim_en is set to true.

-meap_sim_fast_reauth_max Specifies the Max counter of fast re-authentication. Range: 1-65535 Default: 65535 This argument is available when -meap_sim_id_type is set to fast_reauth.

-meap_sim_tdf_to_para_en Enables/disables apply SIM parameters from TDF. Possible Values:true,false Default: false This argument is available when -meap_sim_en is set to true.

AAA Server Node

78

-meap_sim_tdf_to_sim_para Specifies the tdf for applying SIM parameters. This argument is available when -meap_sim_tdf_to_para_en is set to true. -meap_aka_en Enables/disables support for AKA authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-meap_aka_operator_var Specifies the 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Default: 0x63BFA50EE6523365FF14C1F45F88737D This argument is available when -meap_aka_encryption_algorithm is set to 3gpp.

-meap_aka_encryption_algorithm Specifies method of cryptographic encryption of the data to be transmitted between the MN and the AAA Server. Possible Values: 3gpp,3gpp2,usim Default: 3gpp This argument is available when -meap_aka_en is set to true.

-meap_aka_secret_key Specifies the shared key that is known to both the MN and the AAA Server. Default: 0x0123456789ABCDEF0123456789ABCDEF This argument is available when -meap_aka_en is set to true.

-meap_aka_family_key Specifies 32-bit identifier used by the 3GPP2 Enhanced Cryptographic Algorithm. Default: 0x41484147 This argument is available when -meap_aka_encryption_algorithm is set to 3gpp2.

-meap_aka_sqn_en Enables/disables Starting Sequence Number input. Possible Values:true,false Default: false This argument is available when -ip_address_allocation_rad is set to true.

-meap_aka_sqn Specifies the Starting Sequence Number. Range: 0- 281474976710655 Default: 1 This argument is available when -meap_aka_sqn_en is set to true.

-meap_aka_permanent_id_en Indicates whether permanent identity can be used. Possible Values:true,false Default: false This argument is available when -meap_aka_en is set to true.

-meap_aka_permanent_id Indicates the permanent identity used on full authentication only. This argument is available when -meap_aka_permanent_id_en is set to true. -meap_aka_request_id Selects Send Request Identity to include AKA-Identity in response to a valid MEAP-Request/AKA-Identity from the server. Range: 0- 1 Default: 1 This argument is available when -meap_aka_sqn_en is set to true.

-meap_aka_amf_value With MEAP-AKA authentication, in order to reduce the risk of node

AAA Server Node

79

vulnerability, the AKA algorithm is computed with the AMF separation bit set to 1, and the peer checks to ensure that this is indeed the case. Range: 0- 2 Default: 0 This argument is available when -meap_aka_sqn_en is set to true.

-meap_aka_id_type Specifies the ID type for re-authentication. Possible Values: fast_reauth,pseudo,permanent Default: fast_reauth This argument is available when -meap_aka_en is set to true.

-meap_aka_fast_reauth_max Specifies the Max counter of fast re-authentication. Range: 1-65535 Default: 65535 This argument is available when -meap_aka_id_type is set to fast_reauth.

-meap_aka_tdf_to_para_en Enables/disables apply AKA parameters from TDF. Possible Values:true,false Default: false This argument is available when -meap_aka_en is set to true.

-meap_aka_tdf Specifies the tdf for applying AKA parameters. This argument is available when -meap_aka_tdf_to_para_en is set to true. -meap_mschapv2_en Enables/disables support for MSCHAPV2 authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-meap_mschapv2_password Specifies password for MSCHAPV2 authentication. Default: pword This argument is available when -meap_mschapv2_en is set to true.

-meap_mschapv2_tdf_to_para_en Enables/disables apply MSCHAPV2 parameters from tdf. Possible Values:true,false Default: false This argument is available when -meap_mschapv2_en is set to true.

-meap_mschapv2_tdf Specifies the tdf for applying MSCHAPV2 parameters. This argument is available when -meap_mschapv2_tdf_to_para_en is set to true. -meap_tls_en Enables/disables support for TLS authentication. This argument is available when -mult_eap_en is set to true. OR -aaa_app_application is set to one of the following: {dia_eap | wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value:true,false Default: false

-meap_tls_gen_pairwise_master_key Enables/disables generate pairwise master key. Possible Values:true,false Default: false This argument is available when -meap_tls_en is set to true.

-meap_tls_reauth_en Enables/disables re-authentication. Possible Values:true,false

AAA Server Node

80

Default: false This argument is available when -meap_tls_en is set to true.

-meap_tls_gen_wimax_msk_en Enables/disables generate WiMax MSK. Possible Values:true,false Default: false This argument is available when -meap_tls_en is set to true.

-meap_tls_pre_shared_key_en Enables/disables Pre shared key cipher suites. Possible Values:true,false Default: false This argument is available when -meap_tls_en is set to true.

-meap_tls_pre_shared_key Specifies the pre-shared key. This argument is available when -meap_tls_pre_shared_key_en is set to true. -meap_tls_include_certs_en Enables/disables include certificates. Possible Values:true,false Default: true This argument is available when -meap_tls_en is set to true. AND -meap_tls_pre_shared_key_en is set to false

-meap_tls_private_key_file_type Defines the type of private key file. Possible Values: installed,tdf Default: installed This argument is available when -meap_tls_include_certs_en is set to true.

-meap_tls_private_key_file Specifies the private key file. Possible Values: private-rsa-key.pem, public-rsa-key.pem, x509-certificate.pem Default: private-rsa-key.pem This argument is available when -meap_tls_private_key_file_type is set to installed.

-meap_tls_private_key_tdf Specifies the TDF used as private key file. This argument is available when -meap_tls_private_key_file_type is set to tdf. -meap_tls_x509_cert_file_type Defines the type of X509 certificate file. Possible Values: installed,tdf Default: installed This argument is available when -meap_tls_include_certs_en is set to true.

-meap_tls_x509_cert_file Specifies the X509 certificate file. Possible Values: private-rsa-key.pem,public-rsa-key.pem, x509-certificate.pem Default: private-rsa-key.pem This argument is available when -meap_tls_x509_cert_file_type is set to installed.

-meap_tls_x509_cert_tdf Specifies the TDF used as X509 certificate file. This argument is available when -meap_tls_x509_cert_file_type is set to tdf. -meap_tls_num_of_entries Spesifies the number of entries. Default: 0 This argument is available when -meap_tls_include_certs_en is set to true.

-meap_tls_file_format

AAA Server Node

81

Specifies the file format. Possible Values: RSA,EVP Default: RSA This argument is available when -meap_tls_include_certs_en is set to true.

-meap_tls_first_entry Specifies the first entry. Default: 0 This argument is available when -meap_tls_include_certs_en is set to true.

-meap_tls_peap_en Enables/disables peap TLS authentication. Possible Values:true,false Default: false This argument is available when -meap_tls_en is set to true.

-meap_tls_peap_ver Specifies the version of peap in tls authentication. Range: 0-1 Default: 0 This argument is available when -meap_tls_peap_en is set to true.

-meap_tls_peap_mschapv2_en Enables/disables support for MSCHAPV2 in peaq tls authentication. Possible Values:true,false Default: false This argument is available when -meap_tls_peap_en is set to true.

-meap_tls_peap_mschapv2_password Specifies password for MSCHAPV2 in peaq tls authentication. Default: pword This argument is available when -meap_tls_peap_mschapv2_en is set to true.

-meap_tls_peap_mschapv2_tdf_to_para_en Enables/disables apply MSCHAPV2 parameters from tdf. Possible Values:true,false Default: false This argument is available when -meap_tls_peap_mschapv2_en is set to true.

-meap_tls_peap_mschapv2_tdf Specifies the tdf for applying MSCHAPV2 parameters. meap_tls_peap_mschapv2_tdf_to_para_en true -meap_tls_peap_mschapv2_meap_header_en Enables/disables Microsoft PEAP includes MEAP header on the MEAP message. Possible Values:true,false Default: true This argument is available when -protocol is set to Radius. AND -meap_tls_peap_mschapv2_en is set to true -meap_tls_fast_en Enables/disables fast TLS authentication. Possible Values:true,false Default: false This argument is available when -meap_tls_en is set to true.

-meap_tls_fast_pac_en Defines credential to a peer for optimized network authentication. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_en is set to true.

-meap_tls_fast_md5_en Enables/disables support for MD5 authentication. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_en is set to true.

-meap_tls_fast_md5_password Specifies password for MD5 authentication. Default: pword

AAA Server Node

82

This argument is available when -meap_tls_fast_md5_en is set to true.

-meap_tls_fast_md5_tdf_to_para_en Enables/disables apply MD5 parameters from tdf. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_md5_en is set to true.

-meap_tls_fast_md5_tdf Specifies the tdf for applying MD5 parameters. This argument is available when -meap_tls_fast_md5_tdf_to_para_en is set to true. -meap_tls_fast_gtc_en Enables/disables support for GTC authentication. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_en is set to true.

-meap_tls_fast_gtc_token Specifies token for GTC authentication. Default: pword This argument is available when -meap_tls_fast_gtc_en is set to true.

-meap_tls_fast_gtc_tdf_to_para_en Enables/disables apply GTC parameters from tdf. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_gtc_en is set to true.

-meap_tls_fast_gtc_tdf Specifies the tdf for applying GTC parameters. This argument is available when -meap_tls_fast_gtc_tdf_to_para_en is set to true. -meap_tls_fast_sim_en Enables/disables support for SIM authentication. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_en is set to true.

-meap_tls_fast_sim_operator_var Specifies the 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Default: 0x63BFA50EE6523365FF14C1F45F88737D This argument is available when -meap_tls_fast_sim_encryption_algorithm is set to 3gpp. -meap_tls_fast_sim_encryption_algorithm Specifies method of cryptographic encryption of the data to be transmitted between the MN and the AAA Server. Possible Values: 3gpp,3gpp2 Default: 3gpp This argument is available when -meap_tls_fast_sim_en is set to true.

-meap_tls_fast_sim_secret_key Specifies the shared key that is known to both the MN and the AAA Server. Default: 0x0123456789ABCDEF0123456789ABCDEF This argument is available when -meap_tls_fast_sim_en is set to true.

-meap_tls_fast_sim_family_key Specifies 32-bit identifier used by the 3GPP2 Enhanced Cryptographic Algorithm. Default: 0x41484147 This argument is available when -meap_tls_fast_sim_encryption_algorithm is set to 3gpp2. -meap_tls_fast_sim_use_hardcoded_val_en Enables/disables use hard-coded values to define fixed SRES AND Kc values. Possible Values:true,false Default: false

AAA Server Node

83

This argument is available when -meap_tls_fast_sim_en is set to true. -meap_tls_fast_sim_sres Specifies the SRES value that will be used to formulate the challenge response for all MNs. Default: 0x000000000000 This argument is available when -meap_tls_fast_sim_use_hardcoded_val_en is set to true.

-meap_tls_fast_sim_kc Specifies the key that will be used to derive new keying material for all MNs. Default: 0x00000000000000000000000000000000 This argument is available when -meap_tls_fast_sim_use_hardcoded_val_en is set to true.

-meap_tls_fast_sim_permanent_id_en Indicates whether permanent identity can be used. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_sim_en is set to true.

-meap_tls_fast_sim_permanent_id Indicates the permanent identity used on full authentication only. This argument is available when -meap_tls_fast_sim_permanent_id_en is set to true. -meap_tls_fast_sim_id_type Specifies the ID type for re-authentication. Possible Values: fast_reauth,pseudo,permanent Default: fast_reauth This argument is available when -meap_tls_fast_sim_en is set to true. -meap_tls_fast_sim_fast_reauth_max Specifies the Max counter of fast re-authentication. Range: 1-65535 Default: 65535 This argument is available when -meap_tls_fast_sim_id_type is set to fast_reauth.

-meap_tls_fast_sim_tdf_to_para_en Enables/disables apply SIM parameters from TDF. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_sim_en is set to true. -meap_tls_fast_sim_tdf_to_sim_para Specifies the tdf for applying SIM parameters. This argument is available when -meap_tls_fast_sim_tdf_to_para_en is set to true. -meap_tls_fast_aka_en Enables/disables support for AKA authentication. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_en is set to true.

-meap_tls_fast_aka_operator_var Specifies the 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Default: 0x63BFA50EE6523365FF14C1F45F88737D This argument is available when -meap_tls_fast_aka_encryption_algorithm is set to 3gpp. -meap_tls_fast_aka_encryption_algorithm Specifies method of cryptographic encryption of the data to be transmitted between the MN and the AAA Server. Possible Values: 3gpp,3gpp2,usim Default: 3gpp This argument is available when -meap_tls_fast_aka_en is set to true.

AAA Server Node

84

-meap_tls_fast_aka_secret_key Specifies the shared key that is known to both the MN and the AAA Server. Default: 0x0123456789ABCDEF0123456789ABCDEF This argument is available when -meap_tls_fast_aka_en is set to true. -meap_tls_fast_aka_family_key Specifies 32-bit identifier used by the 3GPP2 Enhanced Cryptographic Algorithm. Default: 0x41484147 This argument is available when -meap_tls_fast_aka_encryption_algorithm is set to 3gpp2.

-meap_tls_fast_aka_sqn_en Enables/disables Starting Sequence Number input. Possible Values:true,false Default: false This argument is available when -ip_address_allocation_rad is set to true. -meap_tls_fast_aka_sqn Specifies the Starting Sequence Number. Range: 0- 281474976710655 Default: 1 This argument is available when -meap_tls_fast_aka_sqn_en is set to true. -meap_tls_fast_aka_permanent_id_en Indicates whether permanent identity can be used. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_aka_en is set to true. -meap_tls_fast_aka_permanent_id Indicates the permanent identity used on full authentication only. This argument is available when -meap_tls_fast_aka_permanent_id_en is set to true. -meap_tls_fast_aka_request_id Select Send Request Identity to include AKA-Identity in response to a valid MEAP-Request/AKA-Identity from the server. Range: 0- 1 Default: 1 This argument is available when -meap_tls_fast_aka_sqn_en is set to true. -meap_tls_fast_aka_amf_value With MEAP-AKA authentication, in order to reduce the risk of node vulnerability, the AKA algorithm is computed with the AMF separation bit set to 1, and the peer checks to ensure that this is indeed the case. Range: 0- 2 Default: 0 This argument is available when -meap_tls_fast_aka_sqn_en is set to true.

-meap_tls_fast_aka_id_type Specifies the ID type for re-authentication. Possible Values: fast_reauth,pseudo,permanent Default: fast_reauth This argument is available when -meap_tls_fast_aka_en is set to true.

-meap_tls_fast_aka_fast_reauth_max Specifies the Max counter of fast re-authentication. Range: 1-65535 Default: 65535 This argument is available when -meap_tls_fast_aka_id_type is set to fast_reauth.

-meap_tls_fast_aka_tdf_to_para_en Enables/disables apply AKA parameters from TDF. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_aka_en is set to true. -meap_tls_fast_aka_tdf Specifies the tdf for applying AKA parameters.

AAA Server Node

85

This argument is available when -meap_tls_fast_aka_tdf_to_para_en is set to true. -meap_tls_fast_mschapv2_en Enables/disables support for MSCHAPV2 authentication. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_en is set to true. -meap_tls_fast_mschapv2_password Specifies password for MSCHAPV2 authentication. Default: pword This argument is available when -meap_tls_fast_mschapv2_en is set to true.

-meap_tls_fast_mschapv2_tdf_to_para_en Enables/disables apply MSCHAPV2 parameters from tdf. Possible Values:true,false Default: false This argument is available when -meap_tls_fast_mschapv2_en is set to true. -meap_tls_fast_mschapv2_tdf Specifies the tdf for applying MSCHAPV2 parameters. This argument is available when -meap_tls_fast_mschapv2_tdf_to_para_en is set to true. -meap_tls_fast_mschapv2_meap_header_en Enables/disables Microsoft PEAP includes MEAP header on the MEAP message. Possible Values:true,false Default: true This argument is available when -meap_tls_fast_mschapv2_en is set to true.

-meap_tls_ttls_enable Enables/disables TTLS extensions. To enable an authentication method with an AAA Server within MEAP-TLS. Possible Values:true,false Default: false This argument is available when -meap_tls_en is set to true.

-meap_tls_ttls_method Specifies authentication method used in TTLS. Possible Values: CHAP,EAP,PAP,MSCHAPV1,MSCHAPV2 Default: CHAP This argument is available when -meap_tls_ttls_enable is set to true.

-meap_tls_ttls_user_name Specifies user name for certain authentication method used in TTLS. This argument is available when -meap_tls_ttls_enable is set to true. AND -meap_tls_ttls_method is set to one of the following: {CHAP| PAP| MSCHAPV1| MSCHAPV2} -meap_tls_ttls_chap_password Specifies password for certain authentication method used in TTLS. This argument is available when -meap_tls_ttls_enable is set to true. AND -meap_tls_ttls_method is set to one of the following: {CHAP| PAP| MSCHAPV1| MSCHAPV2} -meap_tls_tdf_to_para_en Enables/disables apply TLS parameters from TDF. Possible Values:true,false Default: false This argument is available when -meap_tls_en is set to true.

-meap_tls_tdf Specifies the tdf for applying TLS parameters. This argument is available when -meap_tls_tdf_to_para_en is set to true. -aaa_app_application Provisions the Application, Auth-Application and Acct-Application AVPs in messages sent by a node and identifies the Diameter application supported by the node. Default: nasreq

AAA Server Node

86

This argument is available when -protocol is set to Diameter. Possible value: nasreq,dia_eap,wimax_mipv4,wm_interface, s6b_interface,sta_interface,s6b_sta_swx_inerface Default: nasreq -aaa_app_wimax_ha4_com_code_en Enables/disables Wimax Mip4 option for application. Possible Values:true,false Default: false This argument is available when -aaa_app_application is set to wimax_mipv4.

-aaa_app_wimax_ha4_com_code WiMAX HA4 Command Code checkbox is only available when the Wimax Mip4 option is selected This argument is available when -aaa_app_wimax_ha4_com_code_en is set to true. -aaa_app_state_mode Specifies the state mode for Diameter application. Possible Values: stateful,stateless Default: stateful This argument is available when -protocol is set to Diameter.

-aaa_app_acct_ts_time Specifies the accounting server TS time for Diameter application. Range: 0-65535 Default: 0 This argument is available when -protocol is set to Diameter.

-aaa_app_user_name Specifies the user name for Diameter application Default: @domain This argument is available when -protocol is set to Diameter.

-aaa_app_password_en Enables/disables password input for Diameter Application. Possible Values:true,false Default: false This argument is available when -protocol is set to Diameter. -aaa_app_password Specifies the password for Diameter Application. Default: secret This argument is available when -aaa_app_password_en is set to true.

-aaa_app_mul_dea_msg Defines whether enable multiround DEA message. aaa_app_application {dia_eap |wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value: 0,1 Default: 0 -aaa_app_succ_dea_msg Defines whether enable success DEA message. aaa_app_application {dia_eap |wimax_mipv4 | wm_interface | s6b_interface | sta_interface | s6b_sta_swx_inerface} Possible value: 0,1 Default: 0 -aaa_app_meap_user_name Specifies the user name for Diameter multiple EAP. Default: @domain This argument is available when -mult_eap_en is set to true. -dia_product_name Provisions the Product-Name AVP in CER and CEA messages. The default server name depends on the test case. Default: Landslide NAS This argument is available when -protocol is set to Diameter.

-dia_vendor_id

AAA Server Node

87

Specifies the application's vendor-specific ID or enterprise code, which is used to provision the Vendor-ID AVP in CER or CEA messages sent by a node. Default: 10415 This argument is available when -protocol is set to Diameter.

-dia_acct_avp_db_size Specifies AVP configuration DB size for AAA Diameter accounting. Range: 200-4000 Default: 200 This argument is available when -protocol is set to Diameter. -dia_auth_avp_db_size Specifies AVP configuration DB size for AAA Diameter authentication. Range: 200-4000 Default: 200 This argument is available when -protocol is set to Diameter. -dia_trans_protocol Specifies the transmission protocol. Possible Values: tcp,sctp Default: tcp This argument is available when -protocol is set to Diameter.

-dia_num_peers Specifies the number of peers. The server node will refuse any attempted TCP connections once the maximum number of connections have been established. Range: 1-10 Default: 1 This argument is available when -protocol is set to Diameter. -dia_retry_time Specifies the number of milliseconds for retry timer. Range: 1-100000 Default: 10000 This argument is available when -protocol is set to Diameter. -dia_watchdog_time Specifies the number seconds to wait before sending a DWR to a peer. If any Diameter message is received from the peer before the time expires, the timer is reset. Range: 0-65535 Default: 0 This argument is available when -protocol is set to Diameter.

-dia_proxy_en indicate whether a Diameter proxy server is used between the peers. Possible Values:true,false Default: false This argument is available when -protocol is set to Diameter.

Return Values: The lsh::aaa_server_node_config function returns a keyed list using the following keys (with the corresponding data):

tc_handle The test case handle, which will be used when you want to modify the test case, or configure more parameters on this test case. Will be returned only when the status is 1 and the -mode is create.

status Success (1) or failure (0) of the operation


Examples: set ret [lsh::aaa_server_node_config -mode create\ -test_hnd $test\ -protocol "Radius"\ -ts_name $ts_name\ -aaa_server_phy_intf "eth1"\

AAA Server Node

88

-aaa_server_intf_ip_addr "10.71.50.106"\ ]

keylget ret status sta if {$sta == $FAIL} { puts "failed to create aaa_server node test session. $ret" exit; } else { puts "successfully create aaa_server node test session" keylget ret tc_handle tc }

DHCP Server Node

89

DHCP Server Node

Functions:lsh::dhcp_server_node_config

lsh::dhcp_server_node_config

Name: lsh::dhcp_server_node_config

Description: Creates or modifies DHCP Server Node test case. This function only serves as the basic configurations required by the test case. To run the test case successfully, you must call other sub-functions that make the configurations complete.

Synopsis: lsh::dhcp_server_node_config -mode {create|modify} -test_hnd <test_session_handle> -tc_hnd <test_case_handle> -ts_name <test_server_name> -process_bmsg_en {true|false} -subscribers_num <1-2000000> -dhcp_server_node_intf_type {eth|atm} -dhcp_server_node_phy_intf {physical interface} -dhcp_server_node_intf_ip_addr <a.b.c.d> -dhcp_server_node_vpi <HEX> -dhcp_server_node_vci <0-4000> -dhcp_server_node_num <NUMERIC> -dhcp_server_node_mac_addr <MAC> -dhcp_server_node_next_hop <a.b.c.d> -dhcp_server_node_out_bound_traffic_port <ANY> -dhcp_server_node_addr_err_inj {0|1|2|3|4|5} -ip_addr_type {IPV4|IPV6} -req_wait_time <1-1000000> -t1_option_en {true|false} -t2_option_en {true|false} -pro_ext_en {true|false} -pro_ext_msg_inc {"0 0 1"| "0 1 0"|"0 1 1"|"1 0 0"|"1 0 1"|"1 1 0"|"1 1 1"} -pro_ext_data <extension data>

Available Sub-Function(s): lsh::ip_pools_config: Used to configure the IP Pools on this test case.

Arguments:

-mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - create a new test case and the parameters in the test session specified by the -test_hnd modify - modify the parameters on the test case specified by the -tc_hnd. -test_hnd Specify the test session handle, in which the test case will be added. This argument is mandatory when the -mode is set to create. -tc_hnd Specify the test case handle. This argument is mandatory when the -mode is set to modify. It can modify the parameters configured on this test case.

DHCP Server Node

90

-ts_name Specify on which the test case will be added. This argument is mandatory when the -mode is set to create. -process_bmsg_en Determine whether the DHCP server will process the broadcast DHCP messages or not. Possible values: true, false Default: false -subscribers_num The number of Mobile Subscribers. In DHCP Server Node test case, it indicates the number of simultaneous client bindings that can be supported by the server node. System resources are reserved for the provisioned number of sessions whether they are used or not. Range: 1-2000000, the maximum number depending on the test system's licensed capability. Default: 1 -dhcp_server_node_intf_type The type of the physical interface. Possible Values: eth, atm Default: eth

-dhcp_server_node_phy_intf Specify which enabled Ethernet Interface will be used for DHCP Server. It is the Ethernet interface name. such as "eth1","eth2". -dhcp_server_node_intf_ip_addr The IP address of the DHCP Server node. When the physical interface type is "eth", it is the DHCP Server node's actual IP address, it is one of the address pool associated with physical interface. When the physical interface type is "atm", it is the source address for all the traffic sent by the node. The address that you enter will be incremented for each node. -dhcp_server_node_vpi The VPI value, it is mandatory when the physical interface type is atm. Dependency: { dhcp_server_node_intf_type: atm} -dhcp_server_node_vci The starting VCI value, if there is more than one DHCP server node, the VCI value will increment for each node. Range: 0-4000 Default: 0 Dependency: { dhcp_server_node_intf_type: atm}

-dhcp_server_node_num The number of the DHCP Server node. Default: 1 -dhcp_server_node_mac_addr The Mac address of the DHCP Server node.

-dhcp_server_node_next_hop device's IP address in the test network to use this IP address as the next hop.

-dhcp_server_node_out_bound_traffic_port With this you can force the packets to send out from the selected interface. -dhcp_server_node_addr_err_inj Choose the type of the error injection to be used during the test. Possible value: 0 - None 1 - Packet Discard 2 - IP Total Length Set to 0 3 - IP Checksum Corrupted

DHCP Server Node

91

4 - Payload Checksum Corrupted 5-Bad Source IP Default: 0 -ip_addr_type Specify the type of addresses that the server node will allocate. Possible values: IPV4, IPV6 Default: IPV4 -req_wait_time The number of milliseconds that the server node will wait for a message from the client in response to a DHCPOFFER (IPV4) or Advertise (IPV6) message. If the request is not received before the timer expires, the server node releases the address reserved for the client back to the address pool. Range: 0 -1,000,000 Default: 1000 -t1_option_en Use the checkbox to include the Renewal Time Value option in messages sent to the client. This option indicates that the client should renew its lease with the server when the timer expires. The client will send a unicast request to the server in an attempt to extend its lease. The T1 timer default is 0.5 x the duration of the lease. Possible values: true, false Default: false

-t2_option_en Use the checkbox to include the Rebinding Time Value option in messages sent to the client. This option indicates that the client should rebind its address with a server if it has not received an acknowledgement to a renewal request when the timer expires. The client will send a broadcast request in an attempt to extend its lease. The T2 timer default is 0.875 x the duration of the lease. Possible values: true, false Default: false -pro_ext_en Determine whether the extension value will be included in the DHCP response message. Possible values: true, false Default: false

-pro_ext_msg_inc Specify in which kind of DHCP server response message the extension data will be included. Possible value: "0 0 1" -the extension value will be included in NAK message. "0 1 0" -the extension value will be included in ACK message. "0 1 1" -the extension value will be included in ACK, NAK message. "1 0 0" -the extension value will be included in Offer message. "1 0 1" -the extension value will be included in Offer, NAK message. "1 1 0"-the extension value will be included in Offer, ACK message. "1 1 1" -the extension value will be included in Offer, ACK , NAK message.

-pro_ext_data Specify the extension data will be included in the DHCP server response message. The value is in hex format. Related measurements: DHCP: Discovers Received - The number of DHCPDISCOVER messages received by the server during IPv4 testing. Offers Sent - The number of DHCPOFFER messages sent by the server during IPv4 testing. Acks Sent - The number of DHCPACK messages sent by the server during IPv4 testing. Naks Sent - The number of DHCPNAK messages sent by the server during IPv4 testing. Solicits Received - The number of Solicit messages received by the server

DHCP Server Node

92

during IPv6 testing. Advertises Sent - The number of Advertise messages sent by the server during IPv6 testing. Replies Sent - The number of Reply messages sent by the server during IPv6 testing. Requests Received - The number of DHCPREQUEST or Request messages received by the server during IPv4 or IPv6 testing. Renews Received - The number of Renew messages received by the server during IPv6 testing. Releases Received - The number of DHCPRELEASE or Release messages received by the server during IPv4 or IPv6 testing. Declines Received - The number of DHCPDECLINE or Decline messages received by the server during IPv4 or IPv6 testing. Sessions Not Found - The number of times a client attempted to renew an address for a binding that was not found on the server. Mismatch Requests Received - The number DHCPREQUEST or Request messages received during IPv4 or IPv6 testing that contained invalid identifiers. No Free Sessions - The number of times a client attempted to obtain an address when the addresses in a requested pool or in all address pools were being used by other clients. Poorly Formed Received - The number of DHCP messages received by the server that were incorrectly formatted. Wait Request Timeouts - The number of times a DHCPREQUEST or Request message was not received by the server before the wait time expired. Lease Timeouts - The number of times a lease expired without being renewed by the client.

DHCP Server Node: Received Packets - The number of packets received by the nodes. Sent Packets - The number of packets sent by the node. Received Bytes - The number of bytes received. Sent Bytes - The number of bytes sent. Invalid Packets - The number of IP packets received that contained an unknown protocol type or an invalid IP checksum. Total Packets - The number of packets processed by the node. Total Bytes - The number of bytes processed by the node. Total Received Packets Discarded - The number of incoming packets discarded. Total Sent Packets Discarded - The number of outgoing packets discarded. Total Discarded Packets - The total number of packets discarded.

Return Values: tc_handle Test case handle, which will be used when you want to modify the test case, or configure more parameters on this test case. Will be returned only when the status is 1 and the -mode is create.

status Success (1) or failure (0) of the operation.


DHCP Server Node

93

Examples: The following is to create a DHCP Server Node test case with basic configuration in test session $test. set ret [::lsh::dhcp_server_node_config \ -mode create\ -test_hnd $test\ -ts_name ls-ts3 \ -process_bmsg_en true\ -subscribers_num 2\ -dhcp_server_node_phy_intf eth1\ -dhcp_server_node_intf_ip_addr 10.155.2.48\ -dhcp_server_node_out_bound_traffic_port eth1\ -t1_option_en true\ -t2_option_en true\ -ip_addr_type IPV4\ -req_wait_time 2000\ -pro_ext_en true\ -pro_ext_msg_inc "0 0 1"\ -pro_ext_data a357]

GGSN Node

94

GGSN Node

Functions:lsh::ggsn_node_config

lsh::ggsn_node_config

Name: lsh::ggsn_node_config

Purpose: Creates or modifies Gateway GPRS Support Node (GGSN) Node test case. This function only serves as the basic configurations required by the test case. To run the test case successfully, you must call other sub-functions that make the configurations complete.

Synopsis: lsh::ggsn_node_config -mode {create|modify} -test_hnd <test session handle> -tc_hnd <test case handle> -ts_name <test server name> -pdp_type {ipv4|ipv6|ipv4v6|ppp} -init_delete_pdp_context_en {0|1} -delete_pdp_context_timer <0- 4294967295 > -relay_agent_en {true|false} -relay_addr <IP> -dhcp_server_addr <IP> -subs_num <1-400000> -prim_pdp_contexts_num <1-11> -sec_pdp_contexts_num <0-10> -pdp_ipv4_pool <IPV4> -pdp_ipv6_pool <IPV6> -context_to_dscp_en {true|false} -dscp_assign <ANY> -traffic_mtu <130-9300> -gi_node_en {true|false} -gi_node_intf_type {eth|atm} -gi_node_phy_intf <ANY> -gi_node_intf_ip_addr <IP> -gi_node_vpi <ANY> -gi_node_vci <NUMERIC> -gi_node_node_num <NUMERIC> -gi_node_mac_addr <MAC> -gi_node_next_hop <IP> -gi_node_out_bound_traffic_port <ANY> -gi_node_addr_err_inj <0-5> -sgsn_sut_name <sgsn sut> -sgsn_v0_ctrl_port <NUMERIC> -sgsn_v0_usr_port <NUMERIC> -sgsn_v1_ctrl_port <NUMERIC> -sgsn_v1_usr_port <NUMERIC> -ctrl_node_intf_type {eth|atm} -ctrl_node_phy_intf <ANY> -ctrl_node_intf_ip_addr <IP> -ctrl_node_vpi <ANY> -ctrl_node_vci <NUMERIC> -ctrl_node_node_num <NUMERIC> -ctrl_node_mac_addr <MAC> -ctrl_node_next_hop <IP> -ctrl_node_out_bound_traffic_port <ANY> -ctrl_node_addr_err_inj <0-5> -user_node_en {true|false} -user_node_intf_type {eth|atm}

GGSN Node

95

-user_node_phy_intf <ANY> -user_node_intf_ip_addr <IP> -user_node_vpi <ANY> -user_node_vci <NUMERIC> -user_node_node_num <NUMERIC> -user_node_mac_addr <MAC> -user_node_next_hop <IP> -user_node_out_bound_traffic_port <ANY> -user_node_addr_err_inj <0-5> -direct_tunnel_en {yes|no} -direct_tunnel_one_shot_err_indication {yes|no} -direct_tunnel_err_timer <0-4294967295> -direct_tunnel_err_pkt <0-4294967295> -direct_tunnel_update_request_delay <0-4294967295> -auth_type {none|pap|chap} -pap_password <ANY> -pap_peer_id <NUMERIC> -chap_challenge <HEX> -chap_id <0-255> -chap_name <ANY> -chap_secret <ANY> -l2tp_vpn_en {true|false} -billing_en {true|false} -qos_updates_en {true|false}

Available Sub Functions: lsh::gtp_config: Used to configure the GTP on this test case lsh::ppp_config: Used to configure the PPP on this test case lsh::gtp'_config: Used to configure the gtp' on the test case lsh::l2tp_config: Used to configure the l2tp on the test case lsh::qos_update_config: Used to configure the Qos Update on the test case

Arguments:

-mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - create a new test case and the parameters in the test session specified by the -test_hnd modify - modify the parameters on the test case specified by the -tc_hnd. -test_hnd Specifies the test session handle on which the test case is added. This argument is mandatory when the -mode is set to create. -tc_hnd Specifies the test case handle. This argument is mandatory when the -mode is set to modify. It can modify the parameters configured on this test case. -ts_name Specifies on which the test case will be added. This argument is mandatory when the -mode is set to create. -pdp_type Packet Data Protocol type that is requested by the SGSN nodes or supported by a GGSN node. Possible values: ipv4, ipv6, ipv4v6 or ppp. Default: ipv4 -init_delete_pdp_context_en Determines whether to initiate the Delete PDP Context. If it is true, the SGSN sends a Delete PDP Context Request to the GGSN, triggering the GGSN to release the context and tear down its tunnel with the SGSN. Upon

GGSN Node

96

completion, the GGSN replies with a Delete PDP Context Accept, allowing the SGSN to tear down its tunnel with the GGSN. Possible values: 0 or 1. Default: 0 -delete_pdp_context_timer Default: 0 Range: 0- 4294967295 Dependency: init_delete_pdp_context_en 1 -relay_agent_en Enables or disbales the DHCP relay agent. If it is true (enabled), you must also specify relay_addr and the dhcp_server_addr. Default: false -relay_addr The IP address of the DHCP Relay agent. Only available when the relay_agent_en is true -dhcp_server_addr The IP address of the DHCP Server. Only available when the relay_agent_en is true -subs_num The number of the subscribers Default: 1 Range: 1-400000 -prim_pdp_contexts_num The number of Primery PDP contexts Default: 1 Range: 1-11 -sec_pdp_contexts_num The number of Secondary PDP contexts. Default: 0 Range: 0-10 Note: The total number of the contexts should be no larger than 11. The total number of the contexts is -prim_pdp_contexts_num + -prim_pdp_contexts_num* -sec_pdp_contexts_num. If -prim_pdp_contexts_num is 3, and the -sec_pdp_contexts_num is 2, then the total contexts number is 3 + 3*2 = 9 -pdp_ipv4_pool Specifies the PDP IPv4 Address Pool. Dependency: relay_agent_en false -pdp_ipv6_pool Specifies the PDP IPv6 Address Pool. Dependency: relay_agent_en false -context_to_dscp_en Specifies whether to enable the context to DSCP. Default: false -dscp_assign Specifies the DSCP assignments. Default: 0 Dependency: context_to_dscp_en true -traffic_mtu The maximum transmission unit of the data traffic. Default: 1400 Range: 130-9300 -gi_node_en Specifies if you want to enable the Gi Node. Default: false -gi_node_intf_type If the Gi Node is enabled, you can specify the interface type. Default: eth

GGSN Node

97

Dependency: gi_node_en true -gi_node_phy_intf If the Gi Node is enabled, you can specify the physical interface of the Gi Node. Dependency: gi_node_en true -gi_node_intf_ip_addr If the Gi Node is enabled, you can specify the IP address of Gi Node. Dependency: gi_node_en true -gi_node_vpi If the Gi Node is enabled, and the interface type is atm, you can specify the vpi of Gi Node. Dependency: gi_node_intf_type atm -gi_node_vci If the Gi Node is enabled, and the interface type is atm, you can specify the vci of Gi Node. Default: 0 Dependency: gi_node_intf_type atm -gi_node_node_num Specifies the number of the Gi Node. Default: 1 Dependency: gi_node_en true -gi_node_mac_addr Specifies the MAC address of the Gi Node. Dependency: gi_node_en true -gi_node_next_hop If the Gi Node is enabled, you can specify the next hop of the Gi Node. Dependency: gi_node_en true -gi_node_out_bound_traffic_port If the Gi Node is enabled, you can specify the outbound traffic port of the Gi Node. Dependency: gi_node_en true -gi_node_addr_err_inj If the Gi Node is enabled, you can specify the error inject of the Gi Node. Default: 0 Range: 0-5 Dependency: gi_node_en true -sgsn_sut_name The name of the SGSN SUT, the sut should have already been added to the TAS. -sgsn_v0_ctrl_port The V0 control port of the SGSN. Default: 3386 -sgsn_v0_usr_port The V0 user port of the SGSN. Default: 3386 -sgsn_v1_ctrl_port The V1 control port of the SGSN Default: 2123 -sgsn_v1_usr_port The V1 user port of the SGSN Default: 2152 -ctrl_node_intf_type The interface type of the control node Possible values : eth, atm Default: eth

GGSN Node

98

-ctrl_node_phy_intf The physical interface of the control node -ctrl_node_intf_ip_addr The IP address of the control node -ctrl_node_vpi Specifies the vpi of the control node Dependency: ctrl_node_intf_type atm -ctrl_node_vci Specifies the vci of the control node Default: 0 Dependency: ctrl_node_intf_type atm -ctrl_node_node_num The number of the control node Default: 1 -ctrl_node_mac_addr The MAC address of the control node -ctrl_node_next_hop The next hope of the control node -ctrl_node_out_bound_traffic_port The outbound traffic port of the Control Node -ctrl_node_addr_err_inj The error inject of the Control Node Default: 0 Range: 0-5 -user_node_en Specifies whether to enable the User Node Default: false -user_node_intf_type Specifies the interface type of the User Node Default: eth Dependency: user_node_en true -user_node_phy_intf Specifies the physical interface of the User Node Dependency: user_node_en true -user_node_intf_ip_addr Specifies the IPv4 address of the User Node Dependency: user_node_en true -user_node_vpi Specifies the vpi of the User Node Dependency: user_node_intf_type atm -user_node_vci If you enabled the User Node and the interface type is atm, then you can specify the vci of the User Node Default: 0 Dependency: user_node_intf_type atm -user_node_node_num The number of the User Node. Default: 1 Dependency: user_node_en true -user_node_mac_addr Specifies the MAC address of the User Node Dependency: user_node_en true -user_node_next_hop

GGSN Node

99

Specifies the next hop of the User Node Dependency: user_node_en true -user_node_out_bound_traffic_port Specifies the outbound traffic port of the User Node Dependency: user_node_en true -user_node_addr_err_inj Specifies the error inject of the User Node Default: 0 Range: 0-5 Dependency: user_node_en true -direct_tunnel_en Specifies whether to enable the direct tunnel. Possible values: yes, no Default: no -direct_tunnel_one_shot_err_indication Specifies the whether to enable the one shot error infication Possible values: yes, no Default: no Dependency: direct_tunnel_en yes -direct_tunnel_err_timer Specifies the error indication timer. Default: 0 Range: 0-4294967295 Dependency: direct_tunnel_en yes -direct_tunnel_err_pkt Specifies the error indication packet count. Default: 0 Range: 0-4294967295 Dependency: direct_tunnel_en yes -direct_tunnel_update_request_delay Specifies the update request delay. Default: 0 Range: 0-4294967295 Dependency: direct_tunnel_en yes -auth_type Specifies the authentication method. Possible values: none, pap, chap Default: none -pap_password Specifies the password of pap authentication. Default: Secret Dependency: auth_type pap -pap_peer_id Specifies the the peer id of pap authentication. Default: Secret Dependency: auth_type pap -chap_challenge Specifies the challenge of CHAP authentication. Default: ABCD Dependency: auth_type chap -chap_id Specifies the identifier of CHAP authentication. Default: 0 Range: 0-255 Dependency: auth_type chap -chap_name Specifies the name of CHAP authentication. Default: MSName

GGSN Node

100

Dependency: auth_type chap -chap_secret Specifies the secret of CHAP authentication. Default: secret Dependency: auth_type chap -l2tp_vpn_en Specifies whether to enable the l2tp VPN connection on the GGSN Node. Default: false -billing_en Specifies whether to enable the billing on the GGSN Node. Default: false -qos_updates_en Specifies whether to enable the Qos Updates on the GGSN Node. Default: false

Return Values: The lsh::ggsn_node_config function returns a keyed list using the following keys (with the corresponding data): tc_handle The test case handle, which will be used when you want to modify the test case, or configure more parameters on this test case. Will be returned only when the status is 1 and the -mode is create. status Success (1) or failure (0) of the operation. log Returned only when the status is 0

Examples: set ret [ ::lsh::ggsn_node_config \ -sgsn_sut_name $sgsn_sut \ -test_hnd $test \ -ctrl_node_phy_intf "eth1" \ -ts_name $ts_name \ -mode create \ -subs_num 10 \ -ctrl_node_intf_ip_addr $ts_eth1 \ -pdp_ipv4_pool 192.1.1.6 \ -pdp_ipv6_pool 2001::0005 \ -l2tp_vpn_en false\ -qos_updates_en false\ -pdp_type ipv4 \ -billing_en false]

Sample output for example shown above: {status 1} {tc_handle java0x8}

IP APP Node

101

IP APP Node

Functions:lsh::ip_app_node_config

lsh::ip_app_node_config

Name: lsh::ip_app_node_config

Purpose: Creates or modifies the IP Application Node test case. This function only serves as the basic configurations required by the test case. To run the test case successfully, you must call other sub-functions that make the configurations complete.

Synopsis: lsh::ip_app_node_config -mode {create|modify} -test_hnd <test session handle> -tc_hnd <test case handle> -ts_name <ANY> -test_activity {Capacity_Test|Inter-PDSN|Session_Loading_Test} -intf_type <ANY> -phy_intf <ANY> -intf_ip_addr <IP> -vpi <0-15> -vci <0-4000> -node_num <NUMERIC> -mac_addr <MAC> -next_hop <IP> -out_bound_traffic_port <ANY> -mobile_node_addr_err_inj <0-5> -mobile_node_addr_ip_encap {0|1} -activation_rate <0.0010-3000> -deactivation_rate <0.0010-3000> -session_interval_shape {Fixed|Poisson|Normal|Uniform} -session_interval_deviation <NUMERIC> -test_type <ANY> -const_session_loading_en {true|false} -session_hold_time <1-100000> -session_pending_time <1-100000> -mobility_delay_time <NUMERIC> -session_start_re {true|false} -start_type {When_All_Sessions_Started|When_Session_Started} -mobility_mode {Single_Handoff|Continuous_Handoff} -mobility_rate <0.001-1000.0> -mobility_rate_interval_shap {Normal|Fixed|Uniform|Posson} -mobility_interval_deviation <NUMERIC> -aaa_server_en {true|false} -data_ipsec_tunnel_en {true|false} -dhcp_en {true|false} -external_data_en {0|1} -data_traffic_en {Enabled|Disabled}

Available Sub Functions: lsh::aaa_radius_client_config: Used to configure the radius client on this test case. lsh::dhcp_client_config: Used to configure the DHCP client and the relay agent on this test case

Arguments:

IP APP Node

102

-mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - create a new test case and the parameters in the test session specified by the -test_hnd modify - modify the parameters on the test case specified by the -tc_hnd -test_hnd Specifies the test session handle, in which the test case will be added. This argument is mandatory when the -mode is set to create. -tc_hnd Specifies the test case handle. This argument is mandatory when the -mode is set to modify. It can modify the parameters configured on this test case. -ts_name Specifies on which the test case will be added. This argument is mandatory when the -mode is set to create. -test_activity Specifies the test activity. Possible values: Capacity_Test, Inter-PDSN, Session_Loading_Test Default: Capacity_Test -intf_type The interface type of the IP APP node. Possible values: eth, atm. Default: eth -phy_intf The interface of the IP APP node. -intf_ip_addr The IP address of the IP APP node -vpi The VPI of the IP APP node, it can be used only when the interface type is set to atm. Range: 0-15 Dependency: intf_type atm -vci The VCI of the IP APP node, it can be used only when the interface type is set to atm. Default: 0 Range: 0-4000 Dependency: intf_type atm -node_num The number of the IP APP Node. Default: 1 -mac_addr The MAC address of the IP APP Node. -next_hop The next hop of the IP APP Node. -out_bound_traffic_port The outbound traffic port of the IP APP Node. -mobile_node_addr_err_inj Choose the type of the error injection to be used during the test. Possible value: 0 - None 1 - Packet Discard 2 - IP Total Length Set to 0 3 - IP Checksum Corrupted 4 - Payload Checksum Corrupted

IP APP Node

103

5- Bad Source IP Default: 0 Range: 0-5 Dependency: intf_type eth -mobile_node_addr_ip_encap The IP encapsulation of the IP APP node. it can be used when the interface type is atm. Default: 0 Dependency: intf_type atm -activation_rate The rate at which the test attempts to activate MN/MS sessions. In tests where the MN/MS establishes a control session with the MN/MS servicing or authorization node, such as an FA, HA, AAA server, SGSN, etc., this rate is the number of MNs/MS that will attempt to establish control sessions every second. When the control plane is not used, this rate is the number of MNs/MS that will begin generating traffic every second. Default: 1.0 Range: 0.0010-3000 -deactivation_rate The rate at which the test attempts to deactivate MN/MS sessions. When the control plane is used, this rate is the number of MNs/MS that will attempt to disconnect their control sessions every second. When the control plane is not used, this rate is the number of MNs/MS that will stop sending data or release their data connections every second. Default: 1.0 Range: 0.0010-3000 -session_interval_shape Interval distribution type of Activation Rate and Deactivation Rate. Possible values: Normal, Fixed, Uniform, Poisson Default: Fixed -session_interval_deviation It stands the standard deviation of the Normal distribution, or the maximum deviation from mean of the Poisson and Uniform distribution. Default: 10 Dependency: session_interval_shape Poisson|Normal|Uniform -const_session_loading_en Whether to ensure the constant session loading, when it is true, it means the system will validate that the value you entered for the -session_hold_time and - session_pending_time will result in a constant load on the SUT, you should make sure that (-session_hold_time) + (- session_pending_time) = Activation Time. Default: false Dependency: test_activity Session_Loading_Test -session_hold_time The number of seconds a session is maintained in an established state before being disconnected Default: 1000 Range: 1-100000 Dependency: test_activity Session_Loading_Test -session_pending_time The number of seconds a session is left idle before it is re-connected. Default: 1000 Range: 1-100000 Dependency: test_activity Session_Loading_Test -mobility_delay_time The number of seconds to wait, after mobility events have been started, before initiating the first handoff. If handoffs begin When All Sessions Started, the delay timer starts when the final session is started; otherwise, the delay is applied to each session as it is started. Default: 10 Dependency: test_activity Inter-PDSN -session_start_re

IP APP Node

104

When you check the Session Start Retries box, the test will continue to attempt to re-connect any sessions that failed. The test first attempts to start all of the sessions defined for the test and then retries failed sessions. A session failure includes any failure to reach the established state and any failure after the session is established. Error counters are incremented for each session failure. Possible values: true, false Default: true Dependency: test_activity Inter-PDSN -start_type Specifies when handoffs should begin Default: When_All_Sessions_Started Possible values: When_All_Sessions_Started|When_Session_Started Dependency: test_activity Inter-PDSN -mobility_mode specify the number of handoffs that will be performed for each session. Possible values: Single_Handoff or Continuous_Handoff Default: Single_Handoff Dependency: test_activity Inter-PDSN -mobility_rate The rate, in sessions per second, that the sessions will be handed off. Default: 2.0 Range: 0.001-1000.0 Dependency: start_type When_All_Sessions_Started -mobility_rate_interval_shap The mobility interval distribution type. Possible values: Normal, Fixed, Uniform, Posson Default: Fixed Dependency: start_type When_All_Sessions_Started -mobility_interval_deviation It stands the standard deviation of the Normal distribution, or the maximum deviation from mean of the Poisson and Uniform distribution. Default: 10 Dependency: mobility_rate_interval_shap Poisson|Normal|Uniform -aaa_server_en Specifies whether to enable the AAA server on the IP APP Node. Possible values: true, false Default: false -data_ipsec_tunnel_en Specifies whether to enable the Data IPSec on the IP APP Node. Possible values: true, false Default: false -dhcp_en Specifies whether to enable the DHCP Cient on the IP APP Node. Possible values: true, false Default: false -external_data_en Specifies whether to enable the External Data on the IP APP Node. Possible values: 0, 1 Default: 0 -data_traffic_en Specifies whether to enable the Data Traffic on the IP APP Node. Possible values: Enabled, Disabled Default: Disabled

Return Values: The lsh::ip_app_node_config function returns a keyed list using the following keys (with the corresponding data):

tc_handle The test case handle, which will be used when you want to modify the test case, or configure more parameters on this test case.

IP APP Node

105

Will be returned only when the status is 1 and the -mode is create. status Success (1) or failure (0) of the operation. log Returned only when the status is 0

Examples: The following is the example to create and modify an IP Application Node test case. set ret [lsh::ip_app_node_config -mode create\ -test_hnd $test\ -phy_intf "eth1"\ -ts_name $ts_name\ -intf_ip_addr $ts_eht1\ -next_hop "1.0.0.1"\ -out_bound_traffic_port "eth2"\ -mac_addr $ts_eth1_mac\ -dhcp_en true\ -activation_rate 215.123]

Sample output for example shown above: {status 1} {tc_handle java0x8}

lsh::ip_app_node_config -mode modify\ -tc_hnd $tc\ -ts_name $ts_name_new

Sample output for example shown above: {status 1}

WIFI Offload Gateway Nodal

106


Functions:lsh::wifi_offload_gateway_nodal_config

lsh::wifi_offload_gateway_nodal_config

Name: lsh::wifi_offload_gateway_nodal_config

Purpose: Creates or modifies the Wifi Offload Gateway Nodal test case. This function only serves as the basic configurations required by the test case. To run the test case successfully, you must call some sub-functions that would make the configuration complete.

Synopsis: lsh::wifi_offload_gateway_nodal_config -mode {create|modify} -test_hnd <test session handle> -tc_hnd <test case handle> -test_activity {Mobility|Capacity_Test} -data_traffic_en {true|false} -inter_access_point_mobility_en {true|false} -inter_ssid_mobility_en {true|false} -start_retries_en {true|false} -mobility_rate_interval_dist {Fixed|Uniform|Normal|Poisson} -mobility_handoff_type {Single_Handoff|Continuous_Handoff} -mobility_rate <0.001-1000.0> -mobility_delay_time <1-100000> -mobility_start_type {When_All_Sessions_Started|When_Session_Started} -mobility_deviation_from_mean <0-99> -mobility_standard_deviation <0-100> -management_interface_en {true|false} -management_interface_graceful_shutdown_en {true|false} -wan_dhcp_client_en {true|false} -wan_graceful_shutdown_en {true|false} -tunnel_type {GRE} -gre_key_en {true|false} -gre_key <HEX> -gre_checksum_en {true|false} -gre_sequence_number_en {true|false} -send_iapp_mobility_msg_en {true|false} -wan_mtu <123-9300> -apply_tdf_access_point_options_en {true|false} -apply_tdf_access_point_options <ANY> -number_of_ssids <1-3000> -ssid_type {Open|Closed} -ssid_starting_dest_wifi_gw_addr <IP> -ssid_vlan_tag_en {true|false} -ssid_vlan_tag <1-65535> -ssid_name <ANY> -number_of_target_ssids <1-3000> -target_ssid_type {Open|Closed} -target_ssid_starting_dest_wifi_gw_addr <IP> -target_ssid_vlan_tag_en {true|false} -target_ssid_vlan_tag <1-65535> -target_ssid_name <ANY> -apply_tdf_ssids_en {true|false} -apply_tdf_ssids <ANY> -number_of_subscribers <1-150000> -activation_rate <0.0010-1000.0> -deactivation_rate <0.0010-1000.0> -mpls_en {true|false}


107

-mpls <0-4294967295> -mac_addr <MAC> -ue_dhcp_en {true|false} -ue_dhcp_via_gre_tunnel_en {true|false} -ue_graceful_shutdown_en {true|false} -ue_graceful_mobility_en {true|false} -ue_authentication_en {true|false} -ue_mobile_reauthentication_en {true|false} -outer_ip_type_of_service <0-255> -interval_distribution_type {Fixed|Uniform|Normal|Poisson} -max_deviation_from_mean <1-99> -standard_deviation <0-100> -apply_tdf_mobile_subscribers_en {true|false} -apply_tdf_mobile_subscribers <ANY> -use_ap_mac_ssid_called_station_id_en {true|false} -use_wan_mac_nas_id_en {true|false} -ap_wan_node_activation_rate <0.0010-1000.0> -ap_wan_node_deactivation_rate <0.0010-1000.0> -ap_wan_node_interface_type {eth|atm} -ap_wan_node_phy_intf <ANY> -ap_wan_node_intf_ip_addr <IP> -ap_wan_node_num_of_aps <1-150000> -ap_wan_node_mac_addr <MAC> -ap_wan_node_next_hop <IP> -ap_wan_node_out_bound_traffic_port <ANY> -ap_mgmt_wan_node_interface_type {eth|atm} -ap_mgmt_wan_node_phy_intf <ANY> -ap_mgmt_wan_node_intf_ip_addr <IP> -ap_mgmt_wan_node_mac_addr <MAC> -ap_mgmt_wan_node_next_hop <IP> -ap_mgmt_wan_node_out_bound_traffic_port <ANY> -target_ap_wan_node_interface_type {eth|atm} -target_ap_wan_node_phy_intf <ANY> -target_ap_wan_node_intf_ip_addr <IP> -target_ap_wan_node_num_of_aps <1-150000> -target_ap_wan_node_mac_addr <MAC> -target_ap_wan_node_next_hop <IP> -target_ap_wan_node_out_bound_traffic_port <ANY> -target_ap_mgmt_wan_node_interface_type {eth|atm} -target_ap_mgmt_wan_node_phy_intf <ANY> -target_ap_mgmt_wan_node_intf_ip_addr <IP> -target_ap_mgmt_wan_node_mac_addr <MAC> -target_ap_mgmt_wan_node_next_hop <IP> -target_ap_mgmt_wan_node_out_bound_traffic_port <ANY> -network_host_type {Local|Remote} -network_host_local_node_interface_type {eth|atm} -network_host_local_node_phy_intf <ANY> -network_host_local_node_intf_ip_addr <IP> -network_host_local_node_num_of_nodes <1-150000> -network_host_local_node_mac_addr <MAC> -network_host_local_node_next_hop <IP> -network_host_local_node_out_bound_traffic_port <ANY> -network_host_reset_idle_host_traffic_session_en {true|false} -network_host_idle_time_trigger_reset <0.0-4000.0> -apply_tdf_network_host_side_en {true|false} -apply_tdf_network_host_side <ANY> -client_traffic_type {Continuous|Verification} -client_perform_verification_en {true|false} -client_traffic_start {When_Session_Established| When_All_Sessions_Established} -client_data_start_delay <0-3600000> -client_auto_stop_contrl_layer_en {true|false} -client_limit_ingress_link_speed_en {true|false} -client_limit_ingress_link_speed <1-8000> -client_limit_egress_link_speed_en {true|false} -client_limit_egress_link_speed <1-8000> -client_max_tran_unit <123-9300> -client_unfragment_en {true|false} -client_resume_rate <1-10000> -error_inject_type {None|PacketDiscard|IPTotalLengthSetTo0| IPChecksumCorrupted|PayloadChecksumCorrupted|BadSourceIP}


108

-error_distribution {Fixed|Random} -outbound_en {true|false} -outbound_value <NUMERIC> -inbound_en {true|false} -inbound_value <NUMERIC> -bad_source_ip <IP> -apply_tdf_user_side_en {true|false} -apply_tdf_user_side <ANY> -dmf_list <ANY> -remote_ip_list <ANY> -dhcp_wan_client_id <ANY> -dhcp_wan_inc_lease_time_req_en {true|false} -dhcp_wan_lease_time <1-1814400> -dhcp_wan_enterprise_num <NUMERIC> -dhcp_wan_inc_rapid_commit_en {true|false} -dhcp_wan_rapid_commit_en {true|false} -dhcp_wan_broadcast_en {true|false} -dhcp_wan_inc_para_req_list_en {true|false} -dhcp_wan_req_para <ANY> -dhcp_wan_server_port <1-65535> -dhcp_wan_client_port <1-65535> -dhcp_wan_retries <0-65535> -dhcp_wan_offer_timer <0-65535> -dhcp_wan_ack_timer <0-65535> -dhcp_wan_user_class_list <ANY> -dhcp_mgmt_client_id <ANY> -dhcp_mgmt_inc_lease_time_req_en {true|false} -dhcp_mgmt_lease_time <1-1814400> -dhcp_mgmt_enterprise_num <NUMERIC> -dhcp_mgmt_inc_rapid_commit_en {true|false} -dhcp_mgmt_rapid_commit_en {true|false} -dhcp_mgmt_broadcast_en {true|false} -dhcp_mgmt_inc_para_req_list_en {true|false} -dhcp_mgmt_req_para <ANY> -dhcp_mgmt_server_port <1-65535> -dhcp_mgmt_client_port <1-65535> -dhcp_mgmt_reties <0-65535> -dhcp_mgmt_offer_timer <0-65535> -dhcp_mgmt_ack_timer <0-65535> -dhcp_mgmt_user_class_list <ANY> -dhcp_ue_client_id <ANY> -dhcp_ue_inc_lease_time_req_en {true|false} -dhcp_ue_lease_time <1-1814400> -dhcp_ue_enterprise_num <NUMERIC> -dhcp_ue_inc_rapid_commit_en {true|false} -dhcp_ue_rapid_commit_en {true|false} -dhcp_ue_broadcast_en {true|false} -dhcp_ue_inc_para_req_list_en {true|false} -dhcp_ue_req_para <ANY> -dhcp_ue_server_port <1-65535> -dhcp_ue_client_port <1-65535> -dhcp_ue_reties <0-65535> -dhcp_ue_offer_timer <0-65535> -dhcp_ue_ack_timer <0-65535> -dhcp_ue_user_class_list <ANY> Available Sub Function(s): lsh::aaa_radius_client_config: Used to configure the radius client on this test case.

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - create a new test case and the parameters in the test session specified by the -test_hnd modify - modify the parameters on the test case specified by the


109

-tc_hnd Possible values: create, modify -test_hnd Specify the test session handle, in which the test case will be added. This argument is mandatory when the -mode is set to create. -tc_hnd Specify the test case handle. This argument is mandatory when -mode is set to modify. It can modify the parameters configured on this test case. -test_activity Specifies the test activity. Possible values: Mobility, Capacity_Test The default value is Capacity_Test -data_traffic_en Specifies whether enable data traffic Possible values: true, false The default value is false -inter_access_point_mobility_en Specifies whether enable inter access point mobility Possible values: true, false The default value is true. This argument is available when -test_activity is set to Mobility -inter_ssid_mobility_en Specifies whether enable inter ssid mobility Possible values: true, false The default value is false This argument is available when -test_activity is set to Mobility. -start_retries_en Specifies whether enable start retry Possible values: true, false The default value is true -mobility_rate_interval_dist Specifies mobility rate interval distribution type Possible values: Fixed, Uniform, Normal, Poisson The default value is Fixed This argument is available when -mobility_start_type is set to When_All_Sessions_Started. -mobility_handoff_type Specifies mobility handoff type. Possible values are: Single_Handoff - Each session is handed off once and then maintained on the handoff node or SUT. Continuous_Handoff - Each session is continuously handed off with the handoffs spaced by the delay time The default value is Single_Handoff This argument is available when -test_activity is set to Mobility -mobility_rate Specifies the rate, in sessions per second, that the sessions will be handed off. Range: 0.001-1000.0 The default value is 1.0 This argument is available when -mobility_start_type is set to When_All_Sessions_Started


110

-mobility_delay_time Specifies mobility delay time The number of seconds to wait, after mobility events have been started, before initiating the first handoff. If handoffs begin When All Sessions Started, the delay timer starts when the final session is started; otherwise, the delay is applied to each session as it is started. Range: 1-100000 The default value is 10 This argument is available when -test_activity is set to Mobility -mobility_start_type Specifies the session start type Possible values: When_All_Sessions_Started - Handoffs begin after the final MN session is started and the delay time has expired. When Session Start Retries is enabled, handoffs will only begin if all sessions are successfully started. When_Session_Started - Each session is started and then handed off as the session's delay time expires. The default value is When_All_Sessions_Started This argument is available when -test_activity is set to Mobility -mobility_deviation_from_mean Specifies the mobility deviation from mean Range: 0-99 The default value is 10 This argument is available when -mobility_rate_interval_dist is set to Uniform|Poisson -mobility_standard_deviation Specifies mobility standard deviation in mobility setting Range: 0-100 The default value is 10 This argument is available when -mobility_rate_interval_dist is set to Normal -management_interface_en Specifies whether enable management interface Possible values: true, false The default value is false -management_interface_graceful_shutdown_en Specifies whether enable management interface graceful shutdown Possible values: true, false The default value is false This argument is available when -management_interface_en is set to true -wan_dhcp_client_en Specifies whether enable WAN dhcp client Possible values: true, false The default value is false -wan_graceful_shutdown_en Specifies whether enable WAN graceful shutdown Possible values: true, false The default value is false This argument is available when -wan_dhcp_client_en is set to true -tunnel_type Specifies the tunnel type Possible values: GRE, The default value is GRE -gre_key_en


111

Specifies whether enable GRE Key Possible values: true, false The default value is true -gre_key Indicates the options:GREKey for the GRE tunnel between the Access Point and the GW. Indicates the options for the GRE tunnel between the Access Point and the GW. The default value is 0x0 This argument is available when -gre_key_en is set to true -gre_checksum_en Indicates the options:GREChecksum for the GRE tunnel between the Access Point and the GW. Possible values: true, false The default value is true -gre_sequence_number_en Indicates the options:GRESequenceNumber for the GRE tunnel between the Access Point and the GW. Possible values: true, false The default value is false -send_iapp_mobility_msg_en The IAPP Mobility Message is a message that gets sent when we do mobility if enabled. The message is a L2 LLC message that gets sent by the Access Point through the GRE tunnel to notify the Gateway that mobility has occurred. Possible values: true, false The default value is false This argument is available when -test_activity is set to Mobility -wan_mtu WAN MTU is the MTU for the outer IP header Range: 123-9300 The default value is 1400 -apply_tdf_access_point_options_en Specifies whether enable apply test data file to access point options Possible values: true, false The default value is false -apply_tdf_access_point_options Specifies test data file to access point options This argument is available when -apply_tdf_access_point_options_en is set to true -number_of_ssids Each test case supports multiple SSID and the maximum number depends on your test case licensed capacity. The UEs get distributed to the SSIDs using a round robin mechanism. Range: 1-3000 The default value is 1 -ssid_type Specifies the SSID type. Possible values are described below: Open - Indicates that SSID does not require authentication of the UE. Authentication may still be performed when you select UE Authentication on the Mobile Subscriber pane. Closed - Indicates the SSID requires authentication of the UE, so authentication is performed regardless of whether you select UE Authentication on the Mobile Subscriber pane. The default value is Open -ssid_starting_dest_wifi_gw_addr Indicates the destination address the SSID uses for the GW.


112

The Wifi GW Address is automatically incremented for each SSID. -ssid_vlan_tag_en Specifies whether enable to input VLAN tag Possible values: true, false The default value is false -ssid_vlan_tag The VLAN tag specified in the SSID is added to the UE's Ethernet header, which is encapsulated in the GRE message. Range: 1-65535 The default value is 1 This argument is available when -ssid_vlan_tag_en is set to true -ssid_name A text string used as the SSID Name. This argument is available when use_ap_mac_ssid_called_station_id_en is set to true -number_of_target_ssids Each test case supports multiple SSID and the maximum number depends on your test case licensed capacity. The UEs get distributed to the SSIDs using a round robin mechanism. Range: 1-3000 The default value is 1 This argument is available when -inter_ssid_mobility_en is set to true -target_ssid_type Specifies the SSID type Open - Indicates that SSID does not require authentication of the UE. Authentication may still be performed when you select UE Authentication on the Mobile Subscriber pane. Closed - Indicates the SSID requires authentication of the UE, so authentication is performed regardless of whether you select UE Authentication on the Mobile Subscriber pane. The default value is Open. This argument is available when -inter_ssid_mobility_en is set to true -target_ssid_starting_dest_wifi_gw_addr Indicates the destination address the SSID uses for the GW. The Wifi GW Address is automatically incremented for each SSID. This argument is available and mandatory when -inter_ssid_mobility_en is set to true. -target_ssid_vlan_tag_en Specifies whether enable to input VLAN tag Possible values: true, false The default value is false This argument is available when -inter_ssid_mobility_en is set to true -target_ssid_vlan_tag The VLAN tag specified in the SSID is added to the UE's Ethernet header, which is encapsulated in the GRE message. Range: 1-65535 The default value is 1 This argument is available when -target_ssid_vlan_tag_en is set to true -target_ssid_name A text string used as the SSID Name This argument is available when -inter_ssid_mobility_en is set to true and use_ap_mac_ssid_called_station_id_en is set to true -apply_tdf_ssids_en


113

Specifies whether enable apply test data file to ssids Possible values: true, false The default value is false -apply_tdf_ssids Specifies test data file to ssids This argument is available when -apply_tdf_ssids_en is set to true -number_of_subscribers Specifies the number of unique mobile subscribers (MSs) emulated during the test. Range: 1-150000 The default value is 1 -activation_rate Specifies the rate at which the test attempts to activate MN/MS sessions. Range: 0.0010-1000.0 The default value is 1.0 -deactivation_rate Specifies the rate at which the test attempts to deactivate MN/MS sessions. Range: 0.0010-1000.0 The default value is 1.0 -mpls_en Specifies whether enable mpls Possible values: true, false The default value is false -mpls Select to include MPLS label in the GRE message. TheProtocol Type in the GRE header when you select MPLS is MPLS Label-Switched Packet. When you do not select MPLS, the Protocol Type in the GRE header is Ethernet Bridging. Range: 0-4294967295 The default value is 0 This argument is available when -mpls_en is set to true -mac_addr Indicates the MAC address of the UE. The UE's Ethernet packet gets passed as payload of the GRE message. This address is auto-incremented for UEs. This argument is mandatory for test_activity. -ue_dhcp_en Allows the UEs to get IP addresses via DHCP. Without this the UEs do not get their IPs and data doesn't transmit. Possible values: true, false The default value is true -ue_dhcp_via_gre_tunnel_en Specifies whether allows the DHCP messages sent from the UE to go through the WAN's DHCP tunnel. Possible values: true, false The default value is true This argument is available when -ue_dhcp_en is set to true -ue_graceful_shutdown_en Specifies to cause the UE to send a DHCP Release when the UE session is being brought down. Possible values: true, false The default value is false -ue_graceful_mobility_en Specifies whether available for Mobility testing. Select to send a DHCP Release when during mobility testing. Possible values: true, false The default value is false This argument is available when -inter_ssid_mobility_en


114

is set to true -ue_authentication_en Specifies to perform Radius Authentication on the UE Possible values: true, false The default value is false -ue_mobile_reauthentication_en Specifies to perform Radius Authentication during mobility testing Possible values: true, false The default value is false This argument is available when -test_activity is set to Mobility -outer_ip_type_of_service Specifies a value used in the outer IP header's "Type of Service". Range: 0-255 The default value is 0 -interval_distribution_type Specifies the interval distribution type Possible values: Fixed, Uniform, Normal, Poisson The default value is Fixed -max_deviation_from_mean limits the standard deviation from mean as a percent of mean in the Uniform and Poisson distribution models. Range: 1-99 The default value is 10 This argument is available when -interval_distribution_type is set to Poisson or Uniform. -standard_deviation defines the standard deviation as a percent of mean in the Normal distribution model. Range: 0-100 The default value is 10 This argument is available when -interval_distribution_type is set to Normal -apply_tdf_mobile_subscribers_en Specifies whether enable apply test data file to mobile subscribers Possible values: true, false The default value is false -apply_tdf_mobile_subscribers Specifies the test data file to mobile subscribers This argument is available when -apply_tdf_mobile_subscribers_en is set to true -use_ap_mac_ssid_called_station_id_en Specifies whether use [AP MAC:SSID] for called station id Possible values: true, false The default value is false This argument is available when -ue_authentication_en or ue_mobile_reauthentication_en is set to true -use_wan_mac_nas_id_en Specifies whether use WAN MAC address as NAS id Possible values: true, false The default value is false This argument is available when -ue_authentication_en or -ue_mobile_reauthentication_en is set to true -ap_wan_node_activation_rate Specifies the activation rate in AP-WAN node Range: 0.0010-1000.0 The default value is 1.0 -ap_wan_node_deactivation_rate Specifies the deactivation rate in AP-WAN node


115

Range: 0.0010-1000.0 The default value is 1.0 -ap_wan_node_interface_type Specifies the type of the physical interface Possible values: eth, atm The default value is eth -ap_wan_node_phy_intf Specifies which enabled Ethernet Interface will be used for WAN node. This argument is mandatory for -test_activity. -ap_wan_node_intf_ip_addr Specifies the IP address of WAN. When the physical interface type is "eth", it is the AAA Server node's actual IP address, it is one of the address pool associated with physical interface. When the physical interface type is "atm", it is the source address for all the traffic sent by the node. The address that you enter will be incremented for each node. This argument is mandatory for -test_activity. -ap_wan_node_num_of_aps Specifies the node number for WAN node Range: 1-150000 The default value is 1 -ap_wan_node_mac_addr Specifies the MAC address of WAN node -ap_wan_node_next_hop If don't want to use the default route, you can specify a physical device's IP address in the test network to use this IP address as the next hop. -ap_wan_node_out_bound_traffic_port Specifies the out bound traffic port -ap_mgmt_wan_node_interface_type Specifies the type of the physical interface Possible values: eth, atm The default value is eth This argument is available when -management_interface_en is set to true. -ap_mgmt_wan_node_phy_intf Specifies which enabled Ethernet Interface will be used for mgmt wan This argument is available when -management_interface_en is set to true -ap_mgmt_wan_node_intf_ip_addr Specifies the IP address of mgmt wan. When the physical interface type is "eth", it is the AAA Server node's actual IP address, it is one of the address pool associated with physical interface. When the physical interface type is "atm", it is the source address for all the traffic sent by the node. The address that you enter will be incremented for each node. This argument is available when -management_interface_en is set to true -ap_mgmt_wan_node_mac_addr Specifies the MAC address for mgmt wan This argument is available when -management_interface_en is set to true -ap_mgmt_wan_node_next_hop If don't want to use the default route, you can specify a physical device's IP address in the test network to use this IP address as the next hop This argument is available when -management_interface_en is set to true -ap_mgmt_wan_node_out_bound_traffic_port


116

Specifies the out bound traffic port This argument is available when -management_interface_en is set to true -target_ap_wan_node_interface_type Specifies the type of the physical interface Possible values: eth, atm The default value is eth This argument is available when -inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_wan_node_phy_intf Specifies which enabled Ethernet Interface will be used for target WAN This argument is available and mandatory when -inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_wan_node_intf_ip_addr Specifies the IP address of target WAN. When the physical interface type is "eth", it is the AAA Server node's actual IP address, it is one of the address pool associated with physical interface. When the physical interface type is "atm", it is the source address for all the traffic sent by the node. The address that you enter will be incremented for each node. This argument is available and mandatory when -inter_access_point_mobility_en is set to true and test_activity is set to Mobility. -target_ap_wan_node_num_of_aps Specifies the node number for target wan node Range: 1-150000 The default value is 1 This argument is available when -inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_wan_node_mac_addr Specifies the MAC address of target wan node This argument is available when -inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_wan_node_next_hop If don't want to use the default route, you can specify a physical device's IP address in the test network to use this IP address as the next hop This argument is available when -inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_wan_node_out_bound_traffic_port Specifies the out bound traffic port This argument is available when -inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_mgmt_wan_node_interface_type Specifies the type of the physical interface Possible values: eth, atm The default value is eth This argument is available when -management_interface_en is set to true and inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_mgmt_wan_node_phy_intf Specifies which enabled Ethernet Interface will be used for target mgmt wan node This argument is available when -management_interface_en is set to true and inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_mgmt_wan_node_intf_ip_addr Specifies the IP address of target mgmt wan node. When the physical interface type is "eth", it is the AAA Server node's actual IP address, it is one of the address pool associated with physical interface. When the physical interface type is "atm", it is the source address for all the traffic sent by the node. The address that you enter will be


117

incremented for each node. This argument is available when -management_interface_en is set to true and inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_mgmt_wan_node_mac_addr Specifies the MAC address of target mgmt wan node This argument is available when -management_interface_en is set to true and inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_mgmt_wan_node_next_hop If don't want to use the default route, you can specify a physical device's IP address in the test network to use this IP address as the next hop This argument is available when -management_interface_en is set to true and inter_access_point_mobility_en is set to true and test_activity is set to Mobility -target_ap_mgmt_wan_node_out_bound_traffic_port Specifies the out bound traffic port This argument is available when -management_interface_en is set to true and inter_access_point_mobility_en is set to true and test_activity is set to Mobility -network_host_type Specifies to select the location for the Network Host nodes.A Local Network Host is defined within a nodal test case, and executes on the same test server as the test case. A Remote Network Host runs in a Network Host test case. Possible values: Local, Remote The default value is Local. This argument is available when -data_traffic_en is set to true. -network_host_local_node_interface_type Specifies the type of the physical interface Possible values: eth, atm The default value is eth This argument is available when -data_traffic_en is set to true and network_host_type is set to Local. -network_host_local_node_phy_intf Specifies which enabled Ethernet Interface will be used for host This argument is available when -data_traffic_en is set to true and network_host_type is set to Local. -network_host_local_node_intf_ip_addr Specifies the IP address of host. When the physical interface type is "eth", it is the AAA Server node's actual IP address, it is one of the address pool associated with physical interface. When the physical interface type is "atm", it is the source address for all the traffic sent by the node. The address that you enter will be incremented for each node. This argument is available when -data_traffic_en is set to true and network_host_type is set to Local. -network_host_local_node_num_of_nodes Specifies the node number for host Range: 1-20 The default value is 1 This argument is available when -data_traffic_en is set to true and network_host_type is set to Local. -network_host_local_node_mac_addr Specifies the MAC address of host This argument is available when -data_traffic_en is set to true and network_host_type is set to Local. -network_host_local_node_next_hop If don't want to use the default route, you can specify a physical device's IP address in the test network to use this IP address as the


118

next hop This argument is available when -data_traffic_en is set to true and network_host_type is set to Local. -network_host_local_node_out_bound_traffic_port Specifies the out bound traffic port This argument is available when -data_traffic_en is set to true and network_host_type is set to Local. -network_host_reset_idle_host_traffic_session_en Specifies whether enable reset idle host traffic session Possible values: true, false The default value is false This argument is available when -data_traffic_en is set to true, -client_traffic_type is set to Continuous and -network_host_type is set to Local. -network_host_idle_time_trigger_reset When stateless (UDP or RAW) data types are used with a Network Host, the idle traffic timer enables the host to detect an MN session that is not responding or that has been disconnected. When the timer expires, the Network Host releases the data resources associated with the MN so that they will be available if the MN becomes active again. When an MN session is programmatically disconnected, during a Session Loading test, for example, this timer is handled automatically. You can use the checkbox to override an automated timer or to manually define a timer and then specify the maximum idle seconds in the Idle Time to Reset field. Range: 0.0-4000.0 The default value is 0.0 This argument is available when network_host_reset_idle_host_traffic_session_en is set to true -apply_tdf_network_host_side_en Specifies whether apply test data file to network host side Possible values: true, false The default value is false This argument is available when -data_traffic_en is set to true and network_host_type is set to Local. -apply_tdf_network_host_side Specifies test data file to network host side This argument is available when -apply_tdf_network_host_side_en is set to true -client_traffic_type Specifies the type of data test. Possible values are described below: Continuous- Generate a continual stream of data traffic, as defined by DMFs, through established MN sessions towards one or more Network Hosts. Default roles are assumed by both sides: MNs assume the client role and Network Hosts act as servers. Verification- Verify the data packet connectivity of an MN session with a single PING. The default value is Continuous. This argument is available when -data_traffic_en is set to true. -client_perform_verification_en Specifies whether to include a Verification test in a Continuous data test. The verification test is executed first, and if it is successful, the test proceeds to the continuous data test. Possible values: true, false The default value is false This argument is available when -data_traffic_en is set to true and client_traffic_type is set to Continuous. -client_traffic_start


119

Specifies the traffic start type Possible values are described below: When_All_Sessions_Established -Thetimer begins when the final MN session is established. When_Session_Established - Thetimer begins for each session as it is established. The default value is When_Session_Established This argument is available when -data_traffic_en is set to true and -client_traffic_type is set to Continuous. -client_data_start_delay Specifies the number of milliseconds to wait, after the Traffic Start trigger, before initiating data traffic by executing a Data Message Flow. Range: 0-3600000 The default value is 1000 This argument is available when -data_traffic_en is set to true. -client_auto_stop_contrl_layer_en Specifies to determine whether MN sessions are disconnected when the traffic layer is stopped. The traffic layer stops naturally at the end of the message flow transactions, but it can also be stopped due to packet loss, tunnel failure, or when Stop on Error is triggered. If the data protocol supports retry processing, the traffic layer can be stopped when the number of retries has been exhausted by selecting this option. Possible values: true, false The default value is false. This argument is available when -data_traffic_en is set to true and client_traffic_type is set to Continuous -client_limit_ingress_link_speed_en Specifies whether enable limit ingress link speed Possible values: true, false The default value is false This argument is available when -data_traffic_en is set to true and client_traffic_type is set to Continuous and network_host_type is set to Local -client_limit_ingress_link_speed Specifies Limit the MN receive (downlink) speed Range: 1-8000 The default value is 16 This argument is available when client_limit_ingress_link_speed_en is set to true and client_traffic_type is set to Continuous -client_limit_egress_link_speed_en Specifies whether enable limit egress link speed Possible values: true, false The default value is false This argument is available when -data_traffic_en is set to true and client_traffic_type is set to Continuous. -client_limit_egress_link_speed Specifies Limit the MN transmit (uplink) speed Range: 1-8000 The default value is 16 This argument is available when client_limit_egress_link_speed_en is set to true. -client_max_tran_unit Specifies the number of bytes at which fragmentation will take place at the bearer plane IP layer. Range: 123-9300 The default value is 1400 This argument is available when -data_traffic_en is set to true and client_traffic_type is set to Continuous


120

-client_unfragment_en Specifies to set the Don't Fragment bit in all bearer plane traffic sent by the node. Possible values: true, false The default value is false This argument is available when -data_traffic_en is set to true and client_traffic_type is set to Continuous -client_resume_rate start/resume data traffic at a specific rate and transactions Range: 1-10000 The default value is 3000 This argument is available when -data_traffic_en is set to true and client_traffic_type is set to Continuous -error_inject_type Specifies the type of errors that are introduced. Possible values: None, PacketDiscard, IPTotalLengthSetTo0 IPChecksumCorrupted, PayloadChecksumCorrupted, BadSourceIP, The default value is None This argument is available when -data_traffic_en is set to true and -client_traffic_type is set to Continuous -error_distribution Specifies the method by which packets are selected to be discarded or corrupted. Possible values: Fixed, Random Fixed - The error is applied at a fixed rate to every nth packet. Random - The error is randomly applied to 1 out of every n packets. The default value is Fixed This argument is available when -error_inject_type is set to set to one of the following: PacketDiscard|IPTotalLengthSetTo0|IPChecksumCorrupted |PayloadChecksumCorrupted -outbound_en Specifies whether use outbound function Possible values: true, false The default value is false. This argument is available when -error_inject_type is set to one of the following: PacketDiscard|IPTotalLengthSetTo0|IPChecksumCorrupted| PayloadChecksumCorrupted -outbound_value Errors are introduced in packets sent by the node. Range: 1-1000000 The default value is 0 This argument is available when -outbound_en is set to true -inbound_en Specifies whether use inbound function Possible values: true, false The default value is false This argument is available when -error_inject_type is set to PacketDiscard -inbound_value Errors are introduced in packets received by the node. Range: 1-1000000 The default value is 0 This argument is available when -inbound_en is set to true -bad_source_ip Specifies IP address in the field provided. That address will be used as the MN's IP address in outbound Data Traffic packets. This argument is available when -error_inject_type is set to BadSourceIP -apply_tdf_user_side_en


121

Specifies whether enable to apply test data file to network host side Possible values: true, false The default value is false. This argument is available when -data_traffic_en is set to true -apply_tdf_user_side Specifies test data file to network host side This argument is available when -apply_tdf_user_side_en is set to true -dmf_list Specifies the data message flows list used in traffic This argument is available when -data_traffic_en is set to true and client_traffic_type is set to Continuous For example: -dmf_list {"sms/brt_dmf_http 0"} "sms" is the library name "brt_dmf_http" is the dmf name "0" means the node index of this dmf is node 0. "/" is must to separate library name and dmf name -remote_ip_list Specifies the remote IP address. The default value is {"0.0.0.0"} This argument is available when data_traffic_en is set to true and network_host_type is set to Remote. -dhcp_wan_client_id Client-identifier option included in messages sent by the client. This value is used by the server to correlate a client request with an address binding. The default value is user# This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_inc_lease_time_req_en Specifies whether include the IP address lease time option in messages sent by the client. Possible values: true, false The default value is false This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_lease_time Defines the lease time included in the message sent by the client. When it is 0, the server will assign a default lease time. Range: 1-1814400 The default value is 1209600 This argument is available when -dhcp_wan_inc_lease_time_req_en is set to true -dhcp_wan_enterprise_num Defines the client's IANA Enterprise Number, which is included in the Identity Association (IA) ID of the IAs that the client associates with each of its interfaces The default value is 0 This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_inc_rapid_commit_en Specifies whether to include the rapid commit option in the solicit message sent to a server Possible values: true, false The default value is false This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_rapid_commit_en Specifies whether the Rapid Commit will be used.


122

Possible values: true, false The default value is false This argument is available when -dhcp_wan_inc_rapid_commit_en is set to true -dhcp_wan_broadcast_en Specifies whether to enable the broadcast. Possible values: true, false The default value is false This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_inc_para_req_list_en Specifies whether to include the parameter Request List in the message sent by the client. Possible values: true, false The default value is false This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_req_para The Parameter Request List include in the message sent by the client. This argument is available when -dhcp_wan_inc_para_req_list_en is set to true -dhcp_wan_server_port Specifies the UDP port that the server uses for DHCP traffic. Range: 1-65535 The default value is 67 This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_client_port Specifies the UDP port that the client uses for DHCP traffic. Range: 1-65535 The default value is 68 This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_retries The number of times a message is re-transmitted. Retries will be disabled when it is 0. Range: 0-65535 The default value is 3 This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_offer_timer Specifies the time waiting for a dhcp offer message. Range: 0-65535 The default value is 1 This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_ack_timer Specifies the time waiting for a dhcp ack message. Range: 0-65535 The default value is 1 This argument is available when -wan_dhcp_client_en is set to true -dhcp_wan_user_class_list Specifies the list of User Class option in messages sent by the client. The server may use the values in the list to determine the appropriate address pool for the client. The default value is "" This argument is available when -wan_dhcp_client_en is set to true -dhcp_mgmt_client_id Client-identifier option included in messages sent by the client. This


123

value is used by the server to correlate a client request with an address binding. The default value is user# This argument is available when -management_interface_en is set to true -dhcp_mgmt_inc_lease_time_req_en Specifies whether include the IP address lease time option in messages sent by the client. Possible values: true, false The default value is false This argument is available when -management_interface_en is set to true -dhcp_mgmt_lease_time Defines the lease time included in the message sent by the client. When it is 0, the server will assign a default lease time. Range: 1-1814400 The default value is 1209600 This argument is available when dhcp_mgmt_inc_lease_time_req_en is set to true. -dhcp_mgmt_enterprise_num Defines the client's IANA Enterprise Number, which is included in the Identity Association (IA) ID of the IAs that the client associates with each of its interfaces The default value is 0 This argument is available when -management_interface_en is set to true. -dhcp_mgmt_inc_rapid_commit_en Specifies whether to include the rapid commit option in the solicit message sent to a server Possible values: true, false The default value is false This argument is available when -management_interface_en is set to true. -dhcp_mgmt_rapid_commit_en Specifies whether the Rapid Commit will be used. Possible values: true, false The default value is false This argument is available when -dhcp_mgmt_inc_rapid_commit_en is set to true. -dhcp_mgmt_broadcast_en Specifies whether to enable the broadcast. Possible values: true, false The default value is false This argument is available when -management_interface_en is set to true. -dhcp_mgmt_inc_para_req_list_en Specifies whether to include the parameter Request List in the message sent by the client. Possible values: true, false The default value is false. This argument is available when -management_interface_en is set to true. -dhcp_mgmt_req_para The Parameter Request List include in the message sent by the client. This argument is available when -dhcp_mgmt_inc_para_req_list_en is set to true. -dhcp_mgmt_server_port Specifies the UDP port that the server uses for DHCP traffic. Range: 1-65535 The default value is 67 This argument is available when -management_interface_en is set to true.


124

-dhcp_mgmt_client_port Specifies the UDP port that the client uses for DHCP traffic. Range: 1-65535 The default value is 68 This argument is available when -management_interface_en is set to true. -dhcp_mgmt_reties The number of times a message is re-transmitted. Retries will be disabled when it is 0. Range: 0-65535 The default value is 3 This argument is available when -management_interface_en is set to true. -dhcp_mgmt_offer_timer Specifies the time waiting for a dhcp offer message. Range: 0-65535 The default value is 1 This argument is available when -management_interface_en is set to true. -dhcp_mgmt_ack_timer Specifies the time waiting for a dhcp ack message. Range: 0-65535 The default value is 1. This argument is available when -management_interface_en is set to true. -dhcp_mgmt_user_class_list Specifies the list of User Class option in messages sent by the client. The server may use the values in the list to determine the appropriate address pool for the client. The default value is "". This argument is available when -management_interface_en is set to true. -dhcp_ue_client_id Client-identifier option included in messages sent by the client. This value is used by the server to correlate a client request with an address binding. The default value is user# This argument is available when -ue_dhcp_en is set to true -dhcp_ue_inc_lease_time_req_en Specifies whether include the IP address lease time option in messages sent by the client. Possible values: true, false The default value is false This argument is available when -ue_dhcp_en is set to true -dhcp_ue_lease_time Defines the lease time included in the message sent by the client. When it is 0, the server will assign a default lease time. Range: 1-1814400 The default value is 1209600 This argument is available when -dhcp_ue_inc_lease_time_req_en is set to true. -dhcp_ue_enterprise_num Defines the client's IANA Enterprise Number, which is included in the Identity Association (IA) ID of the IAs that the client associates with each of its interfaces The default value is 0 This argument is available when -ue_dhcp_en is set to true -dhcp_ue_inc_rapid_commit_en Specifies whether to include the rapid commit option in the solicit message sent to a server Possible values: true, false


125

The default value is false This argument is available when -ue_dhcp_en is set to true -dhcp_ue_rapid_commit_en Specifies whether the Rapid Commit will be used. Possible values: true, false The default value is false This argument is available when -dhcp_ue_inc_rapid_commit_en is set to true -dhcp_ue_broadcast_en Specifies whether to enable the broadcast. Possible values: true, false The default value is false This argument is available when -ue_dhcp_en is set to true -dhcp_ue_inc_para_req_list_en Specifies whether to include the parameter Request List in the message sent by the client. Possible values: true, false The default value is false This argument is available when -ue_dhcp_en is set to true -dhcp_ue_req_para The Parameter Request List include in the message sent by the client. This argument is available when -dhcp_ue_inc_para_req_list_en is set to true -dhcp_ue_server_port Specifies the UDP port that the server uses for DHCP traffic. Range: 1-65535 The default value is 67 This argument is available when -ue_dhcp_en is set to true -dhcp_ue_client_port Specifies the UDP port that the client uses for DHCP traffic. Range: 1-65535 The default value is 68 This argument is available when -ue_dhcp_en is set to true -dhcp_ue_reties The number of times a message is re-transmitted. Retries will be disabled when it is 0. Range: 0-65535 The default value is 3 This argument is available when -ue_dhcp_en is set to true -dhcp_ue_offer_timer Specifies the time waiting for a dhcp offer message. Range: 0-65535 The default value is 1 This argument is available when -ue_dhcp_en is set to true -dhcp_ue_ack_timer Specifies the time waiting for a dhcp ack message. Range: 0-65535 The default value is 1 This argument is available when -ue_dhcp_en is set to true -dhcp_ue_user_class_list Specifies the list of User Class option in messages sent by the client. The server may use the values in the list to determine the appropriate address pool for the client. The default value is "". This argument is available when -ue_dhcp_en is set to true

Return Values tc_handle The test case handle, which will be used when you want to modify the test case, or configure more parameters on this test case. Will be returned only when the status is 1 and the -mode is create.


126

status Success (1) or failure (0) of the operation log Returned only when the status is 0

Examples: set ret [lsh::wifi_offload_gateway_nodal_config -mode create\ -test_hnd $test\ -ap_wan_node_phy_intf eth1\ -ssid_starting_dest_wifi_gw_addr "1.1.1.1"\ -ts_name $ts_name\ -mac_addr "11:22:33:44:55:66"\ -ap_wan_node_intf_ip_addr "10.71.50.106"\ -ue_authentication_en true\ -data_traffic_en true\ -dmf_list {"sms/brt_dmf_http 0" "nana/dmf_create_from_script_sub1 0"}\ -network_host_local_node_phy_intf eth3\ -network_host_local_node_intf_ip_addr "10.71.50.108"\ -error_inject_type BadSourceIP\ -bad_source_ip 1.1.1.1\ -test_activity Mobility\ -mobility_rate_interval_dist Poisson\ -target_ap_wan_node_phy_intf eth2\ -target_ap_wan_node_intf_ip_addr "10.71.50.107"\ -interval_distribution_type Normal\ -standard_deviation 44\ -activation_rate 200.50\ -wan_dhcp_client_en true\ -gre_key_en true\ -gre_key 0x12345\ -dhcp_wan_user_class_list {"spirent_dhcp" "spirent_bangalore"}\ -dhcp_ue_user_class_list {"spirent_dhcp" "spirent_bangalore"}\ ]

keylget ret status sta if {$sta == $FAIL} { puts "failed to create wifi_offload_gateway_nodal test session. $ret" exit; } else { puts "successfully create wifi_offload_gateway_nodal test session" keylget ret tc_handle tc }

Sub Functions

127

Sub Functions

Functions:lsh::aaa_radius_client_configlsh::dhcp_client_configlsh::gtp_configlsh::gtp'_configlsh::ip_pools_configlsh::l2tp_configlsh::ppp_configlsh::qos_update_config

lsh::aaa_radius_client_config

Name: lsh::aaa_radius_client_config

Purpose: Used to configure the radius protocol on the client. It can be configured on following test cases: IP APP NODE WIFI Offload Gateway Nodal

Synopsis: lsh::aaa_radius_client_config -mode {create|modify} -tc_hnd <test case handle> -aaa_protocol {Radius|Diameter} -alter_node_auth_en {true|false} -use_ms_framed_ip {true|false} -aaa_sut_distribution_mode {Dedicated|Round_Robin} -primary_acct_sut <ANY> -primary_auth_sut <ANY> -secondary_acct_en {true|false} -secondary_acct_sut <ANY> -secondary_auth_en {true|false} -secondary_auth_sut <ANY> -sut_name_list <ANY> -nas_intf_type {eth|atm} -nas_phy_intf <ANY> -nas_intf_ip_addr <IP> -nas_node_num <NUMERIC> -nas_mac_addr <MAC> -nas_next_hop <IP> -nas_out_bound_traffic_port <ANY> -nas_vpi <0-15> -nas_vci <0-4000> -nas_node_addr_err_inj <0-5> -nas_node_addr_ip_encap {0|1} -alter_nas_intf_type {eth|atm} -alter_nas_phy_intf <ANY> -alter_nas_intf_ip_addr <IP> -alter_nas_node_num <NUMERIC> -alter_nas_mac_addr <MAC> -alter_nas_next_hop <IP> -alter_nas_out_bound_traffic_port <ANY> -alter_nas_vpi <0-15> -alter_nas_vci <0-4000> -alter_nas_node_addr_err_inj <0-5> -alter_nas_node_addr_ip_encap {0|1} -target_nas_intf_type {eth|atm} -target_nas_phy_intf <ANY>

Sub Functions

128

-target_nas_intf_ip_addr <IP> -target_nas_node_num <NUMERIC> -target_nas_mac_addr <MAC> -target_nas_next_hop <IP> -target_nas_out_bound_traffic_port <ANY> -target_nas_vpi <0-15> -target_nas_vci <0-4000> -target_nas_node_addr_err_inj <0-5> -target_nas_node_addr_ip_encap {0|1} -aaa_test_type {Authentication_With_Accounting|Accounting_Only|Authentication_Only} -nas_identifier <ANY> -rad_user_name <ANY> -retry_time <1-65535> -retry_count <1-65535> -password_en {true|false} -rad_password <ANY> -nas_acct_id <ANY> -rad_tdf_to_nas_en {true|false} -rad_tdf_to_nas <ANY> -vsa <ANY> -vsa_database_size <200-4000> -class_attr_size <20-4000> -auth_type {CHAP|PAP|EAP|DIGEST} -re_auth_en {true|false} -re_auth_interval <5-65535> -auth_sut_port <0-65535> -auth_secret <ANY> -auth_ip_addr_from_aaa_server_en {true|false} -auth_chap_attr_inc {true|false} -auth_nas_identifier_inc {true|false} -auth_nas_ip_addr_inc {true|false} -auth_accounting_id_inc {true|false} -auth_nas_unique_en {0|1} -auth_send_proxy_en {true|false} -alter_nas_identifier <ANY> -alter_nas_access_delay_time <1-100000> -auth_chap_challenge_len <1-128> -auth_eap_user_name <ANY> -auth_eap_expanded {0|1} -auth_eap_retries <0-65535> -auth_eap_retry_time <0-65535> -auth_eap_tdf_to_auth_para_en {true|false} -auth_eap_tdf_to_auth_para <ANY> -auth_eap_sim_en {true|false} -auth_eap_sim_secret_key <HEX> -auth_eap_sim_encry_alg {3gpp|3gpp2} -auth_eap_sim_operator_var <HEX> -auth_eap_sim_family_key <HEX> -auth_eap_sim_use_hard_code_val {true|false} -auth_eap_sim_sres <HEX> -auth_eap_sim_kc <HEX> -auth_eap_sim_init_fast_reauth_id_en {true|false} -auth_eap_sim_init_fast_reauth_id <ANY> -auth_eap_sim_init_pseudonym_id_en {true|false} -auth_eap_sim_init_pseudonym_id <ANY> -auth_eap_sim_permanet_id_en {true|false} -auth_eap_sim_permanet_id <ANY> -auth_eap_sim_tdf_to_sim_para_en {true|false} -auth_eap_sim_tdf_to_sim_para <ANY> -auth_eap_md5_en {true|false} -auth_eap_gtc_en {true|false} -auth_eap_aka_en {true|false} -auth_eap_mschapv2_en {true|false} -auth_eap_tls_en {true|false} -auth_digest_rfc_version {draft|final} -auth_digest_realm <ANY> -auth_digest_method <ANY> -auth_digest_uri <ANY> -auth_digest_algorithm {md5|md5_sess} -auth_digest_qop {auth|auth_int} -acct_send_start_msg_en {true|false}

Sub Functions

129

-acct_started_time <0-1000000> -acct_send_stop_msg_en {true|false} -acct_stopped_time <1-1000000> -acct_interim_update_msg_en {true|false} -acct_interim_update_time <0-1000000> -acct_start_delay_msg_en {true|false} -acct_start_delay_time <0-1000000> -acct_sut_port <0-65535> -acct_secret <ANY> -acct_user_name_inc {true|false} -acct_nas_identifier_inc {true|false} -acct_nas_ip_addr_inc {true|false} -acct_ignore_rsp_en {true|false} -acct_on_off_en {true|false} -rad_tdf_to_para_en {true|false} -rad_to_para_tdf <ANY> -coa_simulation_en {true|false} -coa_ret {coa_ack|coa_nak|none} -das_key_type {user_name|user_ip_address|acct_session_id} -disconect_en {true|false} -coa_auth_secret <ANY> -nas_iteration_limit_en {true|false} -nas_start_port <2000-65535> -nas_end_port <2000-65535> -nas_start_session_id <0-255> -nas_end_session_id <0-255> -nas_session_id_per_group <1-255>

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - create the parameters in the test session specified by the -tc_hnd modify - modify the parameters on the test case specified by the -tc_hnd. -tc_hnd Specifies the test case handle. This argument is mandatory. It can be used to create and modify the parameters configured on this test case. -aaa_protocol The type of AAA protocol. Possible values: Radius, Diameter Default: Radius -alter_node_auth_en Whether to enable the alternate node authentication. Possible values: true, fasle Default: false -use_ms_framed_ip Default: false -aaa_sut_distribution_mode Specifies the AAA SUT distribution mode. Possible values: Dedicated|Round_Robin Default: Dedicated -primary_acct_sut The name of the primary accounting SUT. It can be specified only when the - aaa_sut_distribution_mode is Dedicated and the aaa_test_type is Authentication_With_Accounting or Accounting_Only. Dependency: aaa_sut_distribution_mode Dedicated&aaa_test_type Authentication_With_Accounting|Accounting_Only -primary_auth_sut The name of the primary authentication SUT. It can be only specified when -aaa_sut_distribution_mode is Dedicated and the aaa_test_type is

Sub Functions

130

Authentication_With_Accounting or Authentication_Only.

-secondary_acct_en Specifies whether to use the secondary accounting SUT. It can be only specified when -aaa_sut_distribution_mode is Dedicated and the aaa_test_type is Authentication_With_Accounting or Authentication_Only. Possible values: true, false Default: false Dependency: aaa_sut_distribution_mode Dedicated&aaa_test_type Authentication_With_Accounting|Accounting_Only

-secondary_acct_sut The name of the primary accounting SUT. Dependency: secondary_acct_en true

-secondary_auth_en Specifies whether to use the secondary authentication SUT. It can be specified only when the - aaa_sut_distribution_mode is Dedicated and the aaa_test_type is Authentication_With_Accounting or Authentication _Only. Default: false Dependency: aaa_sut_distribution_mode Dedicated&aaa_test_type Authentication_With_Accounting|Authentication_Only

-secondary_auth_sut The name of the secondary authentication SUT. Dependency: secondary_auth_en true

-sut_name_list Specifies a list of SUT name. Dependency: aaa_sut_distribution_mode Round_Robin

-nas_intf_type The interface type of the NAS node. Possible values: atm, eth Default: eth

-nas_phy_intf The interface of the NAS node.

-nas_intf_ip_addr The IP address of the NAS node.

-nas_node_num The number of the NAS node. Default: 1

-nas_mac_addr The MAC address of the NAS node

-nas_next_hop The next hop address of the NAS node.

-nas_out_bound_traffic_port The outbound traffic port of the NAS node.

-nas_vpi The VPI of the NAS node. it can be used when the nas_intf_type is atm Range: 0-15 Dependency: nas_intf_type atm

-nas_vci The VCI of the NAS node. it can be used when the nas_intf_type is atm Default: 0 Range: 0-4000 Dependency: nas_intf_type atm

-nas_node_addr_err_inj Specifies the error inject of the NAS node. Default: 0 Range: 0-5 Dependency: nas_intf_type eth

Sub Functions

131

-nas_node_addr_ip_encap The IP encapsulation of the NAS node. It can be used when the interface type is atm. Default: 0 Dependency: nas_intf_type atm

-alter_nas_intf_type The interface type of the Alternate NAS node. Possible values: atm, eth Default: eth Dependency: alter_node_auth_en true

-alter_nas_phy_intf The interface of the Alternate NAS node. Dependency: alter_node_auth_en true

-alter_nas_intf_ip_addr The IP address of Alternate NAS node. Dependency: alter_node_auth_en true

-alter_nas_node_num The number of the Alternate NAS node. Default: 1 Dependency: alter_node_auth_en true

-alter_nas_mac_addr The MAC address of the Alternate NAS node. Dependency: alter_node_auth_en true

-alter_nas_next_hop The next hop IP address of the Alternate NAS node. Dependency: alter_node_auth_en true

-alter_nas_out_bound_traffic_port The outbound traffic port of Alternate NAS node. Dependency: alter_node_auth_en true

-alter_nas_vpi The VPI of Alternate NAS node. Range: 0-15 Dependency: alter_nas_intf_type atm

-alter_nas_vci The VPI of Alternate NAS node. Default: 0 Range: 0-4000 Dependency: alter_nas_intf_type atm

-alter_nas_node_addr_err_inj Specifies the error inject of the Alternate NAS node. Default: 0 Range: 0-5 Dependency: alter_nas_intf_type eth

-alter_nas_node_addr_ip_encap The IP encapsulation of the NAS node. It can be used when the interface type is atm. Default: 0 Dependency: alter_nas_intf_type atm

-target_nas_intf_type The interface type of the Target NAS node. Default: eth Dependency: lsname_TestActivity Inter-PDSN

-target_nas_phy_intf The interface of the Target NAS node. Dependency: lsname_TestActivity Inter-PDSN

-target_nas_intf_ip_addr

Sub Functions

132

The IP address of the Target NAS node. Dependency: lsname_TestActivity Inter-PDSN

-target_nas_node_num The number of the Target NAS node. Default: 1 Dependency: lsname_TestActivity Inter-PDSN

-target_nas_mac_addr The MAC address of the Target NAS node. Dependency: lsname_TestActivity Inter-PDSN

-target_nas_next_hop The next hop IP address of the Target NAS node. Dependency: lsname_TestActivity Inter-PDSN

-target_nas_out_bound_traffic_port The outbound traffic port of the Target NAS node. Dependency: lsname_TestActivity Inter-PDSN

-target_nas_vpi The VCI of the Target NAS node. Range: 0-15 Dependency: target_nas_intf_type atm

-target_nas_vci The VPI of the Target NAS node. Default: 0 Range: 0-4000 Dependency: target_nas_intf_type atm

-target_nas_node_addr_err_inj Specifies the error inject of the Target NAS node. Default: 0 Range: 0-5 Dependency: target_nas_intf_type eth

-target_nas_node_addr_ip_encap The IP encapsulation of the Target NAS node. It can be used when the interface type is atm. Default: 0 Dependency: target_nas_intf_type atm

-aaa_test_type Specifies the types of transactions that are included in the test: authentication, accounting, or both. The types of transactions affect the way RADIUS sessions are connected and disconnected. Possible values: Authentication_With_Accounting, Accounting_Only, Authentication_Only Default: Authentication_With_Accounting

-nas_identifier The NAS-Identifier attribute in RADIUS requests sent to the SUT, formatted as the Fully Qualified Domain Name (FQDN) of the NAS. The name must be unique within the scope of the SUT. Either the NAS-IP-Address or the NAS-Identifier attribute is required by RADIUS. Default: @nasdomain

-rad_user_name The user name of the radius session. Default: @domain

-retry_time The amount of time, in milliseconds, that the test will wait for a response if a response is expected. When the time expires and the Retry Count has not been exceeded, the message is re-transmitted. Default: 1000 Range: 1-65535

-retry_count The maximum number of times a message will be sent. if it is 1, it means

Sub Functions

133

that the retries is disabled. Default: 5 Range: 1-65535

-password_en Specifies whether to use the password for the user names. Possible values: true, false Default: false

-rad_password Defines the password that is used for all user names. Default: secret Dependency: password_en true

-nas_acct_id The Acct-Session-Id attribute in the RADIUS Accounting Request messages sent to the SUT. This value is used to associate the Start, Interim Update, and Stop messages for an MN's accounting session Default: ACCT0000 Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

-rad_tdf_to_nas_en Whether to apply the parameters defined in the TDF to the test. Possible values: true, false Default: false

-rad_tdf_to_nas The file name of TDF that will be applied to the test. Dependency: rad_tdf_to_nas_en true

-vsa It is not supported currently

-vsa_database_size Indicates the VSA size allocated for authentication packet flow descriptors and allows you to define the database memory to run VSA packets. Default: 200 Range: 200-4000

-class_attr_size Indicates the Class Attribute Size allocated for authentication/accounting Class Attributes. Default: 420 Range: 20-4000

-auth_type The authentication type. Possible values: CHAP, PAP, EAP, DIGEST Default: CHAP Dependency: aaa_test_type Authentication_With_Accounting|Authentication_Only

-re_auth_en Specifies whether to enable the re-authentication Possible values: true, false Default: false Dependency: aaa_test_type Authentication_With_Accounting|Authentication_Only

-re_auth_interval When enable the re-authentication, specify the interval of the re-authentication. Default: 20 Range: 5-65535 Dependency: re_auth_en true

-auth_sut_port The UDP port that is used for RADIUS authentication on all SUTs Default: 1812 Range: 0-65535

Sub Functions

134

Dependency: aaa_test_type Authentication_With_Accounting|Authentication_Only

-auth_secret The shared secret between a RADIUS NAS and AAA server that is included, along with other values, in the encrypted Authenticator field in the Access Request messages sent to the SUT. Default: secret Dependency: aaa_test_type Authentication_With_Accounting|Authentication_Only

-auth_ip_addr_from_aaa_server_en Specifies whether the AAA SUT will allocate and return an IP address for an MN in the authentication response message. When address allocation is used, the address received is automatically included in the Framed-IP-Address attribute in any accounting requests sent to the SUT. Possible values: true, false Default: false Dependency: aaa_test_type Authentication_With_Accounting|Authentication_Only

-auth_chap_attr_inc Specifies whether the CHAP Challenge value will always be included in the CHAP-Challenge attribute regardless of the challenge length. Possible values: true, false Default: false Dependency: auth_type CHAP

-auth_nas_identifier_inc Specifies whether the NAS-Identifier attribute is included and is provisioned with NAS Identifier. Possible values: true, false Default: false Dependency: aaa_test_type Authentication_With_Accounting|Authentication_Only

-auth_nas_ip_addr_inc Specifies whether the NAS-IP-Address attribute is included and is provisioned with the address of the NAS Node associated with the MN. Possible values: true, false Default: false Dependency: aaa_test_type Authentication_With_Accounting|Authentication_Only

-auth_accounting_id_inc Specifies whether the Acct-Session-Id attribute is included and is provisioned with Accounting ID. Possible values: true, false Default: false Dependency: aaa_test_type Authentication_With_Accounting

-auth_nas_unique_en Specifies whether to enable using a unique authenticator. Possible values 0, 1 Default: 0 Dependency: aaa_test_type Authentication_With_Accounting|Authentication_Only

-auth_send_proxy_en Specifies whether to enable Proxy-State attribute handling if there is a proxy AAA Server between the NAS and the authenticating server. Possible values: true, false Default: false Dependency: aaa_test_type Authentication_With_Accounting|Authentication_Only

-alter_nas_identifier A unique identifier for alternate NAS node Default: @nasdomain2 Dependency: alter_node_auth_en true

Sub Functions

135

-alter_nas_access_delay_time The number of seconds to wait before sending an Access Request message from the Alternate Node. This timer starts when the primary NAS Node sends an Access Request on behalf of the MN. Default: 1000 Range: 1-100000 Dependency: alter_node_auth_en true

-auth_chap_challenge_len Specifies the Challenge Length when the authentication type is CHAP. Default: 16 Range: 1-128 Dependency: auth_type CHAP

-auth_eap_user_name The MN's user name, NAI, or IMSI that will be sent or expected in the EAP Identity response Default: @domain Dependency: auth_type EAP

-auth_eap_expanded Specifies whether to enable support for vendor-specific authentication methods. If the AAA Server requests a method that the MN does not support, the MN responds with an Expanded NAK message. Default: 0 Dependency: auth_type EAP

-auth_eap_retries The number of times a message will be transmitted when the expected response has not been received. if it is 0, the retries will be disabled. Default: 0 Range: 0-65535 Dependency: auth_type EAP

-auth_eap_retry_time The interval between each retries. Default: 5 Range: 0-65535 Dependency: auth_type EAP

-auth_eap_tdf_to_auth_para_en You can provision authentication credentials for each MN by using Test Data Files. Specify whether to use the TDF. Possible values: true, false Default: false Dependency: auth_type EAP

-auth_eap_tdf_to_auth_para The file name of the TDF. Dependency: auth_eap_tdf_to_auth_para_en true

-auth_eap_sim_en Specifies whether to enable support for EAP-SIM authentication in a GSM network. Possible values: true, false. Default: false Dependency: auth_type EAP

-auth_eap_sim_secret_key The shared key that is known to both the MN and the AAA Server which is used for the EAP-SIM authentication. Default: 0x0123456789ABCDEF0123456789ABCDEF Dependency: auth_eap_sim_en true

-auth_eap_sim_encry_alg The method of cryptographic encryption of the data to be transmitted between the MN and the AAA Server which is used for the EAP-SIM authentication. Default: 3gpp Dependency: auth_eap_sim_en true

Sub Functions

136

-auth_eap_sim_operator_var The 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network which is used for the EAP-SIM authentication. Default: 0x63BFA50EE6523365FF14C1F45F88737D Dependency: auth_eap_sim_encry_alg 3gpp

-auth_eap_sim_family_key The 32-bit identifier used by the 3GPP2 Enhanced Cryptographic Algorithm in EAP-SIM. Default: 0x41484147 Dependency: auth_eap_sim_encry_alg 3gpp2

-auth_eap_sim_use_hard_code_val Specifies whether to enable the Use hard-coded values in EAP-SIM. Possible values: true, false Default: false Dependency: auth_eap_sim_en true

-auth_eap_sim_sres The SRES value that will be used to formulate the challenge response for all MNs in EAP-SIM. Default: 0x000000000000 Dependency: auth_eap_sim_use_hard_code_val true

-auth_eap_sim_kc The key that will be used to derive new keying material for all MNs in EAP-SIM. Default: 0x00000000000000000000000000000000 Dependency: auth_eap_sim_use_hard_code_val true

-auth_eap_sim_init_fast_reauth_id_en Specifies whether to use the fast re-authentication on this EAP authentication. Possible values: true, false Default: false Dependency: auth_eap_sim_en true

-auth_eap_sim_init_fast_reauth_id The initial fast re-authentication ID on EAP-SIM Dependency: auth_eap_sim_init_fast_reauth_id_en true

-auth_eap_sim_init_pseudonym_id_en Specifies if the initial pseudonym id is used on EAP-SIM. Possible values: true, false Default: false Dependency: auth_eap_sim_en true

-auth_eap_sim_init_pseudonym_id A pseudonym identity of the peer. Dependency: auth_eap_sim_init_pseudonym_id_en true

-auth_eap_sim_permanet_id_en Specifies whether to use the permanent identity on the EAP-SIM. Possible values: true, false Default: false Dependency: auth_eap_sim_en true

-auth_eap_sim_permanet_id Indicates the permanent identity, used on full authentication only. Dependency: auth_eap_sim_permanet_id_en true

-auth_eap_sim_tdf_to_sim_para_en Specifies whether to apply the EAP-SIM parameters from the Test Data File. Possible values: true, false. Default: false Dependency: auth_eap_sim_en true

-auth_eap_sim_tdf_to_sim_para The TDF file name in which the EAP-SIM parameters defined will be applied. Dependency: auth_eap_sim_tdf_to_sim_para_en true

Sub Functions

137

-auth_eap_md5_en Specifies whether to enable support for MD5 authentication, and then define the MN's Password Default: false Dependency: auth_type EAP

-auth_eap_gtc_en Specifies whether to enable support for GTC authentication, and then define the MN's Token/Password. Default: false Dependency: auth_type EAP

-auth_eap_aka_en Determines whether to enable support for EAP-AKA authentication in a CDMA2000 or UMTS network, and then define the Secret Key, Encryption Algorithm and the Operator Variant or Family Key. Default: false Dependency: auth_type EAP

-auth_eap_mschapv2_en Determines whether to enable support for EAP-MSCHAPv2 authentication for AAA RADIUS client and server testing, and define the MN's Password. Default: false Dependency: auth_type EAP

-auth_eap_tls_en Specifies whether to enable support for TLS authentication. Default: false Dependency: auth_type EAP

-auth_digest_rfc_version Specifies the version of DIGEST. Possible values: draft, final Default: final Dependency: auth_type DIGEST

-auth_digest_realm The realm-value will be included in digest response Default: nas.com Dependency: auth_digest_rfc_version draft

-auth_digest_method The method for the request-URI will be included in digest response, only when the version is draft it can be set. Default: INVITE Dependency: auth_digest_rfc_version draft

-auth_digest_uri The digest-uri-value will be included in digest response, only when the version is draft it can be set. Default: sip:[email protected] Dependency: auth_digest_rfc_version draft

-auth_digest_algorithm The algorithm will be included in digest response, only when the version is draft it can be set. Default: md5 Dependency: auth_digest_rfc_version draft

-auth_digest_qop The qop-value will be included in digest response, only when the version is draft it can be set. Default: auth Dependency: auth_digest_rfc_version draft

-acct_send_start_msg_en Specifies whether to send the accounting request start message Possible values: true, false Default: false Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

Sub Functions

138

-acct_started_time The number of seconds to maintain the accounting session before sending a Stop message Default: 30 Range: 0-1000000 Dependency: acct_send_start_msg_en true

-acct_send_stop_msg_en Specifies whether to send the accounting request stop message Default: false Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

-acct_stopped_time The number of seconds to wait after stopping the MN's accounting session before starting a new accounting session. Default: 30 Range: 1-1000000 Dependency: acct_send_stop_msg_en true

-acct_interim_update_msg_en Specifies whether to send the accounting request interim update message Possible values: true, false. Default: false Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

-acct_interim_update_time The number of seconds between transmissions of Accounting Request - Interim Update messages, and before the first message is sent after the accounting session is started. Default: 10 Range: 0-1000000 Dependency: acct_interim_update_msg_en true

-acct_start_delay_msg_en Specifies whether to enable an accounting delay timer. Possible values: true, false Default: false Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

-acct_start_delay_time The accounting start delay time. The test will wait for the specified delay time before sending the Accounting Request - start message for an MN. The delay is applied to the first start message and all subsequent start messages. Default: 10 Range: 0-1000000 Dependency: acct_start_delay_msg_en true

-acct_sut_port The UDP port that is used for RADIUS accounting on all SUTs. Default: 1813 Range: 0-65535 Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

-acct_secret The shared secret between a RADIUS NAS and an AAA server that is included in the encrypted Authenticator field in the Accounting Request messages sent to the SUT. Default: secret Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

-acct_user_name_inc Specifies whether the User-Name attribute is included and is provisioned with User Name in Accounting Request messages . Possible values: true, false

Sub Functions

139

Default: false Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

-acct_nas_identifier_inc Specifies whether the NAS-Identifier attribute is included in Accounting Request messages. Default: false Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

-acct_nas_ip_addr_inc Specifies whether the NAS-IP-Address attribute is included in Accounting Request messages. Possible values: true, false Default: false Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

-acct_ignore_rsp_en Specifies whether to ignore the accounting response. If it is true, it will allow the test to continue regardless of whether Accounting Responses are received after a Start, Interim Update, or Stop Accounting Request is sent. Default: false Dependency: aaa_test_type Authentication_With_Accounting| Accounting_Only

-acct_on_off_en Determines whether to send the accounting on/off message. If it is true, it will include Accounting-On and Accounting-Off Accounting Request messages in the test. Possible values: true, false. Default: false Dependency: aaa_test_type Authentication_With_Accounting|Accounting_Only

-rad_tdf_to_para_en Specifies whether to apply the Radius parameters from the Test Data File. Possible values: true, false. Default: false

-rad_to_para_tdf The name of the TDF file in which the Radius parameters are defined. Dependency: rad_tdf_to_para_en true

-coa_simulation_en Specifies whether to include support for RADIUS Change of Authorization requests. When the node receives an Access Request, Accounting Request Start, or Accounting Request Stop message, it will send a CoA Request to the SUT of your choice. Possible values: true, false Default: false

-coa_ret Determine the timing of the CoA return messages Possible values: coa_ack - The Access Accept is sent immediately after a successful authentication coa_nak - The Access Accept is delayed until either a CoA ACK or CoA NAK is received, or until retries are exhausted. none- The CoA retun is not delayed. Default: coa_ack Dependency: coa_simulation_en true

-das_key_type Specifies the DAS key type. Possible values: user_name, user_ip_address, acct_session_id

Sub Functions

140

Default: user_name Dependency: disconect_en true

-disconect_en Specifies whether to support for RADIUS Disconnect requests. When the node sends a Disconnect Request, the AAA session stops and tears down the AAA Session immediately. Possible values: true, false Default: false

-coa_auth_secret The secret known to both the AAA node and the CoA SUT. Default: secret Dependency: disconect_en true, coa_simulation_en true

-nas_iteration_limit_en Specifies whether to use the Set Iteration Limits to control how the RADIUS client iterates over the RADIUS IDs and source ports Possible values: true, false Default: false

-nas_start_port The start UDP port of NAS Port Range. Default: 2000 Range: 2000-65535 Dependency: nas_iteration_limit_en true

-nas_end_port The start UDP port of NAS Port Range. Default: 65535 Range: 2000-65535 Dependency: nas_iteration_limit_en true

-nas_start_session_id The start RADIUS session ID of the Session ID Range. Default: 0 Range: 0-255 Dependency: nas_iteration_limit_en true

-nas_end_session_id The stop RADIUS session ID of the Session ID Range. Default: 255 Range: 0-255 Dependency: nas_iteration_limit_en true

-nas_session_id_per_group Use the IDs per Group to specify the number of IDs to be used with a port before using to the next port Default: 1 Range: 1-255 Dependency: nas_iteration_limit_en true Return Values: status Success (1) or failure (0) of the operation. log Returned only when the status is 0 Examples: set ret [lsh::aaa_radius_client_config -mode create\ -tc_hnd $tc \ -nas_intf_type eth\ -nas_phy_intf "eth2"\ -aaa_sut_distribution_mode Round_Robin\ -nas_intf_ip_addr $ts_eht2\ -sut_name_list "$aaa_sut1 $aaa_sut2"\ -aaa_test_type Authentication_Only\ -auth_nas_identifier_inc true\ -auth_nas_ip_addr_inc true\ -auth_type EAP\ -auth_eap_sim_en true\ -auth_eap_retries 5]

Sub Functions

141

Returns: {status 1}

lsh::dhcp_client_config

Name: lsh::dhcp_client_config Purpose: Used to configure the IP pools which is used to allocate the DHCP address for the DHCP client. It can be configured on the following test case: IP APP NODE

Synopsis: lsh::dhcp_client_config -mode {create|modify} -tc_hnd <test case handle> -client_id <ALPHANUM> -hw_addr <ANY> -client_port <NUMERIC> -server_port <NUMERIC> -retry_count <0-65535> -lease_time_en {true|false} -lease_time <0-1814400> -enterprise_num <0-40303> -dhcp_offer_time <0-65535> -dhcp_ack_time <0-65535> -dhcp_rapid_en {true|false} -dhcp_rapid {true|false} -broadcast_bit_flag {true|false} -parms_req_en {true|false} -parms_req_list <ANY> -user_class_list <ANY> -dhcp_relay_agent_en <ANY> -relay_agent_phy_intf <ANY> -relay_agent_intf_ip_addr <IP> -relay_agent_mac_addr <MAC> -relay_agent_next_hop <IP> -relay_agent_out_bound_traffic_port <ANY> -relay_agent_node_addr_err_inj <0-5> -dhcp_server_addr <IP> -relay_agent_circut <ANY> -relay_agent_suboption <ANY> Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - the first time to configure the DHCP client related arguments on the -tc_hnd modify - modify the parameters on the test case specified by the -tc_hnd.

-tc_hnd Specifies the test case handle. This argument is mandatory.

-client_id Client-identifier option included in messages sent by the client. This value is used by the server to correlate a client request with an address binding. Default: user#

-hw_addr Defines the MAC address of the test server interface to which the server

Sub Functions

142

should send responses during the address allocation process. It is mandatory.

-client_port The UDP port that the client uses for DHCP traffic. Default: 68

-server_port The UDP port that the server uses for DHCP traffic. Default: 67

-retry_count The number of times a message is re-transmitted. Retries will be disabled when it is 0. Default: 3 Range: 0-65535

-lease_time_en Specifies whether include the IP address lease time option in messages sent by the client. Possible values: true, false Default: false

-lease_time Defines the lease time included in the message sent by the client. When it is 0, the server will assign a default lease time. Default: 1209600 Range: 0-1814400 Dependency: lease_time_en true

-enterprise_num Defines the client's IANA Enterprise Number, which is included in the Identity Association (IA) ID of the IAs that the client associates with each of its interfaces. Default: 0 Range: 0-40303 -dhcp_offer_time The time wait for a dhcpoffer message in an IPv4 test or an advertise message in an IPv6 test. Default: 1 Range: 0-65535

-dhcp_ack_time The time wait for a dhcpack message in an IPv4 test or an reply message in an IPv6 test. Default: 1 Range: 0-65535

-dhcp_rapid_en Specifies whether to include the Rapid Commit option in the Solicit message sent to a server. Possible values: true, false Default: false

-dhcp_rapid Specifies whether the Rapid Commit will be used. Default: false Possible values: true, false Dependency: dhcp_rapid_en true

-broadcast_bit_flag Specifies whether to enable the broadcast. Possible values: true, false Default: false

-parms_req_en Specifies whether to include the parameter Request List in the message sent by the client. Possible values: true, false Default: false

Sub Functions

143

-parms_req_list The Parameter Request List include in the message sent by the client. Dependency: parms_req_en true

-user_class_list Specifies the list of User Class option in messages sent by the client. The server may use the values in the list to determine the appropriate address pool for the client.

-dhcp_relay_agent_en Specifies whether to enable the DHCP relay agent. Possible values: true, false Default: false

-relay_agent_phy_intf The interface of the DHCP relay agent node. Dependency: dhcp_relay_agent_en true -relay_agent_intf_ip_addr The IP address of the DHCP relay agent node. Dependency: dhcp_relay_agent_en true

-relay_agent_mac_addr The MAC address of the DHCP relay agent node. Dependency: dhcp_relay_agent_en true

-relay_agent_next_hop The next hop IP address of the DHCP relay agent node. Dependency: dhcp_relay_agent_en true

-relay_agent_out_bound_traffic_port The outbound traffic port of the DHCP relay agent node. Dependency: dhcp_relay_agent_en true

-relay_agent_node_addr_err_inj Specifies the error inject of the DHCP relay agent node. Default: 0 Range: 0-5

-dhcp_server_addr The IP address of the DHCP server. Dependency: dhcp_relay_agent_en true

-relay_agent_circut An agent-local identifier of the circuit from which a DHCP client-to-server packet is received Default: cid# Dependency: dhcp_relay_agent_en true

-relay_agent_suboption Define the optional DHCP Relay Agent Sub Options. The value of relay_agent_suboption is a list, and each element in the list is a type value pair. For the type, the range is 2-255.

Return Values: status Success (1) or failure (0) of the operation. log Returned only when the status is 0

Examples: set ret [lsh::dhcp_client_config -mode create\ -tc_hnd $tc \ -hw_addr $ts_eth1_mac\ -parms_req_en true\ -lease_time_en true\ -lease_time 100\ -parms_req_list 2\ -dhcp_relay_agent_en true\ -relay_agent_intf_ip_addr $ts_eht2\ -relay_agent_phy_intf "eth2"\ -dhcp_server_addr "10.155.2.61"\

Sub Functions

144

-relay_agent_suboption {{5 567d} {3 5678}}] Returns: {status 1}

lsh::gtp_config

Name: lsh::gtp_config

Purpose: Used to configure the GTP related arguments. It can be configured on following test case: GGSN NODE

Synopsis: lsh::gtp_config -mode {create|modify} -test_hnd <test session handle> -tc_hnd <test case handle> -gtp_version {0|1} -gtp_use_gsn_sig_addr {0|1} -gtp_persistent_imsi_en {true|false} -gtp_charg_gate_addr_en {true|false} -gtp_charg_gate_addr <IP> -gtp_echo_msg_time <0-65535> -gtp_pdp_context_id <1-4294967295> -gtp_n3_req_attempts <1-65535> -gtp_c_tunnel_endpt_id <1-4294967295> -gtp_u_tunnel_endpt_id <1-4294967295> -gtp_t3_wait_time <1-65535> -gtp_inc_common_flags {true|false} -gtp_common_flags <0-255> -gtp_teardown_indicator {true|false} -gtp_inc_apn_restriction {true|false} -gtp_apn_restriction <NUMERIC> -gtp_tdf_to_para_en {true|false} -gtp_tdf_to_para <ANY>

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - the first time to configure the GTP related arguments on the -tc_hnd modify - modify the parameters on the test case specified by the -tc_hnd. -tc_hnd Specifies the test case handle. This argument is mandatory. -gtp_version Specifies the GTP version. Possible values: 0, 1 Default: 1 -gtp_use_gsn_sig_addr Specifies whether to use the GSN singnalling address or not. If the value is 1, then it will use the GSN singnalling address Possible values: 0, 1 Default: 0 -gtp_persistent_imsi_en Specifies whether to enable the persistent IMSI/MEI or not. If the value is true, then it will enable the persistent IMSI/MEI Possible values: true, false

Sub Functions

145

Default: false -gtp_charg_gate_addr_en Specifies whether to use the charging gateway addr to sent to SGSN or not. If the value is true, then it will use the charging gateway addr to sent to SGSN Possible values: true, false Default: false -gtp_charg_gate_addr When the charging gateway addr sent to SGSN is used, then you should specify the charging gateway address. Dependency: gtp_charg_gate_addr_en true -gtp_echo_msg_time Specifies the interval of the periodic Echo message time. Default: 0 Range: 0-65535 -gtp_pdp_context_id The starting PDP context charging id that sent to the GGSN. The Charging ID is used by the SGSN to identify all CDRs produced by a PDP context. The GGSN informs the SGSN of the ID to use for each context. Default: 1 Range: 1-4294967295 -gtp_n3_req_attempts The maximum number of attempts made by GTP to send a request message without receiving an associated response message from the GGSN. Default: 5 Range: 1-65535 -gtp_c_tunnel_endpt_id The starting GTPC tunnel endpoint ID. Default: 1000000 Range: 1-4294967295 -gtp_u_tunnel_endpt_id The starting GTPU tunnel endpoint ID Default: 2000000 Range: 1-4294967295 -gtp_t3_wait_time The number of seconds to wait for a command request response. The T3 timer starts when a signaling request message (for which a response has been defined) is sent. Default: 20 Range: 1-65535 -gtp_inc_common_flags Specifies whether to include the Common Flags IE in messages sent to the SGSN. Default: false -gtp_common_flags The value of the Common Flags IE in messages sent to the SGSN. It can be configured only when gtp_inc_common_flags is true Default: 1 Range: 0-255 Dependency: gtp_inc_common_flags true -gtp_teardown_indicator Specifies whether to include a Teardown Indicator in the Delete PDP Context message. Default: false -gtp_inc_apn_restriction Specifies whether to include the optional APN Restriction information element messages sent by the GGSN node, Default: false

Sub Functions

146

-gtp_apn_restriction The Maximum APN Restriction used for all APNs Default: 0 Range: 0-255 Dependency: gtp_inc_apn_restriction true -gtp_tdf_to_para_en Specifies whether to the values defined in the Test Data File for each MN. Default: false -gtp_tdf_to_para The name of the Test Data File in which the values used for each MN is defined. Dependency: gtp_tdf_to_para_en true


Examples: set ret [::lsh::gtp_config \ -mode create\ -tc_hnd $tc\ -gtp_version 1\ -gtp_use_gsn_sig_addr 1\ -gtp_charg_gate_addr_en true\ -gtp_charg_gate_addr 10.0.0.2\ -gtp_echo_msg_time 1\ -gtp_pdp_context_id 2\ -gtp_n3_req_attempts 7\ -gtp_t3_wait_time 21 \ -gtp_inc_common_flags true\ -gtp_inc_apn_restriction true]

Return: {status 1}

lsh::gtp'_config

Name: lsh::gtp'_config

Purpose: Used to configure the GTP' related arguments. It can be configured on following test case: GGSN NODE

Synopsis: lsh::gtp'_config -mode {create|modify} -tc_hnd <test case handle> -primary_cgf_sut_name <ANY> -secondary_cgf_sut_en {true|false} -secondary_cgf_sut_name <ANY> -gtp'_node_intf_type {eth|atm} -gtp'_node_phy_intf <ANY> -gtp'_node_intf_ip_addr <IP> -gtp'_node_vpi <ANY> -gtp'_node_vci <NUMERIC> -gtp'_node_node_num <NUMERIC> -gtp'_node_mac_addr <MAC> -gtp'_node_next_hop <IP> -gtp'_node_out_bound_traffic_port <ANY> -gtp'_node_addr_err_inj <0-5> -data_record_type {Landslide_GGSN|GGSN|EGSN}

Sub Functions

147

-cdr_en {true|false} -cdr_intervals <1-65536> -cdr_send_cycle {Continuous|Fixed} -fixed_number <1-65535> -traf_vol_changes_en {0|1} -traf_vol_qos_change_en {0|1} -traf_vol_record_closure_en {0|1} -traf_vol_cgi_sai_change_en {0|1} -traf_vol_dt_establishment_en {0|1} -traf_vol_tai_change_en {0|1} -traf_vol_tariff_change_en {0|1} -traf_vol_ecgi_change_en {0|1} -traf_vol_dt_change_en {0|1} -traf_vol_rai_change_en {0|1} -traf_vol_user_location_change_en {0|1} -serv_data_changes_en {0|1} -serv_data_qos_change_en {0|1} -serv_data_sgsn_change_en {0|1} -serv_data_sgsn_plmn_id_change_en {0|1} -serv_data_tariff_change_en {0|1} -serv_data_pdp_context_release_en {0|1} -serv_data_rat_change_en {0|1} -serv_data_serv_idled_out_en {0|1} -serv_data_config_change_en {0|1} -serv_data_serv_stop_en {0|1} -serv_data_dcca_time_thres_en {0|1} -serv_data_dcca_vol_thres_en {0|1} -serv_data_dcca_serv_spec_thres_en {0|1} -serv_data_dcca_time_exhausted_en {0|1} -serv_data_dcca_vol_exhausted_en {0|1} -serv_data_dcca_val_timeout_en {0|1} -serv_data_dcca_re_auth_req_en {0|1} -serv_data_dcca_cont_session_en {0|1} -serv_data_dcca_retry_termi_session_en {0|1} -serv_data_dcca_termi_session_en {0|1} -serv_data_cgi_sai_change_en {0|1} -serv_data_rai_change_en {0|1} -serv_data_dcca_serv_spec_unit_exhausted_en {0|1} -serv_data_record_closure_en {0|1} -serv_data_time_limit_en {0|1} -serv_data_vol_limit_en {0|1} -serv_data_serv_spec_unit_limit_en {0|1} -serv_data_enevlope_closure_en {0|1} -init_mode {Active|Passive} -valid_sut {true|false} -transport_type {UDP|TCP} -dest_port <0-65535> -node_alive_en {true|false} -periodic_echo_en {true|false} -periodic_echo_time <5-900> -retry_interval <1-65536> -retries <0-65536> -gtp'_version {0|1|2} -header_len {6-octet|20-octet}

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - the first time to configure the GTP' related arguments on the -tc_hnd modify - modify the parameters on the test case specified by the -tc_hnd. -tc_hnd Specifies the test case handle. This argument is mandatory. -primary_cgf_sut_name The name of the primary CGF SUT. -secondary_cgf_sut_en

Sub Functions

148

Specifies whether to use the secondary CGF SUT. Possible values: true, false. Default: false -secondary_cgf_sut_name The name of the secondary SUT. Dependency: secondary_cgf_sut_en true -gtp'_node_intf_type The interface type of GTP' Node. Possible values: eth, atm Default: eth -gtp'_node_phy_intf The interface of the GTP' Node. -gtp'_node_intf_ip_addr The IP address of the GTP' Node. -gtp'_node_vpi The vpi of GTP' Node. it can only be used when the interface type is ATM Dependency: gtp'_node_intf_type atm -gtp'_node_vci The vci of GTP' Node. it can only be used when the interface type is ATM Default: 0 Dependency: gtp'_node_intf_type atm -gtp'_node_node_num The number of the GTP' Node. Default: 1 -gtp'_node_mac_addr The mac address of the GTP' Node. -gtp'_node_next_hop The next hop of the GTP' Node. -gtp'_node_out_bound_traffic_port The out bound traffic port of the GTP' Node. -gtp'_node_addr_err_inj The error inject of the GTP' Node. Default: 0 Range: 0-5 -data_record_type The type of CDR that the GTP' node will generate Possible values: Landslide_GGSN, GGSN, EGSN - Default: Landslide_GGSN -cdr_en Specifies whether to emulate change in charging conditions. Possible values: true, false Default: false -cdr_intervals The interval of the CDR. Default: 10 Range: 1-65536 Dependency: cdr_en true -cdr_send_cycle The CDR send cycle. Possible values: Continuous, Fixed Default: false -fixed_number If the CDR send cycle is Fixed, then should specify the number of the cycle. Default: 5 Range: 1-65535 Dependency: cdr_send_cycle Fixed

Sub Functions

149

-traf_vol_changes_en Specifies whether to include the traffic volumes item changes in the CDR. At least one kind of traffic volumes item should be included if traffic volumes item changes is enabled Possible values: 0, 1 Default: 0 Dependency: cdr_en true -traf_vol_qos_change_en Specifies whether to include the QoS change of traffic volumes in the CDR. Possible values: 0, 1 Default: 0 Dependency: traf_vol_changes_en 1 -traf_vol_record_closure_en Specifies whether to include the Record Closure of traffic volumes in the CDR. Possible values: 0, 1 Default: 0 Dependency: traf_vol_changes_en 1 -traf_vol_cgi_sai_change_en Specifies whether to include the CGI-SAI change of traffic volumes in the CDR. Possible values: 0, 1 Default: 0 Dependency: traf_vol_changes_en 1 -traf_vol_dt_establishment_en Specifies whether to include the DT establishment of traffic volumes in the CDR. Possible values: 0, 1 Default: 0 Dependency: traf_vol_changes_en 1 -traf_vol_tai_change_en Specifies whether to include the TAI change of traffic volumes in the CDR. Possible values: 0, 1 Default: 0 Dependency: traf_vol_changes_en 1 -traf_vol_tariff_change_en Specifies whether to include the Tariff change of traffic volumes in the CDR. Possible values: 0, 1 Default: 0 Dependency: traf_vol_changes_en 1 -traf_vol_ecgi_change_en Specifies whether to include the eCGI change of traffic volumes in the CDR. Possible values: 0, 1 Default: 0 Dependency: traf_vol_changes_en 1 -traf_vol_dt_change_en Specifies whether to include the DT Removal change of traffic volumes in the CDR. Possible values: 0, 1 Default: 0 Dependency: traf_vol_changes_en 1 -traf_vol_rai_change_en Specifies whether to include the RAI change of traffic volumes in the CDR. Possible values: 0, 1 Default: 0 Dependency: traf_vol_changes_en 1 -traf_vol_user_location_change_en Specifies whether to include the User Location change of traffic volumes in the CDR. Possible values: 0, 1

Sub Functions

150

Default: 0 Dependency: traf_vol_changes_en 1 -serv_data_changes_en Specifies whether to include the service data item changes in the CDR. At least one kind of service data item should be included if service data item changes is enabled Possible values: 0, 1 Default: 0 Dependency: cdr_en true&data_record_type EGSN -serv_data_qos_change_en Specifies whether to include the QoS change of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_sgsn_change_en Specifies whether to include the SGSN change of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_sgsn_plmn_id_change_en Specifies whether to include the SGSN PLMN ID change of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_tariff_change_en Specifies whether to include the Tariff change of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_pdp_context_release_en Specifies whether to include the PDPD context release of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_rat_change_en Specifies whether to include the RAT change of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_serv_idled_out_en Specifies whether to include the service idled out of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_config_change_en Specifies whether to include the configuration change of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_serv_stop_en Specifies whether to include the service stop of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_time_thres_en Specifies whether to include the DCCA time threshold of service data in the CDR. Possible values: 0, 1

Sub Functions

151

Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_vol_thres_en Specifies whether to include the DCCA volume threshold of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_serv_spec_thres_en Specifies whether to include the DCCA service specific threshold of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_time_exhausted_en Specifies whether to include the DCCA time exhausted of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_vol_exhausted_en Specifies whether to include the DCCA volume exhausted of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_val_timeout_en Specifies whether to include the DCCA validity timeout of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_re_auth_req_en Specifies whether to include the DCCA re-authorization request of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_cont_session_en Specifies whether to include the DCCA continue session of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_retry_termi_session_en Specifies whether to include the DCCA retry&terminate session of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_termi_session_en Specifies whether to include the DCCA terminate session of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_cgi_sai_change_en Specifies whether to include the CGI-SAI change of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1

Sub Functions

152

-serv_data_rai_change_en Specifies whether to include the RAI change of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_dcca_serv_spec_unit_exhausted_en Specifies whether to include the DCCA service specific unit exhausted of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_record_closure_en Specifies whether to include the record closure of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_time_limit_en Specifies whether to include the time limit of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_vol_limit_en Specifies whether to include the volume limit of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_serv_spec_unit_limit_en Specifies whether to include the service specific unit limit of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -serv_data_enevlope_closure_en Specifies whether to include the envelope closure of service data in the CDR. Possible values: 0, 1 Default: 0 Dependency: serv_data_changes_en 1 -init_mode The initiate mode of the GTP' Node. It can initiate the connection with the CGF in when the mode is Active. Default: Active -valid_sut Validates the SUT that will receive the Data Records generated by the GTP' node. Default: false Dependency: init_mode Passive -transport_type Specifies the GTP' transport protocol Default: UDP -dest_port The CGF's GTP' port. Default: 3386 Range: 0-65535 Dependency: init_mode 0,valid_sut true -node_alive_en Specifies whether to send the node alive message. Default: false -periodic_echo_en

Sub Functions

153

Specifies whether to send periodic Echo Request messages to the CGF. Default: false -periodic_echo_time Defines the number of seconds between periodic Echo Request messages sent to the CGF. Default: 5 Range: 5-900 Dependency: periodic_echo_en true -retry_interval The interval that between the message sent. Default: 10 Range: 1-65536 -retries The retry times to send the message. Default: 5 Range: 0-65536 -gtp'_version The latest GTP' version supported by the CGF Default: 0 Dependency: data_record_type GGSN -header_len The GTP' header length that will be used in the test. You can only specify a length that is valid for the selected GTP' version. Default: 6-octet Dependency: data_record_type GGSN


Examples: set ret [::lsh::gtp'_config \ -mode create \ -tc_hnd $tc \ -primary_cgf_sut_name $gtp2_sut \ -gtp'_node_phy_intf "eth2" \ -gtp'_node_intf_ip_addr $ts_eht2 \ -data_record_type GGSN \ -periodic_echo_en true\ -node_alive_en true\ -init_mode Passive\ -valid_sut true\ -gtp'_version 0\ -header_len 20-octet] Return: {status 1}

lsh::ip_pools_config

Name: lsh::ip_pools_config

Description: Used to configure the IP pools which is used to allocate the DHCP address for the DHCP client. It can be configured on following test cases: DHCP Server Node AAA Server Node

Synopsis:

Sub Functions

154

lsh::ip_pools_config -mode {create|modify} -tc_hnd < test_case_handle> -addr_pools_num <1-30> -pool_select_cycle_method { Exhaustive|Round-robin } -pool1_addr_num <1-2000000> -pool1_start_ip_addr <IP> -pool1_queue_type { FIFO| LIFO } -pool1_incr_by { Interface-ID| Prefix } -pool1_pool_id <ANY> -pool1_lease_time <NUMERIC> -pool1_alt_pool_id <ANY> -pool2_addr_num <1-2000000> -pool2_start_ip_addr <IP> -pool2_queue_type { FIFO| LIFO } -pool2_incr_by { Interface-ID| Prefix } -pool2_pool_id <ANY> -pool2_lease_time <NUMERIC> -pool2_alt_pool_id <ANY> -pool3_addr_num <1-2000000> -pool3_start_ip_addr <IP> -pool3_queue_type { FIFO| LIFO } -pool3_incr_by { Interface-ID| Prefix } -pool3_pool_id <ANY> -pool3_lease_time <NUMERIC> -pool3_alt_pool_id <ANY> -pool4_addr_num <1-2000000> -pool4_start_ip_addr <IP> -pool4_queue_type { FIFO| LIFO } -pool4_incr_by { Interface-ID| Prefix } -pool4_pool_id <ANY> -pool4_lease_time <NUMERIC> -pool4_alt_pool_id <ANY> -pool5_addr_num <1-2000000> -pool5_start_ip_addr <IP> -pool5_queue_type { FIFO| LIFO } -pool5_incr_by { Interface-ID| Prefix } -pool5_pool_id <ANY> -pool5_lease_time <NUMERIC> -pool5_alt_pool_id <ANY> -pool6_addr_num <1-2000000> -pool6_start_ip_addr <IP> -pool6_queue_type { FIFO| LIFO } -pool6_incr_by { Interface-ID| Prefix } -pool6_pool_id <ANY> -pool6_lease_time <NUMERIC> -pool6_alt_pool_id <ANY> -pool7_addr_num <1-2000000> -pool7_start_ip_addr <IP> -pool7_queue_type { FIFO| LIFO } -pool7_incr_by { Interface-ID| Prefix } -pool7_pool_id <ANY> -pool7_lease_time <NUMERIC> -pool7_alt_pool_id <ANY> -pool8_addr_num <1-2000000> -pool8_start_ip_addr <IP> -pool8_queue_type { FIFO| LIFO } -pool8_incr_by { Interface-ID| Prefix } -pool8_pool_id <ANY> -pool8_lease_time <NUMERIC> -pool8_alt_pool_id <ANY> -pool9_addr_num <1-2000000> -pool9_start_ip_addr <IP> -pool9_queue_type { FIFO| LIFO } -pool9_incr_by { Interface-ID| Prefix } -pool9_pool_id <ANY> -pool9_lease_time <NUMERIC> -pool9_alt_pool_id <ANY> -pool10_addr_num <1-2000000> -pool10_start_ip_addr <IP> -pool10_queue_type { FIFO| LIFO }

Sub Functions

155

-pool10_incr_by { Interface-ID| Prefix } -pool10_pool_id <ANY> -pool10_lease_time <NUMERIC> -pool10_alt_pool_id <ANY> -pool11_addr_num <1-2000000> -pool11_start_ip_addr <IP> -pool11_queue_type { FIFO| LIFO } -pool11_incr_by { Interface-ID| Prefix } -pool11_pool_id <ANY> -pool11_lease_time <NUMERIC> -pool11_alt_pool_id <ANY> -pool12_addr_num <1-2000000> -pool12_start_ip_addr <IP> -pool12_queue_type { FIFO| LIFO } -pool12_incr_by { Interface-ID| Prefix } -pool12_pool_id <ANY> -pool12_lease_time <NUMERIC> -pool12_alt_pool_id <ANY> -pool13_addr_num <1-2000000> -pool13_start_ip_addr <IP> -pool13_queue_type { FIFO| LIFO } -pool13_incr_by { Interface-ID| Prefix } -pool13_pool_id <ANY> -pool13_lease_time <NUMERIC> -pool13_alt_pool_id <ANY> -pool14_addr_num <1-2000000> -pool14_start_ip_addr <IP> -pool14_queue_type { FIFO| LIFO } -pool14_incr_by { Interface-ID| Prefix } -pool14_pool_id <ANY> -pool14_lease_time <NUMERIC> -pool14_alt_pool_id <ANY> -pool15_addr_num <1-2000000> -pool15_start_ip_addr <IP> -pool15_queue_type { FIFO| LIFO } -pool15_incr_by { Interface-ID| Prefix } -pool15_pool_id <ANY> -pool15_lease_time <NUMERIC> -pool15_alt_pool_id <ANY> -pool16_addr_num <1-2000000> -pool16_start_ip_addr <IP> -pool16_queue_type { FIFO| LIFO } -pool16_incr_by { Interface-ID| Prefix } -pool16_pool_id <ANY> -pool16_lease_time <NUMERIC> -pool16_alt_pool_id <ANY> -pool17_addr_num <1-2000000> -pool17_start_ip_addr <IP> -pool17_queue_type { FIFO| LIFO } -pool17_incr_by { Interface-ID| Prefix } -pool17_pool_id <ANY> -pool17_lease_time <NUMERIC> -pool17_alt_pool_id <ANY> -pool18_addr_num <1-2000000> -pool18_start_ip_addr <IP> -pool18_queue_type { FIFO| LIFO } -pool18_incr_by { Interface-ID| Prefix } -pool18_pool_id <ANY> -pool18_lease_time <NUMERIC> -pool18_alt_pool_id <ANY> -pool19_addr_num <1-2000000> -pool19_start_ip_addr <IP> -pool19_queue_type { FIFO| LIFO } -pool19_incr_by { Interface-ID| Prefix } -pool19_pool_id <ANY> -pool19_lease_time <NUMERIC> -pool19_alt_pool_id <ANY> -pool20_addr_num <1-2000000> -pool20_start_ip_addr <IP> -pool20_queue_type { FIFO| LIFO } -pool20_incr_by { Interface-ID| Prefix }

Sub Functions

156

-pool20_pool_id <ANY> -pool20_lease_time <NUMERIC> -pool20_alt_pool_id <ANY> -pool21_addr_num <1-2000000> -pool21_start_ip_addr <IP> -pool21_queue_type { FIFO| LIFO } -pool21_incr_by { Interface-ID| Prefix } -pool21_pool_id <ANY> -pool21_lease_time <NUMERIC> -pool21_alt_pool_id <ANY> -pool22_addr_num <1-2000000> -pool22_start_ip_addr <IP> -pool22_queue_type { FIFO| LIFO } -pool22_incr_by { Interface-ID| Prefix } -pool22_pool_id <ANY> -pool22_lease_time <NUMERIC> -pool22_alt_pool_id <ANY> -pool23_addr_num <1-2000000> -pool23_start_ip_addr <IP> -pool23_queue_type { FIFO| LIFO } -pool23_incr_by { Interface-ID| Prefix } -pool23_pool_id <ANY> -pool23_lease_time <NUMERIC> -pool23_alt_pool_id <ANY> -pool24_addr_num <1-2000000> -pool24_start_ip_addr <IP> -pool24_queue_type { FIFO| LIFO } -pool24_incr_by { Interface-ID| Prefix } -pool24_pool_id <ANY> -pool24_lease_time <NUMERIC> -pool24_alt_pool_id <ANY> -pool25_addr_num <1-2000000> -pool25_start_ip_addr <IP> -pool25_queue_type { FIFO| LIFO } -pool25_incr_by { Interface-ID| Prefix } -pool25_pool_id <ANY> -pool25_lease_time <NUMERIC> -pool25_alt_pool_id <ANY> -pool26_addr_num <1-2000000> -pool26_start_ip_addr <IP> -pool26_queue_type { FIFO| LIFO } -pool26_incr_by { Interface-ID| Prefix } -pool26_pool_id <ANY> -pool26_lease_time <NUMERIC> -pool26_alt_pool_id <ANY> -pool27_addr_num <1-2000000> -pool27_start_ip_addr <IP> -pool27_queue_type { FIFO| LIFO } -pool27_incr_by { Interface-ID| Prefix } -pool27_pool_id <ANY> -pool27_lease_time <NUMERIC> -pool27_alt_pool_id <ANY> -pool28_addr_num <1-2000000> -pool28_start_ip_addr <IP> -pool28_queue_type { FIFO| LIFO } -pool28_incr_by { Interface-ID| Prefix } -pool28_pool_id <ANY> -pool28_lease_time <NUMERIC> -pool28_alt_pool_id <ANY> -pool29_addr_num <1-2000000> -pool29_start_ip_addr <IP> -pool29_queue_type { FIFO| LIFO } -pool29_incr_by { Interface-ID| Prefix } -pool29_pool_id <ANY> -pool29_lease_time <NUMERIC> -pool29_alt_pool_id <ANY> -pool30_addr_num <1-2000000> -pool30_start_ip_addr <IP> -pool30_queue_type { FIFO| LIFO } -pool30_incr_by { Interface-ID| Prefix } -pool30_pool_id <ANY>

Sub Functions

157

-pool30_lease_time <NUMERIC> -pool30_alt_pool_id <ANY>

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - create the parameters in the test session specified by the -tc_hnd modify - modify the parameters on the test case specified by the -tc_hnd. -tc_hnd Specify the test case handle. This argument is mandatory. It can be used to create and modify the parameters configured on this test case. -addr_pools_num Specify the number of IP address pools. Range: 1-30 Default: 1 -pool_select_cycle_method Specify the method used to select an address pool when more than one address pool is defined and a Pool Identifier or Alternate Pool Identifier is not provided in a request message. Possible values: Exhaustive, Round-robin Default: Exhaustive -pool1_addr_num The number of address in pool1. Range: 1-2000000 Default: 1 -pool1_start_ip_addr The first IPv4 or IPv6 address for address pool1. Default: 1.1.1.1 -pool1_queue_type The Queue type in pool1. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO -pool1_incr_by When pool1 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID -pool1_pool_id The pool identifier of pool1. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None -pool1_lease_time The lease time in pool1. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP Pool1 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Note: It can only be used in DHCP Server Node test case. -pool1_alt_pool_id Alternate Pool Identifier of pool1. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier.

Sub Functions

158

Default: None Note: It can only be used in DHCP Server Node test case. -pool2_addr_num The number of address in pool2. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=2 -pool2_start_ip_addr The first IPv4 or IPv6 address for address pool2. Default: 1.1.1.1 Dependency: addr_pools_num >=2 -pool2_queue_type The Queue type in pool2. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO Dependency: addr_pools_num >=2 -pool2_incr_by When pool2 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=2 -pool2_pool_id The pool identifier of pool2. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=2 -pool2_lease_time The lease time in pool2. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool2 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=2 Note: It can only be used in DHCP Server Node test case. -pool2_alt_pool_id Alternate Pool Identifier of pool2. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=2 Note: It can only be used in DHCP Server Node test case. -pool3_addr_num The number of address in pool3. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=3 -pool3_start_ip_addr The first IPv4 or IPv6 address for address pool3. Default: 1.1.1.1 Dependency: addr_pools_num >=3 -pool3_queue_type The Queue type in pool3. It is used to select the method used to determine the order in which addresses are allocated from the pool.

Sub Functions

159

Possible value: FIFO, LIFO Default: FIFO dependency: addr_pools_num >=3 -pool3_incr_by When pool3 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=3 -pool3_pool_id The pool identifier of pool3. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=3 -pool3_lease_time The lease time in pool3. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool3 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=3 Note: It can only be used in DHCP Server Node test case. -pool3_alt_pool_id Alternate Pool Identifier of pool3. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=3 Note: It can only be used in DHCP Server Node test case. -pool4_addr_num The number of address in pool4. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=4 -pool4_start_ip_addr The first IPv4 or IPv6 address for address pool4. Default: 1.1.1.1 Dependency: addr_pools_num >=4 -pool4_queue_type The Queue type in pool4. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO dependency: addr_pools_num >=4 -pool4_incr_by When pool4 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=4 -pool4_pool_id The pool identifier of pool4. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated.

Sub Functions

160

Default: None Dependency: addr_pools_num >=4 -pool4_lease_time The lease time in pool4. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool4 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=4 Note: It can only be used in DHCP Server Node test case. -pool4_alt_pool_id Alternate Pool Identifier of pool4. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=4 Note: It can only be used in DHCP Server Node test case. -pool5_addr_num The number of address in pool5. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=5 -pool5_start_ip_addr The first IPv4 or IPv6 address for address pool5. Default: 1.1.1.1 Dependency: addr_pools_num >=5 -pool5_queue_type The Queue type in pool5. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO dependency: addr_pools_num >=5 -pool5_incr_by When pool5 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=5 -pool5_pool_id The pool identifier of pool5. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=5 -pool5_lease_time The lease time in pool5. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool5 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=5 Note: It can only be used in DHCP Server Node test case. -pool5_alt_pool_id Alternate Pool Identifier of pool5. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a

Sub Functions

161

relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=5 Note: It can only be used in DHCP Server Node test case. -pool6_addr_num The number of address in pool6. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=6 -pool6_start_ip_addr The first IPv4 or IPv6 address for address pool6. Default: 1.1.1.1 Dependency: addr_pools_num >=6 -pool6_queue_type The Queue type in pool6. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO dependency: addr_pools_num >=6 -pool6_incr_by When pool6 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=6 -pool6_pool_id The pool identifier of pool6. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=6 -pool6_lease_time The lease time in pool6. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool6 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=6 Note: It can only be used in DHCP Server Node test case. -pool6_alt_pool_idNH Alternate Pool Identifier of pool6. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=6 Note: It can only be used in DHCP Server Node test case. -pool7_addr_num The number of address in pool7. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=7 -pool7_start_ip_addr The first IPv4 or IPv6 address for address pool7. Default: 1.1.1.1 Dependency: addr_pools_num >=7 -pool7_queue_type The Queue type in pool7. It is used to select the method used to

Sub Functions

162

determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO dependency: addr_pools_num >=7 -pool7_incr_by When pool7 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=7 -pool7_pool_id The pool identifier of pool7. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=7 -pool7_lease_time The lease time in pool7. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool7 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=7 Note: It can only be used in DHCP Server Node test case. -pool7_alt_pool_id Alternate Pool Identifier of pool7. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=7 Note: It can only be used in DHCP Server Node test case. -pool8_addr_num The number of address in pool8. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=8 -pool8_start_ip_addr The first IPv4 or IPv6 address for address pool8. Default: 1.1.1.1 Dependency: addr_pools_num >=8 -pool8_queue_type The Queue type in pool8. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO Dependency: addr_pools_num >=8 -pool8_incr_by When pool8 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=8 -pool8_pool_id The pool identifier of pool8. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will

Sub Functions

163

be allocated. Default: None Dependency: addr_pools_num >=8 -pool8_lease_time The lease time in pool8. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool8 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=8 Note: It can only be used in DHCP Server Node test case. -pool8_alt_pool_id Alternate Pool Identifier of pool8. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=8 Note: It can only be used in DHCP Server Node test case. -pool9_addr_num The number of address in pool9. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=9 -pool9_start_ip_addr The first IPv4 or IPv6 address for address pool9. Default: 1.1.1.1 Dependency: addr_pools_num >=9 -pool9_queue_type The Queue type in pool9. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO Dependency: addr_pools_num >=9 -pool9_incr_by When pool9 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=9 -pool9_pool_id The pool identifier of pool9. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=9 -pool9_lease_time The lease time in pool9. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool9 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=9 Note: It can only be used in DHCP Server Node test case. -pool9_alt_pool_id Alternate Pool Identifier of pool9. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier.

Sub Functions

164

Default: None Dependency: addr_pools_num >=9 Note: It can only be used in DHCP Server Node test case. -pool10_addr_num The number of address in pool10. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=10 -pool10_start_ip_addr The first IPv4 or IPv6 address for address pool10. Default: 1.1.1.1 Dependency: addr_pools_num >=10 -pool10_queue_type The Queue type in pool10. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO Dependency: addr_pools_num >=10 -pool10_incr_by When pool10 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=10 -pool10_pool_id The pool identifier of pool10. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=10 -pool10_lease_time The lease time in pool10. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool10 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=10 Note: It can only be used in DHCP Server Node test case. -pool10_alt_pool_id Alternate Pool Identifier of pool10. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=10 Note: It can only be used in DHCP Server Node test case. -pool11_addr_num The number of address in pool11. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=11 -pool11_start_ip_addr The first IPv4 or IPv6 address for address pool11. Default: 1.1.1.1 Dependency: addr_pools_num >=11 -pool11_queue_type The Queue type in pool11. It is used to select the method used to determine the order in which addresses are allocated from the pool.

Sub Functions

165

Possible value: FIFO, LIFO Default: FIFO Dependency: addr_pools_num >=11 -pool11_incr_by When pool11 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=11 -pool11_pool_id The pool identifier of pool11. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=11 -pool11_lease_time The lease time in pool11. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool11 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=11 Note: It can only be used in DHCP Server Node test case. -pool11_alt_pool_id Alternate Pool Identifier of pool11. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=11 Note: It can only be used in DHCP Server Node test case. -pool12_addr_num The number of address in pool12. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=12 -pool12_start_ip_addr The first IPv4 or IPv6 address for address pool12. Default: 1.1.1.1 Dependency: addr_pools_num >=12 -pool12_queue_type The Queue type in pool12. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO Dependency: addr_pools_num >=12 -pool12_incr_by When pool12 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=12 -pool12_pool_id The pool identifier of pool12. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None

Sub Functions

166

Dependency: addr_pools_num >=12 -pool12_lease_time The lease time in pool12. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool12 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=12 Note: It can only be used in DHCP Server Node test case. -pool12_alt_pool_id Alternate Pool Identifier of pool12. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=12 Note: It can only be used in DHCP Server Node test case. -pool13_addr_num The number of address in pool13. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=13 -pool13_start_ip_addr The first IPv4 or IPv6 address for address pool13. Default: 1.1.1.1 Dependency: addr_pools_num >=13 -pool13_queue_type The Queue type in pool13. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO Dependency: addr_pools_num >=13 -pool13_incr_by When pool13 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=13 -pool13_pool_id The pool identifier of pool13. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=13 -pool13_lease_time The lease time in pool13. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool13 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=13 Note: It can only be used in DHCP Server Node test case. -pool13_alt_pool_id Alternate Pool Identifier of pool13. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's

Sub Functions

167

Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=13 Note: It can only be used in DHCP Server Node test case. -pool14_addr_num The number of address in pool14. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=14

-pool14_start_ip_addr The first IPv4 or IPv6 address for address pool14. Default: 1.1.1.1 Dependency: addr_pools_num >=14

-pool14_queue_type The Queue type in pool14. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO Default: FIFO Dependency: addr_pools_num >=14

-pool14_incr_by When pool14 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=14

-pool14_pool_id The pool identifier of pool14. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=14

-pool14_lease_time The lease time in pool14. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP pool14 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=14 Note: It can only be used in DHCP Server Node test case.

-pool14_alt_pool_id Alternate Pool Identifier of pool14. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=14 Note: It can only be used in DHCP Server Node test case.

-pool15_addr_num The number of address in pool15. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=15


Sub Functions

168










-pool16_pool_id The pool identifier of pool16. When you define more than one address

Sub Functions

169

pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None Dependency: addr_pools_num >=16









-pool17_alt_pool_id

Sub Functions

170

Alternate Pool Identifier of pool17. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=17 Note: It can only be used in DHCP Server Node test case.









Sub Functions

171










-pool20_incr_by When pool20 is IPv6 address pool, use this to determine which part of the address is incremented: the interface identifier or the subnet prefix. It

Sub Functions

172

is not applicable to IPv4 address pools. Possible value: Interface-ID, Prefix Default: Interface-ID Dependency: addr_pools_num >=20









-pool21_lease_time The lease time in pool21. It is the maximum number of seconds that a DHCP client's binding can remain established with the address allocated by IP

Sub Functions

173

pool21 before it expires. If the client requests a lease time, the request is ignored. Default: 60 Dependency: addr_pools_num >=21 Note: It can only be used in DHCP Server Node test case.









Sub Functions

174










-pool24_queue_type The Queue type in pool24. It is used to select the method used to determine the order in which addresses are allocated from the pool. Possible value: FIFO, LIFO

Sub Functions

175

Default: FIFO Dependency: addr_pools_num >=24









-pool25_pool_id The pool identifier of pool25. When you define more than one address pool, the server node may compare Pool Identifier to information received in the request message in order to determine from which pool an address will be allocated. Default: None

Sub Functions

176

Dependency: addr_pools_num >=25









-pool26_alt_pool_id Alternate Pool Identifier of pool26. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a

Sub Functions

177

relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=26 Note: It can only be used in DHCP Server Node test case.







-pool27_alt_pool_id Alternate Pool Identifier of pool27. In the DHCP Server Node test case, the Alternate Pool Identifier may be used in the address pool selection process when more than one pool is defined. When the User Class option is not present in an IPv4 discover request that has been forwarded by a relay agent, the relay agent's IP address is compared to each pool's Alternate Pool Identifier. Default: None Dependency: addr_pools_num >=27 Note: It can only be used in DHCP Server Node test case. -pool28_addr_num The number of address in pool28. Range: 1-2000000 Default: 1 Dependency: addr_pools_num >=28


Sub Functions

178










Sub Functions

179










Sub Functions

180



Examples: ::lsh::ip_pools_config \ -mode create\ -tc_hnd $tc\ -pool_select_cycle_method Roud_robin\ -addr_pools_num 30\ -pool1_addr_num 10\ -pool1_start_ip_addr "10.155.2.1"\ -pool1_queue_type "FIFO"\ -pool1_incr_by "Interface-ID"\ -pool1_pool_id "10.155.2.0"\ -pool1_lease_time 60\ -pool1_alt_pool_id "1"\ -pool2_addr_num 10\ -pool2_start_ip_addr "10.155.3.1"\ -pool2_queue_type "FIFO"\ -pool2_incr_by "Interface-ID"\ -pool2_pool_id "10.155.3.0"\ -pool2_lease_time 60\ -pool2_alt_pool_id "2"\ -pool3_addr_num 10

Related measurements: IP Pool Manager: Allocates - The number of addresses that have been allocated from all address pools. Releases - The number of allocated addresses that have been released back to the address pools. Allocate Fails Pool Empty - The number of times an address could not be allocated because all addresses in the specified pool have already been allocated. Allocate Fails Pool Not Found - The number of times an address could not be allocated because the pool identifier received in a request message does not match any of the defined address pools. Duplicate Releases - The number of times a request was received to release an address after it was released by a previous request.

lsh::l2tp_config

Name: lsh::l2tp_config

Purpose: Used to configure the L2TP protocol related arguments. It can be configured on following test case: GGSN NODE

Sub Functions

181

Synopsis: lsh::l2tp_config -mode {create|modify} -tc_hnd <test case handle> -l2tp_sut_name <ANY> -l2tp_node_intf_type {eth|atm} -l2tp_node_phy_intf <ANY> -l2tp_node_intf_ip_addr <IP> -l2tp_node_vpi <ANY> -l2tp_node_vci < NUMERIC > -l2tp_node_node_num <NUMERIC> -l2tp_node_mac_addr <MAC> -l2tp_node_next_hop <IP> -l2tp_node_out_bound_traffic_port <ANY> -l2tp_node_addr_err_inj <0-5> -l2tp_sut_port <0-65535> -tunnel_connect_rate <0-100000000> -tunnel_disconnect_rate <0-100000000> -recieve_win_size <4-2000> -retries <1-65535> -max_retry_interval <1-65535> -vpn_session_id <1-65535> -expected_host_name <1-65535> -tunnel_auth_en {true|false} -password <ALPHANUM> -require_auth_en {true|false} -send_challenge_size <1-255>

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - the first time to configure the GTP related arguments on the -tc_hnd modify - modify the parameters on the test case specified by the -tc_hnd. -tc_hnd Specifies the test case handle. This argument is mandatory. -l2tp_sut_name The name of L2TP SUT. -l2tp_node_intf_type The interface type of L2TP Node Default: eth -l2tp_node_phy_intf The interface of L2TP Node -l2tp_node_intf_ip_addr The IP address of the L2TP Node -l2tp_node_vpi The VPI of the L2TP Node, it can be configured when the interface type is atm. Dependency: l2tp_node_intf_type atm -l2tp_node_vci The VPI of the L2TP Node, it can be configured when the interface type is atm. Default: 0 Dependency: l2tp_node_intf_type atm -l2tp_node_node_num The number of the L2TP Node Default: 1 -l2tp_node_mac_addr The MAC address of the L2TP Node

Sub Functions

182

-l2tp_node_next_hop The next hop of the L2TP Node -l2tp_node_out_bound_traffic_port The outbound traffic port of the L2TP Node -l2tp_node_addr_err_inj The error inject of the L2TP Node. Default: 0 Range: 0-5 -l2tp_sut_port The port number used for the L2TP tunnel on the SUT. Default: 1701 Range: 0-65535 -tunnel_connect_rate The rate at which the test will attempt to establish L2TP tunnels. Default: 1.0 Range: 0-100000000 -tunnel_disconnect_rate The rate at which the test will attempt to tear down established L2TP tunnels. Default: 1.0 Range: 0-100000000 -recieve_win_size The Receive Window Size AVP used during L2TP tunnel establishment, indicating the number of control messages that a peer may send before waiting for an acknowledgment Default: 4 Range: 4-2000 -retries The retry times to send the message. Default: 3 Range: 1-65535 -max_retry_interval The interval of the retries. Default: 8 Range: 1-65535 -vpn_session_id The Assigned Session ID AVP that is used by L2TP peers to distinguish between L2TP sessions within a tunnel. Default: 1 Range: 1-65535 -expected_host_name The Host Name AVP used during L2TP tunnel establishment Default: 1 Range: 1-65535 -tunnel_auth_en Specifies whether to enable tunnel authentication during the L2TP tunnel establiment. Possible values: true, false Default: false -password Password that will be sent in response to a challenge from the peer when the tunnel authentication is enabled during the L2TP tunnel establiment. Dependency: tunnel_auth_en true -require_auth_en Specifies whether to send a challenge to the peer. Default: false Dependency: tunnel_auth_en true

Sub Functions

183

-send_challenge_size Specifies the number of bytes in the challenge Default: 4 Range: 1-255 Dependency: require_auth_en true


Examples: set ret [::lsh::l2tp_config \ -mode create\ -tc_hnd $tc\ -l2tp_sut_name $l2tp_sut\ -l2tp_node_phy_intf "eth2"\ -l2tp_node_intf_ip_addr $ts_eht2\ -l2tp_node_mac_addr $l2tp_mac\ -tunnel_auth_en true\ -password spirent\ -require_auth_en true\ -send_challenge_size 5] Return: {status 1}

lsh::ppp_config

Name: lsh::ppp_config

Purpose: Used to configure the PPP protocol related arguments. It can be configured on following test case: GGSN NODE

Synopsis: lsh::ppp_config -mode {create|modify} -tc_hnd <test case handle> -magic_num <0-4294967295> -net_ctrl_protocol {IPCP|IPV6CP} -intf_id <IPV6> -local_mtu <20-65535> -ignore_ipcp_req_en {0|1} -retries <0-10> -lcp_config_timer <0-65535> -max_lcp_config_req <0-65535> -max_ipcp_config_req <0-65535> -lcp_terminate_timer <0-65535> -max_lcp_terminate_retries <0-65535> -mobile_node_init_delay <0-6000> -ignore_lcp_req_en {0|1} -ignore_auth_msg_en {true|false} -always_fail_auth_en {true|false} -auth_optional_en {true|false} -valid_chap_challenges <1-16> -alternate_name <ALPHANUM> -respond_router_soclic_en {0|1} -unsoclic_router_advert_interval <0-65535> -unsoclic_router_advert_num <0-255> -advertise_ip_addr_en {true|false} -empty_ip_pool_en {true|false} -meintain_idle_connect_en {true|false}

Sub Functions

184

-auth_type {None|Any|PAP|CHAP|MSCHAPV2} -auth_proposal {None|PAP|CHAP|MSCHAPV2} -ppp_user_name <ALPHANUM> -ppp_password <ALPHANUM> -pap_retries <0-10> -pap_intervals <0-65535> -chap_retries <0-10> -chap_intervals <0-65535> -sync_mode {Async|Sync} -inactivity_timer_en {true|false} -inactivity_interval <0-65535> -accm_en {true|false} -accm_value <0-4294967295> -forced_equivalent_en {true|false} -err_inject {None|Bad_HDLC_checksum_for_all_data_packets |Bad_HDLC_checksum_for_all_control_packets} -inc_hdlc_header_en {0|1} -protocol_feild_compress_en {0|1} -addr_ctrl_feild_compress_en {0|1} -van_jacobson_compress_en {true|false} -max_slot <3-256> -vj_slot_id_compress {No_Compression|Force_Compression|Request_Compression} -primary_dns_en {true|false} -primary_dns <IP> -secondary_dns_en {true|false} -secondary_dns <IP> -primary_nbns_en {true|false} -primary_nbns <IP> -secondary_nbns_en {true|false} -secondary_nbns <IP> -ppp_tdf_to_para_en {true|false} -ppp_tdf_to_para <ANY>

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - the first time to configure the GTP related arguments on the -tc_hnd modify - modify the parameters on the test case specified by the -tc_hnd. -tc_hnd Specifies the test case handle. This argument is mandatory. -magic_num The magic number to use when establishing a PPP session Default: 654322 Range: 0-4294967295 -net_ctrl_protocol Specifies the PPP control protocol. Possible values: IPCP, IPV6CP Default: IPCP -intf_id A 64-bit starting Interface ID for the MNs Default: ::0:0:0:0 Dependency: net_ctrl_protocol IPV6CP -local_mtu The number of bytes at which fragmentation will take place at the PPP layer, This value includes all data payload bytes, the TCP header (if present), and the PPP header Default: 1500 Range: 20-65535 -ignore_ipcp_req_en Specifies whether to ignore IPCP Config Requests, when it is 1, the IPCP configuration requests that allow negotiation of IP parameters are ignored. When it is 0, the IPCP Configuration Options that allow

Sub Functions

185

negotiation of IP parameters are used. Possible values: 0, 1 Default: 0 Dependency: net_ctrl_protocol IPCP -retries The number of times the test will re-transmit (retry) a message after a timeout occur. Default: 3 Range: 0-10 -lcp_config_timer The number of milliseconds to wait for a response during LCP establish a link. Default: 5000 Range: 0-65535 -max_lcp_config_req The maximum number of LCP Configuration requests that will be sent during a LCP Configuration negotiation. If the maximum number of requests is reached Landslide will not send additional requests and will send a CDN message. Default: 5 Range: 0-65535 -max_ipcp_config_req The maximum number of IPCP Configuration requests that will be sent during a IPCP Configuration negotiation. If the maximum number of requests is reached Landslide will not send additional requests and will send a CDN message. Default: 5 Range: 0-65535 -lcp_terminate_timer The number of milliseconds to wait for a response during LCP terminate the link. Default: 5000 Range: 0-65535 -max_lcp_terminate_retries The maximum number of attempts made to terminate the link. Default: 5 Range: 0-65535 -mobile_node_init_delay The number of milliseconds that the MN will wait before initiating a PPP session. If a network element initiates PPP before the time has expired, the MN will respond; otherwise, the MN will initiate PPP when the timer expires. Enter 0 to disable the delay timer. Default: 0 Range: 0-6000 -ignore_lcp_req_en Specifies whether to ignore LCP Config Requests, when it is 1, the LCP configuration requests are ignored. When it is 0, the LCP Configuration Options are used. Possible values: 0, 1 Default: 0 -ignore_auth_msg_en Specifies whether to the PPP server will ignore the authentication messages from client. Possible values: true, false Default: false -always_fail_auth_en Specifies whether PPP server will fail authentication messages from the client Possible values: true, false Default: false

Sub Functions

186

-auth_optional_en Specifies whether to enable the Authentication Optional Default: false Dependency: auth_type Any|PAP|CHAP|MSCHAPV2 -valid_chap_challenges The challenge value for CHAP authentication. This indicates the number of past CHAP challenges that will be considered when the PPP server received the CHAP Authentication Response. Default: 1 Range: 1-16 Dependency: auth_type Any|CHAP|MSCHAPV2 -alternate_name Specifies the alternate user name. Dependency: auth_type Any|PAP|CHAP|MSCHAPV2 -respond_router_soclic_en Specifies whether to respond to router solicitation. Possible values: 0, 1 Default: 0 Dependency: net_ctrl_protocol IPV6CP -unsoclic_router_advert_interval Specifies the unsolicited router advertisement interval. Default: 2 Range: 0-65535 Dependency: net_ctrl_protocol IPV6CP -unsoclic_router_advert_num Specifies the number of unsolicited router advertisements. Default: 1 Range: 0-255 Dependency: net_ctrl_protocol IPV6CP -advertise_ip_addr_en Specifies whether the PPP server to send its IP address to the client during the IPCP negotiation procedure. Possible values: true, false Default: false -empty_ip_pool_en Specifies whether the PPP server to send its IP address to the client during the IPCP negotiation procedure. Default: false -meintain_idle_connect_en Specifies whether the PPP server to maintain connection during idle time. Default: false -auth_type Specifies the type of PPP authentication that will be used Possible values: None, Any, PAP, CHAP, MSCHAPV2 Default: None -auth_proposal Specifies the type of PPP authorization proposal that will be used Possible values: None, PAP, CHAP, MSCHAPV2 Default: PAP Dependency: auth_type Any -ppp_user_name Specifies the user name used in the authentication. Default: @domain Dependency: auth_type Any|PAP|CHAP|MSCHAPV2 -ppp_password The user password used in the authentication. Default: pword Dependency: auth_type Any|PAP|CHAP|MSCHAPV2 -pap_retries The number of times an authorization request message can be sent

Sub Functions

187

Default: 3 Range: 0-10 Dependency: auth_type Any|PAP -pap_intervals The amount of time, in milliseconds, that the test will wait for a response if a response is expected. When the time expires and the PAP Intervals has not been exceeded, the message is re-transmitted. Default: 1000 Range: 0-65535 Dependency: auth_type Any|PAP -chap_retries The number of times an authorization request message can be sent. Default: 3 Range: 0-10 Dependency: auth_type Any|CHAP|MSCHAPV2 -chap_intervals The amount of time, in milliseconds, that the test will wait for a response if a response is expected. When the time expires and the CHAP Intervals has not been exceeded, the message is re-transmitted. Default: 1000 Range: 0-65535 Dependency: auth_type Any|CHAP|MSCHAPV2 -sync_mode Specifies the Synchronization Mode for the PPP communication. Possible values: Async, Sync Default: Async -inactivity_timer_en Specifies whether to enable the inacvtivity timer. Possible values: true, false Default: false -inactivity_interval The number of seconds that an PPP connection can remain established without receiving any communication. When the defined value is reached, the PPP connection is torn down. Default: 0 Range: 0-65535 Dependency: inactivity_timer_en true -accm_en Specifies whether to enable ACCM negotiation with the PPP peer. Possible values: true, false Default: false Dependency: sync_mode Async -accm_value The ACCM value that the PPP peer will use. Default: 0 Range: 0-4294967295 Dependency: accm_en true -forced_equivalent_en Whether to require the PPP peer to negotiate using the ACCM value that is specified Possible values: true, false Default: false Dependency: accm_en true -err_inject Specifies the error injection at the PPP layer in either control or data packets. Default: None Dependency: sync_mode Async -inc_hdlc_header_en Default: 0

Sub Functions

188

Dependency: sync_mode Sync -protocol_feild_compress_en Specifies whether to enable sending packets with compressed protocol fields Possible values: 0, 1 Default: 0 -addr_ctrl_feild_compress_en Specifies whether to enable sending packets with compressed address and control fields Possible values: 0, 1 Default: 0 -van_jacobson_compress_en Specifies whether to enable Van Jacobson header compression in PPP packets when IPCP is used. Possible values: true, false Default: false Dependency: net_ctrl_protocol IPCP -max_slot The maximum slots. Default: 4 Range: 3-256 Dependency: van_jacobson_compress_en true -vj_slot_id_compress Specifies the Van Jacobson Slot ID Compression Possible values: No_Compression, Force_Compression, Request_Compression Default: No_Compression Dependency: van_jacobson_compress_en true -primary_dns_en Specifies whether to use the primary DNS. Possible values: true, false Default: false -primary_dns The address of the primary DNS. Dependency: primary_dns_en true -secondary_dns_en Specifies whether to use the secondary DNS. Possible values: true, false Default: false -secondary_dns The address of the secondary DNS. Dependency: secondary_dns_en true -primary_nbns_en Specifies whether to use the primary NBNS. Possible values: true, false Default: false -primary_nbns The address of the primary NBNS. Dependency: primary_nbns_en true -secondary_nbns_en Specifies whether to use the secondary NBNS. Possible values: true, false Default: false -secondary_nbns The address of the secondary NBNS. Dependency: secondary_nbns_en true -ppp_tdf_to_para_en Specifies whether to the PPP parameters defined in the Test Data File.

Sub Functions

189

Default: false -ppp_tdf_to_para The name of the Test Data File in which the PPP parameters is defined. Dependency: ppp_tdf_to_para_en true


Examples: set ret [::lsh::ppp_config \ -tc_hnd $tc\ -mode modify\ -magic_num 3333\ -auth_type PAP\ -pap_retries 5\ -primary_dns_en true\ -sync_mode Sync\ -ignore_lcp_req_en 0\ -ignore_ipcp_req_en 0\ -van_jacobson_compress_en true\ -vj_slot_id_compress Request_Compression] Return: status 1}

lsh::qos_update_config

Name: lsh::qos_update_config

Purpose: Used to configure the QoS update related arguments. It can be configured on following test case:

GGSN NODE

Synopsis: lsh::qos_update_config -mode {create|modify} -tc_hnd <test case handle> -cont_qos_update_en {true|false} -qos_update_delay_time <1-10000> -pdp_ip_addr_update_en {true|false} -pdp_update_ip <IP> -init_qos_type {summary|individual } -init_qos_relia_class <0-7> -init_qos_err_sdus <0-7> -init_qos_residual_ber <0-15> -init_qos_delay_class <0-7> -init_qos_guaranteed_rate_uplink <0-255> -init_qos_traffic_class <0-7> -init_qos_peak_thrpt <0-15> -init_qos_guaranteed_rate_downlink <0-255> -init_qos_max_sdu_size <0-255> -init_qos_mean_thrpt <0-31> -init_qos_max_rate_uplink <0-255> -init_qos_traffic_hand_pri <0-3> -init_qos_deliver_order <0-3> -init_qos_max_rate_downlink <0-255> -init_qos_sdu_error_ratio <0-15> -init_qos_trasfer_delay <0-63> -init_qos_allco_pri <0-255> -init_qos_precedence_class <0-7> -init_qos_src_stat_des_en {true|false}

Sub Functions

190

-init_qos_src_stat_des <0-15> -init_qos_sig_indicator <0-1> -init_qos_inc_bit_rate_downlink_ex_en {true|false} -init_qos_max_rate_downlink_ex <0-255> -init_qos_guaranteed_rate_downlink_ex <0-255> -init_qos_inc_bit_rate_uplink_ex_en {true|false} -init_qos_max_rate_uplink_ex <0-255> -init_qos_guaranteed_rate_uplink_ex <0-255> -update_qos_type {summary|individual } -update_qos_relia_class <0-7> -update_qos_err_sdus <0-7> -update_qos_residual_ber <0-15> -update_qos_delay_class <0-7> -update_qos_guaranteed_rate_uplink <0-255> -update_qos_traffic_class <0-7> -update_qos_peak_thrpt <0-15> -update_qos_guaranteed_rate_downlink <0-255> -update_qos_max_sdu_size <0-255> -update_qos_mean_thrpt <0-31> -update_qos_max_rate_uplink <0-255> -update_qos_traffic_hand_pri <0-3> -update_qos_deliver_order <0-3> -update_qos_max_rate_downlink <0-255> -update_qos_sdu_error_ratio <0-15> -update_qos_trasfer_delay <0-63> -update_qos_allco_pri <0-255> -update_qos_precedence_class <0-7> -update_qos_src_stat_des_en {true|false} -update_qos_src_stat_des <0-15> -update_qos_sig_indicator <0-1> -update_qos_inc_bit_rate_downlink_ex_en {true|false} -update_qos_max_rate_downlink_ex <0-255> -update_qos_guaranteed_rate_downlink_ex <0-255> -update_qos_inc_bit_rate_uplink_ex_en {true|false} -update_qos_max_rate_uplink_ex <0-255> -update_qos_guaranteed_rate_uplink_ex <0-255>

Arguments: -mode Specifies the action to perform. Possible values are create and modify. This argument is mandatory. The modes are described below: create - the first time to configure the GTP related arguments on the -tc_hnd modify - modify the parameters on the test case specified by the -tc_hnd. -tc_hnd Specifies the test case handle. This argument is mandatory. -cont_qos_update_en Specifies whether to enable the continuous QoS updates Possible values: true, false Default: false -qos_update_delay_time The delay time before the QoS update request is sent. if the continuous QoS update is enabled, it also means the interval between each QoS update request is sent Default: 1 Range: 1-10000 -pdp_ip_addr_update_en Specifies whether to enable the PDP context IP address update. Possible values: true, false Default: false -pdp_update_ip If the PDP context IP address update is enabled, specify the PDP context IP address. Dependency: pdp_ip_addr_update_en true

Sub Functions

191

-init_qos_type The type of the QoS. Possible values: summary - all PDP/bearer contexts use the same QoS profile. individual - define different QoS profiles for each contexts. Default: summary -init_qos_relia_class The reliability class. 0 - Subscribed reliability class 1- Unused (treated as 2) 2- Unacknowledged GTP; Acknowledged LLC and RLC, Protected Data 3- Unacknowledged GTP and LLC; Acknowledged RLC, Protected Data 4- Unacknowledged GTP, LLC and RLC, Protected Data 5- Unacknowledged GTP, LLC and RLC, Unprotected Data 6- Unused 7- Reserved Default: 1 Range: 0-7 Note: It can be one value or multiple values. If -init_qos_type is summary, it is one value; if -init_qos_type is individual, it can be more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_err_sdus Specifies whether SDUs detected as erroneous will be delivered or discarded 0- Subscribed delivery of erroneous SDUs 1- No detect 2- Erroneous SDUs are delivered 3- Erroneous SDUs are not delivered 4-7 - Reserved Default: 1 Range: 0-7 Note: It can be one value or more than one value. If the -init_qos_type is summary, it should be only one value, if -init_qos_type is individual, it can be a more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_residual_ber The undetected bit error ratio in the delivered SDUs. If error detection is not requested, this indicates the BER in the delivered SDUs. 0- Subscribed residual BER 1- 5 * 10 2- 1 * 10-2 3- 5 * 10-3 4- 4 * 10-3 5- 1 * 10-3 6- 1 * 10-4 7- 1 * 10-5 8- 1 * 10-6 9- 8 * 10-8 10- 15 - Reserved Default: 1 Range: 0-15 Note: It can be one value or more than one value. If the -init_qos_type is summary, it should be only one value, if -init_qos_type is individual, it can be a more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_delay_class The relative importance for the handling of all SDUs 0- Subscribed delay class

Sub Functions

192

1- Delay class 1 2- Delay class 2 3- Delay class 3 4- Delay class 4 (best effort) 5- Unused 6- Unused 7- Reserved Default: 1 Range: 0-7 Note: It can be one value or more than one. If -init_qos_type is set to summary, it should be only one value; if -init_qos_type is individual, it can be more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_guaranteed_rate_uplink The guaranteed uplink bit rate. 0- Subscribed bit rate 1 -63 - Maximum bit rate in 1 kbps increments (1 - 63 kbps) 64 - 127 - Maximum bit rate in 8 kbps increments (64 - 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)). 128 - 254 - Maximum bit rate in 64 kbps increments (576 - 8,640 kbps) calculated as (576 kbps + (value - 128 kbps) * 64 kbps)). 255 - 0 kbps Default: 1 Range: 0-255 Note: It can be one value or more than one value. If the -init_qos_type is summary, it should be only one value, if -init_qos_type is individual, it can be a more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_traffic_class The traffic class. 0 - Subscribed traffic class 1 - Conversational class 2 - Streaming class 3 - Interactive class 4 - Background class 5-7 - Reserved Default: 1 Range: 0-7 Note: It can be one value or more than one value. If the -init_qos_type is summary, it should be only one value, if -init_qos_type is individual, it can be a more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_peak_thrpt The maximum throughput allowed for a PDP context. 0- Subscribed peak throughput 1 - Up to 1,000 octets/sec 2- Up to 2,000 octets/sec 3- Up to 4,000 octets/sec 4- Up to 8,000 octets/sec 5- Up to 16,000 octets/sec 6- Up to 32,000 octets/sec 7- Up to 64,000 octets/sec 8- Up to 128,000 octets/sec 9- Up to 256,000 octets/sec 10 - 14 - Unused 15- Reserved Default: 1 Range: 0-15 Note: It can be one value or more than one value. If the -init_qos_type is

Sub Functions

193

summary, it should be only one value, if -init_qos_type is individual, it can be a more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_guaranteed_rate_downlink The guaranteed uplink bit rate. 0- Subscribed bit rate 1 -63 - Maximum bit rate in 1 kbps increments (1 - 63 kbps) 64 - 127 - Maximum bit rate in 8 kbps increments (64 - 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)). 128 - 254 - Maximum bit rate in 64 kbps increments (576 - 8,640 kbps) calculated as (576 kbps + (value - 128 kbps) * 64 kbps)). 255 - 0 kbps Default: 1 Range: 0-255 Note: It can be one value or more than one value. If the -init_qos_type is summary, it should be only one value, if -init_qos_type is individual, it can be a more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_max_sdu_size The maximum SDU size for which the network will satisfy the negotiated QOS. 0- Subscribed maximum SDU size 1- 150 - Maximum SDU size in 10-octet increments (10 - 1500 octets) 151- 1502 octets 152- 1510 octets 153- 1520 octets 154+ - Reserved Range: 0-255 Dependency: init_qos_type individual Note: It can be one value or more than one value. If the -init_qos_type is summary, it should be only one value, if -init_qos_type is individual, it can be a more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_mean_thrpt The average throughput allowed for a PDP context. 0- Subscribed mean throughput 1- Up to 100 octets/sec 2- Up to 200 octets/sec 3- Up to 500 octets/sec 4- Up to 1,000 octets/sec 5- Up to 2,000 octets/sec 6- Up to 5,000 octets/sec 7- Up to 10,000 octets/sec 8- Up to 20,000 octets/sec 9- Up to 50,000 octets/sec 10- Up to 100,000 octets/sec 11- Up to 200,000 octets/sec 12- Up to 500,000 octets/sec 13- Up to 1,000,000 octets/sec 14- Up to 2,000,000 octets/sec 15- Up to 5,000,000 octets/sec 16- Up to 10,000,000 octets/sec 17- Up to 20,000,000 octets/sec 18- Up to 50,000,000 octets/sec 19 - 29 - Unused 30- Reserved 31- Best effort Default: 1 Range: 0-31 Note:

Sub Functions

194

It can be one value or more than one value. If the -init_qos_type is summary, it should be only one value, if -init_qos_type is individual, it can be a more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_max_rate_uplink The maximum uplink bit rate. 0- Subscribed bit rate 1- 63 - Maximum bit rate in 1 kbps increments (1 - 63 kbps) 64- 127 - Maximum bit rate in 8 kbps increments (64 - 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)). 128- 254 - Maximum bit rate in 64 kbps increments (576 - 8,640 kbps) calculated as (576 kbps + ((value - 128 kbps) * 64 kbps)). 255 - 0 kbps Default: 1 Range: 0-255 Note: It can be one value or more than one value. If the -init_qos_type is summary, it should be only one value, if -init_qos_type is individual, it can be a more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_traffic_hand_pri The relative importance for the handling of all SDUs 0- Subscribed traffic handling priority 1- Priority level 1 2- Priority level 2 3- Priority level 3 Default: 1 Range: 0-3 Note: It can be one value or more than one value. If the -init_qos_type is summary, it should be only one value, if -init_qos_type is individual, it can be a more than one, the count depend on the -prim_pdp_contexts_num and -sec_pdp_contexts_num in lsh::ggsn_node_config function. if -prim_pdp_contexts_num is 2, and -sec_pdp_contexts_num is 3, then the count should be 2+2*3 = 8. -init_qos_deliver_order Indicates whether in-sequence SDU delivery is used 0- Subscribed delivery order 1- With delivery order 2- Without delivery order 3- Reserved Default: 1 Range: 0-3 -init_qos_max_rate_downlink The max downlink bit rate. 0- Subscribed bit rate 1- 63 - Maximum bit rate in 1 kbps increments (1 - 63 kbps) 64- 127 - Maximum bit rate in 8 kbps increments (64 - 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)). 128- 254 - Maximum bit rate in 64 kbps increments (576 - 8,640 kbps) calculated as (576 kbps + ((value - 128 kbps) * 64 kbps)). 255 - 0 kbps Default: 1 Range: 0-255 -init_qos_sdu_error_ratio The fraction of SDUs lost or detected as erroneous 0- Subscribed SDU error ratio 1- 1 * 10-2 2- 7 * 10-3 3- 1 * 10-3 4- 1 * 10-4 5- 1 * 10-5

Sub Functions

195

6- 1 * 10-6 7- 1 * 10-1 8 - 15- Reserve Default: 1 Range: 0-15 -init_qos_trasfer_delay Indicates the maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a bearer service, where delay for an SDU is defined as the time from a request to transfer an SDU to its delivery. 0- Subscribed transfer delay 1- 15- Transfer delay in 10ms increments (10ms - 150ms) 16- 31-Transfer delay in 50ms increments (200ms - 950ms) calculated as (200ms + (value - 16) * 50ms)). 32- 62- Transfer delay in 100ms increments (1,000ms - 4,000ms) calculated as (1000ms + (value - 32) * 100ms)). 63- Reserved Default: 1 Range: 0-63 -init_qos_allco_pri The relative importance of the GPRS bearer compared to other GPRS bearers for allocation and retention. The network elements can use Allocation/Retention Priority to prioritize bearers when performing admission control Default: 1 Range: 0-255 -init_qos_precedence_class The relative importance of the GPRS bearer compared to other GPRS bearers for allocation and retention. The network elements can use Allocation/Retention Priority to prioritize bearers when performing admission control 0- Subscribed precedence 1- High priority 2- Normal priority 3- Low priority 4- Unused 5- Unused 6- Unused 7- Reserved Default: 1 Range: 0-7 -init_qos_src_stat_des_en Specifies whether to include octets 14-16 in the QOS Information Element Possible values: true, false Default: false -init_qos_src_stat_des Source Statistics Descriptor, indicates the source type Default: 0 Range: 0-15 Dependency: init_qos_src_stat_des_en true -init_qos_sig_indicator Signalling Indication, indicates whether the PDP context is optimized for signalling traffic. Default: 0 Range: 0-1 Dependency: init_qos_src_stat_des_en true -init_qos_inc_bit_rate_downlink_ex_en Specifies whether to include octets 15 and 16 when a downlink rate larger than 8,640 kbps should be requested. The bit rates are calculated in 100 kbps increments (8,700 - 256,000 kbps) as (8600 kbps + (value * 100 kbps)). Possible values: true, false Default: false

Sub Functions

196

-init_qos_max_rate_downlink_ex If it is set to anything other than 0, the extended downlink max bit rate will completely override the downlink max bit rate Default: 0 Range: 0-255 Dependency: init_qos_inc_bit_rate_downlink_ex_en true -init_qos_guaranteed_rate_downlink_ex If it is set to anything other than 0, the extended downlink guaranteed Bit Rate will completely override the downlink guaranteed Bit rate Default: 0 Range: 0-255 Dependency: init_qos_inc_bit_rate_downlink_ex_en true -init_qos_inc_bit_rate_uplink_ex_en Specifies whether to include octets 15 and 16 when a uplink rate larger than 8,640 kbps should be requested. The bit rates are calculated in 100 kbps increments (8,700 - 256,000 kbps) as (8600 kbps + (value * 100 kbps)). Possible values: true, false Default: false -init_qos_max_rate_uplink_ex If it is set to anything other than 0, the extended uplink max bit rate will completely override the uplink max bit rate Default: 0 Range: 0-255 Dependency: init_qos_inc_bit_rate_uplink_ex_en true -init_qos_guaranteed_rate_uplink_ex If it is set to anything other than 0, the extended uplink guaranteed Bit Rate will completely override the uplink guaranteed Bit rate Default: 0 Range: 0-255 Dependency: init_qos_inc_bit_rate_uplink_ex_en true -update_qos_type The type of the QoS. Possible values: summary - all PDP/bearer contexts use the same QoS profile. Individual - define different QoS profiles for each contexts. Default: summary -update_qos_relia_class The reliability class. 0 - Subscribed reliability class 1- Unused (treated as 2) 2- Unacknowledged GTP; Acknowledged LLC and RLC, Protected Data 3- Unacknowledged GTP and LLC; Acknowledged RLC, Protected Data 4- Unacknowledged GTP, LLC and RLC, Protected Data 5- Unacknowledged GTP, LLC and RLC, Unprotected Data 6- Unused 7- Reserved Default: 1 Range: 0-7 -update_qos_err_sdus Specifies whether SDUs detected as erroneous will be delivered or discarded 0- Subscribed delivery of erroneous SDUs 1- No detect 2- Erroneous SDUs are delivered 3- Erroneous SDUs are not delivered 4-7 - Reserved Default: 1 Range: 0-7 -update_qos_residual_ber The undetected bit error ratio in the delivered SDUs. If error detection is not requested, this indicates the BER in the delivered SDUs.

Sub Functions

197

0- Subscribed residual BER 1- 5 * 10 2- 1 * 10-2 3- 5 * 10-3 4- 4 * 10-3 5- 1 * 10-3 6- 1 * 10-4 7- 1 * 10-5 8- 1 * 10-6 9- 8 * 10-8 10- 15 - Reserved Default: 1 Range: 0-15 -update_qos_delay_class The relative importance for the handling of all SDUs 8- Subscribed delay class 9- Delay class 1 10- Delay class 2 11- Delay class 3 12- Delay class 4 (best effort) 13- Unused 14- Unused 15- Reserved Default: 1 Range: 0-7 -update_qos_guaranteed_rate_uplink The guaranteed uplink bit rate. 0- Subscribed bit rate 1 -63 - Maximum bit rate in 1 kbps increments (1 - 63 kbps) 64 - 127 - Maximum bit rate in 8 kbps increments (64 - 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)). 128 - 254 - Maximum bit rate in 64 kbps increments (576 - 8,640 kbps) calculated as (576 kbps + (value - 128 kbps) * 64 kbps)). 255 - 0 kbps Default: 1 Range: 0-255 -update_qos_traffic_class The traffic class. 0 - Subscribed traffic class 1 - Conversational class 2 - Streaming class 3 - Interactive class 4 - Background class 5-7 - Reserved Default: 1 Range: 0-7 -update_qos_peak_thrpt The maximum throughput allowed for a PDP context. 0- Subscribed peak throughput 1 - Up to 1,000 octets/sec 2- Up to 2,000 octets/sec 3- Up to 4,000 octets/sec 4- Up to 8,000 octets/sec 5- Up to 16,000 octets/sec 6- Up to 32,000 octets/sec 7- Up to 64,000 octets/sec 8- Up to 128,000 octets/sec 9- Up to 256,000 octets/sec 10 - 14 - Unused 15- Reserved Default: 1 Range: 0-15 -update_qos_guaranteed_rate_downlink The guaranteed uplink bit rate. 0- Subscribed bit rate 1 -63 - Maximum bit rate in 1 kbps increments (1 - 63 kbps)

Sub Functions

198

64 - 127 - Maximum bit rate in 8 kbps increments (64 - 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)). 128 - 254 - Maximum bit rate in 64 kbps increments (576 - 8,640 kbps) calculated as (576 kbps + (value - 128 kbps) * 64 kbps)). 255 - 0 kbps Default: 1 Range: 0-255 -update_qos_max_sdu_size The maximum SDU size for which the network will satisfy the negotiated QOS. 0- Subscribed maximum SDU size 1- 150 - Maximum SDU size in 10-octet increments (10 - 1500 octets) 151- 1502 octets 152- 1510 octets 153- 1520 octets 154+ - Reserved Range: 0-255 Dependency: init_qos_type individual -update_qos_mean_thrpt The average throughput allowed for a PDP context. 0- Subscribed mean throughput 1- Up to 100 octets/sec 2- Up to 200 octets/sec 3- Up to 500 octets/sec 4- Up to 1,000 octets/sec 5- Up to 2,000 octets/sec 6- Up to 5,000 octets/sec 7- Up to 10,000 octets/sec 8- Up to 20,000 octets/sec 9- Up to 50,000 octets/sec 10- Up to 100,000 octets/sec 11- Up to 200,000 octets/sec 12- Up to 500,000 octets/sec 13- Up to 1,000,000 octets/sec 14- Up to 2,000,000 octets/sec 15- Up to 5,000,000 octets/sec 16- Up to 10,000,000 octets/sec 17- Up to 20,000,000 octets/sec 18- Up to 50,000,000 octets/sec 19 - 29 - Unused 30- Reserved 31- Best effort Default: 1 Range: 0-31 -update_qos_max_rate_uplink The max uplink bit rate. 0- Subscribed bit rate 1- 63 - Maximum bit rate in 1 kbps increments (1 - 63 kbps) 64- 127 - Maximum bit rate in 8 kbps increments (64 - 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)). 128- 254 - Maximum bit rate in 64 kbps increments (576 - 8,640 kbps) calculated as (576 kbps + ((value - 128 kbps) * 64 kbps)). 255 - 0 kbps Default: 1 Range: 0-255 -update_qos_traffic_hand_pri The relative importance for the handling of all SDUs 0- Subscribed traffic handling priority 1- Priority level 1 2- Priority level 2 3- Priority level 3 Default: 1 Range: 0-3 -update_qos_deliver_order Determines whether in-sequence SDU delivery is used 0- Subscribed delivery order

Sub Functions

199

1- With delivery order 2- Without delivery order 3- Reserved Default: 1 Range: 0-3 -update_qos_max_rate_downlink The maximum downlink bit rate. 0- Subscribed bit rate 1- 63 - Maximum bit rate in 1 kbps increments (1 - 63 kbps) 64- 127 - Maximum bit rate in 8 kbps increments (64 - 568 kbps) calculated as (64 kbps + ( (value - 64 kbps) * 8 kbps)). 128- 254 - Maximum bit rate in 64 kbps increments (576 - 8,640 kbps) calculated as (576 kbps + ((value - 128 kbps) * 64 kbps)). 255 - 0 kbps Default: 1 Range: 0-255 -update_qos_sdu_error_ratio The fraction of SDUs lost or detected as erroneous 0- Subscribed SDU error ratio 1- 1 * 10-2 2- 7 * 10-3 3- 1 * 10-3 4- 1 * 10-4 5- 1 * 10-5 6- 1 * 10-6 7- 1 * 10-1 8 - 15- Reserved Default: 1 Range: 0-15 -update_qos_trasfer_delay Indicates the maximum delay for 95th percentile of the distribution of delay for all delivered SDUs during the lifetime of a bearer service, where delay for an SDU is defined as the time from a request to transfer an SDU to its delivery. 0- Subscribed transfer delay 1- 15- Transfer delay in 10ms increments (10ms - 150ms) 16- 31-Transfer delay in 50ms increments (200ms - 950ms) calculated as (200ms + (value - 16) * 50ms)). 32- 62- Transfer delay in 100ms increments (1,000ms - 4,000ms) calculated as (1000ms + (value - 32) * 100ms)). 63- Reserved Default: 1 Range: 0-63 -update_qos_allco_pri The relative importance of the GPRS bearer compared to other GPRS bearers for allocation and retention. The network elements can use Allocation/Retention Priority to prioritize bearers when performing admission control Default: 1 Range: 0-255 -update_qos_precedence_class The relative importance of the GPRS bearer compared to other GPRS bearers for allocation and retention. The network elements can use Allocation/Retention Priority to prioritize bearers when performing admission control 0- Subscribed precedence 1- High priority 2- Normal priority 3- Low priority 4- Unused 5- Unused 6- Unused 7- Reserved Default: 1 Range: 0-7 -update_qos_src_stat_des_en

Sub Functions

200

Specifies whether to include octets 14-16 in the QOS Information Element Possible values: true, false Default: false -update_qos_src_stat_des Source Statistics Descriptor, indicates the source type Default: 0 Range: 0-15 Dependency: update_qos_src_stat_des_en true -update_qos_sig_indicator Signalling Indication, indicates whether the PDP context is optimized for signalling traffic. Default: 0 Range: 0-1 Dependency: update_qos_src_stat_des_en true -update_qos_inc_bit_rate_downlink_ex_en Specifies whether to include octets 15 and 16 when a downlink rate larger than 8,640 kbps should be requested. The bit rates are calculated in 100 kbps increments (8,700 - 256,000 kbps) as (8600 kbps + (value * 100 kbps)). Possible values: true, false Default: false -update_qos_max_rate_downlink_ex If it is set to anything other than 0, the extended downlink max bit rate will completely override the downlink max bit rate Default: 0 Range: 0-255 Dependency: update_qos_inc_bit_rate_downlink_ex_en true -update_qos_guaranteed_rate_downlink_ex If it is set to anything other than 0, the extended downlink guaranteed Bit Rate will completely override the downlink guaranteed Bit rate Default: 0 Range: 0-255 Dependency: update_qos_inc_bit_rate_downlink_ex_en true -update_qos_inc_bit_rate_uplink_ex_en Specifies whether to include octets 15 and 16 when a uplink rate larger than 8,640 kbps should be requested. The bit rates are calculated in 100 kbps increments (8,700 - 256,000 kbps) as (8600 kbps + (value * 100 kbps)). Possible values: true, false Default: false -update_qos_max_rate_uplink_ex If it is set to anything other than 0, the extended uplink max bit rate will completely override the uplink max bit rate Default: 0 Range: 0-255 Dependency: update_qos_inc_bit_rate_uplink_ex_en true -update_qos_guaranteed_rate_uplink_ex If it is set to anything other than 0, the extended uplink guaranteed Bit Rate will completely override the uplink guaranteed Bit rate Default: 0 Range: 0-255 Dependency: update_qos_inc_bit_rate_uplink_ex_en true


Examples:

set ret [::lsh::qos_update_config \ -mode create\ -tc_hnd $tc\

Sub Functions

201

-cont_qos_update_en true\ -init_qos_type individual\ -init_qos_relia_class "0 1 3"\ -init_qos_src_stat_des_en "true true false"\ -init_qos_inc_bit_rate_downlink_ex_en "true false true"\ -update_qos_src_stat_des_en true\ -update_qos_inc_bit_rate_downlink_ex_en true\ -update_qos_inc_bit_rate_uplink_ex_en true]

Return {status 1}

Function Index

lsh::aaa_radius_client_config................................................................................................................................................................................127lsh:: aaa_server_node_config................................................................................................................................................................................ 52lsh::abort_test......................................................................................................................................................................................................... 19lsh::automation_config............................................................................................................................................................................................ 24lsh::automation_step_buidler.................................................................................................................................................................................. 26lsh::capture............................................................................................................................................................................................................. 20lsh::connect...............................................................................................................................................................................................................6lsh::criterion_config................................................................................................................................................................................................... 7lsh::dhcp_client_config..........................................................................................................................................................................................141lsh::dhcp_server_node_config................................................................................................................................................................................ 89lsh::dmf_config........................................................................................................................................................................................................28lsh::dmf_control_config........................................................................................................................................................................................... 45lsh::ger_tac_report.................................................................................................................................................................................................. 21lsh::get_handle........................................................................................................................................................................................................49lsh::get_results........................................................................................................................................................................................................19lsh::get_session_status...........................................................................................................................................................................................25lsh::ggsn_node_config............................................................................................................................................................................................ 94lsh::gtp_config.......................................................................................................................................................................................................144lsh::gtp'_config...................................................................................................................................................................................................... 146lsh::ip_app_node_config....................................................................................................................................................................................... 101lsh::ip_pools_config.............................................................................................................................................................................................. 153lsh::l2tp_config...................................................................................................................................................................................................... 180lsh::log_config......................................................................................................................................................................................................... 23lsh::ppp_config......................................................................................................................................................................................................183lsh::qos_update_config......................................................................................................................................................................................... 189lsh::report_options_config.......................................................................................................................................................................................14lsh::reserve_ports................................................................................................................................................................................................... 27lsh::run_test............................................................................................................................................................................................................ 18lsh::save..................................................................................................................................................................................................................50lsh::stop_test...........................................................................................................................................................................................................18lsh::sut_config......................................................................................................................................................................................................... 22lsh::test_case_config.............................................................................................................................................................................................. 13lsh::test_control.......................................................................................................................................................................................................17lsh::test_session_config..........................................................................................................................................................................................12lsh::test_session_create......................................................................................................................................................................................... 11lsh::validate............................................................................................................................................................................................................. 17lsh::wifi_offload_gateway_nodal_config................................................................................................................................................................106

Date post:	04-Apr-2018
Category:	Documents
Upload:	truonganh
View:	253 times
Download:	2 times

HLAPI Command Reference - Spirent · HLAPI Command Reference ... The Knowledge Base gives you...

Documents