From: John Kaberna (jkaberna@xxxxxxxxxxxx)
Date: Fri Feb 09 2001 - 03:25:18 GMT-3
The routing table is not affected by policy routing in this scenario. The
way the route-maps work is that they go through the map and if their is a
match then it is policy routed. If there is no match the packet is turned
over to the normal routing table.
----- Original Message -----
From: Thomas Trygar <trygar@wans.net>
Cc: <ccielab@groupstudy.com>
Sent: Friday, February 09, 2001 10:09 AM
Subject: Re: ccbootcamp lab#1
> I've done Lab 1 a few times and is it normal for 'show ip route' to keep
> giving you the original router as next hop? Or is it that the routing
table is
> correct and will never change, but then the 'local policy' will take
effect?
> I.E. that local policy is the last task perform?
>
> Local policies work and issuing the trace commands displays 10.10.1.1
> (Router1) in the output. e output displaying Router1 10.10.1.1
>
> Tom
>
> John Kaberna wrote:
>
> > I am nearly certain the proctor will not give you the points on the lab
if
> > you use both. It's not recommended nor is it necessary. I would
suggest
> > learning which situations each is useful for and thoroughly
understanding
> > the differences.
> >
> > ----- Original Message -----
> > From: Peter Puczko <ppuczko@excite.com>
> > To: <ccielab@groupstudy.com>
> > Sent: Thursday, February 08, 2001 9:20 PM
> > Subject: Re: ccbootcamp lab#1
> >
> > > I use both and never had a problem with that.
> > >
> > > Peter
> > >
> > >
> > > On Fri, 09 Feb 2001 00:12:08 -0500, Les Hardin wrote:
> > >
> > > > Peter,
> > > >
> > > > The map statements take care of that stuff. You don't need both
map
> > and
> > > > interface-dlci commands. At least, I've never used both, and I've
> > never
> > > > had problems. Although, I have seen folks use both (like in the
> > Solutions
> > >
> > > > Labs labs). Am I missing something?
> > > >
> > > > Les
> > > >
> > > >
> > > > At 08:32 PM 2/8/2001 -0800, Peter Puczko wrote:
> > > > >Do not mix frame relay behaviour and OSPF.
> > > > >DLCIs are bound to the major interface s0 after you configure
> > > encapsulation
> > > > >frame relay. If you want those DLCIs to be used on subinterface
you
> > have
> > > to
> > > > >add those lines into configuration. They don't just migrate there
> > > > >auto-magically.
> > > > >Once you put them there and verify IP connectivity you can start
> > > thinking
> > > > >about OSPF part of it.
> > > > >
> > > > >Peter
> > > > >
> > > > >
> > > > >On Thu, 08 Feb 2001 23:22:28 -0500, Steven Weber wrote:
> > > > >
> > > > > > If you do that then you need ip ospf network command and we
are
> > > trying to
> > > > >avoid
> > > > > > that
> > > > > >
> > > > > > Peter Puczko wrote:
> > > > > >
> > > > > > > Where are your "frame-relay interface-dlci xxx" commands
under
> > > s0.1?
> > > > > > >
> > > > > > > Peter
> > > > > > >
> > > > > > > On Thu, 08 Feb 2001 22:53:58 -0500, Steven Weber wrote:
> > > > > > >
> > > > > > > > I'm having some problems with my config I can't get any
of
> > the
> > > > >spokes to
> > > > > > > > ping each other any suggestions.Current configuration:
> > > > > > > > !
> > > > > > > > version 11.2
> > > > > > > > !
> > > > > > > > hostname r1
> > > > > > > > !
> > > > > > > > !
> > > > > > > > no ip domain-lookup
> > > > > > > > ip host r2 2001 10.1.1.100
> > > > > > > > ip host r3 2002 10.1.1.100
> > > > > > > > ip host r4 2003 10.1.1.100
> > > > > > > > ip host r5 2004 10.1.1.100
> > > > > > > > ip host r7 2006 10.1.1.100
> > > > > > > > !
> > > > > > > > interface Loopback0
> > > > > > > > ip address 10.1.1.100 255.255.255.0
> > > > > > > > !
> > > > > > > > interface Ethernet0
> > > > > > > > ip address 10.100.100.1 255.255.0.0
> > > > > > > > no keepalive
> > > > > > > > !
> > > > > > > > interface Serial0
> > > > > > > > no ip address
> > > > > > > > encapsulation frame-relay
> > > > > > > > ip ospf priority 10
> > > > > > > > !
> > > > > > > > interface Serial0.1 multipoint
> > > > > > > > ip address 10.10.1.1 255.255.0.0
> > > > > > > > ip policy route-map FRAM
> > > > > > > > frame-relay map ip 10.10.1.2 102
> > > > > > > > frame-relay map ip 10.10.1.3 103
> > > > > > > > frame-relay map ip 10.10.1.5 105
> > > > > > > > !
> > > > > > > > interface Serial1
> > > > > > > > no ip address
> > > > > > > > shutdown
> > > > > > > > !
> > > > > > > > router ospf 1
> > > > > > > > network 10.10.0.0 0.0.255.255 area 0
> > > > > > > > network 10.100.0.0 0.0.255.255 area 1
> > > > > > > > neighbor 10.10.1.3 priority 1
> > > > > > > > neighbor 10.10.1.2 priority 1
> > > > > > > > neighbor 10.10.1.5 priority 1
> > > > > > > > !
> > > > > > > > ip classless
> > > > > > > > access-list 100 permit ip any 10.10.0.0 0.0.255.255
> > > > > > > > access-list 101 permit ip any 10.10.0.0 0.0.255.255
> > > > > > > > access-list 102 permit ip any 10.10.0.0 0.0.255.255
> > > > > > > > route-map FRAM permit 10
> > > > > > > > match ip address 100
> > > > > > > > set ip next-hop 10.10.1.2
> > > > > > > > !
> > > > > > > > route-map FRAM permit 20
> > > > > > > > match ip address 101
> > > > > > > > set ip next-hop 10.10.1.3
> > > > > > > > !
> > > > > > > > route-map FRAM permit 30
> > > > > > > > match ip address 102
> > > > > > > > set ip next-hop 10.10.1.5
> > > > > > > > !
> > > > > > > > !
> > > > > > > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:42 GMT-3