Stuart Little wrote:
> Hi,
>   Using open-iscsi-2.0.869-8.1  (x86_64) on a SUSE 11.0 based machine,
> connecting to an HP D2D.
> 
>   Generally operation seems fine but I have some issues:-
> 
>   I cannot get the system to reconnect as start, if I configure open-isci to
> start at boot
>   the system hangs, I have to do a force reboot and boot single user, 
> configure
> open-iscsi to off.
>   Starting open-iscsi by hand always works,  but login appears to work on two
> interfaces only.
> 
>   Messages displayed during manual start:-
> 
> etc/init.d/open-iscsi start
> Starting iSCSI initiator service:
> done
> Setting up iSCSI targets: Logging in to [iface: default, target:
> iqn.1986-03.com.hp:storage.d2dbs.hu191248n0.500110a0002b2aa6.autoloader2.drive,
> portal: 192.168.2.85,3260]
> 
> Logging in to [iface: iser, target:
> iqn.1986-03.com.hp:storage.d2dbs.hu191248n0.500110a0002b2aa6.autoloader2.drive,
> portal: 192.168.2.85,3260]               
> Logging in to [iface: default, target:
> iqn.1986-03.com.hp:storage.d2dbs.hu191248n0.500110a0002b2aac.autoloader2.robotic
> s, portal: 192.168.2.85,3260]         
> Logging in to [iface: iser, target:
> iqn.1986-03.com.hp:storage.d2dbs.hu191248n0.500110a0002b2aac.autoloader2.robotic
> s, portal: 192.168.2.85,3260]
> Login to [iface: default, target:
> iqn.1986-03.com.hp:storage.d2dbs.hu191248n0.500110a0002b2aa6.autoloader2.drive,
> portal: 192.168.2.85,3260]: successful
> Login to [iface: default, target:
> iqn.1986-03.com.hp:storage.d2dbs.hu191248n0.500110a0002b2aac.autoloader2.robotic
> s, portal: 192.168.2.85,3260]: successful
> 
>   I can change the constraints in the startup to start open-iscsi after
> everything else and it will
>   still hang.
>   Could the failure to connect on the iser interfaces be a cause of the 
> failure
> to start at boot?


Yes. Is your system completely hung or does it just not proceed. It 
looks like we cannot log into the iser targets. With the default time 
outs, it could retry for around 5 minutes, so the system will look hung, 
but eventually it would proceed.

Decrease node.conn[0].timeo.login_timeout and 
node.session.initial_login_retry_max.

>   If so is there a way to disable the iser interfaces and stick with the tcp
> connections?

Set the node.startup to manual for the iser ones.


I think you would want to set things up so the infinniband stuff is 
tarted earlier or iscsi is started later. Then you can leave the 
node.startup values alone.




> 
>   Another problem was uncovered when a real local tape drive was added, while
> status messages suggsted that
>   the open-iscsi interfaces hand changed from using /dev/st0 to /dev/st1 the
> system would not actually

You lost me. So the tape device is local or accessed through iscsi?

>   work correctly. I have not tried a reinstall yet, but removal of the 
> offending
> local drive let the system
>   work sensibly again.
> 
>   Cheers,
>     Stuart
>                                 
> 
> 
> --
> 
> You received this message because you are subscribed to the Google Groups 
> "open-iscsi" group.
> To post to this group, send email to open-is...@googlegroups.com.
> To unsubscribe from this group, send email to 
> open-iscsi+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/open-iscsi?hl=en.
> 
> 

--

You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-is...@googlegroups.com.
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.


Reply via email to