300-730 · Question #20
On a FlexVPN hub-and-spoke topology where spoke-to-spoke tunnels are not allowed, which command is needed for the hub to be able to terminate FlexVPN tunnels?
The correct answer is D. interface virtual-template. FlexVPN hubs use a virtual-template interface as a blueprint from which dynamic virtual-access interfaces are cloned for each incoming spoke connection.
Question
Options
- Ainterface virtual-access
- Bip nhrp redirect
- Cinterface tunnel
- Dinterface virtual-template
How the community answered
(29 responses)- A3% (1)
- B10% (3)
- C14% (4)
- D72% (21)
Why each option
FlexVPN hubs use a virtual-template interface as a blueprint from which dynamic virtual-access interfaces are cloned for each incoming spoke connection.
Virtual-access interfaces are created automatically by the system from the virtual-template at connection time and are not manually configured by an administrator to enable spoke termination.
'ip nhrp redirect' enables spoke-to-spoke shortcut routing in DMVPN and FlexVPN topologies, which is explicitly not required and not desired in this hub-and-spoke-only design.
A static 'interface tunnel' is used for fixed point-to-point or multipoint GRE tunnels and does not support the dynamic, per-spoke interface instantiation that FlexVPN hub termination requires.
The 'interface virtual-template' command defines a reusable template configuration on the hub that IKEv2 references to dynamically instantiate per-spoke virtual-access interfaces when spokes connect. Without a virtual-template, the hub has no blueprint from which to create these dynamic interfaces and cannot terminate FlexVPN tunnels.
Concept tested: FlexVPN hub virtual-template interface for dynamic spoke termination
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_conn_ike2vpn/configuration/xe-16/sec-conn-ike2vpn-xe-16-book/sec-conn-ike2vpn-flex-hub-spoke.html
Topics
Community Discussion
No community discussion yet for this question.