Closed Raizo62 closed 7 years ago
Do you have the issues with all IOU images? For me it seem a problem with an image with a different behavior and we can do nothing about it.
Which IOU do you advise me to test ?
If it is a problem of the image (why not), why i don't have the error message if i start manually the image ?
Have you connected your IOU to something when you tested in GNS3?
On Fri, Jul 7, 2017, 18:13 Raizo62 notifications@github.com wrote:
Which IOU do you advise me to test ?
If it is a problem of the image (why not), why i don't have the error message if i start manually the image ?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/GNS3/gns3-gui/issues/2147#issuecomment-313654236, or mute the thread https://github.com/notifications/unsubscribe-auth/AEiE5oMKWOKEQTLiURR4ae_Dx5kgAOctks5sLhLhgaJpZM4OQBMv .
I have tested 2 IOU switch. 1 is not connected, 1 is connected to ethernet switch. In GNS3, i have the error message. Manually, no error message.
I have tested on old Live Raizo v8.17.04.22 (with GNS3 2.0.0dev13). I have the message error.
I have tested on old Live Raizo v7.16.09.11 (with GNS3 1.5.3.dev1). I don't see the error message, but i can't see the first lines of boot of cisco : perhaps the error is here, but the console does not show it to me)
I do not have the issue with Ubuntu 16.04
IOU1#show version
Cisco IOS Software, Linux Software (I86BI_LINUXL2-ADVIPSERVICESK9-M), Version 15.2(CML_NIGHTLY_20151103)FLO_DSGS7, EARLY DEPLOYMENT DEVELOPMENT BUILD, synced to FLO_DSGS7_POSTCOLLAPSE_TEAM_TRACK_DSGS_PI5
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Wed 04-Nov-15 02:31 by mmen
According the many forums and other websites (e.g. http://evilrouters.net/2011/01/18/cisco-iou-faq/), this error has no consequences.
Hi
I think that is not a critical bug.
On Live Raizo (Debian Jessie), i use and start an IOU switch (i86bi-linux-l2-adventerprisek9-15.2d)
The switch seems to work correctly.
If i stop this switch, i open an xterm, and i do :
I don't see the error message