An AI network agent prepares a change to a Catalyst 9300 switch stack: more ACL entries, more routed ports, a new stack member, a license change or StackPower. Describe the stack and the change below, and the validator checks it against the limits in Cisco’s public Catalyst 9300 data sheet and the customer’s own change policy. It returns a verdict and every reason at once.
Scope: Cisco Catalyst 9300 Series stacks (C9300, C9300X, higher-scale C9300 and fixed-uplink C9300L). See everything this validator covers
Any case, not just these samples. The validator handles any change to a Catalyst 9300 stack that touches the rules below, in any combination.
What it checks
Scale limits: ACL entries after the change (5,120 on C9300 and C9300L, 8,000 on C9300X, 18,000 on higher-scale models); 1,000 switched virtual interfaces; routed ports per stack (448, or 416 for C9300L)
Stacking: up to 8 members; a fixed-uplink C9300L does not stack with modular-uplink C9300 models; higher-scale models stack only with other higher-scale models; all members share one license level
StackPower: up to 4 switches, or 8 with the XPS-2200, on modular-uplink C9300 and C9300X only
Totals the agent states (ACL entries, routed ports, stack size) compared with the validator’s own arithmetic
Needs approval: a C9300 and a C9300X in one stack (Cisco does not publish the mixed-stack scale limits), and two customer-policy inputs, a change freeze and a missing change ticket, which are the customer’s rules, not Cisco facts
Not in this validator today
Which features need which license tier, and minimum IOS XE releases (Cisco’s data sheet is inconsistent there)
MAC address scale, power budgets and other data-sheet entries
Other Catalyst families, and live device state or telemetry; the stack inventory is what you enter
Cisco’s data sheet says any combination of 9300 models can form a stack, which contradicts its own stacking table; this validator follows the specific table rules
ReadyThe validator is called when you click Check this change.
1. Pick a sample or fill in the form
A sample only fills in the form. Nothing is sent until you click Check this change.
2. The stack and the proposed change
Leave a number blank when the change does not touch it.
Stack inventory (from the customer’s network inventory)
ACL entries
Switched virtual interfaces and routed ports
Adding switches to the stack
License change and StackPower
Customer policy (the customer’s rules, not Cisco facts)
Sources and what is not modeled
Cisco Catalyst 9300 Series Switches data sheet (updated September 23, 2026), scale and stacking tables: ACL scale, 1,000 SVIs, routed ports per stack, stack size, which models may stack together, one license level per stack, and StackPower limits.
Cisco blog post on AgenticOps Trusted Validation (February 10, 2026): used for positioning only. It describes evaluating proposed changes before execution; this validator checks the request itself against the published limits and does not replace it.
Not modeled: feature-to-license mapping, minimum IOS XE release (the data sheet is inconsistent), MAC address scale, and the scale of a mixed C9300 and C9300X stack (Cisco does not publish it, so the validator asks for approval).
Customer-supplied, not Cisco facts: the stack inventory and counts, license level, change freeze and change-ticket requirement.