Multi LAN edge deployment, one global, one private¶

The following page explains how to set up a multi LAN edge node deployment connecting to a remote node, with one LAN in the global VRF and one LAN in a private VRF (“Red”).

$graph { rankdir=TB; newrank=true; fontname="Arial"; splines=ortho; bgcolor="transparent"; nodesep=0.25; ranksep=0.75; node [ shape=box, style="filled,rounded", fontname="Arial", fontsize=12 ]; edge [ penwidth=1.5, fontname="Arial", fontsize=10 ]; lan_global [label=<LAN: 198.51.100.0/24 LAN: 2001:db8::/64 >, fillcolor="#FFFFFF", color="#666666"]; lan_red [label=<LAN: 172.16.1.0/24 LAN: fe00:1::/64 >, fillcolor="#FFE0E0", color="#C0392B"]; subgraph cluster_dc0 { label="Node: dc0"; labelloc="t"; style="filled,rounded"; fillcolor="#E9F7EF"; color="#1E8449"; dc0_eth1 [ label=<Interface: eth1 Aliases: private1 VRF: Red IPv4: 10.0.1.1/24 IPv6: fd00:1::1/64 Keep on shutdown: ✗ >, fillcolor="#FFE0E0", color="#C0392B" ]; dc0_eth0 [ label=<Interface: eth0 Aliases: public VRF: Global IPv4: 203.0.113.1/24 IPv6: 2001:db8:1::1/64 Keep on shutdown: ✔ (IPv4/IPv6) >, fillcolor="#FFFFFF", color="#666666" ]; dc0_peer [ label=<Peer: Default Mode: Listen >, shape=box, fillcolor="#FEF9E7", color="#F1C40F" ]; dc0_eth0 -- dc0_peer; dc0_eth1 -- dc0_peer [color="#C0392B"]; } subgraph cluster_cpe0 { label="Node: cpe0"; labelloc="b"; style="filled,rounded"; fillcolor="#E9F7EF"; color="#1E8449"; cpe0_route_global1 [ label=<Route: 0.0.0.0/0 VRF: Global Nexthop: Default Preference: 500 >, style="filled", fillcolor="#FFFFFF", color="#666666" ]; cpe0_route_global2 [ label=<Route: ::/0 VRF: Global Nexthop: Default Preference: 500 >, style="filled", fillcolor="#FFFFFF", color="#666666" ]; cpe0_route_red1 [ label=<Route: 10.0.1.0/24 VRF: Red Nexthop: Default Preference: 500 >, style="filled", fillcolor="#FFE0E0", color="#C0392B" ]; cpe0_route_red2 [ label=<Route: fd00:1::0/64 VRF: Red Nexthop: Default Preference: 500 >, style="filled", fillcolor="#FFE0E0", color="#C0392B" ]; cpe0_nexthop [ label=<Nexthop: Peer Peer: Default >, style="filled", fillcolor="#FFFFFF", color="#666666" ]; cpe0_peer [ label=<Peer: Default Mode: Connect Interface: eth2 Interface: eth3 Remote (node): dc0 Preference: 500 >, fillcolor="#FEF9E7", color="#F1C40F" ]; cpe0_eth0 [ label=<Interface: eth0 Aliases: lan0 VRF: Global IPv4: 198.51.100.1/24 IPv6: 2001:db8::1/64 Keep on shutdown: ✗ >, fillcolor="#FFFFFF", color="#666666" ]; cpe0_eth1 [ label=<Interface: eth1 Aliases: lan1 VRF: Red IPv4: 172.16.1.1/24 IPv6: fe00:1::1/64 Keep on shutdown: ✗ >, fillcolor="#FFE0E0", color="#C0392B" ]; cpe0_eth2 [ label=<Interface: eth2 Aliases: wan0 VRF: No VRF IPv4: DHCP Keep on shutdown: ✔ (IPv4) > ]; cpe0_eth3 [ label=<Interface: eth3 Aliases: wan1 VRF: No VRF IPv4: DHCP Keep on shutdown: ✗ > ]; cpe0_peer -- cpe0_eth2 [weight=100]; cpe0_peer -- cpe0_eth3 [weight=100]; cpe0_route_global1 -- cpe0_route_red1 -- cpe0_eth1 [style=invis, weight=50]; cpe0_route_global2 -- cpe0_route_red2 -- cpe0_eth2 [style=invis, weight=100]; cpe0_route_global1 -- cpe0_eth0 [constraint=false]; cpe0_route_global2 -- cpe0_eth0 [constraint=false]; cpe0_route_red1 -- cpe0_eth1 [constraint=false, color="#C0392B"]; cpe0_route_red2 -- cpe0_eth1 [constraint=false, color="#C0392B"]; cpe0_route_global1 -- cpe0_nexthop [constraint=false]; cpe0_route_global2 -- cpe0_nexthop [constraint=false]; cpe0_route_red1 -- cpe0_nexthop [constraint=false, color="#C0392B"]; cpe0_route_red2 -- cpe0_nexthop [constraint=false, color="#C0392B"]; cpe0_nexthop -- cpe0_peer [constraint=false]; } dc0_peer -- cpe0_peer [color="#F1C40F"]; cpe0_eth0 -- lan_global; cpe0_eth1 -- lan_red [color="#C0392B"]; { rank=same; cpe0_route_global1 -- cpe0_route_global2 -- cpe0_nexthop -- cpe0_peer [style=invis] } { rank=same; cpe0_route_red1 -- cpe0_route_red2 [style=invis] } { rank=same; cpe0_eth0 -- cpe0_eth1 -- cpe0_eth2 -- cpe0_eth3 [style=invis] } }$

Instructions¶

Follow the instructions to set up a core node with an interface in a private VRF.
Create a new node record on the management server with the name cpe0.
Add the following interfaces to the newly created node:
- Name: eth0
  - Aliases: lan0
  - VRF: Global
  - IPv4: 198.51.100.1/24
  - IPv6: 2001:db8::1/64
  - Keep on shutdown disabled
- Name: eth1
  - Aliases: lan1
  - VRF: Red
  - IPv4: 172.16.1.1/24
  - IPv6: fe00:1::1/64
  - Keep on shutdown disabled
- Name: eth2
  - Aliases: wan0
  - VRF: No VRF
  - IPv4: DHCP
  - Keep on shutdown enabled
- Name: eth3
  - Aliases: wan1
  - VRF: No VRF
  - IPv4: DHCP
  - Keep on shutdown disabled
Next, add a peer to the node:
- Name: Default
  - Interface: eth2 (Preference: 500)
  - Interface: eth3 (Preference: 500)
  - Remote (node): dc0 (Preference: 500)
Then, add a nexthop to the node:
- Type: Peer
  - Peer: Default
Finally, add four routes to the node:
- Destination: 0.0.0.0/0
  - VRF: Global
  - Nexthop: Default (Preference: 500)
- Destination: ::/0
  - VRF: Global
  - Nexthop: Default (Preference: 500)
- Destination: 10.0.1.0/24
  - VRF: Red
  - Nexthop: Default (Preference: 500)
- Destination: fd00:1::/64
  - VRF: Red
  - Nexthop: Default (Preference: 500)
You now have a complete multi LAN edge node configuration forming a peer connection with a remote node, with one LAN in the global VRF and another LAN in a private VRF.