question

ChrisB avatar image
ChrisB asked srujan.sama answered

Closing IxLoad session crashes ports

Closing IxLoad session crashes ports. According to Ixia, this is because iTest is not doing an unconfigure before releasing the session. Failing to do this leaves the ports in a hosed ownership state. If you try closing the IxLoad GUI without unconfiguring you'll get a bunch of warnings regarding this.

 

Two questions:

1. Is there an API call for doing this, which I can call using IxLoad.eval before closing the session?

2. When can we get this fixed in iTest? This is happening on 3.2 - any chance it's already fixed in 3.3? :-)

 

Regards,

chris

iTesttraffic generation
10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

3 Answers

·
AlexanderK avatar image
AlexanderK answered AlexanderK posted
I can not find IxLoad tcl API to release ports by invoking command.
Actually this should be handled by each IxLoad test itself.
Each test contains boolean properties like:
1) enableForceOwnerShip - If true , at the beginning of the test, any ports that are selected for the test but

owned by another user are rebooted and their previous ownership cleared. This

parameter corresponds to the GUI option “Forcefully Take Ownership.” (Default

= false).

 
2) enableResetPorts - If true , IxLoad reboots the ports before downloading the test configuration to

them. To ensure the integrity of your testing, it is always safest to reboot the ports

before running a test. However, rebooting the ports does increase the amount of

time required to prepare the ports for a test.

 

3) enableReleaseConfigAfterRun -If true, purges the test configuration from the ports after a test completes, releases

ownership of them, and the ports will no longer respond to ARPs and PINGs

from the DUT. (Default = false).

 

As I understand we are talking about option 3).

iTest do not change any of this properties, so all these properties should be set by test owner in IxLoad GUI.

10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

srujan.sama avatar image
srujan.sama answered

this is still an observed issue in 2020, IxTest still has this issue and setting enableReleaseConfigAfterRun parameter helped.

10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

KumarS avatar image
KumarS answered KumarS posted
Please file a bug for this. We may be able to incorporate a fix in next bug fix release for 3.3.
1 comment
10 |950
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ChrisB avatar image ChrisB commented ·

Logged - 12708

 

Please let me know if there is a workaround using an IxLoad API call in the meantime.

 

Regards,

chris

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.