Posted on November 2, 2019 1:23 am
 |  Asked by Jeff
 |  521 views
RESOLVED
0
0
Print Friendly, PDF & Email

I foloowed the setup at https://eos.arista.com/ceos-lab-in-gns3/ and successfully installed CEOS 4.21.7M on docker on my GNS3 VM. I can start, log in and configure. However, no Management port is available, and cannot be created. the ENV parameter “MGMT_INTF=eth0” has been added and can be seen in the running container.
Any help would be appreciated.

localhost(config)#sh run
! Command: show running-config
! device: localhost (cEOSLab, EOS-4.21.7M)
!
transceiver qsfp default-mode 4x10G
!
spanning-tree mode mstp
!
no aaa root
!
interface Ethernet1
!
interface Ethernet2
!
interface Ethernet3
!
interface Ethernet4
!
interface Ethernet5
!
interface Ethernet6
!
interface Ethernet7
!
no ip routing
!
end

0
Posted by Jason Hardy
Answered on November 2, 2019 3:52 am

Hi Jeff,

Management interfaces were introduced in cEOS 4.22.0 and up.

localhost#sh ver
cEOSLab
Hardware version:
Serial number:
System MAC address: 066d.ca12.aa7c

Software image version: 4.22.0.1F
Architecture: i386
Internal build version: 4.22.0.1F-12454880.42201F
Internal build ID: 6b11415f-b52b-4b9a-9611-4ba21bf993fb

cEOS tools version: 1.1

Uptime: 0 weeks, 0 days, 0 hours and 57 minutes
Total memory: 57720508 kB
Free memory: 55426936 kB

localhost#sh int status
Port Name Status Vlan Duplex Speed Type Flags Encapsulation
Et1 connected 1 full unconf EbraTestPhyPort
Et2 connected 1 full unconf EbraTestPhyPort
Et3 connected 1 full unconf EbraTestPhyPort
Et4 connected 1 full unconf EbraTestPhyPort
Et5 connected 1 full unconf EbraTestPhyPort
Et6 connected 1 full unconf EbraTestPhyPort
Et7 connected 1 full unconf EbraTestPhyPort
Et8 connected 1 full unconf EbraTestPhyPort
Et9 connected 1 full unconf EbraTestPhyPort
Et10 connected 1 full unconf EbraTestPhyPort
Et11 connected 1 full unconf EbraTestPhyPort
Et12 connected 1 full unconf EbraTestPhyPort
Ma0 connected routed full 10M 10/100/1000

Can you please try one of those releases and see if that works for you?

Thanks!
Jason

Yes, I will try a 4.22.x version and report back
(Jeff at November 4, 2019 1:13 pm)
I imported CEOS 4.22.2F and the management port is now available. Thanks.
(Jeff at November 4, 2019 2:32 pm)
How do we create Ma0...All default networks that are getting created are Et1 Et2 and so on .
(Deepak Makkar at April 5, 2020 6:27 am)
You can use systemd.setenv=MGMT_INTF=eth0 when you create the container, example:

tamas@tamas # docker create --name=ceos1337 -p 4000:8080 -p 4001:6030 -p 4002:6061 -p 4003:8081 -p 4423:443 --privileged -e INTFTYPE=eth -e ETBA=4 -e SKIP_ZEROTOUCH_BARRIER_IN_SYSDBINIT=1 -e CEOS=1 -e EOS_PLATFORM=ceoslab -e container=docker -i -t ceosimage:test64 /sbin/init systemd.setenv=INTFTYPE=eth systemd.setenv=ETBA=4 systemd.setenv=SKIP_ZEROTOUCH_BARRIER_IN_SYSDBINIT=1 systemd.setenv=CEOS=1 systemd.setenv=EOS_PLATFORM=ceoslab systemd.setenv=container=docker systemd.setenv=MAPETH0=1 systemd.setenv=MGMT_INTF=eth0

HTH,
Tamas

(Tamas Plugor at April 5, 2020 1:11 pm)
0
Answered on August 27, 2020 11:58 am

Hi,

the management port is indeed mapped, but Ma0 does not inherit the ip assign by docker to eth0:


sh-4.2# ip -f inet address
101: eth0@if102: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link-netnsid 0
inet 172.23.0.2/16 brd 172.23.255.255 scope global eth0
valid_lft forever preferred_lft forever

sh-4.2# Cli
localhost>show ip int bri Address
Interface IP Address Status Protocol MTU Owner
----------------- ---------------- ------------ -------------- ---------- -------
Management0 unassigned up up 1500

Manually assigning the IP to Ma0 doese not work either and I cannot ping the docker Brige IP (arp table stays empty).

Is there any possibility to make Ma0 reachable over the docker bridge?

Best regards,

JB

0
Posted by Tamas Plugor
Answered on August 27, 2020 12:13 pm

Hi JB,

I just did a quick test, and configuring the IP on ma0 that I see when doing docker inspect, works fine!

Excerpt from docker inspect ceos138

     "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "8e2be567aac4de4da59aad2e7549c45d32e194cc52ade865703fd48d0f068675",
                    "EndpointID": "ff97ddf921b0eb7d8f9bcbebda5001a0365b05e394a465726d7a8ff8ace6d745",
                    "Gateway": "172.17.0.1",
                    "IPAddress": "172.17.0.3",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:11:00:03",
                    "DriverOpts": null
                },

 

Output of show ip int br

ceos138(config-if-Ma0)#sh ip int b
                                                                                 Address
Interface         IP Address              Status       Protocol           MTU    Owner
----------------- ----------------------- ------------ -------------- ---------- -------
Ethernet1         192.168.208.40/24       up           up                1500
Management0       172.17.0.3/24           up           up                1500

 

Pinging from the host:

[root@master-node ~]# ping 172.17.0.3
PING 172.17.0.3 (172.17.0.3) 56(84) bytes of data.
64 bytes from 172.17.0.3: icmp_seq=1 ttl=64 time=0.154 ms
64 bytes from 172.17.0.3: icmp_seq=2 ttl=64 time=0.078 ms

HTH,
Tamas

0
Answered on August 31, 2020 9:24 am

Hi Tamas,

Indeed, it works. I was using Docker on my Windows Laptop with WSL2, it does not work their. But with a standard Ubuntu Host everything is fine.

Thank you for the test.

Regards,

JB

Post your Answer

You must be logged in to post an answer.