problem with NIC of DL 360 g4.

[Melvin C. Ladra]

Hi, our company is reseller of HP and we have client here that have a problem with their servers. Most of their NIC has a problem and we diagnosed it and isolated the problem. We resulted to recommend to replace the system board of their server since its all built-in on system board the NICs. This problem recurs on our client.would like to know if there is an batch issues on DL 360 G4 servers? THanks

[Steven Clementi]

Melvin:

Can you explain what the problem is? There are several issues that I can think of regarding NIC's and DL380's that are't really issues at all, just normal operation.


Is this the first DL380G4 the client has in his/her environment?



Steven

[Melvin C. Ladra]

Hi Steven,


Our client reported a series of problems on their servers. We visited their servers to isolate the problem. Here are the procedures we did.


1. We PING the gateway using the NIC 1 and resulted us to request time out.
2. We PING the gateway using the NIC 2 and we receive a reply.
3. Then we use the patch cable used by NIC2 on NIC1 and PING the gateway. Again we could not receive any reply from the gateway.
4. We also test the patch cable of NIC 1 and use it on NIC2 then perform PING to test the connection with gateway.
5. Checked the status of the NIC on hardware and it display working properly.
6. We also used another server and perform the same procedure just to isolate the problem to test the connectivity with the router and the patch cable. So far it resulted that all devices are all working.

These procedures were also done to those 4 other server with problem with connectivity.


Therefore we conclude that the problem is in the NIC and we recommend replacing the system board since the NIC is built-in part of the system board.


They bought their servers last December 2004. Would like to know if there any possible batch problem with these servers? Because there are other DL360 G4 which dont have any problem with their NIC since it was installed .

[Frank Humeau]

This issue is most likely caused by the NIC teaming. We have the same issue here and if you unteam the nics, everything works fine. It's part of the "Large Send Offload" issue that HP has with their NIC teaming which hasn't been fixed yet.