---
title: "How to troubleshoot swx-top"
slug: "troubleshooting-swx-top"
updated: 2025-12-23T14:58:42Z
published: 2025-12-23T14:58:42Z
canonical: "docs.swxtch.io/troubleshooting-swx-top"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.swxtch.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How to troubleshoot swx-top

**WHAT TO EXPECT**

**In this article**, users will learn how to troubleshoot swx-top issues.

1. **If the swx-top "Status" is showing that there is a "Connection error:"**
  1. Check that the cloudSwXtch is started.
  2. Check that you entered the proper cloudSwXtch name or IP when running the swx-top command, if necessary.
  3. If the name does not work when running the swx-top command, then the DNS is not set up correctly; use the IP address instead.
2. **If an xNIC was installed but is not showing up in swx-top:**
  1. Navigate to the swxtch-nic.conf file and validate that the "SwxtchSvcAddr" is correct.
    - Windows can be found at "C:\Program Files\SwXtch.io\Swxtch-xNIC"
    - Linux can be found at "/var/opt/swxtch/swxtch-xnic.conf"
  2. Check that the firewall is open for the following ports:

| subnet | protocol | ports | vm |
| --- | --- | --- | --- |
| ctrl-subnet | tcp | 80 | cloudSwXtch |
| ctrl-subnet | udp | 10800-10803 | all |
| data-subnet | udp | 9999 | all |

1. **If a multicast group is not showing up, then check that they have registered.**
  - **In Linux**, run this command:

Text

```shell
ip maddress show
```
  - **In Windows**, run this command in PowerShell:

```shell
netsh.exe interface ipv4 show joins
```
  - If the joins are not showing here, then the application is not joining the multicast group. In this case, run swxtch-perf for the same IP:Port combination and then re-try in the program.
  - If the joins are not showing here, then the application is not joining the multicast group. In this case, run swxtch-perf for the same IP:Port combination and then re-try in the program.
  - If using Windows, make use of Task Manager and view Performance to know where data is being sent/received.
  - Validate using TCPdump or Wireshark to identify where traffic is going, as it could be going to the wrong network interface; it should be going to the Data Interface if xNIC2 and swx0 if xNIC is Type 1 or 3. An example is below:

```shell
$ sudo tcpdump udp -X -i <interface>
```

**PLEASE NOTE**

xNIC Type 1 and Type 3 interface: `swx0` xNIC2 interface: data nic (usually `eth1 or ens6 for Linux, and "Ethernet 2" for Windows`)

- Validate that a firewall is not stopping the multicast and open up the firewall to include port exceptions.