Printer FriendlyEmail Article Link

Spirent TestCenter: 5.01 - Conformance - IUT AUTOMATION not working using SSH instead of telnet

Symptoms

Using Conformance version 5.01 IUT AUTOMATION is not working when using SSH instead of telnet, however it looks like this same test using SSH on 4.69 works.
Usually we use Conformance IUT AUTOMATION with telnet, however this time the customer uses ssh for his tests.

However when trying iut automation using SSH, CTS application could show some of the following error messages:
 
  1. KNI15815 - Spirent TestCenter Conformance Application - CTS 5.01 IUTAutomation not working.
    • Tcl Evaluate () Failed, couldn't load library "C:/Program Files (x86)/Spirent Communications/Spirent_TestCenter_5.01/Conformance Application/cts_tcl/expect/expect543.dll": This library or a dependent library could not be found in library path while executing "load [file join $::exp::library $::exp::dll]"
 
  1. ​Tcl Evaluate() Failed send: spawn id exp5 not open while executing "exp_send -h "$input/r/r"" (procedure "telnetinteract" line 11) invoked from within "telnetInteract $cmdList" (procedure "::stc::cts::ipv6::TestC2" line 22) invoked from within...
 
  1. ​Tcl Evaluate() Failed. The request is not supported. wile executing "exp_spawn ssh.exe spirent@IUTIP" (procedure "ConnectToIut line 8) invoked from within "ConnectToIut $loginPrompt" (procedure "::stc::cts::ipv6::TestC2" line 19) invoked from within...
 
  1. CTS: Synch Iut Configuration 2 failed with error: Faile dto synchronize with Iut
 
Environment
 
  • Spirent TestCenter Conformance Application
  • CTS
  • Conformance
  • CTS 4.69
  • CTS 5.01
  • Telnet
  • SSH
  • IUT AUTOMATION
Explanation/Resolution

The following CR has been raised to have this investigated:
  • CR-01409572 
  • JIRA: CIPCD-15603
  • Date/Time Opened : 10/14/2019
  • Date/Time Closed: 6/16/2020

Explanation:
 
  • Based on the investigation so far from our dev team, the root cause for the original issue (CTS 4.69 automation working with SSH but NOT working on 5.01) is as follows:
  1. New CTS versions have upgraded TCL libraries and the code base of 4.69 and 5.01 are different, we have the hypothesis that some of those changes brought the incompatibility on your environment. 

Resolution

 
From all of our testing so far, we have found 2 possible solutions for this:
  1. Replacing the complete cts_tcl folder with that from 4.69 (or the version that is working) should help to make this work. Steps are as follows:
    1.  Please backup the “cts_tcl” folder from    C:\Program Files (x86)\Spirent Communications\Spirent TestCenter 5.01\Conformance Application\      (The application version should be the version you want to make it work, in this case we are using 5.01 as an example) and move that folder to another location you prefer (maybe the desktop), just in case.
    2. Copy the “cts_tcl” folder from    C:\Program Files (x86)\Spirent Communications\Spirent TestCenter 4.69 \Conformance Application    to      C:\Program Files (x86)\Spirent Communications\Spirent TestCenter 5.01\Conformance Application.
 
  1.  On Windows 10 system all versions are working well. We tested multiple versions like 4.69, 4.89, 4.90, 5.01, 5.02, 9.90. using same customer's tcl script, and we  could successfully get the DUT configured well as expected. So suggestion is to upgrade to windows 10
    • Our windows 10 tests were done using Cygwin 32 bits
 
 
Root Cause
 
  • New CTS versions have upgraded TCL libraries and the code base of 4.69 and 5.01 are different, we have the hypothesis that some of those changes brought the incompatibility on your environment. 
Attachments
Attachment
Attachment Description
v4.69 cts_tcl folder


Product : Conformance,Conformance Test,Spirent TestCenter