On Nov 17, 2007, at 11:43, Chris wrote: > I do not have any iscsi related messages. > What other diags can I run that might help me troubleshoot the > problem?
check port 3260 traffic with tcpdump, and netstat to make sure you're maintaing a connection, or if you have parallels or vmware fusion, you could try testing with the solaris initiator to make sure you can connect: # iscsiadm modify discovery -t enable # iscsiadm add discovery-address <IP address of host> then for CHAP use the initiator-node --CHAP commands # iscsiadm modify initiator-node --authentication CHAP # iscsiadm modify initiator-node --CHAP-name <name> # iscsiadm modify initiator-node --CHAP-secret Enter secret: Re-enter secret: On the target side, I also find it helpful to set a TPGT to force discovery on a particular IP or subnet .. the tpgt number is an arbitrary number between 1 - 65535 .. so for example: # iscsitadm create tpgt 1 # iscsitadm modify tpgt -i <IP address> 1 # iscsitadm modify target -p 1 media For relative performance gains, you might want to set TCP_NO_DELAY on the initiator, and maxrecv on the target. hth --- .je _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
