L1 functionality isn’t working (2022.1 and above)
Description
If you upgraded to CloudShell 2022.1 and above and your L1 isn’t working, please follow these steps.
Solution
To resolve this issue:
-
If you're using CloudShell 2022.1, create a symlink by doing the following:
mklink /D "C:\Program Files (x86)\QualiSystems\CloudShell\Server\python\2.7.10" "C:\Program Files (x86)\QualiSystems\CloudShell\Server\python\2"
-
Make a backup of L1 driver folder
C:\Program Files (x86)\QualiSystems\CloudShell\Server\Drivers\%driver_name%
. -
Open the L1 driver's folder.
-
Delete these folders:
Include
Lib
Scripts
Tcl
located underC:\Program Files (x86)\QualiSystems\CloudShell\Server\Drivers\%driver_name%
-
Open Windows Task Manager and end all running python2 processes from the L1 driver folder
-
Re-install the L1 driver by executing
install_driver.bat
. -
Auto-load the new L1 resource in Resource Manager Client.
-
Make sure it works as expected. You can do this by clicking the Sync from button in the L1 resource's Configuration tab in Resource Manager Client - see Sync between the L1 switch and CloudShell.