If it is clear that a particular component system is at fault in a problem situation, go directly to that
component. If it is not clear, the best approach is to troubleshoot using the inside-out method.
You may check on the status of your iPBridge using
the ExpressNAV interface. Refer to
pages
on page 23 to see which pages may contain the
information you need. You may also look for
information by using the diagnostic CLI commands,
enumerated in
Diagnostic commands
the Advanced page of the ExpressNAV interface or by
Inside out method
To troubleshoot using the inside out method, begin with the device(s) connected to the iPBridge first, then work
your way out.
• SCSI devices
• iPBridge SCSI ports
•
iPBridge internal configuration
•
iPBridge Ethernet/IP ports
• LAN/WAN
• Ethernet host adapter or NIC in host
• iSCSI OS driver
Check the host event log
Check the event log on the host. Look for the most
recent entries and determine what could be causing a
Check the iPBridge event and trace logs
Check the iPBridge event log through the CLI. Refer
to
Diagnostic commands
most recent entries and determine what could be
Visually inspect LEDs
Light Emitting Diodes (LEDs) are located the back of
the iPBridge.
Check for problems on attached devices
Check the following in order to find problems on
attached devices:
• LEDs
23
ATTO Technology Inc. iPBridge Installation and Operation Manual
5 Troubleshooting
ExpressNAV
on page 43, in
• OS
• Application
on page 43. Look for the
using the CLI directly (refer to
based interface
on page 35).
To start and use the ExpressNAV interface, including
how to access the version information, refer to
ExpressNAV provides web-based interface
29.
problem, then go to that event and continue
troubleshooting.
causing a problem. Then go to that event and continue
troubleshooting.
Each SCSI bus has its own LED
the iPBridge is ready and blinks steadily when
there is SCSI activity.
• Display panels
• Firmware levels
• Operability
CLI provides ASCII-
on page
which lights when