Bridge FC4/2 Service and User Manual

2EVHUYLQJWKH 6\PSWRPV101
Troubleshooting
Observing the Symptoms
)RUDGGLWLRQDOLQIRUPDWLRQRQWURXEOHVKRRWLQJWKHSUREOHPVHH
 &RQILJXULQJ+38;IRU3HULSKHUD OV+3%
 +3)LEUH&KDQQHO0DVV6WRUDJH$ GDSWHU6HUYLFHDQG8VHU0DQXDO$
 +38;6\VWHP$GPLQLVWUDWLRQ7DVNV0DQXDO%
 7KHPDQXDOWKDWFDPHZLWKWKH6&6,GHYLFH
7DEOH 2YHUYLHZRI6\PSWRPV+RVW6LGH
Symptom Possible causes Recommended action
The host cannot read or
write to devices
connected to the SSB.
There could be a faulty FC
connection, SCSI bus or
connection between the SSB and
its device. Also, the device itself
could be faulty or marginal.
Use the SSB menu to check FC
link status and SCSI device status.
An unusual number of
SCSI devices reset.
There could be a wide variety of
causes; for example, a SCSI
terminator could be missing.
Check the manual that came with
the SCSI device for possible
causes.
Check the SCSI hardware and
terminators. Check to see if the
host bus adapter includes on-
board termination and termination
power or if they must be supplied
externally.
Input/output performance
is slow.
Host system parameters may
need to be changed.
Fiber optic connections may be
damaged.
Refer to the manual that came with
the host FC adapter for
information on tuning parameters.
Replace cables.
The host sees path to
SSB but does not see
path to target and LUN.
Hardware (adapters, cables, etc.)
may be faulty or marginal.
Use the procedure listed on page
88.
The host does not
recognize the SSB or
targets and LUNs.
FC hardware is faulty. HP-UX
does not have FC driver or
updated FC driver. SSB is offline.
Use the procedures on pages 86
and 88.