Validate Disk Access Latency:No disks were found on which to perform cluster validation tests.

  • Hi ,

    I get the following below error .Kindly check and let me know what should be done in initiating iscsi disk.

    Validate Disk Access Latency

    Description: Validate acceptable latency for disk read and write operations.

    Start: 4/29/2013 11:38:53 AM.

    No disks were found on which to perform cluster validation tests.

    Stop: 4/29/2013 11:38:53 AM.

    Back to Summary

    Back to Top

    --------------------------------------------------------------------------------

    Validate Disk Arbitration

    Description: Validate that a node that owns a disk retains ownership after disk arbitration.

    Start: 4/29/2013 11:38:53 AM.

    No disks were found on which to perform cluster validation tests.

    Stop: 4/29/2013 11:38:53 AM.

    Back to Summary

    Back to Top

    --------------------------------------------------------------------------------

    Validate Disk Failover

    Description: Validate that a disk can fail over successfully with data intact.

    Start: 4/29/2013 11:38:53 AM.

    No disks were found on which to perform cluster validation tests.

    Stop: 4/29/2013 11:38:53 AM.

    Back to Summary

    Back to Top

    --------------------------------------------------------------------------------

    Validate File System

    Description: Validate that the file system on disks in shared storage is supported by failover clusters.

    Start: 4/29/2013 11:38:53 AM.

    No disks were found on which to perform cluster validation tests.

    Stop: 4/29/2013 11:38:53 AM.

    Back to Summary

    Back to Top

    --------------------------------------------------------------------------------

    Validate IP Configuration

    Description: Validate that IP addresses are unique and subnets configured correctly.

    AGSCHEL02-SRV03.agshealth.com

    Item Name

    Adapter Name Local Area Connection* 11

    Adapter Description Microsoft Failover Cluster Virtual Adapter

    Physical Address 02-30-E6-30-4C-47

    Status Not Operational

    DNS Servers

    IP Address fe80::8cdb:826d:a12a:d479%15

    Prefix Length 64

    IP Address 169.254.212.121

    Prefix Length 16

    Item Name

    Adapter Name Ethernet

    Adapter Description Intel(R) PRO/1000 MT Network Connection

    Physical Address 00-0C-29-7B-F0-1A

    Status Operational

    DNS Servers 10.10.12.15, 10.10.10.21

    IP Address 10.10.12.18

    Prefix Length 24

    Item Name

    Adapter Name Loopback Pseudo-Interface 1

    Adapter Description Software Loopback Interface 1

    Physical Address

    Status Operational

    DNS Servers

    IP Address ::1

    Prefix Length 128

    IP Address 127.0.0.1

    Prefix Length 8

    Item Name

    Adapter Name isatap.{46BEEE67-06E3-40D4-B5B6-2C61FEDCD197}

    Adapter Description Microsoft ISATAP Adapter #2

    Physical Address 00-00-00-00-00-00-00-E0

    Status Not Operational

    DNS Servers

    IP Address fe80::5efe:10.10.12.18%14

    Prefix Length 128

    AGSCHTD05-SRV01.agshealth.com

    Item Name

    Adapter Name Local Area Connection* 11

    Adapter Description Microsoft Failover Cluster Virtual Adapter

    Physical Address 02-CE-31-7E-6B-47

    Status Not Operational

    DNS Servers

    IP Address fe80::b1cb:2621:8ba0:fa8c%16

    Prefix Length 64

    IP Address 169.254.250.140

    Prefix Length 16

    Item Name

    Adapter Name Ethernet

    Adapter Description Intel(R) PRO/1000 MT Network Connection

    Physical Address 00-50-56-B4-59-25

    Status Operational

    DNS Servers 10.10.10.21, 10.10.12.15

    IP Address fe80::4802:b41d:bcca:4363%12

    Prefix Length 64

    IP Address 10.10.10.10

    Prefix Length 23

    Item Name

    Adapter Name Loopback Pseudo-Interface 1

    Adapter Description Software Loopback Interface 1

    Physical Address

    Status Operational

    DNS Servers

    IP Address ::1

    Prefix Length 128

    IP Address 127.0.0.1

    Prefix Length 8

    Item Name

    Adapter Name isatap.{D82337FC-B8DF-4D4D-9D86-CB2BB252814C}

    Adapter Description Microsoft ISATAP Adapter #2

    Physical Address 00-00-00-00-00-00-00-E0

    Status Not Operational

    DNS Servers

    IP Address fe80::5efe:10.10.10.10%14

    Prefix Length 128

    Item Name

    Adapter Name Teredo Tunneling Pseudo-Interface

    Adapter Description Teredo Tunneling Pseudo-Interface

    Physical Address 00-00-00-00-00-00-00-E0

    Status Not Operational

    DNS Servers

    IP Address fe80::100:7f:fffe%15

    Prefix Length 64

    Verifying that a node does not have multiple adapters connected to the same subnet.

    Verifying that each node has at least one adapter with a defined default gateway.

    Verifying that there are no node adapters with the same MAC physical address.

    Verifying that there are no duplicate IP addresses between any pair of nodes.

    Checking that nodes are consistently configured with IPv4 and/or IPv6 addresses.

    Verifying that all nodes IPv4 networks are not configured using Automatic Private IP Addresses (APIPA).

    Back to Summary

    Back to Top

    --------------------------------------------------------------------------------

    Validate Memory Dump Settings

    Description: Validate that none of the nodes currently requires a reboot (as part of a software update) and that each node is configured to capture a memory dump if it stops running.

    Validating software configuration.

    Back to Summary

    Back to Top

    --------------------------------------------------------------------------------

    Validate Microsoft MPIO-based disks

    Description: Validate that disks that use Microsoft Multipath I/O (MPIO) have been configured correctly.

    Start: 4/29/2013 11:38:53 AM.

    No disks were found on which to perform cluster validation tests.

    Stop: 4/29/2013 11:38:53 AM.

    Back to Summary

    Back to Top

    --------------------------------------------------------------------------------

    Validate Multiple Arbitration

    Description: Validate that in a multiple-node arbitration process, only one node obtains control.

    Start: 4/29/2013 11:38:53 AM.

    No disks were found on which to perform cluster validation tests.

    Stop: 4/29/2013 11:38:53 AM.

  • some people create database names that REQUIRE brackets (like 12345), so I would try something like this:

    from [' + name + '].dbo.mytable ...

    same goes for table names too, btw

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • Can anyone reply with the appropriate answer !!

  • vishalsurya50 (4/30/2013)


    Can anyone reply with the appropriate answer !!

    Is the storage offline when you are running the cluster validation tool? This is a prerequisite for the test.

  • TheSQLGuru (4/29/2013)


    some people create database names that REQUIRE brackets (like 12345), so I would try something like this:

    from [' + name + '].dbo.mytable ...

    same goes for table names too, btw

    How in the HECK this this reply wind up under THIS thread?!? sigh...

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • vishalsurya50 (4/29/2013)


    Hi ,

    I get the following below error .Kindly check and let me know what should be done in initiating iscsi disk.

    Validate Disk Access Latency

    Description: Validate acceptable latency for disk read and write operations.

    Start: 4/29/2013 11:38:53 AM.

    No disks were found on which to perform cluster validation tests.

    Stop: 4/29/2013 11:38:53 AM.

    Back to Summary

    Back to Top

    --------------------------------------------------------------------------------

    Validate Disk Arbitration

    Description: Validate that a node that owns a disk retains ownership after disk arbitration.

    Start: 4/29/2013 11:38:53 AM.

    No disks were found on which to perform cluster validation tests.

    Stop: 4/29/2013 11:38:53 AM.

    Back to Summary

    Back to Top

    --------------------------------------------------------------------------------

    Validate Disk Failover

    Description: Validate that a disk can fail over successfully with data intact.

    Start: 4/29/2013 11:38:53 AM.

    No disks were found on which to perform cluster validation tests.

    Stop: 4/29/2013 11:38:53 AM.

    Back to Summary

    Back to Top

    --------------------------------------------------------------------------------

    Validate File System

    Description: Validate that the file system on disks in shared storage is supported by failover clusters.

    Start: 4/29/2013 11:38:53 AM.

    No disks were found on which to perform cluster validation tests.

    Stop: 4/29/2013 11:38:53 AM.

    Can you supply more detail about the iscsi setup, are you using the microsoft iscsi initiator?

    Are you using MPIO or MCS?

    Have you attached the LUNs to more than one node?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply