10- Multiple WAN Links

Exercise 1	Configure an Internet Path
Step 1	Gather PCI Addresses for Datacenter Router 1
PCLI bosdc1	su admin Password: 128Tadmin # show platform device-interfaces >> wan1 PCI address
Step 2	Configure WAN Interface on Datacenter Router 1
	Configuration > Authority > Routers: seabo1 > Node: node1 > ADD Device Interface: wan1 ADD Network Interface: wan1 ADD next to Interface Addresses: 3.3.3.128 SET: Prefix: 24 SET: Gateway: 3.3.3.1
Step 3	Gather PCI Addresses for Branch 1 Router
PCLI seabo1	su admin Password: 128Tadmin # show platform device-interfaces >> wan1 PCI address
Step 4	Configure WAN Interface on Branch Router 1
	Configuration > Authority > Routers: seabo1 > Node: node1 > ADD Device Interface: wan1 ADD Network Interface: wan1 ADD next to Interface Addresses: 1.1.1.128 SET: Prefix: 24 SET: Gateway: 1.1.1.1
Step 5	Apply Internet Neighborhood and Vector
bosdc1	Configuration > Authority > Routers: bosdc1 > Node: node1 > Device Interface: wan1 > Network Interface: wan1 > neighborhoods neighborhood name: internet CHECK: Topology: hub Vector: broadband
seabo1	Configuration > Authority > Routers: seabo1 > Node: node1 > Device Interface: wan1 > Network Interface: wan1 neighborhood name: internet CHECK: Topology: spoke Vector: broadband
	VALIDATE and COMMIT
Step 6	Verify MPLS Neighbourhood and Apply Vector
	Configuration > Authority > Routers: bosdc1 > Node: node1 > Device Interface: mpls1 > Network Interface: mpls1 > neighborhoods
	Configuration > Authority > Routers: seabo1 > Node: node1 > Device Interface: mpls1 > Network Interface: mpls1 > neighborhoods
Step 7	Verify Two Links
Web GUI	Select: Topology Verify there are 2 links between the Seattle Router and Boston Router
	Click on the Seattle Router and CLICK: "Show Stats" and "LOAD PEER PATHS"
PCLI	show peers router bosdc1
	show peers router seabo1

Exercise 2	Configure Path Preference
Step 1	Verify Old WAN Link on Branch 1 Router
PCLI on Branch 1 Router	su admin Password: 128Tadmin
	show load-balancer router seabo1 service webserver show load-balancer Expand source admin@node1.seabo1# show load-balancer service webserver Thu 2021-05-06 13:44:26 UTC =============================================================================== Service: webserver Strategy: hunt +-----------------+-------------+-------+-----------+ \| Agent \| Destination \| Node \| Service \| +-----------------+-------------+-------+-----------+ \| webserver-route \| bosdc1 \| node1 \| webserver \| +-----------------+-------------+-------+-----------+ Capacity: ====== =========== ====== ====== Used Max Util Rate ====== =========== ====== ====== 2 unlimited 0/s Paths (count 2): wan1.0 gateway 3.3.3.128 ======== ========= ====== ======= ====== ========= ======== Type Quality Cost State Loss Latency Jitter ======== ========= ====== ======= ====== ========= ======== router 0 N/A up 0% 1ms 0ms mpls1.0 gateway 10.0.128.0 ======== ========= ====== ======= ====== ========= ======== Type Quality Cost State Loss Latency Jitter ======== ========= ====== ======= ====== ========= ======== router 0 N/A up 0% 1ms 0ms Completed in 0.81 seconds admin@node1.seabo1#
Step 2	Configure Service Policy
	Configuration > Authority ADD: Service Policies name prefer_mpls
	SET: Vectors: mpls. SET: priority of 1
	ADD: Vectors: broadband under SET: priority: 100
	Configuration > Authority > Services: webserver SET: Service Policy: prefer_mpls
	VALIDATE and COMMIT
Step 3	Verify Path Preference
PCLI on Branch 1 Router	su admin Password: 128Tadmin
	show load-balancer router seabo1 service webserver
	show load-balancer service webserver show load-balancer Expand source admin@node1.seabo1# show load-balancer service webserver Thu 2021-05-06 13:48:25 UTC =============================================================================== Service: webserver Strategy: hunt +-----------------+-------------+-------+-----------+ \| Agent \| Destination \| Node \| Service \| +-----------------+-------------+-------+-----------+ \| webserver-route \| bosdc1 \| node1 \| webserver \| +-----------------+-------------+-------+-----------+ Capacity: ====== =========== ====== ====== Used Max Util Rate ====== =========== ====== ====== 2 unlimited 0/s Paths (count 2): wan1.0 gateway 3.3.3.128 ======== ========= ====== ======= ====== ========= ======== Type Quality Cost State Loss Latency Jitter ======== ========= ====== ======= ====== ========= ======== router N/A 100 up 0% 2ms 0ms mpls1.0 gateway 10.0.128.0 ======== ========= ====== ======= ====== ========= ======== Type Quality Cost State Loss Latency Jitter ======== ========= ====== ======= ====== ========= ======== router N/A 1 up 0% 1ms 0ms Completed in 0.51 seconds admin@node1.seabo1#
	show fib show fib Expand source admin@node1.seabo1# show fib Thu 2021-05-06 13:48:50 UTC Node: node1 Entry Count: 75 Capacity: 19039 ==================== ======= ======= ============== ========================= ============ IP Prefix Port Proto Tenant Service Next Hops ==================== ======= ======= ============== ========================= ============ . . . . 172.16.128.2/32 <any> <any> <global> webserver 10.0.128.0 3.3.3.128 172.16.128.2/32 <any> <any> corp webserver 10.0.128.0 3.3.3.128 172.16.128.2/32 <any> <any> seattle.corp webserver 10.0.128.0 3.3.3.128 192.0.0.0/24 <any> <any> <global> <ControlMessageService> <none>
	repeat show device-interface name mpls1 show device-interface Expand source Running "show device-interface name mpls1" every 2 seconds Thu 2021-05-06 13:55:46 UTC ======================================== node1:mpls1 ======================================== Type: ethernet Forwarding: true PCI Address: 0000:00:04.0 MAC Address: 52:54:00:72:0e:4a Admin Status: up Operational Status: up Redundancy Status: non-redundant Speed: 1000 in-octets: 0 in-unicast-pkts: 4854 in-errors: 0 out-octets: 0 out-unicast-pkts: 4861 out-errors: 0 Completed in 0.12 seconds

Exercise 3	Configure a 2nd Service with a Different Path Preference
Step 1	Configure Service
	Configuration > Authority AD: Services name: webserver2
	ADD: Service Address: 172.26.128.2/32 SET: Security Policy: encryption_only
	SET: Access Policies ADD: Source: corp SET: permission: allow
Step 2	Configure Service Route
	Configuration > Authority > Routers: seabo1 ADD: Service Routes: webserver2-routes
	Service Name: webserver2 Service Route Tpe: Peer Service Route Peer: bosdc1
Step 3	Gather PCI Addresses for Datacenter Router 1
PCLI bosdc1	su admin Password: 128Tadmin # show platform >> srv2 PCI address
Step 4	Configure Interface on Datacenter Router 1
	Configuration > Authority > Routers: bosdc1 > Node: node1 > ADD Device Interface: srv2 Type: ethernet SET: PCI Address: Enter the PCI address of srv2 under
	ADD Network Interface: srv2 ADD next to Interface Addresses: 172.26.128.1 SET: Prefix: 30
Step 5	Configure Service Policy
	Configuration > Authority > ADD: Service Policies: broadband_only Vectors: broadband and Priority ordered Vectors: mpls and Priority: never
	configuration > Authority level > Services: webserver2 Service Policy: broadband_only
	VALIDATE and COMMIT
Step 6	Verify Server2 Connectivity
OPEN CONSOLE for Branch 1 Client	ping 172.26.128.2
	http://172.26.128.2
Step 7	Verify Path Preference
PCLI Open Console for Conductor	su admin Password: 128Tadmin
	show load-balancer router seabo1 service webserver2