second ethernet card hangs up

[admin@beatson.gla.ac.uk]

I have an open-e nas xsr enterprise

Model: Open-E NAS-XSR ENTERPRISE
Version:3.10.XE00000000.2364
Release date:2006-11-14


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?

[To-M]

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

[admin@beatson.gla.ac.uk]

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.


Network controllers

3Com Corporation 3C941 Gigabit LOM Ethernet Adapter
Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (rev 03)
Intel Corporation 82573L Gigabit Ethernet Controller

Network drivers:
Intel(R) PRO/1000 Network Driver
SysKonnect SK-NET Gigabit Ethernet SK-98xx driver
SysKonnect Gigabit Ethernet driver



have sent support at eopen a copy of the log files

[To-M]

The critical_error.log file shows the following:

Dec 15 18:32:42 nas ip_test_log: WARNING: Two or more network adapters are in the same subnetwork.

Please check to see if there is another duplicated IP Address on the network.

[admin@beatson.gla.ac.uk]

I have checked and no duplicate ip address in the network.

I run ping 172.xxx.xxx.xxx -n 1000. There is no reply until the nas is power cycled. The I get a response for about 15 minutes then no more response.

Peter

[To-M]

Can you test this using a 10.x.x.x network (using a crossover) and a 192.168.x.x. Then test with crossover to the 172.x.x.x.

Are you using any Jumbo frames?

[admin@beatson.gla.ac.uk]

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


Change
Et0 onboard 130.209.232.x
Et1 onboard 130.209.232.x

Ping these cards all works perfectly


I have added a 3com card and there are now three ether net cards in the system

Et0 onboard 130.209.232.x
Et1 onboard 130.209.232.x
Et2 3com 172.20.232.x

Then I ping all three cards and after about 15 minutes the et2 hangs up, eto and 1 remain fine.

ping in with cross over cable is fine.

Peter

[To-M]

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.

[admin@beatson.gla.ac.uk]

problem identified


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

[To-M]

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.

[bzazzera]

Hi all,

I have quite the same problem but not on the second Ethernet port, it is on the first port Eth0. After many heavy data transfers CIFS or NFS, the port Eth0 "hangs" and does not response to a ping anymore until we reboot the machine.

Eth0 is a Gigabit Yukon Chip configured with a static IP 192.168.x.x and netmask 255.255.255.0.

Eth1 is an Intel Gigabit Chip configured with a DHCP IP but not connected to the network.

The motherboard of the machine is an Intel SE7520BD2 and I am using the NAS R3 Enterprise version 4.01.DB0000000-2528.

Is there a fix to this issue ?

Best regards,

Bruno.

[To-M]

Try to see if this setting will resolve the issue. Enter to console tools-> boot options-select system architecture and choose Intel I/O AT mode then restart. Also there is a newer version for the NAS-R3 ver. 410 build 2584 please update and test as well.

[bzazzera]

Thanks for the fast answer.

Unfortunately, I have no IDE CD-ROM on my machine, could we upgrade to version 4.10 Build 2584 from an external USB CD-ROM?

Bruno.

[To-M]

Yes as long as you can see this in the BIOS of Motherboard.

[bzazzera]

Could we upgrade an external USB Flash Pen Drive?

Thanks.

Bruno.

[To-M]

Sorry we do not support updating with Pen Drives only the following ways below.

Update Instructions:
NOTE: this update will reset all settings to factory defaults with the exception of IP
addresses settings !

Before Updating, all existing snapshots must be removed. You might have trouble to
access your volumes after updating when you leave old snapshots on the server.
To be sure, that no snapshot is active, please deactivate synchronization as well.
Please write down the actual NAS server IP address and NAS server name. After having
updated Open-E NAS-XSR, please re-enter both.

Please write down authorization settings.
Before Updating, please save “User & Groups”, “Shares” and “Assignments” under Menu:
“maintenance” �� “resources misc.” �� in Function “Save resources”.
Please download and save NAS Server Logs:
Menu “status” �� “hardware” in Function “Logs” click on “download” button, then save on
your local HDD.

There are different ways of updating NAS-XSR software:
1. Updating with online-update:
o In order to download a new online-update you need to be registered at www.opene.
com.
o You also have to remember to set correct DNS and Gateway address in “setup” ��
“network” menu.
o Next under menu: “maintenance”��“update” in Function “Update downloader” press
“apply” button.
o If update-file appears then you must mark it and press “Update” button, then confirm
update when you will be asked. In case of a new update do as in previous updates.
NOTE: Some updates need a system restart. In this case you will be informed about needed restart by confirmation message.

2. Updating directly from administrator’s PC:
o Under menu: “maintenance” �� “update” in Function “System software update” press
“Browse” button and search previously downloaded ISO-file or update-file,
o Next you must mark it and press “Update” button and confirm update when you will be
asked.

3. Updating from a share (on NAS-XSR server):
o In resources menu create share "update" with default path,
o Copy update ISO-file or update-file into “update” folder with SMB, NFS or FTP etc. ,
o Under menu: “maintenance” �� “update” in Function “System software update” this file
will appear automatically,
o Next you must mark it (on the left) and press “Update” button and confirm update
when you will be asked.

4. With update from ISO-image CD follow this steps:
o The ISO-files which include in update file must be burned on a CD with your favorite
Burning software. (For example: Nero Burning ROM - option: “Burn Image”, etc.)
o Next please install CD-ROM as Secondary-Master and DOM (disk-on-module) as
Primary-Master. USB CD-ROM can be used as well.
o Please set the BIOS to boot from CD-ROM drive.
o Then boot from the ISO-CD and wait until prompt: “Update complete, Please Remove
CD and restart”
o After update, please reset the BIOS to boot from Primary-master HDD.
NOTE: Updating the system may take about 10 minutes !

[bzazzera]

Hi everybody,

I upgraded the NAS R3 Enterprise to version 4.10 and the problem has been fixed.

Many Thanks.

Bruno.