Refer to the exhibit. An engineer is troubleshooting an issue where vManage and vSmart have a problem establishing a connection to vBond. Which action fixes the issue?
A.
Remove the encapsulation ipsec command under the tunnel interface of vBond
B.
Reconfigure the vbond command on the vBond as vbond 150.5.1.3 local
C.
Configure the tunnel interface on all three controllers with a color of transport
D.
Configure encapsulation as IPsec under the tunnel interface of vManage and vSmart
The given Answer is correct. People are being confused between setting up controlers and Edge routers. Tunnel Interface TYPE (Encapsulation IPSEC /(color in SCR) must be configured on the WAN edge router. On Vbond, Tunne interface is enabled by default.
Configuring vBond Transport Interface Settings
vBond VPN 0 ge0/0 interface:
The VPN 0 interface is preconfigured for WAN transport (DHCP/IPsec).
The tunnel interface configuration settings lock down the interface and also prevent incoming NETCONF and SCP/SSH connection.
vManage establishes NETCONF and SCP connections with vBond over VPN 0.
Recommendation: disable the tunnel-interface configuration while performing controller integration.
Alternative: temporarily allow the NETCONF and sshd service
Answer: B is correct!
A is WRONG , On page 27 it says you have to specify encapsulation ipsec on the tunnel interface of the vBond (and only for the vBond, neither for the vSmarts nor for the vManage)
https://www.ciscolive.com/c/dam/r/ciscolive/emea/docs/2020/pdf/LTRRST-2734-LG.pdf
D is WRONG Vmanage use DTLS/TLS TUNNELS
in the real vmanage devico no show ipsec
PSEC tunnel is used to send out the data traffic between the vEdges/cEdges and as most of you already knew about the how secure is IPSEC tunnel. The parameters used in IPSEC tunnel is generally are
Authentication and encryption
Rekeying interval
Replay window
Answer: D makes sence
I believe Nean posted the missing piece of the exhibit.
"Tunnel interfaces on vEdge routers must have an IP address, a color, and an encapsulation type:"
The vManage and vSmart configurations are missing the encapsulation type.
D. Configure encapsulation as IPsec under the tunnel interface of vManage and vSmart
https://sdwan-docs.cisco.com/Product_Documentation/Software_Features/SD-WAN_Release_16.2/02System_and_Interfaces/06Configuring_Network_Interfaces
B
without the vBond 150.5.1.3 LOCAL, the vBond would not act as a vBond
"Note: vBond is actually the same image as a vEdge. We convert the personality by initiating the “vBond {ip-address} local” command."
Answer: D
I believe Nean posted the missing piece of the exhibit.
"Tunnel interfaces on vEdge routers must have an IP address, a color, and an encapsulation type:"
The vManage and vSmart configurations are missing the encapsulation type.
D. Configure encapsulation as IPsec under the tunnel interface of vManage and vSmart
https://sdwan-docs.cisco.com/Product_Documentation/Software_Features/SD-WAN_Release_16.2/02System_and_Interfaces/06Configuring_Network_Interfaces
This section is not available anymore. Please use the main Exam Page.300-415 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Nean
Highly Voted 3 years, 2 months agoZeroBits
Highly Voted 3 years, 4 months agothomazmr
Most Recent 9 months agoKnowledge33
9 months, 2 weeks agohamidreza0010
1 year, 4 months ago[Removed]
1 year, 7 months agoeric0430
1 year, 8 months agoMohamedvibes
1 year, 11 months agoatiWok
1 year, 11 months agoEliasmiranda
2 years, 1 month agomadcloud
2 years, 3 months agoRREVECO
2 years, 5 months agoshanntorana
2 years, 6 months agoshanntorana
2 years, 6 months agoA_Wolf
2 years, 9 months ago[Removed]
2 years, 9 months agoJTPRO
2 years, 9 months agoA_Wolf
2 years, 9 months ago