FSRM: All nodes in a failover cluster should be reachable

Published: April 27, 2010

Updated: August 31, 2012

Applies To: Windows Server 2008 R2, Windows Server 2012

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the File Services Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.

 

Operating System

Windows Server 2008 R2, Windows Server 2012

Product/Feature

File Services

Severity

Error

Category

Operation

The following nodes in a failover cluster cannot be verified because the nodes are not reachable, or because the BPA scan was performed against a remote failover cluster: {0}

The Best Practices Analyzer will not be able to check the status of File Server Resource Manager on the following nodes: {0}

Confirm that the nodes are online, log on to the nodes locally (or by using Remote Desktop), and then run the Best Practices Analyzer scan again. If this does not resolve the issue, use Windows PowerShell to troubleshoot the problem.

  1. From a command prompt, type the following to check the status of a node: CLUSTER [cluster-name] NODE node-name /STATUS

  1. Open an elevated Windows PowerShell command prompt.

  2. Type Get-ClusterNode and then press Enter.

Community Additions

ADD
Show: