Microsoft SCVMM Integration
Figure 6-7 shows a representative topology for a Microsoft SCVMM integration with Cisco ACI. Hyper-V clustering connectivity between SCVMM virtual machines and the APIC can run over the management network.
Figure 6-8 illustrates the workflow for integrating Microsoft SCVMM with Cisco ACI. The following sections describe the steps in this workflow.
Mapping ACI and SCVMM Constructs
Figure 6-9 shows the mapping of Cisco ACI and the SCVMM constructs (SCVMM controller, cloud, and logical switches).
One VMM domain cannot map to the same SCVMM more than once. An APIC can be associated with up to five SCVMM controllers. For additional information on other limitations, see the Verified Scalability Guide for Cisco ACI on the Cisco website.
Mapping Multiple SCVMMs to an APIC
When multiple SCVMMs are associated with an APIC, the OpFlex certificate from the first SCVMM controller must be copied to the secondary controller and other controllers, as applicable. You use the certlm.msc command on the local SCVMM controller to import the certificate to the following location:
Certificates - Local Computer > Personal > Certificates
The same OpFlex certificate is deployed on the Hyper-V servers that are managed by this SCVMM controller. You use the mmc command to install the certificate on the Hyper-V servers.
Verifying That the OpFlex Certificate Is Deployed for a Connection from the SCVMM to the APIC
You can verify that the OpFlex certificate is deployed for a connection from the SCVMM to the APIC by viewing the Cisco_APIC_SCVMM_Service log file, which is located in the C:\Program Files (x86)\ApicVMMService\Logs\ directory. In this file, ensure that the correct certificate is used and also check to make sure there was a successful login to the APIC (see Example 6-1).
Example 6-1 Viewing the Cisco_APIC_SCVMM_Service Log File
Verifying VMM Deployment from the APIC to the SCVMM
You can verify that the OpFlex certificate is deployed on the Hyper-V server by viewing log files in the C:\Program Files (x86)\ApicHyperAgent\Logs directory. In this file, ensure that the correct certificate is used and ensure that the connection with the Hyper-V servers on the fabric leafs is established. In addition, ensure that a VTEP virtual network adapter is added to the virtual switch and an IP address is assigned to the VTEP adapter.
In the SCVMM, check for the following:
▪ Under Fabric > Logical Switches, verify that apicVswitch_VMMdomainName is deployed from the APIC to the SCVMM.
▪ Under Fabric > Logical Networks, verify that apicLogicalNetwork_VMMdomainName is deployed from the APIC to the SCVMM.
▪ Under Fabric > Port Profiles, verify that apicUplinkPortProfile_VMMdomainName is deployed. If it is not deployed, right-click the host under Servers and choose Properties. Go to Virtual Switches and ensure that the physical adapters are attached to the virtual switches.