NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Starlionblue3
Jan 26, 2016Tutor
Network performance slowdown after a few hours
I have a ReadyNAS NVX connected to a Netgear GS108T smart switch through two CAT6 cables using link aggregation with LACP on the switch. The ReadyNAS ports are set up as 803.2ad LACP, with Layer 3+4 xmit hash policy. (The switch ports and LAG are set up as edge ports but either on or off doesn't seem to affect the problem).
Network settings from logs below.
Typically when I start the NAS up I can copy large files to my desktop at around 50-65 MB/s, which is quite reasonable considering the hardware limitations. However after a few hours of heavy file copying the speed goes down to 6-7 MB/s.
Rebooting the ReadyNAS speeds things right back up, so I can't help but think that something on the ReadyNAS degrades over time. Perhaps a full cache or something similar.
I'm looking for any possible solutions to this issue.
bond0 Link encap:Ethernet HWaddr 00:22:3F:A9:FE:56
inet addr:10.0.0.27 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::222:3fff:fea9:fe56/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:87804911 errors:0 dropped:441 overruns:0 frame:0
TX packets:254931345 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:752847125 (717.9 MiB) TX bytes:374615947 (357.2 MiB)
eth0 Link encap:Ethernet HWaddr 00:22:3F:A9:FE:56
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:87735909 errors:0 dropped:0 overruns:0 frame:0
TX packets:43207 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:739297710 (705.0 MiB) TX bytes:16557638 (15.7 MiB)
Base address:0xde80 Memory:fea40000-fea60000
eth1 Link encap:Ethernet HWaddr 00:22:3F:A9:FE:56
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:69002 errors:0 dropped:6 overruns:0 frame:0
TX packets:254888138 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13549415 (12.9 MiB) TX bytes:358058309 (341.4 MiB)
Base address:0xdf00 Memory:fea60000-fea80000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:29326 errors:0 dropped:0 overruns:0 frame:0
TX packets:29326 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2084454 (1.9 MiB) TX bytes:2084454 (1.9 MiB)
tunl0 Link encap:IPIP Tunnel HWaddr
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
IPV6_ASSIGN_eth0=STATELESS
JUMBO_FRAMES_eth0=0
SPEED_DUPLEX_eth0=AUTO_NEGOTIATION
Settings for bond0:
Link detected: yes
Settings for eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
bond0:4:eth0,eth1:1
22 Replies
Replies have been turned off for this discussion
- StephenBGuru - Experienced User
What firmware are you running? Also, what OS is the PC running?
FWIW, the bond will not increase your single-user speeds, so you could try disconnecting one of the cables and see if that makes any difference. My guess is that it won't though.
Yep, I tried single cable. No difference. I've tried connecting with only one switch between PC and ReadyNAS as well with the same results. Right now I'm running a Netgear GS108T smart switch for the NAS, connecting with two cables (LACP with RSTP) to a Netgear GS716T smart switch which connects to the PC.
Maybe it has something to do with the networking between the switches, but that wouldn't explain why restarting the ReadyNAS fixes it. Or?
ReadyNAS firmware is 4.2.2.28, and I'm on Windows 10. However I had similar problems in Windows 7 and 8.1, but they didn't appear as "reliably" as now.
Model: ReadyNAS NVX Business Edition [X-RAID2] Serial: 23N5047F00839 Firmware: RAIDiator 4.2.28 Memory: 1024 MB [6-6-6-24 DDR2]
- StephenBGuru - Experienced User
I think you've ruled that out. If you want to be 100% certain you could try a direct connect. Maybe next time try rebooting the PC instead of the NAS, and see if it also recovers. How are you doing the copies?
Starlionblue3 wrote:
Maybe it has something to do with the networking between the switches...
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!