Problems with iSCSI attached servers

If you are experiencing one of the problems listed below, you may begin troubleshooting by performing the actions listed. This is not a comprehensive list, so some problems may require actions beyond those listed here. To find information that may help you troubleshoot problems, see Check message and job logs.

Initializing the service processor configuration fails

If there is a message CPDC4xx or CPFC4xx in the system operator's message queue (QSYSOPR) or the job log of the batch job or interactive user involved, see IBM Director Troubleshooting.

When installing or starting a server, the NWSD status stays VARIED OFF

• Ensure that all required network server host adapters configured for the server are varied on before installing or starting a server. If a network server host adapter will not vary on, check for messages in the network server host device's message queue.
• If there is a message CPDC4xx or CPFC4xx in the system operator's message queue (QSYSOPR) or the job log of the batch job or interactive user involved, see IBM Director Troubleshooting.

With the hosted system powered on, a server will not start

See Problems sharing hosted system hardware.

The hosted system's console displays 'No iSCSI devices found' or prompts for diskette

• The iSCSI HBA configured for boot in the hosted system was unable to do so.
• There may be an iSCSI configuration problem. See iSCSI Troubleshooting
  (www.ibm.com/servers/eserver/iseries/integratedxseries/iscsireadme/troubleshooting.html).
• If message CPPC056 is in the Product Activity Log, a CHAP configuration problem is likely.
• There may be a network problem between the hosted system's iSCSI HBA configured for boot and the iSeries™ HBA corresponding to the path configured for the NWSD's system drive storage space. See Boot and storage path network analysis.

The NWSD status is VARIED ON, but Windows does not begin to boot

• There may be an iSCSI configuration problem. See iSCSI Troubleshooting
  (www.ibm.com/servers/eserver/iseries/integratedxseries/iscsireadme/troubleshooting.html).
• If message CPPC056 is in the Product Activity Log, a CHAP configuration problem is likely.
• There may be a network problem between the hosted system's iSCSI HBA configured for boot and the iSeries HBA corresponding to the path configured for the NWSD's system drive storage space. See Boot and storage path network analysis.

The NWSD status is DEGRADED

Ensure that all required network server host adapters configured for the server are varied on. If a network server host adapter will not vary on, check for messages in the network server host device's message queue.

Storage using a path other than the boot path does not show up in Windows

• There may be a network problem between the hosted system and the iSCSI HBA in the iSeries that corresponds to the non-boot path. See Boot and storage path network analysis.
• If message CPPC056 is in the Product Activity Log, there is a CHAP problem. In this case, it is most likely due to a problem with the digital certificates that the Windows environment on iSeries needs to securely transfer its own sensitive data between i5/OS and Windows. See Managing path certificates.

Storage using a path other than the boot path sometimes shows up late in Windows

• This is normal the first time the server is started after you change certain i5/OS configuration information, such as SCSI local interface information in the network server host adapter or CHAP information in the remote system configuration.
• This is normal if an iSCSI HBA in the hosted system has not been used with this particular NWSD before. This would be the case when an iSCSI HBA is replaced in the hosted system, or when using a different hosted system as a hot spare.
• If your application involves an automatic start service that is sensitive to the above situations, see the Advanced iSCSI tasks web page (www.ibm.com/servers/eserver/iseries/integratedxseries/iscsireadme/advancedtasks.html).

User enrollment or submit remote command fails with NTA02BB, NTA028A, NTA028B

• There is a problem with the digital certificates that the Windows environment on iSeries needs to securely transfer its own sensitive data between i5/OS and Windows. See Managing path certificates.
• For NTA028A and NTA028B, ensure that the time and date on the hosted system doesn't differ significantly from the date on the iSeries, as this can cause digital certificates to appear to be invalid.