The EIGRPv6 stub routing
feature, reduces resource utilization by moving routed traffic closer to the
In a network using EIGRPv6
stub routing, the only allowable route for IPv6 traffic to the user is through
a switch that is configured with EIGRPv6 stub routing. The switch sends the
routed traffic to interfaces that are configured as user interfaces or are
connected to other devices.
When using EIGRPv6 stub
routing, you need to configure the distribution and remote routers to use
EIGRPv6 and to configure only the switch as a stub. Only specified routes are
propagated from the switch. The switch responds to all queries for summaries,
connected routes, and routing updates.
Any neighbor that receives a
packet informing it of the stub status does not query the stub router for any
routes, and a router that has a stub peer does not query that peer. The stub
router depends on the distribution router to send the proper updates to all
In the figure given below,
switch B is configured as an EIGRPv6 stub router. Switches A and C are
connected to the rest of the WAN. Switch B advertises connected, static,
redistribution, and summary routes to switch A and C. Switch B does not
advertise any routes learned from switch A (and the reverse).
Figure 2. EIGRP Stub Router
For more information about
EIGRPv6 stub routing, see “Implementing EIGRP for IPv6” section of the
Cisco IOS IP Configuration
Guide, Volume 2 of 3: Routing Protocols, Release 12.4.