Chapter 19 Intelligent Fibre Channel Processor Test (ifptest)
ifptest tests the functionality of the PCI FC_AL card when there are no devices attached to the loop. The driver checks for devices on the fibre loop. If devices are detected the driver blocks any diagnostic commands.
Note -
When devices are attached to the loop, do not run ifptest. Instead, run disktest tests on the individual devices. This will test the whole subsystem including the FC_AL controller.
ifptest uses the "mailbox" interface to the card. This interface allows certain firmware operations to be performed that normally would not be available to the application layer.
There are four subtests that are run in online and functional modes:
-
Mailbox loopback Test
Loads a series of registers into the input mailboxes on the card and then reads the output mailboxes and compares results. This verifies that the system side of the card is operating correctly, and that the internal data paths are ok.
-
Firmware revision check
Reads the firmware revision from the firmware and compares it against a revision loaded by the driver.
-
Checksum firmware test
Runs an internal checksum test on the installed firmware. This verifies that the RISC ram on the card is fully functional and that the installed firmware is still intact. This test also serves as a quick ram check of the RISC ram.
-
Dump revision levels
Extracts the hardware and firmware revision levels of different sub modules on the card.
ifptest Options
ifptest Option Menu
Table 19-1 ifptest Options|
ifptest Options |
Description |
|---|---|
|
Mailbox Loopback Test |
Enable|Disable the mailbox loopback command. This test writes data patterns into the mailboxes and then reads them back from the output mailboxes and verifies the data is correct. |
|
Firmware Revision Check |
Enable|Disable the firmware revision check command. This test extracts the firmware revision from the RISC firmware code and verifies against expected values. |
|
Firmware Checksum Test |
Enable|Disable the firmware checksum command. This command instructs the interface's RISC processor to calculate the checksum on the current microcode and then compare it against the checksum that was loaded in with the microcode. |
|
Check Module Revisions |
Enable|Disable the firmware checksum command. This command returns the revision level of several sub-modules on the interface card. Although this test is executed when enabled, the module revision levels are only printed out in VERBOSE mode. |
ifptest Command Line Syntax
/opt/SUNWvts/bin/ifptest standard_arguments -o dev=device name,mbox=Enable|Disable,fwrevcheck=[Enable|Disable], checksum=[Enable|Disable],modrevcheck=[Enable|Disable]
Table 19-2 ifptest Command Line Syntax|
Argument |
Explanation |
|---|---|
|
dev |
The name of the device to test. |
|
mbox |
Enable|Disable the mailbox loopback command. This test writes data patterns into the mailboxes and then reads them back from the output mailboxes and verifies the data is correct. |
|
fwrevcheck |
Enable|Disable the firmware revision check command. This test extracts the firmware revision from the RISC firmware code and verifies against expected values. |
|
checksum |
Enable|Disable the firmware checksum command. This command instructs the interface's RISC processor to calculate the checksum on the current microcode and then compare it against the checksum that was loaded in with the microcode. |
|
modrevcheck |
Enable|Disable the firmware checksum command. This command returns the revision level of several sub-modules on the interface card. Although this test is executed when enabled, the module revision levels are only printed out in VERBOSE mode. |
Note -
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".
ifptest Test Modes
Table 19-3 ifptest Test Modes|
Test Mode |
Description |
|---|---|
|
Functional mode |
ifptest runs the full set of mailbox tests |
| Functional mode through SyMON |
ifptest runs the full set of mailbox tests |
|
Connectivity |
ifptest only performs an open/close |
Note -
Connectivity mode will only open the controller to verify that the path is still viable.
ifptest Error Messages
Table 19-4 ifptest Error Messages|
|
Error Message |
Probable Cause(s) |
Recommended Action |
|---|---|---|---|
|
6000 |
Mailbox loopback failed |
FC_AL board, System software. |
Replace FC_AL board. If the problem persists, contact your authorized Sun service provider. |
|
6001 |
Error parsing command line options |
Error in command line. |
Check your command line and re-enter it if necessary. |
|
6002 |
Can not associate device with string. |
New hardware added since VTS probe or system software. |
Stop all testing and re-probe. If the problem persists, contact your authorized Sun service provider. |
|
6003 |
FW Stop command returned data, expected 0. |
IFP Firmware or a system software. |
Reload IFP firmware. If the problem persists, contact your authorized Sun service provider. |
|
6004 |
Command #data (cmd=value) did not successfully complete, status: Obs 0xvalue, Exp 0xvalue |
IFP Firmware or a system software.
|
Reload IFP firmware. If the problem persists, contact your authorized Sun service provider. |
|
6005 |
Chained command number data failed to complete. |
IFP Firmware or a system software.
|
Reload IFP firmware. If the problem persists, contact your authorized Sun service provider. |
|
6006 |
data errors were observed during this cycle. |
|
|
|
6007 |
Command chain aborted: data commands queued, data commands run |
|
|
|
6008 |
Command Issued: mbox[0]=0xvalue, mbox[1]=0xvalue, mbox[2]=0xvalue, mbox[3]=0xvalue, mbox[4]=0xvalue, mbox[5]=0xvalue, mbox[6]=0xvalue, mbox[7]=0xvalue |
|
|
|
6009 |
Result Mboxes: mbox[0]=0xvalue, mbox[1]=0xvalue, mbox[2]=0xvalue, mbox[3]=0xvalue, mbox[4]=0xvalue, mbox[5]=0xvalue, mbox[6]=0xvalue, mbox[7]=0xvalue |
|
|
|
6010 |
HCCR=0xvalue, BUS_SEMA=0xvalue, ISR=0xvalue, ICR=0xvalue, CDMA_COUNT=0xvalue, CDMA_ADDR=0xvalue |
|
|
|
6011 |
CDMA_STATUS=0xvalue, CDMA_CONTROL=0xvalue, RDMA_COUNT=0xvalue, RDMA_ADDR=0xvalue, RDMA_STATUS=0xvalue, RDMA_CONTROL=0xvalue |
|
|
|
6012 |
TDMA_COUNT=0xvalue, TDMA_ADDR=0xvalue, TDMA_STATUS=0xvalue, TDMA_CONTROL=0xvalue, RISC_PSR=0xvalue, RISC_IVR=0xvalue |
|
|
|
6013 |
RISC_REGS: RR0=0xvalue, RR1=0xvalue, RR2=0xvalue, RR3=0xvalue, RR4=0xvalue, RR5=0xvalue, RR6=0xvalue, RR7=0xvalue |
|
|
|
6014 |
RISC_REGS: RR8=0xvalue, RR9=0xvalue, RR10=0xvalue, RR11=0xvalue, RR12=0xvalue, RR13=0xvalue, RR14=0xvalue, RR15=0xvalue |
|
|
|
6015 |
RISC_PCR=0xvalue, RISC_RAR0=0xvalue, RISC_RAR1=0xvalue, RISC_LCR=0xvalue, RISC_PC=0xvalue, RISC_SP=0xvalue |
|
|
|
6016 |
REQUEST_IN=0xvalue, REQUEST_OUT=0xvalue, RESPONSE_IN=0xvalue, RESPONSE_OUT=0xvalue |
|
|
|
6017 |
CURRENT_REQ_PTR=0xvalue, BASE_REQ_PTR=0xvalue, CURRENT_RESP_PTR=0xvalue, BASE_RESP_PTR=0xvalue |
|
|
| 6018 | Interface at string is currently not testable, there may be devices attached. | ||
| 6019 | Bad option passed to test: string | ||
| 6020 | No device detected for ifpdata | ||
| 6021 | Cannot associate an IFP device with string. | ||
| 6021 | No IFP devices detected on this system. | ||
|
8000 |
string: invalid file descriptor data passed in. |
Programming error or system software. |
If the problem persists, contact your authorized Sun service provider. |
|
8001 |
string: IOCTL call failed: string. |
wrong/missing IFP driver. |
Contact your system administrator to load correct driver. If the problem persists, contact your authorized Sun service provider. |
|
8002 |
string: Firmware checksum failed, Rec: value, Exp: 0x0 |
Unsupported or bad firmware loaded or bad ifp controller. |
Load the correct ifp driver. If the problem persists, contact your authorized Sun service provider. |
|
8003 |
string: Get Revision mailbox command failed, return code 0xvalue. |
Incorrect ifp firmware loaded or a system software problem. |
Load the correct ifp driver. If the problem persists, contact your authorized Sun service provider. |
|
8004 |
Bad device name passed to test: string | Wrong entry on command line. |
Check and retype the command line. If the problem persists, contact your authorized Sun service provider. |
|
8005 |
Bad option passed to test: string | Wrong entry on command line. | Check and retype the command line If the problem persists, contact your authorized Sun service provider. |
|
8006 | Open of IFP device string failed; string | System software problem. |
Contact your system administrator. If the problem persists, contact your authorized Sun service provider. |
|
8007 | Open of /etc/path_to_inst file failed; string | System software problem. |
Contact your system administrator. If the problem persists, contact your authorized Sun service provider. |
|
8008 | Get firmware revision IOCTL failed: string |
System software problem. |
Contact your system administrator. If the problem persists, contact your authorized Sun service provider. |
| 8009 | Device string is untestable, devices attached to loop | Devices attached to controller or a system software problem. | Remove interface connections and try again. |
| 8010 | Open ctrlr string as RDWR failed. Reason: string | Device name incorrect (command line only), or a system software problem. | Check and re-enter the command line. If the problem persists, contact your authorized Sun service provider. |
| 8011 | Device string is untestable, reason: string | Device name is incorrect (command line only), or the wrong driver is installed or a system software problem. | Check and re-enter the command line. Verify that the correct driver is installed. If problem persists, contact your authorized Sun service provider. |
- © 2010, Oracle Corporation and/or its affiliates