#start-AzVM -ResourceGroupName $ResourceGroupName -Name $VM.Name Set-AzNetworkInterface -NetworkInterface $NIC Write-Host "Assigning network card '$NICName' of the '$VMName' VM to the backend pool '$BackEndConfigurationName'. $NIC = Get-AzNetworkInterface -name $NICName -ResourceGroupName $ResourceGroupName $NICName = ($VM.NetworkInterfaceIDs.Split('/') | select -last 1) $VM = Get-AzVM -ResourceGroupName $ResourceGroupName -Name $VMName $BEPool = Get-AzLoadBalancerBackendAddressPoolConfig -Name $BackEndConfigurationName -LoadBalancer $ILB $BEConfig = Add-AzLoadBalancerBackendAddressPoolConfig -Name $BackEndConfigurationName -LoadBalancer $ILB | Set-AzLoadBalancer Write-Host "Adding new backend Pool '$BackEndConfigurationName'. $BackEndConfigurationName = "backendPoolASCS$count" # Add new back-end configuration into existing ILB $HealthProbe = Get-AzLoadBalancerProbeConfig -Name $LBProbeName -LoadBalancer $ILB $FEConfig = Get-AzLoadBalancerFrontendIpConfig -Name $FrontEndConfigurationName -LoadBalancer $ILB $ILB = Get-AzLoadBalancer -Name $ILBname -ResourceGroupName $ResourceGroupName $ILB | Add-AzLoadBalancerProbeConfig -Name $LBProbeName -Protocol Tcp -Port $Probeport -ProbeCount 2 -IntervalInSeconds 10 | Set-AzLoadBalancer $ILB | Add-AzLoadBalancerFrontendIpConfig -Name $FrontEndConfigurationName -PrivateIpAddress $ILBIP -SubnetId $Subnet.Id Write-Host "Adding new front end IP Pool '$FrontEndConfigurationName'. # Add second front-end and probe configuration $Subnet = Get-AzVirtualNetworkSubnetConfig -VirtualNetwork $VNet -Name $SubnetName $VNet = Get-AzVirtualNetwork -Name $VNetName -ResourceGroupName $ResourceGroupName $FrontEndConfigurationName ="lbFrontendASCS$count" $ILB = Get-AzLoadBalancer -Name $ILBName -ResourceGroupName $ResourceGroupName $ProbePort = "623$SAPInstanceNumber" # Probe port: must be a unique value for each IP and load balancer $SAPInstanceNumber = 50 # SAP ASCS/SCS instance number: must be a unique value for each cluster $VMNames = "pr2-ascs-0","pr2-ascs-1" # Existing cluster virtual machine names
$ILBName = "pr2-lb-ascs" # Existing ILB name $SubnetName = "Subnet" # Existing subnet name $VNetName = "pr2-vnet" # Existing virtual network name $ResourceGroupName = "SAP-MULTI-SID-Landscape" # Existing resource group name The script will create all needed load-balancing rules for all SAP ASCS/SCS ports.
#HOW TO INSTALL SAP DOWNLOAD MANAGER IN WINDOWS 2012 UPDATE#
Update the PowerShell variables for your environment. The following script adds a new IP address to an existing load balancer. Each IP address requires its own load-balancing rules, probe port, front-end IP pool, and back-end pool. To create more than one SAP ASCS/SCS instance in the same WSFC cluster, use PowerShell to add an IP address to an existing Azure internal load balancer. Add an IP address to an existing Azure internal load balancer by using PowerShell In our scenario, the IP address is 10.0.0.50. The new IP address that you assign to the virtual host name of the additional ASCS/SCS instance must be the same as the new IP address that you assigned to the SAP Azure load balancer. The procedure for creating a DNS entry is also described in detail in the main guide for high-availability SAP NetWeaver on Windows VMs. The new host name and IP address are displayed in the DNS Manager, as shown in the following screenshot:
You can create a DNS entry for the virtual host name of the ASCS/SCS instance by using the following parameters: New SAP ASCS/SCS virtual host name You can install additional SAP ASCS/SCS instances in the existing WSFC cluster with two nodes: Virtual machine roleĬreate a virtual host name for the clustered SAP ASCS/SCS instance on the DNS server
For example, if one IP address on an Azure internal load balancer uses probe port 62300, no other IP address on that load balancer can use probe port 62300.įor our purposes, because probe port 62300 is already reserved, we are using probe port 62350. For SAP ASCS/SCS cluster instances, each IP address requires a unique probe port.
0 kommentar(er)
