Contrail version seeing this issue: 3.2.8.0-66.
MetaSwitch Perimeta VOIP VNF fails to send traffic to vRouter in DPDK mode when the “Mergeable buffer” is turned on/introduced in 3.2.8.0. Previous releases work fine due to no support of Mergeable buffer feature.
The Perimeta VNF does not have any features it uses for QEMU 2.5 to pass to the vRouter (see guest features below). When the vRouter restarts, Perimeta sends 0x0 code to the vRouter, but we are expecting anything other than 0x0. 0x0 is specifically used to handle a qemu reconnect case when the dpdk vrouter application is restarted.
Juniper BU said we didn’t expect VNF’s NOT to use any features and hence we turned mergeable buffer on. Action Item on Juniper BU(Raja) to research is if there is any way to unblock them since upgrading Perimeta code which supports Mergeable buffer will derail their timelines and expense on ECOMP.
There are apparently other VOIP VNF’s which are also going to be affected….not yet sure which ones.
#define VIRTIO_PMD_DEFAULT_GUEST_FEATURES \
(1u << VIRTIO_NET_F_MAC | \
1u << VIRTIO_NET_F_STATUS | \
1u << VIRTIO_NET_F_MQ | \
1u << VIRTIO_NET_F_CTRL_MAC_ADDR | \
1u << VIRTIO_NET_F_CTRL_VQ | \
1u << VIRTIO_NET_F_CTRL_RX | \
1u << VIRTIO_NET_F_CTRL_VLAN | \
1u << VIRTIO_NET_F_CSUM | \
1u << VIRTIO_NET_F_HOST_TSO4 | \
1u << VIRTIO_NET_F_HOST_TSO6 | \
1u << VIRTIO_NET_F_MRG_RXBUF | \
1u << VIRTIO_NET_F_MTU | \
1u << VIRTIO_RING_F_INDIRECT_DESC | \
1ULL << VIRTIO_F_VERSION_1 | \
1ULL << VIRTIO_F_IOMMU_PLATFORM)
Review in progress for https:/
Submitter: Jeya ganesh babu (<email address hidden>)