Preview Tool

Cisco Bug: CSCsz82147 - Validation required for modify fex max pinning links xml delivery -

Last Modified

Apr 22, 2014

Products (3)

  • Cisco Nexus 5000 Series Switches
  • Cisco Nexus 5020 Switch
  • Cisco Nexus 5010 Switch

Known Affected Releases


Description (partial)


When a FEX uplinks are part of a portchannel members, then the pinning max-link can only be "1". And it can not be modified. But, when the configuration is performed via DCNM, device accepts any value.

fex 100
 pinning max-link 1

interface port-channel 10
   switchport mode fex-fabric
   fex associate-id 100
   no shut

fex 100
   pinning max-link 2 >>>>>>> This command will result in error in the CLI. 

But the same command executed via XML ( via DCNM ), succeeds in the device. And device does not throw any error. Because, of this DCNM will assume that the pinning has changed in the device, and it will start showing the newly configured value in GUI.


When user configures a fex pinning max-links value to other than 1 ( eventhough the FEX uplinks are part of a port channel ), DCNM allows it.
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.