Guest

Preview Tool

Cisco Bug: CSCvt12098 - vedge cloud 18.4.3/19.2.1 on top of NFVIS(3.12.3 RC4) stop fowarding traffic when CU flap interface.

Last Modified

Oct 04, 2020

Products (2)

  • Cisco vEdge Router
  • Cisco vEdge Router Model

Known Affected Releases

18.4 19.2.1

Description (partial)

Symptom:
Customer has vedge cloud 19.2.1 on top of NFVIS(3.12.3 RC4).

vEdge cloud ge0/0 under vpn0 gets it ip address via DHCP.
vEdge cloud ge0/0 is mapped to SRIOV port on NFVIS gi0/0.
vEdge cloud ge0/1 is assigned static ip address and mapped to NFVIS GI0/1 (SRIOV)
Vedge forms controll connections via both the paths via gi0/1 and gi0/0.

The question or the issue is when we shut and not shut the NFVIS Ge0/0 port or Gi0/1 port, Vedge stops forwarding the packets even after the interface come back up, the control connections stay down, DHCP address address is not learnt again on Gig0/0 interface, Can not ping the gateway via Ge0/1 where the ip address is statically assigned.

We do not see the issue when there is physical fiber pull.

Work around is to do a shut and no shut of the interface on vedge, and all the control connections recover.

I did try with vEdge version 18.4.302/ 18.4.3 as well and same result.
May be this is related to DPDK/SRIOV Gig drivers on vedge towards i350 NFVIS WAN NIC.

Conditions:
vedge cloud 19.2.1 on top of NFVIS(3.12.3 RC4)
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.