You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nodes: Nexus 9kv 9.3.8 and 10.3.1.F
GNS3 VM 3.0.0beta3 running on ESXi 6.7 20497097
Using web-ui to interface with GNS3 VM.
Google Chrome 125.0.6422.113 (Official Build) (64-bit) on Windows 11
Terminal: both MobaXterm and Web Console for telnet connectivity.
Both Roms work fine on 2.2.47 and boot properly. Both in desktop GUI and Web-UI.
Template had the wrong number of vCPUs changed it to 2.
Nodes appear to boot and turn green on node list.
CPU and Memory usage go up.
Other nodes such as Fortigate, Cisco IOSv, etc. do not seem to have an issue.
Also tried a manual telnet to the port. It connects, but no boot sequence is seen.
Steps to reproduce:
Add Nexus 9k node to topology.
Start node.
Connect console.
Wait
See no boot sequence.
Let me know if you need additional information.
The text was updated successfully, but these errors were encountered:
Nodes: Nexus 9kv 9.3.8 and 10.3.1.F
GNS3 VM 3.0.0beta3 running on ESXi 6.7 20497097
Using web-ui to interface with GNS3 VM.
Google Chrome 125.0.6422.113 (Official Build) (64-bit) on Windows 11
Terminal: both MobaXterm and Web Console for telnet connectivity.
Both Roms work fine on 2.2.47 and boot properly. Both in desktop GUI and Web-UI.
Template had the wrong number of vCPUs changed it to 2.
Nodes appear to boot and turn green on node list.
CPU and Memory usage go up.
Other nodes such as Fortigate, Cisco IOSv, etc. do not seem to have an issue.
Also tried a manual telnet to the port. It connects, but no boot sequence is seen.
Steps to reproduce:
Let me know if you need additional information.
The text was updated successfully, but these errors were encountered: