The stub routing feature in EIGRP can be used to increase the stability of your network and reduce resource usage. It can also be very useful in cases where you have a large number of routers that need to be configured as stubs. Here is an example of how stub routing can be configured. In the case above, we will use the ASBR configuration in EIGRP.
The stub routing command advertises the address 10.1.2.0/24 to Router A. However, 10.1.3.0/24 is also connected to Router A, so the stub command does not advertise this network to Router A. The stub connected command advertises the address 10.1.2.0/13/24 to Router A. This route is advertised to all the routers in the LAN. The stub static command advertises the address 10.1.4.0/24.
Using stub routing limits the QUERY range to a local router and filters out transit routes. The stub does not receive a query message but still sends it to its neighbors. An EIGRP stub router will only advertise summary and connected routes. The stub configuration allows you to configure the local route and manually specify its neighbors. You can also configure a static route and send it to your neighbors, but it will not advertise a redistributed route.
As you can see, stub routing is used to minimize query exchanges in EIGRP. The stub router advertises all static and connected routes to one neighbor. If you are not using this configuration, you should redistribute all the static routes to the other neighbor. The stub router must send out the special peer information to the other neighbors as well.
If you don’t use stub routing, it will only advertise the connected routes to the router. This is a good option if you want to avoid lengthy traffic exchanges with other routers. The stub routing feature helps minimize query exchanges by allowing the router to advertise summary routes to the neighbours. While stub routing may be effective in certain scenarios, it is not recommended to use it for transit routes.
In EIGRP, stub routing is not used for transit routes. It is used to reduce traffic in an area. Unlike stub routing, stub routes are not advertised. The default route is always advertised for each stub router, but there is no need to advertise static routes when they are not used. In this case, stubs should be avoided.
A stub router is a router that advertises a network. The stub router advertises a network if it knows it exists. If it can’t find a route to a specific destination, it will send a query to each router. The neighbours will then forward the query to the next routers in the network. If it receives a response, the stub router will change its route status to Active. This means that it is actively looking for a path and reset the neighbour relationships.
A stub EIGRP router will limit the QUERY range by limiting the number of neighbors. This is the best way to avoid routing loops in large networks. If your network is made up of a lot of routers, stubs will limit the number of routes available to it. This is why stub routers are not considered transit routes in EIGRP.
The stub routers are considered the stub EIGRP routers. They filter the transit paths by sending a QUERY message to all neighbors. These routers do not receive QUERY messages and only send them to their neighbors if they have an alternate path. They also don’t get any QUERY responses if they don’t have an alternate path.
The stub router configuration command allows you to configure a router as an EIGRP stub. This configuration command allows you to share summary routes with all neighbor routers. In addition to the stub, you can use the eigrp stub-only keyword to limit the EIGRP stub. The stub-routers are not allowed to send SIAs.