frame-relay map

From: chiragshroff (chiragshroff@myrealbox.com)
Date: Tue Jun 10 2003 - 05:25:49 GMT-3


dear............. brian dennis,jung jin and group

yes definately..............you just try this statement in this example

R4
int S0
frame-relay map ip 10.1.1.2 201 broadcast
frame-relay map ip 10.1.1.5 201 ...........???

R5
int S0
frame-relay map ip 10.1.1.2 301 broadcast
frame-relay map ip 10.1.1.4 301 ...........???

we dont require broadcast key word on the next statement...........i have
tested it......i think we dont need that keyword on spok to spok
maping....???

if i am wrong plz explain me.

----- Original Message -----
From: Brian Dennis <brian@labforge.com>
To: 'Jung, Jin' <jin.jung@lmco.com>; 'chiragshroff'
<chiragshroff@myrealbox.com>; 'Group' <ccielab@groupstudy.com>
Sent: Monday, June 09, 2003 09:59 PM
Subject: RE:

> The broadcast has to be sent via the hub so do you think the hub will
> forward the broadcast?
>
> Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Jung, Jin
> Sent: Monday, June 09, 2003 8:31 AM
> To: 'chiragshroff'; Group
> Subject: RE:
>
> Yes,,
> Without it your IGP will not work, like ospf and eigrp
> Try it.
>
> Remember, you are working in NBMA network, non-broadcast multi access.
>
> Jin jung...
>
> -----Original Message-----
> From: chiragshroff [mailto:chiragshroff@myrealbox.com]
> Sent: Monday, June 09, 2003 4:02 AM
> To: Group
> Subject:
>
>
> thnx for your setisfactory answer .................but
>
> why we should give "broadcast" keywork after framerelay map statement of
> spok to spok router maping...............is that necessary.
>
>
> ----- Original Message -----
> From: John Underhill <stepnwlf@magma.ca>
> To: chiragshroff <chiragshroff@myrealbox.com>; Group
> <ccielab@groupstudy.com>
> Sent: Monday, June 09, 2003 01:10 AM
> Subject: Re: routing protocol over frame-relay
>
>
> > If you are using point-to-multipoint as ospf type on hub and spokes,
> > you
> can
> > use inverse arp, or create mappings between all nodes. Spokes are
> > mapped
> to
> > each other using the hubs DLCI. In EIGRP, the same frame mappings will
> work,
> > so long as you have disabled split horizon on the hub, and use
> > neighbor statements on hub and spokes..
> >
> > R2
> > D 192.168.4.0/24 [90/2297856] via 10.1.1.4, 00:00:10, Serial0.1
> > D 192.168.5.0/24 [90/2297856] via 10.1.1.5, 00:03:53, Serial0.1
> > 10.0.0.0/24 is subnetted, 1 subnets
> > C 10.1.1.0 is directly connected, Serial0.1
> > C 192.168.2.0/24 is directly connected, Loopback0
> > 150.50.0.0/24 is subnetted, 2 subnets
> > C 150.50.9.0 is directly connected, Dialer0
> > C 150.50.17.0 is directly connected, Ethernet0
> >
> > interface Serial0.1 multipoint
> > ip address 10.1.1.2 255.255.255.0
> > no ip split-horizon eigrp 100
> > frame-relay map ip 10.1.1.4 101 broadcast
> > frame-relay map ip 10.1.1.5 102 broadcast
> > no frame-relay inverse-arp
> >
> > router eigrp 100
> > passive-interface default
> > no passive-interface Serial0.1
> > network 10.0.0.0
> > network 192.168.2.0
> > neighbor 10.1.1.5
> > neighbor 10.1.1.4
> > no auto-summary
> > !
> >
> > R4
> > Gateway of last resort is not set
> >
> > 172.16.0.0/24 is subnetted, 1 subnets
> > C 172.16.1.0 is directly connected, TokenRing0
> > C 192.168.4.0/24 is directly connected, Loopback0
> > D 192.168.5.0/24 [90/2809856] via 10.1.1.2, 00:01:07, Serial0
> > 10.0.0.0/24 is subnetted, 1 subnets
> > C 10.1.1.0 is directly connected, Serial0
> > D 192.168.2.0/24 [90/2297856] via 10.1.1.2, 00:01:07, Serial0
> >
> > interface Serial0
> > ip address 10.1.1.4 255.255.255.0
> > no ip directed-broadcast
> > encapsulation frame-relay
> > logging event subif-link-status
> > logging event dlci-status-change
> > frame-relay map ip 10.1.1.2 201 broadcast
> > frame-relay map ip 10.1.1.5 201 broadcast
> > no frame-relay inverse-arp
> >
> > router eigrp 100
> > network 10.0.0.0
> > network 192.168.4.0
> > neighbor 10.1.1.2
> > neighbor 10.1.1.5
> > no auto-summary
> >
> > R5
> > Gateway of last resort is not set
> >
> > 172.16.0.0/24 is subnetted, 1 subnets
> > C 172.16.1.0 is directly connected, TokenRing0
> > D 192.168.4.0/24 [90/2809856] via 10.1.1.2, 00:01:18, Serial0
> > C 192.168.5.0/24 is directly connected, Loopback0
> > 10.0.0.0/24 is subnetted, 1 subnets
> > C 10.1.1.0 is directly connected, Serial0
> > D 192.168.2.0/24 [90/2297856] via 10.1.1.2, 00:01:39, Serial0
> > 150.50.0.0/24 is subnetted, 2 subnets
> > C 150.50.9.0 is directly connected, Dialer0
> > C 150.50.18.0 is directly connected, Serial1
> >
> > interface Serial0
> > ip address 10.1.1.5 255.255.255.0
> > no ip directed-broadcast
> > encapsulation frame-relay
> > logging event subif-link-status
> > logging event dlci-status-change
> > no fair-queue
> > frame-relay map ip 10.1.1.2 301 broadcast
> > frame-relay map ip 10.1.1.4 301 broadcast
> > no frame-relay inverse-arp
> >
> > router eigrp 100
> > network 10.0.0.0
> > network 192.168.5.0
> > neighbor 10.1.1.4
> > neighbor 10.1.1.2
> > no auto-summary
> >
> >
> >
> > ----- Original Message -----
> > From: "chiragshroff" <chiragshroff@myrealbox.com>
> > To: "Group" <ccielab@groupstudy.com>
> > Sent: Sunday, June 08, 2003 11:57 AM
> > Subject: routing protocol over frame-relay
> >
> >
> > > hello every body,
> > >
> > > in framrelay p-t-m network.on spok routers we r giving framerelay
> > > map
> > command
> > > to map other spok router.if we dont ginve it and will give only map
> > > to
> hub
> > it
> > > will not work with eigrp while it will work with ospf ...........as
> > > we
> > will
> > > give ip ospf net p-t-m command.
> > >
> > > is that a behaviour of ospf to work on fram relay point to
> > > multipoing network then is there any command in eigrp or other
> > > routing portocol to work on ........
> > >
> > > is that necessary in ccie lab that we have to up the basic p-t-m
> > framerelay
> > > whether it work with ospf or eigrp...........???
> > >
> > > have a nice day
> > > regards,
> > >
> > > chirag
>
> have a nice day
> regards,
>
> chirag



This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:10:55 GMT-3