Mailing List Archive: import BGP routes in RIB

On Thu, Sep 05, 2002 at 03:02:52PM -0700, Andrew Ramsey wrote:
> group internal {
> type internal;
> local-address 10.10.10.102;
> family inet {
> unicast {
> rib-group new_rib;
> }
> }
> neighbor 10.10.10.40;
> }

Ah, thats the part I was missing. But here is a question, can you apply
an import policy per rib instead of per rib-group?

For example, lets say you are a provider buying and selling transit in two
very different classes of service, say Cogent and "Someone Expensive".
Lets say you wanted to setup two routing-instances, one where the cheap
transit is primary and the expensive one backs it up in the event of a
failure, and one where the roles are reversed.

Since you can only set one rib-group for export under the bgp peer, all
the ribs would have to be under one rib-group. But how do you apply an
import policy for each rib? There isn't an import-policy on the rib level,
and it doesn't seem to have any effect on the routing-instance level.

--
Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras
PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6)

Hi Richard,

Yes, I've had a couple of people ask me about this in the last few
weeks. Right now, when importing routes into the rib-group, you can
only control accept or reject, and not manipulate route metrics. What
you need is the ability to manipulate metrics when importing into the
rib-group. This will be supported in a later release of JUNOS. Please
contact your SE for the details.

What's your criteria for selecting which packet goes to which ISP?

In the meantime could you use FBF and a static default in each instance
for backing the other up? For example,:

1. Create 2 routing instances; expensive-net and cheap-net. =20
2. Populate routes into each of these instances via BGP. =20
3. Create an interface routes' rib-group
4. Create a static default route in each of the instances pointing to
the other instance BGP neighbor (for backup)
5. Create a firewall pointing to the appropriate instance based on ?
(things you can match in a FW filter)
6. You can also make a rib-group w/ inet.0 so that you end up with:

a. A user group that always uses expensive-net backed up by cheap-net
b. A user group that always uses cheap-net backed up by expensive net
c. A user group that always follows the BGP selected best path

For 2 ISPs this might work, but as you add more it becomes less elegant.

Let me know offline if I can be of some help.

Andy

>-----Original Message-----
>From: Richard A Steenbergen [mailto:ras@e-gerbil.net]
>Sent: Monday, October 14, 2002 3:13 PM
>To: Andrew Ramsey
>Cc: Christian Malo; juniper-nsp@puck.nether.net
>Subject: Re: [j-nsp] import BGP routes in RIB
>
>
>On Thu, Sep 05, 2002 at 03:02:52PM -0700, Andrew Ramsey wrote:
>> group internal {
>> type internal;
>> local-address 10.10.10.102;
>> family inet {
>> unicast {
>> rib-group new_rib;
>> }
>> }
>> neighbor 10.10.10.40;
>> }
>
>Ah, thats the part I was missing. But here is a question, can you apply
>an import policy per rib instead of per rib-group?
>
>For example, lets say you are a provider buying and selling=20
>transit in two=20
>very different classes of service, say Cogent and "Someone Expensive".=20
>Lets say you wanted to setup two routing-instances, one where=20
>the cheap=20
>transit is primary and the expensive one backs it up in the event of a=20
>failure, and one where the roles are reversed.
>
>Since you can only set one rib-group for export under the bgp=20
>peer, all=20
>the ribs would have to be under one rib-group. But how do you apply an=20
>import policy for each rib? There isn't an import-policy on=20
>the rib level,=20
>and it doesn't seem to have any effect on the routing-instance level.
>
>--=20
>Richard A Steenbergen <ras@e-gerbil.net> =20
http://www.e-gerbil.net/ras
PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE
B6)