# DMVPN Phase 2 EIGRP Routing **URL:** https://forum.networklessons.com/t/dmvpn-phase-2-eigrp-routing/1308 **Category:** Lessons Discussion **Created:** [December 29, 2016, 8:25pm UTC](https://forum.networklessons.com/t/dmvpn-phase-2-eigrp-routing/1308 "2016-12-29T20:25:09Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![andrew](https://cdn-forum.networklessons.com/user_avatar/forum.networklessons.com/andrew/32/645_2.png) [@andrew](https://forum.networklessons.com/u/andrew) #### Post date: [May 7, 2016, 2:16pm UTC](https://forum.networklessons.com/t/dmvpn-phase-2-eigrp-routing/1308/3 "2016-05-07T14:16:01Z")
Ahmad, The network will still function, but it will not be optimized. By having traffic go Spoke-Hub-Spoke instead of Spoke-Spoke, you could experience the following: 1. Bandwidth Saturation: With a large number of spokes, the Hub’s bandwidth could become saturated with all the traffic that could be going between the spokes directly 2. Increased delay: Applications that are sensitive to delay (like voice or video) might experience adverse effects because of the extra hops and introduced delay with Spoke-Hub-Spoke traffic 3. Increased dependence on the Hub being available: Even through the Hub will remain a single point of failure for the control plane (meaning the spokes still depend on the hub to learn about spoke to spoke routes), once a spoke establishes spoke to spoke communication, the hub could go down for a short time and not interrupt the traffic between spokes (that have already learned of each other). With Spoke-Hub-Spoke data flow, this means that the Hub is also in the data plane of the traffic, so if the hub has any interruption in service, even for a moment, then spoke to spoke traffic will suffer. --- _[View the full topic](https://forum.networklessons.com/t/dmvpn-phase-2-eigrp-routing/1308)._