Hello Operations Manager Community,
We are excited to announce the release of the Operations Manager 2007 R2 Interop Connectors (Beta 2) to Connect.
This package contains the beta software for System Center Operations Manager 2007 R2 Interop Connectors.
The following Connectors are included:

• Operations Manager 2007 R2 Connector for Tivoli Enterprise Console
• Operations Manager 2007 R2 Connector for HP OpenView Operations
• Operations Manager 2007 R2 Universal Connector

https://connect.microsoft.com/
Title Operations Manager 2007 R2 Interop Connectors - Beta 2
Release Date 12/19/2008
Size 122.95 MB
Version 1.0.0.0
Category Build
Milestone Beta 2

 

Using NLB is very handy on several configurations ( but remember there is a lot of broadcast trafic ) so the nlb network should be in a different subnet than your own production network.

First add the feature in windows 2008 , start up the NLB mmc on the server.

  

In my care I have 3 nic , one production , two DHCP.

I did new cluster and the wizzard starts. I did pick the second nic.

 

  

The warning is I NEED a fixed IP !!  so i put in a fix IP and added the cluster IP address

 

  

Most of the times You don’t need every port on the nic , for webservers it is only one or two ports. I my case I used the opsmgr webconsole basic port 51908.

  

Now One host is ready to go.

I went to my IIS 7 MMC

  

For changing the IP you do on the website edit bindings get the default. And Edit the settings.

 

  

As you can see the NLB cluster IP is there I did not config a second IP for the NLB . So I put in the NLB IP and now the website is listening on the NLB IP. AND NOT on the default IP from the server.

 

So If you want to add a second IP to the NLB go back to the NLB config an do edit on the cluster properties

as you can see the IIS config shows the second IP

This could be handy for large webfarms that uses hostheaders.

For Setting up the Second , thirth node just add the machine in the cluster Add host and settings are deployed to the other server.

Fixed IP is needed !!

 

How setup a Windows 2008 cluster, First you have to add a new feature. Go Server Manager Add Features.

We select failover clustering and if there is something worng you can get a nice screen.

  Now that we did the windows feature addon we can start with the real configuration

Start the wizzard and select the first cluster node, the server needs the netbios name and auto resolve it to FQDN.

Always do the test  you can easy see if there is a problem with your clustre configuration, if you don’t want to run all the test you can make a selection.

     

I did run all the tests and as you can see it ends with a nice report.

 

Now the test is success full we can start to create the first node.

Give a cluster Netbios name this is the name that holds the cluster resources, and it needs a IP ( check the DNS ! )

Now that the first node is created we start to put the second node in place

 

   

The Same steps for the second node , run the tests and get a report

 

As you can see in the steps there is no Quorum drive , this is not needed anymore ;-). In the next sessions I will dive deep in the cluster management and advanced config.