Problem with zf7372 and ZD1100 in VPN

  • 1
  • Question
  • Updated 7 months ago
  • (Edited)
I have i problem connecting ZF in VPN.
I can connect zone flex to the zone director, but cant get wireless at all.

when i tracert form zone director i get
192.168.4.1
10.200.200.2
192.168.9.149

I am not sure what am i doing wrong.

if a configure access point in other subnet, but not in VPN, access point can connect to the ZD and have wireless radio enable, but in VPN can connect to ZD  and have wireless radio disabled

In ZD controler in monitor section, for ZF status says provisioning.

Here is log from access point:



Nov 30 15:39:41 RuckusAP daemon.warn Eved: Last Reboot Reason: user reboot

Nov 30 15:39:49 RuckusAP local2.err syslog: Parameter value L2 is invalid for parameter Tunnel-Mode

Nov 30 15:40:19 RuckusAP local2.err syslog: (ap state) AP begin to join ac. 

Nov 30 15:40:19 RuckusAP local2.err syslog: Cannot notify kernel for Upd AP Param 192.168.7.250(0) event, -- No such file or directory(2)

Nov 30 15:40:19 RuckusAP daemon.notice rsmd[24]: led ............. [stopped] (0.018)

Nov 30 15:40:21 RuckusAP daemon.notice rsmd[24]: led ............. [started] (0.093)

Nov 30 15:40:21 RuckusAP user.info kernel: v54_bsp: 0xff

Nov 30 15:40:21 RuckusAP local0.info snmpd[436]: Received TERM or STOP signal...  shutting down...

Nov 30 15:40:22 RuckusAP daemon.notice rsmd[24]: snmpd ........... [stopped] (1.280)

Nov 30 15:40:23 RuckusAP daemon.notice rsmd[24]: snmpd ........... [started] (0.628)

Nov 30 15:40:23 RuckusAP daemon.notice rsmd[24]: tr069 ........... [stopped] (0.081)

Nov 30 15:40:23 RuckusAP local0.info snmpd[849]: NET-SNMP version 5.3.0.1

Nov 30 15:41:26 RuckusAP local2.err syslog: Proceed to IDLE state from CONFIGURAION state, no resp after 15 re-transmits

Nov 30 15:41:26 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP 192.168.7.250(0) event, -- No such file or directory(2)

Nov 30 15:42:02 RuckusAP local2.err syslog: (ap state) AP begin to join ac. 

Nov 30 15:42:02 RuckusAP local2.err syslog: Cannot notify kernel for Upd AP Param 192.168.7.250(0) event, -- No such file or directory(2)

Nov 30 15:43:07 RuckusAP local2.err syslog: Proceed to IDLE state from CONFIGURAION state, no resp after 15 re-transmits

Nov 30 15:43:07 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP 192.168.7.250(0) event, -- No such file or directory(2)

Nov 30 15:43:46 RuckusAP local2.err syslog: (ap state) AP begin to join ac. 

Nov 30 15:43:46 RuckusAP local2.err syslog: Cannot notify kernel for Upd AP Param 192.168.7.250(0) event, -- No such file or directory(2)

Nov 30 15:44:51 RuckusAP local2.err syslog: Proceed to IDLE state from CONFIGURAION state, no resp after 15 re-transmits

Nov 30 15:44:51 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP 192.168.7.250(0) event, -- No such file or directory(2)

Nov 30 15:45:21 RuckusAP local2.err syslog: (ap state) AP begin to join ac. 

Nov 30 15:45:21 RuckusAP local2.err syslog: Cannot notify kernel for Upd AP Param 192.168.7.250(0) event, -- No such file or directory(2)

Nov 30 15:46:26 RuckusAP local2.err syslog: Proceed to IDLE state from CONFIGURAION state, no resp after 15 re-transmits

Nov 30 15:46:26 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP 192.168.7.250(0) event, -- No such file or directory(2)

Nov 30 15:46:51 RuckusAP local2.err syslog: (ap state) AP begin to join ac. 

Nov 30 15:46:51 RuckusAP local2.err syslog: Cannot notify kernel for Upd AP Param 192.168.7.250(0) event, -- No such file or directory(2)

Nov 30 15:47:56 RuckusAP local2.err syslog: Proceed to IDLE state from CONFIGURAION state, no resp after 15 re-transmits

Nov 30 15:47:56 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP 192.168.7.250(0) event, -- No such file or directory(2)

Nov 30 15:48:27 RuckusAP local2.err syslog: (ap state) AP begin to join ac. 

Nov 30 15:48:27 RuckusAP local2.err syslog: Cannot notify kernel for Upd AP Param 192.168.7.250(0) event, -- No such file or directory(2)

 
Photo of Bogdan Prascevic

Bogdan Prascevic

  • 9 Posts
  • 1 Reply Like

Posted 7 months ago

  • 1
Photo of Michael Brado

Michael Brado, Official Rep

  • 1889 Posts
  • 269 Reply Likes
Might need to contact TS to analyze all IPs and open ports/protocols needed.
Photo of Bogdan Prascevic

Bogdan Prascevic

  • 9 Posts
  • 1 Reply Like
i allready contacted them before posting here
Problem is when i do traceroute form access point to zone director i get form 10-20 seconds to even 200 seconds

When i do tracert form ZD to AP i get very low respons (lower than 100 ms)

I am not sure what to do

Any opinion is welcome

Thanks in advance