IBNs v2 back to legacy

[royce.varughese.1984]

Is there any way to go back from C3PL to legacy style? 

Is write erase, reload with backup config only method? Wanted to test config for few ports but i completly ignored the message clearly shown on CLI and copy and pasted a whole bunch of class policy command which converted everything "authentication" to new style and also thousands of line in to config 

[MHM Cisco World]

• Enter the authentication display new-style command—This command switches to C3PL display mode, temporarily converting your legacy configuration to a Identity-Based Networking Services configuration so you can see how it looks before you make the conversion permanent. You can switch back to legacy mode by using the authentication display legacy command. See the Enabling the Display Mode for Cisco Identity Based Networking Services section.

• Enter a Identity-Based Networking Services configuration command—After you enter the first explicit Identity-Based Networking Services command, the configuration converts to C3PL display mode permanently and legacy commands are suppressed. The authentication display command is disabled and you can no longer revert to the legacy configuration mode.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9200/software/release/17-14/configuration_guide/sec/b_1714_sec_9200_cg/configuring_identity_control_policies.html

read this carefully 

MHM

[royce.varughese.1984]

I am trying my way back, i cant keep config on new style as that is not what was agreed in our design and i was testing for a docking station that way not letting authentication happen.. and we noticed on SDA with the new style of config same dock and connected clients work fine..

[royce.varughese.1984]

This is where i should have paused.. instead i marched as if i am on a battle field

[MHM Cisco World]

You are correct 
cisco push engineer to use IBN2.0 but many find it so complex and from my view keep using legacy it better and easy to config 

MHM

[royce.varughese.1984]

oh this was not cisco.. it was a self engineered mistake without really understanding consequence of what i could end up with.. 

https://community.cisco.com/t5/network-access-control/switching-from-ibns2-0-to-ibns1-0/td-p/4182757

found above which to me is complex and going back to customer at this stage when site is expected to go live wont help.. 

[MHM Cisco World]

I am honest with you I prefere legcay 
https://youtu.be/Bc7xQUdL_XU?si=7hF7Y5DwddqTNiog

MHM

[royce.varughese.1984]

Agreed should have been careful but now i need find a way to revert to legacy style with minimal damage.. if anyone knows ways or used some let me know.. meanwhile let me figure a way out to present the mess i have created