IBM Software Technical Document

_______________________________________________________________
Document Information

Document Number:	409449775
Functional Area:	System i Integration with BladeCenter and System x
Subfunctional Area:	iSCSI
Sub-Subfunctional Area:	General
OS/400 Release:	V5R4M0
Product:	OS/400 BASE (5722SS100)
Product Release:	N/A

_______________________________________________________________

Document Title
Storage Using a Path Other Than the Boot Path Sometimes Shows Up Late in Windows

Document Description
For programs that run in Windows prior to an automatic start service known as 'iSeries Manager', the ability to access storage assigned to a non-boot path relies on information cached in the iSCSI HBA for the host system. However, the following cases exist where this cached information is not current until the iSeries Manager service runs. In these cases, early accesses to non-boot storage may fail:

o	When certain IBM® i5/OS™ configuration changes have been made since the last time this server was started, such as changes to the SCSI interface information or to CHAP information.
o	When a different hosted system iSCSI HBA is utilized than that which was used the last time this server was started. This will be the case when an iSCSI HBA is replaced, or when a different hosted system is being used as hot spare.

For the cases, do one of the following:

o

Stop and start the server again.

o

If the application involves an automatic start service that uses storage assigned to a non-boot path, make the service wait for the iSeries Manager service by entering the following at a command prompt: sc [server] config [service name] depend= "iSeries Manager" where [server] is the computer name for the server, and [service name] is the name of the automatic start service that should wait for the iSeries Manager service to start.

__________________________________________________________________

PMR Number:
Related APARs:
Related Public Documents: