<div dir="ltr"><div><div><div><div><div><div>I was thinking about something like this:<br></div><div><br>router bgp x<br></div> address-family ipv4 vrf vrf-a<br></div> redistribute connected<br></div> address-familiy ipv4 vrf vrf-b<br>
</div> redistribute connected<br></div> address-family vpnv4 unicast<br>
<br></div>I don't know if it works, but maybe you can try it on a testbox?<br><div><div class="gmail_extra"><br><div class="gmail_quote">On 1 September 2014 20:37, Alexander Shikoff <span dir="ltr"><<a href="mailto:minotaur@crete.org.ua" target="_blank">minotaur@crete.org.ua</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<div><br>
On Mon, Sep 01, 2014 at 07:25:36PM +0200, Wouter Prins wrote:<br>
> hi Alexander,<br>
> Have you tried redistributing vrf-a to vpnv4 and export it to vrf-b to see if the bgp<br>
> attributes are available?<br>
</div>I cannot find a way how to do that.<br>
<div><br>
> AFAIK, import/export belongs to the vpnv4 afi and not to vrf-lite functionality.<br>
</div><div>vrf Crimea-IX<br>
rd 31210:39751<br>
address-family ipv4<br>
</div> route-target export 31210:39751<br>
route-target import 31210:31210<br>
route-target import 31210:39751<br>
exit-address-family<br>
exit-vrf<br>
<br>
There is no address-family vpnv4 within vrf configuration:<br>
<a href="mailto:telnet@lsr1-gdr.ki" target="_blank">telnet@lsr1-gdr.ki</a>(config)#vrf Crimea-IX<br>
<a href="mailto:telnet@lsr1-gdr.ki" target="_blank">telnet@lsr1-gdr.ki</a>(config-vrf-Crimea-IX)#address-family ?<br>
ipv4 IPv4 address Family<br>
ipv6 IPv6 address Family<br>
<div><br>
<br>
> On 27 August 2014 14:38, Alexander Shikoff <[1]<a href="mailto:minotaur@crete.org.ua" target="_blank">minotaur@crete.org.ua</a>> wrote:<br>
><br>
> Hi Eldon,<br>
><br>
> On Wed, Aug 13, 2014 at 04:53:05PM -0600, Eldon Koyle wrote:<br>
> > I suspect you are actually wanting to look at the vpn route. You<br>
> > probably need to run:<br>
</div>> > show ip bgp vpnv4 route [2]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a><br>
<div>> > 'show ip bgp vrf NAME' only shows routes learned via the BGP neighbors<br>
> > within the VRF, not the vpn routes; that is to say the routes learned<br>
> > from neighbors such as:<br>
> ><br>
> > router bgp<br>
> > ...<br>
> > address-family ipv4 unicast vrf NAME<br>
> > neighbor ...<br>
> ><br>
> > These routes are then redistributed across your provider routers via the<br>
> > BGP vpnv4 address family.<br>
><br>
> Thank you for suggestion. But I'm afraid I didn't understand you clearly.<br>
</div>> [3]<a href="http://telnet@lsr1-gdr.ki#show" target="_blank">telnet@lsr1-gdr.ki#show</a> ip bgp vpnv4 route [4]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a><br>
<div><div>> BGP Routing Table is empty<br>
> I don't need any VPN. I have a single box with two BGP neighbors connected to,<br>
> each neighbor in separate VRF.<br>
> In one VRF I need to import routes from different VRF and announce them to BGP<br>
> neighbor. But I cannot do that because BGP attributes is lost during import.<br>
><br>
> > --<br>
> > Eldon Koyle<br>
> > --<br>
> > If built in great numbers, motels will be used for nothing but illegal<br>
> > purposes.<br>
> > -- J. Edgar Hoover<br>
> ><br>
> > On Aug 13 16:24+0300, Alexander Shikoff wrote:<br>
> > > Hi!<br>
> > ><br>
> > > I have two VRFs on MLXe-16 box and I noticed that exported routes<br>
> > > from one VRF to other lost their BGP attributes.<br>
> > ><br>
> > > vrf Crimea-IX<br>
> > > rd 31210:39751<br>
> > > address-family ipv4<br>
> > > import routes vrf DTEL-IX route-map rm-BGP-and-Direct<br>
> > > exit-address-family<br>
> > > exit-vrf<br>
> > > !<br>
> > > vrf DTEL-IX<br>
> > > rd 31210:31210<br>
> > > address-family ipv4<br>
> > > import routes vrf Crimea-IX route-map rm-Crimea-IX2DTEL-IX<br>
> > > exit-address-family<br>
> > > exit-vrf<br>
> > ><br>
> > ><br>
> > > The routes are exported from Crimea-IX to DTEL-IX, for example:<br>
> > ><br>
</div></div>> > > [5]<a href="http://telnet@lsr1-gdr.ki#show" target="_blank">telnet@lsr1-gdr.ki#show</a> ip route vrf DTEL-IX [6]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a><br>
<div>> > > Type Codes - B:BGP D:Connected I:ISIS O:OSPF R:RIP S:Static; Cost - Dist/Metric<br>
> > > BGP Codes - i:iBGP e:eBGP<br>
> > > ISIS Codes - L1:Level-1 L2:Level-2<br>
> > > OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2 s:Sham Link<br>
> > > STATIC Codes - d:DHCPv6<br>
> > > Destination Gateway Port Cost Type Uptime<br>
> src-vrf<br>
</div>> > > 1 [7]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a> 193.34.200.141 ve 205 20/0 Be 25m23s<br>
<div>> Crimea-IX<br>
> > ><br>
> > ><br>
> > > In Crimea-IX this route has all its attributes:<br>
</div>> > > [8]<a href="http://telnet@lsr1-gdr.ki#show" target="_blank">telnet@lsr1-gdr.ki#show</a> ip bgp vrf Crimea-IX route [9]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a><br>
<div>> > > Number of BGP Routes matching display condition : 1<br>
> > > Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED<br>
> > > E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH<br>
> > > S:SUPPRESSED F:FILTERED s:STALE<br>
> > > Prefix Next Hop MED LocPrf Weight Status<br>
</div>> > > 1 [10]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a> 193.34.200.141 100 0 BE<br>
<div>> > > AS_PATH: 42896 15169<br>
> > > Last update to IP routing table: 0h26m44s, 1 path(s) installed:<br>
> > > Route is not advertised to any peers<br>
> > ><br>
> > > In DTEL-IX this route has no attributes already:<br>
> > ><br>
</div>> > > [11]<a href="http://telnet@lsr1-gdr.ki#show" target="_blank">telnet@lsr1-gdr.ki#show</a> ip bgp vrf DTEL-IX route [12]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a><br>
<div>> > > BGP4 : None of the BGP4 routes match the display condition<br>
> > ><br>
> > ><br>
> > > Is there any way to keep BGP attributes when exporting routes ?<br>
> > ><br>
> > > Thanks in advance!<br>
> > ><br>
> > > --<br>
> > > MINO-RIPE<br>
> > > _______________________________________________<br>
> > > foundry-nsp mailing list<br>
</div>> > > [13]<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> > > [14]<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
<div>> > ><br>
> --<br>
> MINO-RIPE<br>
> _______________________________________________<br>
> foundry-nsp mailing list<br>
</div>> [15]<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> [16]<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
><br>
> --<br>
> Wouter Prins<br>
> [17]<a href="mailto:wp@null0.nl" target="_blank">wp@null0.nl</a><br>
><br>
> Ссылки<br>
><br>
> 1. mailto:<a href="mailto:minotaur@crete.org.ua" target="_blank">minotaur@crete.org.ua</a><br>
> 2. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 3. <a href="http://telnet@lsr1-gdr.ki/#show" target="_blank">http://telnet@lsr1-gdr.ki/#show</a><br>
> 4. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 5. <a href="http://telnet@lsr1-gdr.ki/#show" target="_blank">http://telnet@lsr1-gdr.ki/#show</a><br>
> 6. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 7. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 8. <a href="http://telnet@lsr1-gdr.ki/#show" target="_blank">http://telnet@lsr1-gdr.ki/#show</a><br>
> 9. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 10. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 11. <a href="http://telnet@lsr1-gdr.ki/#show" target="_blank">http://telnet@lsr1-gdr.ki/#show</a><br>
> 12. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 13. mailto:<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> 14. <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
> 15. mailto:<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> 16. <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
> 17. mailto:<a href="mailto:wp@null0.nl" target="_blank">wp@null0.nl</a><br>
<span><font color="#888888"><br>
--<br>
MINO-RIPE<br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>Wouter Prins<br><a href="mailto:wp@null0.nl" target="_blank">wp@null0.nl</a><br><br>
</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 1 September 2014 20:37, Alexander Shikoff <span dir="ltr"><<a href="mailto:minotaur@crete.org.ua" target="_blank">minotaur@crete.org.ua</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi!<br>
<div class=""><br>
On Mon, Sep 01, 2014 at 07:25:36PM +0200, Wouter Prins wrote:<br>
> hi Alexander,<br>
> Have you tried redistributing vrf-a to vpnv4 and export it to vrf-b to see if the bgp<br>
> attributes are available?<br>
</div>I cannot find a way how to do that.<br>
<div class=""><br>
> AFAIK, import/export belongs to the vpnv4 afi and not to vrf-lite functionality.<br>
</div><div class="">vrf Crimea-IX<br>
rd 31210:39751<br>
address-family ipv4<br>
</div> route-target export 31210:39751<br>
route-target import 31210:31210<br>
route-target import 31210:39751<br>
exit-address-family<br>
exit-vrf<br>
<br>
There is no address-family vpnv4 within vrf configuration:<br>
<a href="mailto:telnet@lsr1-gdr.ki">telnet@lsr1-gdr.ki</a>(config)#vrf Crimea-IX<br>
<a href="mailto:telnet@lsr1-gdr.ki">telnet@lsr1-gdr.ki</a>(config-vrf-Crimea-IX)#address-family ?<br>
ipv4 IPv4 address Family<br>
ipv6 IPv6 address Family<br>
<div class=""><br>
<br>
> On 27 August 2014 14:38, Alexander Shikoff <[1]<a href="mailto:minotaur@crete.org.ua">minotaur@crete.org.ua</a>> wrote:<br>
><br>
> Hi Eldon,<br>
><br>
> On Wed, Aug 13, 2014 at 04:53:05PM -0600, Eldon Koyle wrote:<br>
> > I suspect you are actually wanting to look at the vpn route. You<br>
> > probably need to run:<br>
</div>> > show ip bgp vpnv4 route [2]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a><br>
<div class="">> > 'show ip bgp vrf NAME' only shows routes learned via the BGP neighbors<br>
> > within the VRF, not the vpn routes; that is to say the routes learned<br>
> > from neighbors such as:<br>
> ><br>
> > router bgp<br>
> > ...<br>
> > address-family ipv4 unicast vrf NAME<br>
> > neighbor ...<br>
> ><br>
> > These routes are then redistributed across your provider routers via the<br>
> > BGP vpnv4 address family.<br>
><br>
> Thank you for suggestion. But I'm afraid I didn't understand you clearly.<br>
</div>> [3]<a href="http://telnet@lsr1-gdr.ki#show" target="_blank">telnet@lsr1-gdr.ki#show</a> ip bgp vpnv4 route [4]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a><br>
<div><div class="h5">> BGP Routing Table is empty<br>
> I don't need any VPN. I have a single box with two BGP neighbors connected to,<br>
> each neighbor in separate VRF.<br>
> In one VRF I need to import routes from different VRF and announce them to BGP<br>
> neighbor. But I cannot do that because BGP attributes is lost during import.<br>
><br>
> > --<br>
> > Eldon Koyle<br>
> > --<br>
> > If built in great numbers, motels will be used for nothing but illegal<br>
> > purposes.<br>
> > -- J. Edgar Hoover<br>
> ><br>
> > On Aug 13 16:24+0300, Alexander Shikoff wrote:<br>
> > > Hi!<br>
> > ><br>
> > > I have two VRFs on MLXe-16 box and I noticed that exported routes<br>
> > > from one VRF to other lost their BGP attributes.<br>
> > ><br>
> > > vrf Crimea-IX<br>
> > > rd 31210:39751<br>
> > > address-family ipv4<br>
> > > import routes vrf DTEL-IX route-map rm-BGP-and-Direct<br>
> > > exit-address-family<br>
> > > exit-vrf<br>
> > > !<br>
> > > vrf DTEL-IX<br>
> > > rd 31210:31210<br>
> > > address-family ipv4<br>
> > > import routes vrf Crimea-IX route-map rm-Crimea-IX2DTEL-IX<br>
> > > exit-address-family<br>
> > > exit-vrf<br>
> > ><br>
> > ><br>
> > > The routes are exported from Crimea-IX to DTEL-IX, for example:<br>
> > ><br>
</div></div>> > > [5]<a href="http://telnet@lsr1-gdr.ki#show" target="_blank">telnet@lsr1-gdr.ki#show</a> ip route vrf DTEL-IX [6]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a><br>
<div class="">> > > Type Codes - B:BGP D:Connected I:ISIS O:OSPF R:RIP S:Static; Cost - Dist/Metric<br>
> > > BGP Codes - i:iBGP e:eBGP<br>
> > > ISIS Codes - L1:Level-1 L2:Level-2<br>
> > > OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2 s:Sham Link<br>
> > > STATIC Codes - d:DHCPv6<br>
> > > Destination Gateway Port Cost Type Uptime<br>
> src-vrf<br>
</div>> > > 1 [7]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a> 193.34.200.141 ve 205 20/0 Be 25m23s<br>
<div class="">> Crimea-IX<br>
> > ><br>
> > ><br>
> > > In Crimea-IX this route has all its attributes:<br>
</div>> > > [8]<a href="http://telnet@lsr1-gdr.ki#show" target="_blank">telnet@lsr1-gdr.ki#show</a> ip bgp vrf Crimea-IX route [9]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a><br>
<div class="">> > > Number of BGP Routes matching display condition : 1<br>
> > > Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED<br>
> > > E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH<br>
> > > S:SUPPRESSED F:FILTERED s:STALE<br>
> > > Prefix Next Hop MED LocPrf Weight Status<br>
</div>> > > 1 [10]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a> 193.34.200.141 100 0 BE<br>
<div class="">> > > AS_PATH: 42896 15169<br>
> > > Last update to IP routing table: 0h26m44s, 1 path(s) installed:<br>
> > > Route is not advertised to any peers<br>
> > ><br>
> > > In DTEL-IX this route has no attributes already:<br>
> > ><br>
</div>> > > [11]<a href="http://telnet@lsr1-gdr.ki#show" target="_blank">telnet@lsr1-gdr.ki#show</a> ip bgp vrf DTEL-IX route [12]<a href="http://173.194.40.0/24" target="_blank">173.194.40.0/24</a><br>
<div class="">> > > BGP4 : None of the BGP4 routes match the display condition<br>
> > ><br>
> > ><br>
> > > Is there any way to keep BGP attributes when exporting routes ?<br>
> > ><br>
> > > Thanks in advance!<br>
> > ><br>
> > > --<br>
> > > MINO-RIPE<br>
> > > _______________________________________________<br>
> > > foundry-nsp mailing list<br>
</div>> > > [13]<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> > > [14]<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
<div class="">> > ><br>
> --<br>
> MINO-RIPE<br>
> _______________________________________________<br>
> foundry-nsp mailing list<br>
</div>> [15]<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> [16]<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
><br>
> --<br>
> Wouter Prins<br>
> [17]<a href="mailto:wp@null0.nl">wp@null0.nl</a><br>
><br>
> Ссылки<br>
><br>
> 1. mailto:<a href="mailto:minotaur@crete.org.ua">minotaur@crete.org.ua</a><br>
> 2. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 3. <a href="http://telnet@lsr1-gdr.ki/#show" target="_blank">http://telnet@lsr1-gdr.ki/#show</a><br>
> 4. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 5. <a href="http://telnet@lsr1-gdr.ki/#show" target="_blank">http://telnet@lsr1-gdr.ki/#show</a><br>
> 6. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 7. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 8. <a href="http://telnet@lsr1-gdr.ki/#show" target="_blank">http://telnet@lsr1-gdr.ki/#show</a><br>
> 9. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 10. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 11. <a href="http://telnet@lsr1-gdr.ki/#show" target="_blank">http://telnet@lsr1-gdr.ki/#show</a><br>
> 12. <a href="http://173.194.40.0/24" target="_blank">http://173.194.40.0/24</a><br>
> 13. mailto:<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> 14. <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
> 15. mailto:<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
> 16. <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
> 17. mailto:<a href="mailto:wp@null0.nl">wp@null0.nl</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
MINO-RIPE<br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>Wouter Prins<br><a href="mailto:wp@null0.nl" target="_blank">wp@null0.nl</a><br><br>
</div>