To Developer's
I have studied the netlink interface What i have understood from code
study is that the request goes to the iscsi layer through the netlink
interface after then the iscsi_tcp forwards the request through the
network
In response the iscsi_tcp Interface receives the response , then
To Developer's
I have studied the netlink interface What i have understood from
code
study is that the request goes to the iscsi layer through the
netlink
interface after then the iscsi_tcp forwards the request through the
network
In response the iscsi_tcp Interface receives the response , then
On 02/01/2012 10:05 AM, Gopesh Sharma wrote:
The SAN admin page does not show any error except 1 failed disk . I
restarted the SAN which came up without any issue.
I have gone through the configuration couple of times
I suspect the 10GigE Switch which lies between SAN and Server .
Right now
On 02/01/2012 10:16 AM, kundra wrote:
To Developer's
I have studied the netlink interface What i have understood from code
study is that the request goes to the iscsi layer through the netlink
interface after then the iscsi_tcp forwards the request through the
network
In response the
Confused as IOCTL is not being used in the open-iscsi , then the iscsi-tcp
routines are not being called in this interface , I have different flow chart
which I have implemented on study by taking iscsi_sw_tcp.. as my reference .As
the ioctl is obsolete and not being used instead iscsi_ipc
Eddie Wai eddie@broadcom.com schrieb am 02.02.2012 um 04:03 in
Nachricht 1328151794-21893-1-git-send-email-eddie@broadcom.com:
Whenever a new node gets created via the 'iscsiadm -m node -I name
-I ifacename -o new' command, the new iface net parameters doesn't
get populated to the
