Logical Network Definitions and Subnet-VLAN pairs in Logical Networks

Logical Network Definitions and Subnet-VLAN pairs in Logical Networks

  • Comments 4
  • Likes

Hi, I am Alex Perez Balboa, System Development Engineer on the SCVMM team. Today I am going to provide an overview of some of the new networking concepts in SCVMM 2012 Beta.

Logical Network Definitions

clip_image002

A Logical Network is a way of representing networks in your datacenter that have the same connectivity properties (DMZ, public network, Intranet , management). The Network Admin needs to tell SCVMM what VLAN ID belong to each Logical Network so the hosts can be configured to indicate the networks they are connected to. If you come from SCVMM v2, Logical Networks replace network locations and take it a step further. SCVMM now allows the administrator to give a logical meaning to each of the VLANs existing in their datacenter.

Logical Network Definitions are each of the items that form a Logical Network. Logical Network Definitions scope the Logical Networks to a specific set of host groups. Logical Network Definitions are composed of Subnet-VLAN pairs. This way you can indicate what VLAN belongs to what Logical Network on each host group. When you make a Logical Network Definition available on a host group, all descendant host groups also have access to the Subnet-VLAN pairs defined in the Logical Network Definition.

Why do subnet and VLAN come together in pairs?

The VLAN id is used to know what VLAN to use when connecting a Virtual Machine to the network on the host. This is the physical configuration for a specific virtual network adapter.

The subnet is the IP subnet that is linked to the specified VLAN ID. The subnet is an optional parameter. The subnet is needed by SCVMM to configure static IP addresses during virtual machine creation.

When SCVMM creates a virtual machine and connects it to a specific VLAN ID according to the Logical Network configured on the virtual machine hardware properties , SCVMM knows that the IP to set on the virtual machine should be within the subnet specified.

What different combinations are allowed and when to use them?

· clip_image004

Empty subnet

  • Use this configuration when you want all your virtual machines to be configured using DHCP
  • Only 1 entry per VLAN ID per Logical Network Definition
  • Can be configured on different Logical Networks on the same host group at the same time

Subnet with value

  • Subnets have to be unique within a host group hierarchy across all Logical Networks
  • A subnet can be duplicated as long as the host group branches where they are applied are completely separated

This configuration can be used when you reuse private IP addresses across different locations

  • You can configure different subnets to the same VLAN ID.
  • This enables having IPv4 and IPv6 subnets defined on the same subnet.
  • If you have different subnets sharing the same VLAN ID, although it is not recommended, it is supported

What is VLAN 0?

VLAN 0 means you want VLAN disabled. Use this setting when you don’t care about VLAN IDs.

Normally this means you have your hosts configured on Access mode.

clip_image006

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • It would be nice if the screenshots were linked to a larger version of the picture, rather than the main page for this blog.

  • Nice post. Very simple explanation. Agree with Jim on images.

  • We have SCVMM 2012 SP1 and Orchestrator.

    Our aim is to create VM from template from orchestrator using code and assign IP to guest OS from static pool.

    In this process, we are able to deploy a VM using orchestrator and VM is getting IP from static IP pool, but when installed guest OS using VHD/ISO, guest OS is not getting the IP Address after installation. Guest OS is trying to get IP from DHCP, but not the static IP pool configured in logical network. When we look at hardware properties of VM->Network-> connection Details, Its showing proper IP address. Is this IP really passed to VM using SCVMM ? any other extra steps are needed for this?

    What are the requirements for guest OS to get IP from static pool when deployed from orchestrator.

    Our Setup:

    ----------------

    1. We have Hyper-V servers

    2. SCVMM 2012 SP1

    3. Orchestrator

    4. Created Hard ware profile-> guest profile -> VM Template

    5. Now executed code in SCVMM

    6. VM is getting IP, but not the guest OS installed inside VM.

    We are greatful to you, if you could help us in this regard.

  • We have SCVMM 2012 SP1 and Orchestrator.

    Our aim is to create VM from template from orchestrator using code and assign IP to guest OS from static pool.

    In this process, we are able to deploy a VM using orchestrator and VM is getting IP from static IP pool, but when installed guest OS using VHD/ISO, guest OS is not getting the IP Address after installation. Guest OS is trying to get IP from DHCP, but not the static IP pool configured in logical network. When we look at hardware properties of VM->Network-> connection Details, Its showing proper IP address. Is this IP really passed to VM using SCVMM ? any other extra steps are needed for this?

    What are the requirements for guest OS to get IP from static pool when deployed from orchestrator.

    Our Setup:

    ----------------

    1. We have Hyper-V servers

    2. SCVMM 2012 SP1

    3. Orchestrator

    4. Created Hard ware profile-> guest profile -> VM Template

    5. Now executed code in SCVMM

    6. VM is getting IP, but not the guest OS installed inside VM.

    We are greatful to you, if you could help us in this regard.