Forum Discussion
Fabrizio_Chiava
Nimbostratus
Nimbostratusdiscovery problem!!!
Hello everybody,
the problem is we can't discovery network F5 object by Management Pack of SCOM (System Center Operations Manager 2007 R2).
The version of Management Pack is 2.1.5.440.
The SCOM environment is installed on Windows Server 2008 v6.0 build 6002 SP2 with DB on SQL Server 2008.
The service account with start F5 Service on RMS, is the same of SQL DB F5_ManagementPack (is a user with Global Admin rights).
In the customer environment there are two Viprions (in cluster) with two blade per chassis. On the Viprion there is LTM software version 10.0.1 HF4.
The problem is:
When the Discover Devices Wizard of F5 Management Pack perform discovery appliances on the network, we insert the IP address and the credentials of BIGIP GUI (f.i. admin, admin or an user with Administrator Role) it shown the error in attachment (error event Windows - SCOM).
We try the same operation this time with ROOT credentials and the software perform the error in attachment (error event Windows - ROOT).
We try also to connect to the Viprion appliances by telnet on port 443 and 4353 (iControl). The firewall doesn't block this port, there is a rule "ad-hoc".
We connect correcty with browser to web service of iControl on the appliance (
) and insert admin credentials. We enter correctly. This test we performed on the machine with RMS installed.
Summary:
1) The SCOM environment is integrated with Active Directory, and perform discovery with an user of AD (with Admin right on the local server with SCOM installed);
2) On the Viprion web GUI there is local basic authentication (default) and not AD integrated.
Does exist a best practice to configure SCOM discover with a local user of Viprion? Can we configure on Viprion level authentication with AD only for the monitoring?
Could you help me, please???
Thanks in advance
Fabrizio.
Fabrizio_ChiavaHi Julian,
thanks again.. I suggest to customer to reinstall the agent on another machine (different from RMS).
I'll inform you asap about any results.
Regards
Fabrizio.- Thank you Fabrizio!
I would also suggest installing the latest release of the F5 Management Pack (v2.2.0.580) as it would make our troubleshooting easier. Here's the download page for the F5 Management Pack:
http://devcentral.f5.com/Community/GroupDetails/tabid/1082223/asg/54/afv/topic/aft/1176625/aff/2301/showtab/groupforums/Default.aspx
(Just stick with the core management pack for now.)
Thank you.
Julian - Fabrizio_ChiavaHi Julian,
on below there is the setup.log from MS machine different from RMS. There were many problems during the installation:
Log Name: F5 Monitoring Log
Source: F5Networks.HealthMonitor
Date: 14/03/2011 16.20.48
Event ID: 201
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Gewvasco3.ternaren.prv
Description:
Unhandled global exception: Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host HealthService could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: HealthService
Detailed Exception Information:
F5Networks.F5Exception: Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host HealthService could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: HealthService ---> F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionFailedException: The PerformanceDataSourceConnector connection to Operations Manager Health Service host HealthService could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: HealthService ---> 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()
at F5Networks.ManagementPack.Services.DeviceMonitor._InitializeDataStore()
--- End of inner exception stack trace ---
Event Xml:
201
2
0
0x80000000000000
12
F5 Monitoring Log
Gewvasco3.ternaren.prv
Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host HealthService could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: HealthService
Detailed Exception Information:
F5Networks.F5Exception: Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host HealthService could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: HealthService ---> F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionFailedException: The PerformanceDataSourceConnector connection to Operations Manager Health Service host HealthService could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.
: HealthService ---> 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()
at F5Networks.ManagementPack.Services.DeviceMonitor._InitializeDataStore()
--- End of inner exception stack trace ---
Thanks a lot
Fabrizio. - Thanks for the update Fabrizio. The error you're getting could be the result of either of the following causes:
1. The F5 Monitoring Service cannot connect to the SCOM Health Service, for writing health and performance data, or:
2. The F5 Management Pack data sources are not loaded in the SCOM Health Service running on the Management Server where you monitor the F5 Devices from.
I'm going to assume that you have done the correct deployment of the F5 Management Pack in your distributed SCOM environment: first you have installed the F5 MP on the RMS where you have left the F5 Monitoring Service stopped (and in Manual/Disabled) mode as the F5 MP setup leaves it, and then you deployed the F5 MP on a (secondary) management server, where you plan to discover and monitor the F5 device(s) from. If my assumption is not correct please let me know.
Coming back to the two possible causes for the error, for 1 make sure that the service account running the F5 Monitoring Service is in the Operations Manager Administrators group.
To validate 2, I would suggest running the "Show Failed Rules and Monitors for this Health Service" SCOM task for the Management Server where the F5 devices are being discovered/monitored from. The output of this task will show if the F5 Management Pack data sources are not loaded.
You can run the task from the SCOM Management Console :: Monitoring :: Operations Manager :: Management Server :: Management Server Health State :: select your management server :: Health Service Tasks (in the Action pane) :: Show Failed Rules and Monitors for this Health Service. Please let me know the result of this task or if you need assistance running it.
Also, if you send us the Operations Manager event log and the F5 Monitoring Log (event log) to managementpack(at)f5(dot)com, we can probably find out more about the root of the problem.
Thank you.
Julian - Fabrizio,
Please take a look at the following post, which could be tracking a very similar issue with yours, and see if any of the suggestions made there would be relevant to your problem:
http://devcentral.f5.com/Community/GroupDetails/tabid/1082223/asg/54/aft/1177189/showtab/groupforums/Default.aspx1225360
Basically, what I would suggest you to do is to run the two tasks for showing failed rules and running rules on the Health Service:
1. Failed Rules: You can run this task from SCOM Management Console :: Monitoring :: Operations Manager :: Management Server :: Management Server Health State :: select your management server :: Health Service Tasks (in the Action pane) :: Show Failed Rules and Monitors for this Health Service.
2. Running Rules: You can run this task from SCOM Management Console :: Monitoring :: Operations Manager :: Management Server :: Management Server Health State :: select your management server :: Health Service Tasks (in the Action pane) :: Show Running Rules and Monitors for this Health Service.
For 1: Make sure the F5 related workflows are NOT shown as being reported as failed rules. If they do, we'll have to investigate why did they fail to load.
For 2: Make sure you see the F5 Monitors and rules loaded and running. If not, than we may have a problem with the actual SCOM F5 Management Pack not being correctly imported in SCOM.
Julian
