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 ------------------------------------------------------------------------------
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
