Troubleshooting
Problem
After a system reboot, when SANsurfer is launched the second iSCSI port (port1) is not displayed in SANsurfer.
Resolving The Problem
| Source |
|---|
RETAIN tip: H184441
Symptom |
|---|
After a system reboot, when SANsurfer is launched the second iSCSI port (port1) is not displayed in SANsurfer.
Affected configurations |
|---|
The system may be any of the following IBM eServers:
- eServer BladeCenter LS20, Type 8850, any model
- IBM eServer BladeCenter HS20, Type 8678, any model
- IBM eServer BladeCenter HS20, Type 8832, any model
- IBM eServer BladeCenter HS20, Type 8843, any model
The system is configured with the following option(s):
- 1GB iSCSI TOE Expansion Card, Option part number 26K6487, FRU
part number 26K6490.
The following NOS(es) are affected:
- Red Hat Enterprise Linux, version 3 AS U4, 4 AS.
- SuSE Linux Enterprise Server 9.
- SuSE Linux Enterprise Server 9 x86.
Note: This does not imply that the network operating
system will work under all combinations of hardware and
software.
Please see the compatibility page for more information:
http://www.ibm.com/servers/eserver/serverproven/compat/us/
The 4.00.11 Firmware for SANsurfer is affected.
The system has the symptom described above.
Solution |
|---|
This issue will be fixed in a later release of SANsurfer, scheduled for release to the QLogic web site in 3rd Quarter 2005.
Workaround |
|---|
- Close SANsurfer.
Note: If iqlremote agent is running, stop it by entering "pkill iqlremote" at a linux terminal.
- Restart SANsurfer.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
29 January 2019
UID
ibm1MIGR-61095