Posted on March 11, 2019 8:13 pm
 |  Asked by jean-marc
 |  1132 views
« Back to Previous Page
▲
0
▼
♥ 0
Print Friendly, PDF & Email

s
Hello

I ‘ve created two cEOS nodes in GNS3.
I can config ip address on Ethernet interfaces in EOS.
Ethernet1 address in Cli is mapped to Et1 interfaces in bash interfaces
Unfortunately GNS3 use Eth interfaces to connect the container to other nodes

localhost#sh run
! Command: show running-config
! device: localhost (cEOSLab, EOS-4.21.0F)
!
transceiver qsfp default-mode 4x10G
!
spanning-tree mode mstp
!
no aaa root
!
interface Ethernet1
no switchport
ip address 192.168.122.170/24

bash-4.3# ip a show eth1
125: eth1: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 9e:59:07:00:cf:ef brd ff:ff:ff:ff:ff:ff
inet6 fe80::9c59:7ff:fe00:cfef/64 scope link
valid_lft forever preferred_lft forever
bash-4.3# ip a show et1
3: et1: mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 36:27:87:e4:29:05 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.170/24 brd 255.255.255.255 scope global et1
valid_lft forever preferred_lft forever

How to get eth interfaces in EOS Cli ?

thanks for your help
▲
1
▼
✔
Posted by Joris Claassen
Answered on March 12, 2019 8:06 am

Hi Jean-Marc,

When adding the Docker container configuration to GNS3, you have to specify the parameters and number of adapters in the configuration. This can be done like the following example:

Then, you will need to connect the ports (eth1 as eth0 is not yet mapped to the ma1 port, this will be supported in a future release) to eachother like the following example:

Afterwards it is possible to assign IP configuration and reach the cEOS instances over IP:

Have fun playing with cEOS!
▲
0
▼
✔
Posted by Abdeljabbar Nouri
Answered on August 20, 2019 5:40 am

It looks like there is no persistancy.

Hi,

To have persistency for the startup-config in GNS3 when you import a new image of the docker container, you have to define a persistent VOLUME location where startup-configs will be stored.

docker import –change ‘VOLUME /mnt/flash/’ cEOS-lab-.tar.xz ceoslab:

(Claudiu Captari at September 30, 2019 10:08 pm)
▲
0
▼
✔
Posted by Claudiu Captari
Answered on September 30, 2019 10:09 pm

Hi,

To have persistency for the startup-config in GNS3 when you import a new image of the docker container, you have to define a persistent VOLUME location where startup-configs will be stored.

docker import –change ‘VOLUME /mnt/flash/’ cEOS-lab-.tar.xz ceoslab:
« Back to Previous Page

Post your Answer

You must be logged in to post an answer.