- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have an issue with a S1600JP4 motherboard where the static IP address keeps disappearing. All four ports can link up just fine but could only ping for a certain amount of time before the IP address disappears. This issue keep persisting even after I reassign it with a different IP address. The harddrive and CPU has been swapped but it didn't resolve the issue.
Any ideas to solve this issue?
Thanks!
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Where exactly is the static IP address disappearing? Can you link up fine when doing a peer to peer communication?
If you could provide more detailed information about the issue so we can better understand it would be really appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Thank you for replying.
Yes, I can link up fine when doing peer to peer communication. I've used ethtool utility to verify that the port is linked up. However, the IP address keeps disappearing after a few seconds. The problem looks like the following below.
The following showed that I've assigned 192.168.0.12 to eth26.
root@user:/home/user# ifconfig eth26 192.168.0.12
root@user:/home/user# ifconfig eth26
eth26 Link encap:Ethernet HWaddr 00:1e:67:d7:01:59
inet addr:192.168.0.12 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21e:67ff:fed7:159/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:110 errors:0 dropped:0 overruns:0 frame:0
TX packets 194 errors:0 dropped:0 overruns:0 carrier:0
Collision:0 txqueuelen:1000
RX bytes:0 (27.3 KB) TX bytes:0 (40.9 KB)
Memory:d0900000-d0920000
root@user:/home/user#
At this point, it was able to ping to 192.168.0.1 for a few seconds and it starts to display "Destination Host Unreachable" once the IP address is lost.
64 bytes from 192.168.0.12: icmp_req=20888 ttl=64 time=0.004 ms
64 bytes from 192.168.0.12: icmp_req=20889 ttl=64 time=0.003 ms
64 bytes from 192.168.0.12: icmp_req=20890 ttl=64 time=0.003 ms
From 127.0.0.1 icmp_seq=20892 Destination Host Unreachable
From 127.0.0.1 icmp_seq=20893 Destination Host Unreachable
I hit ctrl + c and entered ifconfig eth26. Notice the IP address assigned to eth26 has disappeared.
root@user:/home/user# ifconfig eth26
eth26 Link encap:Ethernet HWaddr 00:1e:67:d7:01:59
inet6 addr: fe80::21e:67ff:fed7:159/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26099 errors:0 dropped:0 overruns:0 frame:0
TX packets 26172 errors:0 dropped:0 overruns:0 carrier:0
Collision:0 txqueuelen:1000
RX bytes:2568639 (2.5 MB) TX bytes:2578315 (2.5 MB)
Memory:d0900000-d0920000
The problem keeps recurring even after I assign it with a different IP address. I've swapped the harddrive and CPU but the problem still persist. I do not see the problem when I use the harddrive and CPU with a different motherboard.
Thanks,
Hai Huynh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
We can confirm the network adapters are working fine since you can create a peer to peer connection and link up. If the issue is following the board as you stated, our best recommendation is updating the firmware to the latest version:
https://downloadcenter.intel.com/download/25773/Intel-Server-Board-S1600JP-Intel-Server-System-R1000JP-System-Update-Package-for-UEFI?product=68407 Intel® Server Board S1600JP / Intel® Server System R1000JP System Update Package for UEFI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for your response.
I've updated the firmware but the problem still persist. I also tried bios recovery.
Any ideas on what else I can try?
Thanks,
Hai Huynh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Based on the fact that the issue stops occuring when testing a different server motherboard as you mentioned, at this point we strongly recommend contacting our support group directly to validate the warranty and replace the board:
http://www.intel.com/content/www/us/en/support/contact-support.html http://www.intel.com/content/www/us/en/support/contact-support.html
![](/skins/images/7FC17B7B85029576C25F1E43CE255B51/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page