From: Joe Chang (changjoe@earthlink.net)
Date: Mon Dec 30 2002 - 15:07:54 GMT-3
Looks like you want to advertise the aggregate address, but do not want to
keep it in the routing table. I don't think that's an option because the
route to Null0 is automatically installed as a routing loop prevention
feature. Say you had also had a default route pointing out to one of the AS
400 neighbors. If your router received a packet from AS 400 for
"192.168.0.1" it would send it back to AS 400, which would send it back to
you, etc etc.
----- Original Message -----
From: "Aamer Kaleem" <kaleemaamer@yahoo.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, December 29, 2002 5:17 AM
Subject: How to get rid of Null0 route that is created by BGP aggregation
> Here is BGP Config:
>
> router bgp 100
> no synchronization
> network 100.100.100.0 mask 255.255.255.0
> network 161.61.160.0 mask 255.255.255.0
> network 161.61.161.0 mask 255.255.255.0
> network 192.168.1.0
> network 192.168.2.0
> network 192.168.3.0
> network 200.100.100.0
> network 200.200.100.0
> network 200.200.200.0
> aggregate-address 192.168.0.0 255.255.252.0
> neighbor 161.61.16.3 remote-as 400
> neighbor 161.61.16.3 send-community
> neighbor 161.61.16.3 route-map set-as out
> neighbor 161.61.16.6 remote-as 400
> neighbor 161.61.16.6 send-community
> neighbor 161.61.16.6 route-map set-as out
> no auto-summary
>
> BGP also adds a 192.168.0.0/22 route to null0
> interface in the routing table....can it be avoided?
>
> Thank you,
>
> Aamer
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
> .
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:54 GMT-3