Forum Discussion
PT_Inova__231__
Nimbostratus
NimbostratusBIG-IP LTM does not appear on Agent add target combo box
Hi,
I am trying to setup the plug-in in a test platform.
The version of OEM is OEM 11g R1 11.1.0.1.0 and I went to preferences and setup the preferred credentials to the specific agent. I have used the credentials for the same user which runs the agent ->"oracle".
Then imported the plug-in, and deployed on the specific agent. Apparently there were no errors on the deploy.
When I go to the agent homepage, there is no "BIG-IP Local Traffic Manager" option.
And I have no files inside %scriptsDir%/emx/f5_bigip_v9plus_loadbalancer/, wich are pointed by OSLineToken FetchLets. But the directory exists.
Did a bounce on the agent and got a warning about parsing the default_collection in the logs, and so I have corrected the typos in lines 229 and 279 passing "HR" to "Hr".
Bounced the agent again, still no luck about getting the entry in the combo box.
In the installation guide, what are "correct privileges"?
---Preferred credentials are set on all Agents where you want to deploy the plug-in. Unless you assign correct privileges, the deployment will fail.
PT_Inova__231__
Hi,
When I come back from lunch, re-entered in Oracle EM OMS GUI, and when went to the Agent, the BIG IP was now available.
I have already added instances, and it look OK. Now I have to take a look to all these metric collection errors.... like these:em_error = 10.111.71.137%1714 java.net.UnknownHostException: 10.111.71.137%1714 at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:849) at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1200) at java.net.InetAddress.getAllByName0(InetAddress.java:1153) at java.net.InetAddress.getAllByName(InetAddress.java:1083) at java.net.InetAddress.getAllByName(InetAddress.java:1019) at java.net.InetAddress.getByName(InetAddress.java:969) at oracle.sysman.mpi.f5.bigip.VirtualServerConfig.getVSInfo(VirtualServerConfig.java:98) at oracle.sysman.mpi.f5.bigip.VirtualServerConfig.getAllVSInfo(VirtualServerConfig.java:59) at oracle.sysman.mpi.f5.bigip.VirtualServerConfig.acceptRequest(VirtualServerConfig.java:48) at oracle.sysman.mpi.f5.bigip.MetricCollection.acceptRequest(MetricCollection.java:107) at oracle.sysman.mpi.f5.bigip.MetricCollector.main(MetricCollector.java:123)- On the surface it appears that somehow the hostname for the BIG-IP was entered as 10.111.71.137%1714 rather than 10.111.71.137 ???
Is this happening for all metrics or just some?
If you go to target -> All Metrics (bottom in related links) -> Nodes (for example), do you see good data?
