[j-nsp] Juniper equivalent of Cisco redistribute in a VRF

[Aleksander Zawisza]

Thank you, that explains it.

Regards,
Aleks


-----Original Message-----
From: Piotr Marecki [mailto:p.marecki at swiat.pl] 
Sent: July 21, 2004 6:57 AM
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Juniper equivalent of Cisco redistribute in a VRF


Ehlo

Actually this should work since order of operation is like
1) redistribute-connected -> export route-target -> export map ->  MP-BGP
family VPN-IPv4

My bet is that you don't include "neighbor x.x.x.x send-community both"
under family vpnv4  since by default cisco routers won't send community
attribute along with extended community for AFI/SAFI 1/128.

2)
In juniper you should add community under policy-statement that is applied
to "vrf-export" under routing-instance xxxx stanza , for example [edit
policy-options policy-statement siteX-export] term term1 {
    from protocol  direct ;
    then {
        community add siteX-inet-export;                #target:100:200
        community add community-connected;        #12345:1
        accept;
    }
}
term default {
    then reject;
}

regards

Piotr Marecki
Netia S.A


----- Original Message ----- 
From: "Aleksander Zawisza" <aleks at nortelnetworks.com>
To: <juniper-nsp at puck.nether.net>
Sent: Tuesday, July 20, 2004 11:23 PM
Subject: [j-nsp] Juniper equivalent of Cisco redistribute in a VRF


> Hi,
> What would be the Juniper equivalent of the following line in the 
> Cisco config below:  redistribute connected route-map 
> SET-COMMUNITY-CONNECTED Is this a vrf export policy? If so, since I 
> already have an export map for the VRF (EXPORT-MY-VRF), what order do 
> these get applied in? If not, what does this policy apply to? When I 
> trace the updates I'm getting from this Cisco on a Juniper inet-vpn 
> RR, I don't see the community 12345:1.
>
> !
> ip vrf MY-VRF
> ...
>  export map EXPORT-MY-VRF
>  route-target import 100:100
> ...
> !
>
> router bgp 10000
>  !
>  # stuff
>  !
>  address-family ipv4 vrf MY-VRF
>  redistribute connected route-map SET-COMMUNITY-CONNECTED  neighbor 
> 66.1.1.2 remote-as 65500  neighbor 66.1.1.2 activate
>  neighbor 66.1.1.2 prefix-list MY-LIST in
>  no auto-summary
>  no synchronization
>  exit-address-family
>  !
> !
> route-map EXPORT-MY-VRF permit 10
>  match community 120
>  set extcommunity rt  100:200
> !
> route-map SET-COMMUNITY-CONNECTED permit 10
>  set community 12345:1
> !
>
> Thanks,
> Aleks
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp