Hello All, and welcome to a new mini-series, these posts will be on SCOM High Availability, in particular the Data Access Service (which is what the Console connects to).
By default if your Operations Manager Operations console is connected to the Data Access service of one management server and the connection fails, it does not automatically failover to another management server in your management group. To enable high availability for your Operations Manager Data Access service, you can use Network Load Balancing (NLB). By configuring NLB, and connecting to the NLB cluster, if the connection fails, it will automatically be redirected to another management server.
We’ll break the articles/posts down into smaller pieces. Here is a high-level of each piece.
Let’s start with the first step.
Configure A Static IP Address
The first thing we need is each Management Server to have a static IP Address.
Let’s log into our first Management Server, and check it’s IP Address/configuration.
Right-click on the Windows button, and click Control Panel
Within the Control Panel, click on Network and Internet
Then click on Network and Sharing
Then click the Ethernet link under Connection
On the Ethernet Status dialog, click the Properties button
On the Ethernet Properties dialog, select Internet Protocol Version 4 (TCP/IPv4), then click Properties
On the Internet Protocol Version 4 (TCP/IPv4) Properties dialog, change the configuration to “Use the following IP address“, and supply a static IP from your environment. You will also have to do the same for DNS, so choose “Use the following DNS server addresses“. Once you have filled in the appropriate information, click OK. Then close any of the open dialogs/windows.
Now our first Management Server has a static IP address. Repeat these same steps on any other Management Servers you want to include in the cluster.
In the next post in this series, we will move onto Step 2: Enable NLB on each Management Server > Install Network Load Balancing.