Send route across sdwan

[interfacedy]

Hi there is bgp neighbor relation between R3 and vEdge3, between R6 and vEdge6. R6 can ping R3. Can we send 6.6.6.6 to R3?　

R3---vEdge3-- --cloud ----vEdge6---R6--6.6.6.6/32

[Kanan Huseynli · Accepted solution]

Hi,

simple...advertise 6.6.6.6/32 from R6 to vEdge6 via BGP (you can archive by just network 6.6.6.6 mask 255.255.255.255 command in BGP process) do mutual redistribution between OMP and BGP on vEdge6.

[interfacedy]

Thanks for your reply. Is there example to configure the redistribute mutually? 

[Kanan Huseynli · Accepted solution]

Hi,

under OMP template, in "ADVERTISE" section, select "on" option for BGP. This enables redistribution of BGP routes into OMP.

Under BGP template, in "UNICAST ADDRESS FAMILY" section, select "New Redistribute" and from drop-down menu select "omp" add and push config.

[interfacedy]

Thank you very much. One OMP feature template is created, but where to add it in this device template? I can add bgp template into device template, i cannot find option that i can add the omp template into device template. 

[Kanan Huseynli]

Hi,

in device template, there is subsection "Basic Information". It contains OMP template and normally default template is chosen.

See below which is from my-lab:

The first two templates are default created, the "vEdge_OMP" is what I've created

[interfacedy]

I found it, Thanks. but just before pushing the device template into vedge, i got the below error message. Looks like something relateted with ipv6. i never touch ipv6

[Kanan Huseynli]

Hi,

most probably you have chosen wrong template.You should create your OMP template (ipv4) and choose it.

[interfacedy]

Another omp template is created and no issue to attach to vEdge6, but in vEdge6 cannot see route 6.6.6.6. bgp routes configured is correct in R6. Maybe there is issue in below vEdge6 config.  bgp neighbor can be seen between vEdge6 and R6

omp
no shutdown
graceful-restart
advertise bgp
advertise ospf external
advertise connected
advertise static
advertise eigrp
!
security
ipsec
authentication-type sha1-hmac ah-sha1-hmac
!
!
vpn 0
interface ge0/0
ip address 172.16.20.6/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 172.16.30.6/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 0.0.0.0/0 172.16.20.100
ip route 0.0.0.0/0 172.16.30.100
!
vpn 10
router
bgp 1
address-family ipv4-unicast
redistribute omp
!
neighbor 10.2.1.101
no shutdown
remote-as 1
!
!
!
interface ge0/2
ip address 10.2.1.1/24
no shutdown
!
omp
advertise connected

[Kanan Huseynli]

Hi,

I've already answered to this question. Subnet is behind R6, so you need to advertise it from R6 and vEdge6 will receive that prefix.

[interfacedy]

Thank you Kanan!