!
--------------------------
! vEdge Sites Configuration
!--------------------------
The configuration of vEdge Routers through the CLI is described in this Document:
https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-
book/cisco-sd-wan-overlay-network-
bringup.html#c_Create_vEdge_Cloud_VM_Instance_on_ESXi_7846.xml
So please refer to this URL for more details about this configuration
!------------------
! Site-101-vEdge1
!------------------
!
conf t
system
host-name Site-101-vEdge1
system-ip 1.1.1.101
site-id 101
organization-name Ciscoland
vbond 10.1.1.2
!
vpn 512
! This is the Default Gateway for Local Network
int eth0
description "Connection to Site-101-Host"
no shut
ip address 192.168.101.254/24
exit
exit
!----------------------------------------------------------------
! Interfaces to the Internet & MPLS Routers should be under VPN 0
! Optionally we can also configure DNS for VPN 0
!
! Although here we configure Interface ge0/1 as the Connection
! to the Internet-Router, the actual Internet Connection is provided
! through the Lab's Local Network Internet Gateway ==> 192.168.15.254
!
! This Router is also a DNS Server!
! Therefore, we'll configure this IP Address as the DNS Server
!----------------------------------------------------------------
vpn 0
dns 192.168.15.254
no interface ge0/0
! This is the Default Route that points to the Internet-Router
ip route 0.0.0.0/0 200.200.100.5
interface ge0/1
description "Connection to Internet-Router"
no shut
ip address 200.200.100.6/30
tunnel-interface
encapsulation ipsec
! vEdges, like vBond, doe need: encapsulation ipsec!
allow-service all
color public-internet
interface ge0/2
description "Connection to MPLS-Router"
no shut
ip address 172.16.1.6/30
tunnel-interface
encapsulation ipsec
! vEdges, like vBond, doe need: encapsulation ipsec!
allow-service all
color mpls
commit and-quit
!----------------------------------------------------------------------
! After Configuration is done, we should have Reachability from vManage
! That is, we should be able to ping the vEdge and SSH to it
!
! To SSH to the vEdge, we must enter vshell mode
! The ping Command can be run either from CLI or vshell mode
! So we'll do BOTH in vshell mode
!----------------------------------------------------------------------
vManage# vshell
vManage:~$
vManage:~$ ping 200.200.100.6
PING 200.200.100.6 (200.200.100.6) 56(84) bytes of data.
64 bytes from 200.200.100.6: icmp_seq=1 ttl=62 time=41.2 ms
64 bytes from 200.200.100.6: icmp_seq=2 ttl=62 time=42.2 ms
64 bytes from 200.200.100.6: icmp_seq=3 ttl=62 time=45.7 ms
viptela 18.4.4
[email protected]'s password:
Welcome to Viptela CLI
admin connected from 10.1.1.1 using ssh on Site-101-vEdge1
Site-101-vEdge1#
Site-101-vEdge1# exit
!------------------
! Site-102-vEdge2
!------------------
!
conf t
system
host-name Site-102-vEdge2
system-ip 1.1.1.102
site-id 102
organization-name Ciscoland
vbond 10.1.1.2
!
vpn 512
! This is the Default Gateway for Local Network
int eth0
description "Connection to Site-102-Host"
no shut
ip address 192.168.102.254/24
exit
exit
!----------------------------------------------------------------
! Interfaces to the Internet & MPLS Routers should be under VPN 0
! Optionally we can also configure DNS for VPN 0
!
! Although here we configure Interface ge0/1 as the Connection
! to the Internet-Router, the actual Internet Connection is provided
! through the Lab's Local Network Internet Gateway ==> 192.168.15.254
!
! This Router is also a DNS Server!
! Therefore, we'll configure this IP Address as the DNS Server
!----------------------------------------------------------------
vpn 0
dns 192.168.15.254
no interface ge0/0
! This is the Default Route that points to the Internet-Router
ip route 0.0.0.0/0 200.200.100.9
interface ge0/1
description "Connection to Internet-Router"
no shut
ip address 200.200.100.10/30
tunnel-interface
encapsulation ipsec
! vEdges, like vBond, doe need: encapsulation ipsec!
allow-service all
color public-internet
interface ge0/2
description "Connection to MPLS-Router"
no shut
ip address 172.16.1.10/30
tunnel-interface
encapsulation ipsec
! vEdges, like vBond, doe need: encapsulation ipsec!
allow-service all
color mpls
commit and-quit
!----------------------------------------------------------------------
! After Configuration is done, we should have Reachability from vManage
! That is, we should be able to ping the vEdge and SSH to it
!
! To SSH to the vEdge, we must enter vshell mode
! The ping Command can be run either from CLI or vshell mode
! So we'll do BOTH in vshell mode
!----------------------------------------------------------------------
vManage# vshell
vManage:~$
vManage:~$ ping 200.200.100.10
PING 200.200.100.10 (200.200.100.10) 56(84) bytes of data.
64 bytes from 200.200.100.10: icmp_seq=1 ttl=62 time=39.6 ms
64 bytes from 200.200.100.10: icmp_seq=2 ttl=62 time=55.1 ms
64 bytes from 200.200.100.10: icmp_seq=3 ttl=62 time=42.8 ms
viptela 18.4.4
[email protected]'s password:
Last login: Sun Mar 7 20:06:45 2021 from 10.1.1.1
Welcome to Viptela CLI
admin connected from 10.1.1.1 using ssh on Site-102-vEdge2
Site-102-vEdge2#
Site-102-vEdge2# exit
!------------------
! Site-103-vEdge3
!------------------
!
conf t
system
host-name Site-103-vEdge3
system-ip 1.1.1.103
site-id 103
organization-name Ciscoland
vbond 10.1.1.2
!
vpn 512
! This is the Default Gateway for Local Network
int eth0
description "Connection to Site-103-Host"
no shut
ip address 192.168.103.254/24
exit
exit
!----------------------------------------------------------------
! Interfaces to the Internet & MPLS Routers should be under VPN 0
! Optionally we can also configure DNS for VPN 0
!
! Although here we configure Interface ge0/1 as the Connection
! to the Internet-Router, the actual Internet Connection is provided
! through the Lab's Local Network Internet Gateway ==> 192.168.15.254
!
! This Router is also a DNS Server!
! Therefore, we'll configure this IP Address as the DNS Server
!----------------------------------------------------------------
vpn 0
dns 192.168.15.254
no interface ge0/0
! This is the Default Route that points to the Internet-Router
ip route 0.0.0.0/0 200.200.100.13
interface ge0/1
description "Connection to Internet-Router"
no shut
ip address 200.200.100.14/30
tunnel-interface
encapsulation ipsec
! vEdges, like vBond, doe need: encapsulation ipsec!
allow-service all
color public-internet
interface ge0/2
description "Connection to MPLS-Router"
no shut
ip address 172.16.1.14/30
tunnel-interface
encapsulation ipsec
! vEdges, like vBond, doe need: encapsulation ipsec!
allow-service all
color mpls
commit and-quit
!----------------------------------------------------------------------
! After Configuration is done, we should have Reachability from vManage
! That is, we should be able to ping the vEdge and SSH to it
!
! To SSH to the vEdge, we must enter vshell mode
! The ping Command can be run either from CLI or vshell mode
! So we'll do BOTH in vshell mode
!----------------------------------------------------------------------
vManage# vshell
vManage:~$
vManage:~$ ping 200.200.100.14
PING 200.200.100.14 (200.200.100.14) 56(84) bytes of data.
64 bytes from 200.200.100.14: icmp_seq=1 ttl=62 time=54.8 ms
64 bytes from 200.200.100.14: icmp_seq=2 ttl=62 time=51.1 ms
64 bytes from 200.200.100.14: icmp_seq=3 ttl=62 time=54.6 ms
viptela 18.4.4
[email protected]'s password:
Last login: Sun Mar 7 20:10:19 2021 from 10.1.1.1
Welcome to Viptela CLI
admin connected from 10.1.1.1 using ssh on Site-103-vEdge3
Site-103-vEdge3#
Site-103-vEdge3# exit
