HP Cluster Test Software manual Troubleshooting, Detecting new hardware

Page 44

10 Troubleshooting

Detecting new hardware

NOTE: This section applies only to the image version of Cluster Test.

When Cluster Test is installed on a head node of a new, unsupported model, or when Cluster Test is booted on a compute node on a new, unsupported model, a menu will be displayed with options for you to choose from. The message will look similar to

Model DL370G10 is not supported

Your options are:

1)Gather information about this model to send to the ClusterTest team.

2)Assume this model is like another, supported model and continue

Option 1: Cluster Test gathers information about the model, and if possible, saves it to the install media (this works for USB and network installs, but will not work for DVD installs). Information about the system is written to a tar file that is copied to the install media. Assuming everything goes well, your install media (your USB drive for USB installs, the capture directory for network installs, or the network install directory if no capture directory was specified) will contain a tar file similar to CT_<model-name>_<kernel-version>.tar.

Send the tar file to the Cluster Test team at ct-support@hp.com, who will provide a new kit that supports the new hardware.

Option 2: You will be prompted for a supported model to use instead.

These are the models supported by ClusterTest:

DL360G4 DL360G5 DL360G6

What model do you want to assume to boot this DL360G7 (enter q for quit)?

Cluster Test will attempt to complete the installation by assuming your DL360G7 is the model you specify. This might not work. If the installation is successful, an entry will be made to /opt/ clustertest/model_info on the head node, that describes the new model. This description will be used by clsetup.pl and other commands run from the head node.

Once you have successfully installed the head node using this approach, you may update the /tftpboot/netboot_initrd.gz file, which is used to boot the compute nodes, by running the apply_new_model_updates command. This command updates the /tftpboot/ netboot_init.gz with the collected information and should be run before booting any of the compute nodes.

44 Troubleshooting

Image 44
Contents HP Cluster Test Administration Guide January Contents Documentation feedback Glossary Index Useful files and directories Utility commandsSample test output CT Image CT Image using a networkVarieties of Cluster Test RPM Cluster Test GUI Starting Cluster TestFiles generated by Cluster Test Running cluster testsCluster Test GUI Running cluster tests Configuration settings Running tests in a batch Using scripts to run tests Running cluster tests Test descriptions CrissCrossMonitoring tests and viewing results Nodes monitoring windowTest output window Monitoring tests and viewing results Performance analysis Test report Checking the InfiniBand fabric Cluster Test toolbar menus Cluster Test toolbar menusFiles generated by accelerator test Accelerator test GUIStarting accelerator tests Verify Running accelerator testsGPU detection Sgemm Single Precision General Matrix Multiply Test Dgemm Double Precision General Matrix Multiply TestBandWidth GPU Bandwidth Test Memory TestNvidia Linpack Cuda Accelerated Linpack Benchmark Additional software Cluster Test procedure as recommended by HPConfiguring Cluster Test when using RPM Accelerator test procedure Cluster Test procedure as recommended by HP Cluster Test procedure # checkadm Cluster Test procedure Cluster Test procedure as recommended by HP Performance monitor Performance monitor utilityPerformance Monitor toolbar menu Xperf utility Firmware Summary Cluster Test toolsHardware Inventory Server health check Excluding the head node from tests Disk Scrubber Cluster Test tools Running tests in parallel An example cloned per-node directory Creating and changing per node filesAn example per-node directory NFS performance tuning NfsTroubleshooting Detecting new hardwareTroubleshooting Cluster Test Cluster Test Troubleshooting GuideSupport and other resources Scope of this documentIntended audience Contacting HPNew and changed information in this edition Related informationDocumentation WebsitesTypographic conventions Customer self repairCustomer self repair Useful files and directories Cluster Test Useful Files and DirectoriesUtility commands AnalyzeConrep Files generated by ibfabriccheck Inspectibfabric.pl Inspectibfabric.pl Utility commands Ipmitool Pdsh Sample test output CrissCrossSample test output Test4 Pallas Mpibyte Sample test output Stream Node24 Triad 3078.7949 3355 3488 3536 Disk Test CPULinpack UTKPassed Passed Passed Documentation feedback Glossary CMUIndex MPI Accelerator
Related manuals
Manual 25 pages 60.17 Kb