AW: [j-nsp] BGP export

[Struck, Olaf]

I think the "no-readvertise" option for the more specific static routes
would solve your problem.

static {
    route 10.0.0.0/8 {
        next-hop 1.1.1.1;
        no-readvertise;
    }
}

/Olaf

-----Ursprungliche Nachricht-----
Von: Jonas Frey (Probe Networks) [mailto:jf at probe-networks.de]
Gesendet: Donnerstag, 15. April 2004 08:55
An: juniper-nsp at puck.nether.net
Betreff: [j-nsp] BGP export


Hello,

we are currently using static routes on our Juniper and therefore a
static export policy. However, now we need to connect a customer
directly to our Juniper and i have to deaggregate our /18 and slice his
net out of it. Since we are exporting the static table, BGP would now
announce alot of small deaggregated blocks, which is not what we'd like
to have.
Whats the best way to still rip out a say /24 out of the /18 and still
announce the /18 to all peers? This shouldnt be much of a problem,
however i cant figure out howto do it.

Regards,
Jonas


_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp