problem connecting after reset

  • 1
  • Question
  • Updated 3 years ago
Hello,

I'm struggling to connect to a ZoneFlex 7372. The only time I can achieve any response is during a full reset. After releasing the reset button, the host goes down for a second then as you can see below it responds to a ping for few moments then it stops again.

Needless to say, I can't get any response in the browser.

Any help would be great!

ping: sendto: Host is down
Request timeout for icmp_seq 32
ping: sendto: Host is down
Request timeout for icmp_seq 33
ping: sendto: Host is down
Request timeout for icmp_seq 34
Request timeout for icmp_seq 35
Request timeout for icmp_seq 36
Request timeout for icmp_seq 37
Request timeout for icmp_seq 38
Request timeout for icmp_seq 39
Request timeout for icmp_seq 40
Request timeout for icmp_seq 41
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=0.459 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=0.240 ms
64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=0.382 ms
64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=0.329 ms
64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=0.336 ms
64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=0.333 ms
64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=0.324 ms
64 bytes from 192.168.0.1: icmp_seq=52 ttl=64 time=0.222 ms
64 bytes from 192.168.0.1: icmp_seq=53 ttl=64 time=0.301 ms
64 bytes from 192.168.0.1: icmp_seq=54 ttl=64 time=0.240 ms
Request timeout for icmp_seq 55
Request timeout for icmp_seq 56
Request timeout for icmp_seq 57
Request timeout for icmp_seq 58
Request timeout for icmp_seq 59
Photo of Robert Wilde

Robert Wilde

  • 2 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Michael Brado

Michael Brado, Official Rep

  • 2183 Posts
  • 301 Reply Likes
I'd suggest to contact tech support, as you may need an RMA.
Photo of Robert Wilde

Robert Wilde

  • 2 Posts
  • 0 Reply Likes
I've actually worked out the issue, for others if they are experiencing simliar.

There was an active DHCP server connected to the POE switch, which was giving the Ruckus AP an IP during that short period.

I managed to connect to the AP no prob, when I looked at the connected devices within the DHCP server and found the dynamic IP that it was given.

What you're supposed to do is power up the AP without any other routers connected so it uses its own static IP - not always possible though if your POE switch is in use.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2183 Posts
  • 301 Reply Likes
Ah, it wasn't obvious that your AP was ZD managed in the inquiry.

If bringing up new APs in a production network, they will take local DHCP.

If this is not the VLAN/subnet the ZD is in, we recommend DHCP option 43/DNS
hostname resolution to point them, or you may need to use 'set director ip a.b.c.d'.

--
If bringing up/upgrading APs prior to ZD/AP deployment and not on a network,
you can temporarily use the built-in DHCP server (max scope 512 IPs).

If trying to bring up multiple new APs on a defaulted non-network ZD (192.168.0.2),
the first AP (default IP 192.168.0.1) will join, but all other APs after the first will not.