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