DISQUS

Since you're already in the terminal just add "killall finder" after the show or hide commands. Finder will go away and then restart.

The last command in this example is incorrect as it doesn't use the access-list that's been defined. The last example should be:


access-list 100 permit ip any host 1.1.1.1
access-list 100 permit ip host 1.1.1.1 any

debug ip packet detail 100



Note the 100 at the end of the debug line. That applies ACL 100 to the debug. Without that you risk choking the router if it's at all busy.

I don't know quite where to start with this but if you're looking for info I'd suggest looking elsewhere.

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

Alternately you could configure a DNS server with the command: ip name-server <ip address>


Now if you type "confligure" you'll get something like
Translating "confligure"...domain server (1.1.1.1)
% Unknown command or computer name, or unable to find computer address
within a few seconds as the domain server reports that the name doesn't look up.

"show mac-address-table 0000.0000.0000" is too much typing for me, especially as I'm frequently called on to find which interface a server or user is connected to. Because I'm lazy in an efficient kind of way I add the "shmac" alias to all my switches.

In config mode enter alias exec shmac SH MAC-address-table | include

Now when you want to find a server that's got a mac address of 0102.0304.0506 you can just type shmac 0506
and nine times out of ten you'll get the entry you're looking for. You may get multiple entries if you've got two devices with MACs ending in 0506 so you could type the whole MAC address, but I did mention that I'm "efficient" so I rarely do.

I'd also like to note that while the author's network may always use gig interface for switch connections it's perfectly possible for a user to be connected to one so that's not actually a guarantee that's it's an interswitch link. Figuring that out requires that you know your network; which means that I can't think of a simple to explain way to figure out where the port shown leads to another switch.