this has two onboard ethernet cards. I have segmented my lan so that my clients connect over 1 ip range and my backup server and application servers over a second private address space. This means that most of my backup and work traffic never routes outside the switch the open-e nas is attached to.
The open-e unit is about 1 week old. When I configure the two ethernet cards they both work perfectly, I can map drive to the addresses on both the first and second ethernet cards. However after about 15/20 minutes the second ethernet card stops responding. I can reproduce this using ping. Both cards respond then eth1 stops responding after 15 minutes. The only way to bring eth1 back to life is to reboot (power cycle) the nas. The supplier has replaced the motherboard in the unit.
I have a fealing that this is not faulty hard ware but may be a problem with the kernel, but I could be wrong.
Is anyone else experiencing this problem or has a soloution for it?
Can you try with using a crossover cable. Also see if you can try using another approved NIC from our web site compatibility listings. If this does not help please send logs to support@open-e.com
OK this morning I added a 3com card. It is seen by the nas and works fine as long as the ip address is in the 130.xxx.xxx.xxx range as soon as I set it to 172.xx.xxx.x range then the card responds for about 15 minutes then hangs up.
OK have tested and it is fine with crossover cable
so the play so far is
When the two Ethernet cards are in the same subnet then everything works fine. I only encounter problems when one card is in the 130.209.232.x range and the other card is in the 172.20.232.x range.
The tests so far
Initial set up
Et0 onboard 130.209.232.x
Et1 onboard 172.20.232.x
Ping these two cards and after about 15 minutes et1 hangs up
Let me see if I understand correctly - when you used another NIC and a crossover cable everything is working fine with 172.x.x.x?
If yes then could there be a switch issue or software installed on another system. We had a customer use GoldDisk on a system that would block certain requests from systems (like ping) that they forgot to mention. Please check for similar.
If no send logs to support. If you have sent logs please try to stay with one engineer for support this helps us duplicate efforts.
Support asked me to revert to an nas-xsr version 3.08 which has an older kernel. Once applied both interfaces stay up ( well for three hours so far, previously 16 minutes). So looks like a kernel issue?
Peter,
I saw this in support as well; please keep in touch with them to keep tracking this issue. What is weird we have another customer with same virtual setup and version and not a problem. But in this case there is a kernel problem. Thanks for being patient.