second ethernet card hangs up

[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.