This is another thing that has been happening in our environment. the event logs reports from source = Clussvc; Category= Node Mgr and shows a message: "Cluster node D01EXCHANGE03 selected multicast address 239.255.73.71 for network Private after failing to contact a MADCAP server." Does anyone know why this happens? Is it a big deal? - the event log shows this as Informational so I'm assuming this is normal? I would assume that we would want to fix the problem if it "fails" to contact the MADCAP server. Does anyone know how to fix? I've researched this for some time and can't find anything that is helping.
this is resolved..... "BHarley99" wrote in message news:epLsxLjGIHA.700@TK2MSFTNGP05.phx.gbl... This is another thing that has been happening in our environment. the event logs reports from source = Clussvc; Category= Node Mgr and shows a message: "Cluster node D01EXCHANGE03 selected multicast address 239.255.73.71 for network Private after failing to contact a MADCAP server." Does anyone know why this happens? Is it a big deal? - the event log shows this as Informational so I'm assuming this is normal? I would assume that we would want to fix the problem if it "fails" to contact the MADCAP server. Does anyone know how to fix? I've researched this for some time and can't find anything that is helping.
I am very interested in what you did in the end. This is a gapping hole for Microsoft Clusters, no best practices what so ever, confusing statements and lack of any real documentation. Cheers, Rodney R. Fournier MVP - Windows Server - Clustering http://www.nw-america.com - Clustering Website http://msmvps.com/clustering - Blog http://www.clusterhelp.com - Cluster Training ClusterHelp.com is a Microsoft Certified Gold Partner "BHarley99" wrote in message news:%23PlXaMxGIHA.1548@TK2MSFTNGP05.phx.gbl... this is resolved..... "BHarley99" wrote in message news:epLsxLjGIHA.700@TK2MSFTNGP05.phx.gbl... This is another thing that has been happening in our environment. the event logs reports from source = Clussvc; Category= Node Mgr and shows a message: "Cluster node D01EXCHANGE03 selected multicast address 239.255.73.71 for network Private after failing to contact a MADCAP server." Does anyone know why this happens? Is it a big deal? - the event log shows this as Informational so I'm assuming this is normal? I would assume that we would want to fix the problem if it "fails" to contact the MADCAP server. Does anyone know how to fix? I've researched this for some time and can't find anything that is helping.
I created a MultiCast DHCP scope with 5 available addresses. I only have 3 servers that are a member of the cluster. Once the system attempted to contact the MADCAP server it found it - because it is just apparently DHCP for Multicast IP addresses. 224.1.1.1 thru 224.1.1.5 is the range I setup. I set this up right along side our existing DHCP scope. Now the event log reports it successfully found the MADCAP server and you can see which address it obtained and they appear to be talking to each other better. "Rodney R. Fournier [MVP]" wrote in message news:exVZbYxGIHA.4684@TK2MSFTNGP06.phx.gbl... I am very interested in what you did in the end. This is a gapping hole for Microsoft Clusters, no best practices what so ever, confusing statements and lack of any real documentation. Cheers, Rodney R. Fournier MVP - Windows Server - Clustering http://www.nw-america.com - Clustering Website http://msmvps.com/clustering - Blog http://www.clusterhelp.com - Cluster Training ClusterHelp.com is a Microsoft Certified Gold Partner "BHarley99" wrote in message news:%23PlXaMxGIHA.1548@TK2MSFTNGP05.phx.gbl... this is resolved..... "BHarley99" wrote in message news:epLsxLjGIHA.700@TK2MSFTNGP05.phx.gbl... This is another thing that has been happening in our environment. the event logs reports from source = Clussvc; Category= Node Mgr and shows a message: "Cluster node D01EXCHANGE03 selected multicast address 239.255.73.71 for network Private after failing to contact a MADCAP server." Does anyone know why this happens? Is it a big deal? - the event log shows this as Informational so I'm assuming this is normal? I would assume that we would want to fix the problem if it "fails" to contact the MADCAP server. Does anyone know how to fix? I've researched this for some time and can't find anything that is helping.
So you are using MADCAP, got it. Thanks for data point! Cheers, Rodney R. Fournier MVP - Windows Server - Clustering http://www.nw-america.com - Clustering Website http://msmvps.com/clustering - Blog http://www.clusterhelp.com - Cluster Training ClusterHelp.com is a Microsoft Certified Gold Partner "BHarley99" wrote in message news:OVBtRwWHIHA.4712@TK2MSFTNGP04.phx.gbl... I created a MultiCast DHCP scope with 5 available addresses. I only have 3 servers that are a member of the cluster. Once the system attempted to contact the MADCAP server it found it - because it is just apparently DHCP for Multicast IP addresses. 224.1.1.1 thru 224.1.1.5 is the range I setup. I set this up right along side our existing DHCP scope. Now the event log reports it successfully found the MADCAP server and you can see which address it obtained and they appear to be talking to each other better. "Rodney R. Fournier [MVP]" wrote in message news:exVZbYxGIHA.4684@TK2MSFTNGP06.phx.gbl... I am very interested in what you did in the end. This is a gapping hole for Microsoft Clusters, no best practices what so ever, confusing statements and lack of any real documentation. Cheers, Rodney R. Fournier MVP - Windows Server - Clustering http://www.nw-america.com - Clustering Website http://msmvps.com/clustering - Blog http://www.clusterhelp.com - Cluster Training ClusterHelp.com is a Microsoft Certified Gold Partner "BHarley99" wrote in message news:%23PlXaMxGIHA.1548@TK2MSFTNGP05.phx.gbl... this is resolved..... "BHarley99" wrote in message news:epLsxLjGIHA.700@TK2MSFTNGP05.phx.gbl... This is another thing that has been happening in our environment. the event logs reports from source = Clussvc; Category= Node Mgr and shows a message: "Cluster node D01EXCHANGE03 selected multicast address 239.255.73.71 for network Private after failing to contact a MADCAP server." Does anyone know why this happens? Is it a big deal? - the event log shows this as Informational so I'm assuming this is normal? I would assume that we would want to fix the problem if it "fails" to contact the MADCAP server. Does anyone know how to fix? I've researched this for some time and can't find anything that is helping.
