Mode: Unmanaged¶

The Unmanaged private WAN mode does nothing but configure bonders as BGP peers with their aggregators (all private WAN modes do this).

It is intended to be used in conjuction with space-associated interfaces and protocols (similar to how the managed mesh works), to create custom private WAN topologies.

Example Use-case¶

Consider the following physical network topology, where aggregators 1 & 2 are in one routing group (RG1) and aggregators 3 & 4 are in another routing group (RG2):

mm_physical

The unmanaged private WAN mode simply maintains bonders as BGP peers with their aggregators over the tunnel, which looks like this:

um_logical

From here, we can define interfaces and protocols on aggregators 1, 2, 3 and 4 to create a custom PWAN topology.

For example, perhaps we want all PWAN traffic to use the gateway in RG1 for internet breakout, and for traffic between routing groups to use a specific backhaul between aggregators 2 and 3.

We can add interfaces, addresses, and OSPF protocols (associated with SPC1) to aggregators 1 & 2 to have them peer with each other. By running OSPF on the RG1 gateway as well, all three devices can peer with each other on that segment.

We can do a similar thing in RG2 to have aggregators 3 & 4 peer with each other, but we do not run OSPF on the gateway there.

Lastly, we could add a BGP protocol to aggregators 2 & 3, bound to the backhaul IPs, to have them peer directly over the backhaul as desired.

Then, we would have a topology that looks something like this:

um_custom

This is just one arbitary example of what is possible.