NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Link aggregation (LACP) problems
I have just installed my ReadyNAS Pro 6 and yesterday I bumped into a couple of strange problems. First of all my Orb server was reported unreachable on my iPad and next one of my Windows machines was unable to connect to the ReadyNAS as well. The weirdest symptom on the latter was, that when I tried to ping the ReadyNAS' IP address from this Windows machine, a different IP address was reported to fail.
A quick Google search showed that some people had solved this problem by resetting their managed switch to factory settings. I have a LinkSys/Cisco L3 managed switch, a SRW2024P. And resetting it to factory defaults made sense, because I had to downgrade firmware earlier that day because a newer version didn't show it's web interface. In can imagine the old firmware not being forward-compatible with setting of the newer firmware. So I reset the setting and the problem was gone indeed.
Now I don't have many settings in this switch, and therefore it may have been a bit of a waste of money, but Techies buy features and I hope I don't have to explain why here ;-)
When reconfiguring the only non-default setting in the switch, link aggregation for my ReadyNAS, the connection problems and ping symptom immediately reappeared.
I have configured both Ethernet ports on the switch as one aggregated link as well as on the ReadyNAS. The first is spec'ed to be 802.3ad compatible and the latter is configured to 802.3ad mode. Any solutions, ideas, or similar problems anybody?
A quick Google search showed that some people had solved this problem by resetting their managed switch to factory settings. I have a LinkSys/Cisco L3 managed switch, a SRW2024P. And resetting it to factory defaults made sense, because I had to downgrade firmware earlier that day because a newer version didn't show it's web interface. In can imagine the old firmware not being forward-compatible with setting of the newer firmware. So I reset the setting and the problem was gone indeed.
Now I don't have many settings in this switch, and therefore it may have been a bit of a waste of money, but Techies buy features and I hope I don't have to explain why here ;-)
When reconfiguring the only non-default setting in the switch, link aggregation for my ReadyNAS, the connection problems and ping symptom immediately reappeared.
I have configured both Ethernet ports on the switch as one aggregated link as well as on the ReadyNAS. The first is spec'ed to be 802.3ad compatible and the latter is configured to 802.3ad mode. Any solutions, ideas, or similar problems anybody?
11 Replies
Replies have been turned off for this discussion
It's not obvious to me either, perhaps you should clarify (I suspect you meant it "should be..." something else).MindBender wrote: It turned out that I had configured a static link aggregation, which is nog supported by ReadyNAS. It should be a static link aggregation, and the difference is not obvious in my Switch's web front-end.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
