Every multipoint interface needs to have some way of know who is on the
other side.  Inverse ARP is the default method.  Manual L3-L2 mapping
certainly works fine as well.  Point-to-point configuration changes the
logic because now there's no doubt of who's on the other end!
 
So if you were to do "debug ip packet" on each side.  One side (that had the
mapping) would send things out just fine.  The other side (which did NOT
have a manual mapping) would receive the packet without a problem, but when
it went to reply, you would see "encapsulation failed" messages meaning that
it didn't know exactly where to send the response to at a Layer2 address.
 
Either of the methods below would solve the problem!
 
HTH,
 


Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE-M
#153, JNCIS-ER, CISSP, et al.
CCSI/JNCI-M/JNCI-ER
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor

A Cisco Learning Partner - We Accept Learning Credits!

[EMAIL PROTECTED]

 

Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com

 


  _____  

From: MAK [mailto:[EMAIL PROTECTED] 
Sent: Sunday, January 27, 2008 11:58 PM
To: [EMAIL PROTECTED]
Cc: [email protected]
Subject: Fw: Frame Relay porblem


HI,
 
 
 attached are two running-config files for respecitve routers R5 and R6...

R5 is configured with point to point sub-interface s0/1.1 which is pointing
to R6 S0/1 without any point to point subinterface configured on R6. With
current config I can't ping either way but when I am doing show frame-relay
map on R-5 then I can see the static map to R-6 which is showing active
state. But when I see the show frame-relay map on R6 then there is not entry
there. 

I found that communication starts in the below two scenarios:

1) If I enable inverse-arp on R6 s0/1

2) If I configure a point to point sub-interface on R6 with frame-relay
interface-dlci command.

 

My questions is why the subinterface is not communicating without giving
inverse-arp or making a subinterface on r6.

Regards

MAK

 

 

 

Reply via email to