From: Richard Davidson (rich@myhomemail.net)
Date: Tue Apr 27 2004 - 15:45:30 GMT-3
This is an excerpt from Alex Zinin's book called Cisco
IP routing. It describes how a router decides whether
a route should be redistributed and is based on the
TredistributeInfo data structure (programmer lingo, if
you ask me). I think it's the data structure for all
routing protocols except ISIS.
I'm sharing this excerpt because it has helped me a
lot. My guess is that the ISIS data structure is
similar but doesn't include 1.C in the description
bellow.
Rich
Page 285
1. If a route is directly connected, perform the
following:
A. If the route is covered by a network statement of
the redistributing protocol, it is announced internal
to that protocol and is not redistributed. ("continue
to B")
B. otherwise, if an explicit redistribute connected or
a redistribute static command is configured and a
route is not filtered out by a corresponding
distribute list, it is accepted and redistributed.
("continue to C")
C. Otherwise, if the route is covered by a network
statement of a redistributed protocol and is not
filtered by a distribute list specific for
redistribution out of this protocol, the route is
accepted for redistribution. ("If using ISIS C may not
be used but I am not sure, continue to D")
D. Otherwise, the directly connected route is not
redistributed.
2. If the route is not directly connected it is
redistributed only when there is a corresponding
redistribute statement for the route source and the
route is not filtered by a corresponding distribute
list.
--- Adam Asay <aasay@cerberian.com> wrote:
> Does anyone have a good example of mutual isis and
> ospf redistribution. I
> am having some problems grasping the concepts with
> isis and the connected
> routes.
>
> Thanks for the help.
>
> -Adam
>
>
This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:56 GMT-3