ok it worked after a reboot.but dropping eid does not make sense to me.
What might be the exact cause of this eid being the FQDN not to be
authorised???
On Tue, Jan 13, 2009 at 11:27 PM, Nikhil nikhil.talpalli...@gmail.comwrote:
Hi,
It does not work for me :(
I used target name instead
Hi,
The iSNS server refuses connection to a network entity (eid) if there exists
an object already registered with the same network entity id but different
iSCSI node type(i.e. one initator and other target or vice versa). But if
the iSCSI node type is same (in case of two targets on same network
Hi,
It does not work for me :(
I used target name instead of eid . but the same err HELP!
cheers,
nikhil
On Jan 5, 2:21 am, Albert Pauw albert.p...@gmail.com wrote:
For the watchfull observant,the patch is shown in reverse,
it should read:
--- usr/isns.c 2009-01-04
I found the problem.
The problem is in the Entity Identifier. As it is now, it's just the
IP number of the initiator.
The Solaris initiator reports then Entity Identifier with its iqn
name. If I change usr/isns.c like this:
--- usr/isns.c.new 2009-01-04 12:11:27.0 +0100
+++
For the watchfull observant,the patch is shown in reverse,
it should read:
--- usr/isns.c 2009-01-04 12:11:27.0 +0100
+++ usr/isns.c.new 2009-01-04 11:17:43.0 +0100
@@ -162,10 +162,10 @@
length += isns_tlv_set(tlv, ISNS_ATTR_ISCSI_NAME, strlen
(name), name);
