Jump to content

[OFFER] IOL images from CML 2.7


Recommended Posts

3 hours ago, w1z4rd said:

Downloaded the two images.

Installed the L2 image in GNS3 on my Ubuntu laptop. I gave it 640MB or RAM and it worked just fine. My only issue is that GNS3 cannot push a template startup-config. So you have to create the IOL device and do not define a Startup-config.

To get the file to work with GNS3 on Ubuntu, I also renamed the file to give it a .bin extension. Also, you need to give the file executable permissions:

This is the hidden content, please

At the end, I got the following:

This is the hidden content, please

Thanks a bunch @netkillui!

Tried this on gns3 running with a VM in Windows and on eve-ng. did not work. The L3 image works fine as is. 

  • Like 31
  • Thanks 3
  • Haha 2
Link to comment
Share on other sites

4 hours ago, netkillui said:

Tried this on gns3 running with a VM in Windows and on eve-ng. did not work. The L3 image works fine as is. 

I did manage to get the IOL L2 image to run on GNS3. I run my GNS3 images directly on my Ubuntu host. I guess the way I do it must be very similar to how you would do it when using the GNS3 VM.

When I first tried running the IOL L2 image, it would not run because the image was not an executable. I thus had to `chmod +x` the file. 

After that, I managed to add it into GNS3 as an IOL device, with no issues. But when I tried running it, GNS3 threw an error. I think the problem that GNS3 had in the beginning was actually writing the startup-config into the switch's NVRAM (or flash, whatever).

GNS3 just couldn't do it and it threw an error. (I am not exactly sure but, if I remember correctly, the error was something like "GNS3 could not find nvram in the expected location"). Well, I thought, the only reason that GNS3 is looking for the nvram during bootup, to begin with, would be to put the startup-config in there. I knew it wasn't the IOL image that couldn't find its NVRAM, because it was GNS3 that was complaining, not the IOL itself.

So I went to the device's settings in GNS3, and told GNS3 to not use a startup-config. To be sure that the issue had nothing to do with the VM's RAM, I also bumped RAM to 614 MB.

I started the switch, and it worked. It actually boots up pretty fast too.

I later tried 512 MB RAM, and that worked as well.

I tried the L2 IOL because my experience that those ones are a little harder to get to run, and have not yet tested the IOL L3 image.

Are you getting an error message when trying to run the L2 image in GNS3? Can you post the error here? And how much RAM did you give it?

  • Like 1
Link to comment
Share on other sites

19 hours ago, w1z4rd said:

I did manage to get the IOL L2 image to run on GNS3. I run my GNS3 images directly on my Ubuntu host. I guess the way I do it must be very similar to how you would do it when using the GNS3 VM.

When I first tried running the IOL L2 image, it would not run because the image was not an executable. I thus had to `chmod +x` the file. 

After that, I managed to add it into GNS3 as an IOL device, with no issues. But when I tried running it, GNS3 threw an error. I think the problem that GNS3 had in the beginning was actually writing the startup-config into the switch's NVRAM (or flash, whatever).

GNS3 just couldn't do it and it threw an error. (I am not exactly sure but, if I remember correctly, the error was something like "GNS3 could not find nvram in the expected location"). Well, I thought, the only reason that GNS3 is looking for the nvram during bootup, to begin with, would be to put the startup-config in there. I knew it wasn't the IOL image that couldn't find its NVRAM, because it was GNS3 that was complaining, not the IOL itself.

So I went to the device's settings in GNS3, and told GNS3 to not use a startup-config. To be sure that the issue had nothing to do with the VM's RAM, I also bumped RAM to 614 MB.

I started the switch, and it worked. It actually boots up pretty fast too.

I later tried 512 MB RAM, and that worked as well.

I tried the L2 IOL because my experience that those ones are a little harder to get to run, and have not yet tested the IOL L3 image.

Are you getting an error message when trying to run the L2 image in GNS3? Can you post the error here? And how much RAM did you give it?

Here's my settings and the error message:

image.png.2626c93eb373c06a0bc6fbc1078ab040.png

Link to comment
Share on other sites

PNET Lab - L2 Image not working.

i get below error on wrapper.

tail: /opt/unetlab/tmp/9/50/wrapper.txt: file truncated
30/2 14:40:13.66 INF    Device_id = 2
30/2 14:40:13.66 INF    Session_id = 50
30/2 14:40:13.66 INF    port = 30050
30/2 14:40:13.67 INF    NETMAP file created.
30/2 14:40:13.67 INF    TS configured.
30/2 14:40:13.67 INF    TAP interface configured (s=9, n=vunl50_0).
30/2 14:40:13.67 INF    TAP interface configured (s=11, n=vunl50_16).
30/2 14:40:13.67 INF    TAP interface configured (s=13, n=vunl50_32).
30/2 14:40:13.67 INF    TAP interface configured (s=15, n=vunl50_48).
30/2 14:40:13.67 INF    Adding subprocess stdout descriptor (6).
30/2 14:40:13.68 INF    Adding telnet socket descriptor (8).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (9).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (11).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (13).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (15).
30/2 14:40:16.68 ERR    /tmp/netio32818/514,/tmp/netio32818/2,-2070196716,-2070196724.
30/2 14:40:16.68 ERR    Error while connecting local AF_UNIX: Connection refused (2)
30/2 14:40:16.68 ERR    Cannot listen at AF_UNIX (2). ERR: Cannot open AF_UNIX sockets (2).
30/2 14:40:16.68 ERR    Failed to create AF_UNIX socket file (2).
30/2 14:40:16.68 INF    Caught SIGTERM, killing child.
30/2 14:40:16.68 INF    Child is no more running.
 

Link to comment
Share on other sites

3 hours ago, hariram said:

PNET Lab - L2 Image not working.

i get below error on wrapper.

tail: /opt/unetlab/tmp/9/50/wrapper.txt: file truncated
30/2 14:40:13.66 INF    Device_id = 2
30/2 14:40:13.66 INF    Session_id = 50
30/2 14:40:13.66 INF    port = 30050
30/2 14:40:13.67 INF    NETMAP file created.
30/2 14:40:13.67 INF    TS configured.
30/2 14:40:13.67 INF    TAP interface configured (s=9, n=vunl50_0).
30/2 14:40:13.67 INF    TAP interface configured (s=11, n=vunl50_16).
30/2 14:40:13.67 INF    TAP interface configured (s=13, n=vunl50_32).
30/2 14:40:13.67 INF    TAP interface configured (s=15, n=vunl50_48).
30/2 14:40:13.67 INF    Adding subprocess stdout descriptor (6).
30/2 14:40:13.68 INF    Adding telnet socket descriptor (8).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (9).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (11).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (13).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (15).
30/2 14:40:16.68 ERR    /tmp/netio32818/514,/tmp/netio32818/2,-2070196716,-2070196724.
30/2 14:40:16.68 ERR    Error while connecting local AF_UNIX: Connection refused (2)
30/2 14:40:16.68 ERR    Cannot listen at AF_UNIX (2). ERR: Cannot open AF_UNIX sockets (2).
30/2 14:40:16.68 ERR    Failed to create AF_UNIX socket file (2).
30/2 14:40:16.68 INF    Caught SIGTERM, killing child.
30/2 14:40:16.68 INF    Child is no more running.
 

can you test these two commands :

sed -i -e 's/127.0.0.1 xml.cisco.com//' /etc/hosts


 

Edited by najibarca
Link to comment
Share on other sites

15 hours ago, hariram said:

PNET Lab - L2 Image not working.

i get below error on wrapper.

tail: /opt/unetlab/tmp/9/50/wrapper.txt: file truncated
30/2 14:40:13.66 INF    Device_id = 2
30/2 14:40:13.66 INF    Session_id = 50
30/2 14:40:13.66 INF    port = 30050
30/2 14:40:13.67 INF    NETMAP file created.
30/2 14:40:13.67 INF    TS configured.
30/2 14:40:13.67 INF    TAP interface configured (s=9, n=vunl50_0).
30/2 14:40:13.67 INF    TAP interface configured (s=11, n=vunl50_16).
30/2 14:40:13.67 INF    TAP interface configured (s=13, n=vunl50_32).
30/2 14:40:13.67 INF    TAP interface configured (s=15, n=vunl50_48).
30/2 14:40:13.67 INF    Adding subprocess stdout descriptor (6).
30/2 14:40:13.68 INF    Adding telnet socket descriptor (8).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (9).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (11).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (13).
30/2 14:40:13.68 INF    Adding TAP interface descriptor (15).
30/2 14:40:16.68 ERR    /tmp/netio32818/514,/tmp/netio32818/2,-2070196716,-2070196724.
30/2 14:40:16.68 ERR    Error while connecting local AF_UNIX: Connection refused (2)
30/2 14:40:16.68 ERR    Cannot listen at AF_UNIX (2). ERR: Cannot open AF_UNIX sockets (2).
30/2 14:40:16.68 ERR    Failed to create AF_UNIX socket file (2).
30/2 14:40:16.68 INF    Caught SIGTERM, killing child.
30/2 14:40:16.68 INF    Child is no more running.
 

Can you try running the binary as root? Something like `sudo x86_64_crb_linux_l2-adventerprisek9-ms.bin` ?

Link to comment
Share on other sites

The host file already have xml.cisco.com

not sure i have understand this command "sudo x86_64_crb_linux_l2-adventerprisek9-ms.bin" - dont think that work in Linux.

i run manually i get below error :

root@pnetlab:/opt/unetlab/addons/iol/bin# LD_LIBRARY_PATH=/opt/unetlab/addons/iol/lib /opt/unetlab/addons/iol/bin/x86_64_crb_linux_l2-adventerprisek9-ms.bin 1
IOS On Unix - Cisco Systems confidential, internal use only

Warning: Abnormal ciscoversion string, please notify the IOU team
with the name of this branch
Warning: we parsed - NULL
Aborted (core dumped)

(other images - boots as expected)
 

Link to comment
Share on other sites

Posted (edited)
2 hours ago, hariram said:

The host file already have xml.cisco.com

not sure i have understand this command "sudo x86_64_crb_linux_l2-adventerprisek9-ms.bin" - dont think that work in Linux.

i run manually i get below error :

root@pnetlab:/opt/unetlab/addons/iol/bin# LD_LIBRARY_PATH=/opt/unetlab/addons/iol/lib /opt/unetlab/addons/iol/bin/x86_64_crb_linux_l2-adventerprisek9-ms.bin 1
IOS On Unix - Cisco Systems confidential, internal use only

Warning: Abnormal ciscoversion string, please notify the IOU team
with the name of this branch
Warning: we parsed - NULL
Aborted (core dumped)

(other images - boots as expected)
 

1. remove xml.cisco.com entry from /etc/hosts file

2. run this command "iptables -I OUTPUT -p udp --dport 53 -m string --hex-string "|03|xml|05|cisco|03|com" --algo bm -j DROP"

3. Try IOL2 image again. 
 

Edited by netkillui
  • Like 4
  • Thanks 1
Link to comment
Share on other sites

On 3/31/2024 at 7:21 PM, netkillui said:

1. remove xml.cisco.com entry from /etc/hosts file

2. run this command "iptables -I OUTPUT -p udp --dport 53 -m string --hex-string "|03|xml|05|cisco|03|com" --algo bm -j DROP"

3. Try IOL2 image again. 
 

Hey, Thanks a lot! That worked for me in GNS3 VM. 

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...