You have a VSM that experiences a failure. Which two options are results of the failure? (Choose two.)
A. CLI access to the virtual switch continues to work without any interruption.
B. VEM stop working.
C. Traffic forwarding stops for a short period of time and then continues to work normally.
D. Traffic forwarding continues to work without any interruption.
E. VMware vMotion stops working.
Answer is D and E
Q. What happens if the VSM is down?
A. While the VSM is down, the VEMs continue to forward traffic using the last known configuration. Any new virtual machines that are started on those VEMs will not have connectivity because the VSM will not be available to set up the port configurations. When the virtual machine is migrated, the virtual Ethernet (vEth) ports will not be configured on the new host because the VSM is not there. However, Cisco plans to address this situation in the future. The NetFlow cache will be maintained in the VEM, and the Switched Port Analyzer (SPAN) will continue to work.
As far as vmotion when the VSMs are down, that is expected. Keep in mind the VSM is the control plane of the N1KV solution and when a VM moves from one ESX host to another it requires changes on the control plane. If the VSM is down the VEMs cannot get the programming they need from the VSM to allow the VM access to the network. We are working a solution to this problem but I couldn’t give you a timeline on when it will be available.
Answer is D and E.
Q. What happens if the VSM is down?
A. While the VSM is down, the VEMs continue to forward traffic using the last known configuration. Any new virtual machines that are started on those VEMs will not have connectivity because the VSM will not be available to set up the port configurations. When the virtual machine is migrated, the virtual Ethernet (vEth) ports will not be configured on the new host because the VSM is not there. However, Cisco plans to address this situation in the future. The NetFlow cache will be maintained in the VEM, and the Switched Port Analyzer (SPAN) will continue to work.
As far as vmotion when the VSMs are down, that is expected. Keep in mind the VSM is the control plane of the N1KV solution and when a VM moves from one ESX host to another it requires changes on the control plane. If the VSM is down the VEMs cannot get the programming they need from the VSM to allow the VM access to the network. We are working a solution to this problem but I couldn’t give you a timeline on when it will be available.
https://www.cisco.com/c/en/us/products/collateral/switches/nexus-1000v-switch-vmware-vsphere/qa_c67-556624.html
https://communities.vmware.com/thread/409782
Answer is D and E.
https://www.cisco.com/c/en/us/products/collateral/switches/nexus-1000v-switch-vmware-vsphere/qa_c67-556624.html
https://communities.vmware.com/thread/409782
As far as vmotion when the VSMs are down, that is expected. Keep in mind the VSM is the control plane of the N1KV solution and when a VM moves from one ESX host to another it requires changes on the control plane. If the VSM is down the VEMs cannot get the programming they need from the VSM to allow the VM access to the network. We are working a solution to this problem but I couldn’t give you a timeline on when it will be available.
Q. What happens if the VSM is down?
A. While the VSM is down, the VEMs continue to forward traffic using the last known configuration. Any new virtual machines that are started on those VEMs will not have connectivity because the VSM will not be available to set up the port configurations. When the virtual machine is migrated, the virtual Ethernet (vEth) ports will not be configured on the new host because the VSM is not there. However, Cisco plans to address this situation in the future. The NetFlow cache will be maintained in the VEM, and the Switched Port Analyzer (SPAN) will continue to work.