[SOLVED] Strange IP behaviour of server and HPE iLO

[PL-Infra]

I've got two sets of assets with strange behavior. These are two physical Hyper-V Servers:

• server1 - 192.168.100.100
  
• server2 - 192.168.100.102
  

Each with an HPE iLO asset:

• server1ilo - 192.168.100.101
  
• server2ilo - 192.168.100.103
  

Server1 and server2 both run different OS and the version of iLO 2 is 2.33 03/20/2018

Everytime the iLO asset gets scanned, the corresponding server asset changes its IP to the IP of the ilo asset. So server1 will get 192.168.100.101 as IP. As a consequence the asset server1 will get a status of "RPC Server unavailable". Only by changing the IP of server1 I can resolve this (temporary)

How can this be resolved permanently?

[PL-Infra]

Did some additional research on the iLO host using Lansweeper Device Tester (Thanks!):

Scanning SNMP..
ObjectID: 1.3.6.1.4.1.311.1.1.3.1.2
Scanning SNMP for custom OID's..
Valid connection: True
ObjectID: 1.3.6.1.4.1.311.1.1.3.1.2
OID 1.3.6.1.2.1.1.5.0: server1


So this specific setting was causing for issues:
Administration/Settings/Management/
SNMP Pass-thru: Enabled Disabled

When this was changed to Disabled:

Scanning SNMP..
SNMP disabled or wrong community
Scanning SNMP for custom OID's..
Valid connection: True
Stopped: No SysObjectId found

Now, there are no references to server1 when scanning server1ilo