Routing

Hi Dmitriy , So I did as you suggested. I created separate community names for each community. community target:11.11.11.11:700 members target:11.11.11.11:700; community target:22.22.22.22:700 members target:22.22.22.22:700; community target:44.44.44.44:700 ...

Hello Did you ever find an answer to this issue? we have the same problem today. our temporary solution is to use QFX5120Switch stack(2) as a router/gateway for these /30 subnets. please let me know if anyone found a better solution. Regards, ...

For Item 1 As I assumed, if you use import policy in your way, the policy tries to catch routes, which have all enumerated five communities . That's why that output is empty. vMX_R3> show route table bgp.l3vpn.0 community-name VPRN_700_Community ...

Hi, For Item 2 In the Operations we are used to apply policy on both: import and export. policy-statement VPRN_700_Policy { term 1 { from community VPRN_700_Community; then accept; } ...

Hi Dmitriy, Item 1 A little weird. cmendoza@vMX_R3> show route table bgp.l3vpn.0 community-name VPRN_700_Community bgp.l3vpn.0: 14 destinations, 28 routes (14 active, 0 holddown, 0 hidden) --> this is the whole output cmendoza@vMX_R3> ...

Hi, Looks like a filter problem, could you please share/check the lo0.0 filter? Are you blocking LDP? Regards, Alin ------------------------------ Bandiu Alin-Filip-Gabriel ------------------------------

1) Your output of vMX_R3> show route table bgp.l3vpn.0 doesn't show any attached community on the inet-vpn routes without "detail" option. With detail option it has so long outcome. That's why I asked to run the command vMX_R3>show route table bgp.l3vpn.0 ...