Masuk
 
AwalPerpustakaanWikiPelajariUnduhDukunganKomunitasForum
Resources for IT Professionals >
> 
> 
Upgraded SCVMM logical network disconnects all VM's in cluster

问题 Upgraded SCVMM logical network disconnects all VM's in cluster

  • 22 Mei 2012 16:28
     
     
    Masuk untuk Memilih
    0

    Didnt expect this !!!!

    I upgraded SCVMM to 2012 pretty painless.. and things look great...  Then I noticed all the hosts are showing non compliant with respect to their  related network fabric.

    So I read up and understand how logical networks are setup  ..  We have a four node cluster with about 50 VM's in it..  We use LinkAg on the hosts and Trunk mode .1q tagging.  We dont have any sites or use dynamic IP allocation etc....

    So I create a logical network and assign the appropriate VLAN tags. I then associate the logical network to the cluster and virtual network.  Boom !   All VM's are disconnected from the network. The even worse thing is that even after undoing the logical network they are still disconnected.  I had to migrate them from one host to another before they reestablished connectivity.

    Anyone have any advice on what I did wrong ?  Or what the appropriate steps are to bring an existing cluster with running VM's into a logical network ?

    Steve Lithgow


     

Semua Balasan

  • 22 Mei 2012 17:00
     
     
    Masuk untuk Memilih
    0

    Hello Steve,

    Can you check for the following link?

    http://social.technet.microsoft.com/wiki/contents/articles/create-networks-with-vmm-2012.aspx

    It gives detailed information.

    If you have any concerns, do not hesitate to contact.

    Sincerely,

    Murat Demirkiran

    If the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. www.scvmm2012.com (TR Language) Please note that I'm not a Microsoft Representative or SpokesPerson.

     
  • 22 Mei 2012 17:58
     
     
    Masuk untuk Memilih
    0

    Yep read it already... I  understand how to create the logical network.. and my guess is that it works great when provisoning a cluster from scratch.... 

    What it doesnt address is how to create a logical network in an existing cluster without having all the VM's disconnected from the network when the virtual network and physical adapter are assigned to the logical network. As this makes it impossible to change the entire cluster at once..

    OR

    How to get the cluster configuration synched host by host so that VMM sees it as a compliant configuration..  I also failed to mention (intentionally so as not to confuse the matter) that once the logical network was assigned any migrations came up with an error that the cluster configuration was not supported...

    Steve Lithgow



     
  • 26 Mei 2012 17:44
    Moderator
     
     
    Masuk untuk Memilih
    0

    Check the settings workspace in VMM on how VMM should detect/create logical/virtual networks. Basically it`s default set to DNS suffix, so a good tip would be to name/tag your NICs on your hosts properly, so that they are similar on every node in your cluster.

    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

     
  • 27 Mei 2012 21:23
     
     
    Masuk untuk Memilih
    0

    Can you post more detail about the Logical network you have created ?

    basically you need to create three logical networks:

    1. Private Heartbeat network Range

    2. Public and VIP network rage

    3. VM IP address network range (if VMs have different range than Public)

    Hikmat Kanaan Amman-Jordan MCSE

     
  • 29 Mei 2012 14:19
     
     
    Masuk untuk Memilih
    0

    Thanks for the replies,

    Kristian I am not sure what you refer to as "Name/tag" all my Nics on the hosts are named identically across the cluster.  Also can you be more specific where this setting is?  I'm not sure what the "workspace" is?

    Hikmat,

    Ok..  we dont use DHCP in our server vlan this server was upgraded from SCVMM 08 R2 and is not a build from scratch cluster either..

    Bascially the cluster looks like this:

    2 NICs Teamed via Link Ag  Trunk Mode for VM LAN access not Shared only for virtual network (no IP bound) VM's use VLANs
    2 NICs guest iSCSI  (non shared as well )
    2 NICs host iSCSI (for  CSV)
    1 NIC Live Migration (private)
    1 NIC Management Interface (public but not shared to VM's)

    So I created a logical network for the VM access to trunked..  I Created a Site and added the host group where the cluster lives.  I setup vlans for all the VLAN the VM's access.  I did not setup IP subnet (no DHCP or pools).

    As soon as I assign a host to the Logical network ..  All VM's lose connectivity.

    I'm assuming creating a Logical network for Live migration/cluster communication  will be used for host management ? (i.e. add new host to cluster)

    I'm not clear as to what Public /VIP network range is ?

    VM IP's are all over the place since we have many VLANs the VM's might ... I understood the documentation to say if you dont use pooling (IP's ) you dont need to configure the network range in the site config?

    Steve Lithgow

     
  • 30 Mei 2012 5:39
     
     
    Masuk untuk Memilih
    0

    Hi, Steve

    Adding IP range to site is Just a good way to understand your network and have more control , I would suggest to you to add the IP range even if you are not using Pools or DHCP.

    This is how I would setup logical network for your configuration:

    Create 5 Logical network :

            1.Trunk_Netwrok with defined VLAN number/IP Range (select Available for Placement)

               VLAN10 - 172.20.20.0/24

               VLAN11 - 172.20.10.0/24

               VLAN15 - 172.20.30.0/24

            2. VM_Iscsi (clear Available for Placement, Used By Management)

                 VLAN 0 - 10.10.10.0/24

            3. Host_Iscsi  (clear Available for Placement, Used By Management)
                VLAN 0 - 192.168.100.0/24

            4. HOST_Private  (clear Available for Placement, Used By Management)

                  VALN 0 -192.168.1.0/24

            5.HOSt_Managment (Select Used By Management)

                  VLAN 0 - 212.10.12.0/24

    in the Hardware TAB of host properties assign each Logical network to the corresponding network interface

    Hikmat Kanaan Amman-Jordan MCSE

     
  • 30 Mei 2012 17:04
     
     
    Masuk untuk Memilih
    0

    Ok.. Thanks Hikmat !

    I understand what you are describing above.. although it almost now seems to make more sense to have a logical network for each VLAN  otherwise I would need to set the specific vlan for each VM at its hyper-v configuration ?

    Also,

    I am ok with including the IP range for identification purposes.. I'm just not using pooling of MAC or static IP's ;)

    Finally,

    I pretty much did exactly this ,  Created a logical network called  Trunked and added all the VLANs the VM's might connect to..  and assigned a host to this Logical Network..    once again all VM's became disconnected.  :(

    So my question is do I have to reconfigure each VM hardware ......config or something ?

    Steve Lithgow

     
  • 30 Mei 2012 18:29
     
     
    Masuk untuk Memilih
    1

    I'm Not sure that I understand your configuration but here is what I have in my network

    I have host that has two adapters:

    1. Trunk Port --> carry Multiple VLAN 10,20,30,40,50

    2. Management interface  - no VLANs access port ( us an ip address from VLAN 40 range )

    I have created 1 logical network let call it "JDC_EXternal_Trunk_virtual_netwrok" with one site  , where I defined all my VLANS with IP ranges

    in the hardware tab of my Host :

    Adapter 1 assigned to logical network ""JDC_EXternal_Trunk_virtual_netwrok"" ( select Available for Placement)

    Adapter 2 assigned to logical network  ""JDC_EXternal_Trunk_virtual_netwrok"" (clear Available for Placement, Used By Management)--> click Advanced --> remove all click remove until only 1 VLAN 40 is in the list the Port will convert to Access mode.

    in VM properties Vm is assigned to logical network with VLAN number 

     

    I hope this will help you

    Hikmat Kanaan Amman-Jordan MCSE

     
  • 04 Juni 2012 21:29
     
     
    Masuk untuk Memilih
    0

    Thanks Hikmat,

    I get the concept of configuring the logical networks...   My concern here is at what point will my VM's regain connectivity and will I  need to reconfigure all the vm properties to utilize the logical network as well...  As I stated above.. I attempted just this (as you have outlined) and the VM's became disconnected from the network..   I did not finish configuring all the nodes in teh cluster as this is  a production environment and the loss of VM connectivity  was not expected. 

    Also.. at what point do I add the logical network association to the Cluster properties ?..  (i.e.  cluster properties, virtual networks)???

    Steve Lithgow

     
  • 05 Juni 2012 9:15
     
     
    Masuk untuk Memilih
    0

    Hi, Steve

    what I think you need to do is :

    Create your Logical network , and add all VLANs and IP ranges to this Logical network lets Call it (Production_network)

    when you add a new Host to VMM , VMM create new logical network with the same name as your host external network let call it (host_external_Network).

    Now:

    select the Properties of the  Host :

    1.click the check box for (production_network ) so your host would have two logical networks assigned to it

    2. assign each Host adapter to it's correct subnets as per my previous post trunk port or access port  for (production_network )

    3. Visit all your Vm's on the host , in the Hardware properties select VM network adapter  , in connected to select your logical network  (production_netwrok ) and check VLan Assignment

    once all VM's are assigned , visit the Host properties and remove the check box from the old logical network  (host_external_Network) , after that you can delete the (host_external_Network) from the Fabric .

    Tip:

    What I do and makers my life easier , is that I use the Same name for my logical network and Hyper-v virtual network . then VMM would understand and Vlans assignment and I don't need to visit each VM properties

    Hikmat Kanaan Amman-Jordan MCSE