Just deployed a cEOS container running 188.8.131.52M and when I try to configure a routing protocol it shows that it is inactive. For example OSPF:
ceos3#show ip ospf
Same thing for BGP;
ceos3#show ip bgp
It seems the Rib process is continually crashing, seeing these messages in the logs:
Aug 28 20:00:09 ceos3 Rib: Commence routing updates
Container was started with these commands:
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:184.108.40.206M /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
docker network connect net1 ceos1
docker start ceos1
Anyone else seen this and have any ideas on how to remediate?
The same issue was discussed here: https://eos.arista.com/forum/ceos-lab-error-no-space-left-on-device/
You'll have to use a port-channel or an SVI for IGP protocols today (for ArBGP you can use Ethernet ports). There's an issue with the naming convention of the kernel interfaces, tracked under BUG397410, which is currently being worked on.
Ok, thanks Tamas.
Post your Answer
You must be logged in to post an answer.