From: ccie2be (ccie2be@nyc.rr.com)
Date: Sat May 10 2003 - 14:31:09 GMT-3
Hi group,
I've lost count of how many hours of my life I've spent troubleshooting F/R
misconfigurations including in the F/R map statement wrong remote ip address,
wrong DLCI, and missing Broadcast keyword.
So, when I came across some material in a Cisco Press book which described how
each of these misconfigurations could be quickly diagnosed, I was very
excited.
Unfortunately, the test for one of the mistakes - wrong remote ip address -
didn't exhibit the symptoms as described. The book said that if you enter the
wrong ip addr in the map statement, when you did a show frame map, you would
see the ip address. It would be missing.
I tried it and contrary to what the book said, the wrong ip address was right
there in the output.
So, I'm wondering did I do something wrong in recreating this problem or is
the book wrong?
Assuming the book is wrong, what's the best way to identify and isolate a
wrong ip address in the F/R map statement?
Up to now, what I've been doing is checking the ip addr in the map statement
and then going to the remote router and checking the ip addr there. I don't
like this method because I find it so easy to miss transposed numbers or check
the wrong interface, etc and end up wasting so much time. So, if there's a
better method, I'd really like hear about it.
Thanks, Jim
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:40 GMT-3