"Orchestrator Blues" Part 3: Edge Remote Diagnostics and NATted VCO address

 

If an Enterprise uses its own Orchestrator (VCO) the device is often placed inside the internal Datacenter (DC) network and has a private internal Eth0 address configured.

Therfore the internet facing Firewall in the main Data Center will have a static 1:1 translation between the public IP address used by SD-WAN Edges and the private IP address used by the VCO.

In my lab Edges are reaching the Orchestrator via 110.1.1.254 and the RO-230-IOL-Entry router will translate it to 10.8.1.254 the VCO address on Eth0.

In such cases you need a specific additional system property set to make remote diagnostics to work


 as you see you also need to set the network.portal.websocket.address


Then Remote Diagnostic access from your browser using the internal private address and edges using the public address should work.


 

Comments

Popular posts from this blog

Orchestrator Upgrade to Version 5.2

Deep Dive on DMPO and its Performance Features (available and missing) Part 1

Deep Dive on DMPO and its Performance Features (available and missing) Part 2