Hi,
For those cards the bnx2i driver must be used whether you want to use
ISCSI offloading or not. To get ISCSI offloading working you need to be
running a custom version of bnx2i.
Dell supply their own custom version of the bnx2i driver (or at least
they did around the time of CentOS 5.3).
I experimented with this on Both CentOS and Red Hat. Initially when
contacting Dell I was told ISCSI offloading with a multipath
configuration in Linux was definitely possible. Then after a 3-4 months
of trial and failure the call was closed as Technically not possible. I
was told to wait for the release of Red Hat 6.
On 20/08/10 08:10, David wrote:
> Pardon my banter, after drinking some more coffee and waking up, I think
> I pretty much answered my own question....
>
> In this case, "not supported" MOST likely means not currently enabled
>
> I return you to a better program already in progress.....
>
> David
>
> On 08/19/2010 03:03 PM, David wrote:
>
>> Not supported by CentOS/RHEL or...?
>>
>> The adapters are Broadcom 5709 which are capable of hardware
>> offload/iSCSI HBA, though it isn't currently enabled (no key).
>>
>> Trying to rationalize why bnx2i is being invoked if hardware offload
>> isn't supported.
>>
>> David
>>
>> On 08/19/2010 02:44 PM, James Hogarth wrote:
>>
>>
>>> On 19 August 2010 20:39, David<david@xxxxxxxxxxxx> wrote:
>>>
>>>
>>>
>>>> Getting "bnx2i: iSCSI not supported, dev=eth0" for all the NIC adapters
>>>> on all of my R710's running CentOS 5.5.
>>>>
>>>> Here is an sample of the error messages:
>>>>
>>>> bonding: Warning: either miimon or arp_interval and arp_ip_target module
>>>> parameters must be specified, otherwise bonding will not detect link
>>>> failures! see bonding.txt for details.
>>>> bonding: bond0: setting mode to active-backup (1).
>>>> bonding: bond0: Setting MII monitoring interval to 500.
>>>> ADDRCONF(NETDEV_UP): bond0: link is not ready
>>>> bonding: bond0: Adding slave eth0.
>>>> bnx2: eth0: using MSIX
>>>> bnx2i: iSCSI not supported, dev=eth0
>>>> bonding: bond0: enslaving eth0 as a backup interface with a down link.
>>>> bnx2i: iSCSI not supported, dev=eth0
>>>> bonding: bond0: Adding slave eth2.
>>>> bnx2: eth2: using MSIX
>>>> bnx2i: iSCSI not supported, dev=eth2
>>>> bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex
>>>> bonding: bond0: enslaving eth2 as a backup interface with a down link.
>>>> bnx2i: iSCSI not supported, dev=eth2
>>>> bonding: bond0: link status definitely up for interface eth0.
>>>> bonding: bond0: making interface eth0 the new active one.
>>>> bonding: bond0: first active interface up!
>>>> bonding: bond0: link status definitely up for interface eth2.
>>>> ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
>>>> bonding: bond0: link status definitely down for interface eth2, disabling it
>>>> bnx2: eth2 NIC Copper Link is Up, 1000 Mbps full duplex
>>>> bonding: bond0: link status definitely up for interface eth2.
>>>> bond0: no IPv6 routers present
>>>>
>>>>
>>>> Understanding that bnx2i is used for hardware iscsi, why is this error
>>>> occurring?
>>>>
>>>> David
>>>> _______________________________________________
>>>> CentOS mailing list
>>>> CentOS@xxxxxxxxxx
>>>> http://lists.centos.org/mailman/listinfo/centos
>>>>
>>>>
>>>>
>>>>
>>> This was asked 2 or 3 days ago ... it refers to hardware offloading
>>> isn't supported I believe.
>>> _______________________________________________
>>> CentOS mailing list
>>> CentOS@xxxxxxxxxx
>>> http://lists.centos.org/mailman/listinfo/centos
>>>
>>>
>>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> http://lists.centos.org/mailman/listinfo/centos
>>
>>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
