Preview Tool

Cisco Bug: CSCur66534 - Unable to add VM Nics to vEthernets after upgrade to 3.1.1

Last Modified

Sep 09, 2019

Products (3)

  • Cisco Nexus 1000V Switch for VMware vSphere
  • Cisco Nexus 1000V Switch
  • Cisco Application Virtual Switch

Known Affected Releases


Description (partial)

Recreate steps:

Nexus 1000v version 4.2(1)SV2(2.2) ha pair

1.	Manually create vEthernet with next available sequential number on VSM
interface vethernet10
  			vmware dvport 105
  			no shutdown
2.	Upgrade the Nexus 1000v to version 5.2(1)SV3(1.1)
        a.	Vethernet will get configurations added automatically
               i.	storm-control broadcast 0 pps 

                     interface Vethernet10
  		         vmware dvport 105
  		         storm-control broadcast 0 pps
  		         storm-control broadcast 0 pps
 	 	         storm-control broadcast 0 pps
  		         no shutdown
3.	End user cannot assign VM nics to this Vethernet by dvport (advanced settings)
          a.	Unable to assign dvport ID/vEthernet pair in vCenter to VM NICs
          b.	A new vEthernet is created instead
4.	Workaround
         a.	Remove the vEthernet and then add the vethernet back to the VSM as in step 1 before assigning the dvport/vethernet pair in vCenter.

Bug details contain sensitive information and therefore require a 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.