quadrumane
asked on
Hyper-V R2 console network adapter
Hi,
Vmware is a system a more familiar with. But I'm currently testing Hyper-V R2. I have 2 identical servers and a LUN (from a SAN) all iSCSI and host group have been created to support the cluster in order to use Live migration. The volume is already visible on both servers.
Windows 2008 R2 with Hyper-V and the failover cluster have been installed
I have 2 questions:
1 - Microsoft suggests to assign a dedicated network adapter to the console (as we do in Vmware) As the Hyper-V R2 clustered server is not a VM, my understanding is that I have to keep the console network adapter out of the Virtual network because the IP of the Hyper-V R2 server is attached to this NIC. But I may be wrong and please feel free to tell me
2 - I already have assigned a External network adapter for the failover cluster. But is it possible to use un internal adapter (virtual) ?
Vmware is a system a more familiar with. But I'm currently testing Hyper-V R2. I have 2 identical servers and a LUN (from a SAN) all iSCSI and host group have been created to support the cluster in order to use Live migration. The volume is already visible on both servers.
Windows 2008 R2 with Hyper-V and the failover cluster have been installed
I have 2 questions:
1 - Microsoft suggests to assign a dedicated network adapter to the console (as we do in Vmware) As the Hyper-V R2 clustered server is not a VM, my understanding is that I have to keep the console network adapter out of the Virtual network because the IP of the Hyper-V R2 server is attached to this NIC. But I may be wrong and please feel free to tell me
2 - I already have assigned a External network adapter for the failover cluster. But is it possible to use un internal adapter (virtual) ?
plimpias
Doesn't matter what u use, external or internal. But u have to have the same type of adapter with the exact same name on both servers for the migration to work
ASKER
Thanks
You didn't answer the first question but I guess what you,re saying applies to network console port (which is used to provide the IP address on the Windows 2008 R2 Hyper-V server) Does it mean I can add this network adapter inside the virtual network, provided that it's external and it will be used to remote access and console port ?
Regarding the migration, what is the best practice ? The internal is not forbidden as I read the documentation from technet, Dell and anywhere else. But They keep saying to "create virtual network and select external"
You didn't answer the first question but I guess what you,re saying applies to network console port (which is used to provide the IP address on the Windows 2008 R2 Hyper-V server) Does it mean I can add this network adapter inside the virtual network, provided that it's external and it will be used to remote access and console port ?
Regarding the migration, what is the best practice ? The internal is not forbidden as I read the documentation from technet, Dell and anywhere else. But They keep saying to "create virtual network and select external"
You can use the console adapter as a vm adapter also. Not a best practice but yea u can do that. You can add any type of adapter to it
you have to understand internal and external . External allows u to communicate to the hosts outside of the server, like the internet or client computers
internal only allows communication between everything on the host
you have to understand internal and external . External allows u to communicate to the hosts outside of the server, like the internet or client computers
internal only allows communication between everything on the host
More than likely u will use an external adapter. It is rare to use internal
ASKER
Are you talking about both console and cluster ?
I'm aware of the difference between external and internal. As to why your advice is to go with external I guess in the event that something goes wrong with the internal adaptor assigned to the cluster we may find it difficult to get over with it.
I have 8 physical NIC so I can manage to assign external adapters to the console and cluster.
I'm aware of the difference between external and internal. As to why your advice is to go with external I guess in the event that something goes wrong with the internal adaptor assigned to the cluster we may find it difficult to get over with it.
I have 8 physical NIC so I can manage to assign external adapters to the console and cluster.
Maybe I am confusing u
your console network adapter for your server host should be a dedicated physical adapter
your cluster network adapter for your server host should be a dedicated physical adapter
if you wish to use the same physical adapters for yor BMW u can but it is not recommeded. When u create it u can use either internal or external
your console network adapter for your server host should be a dedicated physical adapter
your cluster network adapter for your server host should be a dedicated physical adapter
if you wish to use the same physical adapters for yor BMW u can but it is not recommeded. When u create it u can use either internal or external
ASKER
Ok I will end up with better knowledge on Hyper-V
But I don't know what is BMW (apart a car ;+)
I will assign a dedicated physical adapter to the cluster (External)
Now, there is only one thing I,m not really sure about. In Vmware, the network adapter acting as console is physical but also virtual. This adapter must be virtual (in vmware) because it's listening the heart beat. If this adapter goes down that means the switch is down or the server is down. This is how vsphere will know the VM must be migrated to another host.
So how can the Hyper-V cluster can be aware of a server failure if the console network adapter is not part of the virtual network ?
But I don't know what is BMW (apart a car ;+)
I will assign a dedicated physical adapter to the cluster (External)
Now, there is only one thing I,m not really sure about. In Vmware, the network adapter acting as console is physical but also virtual. This adapter must be virtual (in vmware) because it's listening the heart beat. If this adapter goes down that means the switch is down or the server is down. This is how vsphere will know the VM must be migrated to another host.
So how can the Hyper-V cluster can be aware of a server failure if the console network adapter is not part of the virtual network ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks again now I understand everything. Believe it or not, I'm reading on technet for days and I haven't seen much details regarding what I,m asking. . Vmware has a better documentation.
As a personal comment, I'm not sure I trust the failover cluster as I trust HA or FC in Vmware. I've got a lot of errors with Windows 2008 R2 after I added DAG, although I followed the instructions to the letter.
Do you think the failover cluster is really safe ?
As a personal comment, I'm not sure I trust the failover cluster as I trust HA or FC in Vmware. I've got a lot of errors with Windows 2008 R2 after I added DAG, although I followed the instructions to the letter.
Do you think the failover cluster is really safe ?
ASKER
Hyper-V R2 is easy to manage. But until now I got so many problems because it's windows. All of a sudden a VM is no longer accessible when the SAN goes down (for testing purpose) and then up again.
Besides, I've got a lot of "Hyper-V VM failed to start - General access denied errror"
Of course I'm not used to it. But it looks like ACL, permissions must be carefully taken care of to avoid any mistake. But the documentation don't really specify it.
I don't feel safe with Hyper-V R2. I think Vsphere is more stable. But it's also far more expensive (enterprise version with vmotion, HA, DRS)
Besides, I've got a lot of "Hyper-V VM failed to start - General access denied errror"
Of course I'm not used to it. But it looks like ACL, permissions must be carefully taken care of to avoid any mistake. But the documentation don't really specify it.
I don't feel safe with Hyper-V R2. I think Vsphere is more stable. But it's also far more expensive (enterprise version with vmotion, HA, DRS)