nerdexam
Cisco

300-415 · Question #268

Refer to the exhibit. An engineer is troubleshooting a control connection issue on a WAN Edge that device shows socket errors. The packet capture shows some ICMP packets dropped between the two…

The correct answer is C. Recover the vManage controller that is down in a high availability cluster. The exhibit shows a WAN Edge device attempting to connect to multiple vManage instances, one of which appears to be down based on the duplicated system IP and multiple connection attempts, indicating a vManage HA cluster issue.

Controller Deployment

Question

Refer to the exhibit. An engineer is troubleshooting a control connection issue on a WAN Edge that device shows socket errors. The packet capture shows some ICMP packets dropped between the two devices. Which action resolves the issue? PEER TYPE PEER PROTOCOL PEER SYSTEM IP PEER ID SITE ID DOMAIN ID PEER PRIVATE IP PEER PRIVATE PORT vsmart dtls 10 1.1.8 1 0 1.1.1.1 12447 vmanage dtls 10.1.1.7 1 1 2.2.2.2 12647 vmanage dtls 10.1.1.7 1 1 2.2.2.2 12867 LOCAL COLOR STATE ERROR ERROR UNIT gold up LISFD NOERRR 45 gold up LISFD NOERRR 70 gold up LISFD NOERRR 69

Options

  • ARemove IP duplication in the network and configure a unique IP address.
  • BRecover vBond or wait for the controller to reload, which could be caused by a reset.
  • CRecover the vManage controller that is down in a high availability cluster.
  • DChange the system IP or restart the WAN Edge if the system IP is changed.

How the community answered

(34 responses)
  • A
    3% (1)
  • B
    15% (5)
  • C
    76% (26)
  • D
    6% (2)

Why each option

The exhibit shows a WAN Edge device attempting to connect to multiple vManage instances, one of which appears to be down based on the duplicated system IP and multiple connection attempts, indicating a vManage HA cluster issue.

ARemove IP duplication in the network and configure a unique IP address.

While IP duplication can cause issues, the duplicated entry for vManage with the same system IP but different ports is indicative of a vManage HA setup, not necessarily an accidental IP duplication that needs removing.

BRecover vBond or wait for the controller to reload, which could be caused by a reset.

The exhibit does not directly indicate an issue with vBond, and recovering vBond would not address a problem specific to vManage connections if vBond itself is operational.

CRecover the vManage controller that is down in a high availability cluster.Correct

The exhibit shows two entries for vManage with the same System IP (10.1.1.7) but different private IP addresses (2.2.2.2) and peer ports (12647, 12867), which indicates a vManage high availability (HA) cluster. If the WAN Edge is reporting socket errors and ICMP drops, recovering the downed vManage controller in the HA cluster would resolve the connectivity issues.

DChange the system IP or restart the WAN Edge if the system IP is changed.

Changing the system IP of the WAN Edge or restarting it might temporarily alleviate some issues but would not fix a fundamental problem with a vManage controller in an HA cluster.

Concept tested: Troubleshooting SD-WAN control connections, vManage HA

Source: https://www.cisco.com/c/en/us/td/docs/sdwan/sd-wan-release-20-x/install-and-upgrade/vManage-NMS/vmanage-vbond-vsmart-installation-guide.html

Topics

#SD-WAN Control Plane#vManage High Availability#Troubleshooting#WAN Edge Connectivity

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 300-415 Practice