So the first thing that I thought of with named configuration is "Holy Crap. That's a lot of typing." After that I got to see the real power of named mode. It is a great way to see all of your EIGRP configuration in one place without having to look at interfaces for more configuration options.
It is also great so that not only can you configure IPv4 but also IPv6 all in one place. This is done through the use of address-families (think BGP with VRFs or EIGRP traditional mode with VRFs). This again keeps the configuration clean and keeps everything in one place. I like this and may actually start to use this no matter.
So, some more about named mode. Like I said, it used address families to configure EIGRP networks. Autonomous system numbers are assigned to specific families as well. Network commands are placed directly under the address family and this gets a little confusing at first. Network commands are used to identify interfaces to advertise into EIGRP so they help to make up the topology. Now there is a topology section under each address family and no network commands go under there. What goes there are distribute-lists, redistributes, and things that affect the topology of the network. Network commands since they have dual duty don't belong under the topology section.
Also under each address family is where you configure interface information. All the commands that the traditional method uses under and interface are now here. Again, think cleaner. This is done with the af-interface section and there is default for all interfaces or you can specify the exact interface. Under it you have all the typical traditional options and the ability to do passive or not on the interface.
Now, ready for a kicker. Where do you think that summary-addresses are configured? Under af-interface or topology? It is changing some of the topology but it is really configured under the af-interface section and cannot be done under default. It has to be done on the specific interface. Just a little gotcha.
So what is the difference for named versus traditional when it comes to IPv6? Well with IPv6, it all comes under named mode. Nothing is done on the interfaces. Also all interfaces are auto-magically added to EIGRP. This can be stopped by adding shutdown to the af-interface section for that interface or under af-interface default. I can see little things like that being a great trouble ticket on the new R&S test.
Okay. I talked about it but what does it all look like. Below is the configuration that I made from following the video. You will see it looks scary but truly looking at it shows that it ain't so bad.
router eigrp cisco
!
address-family ipv4 unicast autonomous-system 12
!
af-interface default
authentication mode md5
authentication key-chain E12
passive-interface
exit-af-interface
!
af-interface GigabitEthernet0/0
summary-address 2.0.0.0 255.0.0.0
no passive-interface
exit-af-interface
!
af-interface GigabitEthernet1/0
summary-address 2.0.0.0 255.0.0.0
no passive-interface
exit-af-interface
!
af-interface GigabitEthernet2/0
summary-address 2.0.0.0 255.0.0.0
no authentication mode
no passive-interface
exit-af-interface
!
topology base
distribute-list prefix MyFilter in
redistribute connected metric 1 1 1 1 1 route-map Lo0
exit-af-topology
network 10.100.2.0 0.0.0.255
network 192.168.12.0
network 192.168.21.0
network 192.168.102.0
exit-address-family
!
address-family ipv6 unicast autonomous-system 12
!
af-interface default
shutdown
passive-interface
exit-af-interface
!
af-interface GigabitEthernet0/0
no shutdown
no passive-interface
exit-af-interface
!
topology base
redistribute connected metric 10000 10 255 1 1500 route-map Lo0
exit-af-topology
exit-address-family
!
Hope this helps. I know that I feel a lot better about it now.
The video is below as well in case anyone was curious.
No comments:
Post a Comment