Preview Tool

Cisco Bug: CSCvu36778 - [MTS] NDB doesn't respect nx.flows.batch.size setting when removes stale flow entries

Last Modified

Aug 04, 2020

Products (1)

  • Cisco Nexus Data Broker

Known Affected Releases


Description (partial)

Following logs are seen:
INFO - Removing stale source flows for node <...>

followed by
WARN - Invalid response null for device NetworkElement [address=XXX, port=443, protocol=https] for cmds [ <...> ]  due to Read timed out.

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 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.