Diagnose issues using discovery scanning with the Auvik collector?

The Auvik collector is equipped with a Linux shell that can capture data about your network, devices, or collector to help Auvik diagnose issues.

If you run any of the following commands, send the resulting information to Auvik support for data analysis, or include it on a support ticket that needs follow-up or resolution.

Access the diagnostic shell on the Auvik Collector

• Windows:
  • Launch Command Prompt as Administrator.
  • Navigate to the install directory, e.g., cd C:\auvik.
  • Run:

    AuvikAgentService -shell

• Linux/Docker:
  • With Docker Compose:
    • From the host machine, open a terminal window
    • Change directories to the location of the Docker compose configuration file

    • Run the following command to start the agent shell, replacing <SERVICE_NAME> with the service name defined within the Docker compose file:

      docker compose exec -it <SERVICE_NAME> /var/auvik/bin/agent -x

      Note: The <SERVICE_NAME> will be dependent on the deployment configuration. The service name will be based on the entry within the Docker compose file, specifically under the services section.

  • Standalone Docker:If your Docker image was not deployed using Docker compose, or you do not have access to the Docker compose configuration, then the following Docker commands can be used to start an agent shell process.From the host machine, open a terminal window

    • Run the following Docker command:

      docker exec -it <container_name_or_id> /var/auvik/bin/agent -x

      Note: The <container name/id> will be dependent on the deployment. If using Docker compose for the deployment, this will be the container_name used in the docker-compose.yaml file.
      
      If no name was specified during the configuration, a Docker will set a default name. This can be found using Docker ps command to list all running containers. Once the correct container has been identified, the container id OR the container name can be used in the above command.  Failure to keep the Docker image up to date can cause the collector to fail with these updates, causing instability and disconnects.

• Virtual Collector:
  • Open the collector’s VM console via your hypervisor.
  • At the menu, select Option 6, then confirm with Y—this drops you into the bash shell.
  • Run this command

    sudo /usr/share/agent/bin/agent_shell

Where are all the devices?

Things to be answered with these diagnostics: What does the health check ping say about this device? Does it find the device? If so, what is the ping latency? If it doesn’t find the device, it's unlikely the Auvik collector will find the device no matter what we do.

Pick a device with a known IP address that you know is currently online. Next, try a scan of the subnet from the diagnostic shell. This will serve as a baseline for scan performance.

scan <ip> <subnet>

ping <ip>

portOpen <ip> <port>

portScan <ip> <port>

For example:

auvik > scan 10.0.40.0 24
       Scan result for 10.0.40.0/24
       10.0.40.1
       10.0.40.110
       10.0.40.123
       10.0.40.198
auvik > ping 10.0.40.110
       10.0.40.110 responded to ping
auvik > portOpen 10.0.40.110 80
       10.0.40.110:80 port is not open
auvik > portScan 10.0.40.110 80
       No ports found to be open

Try repeating the scan a couple of times to see if hosts magically start appearing. Contact Auvik support for further analysis of what you’re seeing.

Is a scan killing the network?

There are two parameters that control how fast Auvik sends out ICMP packets:

ScanService.max-simultaneous-ping

ScanService.simultaneous-send-delay

Both default to 10, meaning we send at most 10 packets within any particular 10ms window. Increasing the delay or decreasing the maximum number of sends will slow the scan down.

Other troubleshooting

If you need help troubleshooting SNMP, click here.

If you need help testing SSH, click here.

If you need help testing HTTP, click here.