Sunday, July 25, 2021

Viptela | vSmart not advertising prefixes to specific vEdge?

Hi, I'm reviewing how routes is being advertised and upon adding additional site (vedge3) with different vpn 10 I noticed that routes still separated on overlay network. I have resolve the issue although seeking more inputs about this. Here is my setup.

I have 3 vedges which represent 3 separate sites and 1 vSmart in my Lab but the issue is that vSmart not sending the prefixes received from vEdge 1 & 2 to vEdge 3... Also vSmart received the prefix from vEdge but it is not advertised to any of the vEdges?

Vedge name and it's prefix: vEdge#1 - vpn 1 - 10.0.10.0/24 vEdge#2 - vpn 1 - 10.0.20.0/24 vEdge#3 - vpn 10 - 10.0.50.3/24 vEdge#1# show omp routes | t PATH ATTRIBUTE VPN PREFIX FROM PEER ID LABEL STATUS TYPE TLOC IP COLOR ENCAP PREFERENCE -------------------------------------------------------------------------------------------------------------------------------------- 1 10.0.10.0/24 0.0.0.0 66 1002 C,Red,R installed 1.1.200.1 mpls ipsec - 0.0.0.0 68 1002 C,Red,R installed 1.1.200.1 biz-internet ipsec - 1 10.0.20.0/24 1.1.1.2 1 1002 C,I,R installed 1.1.201.1 biz-internet ipsec - 1.1.1.2 2 1002 C,I,R installed 1.1.201.1 mpls ipsec - Note: vEdge1 unable to see prefix from vedge3 vEdge#3# show omp routes | t PATH ATTRIBUTE VPN PREFIX FROM PEER ID LABEL STATUS TYPE TLOC IP COLOR ENCAP PREFERENCE -------------------------------------------------------------------------------------------------------------------------------------- 10 10.0.50.0/24 0.0.0.0 68 1004 C,Red,R installed 1.1.50.3 biz-internet ipsec - Note: vEdge3 unable to see prefixes from vedge1/2 

The only different is the service VPN of vEdge3 which is VPN 10? Does it needs to be on the same service VPN?

If yes, Does VPN ID is visible on omp route attributes?

vsmart# show omp routes 10.0.50.0/24 detail --------------------------------------------------- omp route entries for vpn 10 route 10.0.50.0/24 --------------------------------------------------- RECEIVED FROM: peer 1.1.50.3 path-id 68 label 1004 status C,R loss-reason not set lost-to-peer not set lost-to-path-id not set Attributes: originator 1.1.50.3 type installed tloc 1.1.50.3, biz-internet, ipsec ultimate-tloc not set domain-id not set overlay-id 1 site-id 500 preference not set tag not set origin-proto connected origin-metric 0 as-path not set unknown-attr-len not set 

I cannot see any attributes related to VPN 10... or this can be only seen using this command "show omp services"

In instance that we need to allow specific routes from one vpn to another vpn.. is this possible ? and would you recommend to do it? any risk?

Thank you



No comments:

Post a Comment