Michael Wolf wrote:
Only four of them are connected to the SAN. How to figure out which hw-
adress belongs to which interface?
Perhaps BIOS / iface's ROM util should give you some hint(s).
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To
On 03/09/2010 01:49 PM, Hoot, Joseph wrote:
I had a similar issue, just not using bonding. The gist of my problem was
that, when connecting a physical network card to a bridge, iscsiadm will not
login through that bridge (at least in my experience). I could discover just
fine, but wasn't
Hi everybody,
Just wondering if anybody's got any experience with the bonding driver
(and LACP on the switch) used as an iSCSI path? OK? Don't do
it!? Yes, but...?
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send
, separate switches and DM-Multipath would give you
the same thing, only all the way through to the SAN.
Den 3 Dec, 2009 kl. 12:04 skrev Ciprian Marius Vizitiu (GBIF):
Hi everybody,
Just wondering if anybody's got any experience with the bonding driver
(and LACP on the switch) used
Hi everybody,
Is there a list with all the iferror codes and their meaning? I'm trying
to use bnx2i on RHEL 5.4 in order to do iSOE on a Dell M610 and a EQL
PS6000XV and from time to time I get iferror -1.
--~--~-~--~~~---~--~~
You received this message because
The iferror values are just normal old errnos. -1 is
#define EPERM1 /* Operation not permitted */
You should get the iferror translated to a string in
/var/log/messages.
[...]
Ignore this last part about the log message. The printf and
iferror use
is broken.
