diff --git a/azure-bigip-version-matrix.md b/azure-bigip-version-matrix.md index 50892398b2..7e47b50321 100644 --- a/azure-bigip-version-matrix.md +++ b/azure-bigip-version-matrix.md @@ -8,6 +8,12 @@ The following table contains all of the tagged releases of the F5 ARM templates | Release Tag | Template Family | BIG-IP Versions | BIG-IQ Versions | PAYG License Bundles and Throughput | BYOL/BIG-IQ Image options | | --- | --- | --- | --- | --- | --- | +| [v7.0.0.1](https://github.com/F5Networks/f5-azure-arm-templates/releases/tag/v7.0.0.1) | Standalone | Latest, BIG-IP v14.1.0.3, BIG-IP v13.1.100000 | BIG-IQ v5.4, v6.1.0 | *Good/Better/Best*: 1Gbps, 200Mbps, 25Mbps
BIG-IP v13.1+:
Advanced WAF: 25Mbps, 200Mbps, 1Gbps
Per App VE LTM: 25Mbps, 200Mbps
Per App VE Advanced WAF: 25Mbps, 200Mbps | AllOneBootLocation, AllTwoBootLocations, LTMOneBootLocation, LTMTwoBootLocations | +| | Cluster (Failover-API) | Latest, BIG-IP v14.003000, BIG-IP v13.1.100000 | BIG-IQ v5.4, v6.0.1 | *Good/Better/Best*: 1Gbps, 200Mbps, 25Mbps
BIG-IP v13.1+:
Advanced WAF: 25Mbps, 200Mbps, 1Gbps | AllOneBootLocation, AllTwoBootLocations, LTMOneBootLocation, LTMTwoBootLocations | +| | Cluster (Failover-LB) | Latest, BIG-IP v14.003000, BIG-IP v13.1.100000 | BIG-IQ v5.4, v6.0.1 | *Good/Better/Best*: 1Gbps, 200Mbps, 25Mbps
BIG-IP v13.1+:
Advanced WAF: 25Mbps, 200Mbps, 1Gbps | AllOneBootLocation, AllTwoBootLocations, LTMOneBootLocation, LTMTwoBootLocations | +| | Auto Scale WAF | Latest, BIG-IP v14.003000, BIG-IP v13.1.100000 | BIG-IQ v5.4, v6.0.1 | *Best*: 1Gbps, 200Mbps, 25Mbps
BIG-IP v13.1+:
Advanced WAF: 25Mbps, 200Mbps, 1Gbps
Per App VE Advanced WAF: 25Mbps, 200Mbps | AllOneBootLocation, AllTwoBootLocations, LTMOneBootLocation, LTMTwoBootLocations | +| | Auto Scale LTM | Latest, BIG-IP v14.003000, BIG-IP v13.1.100000 | BIG-IQ v5.4, v6.0.1 | *Good/Better/Best*: 1Gbps, 200Mbps, 25Mbps
v13.1+: Per App VE LTM: 25Mbps, 200Mbps | AllOneBootLocation, AllTwoBootLocations, LTMOneBootLocation, LTMTwoBootLocations | +| | BIG-IQ | N/A | 6.0.1 | N/A | Best | | [v7.0.0.0](https://github.com/F5Networks/f5-azure-arm-templates/releases/tag/v7.0.0.0) | Standalone | Latest, BIG-IP v14.1.0.3, BIG-IP v13.1.100000 | BIG-IQ v5.4, v6.1.0 | *Good/Better/Best*: 1Gbps, 200Mbps, 25Mbps
BIG-IP v13.1+:
Advanced WAF: 25Mbps, 200Mbps, 1Gbps
Per App VE LTM: 25Mbps, 200Mbps
Per App VE Advanced WAF: 25Mbps, 200Mbps | AllOneBootLocation, AllTwoBootLocations, LTMOneBootLocation, LTMTwoBootLocations | | | Cluster (Failover-API) | Latest, BIG-IP v14.003000, BIG-IP v13.1.100000 | BIG-IQ v5.4, v6.0.1 | *Good/Better/Best*: 1Gbps, 200Mbps, 25Mbps
BIG-IP v13.1+:
Advanced WAF: 25Mbps, 200Mbps, 1Gbps | AllOneBootLocation, AllTwoBootLocations, LTMOneBootLocation, LTMTwoBootLocations | | | Cluster (Failover-LB) | Latest, BIG-IP v14.003000, BIG-IP v13.1.100000 | BIG-IQ v5.4, v6.0.1 | *Good/Better/Best*: 1Gbps, 200Mbps, 25Mbps
BIG-IP v13.1+:
Advanced WAF: 25Mbps, 200Mbps, 1Gbps | AllOneBootLocation, AllTwoBootLocations, LTMOneBootLocation, LTMTwoBootLocations | diff --git a/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/README.md b/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/README.md index b698ab724b..c5cbfc6f69 100644 --- a/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/README.md +++ b/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/README.md @@ -106,7 +106,7 @@ Use the appropriate button below to deploy: - **BIGIQ-PAYG**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s), as well as use PAYG instances. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbigiq-payg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbigiq-payg%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.json b/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.json index c08d1b7b75..99831248ed 100644 --- a/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.json +++ b/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -499,7 +499,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -723,7 +723,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-existing-stack-experimental-bigiq-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq-payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-existing-stack-experimental-bigiq-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq-payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.parameters.json b/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.parameters.json index a70bdbdd90..b94eea89a1 100644 --- a/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.parameters.json +++ b/experimental/autoscale/ltm/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/README.md b/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/README.md index 496665d6c7..d4bb27a7af 100644 --- a/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/README.md +++ b/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/README.md @@ -106,7 +106,7 @@ Use the appropriate button below to deploy: - **BIGIQ-PAYG**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s), as well as use PAYG instances. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fnew-stack%2Fbigiq-payg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fnew-stack%2Fbigiq-payg%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.json b/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.json index 110f7c8f46..e5076d25c6 100644 --- a/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.json +++ b/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -488,7 +488,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -714,7 +714,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-new-stack-experimental-bigiq-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq-payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-new-stack-experimental-bigiq-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq-payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.parameters.json b/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.parameters.json index 7cb9b67700..a231f05fbb 100644 --- a/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.parameters.json +++ b/experimental/autoscale/ltm/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/README.md b/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/README.md index fe64f0ccfb..3bdd577d52 100644 --- a/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/README.md +++ b/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/README.md @@ -108,7 +108,7 @@ Use the appropriate button below to deploy: - **BIGIQ-PAYG**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s), as well as use PAYG instances. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbigiq-payg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbigiq-payg%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.json b/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.json index b1040963ee..704dc11f33 100644 --- a/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.json +++ b/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -571,7 +571,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -798,7 +798,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-existing-stack-experimental-bigiq-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq-payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-existing-stack-experimental-bigiq-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq-payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.parameters.json b/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.parameters.json index 95840e8c6a..4259626396 100644 --- a/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.parameters.json +++ b/experimental/autoscale/waf/via-lb/1nic/existing-stack/bigiq-payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/README.md b/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/README.md index e9090d6393..86be9606d0 100644 --- a/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/README.md +++ b/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/README.md @@ -108,7 +108,7 @@ Use the appropriate button below to deploy: - **BIGIQ-PAYG**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s), as well as use PAYG instances. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fnew-stack%2Fbigiq-payg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fnew-stack%2Fbigiq-payg%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.json b/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.json index 48355fcc5f..9f260e76da 100644 --- a/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.json +++ b/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -560,7 +560,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -789,7 +789,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-new-stack-experimental-bigiq-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq-payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-new-stack-experimental-bigiq-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq-payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.parameters.json b/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.parameters.json index e0e209ffc3..dc99369ad1 100644 --- a/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.parameters.json +++ b/experimental/autoscale/waf/via-lb/1nic/new-stack/bigiq-payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/README.md b/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/README.md index 4def72cce0..c57815e895 100644 --- a/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/README.md +++ b/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/README.md @@ -103,7 +103,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Fbigiq%2FlicenseManagement%2Fcluster%2F2nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Fbigiq%2FlicenseManagement%2Fcluster%2F2nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/azuredeploy.json b/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/azuredeploy.json index f2139a16cf..290b718e59 100644 --- a/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/azuredeploy.json +++ b/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -847,7 +847,7 @@ "properties": { "autoUpgradeMinorVersion": "true", "protectedSettings": { - "commandToExecute": "[concat('mkdir -p /var/log/cloud/azure; mkdir -p /config/cloud; echo ', variables('initScript'), ' | /usr/bin/base64 -d > /config/cloud/init.sh; chmod +x /config/cloud/init.sh;', ' /config/cloud/init.sh --cloud azure --log-level silly --data-interface eth1 --license ', parameters('bigIqLicenseKey1'), ' --ntp ', parameters('ntpServer'), ' --timezone ', parameters('timeZone'), ' --big-iq-password-data-uri file:///mnt/cloudTmp/.bigiq_pass --big-iq-password ', variables('adminPassword'), ' --big-iq-master-key ', parameters('masterKey'), ' --fcl-tag ', variables('f5CloudLibsTag'), ' --fcl-cloud-tag ', variables('f5CloudLibsAzureTag'), ' --tag-value ', variables('resourceGroupId'), ' --private-ip ', variables('intSubnetPrivateAddress2'), ' --associate-intf ', concat(variables('intNicName'), '0'), ' --dissociate-intf ', concat(variables('intNicName'), '1'), ' --vlan ', variables('singleQuote'), 'n:internal,nic:1.1', variables('singleQuote'), ' --self-ip ', variables('singleQuote'), 'n:internal_self,a:', variables('intSubnetPrivateAddress'), ',v:internal,i:eth1', variables('singleQuote'), ' --discovery-address ', variables('intSubnetPrivateAddress'), ' --usage-analytics ', variables('singleQuote'), 'send:', parameters('allowUsageAnalytics'), ',r:', variables('location'), ',cI:', variables('subscriptionID'), ',dI:', variables('deploymentId'), ',cN:azure,lT:byol,bIV:',parameters('bigIqVersion'),',tN:f5-existing-stack-byol-2nic-bigiq,tV:','7.0.0.0', variables('singleQuote'), ' &>> /var/log/cloud/azure/install.log &')]" + "commandToExecute": "[concat('mkdir -p /var/log/cloud/azure; mkdir -p /config/cloud; echo ', variables('initScript'), ' | /usr/bin/base64 -d > /config/cloud/init.sh; chmod +x /config/cloud/init.sh;', ' /config/cloud/init.sh --cloud azure --log-level silly --data-interface eth1 --license ', parameters('bigIqLicenseKey1'), ' --ntp ', parameters('ntpServer'), ' --timezone ', parameters('timeZone'), ' --big-iq-password-data-uri file:///mnt/cloudTmp/.bigiq_pass --big-iq-password ', variables('adminPassword'), ' --big-iq-master-key ', parameters('masterKey'), ' --fcl-tag ', variables('f5CloudLibsTag'), ' --fcl-cloud-tag ', variables('f5CloudLibsAzureTag'), ' --tag-value ', variables('resourceGroupId'), ' --private-ip ', variables('intSubnetPrivateAddress2'), ' --associate-intf ', concat(variables('intNicName'), '0'), ' --dissociate-intf ', concat(variables('intNicName'), '1'), ' --vlan ', variables('singleQuote'), 'n:internal,nic:1.1', variables('singleQuote'), ' --self-ip ', variables('singleQuote'), 'n:internal_self,a:', variables('intSubnetPrivateAddress'), ',v:internal,i:eth1', variables('singleQuote'), ' --discovery-address ', variables('intSubnetPrivateAddress'), ' --usage-analytics ', variables('singleQuote'), 'send:', parameters('allowUsageAnalytics'), ',r:', variables('location'), ',cI:', variables('subscriptionID'), ',dI:', variables('deploymentId'), ',cN:azure,lT:byol,bIV:',parameters('bigIqVersion'),',tN:f5-existing-stack-byol-2nic-bigiq,tV:','7.0.0.1', variables('singleQuote'), ' &>> /var/log/cloud/azure/install.log &')]" }, "publisher": "Microsoft.Azure.Extensions", "settings": { @@ -874,7 +874,7 @@ "properties": { "autoUpgradeMinorVersion": "true", "protectedSettings": { - "commandToExecute": "[concat('mkdir -p /var/log/cloud/azure; mkdir -p /config/cloud; echo ', variables('initScript'), ' | /usr/bin/base64 -d > /config/cloud/init.sh; chmod +x /config/cloud/init.sh;', ' /config/cloud/init.sh --cloud azure --log-level silly --data-interface eth1 --license ', parameters('bigIqLicenseKey2'), ' --ntp ', parameters('ntpServer'), ' --timezone ', parameters('timeZone'), ' --create-license-pool ', parameters('licensePoolKeys'), ' --create-reg-key-pool ', parameters('regPoolKeys'), ' --big-iq-password-data-uri file:///mnt/cloudTmp/.bigiq_pass --big-iq-password ', variables('adminPassword'), ' --big-iq-master-key ', parameters('masterKey'), ' --master --big-iq-failover-peer-ip ', variables('intSubnetPrivateAddress'), ' --fcl-tag ', variables('f5CloudLibsTag'), ' --fcl-cloud-tag ', variables('f5CloudLibsAzureTag'), ' --tag-value ', variables('resourceGroupId'), ' --private-ip ', variables('intSubnetPrivateAddress3'), ' --associate-intf ', concat(variables('intNicName'), '1'), ' --dissociate-intf ', concat(variables('intNicName'), '0'), ' --vlan ', variables('singleQuote'), 'n:internal,nic:1.1', variables('singleQuote'), ' --self-ip ', variables('singleQuote'), 'n:internal_self,a:', variables('intSubnetPrivateAddress1'), ',v:internal,i:eth1', variables('singleQuote'), ' --discovery-address ', variables('intSubnetPrivateAddress1'), ' --usage-analytics ', variables('singleQuote'), 'send:', parameters('allowUsageAnalytics'), ',r:', variables('location'), ',cI:', variables('subscriptionID'), ',dI:', variables('deploymentId'), ',cN:azure,lT:byol,bIV:',parameters('bigIqVersion'),',tN:f5-existing-stack-byol-2nic-bigiq,tV:','7.0.0.0', variables('singleQuote'), ' &>> /var/log/cloud/azure/install.log &')]" + "commandToExecute": "[concat('mkdir -p /var/log/cloud/azure; mkdir -p /config/cloud; echo ', variables('initScript'), ' | /usr/bin/base64 -d > /config/cloud/init.sh; chmod +x /config/cloud/init.sh;', ' /config/cloud/init.sh --cloud azure --log-level silly --data-interface eth1 --license ', parameters('bigIqLicenseKey2'), ' --ntp ', parameters('ntpServer'), ' --timezone ', parameters('timeZone'), ' --create-license-pool ', parameters('licensePoolKeys'), ' --create-reg-key-pool ', parameters('regPoolKeys'), ' --big-iq-password-data-uri file:///mnt/cloudTmp/.bigiq_pass --big-iq-password ', variables('adminPassword'), ' --big-iq-master-key ', parameters('masterKey'), ' --master --big-iq-failover-peer-ip ', variables('intSubnetPrivateAddress'), ' --fcl-tag ', variables('f5CloudLibsTag'), ' --fcl-cloud-tag ', variables('f5CloudLibsAzureTag'), ' --tag-value ', variables('resourceGroupId'), ' --private-ip ', variables('intSubnetPrivateAddress3'), ' --associate-intf ', concat(variables('intNicName'), '1'), ' --dissociate-intf ', concat(variables('intNicName'), '0'), ' --vlan ', variables('singleQuote'), 'n:internal,nic:1.1', variables('singleQuote'), ' --self-ip ', variables('singleQuote'), 'n:internal_self,a:', variables('intSubnetPrivateAddress1'), ',v:internal,i:eth1', variables('singleQuote'), ' --discovery-address ', variables('intSubnetPrivateAddress1'), ' --usage-analytics ', variables('singleQuote'), 'send:', parameters('allowUsageAnalytics'), ',r:', variables('location'), ',cI:', variables('subscriptionID'), ',dI:', variables('deploymentId'), ',cN:azure,lT:byol,bIV:',parameters('bigIqVersion'),',tN:f5-existing-stack-byol-2nic-bigiq,tV:','7.0.0.1', variables('singleQuote'), ' &>> /var/log/cloud/azure/install.log &')]" }, "publisher": "Microsoft.Azure.Extensions", "settings": { diff --git a/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/azuredeploy.parameters.json b/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/azuredeploy.parameters.json index 8bd66dc4f6..dc5669c752 100644 --- a/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/azuredeploy.parameters.json +++ b/experimental/bigiq/licenseManagement/cluster/2nic/existing-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/README.md b/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/README.md index d7640da3fa..b709dbf067 100644 --- a/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/README.md +++ b/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/README.md @@ -103,7 +103,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Fbigiq%2FlicenseManagement%2Fcluster%2F2nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Fbigiq%2FlicenseManagement%2Fcluster%2F2nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/azuredeploy.json b/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/azuredeploy.json index 7d9822006e..ec133f1ac8 100644 --- a/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/azuredeploy.json +++ b/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -826,7 +826,7 @@ "properties": { "autoUpgradeMinorVersion": "true", "protectedSettings": { - "commandToExecute": "[concat('mkdir -p /var/log/cloud/azure; mkdir -p /config/cloud; echo ', variables('initScript'), ' | /usr/bin/base64 -d > /config/cloud/init.sh; chmod +x /config/cloud/init.sh;', ' /config/cloud/init.sh --cloud azure --log-level silly --data-interface eth1 --license ', parameters('bigIqLicenseKey1'), ' --ntp ', parameters('ntpServer'), ' --timezone ', parameters('timeZone'), ' --big-iq-password-data-uri file:///mnt/cloudTmp/.bigiq_pass --big-iq-password ', variables('adminPassword'), ' --big-iq-master-key ', parameters('masterKey'), ' --fcl-tag ', variables('f5CloudLibsTag'), ' --fcl-cloud-tag ', variables('f5CloudLibsAzureTag'), ' --tag-value ', variables('resourceGroupId'), ' --private-ip ', variables('intSubnetPrivateAddress2'), ' --associate-intf ', concat(variables('intNicName'), '0'), ' --dissociate-intf ', concat(variables('intNicName'), '1'), ' --vlan ', variables('singleQuote'), 'n:internal,nic:1.1', variables('singleQuote'), ' --self-ip ', variables('singleQuote'), 'n:internal_self,a:', variables('intSubnetPrivateAddress'), ',v:internal,i:eth1', variables('singleQuote'), ' --discovery-address ', variables('intSubnetPrivateAddress'), ' --usage-analytics ', variables('singleQuote'), 'send:', parameters('allowUsageAnalytics'), ',r:', variables('location'), ',cI:', variables('subscriptionID'), ',dI:', variables('deploymentId'), ',cN:azure,lT:byol,bIV:',parameters('bigIqVersion'),',tN:f5-existing-stack-byol-2nic-bigiq,tV:','7.0.0.0', variables('singleQuote'), ' &>> /var/log/cloud/azure/install.log &')]" + "commandToExecute": "[concat('mkdir -p /var/log/cloud/azure; mkdir -p /config/cloud; echo ', variables('initScript'), ' | /usr/bin/base64 -d > /config/cloud/init.sh; chmod +x /config/cloud/init.sh;', ' /config/cloud/init.sh --cloud azure --log-level silly --data-interface eth1 --license ', parameters('bigIqLicenseKey1'), ' --ntp ', parameters('ntpServer'), ' --timezone ', parameters('timeZone'), ' --big-iq-password-data-uri file:///mnt/cloudTmp/.bigiq_pass --big-iq-password ', variables('adminPassword'), ' --big-iq-master-key ', parameters('masterKey'), ' --fcl-tag ', variables('f5CloudLibsTag'), ' --fcl-cloud-tag ', variables('f5CloudLibsAzureTag'), ' --tag-value ', variables('resourceGroupId'), ' --private-ip ', variables('intSubnetPrivateAddress2'), ' --associate-intf ', concat(variables('intNicName'), '0'), ' --dissociate-intf ', concat(variables('intNicName'), '1'), ' --vlan ', variables('singleQuote'), 'n:internal,nic:1.1', variables('singleQuote'), ' --self-ip ', variables('singleQuote'), 'n:internal_self,a:', variables('intSubnetPrivateAddress'), ',v:internal,i:eth1', variables('singleQuote'), ' --discovery-address ', variables('intSubnetPrivateAddress'), ' --usage-analytics ', variables('singleQuote'), 'send:', parameters('allowUsageAnalytics'), ',r:', variables('location'), ',cI:', variables('subscriptionID'), ',dI:', variables('deploymentId'), ',cN:azure,lT:byol,bIV:',parameters('bigIqVersion'),',tN:f5-existing-stack-byol-2nic-bigiq,tV:','7.0.0.1', variables('singleQuote'), ' &>> /var/log/cloud/azure/install.log &')]" }, "publisher": "Microsoft.Azure.Extensions", "settings": { @@ -853,7 +853,7 @@ "properties": { "autoUpgradeMinorVersion": "true", "protectedSettings": { - "commandToExecute": "[concat('mkdir -p /var/log/cloud/azure; mkdir -p /config/cloud; echo ', variables('initScript'), ' | /usr/bin/base64 -d > /config/cloud/init.sh; chmod +x /config/cloud/init.sh;', ' /config/cloud/init.sh --cloud azure --log-level silly --data-interface eth1 --license ', parameters('bigIqLicenseKey2'), ' --ntp ', parameters('ntpServer'), ' --timezone ', parameters('timeZone'), ' --create-license-pool ', parameters('licensePoolKeys'), ' --create-reg-key-pool ', parameters('regPoolKeys'), ' --big-iq-password-data-uri file:///mnt/cloudTmp/.bigiq_pass --big-iq-password ', variables('adminPassword'), ' --big-iq-master-key ', parameters('masterKey'), ' --master --big-iq-failover-peer-ip ', variables('intSubnetPrivateAddress'), ' --fcl-tag ', variables('f5CloudLibsTag'), ' --fcl-cloud-tag ', variables('f5CloudLibsAzureTag'), ' --tag-value ', variables('resourceGroupId'), ' --private-ip ', variables('intSubnetPrivateAddress3'), ' --associate-intf ', concat(variables('intNicName'), '1'), ' --dissociate-intf ', concat(variables('intNicName'), '0'), ' --vlan ', variables('singleQuote'), 'n:internal,nic:1.1', variables('singleQuote'), ' --self-ip ', variables('singleQuote'), 'n:internal_self,a:', variables('intSubnetPrivateAddress1'), ',v:internal,i:eth1', variables('singleQuote'), ' --discovery-address ', variables('intSubnetPrivateAddress1'), ' --usage-analytics ', variables('singleQuote'), 'send:', parameters('allowUsageAnalytics'), ',r:', variables('location'), ',cI:', variables('subscriptionID'), ',dI:', variables('deploymentId'), ',cN:azure,lT:byol,bIV:',parameters('bigIqVersion'),',tN:f5-existing-stack-byol-2nic-bigiq,tV:','7.0.0.0', variables('singleQuote'), ' &>> /var/log/cloud/azure/install.log &')]" + "commandToExecute": "[concat('mkdir -p /var/log/cloud/azure; mkdir -p /config/cloud; echo ', variables('initScript'), ' | /usr/bin/base64 -d > /config/cloud/init.sh; chmod +x /config/cloud/init.sh;', ' /config/cloud/init.sh --cloud azure --log-level silly --data-interface eth1 --license ', parameters('bigIqLicenseKey2'), ' --ntp ', parameters('ntpServer'), ' --timezone ', parameters('timeZone'), ' --create-license-pool ', parameters('licensePoolKeys'), ' --create-reg-key-pool ', parameters('regPoolKeys'), ' --big-iq-password-data-uri file:///mnt/cloudTmp/.bigiq_pass --big-iq-password ', variables('adminPassword'), ' --big-iq-master-key ', parameters('masterKey'), ' --master --big-iq-failover-peer-ip ', variables('intSubnetPrivateAddress'), ' --fcl-tag ', variables('f5CloudLibsTag'), ' --fcl-cloud-tag ', variables('f5CloudLibsAzureTag'), ' --tag-value ', variables('resourceGroupId'), ' --private-ip ', variables('intSubnetPrivateAddress3'), ' --associate-intf ', concat(variables('intNicName'), '1'), ' --dissociate-intf ', concat(variables('intNicName'), '0'), ' --vlan ', variables('singleQuote'), 'n:internal,nic:1.1', variables('singleQuote'), ' --self-ip ', variables('singleQuote'), 'n:internal_self,a:', variables('intSubnetPrivateAddress1'), ',v:internal,i:eth1', variables('singleQuote'), ' --discovery-address ', variables('intSubnetPrivateAddress1'), ' --usage-analytics ', variables('singleQuote'), 'send:', parameters('allowUsageAnalytics'), ',r:', variables('location'), ',cI:', variables('subscriptionID'), ',dI:', variables('deploymentId'), ',cN:azure,lT:byol,bIV:',parameters('bigIqVersion'),',tN:f5-existing-stack-byol-2nic-bigiq,tV:','7.0.0.1', variables('singleQuote'), ' &>> /var/log/cloud/azure/install.log &')]" }, "publisher": "Microsoft.Azure.Extensions", "settings": { diff --git a/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/azuredeploy.parameters.json b/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/azuredeploy.parameters.json index 7d5320aeb4..d180a53ffd 100644 --- a/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/azuredeploy.parameters.json +++ b/experimental/bigiq/licenseManagement/cluster/2nic/new-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/README.md b/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/README.md index 77495a9a8f..805b8cd452 100644 --- a/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/README.md +++ b/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/README.md @@ -97,7 +97,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Fbigiq%2FlicenseManagement%2Fstandalone%2F2nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Fbigiq%2FlicenseManagement%2Fstandalone%2F2nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/azuredeploy.json b/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/azuredeploy.json index df05ec585f..57af7f47e7 100644 --- a/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/azuredeploy.json +++ b/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", diff --git a/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/azuredeploy.parameters.json b/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/azuredeploy.parameters.json index 4b1b26036c..c11e1bf7c3 100644 --- a/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/azuredeploy.parameters.json +++ b/experimental/bigiq/licenseManagement/standalone/2nic/existing-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/README.md b/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/README.md index ef94a69f60..22fd33a1d2 100644 --- a/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/README.md +++ b/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/README.md @@ -119,7 +119,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Flearning-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Flearning-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/azuredeploy.json b/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/azuredeploy.json index 43241c79a7..6e8d89111b 100644 --- a/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/azuredeploy.json +++ b/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -485,7 +485,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -657,7 +657,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-learning-stack-experimental-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-learning-stack-experimental-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -860,7 +860,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations'), 0), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations'), 1)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations'), 0), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/azuredeploy.parameters.json b/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/azuredeploy.parameters.json index 7c734feb64..341d0fd0cb 100644 --- a/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/azuredeploy.parameters.json +++ b/experimental/failover/same-net/via-api/n-nic/learning-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/README.md b/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/README.md index 462b4c6204..4f4e6dc668 100644 --- a/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/README.md +++ b/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/README.md @@ -118,7 +118,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Flearning-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Flearning-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/azuredeploy.json b/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/azuredeploy.json index 4e93194c7b..0a30e63e4e 100644 --- a/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/azuredeploy.json +++ b/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -461,7 +461,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -633,7 +633,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-learning-stack-experimental-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-learning-stack-experimental-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -836,7 +836,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations'), 0), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations'), 1)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations'), 0), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/azuredeploy.parameters.json b/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/azuredeploy.parameters.json index 4ab008e232..44e3d271a6 100644 --- a/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/azuredeploy.parameters.json +++ b/experimental/failover/same-net/via-api/n-nic/learning-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/README.md b/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/README.md index 22694b28d7..a8f42cd76e 100644 --- a/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/README.md +++ b/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/README.md @@ -116,7 +116,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Flearning-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Flearning-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/azuredeploy.json b/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/azuredeploy.json index 08f099f4e7..6a10907577 100644 --- a/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/azuredeploy.json +++ b/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -457,7 +457,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -666,7 +666,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-learning-stack-experimental-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-learning-stack-experimental-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -869,7 +869,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations'), 0), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations'), 1)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations'), 0), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/azuredeploy.parameters.json b/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/azuredeploy.parameters.json index cd5948e7d3..4ee2722543 100644 --- a/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/azuredeploy.parameters.json +++ b/experimental/failover/same-net/via-api/n-nic/learning-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/failover/same-net/via-lb/1nic/production-stack/bigiq/README.md b/experimental/failover/same-net/via-lb/1nic/production-stack/bigiq/README.md index e210d6441f..34eee9992c 100644 --- a/experimental/failover/same-net/via-lb/1nic/production-stack/bigiq/README.md +++ b/experimental/failover/same-net/via-lb/1nic/production-stack/bigiq/README.md @@ -100,7 +100,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fproduction-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fproduction-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/failover/same-net/via-lb/1nic/production-stack/bigiq/azuredeploy.json b/experimental/failover/same-net/via-lb/1nic/production-stack/bigiq/azuredeploy.json index 67344acb55..49ac8aca85 100644 --- a/experimental/failover/same-net/via-lb/1nic/production-stack/bigiq/azuredeploy.json +++ b/experimental/failover/same-net/via-lb/1nic/production-stack/bigiq/azuredeploy.json @@ -378,7 +378,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.0", "f5CloudLibsAzureTag": "v2.9.0", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", diff --git a/experimental/standalone/3nic/learning-stack/bigiq/README.md b/experimental/standalone/3nic/learning-stack/bigiq/README.md index 89a3900574..d8192935d0 100644 --- a/experimental/standalone/3nic/learning-stack/bigiq/README.md +++ b/experimental/standalone/3nic/learning-stack/bigiq/README.md @@ -100,7 +100,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Fstandalone%2F3nic%2Flearning-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Fstandalone%2F3nic%2Flearning-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/standalone/3nic/learning-stack/bigiq/azuredeploy.json b/experimental/standalone/3nic/learning-stack/bigiq/azuredeploy.json index 67fb052e80..70d838e624 100644 --- a/experimental/standalone/3nic/learning-stack/bigiq/azuredeploy.json +++ b/experimental/standalone/3nic/learning-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -358,7 +358,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -469,7 +469,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-learning-stack-experimental-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-learning-stack-experimental-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -628,7 +628,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/experimental/standalone/3nic/learning-stack/bigiq/azuredeploy.parameters.json b/experimental/standalone/3nic/learning-stack/bigiq/azuredeploy.parameters.json index 405c4dd755..201b7cf0db 100644 --- a/experimental/standalone/3nic/learning-stack/bigiq/azuredeploy.parameters.json +++ b/experimental/standalone/3nic/learning-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/standalone/3nic/learning-stack/byol/README.md b/experimental/standalone/3nic/learning-stack/byol/README.md index 9361bbdeb2..077cce3971 100644 --- a/experimental/standalone/3nic/learning-stack/byol/README.md +++ b/experimental/standalone/3nic/learning-stack/byol/README.md @@ -99,7 +99,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Fstandalone%2F3nic%2Flearning-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Fstandalone%2F3nic%2Flearning-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/standalone/3nic/learning-stack/byol/azuredeploy.json b/experimental/standalone/3nic/learning-stack/byol/azuredeploy.json index 55c1967a78..6767e09f74 100644 --- a/experimental/standalone/3nic/learning-stack/byol/azuredeploy.json +++ b/experimental/standalone/3nic/learning-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -327,7 +327,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -438,7 +438,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-learning-stack-experimental-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-learning-stack-experimental-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -597,7 +597,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/experimental/standalone/3nic/learning-stack/byol/azuredeploy.parameters.json b/experimental/standalone/3nic/learning-stack/byol/azuredeploy.parameters.json index 3bcd26e076..e016fe536c 100644 --- a/experimental/standalone/3nic/learning-stack/byol/azuredeploy.parameters.json +++ b/experimental/standalone/3nic/learning-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/experimental/standalone/3nic/learning-stack/payg/README.md b/experimental/standalone/3nic/learning-stack/payg/README.md index 75b09c54fa..47c5e645ef 100644 --- a/experimental/standalone/3nic/learning-stack/payg/README.md +++ b/experimental/standalone/3nic/learning-stack/payg/README.md @@ -97,7 +97,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fexperimental%2Fstandalone%2F3nic%2Flearning-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fexperimental%2Fstandalone%2F3nic%2Flearning-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters diff --git a/experimental/standalone/3nic/learning-stack/payg/azuredeploy.json b/experimental/standalone/3nic/learning-stack/payg/azuredeploy.json index 8e958b6d83..7363c9c310 100644 --- a/experimental/standalone/3nic/learning-stack/payg/azuredeploy.json +++ b/experimental/standalone/3nic/learning-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -332,7 +332,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -480,7 +480,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-learning-stack-experimental-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-learning-stack-experimental-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -639,7 +639,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/experimental/standalone/3nic/learning-stack/payg/azuredeploy.parameters.json b/experimental/standalone/3nic/learning-stack/payg/azuredeploy.parameters.json index cd315721fd..ce9352e87b 100644 --- a/experimental/standalone/3nic/learning-stack/payg/azuredeploy.parameters.json +++ b/experimental/standalone/3nic/learning-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/ltm/via-dns/1nic/README.md b/supported/autoscale/ltm/via-dns/1nic/README.md index 8c779e20e2..6018ca5fe3 100644 --- a/supported/autoscale/ltm/via-dns/1nic/README.md +++ b/supported/autoscale/ltm/via-dns/1nic/README.md @@ -2,8 +2,8 @@ For each of the standalone templates, you must choose the type of stack into which you want to deploy the BIG-IP VE. See the individual README files for exact requirements. Note that not all options are available for all templates. - - **Existing Stack**
These templates deploy into an existing cloud network. This means that all of the cloud networking infrastructure must be available prior to launching the template. + - **Existing Stack**
These templates deploy BIG-IP instances into an existing cloud network. This means that the Azure virtual network and subnets must be available prior to launching the template. If you choose "No" for the provisionPublicIP parameter, existing stack templates do not create or attach public IP addresses to the BIG-IP network interface(s). As BIG-IP VEs behind an Azure load balancer need external connectivity to download files for onboarding and access Cloud API services (autoscale only), these deployments will create a public front end IP configuration and load balancing rules on the external ALB. If Internet access is to be provided via another public NAT service, firewall, etc., F5 recommends removing this public configuration after deployment completes. - - **Production Stack**
Production stack templates also require the cloud networking infrastructure to be in place, however these templates do not create or attach a public IP address/NAT (there is never a public IP address assigned to the Management IP address). As BIG-IP VEs need access to the internet to access Cloud API services and download files for onboarding, these deployments assume Internet access is provided via another Public NAT service, Firewall, etc. In most cases, there is no public IP assigned to the IP addresses on the external interfaces (Virtual Servers, Self IP addresses, etc). + - **New Stack**
These templates deploy BIG-IP instances into a new cloud network. The required Azure virtual network and subnets will be created along with the deployment, and public IP addresses are created on all external Azure network interfaces and load balancers by default. - - **New Stack**
This solution deploys into a new cloud network, this means that all of the cloud networking infrastructure required will be created along with the deployment. \ No newline at end of file + - **Production Stack**
These templates have been deprecated. Production stack templates are still available for deployment in f5-azure-arm-templates release v6.1.0 or earlier. \ No newline at end of file diff --git a/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/README.md b/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/README.md index ceddb9f55b..7c3b8433fa 100644 --- a/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/README.md +++ b/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/README.md @@ -38,7 +38,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -61,6 +61,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -114,7 +115,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fltm%2Fvia-dns%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fltm%2Fvia-dns%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -184,48 +185,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --dnsMemberIpType private --dnsMemberPort 80 --dnsProviderHost --dnsProviderPort 443 --dnsProviderUser --dnsProviderPassword --dnsProviderPool autoscale_pool --dnsProviderDataCenter azure_datacenter --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a UCS archive in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally - -10. Install new ISO and reboot into upgraded volume - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example diff --git a/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/azuredeploy.json b/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/azuredeploy.json index cb3483df56..7a423d5c02 100644 --- a/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -511,7 +511,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -634,7 +634,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_dns-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_dns-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/azuredeploy.parameters.json index 230d838f69..9ce0adee64 100644 --- a/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/autoscale/ltm/via-dns/1nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/README.md b/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/README.md index b175d8e57a..cb79287b1d 100644 --- a/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/README.md +++ b/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/README.md @@ -37,7 +37,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -58,6 +58,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -111,7 +112,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fltm%2Fvia-dns%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fltm%2Fvia-dns%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -175,47 +176,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --dnsMemberIpType private --dnsMemberPort 80 --dnsProviderHost --dnsProviderPort 443 --dnsProviderUser --dnsProviderPassword --dnsProviderPool autoscale_pool --dnsProviderDataCenter azure_datacenter --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a UCS archive in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally - -10. Install new ISO and reboot into upgraded volume - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE appliance is through an Azure Load Balancer. The Azure Load Balancer processes both management and data plane traffic into the BIG-IP VEs, which then distribute the traffic to web/application servers according to normal F5 patterns. diff --git a/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/azuredeploy.json b/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/azuredeploy.json index 266fe06538..8ae31e49fa 100644 --- a/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/azuredeploy.json +++ b/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -480,7 +480,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -640,7 +640,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_dns-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_dns-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/azuredeploy.parameters.json b/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/azuredeploy.parameters.json index ff5c9fa44f..f1ea26cb18 100644 --- a/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/autoscale/ltm/via-dns/1nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/README.md b/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/README.md index 789d242a01..886311b5e8 100644 --- a/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/README.md +++ b/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/README.md @@ -38,7 +38,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -61,6 +61,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -114,7 +115,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fltm%2Fvia-dns%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fltm%2Fvia-dns%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -182,47 +183,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --dnsMemberIpType private --dnsMemberPort 80 --dnsProviderHost --dnsProviderPort 443 --dnsProviderUser --dnsProviderPassword --dnsProviderPool autoscale_pool --dnsProviderDataCenter azure_datacenter --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a UCS archive in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally - -10. Install new ISO and reboot into upgraded volume - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE appliance is through an Azure Load Balancer. The Azure Load Balancer processes both management and data plane traffic into the BIG-IP VEs, which then distribute the traffic to web/application servers according to normal F5 patterns. diff --git a/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/azuredeploy.json b/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/azuredeploy.json index 2b68bcdd3c..944149180e 100644 --- a/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/azuredeploy.json +++ b/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -500,7 +500,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -625,7 +625,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_dns-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_dns-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/azuredeploy.parameters.json index 2e1ea03d03..8863c9afcd 100644 --- a/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/autoscale/ltm/via-dns/1nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/README.md b/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/README.md index 68e1f82342..0b7e51d6ba 100644 --- a/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/README.md +++ b/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/README.md @@ -37,7 +37,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -58,6 +58,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -111,7 +112,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fltm%2Fvia-dns%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fltm%2Fvia-dns%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -173,47 +174,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --dnsMemberIpType private --dnsMemberPort 80 --dnsProviderHost --dnsProviderPort 443 --dnsProviderUser --dnsProviderPassword --dnsProviderPool autoscale_pool --dnsProviderDataCenter azure_datacenter --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/azuredeploy.json b/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/azuredeploy.json index 9c0e5c73a8..d94d50f2a0 100644 --- a/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/azuredeploy.json +++ b/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -469,7 +469,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -631,7 +631,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_dns-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_dns-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/azuredeploy.parameters.json b/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/azuredeploy.parameters.json index d4fca1908f..3a301512ed 100644 --- a/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/autoscale/ltm/via-dns/1nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/ltm/via-lb/1nic/README.md b/supported/autoscale/ltm/via-lb/1nic/README.md index 8c779e20e2..6018ca5fe3 100644 --- a/supported/autoscale/ltm/via-lb/1nic/README.md +++ b/supported/autoscale/ltm/via-lb/1nic/README.md @@ -2,8 +2,8 @@ For each of the standalone templates, you must choose the type of stack into which you want to deploy the BIG-IP VE. See the individual README files for exact requirements. Note that not all options are available for all templates. - - **Existing Stack**
These templates deploy into an existing cloud network. This means that all of the cloud networking infrastructure must be available prior to launching the template. + - **Existing Stack**
These templates deploy BIG-IP instances into an existing cloud network. This means that the Azure virtual network and subnets must be available prior to launching the template. If you choose "No" for the provisionPublicIP parameter, existing stack templates do not create or attach public IP addresses to the BIG-IP network interface(s). As BIG-IP VEs behind an Azure load balancer need external connectivity to download files for onboarding and access Cloud API services (autoscale only), these deployments will create a public front end IP configuration and load balancing rules on the external ALB. If Internet access is to be provided via another public NAT service, firewall, etc., F5 recommends removing this public configuration after deployment completes. - - **Production Stack**
Production stack templates also require the cloud networking infrastructure to be in place, however these templates do not create or attach a public IP address/NAT (there is never a public IP address assigned to the Management IP address). As BIG-IP VEs need access to the internet to access Cloud API services and download files for onboarding, these deployments assume Internet access is provided via another Public NAT service, Firewall, etc. In most cases, there is no public IP assigned to the IP addresses on the external interfaces (Virtual Servers, Self IP addresses, etc). + - **New Stack**
These templates deploy BIG-IP instances into a new cloud network. The required Azure virtual network and subnets will be created along with the deployment, and public IP addresses are created on all external Azure network interfaces and load balancers by default. - - **New Stack**
This solution deploys into a new cloud network, this means that all of the cloud networking infrastructure required will be created along with the deployment. \ No newline at end of file + - **Production Stack**
These templates have been deprecated. Production stack templates are still available for deployment in f5-azure-arm-templates release v6.1.0 or earlier. \ No newline at end of file diff --git a/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/README.md b/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/README.md index 6d8ba13a8f..fb2a4e7130 100644 --- a/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/README.md +++ b/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/README.md @@ -35,7 +35,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -58,6 +58,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -111,7 +112,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -174,48 +175,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --provisionPublicIP No --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example diff --git a/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/azuredeploy.json b/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/azuredeploy.json index b730a0ccd9..b54ca3cf03 100644 --- a/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -465,7 +465,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -588,7 +588,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json index 0be723c225..4774523f96 100644 --- a/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/autoscale/ltm/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/README.md b/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/README.md index 52c37961a5..22869f8bd4 100644 --- a/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/README.md +++ b/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/README.md @@ -34,7 +34,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -55,6 +55,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -108,7 +109,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -165,48 +166,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --provisionPublicIP No --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example diff --git a/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/azuredeploy.json b/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/azuredeploy.json index bf0a272b26..07aef1b82c 100644 --- a/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/azuredeploy.json +++ b/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -434,7 +434,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -594,7 +594,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json b/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json index 6a809bdb70..c429124f0e 100644 --- a/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/autoscale/ltm/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/README.md b/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/README.md index 7115b9b76e..cdf8c9aa31 100644 --- a/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/README.md +++ b/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/README.md @@ -35,7 +35,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -58,6 +58,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -111,7 +112,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -172,48 +173,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --provisionPublicIP No --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE appliance is through an Azure Load Balancer. The Azure Load Balancer processes both management and data plane traffic into the BIG-IP VEs, which then distribute the traffic to web/application servers according to normal F5 patterns. diff --git a/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/azuredeploy.json b/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/azuredeploy.json index 8563064bef..fb66198cdd 100644 --- a/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/azuredeploy.json +++ b/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -454,7 +454,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -579,7 +579,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json index c50acc9d45..c741e5a4d0 100644 --- a/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/autoscale/ltm/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/README.md b/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/README.md index e654561576..b521cfc2f0 100644 --- a/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/README.md +++ b/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/README.md @@ -34,7 +34,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -55,6 +55,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -108,7 +109,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fltm%2Fvia-lb%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -163,49 +164,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --provisionPublicIP No --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE appliance is through an Azure Load Balancer. The Azure Load Balancer processes both management and data plane traffic into the BIG-IP VEs, which then distribute the traffic to web/application servers according to normal F5 patterns. diff --git a/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/azuredeploy.json b/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/azuredeploy.json index 19e6461f80..84f8046eaf 100644 --- a/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/azuredeploy.json +++ b/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -423,7 +423,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -585,7 +585,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_ltm_via-lb-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json b/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json index e932825721..bafd39253f 100644 --- a/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/autoscale/ltm/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/waf/via-dns/1nic/README.md b/supported/autoscale/waf/via-dns/1nic/README.md index eeeafe2b8b..6018ca5fe3 100644 --- a/supported/autoscale/waf/via-dns/1nic/README.md +++ b/supported/autoscale/waf/via-dns/1nic/README.md @@ -2,8 +2,8 @@ For each of the standalone templates, you must choose the type of stack into which you want to deploy the BIG-IP VE. See the individual README files for exact requirements. Note that not all options are available for all templates. - - **Existing Stack**
These templates deploy into an existing cloud network. This means that all of the cloud networking infrastructure must be available prior to launching the template. + - **Existing Stack**
These templates deploy BIG-IP instances into an existing cloud network. This means that the Azure virtual network and subnets must be available prior to launching the template. If you choose "No" for the provisionPublicIP parameter, existing stack templates do not create or attach public IP addresses to the BIG-IP network interface(s). As BIG-IP VEs behind an Azure load balancer need external connectivity to download files for onboarding and access Cloud API services (autoscale only), these deployments will create a public front end IP configuration and load balancing rules on the external ALB. If Internet access is to be provided via another public NAT service, firewall, etc., F5 recommends removing this public configuration after deployment completes. - - **Production Stack**
Production stack templates also require the cloud networking infrastructure to be in place, however these templates do not create or attach a public IP address/NAT (there is never a public IP address assigned to the Management IP address). As BIG-IP VEs need access to the internet to access Cloud API services and download files for onboarding, these deployments assume Internet access is provided via another Public NAT service, Firewall, etc. In most cases, there is no public IP assigned to the IP addresses on the external interfaces (Virtual Servers, Self IP addresses, etc). - - - **New Stack**
This solution deploys into a new cloud network, this means that all of the cloud networking infrastructure required will be created along with the deployment. \ No newline at end of file + - **New Stack**
These templates deploy BIG-IP instances into a new cloud network. The required Azure virtual network and subnets will be created along with the deployment, and public IP addresses are created on all external Azure network interfaces and load balancers by default. + + - **Production Stack**
These templates have been deprecated. Production stack templates are still available for deployment in f5-azure-arm-templates release v6.1.0 or earlier. \ No newline at end of file diff --git a/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/README.md b/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/README.md index a17515b317..892da6400f 100644 --- a/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/README.md +++ b/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/README.md @@ -37,7 +37,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -62,6 +62,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -115,7 +116,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fwaf%2Fvia-dns%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fwaf%2Fvia-dns%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -194,47 +195,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules asm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --applicationProtocols http-https --applicationAddress --applicationPort 80 --applicationSecurePort 443 --sslCert NOT_SPECIFIED --sslPswd NOT_SPECIFIED --applicationType Linux --blockingLevel medium --customPolicy NOT_SPECIFIED --dnsMemberIpType private --dnsMemberPort 80 --dnsProviderHost --dnsProviderPort 443 --dnsProviderUser --dnsProviderPassword --dnsProviderPool autoscale_pool --dnsProviderDataCenter azure_datacenter --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/azuredeploy.json b/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/azuredeploy.json index ae34ac6416..5a5c4fb5a0 100644 --- a/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -586,7 +586,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -716,7 +716,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_dns-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_dns-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/azuredeploy.parameters.json index 786ab057bf..9573d1d8ba 100644 --- a/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/autoscale/waf/via-dns/1nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/README.md b/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/README.md index 1b83d05dd3..a020b610d2 100644 --- a/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/README.md +++ b/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/README.md @@ -36,7 +36,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -59,6 +59,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -112,7 +113,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fwaf%2Fvia-dns%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fwaf%2Fvia-dns%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -185,48 +186,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules asm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --applicationProtocols http-https --applicationAddress --applicationPort 80 --applicationSecurePort 443 --sslCert NOT_SPECIFIED --sslPswd NOT_SPECIFIED --applicationType Linux --blockingLevel medium --customPolicy NOT_SPECIFIED --dnsMemberIpType private --dnsMemberPort 80 --dnsProviderHost --dnsProviderPort 443 --dnsProviderUser --dnsProviderPassword --dnsProviderPool autoscale_pool --dnsProviderDataCenter azure_datacenter --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE appliance is through an Azure Load Balancer. The Azure Load Balancer processes both management and data plane traffic into the BIG-IP VEs, which then distribute the traffic to web/application servers according to normal F5 patterns. diff --git a/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/azuredeploy.json b/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/azuredeploy.json index bd98963d84..5450043f81 100644 --- a/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/azuredeploy.json +++ b/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -554,7 +554,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -721,7 +721,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_dns-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_dns-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/azuredeploy.parameters.json b/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/azuredeploy.parameters.json index 24c04690e8..15c596dbf2 100644 --- a/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/autoscale/waf/via-dns/1nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/README.md b/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/README.md index 5c2e24c42d..7879fd600f 100644 --- a/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/README.md +++ b/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/README.md @@ -37,7 +37,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -62,6 +62,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -115,7 +116,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fwaf%2Fvia-dns%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fwaf%2Fvia-dns%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -192,49 +193,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules asm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --applicationProtocols http-https --applicationAddress --applicationPort 80 --applicationSecurePort 443 --sslCert NOT_SPECIFIED --sslPswd NOT_SPECIFIED --applicationType Linux --blockingLevel medium --customPolicy NOT_SPECIFIED --dnsMemberIpType private --dnsMemberPort 80 --dnsProviderHost --dnsProviderPort 443 --dnsProviderUser --dnsProviderPassword --dnsProviderPool autoscale_pool --dnsProviderDataCenter azure_datacenter --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE appliance is through an Azure Load Balancer. The Azure Load Balancer processes both management and data plane traffic into the BIG-IP VEs, which then distribute the traffic to web/application servers according to normal F5 patterns. diff --git a/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/azuredeploy.json b/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/azuredeploy.json index 50017e7e71..9456247cef 100644 --- a/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/azuredeploy.json +++ b/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -575,7 +575,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -707,7 +707,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_dns-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_dns-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/azuredeploy.parameters.json index 8363f5bb7b..dc4494bcee 100644 --- a/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/autoscale/waf/via-dns/1nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/waf/via-dns/1nic/new-stack/payg/README.md b/supported/autoscale/waf/via-dns/1nic/new-stack/payg/README.md index e5a8759be8..57191bc98f 100644 --- a/supported/autoscale/waf/via-dns/1nic/new-stack/payg/README.md +++ b/supported/autoscale/waf/via-dns/1nic/new-stack/payg/README.md @@ -36,7 +36,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -59,6 +59,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -112,7 +113,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fwaf%2Fvia-dns%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fwaf%2Fvia-dns%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -183,49 +184,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules asm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --applicationProtocols http-https --applicationAddress --applicationPort 80 --applicationSecurePort 443 --sslCert NOT_SPECIFIED --sslPswd NOT_SPECIFIED --applicationType Linux --blockingLevel medium --customPolicy NOT_SPECIFIED --dnsMemberIpType private --dnsMemberPort 80 --dnsProviderHost --dnsProviderPort 443 --dnsProviderUser --dnsProviderPassword --dnsProviderPool autoscale_pool --dnsProviderDataCenter azure_datacenter --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE appliance is through an Azure Load Balancer. The Azure Load Balancer processes both management and data plane traffic into the BIG-IP VEs, which then distribute the traffic to web/application servers according to normal F5 patterns. diff --git a/supported/autoscale/waf/via-dns/1nic/new-stack/payg/azuredeploy.json b/supported/autoscale/waf/via-dns/1nic/new-stack/payg/azuredeploy.json index 64e3ccd818..c8ed1dce53 100644 --- a/supported/autoscale/waf/via-dns/1nic/new-stack/payg/azuredeploy.json +++ b/supported/autoscale/waf/via-dns/1nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -543,7 +543,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -712,7 +712,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_dns-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_dns-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/waf/via-dns/1nic/new-stack/payg/azuredeploy.parameters.json b/supported/autoscale/waf/via-dns/1nic/new-stack/payg/azuredeploy.parameters.json index 3b378c4157..3b50a422a1 100644 --- a/supported/autoscale/waf/via-dns/1nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/autoscale/waf/via-dns/1nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/waf/via-lb/1nic/README.md b/supported/autoscale/waf/via-lb/1nic/README.md index eeeafe2b8b..6018ca5fe3 100644 --- a/supported/autoscale/waf/via-lb/1nic/README.md +++ b/supported/autoscale/waf/via-lb/1nic/README.md @@ -2,8 +2,8 @@ For each of the standalone templates, you must choose the type of stack into which you want to deploy the BIG-IP VE. See the individual README files for exact requirements. Note that not all options are available for all templates. - - **Existing Stack**
These templates deploy into an existing cloud network. This means that all of the cloud networking infrastructure must be available prior to launching the template. + - **Existing Stack**
These templates deploy BIG-IP instances into an existing cloud network. This means that the Azure virtual network and subnets must be available prior to launching the template. If you choose "No" for the provisionPublicIP parameter, existing stack templates do not create or attach public IP addresses to the BIG-IP network interface(s). As BIG-IP VEs behind an Azure load balancer need external connectivity to download files for onboarding and access Cloud API services (autoscale only), these deployments will create a public front end IP configuration and load balancing rules on the external ALB. If Internet access is to be provided via another public NAT service, firewall, etc., F5 recommends removing this public configuration after deployment completes. - - **Production Stack**
Production stack templates also require the cloud networking infrastructure to be in place, however these templates do not create or attach a public IP address/NAT (there is never a public IP address assigned to the Management IP address). As BIG-IP VEs need access to the internet to access Cloud API services and download files for onboarding, these deployments assume Internet access is provided via another Public NAT service, Firewall, etc. In most cases, there is no public IP assigned to the IP addresses on the external interfaces (Virtual Servers, Self IP addresses, etc). - - - **New Stack**
This solution deploys into a new cloud network, this means that all of the cloud networking infrastructure required will be created along with the deployment. \ No newline at end of file + - **New Stack**
These templates deploy BIG-IP instances into a new cloud network. The required Azure virtual network and subnets will be created along with the deployment, and public IP addresses are created on all external Azure network interfaces and load balancers by default. + + - **Production Stack**
These templates have been deprecated. Production stack templates are still available for deployment in f5-azure-arm-templates release v6.1.0 or earlier. \ No newline at end of file diff --git a/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/README.md b/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/README.md index 4aa6241fec..c13c53910f 100644 --- a/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/README.md +++ b/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/README.md @@ -35,7 +35,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -60,6 +60,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -113,7 +114,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -185,48 +186,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules asm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --provisionPublicIP No --applicationProtocols http-https --applicationAddress --applicationPort 80 --applicationSecurePort 443 --sslCert NOT_SPECIFIED --sslPswd NOT_SPECIFIED --applicationType Linux --blockingLevel medium --customPolicy NOT_SPECIFIED --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE appliance is through an Azure Load Balancer. The Azure Load Balancer processes both management and data plane traffic into the BIG-IP VEs, which then distribute the traffic to web/application servers according to normal F5 patterns. diff --git a/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/azuredeploy.json b/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/azuredeploy.json index 57e32bd014..df82f225c9 100644 --- a/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -540,7 +540,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -670,7 +670,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json index 0779e1d517..25e1cfb07e 100644 --- a/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/autoscale/waf/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/README.md b/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/README.md index 6e4e65a955..aa5ddb0444 100644 --- a/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/README.md +++ b/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/README.md @@ -34,7 +34,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -57,6 +57,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -110,7 +111,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -176,47 +177,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules asm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --provisionPublicIP No --applicationProtocols http-https --applicationAddress --applicationPort 80 --applicationSecurePort 443 --sslCert NOT_SPECIFIED --sslPswd NOT_SPECIFIED --applicationType Linux --blockingLevel medium --customPolicy NOT_SPECIFIED --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/azuredeploy.json b/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/azuredeploy.json index 3f9069b08f..7b7259a586 100644 --- a/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/azuredeploy.json +++ b/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -508,7 +508,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -675,7 +675,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json b/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json index f23a4b1623..e76e8dee80 100644 --- a/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/autoscale/waf/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/README.md b/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/README.md index 0c3988b1ad..e8fa0c64ee 100644 --- a/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/README.md +++ b/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/README.md @@ -35,7 +35,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -60,6 +60,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -113,7 +114,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -183,49 +184,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules asm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --provisionPublicIP No --applicationProtocols http-https --applicationAddress --applicationPort 80 --applicationSecurePort 443 --sslCert NOT_SPECIFIED --sslPswd NOT_SPECIFIED --applicationType Linux --blockingLevel medium --customPolicy NOT_SPECIFIED --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE appliance is through an Azure Load Balancer. The Azure Load Balancer processes both management and data plane traffic into the BIG-IP VEs, which then distribute the traffic to web/application servers according to normal F5 patterns. diff --git a/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/azuredeploy.json b/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/azuredeploy.json index d4d8e61297..450e9374d8 100644 --- a/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/azuredeploy.json +++ b/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -529,7 +529,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -661,7 +661,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json index c8b56443a8..1f850c7d55 100644 --- a/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/autoscale/waf/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/autoscale/waf/via-lb/1nic/new-stack/payg/README.md b/supported/autoscale/waf/via-lb/1nic/new-stack/payg/README.md index d85ce471df..6344ee6139 100644 --- a/supported/autoscale/waf/via-lb/1nic/new-stack/payg/README.md +++ b/supported/autoscale/waf/via-lb/1nic/new-stack/payg/README.md @@ -34,7 +34,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -57,6 +57,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -110,7 +111,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fautoscale%2Fwaf%2Fvia-lb%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -174,48 +175,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules asm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --vmScaleSetMinCount 2 --vmScaleSetMaxCount 4 --appInsights CREATE_NEW --scaleOutCpuThreshold 80 --scaleInCpuThreshold 20 --scaleOutThroughputThreshold 20000000 --scaleInThroughputThreshold 10000000 --scaleOutTimeWindow 10 --scaleInTimeWindow 10 --notificationEmail OPTIONAL --provisionPublicIP No --applicationProtocols http-https --applicationAddress --applicationPort 80 --applicationSecurePort 443 --sslCert NOT_SPECIFIED --sslPswd NOT_SPECIFIED --applicationType Linux --blockingLevel medium --customPolicy NOT_SPECIFIED --tenantId --clientId --servicePrincipalSecret --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE appliance is through an Azure Load Balancer. The Azure Load Balancer processes both management and data plane traffic into the BIG-IP VEs, which then distribute the traffic to web/application servers according to normal F5 patterns. diff --git a/supported/autoscale/waf/via-lb/1nic/new-stack/payg/azuredeploy.json b/supported/autoscale/waf/via-lb/1nic/new-stack/payg/azuredeploy.json index f51aacc56b..4302dca8a6 100644 --- a/supported/autoscale/waf/via-lb/1nic/new-stack/payg/azuredeploy.json +++ b/supported/autoscale/waf/via-lb/1nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -497,7 +497,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -666,7 +666,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" + "metricsCmd": "[concat(' --usageAnalytics \\\" --metrics customerId:${custId},deploymentId:${deployId},templateName:as_waf_via-lb-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure\\\"')]" } }, "osProfiles": { diff --git a/supported/autoscale/waf/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json b/supported/autoscale/waf/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json index 64d7f5f739..36128d3c9a 100644 --- a/supported/autoscale/waf/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/autoscale/waf/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-api/n-nic/README.md b/supported/failover/same-net/via-api/n-nic/README.md index 8c779e20e2..6018ca5fe3 100644 --- a/supported/failover/same-net/via-api/n-nic/README.md +++ b/supported/failover/same-net/via-api/n-nic/README.md @@ -2,8 +2,8 @@ For each of the standalone templates, you must choose the type of stack into which you want to deploy the BIG-IP VE. See the individual README files for exact requirements. Note that not all options are available for all templates. - - **Existing Stack**
These templates deploy into an existing cloud network. This means that all of the cloud networking infrastructure must be available prior to launching the template. + - **Existing Stack**
These templates deploy BIG-IP instances into an existing cloud network. This means that the Azure virtual network and subnets must be available prior to launching the template. If you choose "No" for the provisionPublicIP parameter, existing stack templates do not create or attach public IP addresses to the BIG-IP network interface(s). As BIG-IP VEs behind an Azure load balancer need external connectivity to download files for onboarding and access Cloud API services (autoscale only), these deployments will create a public front end IP configuration and load balancing rules on the external ALB. If Internet access is to be provided via another public NAT service, firewall, etc., F5 recommends removing this public configuration after deployment completes. - - **Production Stack**
Production stack templates also require the cloud networking infrastructure to be in place, however these templates do not create or attach a public IP address/NAT (there is never a public IP address assigned to the Management IP address). As BIG-IP VEs need access to the internet to access Cloud API services and download files for onboarding, these deployments assume Internet access is provided via another Public NAT service, Firewall, etc. In most cases, there is no public IP assigned to the IP addresses on the external interfaces (Virtual Servers, Self IP addresses, etc). + - **New Stack**
These templates deploy BIG-IP instances into a new cloud network. The required Azure virtual network and subnets will be created along with the deployment, and public IP addresses are created on all external Azure network interfaces and load balancers by default. - - **New Stack**
This solution deploys into a new cloud network, this means that all of the cloud networking infrastructure required will be created along with the deployment. \ No newline at end of file + - **Production Stack**
These templates have been deprecated. Production stack templates are still available for deployment in f5-azure-arm-templates release v6.1.0 or earlier. \ No newline at end of file diff --git a/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/README.md b/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/README.md index 8d8f382bfd..4b2d62b80a 100644 --- a/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/README.md +++ b/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/README.md @@ -43,7 +43,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -72,6 +72,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. - All autoscale and failover-lb templates now deploy Standard SKU Azure Load Balancers. - The autoscale LTM and failover-lb NIC templates create a default port 443 load balancing rule and probe at deployment time; this rule is necessary to download required cloud libraries to BIG-IP and may be deleted or modified following a successful deployment. @@ -125,7 +126,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters diff --git a/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/azuredeploy.json b/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/azuredeploy.json index eb831de6e8..6b75297b0d 100644 --- a/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -543,7 +543,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -582,7 +582,7 @@ "appScript": "IyEvYmluL2Jhc2gKZnVuY3Rpb24gcGFzc3dkKCkgewogIGVjaG8gfCBmNS1yZXN0LW5vZGUgL2NvbmZpZy9jbG91ZC9henVyZS9ub2RlX21vZHVsZXMvQGY1ZGV2Y2VudHJhbC9mNS1jbG91ZC1saWJzL3NjcmlwdHMvZGVjcnlwdERhdGFGcm9tRmlsZS5qcyAtLWRhdGEtZmlsZSAvY29uZmlnL2Nsb3VkLy5wYXNzd2QgfCBhd2sgJ3twcmludCAkMX0nCn0KCndoaWxlIGdldG9wdHMgbzp1OiBvcHRpb24KZG8gY2FzZSAiJG9wdGlvbiIgIGluCiAgICAgICAgbykgZGVjbGFyYXRpb25Vcmw9JE9QVEFSRzs7CiAgICAgICAgdSkgdXNlcj0kT1BUQVJHOzsKICAgIGVzYWMKZG9uZQoKZGVwbG95ZWQ9Im5vIgpmaWxlX2xvYz0iL2NvbmZpZy9jbG91ZC9jdXN0b21fY29uZmlnIgpkZmxfbWdtdF9wb3J0PWB0bXNoIGxpc3Qgc3lzIGh0dHBkIHNzbC1wb3J0IHwgZ3JlcCBzc2wtcG9ydCB8IHNlZCAncy9zc2wtcG9ydCAvLztzLyAvL2cnYAp1cmxfcmVnZXg9IihodHRwOlwvXC98aHR0cHM6XC9cLyk/W2EtejAtOV0rKFtcLVwuXXsxfVthLXowLTldKykqXC5bYS16XXsyLDV9KDpbMC05XXsxLDV9KT8oXC8uKik/JCIKCmlmIFtbICRkZWNsYXJhdGlvblVybCA9fiAkdXJsX3JlZ2V4IF1dOyB0aGVuCiAgICByZXNwb25zZV9jb2RlPSQoL3Vzci9iaW4vY3VybCAtc2sgLXcgIiV7aHR0cF9jb2RlfSIgJGRlY2xhcmF0aW9uVXJsIC1vICRmaWxlX2xvYykKICAgIGlmIFtbICRyZXNwb25zZV9jb2RlID09IDIwMCBdXTsgdGhlbgogICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIGRvd25sb2FkIGNvbXBsZXRlOyBjaGVja2luZyBmb3IgdmFsaWQgSlNPTi4iCiAgICAgICAgIGNhdCAkZmlsZV9sb2MgfCBqcSAuY2xhc3MKICAgICAgICAgaWYgW1sgJD8gPT0gMCBdXTsgdGhlbgogICAgICAgICAgICAgcmVzcG9uc2VfY29kZT0kKC91c3IvYmluL2N1cmwgLXNrdnZ1ICR1c2VyOiQocGFzc3dkKSAtdyAiJXtodHRwX2NvZGV9IiAtWCBQT1NUIC1IICJDb250ZW50LVR5cGU6IGFwcGxpY2F0aW9uL2pzb24iIGh0dHBzOi8vbG9jYWxob3N0OiRkZmxfbWdtdF9wb3J0L21nbXQvc2hhcmVkL2FwcHN2Y3MvZGVjbGFyZSAtZCBAJGZpbGVfbG9jIC1vIC9kZXYvbnVsbCkKCiAgICAgICAgICAgICBpZiBbWyAkcmVzcG9uc2VfY29kZSA9PSAyMDAgfHwgJHJlc3BvbnNlX2NvZGUgPT0gNTAyIF1dOyB0aGVuCiAgICAgICAgICAgICAgICAgIGVjaG8gIkRlcGxveW1lbnQgb2YgYXBwbGljYXRpb24gc3VjY2VlZGVkLiIKICAgICAgICAgICAgICAgICAgZGVwbG95ZWQ9InllcyIKICAgICAgICAgICAgIGVsc2UKICAgICAgICAgICAgICAgICBlY2hvICJGYWlsZWQgdG8gZGVwbG95IGFwcGxpY2F0aW9uOyBjb250aW51aW5nIHdpdGggcmVzcG9uc2UgY29kZSAnIiRyZXNwb25zZV9jb2RlIiciCiAgICAgICAgICAgICBmaQogICAgICAgICBlbHNlCiAgICAgICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIHdhcyBub3QgdmFsaWQgSlNPTiwgY29udGludWluZyIKICAgICAgICAgZmkKICAgIGVsc2UKICAgICAgICBlY2hvICJGYWlsZWQgdG8gZG93bmxvYWQgY3VzdG9tIGNvbmZpZzsgY29udGludWluZyB3aXRoIHJlc3BvbnNlIGNvZGUgJyIkcmVzcG9uc2VfY29kZSInIgogICAgZmkKZWxzZQogICAgIGVjaG8gIkN1c3RvbSBjb25maWcgd2FzIG5vdCBhIFVSTCwgY29udGludWluZy4iCmZpCgppZiBbWyAkZGVwbG95ZWQgPT0gIm5vIiAmJiAkZGVjbGFyYXRpb25VcmwgPT0gIk5PVF9TUEVDSUZJRUQiIF1dOyB0aGVuCiAgICBlY2hvICJBcHBsaWNhdGlvbiBkZXBsb3ltZW50IGZhaWxlZCBvciBjdXN0b20gVVJMIHdhcyBub3Qgc3BlY2lmaWVkLiIKZmkKCmVjaG8gIkRlcGxveW1lbnQgY29tcGxldGUuIgpleGl0", "extSubnetPrivateAddressSuffixInt": "[int(variables('extSubnetPrivateAddressPrefixArray')[3])]", "extSubnetName": "[parameters('externalSubnetName')]", - "extSubnetPrivateAddress": "[parameters('externalIpAddressRangeStart')]", + "extSubnetPrivateAddress": "[parameters('externalIpSelfAddressRangeStart')]", "extSubnetPrivateAddressPrefix": "[concat(variables('extSubnetPrivateAddressPrefixArray')[0], '.', variables('extSubnetPrivateAddressPrefixArray')[1], '.', variables('extSubnetPrivateAddressPrefixArray')[2], '.')]", "extNsgID": "[resourceId('Microsoft.Network/networkSecurityGroups/',concat(variables('dnsLabel'),'-ext-nsg'))]", "extSelfPublicIpAddressNamePrefix": "[concat(variables('dnsLabel'), '-self-pip')]", @@ -671,7 +671,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -757,7 +757,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -854,7 +854,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations'), 0), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations'), 1))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations'), 0), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/azuredeploy.parameters.json index aa8baeabbf..775ebab55e 100644 --- a/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-api/n-nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-api/n-nic/existing-stack/byol/README.md b/supported/failover/same-net/via-api/n-nic/existing-stack/byol/README.md index 4acfc429da..923592fa8c 100644 --- a/supported/failover/same-net/via-api/n-nic/existing-stack/byol/README.md +++ b/supported/failover/same-net/via-api/n-nic/existing-stack/byol/README.md @@ -43,7 +43,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -71,6 +71,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -122,7 +123,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -213,6 +214,16 @@ From the volume to be upgraded on the standby device, you must edit **cs.dat** t 9. Download myUCS.ucs locally. +10. Install new ISO and reboot into upgraded volume. + +11. Boot into the newly upgraded volume. + +12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. + +13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: + - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** + - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** + ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, each BIG-IP has one NIC for management, one NIC for external traffic and one NIC for internal traffic. This is the traditional BIG-IP deployment model where data-plane, management and internal traffic is separate. The IP addresses in this example may be different in your implementation. diff --git a/supported/failover/same-net/via-api/n-nic/existing-stack/byol/azuredeploy.json b/supported/failover/same-net/via-api/n-nic/existing-stack/byol/azuredeploy.json index b566b5fd30..f48cb806e8 100644 --- a/supported/failover/same-net/via-api/n-nic/existing-stack/byol/azuredeploy.json +++ b/supported/failover/same-net/via-api/n-nic/existing-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -519,7 +519,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -558,7 +558,7 @@ "appScript": "IyEvYmluL2Jhc2gKZnVuY3Rpb24gcGFzc3dkKCkgewogIGVjaG8gfCBmNS1yZXN0LW5vZGUgL2NvbmZpZy9jbG91ZC9henVyZS9ub2RlX21vZHVsZXMvQGY1ZGV2Y2VudHJhbC9mNS1jbG91ZC1saWJzL3NjcmlwdHMvZGVjcnlwdERhdGFGcm9tRmlsZS5qcyAtLWRhdGEtZmlsZSAvY29uZmlnL2Nsb3VkLy5wYXNzd2QgfCBhd2sgJ3twcmludCAkMX0nCn0KCndoaWxlIGdldG9wdHMgbzp1OiBvcHRpb24KZG8gY2FzZSAiJG9wdGlvbiIgIGluCiAgICAgICAgbykgZGVjbGFyYXRpb25Vcmw9JE9QVEFSRzs7CiAgICAgICAgdSkgdXNlcj0kT1BUQVJHOzsKICAgIGVzYWMKZG9uZQoKZGVwbG95ZWQ9Im5vIgpmaWxlX2xvYz0iL2NvbmZpZy9jbG91ZC9jdXN0b21fY29uZmlnIgpkZmxfbWdtdF9wb3J0PWB0bXNoIGxpc3Qgc3lzIGh0dHBkIHNzbC1wb3J0IHwgZ3JlcCBzc2wtcG9ydCB8IHNlZCAncy9zc2wtcG9ydCAvLztzLyAvL2cnYAp1cmxfcmVnZXg9IihodHRwOlwvXC98aHR0cHM6XC9cLyk/W2EtejAtOV0rKFtcLVwuXXsxfVthLXowLTldKykqXC5bYS16XXsyLDV9KDpbMC05XXsxLDV9KT8oXC8uKik/JCIKCmlmIFtbICRkZWNsYXJhdGlvblVybCA9fiAkdXJsX3JlZ2V4IF1dOyB0aGVuCiAgICByZXNwb25zZV9jb2RlPSQoL3Vzci9iaW4vY3VybCAtc2sgLXcgIiV7aHR0cF9jb2RlfSIgJGRlY2xhcmF0aW9uVXJsIC1vICRmaWxlX2xvYykKICAgIGlmIFtbICRyZXNwb25zZV9jb2RlID09IDIwMCBdXTsgdGhlbgogICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIGRvd25sb2FkIGNvbXBsZXRlOyBjaGVja2luZyBmb3IgdmFsaWQgSlNPTi4iCiAgICAgICAgIGNhdCAkZmlsZV9sb2MgfCBqcSAuY2xhc3MKICAgICAgICAgaWYgW1sgJD8gPT0gMCBdXTsgdGhlbgogICAgICAgICAgICAgcmVzcG9uc2VfY29kZT0kKC91c3IvYmluL2N1cmwgLXNrdnZ1ICR1c2VyOiQocGFzc3dkKSAtdyAiJXtodHRwX2NvZGV9IiAtWCBQT1NUIC1IICJDb250ZW50LVR5cGU6IGFwcGxpY2F0aW9uL2pzb24iIGh0dHBzOi8vbG9jYWxob3N0OiRkZmxfbWdtdF9wb3J0L21nbXQvc2hhcmVkL2FwcHN2Y3MvZGVjbGFyZSAtZCBAJGZpbGVfbG9jIC1vIC9kZXYvbnVsbCkKCiAgICAgICAgICAgICBpZiBbWyAkcmVzcG9uc2VfY29kZSA9PSAyMDAgfHwgJHJlc3BvbnNlX2NvZGUgPT0gNTAyIF1dOyB0aGVuCiAgICAgICAgICAgICAgICAgIGVjaG8gIkRlcGxveW1lbnQgb2YgYXBwbGljYXRpb24gc3VjY2VlZGVkLiIKICAgICAgICAgICAgICAgICAgZGVwbG95ZWQ9InllcyIKICAgICAgICAgICAgIGVsc2UKICAgICAgICAgICAgICAgICBlY2hvICJGYWlsZWQgdG8gZGVwbG95IGFwcGxpY2F0aW9uOyBjb250aW51aW5nIHdpdGggcmVzcG9uc2UgY29kZSAnIiRyZXNwb25zZV9jb2RlIiciCiAgICAgICAgICAgICBmaQogICAgICAgICBlbHNlCiAgICAgICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIHdhcyBub3QgdmFsaWQgSlNPTiwgY29udGludWluZyIKICAgICAgICAgZmkKICAgIGVsc2UKICAgICAgICBlY2hvICJGYWlsZWQgdG8gZG93bmxvYWQgY3VzdG9tIGNvbmZpZzsgY29udGludWluZyB3aXRoIHJlc3BvbnNlIGNvZGUgJyIkcmVzcG9uc2VfY29kZSInIgogICAgZmkKZWxzZQogICAgIGVjaG8gIkN1c3RvbSBjb25maWcgd2FzIG5vdCBhIFVSTCwgY29udGludWluZy4iCmZpCgppZiBbWyAkZGVwbG95ZWQgPT0gIm5vIiAmJiAkZGVjbGFyYXRpb25VcmwgPT0gIk5PVF9TUEVDSUZJRUQiIF1dOyB0aGVuCiAgICBlY2hvICJBcHBsaWNhdGlvbiBkZXBsb3ltZW50IGZhaWxlZCBvciBjdXN0b20gVVJMIHdhcyBub3Qgc3BlY2lmaWVkLiIKZmkKCmVjaG8gIkRlcGxveW1lbnQgY29tcGxldGUuIgpleGl0", "extSubnetPrivateAddressSuffixInt": "[int(variables('extSubnetPrivateAddressPrefixArray')[3])]", "extSubnetName": "[parameters('externalSubnetName')]", - "extSubnetPrivateAddress": "[parameters('externalIpAddressRangeStart')]", + "extSubnetPrivateAddress": "[parameters('externalIpSelfAddressRangeStart')]", "extSubnetPrivateAddressPrefix": "[concat(variables('extSubnetPrivateAddressPrefixArray')[0], '.', variables('extSubnetPrivateAddressPrefixArray')[1], '.', variables('extSubnetPrivateAddressPrefixArray')[2], '.')]", "extNsgID": "[resourceId('Microsoft.Network/networkSecurityGroups/',concat(variables('dnsLabel'),'-ext-nsg'))]", "extSelfPublicIpAddressNamePrefix": "[concat(variables('dnsLabel'), '-self-pip')]", @@ -647,7 +647,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-existing-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-existing-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -733,7 +733,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -830,7 +830,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations'), 0), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations'), 1))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations'), 0), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/failover/same-net/via-api/n-nic/existing-stack/byol/azuredeploy.parameters.json b/supported/failover/same-net/via-api/n-nic/existing-stack/byol/azuredeploy.parameters.json index 969520cd27..e8e86d4513 100644 --- a/supported/failover/same-net/via-api/n-nic/existing-stack/byol/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-api/n-nic/existing-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-api/n-nic/existing-stack/payg/README.md b/supported/failover/same-net/via-api/n-nic/existing-stack/payg/README.md index 697d1a6683..1161d7f7db 100644 --- a/supported/failover/same-net/via-api/n-nic/existing-stack/payg/README.md +++ b/supported/failover/same-net/via-api/n-nic/existing-stack/payg/README.md @@ -42,7 +42,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -69,6 +69,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -120,7 +121,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters diff --git a/supported/failover/same-net/via-api/n-nic/existing-stack/payg/azuredeploy.json b/supported/failover/same-net/via-api/n-nic/existing-stack/payg/azuredeploy.json index 1215ed165e..ee22722494 100644 --- a/supported/failover/same-net/via-api/n-nic/existing-stack/payg/azuredeploy.json +++ b/supported/failover/same-net/via-api/n-nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -515,7 +515,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -554,7 +554,7 @@ "appScript": "IyEvYmluL2Jhc2gKZnVuY3Rpb24gcGFzc3dkKCkgewogIGVjaG8gfCBmNS1yZXN0LW5vZGUgL2NvbmZpZy9jbG91ZC9henVyZS9ub2RlX21vZHVsZXMvQGY1ZGV2Y2VudHJhbC9mNS1jbG91ZC1saWJzL3NjcmlwdHMvZGVjcnlwdERhdGFGcm9tRmlsZS5qcyAtLWRhdGEtZmlsZSAvY29uZmlnL2Nsb3VkLy5wYXNzd2QgfCBhd2sgJ3twcmludCAkMX0nCn0KCndoaWxlIGdldG9wdHMgbzp1OiBvcHRpb24KZG8gY2FzZSAiJG9wdGlvbiIgIGluCiAgICAgICAgbykgZGVjbGFyYXRpb25Vcmw9JE9QVEFSRzs7CiAgICAgICAgdSkgdXNlcj0kT1BUQVJHOzsKICAgIGVzYWMKZG9uZQoKZGVwbG95ZWQ9Im5vIgpmaWxlX2xvYz0iL2NvbmZpZy9jbG91ZC9jdXN0b21fY29uZmlnIgpkZmxfbWdtdF9wb3J0PWB0bXNoIGxpc3Qgc3lzIGh0dHBkIHNzbC1wb3J0IHwgZ3JlcCBzc2wtcG9ydCB8IHNlZCAncy9zc2wtcG9ydCAvLztzLyAvL2cnYAp1cmxfcmVnZXg9IihodHRwOlwvXC98aHR0cHM6XC9cLyk/W2EtejAtOV0rKFtcLVwuXXsxfVthLXowLTldKykqXC5bYS16XXsyLDV9KDpbMC05XXsxLDV9KT8oXC8uKik/JCIKCmlmIFtbICRkZWNsYXJhdGlvblVybCA9fiAkdXJsX3JlZ2V4IF1dOyB0aGVuCiAgICByZXNwb25zZV9jb2RlPSQoL3Vzci9iaW4vY3VybCAtc2sgLXcgIiV7aHR0cF9jb2RlfSIgJGRlY2xhcmF0aW9uVXJsIC1vICRmaWxlX2xvYykKICAgIGlmIFtbICRyZXNwb25zZV9jb2RlID09IDIwMCBdXTsgdGhlbgogICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIGRvd25sb2FkIGNvbXBsZXRlOyBjaGVja2luZyBmb3IgdmFsaWQgSlNPTi4iCiAgICAgICAgIGNhdCAkZmlsZV9sb2MgfCBqcSAuY2xhc3MKICAgICAgICAgaWYgW1sgJD8gPT0gMCBdXTsgdGhlbgogICAgICAgICAgICAgcmVzcG9uc2VfY29kZT0kKC91c3IvYmluL2N1cmwgLXNrdnZ1ICR1c2VyOiQocGFzc3dkKSAtdyAiJXtodHRwX2NvZGV9IiAtWCBQT1NUIC1IICJDb250ZW50LVR5cGU6IGFwcGxpY2F0aW9uL2pzb24iIGh0dHBzOi8vbG9jYWxob3N0OiRkZmxfbWdtdF9wb3J0L21nbXQvc2hhcmVkL2FwcHN2Y3MvZGVjbGFyZSAtZCBAJGZpbGVfbG9jIC1vIC9kZXYvbnVsbCkKCiAgICAgICAgICAgICBpZiBbWyAkcmVzcG9uc2VfY29kZSA9PSAyMDAgfHwgJHJlc3BvbnNlX2NvZGUgPT0gNTAyIF1dOyB0aGVuCiAgICAgICAgICAgICAgICAgIGVjaG8gIkRlcGxveW1lbnQgb2YgYXBwbGljYXRpb24gc3VjY2VlZGVkLiIKICAgICAgICAgICAgICAgICAgZGVwbG95ZWQ9InllcyIKICAgICAgICAgICAgIGVsc2UKICAgICAgICAgICAgICAgICBlY2hvICJGYWlsZWQgdG8gZGVwbG95IGFwcGxpY2F0aW9uOyBjb250aW51aW5nIHdpdGggcmVzcG9uc2UgY29kZSAnIiRyZXNwb25zZV9jb2RlIiciCiAgICAgICAgICAgICBmaQogICAgICAgICBlbHNlCiAgICAgICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIHdhcyBub3QgdmFsaWQgSlNPTiwgY29udGludWluZyIKICAgICAgICAgZmkKICAgIGVsc2UKICAgICAgICBlY2hvICJGYWlsZWQgdG8gZG93bmxvYWQgY3VzdG9tIGNvbmZpZzsgY29udGludWluZyB3aXRoIHJlc3BvbnNlIGNvZGUgJyIkcmVzcG9uc2VfY29kZSInIgogICAgZmkKZWxzZQogICAgIGVjaG8gIkN1c3RvbSBjb25maWcgd2FzIG5vdCBhIFVSTCwgY29udGludWluZy4iCmZpCgppZiBbWyAkZGVwbG95ZWQgPT0gIm5vIiAmJiAkZGVjbGFyYXRpb25VcmwgPT0gIk5PVF9TUEVDSUZJRUQiIF1dOyB0aGVuCiAgICBlY2hvICJBcHBsaWNhdGlvbiBkZXBsb3ltZW50IGZhaWxlZCBvciBjdXN0b20gVVJMIHdhcyBub3Qgc3BlY2lmaWVkLiIKZmkKCmVjaG8gIkRlcGxveW1lbnQgY29tcGxldGUuIgpleGl0", "extSubnetPrivateAddressSuffixInt": "[int(variables('extSubnetPrivateAddressPrefixArray')[3])]", "extSubnetName": "[parameters('externalSubnetName')]", - "extSubnetPrivateAddress": "[parameters('externalIpAddressRangeStart')]", + "extSubnetPrivateAddress": "[parameters('externalIpSelfAddressRangeStart')]", "extSubnetPrivateAddressPrefix": "[concat(variables('extSubnetPrivateAddressPrefixArray')[0], '.', variables('extSubnetPrivateAddressPrefixArray')[1], '.', variables('extSubnetPrivateAddressPrefixArray')[2], '.')]", "extNsgID": "[resourceId('Microsoft.Network/networkSecurityGroups/',concat(variables('dnsLabel'),'-ext-nsg'))]", "extSelfPublicIpAddressNamePrefix": "[concat(variables('dnsLabel'), '-self-pip')]", @@ -680,7 +680,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -766,7 +766,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -863,7 +863,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations'), 0), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations'), 1))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations'), 0), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/failover/same-net/via-api/n-nic/existing-stack/payg/azuredeploy.parameters.json b/supported/failover/same-net/via-api/n-nic/existing-stack/payg/azuredeploy.parameters.json index a25d2c87dd..68588385d1 100644 --- a/supported/failover/same-net/via-api/n-nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-api/n-nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/README.md b/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/README.md index 8e1a6f45d7..d04af133d8 100644 --- a/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/README.md +++ b/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/README.md @@ -43,7 +43,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -72,6 +72,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -123,7 +124,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters diff --git a/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/azuredeploy.json b/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/azuredeploy.json index 0a71d7308c..c70540f870 100644 --- a/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/azuredeploy.json +++ b/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -485,7 +485,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -653,7 +653,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -856,7 +856,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations'), 0), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations'), 1)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations'), 0), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/azuredeploy.parameters.json index 7c734feb64..341d0fd0cb 100644 --- a/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-api/n-nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-api/n-nic/new-stack/byol/README.md b/supported/failover/same-net/via-api/n-nic/new-stack/byol/README.md index f15f85a91d..bfbc0ea106 100644 --- a/supported/failover/same-net/via-api/n-nic/new-stack/byol/README.md +++ b/supported/failover/same-net/via-api/n-nic/new-stack/byol/README.md @@ -43,7 +43,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -71,6 +71,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. @@ -123,7 +124,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters diff --git a/supported/failover/same-net/via-api/n-nic/new-stack/byol/azuredeploy.json b/supported/failover/same-net/via-api/n-nic/new-stack/byol/azuredeploy.json index 3621d235da..e037be3449 100644 --- a/supported/failover/same-net/via-api/n-nic/new-stack/byol/azuredeploy.json +++ b/supported/failover/same-net/via-api/n-nic/new-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -461,7 +461,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -629,7 +629,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-new-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-new-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -832,7 +832,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations'), 0), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations'), 1)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations'), 0), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/failover/same-net/via-api/n-nic/new-stack/byol/azuredeploy.parameters.json b/supported/failover/same-net/via-api/n-nic/new-stack/byol/azuredeploy.parameters.json index 4ab008e232..44e3d271a6 100644 --- a/supported/failover/same-net/via-api/n-nic/new-stack/byol/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-api/n-nic/new-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-api/n-nic/new-stack/payg/README.md b/supported/failover/same-net/via-api/n-nic/new-stack/payg/README.md index c8a0cc4176..b7df5f4595 100644 --- a/supported/failover/same-net/via-api/n-nic/new-stack/payg/README.md +++ b/supported/failover/same-net/via-api/n-nic/new-stack/payg/README.md @@ -42,7 +42,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -69,6 +69,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -120,7 +121,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-api%2Fn-nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters diff --git a/supported/failover/same-net/via-api/n-nic/new-stack/payg/azuredeploy.json b/supported/failover/same-net/via-api/n-nic/new-stack/payg/azuredeploy.json index e4e64a0a83..dd8fa6ad33 100644 --- a/supported/failover/same-net/via-api/n-nic/new-stack/payg/azuredeploy.json +++ b/supported/failover/same-net/via-api/n-nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -457,7 +457,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -662,7 +662,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_nnic-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -865,7 +865,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations'), 0), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations'), 1)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations'), 0), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations'), 0), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations'), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/failover/same-net/via-api/n-nic/new-stack/payg/azuredeploy.parameters.json b/supported/failover/same-net/via-api/n-nic/new-stack/payg/azuredeploy.parameters.json index cd5948e7d3..4ee2722543 100644 --- a/supported/failover/same-net/via-api/n-nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-api/n-nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/README.md b/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/README.md index bdbc7afc2c..057c993d16 100644 --- a/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/README.md +++ b/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -53,6 +53,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -104,7 +105,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -156,48 +157,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddressRangeStart --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfInstances 2 --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. The IP addresses in this example may be different in your implementation. diff --git a/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/azuredeploy.json b/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/azuredeploy.json index 728e0c6088..3d0ec0fd20 100644 --- a/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -366,7 +366,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -406,7 +406,6 @@ "mgmtSubnetPrivateAddressPrefix": "[concat(variables('mgmtSubnetPrivateAddressPrefixArray')[0], '.', variables('mgmtSubnetPrivateAddressPrefixArray')[1], '.', variables('mgmtSubnetPrivateAddressPrefixArray')[2], '.')]", "mgmtSubnetPrivateAddressSuffix": "[int(variables('mgmtSubnetPrivateAddressPrefixArray')[3])]", "mgmtSubnetPrivateAddressSuffix1": "[add(variables('mgmtSubnetPrivateAddressSuffix'), 1)]", - "externalLoadBalancerAddress": "[concat(variables('mgmtSubnetPrivateAddress'), add(variables('mgmtSubnetPrivateAddressSuffix1'), 1))]", "provisionPublicIP": "[parameters('provisionPublicIP')]", "imageNameSub": "[variables('imageNameArray')[parameters('bigIpVersion')][parameters('imageName')]]", "imageNameArray": { @@ -460,7 +459,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -832,11 +831,11 @@ "outputs": { "GUI-URL": { "type": "string", - "value": "[if(equals(parameters('provisionPublicIP'),'No'), concat('https://', variables('externalLoadBalancerAddress'), ':8443'), concat('https://',reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,':8443'))]" + "value": "[concat('https://',reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,':8443')]" }, "SSH-URL": { "type": "string", - "value": "[if(equals(parameters('provisionPublicIP'),'No'), concat(variables('externalLoadBalancerAddress'), ' ', 8022), concat(reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,' ',8022))]" + "value": "[concat(reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,' ',8022)]" } } } \ No newline at end of file diff --git a/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json index 39edb35f00..c30d31fc3c 100644 --- a/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/1nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/1nic/existing-stack/byol/README.md b/supported/failover/same-net/via-lb/1nic/existing-stack/byol/README.md index 4a36a436a6..ccb373348e 100644 --- a/supported/failover/same-net/via-lb/1nic/existing-stack/byol/README.md +++ b/supported/failover/same-net/via-lb/1nic/existing-stack/byol/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -52,6 +52,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -103,7 +104,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -151,48 +152,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --licenseKey2 --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddressRangeStart --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfInstances 2 --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. The IP addresses in this example may be different in your implementation. diff --git a/supported/failover/same-net/via-lb/1nic/existing-stack/byol/azuredeploy.json b/supported/failover/same-net/via-lb/1nic/existing-stack/byol/azuredeploy.json index 1c8ad1b23a..175632ebd3 100644 --- a/supported/failover/same-net/via-lb/1nic/existing-stack/byol/azuredeploy.json +++ b/supported/failover/same-net/via-lb/1nic/existing-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -342,7 +342,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -382,7 +382,6 @@ "mgmtSubnetPrivateAddressPrefix": "[concat(variables('mgmtSubnetPrivateAddressPrefixArray')[0], '.', variables('mgmtSubnetPrivateAddressPrefixArray')[1], '.', variables('mgmtSubnetPrivateAddressPrefixArray')[2], '.')]", "mgmtSubnetPrivateAddressSuffix": "[int(variables('mgmtSubnetPrivateAddressPrefixArray')[3])]", "mgmtSubnetPrivateAddressSuffix1": "[add(variables('mgmtSubnetPrivateAddressSuffix'), 1)]", - "externalLoadBalancerAddress": "[concat(variables('mgmtSubnetPrivateAddress'), add(variables('mgmtSubnetPrivateAddressSuffix1'), 1))]", "provisionPublicIP": "[parameters('provisionPublicIP')]", "imageNameSub": "[variables('imageNameArray')[parameters('bigIpVersion')][parameters('imageName')]]", "imageNameArray": { @@ -436,7 +435,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-existing-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-existing-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -808,11 +807,11 @@ "outputs": { "GUI-URL": { "type": "string", - "value": "[if(equals(parameters('provisionPublicIP'),'No'), concat('https://', variables('externalLoadBalancerAddress'), ':8443'), concat('https://',reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,':8443'))]" + "value": "[concat('https://',reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,':8443')]" }, "SSH-URL": { "type": "string", - "value": "[if(equals(parameters('provisionPublicIP'),'No'), concat(variables('externalLoadBalancerAddress'), ' ', 8022), concat(reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,' ',8022))]" + "value": "[concat(reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,' ',8022)]" } } } \ No newline at end of file diff --git a/supported/failover/same-net/via-lb/1nic/existing-stack/byol/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/1nic/existing-stack/byol/azuredeploy.parameters.json index 5fb60bb47c..77da189238 100644 --- a/supported/failover/same-net/via-lb/1nic/existing-stack/byol/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/1nic/existing-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/1nic/existing-stack/payg/README.md b/supported/failover/same-net/via-lb/1nic/existing-stack/payg/README.md index a9bc37f340..4e03aa784e 100644 --- a/supported/failover/same-net/via-lb/1nic/existing-stack/payg/README.md +++ b/supported/failover/same-net/via-lb/1nic/existing-stack/payg/README.md @@ -31,7 +31,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -50,6 +50,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -101,7 +102,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -147,48 +148,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddressRangeStart --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfInstances 2 --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. The IP addresses in this example may be different in your implementation. diff --git a/supported/failover/same-net/via-lb/1nic/existing-stack/payg/azuredeploy.json b/supported/failover/same-net/via-lb/1nic/existing-stack/payg/azuredeploy.json index 3a972e765c..f8b629fced 100644 --- a/supported/failover/same-net/via-lb/1nic/existing-stack/payg/azuredeploy.json +++ b/supported/failover/same-net/via-lb/1nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -338,7 +338,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -378,7 +378,6 @@ "mgmtSubnetPrivateAddressPrefix": "[concat(variables('mgmtSubnetPrivateAddressPrefixArray')[0], '.', variables('mgmtSubnetPrivateAddressPrefixArray')[1], '.', variables('mgmtSubnetPrivateAddressPrefixArray')[2], '.')]", "mgmtSubnetPrivateAddressSuffix": "[int(variables('mgmtSubnetPrivateAddressPrefixArray')[3])]", "mgmtSubnetPrivateAddressSuffix1": "[add(variables('mgmtSubnetPrivateAddressSuffix'), 1)]", - "externalLoadBalancerAddress": "[concat(variables('mgmtSubnetPrivateAddress'), add(variables('mgmtSubnetPrivateAddressSuffix1'), 1))]", "provisionPublicIP": "[parameters('provisionPublicIP')]", "paygImageMap": { "advancedwaf1gbps": { @@ -469,7 +468,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -841,11 +840,11 @@ "outputs": { "GUI-URL": { "type": "string", - "value": "[if(equals(parameters('provisionPublicIP'),'No'), concat('https://', variables('externalLoadBalancerAddress'), ':8443'), concat('https://',reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,':8443'))]" + "value": "[concat('https://',reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,':8443')]" }, "SSH-URL": { "type": "string", - "value": "[if(equals(parameters('provisionPublicIP'),'No'), concat(variables('externalLoadBalancerAddress'), ' ', 8022), concat(reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,' ',8022))]" + "value": "[concat(reference(variables('mgmtPublicIPAddressId')).dnsSettings.fqdn,' ',8022)]" } } } \ No newline at end of file diff --git a/supported/failover/same-net/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json index 70d14c0711..bfd490a332 100644 --- a/supported/failover/same-net/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/1nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/README.md b/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/README.md index c3fc3d4bf8..e88b9cc2e2 100644 --- a/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/README.md +++ b/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -53,6 +53,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -104,7 +105,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -152,48 +153,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfInstances 2 --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. The IP addresses in this example may be different in your implementation. diff --git a/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/azuredeploy.json b/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/azuredeploy.json index 37db2e12c7..71477eec20 100644 --- a/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/azuredeploy.json +++ b/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -338,7 +338,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -430,7 +430,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { diff --git a/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json index aa74e92d6e..ec805c4214 100644 --- a/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/1nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/1nic/new-stack/byol/README.md b/supported/failover/same-net/via-lb/1nic/new-stack/byol/README.md index a4b08373c4..cbe3277cc2 100644 --- a/supported/failover/same-net/via-lb/1nic/new-stack/byol/README.md +++ b/supported/failover/same-net/via-lb/1nic/new-stack/byol/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -52,6 +52,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -103,7 +104,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -147,48 +148,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --licenseKey2 --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfInstances 2 --resourceGroupName --azureLoginUser --azureLoginPassword ``` - -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. The IP addresses in this example may be different in your implementation. diff --git a/supported/failover/same-net/via-lb/1nic/new-stack/byol/azuredeploy.json b/supported/failover/same-net/via-lb/1nic/new-stack/byol/azuredeploy.json index 77353f0de5..9e028e827c 100644 --- a/supported/failover/same-net/via-lb/1nic/new-stack/byol/azuredeploy.json +++ b/supported/failover/same-net/via-lb/1nic/new-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -314,7 +314,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -406,7 +406,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-new-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-new-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { diff --git a/supported/failover/same-net/via-lb/1nic/new-stack/byol/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/1nic/new-stack/byol/azuredeploy.parameters.json index 17eea69da6..f318a168b1 100644 --- a/supported/failover/same-net/via-lb/1nic/new-stack/byol/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/1nic/new-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/1nic/new-stack/payg/README.md b/supported/failover/same-net/via-lb/1nic/new-stack/payg/README.md index 5560f8f405..fca5d7bced 100644 --- a/supported/failover/same-net/via-lb/1nic/new-stack/payg/README.md +++ b/supported/failover/same-net/via-lb/1nic/new-stack/payg/README.md @@ -31,7 +31,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -50,6 +50,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -101,7 +102,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -143,47 +144,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfInstances 2 --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. The IP addresses in this example may be different in your implementation. diff --git a/supported/failover/same-net/via-lb/1nic/new-stack/payg/azuredeploy.json b/supported/failover/same-net/via-lb/1nic/new-stack/payg/azuredeploy.json index a1e35e09dd..c351678fde 100644 --- a/supported/failover/same-net/via-lb/1nic/new-stack/payg/azuredeploy.json +++ b/supported/failover/same-net/via-lb/1nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -310,7 +310,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -439,7 +439,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_1nic-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { diff --git a/supported/failover/same-net/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json index dea0e9a395..7d378293ec 100644 --- a/supported/failover/same-net/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/1nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/3nic/README.md b/supported/failover/same-net/via-lb/3nic/README.md index 8c779e20e2..6018ca5fe3 100644 --- a/supported/failover/same-net/via-lb/3nic/README.md +++ b/supported/failover/same-net/via-lb/3nic/README.md @@ -2,8 +2,8 @@ For each of the standalone templates, you must choose the type of stack into which you want to deploy the BIG-IP VE. See the individual README files for exact requirements. Note that not all options are available for all templates. - - **Existing Stack**
These templates deploy into an existing cloud network. This means that all of the cloud networking infrastructure must be available prior to launching the template. + - **Existing Stack**
These templates deploy BIG-IP instances into an existing cloud network. This means that the Azure virtual network and subnets must be available prior to launching the template. If you choose "No" for the provisionPublicIP parameter, existing stack templates do not create or attach public IP addresses to the BIG-IP network interface(s). As BIG-IP VEs behind an Azure load balancer need external connectivity to download files for onboarding and access Cloud API services (autoscale only), these deployments will create a public front end IP configuration and load balancing rules on the external ALB. If Internet access is to be provided via another public NAT service, firewall, etc., F5 recommends removing this public configuration after deployment completes. - - **Production Stack**
Production stack templates also require the cloud networking infrastructure to be in place, however these templates do not create or attach a public IP address/NAT (there is never a public IP address assigned to the Management IP address). As BIG-IP VEs need access to the internet to access Cloud API services and download files for onboarding, these deployments assume Internet access is provided via another Public NAT service, Firewall, etc. In most cases, there is no public IP assigned to the IP addresses on the external interfaces (Virtual Servers, Self IP addresses, etc). + - **New Stack**
These templates deploy BIG-IP instances into a new cloud network. The required Azure virtual network and subnets will be created along with the deployment, and public IP addresses are created on all external Azure network interfaces and load balancers by default. - - **New Stack**
This solution deploys into a new cloud network, this means that all of the cloud networking infrastructure required will be created along with the deployment. \ No newline at end of file + - **Production Stack**
These templates have been deprecated. Production stack templates are still available for deployment in f5-azure-arm-templates release v6.1.0 or earlier. \ No newline at end of file diff --git a/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/README.md b/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/README.md index e1521827e1..ef9c72d4de 100644 --- a/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/README.md +++ b/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/README.md @@ -42,7 +42,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -64,6 +64,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -115,7 +116,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -176,48 +177,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --enableNetworkFailover Yes --internalLoadBalancerType Per-protocol --internalLoadBalancerProbePort 3456 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddressRangeStart --externalSubnetName --externalIpAddressRangeStart --externalIpSelfAddressRangeStart --internalSubnetName --internalIpAddressRangeStart --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. For diagrams of alternate deployment topologies, see [alternate topologies](../../alternate-deployment-topologies.md). diff --git a/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/azuredeploy.json b/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/azuredeploy.json index 8a8e94fb40..4724c740bc 100644 --- a/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -444,7 +444,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -490,7 +490,7 @@ "appScript": "IyEvYmluL2Jhc2gKZnVuY3Rpb24gcGFzc3dkKCkgewogIGVjaG8gfCBmNS1yZXN0LW5vZGUgL2NvbmZpZy9jbG91ZC9henVyZS9ub2RlX21vZHVsZXMvQGY1ZGV2Y2VudHJhbC9mNS1jbG91ZC1saWJzL3NjcmlwdHMvZGVjcnlwdERhdGFGcm9tRmlsZS5qcyAtLWRhdGEtZmlsZSAvY29uZmlnL2Nsb3VkLy5wYXNzd2QgfCBhd2sgJ3twcmludCAkMX0nCn0KCndoaWxlIGdldG9wdHMgbzp1OiBvcHRpb24KZG8gY2FzZSAiJG9wdGlvbiIgIGluCiAgICAgICAgbykgZGVjbGFyYXRpb25Vcmw9JE9QVEFSRzs7CiAgICAgICAgdSkgdXNlcj0kT1BUQVJHOzsKICAgIGVzYWMKZG9uZQoKZGVwbG95ZWQ9Im5vIgpmaWxlX2xvYz0iL2NvbmZpZy9jbG91ZC9jdXN0b21fY29uZmlnIgpkZmxfbWdtdF9wb3J0PWB0bXNoIGxpc3Qgc3lzIGh0dHBkIHNzbC1wb3J0IHwgZ3JlcCBzc2wtcG9ydCB8IHNlZCAncy9zc2wtcG9ydCAvLztzLyAvL2cnYAp1cmxfcmVnZXg9IihodHRwOlwvXC98aHR0cHM6XC9cLyk/W2EtejAtOV0rKFtcLVwuXXsxfVthLXowLTldKykqXC5bYS16XXsyLDV9KDpbMC05XXsxLDV9KT8oXC8uKik/JCIKCmlmIFtbICRkZWNsYXJhdGlvblVybCA9fiAkdXJsX3JlZ2V4IF1dOyB0aGVuCiAgICByZXNwb25zZV9jb2RlPSQoL3Vzci9iaW4vY3VybCAtc2sgLXcgIiV7aHR0cF9jb2RlfSIgJGRlY2xhcmF0aW9uVXJsIC1vICRmaWxlX2xvYykKICAgIGlmIFtbICRyZXNwb25zZV9jb2RlID09IDIwMCBdXTsgdGhlbgogICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIGRvd25sb2FkIGNvbXBsZXRlOyBjaGVja2luZyBmb3IgdmFsaWQgSlNPTi4iCiAgICAgICAgIGNhdCAkZmlsZV9sb2MgfCBqcSAuY2xhc3MKICAgICAgICAgaWYgW1sgJD8gPT0gMCBdXTsgdGhlbgogICAgICAgICAgICAgcmVzcG9uc2VfY29kZT0kKC91c3IvYmluL2N1cmwgLXNrdnZ1ICR1c2VyOiQocGFzc3dkKSAtdyAiJXtodHRwX2NvZGV9IiAtWCBQT1NUIC1IICJDb250ZW50LVR5cGU6IGFwcGxpY2F0aW9uL2pzb24iIGh0dHBzOi8vbG9jYWxob3N0OiRkZmxfbWdtdF9wb3J0L21nbXQvc2hhcmVkL2FwcHN2Y3MvZGVjbGFyZSAtZCBAJGZpbGVfbG9jIC1vIC9kZXYvbnVsbCkKCiAgICAgICAgICAgICBpZiBbWyAkcmVzcG9uc2VfY29kZSA9PSAyMDAgfHwgJHJlc3BvbnNlX2NvZGUgPT0gNTAyIF1dOyB0aGVuCiAgICAgICAgICAgICAgICAgIGVjaG8gIkRlcGxveW1lbnQgb2YgYXBwbGljYXRpb24gc3VjY2VlZGVkLiIKICAgICAgICAgICAgICAgICAgZGVwbG95ZWQ9InllcyIKICAgICAgICAgICAgIGVsc2UKICAgICAgICAgICAgICAgICBlY2hvICJGYWlsZWQgdG8gZGVwbG95IGFwcGxpY2F0aW9uOyBjb250aW51aW5nIHdpdGggcmVzcG9uc2UgY29kZSAnIiRyZXNwb25zZV9jb2RlIiciCiAgICAgICAgICAgICBmaQogICAgICAgICBlbHNlCiAgICAgICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIHdhcyBub3QgdmFsaWQgSlNPTiwgY29udGludWluZyIKICAgICAgICAgZmkKICAgIGVsc2UKICAgICAgICBlY2hvICJGYWlsZWQgdG8gZG93bmxvYWQgY3VzdG9tIGNvbmZpZzsgY29udGludWluZyB3aXRoIHJlc3BvbnNlIGNvZGUgJyIkcmVzcG9uc2VfY29kZSInIgogICAgZmkKZWxzZQogICAgIGVjaG8gIkN1c3RvbSBjb25maWcgd2FzIG5vdCBhIFVSTCwgY29udGludWluZy4iCmZpCgppZiBbWyAkZGVwbG95ZWQgPT0gIm5vIiAmJiAkZGVjbGFyYXRpb25VcmwgPT0gIk5PVF9TUEVDSUZJRUQiIF1dOyB0aGVuCiAgICBlY2hvICJBcHBsaWNhdGlvbiBkZXBsb3ltZW50IGZhaWxlZCBvciBjdXN0b20gVVJMIHdhcyBub3Qgc3BlY2lmaWVkLiIKZmkKCmVjaG8gIkRlcGxveW1lbnQgY29tcGxldGUuIgpleGl0", "extSubnetPrivateAddressSuffixInt": "[int(variables('extSubnetPrivateAddressPrefixArray')[3])]", "extSubnetName": "[parameters('externalSubnetName')]", - "extSubnetPrivateAddress": "[parameters('externalIpAddressRangeStart')]", + "extSubnetPrivateAddress": "[parameters('externalIpSelfAddressRangeStart')]", "extSubnetPrivateAddressPrefix": "[concat(variables('extSubnetPrivateAddressPrefixArray')[0], '.', variables('extSubnetPrivateAddressPrefixArray')[1], '.', variables('extSubnetPrivateAddressPrefixArray')[2], '.')]", "extNsgID": "[resourceId('Microsoft.Network/networkSecurityGroups/',concat(variables('dnsLabel'),'-ext-nsg'))]", "extSelfPublicIpAddressNamePrefix": "[concat(variables('dnsLabel'), '-self-pip')]", @@ -595,7 +595,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -681,7 +681,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -801,6 +801,7 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, + "privateIPAllocationMethod": "Static", "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), variables('extSubnetPrivateAddressSuffix0'))]", "subnet": { "id": "[variables('extSubnetId')]" @@ -844,6 +845,7 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, + "privateIPAllocationMethod": "Static", "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), variables('extSubnetPrivateAddressSuffix1'))]", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/azuredeploy.parameters.json index 0d30dbfa59..766cc254c1 100644 --- a/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/3nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/3nic/existing-stack/byol/README.md b/supported/failover/same-net/via-lb/3nic/existing-stack/byol/README.md index 53b09344dd..bbd54af151 100644 --- a/supported/failover/same-net/via-lb/3nic/existing-stack/byol/README.md +++ b/supported/failover/same-net/via-lb/3nic/existing-stack/byol/README.md @@ -42,7 +42,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -63,6 +63,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -114,7 +115,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -171,47 +172,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --enableNetworkFailover Yes --internalLoadBalancerType Per-protocol --internalLoadBalancerProbePort 3456 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --licenseKey2 --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddressRangeStart --externalSubnetName --externalIpAddressRangeStart --externalIpSelfAddressRangeStart --internalSubnetName --internalIpAddressRangeStart --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. For diagrams of alternate deployment topologies, see [alternate topologies](../../alternate-deployment-topologies.md). diff --git a/supported/failover/same-net/via-lb/3nic/existing-stack/byol/azuredeploy.json b/supported/failover/same-net/via-lb/3nic/existing-stack/byol/azuredeploy.json index 9855704dbc..b4c330d7a0 100644 --- a/supported/failover/same-net/via-lb/3nic/existing-stack/byol/azuredeploy.json +++ b/supported/failover/same-net/via-lb/3nic/existing-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -420,7 +420,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -466,7 +466,7 @@ "appScript": "IyEvYmluL2Jhc2gKZnVuY3Rpb24gcGFzc3dkKCkgewogIGVjaG8gfCBmNS1yZXN0LW5vZGUgL2NvbmZpZy9jbG91ZC9henVyZS9ub2RlX21vZHVsZXMvQGY1ZGV2Y2VudHJhbC9mNS1jbG91ZC1saWJzL3NjcmlwdHMvZGVjcnlwdERhdGFGcm9tRmlsZS5qcyAtLWRhdGEtZmlsZSAvY29uZmlnL2Nsb3VkLy5wYXNzd2QgfCBhd2sgJ3twcmludCAkMX0nCn0KCndoaWxlIGdldG9wdHMgbzp1OiBvcHRpb24KZG8gY2FzZSAiJG9wdGlvbiIgIGluCiAgICAgICAgbykgZGVjbGFyYXRpb25Vcmw9JE9QVEFSRzs7CiAgICAgICAgdSkgdXNlcj0kT1BUQVJHOzsKICAgIGVzYWMKZG9uZQoKZGVwbG95ZWQ9Im5vIgpmaWxlX2xvYz0iL2NvbmZpZy9jbG91ZC9jdXN0b21fY29uZmlnIgpkZmxfbWdtdF9wb3J0PWB0bXNoIGxpc3Qgc3lzIGh0dHBkIHNzbC1wb3J0IHwgZ3JlcCBzc2wtcG9ydCB8IHNlZCAncy9zc2wtcG9ydCAvLztzLyAvL2cnYAp1cmxfcmVnZXg9IihodHRwOlwvXC98aHR0cHM6XC9cLyk/W2EtejAtOV0rKFtcLVwuXXsxfVthLXowLTldKykqXC5bYS16XXsyLDV9KDpbMC05XXsxLDV9KT8oXC8uKik/JCIKCmlmIFtbICRkZWNsYXJhdGlvblVybCA9fiAkdXJsX3JlZ2V4IF1dOyB0aGVuCiAgICByZXNwb25zZV9jb2RlPSQoL3Vzci9iaW4vY3VybCAtc2sgLXcgIiV7aHR0cF9jb2RlfSIgJGRlY2xhcmF0aW9uVXJsIC1vICRmaWxlX2xvYykKICAgIGlmIFtbICRyZXNwb25zZV9jb2RlID09IDIwMCBdXTsgdGhlbgogICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIGRvd25sb2FkIGNvbXBsZXRlOyBjaGVja2luZyBmb3IgdmFsaWQgSlNPTi4iCiAgICAgICAgIGNhdCAkZmlsZV9sb2MgfCBqcSAuY2xhc3MKICAgICAgICAgaWYgW1sgJD8gPT0gMCBdXTsgdGhlbgogICAgICAgICAgICAgcmVzcG9uc2VfY29kZT0kKC91c3IvYmluL2N1cmwgLXNrdnZ1ICR1c2VyOiQocGFzc3dkKSAtdyAiJXtodHRwX2NvZGV9IiAtWCBQT1NUIC1IICJDb250ZW50LVR5cGU6IGFwcGxpY2F0aW9uL2pzb24iIGh0dHBzOi8vbG9jYWxob3N0OiRkZmxfbWdtdF9wb3J0L21nbXQvc2hhcmVkL2FwcHN2Y3MvZGVjbGFyZSAtZCBAJGZpbGVfbG9jIC1vIC9kZXYvbnVsbCkKCiAgICAgICAgICAgICBpZiBbWyAkcmVzcG9uc2VfY29kZSA9PSAyMDAgfHwgJHJlc3BvbnNlX2NvZGUgPT0gNTAyIF1dOyB0aGVuCiAgICAgICAgICAgICAgICAgIGVjaG8gIkRlcGxveW1lbnQgb2YgYXBwbGljYXRpb24gc3VjY2VlZGVkLiIKICAgICAgICAgICAgICAgICAgZGVwbG95ZWQ9InllcyIKICAgICAgICAgICAgIGVsc2UKICAgICAgICAgICAgICAgICBlY2hvICJGYWlsZWQgdG8gZGVwbG95IGFwcGxpY2F0aW9uOyBjb250aW51aW5nIHdpdGggcmVzcG9uc2UgY29kZSAnIiRyZXNwb25zZV9jb2RlIiciCiAgICAgICAgICAgICBmaQogICAgICAgICBlbHNlCiAgICAgICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIHdhcyBub3QgdmFsaWQgSlNPTiwgY29udGludWluZyIKICAgICAgICAgZmkKICAgIGVsc2UKICAgICAgICBlY2hvICJGYWlsZWQgdG8gZG93bmxvYWQgY3VzdG9tIGNvbmZpZzsgY29udGludWluZyB3aXRoIHJlc3BvbnNlIGNvZGUgJyIkcmVzcG9uc2VfY29kZSInIgogICAgZmkKZWxzZQogICAgIGVjaG8gIkN1c3RvbSBjb25maWcgd2FzIG5vdCBhIFVSTCwgY29udGludWluZy4iCmZpCgppZiBbWyAkZGVwbG95ZWQgPT0gIm5vIiAmJiAkZGVjbGFyYXRpb25VcmwgPT0gIk5PVF9TUEVDSUZJRUQiIF1dOyB0aGVuCiAgICBlY2hvICJBcHBsaWNhdGlvbiBkZXBsb3ltZW50IGZhaWxlZCBvciBjdXN0b20gVVJMIHdhcyBub3Qgc3BlY2lmaWVkLiIKZmkKCmVjaG8gIkRlcGxveW1lbnQgY29tcGxldGUuIgpleGl0", "extSubnetPrivateAddressSuffixInt": "[int(variables('extSubnetPrivateAddressPrefixArray')[3])]", "extSubnetName": "[parameters('externalSubnetName')]", - "extSubnetPrivateAddress": "[parameters('externalIpAddressRangeStart')]", + "extSubnetPrivateAddress": "[parameters('externalIpSelfAddressRangeStart')]", "extSubnetPrivateAddressPrefix": "[concat(variables('extSubnetPrivateAddressPrefixArray')[0], '.', variables('extSubnetPrivateAddressPrefixArray')[1], '.', variables('extSubnetPrivateAddressPrefixArray')[2], '.')]", "extNsgID": "[resourceId('Microsoft.Network/networkSecurityGroups/',concat(variables('dnsLabel'),'-ext-nsg'))]", "extSelfPublicIpAddressNamePrefix": "[concat(variables('dnsLabel'), '-self-pip')]", @@ -571,7 +571,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-existing-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-existing-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -657,7 +657,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -777,6 +777,7 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, + "privateIPAllocationMethod": "Static", "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), variables('extSubnetPrivateAddressSuffix0'))]", "subnet": { "id": "[variables('extSubnetId')]" @@ -820,6 +821,7 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, + "privateIPAllocationMethod": "Static", "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), variables('extSubnetPrivateAddressSuffix1'))]", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/failover/same-net/via-lb/3nic/existing-stack/byol/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/3nic/existing-stack/byol/azuredeploy.parameters.json index cc9c71233a..edfde92211 100644 --- a/supported/failover/same-net/via-lb/3nic/existing-stack/byol/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/3nic/existing-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/3nic/existing-stack/payg/README.md b/supported/failover/same-net/via-lb/3nic/existing-stack/payg/README.md index 0fa4726876..316992b6cc 100644 --- a/supported/failover/same-net/via-lb/3nic/existing-stack/payg/README.md +++ b/supported/failover/same-net/via-lb/3nic/existing-stack/payg/README.md @@ -41,7 +41,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -61,6 +61,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. @@ -113,7 +114,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -168,48 +169,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --enableNetworkFailover Yes --internalLoadBalancerType Per-protocol --internalLoadBalancerProbePort 3456 --instanceType Standard_DS3_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddressRangeStart --externalSubnetName --externalIpAddressRangeStart --externalIpSelfAddressRangeStart --internalSubnetName --internalIpAddressRangeStart --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. For diagrams of alternate deployment topologies, see [alternate topologies](../../alternate-deployment-topologies.md). diff --git a/supported/failover/same-net/via-lb/3nic/existing-stack/payg/azuredeploy.json b/supported/failover/same-net/via-lb/3nic/existing-stack/payg/azuredeploy.json index 73d6cf9ae4..086171c26f 100644 --- a/supported/failover/same-net/via-lb/3nic/existing-stack/payg/azuredeploy.json +++ b/supported/failover/same-net/via-lb/3nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -416,7 +416,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -462,7 +462,7 @@ "appScript": "IyEvYmluL2Jhc2gKZnVuY3Rpb24gcGFzc3dkKCkgewogIGVjaG8gfCBmNS1yZXN0LW5vZGUgL2NvbmZpZy9jbG91ZC9henVyZS9ub2RlX21vZHVsZXMvQGY1ZGV2Y2VudHJhbC9mNS1jbG91ZC1saWJzL3NjcmlwdHMvZGVjcnlwdERhdGFGcm9tRmlsZS5qcyAtLWRhdGEtZmlsZSAvY29uZmlnL2Nsb3VkLy5wYXNzd2QgfCBhd2sgJ3twcmludCAkMX0nCn0KCndoaWxlIGdldG9wdHMgbzp1OiBvcHRpb24KZG8gY2FzZSAiJG9wdGlvbiIgIGluCiAgICAgICAgbykgZGVjbGFyYXRpb25Vcmw9JE9QVEFSRzs7CiAgICAgICAgdSkgdXNlcj0kT1BUQVJHOzsKICAgIGVzYWMKZG9uZQoKZGVwbG95ZWQ9Im5vIgpmaWxlX2xvYz0iL2NvbmZpZy9jbG91ZC9jdXN0b21fY29uZmlnIgpkZmxfbWdtdF9wb3J0PWB0bXNoIGxpc3Qgc3lzIGh0dHBkIHNzbC1wb3J0IHwgZ3JlcCBzc2wtcG9ydCB8IHNlZCAncy9zc2wtcG9ydCAvLztzLyAvL2cnYAp1cmxfcmVnZXg9IihodHRwOlwvXC98aHR0cHM6XC9cLyk/W2EtejAtOV0rKFtcLVwuXXsxfVthLXowLTldKykqXC5bYS16XXsyLDV9KDpbMC05XXsxLDV9KT8oXC8uKik/JCIKCmlmIFtbICRkZWNsYXJhdGlvblVybCA9fiAkdXJsX3JlZ2V4IF1dOyB0aGVuCiAgICByZXNwb25zZV9jb2RlPSQoL3Vzci9iaW4vY3VybCAtc2sgLXcgIiV7aHR0cF9jb2RlfSIgJGRlY2xhcmF0aW9uVXJsIC1vICRmaWxlX2xvYykKICAgIGlmIFtbICRyZXNwb25zZV9jb2RlID09IDIwMCBdXTsgdGhlbgogICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIGRvd25sb2FkIGNvbXBsZXRlOyBjaGVja2luZyBmb3IgdmFsaWQgSlNPTi4iCiAgICAgICAgIGNhdCAkZmlsZV9sb2MgfCBqcSAuY2xhc3MKICAgICAgICAgaWYgW1sgJD8gPT0gMCBdXTsgdGhlbgogICAgICAgICAgICAgcmVzcG9uc2VfY29kZT0kKC91c3IvYmluL2N1cmwgLXNrdnZ1ICR1c2VyOiQocGFzc3dkKSAtdyAiJXtodHRwX2NvZGV9IiAtWCBQT1NUIC1IICJDb250ZW50LVR5cGU6IGFwcGxpY2F0aW9uL2pzb24iIGh0dHBzOi8vbG9jYWxob3N0OiRkZmxfbWdtdF9wb3J0L21nbXQvc2hhcmVkL2FwcHN2Y3MvZGVjbGFyZSAtZCBAJGZpbGVfbG9jIC1vIC9kZXYvbnVsbCkKCiAgICAgICAgICAgICBpZiBbWyAkcmVzcG9uc2VfY29kZSA9PSAyMDAgfHwgJHJlc3BvbnNlX2NvZGUgPT0gNTAyIF1dOyB0aGVuCiAgICAgICAgICAgICAgICAgIGVjaG8gIkRlcGxveW1lbnQgb2YgYXBwbGljYXRpb24gc3VjY2VlZGVkLiIKICAgICAgICAgICAgICAgICAgZGVwbG95ZWQ9InllcyIKICAgICAgICAgICAgIGVsc2UKICAgICAgICAgICAgICAgICBlY2hvICJGYWlsZWQgdG8gZGVwbG95IGFwcGxpY2F0aW9uOyBjb250aW51aW5nIHdpdGggcmVzcG9uc2UgY29kZSAnIiRyZXNwb25zZV9jb2RlIiciCiAgICAgICAgICAgICBmaQogICAgICAgICBlbHNlCiAgICAgICAgICAgICBlY2hvICJDdXN0b20gY29uZmlnIHdhcyBub3QgdmFsaWQgSlNPTiwgY29udGludWluZyIKICAgICAgICAgZmkKICAgIGVsc2UKICAgICAgICBlY2hvICJGYWlsZWQgdG8gZG93bmxvYWQgY3VzdG9tIGNvbmZpZzsgY29udGludWluZyB3aXRoIHJlc3BvbnNlIGNvZGUgJyIkcmVzcG9uc2VfY29kZSInIgogICAgZmkKZWxzZQogICAgIGVjaG8gIkN1c3RvbSBjb25maWcgd2FzIG5vdCBhIFVSTCwgY29udGludWluZy4iCmZpCgppZiBbWyAkZGVwbG95ZWQgPT0gIm5vIiAmJiAkZGVjbGFyYXRpb25VcmwgPT0gIk5PVF9TUEVDSUZJRUQiIF1dOyB0aGVuCiAgICBlY2hvICJBcHBsaWNhdGlvbiBkZXBsb3ltZW50IGZhaWxlZCBvciBjdXN0b20gVVJMIHdhcyBub3Qgc3BlY2lmaWVkLiIKZmkKCmVjaG8gIkRlcGxveW1lbnQgY29tcGxldGUuIgpleGl0", "extSubnetPrivateAddressSuffixInt": "[int(variables('extSubnetPrivateAddressPrefixArray')[3])]", "extSubnetName": "[parameters('externalSubnetName')]", - "extSubnetPrivateAddress": "[parameters('externalIpAddressRangeStart')]", + "extSubnetPrivateAddress": "[parameters('externalIpSelfAddressRangeStart')]", "extSubnetPrivateAddressPrefix": "[concat(variables('extSubnetPrivateAddressPrefixArray')[0], '.', variables('extSubnetPrivateAddressPrefixArray')[1], '.', variables('extSubnetPrivateAddressPrefixArray')[2], '.')]", "extNsgID": "[resourceId('Microsoft.Network/networkSecurityGroups/',concat(variables('dnsLabel'),'-ext-nsg'))]", "extSelfPublicIpAddressNamePrefix": "[concat(variables('dnsLabel'), '-self-pip')]", @@ -604,7 +604,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -690,7 +690,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -810,6 +810,7 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, + "privateIPAllocationMethod": "Static", "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), variables('extSubnetPrivateAddressSuffix0'))]", "subnet": { "id": "[variables('extSubnetId')]" @@ -853,6 +854,7 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, + "privateIPAllocationMethod": "Static", "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), variables('extSubnetPrivateAddressSuffix1'))]", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/failover/same-net/via-lb/3nic/existing-stack/payg/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/3nic/existing-stack/payg/azuredeploy.parameters.json index f91e1c4058..e716c8e465 100644 --- a/supported/failover/same-net/via-lb/3nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/3nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/README.md b/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/README.md index c435507a8e..1605705d9f 100644 --- a/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/README.md +++ b/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/README.md @@ -42,7 +42,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -64,6 +64,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -115,7 +116,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -167,47 +168,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --enableNetworkFailover Yes --internalLoadBalancerType Per-protocol --internalLoadBalancerProbePort 3456 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/azuredeploy.json b/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/azuredeploy.json index 49f775113c..48d928ba7a 100644 --- a/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/azuredeploy.json +++ b/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -386,7 +386,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -521,7 +521,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -766,8 +766,8 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, - "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 10)]", "privateIPAllocationMethod": "Static", + "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 10)]", "subnet": { "id": "[variables('extSubnetId')]" } @@ -813,8 +813,8 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, - "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 11)]", "privateIPAllocationMethod": "Static", + "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 11)]", "subnet": { "id": "[variables('extSubnetId')]" } diff --git a/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/azuredeploy.parameters.json index 54c36c749e..1e8299da43 100644 --- a/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/3nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/3nic/new-stack/byol/README.md b/supported/failover/same-net/via-lb/3nic/new-stack/byol/README.md index ca71feb012..8030a1748f 100644 --- a/supported/failover/same-net/via-lb/3nic/new-stack/byol/README.md +++ b/supported/failover/same-net/via-lb/3nic/new-stack/byol/README.md @@ -42,7 +42,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -63,6 +63,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -114,7 +115,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -162,47 +163,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --enableNetworkFailover Yes --internalLoadBalancerType Per-protocol --internalLoadBalancerProbePort 3456 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --licenseKey2 --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. For diagrams of alternate deployment topologies, see [alternate topologies](../../alternate-deployment-topologies.md). diff --git a/supported/failover/same-net/via-lb/3nic/new-stack/byol/azuredeploy.json b/supported/failover/same-net/via-lb/3nic/new-stack/byol/azuredeploy.json index a25a0bc3af..0fa5c0ee39 100644 --- a/supported/failover/same-net/via-lb/3nic/new-stack/byol/azuredeploy.json +++ b/supported/failover/same-net/via-lb/3nic/new-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -362,7 +362,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -497,7 +497,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-new-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-new-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -742,8 +742,8 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, - "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 10)]", "privateIPAllocationMethod": "Static", + "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 10)]", "subnet": { "id": "[variables('extSubnetId')]" } @@ -789,8 +789,8 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, - "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 11)]", "privateIPAllocationMethod": "Static", + "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 11)]", "subnet": { "id": "[variables('extSubnetId')]" } diff --git a/supported/failover/same-net/via-lb/3nic/new-stack/byol/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/3nic/new-stack/byol/azuredeploy.parameters.json index f45a0d84ff..df2f96783b 100644 --- a/supported/failover/same-net/via-lb/3nic/new-stack/byol/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/3nic/new-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/failover/same-net/via-lb/3nic/new-stack/payg/README.md b/supported/failover/same-net/via-lb/3nic/new-stack/payg/README.md index 2f6e3dc7fc..a747f31e82 100644 --- a/supported/failover/same-net/via-lb/3nic/new-stack/payg/README.md +++ b/supported/failover/same-net/via-lb/3nic/new-stack/payg/README.md @@ -41,7 +41,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -61,6 +61,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -112,7 +113,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Ffailover%2Fsame-net%2Fvia-lb%2F3nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -158,48 +159,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --enableNetworkFailover Yes --internalLoadBalancerType Per-protocol --internalLoadBalancerProbePort 3456 --instanceType Standard_DS3_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - - ## Configuration Example The following is an example configuration diagram for this solution deployment. In this scenario, all access to the BIG-IP VE cluster (Active/Active) is through an ALB. For diagrams of alternate deployment topologies, see [alternate topologies](../../alternate-deployment-topologies.md). diff --git a/supported/failover/same-net/via-lb/3nic/new-stack/payg/azuredeploy.json b/supported/failover/same-net/via-lb/3nic/new-stack/payg/azuredeploy.json index 0efafbd31d..82c98f16da 100644 --- a/supported/failover/same-net/via-lb/3nic/new-stack/payg/azuredeploy.json +++ b/supported/failover/same-net/via-lb/3nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -358,7 +358,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -530,7 +530,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:failover_3nic-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -775,8 +775,8 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, - "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 10)]", "privateIPAllocationMethod": "Static", + "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 10)]", "subnet": { "id": "[variables('extSubnetId')]" } @@ -822,8 +822,8 @@ "properties": { "loadBalancerBackendAddressPools": "[if(equals(variables('numberOfExternalIps'), 0), take(variables('backEndAddressPoolArray'), 0), take(variables('backEndAddressPoolArray'), 1))]", "primary": false, - "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 11)]", "privateIPAllocationMethod": "Static", + "privateIPAddress": "[concat(variables('extSubnetPrivateAddressPrefix'), 11)]", "subnet": { "id": "[variables('extSubnetId')]" } diff --git a/supported/failover/same-net/via-lb/3nic/new-stack/payg/azuredeploy.parameters.json b/supported/failover/same-net/via-lb/3nic/new-stack/payg/azuredeploy.parameters.json index 9f43ceacf6..ddb0183a4b 100644 --- a/supported/failover/same-net/via-lb/3nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/failover/same-net/via-lb/3nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/1nic/existing-stack/bigiq/README.md b/supported/standalone/1nic/existing-stack/bigiq/README.md index 9cd40a13c3..a586794375 100644 --- a/supported/standalone/1nic/existing-stack/bigiq/README.md +++ b/supported/standalone/1nic/existing-stack/bigiq/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -99,7 +99,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F1nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters diff --git a/supported/standalone/1nic/existing-stack/bigiq/azuredeploy.json b/supported/standalone/1nic/existing-stack/bigiq/azuredeploy.json index 1386b79fd8..e8f0455fc4 100644 --- a/supported/standalone/1nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/standalone/1nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -384,7 +384,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -472,7 +472,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { diff --git a/supported/standalone/1nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/standalone/1nic/existing-stack/bigiq/azuredeploy.parameters.json index e99b72d6bd..9197a13010 100644 --- a/supported/standalone/1nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/standalone/1nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/1nic/existing-stack/byol/README.md b/supported/standalone/1nic/existing-stack/byol/README.md index bc8d59993a..38b32e5d78 100644 --- a/supported/standalone/1nic/existing-stack/byol/README.md +++ b/supported/standalone/1nic/existing-stack/byol/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -51,6 +51,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -102,7 +103,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F1nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F1nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -151,47 +152,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/1nic/existing-stack/byol/azuredeploy.json b/supported/standalone/1nic/existing-stack/byol/azuredeploy.json index 288fe466fd..c2401b597f 100644 --- a/supported/standalone/1nic/existing-stack/byol/azuredeploy.json +++ b/supported/standalone/1nic/existing-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -353,7 +353,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -441,7 +441,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-existing-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-existing-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { diff --git a/supported/standalone/1nic/existing-stack/byol/azuredeploy.parameters.json b/supported/standalone/1nic/existing-stack/byol/azuredeploy.parameters.json index d1be49aea3..dfa72a22a4 100644 --- a/supported/standalone/1nic/existing-stack/byol/azuredeploy.parameters.json +++ b/supported/standalone/1nic/existing-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/1nic/existing-stack/payg/README.md b/supported/standalone/1nic/existing-stack/payg/README.md index 9dced47118..2141de1fc9 100644 --- a/supported/standalone/1nic/existing-stack/payg/README.md +++ b/supported/standalone/1nic/existing-stack/payg/README.md @@ -31,7 +31,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -49,6 +49,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -100,7 +101,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F1nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -148,47 +149,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/1nic/existing-stack/payg/azuredeploy.json b/supported/standalone/1nic/existing-stack/payg/azuredeploy.json index 9432effaca..7611894e04 100644 --- a/supported/standalone/1nic/existing-stack/payg/azuredeploy.json +++ b/supported/standalone/1nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -358,7 +358,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -483,7 +483,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { diff --git a/supported/standalone/1nic/existing-stack/payg/azuredeploy.parameters.json b/supported/standalone/1nic/existing-stack/payg/azuredeploy.parameters.json index 3dd46ed7cb..a2a49e86a6 100644 --- a/supported/standalone/1nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/standalone/1nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/1nic/new-stack/bigiq/README.md b/supported/standalone/1nic/new-stack/bigiq/README.md index 58dd8e3334..dcf63800c5 100644 --- a/supported/standalone/1nic/new-stack/bigiq/README.md +++ b/supported/standalone/1nic/new-stack/bigiq/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -52,6 +52,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -103,7 +104,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F1nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -151,46 +152,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** ## Configuration Example diff --git a/supported/standalone/1nic/new-stack/bigiq/azuredeploy.json b/supported/standalone/1nic/new-stack/bigiq/azuredeploy.json index dfdef444bd..095b4abb1b 100644 --- a/supported/standalone/1nic/new-stack/bigiq/azuredeploy.json +++ b/supported/standalone/1nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -337,7 +337,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -425,7 +425,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { diff --git a/supported/standalone/1nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/standalone/1nic/new-stack/bigiq/azuredeploy.parameters.json index 4ec96f805e..b6b86d35b9 100644 --- a/supported/standalone/1nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/standalone/1nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/1nic/new-stack/byol/README.md b/supported/standalone/1nic/new-stack/byol/README.md index b9a1a941f1..5bb3a05074 100644 --- a/supported/standalone/1nic/new-stack/byol/README.md +++ b/supported/standalone/1nic/new-stack/byol/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -51,6 +51,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -102,7 +103,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F1nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F1nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -145,47 +146,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/1nic/new-stack/byol/azuredeploy.json b/supported/standalone/1nic/new-stack/byol/azuredeploy.json index fb4f26892c..a0ddf063b1 100644 --- a/supported/standalone/1nic/new-stack/byol/azuredeploy.json +++ b/supported/standalone/1nic/new-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -306,7 +306,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -394,7 +394,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-new-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-new-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { diff --git a/supported/standalone/1nic/new-stack/byol/azuredeploy.parameters.json b/supported/standalone/1nic/new-stack/byol/azuredeploy.parameters.json index 2b41cb8ee7..1dcddecb37 100644 --- a/supported/standalone/1nic/new-stack/byol/azuredeploy.parameters.json +++ b/supported/standalone/1nic/new-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/1nic/new-stack/payg/README.md b/supported/standalone/1nic/new-stack/payg/README.md index 6a3a89f20b..b4fa5e7591 100644 --- a/supported/standalone/1nic/new-stack/payg/README.md +++ b/supported/standalone/1nic/new-stack/payg/README.md @@ -31,7 +31,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -49,6 +49,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -100,7 +101,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F1nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -142,47 +143,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/1nic/new-stack/payg/azuredeploy.json b/supported/standalone/1nic/new-stack/payg/azuredeploy.json index 844cf630ee..56b7cf28b4 100644 --- a/supported/standalone/1nic/new-stack/payg/azuredeploy.json +++ b/supported/standalone/1nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -311,7 +311,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -436,7 +436,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_1nic-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { diff --git a/supported/standalone/1nic/new-stack/payg/azuredeploy.parameters.json b/supported/standalone/1nic/new-stack/payg/azuredeploy.parameters.json index 62922a5ca9..eae202e269 100644 --- a/supported/standalone/1nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/standalone/1nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/2nic/existing-stack/bigiq/README.md b/supported/standalone/2nic/existing-stack/bigiq/README.md index 00bf79e54c..d220e4c5ec 100644 --- a/supported/standalone/2nic/existing-stack/bigiq/README.md +++ b/supported/standalone/2nic/existing-stack/bigiq/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -53,6 +53,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -104,7 +105,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F2nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F2nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -161,47 +162,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --externalSubnetName --externalIpAddressRangeStart --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/2nic/existing-stack/bigiq/azuredeploy.json b/supported/standalone/2nic/existing-stack/bigiq/azuredeploy.json index 2476f584d0..351ba2b848 100644 --- a/supported/standalone/2nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/standalone/2nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -426,7 +426,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -530,7 +530,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -583,7 +583,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -651,7 +651,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/2nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/standalone/2nic/existing-stack/bigiq/azuredeploy.parameters.json index 26e6c1db77..7f4ad41a70 100644 --- a/supported/standalone/2nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/standalone/2nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/2nic/existing-stack/byol/README.md b/supported/standalone/2nic/existing-stack/byol/README.md index 328272cd26..a7d4be1464 100644 --- a/supported/standalone/2nic/existing-stack/byol/README.md +++ b/supported/standalone/2nic/existing-stack/byol/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -52,6 +52,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -103,7 +104,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F2nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F2nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -155,47 +156,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --externalSubnetName --externalIpAddressRangeStart --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/2nic/existing-stack/byol/azuredeploy.json b/supported/standalone/2nic/existing-stack/byol/azuredeploy.json index ac830cd5bc..74e07959e8 100644 --- a/supported/standalone/2nic/existing-stack/byol/azuredeploy.json +++ b/supported/standalone/2nic/existing-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -395,7 +395,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -499,7 +499,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-existing-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-existing-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -552,7 +552,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -620,7 +620,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/2nic/existing-stack/byol/azuredeploy.parameters.json b/supported/standalone/2nic/existing-stack/byol/azuredeploy.parameters.json index 492254ce9b..d663c6319b 100644 --- a/supported/standalone/2nic/existing-stack/byol/azuredeploy.parameters.json +++ b/supported/standalone/2nic/existing-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/2nic/existing-stack/payg/README.md b/supported/standalone/2nic/existing-stack/payg/README.md index a03ff68447..2fb73efb55 100644 --- a/supported/standalone/2nic/existing-stack/payg/README.md +++ b/supported/standalone/2nic/existing-stack/payg/README.md @@ -31,7 +31,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -50,6 +50,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -101,7 +102,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F2nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F2nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -152,47 +153,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --externalSubnetName --externalIpAddressRangeStart --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/2nic/existing-stack/payg/azuredeploy.json b/supported/standalone/2nic/existing-stack/payg/azuredeploy.json index aebcdc3136..535301de63 100644 --- a/supported/standalone/2nic/existing-stack/payg/azuredeploy.json +++ b/supported/standalone/2nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -400,7 +400,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -541,7 +541,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -594,7 +594,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -662,7 +662,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/2nic/existing-stack/payg/azuredeploy.parameters.json b/supported/standalone/2nic/existing-stack/payg/azuredeploy.parameters.json index 7782317651..6b5fa7567d 100644 --- a/supported/standalone/2nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/standalone/2nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/2nic/new-stack/bigiq/README.md b/supported/standalone/2nic/new-stack/bigiq/README.md index 147070d575..aafb97a491 100644 --- a/supported/standalone/2nic/new-stack/bigiq/README.md +++ b/supported/standalone/2nic/new-stack/bigiq/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -53,6 +53,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -104,7 +105,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F2nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F2nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -153,47 +154,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/2nic/new-stack/bigiq/azuredeploy.json b/supported/standalone/2nic/new-stack/bigiq/azuredeploy.json index c3df213ed5..d3c9d24d00 100644 --- a/supported/standalone/2nic/new-stack/bigiq/azuredeploy.json +++ b/supported/standalone/2nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -367,7 +367,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -469,7 +469,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -622,7 +622,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/2nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/standalone/2nic/new-stack/bigiq/azuredeploy.parameters.json index 83716a1524..23dd803028 100644 --- a/supported/standalone/2nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/standalone/2nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/2nic/new-stack/byol/README.md b/supported/standalone/2nic/new-stack/byol/README.md index 55ae7d5a48..e0fbc7a98f 100644 --- a/supported/standalone/2nic/new-stack/byol/README.md +++ b/supported/standalone/2nic/new-stack/byol/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -52,6 +52,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -103,7 +104,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F2nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F2nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -147,47 +148,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS2_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/2nic/new-stack/byol/azuredeploy.json b/supported/standalone/2nic/new-stack/byol/azuredeploy.json index ea3e82b654..7ead2420e0 100644 --- a/supported/standalone/2nic/new-stack/byol/azuredeploy.json +++ b/supported/standalone/2nic/new-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -336,7 +336,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -438,7 +438,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-new-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-new-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -591,7 +591,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/2nic/new-stack/byol/azuredeploy.parameters.json b/supported/standalone/2nic/new-stack/byol/azuredeploy.parameters.json index b50c91a10a..dad3d79ddf 100644 --- a/supported/standalone/2nic/new-stack/byol/azuredeploy.parameters.json +++ b/supported/standalone/2nic/new-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/2nic/new-stack/payg/README.md b/supported/standalone/2nic/new-stack/payg/README.md index 321d18c729..396b74c1c7 100644 --- a/supported/standalone/2nic/new-stack/payg/README.md +++ b/supported/standalone/2nic/new-stack/payg/README.md @@ -31,7 +31,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -50,6 +50,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -101,7 +102,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F2nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F2nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -144,47 +145,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS2_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/2nic/new-stack/payg/azuredeploy.json b/supported/standalone/2nic/new-stack/payg/azuredeploy.json index fd543bde85..6daa453917 100644 --- a/supported/standalone/2nic/new-stack/payg/azuredeploy.json +++ b/supported/standalone/2nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -341,7 +341,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -480,7 +480,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_2nic-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -633,7 +633,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/2nic/new-stack/payg/azuredeploy.parameters.json b/supported/standalone/2nic/new-stack/payg/azuredeploy.parameters.json index 7b53b5c41a..05ce2f1cfd 100644 --- a/supported/standalone/2nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/standalone/2nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/3nic/existing-stack/bigiq/README.md b/supported/standalone/3nic/existing-stack/bigiq/README.md index 3b81cf0488..d033cc2f56 100644 --- a/supported/standalone/3nic/existing-stack/bigiq/README.md +++ b/supported/standalone/3nic/existing-stack/bigiq/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -53,6 +53,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -104,7 +105,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F3nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F3nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -163,47 +164,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --externalSubnetName --externalIpAddressRangeStart --internalSubnetName --internalIpAddress --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/3nic/existing-stack/bigiq/azuredeploy.json b/supported/standalone/3nic/existing-stack/bigiq/azuredeploy.json index 94658fd69c..f021b725e4 100644 --- a/supported/standalone/3nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/standalone/3nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -429,7 +429,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -538,7 +538,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -591,7 +591,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -659,7 +659,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/3nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/standalone/3nic/existing-stack/bigiq/azuredeploy.parameters.json index 01d8e05017..3f379eec0c 100644 --- a/supported/standalone/3nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/standalone/3nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/3nic/existing-stack/byol/README.md b/supported/standalone/3nic/existing-stack/byol/README.md index 40de709e8b..8053ad711c 100644 --- a/supported/standalone/3nic/existing-stack/byol/README.md +++ b/supported/standalone/3nic/existing-stack/byol/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -52,6 +52,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -103,7 +104,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F3nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F3nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -157,47 +158,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --externalSubnetName --externalIpAddressRangeStart --internalSubnetName --internalIpAddress --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/3nic/existing-stack/byol/azuredeploy.json b/supported/standalone/3nic/existing-stack/byol/azuredeploy.json index 364ad41f9d..1fce1b315d 100644 --- a/supported/standalone/3nic/existing-stack/byol/azuredeploy.json +++ b/supported/standalone/3nic/existing-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -398,7 +398,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -507,7 +507,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-existing-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-existing-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -560,7 +560,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -628,7 +628,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/3nic/existing-stack/byol/azuredeploy.parameters.json b/supported/standalone/3nic/existing-stack/byol/azuredeploy.parameters.json index 54714bfec2..c629644a68 100644 --- a/supported/standalone/3nic/existing-stack/byol/azuredeploy.parameters.json +++ b/supported/standalone/3nic/existing-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/3nic/existing-stack/payg/README.md b/supported/standalone/3nic/existing-stack/payg/README.md index 4a6d085f3d..c293ff7f7a 100644 --- a/supported/standalone/3nic/existing-stack/payg/README.md +++ b/supported/standalone/3nic/existing-stack/payg/README.md @@ -31,7 +31,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -50,6 +50,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -101,7 +102,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F3nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F3nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -154,47 +155,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --externalSubnetName --externalIpAddressRangeStart --internalSubnetName --internalIpAddress --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/3nic/existing-stack/payg/azuredeploy.json b/supported/standalone/3nic/existing-stack/payg/azuredeploy.json index f506b3f721..3b71b49cfe 100644 --- a/supported/standalone/3nic/existing-stack/payg/azuredeploy.json +++ b/supported/standalone/3nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -403,7 +403,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -549,7 +549,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -602,7 +602,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -670,7 +670,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/3nic/existing-stack/payg/azuredeploy.parameters.json b/supported/standalone/3nic/existing-stack/payg/azuredeploy.parameters.json index 02fb84ffac..59beaa153f 100644 --- a/supported/standalone/3nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/standalone/3nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/3nic/new-stack/bigiq/README.md b/supported/standalone/3nic/new-stack/bigiq/README.md index 073015a2f3..2cf0f17a6d 100644 --- a/supported/standalone/3nic/new-stack/bigiq/README.md +++ b/supported/standalone/3nic/new-stack/bigiq/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -53,6 +53,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -104,7 +105,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F3nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F3nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -153,47 +154,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/3nic/new-stack/bigiq/azuredeploy.json b/supported/standalone/3nic/new-stack/bigiq/azuredeploy.json index 6f51324865..35b497c3ea 100644 --- a/supported/standalone/3nic/new-stack/bigiq/azuredeploy.json +++ b/supported/standalone/3nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -358,7 +358,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -465,7 +465,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -624,7 +624,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/3nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/standalone/3nic/new-stack/bigiq/azuredeploy.parameters.json index 405c4dd755..201b7cf0db 100644 --- a/supported/standalone/3nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/standalone/3nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/3nic/new-stack/byol/README.md b/supported/standalone/3nic/new-stack/byol/README.md index 91da262e90..129becf376 100644 --- a/supported/standalone/3nic/new-stack/byol/README.md +++ b/supported/standalone/3nic/new-stack/byol/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -52,6 +52,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -103,7 +104,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F3nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F3nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -147,47 +148,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/3nic/new-stack/byol/azuredeploy.json b/supported/standalone/3nic/new-stack/byol/azuredeploy.json index e9cdc92463..6f1021beb5 100644 --- a/supported/standalone/3nic/new-stack/byol/azuredeploy.json +++ b/supported/standalone/3nic/new-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -327,7 +327,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -434,7 +434,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-new-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-new-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -593,7 +593,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/3nic/new-stack/byol/azuredeploy.parameters.json b/supported/standalone/3nic/new-stack/byol/azuredeploy.parameters.json index 3bcd26e076..e016fe536c 100644 --- a/supported/standalone/3nic/new-stack/byol/azuredeploy.parameters.json +++ b/supported/standalone/3nic/new-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/3nic/new-stack/payg/README.md b/supported/standalone/3nic/new-stack/payg/README.md index eeb15a5eaa..e3da0df71d 100644 --- a/supported/standalone/3nic/new-stack/payg/README.md +++ b/supported/standalone/3nic/new-stack/payg/README.md @@ -31,7 +31,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -50,6 +50,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -101,7 +102,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2F3nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2F3nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -144,47 +145,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/3nic/new-stack/payg/azuredeploy.json b/supported/standalone/3nic/new-stack/payg/azuredeploy.json index 1a0d6ed22c..c1a08753c9 100644 --- a/supported/standalone/3nic/new-stack/payg/azuredeploy.json +++ b/supported/standalone/3nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -332,7 +332,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -476,7 +476,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_3nic-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -635,7 +635,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/3nic/new-stack/payg/azuredeploy.parameters.json b/supported/standalone/3nic/new-stack/payg/azuredeploy.parameters.json index cd315721fd..ce9352e87b 100644 --- a/supported/standalone/3nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/standalone/3nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/n-nic/existing-stack/bigiq/README.md b/supported/standalone/n-nic/existing-stack/bigiq/README.md index 4f8594648b..f2ca224279 100644 --- a/supported/standalone/n-nic/existing-stack/bigiq/README.md +++ b/supported/standalone/n-nic/existing-stack/bigiq/README.md @@ -33,7 +33,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -55,6 +55,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -106,7 +107,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2Fn-nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2Fn-nic%2Fexisting-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -167,47 +168,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --externalSubnetName --externalIpAddressRangeStart --internalSubnetName --internalIpAddress --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfAdditionalNics 1 --additionalNicLocation --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/n-nic/existing-stack/bigiq/azuredeploy.json b/supported/standalone/n-nic/existing-stack/bigiq/azuredeploy.json index d302f670b2..8194ee0f1c 100644 --- a/supported/standalone/n-nic/existing-stack/bigiq/azuredeploy.json +++ b/supported/standalone/n-nic/existing-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -497,7 +497,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -606,7 +606,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-existing-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-existing-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -659,7 +659,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -727,7 +727,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/n-nic/existing-stack/bigiq/azuredeploy.parameters.json b/supported/standalone/n-nic/existing-stack/bigiq/azuredeploy.parameters.json index c14e451e9d..3cd05bd989 100644 --- a/supported/standalone/n-nic/existing-stack/bigiq/azuredeploy.parameters.json +++ b/supported/standalone/n-nic/existing-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/n-nic/existing-stack/byol/README.md b/supported/standalone/n-nic/existing-stack/byol/README.md index 13bdeb5fd0..cb7a7cfddb 100644 --- a/supported/standalone/n-nic/existing-stack/byol/README.md +++ b/supported/standalone/n-nic/existing-stack/byol/README.md @@ -33,7 +33,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -54,6 +54,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -105,7 +106,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2Fn-nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2Fn-nic%2Fexisting-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -161,47 +162,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --externalSubnetName --externalIpAddressRangeStart --internalSubnetName --internalIpAddress --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfAdditionalNics 1 --additionalNicLocation --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/n-nic/existing-stack/byol/azuredeploy.json b/supported/standalone/n-nic/existing-stack/byol/azuredeploy.json index f9537587ca..2d5aa5b9e5 100644 --- a/supported/standalone/n-nic/existing-stack/byol/azuredeploy.json +++ b/supported/standalone/n-nic/existing-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -466,7 +466,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -575,7 +575,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-existing-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-existing-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -628,7 +628,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -696,7 +696,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/n-nic/existing-stack/byol/azuredeploy.parameters.json b/supported/standalone/n-nic/existing-stack/byol/azuredeploy.parameters.json index f4d9daad91..197fbf329f 100644 --- a/supported/standalone/n-nic/existing-stack/byol/azuredeploy.parameters.json +++ b/supported/standalone/n-nic/existing-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/n-nic/existing-stack/payg/README.md b/supported/standalone/n-nic/existing-stack/payg/README.md index 3869e35898..acd42432c6 100644 --- a/supported/standalone/n-nic/existing-stack/payg/README.md +++ b/supported/standalone/n-nic/existing-stack/payg/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -52,6 +52,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -103,7 +104,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2Fn-nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2Fn-nic%2Fexisting-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -158,47 +159,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetName --vnetResourceGroupName --mgmtSubnetName --mgmtIpAddress --externalSubnetName --externalIpAddressRangeStart --internalSubnetName --internalIpAddress --avSetChoice CREATE_NEW --zoneChoice 1 --provisionPublicIP Yes --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfAdditionalNics 1 --additionalNicLocation --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/n-nic/existing-stack/payg/azuredeploy.json b/supported/standalone/n-nic/existing-stack/payg/azuredeploy.json index af0ef51c2d..a8883c3032 100644 --- a/supported/standalone/n-nic/existing-stack/payg/azuredeploy.json +++ b/supported/standalone/n-nic/existing-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -471,7 +471,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -617,7 +617,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-existing-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-existing-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -670,7 +670,7 @@ "type": "Microsoft.Network/publicIPAddresses" }, { - "condition": "[not(equals(variables('numberOfExternalIps'),0))]", + "condition": "[and(equals(parameters('provisionPublicIP'),'Yes'), not(equals(variables('numberOfExternalIps'),0)))]", "apiVersion": "[variables('networkApiVersion')]", "sku": { "name": "Standard" @@ -738,7 +738,7 @@ "properties": { "PublicIpAddress": "[if(equals(parameters('provisionPublicIP'),'No'), json('null'), json(concat('{\"Id\": \"', if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2))), '\"}')))]", "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), add(variables('extSubnetPrivateAddressSuffixInt'), sub(copyIndex('ipConfigurations', 1), 1))))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/n-nic/existing-stack/payg/azuredeploy.parameters.json b/supported/standalone/n-nic/existing-stack/payg/azuredeploy.parameters.json index 134ee64fb1..751598a8ff 100644 --- a/supported/standalone/n-nic/existing-stack/payg/azuredeploy.parameters.json +++ b/supported/standalone/n-nic/existing-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/n-nic/new-stack/bigiq/README.md b/supported/standalone/n-nic/new-stack/bigiq/README.md index 5ee2d482cd..15768c8339 100644 --- a/supported/standalone/n-nic/new-stack/bigiq/README.md +++ b/supported/standalone/n-nic/new-stack/bigiq/README.md @@ -33,7 +33,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -55,6 +55,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -106,7 +107,7 @@ Use the appropriate button below to deploy: - **BIGIQ**: This allows you to launch the template using an existing BIG-IQ device with a pool of licenses to license the BIG-IP VE(s). - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2Fn-nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2Fn-nic%2Fnew-stack%2Fbigiq%2Fazuredeploy.json) ### Template parameters @@ -157,47 +158,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIqAddress --bigIqUsername --bigIqPassword --bigIqLicensePoolName --bigIqLicenseSkuKeyword1 OPTIONAL --bigIqLicenseUnitOfMeasure OPTIONAL --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfAdditionalNics 1 --additionalNicLocation --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/n-nic/new-stack/bigiq/azuredeploy.json b/supported/standalone/n-nic/new-stack/bigiq/azuredeploy.json index 9601097c44..a83eeaa60e 100644 --- a/supported/standalone/n-nic/new-stack/bigiq/azuredeploy.json +++ b/supported/standalone/n-nic/new-stack/bigiq/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -426,7 +426,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -585,7 +585,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-new-stack-supported-bigiq,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-new-stack-supported-bigiq,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:bigiq,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -725,7 +725,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/n-nic/new-stack/bigiq/azuredeploy.parameters.json b/supported/standalone/n-nic/new-stack/bigiq/azuredeploy.parameters.json index cf75715c69..7e0d3ca0a7 100644 --- a/supported/standalone/n-nic/new-stack/bigiq/azuredeploy.parameters.json +++ b/supported/standalone/n-nic/new-stack/bigiq/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/n-nic/new-stack/byol/README.md b/supported/standalone/n-nic/new-stack/byol/README.md index 3ab7ba9bfe..be1f753da4 100644 --- a/supported/standalone/n-nic/new-stack/byol/README.md +++ b/supported/standalone/n-nic/new-stack/byol/README.md @@ -33,7 +33,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -54,6 +54,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -105,7 +106,7 @@ Use the appropriate button below to deploy: - **BYOL** (bring your own license): This allows you to use an existing BIG-IP license. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2Fn-nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2Fn-nic%2Fnew-stack%2Fbyol%2Fazuredeploy.json) ### Template parameters @@ -151,47 +152,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName AllTwoBootLocations --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --licenseKey1 --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfAdditionalNics 1 --additionalNicLocation --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/n-nic/new-stack/byol/azuredeploy.json b/supported/standalone/n-nic/new-stack/byol/azuredeploy.json index 1a70e209e1..0f0e6890e9 100644 --- a/supported/standalone/n-nic/new-stack/byol/azuredeploy.json +++ b/supported/standalone/n-nic/new-stack/byol/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -395,7 +395,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -554,7 +554,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-new-stack-supported-byol,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-new-stack-supported-byol,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:byol,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -694,7 +694,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/n-nic/new-stack/byol/azuredeploy.parameters.json b/supported/standalone/n-nic/new-stack/byol/azuredeploy.parameters.json index 0a7f72c377..3ced7bddaf 100644 --- a/supported/standalone/n-nic/new-stack/byol/azuredeploy.parameters.json +++ b/supported/standalone/n-nic/new-stack/byol/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/supported/standalone/n-nic/new-stack/payg/README.md b/supported/standalone/n-nic/new-stack/payg/README.md index cb9bf3df51..66f6f6b57b 100644 --- a/supported/standalone/n-nic/new-stack/payg/README.md +++ b/supported/standalone/n-nic/new-stack/payg/README.md @@ -32,7 +32,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr ## Important configuration notes -> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v6.0.4.0** or earlier. +> **_CRITICAL:_** As of Release 6.1.0.0, BIG-IP version 12.1 is no longer supported. If you require BIG-IP version 12.1, you can use a previously released ARM template. To find a previously released template, from the **Branch** drop-down, click the **Tags** tab, and then select a tag of **v7.0.0.0** or earlier. - All F5 ARM templates include Application Services 3 Extension (AS3) v3.5.1 (LTS version) on the BIG-IP VE. As of release 4.1.2, all supported templates give the option of including the URL of an AS3 declaration, which you can use to specify the BIG-IP configuration you want on your newly created BIG-IP VE(s). In templates such as autoscale, where an F5-recommended configuration is deployed by default, specifying an AS3 declaration URL will override the default configuration with your declaration. See the [AS3 documentation](https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/3.5.1/) for details on how to use AS3. - There are new options for BIG-IP license bundles, including Per App VE LTM, Advanced WAF, and Per App VE Advanced WAF. See the [the version matrix](https://github.com/F5Networks/f5-azure-arm-templates/blob/master/azure-bigip-version-matrix.md) for details and applicable templates. @@ -52,6 +52,7 @@ For information on getting started using F5's ARM templates on GitHub, see [Micr - Previous tagged releases can be used to reference functionality that has been changed or removed. - If you are using a failover via-API template and performing an in-place upgrade of BIG-IP v13.1.1 or later, you must follow the instructions in [Post-Deployment Configuration Steps](#post-deployment-configuration-steps) - All templates now deploy Standard SKU Azure Public IP Addresses. +- If you choose "No" in response to the provisionPublicIP parameter, the choice for "numberOfExternalIps" is not honored and no public IP addresses are created. - All templates deploy Azure Virtual Machines and Virtual Machine Scale Sets into Availability Zones in supported regions; Availability Sets are still created in unsupported regions. Virtual Machine Scale Sets are distributed across zones 1, 2, and 3; failover Virtual Machines across zones 1 and 2. Standalone Virtual Machines are placed in zone 1 by default; however, you may select zone 1, 2, or 3 using the new zoneChoice parameter. ## Security @@ -103,7 +104,7 @@ Use the appropriate button below to deploy: - **PAYG**: This allows you to use pay-as-you-go hourly billing. - [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.0%2Fsupported%2Fstandalone%2Fn-nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) + [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FF5Networks%2Ff5-azure-arm-templates%2Fv7.0.0.1%2Fsupported%2Fstandalone%2Fn-nic%2Fnew-stack%2Fpayg%2Fazuredeploy.json) ### Template parameters @@ -148,47 +149,6 @@ As an alternative to deploying through the Azure Portal (GUI) each solution prov ## Example Command: ./deploy_via_bash.sh --adminUsername azureuser --authenticationType password --adminPasswordOrKey --dnsLabel --instanceName f5vm01 --numberOfExternalIps 1 --instanceType Standard_DS3_v2 --imageName Best1Gbps --bigIpVersion 14.1.003000 --bigIpModules ltm:nominal --vnetAddressPrefix 10.0 --declarationUrl NOT_SPECIFIED --ntpServer 0.pool.ntp.org --timeZone UTC --customImage OPTIONAL --allowUsageAnalytics Yes --numberOfAdditionalNics 1 --additionalNicLocation --resourceGroupName --azureLoginUser --azureLoginPassword ``` -## Post-Deployment Configuration Steps - -When performing an in-place upgrade of BIG-IP software v13.1.1 or later, you must complete the following steps to ensure that all the components required for failover are copied to the volume where the new version of BIG-IP is installed. To ensure traffic processing is not interrupted, F5 highly recommends upgrading the standby device, verifying failover functionality, and then upgrading the previously active device. - -From the volume to be upgraded on the standby device, you must edit **cs.dat** to allow inclusion of all files in **/config/cloud** in UCS backup. - -1. Remount the /usr directory as writable: - ``mount -o remount,rw /usr`` - -2. Back up the cs.dat file: - ``cp /usr/libdata/configsync/cs.dat /usr/libdata/configsync/cs.dat.bak`` - -3. Edit the cs.dat file: -``vi /usr/libdata/configsync/cs.dat`` - -4. In cs.dat, find the entry similar to the one below (the number between save and ignore may differ): -**save.10100.ignore = (/config/cloud/*)** - -5. Change **ignore** to **file** in the save key, and remove the parentheses from the value: -``save.10100.file = /config/cloud/*`` - -6. Save the cs.dat file and exit the editor. - -7. Remount the **/usr** directory as read-only: -``mount -o remount,ro /usr`` - -8. Create a [UCS archive](https://support.f5.com/csp/article/K13132) in the BIG-IP UI (accept defaults): -**System > Archives > Create > myUCS** - -9. Download myUCS.ucs locally. - -10. Install new ISO and reboot into upgraded volume. - -11. Boot into the newly upgraded volume. - -12. After verifying failover functionality, repeat steps 1-11 on the now-standby BIG-IP device. - -13. Following the upgrade, all the necessary files should be present and failover should work normally. To manually restore the UCS archive you created previously, use the following steps: - - From the upgraded volume, upload UCS file: **System > Archives > Upload > myUCS.uss** - - Restore the previously created UCS archive: **System > Archives > myUCS.ucs > Restore** - ## Configuration Example diff --git a/supported/standalone/n-nic/new-stack/payg/azuredeploy.json b/supported/standalone/n-nic/new-stack/payg/azuredeploy.json index 55b6dbefc7..f192e58e0e 100644 --- a/supported/standalone/n-nic/new-stack/payg/azuredeploy.json +++ b/supported/standalone/n-nic/new-stack/payg/azuredeploy.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "defaultValue": "azureuser", @@ -400,7 +400,7 @@ "singleQuote": "'", "f5CloudLibsTag": "v4.9.1", "f5CloudLibsAzureTag": "v2.9.1", - "f5NetworksTag": "v7.0.0.0", + "f5NetworksTag": "v7.0.0.1", "f5CloudIappsLoggerTag": "v1.0.0", "f5CloudIappsSdTag": "v2.3.2", "f5AS3Build": "f5-appsvcs-3.5.1-5.noarch.rpm", @@ -596,7 +596,7 @@ }, "Yes": { "hashCmd": "[concat('custId=`echo \"', variables('subscriptionId'), '\"|sha512sum|cut -d \" \" -f 1`; deployId=`echo \"', variables('deploymentId'), '\"|sha512sum|cut -d \" \" -f 1`')]", - "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-new-stack-supported-payg,templateVersion:7.0.0.0,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" + "metricsCmd": "[concat(' --metrics customerId:${custId},deploymentId:${deployId},templateName:standalone_nnic-new-stack-supported-payg,templateVersion:7.0.0.1,region:', variables('location'), ',bigIpVersion:', parameters('bigIpVersion') ,',licenseType:payg,cloudLibsVersion:', variables('f5CloudLibsTag'), ',cloudName:azure')]" } }, "osProfiles": { @@ -736,7 +736,7 @@ "Id": "[if(equals(copyIndex('ipConfigurations', 1), 1), concat(variables('extSelfPublicIpAddressIdPrefix'), '0'), concat(variables('extPublicIPAddressIdPrefix'), sub(copyIndex('ipConfigurations', 1), 2)))]" }, "primary": "[if(equals(copyIndex('ipConfigurations', 1), 1), 'True', 'False')]", - "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), parameters('externalIpSelfAddressRangeStart'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", + "privateIPAddress": "[if(equals(copyIndex('ipConfigurations', 1), 1), variables('extSubnetPrivateAddress'), concat(variables('extSubnetPrivateAddressPrefix'), 1, sub(copyIndex('ipConfigurations', 1), 2)))]", "privateIPAllocationMethod": "Static", "subnet": { "id": "[variables('extSubnetId')]" diff --git a/supported/standalone/n-nic/new-stack/payg/azuredeploy.parameters.json b/supported/standalone/n-nic/new-stack/payg/azuredeploy.parameters.json index 6562f9acb1..08df1bf9a7 100644 --- a/supported/standalone/n-nic/new-stack/payg/azuredeploy.parameters.json +++ b/supported/standalone/n-nic/new-stack/payg/azuredeploy.parameters.json @@ -1,6 +1,6 @@ { "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#", - "contentVersion": "7.0.0.0", + "contentVersion": "7.0.0.1", "parameters": { "adminUsername": { "value": "azureuser" diff --git a/template-index.md b/template-index.md index f18d9012ee..4e3ee0addb 100644 --- a/template-index.md +++ b/template-index.md @@ -2,120 +2,120 @@ The following is a list of the current **supported** F5 ARM templates. See the **experimental** directory for experimental templates. Click the links to view the README files which include the Launch buttons and additional information, or click the **Deploy to Azure** buttons to immediately launch the template. Because individual templates may have specific prerequisites, we strongly recommend you view the README file before attempting to launch a template. - **Deploying the BIG-IP VE in Azure - Single NIC** - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/standalone/1nic/new-stack) - - *BYOL*

- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/standalone/1nic/new-stack) + - *BYOL*

+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/standalone/1nic/existing-stack) - - *BYOL*

- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/standalone/1nic/existing-stack) + - *BYOL*

+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- **Deploying the BIG-IP VE in Azure - 2 NICs** - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/standalone/2nic/new-stack) - - *BYOL*

- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/standalone/2nic/new-stack) + - *BYOL*

+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/standalone/2nic/existing-stack) - - *BYOL*

- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/standalone/2nic/existing-stack) + - *BYOL*

+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- **Deploying the BIG-IP VE in Azure - 3 NICs** - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/standalone/3nic/new-stack) - - *BYOL*

- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/standalone/3nic/new-stack) + - *BYOL*

+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/standalone/3nic/existing-stack) - - *BYOL*

- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/standalone/3nic/existing-stack) + - *BYOL*

+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- **Deploying the BIG-IP VE in Azure - N NICs** - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/standalone/n-nic/new-stack) - - *BYOL*

- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/standalone/n-nic/new-stack) + - *BYOL*

+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/standalone/n-nic/existing-stack) - - *BYOL*

- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/standalone/n-nic/existing-stack) + - *BYOL*

+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- **Deploying the BIG-IP VE in Azure - HA Cluster: Active/Active** - *Single NIC* - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/failover/same-net/via-lb/1nic/new-stack) - - *BYOL*
- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/failover/same-net/via-lb/1nic/new-stack) + - *BYOL*
+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/failover/same-net/via-lb/1nic/existing-stack) - - *BYOL*
- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/failover/same-net/via-lb/1nic/existing-stack) + - *BYOL*
+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- *3 NICs* - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/failover/same-net/via-lb/3nic/new-stack) - - *BYOL*
- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/failover/same-net/via-lb/3nic/new-stack) + - *BYOL*
+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/failover/same-net/via-lb/3nic/existing-stack) - - *BYOL*
- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/failover/same-net/via-lb/3nic/existing-stack) + - *BYOL*
+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- **Deploying the BIG-IP VE in Azure - HA Cluster: Active/Standby** - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/failover/same-net/via-api/n-nic/new-stack) - - *BYOL*

- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/failover/same-net/via-api/n-nic/new-stack) + - *BYOL*

+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/failover/same-net/via-api/n-nic/existing-stack) - - *BYOL*

- - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/failover/same-net/via-api/n-nic/existing-stack) + - *BYOL*

+ - *PAYG*
+ - *Using BIG-IQ for Licensing*
- **Deploying the BIG-IP VE in Azure - AutoScale BIG-IP LTM - VM Scale Set** - *Frontend via ALB* - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/autoscale/ltm/via-lb/1nic/new-stack) - - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/autoscale/ltm/via-lb/1nic/new-stack) + - *PAYG*
+ - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/autoscale/ltm/via-lb/1nic/existing-stack) - - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/autoscale/ltm/via-lb/1nic/existing-stack) + - *PAYG*
+ - *Using BIG-IQ for Licensing*
- *Frontend via DNS* - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/autoscale/ltm/via-dns/1nic/new-stack) - - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/autoscale/ltm/via-dns/1nic/new-stack) + - *PAYG*
+ - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/autoscale/ltm/via-dns/1nic/existing-stack) - - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/autoscale/ltm/via-dns/1nic/existing-stack) + - *PAYG*
+ - *Using BIG-IQ for Licensing*
- **Deploying the BIG-IP VE in Azure - Auto Scale BIG-IP WAF (LTM + ASM) - VM Scale Set** - *Frontend via ALB* - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/autoscale/waf/via-lb/1nic/new-stack) - - *PAYG*
- - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/autoscale/waf/via-lb/1nic/existing-stack) - - *PAYG*
- - *Using BIG-IQ for Licensing*
+ - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/autoscale/waf/via-lb/1nic/new-stack) + - *PAYG*
+ - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/autoscale/waf/via-lb/1nic/existing-stack) + - *PAYG*
+ - *Using BIG-IQ for Licensing*
- *Frontend via DNS* - - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/autoscale/waf/via-dns/1nic/new-stack) - - *PAYG*
- - *Using BIG-IQ for Licensing*
- - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v6.0.3.0/supported/autoscale/waf/via-dns/1nic/existing-stack) - - *PAYG*
- - *Using BIG-IQ for Licensing*
\ No newline at end of file + - [New Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/autoscale/waf/via-dns/1nic/new-stack) + - *PAYG*
+ - *Using BIG-IQ for Licensing*
+ - [Existing Networking Stack](https://github.com/F5Networks/f5-azure-arm-templates/tree/v7.0.0.1/supported/autoscale/waf/via-dns/1nic/existing-stack) + - *PAYG*
+ - *Using BIG-IQ for Licensing*
\ No newline at end of file