I would say they are just there. They don't necessarily "do" anything.
It's just a logical interface. It's there to help you "do" things, not to
do things itself. You'll never list all of the uses for a loopback (in or
out of the classroom). I think the best definition would be a simple one.
Like "An interface that belongs to the router itself and not any
particular network.". Then list the popular uses. Router-id's, nat's,
tunnels, syslog, snmp...
Have fun,
Keegan
From:
"Abraham, Tharak" <tharakabraham_at_gmail.com>
To:
Cisco certification <ccielab_at_groupstudy.com>
Date:
08/04/2009 04:24 PM
Subject:
OT: Loopback usages
Sent by:
nobody_at_groupstudy.com
Hi All,
While giving some short lectures on CCNA, my colleague asked me ..
What are these loopbacks interfaces doing in Routers ?
I tried my best...
Stability for protocol functionality, BGP, OSPF blah blah..but it didnt
make
sense giving those examples..-:)
Avoiding situations when/if physical interfaces go down...but then..
Populating networks ..?
I was not happy..:-(
Is that all folks ?
Best Regards,
Tharak Abraham Luke
Blogs and organic groups at http://www.ccie.net
Received on Tue Aug 04 2009 - 20:56:53 ART
This archive was generated by hypermail 2.2.0 : Tue Sep 01 2009 - 05:43:56 ART