Lets say we have two edge router.
vEdge1 and vEdge2.
I configured vEdge 1 through template and Evdge 2 via CLI.
Design is VERY much similar, what we are learning here.
Problem - I don’t see route of connected switch’ with vEedge2 in VEdge1 and vice-versa.
vEdge1# show ip route
Codes Proto-sub-type:
IA -> ospf-intra-area, IE -> ospf-inter-area,
E1 -> ospf-external1, E2 -> ospf-external2,
N1 -> ospf-nssa-external1, N2 -> ospf-nssa-external2,
e -> bgp-external, i -> bgp-internal
Codes Status flags:
F -> fib, S -> selected, I -> inactive,
B -> blackhole, R -> recursive
PROTOCOL NEXTHOP NEXTHOP NEXTHOP
VPN PREFIX PROTOCOL SUB TYPE IF NAME ADDR VPN TLOC IP COLOR ENCAP STATUS
---------------------------------------------------------------------------------------------------------------------------------------------
0 10.1.0.0/24 static - ge0/0 10.199.199.254 - - - - F,S
0 10.19.19.0/24 connected - ge0/1 - - - - - F,S
0 10.199.199.0/24 connected - ge0/0 - - - - - F,S
0 172.16.1.1/32 connected - system - - - - - F,S
10 10.2.0.0/24 connected - ge0/2 - - - - - F,S
vEdge1# show ipsec outbound-connections
SOURCE SOURCE DEST DEST REMOTE REMOTE AUTHENTICATION NEGOTIATED PEER PEER
IP PORT IP PORT SPI TUNNEL MTU TLOC ADDRESS TLOC COLOR USED KEY-HASH ENCRYPTION ALGORITHM TC SPIs KEY-HASH SPI
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
10.199.199.2 12386 10.19.19.2 12406 259 1442 172.16.1.2 biz-internet AH_SHA1_HMAC *****14cf AES-GCM-256 8 NONE 0
vEdge1# show run vpn 10
vpn 10
interface ge0/2
ip address 10.2.0.254/24
no shutdown
!
omp
advertise connected
!
!
vEdge2# show ip route
Codes Proto-sub-type:
IA -> ospf-intra-area, IE -> ospf-inter-area,
E1 -> ospf-external1, E2 -> ospf-external2,
N1 -> ospf-nssa-external1, N2 -> ospf-nssa-external2,
e -> bgp-external, i -> bgp-internal
Codes Status flags:
F -> fib, S -> selected, I -> inactive,
B -> blackhole, R -> recursive
PROTOCOL NEXTHOP NEXTHOP NEXTHOP
VPN PREFIX PROTOCOL SUB TYPE IF NAME ADDR VPN TLOC IP COLOR ENCAP STATUS
---------------------------------------------------------------------------------------------------------------------------------------------
0 10.1.0.0/24 static - ge0/0 10.19.19.254 - - - - F,S
0 10.19.19.0/24 connected - ge0/0 - - - - - F,S
0 10.199.199.0/24 connected - ge0/1 - - - - - F,S
0 172.16.1.2/32 connected - system - - - - - F,S
10 10.3.0.0/24 connected - ge0/2 - - - - - F,S
vEdge2# show ipsec outbound-connections
SOURCE SOURCE DEST DEST REMOTE REMOTE AUTHENTICATION NEGOTIATED PEER PEER
IP PORT IP PORT SPI TUNNEL MTU TLOC ADDRESS TLOC COLOR USED KEY-HASH ENCRYPTION ALGORITHM TC SPIs KEY-HASH SPI
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
10.19.19.2 12406 10.199.199.2 12386 259 1442 172.16.1.1 biz-internet AH_SHA1_HMAC *****0c2a AES-GCM-256 8 NONE 0
vEdge2# show run vpn 10
vpn 10
interface ge0/2
ip address 10.3.0.254/24
no shutdown
!
!
vSmart1# show omp peers
R -> routes received
I -> routes installed
S -> routes sent
DOMAIN OVERLAY SITE
PEER TYPE ID ID ID STATE UPTIME R/I/S
-------------------------------------------------------------------------------- ----------
172.16.1.1 vedge 1 1 2 up 0:13:13:03 1/0/1
172.16.1.2 vedge 1 1 3 up 0:12:35:31 1/0/1