Possible Problems And Recommended Corrective Actions - D-Link DSN-5410-10 - xStack Storage Area Network Array Hard Drive Software Manual

Click on each link to download the diagnostic capture file(s) to your local host system. You
can then send the file(s) to the Technical Support staff at D-Link. For more information
about how to contact Technical Support and send them the file, please refer to the Contact
Information section in the Preface of this guide.

10.2 Possible Problems and Recommended Corrective Actions

Table 10-1 lists some problem symptoms, probable causes, and recommended corrective
actions. Some symptoms may appear as error messages in the D-Link Management Center or
as Warning or Error entries in the Event History Log. Other symptoms may be a requested
operation that failed to occur as expected. Please refer to the information in this table as
an aid before contacting D-Link for further assistance.
Problem Symptom
Unable to Bind
Target is not found
by an iSCSI initiator
xStack Storage Management Center Software User's Guide
Figure 10-3. Diagnostic Capture Download Page
Table 10-1. Problems and Corrective Actions
Description and Probable Cause
For DSN-5000 series dual-controller
systems, the controllers were unable to
Bind because of a mismatch of controller
attributes or some other unexpected
system error condition.
The iSCSI initiator is unable to detect the
iSCSI target on the specified IP address.
This could be caused by the lack of
network connectivity between your host
and the xStack Storage system, by an
improperly configured network portal, or
by insufficient initiator access for the
volume.
Recommended Corrective Actions
Refer to the description for this condition in the Main
Display of the System Administration View, and
correct the problem that appears there.
Verify that a valid IP address has been specified for
the network portal in the Network Settings View.
Verify that the appropriate iSCSI initiator access has
been granted to the volume in the Volume View.
Verify that the network portal IP address has been
correctly specified in the initiator.
Verify that you can ping the initiator host from the
network portal in the Network Settings View.
129