From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Sun Jun 17 2007 - 20:04:22 ART
Max,
Without seeing your FR switch configuration the router configurations
"appear "to be correct. You should try and isolate the problem by doing any
of the following:
1) When you ping remember that it is a two way process that could be broken
in one direction but not the other. When your ping is unsuccessful the
first thing you would to do is do a show ip route for the remote side's IP
address. Although the chances are remote you want to exclude any possibly
of it being a "routing" problem (connected route not in the table, more
specific route in the table, etc). Once you are sure that there isn't a
routing problem enable debug ip icmp on the remote side to see if the pings
are even arriving. If the pings aren't arriving you could debug frame
packet on the local side to see if it shows any problems.
2) You should enable CDP on the multipoint interfaces (off by default) to
see if the remote routers are showing up. This would indicate that layer 2
is or isn't working.
3) Lastly you could try and isolate the problem to being a Frame
Relay/Frame Relay switch problem by using only point-to-point subinterfaces
with /30 addressing.
In regards to inverse ARP it is not even used in your scenario below. With
your configurations none of the routers will send an inverse ARP request for
IP. Also remember that if an interface doesn't have an IP address assigned
that you don't need to apply any IP related commands to it (i.e. no
frame-relay inverse-arp, no ip split-horizon, etc).
--Brian Dennis, CCIE4 #2210 (R&S/ISP-Dial/Security/SP) bdennis@internetworkexpert.com Internetwork Expert, Inc. http://www.InternetworkExpert.com Toll Free: 877-224-8987 Direct: 775-745-6404 (Outside the US and Canada)
On 6/17/07 5:13 AM, "Max Braun" <r_s_lab@mail.com> wrote:
> Hi, Group! > > I have a trouble with frame relay. There is next scheme and > configuration: > > r2 > / \ > r1 r3 > \ / > r4 > > r1: > interface Serial0/0 > no ip address > encapsulation frame-relay IETF > no frame-relay inverse-arp > frame-relay lmi-type ansi > ! > interface Serial0/0.24 multipoint > ip address 172.16.124.1 255.255.255.0 > frame-relay map ip 172.16.124.2 102 broadcast > frame-relay map ip 172.16.124.4 104 broadcast > > r2: > interface Serial0/0 > no ip address > encapsulation frame-relay IETF > no dce-terminal-timing-enable > no frame-relay inverse-arp > frame-relay lmi-type ansi > ! > interface Serial0/0.1 point-to-point > ip address 172.16.124.2 255.255.255.0 > frame-relay interface-dlci 201 > ! > interface Serial0/0.3 point-to-point > ip address 172.16.234.2 255.255.255.0 > frame-relay interface-dlci 203 > > r3: > interface Serial0/0 > no ip address > encapsulation frame-relay IETF > no ip route-cache cef > ip split-horizon > no frame-relay inverse-arp > frame-relay lmi-type ansi > ! > interface Serial0/0.24 multipoint > ip address 172.16.234.3 255.255.255.0 > frame-relay map ip 172.16.234.2 302 broadcast > frame-relay map ip 172.16.234.4 304 broadcast > > r4: > interface Serial0/0 > no ip address > encapsulation frame-relay IETF > no frame-relay inverse-arp > frame-relay lmi-type ansi > ! > interface Serial0/0.1 point-to-point > ip address 172.16.124.4 255.255.255.0 > frame-relay interface-dlci 401 > ! > interface Serial0/0.3 point-to-point > ip address 172.16.234.4 255.255.255.0 > frame-relay interface-dlci 403 > > When I ping the r2 interface from r1 - it's successful, but when I ping > r4 interface from r1 - it's .... > Same scenario with r3 - when I ping r4 - it's success, but when r2 - it's > .... > > > Many thanks, > Max Braun > > -- > Get a Free E-mail Account at Mail.com! > Choose From 100+ Personalized Domains > Visit http://www.mail.com today > > _______________________________________________________________________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Jul 01 2007 - 17:24:49 ART