What are the two impacts of losing vManage connectivity to fabric in the Cisco SD-WAN network? (Choose two.)
What are the two impacts of losing vManage connectivity to fabric in the Cisco SD-WAN network? (Choose two.)
Losing vManage connectivity to the fabric impacts two main areas. First, policy changes propagation stops, meaning any modifications to policies cannot be pushed or propagated to the network devices. Second, statistics collection stops, resulting in the loss of visibility into network performance and other metrics. These impacts are critical as they affect both the management and monitoring functions within the Cisco SD-WAN network.
Propagation stop? you can't modify it if you dont have vmanage.
AD A. Policy changes propagation stops. -> true / if you change a policy you cannot push it B. Creation of templates is impossible. -> false, you can create on vManage only C. BFD peering between WAN Edge devices are established. ->false D. Statistics collection stops. -> true E. IPsec tunnels tear down for WAN Edge devices. ->false
A. Policy changes propagation stops. is not right because you don't have vManage to modify Policy.
It is important to understand that policies are configured on vSmart or vEdge. vManage is only a graphical user interface used to create and store policies, but once a policy is activated through the vManage GUI, it is configured with a NETCONF transaction either on vSmart or vEdge. https://www.networkacademy.io/ccie-enterprise/sdwan/policies