Configure Azure Load Balancer – Part5

Load Balancer Configuration – East US

-> Search for “Load Balancers” on Azure portal,

-> Basics Tab,

-> “Frontend IP Configuration” tab. Click “Add a frontend IP configuration”. This one will be utilized for the creating windows cluster,

-> Again, click “Add a frontend IP configuration”. This one will be utilized for Always On Listener,

-> “Backend Pools” Tab,

-> Click “Add” and select JBSAG1 and JBSAG2,

-> “Inbound Rules” Tab,

-> Click “Add a load balancing rule”,

-> Click “Create new” under “Health probe”,

-> Click “Add a load balancing rule”,

-> Click “Create new” under “Health probe”,

-> I will go with the default values for tabs “Outbound rules” and “Tags”. Click Create.

Load Balancer Configuration – West US

-> Search for “Load Balancers” on Azure portal,

-> Basics Tab,

-> “Frontend IP Configuration” tab. Click “Add a frontend IP configuration”. This one will be utilized for the creating windows cluster,

-> Again, click “Add a frontend IP configuration”. This one will be utilized for Always On Listener,

-> “Backend Pools” Tab,

-> Click “Add” and select JBSAG3,

-> “Inbound Rules” Tab,

-> Click “Add a load balancing rule”,

-> Click “Create new” under “Health probe”,

-> Click “Add a load balancing rule”,

-> Click “Create new” under “Health probe”,

-> I will go with the default values for tabs “Outbound rules” and “Tags”. Click Create.

More articles on this Series,

-> Always On Availability Group Configuration on Azure IaaS Virtual Machine utilizing Multi Subnet
-> Always On Availability Group Environment on Azure IaaS Virtual Machine Introduction – Part1
-> Configure appropriate Virtual Network and Subnet for Azure IaaS Virtual Machine – Part2
-> Deploy required Azure IaaS Virtual Machine – Part3
-> Configure Domain Controller and Windows Cluster on appropriate Azure IaaS Virtual Machine – Part4
-> Configure Always On Availability Group with Listener – Part6

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.

Configure Domain Controller and Windows Cluster on appropriate Azure IaaS Virtual Machine – Part4

Active Directory Configuration – JBSDC

-> Connect to Azure Virtual Machine JBSDC and open a PowerShell command window.

-> Execute below command for installing Active Directory Domain Services,

Install-WindowsFeature AD-Domain-Services -IncludeManagementTools

-> Execute below command to configure an appropriate domain,

Install-ADDSForest -DomainName JBSWIKI.com

-> Virtual Server JBSDC will restart after the configuration. Login to Virtual Server JBSDC using your domain account, in my case I will use account jbswikijbswiki.

Add Database Server JBSAG1 to Domain JBSWIKI.COM

-> Login to Database server JBSAG1 and execute below powershell script to add Database Server JBSAG1 to domain JBSWIKI.COM. Please modify $domain and $DNSIP with appropriate values before executing,

$domain = "JBSWIKI.COM"
$DNSIP = "172.20.1.4"
$IAlias = (Get-NetConnectionProfile -ErrorAction Stop).InterfaceAlias
Set-DnsClientServerAddress -InterfaceAlias $IAlias -ServerAddresses $DNSIP -ErrorAction Stop
Add-Computer -DomainName $domain -ErrorAction Stop

-> After you execute above powershell script, you will need to key in the admin account that has permission to access DNS Server JBSDC,

-> Restart Database Server JBSAG1 as requested,

Add Database Server JBSAG2 to Domain JBSWIKI.COM

-> Follow same procedure as detailed above to add Database Server JBSAG2 to domain JBSWIKI.COM.

Add Database Server JBSAG3 to Domain JBSWIKI.COM

-> Follow same procedure as detailed above to add Database Server JBSAG3 to domain JBSWIKI.COM.

Connecting to SQL Server Instances JBSAG1 and JBSAG2 using SQL Server Management Studio

-> When connecting to SQL Server JBSAG1\JBSAG2\JBSAG3 from SSMS, we will get below error,
TITLE: Connect to Server
Cannot connect to JBSAG1.
ADDITIONAL INFORMATION:

Login failed for user ‘JBSWIKIjbswiki’. (Microsoft SQL Server, Error: 18456)
For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-18456-database-engine-error
BUTTONS:

-> I logged into Database Server JBSAG1\JBSAG2\JBSAG3 using Server\Login (eg: JBSAG1\jbswiki) or use a Run As on SSMS with account Server\Login (eg: JBSAG1\jbswiki) and then add the required logins to SQL Server JBSAG1\JBSAG2\JBSAG3.

More articles on this Series,

-> Always On Availability Group Configuration on Azure IaaS Virtual Machine utilizing Multi Subnet
-> Always On Availability Group Environment on Azure IaaS Virtual Machine Introduction – Part1
-> Configure appropriate Virtual Network and Subnet for Azure IaaS Virtual Machine – Part2
-> Deploy required Azure IaaS Virtual Machine – Part3
-> Configure Azure Load Balancer – Part5
-> Configure Always On Availability Group with Listener – Part6

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.

Configure appropriate Virtual Network and Subnet for Azure IaaS Virtual Machine – Part2

Provision Appropriate Virtual Network and associated Subnet

Virtual Network and Subnet – East US

-> Search for “Virtual Network” in Azure portal and provision it as per below guidance,

-> Click on ” Add subnet” on “IP Address” Tab and fill it up with appropriate details as shown in the screenshot,

-> I will go with the default values for “Security” and “Tags” tab.

-> Click Create and wait for the Virtual Network creation.

Virtual Network and Subnet – West US

-> Search for “Virtual Network” in Azure portal and provision it as per below guidance,

-> I will go with the default values for “Security” and “Tags” tab.

Virtual Network jbswiki_VNET_eastus and jbswiki_VNET_westus Peering

-> Open Virtual Network jbswiki_VNET_eastus and click on “Peerings”.

More articles on this Series,

-> Always On Availability Group Configuration on Azure IaaS Virtual Machine utilizing Multi Subnet
-> Always On Availability Group Environment on Azure IaaS Virtual Machine Introduction – Part1
-> Deploy required Azure IaaS Virtual Machine – Part3
-> Configure Domain Controller and Windows Cluster on appropriate Azure IaaS Virtual Machine – Part4
-> Configure Azure Load Balancer – Part5
-> Configure Always On Availability Group with Listener – Part6

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.