Hide Forgot
Description of problem: Booting a server with 2 HBAs, each HBA is configured to boot via 1 target. After boot the server has 2 sessions, one to each target. iscsiadm -m session -P1 Target: iqn.1992-08.com.netapp:sn.151753773 Current Portal: 10.16.41.222:3260,1 Persistent Portal: 10.16.41.222:3260,1 ********** Interface: ********** Iface Name: be2iscsi.00:00:c9:a0:e9:09 Iface Transport: be2iscsi Iface Initiatorname: iqn.1994-05.com.redhat:be2iscsi-storageqe-02 Iface IPaddress: <empty> Iface HWaddress: 00:00:c9:a0:e9:09 Iface Netdev: <empty> SID: 1 iSCSI Connection State: LOGGED IN iSCSI Session State: LOGGED_IN Internal iscsid Session State: NO CHANGE Current Portal: 10.16.43.127:3260,1 Persistent Portal: 10.16.43.127:3260,1 ********** Interface: ********** Iface Name: be2iscsi.00:00:c9:a0:e9:0b Iface Transport: be2iscsi Iface Initiatorname: iqn.1994-05.com.redhat:be2iscsi-storageqe-02 Iface IPaddress: <empty> Iface HWaddress: 00:00:c9:a0:e9:0b Iface Netdev: <empty> SID: 2 iSCSI Connection State: LOGGED IN iSCSI Session State: LOGGED_IN Internal iscsid Session State: NO CHANGE Although, firmware discovered another target to each HBA, these 2 targets are not connected after boot. iscsiadm -m discovery -P1 SENDTARGETS: No targets found. iSNS: No targets found. STATIC: No targets found. FIRMWARE: Target: iqn.1992-08.com.netapp:sn.151753773 Portal: 10.16.41.222:3260,1 Iface Name: be2iscsi.00:00:c9:a0:e9:09 Iface Name: be2iscsi.00:00:c9:a0:e9:0b Portal: 10.16.43.127:3260,1 Iface Name: be2iscsi.00:00:c9:a0:e9:09 Iface Name: be2iscsi.00:00:c9:a0:e9:0b Then these 2 targets can be logged in manually. iscsiadm -m node -l Logging in to [iface: be2iscsi.00:00:c9:a0:e9:0b, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.41.222,3260] (multiple) Logging in to [iface: be2iscsi.00:00:c9:a0:e9:09, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.43.127,3260] (multiple) Login to [iface: be2iscsi.00:00:c9:a0:e9:0b, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.41.222,3260] successful. Login to [iface: be2iscsi.00:00:c9:a0:e9:09, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.43.127,3260] successful. Version-Release number of selected component (if applicable): rpm -q iscsi-initiator-utils iscsi-initiator-utils-6.2.0.873-6.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.Configure server with 2 HBAs to connect to a NetApp target with 2 portals. 2.Boot the server up and check how many sessions are online 3.execute "iscsiadm -m node -l" 4.check if more session got connected.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Is this because the iSCSI boot sessions are not set to startup automatically? # iscsiadm -m session -r 1 # BEGIN RECORD 6.2.0-873.10.el6 node.name = iqn.1992-08.com.netapp:sn.151753773 node.tpgt = 1 node.startup = manual node.leading_login = No iface.hwaddress = 00:00:c9:a0:e9:09 iface.ipaddress = <empty> iface.iscsi_ifacename = be2iscsi.00:00:c9:a0:e9:09 iface.net_ifacename = <empty> iface.transport_name = be2iscsi ----- # iscsiadm -m fw # BEGIN RECORD 6.2.0-873.10.el6 iface.initiatorname = iqn.1994-05.com.redhat:be2iscsi-storageqe-02 iface.transport_name = be2iscsi iface.hwaddress = 00:00:c9:a0:e9:09 iface.bootproto = STATIC node.name = iqn.1992-08.com.netapp:sn.151753773 node.conn[0].address = 10.16.41.222 node.conn[0].port = 3260 # END RECORD # BEGIN RECORD 6.2.0-873.10.el6 iface.initiatorname = iqn.1994-05.com.redhat:be2iscsi-storageqe-02 iface.transport_name = be2iscsi iface.hwaddress = 00:00:c9:a0:e9:0b iface.bootproto = STATIC node.name = iqn.1992-08.com.netapp:sn.151753773 node.conn[0].address = 10.16.43.127 node.conn[0].port = 3260 # END RECORD
(In reply to Bruno Goncalves from comment #3) > Is this because the iSCSI boot sessions are not set to startup automatically? Looks like it. You're able to see all four node listings as being firmware discovered, which means that the firmware discovery command was run to copy the information out to a node listing in the DB. If they're set for manual login, then the active boot sessions are recovered but target portals that were discovered through firmware but aren't active are not logged in. In this case the boot firmware is configured to log into two target portals on two different HBAs. Because the target portals are part of the same target portal group, each HBA is likely discovering both portals but logging into only the one it's configured for. That matches the configuration once the OS is up as well. The problem may be that FW discovery isn't taking the default node.startup setting from /etc/iscsi/iscsid.conf.
cc
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/