Support and News Forum

Posted: **Tue Oct 30, 2018 2:19 pm**

problem description

we have a bare metal eve-ng deployment running csr's (everest), but I'm unable to get csr's to communicate over dot1q when they're either directly connected, or over a pnet (using pnet7). We had a previous deployment of EVE (not bare metal) and this worked fine. Is there anything I can do on a bare metal deployment to make this work?

Thanks!
Erik

bare metal deployment

Code: Select all

root@eve-lab:~# uname -r
4.9.40-eve-ng-ukms-2+

root@eve-lab:~# arch
x86_64


root@eve-lab:~# more /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
iface eth0 inet manual
auto pnet0
iface pnet0 inet static
    address x.x.x.x
    netmask 255.255.254.0
    gateway x.x.x.x
    hwaddress 00:0a:f7:9e:8e:44
    dns-domain ne.x.net
    dns-nameservers  x.x.x.x  x.x.x.x
    bridge_ports eth0
    bridge_stp off

# Cloud devices
iface eth1 inet manual
auto pnet1
iface pnet1 inet static
    address x.x.x.x
    netmask 255.255.252.0
    bridge_ports eth1
    bridge_stp off

iface eth2 inet manual
auto pnet2
iface pnet2 inet manual
    bridge_ports eth2
    bridge_stp off

iface eth3 inet manual
auto pnet3
iface pnet3 inet manual
    bridge_ports eth3
    bridge_stp off

iface eth4 inet manual
auto pnet4
iface pnet4 inet manual
    bbridge_ports eth4
    bridge_stp off

iface eth5 inet manual
auto pnet5
iface pnet5 inet manual
    bridge_ports eth5
    bridge_stp off

iface eth6 inet manual
auto pnet6
iface pnet6 inet manual
    bridge_ports eth6
    bridge_stp off

iface eth7 inet manual
auto pnet7
iface pnet7 inet manual
    bridge_ports eth7
    bridge_stp off

iface eth8 inet manual
auto eth8
iface pnet8 inet manual
    bridge_ports eth8
    bridge_stp off

iface eth9 inet manual
auto pnet9
iface pnet9 inet manual
    bridge_ports eth9
    bridge_stp off

Posted: **Tue Oct 30, 2018 2:45 pm**

all simple mate, you didnt complete very important steps in bare install..

2.8 - 2.10, it is very very important !!! redo this again !!!

http://www.eve-ng.net/documentation/ins ... re-install

thats why you have not eth interface in your ifconfig !!!!!!!!!!
and no need make pnet1 with IP in the intial setup !

Uldis

Posted: **Wed Oct 31, 2018 9:56 am**

thanks for the quick answer... unfortunately I didn't set this up, a former coworker of mine did, so I'm not 100% sure which steps he followed, etc. Do I need to re-install EVE to get this to work properly or do I just need to run steps 2.8 - 2.10 and then reboot? I only have remote access to the machine, so I'm worried that I will lose access via the management interface...
Thanks again!
The SED commands were run & the /etc/network/interfaces config now looks like this:

Code: Select all

root@eve-lab:~# more /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
    address x.x.x.x
    netmask 255.255.254.0
    gateway x.x.x.x
    hwaddress 00:0a:f7:9e:8e:44
    dns-domain x.x.net
    dns-nameservers  x.x.x.x  x.x.x.x
    bridge_stp off

# Cloud devices
iface eth1 inet manual
auto pnet1
iface pnet1 inet static
    address  x.x.x.x
    netmask 255.255.252.0
    bridge_ports eth1
    bridge_stp off

iface eth2 inet manual
auto pnet2
iface pnet2 inet manual
    bridge_ports eth2
    bridge_stp off

Erik

Posted: **Wed Oct 31, 2018 3:02 pm**

IT DOES, you must upgrade EVE Community to v92
the new interface from v92 is introduced for Denali, Everest or Fuji..
it is vmxnet3

upgrade your eve please

Posted: **Fri Nov 02, 2018 2:45 pm**

Hello there, really appreciate the help... I ran the specified commands & upgraded EVE according to instructions on the site, but ended up w/ the same packager version:

Code: Select all

root@eve-lab:~# dpkg -l eve-ng
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                                 Version                         Architecture                    Description
+++-====================================================-===============================-===============================-==============================================================================================================
ii  eve-ng                                               2.0.3-86                        amd64                           A new generation software for networking labs.


root@eve-lab:~# apt-cache policy eve-ng
eve-ng:
  Installed: 2.0.3-86
  Candidate: 2.0.3-92
  Version table:
     2.0.3-92 500
        500 http://www.eve-ng.net/repo xenial/main amd64 Packages
 *** 2.0.3-86 100
        100 /var/lib/dpkg/status
        
root@eve-lab:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  eve-ng eve-ng-qemu libdrm-amdgpu1 libdrm2 libgl1-mesa-dri linux-headers-generic linux-headers-virtual linux-image-virtual linux-virtual ubuntu-minimal
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
root@eve-lab:~#

root@eve-lab:~# apt-get upgrade eve-ng
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  libllvm4.0
Use 'apt autoremove' to remove it.
The following NEW packages will be installed:
  libcapnp-0.5.3 libdrm-common libegl1-mesa libgbm1 libllvm6.0 libmirclient9 libmircommon7 libmircore1 libmirprotobuf3 libprotobuf-lite9v5 libsdl2-2.0-0 libsndio6.1 libwayland-client0 libwayland-cursor0 libwayland-egl1-mesa
  libwayland-server0 libxcb-xfixes0 libxkbcommon0 libxss1
The following packages have been kept back:
  linux-headers-generic linux-headers-virtual linux-image-virtual linux-virtual ubuntu-minimal
The following packages will be upgraded:
  eve-ng eve-ng-qemu libdrm-amdgpu1 libdrm2 libgl1-mesa-dri
5 upgraded, 19 newly installed, 0 to remove and 5 not upgraded.
Need to get 127 MB of archives.
After this operation, 90.0 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

I was expecting 2.0.3-92..? There were no errors on install & I followed all steps according to your video, but I think I ended up w/ the exact same version I started with. After the install apt-get upgrade doesn't do anything anymore (see above output in code) and says eve-ng & some dependent packages are being 'kept back'... BUT if I do 'apt-get upgrade eve-ng' it looks ready to UG again. Because the instructions are very specific for upgrading I didn't want to do something wrong... Should I try 'apt-get upgrade eve-ng' or 'apt-get --with-new-pkgs upgrade'?

thanks,
Erik

Posted: **Sat Nov 03, 2018 8:02 am**

CSR Everest and Denali are supported from v92, please update your EVE
for everest and denali is integrated vmxnet3 driver in the eve
So dot1q will work

Posted: **Thu Nov 08, 2018 12:48 pm**

sorry for the late response but I had a couple of days off.. thanks so much for your help, I got eve upgraded just w/ 'apt-get upgrade eve-ng' which automatically installed any dependencies & now .1q works as advertised. Thanks again!

Support and News Forum

csr:everest:dot1q connectivity doesn't work

csr:everest:dot1q connectivity doesn't work

Re: csr:everest:dot1q connectivity doesn't work

Re: csr:everest:dot1q connectivity doesn't work

Re: csr:everest:dot1q connectivity doesn't work

Re: csr:everest:dot1q connectivity doesn't work

Re: csr:everest:dot1q connectivity doesn't work

Re: csr:everest:dot1q connectivity doesn't work