352-001 · Question #303
Which two headend router scalability factors should be considered when designing a DMVPN network solution that uses a hub-and-spoke topology? (Choose two.)
The correct answer is A. the required aggregated packet per second D. the maximum number of tunnels supported by the headend router. When sizing a DMVPN headend router for a hub-and-spoke topology, the two critical platform-level scalability constraints are the maximum supported tunnel count and the aggregated packets-per-second forwarding rate.
Question
Which two headend router scalability factors should be considered when designing a DMVPN network solution that uses a hub-and-spoke topology? (Choose two.)
Options
- Athe required aggregated packet per second
- Bthe amount of bandwidth necessary to terminate all the remote tunnels
- Cthe routing protocol chosen for the data plane routing
- Dthe maximum number of tunnels supported by the headend router
- Ethe CPU and memory of the headend router
How the community answered
(40 responses)- A80% (32)
- B3% (1)
- C13% (5)
- E5% (2)
Why each option
When sizing a DMVPN headend router for a hub-and-spoke topology, the two critical platform-level scalability constraints are the maximum supported tunnel count and the aggregated packets-per-second forwarding rate.
The aggregated packets per second rate is a direct headend scalability limit - the router must encapsulate and decapsulate traffic from all active spoke tunnels simultaneously, and exceeding the platform's PPS ceiling causes packet drops regardless of available bandwidth.
Bandwidth is a WAN circuit sizing concern rather than a headend router hardware scalability factor - it describes the uplink capacity, not the router's ability to process and maintain tunnel state.
The routing protocol affects convergence behavior and design complexity but is not a measurable hardware scalability constraint on the headend router platform itself.
The maximum number of tunnels is a hard platform limit; exceeding the router's NHRP/IPsec tunnel table capacity will prevent additional spokes from registering, making it a primary design constraint when estimating spoke growth.
CPU and memory are underlying resources that contribute to scalability but are not the actionable scalability metrics - PPS capacity and maximum tunnel count are the specific limits derived from those resources and used in design calculations.
Concept tested: DMVPN hub-and-spoke headend router scalability design
Source: https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/WAN_and_MAN/DMVPN_2_Phase2/DMVPN_Phase2.html
Topics
Community Discussion
No community discussion yet for this question.