f5devcentral / f5-oci-failover

Failover configuration for BIG-IP VE in Oracle Cloud Infrastructure

Welcome to the F5 BIG-IP VE Failover Configuration for OCI

Configuration tools provided in this GitHub repo are community-supported. However, F5 supports BIG-IP VE in OCI. You can find all documentation related to deploying BIG-IP VE in OCI at:

https://clouddocs.f5.com/cloud/public/v1/oracle_index.html

Please let us know if you find an issue or have a suggestion related to these failover configuration tools, by submitting an issue through this GitHub repository. Provide as much information as you can about what you found, how you found it, your environment, suggested enhancements, and other similar details.

Copyright

Copyright 2014-2022 F5 Inc.

License

Apache V2.0

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Contributor License Agreement

Individuals or business entities who contribute to this project must have completed and submitted the F5 Contributor License Agreement.

f5-oci-failover's Issues

OCI Regional Subnets

OCI now has regional subnets supporting the spanning of a single class C across availability domains. If you move the private IP it will also move the associated RESERVED PUBLIC IP. Can we use these scripts to perform that function? I have an HA pair setup across AD1 and AD2 it works fine. Just need to get the IP to move after failure. For Beeline/OCI Thanks.

Public IP address failover across AD's

Failover Issues

Hi Team,
I followed instructions provided in F5 article: https://clouddocs.f5.com/cloud/public/v1/oracle_index.html

Article calls for editing "Active" file whereas the download has tgactive. Is there a difference?
Tgactive IP address OCIID includes "/20160918/privateIps/" - do I need include it? I tried with and without but failover is not happening between active and standby.

Modify oci-curl to include proxy for API calls

add conditional and variable for proxy server destination IP and port and add -x host:port to script

support for 15.1.1

Does the script support 15.1.1.0.0.6?
Seems the secondary IP is not moved triggering the traffic-group switch but if I lunch manually from BIG-IP the oci-curl command as it is built in the tgactive file the secondary IP is moved correctly?
Maybe the traffic-group switch is not recognized ?
anyway this is included in my ltm log triggering the event:
Nov 20 13:41:25 pem02.oci.local notice logger[6086]: /config/failover/tgactive traffic-group-1 : Started.
Nov 20 13:41:25 pem02.oci.local notice logger[6111]: /config/failover/tgactive (): Finished.

tgactive update

Update active script to use tgactive and determine failover for individual traffic groups.

Update documentation.

Update documents for virtio instead of emmulated drivers

Failover torubleshooting

Dears,

I have followed the documentation for configuration part and it was working for me. However, last month noticed all of OCI based objects are not moving (Secondary IPs for internal and external).

Searched a lot on decentral and ticket is also raised with support but i couldn't get resolution. I haven't found any material for troubleshooting.

Do we have tail commands to check what's going on when failover is happening either its auth or privilge issue on OCI?

Version 14.1.0.3 oci-curl issue

Since upgrading to version 14.1.0.3 from version 13.1 when failing over oci-curl is throwing error:
oci-curl[22240]: curl: (6) Could not resolve host: iaas.us-phoenix-1.oraclecloud.com

DNS is working fine. Can run tgactive logged in as root and it runs fine. Can also run curl to iaas.us-phoenix-1.oraclecloud.com and it is able to connect. Ping works and resolves. Still trying to figure this one out.

Instance calling API

Update script to do instance calling of the API