cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

"Hardware changes detected ..." error when restarting OS

tiida
Newcomer

I will post for the first time.

Although the hardware (NIC: Label3) was not changed, an error message was output after the AMD server was restarted and data collection stopped. As a result, Label1 and Label2 data can no longer be collected. The hardware of Label1 and Label2 has not changed.


I want to know the following.

1. Why Label3 hardware recognition changed after AMD server restart

2. Why Label1 and Label2 can no longer collect data


-----------------------------

cmd: rtminst

Network setup:

Default gateway: xx.xx.xx.xx

Hostname: AAAAA

AMD type: Probe HS

Driver type: native


| | Aval. | Link | | | Link | IP /

# | Name | HW type | driver | param. | Mode | Traffic | det. | Label

-| ---------- | ----------- | ----------- | --------- |- ----- | ------- | ------ | --------------

1 | aaa1 | e1000e | Native | default | Comm. | In | Y | AAAAA

2 | aaa2s0 | igb | Native | default | Capt. | In | Y | Label2

3 | aaa4s0! | 8139too | Native | default | Capt. | In | Y | Label3

4 | aaa5s0 | e1000e | Native | default | Capt. | In | Y | Label1

(*)-changed since last refresh

port type colors: capture, communication, IP assigned, IP DHCP, other


-Problems:

Error: Hardware changes detected aaa4s0: 10ec: 8169-> 10ec: 8129, use M to reconfigure ports

-----------------------------


Best Regards,

Takayuki Iida


1 REPLY 1

Erik_Soderquist
Dynatrace Pro
Dynatrace Pro

Did you recently update your RHEL/CentOS? There is a known issue with one of the updates that reshuffles how the networking hardware is identified.


-- Erik