Forum Discussion
Don_1780
Nimbostratus
Nov 20, 2007Grid Control?
Anyone using Oracle Grid Control to monitor their F5 BIG IP? We recently did a migration and have gone from a set of Big IP 6800 running 9.2.5 build 5.0 to a set of 6800 running 9.4.1 build 29.0 The Grid Control software worked fine on the old set but now we are getting java exception errors on the new set. Anyone have any ideas?
thanks!
9 Replies
- Don_MacVittie_1Historic F5 AccountHi Don,
Can you tell us which exceptions it's throwing? The first thing that springs to mind is Java version incompatibilities, and that can be ruled out pretty easily if we see the version numbers.
Posting a stack trace is best, if you have one from one of the exceptions.
Thanks!
Don. - Don_1780
Nimbostratus
Ok, I'm a network geek, so this whole thing is outside of my normal knowledge, I'm going to paste the error I was sent by the guy who runs grid control. Hopefully this is what you need.
Failed to contact the target to be added. Following errors were received while testing the connection to the target. Update the properties accordingly, try Test Connection for testing the properties before saving.
Switch - em_error = ; nested exception is: java.lang.IllegalArgumentException Nov 16, 2007 11:25:56 AM org.apache.axis.client.Call invoke SEVERE: Exception: java.lang.IllegalArgumentException at org.apache.axis.encoding.ser.SimpleDeserializer.onEndElement(SimpleDeserializer.java:176) at org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:502) at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171) at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1140) at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:345) at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384) at org.apache.axis.client.Call.invoke(Call.java:2448) at org.apache.axis.client.Call.invoke(Call.java:2347) at org.apache.axis.client.Call.invoke(Call.java:1804) at iControl.SystemStatisticsBindingStub.get_global_statistics(SystemStatisticsBindingStub.java:607) at oracle.sysman.mpi.f5.bigip.SystemSwitch.getSystemSwitchInfo(SystemSwitch.java:50) at oracle.sysman.mpi.f5.bigip.SystemSwitch.acceptRequest(SystemSwitch.java:37) at oracle.sysman.mpi.f5.bigip.MetricCollection.acceptRequest(MetricCollection.java:93) at oracle.sysman.mpi.f5.bigip.MetricCollector.main(MetricCollector.java:149)
Thanks again for your time!
Don - Don_1780
Nimbostratus
Ok so I started looking at the Grid Control documentation and I found a blurb that said: " Be sure the BigIP is configured to accept iControl web services." I know it's a "no-no" but we are using the admin account for Grid Control to log in. Are we missing a config somewhere?
You guys are going to make me become a damn (no offense) programmer after all aren't you...I've been dodging this for years ;-)
Don - Don_1780
Nimbostratus
bump - I don't have a way to test the Oracle Grid Control plugin. I'll ask around and see what I can come up with.
From an iControl perspective, the only possible issue I could see is if the get_global_statistics() method in the newer version of the BIG-IP introduced a new statistics type introduced in a newer version of the SDK and the grid control plugin didn't have a proxy handler for that type, then it could cause an runtime translation error from SOAP to native types. I'll look at the sources between the two versions of your BIG-IPs and see if a new global stat type was added. If so, we'll need to get an updated version of the grid control plugin built. This is all guessing though, so it could be some other issue completely.
-Joe - Ray_Sbrusch_941
Nimbostratus
We're getting the same error and I'd like to see if there was ever resolved. We are using a guest account for grid control, and 9.4.3. BigIP. Any tips? Thanks! - Don_Givens_2232
Nimbostratus
No real solution although we came up with a work around. We gather the snmp data with a script on a linux box and then let grid control analyze the data we collect. Had to do the same for our firewall. Meanwhile I'm looking at Solarwinds Orion network monitoring and application monitoring solution. Good luck! - Kotesh_52116
Nimbostratus
Hi,
Has this issue been resolved? I am getting the same error when I am trying to BigIp Local Traffic Manager to Grid Control.
Please tell us the solution or work around.
Thanks
Kotesh - dhochste_22517
Nimbostratus
Has this issue been resolved? I just installed the BIG-IP Traffic Manager and got the following error. I can successfully log into the target server from the OEM Grid Unix server.
Text of the error given is as follows:
Failed to contact the target to be added. Following errors were received while testing the connection to the target. Update the properties accordingly, try Test Connection for testing the properties before saving.
Switch - em_error = ; nested exception is: java.net.ConnectException: Connection refused
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects
