# Troubleshooting

Use these steps if the sensor stops reporting to the console.

***

### 1. Reboot the sensor

Reboot the sensor first.

If the sensor still does not report, continue with the checks below.

***

### 2. Verify outbound connectivity

Confirm the sensor can reach these domains on `TCP/443`:

* `tele.threatdefence.io`
* `vle.us.secops-apps.io`

Make sure SSL/TLS inspection is disabled or bypassed for both domains.

Run these commands on the sensor and capture the output:

* `nc -vz tele.threatdefence.io 443`
* `nc -vz vle.us.secops-apps.io 443`

***

### 3. Restart the sensor services

Run these commands:

* `systemctl restart siemlink.service`
* `systemctl restart teleport`

***

### 4. Confirm mirrored traffic is present

Run this command:

* `sudo tcpdump -i eth1`

If you only see ARP traffic, the mirror or SPAN port is not configured correctly.

Check that the mirror points to the internal firewall port.

***

### 5. Check storage capacity

High packet volume can fill storage and cause packet drops.

If storage is low, increase disk space on the sensor.

***

### 6. Contact support

If the issue persists, contact <socv2@cybrhawk.com>.

Include screenshots or command output for:

* `systemctl restart siemlink.service`
* `systemctl restart teleport`
* `ip a`
* `ip -br a`
* `ping 1.1.1.1`


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cybrhawksoc.gitbook.io/cybrhawk-docs/appliances/network-sensor/troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.