CiB Raid Controller Kit Tests
The tests help validate that a Continuously Available (CA) storage controller and drivers meet all applicable requirements. The tests conduct various end-to-end test scenarios by running I/O workloads, data integrity tests against the cluster during a planned or unplanned failover, and validates that the hardware platform under test meets CA hardware requirements.
Test details
Specifications |
|
Platforms |
|
Supported Releases |
|
Expected run time (in minutes) | 270 |
Category | Scenario |
Timeout (in minutes) | 16200 |
Requires reboot | false |
Requires special configuration | true |
Type | automatic |
Additional documentation
Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):
Running the test
Before you run the test, complete the test setup as described in the test requirements for the type of storage controller that you are testing: Storage Adapter or Controller Testing Overview.
Hardware requirements
The following network requirements on the cluster nodes and the test controller machine must be met:
A minimum of two 1-Gigabit Ethernet adapters plus a private network for cluster communications.
We recommend one 10Gigabit Ethernet adapter.
All cluster nodes must have IP addresses that are provided by DHCP.
DNS resolution for all cluster nodes and the test controller machine.
The following requirements on cluster nodes must be met:
The cluster nodes must meet the Failover Clustering hardware requirements for Windows Server 10.
The cluster nodes must meet the hardware requirements for Windows Server 10.
The cluster nodes must have approximately 100 GB of free space on the local hard drive.
The following requirements on the test controller machine must be met:
The test controller must meet the hardware requirements for Windows Server 10.
The test controller must have approximately 100 GB of free space on the local hard drive.
The test controller must have at least 32 GB of memory.
We recommend that the test controller have at least two quad core processors.
The following shared storage requirements for cluster nodes must be met:
Must have at least 22 shared LUNs.
Must have a minimum LUN size of 1 GB.
Must be using either RAID1, RAID5, RAID6, or RAID10.
All LUNs must be visible on all cluster nodes.
All LUNs must be initialized and formatted as NTFS volumes with appropriate drive letters.
Software requirements
The following Active Directory Domain Services requirements must be met:
All machines must be joined to the same domain.
You must have logged in as a member of the Domain Admins security group on the test controller machine.
The following operating system requirements must be met:
The test controller must be running Windows Server 10.
The cluster nodes must be running Windows Server 10.
Support for Clustered Windows Servers that use clustered RAID controllers must be enabled on each cluster node. For more information, see Enable Support for Clustered Windows Servers using clustered RAID controllers
To start the tests
Open Windows HLK Studio.
Create a project.
In Device Manager, select your raid controller from the test pool.
Right-click each selected target. Click Add new features, select Device.Storage.Controller.Raid.ContinuousAvailability, and then click OK.
Click the Tests tab, select CiB Raid Controller Test, and click Run Selected. Assign TestController to the test controller machine.
Assign the remaining node to the remaining machine.
In the parameters, set the domain name, username, password, and cluster name.
Note
Cluster name cannot exceed 9 characters. If running the test multiple times, please use a different cluster name for each test run.
Click OK to schedule the test.
Troubleshooting
For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.
For troubleshooting information, see Troubleshooting Device.Storage Testing.
An error similar to "Cluster failure: test case ### failure" indicates that the cluster has not properly configured. Make sure that your shared disks are initialized and formatted as NTFS volumes to ensure a cluster can be formed and that no clusters or resource groups exist with the name specified in the cluster parameter.
If failures are found, you can review the logs to get additional details about the failures in HLK Studio under Results page:
- CiB Raid Controller Kit Tests->Run Eval Quality tests->Logs->te.wtl
- CiB Raid Controller Kit Tests->Run Raid Controller tests->Logs->te.wtl
More information
Parameters
Parameter name | Parameter description |
---|---|
CiBTestBin | test binary location |
AutomatedOnly | Specify true if this test should not run any manual tests |
ReplaceNodeNames.ps1 | |
PATHTOXML | |
CONFIGFILENAME | Name of the config XML file |
NODE1 | The first node in the cluster |
NODE2 | The second node in the cluster |
Domain | The name of the domain to which the cluster nodes are joined |
UserName | The user name of a user in the Domain Admins security group |
Password | The password of the user in the Domain Admins security group |
LOGFILE_INPUT | |
LOGFILE_OUTPUT | |
parse_whck.ps1 | |
ClusterName | The name of the cluster to be created |