This feature is mostly used with the hub and spoke topologies. Routers at the spoke sites are configured as stubs ensuring they the spoke sites don’t act as a transit path for the traffic.
A stub router will inform in EIGRP Hello packets that it has stub feature enabled and hence no queries are sent to stub router for any routes.
Related – EIGRP Packet Types
This is one way to tackle the well-known stuck-in-active issues in EIGRP networks.
Let us use the topology below to configure it’s a feature on Router 2.
In the topology above we have formed EIGRP neighborship between Router 1 & 2 as below:
We have used the following configuration on R2:
Now we will configure EIGRP Stub feature on R2 with following options and check the EIGRP routes on R1 accordingly.
1: CONFIGURING EIGRP STUB CONNECTED
Only connected subnet 188.8.131.52 is advertised to R1.Though 184.108.40.206/24 is also connected network but is not advertised as it isn’t advertised under EIGRP process.
2: CONFIGURING EIGRP STUB STATIC
Only the static route to 220.127.116.11 is seen as advertised to R1.
3: EIGRP STUB RECEIVE-ONLYVerification:
No route is advertised to R1.
4: EIGRP STUB REDISTRIBUTED
Only the redistribute static route is seen to be advertised.
ABOUT THE AUTHOR
I am here to share my knowledge and experience in the field of networking with the goal being – “The more you share, the more you learn.”
I am a biotechnologist by qualification and a Network Enthusiast by interest. I developed interest in networking being in the company of a passionate Network Professional, my husband.
I am a strong believer of the fact that “learning is a constant process of discovering yourself.”
– Rashmi Bhardwaj (Author/Editor)