ISO8859-1 $(q+rR+ c R 1 > U l } , *      -  D  d    2 3 3 G" {    2 3 M3 " N o'RS 0>!Do"T#' $&1%6X&' ()*+,"-9.M/_0r1 !+"M p   ! ""<"Kn# <FvQ $   2 !"$"""##1#-% %?)( (4()*6++ , - .v 0 2. Y23Ee57k9:;&S; < < =/ |=YESNOThe next test requires a wrap plug. It uses one of the following Part Numbers: %1$s. Do you have this wrap plug?UNPLUG.........the network cable, if attached, from the connector on the adapter. PLUG...........the wrap plug into the adapter connector. Use a wrap plug with one of the following Part Numbers: %1$s.UNPLUG.........the wrap plug from the connector on the adapter. PLUG...........the network cable, if removed, into the connector on the adapter.The next test requires Disc Test Media with one of the following Part Numbers: %1$s. Do you have this Test Media?UNLOAD.........any existing media in the drive. LOAD...........the Disc Test Media in the drive. Use Disc Test Media with one of the following Part Numbers: %1$s. Note: If you are unable to load the test media, continue by pressing the Enter key.UNLOAD.........the Disc Test Media in the drive. LOAD...........any media that may have been unloaded due to loading the Test Media.No trouble was found. However, the resource was not completely tested because the SR-IOV logical resource interface assigned to this partition indicated that the resource was not available for diagnostic mode. To completely test this resource: At the management console, enable diagnostic mode for the SR-IOV logical port assigned to this partition.Module Information Expected Speed:..... %1$s Gbps Current Speed:...... %2$s Gbps Registers test failed.Interrupt test failed.VPD test failed.Flash test failed.External link test failed.Internal parallel path loopback test failed.Internal serial path loopback test failed.Timer test failure.DMA read test failed.DMA write test failed.DMA read and write test failed.Internal loopback test failed.Internal 10 Mbps test failed.Internal 100 Mbps test failed.Internal 1000 Mbps test failed.Internal loopback IP checksum offload test failed.Internal loopback TCP checksum offload test failed.Internal loopback UDP checksum offload test failed.Internal loopback LSO test failed.External loopback test failed.External 10 Mbps test failed.External 100 Mbps test failed.External 1000 Mbps test failed.External loopback IP checksum offload test failed.External loopback TCP checksum offload test failed.External loopback UDP checksum offload test failed.External loopback LSO test failed.Error log analysis indicates a failure to initialize due to a self-test error.Error log analysis indicates a failure to initialize due to a problem while reading the EEPROM on the resource.Error Log Analysis indicates that this resource has failed due to a reset failure.Error Log Analysis indicates that this resource has failed due to a hardware error.Error Log Analysis indicates a resource failure.Error Log Analysis indicates a permanent resource error is reported.Error Log Analysis indicates that the microcode could not be loaded on the resource.Enhanced Error Handling failure on bus.Enhanced Error Handling logic failure.Enhanced Error Handling failure while testing adapter.Resource configuration error.EEH error.Resource I/O test failure.Download Firmware Error.Resource parity error.EEPROM Read Error.Checksum Verification Test failed.Memory Test failed.Open Test failed.Close Test failed.Port Link Failed.Port Speed Mismatch.Opening deviceRunning registers testRunning DMA read testRunning DMA write testRunning DMA read and write testRunning internal loopback testRunning internal IP checksum testRunning internal TCP checksum testRunning internal UDP testRunning internal LSO testRunning external loopback testRunning external IP checksum testRunning external TCP checksum testRunning external UDP testRunning external LSO testClosing deviceRunning checksum verification testRunning memory testRunning resource configuration test%1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s %1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s No trouble was found. However, the resource was not tested because other resources on the device are configured. To test this resource, you can perform one of the following: 1) Unconfigure the other resources and run Diagnostics again. 2) Shut down the system and run in maintenance mode. 3) Run Diagnostics from the Diagnostic Standalone package. %1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s Error Log Analysis has analyzed the hardware errors that were logged against this resource starting at %4$s on %5$s and ending at %6$s on %7$s. The number of errors analyzed: %8$d. The Diagnostic Application has determined that the resource is functioning properly. No repair actions or additional problem determination procedures need to be performed at this time. Error Log Analysis will continue to monitor this resource. %1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s Error Log Analysis indicates a possible problem with the resource's microcode. Make sure that the latest level of microcode is installed on the resource. If the microcode is at the latest level and the problem persists, contact your service support structure. %1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s The device has detected that the link between the resource and the switch is down and could not successfully recover the link. Check that the switch module is powered on and is properly seated.%1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s No trouble was found with this resource. However Error Log Analysis indicates that there recently may have been a network problem. If your Ethernet device is connected to a network, and if you are experiencing problems with network communications, check for a loose or defective cable or connection. If a switch or another system is directly attached to the Ethernet device, verify it is powered up, configured, and functioning correctly.%1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s No trouble was found with this resource. However Error Log Analysis indicates that there may be a problem with the connection to the network. Check for extensive network traffic. If this is not the cause, and if you are still experiencing problems, run advanced diagnostics.%1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s No trouble was found with this resource. However Error Log Analysis indicates that there may be a problem with the connection to the network. Check for extensive network traffic.%1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s No trouble was found. However, resource %2$s could not be restored to its initial defined state. If you do not want the resource to remain in the available state, run the following command from the command line: rmdev -l %2$s -R%1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s No trouble was found, however testing did not complete due to an error in the following ODM Class belonging to the device: %4$s Please correct the error or re-install the device's software, then run diagnostics again.%1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s Error Log Analysis has detected a communication error. This error may be caused by the device itself, by connecting cables, and/or by any attached devices. If you are experiencing communication issues, please check all the above beginning with any connecting cables. Check that the device is properly seated and that any attached devices are powered on as appropriate.%1$06.6lx ADDITIONAL INFORMATION FOR %2$s IN LOCATION %3$s Error Log analysis has detected multiple link errors. These errors can be caused by loose or defective cables. Check all cables and their connections.DISPLAY MICROCODE LEVEL %1$s %2$sINSTALL MICROCODE %1$s %2$sUnable to proceed due to an error in the following ODM Class belonging to the device: %1$s Please correct the error or re-install the device's software, then run diagnostics again.The upgrade may take longer.Processing Data ... Usage error. Use the following syntax when attempting to run this task from the command line: diag [-c] -d -T disp_mcode -c No console mode. Run without user interaction. -d Run the task on the device specified. -T disp_mcode Display the microcode level.The current microcode level for %1$s is %2$s. Usage error. Use the following syntax when attempting to run this task from the command line: diag [-c] -d -T "download [-s ] [-l {latest|previous}] [-f]" -c No console mode. Run without user interaction. -d Run the task on the device specified. -T download Install microcode. -s Specify the source for the microcode /etc/microcode or device name like fd0, cd0. -l latest Install latest level of microcode. This is the default. -l previous Install previous level of microcode. -f Install microcode even if the current level is not on source. Microcode installation is in progress. Installation of the microcode has not completed successfully. A software error occurred. Contact the service support structure for futher assistance. Installation of the microcode has not completed successfully. The current microcode level for %1$s is still %2$s. A software error occurred. Contact the service support structure for futher assistance. Installation of the microcode has not completed successfully. A hardware error occurred. Contact the service support structure for futher assistance. Installation of the microcode has not completed successfully. The current microcode level for %1$s is still %2$s. A hardware error occurred. Contact the service support structure for futher assistance. Installation of the microcode has not completed successfully. An error was detected while configuring the following resources %2$s Please run diagnostics on all of the following resources to ensure that the device is functioning properly %1$s Installation of the microcode has not completed successfully. The current microcode level for %1$s is still %2$s. The resource is currently in use. Free the resource and attempt the installation of the microcode again. Installation of the microcode has not completed successfully. The resource is currently in use. Free the resource and attempt the installation of the microcode again. Installation of the microcode has completed successfully on the following instances of the device: %1$s The current microcode level is %2$s. Please run diagnostics on these resources to ensure that the device is functioning properly. Installation of the microcode has completed successfully on the following instances of the device: %1$s The current microcode level is %2$s. However, an error was detected while restoring one or more of the resources to its initial state. An error was detected for the following resources %3$s. Please run diagnostics on all of the following resources to ensure that the device is functioning properly %1$s Installation of the microcode has completed successfully on the following instances of the device: %1$s The current microcode level is %2$s. However, the Configuration Data Base was not properly updated for the following resources %3$s. To properly update the Configuration Data Base, please run: rmdev -l resource -R (for each resource listed) followed by: cfgmgr -l resource (for each resource listed) Until this is done, neither lscfg nor the Display Microcode Task will reflect the correct microcode information. The new microcode will be %1$s. In order for the update to take full effect, the system must be rebooted. Until then, the resource will continue to report and operate at the current level.A software error occurred. Contact the service support structure for further assistance. **NOTICE *** NOTICE ** This device contains multiple resources that share a common microcode image. The common resources presently found are: %1$s When a microcode update is performed on the selected resource, the common resources are also updated. It is recommended that microcode installation be scheduled during non-peak production periods. If any drives are attached to this device, make sure that a current backup is available **NOTICE *** NOTICE ** This device contains multiple resources that share a common microcode image. The common resources presently found are: %1$s When a microcode update is performed on the selected resource, the common resources are also updated. Some of the resources of the device are currently not defined in the system. When these resources are configured, they will also have the newly installed microcode. It is recommended that microcode installation be scheduled during non-peak production periods. If any drives are attached to this device, make sure that a current backup is available This device contains multiple resources that share a common microcode image. The common resources presently found are: %1$s To update microcode on this device, microcode needs to be installed via an available fibre channel resource. There are no fibre channel resources available to perform the download operation at this time. Please make sure that a fibre channel resource is configured and run this task again This device contains multiple resources that share a common microcode image. The common resources presently found are: %1$s When a microcode update is performed on the selected resource, the common resources are also updated. The following resources are not in the proper state for the download operation %2$s Free these resources and attempt microcode installation again The system configuration indicates that there are client processes using this resource. Microcode Download can not proceed under these circumstances. An error occured connecting to the device driver. The device may not exist or may not be configured. Contact the service support structure for further assistance.%1$s is not available on the system and can not be selected as a microcode source. A software error occurred. The current level for %1$s could not be determined. Contact the service support structure for further assistance.There was a problem with the microcode file %1$s. Please make sure that the file is a valid microcode image and is not corrupted. ** NOTICE *** NOTICE ** In order to update microcode on %1$s, the process will be performed via %2$s. Be aware that subsequent messages may refer to %2$s and not %1$s. This is not an error. ** NOTICE *** NOTICE ** This device contains multiple resources that share a common microcode image. The common resources presently found are: %1$s When a microcode update is performed on the selected resource, the common resources are also updated. It is possible that there are additional resources on the device that are not currently available. When these resources are configured they will also have the newly installed microcode. It is recommended that microcode installation be scheduled during non-peak production periods. If any drives are attached to this device, make sure that a current backup is available.