Resource manager windows

Actively receiving network traffic. A switchover from active to backup instances in the HA pair can occur with no apparent change in IP address, as far as the SIP dialog is concerned.Figure: High Availability Using a Virtual IP ConfigurationFeature LimitationWhen using Windows Network Load Balancing (NLB) for virtual IP-based HA, only processes running outside the Windows NLB cluster can address that cluster. If SIP Server uses Windows NLB and Resource Manager/Media Control Platform are running on the same machine as SIP Server, then RM/MCP cannot address SIP Server using the cluster address.With Windows NLB, a local process will always resolve a virtual IP address to the local host. This means that if an MCP process on a particular server tries to contact a failed Resource Manager, Windows NLB will resolve the virtual IP address in the configuration to the local host, and the same local Resource Manager will be contacted, instead of the backup Resource Manager on the backup host.Sample ConfigurationThe following task table outlines the basic steps required for an HA deployment on Windows, with the following assumptions:This is a two-machine deployment, with one SIP Server and Resource Manager instance co-deployed on each machine.Task Summary: Configuring HA through Virtual IP for WindowsObjective Key Procedures and Actions1. Configure RM applicationsGo to: Provisioning > Environment > ApplicationsSet the Resource Manager option cluster.ha-mode to active-standby.2. Configure GVP components.See the GVP 9.0 Deployment Guide for more information.3. Configure GVP DNs.Go to: Provisioning > Switching > SwitchesIn the GVP Trunk DN, set the contact and contact-backup options to the two Resource Manager IP addresses.For the Voice over service IP Service DN, create two separate DNs with each contact option set to one of the Resource Manager IP addresses.LinuxVirtual IP Takeover Solution LinuxFigure: Virtual IP Takeover Solution (Linux) RM active-standbyThis configuration is applicable for RM active-standby.GVP deployment is for Linux.Simple IP Takeover for single NIC is supported; if multiple NICs are present in the system, then a Linux bonding driver can be used.Separate hosts are required for SIP-Server, RMs and MCPs.Genesys recommends that you configure alarm conditions and reaction scripts for handling the failover/switchover condition in this case.Resource ManagerGVP 9.0 supports HA for Resource Manager on both Windows and Linux operating systems.HA (Windows)Windows Network Load Balancing (NLB) provides HA for the Resource Manager. You can configure two Resource Managers to run as hot standby, or warm active standby pairs that have a common virtual IP.Incoming IP traffic is load-balanced by using NLB, in which two Resource Manager servers use a virtual IP number to switch the load to the appropriate server during failover. The network interface cards (NICs) in each Resource Manager host in a NLB cluster are monitored to determine when network errors occur. If any of the NICs encounter an error, the Resource Manager considers the network down, and the load balancing of the incoming IP traffic is adjusted accordingly.To determine the current status of the Resource Manager at any time, check the traps in the SNMP Manager Trap Console to which the

SubscriptionName TenantId Environment------- ---------------- -------- -----------EdgeArmUser@localhost Default Provider Subscription aaaabbbb-0000-cccc-1111-dddd2222eeee AzASEPS C:\windows\system32>An alternative way to sign in is to use the login-AzAccount cmdlet.login-AzAccount -EnvironmentName -TenantId aaaabbbb-0000-cccc-1111-dddd2222eeeeHere's an example output.PS C:\WINDOWS\system32> login-AzAccount -EnvironmentName AzASE -TenantId aaaabbbb-0000-cccc-1111-dddd2222eeeeAccount SubscriptionName TenantId------- ---------------- --------EdgeArmUser@localhost Default Provider Subscription c0257de7-538f-415c-993a-1b87a...PS C:\WINDOWS\system32>To verify that the connection to the device is working, use the Get-AzResource command. This command should return all the resources that exist locally on the device.Here's an example output.PS C:\WINDOWS\system32> Get-AzResourceName : aseimagestorageaccountResourceGroupName : ase-image-resourcegroupResourceType : Microsoft.Storage/storageaccountsLocation : dbelocalResourceId : /subscriptions/.../resourceGroups/ase-image-resourcegroup/providers/Microsoft.Storage/storageac counts/aseimagestorageaccountTags :Name : myaselinuxvmimage1ResourceGroupName : ASERGResourceType : Microsoft.Compute/imagesLocation : dbelocalResourceId : /subscriptions/.../resourceGroups/ASERG/providers/Microsoft.Compute/images/myaselinuxvmimage1Tags :Name : ASEVNETResourceGroupName : ASERGResourceType : Microsoft.Network/virtualNetworksLocation : dbelocalResourceId : /subscriptions/.../resourceGroups/ASERG/providers/Microsoft.Network/virtualNetworks/ASEVNETTags :PS C:\WINDOWS\system32>Set the Azure Resource Manager environment and verify that your device to client communication via Azure Resource Manager is working fine. Take the following steps for this verification:Use the Add-AzureRmEnvironment cmdlet to further ensure that the communication via Azure Resource Manager is working properly and the API calls are going through the port dedicated for Azure Resource Manager - 443.The Add-AzureRmEnvironment cmdlet adds endpoints and metadata to enable Azure Resource Manager cmdlets to connect with a new instance of Azure Resource Manager.ImportantThe Azure Resource Manager endpoint URL that you provide in the following cmdlet is case-sensitive. Make sure the endpoint URL is all in lowercase and matches what you provided in the hosts file. If the case doesn't match, then you will see an error.Add-AzureRmEnvironment -Name -ARMEndpoint " output:PS C:\windows\system32> Add-AzureRmEnvironment -Name AzDBE -ARMEndpoint Resource Manager Url ActiveDirectory Authority---- -------------------- -------------------------AzDBE the environment as Azure Stack Edge and the port to be used for Azure Resource Manager calls as 443. You define the environment in two ways:Set the environment. Type the following command:Set-AzureRMEnvironment -Name For more information, go to Set-AzureRMEnvironment.Define the environment inline for every cmdlet that you execute. This ensures that all the API calls are going through the correct environment. By default, the calls would go through the Azure public but you want these to go through the environment that you set for Azure Stack Edge device.See more information on how to switch AzureRM environments.Call local device APIs to

Fine. Take the following steps for this verification:Use the Add-AzEnvironment cmdlet to further ensure that the communication via Azure Resource Manager is working properly and the API calls are going through the port dedicated for Azure Resource Manager - 443.The Add-AzEnvironment cmdlet adds endpoints and metadata to enable Azure Resource Manager cmdlets to connect with a new instance of Azure Resource Manager.ImportantThe Azure Resource Manager endpoint URL that you provide in the following cmdlet is case-sensitive. Make sure the endpoint URL is all in lowercase and matches what you provided in the hosts file. If the case doesn't match, then you will see an error.Add-AzEnvironment -Name -ARMEndpoint " sample output is shown below:PS C:\WINDOWS\system32> Add-AzEnvironment -Name AzASE -ARMEndpoint " Resource Manager Url ActiveDirectory Authority---- -------------------- -------------------------AzASE the environment as Azure Stack Edge and the port to be used for Azure Resource Manager calls as 443. You define the environment in two ways:Set the environment. Type the following command:Set-AzEnvironment -Name Here's an example output.PS C:\WINDOWS\system32> Set-AzEnvironment -Name AzASEName Resource Manager Url ActiveDirectory Authority---- -------------------- -------------------------AzASE more information, go to Set-AzEnvironment.Define the environment inline for every cmdlet that you execute. This ensures that all the API calls are going through the correct environment. By default, the calls would go through the Azure public but you want these to go through the environment that you set for Azure Stack Edge device.See more information on how to Switch Az environments.Call local device APIs to authenticate the connections to Azure Resource Manager.These credentials are for a local machine account and are solely used for API access.You can connect via login-AzAccount or via Connect-AzAccount command.To sign in, type the following command.$pass = ConvertTo-SecureString "" -AsPlainText -Force;$cred = New-Object System.Management.Automation.PSCredential("EdgeArmUser", $pass)Connect-AzAccount -EnvironmentName AzASE -TenantId aaaabbbb-0000-cccc-1111-dddd2222eeee -credential $credUse the tenant ID aaaabbbb-0000-cccc-1111-dddd2222eeee as in this instance it's hard coded.Use the following username and password.Username - EdgeArmUserPassword - Set the password for Azure Resource Manager and use this password to sign in.Here's an example output for the Connect-AzAccount:PS C:\windows\system32> $pass = ConvertTo-SecureString "" -AsPlainText -Force;PS C:\windows\system32> $cred = New-Object System.Management.Automation.PSCredential("EdgeArmUser", $pass)PS C:\windows\system32> Connect-AzAccount -EnvironmentName AzASE -TenantId aaaabbbb-0000-cccc-1111-dddd2222eeee -credential $credAccount