spirent.com

Finding Avalanche Versions From Project Files

By Arnaud Castaner On April 28, 2011
Networks
No tags assigned.

If you’re a big Avalanche user, you probably one day or another had an old test that you needed to import in a recent version of the Avalanche Commander. To optimize the data structure and therefore improve the overall performance of the tool, sometimes the XML structure gets updated. This doesn’t happen between every version but when it happens there is a chance that these are not backwards compatible.

There is one caveat: any given version will only know about its own XML data structure (obviously), but also the previous XML data structure. So if you are more than one XML structure behind in the project you are attempting to import, the Commander will complain that it can’t import it – because it doesn’t understand the structure. Installing a previous version usually fixes this, and our Support Services have always been helpful in converting older tests to current XML structure.

But did you know you could find out, on your own, the version the project was created with? It’s a little bit of an advanced topic, but here goes.

You need to get the project in its “uncompressed” form (i.e., not in a SPF file). Note that SPF files are ZIP in a ZIP. So simply unzip the SPF twice, and you’ll see the usual XML files. If it’s not in a SPF, the default location for these files is:

  • Windows 7: C:\Users\\AppData\Roaming\Avalanche\ 
  • Windows XP: C:\Document and Settings\Application Data\Avalanche\ 
  • Now browse to the “tests” directory. This directory contains the list of tests of the project. Simply open one of them with a XML-aware text editor such as Notepad++. You should see this:

Finding Avalanche versions from project files

In the first node (“TestSpec”) you will see a key named “Version”. The value of that key (20 in the example above) is the information you are looking for.

“But 20 isn’t an Avalanche version!” you say. And that would be correct. You need a table to convert that internal version number to match it to a General Availability (GA) release. And here’s such a table:

AV4_00_XML_VERSION = "21";
AV3_60_XML_VERSION = "20";
AV3_50_XML_VERSION = "19";
AV3_40_XML_VERSION = "18";
AV3_30_XML_VERSION = "17";
AV3_10_XML_VERSION = "16";
AV2_31_XML_VERSION = "15";
AV2_30_XML_VERSION = "14";
AV2_20_XML_VERSION = "13";
AV2_16_XML_VERSION = "12";
AV7_8_XML_VERSION = "11";
P2_7_7_XML_VERSION = "10";
AV7_5_XML_VERSION = "9";
AV7_0_XML_VERSION = "8";

With this, you can now browse to any project you have and figure out which version was used to create the test you’re looking at.

 
comments powered by Disqus
× Spirent.com uses cookies to enhance and streamline your experience. By continuing to browse our site, you are agreeing to the use of cookies.