Cisco Bug: CSCvu36778 - [MTS] NDB doesn't respect nx.flows.batch.size setting when removes stale flow entries
Aug 04, 2020
- Cisco Nexus Data Broker
Known Affected Releases
Symptom: Following logs are seen: INFO com.cisco.csdn.monitor.internal.NDBFlowLayerManager:default - Removing stale source flows for node <...> followed by WARN com.cisco.csdn.protocol_plugin.nxapi.service.internal.ElementServices - Invalid response null for device NetworkElement [address=XXX, port=443, protocol=https] for cmds [ <...> ] due to Read timed out. Conditions: When NDB applies configuration updates on the switches in NX-AP mode, update is usually divided in batches, [nx.flows.batch.size] (default 60) per batch. But if NDB upgraded to 3.9 performs stale entries removal (seen because of software defect in 3.8), updates are pushed in one huge batch.
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