Hello Community,
I have a question about the Critical Pool in SDA.
In the old days, creating a Critical Pool on DNA resulted in VLAN 2047 being configured with this subnet, and that VLAN 2047 got hardcoded in interface templates as the default data access VLAN.
All very clear and usable!
Now when I configure Critical Pool in DNA 2.2.2.4 (and I don’t enter any VLAN number) the result is a random VLAN (1027 in my case).
This VLAN is not configured as the default in interface templates, data access vlan remains unconfigured so results in VLAN 1 (where Voice is still using 2046)
However there is now a “policy-map control” process (not sure how to call this) that makes sure endpoints end up in Critical ONLY when AAA is dead, so yes it works.
Are my conclusions correct? What is the reason for this significant change?
This broke our “defaultpermit/profiling” setup
Regards Kristof
