Hi Carlos,
Well, Im really not an Frame-Relay Expert but after a bit googling around I found the following article which confused me a bit. Until now, I only configured no frame-relay inverse-arp under the physical interface, which I also teached by the Proctor Guide even for multipoint subinterfaces, but after reading the following article Im not 100% sure anymore . http://cciepursuit.wordpress.com/2007/08/22/frame-relay-subinterfaces-do-not -inherit-inverse-arp-configuration/ Well, maybe there is a real master of frame-relay out there :o)) which could clarify this?? Thanks Roger Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Carlos Valero Gesendet: Montag, 28. April 2008 19:48 An: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [email protected] Betreff: Re: [OSL | CCIE_RS] Frame-Relay Hello, Here you said the InvARP is on by default. Question is: Is it enabled by default on physical interfaces AND on multipoint subinterfaces? I read that it is enabled by default for all network layer protocols enabled on the Physical Interface only! I know that InvArp is not needed for point-to-point subinterfaces. But I'm not sure about multipoint subinterfaces. Is it also on by default in real life? Thanks! Scott Morris <[EMAIL PROTECTED]> wrote: In a multipoint interface, you need something to map L3 to L2 reachability. In ethernet, we have ARP to do that for us. In frame-relay, we have either Inverse-ARP (on by default, but likely disabled in the lab) or we have static mapping. But this MUST be done, or we have no reachability and therefore can't encapsulate! Cheers, _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, February 17, 2008 2:29 AM To: [EMAIL PROTECTED]; [email protected] Subject: RE: [OSL | CCIE_RS] Frame-Relay I have just executed Debug IP Packet, and in fact seem like that knows the interface to use, however the message Encapsulation failed revealed no information L2-L3, I thought to reach directly connected although without static mapping. In the meantime I thank you everyone for support. ----- Original message ----- From: "Scott Morris" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [email protected] Date: Sat, 16 Feb 2008 20:04:09 -0500 Subject: RE: [OSL | CCIE_RS] Frame-Relay Try looking at the output of "debug ip packet" as you do the various pings! That may help highlight the missing piece there from pinging yourself versus the other devices! 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Saturday, February 16, 2008 12:17 PM To: [email protected] Subject: [OSL | CCIE_RS] Frame-Relay I`ve just configured Frame-Relay Hub and Spoke, plus point-to-point. with point-to-point no problem, with Hub and spoke I pinged only the spokes but not myself,same thing for both spokes, not reachability for myself. Can someone help me? Straight forward the config for Hub: interface Serial0/1/0 no ip address encapsulation frame-relay ! interface Serial0/1/0.100 multipoint ip address 150.50.100.2 255.255.255.224 frame-relay map ip 150.50.100.5 205 broadcast frame-relay map ip 150.50.100.6 206 broadcast ! interface Serial0/1/0.104 point-to-point ip address 150.50.24.2 255.255.255.0 frame-relay interface-dlci 104 ! interface Serial0/2/0 description Link to R5 ip address 150.50.9.2 255.255.255.192 clock rate 2000000 ! interface FastEthernet1/0 description Link to Switch1 no switchport ip address 150.50.17.2 255.255.255.0 Spoke: interface Loopback0 ip address 200.0.0.5 255.255.255.255 ! interface FastEthernet0/0 description Link to Switch1 ip address 150.50.7.5 255.255.255.128 duplex auto speed auto ! interface FastEthernet0/1 no ip address shutdown duplex auto speed auto ! interface Serial0/1/0 ip address 150.50.100.5 255.255.255.224 encapsulation frame-relay frame-relay map ip 150.50.100.2 502 broadcast frame-relay map ip 150.50.100.6 506 broadcast ! interface Serial0/2/0 description Link to R2 ip address 150.50.9.5 255.255.255.192 -- This message is intended for the individual(s) to whom it is addressed and may contain information that is privileged or confidential. If you are not the addressee you must not read,use or disclose the contents of this email. Whilst all reasonable care has been taken to avoid the transmission of viruses, the recipient should carry out virus and other checks, as they consider appropriate. Myself accepts no responsibility in this regard. -- This message is intended for the individual(s) to whom it is addressed and may contain information that is privileged or confidential. If you are not the addressee you must not read,use or disclose the contents of this email. Whilst all reasonable care has been taken to avoid the transmission of viruses, the recipient should carry out virus and other checks, as they consider appropriate. Myself accepts no responsibility in this regard. _____ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try <http://us.rd.yahoo.com/evt=51733/*http:/mobile.yahoo.com/;_ylt=Ahu06i62sR8H DtDypao8Wcj9tAcJ%20> it now.
