Posted on February 28, 2020 6:57 pm
 |  Asked by Wei Su
 |  147 views
Tags:
RESOLVED
0
0
Print Friendly, PDF & Email

I am trying ceos 4.20.5F to build a lab topology. I found a lot of features are not supported. Even the basic bgp, vlan .

Did I miss something?

DSW-VM-G3-2.OT7#show running-config section router bgp
DSW-VM-G3-2.OT7(config)#router bgp 4200001173
% Unavailable command (not supported on this hardware platform)
DSW-VM-G3-2.OT7(config)#router ?
general Protocol independent routing configuration
kernel Routes installed by kernel
ospfv3 OSPF Version 3
traffic-engineering traffic-engineering global config

DSW-VM-G3-2.OT7#show version
Arista cEOSSim
Hardware version:
Serial number: N/A
System MAC address: Not available

Software image version: 4.20.5F
Architecture: i386
Internal build version: 4.20.5F-8127914.4205F
Internal build ID: 4d6b4859-39b5-4581-993b-f84ac0736664

cEOS tools version: 1.0

Uptime: 1 day, 20 hours and 45 minutes
Total memory: 131676440 kB
Free memory: 119462412 kB

0
Posted by Tamas Plugor
Answered on February 28, 2020 7:07 pm

From what I see you are not using cEOS-lab, but cEOS, so you have to make sure your underlying hardware supports this.

in cEOS-lab this works on any machine running on linux (but cEOS-lab as the name says is meant for lab testing):

 

cEOS-TP(config)#sh ver
cEOSLab
Hardware version:
Serial number:
System MAC address: 0242.ac11.3eb8

Software image version: 4.23.1F
Architecture: i686
Internal build version: 4.23.1F-14427599.4231F
Internal build ID: eebf6090-7ecd-4bbb-84b9-7c7219570a30

cEOS tools version: 1.1

Uptime: 0 weeks, 3 days, 17 hours and 12 minutes
Total memory: 2036900 kB
Free memory: 984480 kB

cEOS-TP(config-router-bgp)#ip routing
cEOS-TP(config)#
cEOS-TP(config)#
cEOS-TP(config)#router bgp 4200001173
cEOS-TP(config-router-bgp)#

 

Also any reason you are using 4.20.5? Please use the latest images as they have more features, the code has matured a lot since then.

 

0
Posted by Wei Su
Answered on February 28, 2020 7:30 pm

I tried the latest cEOS64-lab-4.23.2F.tar.tar and got the same result

localhost(config)#router ?
bfd Bidirectional Forwarding Detection
general Protocol independent routing configuration
kernel Routes installed by kernel
l2-vpn l2-vpn configuration
ospfv3 OSPF Version 3
traffic-engineering traffic-engineering global config

localhost(config)#router bgp 4200001173
% Unavailable command (not supported on this hardware platform)
localhost(config)#do show version
cEOSLab
Hardware version:
Serial number:
System MAC address: Not available

Software image version: 4.23.2F
Architecture: x86_64
Internal build version: 4.23.2F-15409035.4232F
Internal build ID: 8466ca7e-e60a-453e-8c2f-7b2cf6ad1960

cEOS tools version: 1.1

Uptime: 0 weeks, 0 days, 0 hours and 1 minutes
Total memory: 263464220 kB
Free memory: 262935516 kB

 

---> in the startup log. see this failed log, not sure if it is the cause?

OK ] Started Set the CPU affinity of the... memory, as seen in BUG155276..
[ OK ] Started Publish /etc/port-numbering if needed.
eoskernel-config.service: main process exited, code=exited, status=1/FAILURE
[FAILED] Failed to start Dynamic EosKernel configuration.
See 'systemctl status eoskernel-config.service' for details.
Unit eoskernel-config.service entered failed state.
eoskernel-config.service failed.

 

 

 

0
Posted by Wei Su
Answered on February 28, 2020 10:49 pm

Tried the latest 4.23.2F. Also got the same error.

Here is the docker command(exactly as the readme file)

docker create --name=ceos1 --privileged -e INTFTYPE=eth -e ETBA=1 -e SKIP_ZEROTOUCH_BARRIER_IN_SYSDBINIT=1 -e CEOS=1 -e EOS_PLATFORM=ceoslab -e container=docker -i -t ceosimage:4.23.2F /sbin/init systemd.setenv=INTFTYPE=eth systemd.setenv=ETBA=1 systemd.setenv=SKIP_ZEROTOUCH_BARRIER_IN_SYSDBINIT=1 systemd.setenv=CEOS=1 systemd.setenv=EOS_PLATFORM=ceoslab systemd.setenv=container=docker

[admin@a73c11267.et15 /home/admin]
$docker exec -it ceos2 Cli
localhost>en
localhost#show version
cEOSLab
Hardware version:
Serial number:
System MAC address: Not available

Software image version: 4.23.2F
Architecture: x86_64
Internal build version: 4.23.2F-15409035.4232F
Internal build ID: 8466ca7e-e60a-453e-8c2f-7b2cf6ad1960

cEOS tools version: 1.1

Uptime: 0 weeks, 0 days, 3 hours and 20 minutes
Total memory: 263464220 kB
Free memory: 262782884 kB

localhost#conf
localhost(config)#ip routing
% Unavailable command (not supported on this hardware platform)
localhost(config)#router bgp 10010
% Unavailable command (not supported on this hardware platform)
localhost(config)#

0
Posted by Wei Su
Answered on February 29, 2020 1:36 am

I've tried ceos lab 4.23.2F 4.21.6F 4.20.5F. All have the same problem. I'm puzzled what do I miss?

 

 

did you follow all steps? I don't see a MAC address in your show version so you probably didn't connect the container to a docker network.

Please see below full steps (using 4.23.2F 64 bit, but it should work with any version):

Import image:

~/images # tamas@tamas # docker import cEOS64-lab-4.23.2F.tar.xz ceosimage:test64                                                                                              
sha256:c276941d89187972c3763f3b5e716338b293fe3dcad7fda6dc83c0b2c31f7938

Create docker network if you don't have one already:

~/images # tamas@tamas # docker network create net1337 
9d49f3d3d02cf031185c371655226b755d9f8bf7b528709c8908d96e2632e61e

Create docker container

~/images # 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
c091a79e2481f158eac44a91cde245f2aab266c7ca12a1d1db24381c5816e6c7

Connect container to the docker network

~/images # tamas@tamas # docker network connect net1337 ceos1337

Start container and exec into it

~/images # tamas@tamas # docker start ceos1337 
ceos1337

~/images # tamas@tamas # docker exec -it ceos1337 Cli

Run your commands

 
c091a79e2481>en
localhost#sh ver
 cEOSLab
Hardware version:
Serial number:
System MAC address:  0242.ac66.6f8a

Software image version: 4.23.2F
Architecture:           x86_64
Internal build version: 4.23.2F-15409035.4232F
Internal build ID:      8466ca7e-e60a-453e-8c2f-7b2cf6ad1960

cEOS tools version: 1.1

Uptime:                 0 weeks, 4 days, 5 hours and 10 minutes
Total memory:           2036900 kB
Free memory:            863172 kB

localhost#conf
localhost(config)#ip routing
localhost(config)#router bgp 4200001173
localhost(config-router-bgp)#

HTH,
Tamas

(Tamas Plugor at February 29, 2020 5:18 pm)
0
Posted by Wei Su
Answered on March 2, 2020 8:07 pm

Thank you Tamas

I found the reason. It was because there is no interface created. Arista BGP needs at least one interface up. I think missing the step to create docker network caused the no interface problem.

Regards,

Wei

Yes that's correct, that's why I was saying you need to connect it to a docker network. Glad it got resolved! Let us know if you see any other issues!
(Tamas Plugor at March 2, 2020 10:07 pm)

Post your Answer

You must be logged in to post an answer.