Spirent TestCenter: Chassis and Ports goes offline after running SNTtc scripts.


Doc ID    SOL14278
Version:    1.0
Status:    Published
Published date:    03/20/2020
 

Objective/Summary

Chassis and Ports are going offline and have network connection issues, when the customer is using SNTtc scripts. This article explains the reason and possible fix for it.

Environment/Versions

  • Spirent TestCenter Chassis N11U - Probably any version, confirmed 4.66
  • SNTtc -4.66

Procedure

The main issue was that the script that was being used, did not had the "clear config" command to release the ports after /  before the rest was run for the first time.
Explanation:

While the ports are in reserved state and the config file is run for the second time(The config file has configs to create port and reserve them), it ends up creating some offline ports and this error is seen.
When "clear config” command is added to the config file, the ports are being released and available to re-run the script multiple times.
 

Notes


Image showing how the error appeared.




Errors found in the logs

***FATAL***
            20/02/29 09:16:14.087 FATAL 3668966208 - user.rpc             - Lost connection to port //10.1.1.250/1/3.  Please check connection and network condition.
            20/02/29 09:16:15.143 FATAL 2241801024 - user.rpc             - Lost connection to 10.1.1.250 test module 1 port group 3.  Please check connection and network condition

 

Find Answers

Specified Languages
English
中文

Please Sign In

Username
Password

Did you forget your password?
Click here for assistance

New user? Start here.