NimbostratusIn f5 i2800, we can see the hardwired failover port and we have receieved only 4 sfp for two boxes. We will be doing a 2 arm mode deployment so we will be using 2 for ext and int vlan from each box.do you guys suggest going with hardwired failover port for configuring ha?
MVPHi divyaskumar,
you may read the following solution article to see the pros & cons of each method...
https://support.f5.com/csp/article/K2397
In general a Hardwired Failover (with additional Network Failover configuration) is the recommended choice, since the Hardwired Failover supports a faster/better detection. The only downside of a Hardwired Failover is, that it requires you to place the individual units side-by-side in the same rack / fire compartment (max. 50 feet distance is supported).
Note: If you're running out of dedicated interfaces for the Network Failover configuration, then you can also use the INT/EXT production interface (e.g. via an additional VLAN) to establish the Network Failover communication. Well, its not a recommended practise to deploy an intermediate switch into Network Failover communication, but its still a supported scenario and has just very little downsides in combination with a Hardwired Failover setup. In this case the Active/Passive detection takes place over (very stable) Hardwired connection and the remaining stuff (e.g. Informational status exchange) takes place over the (potential unstable) Network Failover connection^^
Cheers, Kai
NimbostratusHi, Serial cable failover seems to be something pretty legacy nowdays. It is just a "voltage heartbeat". You don't need a separate dedicated "ethernet" cable for network failover, your sync/mirror vlans can be trunked inside your physical "arms".