Problem with Failover

Javatooo

 

 

Have you got Redundancy State Preference set on the boxes? You can set a box to have a preferred Active or Standby state. Best to stick to None.

 

 

Rgds

 

N

check 'b ha table' from the cli - something is causing the other box not to stay active.

 

Hi,

 

 

Last Friday we didnt´t see any log on the ltm. Today i can see this

 

 

May 30 10:16:37 local/tmm warning tmm[6093]: 01190004:4: address conflict detected for 1.1.1.7 (00:01:d7:b7:46:44) on vlan 330

 

May 30 10:16:37 local/tmm warning tmm[6093]: 01190004:4: address conflict detected for 2.2.2.1 (00:01:d7:b7:46:43) on vlan 301

 

May 30 10:16:37 local/tmm warning tmm[6093]: 01190004:4: address conflict detected for 1.1.1.7 (00:01:d7:b7:46:44) on vlan 330

 

May 30 10:16:37 local/tmm warning tmm[6093]: 01190004:4: address conflict detected for 2.2.2.1 (00:01:d7:b7:46:43) on vlan 301

 

 

There are the floating ips.

 

 

Can anybody help me?

 

 

Thanks

Hi,

 

 

Last Friday we didnt´t see any log on the ltm. Today i can see this

 

 

May 30 10:16:37 local/tmm warning tmm[6093]: 01190004:4: address conflict detected for 1.1.1.7 (00:01:d7:b7:46:44) on vlan 330

 

May 30 10:16:37 local/tmm warning tmm[6093]: 01190004:4: address conflict detected for 2.2.2.1 (00:01:d7:b7:46:43) on vlan 301

 

May 30 10:16:37 local/tmm warning tmm[6093]: 01190004:4: address conflict detected for 1.1.1.7 (00:01:d7:b7:46:44) on vlan 330

 

May 30 10:16:37 local/tmm warning tmm[6093]: 01190004:4: address conflict detected for 2.2.2.1 (00:01:d7:b7:46:43) on vlan 301

 

 

There are the floating ips.

 

 

Can anybody help me?

 

 

Thanks

Hi there,

 

 

Can you give me the output of this commands from both unit:

 

 

[root@czar:Active] config b db |grep -i Failover.Force

 

Failover.ForceActive = disable (they should be disable)

 

Failover.ForceStandby = disable (they should be disable)

 

 

 

[root@czar1cba:Active] config b ha table

 

[root@czar1cba:Active] config b failover list

 

 

The address conflict might be because that both unit has taken the active role in a short period of time. First thing you'll need to check is the state preferences and when you said that "when I forced the failover in the active box", you forced it from GUI?

 

 

I would like to see your configs so that we can see exactly what might have happened, and if you need urgent assistance on this - F5 Support will be the best gateway :) support@f5.com

 

 

Hth,

 

/Czar

Hi Javatooo,

 

as Czar mentioned this happens when both units tend to go active

 

 

Click Here to go to an ask.f5.com Solution article that takes about and ways you can resolve it.

 

 

For example - perhaps you

 

 

I hope this helps

 

Bhattman

I'd open a case on this with F5 Support. They'll be able to review tech.out's from each unit and help diagnose the issue. Troubleshooting this via the forums is going to be slow and incomplete in comparison.

 

 

Aaron

Hi,

 

 

I found the problem. It´s in the peer management address, i wrote 10.10.196.40 and the correct is 10.10.195.40.

 

 

Thanks to all for your time.