Boot and storage path network analysis

For more information about these steps and additional troubleshooting procedures, see iSCSI troubleshooting (www.ibm.com/servers/eserver/iseries/integratedxseries/iscsireadme/troubleshooting.html).

• On the hosted system, use the CTRL-Q utility to display the hosted system's iSCSI HBA MAC addresses. Ensure that these match the SCSI interface adapter address values in the i5/OS remote server configuration. This step may be skipped if you are here because a manually configured boot failed.
• Use the CTRL-Q utility or Device Manager view of the SCSI driver to PING the SCSI IP address of the appropriate iSCSI HBA for iSeries™.
• If PING fails, perform the following steps.
  • Ensure that the physical network is properly connected, and that devices in the network, such as switches, are functioning.
  • Ensure that requirements defined in iSCSI network are satisfied.
  • If a firewall or a similar packet filtering function is involved, ensure that the firewall allows Internet Control Message Protocol (ICMP) packets to pass. Unlike SCSI IP addresses, LAN IP addresses can be affected by firewall software running in Windows.
  • If your NWSD uses IP security (IPSec) rules other than *NONE, See iSCSI Troubleshooting
    (www.ibm.com/servers/eserver/iseries/integratedxseries/iscsireadme/troubleshooting.html).
• If ping succeeds, perform the following steps.
  • If a firewall or a similar packet filtering function is involved, see Configure a firewall. Unlike SCSI IP addresses, LAN IP addresses can be affected by firewall software running in Windows.
  • If DHCP boot fails and a routed network is involved, ensure that an appropriately configured DHCP relay agent (also known as a BOOTP relay boot) exists in the network.