Skip to main content
S

4 Messages

 • 

150 Points

Mon, Jan 18, 2021 7:15 AM

R600 suddenly cannot ping or connect to ZoneDirector

Hello,

We have an R600 AP that suddenly could not discover the ZoneDirector.

Doing a diagnostic Ping in the AP's Web GUI shows that it cannot ping the ZoneDirector or the other APs.

However, replacing this with a different AP does not show this problem of not discovering the ZoneDirector.

We have reset the R600 to no avail.

Any help or suggestion would be greatly appreciated!

Responses

289 Messages

 • 

4K Points

a month ago

As you can connect to Web GUI of AP, it has not yet adopted by ZD, but network connectivity must be  fine. But you can't ping other APs or Zd from it? Sounds weird. 

Are they all on same VLAN? What is firmware version of ZD and AP  -- is R600 supported by ZD firmware and is the firmware on AP suitable for connection? 

7 Messages

 • 

234 Points

a month ago

Sunstar# I am recommending first check the  status of  LED on your AP if working fine.please reboot your Zonedirector so see if it will add or you will be able to ping or access it.

2 years ago I had same problems after reboot finally  ZD1200 , so the problem was ZD and we replace. reboot and check LED status and Beep from ZD

Sebastiao Paulo Antonio 

4 Messages

 • 

150 Points

Hello Sebastiao Paulo,

The AP network LED status are okay and we already tried rebooting the ZD with the same result, unfortunately.

But thanks for the suggestion.

289 Messages

 • 

4K Points

a month ago

What are firmware versions of ZD and R600?

Are they on same VLAN?

Do you use VLAN1 (untagged) as management VLAN on ZD?

If you have WEB access to AP, it must be in standalone mode, what is the status of management services on it? Please, publish screenshot. You need to enable them to connect to  ZD. Also firmware of ZD must support R600.

It is weird that you can't ping other APs or ZD from R600, if  you can connect to is through WEB -- what AP is R600 getting, is it on correct VLAN? I don't see how it is possible that you have access to AP, but can't ping other APs, if they are on same VLAN and subnet. If they are on different subnets, than you may have incorrect default gateway on AP.

Hope ti helps.

4 Messages

 • 

150 Points

Hello @eizens_putnins 

Just to clarify, this AP was working fine up until last week when it suddenly showed disconnected status on ZD.  We swapped in a different AP and this was able to ping and discover the ZD just fine.

We are able to access the Web GUI because we attached a laptop to the second ethernet port on the AP.  It is in standalone mode because it could not discover the ZD.

We'll do more tests.

Official Rep

 • 

803 Messages

 • 

12.1K Points

a month ago

Hi,

Factory reset the AP, configure a manual IP address (same as ZD IP subnet) using GUI or CLI and plug the AP directly to the ZD's second or free port (you will need POE injector or power adapter to power up the AP). If AP comes up on ZD, this will rule out any network issue between ZD to AP.

Also make sure to check if management VLAN is tagged on ZD or not, if tagged, make sure you tag the VLAN when configure manual IP address.

Regards,

Syamantak Omer

4 Messages

 • 

150 Points

Hello @syamantak_omer 

Thank you for that suggestion.  That did the trick!

After connecting the AP directly to the ZD's second port, it was able to discover the ZD and get the configuration. When it was plugged back to the VLAN network for APs, it connected to the ZD right away.

This has been a strange issue but I'm glad this was resolved.  A big Thank You!

Official Rep

 • 

803 Messages

 • 

12.1K Points

Glad to know issue got fixed.

Regards,

Syamantak Omer

289 Messages

 • 

4K Points

Interesting that it worked. I would not expect it to work, as second port on ZD is not actually much of separate port. Possibbly you use tagged management VLAN, and provide DHCP from ZD? Anyway as issue is resolved, you can forget it (until next time)...