From: Aidan Marks (amarks@cisco.com)
Date: Tue Feb 04 2003 - 00:34:40 GMT-3
I don't see the behaviour you are describing (i.e. it's still advertising
it out since I sent the last email). Also blasting bgp away and putting it
back produces the result I originally described.
Though I do notice that when removing the distribute list the null route
did not re-appear in the RIB but clear ip bgp * brought it back.
This command in bgp I think has been buggy in the past so your mileage may
vary. I also can't provide any guarantees the distribute functionality in
bgp will remain, as I thought I saw some reference to wanting it
deprecated, but don't quote me on that.
Aidan
At 02:09 PM 4/02/2003, Donny MATEO wrote:
>Hi Aidan,
>
>did you observe the behaviour long enough in example for BGP to refresh
>the routing updates. BGP is
>very slow on detecting network outage. what I'm affraid is that at the
>point of your observation BGP
>might still be sending the update simply because it has not check the RIB.
>once it checked the RIB
>it will update is's update and the summary will be gone.
>
>Donny
>
>
>
>
> Aidan
> Marks
>
> <amarks@cisco.com To: "love cisco"
> <love_cisco@hotmail.com>
> > cc:
> ccielab@groupstudy.com
> Sent by: Subject: Re: How to
> remove Null0 in the routing table?
> nobody@groupstudy
>
> .com
>
>
>
>
>
> 04-02-2003
> 07:50
>
> Please respond
> to
>
> Aidan
> Marks
>
>
>
>
>
>
>
>
>
>Your mileage may vary on different code versions but I quickly got this to
>work by creating a distribute-list in on the bgp process referencing a
>prefix list for the null0 route. The null route was in bgp and not in the
>RIB after clear ip route *.
>
>Be wary of your actions and the potential routing loop disaster you can get
>into with removing null0 routes. They are there for a very good reason.
>
>Aidan
>
>At 10:02 AM 4/02/2003, love cisco wrote:
>
> >How to remove Null0 in the routing table? Because BGP aggregate-address
> >create Null0 route. If the lab ask you remove it.
> >
> >router bgp 100
> >network 192.168.10.0 mask 255.255.255.240
> >network 192.168.10.16 mask 255.255.255.240
> >network 192.168.20.32 mask 255.255.255.240
> >network 192.168.20.48 mask 255.255.255.240
> >aggregate-address 192.168.10.0 255.255.255.0 summary-only
> >aggregate-address 192.168.20.0 255.255.255.0 summary-only
> >neighbor 150.50.17.2 remote-as 200
> >neighbor 150.50.17.2 update-source Loopback0
> >no auto-summary
> >
> >
> >R1#sh ip route
> >Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
> > D - EIGRP, EX - EIGRP external, 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, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter
> > area
> > * - candidate default, U - per-user static route, o - ODR
> > P - periodic downloaded static route
> >
> >Gateway of last resort is not set
> >
> > 200.0.0.0/32 is subnetted, 2 subnets
> >C 200.0.0.1 is directly connected, Loopback0
> >B 200.0.0.4 [20/0] via 150.50.17.2, 13:46:01
> > 192.168.10.0/24 is variably subnetted, 3 subnets, 2 masks
> >B 192.168.10.0/24 [200/0] via 0.0.0.0, 14:33:26, Null0
> >C 192.168.10.0/28 is directly connected, Loopback1
> >C 192.168.10.16/28 is directly connected, Loopback2
> > 192.168.20.0/24 is variably subnetted, 3 subnets, 2 masks
> >C 192.168.20.48/28 is directly connected, Loopback4
> >C 192.168.20.32/28 is directly connected, Loopback3
> >B 192.168.20.0/24 [200/0] via 0.0.0.0, 14:18:13, Null0
> > 10.0.0.0/25 is subnetted, 1 subnets
> >B 10.1.1.0 [20/0] via 150.50.17.2, 13:46:01
> > 150.50.0.0/24 is subnetted, 1 subnets
> >C 150.50.17.0 is directly connected, FastEthernet0/0
> >
> >
> >
> >_________________________________________________________________
> >Cb7QOBTX MSN Explorer: http://explorer.msn.com/lccn/
> >.
>.
>This message is for information purposes only and its content
>should not be construed as an offer, or solicitation of an offer,
>to buy or sell any banking or financial instruments or services
>and no representation or warranty is given in respect of its
>accuracy, completeness or fairness. The material is subject
>to change without notice. You should take your own independent
>tax, legal and other professional advice in respect of the content
>of this message. This message may contain confidential or
>legally privileged material and may not be copied, redistributed
>or published (in whole or in part) without our prior written consent.
>This email may have been intercepted, partially destroyed,
>arrive late, incomplete or contain viruses and no liability is
>accepted by any member of the Credit Agricole Indosuez group
>as a result. If you are not the intended recipient of this message,
>please immediately notify the sender and delete this message
>from your computer.
.
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:07 GMT-3