Hello.
We use 5 cp-nodes based on Proxmox ve in cluster.
Additionaly we have dedicated iSCSI storage built on CentOS 7.2 (targetcli).
When cp-nodes connect directly to the iscsi target, everything work perfect with no strange debug logs.
But when connecting to iscsi st-node using proxmox gui, there are many strange logs at st-node:
Jun 6 16:43:15 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:16 st-node1 kernel: rx_data returned 0, expecting 48.
Jun 6 16:43:16 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:25 st-node1 kernel: rx_data returned 0, expecting 48.
Jun 6 16:43:25 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:25 st-node1 kernel: rx_data returned 0, expecting 48.
Jun 6 16:43:25 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:25 st-node1 kernel: rx_data returned 0, expecting 48.
Jun 6 16:43:25 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:26 st-node1 kernel: rx_data returned 0, expecting 48.
Jun 6 16:43:26 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:26 st-node1 kernel: rx_data returned 0, expecting 48.
The iscsi.conf file,
node.session.auth.username = login1
node.session.auth.password = password1
discovery.sendtargets.auth.username = login2
discovery.sendtargets.auth.password = password2
root@cp-node1:~# iscsiadm --mode session -P 1
**********
Interface:
**********
Iface Name: default
Iface Transport: tcp
Iface Initiatorname: xxx
Iface IPaddress: 164.40.241.18
Iface HWaddress: <empty>
Iface Netdev: <empty>
SID: 61
iSCSI Connection State: LOGGED IN
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE
I would like to add, that there are no problems with accessing target, even using storage by all the cp-nodes as shared backend for lvm group.
What can cause that problems?
Regards.
We use 5 cp-nodes based on Proxmox ve in cluster.
Additionaly we have dedicated iSCSI storage built on CentOS 7.2 (targetcli).
When cp-nodes connect directly to the iscsi target, everything work perfect with no strange debug logs.
But when connecting to iscsi st-node using proxmox gui, there are many strange logs at st-node:
Jun 6 16:43:15 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:16 st-node1 kernel: rx_data returned 0, expecting 48.
Jun 6 16:43:16 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:25 st-node1 kernel: rx_data returned 0, expecting 48.
Jun 6 16:43:25 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:25 st-node1 kernel: rx_data returned 0, expecting 48.
Jun 6 16:43:25 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:25 st-node1 kernel: rx_data returned 0, expecting 48.
Jun 6 16:43:25 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:26 st-node1 kernel: rx_data returned 0, expecting 48.
Jun 6 16:43:26 st-node1 kernel: iSCSI Login negotiation failed.
Jun 6 16:43:26 st-node1 kernel: rx_data returned 0, expecting 48.
The iscsi.conf file,
node.session.auth.username = login1
node.session.auth.password = password1
discovery.sendtargets.auth.username = login2
discovery.sendtargets.auth.password = password2
root@cp-node1:~# iscsiadm --mode session -P 1
**********
Interface:
**********
Iface Name: default
Iface Transport: tcp
Iface Initiatorname: xxx
Iface IPaddress: 164.40.241.18
Iface HWaddress: <empty>
Iface Netdev: <empty>
SID: 61
iSCSI Connection State: LOGGED IN
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE
I would like to add, that there are no problems with accessing target, even using storage by all the cp-nodes as shared backend for lvm group.
What can cause that problems?
Regards.