I have to admit that "clear frame inarp" has never worked for me.
On Thu, Oct 7, 2010 at 10:14 PM, Di Bias, Steve <[email protected]> wrote: > Sorry I sent that from my home while holding my daughter. In any event I > don’t believe that “clear frame inarp” will remove the 0.0.0.0 entries, in > fact I just tried it again and they are still there. While this command > will clear other entries the 0/0’s seem to return. :/ > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Di Bias, Steve > Sent: Thursday, October 07, 2010 6:58 PM > To: [email protected]; [email protected] > Cc: [email protected] > Subject: Re: [OSL | CCIE_RS] WB1 - LAB8 -Task 1-2 > > > > This command did not work for me, never has > > Sent from my T-Mobile myTouch 3G Slide > > ----- Reply message ----- > From: "Magnus Påhlsson" <[email protected]> > Date: Thu, Oct 7, 2010 6:46 pm > Subject: [OSL | CCIE_RS] WB1 - LAB8 -Task 1-2 > To: "Adam Booth" <[email protected]> > Cc: "Di Bias, Steve" <[email protected]>, > "[email protected]" <[email protected]> > > R1# clear frame inarp > > Is my personal favorite as long as you're fine with clearing the entire > table. Saves you the hassle of redoing configs. > > > > /M > > On 8 okt 2010, at 03:33, Adam Booth <[email protected]> wrote: > > Hi Steve, > > While that works (rebooting the router to clear the mappings to 0.0.0.0) it > can take much longer than the alternative of: > > 1) shutdown the interface. > 2) Do a show run of the interface and sub-interface configs so we can > reapply it after the next step > 3) Change the encapsulation of the interface to ppp or hdlc - this will > immediately remove all fr mappings associated with that interface. > 4) Reapply the old interface config > 5) no shutdown > > Cheers, > Adam > > , change the encapsulation to something else like ppp or hdlc and then > change it back to frame-relay > > On Fri, Oct 8, 2010 at 9:08 AM, Di Bias, Steve <[email protected]> > wrote: > > I had some free time so I labbed up your scenario using the initial configs > and had the same issue as you. What you will notice in your “show > frame-relay map” command is that you have a bunch of mappings to 0.0.0.0. > The moment you enter “encapsulation frame-relay” on your interface they will > learn the DLCI’s automatically. The only way to clear these out is to reload > your router. Once the router is back up you should have a dynamic mapping to > R2 (150.100.24.2) I just did this and now it looks correct and I can ping :) > > > > R4(config-if)#do sh frame map | i 150.100.24|broad > > Serial0/0 (up): ip 150.100.24.2 dlci 402(0x192,0x6420), dynamic, > > broadcast,, status defined, active > > > > R4(config-if)#do ping 150.100.24.2 > > Type escape sequence to abort. > > Sending 5, 100-byte ICMP Echos to 150.100.24.2, timeout is 2 seconds: > > !!!!! > > Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms > > > > You could also use a static mapping (if you are permitted) > > > > “frame-relay map ip 150.100.24.2 402 broadcast” > > > > It sucks that you had to spend so much time troubleshooting an issue you > thought was with RIP, but had nothing to do with it at all. This is a good > learning process however, just try and remember to test this prior to > starting your lab and definitely before running a routing protocol over it! > In this way you will spend less time troubleshooting the wrong technology > (e.x. RIP instead of Frame Relay). > > > > > > Thank you, > > > > Steve Di Bias > > Network Engineer - Information Systems > > Valley Health System – Las Vegas > > Office - 702- 369-7594 > > Cell - 702-241-1801 > > [email protected] > > > > ________________________________ > > From: Nilesh Mehta [mailto:[email protected]] > Sent: Thursday, October 07, 2010 9:46 AM > To: Di Bias, Steve > Cc: [email protected]; [email protected]; [email protected] > Subject: Re: [OSL | CCIE_RS] WB1 - LAB8 -Task 1-2 > > > > Steve, > > Thanks for your prompt reply. I had a same config for interfaces on R2 and > R4. I did not store output for > > show frame pvc | in ACT > > show frame map > > so I will have to do it again. I am not 100% sure but I remember that that > show frame pvc | in ACTIVE did not show me map for 402 dlci through inverse > arp but still interface shows up/up. > > I will let you know within a day or two . Any other thing do you want me to > try except frame relay map command on R4 ? I believed that its an issue on > R4 only as I was able to ping all loop back from R1 to R9 without any > problem. > > > > Thanks > > Nilesh > > On Thu, Oct 7, 2010 at 9:20 AM, Di Bias, Steve <[email protected]> > wrote: > > Looking at the initial configs for lab 8 I’m seeing the following > > > > R2 > > > > interface Serial0/1/0.24 point-to-point > > description Frame Relay Cloud 2 > > ip address 150.100.24.2 255.255.255.0 > > frame-relay interface-dlci 204 > > > > R4 > > > > interface Serial0/0/0 > > ip address 150.100.24.4 255.255.255.0 > > encapsulation frame-relay > > frame-relay lmi-type cisco > > no shut > > > > So you are correct in that it looks like R4 is using inverse-arp > > > > So please post the output from the commands on R4 > > > > show frame pvc | in ACT > > show frame map > > > > Thanks! > > > > > > From: Di Bias, Steve > Sent: Thursday, October 07, 2010 9:16 AM > To: 'Nilesh Mehta' > > Cc: [email protected]; [email protected]; [email protected] > > Subject: RE: [OSL | CCIE_RS] WB1 - LAB8 -Task 1-2 > > > > On both R2 and R4 run the following commands and post the output > > > > show frame pvc | in ACT > > show frame map > > > > Thanks! > > > > Steve > > > > From: Nilesh Mehta [mailto:[email protected]] > > Sent: Thursday, October 07, 2010 9:12 AM > > To: Di Bias, Steve > Cc: [email protected]; [email protected]; [email protected] > > Subject: Re: [OSL | CCIE_RS] WB1 - LAB8 -Task 1-2 > > > > NO even I am not able to ping. but interface shows up/up status.Looks like > its issue with frame relay interface. By default initial config for lab 8 > does not map frame interface properly and its use inverse ARP by default and > we do not have mapping statement for frame interface. > > On Wed, Oct 6, 2010 at 4:18 PM, Di Bias, Steve <[email protected]> > wrote: > > Can you ping 150.100.24.4 from R2? > > > > > > From: Nilesh Mehta [mailto:[email protected]] > Sent: Wednesday, October 06, 2010 4:13 PM > To: Di Bias, Steve > Cc: [email protected] > Subject: Re: [OSL | CCIE_RS] WB1 - LAB8 -Task 1-2 > > > > All the loopback addresses in routing table except only R4. I can ping to > all loopback from R1to R9 but not routes for 200.0.0.4 > > On Wed, Oct 6, 2010 at 2:46 PM, Di Bias, Steve <[email protected]> > wrote: > > Well you are advertising 200.0.0.0 in RIP so what do you see on R2 when you > issue the following command > > > > “show ip route 200.0.0.4” > > > > Steve > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Nilesh Mehta > Sent: Wednesday, October 06, 2010 1:59 PM > To: [email protected] > Subject: [OSL | CCIE_RS] WB1 - LAB8 -Task 1-2 > > > > > > I was trying to setup neighbor adjacency between R2 and R4. I have same > configuration as per DSG > > but I was not able to connect R4 loop back’s address. R4’s loop back > address never appeared in routing table > > (200.0.0.4).I have both up/up status for serial link on both side and I > tried with no validate source command on R4 and split horizon on R2 but it > did not work. Not sure what could be problem? Any one has this problem > earlier ? Please let me know > > Thanks--Nilesh > > ---------------------------------------------------------- > > R4(config-router)#do sh run | s rip > > router rip > > version 2 > > passive-interface default > > no passive-interface Serial0/0/0 > > network 150.100.0.0 > > network 200.0.0.0 > > no auto-summary > > ----------------------------------- > > > > R2#sh run | s rip > > description Ethernet Link to R1 > > description Frame Relay Links > > description Frame Relay Cloud 2 > > description Frame Relay Cloud 1 > > description Serial Link to R5 > > router rip > > version 2 > > passive-interface default > > no passive-interface GigabitEthernet0/0 > > no passive-interface Serial0/1/0.24 > > no passive-interface Serial0/1/0.256 > > no passive-interface Serial0/2/0 > > network 150.100.0.0 > > network 200.0.0.0 > > no auto-summary > > ------------------------------------------------------------------------------------------------------------ > > -------------------------------------------------- > > R4# > > *Oct 6 05:55:05.535: RIP: ignored v2 update from bad source 150.100.100.5 > on Serial0/0/0 > > R4# > > *Oct 6 05:55:09.179: RIP: ignored v2 update from bad source 150.100.100.6 > on Serial0/0/0 > > R4# > > *Oct 6 05:55:10.587: RIP: sending v2 update to 224.0.0.9 via Serial0/0/0 > (150.100.24.4) > > *Oct 6 05:55:10.587: RIP: build update entries > > *Oct 6 05:55:10.587: 150.100.24.0/24 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:55:10.587: 150.100.40.0/24 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:55:10.587: 150.100.41.0/24 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:55:10.587: 200.0.0.4/32 via 0.0.0.0, metric 1, tag 0 > > R4# > > *Oct 6 05:55:35.139: RIP: ignored v2 update from bad source 150.100.100.5 > on Serial0/0/0 > > R4# > > *Oct 6 05:55:36.967: RIP: sending v2 update to 224.0.0.9 via Serial0/0/0 > (150.100.24.4) > > *Oct 6 05:55:36.967: RIP: build update entries > > *Oct 6 05:55:36.967: 150.100.24.0/24 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:55:36.967: 150.100.40.0/24 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:55:36.967: 150.100.41.0/24 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:55:36.967: 200.0.0.4/32 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:55:37.483: RIP: ignored v2 update from bad source 150.100.100.6 > on Serial0/0/0 > > R4# > > --------------------------------------------------------------------------------------------------------------------- > > R2# > > R2#*Oct 6 05:42:08.283: RIP: sending v2 update to 224.0.0.9 via > Serial0/1/0.24 (150.100.24.2) > > *Oct 6 05:42:08.283: RIP: build update entries > > *Oct 6 05:42:08.283: 66.0.0.0/8 via 0.0.0.0, metric 12, tag 0 > > *Oct 6 05:42:08.283: 66.110.173.0/24 via 0.0.0.0, metric 10, tag 0 > > *Oct 6 05:42:08.283: 66.203.191.0/24 via 0.0.0.0, metric 10, tag 0 > > *Oct 6 05:42:08.283: 100.0.0.0/8 via 0.0.0.0, metric 4, tag 0 > > *Oct 6 05:42:08.283: 100.100.100.0/24 via 0.0.0.0, metric 2, tag 0 > > *Oct 6 05:42:08.283: 150.100.12.0/24 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:42:08.283: 150.100.24.0/24 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:42:08.283: 150.100.25.0/24 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:42:08.283: 150.100.69.0/24 via 0.0.0.0, metric 2, tag 0 > > *Oct 6 05:42:08.283: 150.100.78.0/24 via 0.0.0.0, metric 3, tag 0 > > *Oct 6 05:42:08.283: 150.100.81.0/24 via 0.0.0.0, metric 4, tag 0 > > *Oct 6 05:42:08.283: 150.100.91.0/24 via 0.0.0.0, metric 3, tag 0 > > *Oct 6 05:42:08.283: 150.100.100.0/24 via 0.0.0.0, metric 1, tag 0 > > *Oct 6 05:42:08.283: 150.100.220.0/24 via 0.0.0.0, metric 2, tag 0 > > ------------------------------------------------------------------------------ > > > UHS Confidentiality Notice: This e-mail message, including any attachments, > is for the sole use of the intended recipient(s) and may contain > confidential and privileged information. Any unauthorized review, use, > disclosure or distribution of this information is prohibited, and may be > punishable by law. If this was sent to you in error, please notify the > sender by reply e-mail and destroy all copies of the original message. > > > > > UHS Confidentiality Notice: This e-mail message, including any attachments, > is for the sole use of the intended recipient(s) and may contain > confidential and privileged information. Any unauthorized review, use, > disclosure or distribution of this information is prohibited, and may be > punishable by law. If this was sent to you in error, please notify the > sender by reply e-mail and destroy all copies of the original message. > > > > > UHS Confidentiality Notice: This e-mail message, including any attachments, > is for the sole use of the intended recipient(s) and may contain > confidential and privileged information. Any unauthorized review, use, > disclosure or distribution of this information is prohibited, and may be > punishable by law. If this was sent to you in error, please notify the > sender by reply e-mail and destroy all copies of the original message. > > > > > UHS Confidentiality Notice: This e-mail message, including any attachments, > is for the sole use of the intended recipient(s) and may contain > confidential and privileged information. Any unauthorized review, use, > disclosure or distribution of this information is prohibited, and may be > punishable by law. If this was sent to you in error, please notify the > sender by reply e-mail and destroy all copies of the original message. > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > > UHS Confidentiality Notice: This e-mail message, including any attachments, > is for the sole use of the intended recipient(s) and may contain > confidential and privileged information. Any unauthorized review, use, > disclosure or distribution of this information is prohibited, and may be > punishable by law. If this was sent to you in error, please notify the > sender by reply e-mail and destroy all copies of the original message. > > > UHS Confidentiality Notice: This e-mail message, including any attachments, > is for the sole use of the intended recipient(s) and may contain > confidential and privileged information. Any unauthorized review, use, > disclosure or distribution of this information is prohibited, and may be > punishable by law. If this was sent to you in error, please notify the > sender by reply e-mail and destroy all copies of the original message. > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > -- Favorite Quote: "What you do not know doing will quickly teach you." -- Master Po _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
