From: Khurram Khani (kkhani@xxxxxxxxxxxxxxxxxx)
Date: Tue Jun 04 2002 - 20:58:43 GMT-3
Great reply!! Seems to Zebra problem.
Thanks
Khurram.
----- Original Message -----
From: "Carlos G Mendioroz" <tron@huapi.ba.ar>
To: "Khani, Khurram [INGO1:8851:EXCH]" <kkhani@americasm06.nt.com>
Cc: <ccielab@groupstudy.com>
Sent: Tuesday, June 04, 2002 4:15 PM
Subject: Re: BGP: UPDATE Packet Problem
> Seems to be a Zebra problem...
> From RFC1771:
>
> 9. UPDATE Message Handling
>
> ...
>
> i) If its Network Layer Reachability Information (NLRI) is identical
> to the one of a route currently stored in the Adj-RIB-In, then the
> new route shall replace the older route in the Adj-RIB-In, thus
> implicitly withdrawing the older route from service. The BGP speaker
> shall run its Decision Process since the older route is no longer
> available for use.
>
>
>
> Khurram Khani wrote:
> >
> > Hi All,
> >
> > Question:
> >
> > If I add a route-map to a BGP neighbour already in ESTABLISHED state and
> > then prepend AS_PATH attibute, do I need to reset BGP neighbour to get
the
> > new changes in new UPDATE Packet?? I dont see Router sending an UPDATE
> > packet though i have changed the AS_Path attribute.
> >
> > When I do a soft-reset I see BGP Router sends out an UPDATE but without
> > WITHDRAWING the previous route. I have a Linux Zebra BGP Router on other
> > side, it ignores the UPDATE coming for an existing Route in the table.
> >
> > Question
> >
> > Q. Does a BGP neighbour needs to withdraw a route first before sending
an
> > update with same NLRI with modified attribute or sending an UPDATE
directly
> > with modified attributes works?
> >
> > Help appreciated
> >
> > thanks
> > Khurram.
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:24 GMT-3