Sdwan implementation external routers

[Hamada Ahmed]

Hi,

For Sdwan implementation, if I have external router which not supported Sdwan management.

How I can create tunnel between this routers and HQ router, if HQ router is managed by vmanage which mean no CLI enabled anymore?

If no cli anymore, who will manage the external routers? 

Also, is there any limitations regarding the external routers qualities that can be managed? If there any, how to mitigate this limitation? 

[Octavian Szolga]

Hi Hamada,

You mean you have an SDWAN HQ router which has to be connected using an IPsec tunnel to a different external (non-SDWAN) router?

If so, you configure the external router connection to the HQ SDWAN router using CLI. 

The HQ SDWAN router IPsec connection to the external routers can be configured using a vManage feature template.

BR,
Octavian

[Hamada Ahmed]

You mean you have an SDWAN HQ router which has to be connected using an IPsec tunnel to a different external (non-SDWAN) router? Yes this my mean

1- so how I can create tunnel between this routers and HQ router, if HQ router is managed by vmanage which mean no CLI enabled anymore?

2- or CLI still enabled?

3- If no cli anymore, who will manage the external routers? 

4- Also, is there any limitations regarding the external routers qualities that can be managed? If there any, how to mitigate this limitation? 

[Octavian Szolga]

Hi Hamada,

The HQ router (part of SDWAN) can have its IPSec tunnels outside SDWAN configured using feature templates. No CLI needed.

You just push (using vManage/template) an IPsec tunnel configuration related to as many non-SDWAN/external routers you like.

The external routers (non-SDWAN) are CLI configured for IPsec connectivity toward your SDWAN router. The SDWAN router is just an IPsec peer.

The external routers do not have to be managed in any way by vManage. You just called them 'external'. So no SDWAN, no fabric.

They're just like a 3rd party entity in this whole setup.

BR,

Octavian