300-415 · Question #210
What is a restriction when configuring a tunnel interface?
The correct answer is B. It is manually assigned when using vManage feature templates. When configuring a tunnel interface using vManage feature templates, the tunnel interface name is a manually assigned value, not automatically generated or fixed.
Question
Exhibit
Options
- AUp to six tunnel interfaces are configurable on a vSmart.
- BIt is manually assigned when using vManage feature templates.
- CIt must be configured for the interface under all VPNs.
- DUp to six tunnel interfaces are configurable on a WAN Edge.
How the community answered
(26 responses)- B88% (23)
- C4% (1)
- D8% (2)
Why each option
When configuring a tunnel interface using vManage feature templates, the tunnel interface name is a manually assigned value, not automatically generated or fixed.
vSmart controllers do not have data plane tunnel interfaces in the same way WAN Edges do; they manage control plane tunnels (DTLS/TLS) to other controllers and WAN Edges.
When using vManage feature templates for configuring a tunnel interface, the interface name (e.g., tunnel0) must be manually specified. This allows administrators to use consistent naming conventions across devices.
Tunnel interfaces are typically configured under vpn 0 (transport VPN) and not under all VPNs, as they are part of the transport infrastructure.
The number of configurable tunnel interfaces on a WAN Edge is typically more than six, depending on the platform and specific configuration needs, so six is not a universal limit.
Concept tested: Tunnel interface configuration in vManage templates
Source: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/sdwan-templates-and-features.html
Topics
Community Discussion
No community discussion yet for this question.