plntest checks the functionality of the controller board on the SPARCstorage(TM) Array. The SPARCstorage Array (SSA) is a large disk storage I/O subsystem capable of housing up to 30 SCSI hard drives. The SSA communicates with a host system over a fiber-optic link provided by an SBus-based host adapter card in the host system and the corresponding SSA controller board hardware.
The SSA controller card is an intelligent, CPU-based board with its own memory and ROM-resident software. In addition to providing a communications link to the disk drives, it also buffers data between the host system and disk drives in its nonvolatile RAM (NVRAM). For data to go from the host to a particular disk, it must first be successfully transferred to this NVRAM space.
The host machine, SBus host adapter card, fiber-channel connection, and the SSA controller board must be working properly to perform this data transfer operation. By verifying and stressing this operation, plntest can isolate failures on the SSA disk drives from failures on the SSA controller board.
disktest transfers data on the SSA disk drives over the same path mentioned above. However, disktest does not transfer data as quickly as plntest.
The plntest exercises the hardware and software by invoking SCSI read buffer commands of various sizes to the NVRAM. These operations exercise the host fiber channel hardware, the SSA fiber channel hardware, the SSA resident management software, and the hardware component interaction on the SSA controller card (all components except the SCSI devices). In addition, the plntest reports failure of the fan module and the NVRAM battery module of the SPARC storage array.
Configuration lists the names of all the logical disk drives (both single and grouped) that are attached to the SPARCstorage Array controller board. plntest is not a scalable test.
If no disks are present, none is displayed under the Attached Disks heading.
Test Mode |
Description |
---|---|
Connection Test |
In this mode, plntest checks the state of the battery module and the fan module of the SPARCstorage array. |
Functional Test |
Performs the same type of tests as Online mode. |
Functional mode through SyMON |
If you invoke SunVTS through SyMON, the following Functional test description applies: plntest checks the state of the battery module and the fan module of the SPARCstorage array. The plntest issues a SCSI command, READBUFFER, causing the entire NVRAM to be read. This test uses different transfer buffer sizes |
/opt/SUNWvts/bin/plntest standard_arguments -o ?,dev=device_name,x,
Table 24-2 plntest Command Line Syntax
Argument |
Explanation |
---|---|
? |
Probes the system for valid SSA controller devices and prints them to screen (see "Probing for SSA Controller Devices.") |
dev=device_name |
Specifies the physical path name of the SSA controller card to be tested. This argument must be included when running plntest from the command line, unless the ? argument is used. |
x |
Probes the specified SSA controller card for the single and grouped disks attached to the controller card, and prints their logical names to the screen. Note: The dev=device_name must be specified for this option to work. |
64-bit tests are located in the sparcv9 subdirectory: /opt/SUNWvts/bin/sparcv9/testname. If a test is not present in this directory, then it may only be available as a 32-bit test. For more information refer to "32-Bit and 64-Bit Tests".
Unlike most other hardware devices, the SSA controller card does not have a logical device name (one you would find in the /dev directory). Therefore, the SSA controller card is identified by its longer, physical device name.
The physical device name of the SSA controller card cannot be used to run plntest.
When running plntest from the command line, the physical device name of the SSA controller card cannot be used, so a logical name must be specified. ANSI standards require commas as delimiters between items. Since the physical name of the SSA controller contains embedded commas, if you use a physical name that contains commas as a command line option, plntest misinterprets the option.
There are two ways that you can create a logical name:
Run the SunVTS kernel (vtsk), which automatically creates a logical name entry for the SSA controller under the /dev directory, such as:
# /dev/ssaXX , where XX represents the decimal number of the controller
Use this name as the parameter for the dev= option of plntest.
Manually make a soft link from the actual physical device name to a logical name of your choice (under /dev). Use this name as the parameter for the dev= option of plntest, as shown in the following example:
machine# ./plntest "?" 1: /devices/io-unit@f,e3200000/sbi@0,0/SUNW,soc@1,0/ SUNW,pln@0c0d,0e0f0102:ctlr 2: /devices/io-unit@f,e0200000/sbi@0,0/SUNW,soc@3,0/SUNW,pln@0c0d,0e0f0102:ctlr machine# ln -s \ /devices/io-unit@f,e3200000/sbi@0,0/SUNW,soc@1,0/ SUNW,pln@0c0d,0e0f0102:ctlr \ /dev/ssa1 machine# /opt/SUNWvts/bin/plntest dev=/dev/ssa1
|
Error Message |
Probable Cause(s) |
Recommended Action |
---|---|---|---|
6010 |
device_name text1 during text2. text1 indicates SCSI sense information for the SCSI command text2 |
|
|
6011 |
device_name SCSI status returned is text, Command issued was text |
|
|
6012 |
device_name: NVRAM Battery is low or has failed |
Suspect battery module. |
Fast writes will be disabled. Consult your authorized Sun service provider. |
8000 |
device_name Failed to open()(error_message |
Suspect fiber optic cable. |
Consult your authorized Sun service provider. |
Suspect SSA controller board. |
|
||
Suspect SOC host adapter. |
|
||
8010 |
device_name text1 during text2. text1 indicates SCSI sense information for the SCSI command text2 |
|
|
8011 |
device_name SCSI status returned is text, Command issued was text |
|
|
8012 |
device_name Fans have failed |
Fan failure. |
Consult your authorized Sun service provider. |