Changing Management IP of Active BIG-IP caused both Big-IPs to become Ative

Hi,

Thanks, yes the Standby LTM has the peer management address set to the managment IP address of the Active LTM but the Active LTM has the peer management address set to the ip address of the dedicated interface we use for the network failover.

The settings are as follows.

ACTIVE LTM

Peer Management Address: 192.168.254.3 ( (Dedicated hearbeat interface of Standby LTM)

Configuration Identifier: f5-int-ltm-sync-unicast

Local Address: 192.168.254.2 (Dedicated hearbeat interface)

Remote Address: 192.168.254.3 (Dedicated hearbeat interface

Port: 1026

STANDBY LTM

Peer Management Address: 10.128.81.43 (Management IP Address of Active LTM)

Configuration Identifier: f5-int-ltm-sync-unicast

Local Address: 192.168.254.3 (Dedicated hearbeat interface)

Remote Address: 192.168.254.2 (Dedicated hearbeat interface)

Port: 1026

So there appears to be some difference in the configuration of each LTM. Would the preference be to change the Peer Management of the Standby LTM to the Dedicated hearbeat interface of the Active LTM and when i do this should I force the Standby LTM offline while I make these changes? What I would also like to do is add the management interfaces as a secondary interface for network failover monitoring so we have two just so any problem affecting the decicated hearbeat interfaces doesn't cause a failover.

Does this sound OK?

Thanks for your help

He does. A TMM interface is any interface that isn't the management interface (i.e. a switch port) and thus a TMM IP address is any IP address not assigned to the management interface (i.e. configured under Network not Platform). Apologies if this sounds a bit snotty, I can't think of a better way of putting it without losing the detail. =]