Run some frame-relay debugging while trying to ping your own serial
interface. You will see an "encapsulation failed" message... The trouble is
that Frame-Relay, being a layer 2 technology, needs to have a way to
translate the IP address of your serial interface (a layer 3 entity) to a
layer 2 address (DLCI).
Configure a "frame-relay map ip (IP address of local serial int) (dlci)" on
the interface and it will work... You need to do the same on the other side.
I hope this helps...
Z
>From: "Niraj Palikhey" <[EMAIL PROTECTED]>
>Reply-To: "Niraj Palikhey" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject: Cannot ping own serial int. in a FR lab env??
>Date: Mon, 26 Mar 2001 07:20:39 -0500
>
><html><DIV>Hi,</DIV>
><DIV>I have setup 3 2501 routers for FR and cannot figure out why I am
>NOT able to ping my own serial int.(10.1.1.1) but can ping the other
>router(10.1.1.2) through the frame relay switch. I face the same problem
>from the other side too. I setup additional 3 router configs. to verify
>this and I have the same problem. Is this only in a lab environment or am I
>missing something? Please advise. Thank you.</DIV>
><DIV>Sincerely,</DIV>
><DIV>[EMAIL PROTECTED]</DIV><br clear=all><hr>Get your FREE
>download of MSN Explorer at <a
>href="http://explorer.msn.com">http://explorer.msn.com</a><br></p></html>
>
>_________________________________
>FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
