D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-345 => Topic started by: Spock83 on May 31, 2012, 01:37:33 PM
-
What is the best practise for best upload and download?
(http://shrani.si/f/3O/kr/3GNcy8dB/dns345.jpg)
Ty
-
Anyone?
-
I tried every configuration. For me the best is with just one cable connected...
-
What is ethernet bonding?
-
Use both ethernet links...
-
Ah, ok. Thanks. :)
-
I tried every configuration. For me the best is with just one cable connected...
So what are your speeds for up/dl? I have around 90-100MB/s download (read) and 40-50MB/s upload(write).
Only adaptive options works without special switch.
-
It depends on drives configuration...
-
hey just confused a little on the ethernet bonding i have the lan1 and pan2 both connecting to 2 ports on the back of my time capsule
are they both suppose to go there? what will happen if i connect one to a computer and one to the router?
and what are the best settings for transferring and speed performance will be streaming alot around the house to different devices
help is much appreciated
-
Take a look at this:
http://en.wikipedia.org/wiki/802.3ad#Linux_Bonding_Driver (http://en.wikipedia.org/wiki/802.3ad#Linux_Bonding_Driver)
This article explains all the modes.
-
I use Adaptive Load Balancing.
I have a matching pair of CAT6 cables going from my NAS to my Gbit switch. I also found that I had to restart my NAS before it would start working correctly. I have firmware 1.01 installed. Initially when I set it up it showed the IP as being 169.254.xxx.xxx even though I could get it to on its reserved IP.
-
I use Adaptive Balancing and get 80MB/s writes from my Mac to the NAS hardwired through ethernet.
-
Dnsguy: the question is how are your drives configured?
-
Dnsguy: the question is how are your drives configured?
2-2TB Seagate Barracuda drives mirrored and encrypted.
-
Ok, I'm going to experiment a bit with the link aggregation.
Had a 500GB (7200 RPM) test hard drive in my unit (while waiting for two WD Red 3TB drives to arrive). While doing a backup from my computer to the NAS I was getting 9% network utilization (Windows resource monitor)....and backing my system drive as a 260GB image (sector) was agonizingly slow.
My two WD drives have arrived and are installed.
I was out of ethernet ports (Dlink DIR-655 4 port + Dlink 5 port switch) so replaced the 5 port with an 8 port switch and thus now have LAN 1 and LAN 2 cables running into the NAS.
Will do some reading and try to figure out what is the best choice for joining the ports to improve performance.
This document http://www.mjmwired.net/kernel/Documentation/networking/bonding.txt (http://www.mjmwired.net/kernel/Documentation/networking/bonding.txt) seems to offer the most useful information on the way to "Maximum Throughput", in section 12....but I've read it twice and it hasn't sunk in yet...hoping others will take a look at this and offer suggestions..!!
-
I'm interested by the results of your tests
Thanx
-
Have you had an opportunity to perform your link aggregation testing? ???
-
Well, its a mit confusing. Wish the "Dummy's Guide to Ethernet Bonding" was available.
I have the two LAN cables connected, and i've tried various settings, but the results are not consistent. I've seen network utilization rise...originally was 9% with the single connection and my Seagate drive. The transfer was fairly constant (+/- a few percent)...now ranges from 3% up to 60% (on a gigabit router/switch) in wild swings (looks like the squiggles from a lie detector tape)...!!
I've looked at the resource monitor available from the NAS' ... it shows graphs for LAN1 LAN2, but only LAN1 shows any activity...LAN2 never shows a twitch...regardless of the setting. Am i doing it right?? What is the process for the DNS-345...its just not really clear. I've restarted the unit (as another post suggested), but noting every registers on the LAN2 graph.
I don't know how to approach this in a methodical manner...so have shelved it for now...left the settings on Adaptive Load Balancing...
-
I would imagine the dual ports would also be beneficial in a WAN environment, where two routers in the same WAN have dedicated GB connections to the DNS-345.
-
Wouldn't you need a managed switch (with bandwidth aggregation support) behind the DNS-345 to route inbound traffic? I'm looking at the DNS-345 manual and found this excerpt:
". . .The ShareCenter will auto-negotiate the highest connection speed available to your router or switch. If you are using Port Bonding, use a managed switch."
-
Well, that is part of the complexity. Some of the options in the "link aggregation" require a switch that supports 802.3ad, which my D-Link router does not, but there are a number of options and some options do not need the specialized support.
I'm still reading on this, but here is an example of where someone was looking for performance gain, and decided that 802.3ad was not the way to go...
From my understanding the only bonding mode that offers any performance improvement for a single TCP stream is balance-rr (mode 0 for the bonding driver) which simply tosses packets out in a round-robin fashion.
...rather the balance-rr (Round Robin) was the 'performance choice' after his analysis. The article goes on to describe the challenges he faced (and overcame)...how he figured out how to make it work...and how to measure the throughput: http://devnerd.net/2011/02/high-performance-interface-bonding-in-linux/ (http://devnerd.net/2011/02/high-performance-interface-bonding-in-linux/)
But MTU (?) and most of this is gobble-de-gook to me...
-
According to this document, the round robin needs a switch or router that can be configured for "static link aggregation" http://www.readynas.com/wp-content/uploads/2008/09/ReadyNAS-Teaming.pdf (http://www.readynas.com/wp-content/uploads/2008/09/ReadyNAS-Teaming.pdf). And they refer to "managed switches"...
-
What is the best practise for best upload and download?
(http://shrani.si/f/3O/kr/3GNcy8dB/dns345.jpg)
Ty
The DNS-345 doesn't properly bound, instead of using a virtual NIC and bonding both NICs together grabbing 1 IP address from the DHCP server both NICs grab an IP address and who knows what it does for bounding as it doesn't seem to do what industry standards saying bounding is.