Network Management

 View Only
last person joined: 2 days ago 

Keep an informative eye on your network with IMC and AirWave network management solutions.
Expand all | Collapse all

E0706P06 Loopback conflict

This thread has been viewed 109 times
  • 1.  E0706P06 Loopback conflict

    Posted Dec 14, 2021 03:07 PM
    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
    ------------------------------


  • 2.  RE: E0706P06 Loopback conflict

    Posted Dec 16, 2021 12:09 AM
    I have the same issue you are having.
    Here is what I did to silence the alarm, I went into the alarm and on the right, select Filter this alarm, I gave it a name and saved.  The alarms are not there anymore but I suspect this is just a temporary fix and may block other important alarms if they were to occur.

    Thanks,
    Jeremy

    ------------------------------
    Jeremy OBrien
    ------------------------------



  • 3.  RE: E0706P06 Loopback conflict

    EMPLOYEE
    Posted Dec 16, 2021 03:44 AM
    Hello there,

    I would suggest to open case with support , filtering the alarm is a workaround  , but will not solve the issue!

    Regards,

    ------------------------------
    Marina Milenkova
    ------------------------------



  • 4.  RE: E0706P06 Loopback conflict

    Posted Dec 16, 2021 09:47 AM
    This has to be an issue with E0706P06. I've seen three people report this now. Someone needs to start a support ticket.

    I'd do it, but I can't figure out:
    A.  How to add the iMC product to my support portal, it doesn't seem to find it as a product
    B. Which support portal to use (hpe or aruba)?
    C. I don't pay for support anymore as this is perpetual licensing, I doubt they would take ticket from me.

    I don't want their help really, I just want to report the issue and let them release a new patch.
    Does HP engineering look at these posts?

    ------------------------------
    Kevin Haldeman
    ------------------------------



  • 5.  RE: E0706P06 Loopback conflict

    Posted Dec 17, 2021 10:14 AM

    Same here. Just updated and did the log4j disable in startup.bat.

    saw the error as you mentioned and it wasn't there in E0705P12

    Log4J advisory btw.

    https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-a00120129en_us
     



    ------------------------------
    Claus Andersen
    ------------------------------



  • 6.  RE: E0706P06 Loopback conflict

    Posted Dec 21, 2021 08:49 AM

    Got this message from our Aruba SE.
    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    HPE Intelligent Management Center (IMC) is affected by this CVE-2021-44228. 

    There is a planned E0706P07 patch to protect against this vulnerability. Patch release ETA is yet to be determined.
    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------



    ------------------------------
    Jeremy OBrien
    ------------------------------



  • 7.  RE: E0706P06 Loopback conflict

    EMPLOYEE
    Posted Dec 21, 2021 04:52 AM
    Hello,

    I'm not sure if anyone here has opened a case already, but I can confirm that I've opened one for the issue and it's being investigated.

    ------------------------------
    Justin Guse
    ------------------------------



  • 8.  RE: E0706P06 Loopback conflict

    Posted Dec 28, 2021 12:06 PM
    Would love to hear what support say about this.  I just upgraded to E0706P06 and the number of this alarm is hitting 2.5million on my system.  Don't really want to filter out Device IP Conflict Alarms.

    ------------------------------
    Minh Nguyen
    ------------------------------



  • 9.  RE: E0706P06 Loopback conflict

    Posted Dec 28, 2021 04:48 PM
    How did you clear the mass warnings?  I have about 2.5million warnings about the loopback IP address conflict.  I tried the Process All Alarms and Recover All but keep getting a System is busy message after it spins for a while and nothing clears.  It will take 2 years clearing 200 at a time.

    ------------------------------
    Minh Nguyen
    ------------------------------



  • 10.  RE: E0706P06 Loopback conflict

    Posted Jan 02, 2022 10:15 PM
    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
    ------------------------------



  • 11.  RE: E0706P06 Loopback conflict

    Posted Jan 04, 2022 09:44 AM
    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

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



  • 12.  RE: E0706P06 Loopback conflict

    Posted Jan 10, 2022 04:00 AM
    Any solution for this ?????

    ------------------------------
    Jesper Frydenreich
    ------------------------------



  • 13.  RE: E0706P06 Loopback conflict

    EMPLOYEE
    Posted Jan 10, 2022 05:16 AM
      |   view attached
    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
    ------------------------------



  • 14.  RE: E0706P06 Loopback conflict

    Posted Jan 10, 2022 05:25 AM
    Hello,

    For now I have filtered all duplicate IP alarms out, but as you write, it's not a good solution as I won't see any real IP conflict alarms.

    I hope HP will come out with a patch for this issue ASAP.

    rgds,
    Jesper

    ------------------------------
    Jesper Frydenreich
    ------------------------------



  • 15.  RE: E0706P06 Loopback conflict

    Posted Apr 17, 2022 11:58 PM
    You can remove this temp rule from the version of E0706P11

    ------------------------------
    Jax
    ------------------------------