The EIGRP stub routing feature does not automatically enable summarization on distribution devices. If a true stub network is desired, the distribution device should be configured to send only a default route to the remote device. The remote device need not receive routes that have been learned from other networks because the remote device must send all nonlocal traffic, regardless of the destination, to the distribution device. Bandwidth and memory can be conserved by summarizing and filtering routes in the distribution device. The large route table would only reduce the amount of memory required by the remote device. Having a complete route table on the remote device would serve no functional purpose because the path to the corporate network and the Internet would always be through the distribution device. In the above example, the remote device can access the corporate network and the Internet only through the distribution device. The stub routing feature by itself does not prevent routes from being advertised to the remote device. The figure below shows a simple hub-and-spoke network. The stub device will depend on the distribution device to send proper updates to all peers. The stub device responds to all queries for summaries, connected routes, redistributed static routes, external routes, and internal routes with the message “inaccessible.” A device that is configured as a stub will send a special peer information packet to all neighboring devices to report its status as a stub device.Īny neighbor that receives a packet informing it of the stub status will not query the stub device for any routes, and a device that has a stub peer will not query that peer. Only specified routes are propagated from the remote (stub) device. When using the EIGRP stub routing feature, you need to configure the distribution and remote devices to use EIGRP and configure only the remote device as a stub. Generally, the distribution device need not send anything more than a default route to the remote device. In a hub-and-spoke topology, the remote device must forward all nonlocal traffic to a distribution device, so it becomes unnecessary for the remote device to have a complete routing table. The distribution device can be connected to many remote devices, which is often the case. This type of configuration is commonly used in WAN topologies, where the distribution device is directly connected to a WAN. The only route for IP traffic to reach the remote device is through a distribution device. The remote device is adjacent to one or more distribution devices. In a hub-and-spoke network, one or more end (stub) networks are connected to a remote device (the spoke) that is connected to one or more distribution devices (the hub). Stub routing is commonly used in hub-and-spoke network topologies. Information About EIGRP Stub Routing EIGRP Stub Routing To access Cisco Feature Navigator, go to An account on is not required. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. Your software release may not support all the features documented in this module.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |