[quagga-users 14055] Re: Redistributing a kernel default into BGP

Ajinkya Fotedar ajinkyafotedar at gmail.com
Fri Jul 17 16:33:47 BST 2015


Thanks Dunc. That is pretty much what I'm after as well, a geo-redundant
setup.
Although, our f5s are on-a-stick to our PEs as opposed to being inline
(don't believe that
makes a difference in advertising defaults from BGP). And yes, I'm are
using "default-originate",
but just not sure if it will work as expected.

I'll try to explain, bear with me.
Their primary function will be to perform NAT. The default RD0 has a global
NAT pool
being advertised (via BGP) on the egress interface (that connects to a PE).
RD1 (child of RD0) has a default virtual server that I'd like to advertise
(again via BGP and RHI, that I cannot see in "show ip bgp")
to a VRF on the PE. The only way I see this happening right now is the
"default-originate" statement. But that does
not advertise the default virtual server in RD1. That advertises a BGP
generated default.

It is the default virtual server that references the NAT pool. So unless
the virtual server is advertised,
I've no clue as to how clients would be translated for outbound
connectivity.
Hope I'm making sense. Let me know if I'm not seeing this right.

Thanks.
Ajinkya

On Fri, Jul 17, 2015 at 9:50 AM, Dunc <dunc at lemonia.org> wrote:

> Hi Ajinkya,
>
>
> Glad to see some others are using BGP on F5s, we're just about to roll
> some out at $work too.
>
> I don't know if this is any use to you, but could you try just advertising
> default inwards all the time with
>
> neighbor x.x.x.x default-originate
>
> (where x.x.x.x is your southbound router)
>
>
> Also, what I'm doing at $work is to have the F5 inline, with BGP sessions
> both north and south. Then I'm passing in the default route from the
> upstream router, down to the F5, which in turn is sending it south into a
> VRF.
>
> I have successfully used the above (at least in testing), to have a pair
> of F5s that are in different DCs but still config-synced. So I can load
> balance servers at any location so long as they're in a VRF.
>
>
> Cheers,
>
> Dunc
>
>
> On 17/07/15 14:00, Ajinkya Fotedar wrote:
>
>> Hi Steven,
>>
>> Thank you for your inputs. The more I have, the better.
>> Here is the link to the devCentral post
>> https://devcentral.f5.com/questions/bgp-and-route-domains (might not be
>> obvious from the title, sorry about that).
>>
>> I believe you can advertise network virtual servers using RHI and BGP.
>> Sure in the "show ip bgp" and "show ip bgp neighbor x.x.x.x
>> advertised-routes"
>> outputs, you see them as a host route (not the case in "show ip route"
>> though), but I can confirm that I'm receiving a network virtual server
>> route on the
>> peer (advertised from the f5).
>>
>> router[1]#show ip route
>> Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
>>         O - OSPF, IA - OSPF inter area
>>         N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
>>         E1 - OSPF external type 1, E2 - OSPF external type 2
>>         i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
>> inter area
>>         * - candidate default
>>
>> Gateway of last resort is 0.0.0.0 to network 0.0.0.0
>>
>> K* 0.0.0.0/0 <http://0.0.0.0/0> is directly connected, tmm0
>> C 127.0.0.1/32 <http://127.0.0.1/32> is directly connected, lo
>> C 127.1.1.0/24 <http://127.1.1.0/24> is directly connected, tmm0
>> K 172.24.0.0/16 <http://172.24.0.0/16> is directly connected, tmm0
>> C 172.14.0.4/30 <http://172.14.0.4/30> is directly connected, VLAN_701
>>
>>
>> router[1]#show ip bgp
>> BGP table version is 6, local router ID is 1.1.1.1
>> Status codes: s suppressed, d damped, h history, * valid, > best, i -
>> internal, l - labeled
>>                S Stale
>> Origin codes: i - IGP, e - EGP, ? - incomplete
>>
>>     Network          Next Hop            Metric     LocPrf     Weight Path
>> *> 172.24.0.0       0.0.0.0                                    32768 ?
>>
>> Total number of prefixes 1
>>
>>
>> The 172.24.0.0/16 <http://172.24.0.0/16> virtual server route can be
>> seen in BGP received-routes on the peer.
>> Shouldn't a 0.0.0.0/0 <http://0.0.0.0/0> be sent to the peer the same
>> way (by redistribution)?
>>
>> The ultimate goal here is to perform NAT. The default virtual server
>> references a NAT pool.
>> And if that virtual server cannot be advertised to the rest of the
>> network, wondering how the
>> clients will connect to it and get translated (get an outside IP from
>> the pool this virtual server references)
>> for outbound connectivity.
>>
>> Thanks.
>> Ajinkya
>>
>> On Fri, Jul 17, 2015 at 4:53 AM, Steven Iveson <sjiveson at live.com
>> <mailto:sjiveson at live.com>> wrote:
>>
>>     Hi Ajinkya,
>>
>>     My apologies all if I've broken any etiquette in this response, I'm
>>     normally just a lurker.
>>
>>     I couldn't find your post on DevCentral.
>>
>>     Based on this statement:
>>
>>     "For purposes of redistribution, the dynamic routing protocols
>>     consider any route generated through Route Health Injection (RHI) to
>>     be a host route."
>>
>>      From this document:
>>
>>
>> https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-ip-routing-administration-11-3-0/4.html
>>
>>     It seems you may not be able to advertise a default route, or any
>>     network route, using the method you have.
>>
>>     I wonder if perhaps a default route configured in LTM would be
>> helpful?
>>
>>     Kind regards,
>>
>>     Steven Iveson
>>
>>
>>      > From: quagga-users-request at lists.quagga.net
>>     <mailto:quagga-users-request at lists.quagga.net>
>>      > Subject: Quagga-users Digest, Vol 144, Issue 9
>>      > To: quagga-users at lists.quagga.net
>>     <mailto:quagga-users at lists.quagga.net>
>>      > Date: Thu, 16 Jul 2015 22:02:58 +0100
>>      >
>>      > Send Quagga-users mailing list submissions to
>>      > quagga-users at lists.quagga.net <mailto:
>> quagga-users at lists.quagga.net>
>>      >
>>      > To subscribe or unsubscribe via the World Wide Web, visit
>>      > https://lists.quagga.net/mailman/listinfo/quagga-users
>>      >
>>      > You can reach the person managing the list at
>>      > quagga-users-owner at lists.quagga.net
>>     <mailto:quagga-users-owner at lists.quagga.net>
>>      >
>>      > When replying, please edit your Subject line so it is more specific
>>      > than "Re: Contents of Quagga-users digest..."
>>      >
>>      >
>>      > Today's Topics:
>>      >
>>      > 1. [quagga-users 14048] Redistributing a kernel default into BGP
>>      > (Ajinkya Fotedar)
>>      > 2. [quagga-users 14049] Re: Redistributing a kernel default into
>>      > BGP (Michael Moffatt)
>>      > 3. [quagga-users 14050] Re: Redistributing a kernel default into
>>      > BGP (Ajinkya Fotedar)
>>      >
>>      >
>>      >
>>     ----------------------------------------------------------------------
>>      >
>>      > Message: 1
>>      > Date: Thu, 16 Jul 2015 14:27:15 -0400
>>      > From: Ajinkya Fotedar <ajinkyafotedar at gmail.com
>>     <mailto:ajinkyafotedar at gmail.com>>
>>      > To: quagga-users at lists.quagga.net
>>     <mailto:quagga-users at lists.quagga.net>
>>      > Subject: [quagga-users 14048] Redistributing a kernel default
>>     into BGP
>>      > Message-ID:
>>      >
>>     <CAHb032JF4yQA3Mw-0F0cpd88mAcLe3pE_1fo-JsWyV9jQWLd6Q at mail.gmail.com
>>     <mailto:
>> CAHb032JF4yQA3Mw-0F0cpd88mAcLe3pE_1fo-JsWyV9jQWLd6Q at mail.gmail.com>>
>>
>>      > Content-Type: text/plain; charset="utf-8"
>>
>>      >
>>      > Hello list,
>>      >
>>      > We have a couple of devices (f5) in our network and they are
>>     shipped with
>>      > zebos for anything routing.
>>      > I realize that the f5 community might be the right place to ask
>> this
>>      > question, and I have, but I also wanted
>>      > to consult this list since apart from vendor docs, I've also
>> referred
>>      > http://www.nongnu.org/quagga/docs/docs-info.html
>>      > if I run into any issues.
>>      >
>>      > The vendor has this concept of virtual servers that are
>>     essentially kernel
>>      > routes.
>>      > All I'm trying to do is to redistribute a kernel route into BGP,
>> and
>>      > although that's a straight forward task ("redistribute kernel"
>>      > in the BGP config), I cannot see the route in "show ip bgp". The
>>     kernel
>>      > route in question here is a default route that I'd like
>>      > to export to the upstream router.
>>      >
>>      > BGP Config:
>>      > router[1]#show run router bgp
>>      > !
>>      > router bgp 64998
>>      > bgp router-id 1.1.1.1
>>      > bgp log-neighbor-changes
>>      > bgp graceful-restart restart-time 120
>>      > redistribute kernel
>>      > neighbor 172.14.0.4 remote-as 1111
>>      > neighbor 172.14.0.4 capability graceful-restart
>>      > !
>>      >
>>      > router[1]#show ip route
>>      > Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
>>      > O - OSPF, IA - OSPF inter area
>>      > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
>>      > E1 - OSPF external type 1, E2 - OSPF external type 2
>>      > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter
>>      > area
>>      > * - candidate default
>>      >
>>      > Gateway of last resort is 0.0.0.0 to network 0.0.0.0
>>      >
>>      > K* 0.0.0.0/0 <http://0.0.0.0/0> is directly connected, tmm0 ==>
>>     kernel route shows up here
>>      > C 127.0.0.1/32 <http://127.0.0.1/32> is directly connected, lo
>>      > C 127.1.1.0/24 <http://127.1.1.0/24> is directly connected, tmm0
>>      > C 172.14.0.4/30 <http://172.14.0.4/30> is directly connected,
>>     VLAN_701
>>      >
>>      > router[1]#show ip bgp ==> cannot see the kernel route being
>>     advertised
>>      >
>>      > router[1]#
>>      >
>>      > router[1]#show ip bgp neighbors 172.14.0.4 advertised-routes ==>
>>     nor here
>>      > router[1]#
>>      >
>>      > Just want to clarify that the neighbor relationships are in a
>>     "Established"
>>      > state,
>>      > and if I export a route from the peer, I can see it in the
>>     received-routes
>>      > show cmd.
>>      >
>>      > Would really appreciate if anyone here could point me in the right
>>      > direction.
>>      >
>>      > TIA!
>>      > -------------- next part --------------
>>      > An HTML attachment was scrubbed...
>>      > URL:
>>     <
>> http://lists.quagga.net/pipermail/quagga-users/attachments/20150716/de0336b2/attachment-0001.html
>> >
>>      >
>>      > ------------------------------
>>      >
>>      > Message: 2
>>      > Date: Thu, 16 Jul 2015 22:36:53 +0200
>>      > From: "Michael Moffatt" <michael at moffatt.org.nz
>>     <mailto:michael at moffatt.org.nz>>
>>      > To: "Ajinkya Fotedar" <ajinkyafotedar at gmail.com
>>     <mailto:ajinkyafotedar at gmail.com>>
>>      > Cc: quagga-users at lists.quagga.net
>>     <mailto:quagga-users at lists.quagga.net>
>>      > Subject: [quagga-users 14049] Re: Redistributing a kernel default
>>     into
>>      > BGP
>>      > Message-ID:
>>      > <a79f201d0efe0e88b6357293f2dfc16e.squirrel at mail.moffatt.org.nz
>>     <mailto:a79f201d0efe0e88b6357293f2dfc16e.squirrel at mail.moffatt.org.nz
>> >>
>>      > Content-Type: text/plain;charset=iso-8859-1
>>
>>      >
>>      > Hi Ajinkya,
>>      >
>>      > If your network is actually part of another route-domain, say
>>     RD1, then
>>      > make sure to issue the command in that route-domain, so for
>>     example from
>>      > the BIG-IP bash prompt:
>>      >
>>      > ---
>>      > [root at HOSTNAME:Active:Standalone] # imish -r 1
>>      > HOSTNAME[1]>ena
>>      > HOSTNAME[1]#sh ip route k
>>      > K 172.30.1.1/32 <http://172.30.1.1/32> is directly connected, tmm0
>>      >
>>      > Gateway of last resort is not set
>>      > HOSTNAME[1]#show ip bgp
>>      > BGP table version is 1, local router ID is 1.1.1.1
>>      > Status codes: s suppressed, d damped, h history, * valid, > best,
>> i -
>>      > internal, l - labeled
>>      > S Stale
>>      > Origin codes: i - IGP, e - EGP, ? - incomplete
>>      >
>>      > Network Next Hop Metric LocPrf Weight Path
>>      > *> 172.30.1.1/32 <http://172.30.1.1/32> 0.0.0.0 32768 ?
>>
>>      >
>>      > Total number of prefixes 1
>>      > ---
>>      >
>>      > Notice that I also used the command "show ip bgp" to see that the
>>     route
>>      > was in BGP.
>>      >
>>      > If you do not specify the route-domain then imish will assume RD0.
>> If
>>      > there is no BGP enabled in tmsh and/or configured in imish for
>>     that route
>>      > domain, then the result will be no output.
>>      >
>>      > [root at HOSTNAME:Active:Standalone] # tmsh list net route-domain
>>      > /Common/MY_RD_NAME routing-protocol
>>      > net route-domain MY_RD_NAME {
>>      > routing-protocol {
>>      > OSPFv2
>>      > BGP
>>      > }
>>      > }
>>      >
>>      > You can execute the commands without entering interactive mode by
>>     using
>>      > the -e. E.G: to execute commands in RD1, use:
>>      >
>>      > # imish -r 1 -e 'show ip route'
>>      >
>>      > Hope this helps,
>>      > Michael Moffatt.
>>      >
>>      > > Hello list,
>>      > >
>>      > > We have a couple of devices (f5) in our network and they are
>>     shipped with
>>      > > zebos for anything routing.
>>      > > I realize that the f5 community might be the right place to ask
>>     this
>>      > > question, and I have, but I also wanted
>>      > > to consult this list since apart from vendor docs, I've also
>>     referred
>>      > > http://www.nongnu.org/quagga/docs/docs-info.html
>>      > > if I run into any issues.
>>      > >
>>      > > The vendor has this concept of virtual servers that are
>>     essentially kernel
>>      > > routes.
>>      > > All I'm trying to do is to redistribute a kernel route into
>>     BGP, and
>>      > > although that's a straight forward task ("redistribute kernel"
>>      > > in the BGP config), I cannot see the route in "show ip bgp".
>>     The kernel
>>      > > route in question here is a default route that I'd like
>>      > > to export to the upstream router.
>>      > >
>>      > > BGP Config:
>>      > > router[1]#show run router bgp
>>      > > !
>>      > > router bgp 64998
>>      > > bgp router-id 1.1.1.1
>>      > > bgp log-neighbor-changes
>>      > > bgp graceful-restart restart-time 120
>>      > > redistribute kernel
>>      > > neighbor 172.14.0.4 remote-as 1111
>>      > > neighbor 172.14.0.4 capability graceful-restart
>>      > > !
>>      > >
>>      > > router[1]#show ip route
>>      > > Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
>>      > > O - OSPF, IA - OSPF inter area
>>      > > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
>>      > > E1 - OSPF external type 1, E2 - OSPF external type 2
>>      > > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
>> inter
>>      > > area
>>      > > * - candidate default
>>      > >
>>      > > Gateway of last resort is 0.0.0.0 to network 0.0.0.0
>>      > >
>>      > > K* 0.0.0.0/0 <http://0.0.0.0/0> is directly connected, tmm0 ==>
>>     kernel route shows up
>>      > > here
>>      > > C 127.0.0.1/32 <http://127.0.0.1/32> is directly connected, lo
>>      > > C 127.1.1.0/24 <http://127.1.1.0/24> is directly connected, tmm0
>>      > > C 172.14.0.4/30 <http://172.14.0.4/30> is directly connected,
>>     VLAN_701
>>      > >
>>      > > router[1]#show ip bgp ==> cannot see the kernel route being
>>     advertised
>>      > >
>>      > > router[1]#
>>      > >
>>      > > router[1]#show ip bgp neighbors 172.14.0.4 advertised-routes
>>     ==> nor here
>>      > > router[1]#
>>      > >
>>      > > Just want to clarify that the neighbor relationships are in a
>>      > > "Established"
>>      > > state,
>>      > > and if I export a route from the peer, I can see it in the
>>     received-routes
>>      > > show cmd.
>>      > >
>>      > > Would really appreciate if anyone here could point me in the
>> right
>>      > > direction.
>>      > >
>>      > > TIA!
>>      > > _______________________________________________
>>      > > Quagga-users mailing list
>>      > > Quagga-users at lists.quagga.net
>>     <mailto:Quagga-users at lists.quagga.net>
>>      > > https://lists.quagga.net/mailman/listinfo/quagga-users
>>      > >
>>      >
>>      >
>>      >
>>      >
>>      >
>>      > ------------------------------
>>      >
>>      > Message: 3
>>      > Date: Thu, 16 Jul 2015 17:02:40 -0400
>>      > From: Ajinkya Fotedar <ajinkyafotedar at gmail.com
>>     <mailto:ajinkyafotedar at gmail.com>>
>>      > To: michael at moffatt.org.nz <mailto:michael at moffatt.org.nz>
>>      > Cc: quagga-users at lists.quagga.net
>>     <mailto:quagga-users at lists.quagga.net>
>>      > Subject: [quagga-users 14050] Re: Redistributing a kernel default
>>     into
>>      > BGP
>>      > Message-ID:
>>      >
>>     <CAHb032Li-OtLChtXsqQBgQC9sW710ThH=DuGtxy7KYGQT6fWog at mail.gmail.com
>>     <mailto:DuGtxy7KYGQT6fWog at mail.gmail.com>>
>>      > Content-Type: text/plain; charset="utf-8"
>>
>>      >
>>      > Hi Michael,
>>      >
>>      > Thank you for the prompt reply.
>>      > You guessed it right, I also have RD1, apart from the default RD0.
>>      > I do have BGP enabled in both RDs and all the above outputs are
>>     from RD1
>>      > (imish -r 1, router[1]#).
>>      >
>>      > net route-domain 0 {
>>      > id 0
>>      > routing-protocol {
>>      > OSPFv2
>>      > BGP
>>      > }
>>      > }
>>      >
>>      > net route-domain rd1 {
>>      > id 1
>>      > parent 0
>>      > routing-protocol {
>>      > OSPFv2
>>      > BGP
>>      > }
>>      > }
>>      >
>>      >
>>      > If I advertise a non-default virtual server (172.24.0.0/16
>>     <http://172.24.0.0/16>) from RD1 (the
>>      > way you did above),
>>      > that kernel route can be seen in BGP. But that is not the case for
>> a
>>      > default virtual server (0.0.0.0/0 <http://0.0.0.0/0>).
>>      > If you can test at your end by advertising a default virtual
>>     server, that
>>      > would be really helpful.
>>      >
>>      > router[1]#show ip route
>>      > Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
>>      > O - OSPF, IA - OSPF inter area
>>      > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
>>      > E1 - OSPF external type 1, E2 - OSPF external type 2
>>      > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter
>>      > area
>>      > * - candidate default
>>      >
>>      > Gateway of last resort is 0.0.0.0 to network 0.0.0.0
>>      >
>>      > K* 0.0.0.0/0 <http://0.0.0.0/0> is directly connected, tmm0
>>      > C 127.0.0.1/32 <http://127.0.0.1/32> is directly connected, lo
>>      > C 127.1.1.0/24 <http://127.1.1.0/24> is directly connected, tmm0
>>      > K 172.24.0.0/16 <http://172.24.0.0/16> is directly connected, tmm0
>>      > C 172.14.0.4/30 <http://172.14.0.4/30> is directly connected,
>>     VLAN_701
>>      >
>>      >
>>      > router[1]#show ip bgp
>>      > BGP table version is 6, local router ID is 1.1.1.1
>>      > Status codes: s suppressed, d damped, h history, * valid, > best,
>> i -
>>      > internal, l - labeled
>>      > S Stale
>>      > Origin codes: i - IGP, e - EGP, ? - incomplete
>>      >
>>      > Network Next Hop Metric LocPrf Weight Path
>>      > *> 172.24.0.0 0.0.0.0 32768 ?
>>      >
>>      > Total number of prefixes 1
>>      >
>>      >
>>      > Thank you.
>>      > Ajinkya
>>      >
>>      > On Thu, Jul 16, 2015 at 4:36 PM, Michael Moffatt
>>     <michael at moffatt.org.nz <mailto:michael at moffatt.org.nz>>
>>      > wrote:
>>      >
>>      > > Hi Ajinkya,
>>      > >
>>      > > If your network is actually part of another route-domain, say
>>     RD1, then
>>      > > make sure to issue the command in that route-domain, so for
>>     example from
>>      > > the BIG-IP bash prompt:
>>      > >
>>      > > ---
>>      > > [root at HOSTNAME:Active:Standalone] # imish -r 1
>>      > > HOSTNAME[1]>ena
>>      > > HOSTNAME[1]#sh ip route k
>>      > > K 172.30.1.1/32 <http://172.30.1.1/32> is directly connected,
>> tmm0
>>      > >
>>      > > Gateway of last resort is not set
>>      > > HOSTNAME[1]#show ip bgp
>>      > > BGP table version is 1, local router ID is 1.1.1.1
>>      > > Status codes: s suppressed, d damped, h history, * valid, >
>>     best, i -
>>      > > internal, l - labeled
>>      > > S Stale
>>      > > Origin codes: i - IGP, e - EGP, ? - incomplete
>>      > >
>>      > > Network Next Hop Metric LocPrf Weight Path
>>      > > *> 172.30.1.1/32 <http://172.30.1.1/32> 0.0.0.0 32768 ?
>>
>>      > >
>>      > > Total number of prefixes 1
>>      > > ---
>>      > >
>>      > > Notice that I also used the command "show ip bgp" to see that
>>     the route
>>      > > was in BGP.
>>      > >
>>      > > If you do not specify the route-domain then imish will assume
>>     RD0. If
>>      > > there is no BGP enabled in tmsh and/or configured in imish for
>>     that route
>>      > > domain, then the result will be no output.
>>      > >
>>      > > [root at HOSTNAME:Active:Standalone] # tmsh list net route-domain
>>      > > /Common/MY_RD_NAME routing-protocol
>>      > > net route-domain MY_RD_NAME {
>>      > > routing-protocol {
>>      > > OSPFv2
>>      > > BGP
>>      > > }
>>      > > }
>>      > >
>>      > > You can execute the commands without entering interactive mode
>>     by using
>>      > > the -e. E.G: to execute commands in RD1, use:
>>      > >
>>      > > # imish -r 1 -e 'show ip route'
>>      > >
>>      > > Hope this helps,
>>      > > Michael Moffatt.
>>      > >
>>      > > > Hello list,
>>      > > >
>>      > > > We have a couple of devices (f5) in our network and they are
>>     shipped with
>>      > > > zebos for anything routing.
>>      > > > I realize that the f5 community might be the right place to
>>     ask this
>>      > > > question, and I have, but I also wanted
>>      > > > to consult this list since apart from vendor docs, I've also
>>     referred
>>      > > > http://www.nongnu.org/quagga/docs/docs-info.html
>>      > > > if I run into any issues.
>>      > > >
>>      > > > The vendor has this concept of virtual servers that are
>>     essentially
>>      > > kernel
>>      > > > routes.
>>      > > > All I'm trying to do is to redistribute a kernel route into
>>     BGP, and
>>      > > > although that's a straight forward task ("redistribute kernel"
>>      > > > in the BGP config), I cannot see the route in "show ip bgp".
>>     The kernel
>>      > > > route in question here is a default route that I'd like
>>      > > > to export to the upstream router.
>>      > > >
>>      > > > BGP Config:
>>      > > > router[1]#show run router bgp
>>      > > > !
>>      > > > router bgp 64998
>>      > > > bgp router-id 1.1.1.1
>>      > > > bgp log-neighbor-changes
>>      > > > bgp graceful-restart restart-time 120
>>      > > > redistribute kernel
>>      > > > neighbor 172.14.0.4 remote-as 1111
>>      > > > neighbor 172.14.0.4 capability graceful-restart
>>      > > > !
>>      > > >
>>      > > > router[1]#show ip route
>>      > > > Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
>>      > > > O - OSPF, IA - OSPF inter area
>>      > > > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
>>      > > > E1 - OSPF external type 1, E2 - OSPF external type 2
>>      > > > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
>>      > > inter
>>      > > > area
>>      > > > * - candidate default
>>      > > >
>>      > > > Gateway of last resort is 0.0.0.0 to network 0.0.0.0
>>      > > >
>>      > > > K* 0.0.0.0/0 <http://0.0.0.0/0> is directly connected, tmm0
>>     ==> kernel route shows up
>>      > > > here
>>      > > > C 127.0.0.1/32 <http://127.0.0.1/32> is directly connected, lo
>>      > > > C 127.1.1.0/24 <http://127.1.1.0/24> is directly connected,
>> tmm0
>>      > > > C 172.14.0.4/30 <http://172.14.0.4/30> is directly connected,
>>     VLAN_701
>>      > > >
>>      > > > router[1]#show ip bgp ==> cannot see the kernel route being
>>     advertised
>>      > > >
>>      > > > router[1]#
>>      > > >
>>      > > > router[1]#show ip bgp neighbors 172.14.0.4 advertised-routes
>>     ==> nor here
>>      > > > router[1]#
>>      > > >
>>      > > > Just want to clarify that the neighbor relationships are in a
>>      > > > "Established"
>>      > > > state,
>>      > > > and if I export a route from the peer, I can see it in the
>>      > > received-routes
>>      > > > show cmd.
>>      > > >
>>      > > > Would really appreciate if anyone here could point me in the
>>     right
>>      > > > direction.
>>      > > >
>>      > > > TIA!
>>      > > > _______________________________________________
>>      > > > Quagga-users mailing list
>>      > > > Quagga-users at lists.quagga.net
>>     <mailto:Quagga-users at lists.quagga.net>
>>      > > > https://lists.quagga.net/mailman/listinfo/quagga-users
>>      > > >
>>      > >
>>      > >
>>      > >
>>      > -------------- next part --------------
>>      > An HTML attachment was scrubbed...
>>      > URL:
>>     <
>> http://lists.quagga.net/pipermail/quagga-users/attachments/20150716/f665c314/attachment.html
>> >
>>      >
>>      > ------------------------------
>>     >
>>     > _______________________________________________
>>     > Quagga-users mailing list
>>     >Quagga-users at lists.quagga.net <mailto:Quagga-users at lists.quagga.net>
>>     >https://lists.quagga.net/mailman/listinfo/quagga-users
>>     >
>>     >
>>      > End of Quagga-users Digest, Vol 144, Issue 9
>>      > ********************************************
>>
>>
>>
>>
>> _______________________________________________
>> Quagga-users mailing list
>> Quagga-users at lists.quagga.net
>> https://lists.quagga.net/mailman/listinfo/quagga-users
>>
>>
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users at lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-users/attachments/20150717/44af95d3/attachment-0001.html>


More information about the Quagga-users mailing list