# Introduction

On every VerneMQ node you'll find the `vmq-admin` command line tool in the release's bin directory. It has different sub-commands that let you check for status, start and stop listeners, re-configure values and a couple of other administrative tasks.

{% hint style="info" %}
`vmq-admin` works by RPC'ing into the local VerneMQ node by default. For most commands you can add a `--node` option and set values on other cluster nodes, even if the local VerneMQ node is down. \
\
To check for the global cluster state in case the local VerneMQ node is down, you'll have to go to another node though.
{% endhint %}

{% hint style="danger" %}
`vmq-admin` is a live re-configuration utility. Please note that all dynamically configured values will be reset by vernemq.conf upon broker restart. \
 Don't use this to wildly re-configure a production system without keeping track what you are doing. `vmq-admin` gives you the flexibility to test stuff and react live, but please persistent any static configuration you need in the vernemq.conf file.
{% endhint %}


---

# 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://docs.vernemq.com/1.7.1/administration/introduction.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.