> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/home-cloud-user-manual/getting-started/device-setup/troubleshooting-ecw-ap/default-ssids.md).

# Default SSIDs

{% hint style="info" %}
**Default SSIDs (only available before ECW AP is managed by EnGenius Cloud)**

Potential known default SSID names along with potential causes/solutions: 

**EnMGMTxxxx-Initializing** 

Cause: AP is in bootup sequence.

**EnMGMTxxxx-SSID\_name>-No\_Eth**

Cause: AP does not have an Ethernet connection.

Solution: Check if the Ethernet cable is unplugged.

**EnMGMTxxxx-No\_IP**

Cause: AP cannot get an IP address from the DHCP server. Solution: Check the AP's IP address configuration.

**EnMGMTxxxx-IP\_Conflict**

Cause: AP’s IP address conflicts with another device’s IP in the same network.

Solution: Check the AP's IP address configuration.

**EnMGMTxxxx-Gateway\_ERR**

Cause: AP is unable to connect to its default gateway.

Solution: Check the AP's IP address configuration and connectivity to its default gateway.

**EnMGMTxxxx-Proxy\_ERR**

Cause: AP could not access Internet through an HTTP/HTTPS proxy.

Solution: Check the AP’s proxy configuration in Miscellaneous Settings.

**EnMGMTxxxx-DNS\_ERR**

Cause: AP could not resolve the domain name from the DNS server.

Solution: Check the AP's IP address configuration.

**EnMGMTxxxx-Cloud\_ERR**

Cause: Everything appears to work normally, but device is unable to connect to cloud server. 

Solution: Check cloud server status with EnGenius.

**EnMGMTxxxx-No\_Cloud\_Configure**

Cause: AP’s S/N has not been added to any network. 

Solution: Check whether the AP has been added in the inventory and has been added to a network.

**EnMGMTxxxx-Cloud\_Configured**

Everything is working as it should!

**EnMGMTxxxx**

Cause: An AP has never connected to the EnGenius cloud or has been factory reset.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.engenius.ai/home-cloud-user-manual/getting-started/device-setup/troubleshooting-ecw-ap/default-ssids.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.