Am 19.12.2016 um 14:49 schrieb Udo Grabowski (IMK):
As said, we've not confifured any pathes, it finds two, but there's really
only one single physical connection, the e1000g network device. I don't
see how it gets two pathes out of that (something strange in scsi_vhci ?).
There is also a global property in /kernel/drv/iscsi.conf afaik.
mpxio-disable is the name of the property.

Maybe there is also a Way to push the first ISCSI Connection after
that network
reconnect. I once had a Crashed ISCSI Client that did not want to Log
into the
Target because the Target still thought the client was connected. So I
had to
kick the Client on the Target Side.

But how if you don't get any access ? Tried with -kd, but ::prtconf
in the kernel debugger only freezes because it looses the network.

With svcprop from a live image with the -f argument or still on the Original.

Also tried to use the volume as a disk on a different machine, and
boot from it with qemu-kvm ... -hda=/dev/rdsk/cxtyd0s0, but it freezes
already when reading the grub menu, that seems not to work like a
usual disk.
ISCSI is a special case in qemu http://wiki.qemu.org/download/qemu-doc.html#disk_005fimages_005fiscsi

It sounds like the following happens:
Boot
Network gets configured(with parameters from ipxe?)
ISCSI Connection to rpool
Root switch to rpool and start of startd from rpool
DHCP Client starts from Root Disk and reconfigures Networking(network:physical?)
ISCSI looses connection due to reconnect.

I see the following options:
- Increase ISCSI Timeout so that the connection does not get dropped during reconnect.
- Disable the Second Network Configuration.
- Dont give values via ipxe (if done) and tell the boot archive to use dhcp for IP. This schould hopefully not cause a reconnect when dhcpclient starts as it should get a NOOP Answer from DHCP. (I can't recall what that package is called but basicly it tells the Client IP Already requested from you)

Greetings
Till

_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Reply via email to