• Tag : cEOS


LLDP crashed with Assertion `port <= phyIntfPerSlot' failed.

Hello, I created a lab using cEOS where I connected containers using veth pairs. Seems when the interface number (e.g. ‘eth149’) is large, Lldp would fail to start. So my questions are, what is exact value of ‘phyIntfPerSlot’? Is there any way to adjust its value (e.g. by setting some environment variables for cEOS)? bash-4.2# Lldp Lldp: /src/Lldp/LldpInputSm.tin:118: void Lldp::Agent::Input::intfNameToVlanIdAndManAddrPriority(Arnet::IntfId, Bridging::VlanIdOrNone*, Lldp::ManAddrPriority*): Assertion `port <= phyIntfPerSlot’ failed. Unix Time: 1633450063: Process 3388 lwp 3388 died with signal 6 (SIGABRT) code -6 (tkill) Process has 1 thread —————————————- Backtrace: (most recent first) /lib/libtac.so.0(_ZN3Tac13SignalHandler13signalHandlerEiP9siginfo_tPv+0x736)[0xf79d0166] [0xf7f21020] [0xf7f20ff9] /lib/libc.so.6(gsignal+0x48)[0xf743dc08] /lib/libc.so.6(abort+0x156)[0xf743fa96] /lib/libc.so.6(+0x25ebd)[0xf7435ebd] /lib/libc.so.6(+0x25f3a)[0xf7435f3a] /lib/libLldpImpl.so(+0x74973)[0xf4485973] ……...
Continue reading →

Multiple commands in non-interactive CLI

Hello, I was trying to run non-interactive CLI in cEOS and could not find much documents about it. According to its help, bash-4.2# Cli –help usage: Cli [-h] [-s SYSNAME] [-k SYSDBSOCKNAME] [-l] [–pdb] [-c COMMAND] [-A]            [-M] [-e] [-E] [-p PRIVILEGE] [-i PLUGINS] [-I] [-G]            [–startup-config] [–disable-autocomplete]            [-T STANDALONE_SHELL_TIMEOUT] [–completions COMPLETIONS]            [config-filename] positional arguments:   config-filename       Configuration filename to parse optional arguments:   -h, –help            show this help message and exit...
Continue reading →

cEOS-lab – GRE support?

Hi, Just started playing with Arista cEOS and wanted to test the GRE. I have Cisco background. This is very simple setup. The underlying connectivity is fine (the endpoints are reachable on the sub-net). But the GRE endpoints fail. I see that the “Hardware forwarding is not supported” – see below. Not sure what does it mean here. The Wireshark shows that the packet is leaving the ceos1. The cEOS embedded tcpdump on the peer container shows nothing The questions: Is the GRE supported on cEOS lab image? Where can I find the the cEOS restriction list (what feature...
Continue reading →

cEOS, VRFs, and EVPN – Not Working Properly

Hey folks –   I’m playing around with the latest cEOS image 4.25.2F-20711308.4252F (engineering build) and its handling of VRFs within EVPN seems broken.  Specifically around the importing and exporting of RTs.  As an example, let’s say I have three VRFs: VRF A VRF B VRF C Within BGP I have: VRF A importing [A, B, C], and exporting A. VRF B importing [A, B], and exporting B. VRF C importing [A, C], and exporting C. Basically, A is importing all VRFs so he can talk to them via the VXLAN data plane.  Each of the other VRFs is importing...
Continue reading →

Can cEOS inherit docker assigned IP address on management interface?

Hello, I create a ceos image with the following command docker create –name=ceostest –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 ceos /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   Unfortunately, the Ma0 interface doesn’t come up with interface IP that docker assigned to eth0 interface. Is there a way to start a cEOS container and have network access to its interface via docker network?

CEOS feature restrictions?

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...
Continue reading →


Introduction vEOS-lab/cEOS-lab on GNS3 – What is it? Fast, Multi-user, Efficient nested virtual lab using Qemu/Kvm/docker images of vEOS-lab/cEOS-lab Dynamic persistent config/storage of each cEOS container across stop/starts and GNS3 project closure/re-opens Deployed in minutes on ESXi host. Cloning and creating another bubble is easy, fast and can be moved around Integrated data plane traffic generation tool (Ostinato) in this lab Packet capture on any links between vEOS/cEOS devices Required SW/HW  GNS3 Server VM (Ubuntu 18.04 LTS VM + GNS3 Server) VMware Host system running ESXi version 6 or above with Mgmt Network access ESXi host to deploy this GNS3...
Continue reading →

cEOS at Podman

Hi Colleagues, I’ve been trying to start cEOS at Fedora 31. Quite handy manual https://eos.arista.com/ceos-lab-topo/ doesn’t work in full . I managed to start a container, but couldn’t execute CLI. It says that “Error: executable file not found in $PATH: No such file or directory: OCI runtime command not found error”. Did anyone have a chance to activate it at the similar platform ? Regards, Yury

Management port on cEOS missing

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 !...
Continue reading →

VXLAN support on cEOS

Does VXLAN works with cEOS? I have seen some issues where the VLAN SVI stops responding(couldn’t ping) as soon as you enable vxlan on cEOS Thanks, R

cEOS-lab in GNS3

GNS3 is a great tool to visualize your (home-)lab environment and simulate all kinds of network topologies using different virtualization and isolation technologies. It has been widely used to create environments using vEOS-lab, but because vEOS-lab requires quite some resources (e.g. 2GB of RAM is required) the scale of these labs was often quite limited, especially on low-memory devices. Arista’s cEOS-lab is a new way of packaging the EOS-lab suite. Using the Docker container daemon, it is possible to use the kernel of the host machine and to only run the EOS processes that are required on the machine, making...
Continue reading →

cEOS License Scheme

Starting from EOS-4.21.3F, license for feature BRCM-STRATA-SCHW-TP, which stands for Broadcom Strata Single Chip Hardware Third Party, is required to deploy cEOS/EOS on White Box. Following is an illustration of how cEOS/EOS White Box license is enforced, Details Expiry Warning Log In case of less than 30 days but more than 24 hours to expiration, following log is generated, %LICENSE-4-ABOUT_TO_EXPIRE: License for feature BRCM-STRATA-SCHW-TP expires in <n> days in case of less than 24 hours to expiration, %LICENSE-4-ABOUT_TO_EXPIRE: License for feature BRCM-STRATA-SCHW-TP expires today Soft Enforcement In case of license expiration, following syslog message is generated within grace period, %LICENSE-4-EXPIRED: License...
Continue reading →

cEOS interfaces without docker

I turned up 2 devices, with 2 docker networks (as seen in the README). The problem with this is that you have to use docker networking and bridges. With bridges there is an additional step to allow LLDP: echo 16384 > /sys/class/net/bridge_name/bridge/group_fwd_mask I was hoping that I could just not use docker networking (or docker at all eventually). Here is what I did to add an interface via iproute. Is there any issue with this approach? (ceo1 and ceos2) localhost#show int status Port Name Status Vlan Duplex Speed Type Flags Encapsulation Et1 connected 1 full unconf EbraTestPhyPort Et2 connected 1...
Continue reading →


Description Ahost is a generic Fedora-based Linux OS primarily for the purposes of hosting cEOS. It has a 64-bit kernel (EosKernel) and a 32-bit userspace. It is provided as a SWI called Ahost.swi. Platform compatibility DCS-7050CX3-32S DCS-7050SX3-48YC12 DCS-7060CX-32S-ES DCS-7060CX-32S-SSD DCS-7260CX3-64 Configuration To load Ahost on a box running EOS: Copy Ahost.swi to /mnt/flash/ on the box Modify the boot-config (/mnt/flash/boot-config) to point to Ahost.swi: SWI=flash:/Ahost.swi Reboot the box   Installation of Ahost.swi through onie-installer is supported on White Boxes in experimental mode.   Ahost acquires its IP over DHCP. This may result in a different IP address than the one...
Continue reading →

cEOS Trunk issues

Using 2 cEOS with 2 vlans in each with the corresponding nodes from the vlan subnets: vlan10 = vlan20 = hosts from the same vlan can ping each other if connected to the same switch, but not if they are in different ones through the trunk (configured as etherchannel). Traffic capture showing arp queries from both sides looking for each other. But both switches arp tables is empty, not showing even those connected locally: ceos1#sh arp Address Age (min) Hardware Addr Interface ceos3#sh arp Address Age (min) Hardware Addr Interface ——————- ceos3: ceos3#sh run ! Command: show running-config...
Continue reading →

cEOS instability

Hi, I played a bit with cEOS, I have 4 containers running, 2 spines and 2 leaf, each spine is connected to the 2 leafs. I first built a lab with eBPG between the spines and leaf, and then wanted to try eVPN. The connectivity between the cEOS is quite unreliable, I often have to “shut / noshut” the interfaces when they lose connectivity (ie: spine can no longer ping leaf). Anyone aware of issues with cEOS ? This is the process I followed to create the lab: # create docker instances with needed environment variables docker create –name=spine1 –privileged...
Continue reading →

Network CI/CD Part 1 – Building network topologies with Docker and cEOS-lab

Introduction As the networking industry continues riding the DevOps wave and network engineers become more comfortable using automation tools like Ansible and Salt, network still remains the most brittle piece of IT infrastructure. Partially this can be justified by the fact that network underpins all other areas of IT infrastructure stack – compute, storage and virtualisation. However we, as network engineers, have done very little to improve our confidence in networks and until now some of the biggest outages were caused by trivial network configuration mistakes. When software industry was facing similar challenges, the response was to create Continuous Integration (CI) pipelines –...
Continue reading →


Get every new post on this blog delivered to your Inbox.

Join other followers: