Support

The Linux SCSI Target Wiki

These are the instructions for getting support for LIO Target and the Core-iSCSI initiator. Please collect and report debugging context and information as described below to help the developers finding and fixing the problem.

Contents 1 Contact 2 RTS OS 2.1 Support tool 2.2 Other 2.3 Initiator info 2.3.1 Windows 2.3.2 Linux 2.4 Source code 3 LIO Target 4 Core-iSCSI 4.1 Configuration 4.2 Logs 4.3 Debug output 5 See also 6 External links

Contact

• Please post your comments, questions or bug reports here:
  • For the Target or targetcli: the target-devel mailing list (post, subscribe, list info, gmane archive)
  • For the Initiator: the Core-iSCSI mailing list
  • For general SCSI: the linux-scsi mailing list
  • For the Linux kernel: the Linux Kernel mailing list (archive)
• Please contact RTS to obtain an RTS OS eval version, subscription or support with an SLA:
  • Phone (US): +1.650.384.6366 (US)
  • Phone (EMEA): +49.172.7277920 (EMEA)
  • Email: support@risingtidesystems.com
  • Web: risingtidesystems.com
• Please contact support@risingtidesystems.com if you have any questions regarding the RTS OS source code.

RTS OS

Support tool

For licensed RTS OS copies, run the following command as root, and follow the instructions:

# rts-support

Other

• If the system is locking or crashing, get the output from the console via the serial console.
• If the problems are related to iSCSI, collect iSCSI network traffic with Wireshark or Ethereal, where possible.

Initiator info

Windows

Obtain the exact Windows version and service pack.

Linux

Obtain the exact distribution info:

# cat /etc/issue

Obtain the exact system info and kernel version:

# uname -a

Source code

Please contact support@risingtidesystems.com if you have any questions regarding the RTS OS source code.

LIO Target

For LIO Target, the debug information needs to be captured manually. Here are the most important pieces.

• Get the versions of the modules and user space code (where applicable).
• Get the information in the configuration files for the system and Target:
  • /etc/issue
• Get the exact kernel version and system info:

# uname -a

• Get the PCI device info:

# lspci -vvv

• Get the output from /var/log/messages:

# dmesg

• If the system is locking or crashing, get the output from the console via the serial console.
• If the problems are related to iSCSI, collect iSCSI network traffic with Wireshark or Ethereal, where possible.

Core-iSCSI

Configuration

• Get the versions of the modules and user space code (where applicable).
• Get the information in the configuration files for Core-iSCSI & the Core-iSCSI tools:
  • /etc/sysconfig/initiator
  • /etc/sysconfig/iscsi_device_maps
  • /etc/sysconfig/initiator_auth

Logs

• If the system is having non-fatal isses with iSCSI (i.e.: the module can be unloaded), then get the output from /var/log/messages:

# dmesg

• If the system is locking or crashing, get the output from the console via the serial console.
• Where possible, collect iSCSI network traffic with Wireshark or Ethereal.

Debug output

Enable debugging output for Core-iSCSI:

DEBUG_ISCSI = 1 core-iscsi-vx.x.x.x/MCONFIG

If the resulting verbosity is insufficient, recompile Core-iSCSI:

1. Enable additional debugging sections in iscsi_debug.h
2. Compile, shutdown, install and restart to enable the changes

See also

• Using targetcli
• Downloading and installing
• Background on the Unified Target and Core-iSCSI
• CentOS, Debian, Fedora, openSUSE, RHEL, Scientific Linux, SLES, Ubuntu

External links

• Relevant RTS OS source code
• Wireshark network protocol analyzer
• Ethereal network protocol analyzer
• Open-iSCSI mailing list
• IET problem report