Forum Discussion
Steve_M__153836
Nimbostratus
NimbostratusLooking for Feedback on Configuring Network Mirroring/Failover for LTM v10.2.2
I have a pair of 3600s that are connected via serial cable and also have a directly connected network connection. Below is the current status of each of the High Availability features and what they use. My goal is to get everything going over the network. I used the article below as a reference and was just looking for some confirmation/feedback. Any reason to leave the serial cable in place or should I go this route?
Device 1 MGMT. 192.168.10.15
Device 2 MGMT. 192.168.10.16
Device 1 Direct Network Connection - 10.0.0.1
Device 2 Direct Network Connection - 10.0.0.2
Current
-Configsync
Device 1 Peer - 10.0.0.2
Device 2 Peer - 10.0.0.1
-Network Mirroring (Self-Peer; Primary Addr, Alternate Addr)
Device 1 - N/A, N/A
Device 2 - N/A, N/A
-Network Failover
Device 1 Peer Address - N/A
Device 2 Peer Address - N/A
Proposed
-Configsync
Device 1 Peer - 10.0.0.2
Device 2 Peer - 10.0.0.1
-Network Mirroring (Self-Peer; Primary Addr, Alternate Addr)
Device 1 - 10.0.0.1-10.0.0.2, 192.168.10.15-192.168.10.16
Device 2 - 10.0.0.2-10.0.0.1, 192.168.10.16-192.168.10.15
-Network Failover
Device 1 Peer Address - 192.168.10.16
Device 2 Peer Address - 192.168.10.15
I just wasn't sure if there was any reasons/thoughts on if it should be kept or removed.
i prefer keeping it because, as in askf5 sol, it provides faster failover response time.
Also wanted to make sure I was setting up the configuration correctly.
it looks okay to me. anyway, if you want, you may also add tmm self ip (in addition to mgmt ip) to network failover configuration.
nitass_89166Noctilucent
Any reason to leave the serial cable in place or should I go this route?
you can keep both (hardware and network), can't you?
Steve_M__153836Yes I think you can keep both. This SOL (http://support.f5.com/kb/en-us/solutions/public/2000/300/sol2397.html?sr=34012910) describes the differences and it looks like if you use both then even if the network failover indicates it should fail over, it will not unless the hardware failover is also indicating a failover needs to take place. I just wasn't sure if there was any reasons/thoughts on if it should be kept or removed. Also wanted to make sure I was setting up the configuration correctly.
nitassEmployee
Any reason to leave the serial cable in place or should I go this route?
you can keep both (hardware and network), can't you?
- Steve_M__153836Yes I think you can keep both. This SOL (http://support.f5.com/kb/en-us/solutions/public/2000/300/sol2397.html?sr=34012910) describes the differences and it looks like if you use both then even if the network failover indicates it should fail over, it will not unless the hardware failover is also indicating a failover needs to take place. I just wasn't sure if there was any reasons/thoughts on if it should be kept or removed. Also wanted to make sure I was setting up the configuration correctly.
- nitass
I just wasn't sure if there was any reasons/thoughts on if it should be kept or removed.
i prefer keeping it because, as in askf5 sol, it provides faster failover response time.
Also wanted to make sure I was setting up the configuration correctly.
it looks okay to me. anyway, if you want, you may also add tmm self ip (in addition to mgmt ip) to network failover configuration.
- Steve_M__153836Thanks! I'll look at the self IPs as well.
- nitass_89166
I just wasn't sure if there was any reasons/thoughts on if it should be kept or removed.
i prefer keeping it because, as in askf5 sol, it provides faster failover response time.
Also wanted to make sure I was setting up the configuration correctly.
it looks okay to me. anyway, if you want, you may also add tmm self ip (in addition to mgmt ip) to network failover configuration.
- Steve_M__153836Thanks! I'll look at the self IPs as well.