How to add static route to cedge router managed via vmanage

[Sw000976]

I have a cedge router that is managed via vmanage and I am trying to add a static route via the cli and get this: 

Aborted: 'system is-vmanaged': This device is being managed by the vManage. Configuration through the CLI is not allowed.
Error executing command: CLI command error -

Which logically makes sense to me as then the local config would not match the template in vmanage. But when I start looking at the template I dont actually see any routes defined? So not sure how to get this done? 

[Torbjørn]

Hello @Sw000976, welcome to the community!

You can define static routes in the VPN feature template on vManage. Keep in mind that this will affect all edges with that template attached, so you might want to make a copy of the VPN template if you only want to change one device.

[Sw000976]

Ok so yes that makes sense since the template is attached to 8 devices. My assumption is the original engineer did all things cli before the edges were vmanaged then made them managed by vmanage and just made templates for various non specific things like ntp, dns, banner, etc.

Not sure this is the way to do it. 

[Torbjørn]

Since feature templates are in use the whole config must be generated from these - it is not possible to keep parts of old local cli config. You will hence need to create a new version of the VPN config if you need to add this route to this device only.

If you are going to be supporting this solution going forwards I can recommend the new Cisco Press book for SD-WAN. You will make your job a lot easier if you learn to use feature templates, feature profiles and configuration groups.

[Kanan Huseynli]

Hi,

even if you have CLI based initial config, all are replaced by vManage templates while device template (which contains lots of feature templates) is pushed. All routes will be part of VPN template and must be explicitly noted.

If you want just one VPN template with different configuration, you can mark certain sub-configurations (like static route) as optional.

Which means, if you have optional 3 static routes, it is not mandatory to configure all of them for each router.