[PVE-User] iscsi storage array is reporting errors when is defined trough web interface

Martin Krpata martin.krpata at ou-nem.cz
Tue Sep 11 11:40:32 CEST 2012


Hi,
why is iscsi client (proxmox server) trying to establish second 
connection (when is defined in web interface)? Proxmox is watching 
connection to iscsi storage or forcing it? How?

What exactly do command that add iscsi storage trough web interface?
This is what i found:
* iscsi discovery
* define iscsi connection in /etc/iscsi (nodes, ...)
* /etc/init.d/open-iscsi start
* add iscsi storage to /etc/pve/storage.cfg

Martin Krpata


> Hello,
>
> i have GigastorATX - iscsi storage. It has 8x1Gbps ports and 16 slots 
> for sata disks. I want to have 2 proxmox HA server (3 nodes=1 for 
> quorum, 2 HA). On 2 HA servers iscsi storage with shared LVM.
>
> My test was: setup ethernets, switch, setup gigastor iscsi storage, 
> add trough web interface iscsi storage, no direct lun, prox1 and 2 
> servers, connect. (it generate configs in /etc/open-iscsi/...) iscsi 
> is connected running, but gigastor report errors (bellow). Remove from 
> web interface, configure iscsiadm, connect on both servers, all ok, 
> but is not defined iscsi storage on web interface (/etc/pve/storage). 
> Add iscsi storage to web interface, gigastor report errors again.
>
> With defined iscsi in web interface and //etc/iscsi.d/open-iscsi stop/ 
> does not stop error reports - just disconnect from iscsi. But prox 
> still try open tcp socket to iscsi without open-iscsi running, how it 
> is possible?
>
> It looks like proxmox is connecting to storage trough some direct 
> command? How can i fix error reports, do not define iscsi in web 
> interface, only lvm?
>
> 10.2.2.2 - storage
> 10.2.2.201 - server 1
>
> *
> *Cycling errors on iscsi storage (10s timeout), socket number is 
> increasing (sample is socket 262):
> *OPEN*:
> /Category://
> //iSCSI//
> //Severity://
> //Info//
> //EventID://
> //Open Socket Request//
> //Source://
> //ICS//
> //Summary://
> //Target 10.2.2.2:3260, Initiator 10.2.2.201:44780, Socket 262//
> ////
> //Sequence ID//
> //827//
> //Socket//
> //262//
> //Target TCP Port//
> //3260//
> //Target IP Address//
> //10.2.2.2//
> //Initiator TCP Port//
> //44780//
> //Initiator IP Address//
> //10.2.2.201//
> /
> *ERROR:*
> /Category://
> //Network//
> //Severity://
> //Warning//
> //EventID://
> //TCP TxIscsiCloseInd//
> //Source://
> //AWR//
> //Summary://
> //Skt:262::10.2.2.201:44780.0xaeec::10.2.2.2: Tx Close Indi. to iSCSI//
> ////
> //Sequence ID//
> //828//
> //
> //Skt:262::10.2.2.201:44780.0xaeec::10.2.2.2: Tx Close Indi. to iSCSI//
> //0000//
> //07 00 01 06 00 00 00 00 00 00 00 00 00 00 00 00 ........|......../
>
> *CLOSE:*
> Category:
> iSCSI
> Severity:
> Warning
> EventID:
> Close Socket
> Source:
> ICS
> Summary:
> TCP FIN, Socket 262
>
> Sequence ID
> 829
> Socket
> 262
> Target TCP Port
> 3260
> Target IP Address
> 10.2.2.2
> Initiator TCP Port
> 44780
> Initiator IP Address
> 10.2.2.201
> Close Reason
> TCP FIN
>
> Thanks for any help,
> Martin Krpata
> Czech Republic
>
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pve.proxmox.com/pipermail/pve-user/attachments/20120911/7bbb62f0/attachment-0014.html>


More information about the pve-user mailing list