702211 – [Broadcom 6.1] iscsi boot does not work when using broadcom nics and software iscsi

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 702211 - [Broadcom 6.1] iscsi boot does not work when using broadcom nics and software iscsi

Summary: [Broadcom 6.1] iscsi boot does not work when using broadcom nics and software...

Keywords:
Status:	CLOSED NOTABUG
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	dracut
Sub Component:
Version:	6.1
Hardware:	Unspecified
OS:	Unspecified
Priority:	urgent
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Harald Hoyer
QA Contact:	Release Test Team
Docs Contact:
URL:
Whiteboard:
Depends On:	696267
Blocks:	696275
TreeView+	depends on / blocked

Reported:	2011-05-05 05:10 UTC by Mike Christie
Modified:	2011-05-05 21:48 UTC (History)
CC List:	11 users (show)
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Clone Of:	696267
Environment:
Last Closed:	2011-05-05 21:48:48 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Comment 2 Mike Christie 2011-05-05 05:15:55 UTC

Hey Harold,

To sum up the problem:

Broadcom nics can do iscsi offload, but there are cases where users do not want to use the offload feature and instead want to use the normal nic (bnx2x or bnx2) + ibft + software iscsi (iscsi_tcp).

The problem is that when booting off the normal nic + ibft, iscsi_ibft does seem to get loaded. We see this in the boot up logs:

iscsi: registered transport (tcp)
FATAL: Module ibft not found.

Comment 4 Mike Christie 2011-05-05 05:56:48 UTC

Note:

I tried RHEL6.1-20110501.n.0-Server-x86_64 and it worked fine for me.

Broadcom is testing snap5.

I am not sure if there is a anaconda or dracut change since then.

Comment 5 Mike Christie 2011-05-05 06:04:14 UTC

Oh yeah Jamal,

I just wanted to confirm that when you do the install ibft is setup ok. So when the installer runs if the machine is setup for ibft, then it will automatically set up the targets/sessions based on the info found in ibft. You do not have to go the special storage devices section and manually add your target info.

Is anaconda setting things up using the ibft data found automatically for you or are you setting it up manually?

Also, some helpful debugging tips:

1. When installing, you can do "ctrl+F2" and drop into a shell. From there you can you look at /sys/firmware/ibft and confim it has the needed info. Or you can run "iscsistart -f" and it will print out the ibft info found in sysfs. Or you can run "iscsiadm -m fw" and that will also print out the ibft info.

2. You can add rdshell to the kernel command line and if the boot fails you will be dropped into a shell. From there you can run commands and search sysfs to do some debugging.

Comment 6 Harald Hoyer 2011-05-05 11:28:01 UTC

(In reply to comment #4)
> Note:
> 
> I tried RHEL6.1-20110501.n.0-Server-x86_64 and it worked fine for me.
> 
> Broadcom is testing snap5.
> 
> I am not sure if there is a anaconda or dracut change since then.

dracut changed! they should test the new version

Comment 8 Michael Chan 2011-05-05 15:54:29 UTC

(In reply to comment #6)
> dracut changed! they should test the new version

Is the new dracut in RC1?

Comment 9 Jamal Mir 2011-05-05 16:36:22 UTC

(In reply to comment #5)
> Oh yeah Jamal,
> I just wanted to confirm that when you do the install ibft is setup ok. So when
> the installer runs if the machine is setup for ibft, then it will automatically
> set up the targets/sessions based on the info found in ibft. You do not have to
> go the special storage devices section and manually add your target info.
> Is anaconda setting things up using the ibft data found automatically for you
> or are you setting it up manually?
> Also, some helpful debugging tips:
> 1. When installing, you can do "ctrl+F2" and drop into a shell. From there you
> can you look at /sys/firmware/ibft and confim it has the needed info. Or you
> can run "iscsistart -f" and it will print out the ibft info found in sysfs. Or
> you can run "iscsiadm -m fw" and that will also print out the ibft info.
> 2. You can add rdshell to the kernel command line and if the boot fails you
> will be dropped into a shell. From there you can run commands and search sysfs
> to do some debugging.

Everything was picked up from ibft automatically during first phase of installation. After I chose " Special Storage Devices" option and clicked NEXT, target was found automatically. The target found matched the one specified in ibft.

I am in the middle of trying RC1. I'll keep you posted.

Comment 10 Jamal Mir 2011-05-05 17:21:11 UTC

(In reply to comment #9)
> (In reply to comment #5)
> > Oh yeah Jamal,
> > I just wanted to confirm that when you do the install ibft is setup ok. So when
> > the installer runs if the machine is setup for ibft, then it will automatically
> > set up the targets/sessions based on the info found in ibft. You do not have to
> > go the special storage devices section and manually add your target info.
> > Is anaconda setting things up using the ibft data found automatically for you
> > or are you setting it up manually?
> > Also, some helpful debugging tips:
> > 1. When installing, you can do "ctrl+F2" and drop into a shell. From there you
> > can you look at /sys/firmware/ibft and confim it has the needed info. Or you
> > can run "iscsistart -f" and it will print out the ibft info found in sysfs. Or
> > you can run "iscsiadm -m fw" and that will also print out the ibft info.
> > 2. You can add rdshell to the kernel command line and if the boot fails you
> > will be dropped into a shell. From there you can run commands and search sysfs
> > to do some debugging.
> Everything was picked up from ibft automatically during first phase of
> installation. After I chose " Special Storage Devices" option and clicked NEXT,
> target was found automatically. The target found matched the one specified in
> ibft.
> I am in the middle of trying RC1. I'll keep you posted.


I am glad to report that non-HBA mode is now working in RH6.1 RC1. I was able to install and boot the iscsi boot image.

The HBA Mode problem will be tracked in BZ 701864. I will try the HBA Mode with RH6.1 RC1 and post finding in BZ701864.

Comment 11 Mike Christie 2011-05-05 21:48:48 UTC

Thanks Harold. Closing this bz.

Note You need to log in before you can comment on or make changes to this bug.