muma wrote:
Anyone feel free to chime in if this isn't up-to-snuff... this used to be a problem, but not with the current released beta-1v3...
I think the issue was with the order of the steps to create a project. This was also with an earlier (beta-1.0v1, I think) of the software ...
1. Create a diagram of your desired network structure, without changing the device names, but including the creation of links between devices;
2. start up the topology, then look at the folder structure in ~/Documents/<project-name> - you should see a list of device directories ("device-1", "device-2", "device-3", etc.)
3. now enter some configurations, save them (within the device consoles).
4. now change the names of the devices, by right-clicking on the devices and clicking on "Configure"
- for each device, change the device label from the assigned default, click "Apply" then click "OK"
5. Now save the overall project and stop all devices.
6. quit gns3 client program.
What used to happen before is that the ".gns3" project file seemed to "lose" the association with the device's changed name and the device-id. IN the latest version that I tried (beta-1.0v3) this does NOT happen, and the program behaves as it should.
You could recover the configurations from the nvram_NNN files and simply copy the contents of each of the "device-n" folders back ... but the format of the ".gns3" file has changed (been corrected...?) and the behaviour hasn't re-appeared (for me, at least, on some pretty "heavy" configurations).
I might suggest that you forget about trying to recover your previous-versions design and move to the newer version of released beta - and chalk things up to experience :-) The folder structure has not changed (right?) and devices are appropriately tracked in the "gns3" project configuration file.
My 2-cents...
Kim
but i have this issue on beta3, and topology was created on beta1, then continued on beta3
isn't it possible to get configs for IOU through GNS3 OVA?