cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Choose one of the topics below for SD-WAN Resources to help you on your journey with SD-WAN

This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC!
We will not comment or assist with your TAC case in these forums.

316
Views
0
Helpful
1
Replies
Amr_Younes
Beginner

Design query for Cisco SD-WAN

Hello,

 

If we have Cisco SD-WAN controller deployed on customer premises.

 

Can we have these controller deployed behind an HQ cEdge which has an IP in the same range of the Cisco SD-WAN controllers and this HQ cEdge should be part of the Cisco SD-WAN fabric in the same time?

 

So HQ cEdge should be hacting as underlay & overlay at the same time.

 

I've tried but cEdge couldn't join the network and it only worked once we deployed the Cisco SD-WAN controller behind a traditional L3 device which is not part of Cisco SD-WAN fabric.

 

Attached you can check an example of the desired topology.

1 ACCEPTED SOLUTION

Accepted Solutions
Kanan Huseynli
Participant

Hi,

 

hmm....this type of design actually is not acceptable. Let me explain why, 15.1.1.1 can't use another interface to reach controllers. You should have route - path over that interface. For normal SD-WAN you internet border that does normal NAT operations (because at least all controllers should reach vbond's public address and internet based TLOCs as well) and mpls CE device that does normal routing operations for underlay.

I suggest to read SD-WAN design and deployment guides. In addition to, it is highly recommended to read and/ or watch SD-WAN design related ciscolive sessions.

 

https://www.cisco.com/c/en/us/td/docs/solutions/CVD/SDWAN/cisco-sdwan-design-guide.html

 

https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/SDWAN/SD-WAN-End-to-End-Deployment-Guide.pdf

 

HTH,

View solution in original post

1 REPLY 1
Kanan Huseynli
Participant

Hi,

 

hmm....this type of design actually is not acceptable. Let me explain why, 15.1.1.1 can't use another interface to reach controllers. You should have route - path over that interface. For normal SD-WAN you internet border that does normal NAT operations (because at least all controllers should reach vbond's public address and internet based TLOCs as well) and mpls CE device that does normal routing operations for underlay.

I suggest to read SD-WAN design and deployment guides. In addition to, it is highly recommended to read and/ or watch SD-WAN design related ciscolive sessions.

 

https://www.cisco.com/c/en/us/td/docs/solutions/CVD/SDWAN/cisco-sdwan-design-guide.html

 

https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/SDWAN/SD-WAN-End-to-End-Deployment-Guide.pdf

 

HTH,

View solution in original post