Perceptive - I did have some mistakes in what I pasted. I had it completely
wrong, inverse-arp was disabled AFTER it had already done its job. 

I reconfigured to what I think is correct now on R6 (R4 mirrors this):

interface Serial0/1/0
 ip address 142.42.64.6 255.255.224.0
 encapsulation frame-relay
 clock rate 2000000
 frame-relay map ip 142.42.64.4 604 broadcast
 frame-relay map ip 142.42.64.6 604 broadcast
 no frame-relay inverse-arp
end


R6(config-if)#do ping 142.42.64.4

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 142.42.64.4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
R6(config-if)#do ping 142.42.64.6

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 142.42.64.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms

Now I can ping myself though - so...yeah. I think the fact that I had it
wrong (and thought it was wrong) but that inverse-arp had already done it's
thing and got things working for me was throwing me off (easy to do with
frame).

My configuration uses a 2821 as a frame switch. The clock rate command just
shows up in the default interface configuration for some reason.

My frame switch has the following configuration:

frame-relay switching

interface Serial0/0/0
 description Int to R2
 no ip address
 encapsulation frame-relay
 cdp enable
 frame-relay intf-type dce
 frame-relay route 204 interface Serial0/1/0 402
 frame-relay route 205 interface Serial0/2/0 502
 frame-relay route 206 interface Serial0/3/0 602
 frame-relay route 214 interface Serial0/1/0 412
 frame-relay route 215 interface Serial0/2/0 512
 frame-relay route 216 interface Serial0/3/0 612
 frame-relay route 224 interface Serial0/1/0 422
 frame-relay route 225 interface Serial0/2/0 522
 frame-relay route 226 interface Serial0/3/0 622
!
interface Serial0/1/0
 description int to R4
 no ip address
 encapsulation frame-relay
 clock rate 2000000
 cdp enable
 frame-relay intf-type dce
 frame-relay route 402 interface Serial0/0/0 204
 frame-relay route 405 interface Serial0/2/0 504
 frame-relay route 406 interface Serial0/3/0 604
 frame-relay route 412 interface Serial0/0/0 214
 frame-relay route 415 interface Serial0/2/0 514
 frame-relay route 416 interface Serial0/3/0 614
 frame-relay route 422 interface Serial0/0/0 224
 frame-relay route 425 interface Serial0/2/0 524
 frame-relay route 426 interface Serial0/3/0 624
!
interface Serial0/2/0
 description int to R5
 no ip address
 encapsulation frame-relay
 cdp enable
 frame-relay intf-type dce
 frame-relay route 502 interface Serial0/0/0 205
 frame-relay route 504 interface Serial0/1/0 405
 frame-relay route 506 interface Serial0/3/0 605
 frame-relay route 512 interface Serial0/0/0 215
 frame-relay route 514 interface Serial0/1/0 415
 frame-relay route 516 interface Serial0/3/0 615
 frame-relay route 522 interface Serial0/0/0 225
 frame-relay route 524 interface Serial0/1/0 425
 frame-relay route 526 interface Serial0/3/0 625
!
interface Serial0/3/0
 description int to R6
 no ip address
 encapsulation frame-relay
 cdp enable
 frame-relay intf-type dce
 frame-relay route 602 interface Serial0/0/0 206
 frame-relay route 604 interface Serial0/1/0 406
 frame-relay route 605 interface Serial0/2/0 506
 frame-relay route 612 interface Serial0/0/0 216
 frame-relay route 614 interface Serial0/1/0 416
 frame-relay route 615 interface Serial0/2/0 516
 frame-relay route 622 interface Serial0/0/0 226
 frame-relay route 624 interface Serial0/1/0 426
 frame-relay route 625 interface Serial0/2/0 526

Magical connectivity is bad.

-Mike


-----Original Message-----
From: Matt Hill [mailto:[email protected]] 
Sent: Saturday, August 15, 2009 4:35 PM
To: Bryan Bartik
Cc: Michael Lipsey; [email protected]
Subject: Re: [OSL | CCIE_RS] Simple Frame-Relay Question

Hi Michael,

I'm curious as to how that is working....

Did you no shut the interface prior to entering "encapsulation
frame-relay" or after?  Do you have dynamic frame-relay maps? (show
frame-relay map).  Otherwise you don't have an l2-l3 mapping.

Also, you have clock rate xxxx  is this back to back or going via a
frame switch?  Clock rate sets the interface type to dce and is
superfluous if you are going via a switch.  If its back to back you
should also use frame-relay intf-type dce at one end (not necessarily
the serial dce end, but its a good idea to keep it consistent)

To summarise:
I think you did "no shut" then did "encapsulation frame-relay" and
then inverse-arp kicked in and learned all the dynamic l2-l3 mappings.
 After that you put in "no frame-relay inverse-arp" but by that stage
it had already done its trick.


Afterthought:  I also see your "do ping" is from dlci config mode.
Did you enter dlci information?  There isnt any shown in the config.
If you did then inverse-arp doent happen, but also other things will
go wrong with the ip address on the physical interface rather than on
the dlci.

I'm not trying to be a pain but if your frame-relay is cactus then so
is your ospf and you will see ridiculous neighbours pop up on dlcis
that they shouldnt be and there begins the world of hurt...

Cheers,
Matt

CCIE #22386
CCSI #31207

2009/8/16 Bryan Bartik <[email protected]>:
> Michael,
>
> That's correct. If you want to ping yourself then create a static map for
> your address. Be careful as this is not always allowed.
>
> On Sat, Aug 15, 2009 at 5:03 PM, Michael Lipsey <[email protected]>
> wrote:
>>
>> So…yeah – I am not the brightest frame-relay star.
>>
>>
>>
>> I seem to recall that in some configurations you just can’t ping yourself
>> – my topology works just fine but I wanted to make myself feel better so
>> here’s  my basic Frame config (nothing special) I don’t expect I can ping
>> myself here:
>>
>>
>>
>> interface Serial0/1/0
>>
>>  ip address 142.42.64.6 255.255.224.0
>>
>>  encapsulation frame-relay
>>
>>  clock rate 2000000
>>
>>  no frame-relay inverse-arp
>>
>>  frame-relay lmi-type cisco
>>
>> end
>>
>>
>>
>> R6(config-fr-dlci)#do ping 142.42.64.4
>>
>>
>>
>> Type escape sequence to abort.
>>
>> Sending 5, 100-byte ICMP Echos to 142.42.64.4, timeout is 2 seconds:
>>
>> !!!!!
>>
>> Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms
>>
>> R6(config-fr-dlci)#do ping 142.42.64.6
>>
>>
>>
>> Type escape sequence to abort.
>>
>> Sending 5, 100-byte ICMP Echos to 142.42.64.6, timeout is 2 seconds:
>>
>> .....
>>
>> Success rate is 0 percent (0/5)
>>
>>
>>
>> And I can’t (and I get the same results on the other side of the
interface
>> – R4).
>>
>>
>>
>>
>>
>> Correct me if I am wrong please.
>>
>>
>>
>> Thanks,
>>
>> -Mike
>>
>> _______________________________________________
>> For more information regarding industry leading CCIE Lab training, please
>> visit www.ipexpert.com
>>
>
>
>
> --
> Bryan Bartik
> CCIE #23707 (R&S), CCNP
> Sr. Support Engineer - IPexpert, Inc.
> URL: http://www.IPexpert.com
>
> _______________________________________________
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
>

_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to