Hey Michael, that is a pretty good way to do it. Thank you,
Marc On Thu, Aug 25, 2011 at 4:17 PM, Michael Smith <[email protected]> wrote: > Hello Marc, > > You should be able to ping with the source being your loopback if you are > advertising any routes to the backbone. What I like to do is advertise my > loopback to the backbone attempt to ping it with a source of that loopback > and then remove it from the routing process. > >> Date: Thu, 25 Aug 2011 14:06:44 -0500 >> From: [email protected] >> To: [email protected] >> Subject: [OSL | CCIE_RS] How to verify RIP >> >> In a case where you need to establish a RIP adjacency with a back bone >> router, and you aren't sure if you should be receiving any extra >> routes. How can you verify RIP? If you are only advertising your >> common network, neither of you would be sending updates so debug ip >> rip data or debug ip rip events doesn't seem to help right? >> >> All I see is: >> >> Aug 25 19:02:18.894: RIP: sending v2 update to 224.0.0.9 via >> FastEthernet0/1.200 (20.20.20.9) >> Aug 25 19:02:18.894: RIP: build update entries - suppressing null upd >> >> -Marc >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com >> >> Are you a CCNP or CCIE and looking for a job? Check out >> www.PlatinumPlacement.com > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
