Hi,
searched the posts, could not find a similar question.
I grabbed an old dell dimension e520 and whipped a fine running Nas4Free 11.0.0.4
The issue is that this old motherboard comes with an integrated 10/100 NIC. It does the job, it takes the Wake on Lan (WOL) fine so I can boot up the server from another room, etc.
However, I wanted more speed. I bought a 10/100/1000 NIC, and it sits fine in the PCI port and actually can be active inside NAS as an additional card.
I am not very good with NAS, and I can't seem to find a way to:
Use the integrated NIC card to boot using WOL, but then, right after, having NAS4Free boot using only the second added-on card, and only using the second card from boot until shutdown. I do not need both working together as the 1000 NIC alone with be enough for my needs.
How to I tell Nas4Free to use the second added-on card only?
BTW I tried LAGG/Fallover setting, it did not seem to meet my goals.
Any suggestions?
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
One NIC to boot, the other NIC to provide services?
-
eagle3000
- NewUser
- Posts: 6
- Joined: 19 Oct 2017 17:58
- Status: Offline
-
ms49434
- Developer
- Posts: 828
- Joined: 03 Sep 2015 18:49
- Location: Neuenkirchen-Vörden, Germany - GMT+1
- Contact:
- Status: Offline
Re: One NIC to boot, the other NIC to provide services?
Select your Gbit NIC as LAN interface in Network -> Interface management, there shouldn't be any OPT interfaces configured.
Save, configure and reboot.
Save, configure and reboot.
1) XigmaNAS 12.1.0.4 amd64-embedded on a Dell T20 running in a VM on ESXi 6.7U3, 22GB out of 32GB ECC RAM, LSI 9300-8i IT mode in passthrough mode. Pool 1: 2x HGST 10TB, mirrored, L2ARC: Samsung 850 Pro; Pool 2: 1x Samsung 860 EVO 1TB, SLOG: Samsung SM883, services: Samba AD, CIFS/SMB, ftp, ctld, rsync, syncthing, zfs snapshots.
2) XigmaNAS 12.1.0.4 amd64-embedded on a Dell T20 running in a VM on ESXi 6.7U3, 8GB out of 32GB ECC RAM, IBM M1215 crossflashed, IT mode, passthrough mode, 2x HGST 10TB , services: rsync.
2) XigmaNAS 12.1.0.4 amd64-embedded on a Dell T20 running in a VM on ESXi 6.7U3, 8GB out of 32GB ECC RAM, IBM M1215 crossflashed, IT mode, passthrough mode, 2x HGST 10TB , services: rsync.
-
eagle3000
- NewUser
- Posts: 6
- Joined: 19 Oct 2017 17:58
- Status: Offline
Re: One NIC to boot, the other NIC to provide services?
I think I got something wrong in my original post.
The goal is to WOL each and everytime using the slow integrated 100 NIC. The server will go off many times. So it needs to be able to WOL remotely.
Since the card is slow, it would be better if after it boots up, switch exclusively to the PCI-add-on 1000 NIC for the service, reading and writing of files.
If it gets shuts down, be able to WOL again using the old NIC.
Why the trouble? The motherboard won't WOL from the added-on PCI card. So it is not viable to use this added-on PCI card only for all purposes. The instructions above did not help me. Unfortunately.
-------------
Anyways, I solved the issue, somewhat, by using LAN and OPT1.
LAN is setup for WOL (LAN is the slow integrated NIC)
Then I set up OPT1 with its own IP address, and later in CIFS/SMB I actually found an setting that lets me select which Interface to use. I selected OPT only.
It seemed to work, however, I checked NICs activity on the Status/Monitoring page and I discovered something puzzling. When I write a file, OPT1 indeed picks up the data, BUT when I read a file, the activity goes back to LAN (slow integrated NIC).
Is this a BUG??
Is there a setting I missed??
The goal is to WOL each and everytime using the slow integrated 100 NIC. The server will go off many times. So it needs to be able to WOL remotely.
Since the card is slow, it would be better if after it boots up, switch exclusively to the PCI-add-on 1000 NIC for the service, reading and writing of files.
If it gets shuts down, be able to WOL again using the old NIC.
Why the trouble? The motherboard won't WOL from the added-on PCI card. So it is not viable to use this added-on PCI card only for all purposes. The instructions above did not help me. Unfortunately.
-------------
Anyways, I solved the issue, somewhat, by using LAN and OPT1.
LAN is setup for WOL (LAN is the slow integrated NIC)
Then I set up OPT1 with its own IP address, and later in CIFS/SMB I actually found an setting that lets me select which Interface to use. I selected OPT only.
It seemed to work, however, I checked NICs activity on the Status/Monitoring page and I discovered something puzzling. When I write a file, OPT1 indeed picks up the data, BUT when I read a file, the activity goes back to LAN (slow integrated NIC).
Is this a BUG??
Is there a setting I missed??