AP goes offline after dhcp change on customer site. Can`t reconnect to scg
public ip
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2018 02:55 AM
13 REPLIES 13
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2018 04:22 AM
Hi,
we have a vscg controller for our customers. We need to change the dhcp server on one customer site. We added option 42 for ntp server. After that, the APs on the site go offline.
After factory reset of the AP i signed in and set scg ip "public IP of our controller" and reboot this guy. But it didn`t appear in our controller.
On vscg the NAT IP is set and ports are forwared to vscg.
Actually it looks like this:
rkscli: get scg
------ SCG Information ------
SCG Service is enabled.
AP is not managed by SCG.
State: DISCONNECTED
Server List: -public ip of vscg-
No SSH tunnel exists
Failover List: Not found
Failover Max Retry: 2
DHCP Opt43 Code: 6
Server List from DHCP (Opt43/Opt52): Not found
SCG default URL: RuckusController
SCG config|heartbeat intervals: 300|30
SCG gwloss|serverloss timeouts: 1800|7200
-----------------------------
OK
I`m looking forward hearing from you guys.
Kind Regards
Christoph
we have a vscg controller for our customers. We need to change the dhcp server on one customer site. We added option 42 for ntp server. After that, the APs on the site go offline.
After factory reset of the AP i signed in and set scg ip "public IP of our controller" and reboot this guy. But it didn`t appear in our controller.
On vscg the NAT IP is set and ports are forwared to vscg.
Actually it looks like this:
rkscli: get scg
------ SCG Information ------
SCG Service is enabled.
AP is not managed by SCG.
State: DISCONNECTED
Server List: -public ip of vscg-
No SSH tunnel exists
Failover List: Not found
Failover Max Retry: 2
DHCP Opt43 Code: 6
Server List from DHCP (Opt43/Opt52): Not found
SCG default URL: RuckusController
SCG config|heartbeat intervals: 300|30
SCG gwloss|serverloss timeouts: 1800|7200
-----------------------------
OK
I`m looking forward hearing from you guys.
Kind Regards
Christoph
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2018 10:15 PM
You have to configure NAT-IP on SZ if SZ is locate behind NAT.
And you have to configure option 43 properly.
For option43, refer to https://shimi.net/services/opt43/.
And you have to configure option 43 properly.
For option43, refer to https://shimi.net/services/opt43/.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2018 01:21 AM
Hi Jeronimo,
Control NAT IP is configured. It works fine for other customers.
Why do i need option 43 if other Access Points, on other locations can connect to my controller without option 43?
Control NAT IP is configured. It works fine for other customers.
Why do i need option 43 if other Access Points, on other locations can connect to my controller without option 43?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2018 01:41 AM
You do not have to do option 43.
Do you deploy vsz-h or vsz-e?
Do you deploy vsz-h or vsz-e?

