**** 𝐈𝐦𝐩𝐨𝐫𝐭𝐚𝐧𝐭 𝐓𝐢𝐩𝐬 𝐀𝐛𝐨𝐮𝐭 𝐅𝟓 𝐇𝐢𝐠𝐡-𝐀𝐯𝐚𝐢𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲 𝐒𝐜𝐞𝐧𝐚𝐫𝐢𝐨 ****

 Here, I am going to share some Important Tips which could help you as F5 𝐀𝐝𝐦𝐢𝐧𝐢𝐬𝐭𝐫𝐚𝐭𝐨𝐫 once you want to plan for "𝐇𝐢𝐠𝐡-𝐀𝐯𝐚𝐢𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲" Configuration on F5 TMOS. Hope these notes could be helpful for you guys.

⊛ The 𝐓𝐌𝐎𝐒 𝐯𝐞𝐫𝐬𝐢𝐨𝐧 on all Peers MUST be the Same
⊛ In "𝐒𝐲𝐧𝐜-𝐅𝐚𝐢𝐥𝐨𝐯𝐞𝐫" Model, it's possible to Gorup up to "𝟖" TMOS
⊛ Each TMOS can be the Member of Just ONE "𝐒𝐲𝐧𝐜-𝐅𝐚𝐢𝐥𝐨𝐯𝐞𝐫" Device-Group, at any time
⊛ In "𝐒𝐲𝐧𝐜-𝐎𝐧𝐥𝐲" Model, it's possible to Group up to "𝟑𝟐" TMOS
⊛ You have to Make decision about three Important Parameters, including: "𝐂𝐨𝐧𝐟𝐢𝐠𝐒𝐲𝐧𝐜 𝐒𝐞𝐥𝐟-𝐈𝐏 (Single-choice)", "𝐍𝐞𝐭𝐰𝐨𝐫𝐤 𝐅𝐚𝐢𝐥𝐨𝐯𝐞𝐫 𝐈𝐧𝐭𝐞𝐫𝐟𝐚𝐜𝐞 (Multi-choice)", and "𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧 𝐌𝐢𝐫𝐫𝐨𝐫𝐢𝐧𝐠 𝐒𝐞𝐥𝐟-𝐈𝐏 (Multi-choice)"
⊛ The "𝐇𝐚𝐫𝐝𝐰𝐢𝐫𝐞𝐝 𝐅𝐚𝐢𝐥𝐨𝐯𝐞𝐫" is ONLY usable once you want to have "𝐀𝐜𝐭𝐢𝐯𝐞/𝐒𝐭𝐚𝐧𝐝𝐛𝐲" Failover model, and 𝐉𝐔𝐒𝐓 𝐛𝐞𝐭𝐰𝐞𝐞𝐧 𝐓𝐖𝐎 "𝐁𝐈𝐆-𝐈𝐏" 𝐃𝐞𝐯𝐢𝐜𝐞𝐬
⊛ On the other hand, the "𝐍𝐞𝐭𝐰𝐨𝐫𝐤 𝐅𝐚𝐢𝐥𝐨𝐯𝐞𝐫" is usable on both "𝐀/𝐀" and "𝐀/𝐒" Failover models, and between 𝐃𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭 𝐏𝐥𝐚𝐭𝐟𝐨𝐫𝐦𝐬!
⊛ You can use both the "𝐇𝐚𝐫𝐝𝐰𝐢𝐫𝐞𝐝 𝐅𝐚𝐢𝐥𝐨𝐯𝐞𝐫" and "𝐍𝐞𝐭𝐰𝐨𝐫𝐤 𝐅𝐚𝐢𝐥𝐨𝐯𝐞𝐫" models at the same time; In such situations, the Logical Operator would be "𝐀𝐍𝐃" between them to fire the "Failover Condition"...
⊛ To configure "𝐃𝐞𝐯𝐢𝐜𝐞 𝐓𝐫𝐮𝐬𝐭" Relationship between Peers, You have to use the Credential of either "𝐀𝐝𝐦𝐢𝐧" or "𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞 𝐀𝐝𝐦𝐢𝐧" User
⊛ You can configure up to "𝟏𝟐𝟕" 𝐓𝐫𝐚𝐟𝐟𝐢𝐜-𝐆𝐫𝐨𝐮𝐩𝐬
⊛ In case of implementing "𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧-𝐌𝐢𝐫𝐨𝐫𝐫𝐢𝐧𝐠" feature, TMOS leverages the Port Numbers "𝐓𝐂𝐏 𝟏𝟎𝟐𝟗 - 𝟏𝟏𝟓𝟓" on the Involved Self-IP(s) automatically for the configured Traffic-Group(s)
⊛ Using "𝐅𝐨𝐫𝐜𝐞 𝐭𝐨 𝐒𝐭𝐚𝐧𝐝𝐛𝐲" or "𝐅𝐨𝐫𝐜𝐞 𝐎𝐟𝐟𝐥𝐢𝐧𝐞" could be so practical once you are going to have "Device Maintenance/Upgrade"