Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Strange IP with Cisco 2710 location apppliance


We've set up a Cisco 2710 location appliance.

The appliance has the ip address

Looking at the core switch where this appliance is connected to, we saw a lot of duplicated address with IP

We tried to disable the thernet port where the location is connected to, and the duplicated address stopped. So we are sure that the ip address is generated by the location appliance.

The fact strange is that the ip address is not present in the interfaces of the appliance, and is not configured anywhere....

Moreover, the mac-address associated to is different from the mac-address of the real location ip (in my case

Any idea?



Re: Strange IP with Cisco 2710 location apppliance

You say that the address is a duplicate address. So, is it used anywhere else in the network. Can you post the location appliance cofiguration? We need to see what is causing this issue.

New Member

Re: Strange IP with Cisco 2710 location apppliance

I've also open a TAC case, but no solution yet.

The ip address is duplicated because the switch where the location app is connected to has that ip address (it's the core switch of the net).

The eth0 of the appliance is directly connected to the GigabitEthernet5/2 of this switch, and look at this:

sw-core#sh mac-address-table | inc GigabitEthernet5/2

1 0016.3656.68c2 dynamic ip GigabitEthernet5/2

1 0016.3656.69ae dynamic ip GigabitEthernet5/2

Two different mac address are coming from that port. One (0016.3656.68c2) is the mac address related to the ip address correctly configured in the eth0 ifup config, and the other one is probably related to the IP address duplicated that is configured nowhere....

Moreover, that mac address (and interface) doesn't appears if I do an ifconfig....

I've discovered another interesting thing: this doesn't happen if I use the eth1 port...

So, I think there is something strange binded to the eth0, but I cannot find it anywhere in the machine.