{"id":570,"date":"2012-06-01T00:00:00","date_gmt":"2012-06-01T00:00:00","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2012\/06\/01\/f5-ltm-ha\/"},"modified":"2021-07-31T18:32:28","modified_gmt":"2021-07-31T18:32:28","slug":"f5-ltm-ha","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html","title":{"rendered":"BigIP F5 LTM &#8211; High Availability (v10.x)"},"content":{"rendered":"<p>The F5 LTM provides the ability to configure a HA (High-Availability) based setup. Configuring HA ensures that traffic is still processed even in the event of a failure (such as a software or hardware).<br \/>\nWithin this article we will explain and discuss a Active \/ Standby HA F5 setup. This allows one unit to pass traffic (Active) whilst the other acts as standby ready to take the role of active should a fail-over event occur.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_65 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<p class=\"ez-toc-title\">Table of Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-662d37b4cb8a2\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-662d37b4cb8a2\"  aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#Communication\" title=\"Communication\">Communication<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#Communication_Types\" title=\"Communication Types\">Communication Types<\/a><\/li><\/ul><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#HA_Table\" title=\"HA Table\">HA Table<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#Failover_Triggers\" title=\"Failover Triggers\">Failover Triggers<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#Stateful_Failover\" title=\"Stateful Failover\">Stateful Failover<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#MAC_Masquerading\" title=\"MAC Masquerading\">MAC Masquerading<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#Configuration_Example\" title=\"Configuration Example\">Configuration Example<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#Unit_1_%E2%80%93_Primary\" title=\"Unit 1 &#8211; Primary\">Unit 1 &#8211; Primary<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#Unit_2_%E2%80%93_Standby\" title=\"Unit 2 &#8211; Standby \n\">Unit 2 &#8211; Standby \n<\/a><\/li><\/ul><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#Configuration_Options\" title=\"Configuration Options\">Configuration Options<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#Commands\" title=\"Commands\">Commands<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\/#Files\" title=\"Files\">Files<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"Communication\"><\/span><strong>Communication<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>There are 2 HA communication methods. These methods provide the mechanism for which each node determines whether they should be placed into an Active or Standby status.<strong><br \/>\n<\/strong><\/p>\n<p><strong>Hardware Failover<\/strong> &#8211; Each F5 LTM provides a front panel port for which a failover cable can be used to interconnect both systems. The failover cable is a specially pinned BD9 cable and is only used to pass a voltage (which the active system supplies). If the backup device detects that there is no voltage on its corresponding port the failover mechanism is initiated.<br \/>\n<strong>Network Failover<\/strong> &#8211; Network failover overcomes the ~50 ft cable limitation imposed with Hardware failover. A network pulse is sent via UDP 1026. If the back device does not receive the network pulse within the given time period then the failover mechanism is initiated.<\/p>\n<p>Network failover is configured within &#8216;System \/ High Availability \/ Network Failover&#8217;.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"Communication_Types\"><\/span><strong>Communication Types<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>There are 3 types of network communication that can occur between a BIG-IP LTM pair. These are:<\/p>\n<p><strong>Synchronisation<\/strong> (of configuration) between nodes via TCP 443.<br \/>\n<strong>Mirroring<\/strong> (connections and persistence) information via TCP 1028.<br \/>\n<strong>Network failover<\/strong> uses UDP 1026.<\/p>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"HA_Table\"><\/span><strong>HA Table<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Failed events are written to the HA table. Processes monitor this table continuously for failed instances and the necessary action is taken. These actions are configured with the High Availability feature options.<\/p>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"Failover_Triggers\"><\/span><strong>Failover Triggers<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>There are\u00a0 numerous events that are monitored. Such as :<\/p>\n<p><strong>Daemon Heartbeats<\/strong> \u2013 By default six of the core LTM daemons are monitored. In the event of failure the daemon is either restarted or the device is rebooted. The defaults can be configured via \u2018System &gt; High Availability &gt; Failsafe &gt; System Servcies\u2019<br \/>\n<strong>VLAN Failsafe<\/strong> \u2013 When enabled traffic transversing the VLAN is monitored. BigIP also initiates traffic (ICMP Echo`s) in an attempt to receive\/generate traffic. If no traffic is received on the VLAN (within the given time period) the designated action is taken.<br \/>\n<strong>Switchports<\/strong> \u2013 The switchboard is monitored. If an error is detected the Traffic Management process is aborted.<\/p>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"Stateful_Failover\"><\/span><strong>Stateful Failover<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Stateful failover ensures that each device has a copy of the state information (such as connection information, persistence data etc). At the point of failover connections through the newly prompted node can continue.<\/p>\n<p><em><strong>Note<\/strong><\/em> : It is also worth noting that mirroring is enabled on a per profile basis.<\/p>\n<p><strong>Mirroring<\/strong> &#8211; Mirroring is the feature used to synchronise the active devices real time connection and\/or persistence state information to the standby system.<br \/>\n<strong>Connection Mirroring<\/strong> &#8211; Connection mirroring is enabled on a per virtual server basis and is disabled by default (due to the overhead required).<br \/>\n<strong>Persistence Mirroring<\/strong> &#8211; Though Persistence Monitoring is disabled by default it typically should always be enabled apart from when cookie persistence is being used.<br \/>\n<strong>SNAT Connection Mirroring<\/strong> &#8211; SNAT mirroring is configured from within each SNAT. The active system must keep track of the ports and connections held within the connection table. In the event of failover the newly promoted node must have a copy of these records to ensure that SNAT connections are maintained.<\/p>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"MAC_Masquerading\"><\/span><strong>MAC Masquerading<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>At the point of failover BIGIP sends a gratuitous ARP to ensure that neighbouring ARP caches are updated. This however can cause issues when the gratuitous ARP is ignored and subsequent traffic is sent to the old MAC address. MAC Masquerading allows the BIGIP to maintain a virtual MAC address for each VLAN.<br \/>\nMAC Masquerading is configured via the &#8216;VLAN \/ Advanced&#8217; configuration section. A typical value that is used when configuring MAC Masquerading is to set the first byte of the MAC address to 0x02 i.e if the MAC address of one of your systems is 00:00:00:00:00:01 the Masqueraded MAC address would be 02:00:00:00:00:01.<\/p>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"Configuration_Example\"><\/span><strong>Configuration Example<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Within this example we will configure a HA setup using network failover.<\/p>\n<pre>Note : The following configuration settings were pulled from the bigip.conf and bigip_base.conf configuration files.\r\n\r\n##################\r\n##### UNIT 1 #####\r\n##################\r\n\r\nself 172.16.1.80 {\r\n   netmask 255.255.255.0\r\n   unit 1\r\n   floating enable\r\n   vlan EXTERNAL\r\n   allow all\r\n}\r\nself 192.168.1.80 {\r\n   netmask 255.255.255.0\r\n   unit 1\r\n   floating enable\r\n   vlan INTERNAL\r\n   allow all\r\n}\r\nconfigsync {\r\n   auto detect enable\r\n}\r\nmgmt 2.2.2.2 {\r\n   netmask 255.255.255.0\r\n}\r\nvlan EXTERNAL {\r\n   tag 4094\r\n   failsafe enable\r\n   timeout 10\r\n   failsafe failover\r\n   interfaces 1.1\r\n}\r\nvlan INTERNAL {\r\n   tag 4093\r\n   failsafe enable\r\n   timeout 10\r\n   failsafe failover\r\n   interfaces 1.2\r\n}\r\nself 172.16.1.70 {\r\n   netmask 255.255.255.0\r\n   vlan EXTERNAL\r\n   allow all\r\n}\r\nself 192.168.1.70 {\r\n   netmask 255.255.255.0\r\n   vlan INTERNAL\r\n   allow all\r\n}\r\nfailover {\r\n   force active disable\r\n   peer mgmt addr 1.1.1.1\r\n   unicast peer F5HA {\r\n         dest addr 172.16.1.71\r\n         port 1026\r\n         source addr 172.16.1.70\r\n      }\r\n}\r\nstatemirror {\r\n   addr 172.16.1.70\r\n   peer addr 172.16.1.71\r\n}\r\nsystem {\r\n   gui setup disable\r\n   hostname \"bigip1-unit1.home\"\r\n}\r\n\r\n##################\r\n##### UNIT 2 #####\r\n##################\r\n\r\nself 172.16.1.80 {\r\n   netmask 255.255.255.0\r\n   unit 1\r\n   floating enable\r\n   vlan EXTERNAL\r\n   allow all\r\n}\r\nself 192.168.1.80 {\r\n   netmask 255.255.255.0\r\n   unit 1\r\n   floating enable\r\n   vlan INTERNAL\r\n   allow all\r\n}\r\nconfigsync {\r\n   auto detect enable\r\n}\r\nmgmt 1.1.1.1 {\r\n   netmask 255.255.255.0\r\n}\r\nvlan EXTERNAL {\r\n   tag 4093\r\n   failsafe enable\r\n   timeout 10\r\n   failsafe failover\r\n   interfaces 1.1\r\n}\r\nvlan INTERNAL {\r\n   tag 4094\r\n   failsafe enable\r\n   timeout 10\r\n   failsafe failover\r\n   interfaces 1.2\r\n}\r\nself 172.16.1.71 {\r\n   netmask 255.255.255.0\r\n   vlan EXTERNAL\r\n   allow all\r\n}\r\nself 192.168.1.71 {\r\n   netmask 255.255.255.0\r\n   vlan INTERNAL\r\n   allow all\r\n}\r\nfailover {\r\n   force standby disable\r\n   peer mgmt addr 2.2.2.2\r\n   unit 2\r\n   unicast peer F5HA {\r\n         dest addr 172.16.1.70\r\n         port 1026\r\n         source addr 172.16.1.71\r\n      }\r\n}\r\nstatemirror {\r\n   addr 172.16.1.71\r\n   peer addr 172.16.1.70\r\n}\r\nsystem {\r\n   gui setup disable\r\n   hostname \"bigip1-unit2.home\"\r\n}\r\n<\/pre>\n<h4><span class=\"ez-toc-section\" id=\"Unit_1_%E2%80%93_Primary\"><\/span><strong>Unit 1 &#8211; Primary<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p><strong>Set Redundancy \/ Unit ID<\/strong><\/p>\n<ol>\n<li>Within &#8216;System \/ Platform \/ General Properties&#8217; set the High Availability to &#8216;Redundant Pair&#8217;.<\/li>\n<li>Within &#8216;System \/ Platform \/ General Properties&#8217; set the Unit ID to &#8216;1&#8217;.<\/li>\n<\/ol>\n<p><strong>Set Floating IP`s<\/strong><\/p>\n<ol>\n<li>Within &#8216;Network \/ Self IPs&#8217; create a new self IP. This will act as a VIP. Add the IP \/ Netmask and select Floating IP along with a Unit ID of &#8216;1&#8217;.<\/li>\n<\/ol>\n<p><strong>Set Failover Options<\/strong><\/p>\n<ol>\n<li>Within &#8216;System \/ High Availability \/ Network Failover&#8217; and enable Network Failover along with adding the peer management IP address (note this must exactly match the peer management IP address other wise both units will become active). Within the unicast section configure the following settings:<\/li>\n<\/ol>\n<p>&#8211; Configuration Identifier: F5HA<br \/>\n&#8211; Local Address: &lt;LOCAL IP ADDRESS&gt;<br \/>\n&#8211; Remote Address: &lt;PEER IP ADDRESS&gt;<br \/>\n&#8211; Port: 1026<\/p>\n<h4><span class=\"ez-toc-section\" id=\"Unit_2_%E2%80%93_Standby\"><\/span><strong>Unit 2 &#8211; Standby<br \/>\n<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p><strong>Set Redundancy \/ Unit ID<\/strong><\/p>\n<ol>\n<li>Within &#8216;System \/ Platform \/ General Properties&#8217; set the High Availability to &#8216;Redundant Pair&#8217;.<\/li>\n<li>Within &#8216;System \/ Platform \/ General Properties&#8217; set the Unit ID to &#8216;2&#8217;.<\/li>\n<\/ol>\n<p><strong>Set Floating IP`s<\/strong><\/p>\n<ol>\n<li>Within &#8216;Network \/ Self IPs&#8217; create a new self IP. This will act as a VIP. Add the IP \/ Netmask and select Floating IP along with a Unit ID of &#8216;1&#8217;.<\/li>\n<\/ol>\n<p><strong>Set Failover Options<\/strong><\/p>\n<ol>\n<li>Within &#8216;System \/ High Availability \/ Network Failover&#8217; and enable Network Failover along with adding the peer management IP address (note this must exactly match the peer management IP address other wise both units will become active). Within the unicast section configure the following settings:<\/li>\n<\/ol>\n<p>&#8211; Configuration Identifier: F5HA<br \/>\n&#8211; Local Address: &lt;LOCAL IP ADDRESS&gt;<br \/>\n&#8211; Remote Address: &lt;PEER IP ADDRESS&gt;<br \/>\n&#8211; Port: 1026<\/p>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"Configuration_Options\"><\/span><strong>Configuration Options<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Below details the various configuration options available from within System \/ High Availability via the Web UI.<\/p>\n<p><strong>Redundancy<\/strong> &#8211; General Properties such as state preference etc.<br \/>\n<strong>ConfigSync<\/strong> &#8211; Defines how the configuration is synchronized between nodes.<br \/>\n<strong>Network Failover<\/strong> &#8211; Defines the parameters for Network Failover (standby unit determining the status of the active unit).<br \/>\n<strong>Network Mirroring<\/strong> &#8211; Defines the addresses that are used to mirror connections and session persistence records between the systems.<br \/>\n<strong>HA Group<\/strong> &#8211; Defines the parameters for configuring a HA group. An HA group is a set of trunks, pools, or clusters (or any combination of these) that you want the BIG-IP system to use to calculate an overall health score for a unit in a redundant system configuration<br \/>\n<strong>Fail-safe<\/strong> &#8211; Defines the various Failover Triggers. Such as VLAN Failsafe, Daemon Heartbeats etc.<\/p>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"Commands\"><\/span><strong>Commands<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Below shows some of the main commands that can be used to administer HA from the command line.<\/p>\n<p><em>(tmsh)<br \/>\n<\/em><strong>run sys config-sync &#8211; <\/strong>push\/sync config to peer<em> <strong><br \/>\n<\/strong><\/em><\/p>\n<p><em>(bigpipe)<br \/>\n<\/em><strong>bigtop<\/strong> &#8211; Confirm system state<br \/>\n<strong>b failover standby<\/strong> &#8211; Force to standby mode<br \/>\n<strong>b ha table<\/strong> &#8211; show ha table<br \/>\n<strong>b ha table failures<\/strong> &#8211; show ha table failures<br \/>\n<strong>b config sync all<\/strong> &#8211; sync configuration<\/p>\n<h2 class=\"h3\"><span class=\"ez-toc-section\" id=\"Files\"><\/span><strong>Files<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The main crux of the HA configuration settings are defined within the file &#8216;bigip_base.conf&#8217;. It is important to note that this file is not synchronized between systems.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The F5 LTM provides the ability to configure a HA (High-Availability) based setup. Configuring HA ensures that traffic is still processed even in the event of a failure (such as a software or hardware). Within this article we will explain and discuss a Active \/ Standby HA F5 setup. This allows one unit to pass &#8230; <a title=\"BigIP F5 LTM &#8211; High Availability (v10.x)\" class=\"read-more\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\" aria-label=\"Read more about BigIP F5 LTM &#8211; High Availability (v10.x)\">Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v22.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>BigIP F5 LTM - High Availability (v10.x) - Fir3net<\/title>\n<meta name=\"description\" content=\"The F5 LTM provides the ability to configure a HA (High-Availability) based setup. Configuring HA ensures that traffic is still processed even in the\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BigIP F5 LTM - High Availability (v10.x) - Fir3net\" \/>\n<meta property=\"og:description\" content=\"The F5 LTM provides the ability to configure a HA (High-Availability) based setup. Configuring HA ensures that traffic is still processed even in the\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\" \/>\n<meta property=\"og:site_name\" content=\"Fir3net\" \/>\n<meta property=\"article:published_time\" content=\"2012-06-01T00:00:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-07-31T18:32:28+00:00\" \/>\n<meta name=\"author\" content=\"Rick Donato\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Rick Donato\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\"},\"author\":{\"name\":\"Rick Donato\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037\"},\"headline\":\"BigIP F5 LTM &#8211; High Availability (v10.x)\",\"datePublished\":\"2012-06-01T00:00:00+00:00\",\"dateModified\":\"2021-07-31T18:32:28+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\"},\"wordCount\":1192,\"publisher\":{\"@id\":\"https:\/\/www.fir3net.com\/#organization\"},\"articleSection\":[\"F5 Loadbalancers\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\",\"url\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\",\"name\":\"BigIP F5 LTM - High Availability (v10.x) - Fir3net\",\"isPartOf\":{\"@id\":\"https:\/\/www.fir3net.com\/#website\"},\"datePublished\":\"2012-06-01T00:00:00+00:00\",\"dateModified\":\"2021-07-31T18:32:28+00:00\",\"description\":\"The F5 LTM provides the ability to configure a HA (High-Availability) based setup. Configuring HA ensures that traffic is still processed even in the\",\"breadcrumb\":{\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.fir3net.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Networking\",\"item\":\"https:\/\/www.fir3net.com\/networking\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Loadbalancers\",\"item\":\"https:\/\/www.fir3net.com\/networking\/loadbalancers\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"F5 Loadbalancers\",\"item\":\"https:\/\/www.fir3net.com\/networking\/loadbalancers\/f5-big-ip\"},{\"@type\":\"ListItem\",\"position\":5,\"name\":\"BigIP F5 LTM &#8211; High Availability (v10.x)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.fir3net.com\/#website\",\"url\":\"https:\/\/www.fir3net.com\/\",\"name\":\"Fir3net\",\"description\":\"Keeping you in the know\",\"publisher\":{\"@id\":\"https:\/\/www.fir3net.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.fir3net.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.fir3net.com\/#organization\",\"name\":\"Fir3net\",\"url\":\"https:\/\/www.fir3net.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png\",\"contentUrl\":\"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png\",\"width\":390,\"height\":88,\"caption\":\"Fir3net\"},\"image\":{\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037\",\"name\":\"Rick Donato\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.fir3net.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g\",\"caption\":\"Rick Donato\"},\"description\":\"Rick Donato is a Network Automation Architect\/Evangelist and the founder of Packet Coders.\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BigIP F5 LTM - High Availability (v10.x) - Fir3net","description":"The F5 LTM provides the ability to configure a HA (High-Availability) based setup. Configuring HA ensures that traffic is still processed even in the","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html","og_locale":"en_US","og_type":"article","og_title":"BigIP F5 LTM - High Availability (v10.x) - Fir3net","og_description":"The F5 LTM provides the ability to configure a HA (High-Availability) based setup. Configuring HA ensures that traffic is still processed even in the","og_url":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html","og_site_name":"Fir3net","article_published_time":"2012-06-01T00:00:00+00:00","article_modified_time":"2021-07-31T18:32:28+00:00","author":"Rick Donato","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Rick Donato","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html#article","isPartOf":{"@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html"},"author":{"name":"Rick Donato","@id":"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037"},"headline":"BigIP F5 LTM &#8211; High Availability (v10.x)","datePublished":"2012-06-01T00:00:00+00:00","dateModified":"2021-07-31T18:32:28+00:00","mainEntityOfPage":{"@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html"},"wordCount":1192,"publisher":{"@id":"https:\/\/www.fir3net.com\/#organization"},"articleSection":["F5 Loadbalancers"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html","url":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html","name":"BigIP F5 LTM - High Availability (v10.x) - Fir3net","isPartOf":{"@id":"https:\/\/www.fir3net.com\/#website"},"datePublished":"2012-06-01T00:00:00+00:00","dateModified":"2021-07-31T18:32:28+00:00","description":"The F5 LTM provides the ability to configure a HA (High-Availability) based setup. Configuring HA ensures that traffic is still processed even in the","breadcrumb":{"@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/f5-ltm-ha.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.fir3net.com\/"},{"@type":"ListItem","position":2,"name":"Networking","item":"https:\/\/www.fir3net.com\/networking"},{"@type":"ListItem","position":3,"name":"Loadbalancers","item":"https:\/\/www.fir3net.com\/networking\/loadbalancers"},{"@type":"ListItem","position":4,"name":"F5 Loadbalancers","item":"https:\/\/www.fir3net.com\/networking\/loadbalancers\/f5-big-ip"},{"@type":"ListItem","position":5,"name":"BigIP F5 LTM &#8211; High Availability (v10.x)"}]},{"@type":"WebSite","@id":"https:\/\/www.fir3net.com\/#website","url":"https:\/\/www.fir3net.com\/","name":"Fir3net","description":"Keeping you in the know","publisher":{"@id":"https:\/\/www.fir3net.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.fir3net.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.fir3net.com\/#organization","name":"Fir3net","url":"https:\/\/www.fir3net.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png","contentUrl":"https:\/\/www.fir3net.com\/wp-content\/uploads\/Fir3net-Background-Logo-compressed.png","width":390,"height":88,"caption":"Fir3net"},"image":{"@id":"https:\/\/www.fir3net.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.fir3net.com\/#\/schema\/person\/ab35009601b7687ee1c5310be6038037","name":"Rick Donato","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.fir3net.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d75d69a54c0ca3b32c24c3a9703b623c?s=96&d=mm&r=g","caption":"Rick Donato"},"description":"Rick Donato is a Network Automation Architect\/Evangelist and the founder of Packet Coders."}]}},"_links":{"self":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/posts\/570"}],"collection":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/comments?post=570"}],"version-history":[{"count":0,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/posts\/570\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/media?parent=570"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/categories?post=570"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fir3net.com\/wp-json\/wp\/v2\/tags?post=570"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}