# Cisco SD-WAN vSmart CLI Template
**URL:** https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041
**Category:** Lessons Discussion
**Created:** [August 2, 2021, 6:42pm UTC](https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041 "2021-08-02T18:42:31Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@ReneMolenaar](https://forum.networklessons.com/u/ReneMolenaar)
#### Post date: [August 2, 2021, 6:42pm UTC](https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041/1 "2021-08-02T18:42:31Z")
This topic is to discuss the following lesson:
> **[Cisco SD-WAN vSmart CLI Template](https://networklessons.com/cisco/ccie-enterprise-infrastructure/cisco-sd-wan-vsmart-cli-template)**
>
> This lesson explains how to solve the vSmarts are not in vManage mode error by attaching a CLI Template to your vSmart controller.
---
### Author:  [@jeromypolachak](https://forum.networklessons.com/u/jeromypolachak)
#### Post date: [February 22, 2022, 6:25pm UTC](https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041/2 "2022-02-22T18:25:20Z")
When trying to do this in a lab I am getting the error:
`Device failed to process request. Error type : application Error tag : access-denied`
I have googled the error but the fix about removing the ciscotacro and ciscotacrw couldn’t be done as well
```auto
vSmart(config-aaa)# no user ciscotacro group operator
Error: access denied
```
---
### Author:  [@lagapidis](https://forum.networklessons.com/u/lagapidis)
#### Post date: [February 24, 2022, 7:01am UTC](https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041/3 "2022-02-24T07:01:02Z")
Hello Jeromy
After doing some research, I have found that this seems to be a bug that appears occasionally. [Some bug reports](https://quickview.cloudapps.cisco.com/quickview/bug/CSCvu69248) do indeed suggest the fix you mentioned, while [others](https://quickview.cloudapps.cisco.com/quickview/bug/CSCvr41899) state that it has to do with a manually configured `ip routing` command on the vEdge. These involve releases 17.3.1 20.3 20.3.1 20.4 20.4.1, and cEdge-16.10.1 respectively. Rene used version 19.3.0 in his lessons.
The only thing I can suggest is to see if you can obtain the same version as Rene to duplicate his implementation. Otherwise, you can troubleshoot using Cisco TAC (if this is a production network) or other workarounds posted online.
Let us know how your troubleshooting comes along!
I hope this has been helpful!
Laz
---
### Author:  [@gogosb](https://forum.networklessons.com/u/gogosb)
#### Post date: [August 8, 2022, 3:03pm UTC](https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041/4 "2022-08-08T15:03:02Z")
Hi Jeromy,
The same at my side. You can solve it if you delete the ciscotacro and ciscotacrw from the template. It is not supported now:
> **[Bug Search Tool](https://quickview.cloudapps.cisco.com/quickview/bug/CSCvu69248)**
---
### Author:  [@cylemmulo](https://forum.networklessons.com/u/cylemmulo)
#### Post date: [December 30, 2022, 8:37pm UTC](https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041/5 "2022-12-30T20:37:06Z")
I concur I had this same problem with version 20.3.2. Just went to the copied config and deleted the ciscotacro and ciscotacrw accounts from it.
---
### Author:  [@roger.correadantas](https://forum.networklessons.com/u/roger.correadantas)
#### Post date: [June 13, 2023, 11:53pm UTC](https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041/6 "2023-06-13T23:53:15Z")
It worked here too, by removing the lines below from the created template:
> user ciscotacro
> description CiscoTACReadOnly
> group operator
> status enabled
> !
> user ciscotacrw
> description CiscoTACReadWrite
> group netadmin
> status enabled
> !
---
### Author:  [@sathish84be](https://forum.networklessons.com/u/sathish84be)
#### Post date: [November 21, 2024, 8:35pm UTC](https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041/7 "2024-11-21T20:35:53Z")
Hello @cylemmulo
i did the same but still getting same error.
---
### Author:  [@lagapidis](https://forum.networklessons.com/u/lagapidis)
#### Post date: [November 25, 2024, 5:16am UTC](https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041/8 "2024-11-25T05:16:40Z")
Hello Sathish
It sounds like a frustrating issue, as you can see from previous posts, you’re not alone in encountering it! Based on what’s been shared in this thread, many users have resolved this problem by removing the `ciscotacro` and `ciscotacrw` accounts from their templates, as these are no longer supported.
If you’ve already done this and still face the error, here are a few additional troubleshooting suggestions:
- Check the Bug CSCvu69248: Ensure that your software version is compatible and doesn’t have known issues [mentioned in this post](https://forum.networklessons.com/t/cisco-sd-wan-vsmart-cli-template/15041/4), beyond what’s already mentioned.
- Validate the template syntax: If you’re editing via a template, ensure there are no syntax errors or missing mandatory commands.
- Use direct device CLI: Try applying the change directly on the device CLI to verify whether the issue is related to the template or vManage.
- Check for lingering configurations: On the device, ensure there are no residual references to ciscotacro or ciscotacrw.
Let us know how it goes, or if you’ve tried these steps already, we can explore further!
I hope this has been helpful!
Laz