Preview Tool

Cisco Bug: CSCvv33533 - After reboot vEth interfaces are not programmed due to deadlock

Last Modified

Sep 21, 2020

Products (1)

  • Cisco Unified Computing System

Known Affected Releases


Description (partial)

When rebooting fabric interconnect you may see FSM processes stuck and no other configuration will take place. These are possible tasks that might be a sign of the issue.

Description: [FSM:STAGE:RETRY:]: Wait for border ports configuration completion on primary fabric interconnect (FSM-STAGE:sam:dme:ComputePhysicalAssociate:WaitForBorderConfigCompletionLocal)


Uplink eth port configuration on X(FSM:sam:dme:SwEthLanBorderDeploy)

Vlan group configuration on X(FSM-STAGE:sam:dme:SwEthLanBorderDeploy:UpdateVlanGroups)

This will cause anything pending to wait indefinitely for this process to complete. vEth interfaces may not get programmed until the FSM deadlock condition has been resolved.

Rebooting fabric interconnect or joining new fabric interconnect to cluster

This is usually seen when UCSM is on a different version than fabric interconnect
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.