Cisco Bug: CSCsz82147 - Validation required for modify fex max pinning links xml delivery -
Apr 22, 2014
- Cisco Nexus 5000 Series Switches
- Cisco Nexus 5020 Switch
- Cisco Nexus 5010 Switch
Known Affected Releases
Symptom: 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. <CmdBold> 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. </CmdBold> 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. Conditions: 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 Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases