-
Website
http://www.tech-recipes.com/ -
Original page
http://www.tech-recipes.com/rx/2019/dark_secrets_of_loopback_addresses_cisco/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
davak
83 comments · 1 points
-
Web Design
3 comments · 1 points
-
danishbacker
9 comments · 1 points
-
flexinfo
11 comments · 1 points
-
Tonychelle
4 comments · 1 points
-
-
Popular Threads
-
Symfony: Drop Down List Box Without Submit Button
18 hours ago · 1 comment
-
PowerPoint 2010: How To Convert a Presentation to Video (WMV format)
1 week ago · 1 comment
-
Windows Live Mail: Automatically Spell Check All Email Before Sending
1 week ago · 2 comments
-
Firefox: How to Make Google Reader the Default RSS Reader for Subscribing to Feeds
1 week ago · 1 comment
-
Facebook: How To Get Only Status Updates on Your FB Home Page
1 month ago · 4 comments
-
Symfony: Drop Down List Box Without Submit Button
First, loopbacks don't have much to do with troubleshooting. You can ping one or use it as the source for pings but you can do that with any interface with an IP.
Loopbacks are often used for router management but can also be used to provide virtual interfaces for things like GRE tunnels. The reason you use a loopback is that a physical interface can go down but the loopback, being virtual, is up as long as the router is up.
Regarding OSPF, the term "feasible successor" is from EIGRP, it's not used in OSPF. I think the author was looking for is Router ID. This the IP the router uses to identify itself to other routers running OSPF. The router is determined thusly:
1 Use the address configured by the ospf router-id command
2 Use the address of the loopback 0 interface
3 Use the highest IP address of any interface
4 If no interface exists, set the router-ID to 0.0.0.0