What Does the AP Status LED Indicate?
LED Blink Patterns for AP States
A Juniper Access Point (AP) has one multicolor status LED that indicates the operational state of the AP. The LED uses a series of blink patterns that help you assess the status of an AP or determine any issues such as network or cloud connectivity issues. Use the information in the following sections to understand what the blink patterns indicate.
|
LED Color |
Blink Pattern |
AP Status |
|---|---|---|
|
|
Blinking red for 3 seconds |
The AP is starting to boot. |
|
|
Blinking green-off-yellow-off for 12 seconds |
The AP is booting. |
|
|
Blinking green and yellow for 30–40 seconds |
The AP is connecting to the Juniper Mist cloud. |
|
|
White steadily on |
The AP is connected to the cloud. |
|
|
Green steadily on |
The AP is configured by the Juniper Mist cloud. |
|
|
Blue steadily on |
The AP has at least one wireless client connected to it. |
|
|
Blinking orange |
The AP is upgrading. |
|
|
Blinking green and purple |
The status LED blinks green and purple when the user clicks the Locate button in the Access Point details page. |
|
|
Red steadily on |
The AP has failed. |
|
|
Gradually progresses to red |
The user is holding down the Reset button. |
|
|
White gradually fades to off |
The AP is going to reset the configuration to the factory default. |
|
|
Green gradually fades to off |
The AP is receiving insufficient power. |
LED Blink Patterns for Network Connectivity Errors
|
LEDs |
Blink Pattern |
Error |
Description |
|---|---|---|---|
|
|
2 yellow |
No ethernet link |
The AP does not have an Ethernet link. This error is usually seen if you did not connect the AP to a switch when using a power injector. |
|
|
3 yellow |
No IP Address |
There is no IP address in the static configuration or through the DHCP lease. |
|
|
4 yellow |
No default gateway |
Neither the static configuration nor the DHCP lease has a default gateway. |
|
|
5 yellow |
Default gateway unreachable |
The AP does not receive an ARP response from the default gateway. |
|
|
6 yellow |
No DNS |
Neither the static configuration nor the DHCP lease has a DNS server. |
|
|
7 yellow |
No DNS response |
The AP did not receive a response to the DNS lookup. The AP receives the DNS server information through DHCP but the AP is unable to reach the Mist cloud. |
|
|
8 yellow |
Empty DNS response |
The AP received an empty DNS response with no address records. |
|
|
9 yellow |
Duplicate IP Address |
The AP has detected a duplicate IP address on the LAN (ARP probes). |
LED Blink Patterns for Cloud Connectivity Errors
| LEDs | Blink Pattern | Error | Description |
|---|---|---|---|
|
|
1 yellow, pause, 2 yellow |
Cloud unreachable |
TCP SYN fails and the AP cannot ping ep-terminator. |
|
|
1 yellow, pause, 3 yellow |
No cloud response |
The AP did not receive a response from the cloud. |
|
|
1 yellow, pause, 4 yellow |
Cloud cert time check failed |
NTP Time is not within cert's not-before/not-after times. |
|
|
1 yellow, pause, 5 yellow |
Cloud cert invalid |
The cloud provided an invalid certificate during authentication. |
|
|
1 yellow, pause, 6 yellow |
Mutual auth failed |
Mutual authentication between the AP and the Juniper Mist cloud failed. |
|
|
1 yellow, pause, 7 yellow |
Config fetch failed |
The Juniper Mist cloud is unable to push the configuration to the AP. |
|
|
1 yellow, pause, 8 yellow |
Invalid configuration |
The Juniper Mist cloud provided an invalid configuration. |
|
|
1 yellow, pause, 9 yellow |
Boot config save failed |
The AP was unable to save or delete the boot configuration. |
LED Blink Patterns for Layer 2 Tunneling Protocol (L2TP) Management Errors
| LEDs | Blink Pattern | Error | Description |
|---|---|---|---|
|
|
2 yellow, pause, 1 yellow |
L2TP mgmt tunnel peer unreachable |
The start control connection request (SCCRQ) failed and the L2TP management server is unreachable. |
|
|
2 yellow, pause, 3 yellow |
No response from L2TP mgmt tunnel peer |
The L2TP management server is reachable but it does not send a response to SCCRQ. |
|
|
2 yellow, pause, 4 yellow |
L2TP mgmt tunnel config rejected |
The L2TP management server credentials failed. The SCCRQ returns a StopCCN message instead of start control connection reply (SCCRP). |
|
|
2 yellow, pause, 5 yellow |
L2TP mgmt tunnel stopped |
The L2TP management server sent a StopCCN and terminated the tunnel. |
|
|
2 yellow, pause, 6 yellow |
L2TP mgmt session config rejected |
The L2TP management server sent a CDN in response to ICRQ. |
|
|
2 yellow, pause, 7 yellow |
L2TP mgmt session shutdown |
The L2TP management server sent a CDN and terminated the session. |
LED Blink Patterns for L2TP Connectivity Errors
| LEDs | Blink Pattern | Error | Description |
|---|---|---|---|
|
|
3 yellow, pause, 1 yellow |
L2TP DHCP no response |
The AP did not receive a response to the DHCP discover message over the L2TP tunnel. |
|
|
3 yellow, pause, 2 yellow |
L2TP default gateway missing |
The DHCP offer message does not have a default gateway. |
|
|
3 yellow, pause, 4 yellow |
L2TP default gateway unreachable |
The default gateway does not send an ARP response. |
|
|
3 yellow, pause, 5 yellow |
L2TP mgmt DNS missing |
The DHCP offer message does not contain any DNS servers. |
LED Blink Patterns for Boot Configuration Errors
| LEDs | Blink Pattern | Error | Description |
|---|---|---|---|
|
|
4 yellow, pause, 1 yellow |
Boot config unreadable |
The boot configuration file is unreadable. |
|
|
4 yellow, pause, 2 yellow |
Boot config invalid |
The boot configuration is invalid. |
|
|
4 yellow, pause, 3 yellow |
Boot config failed |
The boot configuration failed and the AP has lost connection to the cloud. |
LED Blink Patterns for Firmware and Other Errors
| LEDs | Blink Pattern | Error | Description |
|---|---|---|---|
|
|
5 yellow, pause, 1 yellow |
Firmware corrupt |
The firmware image is corrupted. |
|
|
5 yellow, pause, 2 yellow |
Unexpected failure |
An API failed unexpectedly. |
LED Blink Patterns for Proxy Server Errors
| LEDs | Blink Pattern | Error | Description |
|---|---|---|---|
|
|
6 yellow, pause, 1 yellow |
Proxy config invalid |
The proxy configuration is invalid. |
|
|
6 yellow, pause, 2 yellow |
Empty DNS response to proxy host lookup |
The AP received an empty DNS response with no A (address) records for the proxy host. |
|
|
6 yellow, pause, 3 yellow |
Proxy is unreachable |
The proxy server is unreachable. |
|
|
6 yellow, pause, 4 yellow |
No proxy server response |
The proxy server is reachable but the AP is unable to connect to the proxy TCP port. |
|
|
6 yellow, pause, 5 yellow |
Proxy Authentication Required |
Proxy authentication is required (code 407). |
AP Status LED Video Demo
In this demo, you'll see how you can use the LED blink pattern to identify issues.
The Mist access point has a single LED to indicate status. Let's walk through several boot configurations and look at three different errors. Flashing red indicates the AP is starting, and then the yellow alternating is the AP boot sequence. We're going to speed things up a bit here to show three common error scenarios.
Now the AP is trying to talk to the cloud and it fails. It'll start blinking indications to tell you what's wrong 112112. Now if we go to our CHEAT SHEET, we'll notice that 112 is cloud unreachable. So I was able to get out on the Internet, tried to connect to the cloud, even tried to ping the Terminator and was unsuccessful.
Now, in this case, the AP is booting up. We've sped this up for video's sake, and when we get to about the 52nd mark, we go into the failure mode. We're going to see it blink three times, and again three times. And when we look at the CHEAT SHEET, #3, no IP address, so the DHCP server didn't respond.
Something easy to go look for. And the last case it was a case that this was a closed network 123-4567 again, you'll see it's going to blink out seven. So if we look at 7, no DNS response. In this case, it was a private network just for IP phones and there was no interconnection at all.
Here's the good things that you would see if you were connected to the cloud. Obviously, blue clients are connected.