|
Off |
The AP is not receiving power. |
-
Check whether the switch port connected to the AP learns the
MAC address of the AP.
-
Check the power logs on the AP to verify that PoE is enabled
on the switch port.
-
Check whether the switch is supplying power to the AP. Change
the cable and the switch port to see whether the AP powers
on.
-
If you have a working AP, swap it with the faulty AP. Check
whether the issue persists.
Note:
If your APs are already installed and you cannot swap any
AP, skip this step.
|
|
Blinking green and yellow for more than 30 seconds |
The AP is trying to connect to the Juniper Mist™ cloud but is unable
to connect. |
-
Verify that the relevant ports are open on the firewall. See
Firewall
Configuration.
-
Connect a laptop to the same switch port as the AP. Open
https://ep-terminator.mistsys.net/about and see if it resolves
the host.
Your output should look like this:
{
"version": "0.3.4476",
"git-commit": "0db544d97d09c21dd2ea0778c1f6d03465861c9d",
"build-time": "2020-03-16_23:45:06_UTC",
"go-runtime": "go1.14",
"env": "production",
"procname": "ep-terminator/🌧/provider=aws/env=production/host=ep-terminator-172-31-16-17-762f638f-production.mistsys.net/pid=12226/user=terminator",
"start-time": "2020-03-19T01:32:54Z",
"uptime": 707675.367648
}
-
Check the firewall logs to see whether any policy is blocking
the https://ep-terminator.mistsys.net/about URL.
|
|
Blinking yellow two times |
The switch or AP is experiencing a Layer 2 issue. |
-
Run a cable test to verify that the cable connected to the AP
is working correctly.
-
Check whether the switch port connected to the AP learns the
MAC address of the AP.
-
Check for any eth0 errors on the switch port.
-
Change the cable and switch port and verify that the AP
powers on.
-
If you have a working AP, swap it with the faulty AP. Check
whether the issue persists.
Note:
If your APs are already installed and you cannot swap any
AP, skip this step.
|
|
Blinking yellow three times |
The AP is unable to obtain an IP address. |
The AP can obtain an IP address either through DHCP or through a
static configuration.
Troubleshooting steps for DHCP:
-
Check whether the switch port configuration has the required
parameters (such as native VLAN and VLAN ID) configured.
-
Check the DHCP server logs to verify that leases are
available in the DHCP pool.
-
Connect a laptop to the switch port to which the AP was
connected. Verify that the laptop is able to obtain an IP
address from the VLAN management pool.
-
If the laptop is unable to obtain an IP address,
contact the DHCP team to fix the DHCP pool. You can
port-mirror the switch port to identify which step
in the DHCP Discover, Offer, Request, Acknowledgment
(DORA) process is failing.
-
If your laptop is able to obtain an IP address
whereas the AP is unable to obtain an IP address,
contact the Juniper support
team.
Troubleshooting steps for static configuration:
If the AP was connected to the Juniper Mist cloud earlier, check the
static configuration on the Juniper Mist portal. If the static
configuration is incorrect, then the AP will not be able to connect
to the Juniper Mist cloud. To correct the static configuration:
-
Power off the AP by shutting down the PoE on the switch
connected to the AP. Alternatively, you can remove the
physical cable that provides power to the AP.
-
Correct the configuration on the switch port.
-
Reset the AP to the factory-default configuration. See Reset an Access Point to the Factory-Default Configuration.
-
Power on the AP.
|
|
Blinking yellow four times |
No default gateway IP address found in the DHCP lease or static
configuration. |
-
Check the DHCP pool configuration to see whether the default
gateway is configured.
-
If you've configured a static IP address for the AP, check
whether the default gateway is configured correctly.
If the default gateway is not configured correctly, follow
these steps:
-
Power off the AP by shutting down the PoE on the
switch port to which the AP is connected.
Alternatively, you can remove the physical cable
that provides power to the AP.
-
Correct the configuration on the switch port.
-
Reset the AP to the factory-default configuration.
See Reset an Access Point to the Factory-Default Configuration.
-
Power on the AP.
-
Perform port mirroring for the switch port and obtain the
packet capture. In the DHCP offer packet from the server,
check whether the default gateway
field displays an IP address.
-
If the default gateway field
does not display an IP address, contact your DHCP
server team to fix the configuration on the DHCP
server.
-
If the default gateway field
displays an IP address, contact Juniper Mist support
to troubleshoot the issue.
|
|
Blinking yellow five times |
The default gateway IP address is configured but the AP is unable to
connect to the default gateway. |
-
Verify that the default gateway IP address is set correctly
in all the configurations on the switch port (VLAN, native
VLAN) and the DHCP pool configuration.
-
If you've configured a static IP address for the AP, check
whether the default gateway is configured correctly.
If the default gateway is not configured correctly, follow
these steps:
-
Power off the AP by shutting down the PoE on the
switch port to which the AP is connected.
Alternatively, you can remove the physical cable
that provides power to the AP.
-
Correct the configuration on the switch port.
-
Reset the AP to the factory-default configuration.
See Reset an Access Point to the Factory-Default Configuration.
-
Power on the AP.
If the configuration is correct and the LED still blinks
yellow five times, follow these steps:
-
Connect a laptop on the same VLAN, network, or switch
port to which the AP was connected.
-
Ping the default gateway. Use the ipconfig
/all command to get the default gateway
information.
If the ping fails, contact your network administrator
to check for issues on the wired side.
If the ping succeeds but the AP still fails to
connect, contact Juniper Mist support.
|
|
Blinking yellow six times |
No DNS IP address found in the DHCP lease or static
configuration. |
-
Check the DHCP pool configuration to see whether the DNS
server is configured.
-
If you've configured a static IP address for the AP, check
whether the DNS server is configured correctly.
If the DNS server is not configured correctly, follow these
steps:
-
Power off the AP by shutting down the PoE on the
switch port to which the AP is connected.
Alternatively, you can remove the physical cable
that provides power to the AP.
-
Correct the configuration on the switch port.
-
Reset the AP to the factory-default configuration.
See Reset an Access Point to the Factory-Default Configuration.
-
Power on the AP.
-
Perform port mirroring for the switch port and obtain the
packet capture. In the DHCP offer packet from the server,
check whether the dns server field
displays an IP address.
-
If the dns server field does
not display an IP address, contact your DNS server
team to fix the configuration on the DNS server.
-
If the dns server field
displays an IP address, contact Juniper Mist support
to troubleshoot the issue.
|
|
Blinking yellow seven times |
The DNS server does not respond to a DNS lookup. The AP receives the
DNS server through DHCP but it cannot reach or ping the Juniper Mist™
cloud. When the AP gets an IP address from the DHCP server, the AP tries
to reach ep-terminator.mistsys.net. If the DNS server
is unable to resolve this URL, the AP cannot connect to the
cloud. |
-
Connect a laptop on the same VLAN or network, and try to
resolve the URL ep-terminator.mistsys.net
to an IP address by executing the nslookup
command at the command prompt.
C:\Users\username>nslookup ep-terminator.mistsys.net
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: ep-term-production-1584483204-1989267174.us-west-1.elb.amazonaws.com
Addresses: 52.9.76.55
13.57.102.113
Aliases: ep-terminator.mistsys.net
-
If the nslookup command cannot resolve the
URL, explicitly add the URL to your DNS server.
-
If the issue is still not resolved, check the firewall and
proxy logs to see whether the traffic for the URL is getting
dropped. You can also take a packet capture to analyze
further.
|