Troubleshoot > Troubleshooting Data Flow Management > Troubleshooting and Limitations

Troubleshooting and Limitations – Data Flow Probe Setup

Data Flow Probe Setup - Troubleshooting

Data Flow Probe Setup - Limitations

  • Limitation: The Probe cluster range distribution purely handles the potential number of active or inactive IP addresses available in its network range, not the actual number of IP addresses populated or the number of devices available inside those ranges. For example, You have 100 IP addresses, and Probe cluster distributes them into two Probes: 50 IP addresses to one Probe and 50 IP addresses to the other Probe. If only one IP address is active on Probe A and 50 IP addresses are active on Probe B, Probe B would take a disproportional share of the load.

    Reason: The actual number of IP addresses are unavailable before the actual discovery.

    Workaround: If many IP ranges are unevenly populated, in order to have full control of the IP address distribution, it is best to avoid using the Probe cluster feature and simply use Probes separately.

  • When the Probe is running in separate mode on a machine where both the Gateways and the Manager share a same installation folder, the Data Flow Probe CUP must be installed manually. For details, see How to Deploy a Data Flow Probe CUP Manually.

  • Data Flow Probe CUPs that were deployed manually can be uninstalled using manual methods only. For details, see How to Uninstall Probe CUPs Manually.

  • Universal Discovery Agent may not callhome in, but not limited to, the following scenario:

    • The callhome IP address that is configured on the Universal Discovery Agent belongs to a client type range that is added to a cluster.

      Note The Universal Discovery Agent supports 1 primary and 1 secondary probe.

    • The range is a member of a probe cluster.
    • The cluster contains two or more probes.

    In this scenario, callhome may not work as expected. Contact Support for assistance in configuring callhome.