The Test-ReplicationHealth cmdlet in Exchange 2007 will show an inaccurate warning for the ClusterNetwork check if your CCR nodes are configured in geographically dispersed clusters.
Exchange 2007 CCR clusters must be located on the same subnet(s) when deployed on Windows 2003 servers. Clustering enhancements in Windows Server 2008 enable you to create clusters in different subnets, negating the need to do networking acrobatics like stretching VLANs across geographic sites. Unfortunately, the Test-ReplicationHealth cmdlet still expects that the network adapters are on the same network and will display the following warning if they are not:
Server Check Result ErrorThis behavior also affects System Center Operations Manager 2007, since SCOM uses the same Test-ReplicationHealth cmdlet to monitor Exchange 2007 replication health. This will cause the CCR nodes to show in a critical condition for the Exchange 2007 Test Replication Health Monitor - Log Shipping monitor.
------ ----- ------ -----
EXNODE1 PassiveNodeUp Passed
EXNODE1 ClusterNetwork WARNING Warnings:
Network 'EXNODE2 Public' used for client connectivity is up but node 'EXNODE1' does not have a Network Interface Card configured on it. Check that a NIC is configured for this network and is enabled.
Network 'EXNODE2 Private' used for internal cluster communications is up; however, node 'EXNODE1' does not appear to have a configured network interface card (NIC). Check that a NIC is configured and enabled for this network on this node.
Network 'EXNODE1 Private' used for internal cluster communications is up; however, node 'EXNODE2' does not appear to have a configured network interface card (NIC). Check that a NIC is configured and enabled for this network on this node.
Network 'EXNODE1 Public' used for client connectivity is up but node 'EXNODE2' does not have a Network Interface Card configured on it. Check that a NIC is configured for this network and is enabled.
EXNODE1 QuorumGroup Passed
EXNODE1 FileShareQuorum Passed
EXNODE1 CmsGroup Passed
EXNODE1 NodePaused Passed
EXNODE1 DnsRegistrationStatus Passed
EXNODE1 ReplayService Passed
EXNODE1 DBMountedFailover Passed
EXNODE1 SGCopySuspended Passed
EXNODE1 SGCopyFailed Passed
EXNODE1 SGInitializing Passed
EXNODE1 SGCopyQueueLength Passed
EXNODE1 SGReplayQueueLength Passed
VLEM SGReplayQueueLength Passed
I ran into this when I brought up my GeoClusters with WinSvr '08 + Exchange 07 SP1 back in fall of '08. I logged a case with PSS at that time and they told me it was supposed to be resolved in SP1 RU7 and it never was, we're on RU9 and still get the error. Good times.
ReplyDeleteI have not confirmed this myself, but this is supposed to have been fixed in Update Rollup 1 for Exchange 2007 Service Pack 3. UR1 for SP3 is available here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ae45d06e-dcb7-43d8-b1ff-d3953836425b&displaylang=en
ReplyDeleteI hope to confirm the fix soon.
Just an update on this?: This error still presents itself in SCOM2012. Same error with CCR cluster nodes.
ReplyDelete