[j-nsp] BGP origination

[Fernando Krahe]

Richard,

you can still play with those nice parameters even importing from direct,
static or agregate. One way of injecting the next-hop information from
prefixes you learn from an eBGP peer is importing it from the direct
protocol (juniper parlance) into BGP. Thus you don't have to run an IGP in
passive on that interface or set next-hop-self.
I added some examples:

routing-options {
    static {
        route 172.16.0.0/19 {
            next-hop 1.1.1.1;
            preference 254;
            community 65001:55111;
        }
    }
    aggregate {
        route 128.0.0.0/16 community 65001:111;
    }
    autonomous-system 65001;
}
policy-options {
    policy-statement originate-network {
        term originate-network {
            from protocol aggregate;
            then accept;
        }
    }
    policy-statement distribute-links {
        term external-links {
            from {
                protocol direct;
                route-filter 1.1.1.1/30 exact;
                route-filter 2.2.2.2/30 exact;
            }
            then {
                origin igp;
                community set idc-identifier;
                accept;
            }
        }
    }
    policy-statement other-idc-blocks {
        term other-idc {
            from {
                protocol static;
                route-filter 172.16.0.0/19 exact;
            }
            then {
                local-preference 60;
                origin igp;
                community set idc-identifier;
                accept;
            }
        }
    }
}
protocols {
    bgp {
        group internal {
            type internal;
            export [ originate-network distribute-links other-idc-blocks ];
        }
        group rr-clients {
            type internal;
            export [ originate-network distribute-links other-idc-blocks ];
         }
        group ISP-1 {
            type external;
            export [ originate-network allow-transit ];
        }
    }
}


Fernando Krahe
PGP Key: 0x6582579A (F163 9323 129C 2602 792F  A881 123C 9E3F 6582 579A)


----- Original Message -----
From: "Richard A Steenbergen" <ras at e-gerbil.net>
To: "Hannes Gredler" <hannes at juniper.net>
Cc: "dre" <andre at operations.net>; <juniper-nsp at puck.nether.net>
Sent: Wednesday, January 29, 2003 1:22 PM
Subject: Re: [j-nsp] BGP origination


> On Wed, Jan 29, 2003 at 02:50:37PM +0100, Hannes Gredler wrote:
> >
> > why relying on a static route if we have a direct route ?
> >
> > policy-options {
> >     policy-statement adv-customer-xyz {
> >        from {
> >            protocol direct;
> >            route-filter 192.168.1.0/24;
> >        }
> >        then accept;
> >    }
> > }
> > protocols {
> >     bgp {
> >         group to-my-upstream {
> >             export adv-customer-xyz;
> >         }
> >     }
> > }
> >
> > should do the trick ...
>
> Because then I lose the ability to easily tag that /24 with communities,
> as-path, etc, as I would when defining a static holddown route. At best, I
> end up with a REALLY ugly policy-statement to do it.
>
> --
> Richard A Steenbergen <ras at e-gerbil.net>       http://www.e-gerbil.net/ras
> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp