Bug 514926

If this problem is specific to the bnx2i, then this is probably something we should release note in 5.4, and plan to fix in 5.5, considering the RHEL 5.4 schedule.

Here is a proposed release note:

Removing the bnx2 modules or running ifdown on the network interface being used by bnx2i, will result in the iSCSI sessions being disconnected. Reloading the module or running ifup, will not result in the SCSI sessions being reconnected. You must also stop the iscsi service, and then relogin by restarting the iscsi service.

Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
Removing the bnx2 modules or running ifdown on the network interface being used by bnx2i, will result in the iSCSI sessions being disconnected. Reloading the module or running ifup, will not result in the SCSI sessions being reconnected. You must also stop the iscsi service, and then relogin by restarting the iscsi service.

Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1 +1 @@
-Removing the bnx2 modules or running ifdown on the network interface being used by bnx2i, will result in the iSCSI sessions being disconnected. Reloading the module or running ifup, will not result in the SCSI sessions being reconnected. You must also stop the iscsi service, and then relogin by restarting the iscsi service.+Removing the <filename>bnx2</filename> modules or running ifdown on the network interface being used by <filename>bnx2i</filename> driver will result in the iSCSI sessions being disconnected. Reloading the module or running ifup, will not reconnect the SCSI sessions. To work around this issue, the iscsi service must be stopped and then restarted.

@Broadcom,

We need to confirm that there is commitment to test 
for the resolution of this request during the RHEL 5.5 test
phase, if it is accepted into the release. 

Please post a confirmation before Oct 16th, 2009, 
including the contact information for testing engineers.

Yes, adding QA managers Nasser and Eddie to assign test engineers.

Yes, bnx2i test engineer contact info is:

Emory Bestenlehner, emoryb, 949-926-6731

We will be posting test results when available periodically.

If there are any questions/problems, please contact me.

Ed Narvaez, enarvaez, 949-926-6456

You can also reach me via cell 714 366 1986, or my lab phone 949 926 8482. The above # is my office phone. Use these two numbers primarily, I'm rarely in my office.

Thanks

Quick update from Broadcom:
I was told that iscsi-initiator-utils-6.2.0.871-0.11.el5.x86_64.rpm along with kernel-2.6.18-178.el5.x86_64.rpm might fix this problem.  I tried the following combination and the iSCSI session still does not recover after an ifconfig down/up.

Ben,

Could Edward be hitting the same thing I was? Does the update here
http://people.redhat.com/mchristi/iscsi/rhel5.5/iscsi-initiator-utils/
work for you?

Hi Mike,

I tried the iscsi-utils located at the URL you posted, iscsi-initiator-utils-6.2.0.871-0.11.el5, and I think it might be a different problem.  I will work with Ed and Anil to see if we can narrow this down.

Thanks again.

OK, looks like this is waiting on Broadcom for more investigation. Correct me if I'm wrong here. Please keep us posted.

Yes, Broadcom engineering is debugging this.

Hey Ben,

I update the iscsi-initiator-utils rpm with your uip reopen con patch here
http://people.redhat.com/mchristi/iscsi/rhel5.4.z/iscsi-initiator-utils/

Hey, the rpm in comment #23 is for 5.4.z.

The rpm for 5.5 is here
http://people.redhat.com/mchristi/iscsi/rhel5.5/iscsi-initiator-utils/
It has your fixes plus bnx2x support and some other fixes.

Tried the initiator in comment #23 (iscsi-initiator-utils-6.2.0.871-0.12.el5) with the 5.4.z kernel and the issue appears to be resolved.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0293.html