×
![]()
Rejection reasons
Floating Netprobes Copied
Gateways may refuse to accept a floating Netprobe for the following reasons:
- The probe name is not configured as a
floatingProbein the Gateway setup. - A probe under the required name is currently connected to the Gateway.
- Probe has been configured to require a reverse connection, but the Gateway does not support that feature.
- Probe is trying to connect insecurely on a secure Gateway port.
- Probe is trying to connect securely on an insecure Gateway port.
For more information on how to set up a floating Netprobe, see Manage floating Netprobes.
Self-Announcing Netprobes Copied
Gateways may refuse to accept a Self-Announcing Netprobe for the following reasons:
- The probe name specified in the Netprobe setup file is already in use by a Netprobe specified in the Gateway Setup File.
- The Managed Entity name specified in the Netprobe setup file is already in use by a Managed Entity specified in the Gateway setup file.
- The Gateway is an inactive (secondary) Gateway in a hot-standby pair.
- Self-Announcing Netprobe is disabled on the Gateway.
- The Gateway has reached its Self-Announcing Netprobe limit.
- Netprobe has been configured to require a reverse connection but the Gateway does not support that feature.
- Netprobe is trying to connect insecurely on a secure Gateway port.
- Netprobe is trying to connect securely on an insecure Gateway port.
For more information on how to set up a Self-Announcing Netprobe, see Manage Self-Announcing Netprobes.
Managed entity variables Copied
The Self-Announcing Netprobe can set a list of user-defined variables to be created on the Managed Entity.
In the following scenarios, the Gateway will ignore these variables and report an error in both the Gateway and Netprobe logs.
- If a variable of any password type is set in the Netprobe setup file. For example:
<var name="var_stdAESPassword">
<stdAESPassword>
<stdAES>+encs+CFB98A43AD52E4D2772030514B49B906</stdAES>
</stdAESPassword>
</var>
Netprobe log:
ERROR: SelfAnnouncing Message from gateway '<PROBENAME>' (<HOST:PORT>): var_stdAESPassword ignored, as Self Announcing Probes do not support stdAESPassword variable type.
Gateway log:
ERROR: DirectoryManager var_stdAESPassword ignored, as Self Announcing Probes do not support stdAESPassword variable type. [/variables[@disabled!="true"][1]/var[@disabled!="true"]
- If a variable of type
activeTimerefers to an active time that does not exist. For example:
<var name="var_ActiveTime">
<activeTime>
<activeTime ref="Nonexistent"> </activeTime>
</activeTime>
</var>
Netprobe Log:
ERROR: SelfAnnouncing Message from gateway '<PROBENAME>' (<HOST:PORT>): Variable var_ActiveTime ignored, because ActiveTime 'Nonexistent' does not exist.
Gateway Log:
ERROR: DirectoryManager Variable var_ActiveTime ignored, because ActiveTime 'Nonexistent' does not exist. [/variables[@disabled!="true"][1]/var[@disabled!="true"]
- If there is a parse error in the variables section, Gateway and Netprobe will report the error, and the variable will not be set.
["Geneos"]
["Geneos > Netprobe"]
["User Guide"]