I need your help with the SNMPCOLLECTOR probe.
We have a client, with 6 thousand devices that will be monitored in this test.The Client is in another country, therefore, through our architecture we will use tertiary hubs (TIER-III)
The architecture reads as follows:
Core NMS (Brazil)Intermediate Hub (Argentina)Customer Hubs (Peru)
Core NMS> VPN> Intermediate Hub> VPN> Customer Hub in Peru.
Each server has 8GB of RAM and 4VCPU.Consumption is low. You do not have any equipment added yet in monitoring.
The probe has been successfully installed and does not have any add-on equipment yet.
However, the probe takes 30 minutes to load into adminconsole.This is normal? Does this probe work on TIER-III?The probe takes 30 minutes on average to perform any operation, from loading how much to open the template editor.
The probe has RAW memory set to 6144mb of RAM.
I already deployed an adminconsole in the intermediate hub. We continue with 30 minutes for the probe to load.
Is there a solution for this case?
If this is a UIM 8.51 environment, make sure that you have downloaded the mps_webapp-8.5.1_HF1.zip package from the CA UIM Hot Fix Index site to a temporary directory on your primary hub, imported the package into the local archive on your primary hub, then deployed the 8.51 mps package to all of the hubs where you have deployed the adminconsoleapp package. Restart the Admin Console wasp probe after deploying this package. This mps hot fix contains a fix to improve performance opening Admin Console based probe GUIs.
Thanks for this tip.
Everything is OK now!
The probe opened in only 2 minutes.