vEdge can't be reached

[osamahq]

In an EVE-NG lab, I have connected a vedge directly to a 7200 router and configured both interfaces facing each other on the same subnet 10.10.10.0/24. the vedge needs to reach out of this network to reach the controllers in a different network, but I cant manage to get it to reach the the router connected directly to it.

subnet 10.10.10.0/24 can reach the controllers from the 7200 router.

the following is the config I added to the vedge

host-name vEdge
system-ip 11.11.11.11
site-id 2
organization-name lab
vbond 192.168.11.13

vpn 0
interface ge0/0
ip address 10.10.10.2/24
tunnel-interface
encapsulation ipsec
allow-service all
no shutdown
ip route 0.0.0.0/0 10.10.10.1

[osamahq]

as mentioned, vbond is already reachable from this subnet

internet#ping 192.168.11.13 source 10.10.10.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.11.13, timeout is 2 seconds:
Packet sent with a source address of 10.10.10.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/31/32 ms

but vedge can't reach anything

vEdge# ping 192.168.11.13
Ping in VPN 0
connect: Network is unreachable
vEdge# ping 10.10.10.1
Ping in VPN 0
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
^C
--- 10.10.10.1 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1000ms

[Flavio Miranda]

Hi

If you have vrf, try to ping with VRF

ping vrf x "ip"

and try to add a route outside VPN0.

ip route 0.0.0.0/0 10.10.10.1

[osamahq]

no vrfs on the 7200 router.. for the vedge, the route and the interface are obviously under vpn0

[Flavio Miranda]

I meant cEdge no 7200.

"obviously under vpn0"

Obviously for overlay and control connection but if you dont have communication on the underlay, you can't build the overlay. 

[osamahq]

I'm talking about a vedge not a cedge.. a vedge only takes interface and ip route config under vpn.

under global config:

vEdge(config)# ip route?
^
% Invalid input detected at '^' marker.

[Flavio Miranda]

vEgde and cEdge is the samething.  Viptela does not exist anymore, now is Cisco.  But it is noly terminology.

[osamahq]

there is a difference but that doesn't help me with my main question

[Flavio Miranda]

Alright then. Best of luck. 

[osamahq · Accepted solution]

There simply was a connectivity issue