Deploy TrafficTest/d3-red-d4-red-bidir for network network:default

Readme.md

@@ -1,3 +0,0 @@
-# Virtual Network Repository
-
-ConfigSync "network" namespace repository

all-spokes-hub-udp.yaml

@@ -0,0 +1,41 @@
+apiVersion: google.dev/v1
+kind: TrafficTest
+metadata:
+  labels:
+    compression: 240x
+    destination: dh-blue
+    direction: unidirectional
+    pattern: multi_sine
+    scenario: l3vpn-spoke-hub
+    source: all-spokes
+    vpn: blue-spoke
+  name: all-spokes-hub-udp
+  namespace: network
+spec:
+  bandwidth: 12Mbps
+  concurrent_users: 8
+  destination_device: dh-blue
+  duration: 172800
+  pattern_config:
+    base_rate: 4Mbps
+    components:
+    - amplitude: 3Mbps
+      period: 180
+      phase_offset: -75
+    - amplitude: 1Mbps
+      period: 360
+      phase_offset: -210
+    - amplitude: 1Mbps
+      period: 2520
+      phase_offset: -1470
+    max_rate: 15Mbps
+    min_rate: 500Kbps
+    noise_stddev_pct: 4.0
+    time_reference: elapsed
+  pattern_type: multi_sine
+  protocol: UDP
+  source_devices:
+  - d1-blue
+  - d2-blue
+  - d3-blue
+  vpnRef: l3vpn-blue-service

d1-hub-bidir-tcp.yaml

@@ -0,0 +1,58 @@
+apiVersion: google.dev/v1
+kind: TrafficTest
+metadata:
+  labels:
+    compression: 240x
+    destination: dh-blue
+    direction: bidirectional
+    pattern: multi_sine
+    scenario: l3vpn-spoke-hub
+    source: d1-blue
+    vpn: blue-spoke
+  name: d1-hub-bidir-tcp
+  namespace: network
+spec:
+  bandwidth: 40Mbps
+  bidirectional: true
+  concurrent_users: 20
+  destination_device: dh-blue
+  duration: 172800
+  pattern_config:
+    base_rate: 12Mbps
+    components:
+    - amplitude: 8Mbps
+      period: 180
+      phase_offset: -75
+    - amplitude: 3Mbps
+      period: 360
+      phase_offset: -210
+    - amplitude: 2Mbps
+      period: 2520
+      phase_offset: -1470
+    max_rate: 70Mbps
+    min_rate: 2Mbps
+    noise_stddev_pct: 5.0
+    time_reference: elapsed
+  pattern_type: multi_sine
+  protocol: TCP
+  reverse_bandwidth: 90Mbps
+  reverse_pattern_config:
+    base_rate: 30Mbps
+    components:
+    - amplitude: 20Mbps
+      period: 180
+      phase_offset: -75
+    - amplitude: 8Mbps
+      period: 360
+      phase_offset: -210
+    - amplitude: 5Mbps
+      period: 2520
+      phase_offset: -1470
+    max_rate: 95Mbps
+    min_rate: 5Mbps
+    noise_stddev_pct: 4.0
+    time_reference: elapsed
+  reverse_pattern_type: multi_sine
+  source_devices:
+  - d1-blue
+  vpnRef: l3vpn-blue-service

d1-red-d2-red-bidir.yaml

@@ -0,0 +1,52 @@
+apiVersion: google.dev/v1
+kind: TrafficTest
+metadata:
+  labels:
+    compression: 240x
+    destination: d2-red
+    direction: bidirectional
+    pattern: multi_sine
+    scenario: l3vpn-red-mesh
+    source: d1-red
+    vpn: red-mesh
+  name: d1-red-d2-red-bidir
+  namespace: network
+spec:
+  bandwidth: 50Mbps
+  bidirectional: true
+  concurrent_users: 15
+  destination_device: d2-red
+  duration: 172800
+  pattern_config:
+    base_rate: 18Mbps
+    components:
+    - amplitude: 12Mbps
+      period: 360
+      phase_offset: -120
+    - amplitude: 4Mbps
+      period: 2520
+      phase_offset: -450
+    max_rate: 80Mbps
+    min_rate: 2Mbps
+    noise_stddev_pct: 4.0
+    time_reference: elapsed
+  pattern_type: multi_sine
+  protocol: TCP
+  reverse_bandwidth: 70Mbps
+  reverse_pattern_config:
+    base_rate: 25Mbps
+    components:
+    - amplitude: 18Mbps
+      period: 360
+      phase_offset: -120
+    - amplitude: 5Mbps
+      period: 2520
+      phase_offset: -450
+    max_rate: 90Mbps
+    min_rate: 4Mbps
+    noise_stddev_pct: 4.0
+    time_reference: elapsed
+  reverse_pattern_type: multi_sine
+  source_devices:
+  - d1-red
+  vpnRef: l3vpn-red-service

d1-red-d3-red-bidir.yaml

@@ -0,0 +1,52 @@
+apiVersion: google.dev/v1
+kind: TrafficTest
+metadata:
+  labels:
+    compression: 240x
+    destination: d3-red
+    direction: bidirectional
+    pattern: multi_sine
+    scenario: l3vpn-red-mesh
+    source: d1-red
+    vpn: red-mesh
+  name: d1-red-d3-red-bidir
+  namespace: network
+spec:
+  bandwidth: 40Mbps
+  bidirectional: true
+  concurrent_users: 15
+  destination_device: d3-red
+  duration: 172800
+  pattern_config:
+    base_rate: 15Mbps
+    components:
+    - amplitude: 12Mbps
+      period: 360
+      phase_offset: -120
+    - amplitude: 4Mbps
+      period: 2520
+      phase_offset: -450
+    max_rate: 75Mbps
+    min_rate: 2Mbps
+    noise_stddev_pct: 4.0
+    time_reference: elapsed
+  pattern_type: multi_sine
+  protocol: TCP
+  reverse_bandwidth: 60Mbps
+  reverse_pattern_config:
+    base_rate: 22Mbps
+    components:
+    - amplitude: 16Mbps
+      period: 360
+      phase_offset: -120
+    - amplitude: 5Mbps
+      period: 2520
+      phase_offset: -450
+    max_rate: 85Mbps
+    min_rate: 3Mbps
+    noise_stddev_pct: 3.0
+    time_reference: elapsed
+  reverse_pattern_type: multi_sine
+  source_devices:
+  - d1-red
+  vpnRef: l3vpn-red-service

d1-red-d4-red-bidir.yaml

@@ -0,0 +1,52 @@
+apiVersion: google.dev/v1
+kind: TrafficTest
+metadata:
+  labels:
+    compression: 240x
+    destination: d4-red
+    direction: bidirectional
+    pattern: multi_sine
+    scenario: l3vpn-red-mesh
+    source: d1-red
+    vpn: red-mesh
+  name: d1-red-d4-red-bidir
+  namespace: network
+spec:
+  bandwidth: 15Mbps
+  bidirectional: true
+  concurrent_users: 10
+  destination_device: d4-red
+  duration: 172800
+  pattern_config:
+    base_rate: 5Mbps
+    components:
+    - amplitude: 4Mbps
+      period: 360
+      phase_offset: -120
+    - amplitude: 1Mbps
+      period: 2520
+      phase_offset: -450
+    max_rate: 20Mbps
+    min_rate: 1Mbps
+    noise_stddev_pct: 2.0
+    time_reference: elapsed
+  pattern_type: multi_sine
+  protocol: UDP
+  reverse_bandwidth: 15Mbps
+  reverse_pattern_config:
+    base_rate: 5Mbps
+    components:
+    - amplitude: 4Mbps
+      period: 360
+      phase_offset: -120
+    - amplitude: 1Mbps
+      period: 2520
+      phase_offset: -450
+    max_rate: 20Mbps
+    min_rate: 1Mbps
+    noise_stddev_pct: 2.0
+    time_reference: elapsed
+  reverse_pattern_type: multi_sine
+  source_devices:
+  - d1-red
+  vpnRef: l3vpn-red-service

d2-hub-bidir-udp.yaml

@@ -0,0 +1,42 @@
+apiVersion: google.dev/v1
+kind: TrafficTest
+metadata:
+  labels:
+    compression: 240x
+    destination: dh-blue
+    direction: bidirectional
+    pattern: multi_sine
+    scenario: l3vpn-spoke-hub
+    source: d2-blue
+    vpn: blue-spoke
+  name: d2-hub-bidir-udp
+  namespace: network
+spec:
+  bandwidth: 30Mbps
+  bidirectional: true
+  concurrent_users: 12
+  destination_device: dh-blue
+  duration: 172800
+  pattern_config:
+    base_rate: 8Mbps
+    components:
+    - amplitude: 6Mbps
+      period: 180
+      phase_offset: -75
+    - amplitude: 2Mbps
+      period: 360
+      phase_offset: -210
+    - amplitude: 2Mbps
+      period: 2520
+      phase_offset: -1470
+    max_rate: 40Mbps
+    min_rate: 1Mbps
+    noise_stddev_pct: 4.0
+    time_reference: elapsed
+  pattern_type: multi_sine
+  protocol: UDP
+  reverse_bandwidth: 10Mbps
+  reverse_pattern_type: constant
+  source_devices:
+  - d2-blue
+  vpnRef: l3vpn-blue-service

d2-red-d3-red-bidir.yaml

@@ -0,0 +1,52 @@
+apiVersion: google.dev/v1
+kind: TrafficTest
+metadata:
+  labels:
+    compression: 240x
+    destination: d3-red
+    direction: bidirectional
+    pattern: multi_sine
+    scenario: l3vpn-red-mesh
+    source: d2-red
+    vpn: red-mesh
+  name: d2-red-d3-red-bidir
+  namespace: network
+spec:
+  bandwidth: 45Mbps
+  bidirectional: true
+  concurrent_users: 15
+  destination_device: d3-red
+  duration: 172800
+  pattern_config:
+    base_rate: 15Mbps
+    components:
+    - amplitude: 11Mbps
+      period: 360
+      phase_offset: -120
+    - amplitude: 4Mbps
+      period: 2520
+      phase_offset: -450
+    max_rate: 70Mbps
+    min_rate: 2Mbps
+    noise_stddev_pct: 4.0
+    time_reference: elapsed
+  pattern_type: multi_sine
+  protocol: TCP
+  reverse_bandwidth: 55Mbps
+  reverse_pattern_config:
+    base_rate: 20Mbps
+    components:
+    - amplitude: 14Mbps
+      period: 360
+      phase_offset: -120
+    - amplitude: 4Mbps
+      period: 2520
+      phase_offset: -450
+    max_rate: 80Mbps
+    min_rate: 3Mbps
+    noise_stddev_pct: 3.0
+    time_reference: elapsed
+  reverse_pattern_type: multi_sine
+  source_devices:
+  - d2-red
+  vpnRef: l3vpn-red-service

d2-red-d4-red-bidir.yaml

@@ -0,0 +1,39 @@
+apiVersion: google.dev/v1
+kind: TrafficTest
+metadata:
+  labels:
+    compression: 240x
+    destination: d4-red
+    direction: bidirectional
+    pattern: multi_sine
+    scenario: l3vpn-red-mesh
+    source: d2-red
+    vpn: red-mesh
+  name: d2-red-d4-red-bidir
+  namespace: network
+spec:
+  bandwidth: 25Mbps
+  bidirectional: true
+  concurrent_users: 10
+  destination_device: d4-red
+  duration: 172800
+  pattern_config:
+    base_rate: 8Mbps
+    components:
+    - amplitude: 5Mbps
+      period: 360
+      phase_offset: -120
+    - amplitude: 2Mbps
+      period: 2520
+      phase_offset: -450
+    max_rate: 30Mbps
+    min_rate: 1Mbps
+    noise_stddev_pct: 3.0
+    time_reference: elapsed
+  pattern_type: multi_sine
+  protocol: UDP
+  reverse_bandwidth: 4Mbps
+  reverse_pattern_type: constant
+  source_devices:
+  - d2-red
+  vpnRef: l3vpn-red-service

d3-hub-bidir-tcp.yaml

@@ -0,0 +1,58 @@
+apiVersion: google.dev/v1
+kind: TrafficTest
+metadata:
+  labels:
+    compression: 240x
+    destination: dh-blue
+    direction: bidirectional
+    pattern: multi_sine
+    scenario: l3vpn-spoke-hub
+    source: d3-blue
+    vpn: blue-spoke
+  name: d3-hub-bidir-tcp
+  namespace: network
+spec:
+  bandwidth: 35Mbps
+  bidirectional: true
+  concurrent_users: 18
+  destination_device: dh-blue
+  duration: 172800
+  pattern_config:
+    base_rate: 10Mbps
+    components:
+    - amplitude: 7Mbps
+      period: 180
+      phase_offset: -75
+    - amplitude: 3Mbps
+      period: 360
+      phase_offset: -225
+    - amplitude: 2Mbps
+      period: 2520
+      phase_offset: -1470
+    max_rate: 60Mbps
+    min_rate: 2Mbps
+    noise_stddev_pct: 5.0
+    time_reference: elapsed
+  pattern_type: multi_sine
+  protocol: TCP
+  reverse_bandwidth: 85Mbps
+  reverse_pattern_config:
+    base_rate: 28Mbps
+    components:
+    - amplitude: 18Mbps
+      period: 180
+      phase_offset: -75
+    - amplitude: 7Mbps
+      period: 360
+      phase_offset: -225
+    - amplitude: 4Mbps
+      period: 2520
+      phase_offset: -1470
+    max_rate: 90Mbps
+    min_rate: 4Mbps
+    noise_stddev_pct: 4.0
+    time_reference: elapsed
+  reverse_pattern_type: multi_sine
+  source_devices:
+  - d3-blue
+  vpnRef: l3vpn-blue-service

d3-red-d4-red-bidir.yaml

@@ -0,0 +1,39 @@
+apiVersion: google.dev/v1
+kind: TrafficTest
+metadata:
+  labels:
+    compression: 240x
+    destination: d4-red
+    direction: bidirectional
+    pattern: multi_sine
+    scenario: l3vpn-red-mesh
+    source: d3-red
+    vpn: red-mesh
+  name: d3-red-d4-red-bidir
+  namespace: network
+spec:
+  bandwidth: 20Mbps
+  bidirectional: true
+  concurrent_users: 10
+  destination_device: d4-red
+  duration: 172800
+  pattern_config:
+    base_rate: 7Mbps
+    components:
+    - amplitude: 5Mbps
+      period: 360
+      phase_offset: -113
+    - amplitude: 2Mbps
+      period: 2520
+      phase_offset: -450
+    max_rate: 25Mbps
+    min_rate: 1Mbps
+    noise_stddev_pct: 3.0
+    time_reference: elapsed
+  pattern_type: multi_sine
+  protocol: UDP
+  reverse_bandwidth: 3Mbps
+  reverse_pattern_type: constant
+  source_devices:
+  - d3-red
+  vpnRef: l3vpn-red-service

l3vpn-blue-service.yaml

@@ -0,0 +1,121 @@
+apiVersion: google.dev/v1
+kind: VyOSL3VPN
+metadata:
+  name: l3vpn-blue-service
+  namespace: network
+spec:
+  ce_routers:
+  - name: ce1-spoke
+    protocols:
+      bgp:
+        as_number: 65035
+        neighbors:
+        - description: eBGP to pe1 BLUE_SPOKE VRF
+          peer: 10.50.50.1
+          remote_as: 65001
+        router_id: 10.0.0.80
+  - name: ce1-hub
+    protocols:
+      bgp:
+        as_number: 65035
+        neighbors:
+        - description: eBGP to pe2 BLUE_HUB VRF
+          peer: 10.80.80.1
+          remote_as: 65001
+        router_id: 10.0.0.100
+  - name: ce2-spoke
+    protocols:
+      bgp:
+        as_number: 65035
+        neighbors:
+        - description: eBGP to pe3 BLUE_SPOKE VRF
+          peer: 10.60.60.1
+          remote_as: 65001
+        router_id: 10.0.0.90
+  - name: ce3-spoke
+    protocols:
+      bgp:
+        as_number: 65035
+        neighbors:
+        - description: eBGP to pe4 BLUE_SPOKE VRF
+          peer: 10.70.70.1
+          remote_as: 65001
+        router_id: 10.0.0.91
+  routers:
+  - bgp:
+      vrfs:
+      - name: BLUE_SPOKE
+        neighbors:
+        - peer: 10.50.50.2
+          remote_as: 65035
+    name: pe1
+    vrfs:
+    - interfaces:
+      - eth2
+      name: BLUE_SPOKE
+      rd: 10.50.50.1:1011
+      rt_export:
+      - 65035:1011
+      rt_import:
+      - 65035:1030
+      table: 200
+  - bgp:
+      vrfs:
+      - name: BLUE_HUB
+        neighbors:
+        - peer: 10.80.80.2
+          remote_as: 65035
+    name: pe2
+    vrfs:
+    - interfaces:
+      - eth3
+      name: BLUE_HUB
+      rd: 10.80.80.1:1011
+      rt_export:
+      - 65035:1030
+      rt_import:
+      - 65035:1011
+      - 65035:1030
+      table: 400
+  - bgp:
+      vrfs:
+      - name: BLUE_SPOKE
+        neighbors:
+        - peer: 10.60.60.2
+          remote_as: 65035
+    name: pe3
+    vrfs:
+    - interfaces:
+      - eth2
+      name: BLUE_SPOKE
+      rd: 10.60.60.1:1011
+      rt_export:
+      - 65035:1011
+      rt_import:
+      - 65035:1030
+      table: 200
+  - bgp:
+      vrfs:
+      - name: BLUE_SPOKE
+        neighbors:
+        - peer: 10.70.70.2
+          remote_as: 65035
+    name: pe4
+    vrfs:
+    - interfaces:
+      - eth2
+      name: BLUE_SPOKE
+      rd: 10.70.70.1:1011
+      rt_export:
+      - 65035:1011
+      rt_import:
+      - 65035:1030
+      table: 200
+  services:
+  - name: BLUE_SPOKE
+    topology: spoke
+    type: l3vpn
+  - name: BLUE_HUB
+    topology: hub
+    type: l3vpn
+  underlayRef: l3vpn-underlay

l3vpn-infra.yaml

@@ -0,0 +1,859 @@
+apiVersion: google.dev/v1
+kind: VyOSInfrastructure
+metadata:
+  labels:
+    environment: lab
+    type: telco-lab
+  name: l3vpn-infra
+  namespace: network
+spec:
+  description: L3VPN Infrastructure
+  devices:
+  - gateway: 10.100.2.1
+    ip_address: 10.100.2.10
+    mgmt_ip: 192.168.122.50
+    name: dh-blue
+    network_name: lan-hub
+  - gateway: 10.100.1.1
+    ip_address: 10.100.1.10
+    mgmt_ip: 192.168.122.51
+    name: d1-blue
+    network_name: lan-spoke1
+  - gateway: 10.100.3.1
+    ip_address: 10.100.3.10
+    mgmt_ip: 192.168.122.52
+    name: d2-blue
+    network_name: lan-spoke2
+  - gateway: 10.100.4.1
+    ip_address: 10.100.4.10
+    mgmt_ip: 192.168.122.53
+    name: d3-blue
+    network_name: lan-spoke3
+  - gateway: 10.101.1.1
+    ip_address: 10.101.1.10
+    mgmt_ip: 192.168.122.54
+    name: d1-red
+    network_name: lan-red1
+  - gateway: 10.101.2.1
+    ip_address: 10.101.2.10
+    mgmt_ip: 192.168.122.55
+    name: d2-red
+    network_name: lan-red2
+  - gateway: 10.101.3.1
+    ip_address: 10.101.3.10
+    mgmt_ip: 192.168.122.56
+    name: d3-red
+    network_name: lan-red3
+  - gateway: 10.101.4.1
+    ip_address: 10.101.4.10
+    mgmt_ip: 192.168.122.57
+    name: d4-red
+    network_name: lan-red4
+  networks:
+  - bandwidth: 1gbit
+    connected_routers:
+    - interface: eth1
+      ip_address: 172.16.30.1
+      router_name: p1
+    - interface: eth1
+      ip_address: 172.16.30.2
+      router_name: p2
+    name: p1-p2
+    network_type: p2p
+    subnet: 172.16.30.0/24
+    vlan: 301
+  - bandwidth: 1gbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 172.16.40.1
+      router_name: p1
+    - interface: eth2
+      ip_address: 172.16.40.2
+      router_name: p3
+    name: p1-p3
+    network_type: p2p
+    subnet: 172.16.40.0/24
+    vlan: 302
+  - bandwidth: 1gbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 172.16.60.1
+      router_name: p2
+    - interface: eth2
+      ip_address: 172.16.60.2
+      router_name: p4
+    name: p2-p4
+    network_type: p2p
+    subnet: 172.16.60.0/24
+    vlan: 303
+  - bandwidth: 1gbit
+    connected_routers:
+    - interface: eth3
+      ip_address: 172.16.50.1
+      router_name: p3
+    - interface: eth3
+      ip_address: 172.16.50.2
+      router_name: p4
+    name: p3-p4
+    network_type: p2p
+    subnet: 172.16.50.0/24
+    vlan: 304
+  - bandwidth: 1gbit
+    connected_routers:
+    - interface: eth4
+      ip_address: 172.16.10.1
+      router_name: p1
+    - interface: eth2
+      ip_address: 172.16.10.2
+      router_name: rr1
+    name: p1-rr1
+    network_type: p2p
+    subnet: 172.16.10.0/24
+    vlan: 305
+  - bandwidth: 1gbit
+    connected_routers:
+    - interface: eth3
+      ip_address: 172.16.20.1
+      router_name: p2
+    - interface: eth1
+      ip_address: 172.16.20.2
+      router_name: rr1
+    name: p2-rr1
+    network_type: p2p
+    subnet: 172.16.20.0/24
+    vlan: 306
+  - bandwidth: 1gbit
+    connected_routers:
+    - interface: eth4
+      ip_address: 172.16.70.1
+      router_name: p3
+    - interface: eth2
+      ip_address: 172.16.70.2
+      router_name: rr2
+    name: p3-rr2
+    network_type: p2p
+    subnet: 172.16.70.0/24
+    vlan: 307
+  - bandwidth: 1gbit
+    connected_routers:
+    - interface: eth1
+      ip_address: 172.16.80.1
+      router_name: p4
+    - interface: eth1
+      ip_address: 172.16.80.2
+      router_name: rr2
+    name: p4-rr2
+    network_type: p2p
+    subnet: 172.16.80.0/24
+    vlan: 308
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth3
+      ip_address: 172.16.90.1
+      router_name: p1
+    - interface: eth1
+      ip_address: 172.16.90.2
+      router_name: pe1
+    name: p1-pe1
+    network_type: p2p
+    subnet: 172.16.90.0/24
+    vlan: 309
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth5
+      ip_address: 172.16.100.1
+      router_name: p1
+    - interface: eth1
+      ip_address: 172.16.100.2
+      router_name: pe2
+    name: p1-pe2
+    network_type: p2p
+    subnet: 172.16.100.0/24
+    vlan: 310
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth1
+      ip_address: 172.16.110.1
+      router_name: p3
+    - interface: eth2
+      ip_address: 172.16.110.2
+      router_name: pe2
+    name: p3-pe2
+    network_type: p2p
+    subnet: 172.16.110.0/24
+    vlan: 311
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth4
+      ip_address: 172.16.140.1
+      router_name: p4
+    - interface: eth1
+      ip_address: 172.16.140.2
+      router_name: pe3
+    name: p4-pe3
+    network_type: p2p
+    subnet: 172.16.140.0/24
+    vlan: 312
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth4
+      ip_address: 172.16.150.1
+      router_name: p2
+    - interface: eth1
+      ip_address: 172.16.150.2
+      router_name: pe4
+    name: p2-pe4
+    network_type: p2p
+    subnet: 172.16.150.0/24
+    vlan: 313
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth5
+      ip_address: 172.16.160.1
+      router_name: p3
+    - interface: eth4
+      ip_address: 172.16.160.2
+      router_name: pe1
+    name: p3-pe1
+    network_type: p2p
+    subnet: 172.16.160.0/24
+    vlan: 314
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth5
+      ip_address: 172.16.170.1
+      router_name: p2
+    - interface: eth4
+      ip_address: 172.16.170.2
+      router_name: pe3
+    name: p2-pe3
+    network_type: p2p
+    subnet: 172.16.170.0/24
+    vlan: 315
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth5
+      ip_address: 172.16.180.1
+      router_name: p4
+    - interface: eth4
+      ip_address: 172.16.180.2
+      router_name: pe4
+    name: p4-pe4
+    network_type: p2p
+    subnet: 172.16.180.0/24
+    vlan: 316
+  - bandwidth: unlimited
+    connected_routers:
+    - interface: eth0
+      ip_address: 192.168.122.11
+      router_name: p1
+    - interface: eth0
+      ip_address: 192.168.122.12
+      router_name: p2
+    - interface: eth0
+      ip_address: 192.168.122.13
+      router_name: p3
+    - interface: eth0
+      ip_address: 192.168.122.14
+      router_name: p4
+    - interface: eth0
+      ip_address: 192.168.122.21
+      router_name: rr1
+    - interface: eth0
+      ip_address: 192.168.122.22
+      router_name: rr2
+    - interface: eth0
+      ip_address: 192.168.122.31
+      router_name: pe1
+    - interface: eth0
+      ip_address: 192.168.122.32
+      router_name: pe2
+    - interface: eth0
+      ip_address: 192.168.122.33
+      router_name: pe3
+    - interface: eth0
+      ip_address: 192.168.122.40
+      router_name: ce1-spoke
+    - interface: eth0
+      ip_address: 192.168.122.41
+      router_name: ce1-hub
+    - interface: eth0
+      ip_address: 192.168.122.42
+      router_name: ce2-spoke
+    - interface: eth0
+      ip_address: 192.168.122.34
+      router_name: pe4
+    - interface: eth0
+      ip_address: 192.168.122.43
+      router_name: ce3-spoke
+    - interface: eth0
+      ip_address: 192.168.122.44
+      router_name: ce1-red
+    - interface: eth0
+      ip_address: 192.168.122.45
+      router_name: ce2-red
+    - interface: eth0
+      ip_address: 192.168.122.46
+      router_name: ce3-red
+    - interface: eth0
+      ip_address: 192.168.122.47
+      router_name: ce4-red
+    gateway: 192.168.122.1
+    name: mgmt
+    network_type: management
+    subnet: 192.168.122.0/24
+  - bandwidth: unlimited
+    name: loopbacks
+    network_type: loopback
+    subnet: 10.0.0.0/24
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.50.50.1
+      router_name: pe1
+    - interface: eth1
+      ip_address: 10.50.50.2
+      router_name: ce1-spoke
+    name: pe1-ce1-spoke
+    network_type: p2p
+    subnet: 10.50.50.0/24
+    vlan: 401
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth3
+      ip_address: 10.80.80.1
+      router_name: pe2
+    - interface: eth1
+      ip_address: 10.80.80.2
+      router_name: ce1-hub
+    name: pe2-ce1-hub
+    network_type: p2p
+    subnet: 10.80.80.0/24
+    vlan: 402
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.60.60.1
+      router_name: pe3
+    - interface: eth1
+      ip_address: 10.60.60.2
+      router_name: ce2-spoke
+    name: pe3-ce2-spoke
+    network_type: p2p
+    subnet: 10.60.60.0/24
+    vlan: 403
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.70.70.1
+      router_name: pe4
+    - interface: eth1
+      ip_address: 10.70.70.2
+      router_name: ce3-spoke
+    name: pe4-ce3-spoke
+    network_type: p2p
+    subnet: 10.70.70.0/24
+    vlan: 404
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth3
+      ip_address: 10.55.55.1
+      router_name: pe1
+    - interface: eth1
+      ip_address: 10.55.55.2
+      router_name: ce1-red
+    name: pe1-ce1-red
+    network_type: p2p
+    subnet: 10.55.55.0/24
+    vlan: 405
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth4
+      ip_address: 10.65.65.1
+      router_name: pe2
+    - interface: eth1
+      ip_address: 10.65.65.2
+      router_name: ce2-red
+    name: pe2-ce2-red
+    network_type: p2p
+    subnet: 10.65.65.0/24
+    vlan: 406
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth3
+      ip_address: 10.75.75.1
+      router_name: pe3
+    - interface: eth1
+      ip_address: 10.75.75.2
+      router_name: ce3-red
+    name: pe3-ce3-red
+    network_type: p2p
+    subnet: 10.75.75.0/24
+    vlan: 407
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth3
+      ip_address: 10.85.85.1
+      router_name: pe4
+    - interface: eth1
+      ip_address: 10.85.85.2
+      router_name: ce4-red
+    name: pe4-ce4-red
+    network_type: p2p
+    subnet: 10.85.85.0/24
+    vlan: 408
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.100.1.1
+      router_name: ce1-spoke
+    gateway: 10.100.1.1
+    name: lan-spoke1
+    network_type: multi-access
+    subnet: 10.100.1.0/24
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.100.3.1
+      router_name: ce2-spoke
+    gateway: 10.100.3.1
+    name: lan-spoke2
+    network_type: multi-access
+    subnet: 10.100.3.0/24
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.100.4.1
+      router_name: ce3-spoke
+    gateway: 10.100.4.1
+    name: lan-spoke3
+    network_type: multi-access
+    subnet: 10.100.4.0/24
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.100.2.1
+      router_name: ce1-hub
+    gateway: 10.100.2.1
+    name: lan-hub
+    network_type: multi-access
+    subnet: 10.100.2.0/24
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.101.1.1
+      router_name: ce1-red
+    gateway: 10.101.1.1
+    name: lan-red1
+    network_type: multi-access
+    subnet: 10.101.1.0/24
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.101.2.1
+      router_name: ce2-red
+    gateway: 10.101.2.1
+    name: lan-red2
+    network_type: multi-access
+    subnet: 10.101.2.0/24
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.101.3.1
+      router_name: ce3-red
+    gateway: 10.101.3.1
+    name: lan-red3
+    network_type: multi-access
+    subnet: 10.101.3.0/24
+  - bandwidth: 100mbit
+    connected_routers:
+    - interface: eth2
+      ip_address: 10.101.4.1
+      router_name: ce4-red
+    gateway: 10.101.4.1
+    name: lan-red4
+    network_type: multi-access
+    subnet: 10.101.4.0/24
+  routers:
+  - hostname: p1
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: p1-p2
+    - name: eth2
+      network: p1-p3
+    - name: eth3
+      network: p1-pe1
+    - name: eth4
+      network: p1-rr1
+    - name: eth5
+      network: p1-pe2
+    - name: lo
+      network: loopbacks
+    location:
+      city: London
+      country: United Kingdom
+      latitude: 51.5074
+      longitude: -0.1278
+      site: London-DC1
+    name: p1
+    role: P
+    router_id: 10.0.0.3
+  - hostname: p2
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: p1-p2
+    - name: eth2
+      network: p2-p4
+    - name: eth3
+      network: p2-rr1
+    - name: eth4
+      network: p2-pe4
+    - name: eth5
+      network: p2-pe3
+    - name: lo
+      network: loopbacks
+    location:
+      city: Manchester
+      country: United Kingdom
+      latitude: 53.4808
+      longitude: -2.2426
+      site: Manchester-DC1
+    name: p2
+    role: P
+    router_id: 10.0.0.4
+  - hostname: p3
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: p3-pe2
+    - name: eth2
+      network: p1-p3
+    - name: eth3
+      network: p3-p4
+    - name: eth4
+      network: p3-rr2
+    - name: eth5
+      network: p3-pe1
+    - name: lo
+      network: loopbacks
+    location:
+      city: Edinburgh
+      country: United Kingdom
+      latitude: 55.9533
+      longitude: -3.1883
+      site: Edinburgh-DC1
+    name: p3
+    role: P
+    router_id: 10.0.0.5
+  - hostname: p4
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: p4-rr2
+    - name: eth2
+      network: p2-p4
+    - name: eth3
+      network: p3-p4
+    - name: eth4
+      network: p4-pe3
+    - name: eth5
+      network: p4-pe4
+    - name: lo
+      network: loopbacks
+    location:
+      city: Leeds
+      country: United Kingdom
+      latitude: 53.8008
+      longitude: -1.5491
+      site: Leeds-DC1
+    name: p4
+    role: P
+    router_id: 10.0.0.6
+  - hostname: rr1
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: p2-rr1
+    - name: eth2
+      network: p1-rr1
+    - name: lo
+      network: loopbacks
+    location:
+      city: Birmingham
+      country: United Kingdom
+      latitude: 52.4862
+      longitude: -1.8904
+      site: Birmingham-DC1
+    name: rr1
+    role: RR
+    router_id: 10.0.0.1
+  - hostname: rr2
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: p4-rr2
+    - name: eth2
+      network: p3-rr2
+    - name: lo
+      network: loopbacks
+    location:
+      city: Bristol
+      country: United Kingdom
+      latitude: 51.4545
+      longitude: -2.5879
+      site: Bristol-DC1
+    name: rr2
+    role: RR
+    router_id: 10.0.0.2
+  - hostname: pe1
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: p1-pe1
+    - name: eth2
+      network: pe1-ce1-spoke
+    - name: eth3
+      network: pe1-ce1-red
+    - name: eth4
+      network: p3-pe1
+    - name: lo
+      network: loopbacks
+    location:
+      city: Oxford
+      country: United Kingdom
+      latitude: 51.752
+      longitude: -1.2577
+      site: Oxford-DC1
+    name: pe1
+    role: PE
+    router_id: 10.0.0.7
+  - hostname: pe2
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: p1-pe2
+    - name: eth2
+      network: p3-pe2
+    - name: eth3
+      network: pe2-ce1-hub
+    - name: eth4
+      network: pe2-ce2-red
+    - name: lo
+      network: loopbacks
+    location:
+      city: Cambridge
+      country: United Kingdom
+      latitude: 52.2053
+      longitude: 0.1218
+      site: Cambridge-DC1
+    name: pe2
+    role: PE
+    router_id: 10.0.0.8
+  - hostname: pe3
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: p4-pe3
+    - name: eth2
+      network: pe3-ce2-spoke
+    - name: eth3
+      network: pe3-ce3-red
+    - name: eth4
+      network: p2-pe3
+    - name: lo
+      network: loopbacks
+    location:
+      city: Brighton
+      country: United Kingdom
+      latitude: 50.8198
+      longitude: -0.1371
+      site: Brighton-DC1
+    name: pe3
+    role: PE
+    router_id: 10.0.0.10
+  - hostname: ce1-spoke
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: pe1-ce1-spoke
+    - name: eth2
+      network: lan-spoke1
+    - name: lo
+      network: loopbacks
+    location:
+      city: Sheffield
+      country: United Kingdom
+      latitude: 53.3811
+      longitude: -1.4701
+      site: Sheffield-Site1
+    name: ce1-spoke
+    role: CE
+    router_id: 10.0.0.80
+  - hostname: ce1-hub
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: pe2-ce1-hub
+    - name: eth2
+      network: lan-hub
+    - name: lo
+      network: loopbacks
+    location:
+      city: Nottingham
+      country: United Kingdom
+      latitude: 52.9548
+      longitude: -1.1581
+      site: Nottingham-Hub1
+    name: ce1-hub
+    role: CE
+    router_id: 10.0.0.100
+  - hostname: ce2-spoke
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: pe3-ce2-spoke
+    - name: eth2
+      network: lan-spoke2
+    - name: lo
+      network: loopbacks
+    location:
+      city: Liverpool
+      country: United Kingdom
+      latitude: 53.4084
+      longitude: -2.9916
+      site: Liverpool-Site1
+    name: ce2-spoke
+    role: CE
+    router_id: 10.0.0.90
+  - hostname: pe4
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: p2-pe4
+    - name: eth2
+      network: pe4-ce3-spoke
+    - name: eth3
+      network: pe4-ce4-red
+    - name: eth4
+      network: p4-pe4
+    - name: lo
+      network: loopbacks
+    location:
+      city: Cardiff
+      country: United Kingdom
+      latitude: 51.4816
+      longitude: -3.1791
+      site: Cardiff-DC1
+    name: pe4
+    role: PE
+    router_id: 10.0.0.11
+  - hostname: ce3-spoke
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: pe4-ce3-spoke
+    - name: eth2
+      network: lan-spoke3
+    - name: lo
+      network: loopbacks
+    location:
+      city: Huddersfield
+      country: United Kingdom
+      latitude: 53.645
+      longitude: -1.785
+      site: Huddersfield-Site1
+    name: ce3-spoke
+    role: CE
+    router_id: 10.0.0.91
+  - hostname: ce1-red
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: pe1-ce1-red
+    - name: eth2
+      network: lan-red1
+    - name: lo
+      network: loopbacks
+    location:
+      city: Norwich
+      country: United Kingdom
+      latitude: 52.6309
+      longitude: 1.2974
+      site: Norwich-Site1
+    name: ce1-red
+    role: CE
+    router_id: 10.0.0.101
+  - hostname: ce2-red
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: pe2-ce2-red
+    - name: eth2
+      network: lan-red2
+    - name: lo
+      network: loopbacks
+    location:
+      city: Coventry
+      country: United Kingdom
+      latitude: 52.4082
+      longitude: -1.5109
+      site: Coventry-Site1
+    name: ce2-red
+    role: CE
+    router_id: 10.0.0.102
+  - hostname: ce3-red
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: pe3-ce3-red
+    - name: eth2
+      network: lan-red3
+    - name: lo
+      network: loopbacks
+    location:
+      city: Plymouth
+      country: United Kingdom
+      latitude: 50.3755
+      longitude: -4.1427
+      site: Plymouth-Site1
+    name: ce3-red
+    role: CE
+    router_id: 10.0.0.103
+  - hostname: ce4-red
+    interfaces:
+    - name: eth0
+      network: mgmt
+    - name: eth1
+      network: pe4-ce4-red
+    - name: eth2
+      network: lan-red4
+    - name: lo
+      network: loopbacks
+    location:
+      city: Leicester
+      country: United Kingdom
+      latitude: 52.6369
+      longitude: -1.1398
+      site: Leicester-Site1
+    name: ce4-red
+    role: CE
+    router_id: 10.0.0.104

l3vpn-red-service.yaml

@@ -0,0 +1,117 @@
+apiVersion: google.dev/v1
+kind: VyOSL3VPN
+metadata:
+  name: l3vpn-red-service
+  namespace: network
+spec:
+  ce_routers:
+  - name: ce1-red
+    protocols:
+      bgp:
+        as_number: 65035
+        neighbors:
+        - description: eBGP to pe1 RED_MESH VRF
+          peer: 10.55.55.1
+          remote_as: 65001
+        router_id: 10.0.0.101
+  - name: ce2-red
+    protocols:
+      bgp:
+        as_number: 65035
+        neighbors:
+        - description: eBGP to pe2 RED_MESH VRF
+          peer: 10.65.65.1
+          remote_as: 65001
+        router_id: 10.0.0.102
+  - name: ce3-red
+    protocols:
+      bgp:
+        as_number: 65035
+        neighbors:
+        - description: eBGP to pe3 RED_MESH VRF
+          peer: 10.75.75.1
+          remote_as: 65001
+        router_id: 10.0.0.103
+  - name: ce4-red
+    protocols:
+      bgp:
+        as_number: 65035
+        neighbors:
+        - description: eBGP to pe4 RED_MESH VRF
+          peer: 10.85.85.1
+          remote_as: 65001
+        router_id: 10.0.0.104
+  routers:
+  - bgp:
+      vrfs:
+      - name: RED_MESH
+        neighbors:
+        - peer: 10.55.55.2
+          remote_as: 65035
+    name: pe1
+    vrfs:
+    - interfaces:
+      - eth3
+      name: RED_MESH
+      rd: 10.55.55.1:2000
+      rt_export:
+      - 65035:2000
+      rt_import:
+      - 65035:2000
+      table: 300
+  - bgp:
+      vrfs:
+      - name: RED_MESH
+        neighbors:
+        - peer: 10.65.65.2
+          remote_as: 65035
+    name: pe2
+    vrfs:
+    - interfaces:
+      - eth4
+      name: RED_MESH
+      rd: 10.65.65.1:2000
+      rt_export:
+      - 65035:2000
+      rt_import:
+      - 65035:2000
+      table: 300
+  - bgp:
+      vrfs:
+      - name: RED_MESH
+        neighbors:
+        - peer: 10.75.75.2
+          remote_as: 65035
+    name: pe3
+    vrfs:
+    - interfaces:
+      - eth3
+      name: RED_MESH
+      rd: 10.75.75.1:2000
+      rt_export:
+      - 65035:2000
+      rt_import:
+      - 65035:2000
+      table: 300
+  - bgp:
+      vrfs:
+      - name: RED_MESH
+        neighbors:
+        - peer: 10.85.85.2
+          remote_as: 65035
+    name: pe4
+    vrfs:
+    - interfaces:
+      - eth3
+      name: RED_MESH
+      rd: 10.85.85.1:2000
+      rt_export:
+      - 65035:2000
+      rt_import:
+      - 65035:2000
+      table: 300
+  services:
+  - name: RED_MESH
+    topology: any-to-any
+    type: l3vpn
+  underlayRef: l3vpn-underlay

l3vpn-underlay.yaml

@@ -0,0 +1,242 @@
+apiVersion: google.dev/v1
+kind: VyOSUnderlay
+metadata:
+  name: l3vpn-underlay
+  namespace: network
+spec:
+  infrastructureRef: l3vpn-infra
+  mpls:
+    enabled: true
+    ldp:
+      router_id_interface: loopback
+  routers:
+  - name: p1
+    protocols:
+      mpls:
+        enabled: true
+        ldp:
+          interfaces:
+          - eth1
+          - eth2
+          - eth3
+          - eth4
+          - eth5
+          router_id: 10.0.0.3
+      ospf:
+        areas:
+        - area: 0.0.0.0
+          type: backbone
+        router_id: 10.0.0.3
+  - name: p2
+    protocols:
+      mpls:
+        enabled: true
+        ldp:
+          interfaces:
+          - eth1
+          - eth2
+          - eth3
+          - eth4
+          - eth5
+          router_id: 10.0.0.4
+      ospf:
+        areas:
+        - area: 0.0.0.0
+          type: backbone
+        router_id: 10.0.0.4
+  - name: p3
+    protocols:
+      mpls:
+        enabled: true
+        ldp:
+          interfaces:
+          - eth1
+          - eth2
+          - eth3
+          - eth4
+          - eth5
+          router_id: 10.0.0.5
+      ospf:
+        areas:
+        - area: 0.0.0.0
+          type: backbone
+        router_id: 10.0.0.5
+  - name: p4
+    protocols:
+      mpls:
+        enabled: true
+        ldp:
+          interfaces:
+          - eth1
+          - eth2
+          - eth3
+          - eth4
+          - eth5
+          router_id: 10.0.0.6
+      ospf:
+        areas:
+        - area: 0.0.0.0
+          type: backbone
+        router_id: 10.0.0.6
+  - name: rr1
+    protocols:
+      bgp:
+        as_number: 65001
+        neighbors:
+        - peer: 10.0.0.7
+          remote_as: 65001
+          route_reflector_client: true
+        - peer: 10.0.0.8
+          remote_as: 65001
+          route_reflector_client: true
+        - peer: 10.0.0.10
+          remote_as: 65001
+          route_reflector_client: true
+        - peer: 10.0.0.11
+          remote_as: 65001
+          route_reflector_client: true
+        route_reflector: true
+        router_id: 10.0.0.1
+      mpls:
+        enabled: true
+        ldp:
+          interfaces:
+          - eth1
+          - eth2
+          router_id: 10.0.0.1
+      ospf:
+        areas:
+        - area: 0.0.0.0
+          type: backbone
+        router_id: 10.0.0.1
+  - name: rr2
+    protocols:
+      bgp:
+        as_number: 65001
+        neighbors:
+        - peer: 10.0.0.7
+          remote_as: 65001
+          route_reflector_client: true
+        - peer: 10.0.0.8
+          remote_as: 65001
+          route_reflector_client: true
+        - peer: 10.0.0.10
+          remote_as: 65001
+          route_reflector_client: true
+        - peer: 10.0.0.11
+          remote_as: 65001
+          route_reflector_client: true
+        route_reflector: true
+        router_id: 10.0.0.2
+      mpls:
+        enabled: true
+        ldp:
+          interfaces:
+          - eth1
+          - eth2
+          router_id: 10.0.0.2
+      ospf:
+        areas:
+        - area: 0.0.0.0
+          type: backbone
+        router_id: 10.0.0.2
+  - name: pe1
+    protocols:
+      bgp:
+        as_number: 65001
+        neighbors:
+        - peer: 10.0.0.1
+          remote_as: 65001
+        - peer: 10.0.0.2
+          remote_as: 65001
+        router_id: 10.0.0.7
+      mpls:
+        enabled: true
+        ldp:
+          interfaces:
+          - eth1
+          - eth4
+          router_id: 10.0.0.7
+      ospf:
+        areas:
+        - area: 0.0.0.0
+          type: backbone
+        router_id: 10.0.0.7
+  - name: pe2
+    protocols:
+      bgp:
+        as_number: 65001
+        neighbors:
+        - peer: 10.0.0.1
+          remote_as: 65001
+        - peer: 10.0.0.2
+          remote_as: 65001
+        router_id: 10.0.0.8
+      mpls:
+        enabled: true
+        ldp:
+          interfaces:
+          - eth1
+          - eth2
+          router_id: 10.0.0.8
+      ospf:
+        areas:
+        - area: 0.0.0.0
+          type: backbone
+        router_id: 10.0.0.8
+  - name: pe3
+    protocols:
+      bgp:
+        as_number: 65001
+        neighbors:
+        - peer: 10.0.0.1
+          remote_as: 65001
+        - peer: 10.0.0.2
+          remote_as: 65001
+        router_id: 10.0.0.10
+      mpls:
+        enabled: true
+        ldp:
+          interfaces:
+          - eth1
+          - eth4
+          router_id: 10.0.0.10
+      ospf:
+        areas:
+        - area: 0.0.0.0
+          type: backbone
+        router_id: 10.0.0.10
+  - name: pe4
+    protocols:
+      bgp:
+        as_number: 65001
+        neighbors:
+        - peer: 10.0.0.1
+          remote_as: 65001
+        - peer: 10.0.0.2
+          remote_as: 65001
+        router_id: 10.0.0.11
+      mpls:
+        enabled: true
+        ldp:
+          interfaces:
+          - eth1
+          - eth4
+          router_id: 10.0.0.11
+      ospf:
+        areas:
+        - area: 0.0.0.0
+          type: backbone
+        router_id: 10.0.0.11
+  routing:
+    bgp:
+      as_number: 65001
+      route_reflectors:
+      - 10.0.0.1
+      - 10.0.0.2
+      router_id_source: loopback
+    ospf:
+      areas:
+      - area_id: 0.0.0.0
+        type: backbone
+      router_id_source: loopback