IPv6 is something that I haven't gotten to play with at work. I have taken a class on it. I have played with it in the lab. I have studied it for tests. Production, though...NOPE!! I do like it. I remember when I first heard about it and someone was saying that it HAD to have IPSec because it was built in. Well, it is, but thankfully, it is not required. Could you imagine the implementation mess that would make.
When using autoconfiguration on an interface, add the default keyword to have the router add a default gateway to the router it is learning its prefix from. Also since routing is enabled essentially on the autoconfiguration-passing router, may be a good idea to turn on ipv6 unicast-routing. Apparently Ethernet interfaces by default have router advertisements turned off. If you are wanting to do some autoconfiguration, you may want to use the command no ipv6 nd suppress-ra but you definitely need to turn on unicast routing for it to work.
In IPv4, you could disable the split horizon per interface for RIP. For IPv6, it is done on the process level. That means you are turning off split horizon on all interfaces that that RIP process is configured on. That seems like a bad idea because what if you don't want it off on all interfaces. Also the EIGRPv6 split horizon is still per interface.
So with IPv6 EIGRP, there apparently isn't a leak map. Interesting. Fun trying to let some prefixes out and hide others then when doing a summary. Think about when doing that for a default route injection but still want to show some routes. Have to redistribute the route and use distribute-lists for the other routes to advertise.
So even though the command reference doesn't mention it, you can still use in and out keywords when doing a distribute-list prefix-list in IPv6 EIGRP. Messed me up since it wasn't shown.
Just read that right now, IPv6 EIGRP can only do equal-cost load balancing. That may be something to look at. Apparently you can tell EIGRPv6 to find paths with unequal metrics but it will say screw you and only balance across them equally.
Two things about summarizing routes in OSPF between areas. One, and this doesn't matter where the summarization is, remember to change the OSPF network type for loopbacks otherwise they come in as /128 or /32 depending on the protocol. Next, the area range command still throws me. It is saying pull from this area anything that matches this range. I don't know why I can't get that. Getting frustrating.
And here I was looking for how to turn on PIM on interfaces. Crap. When you enable multicast routing for IPv6 on a router, it does so for ALL interfaces. You have turn it off on the interfaces you don't want with no ipv6 pim. Also replace ip igmp with ipv6 mld and you just about got it all. Other interesting note is that the documentation for PIM is broken on Cisco's website for the 15 code. I am having to use the 12.4T documentation for PIM.
IPv6 tunnelling has been moved to the Interface and Hardware Component configuration guide. Well, ain't that something. Figured it would have been kept in the IPv6 guide but that was too easy I guess.
So according to what I read, you have to do static routing with Automatic 6to4 Tunnelling. Since 6to4 is a multipoint technology, dynamic routing seems to be an issue. INE says that the common thing is to do a static for the full 2002::/16 network pointing to the created tunnel. Also since ISATAP tunnels cannot extract the destination automatically, static routes have to be used there as well.
No comments:
Post a Comment