A Unified Communication Blog
Get Adobe Flash player

 

In the third post of the series of creating a High Availability solution for Lync, we will be looking on how to configure the SQL 2012 mirroring cluster which has been installed in Part 1 and Part 2.

 

I like to use windows firewall on my servers – many disable it, but I will rather use a little bit more time to figure out to configure it, so the first part is to add exceptions to the default rules, so that the SQL cluster will work.

I will run the below cmdlets on all three SQL servers (you could get more restrictive on the witness server).

Before running it on the servers you should adjust the IP ranges so it fit your environment and subnets.

 

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQLServer)” -Direction Inbound –Protocol TCP –LocalPort 1433 -RemoteAddress LocalSubnet -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQL Admin Connection)” -Direction Inbound –Protocol UDP –LocalPort 1434 -RemoteAddress LocalSubnet -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQL Admin Connection)” -Direction Inbound –Protocol TCP –LocalPort 1434 -RemoteAddress LocalSubnet -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQL Service Broker)” -Direction Inbound –Protocol TCP –LocalPort 4022 -RemoteAddress LocalSubnet -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQL Debugger/RPC)” -Direction Inbound –Protocol TCP –LocalPort 135 -RemoteAddress LocalSubnet -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (Analysis Services)” -Direction Inbound –Protocol TCP –LocalPort 2383 -RemoteAddress LocalSubnet -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQL Browser)” -Direction Inbound –Protocol TCP –LocalPort 2382 -RemoteAddress LocalSubnet -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQL Mirroring1)” -Direction Inbound –Protocol TCP –LocalPort 5022 -RemoteAddress LocalSubnet -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQL Mirroring2)” -Direction Inbound –Protocol TCP –LocalPort 7022 -RemoteAddress LocalSubnet -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (http)” -Direction Inbound –Protocol TCP –LocalPort 80 -RemoteAddress 10.0.0.0/8 -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (https)” -Direction Inbound –Protocol TCP –LocalPort 443 -RemoteAddress 10.0.0.0/8 -Action Allow

New-NetFirewallRule -DisplayName “Allow Inbound SQL Server (SQL Server Dynamic)” -Direction Inbound -Program “%ProgramFiles%Microsoft SQL ServerMSSQL11.RTCMSSQLBinnsqlservr.exe” -RemoteAddress LocalSubnet -Action Allow

Enable-NetFirewallRule -DisplayName “File and Printer Sharing (NB-Name-In)”

Enable-NetFirewallRule -DisplayName “File and Printer Sharing (NB-Datagram-In)”

Enable-NetFirewallRule -DisplayName “File and Printer Sharing (NB-Session-In)”

Enable-NetFirewallRule -DisplayName “File and Printer Sharing (SMB-In)”

Enable-NetFirewallRule -DisplayName “Inbound Rule for Remote Shutdown (RPC-EP-In)”

Enable-NetFirewallRule -DisplayName “Inbound Rule for Remote Shutdown (TCP-In)”

 

The next thing is to configure the reporting services on the two primary cluster nodes.

Launch the “Reporting Service Configuration Manager”

Select the Web Service URL:

I will go for the default configuration in this example, but you could choose to install a web server certificate so that the communication is encrypted.

Select Database and choose “Change Database”

 

Select “Create a new…” and Select Next

 

Select Next

 

Select Next

 

Select Next

 

Select Next to create the database.

Select “Report Manager URL” and hit Apply

 

Select Exit when it is complete

 

The reporting service is now finish and ready for use with Lync monitoring services.

This also completes the installation of the SQL Servers, which are now ready for installation of Lync, which I will cover in another post.

 

Lync 2013 High Availability

Part 1: http://exchangepro.dk/2013/08/28/install-a-sql-2012-mirroring-cluster-for-use-with-lync-2013-part-1/

Part 2: http://exchangepro.dk/2013/08/29/install-a-sql-2012-witness-server-for-use-with-lync-2013-part-2/

Part 4: http://exchangepro.dk/2013/09/14/deploy-a-lync-2013-file-store-part-4/

Part 5: http://exchangepro.dk/2013/09/19/prepare-your-servers-for-lync-server-2013-ha-part-5/

Part 6: http://exchangepro.dk/2013/09/21/creating-the-lync-server-2013-ha-topology-part-6/

Part 7: http://exchangepro.dk/2013/09/30/install-the-first-frontend-server-part-7/

Part 8: http://exchangepro.dk/2013/10/06/update-the-frontend-server-part-8/

Part 9: http://exchangepro.dk/2013/10/13/install-the-office-web-servers-part-9/

Part 10: http://exchangepro.dk/2013/10/21/deploy-the-director-servers-in-lync-2013-ha/

Part 11: http://exchangepro.dk/2013/10/25/install-the-access-edge-ha-servers-part-11/

Part 12: http://exchangepro.dk/2013/11/05/deploy-reverse-proxy-using-kemp-hardware-load-balancer-part-12/

Part 13: http://exchangepro.dk/2013/11/14/adding-additional-frontend-servers-to-lync-ha-part-13/

Part 14: http://exchangepro.dk/2013/11/26/setup-load-balancers-for-the-internal-lync-servers-part-14/

Part 15: http://exchangepro.dk/2013/11/26/load-balance-the-office-web-apps-server-part-15/

Part 16: http://exchangepro.dk/2013/11/26/load-balance-the-lync-frontend-web-services-part-16/

Part 17: http://exchangepro.dk/2013/11/28/load-balance-the-lync-frontend-services-part-17/

Part 18: http://exchangepro.dk/2013/12/15/load-balance-the-lync-director-servers-part-18/

Part 19: http://exchangepro.dk/2013/12/15/load-balance-lync-access-edge-internal-nic-part-19/

Part 20: http://exchangepro.dk/2013/12/29/load-balance-lync-access-edge-external-nic-part-20/

8 Responses to Configure a SQL 2012 Mirroring Cluster for use with Lync 2013 – Part 3

  • WHen i try to change the DB it says “Test Connection: could not connec to server: a network-related or instance-specific error occurrred while establishing a connectoin to SQL”

    Any thoughts on why i would get this? i followd your docs.

    thanks

    pete

    • Hi Pete

      Do you get the error when you click on the change database or later on.

      Did you make the changes to the Windows firewall ?
      In SQL Server Configuration Manager -> Select SQL Server Network Configuration -> Protocols for RTC make sure that Shared Memory, Named pipes and TCP/IP is enabled.

      /Joachim

      • Thanks for replying!!

        The local windows FW is turned off on both SQL servers.

        Named Pipes was disabled after install and I enabled that with no luck.

        It fails when it tests the connection.

        Verify that the instance name is correct and that SQL service is configured to allow remote connections. Provicer: Named Pipes Providoer, error 40 – cannot open a connecttion to SQL.

        Thanks,

        Pete

        • Hi Pete

          Can you connect to the databases from SQL Management Studio – sounds like the databases is not installed.
          could you check with the installer as well.

          /Joachim

  • I ran your script as above, making the necessary changes to the Remote Addresses, and all the rules populate as expected. However, when I try to publish the topology initially, it fails with an error saying the DB can’t be reached, ensure the service is running, etc… The only way I can publish the topology successfully is to turn off the firewall. I validated all the ports as correct, so what am I missing?

    • Hi Sean

      Try to enable logging in Windows firewall, and log failed attempts. Then you can see which port is blocked.

    • When you connect for the first time, it generally displays just the host server name i.e MYSQLSERVER , you are most likely after installing LYNC into an instance as you are planning to deploy ha or mirroring, therefore the instance name may be LYNC, in which case you should set your server name to MYSQLSERVER\LYNC and then click test connection, :-)

  • Did you try putting a \RTC after the server name in the Database Name Field?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Search

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 71 other subscribers

Follow me on Twitter