Wired Intelligent Edge

 View Only
  • 1.  Duplicate IP address warning

    Posted Oct 01, 2017 02:31 AM

    Hi all,

    I am using Aruba core switch 5406zl , Every day I see the  following  warning

    IPv4: Duplicate IPv4 address 192.168.1.1 is detected on port 1/C7 in VLAN2 with a MAC address of xxxxxxxx.

    I have checked the switch connected on this port there is no duplicate IP Address.

     

    Note: mac address xxxxxx this for Core switch 

    IP address 192.168.1.1 this gateway for vlan 2 on Core switch.

     

    Thanks



  • 2.  RE: Duplicate IP address warning

    Posted Oct 03, 2017 01:46 AM

    any insight?

     



  • 3.  RE: Duplicate IP address warning

    Posted Oct 06, 2017 07:26 AM

    Hi,

    please clarify your topology a little bit. Do you get this log message on the core switch, that has this IP? If yes, where does the interface C7 lead to? 

    Please enter the following on the core and on the switch, that logs the message:

    show arp | include 192.168.1.1

    What does it return?



  • 4.  RE: Duplicate IP address warning

    Posted Oct 11, 2017 10:29 AM

    Thanks for response 

    yes i got message in core switch 

    belwo  Arp command result :

    show arp | include 192.168.1.1
    192.168.1.100 xx089b-xxxxx dynamic Trk3
    192.168.1.102 xxfeb5-xxxxx dynamic Trk2
    192.168.1.106 xx23ae-xxxxx dynamic Trk2
    192.168.1.109 xxbeb-xxxxx dynamic Trk2



  • 5.  RE: Duplicate IP address warning

    Posted Oct 11, 2017 10:40 AM

    My network topology straight
    All client switches connected to the core switch(uplink).

    Note: This message appears only in early morning or late at night
    But never appear during working hours.

    Thanks



  • 6.  RE: Duplicate IP address warning

    Posted Jan 23, 2020 02:57 PM

    Do you know ended up happening with this issue you had?  I'm having the exact same thing going on where the 5406 reports a duplicate IP address out a specific port with it's own mac-address on it.  

    Spent 2 hours with an engineer and then a senior engineer who also didn't quite know what would be causing it as everything seems to be configured correctly.  Was hoping you had resolved and could share what it may have been though it was years ago.