Posted on August 28, 2020 8:40 pm
 |  Asked by Matt Mullen
 |  55 views
RESOLVED
0
0
Print Friendly, PDF & Email

Just deployed a cEOS container running 4.23.4.2M and when I try to configure a routing protocol it shows that it is inactive.  For example OSPF:

ceos3#show ip ospf
! OSPF inactive  <—-
OSPF instance 1
Maximum number of LSA allowed 12000
Threshold for warning message 75%
Ignore-time 5 minutes, reset-time 5 minutes
Ignore-count allowed 5, current 0

Same thing for BGP;

ceos3#show ip bgp
BGP inactive

It seems the Rib process is continually crashing,  seeing these messages in the logs:

Aug 28 20:00:09 ceos3 Rib: Commence routing updates
Aug 28 20:00:10 ceos3 ProcMgr-worker: %PROCMGR-6-PROCESS_TERMINATED: ‘Rib’ (PID=27455, status=133) has terminated.
Aug 28 20:00:10 ceos3 ProcMgr-worker: %PROCMGR-6-PROCESS_RESTART: Restarting ‘Rib’ immediately (it had PID=27455)
Aug 28 20:00:10 ceos3 ProcMgr-worker: %PROCMGR-6-PROCESS_STARTED: ‘Rib’ starting with PID=27456 (PPID=465) — execing ‘/usr/bin/Rib’
Aug 28 20:00:11 ceos3 Rib: %AGENT-6-INITIALIZED: Agent ‘Rib’ initialized; pid=27456
Aug 28 20:00:13 ceos3 Rib: Commence routing updates
Aug 28 20:00:14 ceos3 ProcMgr-worker: %PROCMGR-6-PROCESS_TERMINATED: ‘Rib’ (PID=27456, status=133) has terminated.
Aug 28 20:00:14 ceos3 ProcMgr-worker: %PROCMGR-6-PROCESS_RESTART: Restarting ‘Rib’ immediately (it had PID=27456)
Aug 28 20:00:14 ceos3 ProcMgr-worker: %PROCMGR-6-PROCESS_STARTED: ‘Rib’ starting with PID=27460 (PPID=465) — execing ‘/usr/bin/Rib’
Aug 28 20:00:15 ceos3 Rib: %AGENT-6-INITIALIZED: Agent ‘Rib’ initialized; pid=27460
Aug 28 20:00:17 ceos3 Rib: Commence routing updates
Aug 28 20:00:18 ceos3 ProcMgr-worker: %PROCMGR-6-PROCESS_TERMINATED: ‘Rib’ (PID=27460, status=133) has terminated.
Aug 28 20:00:18 ceos3 ProcMgr-worker: %PROCMGR-3-PROCESS_DELAYRESTART: ‘Rib’ (PID=27460) restarted too often! Delaying restart for 120.0 (until 2020-08-28 20:02:18.913349)

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:4.23.4.2M /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 network connect net2 ceos1

docker start ceos1

Anyone else seen this and have any ideas on how to remediate?

1
Posted by Tamas Plugor
Answered on August 28, 2020 8:42 pm

Hi Matt,

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.

HTH,

Tamas

0
Posted by Matt Mullen
Answered on September 2, 2020 6:12 pm

Ok, thanks Tamas.

Matt

Post your Answer

You must be logged in to post an answer.