I actually got VXLAN working between 2 x 4431s in the end, regardless of
what the Cisco site said. I guess what they mean is, "it will work on the
4431 but we will not support it". It's actually a cool protocol/feature,
works well and fails over fast.
On Sun, 9 Dec 2018 at 14:40, Richard
Changed my lab to VXLAN only to find its not supported on the 4431, only
supported on the 4451. It lets you put all the commands in but doesn't
work, why do Cisco do that to us, surely just remove the commands when
there is no support for it?
Config snippet from both routers
CE R1
interface GigabitEthernet0/0/3
description POP1-CE02 3750SW-1
mtu 1600
no ip address
media-type rj45
negotiation auto
service instance 1 ethernet
description L2 Extension LAN
encapsulation dot1q 229,232
xconnect 100.66.50.110 100 encapsulation
Hi Guys
I have two main sites, HQ and DR, the site has layer 2 p2p between them and
a 4431 on each for the WAN. They want layer two backup over the 4431 WAN
circuits for their existing layer 2 p2p.
I have tested L2TPV3 xconnect inside LAN facing Service Instance, the
L2TPV3 session establishes,
