SDWAN CONTROLLERS and NAT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2023 12:45 PM
Here is the scenario.
I have multiple private WAN connections providers that do not allow routing our own IP blocks. So the vBond is published (1:1 nat) to these private networks. VBond is also published to internet (1:1 nat). The vManage and vSmart communicate to vBond via public IPs. Controllers connect and establish the control connections.
Problem:
Remote sites routers authenticate to vBond successfully on correct natted IP. However, when it tries to establish connection to vSmart and vManage it tries to connect to wrong public IP. After connections are cleared from vSmart and vManage and after multiple tries the remote site establishes the connections properly. The remote site router get the correct public IP of the vManage and vSmart. If the connection is not cleared it keeps trying to wrong IP. What could be the reason for this behavior?
- Labels:
-
SD-WAN Infrastructure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2023 04:28 AM
This required some troubleshooting based on your routing and design. contact Local Partner or Contact TAC.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2023 09:27 AM
Hi,
give with topology what and where is NAT configured with possible IP values (for public addresses, don't share them but you can give fake or named IP).
Please rate and mark as an accepted solution if you have found any of the information provided useful.
