Nimbostratus
Nimbostratus
Thanks for the update. You mention that "we basically require the RMS deployment for loading the actual F5 MP, F5 device configuration and related data-source,etc". My question is what's the benefit of having the service clusters on the RMS? Is this specific for environments where they dont have a fully distributed Ops Mgr environment but instead of 2 RMS servers that are cluster and the managment server. (meaning they dont have designated mgmt servers that report to the RMS)
I was able to successfully install the F5 MP on both of our RMS server and I added it as a clusterd service but am now wondering if that was not necessary. I also installed/ran the F5 MP setup on a dedicated mgmt server, discovered an F5 and applied overrides to the MP enabling rules for performance collection of LTM avg/sec connection info. The problem is i see no data or even the list of perf rules in the performance rule. I could be mistaken but i did not think it was necessary to enable the red/green rules to collect this info and I would have expected to at least see the data that is collected from the F5 mp rules that are enabled by default.
Looking at the F5 Monitoring Log I do see Event 201 & 405 errors
Event 201 Error detail
Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host OKCMONTST942 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: OKCMONTST942
Detailed Exception Information:
F5Networks.F5Exception: Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host OKCMONTST942 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: OKCMONTST942 ---> F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionFailedException: The PerformanceDataSourceConnector connection to Operations Manager Health Service host OKCMONTST942 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: OKCMONTST942 ---> System.Runtime.Remoting.RemotingException: Failed to connect to an IPC Port: The system cannot find the file specified.
Server stack trace:
at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel, Int32 timeout)
at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel level, Int32 timeout)
at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at F5Networks.Remoting.ServerBase.get_HostProcess()
at F5Networks.ManagementPack.DataAccess.OperationsManager.DataSource.DataSourceConnector`2.Connect()
--- End of inner exception stack trace ---
at F5Networks.ManagementPack.DataAccess.OperationsManager.DataSource.DataSourceConnector`2.Connect()
at F5Networks.ManagementPack.DataAccess.OperationsManager.DataSource.ManagedDataSourceConnection`3.CoreConnect()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ManagedConnectionBase`1._DoConnectWithRecovery()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ManagedConnectionBase`1.Connect()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2._CreatePoolMember()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2._InitializeCache()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.Initialize(UInt32 initialOperationSize)
at F5Networks.ManagementPack.Services.DeviceMonitor._CreateDataSourceConnection() in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\HealthMonitor\Services\DeviceMonitor\DataAccess.cs:line 939
at F5Networks.ManagementPack.Services.DeviceMonitor._InitializeDataStore() in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\HealthMonitor\Services\DeviceMonitor\DataAccess.cs:line 662
Event 405 Error detail
Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host OKCMONTST942 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: OKCMONTST942
Detailed Exception Information:
F5Networks.F5Exception: Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host OKCMONTST942 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: OKCMONTST942 ---> F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionFailedException: The PerformanceDataSourceConnector connection to Operations Manager Health Service host OKCMONTST942 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: OKCMONTST942 ---> System.Runtime.Remoting.RemotingException: Failed to connect to an IPC Port: The system cannot find the file specified.
Server stack trace:
at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel, Int32 timeout)
at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel level, Int32 timeout)
at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at F5Networks.Remoting.ServerBase.get_HostProcess()
at F5Networks.ManagementPack.DataAccess.OperationsManager.DataSource.DataSourceConnector`2.Connect()
--- End of inner exception stack trace ---
at F5Networks.ManagementPack.DataAccess.OperationsManager.DataSource.DataSourceConnector`2.Connect()
at F5Networks.ManagementPack.DataAccess.OperationsManager.DataSource.ManagedDataSourceConnection`3.CoreConnect()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ManagedConnectionBase`1._DoConnectWithRecovery()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ManagedConnectionBase`1.Connect()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2._CreatePoolMember()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2._InitializeCache()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.Initialize(UInt32 initialOperationSize)
at F5Networks.ManagementPack.Services.DeviceMonitor._CreateDataSourceConnection() in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\HealthMonitor\Services\DeviceMonitor\DataAccess.cs:line 939
at F5Networks.ManagementPack.Services.DeviceMonitor._InitializeDataStore() in c:\home\f5cm\sandbox\cc\builds\ballantine\104734\Branches\Trunk\HealthMonitor\Services\DeviceMonitor\DataAccess.cs:line 662
--- End of inner exception stack trace ---