meta data for this page
  •  
Book Creator
 Add this page to your book
Book Creator
 Remove this page from your book  

 Manage book(0 page(s))
 Help

This is an old revision of the document!

Cluster

From Proxmox 6.0 it is possible to use GUI t ocreate and join cluster.

Second network interface with separate internal IP network is recommended for redundacy.

Datacenter –> Cluster –> Create cluster

Joining

Joining other nodes

Join can stuck when there is problem with iSCSI connection from newly added node. Check journal on joining node; 

kernel: scsi host9: iSCSI Initiator over TCP/IP
pvestatd[2097]: command '/usr/bin/iscsiadm --mode node --targetname iqn.2020-04.com.zyxel:nas326-iscsi-pve1-isos-target.tjlintux --login' failed: exit code 24
iscsid[1060]: conn 0 login rejected: initiator failed authorization with target
iscsid[1060]: Connection135:0 to [target: iqn.2020-04.com.zyxel:nas326-iscsi-pve1-isos-target.tjlintux, portal: 192.168.28.150,3260] through [iface: default] is shutdown.

Joining process will be waiting infinitely until iSCSI device will be connected. During this time it is possible to disable CHAP authentication in remote iSCSI target, or provide common credentials for Target Portal Group.

iSCSI issue with CHAP

When CHAP is used for iSCSI (manually configured from Debian console), joined node wants to connect to the same iSCSI target using own initiator name and own local configuration. Of coruse NAS326 is configured with only one CHAP login and passwod, so joining is not possible.

Is it possible to add new acl for target on NAS326 using targetcli command, or disable CHAP.