Support and News Forum

Hello all, first post here. I checked through the help-desk posts and didnt notice any posts with the same issue.

I am able to ping all nodes contained within the lab from the Eve-ng console. I can ping the eve-ng management address, login, update, etc without issue. I can ping the eve-ng management address from the nodes in the lab, I can bridge from the real network to the lab nodes. I created the cloud interface

Switch#ping 192.168.128.
*Apr 5 02:04:04.016: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet0/3 (not full duplex), with WLC GigabitEthernet1 (full duplex).25
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.128.25, timeout is 2 seconds:
!!!!!

root@EVE:/opt/unetlab/addons/qemu/viosl2-adventerprisek9-m.03.2017# ping 192.168.128.1
PING 192.168.128.1 (192.168.128.1) 56(84) bytes of data.
64 bytes from 192.168.128.1: icmp_seq=1 ttl=64 time=0.639 ms
64 bytes from 192.168.128.1: icmp_seq=2 ttl=64 time=0.420 ms
^C
--- 192.168.128.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1007ms
rtt min/avg/max/mdev = 0.420/0.529/0.639/0.111 ms
root@EVE:/opt/unetlab/addons/qemu/viosl2-adventerprisek9-m.03.2017# ping 192.168.128.25
PING 192.168.128.25 (192.168.128.25) 56(84) bytes of data.
64 bytes from 192.168.128.25: icmp_seq=1 ttl=64 time=0.035 ms
64 bytes from 192.168.128.25: icmp_seq=2 ttl=64 time=0.034 ms
v64 bytes from 192.168.128.25: icmp_seq=3 ttl=64 time=0.029 ms
c64 bytes from 192.168.128.25: icmp_seq=4 ttl=64 time=0.042 ms
^C
--- 192.168.128.25 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3054ms
rtt min/avg/max/mdev = 0.029/0.035/0.042/0.004 ms
root@EVE:/opt/unetlab/addons/qemu/viosl2-adventerprisek9-m.03.2017# ^C
root@EVE:/opt/unetlab/addons/qemu/viosl2-adventerprisek9-m.03.2017# ping 192.168.128.26
PING 192.168.128.26 (192.168.128.26) 56(84) bytes of data.
64 bytes from 192.168.128.26: icmp_seq=1 ttl=255 time=80.3 ms
64 bytes from 192.168.128.26: icmp_seq=2 ttl=255 time=18.7 ms
64 bytes from 192.168.128.26: icmp_seq=3 ttl=255 time=24.8 ms
^C
--- 192.168.128.26 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 18.702/41.300/80.334/27.715 ms
root@EVE:/opt/unetlab/addons/qemu/viosl2-adventerprisek9-m.03.2017# ping 192.168.128.245
PING 192.168.128.245 (192.168.128.245) 56(84) bytes of data.
64 bytes from 192.168.128.245: icmp_seq=1 ttl=255 time=31.4 ms
64 bytes from 192.168.128.245: icmp_seq=2 ttl=255 time=8.53 ms
^C
--- 192.168.128.245 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 8.538/20.003/31.469/11.466 ms
root@EVE:/opt/unetlab/addons/qemu/viosl2-adventerprisek9-m.03.2017#

if you got success your vIOS Switch connectivity over Cloud to real device, then it is more than enough.
Those other pings you are showing from EVE itself are not in use at all.

In your output vIOS crys about duplex mismatch, so correct it on vIOS switch port facing to WLC, adding duplex full on interface.

Depends where is EVE VM installed, you can have L2 on ESXI or L3 with VM ware workstation connection to real device.
Esxi require to allow promiscue mode.
By the way it is all described in our cookbook.
Section networking.
EVE Pro book, section 10
https://www.eve-ng.net/index.php/docume ... -cookbook/

Eve Community book:
https://www.eve-ng.net/index.php/docume ... -cookbook/
Section 9

Uldis
P.S. On VM workstation L2 connection is possible as well.
vIOS SW---cloud---real sw (trunk !
But need intervent in windows registry allow promiscue mode.

I tried to fix the duplex prior to posting with no luck. That ping was from a 9800 controller. Eve is installed on ESXI v6.5 on a Dell server. I cant figure out how to put the nic into promiscuous mode. I am not seeing that option

In the cookbook is given how to enable promiscue mode, check eve community book section 9.2

This is really weird, I can hit everything from EVE-NG to my network but not vice-versa. I read the cookbook, but this is really odd.
I am also seeing this:
Apr 6 13:26:14.731: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet0/3 (not full duplex), with WLC GigabitEthernet1 (full duplex).conf
t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#int gi0/3
Switch(config-if)#du
Switch(config-if)#duplex fu
Switch(config-if)#duplex full
Autoneg enabled. Duplex cannot be set

Switch(config-if)#no du
Switch(config-if)#no duplex au
Switch(config-if)#no duplex auto
Autoneg enabled. Duplex cannot be set


Any thoughts?

ok, forget the last comment. I can hit it.

I have 2 networks at my home, 192.168.0.0/24 & 192.168.1.0/24. The VMware network is on 192.168.0.0/24 and I am on 192.168.1.0/24. Ive been trying to hit the devices in my lab but havent been able to ping them. It looks like I need to add a route somewhere. I am currently able to access both network so routing on my home network is fine, I guess I need to understand where I have to add a route back from the Eve-ng network

the best way to discuss such things is our live chat ear..
you posting a lot info and but it still missing a lot to answer correctly..

use our live chat:
https://www.eve-ng.net/index.php/live-helpdesk/
use gmail to join

it will be better contact with eve experts in there