Special notes
- In the dataview tables for Resource Pool Monitors, the source IP (SRCIP) is displayed as RESOURCE POOL, a device to which all resource pool monitors are attached.
- Some attributes are specific to the operating system. Consider operating system dependencies while selecting attributes for Resource Pool Monitors.
- If the error Cannot find Agent on PN Server is displayed when you try to create a Resource Pool Monitor, set pronet.apps.agent.localagentid=local agent ID in the usr/pw/custom/conf/pronet.conf file.
- The number of Stats attributes per Resource Pool Monitor type is limited to 50.
- The values reported by RPM are based on the poll frequency of the RPM and the underlying monitors. If multiple data points are available when the RPM poll frequency does not match that of the individual monitors, only the latest data point is considered. For example, if the RPM is polling at 10-minutes intervals and the underlying monitors are polling at 5-minute intervals, then the RPM considers the latest data point.
Suppose the RPM is reporting average availability. If the availability of monitor A is 100% and 100%, and that of monitor B is 0 and 100%, the RPM considers only the second data point for each monitor, that is, 100%. However, if the poll frequency of the RPM and underlying monitors was the same, then in the first poll, the availability would have been 50%, and in the second poll, it would have been 100%.
To avoid any confusion on reported values, BMC ProactiveNet recommends due consideration for setting RPM poll frequency. For wizard level-timeout during load: pronet.agent.controller.attributechoice.timeout=120. If you want to change the value of timeout for wizard side load, then set the new value, change the value on the server side's pronet.conf file, and restart the agent controller.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*