HP-Proliant-DL380p-Gen8 and the HPE Ethernet 1Gb 4-port 331FLR Adapter damaged

[Timo20201]

Good day,

I have HP-Proliant-DL380p-Gen8 and the HPE Ethernet 1Gb 4-port 331FLR Adapter not working anymore. In fact this is the second Adapter that I have replaced from nearly 6 months. Unfortunately , it is also damaged and I couldn't know why.
I wish you could inform me please about the potantal reasons and how I can protect the new adapter

[support_s]

System recommended content:

1. HPE ProLiant DL580 Gen8 Server - Product Information Reference | HPE Ethernet 1Gb 4-port 331FLR adapter

2. Advisory: HP Ethernet 1Gb 4-port 33x Adapters - NMI May Occur Under Heavy Network Stress After Network Adapter Firmware Is Installed by HP Service Pack for ProLiant (SPP) Version 2013.02.0

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[Cali]

Hi,

the last Gen8 Server was sold in 2016.

How long did you expect, that a Server running 24h a Day should work?

More than 52.500h?

I assume, also the replacing 6 Month Adapter has the same Runtime because they are no longer sold until than end of 2016.

Sorry, I don't see an issue here, but maybe you have too much Voltage on the Cable.

Cali

[Timo20201]

THanks for reply 

The adapter doesn't appear in the system at all

[Timo20201]

Thanks Cali

In fact, the Server running 8h a Day. 

The first one has been demaged in 2021 and we bought new one and replace it, after 6 Month the new Adapter is demaged too.

I want to find out the reason, the underlying causes and how to protect the new Adapter.

thanks in advance

[Sebasbin]

Hi,

Make sure to use known good network cables to connect adapter to the external switch.

Also keep update the adapter firmware to the latest versions .

[Timo20201]

@Sebasbin 

Thanks Sebasbin.

I wish you have a great Day

Could you please tell how this affects the complete breakdown of the Adapter ?

[Sebasbin]

Hi,

The recommendation is to make sure you are running with the latest firmware and use known good cable in order to isolate the issues.

With the available information, we cannot say what is causing the issue.

I would request you to log a support case with HPE to do a detailed investigation including log analysis.