Netprobe unable to connect to my gateway (Self-Announcing)
Problem Copied
- Self-Announcing Netprobe starts up but is unable to connect to my Gateway.
- Self-Announcing Netprobe does not show up in my Active Console.
Possible causes Copied
- Network connectivity issue between Gateway and Netprobe.
- Self-Announcing Netprobe is disabled on the Gateway.
- Self-Announcing Netprobe limit is reached on the Gateway.
- Gateway connection details are missing or wrong secure port type is used in the Self-Announcing Netprobe setup file.
- Configuration conflict. The probe name or managed entity name specified in the Netprobe setup file is already in use by a Netprobe or managed entity in the Gateway setup file.
- Self-Announcing Netprobe token is missing in the License Daemon.
- Self-Announcing Netprobe version 5.2 or later, that is configured with a Dynamic Entities Mapping type, will not connect to a Gateway version 5.1.x or earlier.
- Self-Announcing Netprobe version is older than the minimum Netprobe version specified by the Gateway.
Possible solutions Copied
- Network connectivity issue between Gateway and Netprobe
Verify that there is no network connectivity issue between the Gateway and Netprobe hosts. You may try running ping and traceroute commands on the Netprobe host. You may also want to test connecting the gateway port, which includes an ORB debug page accessible with HTTP requests.
If the Netprobe is installed on Linux, the curl command can be used.
curl -v http://mygatewayhost.example.com:7039/orb
If the Self-Announcing Netprobe is behind a firewall, you may prefer the Self-Announcing Netprobe to initiate the connection to the chosen Gateway. To do so, the following settings must be enabled:
- enableReverseConnections in the Gateway
- requireReverseConnections in the Netprobe setup file
This is known as the reverse connection process.
Enable reverse connections:
Netprobe setup file setting:
<requireReverseConnection>true</requireReverseConnection>
- Self-Announcing Netprobe is disabled on the Gateway.
Verify that the Self-announcing probes setting is enabled on the Gateway. If not, a Self-Announced Probes disabled message will be recorded in the Netprobe and Gateway logs.
Example Netprobe log:
2021-08-02 12:43:06.502-0400 INFO: SelfAnnouncing Connected to Gateway nysupsvr10:61161
2021-08-02 12:43:06.603-0400 INFO: SelfAnnouncing Gateway GW2-klee-SSL_64 (nysupsvr10:61161) will not accept Self-Announcing probe: Self-Announced Probes disabled for this gateway
Example Gateway log:
2021-08-02 12:47:06.336-0400 INFO: SelfAnnouncingProbeManager Connection received from Self-Announcing Netprobe nysupsvr21.ny.us.itrs:51141
2021-08-02 12:47:06.337-0400 INFO: SelfAnnouncingProbeManager Not accepting self announced probe. This feature has been disabled in GW config.
2021-08-02 12:47:06.337-0400 INFO: SelfAnnouncingProbeManager Sending data to Self-Announcing Netprobe 'SelfAnnouncing-nysupsvr21.ny.us.itrs-51141-autodiscovery' nysupsvr21.ny.us.itrs:51141: Will not accept probe. 'Self-Announced Probes disabled for this gateway'
Self-Announcing Enabled setting:
- Self-Announcing Netprobe limit is reached on the Gateway.
Increase the number defined in Self-announcing probes > Probe limit on the Gateway. If the limit is reached, a Self-Announced Probe Limit reached message will be recorded in the Netprobe and Gateway logs. For more details, see Probe limit.
Example Netprobe log:
2021-08-02 13:25:49.633-0400 INFO: SelfAnnouncing Connected to Gateway nysupsvr10:61161
2021-08-02 13:25:49.734-0400 INFO: SelfAnnouncing Gateway GW2-klee-SSL_64 (nysupsvr10:61161) will not accept Self-Announcing probe: Self-Announced Probe Limit reached
Example Gateway log:
2021-08-02 13:25:49.706-0400 INFO: SelfAnnouncingProbeManager Connection received from Self-Announcing Netprobe nysupsvr21.ny.us.itrs:51143
2021-08-02 13:25:49.706-0400 INFO: SelfAnnouncingProbeManager Not accepting self announced probe. Limit reached (probe connected 2, probe limit 2)
2021-08-02 13:25:49.707-0400 INFO: SelfAnnouncingProbeManager Sending data to Self-Announcing Netprobe 'SelfAnnouncing-nysupsvr21.ny.us.itrs-51143-autodiscovery' nysupsvr21.ny.us.itrs:51143: Will not accept probe. 'Self-Announced Probe Limit reached'
Probe limit setting:
- Gateway connection detail is missing or wrong secure port type is used in the Self-Announcing Netprobe setup file.
Verify the Gateway connection details and ensure it is defined correctly in the Self-Announcing Netprobe setup file.
Check for any typos in the hostname, port and secure type for the Gateway connection. Ensure the Self-Announcing Netprobe is not trying to connect insecurely to a secure Gateway port. Or the Self-Announcing Netprobe is not trying to connect securely on an insecure Gateway port.
- Configuration conflict. The probe name or managed entity name specified in the Netprobe setup file is already in use by a Netprobe or managed entity in the Gateway setup file.
If the probe or managed entity name specified in the Netprobe setup file is already in use by another probe or managed entity on the Gateway, then an already exists info message indicating such name is already in use will be recorded in both the Netprobe and Gateway logs. To address the issue, update the configuration to ensure the name is unique across the Gateway.
Example messages when same probe name is in use:
Netprobe log:
2021-08-15 11:00:18.415-0400 INFO: SelfAnnouncing Gateway GW2-klee-SSL_64 (nysupsvr10:61161) will not accept Self-Announcing probe: **Probe** SelfAnnouncing-51145 **already exists**.
Gateway log:
2021-08-15 11:00:18.369-0400 INFO: SelfAnnouncingProbeManager Sending data to Self-Announcing Netprobe 'SelfAnnouncing-51145' nysupsvr21.ny.us.itrs:51145: Will not accept probe. '**Probe** SelfAnnouncing-51145 **already exists**.'
Example messages when same managed entity name is in use:
Netprobe log:
2021-08-15 11:33:09.341-0400 INFO: SelfAnnouncing Gateway GW2-klee-SSL_64 (nysupsvr10:61161) will not accept Self-Announcing probe: **ManagedEntity** SelfAnnouncing-nysupsvr21-51145 **already exists** on probe 'nysupsvr21_ga590_51170'
Gateway log:
2021-08-15 11:33:09.252-0400 INFO: SelfAnnouncingProbeManager Sending data to Self-Announcing Netprobe 'SelfAnnouncing-51145' nysupsvr21.ny.us.itrs:51145: Will not accept probe. **'ManagedEntity** SelfAnnouncing-nysupsvr21-51145 **already exists** on probe 'nysupsvr21_ga590_51170'.'
- Self-Announcing Netprobe token is missing in the License Daemon.
If the License daemon is missing the Self-Announcing Netprobe token then the Gateway won’t be able to add any Self-Announcing Netprobe connections. A Self Announcing Probes feature not licensed message will be recorded in the Netprobe and Gateway logs.
Example Netprobe log:
2021-08-04 15:06:22.128-0400 INFO: SelfAnnouncing Connected to Gateway nysupsvr10:61161
2021-08-04 15:06:22.229-0400 INFO: SelfAnnouncing Gateway GW2-klee-SSL_64 (nysupsvr10:61161) will not accept Self-Announcing probe: **Self Announcing Probes feature not licensed**
Example Gateway log:
2021-08-04 15:06:22.129-0400 INFO: SelfAnnouncingProbeManager Connection received from Self-Announcing Netprobe nysupsvr21.ny.us.itrs:51141
2021-08-04 15:06:22.129-0400 INFO: SelfAnnouncingProbeManager Sending data to Self-Announcing Netprobe 'SelfAnnouncing-nysupsvr21.ny.us.itrs-51141-autodiscovery' nysupsvr21.ny.us.itrs:51141: Will not accept probe. '**Self Announcing Probes feature not licensed**'
You can verify if the self-announcing-probes token is available by connecting to the License Daemon http(s)://LicenceDaemonIPAddress:7041/licensing/. If it is missing, please raise a ticket so we may follow up with your ITRS account manager for approval to update the license.
- Self-Announcing Netprobe version 5.2 or later, that is configured with a Dynamic Entities Mapping type, will not connect to a Gateway version 5.1.x or earlier.
Upgrade the Gateway and Licence Daemon to the same version or later than GA5.2. Otherwise, a failed connection will be recorded in the Netprobe log, with a warning that the Gateway version is too old.
- Self-Announcing Netprobe version is older than the minimum Netprobe version specified by the Gateway.
Adjust the setting if needed in the Gateway > Operating environment > Connections > Client connection requirements > Minimum component version. For more details, see Operating Environment
Example gateway log:
2021-08-14 21:29:06.821-0400 INFO: **OperatingEnvironment Netprobe rejected because older than version** 'GA5.9.0'. Version:GA5.8.2-210629 Host:nysupsvr21.ny.us.itrs (192.168.2.33)
For more information, see Manage Self-Announcing Netprobes and Netprobe Troubleshooting.