Frank,
I am also using version 3.3.0.43 of GlobalSAN.
The initiator name is not set to NULL, so I don't know why it isn't
being propagated to the server correctly.
If it were NULL on the client, or being passed as NULL to the
server, wouldn't the NULL pointer dereference be occurring both with
and without CHAP enabled?
No, the specific place where the client name is checked is in the
following code segment, which is under the conditional of "if
(isns_enabled() == True)"
http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/iscsi/iscsitgtd/util.c#107
Also, this is the first I hear of iSNS discovery or iSNS servers.
I never explicitly enabled any such thing... could that be what's
causing the problem?
No sure at this point.
How do I determine what those settings are?
# iscsitadm show admin
iscsitadm:
Base Directory: Not set
CHAP Name: Not set
RADIUS Access: Not set
RADIUS Server: Not set
iSNS Access: Not set
iSNS Server: Not set
iSNS Server Status: Not applicable
Fast Write ACK: Not set
Can iSNS discovery be disabled?
Yes, see the following:
iscsitadm modify admin --help
iscsitadm modify admin <OPTIONS>
OPTIONS:
-d, --base-directory <directory>
-H, --chap-name <chap username>
-C, --chap-secret
-R, --radius-access <enable/disable>
-r, --radius-server <hostname[:port]>
-P, --radius-secret
-S, --isns-access <enable/disable>
-s, --isns-server <hostname[:port]>
-f, --fast-write-ack <enable/disable>
Jim
Thanks.
Frank
--
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
