Cisco Bug: CSCur06678 - Restriction on HIF storm control isn't clear
Mar 09, 2017
- Cisco Nexus 6000 Series Switches
Known Affected Releases
Symptom:There is a specific restriction for HIF storm control: - Applying storm control over a HIF range is not recommended. The configuration might fail for one or more interfaces in the range depending on the hardware resource availability. The result of the command is partial success in some cases. (http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus6000/sw/layer2/7x/b_6k_Layer2_Config_7x/b_6k_Layer2_Config_7x_chapter_01101.html#con_1086245) Further information is required on how this restriction works. For each port that is configured with storm-control , 3 storm policers are allocated by AFM, each for broadcast/multicast/unicast levels. For Ethernet ports , the policers are statically allocated by AFM. But for HIF ports, the storm policers are dynamically allocated by LIBAFM/AFM on request from FWM. Conditions: In a scaled setup when multiple HIF ports from multiple FEXs( in a range ) are requesting for storm policers to AFM, due to heavy load on AFM, there are few timing issues seen in handling the requests. Hence it is recommended to apply storm control configs on small chunks of HIF port ranges (may be one FEXs HIF ports at a time in a range).
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