Netprobes are greyed out in Active Console

Related topics Copied

Depending on its state, the Netprobe icon is displayed in four different colours: grey, green, amber, and red.

Problem Copied

Netprobes are greyed out in Active Console.

Possible causes Copied

• Root Cause 1: Network issue in which the connection from the Gateway to the Netprobe cannot be established.
• Root Cause 2: Netprobe is not started.
• Root Cause 3: Netprobe crashed and is still down.
• Root Cause 4: License has expired.
• Root Cause 5: No severity rules are applied to the Netprobe and its child data item.

Possible solutions Copied

In general, data items such as a Netprobe show the following icons when there is an error:

| Disconnected | | Data item where this is published from is disconnected. |

| Error | | Item has a general error. More information is available through its Properties dialog. |

| Unreachable | | Geneos components (Gateway or Netprobe) on which the data item sits (or is published from) are unreachable. Usually, this means that the host on which the component runs is unreachable. |

| License Warning | | Component’s licence is expired. |

| Rejected | | Connection to this item is rejected. |

| Suspended | | Connection to this item is temporarily suspended. |

| Waiting | | Waiting for a response from the data item. |

You can also hover over the Netprobe to see more details.

• Solution to Root Cause 1 - Network issue in which the connection from the Gateway to the Netprobe cannot be established

Check the connection from the Gateway host to the Netprobe host using telnet, ncat, cURL, or any of your preferred network tools. If you cannot connect, check with your network and sysadmin team regarding the connection issue.

[sandbox@EU-GATEWAY-HOST ~]$ telnet 152.24.55.65 7036
Trying 152.24.55.65...
Connected to 152.24.55.65.

[sandbox@EU-GATEWAY-HOST ~]$ nc -zv 152.24.55.65 7036
Ncat: Connected to 152.24.55.65:7036.

[sandbox@EU-GATEWAY-HOST ~]$ curl -v 152.24.55.65:7036
- Connected to 152.24.55.65 (152.24.55.65) port 7036 (#0)

• Solution to Root Cause 2 - Netprobe is not started

On a Windows host, check if the Netprobe service is running by going to Windows Services. The service should be running. If not, start the service. Collect the Netprobe log to investigate why the service stopped.

On Linux and other platforms, check if the Netprobe process is up by using the ps tool (for example, ps -ef | grep -ia netprobe). If you cannot see the process, go to the Netprobe directory and use the Netprobe startup script to start the Netprobe. Collect the Netprobe log to investigate why the process stopped.

[sandbox@EU-GATEWAY-HOST ~]$ ps -ef | grep netprobe.linux_64
netprobe-user 2150534 2148289 0 07:05 pts/0 00:00:00 ./netprobe.linux_64

• Solution to Root Cause 3 - Netprobe crashed and is still down

Follow the Netprobe is not started steps above and start the Netprobe. Collect the Netprobe log and the crash dump to investigate the cause of the crash.

• Solution to Root Cause 4 - License has expired If you see a No License icon, check the license validity by using the Gateway-licenceUsage plugin or the Gateway-gatewayData plugin. Please refer to License Monitoring. If the license has expired, coordinate with your Geneos admin so that they can request a new license from us (Client Services) or from the ITRS Group account manager (Sales).

• Solution to Root Cause 5 - No severity rules applied to the Netprobe and its child data items

No rules are triggered on the Netprobe component or its children, but a rule can still exist. The severity is Undefined. If you expect a certain severity (colour) on the Netprobe icon, check the rule that you created to confirm that you supplied the correct XPath.

Related articles Copied

• Geneos Icons and Colors
• Start the Netprobe on Windows
• Start the Netprobe on Linux and other platforms
• Netprobe documentation
• Why did Netprobe crash with the following message: " ERROR: NetProbe Restart Message: IMPORTANT - Contact your support provider; if supported directly by ITRS then mailto:support@itrsgroup.com (0) otherwise your usual support contact " ?
• My Gateway/Netprobe crashed, what information do I need to gather first before opening a ticket and reporting the issue to ITRS?