Well, it took me a while to finish the EIGRP section of INE. With work, travel, and everything else, it took a lot longer for me to finish this section than I really wanted. Well, on to the fun that is EIGRP.
This section really wasn't that bad. I go a lot of it configured without many problems. There were a couple of gotchas. First off was dealing with setting the metric weights. In EIGRP normal mode, we all know that there are 5 k values. With EIGRP, there are 6 k values which I have talked about before. These k values deal with the EIGRP Wide Metrics that I have talked about before. So to use only delay for EIGRP standard mode, you would use the command
metric weight 0 0 0 1 0 0
When doing the same thing in EIGRP Named Mode, the command becomes
metric weight 0 0 0 1 0 0 0
This sixth value covers the extended attributes that are available.
My next gotcha is that I forgot that EIGRP hello and hold timers don't have to match. This is unlike OSPF. EIGRP hold time is also used to tell the neighbors how long to wait for a hello. It is not how long the local router will wait for a hello. The hold time is transmitted in EIGRP packets to the neighbors.
So now that the 15 code is being used, there are slight differences that are being seen. One is the stub command in EIGRP has been replaced with eigrp stub. Woo-hoo!! Something new to remember.
I also came across an interesting little pitfall. The AD for EIGRP internal routes can be changed on a per-prefix basis while external EIGRP routes cannot. This is something that I got from the INE workbook and is something worth remembering as well. That would mean you would use the distance command for EIGRP and set the external AD but it would be for all external routes.
For troubleshooting, INE gives you a little piece of help. When there is a duplicate EIGRP router-id, use either debug eigrp fsm or show ip eigrp events | include Ignored. These two commands will show if there is a duplicate from the point of view of the local router.
Well, EIGRP and RIP are done. Next is OSPF. Hopefully I can knock that out soon.
No comments:
Post a Comment