This is an SD-WAN lab practical that will show how to configure WAN cloud components. You can practice along with this practical, using our SD-WAN virtual lab.

Tasks
Configure hostname as “Internet-Cloud”, “MPLS-Cloud” and “HQ” (Without quotes) on Internet-Cloud, MPLS-Cloud, and HQ Routers respectively.
Configure IP addresses of Internet-Cloud and MPLS-Cloud Router on their respective Interfaces as per the IP schema given below and verify it with the logical topology diagram.
Internet-Cloud Router |
Interfaces | IP Address | Subnet Mask |
Eth0/0 | 172.16.3.2 | 255.255.255.0 |
Eth0/1 | 192.168.5.1 | 255.255.255.0 |
Eth0/2 | 172.16.4.1 | 255.255.255.0 |
Eth0/3 | 10.1.4.1 | 255.255.255.0 |
Eth1/0 | 192.168.4.1 | 255.255.255.0 |
MPLS-Cloud Router |
Eth0/0 | 192.168.3.2 | 255.255.255.0 |
Eth0/1 | 10.1.5.2 | 255.255.255.0 |
Eth0/2 | 172.16.6.1 | 255.255.255.0 |
Eth0/3 | 192.168.7.1 | 255.255.255.0 |
Eth1/0 | 10.1.7.1 | 255.255.255.0 |
HQ Router |
Eth0/0 | 200.1.1.1 | 255.255.255.0 |
Eth0/1 | 10.1.1.2 | 255.255.255.0 |
Eth0/2 | 192.168.3.1 | 255.255.255.0 |
Eth0/3 | 172.16.3.1 | 255.255.255.0 |
On Internet-Cloud Router
● Configure a static route for 200.1.1.0/24 network pointing towards HQ Router IP address 172.16.3.1
On MPLS-Cloud Router
● Configure and enable OSPF Area 0 on Interfaces (Eth0/0, Eth0/1, Eth0/2, Eth0/3, Eth1/0)
On HQ Router
● Configure and enable OSPF Area 0 on Interfaces (Eth0/0, Eth0/1, Eth0/2, Eth0/3)
● Make sure OSPF only sends and receives OSPF packets on the link towards the MPLS Cloud using the Passive-interface command.
● Configure a default route towards the Internet-Cloud Router IP address 172.16.3.2
● Configure BGP AS 65001 with source IP address as 10.1.1.2 and neighbor address as 10.1.1.1
● Redistribute OSPF into BGP
● Make sure there are no initial configurations on these devices
Online Cisco SD-WAN TrainingLearn from expert trainers and master SD-WAN.Explore course
Configuration and Verification
In this lab we will be configuring WAN cloud components, It includes HQ routers, Internet-Cloud, and MPLS-Cloud routers. These devices will provide network connectivity to all branch sites from SDWAN controllers.
Power on devices (HQ router, Internet-Cloud, and MPLS-Cloud routers). Using the console of these devices, first, we will configure hostnames and IP addresses as given in the task’s requirement.
Internet-Cloud
enable configure terminal hostname Internet-Cloud ! interface ethernet0/0 ip address 172.16.3.2 255.255.255.0 no shutdown interface ethernet0/1 ip address 192.168.5.1 255.255.255.0 no shutdown interface ethernet0/2 ip address 172.16.4.1 255.255.255.0 no shutdown interface ethernet0/3 ip address 10.1.4.1 255.255.255.0 no shutdown interface ethernet1/0 ip address 192.168.4.1 255.255.255.0 no shutdown end ! write |
Now verify the configured interface IP addresses on the Internet-Cloud router, all interfaces are showing up/up status.
ShapeInternet-Cloud#show ip interface brief Interface IP-Address OK? Method Status Protocol Ethernet0/0 172.16.3.2 YES manual up up Ethernet0/1 192.168.5.1 YES manual up up Ethernet0/2 172.16.4.1 YES manual up up Ethernet0/3 10.1.4.1 YES manual up up Ethernet1/0 192.168.4.1 YES manual up up |
MPLs Cloud
enable configure terminal hostname MPLS-Cloud ! interface ethernet0/0 ip address 192.168.3.2 255.255.255.0 no shutdown interface ethernet0/1 ip address 10.1.5.2 255.255.255.0 no shutdown interface ethernet0/2 ip address 172.16.6.1 255.255.255.0 no shutdown interface ethernet0/3 ip address 192.168.7.1 255.255.255.0 no shutdown interface ethernet1/0 ip address 10.1.7.1 255.255.255.0 no shutdown end ! write |
Verify the configured interface IP addresses on the MPLS-Cloud router, all interfaces are showing up/up status
MPLS-Cloud#show ip interface brief Interface IP-Address OK? Method Status Protocol Ethernet0/0 192.168.3.2 YES manual up up Ethernet0/1 10.1.5.2 YES manual up up Ethernet0/2 172.16.6.1 YES manual up up Ethernet0/3 192.168.7.1 YES manual up up Ethernet1/0 10.1.7.1 YES manual up up |
HQ
enable configure terminal hostname HQ ! interface ethernet0/0 ip address 200.1.1.1 255.255.255.0 no shutdown interface ethernet0/1 ip address 10.1.1.2 255.255.255.0 no shutdown interface ethernet0/2 ip address 192.168.3.1 255.255.255.0 no shutdown interface ethernet0/3 ip address 172.16.3.1 255.255.255.0 no shutdown ! write |
Verify the configured interface IP addresses on HQ router, all interfaces are showing up/up status, also verify the point-to-point connectivity from HQ to Internet-Cloud and MPLS-Cloud routers.
HQ#show ip interface brief Interface IP-Address OK? Method Status Protocol Ethernet0/0 200.1.1.1 YES manual up up Ethernet0/1 10.1.1.2 YES manual up up Ethernet0/2 192.168.3.1 YES manual up up Ethernet0/3 172.16.3.1 YES manual up up |
HQ#ping 192.168.3.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.3.2, timeout is 2 seconds: .!!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms HQ#ping 172.16.3.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.3.2, timeout is 2 seconds: .!!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms |
Now on Internet-Cloud configure a static route for network 200.1.1.0/24 (connecting HQ to SDWAN controllers) towards gateway HQ router IP address 172.16.3.1
Internet Cloud
enable configure terminal ! ip route 200.1.1.0 255.255.255.0 172.16.3.1 end ! write |
Verify that this static route is installed in its routing table and we can get the connectivity to
Internet-Cloud#show ip route 200.1.1.0 Routing entry for 200.1.1.0/24 Known via "static", distance 1, metric 0 Routing Descriptor Blocks: * 172.16.3.1 Route metric is 0, traffic share count is 1 Internet-Cloud#ping 200.1.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 200.1.1.1, timeout is 2 seconds: !!!!! |
On MPLS-Cloud router configure the OSPF Area 0 on all its interfaces, OSPF process can be any number
interface ethernet0/0 ip ospf 1 area 0 ip ospf network point-to-point interface ethernet0/1 ip ospf 1 area 0 ip ospf network point-to-point interface ethernet0/2 ip ospf 1 area 0 ip ospf network point-to-point interface ethernet0/3 ip ospf 1 area 0 ip ospf network point-to-point interface ethernet1/0 ip ospf 1 area 0 ip ospf network point-to-point end |
Verify if OSPF is enabled on all its interfaces but still its not forming OSPF neighborship with HQ because we have yet to configure OSPF on HQ.
MPLS-Cloud#show ip ospf interface brief Interface PID Area IP Address/Mask Cost State Nbrs F/C Et0/2 1 0 172.16.6.1/24 10 P2P 0/0 Et0/3 1 0 192.168.7.1/24 10 P2P 0/0 Et0/1 1 0 10.1.5.2/24 10 P2P 0/0 Et0/0 1 0 192.168.3.2/24 10 P2P 0/0 |
Now configure OSPF Area 0 on HQ (take any process ID) and it will only form OSPF neighborship with MPLS-Cloud router. Make sure OSPF network type point to point is also configured on HQ interface Ethernet 0/2 to avoid network type issue.
HQ
! router ospf 1 passive-interface default no passive-interface Ethernet0/2 network 200.1.1.1 0.0.0.0 area 0 network 10.1.1.2 0.0.0.0 area 0 network 192.168.3.1 0.0.0.0 area 0 network 172.16.3.1 0.0.0.0 area 0 exit interface Ethernet0/2 ip ospf network point-to-point end ! write ! |
Verify that the OSPF is configured on all interfaces and it is forming OSPF neighborship with the MPLS-Cloud router. HQ is also receiving routes from MPLS-Cloud.
HQ#show ip ospf interface brief Interface PID Area IP Address/Mask Cost State Nbrs F/C Et0/3 1 0 172.16.3.1/24 10 DR 0/0 Et0/2 1 0 192.168.3.1/24 10 P2P 1/1 Et0/1 1 0 10.1.1.2/24 10 DR 0/0 Et0/0 1 0 200.1.1.1/24 10 DR 0/0 HQ#show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 192.168.7.1 0 FULL/ - 00:00:36 192.168.3.2 Ethernet0/2 HQ#show ip route ospf Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP a - application route + - replicated route, % - next hop override Gateway of last resort is not set 10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks O 10.1.5.0/24 [110/20] via 192.168.3.2, 00:06:06, Ethernet0/2 O 10.1.7.0/24 [110/20] via 192.168.3.2, 00:06:06, Ethernet0/2 172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks O 172.16.6.0/24 [110/20] via 192.168.3.2, 00:06:06, Ethernet0/2 O 192.168.7.0/24 [110/20] via 192.168.3.2, 00:06:06, Ethernet0/2 |
Now configure a default route towards the Internet-Cloud Router IP address 172.16.3.2 and configure BGP AS 65001 with source IP address as 10.1.1.2 and neighbour address as 10.1.1.1 and redistribute OSPF into BGP
ip route 0.0.0.0 0.0.0.0 172.16.3.2 ! router bgp 65001 neighbor 10.1.1.1 remote-as 65001 redistribute ospf 1 end ! write |
Verify that the default route is installed on its routing table, BGP is configured and OSPF routes appear on the BGP table.
HQ#show ip route 0.0.0.0 Routing entry for 0.0.0.0/0, supernet Known via "static", distance 1, metric 0, candidate default path Routing Descriptor Blocks: * 172.16.3.2 Route metric is 0, traffic share count is 1 HQ#show ip bgp BGP table version is 10, local router ID is 200.1.1.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter, x best-external, a additional-path, c RIB-compressed, Origin codes: i - IGP, e - EGP, ? - incomplete RPKI validation codes: V valid, I invalid, N Not found Network Next Hop Metric LocPrf Weight Path *> 10.1.5.0/24 192.168.3.2 20 32768 ? *> 10.1.7.0/24 192.168.3.2 20 32768 ? *> 172.16.3.0/24 0.0.0.0 0 32768 ? *> 172.16.6.0/24 192.168.3.2 20 32768 ? *> 192.168.3.0 0.0.0.0 0 32768 ? *> 192.168.7.0 192.168.3.2 20 32768 ? *> 200.1.1.0 0.0.0.0 0 32768 ? |