Frame Relay - Unable to ping local frame relay interfaces

Unanswered Question
Mar 27th, 2007
User Badges:

Frame Relay - Unable to ping localframe relay interfaces and in some case remote frame relay interfaces as well, but LAN to LAN traffic through Frame Relay cloud is fine.


I used to know the reason on why this happens but I have forgotten.


I think local frame-relay interface ping doesn't work because there is no PVC (DLCI) for it, but I don't know why remote frame-relay ping doesn't work.


I have all point-to-point frame relay sub-interfaces.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (2 ratings)
Loading.
flashsplash Tue, 03/27/2007 - 02:27
User Badges:

pls post ur config to getter a better idea what could be the issue...


ciao flash

astanislaus Tue, 03/27/2007 - 03:01
User Badges:


From the NMS on the LAN or HUB router, I cannot ping Spoke 2's frame relay interfaces 10.20.17.9 (far end) or 10.20.17.10 (local end) - Ping timed out in both cases


From the NMS on the LAN of HUB router, I can ping SPOKE 1's frame relay interface 10.20.25.5 (local end), but not 10.20.25.6 (far end) - Destination unreachable.



owaisberg Tue, 03/27/2007 - 12:35
User Badges:

Looked at your configs and I can see that on the spokes you run multipoint interfaces

and use dynamic mapping which is not recommended on these interface types as

mapping can become unpredictable.


Two solutions:


1. Rebuild interfaces on the spokes as

point-to-point subinterfaces, leave the

rest of the commands as it is. Ping to

local interface will work automatically

since you're on point-to-point interface.




2. Use "frame-relay map ip on the spokes. You will need two

frame mappings on each spoke to be able to

ping local interface. Second mapping has to

be mapped to the local interface IP address

with the same DLCI. At the same time on the hub you have to make sure you run multipoint

as well, for that you can recreate current

subinterfaces on the HUB as multipoint ones

and use the same "frame-relay map ip" command

to map to the spokes. Total you will have

4 mappings on the HUB (to cover local ping

issue)


Of course as you can see solution #1 is much more simple but I'm not sure if all current

config on the spokes interfaces can run under

subinterface...if yes then use #1 if not go

for #2


HTH,

OW

astanislaus Tue, 03/27/2007 - 17:11
User Badges:

I will write modified config and post it here for validity check. Thanks for your help.

Actions

This Discussion