EIGRP for IPv6

EIGRP for IPv6

Like OSPFv3 compared to OSPFv2, EIGRP for IPv6 has a abundant accord in accepted with EIGRP for

IPv4. In fact, EIGRP for IPv6 is actual agnate to EIGRP for IPv4. Of course, some differences exist,

so this area covers the key differences afore affective on to configuration.

Differences Amid EIGRP for IPv4 and for IPv6

IPv6 EIGRP requires a acquisition activity to be authentic and enabled (no shutdown) and a router ID

(in 32-bit IPv4 abode format) to be manually assigned application the router-id command, both of

which charge be done in IPv6 router agreement approach afore the IPv6 EIGRP acquisition activity can

start. These are two of the differences amid EIGRP for IPv4 and IPv6. Some others board the

following:

■ Configured on the interface—As with OSPFv3 (and RIPng), EIGRP advertises networks

based on interface commands rather than acquisition activity arrangement commands. For example,

the command to accredit IPv6 EIGRP AS 100 on an interface is ipv6 eigrp 100.

■ Charge no shut the acquisition process—When EIGRP for IPv6 is aboriginal configured on an interface,

this activity creates the IPv6 EIGRP acquisition activity on the router. However, the acquisition process

is initially placed in the abeyance state, and requires a no abeyance command in router

configuration approach to become active.

■ Router ID—EIGRP for IPv6 requires a 32-bit router ID (a dotted-decimal IPv4 address) to

be configured afore it starts. A router does not accuse about the abridgement of an EIGRP RID,

however, so bethink to configure one statically back accomplishing a no abeyance in the routing

process.

■ Acquiescent interfaces—IPv6 EIGRP, acquiescent interfaces are configured in the acquisition process

only. That is, no accompanying agreement commands are appropriate on the interface.

■ Avenue filtering—IPv6 EIGRP performs avenue clarification application alone the distribute-list prefixlist

command. IPv6 EIGRP does not abutment avenue clarification through avenue maps that call

distribute lists.

■ Automatic summarization—IPv6 EIGRP has no agnate to the IPv4 (no) auto-summary

command, because there is no abstraction of classful acquisition in IPv6.

■ Cisco IOS support—EIGRP for IPv6 is accurate in Cisco IOS alpha with

Release 12.4(6)T.

Unchanged Features

All of the afterward EIGRP appearance assignment the aforementioned way in IPv6 as they do in IPv4. The only

exceptions are the commands themselves, with ipv6 instead of ip in interface commands:

■ Metric weights

■ Authentication

■ Link bandwidth percentage

■ Split horizon

■ Next-hop setting, configured via the interface-level ipv6 next-hop-self eigrp as command

■ Hello breach and holdtime configuration

■ Abode summarization (syntax differs hardly to board IPv6 abode format)

■ Stub networks (syntax and options alter slightly)

■ Variance

■ Most added features

IPv6 EIGRP uses affidavit keys configured absolutely as they are for IPv4 EIGRP.