From: John Kaberna (jkaberna@xxxxxxxxxxxx)
Date: Fri Feb 09 2001 - 02:17:19 GMT-3
There is no reason to have both. Actually its a big no no to have both.
You have to pick one. You will have different responses depending which
command you use first. I don't have the results memorized since I have
never tried doing it the wrong way. Using the interface-dlci command means
you want to rely on inverse-arp whereas with frame map you are statically
mapping a destination ip to a dlci.
----- Original Message -----
From: Peter Puczko <ppuczko@excite.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, February 08, 2001 9:16 PM
Subject: Re: ccbootcamp lab#1
> In addition to.
>
> Peter
>
> On Thu, 8 Feb 2001 20:54:53 -0800, John Kaberna wrote:
>
> > Peter are you suggesting that he use the interface-dlci concurrently
with
> > the frame map statement or instead of frame map?
> >
> > ----- Original Message -----
> > From: Peter Puczko <ppuczko@excite.com>
> > To: Steven Weber <itweber@netzero.net>; Peter Puczko
<ppuczko@excite.com>
> > Cc: <ccielab@groupstudy.com>
> > Sent: Thursday, February 08, 2001 8:32 PM
> > Subject: Re: ccbootcamp lab#1
> >
> >
> > > 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