VRRP for Cisco vEdge cloud is not supported on E1000 and VMXNET3 I/O types from 18.3 version onwards. [CSCvn53200/VIP-48217]

[atsaya2512]

Hi,

Please help us to clarify what type of network adapter supports the VRRP configuration in Cisco vEdge router, as we came across a document stating "VRRP for Cisco vEdge cloud is not supported on E1000 and VMXNET3 I/O types from 18.3 version onwards. [CSCvn53200/VIP-48217]", which is listed below Outstanding Issues > Forwarding part. Our ESXi version is 5.5 build 2, vEdge version 18.4.0 and the link we referred is https://sdwan-docs.cisco.com/Product_Documentation/Software_Features/Release_18.4/Release_Notes/Release_Notes_for_IOS_XE_SD-WAN_Release_16.10_and_SD-WAN_Release_18.4

It would be great if someone can help us in this regards. 

Thanks in advance.

Regards

Akchaiah

[stefan.radovanovici]

We've hit the same issue. The answer was that is indeed not supported at all on the vedge-cloud starting with 18.3 until further notice, on any type of adapters. The official "workaround" is to use hardware vedges. 

[ekhabaro]

or you can use 17.2.10 vEdge-Cloud. Honestly speaking, VRRP in the virtualized environment is bad idea (certainly debatable) because you should provide redundancy on hypervisor level, not on the VM level with "stateless" VRRP (and it's waste of resources as well IMO),

[Joe-Jose]

Hope you have upgraded the version. ? 18.4.1 software vedge works fine with VRRP. but you need to have E1000 interface. VMXNET3 interface will give an error "Virtual mac address cannot be created".

[ekhabaro]

No, it's not fixed in 18.4.1 as far as I know, it won't give us warning for E1000 interface, this is the only difference. Joe, can you ping VRRP address with 18.4.1 software actually? I see two enhancement requests opened for that issue and CSCvn53200/VIP-48217 is not fixed.
If you really need VRRP, the best option will be to chase your account team and ask for support of this feature.

[Joe-Jose]

Hi ekhabaro,

I didnt realize that this is even a bug, when i started configuring VRRP , it was giving a message "Addition of virtual mac address not supported on this device on interface". But then i changed the adapter type from VMXNET3 to E1000 using Vmware powershell. Then the configuration was successfull.

I was able to ping even.

vEdge01# ping vpn 30 10.50.0.6
Ping in VPN 30
PING 10.50.0.6 (10.50.0.6) 56(84) bytes of data.
64 bytes from 10.50.0.6: icmp_seq=1 ttl=64 time=0.008 ms
64 bytes from 10.50.0.6: icmp_seq=2 ttl=64 time=0.013 ms
64 bytes from 10.50.0.6: icmp_seq=3 ttl=64 time=0.019 ms

But strangely, since you asked whether, i was able to ping, i tried from all of the nodes and it looks like you are absolutely right about it, i am not able to ping from all of the vEdge participating in VRRP. If its a known issue, i better wait for it be fixed.

Thanks for your reply.

[atsaya2512]

Thanks a ton Joe-Jose, I'm able to configure VRRP after changing the adapter type to E1000. Will wait for the official fix.