Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Storage tests on a failover cluster may not discover all shared LUNs

Storage tests on a failover cluster may not discover all shared LUNs

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a Windows Server 2012 or Windows Server 2012 R2 multi-site failover cluster.
  • A multi-site storage area network (SAN) is configured to have site-to-site mirroring.
  • You use the Validate a Configuration Wizard to run a set of validation tests on the failover cluster.
In this scenario, storage tests may not detect all logical unit numbers (LUNs) as shared LUNs.

↑ Back to the top

Cause

Storage validation test selects only shared LUNs. A LUN is determined to be shared if its disk signatures, device identification number (page 0×83), and storage array serial number are the same on all cluster nodes. When you have site-to-site mirroring configured, a LUN in one site (site A) has a mirrored LUN in another site (site B). These LUNs have the same disk signatures and device identification number (page 0×83), but the storage array serial number are different. Therefore, they are not recognized as shared LUNs.

↑ Back to the top

Resolution

To resolve the issue, run all the cluster validation tests before you configure the site-to-site LUN mirroring.

Note If the validation test is needed afterward for support situations, LUNs that are not selected for storage validation tests are supported by Microsoft and the storage vendor as valid Shared LUNs.

↑ Back to the top

Keywords: kbtshoot, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2914974
Revision : 1
Created on : 1/7/2017
Published on : 1/15/2014
Exists online : False
Views : 392