FrameRelay Cloud

From: Emil Patel (emilpatel@hotmail.com)
Date: Sat Sep 08 2007 - 21:39:46 ART


I am setting up a lab and have question about FrameRelay Cloud.

R1>- FR>- R2

R1 Config is:

in s 0/0
encap frame relay

int s0/0.1 multipoint
ip adress 172.16.123.1 255.255.255.0
no frame inv-arp
frame-relay map ip 172.16.123.2 102 broadcast

R2 config is:

int s0/0
ip adress 172.16.123.2 255.255.255.0
no frame inv-arp
frame-relay map ip 172.16.123.1 201 broadcast

and framerelay Switch Config is:

frame-relay switching

interface Serial0 description Connected to Rack1R1 no ip address encapsulation
frame-relay no ip route-cache no ip mroute-cache clockrate 2000000 no
fair-queue frame-relay intf-type dce frame-relay route 102 interface Serial1
201 frame-relay route 103 interface Serial2 301 frame-relay route 104
interface Serial4 401 frame-relay route 105 interface Serial5 501 frame-relay
route 113 interface Serial3 311!interface Serial1 description Connected to
Rack1R2 no ip address encapsulation frame-relay no ip route-cache no ip
mroute-cache clockrate 2000000 frame-relay intf-type dce frame-relay route 201
interface Serial0 102 frame-relay route 203 interface Serial2 302 frame-relay
route 204 interface Serial4 402 frame-relay route 205 interface Serial5 502
frame-relay route 213 interface Serial3 312!interface Serial2 description
Connected to Rack1R3 no ip address encapsulation frame-relay no ip route-cache
no ip mroute-cache clockrate 64000 frame-relay intf-type dce frame-relay route
301 interface Serial0 103 frame-relay route 302 interface Serial1 203
frame-relay route 304 interface Serial4 403 frame-relay route 305 interface
Serial5 503

I am unable to ping R2 from R1 and viceversa. I did debug frame packet and
seeing encapsulation failed message. But the I have defined the mappings so I
am really confused what is causing this behavior.

Any feedback will be appreiciated.Emil Patel MD Anderson Cancer Center -
Diagnostic Imaging Making Cancer History!

epatel@mdanderson.org
emilpatel@hotmail.com



This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:10 ART