Hello,
The workaround was posted above to filter the duplicate IP alarms. Note that you should also add an alarm parameter specifically to filter out only 127.0.0.1 alarms, so that you still get alarms for other duplicate IPs across your devices. See attached image.
You can also turn duplicate IP alarms off completely if you prefer:
1. Stop imcnetresdm process in IDMA
2. Back up $IMC/server/conf/qvdm.conf to the desktop.
3. Edit the file, adding the line at the end of the file:
DupIpConflictAlarm=false
then add another blank line. Save it.
4. Start imcnetresdm process in IDMA
5. Delete all existing IP conflict alarms
However I wouldn't recommend that as you won't get alarms for any duplicate IPs at all anymore.
The issue should be fixed permanently in the next IMC patch release.
------------------------------
Justin Guse
------------------------------
Original Message:
Sent: Jan 10, 2022 04:00 AM
From: Jesper Frydenreich
Subject: E0706P06 Loopback conflict
Any solution for this ?????
------------------------------
Jesper Frydenreich
Original Message:
Sent: Jan 04, 2022 09:44 AM
From: Nicolas Leseignoux
Subject: E0706P06 Loopback conflict
Had the same problem and opened a case.
Support told us that this bug will be corrected in a future patch. For us the workaround was to create a trap filter (Alarm -> Trap Management -> Filtering Trap) with the following details:
and
Regards
Original Message:
Sent: Jan 02, 2022 10:15 PM
From: Jax Dao
Subject: E0706P06 Loopback conflict
We all got the same issue with the latest patch E0706H07.
Million warning alarms of Device IP Conflict relating to the loopback interface 127.0.0.1, which are very frustrating and hilarious in our NMS at the moment.
Stay tuned and calm with HPE/Aruba Development team anyway
------------------------------
Jax Dao
Original Message:
Sent: Dec 14, 2021 03:06 PM
From: Kevin Haldeman
Subject: E0706P06 Loopback conflict
I just upgrade from E0705 to E0706P06 and I'm getting warnings from every device in my network:
Interface InLoopBack0 of device at 10.2.0.212 and interface HP ProCurve Switch software loopback interface of device at 10.3.0.208 have a conflicting IP address 127.0.0.1.
I've never seen this one triggered like this before. I've got hundreds of alarms. How would I go about adding an exception for 127.0.0.1?
Not sure if this is a code flaw or a new "feature"?
------------------------------
Kevin Haldeman
------------------------------