User’s Guide IOCTL to Open-iSCSI Interface QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters IS0054604-00 A
User’s Guide—IOCTL to Open-iSCSI Interface QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters Information furnished in this manual is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice.
Table of Contents Preface What is in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . .
User’s Guide—IOCTL to Open-iSCSI Interface QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters Boot Target Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Behavior on RHEL 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . Default Behavior on SLES 11 SP2 . . . . . . . . . . . . . . . . . . . . . . . Persistence through Flash and Open-iSCSI Database . . . . . . . . . . . . Managing QLogic iSCSI Adapters Using iscsiadm . . . . . . .
User’s Guide—IOCTL to Open-iSCSI Interface QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters 1-5 1-6 1-7 1-8 1-9 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 2-12 2-13 2-14 2-15 2-16 2-17 2-18 2-19 2-20 2-21 2-22 2-23 2-24 2-25 2-26 2-27 2-28 2-29 2-30 2-31 2-32 2-33 2-34 2-35 2-36 2-37 2-38 2-39 2-40 Open-iSCSI Target Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IOCTL Session Recovery. . . . . . . . . . . . . . . . . . . . . .
User’s Guide—IOCTL to Open-iSCSI Interface QLogic 4000 Series iSCSI Adapters and 8200 Series Converged Network Adapters 2-41 2-42 2-43 Selecting the Installation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation in Progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Starting with Red Hat® Enterprise Linux® (RHEL™) 6.2 and Novell® SUSE® Linux Enterprise Server (SLES®) 11 SP2, the QLogic qla4xxx driver (iSCSI driver for Linux) supports the Open-iSCSI tool iscsiadm. As a result, iscsiadm can now be used to perform management functions (configuring network settings, managing iSCSI targets, and so on) on QLogic 4000 Series 1GbE iSCSI Adapters and 8200 Series 10GbE Converged Network Adapters.
Preface Related Materials Related Materials For additional information, refer to the following: Technical Note, 2.10. Kernel http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.2_T echnical_Notes/kernel_issues.html Release Notes for SUSE Linux Enterprise Server 11 Service Pack 2 http://www.novell.com/linux/releasenotes/i386/SUSE-SLES/11-SP2/ Linux Open-iSCSI README http://www.open-iscsi.
Preface Technical Support Text in italics indicates terms, emphasis, variables, or document titles: For a complete listing of license agreements, refer to the QLogic Software End User License Agreement. What are shortcut keys? To enter the date type mm/dd/yyyy (where mm is the month, dd is the day, and yyyy is the year).
Preface Technical Support Training QLogic Global Training maintains a Web site at www.qlogictraining.com offering online and instructor-led training for all QLogic products. In addition, sales and technical professionals may obtain Associate and Specialist-level certifications to qualify for additional benefits from QLogic. Contact Information QLogic Technical Support for products under warranty is available during local standard working hours excluding QLogic Observed Holidays.
1 Legacy vs. Open-iSCSI This section describes the major differences between the legacy driver which has an IOCTL-based interface for user space application communications, and the Open-iSCSI model.
1–Legacy vs. Open-iSCSI Summary of Major Differences Summary of Major Differences Table 1-1 summarizes the major differences between the legacy IOCTL-based and Open-iSCSI models. Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models Serial No. 1 Feature Firmware Operational Mode IOCTL-based Driver Open-iSCSI-based Driver Firmware is configured in AUTO CONNECT MODE. In this mode: Firmware is configured in NON AUTO CONNECT MODE.
1–Legacy vs. Open-iSCSI Summary of Major Differences Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued) Serial No. 3 Feature Boot Target IOCTL-based Driver Open-iSCSI-based Driver Remarks During driver load, the firmware performs auto discovery and login to the boot targets based on the target information saved in the Flash, and posts an AEN to inform the driver of the targets and their login status.
1–Legacy vs. Open-iSCSI Summary of Major Differences Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued) Serial No. 6 Feature IOCTL-based Driver Open-iSCSI-based Driver How to view sessions logged in Qlogic applicationa 7 Target scanning Login and target scanning Login and target scanning is is done in kernel space as done by user space as follows: follows: 1. When the driver receives 1.
1–Legacy vs. Open-iSCSI Summary of Major Differences Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued) Serial No. 9 Feature IOCTL-based Driver Open-iSCSI-based Driver Dynamic mapping/unmapping of LUNs added to the back-end storage The driver handles the following check condition/sense data: 10 Tearing Down Session/Connection objects The session object can be destroyed using QLogic applicationsa The session object lifecycle is completely determined by Open-iSCSI.
1–Legacy vs. Open-iSCSI Summary of Major Differences Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued) Serial No. 12 1-6 Feature Flash DDBs with Open-iSCSI model driver IOCTL-based Driver Not applicable Open-iSCSI-based Driver The Open-iSCSI driver will support existing Flash DDB entries in the adapter. iscsiadm has no control over these sessions. Session management of Flash DDB entries is done by the driver itself.
1–Legacy vs. Open-iSCSI Functional Flows Table 1-1. Differences Between IOCTL and Open-iSCSI Driver Models (Continued) Serial No. 13 Feature CHAP IOCTL-based Driver Open-iSCSI-based Driver Remarks CHAP settings are applied using the QLogic applicationa. With CHAP support in iscsiadm, CHAP entries can now be added, deleted, and listed from the user space.
1–Legacy vs. Open-iSCSI Functional Flows Discovery Figures 1-1 through 1-3 provide functional flow diagrams of the discovery process for IOCTL and Open-iSCSI. Figure 1-1. Noninteractive Discovery in IOCTL Mode (Legacy) Figure 1-2.
1–Legacy vs. Open-iSCSI Functional Flows Figure 1-3.
1–Legacy vs. Open-iSCSI Functional Flows Target Login Figures 1-4 through 1-5 provide functional flow diagrams of the target login process for IOCTL and Open-iSCSI. Figure 1-4. IOCTL iSCSI Target Login Figure 1-5.
1–Legacy vs. Open-iSCSI Functional Flows Session Recovery Figures 1-6 through 1-7 provide functional flow diagrams of the session recovery process for IOCTL and Open-iSCSI. Figure 1-6.
1–Legacy vs. Open-iSCSI Functional Flows Figure 1-7.
1–Legacy vs. Open-iSCSI State Transition Diagrams State Transition Diagrams Figures 1-8 through 1-9 provide state transition diagrams for IOCTL and Open-iSCSI. These diagrams illustrate the management of the session/target life cycle. Figure 1-8.
1–Legacy vs. Open-iSCSI State Transition Diagrams Figure 1-9.
2 Boot from SAN This section provides information on configuring Boot from SAN (BFS) when migrating to the Open-iSCSI model. This section includes the following topics: IS0054604-00 A “New Parameter: ql4disablesysfsboot” on page 2-2 “Boot from SAN Configuration Matrix” on page 2-2 “Configuring Boot from SAN” on page 2-4 “Configuring Boot from SAN on RHEL 6.
2–Boot from SAN New Parameter: ql4disablesysfsboot New Parameter: ql4disablesysfsboot The ql4disablesysfsboot parameter is a new driver module parameter for the Open-iSCSI based driver model (it is not supported by the ioctl based driver). This parameter controls the behavior of boot target login in the Open-iSCSI base driver, which provides two ways to log in to the boot targets.
2–Boot from SAN Boot from SAN Configuration Matrix Table 2-1. Boot from SAN Configuration Matrix ql4xdisablesysfsboot = 0 Boot Target as sendtarget (ST) Export boot target through sysfs (/sys/firmware/ iscsi_bootx/ where x is 1, 2,...) The Boot Target will be exported through sysfs (with IP address and port only) Note: If the iSCSI BIOS login is disabled, the entry made at the boot index will not be exported to sysfs.
2–Boot from SAN Configuring Boot from SAN Configuring Boot from SAN Boot from SAN Installation on SLES 11 SP2 and RHEL 6.2 To configure the adapter for BFS on SLES 11 SP2 or RHEL 6.2, follow these steps: 1. While the system is booting up, press CTRL+Q to enter Fast!UTIL on the iSCSI BIOS banner, as shown in Figure 2-1. Figure 2-1.
2–Boot from SAN Configuring Boot from SAN 2. Once in, select the port to be configured, as shown in Figure 2-2. Figure 2-2. Selecting the Port to Be Configured 3. Select Configuration Settings, as shown in Figure 2-3. Figure 2-3.
2–Boot from SAN Configuring Boot from SAN 4. Select Host Adapter Settings, as shown in Figure 2-4. Figure 2-4. Selecting the Host Adapter Settings Option 5. Select the Initiator IP Settings field, as shown in Figure 2-5. Figure 2-5.
2–Boot from SAN Configuring Boot from SAN 6. Provide the initiator IP address, as shown in Figure 2-6. Figure 2-6. Providing the Initiator IP Address 7. Press ESC repeatedly until the screen shown in Figure 2-7 appears. Then, select the iSCSI Boot Settings option. Figure 2-7.
2–Boot from SAN Configuring Boot from SAN 8. Select Primary Boot Device Settings, as shown in Figure 2-8. Figure 2-8. Selecting Primary Boot Device Settings 9. Provide the target IP address, as shown in Figure 2-9. Figure 2-9.
2–Boot from SAN Configuring Boot from SAN 10. Select Alternate Boot Device Settings, as shown in Figure 2-10. Figure 2-10. Selecting Alternate Boot Device Settings 11. Provide the target IP address, as shown in Figure 2-11. Figure 2-11.
2–Boot from SAN Configuring Boot from SAN 12. Press ESC until the menu in Figure 2-12 appears. Select Reinit Adapter to save all IP settings. Figure 2-12. Fast!UTIL Options 13. In iSCSI Boot Settings, select Primary (LUN), as shown in Figure 2-13. Figure 2-13.
2–Boot from SAN Configuring Boot from SAN 14. A list of the port’s devices is displayed, as shown in Figure 2-14. Select the device to be used as the boot device and press ENTER. Figure 2-14. List of Devices on the Port 15. Repeat steps 13–14 to edit the alternate boot device setting, as in Figure 2-15. Figure 2-15.
2–Boot from SAN Configuring Boot from SAN 16. Change the adapter’s boot mode to Manual, as Figure 2-16 shows. Figure 2-16. Setting the Boot Mode to Manual 2-12 17. 18. Save the settings for the port. Repeat steps 2–14, but select the second port, and configure the boot targets on the port. 19. Save the settings and reboot the system with the installation disk.
2–Boot from SAN Configuring Boot from SAN Boot from SAN Installation on SLES 11 SP2 To configure the adapter for BFS on SLES 11 SP2, follow these steps: 1. Boot from the SLES 11 SP2 DVD, as shown in Figure 2-17. Figure 2-17. Entering the Boot BIOS 2. Provide the withiscsi=1 boot option, as shown in Figure 2-18. Figure 2-18.
2–Boot from SAN Configuring Boot from SAN 3. The Welcome screen appears, as shown in Figure 2-19. Follow the instructions on this screen to begin the installation. Figure 2-19. Installation Welcome Screen 4. Complete the installation by following the instructions on all subsequent screens, as shown in Figures 2-20 through 2-27. Figure 2-20.
2–Boot from SAN Configuring Boot from SAN Figure 2-21. iSCSI Initiator Overview Figure 2-22.
2–Boot from SAN Configuring Boot from SAN Figure 2-23. Selecting the Installation Mode Figure 2-24.
2–Boot from SAN Configuring Boot from SAN Figure 2-25. Selecting the Server Base Scenario Figure 2-26.
2–Boot from SAN Configuring Boot from SAN Figure 2-27. Performing the Installation 5. 2-18 When the installation is completed, reboot the system and boot from the iSCSI adapter.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 Configuring Boot from SAN on RHEL 6.2 Installing RHEL 6.2 To install RHEL 6.2, follow these steps: 1. Boot from the installation media, as shown in Figure 2-28. Figure 2-28. Booting From the Installation Media 2. Choose either to test the media disk or skip the test, as Figure 2-29 shows. Figure 2-29.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 3. Select the network interface through which the installation is to be done, as Figure 2-30 shows. Figure 2-30. Selecting Network Interface for Installation 4. Configure the IP address either statically or using, as Figure 2-31 shows. Figure 2-31.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 5. Once the network interface is configured, the installation starts, as shown in Figure 2-32. Figure 2-32. Start of RHEL 6.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 6. Select the language to use during the installation, as shown in Figure 2-33. Figure 2-33.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 7. Select the type of keyboard that is connected to your system, as shown in Figure 2-34. Figure 2-34.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 8. Select one the two options shown in Figure 2-35: Basic Storage Devices or Specialized Storage Devices. You may select either option since the LUN has been added in the adapter’s BIOS. Figure 2-35.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 9. Select the disk that was added in the adapter’s BIOS and verify that it has two paths to it, as shown in Figure 2-36. Figure 2-36.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 10. Enter the host name, as shown in Figure 2-37. Figure 2-37.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 11. Select the time zone, as shown in Figure 2-38. Figure 2-38.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 12. Enter the root credentials that you want to set for the system, as shown in Figure 2-39. Figure 2-39.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 13. Select the type of partition layout you want, as shown in Figure 2-40. Figure 2-40.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 14. Select the type of installation, as shown in Figure 2-41. Figure 2-41.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 15. The installer creates the partitions on the disk and begins to copy files to it, as shown in Figure 2-42. Figure 2-42.
2–Boot from SAN Configuring Boot from SAN on RHEL 6.2 16. Once the files have been copied, the installer will prompt you to reboot the machine, as shown in Figure 2-42. Figure 2-43.
2–Boot from SAN ql4xdisablesysfsboot Settings and Adapter Boot Mode ql4xdisablesysfsboot Settings and Adapter Boot Mode This section demonstrates the effect of the ql4xdisablesysfsboot parameter under different adapter boot modes. NOTE For target discovery and login to work, the adapter’s IP address must be configured using either BIOS settings or iscsiadm. The following examples show the iscsiadm commands to use to set the IP address. # iscsiadm -m iface -I qla4xxx.00:c0:dd:07:59:f2.ipv4.0 -n iface.
2–Boot from SAN ql4xdisablesysfsboot Settings and Adapter Boot Mode Table 2-2. Configurations and Tools for Checking iSCSI Sessions (Continued) No. 2 Configuration Target info Non-Boot No target from SAN a info is in the firmware ql4xdisable Adapter Boot iscsiadm command sysfsboot Mode 1 or 0 Disable Use iscsiadm for discovery and login to targets. The correct qla4xxx iface must be used.
3 Open-iSCSI User’s Guide This section provides a User’s Guide for Open-iSCSI.
3–Open-iSCSI User’s Guide Open-iSCSI Supported Features Open-iSCSI Supported Features Open-iSCSI support has been added to the QLogic iSCSI driver in Red Hat Enterprise Linux 6.2 and SUSE Linux Enterprise Server 11 Service Pack 2. Open-iSCSI infrastructure supports discovery, login to and logout from iSCSI targets, and modification and display of iSCSI configuration parameters. The QLogic iSCSI driver provides persistence through Flash and Open-iSCSI nodes and sendtargets databases.
3–Open-iSCSI User’s Guide Open-iSCSI Supported Features NOTE Refer to the following Red Hat Technical Note about issues and workarounds when upgrading from RHEL 6.1 to RHEL 6.2: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.2_T echnical_Notes/kernel_issues.html Default Behavior on SLES 11 SP2 Open-iSCSI is enabled by default on SLES 11 SP2 and login to boot targets is triggered by iscsiadm during installation.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm Managing QLogic iSCSI Adapters Using iscsiadm iSCSI Configuration Files and Persistent Databases The Open-iSCSI daemon iscsid can be configured to use the default node configuration and persistent database to automatically start discovery on startup. Table 3-1 lists the configuration and persistent database files for SLES 11 SP2 and RHEL6.2. Table 3-1.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm 2. Discover the iSCSI target. # iscsiadm -m discovery -t st -p 192.168.1.11 -I qla4xxx.00:0e:1e:05:38:42.ipv4.0 192.168.1.11:3260,1 iqn.1992-04.com.emc:cx.ckm00101200392.a2 192.168.1.8:3260,3 iqn.1992-04.com.emc:cx.ckm00101200392.a3 192.168.1.12:3260,2 iqn.1992-04.com.emc:cx.ckm00101200392.b2 192.168.1.9:3260,4 iqn.1992-04.com.emc:cx.ckm00101200392.b3 3. List all discovered targets. # iscsiadm -m node 192.168.1.8:3260,3 iqn.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm iSCSI Interface Configuration iSCSI Configuration Parameters Each iSCSI Host Bus Adapter, NIC, or network interface to which sessions are bound should have its own iSCSI interface config file in /etc/iscsi/ifaces. For hardware offload iSCSI, iscsiadm creates ifaces for QLogic iSCSI ports. Before the iface can be used, the IP address for the port must be set as shown in “Update iface Network Parameters” on page 3-9.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm Example: IPv4 sample config file with static IP address # BEGIN RECORD 2.0-872 iface.iscsi_ifacename = qla4xxx-3 iface.ipaddress = 192.168.1.75 iface.hwaddress = 00:0e:1e:04:93:92 iface.transport_name = qla4xxx iface.bootproto = static iface.subnet_mask = 255.255.255.0 iface.gateway = 192.168.1.1 iface.state = enable iface.vlan = iface.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm Display iface Configuration Details # iscsiadm -m iface -I Example: # iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 # BEGIN RECORD 2.0-872.28.el6-1031 iface.iscsi_ifacename = qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 iface.net_ifacename = iface.ipaddress = 192.168.2.214 iface.hwaddress = 00:c0:dd:0b:13:f1 iface.transport_name = qla4xxx iface.initiatorname = iface.bootproto = iface.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm Example: # iscsiadm -m iface -I qla4xxx-4 # BEGIN RECORD 2.0-872 iface.iscsi_ifacename = qla4xxx-4 iface.net_ifacename = iface.ipaddress = iface.hwaddress = iface.transport_name = qla4xxx iface.initiatorname = iface.bootproto = iface.subnet_mask = iface.gateway = iface.ipv6_autocfg = iface.linklocal_autocfg = iface.router_autocfg = iface.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm Example: IPv4 Settings (static) # iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 -o update -n iface.ipaddress -v 192.168.2.214 qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 updated. # iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 -o apply qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 applied. Example: IPv4 Settings (DHCP) # iscsiadm -m iface -I qla4xxx.00:c0:dd:0b:13:f1.ipv4.0 -o update -n iface.bootproto -v dhcp qla4xxx.00:c0:dd:0b:13:f1.ipv4.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm NOTE The target should be logged out before updating the network parameters. iscsiadm will give the following warning if a network parameter of an iface with active sessions is updated: iscsiadm: Updating iface while iscsi sessions are using it. You must logout the running sessions then log back in for the new settings to take affect. Unidirectional and Bidirectional CHAP settings # iscsiadm -m node -p 192.168.1.84:3260 -T iqn.2011.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm Target Discovery Discover Targets using sendtarget # iscsiadm -m discovery -t st -p -I -o new, delete, update, nonpersistent In discovery mode, iscsiadm will use the iscsid.conf discovery settings and overwrite the discovery record settings with it. By default, it will remove records for portals not returned.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm Adding a New discoverydb for sendtarget # iscsiadm -m discoverydb -t st -p 192.168.2.105 -I qla4xxx-3 -o new New discovery record for [192.168.2.105,3260] added. # cat /var/lib/iscsi/send_targets/192.168.2.105,3260/st_config # BEGIN RECORD 2.0-872.28.el6-1031 discovery.startup = manual discovery.type = sendtargets discovery.sendtargets.address = 192.168.2.105 discovery.sendtargets.port = 3260 discovery.sendtargets.auth.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm # cat /var/lib/iscsi/send_targets/192.168.2.105,3260/st_config # BEGIN RECORD 2.0-872.28.el6-1031 discovery.startup = manual discovery.type = sendtargets discovery.sendtargets.address = 192.168.2.105 discovery.sendtargets.port = 3260 discovery.sendtargets.auth.authmethod = CHAP discovery.sendtargets.auth.username = joe discovery.sendtargets.auth.password = secret discovery.sendtargets.timeo.login_timeout = 15 discovery.sendtargets.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm List All Targets # iscsiadm -m node Example: # iscsiadm -m node 192.168.2.105:3260,1 iqn.2001-05.com.equallogic:0-8a0906-32e33fe02-517000ecd724ea83-karen-1 192.168.2.105:3260,1 iqn.2001-05.com.equallogic:0-8a0906-eddd93203-dc1000ece454e721-karen-2 192.168.2.105:3260,1 iqn.2001-05.com.equallogic:0-8a0906-ef8d93203-e99000ece484e721-karen-3 192.168.2.105:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f16d93203-92d000ece4b4e721-karen-4 192.
3–Open-iSCSI User’s Guide Managing QLogic iSCSI Adapters Using iscsiadm Login to All Targets Not specifying the target name, portal, and iface name results in login to all portals on all nodes/targets through each interface specified in the node configuration.
3–Open-iSCSI User’s Guide Features Not Supported NOTE If targets are logged in through Open-iSCSI, all targets should be logged out before unloading the QLogic iSCSI driver, otherwise driver unload will fail with the following error: ERROR: Module qla4xxx is in use Features Not Supported The features below are not supported in Red Hat Enterprise Linux 6.2. These features will be supported in Red Hat Enterprise Linux 6.3. 1. iSNS 2.
3–Open-iSCSI User’s Guide Linux Open-iSCSI README Linux Open-iSCSI README Go to http://www.open-iscsi.org/docs/README for more detailed information about Linux Open-iSCSI.
4 Known Issues This section lists currently known issues and provides a brief explanation of each issue. QLogic Application Limitations The RHEL 6.2 and SLES 11 SP2 inbox drivers do not support the following QLogic applications: iscli (SANsurfer iSCSI CLI) qaucli (QConvergeConsole CLI) The QLogic iSCSI driver and firmware handle discovery and login to targets in Flash and also export them to sysfs where they can be viewed. Target entries that have been made persistent in Flash on RHEL 6.
4–Known Issues CHAP Limitations 4-2 IS0054604-00 A
Corporate Headquarters QLogic Corporation 26650 Aliso Viejo Parkway Aliso Viejo, CA 92656 949.389.6000 www.qlogic.com International Offices UK | Ireland | Germany | France | India | Japan | China | Hong Kong | Singapore | Taiwan © 2012 QLogic Corporation. Specifications are subject to change without notice. All rights reserved worldwide. QConvergeConsole, QLogic, the QLogic logo, and SANsurfer are registered trademarks of QLogic Corporation. Linux is a registered trademark of Linus Torvalds.
