I would follow the Validated Solution Guides as a best-practice.
If template groups meet your requirements best, I don't see an issue using them for now. With the new configuration model, things indeed change, but also change from gui config; at one point in time you may need to convert your configuration anyway. If you need to design/setup a very large/complex network, and days/weeks/months will go in the rollout/testing, it may be good to work with your local account team and see what is wise to do at this moment and how to make sure that investments you do now in the configuration can be reused as much as possible in the future.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Apr 21, 2025 02:40 PM
From: ascott
Subject: Central Template Groups - Yes or No?
I'm doing a PoC of Central right now. 20 year Aruba customer and have used all their other products. Just recently logged into Central for basically the first time and have been navigating around. I am primarily interested in getting my CX and AOS switches moved to Central. I watched a few YT videos and they primarily show switches being managed with variables and template groups (TG).
My account team is recommending against TG because the migration to NextGen Central does not support TGs. I would just like to get the groups opinion on the best method to manage switches in Central. Any other things you would do different from naming standards, organization, etc....