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.
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.
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.
Reply With Quote