This topic is to discuss the following lesson:
1 Like
Hi @ReneMolenaar and @lagapidis ,
I have tested this with my lab.Service VPN is working fine.But I have some confusion because in my main dashboard it said partial wan connectivity.when I dig deeper I found that BFD sessions between two colors are down.
As far as I know WAN edge routers try to form overlay tunnels to every received TLOC from a different site using every available color.So can you please help me to understand this issue.Your help is highly appriciated
Update 
Actually after I configure default route from both vEdge routers Full WAN connectivity obtained.
But If I create static routes to obtain the same connectivity it is not working…
For a example :
If create following summery routes insted of defult route BFD is down between two colors.
ip route 10.65.0.0/16 10.65.91.100
ip route 10.65.0.0/16 10.65.92.100
Can you please explain what is the logic here …
In vEdge1 why next hop in is towards 10.65.91.100 , why not10.65.92.100…
Hello Himanshu
First of all, in this lab, there is no vEdge1, so I am assuming from the context, that you are referring to the output of vEdge3. Indeed, in the routing table of vEdge3, we see that in order to reach the network of 10.1.0.0/24, it says that the next-hop IP is 10.65.91.100.
Now, this is not necessarily incorrect, since, in the network diagram, you can see that vEdge3 does connect to the biz-internet cloud which is the 10.65.91.0/24 network. And you can see that the exit interface for vEdge3 to reach that network is Ge0/0 which is correctly indicated in the routing table.
You can see from the configs that this route is statically configured in vEdge3. It may just be that we want vEdge3 to reach this subnet via the biz-internet WAN rather than the public-internet WAN.
So you see, you can configure whatever routing you like, as long as it conforms to the needs of your network. In this particular case, we can assume that communication between Site1 and Site3 should take place via the “private” biz-internet WAN rather than via the public WAN.
I hope this has been helpful!
Laz
Hello,
Let’s say I have a router with 3 interfaces: 1 WAN interface and 2 LAN interfaces. The WAN interface is in VPN 0 and other 2 LAN interfaces are in VPN 10 and VPN 20. Are these three interfaces going to be able to talk to each other? If not, why and how can I make them talk to each other? Thanks a lot in advance.
Best Regards,
Azm
Hi @azmuddincisco ,
It is possible to configure route leaking between VPNs yes. It’s called route leaking. Cisco has some examples here:
Rene
So all my configurations look great but OMP is not advertising connected routes are configured on the VPN10 templates. When I type show omp routes I can see the routes pointing to both LAN switches installed but when I type show ip routes, I can see the OMP advertised routes and I can not ping across both LANs between sites 2 & 3. Any help? Am using the latest version of the controller and vEdge routers.
See attached and below:
system
host-name vEdge2
system-ip 172.16.1.2
site-id 2
admin-tech-on-failure
no route-consistency-check
no vrrp-advt-with-phymac
sp-organization-name mknet-sdwan
organization-name mknet-sdwan
vbond 10.1.0.2
aaa
auth-order local radius tacacs
usergroup basic
task system read write
task interface read write
!
usergroup netadmin
!
usergroup operator
task system read
task interface read
task policy read
task routing read
task security read
!
user admin
password $6$siwKBQ==$wT2lUa9BSreDPI6gB8sl4E6PAJoVXgMbgv/whJ8F1C6sWdRazdxorYYTLrL6syiG6qnLABTnrE96HJiKF6QRq1
!
ciscotacro-user true
ciscotacrw-user true
!
logging
disk
enable
!
!
ntp
parent
no enable
stratum 5
exit
!
support
zbfw-tcp-finwait-time 30
zbfw-tcp-idle-time 3600
zbfw-tcp-synwait-time 30
zbfw-udp-idle-time 30
!
!
omp
no shutdown
graceful-restart
advertise connected
advertise static
!
security
ipsec
integrity-type ip-udp-esp esp
!
!
banner
motd "Welcome to MKNet vEdge Router"
!
vpn 0
interface ge0/0
ip address 10.65.91.2/24
tunnel-interface
encapsulation ipsec
color biz-internet
allow-service all
no allow-service bgp
allow-service dhcp
allow-service dns
allow-service icmp
no allow-service sshd
no allow-service netconf
no allow-service ntp
no allow-service ospf
no allow-service stun
allow-service https
!
no shutdown
!
interface ge0/1
ip address 10.65.92.2/24
tunnel-interface
encapsulation ipsec
color public-internet
allow-service all
no allow-service bgp
allow-service dhcp
allow-service dns
allow-service icmp
no allow-service sshd
no allow-service netconf
no allow-service ntp
no allow-service ospf
no allow-service stun
allow-service https
!
no shutdown
!
ip route 10.1.0.0/24 10.65.91.100
!
vpn 10
interface ge0/3
ip address 10.2.0.254/24
no shutdown
!
omp
advertise connected
!
!
vpn 512
interface eth0
shutdown
!
!
system
host-name vEdge3
system-ip 172.16.1.3
site-id 3
admin-tech-on-failure
no route-consistency-check
no vrrp-advt-with-phymac
organization-name mknet-sdwan
vbond 10.1.0.2
aaa
auth-order local radius tacacs
usergroup basic
task system read
task interface read
!
usergroup netadmin
!
usergroup operator
task system read
task interface read
task policy read
task routing read
task security read
!
usergroup tenantadmin
!
user admin
password $6$3e3dc1598d9bdb68$/F.xg3onyxTe17w8xBu3NbGtrWHVxd5ic.bjr5iGJymzWzy1885H4jQf2/OkdABwI4txtVoyZTmArzYlDKiEE0
!
ciscotacro-user true
ciscotacrw-user true
!
logging
disk
enable
!
!
ntp
parent
no enable
stratum 5
exit
!
support
zbfw-tcp-finwait-time 30
zbfw-tcp-idle-time 3600
zbfw-tcp-synwait-time 30
zbfw-udp-idle-time 30
!
!
omp
no shutdown
graceful-restart
advertise connected
advertise static
!
security
ipsec
integrity-type ip-udp-esp esp
!
!
vpn 0
interface ge0/0
ip address 10.65.92.3/24
ipv6 dhcp-client
tunnel-interface
encapsulation ipsec
color public-internet
allow-service all
no allow-service bgp
allow-service dhcp
allow-service dns
allow-service icmp
no allow-service sshd
no allow-service netconf
no allow-service ntp
no allow-service ospf
no allow-service stun
allow-service https
!
no shutdown
!
interface ge0/1
ip address 10.65.93.1/24
tunnel-interface
encapsulation ipsec
color mpls
allow-service all
no allow-service bgp
allow-service dhcp
allow-service dns
allow-service icmp
no allow-service sshd
no allow-service netconf
no allow-service ntp
no allow-service ospf
no allow-service stun
allow-service https
!
no shutdown
!
ip route 10.1.0.0/24 10.65.92.100
!
vpn 10
interface ge0/3
ip address 10.3.0.254/24
no shutdown
!
omp
advertise connected
!
!
vpn 512
interface eth0
ip dhcp-client
ipv6 dhcp-client
no shutdown
!
!
Hi @bansah29 ,
You might have solved this by now but if you still have issues, see if your output matches mine here:
https://notes.networklessons.com/cisco-sd-wan-verify-connectivity-in-service-vpn
Rene
Hi Rene and team,
I cannot seem to see my omp routes on vpn 0 route table
I also cannot ping both vedges WAN form LAN side
Here is the problem below, I do not seem to be able to ping any interface off my LAN interface
Literally drops at the edge
Also, VPN0 routes table not showing omp routes
Also, VPN0 routes table not showing omp routes
Any thoughts?
Hi Rene,
Upon successfully onboarded both vEdge and cEdge, traffic is able to route via MPLS or Biz-internet where I could ping 8.8.8.8. But I notice hosts behind service VPN / VRF (vEdge and cEdge) are not able to ping to 8.8.8.8. Traffic is not passing vEdge and cEdge.
I believed need to Leak Routes between Global VRF and Service VPNs or is there anything I have missed?
Tired the command below, not sure why both route-replicate and global-address-family ipv4 command is missing below on cEdge?
Also for route leak how do I configure using CLI on vEdge?
cEdge(config-ipv4)# vrf definition 1
cEdge(config-vrf)# address-family ipv4
cEdge(config-ipv4)# route-replicate from vrf global unicast connected
-----------------------^
syntax error: unknown argument
cEdge(config-ipv4)#
**Configuration on cEdge vrf 1**
cEdge-30#sh run vrf
Building configuration...
Current configuration : 546 bytes
vrf definition 1
rd 1:1
!
address-family ipv4
route-target export 1:1
route-target import 1:1
exit-address-family
!
!
interface GigabitEthernet3
description Link to LAN
vrf forwarding 1
ip address 10.0.30.30 255.255.255.0
negotiation auto
no mop enabled
no mop sysid
!
ip route vrf 1 0.0.0.0 0.0.0.0 172.16.10.1 global
ip route vrf 1 0.0.0.0 0.0.0.0 172.16.20.1 global
vrf definition 65528
!
address-family ipv4
exit-address-family
!
!
interface Loopback65528
vrf forwarding 65528
ip address 192.168.1.1 255.255.255.255
!
end
cEdge-30#
**Configuration for vEdge VPN 1**
vEdge-10# show run vpn 1
vpn 1
name INSIDE
router
ospf
router-id 10.10.10.10
timers spf 200 1000 10000
redistribute connected
redistribute omp
area 10
interface ge0/3
exit
exit
!
bgp 10
address-family ipv4-unicast
redistribute omp
!
neighbor 10.0.10.101
no shutdown
remote-as 10
!
!
!
interface ge0/3
description "Service VPN 1"
ip address 10.0.10.10/24
no shutdown
!
interface loopback1
description "Interface loopback1"
ip address 1.1.1.10/32
no shutdown
!
interface loopback2
description "Interface loopback2"
ip address 2.2.2.10/32
no shutdown
!
omp
advertise ospf external
advertise connected
advertise static
!
!
vEdge-10#
Hello @kent2612 ,
With 8.8.8.8, you mean Google DNS right? Not some loopback with this IP address that you use in your topology?
I don’t have an example ready, but what you should look for is Direct Internet Access. It requires NAT and a policy to make it work, but this is what allows a service VPN to access the Internet.
Rene
Hi, It is exactly same problem I have with version 20.1.1.
OMP is not advertising connected routes are configured on the VPN10. I have tried by using cli and templates, in both cases OMP not advertising vpn 10 connected network.
The SDWAN control connections are up; no BFD sessions. I could not make BFD sessions the be up.
Hello Abdussalam
Have you taken a look at this response from Rene?
Please take a look and see if you get similar output with that in the lesson. If not, let us know so we can help you further.
I hope this has been helpful!
Laz
Hi,
Yes I have, I cant see omp route in routing table #show ip route vpn 10.
The issue is BFD is down, this will cause omp to not work.
I can ping from vEdge to vsmart, vbond and vmanage. vpn 0 is working fine.
What about pinging between two vEdge routers?
https://notes.networklessons.com/cisco-sd-wan-verify-connectivity-in-service-vpn#test-reachability
Does that work too?