HP BL25/35/45p HP Broadcom iSCSI Boot for NC37xx/NC380x Adapters User Guide - Page 21

Target login problems Symptoms: The iSCSI initiator is able to connect to the ta rget but is unable to log in successfully. Possible causes: • The initiator is not configured with the right target name • The initiator is not configured with the right target IP address • The initiator is not configured with the right initiator name • The initiator and target are not configured for the same authentication method • The initiator and target are using CHAP or Mutual CHAP authentication so they may not be configured with matching user name and secret(s) • If the target implements some form of Access Control Lists (ACL), the target ma y not be configured to allow it on the initiator Boot problems Symptoms: The initiator is able to connect to and log in to the ta rget, but the system does not attempt to boot from the iSCSI disk. Possible causes: • Verif y the Standard Boot Order (IPL) list and Boot Controller Order list is configured correctly in RBSU according to the Configure the server for iSCSI boot section. • Option ROM space is limited. If too many option ROMs a re enabled the boot ma y fail due to lack of space. In this case it is necessary to d isable PXE on other adapters, disable the Smart Arra y Controller, physically remove the hard drives, and so on. • Verif y the Option ROM configuration setting "Boot to iSCSI" is set to Enabled. LUN access problems Symptoms: The initiator is able to connect to and log in to the ta rget, but the system doesn't see a disk present (it attempts to b oot f rom an internal disk or PXE). Possible causes: • The initiator is not configured with the correct LUN from which to boot (Some targets start nu mbering at 1 instead of 0) • The target is not conf igured to allow access to the specified LUN by the initiator OS problems Symptoms: Troubleshooting 21