Preview Tool

Cisco Bug: CSCtf07382 - Port-profile FSM gets stuck while processing interface adds

Last Modified

Mar 16, 2016

Products (2)

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

Known Affected Releases


Description (partial)


VEM uplinks are coming up as access ports even though in the CLI it shows the Ethernet ports associated with the module as inheriting the correct port-profile.


Steps to reproduce:
1. Let Eth3/2 and Eth3/3 inherit profiles P1 and P2 resp.
2. VEM stop (module 3)
3. On vCenter, swap the port-groups for the 2 uplink ports
4. VEM start (module 3)
You will observe that FSMs of profiles P1 and P2 are now stuck in adding
interface state (use 'show port-profile internal info') and the Eth
ports are access & in down state.
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.