Distributed SCOM Instance - Installing F5 Management Pack on a Management Server Only

Setup on the RMS is doing 2 important things. First it imports the mp as you noticed. Second, it creates or upgrades our SQL database, which is vital to getting the F5 Monitoring Service to run on any management server.

 

 

The other reason you should run Setup on the RMS is to prevent potential error messages. Our management pack uses custom data sources which get loaded by Operations Manager's Health Service at start up. If these modules don't get loaded, there will most likely be errors in your SCOM event log.

 

 

Also, by default, we don't have the F5 Monitoring Service start on the RMS if there are other management servers in a SCOM deployment, but you could actually start the service and run discoveries and monitor F5 devices from the RMS as well.

 

 

To your last concern, the only server that connects to the F5 is the one that the device was discovered from. So if you have ManagementServer1 which discovers F51 and ManagementServer2 which discovers F52, the connector on MS1 will only connect to F51 and the same with MS2 and F52. This was done on purpose to increase performance across your whole deployment. So even though you have to run the F5 Management Pack Setup on the RMS, the RMS will not be directly connected to the F5 devices unless you use it to discover those devices to begin with.