Configuring blueprints for Microsoft Hyper-V switches

BMC Network Automation does not directly support Microsoft Hyper-V, so BMC Cloud Lifecycle Management cannot automatically create networks in the Hyper-V infrastructure. To work around this limitation, you must configure the network manually by:

• Adding a logical switch (using the a ROGUE_DEVICE parameter) in the pod blueprint.  
• Make the pod and network container XML blueprints compatible with Microsoft Hyper-V by editing the <nameWithinSwitch> tag so that it has the same switch name as on the System Center Virtual Machine Manager (VMM).
• Use these blueprints to create pods and network containers in BMC Network Automation.

This topic includes the following sections:

Before you begin

Create a template in BMC Network Automation with the name ConfigFakeHYPERVTemplate. Templates are used for configuring and unconfiguring a max topology container on the pod.

To create a ROGUE_DEVICE in the pod blueprint

1. Open the pod blueprint XML file.
   Click here for a sample file.
2. Scroll to <nodeBlueprints>.

3. Insert the following text:
   
   

   <paramBlueprints>
     <paramBlueprint>
       <description>ROGUE DEVICE ADDRESS</description>
       <name>ROGUE_DEVICE_ADDRESS</name>
       <type>String</type>
     </paramBlueprint>
   </paramBlueprints>
   

4. Save the file.

You can now import the pod blueprint into BMC Network Automation.

To edit the network container blueprint XML

1. Open the Container blueprint XML file.
2. Scroll down to <nodeBlueprints>.

3. Insert the following text to take no action in BMC Network Automation on this node:

   <configureActionInfoBlueprints/>
   <unconfigureActionInfoBlueprints/>

4. Save the file.

To create the pod in BMC Network Automation

Import the pod blueprint into BMC Network Automation as follows:

1. Open BMC Network Automation.
2. Click the Network tab.
3. Click Pod Blueprints under Virtual Data Center.
4. Click Create Pod in the Pod Blueprint.

5. In the Pod wizard, enter the name of the pod, and click Next.

   Note

   Do not select a device for the pod nodes.

6. In the Hypervisor Context field, enter the name of the Microsoft Hyper-V server.

   Note

   Hypervisor Context field was used to specify the name of either the hypervisor cluster (for example, ESX cluster) or hypervisor host (for example, ESX host) which the hypervisor switch controls network traffic for. This information is no longer specified in BMC Network Automation. However, it is specified in BMC Server Automation only.

7. In the ROGUE_DEVICE_ADDRESS field, enter the name of the rogue device by using the following format:
   <SWITCH_NAME><HYPERV_HOST_NAME><SCVMM_NAME>
   For example:
   vSwitch1@pun-hyperv-05@pun-scvmm-15
8. Click Next.
9. Enter any remaining values to create the pod, and click Submit.

Where to go next

Onboarding Microsoft Hyper-V resources