Are you asking about the public IP side? What will happen is the slave box will take the IP of the master box. Say you have .204 and .205 as IP addresses, and you want the .204 to be the master/primary. You setup HA, configure the HA ip's (which differ of course, so they can talk), and then save the HA configuration (which will reset) the MASTER box first, which will come up and start purring away, since it doesnt see any active boxes, so it rightly assumes it is needed in an "up" configuration.
Then you save the SLAVE (.205) box and that will reboot, see the master running, and go into standby. If it does need to "come up" it will assume the MASTERS IP address.
Thx for the answer, actually it was the Internal (administrative) Interface that I was refering to during the installation.
I had a bit of time to test it, and discovered it really doesnt matter if during the Initial Configuration the Internal (administrative) interface has the same IP or not. If following the manual instructions BOTH machines are never on at the same time during the basic configuration.
After configuring the HA part and the Master/Slave both are up, the Internal (administrative) interface on the slave assumes the IP of the master so the point is really Moot [;)]
Thx for the answer, actually it was the Internal (administrative) Interface that I was refering to during the installation.
I had a bit of time to test it, and discovered it really doesnt matter if during the Initial Configuration the Internal (administrative) interface has the same IP or not. If following the manual instructions BOTH machines are never on at the same time during the basic configuration.
After configuring the HA part and the Master/Slave both are up, the Internal (administrative) interface on the slave assumes the IP of the master so the point is really Moot [;)]
