Guest

Preview Tool

Cisco Bug: CSCus48680 - Dao : veth with dvport id not coming up as expected after upgrade

Last Modified

Feb 02, 2017

Products (1)

  • Cisco Nexus 1000V Switch for VMware vSphere

Known Affected Releases

5.2(1)SV3(1.2.96)

Description (partial)

Symptom:
User will Not be able to use manually created veth.

Conditions:
Below conditions are seen when we hit this issue.
---------------------------------------------------------------------
1)  Vethernet should be manually created on VSM.
2)  Vethetnet should have vmware dvport configuration.
example :
CY-P2# sh run int vethernet 100

!Command: show running-config interface Vethernet100
!Time: Tue Jan 13 07:48:29 2015

version 4.2(1)SV2(2.2)

interface Vethernet100
  vmware dvport 670
  no shutdown

3) Issue is seen after upgrade. where before upgrade we were not using the manually created Vethenet (but we had configuration in VSM) and Post upgrade we are trying to use it .
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.