qdevice NR

[bluedog]

I have a 5 node cluster, one of which is a piNode
When I recently added the 5th node, I ran into trouble as I have 2FA enabled. I was finally able to add node to cluster using command

pvecm add <target ip> -link0 <source ip>

Node was added to cluster and all seemed good

When I ran pvecm status it shows:

Membership information
----------------------
    Nodeid      Votes    Qdevice Name
0x00000001          1  NA,NV,NMW 192.168.1.24
0x00000002          1  NA,NV,NMW 192.168.1.26
0x00000003          1                   NR 192.168.1.20
0x00000004          1  NA,NV,NMW 192.168.1.22 (local)
0x00000000          0            Qdevice (votes 1)

My question is Node 3 shows as NR. What is significance of this? Is this something that needs to be corrected and if so how?

 

[bbgeek17]

My question is Node 3 shows as NR. What is significance of this?

NR (Not Registered).
https://access.redhat.com/documenta...sters#:~:text=Add the quorum,(Not Registered).

Is this something that needs to be corrected and if so how?

I dont have an advice on that.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Erin]

Did you get the NR device sorted out?
I am having this issue in a 2 node cluster with an RPi as a third voting node.
I can migrate between hosts fine but when I shutdown host one, the vms on host two go down with it.

 

[Erin]

Got mine sorted fairly easily, used the following workflow:
On the host with the NR flag ran

pvecm qdevice remove

On one of the working hosts ran

pvecm qdevice setup 192.168.44.31

Host came back and seems to be working properly now.