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

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

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Bronze

ARP collision on failover interface of ASA5510

Seeing a funny problem.  Whenver the secondary ASA is rebooted, there is complaint of an ARP conflict on the failover interface:

Received ARP request collision from 169.254.0.1/1cdf.0f2e.e8b6 on interface FAILOVER with existing ARP entry 169.254.0.1/1cdf.0f2e.e0b0

169.254.0.1 is the primary ASA's failover interface, and the physical interface has MAC address 1cdf.0f2e.e0b0

169.254.0.2 is the secondary ASA's failover interface, and the physical interface has MAC address 1cdf.0f2e.e8b6

Failover IPs should remain constant even as roles change, so I'm very puzzled why the secondary would take the primary's IP.

Both are single context running 9.0(3)

Everyone's tags (3)
1 REPLY
New Member

ARP collision on failover interface of ASA5510

Hi Johnny,

The Ip addresses that we assign in failover are for active and standby unit, they are not assigned as primary and secondary units.

So as the role of a unit in the failover pair changes the IP addresses and the MAC also changes accrodingly.

So what you are seeing is normal.

further the same is documented as well:

http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml#acti

Hope this helps,

Cheers,

Naveen

260
Views
0
Helpful
1
Replies