The documents explicitly mention an upgrade from 2.1.2.7 to 2.2.2.9, and the issue is observed post-upgrade on the 3-node DNAC running 2.2.2.9. The problem description and configuration context directly reference this version as the current software in use.
The principal software version discussed is 2.2.2.9, as the issue arises after upgrading to this version and the configuration行为 is tied to its behavior.