jsevedge
commented
4 years ago @Charding2008 The error is a result of one of the prereqs not being fulfilled I believe. CFE needs to talk to the Azure metadata service, so the BIG-IP routing needs to be set up for that. We describe that in some detail here: https://clouddocs.f5.com/products/extensions/f5-cloud-failover/latest/userguide/azure.html#setting-up-access-to-azure-s-instance-metadata-service
The scoping address ranges is meant to filter down not only which route tables but also which specific routes in the route table should have the next hop address updated (if route failover is required). So the scoping address ranges should match the cidr blocks of any routes where the next hop address should be updated to follow the active BIG-IP. This could use some additional explanation in the documentation.
Charding2008
shyawnkarim
Having two issue following the Azure lab guide
Have installed f5-cloud-failure on.
Issues 1: Posting example declaration below fails { "class": "Cloud_Failover", "environment": "azure", "externalStorage": { "scopingTags": { "f5_cloud_failover_label": "mydeployment" } }, "failoverAddresses": { "scopingTags": { "f5_cloud_failover_label": "mydeployment" } }, "failoverRoutes": { "scopingTags": { "f5_cloud_failover_label": "mydeployment" }, "scopingAddressRanges": [ "192.168.1.0/24" ] } } error: {"message":"Cloud Provider initialization failed with error: connect ECONNREFUSED 169.254.169.254:80 Error: connect ECONNREFUSED 169.254.169.254:80\n at Object._errnoException (util.js:1022:11)\n at _exceptionWithHostPort (util.js:1044:20)\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14)"
question what is the default Address range meant to be? my bigip's are all in the 10.x range.
Issue 2. Setting up access to Azure’s Instance Metadata Service
Not sure I'm using the correct IP's as the defaults provide do not get saved ( tried with both tmsh and Postman). What is the 169.xxx address? think it needs more clarity here.