cancel
Showing results for 
Search instead for 
Did you mean: 

vIST still not working in GNS3 with version9.2

vIST still not working in GNS3 with version9.2

flan
New Contributor

I was able to get the virtual-ist up and running in the GNS3 environment using the new 9.2 image. Oh I was so happy. But, alas it stops working after a couple of minutes. 

If we reset the switch it comes up and then a couple of minutes later it goes down again. this is with the new image 9.2 on the github. As much as I appreciate having a gns3 image to work with and believe me I am very grateful. Having something as common as vIST not work is very frustrating to say the least. If there is anyway that I can help get this working please feel free to DM me.  Screenshot 2025-04-25 at 11.46.11 AM.png

 

Screenshot 2025-04-25 at 11.48.09 AM.png

Screenshot 2025-04-25 at 11.49.49 AM.png

Screenshot 2025-04-25 at 11.50.16 AM.png

the message that we are getting is. 

1-FE-A:1#1 2025-04-25T15:50:31.393Z 1-FE-A CP1 - 0x000646ef - 00000000 GlobalRouter MLT WARNING SMLT IST failing to come up because socket connect failed: istSocketConnectErr=12
1 2025-04-25T15:52:35.210Z 1-FE-A CP1 - 0x000646ef - 00000000 GlobalRouter MLT WARNING SMLT IST failing to come up because socket connect failed: istSocketConnectErr=24
show software
************************************************************************************
Command Execution Time: Fri Apr 25 15:54:37 2025 UTC
************************************************************************************
 
====================================================================================================
                    software releases in /intflash/release/
====================================================================================================
FEGNS3.9.2.0.0.GA             (Primary Release)             (Signed Release)
 
-----------------------------------------------------------------------------------------------------------
Auto Commit     : enabled
Commit Timeout  : 10 minutes
 
1-FE-A:1#1 2025-04-25T15:54:38.189Z 1-FE-A CP1 - 0x000646ef - 00000000 GlobalRouter MLT WARNING SMLT IST failing to come up because socket connect failed: istSocketConnectErr=36
 
1-FE-B:1#1 2025-04-25T15:50:32.272Z 1-FE-B CP1 - 0x000646ef - 00000000 GlobalRouter MLT WARNING SMLT IST failing to come up because IST VLAN is down, retry1
1 2025-04-25T15:50:32.272Z 1-FE-B CP1 - 0x000646ef - 00000000 GlobalRouter MLT WARNING SMLT IST failing to come up because listen socket select timed out, 2
1 2025-04-25T15:50:32.272Z 1-FE-B CP1 - 0x000646ef - 00000000 GlobalRouter MLT WARNING SMLT IST failing to come up because encountered select error: istSoc1
1 2025-04-25T15:52:35.246Z 1-FE-B CP1 - 0x000646ef - 00000000 GlobalRouter MLT WARNING SMLT IST failing to come up because listen socket select timed out, 4
1 2025-04-25T15:54:39.221Z 1-FE-B CP1 - 0x000646ef - 00000000 GlobalRouter MLT WARNING SMLT IST failing to come up because listen socket select timed out, 6
 
 
Please let me know thanks,
Flan
 

 

6 REPLIES 6

flan
New Contributor

BUMP?

Yes, that's unfortunate, there are a few limitations with the VM, vIST is one of them.

GTM-P2G8KFN