Unable to Open Avalanche Session

Question

question

JeffJ asked Sep 20, '11 JeffJ posted Sep 20, '11

Unable to Open Avalanche Session

I'm creating an Avalanche session for Avalanche 3.70 in iTest 4.1.3. I have check the box for using the Avalanche TCL Test and provided the directory path for the test. I've also added the path to the TCLAPI for Avalanche (file:/C:/Program%20Files%20(x86)/Spirent%20Communications/Spirent%20TestCenter%203.70/Layer%204-7%20Application/TclAPI/). For the license, I've checked the box and added the path to the license file (file:/C:/Program%20Files%20(x86)/Spirent%20Communications/Spirent%20TestCenter%203.60/Layer%204-7%20Application/license/License_R11191044.xml).

When I save and start the session, I see iTest "Opening..." the session but there is no output on the console view after showing the session profile. I would expect to see the TCL information but that is not coming up. After a couple of minutes, I abort the session by clicking on the X on the session tab but iTest continues to display "Opening..." in the status at the bottom right of the window.

Any clues as to what's happening?

iTest traffic generation

10 |950

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

Answer 1 · 2011-09-21T22:38:26Z

akazantsev answered Sep 21, '11 akazantsev posted Sep 21, '11

Response from Jeff:

Team,

I wanted to let you know I did get the test running in Avalanche via iTest. The issue came down to patience and a reboot of their PC.

I abandoned iTest to see if the test.tcl would even run. It appeared to hang so I regenerated the test. This failed with an error that it couldn’t get the hardware information. Thinking something was hung, I rebooted their machine. When it came back up, I regenerated the TCL version of the test. The TCL generation worked.

I then started up TCL and ran the test there. After more than 5 minutes, the test kicked off and ran successfully. I then typed in the TCL commands by hand and found that the “package require SPI_AV” was what was taking so long. Not sure what it was doing but it was taking it’s sweet time!

Once I understood the timing, I used iTest to run the test. iTest took 7 minutes to open the session and 6 minutes to start the test. One question I have is what do we do when we open the session? Do we load the environment? I’m not sure why it took so long to open the session.

I’m not sure if this is key information but the host system was a new HP 64-bit Laptop running Windows 7 Professional. I’m going to download the Avalanche 3.70 when I get back to my office to test on my host (64-bit Windows 7) to see if I can duplicate the issue.

10 |950

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

question