Hi all,
I've got a TrueNAS Core system running TrueNAS-13.0-U4 in HA mode with two nodes, and it's providing both NFS, CIFS and iSCSI service. I just added a new interface IP setup and I want to mount a specifc dataset (volume) from that IP address. But while I can ping the new IP from the client, I can't seem to get NFS working at all. Looking at the TrueNAS Console, I see with 'lsof -i -P' that mountd, rpcbind, rpc.statd, and nfsd are all listening on that IP address, as well as the existing IP address (virtual) that was defined before.
What do I need to do get the NFS services to respond to clients on new IPs? I've tried stopping/restarting the NFS daemons from the web gui, but since it's now production, I really don't want to have to bounce the box. Do I need to force a failover, and the consequent interruption of service to make things work?
How can I make changes like this take effect without impacting current NFS users?
I've got a TrueNAS Core system running TrueNAS-13.0-U4 in HA mode with two nodes, and it's providing both NFS, CIFS and iSCSI service. I just added a new interface IP setup and I want to mount a specifc dataset (volume) from that IP address. But while I can ping the new IP from the client, I can't seem to get NFS working at all. Looking at the TrueNAS Console, I see with 'lsof -i -P' that mountd, rpcbind, rpc.statd, and nfsd are all listening on that IP address, as well as the existing IP address (virtual) that was defined before.
What do I need to do get the NFS services to respond to clients on new IPs? I've tried stopping/restarting the NFS daemons from the web gui, but since it's now production, I really don't want to have to bounce the box. Do I need to force a failover, and the consequent interruption of service to make things work?
How can I make changes like this take effect without impacting current NFS users?
