ACS 5.8.1.4 eth issues

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
ip_warrior
Posts: 14
Joined: Tue Mar 28, 2017 5:22 pm

ACS 5.8.1.4 eth issues

Post by ip_warrior » Thu Apr 06, 2017 10:03 pm

Hi,
In the EVE-NG website says that ACS version 5.8.1.4 is supported.
I made all the procedures to install it on a VMware (creating a machine, install from ISO and so on), I converted the vmdk to qcow2 format and imported it to EVE-NG VM.
It's normally boots and start correctly, but in the console, when I tried to ping, I got a 'Network is unreachable' error. I connected the ACS node to a cloud and after to a IOU switch, but no luck.
The main point is that no interface is showing in output from 'show ip route'. In VMware VM, it's show correctly the eth0 as destination.
Please, can someone from EVE's Team check it?

ACS/admin# ping ip 192.168.0.1
% Error: connect: Network is unreachable
ACS/admin#
ACS/admin# sh ip route

Destination Gateway Iface
----------- ------- -----

ACS/admin# sh interface
GigabitEthernet 0
Link encap:Ethernet HWaddr 50:00:00:05:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:22658 errors:0 dropped:0 overruns:0 frame:0
TX packets:22658 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6289106 (5.9 MiB) TX bytes:6289106 (5.9 MiB)

ACS/admin# sh inventory

NAME: "UNSUPPORTED chassis", DESCR: "UNSUPPORTED chassis"
PID: UNSUPPORTED , VID: NA , SN: UNSUPPORTED
Total RAM Memory: 4054840 kB
CPU Core Count: 2
CPU 0: Model Info: QEMU Virtual CPU version 1.0
CPU 1: Model Info: QEMU Virtual CPU version 1.0
Hard Disk Count(*): 1
Disk 0: Device Name: /dev/sda
Disk 0: Capacity: 85.90 GB
Disk 0: Geometry: 255 heads 63 sectors/track 10443 cylinders
NIC Count: 1
NIC 0: Device Name: eth0
NIC 0: HW Address: 50:00:00:05:00:00
NIC 0: Driver Descr: Intel(R) PRO/1000 Network Driver

(*) Hard Disk Count may be Logical.
ACS/admin#

ramindia
Posts: 409
Joined: Sun Mar 19, 2017 10:27 pm

Re: ACS 5.8.1.4 eth issues

Post by ramindia » Fri Apr 07, 2017 7:06 am

Hi

I did not see any ip configured on below interface, configure ACS IP address

GigabitEthernet 0

R!

ip_warrior
Posts: 14
Joined: Tue Mar 28, 2017 5:22 pm

Re: ACS 5.8.1.4 eth issues

Post by ip_warrior » Fri Apr 07, 2017 2:48 pm

ramindia
If you played with ACS, you remember that after ACS's ISO installation, the setup needs the IP information for VM, like, IP, mask, Default Gateway, DNS and so on... This IP information is mandatory, you cannot skip this part.
The answer for you question is yes, I already configured an IP address, before made all of these tests.
And to be exactly, this ACS VM was working fine in VMware. In EVE-NG, the same VM was with that issues I already mentioned.

EVE-NG team, can someone check this? Or inform an specific trick that need to be set in?
Thanks in advance!

ecze
Posts: 533
Joined: Wed Mar 15, 2017 1:54 pm

Re: ACS 5.8.1.4 eth issues

Post by ecze » Fri Apr 07, 2017 3:17 pm

When you convert image, You may be in a situation of persistent Device ID/ Mac address.
So into the core os config files ( invisible for you ), the nic is not set because it appears as a new one for the system after conversion....
...
You need to clean your VM...

cd into directoty of your vm ( /opt/unetlab/addons/qemu/acs-5.8.1.4/

Code: Select all

apt-get install libguestfs-tools
guest-fish -a hda.qcow2
run
mount /dev/smosvg/rootvol /
vi /etc/udev/rules.d/70-persistent-net.rules
Delete all lines not commented
Vi commands are :
use arrow keys to choose a line
type twice on 'd' to delete current line

to save and exit: type: ":x!"

Code: Select all

unmount /
exit 

E.

ip_warrior
Posts: 14
Joined: Tue Mar 28, 2017 5:22 pm

Re: ACS 5.8.1.4 eth issues

Post by ip_warrior » Sat Apr 08, 2017 4:05 am

ecze
Thanks for you tip, but unfortunately the '70-persistent-net.rules' file was blank.

But I found the solution in an YouTube video! :D The trick is at video time 14:10
https://www.youtube.com/watch?v=SXXXAtPJh0s

You need to remove and put again the 'ip default-gateway' command!!! :roll:
After this, the eth0 shows in 'show ip route'.

badgerdog
Posts: 41
Joined: Tue Apr 11, 2017 2:03 am

Re: ACS 5.8.1.4 eth issues

Post by badgerdog » Tue Apr 11, 2017 2:32 am

I found that you need to remove and replace the ip default-gateway command EVERY time the ACS image is booted.... would be nice if there was a permanent solution to this problem.

2600
Posts: 36
Joined: Mon Mar 20, 2017 7:45 pm

Re: ACS 5.8.1.4 eth issues

Post by 2600 » Wed May 10, 2017 11:24 am

I can confirm that this is the persistent issue too.

jiggamaine
Posts: 8
Joined: Mon Mar 20, 2017 2:50 pm

Re: ACS 5.8.1.4 eth issues

Post by jiggamaine » Mon May 15, 2017 7:46 pm

Hi,

I got the interface to show an IP address but im getting the following errors when pinging to the gateway. It connected to a cloud connected to my network. i made sure it could connect by adding a 3725 router to the cloud and setting the ip of the 3725 to dhcp and it worked. Not sure what could be wrong. Help would be greatly appreciated.

ACS-LAB/admin# sh int
GigabitEthernet 0
Link encap:Ethernet HWaddr 50:00:00:01:00:00
inet addr:192.168.1.111 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::5200:ff:fe01:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:163 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14556 (14.2 KiB) TX bytes:1476 (1.4 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:22417 errors:0 dropped:0 overruns:0 frame:0
TX packets:22417 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7556638 (7.2 MiB) TX bytes:7556638 (7.2 MiB)

ACS-LAB/admin# ping ip 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.111 icmp_seq=1 Destination Host Unreachable
From 192.168.1.111 icmp_seq=2 Destination Host Unreachable
From 192.168.1.111 icmp_seq=3 Destination Host Unreachable
From 192.168.1.111 icmp_seq=4 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 6658ms

ecze
Posts: 533
Joined: Wed Mar 15, 2017 1:54 pm

Re: ACS 5.8.1.4 eth issues

Post by ecze » Mon May 15, 2017 8:57 pm


ip_warrior
Posts: 14
Joined: Tue Mar 28, 2017 5:22 pm

Re: ACS 5.8.1.4 eth issues

Post by ip_warrior » Sat Oct 05, 2019 4:13 am

Hello!

After two years and almost half, I was able to identify and fix this issue!
I tested in the 5.8.0.32 version but I suppose that it will work in other versions!
It may work when running ACS in Virtual Box too!
The problem is caused by a Linux script in the OS, that made permanent the mac address of the ethernet interface when running the ACS setup.
When you follow the procedures below, you will be activating this script again when booting the ACS, it will fill the new mac address of the current eth0 interface.

Follow the procedures in the ssh shell of the EVE-NG:

cd /opt/unetlab/addons/qemu/acs-5.8.0.32/
guestfish -a hda.qcow2
run
mount /dev/sda3 /
vi /startup-config-1570067776/etc/sysconfig/network-scripts/ifcfg-eth0
delete the line that contains "HWADDR=" using the cursor and deleting the line with the command "dd" (type d two times)
save the file in vi using the commands: ":qw" and hit enter
umount /
exit

Start you ACS image and voilá! :D

I recommend to do this in the ACS base image!

Can someone from the EVE-NG admin team, put this information into the ACS how to? Thank you!

Post Reply