A Cisco ACI environment is configured to integrate with a vCenter environment using the VMM domain name west_coast_VMM. Within the ACI environment, only tenant west_coast has EPGs associated with west_coast_VMM. This deployment is new, so these EPGs currently do not have any members. A systems engineer is setting up vCenter, creates a VDS named west-coast-VMM, and deletes the VDS named west_coast_VMM. The systems engineer creates the necessary port groups that correspond with the EPGs, but when VMs are connected to the port groups, they cannot ping their gateway. Which action establishes connectivity?

Question

Accepted Answer

B. Rename the VDS to west_coast_VMM. Cisco ACI's VMM integration relies on an exact name match between the VMM domain defined in ACI and the Distributed Virtual Switch (VDS) in vCenter. Renaming the VDS in vCenter back to 'west_coast_VMM' will re-establish ACI's control and visibility, allowing it to push configurations and for VMs to gain connectivity.

Answer

A. Associate the EPGs to west-coast-VMM. Associating EPGs to 'west-coast-VMM' would require reconfiguring the ACI VMM domain to match the new VDS name, which is a more involved change than simply correcting the VDS name.

Answer

C. Use the EPG encap-VLAN on the port groups. Manually configuring EPG encap-VLANs on port groups will not resolve the underlying issue of the VMM integration being broken due to the VDS name mismatch, preventing ACI from managing the network policies.

Answer

D. Disconnect Cisco APIC connectivity from vCenter. Disconnecting Cisco APIC connectivity from vCenter would completely disable the VMM integration and prevent ACI from managing any virtual networking components, leading to a loss of connectivity.

A Cisco ACI environment is configured to integrate with a vCenter environment using the VMM domain name west_coast_VMM. Within the ACI environment, only tenant west_coast has EPGs associated with…

Question

Options

How the community answered

Why each option

Topics

Community Discussion