NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Bonded Network adaptors #24629694
Hold on to your hats, this one is a lulu. I have a call into tech support, but I think this needs to be seen by all.
The trouble started when I changed the name of my 516 after I had it configured. I figured it would be the easiest way to integrate it into my office...set it up under one name and then when everything is good to go, change the name to an existing server (after taking the old one offline). I've done this a few times before with older ReadyNAS so I didn't give it much thought. As a potential piece to the puzzle, I also chose this change-over time to bond the ports together. Initially, everything seemed fine. But after a short time, things got weird. Windows computers started disappearing from the network discovery window and every machine continued to report seeing the server under the old name and not the new one. You could only access the server using the new name. The old name could not be pinged or anything. To further complicate things, my R7000 also reported the NAS under the old name.
Netgear Support suggested I change the DNS address on a Windows machine and see what happened. Low and behold, all the computer names could be seen and the old name disappeared. They suggested I upgrade the firmware in the R7000 and see if that fixed the issue. Well, it didn't. The R7000 continued to see the NAS under the old name. I then did a hard reset on the r7000. Presto...everything showed up again and even the R7000 showed the correct name. Ok, so I tried loading the configuration file into the r7000 and move on with my day. No dice. The old name returned. OK, I'll just wipe the r7000 and reenter everything by hand. So now the r7000 shows the right name..oh wait...now it is showing the right name TWICE. 2 different IP addresses, both pointing to the SAME MAC address! Didn't even know that was possible! Furthermore, the display is showing one IP address and Frontview is showing the other. Well, this deserves a call to Netgear. ReadyNAS folks don't work on weekends I guess as they took my number and said they would call Monday.
To be sure there wasn't something funny going on with my GS724Tv4, I called to be sure that was OK. After some very extensive convincing to get someone to look at my router, it was determined it was ok. But they then turned back to the ReadyNAS and started trying the different bonding options only to get the whole server to completely lock up. After a forceful shutdown, the system came online and presto....everything started working the way they were supposed to. Now I'm certain I did both hard and soft resets on the server, switch, and router during all of this so my guess is that from playing with the bonding options enough, that somehow slapped the NAS back into reality.
So what in the world happened here? Most likely this won't happen again as I don't have any plans to change the name again...but could I be looking at a hardware issue or is there another weird bug in OS6.2.2?
The trouble started when I changed the name of my 516 after I had it configured. I figured it would be the easiest way to integrate it into my office...set it up under one name and then when everything is good to go, change the name to an existing server (after taking the old one offline). I've done this a few times before with older ReadyNAS so I didn't give it much thought. As a potential piece to the puzzle, I also chose this change-over time to bond the ports together. Initially, everything seemed fine. But after a short time, things got weird. Windows computers started disappearing from the network discovery window and every machine continued to report seeing the server under the old name and not the new one. You could only access the server using the new name. The old name could not be pinged or anything. To further complicate things, my R7000 also reported the NAS under the old name.
Netgear Support suggested I change the DNS address on a Windows machine and see what happened. Low and behold, all the computer names could be seen and the old name disappeared. They suggested I upgrade the firmware in the R7000 and see if that fixed the issue. Well, it didn't. The R7000 continued to see the NAS under the old name. I then did a hard reset on the r7000. Presto...everything showed up again and even the R7000 showed the correct name. Ok, so I tried loading the configuration file into the r7000 and move on with my day. No dice. The old name returned. OK, I'll just wipe the r7000 and reenter everything by hand. So now the r7000 shows the right name..oh wait...now it is showing the right name TWICE. 2 different IP addresses, both pointing to the SAME MAC address! Didn't even know that was possible! Furthermore, the display is showing one IP address and Frontview is showing the other. Well, this deserves a call to Netgear. ReadyNAS folks don't work on weekends I guess as they took my number and said they would call Monday.
To be sure there wasn't something funny going on with my GS724Tv4, I called to be sure that was OK. After some very extensive convincing to get someone to look at my router, it was determined it was ok. But they then turned back to the ReadyNAS and started trying the different bonding options only to get the whole server to completely lock up. After a forceful shutdown, the system came online and presto....everything started working the way they were supposed to. Now I'm certain I did both hard and soft resets on the server, switch, and router during all of this so my guess is that from playing with the bonding options enough, that somehow slapped the NAS back into reality.
So what in the world happened here? Most likely this won't happen again as I don't have any plans to change the name again...but could I be looking at a hardware issue or is there another weird bug in OS6.2.2?
5 Replies
Replies have been turned off for this discussion
- What bonding mode were you using initially? What are you using now?
- What I started with is what I ended with: LACP Layer 3+4 in the hopes that when the dust clears, I can copy everything from this server to my old one for backup way faster.
- LACP generally won't improve performance for a single connection. It's designed for trunking, so clients using unbonded connections will still see packets in order with no drops. That limits performance gains when both clients are bonded connections.
Layer 3+4 hashing might help some, but only if layer 4 is using multiple ports. StephenB wrote: LACP generally won't improve performance for a single connection. It's designed for trunking, so clients using unbonded connections will still see packets in order with no drops. That limits performance gains when both clients are bonded connections.
Layer 3+4 hashing might help some, but only if layer 4 is using multiple ports.
That is my hope: both NASs will have a bonded connection to increase the speed of the initial copy before I send the backup NAS to its off site home.
I heard from support this morning. I was told there were no known issues with bonding and that I shouldn't have any more trouble. I find that line of thinking troubling as there was very clearly an issue. Yes, it cleared up after several days of screwing around and much finger pointing on Netgear's side, but that doesn't mean there isn't something wrong with the code that shouldn't be looked at.
Anyhow, it is here for others to Google if someone else has the same problem.
I don't think it will. But if you measure speeds over 125 MB/s then it clearly will be helping.rjwerth wrote: That is my hope: both NASs will have a bonded connection to increase the speed of the initial copy before I send the backup NAS to its off site home.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
