Brachus12

Changing IP, Subnet and VLAN on Management vNIC for Hyper-V Cluster

We currently have a 5 node 2016 Hyper-V Cluster using a dual 10GB Team for Management, Cluster and Live Migration virtual adapters. We need to change the IP, subnet and VLAN on the management vNIC for the nodes. The cluster and LM nics are staying the same.

Is the process similar to the answer on this post? https://social.technet.microsoft.com/Forums/en-US/b229869f-b373-40ca-9e2e-bd276aebd12a/change-subnet-mask-for-2012r2-hyperv-cluster?forum=winserverhyperv

It looks like this is an all or nothing change? Once we start, we would need to complete all the hosts and then set the CNO to use the new network? 

Read full post . . . .

How to resolve Event 14260, Hyper-V-VMMS

We have a brand new Server 2019 Hyper-V host that was added into an existing 2016 Cluster. (Yes we are in process of replacing all these hosts with 2019)

When an admin logs onto the new host, it generates these warnings for each VM.

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          5/15/2020 9:12:00 AM
Event ID:      14260
Task Category: None
Level:         Warning
Keywords:      
User:          SYSTEM
Computer:      HyperDW01.DOMAIN.com
Description:
User 'DOMAINXXAdminXX' does not have the permission required to perform the operation on 'DMBIDev'. (Virtual machine ID E3A3F77F-XXXX-474A-XXXX-032E9DB9BE54)
Event Xml:

  
    
    14260
    0
    3
    0
    0
    0x8000000000000000
    
    212
    
    
    Microsoft-Windows-Hyper-V-VMMS-Admin
    HyperDW01.DOMAIN.com
    
  
  
    
      DMBIDev
      E3A3F77F-XXXX-474A-XXXX-032E9DB9BE54
      DOMAINXXAdminXX
    
  

This appears to be the same issue mentioned in the below post from 6 years ago that went unanswered.

https://social.technet.microsoft.com/Forums/en-US/7b2b682d-d93f-4eca-a442-86851f35e691/how-to-resolve-event-14260-hypervvmms?forum=winserverhyperv

Does anyone know how to resolve?

Read full post . . . .

Error Setting VMQ MaxProcessors on LBFO Switch Independent Team

We are attempting to set the VMQ for both NICs on a dual-port Intel X520. They are currently in a LBFO team with Switch Independent and Dynamic set.

However when using Set-NetAdapterVMQ with the ‘MaxProcessors’ property, it gives an error:

Set-NetAdapterVMQ : No matching keyword value found. The following are valid keyword values: 1, 2, 4, 8, 16
At line:1 char:1
+ Set-NetAdapterVMQ -Name "NIC1" -BaseProcessorNumber 2 -MaxProcessors  …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (MSFT_NetAdapter…426E65C8AE98}"):ROOT/StandardCi…rVmqSettingData) [Set-NetAdapterVmq], CimException
    + FullyQualifiedErrorId : Windows System Error 87,Set-NetAdapterVmq

I find several sites using that command with many values without issue. I did find a single post here that states that this error would only appear for those using Switch Dependent on their team.

https://blog.apps.id.au/hyper-v-and-vmqs-mythbusting/

So why are we getting this error for a Switch Independent team? Is it because these NIC ports are on the same single card?

Read full post . . . .

Hyper-V Replication State Stuck on "Waiting for Initial Replication" after Shared Nothing Live Migration – BUG or Real?

We have VMs that are replicating to Azure Site Recovery without issue.

One of those VMs was migrated (from 2012R2 host) over to a new Windows Server 2016 Hyper-V host that had the latest ASR agent installed.

In Hyper-V Manager, Replication shows normal. There are no errors in the Replication Health.

Everything appears normal and good on the Azure side as well.

However, if we run the PowerShell cmdlet Get-VM, it shows the replication state as "Waiting for Initial Replication"

Is this a bug or a real issue?

Read full post . . . .

"Cluster Rolling Upgrade" 2012R2 to 2016 ON NEW HOSTS?

Can the CRU process also be used if instead of reloading existing hosts, a new host with new hardware is instead used?

In the past there was always that CPU compatibility setting that needed to be checked for live migrations, but has that requirement changed now for mixed mode clusters?

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 16 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995