Discovery problems

If a message is logged that indicates that the remote server or enclosure is not found, then the IBM Director interface was not able to find the targeted service processor on the network. See Remote server discovery and management.

If you are using a Remote Supervisor II service processor, verify that you are using the most recent firmware. See iSCSI install read me first

(www.ibm.com/servers/eserver/iseries/integratedxseries/iscsireadme)

If you are not using unicast addressing to discover the service processor, do the following steps:

• Verify that your iSeries™ server has a physical network connection to the service processor of the remote system.
  • See Ping from iSeries Navigator in the TCP/IP troubleshooting topic collection.
• If your iSeries server has a physical network connection to the service processor, check the firewall settings for the routers or switches on the iSCSI network. Network routers or switches between the iSeries LAN interface and the service processor might not support multicast addressing or are not configured to allow multicast addressing.

  Network routers or firewalls can block SLP multicast packets. The routers or firewalls may need to be configured to allow the Service Location Protocol IP address of 239.255.255.253 or port number 427 to allow passage of the SLP packets.

• Configure your service processor to use unicast addressing.

  The service processor must have a static host name or IP address configured. You can do this using the BIOS utility for an RSA II or the service processor web interface. See Use the Management Module or RSA II web interface for instructions on how to use the service processor web interface to configure the service processor.

  Change the service processor configuration to use unicast addressing, which uses the host name or IP address that was set in the service processor above to connect to the service processor. See Change service processor configuration properties.

If you are using unicast addressing to discover the service processor

• Verify your service processor IP address or host name is configured correctly both in the remote system service processor and in the service processor configuration on i5/OS.
• See the TCP/IP troubleshooting topic for general TCP/IP troubleshooting procedures.