artioml/f5-azure-ha

:cloud: F5 High Availability in Microsoft Azure

f5-azure-ha's Issues

ARM Async Operation Status

InProgress for up to 3 minutes!

vmF5B

• License
• Configuration

stdout - Change Verification

If run interactively - verify failover actions.

Script Execution

Run the script based on a syslog message (monitor down):

https://support.f5.com/kb/en-us/solutions/public/14000/300/sol14397.html

https://support.f5.com/kb/en-us/solutions/public/11000/900/sol11900.html

Instance Metadata

https://azure.microsoft.com/en-us/blog/what-just-happened-to-my-vm-in-vm-metadata-service/?cdn=disable

Supported Topologies Drawing

funUpdUDR() Exit Code

Non-zero on No update needed.

LBAZ Name

Option to specify LBAZ name.

funUpdUDR Exit Codes

No NICs Scenario

• If no NICs in the backend pool for some reason - add your own.
• Divide funFailover into sub-functions

LBAZ / UDR modes

Consider adding two different, selectable modes for funCurState() and funFailover():

• LBAZ in front of the BIG-IP
• FW in front, using UDR to route to the BIG-IP

Exit Codes

class clsExCodes:
    intArgs = 8
    intArmAuth = 4

• Numbering
• Add more

funFailover

Noop when local state is not Standby.

Local IP Detection

Wrong local IP detected when tested from an external F5 (not part of the HA pair)

Config Lock

Lock configuration while making ARM changes to prevent conflicts.