Hi,
yesterday I added a LUN to our hyper-v cluster from an fc storage (eva 4100), and added it to our cluster storage.
This needed the newest MPIO Driver and Qlogic Driver from HP, aswell as adding MPIO Role.
Everything works fine, Failover of Storage, Failover of VM's, rebooting, no troubles, tried it several times.
The Cluster check went fine with the storage which I tried before moving over the VM's.
Just our logs turn crazy with those 5 messages reappearing on each cluster node constantly.
I tried to search up some information about this error, but the results are usually cases where failover is not working.
But besides the logs that I don't want to ignore, all seems to work fine.
HYPERV2 2050
Warning Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:58
[ClRtl] SsCoreShareAdd(): status = 2118 share = 5a226444-0bb5-45ef-9579-3594ee536745-135266304$ server = (null)
HYPERV2 2050 Warning Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:58
[ClRtl] SsCoreShareAdd(): status = 2118 share = CSV$ server = (null)
HYPERV2 2051 Error Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
HYPERV2 2050 Warning Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RCM] Failed to load restype 'MSMQ': error 21.
HYPERV2 2050 Warnung Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RCM] Failed to load restype 'MSMQTriggers': error 21.
HYPERV2 2051 Fehler Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'
We also have this hotfix installed (as first we used iscsi and had troubles with backups, that where gone). We had version 1 installed, today I tried version 2, just to be sure it's not related. I doubt it is, but worth to mention. Hotfix: KB2813630 - v2
Thanks
Patrick
yesterday I added a LUN to our hyper-v cluster from an fc storage (eva 4100), and added it to our cluster storage.
This needed the newest MPIO Driver and Qlogic Driver from HP, aswell as adding MPIO Role.
Everything works fine, Failover of Storage, Failover of VM's, rebooting, no troubles, tried it several times.
The Cluster check went fine with the storage which I tried before moving over the VM's.
Just our logs turn crazy with those 5 messages reappearing on each cluster node constantly.
I tried to search up some information about this error, but the results are usually cases where failover is not working.
But besides the logs that I don't want to ignore, all seems to work fine.
HYPERV2 2050
Warning Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:58
[ClRtl] SsCoreShareAdd(): status = 2118 share = 5a226444-0bb5-45ef-9579-3594ee536745-135266304$ server = (null)
HYPERV2 2050 Warning Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:58
[ClRtl] SsCoreShareAdd(): status = 2118 share = CSV$ server = (null)
HYPERV2 2051 Error Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
HYPERV2 2050 Warning Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RCM] Failed to load restype 'MSMQ': error 21.
HYPERV2 2050 Warnung Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RCM] Failed to load restype 'MSMQTriggers': error 21.
HYPERV2 2051 Fehler Microsoft-Windows-FailoverClustering
Microsoft-Windows-FailoverClustering/Diagnostic
19.02.2013 00:04:57
[RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'
We also have this hotfix installed (as first we used iscsi and had troubles with backups, that where gone). We had version 1 installed, today I tried version 2, just to be sure it's not related. I doubt it is, but worth to mention. Hotfix: KB2813630 - v2
Thanks
Patrick