From: gary braver (gbraver@xxxxxxxxx)
Date: Thu Jun 06 2002 - 17:28:56 GMT-3
Brian
Agreed - leaving things for chance in the lab is not a good idea. Shorting
commands at the expense of adding complexity is not a good strategy
-----Original Message-----
From: Brian Dennis [mailto:brian@5g.net]
Sent: Thursday, June 06, 2002 3:46 PM
To: gary_braver@ins.com; 'gary braver'; ccielab@groupstudy.com
Subject: RE: Frame-relay Inverse-arp
Gary,
You're better off having as much of the network configuration static as
opposed to being dynamic in the lab. I'm not just referring to frame
mappings. Anything that you can hard code by using distribute lists,
route-maps, dialer maps, etc) to ensure that it's going to work the way
you expect it to the better off you are in the lab. By making the
network dynamic you open yourself up to the "possibility" of problems.
Being that typing the frame-relay interface-dlci command is faster than
typing the frame-relay map command is not a good reason to use one over
the other. People take the "speed" issue in the lab the wrong way. It
isn't that someone can type faster than someone else that enables them
to pass. It's the fact that someone can configure a complex task off the
top of the head and make it work the first time without having to spend
time troubleshooting it or referring to the documentation CD.
Brian Dennis, CCIE #2210 (R&S/ISP Dial)
-----Original Message-----
From: Gary Braver [mailto:gary_braver@ins.com]
Sent: Thursday, June 06, 2002 11:28 AM
To: 'Brian Dennis'; 'gary braver'; ccielab@groupstudy.com
Subject: RE: Frame-relay Inverse-arp
summarizing the discussion
recommendation is to use frame-relay map and disable arp as gives
greater
confidence that it is going to work.
I personally have not seen in-arp problems with frame and IP but you
never
know (and frame-relay interface-dlci xxx is shortner to type than the
map
statement).
gary
-----Original Message-----
From: Brian Dennis [mailto:brian@5g.net]
Sent: Thursday, June 06, 2002 2:17 PM
To: 'gary braver'; ccielab@groupstudy.com
Subject: RE: Frame-relay Inverse-arp
In the real CCIE lab why would you want to rely on something dynamic and
hope it works when you can just hard code it and be sure it's going to
work?
Brian Dennis, CCIE #2210 (R&S/ISP Dial)
bdennis@5g.net
5G Networks, Inc.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
gary braver
Sent: Thursday, June 06, 2002 10:29 AM
To: 'Erhan Kurt'; 'Joe Jia'; ccielab@groupstudy.com
Subject: RE: Frame-relay Inverse-arp
Know how to disable inarp and put in map statments. My question is why
should we disable inarp and not rely on dynamic mappings?
thanks
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Erhan Kurt
Sent: Tuesday, June 04, 2002 4:44 AM
To: Joe Jia; ccielab@groupstudy.com
Subject: RE: Frame-relay Inverse-arp
Use "no fram inv" every FR interfaces except point-to-point. i.e. Do not
rely on dynamic mappings even for IPX.
Never Give Up,
Erhan
-----Original Message-----
From: Joe Jia [mailto:ellenjjl@rogers.com]
Sent: 09 May}s 2002 Per~embe 01:55
To: ccielab@groupstudy.com
Subject: Frame-relay Inverse-arp
Hi,
I have been confused by frame-relay inverse-arp and arp frame-relay.
For
example, suppose that Router R1, R2, R3, R4 fully messed to configure
IP.
Only R1 can use subinterfaces, say s0.1 point-to-point (to R4), s0.2
multipoint (to R2 and R3). The requirement is that on R4 can not use
subinterface and map. I also don't want to see R2,R3's IP address on R4,
and
on R2,R3 can't see R4's IP address. (Show Frame-relay map"
With the following configuration, I reloaded the Routers, but still
can't
solve the problem.
(1)on R4 cannot see R2, R3's IP address? Even though on R2, R3, I
configured "no frame-relay inverse" and "no arp frame-relay".
(2)On R4, whether or not put "no arp frame-relay", on R2,R3 can still
see
R4's IP address.
R1:
interface Serial0
no ip address
no ip directed-broadcast
encapsulation frame-relay
no ip mroute-cache
no arp frame-relay
no fair-queue
clockrate 64000
no frame-relay inverse-arp
!
interface Serial0.1 point-to-point
ip address 137.20.100.2 255.255.255.0
no ip directed-broadcast
frame-relay interface-dlci 131
!
interface Serial0.2 multipoint
ip address 137.20.101.1 255.255.255.0
no ip directed-broadcast
frame-relay map ip 137.20.101.3 132 broadcast
frame-relay map ip 137.20.101.5 130 broadcast
R4:
interface Serial0
ip address 137.20.100.1 255.255.255.0
no ip directed-broadcast
encapsulation frame-relay
no ip mroute-cache
no arp frame-relay
no fair-queue
clockrate 64000
frame-relay interface-dlci 123
R2:
interface Serial0
ip address 137.20.101.3 255.255.255.0
no ip directed-broadcast
encapsulation frame-relay
no ip mroute-cache
logging event subif-link-status
logging event dlci-status-change
no fair-queue
clockrate 64000
no arp frame-relay
frame-relay map ip 137.20.101.1 231 broadcast
no frame-relay inverse-arp
R3:
interface Serial0
ip address 137.20.101.5 255.255.255.0
no ip directed-broadcast
encapsulation frame-relay
no ip mroute-cache
logging event subif-link-status
logging event dlci-status-change
no fair-queue
clockrate 64000
no arp frame-relay
frame-relay map ip 137.20.101.1 230 broadcast
no frame-relay inverse-arp
Show Frame-relay map:
R1:
Serial0.2 (up): ip 137.20.101.3 dlci 132(0x84,0x2040), static,-`R2
broadcast,
CISCO, status defined, active
Serial0.2 (up): ip 137.20.101.5 dlci 130(0x82,0x2020), static, `R3
broadcast,
CISCO, status defined, active
Serial0.1 (up): point-to-point dlci, dlci 131(0x83,0x2030),
broadcast`R4
status defined, active
R4:
Rack01R2#sh fram map
Serial0 (up): ip 137.20.100.2 dlci 123(0x7B,0x1CB0), dynamic,`R1
broadcast,, status defined, active
Serial0 (up): ip 137.20.101.3 dlci 400(0x190,0x6400), dynamic, --`R2
broadcast,, status defined, active
Serial0 (up): ip 137.20.101.5 dlci 200(0xC8,0x3080), dynamic,-`R3
broadcast,, status defined, active
R2:
Serial0 (up): ip 137.20.100.1 dlci 400(0x190,0x6400), dynamic,`R4
broadcast,, status defined, active
Serial0 (up): ip 137.20.101.1 dlci 231(0xE7,0x3870), static, `R1
broadcast,
CISCO, status defined, active
R3:
Serial0 (up): ip 137.20.100.1 dlci 200(0xC8,0x3080), dynamic, `R4
broadcast,, status defined, active
Serial0 (up): ip 137.20.101.1 dlci 230(0xE6,0x3860), static,-`R1
broadcast,
CISCO, status defined, active
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:27 GMT-3