{"id":7121,"date":"2016-05-31T19:12:56","date_gmt":"2016-05-31T17:12:56","guid":{"rendered":"https:\/\/blog.redbaronofazure.com\/?p=7121"},"modified":"2016-05-31T20:24:27","modified_gmt":"2016-05-31T18:24:27","slug":"getting-a-vm-out-the-azure-load-balancer-pool","status":"publish","type":"post","link":"https:\/\/blog.redbaronofazure.com\/?p=7121","title":{"rendered":"Getting a VM out the Azure Load Balancer pool"},"content":{"rendered":"

When it’s time for maintenance you need to take your VMs out of rotation in the Azure Load Balancer backend pool. If you’ve deployed your solution via the portal, a JSON Template or via ARM scripting, you know that there are many moving parts involved. There is no API specific for this and what you have to do is unbind the network interface card (NIC) from the backend address pool. Script wise, this is not a one-liner although not as complex as you might think at first.<\/p>\n

Steps to remove a VM from the Load Balancer pool<\/strong><\/p>\n

First step is to find the NIC on the VM. Assuming your VM only have one NIC this is not that complicated. Once you have the NIC, you just update it and discard the binding to the load balancer.<\/p>\n

In Azure CLI code this would be as below. You name the NIC and you pass in nothing for the parameter –lb-address-pool-ids.<\/p>\n

azure network nic set -g resourceGroup -n nickname --lb-address-pool-ids<\/pre>\n
In PowerShell this is bit more complex as you have to nullify the property instead<\/p>\n
$nic = Get-AzureRmNetworkInterface -ResourceGroupName $rgName -Name $nicName\r\n\r\n$nic.IpConfigurations[0].LoadBalancerBackendAddressPools = $null\r\n\r\nSet-AzureRmNetworkInterface -NetworkInterface $nic<\/pre>\n
Bear in mind that the CLI version expects a resource-id for it’s parameter value and not just the name. The resource-id is the long path containing the subscription-guid, etc.<\/p>\n
Steps to add a VM to the Load Balancer pool<\/strong><\/p>\n
Once you are done with your maintenance of your VM it is time to put it back in the pool. This is basically no different from the above steps except this time we need to supply a value of the load balancer’s backend pool instead of nullifying it.<\/p>\n
In Azure CLI on a Mac\/Linux, this becomes a somewhat tricky task if we want to stick with using just a bash script. The CLI can emit JSON, which makes parsing it simpler, but bash has no build in JSON parser functionality, so for this I use jq (see refs for Github).<\/p>\n
 # get vm nic id\r\nnicID=$(azure vm show -g $resourceGroupName -n $vmName --json | jq '.networkProfile.networkInterfaces[0].id')\r\n# remove double quotes at start\/end\r\nnicID=\"${nicID%\\\"}\"\r\nnicID=\"${nicID#\\\"}\"\r\n# get just the name and not the long resourceId\r\nnicName=$(echo $nicID | cut -f9 -d '\/')\r\n\r\n# get id of LB BE pool\r\nlbbeID=$(azure network lb address-pool list  -g $resourceGroupName -l $loadBalancerName --json | jq '.[0].id')\r\n# remove double quotes at start\/end\r\nlbbeID=\"${lbbeID%\\\"}\"\r\nlbbeID=\"${lbbeID#\\\"}\"\r\n\r\n# add nic to lb\r\nazure network nic set -g $resourceGroupName -n $nicName --lb-address-pool-ids $lbbeID\r\n<\/pre>\n
In PowerShell this is cleaner\u00a0and means looking up the LoadBalancer and finding it’s backend address pool to the NIC.<\/p>\n
$nic = Get-AzureRmNetworkInterface -ResourceGroupName $rgName -Name $nicName\r\n\r\n$lb = Get-AzureRmLoadBalancer -Name $LoadBalancerName -ResourceGroupName $rgName\r\n\r\n$nic.IpConfigurations[0].LoadBalancerBackendAddressPools = $lb.BackendAddressPools\r\n\r\nSet-AzureRmNetworkInterface -NetworkInterface $nic\r\n<\/pre>\n
Putting it together<\/strong><\/p>\n
In my github repo, I’ve added small bash and PowerShell scripts that carries out the operation of adding and removing a VM from the load balancer.<\/p>\n
Removing a VM script wise from the Load Balancer\u00a0\"es-lb-remove\"<\/a><\/p>\n
Adding the VM back to the Load Balancer pool<\/p>\n
\"es-lb-add\"<\/a><\/p>\n
References<\/strong><\/p>\n
JSON parser on Github
\nhttps:\/\/stedolan.github.io\/jq\/<\/a><\/p>\n
Script Github repo
\nhttps:\/\/github.com\/cljung\/az-search-cluster<\/a><\/p>\n
 <\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
When it’s time for maintenance you need to take your VMs out of rotation in the Azure Load Balancer backend pool. If you’ve deployed your solution via the portal, a JSON Template or via ARM scripting, you know that there are many moving parts involved. There is no API specific for this and what you […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[91,131,121,141],"tags":[398,399,71],"_links":{"self":[{"href":"https:\/\/blog.redbaronofazure.com\/index.php?rest_route=\/wp\/v2\/posts\/7121"}],"collection":[{"href":"https:\/\/blog.redbaronofazure.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.redbaronofazure.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.redbaronofazure.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.redbaronofazure.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=7121"}],"version-history":[{"count":4,"href":"https:\/\/blog.redbaronofazure.com\/index.php?rest_route=\/wp\/v2\/posts\/7121\/revisions"}],"predecessor-version":[{"id":7127,"href":"https:\/\/blog.redbaronofazure.com\/index.php?rest_route=\/wp\/v2\/posts\/7121\/revisions\/7127"}],"wp:attachment":[{"href":"https:\/\/blog.redbaronofazure.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7121"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.redbaronofazure.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7121"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.redbaronofazure.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7121"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}