NFS over second nic (bond) connection

[newton21890]

Hello guys,

I want to use the second NIC of my HP server to connect my shared NFS dir from my Synology NAS.
Now, my HP server is configured as follows:
- First NIC (192.168.9.46) for control connection and for cluster connection
- Second NIC (192.168.9.49) for NFS connection with my NAS

The problem is: If i remove the IP .46 from auth list from NFS shared dir, I can't reach dir from my server, even if the IP .49 is in the same auth list.

Why ?

 

[waltar]

1 NIC per network segment, so take other segment (eg 192.168.8...) or use first nic to synology too.

 

[newton21890]

Thanks for the answer.
I can't use more than one nic for the same subnet, It's so crazy !!! Why ?

use first nic to synology too.

To avoid performance problem with a single 1GB NIC, the second step of my config is to make a bond with the other 2 NIC inside my Server. I try to make a linux bond LACP layer2+3 and I do the same think with Synology NAS (has 4 nic at 1G) ant if it test the speed connection with iperf3 from server to nas the speed was 2Gbps (more o less) but if I do the test from NAS to my PVE the speed was half.

I config my old Switch with 2 eth-trunk in LACP mode.

I don't understand why this strange behavior.

 

[waltar]

Take a cable direct between your hp and synology with eg. 192.168.8... and mount it with that IP, all your other equipment still use the 192.168.9... IP's.

 

[sw-omit]

Thanks for the answer.
I can't use more than one nic for the same subnet, It's so crazy !!! Why ?

Probably not that crazy if you can't answer me the next question:
Where are you telling your server from which IP it should connect to which other IP when they are on the same subnet?

Note that there ARE ways to do the above, but it's generally more advised to use a different IP for each port that has an IP at all. Here's a recent longer explanation of it I did: https://forum.proxmox.com/threads/my-network-setup-need-tlc.153924/#post-700648