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
Answer by Alexander Kazantsev · Dec 05, 2008 at 02:40 AM
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 tothem. 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.
Answer by KumarS · Dec 05, 2008 at 12:14 AM
Logged - 12708
Please let me know if there is a workaround using an IxLoad API call in the meantime.
Regards,
chris
Copyright 2008- Spirent Communications, all rights reserved. Terms and Conditions.