How to test an SSH connection for Auvik

1. Testing from the Diagnostic Shell (Collector-Level Testing)

From the Auvik collector's diagnostic shell, you can run a built-in SSH tester to verify access to devices directly:

auvik> ssh <target_IP> <username> <password> <command>

Example:

auvik> ssh 10.0.40.1 auvik testpassword show ver  
ssh session established and authenticated  
ssh channel created  
CISCO_2801> show ver  
...  

This approach confirms whether the collector can successfully authenticate and run commands via SSH.
For more information, click here.

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

2. Testing from the In-App SSH Terminal (Auvik Dashboard)

If SSH credentials are set up correctly for your network devices in Auvik, you can also test SSH directly from the Auvik web interface:

• Navigate to the device in Auvik’s Inventory.
• Hover over Remote Management → click Terminal (this attempts an SSH session).
• For further information, click here.
• A terminal window opens. If it connects, you can interact with the device live.
• If credentials or device settings are incorrect, you'll receive an authentication or connection error.

Recommendations

• Start by troubleshooting credentials:
  Ensure SSH is enabled on the device, the correct ports are open (typically TCP/22), and Auvik has proper credentials and permissions—check under Discovery → Troubleshooting.
  For more information, click here.
• Use the diagnostic shell first:
  It provides quick, low-level SSH testing without involving the UI.
• Then validate via the in-app terminal:
  Confirms that both Auvik and your device are properly configured for SSH sessions.