Skip to content

Fix FX3 memory query filter limit on large fabrics - #428

Merged
monrog2 merged 1 commit into
v4.2.0-devfrom
issue-423-fx3-memory-filter-limit
Aug 18, 2026
Merged

Fix FX3 memory query filter limit on large fabrics#428
monrog2 merged 1 commit into
v4.2.0-devfrom
issue-423-fx3-memory-filter-limit

Conversation

@monrog2

@monrog2 monrog2 commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • replace the per-FX3-node APIC filter with one constant-size procMemUsage query
  • filter the below-32GB response locally against the affected FX3 node IDs already present in fabric_nodes
  • add regression coverage for 55 affected nodes and for excluding low-memory non-FX3 switches

Validation

  • python3 -m pytest tests/checks/n9k_c93180yc_fx3_switch_memory_check/test_n9k_c93180yc_fx3_switch_memory_check.py (7 passed)
  • python3 -m pytest (1004 passed)
  • GitLab integration pipeline 208, actual-current-version job 698: scale1 completed with 104 fabric nodes and 52 affected FX3 nodes; the constant-size query returned 7 below-threshold supervisor records, none from affected FX3 nodes; the check passed with no APIC 301/filter-expression-limit error

Fixes #423

@monrog2
monrog2 merged commit 2775613 into v4.2.0-dev Aug 18, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant