EIGRP STUB

First a heads up - it's a bit complicated because there are just too many details... Subjective impression!

The command is rather straight forward:

Cisqueros_1(config-router)#eigrp stub connected [connected | summary | static | receive-only | redistributed]

When the EIGRP process is configured as STUB on a router using the "stub connected" command:

Cisqueros_1(config-router)#eigrp stub connected

There are a few things that we need to remember:
- That router will no longer see Connected routes, ONLY the Summary (if configured), and also Static and Redistributed routes (because the STUB doesn't affect the Router where it's configured)
- The EIGRP Neighbor(s) will NOT see the Summary, Static or Redistributed Routes, ONLY the specific routes BECAUSE ONLY Connected Routes are advertised

If however we use the "stub summary" command to configure the STUB:

Cisqueros_1(config-router)#eigrp stub stub summary

- The router will keep the same EIGRP routes in the routing table
- The EIGRP Neighbor(s) will ONLY see the Summary

Now with the "stub static" or "stub redistributed":

Cisqueros_1(config-router)#eigrp stub stub [static | redistributed]

This router keeps behaving exactly the same, while the EIGRP Neigbors ONLY receive the Static OR Redistributed routes

With the "stub receive-only":

Cisqueros_1(config-router)#eigrp stub receive-only

This router keeps behaving exactly the same, while the EIGRP Neigbors stop receiving ANY routes from the Router

And finally the "eigrp stub" command can be configured without any attributes, so just:

Cisqueros_1(config-router)#eigrp stub

in which case the EIGRP neighbors ONLY receive the Summary Route